Documentation request

Problem:
The client was unable to translate a single menu point using WPML's string translations feature. Despite translating the string "About us", it still displayed in English on the Dutch version of the website.
Solution:
We advised the client to create separate menus for each language as per our guide on translating menus. Additionally, we recommended increasing the WordPress memory limit to at least 128MB, which can be done by adding the following line to the wp-config.php file:

/* Memory Limit */<br />define('WP_MEMORY_LIMIT', '512M');

After these adjustments, the entire menu needed to be translated, not just the single menu item. Once the menu was fully translated, the issue was resolved.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. We highly recommend opening a new support ticket at WPML support forum for further assistance.

Problem:
The client was unable to translate the content of ACF (Advanced Custom Fields) fields and the page content itself in a custom WordPress site using WPML. The translation interface did not allow changes to the content for different languages, although the ACF field labels were detected correctly.
Solution:
1. We recommended ensuring that ACFs are set as translatable by comparing the site's configuration with the guide on translating sites built with ACF.
2. It was important to set the ACF Groups post type as 'Not Translate' in WPML -> Settings -> Post Type Translation.
3. We advised increasing the WordPress memory limit to at least 128MB, suggesting adding the following code in wp-config.php:

/* Memory Limit */<br />define('WP_MEMORY_LIMIT', '256M');

4. Installation of the String Translation plugin was recommended to manage string translations effectively.
5. We updated the configuration to set ACF fields as translatable, which resolved the issue of fields not appearing in the translation interface.

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, 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.

Problem:
You are trying to translate a blog post into Spanish and Italian. The translations are already done and saved, but in the WP admin post list, WPML still shows a (+) symbol instead of the pencil, suggesting the translation is missing. When clicking the (+), it opens the existing translated post. Additionally, the Spanish and Italian versions are missing from the frontend language switcher.
Solution:
First, check WPML > Support > Error logs to see if there are any errors being generated. If no errors are found, follow these steps:
1. Edit the original post.
2. Make a small change to the content and save it.
3. Resend the post for automatic translation.
For more details, refer to our documentation here: https://wpml.org/faq/translation-status-stuck-or-displaying-the-error-wpml-didnt-manage-to-translate-this-page/
If the issue persists, try the following steps in WPML > Support > Troubleshooting:
1. Clear the cache in WPML.
2. Remove ghost entries from the translation tables.
3. Fix element_type collation.
4. Fix WPML tables collation.
5. Set language information.
6. Fix terms count.
7. Fix post type assignment for translations.
If these steps do not resolve the issue, it might be due to outdated solutions or a different problem. 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 problem persists, please open a new support ticket at WPML support forum.