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.
Our wait time is higher than usual, please make sure you are meeting the minimum requirement - https://wpml.org/home/minimum-requirements before you report issues, and if you can take a look at current Known Issues - https://wpml.org/known-issues/. Thank you.
I tested a bit more and I'm quite sure that I found a bug.
The fields are configured like this:
group_field (type: group - translation preference: copy)
-> group_field_1 (type: text - translation preference: translate)
-> group_field_1 (type: text - translation preference: copy once)
After this I did the following:
- I added values to these fields in the primary language;
- I opened up the secondary language and the fields are prepopulated with the values from the primary language (which is great);
- I changed the values of the fields and saved the page;
- The newly loaded page again shows the values from the primary language.
So it seems like the translation value from the group (group_field) is being used for all fields.
When I change the translation setting for the group field to 'translate' it no longer pre-populates the sub-fields from new languages with the value from the primary language. When I add a value to the field it is saved, though.
When I change the group field to 'copy once', I'd expect (if everything works) the values for sub-fields to get copied when opening another language as well. But that doesn't happen either.
Our developers are still checking the issue, in the meantime, they suggested the following workaround, can you try it and see if it works?
- Set the group fields to copy
- Update the options in the main language
- Update the options in the secondary language
- Set the group field to translate again
You will now have all fields copied to the secondary language and can modify the values as well.
Thanks for getting back at me. 👍
This will probably work, although I have many option pages with several groups in them so this is not really convenient. And if the secondary language already had differing fields, that data will be overwritten. I understand that it's a temporary workaround and it could work for setting up a new language.
Thanks for coming back with me, it's been too long already (no offence, of course).
I hope a definitive solution will be available soon!
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.