Try our conversational search powered by Generative AI!

Linh Nguyen
Mar 19, 2024
  348
(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.

Before:

Now:

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

Mar 19, 2024

Comments

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

Thanks.

Can you improve the users experience by doing this one too?
https://feedback.optimizely.com/ideas/CMS-I-410

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:

    [Display(
        Name = "Main Content",
        Order = 20)]
    [AllowedTypes(typeof(ITwoThirdsBlock))]
    public virtual ContentArea? LeftContent { get; set; }

    [Display(
        Name = "Main Content",
        Order = 20)]
    [AllowedTypes(typeof(IOneThirdBlock))]
    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 https://world.optimizely.com/support/Bug-list/bug/CMS-32870

Please login to comment.
Latest blogs
Azure AI Language – Extractive Summarisation in Optimizely CMS

In this article, I demonstrate how extractive summarisation, provided by the Azure AI Language platform, can be leveraged to produce a set of summa...

Anil Patel | Apr 26, 2024 | Syndicated blog

Optimizely Unit Testing Using CmsContentScaffolding Package

Introduction Unit tests shouldn't be created just for business logic, but also for the content and rules defined for content creation (available...

MilosR | Apr 26, 2024

Solving the mystery of high memory usage

Sometimes, my work is easy, the problem could be resolved with one look (when I’m lucky enough to look at where it needs to be looked, just like th...

Quan Mai | Apr 22, 2024 | Syndicated blog

Search & Navigation reporting improvements

From version 16.1.0 there are some updates on the statistics pages: Add pagination to search phrase list Allows choosing a custom date range to get...

Phong | Apr 22, 2024

Optimizely and the never-ending story of the missing globe!

I've worked with Optimizely CMS for 14 years, and there are two things I'm obsessed with: Link validation and the globe that keeps disappearing on...

Tomas Hensrud Gulla | Apr 18, 2024 | Syndicated blog

Visitor Groups Usage Report For Optimizely CMS 12

This add-on offers detailed information on how visitor groups are used and how effective they are within Optimizely CMS. Editors can monitor and...

Adnan Zameer | Apr 18, 2024 | Syndicated blog