Problem: Mit dem neuen Übersetzungstool gehen die Formatierungen verloren, wenn von Englisch auf Deutsch übersetzt wird. Vor der Aktualisierung des Advanced Translation Editor hat die Formatierung problemlos funktioniert. Solution: Es handelt sich um ein bekanntes Problem, das hier beschrieben wird: https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/ Wir empfehlen, die Option "I prefer bigger segments" zu deaktivieren und einen neuen Übersetzungsauftrag anzulegen, um die Änderungen im Übersetzungseditor zu sehen. Nachdem die Übersetzung erneut übernommen wurde, sollte das Problem behoben sein.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) 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.
Problem: The client is unable to view content in the WPML >> String Translation page, which appears empty. Additionally, when editing a page in both languages, changes made in the default language do not save correctly, causing the translated page to revert to the original. Solution: First, ensure you have a backup of your site. Then, follow the workaround provided in the WPML errata page to address missing database tables related to string translations. You can find the necessary steps here: Missing _icl_strings and _icl_string_translations Data Tables. If the issue persists or if the solution provided here becomes 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.
Problem: If you're trying to translate a global element created with Bricks Builder and are encountering issues where the translation does not appear correctly on the frontend.
Solution: We recommend following these steps: 1. Apply the fix from the WPML errata page for Bricks Builder issues. You can find it here: Bricks translated content not showing on frontend. 2. Edit the home page in the default language using Bricks Builder and make necessary text changes. 3. Save your changes and exit to WordPress. 4. Update the translations in the Advanced Translation Editor (ATE), ensuring all text is present and translated. 5. If some elements still don't display correctly, go to WPML -> String Translation. Search for the strings that are not showing correctly, correct their language if necessary, and translate them. For guidance on changing the language of a string, visit: How to change the source language of strings. 6. Note that if you are using plugins like 'Max Addons for Bricks' which are not compatible with WPML, you might need to manually translate some elements using the WP Editor. For more information on using different translation editors, see: Using different translation editors for different pages.
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.
Problem: You are experiencing a fatal error on the cart page and other pages when WPML String Translation is activated in the Arabic version. Solution: We have removed the incorrect string translations which resolved the issue. Please check if the error persists. Additionally, we recommend reviewing the related known issue documented here: PHP 8 PHP Fatal Error Uncaught ValueError: Unknown format specifier in.
If this solution does not apply to your case, or if it seems outdated, 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 through the WPML support forum.
Problem: If you're experiencing issues with currency switching on your site when not logged in, and your site uses WCML without WPML, along with multi-currency settings similar to those shown here: https://www.screencast.com/t/hadJtfwc1E, it might be related to WP-Rocket caching. Solution: We recommend following the workaround provided in our errata page for issues with WP-Rocket where currency does not change on the products page. You can find the necessary steps here: https://wpml.org/errata/wp-rocket-currency-not-changing-in-products-page/.
If this solution does not resolve your issue or seems irrelevant due to being 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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: Wenn Sie eine Seite, die in Deutsch erstellt wurde, automatisch in andere Sprachen übersetzen und dabei feststellen, dass eine Gruppe von Elementor-Form-Checkboxen als ein einziger Checkbox übersetzt wird statt mehrerer Checkboxen, liegt das an einem bekannten Problem mit dem neuen Layout des Erweiterten Übersetzungseditors. Solution: Eine aktuelle Lösung finden Sie unter https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/. Nachdem Sie die Einstellung angepasst haben, müssen Sie einen neuen Job erstellen oder das originale Template editieren, erneut speichern und erst dann den Übersetzungseditor öffnen. Nun sollten die Segmente korrekt erscheinen und sich speichern lassen.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) 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 unter https://wpml.org/de/forums/forum/support-in-german/.
Problem: Al intentar traducir un formulario de Avada utilizando el editor de WordPress, aparece un error de 'código de contenido no válido'. Si se utiliza el editor de WPML, se muestra un error indicando problemas con algunas tablas en la base de datos, acompañado de un mensaje que sugiere contactar al soporte de WPML para resolverlo. Solution: Para resolver estos problemas, seguimos los siguientes pasos: 1. Aplicar las instrucciones disponibles en https://wpml.org/errata/missing-_icl_strings-_icl_string_translations-data-tables/ 2. Seleccionar nuestro editor de traducción antes de abrir las traducciones en inglés (EN) y alemán (DE). Esto permitió actualizar y publicar la traducción en inglés sin problemas, y luego completar añadiendo los textos en español (ES) en las traducciones faltantes. 3. Asegurarse que los formularios estén activados en los demás idiomas.
Si esta solución no resuelve tu problema, o si parece desactualizada o no aplicable a tu caso, 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 los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/soporte-en-espanol/.
Problem: You are experiencing an issue with the String Translation table on your site, which could potentially become a critical issue in the future. Solution: We recommend following the steps outlined in the WPML errata page to fix issues related to missing String Translation tables. You can find the detailed instructions here: Missing _icl_strings and _icl_string_translations Data Tables. After applying these steps, please check your site to confirm that the issue is resolved.
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 the problem persists, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client reported that after translating their site from English to Russian, all Russian translations were displayed as question marks across the site. Solution: We identified that the issue was due to the database encoding not being set to UTF-8. We recommended the following steps: 1. Adjust the database tables to use UTF-8 encoding by executing the following SQL commands:
ALTER TABLE $table DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci
ALTER TABLE $table CHANGE $field_name $field_name $field_type CHARACTER SET utf8 COLLATE utf8_bin
2. Add the following line to the wp-config.php file to ensure the database uses UTF-8 charset:
define('DB_CHARSET', 'utf8');
3. Clear the WPML cache and fix WPML tables collation via WPML->Support->Troubleshooting. 4. If the issue persists, deactivate WPML temporarily and test creating a new page with Cyrillic letters. 5. For existing pages, re-save the translations or edit and update the pages without making changes to force a refresh of the content.
If these steps do not resolve the issue or if the solution 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.
