Thread

To upgrade to EE2.2.1 cleanly I moved the system folder back down under htdocs. I went through the config file, changed the various entries, and upgraded to 2.2.  This seems to have gone OK. 

I have used MSM with EE1, but had no luck previously installing it on EE2, so I thought I’d try again with the new release before moving the system folder above root again.

I downloaded latest MSM, transferred the three files ( in cp, lib, language), then went into the control panel/general configuration and set MSM to enabled. However, I get the above error upon submitting the change in configuration. By editing the config file and setting MSM to not enabled, I am able to gain access to the site again.

I thought it was not necessary to edit the values of the index.php files with only one site? However, I also tried to set the values in (htdocs/index.php and htdocs/system/index.php) But with these settings the site fails to load (white page).

What is the proper installation sequence/what could be wrong ?

v2.2.1 - Build: date 20110705
MSM latest 2.1.0
PHP memory 2560

icebreaker,

Can you confirm that you have the latest index.php and admin.php from the EE2.2.1 download in your root?
If not add them and update your system folder path in both

What version was your upgrade from?

What host are you using and what type of hosting environment is it?

1. I have uploaded new versions of index.php and admin.php to be sure.
2. I have moved the system folder back above webroot again, changed the name of the system folder, and the name of admin.php
3. However, I have the same behaviour—site is OK, Control Panel works, but on submitting the General Configuration - Enable MSM I get the same error message.

I am running a Ubuntu 11.04 “natty” as server. Installs is done as root.
Everything is current.

(I am currently also running MSM on EE1.68 for three other sites, but there should not be any possibility of interference since these are sister sites, and a separate installment of EE).

Upgrade was from 2.1.3 which again was installed from scratch.

Used grep to find where the error message originated.
Found that it was in core/EE_config and that there was a query on site-name.
When I use the utility functions inspect the site table /select * from exp_sites the site_name was “default_site”.

Used MySQL Manager to look up exp_sites, right_click edit Table and changed name to the correct one.

MSM now seemingly functioning ok and sites menu visible - which of course makes me happy 😊

Hi, icebreaker -

It seems odd that you had to do that.  When you were running MSM previously, did you change the site short_name for Site 1?  Or was it always default_site?

And most importantly, you’re up and running?  I don’t want to get side-tracked in “why did that happen” if we still need to fix something.  =)

I think it could be worth looking into. Not on my account, but because I suspect this will produce problems for other developers upgrading. This was an error that failed to show up in the config editor, the configuration manager and the config file and over a long time.

It should be easy to implement a warning that there is a mismatch between the name set in the general configuration and the one set in the MySQL file. 

When a site name change fails to register, it would also be reasonable to expect an error message.

However, I am satisfied that I have a site where this seems no longer to be a problem, and the thread can be closed. I also want to thank for the follow up. I feel I can depend on support when in trouble, and it is nice to have assurance that you (within reason!) will not be left high and dry when you really need help.
———————————

A Gotcha when rearranging the site in preparation for the upgrade to 2.2.1 is that the Menu Manager allows users to make their own short cuts to parts of the control panel. Since these links no longer point to the correct location during the upgrade process,  several of the user defined menus on the right side of the Menu bar points to the “old” admin file, whereas the system defined options in the left part of the Menu bar point to the new. It is easy to think that there is a configuration problem, and not realise that parts of what appears to be system choices are in fact user defined.

Thanks icebreaker,

I will go ahead and close this one for now. The menu issue you mentioned is indeed a confirmed bug. Thanks!