This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with product attributes not being available for selection on the product page in different language versions after translation. The attributes appear correctly in the original language but not in the translations. Solution: 1. Ensure that global attributes are created in the site's default language and avoid duplicating attributes under different names in different languages. This can be managed under WPML > Taxonomy Translation. 2. If changes are made to the original product's attributes or variations, save the variations again to sync these changes across translations. There is no need to re-translate the products if only attributes or variations are changed. 3. For issues related to caching, especially with WP Rocket, ensure that the cache is cleared after updates to products. This can be automated by setting up 'Always purge URLs' in WP Rocket settings to include:
/shop/*
4. If these steps do not resolve the issue, it may be helpful to deactivate unrelated plugins and switch to a default theme like Twenty Twenty-One to identify if the issue is related to specific plugins or themes.
If the problem persists or if this solution 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. Additionally, please feel free to open a new support ticket for further assistance 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.
Background of the issue:
I am trying to periodically translate the attribute of a product, but it becomes unavailable for selection on the product page. I resaved the attribute, and it is displayed on the product page, but not in other language versions of the product. Link to a page where the issue can be seen: hidden link
Symptoms:
The translated attribute of a product becomes unavailable for selection on the product page in other language versions.
Questions:
Why does the translated attribute become unavailable for selection on the product page?
How can I ensure the attribute is displayed in all language versions of the product?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
In your example the attributes are available: hidden link
The attributes worked on some translations, while on others not.
The original product in this example is the Ukranian version. I edited the original product, saved it again, and then updated the translation.
This solved the issue for most translations.
Exception: Russian
At this point, I need some guidance and explanation as I am not fully understanding how those attributes were created.
If you review WPML > Taxonomy Translation you will find various taxonomies for global attributes.
Now, if you create your products in Ukrainian, it would also be recommendable to use Ukranian as the default language for your global attributes.
I see here instead a mix of source languages. Some global attributes were originally created in Italian, some in Ukrainian, and so on.
You can see more details about this at Product > Attributes.
Here for example also one attribute uses the same name twice:
Розмір
Further, there also exists "Dimensione".
I would suggest sorting these global attributes out first and then we can take further steps. I suspect that those duplicated entries might cause an issue trying to synchronize the global attributes across languages.
It is better to edit the Ukrainian version of the product. All other languages are translations.
There are no problems with other attributes. The problem is only with these attributes: hidden link and hidden link
Just yesterday, the size list disappeared again on the product page hidden link.
We have tested this issue several times. Your colleagues even provided a solution that does not work.
Please read our dialogues https://wpml.org/forums/topic/problem-with-attribute-translation-2/.
(!!) Currently, these versions do not have attributes: hidden link hidden link
>At this point, I need some guidance and explanation as I am not fully understanding how those attributes were created.
If you read our dialogue with your colleague, you will see that I created a new attribute x-size
I am now using it in this product. I simply created a new attribute. All values here are in Italian.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I understand, but my question is, why are you using duplicated global attributes?
See screenshot.
I would suggest removing "Dimensione".
Further, you see on the screenshot that many global attributes and items were created in Italian. If your original products are all created in Ukranian I would suggest also creating the attributes and their items in Ukranian.
Otherwise, it might cause issues with the synchronization from original source to the target languages.
I created Dimensione as part of testing the issue we discussed with your colleague.
Of course, I can delete it. That's not a problem. But I'm not sure that will solve the issue. Since I did this earlier
There are attributes here now.
This is not the first time I have contacted you about this issue.
But it always ends the same way. It works for a while and then stops working again. When I write to you about this problem, we find a temporary solution and you close my ticket.
And now the same situation is happening again.
Your colleagues recommended that I manually edit one of your plugins.
I have been doing this for over 7 months. Tell me, am I paying you money for this?
I won't even mention that this error, which has been going on for almost a year, is costing my business money. After all, there is no way of knowing when the attributes will stop working. Without attributes, people cannot order products. And you don't seem to care at all.
If so, please take note that this issue is still escalated and our developers are still working on a solution in the coming versions of our plugins.
Until then, the only thing we can offer is the provided workaround, which will need to be added anytime again, after you update WPML String Translation.
Yes, I'm talking about those tickets. It's just taking a very long time. Is it normal for a business to suffer losses because you haven't been able to release updates for almost a year?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Indeed, this issue was reported 8 months ago.
Mainly the developers fix issues or release new features based on the amount of clients that require these changes. The more affected clients, the higher the priority.
In this specific case, the timeframe appears to be longer as it is a fairly complex issue inside WCML that relies on at least one further issue inside WPML and those need to be fixed simultaneously.
Further, this issue has a workaround that should solve the problem while being implemented.
Could you please confirm if the provided workaround is still solving the issue?
