Last modified: 2010-05-15 15:33:08 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 1899 - Invalid pagename in URL gives "Fatal error" rather than failing gracefully
Invalid pagename in URL gives "Fatal error" rather than failing gracefully
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
All All
: Low trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-04-15 18:28 UTC by Marc Adler
Modified: 2010-05-15 15:33 UTC (History)
0 users

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


Description Marc Adler 2005-04-15 18:28:07 UTC
I accessed a wikipage in a special namespace. Trying to return to some kind of
index-page i removed the part after the colon an got an PHP Error:

Fatal error: Call to a member function on a non-object in
/usr/local/apache/common-local/php-1.4/index.php on line 50

I tried it with
Comment 1 Rowan Collins [IMSoP] 2005-04-15 19:27:21 UTC
Hm. I guess the title code is trying to look up a page with no name (just a
namespace) and failing, and the display code is not checking for this condition.
Testing reveals that other invalid pages behave the same, e.g.

The line in question just needs a check like "if(!$wgTitle)", initialising some
"invalid pagename" text, which I have a feeling we already have for other purposes.
Comment 2 Brion Vibber 2005-04-15 19:49:33 UTC
Broken code in the variant handling. I've reverted the change again pending correct fixes in that code.

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