#2481 - Installing as MSN error

By Adam Edington
Added 23rd Apr 2016, 3:37 PM
1 view

Identifier	#2481
Issue type	Feature request or suggestion
Title	Installing as MSN error
Status	Closed (cannot reproduce)
Handling member	Chris Graham
Addon	core
Description	Unfortunately a query has failed [DELETE FROM cms10_privilege_list WHERE (the_name='run_multi_moderations') LIMIT 1] [Table '_msn_kal.cms10_privilege_list' doesn't exist]
Steps to reproduce	1) Created a table in SqlYog 2) Selected MSN, entered existing db details 3) Entered new db details 4) Get the above error on Step 6 linked to multi moderation
Funded?	No

The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated

Comments

By Guest posted 23rd Apr 2016, 3:39 PM

Okay, I also notice it is stripping cms. The database was entered as cms_msn_kal and is now just _msn_kal in these error messages.

By Guest posted 23rd Apr 2016, 3:57 PM

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.

By Guest posted 23rd Apr 2016, 11:18 PM

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.

By Guest posted 24th Apr 2016, 3:09 AM

Yeah I always tend to skip that bit, shall try not to in future.

By Guest posted 24th Apr 2016, 7:14 PM

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.

By Guest posted 26th Apr 2016, 4:09 AM

By Guest posted 26th Apr 2016, 4:10 AM

Okay, tried this again and it worked out. Got a couple of messages (see screenshot) that claimed to be software bugs.

By Guest posted 26th Apr 2016, 8:21 PM

See #2514 for that.