Skip to content

Conversation

@alexclassroom
Copy link
Contributor

Description of the Change

If strings in your plugin are also used in WordPress core (e.g., ‘Settings’), you should still add your own text domain. Otherwise, they’ll become untranslated if the core string changes (which happens). Please refer to this official article.

Closes #

How to test the Change

Add the necessary text domain, and replace previous version files, the UI strings with the missing text domain will be applied the translations from language pack (NOT from Core)

Changelog Entry

Added - The missing Text Domain

Credits

Props @alexclassroom

Checklist:

  • [ x ] I agree to follow this project's Code of Conduct.
  • [ x ] I have updated the documentation accordingly.
  • [ x ] I have added tests to cover my change.
  • [ x ] All new and existing tests pass.

If strings in your plugin are also used in WordPress core (e.g., **‘Settings’**), you should still add your own text domain. Otherwise, they’ll become untranslated if the core string changes (which happens). Please refer to [this official article](https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/#add-text-domain-to-strings).
@jeffpaul jeffpaul added this to the 2.7.1 milestone Apr 10, 2024
@dkotter dkotter merged commit a9ade82 into 10up:develop Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants