WP translation functions, are meant to translate static strings. E.g. Regarding options, you should use them to translate the labels, not values. However, as far I remember, the translation utility of WPML works in contrast to standard translation, i.e. if you use that than you can’t load the transaltion using from .po/.mo files. If users … Read more
When a user creates a new page/post/product on one site, use the XML-RPC API to create a matching one on the other site. Make sure to save the ID of the original post under a meta key for the “duplicate” post, and then use the response ID from the API to save the “duplicate” ID … Read more
This is fixed. I made a small script to get this working. Because it was a multi language site I just named the site’s to the language they should be in. So the English page is named English, German page is called German etc. Made a small php script to check what the page name … Read more
I’m not completely sure whether this is what you want, but if the option page is in one language you can simply put the gettext call in the custom field itself to avoid using variables. For the admin you force the translation to spanish: function wpse227983_force_language ( $locale ) { if ( is_admin() ) { … Read more
Plugins and themes pull the translation files manually from (mostly) their directory. There are 2 different functions which handle this: For plugins : load_plugin_textdomain() For themes: load_theme_textdomain() The syntax would be something like this, mostly hooked into init or plugins_loaded action hook: load_plugin_textdomain( ‘text-domain’, get_template_directory() . ‘/some-directory’ ); OR: load_plugin_textdomain( ‘text-domain’, false, basename(dirname(__FILE__)).’/some-directory’); Look for … Read more
The third parameter to load_plugin_textdomain function should only be the plugin name suffixed with the language folder. It does not need the absolute path to the language folder. For e.g. in my scenario, the correct parameter is: load_plugin_textdomain( ‘bgm’, false, basename(__DIR__) . ‘/languages/’);
You need to load_theme_textdomain() in your theme. Place this in theme functions file: function theme_init(){ load_theme_textdomain(‘theme_name’, get_template_directory() . ‘/languages’); } add_action (‘init’, ‘theme_init’); Then you put you language files in you theme /languages folder you language files should be es_ES.mo and es_ES.po without the text domain at the front as the codex states File names … Read more
You could check the contents of the $_SERVER[‘REQUEST_URI’] array when the site is loaded, by placing the conditional checking logic in your header.php file of your site and then redirect the user to the appropriate language from there. For example in header.php add: $incomingUrl = $_SERVER[‘REQUEST_URI’]; if($incomingUrl == ‘mydomain.dk’) { wp_redirect(URL FOR THIS LANGUAGE); exit; … Read more
Go to wp-admin/network/sites.php. Edit one site, and set a language for that blog: No do the same on a second site. There have to be two sites with an associated language. And then you get the relationship setting below on the same page after hitting F5 one time. This will be fixed in the next … Read more
You can filter mu_dropdown_languages and re-add American English here. Sample code, not tested: add_filter( ‘mu_dropdown_languages’, function( $output, $lang_files, $current ) { array_unshift( $output, ‘<option value=””‘ . selected( $current, ‘en_US’, false ) . ‘>’ . __( ‘American English’ ) . “</option>” ); return $output; }, 10, 3 ); Filter sanitize_option_WPLANG or pre_update_option_WPLANG to jump into the … Read more