The PropertyList is the new property introduced in EPiServer 9. It allows to use generic list on content model. List item property could be described with the same attributes as regular model properties. For example if we annotate property with Display attribute and set name, then name will be used as grid column header and as a label on the edit form. If we set the UiHint, like StringList then editing form will use selected editor. (more…)
Page & Asset trees synchronization
18 December 2015 EPiServer No comments
Page tree and Asset tree are kept separate and that’s definitely a good thing. It’s totally up to the editor on how to structure both pages and folders.
However in big sites that may soon become problematic simply because pages are strictly dependant on the files that are displayed in its body. It’s very important to make the files easy to find and reuse later on. (more…)
SEO friendly list using KnockouJs
12 December 2015 EPiServer No comments
In many scenarios we need to display page children as a list. Usually the list is not just a static HTML. It has to support additional features like sorting, filtering or switching between different item layouts. (more…)
Changing root for Content References property
4 December 2015 EPiServer, EPiServer properties No comments
EPiServer has a builtin Content References list property which is used to collect list of pages, blocks, or media. To add new reference, editor could D&D content or click Browse. Clicking Browse button will show dialog with content tree. (more…)
Sort order of module dependencies
EPierver has build-in initialization mechanism implemented with Initialization Modules. It’s used to initialize internal code as well as custom functionalities. All classes marked with InitializableModule attribute that implements IInitializableModule interface will be used to setup CMS. (more…)
How to show Allowed types on Content Area
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…)
Show additional properties on content creation
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…)
Compare page versions with markup
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.
Compare properties with markup
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…)
Increasing the drop area for ContentArea
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.
