Last modified: 2011-01-25 01:20:54 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 17509 - Special:RecentChanges returns a php error on
Special:RecentChanges returns a php error on
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Trevor Parscal
: shell
Depends on:
  Show dependency treegraph
Reported: 2009-02-15 18:42 UTC by Mike.lifeguard
Modified: 2011-01-25 01:20 UTC (History)
2 users (show)

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


Description Mike.lifeguard 2009-02-15 18:42:37 UTC
Fatal error: Call to a member function title() on a non-object in /srv/org/wikimedia/usability/extensions/LiquidThreads/LqtBaseView.php on line 215
Comment 1 Mike.lifeguard 2009-02-15 18:46:12 UTC
I guess it's simply a matter of updating the extension
Comment 2 Brion Vibber 2009-02-17 06:58:23 UTC
Trevor, can you fix this up when you get a chance? Thanks. :D
Comment 3 Mike.lifeguard 2009-03-20 18:30:06 UTC
Was fixed at some point - work now.
Comment 4 Trevor Parscal 2009-03-20 18:39:33 UTC
To be clear, the extension was not compatible with the version of MediaWiki, and even after updating and attempting to fix the code it was becoming clear that we were somewhat jumping the gun on using Lqt on our site. There's ongoing development on this extension now, and at some point in the future when it is stable and compatible we may reintroduce it to our site. In the mean time, we have just disabled it.

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