Numerous times in recent years I’ve had to use Reflector Pro to debug third-party dlls. While this works well and allows you to step through code as if it was your own the value of doing so can be completely lost if you cannot see critical object values due them being ‘optimized away’.
Recently I was stuck with a problem of optimization that refused to be disabled by the usual means that I’d used in the past. I stumbled onto a neat trick which finally did work, but it also clarified what happens when the web application, usually Sitecore CMS, restarts.
Sitecore uses the extensive log4net logging framework to handle the large volume of logging entries it generates. Sometimes vague log entries can leave you scratching around trying to find where they originated from. This post explores some simple steps to add useful detail to, and real-time viewing of, the Sitecore log.
Using the new Sitecore contentsearch api allows you search against a lucene index with very little effort. Examples are a bit short on the ground but using Linq you can find yourself doing something like this to search for an item by name, somewhere within a folder structure:
public void BadSearch(string searchTerm)
var webIndex = ContentSearchManager.GetIndex("sitecore_web_index");
using (var context = webIndex.CreateSearchContext())
var results = context.GetQueryable<SearchResultItem>().Where(i =>
i.Name == searchTerm &&
i.Path.StartsWith("sitecore/content/stuff/")); // don't do this!
This may well work. However you may also run into a Lucene error stating that you are using too many clauses, the default limit is 1024.
This XmlException can occur within a Sitecore site where a general link field contains just plain text, for example a template flipped from link field to text field or just editing in raw.
Clear the field and re-populate with a valid target.