Hi @clocksaysnow,
Where do you host your WordPress blog?
Thanks,
John
Thread Starter
D
(@clocksaysnow)
It’s hosted on Hostgator.
Known softwares which can cause this issue are InfiniteWP, Wordfence. This issue is caused by a different software. Please check the software provided by Hostgator.
Thanks
Thread Starter
D
(@clocksaysnow)
But as I mentioned, I deactivated ALL my other plugins and still got the same error message. So wouldn’t the problem be with the Cloudflare plugin itself rather than with any of my deactivated plugins?
Something else lower down the stack may be affecting it.
You need to open a support ticket with HostGator and ask if there is anything on your account which is reading php://input.
Thanks,
John
Thread Starter
D
(@clocksaysnow)
With all due respect, you earlier said that it was probably an incompatibility problem with another plugin—despite the fact that I stated that I had deactivated all my other plugins. So before I submit a support ticket and embark on what might be a wild goose chase, let me ask you this: if everything EXCEPT the Cloudflare plugin is working perfectly on my website, why wouldn’t you conclude that the problem is with the Cloudflare plugin rather than with something else on my website?
@clocksaysnow,
We read the post body here. According to the php://input documentation the php://input buffer wasn’t made reusable until PHP 5.6.
When the plugin returns the error you’re getting it means something is reading php://input BEFORE our plugin has a chance to read it. Usually this is another WordPress plugin, but not always. Since these requests are being sent from our plugin to our plugin nothing else should be reading them.
Your options are to either upgrade to PHP 5.6+ or debug further with your host. Unfortunately there is nothing more we can do.
Thanks,
John
-
This reply was modified 9 years, 2 months ago by
jwineman.