Malcolm Tredinnick wrote: > On Sat, 2006-06-24 at 23:57 -0700, [EMAIL PROTECTED] wrote: > > Not sure if this makes a difference or not, but when I run "manage.py > > validate" it says that there are 0 errors... and like I said > > originally... The files on my production server are an exact mirror of > > what is on my dev server. My models shows up on the dev's admin screen, > > just not on the production site... so I doubt that it's something as > > simple as a botched import. Thanks for the patch btw... should come in > > really handy in the future. > > > > Any other ideas? > > Something is certainly different between the two setups. How did you > check that files are the same on the two systems? If you do something > like > > find -type f ! -name \*.pyc | xargs md5sum > MANIFEST > > on each server from the root of the project dir, do you get exactly the > same file produced as a result? Because at this point, I would be > suspecting something like a subtle whitespace difference. > > Also, if you use the manage.py shell and try something like this: > > >>> from weblog.models import Entry > >>> Entry._meta.admin > <django.db.models.options.AdminOptions object at 0x2aaaaf920b50> > >>> > > (customise to suit your circumstances), does it produce similar results > on the two machines? Obviously the big hexadecimal number will be > different, but it should at least return a result. Maybe just check that > the equivalent of Entry._meta.admin.fields is the same, too. > > This is a really strange problem. To compute the list of admin apps, the > admin interface just runs through your list of installed apps and > retrieves every one with an Admin class. So identical settings and code > files should lead to identical results. > > Malcolm
Very strange indeed same thing going on here. It works fine using django-admin.py runserver. But using both lighttpd + fastcgi and apache2 + mod_python it fails. I have run out of time for this afternoon but I tracked it down to django.db.models.load_app raising an exception on module not having a model attribute. However, running the import command manually in django-admin.py shell shows it has a model attribute and doesn't throw an exception. I'll look into the problem more tomorrow. But, it is very strange indeed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
