mojosavingscom

Thanks, I didn’t realize it wouldn’t support the sitemap index. Wouldn’t the preloader still be helpful for generating the fallback cache pages, even if Cloudflare doesn’t keep pages it deems too low traffic? That way when a CF miss happens it doesn’t have to go running PHP but can at least have a static page to pull.

Thanks! I’ll look into that if any problems persist. Even when I was having problems before, the advanced-cache.php file was exactly as it is now. So it doesn’t seem that Rocket is doing anything to that particular file.

Regardless, right now this is what I’m getting in Lighthouse:

So until it breaks again I’m not touching it ;). Seems I finally found the perfect combination to make google pagespeed happy and have a site that’s blazing fast.

Thanks you wordpress wizard!

So oddly enough deleting that file before activating it again did help. I notice that when WP Rocket is disabled that file becomes 0 byte size but is still there. Before, I know I had checked that file (because I suspected it might be an issue) and it was definitely the one created by SPCFC, but the problem persisted. So maybe having that 0 byte file there threw something off with the setup.

It still causes one odd anomaly on my site (a mega menu loads incorrectly on all posts, but somehow is totally normal on all pages) but that’s a minor annoyance on a menu that I’ll probably be getting rid of anyway.

I was even able to re-activate WP Rocket to use it’s other (non-caching) features, and so far so good after making two new posts and clearing every cache a couple times to thoroughly test it.

I’m wondering if part of the issue may have also related to the option to clear HTML only (which I also changed). Perhaps some CSS was getting left behind which was combined/minimized or otherwise not what was expected and getting found somewhere in the bowels of an nginx cache file.

As a suggestion, maybe a third option would be nice. “Clear HTML, CSS, Fonts, etc. but not Media”. That way larger files like images don’t need to be cleared but we can still clear everything else when say a theme update is pushed out and it gets tweaked.

In any event, thanks for an awesome plugin! Please keep up the good work. I look forward to one day buying the pro version with all the bells and whistles (combine/minify CSS, javascript, unload unused js, lazyloading, etc) of other caching plugins.

Thanks for the reply, I think I did try manually removing that file before when I was testing, but maybe not in that order. Let me try it again and see.

I might have to request a refund then (just bought yesterday). Two step verification will undo any increase of signups gained by switching to a spinner.

Yes, but this presents a problem for those of us who don’t have trivial “winning” prizes like coupon codes to give out. If we want to use it just for a giveaway of a bigger prize, and only ONE prize, not two or three different prizes, we can only go as low as a 1% chance because your system forces the winning segments to add up to 100%.

So we need to be able to drop the global odds to much lower, like 1/10,000 as suggested. Otherwise, we have to make up some fake “win” ones that are actually losses to add up to the required 100% total.

At the very least let us add a percentage onto a losing, no prize, segment to make up the necessary 100%. Then we could combine the odds to get the necessary odds.

• This reply was modified 4 years, 2 months ago by mojosavingscom.
• This reply was modified 4 years, 2 months ago by mojosavingscom.

I think this should be a development priority. I was looking to use this on a coupons site (so we don’t have our own coupons to give out) to use as a prize giveaway incentive. But 1 in 1000 odds would be shelling out a fortune for a site that literally makes only pennies per visitor.

I’d love to be able to have a 1 in 5000 chance option where I could justify giving away a $100 Amazon gift card for that many signups.