-=peter=- Posted January 4, 2015 Share Posted January 4, 2015 Hello. I'd like to put all my custom translations under single module, so it's easy to deploy. So I created the module (say trmodule), added it to the displayHeader hook and in the templates used {l 'my text' mod='trmodule'}. (to be more precise {addJsDefL name=myText}{l s='my text' mod='trmodule'}{/addJsDefL} I'd like to point out here, that the module doesn't have it's own tpl file. Problem is, that in the BO translations I see the line my text' mod='trmodule (note the quotes) and also the translation doesn't work. What I'm doing wrong? Link to comment Share on other sites More sharing options...
-=peter=- Posted January 4, 2015 Author Share Posted January 4, 2015 So after some digging in the code I found the mod parameter is valid only for the modules. What other option I have to easily deploy my own translations for (my) strings in the theme files? Link to comment Share on other sites More sharing options...
vekia Posted January 4, 2015 Share Posted January 4, 2015 I'd like to point out here, that the module doesn't have it's own tpl file. so where you added "{addJsDefL name=myText}{l s='my text' mod='trmodule'}{/addJsDefL}" ? Link to comment Share on other sites More sharing options...
-=peter=- Posted January 5, 2015 Author Share Posted January 5, 2015 (edited) This was in product.tpl in the theme. To clarify what i want to achieve is, to have my custom strings at one place and that I would be able to import language pack with no worries of overwriting. Edited January 5, 2015 by -=peter=- (see edit history) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now