David Harlow
Mar 6, 2018
  4298
(6 votes)

Extending Commerce - Content Area Functionality

By default, content areas in Episerver commerce items such as products and variants don't display the option for creating a new block, and only allows for blocks to be dragged in, as seen below.

Image content-area.PNG

However, an extremely simple solution to change this default behaviour is to inherit from IResourceable on your product/variant which will require the interface member ContentAssetsID to be declared which can simply be scaffolded to false, and this will be all the code required to display the content area as expected! 

    public abstract class SiteProductContent : ProductContent, IResourceable
    {
        [ScaffoldColumn(false)]
        public Guid ContentAssetsID { get; set; }
    }
Mar 06, 2018

Comments

Marcus B
Marcus B Mar 6, 2018 10:17 PM

Great!

Johan Book
Johan Book Mar 6, 2018 11:58 PM

Nice!

Luc Gosso (MVP)
Luc Gosso (MVP) Mar 7, 2018 11:16 AM

thx for sharing! nice!

David Harlow
David Harlow May 3, 2018 12:23 PM

Update: We've decided to remove this functionality from our solution and allow editors to only add shared blocks to content areas on commerce pages, this is due to weird behaviour being viewed such as content completely dissapearing from the content area when not published, hopefully Episerver will fix this in the future. Feel free to vote for this in the following feature request:

https://world.episerver.com/forum/developer-forum/Feature-requests/Thread-Container/2018/5/full-block-support-for-the-commerce-catalog/

Please login to comment.
Latest blogs
Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026

Optimizely CMS 11 Is Out of Support — and the Hard Part of the Upgrade Isn't the CMS

On 10 April 2026, Optimizely formally announced that CMS 11 was out of support — CMS 13 had reached GA on 31 March, and by policy only the two most...

Allan Thraen | May 6, 2026 |