Skip to content Skip to sidebar

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

Problem:
You are trying to translate labels from a plugin and set a translation ID for the footer on your Ocean WP page. However, you encounter several issues: sending for translation fails with an error, strings are registered and locked in admin text strings, there are no strings in the string translation list, and there is no 'domain' filter.
Solution:
We have identified that the issue is due to corrupt database entries. Please follow these steps carefully:
1. Important: Create a backup of your database.
2. Execute the following SQL commands on your database:

DELETE FROM `wp_terms` WHERE `term_id` IN (SELECT `term_id` FROM `wp_term_taxonomy` WHERE `taxonomy` = 'translation_priority');

DELETE FROM `wp_term_taxonomy` WHERE `taxonomy` = 'translation_priority';

DELETE FROM `wp_icl_translations` WHERE `element_type` LIKE '%translation_priority%';

3. After completing the above deletions, create a new table with the following SQL command:

CREATE TABLE `wp_icl_string_packages` ( `ID` bigint unsigned NOT NULL AUTO_INCREMENT, `kind_slug` varchar(160) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL, `kind` varchar(160) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL, `name` varchar(160) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL, `title` varchar(160) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL, `edit_link` text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL, `view_link` text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_id` int DEFAULT NULL, `word_count` varchar(2000) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `translator_note` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`ID`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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. Additionally, please feel free to open a new support ticket for further assistance.

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.

This topic contains 4 replies, has 0 voices.

Last updated by Anton 5 days, 16 hours ago.

Assisted by: Christopher Amirian.

Author Posts
July 22, 2025 at 8:17 am

Anton

Background of the issue:
I'm trying to translate labels from one plugin and set a translation ID for the footer on my Ocean WP page. On another site, everything works normally, but here I have several problems. The issue can be seen at hidden link.

Symptoms:
When I try to send for translation, it says 'Sending for translation failed. An error occurred while sending the translation.' In admin text strings, it says the string is registered and locked. In the string translation list, there are no strings, and I see that there is no 'domain' filter.

Questions:
Why are there no strings in the String Translation options?
Why is the 'Sending for translation' process failing with an error?
Why are strings registered and locked in admin text strings?
Why is there no 'domain' filter in the string translation list?

July 22, 2025 at 9:00 am
July 22, 2025 at 12:24 pm #17259193

Christopher Amirian
WPML Supporter since 07/2020

Languages: English (English )

Timezone: Asia/Yerevan (GMT+04:00)

Hi,

Thank you for the details. I created a copy of the website nd reported the issue to the second tier support.

I will get back to you as soon as I have an update.

Thanks.

July 23, 2025 at 11:05 am #17263451

Christopher Amirian
WPML Supporter since 07/2020

Languages: English (English )

Timezone: Asia/Yerevan (GMT+04:00)

Hi,

I have an answer from the second tier support. There was corrupt database entries.

Please follow the steps below:

- Important!: Create a backup of your database
- Perform the SQL commands below on your database:

DELETE
FROM `wp_terms`
WHERE `term_id` IN (SELECT `term_id`
FROM `wp_term_taxonomy`
WHERE `taxonomy` = 'translation_priority');

DELETE
FROM `wp_term_taxonomy`
WHERE `taxonomy` = 'translation_priority';

DELETE
FROM `wp_icl_translations`
WHERE `element_type` LIKE '%translation_priority%';

- After that perform the SQL commands below:

CREATE TABLE `wp_icl_string_packages` (
  `ID` bigint unsigned NOT NULL AUTO_INCREMENT,
  `kind_slug` varchar(160) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `kind` varchar(160) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `name` varchar(160) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `title` varchar(160) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `edit_link` text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `view_link` text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `post_id` int DEFAULT NULL,
  `word_count` varchar(2000) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
  `translator_note` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci,
  PRIMARY KEY (`ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
July 24, 2025 at 8:28 am #17266418

Anton

This solved part of the problem. I can make string translations now, but there are probably more corrupted tables. Now i have problem with YOAST and WPML SEO - they crash the page after activation. I run this SQL and it get page up again, but I will ask you too solve this problem too.

July 24, 2025 at 2:19 pm #17267956

Christopher Amirian
WPML Supporter since 07/2020

Languages: English (English )

Timezone: Asia/Yerevan (GMT+04:00)

Hi,

Thank you for getting back to us. I tested the scenario on the copied version of the website here:

hidden link

You can log in with the same login information.

You will see that I enabled WPML SEO and Yoast SEO with no issues.

If that is not the problem, please give more detailed steps on what I should do to see the problem and what error you get.

July 25, 2025 at 10:06 am #17270576

Anton

When i turned on debug, i saw there is a problem with memory so i enlarged it from 128M to 256M, obviously it was not enough for elementor and wpml together.