Hi @rcscott,
Thanks for your report and I’m sorry to hear that. I was just able to confirm this warning. We will fix this in the next update.
On a side note: If this is on your “live” website and you’re seeing this message, it means you have WP_DEBUG set to true. I would recommend setting this to false, or at least set the WP_DEBUG_DISPLAY to false. You can do so by adding this to your wp-config.php file:
if ( ! defined( 'WP_DEBUG_DISPLAY' ) ) {
define( 'WP_DEBUG_DISPLAY', false );
}
By setting this, the warnings and notices will no longer be displayed to you and all your visitors.
Kind Regards,
Barry Kooij
define( ‘WP_DEBUG’, false ); is in my wp-config file. I also have WP Rocket installed and it was working correctly with Cloudflare 4.14.0.
After I saw the warning messages in Cloudflare 4.14.1, I deleted its directory through ftp and uploaded the zip file for 4.14.0 that I downloaded. Since I activated that version of the plugin, I now see the following fatal error when I try to clear the WP Rocket cache:
Fatal error: Uncaught Error: Class “CF\WordPress\Hooks” not found in /home/83/05/2910583/web/wp-content/plugins/wp-rocket/inc/ThirdParty/Plugins/CDN/CloudflareFacade.php:22 Stack trace: #0 /home/83/05/2910583/web/wp-content/plugins/wp-rocket/inc/ThirdParty/Plugins/CDN/CloudflareFacade.php(32): WP_Rocket\ThirdParty\Plugins\CDN\CloudflareFacade->set_hooks() #1 /home/83/05/2910583/web/wp-content/plugins/wp-rocket/inc/ThirdParty/Plugins/CDN/Cloudflare.php(344): WP_Rocket\ThirdParty\Plugins\CDN\CloudflareFacade->purge_everything() #2 /home/83/05/2910583/web/wp-includes/class-wp-hook.php(343): WP_Rocket\ThirdParty\Plugins\CDN\Cloudflare->purge_cloudflare(”) #3 /home/83/05/2910583/web/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array) #4 /home/83/05/2910583/web/wp-includes/plugin.php(522): WP_Hook->do_action(Array) #5 /home/83/05/2910583/web/wp-content/plugins/wp-rocket/inc/functions/files.php(910): do_action(‘rocket_after_cl…’, ”, Array) #6 /home/83/05/2910583/web/wp-content/plugins/wp-rocket/inc/common/purge.php(465): rocket_clean_domain(”) #7 /home/83/05/2910583/web/wp-includes/class-wp-hook.php(341): do_admin_post_rocket_purge_cache(”) #8 /home/83/05/2910583/web/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(”, Array) #9 /home/83/05/2910583/web/wp-includes/plugin.php(522): WP_Hook->do_action(Array) #10 /home/83/05/2910583/web/wp-admin/admin-post.php(82): do_action(‘admin_post_purg…’) #11 {main} thrown in /home/83/05/2910583/web/wp-content/plugins/wp-rocket/inc/ThirdParty/Plugins/CDN/CloudflareFacade.php on line 22
If your WP_DEBUG is set to false and your website is still showing warnings, you can force it to stop by adding this line below the define(‘WP_DEBUG’, false); line:
@ini_set( 'display_errors', 0 );
Regarding the WP Rocket cache error, this was indeed fixed in 4.14.1.
Could you please add that line to your wp-config.php and upgrade back to 4.14.1 to see if that resolves both the warning and WP Rocket cache issue.
I upgraded back to 4.14.1 and added the line to wp-config. Everything seems stable now and the warnings are cleared.
I’m using both WP Rocket and Cloudflare APO. I see the message below in the Cloudflare plugin, but the response headers otherwise look ok. WP Rocket’s cache was already cleared. Can you confirm if there’s anything I need to do?
“cf-edge-cache response header is missing! Please clear any server cache used via other plugins.”
-
This reply was modified 5 months, 3 weeks ago by
rcscott.
@rcscott great to hear the notice and the WP Rocket errors are gone!
Regarding the cf-edge-cache notice, I’ll look into this and will get back to you. This might take a day or 2 due to the weekend. I’m sorry about that.
Day 1 of my Holiday vacation was spent disabling the Cloudflare plugin due to this issue on over 20 client and personal websites. Had to do it via FTP to even reach my admin login screen on most of them. None of these sites had WP Rocket.
All complained about /wp-content/plugins/cloudflare/vendor/symfony/polyfill-intl-normalizer/Resources/stubs/Normalizer.php
Hey @jasonh1234,
I’m very sorry to hear this. We’re working hard on a fix for this warning and will push one most likely coming Monday. In the meantime you can revert back to version 4.13.0, until the next update is released. You can download version 4.13.0 here: https://downloads.wordpress.org/plugin/cloudflare.4.13.0.zip
Please let me know if there’s anything I can help you with.
Kind Regards,
Barry Kooij
Hello @rcscott
I am also facing the same issue and showing the error, whenever I save the WPRocket Settings or clear the wp-rocket cache,
I have replaced the plugin with version 4.14.0 and this also didn’t help, as whenever I try to clear the cache from wprocket, it still gives an error!
It only works if cloud flare plugin is deactivated.
Please help to identify the issue.
Thanks
Abdullah
@abdullah17 please downgrade to 4.13.0 until we’ve released the fix. See my previous post on how to do this.
This took down my blog also! It caused a critical error that made the admin area AND front end unreachable!
To regain access to my blog, I had to do:
/var/www/xxx/wp-content/plugins$ sudo mv cloudflare/ cloudflare_broken/
This is an extremely careless update. It shows a lack of testing before pushing this out!
-
This reply was modified 5 months, 3 weeks ago by
James.
@hydn hi James, I’m sorry to hear that! We do have a testing process prior to release but this happened because of a bug in our build process combined with a specific PHP extension. We will definitely discuss this internally and improve our testing process.
We have a patch ready for development, waiting on internal processes currently.
Again, I’m very sorry about this situation.
Kind Regards,
Barry Kooij
@barrykooij We can understand this may happens! I’ll check with 4.13.0
Thanks for prompt response.
Thanks & Regards
@abdullah17
@barrykooij Thanks for the follow-up and explanation. No worries.
@barrykooij This is a reminder of my other message in this thread:
I’m using both WP Rocket and Cloudflare APO. I see the message below in the Cloudflare plugin, but the response headers otherwise look ok. WP Rocket’s cache was already cleared. Can you confirm if there’s anything I need to do?
“cf-edge-cache response header is missing! Please clear any server cache used via other plugins.”
@rcscott Thank you for the reminder. We are currently in the process of releasing an update to fix the “Cannot declare class Normalizer”.
I will get back to you regarding the “cf-edge-cache response header is missing” warning as soon as I can.
