# No longer able to edit old posts
**URL:** https://community.haxe.org/t/no-longer-able-to-edit-old-posts/1405
**Category:** Site Feedback
**Created:** [December 27, 2018, 7:47am UTC](https://community.haxe.org/t/no-longer-able-to-edit-old-posts/1405 "2018-12-27T07:47:19Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@AtomicPair](https://community.haxe.org/u/AtomicPair)
#### Post date: [December 27, 2018, 7:47am UTC](https://community.haxe.org/t/no-longer-able-to-edit-old-posts/1405/1 "2018-12-27T07:47:19Z")
This is a quick question for the admins.
I recently noticed that I was no longer able to edit [one of my posts](https://community.haxe.org/t/artstech-engine-development-log/1069), and a quick Google search seems to indicate that Discourse’s default `post edit time limit` setting may be to blame for this.
According to [this thread](https://meta.discourse.org/t/free-to-edit-post-at-any-time/35516), the default value of `86,400` minutes for that setting will prevent users from editing any posts older than 2 months, which is what I’m seeing here. That thread also states that admins should be able to use a value of `0` to permit post editing at any time.
Would it be possible to lift this restriction when editing posts on this site?
---
### Author:  [@AtomicPair](https://community.haxe.org/u/AtomicPair)
#### Post date: [January 5, 2019, 1:06am UTC](https://community.haxe.org/t/no-longer-able-to-edit-old-posts/1405/3 "2019-01-05T01:06:18Z")
@RealyUniqueName @mark.knol @ibilon Is this something one of you can assist with?
---
### Author:  [@andyli](https://community.haxe.org/u/andyli)
#### Post date: [January 5, 2019, 4:33am UTC](https://community.haxe.org/t/no-longer-able-to-edit-old-posts/1405/4 "2019-01-05T04:33:37Z")
I’ve just changed the limit from 86400 to 0 as you suggested. 🙂
---
### Author:  [@AtomicPair](https://community.haxe.org/u/AtomicPair)
#### Post date: [January 5, 2019, 4:53am UTC](https://community.haxe.org/t/no-longer-able-to-edit-old-posts/1405/5 "2019-01-05T04:53:38Z")
Sweet, looks like that fixed the problem. Thanks, @andyli!