Jetpack v14.0 Causes Critical Error

  • Resolved scopemonkey

    (@scopemonkey)


    1 year, 6 months ago

    I recently upgraded to Jetpack v14.0 from v13.9.1 and now get a message stating that “a critical error has occurred on this website. I turned on WP debugging and the log shows:

    Stack trace:
    0 /hermes/bosnacweb06/bosnacweb06ae/b2866/ipg.whitepinelodgeus/wp/wp-includes/html-api/class-wp-html-decoder.php(148): WP_HTML_Decoder::read_character_reference(‘attribute’, ‘https://www.ont…’, 48, NULL)
    1 /hermes/bosnacweb06/bosnacweb06ae/b2866/ipg.whitepinelodgeus/wp/wp-includes/html-api/class-wp-html-decoder.php(114): WP_HTML_Decoder::decode(‘attribute’, ‘https://www.ont…’)
    2 /hermes/bosnacweb06/bosnacweb06ae/b2866/ipg.whitepinelodgeus/wp/wp-includes/html-api/class-wp-html-tag-processor.php(2735): WP_HTML_Decoder::decode_attribute(‘https://www.ont…’)
    3 /hermes/bosnacweb06/bosnacweb06ae/b2866/ipg.whitepinelodgeus/wp/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-image-cdn/src/class-image-cdn.php(361): WP_HTML_Tag_Processor->get_attribute(‘src’)
    4 /hermes/bosnacweb06/bosnacweb06ae/b2866/ipg.whitepin in /hermes/bosnacweb06/bosnacweb06ae/b2866/ipg.whitepinelodgeus/wp/wp-includes/html-api/class-wp-html-decoder.php on line 385

    When I rollback to v13.9.1 the error goes away. I’m on current version of WP (6.7.1) using PHP 7.4.10.

    Is this a known bug in v14.0? Is there some setting I missed somewhere that need to change? Any advice on how to resolve this would be appreciated. In mean time, sticking with 13.9.1.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Rashed Hossain

    (@wprashed)

    1 year, 6 months ago

    Hello,

    The error you’re experiencing after upgrading Jetpack to version 14.0 appears to stem from how the plugin interacts with the WordPress HTML API in combination with your site’s PHP environment. Let’s break this down and explore possible solutions:

    Known Bug in Jetpack v14.0
    The error trace indicates an issue in Jetpack’s class-image-cdn.php, related to decoding and handling HTML attributes using the WordPress HTML API (class-wp-html-decoder.php). This might be a compatibility issue introduced in Jetpack 14.0. While this specific bug has not been widely reported yet, it’s possible the update introduced a problem with certain PHP versions or edge-case scenarios.

    PHP Version Compatibility
    Jetpack 14.0 likely uses newer functions that may not fully support PHP 7.4. While PHP 7.4 is technically supported, WordPress and many plugins are now optimized for PHP 8.x. Upgrading to PHP 8.0 or 8.1 could resolve this issue.

    Rollback to Jetpack 13.9.1
    You’ve already done this, which is a good temporary solution. Stick to 13.9.1 while troubleshooting.

    Update PHP
    1. Log into your hosting control panel or contact your hosting provider.
    2. Update your PHP version to 8.0 or 8.1.
    3. Test Jetpack 14.0 again after updating PHP.

    Debug Further
    1. Enable WordPress debugging:
    – Add the following to your wp-config.php file if it’s not already present:

    `define(‘WP_DEBUG’, true);
    define(‘WP_DEBUG_LOG’, true);
    define(‘WP_DEBUG_DISPLAY’, false);`

    – Check the debug.log file in wp-content for detailed error reports.

    2. Look for other plugins or themes that might conflict with Jetpack 14.0. Temporarily disable other plugins and switch to a default theme (like Twenty Twenty-Three) to see if the error persists.

    4. Stick to Jetpack 13.9.1 for Now until the issue is resolved, it’s perfectly fine to stick with the version that works. Monitor Jetpack’s release notes for any patches or updates addressing this bug.

    Let me know if you’d like more detailed instructions for any of these steps.

    Plugin Support Animesh Gaurav

    (@bizanimesh)

    1 year, 6 months ago

    Hey @scopemonkey – you can check the above reply from @wprashed (thank you @wprashed for adding the inputs).

    Apart from this, could you please completely uninstall the Jetpack plugin and install the fresh updated version from Plugins » Add New Plugin section? Let us know how it went after reinstallation of Jetpack plugin.

    If it doesn’t help, you can try to reinstall WordPress by going to Dashboard » Updates in WP Admin and then check again if that helps with the error. 🙂

    Thread Starter scopemonkey

    (@scopemonkey)

    1 year, 6 months ago

    Thanks to the input from @wprashed and @bizanimesh, I have been able to get this issue resolved. I had already rolled back to 13.9.1 and turned debugging on. I deleted and reinstalled Jetpack, but that too did not work so rolled back to 13.9.1 again and contacted tech support at my hosting company. They apparently have been doing some PHP upgrades (unannounced to the users…) and needed to adjust the PHP memory limit. Once that was done, I was able to successfully upgrade to 14.0 without problems and all is working again. I remain on PHP 7.4 at the recommendation of tech support until they have finished whatever they are doing with PHP installations.

    Plugin Support Animesh Gaurav

    (@bizanimesh)

    1 year, 6 months ago

    Hay @scopemonkey – Thank you for the update! I’m glad to hear the issue has been resolved and appreciate you sharing the steps you took — it could be helpful for others facing similar challenges.

    If you encounter any other issues or have further questions about Jetpack, feel free to reach out. We’re here to help!

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

The topic ‘Jetpack v14.0 Causes Critical Error’ is closed to new replies.