How To Setup EpiFind For the First Time

In my previous tutorial, Review Of The Different Search Providers Available To Use On Your Episerver Project.  I talked about the different search providers available to use with an Episerver project.  If you decided to go with EpiFind then this tutorial will help you get your search up and running.

Setting Up An Index

The first thing you need to do when you using EpiFInd is to create a free dev account.  If you are unsure about how to do this, then I recommend reading, How To Set-Up A New EPiServer Find index in Less Than 5 Minutes.

Enabling EpiFind in your web.config

After you register and create your find index, at the end of the process you’ll be given your Find configuration, like this:

<configuration>
<configSections>
<section
name="episerver.find" type="EPiServer.Find.Configuration, EPiServer.Find" requirePermission="false"/>
</configSections>
<episerver.find
serviceUrl="URL"
defaultIndex="jonjonesshare_shareindex"/>
</configuration> 

Install the Episerver.Find.Cms Package

epi_find-cms

Open your Nuget Package Manager, right click on solutions ‘Manage Nuget Packages’, make sure you use the Episerver Nuget feed. If you haven’t bumped into the Epi Nuget feed, read this, How To Install EPiServer 7.5 Using the New Visual Studio Extension.

Enabling Find In The Episerver Backend

Before you can see EpiFnd, you will need to configure Episerver to display it. In your web.config (or potentially in episerver.config for legacy solutions), you should see a ” section, in here you will need to add this config:

<add name="Find">
<assemblies>
<add assembly="EPiServer.Find.Framework"/>
<add assembly="EPiServer.Find.Cms"/>
</assemblies>
</add>

So the complete ” should now look something like this:

<episerver.shell>
<publicModules rootPath="~/modules/" autoDiscovery="Modules" />
<protectedModules rootPath="~/EPiServer/">
<add name="Find">
<assemblies>
<add assembly="EPiServer.Find.Framework" />
<add assembly="EPiServer.Find.Cms" />
</assemblies>
</add>
<add name="Shell" /><add name="CMS" /><add name="EPiServer.Packaging.UI" /></protectedModules>
</episerver.shell>

Now compile your website and open your Episerver backend…

epi_find_cms_2

Jon D Jones

Software Architect, Programmer and Technologist Jon Jones is founder and CEO of London-based tech firm Digital Prompt. He has been working in the field for nearly a decade, specializing in new technologies and technical solution research in the web business. A passionate blogger by heart , speaker & consultant from England.. always on the hunt for the next challenge

More Posts

1 reply
  1. Henrik Fransas
    Henrik Fransas says:

    I think/thought that the nuget package would add those assemblies by it self, has that changed?

    Another thing is that I would recommend to use app settings instead of the config settings for the URL the the index since it makes it easier to do config transformation or config tab in Azure.

    Reply

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *