dokocino
Hello,
I'm a new user of DokuWiki, I installed it at work for my group and we have an issue with the draft auto-save feature.
When we get an issue where a draft is auto-saved for a page and we want to edit the page again, we have the option to restore the draft or delete the draft (or cancel). On this page only the cancel button works as intended.
Restoring the draft will open a page in source edition mode. From then if I click to switch back to ckgedit I get send back to the last saved version of the page and I have to click edit again (stuck in a loop).
If I click "save" it works but the new page display the source code of the page instead of the formatted page.
The other option, delete draft, just send me back to the page the way I clicked on cancel and if I click back on edit I have the question again about restoring or deleting the draft (so the draft was not deleted).
The only loop out of this is to save the corrupted page that display source code, then restore an old version from history.
What did I do wrong ?
turnermm
The auto save feature of ckgedit is designed to work with ckgedit and not between editors, i.e. switching from one to the other. In ckgedit if there is a browser crash or you have failed to save a document with unsaved edits, then you get the chance to restore the unsaved edits.
dokocino
Thanks for the answer and sorry for the delay since my last post, I had other issues that had to be solve but I'm back with this issue now.
I understand that it's two separate editors, I want to use only ckgedit, but when I got the "crash" or so that involve making a draft auto-saved, I'm stuck out of ckgedit and I have no way to use the saved draft, neither delete it, neither switch back to ckgedit. It's really annoying. No idea where it could come from ? I've re-install ckgedit with last update, but it's still the same. At least is there a manual way to delete the saved draft or to disable the auto-save ?
turnermm
If you get repeated crashes then there is something else wrong. The auto-save feature is tied directly into the Dokuwiki lock timer system and it's hard to see how that alone could be causing the crashes. It's been in place for six or seven years and has never before had any issues associated with it. From the way you describe it, it's hard to know what is happening.