Available Solutions

Problem:
The client was experiencing an issue where color and image swatches were not synchronizing in the second language, and they had to add the colors and image swatches in English as well.
Solution:
We recommended the following steps to resolve the issue:
1. Navigate to WPML -> Settings -> Custom Term Meta Translation section.
2. Set the fields (color, image, and not_dropdown) to copy.
3. Update the attribute to copy the values.
4. Check the translated product.
We also provided a video to demonstrate the steps (https://files.fm/f/63eahyjht).
These steps were applied to a sandbox site and resolved the issue. We asked the client to check the product on the sandbox site to confirm if the solution works correctly (https://rare-furruco.sandbox.otgs.work/el/product/henectus-tincidunt/).

Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues (https://wpml.org/known-issues/), verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket for further assistance.

Problem:
The client is experiencing an issue where the main language is Latvian, and while translating forms into English and Russian using WPML, the Gravity Form is being overwritten to English.
Solution:
We recommend the following steps to resolve this issue:
1. Edit the file at

wp-content/plugins/gravityforms-multilingual/inc/gravity-forms-multilingual.class.php

in the

Gravity_Forms_Multilingual

class.
2. Replace the code at line 772 from:

$st_context = $this->get_st_context( $form['id'] );
		// Cache.
		$current_lang = $sitepress->get_current_language();
		if ( isset( $this->current_forms[ $form['id'] ][ $current_lang ] ) ) {
			return $this->current_forms[ $form['id'] ][ $current_lang ];
		}

		$snh = new GFML_String_Name_Helper();

		$form = $this->populate_translated_values( $form, $st_context );

to:

$st_context = $this->get_st_context( $form['id'] );
		// Cache.
		$current_lang = $sitepress->get_current_language();
		if ( isset( $this->current_forms[ $form['id'] ][ $current_lang ] ) ) {
			return $this->current_forms[ $form['id'] ][ $current_lang ];
		}

		$snh = new GFML_String_Name_Helper();
 $check = new \WPML\Utils\DebugBackTrace();//add this
if ( $check->is_class_function_in_call_stack( 'GFFormDisplay', 'process_form' ) ) { //add this
	return $form;//add this
}//add this

	$form = $this->populate_translated_values( $form, $st_context );

3. Update the form and try to reproduce the issue.

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum.

Problema:
El cliente tenía problemas con la descripción de productos que no aparecían traducidos en el idioma secundario.
Solución:
1. Pedimos al cliente que actualizara todos los plugins y temas desactualizados para evitar conflictos en el código.
2. Tradujimos dos cadenas de texto específicas y pedimos al cliente que confirmara si el problema se había resuelto.
3. Actualizamos la traducción al 100% de un producto y sugerimos al cliente que hiciera lo mismo con otro producto como prueba, asegurándose de descartar la traducción en la sección de traducción de cadenas por el momento.

Si estás experimentando este mismo problema, te recomendamos que sigas los pasos anteriores. Sin embargo, la solución podría no ser relevante para tu caso si es obsoleta o no aplicable. En ese caso, te sugerimos abrir un nuevo ticket de soporte. También recomendamos encarecidamente revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que has instalado las últimas versiones de temas y plugins. Si necesitas asistencia adicional, por favor, contacta con nosotros en el foro de soporte de WPML.

Problem:
The client noticed an unexpected x-default tag on their pages and wondered if it was due to a recent WPML plugin version upgrade. They asked if there was a way to deactivate it through the plugin interface or if there was a hook available for controlling it programmatically.
Solution:
We confirmed that the x-default tag was indeed automatically added in the WPML version 4.5.0 and that there is no built-in option in the WPML interface to switch it on or off. However, we provided a custom hook that can be used to control the x-default tag. Here is the code that the client can use:

add_filter( 'wpml_hreflangs', 'remove_xdefault' );<br />function remove_xdefault($hreflangs){<br />    foreach ($hreflangs as $key => $lang){<br />        if ($key == "x-default"){<br />            unset($hreflangs[$key]);<br />        }<br />    }<br />    return $hreflangs;<br />}

This code should be added to the theme's functions.php file or a custom plugin to remove the x-default tag.

Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.