Problem:
If you're experiencing a page that is loading non-stop when trying to edit a translation, it might be due to invalid HTML within code modules on the page.
Solution:
To fix this issue, we recommend you:
1. Edit the page and both code modules.
2. Remove all style sheets from the code modules and add the CSS to the Divi theme options or the theme's style.css file.
3. Ensure that only the content within the body tags is present in the code modules. For example, you should only include the necessary HTML elements, such as:
4. Save the page after making these changes.
5. Go to WPML → Translation Management and resend the page for translation, or make a slight change to the original page, save it, and then navigate to the translation editor.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket with us.
Problem: The client is manually translating a page using WPML, but despite completing the translation, the page keeps loading and does not create the translated version. The client also mentioned issues with enabling the REST API on the staging site, which is necessary for the Advanced Translation Editor to function properly. Solution: 1. We recommended checking if the 'REST ENABLE' option is activated on the server as it might be causing the issue with the Advanced Translation Editor. For detailed instructions on how to enable and troubleshoot REST API dependencies, visit WPML REST API Dependencies Documentation. 2. If the REST API is confirmed to be working but issues persist, we suggested checking the server resources as gateway timeout errors can interrupt the translation process. 3. We advised the client to contact their hosting provider if they continue to experience issues with the REST API functionality.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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. If problems persist, please open a new support ticket.
