Error Reporting: IP option

Using Maia's code that allowed for the input of a couple "exception" IP addresses to Exponent's error reporting system has been huge, especially with clients who only use IE7, in which having Error Reporting turned on nukes the site's css after 24(or so) css files.

This code:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
// config check for IP address... Only the IP in here will see the
debug stuff, and minify breakdown!

//you can stick this inline anywhere in the system to debug only
certain elements. if in a view, wrap in php variables.
if($_SERVER['REMOTE_ADDR']=='_____your IP_____' ||
$_SERVER['REMOTE_ADDR']=='_____your IP_____')
 define("DEVELOPMENT",1);
else
 define("DEVELOPMENT",0);
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

In the config files has saved TONS of Client frustration. The down side is it screws up the CONFIG FILE. I propose the addition of some config variables that allow for "Exceptions" in the "USER ERROR REPORTING?" selection. The ability to only use error reporting on 1, 2, or a limited number of IP addresses eliminates a client frustration when communication or development requires them to be looking at (or working with) a site in development