Problem: The client is experiencing a 500 Internal Server Error when accessing translated versions of their website in languages other than the main language (Spanish). This issue occurs specifically with URLs like /nl/, /fr/, /de/, etc. The error does not affect the default Spanish pages. The problem seems to be related to the Homelengo Real Estate theme, which triggers a PHP fatal error when WPML is active or when visiting pages in secondary languages. Additionally, there are issues with internal redirects and REST endpoints used by Contact Form 7.
Solution: We recommend the following steps to troubleshoot and potentially resolve the issue: 1. Contact the hosting provider to check the server error logs for more specific details about the error. 2. Disable the Homelengo Real Estate theme temporarily to see if the issue persists with a default theme. 3. Deactivate and reactivate WPML and Contact Form 7 to check if the issue is specifically related to these plugins. 4. Review and possibly adjust the .htaccess file to normalize /wp-json with language prefixes. 5. Flush permalinks and caches to ensure no stale settings are causing the issue. 6. If the problem continues, provide the debug log to the WPML support team for further analysis. You can find instructions on how to provide this information here: https://wpml.org/faq/provide-debug-information-faster-support/
If these steps do not resolve the 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 problems persist, please open a new support ticket with us for further assistance.
Problem: The client is trying to translate pages from Hebrew to English using WPML and Elementor on their website. They have set the English language direction in WPML to Left to Right (LTR), and Elementor page and section settings to Default direction. Despite these settings, all English content still aligns to the right and follows a Right to Left (RTL) direction, without switching columns. Solution: The issue might be related to Elementor Pro display conditions. If you're experiencing this, we recommend checking if certain conditions are set in Elementor Pro that might enforce RTL. You can view a tutorial on how to change these conditions here: https://www.youtube.com/watch?v=aBYuuUcPVuA. Alternatively, if you're unable to find the condition from the Elementor interface, you can remove it directly from the database: 1. Open your database. 2. Go to the wp_options table. 3. Find the entry named elementor_pro_theme_builder_conditions and delete it. Please ensure to back up your database before making any changes. Additionally, check for any custom CSS that might be enforcing RTL globally and remove it.
This solution might be irrelevant if it's 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 at WPML support forum.
Problem: Der Kunde berichtete über Probleme mit automatisch abgeschlossenen Bestellungen in Fremdsprachen seit einem Update von WCML. Bestellungen in der Primärsprache (DE) wurden korrekt abgeschlossen, während Bestellungen in anderen Sprachen nicht korrekt verarbeitet wurden, einschließlich fehlender Bestellnotizen und Trackingnummern. Solution: Wir konnten das Problem auf einer neuen Test-Site nicht bestätigen und empfehlen in solchen Fällen, eine Staging-Umgebung zu erstellen und alle Plugins außer WooCommerce, Klarna for WooCommerce, WPML und unseren Add-Ons zu deaktivieren, um das Problem zu isolieren. Wenn das Problem behoben ist, aktivieren Sie die Plugins einzeln oder in kleinen Gruppen, um den Konflikt zu identifizieren. Sollte das Problem weiterhin bestehen, wechseln Sie zu einem Standardthema wie Twenty Twenty-One, um festzustellen, ob das Thema die Ursache ist. Wir bieten Unterstützung beim Einrichten einer Testumgebung, falls erforderlich.
Bitte beachten Sie, dass diese Lösung möglicherweise veraltet oder nicht auf Ihren Fall zutreffend ist. In diesem spezifischen Fall handelt es sich um ein Problem in WooCommerce, welches bereits an deren Entwicklerteam weitergeleitet wurde. Wir empfehlen zudem dringend, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Wenn das Problem weiterhin besteht, eröffnen Sie bitte ein neues Support-Ticket.
Problem: The client reported an issue where spaces at the beginning and end of text elements in UXBuilder were being removed after translation with WPML. This was observed in both UXBlocks and Pages using UXBuilder, affecting the layout and spacing as intended by the client. Solution: We clarified that the removal of spaces is not specifically related to WPML but is a behavior of WordPress itself. When content is saved or updated using the Gutenberg editor, WordPress automatically removes any leading or trailing spaces in text modules. We recommended testing this behavior on a sandbox site with WPML deactivated to confirm that it occurs even without WPML active. If you're experiencing this issue, we recommend checking this behavior in your setup.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to add new translations using WPML on their development website. Despite existing translations working correctly, any attempt to add new translations, such as German, results in a failure with the message that WPML tried to translate the page three times and failed. Solution: The issue is due to an operational disruption with Amazon Web Services (AWS), particularly affecting services hosted in the N. Virginia region. This disruption is causing certain services to be impaired or unresponsive, which impacts the functionality of WPML. We recommend monitoring the AWS official service health status here: https://health.aws.amazon.com/health/status. We have contacted AWS Support for urgent mitigation and are actively monitoring the situation. We will provide updates as they become available.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
