Hiding the Global Search
Up through version 2.0 of the HTML5 viewer I was able to hide the Global Search field by changing the "SearchView" id visibility from "true" to "false".
Starting with version 2.1 this change no longer hides the Global Search field. Is this a bug, or did something else change with regard to changing the visibility of the Global Search?
Here's an example from the Desktop.json.js file:
{
"moduleName" : "Search",
"moduleType" : "geocortex.essentialsHtmlViewer.mapping.modules.search.SearchModule",
"configuration" : {
"autoLoadSiteGeocoders" : true,
"searchProviders" : [ {
"type" : "geocortex.essentialsHtmlViewer.mapping.modules.search.LayerSearchProvider",
"enable" : true,
"configuration" : {
"exactMatch" : false
}
} ]
},
"views" : [ {
"id" : "SearchView",
"viewModelId" : "SearchViewModel",
"visible" : false, Changed this to "false" to hide the Global Search field
"title" : "@language-search-title",
"iconUri" : "Resources/Images/Icons/search.png",
"markup" : "Mapping/modules/Search/SearchView.html",
"type" : "geocortex.essentialsHtmlViewer.mapping.modules.search.SearchView",
"region" : "BannerContentRegion",
"configuration" : { }
}
-
Steve,
I don't have experience with earlier versions of the HTML5 viewer and have also been struggling with this in the current version. I ended up hiding the banner which I really didn't want to do. Thanks for your post and I hope this is a "bug" and will be fixed in the next release.
0 -
Thanks, Steven. I've confirmed that this is an issue in 2.1. In general, marking a view as non-visible should be respected. It seems like some other component is re-activating the SearchView. This issue is not present in the under-development 2.3, so it was either intentionally or un-intentionally fixed in 2.2.1 or 2.3.
Note that simply removing the SearchView entry from config will successfully remove the view from the UI.
0 -
Jason,
Thank you for looking into this and thank you for the hint. That worked!!
Bobby Jo
0
Please sign in to leave a comment.
Comments
3 comments