Undefined array keys with Cloudflare extension

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    1 month, 3 weeks ago

    Hello @nothin7

    Thank you for reaching out, and I am happy to help!
    Can you please replace the section in /Extension_CloudFlare_Plugin.php

    // Extract out the main IP pieces.
    $ip_pieces = explode( '::', $left_piece, 2 );
    $main_ip_piece = $ip_pieces[0];
    $last_ip_piece = $ip_pieces[1];

    to

    // Extract out the main IP pieces.
    $ip_pieces = explode('::', $left_piece, 2);
    $main_ip_piece = $ip_pieces[0];
    $last_ip_piece = isset($ip_pieces[1]) ? $ip_pieces[1] : '';

    Let me know if this helps and if the issue persists

    Thanks!

    Thread Starter Zade

    (@nothin7)

    1 month, 3 weeks ago

    Yes, this fixes the line 484 warning. Thanks! Will this change be incorporated into the next update of your plugin?

    The 13 warnings that appear only when viewing the Performance Dashboard can be resolved by reauthorizing Cloudflare. This will be annoying to do for 100+ sites but at least it’s possible. Any chance of somehow automating this or updating the code so reauthorizing isn’t needed?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    1 month, 2 weeks ago

    Hello @nothin7

    Thank you for your feedback.
    We’ll make sure to include this to the next release.
    As for the other warnings, we’ll have to check that more as we are not able to replicate this at the moment

    Thank you for your patience with this


    Thread Starter Zade

    (@nothin7)

    1 month, 2 weeks ago

    Much appreciated.

    Triggering those other warnings would probably involve reverting to the oldest version of W3TC that integrated Cloudflare, then authorizing. In other words, it’s something that’s fixed for new installations and is a remnant that only affects early adopters. I can understand if that’s not worth fixing.

    No need to reply, but feel free to let me know when the next update has been released, and I’ll mark this ticket as resolved.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    1 month, 2 weeks ago

    Hello @nothin7

    Thank you for your feedback.
    I’ll let you know when the next update will be reased with this fix

    Thanks!

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

You must be logged in to reply to this topic.