Per Nergård (MVP)
OMVPSaaS CMS Developer CertificationCommerce Connect 13 Developer Certification +2
Dec 7, 2010
visibility 7150
star star star star star
(0 votes)

Quick publishing in edit mode

In CMS 6 EPiServer introduced a nice new functionality for the not so frequent editors. If you don’t know what it is read more about it here.

It’s real simple to setup with only some minor configuration in EPiServer.config and you’re ready to go. The quick guides are accessed from the online center via the Quick Links gadget.

It works great but I think it’s a bit limiting that you need to specify the parent page where each guide will publish it’s pages. And what about the editors that are more advanced but still would benefit from using quick publishing but would like to do it from within edit mode?

It’s the Application\UI\CMS\Edit\NewPage.aspx that creates the table with available page types for creation.

So I did my own version of the codebehind and changed the inherits attribute in the aspx to point to my custom class instead.

Now the create links for the page types where the page type name exist in a page guide section will start up in quick publish mode instead of regular edit mode.

It looks like this for the News demo type:

QuickPublish

Now if all was well it would be up to you how you want to control this. Have two different create links one for quick publishing and one for norma, or control it behind the scenes based on roles in web.config or maybe settings for properties or something else.

Unfortunately the page tree isn’t updated when publishing the page. It’s some code in the Editpanel.SavePage() method that needs to be changed. After a quick look I decided that it wouldn’t be a good solution of if possible at all (uses private eventhandlers and stuff).

So this failed miserably though it looked so promising. Maybe I’ll have a go at it from another angle.

Code is available over here if someone wan’t to have a look..

Dec 07, 2010

Comments

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026