EPiServer Find Archive
When using Optimizely Search & Navigation (previously Episerver Find) you will automatically get a reference to a client side Javascript injected into your markup. Occationally, you may want to proxy it via your Optimizely website’s backend, caching it or just make it appear as if it comes from your own domain. It may also be a way of avoiding false positives in regards to script …
This article is based on work described in A way of consolidating EPiServer Find Unified Search over multiple websites as well as Example: Pluggable EPiServer Find UnifiedSearch for selected types. If you want to use ajax to retrieve more search hits, apply hit filtering or the like, you would need to pay some extra consideration to the API. Since the ajax call from the frontend …
In this example on how the pluggable EPiServer Find UnifiedSearch may be implemented we will look at simple type filtering. Previously we did this using TypeSearch, but since we moved to UnifiedSearch in my current project, it had to be reimplemented. For more information, please see the previous article A way of consolidating EPiServer Find Unified Search over multiple websites. You may also be interested …
At my current client’s we are building a common platform containing shared code between several EPiServer multisite installations. Due to reasons the way we implemented searches with EPiServer Find had diverged to a point where it was necessary to take a step back and refactor it. This is what we came up with. For an implementation of the specific search class, please see article Example: …
At my current client’s we are building a large platform serving several EPiServer multisite installations with common code. Consolidating how we work with EPiServer Find, we ran into a bit of trouble. My collegue Svante Seleborg did all of the heavy lifting on this one (I’m just taking the credit). While attempting to add simple UnifiedSearchRegistry conventions, as the kind shown in below code snippet, …