Skip Navigation

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

Problem:
The client is experiencing fatal errors when trying to access the Translation Management section in WPML, due to missing 'batch_id' column and incorrect data type for 'translation_package' column in the 'wp_icl_translation_status' table.
Solution:
First, add the missing 'batch_id' column by executing the following SQL command:

ALTER TABLE wp_icl_translation_status ADD COLUMN batch_id INT NOT NULL DEFAULT 0;

Next, change the data type of the 'translation_package' column to 'longtext' to prevent data corruption. Run this SQL command:

ALTER TABLE wp_rascg4p5t7_icl_translation_status CHANGE translation_package translation_package LONGTEXT COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER translation_service;

After updating the database, follow these steps to clean up and resend the affected translation:
1. Identify the original post ID.
2. In the 'icl_translations' table, locate the 'trid' for that post ID.
3. Use the 'trid' to filter records in the same table and remove any rows where the 'element_id' column is 'NULL'.
4. Go to WPML > Packages in the WordPress admin and delete the package with the identified ID.
5. Resend the content for translation as usual, following the instructions here: Translating Your Contents.

If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your 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 problems persist, please open a new support ticket 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 21 replies, has 0 voices.

Last updated by Bruno Kos 3 weeks, 1 day ago.

Assisted by: Bruno Kos.

Author Posts
May 14, 2025 at 5:50 am #17030124

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

To troubleshoot this problem, I'll install the Duplicator plugin and generate packages for further debugging purposes. I'll ensure to exclude all media files to maintain a minimal package size.

You can find more information about the process here:
https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#get-help-from-support

Please confirm if this approach is acceptable to you!

May 14, 2025 at 6:59 am #17030409

kellyS-6

Does this mean you are going to make changes in the live site or are you going to clone this site in your environment ?

May 14, 2025 at 11:18 am #17031831

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

Clone the site to debug in our local environment and then propose a solution (based on what we find during debugging) you can apply to your production site.

May 15, 2025 at 4:28 am #17034851

kellyS-6

Sure, You can Proceed with it.

May 15, 2025 at 12:27 pm #17036864

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

I am no longer able to access the site through wpforms username. Can you update the password?

May 16, 2025 at 10:11 am #17040912

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

This has been escalated to our 2nd tier team team and may take some debugging time, I'll get back to you as soon as I have any news or questions for you.

May 16, 2025 at 12:36 pm #17041735

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

We’ve identified a database issue caused by a field size limitation. Specifically, the `translation_package` column in the `icl_translation_status` table is currently set to `text`, but it needs to be `longtext` to avoid data corruption.

To fix this, please run the following SQL command:

ALTER TABLE `wp_rascg4p5t7_icl_translation_status`
CHANGE `translation_package` `translation_package` LONGTEXT COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `translation_service`;

Once the update is complete, follow these steps to clean up and resend the affected translation:

1. Identify the original post ID (for example, `46967`).
2. In the `icl_translations` table, locate the `trid` for that post ID.
3. Use the `trid` to filter records in the same table and remove any rows where the `element_id` column is `NULL`.
4. Go to **WPML > Packages** in the WordPress admin and delete the package with ID `46967`.
5. Resend the content for translation as usual, so like this: https://wpml.org/documentation/translating-your-contents/#choose-what-to-translate

Let us know once you've completed these steps or if you run into any issues. The instructions should work, assuming the corruption is only related to that specific column's type.