Anubis2702 Posted October 8, 2018 Share Posted October 8, 2018 Hi guys, anyone can help me with this weird issue? I have built my own module and the BO translator tries to translate it as a native module in index.php/international/translations and not in index.php?controller=AdminTranslations, obvious throws error 'There is no translation file available.' Link to comment Share on other sites More sharing options...
NemoPS Posted October 13, 2018 Share Posted October 13, 2018 How did your format the string? Make sure you add the dorrect d=, like d='Modules.Facetedsearch.Admin' Link to comment Share on other sites More sharing options...
jstillings1 Posted October 13, 2018 Share Posted October 13, 2018 My guess is you used a boilerplate for the module that the translations module is recognizing as a module it knows how to deal with in the BO natively. I would probably just go change the namespace as we call it in c# not sure what its called in Symphony wrapper. Link to comment Share on other sites More sharing options...
Anubis2702 Posted October 13, 2018 Author Share Posted October 13, 2018 Yes I've changed the module name/namespaces and now it is working with the legacy translator. Not sure what was wrong since it worked fine when I've buit it in ps 1.7.1 and the module name was dresscustomizator so no way ps use this name for any native modules. The strings are formated with mod='module_name' not d= Link to comment Share on other sites More sharing options...
jstillings1 Posted October 15, 2018 Share Posted October 15, 2018 Anubis2702 glad ya got it working. From what i have noticed, the JQuery call in PS 1.7.4.2 has changed a lot. NemoPS hinted at this change in his reply. If you look at your themes JS file you may note it could be completely anonymous functions and the parameter it is passing is now called d= vs the old one where mod= worked. I think by renaming it you triggered a feature in PS where it does like auto update of your code and it search replaces things, but not real sure and this is just a guess. Do a file compare to whats working on live and your Github version and see if there is JQuery parameter changes. Also note Core now has a version of JQuery in it and if your module is loading it's own that could be an issue. I have seen other mod authors report this is the case. Hope this helps. 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