google-code-export / cfwheels

Automatically exported from code.google.com/p/cfwheels
0 stars 0 forks source link

Wheels errors not showing #164

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
My config is Mac/Apache/CF8

When I screw something up in my Wheels app, a blank browser window is shown
instead of the Wheels error.

I can get the error to display if I add a <cfabort> to the end of
wheels/events/onerror/wheelserror.cfm

Original issue reported on code.google.com by chriscle...@gmail.com on 31 Mar 2009 at 1:55

GoogleCodeExporter commented 9 years ago
Does it make any difference if you run in "design" mode or "production" mode?

Original comment by per.djurner@gmail.com on 31 Mar 2009 at 6:38

GoogleCodeExporter commented 9 years ago
I'll have to check on that later, but right now I'm in design mode.

Original comment by chriscle...@gmail.com on 31 Mar 2009 at 2:16

GoogleCodeExporter commented 9 years ago
Go to line 8 in wheels/events/onerror.cfm and put cfoutput tags around 
#returnValue# 
and see if it makes a difference.

Original comment by per.djurner@gmail.com on 31 Mar 2009 at 4:28

GoogleCodeExporter commented 9 years ago
Tried running it in production mode, and it still didn't work.

I also tried putting the <cfoutput> around #returnValue#, and that didn't work
either. I tried that in both design and production modes.

Original comment by chriscle...@gmail.com on 2 Apr 2009 at 1:27

GoogleCodeExporter commented 9 years ago
It's possible that r2258 fixes this (if you had any plugins installed). Please 
give 
that revision a try.

Original comment by per.djurner@gmail.com on 2 Apr 2009 at 9:25

GoogleCodeExporter commented 9 years ago
Hmm, now I'm getting Wheels error messages (which is good!), but when I do this 
in a
config file:

<cfset set(showErrorInformation=false)>

I don't get the custom events to load, like what's defined for
events/onmissingtemplate.cfm or events/onerror.cfm, which should be fired in
production mode or with the showErrorInformation setting, correct?

Original comment by chriscle...@gmail.com on 6 Apr 2009 at 1:22

GoogleCodeExporter commented 9 years ago
Forgot to mention, I can get the custom events like onmissingtemplate to run, 
but
only if I issue a reload=true, reload=production, reload=whatever in the URL.

Original comment by chriscle...@gmail.com on 6 Apr 2009 at 1:24

GoogleCodeExporter commented 9 years ago

Original comment by chriscle...@gmail.com on 6 Apr 2009 at 1:24

GoogleCodeExporter commented 9 years ago
I wonder if it has something to do with header status codes and the way 
different 
browsers handle them. If you search for 404 and 500 in the code and comment out 
those 
lines (there should be 3 of them) it might make a difference?

Original comment by per.djurner@gmail.com on 6 Apr 2009 at 9:28

GoogleCodeExporter commented 9 years ago

Original comment by per.djurner@gmail.com on 13 Apr 2009 at 9:41

GoogleCodeExporter commented 9 years ago
This has been fixed in a recent revision according to Chris. Closing ticket.

Original comment by per.djurner@gmail.com on 15 Apr 2009 at 2:02