Possible DB Errors while upgrading String translation to 2.4.0

Overview of the issue

When using automatic updates, during the upgrade to String Translation 2.4.0 you may see a database error either in the upgrade page on in the debug.log.

The is a cosmetic (display-only) issue and is not causing any loss or damage. The upgrade logic continues normally.

An example of error is:


WordPress database error Table 'cctests.wp_icl_string_pages' doesn't exist for query
SELECT DISTINCT
s.id,
s.name,
s.context,
st.status,
s.gettext_context,
st.value AS tra,
s.value AS orig
FROM wp_icl_string_pages sp
INNER JOIN wp_icl_strings s
ON s.id = sp.string_id
LEFT JOIN wp_icl_string_translations st
ON s.id=st.string_id
AND st.language=sp.language
AND s.language!=sp.language
WHERE (sp.language='en' and sp.url='/wp-admin/admin-ajax.php/') or (sp.language='en' and sp.url IS NULL)
made by require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), WP_Locale->__construct, WP_Locale->init, __, translate, apply_filters('gettext'), icl_sw_filters_gettext, icl_translate, WPML_Register_String_Filter->translate_by_name_and_context, WPML_ST_DB_Cache->get_translation, WPML_ST_Page_Translations_Persist->get_translations_for_page


We are working to fix this issue, so that WPML does not throw any messages during the update process. Right now, no workaround is necessary, because this error doesn’t cause any problems.

Workaround

No workaround is needed: a patch will be provided to avoid this in future.