Support » Plugin: Notely » ERROR at /public_html/wp-content/plugins/notely/notely.php on line 71

  • Resolved Joao Paulo

    (@jpbenfica)



    Getting an error: /public_html/wp-content/plugins/notely/notely.php on line 71
    in ADMIN area.

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

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Michael Ott

    (@mikeyott)

    I can’t replicate this issue, on either Windows or Linux servers, PHP 5.6 or 7. I’d say something else is causing the issue.

    The ERROR occurs because in the WordPress wp-config.php file there is a conflict between the lines.

    The cause
    define ('WP_DEBUG', false);
    Plugin Author Michael Ott

    (@mikeyott)

    Nope. Adding that doesn’t change a thing for me. Still no errors output on screen, no errors in the error log.

    Try switching to a different theme monetarily and see if the problem still exists. If the error goes away, then it’s a theme conflict.

    If the problem still exists, try disabling all plugins momentarily and see if the error still occurs. If the problem goes away, it’s a plugin conflict.

    same here:
    [19-Mar-2018 09:48:13 UTC] PHP Notice: Undefined index: mo_notely_nounce in /var/www/clients/client2/web35/web/wp-content/plugins/notely/notely.php on line 79

    please investigate why your plugin could not work with other plugins.

    Details:
    php 7.1.3, nginx hosting

    debugging totaly block things(ajax) from working.
    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_LOG’, true );
    define( ‘SCRIPT_DEBUG’, true );
    define( ‘WP_DEBUG_DISPLAY’, true );

    PS: thrivethemes plugins activated causing the php notice in debug.log.
    PPS: Please investigate why your plugin could not work with other plugins.
    So we do not need to list up all not notely compatible plugins here.
    PPPS: until then i have to deactivate notely plugin.

    • This reply was modified 6 months, 1 week ago by  Tobias_Conrad.
    • This reply was modified 6 months, 1 week ago by  Tobias_Conrad.
    • This reply was modified 6 months, 1 week ago by  Tobias_Conrad.
    Plugin Author Michael Ott

    (@mikeyott)

    Hi Tobias,

    Are you running the latest version? If so, I’m not sure what I can do. I can’t replicate the issue (no errors, not even in the error log). I’m running it on a handful of sites and Ajax functions continue to work totally fine.

    But you did the right thing deactivating the plugin. I certainly can’t justify paying money for Thrive Themes in order to troubleshoot my little plugin that I give away for free and that I get absolutely nothing in return from.

    So my best suggestion is to try an alternative notes plugin, I’d be surprised if there weren’t a few out there already.

    Good luck.

    Hi everyone,

    I am also having
    [06-Jul-2018 00:59:59 UTC] PHP Notice: Undefined index: mo_notely_nounce in .../wp-content/plugins/notely/notely.php on line 79
    in my log files when someone proceeds passed my checkout page.

    From my research, this is caused by some changes in how PHP 7.1+ or somewhere around there decides to throw notices. I have recently upgraded to PHP 7.2 and am having quite a few plugins causing these notices in my log file somewhat seemingly random.

    First off, no one should be using define( ‘WP_DEBUG_DISPLAY’, true ); on a live site. This should only be used in the development stage. It can cause layout/flow issues and more importantly, serious security issues letting end users see your errors. The following can be used in the wp-config.php on a live site temporarily to log errors and warnings but the log file can grow quite large if left unattended:

    define( ‘WP_DEBUG’, true ); // turns on debuggin
    define( ‘WP_DEBUG_LOG’, true ); // will log any errors in debug.log in your wp-content folder.
    define( ‘WP_DEBUG_DISPLAY’, false ); // will not show errors on your site.

    Second, correct me if I am wrong, but PHP Notices are not that serious, just a note to pay attention, this could cause a problem down the road or maybe you are doing something unnecessary. Undefined index’s seem to be caused by null values trying to be passed. Another words, if there is no data for the notely meta being saved for that particular page being ran, then it throws a undefined index notice. Apparently this used to be no big deal before PHP 7 was introduced, but someone decided that a notice should be generated letting the developer know that they are trying to save empty data or something like that?

    Unfortunately, my scripting skills are very lacking, and google doesn’t seem to provide a lot of answers or examples how to correct this notice since PHP 7.1 + is fairly new. At least not in a way I can understand. That is why I am here, I am hoping that Michael Ott can find the answer and fix it. Then I can learn how to fix other plugins that are generating the same notices.

    Michael,

    I just want to give a big thanks for your time in developing, maintaining, and sharing this awesome little plugin. Simple, lightweight, and very useful on the back end of our product pages.

    Perhaps use PHP 7.2, go through a checkout page and cancel the order. Check logs, this notice should be there. Seems to be triggered when woocommerce tries to update the addresses from the checkout page.

    Notely 1.4
    Woo 1.3.6
    WP 4.9.6

    Plugin Author Michael Ott

    (@mikeyott)

    @joeistoybox

    Props for the amazeballs feedback. I’ll see if I can get a PHP 7.2 instance running in a VM to troubleshoot this.

    Unfortunately, in about 5 hours I’ll officially be on leave (for a week) and so finding some time will be a challenge. I’ll do my best.

    Oh, and thanks for the kind feedback!

    Michael,
    Anyone that works hard on something, then shares if for free, has my ultimate respect.
    I’m in no hurry. Hope you enjoy your leave.

    Anyone having issues with Notely (or any other plugin or snippet) and the newer versions of PHP throwing notices should just turn off debugging or at the very least quit displaying the errors. It should work fine (it’s only a notice not a fatal error).

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