Last modified: 2005-12-08 02:53:23 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 4195 - php error on SpecialUndelete.php
php error on SpecialUndelete.php
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.6.x
All All
: Normal critical (vote)
: ---
Assigned To: Nobody - You can work on this!
http://no.wikipedia.org/wiki/Spesial:...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-12-06 16:16 UTC by Seb35
Modified: 2005-12-08 02:53 UTC (History)
0 users

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


Attachments

Description Seb35 2005-12-06 16:16:54 UTC
I have already reported a similary bug #[[4167]], this time it was on http://no.wikipedia.org/wiki/
Spesial:Undelete, where I have no right (I was an IP), and I received the PHP error
Fatal error: Call to a member function on a non-object in /usr/local/apache/common-local/php-1.5/
includes/SpecialUndelete.php on line 352
Brion Vibber said the bug 4167 was 'A failure case in the patch for bug 153' perhaps it is the same 
thing.
Comment 1 Rob Church 2005-12-06 16:32:40 UTC
Confirmed as still being a problem.
Comment 2 Brion Vibber 2005-12-07 02:22:35 UTC
Under what circumstances is this triggered? If I just go to the page nothing untoward happens.
Comment 3 Rob Church 2005-12-07 02:25:34 UTC
Doesn't seem to be a problem for me any more. Caught out by a caching error when
I tried to reproduce a second ago - perhaps that's the issue here?

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


Navigation
Links