Skip Navigation

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

Problem:
You are trying to create a translation job by assigning content to a translator, but the job does not appear in the translation queue of the assigned translator, despite having up-to-date plugins and themes, and correct translation languages set for the translator.
Solution:
We discovered that the issue was due to the MySQL database having the SQL mode ANSI_QUOTES enabled, which caused WPML queries to misinterpret string literals. To resolve this, you can add the following code to your

functions.php

file:

$wpdb->set_sql_mode(['ONLY_FULL_GROUP_BY', 'ERROR_FOR_DIVISION_BY_ZERO', 'NO_ENGINE_SUBSTITUTION']);

This workaround adjusts the SQL mode settings to prevent the misinterpretation.

**** Important! Please make a full site backup (files and DB) before you proceed with those steps****

If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.

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 10 replies, has 1 voice.

Last updated by Itamar 3 weeks ago.

Assisted by: Itamar.

Author Posts
April 16, 2025 at 11:25 am #16937747

benjaminA-35

Background of the issue:
I am trying to create a translation job by assigning content to a translator. The job appears in the translation jobs list but not in the translation queue of the assigned translator. My plugins and themes are up-to-date and I have all plugins except WPML disabled. I've Also checked that the assigned translator has the correct translation languages set. Trying out options from the "Troubleshooting" page inside the plugin hasn't helped either so far.

Symptoms:
The translation job does not appear in the translation queue of the assigned translator.

Questions:

April 16, 2025 at 11:32 am #16938311

Waqas Bin Hasan
WPML Supporter since 05/2014

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Reference to our recent chat, meanwhile this ticket is attended by one of my colleagues I request temporary access (WP-Admin and FTP), preferably to a test site where the problem has been replicated.

Your next answer will be private, to share this information safely.

Also provide detailed steps to reproduce the issue and links to pages in the admin and on the frontend.

IMPORTANT: Please take a complete backup of the site to avoid data loss. We may need to activate/deactivate plugins also.

See https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ for details on privacy and security.

P.S.: If you don't see the section for providing access information, do not write in the message box or the information may appear as public.

Regards.

April 20, 2025 at 8:57 pm #16950297

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

You are using a WordPress multisite installation; however, WPML is not enabled on your multisite system. Please see the attached screenshot. To learn how to work with WPML in a multisite environment, please read our guide here:
https://wpml.org/documentation/support/multisite-support/
Moreover, there is a message saying this:

Some communications with the translation proxy are locked.

The constant WPML_ENVIRONMENT is set to "Test".

Can you please explain what the WPML_ENVIRONMENT constant is?
It is not one of our contents. You can see the list of our constants here:
https://wpml.org/documentation/support/wpml-coding-api/wpml-constants/

There is a strange situation on your site where WPML is not enabled. However, the WPML admin menu is displayed. I suspect that your WordPress site has some custom configurations. Do you know about any such configurations?

Regards,
Itamar.

2025-04-20_23-43-44.jpg
April 22, 2025 at 7:51 am #16953467

benjaminA-35

Hi,

the plugin is now enabled on the multisite blogs and the WPML_ENVIRONMENT variable is now removed. The site is also correctly registered in the multisite settings ( see screenshot ). To my knowledge we don't have any custom configurations currently active that could affect WPML.

Regards.

Bildschirmfoto 2025-04-22 um 09.15.55.png
April 22, 2025 at 8:03 am #16953556

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi, and thanks for trying my suggestions.

For things to work correctly, you should also activate the Strings Translation add-on. It is WPML's leading add-on. Currently, I can see it is not active on your site.

Regards,
Itamar.

April 22, 2025 at 9:37 am #16954076

benjaminA-35

Hi,

the Strings Translation Plugin is active now.
I hope that helps.

Regards

April 23, 2025 at 2:50 pm #16960719

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I can see the problem on your site. In WPML -> Translation Management -> Translation Jobs, I assigned one job to my user, 'wpml'. Please see the attached screenshot. And then in WPML -> Translations, I can't see it.

I checked the Advanced Translation Editor Error Logs and found this error:
Api error missing resource: No sitekey found for this website

I have checked our system, and it appears that you are using an outdated site key.
The current relevant site key is: AcIwbmVifh
Can you please register the site with the above key?

1. Go to your account here https://wpml.org/account/sites/

2. Delete any other instance of this site's registration.

3. On your main network site, unregister the site.

4. Press the 'Register this site' option.

5. This will open in a new tab, https://wpml.org/account/sites/.

6. Copy the new site key and add it to the field on your site.

Please see our guide on registering WPML on a multisite installation.

https://wpml.org/documentation/support/multisite-support/#register-wpml-multisite

Note that you need to register the main network site.

Is hidden link your main network site?

Please let me know if it helps.

Regards,
Itamar.

2025-04-23_17-22-07.jpg
April 24, 2025 at 7:41 am #16962863

benjaminA-35

Hi,

i have now recreated the sitekeys and reregistered them in the multisite settings under Plugins > Add Plugin > Commerial. The new sitekey for icfdev.com is 7dZVcZ86hs. Did i miss something?

Regards

April 24, 2025 at 8:58 pm #16966343

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi, and thanks for trying my suggestions.

Is hidden link the main site of your network installation?

Also, can you please check if things work as expected when you deactivate the 'Use directory for default language' option in WPML -> Languages -> Language URL format?
You would need to re-save the permalinks after disabling this otpion.

**** Important! Please make a full site backup (files and DB) before you proceed with those steps****

Does disabling this option enable you to see the jobs in WPML -> Translations?

Please note that my weekend is Friday-Saturday, and I'll be able to continue to check this issue and help you on Sunday.

Regards,
Itamar.

April 28, 2025 at 10:15 am #16974184

benjaminA-35

Hi,

yes, hidden link is the main site of the network installation.
I have deactivated the "Use directory for default language" option now but unfortunately the queue under WPML > Translations is still empty.

Regards

April 29, 2025 at 1:12 pm #16979473

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I'm consulting our second-tier supporters about your case.
I'll update you when I have their reply.

I appreciate your patience.
Itamar.

May 5, 2025 at 8:46 am #16995259

benjaminA-35

Hi,

because our development of the site is greatly affected by having all plugins - except WPML - disabled, we have decided to reenable these again. Because the error was still present with all plugins disabled, I assume that the issue is not caused by some interference from them. Please tell me when there is a particular need to disable plugins again.

Regards

May 5, 2025 at 12:32 pm #16996239

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi.

Our second-tier supporter says this might be an issue similar to the one mentioned in the following ticket.

https://wpml.org/forums/topic/translation-jobs-queue-is-empty/#post-16957847

The problem is a collation mismatch between the default WordPress tables and the WPML tables.

If you know what to check and do, please proceed and adjust the tables' collation according to the instructions.

**** Important! Please make a full site backup (files and DB) before you proceed with those steps****

Otherwise, if you need further help, please let me take a copy of your site. For this, I must install a plugin like Duplicator or All In One Migration. Please let me know if you agree.

Regards,
Itamar.

May 6, 2025 at 7:12 am #16999447

benjaminA-35

Hi,

I have executed the first command from the other ticket to check whether the collation mismatch is present here as well.

The tables "wp_icl_languages", "wp_posts", "wp_icl_string_packages" and "wp_icl_translation_batches" seem to have the same correct collation.

When outputting the collation of all tables containing _icl_ in the name, I have found that the wp_icl_string_batches table has another collation. I am not sure if that is intended though.

(see screenshots for both)

Regards

Bildschirmfoto 2025-05-06 um 09.10.27.png
Bildschirmfoto 2025-05-06 um 08.59.23.png
May 6, 2025 at 7:44 am #16999569

benjaminA-35

Edit: I have now changed the collation of the wp_icl_string_batches tables to the desired utf8mb4_unicode_520_ci via the command of the other ticket. Unfortunately this seems to have no effect when checking the queue in wordpress again.