Fatal error

  • Resolved elledawn

    (@elledawn)


    6 months, 1 week ago

    When seeking help with this issue, you may be asked for some of the following information: WordPress version 6.8.2 Active theme: Neve (version 4.1.3) Current plugin: Jetpack (version 15.0.2) PHP version 8.2.29 Error Details ============= An error of type E_ERROR was caused in line 298 of the file /nas/content/live/___/wp-content/plugins/jetpack/modules/photon-cdn.php. Error message: Uncaught TypeError: array_keys(): Argument #1 ($array) must be of type array, null given in /nas/content/live/___/wp-content/plugins/jetpack/modules/photon-cdn.php:298 Stack trace: #0 /nas/content/live/___/wp-content/plugins/jetpack/modules/photon-cdn.php(298): array_keys(NULL) #1 /nas/content/live/___/wp-content/plugins/jetpack/modules/photon-cdn.php(195): Jetpack_Photon_Static_Assets_CDN::get_plugin_assets(‘woocommerce’, ‘10.2.2’) #2 /nas/content/live/___/wp-content/plugins/jetpack/modules/photon-cdn.php(114): Jetpack_Photon_Static_Assets_CDN::cdnize_plugin_assets(‘woocommerce’, ‘10.2.2’) #3 /nas/content/live/___/wp-includes/class-wp-hook.php(324): Jetpack_Photon_Static_Assets_CDN::cdnize_assets(”) #4 /nas/content/live/elyshanyc/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #5 /nas/content/live/___wp-includes/plugin.php(517): WP_Hook->do_action(Array) #6 /nas/content/live/___/wp-includes/script-loader.php(2251): do_action(‘wp_print_script…’) #7 /nas/content/live/___/wp-includes/class-wp-hook.php(324): wp_print_head_scripts(”) #8 /nas/content/live/___/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #9 /nas/content/live/___/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #10 /nas/content/live/___/wp-login.php(127): do_action(‘login_head’) #11 /nas/content/live/___wp-login.php(1490): login_header(‘Log In’, ”, Object(WP_Error)) #12 {main} thrown

    When will this be fixed?

    • This topic was modified 6 months, 1 week ago by elledawn.
    • This topic was modified 6 months, 1 week ago by elledawn.
    • This topic was modified 6 months, 1 week ago by elledawn.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Ken Gagne

    (@kgagne)

    6 months, 1 week ago

    The Asset CDN module of Jetpack is conflicting with something.

    If you can SSH into the site and run this command:

    wp jetpack module deactivate photon-cdn

    That should bring the site back up.

    Plugin Support Alin (a11n)

    (@alinclamba)

    6 months, 1 week ago

    Hi @elledawn,

    Thanks so much for sharing the details. I know how frustrating it can be to run into a fatal error like this, especially when it takes your site offline.

    As mentioned above (thanks @kgagne), our developers have identified this as a known issue in Jetpack’s Asset CDN (Site Accelerator) included in version 15.0.2. It can cause this error on sites running PHP 8.2 or newer.

    The good news is that a fix has already been prepared and will be included in the next Jetpack release.

    In the meantime, you can safely disable the Asset CDN to bring your site back online — either with the command shared above, or by going to Jetpack → Settings → Performance and turning off “Enable site accelerator” if you still have access to your site.

    Once Jetpack next release becomes available, updating will permanently resolve the issue.

    Thanks again for your patience while we roll out the fix!

    Plugin Support Alin (a11n)

    (@alinclamba)

    6 months ago

    Hi @elledawn,

    Good news — the fix for this issue is now available!

    You can update Jetpack to version 15.1.1, which fully resolves the error you experienced with the Asset CDN (photon-cdn.php).

    After updating, you can safely re-enable the Site Accelerator feature if you had previously turned it off.

    Thanks again for your patience while this was being addressed — and please let us know if anything still looks off after updating.

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

The topic ‘Fatal error’ is closed to new replies.