ATE

Issue:
You are trying to translate a page and you are receiving an error message saying: 'WPML attempted to translate this page three times and failed'.
Solution:
The issue was caused by a fatal error during the page translation process due to a theme custom field, _fusion, being incorrectly set to "Translate" instead of "Copy". To resolve this, we have changed this setting in WPML → Settings → Custom Field Translation to "Copy" as it does not contain information that requires translation. Additionally, we canceled the pending translations in WPML → Translation Management → Jobs, made some minor adjustments to the original page titled "Natural Therapies", and then navigated to the translation editor to complete the translation.

If this solution doesn't resolve your issue or doesn't seem to be relevant because it's outdated or doesn't apply to your case, we recommend opening a new support ticket. We also suggest reviewing the known issues, checking the version of the permanent fix, and confirming that you have the latest versions of themes and plugins installed. For additional assistance, please visit our support forum.

Problem:
If you're experiencing issues with automatic translations for 'other strings' not working on a subsite within a WPML-powered multisite network, and encountering errors such as 'Service Unavailable' or 'Api error missing resource: No sitekey found for this website', it might be due to a site key issue.
Solution:
We recommend following these steps:
1. Ensure that each subsite has its own site key. If unsure, create a new site key specifically for the subsite.
2. Visit https://wpml.org/account/sites/ and check if the subsite is registered. If it is, remove it.
3. Navigate to the subsite's admin panel, go to Plugins -> Add new -> Commercial tab.
4. Unregister the subsite and then register it again with the new site key.
5. Verify if the issue with automatic translations has been resolved.

If these steps do not resolve the issue or if the solution 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 open a new support ticket at WPML support forum for further assistance.

Problem:
The client is experiencing a fatal error when trying to automatically translate a Custom Post Type (CPT) post created with JetEngine using the WPML Multilingual CMS plugin. The error message indicates a 'TypeError: array_diff(): Argument #2 must be of type array, string given' in the WPML plugin's custom field synchronization script.
Solution:
We recommend the following steps to resolve the issue:
1. Navigate to JetEngine -> Post Types.
2. Edit the Events post type.
3. Disable the "Custom Meta Storage (Beta)" option.
4. Update the Post Type.
5. Edit an Event post in the default language.
6. Make a minor edit and update it.
7. Update the translation.

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 the problem persists, please open a new support ticket.

Problema:
Estás traduciendo páginas de listados de bienes raíces y las páginas traducidas no aparecen. Además, al seleccionar otro idioma como español o francés, te redirige a la página de inicio en lugar de a la traducción correspondiente.
Solución:
1. Edita la página en cuestión en el idioma predeterminado.
2. Realiza una pequeña edición y actualiza.
3. Accede a la traducción nuevamente.
4. Completa la traducción al 100% y guarda.
Si sigues estos pasos y el problema persiste, es posible que se deba a que anteriormente se utilizó el editor ATE con traducción automática y ahora se ha cambiado al editor de WP. Estos editores no comparten traducciones, lo que podría estar causando el problema de visualización.

Si la solución proporcionada no resuelve el problema o parece no ser relevante debido a que está desactualizada o no se ajusta a tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos relacionados, verifiques la versión del arreglo permanente y confirmes que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, puedes visitar nuestro foro de soporte.