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".
Hydrofox78 (talkcontribs)

I installed everything correctly as I have in the past a thousand times, and for some reason there is no skin showing at all. Please, if anybody can help me get this sorted, I'd be forever grateful.


http://direfall.com/index.php?title=Main_Page

Malyacko (talkcontribs)

See the network tab of your browser's developer tools: There is a 500 Internal Server Error.

Hydrofox78 (talkcontribs)

I have working wikis that have the same internal server error. But those wikis still show up fine. This is strange. I've done a complete fresh install again with entirely new databases. I also made sure PHP is defaulted to 8.1. I'm not seeing a single reason why this should be happening.

Reply to "1.38.4 not showing any skin."

How to prevent "detached head" when downloading bundled extensions with Git?

6
Stefahn (talkcontribs)

After downloading the MediaWiki 1.38 core I do git submodule update --init --recursive to download all bundled extensions.

The problem is: All extensions are checked out as a "detached head". I need to do git checkout REL1_38 in all extensions subfolders to fix that. Otherwise I can't update the extensions with git pull.

Is there an easy way to checkout REL1_38 directly and prevent the detached heads?

Bawolff (talkcontribs)

Just to confirm, when you say "After downloading the MediaWiki 1.38 core" you mean that you git clone'd the mediawiki git repo, and then checked out REL1_38?

I suspect your issue might have to do with REL1_38 being a remote branch.

Stefahn (talkcontribs)
Jonathan3 (talkcontribs)

I used git once for MediaWiki core, thinking it would save time in the long run, but it didn't, and now I just download the tarball when I upgrade. I only use git for extensions and skins. I know that doesn't directly answer your question...

Stefahn (talkcontribs)

Git saves me a lot of time when updating - no more searching for patch files and stuff.

Has anyone a solution to prevent the "detached head" problem?

Bawolff (talkcontribs)

Instead of using git pull, maybe try git submodule update --remote --recursive (never trued myself, but i hear it works)


You could also use git submodule foreach to do the checkout command on each submodule.


You may get better answers on a git support forum.

Reply to "How to prevent "detached head" when downloading bundled extensions with Git?"

Mediawiki running on PHP v 7.4.25 is going to expire in 10 days

12
Pooja2425 (talkcontribs)

Hi Team,

Product Version
MediaWiki 1.35.3
PHP 7.4.25 (apache2handler)
MySQL 8.0.27
ICU 69.1
Lua 5.1.5
Elasticsearch 6.5.4

Currently we are using above Software, But from security Team we got alert that PHP 7.4 Security Support going to end in 10 days, 28 NOV 2022 .https://www.php.net/supported-versions.php

Also if we want to upgrade PHP version to PHP 8, then MediaWiki is not compatible with PHP 8 clearly mention in Compatibility#PHP.

As we can see MediaWiki (1.38) runs on PHP 7.4.3 and higher. But now PHP 7.4 is going to expire . Please suggest us what we need to do ?

213.237.93.136 (talkcontribs)

My wiki uses 8.1 and works totally fine.

Bawolff (talkcontribs)

You should be fine using php 8 or 8.1 with mediawiki. Some minor fixes for php 8 were included in 1.38, but even in 1.35 there aren't really any important bugs.

Note that if you want to stick with php 7.4, i think debian is supporting it past php eol.

Pooja2425 (talkcontribs)
62.68.29.252 (talkcontribs)
Pooja2425 (talkcontribs)

I am running MW 1.35.3 with PHP 8.0 , minor changes for variables & constants i did. Now its working fine.

Pooja2425 (talkcontribs)
Malyacko (talkcontribs)
Malyacko (talkcontribs)

Plus you also posted this as Topic:X7kkfc8258e3uepc. Please do not post in several places, it is not a good use of anyone's time and fragments conversations.

Pooja2425 (talkcontribs)
Malyacko (talkcontribs)

Correct. Please only ask for help on the mediawiki.org Support Desk, and please report software bugs on phabricator.wikimedia.org by following How to report a bug. Thanks!

Bawolff (talkcontribs)

Also if you made unspecified changes to the extension, its much less likely anyone is going to help as we have no idea what you changed or if your issues are the result of the changes you made.

Reply to "Mediawiki running on PHP v 7.4.25 is going to expire in 10 days"

VisualEditor conflicts with templates ("Error contacting the Parsoid/RESTBase server (HTTP 500)")

2
171.33.249.12 (talkcontribs)

Hello friends! After installing the latest version of MediaWiki (1.37.1) I can't get VisualEditor (VE) to work with templates. VE works great without templates. Also, VE allows you to initially insert a template into an article. But if you try to edit an article with the help of VE, in which the template has already been inserted, then when you start editing, the error "Error contacting the Parsoid/RESTBase server (HTTP 500)" occurs. At the same time, the standard wiki markup editor works correctly with templates in articles. And one more observation - if you remove the template from the article using the standard editor, then VE will edit this article normally again.

In other words, the presence of {{}} in the code of a wiki article causes VE to crash.

If anyone has come across a similar issue and managed to solve the problem, please share the solutions!

Thank you in advance!

77.109.186.169 (talkcontribs)

I had the same issue on 1.35.8 with php 8.1 and fixed it by switching to php 7.4.

I found the hint for the solution here: phabricator.wikimedia.org/T270377

Reply to "VisualEditor conflicts with templates ("Error contacting the Parsoid/RESTBase server (HTTP 500)")"

MPDF version 6.1 not working with PHP 8

3
Pooja2425 (talkcontribs)

Product Version

MediaWiki 1.35.3

PHP 8.0.25 (apache2handler)

MySQL 8.0.26

Lua 5.1.5

Elasticsearch 6.5.4

We are using above & Mpdf 6.1 Extension:Mpdf as erlier we re using php v7.4 . But Now we have upgraded the Php to 8.0 and PDF is not working, done so many changes i.e () to [] ,replaced each() with new function in mpdf file but still facing issues. pls suggest which mpdf version we need to use for pdf .

also when trying to update mpdf to another version facing issues with elastic search

  Problem 1

    - elasticsearch/elasticsearch v6.5.0 requires php ^7.0 -> your PHP version (8.0.25) does not satisfy that requirement.

    - elasticsearch/elasticsearch v6.5.0 requires php ^7.0 -> your PHP version (8.0.25) does not satisfy that requirement.

    - Installation request for elasticsearch/elasticsearch  6.5 -> satisfiable by elasticsearch/elasticsearch[v6.5.0].


As elastic server 6.5.4 is suitable for MW 1.35.3 & ElasticSearch Php Client 6.5 for Elastic Server 6.5.4.


Please suggest what to do for pdf.

Pooja2425 (talkcontribs)

Warning: Undefined variable $footer in /data/www/html/wiki/extensions/Mpdf/MpdfAction.php on line 39

[Y4BnM7MF2q2VgmHCDaL-kQAAAAE] /wiki/...../&action=mpdf MpdfException from line 297 of /data/www/html/wiki/extensions/Mpdf/vendor/mpdf/mpdf/classes/otl.php: Can't open file /data/www/html/wiki/extensions/Mpdf/vendor/mpdf/mpdf/ttfontdata/dejavusansmono.GSUBGPOStables.dat


also header is not coming in pdf when generating pdf in some pages, alignment issue also there.

As in php 7 supporting int+float+string , but not php 8. i.e ( 10px+27px +auto ) so many issue in mpdf 6.1 libary code in php 8.

Bawolff (talkcontribs)

Neither of those errors you posted sound like php8 issues.

You should probably take this up with the extension maintainer.

Reply to "MPDF version 6.1 not working with PHP 8"

Dump loading order for en Wikipedia

2
31.44.94.162 (talkcontribs)

I want to restore dumps for english wikipedia (https://dumps.wikimedia.org/enwiki/20221001/). In what order should I do it? First sql dumps, and then xml?

The dumps contain *-pagelinks.sql.gz, *-imagelinks.sql.gz, etc. Do I need to do a refreshlinks.php if the dumps already have these datasets?

Bawolff (talkcontribs)

I dont think the order matters as long as the importer is not refreshing links (if it was, the .sql files are pointless).

If you import the .sql link tables, running refreshLinks.php should be unnessary. Also refreshLinks is very slow, running it on an enwikipedia import will probably take the rest of your life.

Reply to "Dump loading order for en Wikipedia"

How to exclude noindex pages from sitemap?

1
Stefahn (talkcontribs)

I have some pages that should not be indexed. How do I exclude them from the script generateSitemap.php?

In fact those pages include <meta name="robots" content="noindex"/> in their head. This is set with help of the Extension:WikiSEO.

Reply to "How to exclude noindex pages from sitemap?"
Jdm.oliveira (talkcontribs)

Is it possible to query multiple endpoints at once (for example, Wikidata, Europeana and our own pages) and then represent the returned properties in a map or data table, as it is possible to do with a single endpoint? I wanted to be able to show common properties between these endpoints and each of their entries.

Reply to "LinkedWiki problems (SMW)"

Calling Loop index inside #if (Parser functions and LoopFunctions extensions)

3
Jdm.oliveira (talkcontribs)

I wanted to create a condition inside a for loop that used the index of the loop. According to the LoopFunctions documentation, one can call the index with $n$. This works inside the for, but not if it is inside a parser function that is inside a for loop. Is there something I am missing or is it simply not possible to use the index inside another function?

Jonathan3 (talkcontribs)

What about using the Scribunto extension? It's not as difficult as it first seems.

Jdm.oliveira (talkcontribs)

Sorry that I forgot to answer. Thank you, Scribunto did the trick after some research.

Reply to "Calling Loop index inside #if (Parser functions and LoopFunctions extensions)"

trouble with coding common.js use api

4
Samosbor.sheo (talkcontribs)

Hi! My code executing checkcomments() function with TypeError: mw.Api is not a constructor, also type checkcomments() in console executing is succefull. Help please

Ciencia Al Poder (talkcontribs)

You need to load the mw.Api client library first before using it. You'll need to wrap the call of the function that uses mw.Api inside mw.loader.using:

ResourceLoader/Core_modules#mw.loader.using

mw.loader.using( 'mw.Api' ).then( function () {
  // Call to the function that uses mw.Api
} );
BertrandGorge (talkcontribs)

For future reference in case anyone falling here, the above advice is good but the syntax didn't work for me. This did:

mw.loader.using('mediawiki.api', function() {
  // Call to the function that uses mw.Api
} );
Ciencia Al Poder (talkcontribs)

You're right, it's "mediawiki.api" and not "mw.Api"

Reply to "trouble with coding common.js use api"