Problem: If you're experiencing issues with WPML creating a potential attack vector for MITM attacks by disabling SSL verification on sandbox installs, this is relevant to you. Solution: We recommend updating to WPML version 4.6.11 or later, as well as updating the String Translation. This update addresses and resolves the SSL verification issue in sandbox environments.
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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: Der Kunde verwendet Slider Revolution auf seiner Webseite und bemerkt, dass es keine automatische Übersetzung gibt und unklar ist, welche Inhalte nicht übersetzt sind. Er möchte wissen, ob WPML an einer Lösung arbeitet, die eine automatische Übersetzung ermöglicht, ähnlich wie bei Konkurrenzprodukten. Solution: Wir haben bestätigt, dass es derzeit nicht möglich ist, Inhalte, die mit Slider Revolution erstellt wurden, automatisch zu übersetzen. Diese Information ist auch in unserer Dokumentation unter https://wpml.org/documentation/plugins-compatibility/creating-multilingual-sliders-with-revolution-slider-and-wpml/ zu finden. Wir haben keine Informationen über bevorstehende Updates, die diese Funktion implementieren würden. Wir haben die Anfrage des Kunden als Funktionsanforderung in unser internes System weitergeleitet, damit unsere Entwickler darüber informiert sind. Die Entwicklung und Implementierung neuer Funktionen hängt von vielen Faktoren ab und wird von unserem Entwicklungsteam priorisiert.
Falls diese Lösung für Ihr Problem irrelevant erscheint, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen unter https://wpml.org/known-issues/ 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 unter https://wpml.org/de/forums/forum/support-in-german/.
Problem: The client is trying to fetch a localized string for a JavaScript file in the Gutenberg editor, but the string is not being returned in the current language of the admin screen, even after attempting to switch languages programmatically. Solution: We recommend using the
wp_set_script_translations
function to ensure that the JavaScript file recognizes the localized strings. This involves generating a .json file from the .po file and ensuring it is loaded through a WordPress hook. Here are the steps:
For more detailed guidance, refer to the WordPress documentation on how to handle internationalization in block editors: Internationalization in Gutenberg.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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. Additionally, you can open a new support ticket for further assistance at WPML Support Forum.
Problem: You are a website designer using WPML and have connected all your sites to share a single pool of credits, which results in shared translation memory and glossary across all sites. You are looking for a way to share credits but keep the translation memory separated by website. Solution: Currently, there is no option available to share credits while keeping translation memories and glossaries separate for each website. All connected sites to a specific automatic translation account will share the glossary, credits, and translation memory. We have noted your request and will mention it to our developers as a potential feature for future updates.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is trying to set up language definition by IP on their site using WPML, but WPML does not support this functionality natively. Solution: We recommend using a third-party IP geolocation plugin or developing a custom solution to achieve language redirection based on IP address. For more details on how to implement this, you can refer to a similar discussion in our forum: https://wpml.org/forums/topic/country-based-redirect/#post-4843377. If you encounter difficulties with the implementation, consider hiring a professional from our list of recommended contractors: https://wpml.org/contractors/.
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 these steps do not resolve your issue, please open a new support ticket for further assistance: Contact WPML Support.
Problème : Le client travaille sur le site en utilisant WPML et cherche à accéder aux phrases non validées dans l'ATE pour terminer la traduction. Il souhaite pouvoir filtrer les phrases non encore traduites directement dans l'ATE, similaire à l'ancienne fonctionnalité de l'éditeur classique V1. Solution : Nous avons suggéré d'utiliser les outils de navigateur ou une extension de navigateur pour modifier la classe CSS
.AT-segment_list__add_translation_container
. Cette classe est présente uniquement sur les blocs en attente de traduction, permettant ainsi de les mettre en évidence en changeant la couleur d'arrière-plan. Nous avons recommandé l'extension Chrome Visual CSS Editor qui permet de modifier les paramètres CSS de ces éléments sans coder.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous invitons à consulter les problèmes connus, vérifier la version des correctifs et vous assurer que vous avez les dernières versions des thèmes et plugins installés. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: The client created a custom Elementor widget containing an image, headline, and text, and encountered an issue where the image did not change when switching languages, despite using WPML's Media Translation. Solution: We recommended the following steps to resolve the issue: 1. Ensure that the image within the custom Elementor widget is stored as a URL and that the URL field is registered for translation in the XML configuration. 2. Make a small update to the source page and save the changes. 3. Update the translation and use the Advanced Translation Editor to search for the image URL. If found, replace the URL with the correct image URL for the desired language. 4. If the URL does not appear in the translation editor, it's possible that the widget and its configuration need further adjustments. We suggested replicating the issue in a WPML sandbox environment to further diagnose the problem. 5. If manual translation of the image URL is required, consider integrating the Elementor widget with WPML Media Translation using a custom integration class, which may require hiring a developer proficient in WPML.
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.
Problem: The client is trying to set up the Euro currency for different countries on their WooCommerce site, such as France, Germany, and Italy, with different shipping fees for each. They encountered an issue where they could not create multiple instances of the Euro currency for different countries using the WooCommerce Multilingual plugin. Solution: We explained that if the currency is set based on the Site Language, only one currency per language can be configured. However, by basing the currency on the client's location, it's possible to assign a specific currency to multiple countries. We recommended using the geolocation feature, which allows users from specific countries to see the corresponding currency. For detailed steps on setting this up, we advised checking the guide on multi-currency support in WooCommerce.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Additionally, 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. For further assistance, feel free to contact us at WPML support forum.
Problem: You are working on a multilingual website using WPML and bbPress, aiming to automatically translate and publish user-generated content (topics and replies) in multiple languages. However, the current setup only allows automatic translation for content created in the primary language. Solution: Currently, it is not possible to automatically translate and publish user-generated content in several target languages using WPML without manual intervention. You can use the "translate automatically" button in the translation editor for individual posts, but these must be opened and sent manually. Automatic batch translation for user-generated content is not supported at this time.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise checking the related 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.
