Known issue

Problem:
The client is experiencing an issue where Polish translations are appearing on the English page of their WordPress site, despite using WPML and ACF addons. They were advised to add a new filter after accidentally enabling translation for an ACF field group.
Solution:
We reviewed the client's page and did not initially see the Polish content on the English filter. After further investigation, we directed the client to an existing errata that addresses issues with ACF fields not being translated on the frontend. We recommended using the workaround provided in the errata. For more details, please refer to the following link: https://wpml.org/errata/filter-everything-acf-fields-not-translated-on-frontend/.

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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.

Problem:
You are encountering an API error stating 'No sitekey found for this website' after deregistering and activating a new key on your WPML installation. Additionally, despite translating links in ATE and updating them, they remain in the original language.
Solution:
First, ensure that the sitekey issue is resolved by checking if the new key is correctly activated in your WPML account. If the problem persists, it might be due to a known issue which our developers are currently addressing. You can track the progress and find more details on this issue at WPML Errata page.
For the link translation issue, it is identified as a new problem, and our developers are working to resolve it in the upcoming version of WPML.

If these solutions do not apply to your case, or if the problem 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 you still need assistance, please open a new support ticket at WPML support forum.

Problem:
If you're experiencing an internal server error when trying to translate pages using WPML, particularly with pages containing images without metadata, this might be due to a known issue.
Solution:
We recommend waiting for the upcoming WPML 4.8.1 update, which addresses this issue. You can check the progress and details of this known issue on our errata page: WPML 4.8 Fatal Error When Translating Pages Containing Images Without Metadata.

If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also 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.

Problem:
If you're experiencing a 404 error on your WooCommerce category page due to a compatibility issue with Rank Math, it might be related to the 'Remove parent slugs' option or incorrect slug translations for different languages.
Solution:
1. Check if the 'Remove parent slugs' option in Rank Math is causing the issue. A temporary fix can be found in our errata: https://wpml.org/errata/rank-math-seo-remove-parent-slugs-option-causes-category-slug-translation-error-404/
2. If the issue persists, you may need to adjust the slug translations:
- Navigate to WPML > Settings > Slug translations and ensure it is enabled.
- Go to WPML > Taxonomy Translation > Product Categories and check the slug translations for each language.
- Ensure that the slug translations are either blank or a copy of the original WordPress settings: 'product-category'.
3. If you have modified the Rank Math plugin files as a workaround, ensure to update the slug translations accordingly. You might need to edit the original pages and update the translations in the Advanced Translation Editor.

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

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/.