Hi! Is it possible with some quick "hack" to make sure to always load "en" language version of catalog content when ContentLanguage.PreferredCulture is "sv"? For CMS content it's easy to configure fallback and replacement languages, but not for catalog content.
The use case for this is that the customer wants to temporarily serve the international english version of nodes, products and variants until the translation to swedish is done.
Since we have multi catalog scenario with "sv" enabled and inRiver as PIM, all products exists in "sv" version but with mostly empty or poorly translated fields.
Hi! Is it possible with some quick "hack" to make sure to always load "en" language version of catalog content when ContentLanguage.PreferredCulture is "sv"? For CMS content it's easy to configure fallback and replacement languages, but not for catalog content.
The use case for this is that the customer wants to temporarily serve the international english version of nodes, products and variants until the translation to swedish is done.
Since we have multi catalog scenario with "sv" enabled and inRiver as PIM, all products exists in "sv" version but with mostly empty or poorly translated fields.