On Mon, 2006-08-14 at 09:31 -0400, Doug Chestnut wrote:
> I get the same error "No node contained for path ...".
> 
> It seems to be caused by the publish usecases doCheckPreconditions() 
> method called when the authoring menus are created.
> 
> SiteStructure structure = siteManager.getSiteStructure(getDocumentFactory(),
>                          publication,
>                          Publication.LIVE_AREA);
> 
> structure is null for some reason.

See the next line in Publish.java:

SiteNode liveNode = structure.getNode(path);

The structure is not null, but it throws an exception because the index
document has not been published yet and therefore the /index node
doesn't exist in the live sitetree.

Not sure how to fix this, though...

Josias

> Sorry, I haven't had time to look further.
> 
> --Doug
> 
> Joern Nettingsmeier wrote:
> > Joern Nettingsmeier wrote:
> > 
> >>Andreas Hartmann wrote:
> >>
> >>>Joern Nettingsmeier wrote:
> >>>
> >>>[...]
> >>>
> >>>
> >>>>>>when i access http://localhost:8888/default/authoring/index.html, i get
> >>>>>>
> >>>>>>   No node contained for path [/index]!
> >>>>>
> >>>>>Is this with the old or with the migrated (UUID-based) content?
> >>>>>I can't reproduce it with the migrated content ...
> >>>>
> >>>>migrated content. but i forgot to mention that i have my custom
> >>>>publication content outside the build tree, but the default pub is
> >>>>unchanged. the problem occurs on both.
> >>>>
> >>>>the migration target works without problems, though.
> >>>
> >>>Strange, I still can't reproduce it.
> >>>
> >>>- ./build.sh clean
> >>>- ./build.sh
> >>>- outsourced content
> >>>- ./build.sh module.test -Dmodule=org.apache.lenya.modules.migration
> >>>- ./lenya.sh servlet
> >>>
> >>>The homepage appears as expected ...
> >>
> >>funny. i'll try to reproduce it with a clean checkout. maybe it's a
> >>subtle java 1.5 issue? i have had to upgrade my workstations at home and
> >>at work.
> > 
> > 
> > i have done a vanilla checkout again. the build went ok, the migration
> > went ok, same error. this time, i used the most conservative
> > local.build.properties: no custom modules or pubs, modules.copy=true.
> > 
> > what happens if you do a fresh co?
> > 
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to