Problem: The client receives a warning message on their website indicating a problem with some tables in the database, accompanied by a WordPress database error stating 'Could not perform query because it contains invalid data.' Solution: If you're experiencing this issue, we recommend trying the following steps: 1. Click the small 'x' icon on the warning message to attempt to remove it. 2. Refresh the dashboard to see if the warning message still appears. If the message disappears, everything is likely in order. If the issue persists, please let us know so we can investigate further. For more detailed information, please refer to the following documentation: https://wpml.org/faq/how-to-deal-with-error-messages-about-a-broken-table-that-needs-fixing/#problem-with-some-tables-in-the-database
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 problem persists, do not hesitate to open a new support ticket for further assistance.
Problema: Estás intentando traducir el menú en el header de tu sitio web y al cambiar de idioma, el menú se desconfigura. Además, deseas saber cómo colocar el cambio de idioma y sus banderas en el header. Solución: 1. Primero, asegúrate de incrementar el límite de memoria de WordPress a un mínimo de 128Mb. Para esto, agrega el siguiente código en tu archivo wp-config.php, justo encima de la línea /* That's all, stop editing! Happy blogging. */:
Puedes verificar el límite de memoria en WPML -> Soporte. 2. Una vez incrementado el límite de memoria, sigue los pasos descritos en nuestra guía de compatibilidad con el tema Divi Builder para traducir correctamente el header. Encuentra la guía aquí: https://wpml.org/documentation/theme-compatibility/divi-builder/
Si la solución proporcionada no resuelve tu problema o parece no ser relevante debido a actualizaciones o diferencias en tu caso específico, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: Der Kunde verwendet den Classic Editor für die Übersetzung von Seiten und möchte nicht den Advanced Translation Editor (ATE) verwenden. Trotz Einstellung im WPML auf 'klassischer Editor' wird der ATE aufgezwungen, und es erscheint ständig eine Warnung, dass Änderungen verloren gehen könnten. Solution: Der Classic Editor wird von WPML als Legacy betrachtet, und es könnte sein, dass dieses Problem nicht behoben wird oder nur mit niedriger Priorität behandelt wird. Wir empfehlen, langfristig auf den ATE umzusteigen oder alternativ den Standard-WordPress-Editor zu verwenden.
Falls diese Lösung für Sie nicht relevant ist oder veraltet erscheint, empfehlen wir, einen neuen Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.
Problem: The client was unable to translate products using Elementor after installing the WPML plugin. Certain text within the Product Template was not appearing in the WPML translation editor.
Solution: 1. We advised the client to set the Woodmart Layouts to "Translatable" in WPML > Setting > Post Type Translation > Layouts (woodmart_layout) and then proceed to translate them. 2. For the untranslated string in the footer bar, it should be translated using WPML > String Translation. If the string is not visible there, the client should follow the guide to find and register the string for translation: finding strings that don't appear on the string translation page, and ensure the correct source language is set: how to change the source language of strings. 3. We recommended changing the WPML settings from "Translatable - use translation if available or fallback to default language" to "Translatable only show translated items" for both products and templates to ensure proper functionality. 4. We installed an update for the WooCommerce Multilingual addon to address compatibility issues, detailed here: WooCommerce Multilingual 5.5.0.
If this solution does not resolve your issue or seems outdated, we 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.
Problem: The client is setting up a multidomain page using WPML and wants different domains for different English locales (en-US, en-IE, en-GB). However, they encounter an issue where they cannot add a custom language with the locale en_US, as it reports 'The Language name already exists.' Solution: If you're experiencing this issue, we recommend the following steps to resolve it: 1. Activate the pre-configured language: Go to WPML → Languages and activate English. 2. Change its locale: Edit the English language and change its locale to something else (e.g., en_EN or a custom value that fits your needs). 3. Save the changes. 4. Now add your custom language: Once the default locale en_US is free, you can create your custom language and assign en_US to it. For more detailed instructions on adding custom languages, please visit Adding Custom Languages.
Please note that this solution might be irrelevant if it's 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.
