Configuring caches

  • tucason

    (@tucason)


    2 months ago

    I’m using newest version of your plugin + CF for static files and Litespeed for cache.

    Configurin your plugin driving me crazy, there is no manual how to configure both (your plugin is designed for woocommerce, also litespeed is cache designed for woocommerce) but your only tutorial for cache is ‘check if your event_id is doubled, if yes disable cache….’

    Referers are dropped when user redirect from landing page (cached) to checkout (not cached), also with utm, sometimes it persist sometimes not, lost like 40hours to resolve this, but im still in the same place, thats why im writing here.

    Why you can’t write manual like other plugin developers? like this: https://docs.utmgrabber.com/books/102-getting-started-for-handl-utm-grabber-v3/chapter/there-is-no-utm-collected

    We should ignore query strings, if yes what or all? ignore cookies? phpsession cookie? there are so many questions but zero answers.

    • This topic was modified 2 months ago by tucason.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author PixelYourSite

    (@pixelyoursite)

    I am not aware of any significant issue with Litespeed, or any other popular cache solution.

    It’s a good idea to describe the actual problem that you have and send a link where we can replicate it. You mentioned Referrers, do you mean the data we track as events parameters, or the data some of the scripts track (like Google Analytics).

    As for tutorials about using caches, you can direct the request to the cache plugin itself since this is the factor that modifies the behaviour of other plugins.

    jetmg

    (@jetmg)

    I believe there are significant issues with PYS and popular cache / optimize solutions, including WP Rocket. I also spent many hours trying to solve that, but with no long-lasting success. Had several pages affected. In WP Rocket case, PYS tends to be ‘missing’ from some pages (while all other page functionalities, and content are fine). Clearing cache helps, but only for a while – which makes pinning down the problem even more frustrating. Only excluding selected pages from cache helps – PYS works fine then. But – obviously – pages excluded from optimization work slower, so that’s not a proper solution.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Tags