Hello,

I set differents languages to my sub-domains and I've got this "bug" very boring to me.

When I switch from sub-domains to main domain automaticaly set the language default of the main domain to the language of the sub-domain I come back from.

I don't know if it's normal... if I have to change something...

The default language of the main domain couldn't change like that... I think it's the cause of a translation problem I have.

Comments

junro’s picture

Title: Switch from sub-domains to main domain: ---> big problems... » Changing translations of a language of sub-domains change the default language of the main domain to the sub-domain we come from

Hum I don't know if you will understand... if not I will try to be more specific.

ps: It's not exactly when I switch from sub-domains to main domain. It's about translation use.

Very big problem.

junro’s picture

Title: Changing translations of a language of sub-domains change the default language of the main domain to the sub-domain we come from » Changing translations of a language of sub-domains change the default language of the main domain...

Changing translations of a language of sub-domains change the default language of the main domain to the default language of the sub-domain we come from.

agentrickard’s picture

Can you start over please? In the format:

1) I configure default language to do X from the form on page Y from domain Z.
2) I use module A to change setting B from the form on page C on domain Z.
3) D behavior occurs on domain Z on page E.
4) I expect to see F behavior on site Z instead

agentrickard’s picture

Component: - Domain Nav » Code

Why did you file this against Domain Nav?

junro’s picture

Can you start over please? In the format:

1) I configure default language to do X from the form on page Y from domain Z.
2) I use module A to change setting B from the form on page C on domain Z.
3) D behavior occurs on domain Z on page E.
4) I expect to see F behavior on site Z instead

euh I don't really understand what you mean, what you would like.

About Domain Nav, I don't know why I put that, mystake with my mouse, I didn't even have Domain Nav enable. Maybe I should...

agentrickard’s picture

I mean, please give me a detailed breakdown of the steps you took, the behavior you expect, and the behavior you experienced, including the page from which you set values.

You must use Domain Conf to set the domain-specific language variables. If you didn't do that, then this is "by design."

junro’s picture

ok, I will do that

ps: I'm using Domain conf to set the domain-specific language variables.

agentrickard’s picture

I cannot replicate this issue. Using all three forms of language negotiation (path only, path with fallback, and domain.) If using the domain method, you must ensure that the domain settings for the language match the configuration settings for the domain.

junro’s picture

Title: Changing translations of a language of sub-domains change the default language of the main domain... » Changing translations of a language of sub-domains change the default language of others domains

ok, here what to do to replicate the problem:

it's only one way to replicate it, but there is others ways.

Main domain --> default language: english

Sub-domain A --> default language: english

(Your are with B domain)

1. You want to change the default language of A to another language (download one you don't have).

2. /admin/settings/language -->Add language --> and import the new language.

3. /admin/build/domain/conf/A --> default language: your new language.

the default language of Main domain and others domains with english default language are OK, still have the english default language.

4. Switch to the domain A with the new default language.

5. And now go back to the main domain, you will have the last default language you set with the domain A.

IMPORTANT: It's not only the main domain but ALL ENGLIsH DEFAULT DOMAINS. Domains with others languages than english as default language are good.

6. You have to set back the default language of the main domain to english and it will set back all others domains with english as default language.

ps: it's the same problem when you want reimport packages with l10n module: /admin/build/translate/import/package

junro’s picture

StatusFileSize
new194.17 KB
new143.1 KB

Maybe something wrong with my configuration:

1.Advanced settings /admin/build/domain/settings --> see attach file

2.User Default Domain settings /admin/build/domain/settings --> see attach file

Languages settings: /admin/settings/language/configure ---> set on: Path prefix only.

Languages multilingual system: /admin/settings/language/i18n --> Content selection mode: set on: Current language and language neutral.

agentrickard’s picture

I suspect User Default Domains, which I have never used and do not maintain. What happens if you disable that module?

agentrickard’s picture

This could also be a UI issue. I believe that if you don't set a language for a domain, the form picks up the default, which could explain #6:

6. You have to set back the default language of the main domain to english and it will set back all others domains with english as default language.

If you don't set any value for a domain, it just silently inherits the default value.

junro’s picture

StatusFileSize
new436.64 KB

User Default Domains was enable, useless for me, my users are not assign to a default domain. So I disable it and will keep desable, don't need it I think.

1) reimport packages with l10n module: /admin/build/translate/import/package

Looks good!

2) Installing a new language

Always the same problem with the main domain, but it's wird because only one of my 4 sub-domains with english as default language has switched to the new language added.

ps: my enable domain access module in attach file

junro’s picture

Yes maybe you're right.

junro’s picture

Anyway it's not a big problem, when I will have all my languages installed, I should not have this problem anymore. (if reimport packages is ok).

Thanks for you're attention to this little problem :)

agentrickard’s picture

Well, this is a release blocker, so just saying "it is not a problem" is not a solution.

junro’s picture

Title: Changing translations of a language of sub-domains change the default language of others domains » Switch to a sub-domains with a new default language added change default language of others domains.

Sure, what I was saying is it's not a critical bug. As I will I new informations about it, I will report it here.

ps: I can't find a good title to this issue, because we don't know exactle where the problem come from. If you want to change it... in better english :)

agentrickard’s picture

This could be a i10n issue, since I have never used nor tested that module.

agentrickard’s picture

Status: Active » Postponed (maintainer needs more info)

This is not a release blocker.

junro’s picture

I will check all this, with l10n & i18n modules as soon as come back home in 3 days.

junro’s picture

Project: Domain » Localization client
Version: 6.x-2.0-rc8 » 6.x-1.7
Status: Postponed (maintainer needs more info) » Active

Looks like l10n issue (Localization client).

Anyway I prefer to move this issue there than i18n who have so many issues, and it's the same maintainer.

agentrickard’s picture

Interesting. I will monitor the issue.

mrgoltra’s picture

subscribing. I am getting this too.

gábor hojtsy’s picture

@Junro: l10n_client will not change your language anywhere, it just uses the language set for the page. I don't get why you assume this is an issue with l10n_client.

junro’s picture

Project: Localization client » Domain
Version: 6.x-1.7 » 6.x-2.4

Don't know, I still have this bug, sems to be a domain access issue, you're right :)

agentrickard’s picture

Status: Active » Closed (fixed)

DA does not support subdomain-based language switching. Only path-based.

May also be related to #745540: Conflict with i18nstrings (user defined strings not being translated on some sites / to some languages).

At this point, I need you to start over with a new issue so we can come at the problem fresh.