ggalow

Can you share more details? There was a bad plugin release (v3.8.1), so if that is the version of the plugin you have please upgrade to the latest.

v3.8.3 of the plugin should be released soon and should resolve some of the issues with this. See this PR for more info: https://github.com/cloudflare/Cloudflare-WordPress/pull/301

If after updating to v3.8.3 you still are having issues, please let us know.

v3.8.3 of the plugin should be released soon and should resolve some of the issues with this. See this PR for more info: https://github.com/cloudflare/Cloudflare-WordPress/pull/301

If after updating to v3.8.3 you still are having issues, please let us know.

Please follow this github issue for updates: https://github.com/cloudflare/Cloudflare-WordPress/issues/297

Marking this thread closed in lieu of that.

If you api key or api token are changed/rolled/expired then yes that will cause issues in the plugin. Unfortunately right now you need to remove and re-install the plugin, I think, so you can provide new auth.

You need to uncheck the ‘disable cache’ option in dev tools. If I recall correctly that sends a header that will bypass cache for that request and fetch from origin. Try fetching the site again without that option selected and let me know if you are still seeing issues.

yes unfortunately doing anything in the plugin with CF with 3.8.1 will trigger some nasty issues: We posted this https://community.cloudflare.com/t/cloudflare-wordpress-plugin-update-critical-error/210206/10?u=adspedia on how you can get out of that bad state. Unfortunately there isn’t 1 solution since many providers and wordpress setups vary greatly.

caching everything without having exceptions in place for dynamic content or purging content when it gets updated can cause issues.

We just released APO: https://blog.cloudflare.com/automatic-platform-optimizations-starting-with-wordpress/ as a way to automate doing this kind of thing for customers.

I believe this is fixed now, let me know if its not, but either way its cosmetic from what we have seen.

We currently don’t have a logout button. The current workaround is to remove the plugin and then re-add it.

ah hm interesting. Yeah that is NOT related to WP or APO, but I will make sure folks are aware internally. thanks

@mddsharp can you be a bit more specific about what you are seeing?

We just released 3.8.2 of the plugin which contains a fix. Please install that version of the plugin

@europljanin & @brandsteve can you either open up support tickets with more details or reply on github here: https://github.com/cloudflare/Cloudflare-WordPress/issues/238

information if you can provide it:
-wordpress version
-mysql version
-version of CF plugin you upgraded from
-any error logs you have
-list of steps that you took that got you into that state

We haven’t seen this in any of our testing, so the more info given the more likely we can try and reproduce it ourselves.