Hi,

When autosave of this module is enabled, it saves the form even if it is blank, and in that way, blank drafts fill up the drafts table.

Also, when publish is clicked, the module doesn't remove the saved draft from the table which is actually needed.

Who needs the draft, after its published ?

Comments

darren.ferguson’s picture

darren.ferguson commented
Status: Active » Closed (fixed)
nileshgr’s picture

nileshgr commented
Status: Closed (fixed) » Active

why did you close it !??

cayci’s picture

cayci commented

same problem

darren.ferguson’s picture

darren.ferguson commented
Status: Active » Closed (works as designed)

Blank drafts are always created by the module this is part of how it works since the form api does not support it without the draft id being there. The cron job should remove any that were never updated.

lotyrin’s picture

lotyrin commented
Title: Blank drafts getting created, and some other problems » Avoid creating duplicate drafts.
Version: 6.x-1.8 » 6.x-1.x-dev
Category: bug » feature
Status: Closed (works as designed) » Active

Whether they're blank or not, if I have a draft open for a node, and go back to edit it again, I should be warned that there's already a draft for the node I'm editing and asked if I would like to resume it, discard it, or continue editing.

When I first save a draft (whether by auto-save or not), subsequent saves (and auto saves) should always re-use the same draft id.

If you refuse to keep this open as a bug, I've opened it as a feature. I will be investigating implementing this as a patch.