Problem: You are experiencing issues with translating Advanced Custom Fields (ACF) in WPML on your website. Specifically, when translating a WYSIWYG description field from French into Dutch and English, the translations display HTML codes instead of formatted text. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to your WPML dashboard. 2. Switch the language from the top admin bar. 3. Edit the translated body template. 4. Edit the text module that retrieves the description field. 5. Ensure that the Raw HTML is enabled. 6. Update the translated template.
This solution might be irrelevant if it's outdated or not applicable 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 the issue persists, please open a new support ticket.
Problem: The client was unable to see the WPML Translation Editor when editing a custom post and had issues translating an ACF field, as well as translating content using a shortcode with Divi Theme Builder.
Solution: Firstly, we recommended increasing the WP Memory Limit to at least 256M by adding the following code to the wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');
We also suggested checking with the hosting provider if the memory limit could be increased even further.
For the ACF field translation issue, we advised checking the ACF Field Groups Settings and selecting the 'Expert' mode for translation preferences. This allows individual fields to be set as translatable. We provided a guide for reference: Choosing how to translate field groups Expert translation option
For translating the shortcode content, we suggested that if the shortcode or it's attributes are not available in the WPML Translation Editor, the client could try to locate it manually by placing the shortcode directly in the translated content using Divi.
If these solutions do not resolve the issues, or if they seem outdated or not applicable, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the problem persists, please open a new support ticket.
