Himmat Singh Dulawat (3x Sitecore MVP)

In my previous blog, I discussed Multisite in Sitecore 10 . In continuation of that blog, in this blog, I am going to discuss what are the other important things we need to take care of while renaming or adding a site. Add entries to the <cacheSizes> section for site-specific: For the default site named website, Sitecore adds cache sizes for the website site. While working on the multisite we set up one more site with a different name. Then you need to add a section with the site name and add the caching values for that site. Example: Your site name is Site1 then create a patch file and add the below configuration: Update the Preview.DefaultSite setting value for the additional Site: This setting specifies the default site to be used in Preview mode. For example, if you rename the standard 'website' site, and add e.g., site1, please cha

What is a PTA Partner Tech Advisor, added to the Sitecore Support portal? Sitecore has recently launched the Partner Technical Advisory support service. The Partner Technical Advisor (PTA) team is a team of expert developers and subject matter experts who provide partners with pre-sales, sales, implementation, and ongoing support and advocacy. Getting started: How to engage a PTA using Service Now, Sitecore’s case management system: Navigate to the Support Portal and log in Click on Support Cases Click on Partner Technical Advisor in the gray horizontal navigation bar Complete the simple form and add attachments as needed Click Submit (Note: You will receive an acknowledgment via email) All correspondence must be conducted through Service Now Frequently Asked Questions (FAQs): Do I need to be certified to engage with a PTA? PTAs are intended to support partner resources who are already trained and certified

Configuring a multisite in a Single Sitecore instance is an OOTB feature. It means you can share data, templates, rendering, and other items in the same Sitecore Content tree with two different website nodes. Each website node will have its tag and it's managed from Sitecore.Sites.config.  A single Sitecore installation, however, can publish any number of websites, each with its properties. The properties for each site are, by default, stored in the Sitecore Sitecore.Sites.config file.  The Sitecore Sitecore.Sites.config file includes a list of served websites listed in the <sites> section and the definition of the node will be defined into the <site name=”website” …/> tag. Sitecore parses incoming HTTP requests and selects the appropriate site based on the HTTP request parameters. Step 1: Create a new site node into the content tree: Create one more site node in the Sitecore tree. Best practice says each Site node shou

After Login on Sitecore CMS does not redirect to Content Editor and throws error 500 - The request timed out. The web server failed to respond within the specified time error. I have deployed our Application on PROD CM and CD instance on the Azure PAAS and the instance is working fine. When I try to log in to the CM instance, I can log in, but instead of redirecting me to the Sitecore Content Editor it's throwing me an error 500 - The request timed out. The web server failed to respond within the specified time. After logging into the CM site, the following error is displayed: 500 - The request timed out. The web server failed to respond within the specified time After login into the CM instance: I have verified the AllowedCorsOrigins and Redirect URL in the identity server and CM instance in both Sitecore.IdentityServer.Host.xml and Sitecore.Owin.Authentication.IdentityServer.config respective files and all are correct. The same code and depl