[Closed] We're sorry, but something went wrong

Your ticket is now open, please let us know once you receive the Debug.log file.

Hello,

Thank you for coming back with the debug.log,

The error is related to an illegal mix of collations between two tables, here is the exact query: https://pastebin.com/kiNf6g3i

In your error message, it's evident that you have a mix of collations: utf8mb4_unicode_520_ci and utf8mb3_general_ci, and this is causing a problem when you try to use the 'LIKE' operator in your SQL query.

After checking around forums, the solution is to correct these table's collation: https://stackoverflow.com/questions/44027987/illegal-mix-of-collations-utf8mb4-unicode-ci-implicit-and-utf8mb4-general-ci

Here's how you can fix this collation error:

1- Identify the Problem Tables: First, identify the tables involved in this query and check their collations. In your case, you're dealing with the wp_posts and wp_icl_translations tables.

2- Change Collations: You need to make sure that all tables involved in your query have the same collation. In this case, you should change the collation of the tables to match. You can use a tool like phpMyAdmin or run SQL queries to alter the collations. To change the collation of a table, you can use SQL queries like this:

ALTER TABLE table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;

Replace table_name with the actual table names you are working with.

3- Update Character Set and Collation in WordPress: After altering the database table collations, you may also need to update the character set and collation settings in your WordPress configuration to match the new collations. You can do this by editing your wp-config.php file. Make sure that the DB_CHARSET and DB_COLLATE settings match the new collations.

define('DB_CHARSET', 'utf8mb4');
define('DB_COLLATE', 'utf8mb4_unicode_520_ci');

4- Re-run the Query: After making these changes, try running the query again to see if the collation error is resolved.

Please make sure to backup your database before making any changes to the collation. Collation changes can affect data and queries, so it's essential to handle them with caution.

If you're not comfortable making these changes yourself, consider running it on a staging site and seeking the assistance of a database administrator or a developer experienced with WordPress and database management.

Best,

Hello,

This is exactly why translation might have reverted/lost,

When translating your content, WPML will create links between each translated element with its original counterpart,

Editing the translation through a site editor, as in your case here with Elementor, will cause a broken link that will make WPML lose the translation.

You should only use the site editor on the translations if you are translating your content manually : https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/

Here are other possibilities that could explain this issue : https://wpml.org/faq/why-arent-my-translations-showing/

Best,