Title: Make plugin translatable &#8211; not working
Last modified: April 18, 2018

---

# Make plugin translatable – not working

 *  Resolved [Flint](https://wordpress.org/support/users/flintstoned/)
 * (@flintstoned)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/make-plugin-translatable-not-working/)
 * Dear community,
 * I’m struggling with adding the ability to translate my plugin.
    I’ve added ‘Requires
   at least: 4.6’ in the readme file and used for my echo `echo __('my text', 'my-
   text-domain-same-as-plugin-slug');`
 * Also inside this PHP I’ve added Text Domain: my-text-domain-same-as-plugin-slug.
 * When visiting the plugin link, I can translate the read-me file but can’t translate
   the string in the PHP file.
 * While checking the slack channel, it says it’s all imported.
 * Any ideas?
 * Kind regards,

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

 *  [helldog2018](https://wordpress.org/support/users/helldog2018/)
 * (@helldog2018)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/make-plugin-translatable-not-working/#post-10194450)
 * Hi [@flintstoned](https://wordpress.org/support/users/flintstoned/),
 * Did you also added the header to the plug-in?
 *     ```
       /*
        * Plugin Name: My Plugin
        * Author: Plugin Author
        * Text Domain: my-plugin
        * Domain Path: /languages
        */
       ```
   
 * Make sure the Text Domain: is same as slug (I believe in this case ‘my-text-domain-
   same-as-plugin-slug’)
 * Also the Domain Path: is where the .mo and .po files are placed.
    Read [HERE](https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/)
   for more information.
 *  Thread Starter [Flint](https://wordpress.org/support/users/flintstoned/)
 * (@flintstoned)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/make-plugin-translatable-not-working/#post-10194483)
 * Hi [@helldog2018](https://wordpress.org/support/users/helldog2018/),
 * Thank you for your reply.
 * In the documentation I’ve read the following:
 * > After WordPress 4.6 came out, translations now take translate.wordpress.org
   > as priority and so plugins that are translated via translate.wordpress.org 
   > do not necessary require load_plugin_textdomain() anymore.
   >  If you don’t want
   > to add a load_plugin_textdomain() call to your plugin you have to set the Requires
   > at least: field in your readme.txt to 4.6.
 * I understand from this, that if I add the ‘Requires at least: 4.6’ in the readme
   file, I don’t need the load_plugin_textdomain(). So my guess was that I don’t
   need a directory ‘language’ and a .mo file, or am I completely wrong and I still
   need a .mo file etc?
 * Kind regards,
    -  This reply was modified 8 years, 1 month ago by [Flint](https://wordpress.org/support/users/flintstoned/).
 *  [helldog2018](https://wordpress.org/support/users/helldog2018/)
 * (@helldog2018)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/make-plugin-translatable-not-working/#post-10194580)
 * Hi [@flintstoned](https://wordpress.org/support/users/flintstoned/),
 * I believe that hosting your translation via translate.wordpress.org your plugin
   must also be contributed via wp.org (I think if you are still developing the 
   plug-in it is not being contributed yet).
 * [HERE](https://wpgeodirectory.com/loading-wordpress-language-files-correctly/)
   is a tutorial on how to start creating your own internationalization for themes
   and plugins and how to eventually use the translate page of wordpress.
 * Cheers.
 *  Thread Starter [Flint](https://wordpress.org/support/users/flintstoned/)
 * (@flintstoned)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/make-plugin-translatable-not-working/#post-10197036)
 * Hi [@helldog2018](https://wordpress.org/support/users/helldog2018/)
 * Alright! Thank you kindly for your guidance ;-).
 * I’ll use PoEdit to make the files and follow [this](https://sellingplugins.com/create-translation-files-using-poedit-free/)
   tutorial so I don’t need the Pro version to create po/mo files.
 * Thanks!
 * Kind regards,

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

The topic ‘Make plugin translatable – not working’ is closed to new replies.

 * In: [Developing with WordPress](https://wordpress.org/support/forum/wp-advanced/)
 * 4 replies
 * 2 participants
 * Last reply from: [Flint](https://wordpress.org/support/users/flintstoned/)
 * Last activity: [8 years, 1 month ago](https://wordpress.org/support/topic/make-plugin-translatable-not-working/#post-10197036)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
