Product attributes and variations are not copied to translated products

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing issues with translating WooCommerce products using WPML. The attributes, variations, prices, and stock statuses are not being copied correctly to the translated products. The client tried using both the WPML Translation Editor and the Classic WordPress editor, but faced issues like missing variations, out-of-stock status, and missing product descriptions.

Solution:
We recommended using the Advanced Translation Editor (ATE) for translating products to ensure that all content, including variations and videos, is correctly copied. We adjusted some incorrectly configured system custom fields and updated the product translation using the Classic Translation Editor, which resolved the issue with variations appearing correctly in the secondary language. For the issue with the commercekit_wc_video_gallery custom field not being copied, we are investigating a potential incompatibility or regression in the latest version of our plugins and may need to escalate this to our 2nd tier of support.

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 issues persist, please open a new support ticket at WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: WCML

This topic contains 15 replies, has 0 voices.

Last updated by Carlos Rojas 6 months, 3 weeks ago.

Assisted by: Carlos Rojas.

Author	Posts
October 16, 2025 at 10:17 am #17489635
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi, 1.- The text is split line by line because the original text is also split this way in an unordered list. This is the expected behavior. If you had a paragraph, you would see it in only one segment. 2.- Yes, the content translated using the Classic Translation Editor can't be loaded in ATE and vice versa. The translation methods (CTE, ATE, and WordPress interface) are independent. 3.- The product images are appearing twice, probably because the CommerceGurus CommerceKit plugin has activated the option to alter the product gallery, and it is saving the same information in the database. However, in ATE, when you translate a segment, if the same segment is present, it will automatically be translated; therefore, you will only need to translate the image texts once. 4.- Regarding the theme logo, I kindly ask you to open a new ticket describing the problem so we can treat it separately. This way, we will respect our support policy of solving one issue per ticket.

Author

Posts

October 16, 2025 at 10:17 am #17489635

Carlos Rojas

WPML Supporter since 03/2017

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+02:00)

Hi,

1.- The text is split line by line because the original text is also split this way in an unordered list. This is the expected behavior. If you had a paragraph, you would see it in only one segment.

2.- Yes, the content translated using the Classic Translation Editor can't be loaded in ATE and vice versa. The translation methods (CTE, ATE, and WordPress interface) are independent.

3.- The product images are appearing twice, probably because the CommerceGurus CommerceKit plugin has activated the option to alter the product gallery, and it is saving the same information in the database. However, in ATE, when you translate a segment, if the same segment is present, it will automatically be translated; therefore, you will only need to translate the image texts once.

4.- Regarding the theme logo, I kindly ask you to open a new ticket describing the problem so we can treat it separately. This way, we will respect our support policy of solving one issue per ticket.