Hi Vitaliy Thank you for the updates.
>From experience, there is a different between: <%!! Context:CurrentIndex.GetUrl() !!%> and <%!! Context:CurrentPage.GetUrl() !!%> GetUrl() from CurrentIndex produce links of type reference, so page builder do not crawl GetUrl() from CurrentPage produce links of type connected, so page builder crawls The navigation manager documentation advocates the use of CurrentIndex.GetUrl() in navigation templates, which is correct. It has been a best practice since version 7.5 for us to include <!--<!IoRangeList><%lst_Navigation%><!/IoRangeList>--> as part of the foundation page code so page publishing works the exact same way prior to the use of navigation manager. On Jan 26, 1:42 pm, Vitaliy Rabotnik <[email protected]> wrote: > UPDATE: OT Support just admitted that the method described above is > the best practice. > > On Jan 25, 10:05 am, Vitaliy Rabotnik <[email protected]> > wrote: > > > UPDATE: > > > Within all rendering tags in navigation templates pass Boolean True in > > the GetURL method: e.g. GetURL(BOOL:True). This causes the links built > > by rendering tags not to be followed during the publishing. > > > One every master/foundation page include navigation list in the html > > comment tags: > > > e.g. <!--<!IoRangeList><%lst_Navigation%><!/IoRangeList>--> > > > Therefore, the pages will be followed through the list. > > > By default the value is False and all links off the page are > > considered as links to following pages. > > > Works, but looks as a hack to me. This feature is implemented > > incorrectly. > > > On Jan 21, 2:09 pm, Vitaliy Rabotnik <[email protected]> > > wrote: > > > > UPDATE: > > > > I asked one of my guys to develop very simple 2-level site with one > > > navigational area. > > > > He published a section and the CMS published only the required > > > section. But I noticed he forgot to create Global publishing package. > > > I created one and as soon as i created it and inherited to the > > > following levels - the cms published the whole site again. Notice, > > > Home page was the root page and was not connected or referenced > > > anywhere else. > > > > On Jan 21, 10:23 am, Jian Huang <[email protected]> wrote: > > > > > Hi, > > > > > I just re-read you post, and saw how a sectional publish turned into a > > > > full site publish in your sample project. > > > > > Assuming full site, meaning including the home and all pages > > > > underneath that. > > > > > Is it possible that the home page is connected in multiple locations > > > > (Home link in header or footer), so when publish all following pages, > > > > home is considered a following page, then all pages underneath home > > > > are also... > > > > > Also, as Stefan mentioned, GetUrl() was used instead of > > > > GetUrl(Bool:True) in the navigation template. However, the BPP also > > > > uses GetUrl(), but it does the opposite of what you experience. > > > > > Would it be OK for you to export your sample project for us to test > > > > locally? > > > > > -Jian > > > > > On Jan 21, 7:41 am, "stefan.popp" <[email protected]> wrote: > > > > > > Hi, > > > > > > I think this is the normal behaviour since the new page builder is > > > > > available. > > > > > > MS 10.1 SP1 has a new feature: > > > > > > 2.1.6 Render Tag parameter for referencing pages > > > > > If you have a page A with a Render Tag creating a link to a page B, > > > > > the publishing > > > > > process will consider page B as following page and continue > > > > > publishing. > > > > > If this is not intended and you want page B not to be considered as a > > > > > following > > > > > page, you can use the new Boolean parameter that is available with > > > > > Management > > > > > Server 10.1 SP1: > > > > > <a href="<%!! Context:Pages.GetPage(Guid:[GUID PAGE B]).GetUrl(Bool: > > > > > True) > > > > > !!%>">Link</a> > > > > > With the value true, the link will only be considered as a navigation > > > > > link and will > > > > > be considered as not relevant for following pages. > > > > > With the value missing or false, the functionality will be unchanged. > > > > > > We have solved the problem mentioned above with this new release. > > > > > > Regards, > > > > > Stefan > > > > > > On Jan 20, 11:21 pm, Jian Huang <[email protected]> wrote: > > > > > > > Hello, > > > > > > > 1. It should. As a safety measure so at publish, page builder can > > > > > > see the link and crawl it, I place the following at the bottom of > > > > > > the > > > > > > foundation > > > > > > > <!-- <!IoRangeList><%lst_navigation%><!/IoRangeList> --> > > > > > > > please note lst_navigation should be the name of your lst navigation > > > > > > you use in your foundation. > > > > > > > 2. Hmmm...don't see dynmic link in my version... I see > > > > > > > ancInitialConfigDescription > > > > > > List Items > > > > > > Additional List Items (e.g. reference) > > > > > > Hidden List Items (do not inherit packages from here) > > > > > > > Maybe I have an older version. > > > > > > > On Jan 20, 3:07 pm, Vitaliy Rabotnik <[email protected]> > > > > > > wrote: > > > > > > > > I created very simple project using navigation manager. When > > > > > > > publishing with "publish all following pages", instead of site > > > > > > > section > > > > > > > - the whole site gets published. I thought there was something > > > > > > > wrong > > > > > > > with settings or i built the project improperly; therefore, I > > > > > > > tried to > > > > > > > publish a section in "Best Practice" project and got same results. > > > > > > > > Steps to replicate: > > > > > > > > Open "Best-Practice 10.1.0.1" project. > > > > > > > Navigate to page id 178 "Content Types" and publish English/HTML > > > > > > > with > > > > > > > "Publish all following pages" checked and "Publish related pages > > > > > > > " > > > > > > > unchecked. > > > > > > > > The objective is to publish "Content Types" section, which > > > > > > > includes 8 > > > > > > > pages. Instead, the CMS publishes the entire site. > > > > > > > > Note that link and page references not followed according to > > > > > > > project > > > > > > > settings. > > > > > > > > Case 2 > > > > > > > > Start page, which is not Master and set not to be published, > > > > > > > contains > > > > > > > dynamic link. Two master pages and a footer page are connected to > > > > > > > the > > > > > > > dynamic link. When publishing footer page (as server side > > > > > > > include), > > > > > > > the other two pages get published as well. > > > > > > > > Looks as a bug. I reported this issue to OT. Anyone experienced > > > > > > > the > > > > > > > same issue? > > > > > > > > Thank you -- 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.
