Manual:Common errors and symptoms/nl



U ziet een lege pagina
Bij een lege pagina is er meestal een fout in PHP opgetreden, die foutmelding wordt niet getoond. Om die foutmelding wel te tonen, voeg de volgende regels toe aan het bestand  onder de  :

U kunt ook een waarde voor  zetten in   en in de PHP-log zoeken naar wat er fout gaat. Soms staat een PHP-fout ook in de webserver-log.

Een foutrapport kan bevatten:


 * "Warning [...] It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set function." Check if  is set correctly (or set at all) in.
 * Certain files may be reported as missing (e.g. when the  folder in your   folder is no longer present, you may receive the message that a required imaging process "failed to open stream"). Check the original installation package at MediaWiki (make sure to consult the appropriate version) to see if this is the case. If so, simply copy the missing files from the package into your MediaWiki directory. It may be necessary to refresh the cache and restart the webserver afterwards.
 * MySQL socket cannot be found. If  is set to the correct MySQL socket but   is not, it may result in a blank screen with no error output from the webserver or php. The fix is to update the   entry in the   file.

Veel mensen hebben aangegeven dat ze een lege pagina kregen in een recent geïnstalleerde versie van de wiki na het toevoegen van een artikel. Een waarschijnlijke oorzaak in de geheugenlimiet in de standaard php-installatie (meestal 8 MB). Controleer a.u.b. de logbestanden van PHP en/of de webserver (Apache). Om deze instelling aan te passen, wijzig  en verhoog de instelling "memory_limit". Zet het bijvoorbeeld op 32 MB, vervang de bestaande tekst door. Herstart de webserver na het doen van deze wijziging.

De limiet kan ook in uw bestand  zijn gezet. Zoek naar de regel met de instelling memory_limit en verhoog de waarde. 20M kan te laag zijn als u versie 1.15.1 heeft. Wijzig het naar bijvoorbeeld " ". Na deze wijziging hoeft u de webserver niet te herstarten.

Als de pagina enige tijd blijft hangen bij het laden (zeg 30 seconden) bij een specifieke actie, en u daarna een lege pagina te zien krijgt of een 'HTTP 500 error', dan is het probleem waarschijnlijk een time-out van de verbinding. Dit kan de database-server zijn of het gebeurt bij een specifieke actie, de mail-server (als u de instellingen voor e-mail heeft geconfigureerd). Als het de e-mailserver is, controleer dan of u ermee kunt verbinden vanaf de server waar MediaWiki op draait, bijvoorbeeld, het uitvoeren van de Telnet cliënt naar de server en poort geconfigureerd op, kijk of de connectie gemaakt kan worden.

Als u de inhoud van de pagina kort kunt zien voordat de pagina leeg wordt, dan wordt het probleem mogelijk veroorzaakt door de aanwezigheid van een,   of   JavaScript in een van de scripts van de  wiki. U kunt dat controleren door het browserconsole te openen (met F12) en de pagina te herladen. Als de tab netwerk een HTTP 200 status toont, en de transfer is van een paar kilobytes, dan is dat waarschijnlijk de oorzaak. Dit zij verouderde methoden van de  interface die veroorzaken dat de hele pagina leeg wordt als het buiten de HTML van de pagina wordt gebruikt, het kan aanwezig zijn op de wiki's JavaScript pagina's. Het gebruik ervan wordt sterk afgeraden, zoals aangegeven in de HTML specificatie. U kunt JavaScript uitschakelen in uw webbrowser, of en  op 'false' zetten om die scripts uit te schakelen totdat u de fout in de scripts heeft hersteld. 

Fouten in MediaWiki


Alle pagina's hebben geen inhoud, maar wel wikitekst bij het bewerken van de pagina
Eventueel met foutmeldingen als:

PHP Warning: preg_replace: Compilation failed: group name must start with a  non-digit at offset 4 in /var/www/wiki/htdocs/includes/MagicWord.php

Dit wordt veroorzaakt door een wijziging in PCRE 8.34, die niet langer namen van 'capturing' groepen toestaat die met een cijfer beginnen. U moet de MediaWiki bijwerken naar een ondersteunde versie. Zie. Het probleem is opgelost in alle nu ondersteunde versies van MediaWiki.

Zie rapport: Topic:Rz2zo0m88rrxqrfn, Thread:Project:Support desk/MediaWiki don't work with PCRE 8.34 (2)



Miniaturen van afbeeldingen werken niet of worden niet getoond
Hier noemen we de problemen en de oplossingen bij het niet kunnen maken van een miniatuur of het niet kunnen tonen.

Error creating thumbnail: File missing:
Dit kan komen door verkeerde waarden in de globale variabelen zoals uitgelegd in:

Decimal-point in srcset locale bug
If image thumbnails simply don't appear, and there's no error visible on those pages, look at the HTML source of the page and search for " ". If you find something like, where it appears   instead of  , the problem is caused by , and you should add this to LocalSettings.php:

Be sure there's no defined in your LocalSettings.php, or add also this:

SVG

 * Zie ook: 

First, determine your setting. Standaard wordt ingesteld dat voor de conversie ImageMagick wordt gebruikt.



Gebruik ImageMagick
U heeft minimaal versie 6.x.x nodig van ImageMagick. Ensure that your variable is valid. Normale instellingen zijn:

If it does not work, try setting.

Gedeelde hosts kunnen verschillende versies van ImageMagick hebben. Gebruik a.u.b. versie 6.x.x.


 * To determine the version of ImageMagick, search the help files of your host provider, or use  or   to detect.
 * On GoDaddy Linux shared hosts, "/usr/bin/convert" for Version 5.5.6 and "/usr/local/bin/convert" for Version 6.2.8.

If generating thumbnails with ImageMagick fails with a web server error log message like "Memory allocation failed" or "/bin/ulimit4.sh: Segmentation fault /usr/bin/convert ...", the value may need to be increased.

Als het pad geen non-ASCII tekens bevat


 * Check if UTF-8 locals are available on your server by running
 * When it's not available run  or put in the locales with UTF-8 for your country and change the value for  accoring to this

When using IIS/FastCGI on Windows, the guest account that is used also needs execute permission on %SYSTEMROOT%\System32\cmd.exe otherwise you'll receive an "Unable to Fork" error.



Gebruik Batik
MediaWiki gebruikt limieten voor tijd en geheugen bij shell commando's in Linux. If you receive the error "Error occurred during initialization of VM, Could not reserve enough space for object heap, Could not create the Java virtual machine.", try increasing the value of.



Gebruik rsvg
Op enkele Linux en BSD installaties is rsvg is hernoemd:

Instead of setting (default) you would like to set

JPEG
Symptoom: Deze foutmelding in een grijs veld:


 * Error creating thumbnail: Invalid thumbnail parameters

One cause: the number of pixels in the original image exceeding. De standaardwaarde 1.25e7 is te klein voor veel moderne camera's. Helaas geeft de foutopsporing niet het probleem aan.

You can increase the value of or switch to using ImageMagick which evades this restriction (set  and ).

Het verwerken van grote afbeeldingen kan even duren. Het is goed om het formaat van de afbeeldingen te bepalen.



JPEG (via GD)
Symptoom: Deze foutmelding in een grijs veld:


 * Error creating thumbnail: Incomplete GD library configuration: missing function imagecreatefromjpeg

Some PHP 4.x and 5.x versions of PHP have a bug where the libjpeg is detected but not enabled during the  step; this is fairly prevalent on Red Hat/RHEL/CentOS systems. De oplossing is (als u geen ImageMagick gebruikt) om PHP opnieuw te compileren. Bekijk eerst wat (van ) de bestaande  switches zijn, voeg   toe voor.

Herstart daarna de webserver (voor Apache op Red Hat:  dan   ).Om te testen, bekijk opnieuw het bestand:... (Opnieuw uploaden is niet nodig). Voor meer informatie, bekijk de opmerkingen bij PHP: imagecreatefromjpeg



De miniaturen kunnen niet worden opgeslagen
If you get the error "Error generating thumbnail / Error creating thumbnail: Unable to save thumbnail to destination" and the directory has the correct permissions (at all levels), check that  actually exists. (Unlike some path variables such as, $wgTmpDirectory is not created at runtime.) A more detailed error message may be available if you turn on logging with.

This error can also occur when read only mode has been set in. You can try to remove  to see if that solves the issue for you.



Fout (25) bij aanmaken miniatuur
If you get "Error creating thumbnail Error code: 25" with ImageMagick, try increasing.



Handmatig miniaturen toevoegen
In situations in which it's not feasible to create the thumbnails dynamically on request (e.g. for very large images, "Error creating thumbnail: unable to extend cache", "Error creating thumbnail: convert: no images defined", and similar), it is possible to manually add the thumbnail files. This involves creating the smaller images in the desired sizes and uploading them to the  directory in.

For example, a file that has uploaded to:

images/f/f8/Foo.png

should have its thumbnails at:

images/thumb/f/f8/Foo.png/100px-Foo.png images/thumb/f/f8/Foo.png/600px-Foo.png

De pixelgrootte is de horizontale dimensie. An example Bash script for creating thumbnails is available at P7049.



Fout (-1) bij aanmaken miniatuur op OVH gedeelde hosting
Door een onbekende oorzaak krijg men bij het aanmaken van miniaturen op enkele gewijzigde OVH hosting deze fout, ook al werkt het uitvoeren van het commando in de SSH shell wel.

Solution is to specifically prevent from using ImageMagick by setting to false in LocalSettings.php:

Sorry! We could not process your edit due to a loss of session data. Please try again. If it still doesn't work, try logging out and logging back in.
See Manual:How to debug/Login problems.



Inhoud limieten
If your Apache server has the Hardened PHP patch, you may need to edit several variables in your /etc/php.ini file if you wish to have wiki pages with large amounts of content. Bekijk de instellingen, vooral,   en. De standaardinstellingen kunnen uw pagina beperken to minder dan 10k of 64k in grootte.

Another possibility is if your Apache server is using mod_security that could be interfering with MediaWiki. Om MediaWiki goed te laten werken, kunt u dit uitschakelen.

You have not specified a valid user name / Completely blank page edits and previews / Unable to upload
Dit wordt veroorzaakt door het afkappen of verlies van POST-data van de webbrowser naar de webserver.

In minstens een geval werd dit veroorzaakt doordat  en   te hoog waren gezet (2048M) in php.ini. Door ze terug te zetten op redelijke waarden (8M) was het probleem opgelost. Het leek er op dat er geen POST-data op de MediaWiki terecht kwam.

In een ander geval verstoorde mod_auth_sspi de http-posts naar MediaWiki. Gebruik van FireFox en het invoeren van de 'domain credentials' zou goed werken maar MSIE (Internet Explorer) zou niet werken. Dit is een bekend probleem in mod_auth_sspi 1.0.4.

Er zijn opties om het te laten werken:


 * Set SSPIOfferSSPI off &larr; users will get prompted and have to enter domain credentials, same as BASIC mode
 * Set SSPIPerRequestAuth on &larr; I don't see how this is a healthy configuration but it worked (except over the high latency connection I'm forced to contend with)
 * Downgrade to 1.0.3 but it's basically the same as #2 above.



De wiki lijkt geen toegepaste stijlen te hebben en de afbeeldingen ontbreken
Als de wiki er goed uitziet als je op dezelfde server zit als waar de wiki opstaat, maar de CSS lijkt te ontbreken (geen kleur, geen achtergrond, geen afbeeldingen, erg weinig opmaak, enz) als je het vanaf andere plekken benaderd, dat is het meest waarschijnlijke dat de server de IP of de hostnaam niet kan bepalen die wordt gebruikt om het te benaderen of het is verkeerd ingesteld. Hierdoor gaan URL's de stylen en afbeeldingen zoeken met het IP-adres waarop ze terugvallen 127.0.0.1, dat is de localhost of een hostnaam die niet buiten de server bekend is. U kunt de broncode zien van elke pagina en kijken hoe de URL's er uit zien en wat er gebeurt als u ze direct via de webbrowser probeert te benaderen.

De oplossing is om handmatig de variabele te specificeren op de hostnaam die iedereen gebruikt om de wiki te benaderen.

Als de wiki wordt benaderd via een intern en een extern netwerk, dan moet u mogelijk het externe adres gebruiken voor. Vergeet niet de poort als u een niet-standaard poort gebruikt, voor het geval uw ISP de poort 80 heeft geblokkeerd (Voorbeeld: )

If styles aren't applied even when browsing the wiki from the server where it's hosted, the problem may be a PHP error on the   script. Try to browse the load.php file of your MediaWiki installation with your web browser and see if it displays any errors or just a blank page (see #You see a Blank Page). You should see a comment similar to. If so, it may be a problem with the web server's  file.

If you instead see a 404 Not found error, it may be a problem with the web server's rewrite rules if you attempted to configure Short URLs.

If you're getting 500 error responses from load.php urls, check the webserver's error log files to get more information of the errors. There seems to be a problem with some PHP versions and Gentoo that causes Apache to segfault. This can also happen if you have APC enabled, setting  in php.ini might help.

Since MediaWiki 1.23, you may end with a wiki with most of the Vector-specific skin styles, like sidebar placed at the end of the page. That may be caused by a low set up on some distributions like FreeBSD. It's known to have problems with values of 10000. Increase that value to 100000, or the current default of 1000000.

Since MediaWiki 1.26, some skins, and specially Vector, may have this problem. If you see the error Internal error Problematic modules: {"startup":"error"} in the error console of your browser, most likely cause is the lack of permissions of MediaWiki to write to the default temp folder, either because PHP has no permissions to write to  (  on Windows), or because there's an  restriction and that path isn't included on it. See. You can also set if you're unable to change permissions on the system's default temp directory.

Error: invalid magic word 'speciale'
If you get that error message after upgrading, you must run the maintenance script with the   option:

php rebuildLocalisationCache.php --force

This can happen at least upgrading to 1.20.



Werkbalk voor bewerken ontbreekt, JavaScript werkt niet
If JavaScript is not working (one of the symptoms is the edit toolbar not appearing when editing a page) it may be caused by a JavaScript error. Open the error console of your web browser (usually by hitting F12 ), reload the page and see if any error message appears there. If it displays an error, usually, setting would give you more information. Sometimes the problem is that the system's temp directory is not writable. In that case, you can also set if you're unable to change permissions on the system's default temp directory.

If you get errors like  or , the cause is usually a hosting provider that is automatically injecting HTML code for tracking or advertising inside the  script, which is used by ResourceLoader to load the scripts and CSS used by MediaWiki. Open a support ticket with your hosting provider asking them to disable that injection. If that's not possible, you should migrate your site to another hosting provider. That usually happens on free hosting providers.



Elke pagina toont een fatale fout, in de Log staat meldingen als: "MagicWordArray::parseMatch: parameter not found"
Try rebuilding the Localisation Cache:

php maintenance/rebuildLocalisationCache.php

From this thread.

<span id="All_uploads_fail_with_the_message_&quot;The_file_you_uploaded_seems_to_be_empty...&quot;">

Alle uploads mislukken, goutmelding: "The file you uploaded seems to be empty..."
It may be caused by wrong rewrite rules when configuring Short URLs. Try disabling them (and the related configuration variables of MediaWiki) to see if that solves the problem.

Another problem may be a limit imposed by the web server about how many data the server can receive on a single request. See Manual:Configuring file uploads for some configuration variables. If you have mod_security or suhosin installed, they may also be limiting the size of uploaded files, discarding the upload entirely without PHP noticing it.

Check also the configuration directive from php.ini, and be sure that the folder has proper write permissions for the user account running PHP. On Windows, this directive often points to, which may not be accessible in some circumstances. In that case, you can set up a different temp folder like C:\TEMP\ with proper permissions. To discard other problems, give temporarily all permissions to that folder (on Windows, add the local user group "Everyone" with full permissions), and then restrict the permissions as needed once you verify uploads are working.

If all uploads fail with the message "", and in the apache error logs you have entries like this:

Notice: Undefined index: tmp_name in /srv/www/htdocs/mediawiki/includes/WebRequest.php on line 1153 Notice: Undefined index: size in /srv/www/htdocs/mediawiki/includes/WebRequest.php on line 1140 Notice: Undefined index: error in /srv/www/htdocs/mediawiki/includes/WebRequest.php on line 1167

This is a problem with the PHP version your server is using. There have been several reports of this problem with PHP 5.3.8 on SLES11 sp2. You may need to upgrade PHP or recompile it yourself.

<span id="WAMP/Apache_on_Windows:_Some_Special:_pages_are_inaccessible">

WAMP/Apache op Windows: Enkele speciale pagina's zijn niet toegankelijk
It may happen, on windows installations under Apache, that some Special pages are inaccessible, giving a error, and in the logs you can see something like this:

[core:error] The given path is misformatted or contained invalid characters: [client 127.0.0.1] AH00127: Cannot map GET /wiki/Special:SpecialPages HTTP/1.1 to file

This can be caused by various PHP bugs. One of them is when the wiki is installed in a NTFS junction. If that's not the problem, upgrading PHP to a newer version can help (see this forum thread)

<span id="Attempting_to_save_an_edit_gives_you_a_403_Forbidden_error,_or_you_get_redirected_to_the_main_page">

Bij het opslaan van een wijziging een '403 Forbidden error' of u gaat naar de hoofdpagina
This is a common issue for shared host which have  enabled. To know if it's a problem with mod_security or not, create a simple test page and save it with a small text (something as simple as writing just a dot in the content). If the edit is saved, but other edits aren't, that's caused by mod_security. Ask your hosting customer support to disable it completely or the rules affecting your edits.

If even saving a very simple edit gets you redirected to the main page, or to the same page without the edit appearing, it may be a problem with how you've set up or some other configuration variable that controls the path of the index.php script, or conflicts with rewrite rules in your webserver's configuration.

<span id="Login_page_warns_about_cookies_disabled">

Op de inlog-pagina een melding dat de cookies zijn uitgeschakeld
You may get a message like.

If cookies aren't disabled on your browser, it could be one of those problems:


 * You have set to true but MediaWiki can't connect to memcached. Turn off this setting or check the memcached configuration.
 * A wrong cookie configuration. Configuration variables about cookies should work with their default values. Try to not override any of them.
 * is not set correctly on the server, or the server doesn't have permissions to write to that path.
 * If you use some sort of caching proxy in front of MediaWiki, check that it doesn't filter any cookie.
 * is wrongly set. You should normally leave it empty.

Setting a debug log should display any cookie received by MediaWiki, so it may be a first step to detect if cookies are actually received by MediaWiki or not.

<span id="MediaWiki_does_not_function_when_magic_quotes_are_enabled">

MediaWiki werkt niet wanneer 'magic quotes' zijn ingeschakeld
Magic quotes is a feature in PHP that was deprecated in PHP 5.3 and removed in PHP 5.4. If you get this error, you need to disable the magic quotes in your server setting. See how to do it. Since MW 1.24.

Discussions: Thread:Project:Support_desk/Problems_with_installing_mediawiki, Topic:S79xdn9u15xw55vj, Topic:Sdpbmy9q9e0ttp6k, Topic:S7g4rybniat2i36e, Topic:S6vqwk0tysl6m8lc

<span id="Error_creating_thumbnail:_File_with_dimensions_greater_than_12.5_MP">

Fout bij aanmaken miniatuur: File with dimensions greater than 12.5 MP
It may help to increase to get rid of the problem (tried with MediaWiki 1.26.2).

<span id="Internal_Server_Error_when_opening_any_image">

Internal Server Error bij het openen van elke afbeelding
If images are not displayed on the pages, and manually opening the URL of any image results in an Internal Server Error page, the problem is most likely caused by the  file from the   directory. This configuration file contains some rewrite rules to prevent old Internet Explorer versions from being affected by a cross site scripting vulnerability. However, some hosts like strato.de prevents disallow the  directive in .htaccess, causing any request for a file in the images folder to fail with an error. If you can't enable rewrite rules on .htaccess file, you may need to comment-out or remove those lines from .htaccess, or the entire .htaccess altogether. See Topic:Uye1450mvn00f4y1.

<span id="Category_pages,_Special:Whatlinkshere_and_file_usage_aren&#039;t_being_updated">

Categorie pagina's, Speciale pagina met wat linkt hier na toe en bestandsgebruik worden niet bijgewerkt
Information about pages contained in a category, links to other wiki pages and images embedded in pages are tracked in special tables. The update of such tables is not done immediately after the edit is saved, but deferred to the job queue for performance reasons. If it takes too long to update, you may need to adjust, or try setting to false in LocalSettings.php. This can happen specially in some installations since MediaWiki 1.27 (see ).

Error: Could not open lock file for "mwstore://local-backend/local-public/./../image.png
Check that the "images" directory has permissions which allow writing. For example:  and. If you have SELinux enabled, this could also be problematic.

Notice: Did not find alias for special page 'Foo'. Perhaps no aliases are defined for it? [Called from SpecialPageFactory::getLocalNameFor in ...
You need to create an alias file. So, put something like this in your extension file (e.g. /extensions/Foo/Foo.php):

Then create an alias file like this:

Make sure you don't have a item with the same key. Keys of which are also in  will be skipped.

Warning: Invalid argument supplied for foreach in ./includes/objectcache/SqlBagOStuff.php
Probably you just moved your wiki, and didn't import your database, so it's empty.

There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Please resubmit the form.
Please follow Manual:How to debug/Login problems.

Call to undefined method
If a MediaWiki extension shows this error after installing that MediaWiki extension, double-check that you downloaded the version or branch of that MediaWiki extension which matches the version or branch of your MediaWiki installation.

Unable to run external programs, proc_open is disabled
The function has been disabled in. This prevents using ImageMagick to resize images to create thumbnails. Either contact your hosting provider, or try to use  instead of   by setting  to.

CAS update failed on user_touched for user ID '*' (read from slave); the version of the user to be saved is older than the current version
There are several reasons for this error. One simple one is if the content of the user_touched column of the user table is empty or is set to a time in the future.

You might want to check if the server's time is set correctly and synchronized. Also check the contents of that column and fill the column with valid content e.g. with this SQL statement:

Where the date is in YYYYMMDDHHMMSS format for the current date/time. See T247751.

Lua error: Internal error
See Extension:Scribunto

A database query error has occurred. This may indicate a bug in the software.
If you recently upgraded MediaWiki, or recently installed or upgraded extensions, try running the update.php maintenance script. (See also Manual:Upgrading.)

If that doesn't help, then you really may have ran into a bug in the software. Try to obtain more details about the query that fails (Manual:How to debug) and file a bug.

$wgSecretKey key is insecure, generated with mt_rand
Your system does not support  so the key was generated with. See Manual:$wgSecretKey.

<span id="PHP_Errors">

Fatal error: Allowed memory size of X bytes exhausted (tried to allocate Y bytes)
Raise PHP's memory limit in php.ini:

You can add a higher value for in LocalSettings.php.

Read here for more information on configuring resource limits in PHP.

Fatal error: Class 'DOMDocument' not found in xxxxxxxx/Preprocessor_DOM.php on line nnn
This error happens when PHP hasn't been compiled with DOM support, or the DOM/xml extension is missing.


 * Install the right  package for your distro. Example:
 * Alternatively, change the MediaWiki 'preprocessor' class in LocalSettings.php (see )

Fatal error: Invalid opcode 153/1/8. in xxx/includes/cache/MessageCache.php on line nnn
That issue seems to indicate it's a problem with a PHP code accelerator that doesn't match the installed version of PHP or it's outdated. Try upgrading the accelerator. report

Warning: Cannot modify header information - headers already sent by (...)
Most likely, your text editor added a byte order mark (BOM) while you edited MediaWiki's PHP files, but any other content before the opening  causes the same problem. This usually happens with - but see error message for exact file. Note that BOMs are invisible in most text editors. To remove the BOM, edit the file with something better than Windows Notepad, but if you don't really have time - open the file with it and choose Save as..., then choose "Unicode (UTF-8 Without signature) - Codepage 65001" as file type.

Strict Standards: date_default_timezone_get: It is not safe to rely on the system's timezone settings.
If you get Strict Standards: errors in the HTML output, that's because your  configuration variable of PHP is set to , but since PHP >= 5.4.0, E_STRICT became part of E_ALL. E_STRICT are not errors, but warnings about code interoperability and forward compatibility of PHP code, and they shouldn't be visible in production environments.

Just add your time zone to LocalSetting.php, e.g. $wgLocaltimezone = 'Europe/Berlin';

The following does not work in all cases. It may be better to put this in the php.ini which must be present in all affected directories.

You may turn of E_STRICT errors putting the following line of code inside your, or in case a line with the  function exists, replace it with:

You can turn off PHP errors entirely using this instead:

See also: Setting error reporting in PHP.

If nothing works, please check at the start of your LocalSettings.php file: If that error happened on the setup process, the LocalSettings.php that it generated could have included the error message at the top of it (example). If that was what happened, edit the file removing everything before " " and verify there's nothing (even whitespace) before " ".

Fatal Error: Cannot redeclare wfprofilein
This could happen if you upgraded and you have a  file in the root MediaWiki installation directory, probably because you enabled profiling in an old installation. To solve the issue simply remove that file.

Warning: Inaccessible files
After your move, you might see PHP warnings that certain files could not be accessed. This is most likely caused by : The column md_deps in the module_deps table contains absolute file paths, which are used to locate the images and LESS files that CSS depends on. These paths break when the wiki is, e.g., moved to another folder or another server. Until this bug is solved, you can use this workaround to manually fix wrong entries in the module_deps table:

This can be used to update wrong path segments and to fix the error.

A similar issue can happen when MediaWiki tries to read ResourceLoader messages. In this case the solution is to truncate the according tables:

Fatal error: Uncaught Exception: extension.json does not exist
If this error happens when you try to install an extension, it usually means that the extension still requires to use the native PHP  language construct instead of the newer   method.

<span id="Installation_Errors">

LocalSettings.php not readable

 * On a Linux machine, use  and or   to correct the file permissions of.
 * On some Linux machines, temporarily disable SELinux by running the command.

The installer is unstyled when installing under IIS
The installer is unstyled and instead of the stylesheet,  shows this error message: "Less_Exception_Parser from line 447 of ...\vendor\oyejorge\less.php\lib\Less\Parser.php: Less.php cache directory isn't writable: C:\Windows\TEMP"

Make sure that the webserver user, who by default is named, is allowed to access the C:\Windows\TEMP directory. At least read and write permissions are necessary.

Error selecting database wikidb: 1044 Access denied for user 'username'@'localhost' to database 'wikidb'
You need to Grant permissions on wikidb.* - See Manual:Installation guide

or if your Web Server is on a different box than your DB server - you have to configure remote access to MySQL and grant differently

NOTE: Replace 192.168.0.x with your Webserver's IP. Also note that the apostrophes (') need to stay.

Database returned error "1142: CREATE command denied to user 'username'@'localhost' for table 'user_properties' (localhost)"
As above, or temporarily use the mysql root user.

Could not find a suitable database driver!
PHP MySQL support is not installed/enabled - See https://php.net/book.mysqli. Depending on your operating system, you may need to install an additional package. For example, on debian/ubuntu run.

Filename Case Errors
If you are using a different FTP client than FileZilla to upload files to your server, be sure to configure the client to not force uppercase or lowercase filenames. MediaWiki filenames are case-sensitive.

Incomplete Upload Errors
The MediaWiki package includes a lot of files, spread over dozens of directories. Be careful when uploading. If the transfer is interrupted, you might have missing or incomplete files. You may have to retry your upload several times, especially if you have an unreliable connection.

<span id="403_Forbidden_with_Symbolic_Links">

403 Forbidden met symbolische links
If your webserver produces a "403 Forbidden error" page and you are using symbolic links, then make sure your Apache httpd.conf file has Options FollowSymLinks to allow symbolic links and that each directory leading up to your linked directory has +x permission for user running httpd.

<span id="HTTP_500_Internal_Error_during_installation">

HTTP 500 Internal Error bij installatie
If your webserver produces a "500 Internal Error" at the beginning of the install process, you may need to change the permissions on the  directory to 755. If you have changed the permissions for the config directory and still get an unwritable error try changing the owner to apache.

<span id="HTTP_500_Internal_Error_after_installation">

HTTP 500 Internal Error na installatie
If you downloaded the MediaWiki code from Git, and after finishing the installation process, accessing your MediaWiki installation in the web browser produces a "500 Internal Error", go to the MediaWiki installation folder and running the following commands:

SELinux
Linux distributions which support SELinux ('Security Extensions') are becoming more widespread. On such systems, PHP scripts will still be unable to write to the config directory, after you have set the normal file permissions. You will also need to use the 'chcon' command to change the SELinux file type. See SELinux.

Required Advertisements on Hosted Sites
If you are running the MediaWiki software on a free site that requires banners or prefix advertising, this may cause MediaWiki not to work, and appear to only generate empty pages beyond the banner advertising. You will have to contact your host to make them make their advertising compatible with MediaWiki, or choose a different host.

<span id="Debian,_Apache2,_and_PHP">

Debian, Apache2 en PHP
If you're running the MediaWiki on Debian with Apache2 and PHP5, and have problems connecting to MySQL, e.g you get the following error message in your browser: (Can't contact the database server: MySQL functions missing, have you compiled PHP with the --with-mysqli option?) try uncommenting: ';extension=mysqli.so' in the '/etc/php5/apache2/php.ini' file.

If that does not work, try the following...

Check that MySQL module for php is installed:

If you need to install the php5-mysql module enter:

Then restart Apache2:

'user_password' can't have a default value
Ensure that MySQL is not running in strict mode.

<span id="Missing_table_prefix">

Tabel prefix ontbreekt
If you are using a hosting service, the database name and database username may have an extra prefix (normally the userid given by your hosting provider). For example, if you have created a database named db01 with username u01 and your userid is ocom (given by your hosting provider), you should enter the database name and database username as ocom_db01 and ocom_u01 respectively.

MySQL connection fails with error [2013] or [2002]
If you are getting the error:  or , this may be caused by using the wrong database host name or by a permissions issue with the mysql.soc file or directory.

If you are using a hosting provider, ensure that you are using the correct host name for the database.

The MySQL manual has a good set of pages on dealing with common errors (such as these). Visit the page for links to documentation for other versions of MySQL.

If you are unsure if MySQL is even installed, try the command  from the command line; if it is not installed, see Manual:Running_MediaWiki.

UNIX utility binaries not found
Errors include:


 * GNU diff3 not found
 * Git version control software not found
 * ImageMagick not found

PHP must have access to /usr/bin. In php.ini (probably ), add   to open_basedir config variable as below:

open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/var/www/:/usr/bin/

To disable GIT set to a path that's allowed but doesn't exist.

"Forbidden: You don't have permission to access /mediawiki/ on this server."
This is usually an issue with the configuration of your web server software and unrelated to MediaWiki itself. See for example https://stackoverflow.com/questions/10873295/error-message-forbidden-you-dont-have-permission-to-access-on-this-server or other web server forums.

Update/Upgrade Errors
<span id="Missing_rc_timestamp_field_of_recentchanges_table._Should_not_happen.">

Veld rc_timestamp ontbreekt in tabel recentchanges
Might e.g. happen on upgrading from MW 1.27 to another version. If there is no database content at all you might see this message. See T236671.

This may happen if you didn't specify the same than your original installation, causing MediaWiki to not find its tables. Check the existing tables on the database and see if they all share a common prefix, and update that setting accordingly.

Another cause may be that you set an empty database. Reinstall the database content from a backup and proceed with migrating.

Parsoid / VisualEditor
See Parsoid/Troubleshooting and Extension:VisualEditor.