SOLVED: ERROR Rendering control not found for Item in Sitecore

A simple solution (maybe too obvious to some) to a rather cryptic error. This error occurs if you use a MVC rendering (.cshtml or controller rendering) on a page whose Layout item points to a .aspx file.

As in, make sure you have a MVC layout when adding MVC renderings to a page. Duh!

Comments

Post a Comment

Popular posts from this blog

First look at Sitecore XM Cloud: Part 4 - Creating a new Site

Image
 Once you have successfully create an environment, you can go ahead and create your first site. In order to create a new Site, you need to launch the Sitecore Launchpad by clicking on the "XM Cloud Launchpad": Click on "Sites" menu to create a new Site: Click on "Add your first website" button to start the wizard. I chose the "Basic Site" template: Enter a Site name and pick a language and click on "Create website" button. You will see the following screen while your Site is being created: Once the Site is created, you can edit it in Pages or Explorer using the context menu: Explorer view of the Site: 1. "Details" view of page. 2. "Content" view of page: Unfortunately, trying to load the new Site in pages gives "Unable to connect to remote server"
Read more

First look at Sitecore XM Cloud: Part 1 - Getting started with Sitecore Cloud Portal and XM Cloud Deploy

Image
The biggest news of the year in the Sitecore community has been the arrival of Sitecore XM Cloud. In this blog series, I will be showing partner's access to XM Cloud. To get started, one needs to be invited to Sitecore Portal. You can access it at https://portal.sitecorecloud.io/.  Once you create an account and sign-in, you arrive at the following screen which has two main actions: Invite members  Managed projects (Sitecore XM Deploy) If you look closely you will see Sitecore Cloud Portal and XM Cloud Deploy. Invite team members opens up the following screen: "Manage My Projects" option launches the following window In the Part 2 , I will take us through deploying our first XM Cloud instance.
Read more

Part 2 - Decomposing and decoupling to achieve composability

Image
Having introduced "composable" in part 1 , we will now look at deconstructing and decoupling the typical layers of a digital solution to understand how composability can be achieved within them. Let's assume a typical application is composed of the following four layers: Client UI - typical client UI to serve channels like web, mobile, email, Social, AR/VR, Kiosk Infrastructure - this includes networking, security, hosting, routing and other typical functions Platforms/products - Off-the-self, plug-and-play, pay-as-you-go, bespoke products and tools that offer packaged business capabilities (PCBs is another Gartner term) or business applications as well as persistence Data storage - storage and persistence for data and analytics. Enterprise Data Lakes, Collections DB etc. Non-composable version of a digital solution will still include these layers but they are siloed. Decomposing the digital solution into these basic layers is in other terms is achieved through decoupling...
Read more