Sitecore Blog: @sitecorejohn blog

John West, CTO, Sitecore USA, Inc.

@sitecorejohn blog

John West, Chief Technology Officer

How Does Sitecore 6.4 Affect Sitecore.Context.PageMode and sc:pageMode()?

By John West, October 22, 2010 | Rating:  | Leave a comment

This blog post describes how version 6.4 of the Sitecore ASP.NET web CMS affects the Sitecore.Context.PageMode property and the sc:pageMode() XSL extension method that you can use to determine whether the user is in the Page Editor, and if so, the active mode (editing, debugging, or previewing).

As described in the Client Configuration Cookbook, you can use the Sitecore.Context.PageMode property from .NET or the sc:pageMode() extension method from XSL to generate different output depending on the Sitecore mode. For example, you might want to add additional information to the page if the user accesses Sitecore’s browser-based debugger.

Sitecore 6.4 obsoletes WebEdit classic mode (content markers/dots) and merges the design, editorial, and navigation modes of the Page Editor, with the following impacts:

  • 6.4 deprecates IsPageEditorClassic, which now always returns false.
  • 6.4 deprecates IsPageEditorDesigning, which now returns the same result as IsPageEditorEditing.
  • 6.4 deprecates IsPageEditorNavigating, which now always returns false.

Tags: API

*
*
*
More Posts

Learn More with Sitecore

 Newsletter
*

Atlanta Falcons | Read Case Study >

No system I’ve used in the past even approaches the flexibility, scalability and sheer power of our current Sitecore solution.

- Dan Levak, Atlanta Falcons