Thread

This question may be related to a resolved thread.

Tried the solution above but did not work.

I have site A (the first default site) and site B.

Set up like this:
└── siteA.domain.com
  ├── admin.php
  ├── index.php
  ├── images
  ├── system
  └── themes
└── siteB.domain.com
  ├── admin.php
  └── index.php

admin.php in domainB:
$assign_to_config[‘site_name’]  = ‘siteb’;
$assign_to_config[‘cp_url’] = ‘http://siteB.domain.com/admin.php’;

I want the user that logs into CP via http://siteb.domain.com/admin to only see Site B in CP.
And the user that logs into CP via http://sitea.domain.com/admin should only see site A.
Now he is both able to switch between sites if he logs into default sites CP and also site A is the default site no matter what url or user I try.
When logging into CP via site B:s cp the user can not switch between sites, but ends up in the wrong site to start with.

If I set the group permissions in site A for group B so that it does not have CP access they can not login to CP via http://dommainb.com/admin (and not http://dommaina.com/admin for that matter)

How do I acomplish what I want?

v2.5.3 - Build Date: 20120911
MSM 2.1.4 - Build: 20120911
Bugfix: msm_member_groups.zip

I see even more strange things in MSM. It seems that it is not working at all as described.
Is the latest version buggy or am I doing things terribly wrong.

Perhaps the bugfix : msm_member_groups.zip destroyed things even more?

Hi Peter,

The Bug fix does work, but only for Groups created after it’s been applied. Previously created groups still exhibit the error prone behavior.

This is very like a cookie domain issue, so I’d like us to get a quick look if possible? Be on the lookout for an email from EllisLab!

Cheers,

Turned out to be a querky domain issue- going to siteb.me.com/admin.php was actually pulling up sitea.me.com/admin.php.  So it was then thinking it was sitea.

Weirdness!

Once the server issue was squared away, things looked good.