Translation works with global variables, you just need to wait until the proper hook to call the translation functions. I haven’t looked at the code or documentation, but just by experimenting, the translations are loaded sometime before the after_setup_theme hook, but after the other hooks that fire before that. That means that if you try … Read more
you must have to enque your parent theme first. function load_parent_stylesheet() { wp_enqueue_style( ‘parent-styles’, get_template_directory_uri() . ‘/style.css’ ); } add_action( ‘wp_enqueue_scripts’, ‘load_parent_stylesheet’ ); Then load your translation folder function my_theme_lang_setup() { $lang = get_stylesheet_directory() . ‘/languages’; load_child_theme_textdomain( ‘your-domain’, $lang ); } add_action( ‘after_setup_theme’, ‘my_theme_lang_setup’ ); Put this in your function.php and try
It’s quite well explained here: https://developer.wordpress.org/themes/functionality/internationalization/ Basically ensure that all plain text uses the get_text functions with a text domain for your theme: https://developer.wordpress.org/themes/functionality/internationalization/#basic-functions Add code to ‘Load’ any translations https://developer.wordpress.org/themes/functionality/internationalization/#loading-translations. Once you have done that, IF translations exist they will be used. THEN to get the translations. This is also useful https://codex.wordpress.org/I18n_for_WordPress_Developers There are … Read more
It seems that you’re adding translatable strings with text domain “custom-strings” but loading a text domain “Divi” in load_child_theme_textdomain. Needs to be the same Don’t use the same text domain as your parent theme. If your parent theme is Divi, use divi-child (it should match your child theme slug). In your child theme’s style.css, define … Read more
Your error (actually a warning) seems to come from the Theme Check plugin. There’s nothing wrong with the code you’re showing above. ‘acf’ is your text domain. and the _n function takes four arguments as you’ve given it. It strikes me that the Theme Check plugin is not very good at static analysis of function … Read more
so you will need at least translations into german. there shouldn’t be other packages loaded for your site. you can find these files in the language folders in wp-content. there are other language folders as well in the plugins or in thmemes.
If there is no filter to change the content, the other option is to add a function hooked to gettext – for example: /** * Change text strings * * @link http://codex.wordpress.org/Plugin_API/Filter_Reference/gettext */ function wpse_382257_text_strings( $translated_text, $text, $domain ) { switch ( $translated_text ) { case ‘Check your email for the confirmation link, then visit … Read more
Internationalization of a plugin doesn’t mean that you can change its language by setting some option. It means, that translation for this plugin is provided within the package, so after changing the language of WP, the plugin will use the same language as WP does. If you want to change the language of WP, you … Read more
No, you wouldn’t use the translation functions (__(), _e() etc.). Those are for creating language files and must only be used on static strings. They need to be static because the tools for generating the language files don’t execute PHP, so they can’t process variables. They just parse the text of the code, essentially. If … Read more
My advice would be to not use the label as the value in your dropdown. The value is stored in the database and used programatically in your template, so it doesn’t need to be localised. Then you can translate the label without any side effects. public function qib_button_style_callback() { $items = array( ‘theme-style’ => __( … Read more