Pages deleted from server during publish - navigation manager

[JoFo]

Hi,

I've read several similar posts, but nothing with an answer for
me...we're using navigation manager and reddot version 9.0.1.35. Pages
can be set by the user to not show in left hand menus, but still
publish. The problem is, RedDot seems to ignore the pages that don't
appear in the menu (even though they are physically on the
lst_navigation list in smart tree) and not only doesn't publish, but
also deletes from the server if they have been previously published
manually.

This only seems to be a problem when publishing using all following
pages. if the page itself is published it goes live with no problem.

If anyone has any insight into this, please let me know :)

[Sami Dubey]

Hi,

Publishing functionality of Reddot tool can only Publish the pages to its mapped server, it does not have any features which will delete the already existing page. The published page can be deleted manually from the server, it can never be done from Reddot even though you choose following or related pages.

Thanks
Sam

--
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.

[emily stange]

Do you also have the general property "Clean up Live Server" turned on?

-Emily

[JoFo]

Yes we are using 'clean up live server', which would explain the page
deletions, but the pages exist within reddot and need to be published.

On Feb 3, 3:55 pm, emily stange <esta...@gmail.com> wrote:
> Do you also have the general property "Clean up Live Server" turned on?
>
> -Emily
>

> On Thu, Feb 3, 2011 at 10:46 AM, Sami Dubey <sd77...@gmail.com> wrote:
> > Hi,
>
> > Publishing functionality of Reddot tool can only Publish the pages to its
> > mapped server, it does not have any features which will delete the already
> > existing page. The published page can be deleted manually from the server,
> > it can never be done from Reddot even though you choose following or related
> > pages.
>
> > Thanks
> > Sam
>

> > On Thu, Feb 3, 2011 at 8:36 PM, JoFo <noodlebo...@googlemail.com> wrote:
>
> >> Hi,
>
> >> I've read several similar posts, but nothing with an answer for
> >> me...we're using navigation manager and reddot version 9.0.1.35. Pages
> >> can be set by the user to not show in left hand menus, but still
> >> publish. The problem is, RedDot seems to ignore the pages that don't
> >> appear in the menu (even though they are physically on the
> >> lst_navigation list in smart tree) and not only doesn't publish, but
> >> also deletes from the server if they have been previously published
> >> manually.
>
> >> This only seems to be a problem when publishing using all following
> >> pages. if the page itself is published it goes live with no problem.
>
> >> If anyone has any insight into this, please let me know :)
>
> >> --
> >> 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<reddot-cms-users%2Bunsu...@googlegroups.com>
> >> .

> >> For more options, visit this group at
> >>http://groups.google.com/group/reddot-cms-users?hl=en.
>
> >  --
> > 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<reddot-cms-users%2Bunsu...@googlegroups.com>
> > .

[JoFo]

also, I've just discovered that publishing all following pages also
published pages UP the tree...odd!

[emily stange]

Yes, this is the reason they are being deleted. "Clean up Live server" has the tendency for it's database to get out of sync which causes pages to be deleted improperly. To fix this, you should:

- Turn off the property, save

- Turn the property back on, save 

- Enable always publish files and pages in publishing settings

- Clear publication cache

- Perform a full site publish

- Disable always publish files and pages in publishing settings

Also, when you choose to "publish all following pages", then the publishing engine will follow all links down the tree from that point. If there is a page connected (also by keywords) which has a main link higher in the tree, the publishing engine will go there and continue down. To prevent this jump, always reference pages when possible.

-Emily

To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.

[Jian Huang]

Regarding the "publishing all following pages also published pages UP
the tree" problem, like Emily said, if you have tree structure of

A -> B -> C-> D-> B

publishing all following from D also results in publishing of B, C, D
again, B again...don't worry, it stops after the 5th loop I heard.

Also, this could be lead to other problems. Say, publication package
under A tells B to publish to folder A, publication package under D
tells B to publish to folder D. Well, page B will get published to
both folder A and D. Google ranking and other SEO can consider this
as link spamming.

Further more, you have many other pages that are like B, connected in
multiple locations with multiple publication packages. Even the best
"clean up live server" list will get confused over time. I know I
will.

"My god, I have 1000+ pages on the site, and I need to fix it by
Monday!" You said.

I have just the plugin that will check all pages for you and all it
costs is a phone call to OpenText support asking for it.

"Well, you are wrong, I fixed all the aforementioned multiple
connections and the problem persist!" You said.

Well, I wouldn't be a successful forum troll without plan #2.

In your navigation code, do you use CurrentIndex.GetUrl() or
CurrentPage.GetUrl()?

CurrentIndex.GetUrl() generates links of referenced page type, which
page builder/publisher will NOT crawl.

CurrentPage.GetUrl() generates links of connected page type, which
page builder/publisher will crawl.

I would assume you are using CurrentPage.GetUrl(). When page B is
individually published, it is published. When page A is published
using all following pages option, then the following is considered by
page builder/publisher.

Page B is connected to page A via lst_navigation, but it is never
rendered in navigation, hence there is no way to get to the page via
links from other pages, so the page shouldn't exist on the web
server. What? It is on the web server? DELETE!

If you are using CurrentIndex.GetUrl(), I hope you have included <!--<!
IoRangeList><%lst_Navigation%><!/IoRangeList>--> in your foundation
template, else same problem.

On Feb 3, 11:54 am, emily stange <esta...@gmail.com> wrote:
> Yes, this is the reason they are being deleted. "Clean up Live server" has
> the tendency for it's database to get out of sync which causes pages to be
> deleted improperly. To fix this, you should:
>
> - Turn off the property, save
> - Turn the property back on, save
> - Enable always publish files and pages in publishing settings
> - Clear publication cache
> - Perform a full site publish
> - Disable always publish files and pages in publishing settings
>
> Also, when you choose to "publish all following pages", then the publishing
> engine will follow all links down the tree from that point. If there is a
> page connected (also by keywords) which has a main link higher in the tree,
> the publishing engine will go there and continue down. To prevent this jump,
> always reference pages when possible.
>
> -Emily
>

> > <reddot-cms-users%2Bunsu...@googlegroups.com<reddot-cms-users%252Buns...@googlegroups.com>

>
> > > >> .
> > > >> For more options, visit this group at
> > > >>http://groups.google.com/group/reddot-cms-users?hl=en.
>
> > > >  --
> > > > 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<reddot-cms-users%2Bunsu...@googlegroups.com>

> > <reddot-cms-users%2Bunsu...@googlegroups.com<reddot-cms-users%252Buns...@googlegroups.com>

[mreddot]

One more point:

you said, users are able to set pages not to show in left hand
navigation. Dependent one your template implementation, maybe the
publisher is not able to track the linking to the 'invisible' page. In
this case the publisher does not publish this page AND the cleanup-job
expects that this page is not available any longer -> deletion on the
Liveserver.

[JoFo]

Excellent, thanks all for your help! I'll have a look at our settings
and see what's going on there.

RE: last comment, this was my suspicion, so I've added some code to
compensate and it seems to now publish 'hidden' pages.

> > If anyone has any insight into this, please let me know :)- Hide quoted text -
>
> - Show quoted text -

[JoFo]

ok, so I've added the Bool:True to the GetUrl() code in the navigation
manager templates...this doesn't seem to have changed anything, the
publishing is still extremely slow and it is still publishing up the
tree.

I'm wondering about the 'clear page builder cache before publication'
setting. I've heard that this drastically slows publication, but would
it be worth doing one publish with this checked to sort it out and
then revert back to publishing with it unchecked? I've cleared
navigation cache and page cache but doesn't seem to make a difference.

Thanks

[Jian Huang]

Hi Jo,

Not sure if you have had a chance to read my reply above. Have you
tried to implement all the following fixes:

- use CurrentIndex.GetUrl() in navigation template code
- add <!--<!IoRangeList><%lst_Navigation%><!/IoRangeList>--> or
similar to all your foundation pages?
- ensure a page is not connected in multiple locations, especially
somewhere down its own tree.

[JoFo]

Hi,

Thanks for the info :) I am using CurrentIndex rather than CUrrentPage
in nav template code...and have put the lst_navigation commented in
the html. As for pages in multiple locations....I've done some
checking, but not been through the whole site (there are a LOT of
pages) and most pages are referenced rather than connected in multiple
places.

HOWEVER when the site was migrated (also new content classes, styles
etc) over to navigation manager there was a lot of disconnecting and
re-connecting of pages. Whether this has had an impact on the
publishing I'm not sure.

Thanks

[Jian Huang]

Hi Jo,

Please find below the link to a plugin that will check multiple page
connections for you

http://www.qfpost.com/download.do?get=31a2e25e6a0de1f3e3dd6fd940ff318d

To install, just drop content in zip (including the folder inside zip)
to plugins folder, import plugin, activate and assign plugin in server
manger.

In your project, smarttree, select a foundation content class, and
click on the plugin check in action menu

The plugin will automatically go through all page instances of that
content class and list pages are that connected to multiple
locations. If you click on the result, it will take you to that page
in SmartTree.

Best regards,

-Jian

[JoFo]

Reading the publishing log file, it looks like the publisher is
following the navigation on the page...I've added Bool:True to the
geturl code and it still seems to be the same.

Also we do have a lot of keyworded lists which would publish as
following pages.

[Jian Huang]

Hi Jo,

Thanks for update.

If you are using CurrentIndex.GetUrl(), you don't need the Bool:True
parameter.

Assuming you have ran the plugin and have identified all pages with
multiple connections.

1. Regarding keyworded lists, please use shadow list method mentioned
in this thread
http://groups.google.com/group/reddot-cms-users/browse_thread/thread/566342261811bb53/e04a171bdd58ccd1#e04a171bdd58ccd1

2. Regarding navigation pages connected to multiple lists, please
create a content class that does redirects either using javascript or
meta refresh. Instead of connecting a navigation page in multiple
locations, navigation page should live in 1 location, and use redirect
pages at other locations to redirect. SEO? Use robot no in the
<head> of the redirect page.

3. If you have news/events article pages as master pages, hence they
appear in navigation manager structure, then you might want to see if
you can turn that content class back into just a regular content
class. Rule of thumb for navigation manager, if the page do not show
up in navigation, it should not be a navigation page. Imagine if I am
a news website and I have 10000+ articles...

Please keep us updated on your progress. Thanks,

-Jian