Good day.
In the django/contrib/admin/options.py, I see that opts reference is
available in the template context of changelist_view, delete_view,
render_change_form, etc. but however not in history_view. We have a
simple scenario where we override the object_hostory.html and need
access to Model'
Am 10.06.2008 um 03:16 schrieb Karen Tracey:
> I'd trade your controversial part for an alternative: merge mewforms-
> admin back to trunk now. It's been as 'usable' as old admin for
> months. Sure, it's got a couple of dozen 'blocking' bugs in the
> tracker but none of them are all that serious
ch defaults to [1st of current
month to the last day of this month].
-Alen Ribic
On May 9, 10:12 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Fri, May 9, 2008 at 3:58 PM, Alen Ribic <[EMAIL PROTECTED]> wrote:
>
> > Reporting is quite common in
Reporting is quite common in my area of work at the moment and most of
the time some form of aggregation is required to build meaningful
reports. (For such case I have substantially more custom/native
queries then standard ones.)
-Alen
(PS. if there is a need to give some real example with regard
ROTECTED]> wrote:
> whats wrong with overridng save, then calling the super.save() ?
>
> On May 2, 8:10 am, Alen Ribic <[EMAIL PROTECTED]> wrote:
>
> > At the moment, it doesn't seem that a developers can do pre-save/post-
> > save work c
At the moment, it doesn't seem that a developers can do pre-save/post-
save work cleanly when dealing with Forms in NewForms Admin using
django.newforms.models.ModelForm.
For instance, if I'd like to send a notification email to a client
once a form has been submitted for the first time (add_view)
