ACF Options Page field is not showing translation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing an issue where the English version of content is still showing on Arabic pages, despite using Greenshift's 'meta getter block' and WordPress patterns.
Solution:
We recommend trying the following steps after ensuring you have a full site backup:
1) Navigate to WPML>>Settings>>Custom XML Configuration.
2) Add the following language configuration code and save the changes:

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="greenshift-blocks/text" translate="1" label="Advanced Text">
      <key name="dynamictext">
        <key name="dynamicField"></key>
      </key>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

3) Open the 'Contact Us' pattern for editing in English and update it to refresh the translation settings.
4) Update the Arabic translation of the 'Contact Us' pattern with the Arabic option names (options_ar_contact-us_email, options_ar_contact-us_mobile-number, options_ar_contact-us_address).
5) Then update the page in both languages that uses the Arabic pattern.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.

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 is split from https://wpml.org/forums/topic/acf-options-page-translation-4/

Tagged: Bug, Compatibility

This topic contains 8 replies, has 2 voices.

Last updated by basselS-2 2 days, 14 hours ago.

Assisted by: Bigul.

Author	Posts
November 5, 2024 at 12:19 pm #16366507
basselS-2	Hello Bigul, However, there is still an issue, and the English version is still showing in Arabic pages. Please check for example the address under the map on the main page: hidden link Looking forward to your kind support. Regards,
November 5, 2024 at 12:49 pm #16366737
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hello, Welcome to the WPML support forum. I will do my best to help you to resolve the issue. This may be a compatibility conflict. How you are listing the Address field value on the homepage. Please share more details about it. It will help us to track the problem. -- Thanks! Bigul
November 5, 2024 at 1:05 pm #16366852
basselS-2	I am using greenshift using their meta getter and patterns. Could you please access 'my patterns' and you would find it there along all the details.
November 5, 2024 at 1:06 pm #16366853
basselS-2	using their 'meta getter block' and wordpress patterns
November 6, 2024 at 4:43 pm #16373992
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hello, Thank you for the updates. This looks like a compatibility issue. So one request. Can you please try to reproduce the issue in a fresh installation on our sandbox site? It will help us a lot in debugging and we can escalate the issue directly to our developers. Thank you for your kind understanding. Please click this URL to visit the test site - hidden link Please try the following steps in the sandbox site and make sure the issue exists or not. 1) Configure WPML like your live site 2) Install and activate ACF Pro 3) Install your theme 4) Create an option page or export & import it (field groups) from your live site 5) Create a pattern and translate it -- Thanks! Bigul
November 11, 2024 at 6:01 am #16386595
basselS-2	Hello, Thanks for the reply. I really do not understand. I have given access to the website, so everything should be accessible from your side where you can try things or see things in the sandbox you have. Thanks for understanding,
November 12, 2024 at 9:57 am #16391884
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hello, Thank you for the feedback. We request that the issue be recreated in a fresh installation to speed up the debugging. I made a new copy of the site and will test it further and get back to you soon. Please wait. -- Thanks! Bigul
November 15, 2024 at 6:13 pm #16409507
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hello, The bug is existing after the initial troubleshooting steps. So consulting with our team for an expert opinion now. We will get back to you as early as possible. Please wait. -- Thanks! Bigul
November 22, 2024 at 10:07 am #16433060
Bigul Supporter Languages: English (English ) Timezone: Europe/Vienna (GMT+01:00)	Hello, We are getting the expected results in our local copy and the sandbox site after the following steps. The translation is not showing in the frontend because the Pattern stores the Arabic option name in database. Please try it after a full site backup and let us know your feedback. 1) Visit WPML>>Settings>>Custom XML Configuration 2) Add the following language configuration code and save the changes <wpml-config> <gutenberg-blocks> <gutenberg-block type="greenshift-blocks/text" translate="1" label="Advanced Text"> <key name="dynamictext"> <key name="dynamicField" /> </key> </gutenberg-block> </gutenberg-blocks> </wpml-config> 3) Open the Contact Us pattern for a edit in English and update it (to refresh the translation settings) 4) Update the Arabic translation of Contact Us pattern with the Arabic Option names (options_ar_contact-us_email, options_ar_contact-us_mobile-number & options_ar_contact-us_address) 5) Then update Page in both language (which uses Arabic pattern) Please refer to the attached images and following URLs for more details. hidden link hidden link (On the bottom of the page you can view the translation) -- Thanks! Bigul
November 22, 2024 at 10:32 am #16433222
basselS-2	Thank you. Finally the issue is resolved. Really appreciate your support and dedication. I hope this could be done automatically without any additional steps in the future. Best of luck,