Sounds similar to what django-sentry already provides:
http://blog.disqus.com/post/1178923988/django-sentry
(we may want to move this discussion to django-users)
On Sun, Nov 13, 2011 at 7:51 AM, Ric wrote:
> oh fantastic... but i read about security issue...
>
> and what about create a model, sa
yes of course i've read it in the documentation... i'v snv the code
right now!
sorry, i missed it.
On 13 Nov, 15:03, Benjamin Wohlwend wrote:
> Hi Riccardo,
>
> On Sun, Nov 13, 2011 at 2:51 PM, Ric wrote:
>
> > and what about create a model, save the traceback in the db, and
> > reopen it from t
Hi Riccardo,
On Sun, Nov 13, 2011 at 2:51 PM, Ric wrote:
>
> and what about create a model, save the traceback in the db, and
> reopen it from the admin?
>
You should have a look at Sentry[1]. It does exactly what you want,
and much more. Easily one of the best tools to monitor errors of your
we
oh fantastic... but i read about security issue...
and what about create a model, save the traceback in the db, and
reopen it from the admin?
On 12 Nov, 03:39, Karen Tracey wrote:
> On Fri, Nov 11, 2011 at 9:35 PM, Ric wrote:
> > yeah i know it can be done...
>
> > i can try to write it in futu
On Fri, Nov 11, 2011 at 9:35 PM, Ric wrote:
> yeah i know it can be done...
>
> i can try to write it in future... it can be a subclass of something,
> i have to open the code.
>
>
You don't have to write anything, you just have to set include_html=True in
the config for the Django-provided admin
yeah i know it can be done...
i can try to write it in future... it can be a subclass of something,
i have to open the code.
could be an interesting contribute?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send e
On 10 nov 2011, at 22:03, Ric wrote:
> hi, i receive django email on 500 error.
>
> with that kind of mail is difficult to debug, because i don't have a
> lot of informations.
>
> it's much more simple to debug when i set DEBUG = True and i receive
> an html technical response.
> with that respon
not a lot of javascript, really. just a script to expand the local
vars...
but make a an alternative content it's not easy.
attach the html response it's pretty easy, maybe just a few line of
code and some import
--
You received this message because you are subscribed to the Google Groups
"Djan
i don't think so...
the debug response have got a lot of javascript... and a lot of email
client (gmail, outlook) escape javascript and could brake some
functionality of the web page... the safest way, in my opinion, is to
leave the content of email as plain text and to attach the html file
to the
With email you can send and html email and text email in the same
email. You are basically sending and html "alternative" email and part
of a multi-part email.
That would be the best bet.
On Thu, Nov 10, 2011 at 3:03 PM, Ric wrote:
> hi, i receive django email on 500 error.
>
> with that kind of
hi, i receive django email on 500 error.
with that kind of mail is difficult to debug, because i don't have a
lot of informations.
it's much more simple to debug when i set DEBUG = True and i receive
an html technical response.
with that response i can read a lot of informations (like vars,
reque
11 matches
Mail list logo
