Title: Plugin translation
Last modified: May 27, 2021

---

# Plugin translation

 *  [prccp](https://wordpress.org/support/users/prccp/)
 * (@prccp)
 * [5 years ago](https://wordpress.org/support/topic/plugin-translation-103/)
 * I’ve created the proper .mo and .po files usind POEdit, put them in the **\wp-
   content\languages\plugins** folder but it doesn’t work.
    Seems like the plugin
   still gets all of it’s strings from the **\wp-content\plugins\accordion-blocks\
   build\index.js** file, since changing that file works.
 * Am I doing something wrong or is the translation not working yet?
 * Thanks in advance for your great plugin and support!
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fplugin-translation-103%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Plugin Author [philbuchanan](https://wordpress.org/support/users/philbuchanan/)
 * (@philbuchanan)
 * [5 years ago](https://wordpress.org/support/topic/plugin-translation-103/#post-14491728)
 * Honestly, I know very little about how the whole translation thing works. 😬 
   I do know that I am using the appropriate translation functions (`__()`, `_e()`,
   etc).
 * I think you can become an editor for the project and [add translations through WordPress.org](https://translate.wordpress.org/projects/wp-plugins/accordion-blocks/).
   That will make the translations available to everyone. Alternatively, I think
   I can ship custom translation files (a .mo and .po file) with the plugin itself.
   I’m just not sure how to to go about adding your own translations to an existing
   plugin.
 *  Thread Starter [prccp](https://wordpress.org/support/users/prccp/)
 * (@prccp)
 * [5 years ago](https://wordpress.org/support/topic/plugin-translation-103/#post-14492127)
 * Thanks for suggestions! I became part of the translation community a few months
   ago after reading all the documentation and guidelines (mainly because of this
   plugin).
 * And although I haven’t publicly updated the translation entries for the last 
   few versions (I intend to soon), I have a full translated file in my project.
 * I’ve spent some time today checking everything and so far I found that the language
   entries for the file “**accordion-blocks.php**” work fine.
    The problem seems
   to be all the other entries for files such as “**../src/block/edit.js**“, that
   as far as I know doesn’t exist. Instead all of those entries should point to “**
   build\index.js**“. But I’m not sure that file is getting the texts from the language
   files.
 * Let me know what you can find and if you need any help I can give.
 * Thanks again for your time!
 *  Plugin Author [philbuchanan](https://wordpress.org/support/users/philbuchanan/)
 * (@philbuchanan)
 * [5 years ago](https://wordpress.org/support/topic/plugin-translation-103/#post-14492210)
 * Interesting. That certainly give me somewhere to start looking. Give me a day
   or two to do some digging.
 *  Plugin Author [philbuchanan](https://wordpress.org/support/users/philbuchanan/)
 * (@philbuchanan)
 * [5 years ago](https://wordpress.org/support/topic/plugin-translation-103/#post-14512390)
 * Hi [@prccp](https://wordpress.org/support/users/prccp/),
 * I may have figured out the issue. Can you [try this development version of the plugin](https://github.com/philbuchanan/Accordion-Blocks/archive/refs/heads/%23139.zip)
   and let me know if the translations work in the JS file?
 *  Thread Starter [prccp](https://wordpress.org/support/users/prccp/)
 * (@prccp)
 * [5 years ago](https://wordpress.org/support/topic/plugin-translation-103/#post-14513774)
 * Thanks, Phil!
 * Tomorrow is a national holiday here in Brazil and I won’t haven able to do it,
   but I’ll definitely take a look on friday.
 *  Thread Starter [prccp](https://wordpress.org/support/users/prccp/)
 * (@prccp)
 * [5 years ago](https://wordpress.org/support/topic/plugin-translation-103/#post-14520856)
 * [@philbuchanan](https://wordpress.org/support/users/philbuchanan/), I gave it
   a shot, but it didn’t work.
 * Since this beta version didn’t come with a translation file (I think WordPress
   generates those automatically) I used the file from the last version (with the
   translation file from previous version (1.3.5).
 * Editing strings in “\wp-content\plugins\accordion-blocks\build\index.js” worked,
   so I dont’t know if that file is not translated or the translation file references
   are outdated.
 *  Plugin Author [philbuchanan](https://wordpress.org/support/users/philbuchanan/)
 * (@philbuchanan)
 * [5 years ago](https://wordpress.org/support/topic/plugin-translation-103/#post-14521398)
 * Well that is unfortunate.
 * I’ve tried creating the file manually using Poedit. But it refuses to find the
   strings from the build version of the JS file (i.e. `/build/index.js`). It will
   only grab them from the source (i.e. `/src/`), which doesn’t ship with the plugin(
   since that code is never executed). I’ve tried everything I can think of, but
   nothing seems to work.
 * I’m not sure what the next move is.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Plugin translation’ is closed to new replies.

 * ![](https://ps.w.org/accordion-blocks/assets/icon-256x256.png?rev=2198298)
 * [Accordion Blocks](https://wordpress.org/plugins/accordion-blocks/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/accordion-blocks/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/accordion-blocks/)
 * [Active Topics](https://wordpress.org/support/plugin/accordion-blocks/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/accordion-blocks/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/accordion-blocks/reviews/)

## Tags

 * [language](https://wordpress.org/support/topic-tag/language/)

 * 7 replies
 * 2 participants
 * Last reply from: [philbuchanan](https://wordpress.org/support/users/philbuchanan/)
 * Last activity: [5 years ago](https://wordpress.org/support/topic/plugin-translation-103/#post-14521398)
 * Status: not resolved