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.

Error on Echo after installation

WikiGamee (talkcontribs)

Hey there,

I recently installed echo extension on my wiki and I get error like this:

[XtnxGA5HlhkDk-tPralCPwAAABI] /wiki/Main_Page MWException from line 588 of /home/vol5_4/ LocalisationCache::readJSONFile: Invalid JSON file: /home/vol5_4/


#0 /home/vol5_4/ LocalisationCache->readJSONFile(string)

#1 /home/vol5_4/ LocalisationCache->recache(string)

#2 /home/vol5_4/ LocalisationCache->initLanguage(string)

#3 /home/vol5_4/ LocalisationCache->loadItem(string, string)

#4 /home/vol5_4/ LocalisationCache->getItem(string, string)

#5 /home/vol5_4/ Language::getFallbacksFor(string)

#6 /home/vol5_4/ Language::newFromCode(string)

#7 /home/vol5_4/ Language::factory(string)

#8 /home/vol5_4/ Wikimedia\Services\ServiceContainer->{closure}(MediaWiki\MediaWikiServices)

#9 /home/vol5_4/ Wikimedia\Services\ServiceContainer->createService(string)

#10 /home/vol5_4/ Wikimedia\Services\ServiceContainer->getService(string)

#11 /home/vol5_4/ MediaWiki\MediaWikiServices->getContentLanguage()

#12 /home/vol5_4/ require_once(string)

#13 /home/vol5_4/ require(string)

#14 {main}

I follow all the instructions provided for avoid this error but, nothing happens. This is very important extension for me please help. I set my wiki to Hindi language.


Ciencia Al Poder (talkcontribs)

Looks like the /home/vol5_4/ file is corrupted. Try to download the extension again

WikiGamee (talkcontribs)

@Ciencia Al Poder: Thanks for reply. but, when I reinstall echo after download. I see "HTTP 500 error - unable to handle this request".

Reply to "Error on Echo after installation"

I cannot upload pics/files on my mediawiki.

Thepainking (talkcontribs)

I've been trying to upload a picture on my mediawiki by using the standard code as shown "[[File:........|.......|....]]". However, it always comes up as a broken link even when i add the picture from wiki commons. It does not give me an option to upload a file anywhere, and the option is absent on the left panel as well. I know i have an older version of mediawiki because the newer version was not compatible with my host server. How can I solve this problem? Is there a way to upload files (especially batch files and images) with the "upload" link? I need assistance ASAP.

Ciencia Al Poder (talkcontribs)
Reply to "I cannot upload pics/files on my mediawiki."

MediaWiki is a spam target unless it is set up properly.

B d m p (talkcontribs)

I made a new site and it immediately got taken over by spam. It was quite a hassle to delete all the spam and all the users. Not to mention that it was very unclear how to do this.

I am wondering why the captcha is not enabled by default. It seems to me that the by default the OpenID extension, mass delete extension and the BlockandNuke extension should be enabled.

Finding, installing, figuring out how to use them tool several days of work.

Why is the default version of Media Wiki so vulnerable to spam? How can we make it so users who are not that savvy do not get completely overrun?

Thank you.

Glaisher (talkcontribs)

Spammers try to spam anywhere they can find on the Internet. It's not only Mediawiki wikis that are vulnerable to spam. They spam blogs, forums, wikis, guestbooks, email addresses, mailing lists and any other web forms which they find. See Manual:Combating spam for details about how to deal with spam.

B d m p (talkcontribs)

Yes, this is true. That is why spam combating measure should be enabled by default.

Understanding and effectively combating spam with the information on Manual:Combating spam is a very difficult task. I have been trying for days to make my site function properly by using the information on that page, and I am getting no where. I have installed almost all the extensions on that page.

I was able to delete all the spam pages, but I have thousands of spam bot accounts I can't delete (BlockandNuke extension is not working). Also, I enabled OpenID to stop spam bot account creation because the extension that enables the captcha doesn't actually stop the bots, but if I disable the non-OpenID accounts, then users can't make user names when creating an account with OpenID. So, now I have a catch-22, and if I enable account creation, I get spam bots. If I disable it, real uses can't make accounts with OpenID.

This is a huge mess that could have been prevented if strict spam prevention measures were enabled by default. (talkcontribs)


So what would help would be having the information on how to set up a wiki in such a way that it is secure (spamwise) more reachable.

It would help to adjust the content of the original main page (this standard welcome text) to something, which also includes a link to Manual:Combating spam.

B d m p (talkcontribs)

That would be a step in the right direction, but I think it should have spam filters on by default or be in lock down mode with an explanation, so admins can configure it before they get attacked by spam. (talkcontribs)

As for the spam filters, there are extensions, which are coming with MediaWiki by default and which you can configure as you like (SpamBlacklist, TitleBlacklist, ConfirmEdit or so). All you have to do is to configure them. It does not really make sense to activate them preconfiguredly in some way as then spammers would just adapt to that one preconfiguration, which would make it useless.

When you set up MediaWiki there is an option to make it an "open wiki", "closed wiki" and so on. These texts tell something about who can edit the wiki in each case. However, I do not know the exact texts right now. Maybe a recommendation at that place would make sense.

Atcovi (talkcontribs)

Note: At Meta Wikimedia, their is a bot that automatically blocks users for specific spam userpage. You may check that out, or you can talk to User:Jasper Deng, who created that bot at Meta.

This post was posted by Atcovi, but signed as Goldenburg111. (talkcontribs)

Setting p a bot needs a rather good understanding of the MediaWiki internals, maybe a PC with some scripting language and other funky stuff. This is by no means something, that a beginner should be advised to try; it won't work, he will fail, demotivation and so on. I would start configuring the extensions, which come with the release tarball.

PiRSquared17 (talkcontribs)

That's just an abusefilter. (talkcontribs)

...which can be used with Extension:AbuseFilter. However, that is advanced - compared to just using the extensions provided with the tarball. The easiest solution is deactivating registration and making registration compulsory for editing. That is two lines in LocalSettings.php - and the installer even offers you to set them with a single click (I think the option was called "closed wiki").

MarkAHershberger (talkcontribs)

Right. And maybe that should be the default to get people to be more aware of what they need to do if they're going to set up a wiki.

LiturgicaNotata (talkcontribs)

I've had the same problem, and I found it also very difficult to work my way through the CombatingSpam-page. But I'm glad to say that my wiki is spamfree since last october! I've installed some extensions I don't use or didn't set up properly, but I think the two extensions that did the trick were ConfirmEdit with QuestyCaptcha and SimpleAntiSpam. I have to say though that my wiki is very specialised and in German, so I could come up with some really specialised questions in German. And I see this can't be the solution for every kind of wiki: A non-specialised wiki like, let's say, wikipedia can't come up with that kind of specialised questions.

Ciencia Al Poder (talkcontribs)
Lwangaman (talkcontribs)

I am trying to create a wiki, and in order to avoid spam (as happened in a past attempt a few years ago, I had tried creating a wiki which was overrun by spambots and I eventually gave up), this time I created a closed wiki where only registered users who are approved can post content. Well guess what: I was overrun by spam again. If not even a closed wiki is protected from spam then I say, there must be some weaknesses in the wiki software that spambots can take advantage of?

Ciencia Al Poder (talkcontribs)

Sometimes weakness are caused by sysadmins that install new MediaWiki versions but leave an old installation with public access on the internet at a different path

Reply to "MediaWiki is a spam target unless it is set up properly."

Create a gallery for picture - mode="slideshow" - thumb code HTTP 5x ?

Zer00CooL (talkcontribs)

Create a gallery for picture :

From :

Not work 100%

Look my example please.

Click the button for show all thumb :

< (left picture) button (right picture) >

Now, you can't see any thumb, not work ! If you click the link, it's ok.

If i copy the link from the thumb, it's not ok, i have this :

It's a code HTTP 5x ?

Or, a bug ?

There is my Vhosts :

Ciencia Al Poder (talkcontribs)

This is task T181987. As a workaround, set $wgShellLocale = "C.UTF-8";

Zer00CooL (talkcontribs)

Yes ! You have just ! I use the wrong option !

Nice ! Work Fine now !

## If you use ImageMagick (or any other shell command) on a

## Linux server, this will need to be set to the name of an

## available UTF-8 locale

# Valeur par défaut à l'installation de mediawiki 1.31.0 $wgShellLocale = "C.UTF-8";

# J'avais tenté de mettre fr_FR.UTF-8 mais c'était une très mauvaise idée !

# Les miniatures ne s'affichaient plus ! C.UTF-8 est la bonne valeur !

# Source :

$wgShellLocale = "C.UTF-8";

How to properly Install MediaWiki on Fedora 32 (Or Fedora 3x)

Agompel (talkcontribs)

Good day,

I have tried to install Wikimedia on Fedora 32 (and 31 too) with MariaDB. , always to stumble on something not working. (close to the end).

Many posted here and there the same difficulties. Fedora/RedHat is a very popular Linux distro, usually very good.

The issue is probably some level of permissions.

The ideal (most simple) way should be # dnf install mediawiki

Or a similar dnf command using "group install" etc...

Could you look at this and at least document a valid manual install, then an properly working package install? (using Fedora package installer dnf).

Thanks for the attention.

Andre Gompel

Malyacko (talkcontribs)

@Agompel Hi, it is impossible to improve something if there is zero information about what is not working. Hence statements like "many posted here" make no sense (yet)... If there are problems then please explain what the problems are.

Also, for packages for random Linux distributions, please talk to the packagers of those Linux distributions. Thanks! (talkcontribs)
  1. install media-wiki, httpd and mariadb

" sudo dnf install -y httpd mariadb-server php php-pear php-xml php-intl php-pecl-zendopcache php-gd php-mbstring ImageMagick-perl media-wiki "

2. start httpd and mariadb services

"sudo systemctl enable --now httpd"

"sudo systemctl enable --noew mariadb"

3. copy basic wiki template to /var/www/html folder ( fix the permissions and selinux if needed )

"cp -a /var/www/wiki/ /var/www/html" (talkcontribs)

after that access in your browser:


here u can see if your apache server is running


your wikimedia basic setup

Malyacko (talkcontribs)
Reply to "How to properly Install MediaWiki on Fedora 32 (Or Fedora 3x)"

How can I delete all discussion pages?

2A02:908:3111:7DA0:5545:F124:EDE3:F6B1 (talkcontribs)

Want to delete all discussion pages on my wiki. All other pages should stay.

AhmadF.Cheema (talkcontribs)
Ciencia Al Poder (talkcontribs)
Reply to "How can I delete all discussion pages?"

How to edit multiple articles by the same way?

2A02:908:3111:7DA0:5412:338A:BD55:14F9 (talkcontribs)


I have to wiki sites. Let's say wiki#1 and wiki#2.

I have prepared many articles at wiki#1, and now I want to export them to wiki#2.

So far I understand what to do.

But now I want not to delete the articles from wiki#1, but to leave external redirects to the same articles on wiki#2.

How can I do that?

I have hundreds of articles, I don't like to edit every single manually.

Bawolff (talkcontribs)
2A02:908:3111:7DA0:F5BA:9466:A806:79DC (talkcontribs)

Isn't there any command like

#redirect [wiki#2 $NameOfArticle]


Bawolff (talkcontribs)
2A02:908:3111:7DA0:580:5B55:1EF8:481E (talkcontribs)

I had another idea.

Is it possible to take many articles and edit them with the same text?

So that the written text will be saved as the content or many chosen articles at the same time.

Thanks either way.

Ciencia Al Poder (talkcontribs)

If you have command line access to the wiki, it may be easier to use the edit.php maintenance script

Bawolff (talkcontribs)
2A02:908:3111:7DA0:CCF9:36B7:CFCE:F7AD (talkcontribs)

Ha ha thanks Bawolff. Yes it's kind of a way.

Thank you guys anyway, I will look for a way.

How to translate this Cite template to Hebrew?

29 (talkcontribs)

I have an RTL (Hebrew) 1.34.0 principally all-core MediaWiki website with Cite extension and ParserFunctions extension loaded in LocalSettings.php.

In this website I have Template:Cite with the following content, which I use to create English footnotes in English-only pages:

| {{#tag:ref|{{{content|}}}|name={{{refname}}}}}
| {{#tag:ref|{{{content|}}}}}

Credit for @Jonathan3 for developing this template.

Call input examples:

1) Cite with parameter calls WITHOUT English naming (by name attribute)

First check{{Cite|content=First check}}
Second check{{Cite|content=Second check}}
Third check{{Cite|content=Third check}}

<references />

2) Cite with parameter calls WITH English naming (by name attribute)

First check{{Cite|content=First check}}
Second check{{Cite|content=Second check|refname=First_name}}
Third check {{Cite|refname=First_name}}

<references />

Call output examples (appear fine in dir="rtl" modes):

1) Cite with parameter calls WITHOUT English naming

First check[1] Second check[2] Third check[3]

  1. ^ First check
  2. ^ Second check
  3. ^ Third check

2) Cite with parameter calls WITH English naming

First check Second check Third check

  1. ^ First check
  2. ^ לקפוץ מעלה אל:2.0 2.1 Second check


Note: Brackets appear flipped (][) in dir="ltr" modes


My problem

I want to use this template in an Hebrew project, that is, in an RTL && Right-align writing mode but if I write for example:


and my footnote happens to start with English after the first pipeline and also including Hebrew (say, as with links) than everything becomes jumbled up:


The first example shows non messy content and the second shows messy content (תוכן שהתבלגן); in the second example the "Content" part is situated wrongly.

My question

The only solution which comes to my mind to solve this problem is having an Hebrew call to the template such as


Which means Content=content which didn't go messy.

If there were ready to use RTL&&RA Hebrew (or any other RTL) <ref> tags than I wouldn't need such a Hebrew call but HTML is all English so I do need a template and an all-Hebrew one.

Hence I ask,

How to translate my template from English to Hebrew in a successful manner?

How to translate this Cite template to Hebrew? (talkcontribs)

I give you my word of honor that this is generally and most likely the last time I will tag your profiles here with this RTL&&RA issue:

@Amire80 (talkcontribs)

I give you my word of honor that this is generally and most likely the last time I will tag your profiles here with this RTL&&RA issue:

@קיפודנחש (talkcontribs)

I give you my word of honor that this is generally and most likely the last time I will tag your profiles here with this RTL&&RA issue


Bawolff (talkcontribs)

So this is a bit harder. Some possible solutions:

  • If you switch the page language via Special:PageLanguage (After enabling $wgUseDBPageLanguage), the edit box will be the directionality of the page language. (You can see an example of this by comparing the edit box for the page named MediaWiki:Translateinterface/en and MediaWiki:Translateinterface/he )
  • The following js might help: $( function() {box = document.getElementById( 'wpTextbox1' ); if (box) box.dir = 'auto';});
  • If you don't want to specify an overall override, or are authoring a mix of directionality in one page, you can directly insert RLM (right-to-left mark), LRM (Left-to-right mark) or FSI (first-strong-isolate) characters (You would have to directly insert the character, not the entity, for it to affect the edit box. However it may also have an effect on the output, in most cases it should probably be fine, and the isolate characters are probably less likely to have a negative effect than the other characters). This is kind of hard to do, and how to do it varries by operating system. In windows, you can insert an LRM using the key combination Alt+0253. This is what it looks like if you put an LRM character before and after the hebrew part:
{{Cite|content=‎תוכן_שהתבלגן‎}} (talkcontribs)


Brought me a 404 in my own website.


Running the JS

$( function() {box = document.getElementById( 'wpTextbox1' ); if (box) box.dir = 'auto';});

in an edit page juxtaposed all English content left and all Hebrew content right; so I still have a problem calling {{Cite|Content=CONTENT}} in the middle of two Hebrew structures, if the content of the footnote is not solely in English.


About using either RLM/LRM; I don't know these

About FSI; If I understand correctly it is still experimental


Is there a way to tell the backend, for example

Where "הערה" put "Cite" AND where "שם" put "name"?

This way I write everything in Hebrew but the output will always be based on a preexisting English translation of the output, just one step before parsing and rendering everything else?

Bawolff (talkcontribs)

you can use redirects for alternate template names. Template parameters can have multiple names in a fallback pattern. (talkcontribs)

@Bawolff I have read in that page and what I understood is that a redirect does with transferring a human or a bot from one webpage to another.

Perhaps you meant something like that the page


Should contain:

#REDIRECT [[Template:Cite]]

About fallback patterns for template parameters: I want to read about it, but I don't know where exactly,

Did you mean to: Help:Templates#Exceptions to the order of evaluation

I mostly misunderstand how is it essentially different than redirections and how does a template gets directed to do the "fallback",


Bawolff (talkcontribs)

you can do {{{parametername|{{{alternativeparamname}}}}}} (talkcontribs)


I want to better understand that code

I went to Help:Templates and searched:


I didn't match any data.

Please tell us the name of the concept or refer to a man page.

At least a bit more detailing would be helpful.

Bawolff (talkcontribs) (talkcontribs)


parameter תוכן has the default value of content


parameter שם has the default value of refname (a name attribute)

? (talkcontribs)

@Jonathan3 now after the English phase was dealt with in depth (and success), you might have an approach to recommend about translating the template to Hebrew.

Jonathan3 (talkcontribs)

I don't have any experience of foreign languages but will have a look next week. I'd start by changing "refname" to "name", just to simplify things in finding a translation. I just kept it as "refname" as it had been suggested by someone else. They say a camel is a horse designed by a committee. Apologies if it turns out that the distinction is necessary! (talkcontribs)

I agree that in the content of parameter names, name is better than refname (as long as there is no conflict between name as a mere parameter name and name as a special value representing HTML name attribute).

I preferred it all along without knowing if its a problem or not and seemingly it isn't (smile of happiness). (talkcontribs)


Okay, I have redirected תבנית:הערה to Template:Cite

Perhaps it would be redundant to say that English tests go fine

All Hebrew tests fail with the exact two errors:

  • שגיאת ציטוט: תג <ref> לא תקין;
  • להערות שוליים ללא שם חייב להיות תוכן

If you translate this to Hebrew you could understand that the parameters content and refname aren't applicable by through the תבנית:הערה TO Template:Cite redirect.


Because I got lost with Help:Templates#Exceptions to the order of evaluation

Please consider to give an example to how one should implement it in the (confusing and much-background-knowledge requiring context of LTR-to-RTL default parameters). (talkcontribs)

by through = through

(confusing and much-background-knowledge requiring


(confusing and much-background-knowledge requiring)

Bawolff (talkcontribs) (talkcontribs)


My template is the same one Jonathan3 created:

| {{#tag:ref|{{{content|}}}|name={{{refname}}}}}
| {{#tag:ref|{{{content|}}}}}

Currently I also have a redirect from תבנית:הערה to it (Template:Cite)

Although this template (Template:Cite) is in English, I want to call it in Hebrew, as with, say;


בדיקה שלישית{{הערה|שם=שם_ראשון}}

But; I don't know how I might be able be able to do that. (talkcontribs)

@Bawolff do you know a way to do that or would you say it's even possible with the current release?

If it's not possible with the current release than maybe I should indeed migrate, somehow, from MediaWiki to TikiWiki or some other MediaWiki derivative.

Bawolff (talkcontribs)

As i already said above, you can use default values of parameters to have template parameters that have more than one name and you can have redirects to make the template have more than one name. (talkcontribs)


You said:

"you can use default values of parameters to have template parameters that have more than one name"

So, I tried to read Help:Templates#Default_values on which you said:

"It is a parameter that has as its default value a different parameter"

But I said I got lost with it and you said:

"I dont see anything in that section relavent to what you are doing"

So is it relevant or irrelevant? (talkcontribs)

Use default values of parameters

To have template parameters

That have more than one name



Should the default value of the parameter content be תוכן and should the default value of the parameter refname be שם?

Please share with us if I misunderstood. (talkcontribs) (talkcontribs)

@Jonathan3 I start to think that translating this template into Hebrew is impossible. (talkcontribs)

@Jonathan3 I take back what I wrote one post above (which was anyway humorous);

I think I found a way to translate that template;

This version passed my tests below:

    | {{#תגית:ref|{{{תוכן|}}}|name={{{שם}}}}}
    | {{#תגית:ref|{{{תוכן|}}}}}
  • Instead if I wrote תנאי
  • Instead tag I wrote תגית
  • Instead refname I wrote שם
  • Instead content I wrote תוכן

Tests passed successfully

1) Cite with parameter calls WITHOUT English naming (by name attribute)

* בדיקה ראשונה{{הערה|תוכן=בדיקה ראשונה}}
* בדיקה שנייה{{הערה|תוכן=בדיקה שנייה}}
* בדיקה שלישית{{הערה|תוכן=בדיקה שלישית}}
* בדיקה רביעית{{הערה|תוכן=בדיקה רביעית}}


  • [1]בדיקה ראשונה
  • [2]בדיקה שנייה
  • [3]בדיקה שלישית
  • [4]בדיקה רביעית
  1. ^ בדיקה ראשונה
  2. ^ בדיקה שנייה
  3. ^ בדיקה שלישית
  4. ^ בדיקה רביעית

2) Cite with parameter calls WITH English naming (by name attribute)

* בדיקה ראשונה{{הערה|תוכן=בדיקה ראשונה}}
* בדיקה שנייה{{הערה|תוכן=בדיקה שנייה|שם=שם_ראשון}}
* בדיקה שלישית{{הערה|שם=שם_ראשון}}


  • [1]בדיקה ראשונה
  • [2]בדיקה שנייה
  • [2]בדיקה שלישית
  1. בדיקה ראשונה
  2. ^ לקפוץ מעלה אל:2.0 2.1 בדיקה שנייה


Note 1)

Instead ref it was written תגית but in version 1.35.0 or 1.36.0 one could write תג instead תגית and the credit for that goes to @Amire80 for commiting the source code change.

תג is a "male" manner for tag in Hebrew instead the longer "female" manner of תגית.

Note 2)

I haven't tested the template with regards to links. I should do that ASAP and publish my progress here.

Note 3)

Any constructive comment about my translation of Jonathan3's template is most welcome.

Jonathan3 (talkcontribs)

If it works it works! Well done.

It looks like the references/footnotes part is a mixture of LTR and RTL (e.g. the number 1 and its full stop are LTR on the left, then the text itself is RTL). Is that a problem? (talkcontribs)

@Jonathan3 thanks !

Actually in practice (in the Hebrew site) everything is RTL for me but here in the output appears aligned-left for some reason but I cannot edit to try HTMLize the output chapters to give them dir="rtl" and style="text-align: right" or something similar I guess. (talkcontribs)
Reply to "How to translate this Cite template to Hebrew?"

How to use Cite extension in RTL projects?

46 (talkcontribs)

I want to implement a footnote creation mechanism similar to the one implemented in Hebrew Wikipedia in my own MediaWiki 1.34.0 based website (which is a personal and non communal website).


According to my understanding, the footnote creation mechanism implemented in Hebrew Wikipedia includes the usage of at least five very complicated templates which require installing an external extension Scribunto:

template:footnote | תבנית:הערה

template:margin footnotes | תבנית:הערות שוליים

template:documentation | תבנית:תיעוד

template:parameter management | תבנית:ניהול פרמטרים

template:parameter management/content | תבנית:ניהול פרמטרים/תוכן

Contemplating these templates:

Even if I totally strip out all <templatedata> and [[category:]] ([[קטגוריה:]]) mambo jambo, I am still left with five templates which I personally find too many, too complex, too dense and too confusing and too hard to maintain;

How to use Cite extension in RTL projects (most desirably without all these complexity and without installing Scribunto)?

Bawolff (talkcontribs)