Project:Support desk

(Redirected from Project:Support)
Jump to: navigation, search
vde   Welcome to's Support desk, where you can ask MediaWiki questions!

There are also other places where to ask: IRC, mailing 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 discussion".
Start a new discussion


Thread titleRepliesLast modified
Missing "continue" button in installation mediaWiki122:58, 29 July 2015
Migrate from XWIKI to MediaWIKI320:17, 29 July 2015
Can't upgrade (xampp)917:43, 29 July 2015
Preventing spam113:33, 29 July 2015
[RESOLVED] Login Problem2712:08, 29 July 2015
Mediawiki install123:45, 28 July 2015
Starting conversion of LiquidThreads to Flow at mediawiki.org521:58, 28 July 2015
deleting user accounts from user list221:56, 28 July 2015
ElasticSearch extension not supported for CirrusSearch Extension downloaded from latest WIKI version 1.25.1514:33, 28 July 2015
Can't enable skin Vector.php510:29, 28 July 2015
Boot108:38, 28 July 2015
Create users by the admin did not work503:00, 28 July 2015
HTML markup in search results022:55, 27 July 2015
File Upload021:14, 27 July 2015
Search result without image as first.010:50, 27 July 2015
Log has not be created for today107:04, 27 July 2015
Editing footer links107:00, 27 July 2015
delete watchlisttoken406:48, 27 July 2015
Memory Leak? Memory running out.316:37, 26 July 2015
No links in the mobile view1214:50, 26 July 2015
First page
First page
Previous page
Previous page
Last page
Last page

Missing "continue" button in installation mediaWiki


i have a problem with installation mediawiki on Debian server. I am on step "8" called "optioins". On this page i cant found continue button.

I turned on error showing and here is output:

Warning: opendir(/usr/share/mediawiki/extensions): failed to open dir: No such file or directory in /usr/share/mediawiki/includes/installer/Installer.php on line 1273

Warning: readdir() expects parameter 1 to be resource, boolean given in /usr/share/mediawiki/includes/installer/Installer.php on line 1275

Warning: readdir() expects parameter 1 to be resource, boolean given in /usr/share/mediawiki/includes/installer/Installer.php on line 1275

Please, can you help me?

Thank you Dominik, 29 July 2015

Hi Dominik,

you are missing the folder extensions/.

How are you installing MediaWiki? Recommended is to use the tarball from and to extract it. This tarball will contain a folder called extensions/. Basically this folder must be in your installation., 29 July 2015

Migrate from XWIKI to MediaWIKI


do anyone know what's the easiest way to convert XWIKI content to MediaWIKI

Thanks in advance, 12 May 2014

Me too ! Many erros in try to import xml of xwiki !, 24 June 2014

+1, 25 November 2014

Can't upgrade (xampp)


When I run maintenance/update.php, I get the error "DatabaseBase::factory no viable database extension found for type 'mysql'":

mywiki/maintenance$ php update.php 
MediaWiki 1.24.1 Updater

[1c0b983f] [no req]   Exception from line 890 of /opt/lampp/htdocs/mywiki/includes/db/Database.php: DatabaseBase::factory no viable database extension found for type 'mysql'
#0 /opt/lampp/htdocs/mywiki/includes/db/LoadBalancer.php(737): DatabaseBase::factory(string, array)
#1 /opt/lampp/htdocs/mywiki/includes/db/LoadBalancer.php(610): LoadBalancer->reallyOpenConnection(array, boolean)
#2 /opt/lampp/htdocs/mywiki/includes/db/LoadBalancer.php(490): LoadBalancer->openConnection(integer, boolean)
#3 /opt/lampp/htdocs/mywiki/includes/GlobalFunctions.php(3632): LoadBalancer->getConnection(integer, array, boolean)
#4 /opt/lampp/htdocs/mywiki/maintenance/update.php(136): wfGetDB(integer)
#5 /opt/lampp/htdocs/mywiki/maintenance/doMaintenance.php(101): UpdateMediaWiki->execute()
#6 /opt/lampp/htdocs/mywiki/maintenance/update.php(206): require_once(string)
#7 {main}

I searched in other threads, and didn't understand where the error comes from: my PHP version is 5.5.9-1ubuntu4.9 (so I guess it's ok), and my wiki works hosted on localhost works fine. So, how can I upgrade my MediaWiki version?

Hydorn (talk)15:32, 25 June 2015

The error

DatabaseBase::factory no viable database extension found for type 'mysql'

means that MySQL is not available from inside PHP. You can upload a PHP file to your server with the following content:

<?php phpinfo();

When you call this file with your webbrowser, you will see information on your PHP installation.

Make sure that the MySQL extension of PHP is enabled (by editing php.ini)! After you enabled it, restart the server for your changes to take effect. The phpinfo() output then should contain a section on MySQL and it should say that MySQL is "enabled"., 25 June 2015

MediaWiki now requires mysqli driver instead of mysql, IIRC

Ciencia Al Poder (talk)09:22, 26 June 2015

I don't know that, but newer versions of PHP definitely have the mysql extension deprecated in favour of mysqli. So you surely should use the mysqli extension, if that is available.

Thanks for noting!, 26 June 2015

Well, apparently mediawiki now uses mysqli as default, and mysql as fallback, but both are still supported.

Ciencia Al Poder (talk)14:57, 26 June 2015

OK, here is my php configuration (got with phpinfo()) : Php configuration.png Is mysqli or mysql disabled? Not clear to me...

Hydorn (talk)09:39, 1 July 2015

Preventing spam

What can I do to prevent spam? Somebody flooded Speedypedia with hundreds of new users and spam pages, probably because I posted in this website ( a link to Speedypedia. How can we prevent such spam? I think it can be a bot or many bots who created this spam.

Uri Even-Chen (talk)12:34, 29 July 2015

[RESOLVED] Login Problem

Media Wiki: 1.16.0 PHP: 5.2.12 MySQL: 5.0.67-log

Hey, I installed the wiki on a local server and configured all settings, but when i wanted to log in with my admin account, i got this error message: "There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Go back to the previous page, reload that page and then try again" I tried it again and again, but the result was equal, the same problem when I try to register a new account., 5 September 2010

I get the same error as thread starter..anyone pls can help us? Im using 1.16 + wamp., 13 September 2010

I'm having the same problem on the new clean installation when trying login or create a new account - any solution for it?.., 8 November 2010

Probably something is wrong with your sessions; most likely PHP is not able to write to your sessions directory. Check your php.ini for the sessions directory and if PHP can write to those files.

-- Bryan (talk|commons)20:18, 11 November 2010

I got the same problem since soon, but not for all the installations on the same server (same version). Apparently the cookies are not good. It seems to come from the repertory of installation...

Lamidesbetes18:19, 12 November 2010

The connection to the database seems also be examined in this problem !

Lamidesbetes18:20, 12 November 2010

Looks like this has to do with setting a DNS CNAME.. it's only happening in IE8 for me... anyone have a fix?, 8 December 2010

I have the exact same issue now, fresh install. Anyone going to help with this??, 25 March 2011

I found this solution:

go in your LocalSettings.php and at the end add the following code of line :


Create a folder "tmp" in your wiki installation directory. give rights 777 (permissions)

Which worked for me.... also, check to make sure your disk has space, 31 March 2011

This worked perfectly for me on a new install. Thanks, you're the first person to actually give a usable answer to those that don't have access to the server's PHP.ini files that I could find., 20 May 2011

Eh?! Don't put it in web-accessible directories, or your user accounts will be easily hackable.

Max Semenik05:12, 20 May 2011

This worked for me. I had this problem with MW 1.18.1 after I upgraded my hosting with godaddy and they changed my ip and dedicated ip. Mediawiki kept asking for cookies to be enabled (they were enabled) on all types of browsers and platforms including the iphone. Problem solved for now, even though I'd like to know if it will come back after an upgrade.

Mark21:13, 2 March 2012

what is meant by give rights 777?, 27 June 2013

Same problem, can't even register or login as admin. Enough space is present., 21 September 2011

Looks like it was caused by using $wgMainCacheType two times in LocalSettings.php, now it's solved.

Beznogim23:05, 1 October 2011

Hi also have the same problem where the IP address work perfectly yet the hostname fails.

Would love some kind of explanation?, 13 January 2012

The problem i'm experiencing just seems to be Internet Explorer only. Firefox and chrome are un-affected either by the hostname or IP address.

Although I can login using IE6/IE8 with the IP address,
The problem occurs using the hostname.
Example: http://myserver/mediawiki

If I goto the login page a 'sess_xxxx' in the /tmp folder is created. If I attempt to login, or just refresh the login page this seems to set brand new a sess_xxxx everytime.

I have checked the apache logs and the client IP address is always the same regardless if i used the hostname of IP address.

Its not a permission issue.

I have also tried the following which was suggested with no success. $wgUseSquid = true;

Some suggestion would be greatly appreciated.

[SOLVED: My issue was caused by having an 'underscore' in the hostname example http://my_server - IE looks though it doesn't handle the underscore in the hostname as well as FF or Chrome does. Hope this helps anyone else using Mediawiki within their local intranet], 2 February 2012

had this error and the problem is that the facility lacked a standard memcached adding correct configuration

$wgSessionsInMemcached = true; # optional, 20 March 2012

... a little more resolved. This can also be a symptom of being short on disk space.

Salquint (talk)17:44, 23 August 2013

hi please upgrade to 1.19.0 or higher please, 24 August 2013

Nothing would please me more (at least regarding mediawiki), but I require WYSIWYG working on a Semantic Form for my users, so I'm stuck with what I've got. Anyone similarly stuck can heed the diskspace problem as a possible reason for this problem.

Salquint (talk)19:37, 24 August 2013

I have the same issue right now. I am able to login as the administrator but any new account is not able to login.

jjohnson19:13, 8 July 2015
Edited by 0 users.
Last edit: 12:05, 29 July 2015

jjohnson: try this. Worked for me

satpatruni12:05, 29 July 2015

Mediawiki install

I am trying to install this on CentOS 6.6. I install the software and it won't let me do the actual setup. I've tried many things suggested on the internet. When I try to run the update script, I get the following error:

Function: DatabaseBase::sourceFile( /var/www/html/mediawiki-1.25.1/maintenance/interwiki.sql ) Error: 1054 Unknown column 'iw_api' in 'field list' (localhost), 28 July 2015

How are you doing the install?

The recommended method is to use the tarball from, extract it and to go through installation - I usually do that with the webbrowser.

When you now try again, before you start, please make sure that the database, which you are using, is actually empty. Should there be parts of the previous attempts (like some tables with some columns), remove them. The presence of such tables while you in fact want to do a new installation might confuse MediaWiki., 28 July 2015

Starting conversion of LiquidThreads to Flow at

LiquidThreads (LQT) has not been well-supported in a long time. Flow is in active development, and more real-world use-cases will help focus attention on the higher-priority features that are needed. To that end, LQT pages at will start being converted to Flow in the next couple of weeks. This page, as the most active on will be the last to be converted.

Please see details, and an emphatic request for feedback, at Topic:Sdoatsbslsafx6lw. Much thanks.

Quiddity (WMF) (talk)07:28, 17 March 2015
Edited by 2 users.
Last edit: 12:53, 5 June 2015

See also[edit | edit source]

11:43, 18 March 2015

Update: All pages except for this one, and VisualEditor/Feedback (which will be converted tonight), have been converted to Flow. This final page will be converted during the Wednesday workday.

Thanks again to everyone who submitted bug reports, suggestions, constructive criticism, and feature requests. You might be interested to see the slides from the recent Wikimania presentation, File:User(s) Talk(ing) - Wikimania 2015.pdf, or to signup as a user research volunteer via (they're currently doing some Flow research, but they cover many other aspects of the site in other months). As always, your comments and suggestions are welcome, encouraged, and needed, at Talk:Flow.

Quiddity (WMF) (talk)19:08, 28 July 2015

Thanks for the update! Keeping fingers crossed... :-), 28 July 2015

deleting user accounts from user list

running MediaWiki 1.24.1

Three questions:

1.Is it possible to delete user accounts after creating an account, especially if you have sent a random password and cant acquire the password?

2.Is it possible to change the password after creating the account if you have sent a randomly generated password to their email address?

3.Also, if you've selected to send a user a random password to their email when creating the account is it possible to resend this account verification email to them if they accidentally deleted it.

Oechsli123 (talk)18:39, 27 July 2015

"1.Is it possible to delete user accounts after creating an account, especially if you have sent a random password and cant acquire the password?"

For help with Q1, you can try this Extension:UserMerge

Mlpearc (open channel)21:06, 28 July 2015
2.Is it possible to change the password after creating the account if you have sent a randomly generated password to their email address?

Yes, the user himself can simply log in with the random password; afterwards he can change it as he likes. Should the question be, if someone else can change the password, e.g. an admin, because the user for some reason cannot log in: The maintenance script changePassword.php can do that., 28 July 2015

ElasticSearch extension not supported for CirrusSearch Extension downloaded from latest WIKI version 1.25.1


I have upgraded WIKI for latest stable version 1.25.1. As MWSearch is obsolete extension so I have tried install CirrusSearch with ElasticSearch extention. But unfortunately I found below error message :


Warning: Invalid argument supplied for foreach() in /data/www/html/wikinew/extensions/Elastica/ElasticaConnection.php on line 78 Warning: Search backend error during fetching elasticsearch version after 2. Param host does not exist [Called from CirrusSearch\ElasticsearchIntermediary::failure in /data/www/html/wikinew/extensions/CirrusSearch/includes/ElasticsearchIntermediary.php at line 98] in /data/www/html/wikinew/includes/debug/MWDebug.php on line 300

content index...

       Fetching Elasticsearch version...unable to determine, aborting.PHP Notice:  Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53

Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53 ...Not supported! Only Elasticsearch 1.x is supported. Your version: . "

Please help to resolve the above issue.

Thanks in Adv. Sanjay

Sanjay (talk)15:07, 15 July 2015

It seems you haven't a running Elasticsearch server, or you haven't configured it in the configuration variable $wgCirrusSearchServers.

Florianschmidtwelzow (talk)11:10, 16 July 2015

Hi, I configured ElasticSearch Server name in variable $wgCirrusSearchServers. But when I run the script updateSearchIndexConfig.php under /extensions/CirrusSearch/maintenance and I got below Error/Warning message.

content index...

  1. PHP Warning: Invalid argument supplied for foreach() in /data/www/html/wikinew/extensions/Elastica/ElasticaConnection.php on line 78
  2. Warning: Invalid argument supplied for foreach() in /data/www/html/wikinew/extensions/Elastica/ElasticaConnection.php on line 78 Fetching Elasticsearch version...unable to determine, aborting.PHP Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53
  3. Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53
  4. ...Not supported!
  5. Only Elasticsearch 1.x is supported. Your version: .

Please suggest for the solution since it says Only Elasticsearch 1.x is supported.

Info: I have used 'CirrusSearch-REL1_25-ace4f80.tar.gz' & 'Elastica-REL1_25-eb56a6d.tar.gz'

Thank You !

Sanjay (talk)12:22, 16 July 2015

After I configured in the configuration variable $wgCirrusSearchServers = array( 'elasticsearch0', 'elasticsearch1' );

Will you please let me know what a ElasticSearch Server is? Is it the same server where I hosted MediaWIKI 1.25.1 with the extensions 'CirrusSearch-REL1_25-ace4f80.tar.gz' & 'Elastica-REL1_25-eb56a6d.tar.gz' ?

Still I get the below Err Notice after running script 'updateSearchIndexConfig.php'

content index...

  1. Fetching Elasticsearch version...unable to determine, aborting.PHP Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53
  2. Notice: Undefined index: version in /data/www/html/wikinew/extensions/CirrusSearch/includes/Maintenance/ConfigUtils.php on line 53
  3. ...Not supported!
  4. Only Elasticsearch 1.x is supported. Your version: .

Please suggest.

Thank you !

Sanjay (talk)13:49, 16 July 2015

You need to install elasticsearch on a server, it's a search service. You need to install it manually using the shell, it's normally not pre-installed. If it isn't installed, you can't use CirrusSearch (CirrusSearch itself doesn't work without elasticsearch).

Florianschmidtwelzow (talk)06:02, 17 July 2015

I have successfully installed elasticsearch as a service using shell and I can able to access the service through the default port 9200 or by using curl.

Below is the set of configuration on my 'LocalSettings.php'

  1. require_once( "$IP/extensions/Elastica/Elastica.php" );
  2. require_once( "$IP/extensions/CirrusSearch/CirrusSearch.php" );
  3. #$wgDisableSearchUpdate = true;
  4. $wgCirrusSearchServers = array( '' );
  5. $wgSearchType = 'CirrusSearch';

Still I have the below error while searching full text "

An error has occurred while searching: We could not complete your search due to a temporary problem. Please try again later."[edit | edit source]

Kindly provide a fix to the above ERROR !

Thanks in Adv. Sanjay

Sanjay (talk)14:28, 28 July 2015

Can't enable skin Vector.php


I've just installed MW 1.24.2 and tried to display the main page. Unfortunately there is an error saying: \mediawiki\skins\Vector/SkinVector.php): failed to open stream: No such file or directory in ...\mediawiki\includes\AutoLoader.php on line 1282

I checked in the LocalSettings.php if there is a problem with the path, but the default skin is set for "vector" and require_once "$IP/skins/Vector/Vector.php"; seems to be alright as well. The path of SkinVector.php seems to be correct and I couldn't find any typos or similar in the directory. I tried to download the skin separately and paste it into the skins directory, but then it says its only compatible with MW1.25+. I realized the error shows up with every skin I try to enable.

Any hints what might be the problem? I'm actually still thinking of a path problem, but I just don't know where to look after it.

MediaWiki: 1.24.2 PHP: 5.6.3 Database: MySQL 5.6.17

Mafi9 (talk)14:10, 27 July 2015

When you install MediaWiki, have you then taken a checkout from the Git versioning system? Doing so would be a way I could imagine you get this error.

In contrast, for normal end users, the recommended installation method is to use a tarball from here: 1.25 btw. is the newest version - but a 1.24.2 tarball is available as well, if you want that. These tarballs contain everything you need, also the Vector skin in the correct version. :-), 27 July 2015

Hello and thank you for the reply! The reason why I don't use the 1.25 version is that I simply couldn't get the installation running - instead of getting the index.php to start from I always got a blank page, even tough I meet the requirements.

In the meantime I could fix the problem with the vector skin. In Vector.php on line 36 I replaced "$GLOBALS['wgAutoloadClasses']['SkinVector'] = __DIR__ . '/SkinVector.php';" with "$GLOBALS['wgAutoloadClasses']['SkinVector'] = 'skins/Vector/SkinVector.php';" and it seems to work fine now. :)

Mafi9 (talk)07:03, 28 July 2015

Regarding blank pages: Have you checked phab:T44205 (and maybe Manual:Errors_and_symptoms#You_see_a_Blank_Page)?

AKlapper (WMF) (talk)08:42, 28 July 2015

Yes I have checked the errors and symptoms of a blank page, but none of them seems to work for me. Because I have a blank page before the install I don't have a LocalSettings to modify, nor I have access to the php.ini since I'm on a hosted server. Regarding the DOM-XML problem I have checked with the phpInfo, but DOM-XML support is enabled as well as the other requirements.

Mafi9 (talk)09:56, 28 July 2015

Your change in Vector.php looks strange: __DIR__ is defined since PHP 5.3 at least. If you have PHP 5.6, this change should not be needed and if you have an old PHP version, you should get a different error ("Use of undefined constant __DIR__...").

For the blank page, you should check the error log or have your host tell you, what after such error is inside., 28 July 2015


I want to use some boot.

Where should I start?

I want to use boot f.e. to change categories on pages.

TraaBBIT (talk)17:25, 27 July 2015

Which boot?

Malyacko (talk)08:38, 28 July 2015

Create users by the admin did not work

Hi, When creating a rather restricted Wiki (MediaWiki 1.25.1), I set:

$wgGroupPermissions['*']['createaccount'] = false;
$wgGroupPermissions['*']['edit'] = false;
$wgGroupPermissions['*']['read'] = false;

Then I created the users (Create Acccount) as admin and I did set "Use a temporary random password and send it to the specified email address". The users all got a mail with their username and a temporary passwort. But login with the temporary password did not work.

Do I have to do additional steps to 'enable' the users?

In the database there is no (hashed) password for the new users: select user_password from user where user_name='USERNAME'; returns an empty field. Shouldn't that contain the hashed (temporary) password?

Best regards, 14 July 2015

Maybe another instance of task T102927?

Ciencia Al Poder (talk)21:18, 14 July 2015

I thought that as well, but I didn't write it, as -if I got it right- we are not speaking about confirmation emails here., 14 July 2015

Have you checked your server logs? Are there any related error/warning/notice messages?

Florianschmidtwelzow (talk)23:08, 18 July 2015

I think that I have the same problem with version 1.25.1 Did you find a proper solution?

I found a workaround by telling the new users to use the lost password button, which would send them a new random password, which works OK., 19 July 2015

HTML markup in search results


In older versions of MW to removed HTML markup from search results you had to add $this->mText = strip_tags( $this->mText ); to the SearchEngine.php but in 1.25.1 this file no longer has a function called getTextSnippet(). Any ideas where this function is or how to make it work now?

Cristal01 (talk)22:47, 27 July 2015

File Upload


MediaWiki:1.25.1 PHP:5.4.43 (cgi-fcgi) MySQL:5.5.42-cll Lua:5.1.5

Everytime i upload an image i get a database error but no further info, if i look at the file list it states error code 127

File Page:

Any idea how i might fix this?

EDIT: After turning on detailed errors it now shows: Notice: Uncommitted DB writes (transaction from DatabaseBase::query (WikiPage::pageData)). in /home/forgewareinc/public_html/wiki/includes/db/Database.php on line 4362

Dmitchell94 (talk)20:41, 27 July 2015

Search result without image as first.

Hello. I have problem with search result in a mediawiki. In the result of search I'm getting first image and then later pages. It is possibe to change search setting? I would like to have first pages and then images. If there is not possible to change setting. Could you please tell me how I can turn off the image search?, 27 July 2015

Log has not be created for today

using php 5.3.4

added the page curation extension, and when I try to nominate a page for deleteion and give a detail description..I get a popup that reads "log has not been created for today"

can someone help?

You did run "update.php" after adding? See Extension:PageTriage

Malyacko (talk)07:04, 27 July 2015

Editing footer links


I just installed the latest version of mediawiki and the default footer links are not really what I want.

1st How do I make it not a string? I have been through some guides but they were all for some older versions and php files/sections they refer to either do not exist anymore or contain completely different code (I am not an IT guy, I have to idea how to code so I have to rely on examples/guides) :s

2nd Where do I change the actual text of this "This page was last modified on 23 July 2015, at 13:30", I think it's too long so I would like to make the text shorter (not to mention this "Content is available under GNU Free Documentation License 1.3 or later unless otherwise noted.").. my footer is only 700px wide, those two things get wrapped almost twice..

3rd How do I add a new link/text, for example, how many times a page has been viewed. In an older version I had something like "This page has been accessed 153,112 times." but now I do not get that at all, is it because of a different skin (currently Monobook)?, 25 July 2015

delete watchlisttoken

Hi, im using MediaWiki 1.24, PHP 5.3, MySQL 5.1.72 and VectorSkin on my Site ( )

How can I delete the watchlisttoken (the white/blue star next to the searchbox) for all users who are logged in. I've already hidden the watchlist-Link in the personal-url with css (MediaWiki:Common.css) but I can't find how to get rid of this token.

Thanks, Ray

Marienberg2 (talk)10:36, 25 July 2015


#ca-watch { display:none!important; }

will hide the star symbol just as you hide the other tabs currently., 25 July 2015

Thanks a lot!

By adding

  1. ca-watch { display:none!important; }
  2. ca-unwatch { display:none!important; }

the token was gone., 27 July 2015

I don't know what the proper name for the #ca-watch star is, but I'm almost sure the real "watchlist token" is the one described in MediaWiki:Prefs-watchlist-token.

Ricordisamoa14:03, 25 July 2015

What my CSS hides is the star symbol.

What Ricordisamoa‎ speaks about is a text, which shows up in the user preferences (I believe?). If you in fact want to hide options in the user preferences, then you should not use CSS to do that, but you should use the configuration variable $wgHiddenPrefs in the LocalSettings.php file!

$wgHiddenPrefs[] = 'watchlisttoken';

in LocalSettings.php should hide that entry (according to the docs, but untested)., 25 July 2015

Memory Leak? Memory running out.

Hi there, I noticed my media wiki is absorbing a lot of memory especially mysqld.bin.I am not sure why. I have 2gb ram and 1 cpu allocated to the VM for my mediawiki. At the same time, the nodejs has 4 workers. I am not sure why either. the only thing using the nodejs i though would be the parser.

The installed software i am using are: MediaWiki 1.25.1 PHP 5.5.25 (fpm-fcgi) MySQL 5.6.23

The only extensions i have are: Admin Links category Tree launchExternal ParserFunctions DiscussionThreading Universal LanguageSelector VisualEditor WikiEditor

I have a snapshot of the top:

Hope to hear from someone.

AmazingTrans (talk)22:15, 24 July 2015

mysqld is the Mysql database server, not MediaWiki (MediaWiki is handled by php and your webserver). You may need to configure mysql server properly according to your available memory.

Note that databse servers usually need to consume more memory to buffer query results and data that's accessed more frequently, so retrieving that data doesn't require to fetch it from the disk (which would be slow). Reducing the available memory for the database may make database access slower.

Ciencia Al Poder (talk)13:32, 25 July 2015
I guess what configuration should I setup for mysql? Or how can I limit it to 1gb? Rather than dynamically expanding?
AmazingTrans (talk)14:51, 25 July 2015

You should probably document yourself about those settings, but there's (not sure how accurate is it).

Ciencia Al Poder (talk)16:37, 26 July 2015

No links in the mobile view

I recently created Speedypedia [], which is based on MediaWiki. I noticed that in the mobile view, links to articles which don't exist yet are removed, probably with JavaScript (for example, in the article about Haggai Matar there is no link to Anat Matar, and I think it changes after the page loads). Is it possible to remove this feature and display the links in the mobile view, like in the desktop view?

Thanks, Uri.

Uri Even-Chen (talk)10:17, 23 July 2015

I see the red links.

FriedhelmW (talk)11:54, 23 July 2015

Add the following to your LocalSettings.php after the require_once line of MobileFrontend:

$wgMFShowRedLinks = true;
$wgMFShowRedLinksAnon = true;

That's it.

Florianschmidtwelzow (talk)15:53, 23 July 2015

Thank you, it worked! what are these options? @Fried, the red link only didn't appear in the mobile view, not in the desktop view.

Uri Even-Chen (talk)16:16, 23 July 2015

Redlinks are deactivated in mobile for performance reason and because the mobile editor wasn't a really good function to welcome users (especially newcomers). So we deactivated them and added these two options to activate them, e.g. if third party wikis want to use them. The first one is for logged in users (if set to true, logged in users always see redlinks, but logged out users doesn't) and the second one is for logged out users.

Btw.: In the next release (1.26), redlinks will be enabled by default with a Click-to-action banner, if the user really wants to create a new page or not (redlinks are well known in the editing community, but a new user maybe doesn't know what it is, and the mobile editor doesn't have the nce warnings, like on desktop).

Florianschmidtwelzow (talk)18:52, 23 July 2015

I have another problem - in the mobile view, if I search for an article which doesn't exist yet, I don't have a link to create this article (I only get this link in the desktop view). Is it also a feature we have to enable?

Uri Even-Chen (talk)16:54, 23 July 2015

No, that is disabled by design. The mobile editor is a plain wikitext editor, which is a worse experience for newcomers. So, the eitor isn't really suitable for creating pages, too and we've disabled the create link for search. If you really want to enable it, you could do the following:

.mw-search-createlink {
    display: inherit !important;
  • Save and reload the search page (maybe you have to clear your browser cache and maybe any other existing cache layers, depends on your setup)
Florianschmidtwelzow (talk)18:49, 23 July 2015

OK, thank you! I'll try.

Uri Even-Chen (talk)05:20, 24 July 2015

Thank you, it worked!

Uri Even-Chen (talk)12:49, 24 July 2015

I have another question about Speedypedia. In Speedypedia one has to login or register to edit or create articles. When a user is not logged in in the mobile view, if he clicks on the "Edit" of any page he receives the message: "This page is protected to prevent vandalism." But the page is not protected, logged in users can edit it. I want the user to see the message "Would you like to edit this page? Login or register to edit articles.", unless the page is really protected (which is not the case in the page I tested). In the desktop view it's fine, if I'm not logged in I can view source, or create account or log in. But in the mobile view I receive this message if I try to edit the page.

Uri Even-Chen (talk)12:55, 24 July 2015

Yeah, the problem is, that we never tested MobileFrontend with wikis, where you have to register to edit :) MF (=MobileFrontend) show this error message, whenever the page can not be edited by the current user, there is no configuration to handle this. Would you like to file a task in Phabricator for it? (Please note, that you're using REL1_25, so the WMF team(s) can decide what to do, normally we don't support other branches as master :)).

Florianschmidtwelzow (talk)17:32, 24 July 2015

Task created, I don't understand what you mean REL1_25? If you want to know my version of MediaWiki, go to (MediaWiki 1.25.1).

Uri Even-Chen (talk)13:25, 25 July 2015

REL1_25 is the 1.25.X release branch in our git repository, it reflects the latest release of MediaWiki 1.25 :)

Florianschmidtwelzow (talk)14:50, 26 July 2015
First page
First page
Previous page
Previous page
Last page
Last page