Problema: Después de una edición masiva de contenido en inglés sin usar la opción 'Minor edit - don't update translation', WPML marcó cientos de traducciones como 'needs update'. Aunque las traducciones funcionan correctamente en el frontend, hay 234 traducciones marcadas incorrectamente y 26 realmente sin traducir. Solución: 1. Puedes optar por actualizar las traducciones marcadas como pendientes utilizando la interfaz de WPML -> Translation Dashboard, donde puedes filtrar el contenido por el estado de traducción. Este proceso puede ser extenso pero no complicado. 2. Otra opción es ir a WPML -> Translation Dashboard -> Última pestaña de trabajos de traducción y cancelar los trabajos si aparecen como pendientes. 3. Para eliminar los trabajos de traducción, puedes descargar el plugin necesario desde este enlace: https://we.tl/t-LuYooJwkCV 4. Para más detalles sobre troubleshooting, visita https://wpml.org/documentation/support/wpml-troubleshooting-options/
Si esta solución no resuelve tu problema o parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable 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.
Problem: You are trying to translate shortcode contents on your site using WPML, but the translations are not being applied. Specifically, shortcodes like 'tatsu_toggle' and 'tatsu_button' are not displaying the translated content on your German site, despite being visible and translatable in the WPML Translation Editor. Solution: The root of the issue is that the Tatsu page builder and other Brand Exponents products are not compatible with WPML. Therefore, they cannot be reliably translated using WPML’s Translation Editor. To resolve this, you should disable the WPML Translation Editor and translate your content manually using the page builder itself. You can follow this guide on how to switch to manual translation mode: Using Different Translation Editors for Different Pages. If you consider switching to a WPML-compatible builder in the future, you can check the full list of supported themes and plugins here: Theme Compatibility.
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 issue persists, please open a new support ticket at WPML Support Forum.
Problem: You are trying to set up automatic translations for posts on your site and encounter issues with 'CR English' and 'CA French' not supporting automatic translations, even after mapping them to known languages. Solution: For 'CR English', WPML supports mapping only to standard English for automatic translations. You should select 'Don't map this language' for custom variations like 'CR English' as they are intended for manual translation. If the content is the same across languages, consider duplicating the pages instead. More information on mapping custom languages can be found here: https://wpml.org/documentation/automatic-translation/using-automatic-translation-with-custom-languages/#mapping-a-custom-secondary-language-to-your-sites-default-language For 'CA French', the selected translation engine does not support this variant. You should map it to a supported language, such as standard French.
If this solution does not resolve your 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: WPML Support Forum.
Problem: Die französische und italienische Version der Website sind nicht erreichbar, während die deutsche und englische Version funktionieren. Es wurde ein Fehler im Zusammenhang mit der Übersetzung von Strings im Avada Theme und Fusion Builder festgestellt. Solution: Es wurde folgender Fehler festgestellt:
Fatal error: Uncaught ValueError: Unknown format specifier "," in C:\laragon\www\harter\wp-content\themes\Avada\includes\metaboxes\tabs\tab_page.php:69 Stack trace: #0 C:\laragon\www\harter\wp-content\themes\Avada\includes\metaboxes\tabs\tab_page.php(69): sprintf('Contr\xC3\xB4le la co...', ' Leave empty fo...')
Solche Probleme können auftreten, wenn ein String mit einem Platzhalter (wie "%s") nicht korrekt übersetzt wurde. 1. Überprüfen Sie unter WPML > String Translation nach dem String "Leave empty fo" und löschen Sie die entsprechenden Übersetzungen für Französisch und Italienisch. 2. Deaktivieren und reaktivieren Sie die WPML String Translation, um das Problem zu beheben.
Falls diese Lösung nicht relevant ist oder das Problem weiterhin besteht, empfehlen wir, die neuesten Versionen Ihrer Themes und Plugins zu überprüfen und die Seite bekannte Probleme zu besuchen. Sollte das Problem weiterhin bestehen, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Sie können dies über das WPML-Support-Forum tun.
Problema: El cliente no puede ver todas las imágenes en el apartado media de WordPress independientemente del idioma seleccionado, y no aparece el menú desplegable de idiomas en la ventana modal al intentar insertar imágenes desde el editor de páginas. Solución: Si estás experimentando este problema, te recomendamos seguir estos pasos: 1. Asegúrate de que el plugin WPML Media Translation esté configurado correctamente. Puedes encontrar una guía detallada aquí: https://wpml.org/es/documentation-2/guia-de-inicio/modulo-media-translation/ 2. Desde el panel de administración de WordPress, ve a Medios → Biblioteca. 3. En la parte superior de la página de la biblioteca de medios, selecciona 'Todos los idiomas' en el filtro de idioma. Si después de seguir estos pasos el problema persiste y no ves el menú desplegable de idiomas en la ventana modal, te recomendamos abrir un nuevo ticket de soporte para que podamos revisar tu configuración específica y proporcionar una solución adecuada. Además, te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: The client is attempting to export translations from a staging site to a live site using WPML but is only using the default WordPress importer, which does not support the necessary WPML multilingual fields. Solution: 1. Install and activate the required plugins on both sites, including WPML Multilingual CMS, WPML String Translation, WPML Export and Import, and a supported third-party export/import plugin like WP All Export Pro and WP All Import Pro. 2. Use the chosen export plugin to create an export file of your content from the staging site. 3. Import your multilingual content to the live site using your chosen import plugin. 4. Run WPML Export and Import on the live site by navigating to WPML → Export and Import and clicking the Run WPML Import button. If you're experiencing issues with translations not linking after following these steps, ensure that your export file includes the necessary WPML fields (_wpml_import_translation_group, _wpml_import_language_code, _wpml_import_source_language_code) and that these are correctly mapped during the import process. If problems persist, it may be due to using the default WordPress importer, which lacks support for necessary WPML data. In such cases, we recommend switching to a supported third-party tool.
This solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 you still need assistance, we highly recommend opening a new support ticket for personalized help.
Problem: You are trying to translate a string from a HubSpot Form on your website, but the string does not appear for translation, and the ID of the HubSpot form is missing. Solution: First, ensure that you have followed all the steps outlined in our documentation on integrating HubSpot with multilingual sites that use WPML. You can find the guide here: Integrating HubSpot with WPML. If after completing these steps the issue persists, we recommend providing us with temporary access (wp-admin and FTP) to a staging site where the problem can be replicated. This will allow us to investigate further.
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 at WPML support forum for further assistance.
Problem: El cliente está intentando importar propiedades usando un JSON con WP All Import que contiene campos en español e inglés. Aunque la importación en español funciona correctamente, la importación en inglés no muestra las traducciones adecuadamente, y no vincula las propiedades con sus correspondientes en español. Solution: Si estás experimentando problemas similares con la importación de JSON y la sincronización de traducciones en WPML, te recomendamos verificar que los archivos de importación sean idénticos y estén configurados correctamente para cada idioma. Asegúrate de que los campos personalizados estén bien definidos y que las configuraciones de WPML estén correctamente establecidas para manejar las traducciones. Si el problema persiste, podría ser útil revisar la estructura del JSON y asegurarse de que los campos de idioma y grupo de traducción estén correctamente asignados.
Es posible que esta solución sea irrelevante si ya está desactualizada o no aplica a tu caso. Te recomendamos abrir un nuevo ticket de soporte si necesitas asistencia adicional. También es altamente recomendable que revises los problemas conocidos, verifiques la versión de la solución permanente y confirmes que tienes instaladas las últimas versiones de los temas y plugins. Para más ayuda, visita nuestro foro de soporte.
Problem: The client is experiencing an issue where the 'widget_woocommerce_price_filter' duplicates when WPML String Translation is active, and attempts to delete the widget from WordPress settings result in it reappearing and duplicating multiple times. Solution: To address the widget duplication issue, follow these steps: 1. Navigate to Appearance → Widgets in your WordPress dashboard. 2. Find the existing 'WooCommerce Price Filter' widget in your sidebar or widget area and edit it. 3. In the widget settings, locate the language dropdown menu and set the widget to display only in your default language. 4. For each additional language you want the widget to appear in, add a new 'WooCommerce Price Filter' widget to the sidebar. 5. Assign each new widget instance to its respective language using the language dropdown. 6. If necessary, translate the widget strings by going to WPML → String Translation and searching for the widget's title or other text.
If these steps do not resolve the issue, we recommend checking WPML’s widget synchronization settings and the database for any duplicate widget records. Consider temporarily disabling WPML String Translation to see if the duplication persists, then re-enable it after cleaning up the widgets. Avoid repeating prior widget deletion and language assignment steps as these have not resolved the issue.
If the problem persists, it might be due to outdated solutions or specific circumstances not covered here. 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 necessary, please open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to display a language switcher on the menu using a shortcode. Solution: If you're experiencing this, we recommend you follow these steps: 1. Navigate to WPML → Languages. 2. Enable the option 'Custom Language Switchers'. 3. Use the shortcode
[wpml_language_selector_widget]
to display the language switcher wherever you need it. You can also customize the appearance and behavior of the shortcode switcher under WPML → Languages → Custom Language Switchers. For more details, visit Adding Language Switchers using PHP and Shortcodes.
If this solution does not apply to your case, or if it seems outdated, 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. We highly recommend opening a new support ticket if needed.
Problem: You are experiencing a discrepancy between the AI translation credits displayed on your WordPress site and those shown in your WPML account. On your site, it indicates 188,466 credits, which should cover translating 47,116 words, but your WPML account shows 0 credits available. Solution: You use a Pay-As-You-Go system for automatic translation, meaning you only pay for the credits you actually use. This month, you've already used 6,534 credits. There is a monthly safety limit set at approximately 195,000 credits to prevent unexpectedly high translation costs. The 'Pricing AI Translation' section on your site reflects the remaining credits before reaching this safety limit, helping you gauge if you have enough credits for planned translations. For more details on Pay-As-You-Go for Automatic Translation, please visit our terms and conditions.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: You are experiencing partial page translation issues because the WPML String Translation cannot write .mo files to the /var/www/content/languages folder, which is not writable. Additionally, the latest plugin update does not display all expected translation content. Solution: We recommend ensuring that the wp-content/languages folder exists and is writable, as this is crucial for storing .mo files for String Translation. If this folder is not writable, translations cannot be written or updated. Here are the steps you should follow: 1. Contact your hosting provider or the person managing your server to: - Create the wp-content/languages folder if it does not exist. - Ensure the folder is writable. - Prevent automated processes from removing or overwriting its contents. Once the folder is correctly configured, WPML should function as expected. For more details, visit https://wpml.org/faq/cannot-write-mo-files/.
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 at WPML support forum.
