Last modified: 2006-09-08 10:16:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 6615 - PHP fatal error on bad input to Special:Movepage
PHP fatal error on bad input to Special:Movepage
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.8.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/w/index.php?t...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-10 06:39 UTC by Nick Jenkins
Modified: 2006-09-08 10:16 UTC (History)
0 users

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


Attachments
Patch to fix null object bug (515 bytes, patch)
2006-09-08 08:56 UTC, wclark
Details

Description Nick Jenkins 2006-07-10 06:39:26 UTC
http://en.wikipedia.org/w/index.php?title=Special:Movepage&action=success

Will show blank page (due to error logging); but on a non-error-logging wiki,
the same thing will display this PHP fatal error as the output:
=================================================================
Fatal error: Call to a member function isTalkPage() on a non-object in
/var/www/hosts/mediawiki/phase3/includes/SpecialMovepage.php on line 269
=================================================================
Comment 1 Tim Starling 2006-07-10 06:41:34 UTC
I'm not sure if this is a bug. There are lots of ways to generate PHP error 
messages, some of them are beyond our control. I don't think it's a 
security issue, it's barely a code quality issue. I guess the only issue is 
whether it generates unwanted noise in automated testing.
Comment 2 Brion Vibber 2006-07-10 06:43:19 UTC
It's certainly a bug, though quite likely entirely harmless.
Comment 3 wclark 2006-09-08 08:56:29 UTC
Created attachment 2326 [details]
Patch to fix null object bug
Comment 4 Rotem Liss 2006-09-08 10:16:35 UTC
Applied to r16436, but changed a bit.

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


Navigation
Links