You need to use another action when in a mu-plugins. add_action(‘muplugins_loaded’, ‘myplugin_muload_textdomain’); plugins_loaded action work only after active plugins and pluggable functions are loaded. mu-plugins are not regular plugins and will not be loaded like them. As you can see in the following link, mu-plugins are loaded before anything else. Actions Run During a Typical … Read more
Try below code. echo get_the_date(__(‘M d’)); Output: Feb 09 echo get_the_date(__(‘M d, Y’)); Output: Feb 09, 2017
You don’t have to make anything special for WPML, using the regular translation code should be enough. See I18n for WordPress Developers in the Codex. Code preparation style.css Add Text Domain and Domain Path to your theme’s style.css. Example: /* * Theme Name: My awesome theme * Text Domain: my_awesome_theme * Domain Path: /languages */ … Read more
You can wrap it inside double quotes: esc_html_e(“I couldn’t find the page you are looking for.”, “themename”);
You are completely loading your language file wrong in your plugin, and your file naming is also wrong. load_theme_textdomain(‘my_plugin’, plugin_dir_path( __FILE__ ) . ‘/languages’); should be load_plugin_textdomain(‘my_plugin’, false, dirname(plugin_basename(__FILE__)) . ‘/lang/’); Also, your mo and po files should be named my_plugin-en_US.mo and my_plugin-en_US.po. Go have a look at this tutorial also, this will help you … Read more
Is it really need to escape translatable strings? Yes. If a string is translatable then that means its value can be changed from an external source. This means it’s not safe. and how shall i do that? See the documentation on how to escape with WordPress. When it comes to translatable strings, there are two … Read more
The easiest approach would be to have custom fields on the edit page: one text field for every language you want to use (and perhaps different title fields?) For this you could use a plugin like ACF. This would provide an easy interface for non-tech editors. Supposing you are building your own theme you can … Read more
I figured it out almost immediately after asking the question, after months of frustration. The issue was I was using the load_textdomain function (which was the way I learned it) instead of the apparently newer/favored load_plugin_textdomain. The working code looks like this function rsvpmaker_load_plugin_textdomain() { load_plugin_textdomain( ‘rsvpmaker’, FALSE, basename( dirname( __FILE__ ) ) . ‘/translations/’ … Read more
Anyway, I found my answer. I used qTranslate to translate menu wordings as well as widget titles. Free & useful.
(this kind of issues is part of why my standard recommendation is to not have front end with two languages) The core reason to the problem is that your ajax returns text. AJAX should be treated like API which provide machine level values which the front end translate to human text. When your code is … Read more