aigarsM

Problem:
The client needed to change the language code for Estonian from "ET" to "EE" in WPML and encountered issues with string translations not working for the custom "EE" language. Additionally, the client was unable to delete the original Estonian language to set the "Default locale" to "et" because it already existed in the database.

Solution:
We advised the client to:
1. Re-add Estonian from the WPML language list.
2. Change the default locale of the re-added Estonian to any value other than "et".
3. Set the default locale for the custom Estonian ("EE") to "et".
4. Remove the WPML Estonian language.
This process should not create errors and should allow the client to use the "EE" code for Estonian without issues with string translations.

Please note that this solution might be outdated or not applicable to your case. If you're experiencing similar issues and the provided solution does not resolve them, 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 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.