You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documented CMS_MIGRATION_USER_ID doesn't seem to be in use at the moment. My guess is that it's intended for use in helpers.get_or_create_migration_user, which doesn't currently work with User models that are missing the username field?
Rather than implementing it by user ID, would it be worth having a dict-based setting which can be passed to get_or_create, so for example if my user model has an email-based login, I could set CMS_MIGRATION_USER={"email": "[email protected]"}
The text was updated successfully, but these errors were encountered:
The documented
CMS_MIGRATION_USER_ID
doesn't seem to be in use at the moment. My guess is that it's intended for use inhelpers.get_or_create_migration_user
, which doesn't currently work with User models that are missing theusername
field?Rather than implementing it by user ID, would it be worth having a dict-based setting which can be passed to
get_or_create
, so for example if my user model has an email-based login, I could setCMS_MIGRATION_USER={"email": "[email protected]"}
The text was updated successfully, but these errors were encountered: