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.
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
My first thought would be -as Michael mentioned- the processSearchItems pipeline as that enables you to add data to an object in the SearchItem result list. Problem with this pipeline though (maybe an idea for the SXA team to change this in the future as this question does pop up often) is that you don't have access to the solr results (as far as I know).
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 ...
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, ...
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 ...
The official documentation states that this is broken.
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, ...
The configs you are asking here are related to Sitecore Social Connected module, for version 7.5 and previous it came as a separate module which you need to install but for Sitecore 8.0 to 8.2 it comes as part of Sitecore installation. But from Sitecore 9.0 and later Social Connected is not available and is not included in Sitecore.
See the release notes of ...
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
In Sitecore 9.3, it is subjected to add the below lines to make indexAllFields true under
<documentOptions type="Sitecore.ContentSearch.SolrProvider.SolrDocumentBuilderOptions, Sitecore.ContentSearch.SolrProvider"><IndexAllFields>true</IndexAllFields</documentOptions>
Your error might happen due to an invalid config file as some default fields were removed. After comparing your config to the Sitecore.ContentSearch.Solr.DefaultIndexConfiguration.config from 9.3 sitecore vanilla it seems that there are quite a lot of differences in the sections <fields hint="raw:AddComputedIndexField">(removing for example ...
What I understood is: you want to use an existing Solr Service (url), as you are installing Sitecore offline using SIA.
To achieve this do the following:
First make sure the solr service you created is running and the solr instance is accessible through the url. The default url would be https://localhost:8983/solr.
Now, from SIA, skip the "Install ...
You must have missed something in your configuration in solr.config file either on master or on slave server.
Here is a sample configuration for <requestHandler section for master server:
<requestHandler name="/replication" class="solr.ReplicationHandler">