Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


How to localize product's description

Taken from messages of David E. Jones and Matthias Ohlemeyer
This is handled through the alternate locale feature of the Content Manager. Each ProductContent will point to the content for the "default" locale, and that Content can have other content associated with it as alternate locale content
There are various reasons for this structure, but the main one is to be able to create a tree of defaults and to use a generic structure rather than one for each place Content is used in the system.
For clarification it goes like this:Product
-> ProductContent
-> Content -> DataResource
-> ContentAssoc (type: ALTERNATE_LOCALE)
-> Content -> DataResource
-> ContentAssoc (type: ALTERNATE_LOCALE)
-> Content -> DataResource
-> ContentAssoc (type: ALTERNATE_LOCALE)
-> Content -> DataResource
...
Unfortunately, the ProductContent UI in the catalog manager is somewhat misleading and could certainly use some improvements to make it easier to deal with this structure.
Step by step guide:

  1. In Catalog Manager, go to the Edit product content tab; Clear the Product Name Entry in the "Override Simple Fields". When localizing, these fields must be emtpy, I think. They have precedence over the localized product name content.
  2. Create a "Product Name content" (actually four entity values get created: ProductContent, Content, DataResource, ElectronicText) in your preferred locale.
  3. In the Content Manager create a new Content (type "Template") with a different locale and a DataResource (Type "Long Text") belonging to the new content.
  4. Associate the new content to the product content as "Alternate Locale"Now, in ecommerce, the product name should be displayed in diffent locales depending on the browser settings.

...