I found the solution: In the constructor I had to add this public function __construct() { // your code goes here add_action( ‘plugins_loaded’, [$this, ‘load_text_domain’] ); // your code goes here } public function load_text_domain() : void { load_plugin_textdomain(‘your-plugin-textdomain’); } This finally made sure that the language displayed followed the settings of the user profile … Read more
What I now want to be able to do is set the locale for a function call of __(), to retrieve the translation you defined on your plugin’s .mo for a translation which is different from the current locale. I’d prefer my translations to be translated all in the same way, using the same logic … Read more
So i found my own mistake: I did not properly read https://developer.wordpress.org/plugins/internationalization/localization/#translate-the-po-file My .mo files were just called like en-US.mo. But they should be called my-plugin-en-US.mo. Solved!
Yes but it is not useful if you plan to bundle your language files with your plugin: https://developer.wordpress.org/reference/functions/load_plugin_textdomain/ If the path is not given then it will be the root of the plugin directory. So it will look in wp-content/plugins The third parameter is only used if you want to use a subfolder. Likewise, if … Read more
Only use the internal translations if you use the complete string without any addition. Grammar rules, writing directions etc may be different in your user’s language and your order may not match their needs. You example would be Taxonomiename or Name der Taxonomie in German. How should a translator handle this? So, use: <?php echo … Read more
Use the CS Localization plugin and generate the po/mo files, thats all. Save the file also in the repo of git and ready. The performance of the theme is not so high, if you have the strings inside the php-files, but only so it is possible to create different languages for the themes. mo/po files … Read more
_x() requires a context, either remove it completely or set it to something like ‘Recipe Singular’ and ‘Recipe Plural’. Docs: _x()
If your code, be it a theme or a plugin, does not support translation, then don’t use the translation functions. And if you don’t use these functions, you cannot use a text domain. 🙂 There is a very common error that looks like this: echo __( ‘Portfolio’ ); Portfolio is not part of WordPress’ core … Read more
I would say use a $_SESSION[‘var’] var or $_COOKIE[] to check if the link is clicked. Looks like the plugin is calling the geo_redirect_client_location function and then redirecting. function geo_redirect_client_location(){ $geo = new Geo_Redirect(); $geo->checkIfRedirectNeeded(); } I’m not familiar enough with the plugin but I would so something like: <a href=”https://wordpress.stackexchange.com/questions/89111/example-intenational-sitelink.com/?show_intl=true”>Link on US site to … Read more
This should cover everything: function wpa_rewite_translate(){ global $wp_rewrite; $wp_rewrite->pagination_base=”pagina”; $wp_rewrite->author_base=”autor”; $wp_rewrite->comments_base=”comentarios”; $wp_rewrite->feed_base=”alimentar”; $wp_rewrite->search_base=”busqueda”; $wp_rewrite->set_category_base( ‘categoria/’ ); $wp_rewrite->set_tag_base( ‘etiqueta/’ ); } add_action( ‘init’, ‘wpa_rewite_translate’ ); Feel free to laugh at my translations, haha. Also, to flush rewrite rules when your theme is activated, add this: function wpa_flush_rewite(){ flush_rewrite_rules(); } add_action( ‘after_switch_theme’, ‘wpa_flush_rewite’ );