Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is unable to perform translations due to errors related to the 'Default translation engine' failing to load and issues copying translation information to a new URL after migrating a site manually using an SQL file.

Solution:
1. Ensure the 'WPML String Translation' plugin is installed and enabled as it is necessary for using the Advanced Translation Editor and for translating strings from ACF, Yoast SEO, themes, or other plugins.
2. When encountering issues with fields not showing up for translation, verify that each field name is unique across various blocks or field groups. More information on this can be found here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/
3. For errors related to URL mismatches after site migration, try editing the original content, saving it, and running the translation again. If the issue persists, it may be due to completing a job on one site URL and reviewing it on another, leading to URL errors.

If these steps do not resolve your issues or if the solution seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 18 replies, has 1 voice.

Last updated by Andreas W. 1 month, 2 weeks ago.

Assisted by: Andreas W..

Author Posts
July 8, 2025 at 10:23 am #17213009

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Please always name exact examples, including the URL of a post or page where we can see the issue.

---

I can see a few issues, for example, with some heading fields.

Note that each field name should always be unique. If you use the same field name "heading" in various blocks or field groups, you might run into issues with strings not showing up for translation on the Advanced Translation Editor.

We mention this issue in our docs here:
https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/

July 11, 2025 at 10:34 pm #17229430

christopherH-36

Hi, I updated some of the field names that were conflicting.
It seems to be working now.

I'm experiencing another issue by the way. I re-did the translation of the About Us and now the review button just loads infinitely and it doesn't show the translation view.

The page is currently in the translations queue. There is an error in the console saying something about "jobs"? Can you tell me what is causing this and how to avoid this moving forward? I feel like i've encountered this issue often and it just randomly happens.

Thank you so much

Screenshot 2025-07-12 063437.png
Screenshot 2025-07-12 063027.png
July 11, 2025 at 10:42 pm #17229459

christopherH-36

Hi nevermind, it fixed itself on its own I'm not sure what I did.
Is there a feature in the wpml>troubleshooting area that I can run to fix this type of issue?

July 12, 2025 at 8:17 am #17229854

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hi,

Not really, there are only a features inside the troubleshooting section to sync translators and jobs for the Advanced Translation Editor, but the issue in your screenshot looks like a URL issue.

Usually, these errors occur if you, for example, complete a job on one site URL, but you did not make the review, and then you migrate the site to another server. On the new server, WPML will throw a URL error because the review is coming from another site.

Usually, editing the original content, saving it again, and letting the translation run through again should solve this.

If such an error occurs again, please let us know.