Closed (fixed)
Project:
Preserve language
Version:
6.x-0.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Jul 2008 at 12:22 UTC
Updated:
15 Jul 2008 at 16:05 UTC
> Drupal allows the content being displayed to be in a different language than that of the interface.
> However the links to view a translation of a given page force the interface language to that of that page.
> This module fixes this behaviour; when clicking on a link to a translation, the main interface language
> is not changed.
1)
Great that this is fixed with your module.
However, shouldn't it really be optional behaviour in core? Has it been written as a bug or feature request?
2)
I am going to use the i18n module. Will that also fix this behaviour, or do I still this module?
Cheers.
Comments
Comment #1
Alice Heaton commentedHi, sorry for late response I was on holiday !
No I didn't post a feature request - but you are right it probably should be optional in core. Do you want to do that or should I ?
You will still need this module. I suggest you try without and then with, and see the difference.
Note that I have noticed other problems relating to having the interface language different than that of the content in Drupal. As I'm just back from holiday today, I have to get back in to that :) but will extend the functionality of this module in the future to deal with other issues.
Does this answer your questions ?
Comment #2
-Anti- commentedHope you enjoyed your holiday.
Thanks for your replies.
> Note that I have noticed other problems relating to having the interface language
> different than that of the content in Drupal
That sounds like the language implementation all round - fixing something breaks something else!
> No I didn't post a feature request - but you are right it probably should be optional in core
I'm a noob at drupal and php, so such a request might be better coming from someone who
knows what they're talking about and exactly what kind of behaviour is needed, as well as
perhaps being able to make suggestions about how it could be done, or even writing patches.
All I really know is that the core language implementation doesn't function very well and isn't
very 'stable' in different situations. But I wouldn't have a clue how to test it methodically and
then accurately state solutions, especially ones that wouldn't interfere with what other users
might consider 'desired behaviour'.
Cheers.