Hyperkitty migrations fail when using custom User model
Working on project for a client where we have a custom user model. Some of hyperkitty's older migrations assume that auth.User
is the current user model. Specifically migrations 0007
and 0009
.
I would suggest switching to using get_user_model()
or perhaps just issuing a warning that the database might be out of sync related to these migrations.