fix(cms): restore hub bindings lost in PR 65 merge resolution#66
Merged
Conversation
The 'Merge branch main' conflict resolution in PR #65 resurrected the field-level undraw bindings that commit 6385fd1 had reverted, shipping the exact configuration we'd established locks the bank away: scoped to five fields, excluded from Global Assets, unreachable from news. That, not Sveltia behavior, was why searching "undraw" found nothing on the deployed admin. Restore admin/config.yml and the maintainer-notes bullet to the branch tip's state: illustration fields upload to /assets/images/hub again, and the bank is reachable via the global pool today and becomes its own picker-wide folder via asset_collections once the next Sveltia release ships. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
The 'Merge branch main' conflict resolution in PR #65 resurrected the field-level undraw bindings that commit 6385fd1 had reverted, shipping the exact configuration we'd established locks the bank away: scoped to five fields, excluded from Global Assets, unreachable from news. That, not Sveltia behavior, was why searching "undraw" found nothing on the deployed admin.
Restore admin/config.yml and the maintainer-notes bullet to the branch tip's state: illustration fields upload to /assets/images/hub again, and the bank is reachable via the global pool today and becomes its own picker-wide folder via asset_collections once the next Sveltia release ships.