
I have discovered, and fixed in a 'hot-fix' patch, an error with the local autosave functionality which would have affected people who become logged out for some reason while they're editing or creating a new entry.
The investigation was trigged as I received notification that a user is being logged out after 2 hours of inactivity having started an entry then returning later only to end up losing everything in that entry.
I am still investigating why the user is being logged out - there should be no reason for someone to get logged out after 2 hours unless they have set the idle timer (and I've checked, they haven't).
However, the bug I have found is that any error from the backend when trying to save an entry could potentially throw a 'Not Logged In' error as the front end cannot confirm you're logged in if the backend goes away briefly. This may be the cause of the you've been booted error and I will look to make that more robust going forward.
However, the system stores your work locally until you save it. This is meant to protect against these sorts of things - or accidental navigations away from the site, or accidental closure of browser windows / power outages etc. But a couple of bugs had somehow been introduced which, under certain circumstances meant that your locally saved draft would be inadvertently deleted before offering you the option to use it.
This has now been fixed.
If you find yourself logged out (or any other minor catastrophe loses your connection to the server) then the system will tell you you're logged out. Press the dialog box twice to get logged back in (that's another bug I need to get to the bottom of, it should only need one click) and then login in the normal way. You should then be presented with a popup telling you a local draft exists.
Apologies for this inconvenience. I know this doesn't get to the bottom of the logging out completely, but it hopefully restores a mitigating factor that should've always been there.
Please let me know of any issues as you find them!
Steve.
Comments (2)
I've noticed when I write an entry and save it as a private entry then edit it > save as private > edit, save etc...that the calendar date goes back a day for each time I save. So, for example, if I edited an entry three times today, when I go to save it, the date that is highlighted is three days ago, and I manually change it back to today before saving it. Could that be part of the issue?
Hmm, no I suspect thatβs a time zone bug youβve managed to find. Iβll take a look.
Thanks for letting me know, keep up the bug reports if you find them :)