Linus Ekström
Feb 25, 2014
  5904
(1 votes)

Tweaking the settings header in EPiServer 7.5

My collegue Kalle Ljung wrote a blog post about how to tweak the settings header that was added in an UI update last year (http://world.episerver.com/Blogs/Kalle-Ljung/Dates/2013/10/Moving-built-in-properties-to-the-settings-header-in-EPiServer-7-CMS/). Back then he wanted me to have a look at the code to see if there was any room for improvement and there sure was…though it required some stuff in EPiServer 7.5 that was yet to be released. So, now that EPiServer 7.5 has been out for quite a while, I though I’d post a simplified pattern to accomplish this. The code below shows how to move the built in category property into the settings header.

   1: using System;
   2: using System.Collections.Generic;
   3: using EPiServer.Core;
   4: using EPiServer.DataAbstraction;
   5: using EPiServer.Shell.ObjectEditing;
   6: using EPiServer.Shell.ObjectEditing.EditorDescriptors;
   7:  
   8: namespace Samples
   9: {
  10:     [EditorDescriptorRegistrationAttribute(TargetType = typeof(ContentData))]
  11:     public class SiteMetadataExtender : EditorDescriptor
  12:     {
  13:         public override void ModifyMetadata(ExtendedMetadata metadata, IEnumerable<Attribute> attributes)
  14:         {
  15:             foreach (ExtendedMetadata property in metadata.Properties)
  16:             {
  17:                 if (property.PropertyName == "icategorizable_category")
  18:                 {
  19:                     property.GroupName = SystemTabNames.PageHeader;
  20:                     property.Order = 9000;
  21:                 }
  22:             }
  23:         }
  24:     }
  25: }
Feb 25, 2014

Comments

Feb 25, 2014 06:57 PM

Hi,

ExtendedMetadata doesn't contain PropertyName and Order. I have EPiServer.Shell.dll, v7.5.1002.0, am I missing something here?

Feb 26, 2014 07:31 AM

Thats odd. Both these properties are inherited from the class ModelMetadata from the assembly System.Web.Mvc.

Martin Pickering
Martin Pickering Feb 26, 2014 11:17 AM

Try...

[EditorDescriptorRegistration(TargetType = typeof (ContentData))]
public class SiteMetadataExtender : EditorDescriptor
{
public override void ModifyMetadata(ExtendedMetadata metadata, IEnumerable attributes)
{
var property = metadata.Properties.FirstOrDefault(p => p.PropertyName == "icategorizable_category") as ExtendedMetadata;
if (property == null)
{
return;
}
property.GroupName = SystemTabNames.PageHeader;
property.Order = 9000;
}
}

Mari Jørgensen
Mari Jørgensen Feb 26, 2014 12:14 PM

The original blog post is titled "Moving built-in properties..." - I assume this can be done for all properties?

Feb 26, 2014 01:56 PM

@Mari: Sure, the settings header is just a grouping of properties that has a different appearance than the tabs.

Feb 26, 2014 02:07 PM

I had not referenced System.Web.Mvc, that was the problem. Thank you!

Please login to comment.
Latest blogs
Multiple Anonymous Carts created from external Head front fetching custom Api

Scenario and Problem Working in a custom headless architecture where a NextJs application hosted in Vercel consumes a custom API built in a...

David Ortiz | Oct 11, 2024

Content Search with Optimizely Graph

Optimizely Graph lets you fetch content and sync data from other Optimizely products. For content search, this lets you create custom search tools...

Dileep D | Oct 9, 2024 | Syndicated blog

Omnichannel Analytics Simplified – Optimizely Acquires Netspring

Recently, the news broke that Optimizely acquired Netspring, a warehouse-native analytics platform. I’ll admit, I hadn’t heard of Netspring before,...

Alex Harris - Perficient | Oct 9, 2024 | Syndicated blog

Problem with language file localization after upgrading to Optimizely CMS 12

Avoid common problems with xml file localization when upgrading from Optimizely CMS 11 to CMS 12.

Tomas Hensrud Gulla | Oct 9, 2024 | Syndicated blog