A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
Not sure...
If it's not visible here /EPiServer/Find/#manage/optimization/autocomplete I think you need to to something like:
Clear statistics and change the code and...
Another option could be to put your own proxy'ing code on top of Find's autocomplete-URL and filter the JSON yourself. I've done this to re-format to what the front-end code needed.
BUT...
In my experience autocomplete in this manor is not helping the visitor and is open for abuse so I usually recommend some kind of search-as-you-type returning wildcard matches from some specific types or an editorial phrase repository.
I agree with you Johan, it is mutch better to have it working like for example www.prisjakt.se.
Thanks for the input, I will check out how I can filter away the noise
We are having strange suggestions in autocomplete. If someone for example have done a search for Alloy' they will get a result because Find will filter away the ' character but later it will return Alloy' as a suggestion for autocomplete.
Does anyone know if it is possible to filter this suggestions so we wont see them?