Last modified: 2014-06-19 14:17:18 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 T65832, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63832 - Huggle fails to recover from lost connectivity
Huggle fails to recover from lost connectivity
Status: RESOLVED FIXED
Product: Huggle
Classification: Unclassified
Application (Other open bugs)
3.0.0
PC Windows 7
: Normal major
: ---
Assigned To: Peter Bena
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-11 18:42 UTC by Jonatan Svensson Glad (Josve05a)
Modified: 2014-06-19 14:17 UTC (History)
2 users (show)

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


Attachments

Description Jonatan Svensson Glad (Josve05a) 2014-04-11 18:42:18 UTC
I just got this message when I tried to report 65.125.115.30 to WP:AIV.

"Failed to report user because: <?xml version="1.0"?><api servedby="mw1135!><error code="badtoken" info="Invalid token" /></api>"

You should be able to use "mw.Api().postWithToken" (or something similar, because I don't know anything about code, so I just copied from another project about badtokens) which IIRC automatically fetches a new token if you get a badtoken error.
Comment 1 Peter Bena 2014-04-21 17:06:09 UTC
mhm, you have any idea why this happened? why should I get new token when I receive badtoken error? Isn't mediawiki meant to use one token for session? That is how I understand it, were you logged out or something?
Comment 2 Peter Bena 2014-04-21 17:07:00 UTC
I am trying to say I don't know what is wrong neither how to reproduce it
Comment 3 Jonatan Svensson Glad (Josve05a) 2014-04-21 20:03:41 UTC
I might have gone afk for a short while and came acke, and then I was apparently logged out from Wikipedia on Chrome...might have been so as well on Huggle?
Comment 4 Jonatan Svensson Glad (Josve05a) 2014-04-21 20:03:55 UTC
came back*
Comment 5 Peter Bena 2014-04-23 17:46:44 UTC
yes that was probably the reason, it might have been related to session purging done by wmf recently, so I am closing this, it can't be reproduced, so it can't be fixed
Comment 6 Jonatan Svensson Glad (Josve05a) 2014-04-28 11:38:08 UTC
If I log out in Chrome, while having Huggle open, I can not edit in Huggle anymore (badtoken) I have to restart Huggle.

Even if I log in again in Chrome, I can't edit anymore. This is frustrating since I sometimes have to log in using my bot on Chrome, and then I see "a lot" of vandals in Huggle, that I can't revert...It would be better if it could fetch a new token...
Comment 7 Peter Bena 2014-06-19 14:15:45 UTC
https://github.com/huggle/huggle3-qt-lx/pull/86
Comment 8 Jonatan Svensson Glad (Josve05a) 2014-06-19 14:17:18 UTC
I can try to test it "a lot"...just release 0.3! :P

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


Navigation
Links