No backtrace shown on web page although running with ":debug t"

[Mikael Andersson]

I just get an "Oops, we could not complete your request because of an internal error." but I do not get any error information.

I have adapted weblocks-demo and made some changes in the employee.lisp, but I do not have a clue where the problem is.

When I click on an another menu option and then click on the Employee menu item again, I get the following information on the web page, i.e. not much:

Internal Server Error

An error occured while processing your /primarvarden/employees request.

---

Error Message

ERROR

Backtrace

BACKTRACE

Thanks in advance!

Mikael

[Scott L. Burson]

I don't know what's causing the error, but you should be able to debug it.

It used to be the case that server errors, in debug mode, would cause a backtrace page to be displayed in the browser.  That stopped working at some point, I think because of changes to Hunchentoot.  A small change to Weblocks will make it so server errors bring up the Lisp debugger, which is the behavior I prefer anyway, as it lets me debug the error interactively (I am using SLIME).  in debug-mode.lisp, add this line to 'enable-global-debugging':

  (setf *catch-errors-p* nil)

and this to 'disable-global-debugging':

  (setf *catch-errors-p* t)

I have submitted a patch (pull request) to Leslie with this change.

I don't know, though, whether most people would prefer the original behavior of generating a backtrace page.  Maybe that deserves some discussion.

-- Scott

Mikael

--
You received this message because you are subscribed to the Google Groups "weblocks" group.
To view this discussion on the web visit https://groups.google.com/d/msg/weblocks/-/tvsmFJCNOLEJ.
To post to this group, send email to webl...@googlegroups.com.
To unsubscribe from this group, send email to weblocks+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.

[Mikael Andersson]

Many thanks! Now the problem solving is a bit easier! :)

I read about that variable at some point but I was certain that it should be set to true. I mean, since I wanted to catch any errors, it was logical for me to set it to t and not the opposite, or does it mean: Do no let Hunchentoot catch the errors but rather Weblocks, therefore set it to nil?

/Mikael

To unsubscribe from this group, send email to weblocks+unsubscribe@googlegroups.com.