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.
Problema: El cliente ha creado un template en Divi como encabezado global, que incluye un row que debe mostrarse solo en ciertas páginas. Mientras que en español funciona correctamente, no logra que los condicionales de página funcionen en catalán e inglés, a pesar de que los condicionales de categorías de producto sí funcionan en estos idiomas. Solución: Si estás experimentando este problema, primero asegúrate de traducir la plantilla desde WPML --> Administración de traducción. Si el problema persiste, te recomendamos aplicar la solución que se propone en esta errata: https://wpml.org/errata/divi-theme-conditions-for-categories-are-not-applied-to-translations/
Si esta solución no resuelve tu problema o parece no ser relevante debido a que está desactualizada o no se ajusta a tu caso, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente 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 más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: If you're experiencing issues with the WPML translation editor not recognizing line breaks in posts created through the Classic Editor, where instead of seeing different translation zones for each paragraph, you see one big paragraph, we can help. Solution: We are currently working on a permanent fix for this issue in future releases. In the meantime, to address this for previously created content, you need to delete the existing translation and recreate it. Here’s how you can do it: 1. Ensure you have a full website backup. 2. Navigate to your Pages or Posts tab. 3. Change the language in the topbar by clicking on the flag and selecting a secondary language. 4. Find the translation, send it to the trash, and then permanently delete it from the trash can. By following these steps, when you create a new translation, it should adhere to the new settings and resolve the issue. If this solution does not resolve the issue, please visit this 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 problem persists, please open a new support ticket.
Problem: When using SEOPress plugin with WPML, the product archive slugs are not correctly translated in the XML sitemaps generated by SEOPress.
Solution: We have acknowledged the issue with SEO Press not correctly handling translated slugs in sitemaps. We recommend checking the following errata for a workaround and subscribing to the comments on our errata page for this specific issue to stay updated on future fixes: https://wpml.org/errata/seopress-product-archive-slug-not-translated-in-sitemaps/.
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 with us for further assistance.
Problem:
The client is experiencing 500 Internal Server Errors on translation pages (/ru and /en) when WPML Multilingual CMS is active. The issue persists despite disabling other plugins, updating permalinks, and checking .htaccess configurations.
Problem: You are trying to translate content generated by the 'Divi Modules Table Maker' plugin using WPML. Previously, you used an XML config to enable translation, which worked on an older site but has stopped functioning on a new site and a dev/testing environment. The content includes line breaks that are not being preserved in translation. Solution: This issue appears to be related to a known problem where line breaks are ignored when using the Advanced Translation Editor. Here’s what we recommend you try: - Look at the top right corner of the Translation Editor. - Click on the gear icon. - Disable the option 'I prefer larger segments'. - Close the editor and resend the page for translation via WPML > Translation Management.
If this solution does not resolve your issue, or if it 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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues where the formatting, including 'enters'/white spaces, is missing on your translated pages. Additionally, shortcodes that work on the original version of your site do not function on the translated pages. Solution: We recommend trying the workaround provided in the WPML errata for issues related to line breaks being ignored in the Advanced Translation Editor. You can find the specific steps and more details here: WPML Errata on Line Breaks. 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 WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Additionally, if you need further assistance, please open a new support ticket at WPML Support Forum.
Problem: The client is facing an issue where custom links in the menu are not translated correctly from German to English using ATE. The links appear as /?product_cat=vehicle-type-car instead of the expected translated format like https://www.valtron.de/en/c/rear-view-cameras/f/vehicle-type-car/.
Solution: We recommend adding the following code to the end of your
functions.php
file to address the issue:
// WPML Workaround for compsupp-7532
function wpml_compsupp7532_add_custom_blacklist_requests( $blacklist, $sitepress ) {
// Add your custom request to the blacklist array
// We can hardcode URL's, like:
//$blacklist[] = "c/rear-view-cameras/f/vehicle-type-truck";
// Or use REGEX. This regex should match slugs like "c/(any slug here)/f/(any slug here)" - we may need to adapt it if needed
$blacklist[] = '/^c\/[^\/]+\/f\/[^\/]+\/?$/';
return $blacklist;
}
add_filter( 'wpml_sl_blacklist_requests', 'wpml_compsupp7532_add_custom_blacklist_requests', 10, 2 );
After adding the code, save the file, make a small modification to the block content, and save. Then, update the translations. You may need to re-translate the links.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that after translating text from English to Dutch using the Advanced Translation Editor, the paragraphs were not displayed in the Dutch translation. Solution: We first asked the client how they were adding paragraphs to the original content and confirmed whether they were using the Advanced Translation Editor. We then directed the client to review our errata documentation and try a workaround for issues related to line breaks being ignored in the Advanced Translation Editor. The documentation can be found here: https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/. If this solution does not resolve the issue or seems outdated, we recommend opening a new support ticket. We also advise 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: Sie arbeiten an der Website und versuchen, die Funktion 'Bigger Segments' ein- und auszuschalten, was zu unerwünschten Zeilenumbrüchen führt. Sie möchten wissen, wie Sie diese Zeilenumbrüche beheben können und ob die Funktion 'Bigger Segments' die Zeilenumbrüche beeinflusst. Solution: Wir arbeiten derzeit an einer dauerhaften Lösung, die in zukünftigen Versionen von WPML implementiert wird. Als temporäre Lösung empfehlen wir Ihnen, die Seiten, bei denen dieses Problem auftritt, manuell zu übersetzen. Sie können den Inhalt der Originalseite kopieren und die Texte dann im Seiteneditor ersetzen. Weitere Details zur manuellen Übersetzung finden Sie hier: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/
Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen Ihnen 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: https://wpml.org/de/forums/forum/support-in-german/
