All issues in which we had to help clients with Elementor Custom Widgets either because they wanted to create one, or (more likely) when related to themes that have Elementor Custom Widgets integrated. Add whether you helped, sent to docs or escalated.
Problema: Il cliente ha riscontrato un problema con la traduzione delle pagine e un errore PHP quando visualizza i prodotti in francese. L'errore è causato da template/widget di Ecomus che ricevono dati non validi. Soluzione: Abbiamo richiesto l'accesso temporaneo (wp-admin e FTP) per esaminare meglio il problema. È importante effettuare un backup prima di fornire l'accesso. Inoltre, abbiamo suggerito di aprire il template nella lingua tradotta, cliccare su Modifica e verificare che tutte le impostazioni siano configurate correttamente.
Se la soluzione proposta risulta non pertinente, perché potrebbe essere datata o non applicabile al tuo caso, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di consultare la pagina dei problemi noti, verificare la versione della correzione permanente e confermare di avere installato le ultime versioni di temi e plugin. Per assistenza ulteriore, visita il forum di supporto WPML.
Problem: Der Kunde versucht, JKit Elementor Widgets mit WPML zu übersetzen, aber die Texte erscheinen nicht in der WPML String Translation. Es gibt auch Probleme mit der Übersetzung von internen Links und der Anzeige von Button-Texten in der Übersetzung. Solution: Wir haben festgestellt, dass die Elementor-Inhalte in der aktuellen Version von WPML nicht mehr unter WPML > Stringübersetzung angezeigt werden, sondern nur mit dem WPML-Übersetzungseditor oder alternativ mit dem WordPress-Editor übersetzt werden sollten. Jedes benutzerdefinierte Elementor-Widget, wie von Jeg Kit for Elementor, benötigt eine XML-Konfiguration, damit es mit dem WPML-Übersetzungseditor übersetzt werden kann. Der Theme-Autor sollte diese Konfiguration in der Datei wpml-config.xml im Stammverzeichnis des Themes oder Plugins erstellen. Anleitung dazu finden Sie hier: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/ Für die JKit Icon Box und andere Widgets haben wir eine benutzerdefinierte XML-Konfiguration erstellt und unter WPML > Einstellungen > Benutzerdefinierte XML-Konfiguration gespeichert. Nachdem Sie die Widgets auf dem originalen Inhalt in Elementor editiert und die Seiten erneut gespeichert haben, aktualisieren Sie die Übersetzung. Die internen Links müssen nun nicht mehr übersetzt werden.
Diese Lösung könnte veraltet sein oder nicht auf Ihren Fall zutreffen. Wir empfehlen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Wenn das Problem weiterhin besteht, öffnen Sie bitte ein neues Support-Ticket im WPML-Support-Forum.
Problem: El cliente intentaba traducir los testimonios en su sitio web utilizando WPML, pero a pesar de que todos los elementos estaban marcados para traducción, los testimonios no se traducían y no aparecían en el sitio. Solution: 1. **Aumentar el Límite de Memoria de WordPress:** Añadir las siguientes líneas al archivo
wp-config.php
, justo antes de la línea
/* That's all, stop editing! Happy publishing. */
:
define('WP_MEMORY_LIMIT', '256M');
define('WP_MAX_MEMORY_LIMIT', '256M');
2. **Configurar la Traducción de los Testimonios y Taxonomías en WPML:** - Ajustar la configuración de los Testimonios y las Taxonomías de los testimonios en WPML -> Configuración -> Traducción de Tipos de Entrada y Traducción de Taxonomías. - Agregar y traducir una taxonomía de tipo 'Conjunto de testimonio' llamada 'Inicio'. - Publicar los testimonios en inglés que estaban como borradores. - Registrar el elemento de los testimonios siguiendo los pasos descritos en esta guía: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/ - Editar la página de Inicio y modificar el selector de los testimonios para que mostrara los que pertenecen a la categoría 'Inicio'.
Si la solución proporcionada no resuelve tu problema o parece no ser relevante debido a actualizaciones o diferencias en tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable 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 temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: The client is trying to ensure that links on their sub-language website automatically include the URL for the sub-language version. They are using the Themex Pro Addon for the Consalt Theme, which lacks a wpml-config.xml file for making its widgets translatable with WPML. Specifically, the Team widget on the homepage does not automatically include the URL for the sub-language version, causing redirection to the main language version.
Solution: We modified the existing WPML custom XML configuration for the Team widget to include link fields, ensuring they are translatable. After updating the configuration, we edited the Title Link and Social Icon Link of the Team widget on the original homepage, saved the page, and updated the translation. This resolved the issue. We recommend informing the theme author about the need for a proper WPML configuration and suggest using the Multilingual Tools plugin for creating extensive configurations.
Additionally, some custom fields on the site were incorrectly set to be translatable. We advised checking these settings under WPML > Settings > Custom Field Translation and adjusting them as necessary.
If this solution does not apply to your case, or if it seems outdated, please check the related 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 at WPML support forum.
Problem: You are using WPML to manage translations on your site and have encountered an issue where the internal button link does not update in the translated versions of your posts. You have changed the internal button link on the original website, but it remains unchanged in the translations. Solution: We recommend adjusting the link translations within the Advanced Translation Editor. If the URLs have been previously translated using the WPML Translation Editor, the translations are saved in the translation memory, requiring you to overwrite these entries.
Please note that this solution might not be relevant 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 at WPML support forum for further assistance.
Problem: You are trying to translate slides made with the Prime Slider plugin, call to action buttons, and Form 10Web.io widgets on your site built with Elementor and 10WEB.io using WPML, but they were not translated automatically. Solution: For the Prime Slider plugin, which is not officially compatible with WPML, we recommend adding a custom XML configuration to ensure translations. Here are the steps: 1. Navigate to WPML > Settings > Custom XML Configuration. 2. Add the following code:
3. Save the changes. 4. Return to your page, make a minor edit, and save again. 5. Re-translate the page, and the content should now be correctly translated.
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 further assistance is needed, please open a new support ticket at WPML support forum.
