THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Most typically, the entity.name, entity.description and entity.longdescription attributes can be internationalized. A table listing the i18n options of respective entity attributes will be worked in here soon.
| Panel | ||
|---|---|---|
| ||
When using i18n on these entities, the "direct" attributes must be empty, otherwise the CMS lookup will not occur. |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Each of your Content and DataSource items will need a unique ID, so make up your mind about naming conventions for the ContentId and DatasourceId that are related to your entities! |
...
- Product.name
- Product.description
- Product.longDescription
The corresponding relationships are built using the ProductContent entity where the productContentTypeId should be set to 'NAME', 'DESCRIPTION' or 'LONG_DESCRIPTION' for the content that will map to name, description or longDescription respectively (attention, the Demo Data does not define the LONG_DESCRIPTION content items, so you will need to touch this, sorry!).
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
By default, the productContent.description entries are also used in <HTML><HEAD>...<META type="keyword" ...> tags, so using this can help you with localized Search Engine Optimisation projects. |
MORE TO COME SOON (worked example)
...