• Resolved Tom Dupuis

    (@tomdupuis)


    I’ve read older support threads where you say with LiteSpeed Cache, nothing is needed except making sure “fallback page caching” should be disabled in Super Page Cache.

    But on the FAQ page inside the plugin, you recommend disabling cache (in LiteSpeed Cache). Then “Automatically purge the cache when LiteSpeed Cache flushes all caches” should be enabled in Super Page Cache… which it is by default.

    • Which one is correct? And when using the 2nd option, should fallback page caching be enabled?
    • Should we also enter our Cloudflare info in LiteSpeed Cache under “Cloudflare API?” or leave it blank?
    • Should we use the LiteSpeed Cache crawler or Super Page Cache preloader?

    Love your plugin, just trying to clarify things for LiteSpeed users.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter Tom Dupuis

    (@tomdupuis)

    One more question. Guest mode/guest optimization should be disabled when using your plugin as it’s not compatible with APO?

    Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    If you are using LiteSpeed server this is what you can do:

    1. Disable all kind of page caching and guest mode/ guest optimization features in the LS Cache plugin
    2. Use the LS Cache plugin only for static file optimization like CSS/JS etc.
    3. When using this plugin make sure you are not using the official Cloudflare plugin and APO is disbaled.
    4. You can use LiteSpeed Cache Crawler, I think as it is a server level operation, might be more efficient than the preloaded which I personally never recommend anyone using anyways as standing in 2023 it is not needed.
    5. Inside the LS cache do not enter and Cloudfalre API details, all CF operations are handled by this plugin.
    6. If you choose to have a fallback cache, then enable fallback cache inside this plugin and disable all kind of page caching inside litespeed cache plugin. Only use it for static file optimization.

    Hope this helps.

    Thread Starter Tom Dupuis

    (@tomdupuis)

    Thanks for the detailed response iSaumya, it did help.

    Plugin Contributor iSaumya

    (@isaumya)

    Hi Tom,
    Happy to hear that. ??

    hwajidaliattari

    (@hwajidaliattari)

    I have done all the above steps, but when I published new post or update any post it is still showing me old cache data.

    I also try some aditional settings but nothing work for me.

    Here are my log file and settinghs screenshots: https://drive.google.com/drive/folders/1IRNa8jvbi7cm1hRQ3oFf0Y34y6tgGIaO?usp=sharing

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @hwajidaliattari,

    1. Inside the cache tab of the plugin settings I see you have Purge whole cache option selected instead of purging related URLs. Unless you are doing cache by device type uncheck that option.
    2. Go to any page and post and click the update button. Then check the debuig.log file and check if you are seeing a purge on post edit being fired.
    goldfinger1964

    (@goldfinger1964)

    Too bad @hwajidaliattari’s link is no longer available.
    1) in Cloudflare CDN, in Speed > Optimization > Auto Minify: should they have the JavaScript, CSS and HTML flag?
    2) using LiteSpeed Cache + Super Page + Cloudflare CDN, in Cloudflare, how should the Speed and Caching page settings be?
    3) to use LS Cache plugin only for static file optimization, in LS Cache what should I set/configure?

    I think this is useful information because someone who is not a great expert like me, had to disable your Super Page plugin otherwise the performance would get worse!

    Plugin Contributor iSaumya

    (@isaumya)

    As I said before, use the LS Cache plugin only for static file optimization while this plugin will handle page cache. For code minification, you can use the auto minify option inside Cloudfalre.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Using LiteSpeed Cache + Super Page Cache’ is closed to new replies.