Thanks guys, Manual concatenation of URL seems plausible, if a bit fragile.
I wondered if it's possible to reference a list to a dynamic anchor, but likely not. I will post back with the solution I used for future reference... when i think of one 😉 -----Original Message----- From: "Tim D" <timothy.j.da...@gmail.com> Sent: 5/03/2014 1:33 To: "reddot-cms-users@googlegroups.com" <reddot-cms-users@googlegroups.com> Subject: Re: Interesting Page URL Issue A work around: If all the pages live on the same target container (seems implied they do here) you could add and anchor placeholder then do a substring (rendertag or pre-ex) on this to get "pageA" and concatenate in you RSS template. On Tuesday, March 4, 2014 4:23:03 AM UTC-5, Richard Hauer (5 Limes) wrote: RDCMS v10.1 I’m having a Page URL issue that is a little interesting, looking for something that has worked for people that we haven’t tried before I tear the thing apart and re-organise it completely. Here’s the scenario: Page A, ASPX Variant, has a container con_A that is a target container. Its URL is set to “pageA” Page B, ASPX+RSS Variant, has a url of “pageB” and has a list pointed at the target container con_A with a bunch of connected pages, one of whom has a url of “pageC” Now in ASPX the generated url for pageC is “pageA-pageC.aspx” which is great. In the RSS feed (which is a different variant) which is published at pageB.rss the pages connected to the list seem to have no knowledge of the target container, so the elements inside the IoRangeList have blank URLs. I suspect this is because Page A’s template has no RSS variant, only ASPX, and there is no way to specify against the List that I want the URLs from a variant that isn’t the current one. I tried using an Info placeholder for PageURL pointed at the ASPX variant but that didn’t work either, instead I got a url that ignores the target container component, i.e. “pageC.aspx” I think the way to solve this is to kill the RSS variant and instead create an ASPX template that simply outputs RSS instead, so that the variant issue is factored out. But that’s kinda drastic and this is an existing production system so I was hoping to find a more subtle approach. I had a look at the render tags (event the more obscure stuff) and there doesn’t seem to be a way to generate a URL for a page in a variant other than the current variant. The Variant ID is hard-coded all over the place and no parameters can be used to override it, that I can see anyway. Thoughts? Richard H. -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to reddot-cms-users+unsubscr...@googlegroups.com. To post to this group, send email to reddot-cms-users@googlegroups.com. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to reddot-cms-users+unsubscr...@googlegroups.com. To post to this group, send email to reddot-cms-users@googlegroups.com. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
