Blogg
Välkommen till vår blogg. Här delar vi med oss av vår specialistkunskap och våra erfarenheter kring e-handelslösningar. Vi bloggar om handel, tech, trender, strategi, marknadsföring, UX, nyheter och mycket annat.
Content Area - under the Hood, part II
This is second post in series of EPiServer Content Area feature. This time we will take a look at how render templates are selected.
Category selection for multiple sites in EPiServer enterprise solutions
This is a quick tip filed under the "Enhance the user experience for web editors" category. In an enterprise EPiServer solution with multiple sites it's a common scenario to have separate category structures for each site. This simple editor descriptor makes sure the web editor for a specific site only sees and can select the relevant categories.
Content area - under the hood part I
Lately I was visiting and revisiting content area, code and functionality around this feature in EPiServer and decided to revisit it once again and take a closer look at what’s really inside. So the blog post is not about what content area is, but how it works, how responsible party for rendering and templating is selected when EPiServer needs to render this one of the most powerful content editing feature.
New version of Geta oEmbed
Another one of our popular modules has been updated to .NET 4.5 and EPiServer 8. It is still backward compatible with the old custom property and dynamic content. In the new version you'll now find a block that you can easily use as both local and shared.
New version of Geta Tags
The new version now finally supports other types of content like MediaData, BlockData and CatalogContent in addition to PageData.
Moving from EPiServer CMS to EPiServer Commerce as a Developer
Are you starting your first EPiServer Commerce project? What are the major differences between the products? What new challenges do you face in an ecommerce project vs a regular website project?
Simple URL keeper for EPiServer
Here's a little code sample that is useful for when you need to perform an automatic redirect after content is moved in EPiServer, to avoid getting a bunch of 404's.
EPiServer Commerce route messing with block preview
Yesterday we discovered an issue with our block preview implementation in a project we are currently working on, running EPiServer Commerce version 8.2.1. The problem was that all blocks got previewed in the master language (english in our case). When we clicked a property the correct translation was loaded, but it was very confusing for the editors so we had to fix it.