Hi Richard, Neat idea, and I actually tested it out when it was first suggested because it could potentially become a best practice.
The main obstacle is that links pages under A would not appear when viewer from the container page B. Another problem one may have to deal with is that pages with duplicate content are now published onto the same site, not really SEO friendly. However, this is definitely a solution for sites that require the level of context you have mentioned. Best, -Jian On Aug 2, 9:28 pm, "Richard Hauer (5 Limes)" <[email protected]> wrote: > Hi Jian, > > What I was thinking was a bit simpler than that. > The down side of my approach is that you'll get different URLs as you > will end up with 2 different pages, but they will contain identical > content so the client probably won't have an issue with that. > There may be some tweaks needed to the Nav code to ensure the context > (i.e. "current node") is correct too. A will only recognise its > context where it's being used as a master page, not where its being > used as content to another master page. I think this could be handled > with some thought. > > I was thinking: > > Page to dupe = A > A is a master page and connected in to the nav as usual > B is also a master page with a Container and no content other than the > container tag. I can't remember whether it _has_ to also have a list > for Nav Manager to accept it as a master page but if so don't include > the list in the markup > > Add A into Nav tree wherever you want > Add B wherever you want > Connect A to the Container in B. Same page, not a reference. > > B will have its own URL, different than A - it will need it as the > context highlighting in the menu may be different as I mentioned > above. > The main thing is that the content will be identical and that changes > to Page A are automatically reflected everywhere, obviously. > > The problem with the redirect approach is that it will not be able to > correctly present the different contexts and may confuse the user. > Clicking a link in one section and sending them to a different section > is a bit dramatic. > > HTH. > > Richard H. > > On Aug 2, 12:03 am, Jian Huang <[email protected]> wrote: > > > > > > > > > Hi Richard, > > > That is a very creative suggestion. > > > By attaching the other page, I assume you meant referencing the other > > way, else it would create publication issues due to pages being > > connected to multiple locations. > > > There are 2 things one would have to be aware of if one choose to use > > this method: > > - Instead of using the single parameter navigation output area, one > > has to use navigation emulation with all 4 parameters in navigation > > outpput area. > > - Links to deeper navigation will not appear. > > > For example: > > Page 1 > > Page a > > Page a.1 > > Page a.2 > > Page a.3 > > Page b > > Page c > > Page 2 > > Page a (container referencing Page a) > > > Page a.1, Page a.2, Page a.3 will not be rendered as navigation item > > when viewed from Page a (container referencing Page a). > > > -Jian > > > On Jul 30, 6:21 pm, "Richard Hauer (5 Limes)" > > > <[email protected]> wrote: > > > How about creating a now Master Page that has nothing but a container > > > in it and attaching the other page to that? > > > > HTH. > > > > Richard Hauer. > > > > On Jul 30, 2:28 am, Jian Huang <[email protected]> wrote: > > > > > or have > > > > > <META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"> > > > > > On Jul 29, 12:16 pm, Tony Gayter <[email protected]> wrote: > > > > > > Yes that is one way around it, just need to keep a record of pages > > > > > which are > > > > > linked to what otherwise you would end up with dead links if you > > > > > remove the > > > > > actual page. Also make sure its a 301 redirect so google doesnt get > > > > > teh hump- Hide quoted text - > > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text - -- 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.
