JetPack Incompatibility

UpdraftPlus Home › Forums › Paid support forum – UpdraftPlus backup plugin › JetPack Incompatibility

Tagged: , ,

Viewing 15 posts - 1 through 15 (of 17 total)
1 2
  • Author
    Posts
  • May 15, 2019 at 7:57 pm #388387
    phillcoxon
    Participant

    I’m running UpdraftPlus Pro 2.6.14.24 on a site, and I’m getting the following error output into my logs:

    Notice: can_display_jetpack_manage_notice used for an anonymous function is deprecated since version with no alternative available. in /app/public/wp-includes/functions.php on line

    After searching through the entire codebase for the site, the only reference I found, outside of JetPack, to the can_display_jetpack_manage_notice function was inside of updraftplus/udaddons/updraft-addons.php on line 65. It appears that that line is what’s causing the issue. Can you please look into this? Thank you.

    May 15, 2019 at 8:03 pm #388388
    udadmin
    Keymaster

    Hi Phill,

    updraftplus/udaddons/updraft-addons.php on line 65

    That line uses a named function, not an anonymous one, so can’t be what you’re looking for. Anonymous functions start like this: function () {. See: https://www.php.net/manual/en/functions.anonymous.php

    David

    May 16, 2019 at 1:37 pm #388622
    phillcoxon
    Participant

    JetPack uses the is_callable() (https://www.php.net/manual/en/function.is-callable.php) PHP function to determine whether a function is anonymous or not while outputting notices about deprecated functions (https://plugins.trac.wordpress.org/browser/jetpack/trunk/class.jetpack.php#L6394). The __return_false() function (https://developer.wordpress.org/reference/functions/__return_false/) must be evaluating as is_callable() by PHP.

    I can tell you with 99% certainty that line 65 in updraft-addons.php is the line that’s causing the PHP notice.

    May 21, 2019 at 12:32 am #390341
    Karel
    Participant

    Same issue here.

    Any (simple) solution?

    Thanks.

    Karel

    May 21, 2019 at 9:34 am #390512
    Bryle Crodua
    Moderator
    This reply has been marked as moderator-only.
    May 25, 2019 at 5:16 pm #392293
    David
    Participant

    Inclined to agree.. when I disable UpdraftPlus (which is not what I want to do) the error as described goes away.

    May 26, 2019 at 2:24 pm #392495
    davidechols
    Participant

    Hello, I have the same problem. Is there any help for this?

    May 26, 2019 at 2:36 pm #392498
    David
    Participant

    I did ultimately comment out line 65 in updraft-addons.php and enabled the plugin.

    May 26, 2019 at 2:49 pm #392499
    davidechols
    Participant

    Thank you David! I’ve done that now and the notice is gone, what effect might this have on Updraft? Thank you again.

    May 29, 2019 at 7:42 am #393417
    Anonymous
    Inactive

    Thanks Phill for raising this issue.

    I see exactly the same error message:

    Notice: can_display_jetpack_manage_notice used for an anonymous function is deprecated since version with no alternative available. in /home/mybraini/public_html/wp-includes/functions.php on line 4438

    The error message appears on every page of the live version of my website, which is unacceptable.

    The error message disappears when I disable UpDraftPlus. I have disabled UpDraftPlus as I am not prepared to comment out PHP in case it has an adverse effect but also because it is the responsibility of UpDraftPlus to investigate this properly and fix it if it indeed a bug.

    I pay for the Premium version of this plugin so have now raised a support ticket asking for this issue to be investigated properly and fixed asap.

    Will update this thread when I hear back.

    Thomas

    May 29, 2019 at 8:07 am #393428
    udadmin
    Keymaster

    Hi,

    This is a bug in Jetpack which they have slated to fix in the upcoming JetPack 7.3.1: https://github.com/Automattic/jetpack/issues/12303

    Sorry for a lack of reply here. One of our support staff flagged it for a developer to look at, but in an incorrect way that did not work.

    Best wishes,
    David

    May 29, 2019 at 8:08 am #393430
    udadmin
    Keymaster

    Also, you will want to look into why your PHP install is configured to send PHP internal information to the web browser, and turn that off (e.g. WP_DEBUG turned on, or PHP error reporting configured to print instead of log), as that is rarely desirable on a live website.

    May 29, 2019 at 8:11 am #393431
    udadmin
    Keymaster

    Hi,

    Looking again at https://github.com/Automattic/jetpack/issues/12303, it says that they *did* update it in JetPack 7.3.1, which they released two weeks ago; please check that you have updated. (If not, you should re-open that issue).

    David

    May 29, 2019 at 8:56 am #393448
    Anonymous
    Inactive

    Hi David,

    Many thanks for your quick and helpful response, much appreciated. I have JetPack 7.3.1 installed, but still see the issue so have re-opened the issue on Github.

    https://github.com/Automattic/jetpack/issues/12303

    Not sure why the error was going to the web browser. Will contact my host to explore further.

    Thomas

    May 29, 2019 at 9:00 am #393459
    udadmin
    Keymaster

    Hi,

    I’ve reviewed this again more carefully. In fact that issue on the Jetpack tracker is subtly different. In fact, the relevant line of UD just needs removing. I have now done so from our development version, so it’ll be in the next release (due out in a few days). It’s also removed from all new downloads of the current release. You can comment it out without harm. You will still want to not have PHP debugging output go to the browser, as otherwise you may see all kinds of things from many plugins in future.

    David

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 17 total)
1 2
  • The topic ‘JetPack Incompatibility’ is closed to new replies.