Problem: Wenn Sie beim Versuch, das WPML Setup durchzuführen, nur eine weiße Seite mit dem Titel "WPML Setup" sehen, könnte dies auf einen Konflikt mit einem Plugin oder einen fehlerhaften Datenbank-Key zurückzuführen sein. Solution: Wir empfehlen Ihnen, ein Backup Ihrer Datenbank zu erstellen und dann den Eintrag in der Tabelle
wp_options
von "WPML(setup)" zu "WPML(setup)1" umzubenennen. Dies können Sie mit dem folgenden SQL-Snippet tun:
Wenn Sie sich nicht sicher sind, wie Sie diese Änderung vornehmen können, empfehlen wir Ihnen, einen Fachmann zu konsultieren oder uns erneut zu kontaktieren.
Bitte beachten Sie, dass diese Lösung möglicherweise veraltet oder nicht auf Ihr spezifisches Problem anwendbar ist. Wir empfehlen Ihnen, 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. Sollte das Problem weiterhin bestehen, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Besuchen Sie dazu unser Support-Forum.
durante una scansione ad alta sensibilità. Soluzione: Abbiamo confermato che il file è sicuro e non deve essere eliminato. In una futura versione, specificatamente la 4.9.1, risolveremo il problema per evitare che WordFence lo identifichi erroneamente come non sicuro.
Se la soluzione proposta non risolve il problema o se sembra non essere più rilevante, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di controllare gli argomenti noti, verificare la versione della correzione permanente e confermare che hai installato le ultime versioni dei temi e dei plugin. Per ulteriore assistenza, visita il nostro forum di supporto.
Problème : Le site du client ne peut pas se connecter à WPML et certaines chaînes restent non traduites. En back-office du module, il est indiqué que l'API REST n'est pas activée, bien qu'elle le soit (test confirmé via une URL). Les URLs suivantes ont été whitelistées : wpml.org, cdn.wpml.org, et api.wpml.org. Solution : Nous avons vérifié que l'API REST est accessible comme prévu, donc la notification que vous voyez est probablement un faux positif. Il est possible que le blocage provienne de notre côté. Nous vous recommandons de vérifier si les adresses IP suivantes correspondent à celles de votre serveur :
104.26.3.99
104.26.2.99
172.67.73.11
De plus, un autre plugin pourrait bloquer la connexion. Essayez de désactiver temporairement tous les plugins sauf WPML pour tester cela dans un environnement minimal. Si le problème persiste, veuillez partager un accès à votre site pour un examen plus approfondi.
Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, 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 nécessaire, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum d'assistance.
Problem: The client was experiencing an issue where their site did not meet WPML's minimum requirements because the WordPress REST API was not responding correctly. This was initially suspected to be due to WPML's requests to the REST API being blocked or not properly authenticated.
Solution: 1. The client was advised to modify the
WordPressRestApiStatus.php
file within the WPML plugin directory to include cookie authentication in addition to the existing basic authentication. 2. After implementing the suggested changes, the issue persisted, leading to further investigation. 3. It was eventually identified as a false positive caused by a minor bug in WPML's code. A workaround was provided by the second-tier support, and a permanent fix is expected in the next WPML version.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the Litespeed cache crawler is only caching pages in the main currency (USD) and not in the secondary currency (CAD), despite having set the
wcml_client_currency
cookie to capture both currencies. Solution: We recommended the client to temporarily allow all currencies to be accessible from any location to test if the correct cached version is then served. Additionally, we conducted a test using cURL to ensure that the CAD currency pages are being cached when accessed directly with specific cookies set:
The test confirmed that the page with the CAD currency was correctly received. We have also communicated with LiteSpeed's support to address this known issue and are awaiting their feedback.
If this solution does not resolve your issue, or if it 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. If the problem persists, please do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: The client was experiencing an issue where AJAX fragments in a mini-cart were returning in the wrong language when the page was cached. This problem persisted despite the 'Store a language cookie to support language filtering for AJAX' setting being enabled. The issue seemed related to the timing of the cookie change during page load, which was suspected to be too late, affecting AJAX actions.
Solution: We recommended the client to deactivate all unrelated plugins and test with only WPML, LiteSpeed Cache, WPML String Translation, WooCommerce, BricksUltimate, and WPML Multilingual & Multicurrency for WooCommerce active. This setup did not reproduce the issue, suggesting an interaction between LiteSpeed and another plugin was causing the problem. We advised the client to identify the problematic plugin by reactivating them one by one and checking the mini-cart's behavior. Additionally, we provided a workaround involving a custom plugin designed to handle the specific caching and language switching scenario. The client was instructed to install and activate this plugin, then monitor the mini-cart's behavior.
If this solution does not resolve the 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 problems persist, please open a new support ticket at WPML support forum.
Problem: After updating WPML CMS to versions 4.8.5 or 4.8.6 on a multisite, links on the homepage that should direct to posts (custom post types for tours) are instead redirecting to images. This issue was identified when the subsite name 'au' conflicted with an image slug also named 'au'. Solution: 1. Identify and delete the media item with the slug 'au' in your WordPress media library or directly from the database where post_name is 'au'. 2. If deleting the specific media item does not resolve the issue, consider renaming the slug to avoid conflicts. 3. After making these changes, verify if the homepage links are correctly pointing to the intended posts.
Please note that this solution might become outdated or may not apply to your specific case. If the issue persists, we highly recommend checking for 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 necessary, do not hesitate to open a new support ticket for personalized assistance at WPML support forum.
Problem: The client reported an issue where Widget Group titles were not displaying in the translated language on their multilingual site, despite the content within the Widget Group blocks being correctly translated. The REST API was initially reported as disabled by WPML but later appeared as enabled.
Solution: We resolved this issue in the latest version of WPML (4.9.0). To address this, we recommend updating to WPML 4.9.0 along with the latest versions of Strings Translation (3.5.0), Media Translation (3.1.0), and WCML (5.5.4). Here are the steps to update: 1. Navigate to Plugins → Add New Plugin in your site’s admin panel. 2. Click the Commercial tab. 3. Press the Check for updates button. 4. Select WPML 4.9 from the list and click Install. Please ensure to back up your site fully (both files and database) before proceeding with the update. More details about WPML 4.9.0 can be found here.
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. If issues persist, please open a new support ticket.
Problem: WPML Media Translation marked as 'Not Installed' on the Support page. Solution: We resolved this issue in the latest version of WPML (4.9.0). To address this, please follow these steps: 1. Go to your site’s admin area. 2. Navigate to Plugins → Add New Plugin and select the Commercial tab. 3. Click the 'Check for updates' button. 4. Find WPML 4.9 in the list and click 'Install'. Before proceeding, ensure you make a full site backup (files and DB). For more details on WPML 4.9.0, visit this link.
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. If issues persist, please open a new support ticket.
Problem: You've noticed that since the last update, an image that's translated in the Media Translation, when used on a page and then translated in the CTE, isn't translated anymore. Instead, the original image is served on the translated page. Solution: We've resolved this issue in the latest version of WPML (4.9.0). Please also update to the new versions of Strings Translation (3.5.0) and Media Translation (3.1.0). If you don't see these new versions on your site, follow these steps: 1. In your site’s admin, go to Plugins → Add New Plugin and click the Commercial tab. 2. Click the Check for updates button. 3. Select WPML 4.9 from the list and click Install. Before updating our plugins, we strongly recommend making a full site backup (files and DB). Learn more about WPML 4.9.0 in our post: WPML 4.9.0 Changelog
If this solution does not apply to your case because it might be outdated or not relevant, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.
Problem: The client reported a fatal error related to Elementor's Global Widgets when WPML is active. The error message indicated a problem with calling a function on a null object within the Elementor Pro plugin. This issue was causing the client's website to break on specific pages. Solution: We resolved the issue by updating to the latest version of WPML (4.9.0) and the Strings Translation plugin (3.5.0). We advised the client to check for updates at your-domain.com/wp-admin/plugin-install.php?tab=commercial and click the 'Check for updates' button. It is crucial to make a full backup of the site before proceeding with the update.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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. For further assistance, you can also contact us directly at the WPML support forum.
Problem: WCML - Default Form Value is not selected if the attributes were created in the scondery language. Solution: We recommend updating to the latest version of WCML (5.5.4), along with WPML (4.9.0) and Strings Translation (3.5.0). Before updating, ensure to back up your site fully, including files and the database. You can check for updates by visiting your-domain.com/wp-admin/plugin-install.php?tab=commercialyour plugin installation page and clicking the 'Check for updates' button.
If this solution does not apply to your case because it might be outdated, or if you encounter further 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. Please feel free to open a new support ticket with us for additional assistance.
