Hot answers tagged

3

Some clarification of the comment here: Search result boosting works in Solr version 6.6 or earlier, but Solr changed the implementation in Solr 7, and later versions. Therefore, search result boosting is broken in Sitecore 9.1, 9.2, and 9.3. In SItecore 10, and later, item-level boosting works again, but field-level boosting does not. Sitecore stores the ...


2

The solr-init data initialization container script is failing while performing a request to get the list of collections from the Solr service: $solrCollections = (Invoke-RestMethod -Uri "$SolrEndpoint/admin/collections?action=LIST&omitHeader=true" -Method Get -Credential (Get-SolrCredential)).collections You are getting a 401 HTTP status code, ...


2

The official documentation states that this is broken. https://doc.sitecore.com/developers/90/platform-administration-and-architecture/en/search-result-boosting.html Search result boosting works in Solr version 6.6 or earlier, but Solr changed the implementation in Solr 7, and later versions. Therefore, search result boosting is broken in Sitecore 9.1, 9.2, ...


2

By "Social Module", I assume you mean Sitecore Social Connected? In which case the answer is simple. You cannot. Social Connected only supports Sitecore up to and including version 7.5. Reference: Sitecore modules compatibility table for Sitecore XP


2

The simplest code would be like that: var crawler = Sitecore.ContentSearch.ContentSearchManager.GetIndex(indexName).Crawlers.First() as SitecoreItemCrawler; string rootString = crawler.Root; Item rootItem = crawler.RootItem; It assumes that there is one crawler defined only. You should add some null checks, but I skipped them for clarity.


1

That's not really an issue. Attributes of html tags are ignored. If you have a content of rich text like: <div class="red-border" style="font-family: arial">Some text here</div> You don't want the content of field in Solr to be "div class red-border style font-family arial Some text here div" Your content is "...


1

What we ended up doing is removing the username and password and just using the API keys. It worked after that.


1

I have seen a similar problem in the past with new computed fields disappearing from indexes on publish. It was caused by multiple Sitecore instances with different code version connected to the same database and Solr server. One of the differences between the full index rebuild (or re-index tree) and on-publish indexing is the fact that the full index ...


Only top voted, non community-wiki answers of a minimum length are eligible