Blog posts by Matthew Boniface2015-09-04T02:05:29.0000000Zhttps://world.optimizely.com/blogs/Matthew-Boniface/Optimizely WorldEPiServer Commerce CartCheckout workflow with IsIgnoreProcessPayment parameter<p>EPiServer Commerce has substantial processes which rely on workflows. In many scenarios, like on a simple consumer website, you may get away without modifying or configuring these workflows beyond their defaults.</p><p>But on my current project I needed to simply disable payment processing in the CartCheckout workflow. And there is an API method in Mediachase.Commerce.Orders.OrderGroup that facilitates this:</p><pre class="prettyprint"><code>// Summary:<br />// Runs the specified workflow.<br />//<br />// Parameters:<br />// name:<br />// The name.<br />//<br />// throwException:<br />// if set to true the exception will be thrown and should be handled by the<br />// caller.<br />//<br />// param:<br />// The additional input parameters.<br />public virtual WorkflowResults RunWorkflow(string name, bool throwException, Dictionary<string, object> param);</code></pre><p>For my situation setting IsIgnoreProcessPayment to true when running the CartCheckout workflow, this is my simplified code that was required:</p><pre class="prettyprint"><code>var workflowParams = new Dictionary<string, object> { { "IsIgnoreProcessPayment", true } }<br />var results = cartHelper.Cart.RunWorkflow(OrderGroupWorkflowManager.CartCheckOutWorkflowName, true, workflowParams);</code></pre><p>I hunted for examples of how to set IsIgnoreProcessPayment so thought it deserved a blog post.<br /></p>2015-09-04T02:05:29.0000000ZBlog postImplementing IPriceService with default IPriceService as its dependency<p>In EPiServer Commerce prices are loaded via the IPriceService and IPriceDetailService. I needed to customise the IPriceService logic but just to tweak the price filtering and still intend to call the default IPriceService internally to reuse the base functionality.</p><p>This is where confusion ensues, how does one configure the dependency resolver (StructureMap) to return my custom price service implementation which itself has a dependency on the same IPriceService interface? Turns out StructureMap has a method called EnrichWith to achieve this.</p><p>So I have my implementation called “CustomPriceService” and the default EPiServer implmentation is “PriceServiceDatabase“. My CustomPriceService constructor looks like this:<br /></p><pre class="prettyprint"><code>public CustomPriceService(IPriceService defaultPriceService)<br />{<br /> this._defaultPriceService = defaultPriceService;<br />}</code></pre><p>Now I have the local field _defaultPriceService that I can call for default functionality throughout my custom implementation and it still retains the injected abstraction for unit testing purposes.</p><p>To configure StructureMap all that is needed is:</p><pre class="prettyprint"><code>container.For<IPriceService>().Use<PriceServiceDatabase>().EnrichWith((context, systemPriceService) => new CustomPriceService(systemPriceService));</code></pre><p>When an IPriceService dependency is resolved StructureMap will get the default EPiServer Commerce “PriceServiceDatabase” and then create my “CustomPriceService” passing the PriceServiceDatabase into the constructor.</p><p>If your constructor needs other dependencies you can use the “IContext” that EnrichWith provides, for example:</p><pre class="prettyprint"><code>container.For<IPriceService>().Use<PriceServiceDatabase>().EnrichWith((context, systemPriceService) => new CustomPriceService(systemPriceService, context.GetInstance<ICurrentMarket>()));</code></pre><p>Hopefully this will help anyone trying to figure out how to get StructureMap to configure a dependency for a given type to itself have a dependency on the same type.</p>2015-09-04T01:11:54.0000000ZBlog postEPiServer 7 & 8 overriding editor UI language values<p><strong>Update (28 Dec 2015):</strong> I have since noticed that this information now seems to be officially documented at <a href="/link/c783c321595d46cbb797392079692b0c.aspx">http://world.episerver.com/documentation/Items/Developers-Guide/Episerver-CMS/9/Globalization/localizing-the-user-interface/</a></p>
<p>It could be something I simply missed, but I spent a fair amount of time searching the web for how to override the text an EPiServer editor sees for content types and properties. Perhaps this is so obvious that no one else needed documentation or examples on the web to figure it out? Ultimately though, I found the answer in the Alloy sample website code.</p><p>I’m currently using EPiServer 8 (8.2 to be precise) and found placing the following in a lang xml file will override a custom content type and properties:</p><pre class="prettyprint"><code><contenttypes>
<HomePage>
<name>Hemsida</name>
<description>Startsidan för webbplatsen</description>
<properties>
<MainContentArea>
<help>Huvudinnehållsområdet till att omfatta hemsidan widgets</help>
</MainContentArea>
</properties>
</HomePage>
<ContentMetadataBlock>
<name>Innehåll Metadata Block</name>
<properties>
<Description>
<caption>Beskrivning</caption>
<help>Meta beskrivning taggar arbetar med titeln att locka besökare till dina sidor. Standard SEO regeln är att hålla dina metabeskrivningar till 150 tecken eller mindre.</help>
</Description>
</properties>
</ContentMetadataBlock>
</contenttypes></code></pre><p>In this case I’m overriding the HomePage’s “name”, “description” and its “MainContentArea” properties “help” text with the Swedish language version. And below this I demonstrate a block having similar text overridden.</p><p>Now an editor with the UI set to Swedish will find property names and descriptions have been customised for them.</p><p>From what I see in the Alloy site, you can also do generic overrides for common properties throughout your codebase by using a base type or even an interface, such as IContentData:</p><pre class="prettyprint"><code><contenttypes>
<icontentdata>
<properties>
<!-- SitePageData -->
<disableindexing>
<caption>Disable indexing</caption>
<help>Prevents the page from being indexed by search engines</help>
</disableindexing>
<!-- Common properties-->
<mainbody>
<caption>Main body</caption>
<help>Main editorial content of the page</help>
</mainbody>
</properties>
</icontentdata>
</contenttypes></code></pre><p>Hopefully this helps someone else to more easily discover this.</p>2015-05-29T03:58:23.0000000ZBlog postEPiServer log4net stopped working<p>An EPiServer website I worked on had logging working well until it [seemingly] randomly stopped working. I reviewed changes in our configurations and could not trace a cause for the sudden failure.</p>
<p>I proceeded to enable log4net’s own logging which is done by adding this to your web.config:</p>
<pre class="prettyprint"><code><appSettings><br /> <add key="log4net.Internal.Debug" value="true"/><br /></appSettings><br /><system.diagnostics><br /> <trace autoflush="true"><br /> <listeners><br /> <add<br /> name="textWriterTraceListener"<br /> type="System.Diagnostics.TextWriterTraceListener"<br /> initializeData="C:\log4net.txt" /><br /> </listeners><br /> </trace><br /></system.diagnostics></code></pre>
<p>This log revealed the following:</p>
<pre class="prettyprint"><code>log4net: XmlConfigurator: configuring repository [log4net-default-repository] using file [C:\Dev\Project1\Trunk\Src\Web\web.config]<br />log4net: XmlConfigurator: configuring repository [log4net-default-repository] using stream<br />log4net: XmlConfigurator: loading XML configuration<br />log4net: XmlConfigurator: XML configuration does not contain a <log4net> element. Configuration Aborted.</code></pre>
<p>With EPiServer, this should be using it’s default EPiServerLog.config rather than log4net’s default web.config location - hence why it’s not finding the <log4net> element.</p>
<p>It took me a little experimentation and searching before I realised the problem was caused because I referenced log4net in our Global.asax.cs. This causes it to setup log4net prior to EPiServer determining the EPiServerLog.config file. Once I removed that, it all worked again!</p>2013-12-03T02:17:00.0000000ZBlog postWeb deploy ignoring config transforms<p>If you have an annoying issue where your CI (TeamCity) web deployments were not transforming some configs, you’re not alone. And I might have found a reason why:</p>
<p><span>Mine in particular was transforming a few configs (web.config, episerverlog.config etc) whilst not transforming some (connectionstrings.config, episerverframework.config and episerver.config).</span></p>
<p><span>It turns out that the Web.csproj file had them specified differently. The ones that were working looked like this:</span></p>
<pre class="prettyprint"><code><Content Include="EPiServerLog.config"><br /> <SubType>Designer</SubType><br /> <TransformOnBuild>true</TransformOnBuild><br /></Content></code></pre>
<p>While the configs that did not work had only:</p>
<pre class="prettyprint"><code><Content Include="EPiServerFramework.config" /></code></pre>
<p>So I’ve added in the <TransformOnBuild>true</TransformOnBuild> and they now work :)</p>2013-09-18T06:18:20.0000000ZBlog postWeb deploy ignoring config transforms<p>If you have an annoying issue where your CI (TeamCity) web deployments were not transforming some configs, you’re not alone. And I might have found a reason why:</p>
<p><span>Mine in particular was transforming a few configs (web.config, episerverlog.config etc) whilst not transforming some (connectionstrings.config, episerverframework.config and episerver.config).</span></p>
<p><span>It turns out that the Web.csproj file had them specified differently. The ones that were working looked like this:</span></p>
<pre class="prettyprint"><code><Content Include="EPiServerLog.config"><br /> <SubType>Designer</SubType><br /> <TransformOnBuild>true</TransformOnBuild><br /></Content></code></pre>
<p>While the configs that did not work had only:</p>
<pre class="prettyprint"><code><Content Include="EPiServerFramework.config" /></code></pre>
<p>So I’ve added in the <TransformOnBuild>true</TransformOnBuild> and they now work :)</p>2013-09-18T06:18:20.0000000ZBlog postWeb deploy ignoring config transforms<p>If you have an annoying issue where your CI (TeamCity) web deployments were not transforming some configs, you’re not alone. And I might have found a reason why:</p>
<p><span>Mine in particular was transforming a few configs (web.config, episerverlog.config etc) whilst not transforming some (connectionstrings.config, episerverframework.config and episerver.config).</span></p>
<p><span>It turns out that the Web.csproj file had them specified differently. The ones that were working looked like this:</span></p>
<pre class="prettyprint"><code><Content Include="EPiServerLog.config"><br /> <SubType>Designer</SubType><br /> <TransformOnBuild>true</TransformOnBuild><br /></Content></code></pre>
<p>While the configs that did not work had only:</p>
<pre class="prettyprint"><code><Content Include="EPiServerFramework.config" /></code></pre>
<p>So I’ve added in the <TransformOnBuild>true</TransformOnBuild> and they now work :)</p>2013-09-18T06:18:20.0000000ZBlog postWeb deploy ignoring config transforms<p>If you have an annoying issue where your CI (TeamCity) web deployments were not transforming some configs, you’re not alone. And I might have found a reason why:</p>
<p><span>Mine in particular was transforming a few configs (web.config, episerverlog.config etc) whilst not transforming some (connectionstrings.config, episerverframework.config and episerver.config).</span></p>
<p><span>It turns out that the Web.csproj file had them specified differently. The ones that were working looked like this:</span></p>
<pre class="prettyprint"><code><Content Include="EPiServerLog.config"><br /> <SubType>Designer</SubType><br /> <TransformOnBuild>true</TransformOnBuild><br /></Content></code></pre>
<p>While the configs that did not work had only:</p>
<pre class="prettyprint"><code><Content Include="EPiServerFramework.config" /></code></pre>
<p>So I’ve added in the <TransformOnBuild>true</TransformOnBuild> and they now work :)</p>2013-09-18T06:18:20.0000000ZBlog postWeb deploy ignoring config transforms<p>If you have an annoying issue where your CI (TeamCity) web deployments were not transforming some configs, you’re not alone. And I might have found a reason why:</p>
<p><span>Mine in particular was transforming a few configs (web.config, episerverlog.config etc) whilst not transforming some (connectionstrings.config, episerverframework.config and episerver.config).</span></p>
<p><span>It turns out that the Web.csproj file had them specified differently. The ones that were working looked like this:</span></p>
<pre class="prettyprint"><code><Content Include="EPiServerLog.config"><br /> <SubType>Designer</SubType><br /> <TransformOnBuild>true</TransformOnBuild><br /></Content></code></pre>
<p>While the configs that did not work had only:</p>
<pre class="prettyprint"><code><Content Include="EPiServerFramework.config" /></code></pre>
<p>So I’ve added in the <TransformOnBuild>true</TransformOnBuild> and they now work :)</p>2013-09-18T06:18:20.0000000ZBlog postWeb deploy ignoring config transforms<p>If you have an annoying issue where your CI (TeamCity) web deployments were not transforming some configs, you’re not alone. And I might have found a reason why:</p>
<p><span>Mine in particular was transforming a few configs (web.config, episerverlog.config etc) whilst not transforming some (connectionstrings.config, episerverframework.config and episerver.config).</span></p>
<p><span>It turns out that the Web.csproj file had them specified differently. The ones that were working looked like this:</span></p>
<pre class="prettyprint"><code><Content Include="EPiServerLog.config"><br /> <SubType>Designer</SubType><br /> <TransformOnBuild>true</TransformOnBuild><br /></Content></code></pre>
<p>While the configs that did not work had only:</p>
<pre class="prettyprint"><code><Content Include="EPiServerFramework.config" /></code></pre>
<p>So I’ve added in the <TransformOnBuild>true</TransformOnBuild> and they now work :)</p>2013-09-18T06:18:20.0000000ZBlog post