5.x updates

I’m with the OP on this.

The following doesn’t really address any extended features that would be useful for people of make use of the plugin just for the Cloudflare integration. Until the issues related to Cloudflare are addressed properly (which btw have not really been addressed even with version 5.0.1). I think the safest option is to remain on version 4.7.13.

[Version 5.0.1 (2024-08-28)

• Fixed critical error produced by the Cache status bar
• Fixed Test Cache functionality and reliability for Cloudflare
• Improved the domain rules for caching

Version 5.0.0 (2024-08-27)

• Super Page Cache for Cloudflare is now becoming Super Page Cache. While you can still enjoy the Cloudflare functionality, it is now optional. The plugin will work for your non-Cloudflare sites as well, with much more to come.
• Fixed compatibility issues with PHP 8.3
• Fixed an issue with the user survey]

Hey,

That’s totally valid point and I appreciate the feedback. We’re working on 2 upcoming releases that I hope it would improve things for everyone:

1. 5.0.2 We would release soon a new version that is fixing a couple of issues, including a better migration of the page rule to cache rule + lazy loading in the free plugin. This would also introduce a PAID version that at the start would offer Delay & Defer functionality and a great way to support the future development.
2. 5.0.3 We’re planning to take full advantage of the cache rules and allow users to bypass cache for urls, query params or cookies, at the CF level. ^ we’ll be also adding in the PRO version a transform rule aimed to improve the HIT rate by ignoring marketing parameters.

Super Page Cache often provided stuning results, and I have enjoyed that very much.

However, I just found out that 61 sites have all content updates stuck in cache fo the last 10 days, since 5.0.
Even setting up CPC again from scratch does not resolve it.

I am bulk-removing the plugin everywhere. Perhaps I will revisit one day, just can’t deal with it any other way today.

For anyone dealing with this issue while using CF workers:
You need to either diable caching in the plugin (which removes the worker), or remove the CF worker manually. Leftover workers can still cause problems.

@kpbryce132, I’m glad you brought up the general issue. A lot of us don’t like the direction this plugin is taking. Presumably, the original author sold it to Optimole, who are understandably looking to monetise the plugin.

But we old users prefer a plugin that does one thing well, at no cost to us: configuring CF page cache. Which v4.x did well.

So it’s probably time for someone to fork v4.7.13 and maintain it as a separate plugin for the community, fixing the occasional bugs as they arise. @isaumya, you are obviously the person best suited for the task. But I guess others could step in if you’re personally happy with v5.x.

Hi @prestonwordsworth,
Yes, the plugin is now being updated and maintained regularly with a Pro version in the works. You are right about monetizing it. You can absolutely stick to using v4.x

But I would suggest to give this new version a try at least. As the optimal team is working really hard to introduce many new features to the plugin and even the ability to use it without Cloudflare (if such a situation arises). But whatever was in the free plugin does remain there – along with the new support for the cache rule which is a million times better.

No plugin can survive without monetization. Someone has to pay the bill for all the development hours. Besides my full-time work + providing support here I barely get any extra time.

I think the main issue here is the upgrade issue to v5.x which I’m sure will be ironed out soon. And after that, the free plugin can be used with cache rule without ?swcfpc=1 cache buster query param and so on…

Nice to have your perspective, Saumya.

Let me come back to kpbryce132‘s original remark and just add one more point. The root cause of all this fuss around v5.x is really that the new plugin is not production-ready. We’d expect that a commercial outfit such as Optimole had a mature process for testing and releasing software. That’s not the case here.

So, yeah, if Optimole simply add paid features and don’t break anything, fine. What’s deplorable here is they took over the plugin and start breaking people’s production sites, as many a post here attests to.

@prestonwordsworth that’s fair. It’s true that due the lack of familiarity with the product there have been some issues, we’re trying to learn and be responsive & fix quickly. If you want to be on the safe side, just don’t update right away, since sometimes there might be scenarious that we couldn’t foresee.

Otherwise as @isaumya mentioned, we need to generate some revenue in order to be able to continue to support the plugin, otherwise, it doesn’t make sense to use revenue from users paying for our other products, to support this plugin, which is free, we can use that to support the products & people that are paying us.

We don’t plan to limit the free version in any way and you’re free to use an older version for as long as you want.

I agree with @prestonwordsworth.

I love this plugin. It is active on many live websites. A new version of the plugin that is not tested fully can be very detrimental to the visitor experience and make the website essentially inoperable. Optimole has a vested interest in making sure this does not happen, regardless if the plugin is free or a paid version.

If you want happy users and high ratings then then each plugin version must be solid and reliable. Don’t excuse poor testing and claim it is because the plugin is “free”. Always remember that the WordPress CMS is also “free” and the developers do an excellent job of testing and support. That is always the way it should be!

• This reply was modified 2 months ago by kpbryce132.

Hey,

I appreciate your feedback and I never said that releases with issues are an excuse because the plugin is free.