[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175910#comment-14175910
]
Gaudin Pierre commented on OFBIZ-5823:
--------------------------------------
Hi Deepak,
Ok thanks, i haven't seen that the metada were in the contentMapFacade...
I use dataResource entity because in the CMS tree view of a website entity
DataResource is used to store metadata.
Maybe we could add both in metadata contentMapFacade : the ones from
DataResource and the ones from ContentMetaData ?
Another solution is to use ContentMetaData in CMS tree view instead of
dataResource ?
Pierre
ps : My first mane is Pierre ;-)
> Add CMS metadata into renderer context
> --------------------------------------
>
> Key: OFBIZ-5823
> URL: https://issues.apache.org/jira/browse/OFBIZ-5823
> Project: OFBiz
> Issue Type: Improvement
> Components: content, specialpurpose/cmssite
> Affects Versions: Trunk
> Reporter: Gaudin Pierre
> Priority: Minor
> Fix For: Trunk
>
> Attachments: CMSMetadata.patch
>
>
> In website CMS, for a page, you can specify metadata.
> Unfortunatly those metadata are not availables into the cms page context.
> This patch add metadata into context of all pages. Thus you can use them.
> To test this patch, add metadata associated to a cms page (ie
> metaDescription).
> Edit the cms page to add ${metaDescription}.
> Then display the page
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
