SKUName localization

Martin Shin asked on January 14, 2015 14:47

Hi everybody. Is it possible localize SKUName for multistore?

Recent Answers


Roman Hutnyk answered on January 14, 2015 23:07

If this is what you're talking about, the answer is YES.

0 votesVote for this answer Mark as a Correct answer

Martin Shin answered on January 15, 2015 00:00

Hi Roman. Thank you for your answer. Problem in another point. I playing with local trial E-commerce version of Kentico 8.2.1 I do all exactly described in link provided by you. I can see products in different languages in appropriate pages. But, when I add product to basket, I see name of product based on default site content culture.

For example in demo E-commerce site default culture is English. I added new culture - Finland. And when I adding product to basket, I see English name of product. When I switch to Finnish, I still to see English name of product. And if I compare products in "E-commerce - Product" section I see product names associated with every culture (different names).

0 votesVote for this answer Mark as a Correct answer

Martin Danko answered on January 26, 2015 13:00

Hello Martin,

Regrettably this is a limitation by design at the moment. The reason is that documents are localized, so you can see multiple culture variants of the product but... there is only one SKU object. Inside the shopping cart data of SKU are displayed therefore it's not possible to get localized product inside the shoppint cart. I'm really sorry. I've already forwarded this as a requirement to product owner responsible for E-commerce module.

Best regards, Martin

0 votesVote for this answer Mark as a Correct answer

Martin Shin answered on January 26, 2015 13:10

Hi Martin. Thank you for explanation. Which recommendation for quick decision you can make? I tried to use localization strings. This method works. But I see the localization keys instead of the page names in the site tree.

0 votesVote for this answer Mark as a Correct answer

Martin Danko answered on January 26, 2015 17:49

Hello Martin,

You can use localization macros for fields like SKUName and SKUDescription are.

However, I would recommend you to create your custom document type fields and store the data you would store in SKUDescription field on per document basis where you can translate them.

If you need more details, please contact us via e-mail: support@kentico.com

Best regards, Martin

0 votesVote for this answer Mark as a Correct answer

Martin Shin answered on January 29, 2015 11:58

Hi Martin. Thank you for the answer. I tried use localization macros. For example if I place something, like this {$hdr.ProductOne$} to "Product name" field this is works for basket preview nice. But in Kentico in pages tree (left tree view in "Edit" mode I see key {$hdr.ProductOne$} instead Product name. Why?

If I create custom page type with custom fields and assign it as Product in E-commerce section (Page type represents a product type), I can't get any data from custom fields.

0 votesVote for this answer Mark as a Correct answer

Josef Dvorak answered on March 17, 2015 11:53

Hello Martin,

This is unfortunately downside of using translation macros for the DocumentName. Since the SKUName is also saved to the DocumentName the string will be used as-is in the content tree. The only solution to avoid this is to add a separate custom name field to:

Development -> Modules -> E-Commerce -> Classes -> SKU -> Fields

In this field you can store your custom product name and refer to it in transformations instead of the built-in SKUName. For example in the shopping cart transformation it will look like this:

<%# EvalText("SKU.SKUCustomName", true) %>

I also recommend using the Localizable text box as the Form control for your custom field. It will allow you to create localization strings directly from the product edit form.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.