Problem: You encountered a database error after scanning plugins and themes for new strings, indicating an issue with non UTF encoded characters in your database, specifically an emoji (🚀) in the content. Solution: We recommend two options to resolve this issue: Option 1: Remove the Emoji - Locate the page containing the text "Your website could be much faster if it could take advantage of our new features and enhancements. 🚀". - Delete the emoji from the content. - Resubmit the page for translation.
Option 2: Change Database Collation - Ensure you back up your website first. - Access your website's database via your hosting service panel. - Modify the collation of all database tables to one of the recommended settings, which can be found here: Recommended Collations and Charsets.
If these solutions do not apply to your case, or if they seem 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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing a loss of metadata, specifically translator comments from XLIFF files, when switching from the Advanced Translation Editor to the standard WordPress editor. This issue arises after clicking "Edit anyway", causing the translation to disconnect from the XLIFF file and resulting in the loss of all translator comments. Solution: Unfortunately, it is technically not possible with WPML to maintain the
<note>
elements from XLIFF files once you switch to the native WordPress editor. Custom development would be necessary to import these
<note>
elements into WordPress metadata or to make them visible in the block editor UI. We recommend setting the translation method on the original content to "WordPress Editor" to prevent overwriting manual translations when later using the WPML Translation Editor. For more details on setting the translation method, please visit: Using different translation editors for different pages.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problème : Vous souhaitez utiliser Elementor pour éditer les pages traduites dans différentes langues, mais WPML ouvre systématiquement son éditeur de traduction au lieu de permettre la modification directe avec Elementor. Solution : Nous vous recommandons d'activer l'option 'éditeur WordPress' pour les traductions, ce qui vous permettra de créer et de modifier les traductions avec Elementor au lieu de l'éditeur de traduction WPML. Vous pouvez trouver des instructions détaillées sur comment activer cet éditeur pour les traductions ici : https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/. Il est important de noter que vous ne pouvez pas passer d'une méthode de traduction à l'autre sans recréer la traduction. Assurez-vous de faire une sauvegarde complète de votre site avant de changer de mode.
Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous invitons à consulter les problèmes connus sur https://wpml.org/known-issues/, vérifier la version des correctifs permanents, et 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/support-en-francais/.
בעיה: יש לך אתר עם מוצרים באנגלית ואתה רוצה ליבא תרגומים של דפי המוצר מ-Google Sheets. פתרון: אנו ממליצים להשתמש בתוסף WPML Export Import. תוכל למצוא את המדריך הראשי שלנו כאן. בנוסף, עיין במדריך הזה להכנת קבצי היבוא: מדריך הכנת קבצי יבוא. הקפד שקבצי ה-CSV שלך יכילו את העמודות הבאות:
_wpml_import_translation_group
_wpml_import_language_code
_wpml_import_source_language_code
אם הפתרון הזה אינו רלוונטי, כי הוא מיושן או לא מתאים למקרה שלך, אנו ממליצים לפתוח כרטיס תמיכה חדש. כמו כן, מומלץ לבדוק בדף הבעיות הידועות כאן, לוודא את גרסת התיקון הקבוע, ולאשר שהתקנת את הגרסאות העדכניות ביותר של התבניות והתוספים.
Problem: The client has a staging site with languages configured for English and Icelandic. A button in the header links to the English site's shop, but when switching to Icelandic, the link incorrectly redirects to the production site's shop instead of the staging Icelandic version. Solution: We recommend checking if the button was added using the Theme's Customizer at Appearance → Customize → Header Builder. If this is the case, the URL and button text should be translatable via WPML > String Translation. It's important to ensure that these strings are registered and correctly translated to reflect the appropriate staging URLs for each language.
If this solution does not resolve the 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After migrating the server and restoring the backup using the all-in-one WP Migration plugin and re-registering WPML, the client encountered the 'WPML didn't manage to translate this page' problem and an installer support error. Solution: We recommend ensuring that the following domains are whitelisted on your server or firewall:
wpml.org
cdn.wpml.org
api.wpml.org
api.toolset.com
cloudfront.net
Additionally, check if a third-party plugin might be affecting this behavior by temporarily disabling all plugins except WPML and testing this using a default WordPress theme. Before performing any of these actions, please make sure to create a full backup of your site. If the issue persists, please check with your hosting provider to ensure that outgoing connections are not being blocked, which could be caused by firewall rules, security policies, or other server-side restrictions.
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 problem continues, please open a new support ticket at WPML support forum.
Problema: El cliente desea recuperar su dinero. Solución: Si estás experimentando esta situación, te recomendamos que sigas los pasos para solicitar un reembolso completo, siempre y cuando estés dentro de los 30 días posteriores a la compra. Puedes revisar los detalles y procedimientos en el siguiente enlace: Política de reembolso de WPML.
Si esta solución no es relevante para ti porque la información está desactualizada o simplemente no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. También recomendamos encarecidamente revisar los problemas conocidos en problemas conocidos de WPML, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.
Problem: The client is facing an issue where unique HubSpot forms added to contact pages in different languages are overwritten by WPML each time translations are updated. Solution: We recommend using the WordPress Editor to manage the content of the pages where unique forms are required, as the WPML Editor and the WordPress Editor are independent. Content created with one cannot be edited with the other. You should set the WordPress Editor on a page/post level basis, for a post type, or for the entire website, specifically for pages that need different designs or custom HTML per language. It is crucial to have a backup before testing any settings.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
