jwineman
Forum Replies Created
-
Forum: Plugins
In reply to: [Cloudflare] 3.0.1 breaks websiteHi @janworx,
What version did you upgrade to?
What happens when you try to access the admin panel?
Are there any errors in the PHP error log?Thanks,
JohnForum: Plugins
In reply to: [Cloudflare] Wordfence warning on update to 3.0Hi,
It looks like the upgrade failed. If you delete /home/HOME_FOLDER_NAME/public_html/wp-content/upgrade/cloudflare.3.0.0-n1WNba/ does it work?
-John
Forum: Plugins
In reply to: [Cloudflare] New version (3.0.0) crashed backendHi,
We disabled HTTP2/Server Push in 3.0.2 does upgrading to this version fix your errors?
Thanks,
JohnForum: Plugins
In reply to: [Cloudflare] Upgrade to 3.0 prevents site editingWe removed HTTP2/Server Push in 3.0.2 which I think is the root cause of your errors. Does upgrading fix it?
Thanks,
JohnForum: Plugins
In reply to: [Cloudflare] Error Log on 3.0Forum: Plugins
In reply to: [Cloudflare] Failed to flush CGI output to clientHi,
Is this fixed by upgrading to 3.0.2? Were you seeing 520 or 502 http error codes on the front end?
Thanks,
JohnForum: Plugins
In reply to: [Cloudflare] Can’t deploy 3.0 to WPEngine due to PHP syntax errorHi,
I’ve created a ticket to track this internally (PI-809). I’m not sure if this is something we can fix based on the link @cliffseal posted but we’ll try.
Thanks,
JohnHi,
If you upgrade to 3.0.2 is it fixed? We removed the HTTP2/Server Push functionality which I think was the root cause of your errors. Were you getting 520 or 502 responses?
Thanks,
JohnForum: Plugins
In reply to: [Cloudflare] What happened to v2?Hi,
Yeah its very similar to the Windows 8 to 10 thing.
Basically when the plugin was in beta we had it registered in composer as 2.x instead of 2.x.x-beta and so when we actually launched we were forced to a major version bump.
Thanks,
John- This reply was modified 9 years, 8 months ago by jwineman.
Forum: Plugins
In reply to: [Cloudflare] After Update to v3.0 I can’t enter in wp-admin over httpsHi,
Yeah 3.0 contained a bug which caused the headers generated by HTTP2/Server Push to exceed the limits on nginx and fastcgi. This resulted in customers seeing 520 or 502 http error codes when loading their site. This has been fixed in 3.0.2 because we removed the HTTP2/Server Push functionality.
Thanks,
JohnForum: Plugins
In reply to: [Cloudflare] Active Zone dropdown not workingHi,
We use the same front end across all our plugins. Some plugins support administering multiple domains however our WordPress plugin only supports administering the WordPress blog the plugin is installed on which is why the select box will always ever show a list of one.
Thanks,
JohnForum: Plugins
In reply to: [Cloudflare] Question: Why the changed features in 3.)Hi,
1) True Visitor IP restored.
3.x still supports restoring the original visitor IP. The code for this is found here.
2) “CloudFlare will be notified when you mark comments as spam”.
The API endpoint that CloudFlare sent spam comments too only existed in our V1 API which we are deprecating. Since there is no equivalent endpoint in our V4 API we were forced to remove this feature. We may reintroduce it in a future release assuming we recreate that old endpoint in our new API.
3) Toggling Development Mode on/off
We removed Development Mode in 3.x because we got a lot of support tickets where the root cause was a user enabling development mode, forgetting to turn it off, and wondering why CloudFlare functionality wasn’t working.
However 3.x still supports it, you can enable it by following the instructions here.
4) HTTPS Protocol Rewriting
We removed Protocol Rewrite because our implementation couldn’t handle a lot of edge cases and we were receiving too many support tickets. We plan on rewriting this functionality so that it can support all the edge cases we’ve seen in the next few weeks.
Thanks,
JohnForum: Plugins
In reply to: [Cloudflare] Invalid CSRF Token on 3.0.1I don’t think the PHP version should matter here. Are there any errors in the error log? Its possible the WP Nonce is failing to generate for some reason.
Forum: Plugins
In reply to: [Cloudflare] WHY 3.0 update has removed “toggle Development Mode On/Off” ??Hi,
You can enable Development Mode in the 3.x versions of the plugin by following these steps:
Change:
wp-content/plugins/cloudflare/config.js
"homePageCards": ["ApplyDefaultSettingsCard", "PurgeCacheCard", "PluginSpecificCacheCard"],
to
"homePageCards": ["ApplyDefaultSettingsCard", "PurgeCacheCard", "PluginSpecificCacheCard", "DevelopmentModeCard"],Now you should be able to toggle development mode on the plugin homepage.
Forum: Plugins
In reply to: [Cloudflare] Mixed content warnings with version 3Hi,
We removed the protocol rewrite functionality because our implementation had too many edge cases that it couldn’t handle. We’re in the process of redesigning it and should have a more stable implementation in a few weeks.
Thanks,
John