Not all pages publishing

[kimdezen]

Hi All,

Just wondering if anyone has had this problem before..

A large project that im maintaining (with over 20,000 foundation
pages) has some pages in the project that arent being republished
whenever i try to republish an entire site section (by selecting the
'forward' and 'related pages' option)

E.g.

Section 1
- page 1
- page 2
- page 3
- page 4
- page 5
- page 6

If i publish the 'Section 1' page - with both forward and related
pages options, some of the child pages underneath it wont publish (say
page 2 and page 5), even though they are using the same templates,
same target containers, same publication packages, same workflow - and
are connected up to the same list. These pages are even listed in the
publishing log - nor do they throw and publishing errors.

All pages are released. There are also no appearance schedules on
these pages, there is only one main link on these pages as well..

Ive tried clearing all caches (publishing cache included) to no
avail..

The only way to fix is to republish any of the pages that didnt
publish manually.

Using v10.1

Thanks in advance
Kim

[Tony Gayter]

I get that on two of our projects, its really annoying. Luckily they are pages which dont often change but there is another section which has thousands of pages which does teh same!. Ive asked reddot but they couldnt resolve it (mainly as teh project is so intertwined with .net and I dont have the time to write a deployment plan for them to set it up correctly)

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

[Richard Hauer (5 Limes)]

Perhaps it's a problem in the final transfer and not in PageBuilder?
Are the temp files produced properly? If the page is logged then it
was definitely eligible for publication and was queued correctly. Only
an error in the build (which should be reported in the log) or an
error in the delivery would stop it. Or maybe the "clean up live
server" is deleting it again for some reason. I've never been able to
fully understand that bit of kit.

Richard.

On Jan 11, 8:46 pm, Tony Gayter <tonygay...@gmail.com> wrote:
> I get that on two of our projects, its really annoying. Luckily they are
> pages which dont often change but there is another section which has
> thousands of pages which does teh same!. Ive asked reddot but they couldnt
> resolve it (mainly as teh project is so intertwined with .net and I dont
> have the time to write a deployment plan for them to set it up correctly)
>

[Tim D]

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?

[Christoph Straßer]

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 <timothy.j.da...@gmail.com> 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%><%/imaginethesearelistbloc­kmarks%> -->

[kimdezen]

Hi Guys

Thanks for the input so far..

The cleanup liveserver option isnt used in this project
Navigation Manager or Render Tags arent being used also - this is a
really old project running under v10.1 using the list through
container method and target containers.

The lists have been set up correctly - there is certainly no issue
with the logic inside the templates as far as i can see. If there was,
i would expect no pages to publish - or perhaps just the first or last
pages in the list.

I will dive deeper into the logs on the server to see what the problem
is, but what is really confusing is that all pages connected up under
the list (as described intially) are using the exact same templates,
all linked in the same way..

Cheers,
Kim





On Jan 12, 5:53 am, Christoph Straßer <christoph.strasse...@gmail.com>
wrote:

[kimdezen]

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 <christoph.strasse...@gmail.com>
wrote:

[Jian Huang]

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?

[kimdezen]

Whoops my mistake..

That should have read - 'they dont even appear in the log'
So unfortunately no, they are not listed in the publishing report

Sorry about that!

[Christoph Straßer]

Try to add something like this to your template:

<!IoRangeNoRedDotMode>
<!--
wird benötigt, damit RedDot alle Seiten publiziert / is needed that
all pages get published
<!IoRangeList><%lis_nav_Main%><br><!/IoRangeList>
-->
<!/IoRangeNoRedDotMode>

[kimdezen]

Hi Christoph

Already tried that one ;)

Cheers,
Kim

On Jan 12, 6:16 pm, Christoph Straßer <christoph.strasse...@gmail.com>
wrote:

[Jian Huang]

Kim! Just remembered something

When using the old list container navigation method, ensure con_nav is visible within foundation content class, it can be using HTML comments or something, but the code must be visible.

Ran into same problem 3 years ago.

Sent from my iPhone

[kimdezen]

Thanks Jian..

I can confirm that the navigation container is in the HTML source (the
pages are all using the same foundation content class as well) - still
no luck

On Jan 13, 3:21 pm, Jian Huang <jhuangsoftw...@gmail.com> wrote:
> Kim!  Just remembered something
>
> When using the old list container navigation method, ensure con_nav is visible within foundation content class, it can be using HTML comments or something, but the code must be visible.
>
> Ran into same problem 3 years ago.
>
> Sent from my iPhone
>