Codeinwp / Codeinwp/otter-blocks
Unable to translate the About Us section of the plugin
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 198
- Forks
- 36
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 30
Description
Description
Unable to translate the About Us section of the plugin. I guess it's because of using wrong key "textdomain", you should use "otter-blocks".
Step-by-step reproduction instructions
- Open the About Us page.
Screenshots, screen recording, code snippet or Help Scout ticket
Plugin file with invalid key: otter-blocks\vendor\codeinwp\themeisle-sdk\src\Modules\About_us.php
Untranslated strings in the interface
Missing lines on translate.wordpress.org: https://translate.wordpress.org/projects/wp-plugins/otter-blocks/dev/ru/default/?filters%5Bterm%5D=About+Us&filters%5Bterm_scope%5D=scope_any&filters%5Bstatus%5D=current_or_waiting_or_fuzzy_or_untranslated_or_rejected_or_changesrequested_or_old&filters%5Buser_login%5D=&filter=Apply+Filters&sort%5Bby%5D=priority&sort%5Bhow%5D=desc
Environment info
No response
Is the issue you are reporting a regression
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in otter-blocks/vendor/codeinwp/themeisle-sdk/src/Modules/About_us.php and inspect the translation key used by the About Us strings. Reproduce by opening the About Us page, then compare the strings with the linked translate.wordpress.org project. Done means the strings appear for translation and translated text renders in the interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- localization
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100