Rely on just-in-time translation loading #608
Merged
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?
Removes the manual
load_plugin_textdomain()
call to rely on WordPress to load translations at the right time.Bumps the requirement to WordPress 4.6 accordingly.
Also, defines the
Requires *
headers in the main plugin file so that WordPress can actually read them and prevent you from installing the plugin if requirements are not met.The headers mustn't really be set in the readme.
Why?
The plugin was loading translations too early on
plugins_loaded
. Plugins should wait untilinit
to ensure the current user has been set up, so that the current user's locale can be respected.That said, why manually load translations when WordPress can do it for you :-)
How?
Testing Instructions
Switch to a different language and see that the translations are still loaded as expected.
Screenshots or screencast
Changelog Entry