When using the coveo search box and setting it up in the presentation settings on a sitecore item, you will need to specify the target search result item using the field "search page item" (as shown below), so that the results are rendered on that page. But what if in a multi-site scenario, suppose there are 20+ sites and the "search page item" is actually the child item of each of the site's home item?

Sitecore 9 Forms is a powerful upgrade from WFFM. It provides a simple interface that allows the user to easily create forms on demand, and collect information from their visitors. For longer forms, the creation process can be a bit tedious and repetitive. This prompted me to leverage Sitecore PowerShell to create a script that will parse a JSON file and generate a form. Now the repetitive stuff can be managed via copy/paste. All of the scripts and an installation package can be found over at GitHub: Sitecore - Json To Forms. Continue reading to learn more about the thought process that brought these scripts to life.



I have been using coveo for sitecore, well before its JSUI days, when they just had the .NET interface. Indeed coveo has come a long way since then. We all know how coveo for sitecore makes it easy for searching both for sitecore based items and also external sources. Today, I am going to talk about how to search for results based on a given "location" and "distance" from that location. Not only that, we will also show the gogle map with markers showing those searched locations, corresponding to results.

There are many mechanisms for monitoring the health of Sitecore, but Heartbeat.aspx is the simplest. It is easy to monitor with third party tools and requires no knowledge of technological underpinnings. With the release of Sitecore 9, however, things have gotten a bit more complicated. Heartbeat checks every database, even unused ones. this can lead to false negatives and problems monitoring site health in different environments. Fortunately, there is a solution!

This post is somewhat of a sequel to my previous one around multi-site and multi-language setup. When there is only one site and only one language things are pretty straightforward in terms of site context. Once multiple sites are introduced every time we are getting an item in Sitecore and/or building a link we need to make sure we do it within the correct site and correct language. For the most part Sitecore does it out of the box but there are cases when this functionality breaks down.