Change Details

If the installer is given an invalid (too simple etc.) wiki admin password (which is not that hard to do with the new, stricter rules that are default for MW 1.35), it will mostly set up the database, then abort with an exception. (Only seen in the CLI installer, in Varnish, but the CLI and web installer code are close enough that the same will probably happen in both.) That's pretty terrible for user experience. (Before 3df9742b32 there was a normal error instead of an exception, but that's not much better, either.) The password should be checked for validity before installation starts. This should probably be a blocker for the 1.35 release.

If the installer is given an invalid (too simple etc.) wiki admin password (which is not that hard to do with the new, stricter rules that are default for MW 1.35), it will mostly set up the database, then abort with an error. (Only seen in the CLI installer, in Varnish, but the CLI and web installer code are close enough that the same will probably happen in both.) That's pretty terrible for user experience. The password should be checked for validity before installation starts.

If the installer is given an invalid (too simple etc.) wiki admin password (which is not that hard to do with the new, stricter rules that are default for MW 1.35), it will mostly set up the database, then abort with an exceptionerror. (Only seen in the CLI installer, in Varnish, but the CLI and web installer code are close enough that the same will probably happen in both.) That's pretty terrible for user experience. (Before 3df9742b32 there was a normal error instead of an exception, but that's not much better, either.) The password should be checked for validity before installation starts. This should probably be a blocker for the 1.35 release.