just edit $possibleNodes to select the nodes u want to search.

/J

Edit what to what? I tried changing (umbracoNaviHide) != '1' to '0' - but that didn't seem to work..

Could give me a hint ? :)

    
    <xsl:variable name="possibleNodes" select="$items/descendant-or-self::*[
                             @isDoc
                             and string(umbracoNaviHide) != '1'
                             and count(attribute::id)=1 
                             and (umbraco.library:IsProtected(@id, @path) = false()
                              or umbraco.library:HasAccess(@id, @path) = true())
                           ]"/>

Should I just remove the line "and string(umbracoNaviHide) != '1' "?

Hi, Djan,

There should be no need to modify the possibleNodes variable.

XSLTsearch specifically does NOT return pages that are hidden (using the 'umbracoNaviHide' alias set to true), nor any pages that the currently logged in member does not have permissions to view. This has always been the behavior of XSLTsearch and the code snippet you showed for the possibleNodes variable indicates exactly this.

It is a more advanced handling than the default xslt menu and sitemap macros but they share the @isDoc and string(umbracoNaviHide) != '1' code, which is the important part based on your description.

Can you double-check that the page(s) you wish to hide from the search have the umbracoNaviHide document type alias (it is case-sensitive) and that the page has the true/false checkbox selected? The page should not now appear in the navigation, the sitemap, nor the search results. You might temporarily add the umbracoNaviHide property to a top-level page of your site that appears on your main navigation to to make testing more obvious if you have a large site.

Let us know what you find out.

cheers,
doug. 

is working on a reply...