Inicio›Soporte›Etiqueta del tema: Elementor Custom Widgets
Elementor Custom Widgets
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.
Проблема: Клиент не понимал, как перевести блоки, созданные с помощью Elementor, а также как переводить меню и элементы в футере. Решение: 1. Обновите плагин WPML до последней версии (на момент ответа 4.6.9) и его дополнения, чтобы получить последние исправления и улучшения. Проверьте последние версии в разделе «Моя учетная запись -> Загрузки» и следуйте инструкциям по обновлению здесь: http://wpml.org/faq/install-wpml/. 2. Ознакомьтесь с инструкцией по переводу Elementor с WPML: https://wpml.org/documentation/plugins-compatibility/elementor/. 3. Если вы реализовали пользовательские блоки на Elementor, сделайте их переводимыми, следуя документации:
Перед внесением изменений не забудьте сделать резервную копию базы данных.
Если решение не актуально или не подходит для вашего случая, мы рекомендуем открыть новый тикет поддержки. Также настоятельно рекомендуем проверить известные проблемы, убедиться в версии постоянного исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
Problem: The client was unable to translate the icon boxes on their website using WPML with the Consult theme. The text from the icon boxes did not appear in the translation editor, and the source language (English) was displayed instead.
Solution: We recommended adding a custom XML configuration to the WPML settings to ensure that the Elementor widgets used by the Consult theme are translatable. Here is the custom XML configuration that we provided:
We also advised the client to complete any ongoing translations for the English language, add the custom XML to the WPML settings, and then make a minor change in the default language to trigger an update synchronization.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
Problema: Se stai riscontrando problemi con la traduzione manuale di pagine create con Elementor, dove l'editor avanzato di WPML mostra solo alcuni elementi e altri non vengono riconosciuti, il problema potrebbe essere dovuto a widget custom del tema che non sono ottimizzati per la compatibilità con l'editor avanzato di WPML. Soluzione: Per risolvere questo problema, i widget custom di Elementor devono essere registrati seguendo la procedura indicata nella nostra documentazione: Registrare i widget custom di Elementor per la traduzione. Inoltre, puoi suggerire all'autore del tema di contattarci attraverso il nostro programma 'Go Global' se è interessato a rendere il tema pienamente compatibile con WPML: Programma Go Global. Tieni presente che questa soluzione potrebbe non essere più rilevante se è passato molto tempo o potrebbe non essere adatta al tuo caso specifico. Se dopo aver seguito questi passaggi il problema persiste, ti consigliamo di verificare i problemi noti correlati, controllare la versione della soluzione permanente e assicurarti di avere installato le ultime versioni di temi e plugin. Se necessario, non esitare a aprire un nuovo ticket di supporto.
Problem: If you're experiencing issues with automatic translation on your website, where only the navigation menu is affected when switching languages and not the pages, it could be due to custom Elementor widgets that WPML is not recognizing.
Solution: We recommend checking if there are custom widgets on your pages that might not be registered with WPML for translation. These custom widgets could be added by plugins such as "Mascot Core", "Mascot Core - Ecoife WP", or "Qi Addons For Elementor". To resolve this, you need to help WPML recognize these custom widgets by writing a few lines of code. You can find guidance on how to register these widgets for translation in our documentation:
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If after checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins, the problem persists, we highly recommend opening a new support ticket. For further assistance, please visit our support forum.
Problème :
Si vous constatez que les pages, articles et portfolios ne sont pas entièrement traduits après avoir lancé les traductions, et en particulier que les éléments d'Elementor ne sont pas traduits, suivez les étapes ci-dessous pour résoudre le problème.
Solution :
1. Augmentez la mémoire PHP allouée à au moins 128M, idéalement 256M. Pour ce faire :
- Connectez-vous à votre serveur via FTP et ouvrez le fichier
wp-config.php
situé à la racine de votre installation WordPress.
- Ajoutez les lignes suivantes juste avant
2. Après avoir augmenté la mémoire, effectuez une petite modification sur la version originale (par exemple, ajoutez un espace à la fin du titre ou d'un paragraphe et sauvegardez les changements), puis ouvrez à nouveau la traduction pour voir si de nouveaux segments apparaissent.
3. Si vous utilisez des templates Elementor, assurez-vous de les traduire également. Pour plus d'informations, consultez la documentation sur la traduction des templates Elementor.
4. Si vous utilisez des widgets personnalisés, comme le widget titre de Thorsten, vous devez les enregistrer pour la traduction. Voici les étapes à suivre :
- Allez dans "WPML > Paramètres > Configuration XML personnalisée" et ajoutez le code suivant :
Problem: The client is unable to translate the link in a custom Elementor widget button even after following the WPML documentation on how to register page builder widgets for translation. Solution: 1. We recommend checking if the method for translating URLs, shortcodes, and HTML attributes using the Advanced Translation Editor is helpful. You can find the documentation here: https://wpml.org/faq/how-to-translate-urls-shortcodes-and-html-attributes-using-the-advanced-translation-editor/ 2. If the issue persists, it may be necessary to review the XML code that was added to register the widget for translation. 3. Additionally, we found that the button in question is used in the header for the partner page and is linking to itself. We suggest changing the link to point to a different page or avoiding linking to the same page where the button is used.
Problem: The client is experiencing issues with incorrect strings showing in the Rankmath meta information of their multisite WordPress installation. Solution: 1. We resolved the issue on the main site by translating the meta description using the WPML Translation Editor. 2. We translated global metadata through WPML > String Translation. 3. In some instances, we navigated to WPML > String Translation > Translate texts in admin screens, searched for the site title and tagline, added them to WPML String Translation, and then translated them. 4. We reminded the client that WPML needs to be installed and activated on each subsite of a multisite network, as content is handled independently and cannot be connected across subsites. 5. We requested network access to the multisite to assist further with the /journal/ subsite issues. 6. We provided links to guides that could help with understanding the integration of Rankmath and WPML for multilingual SEO:
Problem: The client reported several issues with their website translation into Simplified Chinese: a) Limited text translation, b) An unwanted section appearing on the Chinese version of the Home Page.
Solution: We addressed the issue of limited text translation on the homepage. The problem was due to custom Elementor widgets used by the theme CarDealer that were not registered for translation. We provided a custom XML configuration to register the fields of the 'Feature Box' widget for translation:
After adding the code to WPML > Settings > Custom XML Configuration tab, we instructed the client to update the homepage in English and re-translate it to see the content in the 'Feature Box' translated.
We also recommended that the client contact the theme author to request the registration of all Elementor widgets for translation, as currently, only some theme options and post types are registered. For further guidance, we provided links to our documentation:
Please note that this solution might be outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking related 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.
