On Tue, 2011-11-22 at 10:52 -0800, hynekcer wrote:
> Philip, a runtime error ("500") is probably masked by a bad
> configuration of apache+mod_wsgi. First fix error reporting then fix
> the reported error or ask.
>
> 1) An unprivileged user should get a general error message if you try
> some demo Django application with intentionally added DivisionZero
> error in some view.
>
> 2) An easy way to get details is to fill ADMINS = (('Your Name',
> '[email protected]'), ) in settings.py and verify that you get an email
> or you can use more advanced ways or try it with debug mode and verify
> that debug mode is not worldwide accessible
>
> This is not at all a problem specific to Satchmo or at least one
> general Django problem is there. Satchmo uses by default an error
> message template satchmo_store/shop/templates/500.html if it was not
> in debug mode.
Hynek, why do you say that this is a runtime error ("500")? Apache
never returns HTTP 500. I filled in the ADMINS tuple and restarted the
server, reproduced the problem, and do not get any email. As far as I
can tell, neither Apache nor Django nor Satchmo realize that anything
went wrong -- or at least there's no indication of anything wrong in
Apache's or Satchmo's logs.
Here's some new information: satchmo.log on a webpage that refuses to
load, and satchmo.log once I delete the image in the admin interface and
reload that same webpage:
http://www.qnan.org/~pmw/tmp/satchmo-bad.log
http://www.qnan.org/~pmw/tmp/satchmo-good.log
Please tell me if this helps any...
Thanks again for the replies.
--
You received this message because you are subscribed to the Google Groups
"Satchmo users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/satchmo-users?hl=en.
