Hi Per! Yes, I first ran a custom job which clears the index like this:
var client = ServiceLocator.Current.GetInstance<IClient>(); client.Delete<object>(x => x.GetType().Name.Exists() | !x.GetType().Name.Exists());
After which I ran the built-in job "EPiServer Find Content Indexing Job".
Ah ok, but I assume the job I ran does the same as the "clear index" button?
FilterForVisitorExtension.cs looks like this:
public static IEnumerable<T> FilterOnType<T>(IEnumerable<IContent> collection) where T : IContent { return EPiServer.Filters.FilterForVisitor.Filter(collection).OfType<T>(); // Line 11 }
The code looks correct to me. Although you do not need to to run the extra FilterForVisitor after the query has been run.
Looks like the problem is "ElasticSearchIllegalArgumentException[Sorting on string type field does not support missing parameter]", which does not sound right as "name" should never be empty, and even if it was, that should not really be a problem.
Now that I try to use the "clear index" button instead of the custom job I get an error message saying:
Unable to load /episerver/Find/proxy/_clear?clear_index=true&clear_stats=false status: 400
Perhaps there is something wrong with the index. Could you try the dev index in your staging environment? If there is something wrong with the index, I suggest you contact operations@episerver.com
Unfortunately I can't use my dev index in the staging environment as the staging environment is restricted network-wise (getting error message "No connection could be made because the target machine actively refused it" when trying). Is there any way for me to clear the index completely if I log onto the index server? As you're saying, the index might be corrupted somehow, so would be excellent if I can manually clear it by deleting files/folders on the server where the index is located.
After updating from EPiServer.Find 11.0.0.3701 to 12.3.2.0 I'm getting an error when searching for a page type:
ContactUsPageViewModel.cs:
FindHelper.cs:
Another odd thing is that this error doesn't happen with my local developer Find index, only in our stage environment.