Jump to navigation Jump to search
This page is a translated version of the page Manual:$wgReadOnly and the translation is 12% complete.

Outdated translations are marked like this.
Other languages:
English • ‎Nederlands • ‎español • ‎français • ‎magyar • ‎polski • ‎中文 • ‎日本語
Verrouillage du wiki: $wgReadOnly
Interdit l'édition, affichant la chaîne fournie comme raison.
Introduit dans la version :pre 1.1.0
Retiré dans la version :Encore utilisé
Valeurs autorisées :(string), null/false
Valeur par défaut :null
false (prior to 1.5.7)


C'est fonctionnellement la même chose que $wgReadOnlyFile, mais en utilisant une variable au lieu d'un fichier.

S'il est mis à une chaîne (par ex., dans LocalSettings.php), $wgReadOnly désactive l'édition, affichant la chaîne fournie comme raison.

$wgReadOnly = 'This wiki is currently being upgraded to a newer software version. Please check back in a couple of hours.';

$wgReadOnly = 'maintenance du site'; L'exemple ci-dessus verrouille la base de données et fournit une déclaration par défaut sur les pages d'édition, et donne aussi la chaîne incluse 'maintenance du site' comme explication pourquoi la base de données a été verrouillée.

Wikitext is allowed in this string and will be rendered when the read-only warning is shown which can be used to provide links or highlight upgrade notifications.

Avertissement Avertissement : In contrast to its name, this settings does not make the database read only! Even if $wgReadOnly is set, extensions, API scripts and other cacheable events can write data nonetheless.


Since MediaWiki 1.27, running the upgrade script will not work if $wgReadOnly is set.

A simple solution is to set it to read only when not running from the command line, which will not affect the command line update script:

$wgReadOnly = ( PHP_SAPI === 'cli' ) ? false : 'This wiki is currently being upgraded to a newer software version. Please check back in a couple of hours.';


If sessions are not stored on an external caching system such as Redis or Memcached, users may get logged-out, and no further login attempts would succeed during the time the wiki is set read only, receiving a message similar to Votre session de connexion semble avoir des problèmes ; cette action a été annulée en prévention d'un piratage de session. Veuillez soumettre le formulaire de nouveau..

DB caching

Caches that use the database cannot be written to during read only mode, which could prevent more than just editing (depending on the configuration, logging in or even viewing pages). This can be avoided by disabling cache, albeit at the cost of making your wiki slow. This can be accomplished with the following settings in LocalSettings.php:

$wgMessageCacheType = $wgMainCacheType = $wgParserCacheType = $wgSessionCacheType = CACHE_NONE;
$wgLocalisationCacheConf['storeClass'] = 'LCStoreNull';

If you want your wiki to be fast, while still not using the DB, you should consider using something like Memcached. See $wgMainCacheType and $wgLocalisationCacheConf for details. If you want to enable logins while the database is readonly, at least $wgSessionCacheType needs to be set to some real non-DB caching mechanism.


When in read-only mode, images which need to be transformed or scaled will be shown as an error message instead of as an image. To avoid this problem, put the following in the "LocalSettings.php" file:

$wgIgnoreImageErrors = true;