The admin interface is just that, an interface for administration. If you need something beyond that you should keep it outside of it. I would give it a thumbs down on trying to "hack" the interface, modify the templates, include pages that look the same, etc.. it's just too time consuming.
My two cents. On Dec 18, 11:01 am, "Daniel Kvasnicka jr." <[EMAIL PROTECTED]> wrote: > Thanks for reply, > I also wanted to ask how would one implement a "approving mechanism". I > have a boolean field which says whether an article has been published > or not. And I need to have a "Publish" button with each article entry, > available only to admins. Does Django support something like this? I > just don't want force editors to change 0 to 1 (or False to True, > whatever...) when they want to send an article to the frontpage... > Another thing is that I need to allow authors to write and edit > articles but not publish them but -- wouldn't the approving action be > taken as a regular "edit" permission level? > So, provided this all, is it more productive to hack that functionality > to Django admin or to write a standalone app for this? > > Thanks, > Dan > > On Dec 14, 5:55 pm, "va:patrick.kranzlmueller" > > <[EMAIL PROTECTED]> wrote: > > Am 14.12.2006 um 17:05 schrieb Daniel Kvasnicka jr.: > > > > Hi djangees, > > > I'm a TurboGears user, I like CherryPy, Kid and so. I like Django as > > > well and tried the tutorials. > > > What I like about Django is (obviously) the auto-generated admin > > > interface. > > > > However, what I need to know is how > > > easy/difficult/deprecated/encouraged is to hack the auto-generated > > > admin interface. I'm doing this app, where our customers login and > > > vote > > > for features that we plan to implement in our services. And besides > > > CRUD, I need to enable my boss to login and view a whole bunch of > > > stats > > > about who voted for what and how is that particular guy important for > > > us etc... So, my question is, how easy would it be to "add a page" to > > > admin, that would have the same auth restrictions, same GUI but would > > > only display bars and graphs generated from the DB? Or would you write > > > an admin section from scratch in that case?write custom views (or use > > > generic views). > > making your site _look_ like the admin is probably harder than > > writing the views. > > > adding a page to the admin is quite easy though: > > just extend the index-template and link to your site ... and don´t > > forget to use > > myview = staff_member_required(never_cache(myview)) > > > patrick > > > > Right now I'm writing everything on my own in TurboGears. It's not > > > bad, > > > since auth/auth management is pretty intuitive in TG, but it's kinda > > > boring... > > > > Thanks for your opinions, > > > Dan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
