Problem: If you're experiencing issues with the translations of ACF fields not displaying correctly on your car detail pages, it might be due to the configuration of your field groups. Solution: We recommend setting your ACF Field Groups to 'Not translatable'. You can do this by navigating to WPML → Settings → Post Types Translation. If you have previously created duplicates of these field groups for each language, please delete the duplicates and retain only the default language version. Additionally, ensure that each field within the group has the translation preference set to 'Same fields across language' if you are using the WPML editor to translate. This setup should help WPML correctly synchronize and display the ACF values across different languages. After making these changes, update your default language page, then re-translate, and it should resolve the issue. For more detailed guidance, you can visit these links:
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket.
Problem: You are trying to translate ACF field values on a Car detail page using WPML, but while the texts translate correctly, the property values do not.
Solution: The issue may stem from using Select Fields with Code Widgets in Avada Layouts. Instead of using a Code Widget, we recommend using an Avada Text Widget with the dynamic value set to ACF Select. This approach aligns better with WPML's capabilities.
If you are using ACF Shortcodes, note that they are disabled by default in recent ACF versions due to security concerns. If necessary, you can enable them using the following code snippet:
However, using ACF Shortcodes for Select fields might not work as these are intended only for simple text-based values. Also, embedding Fusion Shortcodes within a Code Widget can disrupt WPML's ability to detect and translate the strings.
We suggest restructuring your content to follow the recommended workflow for using ACF in Avada, as detailed in the Avada documentation.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket at WPML support forum.
Problem: You have translated your Avada menu and header layout using WPML, but the correct header layout is not displaying on the translated pages. Solution: We recommend checking the layout display settings for your translated pages. Specifically, ensure that the correct pages are set in the layout display settings to display the transparent header. This adjustment should resolve the issue of the incorrect header appearing on your translated pages.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Additionally, please check the related known issues and verify that you have installed the latest versions of themes and plugins. For further assistance, you can also visit our support forum.
