[5.x] Fix term reference updates after slug change #11058
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.
Fix an issue where updating a term's slug through the control panel would not update the references to that term in existing entries, even though
system.update_references
is enabled.The root of the issue appears to be that the auto-bound Term instance in the CP controller lacks its original data because there is no initial
syncOriginal()
call. The first call tosyncOriginal
happens only after saving, which is not helpful here. I’m not sure why this doesn't also happen with Entries, but it seems to work there.The existing tests haven't caught this as it only happens in the CP controller, not when creating and updating terms in a test environment. Would love to contribute tests here as well, but that's a bit over my head how to test this reliably across the CP routes/controllers.
Closes #10938
Related: #11021