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 should leave the post type name (and everything else that might need to be translated) in English. Then, in WPML, you can translate its name (labels, and slugs). If the main language of the site is Danish, you simply set this language as default language (not for WPML String Translation though, where I would … 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
2 notes regarding your own answer: try to not access on super global variables directly, but using filter_input your code throw a notice if $_GET[‘lang’] is not set So your code can be improved: function toscho_change_language() { return ‘bn_BD’; } if ( filter_input( INPUT_GET, ‘lang’, FILTER_SANITIZE_STRING ) === ‘bn’ ) { add_filter( ‘locale’, ‘toscho_change_language’ ); … Read more
Can you try adding the following code to the functions.php file in your theme directory and see if works for you function keep_raw_filename( $filename, $filename_raw ) { return $filename_raw; } add_filter( ‘sanitize_file_name’, ‘keep_raw_filename’, 10, 2 );
Just so you know, a Sinhala translation is already in progress. https://si.wordpress.org/ http://wpcentral.io/internationalization/si/ Maybe it would be a good idea to join that team. First, you need to create .po files for the Sinhala translation of WordPress. You’re going to need four of these files. They will be called si_LK.po admin-si_LK.po admin-network-si_LK.po continents-cities-si_LK.po If all … Read more
There is no standard way to get this information across all multilingual plugins. Some plugin use taxonomies for translation relations, other custom tables, separates sites in a network or options. You shouldn’t have to worry about that. Just let the user use different shortcodes in each translation.
WordPress multisite can handle different top-level domains by default. Just set up a »Sub-Domain Install« multisite starting from your existent WordPress (example.no). Then, add a new site with an arbitrary subdoman (e.g. se.example.no). Right after you created the new site, got to the sites edit screen (edit site) and change the domain to what ever … Read more
If you need true localization, like a different checkout process, different themes or product descriptions, then you should use a multisite. You can activate plugins and themes per site here. The problem here is that almost all shopping plugins are not multisite compatible. You have to activate them per site, not as network plugin, or … Read more