Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

Henrik Fransas
Mar 18, 2016
  4064
(3 votes)

Using AppSettings instead of ConfigSections for Episerver Find

In the documentation for Episerver Find it says that you should write like this in your app.config or web.config file:

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

There also exist another way to set this up that are a little hidden, and that are to go through the appsettings in the config file. So instead of writing like the above you can write like this:

<appSettings>
    <add key="episerver:FindServiceUrl" value="http://..." />
    <add key="episerver:FindDefaultIndex" value="myindex" />
  </appSettings>
  

Depending on how you have set up you deployment pipeline this could be a nice way since it is easier to implement config transformation for this I think.

Mar 18, 2016

Comments

Vincent
Vincent Mar 22, 2016 04:40 AM

Good to know :)

For my current project, I remove the element first, then insert with different index key 


Henrik Fransas
Henrik Fransas Mar 22, 2016 07:57 AM

That is true!

Missed to inform about that. Thanks!

Jonas Carlbaum
Jonas Carlbaum Oct 22, 2018 08:57 AM

@episerver please update the documentation about *Staged deployments* settings in https://world.episerver.com/documentation/developer-guides/CMS/Deployment/deployment-scenarios/Deploying-to-Azure-webapps/#StagedDeployment to inform about how to enable a separate Find-index on Deployment slots.

Please login to comment.
Latest blogs
Join the Work Smarter Webinar: Working with the Power of Configured Commerce (B2B) Customer Segmentation December 7th

Join this webinar and learn about customer segmentation – how to best utilize it, how to use personalization to differentiate segmentation and how...

Karen McDougall | Dec 1, 2023

Getting Started with Optimizely SaaS Core and Next.js Integration: Creating Content Pages

The blog post discusses the creation of additional page types with Next.js and Optimizely SaaS Core. It provides a step-by-step guide on how to...

Francisco Quintanilla | Dec 1, 2023 | Syndicated blog

Stop Managing Humans in Your CMS

Too many times, a content management system becomes a people management system. Meaning, an organization uses the CMS to manage all the information...

Deane Barker | Nov 30, 2023

A day in the life of an Optimizely Developer - Optimizely CMS 12: The advantages and considerations when exploring an upgrade

GRAHAM CARR - LEAD .NET DEVELOPER, 28 Nov 2023 In 2022, Optimizely released CMS 12 as part of its ongoing evolution of the platform to help provide...

Graham Carr | Nov 28, 2023