[Escalated to 2nd Tier] Products from default language show secondary language after WPML 4.4.0 update

Hello, so the original error is still not resolved? At the moment I still need to keep the WPML Version 4.3.19 but I am worried keeping that outdated version could cause problems with other plugins.

Regarding the proposed workaround:
What did you mean by setting '"translated mode" for product_tags'? Do you mean that I should set "product_tag" to "Translatable - use translation if available or fallback to default language"?
And how would this help with the untranslated items being shown in the other languages? Because the product_tag terms are actually translated, only the products themselves are not.

Hello,

its been 10 months since I told your team about that bug with mentioned in this support thread. As previously described, here again the issue is in short:

I have 3 languages.
1) English is the default language
2) German is a secondary language for which we manually translated all products
3) Italian is another secondary language for which the products are not translated and thus they should show the English language default post.

To achieve this, I have set in the WPML translation settings the "Products" to "Translatable - use translation if available or fallback to default language".
Now on the archive/shop pages the result is:
In English and in Italian it works as desired, in both cases the English default version of the products are shown. However, in German i see the products each twice, both the manually translated German products BUT ALSO the English language products are displayed - while obviously only German one should be shown here.

Why has this bug still not been fixed? When will this finally be solved in an update? Is there any better workaround now?

Well, can you tell me if this issue is even worked on? This seems quite a basic function that has a major bug here. Having certain languages that are manually translated and other languages which are not that have a fallback to the default language really has to work. As mentioned this issue only appeared since WPML version 4.4.0 so it should not be that difficult to fix.

And yes sure besides the information about whether this issue is worked on at all and a broad timeline when this may be solved, please help me find a workaround for it. The term archive pages of our extensive taxonomies make up a bigger part of our website's most important pages and thus it is important that the content of those term archive pages themselves need to be translated while we can translate all the products which are in the thousands. So your suggested workaround is not applicable, we rely on a combination of these two settings and need a solution for this.