This thread is resolved. Here is a description of the problem and solution.
Problem:
The client was unable to access the WPML plugin in the website backend due to a PHP error indicating a missing database table named 'icl_translate_job'. This error was identified in the file /wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Infrastructure/WordPress/Port/Persistence/QueryHandler.php.
Solution:
We accessed the site and discovered several missing tables and some with incorrect or missing fields. After repairing these tables, we set English as the default language and Greek as the secondary language, based on the active languages found in the WPML tables.
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.
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: Exception
This topic contains 10 replies, has 0 voices.
Last updated by teamA-3 2 months, 4 weeks ago.
Assisted by: Waqas Bin Hasan.
Author | Posts |
---|---|
March 7, 2025 at 5:31 am #16786031 | |
teamA-3 |
Background of the issue: Symptoms: Questions: |
March 7, 2025 at 6:45 am #16786134 | |
teamA-3 |
And when I open the plugin, my website shows a 404 error |
March 7, 2025 at 10:14 am #16787343 | |
Waqas Bin Hasan WPML Supporter since 05/2014
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Hi, Thank you for contacting the support. Looks like somehow the said table (icl_translate_job) was not created or removed. Please follow these steps: - Access your database via database administration plugin or directly via your hosting panel's DB admin (i.e. phpMyAdmin). It is highly advised to try this on a staging/dev site first, so your live website isn't compromised. SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; CREATE TABLE `wpx_icl_translate_job` ( `job_id` bigint(20) UNSIGNED NOT NULL, `rid` bigint(20) UNSIGNED NOT NULL, `translator_id` int(10) UNSIGNED NOT NULL, `translated` tinyint(3) UNSIGNED NOT NULL DEFAULT 0, `manager_id` int(10) UNSIGNED NOT NULL, `revision` int(10) UNSIGNED DEFAULT NULL, `title` varchar(160) DEFAULT NULL, `deadline_date` datetime DEFAULT NULL, `completed_date` datetime DEFAULT NULL, `editor` varchar(16) DEFAULT NULL, `editor_job_id` bigint(20) UNSIGNED DEFAULT NULL, `edit_timestamp` int(11) UNSIGNED DEFAULT NULL, `automatic` tinyint(3) UNSIGNED NOT NULL DEFAULT 0 ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Indexes for dumped tables -- -- -- Indexes for table `wpx_icl_translate_job` -- ALTER TABLE `wpx_icl_translate_job` ADD PRIMARY KEY (`job_id`), ADD KEY `rid` (`rid`,`translator_id`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `wpx_icl_translate_job` -- ALTER TABLE `wpx_icl_translate_job` MODIFY `job_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; And then finally recheck. Here's also the list of WPML tables for a reference. Regards. P.S.: For the other issue (i.e. 404), I recommend opening a separate ticket/chat because as per forum policy we can only handle one issue per ticket/chat. So you can get more to the point help, without mixing up several issues in one long ticket. |
March 10, 2025 at 1:13 am #16793960 | |
teamA-3 |
Hello, there is an error in the database for wpx_icl_translate_job, but it still appears |
March 10, 2025 at 1:28 am #16794026 | |
teamA-3 |
I have given you backend permissions. Could you please help me solve this problem |
March 10, 2025 at 1:28 am #16794027 | |
teamA-3 |
Login address: hidden link |
March 10, 2025 at 2:17 am #16794067 | |
teamA-3 |
It seems to be an issue with the WPML plugin database. After uninstalling the plugin, it was restored to normal |
March 10, 2025 at 4:49 am #16794174 | |
teamA-3 |
Howdy! WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. In this case, WordPress caught an error with one of your plugins, WPML Multilingual CMS. First, visit your website (hidden link) and check for any visible issues. Next, visit the page where the error was caught (hidden link) and check for any visible issues. Please contact your host for assistance with investigating this issue further. If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further. hidden link To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires. When seeking help with this issue, you may be asked for some of the following information: Error Details |
March 10, 2025 at 4:53 am #16794176 | |
teamA-3 |
*** removed for safety reasons *** |
March 10, 2025 at 4:54 am #16794178 | |
teamA-3 |
*** removed for safety reasons *** |
March 10, 2025 at 5:40 am #16794357 | |
teamA-3 |
WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] WordPress database error: [Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '='] |
March 10, 2025 at 7:26 am #16794557 | |
Waqas Bin Hasan WPML Supporter since 05/2014
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Thank you for the updates. I've removed all the credentials from the public messages due to safety reasons. Please DO NOT share the sensitive access information in public messages or these may fall into wrong hands. Always ask to enable the private message when needed. I need to take a closer look at your site. So 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. I 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. |
March 10, 2025 at 7:48 am #16794616 | |
teamA-3 |
The website is located in the public_tml folder |
March 10, 2025 at 7:49 am #16794617 | |
teamA-3 |
public_html |
March 10, 2025 at 1:18 pm #16796637 | |
Waqas Bin Hasan WPML Supporter since 05/2014
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Thank you for the access, I was able to fix the issue. There were several tables missing and some with incorrect or missing fields. I'm not sure why this'd happen. However, for now I 've fixed all the tables. I was also not sure what's the default language, however, based on some digging I found English being the default language while several other languages were added. Out of these only English and Greek were active in the WPML Tables. So I've set English as default while Greek as secondary language. Please feel free to add more languages and/or change default language as needed. I've also turned off Automatic Translation for now, feel free to turn it back on as needed from WPML -> Translation Mangaement. |