Problems with cache system 1.7.6.9

[mk2-pronat]

I've heaving issues with LSCache Module 1.5.3 .It seems to conflict with my GPR module GDPR Compliance Pro + Google Consent Mode v2.2.25 - de PrestaChamps.My server runs LS cache so it's optimal as far as my host tels me however i can't make it to work with the GDPR module, if it's disabled i get HITS if it's enabled it misses.

I deactivated everything and only Smarty cache. I deleted and purged everything and even manually deleted the var/cache still can't get it to work...

[ComGrafPL]

Both modules doesnt work or just one? Or this one is just one module GDPR Compliance Pro + Google Consent Mode v2.2.25?

I have some hosting side LS cache module and GDPR from seigi ( the free one ) works fine.

 

[PrestaHeroes.com]

You've only found the obvious issues so far — with PrestaShop caching there are usually many more problems hiding underneath.

https://docs.litespeedtech.com/lscache/lscps/troubleshoot/  the mention that 1.7 in particular is a problem child and you should hire someone loool.

PrestaShop pages are dynamic by design. The native “cache” options are not real full-page caching — they only store template fragments or database results. Because of this, external cache modules often create inconsistent behavior like stale prices, wrong stock, or sessions not updating.

Historically the only somewhat reliable layer has been basic object caching (like Memcache), and even that is known to cause stale data problems because cache invalidation in PrestaShop is weak.

Many older developers will remember when Varnish first became popular — a huge number of shops broke due to cached carts, wrong pricing, and session conflicts. The same risks still exist today with aggressive cache modules.

In practice, the safest approach is:

Use Smarty cache + CCC only
Rely on PHP OPcache and proper server tuning
Avoid full-page cache modules unless you deeply understand the risks

Based on the troubleshooting described for this module, I would personally recommend not using it. It’s likely to create more instability than performance gain.

Edited February 20 by PrestaHeroes.com (see edit history)

[mk2-pronat]

@ComGrafPL The only module that i can figure out so far that causes this problem(doesn't prive cache) is GDPR Compliance Pro + Google Consent Mode v2.2.25. After the elaborate explanation given by @PrestaHeroes.com (btw thank you for this), it seems that the problem is much deeper.

I've contacted the GDPR Compliance Pro + Google Consent Mode v2.2.25 developer and told me that this most likely is because of LS Cache miss configuration and the module should work. This should work is not helpful at all but indeed i could not achieve Enable LiteSpeed ESI enabling because it doesn't "like" something and i can't figure out what.

In the meantime, i've routed the website through cloudflare but it seem that i ran into other problems.

Thank you anyway for the information, i will try to dig deeper.

[PrestaHeroes.com]

PrestaShop generally does _attachment not play well with full Cloudflare proxying. In most cases, the most stable setup is to use Cloudflare primarily for DNS management, not for aggressive caching or optimization features.

For CloudFlare and to avoid issues with sessions, cart behavior, geolocation, and dynamic content, only specific records should be proxied (orange cloud) — typically the main domain and www record.  Use CF for DNS only.

https://app.screencast.com/hGyYBn9IusbHh

 

Edited Monday at 05:11 PM by PrestaHeroes.com (see edit history)

[Nickz]

5 hours ago, mk2-pronat said:

In the meantime, i've routed the website through cloudflare but it seem that i ran into other problems.

People make their shops load in under a second, then put on cloudflare, resulting in the users needing 2 minutes average to pass thru.