Bug

Problem:
The client reported that the WPML database schema was not up-to-date, with missing tables such as wp_icl_background_task and missing fields in wp_icl_translation_status.
Solution:
We compared the client's database with a fresh WPML install and identified missing tables and fields. We executed SQL commands to create the missing tables and alter existing ones to add the necessary fields.
After applying these changes, the database issues related to WPML were resolved. However, we cannot guarantee that other tables from core or other plugins were not affected.

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 the problem persists, please open a new support ticket.

Problem:
The client was unable to save post translations using the WPML Classic Translation Editor, experiencing infinite loading. The issue was traced to the handling of sticky posts.
Solution:
We discovered that the 'sticky_posts' option was missing in the database. To resolve this, we created a test post, enabled it as a sticky post, and then translated it into a second language. This allowed the client to save translations when using the WPML Classic Translation Editor. We recommend checking if this solution resolves the issue on your end.

Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, please open a new support ticket at WPML support forum for further assistance.

Problem:
If you're experiencing an issue where the CSS selector

current-menu-item

is not being appended to the menu item in the navigation block of the page that is currently being viewed in a secondary language, this might be due to incorrect post IDs in the translated menu.
Solution:
We recommend checking the

wp_posts

table in your database for the menu ID and verifying the record. You should ensure that the post IDs match the translated IDs. Here is an example of what you might see and how to correct it:

<!-- wp:navigation-link {"label":"Post A – es ","type":"post","id":66,"url":"https://your-site.com/es/2024/09/15/post-a-es/","kind":"post-type"} /-->

This ID should be updated to the correct translated post ID, like so:

<!-- wp:navigation-link {"label":"Post A – es ","type":"post","id":72,"url":"https://your-site.com/es/2024/09/15/post-a-es/","kind":"post-type"} /-->

After making these changes, the menu should work correctly in the secondary language.

If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 you still need assistance, please open a new support ticket at WPML support forum.