load_theme_textdomain() needs an absolute path to the directory, so you should set your THEME_URL like so define(“THEME_URL”, get_template_directory()); define(“TRANSLATION_URL”, THEME_URL . “/languages”); It wasn’t working for you because get_bloginfo(“template_url”) is an URL and not an absolute path on your server.
The text domain is a unique identifier, which makes sure WordPress can distinguish between all loaded translations so Using the basename of your plugin/theme is always a good choice because plugin/theme basename is always unique though it is not mandatory to have plugin/theme basename as text domain, you can use any unique identifier. If you’re … Read more
Your theme’s text domain is defined in your Theme Header in style.css. For example: /* * Plugin Name: My Plugin * Author: Otto * Text Domain: my-plugin */ The text domain should match your theme’s ‘slug’ (ie. the name of the folder where your theme is stored). Read more: https://codex.wordpress.org/I18n_for_WordPress_Developers#Text_Domains
Best way around it would probably be to manually call load_textdomain() on the corresponding MO file in your theme’s functions.php.
Themes should always have only one textdomain – most of the localization tools base on that assumption, so if you put multiple textdomains in the same theme, you make localizing it much harder. As for wordpress.org… It is clearly stated that: Themes that are hosted on WordPress.org the text domain must match the slug of … Read more
From https://developer.wordpress.org/themes/functionality/internationalization/ Themes that are hosted on WordPress.org the text domain must match the slug of your theme URL (wordpress.org/themes/). This is needed so that the translations from translate.wordpress.org work correctly. The text domain name must use dashes and not underscores and be lowercase. For example, if the theme’s name My Theme is defined in the style.css or it is … Read more
The default text domain is registered in wp_load.php before plugins are loaded. See the function wp_load_translations_early(). So when you register your action callback, the text domain has been loaded already. For an alternative way to list all registered text domains see this answer: List of Default Translated Phrases.
Yes, you can load multiple translation files for multiple text domains in one plugin. This is sometimes useful, for example when you need just one string in AJAX calls and many strings in the rest of the application: to make AJAX faster, load a separate translation. Be aware, automatic language updates for the plugin from … Read more
I think you just need to load the translations earlier to make them available for ajax hooks: add_action( ‘plugins_loaded’, ‘myplugin_load_textdomain’ ); function myplugin_load_textdomain() { load_plugin_textdomain( ‘myplugin’, false, basename( dirname( __FILE__ ) ) . ‘/languages’ ); }
Yes, Recent Tweets Widget is one of the many plugins which their translations are managed through translate.wordpress.org, and this means that upon installing the plugin (*remember, installing and activating are different), WordPress (on your site) will automatically download the plugin’s language pack (.po and .mo files) from translate.wordpress.org, and then store the translation files in … Read more