Project:Support desk

Jump to navigation Jump to search

About this board

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

There are also other places where to ask :

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".
Previous page history was archived for backup purposes at Project:Support_desk/old on 2015-07-30.
Other languages: English  العربية čeština Esperanto français 日本語 中文
Xaris333 (talkcontribs) Portal

Hello. lv.wikipedia now has 100 000 articles and must move to that group of wikipedias. But I don't know where to add the request.

Reply to " Portal"
Shawarmaji (talkcontribs)

I forgot the password of my old account so I had to -create a new one. How can I transfer my edits and history to this new one?

Bawolff (talkcontribs)

you cant.

At the very least you would have to prove possesion of the old one. If you could have done that you could have just got your password reset.

(This answer assumes wikimedia website. If its your own wiki there may be a way)

This post was hidden by (history)
Reply to "Help"
Rexcall (talkcontribs)

I’m looking for a page that is no longer available. Can you help please?

Bawolff (talkcontribs)

not unless you tell us more details about the situation (like what page)

Reply to "Help"

Update from 1.30 to 1.34 failed with no explicit error

PiNgOo (talkcontribs)

I think i was close to the end of the update:

...Update 'PopulateChangeTagDef' already logged as completed. Use --force to run it again.


...index change_tag_rc_tag_id already set on change_tag table.

...have ipb_sitewide field in ipblocks table.

...ipblocks_restrictions table already exists.

...change_tag table does not contain ct_tag field.

...valid_tag doesn't exist.

...tag_summary doesn't exist.

...protected_titles table does not contain pt_reason field.

...ar_usertext_timestamp key doesn't exist.

...usertext_timestamp key doesn't exist.

...logging table does not contain log_user field.

...index un_user_ip already set on user_newtalk table.

...site_stats is populated...done.

Purging caches...

An error occurred:

Invalid module info for "0": expected array, got NULL

Is this possible to have a more explicit message ?


Reply to "Update from 1.30 to 1.34 failed with no explicit error"
PereslavlFoto (talkcontribs)

How can I open API access only to logged users? So to prevent anonymous users from access to API query? Thank you.

Reply to "API access"

Shared Host Mediawiki install v1.23.9: Editing Common:CSS has no effect.

KarlDrive (talkcontribs)

I have a wiki on a shared hosting server that was auto installed via cpanel, it's an older version of media wiki version 1.23.9. I wish I had known that to start off with, I assumed they were using the latest version, would have saved me some headaches when trying to install extensions.

In any case I've been making due because it does everything I want it to do for the most part and I'm not experience enough to try to manually update it.

The only thing I do wish to change are colors (would like a dark theme) however when I attempt to do so by editing the common:css and reloading the page with shift+f5 I see no effect. I took a look at my wiki in edge and also saw no effect.

I've been goggling this problem for the last two weeks I think I just lack some fundamental knowledge that's causing me to over look the root issue. I've tried copping tutorial changes onto the page and no effect, I've delete the vector.css and common.css pages and tried again and no effect.

I've reduced my css to the simplest of changes in order to eliminate variables. An example of what I've trying now is bellow.

body {background-color: #000000;}

I may just be entering entirely the wrong code, I've tried adding the !important tag after reading some things about css priority and no change.

The only other things I've changed about my wiki is that I've added tinyMCE and tried to add some 1.31 extensions before I realized that I was on 1.23.9. Maybe some of the poking around I did broke the common.css function? I'm not sure. I deleted all of the old

I also tried disabling tinyMCE and running the above code without it enabled in localsettings.php but still no effect.

Any how, this is a long shot but if any one has any insight that would be amazing. Thank you!


Bawolff (talkcontribs)

the page you need to edit to adjust css is named MediaWiki:Common.css not common:css

KarlDrive (talkcontribs)

Yeah that worked *sucks air through teeth and sighs* god damn it, I knew it was some thing obvious. Thank you so much man!

Help setting up ShortURL with Nginx subdomain

Satknave (talkcontribs)

Hi All,

Could someone help me please? I'm tearing my hair out trying to get this working!

So I have the nginx letsencrypt docker container from, set up to serve a number of applications from different subdomains. This all works perfectly.

I have recently added a mediawiki container, this also works absolutely fine.

I'm now trying to shorten the url, using the tool at - trying to integrate the nginx config it gives me with my existing subdomains setup, and I just can't get it to work. It displays a basic 'File not found' page.

Here is what I have so far:

It includes an example of an existing subdomain that does work, my wiki subdomain that doesn't work, and the supporting include files.

Please let me know if any more information is needed - I'm grateful for any help at all.

Ciencia Al Poder (talkcontribs)

You have $wgArticlePath = "/r/$1"; but I can't find anywhere in your nginx config a translation between /r and your actual MediaWiki installation path.

You may want to check out Manual:Short URL/Nginx for a working example.

Reply to "Help setting up ShortURL with Nginx subdomain"
RogerWindsor (talkcontribs)

How do I create a ged file for a selected list of entries?

Ciencia Al Poder (talkcontribs)

Can you elaborate? What is a ged file? What is the purpose?

Reply to "partial upload"

Problems with composer in a new (clean) install of MW 1.34 (or 1.33)

Mgreis (talkcontribs)

I'm looking for some help with Composer on a new (clean) install of Mediawiki and SMW.

As background, I've been using SMW for 5+ years. Like many - I suspect - my use of Composer is pretty much limited to what's needed to install and maintain SMW. My installation is at MW 1.28 and SMW 3.0.1. There was a pretty significant problem with MW 1.30+, PHP 7 and Sphinx Search, so I haven't been able to consider upgrading in some time. At this point, the challenges of going from MW 1.28 -> 1.34 and PHP 5.6 to PHP 7.2 have made upgrading my current wiki a dubious proposition.

Instead, I am creating a new MW 1.34 wiki on a new server, installing my extensions and planning to export my pages from the current wiki and import them into the new wiki. That's the plan, anyway....

When I install MW 1.34 (on a cPanel-based server, so cPanel does the installation), there is no composer.json file in the root directory of the wiki. I can't put SMW in a composer.local.json file and have it recognized.

I can create a minimal composer.json with one or two extensions. However, when the update script is later run and I'm prompted to run composer to create a lock file, a whole bunch of libraries required by MW are removed. It took me the better part of a day to realize what was happening (since the first symptom was a HTTP 500 error). My research uncovered some of the syntax required in composer.json to look for the composer.local.json file and to look for other composer.json files in the MW directory structure, but it's not clear what I need to have in composer.json to ensure that everything MW needs to run is accounted for along with SMW.

I looked back at my current MW 1.28 implementation, and the composer.json file has a lot of statements that were clearly provided by MW, along with my additions for SMW. Somewhere between my first implementation and this, that seems to have changed.

I've been trying to forensically recreate a composer.json that would at least not blow away my MW but that is proving difficult and doesn't make a lot of sense to me.  Why should I re-create a file that MW absolutely must have to operate once composer is used? I may be missing something, but I'm at a loss to understand what.

Any help would be appreciated!

Bawolff (talkcontribs)

honestly,my main advice would be to not use cpanel to install mediawiki but use the official tarball.

Mgreis (talkcontribs)

That's the next step I'm trying.

But can you or anyone tell me, am I correct that there should be a composer.json in the base directory after I've unzipped and installed it? That's the rub. If I can use composer to install SMW and my other extensions without destroying the installation, I should be good to go.

And if not, how do I get/create a composer.json to install extensions without wrecking the installation?

Thanks, @Bawolff

Bawolff (talkcontribs)

afaik the tarball should have a composer.json. mw core dependencies are preinstalled but its there just in case. I think. I havent looked at the tarball recently.

The whole installing extensions via composer isnt really officially reccomended but the smw people seem very insistent on it :S

Mgreis (talkcontribs)

Oh, dear. I don't want to get into the middle of one of those conversations. To your first point, the core dependencies are pre-installed. The problem is that the creation of a minimal composer.json file for one or more of these extensions is eventually followed by having to run either a composer update or a maintenance/update.php script. That results in the removal of those pre-installed, required libraries because they are not referenced in the minimal composer.json. Removing the libraries results in a non-functional wiki and a reinstall.

That, in a nutshell, is my problem. I'm having this conversation in parallel now on the semediawiki-user mailing and hoping that one of these sources helps me find a way out of this mess.

Reply to "Problems with composer in a new (clean) install of MW 1.34 (or 1.33)"

Language of 'contents' in ToC changes randomly on its own

Star Warden (talkcontribs)

Hey. We have the following issue on our wiki where the word 'Contents' in the table of contents translates itself automatically and randomly to a random language. Here are some examples:

What could be the cause behind this? It doesn't matter if I am logged in or not, nor the language chosen for the wiki's interface.

Later Edit: It seems 'Contents' changes back and forth randomly, so the above links might not reproduce the error, but the screenshot is an example.

Bawolff (talkcontribs)

generally this sounds like language parser cache pollution. It can be caused if an extension is using the wrong language object (e.g. not the one for the current page)

That said, i havent looked in detail

Star Warden (talkcontribs)

Thanks for the reply. So, how can I tell which extension is doing this and how to fix said pollution?

Reply to "Language of 'contents' in ToC changes randomly on its own"