You might find this useful if you don’t already know about it. I ran into a problem the other day where the tagging section did not work properly. No tags at all were displayed for selection, I suspected that there was something wrong with the search in the field. You can find all the info you need to debug this and just copy + paste in the search log and your favorite index viewer. Continue reading A tip on debugging Sitecore search
In the official documentation you can read that Sitecore will choose index based on the RootPath in the crawler and based on the placing in the web.config.
Basically if you create an index that indexes everything under /sitecore/content/home/products you will need to get that index defined before for example the master index in the web.config otherwise your new index will not be considered at all. But what does actually happen here? Continue reading How does Sitecore ContentSearch determine which index to use
Have you ever wanted to add a second database so you can keep millions of items in it and not having to publish it?
Well, to be honest me neither until a few days ago. The scenario is that you have lots and lots of data in other systems (PIM, DAM, Pdf-library or whatever). You want this data to be accessible in Sitecore but you do not want to publish it since that will take forever and cause all sorts of problems.
So in this case you could keep all that data in the second master database (in a bucket of course, since the content tree will be quite hard to handle otherwise). Continue reading Adding a second master database
In Sitecore 7.1 the new indexes are very powerful and allow you to do stuff easily that in Sitecore 6 took quite an effort. An example of that is if you want to tag items and show lists of the items based on the tagging. This can be achieved with a computed index field and some good old Sitecore work. So lets look at the first part of the task and add a tag to the index at hand. Continue reading How to create a Computed index field