Last modified: 2014-04-15 15:42:11 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 T39227, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37227 - Handle loss of session data
Handle loss of session data
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Wikidata bugs
: need-volunteer
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-30 17:50 UTC by jeblad
Modified: 2014-04-15 15:42 UTC (History)
4 users (show)

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


Attachments

Description jeblad 2012-05-30 17:50:17 UTC
The user can be logged out due to several reasons and then the token will be illegal and use of it will lead to a session failure. In ApiSetItem this is reported as a no-token -error which is wrong. When this happens the error message should be intercepted and the user logged in again. Preferably without the user loosing any on-going changes.

A guess is that a small popup window asking for user credentials should be sufficient, and after logging in the user through the ordinary API the Wikibase API can be queried for new token(s).
Comment 1 denny vrandecic 2012-06-21 13:17:58 UTC
API needs to return new token on session loss. AJAX calls should recognize that error, replace the token, and let the editor retry (could even automatically retry).
Comment 2 denny vrandecic 2012-06-21 13:20:40 UTC
A new session might be needed as well.

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


Navigation
Links