Documentation request

Problem:
The client is working on a site under development and is trying to use WPML with WP All Import. They are facing issues with automating the WPML export and import process, as it requires manual initiation.
Solution:
We confirmed that the WPML Export & Import add-on does not support automation through cron jobs, webhooks, or custom PHP calls. The import process must be manually triggered. For automating the import process, the client needs to configure WP All Import directly. The WPML add-on only ensures that the multilingual data is correctly structured and mapped during the import. For more details on how to import with WPML Export & Import, please visit WPML Export & Import documentation.

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:
El cliente intentaba traducir el Footer en la versión árabe de su sitio web utilizando el Theme Builder de Divi, como lo había hecho para los idiomas inglés y francés. Sin embargo, encontró un problema donde cada cambio en el Footer árabe afectaba también al Footer en español y viceversa.
Solución:
Primero, verificamos si el cliente había realizado la traducción de strings del Footer, lo cual no había hecho inicialmente porque no lo consideraba necesario. Tras nuestra recomendación, el cliente realizó la traducción de strings y luego pudo modificar el diseño del Footer en árabe sin que afectara a otros idiomas. Para más detalles sobre cómo realizar estas traducciones, recomendamos seguir la guía de compatibilidad de temas en https://wpml.org/documentation/theme-compatibility/divi-builder/.

Si esta solución no resuelve tu problema o parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.

Problem:
The client is working on a site under development and wants to ensure that they are utilizing the translation memory feature in WPML.
Solution:
We explained that WPML offers two types of translation editors: the Advanced Translation Editor and the Classic Translation Editor. The translation memory feature is available only in the Advanced Translation Editor, which is the default on any new WPML installation. If the client sees the Classic Translation Editor when creating a translation, it indicates that the translation memory is not in use. To enable the Advanced Translation Editor, go to WPML > Settings > Translation Editor. However, if translations were already created with the Classic Translation Editor, they would not be migrated automatically to the Advanced Translation Editor and would need to be created again. For a detailed understanding of how the translation memory works, we recommend reading the documentation at How WPML Keeps Track of Your Translations.

If this solution does not apply to your case, or if it 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. We highly recommend opening a new support ticket if further assistance is needed. You can do so at WPML Support Forum.