No matter what languages your site are in, when using WPML you should never install a localised WordPress version, instead you should just install the default one (i.e. US English). Also make sure that you didn’t change the LANG definition in your wp-config.php file, so that should read: define (‘WPLANG’, ”); Then you need to … Read more
You should always use the wpml functions as following: (the HowTo linked by you actually suggests this 🙂 if( function_exists(‘icl_register_string’) ) { icl_register_string( ‘Match Previous Order’ , ‘match_order’, ‘Do you want these items to match a previous order from Direct Linen? If yes, use “Additional Notes” to explain.’ ); } This will ensure that you … Read more
It all depends a bit if your current theme already supports localization. Does your theme’s function file contain something like this? load_theme_textdomain( ‘twentytwelve’, get_template_directory() . ‘/languages’ ); If not, add it in there. And change twentytwelve to your theme-directory-name. After that create a directory called languages in the root of your theme a drop your … Read more
Translation files must be named {locale}.po (e.g. en_US.po in order to be recognized. Rename your language translation file accordingly. See more in the Codex: i18n for developers.
Technically, this is possible. Just make sure to use your strings after the parent plugin has loaded its language file. In terms of maintainability, this is not optimal. Your create a very strond dependency here: each time the parent plugin changes a string (adding a dot, removing a white space), you have to change your … Read more
Check the wp-config.php file and see if your language is defined : define(‘WPLANG’, ‘your_language’); You could add this if you’re still stuck: add_action(‘after_setup_theme’,’wpse_110727_translate_theme’); function wpse_110727_translate_theme() { load_theme_textdomain( ‘textdomain’, get_template_directory() . ‘/languages’ ); $locale = get_locale(); $locale_file = get_template_directory() . “/languages/$locale.php”; if ( is_readable( $locale_file ) ) require_once( $locale_file ); } Just put the translation files … Read more
If you’re simply using one language on your site: Find the utility.php file in your themes folder with location lib/functions/utility.php Next find the lines 227 and 231 and change the __( ‘Previous Post’, ‘contango’ ) and __( ‘Next Post’, ‘contango’ ) to your desired values. For example: previous_post_link( ‘%link’, __( ‘vorige post’, ‘contango’ ) . … Read more
A translatable WordPress theme is a good way to interact with the audience with the language you desire it to present itself. There are many resources available over the Internet, and most of them worked actually. I don’t know why you find them not working for you. Anyways, I found the following tutorial nicely explained … Read more
You can filter locale for admin pages only: is_admin() && add_filter( ‘locale’, function() { return ‘en_US’; });
Use WordPress i18n functions. Normally good plugins are translation-ready, and you should create your translation files for that plugins (if not already present). Explain how to is too much for this answer, start looking at Codex page linked above, search Google and also have a look here. If a plugin is not translation-ready use another … Read more