• Resolved tramaway

    (@tramaway)


    Latest update crashed my website. This is what I get:

    Warning: Invalid Jetpack option name: edit_links_calypso_redirect in /home/site.com/www/wp-content/plugins/jetpack-protect/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-options.php on line 231

    Warning: Invalid Jetpack option name: onboarding in /home/site.com/www/wp-content/plugins/jetpack-protect/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-options.php on line 231

    Warning: Cannot modify header information – headers already sent by (output started at /home/site.com/www/wp-content/plugins/jetpack-protect/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-options.php:231) in /home/site.com/www/wp-admin/includes/misc.php on line 1438

    Warning: Cannot modify header information – headers already sent by (output started at /home/site.com/www/wp-content/plugins/jetpack-protect/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-options.php:231) in /home/site.com/www/wp-includes/functions.php on line 7108

    Warning: Cannot modify header information – headers already sent by (output started at /home/site.com/www/wp-content/plugins/jetpack-protect/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-options.php:231) in /home/site.com/www/wp-includes/pluggable.php on line 1435

    Warning: Cannot modify header information – headers already sent by (output started at /home/site.com/www/wp-content/plugins/jetpack-protect/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-options.php:231) in /home/site.com/www/wp-includes/pluggable.php on line 1438

    • This topic was modified 2 months, 2 weeks ago by tramaway.
Viewing 13 replies - 1 through 13 (of 13 total)
  • I also am getting these errors – possibly they started after upgrading to the very latest jetpack + jp protect versions. Also:

    PHP Deprecated: Function is_onboarding is deprecated since version 4.0.0 with no alternative available

    +1 on this, same problem. For now, inactivating the Jetpack Protect plugin restored site functionality, but looking forward to a bug fix.

    Plugin Author Osk

    (@oskosk)

    Hi. We’re looking into this.

    possibly they started after upgrading to the very latest jetpack + jp protect versions.?

    This is the case, indeed

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Sorry all about the trouble! It would seem to be a conflict between different versions of the Jetpack plugin and the Jetpack Protect plugin.

    Do you all happen to use both the Jetpack plugin and the Jetpack Protect plugin on your sites? Does the problem disappear when you update both plugins to their latest version?

    Plugin Author Osk

    (@oskosk)

    We recommend keeping WP_DEBUG_DISPLAY set to false in your wp-config.php file for sites in production.

    This will prevent warnings from appearing on the frontend, while still logging them with WP_DEBUG_LOG for later review.

    We’re also going to work on a patch to address these deprecations in a more elegant way

    @jeherve I have both plugins installed, both updated to the latest versions (Jetpack 13.8, Jetpack Protect 3.0.1). As I wrote above, the problem exists and inactivating Jetpack Protect restores site functionality.

    Thread Starter tramaway

    (@tramaway)

    Also Jetpack 13.8 and Jetpack Protect 3.0.1. Had to deactivate Jetpack Protect

    Plugin Author Osk

    (@oskosk)

    We’ve just released a new version of Jetpack Protect. Please update to resolve the issue. Thank you for your patience, and we apologize for the inconvenience.

    I’m marking this as solved.

    My site (https://www.teigfam.net/oyvind/home/) seems to not say it needs updating, but that warning still came. There was none of the below in my wp-config.php, but when I added this the warning disappeared at least:

    /**
    * https://www.ads-software.com/support/topic/jetpack-protect-crushed-my-website/
    * 2024 09 06
    */
    define('WP_DEBUG_DISPLAY', false);
    • This reply was modified 2 months, 2 weeks ago by aclassifier. Reason: Better home page link
    Plugin Author Osk

    (@oskosk)

    @aclassifier, it looks like your site is already running Jetpack Protect 3.0.2, the version published a few hours ago. So the issue should be gone there

    @oskosk, I tried removing WP_DEBUG_DISPLAY false now, and the error appeared again. I even got a page that only displayed that warning, nothing else.

    Update: I see that it behaves differently on different pages. I now get the message on top of the page also with that value to false on https://www.teigfam.net/oyvind/home/models/201-my-krokis-notes/. I do the edit by downloading wp-config.php and after edit uploading it again. Where do I edit it in the WordPress panel? Does this make any difference?

    • This reply was modified 2 months, 2 weeks ago by aclassifier. Reason: typo
    • This reply was modified 2 months, 2 weeks ago by aclassifier.

    Update. Like https://www.teigfam.net/oyvind/home/publications-lectures/ only gives the warning message. I have that value set to false

    Plugin Support Paulina H. (a11n)

    (@pehaa)

    Hey all,

    Just an update to let you know that the last update to the Jetpack plugin (13.8.1) should fix the warnings issue.

    Thank you!

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.