This thread is resolved. Here is a description of the problem and solution.
Problem: You are experiencing issues with product variations not being synced when resaving a product using the WPML editor, even after following a guide that temporarily fixed the issue. Solution: 1. Clear the object caches on your site. 2. Make a slight change to the title of the default product and update the product translation. 3. Clear the caches again to ensure all variations display correctly. If the issue persists across many products: - Disable object caching if possible. - Navigate to WooCommerce > WooCommerce Multilingual > Attributes, select the problematic attribute, and click "Synchronize Attribute". - Go to the Status tab and select troubleshooting options as shown here and start the process. For ongoing issues related to object cache compatibility with WPML, refer to the Errata page here and consider using the workaround plugin available here. For excluding specific cache groups, follow the guide here.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum 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.
- Please open the default product in WordPress Editor.
- Scroll to the 'Variation' section and delete the variations named "11 A" and "11N"(As both of them are not showing in translation) and save the variations. Then update the product.
- Now, add the variations again, and ensure that the price and other information are added properly. Save the variation and then update the product.
- Update the product translation.
- Once done, go to "WPML > Support > troubleshooting"
- Select "Variations" from the dropdown under 'Cleanup' and click on the "Synchronize Post Taxonomies" button.
I hope it will help. Feel free to let me know if you need further assistance in this matter. I will be happy to help.
I deleted variations named "11 A" and "11N" from English, saved the product, recreated them, saved again and resaved translation. After that I performed "Synchronize Post Taxonomies" under Cleanup as seen from the screenshot, but that did not fix it.
En: hidden link
Fi: hidden link
I also deleted cache (disabled it actually to be 100% sure), but still the issue is there.
Hello There,
Thank you for trying out the suggestions.
I tried to access the links, but since they are protected by a browser login, I was unable to proceed and examine the issue further. However, as the issue persists, It seems that a more detailed inspection will be necessary to identify the root cause.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to have a testing site where the issue is replicated.
You will find the needed fields below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please backup site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Hi There,
Thanks for sharing the access information.
I've checked and successfully resolved the issue with the variations. Here's what I did:
- First, I cleared the Object caches on your site.
- Then, I made a slight change to the title of the default product (hidden link).
- Updated the product translation, I cleared the caches again. Here is the result: hidden link
Now, all 11 variations are displaying correctly in Finnish.
if you ever encounter the issue again, make sure to clear the object caches and then update the product and its translation. The variiations should appear properly after that.
Please feel free to let me know if you need further assistance in this matter. I will be happy to help.
1. How can we automatically do that for all product that are missing variations, because there are way too many products (and we won't be able do go through all 10-11k products)?
2. How can we make sure that this won't happen again because we have lost considerable amount of revenue because your plugin is not compatible with object cache?
Hi There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
1) If the issue happening with all your products, you can try the following steps:
- Please clear the object caches on your site and, if possible, disable it.
- Navigate to WooCommerce > WooCommerce Multilingual > Attributes.
- Use the dropdown menu to select the attribute whose variation isn't displaying correctly.
- Scroll to the bottom of the page and click the "Synchronize Attribute" button. Wait for the synchronization process to complete.
- After that, go to WooCommerce > WooCommerce Multilingual > Status tab.
- Click on "troubleshooting" at the bottom of the page.
- Select the options shown hidden link">here and click on "Start."
2) We are aware of some issues that may arise while using the Object cache with WPML. We have documented these possible problems in an errata page. For more details, please visit this Errata: https://wpml.org/errata/object-cache-pro-various-issues/
If the issue happens again could you please try following the workaround mentioned in the Errata? You can download the plugin mentioned in the Workaround from this link: hidden link
Additionally, if you can identify the cache group within the Object Cache plugin where the Variation data is stored, you can add this group to the exclusion list. You can edit the plugin file I shared above and include the group in the Array. For more detailed instructions, please refer to this guide: hidden link">hidden link;.
We have completed the troubleshooting steps, and we will keep an eye on the issue. If the issue happens again, we will install that errata plugin - but what exactly does it do?
Also, should we synchronize other things on the troubleshooting page, as seen from the added screenshot?
Note! How should we have known that there is an issue with some other plugin and WPML? For example, with the object cache in our case. We won't realize it until we discover there's an issue, potentially losing a lot of revenue before we figure it out and finally create a ticket. A better way to find out would be if there were some notices in the WPML plugin sections, perhaps even a new tab. And when there are some plugins installed that are incompatible or may cause issues with WPML, it would let us know. Can your team consider creating something like that, the notice of compatibility tab or something similar?
The plugin mentioned in the Errata will add the WPML cache groups to the non-persistent caching group. In simple terms, this means that certain WPML-related groups will be excluded from being cached. As a result, any caching-related issues with WPML will no longer occur.
If you want, you can find the relevant cache groups in the Object cache plugin and add them to the non-persistent cache group by editing the plugin file.
Regarding synchronizing the other option - Depending on your needs, you can synchronize various elements. For example, if an image is not showing in the translation, you can synchronize the gallery image. If a category is not assigned correctly, you can synchronize the category. However, if everything is working fine, there's no need to synchronize them.
Regarding your concern about notifying users about plugin incompatibilities, I understand the importance of identifying potential conflicts with other plugins. However, implementing a feature that automatically detects and notifies users of such conflicts is quite challenging for several reasons. With thousands of plugins being developed and updated regularly, tracking and testing the compatibility of every single plugin with WPML in real-time is an enormous and impractical task.
I can inform our team about this feature, but I can't guarantee whether it will be accepted. In the meantime, we have a directory where you can check if a plugin or theme is compatible with WPML. I'm including the links below.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
