I did a CTRL + SHIFT + F in our solution and didn't see any files containing "ContentAreaRenderer" - so I'd guess we're using whatever the Epi default is there?
It might be also so that ContentAreaRender is overwritten by some 3rd party assembly - meaning that it's inside some other .dll file. Searching for ContentAreaRender inside your code base might yield no results.
One of the ways to check this for sure - is to install Episerver DeveloperTools and check what do you have inside dependency container.
Hey, thanks for the fast replies and further testing. I just added the EPi Dev Tools package and got that running. Here's what I'm seeing when doing a search on that page for "ContentAreaRenderer" (under the "Container" tab):
Exactly - no, this is not correct renderer. You could sneak peek into Bootstrap renderer init module and see which class should be set and renderer. And can try to implement your own initialization module and copy/paste code from library. Maybe there is something wrong with module invoke and renderer is not set - which explains why you see no changes in HTML.
Sorry, I had thought the Nuget package would add that initialization module. I just added a new class called "SetupBootstrapRenderer.cs" in our InitializableModules folder, using the file you referenced (I only changed the namespace to match our project).
Indeed, library is adding required initialization and usually no addition setup is required.
You can try it in simple Alloy Tech sample site.
Regarding your errors - this is due to some stuff is still kept internal. You can mock it and replace it with some hard-coded stuff.
Hm, I did try extracting the needed code from the repo here and using that to workaround the errors, however it created more errors. Unfortunately, we're doing a whole site redesign and I don't have too much time to dive into all the errors.
This is a great project and would be an awesome feature for our editors, so I will definitely be back in the future to figure this out! Thank you for your time and efforts looking into this ticket.
Hey, we just installed this package and selected half-width on a standard HTML content block.
After saving the block and viewing the page again, we aren't seeing any change in the HTML. I was expecting to see a new
Is there any other setup or configuration we're missing?
It's should definitely render appropriate classes ;) that's the main purpose of this package.
Can you check if your ContentAreaRenderer is not overwritten to some other type for some reason?
I did a CTRL + SHIFT + F in our solution and didn't see any files containing "ContentAreaRenderer" - so I'd guess we're using whatever the Epi default is there?
We're running CMS version 11.18:
Hi,
Just re-tested again with plain AlloyTech sample site. Additional HTML element with CSS classes is rendered properly. Used following versions:
It might be also so that
ContentAreaRenderis overwritten by some 3rd party assembly - meaning that it's inside some other .dll file. Searching forContentAreaRenderinside your code base might yield no results.One of the ways to check this for sure - is to install Episerver DeveloperTools and check what do you have inside dependency container.
Hey, thanks for the fast replies and further testing. I just added the EPi Dev Tools package and got that running. Here's what I'm seeing when doing a search on that page for "ContentAreaRenderer" (under the "Container" tab):
EPiServer.ServiceLocation.ServiceAccessor`1[[EPiServer.Web.Mvc.Html.ContentAreaRenderer, EPiServer.Cms.AspNet, Version=11.18.1.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7]],EPiServer.Framework, Version=11.18.1.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7
EPiServer.Web.Mvc.Html.ContentAreaRenderer,EPiServer.Cms.AspNet, Version=11.18.1.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7
Is that what you'd expect to see here for the default ContentAreaRenderer?
Also, our packages are targeting .Net Framework 4.6.1 instead of 4.8, if that matters at all.
Exactly - no, this is not correct renderer. You could sneak peek into Bootstrap renderer init module and see which class should be set and renderer. And can try to implement your own initialization module and copy/paste code from library. Maybe there is something wrong with module invoke and renderer is not set - which explains why you see no changes in HTML.
Sorry, I had thought the Nuget package would add that initialization module. I just added a new class called "SetupBootstrapRenderer.cs" in our InitializableModules folder, using the file you referenced (I only changed the namespace to match our project).
I am seeing two errors:
Indeed, library is adding required initialization and usually no addition setup is required. You can try it in simple Alloy Tech sample site. Regarding your errors - this is due to some stuff is still kept internal. You can mock it and replace it with some hard-coded stuff.
Hm, I did try extracting the needed code from the repo here and using that to workaround the errors, however it created more errors. Unfortunately, we're doing a whole site redesign and I don't have too much time to dive into all the errors.
This is a great project and would be an awesome feature for our editors, so I will definitely be back in the future to figure this out! Thank you for your time and efforts looking into this ticket.