Problem: If you're using the Uncode Theme and experiencing issues where your translated pages include buttons with internal links not pointing to the correct target language, this might be due to corrupted string packages. This problem was noted especially after editing and saving the original homepage. Solution: First, ensure that all your themes and plugins, including Uncode and WooCommerce, are updated to their latest versions. Then, follow these steps: 1. Navigate to WPML > Packages and delete the existing package for the homepage, which might be corrupted. 2. Edit and save the original homepage to allow WPML to create a new, hopefully uncorrupted, string package. 3. Reapply the translations for the homepage. 4. Repeat the process for any other affected products. If you continue to face issues, it might be helpful to switch the translation method to "WPML Translation Editor" from the WordPress Editor and reapply the translations manually.
If these steps do not resolve the issue or if the solution 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. Should problems persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problema: Hai tradotto delle stringhe nel plugin WooCommerce Custom Product Addon, ma la traduzione non appare nel front end. Soluzione: Assicurati che il testo sorgente in inglese corrisponda esattamente a quello nelle impostazioni del plugin. Se non riesci ad attivare il plugin per testare, crea una versione di staging del sito web con lo stesso utente condiviso e informaci quando hai terminato, così possiamo effettuare ulteriori test. Inoltre, puoi provare a tradurre direttamente dal plugin: apri il modulo nella traduzione, clicca su opzioni e traduci. Guarda lo screenshot fornito per assistenza.
Se questa soluzione non risolve il problema o sembra non essere più rilevante, ti consigliamo di verificare i problemi noti e di assicurarti di avere installato le versioni più recenti dei temi e dei plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.
Problem: You are using WPML to translate your website content with a custom WordPress theme, Kreativa, which uses iMaginem Page Builder. However, only the menu and header are being translated, and the main content remains untranslated because iMaginem Page Builder is not supported by WPML. Solution: If you're experiencing this issue, we recommend checking if your page builder is listed among those supported by WPML here: https://wpml.org/documentation/translating-your-contents/page-builders/. If iMaginem Page Builder is not listed, you will need to rebuild the translated pages from scratch using the "WordPress Editor" option to create translations with the page builder. For more details, visit: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/. Alternatively, contacting iMaginem's support to inquire about possible workarounds could be beneficial, as WPML requires the content to be prepared for translation.
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 open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with custom CSS in Elementor not displaying correctly after translating your site using WPML, where the CSS attribute content remains unchanged across translations. Solution: 1. We recommend setting up a minimal installation of WordPress, WPML, and all necessary WPML add-ons, and themes to replicate the issue. This helps in identifying and solving the problem more efficiently. 2. If the issue persists, you can manually edit the translated page and adjust the CSS directly. Access the second language page from Pages > All and click 'edit with Elementor', or go to the page in the frontend and click 'Edit with Elementor' in the top bar. 3. Alternatively, remove your custom CSS from Elementor and add it to your theme via Appearance > Customize > Additional CSS. 4. Follow the errata and workarounds provided by WPML for known issues with Elementor and custom CSS at https://wpml.org/errata/elementor-custom-page-css-not-copied-correctly-in-translations/.
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 issue persists, please open a new support ticket at our support forum.
Problem: The client is experiencing an issue where the stat chart is not displaying on the French version of their site after updating the Houzez theme. This is a recurring problem that seems to arise with updates to the Houzez theme. Solution: 1. We recommended installing the latest version of the Houzez Theme on a test site to replicate the issue and confirm if it's a general compatibility issue between WPML and Houzez. Documentation on theme compatibility 2. We are communicating with the Houzez author to address and resolve these compatibility issues. In the meantime, we are applying a temporary fix to the client's site. 3. We are conducting tests ourselves to prevent any miscommunication and ensure a thorough understanding of the issue.
Please note that this solution might be 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.
Problem: You are using WooCommerce Add-ons with WPML string translation to display translated text on the frontend product page, but the original untranslated text still appears even after clearing both the site cache and the WPML cache. Solution: We investigated this issue and found no bug with WPML and the WooCommerce Product Add-Ons plugin. To resolve the issue, follow these steps: 1. Ensure all product categories are translated from the original language into the target language in WPML -> Taxonomy Translation. 2. Create global add-ons for the original language and add only the categories in that language. 3. In WPML -> Strings Translation, translate the add-ons labels into the target language. Following this workflow should resolve the display issues on the frontend.
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.
Problem: Der Kunde hatte Schwierigkeiten, die internen Links auf der Startseite seiner Website zu übersetzen, die mit Elementor Buttons erstellt wurden. Trotz mehrmaliger Versuche, die Option 'Linkziele übersetzen' zu verwenden, blieben die Links auf Deutsch. Solution: Wir haben die Startseite erneut übersetzt, was dazu führte, dass die Buttons „Book Now“ und „View Silvretta Therme“ nun korrekt auf die englischen Seiten verlinken. Es ist unklar, warum die Übersetzung beim ersten Versuch nicht funktionierte.
Falls diese Lösung für Ihr Problem irrelevant erscheint, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen 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.
