On Fri, Jun 18, 2010 at 11:30 AM, Halo Maps <[email protected]> wrote:
> I literally just caught one in action. The error was a CFML run time error > the one I suspected. Great--so at least the root cause has been identified. > Besides not have error catching (on purpose for this test) I can only > assume > I have something configured incorrectly since I would assume that openbd > would have either appended the generated html error page or served it > instead. Unless I am misunderstanding something. > Well, no--if you were hitting OpenBD directly, you'd probably see the 500 error on the screen. And maybe you're still seeing a basic 500 error message on the screen as things stand now. But what it doesn't do is output the details of the error to the screen unless you have Extended Error Reporting checked in the admin console, at which point (I believe anyway; I'd actually have to experiment with the case of 500 errors) you'd see exactly what's getting logged in the runtime error HTML file. Let me know if that doesn't address your ultimate goal with all of this. If you know files might be gone before they try to be read, I guess I'd put that block of code in a try/catch so you can handle as appropriate for your application. -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon online manual: http://www.openbluedragon.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
