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, Q&A 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".

Where do I change the time a user can be inactive before having to login again?

Tohbbe (talkcontribs)

Where do I change the time a user can be inactive before having to login again?

TheDJ (talkcontribs)

Please see Manual:$wgExtendedLoginCookieExpiration and Manual:$wgCookieExpiration

Reply to "Where do I change the time a user can be inactive before having to login again?"
Waanders (talkcontribs)

One of our templates seems corrupted. We can't edit the page, even not show (yes, it exists) and so on. All this results in a time-out. Now we try to import a back-up version but also Special:Import gives a time-out.

How do I fix this?

Reply to "How to fix a corrupted page?"

Is there any way to block or selectively kill geo info from pictures I uploaded?

Summary last edited by RedKnight7 00:40, 21 November 2017 9 hours ago

If it helps any other newbie. After experimentation I found Bawolff's reply to more precisely mean:

SELECT img_name from image where img_metadata like '%GPSL%';

Where "image" should be the name of your mediawiki dataset. For me, it was named mw_image

Using the SiteGround SQL tools I have, my particular MediaWiki files were located in a \MediaWiki directory off my public site root directory. They had a somewhat arbitrary name assigned when first made (like [domain_name]_mw[number]\mw_image

Hope this helps.

Thanks again, Bawolff! Now I see other pictures with geocoords.

If anyone can ever make a utility to block geocoords? That sure is a lot simpler than never messing up, or having to delete the entire page and start over, if you do.

RedKnight7 (talkcontribs)

Hi everyone,

I uploaded a bunch of pictures to my personal mediawiki site, then realized I forgot to wipe geocoords from them (which can be clearly seen on their metadata pages). I'm just an amateur site builder, but this presents multiple problems:

1) Even if I edit the image and upload a new version with geo info wiped, doesn't the old version remain, with its geo info?

2) How can I be sure I haven't goofed and left a geocoord across the many pictures I've uploaded? Maybe dozens or hundreds; not sure how many were screen captures, and how many from my phone.

In short, I think I am looking for a tool that will wipe and/or block any and all geocoords on any of my pictures, passively and forever more.

Does anyone know of such a thing? Thanks so much if you can help!

P.S. I am using 1.27.1 of MediaWiki, from Sept. 2016 or so.

Bawolff (talkcontribs)

You need to upload a new version, and delete the old version (If you have revision deletion, you can just set the old version of the image content to be deleted and keep the rest of the history).

You can try to get a list of such photos by doing a query on the database like SELECT img_name from image where img_metadata like '%GPSL%';

p.s. Edit - As RedKnight7 noted above, if you're using $wgDBPrefix, then you need to add that to the image name.

Reply to "Is there any way to block or selectively kill geo info from pictures I uploaded?"

Cannot comment to my topic

Summary by MarkAHershberger

Next to the topic headline there are three small dots. After clicking them, you can go for "Reopen Topic" and after that you can again add comments to it.

SB26 (talkcontribs)

I asked a question, and got a reply but I do not understand it, I'm not able to comment on that topic.


Jörgi123 (talkcontribs)

Next to the topic headline there are three small dots. After clicking them, you can go for "Reopen Topic" and after that you can again add comments to it.

A have now reopened that topic for you - but you can also do that yourself!

Having trouble logging in

Summary by MarkAHershberger

See Special:PasswordReset and Help:Logging in. You must have an email address attached to the account for resetting the password. (talkcontribs)

Wiki tells me that my username already exists but "doesn't exist on this Wiki." How can I reset my password?

Tropicalkitty (talkcontribs)

See Special:PasswordReset and Help:Logging in. You must have an email address attached to the account for resetting the password.

Bug in "Als PDF herunterladen" = "Download as PDF"

Summary by MarkAHershberger

This is a bug that should be reported in Phabricator. (talkcontribs)

my Wiki -

in the table - Rolleneinteilung nach Staffeln - is a bug by using the PDF funktion

in the PDF table printout is no color marking from original wiki shown

sorry for this bad english text

german flyglider from gmx

MarkAHershberger (talkcontribs)

This is a bug that should be reported in Phabricator.

How to enable image HiDPI display support?

Zoglun (talkcontribs)

Keep receiving error message like:

2017/11/21 07:14:42 [error] 14879#14879: *79906883 open() "image/common/4/46/Fall_2017_Event_E-1_Map@2x.png" failed (2: No such file or directory), client: *****, server: ******, request: "GET /common/4/46/Fall_2017_Event_E-1_Map@2x.png HTTP/1.1", host: "********", referrer: "http://*************/File:Fall_2017_Event_E-1_Map.png"

Bawolff (talkcontribs)

What are you doing to trigger those sorts of requests? Fall_2017_Event_E-1_Map@2x.png is not the syntax MW uses for HiDPI.

Generally, HiDPI will work by itself (Its controlled by $wgResponsiveImages which is on by default)

Reply to "How to enable image HiDPI display support?"
Star Warden (talkcontribs)

Hi. When trying to access this page on the wiki (, I get this error: Fatal error: Call to a member function getLocalURL() on a non-object in /srv/dml-wiki/includes/skins/Skin.php on line 1051

I went to that line in that php and I found this: return $title->getLocalURL( $urlaction );

So far, it seems it's the only page acting up. Could anyone give me a solution, please? (talkcontribs)

You are using MediaWiki 1.27. I have tested this in your wiki and this is happening with Vector, but also with Monobook, but only on that one page. Other pages display correctly.

Your problem is that for some reason, $title is not a title object at that point. From reading the code I think that this part of the code only is used to create a link to a special page.

In your case, SpecialPage::getSafeTitleFor( $name ); does not return a title object.

A complete backtrace would be great.
Star Warden (talkcontribs)

All right. And how do I give a complete backtrace?

Ciencia Al Poder (talkcontribs)

Star Warden (talkcontribs)

Hey. We found the error without having to backtrace. It's the apostrophe in the title that was causing the issue. As you can see, all events that have the apostrophe return the same error:

Aside from effectively removing it from the title, is there any other better sign with which we could replace it and not resort to sticking the possessive to the word? (talkcontribs)

Although not recommended to be used, apostrophes are allowed in URLs and MediaWiki also can cope with them, e.g. en:Lady's Magazine.

An idea might be to check, why this is not working on your server and to fix the reason - or to use different page titles without apostrophe.

Star Warden (talkcontribs)

To be completely honest, I am not a programmer, I just try to follow the instructions given. With that in mind, how do I find why it's not working? And I've tried using other signs, like the prime or a different-looking comma, but both give the same error....

Ciencia Al Poder (talkcontribs)

Getting a backtrace would be helpful to see what's calling that method, possibly passing an invalid parameter. If that's hard, try disabling all extension and see if the problem still happens.

Star Warden (talkcontribs)

Hey. I didn't backtrace, but I disabled extensions, as you suggested me to, and I found that Extension:Contributors is the culprit. Why though?

Ciencia Al Poder (talkcontribs)

Extension talk:Contributors has other people complaining about that, but I don't see a bug about that on phabricator... Looks like nobody cares enough to report it so devs are aware of the bug.

Star Warden (talkcontribs)

I can open up a bug report, but I am not exactly sure how to formulate it to be as precise as possible. I mean, I could give the error that I am getting, but that points to folders on my wiki's server, so it would be different from what others reported.

AKlapper (WMF) (talkcontribs)

Star Warden (talkcontribs)

Yes, I am aware of HOW to report it, but I am not sure how to formulate the error itself so as to be as precise as possible.

Ciencia Al Poder (talkcontribs)

Just try it. If devs need further information they'll ask in the task.

Star Warden (talkcontribs)

Done ( Hope it's clear enough.

Stefahn (talkcontribs)

Ran into the same (unsolved) issue and added a comment to the bug report.

Bawolff (talkcontribs)

There should be a fix in master now. Try redownloading the extension (Make sure to select the master branch of the extension)

Reply to "getLocalURL error"

What approach to use for Active Directory login?

PSIDWiki (talkcontribs)

I have been going around in circles with trying to get this to work. I had installed 1.29.1 then I read that active directory works better with 1.26.3. Extension:LDAP Authentication

So I removed 1.29.1 and downloaded and setup 1.26.3. So I go to setup the ldap options and I see that I have to use AuthPlugin so I go to this site AuthPlugin where it says it is deprecated and for backwards compatibility up to version 1.27 and to use Manual:SessionManager and AuthManager.

What is the recommended approach to use where I can have users login with their active directory credentials and I can add them to a group to just be able to edit?

Thank you

MarkAHershberger (talkcontribs)

You're right that the situation is confusing right now.

The version for 1.29.x may work depending on your needs or not. Try it and then ask for help here if you run into problems.

If it fails and you need this immediately, go with 1.26.x and Extension:LDAP Authentication since that will most likely work.

Finally, we are working on a replacement for the LDAP authentication. You can follow our progress: LDAP hub.

PSIDWiki (talkcontribs)

Hi Mark,

Thank you for the reply. I'm trying to use 1.26.x since I have to have it completed by today.

I'm running this on

MediaWiki 1.26.3

IIS 8.5

php 7.0 (I think this needs to change since I'm using 1.26.3)

mySQL 5.5.57

Windows Server 2012 R2

Here is what I have in LocalSettings.php for connecting to Active Directory:

require_once( "$IP/extensions/LdapAuthentication/LdapAuthentication.php" );

$wgAuth = new LdapAuthenticationPlugin();

$wgLDAPDomainNames = array( "TMP" );

$wgLDAPServerNames = array( "TMP" => "" );

$wgLDAPSearchStrings = array( "TMP" => "TMP\\USER-NAME" );

$wgLDAPEncryptionType = array( "TMP" => "tls" );

$wgLDAPUseLocal = false;

$wgMinimalPasswordLength = 1;

$wgLDAPBaseDNs = array( "TMP" => "dc=tmp01,dc=ab,dc=cde,dc=fghi,dc=edu" );

$wgLDAPSearchAttributes = array( "TMP" => "sAMAccountName" );

$wgLDAPRetrievePrefs = array( "TMP" => "true" );

$wgLDAPPreferences = array('TMP' => array( 'email' => 'mail','realname' => 'displayname'));

$wgLDAPDebug = 3; //for debugging LDAP

$wgShowExceptionDetails = true; //for debugging MediaWiki

$wgDebugLogFile = "C:\inetpub\wwwroot\NewWiki\w\debug.log" ;

$wgDebugLogGroups["ldap"] = "C:\inetpub\wwwroot\NewWiki\w\debugldap.log" ;

$wgLDAPProxyAgent = array(

'TMP' => 'cn=TMP\userLDAP,dc=tmp01,dc=ab,dc=cde,dc=fghi,dc=edu',


$wgLDAPProxyAgentPassword = array(

'TMP' => 'tmpLDAPpassword',


I know that the ldap server has a certificate and it is not self signed but from a third party. Do I still need to use openssl and create a cert file? If so where do I put this file in a windows server 2012 computer? Should I use SSL?

All I want to do is have my users use their current login information to log into my MediaWiki setup and just allow them to edit. I need to give myself and another user top level control. Anyone else who uses the site will just be a user and just viewing the wiki.

Thank you again for your help. I look forward to hearing from you.l

MarkAHershberger (talkcontribs)

I've used SSL without a client certificate. Unless you are told you need one, you shouldn't have to create one. Yes, you should use SSL.

This comment was hidden by Jörgi123 (history)
Reply to "What approach to use for Active Directory login?"

Fatal exception of type Wikimedia\Rdbms\DBQueryError after update upto 1.29.2

Ektip (talkcontribs)

Update mediawiki from 1.21 to 1.29.2 using web-interface.

Now i have error - [05575cfedebae9daa0d54bb3] 2017-11-18 21:45:24: Fatal exception of type Wikimedia\Rdbms\DBQueryError

Please advice.

星耀晨曦 (talkcontribs)

You should open debug options for more detailed error messages

$wgShowExceptionDetails = true;
$wgShowDBErrorBacktrace = true;
$wgShowSQLErrors = true;
Ektip (talkcontribs)

Here is:

[2cf16b067a21c4921aa451b1] / Wikimedia\Rdbms\DBQueryError from line 1075 of /home/httpd/vhosts/ A database query error has occurred. Did you forget to run your application's database schema updater after upgrading? 
Query: SELECT lc_value FROM `l10n_cache` WHERE lc_lang = 'en' AND lc_key = 'deps' LIMIT 1 
Function: LCStoreDB::get
Error: 1146 Table 'a201591_wikiek.l10n_cache' doesn't exist (

#0 /home/httpd/vhosts/ Wikimedia\Rdbms\Database->reportQueryError(string, integer, string, string, boolean)
#1 /home/httpd/vhosts/ Wikimedia\Rdbms\Database->query(string, string)
#2 /home/httpd/vhosts/ Wikimedia\Rdbms\Database->select(string, string, array, string, array)
#3 /home/httpd/vhosts/ Wikimedia\Rdbms\Database->selectField(string, string, array, string)
#4 /home/httpd/vhosts/ LCStoreDB->get(string, string)
#5 /home/httpd/vhosts/ LocalisationCache->isExpired(string)
#6 /home/httpd/vhosts/ LocalisationCache->initLanguage(string)
#7 /home/httpd/vhosts/ LocalisationCache->loadSubitem(string, string, string)
#8 /home/httpd/vhosts/ LocalisationCache->getSubitem(string, string, string)
#9 /home/httpd/vhosts/ Language->getMessage(string)
#10 /home/httpd/vhosts/ MessageCache->getMessageForLang(Language, string, boolean, array)
#11 /home/httpd/vhosts/ MessageCache->getMessageFromFallbackChain(Language, string, boolean)
#12 /home/httpd/vhosts/ MessageCache->get(string, boolean, Language)
#13 /home/httpd/vhosts/ Message->fetchMessage()
#14 /home/httpd/vhosts/ Message->toString(string)
#15 /home/httpd/vhosts/ Message->text()
#16 /home/httpd/vhosts/ MalformedTitleException->__construct(string, string)
#17 /home/httpd/vhosts/ MediaWikiTitleCodec->splitTitleString(string, integer)
#18 /home/httpd/vhosts/ Title->secureAndSplit()
#19 /home/httpd/vhosts/ Title::newFromURL(NULL)
#20 /home/httpd/vhosts/ MediaWiki->parseTitle()
#21 /home/httpd/vhosts/ MediaWiki->getTitle()
#22 /home/httpd/vhosts/ MediaWiki->main()
#23 /home/httpd/vhosts/ MediaWiki->run()
#24 {main}
Ektip (talkcontribs)


AhmadF.Cheema (talkcontribs)

You will need to run Update.php.

2003:CC:ABE4:6400:19F2:D209:921:4DC9 (talkcontribs)

The database table l10n_cache is missing n your database. This is the problem.

According to Manual:Database_layout this table should already have been there, when you used MediaWiki 1.21. You might have to add this table manually by looking into the tables.sql file:

Bawolff (talkcontribs)

Update.php (or the web updater by going to ) will add the table for you, so there is no need to add it manually.

However, this table has been included since MediaWiki 1.16, so unless you are upgrading from pre-1.16, this means that random tables are disappearing from your db. That generally is very bad and you should figure out how that happened.

Jörgi123 (talkcontribs)

But isn't update.php using the different patch files, which always contain only a small chunk of the complete table structure? Does it really also add tables, which should already have been there?

Bawolff (talkcontribs)

It adds tables that should be there provided they were introduced after MediaWiki 1.5 (The update script doesn't know if the table is "missing" or if you are just upgrading from a really really old version of MediaWiki).

So it will work for l10n_cache table. It wouldn't work for say the querycache table

Reply to "Fatal exception of type Wikimedia\Rdbms\DBQueryError after update upto 1.29.2"