Closed (works as designed)
Project:
Drupal core
Version:
6.6
Component:
language system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Dec 2007 at 20:17 UTC
Updated:
23 Nov 2008 at 13:54 UTC
Yesterday, I tried the new beta. Install was far better than D5 (thanks for the good work). After install, I imported the arabic translation from D5, and made it the default language (btw rtl support is awesome). Now, changing language from the language switcher doesn't work. If I change the default language from my profile, the language switcher works again.
I don't know if this is related with http://drupal.org/node/146084
Comments
Comment #1
abderrahim commentedSorry, I forgot to complete the title
Comment #2
gábor hojtsyYou see language swicther links in the block, but clicking on them does not work? Can you copy here the link targets of the links in the block? ie. http://example.com/en/node/1 etc.
Comment #3
abderrahim commentedfrom the main page, arabic links to ?q=ar/node and english links to ?q=node but both show the arabic version. (arabic is configured as the default language)
Comment #4
gábor hojtsyLet's think through what you are doing. If you have "Path prefix with language fallback. If a suitable path prefix is not identified, language is based on user preferences and browser language settings." mode used, when you don't have a path prefix, the language is identified by your user setting or browser setting or you don't have a user preference. Do you have this mode selected? In this case, what you observe seems to be normal behavior.
Comment #5
abderrahim commentedYes, this mode is selected.
So the bug is that english doesn't actually have a prefix. I guess this bug can be closed as a duplicate of http://drupal.org/node/146084 with adding this comment.
Comment #6
gábor hojtsyWell, this is not a bug then to be more precise :) You selected the mode where the language was discovered based on user settings and in your case, the same language was selected. Actually, a nice improvement would be to redirect to the language specific path in this case, but then again, if you don't have a language specific path prefix/domain set, we cannot redirect. Requirements for different language modes clash here. Anyway, I'll reconsider #146084 thanks.
Comment #7
greggles@abderrahim - does the patch I provided in 146084 fix the problem for you?
Comment #8
abderrahim commentedYes, but I had to reinstall ( I think this is normal since the modification is in the .install file)
Comment #9
hovel commentedLanguage selection conflict cause by English not having a language path prefix.
Occurs in multilingual, non default English, websites.
Implied default: When no path prefix is given (eg: my.website.org) then English is the default.
In the following situations there is a conflict which makes that it is not possible
to select or switch to English, neighter by the language switching block nor by
using a path prefix because English does not have a path prefix.
1: A language different from English is set as default.
2: Language negotiation setting "Path prefix only" is set.
3: Language negotiation setting "Path prefix with language fallback" is set.
In my opinion it is not a question of if but when it gets implemented!