You can learn all about my story and the challenges I face during my professional life as an Episerver Architect and Tech-lead. Feel like home and Welcome
With the release of Episerver’s newest marketing platform and the enhanced order system, forecasting of promotion values via order experiments are now a reality. It has always been difficult to indicate the promotional value gained of doing a given action – e.g. “You qualify for free shipping if you buy this item”. Previously, doing such this was difficult, but the combination
One of Episerver’s latest releases introduced a valuable tiered pricing model, which allows marketers to differentiate Episerver Commerce pricing according to a set of built in criteria. Out of the box, Episerver now supports to target prices for: all customers an individual customer a price group Thinking of specifically business to business (B2B) e-Commerce, relying on a tiered pricing model is essential.
After installing Episerver’s ASP.NET Identity implementation, via EPiServer.Cms.UI.AspNetIdentity and Cookie Authentication, you’ll have to seed at least one user to take advantage of Episerver’s administration or authoring capabilities. Seeding users, in the Alloy example site, are managed by a FilterAttribute, which ensures requests get’s routed by a registration controller for the initial user setup. Instead of relying on that entire mechanism, you can just
Routing is the way an ASP.NET MVC web application directs a web request to a given controller. ASP.NET MVC and Episerver has a dynamic content map (through routes in a route table) that ensures a given URL – e.g. http://mywebsite.com/article-1 – gets processed by a controller with respect to a specific content instance. It’s all something that’s very fundamental in both platforms. Some
Episerver relies on magic paths (via naming conventions) to enable developers to place custom plugin extensions in the out-of-the box Episerver Shell. Over time, most Episerver developers has decompiled Episerver’s code to recollect these conventions. For that reason, the intent with this post is to outline the common paths, which are useful in most scenarios. First off, if you aren’t familiar with
Episerver Commerce relies on expandable enumerations to create Business Foundation definitions of important entities – such as contact groups and credit card options. You may be thinking, what does that mean? From a helicopter perspective, it’s needed because Episerver, by default, ships with a definition of entities. Let me provide an example. Contact groups, which out-of-the-box maps to Customer, Partner and Distributor, are defined via
Episerver’s recent release of Episerver CMS 10 requires ‘add-on contributors’ to revisits their code to mitigate potential breaking changes, which may have negatively impacted the released feature. To that note, I am happy to announce that all my add-ons now have been updated to support Episerver CMS 10. What’s new in the recently released versions? Nothing but Episerver compatibility has
Very recently, Episerver released a new major version by introducing Episerver CMS 10 and Episerver Commerce 10. When major versions are released, we immediately start upgrading some of our sandbox platforms. While upgrading these platforms to Episerver Commerce 10, we stumped upon a interesting exception that I believe could confuse for some developers. Mediachase.Commerce.Customers.Plugins.AutoInstallMetaDataModule must be a valid class implenting
Working with multi lingual formatting is fairly simple in Episerver CMS. It’s simply a matter of relying on a set of key implementations, such as ContentLanguage.PreferredCulture or CultureInfo.CurrentUICulture, when explicitly formatting an object or struct to it’s localized representation. One detail, which I’ve seen being left out by developers, is the fact that code executed in the context of an
ASP.NET MVC and the Razor Engine that is used to render Episerver content is, in combination, an excellent text and HTML template-rendering engine. Together, they make it easy to merge text, model data, and code to produce HTML output. Merging these three parts, through a WebApi, may seem odd to some people.. but it can indeed be beneficial in some (rare)