Bug: 2 XsltResult in one template with diferent XsltFilename return result of first one
Hi, I try use 2 xslt results on one template, but it second one - with different XsltFilename render result of first one. Even when I try change XsltFilename of second one to nonexisting filename same behavior occured, it render output of first one.
Bug: 2 XsltResult in one template with diferent XsltFilename return result of first one
Hi, I try use 2 xslt results on one template, but it second one - with different XsltFilename render result of first one. Even when I try change XsltFilename of second one to nonexisting filename same behavior occured, it render output of first one.
A little sample code would help - not sure exactly what you're talking about.
Regards
.Hauge
Do you have two different macros pointing to the same XSLT file?
Other than that as .Hauge said, we'd need a bit more info!
Tim
Hi Petr,
Do both controls have different ID's? If not, try that.
What version are you using? 1.0 or 1.1?
Otherwise I'll replicate the situation tonight and release an update. Are both controls pointing at xsltfilenames or using the inline xslt?
Cheers,
Chris.
Hi, I use v1.1.
Code sample - in my template:
But second XsltResult render same output as first one. I then try macro for verification and it render correct output.
When I change second result to
It still render output of first xslt result.
Adding id's solve problem!
Will be great if id isn't necessery, or add warning to documentation.
Thank you for help
Glad you solved it.
I added a note to this effect in the update (see top of the project page), but will make it clearer.
I'll look to remove this restriction in the next release, i'm not happy with this restriction either.
Chris
Caching is enabled by default?
There's 2 different caching params; one for the xslt loading and another for the resulting html output from the transform.
The former is on by default, the latter is off by default.
The 1.1 release was sparked from http://our.umbraco.org/projects/xsltresult/xsltresult-general/3471-Caching
is working on a reply...