Available Solutions

Problem:
The client is experiencing two issues: first, imported XLIFF translations are visible on the front-end but not within the Advanced Translation Editor (ATE). Second, the Mega Menu breaks after synchronizing menus with WPML.
Solution:
For the XLIFF import issue, we explained that translation services rely on the Classic Translation Editor (CTE) and it is expected that translations will not be visible in the ATE nor editable there. To resolve this, we recommend disabling the ATE in the WPML translation editor options by navigating to WPML -> Settings. Switching to the CTE may serve as a workaround.
Regarding the Mega Menu issue after WPML Menus Sync, we would need more information to provide a specific solution. If you're experiencing similar issues, please note that the solution provided might be outdated or not applicable to your case. 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 the problem persists, please open a new support ticket with us for further assistance.

Problem:
The client reported a WordPress database error related to invalid data in some tables, specifically mentioning an issue with a Jetpack plugin error message that persisted even after uninstallation.
Solution:
We identified that the error message contained an emoji, which might have contributed to the database issue. We removed the specific message from the database, and the error did not reappear. We recommend checking your site to confirm that the error message no longer displays. If you're experiencing similar issues, we suggest removing any special characters or emojis from database entries that could potentially cause errors.

Please note that this solution might be outdated or not applicable to your specific 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.

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.