Skip Navigation

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 – 16:00 9:00 – 16:00 9:00 – 16:00 9:00 – 16:00 9:00 – 16:00 -
- 17:00 – 18:00 17:00 – 18:00 17:00 – 18:00 17:00 – 18:00 17:00 – 18:00 -

Supporter timezone: Africa/Cairo (GMT+03:00)

Tagged: 

This topic contains 5 replies, has 3 voices.

Last updated by deanm-3 2 years ago.

Assisted by: Ahmed Mohammed.

Author Posts
June 12, 2023 at 3:19 pm #13810921

Pablo

Using ACFML and ACF Pro. I have created a custom post type, a custom taxonomy and then created an ACF taxonomy field attached to the custom post type. The custom post type and custom taxonomy are set to Translatable in the WPML settings. The ACF taxonomy field for the taxonomy is set to Copy. I add several terms to the taxonomy and translate them. I create a new custom post and select one of the taxonomy terms and save. I create a new version of the post in the 2nd language by clicking the Duplicate checkbox in the Language metabox and then clicking the Duplicate button, then clicking the pencil icon to edit the new post. I update the new post and am told WPML will create a new translated version of the post. I change the taxonomy term selection, and even though there is a Lock icon next to the field, after clicking update and refreshing the page, the taxonomy terms have been changed. If I go back to the original language and change the terms and update, only new ones which are added are updated in the 2nd language version.

June 13, 2023 at 11:14 am #13816147

Ahmed Mohammed
Supporter

Timezone: Africa/Cairo (GMT+03:00)

Hi Pablo,

Thank you for contacting WPML support!

I understand you can edit the custom taxonomies in the other languages where they're set to "Copy" and this is not the expected behavior.

I have created the following sandbox website: hidden link - please log in using that quick login URL and replicate the unexpected behavior so that we can check what is happening and forward it to our developers when needed.

Looking forward to hearing back from you.

June 13, 2023 at 3:15 pm #13818619

Pablo

Thanks Ahmed. I have reproduced the problem in the sandbox.

June 14, 2023 at 8:57 am #13823155

Ahmed Mohammed
Supporter

Timezone: Africa/Cairo (GMT+03:00)

Hi Pablo,

Thank you for reproducing the issue.

I have escalated the issue to our second-tier support for further debugging. I will inform you as soon as I receive any updates from them.

June 14, 2023 at 10:18 am #13823943

Ahmed Mohammed
Supporter

Timezone: Africa/Cairo (GMT+03:00)

Hi Pablo,

The bug has been confirmed and escalated to our development team.

For the time being, you can use this workaround:

- Go to: wp-content/plugins/acfml/dist/js/native-editor-translation-edit/app.js and unminify the code
change from:

})(e) && e.querySelectorAll("input, textarea, select, button").forEach((function (e) {
                        e.readOnly = !0
                    }))

To

})(e) && e.querySelectorAll("input, textarea, select, button").forEach((function (e) {
                        e.readOnly = !0, e.disabled = !0
                    }))

Hope that helps 🙂

June 18, 2024 at 10:27 am #15748404

deanm-3

I checked wp-content/plugins/acfml/dist/js/native-editor-translation-edit/app.js with ACFML v2.1.3 the patch is not applied.