Problem: The language switcher flag is aligned to the top of the mobile header instead of the middle, unlike other icons. Solution: We recommend adjusting the CSS for the mobile language switcher. Specifically, you should modify the CSS to remove the bottom margin from the
line, the switcher should align properly in the middle of the mobile header.
Please note that 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 is experiencing issues with displaying the WPML language switcher in a custom header space created with Elementor and the Saasive theme. Solution: 1. Edit Your Header Template with Elementor: Access your WordPress admin, navigate to Templates → Theme Builder, and edit your header with Elementor. 2. Add the WPML Language Switcher Widget: In the Elementor editor, search for the WPML Language Switcher widget and add it to your header. 3. Customize and Publish: Customize the appearance of the language switcher and publish the changes. 4. Translate the Header: Ensure the header template is translated for all languages using WPML’s Translation Dashboard. 5. If the issue persists, consider adding the language switcher to the main menu for better visibility across all devices. You can manage this in WPML -> Languages -> Menu language switcher. 6. Adjust the style of the language switcher using CSS at WPML -> Languages -> Language switcher options -> Additional CSS.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please open 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, you can contact us directly at WPML support forum.
Problem: The client reported that Google only indexes the English pages of their multilingual site, even when manually indexing other languages. The '/EN/' slug appears despite other languages being set up, and WPML is configured correctly.
Solution: We recommended the following steps to address the issue: 1. Ensure the WPML SEO Add-on is active by checking under Plugins → Installed Plugins. If not present, install and activate it from Plugins → Add New → Commercial tab. 2. Verify the presence and correctness of 'hreflang' tags on translated pages by viewing the page source and searching for 'hreflang'. 3. Check the WPML's Language URL format under WPML → Languages and ensure 'Different languages in directories' is selected. 4. Disable the Browser Language Redirect temporarily under WPML → Languages to avoid confusion during indexing. 5. Re-save permalinks under Settings → Permalinks and re-submit sitemaps in Google Search Console.
Additionally, we advised against using the Browser Language Redirect feature as it does not distinguish between users and search engine bots, which can affect SEO and indexing. This is documented in our guides:
If these steps do not resolve the issue or if the information 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.
Problem: If you're experiencing issues with image alignment in a multilingual site using WPML and Elementor, where images within Hebrew (RTL) text are not aligning as expected compared to their English (LTR) counterparts. Solution: We recommend checking how your theme or page builder, such as Elementor, handles RTL layouts. WPML sets the language direction, but the actual layout response, including image alignment, is controlled by Elementor and your theme. You might need to adjust the Elementor widgets and templates manually or apply CSS that uses logical properties for alignment, rather than fixed directional values. For further assistance, consider reaching out to Elementor Support.
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 with us for personalized assistance.
Problème : Le site canaropa.com est devenu très lent et parfois inaccessible. Le client a demandé une analyse pour déterminer si les plugins WPML contribuaient à ces problèmes de performance. Solution : Nous avons constaté que la mémoire et le CPU étaient entièrement utilisés, ce qui indique une surcharge des ressources. Plusieurs plugins ont été identifiés comme sources d'erreurs et de requêtes lentes, ce qui contribue à la lenteur du site. Bien que l'augmentation des ressources serveur puisse aider, nous recommandons de réaliser un audit complet du site pour identifier et éliminer les éléments inutiles. Il est également conseillé de vérifier la base de données pour identifier les tables les plus lourdes et évaluer leur taille appropriée. Nous avons temporairement désactivé WPML pour les tests, et il semble que la mémoire soit toujours très utilisée, bien que jamais entièrement. Pour la configuration actuelle du site et son contenu multilingue, 3 Go de RAM devraient suffire, mais le processeur pourrait nécessiter une évaluation plus approfondie.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous invitons à ouvrir un nouveau ticket de support. Nous vous recommandons également de consulter les problèmes connus et de vérifier que vous avez installé les dernières versions des thèmes et plugins.
Problem: After implementing WPML Multilingual CMS on a WordPress site with Elementor Pro and Advanced Custom Fields Multilingual, some content disappeared, and errors such as 'setting validation failed. title: invalid_value' appeared. Additionally, there were multiple errors in the WPML error log. The client resolved the issue temporarily by resetting WPML and deleting all translations from pages, ACF custom fields, and taxonomies, which restored the normal functionality of the site. Solution: We first need to confirm if the issue is directly related to WPML. We recommend deactivating WPML to see if the issue persists. If the problem remains, it suggests that the issue might not be solely related to WPML. If you have a backup from before the issue occurred, try restoring it to verify if the custom fields work correctly without WPML. If they do, this could indicate a potential conflict or misconfiguration during the WPML setup or translation process.
If this solution does not resolve your issue or seems irrelevant due to being 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: En la página de traducción al inglés, la imagen principal no se visualiza y las imágenes no se agrandan al hacer clic, a diferencia de la versión en español. A pesar de aumentar la memoria y marcar la opción de traducción automática, el problema persiste en ciertas páginas, como https://karlagutierrez.design/en/claudio-coello/. Además, se identificó un error al intentar abrir la publicación original en el Editor Divi: Uncaught (in promise) InvalidValueError: ETBuilderInitGoogleMaps is not a function. Solution: El problema está relacionado con un error en el módulo de Google Maps de Divi, no con WPML. Este error impide que WPML cree una traducción correcta. Se recomienda: 1. Consultar con el equipo de Divi para resolver el error de Google Maps. 2. Una vez resuelto el error en la publicación original, actualizar la traducción en WPML.
Si esta solución no resuelve el problema o si parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problem: The client has been unable to activate the WPML plugin on a simple single landing page website hosted on GoDaddy. Despite following previous advice to add a specific code snippet to the wp-config.php file, the plugin still does not activate or allow registration. Attempts to manually force database table creation through theme functions also failed, and the client is unable to change hosting providers. Solution: We recommend starting with a manual inspection of the file and database for incomplete WPML table creation or permissions issues, as standard and forced activation processes have failed. It's important to check the site environment for unusual file/folder permissions, database connection errors, or server restrictions, particularly with GoDaddy's known limitations. Avoid repeating previous unsuccessful methods such as modifying wp-config.php or using theme functions.php workarounds. Instead, consider direct intervention steps like requesting temporary admin access, reviewing system logs if possible, and ensuring proper communication with WPML registration servers.
If this solution does not resolve your issue or 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problème : Sur iPhone et iPad, la police de votre site ne se charge pas correctement lorsque le plugin WPML est activé. Une erreur de type 'downloadable font: Glyph bbox was incorrect' apparaît dans la console. Solution : Ce problème est souvent lié à la configuration du serveur plutôt qu'à WPML directement. Nous vous recommandons d'activer CORS (Access-Control-Allow-Origin) sur votre serveur. Une autre solution consiste à modifier le fichier .htaccess pour permettre le chargement correct des polices. Vous pouvez trouver des instructions détaillées sur la manière de procéder sur notre forum WPML : https://wpml.org/forums/topic/split-access-to-font-at-from-origin-has-been-blocked-by-cors-policy/
Si cette solution ne résout pas votre problème ou si elle semble obsolète, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, 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 sur notre forum : https://wpml.org/fr/forums/forum/assistance-en-francais/.
Problème : Le site est très lent et souvent inaccessible. Après avoir désactivé le plugin WPML, le site devient accessible. Cependant, l'hébergeur a identifié que les plugins Query Monitor et Google Site Kit étaient la cause du problème, et non WPML. Solution : Si vous rencontrez des problèmes de lenteur avec WPML, nous vous recommandons de vérifier s'il y a des erreurs ou des avertissements liés à WPML dans le journal de débogage de WordPress ou dans le journal d'erreurs du serveur. Pour activer le journal de débogage de WordPress, modifiez votre fichier wp-config.php comme suit:
Ensuite, essayez de reproduire le problème et vérifiez si des erreurs ont été enregistrées dans le fichier debug.log dans le répertoire /wp-content/. Si possible, partagez votre debug.log sur https://pastebin.com/ et fournissez-nous le lien. De plus, activez les informations de débogage en suivant les instructions sur http://wpml.org/faq/provide-debug-information-faster-support/.
Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous recommandons vivement de vérifier les problèmes connus sur https://wpml.org/known-issues/, 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 sur notre forum de support.
Problem: The client is experiencing an issue where dates on their Swiss French language version of the site do not translate correctly and revert back to English. This occurs because WordPress does not officially support the 'fr_CH' locale, causing a fallback to English for core date strings. Solution: To resolve this, we recommend either manually copying the official French WordPress translation files ('fr_FR.po' and 'fr_FR.mo'), renaming them to 'fr_CH.po' and 'fr_CH.mo', and uploading them to
wp-content/languages/
. After clearing all caches, WordPress will automatically load these files, and the
date_i18n()
function will render French month names correctly on the Swiss French site. Alternatively, using the Loco Translate plugin to create a French (Switzerland) 'fr_CH' translation for WordPress core (based on 'fr_FR') and translating the date strings there can achieve the same result without manual file handling and is safe across updates.
Please note that these files will not be removed by a WordPress update as the 'wp-content/languages/' directory is meant for custom and downloaded translation files and is not affected by core updates. However, since 'fr_CH' uses 'fr_FR' as a fallback, it won’t automatically receive updated translations when French translations are updated. If new strings are released, you would need to re-copy the updated 'fr_FR' files again.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem:
A bug triggered by specific plugins, producing a 500 error intermittently. Solution:
We have found out that it is an internal server error triggered by the fact that the .htaccess is altered and /en/ is the rewrite base:
This occurs primarily on a specific page and happens on every heartbeat. This happens when third-party plugins call the flush_rewrite_rules(true) function too often. This can change the rewrite rules in your .htaccess file and cause issues on your WordPress site. The full explanation can be found here: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/.
We suggest implementing the workaround on your staging site by adding the following function to the theme's functions.php file.
