Thank you for your reply I learned something. Unfortunatelly all model admin registration are made in admin.py files. Elsewhere I found an advise to turn debuging on when you launch manage.py runfcgi and since I added that parameter to the command line I don't have any problem.
I'm still looking for a definitive solution. On Feb 2, 3:09 pm, Karen Tracey <kmtra...@gmail.com> wrote: > On Tue, Feb 2, 2010 at 6:10 AM, Thomas Schreiber <t...@insatsu.us> wrote: > > Missing applications in the admin is the sign of an error in an admin.py > > I'd double check there first. > > Or admin registrations being placed somewhere besides admin.py. Sometimes > people put them in models.py and that "works" under the dev server because > it validates models (and thus forces a load of all models.py files) during > startup. Under other servers there's no guarantee a particular models.py > file will be loaded early like that, thus people see apps go missing from > admin under production setups when they've placed admin.site.register calls > in a models.py file. > > 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-us...@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.
