Bug #801
closed
Timeout is too short
Description
I've had it time out on me in the middle of editing, and it's awful, I lose all my edits. Heidi recently emailed saying her edits were lost, presumably from the same behavior. I think GET-Evidence really doesn't need to be so strict about this, especially since the consequences of accidental timeout are so bad.
I think this should be fixed in the next week (urgent) so we can encourage authors interested in contributing to GET-Evidence to do so immediately. (Their offer is going to go stale if we aren't responsive.)
Files
Updated by Tom Clegg over 12 years ago
The production site now has a 2 day idle session timeout (the default in PHP is 24 minutes) and this is now recommended in the INSTALL doc as well.
Updated by Tom Clegg over 12 years ago
- Status changed from New to Feedback
- Assigned To set to Tom Clegg
- % Done changed from 0 to 90
- Resolution set to fixed
Updated by Tom Clegg over 12 years ago
- Status changed from Feedback to In Progress
- % Done changed from 90 to 40
- Resolution deleted (
fixed)
Even worse than the short timeout is the fact that clicking "save draft" in a timed-out session results in a "saved 1:23 pm" message, even though it hasn't. This situation should cause a prompt to log in again, using a process that doesn't destroy the unsaved content (perhaps via pop-up window or iframe).
Updated by Tom Clegg over 12 years ago
- Status changed from In Progress to Resolved
- % Done changed from 40 to 100
- Resolution set to fixed