Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Force load "en" version of catalog content when requesting "sv"
This is out of box functionality in commerce, but you can take help from this blog:
http://fellow.aagaardrasmussen.dk/2016/05/22/optimized-language-support-in-episerver-commerce-with-fallback/
Edited,
Feb 01, 2021 19:41
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
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.