Item2411: NOSEARCHALL not intuitive
Current State: Closed
Released In: 1.0.8, 1.1.0
Target Release: patch
Applies To: Engine
For new webs, the NOSEARCHALL parameter defaults to "on". The new user might change to "off" to disable the parameter, however the web still does not appear in the list.
It is not documented what to do to disable the setting. It turns out that setting this to anything other than "null", or commenting it out, results in the web not appearing is search. In addition, this impacts the WEBLIST
macro and SiteMap
- Should NOSEARCHALL be examined for "off" / "false" / or other negative values to include the web in searches
- Or should Docs be changed to clarify that the parameter should be unset or removed to include the web?
In addtion, ManagingWebs
UI is backwards for creating a new web. "Include in global search" set to include - results in NOSEARCHALL = on. Set to exclude results in NOSEARCHALL = Giving the exact opposite results from what was desired.
Fixed UI and clarified the ManagingWebs
topic. Any changes to behavior would be dangerous for existing sites.