When I try to login into Sitecore using Sitecore CLI command, I am getting /.well-known/openid-configuration: Bad Gateway issue.

In my last blog, I have explained how to setup ASP.Net Rendering SDK on developer machine and configure with your CM website. In this blog, I would explain the ASP.Net Rendering SDK OOTB solution design. If you open the OOTB solution file, you will get two projects. A) Platform B) RenderingHost

Sitecore introduced Sitecore JavaScript Services (JSS) to support headless with Sitecore 9.0. It’s a very good move for the headless and front-end technology where rich digital experience website can be easily using front end having analytics and personalization capabilities. In this case, Sitecore content getting severed by API named Layout Service in JSON format and client scripting technology like ReactJs, Vue Js consume this JSON and render/print the page.

You might come in a situation when you would like to disable the publishing service. Suppose you are working for a very big client, having huge Sitecore platform. But they change their content monthly (once in a month). Since they are sending the content monthly, they have huge content and multiple people change content parallelly.

In today’s time, digital contents are changing very rapidly. Due to this content’s author is very active now a days and changing their content frequently. In CMS worlds, publishing content is one of the most used features of the content management domain used by content authors. In case of bigger client, you may have multiple content authors for managing the website content. They are changing the content even parallelly as well.

One of the new features of Sitecore 9.3 is that they are giving the option to store the media files in Azure Blob storage. This is the less expensive approach and increases the performance as well. It also helps to decrease the Sitecore databases sizes as well.

Sitecore internally does not use this service. It provides this service for the developers/technical people to check the Sitecore health.Sometime website goes down. One of the major issue behind this is your website is not able to connect database. Sitecore provide a service to check the connectivity from all the available databases. It parse ConnectionString.config file and read all the available connectionString.

Cloning a Sitecore item means coping that Sitecore item at the same or different location and inherit its fields value from the base/source Sitecore item. Unclone is require when you would like to break the inheritance.

Search is a major functionality for any of the websites and performance of the website majorly depends on the search performance. Officially Sitecore support three different search engines: SOLR, Azure Search and Lucene. Sitecore does not recommend using Lucene as it would be deprecated in later Sitecore releases. Even Sitecore does not support Lucene for the production environment.

One of the eye catching and most talked feature of Sitecore 10 is support on Dockers Container. Sitecore is providing support on Dockers container officially now. It’s a huge relief for the company would like to use Dockers Container for the development and production.

In today’s world sharing digital content across various channel is very common. People create content at a central place and share the same content across various channel/platform sometime various app/mobile app as well.

Recently we came into a requirement where we need to send email whenever sitecore user trigger rebuild index manually. We also need to send email once that index gets completed. Sitecore does not provide any event for rebuild index like publishing. We have Publish:end and Publish:end:remote event for publishing but don't have similar event for.

From last few days, my analytics tracker was not working. So I thought to fix this issue today.When I start Sitecore Marketing Automation Engine – .MarketingAutomationService.

Rebuilding of index is a very common scenario if your website is built on Sitecore. During the maintenance of the websites, you come in the situation when you have to rebuild your indexes. Here the question is, what is the problem in triggering index rebuild event?

In the software development lifecycle you have to change database password sometimes. Especially if you are working on a new website or redesigning an existing websites and planning to go live. So before going live ideally we should change the existing databases password.

When I installed Sitecore 9.0.2 and Sitecore Commerce 9.0.2, I am getting below errors in the log files: ERROR Unable to connect to [https://localhost:8983/solr], Core: [sitecore_sxa_master_index] ERROR Unable to connect to [https://localhost:8983/solr], Core: [sitecore_sxa_web_index] The above issue is not related to the Sitecore Commerce but it is related to Sitecore 9.0.2 and Sitecore SXA.

Sitecore Commerce solution is not similar to regular Sitecore solution. Even Sitecore Commerce installation package provide us a sample Sitecore Commerce solution as well. But it contains multiple sample project as well. Usually, people don’t remove the existing sample project and start developing Sitecore Commerce component on top of that sample solution.

Changing the default password of Sitecore Commerce (XC) is not as simple as in Sitecore. When we install Sitecore Commerce 9.0 onwards, it creates 8 web applications in your IIS. You can find default password at multiple places in the commerce application’s configuration files.

Today I would like to discuss regarding SEO Friendly URL issue then will discuss the resolutions. Every project has to work on SEO (Search Engine Optimization). Particularly I would like to tell you about the URL. As per SEO recommendation, our URL should be in small letters and it should not have space in URLs.

Suppose you are using Unicorn for Sitecore item serialization. You have deployed your code and Sitecore items on staging/Production environment and released it to client/content author for content entry.

Suppose you are using Unicorn for Sitecore item serialization. You have deployed your code and Sitecore items on staging/Production environment and released it to client/content author for content entry.

One of the main changes from Sitecore 8.0 to 9.0 is, Sitecore changed xDB related API to the service based API. When you install Sitecore 9.0 or Sitecore 9 – Update 1, it creates two websites in your machine. One for your regular CMS and another is for hosting service, that can be used to perform xDB related activity.

For handling dynamic URLs, you can use wildcard item in the Sitecore. Only difference with the regular Sitecore item is, the name of the item is wildcard (*) character. Display name of that item can be anything.