Problem: If you're using Full Site Editing (FSE), Custom Post Types, and WPML, and you notice that WPML applies the default template instead of the custom post type template for translations, this might be your issue. In the original language (English), the correct template appears, but for all other languages, the default Page/Post template is used. Solution: We recommend checking the WPML > Translation Dashboard > Site Templates to ensure all templates are translated. Then, select the "wp_template" in WPML > Settings > Post Types Translation > Translatable - use translation if available or fallback to default language. This should align the template usage across different languages.
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: Der Kunde hat ein Problem mit der Übersetzung eines Class Attributs (Trigger) in WPML, wobei nach einer Synchronisation das Overlay in beiden Sprachen denselben Trigger hat. Solution: 1. Gehe zu WPML > Translation Dashboard. 2. Überprüfe, ob die Beitragstypen 'Header-, Body- und Footer-Templates' vorhanden sind. Falls diese bereits übersetzt sind und nicht angezeigt werden, setze die entsprechenden Filter im oberen Bereich. 3. Erstelle einen Übersetzungsauftrag und teile diesen dir selbst zu. 4. Gehe zu WPML > Übersetzungen und klicke beim entsprechenden Auftrag auf 'Übersetzen'. 5. Sollte die Übersetzung nicht wie erwartet funktionieren, suche die IDs oder Klassen im Textsuchfeld im Advanced Translation Editor oben rechts.
Falls diese Lösung veraltet ist oder nicht auf dein Problem zutrifft, empfehlen wir, einen neuen 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 du die neuesten Versionen von Themes und Plugins installiert hast. Für weitere Unterstützung besuche bitte das WPML Support Forum.
Problème : Vous rencontrez un problème où les produits ne sont pas correctement répartis entre les catégories marine et terrestrial en anglais, contrairement aux versions en français et en espagnol. Malgré les tentatives de dépannage avec WooCommerce Multilingual et WPML, la désactivation des plugins non essentiels et le changement de thème, le problème persiste. Solution : Nous avons identifié que plusieurs paramètres WPML liés aux taxonomies et types de produits, tels que
product_visibility
, n'étaient pas correctement configurés. Nous avons procédé aux ajustements nécessaires. Veuillez vérifier maintenant si les produits sont correctement répartis. Notez également que la catégorie 'terrestrial' en anglais contient 16 produits, et non 15 comme précédemment pensé.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus et de vous assurer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
Problem: You had technical errors with a translation page and created a clone using the Yoast Duplicate Post plugin. After removing the original translation page and replacing it with the clone, the translation link to the original language page was disconnected, and the 'Choose a Page to assign' option doesn't appear on the translation page. Solution: To reconnect the existing original language page with the new translation page, follow these steps: 1. Ensure that both the original and the cloned pages are correctly set up in their respective languages. 2. Go to the WPML > Translation Management section in your WordPress dashboard. 3. Use the 'Connect with translations' feature to manually link the original page with the cloned translation. 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with translating posts from English to Spanish using the Avada theme on their WordPress site. The main problems were that the featured image displayed incorrectly, side margins were not respected, and the background color was missing in the translated version. Additionally, the Avada post page settings were not being copied to the translation. Solution: We recommended translating the 'Custom Content Layouts' for the posts in question. This involved accessing the Avada layout sections in the WordPress admin and ensuring that the layouts were correctly assigned and translated. We also suggested adjusting the layout conditions to include specific posts or categories to ensure that the design settings apply correctly across different languages. After these adjustments, the client confirmed that the layout appeared correctly in the translated posts.
Please note that this solution might be outdated or not applicable to your specific case. If you're experiencing similar issues, 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: You are trying to translate the 'out of stock' status in WooCommerce using the Astra theme, but the translation incorrectly displays in French as 'VENDU' instead of 'SOLD'. Solution: We recommend following the steps in our guide to find and translate strings that do not appear on the String Translation page. Please visit this link and follow the instructions provided.
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 you still need assistance, please open a new support ticket at our support forum.
Problem: The client is experiencing issues with translating product categories using WPML on their website. Specifically, the hierarchy and images of the product categories are not maintained after translation, requiring manual intervention to set these for each translated category.
Solution: We recommend the following steps to improve the translation process of product categories: 1. Ensure product categories are set as Translatable – only show translated items in WPML → Settings → Taxonomies Translation. 2. Use WPML → Taxonomy Translation to translate category names and slugs. 3. To synchronize the hierarchy, navigate to the Hierarchy Synchronization tab within WPML → Taxonomy Translation and click Update Taxonomy Hierarchy. 4. Manually check and set images for each category translation by editing the category in the desired language and setting the image if it is missing. 5. Utilize WPML → Support → Troubleshooting tools like Sync product taxonomies and Remove ghost entries to help relink categories and images across languages. 6. Clear any site, plugin, or browser cache after these changes.
If these steps do not resolve the issue or if the process still seems inefficient, it may be due to limitations within the current WPML functionality or setup. We recommend checking for any updates or known issues related to this problem at https://wpml.org/known-issues/. If the problem persists, please open a new support ticket for further assistance at WPML support forum. We also suggest confirming that you have installed the latest versions of themes and plugins to ensure compatibility and functionality.
Problem: You are trying to export all translation jobs that were sent to the previous WPML connector, needing only the title, date, and status without including all of the content. Solution: The feature you are looking for, previously known as the 'Open Content Updates Log', is no longer available in WPML as it has been removed. We recommend using the Communication Log, which you can find under WPML → Support, to track translation activities. Although it is not a direct replacement, it serves a similar function. For more details on exporting translation statuses, you can refer to our documentation here: Exporting Translation Status to CSV.
If this solution does not fully address your issue or 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. We highly recommend opening a new support ticket if needed for further assistance. You can do so at WPML Support Forum.
Problem: The client is setting up a multilingual site using Divi and WPML and wants to create separate headers and footers for different languages. However, in the Divi Theme Builder, the 'Language' condition is missing from the Template Settings assignment rules, preventing the assignment of templates to specific language pages. Solution: We recommend checking our Divi guide on creating different designs for each language, which can be found here: https://wpml.org/documentation/theme-compatibility/divi-builder/#create-different-designs-in-each-language. Additionally, follow the detailed steps provided here: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/. It is essential to delete any previously created templates in the secondary language and start the process from the beginning. Please ensure to make a full site backup before proceeding.
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.