Project:Support desk

About this board

Welcome to the MediaWiki Support desk, where you can ask MediaWiki questions!

(Read this message in a different language)

See also

Before you post

Post a new question

  1. To help us answer your questions, please indicate which versions you are using, as found on your wiki's Special:Version page:
    • MediaWiki version
    • PHP version
    • Database type and version
  2. Please include the web address (URL) to your wiki if possible. It's often easier for us to identify the source of the problem if we can see the error directly.
  3. To start a new thread, click "Start a new topic".

1.39 Special Page extensions

2003:C2:3F21:FD00:D130:B302:B1E3:AC4 (talkcontribs)

Some of our own extensions are based on existing special pages. According to Mediawiki programming gudelines, the code looks like this:

class WantedPagesNeo extends WantedPagesPage {

        function __construct( $name = 'WantedPages_(PR_Neo)' ) {
                parent::__construct( $name );


Prior to 1.39, this used to work but now it crashes:

[739319141d78cf5548ef724f] /wiki/Spezial:Spezialseiten TypeError: Argument 1 passed to WantedPagesPage::__construct() must implement interface Wikimedia\Rdbms\ILoadBalancer, string given, called in /var/www/test/mediawiki/extensions/PPaddons/src/SpecialPages/WantedPagesNeo.php on line 26


from /var/www/test/mediawiki/includes/specials/SpecialWantedpages.php(39)
#0 /var/www/test/mediawiki/extensions/PPaddons/src/SpecialPages/WantedPagesNeo.php(26): WantedPagesPage->__construct()
#1 /var/www/test/mediawiki/vendor/wikimedia/object-factory/src/ObjectFactory.php(247): PP\SpecialPages\WantedPagesNeo->__construct()
#2 /var/www/test/mediawiki/vendor/wikimedia/object-factory/src/ObjectFactory.php(152): Wikimedia\ObjectFactory\ObjectFactory::getObjectFromSpec()
#3 /var/www/test/mediawiki/includes/specialpage/SpecialPageFactory.php(1279): Wikimedia\ObjectFactory\ObjectFactory->createObject()
#4 /var/www/test/mediawiki/includes/specialpage/SpecialPageFactory.php(1314): MediaWiki\SpecialPage\SpecialPageFactory->getPage()
#5 /var/www/test/mediawiki/includes/specials/SpecialSpecialpages.php(53): MediaWiki\SpecialPage\SpecialPageFactory->getUsablePages()
#6 /var/www/test/mediawiki/includes/specials/SpecialSpecialpages.php(42): SpecialSpecialpages->getPageGroups()
#7 /var/www/test/mediawiki/includes/specialpage/SpecialPage.php(701): SpecialSpecialpages->execute()
#8 /var/www/test/mediawiki/includes/specialpage/SpecialPageFactory.php(1428): SpecialPage->run()
#9 /var/www/test/mediawiki/includes/MediaWiki.php(316): MediaWiki\SpecialPage\SpecialPageFactory->executePath()
#10 /var/www/test/mediawiki/includes/MediaWiki.php(904): MediaWiki->performRequest()
#11 /var/www/test/mediawiki/includes/MediaWiki.php(562): MediaWiki->main()
#12 /var/www/test/mediawiki/index.php(50): MediaWiki->run()
#13 /var/www/test/mediawiki/index.php(46): wfIndexMain()
#14 {main}

What does it mean and where can I find documentation on how to correct it?

Jack Phoenix (talkcontribs)

This is a Dependency Injection (DI) related issue.

If you look at the source code of SpecialWantedpages.php as of REL1_39, you'll notice that the constructor's function signature has changed. These kind of changes are all over the place and will be in the future as well. Honestly, it's a mess.

Anyway, try changing your code to something like this, maybe:

	function __construct() {
		WantedQueryPage::__construct( 'WantedPages_(PR_Neo)' );

This may or may not work (also, I should note that the use of parentheses in a special page name like that is quite unusual). Having access to the actual code would aid in debugging.

Someone who understand's MW's DI and its current state can probably chime in and explain it more and better.

Bawolff (talkcontribs)

You need to pass the correct arguments to parent::__construct(). This can change between versions.

You can adjust your special page registration in extension.json to match what WantedQuery does so it gets the same arguments, which you could just pass on. Alternatively you can use the methods of MediaWiki\MediaWikiServices::getInstance() to get the relavent objects.

> According to Mediawiki programming gudelines, the code looks like this

When you say guidelines, is there a specific page you are referencing? I'm asking because if there is incorrect information somewhere i would like to correct it.

TheDJ (talkcontribs)

Seems the signature was accidentally/deliberately changed/broken in REL1_36 Probably because people assumed it was unused.

The documentation talks about a special page implementation subclassing the generic SpecialPage class, it is not a general example on how to do that for every single imaginable special page class. The best way to implement this tight now, is to, after calling the parent constructor, set $this->mName directly. This is how core classes like SpecialPrefixIndex.php do it.

Reply to "1.39 Special Page extensions"

1.39.6 function numRows missing

2003:C2:3F21:FD00:A1BE:8BA5:2092:924F (talkcontribs)

According to Manual:Database.php#Functions, we use the following code (extract):

$dbr = wfGetDB( DB_REPLICA );
$res = $dbr->query( ... some DB Query ... );
.... $dbr->numRows( $res ) ....

But we get:

Error: Call to undefined method Wikimedia\Rdbms\DatabaseMysqli::numRows()


from /var/www/test/mediawiki/includes/libs/rdbms/database/DBConnRef.php(103)
#0 /var/www/test/mediawiki/extensions/PPcheckRedirects/SpecialPPcheckRedirects.class.php(118): Wikimedia\Rdbms\DBConnRef->__call()
#1 /var/www/test/mediawiki/includes/specialpage/SpecialPage.php(701): SpecialPPcheckRedirects->execute()
#2 /var/www/test/mediawiki/includes/specialpage/SpecialPageFactory.php(1428): SpecialPage->run()
#3 /var/www/test/mediawiki/includes/MediaWiki.php(316): MediaWiki\SpecialPage\SpecialPageFactory->executePath()
#4 /var/www/test/mediawiki/includes/MediaWiki.php(904): MediaWiki->performRequest()
#5 /var/www/test/mediawiki/includes/MediaWiki.php(562): MediaWiki->main()
#6 /var/www/test/mediawiki/index.php(50): MediaWiki->run()
#7 /var/www/test/mediawiki/index.php(46): wfIndexMain()
#8 {main}

Prior to 1.39, the above code worked. Could this be an installation problem or has there been an undocumented redesign of the db access objects?

Bawolff (talkcontribs)

per the Release-notes file included with 1.39, numRows was removed

Use $res->numRows() instead.

TheDJ (talkcontribs)
2003:C2:3F21:FD00:89BA:CA55:9F1B:EC5A (talkcontribs)

$res->numRows, that was the piece of information I have been missing and wasn't able to find. Just to be sure: same problem with $dbr->freeResult, but there's no replacement ... right?

Works fine now, thank you.

@TheDJ no, I really don't want to. Non-voluntary. These are the sort of "improvements" that make Mediawiki worse, not better. I know someday I must but that's nothing I am looking forward to. I've seen many "closed circles" of software developers drifting away to outer space, your companions are en route. Honestly: we only stick to Mediawiki because there's no alternative.

TheDJ (talkcontribs)

No problem, we are only providing the software as a courtesy, without guarantee. Everyone is free to use whatever they want. Thank you for supporting free and opensource software.

Bawolff (talkcontribs)
2003:C2:3F21:FD00:89BA:CA55:9F1B:EC5A (talkcontribs)

Thank you for your patience.

Reply to "1.39.6 function numRows missing"

MediaWiki installing Error

Nexovia (talkcontribs)

Hello please can somone help me out I am in search of help since 10 days back what is this support for please can somone help me out of this is the problem. I am facing this problem while installation.

MediaWiki 1.41 internal error

Installing some PHP extensions is required.

Required components

You are missing a required extension to PHP that MediaWiki requires to run. Please install:

TheDJ (talkcontribs)

You have to install php-intl. how to do this depends on your operating system, the distribution of your operating system and how you installed php. It is not Mediawiki specific, but it is a prerequisite for Mediawiki.

Reply to "MediaWiki installing Error"

moving data from old version to new version

LouiseCooke1 (talkcontribs)

We have a new server where we are installing MediaWiki version 1.41.1.  We also have an older version 1.34.  We need to bring the data from the old version to the new version. What would be the best method for this?  Would exporting the pages from the old version & importing them to the new version be a good solution?

Docwikinoob (talkcontribs)

what os are you installing this on?

Reply to "moving data from old version to new version"
Waterlooglass (talkcontribs)

Hi all,

I have two related questions:

My images are being stored in the default folder on mediawiki, and I'm deployed on kubernetes and leveraging a PVC. Is there a way to migrate those images to AWS S3 without causing any breaking changes


Is there a way to utilize a second PVC for only images?

Reply to "Migrate Images"

Is there a way to make the TOC hidden by default?

Summary by
Txantimedia (talkcontribs)

I don't mean to get rid of it. I would refer that TOCs were displayed hidden with the show link being used to expand them. I've poked around through the manual and faq, but I haven't found anything about that. I guess another way to word this (which I've also searched for) is to have TOCs displayed collapsed by default, and opened by the viewer when desired. I do not want to use __NOTOC__. I want the TOC to be available, just not taking up the entire page before the article begins.

I could swear I saw this at Wikipedia somewhere, but I can't seem to find it.

Seb35 (talkcontribs)

I don’t have a complete answer but there is Manual:Table of contents where possibly there is a link to your desired feature. For Wikipedia, when you close the TOC, it is saved (in a cookie) and the next TOCs are then closed (well, it’s JavaScript, so it is closing when you open the page); when you re-open the TOC, it will then appear opened, etc.

Txantimedia (talkcontribs)

Thanks, @Seb35. I was not aware of the cookie setting. That would explain why I've seen it collapsed before. I looked through the Manual and the FAQ several times and didn't find the answer. I also found a template Template:TOC hidden, but it has no documentation, and the template code is beyond confusing.

The cookie info is useful.

#toc ul{



Will permanently hide the TOC. That is NOT what I want. (talkcontribs)

Nope, the CSS won't permanently hide the table of contents, a user can still click the show / hide link to show it.

Txantimedia (talkcontribs)

I put that code in MediaWiki:Common.css, and it didn't do anything. I put it in my personal common.css, and it didn't do anything. Perhaps I'm missing something?

Seb35's suggestion works though. If I close it, the next time I open the page, the TOC is closed.

Seb35 (talkcontribs)

I tried the CSS 197 gave, it works mostly but the word 'show' (or 'hide') is not always consistent with the real state.

If it does not work after you modified MediaWiki:Common.css, perhaps you need to force a hard refresh of the browser (Ctrl+F5 or Ctrl+R depending on the browser).

Txantimedia (talkcontribs)

That's probably true, but I like your fix better anyway. If you want it hidden when you open a page, hide it before you leave.

Rokejulianlockhart (talkcontribs)
Reply to "Is there a way to make the TOC hidden by default?"

findMissingFiles.php ..., what to do then?

2003:C2:3F21:FD00:89BA:CA55:9F1B:EC5A (talkcontribs)

When running findMissingFiles.php, I get a few files for which there is a database record but no image in the mediawiki/images directory. But what to do next? What I am missing is some documentation or hint of how to get rid of those database entries.

Reply to "findMissingFiles.php ..., what to do then?"

Media Wiki Installing error

Nexovia (talkcontribs)

I am facing this problem and I have tried opening php.ini file and deleting ; this from extension I am using Xampp local host for all process can somone help to get out fro this.

MediaWiki 1.41 internal error

Installing some PHP extensions is required.

Required components

You are missing a required extension to PHP that MediaWiki requires to run. Please install:

Malyacko (talkcontribs)

You need to install the PHP intl extension. I am not sure how to rephrase the error message to make it clearer, please elaborate what is unclear.

Nexovia (talkcontribs)

The problem as I has mentioned is the exact problem it says for installation of php so how could I do it.

Bawolff (talkcontribs)

What happened when you deleted the ; ?

Did you restart xampp? You have to restart for changes to take effect

Nexovia (talkcontribs)

I have restarted xamppp but it's not working.

Reply to "Media Wiki Installing error"

'Background' code is not supported

Summary by Шариф Ахмет

Thanks. Problem solved.

Шариф Ахмет (talkcontribs)

After moving our site to another server, a problem occurred. If a page of the site has 'background' code, it is now not possible to edit that page. This error occurs:

'403 Forbidden Access to this resource on the server is denied!'

But after deleting the "background" code on that page, everything is fine. How to solve this problem?

Jack Phoenix (talkcontribs)

Judging by some quick googling, it sounds like a problem with mod_security (no surprise there...). Try disabling it or if you don't have the access to do that, contact your hosting company to do so.

Шариф Ахмет (talkcontribs)

Thanks. Problem solved.

Nexovia (talkcontribs)

The Wiki as I have already talked about Shout Wiki I actually exactly not know that the founder of wiki should update wiki version or it can be done with MW Shout Wiki was just emerging wiki host but due to their own founder and staffs became inactive so I would know what should be done now.

Bawolff (talkcontribs)

You would have to take that up with ShoutWiki admins.

Nexovia (talkcontribs)

There is no single admin active or Stewards or Staff none is active that's why I am asking here for a way.

Bawolff (talkcontribs)

We have no control over shoutwiki.

Jack Phoenix (talkcontribs)