Skip to content

Loading .mo files for this plugin #560

@DAnn2012

Description

@DAnn2012

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 and pm_get_translations_for_plugin_domain 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions