andzelinaJ

Problem:
If you're experiencing issues where translations are not displaying correctly on your website's front end, even though they appear to be added correctly, we can help you address this.
Solution:
1) We recommend updating your theme and Elementor plugins to their latest versions to see if that resolves the problem. Always ensure to create a backup before proceeding with updates.
2) If updating does not resolve the issue, consider creating a staging site for further investigation. If creating a staging site isn't feasible, we can assist by making a copy of your site using the Duplicator plugin, but we will need your permission to proceed.
3) As a temporary workaround, you can adjust the code in your site. Specifically, add extra conditions in

\WPML\PB\Elementor\Hooks\QueryFilter::recursivelyTranslateQueryIds

in

/wp-content/plugins/sitepress-multilingual-cms/addons/wpml-page-builders/classes/Integrations/Elementor/Hooks/QueryFilter.php

. Here is the code snippet you can use:

if ( ! empty( $data->settings->query_include_term_ids ) ) {
	$data->settings->query_include_term_ids = $this->convertTermTaxonomyIds( $data->settings->post_query_include_term_ids );
}
if ( ! empty( $data->settings->query_exclude_term_ids ) ) {
	$data->settings->query_exclude_term_ids = $this->convertTermTaxonomyIds( $data->settings->post_query_exclude_term_ids );
}
if ( ! empty( $data->settings->post_query_posts_ids ) ) {
	$data->settings->post_query_posts_ids = Ids::convert( $data->settings->post_query_posts_ids, Ids::ANY_POST );
}
// --- New cases ---
if ( ! empty( $data->settings->query_include_term_ids ) ) {
	$data->settings->query_include_term_ids = $this->convertTermTaxonomyIds( $data->settings->query_include_term_ids );
}
if ( ! empty( $data->settings->query_exclude_term_ids ) ) {
	$data->settings->query_exclude_term_ids = $this->convertTermTaxonomyIds( $data->settings->query_exclude_term_ids );
}
if ( ! empty( $data->settings->query_posts_ids ) ) {
	$data->settings->query_posts_ids = Ids::convert( $data->settings->query_posts_ids, Ids::ANY_POST );
}

If these steps do not resolve your issue or if the solution 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 needed, please do not hesitate to open a new support ticket for further assistance.

Problem:
The client reported multiple issues after noticing an error about the site not meeting WPML's minimum requirements, which later disappeared without any action taken by the client. The issues included mismatches in product counts across categories, the price filter not being visible or functioning correctly across different languages and views, and untranslated address information in the footer.
Solution:
We examined the mismatch in product counts within categories. It was found that the content and products were initially created in English and then translated, with English being the default language. The primary issue was with the products in the default language not being assigned to the correct categories. We recommend the client to review all products in the default language to ensure they are correctly categorized. This should be done with WPML disabled to confirm that the setup works independently of WPML. Once verified, WPML can be re-enabled to check if the translation issues persist. If problems continue, we advise opening a new support ticket.

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 issues persist, please do not hesitate to contact us by opening a new support ticket at WPML support forum.