Support » Plugin: Wordbooker » WP_DEBUG notices

  • With WP_DEBUG defined (Wordbooker 2.1.25 / WP 3.5.1), Wordbooker spits out loads and loads of notices. While I realize that they’re “harmless,” it would be nice to get them cleaned up as this is the only of my ~20 plugins that generate error_logs whenever I’m working on debugging other parts of code 🙂

    Examples:

    [07-Feb-2013 20:54:34] PHP Notice: Use of undefined constant id – assumed ‘id’ in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 105
    [07-Feb-2013 20:54:34] PHP Notice: Use of undefined constant id – assumed ‘id’ in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 105
    [07-Feb-2013 20:54:34] PHP Notice: Use of undefined constant id – assumed ‘id’ in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 105
    [07-Feb-2013 20:54:34] PHP Notice: Use of undefined constant id – assumed ‘id’ in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 138
    [07-Feb-2013 20:54:34] PHP Notice: Use of undefined constant id – assumed ‘id’ in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 138
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: wordbooker_thumb_only in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 174
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 174
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: wordbooker_use_excerpt in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 177
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 177
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: wordbooker_override_author in /home/(path)/wordpress/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 182
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 182
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: wordbooker_comment_put in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 225
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 225
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: wordbooker_comment_get in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 226
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 226
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: wordbooker_use_facebook_comments in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 227
    [07-Feb-2013 20:54:34] PHP Notice: Undefined index: in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_posting_options.php on line 227

    …In addition, visiting the Wordbooker page of the admin panel spits out more than I could list here – though I’m sure you’ll see them right away if you define WP_DEBUG 😉

    http://wordpress.org/extend/plugins/wordbooker/

Viewing 5 replies - 1 through 5 (of 5 total)
  • More:

    [07-Feb-2013 21:05:12] PHP Notice: Undefined property: stdClass::$id in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_cron.php on line 275
    [07-Feb-2013 21:05:13] PHP Notice: Undefined property: stdClass::$error in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_cron.php on line 43
    [07-Feb-2013 21:05:13] PHP Notice: Trying to get property of non-object in /home/(path)/wp-content/plugins/wordbooker/includes/wordbooker_cron.php on line 43

    Plugin Author Steve

    (@steveatty)

    Its because when you unset options they vanish out of the form so the option handling code loses them… so I’ve got to put a large pile of isset checks in.

    Yeah, I know the cause 😉 It just makes it quite difficult to debug other stuff, because I either have to disable Wordbooker completely (making my dev site not match the live one), or sift through 99% Wordbooker notices to find the issue I’m attempting to debug 😉

    (Also, I can’t leave WP_DEBUG enabled temporarily on a live site, i.e. to see if an error_log appears – because unless I disable Wordbooker it *always* appears after a bit).

    Plugin Author Steve

    (@steveatty)

    I’m making all the changes in 2.2 – I am not doing it in both code bases because if I do I’ll never get the code finised.

    Gotcha

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘WP_DEBUG notices’ is closed to new replies.