Project:Support desk

Jump to: navigation, search

About this board

vde   Welcome to's Support desk, where you can ask MediaWiki questions!

There are also other places where to askCommunication: IRCCommunication#Chat, mailing listsMailing lists, Wikimedia Developer Support, Q&A, mwusers (unofficial forum) etc.

Before you post

Post a new question

  1. To help us answer your questions, please always indicate which versions you are using (reported by your wiki's Special:Version page):
    • MediaWiki
    • PHP
    • Database
  2. Please include the URL of your wiki unless you absolutely can't. It's often a lot easier for us to identify the source of the problem if we can look for ourselves.
  3. To start a new thread, click "Start a new topic". (talkcontribs)

In the 1.31 version. I exported the local data to XML and imported it to the public network. I found that the classification was lost. What is the reason for this?

  • MediaWiki:1.31
  • PHP:7.1
  • Database:mysql5.7
Ciencia Al Poder (talkcontribs)

What do you mean by classification? (talkcontribs)

Thank you very much for your reply!Category added in content,such as[[Category:Category name]]。 (talkcontribs)

I try to add a content category. Found that the same can not be added, it may be because 1.31 is not perfect reason。 (talkcontribs)

Thank you very much for your reply!Category added in content,such as[[Category:Category name]]。

Reply to "TCM"

Error 500 when a new, non-default skin is added to Localsettings.php

Newman2 (talkcontribs)

I got an error 500 after adding new skins to my LocalSettings.php. This has only occurred with additional skins that are NOT one of four default skins (Cologne Blue, Modern, MonoBook, Vector), and I appeared to have used the correct skin addition method for my current MediaWiki version. I made this wiki with Webhostface, and it runs on a currently supported version. However, I had no problems with adding user rights or enabling extensions.

I have not found a solution to fix this error, and I need some help fixing the error 500 on my wiki. Is there any way to fix this strange error and enable the skins without getting any more errors? Thank you.

2001:16B8:1022:4F00:D9C7:A745:8FE2:7F2B (talkcontribs)

It depends... In order to help you further, please answer the following questions:

  • Which skin did you try to add?
  • Which version of MediaWiki are you using?
  • How exactly does the line look like, which you added to LocalSettings.php?
Newman2 (talkcontribs)

-I was adding two skins, one of them being Monaco and another (being a skin I created) called Candy.

-I am using MediaWiki 1.30

-The line looks exactly like this (Candy is the skin that I added):

# Enabled skins.

# The following skins were automatically enabled:

wfLoadSkin( 'Candy' );

wfLoadSkin( 'CologneBlue' );

wfLoadSkin( 'Modern' );

wfLoadSkin( 'MonoBook' );

wfLoadSkin( 'Vector' );

Ciencia Al Poder (talkcontribs)

A 500 error message is not helpful at all. You'll need to look at server error logs to see a meaningful error message. See blank page

This post was hidden by (history)
Newman2 (talkcontribs)

By the way, I could not find enough information on the error 500.

2001:16B8:10A0:DB00:198F:24E4:C3ED:88E5 (talkcontribs)

On which skin did you base the Candy skin? Is it basically a copy of the Vector skin, which you then modified? Or is it based on the Monaco skin?

> I could not find enough information on the error 500.

That is why Ciencia is asking for more information. This information should be in the error log of the webserver.

After looking at the Monaco skin,

this skin does not support the line with wfLoadSkin(), because it is still using the old skin architecture. The Monaco skin has to be included using a line with require_once "$IP/skins/monaco/monaco.php";.

Does the error happen for both skins, Candy and Monaco?

Apart from that, the last changes to the Monaco skin have been done four years ago. Maybe the skin is no longer working with current versions of MediaWiki.

Newman2 (talkcontribs)

Candy is a copy of the MonoBook skin. And yes, the error happens for both Candy and Monaco.

2001:16B8:10AE:AE00:88E9:486B:2ED1:A316 (talkcontribs)

More information about your server error will be in the error log of the server.

Without more information, we will not be able to help you.

Newman2 (talkcontribs)

Okay. How do I debug the error then?

Newman2 (talkcontribs)

I also get an error 500 when attempting to debug and log the errors.

Ciencia Al Poder (talkcontribs)

The error log of the webserver should contain the information about the error.

Newman2 (talkcontribs)

How do you open the error log then? It wouldn't show up on my wiki.

Ciencia Al Poder (talkcontribs)
Newman2 (talkcontribs)

What do I need to type in to debug the error?

Newman2 (talkcontribs)

^^Look at the post above

Ciencia Al Poder (talkcontribs)

You already have the tools to debug the error. Nobody can tell you what do you need to type in to debug the error, because there are so many environments, operating systems, configurations, etc that is impossible to tell you the exact commands to type.

If you don't plan to take a bit of time to locate the error logs by yourself, interpret them to at least post here the relevant information, feel free to spend some money by hiring someone from Professional development and consulting.

Newman2 (talkcontribs)

The error looks like this:

PHP Fatal error:  Uncaught exception 'Exception' with message '/home/gjlxrtap/public_html/mw19/skins/Candy/skin.json does not exist!' in /home/gjlxrtap/public_html/mw19/includes/registration/ExtensionRegistry.php:99

Stack trace:

#0 /home/gjlxrtap/public_html/mw19/includes/GlobalFunctions.php(157): ExtensionRegistry->queue('/home/gjlxrtap/...')

#1 /home/gjlxrtap/public_html/mw19/LocalSettings.php(126): wfLoadSkin('Candy')

#2 /home/gjlxrtap/public_html/mw19/includes/WebStart.php(102): require_once('/home/gjlxrtap/...')

#3 /home/gjlxrtap/public_html/mw19/index.php(40): require('/home/gjlxrtap/...')

#4 {main}

  thrown in /home/gjlxrtap/public_html/mw19/includes/registration/ExtensionRegistry.php on line 99

Ciencia Al Poder (talkcontribs)

Look, a useful error message after all :)

Looks like Candy skin doesn't support extension registration. You should use require_once "$IP/skins/Candy/Candy.php"; or similar instead of wfLoadSkin

Newman2 (talkcontribs)

I get the same error, even with the require_once setup. Even if the message is useful, is there a way that I could fix this?

Newman2 (talkcontribs)

Now I've got this error:

PHP Fatal error:  Class 'MonoBookTemplate' not found in /home/gjlxrtap/public_html/mw19/skins/Modern/SkinModern.php on line 51

AhmadF.Cheema (talkcontribs)

Does your Skin:Modern version correspond to your MediaWiki core version? How did you download this skin?

Newman2 (talkcontribs)

I'm pretty sure my Modern skin version corresponds with the core version because the skin was built into the installation. Even if these messages are useful, I still need a way to get around this error and make my site run better.

This post was hidden by Newman2 (history)
This post was hidden by 2001:16B8:10A1:2100:3C43:EE16:CDE1:BE37 (history)
2001:16B8:10A1:2100:3C43:EE16:CDE1:BE37 (talkcontribs)

You are using MediaWiki 1.30, which is fine.

The skins, which are coming with MediaWiki 1.30, are Cologne Blue, Modern, MonoBook and Vector. These four skins all do have a skin.json file. Also the Modern skin should be working without the error "Class 'MonoBookTemplate' not found".

I think that something is wrong with the content of the four folders of these skins in the skins/ folder. I would delete these four folders and extract them again from the MediaWiki 1.30 tarball.

If the Candy skin is based on MonoBook from MediaWiki 1.30, it should be working.

Newman2 (talkcontribs)

Thanks for the info. But what software that is easy to download can debug any error including these ones?

2001:16B8:106D:2800:50C0:AF40:FC95:293B (talkcontribs)

You must enable error reporting - and obviously you have done that already as you already know the error message.

You should now replace the folders as detailed in my last post!

Newman2 (talkcontribs)

How do I extract those folders and enable error reporting? The fatal error occurs when I use the Modern skin, and the error 500 occurs when I add Candy to the site.

Now that I have enabled error reporting, now what do I do to debug this error? If the error reports and debugs are enabled, then how do I view and debug the errors if the error still occurs on my page? Where are the error displays located? I need some assistance on viewing the error reports.

星耀晨曦 (talkcontribs)
Newman2 (talkcontribs)

Yes, I saw the page on debugging. The problem is that I do not know whether or not HHVM has debugging on my wiki's database. Also, I do not know where MediaWiki Vagrant would be located. If they are on there, then would they be in the maintenance folder, the includes folder, or what location in MediaWiki? Thank you for reading this.

Ciencia Al Poder (talkcontribs)
Newman2 (talkcontribs)

I added the debug log file to my Localsettings.php, and it caused a 404 error. Does something else need to be send up, or does the $wgDBname have to be changed to the name of the database? There is something that needs to be done.

星耀晨曦 (talkcontribs)

The value of $wgDebugLogFile is the path you want to save. Name the file as you like, do not necessarily name the file by the example code.

> I added the debug log file to my Localsettings.php, and it caused a 404 error.

Very strange, it is likely that you misconfigured.

Newman2 (talkcontribs)

How would I have misconfigured? If so, then how do I fix the error that occurred with adding the debug log file?

星耀晨曦 (talkcontribs)

Normally, $wgDebugLogFile does not cause 404 error. May be due to other reasons. After removing $wgDebugLogFile, does 404 error still exist?

Newman2 (talkcontribs)

Yes, there was still a 404 error. And by the way, where are the debug log and debugging software located?

星耀晨曦 (talkcontribs)

This means that it is not caused by $wgDebugLogFile. You should think about what you did when you adding $wgDebugLogFile before. In this case, it is most likely that you have modified the config of your web server. You can check your web server for error log and access log.

Newman2 (talkcontribs)

Do you know how I get around that uncaught exception?

Ciencia Al Poder (talkcontribs)
  1. Find a relevant error message: a plain "uncaught exception", "unhandled exception", "internal error" is not useful. A "parse error" may indicate a typo in a PHP file. "internal error: unable to contact the database" can be useful.
  2. Go to and paste the detailed error message. Try to open several results and see if something may be applicable to you.
    • Don't try to apply fixes without first understand if the fix may be relevant to you. If you have doubts about some concepts, try to search it in to better understand it.
  3. If a cause described on those results seem relevant, try to apply a fix.
  4. If you come here for support, be sure to give us enough information to be able to help you
Newman2 (talkcontribs)

I fixed this error by adding a skin.json file. I fixed everything to make my Candy skin up and running. Now I get this error:

PHP Fatal error:  Class 'SkinCandy' not found in /home/gjlxrtap/public_html/mw19/includes/ServiceWiring.php on line 142

How do I fix this?

Ciencia Al Poder (talkcontribs)

Looks like you didn't fixed everything to make my Candy skin up and running

Newman2 (talkcontribs)

What needs to be added if the 'SkinCandy' class isn't found in the ServiceWiring?

Reply to "Error 500 when a new, non-default skin is added to Localsettings.php"

Removing "User" and "User Talk" Pages

Summary by Lewishackfath

I ended up just dropping all pages in the database where page_title did not have a corrisponding username in user

Select *

From page

Where (Select user_name from user) Not In page_title

AND (page_namspace = 2 or page_namespace = 3) (talkcontribs)


I need some assistance with deleting User and User Talk pages for all the users who are not registered.

Eg. I deleted about 50 users out of the database of our site and now would like to remove all of their User and User Talk Pages is there an easy way to do this?


Ciencia Al Poder (talkcontribs)

You can use a bot like pywikibot, or use the nukePage.php maintenance script. You can easily generate a list of pages to delete using a spreadsheet and some formulas. (talkcontribs)

I ended up just dropping all pages in the database where page_title did not have a corrisponding username in user

Chauncey edgar (talkcontribs)

I have a new install of mediawiki 1.30.0. It's running on a physical server (not a VM). My php version is 5.6.35. The database is mysql 5.6.40. All this is running on FreeBSD 11.1-RELEASE-p9 with apache 2.4.33.

Here's the issue: I got wikimedia installed and running. Login worked fine. Afterwards, I enabled SSL on the wiki site. Now, when a user logs in, he gets redirected to https://example.comindex.php/Main_Page - note the lack of a '/' between the domain and 'index.php...' - and of course it can't be found. If you manually put the '/' where it belongs, Main_Page loads properly. Before I enabled SSL, this worked correctly. Any ideas? Thanks.

PS - I'd rather not leave apache running until a couple of other unrelated things are resolved.

Ciencia Al Poder (talkcontribs)

If clicking on the logo doesn't redirect you to the faulty address, I'd say the problem may be in redirect rules from apache (if you have any)

Chauncey edgar (talkcontribs)

Clicking the logo gets me to the correct Main_page; but I have to click the Back button in my browser in order to see the logo. Immediately after login, I only see my browser's "not found" page.


Chauncey edgar (talkcontribs)

Another way to phrase the question: when a user enter his password and clicks 'Log in,' which file processes the login and generates the URL?

AhmadF.Cheema (talkcontribs)

Unless you have changed anything in MediaWiki core files, the issue shouldn't be from there.

Can you show your Apache redirect rules (if any), and the values for $wgScriptPath, $wgArticlePath from your LocalSettings.php file.

Chauncey edgar (talkcontribs)

I don't think I've changed those things, but I have $wgScriptPath = ""; $wgArticlePath does not appear in my LocalSettings.php.

Chauncey edgar (talkcontribs)

Update: the same problem appears when creating a new page. When you click the "Save" button, you get sent to the new page's URL, but the same '/' is missing (between the domain and 'index.php'). It also appears when saving an edit to an existing page, or searching on a page that exists. Searching on a nonexistent page works properly, i.e. offers you the opportunity to create it.

To address Ciencia Al Poder's other point: The only apache redirect is from HTTP to HTTPS; this works fine.

You can try it at There is a test user called Testa (how do they think of these things?) with the password Rossa.

Chauncey edgar (talkcontribs)

After triple-checking all the mediawiki files, I rechecked my apache config and did some experimenting. I found that if I have apache listen on port 80 only, my wiki works fine. It's only listening on port 443 that causes the "wrong URL" issue, whether using a redirect from port 80 to 443, or with a straight 443-only setup. Here are the relevant parts of httpd.conf as it stands now, which causes the "wrong URL" problem. The parts that are obviously bogus have "real" values in the actual httpd.conf.

Listen 443

<VirtualHost *:80>


       Redirect "/" ""


<VirtualHost *:443>



       SSLEngine on

       SSLCertificateFile "/path/to/certificate"

       SSLCertificateKeyFile "/path/to/private/key"

     # The following is a symlink to wherever mediawiki ended up:

       DocumentRoot /usr/local/www/apache24/data/sites/   


Behavior is unchanged whether I use a symlink or the real path to mediawiki in the DocumentRoot line. If it matters, I am not using mod_rewrite. I do have shell access to the server.

Ciencia Al Poder (talkcontribs)
Chauncey edgar (talkcontribs)

Adding the trailing '/' to the apache redirect fixed it. The $wgServer change doesn't seem to have any effect, although I left it in place on general principles.

Thank you so much!

Reply to "New login problem"

Math extension error: API error: internal_api_error_DBQueryError

GEP316 (talkcontribs)
Reply to "Math extension error: API error: internal_api_error_DBQueryError"
S.zhangx20 (talkcontribs)

I am new to MediaWiki and after countless googling, I still have this problem: I have the JavaScript file for jCarousel however I am not sure how to implement it so I can create a carousel on my mediawiki. All the directions say to edit MediaWiki:Common.js but I do not know what I am supposed to put in there. When I just put the jCarousel code in Common.js, the images appear next to each other instead of in a sliding motion. Does anyone know what I can do to fix this issue?

Reply to "jCarousel implementation" (talkcontribs)

MediaWiki 1.30.0 PHP 7.0.28 (apache2handler) MySQL

Windows 10

Main language is Russian.

I install Mediawiki (bundle from Bitnami) and add some pages. After a few days I see that in pages _last_ letter of all titles of categories replaced by � (UNICODE FEFF). All pages, including specialpages! When I switch to English interface specialpages is ok, but other, where russian words are bad. What is wrong?

Reply to "Invalid categories names"
Bishonen (talkcontribs)

Hi, would somebody like to protect my user talkpage and preferably globally lock the IP? It has been blocked as an open proxy on both and Commons. ~~~~.

Bishonen (talkcontribs)

Never mind. I guess this was the wrong page, but thank you all for your interest. The IP has been globally locked. Bishonen (talkcontribs)


I am getting line breaks after each use of a template, even though the template itself doesn't include any line breaks at all.

That is a problem for me because I sometimes want to use two templates in a row or even just have some text after a template.

Any ideas why this is happening or any solutions?

Reply to "Linebreak after template"
Johnywhy (talkcontribs)

I would like my extension to create a couple pages. It should only create the pages once, on first run.

  • Template
  • Special page
  • Form

I'm guessing this should happen in the file: MyExtension/extension.json Correct?

I assume it's only a matter of bundling the page-names and page-content in my extension, and passing that to a page-creation call.

But what is the page-creation call? Should i use generic php? Or is there a special page-creation function for mediaWiki?

Johnywhy (talkcontribs)
Reply to "Extension to Create Pages?"