Routing to the Product Detail Page is one of the most important components of our EPiServer 7 MVC and Commerce integration. The routing we create will define the primary path to the product’s information. Since we are not going to be creating page instances for each product, we need to have some way to determine which
Entry should be displayed.
This is part of a multi-post series regarding integrating EPiServer Commerce 1 R3 with an EPiServer 7 MVC site. In this post, I’ll discuss the different routing methods to the Product Detail Page.More ››
Over the last couple of months, we’ve been working on integrating EPiServer Commerce 1 R3 with an EPiServer 7 MVC site. Unfortunately, this is not the most straightforward process, as Commerce 1 R3 is not fully supported with EPiServer 7 sites using MVC. After a lot of trial and error, we’ve developed a workable solution to getting both to play nicely with each other.
This is part of a multi-post series. In this post, I’ll briefly discuss setting up the solution, then cover the basic components needed for our EPiServer 7 MVC and Commerce 1 R3 site.More ››
I’ve recently been working on translating text that is displayed along with an XForm property. Since the localizations that are shipped with EPiServer 7 are now embedded in the assemblies, it’s not as easy as searching through an XML file for the keys you need to override. So, as a reference, here are the system localization keys related to XForms that are embedded into EPiServer 7.More ››
When developing an EPiServer 7 site (or really any site, for that matter), making a link to a page is one of the most common things you’ll do. So, I thought I’d do something a little more basic and explore how to handle this task in your front-end page and block templates, specifically using MVC Razor views. In this post, we’ll look at what you can currently use to create a link to a page, then I’ll introduce some extension methods that you can use to give yourself a little more flexibility in your MVC view.More ››
The creation and editing of content for multiple language sites in EPiServer 7 has recently become a topic of conversation in some of our projects. We occasionally receive feedback from our clients who are looking for ways to reduce the amount of time it takes to enter content, while also being consistent with the page and block layout.
One big change with the new Edit Mode in EPiServer 7, which was available in EPiServer 6 (and technically is still available in the old Edit Mode), is that feature to compare the language branches for a page side-by-side has been removed. This was useful for editors who need to keep the content for pages consistent between each language branch, as it allowed them to easily compare the different language branches.
So to help this, we created a property attribute called
[AutoPopulateLanguageBranch]. Whenever a editor translates a page or block, this copies the values from the master language branch to the new language branch for the decorated page or block type properties. This keeps the content consistent between the language branches, which, at the same time, helps speed up the process of entering content.