Bug List & Feedback

  • Resolved slavomir12

    (@slavomir12)


    3 months, 2 weeks ago

    Dear Developers,

    I would like to start on a positive note to offer some encouragement. Thank you for developing the Super Page Cache plugin. It is a brilliant idea and one of the most useful plugins out there. I truly appreciate your hard work and I am rooting for your success.

    The plugin is great in concept, but in terms of development, you are only halfway there. There is still a lot of work ahead. Currently, the plugin is extremely unreliable and, for the most part, practically unusable. Once you fix all the bugs, conduct thorough testing, and release a new version, please let me know—I would be happy to test it again to see if it works.

    Your documentation is also quite weak; I couldn’t find much information. I had to rely heavily on advanced AI models for advice just to get the plugin running, even in its current unreliable state. I expected the setup to take 10 minutes, but it ended up taking a day and a half of immense struggle.

    My Environment:

    • Server: OpenLiteSpeed 1.8.5
    • WordPress: Multisite version (WordPress Multisite version (version in the form of subdirectories, not subdomains).)

    Issues & Bugs:

    1. Multisite Compatibility: Have you tested this plugin on a Multisite setup? It seems likely that you haven’t. Please test it and fix the bugs related to this architecture.
    2. Erratic Behavior: The plugin behaves unpredictably. On one site within the network, the “Test Cache” shows everything is OK, but on others with identical settings, there are massive problems. There is no logical explanation for this inconsistency.
    3. mu-plugins: Deactivating mu-plugins did not resolve the issues.
    4. Reinstallation: Uninstalling and reinstalling the plugin did not help; the same errors persist.
    5. Cache Pausing: Pausing the cache in the settings only partially resolved some of the issues.
    6. Authenticated User Caching: The plugin cached pages for logged-in users. I viewed an article as an admin and it was served from cache. I had to use AI-suggested workarounds to add cookie-blocking rules for WordPress to stop this.
    7. Purge Cache & Updates: The “Purge Cache” function does not work. Updating an existing article does not trigger a cache refresh. I had to use CLI commands to force an update of the article content.

    Dear developers, please thoroughly test the editing process for existing articles and eliminate these bugs. Currently, it simply doesn’t work. The “Purge Cache” option in the post list is also non-functional.

    Thank you for your effort and I look forward to a more stable version.

    https://ibb.co/S4md321C

    https://i.ibb.co/ZpgYM3wD/Opera-Snapshot-2026-02-19-213515-dash-cloudflare-com.png

    • This topic was modified 3 months, 2 weeks ago by slavomir12.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Poonam Namdev

    (@poonam9)

    3 months, 1 week ago

    Hello,

    Thank you for taking the time to write such a detailed report and for the encouraging words about the plugin. We’re sorry to hear the setup was so time-consuming and that the plugin felt unreliable in your environment.

    To address a few key points based on the plugin’s intended behavior:

    1. Multisite compatibility
      Super Page Cache does support WordPress Multisite, however it must be configured per site in the network. Each site can require an “ad-hoc” configuration (and may even belong to a different Cloudflare zone/account), so it’s possible for the Cache Test to pass on one site and fail on another if anything differs at the host/zone/rules level.
    2. Caching for authenticated (logged-in) users
      Logged-in users should not be served cached HTML. In fact, bypassing cache for authenticated users is one of the core purposes of the plugin. The plugin uses a cache‑buster mechanism for logged-in sessions and also supports cookie-based exclusions (for both Cloudflare edge caching and the disk cache fallback).
      If you were served cached content as an admin, we consider that unexpected and we’d like to reproduce it.
    3. Purge Cache / updates not purging
      Manual purge actions (toolbar/dashboard) and automatic purge on site changes are supported features. Content edits should trigger purge when the relevant auto-purge options are enabled, and manual purge should work regardless. If the UI purge actions are doing nothing, that suggests either an environmental block (REST/AJAX/security layer) or a bug we need to investigate.

    If you’re willing, please enable the plugin’s logging and share:

    • whether each affected site is connected to the same Cloudflare zone/account or different ones
    • the Cache Test results per site
    • a short list of steps to reproduce the “admin served from cache” scenario
    • any relevant log output around purge attempts (UI purge + post update)

    Thanks again, reports like yours help us prioritize real-world stability, especially for multisite + LiteSpeed/OpenLiteSpeed setups.

    Thread Starter slavomir12

    (@slavomir12)

    3 months, 1 week ago

    Thanks for the reply. I have WordPress Multisite installed, some are not based on subdomains but on directories.

    Plugin Support rodicaelena

    (@rodicaelena)

    5 days, 1 hour ago

    Hi there,

    Thank you so much for the feedback!

    Please try updating to the latest version, as we’ve recently implemented several fixes that should make it work much better with WordPress Multisite environments.

    If you are still experiencing any of these bugs after updating, please go ahead and open a new support ticket for the specific issues so we can take a closer look and help you troubleshoot.

    Thanks again for helping us improve!

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.