Ghanendra's Tips

Do you know that version 10.1 onwards, Sitecore is storing default items as resource files. This is an interesting update as the files on disk are binary-serialized item data using Google’s ProtoBuf specification – in this case using the ProtoBuf.Net library for .Net. Why to store item as resource files? Sitecore has lots of  out-of-box items like sitecore/content/Home which are present in Sitecore databases. Sitecore has changed this approach to store these items on file system as resource files as ProtoBuf data to solve the complexity related to upgrading the Sitecore instances especially in containerized environments. If you have an instance of Sitecore 10.1 or above running, you will find these below files. Default Sitecore items are part of these files now -  How do they help in upgrades? In containerized solution, code and config updates are wrapped in Docker Image. When the out of box Sitecore items are placed in resource files, they get updated as part of Docker Image itself. T

This happened during one of our upgrade projects from Sitecore 8.2 to Sitecore 10.1 on dockers. We use Brightcove for videos in our solutions. We added a Brightcove image to docker-compose. After spinning up the environment using docker-compose up, we got the below error -  The reason we got this error as we missed the Brightcove dlls in our docker build folder -  These dlls were missed to be checked in to source control due to gitignore file. You man need to modify the paths in gitignore to include these files as well in source control. Hope it helps!

Problem   We are upgrading from Sitecore 8.2.1 to Sitecore 10.1.1. We are moving towards containerized solution using Dockers as it is officially supported by Sitecore now. Most of the development team has worked on non-docker based Sitecore instances and are still adopting to working with containers based applications. One of the confusions pretty much every developer had was how to debug a Docker based containerized application.  Solution  Debugging container based application using Visual Studio is slightly different.  In Visual Studio, you have two options for attaching to a process in a container: Option 1: use the Containers window T o use the  Containers  window: If the  Containers  window is not showing, open it from the top  View  menu. Click  Other Windows , then  Containers . In the list of running containers, right-click on the one that you want to debug, and click  Attach to Process : The  Attach to Process  dialog appears and shows the available processes running in the c

We were using docker based Sitecore 10.1 for local development. This was an upgrade project and I was working on validating the items in upgraded Sitecore 10.1 environment.  Problem I started performing some simple searches in Content Editor's search box but got no results returned even when the item existed in the content tree. I realized I have never built the SOLR indexes since I setup the environment. So I went to control panel and attempted index rebuild. I got the following error -  Job started: Index_Update_IndexName=sitecore_master_index |# Exception : System . Reflection . TargetInvocationException : Exception has been thrown by the target of an invocation. ---> SolrNet . Exceptions . SolrConnectionException : <?xml version="1.0" encoding=" UTF -8"?> <response> <lst name="response Header "> < int name="rf">1< / int > < int name="status">400< / int > < int name=&quo