Last modified: 2014-08-09 00:04:50 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 T50775, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 48775 - You are not warned when log in is lost or expired
You are not warned when log in is lost or expired
Status: RESOLVED DUPLICATE of bug 69314
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 41466
Blocks:
  Show dependency tree / graph
 
Reported: 2013-05-24 11:59 UTC by Rainer Rillke @commons.wikimedia
Modified: 2014-08-09 00:04 UTC (History)
8 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Rainer Rillke @commons.wikimedia 2013-05-24 11:59:27 UTC 
If it happens that the log in is lost while translating, you don't get a reminder to please log in but instead the tool tries to save the translation under my IP. That's not correct behaviour.

Expected:
A please-log-in reminder. Nothing saved under my IP.
Comment 1 Andre Klapper 2013-06-05 14:55:53 UTC 
Potential duplicate of bug 48657?
Comment 2 Rainer Rillke @commons.wikimedia 2013-06-05 15:06:20 UTC 
(In reply to comment #1)
I don't think so. This extension makes use of the API and has to handle the refresh-token on its own.
Comment 3 Nemo 2013-09-09 05:58:18 UTC 
(In reply to comment #2)
> (In reply to comment #1)
> I don't think so. This extension makes use of the API and has to handle the
> refresh-token on its own.

This is bug 41466.

*** This bug has been marked as a duplicate of bug 41466 ***
Comment 4 Rainer Rillke @commons.wikimedia 2013-09-09 09:52:57 UTC 
Nemo_bis: This is not just about badtoken but about loss of logIn! Badtoken can also happen without loss of login. The workflow to fix it would be:

1) IMMEDIATELY! Prompt the user to log in if not logged-in anymore.
2) User logs in.
3) User confirms being logged-in to the translate extension.
4) Translate extension refreshes token.
5) Translate extension saves all unsaved translations.
Comment 5 Nemo 2014-08-09 00:04:50 UTC 

*** This bug has been marked as a duplicate of bug 69314 ***
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links