1. Bruce Wampler on August 10, 2010 at 6:25 am

    Should be a great tool, but…

    Notice: Undefined index: debog in /wp-content/plugins/debogger/debog.php on line 64

    Warning: DOMDocument::loadHTML() [domdocument.loadhtml]: Empty string supplied as input in /wp-content/plugins/debogger/debog.php on line 242

  2. Pross on August 10, 2010 at 2:48 pm

    Thanks Bruce, it was very late last to fix it 😉

  3. Pross on August 10, 2010 at 3:28 pm

    0.5 should fix this 😉

    • Bruce Wampler on August 10, 2010 at 4:37 pm

      VERY cool tool, by the way!

      • Pross on August 10, 2010 at 4:44 pm

        Bruce have you tested the update?

        • Bruce Wampler on August 10, 2010 at 5:58 pm

          Just tried it – don’t have a broken theme, but am working with a plugin with lots of issues. Don’t know exactly what all debogger is supposed to catch (do plugins get hooked before themes?), but I got this output at the top:
          Notice: Constant FORUM already defined in /Users/bw/Sites/ on line 36

          Notice: get_bloginfo was called with an argument that is deprecated since version 2.2! The siteurl option is deprecated for the family of bloginfo() functions. Use the url option instead. in /Users/bw/Sites/ on line 3321

          Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /Users/bw/Sites/ on line 3237

          Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /Users/bw/Sites/ on line 3237

          Then some more in the debogger box:
          => update_usermeta is deprecated since version 3.0! Use update_user_meta() instead.

          and finally the totally filled in review.

          So I don’t know if that proves anything – would be neat to have it work for plugins as well as themes. It looks like one of my plugins is generating debug stuff before debogger grabs it. If I remember things, you can give priorities to hooks? Can you make debogger run before other plugins?

          And when activated, does it switch on WP_DEBUG? It would be neat to be able to turn it on and off. And once debogger grabs the error output, does it stop it from intermixing with the regular screen?

          Sorry for so many questions. Can carry on by private e-mail if you have any more questions or things I could test for you.

  4. Pross on August 10, 2010 at 7:15 pm

    Shame but I could find no way to enable/disable wp_debug the 3 options available are:
    1: Intercept the PHP error function and store them in a variable allowing the page to render as the author intended (default).
    2: Do nothing, PHP handles the errors.
    3: Suppress all errors.
    The plugin gets called during ‘init’ and captures all theme errors and most plugin errors too. I’m not sure if it can be loaded any earlier?

  5. Debogger 0.6 | The Blog of Pross! on August 25, 2010 at 1:23 pm

    […] Debogger […]

  6. tenman on September 30, 2010 at 12:41 am

    hello Debogger

    thanks very cool plugin.

    We will inform you that one small problem to make it to more wonderful was found.

    debog.php line 25

    echo '';

    ' Seconds.';

    div elements can not use inner address elements

    I’m change this

    echo '';

    • tenman on September 30, 2010 at 12:45 am


      echo '<div style="text-align:center;">';


      echo '<span style="text-align:center;display:block;">';

  7. geneghis on September 4, 2011 at 11:00 am

    Hi Pross

    First, I speak a really bad english.
    I have a problem with the activity and I just put the plugin “Debogger”. I don’t understand because I look at for everywhere and I don’t find how I cann’t activate this plugin.
    How must I do?


Leave a Comment

Used 40 SQLs and finished the page in 0.14 seconds