It will be the good and very handy help for all blueprint developers that yahoo provide List of possible errors that may occur,their possible reasons so that we can take precautions,And possible help and steps how to resolve them.
I know errors can not be determined before and removing them will be good R & D.But still all common errors we can avoid...isn't it.
So waiting for the day when yahoo may think on that...and make developer's work easy and keep development work interesting and exciting...........
If you use the Blueprint.php class, there's this function that helps you identify which line of code that causes an error (in PHP): set_error_handler( "blueprintErrorHandler" );[/code]
the important line shown by Natali is this: set_error_handler( "blueprintErrorHandler" );
so, write your (uday) own error handler function. anything but fatal error then can be gracefully handled by that function which its only job is to emit error message wrapped in valid BP xml, eg. <page><content><?php echo $erro ?></content></page>.