Syncing translations with DB stuck at 50%

[dowadidi]

Description

Syncing translations with DB got stuck at 50%, halting the queue altogether. We ended up having a backlog of 21k tasks before anyone noticed.

Steps to reproduce

1. Update translation, triggering syncing translations with DB
2. Gets stuck at 50%

Additional info

• Craft version: 3.7.43
• PHP version: 7.4.30
• Database driver & version: MySQL 5.7.35
• Plugin version: 2.2.1

[kerrig]

We're also running into this same issue. Eventually causing OOM errors as well. If there's no quick fix could we possibly add a config setting to disable the sync queue job for now?

Additional info

Craft version: 3.7.57
PHP version: 7.3.33
Database driver & version: MySQL 5.5.5
Plugin version: 2.3.2

[naboo]

We're also experiencing the exact same issue. DB keeps clogging up with either empty or numeric string translations and the sync job just gets stuck at 50%.

We are running latest Craft CMS and latest plugin version as of date 2024-03-06.

[andrelopez]

Hi @naboo could you please recreate the issue and send back to us a zip file of the following folder: storage/logs? please send the file to support@enupal.com

[naboo]

So I just replied to my suppor ticket. The issue is related to the character set not being supported in the DB. So it's technically not a plugin issue more then a DB issue.

If you try and store translations with characters not supported by the DB table this row fails:

translate/src/jobs/SyncTranslationsWithDb.php

Line 96 in 8da4077

$connection->createCommand()->upsert($messageTable, $rowToInsert)->execute();

For me personally it was an emoji in the translation.

To store the emoji \xF0\x9F\x91\x89 (or any other emoji) in a MySQL column, the column should use a character set that supports 4-byte characters. The recommended character set for this purpose is utf8mb4.

However I can't seem to get the column conversion to utf8mb4 to work at the moment. I can verify the bug though if I just remove the emoji from the translation everything works fine. I'll keep updating this post if I solve it by the end of my day (or if you beat me to it!).