Home›Support›English Support›[Resolved] wc/store/v1 api retrieving wrong language for endpoint products/attributes/{attr_id}
[Resolved] wc/store/v1 api retrieving wrong language for endpoint products/attributes/{attr_id}
This thread is resolved. Here is a description of the problem and solution.
Problem: You are trying to retrieve a single attribute in a specific language via the `wc/store/v1` API endpoint, but you are receiving the attribute name in the default language (German) instead of the requested language (English). Solution: Attributes themselves are not translatable via the REST API, only their labels. To translate attribute names, navigate to WooCommerce → WooCommerce Multilingual & Multicurrency. In the 'Attributes' tab, scroll down to the 'Translations of taxonomy labels and slug' section and add the translations. As a workaround, you can use localized data to parse an object with all product attribute taxonomy names and their
$tax->labels->singular_name
, since labels are well translated thanks to WPML. This localized data is stored as a transient per language and deleted when their terms or taxonomies are edited/created/deleted.
If this solution seems outdated or does not apply to your problem, we recommend checking the known issues, verifying the version of the permanent solution, and confirming that you have the latest versions of themes and plugins installed. Don't hesitate to open a new support ticket if you still need help. Visit our 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:
Ich versuche, einen `wc/store/v1` API-Endpunkt anzufordern, um ein einzelnes Attribut abzurufen: hidden link. Andere Endpunkte funktionieren wie erwartet, z.B. das Auflisten der Begriffe für dieses Attribut: hidden link. Auf einer einzelnen Produktseite, die in PHP gerendert wird, sind alle Attributübersetzungen korrekt: hidden link. Ich habe gerade (lokale Entwicklungsumgebung) auf WordPress 6.7.2, WooCommerce Version 7.9.0, WooCommerce Multilingual & Multicurrency Version 5.4.2, WPML Multilingual CMS Version 4.7.2 und WPML String Übersetzung Version 3.3.2 aktualisiert, aber der Fehler besteht weiterhin.
Symptoms:
Ich erwarte, den englischen Attributnamen `Fruit color` zu sehen, stattdessen erhalte ich den deutschen (Standardsprache) `Fruchtfarbe`.
Questions:
Warum wird das Attribut in der Standardsprache angezeigt, obwohl ich die englische Sprache angefordert habe? Und bei anderen endpoints der selben API die korrekte Sprache angezeigt wird.
If it works fine for single term, it should also work for the attribute. Let me create a test site and test this out a bit further, and I will get back to you soon.
I have checked further, and it seems this is somehow expected, since Attribute are not translatable ,only their label is, so you will get defaul Attribute. Only attribute terms are translatable.
Also ,there is note in our docs that says next, which is same limitation.
"Please note that you can use the REST API to translate Attribute terms (e.g. Blue), but not Attribute names (e.g. Color). To translate Attribute names, go to WooCommerce → WooCommerce Multilingual & Multicurrency. In the Attributes tab, scroll down to the Translations of taxonomy labels and slug section and add the translations."
Hope this makes sense, let me know if any further questions.
> To translate Attribute names, go to WooCommerce → WooCommerce Multilingual & Multicurrency ...
I think I understood you right. If yes, I did this step already. It works for the php rendered stuff. But unfortunately doesn't for the wc rest api responses. It works for attribute terms, but not for attribute names. But, well, it kind of makes a lot of sense. Regarding on how taxonomies and terms are stored in WP and how woocommerce is utilizing that to store products attributes.
I tried some workarounds, maybe the steps are helpful for someone.
Workaround 1: extending the wc store api. That works well for the schemas `product`, `checkout`, `cart-item` and `cart` but wc doesn't allow to extend the `product-attribute` schema.
So the final workaround is: Using localize data to parse an object with all product attributes taxonomy names and their `$tax->labels->singular_name` (since labels are well translated thanks to wpml) to the frontend. And in frontend I can use this singular labels with a fallback to the taxonomy name from wc api.
... the localize data is stored as a transient per language, and gets cleared when their terms or taxomony is edit/create/delete
