Last modified: 2009-01-21 01:26:07 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 T18025, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16025 - Call to undefined method SimpleCaptcha::showImage()
Call to undefined method SimpleCaptcha::showImage()
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
ConfirmEdit (CAPTCHA extension) (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-18 14:43 UTC by Siebrand Mazeland
Modified: 2009-01-21 01:26 UTC (History)
2 users (show)

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


Attachments

Description Siebrand Mazeland 2008-10-18 14:43:56 UTC
PHP Fatal error:  Call to undefined method SimpleCaptcha::showImage() in /var/www/w/extensions/ConfirmEdit/ConfirmEdit_body.php on line 57

[16:38] <siebrand> NicDumZ: can you give the me steps to reproduce for the issue?
[16:39] <NicDumZ> oh, that's you're not using image captchas !
[16:40] <NicDumZ> because.
[16:41] <NicDumZ> pywp is scraping for that line <input type="hidden" name="wpCaptchaId" id="wpCaptchaId" value="1495761080" />
[16:41] <NicDumZ> which appears on edits by new accounts

Still shouldn't result in a fatal error, I guess.
Comment 1 Siebrand Mazeland 2008-10-18 14:44:42 UTC
[16:43] <NicDumZ> and then tries to load http://translatewiki.net/w/index.php?title=Special:Captcha/image&wpCaptchaId=1495761080
Comment 2 Nicolas Dumazet 2008-10-18 14:53:52 UTC
To clarify this: pywp only supported image captchas until now; didn't know about word captchas. The bot was not supposed to access this page with a Word captcha, and the behavior has been fixed since.

Not sure if in the current version of the extension, such URLs have to be accessed; however such a behavior, even on a bad page title/use case, is wrong :)
Comment 3 Aaron Schulz 2009-01-21 01:26:07 UTC
Fixed in r45957

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


Navigation
Links