first of all I am not familiar with javascript but I saw the easy way azure search generator offers a portal with search features and I used it to make a search portal for more than 100K files. Everything is fine except that I'm facing the same issue of the limit of 5 facets mentionned in this old post (Facet count in Azure cognitive search (Automagic)). Using search explorer I can see the request url needed (example : facet=category,count:10 / https://xxxxxsearch.search.windows.net/indexes/azureblob-index/docs?api-version=2020-06-30-Preview&search=*&facet=category%2Ccount%3A10) but can't figure out where to put this in search app hmtl page or how I can parse it to automagic to consider this.
thank you Gaurav for your feedback. no, that part is clear for me. Please let me show an example of what I want to achieve.I generated a search a portal using AzSearchGenerator and for this sample I have 7 files with the same metadata key but with 7 differents values (blob-content-files). I am seeking a way to override the limit of 5 checkboxfacets in the search portal generated (check here : portal-search-generated). Is there a way to change this by including the request url with count parameter higher than 5 checkboxes (storage-explorer-request ) to update the automagic instance in the html code (automagic-intialization-html).
Could you please advice me how I can complete this.
If I understand correctly, you're looking for a way to specify facet parameter in Search Explorer in Azure Portal.
Simply add &facet=category,count:10 in the Query string field and that should do the trick. For example, see the screenshot below.
I finally found which parameter to update. In the AzSearch.bundle.js referenced in in the html page (see printscreen parameter to change), the default value is at line 44 on the checkboxfacet part. I just updated it with the right value, in my case I put count:30 and now I have more than 5 items in the checkboxes.
Result after change
Related
I'm having a problem that just randomly occured, and I have no idea what caused this and how to fix it.
So I have a searchbox that is supposed to use my search settings. Here are my current search settings:
Settings
Settings 2
My problem is that even though I configure my searchbox to use this sites' search settings, it ignores it. Instead of using /results.aspx?u={searchboxQuery} as specified in the settings, it uses /results.aspx?k={searchboxQuery}
I'm also using a custom Result Source:
{searchboxQuery} Path:https://mypage/Pages
The searchbox works if you provide exact matches, but if you try to shorten a word, no result is displayed. The result query itself works correctly, displaying all the correct pages, but not with search queries.
Any help would be highly appreciated, it's quite an annoying problem
I remember running into this a while back. I ended up using a Search Results template from the Pages library (Publishing needs to be turned on. Trying to create the connections myself was too much of a headache.
I want to define a new template called "product".
This template calls an external service and retrieves the information about that specific product. That is easily done with a custom plugin that access the product information. Information on how to do that has been found here.
However, I would like that the URL of the page would be something like:
/product/<id>/<seo-friendly-description>
So I can retrieve in the Twig template both <id> and <seo-friendly-description> which will be used later to retrieve the specific product information.
I have tried to find something that could help in the documentation, without success. Could someone either point me to the right doc section or highlight the basic steps that shall be achieved so I can start solving this issue?
Just in case it helps, I am trying to find something similar to how bottle or other web frameworks work:
#route('/hello/<name>')
def greet(name):
return 'Hello ' + name
I've been building a family recipebook into my own website and I've been working through a similar problem. I haven't quite worked out all the kinks, but my solution is mostly working if you want to checkout my github repo.
In short, you need the plugin to watch what the active route is. If the route matches, you then create the page and populate it using your plugin data.
I haven't quite figured out how to get the active page to highlight in the navigation menu for generated pages, but you might still find this solution helpful.
How can i localize the drop down option for the search mode? I did some digging and was able to adjust the localization for the search form labels but i'm at loss here.
The CMS Module SearchDialog.ascx call the drop down list here, but i can't see where the values come from.
<cms:CMSDropDownList runat="server" ID="drpSearchMode" CssClass="DropDownField" />
Go to the localization App and create resource strings for
"srch.dialog.AllWords"
"srch.dialog.AnyWord"
"srch.dialog.anywordorsynonyms"
"srch.dialog.ExactPhrase"
Believe those are the 4 you need.
I couldn't find official documentation that helps much with this, though there have been articles in the past on older versions. However, one trick I've used previously is to look in the ~/CMSResources/cms.resx file, find the localized string there, and add a new one with the same key to the Localization module in Kentico. That is, add a new resource string in Kentico with the same key (the naming will be different depending on your version of Kentico).
Here's the docs discussing setting up a multilingual interface: https://docs.kentico.com/display/K9/Setting+up+a+multilingual+user+interface
And here's a screenshot of the resx file:
So in your case I'd create a new resource string within Kentico called "srch.dialog.allwords" as an example and that should overwrite and take priority over whatever is in the .resx file, plus you can manage it via the Kentico admin. There may be a quicker or more reliable way to view the list of default resource strings but in my recent installs of Kentico, the list is hidden from the admin interface.
Alternatively, of course, you could manage the resource strings via various .resx files as in the documentation, but I try to manage as much of these pieces via Kentico as possible for convenience.
I have custom web part registered in Kentico web page and I would like to use Kentico smart search to search information from web part.
My custom web part contains grid view with following columns
Item Code
Item Name
Item Price
Mfg. Date
If user is going to enter "Laptops" in search box then system should search information based on Item Name.
Can anyone give me brief idea about Kentico smart search which satisfy above functionality?
Have you tried using the smart search index and set it to be the document crawler? In this case the crawler will index the HTML output of the pages - including the output of the web part.
I think you have a fundamental misunderstanding of how smart search operates.
Basically you'll use Smart search to index your database.
You can then use Kentico's Smart search API to filter a dataset to be used to bind into a repeater or datalist of some type.
The only thing I can suggest is consulting the Kentico documentation for your version of Kentico, specifically looking for smart search. If you included more information such as the Kentico version and the source of your data (documents, custom tables, etc) then someone may be able to give a clearer answer.
I have a slight problem I have been trying to address for a client I have been working with. We have 4 sets of single pages that are loading content from a database using PHP based upon a get string that is provided. These pages that are generated are optimized well for SEO and have alt tags for images and Content that we need to be able to search using a search feature.
Now i had assumed (An everyone knows what assuming gets you) that these pages by default would be able to be searched by the concrete 5 built in search feature. But it doesn't work. If I search for a word that I know is definitely on one of these pages even multiple times no results are found.
How can I make Concrete5 search these pages. If its no do able by a default or by a plugin, then can someone please offer some advice on how to fix this. This is an important feature and must be completed.
EDIT: See my comment below. I still need some help or direction here as CSE inst much of an option.
EDIT2: It may be viable for me to install a crawler and a custom search engine to address my problems. I was thinking of spider. Any other suggestions on that or other options are much appreciated!
Unfortunately C5 doesn't provide a way to do this -- the only way to tap into the search index is with blocks. And even if you created a phony block just to pass content from the single_page through to the search index, there's no way to say that some content is from one URL while other content is from another URL (which you'd need to do since your single_page controller is handling many different URL's).
I don't know of a way to achieve what you want to do (and it appears that nobody else does either -- http://www.concrete5.org/community/forums/customizing_c5/make-content-in-single-pages-searchable/ ), other than building your own internal search engine.
EDIT: I just did some digging, and thought that perhaps you could manually insert records into the PageSearchIndex table and specify the searchable content and the desired path there -- but this won't work because it relies on one cID (collection id, a.k.a. page id) per entry -- so you'd only be able to insert one record for the top-level single_page path.
I think the simplest solution here would be to create your own searching infrastructure for your single_pages (like some kind of function in the controller that would return an array of page paths and searchable content for each one), then override the search block and perform an additional search of your single_page -- then combine the results on the search results page there. Or just use google site search for your site, which will actually crawl the pages and hence find your various single_page urls: https://www.google.com/cse/
Best of luck.
I have not tested this, but maybe you can put a function getSearchableContent() in the single pages controller like you do for blocks. This would return the string to be searched. Would look something like this:
function getSearchableContent() {
// ... compose searchstring depending on the queried content.
return $searchstring;
}
But I don't know if this works for dynamic content. If not, I'd look into C5's search index core classes and try to extend them for your project.