akrovalis

Hi,

Thank you for the heads up and my bad for not opening a ticket first.

Apparently checking the collation per column did solve the problem. It was utf8mb3_general_ci and I changed to utf8mb4_general_ci as suggested.

I’m not sure why, but this action or maybe clicking “Save” to regenerate within TranslatePress plugin changed?my trp_* tables to utfmb4_unicode_520_ci.

Nonetheless, this is irrelevant as I can now translate pages with emojis, which was the main issue.

So I guess I’ll shrug shoulders and carry on like this for now.

Thanks!

One week and still no answer.

I’m a paying customer. Is there a way to chat? Other translation plugins have inmediate support. Why don’t you?

I could be fine with a delay of a day or two if the answers were solid, but having to set a reminder to follow up this and receiveng generic answers after that time is below mediocre customer support from your part.

I expect more of you in this regard.

Hi Alex,

I’ve make sure that the collation is utf8mb4_general_ci as you can see in the screenshot attached.

I’ve tried removing the “troubled” tables and click save again to recreate them (Note: When I do this, the new tables created are utf8mb3_general_ci, just in case that hints you something).

The problem persists and I cannot translate the pages where at least 1 emoji is present.

I get:

last_error Illegal mix of collations for operation ‘in’

details Error running get_string_ids()

last_querySELECT original,id FROM wp_trp_dictionary_es_es_fr_fr WHERE original IN ( ‘[…]

Note: The same happens with wp_trp_dictionary_es_es_en_us , not just spanish to french. So it happens with any language.

If I try to translate, I see a blue square and when I click on it I see the message “This string is not ready for translation yet. Try again in a moment…“. This happens for all the strings in the page where an emoji is present.

If I remove the emojis in the page, then the page becomes available for translation.

Please advise. Thank you.

Hi, it’s been almost one week without an answer.

So, to my previous question, do I have to assume that the answer is “no”?

Thank your for your answer Alex.

I already went through all the steps and I confirm that the collation of tables in my database is utf8mb4_general_ci.

The answer feels a bit generic though, and it doesn’t address the main issue. So I’ll try to cut to the chase:

?Can Translatepress deal with emojis? If so, why is that the only pages that are causing these errors are the ones that have at least 1 emoji in them?

Thanks Andrei for your sincere answer.

If anyone ends up here looking for a solution for this problem:

What I did was to add meta fields for the fields that need translation (normaly is just <title>, <description>, <link> and product type). Then, using a product feed plugin, map them accordingly in the export for the relevant language.

This can take some time the more products you have, but eventually is doable.

Hope this helps!