• I originally left a one star review for this plugin due to not being able to purge the cache and see site updates no matter what I tried.

    Having tracked down my issue it turns out that whilst my problem was indeed caching, it was not LiteSpeed, it turned out to be Cloudflare.

    I have spent some time testing the plugin today in order to give a more accurate review.

    I have found the plugin to be highly configurable but easy to use with it working well out of the box. Exclusions are easy to add and the interface is a pleasure to work with.

    I quote my original review text below in order to provide context to the high standard of support I received here from LiteSpeed customer care and a LiteSpeed developer, both of whom were quick to respond and were dedicated to resolving the issue.

    I would not hesitate to recommend this plugin for those looking for a way to interact with their LiteSpeed cache from within the WordPress back end. I can give the plugin a 5 star review now having thoroughly tested it today.

    Thanks so much for your patience and time @lclarke and @hailite, greatly appreciated. Apologies for the impulsive 8am rant review.

    Below is the initial review:

    “Yet another aggressive cache that does nothing more than waste developer’s time while wrestling with it to see site updates and get back to the work I’m actually being paid for.

    Genuinely, I would love to see plugin authors forced to pay developer fees for this.”

    • This topic was modified 6 years, 9 months ago by weeblz. Reason: Plugin re-evaluated
    • This topic was modified 6 years, 9 months ago by weeblz. Reason: typo
Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support LiteSpeed Lisa

    (@lclarke)

    Hi, @weeblz

    I’m sorry to hear you’ve had a rough time with our plugin! If you have a moment, I’d love to know exactly what you found problematic. It may be something we can help you with.

    In the meantime, we have extensive documentation that may be of some assistance.

    Let me know if there’s anything we can do to help!

    Plugin Support Hai Zheng?

    (@hailite)

    Hi @weeblz,

    Before we received this one star review, we didn’t receive any post or email from you. If you have any question, you can ask in forum first. Also we have a full API doc. I believe this could be a better way to fix the problem for a developer.

    Best,
    Hai

    Man, no love on Valentines Day – you must be confused @weeblz – read the other reviews. You seem to be mistaken. I don’t work for these guys, but there are days it seems they work for me – supporting an amazing FREE CACHE PLUGIN. Do your research first. Might need to check if you even have a Litespeed server you’re trying to use too… Just saying your post comes across as you’re working for another cache company!

    Thread Starter weeblz

    (@weeblz)

    @lclarke The issue I had was that I was unable to purge the server cache using the plugin.

    I tried all of the back end purge all options and the admin bar option.

    I even tried on a fresh install of WordPress using an unmodified 2017 theme (apart from a test CSS rule in the main style sheet) with yours being the only plugin installed. Furthermore I tested with caching disabled in your plugin with no effect.

    I appreciate that all the evidence would point towards this being a server issue rather than something your plugin has caused however, I cannot be expected to rate the plugin well when it does not work at all in my case.

    @hailite It’s great that you guys have a forum and API however you must appreciate that not everyone has the time to troubleshoot these things, I left this review at 8am after being up all night to hit a deadline and spending a couple of precious hours going back and forward with my hosting company to try to figure out why the plugin and the server did not appear to be communicating correctly. Caching is one of those great innovations that users require to “just work” and in my case (again I appreciate I am not in the majority) it “just doesn’t”.

    @hmsre Happy Valentines Day to everyone involved however, for my use case specifically, I am not mistaken. Perhaps you should take your own advice regards research, this amazing FREE CACHE PLUGIN is an ancillary product to support their paid product which is the server technology. I am also 100% certain that I am on a LiteSpeed server.

    I contend that I sound more like a developer who has been up all night and achieved less than he hoped because of issues that had nothing to do with the actual project.

    If the plugin is working well for you then great, feel free to leave an honest review. It doesn’t work for me so I did the same.

    Plugin Support Hai Zheng?

    (@hailite)

    I understand your situation as a developer. Can you tell a bit more on unable to purge cache? Before purge, did you see it hit the cache? Also how did you try to send the purge request? Is it by call LiteSpeed_Cache_API::purge_all()
    from https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:api ? Did you check the debug log? There should be something at least, no matter if it purged or not.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    Thank you, @weeblz, for your honest feedback. I wouldn’t expect you to rate the plugin in any way that doesn’t reflect your own experience, so no worries there.

    I appreciate that you may not have the time to dig into the issue any further, but if you do find the time later, we’d like to help. If you create a ticket through our client area or by sending email to [email protected], we can take a closer look at your server setup. It does sound like you might have something going on that is peculiar to your setup, and we’d need to see it to know how to advise.

    Thanks, and I hope you get to catch up on your missed sleep soon!

    Plugin Support Hai Zheng?

    (@hailite)

    Back to the beginning, I want to confirm your question is under this situation:

    1. You have cached pages when visiting frontend page. This means when you check the response header, you can see hit. Is this correct?

    2. You try to send the purge request, but failed. When you visit the frontend page, you still see hit while not a miss. This is what you mentioned failed to purge, right?

    Thread Starter weeblz

    (@weeblz)

    @lclarke @hailite Thank you both for your responses and willingness to troubleshoot this issue, I will continue to communicate via the email address that Lisa provided so that I can provide log in information etc. should you wish to review the install.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    You’re welcome. Happy to help!

    Thread Starter weeblz

    (@weeblz)

    @lclarke @hailite Issue has been resolved, I have updated my review to reflect my thoughts on the plugin now that I have had a better chance to fully evaluate it. Thank you both so much for your patience.

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    It’s really nice to see the issue was resolved. I just have to ask @weeblz not to provide login data in future or suggest to provide it. We disallow that here on www.remarpro.com and the plugin authors can get into trouble for it.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    @weeblz I’m so glad to hear you found the problem! Thank you for coming back to let us know, and for updating your review. It is much appreciated.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Fails to purge – Revisited’ is closed to new replies.