Fixed localization issues - #37
Open
kevinmeijer97 wants to merge 1 commit into
Open
Conversation
danielsmink
approved these changes
Aug 20, 2026
BobWez98
approved these changes
Aug 21, 2026
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
3 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.
Fixes structured data resolving the wrong localization. The
StructuredDataPreviewfieldtype now passes the active site handle from the publish context, andgetTemplates()uses it to set the current site and resolve terms via$term->in($site). PreviouslyTerm::find()returned an arbitrary localization, so a Dutch term could render Portuguese output. Raw->get()calls in the controller, service, and builder were also replaced with augmented property access so values follow Statamic's localization cascade.