Login to secure pages, site with multiple contexts, and Babel

I can't for the life of me figure this out! I've googled around and can see that a few others have had this problem, but no solution is helping me.

I have a site with multiple contexts, a context per language. "web" is english, additionally there is a "fr" and "de" context. Babel is installed to handling language linking.

There are some members-only pages on the front-end that need to login and password to access. The resource group and user groups are setup according to the tutorials on the modx site.
The user can login to the "web" context's secure pages, but not to the "fr" or "de" secure pages. The user settings and resource group settings are identical for all contexts though.
The admin can login to any secure pages, but only if he/she is logged into the manager already.

Using the Login plugin with ! so it's uncached.

Any tips would be greatly appreciated!
Thanks in advance.
Alex

Did you include the &contexts attribute in the Login call?

Thanks for your reply.

I did try various combinations of &contexts

&contexts=`web,de,fr`

trying to login to `de` from the web context.
trying `de` only from the de context.

nothing seems to work for us.

Can anyone confirm that they are using Babel, SEO friendly setup, and the Login plugin, without problems?

If I knew that someone was using a similar setup successfully it would give me hope at least that this is solveable.

we're using Modx v2.2.6 with most recent Babel and Login versions.

Can confirm, this is working, if you have setup all permissions for all usergroups/contexts correctly

@Bruno17, thanks for the confirmation! That at least is good news and I know where to dig.

I will post the solution/problem when I've localized it.
In the meantime more tips are still welcome.

The context should be with their real name, like they are in the Site's tree first node per context

is "de" is Deutsch, and "fr" - French, so:

&contexts=`web,Deutch,French`

You must refer to "context name" not to "cultureKey" name.

Thanks nickyz

"de" is also the context name in our setup. web, de, & fr are the context names, culture keys are en, de, fr respectively.

We probably should have named it "Deutsch" and "Francais", but now it's set and it does not look like Modx will easily allow changing the context name until version 2.3 is out.

I don't think this is the problem.

Quote from: alexgustafson at Apr 17, 2013, 06:37 AM

Thanks nickyz

"de" is also the context name in our setup. web, de, & fr are the context names, culture keys are en, de, fr respectively.

We probably should have named it "Deutsch" and "Francais", but now it's set and it does not look like Modx will easily allow changing the context name until version 2.3 is out.

I don't think this is the problem.

I have similar setup as yours and it works with context names. I thought you might be using by mistake culturekey instead.
I have no clue why this is not working for you.

@nickyz, thanks for the tip though. next time we will give our contexts better names. I also thought that &contexts needed the cultureKey, so it's good to know it needs the name for future reference.

Nice to hear again that it is working for other people. There is hope!