[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bärfuss updated MAGNOLIA-2803:
--------------------------------------
Fix Version/s: 4.1.1
Priority: Critical (was: Minor)
> i18n and ${...} / cms:out
> -------------------------
>
> Key: MAGNOLIA-2803
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2803
> Project: Magnolia
> Issue Type: Bug
> Components: templating
> Affects Versions: 4.1
> Environment: Magnolia 4.1 CE
> Default settings for i18n (with i18n set to enabled, of course)
> Reporter: Igor Klimer
> Assignee: Philipp Bärfuss
> Priority: Critical
> Fix For: 4.1.1
>
>
> Hi all,
> I've run in into the following problem:
> First off - I'm using Freemarker for my templates (very cool stuff, great job
> on introducing this :))
> Now, using the guide on the wiki
> (http://wiki.magnolia-cms.com/display/WIKI/Introduction+to+I18nContentSupport)
> I managed to i18n-ify my pages, however it only works when I output the
> values in the template using the cms:out tag - it doesn't work with the very
> nice Freemarker syntax ${content.something}. This is all using the default
> templates from the STK 1.1.
> As per
> http://www.nabble.com/i18n-and-cms%3Aout---%24%7B...%7D-td24234038.html I
> created this bug report so this matter can be looked into :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
