Changes between Initial Version and Version 1 of Ticket #24524, comment 20


Ignore:
Timestamp:
03/22/16 18:32:30 (6 years ago)
Author:
Juergen Brendel
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #24524, comment 20

    initial v1  
    55I use version 0.7.28 of `social_auth`. And, yes, it does come with migrations. I confirmed that they were installed by pip. However, those seems to be migrations of the wrong kind (south?), so they are not recognized.
    66
    7 Your comments, however, allows me to narrow my search, so I was finally able to find a solution that someone had posted on StackOverflow: [http://stackoverflow.com/a/33562236]
     7Your comments, however, allowed me to narrow my search, so I was finally able to find a solution that someone had posted on StackOverflow: [http://stackoverflow.com/a/33562236]
    88
    99In short: Find the original migrations that django-social-auth came with. Delete them. Then run `python manage.py makemigrations social_auth`. This will replace the original migrations with 'the right kind' of migrations. When you then run `python manage.py migrate` everything works as advertised.
     
    1818
    1919I'm lucky, because I don't need to actually migrate old databases, I can start from scratch, but I could imagine that this could cause some issues for people that do need to migrate actual databases.
     20
     21Just want to say thank you for looking into it. Without your insight into social-auths migration issues, I would not have known where to look (or what to look for), so I have to thank you for pointing me in the right direction. And I have to thank Alfredo Rius, who posted a solution on StackOverflow.
Back to Top