Hi guys,
Here is the issue, I want my navigation to look like this:
1. Page1
1. Page a
2. Page b
3. Page 2
2. Page 2
3. Page 3
As you can see Page 2 is a top level nav item but also appears as a sub
section of Page 1
How do you handle this with nav manager? When
As far as I am aware, and goign by logical though, you cant. A page can only
physically exist in one place, you can referance it in lists etc but nav
manager wont pull it though, it will only pull the page though when you use
the list its attatched to. why would anyone want to create this horren
Yeah I was afraid that is the case... but unfortunately the client does want
this.
The site structure is split up into two sections they call Industries and
Capabilities and Some Capabilities are also listed as sub Items of an
Industry.
I am thinking of creating a separate page and referencing
Hi guys,
There is actually a solution for this.
For any secondary links, simply create a page that does nothing but
redirects to an anchor, either via metarefresh or javascript.
Also, make sure content class of the redirect page is set to master
page so it show up in navigation.
Best,
-Jian
O
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
--
You received this message because you are subscribed to the Go
or have
On Jul 29, 12:16 pm, Tony Gayter 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
--
You re
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 wrote:
> or have
>
>
>
> On Jul 29, 12:16 pm, Tony Gayter wrote:
>
>
>
> > Yes that is one way around it, just need to keep a re
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
Thanks guys this has been very interesting and helpful. I think I will go
with the meta refresh approach in this case.
- Dmitry
--
You received this message because you are subscribed to the Google Groups
"RedDot CMS Users" group.
To view this discussion on the web visit
https://groups.google
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 N
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
Hi Jian,
I suspect the issue with the links is because we have broken the
Navigation chain.
To restore it, on the "Empty Container Template" that is also a master
page (B in this case), add a List and mark it as the navigation list.
Then reference the navigation list on A to the navigation list on
Hi Richard,
Your suspicion is correct regarding the broken naigation chain. I
have also tested out what you have suggested in my first test. The
navigation would not be displayed because navigation manager do not
accept references nor secondary linking appearances.
I just want to add that in a
13 matches
Mail list logo
