Browsercaching is not the problem. We're not using a proxy server and it works on all other xslt's. What is different here is that this template is included like this
@cultiv - you're absolutely right about XSLTouch - the problem is actually a sideeffect (defect?) of using .NET's compiled transforms - not really an XSLT 1.0 issue. Just to be clear about that.
XSLT unwanted caching
Hi,
I have an xslt that, when saving it, does not change the output on the page.
If I recycle the app pool, and thereby cleares the cache, the output is updated with the changes.
My macro settings are standard:
Cache Period: 0
Cache By Page: Yes
Cache Personalized: No
What is going on?
IIS configuration?
I've always seen my changes immediatly so far (both on staging and live environments)
You have eliminated proxy servers, browser caching and such right?
Hi Rik,
Browsercaching is not the problem. We're not using a proxy server and it works on all other xslt's. What is different here is that this template is included like this
<xsl:include href="box.xslt"/>
Am i missing something here maybe!?
/Rune
Ah, the include only updates if you update it's "parent". This is an XSLT 1.0 quirk, as I undestand it.
Install this EXCELLENT package and you're good to go!
@cultiv - you're absolutely right about XSLTouch - the problem is actually a sideeffect (defect?) of using .NET's compiled transforms - not really an XSLT 1.0 issue. Just to be clear about that.
/Chriztian
Sorry Chriztian, to offend your favorite subject! ;-) I was always led to belief it wasn't Microsoft's fault, I stand corrected!
Ha ha - no offense taken - we all dig these discussions :-)
/Chriztian
Thanks guys for the tips. The XSLTouch package works like a charm. If I could I would High five all of you.
/Rune
Shouldn't this be placed in the umbraco core instead? It's a quite central problem, so why should it not be handled by default?
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.