Views: 1136
Number of votes: 11
Average rating:

Move inline block edit from Labs.BlockEnhancements to CMS UI

Features in EPiServer.Labs.BlockEnhancements have been used and appreciated by many users. The most common feature - inline editing, now becomes a part of the product and will be available from CMS UI 11.32.0.

Inline Edit

Using the Quick Edit command from the context menu, editors can edit blocks without changing the current content context. The command is available in Forms View, On-Page Edit and the assets pane.

inline edit.gif

The command opens a dialog box with an editable block form. Editors can edit blocks the same way as when switching to blocks editing context.

By default, the Name, Categories properties and the Setting tab are hidden. This developer guide topic shows how to enable them with InlineBlockEditSettings attribute.

The bottom-left button mirrors the main button in the Publish menu, so it can be Ready for Review, Ready to Publish, Publish or Publish Changes. It helps editors to change the block's status directly from the inline edit dialog box.

image34my.png

For block content types that have properties in more than one tab, those tabs are replaced with sections in the inline edit dialog box. Below is an example of a block type which is configured to show Name property and Setting tab, and has property in three tabs - Contact, Products and Content.

    [SiteContentType(GUID = "9E7F6DF5-A963-40C4-8683-211C4FA48AE1")]
    [SiteImageUrl]
    [InlineBlockEditSettings(ShowNameProperty = true, HiddenGroups = "")]
    public class AdvancedBlock : SiteBlockData
    {
        [Display(Order = 1, GroupName = SystemTabNames.Content)]
        public virtual string Text1 { get; set; }

        [Display(Order = 2, GroupName = SystemTabNames.Content)]
        public virtual string Text2 { get; set; }

        [Display(Order = 1, GroupName = Global.GroupNames.Products)]
        public virtual string Text3 { get; set; }

        [Display(Order = 2, GroupName = Global.GroupNames.Contact)]
        public virtual string Text4 { get; set; }
    }

images5vtv.png

Note: For people who use Labs.BlockEnhancements and Labs.ContentManager:
If you have a previous version of EPiServer.Labs.BlockEnhancements installed, you should upgrade to the version 0.10.0 as it is compatible with CMS UI 11.32.0
Compatible version of Labs.ContentManager to work with CMS UI version 11.32.0 is coming soon.
Jan 19, 2021

Stefan Holm Olsen
( By Stefan Holm Olsen, 1/19/2021 5:49:35 PM)

Very nice 👍

Erik Henningson
( By Erik Henningson, 1/21/2021 7:10:07 AM)

Great to see that the CMS part isn't forgotten. A great editor experience is a key to success.

GOSSO
( By GOSSO, 1/21/2021 8:03:26 AM)

Waited for this, why not use tabs? =)

Mike Malloy
( By Mike Malloy, 1/29/2021 7:54:27 PM)

I agree with @GOSSO, use tabs.

Would be nice if it worked in the All Properties view.

Linh Nguyen
( By Linh Nguyen, 2/1/2021 2:43:28 PM)

@GOSSO, @Mike: I should have used tabs in the demo, but tabs is supported.

@Mike: It works in All Properties view as well

GOSSO
( By GOSSO, 2/7/2021 8:33:06 PM)

"you should upgrade to the version 0.10.0"? shouldnt you make clear that you can uninstall Labs.BlockEnhancements, also seems that Advanced.CMS.Forms should be uninstalled ? 

Linh Nguyen
( By Linh Nguyen, 2/19/2021 11:38:46 AM)

@gosso: Labs.BlockEnhancements has other features that people might still use (smart publish, inline publish, status indicator...), for those they should upgrade to 0.10.0 to make Labs.BlockEnhancements compatible with CMS UI. I haven't checked Advanced.CMS.Forms, but we do have some issues with compatible versions of Advanced.CMS vs CMS UI 11.32.0

Please login to comment.