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:
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:
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.
Problem: You are developing a website and need to decide on the best configuration for the default language domain structure using WPML. You are considering whether the default domain should be in a language folder, like http://www.pippo.com/it, or if the default domain should point directly to the Italian language, with English having its own directory, like http://www.pippo.com/en. You are also concerned about potential SEO issues and the compatibility of Yoast SEO with WPML. Solution: If you configure a directory for the default language, it should not impact SEO negatively if you follow the guidelines provided by WPML. You can find detailed instructions on setting up a directory for the default language here.
Regarding the SEO plugin, Yoast SEO is compatible with WPML. To ensure compatibility, you need to install the WPML SEO plugin. You can learn more about using Yoast SEO with WPML here. For specific queries related to Yoast SEO, it is best to contact their support directly. You can find information on how to contact Yoast support here.
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 you still need assistance, please open a new support ticket here.
Problema: Se stai riscontrando un problema con WPML che impedisce di procedere con la traduzione quando il testo è formattato in corsivo, non sei solo. Soluzione: Ti consigliamo di aggiungere il marker anche alla traduzione. Per ulteriori dettagli su come applicare i marker di formattazione, consulta la nostra documentazione: https://wpml.org/faq/how-to-apply-formatting-markers/
Se la soluzione proposta non risolve il tuo problema o se ritieni che le informazioni siano obsolete o non applicabili al tuo caso, ti invitiamo a aprire un nuovo ticket di supporto. Ti consigliamo vivamente di verificare i problemi noti correlati su https://wpml.org/known-issues/, di verificare la versione della correzione permanente e di confermare che hai installato le ultime versioni di temi e plugin.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
