EPiServer DbLocalizationProvider - fresh 2.0 is out!

Why? You might ask, but changes I guess is the only constant thing in this industry. DbLocalizationProvider is witnessing new version and some cool features covered in more details below. Also internally provider survived quite huge refactoring activities, while I was redesigning from central services and repositories to more granular command and queries. But that’s the story for another blog post. New Features in 2.0 Here goes the list of new features available in version 2.0. List is not sorted in any order. Translate System.Enum It's…

Keep reading

Specify Default DisplayOption in the Content Area

Time to time when working on various projects we come across requirement to control somehow which DisplayOption will be selected as default, once content is placed inside particular ContentArea. As most of our projects are running under Twitter Bootstrap system - this is ideal feature request for EPiServer Bootstrap Content Area plugin. As I'm always trying to be developer friendly - I would like to be able to define these default display option rules in the code. And finally version 3.3 got these features. Default DisplayOption for Block So…

Keep reading

Db Localization Provider - Part 2: Configuration and Extensions

In this blog post we are going through some of the configuration options available for DbLocalizationProvider for EPiServer. You might be wondering what can and should be configurable for localization provider in the context of the EPiServer, but there are few things. Configuration Setup for Libraries Developing libraries as an author you always need to keep in mind your consuming projects and usage scenarios, need to think about how your library will be setup, used and extended if needed. I really liked Mark Seeman's blog posts about developing libraries and…

Keep reading

Db Localization Provider - Part 1: Resources and Models

Resources and Models This is first post about more details inside DbLocalizationProvider for EPiServer. In this post we will go through localization approach for arbitrary resources that can be used from the code to provide some message to the user or anywhere else where localization is required. Another type of localization target is model. By model we can assume any kind of class that is used to render a page, or collect posted back data from the user. Usually models are decorated with various data annotation attributes indicating underlying data…

Keep reading

EPiServer Database Localization Provider - Released!

Background Why on the Earth I would ever want to change my EPiServer localization system? EPiServer provides you with a way to organize localization resources using set of Xml files. Working on multi-lingual projects and seeing how support teams are struggling and bored with changing resource value - thought: there has to be space for improvement.. We don't need localization Lately I've been working more and more with international sites where single language is not the case at all. Localization is not needed - because we have only single language.…

Keep reading

Create Your Library Configuration API for EPiServer

Time comes when you need to extent EPiServer functionality by providing your own library with new or modified functionality. I'm big fan of configuration via code. Which may give you possibility to configure some features with LambdaExpression, e.g. () => true to ensure that you are able to set feature's state on or off during runtime. This opens up quite interesting scenarios that I'm going to cover soon enough in other blog post. Anyway, what I'm looking for is to make sure that my library consumers can do something like…

Keep reading

<head> driven by Content Area

For some powerful sites and editors sometimes it's wise to give them power to manipulate some stuff in <head> area. One of the simplest way to give editors this possibility is to create ContentArea where editors could create particular set of available blocks that would output themselves between <head> elements. By default EPiServer will generate wrapping element around content area (div tag name is actually controllable as well, more info here): @Html.PropertyFor(m => m.PageHeaderArea) Resulting in: <div> <!-- CA wrapper…

Keep reading

Year in Review

This is perfect timing for a busy people like us in IT industry to stop by and look back on the path that has been walked and some good things accomplished. Below is a short summary of things that I hope you will find useful and beneficial in your own way. This is an experience had this year within my lovely industry, company I'm working in and with people around me. Github Move I was using git and GitHub particularly as open source project repository quite a while. Once you…

Keep reading

Update EPiServer Commerce SKU price in lightweight way - Service Api

Lately I've been playing around EPiServer Service API. I found these interfaces really simple and lightweight way to manipulate with your catalog's content and characteristics of the items in the catalog. This blog post will show you the way how you can update SKU prices via these services using REST client library called "Refit". There are tons of various style and type REST client frameworks for accessing and consuming REST services. I do not have any interest in promoting "Refit" here, but found it really convenient way to work with.…

Keep reading

Row support added to Bootstrap ContentArea

With helpful support from Huilaaja (@huilaaja) Bootstrap aware ContentArea renderer (or in other words - EPiBootstrapArea) got row markup support. Originally row support documentation for ContentArea you can find in author's blog post. With author's permission now row support is added to Bootstrap aware content area renderer package. Enable Row Support For backward compatibility and general idea of Bootstrap content area renderer - row support is disabled by default. You need to enable it explicitly. If you want to enable row markup support "globally" on every content area, you should…

Keep reading

What's new in FeatureSwitch?

It's been while since last FeatureSwitch library release. Just pushed out a bit of stuff held under the hood. Some of them are requested by my lovely consumers :) Here are enlisted some of the latest version features in the library. 1) EPiServer Site Strategy. Now you can use EPiServer's site strategy to enable or disable feature per particular EPiServer site. With example below feature ThisFeatureIsOnlyForSite1 will only be enabled if request is made against site named "Site1", otherwise - feature will be disabled. [EPiServerSite(Key = "Site1")] public class ThisFeatureIsOnlyForSite1 : BaseFeature…

Keep reading

Creating EPiServer Site Menu out of Block Driven Content

For one of our great customers we needed to make site out of just only few pages and lots of blocks. It reminds sort of single page application, just there is no client-side behavior as original SPA projects have. Anyway, in the middle of the project we came to task to make site menu. As we know it's quite easy to build site menu out of the pages and subpages and children pages of these subpages. But this time, we had almost no page structure in CMS, but instead, we…

Keep reading

Asp.Net Mvc Areas - Packed as NuGet

If you would want to add Asp.Net Areas support to your EPiServer site, you would need to copy some files from my previous blog post. Copying files from someone's blog posts seems to be good idea, but it's a bit problematic in case of updates or changes. If so, then we share common vision that by installing NuGet package, your project gets up-to-date support for Asp.Net Mvc Areas. For that reason I packed up Asp.Net Mvc Areas support into NuGet package, for you guys. You may just…

Keep reading

Asp.Net Mvc Areas in EPiServer - Part 2

Asp.Net Mvc Areas is a great way to organize and structure your EPiServer site. Once you have multi-tenant site where the same EPiServer installation with the same set of libraries, styles, script set and other assets is handling more than single site - Asp.Net Mvc Areas become really handy to group particular site's specific assets and other stuff together under single folder. This also gives developers more obvious and more clear picture of the project setup. However we all know that there is no native support for Asp.…

Keep reading

Content Area - Under the Hood, Part 3

This is last blog post in series under the hood of Content Area. In this blog post we will take a look at how and what exactly could be customizable while content area is being rendered. Where and how developer can hook in, what can be overridden and controlled. Parts in this series: – Part 1: Registration and Discovery – Part 2: Template Selection – Part 3: Extensibility Overview Following parts and pieces can be customizable, changeable or replaced by other code completely: Change renderer - It's possible to change they guy who…

Keep reading