We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Upgraded EE with MSM, now can only see primary site

How Do I?

deeciduous's avatar
deeciduous
30 posts
7 years ago
deeciduous's avatar deeciduous

I upgraded from EE 2x, to EE 3.5.16. I can see my primary site fine, but the other sites (both index.php and admin.php) say:

Your system folder path does not appear to be set correctly. Please open the following file and correct this: index.php

So I have checked all the usual - open_basedir looks ok (has not changed):

{WEBSPACEROOT}{/}{:}{TMP}{/}:/var/www/vhosts/site1.com/httpdocs/:/var/www/vhosts/site2.com/httpdocs/

Folder permissions are 755 on site1.

Just to check the system_path, in index.php for domain2, I have added:

echo SYSPATH.'ee/EllisLab/ExpressionEngine/Boot/boot.php';

And this shows the correct path i.e.

/var/www/vhosts/domain1.com/httpdocs/softwater/ee/EllisLab/ExpressionEngine/Boot/boot.php

I can access the domain2 control panel by first logging into the domain1 control panel.

I’m truly stumped. Everything was working fine with EE2 - what could have gone wrong?

       
Derek Jones's avatar
Derek Jones
7,561 posts
7 years ago
Derek Jones's avatar Derek Jones

Did you replace the index.php files with the new ones from v3?

       
deeciduous's avatar
deeciduous
30 posts
7 years ago
deeciduous's avatar deeciduous

I did. One thing that has come to my attention, is the license key is not the same as the key listed in the EllisLab account purchases. Does the key change when you upgrade from EE2 to EE3, and would it cause the non-primary sites to stop working if the key is not correct in the EE CP?

I have had to roll-back to EE2 for the moment, so I can’t try the correct key on the EE3 installation.

If the above is a red herring, is there anything else I can check?

       
Derek Jones's avatar
Derek Jones
7,561 posts
7 years ago
Derek Jones's avatar Derek Jones

Yes, in v3+ the license is an actual file, that is included in your download and should be in place when you deployed the files before running the update. It lives in system/user/config. Make sure you have that file in place. It would not stop additional sites from functioning, but you would not be able to add any additional sites until that’s resolved. The error you have is not related, though. At the top of your additional site index.php files place:

error_reporting(E_ALL);
ini_set('display_errors', 1);

I suspect there’s a PHP error that is not being displayed that will reveal all.

       
deeciduous's avatar
deeciduous
30 posts
7 years ago
deeciduous's avatar deeciduous

So on my EE3 dev environment I have checked the key and it’s correct, with the correct amout of sites assigned to it. That was a red herring. I guess the key changes between versions.

I have added a secondary site in dev, and added the code you suggest to my index.php file. No errors, and site still not working! To check error reporting was working I temporarily sabotaged open_basedir on site2, and it did display an error.

I can get to the site2 CP via the site1 URL but it’s displaying weird behaviour e.g. when editing a template it’s all out of kilter:

Could this be a clue?

Thanks for your help, I appreciate it.

       
Derek Jones's avatar
Derek Jones
7,561 posts
7 years ago
Derek Jones's avatar Derek Jones

That looks like your themes folder did not get updated, or has some missing resources. Not related directly “Your system folder path does not appear to be set correctly. Please open the following file and correct this: index.php”, that is an error that occurs directly in the bootstrap file (the index.php file itself) and means EE hasn’t even been spun up yet. Perhaps you have some dynamic config that is causing problems in both cases? If you’d like one of our engineers to troubleshoot directly, just drop us a support ticket and we’d be happy to help you sort it out.

       
deeciduous's avatar
deeciduous
30 posts
7 years ago
deeciduous's avatar deeciduous

Thanks Derek, call opened.

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.