You could hook into the action switch_blog. You get the new blog ID as the first argument here. But loading the complete translation files here is expensive, you also have to restore the old files after that. WordPress does not use native gettext functions, but some custom code that is much slower. See #17268. The … Read more
load_theme_textdomain() returns TRUE on success and FALSE if no file was found. For debugging try the following change: function my_theme_setup(){ $path = get_template_directory() . ‘/languages’; $result = load_theme_textdomain(‘my_theme’, $path ); if ( $result ) return; $locale = apply_filters( ‘theme_locale’, get_locale(), ‘my_theme’ ); die( “Could not find $path/$locale.mo.” ); }
Have a look at the wp-settings.php file. You’ll see that the plugins_loaded action is triggered before the theme is loaded. The first action available for themes to hook into is the after_setup_theme action.
TL;DR: If you use strings that are in the parent theme, exaclty how they are used in parent theme, you don’t need to have a text domain for your child theme. But if you use strings that aren’t used in parent theme, to make them translatable, you’ll need another text domain with related translation (.mo) … Read more
No, this is not okay. NO NO NO. Here’s my favourite Otto quote: Inside all translation functions, no PHP variables are allowed in the strings, for any reason, ever. Otto explains this in more detail, but the simple way to say it is that translation calls are parsed, not executed . So your variable (let … Read more
In this case, ‘themify’ is the defined textdomain for the Theme, used to make the Theme translatable. (Codex reference: load_theme_textdomain()). Making a Theme translation-ready requires a few steps. Define the Theme’s textdomain: load_theme_textdomain( ‘themify’, TEMPLATEPATH.’/languages’ ); Define translatable strings in the template. This is done using one of a few translation functions: __() (for returned … Read more