Problem: Old sale products are still displayed on the sale page with normal prices in translations. The issue arises when the old listing price is deleted using the Quick Edit option under products. While this removes the product from the sales page in the default language, it remains on the translated listing pages without the listing price. Solution: First, ensure that the custom field
_flatsome_product_percentage
is set to 'Copy' in WPML → Settings → Custom Fields Translation and save the changes. After setting this, update the product in the original language with minor changes, then update its translations to ensure the custom field is copied correctly. If the issue persists, consider performing a bulk update. Temporarily add a tag or make a small change to the product description, update the products in bulk, and then revert the change. This process may help in triggering synchronization and updating the sale prices correctly.
Please note that the solution provided 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 at WPML support forum.
Problem: After updating the ACF for WPGraphQL plugin, nested relationship fields are returning null when querying the translation, whereas previously they returned content. Solution: If you're experiencing issues with nested relationship fields returning null in translations after updating ACF for WPGraphQL, we recommend checking a similar issue discussed in our forum. Please visit https://wpml.org/fr/forums/topic/wpml-graphql-with-acf-relationial-fields-doesnt-returns-data-on-non-default-language/#post-16721822 for more details. This issue might be similar to what another client experienced, and reviewing that case could provide insights or a solution.
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 these steps not resolve the issue, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing an internal server 500 error when switching to the Arabic language on a WordPress site using the Divi 5 template and The Events Calendar plugin, it might be due to incorrect string translations. Solution: We recommend checking the WPML -> String Translation for any incorrect translations. Specifically, look for the string "%1$s %2$s iCal Feed" and replace it with "موجز iCal %2$s %1$s". Additionally, check the string "%s update available" and replace the Arabic translation with "تتوفر تحديثات %s". After making these changes, your site should function correctly without the internal server error.
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.
Проблема: Клиент столкнулся с проблемой перевода контента в плагине WP Courseware, особенно разделы "Викторины" и "Вопросы", которые хранятся в собственных таблицах базы данных и не используют стандартную структуру WordPress. Решение: Мы предложили два возможных решения: 1. Использовать другой плагин, который уже совместим с WPML. Список таких плагинов можно найти здесь: https://wpml.org/plugin/ 2. Связаться с автором текущего плагина и попросить его сделать плагин совместимым с WPML, отправив ему ссылку на форму участия в нашей программе совместимости: https://wpml.org/documentation/support/go-global-program/
Если данное решение окажется неактуальным или не подходит под ваш случай, рекомендуем открыть новый тикет поддержки. Также настоятельно рекомендуем проверить известные проблемы, убедиться в версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
Problem: Beim Import von Produktnamen für die niederländische Sprache (NL) werden die Produkte aktualisiert, aber die Produkte der Quellsprache (DE) werden gelöscht. Der Kunde verwendet eine CSV-Datei, die nicht aus WooCommerce exportiert wurde und versucht, die SKU als Übersetzungsgruppe zu verwenden. Solution: Wir empfehlen, die deutschen Produkte (DE) frisch zu exportieren und die in der CSV-Datei bereitgestellten
wpml_import_translation_group
IDs zu verwenden. Fügen Sie dann die Übersetzungen hinzu, um eine korrekte Verknüpfung ohne Probleme zu gewährleisten. Für den Import neuer Inhalte in allen Sprachen ist es möglich, jedoch sollten Sie beim Aktualisieren/Importieren von Inhalten in einer Sprache die genauen IDs verwenden, die Ihre Beiträge oder Produkte derzeit haben. Dies stellt sicher, dass die Aktualisierungen genau sind und Duplikationen oder Fehler vermieden werden. Für Inhalte mit Eltern-Kind-Beziehungen sollten Sie zuerst die Elternelemente und ihre Übersetzungen importieren und dann diese IDs in der Spalte 'Parent ID' Ihrer Tabelle verwenden. Weitere Informationen finden Sie in der Dokumentation: WPML Export und Import vorbereiten. Wenn Sie nur Produkte in der niederländischen Sprache aktualisieren möchten, exportieren Sie die NL-Produkte, indem Sie die Sprache im Admin-Sprachschalter auf NL umstellen und importieren Sie diese Datei erneut mit aktualisierten Informationen. Verwenden Sie dabei die WooCommerce-Option, um "die vorhandenen Produkte zu aktualisieren".
Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen Ihnen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: You are unable to find where to change the email in the mailto: link, which displays a Spanish email address on the screen but shows a German email address when hovered over. Solution: We resolved the issue by modifying the email address in the footer of your site. Here are the steps we followed: 1. We accessed the 'Unassigned' footer in WPML -> Translation Dashboard -> Divi Footer Templates and clicked the 'Edit' option. 2. In the editing screen of this template, we clicked to edit the Spanish translation. 3. On the Advanced Translation Editor screen, we edited the email field and updated the mailto: to the Spanish domain email address. Please confirm if this resolves your issue and mark the ticket as resolved.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client was facing issues after changing from a subdirectory to a separate domain for the Spanish version of their site. Specifically, they encountered problems with editing Spanish pages in the front-end editor, displaying a different logo for the Spanish site in the global header, and the Spanish homepage initially displaying in German. Solution: 1. For the issue of the Spanish homepage showing in German, we identified it as a browser caching issue. We recommended the client to try accessing the site in a different browser or in incognito mode. 2. Regarding the different logo for the Spanish site, we advised the client to ensure they are using the correct settings in Divi. We provided guidance on setting up a different logo for different languages by referring to our documentation on Divi theme compatibility (Divi Builder) and using different translation editors for different pages (different translation editors).
If these solutions do not resolve your issues or seem outdated, we highly recommend checking related known issues (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 issues with translating a plugin string using WPML, specifically within the wc-ajax-product-filter plugin. Solution: We recommend you try the following steps: 1- Open the
3- Rescan the plugin or visit the page on the frontend. 4- Navigate to WPML > String Translation to translate it.
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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: When saving a page's CSS in a translated page using Cornerstone, the function
copy_meta_fields
does not properly handle the slashing of values before passing them to
update_post_meta
. This results in incorrect unslashing of characters like '\n' to 'n', causing data corruption. Solution: The issue stems from the Cornerstone save routine, not WPML. The correct fix should be implemented in Cornerstone's translation layer. Modify the function
This modification ensures that values are properly slashed before being saved, preventing data corruption. This issue needs to be solved by the Cornerstone Team, a future update would overwrite such a patch. If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, 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 issues persist, we highly recommend opening a new support ticket at WPML support forum.
