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 user 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, 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, 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 userwizard 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.