Title: Loading .mo files for this plugin
Last modified: November 13, 2025

---

# Loading .mo files for this plugin

 *  Resolved [itapress](https://wordpress.org/support/users/itapress/)
 * (@itapress)
 * [7 months ago](https://wordpress.org/support/topic/loading-mo-files-for-this-plugin/)
 * Hello.
 * I’m doing some tests regarding loading your plugin’s .mo files.
 * I noticed that when translating strings contained in **.php files**, the plugin
   loads the .mo file contained in the system path (`wp-content/languages/plugins/
   wedevs-project-manager-xx_XX.mo`) and, if it doesn’t find it, it loads the .mo
   file contained in the developer path (`wp-content/plugins/wedevs-project-manager/
   languages/wedevs-project-manager-xx_XX.mo`).
 * Instead, regarding the translation of strings contained in **.js files**, which
   are handled by [pm_get_jed_locale_data](https://github.com/weDevsOfficial/wp-project-manager/blob/98ff7de5d23e62ba9547252ac6d2bae012694f6c/libs/functions.php#L610)
   and [pm_get_translations_for_plugin_domain](https://github.com/weDevsOfficial/wp-project-manager/blob/98ff7de5d23e62ba9547252ac6d2bae012694f6c/libs/functions.php#L575)
   functions, the plugin uses only the .mo file contained in the developer path (`
   wp-content/plugins/wedevs-project-manager/languages/wedevs-project-manager-xx_XX.
   mo`) and completely ignores the .mo file contained in the system path (`wp-content/
   languages/plugins/wedevs-project-manager-xx_XX.mo`).
 * Couldn’t we use a procedure that is more compliant with the standards and other
   WordPress plugins?
 * Thanks.

Viewing 1 replies (of 1 total)

 *  [Md. Tanvir Chowdhury](https://wordpress.org/support/users/tanvir101/)
 * (@tanvir101)
 * [6 months, 1 week ago](https://wordpress.org/support/topic/loading-mo-files-for-this-plugin/#post-18740306)
 * Hello [@itapress](https://wordpress.org/support/users/itapress/),
   Thank you for
   the detailed report. You are correct in your findings.At the moment, PHP translations
   follow the WordPress standard and correctly load from the global languages directory
   before falling back to the plugin’s own _**languages/**_ folder. However, JS 
   translations currently load only from the plugin path, which prevents WordPress
   from using the global _**.mo/.json**_ files or language packs.We agree that this
   should be aligned with WordPress standards. We are reviewing the JS translation
   logic, and if this behavior is confirmed as the recommended standard, we will
   implement the necessary changes to ensure both PHP and JS translations follow
   the same loading order.We appreciate your cooperation in this regard.

Viewing 1 replies (of 1 total)

The topic ‘Loading .mo files for this plugin’ is closed to new replies.

 * ![](https://ps.w.org/wedevs-project-manager/assets/icon-256x256.gif?rev=3386164)
 * [Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker](https://wordpress.org/plugins/wedevs-project-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wedevs-project-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wedevs-project-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/wedevs-project-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wedevs-project-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wedevs-project-manager/reviews/)

## Tags

 * [Localization](https://wordpress.org/support/topic-tag/localization/)
 * [strings](https://wordpress.org/support/topic-tag/strings/)

 * 1 reply
 * 2 participants
 * Last reply from: [Md. Tanvir Chowdhury](https://wordpress.org/support/users/tanvir101/)
 * Last activity: [6 months, 1 week ago](https://wordpress.org/support/topic/loading-mo-files-for-this-plugin/#post-18740306)
 * Status: resolved