http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/Wpisy z dziennika internetowego Jogger, wspomaganego przez JabberaFri, 30 Jul 2010 16:00:58 +0200JoggerPLhttp://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337142"What you should do instead is to develop automated reporting utility. With PHP it is super easy."You mean plain PHP? Altough I've never tried any of PHP frameworks, I can't help to notice that all serious Python web frameworks provide that functionality by default - usually you just need to configure it to suit your needs. This is the way of programming I would call "super easy".Thu, 05 Feb 2009 13:43:45 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337142http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337157In this case it really doesn't make any difference whether you handle it manually or via framework. In both scenarios sending email should take no more than 3 lines of code. By "super easy" I mean that average PHP developer already possesses enough knowledge to implement any of my suggestions, whereas using framework would first require him/her to learn functionality provided by a framework in order to use it.To be fair I do believe the latter is cleaner/more appropriate.Thu, 05 Feb 2009 13:57:01 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337157http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337166Sending an e-mail with 3 lines of code? That's unusual. Could you please tell me how is that supposed to work? Come to think of it, it is actually possible - if one's using some convenient facility for sending e-mails. But if that's the case, it is no different than using a framework.Thu, 05 Feb 2009 14:07:38 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337166http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337344@Dodek: have you ever heard about mail() function :>? You don`t have to send whole backtrace via e-mail but instead write it to file and only notice yourself about that:try {// my app code goes herecatch( $e ) { file_put_contents( $name = (time() . '.log'), print_r( $e->getTrace(), true ) ); mail( ja@ja.pl, 'Error you bastard!', "New error occured. More details in file: $name" );}RegardsThu, 05 Feb 2009 22:05:47 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337344http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337351mail(), as far as I remember, requires you to setup an SMTP server, which is kind of uneasy task if it is supposed to be done well. That's why I used "convenient facility" phrase instead of "third-party library".Thu, 05 Feb 2009 22:09:40 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337351http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337357@Dodek: but usually you don`t have to set up an SMTP because it`s already prepared.BTW: Stronger, I beg you: update your post and write that errors should not be displayed on a screen :P (display_errors=off)RegardsThu, 05 Feb 2009 22:19:17 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337357http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337629@Dodek: mail() is a no-brainer in PHP world. And if it was a sane developer should write or use handy library to make it actual three-liner.@Michał: I would update if I was totally convinced it was right. I learned that leaving display_errors on results in better feedback from beta testers. The reason is I think that users not always realize that they found themselves in application's erroneous state, whereas offending them with some semi-programming cryptic junk output make them sure they encountered software problem.I would be hesitant leaving it "on" on production machine/stable release, tho.Fri, 06 Feb 2009 13:31:05 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337629http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337633@stronger: I agree with you, that leaving "display_errors=on" on development or staging server is right but on production server it should be turned off ;)Fri, 06 Feb 2009 13:34:18 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1337633http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1343391There can also be a production server in phase ''beta'', which can be for example - first few months of work. And if I understood right:"First, wrap whole application with try…catch statement. Once otherwise unhandled exception is thrown it gets sent via email." this means NO error will be displayed on the screen, no matter display_errors is Of or On.Tue, 17 Feb 2009 23:05:27 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1343391http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1343401@pldmachine: putting everything between "try... catch " will suppress only exceptions. PHP hardly ever throws an exception ;P so that we should suppress errors by setting "display_errors" to "Off" ;)Tue, 17 Feb 2009 23:19:16 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1343401http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1343633pldmachine, Michał, surely catching exception is not enough for successful reporting, hence "php_value error_log log/errors.txt" above. PHP is known to be long standing sucker when it comes to exceptions.The thing is I am not 100% percent convinced that display_errors should be switched off on production box. To me it seems like choosing the lesser evil between "a fuckup that nobody will ever report, except that the app is behaving mysteriously" and "a fuckup that is evident enough for immediate action". I would go for the latter.Wed, 18 Feb 2009 15:08:01 +0100http://stronger.epsi.pl/2009/02/04/just-before-you-lanuch-a-php-application/#c1343633