The client is using the Advanced Translation Editor in WPML with an Elementor Widget from Brainstorm Force Ultimate Addons. They are facing an issue where line breaks (
<br />
) entered in a table cell are not displayed in the Spanish translation, although they work correctly in German, English, and French translations.
Solution:
We recommended the client to deactivate the 'Bigger Segments Switch' in WPML's Advanced Translation Editor settings, which resolved the issue of line breaks not appearing in the Spanish translation.
Additionally, we advised the client to ensure all plugins, including Elementor and WPML, are updated to the latest versions after taking a full site backup.
For more details on related issues, visit the following errata pages:
If this solution does not apply or is outdated, we recommend opening a new support ticket. We also highly suggest 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 contact us through the WPML support forum.
Problem: Si estás intentando traducir una cadena con el editor de texto de Elementor al español y notas que el carácter ':' no se muestra en la traducción, además de que las palabras 'Palabra' y 'Entrada de glosario' aparecen pegadas, este problema es específico al usar DeepL en el Editor de Traducción Avanzada de WPML. Se activa cuando la primera etiqueta de glosario es de tipo 'name' y la segunda es 'general term', eliminando el dos puntos entre ellas. Solution: Para resolver este problema, te recomendamos seguir utilizando DeepL para traducir a otros idiomas, pero cambiar a Google o Microsoft Translation Engine para las traducciones al español. Lamentablemente, esta limitación está fuera de nuestro control.
Si esta solución no es relevante porque está desactualizada o no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. También te recomendamos revisar los problemas conocidos, 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.
Problem: The client is facing an issue where the anchor part of internal links in a translated template remains untranslated, causing the anchor not to be found. Solution: We recommend manually updating the button link by following these steps: 1. Add the following XML in WPML >> Settings > Custom XML Configuration section:
2. Make a small change in the default language page to reload the translation. 3. Open the translated page and search for the URL and add the translation as needed.
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 the problem persists, please open a new support ticket.
Problem: If you're experiencing an issue where the 'translation management' entry is missing from the WPML menu after the latest update, you are not alone. Solution: We recommend taking a backup of your site first. Then, please follow the workaround provided in our errata. You can find the detailed steps here: https://wpml.org/errata/admins-cannot-access-wpml-translation-management/.
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.
Problem: The client was trying to import 1710 glossary entries from one site to another, where 100 entries already existed. After the import, the new entries were not visible, even though the import process indicated 'Glossary successfully imported'. Solution: We recommended the client to remove all glossary entries starting with a specific letter (e.g., 'A') and then attempt to reimport the glossary entries. This approach was tested and confirmed to show the newly imported entries correctly.
If you're experiencing similar issues, we recommend trying this method. However, 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 at WPML support forum.
Problem: After moving the site from staging to live, the WPML Menu Synchronization still shows old staging site domain names in custom links, despite them being correct in the menu itself. Solution: 1. We identified that the issue arises because WPML does not automatically update absolute links/custom URLs in the String Translation. These are loaded from .mo files located in wp-content/languages/wpml. 2. Since .mo files are compiled and cannot be edited directly, we recommend checking the corresponding .po files that might contain the outdated URLs. 3. Alternatively, you can try the following steps: - Navigate to WPML > Support > Troubleshooting. - Use the option to clean up the Strings table and regenerate the .mo files. This might help update your .mo files to reflect the current strings. 4. If the issue persists, we may need a full copy of your site or at least staging access to further diagnose the problem.
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 continues, please open a new support ticket with us for further assistance.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client's plugin developer is encountering an issue with the
flush_rewrite_rules()
function when deactivating a plugin, which conflicts with WPML, leading to a 500 error. The developer has temporarily commented out this function in the plugin's deactivation hook to avoid the error. Solution: We recommend that the plugin developer joins the WPML Go Global Program to collaborate directly with our team for a compatible solution. Details about the program can be found here.
If this solution is outdated or does not apply to your case, please 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. If issues persist, we highly recommend opening a new support ticket here.
Problem: The client reported issues with images being duplicated in the media library, specifically mentioning images named 'maxresdefault' that seemed to be auto-generated. The client was concerned that WPML might be creating these files. Solution: We clarified that WPML does not directly create image files; it only duplicates existing images in the database when translating them to other languages. The images in question were uploaded by a user and were start images from YouTube videos, likely auto-generated by the Elementor plugin, not WPML. We recommended verifying the image author in the media library and checking if Elementor or another third-party plugin might be generating these images.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. It's also advisable to check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure 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: The client reported an issue where HTML paragraph breaks were not being recognized in the Translation Editor, causing all text to appear in one block without proper separation in translations. Solution: We recommended switching to the older version of the Advanced Translation Editor where this issue might not occur. Detailed instructions for this process can be found here: https://wpml.org/errata/html-attributes-not-available-for-translation-in-advanced-translation-editor/
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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is trying to translate strings in the Plugin RegistrationMagic and RegistrationMagic Pro, which are not WPML ready. Despite changing a string, the changes do not appear unless 'Mark string for Translation' is activated in String Translation. Solution: We recommend contacting the plugin authors and suggesting they join our Go Global program where our Compatibility developers will assist in making their product fully compatible with WPML at no cost. This issue arises because the plugin is not written in an 'internationalized' way, which is necessary for compatibility with WPML. For more details on internationalization, you can visit WordPress internationalization guidelines.
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 issues persist, please open a new support ticket.
