Problem: Il cliente necessita di trasferire il progetto all'account del cliente per permettergli la gestione autonoma dei pagamenti e desidera sapere se può acquistare la soluzione Multilingual Blog anziché il piano Multilingual CMS, nonostante il processo di traduzione sia già stato completato. Solution: Non è possibile trasferire il rinnovo direttamente ai clienti. Il cliente dovrà acquistare una propria licenza WPML. Può trovare maggiori dettagli qui: https://wpml.org/it/purchase/rinnovo-di-wpml-come-funziona-e-cosa-succede-se-non-lo-rinnovate/ La licenza Multilingual Blog potrebbe non essere sufficiente per alcuni temi e plugin che richiedono la funzionalità String Translation, inclusa solo nel piano Multilingual CMS. Tuttavia, il cliente può iniziare con Multilingual Blog e, se necessario, effettuare l'upgrade a Multilingual CMS senza perdere dati. Per maggiori informazioni sulle licenze WPML: https://wpml.org/it/purchase/ Per trasferire il sito in modo che il cliente possa gestire autonomamente i rinnovi, può seguire questa guida: https://wpml.org/purchase/paying-wpml-renewal-for-my-site/
Se questa soluzione non dovesse essere più rilevante o non risolvere il problema, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di verificare le questioni note, di controllare la versione della soluzione permanente e di confermare di avere installato le ultime versioni di temi e plugin.
Problem: The client was unable to save translations for FAQs. Despite the translations appearing correctly in the translation mask, the save function was not working, and the pencil icon disappeared upon refreshing the WordPress admin page. Solution: We took several steps to diagnose and attempt to resolve the issue: 1. Confirmed the WP memory limit is set to 1024M, which is well above the minimum required. 2. Verified that the FAQ custom post type and Elementor templates are configured as translatable in WPML settings. 3. Checked and confirmed that ACF fields are not in use for FAQs. 4. Deactivated all caching mechanisms, including WP Rocket and WP Admin cache, and ensured no server-level cache is present. 5. Advised clearing the browser cache. 6. Attempted to reset WPML translation queues, including cancelling stuck jobs and batching small FAQ translation submissions. 7. Confirmed that automatic translation is not enabled on the site. After these steps, the issue was resolved by using the function "Corriger l'attribution du type de publication pour les traductions", which allowed the translations to be saved correctly.
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 problem persists, please open a new support ticket at WPML support forum.
Problem: The client has created a language landing page and wants the website to remember the user's language choice using cookies, so it doesn't prompt for language selection on subsequent visits. Solution: We recommend the following steps: 1. Ensure that the 'Language filtering for AJAX operations' is enabled in WPML under WPML >> Languages. This setting allows WPML to set the language code in the cookie 'wp-wpml_current_language'. 2. Use a PHP if/else statement to read this cookie and redirect the user to the correct language page based on their previous selection. For more details on handling cookies with WPML, please refer to our documentation: https://wpml.org/documentation/support/browser-cookies-stored-wpml/ https://wpml.org/documentation/getting-started-guide/language-setup/enabling-language-cookie-to-support-ajax-filtering/
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 this does not resolve your issue, please open a new support ticket at https://wpml.org/forums/.
Problem: Sie haben Probleme mit der Anzeige einiger Elementor-Widgets in der Übersetzung und nach dem Einfügen von XML-Code in WPML erscheinen viele nicht benötigte Felder. Solution: Wir empfehlen Ihnen, den folgenden XML-Code zu verwenden und dann die Originalseite erneut zu öffnen und zu speichern:
Für die Zuweisung der Übersetzungen könnten Sie auch diese Methode ausprobieren: Flexible Übersetzungsmethoden. Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Überprüfen Sie auch die bekannten Probleme, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen Ihrer Themes und Plugins installiert haben.
Problem: The client is planning to create an introductory page where site visitors can choose either English or German, and then be redirected to the respective language version of the site. They are also concerned about whether this setup will affect the SEO of their multilingual website. Solution: We recommend using the built-in features of WPML for language redirection, so there is no need to purchase an additional plugin. You can set up a language directory by following the instructions here: Setting up a language directory. Additionally, we confirm that using WPML for this purpose will not negatively impact your website's SEO.
Please note that this solution might be irrelevant 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 you still encounter issues, please open a new support ticket at WPML support forum.
Problem: If you're using JetEngine with a Custom Post Type for a blog page and have added a Post Comments widget using the Elementor Single Post template, you might find that the comment form works in the original language but is not visible in other languages. Solution: We recommend checking the translation status of your templates. In this case, the template translations had the status "Update needed". Completing the translations to 100% resolved the issue, making the comment sections visible on the translated posts. You can access the translations at WPML > Translation Dashboard. Here you can create a job, and send it to automatic translation or assign it to yourself and access it at WPML > Translation to translate the job with the Advanced Translation Editor.
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: You are experiencing issues with WPML's Advanced Translation Editor (ATE) when used with Oxygen Builder 4.8.x, resulting in broken frontend rendering of translated pages. This includes loss of CSS and layout consistency, broken JavaScript functionality, and incorrect DOM structure. Solution: Currently, Oxygen Builder is not officially compatible with WPML. As noted on our compatibility page (https://wpml.org/plugin/oxygen/), some features may not function correctly in a multilingual site. We recommend proceeding with manual translation, similar to your successful approach using the 'Duplicate' option. We are in contact with the developers of Oxygen Builder to work towards official compatibility, but full support is not guaranteed at this time.
If this solution does not resolve your issue or 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. If further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
Problem: You are experiencing an issue where, despite having an active Pay-as-You-Go plan for automatic translations, your WPML dashboard is requesting you to fix an issue and pay €100.00. Solution: We recommend checking the details of your Pay-as-You-Go plan and the status of your automatic translation credits. It's possible that your credits have been depleted faster than anticipated. For a detailed explanation and steps to resolve this, please refer to our previous discussion on this topic at https://wpml.org/forums/topic/pay-as-you-go-12/.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where your dashboard is asking you to pay €100 despite having an active pay-as-you-go plan, this could be due to reaching a safety limit. Solution: We have implemented two safety limits to prevent accidental overspending and to protect against fraud. These limits are triggered the first time you spend €100 and €4,000 in a single month. If you reach these limits, you will be required to make a payment before you can continue using the translation services. At the end of the month, any amount you've paid will be deducted from your total invoice. For more details on these safety limits, we recommend reading our terms and conditions on pay-as-you-go for automatic translation.
If this solution does not apply to your situation, 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 you need further assistance. You can do so at WPML support forum.
