In my soy templates I use
{getText('com.foo.header')}
for i18n. The keys are available both in English and German. There seems to be a problem with caching:
If the template is rendered the first time for a user with a German locale, all other users will see the German text. This cache is valid until I reinstall the plugin. This just affects localized texts but not other dynamic data.
Example (with Fritz and James, who use different browsers):
There seem to be issues with caching: https://answers.atlassian.com/questions/108544/disabling-soy-caching
But I can't reproduce this problem with Soy Templates used by Atlassian. It occurs both on a dev and a production system. Am I missing something?
Jira 5.1.8
<component-import key="soyTemplateRenderer" interface="com.atlassian.soy.renderer.SoyTemplateRenderer"/> <web-resource name="foo" key="foo"> <!-- transform calls to AJS.getText() inside JS files --> <transformation extension="js"> <transformer key="jsI18n"/> </transformation> <!-- Make available to the client-side in JS as well... --> <transformation extension="soy"> <transformer key="soyTransformer"/> </transformation> <resource type="download" name="MyStatus.soy.js" location="/templates/status/mystatus.soy"/> <context>atl.general</context> </web-resource>
Hm, I didn't find any difference to the way Atlassian uses Soy besides the missing
<property key="content-type" value="text/javascript"/>
But setting the content-type didn't help.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.