I’ll speak for qTranslate, I’ve used it a few times and been pretty happy with it. What it sets out to do – letting you offer translations of post content in multiple languages and switch between them – it does pretty well. It gets a bit dicey when you try to extend it beyond alternate … Read more
That plugin loads its language the moment its main file is included: load_plugin_textdomain( ‘wordpress-seo’, false, dirname( plugin_basename( __FILE__ ) ) . ‘/languages’ ); So when your locale filter is used, the language is already there. :/ Move your small plugin into the mu-plugins directory. You can create it if it doesn’t exists in wp-content. That … Read more
Should be put to the translation function. <?php comment_form(array (‘title_reply’ => __(‘Leave a comment’, ‘mytextdomain’))); ?> Or use WordPress translation: <?php comment_form(array (‘title_reply’ => __(‘Leave a comment’))); ?>
I have my own implementation of twig in WordPress as plugin and my translations are working. You can check my code. Keep in mind couple of things when when you will test the code: be sure that your WordPress have set locale which you want translate to be sure that you your mo file is … Read more
There are already an en_US.po file in the theme you are using. You can simply make a copy of that file and rename it as pl_PL.po. You can now open the pl_PL.po template with poedit, do all your translations in there, and just save it. Poedit will automatically create a pl_PL.mo template. No need to … Read more
if the translation is only for the archive widget, a filter function might work (to be added to functions.php of the theme): add_filter(‘get_archives_link’, ‘translate_archive_month’); function translate_archive_month($list) { $patterns = array( ‘/January/’, ‘/February/’, ‘/March/’, ‘/April/’, ‘/May/’, ‘/June/’, ‘/July/’, ‘/August/’, ‘/September/’, ‘/October/’, ‘/November/’, ‘/December/’ ); $replacements = array( ‘jan’, ‘feb’, ‘mar’, ‘apr’, ‘may’, ‘jun’, ‘jul’, ‘aug’, ‘sep’, … Read more
Well, it says you are not including text domain… well – because you are not including text domain. Obviously to fix it – you should include text domain. See I18n for theme and plugin developers in Codex. There is no point in adding extra code just to fake testing results. If you don’t need that … Read more
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
I think I found a solution, but before a little Premise load_theme_textdomain() and load_child_theme_textdomain() are basically equal, the only difference is the default path they use: they get the current language (using get_locale()) and add the relative .mo file to the path passed as argument; then they call load_textdomain() passing as argument both the textdomain … Read more
This fixed it in block.json: “editorScript”: “file:index.js” This is what I used before: “editorScript”: “file:./index.js”,