Closed (fixed)
Project:
Internationalization
Version:
6.x-1.3
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
6 Mar 2010 at 23:59 UTC
Updated:
22 Jul 2010 at 11:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
kewlguy commentedI'm interested in this, so, where's the patch?
Comment #2
kewlguy commentedOOPs, All I needed to do was make sure I was in the admin and then change to the non default language on the setting page for the variables that I set in my settings.php. It would be nice to be able to utilize my l10n translator though...lol.
Comment #3
g10 commentedgood question, obviously I forgot to attach it, here you have it:
Comment #4
kewlguy commentedSWEET! My i18n and l10n client works like a charm after I applied this patch, of course with the additions to my settings.php
The only real issue I have left is one with the core 'contact' link in my primary menu though I believe it is an issue with my Acquia Marina theme, tabs specifically because the sidebar block now works correct after this patch. I know too much information...lol
I have created a somewhat related post in the i18n issues about an open discussion that I would appreciate seeing a little feedback on. please check it out on this post here
Comment #5
Rakward commentedSorry, posted in wrong thread, meant to post here:
http://drupal.org/node/583836#comment-2900142
Comment #6
jose reyero commentedLooks like a good idea. This needs some static caching and handling fallbacks (if the variable is not translated for that language, it should default to the variable in the default language)
Comment #7
jose reyero commentedAdded i18n_variable_get()