Thread

Hi there.

I have MSM up and successfully running, but it seems to only work correctly if I login via the main / default site. When I login via a secondary site (http://www.secondarysite.com/admin.php) I’m able to successfully login, but I immediately get the following error messages on the front-end:

A PHP Error was encountered
Severity: Notice
Message: Array to string conversion
Filename: libraries/Core.php
Line Number: 295

A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/seattleo/public_html/_admin/codeigniter/system/core/Exceptions.php:170)
Filename: libraries/Functions.php
Line Number: 767

A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/seattleo/public_html/_admin/codeigniter/system/core/Exceptions.php:170)
Filename: core/Common.php
Line Number: 405

Fatal error: ob_start() [<a href="http://ref.outcontrol">ref.outcontrol</a>]: Cannot use output buffering in output buffering display handlers in [system_path]/codeigniter/system/core/Exceptions.php on line 166

Any insight on why this is happening would be much appreciated.

Thanks,
Brett

Hi Brett,

What version of ExpressionEngine are you running? What Version of MSM? If you just installed MSM, could you re-upload the files and try again?

Sean

Hi Sean.

Thanks for the followup and sorry for the delayed reply. I’ve been away from my desk on vacation for the Thanksgiving holiday. I’ll followup early next week once I’m back.

best,
Brett

Brett,

Great - will look for your follow-up after the holiday then.

Sean

Hi Sean,

Thanks again for your patience. I finally had a chance to investigate this issue further. Unfortunately, I’ve reinstalled MSM and am still running into issues. Here’s a rundown of what I’m experiencing:

1) If I log into site2.com/admin.php as the SuperAdmin I’m seeing error messages on the front-end of Site2 (but the back-end works fine).

2) If I log into site1.com/admin.php as the SuperAdmin and access Site2 by switching sites in the top right with the MSM things on the front and back-end seem to work fine.

3) If I log into site2.com/admin.php as a member type created just for Site2 things seem to work fine.

4) If I log into site1.com/admin.php as a member type created just for Site2 I see an error message that says “You are not authorized to perform this action.” I’m guessing this is because that member type doesn’t have access to edit Site1 content.

Here are some details on the system and the MSM setup.
– Running EE 2.3.1
– Running latest version of MSM (downloaded and installed today)
– Running 2 sites with MSM

File Structure for the two sites
Site 1
domain1.com
    ├── admin.php
    ├── index.php
    ├── images
    ├── system
    └── themes

Site 2
└── domain1.com/ee/domain2.com
    ├── admin.php
    └── index.php

Site 1 admin.php Settings
$system_path = ‘./system/’;
$assign_to_config[‘site_name’]  = ‘default_site’;
$assign_to_config[‘cp_url’] = ‘http://www.site1.com/eadmin.php’;

Site 1 index.php Settings
$system_path = ‘./system/’;
$assign_to_config[‘site_name’]  = ‘default_site’;
$assign_to_config[‘cp_url’] = ‘http://www.site1.com/admin.php’;
$assign_to_config[‘site_url’] = ‘http://www.site1.com/’;

Site 2 admin.php Settings
$system_path = ‘../../system/’;
$assign_to_config[‘site_name’]  = ‘site2’;
$assign_to_config[‘cp_url’] = ‘http://www.site2.com/ee/admin.php’;

Site 2 index.php Settings
$system_path = ‘../../system/’;
$assign_to_config[‘site_name’]  = ‘site2’;
$assign_to_config[‘cp_url’] = ‘http://www.site2.com/ee/admin.php’;
$assign_to_config[‘site_url’] = ‘http://www.site2.com/ee/’;

The error messages I’m seeing are the same from my original post above.

All in all MSM is currently functional, it’s just not working very well / as expected. Any insight or assistance you can offer would be much appreciated.

best,
Brett

I’m assuming this line is a typo?:

$assign_to_config[‘cp_url’] = ‘http://www.site1.com/eadmin.php’;

There shouldn’t be an ‘e’ in ‘eadmin.php’

- bob.

Thanks for catching that Bob.

You’re right, it’s a typo.

Brett,

Did fixing the typo resolve your login problems?

Sean

Thanks for the followup Sean. I guess I should have been more clear.

It was a typo in the sample code, not the working file. So no, I never was able to solve the issue.

Hi Brett,

Be on the lookout for an email from me. I feel we need to login to your site to further troubleshoot this issue

Thanks John.

I just filled out your login request form.

Here’s some additional info that might be helpful:

– Default site: http://www.826seattle.org/
– Secondary site (Greenwood): http://www.greenwoodspacetravelsupply.com/
– Another issue I’ve been noticing is that from time to time when I log into the default site as a super admin, switch to the Greenwood site and then log out of the control panel, I’m unable to log back into the control panel unless I quit and restart the browser (Firefox 8.0.1 on a Mac).

Let me know if you have any questions and thanks in advance for your assistance.

best,
Brett

Hi Brett,

I think I’ve nailed it. Here’s the issue: one of your snippets on your second site contains something that’s causing EE to completely puke errors. I’m not sure which one it is, but you’ll be able to narrow it down by quickly removing snippets from your main template on site2 until the site loads properly. I didn’t want to do that since it’s a live site.

Now, the reason you’re only seeing it when you log in to site 2’s CP is because PHP errors are only shown to Super Admins. When you log in to site 1’s CP and then click over to edit site 2’s CP, you’re still just logged in to site 1 and therefore site 1’s front-end. You’re not logged in to site 2’s front-end. Only when you login to site 2’s front-end or CP will site 2’s front-end actually see you as logged in. It’s confusing, I know, but did that make sense at all? That’s just to help you understand why you only saw the errors when you saw them. But they’re there all the time.

So if you want to narrow down which snippet it is that’s causing you issues, feel free to post the contents of the snippet here and we’ll be glad to help you troubleshoot it!

Hi Kevin.

Thanks for the detailed followup.

I appreciate you helping me narrow it down. I’ll sniff around and see if I can fix it myself. If not, I appreciate your offer of continued assistance.

One more question, would the PHP errors explain why sometimes I’m unable to log back into site1 immediately after logging out? The only “fix” I’ve found for this is restarting the browser. It would seem to be unrelated, but it didn’t start happening until I installed MSM.

best,
Brett

Hi Brett,

I doubt the PHP errors are causing you login issues, but let’s fix one thing at a time. Otherwise we might get a little turned around by trying to fix several things at once. Once you’re able to knock out those PHP errors, report back here with some more details on the login issues you’re experiencing, and we’ll go from there!

Hi Kevin,

Sorry for the extended delay. This issue got pushed to the back-burner by a few end of the year site launches. I really appreciate you taking the time to login, poke around, and report back. I’m sure it’s frustrating to not get a prompt followup, my apologies.

You were right, I had some unnecessary legacy code from the “main” MSM site that was throwing the PHP errors. Stripping that out fixed things immediately! Thanks so much for pointing me in the right direction. I really do appreciate it.

And I haven’t had any reports of login issues since my last post earlier this month, so for now I’m going to assume that’s a moot point.

Happy holidays and thanks again for your assistance.

all the best,
Brett