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:
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.
Problem: You have created an option page in ACF and are trying to translate these fields into Arabic using WPML. However, when you type the translation in Arabic and save, the old English content still appears. Solution: To resolve this issue, please follow these steps after taking a full site backup: 1) Navigate to ACF>>Field Groups and open the *Global Info* for editing. 2) Click on the *Change option* link. 3) Select the *Expert* option and save the changes. 4) Set the *Translate* option for the *Contact Us* Group Field. 5) Save the changes and go to the *Site Values* Options page. 6) Switch to Arabic. 7) Change the value of the *Address* field and save the changes. For more details, refer to this screencast: https://dl.dropboxusercontent.com/scl/fi/oc6e9zgs3ikq1yn544au1/2024-11-04_16h48_28.mp4
If this solution does not apply to your case, or if it seems outdated, 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where links in automatically translated pages were not converting to contain the other language slug. Instead, links remained pointing to the English pages even when switching languages. Solution: We identified that the client was using a widget from an Gutenberg add-on. To resolve this, we manually registered the widget for translation by creating a custom XML configuration file. We followed the instructions provided on the WPML documentation page: https://wpml.org/documentation/support/language-configuration-files/make-custom-gutenberg-blocks-translatable/ Additionally, we modified the XML configuration using the xpath method to allow manual translation of the links.
If this solution does not resolve your issue or seems outdated, we 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 the problem persists, please open a new support ticket for further assistance.
