ling
ling  -  CMS
Mar 19, 2024
  3084
(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

Linda Mohacsi
Linda Mohacsi May 2, 2024 11:26 AM

Hi!

Looks good! But I noticed that the Swedish translations for the contentreferencelisteditor restriction texts are missing.

We run the UI in Swedish and that text comes up in English.

Is that something that you would like me to report as a bug?

Linh Nguyen
Linh Nguyen May 2, 2024 11:30 AM

Hi Linda Mohacsi,

We are aware that some texts aren't translated. We often have a bit delay with translation. But I will make sure to have the translated texts release soon.

Linda Mohacsi
Linda Mohacsi May 2, 2024 11:32 AM

Thanks Linh! Then we will be patient :) 

Jonas Carlbaum
Jonas Carlbaum May 2, 2024 12:20 PM

It's kind of a "fun fact" that swedish translations are missing these days, since the swedish traditionally was the first language you did translate, as of my memory, being around and knowing the history from ElektroPost AB => EPiServer => Optimizely... With the solid base in Stockholm... I guess swedish translations should be the bare minimum included after every review and before every release... ;) 

Robert Svallin
Robert Svallin May 2, 2024 12:37 PM

Jonas, we will try to improve.

Please login to comment.
Latest blogs
Creating an admin tool - unused assets

Let's make an admin tool to clean unused assets and see how to extend your favorite CMS with custom tools and menues! We will build a tool step by...

Daniel Ovaska | Apr 15, 2026

Running Optimizely CMS on .NET 11 Preview

Learn how to run Optimizely CMS on the .NET 11 preview with a single-line change. Explore performance gains, PGO improvements, and future-proofing...

Stuart | Apr 15, 2026 |

Your Optimizely Opal Is Probably Burning Carbon It Doesn't Need To

Four patterns Optimizely practitioners could be getting wrong with Opal agents: inference levels, oversized tool responses, missing output...

Andy Blyth | Apr 15, 2026 |

Optimizely CMS 13: A Strategic Reset for Content, AI, and Composable Marketing

Optimizely CMS 13 is not just another version upgrade—it represents a deliberate shift toward a connected, AI-enabled, and API-driven content...

Augusto Davalos | Apr 14, 2026

The 74% Problem: Why Most Companies Are Getting AI Wrong

I’ve seen this before… The pattern. The rush, the excitement, the scramble to adopt something new before anyone has stopped to ask what problem it...

Mark Welland | Apr 14, 2026

Scheduled jobs with parameters

Scheduled jobs is an integral part of most Optimizely solution but the UI has, in my opinon, always been lacking in usability and features. Earlier...

Per Nergård (MVP) | Apr 14, 2026