"No results" portal search not returning results after Zurich upgrade for non-admin users<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Users may have noticed that following the Zurich upgrade, in custom portals, or legacy portals where Zing Search (and not AI Search) is being used, that non-admin users are facing "No Results" when attempting to search for anything in the portal. It usually looks like this: Reason: This is observed because the "Search Nav" widget, which is used in the legacy 'search' page, was updated in the Zurich release. In the server script calls to the "GlideRecord" API were replaced with "GlideRecordSecure" which requires a user pass the ACL check. The "GlideRecordSecure" change was introduced as part of the fix for the related defect PRB1895962, which was allowing users to bypass ACL checks for certain tables, such as for the portal search sources. Therefore, as a result of this, the non-admin users may be failing ACLs which prevents them from viewing the search results on this page. Solution: If you wish to continue using the legacy 'search' page and the 'Search nav' widget, you can choose to identify which ACLs the users are now failing, and amend the Access Control configuration in your instance accordingly. Alternatively, we suggest instead to configure and use a page route map (or Activate and utilise the OOTB page route map: /sp_page_route_map.do?sys_id=3821492587001300a785940307cb0bef) to re-route from the 'search' page, to the newer 'sp_search' page, which uses the new and recommended "Faceted Search" widget, with which the users will not have the same issue: