You need to use the internationalisation APIs, these let you swap out hardcoded strings for localised versions, e.g. <p>Hello world</p> versus: <p><?php _e( ‘Hello world’, ‘joes_plugin’ ); ?></p> Then, you can use .po/.mo/.pot files to provide alternatives, e.g. a file with french translations, a file with russian etc. You’ll need to declare your translation text … Read more
Depends of the setup, but in most cases this one was the best translation plugin I’ve used so far: Free Version: https://wordpress.org/plugins/translatepress-multilingual/ Premium Version: https://translatepress.com/
Solution provided in WPML forum.
I have English words in Kurdish pages
AFAIK there’s a one-to-one relationship between a WordPress installation and a theme – you can only have one theme per install. As you say site2 is ‘completely different’ then it probably makes sense to make it a completely separate WordPress installation. The only reason to think about something else would be if it shared a … Read more
As per Theme Handbook ⇒ Internationalization, you should call load_child_theme_textdomain() from within the after_setup_theme hook: function load_greattheme_textdomain() { load_child_theme_textdomain( ‘greattheme’, get_stylesheet_directory() . ‘/languages’ ); } add_action( ‘after_setup_theme’, ‘load_greattheme_textdomain’ ); Make sure you name your *.mo and *.po files properly (follow the link above).
You must change the WordPress permalink settings. Go to Settings>Permalink and chose “post name” and save then reload the Polylang settings and the options should be available. I have not tried it with other permalink settings, but it cannot be “plain” which is the default. It took me 2 hours to figure this out…
How to implement data residency in my WordPress site
I cant test my .po file for Turkish Language
Can non-latin characters appear in slugs?