Problem: You attempted to translate a page, but encountered an error stating that WPML cannot send some of the content for translation because it includes fields that are encoded. As a result, these fields were removed from the translation job. Solution: We have escalated this issue to our development team for further investigation. Meanwhile, we recommend you follow the workaround provided to handle pages with base64 encoded content. You can find detailed instructions on how to proceed by visiting the following link: WPML cannot send base64 encoded content to translation.
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: If you're experiencing issues with your translated page templates still displaying in the original language, or inconsistencies with the language selector, the issue might be related to the slug of the translated template. Solution: First, check if adding a "-2" to the slug of your translated template occurs by referring to our documentation on this specific issue: Template is not applied to translated page. If this is the case, removing the "-2" from the slug should resolve the problem. We are aware of this behavior and plan to make improvements in future releases to prevent similar issues.
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. If issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are working on a preproduction website and encountering issues with automatically translating pages because the plugin indicates that the pages are encoded. Solution: We recommend using the workaround provided in the this documentation. If this solution does not resolve your issue or seems outdated, 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 encourage you to open a new support ticket for further assistance at WPML support forum.
Problem: After migrating a site, TRANSLATE-mode custom fields fail to sync to wp_postmeta due to the FilterJobUrlMigration component in WPML. This component incorrectly handles non-base64 encoded field_data, leading to data corruption and loss of custom field values in the translated post. Solution: Until this issue is resolved, you can avoid the problem by:
- Sending content for translation directly from the post edit screen, or
- Sending content from the post list screen using the + icon.
It also works if your content is being translated with Translate Everything Automatically.
If these solutions do not resolve your issue or seem 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 for further assistance.
as malicious after updating the string translations plugin, this is identified as a false-positive. Solution: We have confirmed that this is a false-positive warning by Wordfence. A fix for this issue is scheduled for the next WPML release. For more details, you can visit our errata page: https://wpml.org/errata/wordfence-reports-a-false-positive-security-warning-with-wpml-4-9-0/
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 open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue installing WPML in a Bedrock + Composer setup due to the inability to access the official WPML Composer repository at https://packages.wpml.org/packages.json. The error reported is 'curl error 6: Could not resolve host: packages.wpml.org', and DNS resolution for packages.wpml.org fails (NXDOMAIN). Solution: We currently do not support installation or updates of WPML via Composer natively. There is no official or supported method to automatically fetch the latest WPML versions via Composer. However, a suggested workaround is discussed in a forum thread, which can be found here: https://wpml.org/forums/topic/composer-update-to-latest-plugins-versions/. Additionally, you can refer to our errata entry here: https://wpml.org/errata/composer-installation-of-wpml-not-officially-supported-yet/. A third-party project that might help is available at https://github.com/ffraenz/private-composer-installer, where the version can be handled as a placeholder.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 contact us through the WPML support forum.
Problem: The client reported a critical security alert from Wordfence concerning a file in the wpml-string-translation.3.5.0 update, identified as potentially malicious or unsafe. The file in question is located at wp-content/plugins/wpml-string-translation/lib/StringScanning/vendor/wp-cli/wp-cli/features/context.feature, and it is flagged as a backdoor with suspicious modifications. Solution: We have identified this issue as a false-positive warning by Wordfence. This will be addressed and resolved in the upcoming WPML release. For more details, please visit our errata page at https://wpml.org/errata/wordfence-reports-a-false-positive-security-warning-with-wpml-4-9-0/.
If this solution does not seem relevant to your case, or if it appears 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 WPML support forum.
Problem: Nach der Migration von Divi 4 auf Divi 5 treten Probleme bei bestehenden Übersetzungsaufträgen auf, einschließlich der Unmöglichkeit, Aufträge zu übersetzen oder zu löschen, sowie 'Critical Errors' bei einigen Übersetzungen. Solution: Die Migration von Divi 4 zu Divi 5 verändert die interne Datenstruktur der Inhalte, wobei Inhalte von verschachtelten Shortcodes zu einem JSON-basierten Format wechseln. Dies kann Probleme bei alten Übersetzungs-Jobs verursachen, die noch auf der alten Shortcode-Struktur basieren. Um diese Probleme zu beheben, empfehlen wir: 1. Versuche, die hängenden Jobs unter WPML > Translation Dashboard > Jobs abzubrechen. 2. Wenn das nicht funktioniert, erstelle neue Übersetzungsaufträge für die betroffenen Inhalte unter WPML > Übersetzungsdashboard. 3. Eine weitere Möglichkeit könnte sein, die originalen Inhalte in Divi zu bearbeiten und erneut zu speichern, um die Struktur zu aktualisieren. Weitere Informationen zur Kompatibilität und Migration findest du hier: https://wpml.org/errata/divi-5-wpml-compatibility-while-new-features-are-being-released/
Falls diese Lösungen dein Problem nicht beheben oder die Informationen veraltet erscheinen, empfehlen wir, einen neuen Support-Ticket zu öffnen. Wir empfehlen 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 du die neuesten Versionen von Themes und Plugins installiert hast.
Problem: The client reported that Google only indexes the English pages of their multilingual site, even when manually indexing other languages. The '/EN/' slug appears despite other languages being set up, and WPML is configured correctly.
Solution: We recommended the following steps to address the issue: 1. Ensure the WPML SEO Add-on is active by checking under Plugins → Installed Plugins. If not present, install and activate it from Plugins → Add New → Commercial tab. 2. Verify the presence and correctness of 'hreflang' tags on translated pages by viewing the page source and searching for 'hreflang'. 3. Check the WPML's Language URL format under WPML → Languages and ensure 'Different languages in directories' is selected. 4. Disable the Browser Language Redirect temporarily under WPML → Languages to avoid confusion during indexing. 5. Re-save permalinks under Settings → Permalinks and re-submit sitemaps in Google Search Console.
Additionally, we advised against using the Browser Language Redirect feature as it does not distinguish between users and search engine bots, which can affect SEO and indexing. This is documented in our guides:
If these steps do not resolve the issue or if the information seems outdated, we highly recommend opening a new support ticket. Also, 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, please visit our support forum.
Problem: The client updated internal links and content in posts, resulting in up to 50% of segments showing an orange bar and being untranslated or needing re-approval. This issue did not occur previously and was suspected to be related to recent server issues. Solution: The issue was due to the site not being properly registered and migrated between different environments (WPML test site, staging site, and production site). The site was moved, creating a new entry instead of copying the existing translation memory. We resolved this by manually merging the translation memory of all site organizations into the current one. The client should now cancel any affected 'In Progress' jobs at WPML > Translation Dashboard > Jobs, and create new jobs for the affected contents at WPML > Translation Dashboard. Assign the translations to yourself and access them at WPML > Translations. We have already applied this solution to the 'Best of Nightlife and Bars in La Spezia' and confirmed a 100% completed translation on ATE. Please verify if the issue is resolved by creating new translation jobs, as changes might not be visible on jobs currently in progress.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at WPML support forum.
Problem: Il cliente ha riscontrato due problemi critici nel sito multilingue: 1. Le variazioni WooCommerce non appaiono nella versione spagnola del sito. 2. I campi personalizzati del plugin Advanced Product Fields for WooCommerce non sono traducibili in WPML. Solution: Per il primo problema, abbiamo suggerito di verificare che i prezzi siano sincronizzati e di utilizzare gli strumenti di "Risoluzione dei problemi" in WooCommerce Multilingual per sincronizzare le variazioni e rigenerare le tabelle di ricerca. Per il secondo problema, abbiamo identificato che il campo _wapf_fieldgroup può essere impostato su 'Copy' per copiare il gruppo di campi nel prodotto tradotto. Tuttavia, i label, le istruzioni e i placeholder dei campi non possono essere tradotti con WPML a causa della loro struttura interna serializzata.
Se questa soluzione non risolve il tuo problema o sembra non essere più attuale, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di controllare le questioni note e di verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Per assistenza ulteriore, visita il forum di supporto WPML.
Problem: When editors add and crop a featured image to an original post, the translated post does not receive the cropped version of the featured image. This issue persists despite expectations for a fix in version 4.7. Solution: We have confirmed that this is a known limitation where image metadata does not sync after edits to attachments that already have translations. Currently, there is no immediate development scheduled for this issue due to its complexity and relatively low impact. We recommend using the suggested workaround available at https://wpml.org/errata/cropped-featured-image-not-displayed-in-translations/.
If this solution does not apply to your case, or if it seems outdated, we encourage you to 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, please visit our support forum at https://wpml.org/forums/.
