5 Results for Popular TechnologyCoveo
My previous blog Dynamically linking Coveo Search box to target Search page talked about how to achieve dynamic search page link on Sitecore 8.2 and Coveo for Sitecore 4.1. Here I am going to describe how to achieve this on Sitecore 9+, using Coveo for Sitecore 5.0 and Hive.
Los Angeles, CA - XCentium today announced the launch and availability of their Flex Accelerator for Sitecore, a new SaaS solution offered as part of the Sitecore KickStart program. Designed specifically for mid-market organizations, Flex Accelerator for Sitecore enables Sitecore’s industry-leading digital experience platform to be deployed in a SaaS setting in as little as 30 days and at a starting price of $100,000 per year.
Flex Accelerator for Sitecore is home to several clients eager to use the new hosting model provided by the Sitecore KickStart program. Nexford University was the first to take advantage of the solution, with a new website built on Sitecore® Experience Platform version 9 only five weeks from hand-off to launch.
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?
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.
In Coveo admin, we noticed that the "Last Source Refresh/Rebuild won't update" wouldn't always give us the latest index rebuild time. Here is a solution that will save you time.