Closed mkao006 closed 8 years ago
This problem is resolved when the name in
MIGRATION_MODULES = {
'sites': 'contrib.sites.migrations'
}
is corrected with the random_walker
prefix removed. This is because we don't have the same directory structure.
However, now we have a new issue:
ImportError: No module named users.adapters
In addition, it is not clear whether we should use the module users
or the users.apps.UsersConfig
specified in the settings of the cookiecutter.
Moreover, we need to investigate why the random_walker
is not restarted when it fails and also why the build does not refresh.
The issue is fixed by removing the random_walker
prefix from the settings.ACCOUNT_ADAPTER
and settings.SOCIALACCOUNT_ADAPTER
. The user signup and login page now functions at c88c05f8a126e35b33f9c6a6feb9d356623a09bd.
When trying to implement the User model in the
django-cookiecutter
we encounter the following migration problem.