Problem: The client is working on a site under development and needs to stop two ACF fields from being automatically translated, which are currently locked. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to ACF >> Field Groups. 2. Edit the field group containing the fields you wish to update. 3. Set the “Expert” translation option for that field group. 4. Individually edit each field and set the “Translation preferences” to “Copy” if you want the same default language value to appear in secondary languages. If you prefer not to display anything in a secondary language, select the “Don't translate” option. 5. Click the Save Changes button. 6. Re-save the default language pages to apply the updated settings. For more detailed guidance, check the documentation here: Recommended Custom Fields Translation Preferences for ACF and WPML.
Please note that this solution might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is working on a site and trying to translate content using a Google API map but encountered a syntax error in the console for the Italian page, indicating a potential issue with the translation of the map code. Solution: We recommend checking the Translation Editor to ensure that the Google Map code is correctly copied over to the translations. You can do this by accessing your pages list and clicking on the pencil icon to edit a translation with the editor. If the code is present and properly copied, this should resolve the syntax error. If you continue to experience issues or have questions about a different section, such as the FAQ, please open a new support ticket and provide detailed information along with your debug info.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related 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, do not hesitate to contact our support team for further assistance.
