Ticket #5409 (closed Bug: wontfix)
Second site language settings is ignored and follows the primary (default) site settings
| Reported by: | siamakz | Owned by: | hannosch |
|---|---|---|---|
| Priority: | major | Milestone: | 2.5.1 |
| Component: | Internationalization | Version: | |
| Keywords: | Cc: |
Description
This is the same bug report as Ticket 5408, I have repeated it since I forgot to enter my id. Sorry for the repetition
I have installed Plone 2.1.2 for Windows package and want to have two independent sites one for English language and one for Persian. I have also installed PloneLanguage? Tool 0.9 on each site. The first site is the default Plone site and the second one I created in the root through the ZMI (logged in through port 8080 and created the second site at the Root Folder of Zope -- this is not a nested site).
The problem is that the second site follows the language settings of the primary (default) site. If I set the first one as English (through Language Settings) and the second one as Persian(Farsi) both sites come up in English. Now if I switch the settings around then both sites come as RTL in Persian (Farsi).
I tried also to turn off the Smart Folder in the Navigation Settings and it did not have any effects.
In my view this (language settings )should be a straight forward settings. My two sites are dev.kargar.net and dev.kargar.net/farsi. These are my development sites and there are no customization on this sites, I only have tried change tabs and languages, before I make a decision in migrating my Plone 2.0.5

I strongly suspect this is a cookie-related issue; since you've using the same name for both.
[BTW, if the orginal author comes back to read this: when you have two sites in one Zope, and one is the "standard" one that is on 8080 and 80, like yours, always visit them as http://dev.kargar.net and http://dev.kargar.net:8080/farsi (note the 8080). Otherwise, subtle and weird things happen because you end up looking for the farsi object in the main site, going up into Zope and finding it via acquisition. But strange things abound. This would also fix your cookie issue, since your browser should keep different cookie for port 80 than port 8080]