Join us this Friday for AI in Action at the Virtual Happy Hour! This free virtual event is open to all—enroll now on Academy and don’t miss out.
Join us this Friday for AI in Action at the Virtual Happy Hour! This free virtual event is open to all—enroll now on Academy and don’t miss out.
Yes personalization works fine if you're just caching the block output. It's a primary reason to cache at the block level rather than page where this can cause issues with visitor groups.
Does anyone know if personalization works togher with Donut Hole Caching in Episerver CMS?
What I want to achive is to show different version of one block based on visior group in content area. This works in login mode, but not anoymous.
We were foreced to use donut hole cache because block in block publishing doesn't work with Episerver output caching (Correct me if I am wrong). Now we are trying to use personalization, but donut hole caching doesn't recognize personalization on the block. It just caches first loaded version and ignore the visitor groups I configured.
I also tried episerver output caching together with personalization, it works. Unfortunately block in block publishing doesn't work.
Here are the articles which inspired me:
://www.david-tec.com/2014/03/Enabling-output-caching-on-an-EPiServer-site-that-uses-Visitor-Groups
://www.jondjones.com/learn-episerver-cms/episerver-developers-tutorials/episerver-caching/how-to-implement-a-donut-hole-cache-in-episerver