David Harlow
Mar 6, 2018
  4280
(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
From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |

Accelerate Optimizely DAM Adoption: Unlocking Business Value with Metadata Bulk Import

Accelerating Optimizely DAM Adoption How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value Executive Summary For enterprises runnin...

Vaibhav | Apr 27, 2026