ggalow

still showing that it supports PHP version 7.2

we are still supporting php 7.2 even though it technically just was EOL’d recently.

Looks like we need to bump the tested version number too. We have done some tests with 5.6 and haven’t found any issues thus far, but I need to check if our automated testing is using 5.6 yet. We have found that it is very rare that a WP minor version update affects our plugin although it is possible.

• This reply was modified 3 years, 9 months ago by ggalow.

This will not require changes by customers using the plugin other than updating the plugin. Cloudflare will update the plugin as necessary.

This will mean though that after the removal of those endpoints, older versions of the plugin will no longer be able to fetch analytics since they will use these old APIs.

Ah I see. Well their Method 1 assumes that you use a shared hosting provider for hosting your website that would support ‘1 click install’ via cPanel for Cloudflare. There are other ways of hosting your website which would not allow for such things. Their Method 2 is what most customers of ours do given they don’t use cPanel or shared hosting providers.

as far as “are there any limitations on the plugin?” The plugin is widely supported across providers and WP versions. The plugin itself does not let you control every aspect of Cloudflare, but presents a subset of likely more relevant controls and actions you can perform in your WP site instead of needing to go to our dashboard. It also helps with avoiding SSL loops and purging static assets when you do things like update your theme.

I hope that helps!

You should contact our support team to get specific help regarding Cloudflare Registrar. This forum is only for support with the Cloudflare WordPress plugin.

You must already have a Cloudflare account and have onboarded your domain into the account before you can use our plugin with WordPress.

Can you be more specific as to ‘which’ tutorial you are talking about?

• This reply was modified 3 years, 10 months ago by ggalow.

In general the plugin itself should be compatible with any other plugin though of course we cannot test every combination of plugins ourselves.

For APO specifically see this this support article for supportability with other plugins: https://support.cloudflare.com/hc/en-us/articles/360049822312-Understanding-Automatic-Platform-Optimization-APO-with-WordPress#h_01EQ44V6KRFM6Z0F06MM0EJGJ5

Yes 3.8.8 caused performance issues for certain wordpress sites with large numbers of posts. This was tracked in https://github.com/cloudflare/Cloudflare-WordPress/issues/351 and has been reverted in 3.8.9 of the plugin which we just released.

In 3.8.8 there was issues for sites with large numbers of posts. 3.8.9 reverts the changes and should not have the issue.

this is being tracked here: https://github.com/cloudflare/Cloudflare-WordPress/issues/316 as joshbeci raised.

The plugin supports API Tokens. We recently fixed an issue with some permissions. There is an API Token template in the dashboard you can use to get a token with all the necessary permissions to use with the plugin.

Unfortunately, I can’t tell you whether you should or shouldn’t disable any plugins you may be using, as there are too many possibilities (and too many other plugins). In general with APO, we will serve more of your site from cache, which might lessen the benefit of other plugins. Depending on the specific capabilities, some of the optimizations by other plugins may still be useful though when we do fetch from origin.

I personally haven’t used Hummingbird myself, so I can’t confidently give a recommendation.

Hi, version 3.8.1 of the plugin caused a fatal error which is likely what you ran into. It was not directly related to APO, but just an issue in the release process of the plugin.

If you need help resolving any issues, check this community thread first as it has some recommendations: https://community.cloudflare.com/t/cloudflare-wordpress-plugin-update-critical-error/210206/8

Updating the plugin to 3.8.2 or higher will resolve the issue.

Sorry for the issue, but glad to hear it is resolved!

Unfortunately the 3.8.1 release of the plugin had this issue. It has since been fixed, so please update to the latest version of the plugin – currently: 3.8.2 but later today it will be 3.8.3