Problem: Meta is setting up multiple WordPress sites and wants to register their internal Localization system as a Translation Service that can integrate with WPML via API. Solution: To register your localization system as a Translation Service with WPML, you need to contact our Translation Partner team. You can apply to join the WPML Translation Service Partner Program by filling out the form available at https://wpml.org/documentation/content-translation/#application-process. After submitting the form, the Translation Partner team will review your request and guide you through the integration process.
If this solution does not resolve your issue or 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problema: Si estás intentando importar traducciones de un documento PDF a tu sitio web multilingüe en WPML, es importante saber que WPML no puede procesar archivos PDF directamente porque necesita datos estructurados y segmentados. Solución: Debes convertir el PDF a un formato compatible como XLIFF, CSV o XML utilizando herramientas externas o un flujo de trabajo personalizado. Asegúrate de que la conversión preserve o te permita añadir la estructura y los identificadores necesarios (como el slug o ID de la página, el SKU del producto, etc.) para vincular correctamente el contenido en búlgaro con el contenido existente del sitio.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: The client translated over 20 pages automatically with a review process, but seven of these pages could not be reviewed or published. When attempting to preview the translations by clicking the eye icon, the client was redirected to the Advanced Translation Editor instead of the frontend. Additionally, the translation queue page was loading but then displayed nothing, and the main translation management page showed no review buttons. Solution: We resolved a recent incident that caused downtime in the Advanced Translation Editor (ATE), which has now recovered. For the specific case of the product '550 Schokoladenmasse 55/45/30' and similar issues, we recommend the following steps: 1. Open the product in edit mode in the original language. 2. Use the language switcher to open the English version. 3. Choose to edit with ATE. 4. After updating and saving the content via the translation workflow, use the preview link to preview the translation and then publish it.
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 open a new support ticket at WPML support forum.
Problem: Auf der .at-Domain wurden teilweise englische Strings, WooCommerce-Seiten und System- bzw. WooCommerce-E-Mails auf Englisch angezeigt, obwohl Deutsch als Standardsprache festgelegt war und deutsche Übersetzungen vorhanden waren. Zusätzlich wurde bei der automatischen Übersetzung gemeldet, dass Deutsch (Austria) nicht unterstützt wird. Solution: Die Lösung bestand darin, eine eigene Sprachdatei für Deutsch (Austria) zu erstellen und diese über Loco Translate zu hinterlegen. Dadurch wurden die WooCommerce-Seiten sowie die System- und E-Mail-Texte korrekt in Deutsch (Österreich) ausgegeben, und es erschienen keine englischen Inhalte mehr auf der .at-Domain.
Wenn Sie ähnliche Probleme erleben, empfehlen wir Ihnen, eine eigene Sprachdatei für Ihre spezifische Sprachvariante zu erstellen und diese entsprechend zu hinterlegen. Es könnte sein, dass diese Lösung veraltet ist oder nicht auf Ihren Fall zutrifft. Wir empfehlen Ihnen daher, 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. Sollten weiterhin Probleme bestehen, öffnen Sie bitte ein neues Support-Ticket.
Il problema verrà risolto nella versione 4.9.2. (Troppo tardi per la versione 4.9.1, in uscita a breve.)
Problem: The client is attempting to use a custom translation service with WPML, but it does not appear in the Translation Services list. They have set
WPML_CUSTOM_TRANSLATION_SERVICE_URL
in wp-config.php to point to their custom Translation Proxy API, which implements the WPML Translation Proxy API (JSON:API). Despite this setup, the custom service is not visible under WPML → Translation Dashboard → Translation Services. The client also noted that the “Enable other translation services” button is not visible under WPML → Support → Troubleshooting, and they do not have a Preferred Translation Service set in their wpml.org account.
Solution: We informed the client that currently, there are no plans to make custom translation services available outside of the Partner program. As alternatives, we recommended considering the following options:
Translation Hub: A centralized interface for managing translations and translators.
Automatic Translation: Built-in machine translation with flexible pay-as-you-go options.
We also mentioned that we will soon announce the PTC (Private Translation Cloud) Partnership program for Agency accounts, which will provide benefits for those accounts regarding site translations.
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 further assistance is needed, please open a new support ticket.
Problem: The client configured WPML on WordPress for English (en) and Spanish (es) languages. However, when attempting to send a translation job to Smartling, it appeared as successfully sent on WordPress, but an error message indicated an issue with sending the jobs. The error message stated that the service does not support translation from English. Solution: We escalated the issue to our 2nd Tier Support who discovered that the problem was due to incorrect language mappings. After updating the mappings to the correct settings, the issue was resolved. We recommend checking your language settings and ensuring they are correctly mapped.
Please note that this solution might be outdated or not applicable to your specific case. If this solution does not resolve your issue, 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: You are unable to find the option to use DeepL as a translation service for the Spanish (Mexico) language variant. Solution: We recommend verifying the list of supported languages by DeepL and other translation engines here. For Mexican Spanish, you should use WPML’s Professional Translation Cloud (PTC), which is the default engine for WPML Automatic Translation and supports dialect-specific language variants, including Spanish (Mexico). Ensure that Automatic Translation is enabled and that WPML is set to use the PTC engine. If you need to translate content, you can either use the Advanced Translation Editor by clicking the plus icon or send the page for automatic translation via WPML → Translation Dashboard. Select the page, choose the target language, and send it for automatic translation.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related 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.
