Refreshed the page and somehow got to step 7, which informs me " Unfortunately a query has failed [SELECT COUNT(*) FROM cms_f_groups g WHERE g_is_private_club=0 LIMIT 1] [Table 'cms.cms_f_groups' doesn't exist] " and I can't get any further.
The database cms_msn_kal has been created, so it must be the bug with cms being stripped from the database name. I also notice that the _msn_kal database has been created with no tables in it.
This reminds me of another potential bug with the standard install, which again is to do with the database name. Pretty sure I changed it from cms a few times, to composr and other variants and it still created a cms database without tables. This is when I was reporting about the cms10_values table crashing all the time. I have left it as the default database name since and had no trouble.
Just a personal suggestion for better categorizing of bugs, the severity should probably be categorized as major (if you can still install as a MSN), or crash (if you cannot install as a MSN at all because of this), instead of feature.
I couldn't reproduce 'cms_' getting stripped, or the DB error.
I did find an error with mixed up table prefixes, which I've fixed, and an inconsistency with default table prefixes.
I think the errors reported here are likely to do with broken legacy installs. The forum chosen for installation against must be a fully working v10 install.
If the issue happens on the next release with entirely clean v10 databases, and you're sure the forum database is a preexisting working one, and the names were carefully checked, please report with the full details of the database names and table prefixes used for each of the two databases.
The database cms_msn_kal has been created, so it must be the bug with cms being stripped from the database name. I also notice that the _msn_kal database has been created with no tables in it.
This reminds me of another potential bug with the standard install, which again is to do with the database name. Pretty sure I changed it from cms a few times, to composr and other variants and it still created a cms database without tables. This is when I was reporting about the cms10_values table crashing all the time. I have left it as the default database name since and had no trouble.
I did find an error with mixed up table prefixes, which I've fixed, and an inconsistency with default table prefixes.
I think the errors reported here are likely to do with broken legacy installs. The forum chosen for installation against must be a fully working v10 install.
If the issue happens on the next release with entirely clean v10 databases, and you're sure the forum database is a preexisting working one, and the names were carefully checked, please report with the full details of the database names and table prefixes used for each of the two databases.
(Click to enlarge)