Playing with Fire - Part 2, updates for DbLocalizationProvider for EPiServer

Story continues with fire and localization cases inside EPiServer sites. This time smaller update for database localization provider, but still - worth sharing. Support for Custom Attributes Currently database provider supports and understands just a few System.Attribute child classes: [LocalizedModel] - this is main marking attribute for making sure that provider resource sync process will pickup decorated class and scan resources there; [LocalizedResource] - this is similar as LocalizedModel, but makes sure that resources discovered at this class will take localized resource semantics. Read more here about differences; [ResourceKey]…

Keep reading

Playing with Fire - Localized EPiServer View Models

Recently released driven localization provider for EPiServer had main focus on more complex view models along the other smaller bug fixes and features. And specifically - there were few unsupported scenarios for the view models with base/parent class. Here is the list of all new features in v2.1. Extract Abstractions Until now, if I do need to decorate some of the resources that are located in some core area assembly - you need to reference DbLocalizationProvider library that had some undesired dependencies (for instance, why do I need…

Keep reading

ImageResizer Plugin for EPiServer v10

ImageResizer.Net Plugin for EPiServer v10 is released. ImageResizer.Plugins.EPiServerBlobReader got version 5.0.0. "Old" NuGet package for EPiServer 9.x is updated with upper version constraint fix. Now plugin package v4.2 has upper EPiServer version set under v10 exclusive. Note About Image Preview That was quite "interesting" experience to realize changes in EPiServer.Web.BlobHttpHandler. This is eventually the guy who is responsible for returning Blob back to the client. A bit more details below. Background First of all a bit background. Images in EPiServer EditUI…

Keep reading

Baking Round Shaped Software - Mapping to the Code

This part of the round shaped software blog posts as promised will be about mapping the theoretical terms and ideas mentioned in previous post to the actual code fragments and components. Application for the Post To move further and map theory to the code, I've created really simple sample application for managing the users. To demonstrate mediator internals and round shaped architecture - we will stick with hand crafted mediator. Mediator will be able to handle commands, queries and events. In the application you can: enlist existing users (for the…

Keep reading

Baking Round Shaped Software

This is the story how I discovered clean, understandable and maintainable software architecture. Why it's round shape and not pentagon, hexagon or any other *-gon shape? In this blog post I'll guide you through my journey. This part will cover theoretical side. Next blog post will map it to the code. Classical Architecture Agree that we all have been taught about N-tier/layer application software in high schools, universities or between the pages of some software development magazine?! Where order and most importantly dependency direction was stressed as one of…

Keep reading

Configure EPiServer Media Auto Publish on Upload

In this post we will enhance media auto-publish option to gain more control over what's going to be automatically published and what will stay for manual publishing. EPiServer gives site admins option to configure whether media file gets automatically published when uploading to Blob storage. This is very nice, but the problem is - this setting is global. It means either all media files get automatically published, or none - on/off. For one of our customers requirement was to delay publish only certain file extensions (usually .pdf files with…

Keep reading

Apply DisplayOptions for EPiServer.Forms Elements

Apply DisplayOption for EPiServer.Forms Elements Would you like to use this feature also for EPiServer.Forms? In this blog post I'm gonna show you how to do that. Background It's really great to see platform evolving and adding new features. But unfortunately - I must say that EPiServer.Forms are pretty close for modification (which is good) but at the same time - not so open for extensions, that's why we will need to modify some of the built-in templates to get this done. Getting Started First of all,…

Keep reading

EPiServer Twitter Bootstrap Content Area Renderer Updates

Here comes small updates for the Content Area renderer in the latest version: Now EPiServer.Forms are supported Possibility to have your own Css classes DisplayOption is now available in block template as well (if needed) Some smaller bug fixes Naming Challenges As you might know - I'm still struggling with naming of this package. Originally it was planned to be as Twitter Bootstrap Content Area Renderer, but apparently over time package feature set deviated from original idea as now package gives so much more than just adding necessary Css…

Keep reading

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