<?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 Marcin Wrzyciel</title> <link>https://world.optimizely.com/blogs/marcin-wrzyciel/</link><description></description><ttl>60</ttl><generator>Optimizely World</generator><item> <title>Configuring coupon promotions to give you two types of rewards</title>            <link>http://wrzyciel.pl/?p=218</link>            <description>In the world of a big business you can find a lot of very complicated business rules but sometimes things that seems to be an easy task when it comes to reality are not. A good example of that was one of our client requirement. Basically he wanted to have a promotion that will give [&amp;#8230;]</description>            <guid>http://wrzyciel.pl/?p=218</guid>            <pubDate>Wed, 26 Nov 2014 23:55:53 GMT</pubDate>           <category>Blog post</category></item><item> <title>Limiting EPiServer Promotions to be “inclusive only”</title>            <link>http://wrzyciel.pl/?p=220</link>            <description>Sometimes, especially when you create your custom promotions, you may like your promotions to meet some criterias. In our latest project due to a nature of our custom promotions we needed to made it &amp;#8220;inclusive only&amp;#8221;, so if user put in his cart products that are eligible for two configured promotions both should be applied. [&amp;#8230;]</description>            <guid>http://wrzyciel.pl/?p=220</guid>            <pubDate>Thu, 23 Oct 2014 23:05:59 GMT</pubDate>           <category>Blog post</category></item><item> <title>Force EPiServer7 to not add empty divs for ContentAreas</title>            <link>http://wrzyciel.pl/?p=179</link>            <description>By default when rendering ContentAreas EPiServer 7 adds a number of empty (without any style or class defined) divs &amp;#8211; one outlining each content area item and another one for ContentArea itself. Although it may be problematic when rendering page for visitors (not semantic and don’t allow you to optimize css selectors) it’s neccessary for [&amp;#8230;]</description>            <guid>http://wrzyciel.pl/?p=179</guid>            <pubDate>Tue, 25 Feb 2014 23:42:19 GMT</pubDate>           <category>Blog post</category></item></channel>
</rss>