Very Good, but…

Hi, @n0m0r3

I’m sorry to hear about your trouble with Guest Mode and UCSS. These options should be disabled by default. As with all advanced functions, we recommend you try them before enabling them, as every site is different, and some themes absolutely may not work with some advanced optimization features.

Just to clarify, did you enable Guest Mode on all of the sites you maintain? Or are you saying the plugin broke your sites immediately upon upgrade without any changes to your configuration?

If it’s the latter, we would like to speak to your further, as this is not expected behavior. You can connect with us on Slack, or open a ticket. We’d appreciate it. Thanks.

Lisa,

I didn’t touch in anything. All sites have auto-update enabled because never in my life I see any update change a cache engine and CSS optimizations without a notice.

Guest Mode are not the culprint, it works ok but without CSS combine, Stale Cache, Asynchronous CSS and of course UCSS.

In fact, many things related to QUIC.cloud are broken now. Full of LQIP, Critical CSS and images served throws 404, 403 and many JS errors in console.

It’s clear to me that you guys want us to pay more on QUIC.cloud servers and force us with this insane update.

If you want to introduce a new function, don’t destroy the old one! Just make a option, not a imposition! Or be clear on the update and aware your users about all changes and risks (Elementor does this all the time)!

I’m still fixing all this since yesterday, loosing a lot of time and money and changing Litespeed plugin with any alternative that works, are stable and reliable!

• This reply was modified 3 years, 2 months ago by NOMORE.

I’m very sorry to hear about this.

The fact is, any new features should be disabled by default in order to avoid this exact problem.

It sounds like something went wrong in this case, and if you are willing, we’d like to chat with you about your configuration to determine what might have happened here.

If you’re up for it, please join us on Slack in the #wpcache channel, or open a ticket. Mention this review, so the support team has the back story.

Thank you!

Thanks for the response Lisa, but I’ll pass.

Next time if u need BETA TESTERS, just asks and give me the option to choose before expose all my sites to this beta version advertised as a final build branch.

I will let you guys figure out this one, because I already pointed where the problem is, no need to repeat myself again as many users are pointing the same.

Understood.

Just one clarification, though: v4.x was put through several months of testing on hundreds of sites before release. There must be something about your sites’ configurations that is different than those of any of our testers, which is why we think your feedback would be valuable.

If you change your mind sometime in the future, just drop by our Slack workspace where we test our pre-release versions.

Best wishes.

Hi, @n0m0r3

I just wanted to let you know that we have discovered an issue where QUIC.cloud quota consumption unexpectedly increased for some users after upgrading to v4. It sounds from your review that maybe this is what was happening to you.

(We had anticipated some increase in usage, which is why we had doubled the amount of free credits for Page Optimization. But there is one scenario where credit consumption increased quite a bit for some sites, and this was unintentional.)

You can disable CCSS by URL under Page Optimization > CSS, and your quota consumption should return to normal.

We’re genuinely sorry for this oversight, and would be happy to issue complementary credits for any unexpected usage. Please contact us about this on Slack or open a ticket.