HI Peter,
The reason for the templates doing the translation is because we want different templates for each portal plus the ability for the manager to change them and the quickest and most understandable way for managers to change things is to have this in the templates. Admittedly in some cases the text from the templates should be in the resx files, but these are there because that’s how we first did it and it never got changed!! In the next version of the temple system (NBrighCore https://nbrightcore.codeplex.com/ ) I have allowed for tokens to pickup resx data (http://docs.nbrightproject.org/TagTokens/TabId/148/eid/1492/modid/494/.aspx ), but in some cases it’s simply more simple and quicker to put it in the templates, but we have made this more simple by having a string replace token (http://docs.nbrightproject.org/TagTokens/TabId/148/eid/1266/modid/494/.aspx ).
Regards,
Dave.
The reason for the templates doing the translation is because we want different templates for each portal plus the ability for the manager to change them and the quickest and most understandable way for managers to change things is to have this in the templates. Admittedly in some cases the text from the templates should be in the resx files, but these are there because that’s how we first did it and it never got changed!! In the next version of the temple system (NBrighCore https://nbrightcore.codeplex.com/ ) I have allowed for tokens to pickup resx data (http://docs.nbrightproject.org/TagTokens/TabId/148/eid/1492/modid/494/.aspx ), but in some cases it’s simply more simple and quicker to put it in the templates, but we have made this more simple by having a string replace token (http://docs.nbrightproject.org/TagTokens/TabId/148/eid/1266/modid/494/.aspx ).
Regards,
Dave.