World is now on Opti ID! Learn more

Grzegorz Wiecheć
Sep 11, 2017
  2277
(0 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

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |