I've solved this problem. The solution: JUST FOLLOW THE DOCUMENTATION.
...I have used Django from 0.96, so my convention was different from the recent Django docs. I used to put admin.site.register() and ModelAdmin classes in models.py (and I moved those classes to admin.py and manually imported them from models.py), but for whatever reason, this does not work with Django 1.1 + mod_wsgi. I'm not sure this should be considered as a bug or not. On 7월28일, 오전12시39분, Ramiro Morales <cra...@gmail.com> wrote: > On Mon, Jul 27, 2009 at 12:20 PM, Daybreaker<daybreake...@gmail.com> wrote: > > > Seehttp://code.djangoproject.com/ticket/11563:) > > > Yes, I had to ask it here first, but I didn't think autodiscover() is > > the only(?) way to be recommended, so I thought that was a bug. > > > So my question is the last comment there -- Is autodiscover() the > > only way that is recommended as the official option? > > Another very helpful resource for this kind of topics > is the admin app documentation: > > http://docs.djangoproject.com/en/dev/ref/contrib/admin/#hooking-admin... > > The tile of the section is "Hooking AdminSite instances into your URLconf" > > HTH > > -- > Ramiro Moraleshttp://rmorales.net > > PyCon 2009 Argentina - Vie 4 y Sab 5 Septiembre > Buenos Aires, Argentinahttp://ar.pycon.org/2009/about/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
