Problem: The client is facing two issues: unable to use 60000 credits for automatic translation and encountering an error when switching from Greek to English related to the function
_load_textdomain_just_in_time
. The error indicates that the translation loading was triggered too early. Solution: 1) The error related to
_load_textdomain_just_in_time
is a known issue in WordPress and not specific to WPML. It can occur even if WPML is disabled. For more details, please visit WPML Errata. 2) To address the issue with using credits for automatic translation: - Navigate to WPML > Support > Troubleshooting. - Click on "Synchronize local job ids with ATE jobs" and "Synchronize translators and translation managers with ATE". - Resend the page for translation from WPML > Translation Management. - Go to WPML > Translation, take and translate the job.
If these steps do not resolve your issues or if the solution seems outdated or irrelevant to your 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. If the problem persists, please open a new support ticket at WPML Support Forum.
Problem: After moving the site to a new domain, the client experienced issues with WPML settings and translation mappings. They were unable to select translations on the mapping page, and some Advanced Custom Fields (ACF) were not displaying after changing the language. Solution: We first confirmed the details of the previous domain and ensured that the site was properly migrated without active WPML subscriptions on the old site. We then checked the WPML configuration on the new domain. For the disappearing ACF fields, we noted that translating the Field Groups post type is not recommended as per our documentation, which can be found here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/.
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 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 do not hesitate to open a new support ticket at our support forum.
Problem: El cliente intenta activar solo la traducción con AI en WPML, pero no aparece el botón de traducir automáticamente el post completo. Además, el botón de traducción automática no funciona a menos que active Google. Solution: Primero, es importante verificar que al menos un motor de traducción esté activo para que la opción de traducción automática funcione correctamente. En WPML -> Configuración, el cliente debe asegurarse de que Google, DeepL o Microsoft estén activos. Si solo está activo WPML AI y no funciona, es probable que se deba a que WPML AI y DeepL no soportan el idioma Gallego. Para confirmar esto, el cliente puede ir a WPML -> Translation Management -> Pestaña 'Tools' -> Sección 'Language mappings' y verificar los idiomas soportados por cada motor de traducción.
Si la solución proporcionada no resuelve el problema o si la información parece desactualizada, recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y asegurarse de que todas las versiones de temas y plugins estén actualizadas. Si necesita más ayuda, puede visitar nuestro foro de soporte.
