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.

We’re currently experiencing a system outage that is affecting our automatic translation service. We’re working to resolve the issue, and services will be back online soon. Thank you for your understanding.
Sun Mon Tue Wed Thu Fri Sat
13:00 – 17:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 -
- 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: Asia/Jerusalem (GMT+03:00)

Tagged: 

This topic contains 1 voice and has 0 replies.

>

Assisted by: Eran Helzer.

Author Posts
June 6, 2023 at 6:25 am #13775241

Pablo

Thank you. When I set the field to Translate I can set them independently and it works as expected - however, the Copy setting does not work as expected regardless of the Local JSON bug.

To demonstrate, create a custom text field, set the translation preference to Copy, and attach it to a Post. When you edit a post in the non-original language, the field is read-only and a lock icon appears next to it with a message "This field value is copied from the default language and will be kept in sync across languages". This does not happen when you have a custom field set to Copy and attached to a taxonomy - there is no indication that the field is not editable in both languages.