Ghanendra's Tips

 We are on Sitecore 10.1.2 and we use Sitecore Publishing Service module. We often encounter random unresponsiveness of Publishing Service where content authors report that they tried publish an item or a site but the publishing dialog seemed unresponsive and errored out as in snapshot below after few seconds - When we looked at the publishing service logs, we could see that it disposed off all the connections but did not attempt at recreating them. An application pool recycle solves the problem but the catch is this blocks the content authors from publishing their changes until a developer gets to recycle the application pool for the publishing service. We had an option of scheduled application pool recycle for the Publishing service but our application is used 24x7 across the globe by content authors for editing their content. So there were chances that application pool recycle may kill any publishing jobs and then create further problems. As an attempt to solve this problem, we star

 The Problem While working in Experience Editor in Sitecore 10.1.2, content authors started reporting that clicking on Lock and Edit link doesnt lock the page sometimes. Content Authors have to reload the page to work or use Content Editor to Edit the page. This has been reported by multiple users at multiple times and is not consistently reproducible. The Research We have observed that when Lock and Edit is unresponsive, it doesnt trigger any requests in Network tab in browser dev tools. When Lock and Edit is responsive, it triggers several requests in Network tab. The HTML for Lock and Edit appears same in both the cases without any missing fields. The console tab doesnt contain any errors. To learn more on this issue, I created a Sitecore Support ticket. Sitecore support representative was able to reproduce the issue on her local instance as well. Below is the response from Sitecore -  "I was able to reproduce this behavior in the local environment and, since this is not the ex

THE PROBLEM We are on Sitecore 10.1 and we use Sitecore Publishing Service for publishing. Recently, we encountered an issue where our items selected in a custom field (called as Multilist Dynamic Source with Search ) were not published even when Related Items checkbox was checked in the Publish Dialog. However, the items selected in the Multilist fields publish properly. Hence, we ruled out the possibility of Sitecore Publishing Service configurations not pointing to correct database that stores Link DB. We discussed that issue in a previous  blog . Multilist or any custom field based on Multilist stores the selected items as a pipe separated list of ItemIDs. You can verify this by looking at the Raw Values of the field. When a user published a page and checked the checkbox for Related Items , then the expectation was that the items selected in Multilist or the custom field of a rendering datasource shall also get published. In our case where we used the custom field based on Multilis

 The Problem Recently, we encountered a weird problem where one of our sites in Experience Editor will resolve to default website and not to the correct site. This happened when an author or developer opened Content Editor and tried to select one of the pages in the SXA site and then clicked on Experience Editor in Publish tab to open the page in Experience Editor, the page opened with the following errors -  On checking the logs, we found that logs contains following entries for each SXA site -  We never saw these kind of errors earlier in our logs.  The Solution We started validating what is wrong with our site definitions. To our surprise, everything configured in site definitions appeared normal except the fact that a recent change was introduced to enable Enforce version presence. We soon found out a KB from Sitecore talking about the same problem - https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB1002873 According to it -  An SXA site might not be resolved

In this blog post, I have shared information about Sitecore Search. Most of the content in this post are my notes from a webinar presented by development team of Sitecore Search that I felt I should share with you :) What is Sitecore Search? Sitecore Search is an API first product designed by Sitecore to build search experiences from scratch without the need of complex code. The APIs can be integrated in any solution and the look and feel can be configured to match the application. Sitecore SPEAK also provides some UI elements that can be integrated with these APIs to build the search experience. Sitecore Search can be a great offering while re-platforming an application. In this post, we will learn more about capabilities of Sitecore Search. How Sitecore Search can help your organization? Sitecore search is great for marketers. It empowers them to configure searchable experiences without need of technology personnel. It enhances content discovery which generates more leads. Hence, it

In Sitecore Media Cache, the images are stored in MediaCache folder using a specific convention. This means if you need to locate an image in MediaCache folder, you need to understand this convention else you have to be really lucky to be able to find your image in MediaCache. I have many times figured this out earlier and then have also forgotten it when it was not needed. Recently, while working on a production issue, I again had to recall it  to know if a media file is being served from MediaCache or not. So this time I decided to document it and share it with other developers in case they too struggle with it. If you go to App_Data/MediaCache on your Sitecore instance, this is how a typical site folder in it looks like. All the media files for sites are cached in their site specific folders only -  If you go one level inside these folders, you will see this -  The above snapshot is from an example site which has few media items only. Your actual MediaCache folder may have hundreds

I have been using Samsung Galaxy F62 for 2 years now without any problem until recently when I would plug the charger in to my phone, it would show all the signs of phone getting charged and after 20-30 seconds it just stops charging. The phone automatically stops showing any signs of charging. This happened once earlier as well but at that time, it worked fine on its own  after few reattempts. I assumed that it was a minor glitch and the problem is solved but that was not the end of it. Soon, the problem resumed and I started trying all the different mechanisms suggested on internet to fix this problem. I tried - using different charging adapters in case the charger was faulty using different charging cables in case the cable was broken  tried cleaning my charging port in case the port had some dirt running charging diagnostics/troubleshooting in my phone which detected nothing Finally, my phone battery drained completely and I had no other option than to visit a near by mobile techni