Using Rendering Parameters to Inject Data into Hidden Input – Sitecore
What are rendering parameters? They are the additional key-value pair data you can feed to the Sitecore component in addition to data source. The textbook example would be adding an additional CSS class to the component. Content authors can customise the style of the component, like background colour or button …
Using Data Source in Controller Renderings – Sitecore
Data source for Sitecore component provide data points to be used in the components, such as controller renderings or view renderings. Content author can easily edit those data points (e.g. header title, body text or CSS style) to customise components. It is one of the techniques to make Sitecore component …
Could not create controller with Constructor on type not found exception – Sitecore 8.2
When your controller rendering is failing with Could not create controller along with the inner exception,Constructor on type (your constructor name, e.g Sitecore.Feature.Controllers.MediaController) not found, there is something wrong with the actual controller code. Could not create controller error has a few different reasons. Another common reason is the inner …
An unhandled exception occurred Rendering Controller Error – Sitecore 8.2
This error is an interesting one because there are a few different reasons. My case was not what the error actually says. Error in Experience Editor Error Rendering Controller: SitecoreDev.Feature.Media.Controllers.MediaController, SitecoreDev.Feature.Media. Action: HeroSlider: An unhandled exception occurred. at Sitecore.Mvc.Pipelines.MvcEvents.Exception.ShowAspNetErrorMessage.ShowErrorMessage(ExceptionContext exceptionContext, ExceptionArgs args) at Sitecore.Mvc.Pipelines.MvcEvents.Exception.ShowAspNetErrorMessage.Process(ExceptionArgs args) at (Object , Object[] ) …
Could not create controller Error for Controller Renderings – Sitecore 8.2
ASP.NET standard controller action routing is {controller}/{action} (see here). When you create a new project, you will see this in RouteConfig.cs file in the App_Start folder. Sitecore has overridden this standard route registration procedures. Routing to controller and action can be determined by the controller rendering component. This makes sense …