[opencms-dev] R: RE: R: Re: Detail pages
gnorrus at libero.it
gnorrus at libero.it
Thu Jul 26 22:45:17 CEST 2012
Thanks for your reply AlexBut is possible to "disable" detail page in some way?I ask because now I have a model page with 2 columns. On the right one I have a group container, and the content of my structured content "product" is on the left part. But I need to drag and drop some other content in the group container for EVERY product. But if I do that, all products page will have that content (because the detail page is unique for that content) on the right part and this is not correct because i need to personalize the detail page with different content on the right
If I don't use detail page, inside the list the url to detail page will be /.content/products/product_00001.html...
Is there a solution for that?
Thanks
----Messaggio originale----
Da: alex at opencms.org
Data: 24-lug-2012 16.52
A: <gnorrus at libero.it>, "The OpenCms mailing list"<opencms-dev at opencms.org>
Ogg: RE: [opencms-dev] R: Re: Detail pages
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Sprechblasentext Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.SprechblasentextZchn
{mso-style-name:"Sprechblasentext Zchn";
mso-style-priority:99;
mso-style-link:Sprechblasentext;
font-family:"Tahoma","sans-serif";}
span.E-MailFormatvorlage21
{mso-style-type:personal-reply;
font-family:"Verdana","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
->@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Sprechblasentext Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.SprechblasentextZchn
{mso-style-name:"Sprechblasentext Zchn";
mso-style-priority:99;
mso-style-link:Sprechblasentext;
font-family:"Tahoma","sans-serif";}
span.E-MailFormatvorlage21
{mso-style-type:personal-reply;
font-family:"Verdana","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
->
-->See my comments in the mail: From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of gnorrus at libero.it
Sent: Tuesday, July 24, 2012 3:52 PM
Subject: [opencms-dev] R: Re: Detail pages Hi Alex
Your answer is clear, but I have some other questions about detail page.
Why the url of the resource is not lowercase?You are right this should be lowercase, but is not because it has not been implemented that way. I have to look into this and see if it needs to be fixed at core level, or if there is some sort of interface so that it can be done by configuration.I mean, in your example "Some-great-title". The first letter is uppercase, like the resource title. Is it possibile to have it lowercase? If not, do I have to create another field inside xsd where put the "SEO title" so the user can write it lowercase?Out of the box the “extra field” is the only option, but as said I agree it should be different. Lowercase by default. And configurable.
The other question is about the position of the detail page.
Imagine this site structure:
- products
|- Type A
|- Type A1
|- Type A2
|- Type A3
|- Type B
|- Type B1
|- Type B2
|- Type B3
If I use categories I can have all produts categorized in the right way and I can display them inside List content in the right way
But if i have a page where I should have the list of all products of Type A + Type B (and this page is inside products folder), where do I have to put the
detail page?
If I put inside Type A folder, also product of type B will have this url:
/products/TypeA/product-name and this is not correct.
In this case I should have another detail page inside products folder in order to have urls like this:
/products/product-name. But, with sitemap, the detail page is created always inside a folder, so I would have /products/product/product-name.
I would suggest not placing this page in the products folder in this case.
This is not a good solution (expecially for SEO).
The detail page is named always index.html, so If i move the detail page inside products folder (having the correct url: /products/product-name) i can't have a index.html page that is the list of all products (i should name it for example "list.html"), because if i try to rename the detail page, then i get an error when clicking on one product in the list (resource not found)
You cannot rename the detail page “index.html”.
So in this case I must create 3 detail pages, one inside products folder to display all products of type A and B, then another one inside Type A folder and another one inside Type B folder. But also this is not good for SEO, because in this case the same content is reachable with different urls (/products/product-name, /products/TypeA/product-name) I suggest going with 3 detail pages and a rule in robots.txt that makes sure only one content is indexed. In general I see your point, but the detail page is meant to work with one piece type content only, not multiple types on the same detail page. You will need some sort of workaround if you want this.Kind Regards,Alex. -------------------Alexander Kandzior Visit OpenCms Days 2012 Conference and Expo September 25 to 25, 2012 in Cologne, Germany http://www.opencms-days.org Alkacon Software GmbH - The OpenCms Experts http://www.alkacon.com - http://www.opencms.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20120726/5923e535/attachment.htm>
More information about the opencms-dev
mailing list