Hello Magnolians :)
I've been developing against the CE since v5.3.6, and I'm loving the new
yaml-based configuration stuff.
However, I've noticed for a while now (since 5.4?), that whenever I deploy a
yaml template defition to a magnolia instance running in production mode, the
change is correctly picked up in the resources app (I can see it is overriding
from the file system), but doesn't apply when viewing a page with the template.
I have managed to work around it by applying a jcr hotfix in the resources app
and then removing it, at which point the file system version is correctly used
in the template.
I'm using the latest CE v5.4.5 with relevant magnolia.properties:
[code]
magnolia.resources.dir=${magnolia.home}
magnolia.resources.classpath.observation.pattern=.*\\.(ftl|yaml)$
magnolia.develop=false
[/code]
I had a quick look on jira to see if there were any open issues like this, but
I can't seem to find any.
Does anybody have any ideas?
Regards,
Kris
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=cb152bdd-955d-4cba-bca9-1c9ff3c8a6b5
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
