Symphony.

Who has experience with the way 2.0 handles error messages? Like for instance when your mysql server crashes, you used to get a 'symphony, cannot establish connection...' is this now a custom generic error page, unless you are logged in? Can one set 'error page' as page type?

The "generic error" page you see related to failed connections is actually not right. Looks like there is a bug with it and all you get is 'Line X -" rather than anything meaningful.

However, the catch with database errors, or PHP errors is that they generally will stop Symphony from actually rendering your custom error page.

E.G. The database stores the information on a page, including type. If a connection cannot be established, than Symphony doesn't even know that page exists.

I had been tinkering with some ideas for a static custom error page, that Symphony falls back to, but that is still in the works.

I see, a static custom generic error page would rock because you can keep the 'branding' of the site going so an error is less shamefull, and doesnt start disclosing how your framework works. But then again how do you get information as an admin about what is wrong; in your apache logs? Or could we start using codes (like microsoft) that have a meaning for symphonians, but not for the general public?