About jeffshurtliff

jeffshurtliff

This is a great article and had information that I definitely needed to hear (and absolutely need to put into practice) so thank you!

jeffshurtliff

Just to partially close the loop on this topic, while it still appears to be a platform bug, we (@MohitVerman and I) were able to come up with a feasible workaround that we are now currently implementing globally in our environment. We are updating all of our quilts that leverage the Search Form component (which is nearly all of them) to set the parameter hideGranularity=false rather than true, and then we're using CSS in our skin to hide the granularity filter in the components where we don't want it to display. So far our tests have shown that this has successfully scoped the search results to the node in question and--in the case of categories or group hubs--any sub-nodes.

jeffshurtliff

Thanks @SuzieH @and @StanGromer! I’m leaning toward it being a bug as well, because after seeing Stan’s post I decided to try toggling the value for hideGranularity (unhiding) it in one of my quilts for a TKB page and found that it caused the search bar to be scoped correctly. So I believe that the bug is that when the hideGranularity parameter is set to “true” it forces the defaultToCommunity parameter to also be true even if it is explicitly set when calling the component in the quilt. (I haven’t tried calling the component within a custom component using the @component directive but I assume it acts the same.)

jeffshurtliff

We are using the Search Form component on most of our nodes in our environment, but for some reason all of them are stuck using a community-level scope (searching the entire website) rather than limiting the scope to the category, board or group hub on which it resides, as expected her the documentation. I've also tried explicitly setting the defaultToCommunity parameter to false as shown below, but still get search results from the entire website on said nodes. <add to="search-bar"> <component id="common.widget.search-form" defaultToCommunity="false" hideGranularity="true"/> </add> Anybody experience this before and know what I should do? Because currently the search functionality on our nodes is pretty useless without a functional scope. Edit: Community version is 20.11-release r2012100721 and search feature version is 3.3.

jeffshurtliff · ‎12-08-2020

As we have a support community, we’ve needed to add several script extensions such as ps1, py and sh. In these situations, to reduce risk of any malfeasance, I would suggest using tanks to disable the ability for new users to upload file attachments to posts until they’ve both verified their email address and achieved a minimum rank. Hope this helps!

Online Status	Offline
Date Last Visited	8 hours ago

Re: I’m an “always-on” community manager. Here’s how I avoid burnout.

Re: Search scope stuck at community level on all nodes

Re: Search scope stuck at community level on all nodes

Search scope stuck at community level on all nodes

Re: .PS1 (Powershell scripts)

Khoros Events & Meetups: North America