Проблема: Клиент столкнулся с проблемой дублирования атрибутов и поломкой таксономий при использовании стандартного CSV-импортера WooCommerce в связке с плагином WPML Export and Import. Атрибуты, которые уже были переведены и связаны через WPML Taxonomy Translation, дублировались и теряли связь с переводами после импорта. Решение: Мы провели тесты и обнаружили, что проблема возникает из-за неправильной структуры файла импорта. В поле
Attribute 1 name
должны быть указаны оригинальные названия атрибутов, а не их переводы. Поле
Attribute 1 value
должно содержать переведённые значения атрибута для соответствующих языков. Это предотвратит создание новых атрибутов при импорте и сохранит корректную связь с уже существующими переводами.
Если данное решение окажется неактуальным или не поможет в вашем случае, мы настоятельно рекомендуем проверить известные проблемы, убедиться в актуальности версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. Если проблема сохранится, пожалуйста, откройте новый тикет поддержки.
Problem: The client reported an issue where the French mobile menu was displaying the incorrect label 'Certificats Cadeaux Vivanti' instead of 'Certificats Cadeaux'. Solution: We recommended the client to check and correct the navigation menu settings for the French language. Here are the steps we suggested: 1. Access the header templates at your WordPress admin area. 2. Edit the header template named Global Header Vivanti Final. 3. Ensure the primary-language template is updated and then retranslate it. After following these steps, the navigation menu should display the correct translated version.
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 the problem persists, please open a new support ticket.
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: 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.
