Hi Kim, Thanks for all the info.
You mentioned that the pages even show up in the publication report, just not in the server. That means page builder did assemble the pages. I was going to say what Tim D said, is the link to those pages visible to the page builder so it can crawl to following pages, but the publishing report confirmed that it can crawl to following pages. Following pages is usually enough for publishing. Checked related pages if you are using "clean up live server" feature, which you are not, so this isn't the problem. Crazy idea here: Create a new publishing target using local path, create new publication package to use the new publishing target, attach the new publication package to Section 1 page, and the list connecting following pages. Publish. I want to see where it is failing: page builder, FTP/local transfer mechanism, targeted server? On Jan 11, 7:35 pm, kimdezen <[email protected]> wrote: > just on a side note Christoph - problem still occurs regardless if i > select just the forward and or forward and related publishing > options.. > > On Jan 12, 5:53 am, Christoph Straßer <[email protected]> > wrote: > > > > > > > > > Im a bit surprised to read this message from one of the reddot/OTWSM- > > pro´s. :-) > > > Think it makes sense to cross-check to 3 log files on the server which > > are written per publishing job and project variante / language > > variant. There´s one log written by the generator / page builder. > > (This one should show whether OTWSM generated a page during publishing > > and wheter it changed since it´s last publication.) You also should > > find a log from the transfer-job (_FTP) and one from the Cleaner-Job. > > After looking to all three of them it should be realtiv clear what > > happens. > > > We didn´t run into this problem in our projects with 10.X. Have 3 > > projects between 20.000 and 50.000 masterpages and some smaller ones. > > I personally know this problem in situations where the generator is > > not able to detect a link to a subpage. In this situations it helps to > > put the anchor or list (additional) inside a HTML-comment. (If you > > have this type of problem the page does not show up in die log written > > by the generator / page builder). > > > As far as a I know there are situations where it´s not good to > > activate both publishing - options ('forward' and 'related pages') at > > once. (Depends on your project.) It may be better to only activate the > > forward-option. In our big projects there is a publishing job which > > runs each night and starts with the root-page an publishes als pages > > with activated forward-option. > > > Kind reagards, > > > Christoph > > > On 11 Jan., 16:52, Tim D <[email protected]> wrote: > > > > They are connected to the same list but is there a list blockmark and list > > > element in your template? > > > > Curious if you are using Rendertags and navigation manager and therefore > > > left out that in the template? > > > > For page builder It is more reliable to add the list block mark and > > > placeholder even if not displayed. > > > > <!-- > > > <%imaginethesearelistblockmarks%><%lst_yourList%><%/imaginethesearelistblockmarks%> > > > --> > > > > If this is the case then please report an issue with nav manager code not > > > finding all following pages but this should get it working. > > > > Also is there any pre-execution or rendertags in the list blockmarks? -- 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.
