Take the community feedback survey now.

Grzegorz Wiecheć
Sep 11, 2017
  7065
(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
Automating Cleanup Tasks with Optimizely Scheduled Jobs

Scheduled jobs in Optimizely CMS are a powerful way to automate any background tasks like content cleanup, indexing, or reporting. I created a simp...

Madhu | Nov 29, 2025 |

Implementing Custom Line Item Pricing in Optimizely Commerce 14

In many enterprise commerce implementations, business users often need the flexibility to override product pricing at the cart level - especially...

Sunil | Nov 28, 2025

Using Okta and OpenID Connect with Optimizely CMS 12

Modern CMS solutions rarely live in isolation. Your editors already log into other systems with SSO, and they expect the same from Optimizely CMS. ...

Sanjay Kumar | Nov 28, 2025

Optimizely Opal — working notes from me

A short, practical orientation I use when introducing Opal. Lately I’ve been helping customers and developers understand Opal, and I kept finding...

Pär Wissmark | Nov 26, 2025 |