WPML breaks woocommerce zoom.js

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 0 replies, has 0 voices.

Last updated by aigarsM 2 days, 17 hours ago.

Assisted by: Shekhar Bhandari.

Author	Posts
January 21, 2025 at 7:31 am
aigarsM	Background of the issue: I have added WPML and activated auto-translate to translate the website. The issue can be seen on this page: hidden link. On the original language products, everything appears normal: hidden link (hidden link). Symptoms: When I switch the language, the WooCommerce zoom.js does not work, and the product images are three times the size of the viewport, breaking the website (hidden link). Questions: Why does the WooCommerce zoom.js not work when switching languages? How can I fix the product image size issue when using WPML?
January 21, 2025 at 8:17 am
January 28, 2025 at 8:06 am #16640218
aigarsM	Hi, sorry for the delay. I have created a test site where the issue can be seen: hidden link I don’t see a place where I can share the new credentials in this support ticket. Could you point it out? Thank you!
January 28, 2025 at 8:08 am #16640223
Shekhar Bhandari Supporter Languages: English (English ) Timezone: Asia/Kathmandu (GMT+05:45)	Hello there, Sure, I will enable the private reply so please add the details in the next reply. Thanks
January 29, 2025 at 7:49 am
January 29, 2025 at 9:04 am #16645096
Shekhar Bhandari Supporter Languages: English (English ) Timezone: Asia/Kathmandu (GMT+05:45)	Hi there, The issue was caused by the custom related products settings. There is a section in your product settings where this can be configured, but it was not set to copy over to secondary languages. As a result, the layout appeared broken. To resolve this, please follow these steps: 1. Navigate to WPML → Settings → Custom Field Translations. 2. Click on Show system fields. 3. Search for _crp_related_ids and set it to Copy. 4. Save the changes. 5. After saving, update the product in the default language. Let me know if this resolves the issue. Thanks!
February 4, 2025 at 1:45 pm #16667032
aigarsM	Again sorry for the delay. I will check the solution right now!
February 4, 2025 at 2:13 pm #16667244
aigarsM	The solution seems to be working. Can you explain how I could have arrived at the solution myself? Also, the site has almost 300 products. Is there a faster way to fix the issue rather than going through each product and updating it manually?
February 5, 2025 at 4:31 am #16668986
Shekhar Bhandari Supporter Languages: English (English ) Timezone: Asia/Kathmandu (GMT+05:45)	Hello there, The fix was found after using performing various debugging steps so it's not possible to explain as this may not be useful for other issues. Regarding the products, you can bulk update the products as mentioned here: https://woocommerce.com/posts/bulk-update-products/ Let me know if this helps. Thanks
February 5, 2025 at 8:08 am #16669269
aigarsM	I understand. Thank you! Could you please check one more thing? For some reason, string translation does not seem to work consistently—some strings are translated, while others are not. Enabling "Look for strings while pages are rendered" appears to help, but as I understand, this is only a debugging tool and should not be enabled on a live site. I would normally create a separate ticket for this issue, but since this site has multiple WPML-related issues that I can't debug myself, I'm including it here along with the previous one. New threads created by Shekhar Bhandari and linked to this one are listed below: https://wpml.org/forums/topic/split-string-arent-showing-translated/
February 5, 2025 at 8:49 am #16669468
Shekhar Bhandari Supporter Languages: English (English ) Timezone: Asia/Kathmandu (GMT+05:45)	Hello there, Since we handle one issue per ticket, I have created a new ticket for your issue. Thanks
February 6, 2025 at 7:24 am #16673730
aigarsM	I understand. Thank you! This tickets issue has been resolved.