[daisy] Error in a sitemap query

[Cunningham, Reginald - BLS]

The navigation tree some how became associated with the wrong
collection. Hence the error message we mentioned below. The fix was to
point it to the correct collection. Your email was the evidence that
solved the crime. Thanks a bunch!!!

*~*~*~*~*~*~*~*~*
Reginald Cunningham
Division of Data Dissemination Systems (DDDS): Procedures Branch
Room 5110 (QCT Room)
e-mail: cunningham.reginald at bls.gov
(202) 691-7354 
*~*~*~*~*~*~*~*~*

-----Original Message-----
From: daisy-bounces at lists.cocoondev.org
[mailto:daisy-bounces at lists.cocoondev.org] On Behalf Of Bruno Dumon
Sent: Monday, July 10, 2006 2:07 PM
To: Daisy: open source CMS - general mailinglist
Subject: RE: [daisy] Error in a sitemap query

On Mon, 2006-07-10 at 10:21 -0400, Thomas, Mark - BLS CTR wrote:
> Bruno Dumon wrote:
> > On Fri, 2006-07-07 at 13:34 -0400, Thomas, Mark - BLS CTR wrote:
> > > I have a query in a navigation document that lists recently
changed 
> > > documents. The section in the nav is:
> > >  
> > >  <d:group label="Latest Modifications">
> > >   <d:query q="select name where true order by lastModified 
> > desc limit 
> > > 20" filterVariants="false" />  </d:group>
> > >  
> > > This used to work, but now it is throwing an error when we click
on 
> > > the "folder". I've appended the error below. This is only a 
> > problem in 
> > > the current navigation document; the same query in a different nav

> > > document is working perfectly. What could explain this? 
> > Could there be 
> > > something elsewhere in the document causing problems? We 
> > only use the 
> > > nav editor to make changes.
> > 
> > Usually you should only get this error if the group node 
> > doesn't contain any children (e.g. query doesn't return any 
> > results for the current user), however then the group node 
> > wouldn't be displayed in the first place (there are of course 
> > edge conditions like all documents below the group node being 
> > deleted between the time you requested the page and click on 
> > the group node).
> 
> The query tests OK, and works in other nav documents.

When testing the query, take into account that a condition is
automatically added to filter on the collections associated with the
navigation document, as also explained in:
http://cocoondev.org/daisydocs-1_5/301/303.html

> 
> > BTW, what Daisy version is this? Is this maybe in combination 
> > with an import node?
> 
> Version 1.4, and no, we're not using any import nodes.
> 
> I tried reverting to a much earlier version of the navigation
document,
> but still get the "Path not found: g2" error. Since this query was
> working fine in the navigation at the time, I have to conclude that
the
> problem is external to the nav document itself.
> 
> Can you suggest any additional troubleshooting steps?

Maybe you could try to disable the contextualized tree, and see if you
then see the query results below the group node.

I also assume there isn't a node in the navigation tree which has the ID
'g2' assigned manually?

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno at outerthought.org                          bruno at apache.org

_______________________________________________
daisy community mailing list
Professional Daisy support:
http://outerthought.org/site/services/daisy/daisysupport.html
mail to: daisy at lists.cocoondev.org
list information: http://lists.cocoondev.org/mailman/listinfo/daisy