I have a block with one property:

public class MyImageBlock : BlockData

    {

        public virtual string Description { get; set; }

    }

I create a view (even not using Description) for it and I wire it together inside TemplateCoordinator, so it will be using my view when rendering.

I have an ArticlePage

public class ArticlePage :

{

        public virtual MyImageBlock DescriptionBlock { get; set; }

        public virtual string MainIntro { get; set; }

}

In the View for ArticlePage:

<h2>@Html.PropertyFor(m=>m.CurrentPage.DescriptionBlock)</h2>

<h2>@Html.PropertyFor(m=>m.CurrentPage.MainIntro)</h2>

When I am in Edit Mode the block is being rendered properly form MyImageBlock.cshtml but all properties after this one are rendered with EditMode wrappers and cannot be edited using OnPageEdit.

Investigation:

Down the road there is a method 'bool CurrentContentContainsProperty<TModel>(HtmlHelper<TModel> html, string propertyName)' which uses

'IContentData GetCurrentData<TModel>(HtmlHelper<TModel> html)'

The second method uses Html.ViewContext.RequestContext.RouteData.Values["currentContent"] and from my colleague investigation this has invalid value. It should not be set when use our custom MyImageBlock.cshtml. Actually the stupid workaround is to clear this value after rendering our block.

<h2>@Html.PropertyFor(m=>m.CurrentPage.DescriptionBlock)</h2>

<h2>@Html.PropertyFor(m=>m.CurrentPage.MainIntro)</h2>

@{

    Html.ViewContext.RequestContext.RouteData.Values["currentContent"] = null;

}

We don’t want to use Blocks with controller as it decrease performance and I remember from somewhere that EPiServer discourage it.

It’s all weird, and we can be wrong, or maybe we miss some small but important thing here. Epi guys, do you have a solution?