Repository navigation
[6.x] Cache term augmentation with taxonomy-qualified ID - #15974
Merged
jasonvarga merged 3 commits intoNov 19, 2026
Merged
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
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.
When using a single-taxonomy field in a blueprint, the augmented value is cached based purely on the slug, since the taxonomy is left out of the value in these cases.
If two of these fields exist and each cover different taxonomies but happen to have the same slug across them, the second augmentation will read the value of first augmentation, causing a term from a different taxonomy to be read.
This can break whatever is being shown quite badly (I have ran into this issue on a Statamic project myself).
With this change, the taxonomy-qualified IDs will be used in the cache key to ensure it will only cache values from within the taxonomy that the terms are from.