Problem: There is an issue with the String Translation table on your site, which could potentially become a critical problem in the future. Solution: If you have not yet created any translations, we recommend resetting WPML and configuring it again from scratch. You can find step-by-step instructions on how to perform a WPML reset here. Please ensure to create a full backup of your database before making any changes.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also 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 contact us directly through our support forum.
Problem: The client was unable to translate various elements of their website using WPML, including the footer created with Elementor, product pages, and specific buttons on the wishlist page. The website uses the XStore theme and WooCommerce. Solution: We identified that the XStore Core plugin was overriding the language settings, causing it to default to Greek even on English pages. We resolved this by adjusting the plugin settings: 1. Navigate to the XStore Control Panel. 2. Go to XStore Built-In Translations. 3. Set the Site language to English.
This adjustment should reflect the correct language across the site, as demonstrated on the updated wishlist page. If this solution does not resolve your issue, or if it seems outdated, we recommend checking for related 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.
Problem: The client reported that after using WPML's automatic translation feature, some pages displayed blank content (post_content) on the front end, even though the translation appeared complete in the Advanced Translation Editor (ATE). No PHP errors were logged, and the issue persisted even after database changes. The problem occurred when editing auto-translated pages where only part of the text was editable in the Translation Editor, and the uneditable text reverted to English. Solution: We recommended re-initiating the automatic translation from the Translation Dashboard. This approach ensured that the full text appeared in the Translation Editor and the translation was correctly reflected on the displayed page. Additionally, we suggested verifying that all WPML plugins are up-to-date to avoid similar issues, as outdated plugins or errors in the ATE logs could contribute to such problems.
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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with your logo not updating on the frontend after publishing changes in the WordPress Customizer, and this only occurs when WPML String Translation is active, the issue might be due to a manually created translation within String Translation that overrides the selected logo ID for a specific language. Solution: We recommend checking WPML String Translation for any manually created translations related to your logo. Specifically, search for entries like 'Logo' or the attachment ID of your logo. If found, delete these translations to ensure that the correct logo ID is used across all languages. This should resolve the issue where the old logo continues to appear despite updating to a new one.
Please note that 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: Sie haben eine Abbuchung von 50,31€ erhalten und finden keine entsprechende Rechnung dazu. Solution: Die Abbuchung ist die Verlängerungsgebühr für ein älteres WPML Multilingual CMS-Konto. Der Betrag von 50,31 € entspricht dem früheren CMS-Verlängerungspreis. Diese Gebühr wurde unter einem anderen Konto mit der E-Mail-Adresse stefan@moonflag.de registriert. Die Rechnungs-ID für diese Transaktion ist 17823201. Bitte überprüfen Sie, ob Ihnen das Konto bekannt ist und ob beide Konten weiterhin benötigt werden.
Falls diese Lösung für Sie nicht relevant ist oder veraltet erscheint, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, 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.
Problem: Your site, built with Divi, functions correctly in the main language, but the translated pages have issues such as missing animated text, non-functional sliders, and other plugins not working. Solution: We reviewed your website and found that the translated pages are displaying correctly, including the animated text and sliders. The problem you encountered might have been related to cache issues. We recommend clearing your browser cache to resolve this. If you're experiencing this issue, try clearing your browser cache and check the pages again.
If the solution provided here becomes irrelevant due to updates or does not apply 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 these steps not resolve your issue, please do not hesitate to open a new support ticket with us for further assistance at https://wpml.org/forums/forum/english-support/.
Problem: The client needs to restrict translators from modifying source pages while allowing them to edit translations in a multi-language WordPress site. The translators currently have sub-admin status, but reducing their role to editor did not achieve the desired limitation. Solution: We found that the desired behavior of restricting translators to only modify their target language pages without affecting the source language pages is not achievable using standard WPML or WordPress user roles. However, we recommend exploring third-party plugins that are WPML compatible and might offer the needed functionality. One such plugin is WP User Manager, which you can find here: https://wpusermanager.com/. Additionally, we suggest checking the Toolset Access plugin, which is supported by us and might help in setting up specific editing permissions for different languages. You can learn more about this plugin here: https://wpml.org/documentation/translating-your-contents/how-to-use-access-plugin-to-create-editors-for-specific-language/. Please ensure to test these solutions in a staging environment or have a backup if testing in production.
If these solutions do not resolve your issue or if they become 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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: The client reported that the text-domain "divi-bang" in their theme was not displaying translations correctly on their website, despite previously functioning well. The issue was isolated to specific pages, and the client wanted to avoid manually changing all text-domains in the theme. Solution: We reviewed the client's website and accessed the String Translation section. We located the string "H1 Erreur 404" and successfully translated it into English, which resolved the display issue on the page: https://cepexperts.staging.tempurl.host/wpml. The problem might have been caused by the string translations not being saved to the translation files, possibly due to hosting restrictions or configuration issues. Additionally, we advised the client to check their child theme's configuration, particularly ensuring that the text domain is correctly defined, as per the WordPress developer documentation: https://developer.wordpress.org/themes/core-concepts/main-stylesheet/.
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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
