Hi, This same error materialized in another way in my case. It said:
Caught an exception while rendering: Tried change_stage in module django.contrib.admin.views.main. Error was: 'module' object has no attribute 'change_stage' I spent half a day figuring this out with the help of this thread. It turned out that the cause, in my case, was because I missed a pre-1.0- style admin entry in an urls.py that was included in the main urls.py. My problem was solved as soon as I changed that to the 1.0 preferred way as specified in: http://docs.djangoproject.com/en/dev/intro/tutorial02/#activate-the-admin-site Just thought I'd post this as an addition to this thread in case anyone else has the same problem. -geir On Aug 14, 10:48 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Thu, Aug 14, 2008 at 6:42 PM, tooper gao <[EMAIL PROTECTED]> wrote: > > > how can you change it ? and I have this errors too. > > For the specific error mentioned by the original poster, it's the first > change noted here: > > http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Merge... > > that is, the change in urlconfs. There will be more changes needed in your > code, to move admin declarations out of the model classes, all documented > there. > > 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
