Problem: The client was unable to use custom translations for the 'utsolgt' string in WooCommerce using WPML String Translation. Despite saving the translations, the default WooCommerce translations were being used instead. This issue arose after updating WooCommerce and WPML to the latest versions. Solution: We advised the client to ensure that all plugins were updated and to flush any existing cache. We also recommended creating a full site backup before proceeding with these steps. Additionally, we suggested following the steps in our guide to find and translate strings that do not appear on the String Translation page. You can find the guide here: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
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 at WPML support forum.
Problem: The client reported that the WordPress UI is set to English, and all WordPress settings are in English, but Elementor still loads in Norwegian when WPML is installed. The client was concerned about WPML creating unnecessary translation files and using translation credits for UI elements. Solution: We clarified that the JSON/PHP files seen by the client are added by WordPress, not WPML. You may try to follow the steps from this thread to see if this resolves the issue: https://wpml.org/forums/topic/elementor-editor-interface-with-wpml/#post-9863547
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 persists, please open a new support ticket.
Problem: The client noticed that their products were suddenly showing as "Waiting for translation" or "Refreshing translation status" despite having used auto-translation with 90,000 credits. They were unsure why the translations were not showing and what happened to the credits.
Solution: We confirmed that the 90,000 credits had been used to translate products and that the translations should be visible on the frontend, for example, on the product page provided. We advised the client to check the Automatic translation usage reports for details on the used credits and product URLs by navigating to WPML > Translation Management > Tools tab > Automatic translation usage reports > Download the report.
We also mentioned that 90,000 credits might not be sufficient to translate 936 products into two languages and suggested that the client add more prepaid credits or opt for the Pay As You Go subscription to translate additional content. For more information on automatic translation pricing, we provided a documentation link: https://wpml.org/documentation/automatic-translation/automatic-translation-pricing/.
If this solution does not apply to your situation, or if it seems 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. If further assistance is needed, please contact us through the WPML support forum: https://wpml.org/forums/forum/english-support/.
Problem: The client reported that taxes were not being calculated in their WooCommerce store after installing WPML and WooCommerce Multilingual. Despite setting the tax-rate calculation to be on "shop base address" for a 25% VAT on all products and shipping prices, the taxes were not being added at checkout or in the cart. The client also noted that WooCommerce Multilingual was incorrectly showing as not installed on the WPML support page.
Solution: We reviewed the client's website and discovered that the tax status for the products was not set to "Taxable." We adjusted the tax status for a product, and after this change, taxes were correctly calculated at checkout. We recommended the client to check the tax status for each product to ensure it is set to "Taxable" to resolve the issue.
If you're experiencing a similar issue with taxes not being calculated in your WooCommerce store after installing WPML, we recommend checking the tax status of your products and ensuring they are set to "Taxable."
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 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.
Utilizziamo i cookie per ottimizzare il nostro sito web e i nostri servizi.
Il tuo consenso ci permette di elaborare dati come il comportamento di navigazione.
Il mancato consenso potrebbe compromettere alcune funzionalità.
Funzionale
Sempre attivo
Necessario affinché il nostro sito web funzioni e comunichi correttamente.
Preferenze
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistiche
Li utilizziamo per analizzare le statistiche del nostro sito.
Le informazioni raccolte sono completamente anonime. L'archiviazione tecnica o l'accesso che viene utilizzato esclusivamente per scopi statistici anonimi. Senza un mandato, la conformità volontaria da parte del tuo fornitore di servizi Internet o altri registri di terzi, le informazioni memorizzate o recuperate per questo scopo da sole non possono generalmente essere utilizzate per identificarti.
Marketing
Questi cookie tracciano la tua navigazione per fornirti annunci pubblicitari pertinenti.
