World is now on Opti ID! Learn more

Jacob Khan
Nov 11, 2011
  3902
(0 votes)

Commerce Manager filter meta properties by language

I was recently asked by a Partner to assist them in an issue they have with EPiServer Commerce and multiple languages. They run around 15 languages and have around 10 xhtlm meta properties on a single product/sku. This means that every time they are editing a sku they see all the language properties.

I made a simple little drop down list that switches between the languages and only loads the classes needed for each language. This makes it easier for the editors when working with multiple languages.

Capture

Meta fields will be fetched as they are needed depending on the language. The loading time is decreased and it is easier to understand for editors. However if you are moving between languages without saving nothing is stored in memory so remember to save in between changing languages.

The plugin needs some configuration but is real easy to use. Since it is added to the eCommerceFramework and not the site there is no epimodule installation. Of course, these are the kinds of things EPiServer is considering for enhancements in a future release.  In the mean time you can get started with this add-on by downloading the code and configuring it. Roger Cevung has also written an article on how to extend the commerce manager here.

In the zip there is a readme that will help you install the feature. Please add comments to the blog for questions and ideas.

If you have problems with the compiling because it cannot find the usercontrols simply remove them from the designer files and add them manually to the codebehind.

This plugin works for CMS 6 R2 with Commerce 1 R2 SP1

Thanks to Nansen for testing this out

Nov 11, 2011

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |