Hi Jo,

It is possible for a non nav page to display navigation.

It is a technique call navigation emulation.

Simple version:
<!IoRangeDynLink>
<!IoRangeNoRedDotMode><!IoRangeRedDotMode><%anc_link%><!/
IoRangeRedDotMode><!/IoRangeNoRedDotMode>
<%!! Navigation:OutputArea(LeftNavArea, Bool:True, Guid:<%inf_page_guid
%> !!%>
<!/IoRangeDynLink>


Advanced version
<reddot:cms>
        <if>
                <query
valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage).GetRootIndex().Id"
operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
                        <!-- This Page is in Navigation Structure -->
                        <htmltext>
                                <%!! Navigation:OutputArea(Left Navigation, 
Bool:False,
Context:CurrentMasterPage.Id, Bool:False) !!%>
                        </htmltext>
                </query>
                <query
valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage).GetRootIndex().Id"
operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
                        <!-- The Page 1 Level Up is in Navigation Structure -->
                        <htmltext>
                                <%!! Navigation:OutputArea(Left Navigation, 
Bool:False,
Context:CurrentMasterPage.MainLink.OwnerPage.Id, Bool:False) !!%>
                        </htmltext>
                </query>
                <query
valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage).GetRootIndex().Id"
operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
                        <!-- The Page 2 Levels Up is in Navigation Structure -->
                        <htmltext>
                                <%!! Navigation:OutputArea(Left Navigation, 
Bool:False,
Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.Id,
Bool:False) !!%>
                        </htmltext>
                </query>
                <query
valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage).GetRootIndex().Id"
operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
                        <!-- The Page 3 Levels Up is in Navigation Structure -->
                        <htmltext>
                                <%!! Navigation:OutputArea(Left Navigation, 
Bool:False,
Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.Id,
Bool:False) !!%>
                        </htmltext>
                </query>
                <query
valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage).GetRootIndex().Id"
operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
                        <!-- The Page 4 Levels Up is in Navigation Structure -->
                        <htmltext>
                                <%!! Navigation:OutputArea(Left Navigation, 
Bool:False,
Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.Id,
Bool:False) !!%>
                        </htmltext>
                </query>
                <query
valuea="Context:Indexes.GetIndexByPage(Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage).GetRootIndex().Id"
operator="==" valueb="Context:Indexes.RootIndexList[Int:0].Id">
                        <!-- The Page 5 Levels Up is in Navigation Structure -->
                        <htmltext>
                                <%!! Navigation:OutputArea(Left Navigation, 
Bool:False,
Context:CurrentMasterPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.MainLink.OwnerPage.Id,
Bool:False) !!%>
                        </htmltext>
                </query>
                <query type="else">
                        <htmltext>
                                <%!! Navigation:OutputArea(Left Navigation, 
Bool:False,
Context:CurrentMasterPage.Id, Bool:False) !!%>
                        </htmltext>
                </query>
        </if>
</reddot:cms>

Best,

-Jian

On Dec 7, 11:46 am, JoFo <[email protected]> wrote:
> Hi Jian,
>
> I understand it's probably difficult to help out when you have never
> seen the project...we're in talks with Opentext about optimising
> performance and some of our publishing problems, so hopefully that
> plus some of your suggestions will get it sorted :)
>
> I think the problem is that if a page isn't included in navigation
> manager, we have problems displaying the left hand nav on that page.
> The code for the left hand nav is quite complicated and was written by
> an opentext consultant, but they won't support it as it's a 'code
> issue'.
>
> Thanks for all your suggestions though, I will try to implement some
> and see where it gets me :)
>
> Jo
>
> On Dec 2, 3:24 pm, Jian Huang <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hi Markus,
>
> > I think you mean lst_navigation.
>
> > Yeah, that works.  Page publisher is able to crawl following page, but
> > the link do not show up in live website's HTML code.
>
> > It is really up to the user's preference though.  Depending on the
> > volume of the site, running server side executed page just for that
> > purpose might be over kill and no so good in high volume.
>
> > Also, with this method, all content class templates need to be changed
> > from having default extension of htm to asp or whichever server side
> > language.
>
> > Again, it all depends on the user's preference.
>
> > Good suggestion though.
>
> > -jian
>
> > On Dec 1, 9:39 pm, Markus Giesen <[email protected]> wrote:
>
> > > Hi Jian,
>
> > > what if you would put the inf_current_page_url into a .NET or other
> > > code language comment block?
> > > That would hide the code from being shown in the HTML but it would
> > > still be in the page during publishing (as long as you don't run it in
> > > PreExecute).
> > > Would that work?
>
> > > Markus
>
> > > On Dec 2, 4:54 am, Jian Huang <[email protected]> wrote:
>
> > > > Hi Jo,
>
> > > > Sorry for the delayed reply.
>
> > > > Without looking at the project, I don't think I will be able to
> > > > provide a full solution, but I will try, but please keep in mind that
> > > > some of my assumption about the project might be wrong.
>
> > > > A navigation should not be generated base on keywords, it should
> > > > follow an IA.
>
> > > > A navigation page should live in a location, the rest of its
> > > > appearances in left navigation should be handled via a redirect page.
>
> > > > News articles should not be navigation/master page because that
> > > > significantly increase the size of the site's navigation structure.
>
> > > > Rule of thumb, if link to the page do not show up in navigation, then
> > > > that page should not be a navigation page.
>
> > > > maybe the new list can be generated with just a regular list
> > > > blockmark?
>
> > > > Again, I am not sure about the requirement of the project nor existing
> > > > structure, I am just throwing out general suggestions for now.
>
> > > > -Jian
>
> > > > On Nov 30, 5:34 am, JoFo <[email protected]> wrote:
>
> > > > > Hi Jian,
>
> > > > > Just a quick question....if our lists in the central column that are
> > > > > displayed using the info element instead of the list element, but a
> > > > > lot of our lst_navigation lists are keyworded (but not necessarily
> > > > > displayed), will this still impact on the publishing time? I'm not
> > > > > sure how to get around having lst_navigation as non-keyworded, as a
> > > > > lot of our different news lists in each section of the site are pulled
> > > > > together using this method.
>
> > > > > Thanks
>
> > > > > Jo
>
> > > > > On Nov 25, 3:31 am, Jian Huang <[email protected]> wrote:
>
> > > > > > Hi Jo,
>
> > > > > > The lst_link need to be within the list blockmark.  In your case, 
> > > > > > just
> > > > > > make sure it is within smartedit and then non smartedit blockmark.
>
> > > > > > The lst_link should be used to pull the info_current_page_url 
> > > > > > through.
>
> > > > > > Yes, lst_navigation with list blockmark must be there for the 
> > > > > > publish
> > > > > > builder to crawl following pages.  You can use HTML comment 
> > > > > > blockmarks
> > > > > > to comment it out, not many people will view source on published
> > > > > > websites...is that your concern?
>
> > > > > > -Jian
>
> > > > > > On Nov 24, 6:28 am, JoFo <[email protected]> wrote:
>
> > > > > > > Also, I have put the lst_navigation in html code at the bottom of 
> > > > > > > the
> > > > > > > pages, but not in the list blockmark as this displays a very long 
> > > > > > > list
> > > > > > > which we didn't really want. Is this essential for pages that are
> > > > > > > hidden in the nav to be published? Is there a way to not show it 
> > > > > > > in
> > > > > > > the published version, but still allow the pages to be published? 
> > > > > > > (I
> > > > > > > tried with smart edit blockmarks only but it didn't publish our 
> > > > > > > hidden
> > > > > > > pages).
>
> > > > > > > Thanks!
>
> > > > > > > On Nov 23, 5:36 pm, Jian Huang <[email protected]> wrote:
>
> > > > > > > > Hi Jo,
>
> > > > > > > > The shadowlist method is no longer valid.  Instead, use the 
> > > > > > > > list to
> > > > > > > > put the info_current_page_url placeholder through instead. Use 
> > > > > > > > that
> > > > > > > > method on lists that uses keyword based page connection.
>
> > > > > > > > Use the redirect method on lst_navigation should a 
> > > > > > > > navigation/master
> > > > > > > > page is connected to multiple locations.
>
> > > > > > > > For others, see if you can use dynamic anchor instead of a list.
>
> > > > > > > > The plugin I provided have a fix button should the page is 
> > > > > > > > connect to
> > > > > > > > an anchor and it is not a mainlink.
>
> > > > > > > > Also, make sure you have the list blockmark around your
> > > > > > > > list_navigation, and that resulting code is visible at publish 
> > > > > > > > time
> > > > > > > > (within HTML comments is fine).
>
> > > > > > > > You are getting close, please report back when you can.
>
> > > > > > > > -Jian
>
> > > > > > > > On Nov 23, 8:06 am, JoFo <[email protected]> wrote:
>
> > > > > > > > > Hi Jian,
>
> > > > > > > > > Having run the plugin with maximum of 400 results, a lot of 
> > > > > > > > > pages have
> > > > > > > > > come up with at least 3 links (inc keywords). I think on most
> > > > > > > > > keyworded lists we are already using the shadow list method.
>
> > > > > > > > > Running it without keywords brings up about 30 pages with 
> > > > > > > > > multiple
> > > > > > > > > links - should I just fix these pages, or the ones with 
> > > > > > > > > multiple
> > > > > > > > > connections including keywords, or both? How would you 
> > > > > > > > > recommend to
> > > > > > > > > fix the pages with multiple connections, with the redirect 
> > > > > > > > > method?
>
> > > > > > > > > Thanks
>
> > > > > > > > > Jo
>
> > > > > > > > > On Nov 18, 4:14 pm, Jian Huang <[email protected]> 
> > > > > > > > > wrote:
>
> > > > > > > > > > Hi Jo,
>
> > > > > > > > > > Available in SolEx now
>
> > > > > > > > > >http://www.solutionexchange.info/check-multi-page-connection.htm
>
> > > > > > > > > > On Nov 18, 11:12 am, JoFo <[email protected]> 
> > > > > > > > > > wrote:
>
> > > > > > > > > > > Do you have a link to the plugin please, as the link in 
> > > > > > > > > > > the other post
> > > > > > > > > > > no longer works
>
> > > > > > > > > > > Thanks
>
> > > > > > > > > > > Jo
>
> > > > > > > > > > > On Nov 18, 4:04 pm, JoFo <[email protected]> 
> > > > > > > > > > > wrote:
>
> > > > > > > > > > > > Hi Jian,
>
> > > > > > > > > > > > We didn't get around to installing the plug in, I will 
> > > > > > > > > > > > try to get it
> > > > > > > > > > > > done and see if the other points help too. We do have a 
> > > > > > > > > > > > lot of news
> > > > > > > > > > > > articles/press releases that are master pages, so I 
> > > > > > > > > > > > will look into
> > > > > > > > > > > > that too.
>
> > > > > > > > > > > > Thanks
>
> > > > > > > > > > > > Jo
>
> > > > > > > > > > > > On Nov 18, 2:39 pm, Jian Huang 
> > > > > > > > > > > > <[email protected]> wrote:
>
> > > > > > > > > > > > > Hi Jo,
>
> > > > > > > > > > > > > As per discussion here:
>
> > > > > > > > > > > > >http://groups.google.com/group/reddot-cms-users/browse_thread/thread/...
>
> > > > > > > > > > > > > Were you able to implement the recommend prior to 
> > > > > > > > > > > > > publishing?
>
> > > > > > > > > > > > > -Jian
>
> > > > > > > > > > > > > On Nov 18, 6:45 am, JoFo <[email protected]> 
> > > > > > > > > > > > > wrote:
>
> > > > > > > > > > > > > > Hi,
>
> > > > > > > > > > > > > > We are having several issues with publishing at the 
> > > > > > > > > > > > > > moment. One is
> > > > > > > > > > > > > > that a publish can take 8 hours or longer (full 
> > > > > > > > > > > > > > site publish). Also,
> > > > > > > > > > > > > > when publishing following pages, it decides to 
> > > > > > > > > > > > > > publish the whole site.
> > > > > > > > > > > > > > And the last problem is that when we want to 
> > > > > > > > > > > > > > publish the whole site,
> > > > > > > > > > > > > > some pages are missed out and not published (pages 
> > > > > > > > > > > > > > are released etc).
>
> > > > > > > > > > > > > > I am wondering if these problems are all related? 
> > > > > > > > > > > > > > Has anyone else had
> > > > > > > > > > > > > > similar problems and have any idea on how to fix 
> > > > > > > > > > > > > > it? We have several
> > > > > > > > > > > > > > tickets open with support, and some that have been 
> > > > > > > > > > > > > > closed, but they've
> > > > > > > > > > > > > > never offered us an actual solution.
>
> > > > > > > > > > > > > > Hope someone can help.
>
> > > > > > > > > > > > > > Thanks.- 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.

Reply via email to