Konstantin Kovshenin

Thank you so much for the kind words Greg!

Top-level or subdomain doesn’t really matter for Surge. If the message shows up it means that it’s having trouble updating the WordPress configuration file (wp-config.php) to enable page caching, and/or creating the wp-content/advanced-cache.php file. Make sure the former is writable by the user executing the script, and the latter does not exist (often left from a previous caching plugin).

Hope that helps!

Yes, fpassthru has to be available. Most reputable hosting providers will have this function enabled.

Thanks Jason, I appreciate the review!

No problem. Doesn’t really look like a very common (or maintained) library to be honest, but also not relevant to this conversation. I’m not here to fix your plugin, or any of its upstream dependencies. I came here to share my experience with this product.

I’ve never used it, don’t even know what it does. I just logged into some WordPress site and it blew up in my face, begging for a review. So here I am, simple as that ??

Here’s a screenshot. Can’t believe none of the 30k users pointed this out before, so here’s one I found with a 4 second search. Also makes it within the gray area of the plugin guidelines and soliciting reviews, but I’m not here to argue about that.

Yeah, there is some binary in the file. Here’s how it’s generated.

Hope that helps!

Thanks for the kind words James, glad you like the plugin!

Thanks for the kind words, will certainly consider it for future updates!

The get_option() functionality is not related to Surge or page caching, so the problem is very likely elsewhere. You could try and disable all active plugins and activate them one by one, to identify the one that’s causing this problem.

Hope that helps.

Thanks for the feedback @xintv123, will certainly keep that in mind for future iterations around configuration in Surge.

> In addition, is this plugin disable cache for logged in users?

Yes, logged in requests will not be cached.

Hi there! We do not have plans to integrate a CDN option for Surge at this time, so you’ll have to find a different plugin/solution that will handle CDN for you, perhaps BunnyCDN has a recommended one.

Thanks for using Surge!

You can change the plugin configuration using a config file. Here are some examples:

https://roytanck.com/2022/01/13/tweaking-surge-by-adding-a-configuration-file/

Hope that helps!

Thanks so much for the review @sicknick!

These should be fixed in 1.0.4.