• Your index does not support statistics

    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 inde...

  • Broken Find UI

    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.Inte...

  • Incorrect or unexpected results when leveraging developer Find index

    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...

  • How to reduce the number of documents indexed by Find

    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 ind...

  • Page search in Edit mode only works with IDs

    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="...

  • Autoscaling and Episerver Search

    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 i...

  • Using Wildcard and Synonym searching in Episerver

    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...

  • How to Combine Standard Sort Orders with BoostMatching

    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 w...

  • Find Index - Public and Private Urls

    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.

  • Episerver Find - related queries on current site on a multi-site

    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" };            });

  • Removing page type from Episerver Search results

    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...

  • Multi-words synonyms don't work if query contains WithAndAsDefaultOperator

    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 and improvements are planned to be made in a future release.

  • Find Index Timeout with OnPublish Event

    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. Reso...