Ticket #2242 (new defect)

Opened 6 months ago

Last modified 2 months ago

Session timeouts break CMS and let you lose data

Reported by: smagnusson Assigned to: sminnee
Type: defect Priority: blocker
Milestone: 2.2.3 Component: CMS - Field editor
Version: 2.2.1 Severity: medium effort / impact
Keywords: Cc:
Due date: Harvest Task: (Unknown)
Invoice sent to client: 0 Hours:

Description

If you're editing a page, go for lunch, and try to resume work, by further editing the page, then go to save, you lose all your work because it asks you to login again.

This is unacceptable and has wasted a lot of my time on numerous occasions. Firefox's back button doesn't rescue you; your edits must entirely be rewritten.

The session system must be updated to be more persistent. If I have ticked 'keep me logged in', then it must do so.

Related, if you try to 'add a page' after leaving silverstripe idle, it does nothing. No user feedback.

Attachments

Change History

Changed 6 months ago by sminnee

  • milestone changed from 2.2.2 feature-lock to 2.2.3 feature-lock

Moving to 2.2.3. Since this is a long-standing issue, it appears that we've been able to cope with the system as it currently is. Leaving priority as blocker to make sure that it really does get done in 2.2.3 and isn't pushed even further out.

In terms of fixes - opening the log-in window in a lightbox could be quite successful; that way, we don't need to shut down the CMS session to re-authenticate.

Changed 4 months ago by afranks

Is there a way to adjust the timeout time... it seems that for whatever reason, I can't even post a normal text edit without being booted. Sometimes I don't even have enough time to add an new editor, and it is the chief (and so far, only) complaint that I have received.

Changed 2 months ago by sharvey

This is related to #2622.

Note: See TracTickets for help on using tickets.