Brandon Hubbard

Hey Chris,

Sounds great, myself and my team would love to help out, let me know when its on Github!

@saintblue

We have pushed out an update we believe resolves the issue, please let us know if you continue to have any issues.

@saintblue We believe to have discovered the cause of the issue, it was only affecting some hosting providers.

To be clear my advice to turn off error reporting was just to hide the errors until a fix was released.

Hi @saintblue

Can you provide us some information and we can look into it:

* Your website url:
* WordPress Version:
* PHP Version:
* Hosting Provider:

Most of these issues appear to be Warnings, so while we will look to address the issue, you can remove the warnings by disabling debug mode for WordPress.

@smartalec10 I am gonna close this request as we are reviewing the issue on Github. Here is the link for anybody to reference:

https://github.com/imFORZA/re-pro/issues/49

Hi,

Thanks for getting back to me quickly. We were not aware of the v2 version of the API, but will be sure to check it out, and write an updated class to support it. The code we have now was something we have been using in production for a bit already. The issue we came across is trying to support multiple third-party APIs in WordPress, and keep up with issues like this, new versions, and API changes. That’s why we started the WP-API-Libraries Project, with the goal to have the WordPress Community help manage, maintain standardized libraries for third-party APIs.

Hey John,

This bug only appears when you first visit the CloudFlare settings page after first activation. I actually had a code fix in my repo on github, you can see the fix here:

https://github.com/bhubbard/cloudflare/commit/6e8d5764951dadac7b76230b016653ecec6c6c35

Everyone please be sure to vote under the compatibility feature so other are aware: https://www.evernote.com/l/AAGn6row_M9HPJXZmiOmPw_KivulDacrrWw

Was this fixed?

Any update on this?

So I pushed up a few fixes and updates to the version of the plugin I have on github.
https://github.com/bhubbard/cloudflare

Hopefully someone at CloudFlare can take a look at it.

You have a couple options:

1) Disable CloudFlare for the subdomain. You do this by going into the DNS settings on the CloudFlare control panel, and clicking on the orange cloud so it turns gray.

2) Set a Page Rule – Again from the control panel you can set a page rule to disable caching and other CloudFlare features for the subdomain.

You can use this guide to write exceptions:
https://jetpack.me/2013/05/03/skip-a-image-with-photon/

@james Huff – In regards to your side note, I accept you removing it considering it as spam. But to be clear I wasn’t attempting to spam all the threads, I simply added it to the few threads that had no valuable input, e.g. generic I’m sad threads, and the one regarding the current large bug in 4.4.

Hi James,

I do have two accounts, one I use as my personal account (bhubbard), and one as a work account (imforza-bhubbard). The company I work for also has a user (imforza) which I and several others have access to as well.

I only submitted the message using my single user account bhubbard. Any and other +1 and comments were created by other users who did so with their own choosing.

With that said I did post the thread in my company Slack for others to read or comment on. And since I now have to clarify, I want to make it clear, no one in the company I work for was required to +1, or leave comments. The majority of our company does use CloudFlare and the plugin, so they do have the right to +1 or comment like any others. We are a small company, with 10 employees, as 3 doesn’t equal 10, its clear to say they all didn’t +1.