This thread is resolved. Here is a description of the problem and solution.
Problem:
The client reported an issue where enabling WPML String Translation caused the product page to display correctly only in the original language, not in the translated language. Additionally, enabling the Single Product Layout resulted in a blank page.
Solution:
We conducted tests and found that the issue was specific to the client's server. A workaround that resolved the problem involved setting the AJAX Variation Threshold value to a lower number, specifically 10. This adjustment helps in loading variation data only when necessary, improving page performance and reducing memory usage. We recommended that the client apply this change to their live site after ensuring a full backup.
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 problems persist, please open a new support ticket for further assistance.
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.
This product exemplifies what happens when WPML String Translation is ENABLED.
Curious thing is that when enabled, only works on the translated language.
Why does it work in the original language but not in the translated language when WPML String Translation is ENABLED? It works in both languages when the plugin is DISABLED.
Welcome to the WPML support forum. I will do my best to help you resolve the issue.
I am getting the expected result for this product in my local copy after the following steps: hidden link
1) Upgrade to the latest version of plugins (including WPML & WooCommerce Multilingual)
2) Deactivated all other plugins except WooCommerce
3) Switch to the WoodMart parent theme
4) Deactivate & reactivate the String Translation plugin
5) Update WooCommerce Database
6) Activate the rest of the plugins as a group of 3-4 plugins
7) Switch to the WoodMart Child theme
So just to make sure, are you facing the similar issue with products in the original language other than hidden link? Please confirm.
Thanks Bigul. Let me try and I'll get back to you asap.
On my earlier email, I also informed that the media translation is not working. We translate images but changes does not reflect on the translated page.
You can check on my initial post where I have enclosed some images of the translation and how is not working. Did you have time to have a look at that issue??
Thank you for the feedback. We will wait for your updates on this. We are still working on the media translation bug and will get back to you as soon as possible in the original ticket. Please wait.
I follow all these steps below and nothing happen. Single product page keeps returning a blank page!
1) Upgrade to the latest version of plugins (including WPML & WooCommerce Multilingual)
2) Deactivated all other plugins except WooCommerce
3) Switch to the WoodMart parent theme
4) Deactivate & reactivate the String Translation plugin
5) Update WooCommerce Database
6) Activate the rest of the plugins as a group of 3-4 plugins
7) Switch to the WoodMart Child theme
So just to make sure, are you facing the similar issue with products in the original language other than hidden link? Please confirm.
It happen on both original and translated page! This only happen when 2 conditions apply:
1/ The Custom Single Product Page is enabled (part of Woodmart Theme)
2/ The variable product has 3 or more variations.
Thank you for the feedback. Please check the attached images. It is loading as expected in our local copy (we made this copy of the site without media files to reduce the backup file size). So, a couple of requests for tracking this.
1) Please share a screenshot for a better understanding of the following page settings
The Custom Single Product Page is enabled (part of Woodmart Theme)
If Custom Page is disabled, the product works fine.
2) Please share the URL of the products having similar issues
The test that you passed me has no media. If I remove all images of all variations, the product shows correctly. Please see my test product (duplicate of the product variation with the problem). If I add all the images to all variations is when the problem triggers and returns a blank page. You can see here below, same product, one with all image variations and one with no images:
hidden link hidden link
About the Custom Single Page:
1. Go to Dashboard and you will see "Layouts" under "Theme Settings"
2. On Layouts, there is the option "Single Product" to make a custom product page. If this option is ENABLED (Active) is when the problem triggers. If you DISABLE (Deactived), the product shows correctly.
3. Also mentioning that the Single Product Layout cannot be translated as it freezes all the time. No way to make save it. The rest of Layouts work fine.
Regards.
New threads created by Bigul and linked to this one are listed below:
Thank you for your feedback and for creating a test product. We will continue debugging the issue using the latest versions of WooCommerce and WordPress, and we will get back to you as soon as possible. Please wait.
Also, please note that I have created a copy of the site (without media files) to make it easier to debug the blank screen issue on product posts. The product variations are visible in the local copy. Please refer to the attached images for more details.
Sorry for the late response becuase of the holidays. We are still working on both issues and consulting with our team for an expert opinion now. We will get back to you as early as possible. Please wait.
I have updated you on the main ticket. Please check. Also, created a new ticket for the Product Layout translation issue for easy follow-up and will get back to you soon on the latest ticket.
Thank you for the updates. Please check the latest reply on the main ticket. This appears to be a compatibility issue. It would be helpful if we could reproduce the bug on a fresh installation, as that will make it easier for us to identify a fix.