Sometimes one ends up wondering why the Solr search returns the documents that it does. Or maybe the order of the items is a bit confusing. The problem for a developer is mostly not to understand it but to be able to explain it to the editors that oftenly do not have the technical background that we do. Continue reading Solr boosting and scoring in short
You might find this useful if you don’t already know about it. I ran into a problem the other day where the tagging section did not work properly. No tags at all were displayed for selection, I suspected that there was something wrong with the search in the field. You can find all the info you need to debug this and just copy + paste in the search log and your favorite index viewer. Continue reading A tip on debugging Sitecore search
Many of today’s Sitecore implementations contain lots and lots of items. In many cases the items are stored in buckets and the editors are therefore totally dependent on finding what they are looking for by using the search functionality in Sitecore. When entering the search in Experience Editor the editors may become a bit overwhelmed with information since the default is to search for everything. Normally the editor could start filtering and then search for whatever is needed. Continue reading Customize default search in Sitecore experience editor
In the official documentation you can read that Sitecore will choose index based on the RootPath in the crawler and based on the placing in the web.config.
Basically if you create an index that indexes everything under /sitecore/content/home/products you will need to get that index defined before for example the master index in the web.config otherwise your new index will not be considered at all. But what does actually happen here? Continue reading How does Sitecore ContentSearch determine which index to use