Fix warning triggered in WordPress 6.7 and newer due to translation functions being called too early in the plugin lifecycle. Thanks to @alessandrocarrera for the report and @richaber for additional context.#549
Merged
jonathanstegall merged 4 commits intomasterfrom Aug 3, 2025
Merged
Conversation
…hod doesn't need to be a class attribute; it can just run a get function
…roperties after init runs
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
1 participant
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.
What does this Pull Request do?
This should fix #548, in which WordPress versions after 6.7.0 show a notice about translation being triggered too early. This makes very minor changes, which should not affect the tasks that the plugin needs to run early, while still preventing translations from being triggered before they should be.
How do I test this Pull Request?