Change Details

If you have a `LocalSettings.php` in place, but an empty database, going to `index.php` results in an error. If you go to `/mw-config` you go through the installation wizard, but then are prompted to download the updated `LocalSettings.php` again. I think this should be updated in this way: # If a `LocalSettings.php` file exists, but the database is empty, the user should be prompted to install MediaWiki # If a `LocalSettings.php` file exists, then the install wizard should only ask you questions whose answers do not need to modify `LocalSettings.php` (i.e. it should ask for the admin user/password, but not the wiki name). The user should *not* be prompted to download/update the `LocalSettings.php` file. We //could// ask the user at the beginning of the wizard if they want to update the file or not and default that option to //no//, but I don't think that is necessary. The only alternative I can think of is for the web server to update the file, but since we don't do that already, it's probably a bad time to start.

If you have a `LocalSettings.php` in place, but an empty database, going to `index.php` results in an error. If you go to `/mw-config` you go through the installation wizard, but then are prompted to download the updated `LocalSettings.php` again. I think this should be updated in this way: # If a `LocalSettings.php` file exists and a database connection can be made, but the database is empty, the user should be prompted to install MediaWiki. The install wizard should only ask you questions whose answers do not need to modify `LocalSettings.php` (i.e. it should ask for the admin user/password, but not the wiki name). # If a `LocalSettings.php` file exists but a database connection cannot be made, then the install wizard should proceed as normal, but should append any needed changes to the end of the existing `LocalSettings.php` before asking the user to download the updated file. The only alternative I can think of is for the web server to update the file, but since we don't do that already, it's probably a bad time to start.

If you have a `LocalSettings.php` in place, but an empty database, going to `index.php` results in an error. If you go to `/mw-config` you go through the installation wizard, but then are prompted to download the updated `LocalSettings.php` again. I think this should be updated in this way: # If a `LocalSettings.php` file exists and a database connection can be made, but the database is empty, the user should be prompted to install MediaWiki. The install wizard should only ask you questions whose answers do not need to modify `LocalSettings.php` (i.e. it should ask for the admin user/password, the user should be prompted to install MediaWikibut not the wiki name). # If a `LocalSettings.php` file exists, then the install wizard should only ask you questions whose answers do not need to modify `LocalSettings.php` (i.e. it should ask for the admin user/password but a database connection cannot be made, but not the wiki name).then the install wizard should proceed as normal, The user should *not* be prompted to download/update the `LocalSettings.php` file. We //could// ask the user at the beginning of the wizard if they want to update the file or not and default that option to //no//, but I don't think that is necessarybut should append any needed changes to the end of the existing `LocalSettings.php` before asking the user to download the updated file. The only alternative I can think of is for the web server to update the file, but since we don't do that already, it's probably a bad time to start.