Collection fix via data migration #6721
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pomax
suggested changes
May 19, 2021
network-api/networkapi/wagtailpages/migrations/0008_collection_fix.py
Outdated
Show resolved
Hide resolved
Pomax
reviewed
May 19, 2021
|
|
||
| # Let's confirm root is ID #1, as it should be just to be safe. | ||
| if root.id != 1: | ||
| print("Incorrect root Collection ID. Stopping this script to prevent any mistakes") |
Pomax
approved these changes
May 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #6720
Related PRs/issues #6702
Note: This migration needs to be run in production before #6702 can be applied. #6702 will fail if the watail migrations are run before the migration in this PR.
Steps to test:
inv manage clean_collectionsAll migrations should run. And if you go to http://localhost:8000/cms/collections/ you should see our collections show up the way they're supposed to.
Let's also double check that the Collections that end up being deleted in the 0008 migration are the in fact factory collections, and not actually being used. As far as I was able to tell today, this is wiping out unused collections from staging's database.