-
- 195 Posts
Hey guys,
I noticed something off about a site that I've upgraded to 1.0.12 from 1.0.10. It's using a [[Personalize &yesChunk=`yesChunkHere`]] snippet and inside its YesChunk chunk, is a call to {{anotherChunk}}. Inside {{anotherChunk}}, I'm using [[Ditto]] to output some filtered results. It seems to have been broken when I updated to 1.0.12. Anyone else encountered this problem?
The main problem:
Calling {{aDifferentChunk}} within the YesChunk chunk of the [[Personalize]] snippet will result in a broken front end.
Here's what my work around is at the moment:
Copy the contents of {{aDifferentChunk}} and use them directly within the YesChunk chunk of the [[Personalize]] snippet. There seem to be no problem with using the [[Ditto]] snippet within the YesChunk directly.
-
- 24,544 Posts
Caching is kind of funky in Evolution, especially with nested objects like you have. Attempts to fix it in new versions of MODX can cause side effects.
Did you try making the page itself uncached?
In revolution, you can start any tag with
to make it uncached, which helps to solve this kind of problem.