World is now on Opti ID! Learn more

Håkon Nordli
Apr 8, 2016
  855
(0 votes)

Episerver full-text search module

Episerver full-text search module aka Standard Search Inspector

The last years I've set up and worked with several sites using Episerver full-text search. Episerver Search is like you might already know, a search engine delivered together with Episerver CMS without any extra costs. It is based on Lucene which gives it a powerful foundation.

Several of times I've had issues when customers wanted something extra like facets or want an explanation on how the relevance work.

For me it has been difficult to find good examples, good practices and/or blog posts about the search API. To solve this I've started to develop a module. I hope this can be a module that more people contribute to.

The goal is not to compete with Find. Find is still a better search engine with more functionality, and the search engine I recommend customers. But for different reasons some customers don't want Find.

At the moment the module only have two functions:

  1. A search inspector which shows indexed items as JSON objects. This gives us as developers a lot more control on which data that are indexed.

    blogg image1

  2. A reindexing page. As several of us know, the reindex page is a hidden feature in Episerver which is a bit annoying. To be honest I visit my colleague Svein Aandahls blog post everytime I need the URL to the reindex-page. Sorry Svein, your visit numbers might go down.

    blogg image2

The module is available through Episervers nuget feed, http://nuget.episerver.com/en/OtherPages/Package/?packageId=Knowit.EPiModules.StandardSearchInspector

It is also added to Github, https://github.com/knowit/Knowit.EPiModules.StandardSearchInspector, where anyone may add pull requests. Please be brave and add features, that would be awesome!

Apr 08, 2016

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |