mod='nameofthemodule' really necessary?

[Thierry]

I was following the indications given by shagshag on how to use module's templates in your theme.

 

For this you have to put the module's templates in : /themes/[your_theme]/modules/[module_name]/

 

I wanted the texts to be translated with the theme and not the module so I deleted all the "mod='nameofthemodule'".

But the Translation tool still put the texts in the module's translation and not in the theme's translation.

 

So I am asking. Does "mod='nameofthemodule'" do something? What is his purpose since it doesn't seems to attach the translated text to the module?

[Thierry]

Without mod='nameofthemodule', if I translate the expressions. They are not displayed on the FO.

 

So, the BO is seeing them as expressions to translate as module translations. But the FO don't display the translations.

 

Is this a bug ? Or I am not understanding how it works?

[shagshag]

Hi,

 

if you add mod='module_name' on /themes/[your_theme]/modules/[module_name]/ files,  translations will be translated with the theme.

 

In Back Office >> Tools >> Translations >> Module translations

 

You should have a box called "prestashop - module_name" and a box 'your_theme - module_name'

 

Is that what you wanted ?

[Thierry]

I find the actual behaviour a little weird...

 

Without mod='module_name', I can go to "Back Office >> Tools >> Translations >> Module translations"" to translate the expressions.

And I have the two boxes "prestashop - module_name" and "my_theme - module_name"

 

The only difference without mod='module_name', it's just that the translated expressions are not displayed on the Front Office.

 

I thought mod='module_name' was needed by Prestashop to detect the expressions which were belonging to a module. But, as I can see, Prestashop can find them alone. I guess mod='module_name' is only needed for the display, and does not act as a scope like I was expecting.