Move all i18n calls to init action as per WP 6.7 #478
Conversation
This file contains 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
|
In WordPress 6.7 update, the non-English site is messed up. The plugin language file and themes do not run correctly. |
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.
See #477
Short introduction
Ticket #477
Remove warnings related to i18n in WordPress 6.7
Description of what the PR accomplishes
This PR removes the warnings for WordPress 6.7 in regards to calling i18n functions before
inithook.The problem is not only on the
load_plugin_textdomaincall but also in any call to a i18n function beforeinitaction.This commit moves the requires to
init. Manual tests were made using this hook level and no issues were found.