Versions Compared

Old Version 17

changes.mady.by.user Carsten Schinzer

Saved on

compared with

New Version 18

changes.mady.by.user Carsten Schinzer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: adding remarks with regards to JIRA issue OFBIZ-4208

...

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!).
 

Info
titleHTML META tags use product.descriptionfor default Product-pages

The content of HTML Meta tags on product pages are handled in

Code Block
applications/order/webapp/ordermgr/WEB-INF/actions/entry/catalog/Product.groovy

The following content will be handled as i18n content, i.e. locale/fallback locale applies By default, the productContent.description entries are also used in <HTML><HEAD>...<META type="keyword" ...> tags, so using this can :

  • product.name (content items mapped as "PRODUCT_NAME" type)
  • catalog.name (not i18n)
  • productCategory.description (content items mapped as "DESCRIPTION" to all categories that this product is a member of)
    The following content will be handled as i18n content, i.e. locale/fallback locale applies in <HTML><HEAD>...<META type="description" ...> tags:
  • product.description (content items mapped as "DESCRIPTION" type)
    Using this will help you with localized SEO (=Search Engine Optimisation) projects.

MORE TO COME SOON (worked example)

...