Last modified: 2007-05-08 21:22:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T8800, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 6800 - LinkSearch often doesn't show up in list of special pages
LinkSearch often doesn't show up in list of special pages
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
LinkSearch (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-24 04:58 UTC by Thomas Hempel
Modified: 2007-05-08 21:22 UTC (History)
0 users

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


Attachments

Description Thomas Hempel 2006-07-24 04:58:13 UTC
Currently it has a very unusual way of registering itself as a special page,
which often doesn't work. making it use the recommended way specified in
SpecialPage.php makes it work consistently.
It requires changing the area around line 21 of LinkSearch.php to:
 	$wgSpecialPages['Linksearch'] = array ('SpecialPage', 'Linksearch');
Comment 1 Brion Vibber 2006-08-31 17:09:50 UTC
Seems to work fine...?
Comment 2 Gunter Schmidt 2007-03-16 13:58:43 UTC
I can confirm this bug. Maybe it is due to the german localization.

Used 1.9 and 1.10 with LinkSearch of today.

Comment 3 Gunter Schmidt 2007-03-17 11:23:19 UTC
The require_once call has to be placed before all other extension calls.
Comment 4 Rob Church 2007-03-17 17:03:07 UTC
(In reply to comment #3)
> The require_once call has to be placed before all other extension calls.

Not an acceptable workaround; extensions MUST NOT interfere with other code in a
negative fashion.
Comment 5 Brion Vibber 2007-05-08 21:22:43 UTC
This will have been fixed a couple weeks ago; several extensions were not
returning correct code from hook, thus aborting other extensions. :)

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


Navigation
Links