Hi Ed, On 11/10/2014 03:43 AM, Dr Ed wrote: > I don't really think it's the Custom model that's at fault here - this > migration was created months ago. The point is that auth migrations are > stored in, to my mind, the wrong place > (in > /Users/XXXX/.virtualenvs/YYYY/lib/python2.7/site-packages/django/contrib/auth/) > and a separate problem revealed this to me. I've included a stack trace > below though.
The migrations for django.contrib.auth are part of Django, thus they are properly located in Django. You should never create or modify migrations for contrib auth, so it's not a problem that those migrations are in Django. When using a custom AUTH_USER_MODEL, that custom user model should be in one of your apps, not in contrib.auth, and the migrations for it should also be in your own app, not in contrib.auth. Changing the value of AUTH_USER_MODEL during the lifetime of a project is not supported (see the warning at https://docs.djangoproject.com/en/1.7/ref/settings/#auth-user-model). If you're trying to do that, I'm not surprised if you're running into difficulties. It's probably possible, but I don't know how it's done. If you really need to, you might consider just backing up your project's data, removing all migrations in your project and re-starting from a totally fresh database, then re-loading the data from backup. I wouldn't be surprised if that's the simplest option. Carl -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5460FE5A.9050802%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
