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.
Our next available supporter will start replying to tickets in about 0.78 hours from now. Thank you for your understanding.
This thread is resolved. Here is a description of the problem and solution.
Client gets this messages in WPML:
"There is a problem with the String Translation table in your site. This problem is not causing a problem running the site right now, but can become a critical issue in the future. WPML support team knows how to fix it. Please add a message in the relevant support thread and we'll fix it for you."
In 'Themes and Plugin Lokalisierung':
"Themes und Plugins nur mit WPMLs String Translation übersetzen (Keine .mo-Dateien laden) WPML kann .mo-Dateien aufgrund technischer Probleme in der String Translation-Tabelle nicht ersetzen. Das WPML-Supportteam weiß, wie sich das lösen lässt. Bitte fügen Sie eine Nachricht im relevanten Support-Thread hinzu, dann beheben wir dies für Sie."
The first notice shows up when the String Translation tables are not created correctly, so the problem with the database is solved re-installating WPML.
To get rid of the notice you need to do remove a key from the table wp_options. If your WordPress is using another table prefix it will be something like ..._options.
The key you need to remove is this:
You can check if it exists by running a query similar to the following, in Adminer or phpMyAdmin (please use your own table prefix if you are not using wp_options):
SELECT * FROM `wp_options` WHERE `option_name` LIKE 'wpml_string_table_ok_for_mo_import'
Once you have seen this key, you should remove it and visit the front-end of your site.
If you visit then the WPML -> Theme and plugin localization page and there is no notice - then you have successfully completed the procedure.