When viewing the French site, I expect to see `$twitter_handle = 'TwitterHandleHere'`.
Instead, I got `$twitter_handle = null`.
I then go to my options page (which has no editable fields in my other languages).
When viewing the French site, I now see `$twitter_handle = 'TwitterHandleHere'`.
This may be a misunderstanding on my part around how the WPML 'Copy' setting functions. I guess 'Copy' means it is literally copying the value on save to the FR version.
If this is not a bug, could it please be a feature request for 'Copy' (Or a new setting?) to pull the value from the default language directly? Trusting the end user to remember to go and save an options page that doesn't actually have any editable fields on seems rather counterintuitive.
I've added a screenshot of my options page, showing all fields locked and showing the values I'm expecting greyed out.
1 - The currently backend behaviour is confusing. It's not clear from this that the fields in French are technically "empty". It's showing me a greyed out value from the default language in the backend so that's why I'm expecting when I use get_field() to get the default value on the frontend.
2 - I'd prefer not to have to hit save on 1/2/3/4 different languages for every options page.
I've seen some workaround in the community such as this thread, these do work for me but I was expecting ACFML v2 to handle this sort of thing for me: hidden link
Symptoms:
When viewing the French site, I see `$twitter_handle = null` instead of the expected value 'TwitterHandleHere'. After re-saving the options page, the value appears correctly.
Questions:
Can the 'Copy' setting be modified to pull the value from the default language directly? (Or a new setting added).
Thank you for taking the time to submit your feature request. I have escalated your request to our second-tier support team for further review and consideration. I will keep you updated as soon as I receive feedback from their end.
I have various true/false checkboxes on my settings page, which are all set to ‘copy’. They are also displayed correctly and with a lock in the different languages on the options page. However, they only have the correct values in the frontend when I save them again in the respective languages. This is a bit annoying for me and very difficult to explain to customers ...
Hello, is this feature planned for implementation soon? I completely agree that it's counterintuitive to require saving the options page in other languages—especially when the fields are set to "Copy" and appear locked and non-editable. It gives the impression that the values should already be inherited automatically, so needing to manually save each language version adds unnecessary complexity, particularly for clients.
I am afraid we don't have any updates on this feature request yet. However its still submitted in our system to be reviewed by our team. We do not have an ETA that if or when it will be accepted as a feature request.
Apologies for the inconvenience and we appreciate your understanding and patience. Thank you
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.