Last modified: 2010-05-15 15:54:50 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 14494 - 'SpecialPage_initList' hook appears to be broken
'SpecialPage_initList' hook appears to be broken
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.12.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-10 08:07 UTC by Lisa Ridley
Modified: 2010-05-15 15:54 UTC (History)
2 users (show)

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


Attachments

Description Lisa Ridley 2008-06-10 08:07:11 UTC
Any functions hooked into SpecialPage_initList do not appear to ever get invoked; this hook appears to be broken.
Comment 1 Christian Neubauer 2008-06-10 18:38:02 UTC
I can't duplicate this on a 1.12.0 installation.  This extension code calls the hook function and dies properly.

$wgHooks['SpecialPage_initList'][] = 'testInitList';

function testInitList(&$list ) {
    die('initList hook is being called.');
}

Is your problem that the hook function is never being called or that you can't manipulate the $list parameter?
Comment 2 Lisa Ridley 2008-06-10 19:14:20 UTC
I have no idea...I set up pretty much the same hook that you did and it never got executed. :(

None of the extensions I have implemented are using this hook, but there may be a conflict elsewhere.  Let me take a look and see if can isolate this to an extension

Thanks for looking at it.  Please leave this open for now.  :)
Comment 3 Siebrand Mazeland 2008-08-13 21:25:10 UTC
+testme
Comment 4 Lisa Ridley 2009-01-22 16:23:24 UTC
Let's close this for now.  I haven't been able to reproduce the error, so I have to assume it was something I did on my end.

Sorry :)

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


Navigation
Links