Thanks Jian, that solution still does publish a duplicate page though even though it's not linked anywhere.
What I should have added to my post was that my code snippet above is also only run in Publish mode, thus avoiding the ampersand killing render tags issue. The tag is only required on the published page in order to allow filtering by the search engine. Of course, this solution is only required if you're using a search engine that you need to filter out the duplicate files. Although, you still could use the cut down version to prevent Google indexing the child pages in a static site. Cheers, Gavin On 3 February 2012 01:30, Jian Huang <[email protected]> wrote: > A solution to make the page publish as mainlink, hence solving the > duplicate page issue can be found here > > http://simplyreddot.blogspot.com/2012/01/duplicate-pages.html > > -Jian > > On Feb 1, 9:26 pm, Gavin Cope <[email protected]> wrote: > > I know this is an old post but I've just come up against this and whilst > > all the above tactics work as described, it's a whole new ball game when > > you throw Verity or Common Search into the mix. The orphan duplicates > still > > get indexed and thus returned in any search results. > > > > I got around this by adding the following code to my foundation > templates: > > <reddot:cms> > > <if> > > <query valuea="String:<%inf_UrlOfCallingPage%>" operator="==" > > valueb="String:<%inf_UrlOfCallingPageMainLink%>"> > > <htmltext> > > <rde-dm:import> > > <keywords mode="set" keyword-separator="," > > name-value-separator=":" hierachy-separator="."> > > IsMainLink:1 > > </keywords> > > </rde-dm:import> > > </htmltext> > > </query> > > <query type="else"> > > <htmltext> > > <meta name="robots" content="noindex" /> > > </htmltext> > > </query> > > </if> > > </reddot:cms> > > > > I then added (IsMainLink:1) to my search queries and - as if by magic - > all > > the duplicates disappeared :) > > > > To explain the above code, it compares the URL of the Calling Page and > the > > URL of the Calling Page's Main Link. If they're the same thing, the page > is > > tagged. If the two values don't match, no tag is added and for good > > measure, I put in a meta tag to prevent any external search engines > finding > > and indexing the orphan page. > > > > So whilst this doesn't address the server space issue, the above and > > aforementioned tactics prevent the page being linked to or found in > search > > results. > > > > Cheers, > > > > Gavin > > > > On 25 January 2011 17:43, kimdezen <[email protected]> wrote: > > > > > > > > > > > > > > > > > on a side note, you can set up automatic referencing within the > > > template - so that any new page instances will have the reference in > > > place if you decide to use the shadow list method! > > > > > On Jan 25, 9:05 am, gk <[email protected]> wrote: > > > > Thank you. The shadow list works perfectly and the page is now only > > > > being published once in the correct place. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "RedDot CMS Users" group. > > > To post to this group, send email to [email protected] > . > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group at > > >http://groups.google.com/group/reddot-cms-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/reddot-cms-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
