Try our conversational search powered by Generative AI!

Linh Nguyen
Mar 19, 2024
(3 votes)

Improve user experience with restriction information

In EPiServer.CMS.UI 12.28.0, an improvement for restriction information is added.

Previously the restriction information takes quite a lot of space, especially for big sites with a long list of restricted types.

This new improvement reduces the space significantly while still gives editors information about restricted types they need to know.



Users can expand the list to view all restricted types, and collapse it if they want.

Mar 19, 2024


Mike Malloy
Mike Malloy Mar 19, 2024 07:21 PM


Can you improve the users experience by doing this one too?

Linh Nguyen
Linh Nguyen Mar 19, 2024 10:38 PM

Mike Malloy The suggestion sounds reasonable. But it will need to go through our product manager to evaluate the design and prioritise the work. Thank you for bring it up!

Mark Stott
Mark Stott Mar 20, 2024 10:44 AM

Hello Linh,

This is a very nice quality of life change.  I've seen and implemented the usage of interfaces to classify block types to make block restrictions easier to manage across the solution.  Examples being blocks that have interfaces of IFullWidthBlock, ITwoThirdsBlock, IHeroBlock etc.  It allowed you to apply restrictions very easily and to include a new block to the LeftContent areas across all templates very quickly:

        Name = "Main Content",
        Order = 20)]
    public virtual ContentArea? LeftContent { get; set; }

        Name = "Main Content",
        Order = 20)]
    public virtual ContentArea? LeftContent { get; set; }

The previous iteration of the restrictions hint text wasn't terribly helpful as it said "You  can add these content types: block".  I can see this updated version works a lot nicer, however you wouldn't want the "undefined" part of this.

Please note in this quick example I only have one block using the interface.

Thank you :)

Linh Nguyen
Linh Nguyen Mar 20, 2024 11:28 AM

Thank you, Mark Stott! We do have a bug for it (CMS-32870), hopefully we can fix it soon.

Mark Stott
Mark Stott Mar 20, 2024 11:35 AM

Thank you Linh :)

Linh Nguyen
Linh Nguyen Mar 20, 2024 01:37 PM

Here is the bug link, it is recently set public

Please login to comment.
Latest blogs
The A/A Test: What You Need to Know

Sure, we all know what an A/B test can do. But what is an A/A test? How is it different? With an A/B test, we know that we can take a webpage (our...

Lindsey Rogers | Apr 15, 2024

.Net Core Timezone ID's Windows vs Linux

Hey all, First post here and I would like to talk about Timezone ID's and How Windows and Linux systems use different IDs. We currently run a .NET...

sheider | Apr 15, 2024

What's new in Language Manager 5.3.0

In Language Manager (LM) version 5.2.0, we added an option in appsettings.json called TranslateOrCopyContentAreaChildrenBlockForTypes . It does...

Quoc Anh Nguyen | Apr 15, 2024

Optimizely Search & Navigation: Boosting in Unified Search

In the Optimizely Search & Navigation admin view, administrators can set a certain weight of different properties (title, content, summary, or...

Tung Tran | Apr 15, 2024

Optimizely CMS – Getting all content of a specific property with a simple SQL script

When you need to retrieve all content of a specific property from a Page/Block type, normally you will use the IContentLoader or IContentRepository...

Tung Tran | Apr 15, 2024

Join the Content Recommendations Work Smarter webinar May 8th 16.00-16.45 CET with expert Aidan Swain

Learn more about Content Recommendations, with Optimizely’s very own Senior Solutions consultant, Aidan Swain . He will discuss best practices and...

Karen McDougall | Apr 12, 2024