Known issue

Problem:
If you're experiencing an 'Unknown format specifier "t"' error when trying to open theme and plugins localization in WPML, it occurs due to an issue in the file

wpml-st-translations-file-registration.php

on line 100.
Solution:
We are aware of this issue and a fix will be included in future updates. For now, we recommend you try the workaround provided in the following link: WPML Errata.

If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance.

Problem:

If you're experiencing issues with losing translations when editing posts in different translation editors on your WPML-powered site, this might be due to using a mix of the WordPress native editor, WPML Classic Translation Editor (CTE), and WPML Advanced Translation Editor (ATE). This problem typically occurs with older posts originally created in a different language and translated using CTE, but now being edited in ATE.

Solution:

We recommend the following steps to resolve this issue after a full site backup:

1) Upgrade to the WPML 4.8 series for improvements and new features.
2) Run the following SQL query in your database using the Adminer plugin or PHPMyAdmin:

UPDATE wp_icl_translate_job SET editor = 'wpml' WHERE editor LIKE 'wp'

This query will help maintain the use of CTE for older translations while enabling ATE for new ones.
3) Disable the *Use also for old translations created with the classic editor* option in WPML >> Settings >> Translation Editor.
4) Update the translations of your posts.

Additionally, it is possible to synchronize taxonomies across translations. You can add new category terms in the original language and translate them into secondary languages without losing existing translations.

While not mandatory, you might also consider following the WPML Troubleshooting steps as outlined here: WPML Troubleshooting.

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.

Problem:
The client reported an issue where WPML String Translation was not functioning correctly due to problems with the String Translation table in the database, which could potentially become a critical issue.
Solution:
We recommended the following steps to resolve the issue:
1. We asked the client to provide temporary access to their site for debugging.
2. We added the following code to the bottom of the functions.php file in the theme:

function wpml_fix_missing_icl_tables() {<br />    if( function_exists( 'icl_sitepress_activate' ) )<br />        icl_sitepress_activate();<br />}<br />add_action( 'wp_footer', 'wpml_fix_missing_icl_tables' );

3. We instructed the client to visit their site’s homepage to activate the code.
4. After confirming the issue was resolved, we removed the code and ensured that the default and secondary languages were enabled correctly in WPML.
For more details, you can check the errata here: https://wpml.org/errata/missing-_icl_strings-_icl_string_translations-data-tables/

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.

Problem:
You are experiencing a conflict between WooCommerce bookings and WPML plugins, which was resolved temporarily by deactivating the 'WooCommerce Multilingual & Multicurrency' plugin.
Solution:
We recommend trying the beta version of the WPML plugin to see if it resolves the issue. If the problem persists, we suggest setting up a staging site with minimal settings to further diagnose the issue.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue continues, please open a new support ticket at WPML support forum for further assistance.