Thanks Malcolm,

I'm going to read through the source code and see how I can create a
new template with my custom authorization. So do you reckon that
django admin system is already sufficient not to be overridden?

Best regards,

On Mar 16, 9:58 am, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> On Mon, 2009-03-16 at 09:40 +1100, Joshua Partogi wrote:
> > Dear all,
>
> > I need a custom authorization needs for the admin system. I need to
> > define certain users that is allowed to access certain admin
> > functionality. I also need to check whether use has logged in or not.
> > In the end I might be creating the admin from scratch.
>
> > Is there any documentation I can read about this admin system so I can
> > override it or maybe create a new one from scratch?
>
> The source code is the documentation here. There are lots of docstrings
> and comments scattered throughout. django/contrib/admin/sites.py is the
> main entry point for registration. A large portion of the heavy lifting
> is in django/contrib/admin/options.py (e.g. the ModelAdmin class).
>
> We tend to avoid writing anything much more than that at the moment,
> since it would predominantly be repeating the code in English
> (duplication) and there are lots of other higher-impact places where we
> can be spending our time.
>
> However, instead of thinking you'll have to replace the whole thing,
> certainly look at customisations you might be able to make. All of the
> things you described in your initial paragraph can be done *without* any
> customisations (admin permissions and admin already requires
> authentication), for example.

--~--~---------~--~----~------------~-------~--~----~
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 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to