ContentArea property has builtin functionality of limiting content types that could be used in the editor. It’s implemented with AllowedTypes attribute. The attribute should be placed on the model and list all of available types. (more…)
16 November 2015 EPiServer, EPiServer properties 2 comments
ContentArea property has builtin functionality of limiting content types that could be used in the editor. It’s implemented with AllowedTypes attribute. The attribute should be placed on the model and list all of available types. (more…)
All model properties annotated with Required attribute will be displayed on the Content Create view. Sometimes we would like show some additional properties when creating new content. For example we have a boolean property “Show article on Start Page”. It’s not mandatory to mark it, but it’s could be a useful feature for editor if he could select it when adding new article. (more…)
2 November 2015 EPiServer 3 comments
In my previous post I described extended “All properties” content compare mode. Now I’d like to show “Compare with markup” view. It allows editor to visually check the differences between two pages. The compare page versions with markup view is similar to previous solution, but instead of comparing data on property level, whole HTML is compared.
23 October 2015 EPiServer, EPiServer properties 8 comments
Our customer editors very often use Compare Versions functionality. The CMS has workflows enabled, so when editor change the content, he need to mark it as Ready to publish. Then one of the supervisor using Tasks list gadget will approve or reject the changes. There are many editors and just few supervisors. They daily have a lot of items to approve. And usually those are really minor changes like single word, comma or typo was corrected. (more…)
11 October 2015 EPiServer, EPiServer properties 4 comments
Our customer editors complained that they have problems with using drag and drop functionality of ContentArea. They quite often use Remote Desktop connection to access the edit mode. The placeholder for ContentArea dragged element is relatively small. With the combination of RDP display lags makes using this feature difficult.
6 October 2015 Admin mode, EPiServer No comments
For one of our customer websites we developed new features, but also get rid of some unused functionality. During the implementation we had to change some properties types and move them into different models. We didn’t want to create drafts for published pages, so for saving content we used GetForceCurrentVersionSaveAction extension method.
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…)
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.
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…)
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.