gelfling

The problem arises when an autosave is the last edit (id) for any particular post.

To fix the problem:

1) Sign in to your server control panel and go to your phpMyAdmin to access your SQL database

2) Access the table called [your installation]posts

3) Sort the table by post_parent

4) If you know the number of the post that’s causing you grief (eg. 123), navigate to where the post_parent numbers match your ineditable post (post_parent = 123)

5) Among the data for each record you will see something like this:
ID … post_name … post_parent
456 123-revision 123
457 123-revision-2 123
458 123-revision-3 123
459 123-autosave 123

There will be no more revisions for post 123 following the autosave.

6) Edit the autosave record and change the post_name to be the next revision number
In our example, ID number 459 needs to be changed so the post_name is 123-revision-4
The corrected data would then look like:
ID … post_name … post_parent
456 123-revision 123
457 123-revision-2 123
458 123-revision-3 123
459 123-revision-4 123

That’s it! You can now use WordPress as usual and go edit your post.

NOTE: If you find records that look something like this:
ID … post_name … post_parent
456 123-revision 123
457 123-revision-2 123
458 123-autosave 123
459 123-revision-3 123

DO NOT change the post_name of the autosave. This record (or post) is fine and should be able to be edited in WordPress. Editing is only a problem if the autosave is the last ID for the post.