SaaS CMS has officially launched! Learn more now.

Bartosz Sekula
Nov 6, 2019
(10 votes)

Inline Block Publishing - create new blocks without leaving current context

We added a new major improvement to the block publishing that I would like to share with you.

Previously, the editors were able to only inline edit existing blocks. However, whenever a new block was needed then they still had to use the default form, that caused the current content context to switch.

It was quite annoying especially in nested block scenarios where you had several levels of nesting i.e. Bootstrap Row Blocks containing Content Blocks.

With it is now possible to create new blocks using the same inline form, without the need to ever leave the current context.

The best part is that we support nesting. As many levels as needed. And it works both in On-Page Edit (OPE) and in regular Forms view.

After upgrading to v0.5 the "Create a new block" link will no longer open a big content type selector and switch editor's context to the newly created content item.

Instead a simple dialog will be presented:

After choosing the content type the editor will see the inline edit form straight away. All properties will be included (both required and optional):

Please note that the new commands are available both from the Forms View and the On-Page Edit.

Please take a look how it all works:

Nov 06, 2019


Allan Thraen
Allan Thraen Nov 6, 2019 09:56 AM

This is an incredibly cool project!!!

Joshua Folkerts
Joshua Folkerts Nov 6, 2019 01:18 PM

I like this alot!  I mean alot!!!!!! I guess the editors will too :)  Nice work!

Benjamin Dean
Benjamin Dean Nov 6, 2019 01:21 PM

This project keeps getting better week after week, this is a really nice enhancement!

In general context switching is one of the worst parts of the user interface, adding this will make a lot of people happy

Erik Henningson
Erik Henningson Nov 6, 2019 01:38 PM

This is really nice! Are there any plans to include this in the core product?

Manoj Kumawat
Manoj Kumawat Nov 6, 2019 02:09 PM

That's super cool!!

Ravindra S. Rathore
Ravindra S. Rathore Nov 6, 2019 08:53 PM

Nice feature 👍👍

That's why we love Epi

Linus Ekström
Linus Ekström Nov 10, 2019 09:04 AM

Very nice work Bartosz - it's fine to see that the intention for how most blocks block be used when the UI for Episerver 7+ was designed - i. e. local blocks with inline edit - has finally been realised. I really like how new blocks automatically are created in the local folder for the current object. One small glitch that I noticed was that when I have a lot of properties on a block, the dialog becomes higher than my screen and the save/cancel buttons are then invisible before I move the dialog on the screen. But all in all - a very nice and welcome addition!

Bartosz Sekula
Bartosz Sekula Nov 10, 2019 07:49 PM

Thank you very much.

Linus, is this the issue that you are referring to?

Nicola Ayan
Nicola Ayan Nov 10, 2019 11:56 PM

Very nice! :)

Tien Quach
Tien Quach Nov 11, 2019 02:18 AM

Been looking for this feature for a long time. Nice work.

Linus Ekström
Linus Ekström Nov 11, 2019 07:02 AM

Yes Bartosz - that seems to be the same issues that I've been experiencing.

Bartosz Sekula
Bartosz Sekula Nov 13, 2019 09:59 PM

Linus, that issue has been resolved in

Thanks for quick feedback! :)

Henning Sjørbotten
Henning Sjørbotten Nov 15, 2019 11:48 AM

This is a great feature, for editors with publishing rights. For other editors this feature is just in the way of everything else. 

The only option in the new block window is Publish. If you do not have publish rights, "Publish" remain the only option. You cannot use this new feature, and must then click this new block-windows away. Then the only thing you can do is to go to normal block-editing instead. There you can submit the block in "Ready to publish"-mode.

This Block Enhancement-functionality should only be visible for editors that can use it (for now that is Publishers). Best would be if user do not have publishing rights, the Ready to publish-option would be available instead.

Bartosz Sekula
Bartosz Sekula Nov 15, 2019 08:51 PM

You are correct Henning. It will be solved soon.

Bartosz Sekula
Bartosz Sekula Nov 21, 2019 07:24 PM


v0.5.2 now supports scenario that you described. Additionally we started to check the access rights so:

If you can Publish you will see the Publish button

If you cannot Publish you will see the Mark as Ready to Publish button

I would really appreciate your feedback if the new version fixes the issues you raised.


Henning Sjørbotten
Henning Sjørbotten Nov 22, 2019 11:07 AM

Hi Bartosz, thanks for looking into this so fast.

I cannot see a Ready to publish button inside the inline-block-edit window. And the ready for publish-alternative will not appear in the block hamburger menu either until a CTRL-F5/have been done, after doing that I can see Ready to publish in that menu.

Another problem I just found is that if the block uses the ImageVault nuget for images, the imagevault property will appear empty in the enhancement-window (this happens also for site admins). You will be able to set a new image from the window, but that will overwrite the existing one (that you cannot see).

Henning Sjørbotten
Henning Sjørbotten Nov 22, 2019 11:28 AM

Tested some more, and the ready for publish do appear without a reload now in the block menu. I think it was something about me being logged in with different browsers with a publisher and an editor without publishing rights on the same page  But it will not show the Mark as Ready to publish-button, I guess it should be located about the same place as the Publish button inside the inline block window.

Bartosz Sekula
Bartosz Sekula Nov 22, 2019 11:07 PM


ImageVault is a 3rd party component, we already have an issue for that - waiting for feedback from guys responsible for ImageVault.

About the missing button, for now, 'Ready to publish' is only available in the context-menu. We did not add it to the inline-edit dialog yet, however, it seems we should have :)

For now, please use the context menu in the content area.

Please login to comment.
Latest blogs
How to have a link plugin with extra link id attribute in TinyMce

Introduce Optimizely CMS Editing is using TinyMce for editing rich-text content. We need to use this control a lot in CMS site for kind of WYSWYG...

Binh Nguyen Thi | Jul 13, 2024

Create your first demo site with Optimizely SaaS/Visual Builder

Hello everyone, We are very excited about the launch of our SaaS CMS and the new Visual Builder that comes with it. Since it is the first time you'...

Patrick Lam | Jul 11, 2024

Integrate a CMP workflow step with CMS

As you might know Optimizely has an integration where you can create and edit pages in the CMS directly from the CMP. One of the benefits of this i...

Marcus Hoffmann | Jul 10, 2024

GetNextSegment with empty Remaining causing fuzzes

Optimizely CMS offers you to create partial routers. This concept allows you display content differently depending on the routed content in the URL...

David Drouin-Prince | Jul 8, 2024 | Syndicated blog