On 6/20/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
>
> On 6/16/06, Tyson Tate <[EMAIL PROTECTED]> wrote:
> >
> > On Jun 16, 2006, at 3:02 PM, Joseph Kocherhans wrote:
> >
> > > Get rid of the inner Admin class on your tag object. That's what
> > > causes it to show up on the main admin page.
> > >
> > > Joseph
> >
> > If I do that, then I can't add any objects inline. Does Django not
> > allow one to do this?
>
> Odd. I swear it's worked for me before, but now that I think about it,
> the permissions wouldn't be created w/o the inner class... Anyhow, you
> can do this another way by overriding the admin/index.html template.
> It may not be as simple as you'd like, but it will work.
>
> Joseph
>

I opened a ticket a while back about permissions and content types not
being created if a class doesn't have an inner Admin class.
http://code.djangoproject.com/ticket/1856 is the one. I have a patch
attached to it as well which decouples permissions and contenttypes
from the admin.


regards

matthew

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to