ATE

Problem:
The client accidentally deleted a WordPress site installed at a subdomain before marking it as moved to the main domain via WPML and removed the old subdomain from their WPML account. On the main domain, they encountered a message indicating the site had moved and were unable to edit translations.
Solution:
1. We asked the client to confirm they had a full site backup.
2. We instructed the client to increase the WordPress memory limit by adding the following code to their wp-config.php file:

This code should be placed above the line /* That's all, stop editing! Happy blogging. */.
3. We provided a guide to help avoid similar issues in the future, which can be found here: Using Advanced Translation Editor when you move or use a copy of your site.

If this solution does not apply to your case, or if it seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
You are translating your site from English to Portuguese using WPML and Elementor Pro Text Editor. Although the Advanced Translation Editor (ATE) identifies and locks internal links with a message that they will be auto-translated later, the links still point to the English version after scanning.
Solution:
1. Ensure that the link fields inside the ATE are locked. When they are locked, WPML will automatically apply internal redirections once the linked content is translated. If you unlock these fields, you must manually translate the URLs.
2. If you are using a text widget that includes an HTML link, WPML might not recognize this as an internal link, and you will need to manually translate it. This is because, currently, WPML handles link fields inside widgets automatically, but not HTML links within text fields.

Please note that this solution might be outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.