Emile wrote: > Hi All > > just a suggestion (albeit from a lesser mortal) - to put the class and > function name into errors. I've struggled for a while trying to find the > problem I was experiencing, for it to end up being something completely > different to what I had interpreted the error as. Had I known the function > that threw the error, it would've saved me a lot of time.
Ussually this is the case (an exception is often shown as a stack-trace, which contains class, method and line numbers of all methods on the stack...). Your description of the problem is not entirely clear. It could be that your app-server is not configured well to show exceptions. The other option is that you mean errors in the log. The source of such an error could be logged by %M.%L in the logging pattern. The last options is that you are hit by a certain browser's 'user friendly' (but _very_ developer unfriendly) error pages, which should be switched of asap in any case (or even better is it to switch of the complete browser, and opt for any other one). Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US
