Blog posts by Richly2015-08-25T18:45:12.2700000Zhttps://world.optimizely.com/blogs/Richly/Optimizely WorldPayPalPayment Serialization for Sending Email Through Commerce Template Service<p>This may be helpful for developers who are looking to serialize the PayPalPayment class - which stores information such as the PayPal token and order number - using Mediachase.Commerce.Engine.Template.Providers.XslTemplateProvider. We received such a question in Developer Support, so I wanted to share one solution provided by our Commerce product team.</p>
<h3>General steps</h3>
<ul>
<li>Create your own TemplateProvider that inherits from XslTemplateProvider</li>
<li>Add a settable property that takes a Type array</li>
<li>Override the Process method (see current source code below) and make sure that the line instantiating the XmlSerializer</li>
<li>
<pre class="language-html"><code> XmlSerializer serializer = new XmlSerializer(contextObject.GetType());</code></pre>
<br /><br /></li>
<li>Instead uses the constructor that takes a type array as the second parameter (this will be the extended types – PayPalPayment in this case)</li>
<li>Before calling into the Process method (from the TemplateService.Process call), make sure that the new type array property has been set (the template provider can be accessed thru “new TemplateSevice().Provider…” since the backing variable is static)</li>
<li>Update configuration file to use your custom TemplateProcessor</li>
</ul>
<h3>Code Example</h3>
<p> </p>
<pre class="language-csharp"><code>public override string Process(string template, CultureInfo culture, System.Collections.IDictionary context)
{
// 1. Serialize all context variables into XML
MemoryStream stream = new MemoryStream();
// Start creating xml document
XmlWriterSettings xmlFileSettings = new XmlWriterSettings();
xmlFileSettings.Indent = true;
XmlWriter exportWriter = XmlWriter.Create(stream, xmlFileSettings);
// Start the Xml Document
exportWriter.WriteStartDocument();
exportWriter.WriteStartElement("ContextDoc", "");
// Cycle through dictionary
foreach (string key in context.Keys)
{
object contextObject = context[key];
XmlSerializer serializer = new XmlSerializer(contextObject.GetType());
serializer.Serialize(exportWriter, contextObject);
}
exportWriter.WriteEndElement(); // End of ContextDoc
exportWriter.WriteEndDocument();
exportWriter.Close(); // Close the XmlWriter Stream
stream.Position = 0;
// 2. Locate XSL Template
XslCompiledTransform xslt = new XslCompiledTransform();
string path = String.Format(TemplateSource, culture.Name, template);
string specificPath = String.Empty;
// Check default path if language specific one doesn't exist
if (!File.Exists(path))
{
specificPath = path;
path = String.Format(TemplateSource, "Default", template);
}
// Generate exception if path doesn't exist
if (!File.Exists(path))
{
throw new ProviderException(String.Format("The template was not found at the default path \"{0}\" nor at the specific path \"{1}\". Please either modify settings in web.config for XSL Provider or create an xsl template in the path specified.", path, specificPath));
}
// Load otherwise
xslt.Load(path);
// 3. Transform Content
stream.Position = 0;
XPathDocument pathDoc = new XPathDocument(stream);
MemoryStream outputStream = new MemoryStream();
StringWriter writer = new StringWriter();
xslt.Transform(pathDoc, null, writer);
// Return contents
return writer.ToString();
}
</code></pre>2015-08-25T18:45:12.2700000ZBlog postUpdated CMO 7.5 Nuget Package Now Available<p>If you’re on 7.5 or greater and on MVC, you’ll be rejoicing at this latest update. The latest package addresses a major issue with MVC and A/B testing (<a href="/link/092227481eb64ae9b78ebd86e7e2d37a.aspx">http://world.episerver.com/Support/Bug-list-beta/bug/113589</a>). If you’re experiencing the issues raised in the bug report, <a href="http://nuget.episerver.com/en/OtherPages/Package/?packageId=EPiServer.Cmo&packageVersion=7.5.566.0">download EPiServer.Cmo 7.5.566.0</a> now!</p>2014-10-22T21:25:53.0000000ZBlog postFor Those Who Had Issues Updating to Commerce 7.10<p> <p> <p>Last Friday, new updates were released for the Commerce NuGet packages. The version numbers are now 7.10.1. I am aware that many who tried to update to the older 7.10 packages were greeted with a new migration page which forced a database update. Unfortunately, it seemed that those who attempted to update to 7.10 got <a href="http://world.episerver.com/Forum/Developer-forum/-EPiServer-75-CMS/Thread-Container/2014/7/Error-in-update-epidatabse/?pageIndex=2">migration failures instead</a>. <br /> <br />I am happy to note that the migration issues should be fixed in 7.10.1 and I was able to update a base Commerce 7.5 site with sample templates to 7.10.1. Via NuGet console, I installed EPiServer.Commerce and then ran “update-epidatabase” to get to the migration page on my Commerce site. <br /> <br /> <a href="/link/4c52b411574649e4a8116424c26c7f4a.png"><img title="image" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="image" src="/link/4232ee23f81444288d92f84e1859538d.png" width="554" height="226" /></a> <br /> <br /><strong>Migration completed. Yay!</strong></p> </p> </p> <p> <p>Clicking on “Go to start page” should direct you to your newly updated 7.10.1 site. <br /> <br />Information specific to what’s new in Commerce 7.10 can be hard to find, so here’s some quick links to get you in the right direction: <br /> <br /><a title="http://world.episerver.com/Documentation/Items/Installation-Instructions/Installing-EPiServer-updates/" href="http://world.episerver.com/Documentation/Items/Installation-Instructions/Installing-EPiServer-updates/">http://world.episerver.com/Documentation/Items/Installation-Instructions/Installing-EPiServer-updates/</a> <br /></p> <p><strong>[New in 7.10.0]</strong> An update may have one or more migration steps that need to be executed in order for the site to work correctly. If so, any request to the site will be redirected to a migration page. In order to access it you need to be part of the "CommerceAdmins" role. From there it is possible to run the migration steps and track the progress. Once all steps have been completed successfully the redirects will stop, and the site will be back to normal. <br /></p> <p><strong>[New in 7.10.0]</strong> It is possible to have the migration started automatically during the sites initialization. That is done by adding an app setting called "AutoMigrateEPiServer" and setting the value to "true". However, until all steps have been completed, any requests will still be redirected to the migration page, where it is possible to track the progress. <br /> <br /><strong>Release Notes:</strong> <br /> <br /><a href="http://world.episerver.com/Documentation/Release-Notes/?versionFilter=7.10.0&packageFilter=EPiServer.Commerce">EPiServer.Commerce 7.10</a> <br /><a href="http://world.episerver.com/Documentation/Release-Notes/?versionFilter=7.10.0&packageFilter=EPiServer.Commerce.UI">EPiServer.Commerce.UI 7.10</a></p></p>2014-08-04T19:40:51.0000000ZBlog postRunning Commerce Manager R2 SP2 in a .NET 4.0 AppPool<p> <p>This is my first blog post, but I’ll keep this short and sweet.</p> <p>Since we don’t have any docs showing how to run Commerce Manager R2 SP2 in a .NET 4 appPool, here’s a way to do it for those running this older version of Commerce.</p> </p> <p>1. Open the B2CSampleSite.sln in Commerce Manager site folder in Visual Studio.</p> <p>2. Look at the Properties of the project and then change target framework from 3.5 to 4.0.</p> <p>3. Build the project.</p> <p>4. Go to the Commerce Manager web.config and look at this section:</p> <p><runtime></p> <p>    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"></p> <p>      <dependentAssembly></p> <p>        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/></p> <p>        <bindingRedirect oldVersion="1.0.0.0-4.0.0.0" newVersion="4.0.0.0"/></p> <p>      </dependentAssembly></p> <p>      <dependentAssembly></p> <p>        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/></p> <p>        <bindingRedirect oldVersion="1.0.0.0-3.5.0.0" newVersion="3.5.0.0"/></p> <p>      </dependentAssembly></p> <p>    </assemblyBinding></p> <p>  </runtime></p> <p>5. Change System.Web.Extensions from oldVersion=”1.0.0.0-3.5.0.0” to oldVersion=“1.0.0.0-4.0.0.0’'” and newVersion=”3.5.0.0” to newVersion=”4.0.0.0”</p> <p>6. Save the web.config and access Commerce Manager.</p> <p>That should do it!</p>2014-04-12T01:08:37.0000000ZBlog post