Project:Support desk

(Redirected from Support Desk)
Jump to: navigation, search
vde   This page is for questions relating to the MediaWiki software.

Welcome to's Support desk, the central on-wiki place to ask MediaWiki questions!

The greater purpose of this page is to make our Manual and other available help so good that you do not have to come here to ask questions, or making them easier to find.

There are other ways for of communication as well (IRC, mailing lists etc.). Read more here.

Before you post

Post a new question

  1. To help us answer your questions, please always indicate which versions you are using:
    • MediaWiki (reported by your wiki's Special:Version page)
    • PHP (likewise)
    • Database (likewise, e.g. MySQL 5.5)
  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".

Archiving topics

Topics are automatically archived when they have been inactive for three weeks. If a question you have asked is approaching this limit and still has not been answered, please 'bump' it to prevent it being archived. However do not 'bump' for other reasons.

Start a new discussion
First page
First page
Previous page
Previous page
Last page
Last page

Some errors with GraphViz 1.4.0 on MW 1.25alpha and SMW 2.0

[2ec1cfca] /w/rurakwiki/index.php?title=Spielwiese&action=submit Exception from line 6390 of /var/www/w/rurakwiki/includes/parser/Parser.php: Parser state cleared while parsing. Did you call Parser::parse recursively?


  1. 0 /var/www/w/rurakwiki/includes/parser/Parser.php(4795): Parser->lock()
  2. 1 /var/www/w/rurakwiki/includes/content/WikitextContent.php(146): Parser->preSaveTransform(string, Title, User, ParserOptions)
  3. 2 /var/www/w/rurakwiki/includes/page/WikiPage.php(2140): WikitextContent->preSaveTransform(Title, User, ParserOptions)
  4. 3 /var/www/w/rurakwiki/extensions/SemanticMediaWiki/includes/src/MediaWiki/EditInfoProvider.php(88): WikiPage->prepareContentForEdit(WikitextContent, NULL, User, string)
  5. 4 /var/www/w/rurakwiki/extensions/SemanticMediaWiki/includes/src/MediaWiki/EditInfoProvider.php(66): SMW\MediaWiki\EditInfoProvider->prepareContentForEdit()
  6. 5 /var/www/w/rurakwiki/extensions/SemanticMediaWiki/includes/src/MediaWiki/Hooks/NewRevisionFromEditComplete.php(81): SMW\MediaWiki\EditInfoProvider->fetchEditInfo()
  7. 6 /var/www/w/rurakwiki/extensions/SemanticMediaWiki/includes/src/MediaWiki/Hooks/NewRevisionFromEditComplete.php(76): SMW\MediaWiki\Hooks\NewRevisionFromEditComplete->getParserOutputFromEditInfo()
  8. 7 /var/www/w/rurakwiki/extensions/SemanticMediaWiki/includes/Setup.php(392): SMW\MediaWiki\Hooks\NewRevisionFromEditComplete->process()
  9. 8 [internal function]: SMW\Setup->SMW\{closure}(WikiFilePage, Revision, integer, User)
  10. 9 /var/www/w/rurakwiki/includes/Hooks.php(206): call_user_func_array(Closure, array)
  11. 10 /var/www/w/rurakwiki/includes/GlobalFunctions.php(4004): Hooks::run(string, array, NULL)
  12. 11 /var/www/w/rurakwiki/includes/filerepo/file/LocalFile.php(1424): wfRunHooks(string, array)
  13. 12 /var/www/w/rurakwiki/includes/filerepo/file/LocalFile.php(1184): LocalFile->recordUpload2(string, string, string, array, boolean, User)
  14. 13 /var/www/w/rurakwiki/includes/upload/UploadBase.php(736): LocalFile->upload(string, string, string, integer, NULL, boolean, User)
  15. 14 /var/www/w/rurakwiki/extensions/GraphViz/UploadLocalFile.php(238): UploadBase->performUpload(string, string, boolean, User)
  16. 15 /var/www/w/rurakwiki/extensions/GraphViz/GraphViz_body.php(1013): UploadLocalFile::upload(string, string, User, string, string, boolean, boolean)
  17. 16 /var/www/w/rurakwiki/extensions/GraphViz/GraphViz_body.php(640): GraphViz::render(string, array, Parser)
  18. 17 [internal function]: GraphViz::graphvizParserHook(string, array, Parser, PPFrame_DOM)
  19. 18 /var/www/w/rurakwiki/includes/parser/Parser.php(4227): call_user_func_array(array, array)
  20. 19 /var/www/w/rurakwiki/includes/parser/Preprocessor_DOM.php(1268): Parser->extensionSubstitution(array, PPFrame_DOM)
  21. 20 /var/www/w/rurakwiki/includes/parser/Parser.php(3310): PPFrame_DOM->expand(PPNode_DOM, integer)
  22. 21 /var/www/w/rurakwiki/includes/parser/Parser.php(1268): Parser->replaceVariables(string)
  23. 22 /var/www/w/rurakwiki/includes/parser/Parser.php(433): Parser->internalParse(string)
  24. 23 /var/www/w/rurakwiki/includes/content/WikitextContent.php(338): Parser->parse(string, Title, ParserOptions, boolean, boolean, NULL)
  25. 24 /var/www/w/rurakwiki/includes/content/AbstractContent.php(490): WikitextContent->fillParserOutput(Title, NULL, ParserOptions, boolean, ParserOutput)
  26. 25 /var/www/w/rurakwiki/includes/page/WikiPage.php(2145): AbstractContent->getParserOutput(Title, NULL, ParserOptions)
  27. 26 /var/www/w/rurakwiki/includes/page/WikiPage.php(1814): WikiPage->prepareContentForEdit(WikitextContent, NULL, User, string)
  28. 27 [internal function]: WikiPage->doEditContent(WikitextContent, string, integer, boolean, NULL, string)
  29. 28 /var/www/w/rurakwiki/includes/page/Article.php(2012): call_user_func_array(array, array)
  30. 29 /var/www/w/rurakwiki/includes/EditPage.php(1903): Article->__call(string, array)
  31. 30 /var/www/w/rurakwiki/includes/EditPage.php(1903): Article->doEditContent(WikitextContent, string, integer, boolean, NULL, string)
  32. 31 /var/www/w/rurakwiki/includes/EditPage.php(1287): EditPage->internalAttemptSave(array, boolean)
  33. 32 /var/www/w/rurakwiki/includes/EditPage.php(522): EditPage->attemptSave()
  34. 33 /var/www/w/rurakwiki/includes/actions/EditAction.php(56): EditPage->edit()
  35. 34 /var/www/w/rurakwiki/includes/actions/SubmitAction.php(40): EditAction->show()
  36. 35 /var/www/w/rurakwiki/includes/MediaWiki.php(414): SubmitAction->show()
  37. 36 /var/www/w/rurakwiki/includes/MediaWiki.php(282): MediaWiki->performAction(Article, Title)
  38. 37 /var/www/w/rurakwiki/includes/MediaWiki.php(584): MediaWiki->performRequest()
  39. 38 /var/www/w/rurakwiki/includes/MediaWiki.php(435): MediaWiki->main()
  40. 39 /var/www/w/rurakwiki/index.php(46): MediaWiki->run()
  41. 40 {main}

Any idea what would be the reason for this? The extension does work and I am able to draw with it, but at times there is a certain reluctance to do the job.

Temptuousinsolence (talk)15:17, 21 October 2014


MediaWiki 1.25 isn't released yet, it's in alpha. So, if you have problems, make sure, that you use the latest version of all components and try to find out, what component causes the error. Then you can create a BUGREPORT for it, so the developers can improve the feature(s).

Florianschmidtwelzow (talk)21:02, 21 October 2014

How can I use mwdumper with Postgresql command line

I was importing a MediaWiki database using mwdumper with MySql. Now I need to do the same thing, but using Postgresql.

Basicly I get a archive in this link:

And I use mwdumper program to get informations and put in my database.

This is the database script:

I created the database through this sql, and now I need to use mwdumper to put data in my database. I saw many links about this, but only to do in MySql.

Anyone know how to do this import using Postgres, using command line?, 21 October 2014

Honest answer? Don't do it.

Sure, you can use Postgres, but if you do, that means that you will have to deal with brokenness and bugs. MediaWiki's Postgres support is by far not as mature as its MySQL support. Instead of trying to make things work with Postgres somehow, you should better set up MySQL and use that.

With MySQL you'll be far better off., 21 October 2014

Install the Gumax skin (4.0.3)

Hello there, I need help installing the Gumax skin for my Wiki I host. I downloaded the Gumax skin 4.0.3 from here. I like the version 4.0.3 more than the other (newer) versions. I installed the Mediawiki software two weeks ago and the current version is MW 1.23.4. Yesterday I followed these steps in order to install the Gumax skin. But it doesn't working, if use ?useskin=gumax or activate the skin as user (preferred) skin. This will appear, if I use the preview: (1) What can I do to solve the problem in order to use this skin without any errors.

Yässinzeldafan (talk)15:48, 19 October 2014

I think it has something to do with this line: "It has been tested and works with MediaWiki 1.17.0" ;) MediaWiki 1.17 is really oudated and not supported anymore.

The Hook mentioned in the expect (in MW 1.23) two variables (array &$vars, OutputPage $out), the first as a reference. The skin file try to run the Hook as th efollowing:

wfRunHooks( 'MakeGlobalVariablesScript', array( $this->data ) )

(only one parameter and not as a reference. So that's why the skin fails :) Try to upgrade to a newer versions or contact the developers, if they can help you to upgrade this skin version to work with newer versions of MediaWiki.

Florianschmidtwelzow (talk)05:28, 20 October 2014
Edited by author.
Last edit: 13:02, 20 October 2014

Okay, mir ist aufgefallen, dass du einen deutschen Namen hast und so gehe ich mal aus, dass du diese Sprache verstehst.

Ich habe schonmal den Support dort kontaktiert. Ich bin gerade am zweifeln, da das Forum als auch die Website seit 2013 nicht mehr bearbeitet wurden und ich zweifle daran, dass eine Antwort kommt... Natürlich kann ich versuchen andere Versionen zu installieren, aber was mich stört ist die Topbar, die zentriert ist. Ich hätte es gerne, wenn die links bleibt. Ich bin mir sicher, dass man in der aktuellen Version mittels PHP die Topbar nach rechts verschiebt. (Siehe zum Beispiel aktuelle Version und Version 4.0.3) Ich wäre offen, wenn man mir hilft, die Topbar nach rechts zu verschieben. Doch zunächst möchte ich warten auf eine Antwort vom dortigen Support. Was meint ihr? Wird es zu einer Antwort vom Support kommen, obwohl die Website schon seit 2013 nicht mehr bearbeitet wurde?

Ich bräuchte nochmal Hilfe: Und zwar versuche ich Extension:CheckUser zu installieren aber es erscheint, wenn ich jemanden CheckUserrechte gebe, "Datenbankfehler - [...] Es liegt ein Fehler in der Software vor". Ich muss gestehen, dass ich zwei Schritte, die auf der Extensionseite stehen übersprungen habe, da ich das erstens nicht verstanden habe und zweitens die nötigen Dateien nicht gefunden habe. Ich verwende FileZilla, aber nur für die Windows XP-Version. Kann man mir da auch helfen? (Wäre es angebracht, dass über Skype zu besprechen? Denn es würde dann vielleicht besser laufen.

Danke für eure Hilfe,

Yässinzeldafan (talk)12:06, 20 October 2014

Zu dem Skin: Ich fürchte, "das Team" ist schlicht Paul, der das Skin entworfen hat. ;-) Wenn du ne E-Mail-Adresse von ihm findest, kannst du ihn ja mal fragen, ob ihr zusammen das Skin für neuere MediaWiki-Versionen aktualisieren wollt.

Du musst alle Schritte von Extension:CheckUser#On_an_existing_wiki wie beschrieben durchführen. Der Datenbankfehler deutet z.B. darauf hin, dass du die nötigen DB-Updates nicht vorgenommen hast., 20 October 2014

Jau, danke. Zu Punkt 1: [Ich verwende FileZilla für Windows XP (aber ich steige eh bald auf Linux um)] Die Datei php maintenance kann ich nicht finden weder noch php maintenance.php, php maintenance/update.php weder noch update.php. Ich finde nur Update.sample und Ugrade.php Bei einer Dateisuche im Server kann ich leider nichts finden. :( Zu Punkt 2: (Erledigt.) Zu Punkt 3: (Erledigt.) Zu Punkt 4: Ich finde die Datei php update.php nicht und ich weiß nicht wie man mit FileZilla eine Datei startet.

Yässinzeldafan (talk)13:19, 20 October 2014

FileZilla ist ein FTP-Programm (übrigens ein sehr gutes) und mit FTP kann man keine Dateien ausführen. Der Befehl php update.php oder php maintenance/update.php ist für die Shell gedacht, also für Zugang über SSH. Da kann man Dateien ausführen. Neue Versionen von MediaWiki haben übrigens als mw-config/index.php einen Web-Updater. Der macht dasselbe wie update.php, aber man ruft ihn über den Webbrowser auf. Das klappt auch, wenn man keinen SSH-Zugang hat., 20 October 2014

Fatal exception of type MWException after upgrade to OSX server yosemite

I use MediaWiki 1.23.0 with OS X server mavericks. However after upgrade to OS X 4.0 yosemite, It shows error '[43887455] 2014-10-21 00:38:56: Fatal exception of type MWException' with the title of Internal error. I have no idea of how to solve. Anyone can advice me? Please let me know the solution., 21 October 2014


you should add $wgShowExceptionDetails to true in your LocalSettings.php to see more information about the Exception. Reproduce the error and give us the exact error message :)

Florianschmidtwelzow (talk)05:09, 21 October 2014

Error was like below:

CACHE_ACCEL requested but no suitable object cache is present. You may want to install APC.


  1. 0 [internal function]: ObjectCache::newAccelerator(array)
  2. 1 /Library/Server/Web/Data/Sites/ call_user_func(string, array)
  3. 2 /Library/Server/Web/Data/Sites/ ObjectCache::newFromParams(array)
  4. 3 /Library/Server/Web/Data/Sites/ ObjectCache::newFromId(integer)
  5. 4 /Library/Server/Web/Data/Sites/ ObjectCache::getInstance(integer)
  6. 5 /Library/Server/Web/Data/Sites/ wfGetMainCache()
  7. 6 /Library/Server/Web/Data/Sites/ require_once(string)
  8. 7 /Library/Server/Web/Data/Sites/ require(string)
  9. 8 {main}

I installed APC with homebrew, but I don't know how to reinstall it. I did uninstall and install but, APC shows error.

brew install autoconf brew install pcre sudo pecl install apc

2 warnings and 6 errors generated. make: *** [apc_compile.lo] Error 1 ERROR: `make' failed

I don't know what to do., 21 October 2014

You need to have a working APC installation to use CACHE_ACCEL (or XCache or WinCache). If you APC isn't working, you should use CACHE_NONE or CACHE_DB (or another supported cahce method).

Florianschmidtwelzow (talk)08:09, 21 October 2014

Now I see the problem.

I upgraded OS X server Mavericks to Yosemite.

Yosemite has php version of 5.5.

PHP 5.5 (Yosemite) is not compatible with APC 3.1.13 (My previous Version of APC).

Any idea for this situation?, 21 October 2014

Use Zend OPCache. It is included with PHP 5.5 and is the replacement for APC.

More info is here:, 21 October 2014

when I check Version, with php -v

It shows like below :

PHP Warning: PHP Startup: apc: Unable to initialize module Module compiled with module API=20100525 PHP compiled with module API=20121212 These options need to match

in Unknown on line 0

PHP 5.5.14 (cli) (built: Sep 9 2014 19:09:25) Copyright (c) 1997-2014 The PHP Group Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies, 21 October 2014

Unrelated but please use the latest 1.23.x version. 1.23.0 is old and has security issues.

AKlapper (WMF) (talk)07:24, 21 October 2014

How to make an image slider for Mediwiki?

Hello all! Does anyone know how to make a template which allows to insert image slider just like that?

Fokebox (talk)17:03, 21 October 2014

Upgraded old MW site to 1.23.3 and thumbnails stopped working

Edited by another user.
Last edit: 09:40, 16 September 2014

I have migrated a MW site onto a new VPS and noticed the version was old (1.16.1). So I updated it to 1.23.3 and after the upgrade, the thumbnails stopped working. Each thumbnail is now replaced by the message "Error creating thumbnail: File missing"

The thumbnails worked perfectly before the upgrade.

I switched on all the debugging by adding the following lines to LocalSettings.php:

# Debug mode on
$wgShowExceptionDetails = true;
$wgDebugToolbar = true;
$wgShowDebug = true;
$wgDevelopmentWarnings = true;

Nothing particularly useful is shown in the debug information that helps me identify the cause.

Today I decided to roll in the latest minor releases one by one and here are my results:

  • 1.16.1 - 1.17.5 = OK
  • 1.17.5 - 1.18.6 = OK
  • 1.18.6 - 1.19.18 = BANG!

I looked at the release notes for 1.19 and also found some posts that I thought might be related to thumbnails and MW 1.19 but none of the solutions offered seem to help me at all.

  • Imagemagick version:
  • php5-imagick is installed
  • php version: 5.4.4-14+deb7u14 (apache2handler)
  • MySQL version: 5.5.38-0+wheezy1

It's beaten me... Anyone have any ideas? I'm hoping for something simple!

AtariDal (talk)16:51, 15 September 2014

Well, in the debug log you should see the paths of the files it's trying to generate.

I'd suggest you to try loading thumb.php on your wiki to generate a thumbnail (specifying the correct parameters) and see if it throws the same error. Then go to the debug log and look at what's trying to do.

Pay special attention to all file paths it's accessing, to see if any file path is missing, or the directory structure it expects is different. Check also file permission issues.

Also look if in the debug log it attempts to run imagemagick, and if the error comes after the call to it. If that's what happens, try running the command directly (the debug log prints the command as it's being executed by MediaWiki). You may need to increase $wgMaxShellFileSize, $wgMaxShellMemory and Manual:$wgMaxShellTime.

Ciencia Al Poder (talk)09:47, 16 September 2014
Edited by another user.
Last edit: 09:28, 16 October 2014

I seem to be having exactly the same issue. Tried to turn debug on, but not and expert on mediawiki, so not certain where I might find what the issue is, if I at least could figure out where to look:)

Here is the debug log:, 15 October 2014

Even if someone could just give me an idea where to start to figure out if it is the database, the location of the files or one of the scripts. As it is now all I can tell is that it is trying to find a pdf (for example) in a specific location, but for one reason or another it can not find it.

I do admit that I am quite new to mediawiki (which clearly does not help), so even obvious things to check I might have missed. Tried to follow the manual, and as far as I can tell I did not miss any steps. I.E. I ran updateall, I ran reguildImages (had one unspecified issue with one image), tried rebuildAll as well, and it seems like it is finding what it wants, think it says 53 files rebuilt, the rest of the mediawiki works, its just the pictures that aren't there.

/Ben, 16 October 2014

That debug log is not helpful at all, because it's for the "/mediawiki/index.php/BO_Overview" page request, but it should be for /mediawiki/thumb.php (as I suggested on the previous message).

Ciencia Al Poder (talk)09:31, 16 October 2014

Thank you very much for that Ciencia, could I ask, is there somewhere I can see what the thumb.php call looks like or an example of one. Looked at ti but could not quite figure out how to make a call to do the debug on., 16 October 2014

OK, manage to find something, and one step forward (one step back?)

Ran it with a resolution that is to high, got Error generating thumbnail

Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?

Took it down to a lower resolution, then I got Error generating thumbnail

Error creating thumbnail: File missing

Also, have set the following in LocalSettings, but not seeing any debug information $wgShowExceptionDetails = true; $wgDebugToolbar = true; $wgShowDebug = true; $wgDevelopmentWarnings = true;, 16 October 2014

Manual:Thumb.php has an example call. You have to adapt it to your URL scheme (thumb.php is at the same location as index.php), and provide a valid filename from your wiki.

Did you manage to test that from your last error?

Ciencia Al Poder (talk)09:30, 17 October 2014
Edited by another user.
Last edit: 10:14, 18 October 2014

Hello Ciencia

Do you mean the section that goes

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^/?w/images/thumb/[0-9a-f]/[0-9a-f][0-9a-f]/[^/]+/[^/]+$ /w/thumb_handler.php [L,QSA]
# If your $wgHashedUploadDirectory is false, remove the first two steps after thumb/
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^/?w/images/thumb/archive/[0-9a-f]/[0-9a-f][0-9a-f]/[^/]+/[^/]+$ /w/thumb_handler.php [L,QSA]

If so, where would I put that, just as a new php file called test or?. I have tried running the following And I get the errors above. I also logged in as apache and tried changing files in that directory, and it definitely have full access., 17 October 2014

php error - file_get_contents

hi !

I get following error message in php_errors.log:

[21-Oct-2014 09:07:59 UTC] PHP Warning: file_get_contents(): Unable to find the wrapper "https" - did you forget to enable it when you configured PHP? in C:\mediawiki\extensions\SpamBlacklist\BaseBlacklist.php on line 273 [21-Oct-2014 09:07:59 UTC] PHP Warning: file_get_contents( failed to open stream: No such file or directory in C:\mediawiki\extensions\SpamBlacklist\BaseBlacklist.php on line 273

can someone help ?

reagards Jan :-), 21 October 2014

You may need to enable the PHP extension php_openssl.dll

Alternatively, replace all URLs on $wgSpamBlacklistFiles that have "https:" with "http:", or remove them

Ciencia Al Poder (talk)09:54, 21 October 2014


You should ask this question on Extension_talk:SpamBlacklist. SpamBlacklist wants to import some files from meta-wiki with a secure https connection. But it seems, that your webhost doesn't support this. So you should remove the s from https (so it's http:// only), which isn't really recommended, or you should ask your hoster to activate https as a wrapper.

Or: You copy the contents of into your local site MediaWiki:Spam-blacklist and add this site to

$wgSpamBlacklistFiles = array(
   "[[MediaWiki:Spam blacklist]]"
Florianschmidtwelzow (talk)09:56, 21 October 2014

problem to send email (smtp) to exchange server

Edited by another user.
Last edit: 09:50, 20 October 2014


I installed on my Win7 64bit machine Apache 2.4, php 5.6.0, mediawiki and the pear mail-packet. the mediawiki server only should be used in the company - not from the www and we used a Exchange-Server 2010.

I added into localsettings.php following parameter:

$wgSMTP = array(
 'host'     => "", // could also be an IP address. Where the SMTP server is located
 'IDHost'   => "",      // Generally this will be the domain name of your website (aka
 'port'     => 25,                 // Port to use when connecting to the SMTP server
 'auth'     => true,               // Should we use SMTP authentication (true or false)
 'username' => "",   // Username to use for SMTP authentication (if being used)
 #'username' => "",   // Username to use for SMTP authentication (if being used)
 'password' => "*******"       // Password to use for SMTP authentication (if being used)

we want that only the admin could create accounts ->

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

when I create a account I get the message: Fehler beim Senden der E-Mail(error by sending email) : authentication failure [SMTP: No supported authentication methods (code: 250, response: Hello [Ip-Adress] SIZE PIPELINING DSN ENHANCEDSTATUSCODES STARTTLS X-ANONYMOUSTLS AUTH NTLM X-EXPS GSSAPI NTLM 8BITMIME BINARYMIME CHUNKING XEXCH50 XRDST XSHADOW)]

my chef-admin try to send emails by telnet - there is no problem!

  • the main question is what are the correct parameters for $wgSMTP - is the username the name at the Exchange-Accout or the email-Adress ?
  • is it require to install a email-client on the server of mediawiki ?

on the other hand I found the tip to active the php-error-log. I add into localsettings.php following:

error_reporting( -1 );
ini_set( 'display_errors', 1 );

I look and see following message: PHP Deprecated: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in C:\PHP-5.6.0\pear\Net\SMTP.php on line 495

can anyone help me ?

it is the last problem on my way to our mediawiki. german answers could be understand better than English.

regards Jan

JanTappenbeck (talk)09:36, 20 October 2014

Pear-Mail has only support for a few authentication methods: Digest-MD5, CRAMMD5, LOGIN and PLAIN [1] and your server doesn't seem to support any of them.

Try to enable at least one of them on the server.

Ciencia Al Poder (talk)09:57, 20 October 2014
Edited by another user.
Last edit: 09:35, 21 October 2014

HI !

thanks for answer.

first i will add some parameter of php.ini i forget in the start-posting.

[mail function]
; For Win32 only.
SMTP = localhost
smtp_port = 25
; For Win32 only.
sendmail_from =
; For Unix only.  You may supply arguments as well (default: "sendmail -t -i").
;sendmail_path =
; Force the addition of the specified parameters to be passed as extra parameters
; to the sendmail binary. These parameters will always replace the value of
; the 5th parameter to mail(), even in safe mode.
;mail.force_extra_parameters =
; Add X-PHP-Originating-Script: that will include uid of the script followed by the filename
mail.add_x_header = On
; The path to a log file that will log all mail() calls. Log entries include
; the full path of the script, line number, To address and headers.
mail.log = c:\temp\mail.log
; Log mail to syslog (Event Log on Windows).
;mail.log = syslog

now to the answer....

sorry - but i did not understand the order.

is mixed Net_SMTP::auth ('', 'mypassword' , 'PLAIN' ) a parameter a had to add into php.ini .... or ??

regards Jan :-)

JanTappenbeck (talk)10:44, 20 October 2014

Ah, I think I didn't specify well where the problem is ;)

It's the mail server (exchange) the one that doesn't support Digest-MD5, CRAMMD5, LOGIN or PLAIN authentication options. Those are the only authentication options that PHP supports.

You don't need to change anything on PHP, because it will automatically choose one of the authentication option on that list (Digest-MD5, CRAMMD5, LOGIN or PLAIN), the first one that your mail server supports.

You have to enable at least one of those authentication mechanisms on MS Exchange to be able to send emails from PHP using that exchange server. Otherwise you'll have to use another mail server like gmail.

Ciencia Al Poder (talk)09:42, 21 October 2014

[RESOLVED] New install. No admin account.


I just did a new install of MediaWiki and cannot login. It is saying there is no such user yet I see it when I look in phpMyAdmin.

I tried to create a new user as well as making sure there was an email for the user I created so I could retrieve password however the password and email fields say "binary. do not edit" and only have a button to upload a file.

Please help me get into my wiki.

thanks in advance Lori G

Lorigreenberg (talk)23:30, 10 August 2013

Are you trying to login with the account you setup in the installation process or a MySQL account? Only the former will work.

In my experience, it never occured that the account you made in the installation process does not work, although I do know it's not an impossibility.

Jasper Deng (talk)00:06, 11 August 2013

I hate to admit that I don't remember setting one during installation so I went into my database through phpMyAdmin and saw that there was one user, which is a name that I would have chosen, so I tried to reset password with that username and it says the user does not exist. It will not let me do it manually in phpMyAdmin as that field says it's binary, do not edit and there is no field to type in a new password, or email, anyway.

I have also tried the MySQL database user names and they didn't work.

Lorigreenberg (talk)01:44, 11 August 2013

You don't remember the account details you initially set during the installation? There are a number of ways you could rectify this. If you have Extension:RenameUser, you could create a new account, assign it bureaucrat access (either by temporarily allowing all users to assign all user rights or doing so in the database), and rename off the old one.

Jasper Deng (talk)03:30, 11 August 2013

If it is a new install, the easiest would maybe be to delete the database contents, remove LocalSettings.php and then to start installation again. And then: Remember the username, please! ;-), 11 August 2013

Gotcha. Thanks. Usually I name things with someting I remember or write them down if I'm getting all fancy. I do not know what happened to me! Thanks for your help!

Lorigreenberg (talk)18:16, 11 August 2013

Image Thumbnail : Error creating thumbnail: '"/convert"' is not recognized as an internal or external command, operable program or batch file. Error code: 1

Edited by 2 users.
Last edit: 09:52, 17 October 2014

Morning everyone, I'm currently configuring a wiki for a project, everything seems to be working fine and mediawiki is great.

Only missing point that I'm facing is the image thumb-nailing not working =/

When I upload a file, I always get this error message in thumb section:

Error creating thumbnail: '"/convert"' is not recognized as an internal or external command, operable program or batch file.

Error code: 1

The setup:

  • Windows Server 2008 R2
  • XAMPP 1.8.3
  • MediaWiki 1.23.5
  • PHP 5.5.15 (apache2handler)
  • MySQL5.6.20

I've installed ImageMagick and it's working as environment variable. I used this release: ImageMagick-6.8.9-8-Q16-x64-dll.exe which installs everything (or not maybe) needed for windows running. The install dir is placed under ../extensions/ of MediaWiki just to be on the safe that htdocs can have access to convert command. But still i got the error.

[MediaWiki configuration] Under LocalSettings.php:

$wgUseImageMagick = true;
$wgImageMagickConvertCommand = '$IP/extensions/ImageMagick/convert.exe';

[PHP configuration]

php_imagick.dll must be added into php.ini? I can't find this dll extension.. on the imagick folder.

Anyway, It would be awesome if I could get this working, even if I got to install other extensions to render thumbs... The option of disabling thumbnails works as plan b

Many thanks in advance

Wbr, Sam

Samuel Matildes (talk)07:57, 17 October 2014

It's strange, it's like it doesn't recognize the setting Manual:$wgImageMagickConvertCommand and it's using the default (because it doesn't say "convert.exe" in the error message).

Check that you haven't mispelled the variable name and that you're editing the correct LocalSettings.php

Ciencia Al Poder (talk)09:56, 17 October 2014

PHP only escapes variables within double quotes, not single ones. Try replacing:

$wgImageMagickConvertCommand = '$IP/extensions/ImageMagick/convert.exe';


$wgImageMagickConvertCommand = "$IP/extensions/ImageMagick/convert.exe";
Ricordisamoa06:39, 19 October 2014


I've replaced the quotes with double quotes...and the results are the same. Is there any workaround for this?

Many thanks in advance,

Wbr, Sam

Samuel Matildes (talk)07:12, 21 October 2014

Blanc Page after MediaWiki Update 1.23.5 to 1.24

I have an Ubuntu Server with MySQL and Apache.

I've first updated my wiki from 1.23alpha to 1.23.5. Everything was fine.

Then I've updated from 1.23.5 to 1.24 and I get blanc pages. Everything is blanc. Source code of the Website is also empty.

My error log shows:

PHP Warning:  require(/var/www/includes/WebStart.php): failed to open stream: 
No such file or directory in /var/www/mywikifolder/index.php on line 36


PHP Fatal error:  require(): Failed opening required '/var/www/includes/WebStart.php' 
(include_path='.:/usr/share/php:/usr/share/pear') in /var/www/mywikifolder/index.php on line 36

I've applied chmod 755 to WebStart.php with no change

After that also chmod 755 -R to includes folder with no change

What do I have to do?

What does this mean:

Sadd (talk)21:03, 20 October 2014

It's looking for the files in the wrong place. Do you have some kind of weird symlinks or aliases set up?

Jackmcbarn (talk)21:09, 20 October 2014

I did nothing special. Just a standard installation.

Sadd (talk)21:19, 20 October 2014

What I do not understand is how you have set up your wiki:

The central index.php file is located at /var/www/mywikifolder/index.php. Then WebStart.php must be available at /var/www/mywikifolder/includes/WebStart.php and this is the location, which MediaWiki should look for this file. However, in your case, this is not where MediaWiki tries to find the file. Instead, it looks at /var/www/includes/WebStart.php. And that is wrong., 20 October 2014

Ok, I didn't see that it looks in the wrong folder. Thank you for that.

But it worked for 1.23.5 somehow. Where do I have to set which variable, so it looks in the correct location for the WebStart.php?

Sadd (talk)22:15, 20 October 2014

Wiki hacked for info

One private wiki used for one customer for collaboration was hacked using special:userlogin twice. Not sure how that works. The hacker went directly to a project category, downloaded a bunch of files. This was obviously someone very familiar with Mediawiki, no kiddie script.

I have not yet found in the log files where this happened yet, but the hacker deleted all the data base entries after 9/9/2013. I did not this this was easily done.

Any help or insight would be appreciated.

Rev 1.19.2 PHP 5.3.24 MySQL 5.0.96-log

Thanks, Don

Dcshank (talk)16:04, 20 October 2014

Please follow Manual:Security. Especially do not disclose details about the hack to the public (including myself).

Note that your MediaWIki version is outdated and has known security holes. Given that there are quite a number of known security related issues in the version you used, which might give an attacker possibilities to manipulate files on the server, I guess it's unlikely that a yet unknown zero-day exploit has been used. Anyway, you cannot be sure about that until you figured out how the attack actually worked., 20 October 2014

Thanks very much for the advice Special:userlogin has been discussed as a problem for a while.

I understand the version is outdated and every version is going to have security holes. Unfortunately any MediaWiki version is outdated the day after it is released. And, since the MediaWiki is not exactly Windows Notepad, I am not going to be doing a Tuesday Windows type update every week.

I have to take a stand at some point and work with what I have until there is a compelling reason to upgrade. I have taken care of the problem for now. I just never expected anyone to go to so much effort to get the trivial information that was taken. I'm anxious to take the time to figure out the hack, but more important thing press at this time

The horrible thing is wiping the DB. I am assuming the image and page files still exist on the server. Is there any utility existing that would rebuild a useful index?

Dcshank (talk)17:55, 20 October 2014

MediaWiki minor updates come out around once a month - or less frequently. For me personally it takes less than five minutes to install such an update. Your current situation proves that security is a compelling reason to update. Not updating, knowing of the dangers, is negligent, if not grossly negligent.

You wrote that the hacker removed "all db entries after 9/9/2013". Content from the tables page, revision and text is unique. Content from these tables (page, revisions, text) cannot be rebuilt. Maybe from Google cache, but you know - that is not, what you want to do. Having a backup would be fine...

You can put those images, which are now missing in the DB, into a folder. Then these images can be imported using the maintenance script importImages.php., 20 October 2014

1.19 is still supported. I'm hoping that you meant 1.19.20 rather than 1.19.2; if not, then that would probably be how you got hacked. "Unfortunately any MediaWiki version is outdated the day after it is released." <-- That isn't true. Releases, especially LTS, are relatively rare. "I have to take a stand at some point and work with what I have until there is a compelling reason to upgrade." <-- Security vulnerabilities are a pretty compelling reason to upgrade. Also, why do you think Special:UserLogin was involved in the hack, and what does "went directly to a project category, downloaded a bunch of files" mean?

Jackmcbarn (talk)21:14, 20 October 2014

A MediaWiki version isn't outdated the next day. See Version_lifecycle to know, how our version lifecycle works. Normally you should use always the latest stable version of MediaWiki, but there are some LTS versions, which get security fixes, too. There should be no problem (and in your own interest) to upgrade/use some of the supported versions of MediaWiki.

Weekly snapshoots of MediaWiki (called wmf-branches) are thought for Wikimedia wikis use only (like Wikipedia and sister projects). You can, if you want, use these versions, too, to get the newest changes, which are mainly untested for environments outside the wikimedia use. So you have to be very familar with MediaWiki, to know what to do, if something went wrong.

Florianschmidtwelzow (talk)21:19, 20 October 2014

Thanks for all your input. Don't take things I say too literally. Of course it not outdated the next day, but we all know the nature of software. I can't disagree with most of it, but like probably most everyone else here, there are never enough hours in the day to do everything that should be done. My primary job is not maintaining the server and websites, and I cannot afford to hire someone to do that full-time, which is what would be required to keep everything pristine.

I figured out most of what happened, still working the issue. I have tried some things, and will see how they look in the log file tomorrow. I have tried to upgrade but there is some kind of bug at GoDaddy that will not allow it, and I have not had time to work on it. And, several upgrades that required MySQL changes took a lot longer than 5 minutes.

Thanks for your help. I have learned a lot, my customer and I will be discussing things.

Dcshank (talk)21:48, 20 October 2014

XCache var cache was not initialized properly

Edited by another user.
Last edit: 00:33, 6 February 2013

I have changed the xcache.var_size to 500 from 100, but nothing changed.

The error below comes up whenever I run any script, i.e. runjobs or even showjobs. Does anybody else have similar experience with xcache? Which is the recommended accelerator for mediawiki? Is it possible to disable xcache in localsettings.php for testing purposes?

  • MW 1.16.5
  • Apache version 2.2.23
  • PHP version 5.3.21
  • MySQL version 5.1.66-cll
Warning: xcache_get(): XCache var cache was not initialized properly. Check php log for actual reason in .../includes/BagOStuff.php on line 552
Warning: xcache_set(): XCache var cache was not initialized properly. Check php log for actual reason in ...includes/BagOStuff.php on line 567
Spiros71 (talk)22:44, 5 February 2013

First, I would recommend that you upgrade to at least 1.19.3 -- you'll get bug fixes and 1.19 is supported until 2015.

APC is the recommended PHP cache.

MarkAHershberger(talk)00:37, 6 February 2013

Did you try setting the variable to 100M?

Bawolff (talk)18:19, 6 February 2013

The issue persists with MW 1.23.5 and XCache 3.0.3. Bawolff, thanks, I am not sure what you mean with 100M? Just add "100M"? That is what it was initially :)

Spiros71 (talk)14:48, 20 October 2014

How to remove a file? I accidentally put file:Stelvio1 and then after realized that the picture could be inserted by editing. I would like to remove the file. Could you tell me how and in detail, please?

First1vip (talk)14:36, 20 October 2014

The page you linked has already been deleted. Which file do you want to have deleted? does not exist..., 20 October 2014

backup mediawiki - image etc.

hi !

is export the mysql-database enought for a good backup - what is with the image? include the sql-export?

regards Jan :-)

JanTappenbeck (talk)12:04, 20 October 2014

You will need the database and the files of the installation. For the database, using mysqldump is the standard way of creating a DB backup. The files can e.g. be tar'ed into an archive.

See Manual:Backing_up_a_wiki for more information!, 20 October 2014

How to install MediaWiki Version 1.23.5?

  • XAMPP 1.8.3
  • MediaWiki Version 1.23.5
  • PHP Version 5.5.15
  • Database MySQL Version 5.6.20

Hello, I've downloaded XAMPP and get an error when I try to install MediaWiki Version 1.23.5. It requires a password for connection to the database with the user 'root' because it isn't safe without a password. I thought MediaWiki creates the database by itself and sets the password?!?, 18 October 2014

> I thought MediaWiki creates the database by itself

No, it will create the tables into the database, that's why it needs the password ;)

> and sets the password?!?

No :) The user has to be created for MediaWiki (with a password). With this credentials, MediaWiki will create the tables into an existing database (you have to create this database, too). For this you can use phpMyAdmin (should be included in XAMPP).

Florianschmidtwelzow (talk)21:59, 18 October 2014

Thank you! It wasn't that tricky in previous versions., 19 October 2014

That's not correct. Mediawiki can create both the user and the database. When you follow the installation script, there's one step where you can provide privileged mysql account credentials and also credentials for the database user MediaWiki will use, so it can create the database and create the user with the necessary privileges. If you don't provide the privileged user, MediaWiki will assume the database and the user already exist.

Ciencia Al Poder (talk)09:43, 20 October 2014

That's what i mean, but for this you need an initial database user with the privileges to do that :)

Florianschmidtwelzow (talk)10:45, 20 October 2014

[RESOLVED]cookies error message during connection to wiki

Edited by another user.
Last edit: 00:09, 20 October 2014


to prevent acces to my mediawiki server, I create a form requiring the login to server and I check the answer according to values saved into a DB table created with phymyadmin Now, before to run the mediawiki object the form is displayed

to perform this , I modified the index.php as following

 header('Content-Type: text/html; charset=UTF-8');
 if ( !function_exists( 'version_compare' ) || version_compare( phpversion(), '5.3.2' ) < 0 ) {
	// We need to use dirname( __FILE__ ) here cause __DIR__ is PHP5.3+
	require dirname( __FILE__ ) . '/includes/PHPVersionError.php';
	wfPHPVersionError( 'index.php' );
 if (isset($_SESSION['Acces']) && ($_SESSION['Acces']==false)){
      echo "<center><h2><font color='red'>Incorrect Login</font></h2><center>"; }
  if (isset($_SESSION['Acces']) && ($_SESSION['Acces'])){
     require __DIR__ . '/includes/WebStart.php'; 
     $mediaWiki = new MediaWiki();
  else { 
       <form action ="checkForm.php" method="post">
       <b>identifiant : </b><input type="text" name="inputlogin" size="30"> <br />
       <b>password : </b><input type="password" name="inputpwd" size="30"> <br />
           <div class="action">
           <input type="submit" class="btn primary" value="Valider">

and I create a checkForm.php as following

error_reporting(E_ALL & ~E_NOTICE);
 $_SESSION['mytwikiLog'] = $_POST['inputlogin'];
 $_SESSION['mywikiPwd'] = sha1($_POST['inputpwd']);
 $connect = mysqli_connect("localhost","root","rootpass","myDB") or die('error BD connect');
 $query = 'SELECT * FROM myTable' ;
 $result = mysqli_query($connect,$query) or die('Table error') ;
  while($row = mysqli_fetch_row($result)){
    if ( ($_SESSION['mywikiLog']==$row[1]) && ($_SESSION['mywikiPwd']==$row[2]) ){
    else {

But Now when I want to enter my connect login to the mediawiki The login is performed but I always have the two messages (brown and pink)

  • 'userlogin-loggedin' : you are already logged in as .... use the form below to ogin an another user
  • 'nocookieslogin' : SITENAME uses cookies to login users. You have cookies disabled. Please enabe them and try again

but I am corectly connect to the wiki and my cookies are activated


Please coud you help me great thanks, 17 October 2014

Ehhh, please Do not hack MediaWiki core :) It's really not the best solution, what you are doing. MediaWiki itself should handle session initialization and all other stuff, so i think, that your problem is somewhere in your implementation.

For what i understand, what you want to reach its much better to use the MediaWiki-built in functions. So why not require login for users in order to read/access the content in your wiki?

If you really want to have a pre-login login, then maybe it's better to use .htaccess login, instead of the above code.

Last, but not least, if you really want to have a pre-login form with your own stuff, you should read, how to implement Extensions in MediaWiki. I think it would be much better to use one (or more) of MediaWikis hooks to break in to MediaWiki's page creation process.

Florianschmidtwelzow (talk)21:57, 18 October 2014

Before I protected all the serveur access with a .htaccess .htpassword but the form which was displayed are different according to the navigators and the access text was limited (no possibiity to add one image in background !)

So, it was requested to me to make a pre-login login form

because it is a private wiki we want "accueil page" should be accessible only when this pre-login is validated

Is existing an extension to perform that : I don't find it

After entering into the wiki: Ok the user right are correctly configurated with the localsetting (the anonymous can read but not write..., the extension confirmAccount is installed to accept only any users ....)

manage one hook is not clear for me : where can I find an exemple of pre-login form which run the mediawiki ony if the prelogin is correct ?

Thanks for your help, 19 October 2014

Delete checkForm.php and put index.php back to normal. Add $wgGroupPermissions['*']['read'] = false; to your LocalSettings.php. Everything will work right with just the regular login then.

Jackmcbarn (talk)20:57, 19 October 2014

[RESOLVED] Image gallery slider

Hello all,
I use Mediawiki v.1.20.6
On one wiki site I saw a useful template which makes a images slider:
I tried to make the same and copied the template, but it does not work at all (((:

Could you please tell me if there is a solution to fix the template to make it working? Or are the any other templates or extensions like this one?

Fokebox (talk)19:40, 19 October 2014

You need JavaScript to make that work. They posted it at

Jackmcbarn (talk)20:51, 19 October 2014

Thx, yes it started to work, but there are two extra buttons appeared on the top that should be hidden, any solution on this?

Fokebox (talk)03:44, 20 October 2014

Note, that MediaWiki 1.20 isn't supported anymore. As a side note. You may want to upgrade to at least MediaWiki 1.22.x, or better to the last stable release MediaWiki 1.23.5.

Florianschmidtwelzow (talk)05:18, 20 October 2014

Additional question - are there some other templates / extensions with the same functionality?

Fokebox (talk)06:33, 20 October 2014

The thread can be closed ))) I decided my own template with jquery image slider … at least I will try )

Fokebox (talk)08:26, 20 October 2014

Disable dynamic redirects so that URL is correct?

How can I disable the dynamic redirects? I want the target to read the proper URL.

Subfader (talk)12:18, 19 October 2014

Could you please elaborate?

Ciencia Al Poder (talk)09:44, 20 October 2014

[RESOLVED] MediaWiki don't work with PCRE 8.34

I was running MediaWiki 1.20.8 with no problems. Then after upgrading PCRE from version 8.33 to 8.34, the content on most of the pages in my MediaWiki site does not display, only empty pages without content. Then I upgraded to MediaWIki 1.22.0, but the same problem still exist there.

The Apache Error Log shows many lines like this (note there is different line numbers in the errors, so its not only line number 902 like in this example) (I have changed the domain name and user name and ip from the error):

[Wed Dec 18 14:07:46.351691 2013] [:error] [pid 8193] [client] PHP Warning: preg_match(): Compilation failed: group name must start with a non-digit at offset 8 in /home/xxx/domains/ on line 907, referer: http://

Then I look at PCRE 8.34 changelog at wich says this:

"Perl no longer allows group names to start with digits, so I have made this change also in PCRE."

Please look into this and make MediaWiki compatible with newest PCRE 8.34

Also, please help me about what changes I need to do in order to patch this problem manually in MagicWord.php, so that I don't have to downgrade PCRE, please help., 18 December 2013

Thanks for the very good problem description!

I have just checked the bugtracker and here already is an issue about this problem:

Please add your findings there, especially this:

Then I look at PCRE 8.34 changelog at wich says this:
"Perl no longer allows group names to start with digits, so I have made this change also in PCRE.", 18 December 2013

The patch on the link above and running php update.php fixed this issue for me. Thanks for directing us to the correct place.

LTech (talk)08:09, 20 October 2014
First page
First page
Previous page
Previous page
Last page
Last page