Try our conversational search powered by Generative AI!

Custom content area rendering stopped working after upgrade to 7.1

Vote:
 

After upgrading to 7.1 a view called ContentArea.cshtml I have placed in ~/Views/Shared/DisplayTemplates no longer kicks in and takes over rendering of content areas like before the upgrade. What has changed in regards to rendering content areas?

I’m using @Html.DisplayFor(m => m.AwesomeContentArea) where AwesomeContentArea is a ContentArea property on my view model. This _should_ match a view called ContentArea.cshtml in my DisplayTemplates folder, right? What has changed – is there another location for these views I need to be aware of now? I can’t see anything in the release notes explaining it.

 

#70729
Apr 29, 2013 10:30
Vote:
 

Works locally, however I'm using Html.PropertyFor.

#70835
May 02, 2013 9:26
Vote:
 

This is a known bug. See this thread for a work around until it can be fixed:

http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=70216

#70836
May 02, 2013 9:45
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.