Django-registration is not maintained for quite a while. And it needs some modification with an update to Django 1.7, at least for my project. So, this might be a good time to migrate from django-registration. From a number of discussions I got an impression that django-allauth is the closest in design and among the most advanced alternatives to django-registration.
I found only one blog [1] about this kind of migration. A link to it says the move is simple, but the very blog cannot be opened at the moment... Any other tips/notes/recommendations are most welcome!
[1] http://blog.willmer.org/2014/04/migrating-django-registration-django-allauth/
Ok, answering my own question, using my answer in another place...
To convert the site from django-registration to django-allauth, I only needed to change "'registration'," to "'allauth'," in INSTALLED_APPS within settings.py (well, I also moved it closer to the end of the list), and all instances of id_username to id_login. All together, 5 files including a test and a css file. I used id_username as a name for an id attribute and changed that too, for consistency. 3 files (1 line per file) would be enough: settings.py and two templates.
I used just basic authentication, and the templates for login pages are in the project.
I also found that the blog (see a link in the question) worked for a short while during the last week. It has something more on installing and on copying the templates, which I had ready before I started the migration.
Tested in Django 1.6.
Upgrade to Django 1.7 is not finished, it needs more work...
- Badges
- Science topic
- Similar topics
- Computer Science and Engineering
- Programming Languages
- Python