Re: Attach a technincal html response to email on server error

2011-11-13 Thread Ric
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

Re: Attach a technincal html response to email on server error

2011-11-13 Thread Benjamin Wohlwend
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

Re: Attach a technincal html response to email on server error

2011-11-13 Thread Ric
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

Re: Attach a technincal html response to email on server error

2011-11-13 Thread John Paulett
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

Re: Multi-DB support within transaction middleware

2011-11-13 Thread Yo-Yo Ma
Before voting for more magic to the transaction middleware, I'd vote to remove it altogether. Explicit is surely better than implicit in this case. The admin already uses commit_on_success, etc. On Oct 18, 1:22 pm, David Winterbottom wrote: > The current implementation of django.middleware.Transa

'default' option for FileField - potential feature, bug, or lack of documentation?

2011-11-13 Thread ptone
This is somewhat of a design decision needed. Currently it seems that FileField doesn't do anything interesting with the "default" option to the field. It certainly could, but there is nothing in the documentation about what default means in the context of a FileField. It seems rather brain-dead

Wiki page on global state

2011-11-13 Thread ptone
Following several discussions on IRC where I realized my understanding of the issue was far from complete, I did some reading and have done my best to summarize what I understand to be the current state of affairs: https://code.djangoproject.com/wiki/GlobalState The idea is that this page could b

Error in formfield in django.db.models.field

2011-11-13 Thread Ric
the field class define this code def formfield(self, form_class=forms.CharField, **kwargs): """ Returns a django.forms.Field instance for this database Field. """ defaults = {'required': not self.blank, 'label': capfirst(self.verbose_name),