Not WPML issue

Problem:
The client reported that the English version of their WooCommerce shop page was displaying fewer products compared to the Bulgarian version, despite both versions being set to automatically translate.
Solution:
We discovered that the issue was related to the WooCommerce Wholesale Prices Premium plugin. We recommended deactivating and then reactivating the plugin, which resolved the problem. Additionally, we advised the client to check and publish any English products that were still in draft status.

Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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. If needed, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client is trying to use WPML's Advanced Translation Editor and Automatic Translations for translating content from English to French, but not from English to Canadian English. They are concerned that the Advanced Translation Editor might automatically translate English (Canada), which is mapped to the default language of the site and should not be auto-translated according to WPML documentation.
Solution:
We advised the client to manually control the translation process to avoid automatic translation for English (Canada). This can be achieved by:
1. Activating the option in WPML -> Settings to control which content is sent for automatic translation.
2. Using the WPML -> Translation Management to filter content by the original language (English) and manually sending it for automatic translation in French.
For English (Canada), since automatic translation is not supported due to its mapping to the default site language, it is not necessary to map it for automatic translation unless desired by the client.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend checking the related 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.

Problem:
The client encountered an issue where the permalinks were mixed up between translations when editing a translated page's slug without reloading the tab first. This confusion occurred because the session information in the other tab of the browser was not updated to reflect the language change.

Solution:
We recommend always reloading the other tab after switching languages in the WPML editor to ensure that the session information correctly reflects the current language you are working on. This step is crucial to prevent the display of incorrect permalinks and to avoid applying changes to the wrong language version of the content.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please visit our known issues page and check if there's a permanent fix available for your version. Also, ensure that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket with us for further assistance at WPML support forum.

Problem:
The client created a Gravity Form using the Gravity Forms Survey Add-On plugin and encountered an issue where the form sends all data correctly in English via email, but not in Arabic. When the form is submitted in Arabic, the data is not being sent in the emails.

Solution:
We first verified that the issue was not related to email content being different between languages by using the "Log Emails" plugin. Both English and Arabic emails had the same content, and form entries were created correctly in both languages. We then identified that the Gravity Form had not been translated, and the notification emails were missing the

{all_fields}

tag. To resolve this:
1. We translated the Gravity Form and added the

{all_fields}

tag to the existing notifications.
2. We added another notification with the

{all_fields}

tag for testing.
3. We created a new test page, added the form, and translated this page as well.
After these adjustments, the form submitted correctly in both languages, and the received emails contained all the information in the respective languages. However, there was a note that the HTML formatted email had a design problem, which is not related to WPML but may affect how content is displayed.

If this solution does not resolve your issue or seems outdated, we recommend checking the related 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.

Problem:
Das Formular auf der englischen Version der Startseite zeigt recaptcha nicht an, was das Absenden des Formulars verhindert.
Solution:
Wenn Sie auf Ihrer mehrsprachigen Website auf ähnliche Probleme stoßen, empfehlen wir, die Borlabs-Einstellungen für jede Sprache manuell anzupassen. Navigieren Sie zu Borlabs > Einstellungen > Blocker > Script Blocker, wechseln Sie die Borlabs Sprachoption auf Englisch und deaktivieren Sie die Script Blocker für:

• elementor-recaptcha-api

• elementor-recaptcha_v3-api

• gravity-forms-recaptcha gform_recaptcha

Diese Anpassung sollte das Problem mit recaptcha auf der englischen Version Ihrer Website beheben.

Bitte beachten Sie, dass diese Lösung möglicherweise veraltet oder nicht auf Ihr Problem zutreffend ist. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme auftreten, zögern Sie nicht, ein neues Support-Ticket zu eröffnen.