Thread

No, I’m afraid it still doesn’t work. I uploaded a fresh index.php from a new EE download. The only thing I changed was the path. Is there something about the server config I should be looking into, perhaps?

Hi Chris,

At this point, we would like to be able to have a look at this. I understand that might not be possible given the nature of your sites, but if so, let me know and I’ll send you the request information.

Cheers,

I can get you in, at least into my test install. What do you need?

Hi Chris,

Be on the lookout for an email from me. It will have a link to s secure place for you to supply your details.

Thanks!

Hi Chris,

I’m just double checking to see if you received the email from me on the 10th. Please let me know where we are on this. I’d love to help you move towards resolution!

Thanks!

Hi Chris,

One more check to see if you have received that email from me. Please let me know where you stand on this. If you need me to resend the request, that’s fine, I just want to do whatever I can to get you a solution.

Thanks!

Just wanted to let onlookers know we’re working with Chris on this issue privately.

We’ll update here when we have more information.

Thanks!

Hi Chris,

After logging in a taking a look, I came away with a few ideas that I need you to try on the live environment. I wasn’t able to fully test them out because of it being a test environment. So, here goes:

1) Make sure you have the most up-to-date /themes folder in place. Also make sure you have the most up-to-date versions of the third-party themes you are using. Make sure to backup your /themes/third-party folder as well.
2) Please make sure to switch over to the default theme in the Control Panel and make sure that anyone experiencing these issues is using the default theme as well.
3) For site-1: cookie domain “.pasco.k12.fl.us” and set the prefix to “www” site-2: cookie domain “.pasco.k12.fl.us” and set the prefix to “memos”

Using those settings and the default theme, please try the MSM login in Chrome and FF and let us know where we are.

Thanks!

OK, so steps 1 and 2 are done, but apparently I’m unable to set a separate cookie prefix for each site at the moment. Whatever I set for one will automatically show up for the other, with no ability to differentiate. How should I fix this? Getting closer, I hope. 😊

edit: Meant cookie prefix, not domain.

edit 2: Should also note (since I fired this off at the end of a very long day) that I have been able two set two separate cookie prefixes at some point in the past. It didn’t have an effect on this issue the last time I tried it, however I’m guessing that the two problems are somehow related.

Hi Chris,

The good news is, you can set this in each site’s index.php with the following:

$assign_to_config['cookie_prefix'] = 'www';

Be sure to use each site’s distinct prefix value.

Thanks!

Yes, I was aware of that. It’s certainly something I’ve tried previously. Unfortunately, it is not respecting hardcoded settings either, or if it is, what’s showing on the admin interface is whatever gets thrown into config.php. If I take the line out of config.php, there’s nothing for either site. If I add something via the interface, it goes into config.php and shows for both sites. The hardcoded index.php settings will not override either.

Hi Chris,

In this instance, clear the values in config.php and in the Control Panel. Then set the values in each site’s index.php file. In ExpressionEngine, config.php is the ultimate authority and *whatever* is coded there will override any values stored in the database and in any individual index.php file. This is why the value was populating for both sites regardless of what you have set for each individual site in the CP/index.php

So, the order of authority is: database (what is entered via the Control Panel), index.php then config.php

Since this is an MSM setup, running 1 copy of ExpressionEngine, it only has 1 config.php file to use, and thus it is overriding anything you set in each site’s index.php

I hope that was clear? It can be a bit confusing.

Thanks!

Yes, understood, but that does not appear to be happening in this case. I’ve cleared the cookie settings (all of them) from the CPs, removed the prefix setting from config.php, and added the prefixes to both index.php files. I’ve done this in the past and remember the hardcoded values showing up from that point on in the CP. Here I’m getting nothing. Just blank lines. If I’m remembering wrong, please let me know. In any case, following those instructions didn’t fix the site switching issue.

If it’s any help, since doing this I notice that I’m getting random ‘preferences updated’ messages on various pages in the cp. I have also gone through and uninstalled pretty much every third party module, accessory, extension, etc. to see if there was any change. Nothing.

Hi Chris,

Just to put you at ease, you are going to get those notices anytime you make changes to your index.php files. ExpressionEngine is just letting you know that they have been changed, in case you weren’t the one to be doing it.

I’m sorry the bigger issue is still ongoing for you. I think it’s time we take a brief step back. Can you verify for me (perhaps again) your version information, for both EE and MSM? Did you make the update to 2.3.1? And have you made sure to keep your MSM installation updated as well? The more we wrestle with this, I’m stating to think there may be a version mis-match between EE and MSM.

Thanks!

Right I’ve seen the messages before. What I meant was that the messages are showing up continually, not matter how many times they are dismissed, or how many times the page is refreshed. The important part of my last post was my suspicion that the hardcoded setting is somehow not being respected at all.

On both the live and dev sites, EE version is 2.3.1, MSM is Version: 2.1.1 Build: 20111011. To note: I’ve been having this problem for quite a while, since about 2.1 on my dev site, if I recall.

Thanks for your continued assistance.