|This feature was removed completely in version 1.23.|
|MediaWiki file: AdminSettings.php|
|Source code:||not in Git (created by user)|
|Classes:||Find code • Find documentation|
The requirement for
AdminSettings.php (along with supporting file
AdminSettings.sample) was rudimentarily removed in MediaWiki 1.16. Prior to MediaWiki 1.16,
AdminSettings.php was used to store database authentication credentials for maintenance scripts and to control the availability of
profileinfo.php. It has finally been removed completely in MediaWiki 1.23.
If upgrading from a pre-1.16 version of MediaWiki to version 1.16 or later, the variables set in
AdminSettings.php file can be safely removed.
AdminSettings.php is no longer needed. If it still exists, it will be loaded by maintenance scripts to retain backward compatibility.
Prior to 1.16
AdminSettings.php in the root directory of the MediaWiki installation. Typically, this is done by renaming
AdminSettings.php and then editing
AdminSettings.php should set three variables:
$wgDBadminuser- the name of a database account that has sufficient privileges to run the database maintenance scripts. For MySQL databases, this account should have "superuser" privileges. For PostgreSQL databases, this account should be the same account used for $wgDBuser.
$wgDBadminpassword- the password for the
$wgEnableProfileInfo- controls the availability of
<?php /* Database authentication credentials */ $wgDBadminuser = 'wikiadmin'; $wgDBadminpassword = 'adminpass'; /* Whether to enable the profileinfo.php script. */ $wgEnableProfileInfo = false; ?>
AdminSettings.php contains sensitive information (account names and passwords) that can help an attacker compromise your database management system. Ensure that you've taken the relevant preventative measures listed in Manual:Security and Manual:Securing database passwords.
If using PostgreSQL with your MediaWiki installation, the authentication credentials used for
$wgDBadminpassword should be the same as the credentials used for
$wgDBpassword. This is necessary to ensure that the owner for new tables is set correctly.