Blog posts by Kim Gunnarsson2016-02-20T23:26:26.0000000Z/blogs/kim-gunnarsson/Optimizely WorldEpiserver Find UnifiedSearchFor with configurable operatorhttp://www.kimgunnarsson.se/unifiedsearchfor-with-configurable-operator/2016-02-20T23:26:26.0000000Z<p>When using <strong>UnifiedSearch</strong> in Episerver Find, I prefer to use the method <code>IClient.UnifiedSearchFor()</code> because it takes care of necessary logic without exposing implementation details, rendering in lower risk of introducing bugs and unwanted behaviour.</p>
<p>By default, multiword queries is concatenated using the operator <code>OR</code>, but in this case we</p>Generic EditorDescriptor for custom SelectionFactorieshttp://www.kimgunnarsson.se/generic-editordescriptor-for-custom-selectionfactories/2015-12-21T08:50:00.0000000Z<p>We are extensive users of the feature of implementing custom selection factories by using the <code>EditorDescriptor</code>-attribute in Episerver. </p>
<p>The use-case is quite simple and provides the editor with the ability to single select a value within multiple alternatives using a drop down. But as the selection stores grow, the</p>Make Episerver SelectionEditor support HTML-labelshttp://www.kimgunnarsson.se/make-selectioneditor-support-html-values/2015-12-21T08:00:00.0000000Z<p>Somewhere between the releases of Episerver 7.5 and latest, a small but subtle change in how the <code>epi-cms/contentediting/editors/SelectionEditor</code> displays labels in associated drop downs was made.</p>
<p>The line <code>label: item.text</code> was replaced with <code>label: entities.encode(item.text)</code> rendering in everything put in a label</p>IContentMedia and Required fields is not the best ideahttp://www.kimgunnarsson.se/mediadata-and-required-fields-is-not-the-best-idea/2015-09-08T21:10:57.0000000Z<p>Sometimes when working with <code>MediaData</code> or other inherited <code>IContentMedia</code> in EPiServer you need to add extra fields and properties. If you do – <strong>resist the temptation to make them <em>Required</em></strong>.</p>
<p>The standard behaviour when uploading a document it becomes <code>Published</code> upon upload completion. When adding properties (fields) with the <code>[Required]</code> attribute,</p>Working with Categories in EPiServer CMS 8 – a nice 'gotcha'!http://www.kimgunnarsson.se/working-with-categories-in-episerver-cms-8-a-quick-heads-up/2015-06-23T16:54:41.0000000Z<p>I am currently working with the category functionality in EPiServer and ran into a small hiccup with the new <strong>CategoryRepository</strong> <a href="/link/5b6e91ea32d24d9f9e3cd22d149f4c63.aspx">introduced in EPiServer CMS 8</a>. Nothing large, just a small heads up if you are working with a site where your editors are using and updating categories. </p>
<p>A small but</p>Using page properties as dynamic propertieshttp://www.kimgunnarsson.se/using-page-properties-as-dynamic-properties/2014-06-23T16:59:00.0000000Z<p>Sometimes in EPiServer you need properties that inherit values.Dynamic Properties is great for that, but as <a href="/link/2c2f0170f444425e917e31017abf5a3d.aspx">Anders Hattestad claims (and proposes a solution)</a>, it's a bit tricky working with these in EPiServer CMS 7+ versions.</p>
<p>In a current project, we needed just that; have a variety of inherited property</p>