Month: September 2015

Content references list with preview

30 September 2015 EPiServer, EPiServer properties 1 comment

Few months ago I prepared ContentArea property with image thumbnails and image preview support. The new EPiServer has Content References list property which already implements thumbnails for list items. In Content references list with preview property I tried to extend standard editor and add support for image preview as well. (more…)

How to hide Display Options for specific ContentArea

21 September 2015 EPiServer, EPiServer properties 1 comment

The “Display Options” is a global settings list defined in DisplayOptions service. It’s used together with ContentArea property to set the layout for the content items. Sometimes editor should not be able to set options on each ContentArea because in some cases they might not be used in the template implementation. Last week I prepared a code for hiding Display Options for specific ContentAreas.


EPiServer Search diagnostic tool

11 September 2015 Admin mode, EPiServer 2 comments

EPiServer Search is integrated with CMS build-in search feature. It’s a very useful functionality that allows users find any content across whole website.

For many times I saw several forum threads and blog posts about solving the problems related to the installation of this service. In recent projects in which I was involved we faced some problems regarding empty results. (more…)

Comparing list properties

6 September 2015 EPiServer, EPiServer properties 2 comments

Probably in every EPiServer project there will be a need to store a list of links to your content pages. EPiServer.CMS.UI 8.6.0 introduced a new multiple ContentReference property. Usually we could use a single property to store a collection of links. For example when building a media slideshow or when displaying links in a site footer. Using EPiServer there are several possibilities of implementation. Until now there were two built-in properties – ContentArea and LinkItemCollection, and the new multiple ContentReference is yet another interesting solution. I’ll try to compare those properties.