Perhaps. However I believe that customization of the admin is not a bad thing. On the contrary it allows people to use it for most everything that they need without having to write duplicate code... One such thing is the thread_locals hack for created_by/updated_by...
Imagine if you wanted to dynamically set the created_by and updated_by fields and were forced to "write a custom view".... for every model you have... that basically takes away the usefulness of the admin. Here is an idea: The Admin class should be able to define post_ and pre_save hooks that are called before or after all Manipulation of the model is done (there are post_save hooks for the save method, but they are still called before the Manipulator is done working with the model) On 11/7/07, Collin Grady <[EMAIL PROTECTED]> wrote: > > > Dmitri Fedortchenko said the following: > > Well django does recommend using the admin for everything admin-related, > > if I stop using the admin for editing an article, then I would have to > > write a whole bunch of code just to edit a single article. Suddenly the > > benefit of a unified admin interface is lost and I have to deal with > > permissions, UI, validation, forms.. it seems like a nightmare for > > something should work in the first place... ( i.e. overriding the save() > > method to add extra functionality) > > > > From the django features list: > > A dynamic admin interface: it's not just scaffolding it's the whole > house > > [The philosophy here is that your site is edited by a staff, or a > > client, or maybe just you and you don't want to have to deal with > > creating backend interfaces just to manage content.] > > > > The message seems clear to me. ;) > > It's not meant to do absolutely everything though - trying to hack it to > do something it doesn't is usually harder than writing a really simple > custom view :) > > -- > Collin Grady > > If I had any humility I would be perfect. > -- Ted Turner > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
