[5.x] Account for custom fields when checking if entry URIs should be updated#13859
Merged
jasonvarga merged 2 commits into5.xfrom Feb 10, 2026
Merged
[5.x] Account for custom fields when checking if entry URIs should be updated#13859jasonvarga merged 2 commits into5.xfrom
jasonvarga merged 2 commits into5.xfrom
Conversation
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
2 participants
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.
Currently, we only update child & mounted entry URIs when the
slugfield changes.However, this means that updating a custom field used in the collection's route will leave child/mounted entries with the "old" URI until either the Stache is cleared or the slug is updated.
This PR ensures that we check the dirty state of fields used in the collection route by taking advantage of the
Antlers::identifiers()method.Closes #13828