Проблема: Клиент пытается синхронизировать комментарии на своем сайте между русской и английской версиями страницы. Комментарии на русской версии страницы не переносятся с английской версии. Решение: На данный момент WPML не поддерживает прямой перевод комментариев пользователей. В качестве временного решения, мы предлагаем метод, который позволяет отображать все комментарии со всех языков на всех языковых версиях сайта. Это не переводит комментарии, но делает исходные комментарии видимыми на всех языковых версиях. Подробнее о данном методе можно узнать в этой теме форума.
Если данное решение окажется неактуальным или не подходит под ваш случай, мы настоятельно рекомендуем проверить известные проблемы, убедиться в версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. В случае дополнительных вопросов, пожалуйста, откройте новый тикет поддержки.
The client attempted to install the WPML Multilingual CMS plugin using Composer with version '4.6.14' and encountered an error indicating that the file could not be unzipped, suggesting it might not be a zipfile or is part of a multi-part archive.
Solution:
We regret to inform you that installing WPML using Composer is currently not supported. This feature has been requested but has not been implemented yet due to certain limitations.
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 for further assistance.
Problem: The client's SEO team noticed that the hreflang tag and the canonical URL have the same structure, which was not expected. Solution: We have resolved this issue in a later version of WPML. We recommend updating to the latest version of WPML to ensure this issue is addressed.
If this solution does not apply because it might be outdated or not relevant 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 experience issues, please open a new support ticket at WPML support forum.
Problem: You are trying to save data on an ACF option page in various languages using ACFML, with fields set as 'copy' to maintain the same values across all languages. While the backend shows values correctly copied and locked, the frontend still displays values from the main language (Italian). Even after updating the value in the main language, you need to manually update it in each secondary language to reflect changes on the frontend. Solution: The behavior you're experiencing is expected when using ACF fields with the copy translation preference. To apply these values to the secondary languages on the frontend, you must re-save the options page in those languages. This process is necessary to ensure consistency across languages as currently implemented by WPML and ACFML. For more details, you can refer to our documentation here: Translating the ACF Options Page Custom Fields with WPML. If this manual update process is cumbersome, we can submit a feature request to explore the possibility of automatically copying the options page values into the secondary languages upon saving the default language options page. Please let us know if you would like us to proceed with this request.
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 WPML support forum.
Problem: The client is experiencing issues with the translation engine in WPML, where it deletes progress and fails to maintain colored highlights for HTML attributes. Additionally, the cross icon does not clear these highlights, and placeholder tags appear in the source text without being able to be added to the translated field. The engine also refuses to mark the translation as complete, and formatting must be applied to save the translation. Solution: We recommend applying the same marker to your translated content as in the original to ensure it can be saved. If you need to remove and re-add markers to different parts of a sentence, this is expected behavior in the translation process. For issues with different formatting across languages, you can use CSS to apply different styles or assign markers to a dot and hide them in the second language. For more details, please see our forum post: https://wpml.org/forums/topic/issues-in-translation-workflow/#post-13119257
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needed a way to display the currency code instead of the symbol across various sections of their WooCommerce site, including product pages, store, cart, and checkout.
Solution: We recommended a temporary solution to display the currency code everywhere on the site. Here are the steps we suggested: 1. Take a backup of your site and database. 2. Edit your active theme's functions.php file. 3. Add the following code at the end of the file:
Additionally, if you want to edit the currency switcher: 1. Go to WooCommerce -> WooCommerce Multilingual & Multicurrency -> Multicurrency. 2. Scroll down to "Product page Currency Switcher" section. 3. Edit the currency switcher and remove "%symbol%" from "Template for currency switcher" field. 4. Save the changes.
For more details on managing multi-currency in WooCommerce, please see our documentation.
If this solution does not apply to your case, or if it becomes outdated, 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. Should you need further assistance, please open a new support ticket.
