• Here is your error log:

    On Activation:
    15-Sep-2016 22:55:03 UTC] PHP Fatal error: Uncaught Error: Class ‘CloudFlare\IpRewrite’ not found in /home/website/public_html/wp-content/plugins/cloudflare/src/Hooks/Init.php:31
    #0 /home/website/public_html/wp-content/plugins/cloudflare/src/Hooks/Init.php(17): CF\Hooks\Init::cloudflareInit()
    #1 /home/website/public_html/wp-includes/plugin.php(524): CF\Hooks\Init::init(”)
    #2 /home/website/public_html/wp-settings.php(411): do_action(‘init’)
    #3 /home/website/public_html/wp-config.php(97): require_once(‘/home/website…’)
    #4 /home/website/public_html/wp-load.php(39): require_once(‘/home/website…’)
    #5 /home/website/public_html/wp-cron.php(26): require_once(‘/home/website…’)
    #6 {main}
    thrown in /home/website/public_html/wp-content/plugins/cloudflare/src/Hooks/Init.php on line 31

    • This topic was modified 9 years, 7 months ago by Kilmanagh.
Viewing 10 replies - 1 through 10 (of 10 total)
  • So it looks like the composer autoloader is failing but if that was true it wouldn’t even get this far, it would fail in cloudflare.php when looking up the init method.

    What is the output of get_include_path() on your server?

    Thread Starter Kilmanagh

    (@kilmanagh)

    You CloudFlare folks to realize your pulled in your entire source code into the repo?
    Most of that 4M+ of files are not needed for production. You do know it was 14K. It went from a light plugin to a super heavy plugin. That is bigger than most paid themes.

    Thread Starter Kilmanagh

    (@kilmanagh)

    It works on a fresh install on WAMP that is not connected to CloudFlare.
    After some investigating, It has to do something with your rewrites.
    HTTP: Fails all
    HTTPS Flex: Fails all
    HTTPS Full” Fails all
    HTTPS Strict: Front end Fails, Backend works but took 3 minutes to populate the Zone in setup.

    I don’t know if your competing with a popular plugin like a cache or SEO plugin but it definitely does not work with a typical WordPress installation that uses cloud flare.
    Looks like it could be nice when you get it working 🙂

    The reason I wanted to know your include path is because I think its causing the namespace based autoloader to fail. The error you got was composer’s autoloader not finding the IpRewrite class at the folder location it expected. If it was the namespace’s fault then it would have failed in cloudflare.php when the init method is called by namespace. My guess (right now) is your php include path is configured differently than our app expects.

    Thread Starter Kilmanagh

    (@kilmanagh)

    get_include_path() = .;/path/to/php/pear

    This is the standard Easy Apache 4 (MultiPHP) path on WHM/Cpanel.
    I never had any problems with it.

    Thread Starter Kilmanagh

    (@kilmanagh)

    Update***************

    I got it to work on one website which is much smaller. It works until you try and edit something.
    The error is in the wp-admin directory log:

    [16-Sep-2016 05:32:39 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/website/public_html/wp-includes/functions.php:3598) in /home/website/public_html/wp-content/plugins/cloudflare/src/Hooks/HTTP2ServerPush.php on line 52
    It will keep 520 errors on any page until you retry for a live version. Editing again just causes errors again.

    • This reply was modified 9 years, 7 months ago by Kilmanagh.

    Hi @kilmanagh,

    We removed HTTP2/ServerPush in 3.0.2 does this version fix your errors?

    Thanks,
    John

    Thread Starter Kilmanagh

    (@kilmanagh)

    It works on some sites.
    However, some sites it is blocked in Mod Security:

    GET /wp-admin/admin-ajax.php?action=cloudflare_proxy&proxyURL=https%3A%2F%2Fapi.cloudflare.com%2Fclient%2Fv4%2Fzones
    Access denied with redirection to http://website.com/ using status 302 (phase 2).
    Match of “beginsWith %{request_headers.host}” against “TX:1” required.

    Thread Starter Kilmanagh

    (@kilmanagh)

    I had to roll back all my sites to 1.3.24. Reason: Mod Security Pattern match “^5\\d{2}$” at RESPONSE_STATUS. I could no longer access Plugins.php. Also a lot of ajax issues. Rolling back made everything work again.

    Hey,

    We’re releasing a patch for the WAF bug on Wednesday or Thursday of this week.

    Thanks,
    John

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Error Log on 3.0’ is closed to new replies.