Ionut Neagu

Hey,

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

That would help, I couldn’t replicate this on my side.

Thanks for reporting this, we didn’t considered this edge case, but would be fixed in the next release.

Hey,

I could not replicate this so far, we’re still looking into it.

@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.

Hey,

Right, we reverted the previous version approach since it was not done properly to a version that matches what the page rule is doing, it is what it should be and should work fine.

In the next version we would update the rule with the dynamic exclusions you have in your settings ( cookies, urls).

Can you help me with the error? What exactly did you disabled and got this so we can replicate and fix? Also disabling the entire cache causes the error Invalid Page Rule identifier (err code: 1002)

Hey,

Yes, but with this not being a widespread issue, we’ll be waiting to bring multiple improvements and fixes together, so it would be out in around a week.

Hey,

The rule was updated in the last update, but you need to disable/enable the cloudflare cache for that to update.

Let me know if it works.

no, it should not, we’re looking into this.

Have you tried cleaning the browser cache?

We haven’t changed any of the Cloudflare functionality really in this version, we just allowed everyone to use it without Cloudflare as well.

The undefined was cause from a browser cache problem, clearing would have helped.

this is all fixed with the new release, thanks for understanding.

Hey,

Yes, we’re considering this.

Hey,

How do you find the new version? Anything you like? Dislike?

thanks!

@jpsws other than the reported issue, how do you like the release? Anything that you find useful or not so?

Thank you very much for the review!