Last modified: 2013-07-13 23:57:24 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T53302, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51302 - Visual Editor: session is not (re)started when entering edit mode
Visual Editor: session is not (re)started when entering edit mode
Status: RESOLVED DUPLICATE of bug 50424
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: James Forrester
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-13 23:17 UTC by Chris McKenna
Modified: 2013-07-13 23:57 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Chris McKenna 2013-07-13 23:17:25 UTC
When loading the visual editor, the session is not (re)started and it continues the one from when you opened the editor in read mode. When the session expires the edits cannot be saved ("Error: We could not process your edit because your session has expired.")

Normally this isn't a problem, except it's counter intuitive (and apparently counter to the way the source editor works) when a page has been open for an extended time prior to entering the edit mode as it apparently continues that session rather than starting a new one. Unlike in source editor (which does work after an extended period in read mode) there is no possibility of working around a session expiry by clicking save again - the page must be reloaded and the edit made again by hand.

Steps to reproduce:
1. Open any VE-editable page in read mode
2. Wait until the session expires*
3. Launch the visual editor
4. Make a change and attempt to save the page

*I don't know how long this is but I encountered the error on a page open for 625 minutes (10.4 hours).

Bug 50424 is possibly related, but the person who reported this issue on en.wikipedia doesn't think so.
Comment 1 James Forrester 2013-07-13 23:57:24 UTC
This is the same problem as bug 50424; happily, we have code fixing this mostly done and we hope to have it deployed on Monday.

*** This bug has been marked as a duplicate of bug 50424 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links