It looks like there may be some funky problem with imports. The models.py file imports some external modules that in turn import the models.py file. Removing the functions that rely on this import and then removing the import make the admin interface work again, but I lose a lot of important functions this way. Bleh.
On Dec 30 2006, 2:35 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
On Dec 26, 1:37 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > On 12/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Is there any way to see where this is bombing out? Perhaps some kind of > > help from Apache? There are no error messages in the apache2 error log > > or on theadmininterface, it's just that the application andallof > > its models/classes aren't visible.The app is in INSTALLED_APPS? The model contains an inner classAdmin? The model has at least oneadmin-editable field? > Code?Yes, the app works just fine outside of the admin interface and the admin interface did work for a good while until it suddenly stopped. Yes, there is at least one admin-editable field. If it was a syntax problem, I figured pylint and the Python interpreter would pick up on it.
--~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
