Transition Technology: Ticket #340: Auto-save: how does it work?

priority changed

ed — Thu, 22 Sep 2011 11:35:16 GMT

priority changed from major to critical

hours, totalhours changed

jim — Thu, 22 Sep 2011 14:18:23 GMT

hours changed from 0.0 to 0.2
totalhours changed from 0.0 to 0.2

Auto save wasn't enabled on SR blogs until a few days back...

How it works: It's set to autosave every 60 seconds silently in the background. It should load the saved version and show a blue banner at the bottom saying "This autosaved version, keep or delete" when people go back to either the node create page or the edit page of an existing node.

It's not working though :(

Something broke it at some point, not sure what, maybe varnish, maybe https, maybe something all together more mysterious...

Is this a high priority? I could take ages to find out the cause... Will look again after the SVN updates.

ed — Thu, 22 Sep 2011 14:38:48 GMT

look again after SVN updates

priority changed

jim — Thu, 06 Oct 2011 12:37:36 GMT

priority changed from critical to major

ed — Thu, 27 Oct 2011 13:51:26 GMT

worth looking at after git thing before end of phase 5?

hours, totalhours changed

jim — Fri, 28 Oct 2011 11:08:27 GMT

hours changed from 0.0 to 0.3
totalhours changed from 0.2 to 0.5

I've had another look around the issues list for the module, but nothing stands out...

I've added an exceptions or ignores to "443 Session" to try allowing/forcing non-ssl for /autosave/handler (the URL it sends saved forms to the site on) but nothing changed.

I'm minded to uninstall this module. It's broken, either by our configuration or by interaction with another module. Ed?

We could tell all those who use the site like this to save their content as unpublished and publish when they're ready, now we have that capability... Would need permissions updates.

hours, owner, status, totalhours changed

jim — Thu, 03 Nov 2011 23:51:46 GMT

hours changed from 0.0 to 0.05
owner changed from jim to ed
status changed from new to assigned
totalhours changed from 0.5 to 0.55

ED: please confirm...

I will remove autosave, since it's broken and I've run out of ideas as to why, and instead allow registered users to publish/unpublish their own blogs, stories, news and events... This way they can save when they want and publish when done.

Or shall we park this for now and let Laura plan it out? There's the 'save and continue' module we've used on CP for instance. It's a workflow/user interaction thing... let me know. Reassigning to you for a decision.

owner changed; cc set

ed — Fri, 04 Nov 2011 14:43:29 GMT

cc laura added
owner changed from ed to jim

confirmed. remove autosave, but don't instantly add the (un)publish to everything - that's Laura's decision from now on.

Laura's mooting the CP style - which following the experiences of the SR bloggers, who are not enjoying the editing and saving experience at all, I think is probably the way to go...

status changed; resolution set

jim — Tue, 22 Nov 2011 19:52:48 GMT

status changed from assigned to closed
resolution set to fixed

Autosave disabled.