If you are running the dev server in a terminal the traceback should show up there. The error messages should show up in the browser like you expect, the only time I can think of that I've seen that happen (debug = true and no browser traceback) was when a UnicodeDecodeError occurred while Django was trying to render the browser traceback.
I would take a look at your terminal and see if any traceback is showing there. In case anyone is interested, in my particular case I had a setting that was registered with Mezzanine as editable. Any time I edited it and subsequently tried to use it in the admin a byte string was returned so I had to decode the byte string as utf-8. On Mon, Feb 3, 2014 at 2:50 AM, <[email protected]> wrote: > Hi, > > >Do you mean why can't you do {{ settings.DEBUG }} in a template? > >Or are you talking about the debug error messages? > I mean debug error messages. > I've set DEBUG=True in my settings.py > > This is a development install on local machine (macosx) inside virtualenv > I am trying to add some 3rd party payment processor just pip installing it > and adding it to installed apps gives an error. > Since this is development server not apache nor nginx I don't know where > to set up logs. > With DEBUG=True I would expect to have some error details in browser all i > have instead when navigating to http://127.0.0.1:8000 is following > message: > > A server error occurred. Please contact the administrator. > > Regards > > Jaroslaw > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
