Hi Richard, Yeah, I have seen this before. Basically, Page A is a news article shell page, which contains a target container for all real new article pages to throw their contents into. Page B is a the RSS feed listing page. Page C is the actual page that contains the real content. Page C can be connected to multiple locations: mainlink and RSS via category and keywords.
Went down this route before and I successfully explored most of the solutions that did not work. 1. Yes, please remove that RSS project variant 2. See if you can get rid of the target container and convert content class of Page C into a Foundation content class made just for new articles. Oh, this is production, good luck and god speed. -Jian On Tue, Mar 4, 2014 at 6:32 AM, RustyLogic <[email protected]> wrote: > Hi Richard, > > No experience with Target containers, but, I do avoid alternate variants > for the very reasons you have stated. I would suggest using the ASPX > variant as you have suggested (that's what I always do for XML). > > Ta, > John > > > On Tuesday, March 4, 2014 9:23:03 AM UTC, 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: >> >> 1. Page A, ASPX Variant, has a container con_A that is a target >> container. Its URL is set to "pageA" >> 2. 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 [email protected]. > To post to this group, send email to [email protected]. > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
