[Resolved] WP Bakery widget not translatable

Hello,

thank you for reaching out to us. I have a solution for you that might work perfectly. Sometimes, widgets are not registered for translation by default, so I recommend you go to WPML > Themes and Plugins localization, select all Plugins and Themes and scan them. This way, you can ensure that texts will be available for translation on the String Translation tool. Here's a detailed step-by-step guide on how to do that:

https://wpml.org/documentation/getting-started-guide/translating-widgets/

Please follow these steps and let me know how it goes.

Have a nice day,
Lucas Vidal

Hello,

thank you for sharing the information. About the first solution I showed you, did it work to translate the widgets you showed in your first request?
For the other topics you sent (translating categories, shortcodes and strings) here are some guides you can follow to translate them:

1. How to translate categories: https://wpml.org/documentation/getting-started-guide/translating-post-categories-and-custom-taxonomies/
2. How to translate shortcodes: https://wpml.org/faq/how-to-translate-urls-shortcodes-and-html-attributes-using-the-advanced-translation-editor/
3. Why your translations are not showing on the front end: https://wpml.org/faq/why-arent-my-translated-strings-showing-up-on-the-front-end-of-my-site/#:~:text=Support-,Why aren't my translated strings showing up on the,to use WPML is 128M.

Please share your results. Those are the default ways to translate. If they do not work, I'll be here to further assist you.

Ok, I see. It might be a compatibility issue. I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to a testing site where the issue is replicated.

You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.

IMPORTANT

- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this:

hidden link

Hello,

Indeed, it was a compatibility problem. The title provided by your theme was not properly set so it could be translated. Our developers came up with a workaround:

• Open the app/public/wp-content/plugins/huber-plugin/shortcodes/gp_vc_blog.php file
• Look for the following snippet (around line 124)

<div class="gp-widget-title">

•Replace it with the following code:

<div class="gp-widget-title">
	<?php
		// WPMl Workaround for compsupp-7082
		if (class_exists('Sitepress')){
			$string = $widget_title;
			$textdomain = 'WordPress';
			$string_name = 'WPML Workaround : '.substr($string, 0, 20);
			
			$wpml_default_lang = apply_filters('wpml_default_language', NULL );
			$wpml_current_lang = apply_filters( 'wpml_current_language', NULL );
			
			if ($wpml_default_lang == $wpml_current_lang ) {
				do_action( 'wpml_register_single_string', $textdomain, $string_name, $string );
			}	
			// Apply the translation to the string
			$string = apply_filters('wpml_translate_single_string', $string , $textdomain, $string_name);
			
			$widget_title = $string;  // Replace the title
		}
	?>

• Visit the page with the issue in the original language, to register the string
• Go to WPML > String Translator and translate the string (under WordPresstextdomain)
• Repeat these steps in the gp_vc_showcase file

Please let me know if you need any assistance on doing that.

As for the YARP plugin, I opened a new ticket, so we can look at it separately:
https://wpml.org/forums/topic/split-yarp-plugin-not-translatable/