Sitecore Docs - Tech Tips by GS

  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": ...

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 Proce...

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=...

Is a newly launched car's astonishing features tempting you to buy a new car or upgrade your existing one?  Or are you thinking of purchasing a new car for your growing family needs?? If yes, welcome to jungle ruled by dealers and car manufacturers. They are fully geared up to trick you in making a purchase which will benefit them most. Not convinced? Make a visit to a nearby car dealer and get astonished by their courtesy and numerous suggestions (over a machine made cup of coffee) as if they are your best friends. Soon enough you will know that all the discussions and showroom visits lead you only into a world of confusions!! Believe me, you are not alone. Every car enthusiast has gone through same and all wish if there was a checklist they can use to decide what's best for them. No doubt, I too have stumbled here and there to get good advice. Based on my research over years and after going through hundreds of car reviews and expert suggestions, I have came up with a list of...

Dianoga is an automatic image optimizer for the Sitecore media library. It reduces the size of your images served from Sitecore by 8-70% automatically.  Dianoga is great for situations where content editors may not be image editing experts. How Dianoga works? By default, Dianoga runs asynchronously after the image is saved into the media cache. This means it has practically no effect on the site's frontend performance (though it does use some CPU time in the background). Dianoga updates the cache after the first image request. This means the first hit to images will serve the unoptimized version of image. Subsequent requests will receive the optimized version from cache. Where is the problem? Dianoga's behavior of serving unoptimized images on first request creates problem while using CDNs. CDNs cache the responses of media requests. Since first hit to images serve unoptimized image, CDN will cache the unoptimized version. CDN will serve this unoptimized version of image in it...