Repository navigation
fix(migrations): skip deleted-site content - #293
Merged
engram-design merged 1 commit intoNov 4, 2026
Merged
engram-design merged 1 commit into
engram-design merged 1 commit into
Conversation
Member
|
Thanks @boboldehampsink ! |
This file contains hidden or 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
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.
Hyper's upgrade scans can encounter retained
elements_sitesrows for a soft-deleted site. Craft rejects that site ID before loading the element, so relation reconciliation aborts withUnable to resolve Hyper relation ownereven when the element record is intact.Exclude unavailable site contexts during relation reconciliation, using Craft's site lookup with disabled sites included. Apply the same deleted-site exclusion to legacy content relation scans on their configured database connection. Stored content is preserved and ordinary content modifications retain their strict owner validation.
The regression cases cover both migration entry points, deleted and disabled sites, current and legacy storage, dry-run behavior and unchanged content.