Problem: The client is experiencing issues with missing excerpt images on their English homepage, while they display correctly on the French homepage using the Divi theme. Solution: 1. Check WPML Media Translation Settings: * Go to WPML → Settings. * Scroll down to the Media Translation section. * Ensure the options Duplicate uploaded media to translations and Duplicate featured images to translations are checked. * Click the Apply button to save changes. 2. Process Existing Media: * Navigate to WPML → Media Translation. * If any images haven't been duplicated to English, use the Start or Translate media buttons to duplicate existing media. 3. Update an Affected Post Translation: * Go to Posts → All Posts. * Edit the translation of a French post missing its excerpt image on the English homepage by clicking the plus or pencil icon under the English language column. * In the Advanced Translation Editor, even without text changes, scroll down and click Complete to update the translation. * Repeat for other affected posts. 4. Clear Your Site's Cache: * Clear any caching plugins or server-side caching to ensure the homepage updates are visible.
After following these steps, check the English homepage to see if the excerpt images appear correctly. If the issue persists or the solution 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 needed, please open a new support ticket at WPML support forum.
Problem: Wenn Sie zu WPML → Übersetzungen gehen und versuchen, eine Übersetzung zu übernehmen, erhalten Sie eine Fehlermeldung: 'Authentifizierungsfehler, bitte kontaktieren Sie Ihren Übersetzungsmanager, um Ihr Abonnement zu überprüfen.' Dies tritt auf, wenn das Plugin 'Add Admin CSS' aktiviert ist. Solution: Wir empfehlen Ihnen, das Plugin 'Add Admin CSS' zu deaktivieren, da es nicht mit WPML kompatibel ist und Konflikte verursacht. Dadurch sollte WPML problemlos funktionieren.
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 Seite mit bekannten Problemen 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.
Problème : Après une mise à jour, un bug est apparu dans une page Divi traduite en quatre langues via WPML. Seul le contenu en allemand s'affiche correctement, les autres langues restent en allemand malgré le changement de langue. Solution : Il semble que les identifiants de shortcode n'ont pas été traduits ou que Divi a changé la manière de gérer ces traductions. Nous recommandons de traduire manuellement les identifiants de shortcode comme montré dans les captures d'écran fournies par notre équipe. Après la traduction, il est important de supprimer le cache du site et de WPML pour que les modifications prennent effet.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous conseillons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions des thèmes et plugins, et si nécessaire, de ouvrir un nouveau ticket de support.
Problem: After migrating a multi-lingual site to a new production server, the backend became very slow, primarily due to frequent API calls made by the WPML Multilingual CMS plugin, resulting in '426 Upgrade Required' errors. Solution: First, ensure that all WPML plugins are updated to their latest versions. Next, within the WPML settings, switch the translation editor as this might resolve the issue temporarily. Additionally, check WPML logs for repeated API requests and review server resource usage to identify any loops or redundant external calls. If these steps do not alleviate the problem, it may be due to a bug that our developers are currently investigating. In this case, switching the translation editor as per the instructions in WPML → Settings should serve as a temporary workaround.
Please note that this solution might become outdated or may not apply to your specific situation. 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 necessary, please do not hesitate to open a new support ticket.
Problem: If you're experiencing issues with WooCommerce endpoints showing a 404 error on your multilingual site, particularly when switching languages, and it temporarily resolves by flushing permalinks but reoccurs, this might be relevant to you. Solution: We recommend updating your WPML Multilingual & Multicurrency for WooCommerce to version 5.5.4 once it is released, as it includes a fix for this issue. Ensure you always have the latest version installed. If this solution becomes outdated or does not resolve your specific 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 the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing a 500 internal server error when accessing WordPress REST API endpoints like wp-json/wp/v2/posts with the default language parameter (?lang=ar) in a multilingual site using WPML, the issue might be due to incorrect string translations. Solution: We recommend checking the translation of specific strings in the WPML String Translation. For instance, the problematic string could be:
Delete the user's %1$s and %2$s data when the %3$s access expires.
Ensure its translation is accurate. In this case, the correct translation should be:
احذف بيانات المستخدم %1$sو %2$s عند انتهاء صلاحية الوصول %3$s.
After correcting the translation, verify that the endpoint no longer returns a 500 error.
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 for further assistance.
