Add migration to fix urls on TranslationContext
model
#12075
Merged
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.
Description
Fixes cases where editors couldn't edit translations because
wagtail-localize
was trying to getURL
onlinkbutton
blocks, which doesn't exist anymore.The remnants were found on the
TranslationContext
model, which saves the field's path onfield
andfield_path
. Because this had explicit references toURL
that weren't migrated, it caused theKeyError
.Link to sample test page: http://localhost:8000/cms/pages/27553/edit/
Related PRs/issues:
Checklist
Tests
Changes in Models:
Documentation:
Merge Method
💡❗Remember to use squash merge when merging non-feature branches into
main
┆Issue is synchronized with this Jira Story