Last modified: 2009-12-30 05:09: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 T21461, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 19461 - Twinkle not working - wrong response from server
Twinkle not working - wrong response from server
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC Windows Vista
: Normal enhancement (vote)
: ---
Assigned To: Brion Vibber
http://ro.wikipedia.org/wiki/Utilizat...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-01 14:18 UTC by Daniel P.
Modified: 2009-12-30 05:09 UTC (History)
5 users (show)

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


Attachments

Description Daniel P. 2009-07-01 14:18:17 UTC
The API server at Romanian Projects (all of them) responds at form.wpTextbox1.value with null and I suspect that the entire 'editform' form is working incorectly.

Firebug extension for Mozilla Firefox: form is null
unlinkBacklinks()(Object currentAction=Unlinking on Pagina principală)index.ph...countme=s (linia 2)
onload()()index.ph...countme=s (linia 1)
var text = form.wpTextbox1.value;

Twinkle: Reverting page: couldn't grab element "editform", aborting, this could indicate failed respons from the server

Is this a different response from the Romanian APIs form the English ones? If yes, what is different?

P.S. I've also posted this question at the English Wikipedia but nobody was interested in the Romanian Wikipedia :|

Thank you.
Comment 1 Roan Kattouw 2009-07-01 14:22:30 UTC
Sounds like a bug in Twinkle's JS rather than a bug in the bot API Twinkle uses. Changing component.
Comment 2 Brion Vibber 2009-07-13 17:59:33 UTC
It sounds like Twinkle isn't using the API, but screen scraping -- which is likely to cause trouble... Looks like there's some bad HTML on the edit page, which is probably causing your trouble. See if we can work that out...

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


Navigation
Links