Caching of some XSLT files, Umbraco setting? or server setting?
Hi all,
This was originally raised by @azzlack in this post: http://forum.umbraco.org/yafpostst6371umbracoNaviHide-hides-everything.aspx
I hope someone can help me with this:
After making changes to some xslt files and refreshing, changes don't appear. When I check back the next day roughly 12 hours later it's updated and working (or in some cases partly working because I've changed it so many times)
I was wondering if anyone knows if this is a cache setting within Umbraco or if it's a server setting? Keeping in mind this only happens with certain files specifically ImageListItem.xslt related to the NitroGallery.
Do check the Macro settings for the two macros that point to the xslt files you mentioned. The Macro settings have cache options and it sounds as if there is a cache time set on those macros that you'll have to wait to expire before you see the changes.
While developing, I leave macro cache times at 0 (no caching) and then as I near production I use the ?umbDebugShowTrace=true querystring to watch the macro times and determine which macros can be cached and what a reasonable duration might be.
Caching of some XSLT files, Umbraco setting? or server setting?
Hi all,
This was originally raised by @azzlack in this post:
http://forum.umbraco.org/yafpostst6371umbracoNaviHide-hides-everything.aspx
I hope someone can help me with this:
After making changes to some xslt files and refreshing, changes don't appear. When I check back the next day roughly 12 hours later it's updated and working (or in some cases partly working because I've changed it so many times)
I was wondering if anyone knows if this is a cache setting within Umbraco or if it's a server setting? Keeping in mind this only happens with certain files specifically ImageListItem.xslt related to the NitroGallery.
Thanks in Advance
tika
Do check the Macro settings for the two macros that point to the xslt files you mentioned. The Macro settings have cache options and it sounds as if there is a cache time set on those macros that you'll have to wait to expire before you see the changes.
While developing, I leave macro cache times at 0 (no caching) and then as I near production I use the ?umbDebugShowTrace=true querystring to watch the macro times and determine which macros can be cached and what a reasonable duration might be.
cheers,
doug.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.