World is now on Opti ID! Learn more

Ravindra S. Rathore
Jul 22, 2019
  35
(0 votes)

Disallow duplicate items in the Episerver ContentArea Property

Hey guys,

In the past, I learned about the validation attributes and to try it out I have created a validation attribute for disabling the duplicate items(page/block/media) in the ContentArea property. Yesterday some of my colleagues asked me about this so thought to write this post.

So, first of all, I have created a class called “DisallowDuplicatesAttribute” and written the below code

using EPiServer.Core;
using EPiServer.DataAbstraction;
using EPiServer.Framework.Localization;
using System;
using System.Collections.Generic;
using System.ComponentModel.DataAnnotations;
using System.Linq;
using System.Web;

namespace Test.Infrastructure.Cms.Models.Attributes
{
    [AttributeUsage(AttributeTargets.Property)]
    public sealed class DisallowDuplicatesAttribute : ValidationAttribute
    {
        protected override ValidationResult IsValid(object value, ValidationContext validationContext)
        {
            var propertyDefinitionRepository = EPiServer.ServiceLocation.ServiceLocator.Current.GetInstance<IPropertyDefinitionRepository>();
            var propertyDefinitionId = ((PageData)validationContext.ObjectInstance).Property[validationContext.MemberName].PropertyDefinitionID;
            var propertyDefinition = propertyDefinitionRepository.Load(propertyDefinitionId);
            propertyDefinition.LocalizationService = LocalizationService.Current;

            if (HasDuplicateItems(value as ContentArea))
            {
                return new ValidationResult(string.Format("Duplicate items are not allowed in {0} Property",
                    new object[] {validationContext.MemberName}));
            }

            return ValidationResult.Success;
        }

        bool HasDuplicateItems(ContentArea contentArea)
        {
            if (contentArea == null || contentArea.IsEmpty)
                return false;
            var contentAreaItems = contentArea.Items;
            if (contentAreaItems == null || !contentAreaItems.Any())
                return false;

            List<int> items = new List<int>();

            foreach (var contentAreaItem in contentAreaItems)
            {
                if (items.Contains(contentAreaItem.ContentLink.ID))
                    return true;

                items.Add(contentAreaItem.ContentLink.ID);
            }

            return false;
        }
    }
}

Now created a new PageType called “TestPage” and applied the newly created attribute on the PageContent contentArea property.

[ContentType(DisplayName = "Test Page", GUID = "133523e4-4da1-49e9-a49d-94a9c9b1d413", Description = "Test Page")]
    public class TestPage: BaseFeedPage
    {
        [DisallowDuplicates]
        [CultureSpecific]
        [Display(
            Name = "PageContent",
            Description = "The page content will be used to show page content",
            GroupName = ApplicationConstants.PropertyGroupNames.Content,
            Order = 100)]
        public virtual ContentArea PageContent { get; set; }
    }

Now if you login into Episerver and then try to drag and drop the same item twice then it will not allow you to publish the page as well as it will give you an error and allow you to publish the page.

Thanks.

Ravindra

Jul 22, 2019

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |