Opened 15 years ago
Closed 13 years ago
#12515 closed enhancement (wontfix)
Destructive Autosaves Happening on All Drafts
Reported by: | miqrogroove | Owned by: | azaozz |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | minor | Version: | |
Component: | Revisions | Keywords: | |
Focuses: | Cc: |
Description
I'm investigating reports of post drafts magically reverting or not being saved at all. This appears to be happening at random, and so far I cannot find the cause. In the meantime, I have discovered a related problem: WordPress 2.9.2 is continuously overwriting drafts during editing.
Steps to Reproduce:
- Create a New Post
- Click Save Draft (or wait for autosave)
- Edit the content and wait 60 seconds.
- Repeat step 3 as many times as you like. Go to other pages. Come back. Do anything other than click Save Draft, and WordPress will repeatedly overwrite the saved information without creating any revisions or autosave records.
This is especially destructive if in step 2 the draft was autosaved by WordPress. In that case, there are no revisions at all. If you clear the content at that point, WordPress essentially deletes your draft without confirmation.
Change History (10)
#2
@
15 years ago
AFAIK, This is by design.
Revisions should not be created for every draft autosave.
Revisions are only created of manual/final saves.
#3
@
15 years ago
Why doesn't the autosave create autosave records now? I can only get it to happen on published posts.
#4
@
15 years ago
- Milestone 2.9.3 deleted
- Resolution set to invalid
- Status changed from new to closed
- Version 2.9.2 deleted
Autosave follows the same logic like any text editing program. If you start a new document in MS Word, type something then delete it, the autosave there will save the empty document. If you've opened an existing document the autosave will create new document/revision leaving the old one intact until the Save button is clicked.
That's why there is multi-step undo in TinyMCE like most text editors, so if you deleted something by mistake you can press Ctrl-Z (or use the Undo button) to get it back.
Closing this as invalid as part of the problem is caused by a plugin and the other part is expected behaviour not just in WordPress but in many text editors.
#5
follow-up:
↓ 6
@
15 years ago
- Milestone set to 2.9.3
- Resolution invalid deleted
- Status changed from closed to reopened
If you've opened an existing document the autosave will create new document/revision
No it doesn't. That only happens on published posts.
#6
in reply to:
↑ 5
@
15 years ago
- Component changed from Autosave to Revisions
- Milestone changed from 2.9.3 to Future Release
- Priority changed from highest omg bbq to normal
- Severity changed from blocker to minor
- Type changed from defect (bug) to enhancement
Replying to miqrogroove:
(In MS Word) If you've opened an existing document the autosave will create new document/revision
No it doesn't. That only happens on published posts.
Yes, currently "saved" in a text editor = "published" in WordPress. If you're suggesting to add revisions to drafts, I see how this can benefit people that edit a draft over a number of days and might want to check an old version of it. However this is an enhancement (feature request?) and some people would be opposed to having more revisions.
Generally drafts are overwritten and the multi-step undo is in place to correct any mistakes like in most text editors.
FWIW, the other half of this bug, where posts are magically not being saved at all, is caused by qTranslate.
Currently, the best workaround is to use WordPress 2.8.