Problem: The client experienced severe instability on their large multilingual WordPress website using WPML, including 500 and 502 errors, login issues, and CPU spikes. The hosting provider initially attributed the issue to configuration problems but later found that reducing the PHP memory limit had caused the issues.
Solution: We confirmed that for larger WPML environments, a higher PHP memory limit is often necessary. Symptoms like intermittent errors and CPU spikes can indeed result from insufficient memory. For large sites, we recommend a minimum of 1GB of PHP memory and increasing the
max_input_vars
to at least 10,000. While there are no specific WPML recommendations for PHP memory limits, more memory generally results in better performance. Additionally, optimizing site performance through caching can also be beneficial, as detailed in our guide: Optimize WPML-powered site performance using WP Rocket.
If this solution does not fully address your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needed advice on handling external redirects, especially since the LiExtension was conflicting with WPML. Solution: If you're experiencing similar issues with external redirects and are using an Apache server, we recommend adding the redirects using the
.htaccess
file. Alternatively, you can use the Redirection plugin. Always ensure to verify the plugin’s compatibility with WPML by checking here.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: You are experiencing an issue where taxonomy terms from the default language (French) are unexpectedly duplicated in the English version when using WPML in combination with JetEngine and JetSmartFilters. This results in duplicated terms not linked as translations and affects filtering logic, causing significant manual effort to maintain data consistency. Solution: We recommend checking your site configuration, any potential plugin conflicts, and ensuring all plugins are updated to their latest versions. Since the source of the problem was not identified despite the site appearing stable for now, if the issue reoccurs, please do not hesitate to contact us again. We may need to review the settings, hooks, or workflows involved, or possibly request access to your site for further debugging.
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 for further assistance.
Problème : Le client a rencontré trois problèmes principaux : les images ne s'affichent pas après la traduction des produits, les boutons sur les pages traduites redirigent incorrectement, et l'incapacité de traduire le bouton 'confirmer le paiement' ainsi que les documents de facturation du plugin PDF Invoices & Packing Slips for WooCommerce. Solution : Pour le problème des URL qui ne fonctionnent pas correctement après la traduction, nous avons identifié que le problème provenait d'un plugin spécifique. Nous avons recommandé de désactiver ce plugin car il entre en conflit avec WPML et de contacter ses auteurs pour un débogage plus approfondi. Concernant le bouton e-crawl, nous avons demandé plus d'informations sur la configuration et l'appel de ce bouton sur les pages pour pouvoir assister plus précisément. Pour les autres problèmes, notamment celui des factures, nous avons ouvert un nouveau ticket pour traiter ces questions séparément afin de maintenir l'efficacité de notre support.
Il est possible que cette solution ne soit plus pertinente en raison de mises à jour ultérieures ou parce qu'elle ne s'applique pas à votre cas. Nous vous recommandons vivement de consulter les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
Problem: If you're experiencing issues where your translated search results page in German does not appear on your website, despite other languages working correctly, there are a couple of steps we recommend you try. Solution: 1. Ensure the German page is not in Draft mode: - Navigate to the Edit screen of the page in English. - From the top admin bar, change the language to German. - Confirm that the page is published and not a draft. 2. Check if the German language is hidden: - Go to "WordPress Dashboard > WPML > Languages". - Verify if the German language is set as hidden. If it is, unhide it using this guide: https://wpml.org/documentation/getting-started-guide/language-setup/hiding-languages-on-the-front-end/ 3. Address potential slug conflicts: - Identify and modify any conflicting slugs to unique values for the German language page. - Save permalinks to refresh the permalink cache after making changes. - Check the functionality across all language versions to ensure the issue is resolved.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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 problem persists, please do not hesitate to open a new support ticket with us for further assistance at https://wpml.org/forums/forum/english-support/.
Problem: After updating WPML to the latest version, the client experienced an issue where the 'Translate content' button was disabled (greyed out) when editing products on a WooCommerce site. This problem affected all products and persisted despite running WPML troubleshooting tools, switching to the Classic Translation Editor, and testing multiple products. The issue was linked to the WPML REST API requests being blocked. Solution: The issue was resolved by identifying that custom security rules in the server configuration (.htaccess and WAF) were unintentionally blocking WPML REST API requests. With the assistance of the hosting provider, these rules were removed, restoring full functionality to the translation dashboard and bulk translation process.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client was unable to find an option to enter the site key in WordPress for WPML registration. Solution: We advised the client to first check if WPML was fully registered or connected to their account. Here are the steps we recommended: 1. Log into your WPML account. 2. Navigate to the 'Register WPML on your sites' link to manage or create a new site key. If these steps did not resolve the issue, we requested the client to provide access credentials privately to further investigate the configuration and ensure everything was set up correctly. Additionally, we confirmed that WPML was registered correctly at the provided admin URL, where the client could also manage their registration keys.
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.
Problem: Si estás intentando traducir tu página al francés y notas que no se cargan las tipografías en la versión en francés, y estás utilizando el tema DIVI, este problema podría ser familiar. Solution: Una solución efectiva que encontró el cliente fue modificar la configuración de nginx para permitir el acceso a los archivos de fuentes. Aquí te mostramos cómo hacerlo:
Además, te recomendamos verificar las rutas de los archivos de fuentes en la versión francesa para identificar posibles problemas con el prefijo del idioma, inspeccionar la integración entre DIVI y WPML en relación con la configuración de traducción de fuentes, y revisar la consola del navegador o la red para detectar errores de activos de fuentes que faltan en la versión en francés.
Si esta solución no es relevante para tu caso, porque podría estar desactualizada o simplemente no aplicar, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos, verifiques la versión de la solución permanente y confirmes que tienes instaladas las últimas versiones de los temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: The client is experiencing difficulties with WPML on various levels, including issues with content translations and the initial setup. Specific challenges include translating Patterns, Templates, and Template Parts, and confusion about whether WPML is the right choice for their needs.
Solution: 1. Confirm that the WPML setup wizard has been completed and that all necessary components are installed. 2. Ensure that post types are set to 'Translatable' and review custom fields translation settings. 3. Use the Translation Dashboard to locate and translate Patterns, Templates, and Template Parts. 4. If issues persist, consider sharing a short video or providing temporary access to the site for direct assistance from our support team. 5. For further guidance, visit the WPML Getting Started Guide and check our known issues page.
If the solution provided here does not resolve your issue or seems outdated, we recommend opening a new support ticket. It's also advisable to verify the version of the permanent fix and confirm that you have installed the latest versions of themes and plugins. For further assistance, please contact us through the WPML support forum.
Problem: The client reported an issue where the translated footer on their page did not match the original footer, nor the non-translated version, indicating a potential mismatch in the template mapping. The site uses the TT5 theme, which previously encountered issues with menu definitions when attempting to implement multilingual capabilities with Polylang. Solution: We requested the client to provide the URL for editing the footer in the original language and to share access credentials securely to investigate the footer translation and verify the WPML configuration. We also advised the client to ensure a full site backup is available before making changes.
If you're experiencing similar issues, we recommend checking your template settings and ensuring your WPML configuration is correct. For detailed guidance, visit our documentation on WPML documentation.
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.
Problem: The client is experiencing issues with their translated page where the company logo does not show, the menu item formatting from the original page is not maintained, and they cannot add a language switcher to the menu as it is greyed out. Automatic Media Translation is enabled, and menu synchronization does not find any synchronized menus. Solution: We recommend creating a staging site to safely replicate and address these issues without affecting the live site. You can use the WP Staging plugin, which is free and user-friendly. Once the staging site is set up, please share the URL to edit the header in the original language, and we will use the credentials from your other ticket to assist further.
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 these steps do not resolve your issue, please open a new support ticket at WPML support forum for further assistance.
