Jeff Wallace
Nov 18, 2011
  3164
(0 votes)

Filter Commerce SEO Tab Properties by Language

Based on CMS 6 R2 and Commerce R2 SP1

Recently Jacob Khan posted a blog and code for filtering the EPiServer Commerce product catalog /properties/metadata by language.  This is of course a fabulous enhancement and one that many customers will likely want to utilize to provide an improved user experience when editing the catalog.  I thought I’d take advantage of my colleague's good work and add the same for the SEO tab since it also contains properties differentiated by each language. 

 

In an ideal world I could have stolen the base of his code, implemented things in the same manner, and it simply would have worked.  Unfortunately since the SEO tab contains child controls in a placeholder I actually had to think about it for a minute and write a few more lines of code.  So much for just stealing from others and claiming glory in the blog post, even though that’s basically what I did, with a few extra bits of effort.  Smile  Anyway, alas it does indeed work.  I also created a language selector helper class for the dropdown so the two tabs in the UI can share this functionality.  The code is commented out with explanation where it differs from the core Commerce code.  If you intend to use it in a production environment you’ll probably want to remove this.

 

image

 

Note that just like Jacob's code, if you change languages in the drop down without saving, the previous languages updates will be lost.  So, in the current state you should select the OK button with each language change.  Some may not like this experience and you’re more than welcome to provide additional updates to this code and feed it back into the community. Winking smile  There’s different ways this could be handled but I’ll let you decide…unless a find a few more cycles to burn and tackle it myself.

 

Get the code here.  It includes Jacob's code as well as my own.  I’ve also included an updated ReadMe.txt file for the setup steps.

 

For a good introduction to customizing EPiServer Commerce, check out Roger Cevung's article. 

 

Please note, this is intended as a starting point for you to customize for your project needs. This code is provided “as is” without warranty or guarantee of operation. Use at your own risk. Good luck and enjoy!

Nov 18, 2011

Comments

Nov 18, 2011 12:19 PM

Fabulous!

Please login to comment.
Latest blogs
Opti ID overview

Opti ID allows you to log in once and switch between Optimizely products using Okta, Entra ID, or a local account. You can also manage all your use...

K Khan | Jul 26, 2024

Getting Started with Optimizely SaaS using Next.js Starter App - Extend a component - Part 3

This is the final part of our Optimizely SaaS CMS proof-of-concept (POC) blog series. In this post, we'll dive into extending a component within th...

Raghavendra Murthy | Jul 23, 2024 | Syndicated blog

Optimizely Graph – Faceting with Geta Categories

Overview As Optimizely Graph (and Content Cloud SaaS) makes its global debut, it is known that there are going to be some bugs and quirks. One of t...

Eric Markson | Jul 22, 2024 | Syndicated blog

Integration Bynder (DAM) with Optimizely

Bynder is a comprehensive digital asset management (DAM) platform that enables businesses to efficiently manage, store, organize, and share their...

Sanjay Kumar | Jul 22, 2024