Problem: The client experienced an issue with media translation where the translated text skipped to the next picture, affecting multiple images sourced from a dummy page. Solution: We explained the difference between 'connected media' and 'copied media'. 'Connected media' allows changes in Media Translation to affect all languages, whereas 'copied media' does not. To address the issue: 1. Disable the 'Automatically detect best options for translating image texts' in WPML > Settings > Media Translation if you prefer not to use this behavior. 2. For images already marked as 'Copied Media', translate the Alt Text through the Advanced Translation Editor while translating the page. 3. Test by adding new images to a new page to see if they are no longer marked as 'copied media'.
If this solution does not resolve your issue or seems outdated, we 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: If you're experiencing a critical error on your translated site pages, it might be due to a PHP Fatal error indicating a type mismatch. Specifically, the error occurs because the code expects an array but receives a string instead. This issue often arises with ACF custom fields that are not correctly handled in translations. Solution: We recommend checking the ACF custom fields used in your template. Ensure that fields such as 'section_details', 'section_info', and 'section_map' are properly registered for translation with WPML and are returning arrays as expected. Here's what you might see in your code:
$salon_details = get_field('section_details');
$salon_info = get_field('section_info');
$salon_map = get_field('section_map');
$map_link = $salon_details['map_link'];
$address = $salon_info['address'];
$coords = $salon_map['lat_lang'];
Please confirm where these fields are defined: Are they attached to a specific page, a custom post type, or an ACF Options 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 problems persist, please open a new support ticket.
Проблема: Клиент столкнулся с проблемой дублирования атрибутов и поломкой таксономий при использовании стандартного 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.
