Problem: The client is using WPML with the Gravity Forms Multilingual plugin and is facing an issue where form entries cannot be translated. While form labels and sub-labels are translatable, the received submissions cannot be translated natively or during export. Solution: Currently, WPML does not support the translation of form entries directly. We recommend adding a hidden field to collect the language code when the form is submitted. This allows filtering submissions by language. For translating the content of form entries, the client might consider implementing a custom function using the Google Translate API, as WPML does not provide a native solution for this.
If this solution does not fully address your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket here.
Problem: The client is working on a site using WPML's Advanced Translation Editor (ATE) and is facing difficulties managing long pages without certain functionalities. Specifically, they need a filter to display only non-translated strings and a 'validate all' button for strings marked in yellow/orange that require validation. Solution: We have acknowledged the client's request for these functionalities and have forwarded it to our development team for consideration in future updates. If you're experiencing similar issues, we recommend checking our known issues page and ensuring you have the latest versions of themes and plugins installed. If the problem persists or the solution provided here is outdated or not applicable to your case, please open a new support ticket with us for further assistance. Contact WPML support
Problem: You are trying to match posts with multiple languages by uploading CSV files for each language. After importing the English posts as the default language and then importing other languages, the language connections are lost after running WPML > Import and Export > Run Imports. The first import after the default language import is successful, but subsequent imports cause the issue.
Solution: To ensure that the posts remain linked across different languages after import, follow these steps: 1. Import all your languages first before running the WPML Import tool. This prevents the tool from cleaning up 'import-related' data which includes unique IDs and translation groups. 2. If you need to import languages at different times, re-run your previous imports using WP All Import to update the posts and reassign the unique ID before importing a new language. 3. Alternatively, you can add the following code to your functions.php to prevent the removal of import-related metadata:
After all languages are imported, you can remove this filter.
If this solution does not resolve your 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 the problem persists, please open a new support ticket.
Problem: If you're setting up a private Packagist account and are struggling to install WPML using Composer, you might encounter some limitations. Solution: Currently, it is not possible to install WPML using Composer. We have recognized this as a feature request, but due to certain limitations, it has not been implemented yet. For more details, you can refer to a related discussion on our forum: WPML and Composer support discussion.
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. Should you need further assistance, please do not hesitate to open a new support ticket on our support forum.
Problem: The client is experiencing issues with publishing translations of variable products. The translations are not published automatically and remain as drafts. Instead of seeing the translated variable products, the original language version appears. The client has to manually publish each translation by editing the product and switching languages. Solution: We confirmed that this behavior is the default for WPML and not a bug. WPML does not currently support automatic synchronization of translations for variable products. Each translation must be published manually. We have verified this behavior on a fresh installation with the latest version of WPML and on previous versions as well. If you're experiencing this issue, we recommend manually publishing each translation by editing the product and switching languages.
Please note that this solution might be irrelevant if it's 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.
Problem: Sie möchten, dass Kommentare auf Ihrer Website in allen Sprachversionen angezeigt werden. In der deutschen Version werden sie angezeigt, aber nicht in der englischen Übersetzung. Solution: Aktuell unterstützt WPML diese Funktion nicht direkt. Wir empfehlen Ihnen, das kostenlose Plugin Multilingual Comments WPML zu verwenden, das wir auf einer Testseite erfolgreich getestet haben und das wie erwartet funktioniert.
Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen Ihnen auch, die Seite mit bekannten Problemen (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: WPML Support-Forum.
Problem: The client needed to know where WPML saves the Glossary entries in the database and if it is possible to export these entries for use outside of WordPress translations. Solution: We informed the client that Glossary entries are not stored in their site database but are saved on our server. These entries are used when utilizing the Advanced Translation Editor to translate content on our server and can be shared between sites associated with the client's organization. For more details on sharing automatic translations, please visit Automatic Translation Subscription for Multiple Sites. Currently, exporting glossary entries directly from the plugin settings on the client's site is not supported. However, we have noted this as a feature request for future updates. If the client needs to export glossary entries, we can assist them manually.
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.
