Thread

This question may be related to a resolved thread.

We’re running on engine hosting and I just upgraded to EE 2 today.  When I turn on MSM I get a 500 error.  I have to edit the config.sys to turn off MSM in order to get the CP to display.

I’m having some other general issues, but this is the big one at the moment.

I doubled checked that the CP templates were OK (and uploaded them again, just to be sure).  I use CuteFTP to upload.

Suggestions?

I found this thread which sounds like it is the issue.  Unfortunately the license owner for the site I’m working on isn’t me, so I have to wait until he can download the updated version of the MSM to see if that fixes the problem.

Before I discovered that, however, I was trying to get back in to the Control Panel.  I downloaded the config.php file and changed multiple sites enabled to “no.”  But I still can’t get to the CP.  (I get a blank screen, which is better than the 500 error, but still not the result desired.)

I found that the config.php file was truncated, cutting off at the midpoint in the PayPal certificate. I fixed it, by copying the remaining data from a back-up of the config file.  Should I have not fixed it?

I still can’t get back in to the Control Panel.  Is there some other file that needs to be edited, with MSM turned off?

Solved this one too so you can close it… but there was an issue with the truncating of the config.php file. 

Since I went through the upgrade to EE2 three times (don’t ask), I had the chance to see if this only happened once, or if it was consistantly wrong.  The truncating of the config file wasn’t a one time thing.  There is something in the upgrade routine that dumped the data in the file, in the middle of the paypal encryption info.  Frankly, I don’t know how the site ran at all with the file like it was, but I’m not that familiar with how EE2 handles things, so it must have been relying on the info from somewhere else.  If anyone wants a copy of the damaged version to research it, let me know.

Also, you may want to note in the docs (somewhere) that the database info is no longer in the config.php (and is in database.php).  Since I was upgrading and testing from copies of the database, that is something important to know. There will surely be others who use that approach on an upgrade as substantial as this.  A mention in the release notes might be a good place for it.

Thank your for your feedback. I’m very glad to see you’re up and running, please don’t hesitate to post again as needed.