Hi @ravanh,
Thanks for trying those LiteSpeed settings and for sharing what you found. You’re right that the root cause is the server-side cookie check, so when the page is served from cache, the server never gets a chance to read the eucookielaw cookie and the banner state is baked into whatever was cached first.
The approach proposed in the issue you’ve linked (moving the visibility check to JavaScript so it runs in the browser after the page loads) is the right direction, and our team is now actively working on making the block cache-compatible. I can’t give a specific timeline, but it is on the radar.
Just be aware you may need to remove the workaround once the official fix ships to avoid any conflicts. Glad you found a working solution, and thanks for flagging this.
-
This reply was modified 1 day, 10 hours ago by Kyle Smith.
