The purpose of computed fields is to create pre-calculated values when working with indexes. Such approach allows to proceed with the search though distributed data or even when some data is outside the Sitecore (data from the external services could be taken into the Sitecore search engine).
There are many interesting use-cases of how to use computed indexes. I’m going to share some tips to help people get the most of them.
Sitecore is an ideal product to manage complex websites. Editors which don’t have a technical vision but oriented in marketing only – it’s a little bit tricky to understand the custom made things.
Here I will show a few examples of how to implement things on a user friendly manner. That is also nice for the tester and other developers to find quickly the way in the created page templates and components.
It takes some time to make a beautiful and user-friendly Sitecore CMS environment. But at the end a user friendly Sitecore implementation save time and makes it fun to work with. Benice to theeditors, the user friendly cmsimplementationhelp to usethethings as they areintended.
The Sitecore CMS allows you to create multiple versions of the pages for each of the languages supported by your site. Still, sometimes you may want to have particular pages translated into to a certain subset of the languages, e.g. if you have French content that should be available for end users in just France and Canada. The problem is that when you try to access the page in a language which does not have a supported version, you won’t get a 404 error, but be displayed an empty page.
In this document functionality has been described very well. Unfortunately, all screens were from Siteocre 5.3. Also, a few options have been removed and some of them have been updated. So, the new screenshots are provided below. Let’s observe them!
Few days ago I have faced with the situation when some of my templates had had language versions that differs from en.
Firstly I opened Template Manager and navigated to desired template. Then I clicked on Versions tab and was very surprised. There was no button to remove version! There is possibility to save, to switch and to reset, on this tab. Fortunately, Sitecore is a very powerful tool with a lots of different helpful utility pages. One of them saved my life.
Sitecore, by default, provides varies options like Vary by Data, Vary by Query String to enable HTML cache (more information about Sitecore caching could be found here). Sometimes none of these options (based on component built type) help the component to get cached by Sitecore cache.
In this article I will describe how to introduce custom VaryByCache option. It’s pretty simple.
First of all, let’s create a new template where all custom VaryByCache options will be presented.