Error Reporting Plugin Release Candidate

The first version of the Error Reporting plugin became available in March of 2007. Since then there have been a few changes, most notably, the Ping Error with dashboard widget feature, and an Auto Delete of old error log files feature that has been added in response to Alex Kah's suggestion. And thanks to Frank's comment, a deprecated parameter has been replaced. It wouldn't do to have the Error Reporting plugin causing errors now would it?

Some known issues remain. With WordPress' switch to SimplePie, many E_STRICT errors are thrown as a result of WordPress maintaining support for PHP 4. In order to avoid Internal Server errors, the Error Reporting plugin does not handle any E_SRICT errors from the class-simplepie.php file. Until WordPress no longer supports PHP 4, this can not be changed.

Perhaps more troublesome is reading the log files under certain configuration settings. Because every error changes permissions to read from, and write to, the error log files, and then makes them secure, if an error occurs after the permissions have been set to "NOT secure" to allow reading, they still can't be accessed. This requires temporarily reconfiguring the Error Reporting plugin's settings so as to not include whatever is causing the error.

TO DO: Find some way to temporarily disable the Error Reporting plugin while the permissions are "NOT secure" and then restore the configuration when made "secure" or after a period of time.

Possible solution: Adding another option or two, i.e. "user's preferred settings" and / or "current settings" to hold configuration settings. This could be "set" by a plugin user and could then later be used to reset the settings after they have been changed.

Alex Kah also suggested that the Error Reporting plugin have a way to send email notifications to an address other than the blog's "admin_email" address. I am hesitant to make this too easy to do, as it would introduce the potential of sending many, many, many, many, many emails to a wrong email address. It's one thing to accidentally flood your own inbox, quite another to flood someone else's. Not to mention sending information about your blog that may create a security risk.

TO DO: Seriously consider adding a "send email notifications to" feature.

Possible solution: As it is now, the plugin can be hacked to hard code an email address in place of the "admin_email". This could be replaced with a CONSTANT that could be defined near the beginning of the script to make changes easier. Or an option could be added so hacking wouldn't be required.

Any comments regarding these issues, or other suggestions, are most welcome and will be greatly appreciated.

For more information please visit the Error Reporting Plugin page.
This post is for comments, suggestions etc. If you need support for the plugin
– please visit the Mittineague Forums (registration required to post).


  1. Posted June 6, 2010 at 6:27 am | Permalink

    Short time ago I had a problem with the wordpress crons for trackbacks und pings (linked blog articles in my own articles). After debugging a long time the reasons was found as of memory limit of 64M exceeded for this cron jobs. Is this a kind of error what this plugin would report?

  2. Posted June 6, 2010 at 2:49 pm | Permalink

    When the Error Reporting plugin is activated, it becomes the error handler. So all errors that can customarily be dealt with by using a custom error handler are passed to it and can be reported.

    The Ping Errors feature first tests to see if the error is an E_WARNING and then tests for the strings "fsockopen" and "connect" in the passed error message. It also tests if the file the error occurred in was the class-IXR.php file. If so, the error will be reported as a ping failure. Other errors that may be associated with it (eg. memory errors) are not included with this feature.

    But …

    The Error Reporting plugin is highly configurable. Both as to what error types and what files the errors occur in are to be reported.

  3. Craig
    Posted October 26, 2010 at 5:01 pm | Permalink

    Any idea on what my ping error is?

    unable to connect to :80
    (php_network_getaddresses: getaddrinfo failed: Name or service not known) ~ October 26, 2010 6:22 pm

    Can you add a subscribe to post plugin to your blog so I know when you reply? :)

  4. Posted November 1, 2010 at 4:11 am | Permalink

    Usually there is a URL before the port. eg.

    unable to connect to

    and then the reason. eg.

    Temporary failure in name resolution
    Connection timed out
    Connection refused

    Yours says

    Name or service not known

    which makes sense for an "empty".

    My guess is you have an empty newline in your Settings -> Writing -> Update Services list.

  5. Craig Mullins
    Posted December 21, 2010 at 9:48 pm | Permalink

    Looked couldn't find any extra lines.

    As far as I can tell my update list is good…

    Happen to know where in the database I would look to see if something is screwy there…

    You need a subscribe to comment plugin homie… I didn't know you replied..