<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><language>en</language><title>Blog posts by Kim Gunnarsson</title> <link>https://world.optimizely.com/blogs/kim-gunnarsson/</link><description></description><ttl>60</ttl><generator>Optimizely World</generator><item> <title>Episerver Find UnifiedSearchFor with configurable operator</title>            <link>http://www.kimgunnarsson.se/unifiedsearchfor-with-configurable-operator/</link>            <description>&lt;p&gt;When using &lt;strong&gt;UnifiedSearch&lt;/strong&gt; in Episerver Find, I prefer to use the method &lt;code&gt;IClient.UnifiedSearchFor()&lt;/code&gt; because it takes care of necessary logic without exposing implementation details, rendering in lower risk of introducing bugs and unwanted behaviour.&lt;/p&gt;

&lt;p&gt;By default, multiword queries is concatenated using the operator &lt;code&gt;OR&lt;/code&gt;, but in this case we&lt;/p&gt;</description>            <guid>http://www.kimgunnarsson.se/unifiedsearchfor-with-configurable-operator/</guid>            <pubDate>Sat, 20 Feb 2016 23:26:26 GMT</pubDate>           <category>Blog post</category></item><item> <title>Generic EditorDescriptor for custom SelectionFactories</title>            <link>http://www.kimgunnarsson.se/generic-editordescriptor-for-custom-selectionfactories/</link>            <description>&lt;p&gt;We are extensive users of the feature of implementing custom selection factories by using the &lt;code&gt;EditorDescriptor&lt;/code&gt;-attribute in Episerver. &lt;/p&gt;

&lt;p&gt;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&lt;/p&gt;</description>            <guid>http://www.kimgunnarsson.se/generic-editordescriptor-for-custom-selectionfactories/</guid>            <pubDate>Mon, 21 Dec 2015 08:50:00 GMT</pubDate>           <category>Blog post</category></item><item> <title>Make Episerver SelectionEditor support HTML-labels</title>            <link>http://www.kimgunnarsson.se/make-selectioneditor-support-html-values/</link>            <description>&lt;p&gt;Somewhere between the releases of Episerver 7.5 and latest, a small but subtle change in how the &lt;code&gt;epi-cms/contentediting/editors/SelectionEditor&lt;/code&gt; displays labels in associated drop downs was made.&lt;/p&gt;

&lt;p&gt;The line &lt;code&gt;label: item.text&lt;/code&gt; was replaced with &lt;code&gt;label: entities.encode(item.text)&lt;/code&gt; rendering in everything put in a label&lt;/p&gt;</description>            <guid>http://www.kimgunnarsson.se/make-selectioneditor-support-html-values/</guid>            <pubDate>Mon, 21 Dec 2015 08:00:00 GMT</pubDate>           <category>Blog post</category></item><item> <title>IContentMedia and Required fields is not the best idea</title>            <link>http://www.kimgunnarsson.se/mediadata-and-required-fields-is-not-the-best-idea/</link>            <description>&lt;p&gt;Sometimes when working with &lt;code&gt;MediaData&lt;/code&gt; or other inherited &lt;code&gt;IContentMedia&lt;/code&gt; in EPiServer you need to add extra fields and properties. If you do – &lt;strong&gt;resist the temptation to make them &lt;em&gt;Required&lt;/em&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The standard behaviour when uploading a document it becomes &lt;code&gt;Published&lt;/code&gt; upon upload completion.  When adding properties (fields) with the &lt;code&gt;[Required]&lt;/code&gt; attribute,&lt;/p&gt;</description>            <guid>http://www.kimgunnarsson.se/mediadata-and-required-fields-is-not-the-best-idea/</guid>            <pubDate>Tue, 08 Sep 2015 21:10:57 GMT</pubDate>           <category>Blog post</category></item><item> <title>Working with Categories in EPiServer CMS 8 – a nice &#39;gotcha&#39;!</title>            <link>http://www.kimgunnarsson.se/working-with-categories-in-episerver-cms-8-a-quick-heads-up/</link>            <description>&lt;p&gt;I am currently working with the category functionality in EPiServer and ran into a small hiccup with the new &lt;strong&gt;CategoryRepository&lt;/strong&gt; &lt;a href=&quot;/link/5b6e91ea32d24d9f9e3cd22d149f4c63.aspx&quot;&gt;introduced in EPiServer CMS 8&lt;/a&gt;. Nothing large, just a small heads up if you are working with a site where your editors are using and updating categories. &lt;/p&gt;

&lt;p&gt;A small but&lt;/p&gt;</description>            <guid>http://www.kimgunnarsson.se/working-with-categories-in-episerver-cms-8-a-quick-heads-up/</guid>            <pubDate>Tue, 23 Jun 2015 16:54:41 GMT</pubDate>           <category>Blog post</category></item><item> <title>Using page properties as dynamic properties</title>            <link>http://www.kimgunnarsson.se/using-page-properties-as-dynamic-properties/</link>            <description>&lt;p&gt;Sometimes in EPiServer you need properties that inherit values.Dynamic Properties is great for that, but as &lt;a href=&quot;/link/2c2f0170f444425e917e31017abf5a3d.aspx&quot;&gt;Anders Hattestad claims (and proposes a solution)&lt;/a&gt;, it&#39;s a bit tricky working with these in EPiServer CMS 7+ versions.&lt;/p&gt;

&lt;p&gt;In a current project, we needed just that; have a variety of inherited property&lt;/p&gt;</description>            <guid>http://www.kimgunnarsson.se/using-page-properties-as-dynamic-properties/</guid>            <pubDate>Mon, 23 Jun 2014 16:59:00 GMT</pubDate>           <category>Blog post</category></item></channel>
</rss>