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.

This topic contains 9 replies, has 2 voices.

Last updated by Itamar 1 year, 4 months ago.

Assigned support staff: Itamar.

Author Posts
February 18, 2019 at 7:57 am #3210423

fernandoG-11

In this post

https://wpml.org/forums/topic/acf-options-pages-are-not-duped-translated/page/2/#post-2438094

Shekhar mentioned it might be possible to support content from ACF Options pages in String Translation in the future. I would like to check the status of this improvement to ACFML.

This would save us manually handling strings for fancy custom menus built using ACF Field Groups on ACF Options pages.

February 18, 2019 at 9:35 pm #3214183

Itamar
Supporter

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi.

There is no progress on this issue. Probably it was given a lower priority. I'll ping our developer and remind him about this issue. When I have news about this issue, I'll let you know here.
Meanwhile, you can try a workaround that I've found here.
https://wpml.org/forums/topic/force-synch-of-some-custom-fields-between-languages/
Please see the yellow summary section at the top of the ticket.

Thanks,
Itamar.

February 19, 2019 at 4:41 am #3215086

fernandoG-11

Thanks Itamar. I've successfully implemented the workaround, so please let me know if/when strings from the options page can be extracted directly by the plugin.

February 19, 2019 at 6:30 am #3215215

fernandoG-11

Actually, I just saw in the release notes for ACFML: https://wpml.org/version/acfml-1-0-4/

"Fixed translation of ACF Options Page"

What was fixed there exactly? Thanks!

February 19, 2019 at 1:41 pm #3216877

Itamar
Supporter

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi.

Our ACFML developer explains to me the following on how to translate the ACF options page.

This is how translating options page translation should work:
- open options page in wp-admin and provide values
- save
- switch language at this page using top menu bar language switcher
- provide translated values
- save

Does it work for you this way?

Thanks,
Itamar.

February 19, 2019 at 2:12 pm #3217060

fernandoG-11

Yes, as described in my first post, this is the workaround I am currently using. But I am trying to get the strings into Translation Management so I can send them to a service provider - as far as I know, this is currently not possible.

February 20, 2019 at 5:26 am #3219941

fernandoG-11

Also there is another step in addition to what you describe above. The Field Group must first be cloned in the target language before the fields even appear on the Options page. This also means means any changes to the English Field Group are not propagated to the duplicates.

tl;dr the workaround works, but it is a bit clunky. I'm going to close this ticket, please include the thoughts here in a feature request. Thanks!

February 20, 2019 at 12:34 pm #3221619

Itamar
Supporter

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

When translating a field group you need to first duplicate it. It is mentioned in or documentation. https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#translating-field-groups.

Translating a field group is only optional and a user can do that if he needs the interface of the of the field translated as well. But you say if I understand you correctly, that without duplicating the field group it is not possible to translate the options page.
Is this correct?
Is this the what you want me to include in the feature request?

February 21, 2019 at 11:11 am #3226926

fernandoG-11

I understand translating field groups is optional in most cases, and that the field group needs to be duplicated before translation.

However, as referenced in my first post, the only way to translate user-facing content (not the interface, field labels or any backend stuff) specified on the Options screen is through this process of duplication and manual entry. My feature request is to implement a way to include this user-facing content in string translation so it can be picked up by the Translation Management module and translated as usual by our service provider.

The Options screen is often used by ACF developers to design custom menu behaviour, so this feature would make those menus easily translatable by WPML. Closing this ticket now, feel free to re-open if you need more details of how we use ACF. Thanks!

February 21, 2019 at 11:35 am #3227036

Itamar
Supporter

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi.

Thanks for explaining this issue.
If you wish you can submit this feature request here.
https://wpml.org/suggest-a-new-feature-for-wpml/

Best Regards,
Itamar.