A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Grzegorz Wiecheć
Sep 11, 2017
  7097
(12 votes)

Sticky View Mode

In previous Episerver versions, a default view for the current content type was loaded when you navigated the content tree. By using a UIDescriptor, it was possible to change the default view for a specific ContentType. For example, in Alloy demo source code, ContainerPage has a default view set to AllPropertiesView.

[UIDescriptorRegistration]
public class ContainerPageUIDescriptor : UIDescriptor<ContainerPage>
{
    public ContainerPageUIDescriptor(): base(ContentTypeCssClassNames.Container)
     {
         DefaultView = CmsViewNames.AllPropertiesView;
     }
}

As a part of Episerver 10.11.0, we are introducing a new feature called “Sticky View mode”.

“Sticky” means that, when navigating the content tree, the previously used view is loaded instead of the default view. This functionality is enabled for every content type by default.

Whenever you change the view using the toggle button, the currently selected view is saved in the local storage and is used when you change the context.

Image sticky view mode.gif

If a saved view is not available for the current content type, then the default view for that content is loaded.

Disabling Sticky View mode

Sticky View mode can be disabled per content type. In UIDescriptor, there is new property EnableStickyView. If you want to turn the feature off,  this property should be set to false.

For example, if you would like to force the All properties view to be the default view for StartPage, then EnableStickyView should be false and DefaultView should be set to AllPropertiesView.

[UIDescriptorRegistration]
public class StartPageUIDescriptor : UIDescriptor<StartPage>
{
    public StartPageUIDescriptor(): base(ContentTypeCssClassNames.Container)
    {
        DefaultView = CmsViewNames.AllPropertiesView;
        EnableStickyView = false;
    }
}
Sep 11, 2017

Comments

Luc Gosso (MVP)
Luc Gosso (MVP) Sep 11, 2017 02:59 PM

This is welcomed! thx

Erik Henningson
Erik Henningson Sep 13, 2017 10:24 AM

It's the small things, like this, that makes you more productive, and love the CMS.
Please also make MenuPin a part of the main product + something like this :-)

Aaron Mitchard
Aaron Mitchard Nov 1, 2017 12:18 PM

Really good update, this has bugged me for a while! Agree with the above comment as well about MenuPin :)

Jonas Boman
Jonas Boman Dec 8, 2017 08:48 AM

Best feature since sliced bread!

Please login to comment.
Latest blogs
Looking back at Optimizely in 2025

Explore Optimizely's architectural shift in 2025, which removed coordination cost through a unified execution loop. Learn how agentic Opal AI and...

Andy Blyth | Dec 17, 2025 |

Cleaning Up Content Graph Webhooks in PaaS CMS: Scheduled Job

The Problem Bit of a niche issue, but we are building a headless solution where the presentation layer is hosted on Netlify, when in a regular...

Minesh Shah (Netcel) | Dec 17, 2025

A day in the life of an Optimizely OMVP - OptiGraphExtensions v2.0: Enhanced Search Control with Language Support and Synonym Slots

Supercharge your Optimizely Graph search experience with powerful new features for multilingual sites and fine-grained search tuning. As search...

Graham Carr | Dec 16, 2025

A day in the life of an Optimizely OMVP - Optimizely Opal: Specialized Agents, Workflows, and Tools Explained

The AI landscape in digital experience platforms has shifted dramatically. At Opticon 2025, Optimizely unveiled the next evolution of Optimizely Op...

Graham Carr | Dec 16, 2025