ziga pipan

Problem:
The client translated a product to Croatian, but the color attributes did not copy over, resulting in the loss of product variations. This issue occurred after updating WPML to the newest version.
Solution:
In this case, the client needed to go to WPML > Settings > Custom Field Translation and make sure that the field settings for the attributes are set to "Translate". After that, edit the original product, save the product, and update the translation.
If these steps do not resolve the issue, we 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 reported that two categories were missing in the Croatian version of their shop sidebar, even though everything was translated correctly. After inserting specific categories manually, they appeared but were not expandable like in the original version.
Solution:
We identified that the issue was due to missing term meta keys for the order in the database. We recommended running the following SQL commands to add the missing term meta:

INSERT INTO `wpnj_termmeta` (`term_id`, `meta_key`, `meta_value`)<br />VALUES ('832', 'order', '1');

and

INSERT INTO `wpnj_termmeta` (`term_id`, `meta_key`, `meta_value`)<br />VALUES<br />  ('847', 'order', '1'),<br />  ('860', 'order', '1'),<br />  ('897', 'order', '1'),<br />  ('914', 'order', '1'),<br />  ('944', 'order', '1'),<br />  ('960', 'order', '1'),<br />  ('987', 'order', '1'),<br />  ('995', 'order', '1'),<br />  ('996', 'order', '1'),<br />  ('999', 'order', '1'),<br />  ('1001', 'order', '1'),<br />  ('1002', 'order', '1');

We also advised clearing transients from WooCommerce tools after running these commands. It is crucial to create a backup before performing any database modifications.

If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
The client was unable to access certain translation features in WPML after an update, specifically encountering issues with translating taxonomies and products. Additionally, the client could not add a translation manager as no user was found.
Solution:
We recommended the following steps to resolve the issue:
1. Ensure a complete site backup is taken.
2. Open the

functions.php

file of your theme in a code editor.
3. Insert the following function to expand translation manager capabilities:

/**
 * Expand translation manager caps to be able to translate taxonomies
 */
add_filter( 'user_has_cap', 'wssupp_boost_caps', 10, 1 );
function wssupp_boost_caps( $allcaps ){

	$newcaps = array();

	if ( isset( $allcaps['manage_translations'] ) && $allcaps['manage_translations'] ) {

		$newcaps = [
			"wpml_manage_taxonomy_translation" => true
		];
	}

	return array_merge(  $allcaps, $newcaps );
}

4. Save changes to the file.
**** Important! Please make a full site backup (files and DB) before you proceed with these steps****
After applying these changes, check if the issue with the 'Translate Products >' button is resolved.

If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.