I've been down this road and I will say that although you can modify the Admin to do everything you need - it actually turns out to be more complex that just writing your own CRUD (which newforms makes a delight).
It's a shame in some ways - Admin is so nearly ready for this kind of thing that it's very tempting to try and use it but in any real world app your requirements will differ from Admin's in so many small ways that you will be fighting it all the way. I've got a site where registered users are using Admin in the way you describe but their requirements were simple. I'm working on a simple CMS and I'm going to use Admin initially but the minute I have to start doing anything complex I'm going to write my own 'admin'... On May 10, 8:52 pm, Doug B <[EMAIL PROTECTED]> wrote: > > Why is that a bad idea? > > If I mainly need CRUD operations it is natural to solve it with admin > > interface. > > Cannot these "security issues" if any eliminated, and use the admin > > interface for a whole site? (if it needs just CRUD). > > ->ADMIN<- Interface. It wasn't designed to be an entire site. If you > only need CRUD, it's relatively easy to do writing your own views. > Even if you could use the admin, I'm not sure it would be much > easier. Writing your own views is very easy in Django, especially if > you only need basic crud and can use the model form helpers. A simple > CRUD view could be 8-10 lines of code, plus a basic html template. > Permission checking can be done with reusable decorators. Personally > I fnd writing a view much simpler than trying to make the admin do > exactly what I want. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
