I think you just need to load the translations earlier to make them available for ajax hooks: add_action( ‘plugins_loaded’, ‘myplugin_load_textdomain’ ); function myplugin_load_textdomain() { load_plugin_textdomain( ‘myplugin’, false, basename( dirname( __FILE__ ) ) . ‘/languages’ ); }
I thought (and hoped) that the translations were written in the folder wp-content/languages/loco/plugins/my-plugin. They are, but only when you create the file in that location. Any users wishing to customize your provided translations should create a new translations file and not edit yours. Opening your provided PO file and starting to edit will not automatically … Read more
i had a similar question posted some time ago: why is translation not working on theme? it might be the solution to put your translation files into the right location (languages directory in wp-content/languages/themes/) and prefix them with the theme name like themename-pt_PT.po
You can use WordPress hooks to load site-specific files, but it requires some work. In this example, we’ll keep a common Dutch language file at a system location. This can contain any strings that work for both sites. Then we’ll override the common strings in two files using the site ID. So we have three … Read more
I can’t comment so I’ll answer and slightly adjust Bhagyashree’s which is exactly what you’ll need to do based on your question. Except you may want to know how to include the 2 pages rather than duplicating the function. And also passing in an array of strings to replace. function replace_some_text( $content ) { // … Read more
If you have PHP’s Intl extension installed, you can use the wonderful Transliterator class. I get some pretty good results, like this: $t = Transliterator::create(‘Latin-Greek’, Transliterator::FORWARD ); var_dump( [ ‘alfa’ => $t->transliterate(‘alfa’), ‘alpha’ => $t->transliterate(‘alpha’), ] ); Both these greeklish forms give me “άλφα”. I don’t know how it knows where to put the accent, … Read more
Found a solution that works for me: add_action( ‘after_setup_theme’, ‘avia_lang_setup’ ); function avia_lang_setup() { $lang = apply_filters(‘parent-theme-slug’, get_template_directory() . ‘/lang’); load_theme_textdomain(‘avia_framework’, $lang); load_child_theme_textdomain( ‘child-theme-text-domain’, get_stylesheet_directory() . ‘/lang’ ); } Note: Exchange “parent-theme-slug” (typically the parent theme name in small letters) and “child-theme-text-domain” (child theme text domain of your choice)
And I’m wondering if I have to translate the array too if I want to make my plugin fully translatable. It wouldn’t be fully translatable if you didn’t, would it? So yes, you need to make these translatable for that to be true. In that case, it’s a good idea to use the new wp-i18n … Read more
The _x() function is meant to be used with the same string/text which has two or more different meanings/contexts, e.g. “read” can be a verb (I can read music.) or noun (It’s a good read.). And when you use _x(), the context is the second parameter and the text domain is the third parameter, but … Read more
For anyone having the same trouble, I am now using a workaround from the accepted answer on the following question: https://wordpress.stackexchange.com/a/30723/181214 I am using the solution beyond the “EDIT: Another Option” which is working fine for slugs, names, singular names etc. function get_labels() { // return a default slug if(!defined(‘WPLANG’) || !WPLANG || ‘de_DE’ == … Read more