Same problem as another person who posted on the list today. You have multiple filter expressions and jackrabbit 1.3 only executes the first one. It's a limitation of Jackrabbit and I think it was fixed in newer versions of Jackrabbit. Unfortunately I haven't tried it myself in 1.4 or 1.5 to know if either have fixed the problem.
--David Bubenik, Wolf wrote: > Hallo, > > We have pages with a boolean page property that should control whether > this page may be found by the search. > > 1) How to write a query string that excludes pages with certain NodeData > values? > I tried > SELECT * FROM mgnl:contentNode WHERE CONTAINS(*, 'something') AND NOT > CONTAINS(hideInNav, 'true') AND jcr:path LIKE '/content/%' ORDER BY > jcr:score DESC > but the page is still in the result set (using JCR query tool in admin > central). > > I tried the XPATH analog > /jcr:root/content[1]//element(*, mgnl:contentNode)[jcr:contains(., > 'something') and not(jcr:contains(@hideInNav, 'true'))] order by > @jcr:score descending > with the same result. At least this is fine :-) > > > 2) Can I exclude some paragraphs from beeing searched? How would such a > query string look like? Is there a better solution than providing (a > long) white list of node names to search in? > > We are using Magnolia 3.5.8 with Jackrabbit 1.3.3. > > Thanks a lot > > Wolf > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
