Ghanendra's Tips

The Publishing Service module is an optional replacement for the existing Sitecore publishing methods. This module increases publishing throughput, reduces the amount of time spent publishing large volumes of items, and offers greater data consistency and reliability. The module also improves the user experience and provides better visual feedback to the user on the state of the publishing system. We decided to use  Sitecore Publishing Service  due to large amount of content in our Site nodes and site publishes that run for more than an hour. Problem When we started implementing with Sitecore Publishing Service on our development machines by following the instructions from SPS installation guide, we got stuck at point where the SPS won't start and will give an error as in the snapshot below -  Solution To solve this problem, we started looking into the logs but the logs did not even record this activity. We were left clueless. We decided to start this service using powershell. Powe

In this blog, I will describe about a Sitecore bug in version 10.1.1 where developers face issues if they try to use out-of-box placeholder items and especially when they try to move them from their default location. Problem We are working on upgrading from Sitecore 8.2 to Sitecore 10.1.1. We are making use of content placeholder present in Sitecore placeholder settings out of the box.  We are updating our solution to follow Helix conventions and decided to move the content placeholder to Project folder. But we encountered a weird issue in moving the 'content' placeholder to any Helix layer. To our surprise, it wont move after numerous attempts. We tried dragging the content placeholder item but that didnt work. Then we tried copying it using right click but that too didnt work. We tried updating its location in ymls related to it and then pushed the item but no success was achieved. Solution We created a Sitecore support ticket to understand this behavior Sitecore support team

Problem In our Sitecore 8 solution, content authors used to add encoded values for html tags like &nbsp; etc. in Multi-line text field and it worked correctly. When the solution was upgraded to Sitecore 10, all the html tags in multi-line text field started to get rendered as plain text instead of html as in snapshot below -  Solution RENDERING - HTML ENCODED FIELD TYPES This setting specifies a pipe-separated list of field types that should be HTML encoded when rendered by the <renderField> pipeline. Default value: text|single-line text|multi-line text We found that this setting has multi-line text included now which wasnt the case in Sitecore 8 -  <setting name="Rendering.HtmlEncodedFieldTypes" value="text|single-line text|multi-line text" /> To fix this, we removed multi-line text from the value of this setting using below patch -  <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" xmlns:environment="http://www.sitec

  While performing dotnet sitecore ser push, I received following error- Unhandled exception: System.Exception: Unhandled exception  ---> System.AggregateException: One or more errors occurred. (Error converting value 404 to type 'GraphQL.Common.Response.GraphQLResponse'. Path '', line 1, position 3.) (Error converting value 404 to type 'GraphQL.Common.Response.GraphQLResponse'. Path '', line 1, position 3.) (Error converting value 404 to type 'GraphQL.Common.Response.GraphQLResponse'. Path '', line 1, position 3.) (Error converting value 404 to type 'GraphQL.Common.Response.GraphQLResponse'. Path '', line 1, position 3.) (Error converting value 404 to type 'GraphQL.Common.Response.GraphQLResponse'. Path '', line 1, position 3.) (Error converting value 404 to type 'GraphQL.Common.Response.GraphQLResponse'. Path '', line 1, position 3.)  ---> Newtonsoft.Json.JsonSerializationException:

  While running dotnet sitecore ser push, I encountered following error- Unhandled exception: System.Exception: Unhandled exception ---> System.NullReferenceException: Object reference not set to an instance of an object. at Sitecore.DevEx.Serialization.Client.TreeCongruencyCommandBuilder.GenerateCommands(TreeSpec subtree, ITreeDataStore sourceDataStore, ITreeDataStore destinationDataStore, CancellationToken cancellationToken) at Sitecore.DevEx.Serialization.Client.TreeSyncOperation.DiscoverCommands(TreeSpec subtree, TreeCongruencyCommandBuilder commandBuilder, CancellationToken cancellationToken) at Sitecore.DevEx.Serialization.Client.TreeSyncOperation.DiscoverCommands(Boolean applyAllowedPushOperations, IEnumerable MyProject.module.json file had following entry which pointed to a non-existent node in Sitecore. The node was moved to a different folder as part of a PR but the entry in MyProject.module.json was not updated. Hence the error. - { "allowedPushOperations": &quo

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