Hardcode user model to avoid conflict with other kolibri usages #11531
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Migration
kolibri/core/device/migrations/0019_syncqueue_and_status.py
is using a setting variablesettings.AUTH_USER_MODEL
to refer tokolibri.core.auth.models.FacilityUser
.This is causing problem in other usages where
settings.AUTH_USER_MODEL
is a different modelThis PR uses the real model name to avoid problems
Reviewer guidance
Tested in KDP where
settings.AUTH_USER_MODEL
=kolibri_data_portal.PortalUser
do migrations run correctly?
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)