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.

Sun Mon Tue Wed Thu Fri Sat
- - 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00
- - - - - - -

Supporter timezone: America/Lima (GMT-05:00)

Tagged: 

This topic contains 2 replies, has 0 voices.

Last updated by Andreas W. 5 months ago.

Assisted by: Andreas W..

Author Posts
March 8, 2025 at 10:12 am #16790964

Noothan Mathew

Sorry, if it wasn't clear enough, I'm not using the same slug - I clearly know that it wont work if I use the same slug.

For eg:

Source taxonomy term data is :

[name] => Gravity Loading initial calculation type
[slug] => gravity-loading-initial-calculation-type
[parent] => Acquisition workflows

The update I am making through WPML taxonomy translation is:

[name] => Gravity Loading initial calculation type ES
[slug] => gravity-loading-initial-calculation-type-es

Please note, there is no field to select parent in the UI (see screenshot).

The above update is not retaining the parent relationship, it saves as below:

[name] => Gravity Loading initial calculation type ES
[slug] => gravity-loading-initial-calculation-type-es
[parent] => 0

Hope things are clear now.

Screenshot 2025-03-08 at 11.11.26 PM.png
March 8, 2025 at 11:47 am #16791142

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

My apologies if I am repeating myself, but I am not sure how to assist you on this matter.

When using the recommended way to display ACF Repeater Fields, which I took from ACF's website, the translated taxonomies showed up as expected:
https://wpml.org/forums/topic/acf-repeater-taxonomy-fields-are-not-showing-up-on-translation-editor-2/page/2/#post-16780386

If you still suspect a bug, I can offer a new test site on which you can upload your theme, create a post and taxonomies, and try to recreate the issue.

Would you like me to send you a link to a test site?

March 9, 2025 at 9:01 am #16792559

Noothan Mathew

Thank you for being patient, I understand it is frustrating.

Let's take a few steps back, and forget about ACF repeater fields for now.

I hope you remember suggesting the idea of bulk translating ACF taxonomies by assigning the all the taxonomies to a post and send it to translation ( please see your comment here : https://wpml.org/forums/topic/acf-repeater-taxonomy-fields-are-not-showing-up-on-translation-editor-2/#post-16721177)

****************
... If you would like to have a translation service to translate all the categories, you would need to create one post, add all untranslated taxonomies to it, and then send the post to translation. If the taxonomy was not yet translated, it will be translated together with the post. ......
****************

I tried this above recommendation by creating a post here - hidden link and assigned to convert the source language terms to "ES" via our translation service.

Please see the job here (Batch name : WPML|en|06-03) : hidden link

All the terms came back successfully, but none of them are retaining the origin term's parent relationship.

Please kindly check the attached screenshot below. I have tried to explain the problem to my best.

My question is, do I need to manually select the parent of this translated taxonomy term or is there an issue with WPML?

Screenshot 2025-03-09 at 9.55.57 PM.png
March 11, 2025 at 4:26 am #16799259

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

This actually might be the reason for the issue that you are experiencing.

I have created a new test site and can confirm the issue when translating the categories assigned to a post the taxonomy hierarchy is not respected.

---

WORKAROUND:
To solve this issue, please go to WPML > Taxonomy Translation, select "Categories" from the dropdown, and go to the tab "Hierarchy synchronization".

Run the dialog and this will fix the issue.

---

I will follow up with the Second Tier Support about this issue, as at the moment I am unaware if this behavior is currently expected or not.

Best regards
Andreas