Comments on: displaying errors http://php100.wordpress.com/2008/05/07/displaying-errors/ What if... Thu, 24 Jul 2008 19:18:46 +0000 http://wordpress.org/?v=MU By: hitesh http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13112 hitesh Thu, 15 May 2008 10:35:00 +0000 http://php100.wordpress.com/?p=42#comment-13112 keep display_errors off it gives sometime trouble for debugging. keep display_errors off it gives sometime trouble for debugging.

]]> By: website design http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13109 website design Wed, 14 May 2008 10:37:00 +0000 http://php100.wordpress.com/?p=42#comment-13109 error_reporting — Sets which PHP errors are reported error_reporting — Sets which PHP errors are reported

]]> By: Richard Heyes’ Blog: Displaying Errors (based on hostname) | Development Blog With Code Updates : Developercast.com http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13076 Richard Heyes’ Blog: Displaying Errors (based on hostname) | Development Blog With Code Updates : Developercast.com Thu, 08 May 2008 17:12:55 +0000 http://php100.wordpress.com/?p=42#comment-13076 [...] a response to this post on the PHP 10.0 Blog, Richard Heyes offers a method for what Stas was wanting: OK, then what we [...] [...] a response to this post on the PHP 10.0 Blog, Richard Heyes offers a method for what Stas was wanting: OK, then what we [...]

]]> By: Ben Hoffman http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13075 Ben Hoffman Thu, 08 May 2008 15:58:24 +0000 http://php100.wordpress.com/?p=42#comment-13075 In PHP 5, you can register an error handler class and handle all errors as exceptions. Just catch the exceptions and log them (or display them if you wish). In PHP 5, you can register an error handler class and handle all errors as exceptions. Just catch the exceptions and log them (or display them if you wish).

]]> By: bleedingshadow http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13074 bleedingshadow Thu, 08 May 2008 15:10:44 +0000 http://php100.wordpress.com/?p=42#comment-13074 :0) :0)

]]> By: Dougal http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13071 Dougal Thu, 08 May 2008 08:02:30 +0000 http://php100.wordpress.com/?p=42#comment-13071 Yeah, that way would work better. Anyway, I agree with Robert. The only reason its really useful in ASP.NET is because it fires up the debugger and allows you to debug straight away. I wouldn't want to risk seeing a different view of a live website. Development (testing if you can have 3) and Production servers are the solution really. Display everything in dev and hide it in production. It's more important to make sure all errors are logged and checked. Yeah, that way would work better.

Anyway, I agree with Robert. The only reason its really useful in ASP.NET is because it fires up the debugger and allows you to debug straight away.

I wouldn’t want to risk seeing a different view of a live website. Development (testing if you can have 3) and Production servers are the solution really. Display everything in dev and hide it in production.

It’s more important to make sure all errors are logged and checked.

]]> By: Open http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13070 Open Thu, 08 May 2008 06:34:14 +0000 http://php100.wordpress.com/?p=42#comment-13070 You can also implement set_error_handler / set_ exception_handler . I don't have any problems with finding errors. You can also implement set_error_handler / set_ exception_handler . I don’t have any problems with finding errors.

]]> By: SlashLife http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13069 SlashLife Thu, 08 May 2008 05:49:10 +0000 http://php100.wordpress.com/?p=42#comment-13069 @ Dougal: Why not real netmask matching? <code> $masks = array( array('255.0.0.0' , '127.0.0.1'), // loopback array('255.255.255.0', '192.168.0.0') // LAN ); function mask_matching($ip, $masks) { $ip = ip2long($ip); foreach($masks as $mask) // if ((ip2long($mask[1]) & ip2long($mask[0])) == ($ip & ip2long($mask[0]))) if (!(ip2long($mask[0]) & ($ip ^ ip2long(mask[1])))) return true; } return false; } </code> @ Dougal: Why not real netmask matching?

$masks = array(
array('255.0.0.0' , '127.0.0.1'), // loopback
array('255.255.255.0', '192.168.0.0') // LAN
);

function mask_matching($ip, $masks) {
$ip = ip2long($ip);
foreach($masks as $mask)
// if ((ip2long($mask[1]) & ip2long($mask[0])) == ($ip & ip2long($mask[0])))
if (!(ip2long($mask[0]) & ($ip ^ ip2long(mask[1])))) return true;
}
return false;
}

]]> By: Robert http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13067 Robert Thu, 08 May 2008 01:29:08 +0000 http://php100.wordpress.com/?p=42#comment-13067 No, I don't think it would be useful. error_log exists for a reason and I think people should use it :) No, I don’t think it would be useful. error_log exists for a reason and I think people should use it :)

]]> By: Jeremy Privett http://php100.wordpress.com/2008/05/07/displaying-errors/#comment-13065 Jeremy Privett Wed, 07 May 2008 22:50:18 +0000 http://php100.wordpress.com/?p=42#comment-13065 Hey Stas, I think because most PHP installations are on a non-Windows environment that is typically accessed by SSH, this feature wouldn't really see much use. This type of feature is useful in ASP because developers can RDP into the server and load up IE to look at the site from the server itself. Most environments that PHP is deployed in don't necessarily have that capability. I guess someone could use SSH + Lynx to look at the site, but that's not the same as using RDP and a fully graphical browser to inspect your site. How about a way to specify a collection of IP Addresses to display errors to? Although, I think that would be overkill for a system-level option, when this is easily implemented at run-time and wouldn't make a difference to normal users. Hey Stas,

I think because most PHP installations are on a non-Windows environment that is typically accessed by SSH, this feature wouldn’t really see much use. This type of feature is useful in ASP because developers can RDP into the server and load up IE to look at the site from the server itself. Most environments that PHP is deployed in don’t necessarily have that capability. I guess someone could use SSH + Lynx to look at the site, but that’s not the same as using RDP and a fully graphical browser to inspect your site.

How about a way to specify a collection of IP Addresses to display errors to? Although, I think that would be overkill for a system-level option, when this is easily implemented at run-time and wouldn’t make a difference to normal users.

]]>