On Mon, Aug 25, 2008 at 5:01 PM, Steve Potter <[EMAIL PROTECTED]>wrote:
> If you look in the django-users archive I think I remember a few other > people having the same auth problems you are describing, however I > don't remember the solution. > As I recall a lot of people reported this error, but it ultimately turned out to be due to either 1 - not calling admin.autodiscover() 2 - not updating customized admin templates 3 - perhaps other incomple admin migrations There certainly was not any requirement to dump/reload tables. As for strategies to migrate forward, beyond carefully following the instructions in backwards-incompatible changes, searching the user's group for similar error messages will likely turn up people who ran into and solved the problem before you hit it, especially for any changes that are more than a few days old. Also, when you're doing a big jump forward, note the revision you are updating from. That way you can 'svn -rnnnn up' back to that if you run into a temporarily unsurmountable problem. 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 -~----------~----~----~----~------~----~------~--~---
