Background of the issue:
I am trying to translate extensive Elementor pages using WPML, with around 250 items needing translation. The complexity of these pages results in a larger DOM size. We have implemented a workaround by using templates to split page content, making translation easier. I suspect some custom code might also be contributing to the problem.
Symptoms:
Elementor pages are unable to save translations, potentially due to the high number of elements. WPML’s health check shows all indicators in the green, but there is a single ATE error related to authentication in the debug log.
Questions:
Is there a specific limit on the number of elements that can be translated with WPML and Elementor?
Is there a better way to verify the issue with saving translations?
I would like to ask you to share the error message (or a screenshot where the error can be seen) so we can gather more information about this behavior.
Also, could you tell me if the issue doesn't happen with a new (smaller) test page?
Hola Carlos, thank you for answering. As for error message there is no error message displayed. It reloads the page overview page, and still keeps it in the settings wheel (not the pen icon), and then the elements are simply not translated.
Best regards
Oly
1.- I would like to reproduce the issue on the site to obtain more information about it. I have set your next message private so you can securely share the access credentials to the site.
Please don't forget to create a full backup of the site before sharing the credentials.
2.- Also, I kindly ask you to share the page URL where the issue can be seen.
Hola Carlos, thank you for your response. Due to data privacy reasons it's more difficult for me to give out the site access. Do you have also a more general answer? Something like "WPML works for pages of a DOM size of X" or considering another metric?
To be able to provide an answer I would need to activate the debug log and check if there are any errors, especially PHP limitations, and get one of the ATE translation jobs URLs to check on our side.
Is it possible for you to create a staging site with a copy of the live site and give us access to run all these tests without affecting the production site?
