Title: Created wrong name
Last modified: August 30, 2016

---

# Created wrong name

 *  Resolved [perteus](https://wordpress.org/support/users/perteus/)
 * (@perteus)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/created-wrong-name/)
 * plugin created wrong name. etc
    Yet another stars raitings have localization 
   files yasr.po yasr.mo but plugin created yet-another-stars-raitings-cs_CZ.mo/
   po and translate not work. I must rename files.
 * [https://wordpress.org/plugins/loco-translate/](https://wordpress.org/plugins/loco-translate/)

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

 *  Plugin Author [Tim W](https://wordpress.org/support/users/timwhitlock/)
 * (@timwhitlock)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/created-wrong-name/#post-6508756)
 * To be compatible, the plugin must declare its text domain is `yasr` in the [Text Domain header tag](https://codex.wordpress.org/File_Header#Plugin).
 * By default Loco will take either the name of the plugin or the name of the POT
   file. If the author adds this declaration Loco will know what the files should
   be called.
 *  [snaidero](https://wordpress.org/support/users/snaidero/)
 * (@snaidero)
 * [10 years ago](https://wordpress.org/support/topic/created-wrong-name/#post-6509024)
 * Is there a way Loco can choose which name to use? I have the same problem with
   several plugins of which new translations Loco misnames (I know it’s probably
   the plugins authors’ fault), but if so they’re quite a few.
 * A feature in admin or in the list (or in some step of the process) where Loco
   could offer a dropdown select choice of what [possible] names to use would be
   an exceptional user experience addition. It would make life SO much easier for
   users since it seems to be a common mistake by many developers.
 * Otherwise I’m left dangling in renaming constantly, in between my browser and
   SFTP client. Please consider it, that or maybe there’s a better solution aside
   from contacting every developer :).
 * Great plugin btw!
 * – SRS
 *  Plugin Author [Tim W](https://wordpress.org/support/users/timwhitlock/)
 * (@timwhitlock)
 * [10 years ago](https://wordpress.org/support/topic/created-wrong-name/#post-6509025)
 * The plugin is being completely rebuilt to address this issue:
    [https://wordpress.org/support/topic/new-version-will-address-all-reported-issues](https://wordpress.org/support/topic/new-version-will-address-all-reported-issues)
 * Version 1.x has no way to alter the names used, but if you’re a coder you can
   use WordPress filters to solve your problem at load time: see [load_textdomain_mofile](https://developer.wordpress.org/reference/hooks/load_textdomain_mofile/).
 *  Plugin Author [Tim W](https://wordpress.org/support/users/timwhitlock/)
 * (@timwhitlock)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/created-wrong-name/#post-6509030)
 * version 2.0 is available for beta testing and provides configuration options 
   to control file naming in unconventional setups.
    [https://localise.biz/help/wordpress/translate-plugin/developers](https://localise.biz/help/wordpress/translate-plugin/developers)
 * If you have issues with v2.0, please open a new thread. Thanks.

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

The topic ‘Created wrong name’ is closed to new replies.

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

 * 4 replies
 * 3 participants
 * Last reply from: [Tim W](https://wordpress.org/support/users/timwhitlock/)
 * Last activity: [9 years, 10 months ago](https://wordpress.org/support/topic/created-wrong-name/#post-6509030)
 * Status: resolved