Problem: Sie haben das Problem, dass die Übersetzungen der Labels auf den Unterseiten nicht funktionieren, obwohl die Feldgruppen mit dem Broadcast Plugin verbreitet wurden. Auch das Entfernen und erneute Broadcasten der Feldgruppen brachte keine Lösung. Solution: Wir konnten das beschriebene Verhalten reproduzieren, sehen jedoch keinen direkten Auslöser. Da der WPML-Editor deaktiviert ist und die Bearbeitung über den WordPress-Editor erfolgt, empfehlen wir, eine Testumgebung bereitzustellen, in der wir das Problem ohne Risiko analysieren können. Alternativ wäre ein Klon Ihrer Seite für lokales Debugging hilfreich.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die bekannten Probleme 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. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.
Problem: The client is experiencing issues with product attributes not being available for selection on the product page in different language versions after translation. The attributes appear correctly in the original language but not in the translations. Solution: 1. Ensure that global attributes are created in the site's default language and avoid duplicating attributes under different names in different languages. This can be managed under WPML > Taxonomy Translation. 2. If changes are made to the original product's attributes or variations, save the variations again to sync these changes across translations. There is no need to re-translate the products if only attributes or variations are changed. 3. For issues related to caching, especially with WP Rocket, ensure that the cache is cleared after updates to products. This can be automated by setting up 'Always purge URLs' in WP Rocket settings to include:
/shop/*
4. If these steps do not resolve the issue, it may be helpful to deactivate unrelated plugins and switch to a default theme like Twenty Twenty-One to identify if the issue is related to specific plugins or themes.
If the problem persists or if this solution seems outdated or irrelevant 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, please feel free to open a new support ticket for further assistance at WPML support forum.
Problème : Vous utilisez un plugin accordéon pour créer un FAQ sur votre site, mais la traduction du titre de l'accordéon ne s'affiche pas correctement, restant dans la langue originelle malgré un enregistrement correct. Solution : Nous avons identifié que le titre de l'accordéon n'était pas enregistré correctement pour être détecté par WPML. Nous avons effectué une modification de la compatibilité en ajoutant le bloc suivant aux paramètres de WPML en utilisant XML :
<gutenberg-block type="aab/accordion-item" translate="1"><br /> <key name="heading" /><br /> <xpath>//h5[contains(@class,"aagb__accordion_title")]//text()</xpath><br /</gutenberg-block></code/><br />Maintenant, vous pouvez traduire les titres de vos accordéons en éditant légèrement le post concerné (ajouter un espace ou un caractère au contenu) pour que WPML charge les titres.<br /><br />Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les <a href="https://wpml.org/known-issues/">problèmes connus</a>, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à <a href="https://wpml.org/fr/forums/forum/support-en-francais/">ouvrir un nouveau ticket de support</a>.
Problem: Der Kunde kann keine bestehenden Glossareinträge im Backend sehen und erhält Fehlermeldungen beim Versuch, neue Einträge hinzuzufügen. Die Fehlermeldung deutet auf einen JSON Parser Fehler hin. Zudem besteht das Problem, dass auf der Produktionsseite, im Gegensatz zur Staging-Seite, weiterhin Probleme auftreten. Solution: 1. Wir haben die Organisation der Websites im System vereinheitlicht, sodass nun alle URLs denselben Glossar und Übersetzungsspeicher teilen. 2. Ein JavaScript-Fehler verhindert die Anzeige des Glossars. Es besteht ein möglicher Konflikt zwischen WPML und einem anderen Plugin oder dem Theme. Eine genauere Untersuchung erfordert eine Kopie der Website. 3. Lokale Tests zeigten, dass das Deaktivieren des 'Extend Editor Role' Plugins das Problem löst. Es wird empfohlen, den Entwickler des Plugins zu konsultieren, da das Plugin möglicherweise in das Translation Management von WPML eingreift. Weitere Informationen zu WPML und Benutzerrechten finden Sie hier: WPML Admin Capabilities
Sollte diese Lösung veraltet sein oder nicht auf Ihr Problem zutreffen, 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 von Themes und Plugins installiert haben.
Problem: If you're experiencing a fatal error when enabling Redis Object Cache on your WordPress site, specifically with PHP 8+ where count() is called on a null value in WPML_Posts_Listing_Page::pre_populate_caches(), this might be due to a cache miss causing
$wp_query->posts
to be null. This error typically appears in wp-content/plugins/sitepress-multilingual-cms/menu/post-menus/wpml-posts-listing-page.class.php on line 26. Solution: We recommend updating to WPML version 4.7.5, which addresses this issue by ensuring compatibility with Redis Object Cache and other object cache implementations. You can download the update and view the changelog here: WPML Changelog.
If this solution does not apply to your case, or if it seems outdated, 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 for further assistance.
Problem: You are trying to translate the Formidable Forms plugin validation messages but encounter an issue where the messages do not translate as expected, displaying the default English text instead. Solution: We recommend the following steps to address this issue: 1. Edit the form. 2. Click on each field and navigate to the "verification message" tab. 3. Replace the [field_name] placeholder with the actual field's name. 4. Retranslate the form from Settings -> Translate Form. 5. Ensure the message displays and can be translated, then save your changes. This workaround has been tested and confirmed to work with WPML and Formidable Forms.
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 was experiencing an 'Invalid Post Type' error when trying to translate posts in a custom post type called Reviews. Upon switching the language to English, the error appeared, despite the post type configuration seeming correct. Solution: We resolved the issue by modifying the translation settings for the custom post type. In the WPML -> Settings -> Post Types Translation section, we changed the 'Post Type' (acf-post-type) from Translatable to Not translatable. This adjustment allowed the client to switch and edit a Review post in English without encountering the 'Invalid Post Type' error.
If this solution does not resolve your issue, or if it 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. Should the problem persist, please open a new support ticket.
Problem: The client is unable to display a linked post in other languages on their website using Divi layouts and the DiviFlash plugin. The expected translated posts are not showing. Solution: 1. Ensure that the Divi layout used to create the page is translated: - Navigate to WPML > Translation Management. - Locate the Divi layout in question. - Select it and send it for translation at the bottom of the page. - Proceed to WPML > Translations and complete the translation. 2. If the translated post still does not display, check the compatibility of the DiviFlash plugin with WPML. The Posts List widget used by DiviFlash is currently not compatible with WPML. We recommend contacting the DiviFlash developers to encourage them to make their plugin compatible with WPML. They can apply for assistance through our Go Global program.
If these steps do not resolve your issue, or if the information provided here is 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to translate fields generated by the B2BKing Pro plugin using WPML string translation, but the translations are not appearing on the website. Additionally, after some operations, the client's 'my-account' page shows a 500 internal server error. Solution: We recommend following the steps outlined in the video provided by our support team member, Carlos. The video can be accessed here: https://komododecks.com/recordings/coOdZ96784GuvFc8EZEG. Please ensure that you follow each step carefully to resolve the issues with translation and the 500 internal server error.
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 your issue, please do not hesitate to open a new support ticket with us for further assistance.
Problem: The client is using the Abandoned Cart Recovery plugin with WPML on a site for abandoned cats. The main language is Greek, and the secondary language is English. After creating a Greek email template and translating it to English, the client expected to receive an English email upon abandoning a cart in the English version of the site. However, they received the Greek email instead. Solution: We recommend checking the language settings of the WordPress dashboard if the email is triggered from there. You can adjust the dashboard language per user by navigating to
WP Dashboard > Users > Profile
. If the email is triggered from the frontend, it should automatically match the language of the frontend at the time of the cart abandonment. If this is not the case, it is advisable to contact the developers of the Abandoned Cart Recovery plugin for further support, as this plugin is not listed among our compatible plugins. Alternatively, consider using one of the following WPML-supported plugins for abandoned cart recovery:
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 you need further assistance, please open a new support ticket at WPML support forum.
