Error Reporting Plugin

This post is for comments, suggestions etc. If you need support for the plugin
– not for fixing all the errors it finds :)
– please visit the Mittineague Forums (registration required to post)

I'm particularly looking for common option configurations to add to the Option Settings Logic section (see the Error Reporting Plugin page) as a "top 4 settings" row of examples. Also, if you find any bugs :shudder: please let me know.

Suggestions for improvement are welcome here too, although I can't guarantee they'll get implemented, feel free to make them.

Thanks, Mittineague


  1. Posted March 29, 2007 at 1:00 am | Permalink

    Further testing with various option settings revealed a bug in the conditional generating code block, another error type, and sporadic server folder permission resets.

    Hence, version Beta 0.9.1 29-Mar-2007

    * fixed buggy conditional generating code block
    * added info re E_RECOVERABLE_ERROR
    * added chmod to fix annoying sporadic permission resets

  2. Posted March 30, 2007 at 7:36 pm | Permalink

    version Beta 0.9.2 30-Mar-2007

    Security improvements
    * make wp-log folders / files not world readable
    * added nonces to form actions

    * minor GUI changes
    * added error_log to Log block fopen-fwrite fails

  3. Posted April 9, 2007 at 11:39 pm | Permalink

    Testing the error_log function revealed that it needs the same permissions as file writing does. So using it as a fail-safe iis useless.

    version Beta 0.9.3 09-Apr-2007

    * removed error_log from Log block fopen-fwrite fails
    * added natsort to log file display
    * rearranged page sections
    * minor mark-up and info edits

  4. Posted April 11, 2007 at 1:52 am | Permalink

    version Beta 0.9.4 10-Apr-2007

    * made date_default_timezone_get/set OK for PHP < ver. 5

  5. Posted January 29, 2009 at 2:46 am | Permalink

    version Beta 0.9.5 27-Jan-2009

    * changed mktime() to time()
    * "info" link fix
    * replaced "short tags"
    * changed "wp"logs to "er"logs
    * added javascript select/deselect all

  6. Posted March 15, 2009 at 9:44 pm | Permalink

    This version release has a few improvements.

    Although some errors are "acceptable", it seemed a bit wrong for a plugin developed for finding errors to have some itself. Especially since only a few more bytes were needed to fix things.

    Having the plugin settings at "all error types" "all folders" can be somewhat scary and a definite eye-opener. But for those wondering how many errors are in the native WordPress Core files and their blog's plugins, the Error Reporting plugin will oblige.

    One such Core error is the way output buffer flush is called from the 'shutdown' action. This was causing a problem accessing log files if the settings were for "E_NOTICE" "wp-includes". You no longer need to turn off error reporting to access the files, but it is more important that you restore permissions and re-enable 'shutdown' when you're done now.

    The Error Reporting plugin is highly customizable and as such has many form inputs. Label tags help make the experience more user friendly.

    Speaking of friendly, the CSS selectors are now more plugin specific to avoid potential naming conflicts.

    Last but not least, to get things in line with WordPress 2.7, the plugin's options are now registered during activation.

    version Beta 0.9.6 15-Mar-2009

    * fixed uninitialized variables
    * fixed 'all types' 'all folders' bug
    * remove/add 'shutdown' action
    * added label tags
    * friendlier CSS selectors
    * added 'register_activation_hook'

  7. ParDarItepe
    Posted March 20, 2009 at 5:54 pm | Permalink

    Was ist das?

  8. Posted March 27, 2009 at 1:47 pm | Permalink

    Sorry for the delay in answering, for some reason your comment got flagged as SPAM and I didn't see it right away.

    The Error Reporting plugin assigns the plugin as the PHP error handler. Depending on how the plugin is configured, various error messages can be logged to files and/or sent via email.

  9. Posted April 1, 2009 at 6:39 pm | Permalink

    This release version has a Ping Error dashboard widget feature. Great for tracking repeated ping failures so you can clean up your ping list. (As found in the stand-alone Ping Watcher plugin).

    It also now removes it's options from the wp_options table and deletes the folders and files it creates when it's deleted using the WordPress plugin page's "delete".

    And the CSS styles are now only included in it's own pages, not other admin pages unnecessarily.

    The nonce tweaks help make the plugin even more secure for WordPress 2.5+ users, but is backwards compatible with older versions for those yet to upgrade.

    version Beta 0.10.0 01-Apr-2009

    * added ping error – dashboard widget code
    * added self-cleanup hooks
    * removed deprecated option descriptions
    * nonce tweaks
    * removed print_r $context
    * added return false
    * changed admin CSS hook
    * removed fail returns from handler

  10. Posted November 21, 2009 at 3:12 pm | Permalink

    The Error Reporting plugin is awesome. Thanks for taking the time to develop this! I did have a minor suggestion… It would be great if you could change the *TO* address for emails so instead of going to the site administrator email address you could specify where you wanted it to go. For instance I like to have error reporting like this all emailed to a gmail account that just keeps the history forever so I can look back at any errors any time in the future. I also didn't see if the logs actually get cleaned out by themsevles or does this need to be done manually though a cronjob or something? Would be cool to have options in the Error Reporting admin to specify how long to keepp the logs. Anyway again great job!

  11. Posted January 15, 2010 at 2:56 am | Permalink

    i love your plugin and use this in the development of WP. Please can you change on the update the follow line, the function has the old paramter user_level and this was deprecead in WP 2.9 and now i have an all pages an error. Thanks
    $mitt_er_op = add_options_page('Error Reporting Options', 'ErrorReporting', 'manage_options', basename(__FILE__), 'mitt_er_options_page');

  12. Posted February 10, 2010 at 3:01 am | Permalink

    @Alex Kah
    Thanks for the suggestions. Error Reporting RC 1.0.0 now has an Auto Delete old log files feature. I'm not sure how I feel about sending email notifications to an optional address, but I'm thinking on it.

    Thanks for the heads up. The deprecated user_level has been replaced in Error Reporting RC 1.0.0

    Note* I have disabled further comments in this post. Please make comments in the Error Reporting Plugin Release Candidate post.