Problem: The client reported that a specific page was not displaying properly. Solution: We recommended clearing the browser cache to resolve the display issue. If you're experiencing a similar problem, we suggest you try clearing your browser cache as well.
Please note that this solution might be 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 issue persists, please open a new support ticket.
Problem: You are experiencing CSS issues with your BeTheme site, specifically with the styling of all language menus, including the main menu, sticky menu, and two mobile phone menus. The flags in the language switcher are not aligned vertically as desired. Solution: 1. Clear All Caches: If you are using any caching plugins or your host provides server-side caching, please clear all caches to ensure that any changes are immediately reflected on your site. 2. Inspect and Adjust CSS: Use your browser's developer tools to inspect the problematic menu CSS. Look for any conflicting or overriding CSS rules and adjust them accordingly. You might need to temporarily disable custom CSS globally and in the WPML Language Switcher to isolate the issue. 3. Manual CSS Adjustments: Since the issue is specific to BeTheme, we recommend manually reviewing and adjusting the CSS related to the language switcher elements and menu wrappers within the BeTheme customizer or a child theme.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client wanted to list only in-stock and visible products on the WooCommerce translations queue page. Solution: We explained that filtering in-stock and visible products is a WooCommerce configuration for the frontend and does not fall within the capabilities of the WPML plugins. The client managed to achieve the desired view by selecting only in-stock items under WooCommerce --> All Products. This solution is specific to WooCommerce settings and not a feature controlled by WPML.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise 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: Wenn Sie eine WordPress/WooCommerce-Installation mit WPML betreiben und neue Alias-Domains hinzufügen, kann es vorkommen, dass der Seiteninhalt nicht ausgeliefert wird und im Frontend die Meldung 'In der Website ist ein kritischer Fehler aufgetreten' erscheint. Dies liegt an einem Fehler im 'functions.php' Ihrer Theme, speziell in der Funktion 'wp_translate()', die nicht für neue Sprachen konfiguriert ist. Solution: Um das Problem zu beheben, sollten Sie die fehlenden Einträge für die neue Sprache (z.B. Polnisch 'PL') in das '$dictionary' Array in Ihrer 'wp_translate()' Funktion hinzufügen. Hier ist ein Beispiel, wie Sie dies tun können:
Stellen Sie sicher, dass Sie alle notwendigen Übersetzungen für die neue Sprache hinzufügen, damit die Inhalte korrekt angezeigt werden. Falls das Problem weiterhin besteht oder Sie Unterstützung benötigen, 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 stating 'Cannot use object of type stdClass as array' in sitepress-multilingual-cms/classes/localization/class-wpml-download-localization.php, it might be due to a conflict with Duplicator Pro plugin. This occurs because the translations_api filter should return an array, but Duplicator Pro sometimes returns an object, causing WPML to treat it incorrectly. Solution: We recommend deactivating Duplicator Pro to see if the issue resolves. If it does, you can apply a temporary fix by modifying the code in wp-content/plugins/duplicator-pro/src/Utils/Translations.php. Replace the problematic line with the following code:
$translations = $this->getTranslations($args['slug'], $this->apiUrl);<br />// Ensure we return an array, not an object (WordPress expects array)<br />if (is_object($translations) && isset($translations->{ $args['slug'] })) {<br /> return $translations->{ $args['slug'] };<br />}<br />return is_array($translations) ? $translations : [];
We also suggest reporting this issue to Duplicator Pro support for a permanent fix. If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client reported that a specific product was not appearing correctly on their website, even though other products were fixed. The issue persisted in both the translated and primary language versions of the product page. Solution: We first suggested deactivating the WPML plugin to determine if the issue was related to WPML or another plugin. After deactivation, the problem still occurred, indicating a potential conflict with another third-party plugin. We then recommended deleting the problematic product and recreating it from scratch. After recreating and retranslating the product, the client should check if the issue still persists.
If this solution does not resolve the 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. If problems continue, please open a new support ticket at WPML support forum for further assistance.