trisager

@donncha – We are not caching html in Cloudflare (it doesn’t do that by default), we use it for security and to deliver static assets over the CDN. That has worked fine with WP Super Cache until now – and still does for websites that have comments disabled.

For websites that use comments: I suppose the updated version of WP Super Cache will show a cached page to users who leave comments unless “Disable caching for visitors who have a cookie set in their browser” is selected? (Which would completely disable caching because of Cloudflare’s __cdfuid cookie).

Could the old behavior be brought back as an additional option in a future update? Or is there some other workaround you can suggest?

For the past few days the daily report I receive via email from ManageWP has notified me that there are a number of plugin updates pending, but the ManageWP dashboard says no updates. Looking at wp admin in the individual sites confirms that it is the worker plugin that needs updating.

Hiding worker plugins in the dashboard is just confusing when implemented this way – better show it, possibly with a notification that it will eventually update itself.

From the plugin description: “This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.”

WordPress password protection is implemented in PHP, which is being completely bypassed when caching is enabled.

There are ways around this, but nothing that I can think of that doesn’t require custom programming (e.g. using JavaScript to retrieve the protected content).

Edit: If your intention is to completely hide the website behind a login, you can just use basic http authentication instead of the plugin. That should work with WP Super Cache.

Many hosting companies lets you setup http authentication via their control panel, or you can do it yourself by editing the .htaccess file.

• This reply was modified 7 years, 7 months ago by trisager.

Asked their support about same. Apparently expected behavior since they are “rolling out 2.5.0 in waves”.

Not sure I fully appreciate the logic here, but the gist is that it will eventually resolve itself – at some point the client update will be available for download. Doesn’t seem to break anything else.

Yep – makes the plugin fairly useless unless you happen to be in the timezone that the plugin assumes.