Closed (fixed)
Project:
Localization client
Version:
6.x-1.3
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
2 Sep 2008 at 07:12 UTC
Updated:
23 Sep 2008 at 11:02 UTC
I've tried to get this module to work with no success so far.
The situation:
- I am logged in as admin (uid 1).
- L10n client is enabled.
- I have set English as the default language and Finnish as a secondary language.
- I have created a translation of a page with i18n. The page has all of its static texts inside t() functions.
- The texts are visible in 'Translate interface', and I'm able to translate them normally from there.
- No success with an editor account either, which has the 'use on-page translation' permission enabled.
- Language negotiation is set to 'Path prefix only', and it works as it should.
- I haven't seen a toolbar yet! :/
What can still be wrong?
Comments
Comment #1
wwalc commentedTook me a while to figure it out - you have to set the default language to any other than "English". That did the trick for me.
Comment #2
mnordstrom commentedThanks for your answer. This however didn't do the trick for me, and I also found out what was actually wrong.
I changed my custom theme to Garland for a while and got the translation box immediately. My theme is practically just html and php in the templates since we need loads of customization, and apparently it doesn't know that it should be able to print out something like this.
Is there some code snippet that I could attach to the template(s) to get this to work?
Comment #3
gábor hojtsy@convulsion: I think the "print $closure" part was missing for you in your theme.
Comment #4
mnordstrom commentedThanks, got it to work!
The previous comment came in handy too, since I in addition to the $closure-thing now had to make a custom English language to be the default. I still don't understand the reason for this behavior, it's apparently not a bug?
Anyway, maybe these things could be mentioned about in the README? They both seem to be essential for the modules performance and are kinda hard to guess.
Comment #5
gábor hojtsyI've updated the project page recently, and also added what was in the readme, that you need a "foreign" language displayed on the page to show the interface. It does not make sense to show the interface on English pages, since Drupal does not support translating from English to English, unless you add a custom English language which you'd like to use instead of the built-in interface.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.