Problem: The client was using the Premium Addons for Elementor widget for their blog, along with WPML for translation. They encountered an issue where the category filter worked correctly in Estonian, the main language, but displayed Estonian posts when filtering in English. Solution: We recommended reviewing an errata our team published, which addresses issues with the Premium Addons for Elementor Widget not displaying posts in secondary languages when including or excluding post categories. You can find the errata here: https://wpml.org/errata/premium-addons-for-elementor-blog-widget-not-showing-posts-in-the-secondary-language/ We also suggested updating the Hello Elementor theme, Premium Addons for Elementor, and Elementor itself. After updates, it was necessary to re-add the snippet from the errata to the functions.php file.
If this solution does not resolve your issue or 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. If the problem persists, please open a new support ticket at WPML support forum.
Problem: The client reported that a new brand attribute "ARS/SOLL" was not appearing in the "Filter by Attribute" section in the catalog in the second language after import. Solution: We found that the ARS/SOLL term in Russian had no products assigned because products and taxonomies were set as 'Appear as translated' and only the Brand term was translated, not the products. We recommended using the 'duplicate' feature instead of the 'fallback' option. Documentation on duplicating content We duplicated one product of the Brand 'ARS/SOLL' to Russian and turned off the option "Use the product attributes lookup table for catalog filtering" in WooCommerce -> Settings -> Products -> Advanced. This should allow the filter widget to show the brand in the Russian shop after duplicating/translating the corresponding products.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem:
It was proving difficult to locate a string which continued to be displayed in the default language on the front end on translated pages.
Solution:
Somehow the small string in question ("KM") was wrongly labelled as originally Russian. Locating the text within String Translation the language can be reset to the correct language, and then a translation to Russian provided.
