[Resolved] Native Woocommerce Product Attribute Term Thumbnails
This thread is resolved. Here is a description of the problem and solution.
Problem: The client translated all product attribute terms into every language using WPML but found that the term thumbnail images did not automatically display for all translated terms.
Solution: 1. Identify the custom field name used for term thumbnails. This can vary depending on the theme or plugins used. 2. Set the translation preference for this custom field in WPML to 'Copy'. This ensures that the thumbnail images display correctly across all languages. 3. If the field is set to 'Don't translate', change it to 'Copy' in WPML -> Settings -> Custom Term Meta Translation, then save the changes. 4. Update the translation of the term to reflect these changes.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, 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. 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.
Background of the issue:
I’ve translated all my product attribute terms into every language via WPML → Taxonomy Translation → Product Taxonomy (X), and everything is working well. I am trying to make the term thumbnail image appear in all languages on my site hidden link.
Symptoms:
The term thumbnail image does not automatically display for all translated terms.
Questions:
How can I make the term thumbnail automatically display for all translated terms?
Thank you for your help. My "thumbnail_id" was already set to "copy". I guess this isn't working for me because I use the Woocommerce plugin "WooCommerce Product Search" by Itthinx (officially woo plugin). See printscreen.
Is there a way to also set this thumbnail to "copy"?
1.- This field is probably set as non-translatable in the same section as the thumbnail_id; however, I will need to take a closer look.
Please share the URL of the product attribute in the screenshot attached to your previous message.
2.- Also, I have set your next message private so you can share the access credentials to the site in a secure way. This will allow me to visit the URL shared in the previous point and check the configuration.
Thank you very much for sharing the information requested.
If you edit the term and inspect the image, you will find the field id 'product_search_image'. That custom field is set to 'Don't translate' in WPML -> Settings -> Custom Term Meta Translation
Just change the configuration of the 'product_search_image' field to 'Copy' -> Save the changes and update the translation of the term.
Thank you for checking. Unfortunately I don't think it is resolved, the field id you checked is named 'product_search_image' and the configuration in wpml -> settings -> custom term meta translation says 'product_search_image_id'.
Yes, 'product_search_image_id' is the correct field. I set it to 'Copy' then re-saved the term (hidden link) in English, and when I update the term into the secondary languages, you can see the image.
Fantastic, thanks Carlos!
Now it's working on my end as well.
The first time I tried my Yoast Multilingual plugin / Yoast Woocommerce plugin was activated and for some reason I get an error every time I save a taxonomy with with those plugins active.
I deactivated them, updated the taxonomy terms and now everything is working well.
If you have a clue why my SEO plugins in combination with WPML and taxonomy updates crashes feel free to let me know 🙂
Hi, I'm happy to hear that the original issue was solved 🙂
Regarding the problem with Yoast, I kindly ask you to check if there is any error in the JavaScript console of the browser or in the debug.log file. With your findings, I will split the ticket and will continue there.
