Skip to content Skip to sidebar

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

Last updated by Paweł Halicki 2 weeks, 6 days ago.

Assisted by: Paweł Halicki.

Author Posts
April 21, 2026 at 8:04 am #17983002

shantoA

We have raised this issue several times across different support topics. On all translated product pages, attribute values are completely missing. Only the labels display.

Example:
- English (working): hidden link — Specifications accordion shows “Model: E750V2”
- Any translated page (e.g. /nl/, /de/, /da/) — shows only “Model:” with no value

All attribute taxonomies are set to “Don’t translate” in WPML settings. The values should be carried over from English but they are not.

---

We want to be transparent: since migrating to WPML we have spent a significant amount of time on these maintenance issues that should have been resolved from the start. We have 10 active languages and customers across the EU who cannot read product content or navigate the site properly. This is directly impacting our sales.

We need all three issues resolved as a priority. We are happy to provide access again if needed.

Thank you.

April 21, 2026 at 11:31 am #17983860

Paweł Halicki
Supporter

Hello,

I’ll be happy to help. You mentioned several similar reports - I took a quick look, but I didn’t find any environment access details. Having access to an environment where the issue can be reproduced (ideally as minimal as possible) would be very helpful in resolving the problem effectively.

My question is: would it be possible to prepare such an environment and share access? I will mark my next reply as private.

Of course, if that’s not possible, I’ll try to reproduce the issue based on the description (or prepare a sandbox environment where we can recreate it together). In most cases, these kinds of issues are easier, faster, and more reliably diagnosed on a “small environment with a full set of plugins,” where the problem can be reproduced consistently.

In the meantime, I’ll review the remaining threads more thoroughly and try to reproduce the issue to find a solution.

Best regards, and I look forward to your feedback,
Paweł

April 21, 2026 at 3:16 pm #17984942

Paweł Halicki
Supporter

Hello,

Thank you for the quick response and for providing the details. I’m working on this task and will split all reports into separate tasks.

---

I can see that a backup is already being prepared so we can work on the exact same environment — this may be necessary to resolve these specific issues.
Currently, the backup generation via Duplicator is at 60% and was started at `2026-04-21 16:07`. I’ll keep monitoring it, or alternatively try to obtain a backup from another forum thread if the other supporter (Long) manages to generate one.

---

I’m not sure if any actions have already been taken, but when checking:

* hidden link
* hidden link
* hidden link
* hidden link

At the moment, when expanding the “Specifications” tab, I can see both Parameter and Value displayed.

Could you please confirm this on your side? I need to verify whether something has changed or if I might be checking it incorrectly.

Best regards, and I look forward to your feedback,
Paweł

April 21, 2026 at 3:47 pm #17985021

shantoA

Hi Paweł,

We have checked and can confirm — the attribute values are now showing correctly on translated product pages. Both the parameter and value are displaying in the Specifications accordion across Dutch, German and Danish.

Thank you for investigating this. This ticket can be closed.

The remaining open issue is the menu disappearing on save, which is being handled separately with Long.

Thank you.

April 21, 2026 at 9:31 pm #17985401

shantoA

Pawel, for some reason its not showing again on different languages. can you please check into this?
For all other products its showing except the cryptphone attribute value doesnt.

April 21, 2026 at 9:46 pm #17985405

shantoA

Hi Paweł,

Thank you for your investigation. We were able to identify and resolve the issue ourselves while you were preparing the environment. Here is a full technical summary of what we found and how we fixed it.

---

Root cause

All translated product copies (post_type = post_product) had zero pa_* taxonomy term relationships in wp_term_relationships. The English source products had all attribute terms correctly assigned, but when WPML created the translated copies, it did not copy the term relationships for product attribute taxonomies (pa_color, pa_model, pa_storage, pa_screen-type, etc.).

This is why translated pages showed attribute labels but no values — the labels come from WooCommerce attribute registration, but the values come from term relationships which were missing entirely on all translated product posts.

Interestingly, weight and dimensions were displaying correctly on translated pages because those are stored as post meta fields (_weight, _length etc.) which WPML does copy. Only the pa_* taxonomy relationships were missing.

---

Fix applied

We wrote a PHP script that:
1. Retrieved all pa_* term_taxonomy_ids linked to each English source product via wpmu_term_relationships
2. For each translated product copy (all 10 language versions), inserted the missing term relationships
3. Skipped any relationships that already existed to avoid duplicates

Results:
- 59 products processed
- 7,470 term relationships inserted across all 10 languages
- All translated product pages now display full attribute values correctly

---

This ticket can be closed. Thank you for your prompt response and for preparing the environment — we appreciate the support.

Note: we still have an open ticket with Long regarding the menu disappearing on save issue, which remains unresolved.

Thank you.

April 22, 2026 at 4:27 pm #17988503

Paweł Halicki
Supporter

Hello,

I’m glad that this specific blocker has been resolved. Thank you also for providing the cause along with a very detailed analysis - I will prepare a note from it, and we will also try to implement a safeguard for this scenario in our plugins.

I hope the issue from the second thread will also be resolved soon.

If everything is covered in this thread, I would kindly ask to close it.

Best regards and have a nice day,
Pawel