It is not the first time that I encounter a problem on Wordpress, that when a plugin is inserted into a theme or another plugin, the language of such a plugin changes to English.

I add the plugin via include_once:

include_once(get_template_directory() . '/plugins/plugin_name/plugin_name.php');

There are no problems with such plugins, except for language change.

Who can faced it and will prompt the decision? Any crutch or idea is also useful.

    1 answer 1

    Naturally. Because you are crushing the WordPress translation system.

    How does she work? During initialization (each time the site is accessed), WordPress checks on its database which plugins it has activated, loads them and causes the action of plugins_loaded (in fact, there are a number of others, but it doesn’t matter now). A plugin should have its own hook for this action and call the function load_plugin_textdomain() in it, where the third parameter is the folder where the .mo translation files are located, usually the relative path from the folder of the plugin itself.

    What happens when you commit violence against WordPress is hard to say. If there are no plug-ins at all, then the action of plugins_loaded may not be called at all. If they are, then perhaps this action is invoked by WordPress before your include_once is executed. And if even later, and in the plugin the hook is triggered, then there may be problems with indicating the relative path to the translation files.

    In addition, when loading plugins, a number of other actions are performed that are practiced by hooks in plugins and most critically affect the functionality. And the loss of the translation system is only one of the possible problems. Only the most primitive plugins will work via include_once. Try this WooCommerce, for example, and see what happens.

    Many plugins perform a series of actions during activation / deactivation, installation and removal. For example, they create / delete their tables in the database or write their data to common tables. By chopping off this mechanism, you can easily get a broken WP database.

    And the most incomprehensible - that's what all this is for? For mythical performance? A properly configured WordPress server can handle up to 10,000 connections per second .

    In general, do not break the system, do everything as it should be - save a lot of time searching for the next jambs.