[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context
[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14213461#comment-14213461
]
Deepak Dixit commented on OFBIZ-5823:
-
IMO we can discard this issue. In OFBiz we have two mechanism to store metadata
so IMO both ways are fine and we can add/render metadata using both ways. CMS
support both ways for metadata.
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, Screen Shot 2014-10-18 at 8.19.17
PM.png, screenshot-1.png
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)
[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context
[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176725#comment-14176725
]
Deepak Dixit commented on OFBIZ-5823:
-
Hi Pierre,
Thanks for the screen shot, I am able to add the metadata from cms tree scree.
There are two way to add the meta data:
- In first way you can add the meta data in ContentMetaData entity based on
metaDataPredicateId and can access it using following way:
{code}
meta name=description
content=${(decoratedContent.metadata['metaDataPredicateId'])!}/
{code}
You can create this type of meta data form
http://demo-trunk-ofbiz.apache.org/content/control/EditContentMetaData?contentId=CMSS_DEMO_PAGE1
- Another way is to add the the metadata as subcontent. ie. Create the content
and create content assoc and can access the meta data content using following
way:
{code}
meta name=description
content=${(decoratedContent.subcontent.metaDescription.render)!}/
{code}
You can crate this type of metadata form
http://demo-trunk-ofbiz.apache.org/content/control/WebSiteCms?webSiteId=CmsSite
You are right, we need to make it consistent and will need to use the
ContentMetaData entity for this.
Let's wait for others opinion...
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, Screen Shot 2014-10-18 at 8.19.17
PM.png, screenshot-1.png
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)
[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context
[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context
[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175921#comment-14175921
]
Deepak Dixit commented on OFBIZ-5823:
-
Thanks Pierre,
ContentMapFacade have different way to render the content.
You can refer the HtmlHead.ftl for this.
{code}
meta name=description
content=${(decoratedContent.subcontent.metaDescription.render)!}/
meta name=keywords
content=${(decoratedContent.subcontent.metaKeywords.render)!}/
{code}
IMO we can close this task.
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)
[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context
[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175964#comment-14175964
]
Gaudin Pierre commented on OFBIZ-5823:
--
Many thanks Deepak, I was on the wrong way !!
But i think that we should change the way CMS tree view of a website stores
metadata because it is store into DataResource entity, not into
ContentMetaData.
I'd like to provide a patch to fix this.
Do you agree with it?
Many thanks,
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)
[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context
[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176010#comment-14176010
]
Deepak Dixit commented on OFBIZ-5823:
-
Hi Pierre,
Are you referring
http://demo-trunk-ofbiz.apache.org/content/control/WebSiteCms?webSiteId=CmsSite
screen?
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)
[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context
[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176014#comment-14176014
]
Gaudin Pierre commented on OFBIZ-5823:
--
Hi Deepak,
Yes, if you select one page and add meta data, then for each meta data a
Content with a DataResource is created.
Thanks
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)
[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context
[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176039#comment-14176039
]
Gaudin Pierre commented on OFBIZ-5823:
--
Hi Deepak,
OK,
Click one page from the content tree (ie CMS Site Demo blog screen example [
CMSS_DEMO_BLOG ])
On the right side of the tree, the content is shown. Above shown content ,
there is 3 links in black color. Select link Meta Tags . Then add the value
and save.
Please, find a screen shot as attachment.
Thanks,
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, Screen Shot 2014-10-18 at 8.19.17
PM.png
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)
[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context
[
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175833#comment-14175833
]
Deepak Dixit commented on OFBIZ-5823:
-
Hi Gaudin,
We have support in cms to render the metadata using
contentMapFacade.get(metadata).
Why are you using dataResource for meata data?
You can use ContentMetaData entity for the same.
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)
