Description Unfortunately due to a limitation of the version of ElasticSearch that we use for Find/Search and Navigation we do not have the ability to use the "explain" parameter referenced in the following document to get an exact weight value for term frequency, inverse document frequency, and field-length norm. There are internal discussions around getting this feature available in future releases to make calculating the weight more accessible to customers, but for the time being custome...

Description The "Active" flag for the Episerver Find Content Indexing job will become inactive if turned on in Integration and Preproduction DxP environments. This happens automatically without anyone manually setting the flag.  Reason Unfortunately the indexing job creates a large load on the Episerver Search backend which can result in slow or even broken search functionality. So the flag is intentionally set to inactive for all DxP Integration and Preproduction sites using a runbook....

Description In some cases Search and Navigation will relay 429(Too Many Requests) exceptions. This occurs when the QPS limit of an index is exceeded. The purpose is to prevent too many requests on the search backend which would adversely affect search availability. See the below answers to frequently asked questions on 429 exceptions.  FAQ What was the reason for the QPS limit? To prevent an excessive number of requests to the search backend. Doing this helps prevent load issues which in...

Description In Episerver Find all media and page types are indexed by default. Here is how to remove certain page and file types from future indexing. Steps To remove a page or media type from indexing convention code can be added.  e.g.  ContentIndexer.Instance.Conventions .ForInstancesOf<Type>() .ShouldIndex(x => false);  Replace <Type> with the type being avoided.  Ideally this should be done during application startup.    More on conventions here Find Indexing

Description If you are seeing this error message when trying to access the Find tab in the CMS UI."The Find user interface is currently not available, please try again later."   This error is shown when the browser can't connect and fetch the javascript/css resources needed for the Find UI, usually delivered from dl.episerver.net but can also be hosted on the website if necessary. It's most likely caused by one of the following * Adblocker plugins in browsers that blocks access to dl.ep...

Description In some cases you may need to see what a site is sending out for Find requests. This is useful for identifying areas in need of caching or reducing the number of queries. Resolution In order for Fiddler to catch requests from Find, it needs to be a proxy or the man in the middle of the requests. Add the proxy within <system.net> tags within the <configuration> section. Note that after this change the site will give a search error until Fiddler is run.  <system.net...

Description In versions prior to Episerver.Find 13.1.0(not yet released), using .StaticallyCacheFor() with .FilterForVisitor() could cause find result caching to fail.  Resolution As a workaround to this issue, replace FilterForVisitor() with the three filters it applies behind the scenes and make sure the date time value is only updated to match cache duration.In other words, replace FilterForVisitor() with the following FiltersExcludeDelete()FilterOnReadAccess()PublishedInCu...

Description Demo indexes, i.e. indexes created at find.episerver.com, can intermittently lead to issues such as no search results,  401 errors, and failure to index. Although demo indexes have no promised uptime or reliability requirements there are some potential considerations. Resolution Find demo indexes are only valid for 30 days. If the index has existed for a period of time it may have expired. If the index is not working after being regenerated it may be caused by mainten...

Description This article describes an error message that can appear in the Find section of the Episerver CMS when accessing features like Best Bets and more. The error is:Your index does not support statistics Resolution This issue occurs when the index being used is expired. Please confirm the index configured in the section of web.config below. <episerver.find serviceUrl="url" defaultIndex="index"/> A lot of times it is a demo or developer Find index that has been decommissi...

Description After installing Find and then go to Edit mode. The whole Episerver Find UI is broken and gives this error:  EPiServer.Global System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: Error while copying content to a stream. ---> System.ObjectDisposedException: The CancellationTokenSource has been disposed. at System.Threading.CancellationTokenSource.ThrowObjectDisposedException() at System.Threading.CancellationTokenSource.InternalRe...

Description When leveraging a developer index for Find incorrect or unexpected results might be returned for larger sites or sites with expansive commerce catalogs. By default developer indexes have a limit of 10 thousand documents. Resolution Developer indexes have a cap of 10 thousand items, and cannot be increased beyond this point. To get an index that allows for more documents to be indexed a larger index can be purchased from the Order Episerver Find page. https://www.ep...

Description On your Find Document Types page (Find > Overview > Document Types) you may have a large number indexed documents, possibly more than your index allow. When your index reaches its max number of documents it will index no more documents than the limit, so reducing the document count may be a priority.   Resolution Two very common types responsible for a large percentage of the document count are .Variation and .Commerce.FindSearchProvider documents which are being indexed b...

Description This article describes an issue with Episerver page search in Edit mode. In this instance it appears to only work when using IDs in the search field. Resolution The first step is to try browsing to the service URL locally on the server. It would look like this and match the url in your configuration. For example: <episerver.search active="true"> <namedIndexingServices defaultService="serviceName"> <services> <add name="serviceName" baseUri="http://localhost:2047/In...

Description If you are using Azure with auto-scaling and you are using the builtin Episerver Search (not Find), search results will likely be corrupted at some point. This is based on the below blog post which stated the following. "Can I use Search, the built-in search function in Episerver CMS, instead of Find?Viktor: I wouldn't recommend it. A key value of the DXC Service is its automatic-scalability. Search is file-based, and gets corrupted when the DXC Service scales and the index ...

Description Episerver has the ability to do Wildcard and Synonym searching and you would like to use them both at the same time, unfortunately Episerver does not currently support this configuration of combined searching. Resolution Due to how Wildcard and Synonym search currently works, users of Episerver will not be able to combine them into a single search. Currently our engineering team is looking into implementing this ability. For now, you will have to do some work in th...

Description The article describes the issue when trying to add sorting of non-BoostMatching results with BoostMatching filtered results. The issue is that when adding sort to the results it will be ordered in that sort order only. The "score"-mechanism will be replaced, which makes BoostMatching useless. This is by design. For more information on Boosting with filters please see here. Resolution It is possible to first order by some property and then by score. This would ensur...

Description What is the difference between the public and private find url's and when to use them.  Resolution The answer is the index permission. The Public URL enables Read permission only while the Private URL allows Read-Write. With Public Url the GET operation can be used to allow searching content. In the UI or areas that need to update, create or delete the index the Private URL can be used.

Description If you have a multisite installation and want to get related queries filtered on the current site. Resolution What you can do is to do something like this: var didyouMean = client.Statistics().GetDidYouMean(model.Query, x =>            {                x.Size = 10;                x.Tags = new List<string> { "siteid:dd42ed4-9682-009a-ffll-8de0012adf8d" };            });

Description To remove page types from episerver search(lucene) search results do the below.  Resolution Add the ISearchable interface to your class and add the following properties.  public bool AllowReIndexChildren { get { return true; } } public bool IsSearchable { get { return false; } }   See the below example from an alloy site.  namespace EpiSearch.Models.Pages { /// /// Used primarily for publishing news articles on the website /// [SiteContentType( GroupName = Global...

Description Multi-words synonyms don't work if query contains WithAndAsDefaultOperator.  For example: if (!String.IsNullOrWhiteSpace(query.QueryString)) { search = search.For(query.QueryString) .InAllField() .WithAndAsDefaultOperator() .UsingSynonyms(); } Cause The issue is with how the tokenization is implemented in the current design of the product. Resolution This is a known design limitation.   However the team has developed a separate package to enhance this f...

The error you might see in your log is this: EPiServer.Logging.Compatibility.LogManager+CompatibilityWrapper.Error - An exception occurred while indexing (IContent). The operation has timed out. EPiServer.Find.ServiceException: The operation has timed out ---> System.Net.WebException: The operation has timed out Cause There is a possible issue with the cluster hosting the index, resulting in timeouts when the Find client is trying to reach the index to update it. Resolut...