I meant, the phenomenon that mod_wsgi behaves differently with my old conventions.
Sorry for my short English.;; On 7월29일, 오전3시42분, Karen Tracey <kmtra...@gmail.com> wrote: > 2009/7/28 Daybreaker <daybreake...@gmail.com> > > > > > 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. > > It isn't clear to me what, exactly, you are asking might should be > considered a bug? > > You start by saying you solved the problem by following the documentation. > OK, so if you follow the documentation, you don't have a problem? > > Putting admin definitions in admin.py (and calling admin.autodiscover()) > from urls.py definitely does work with Django 1.1 rc1 + mod_wsgi. So what > is the "this" that does not work in your case? > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
