Many of the Sitecore solutions I encounter during my work as a Sitecore Consultant face the same performance issue as a result of publishing items;
When a content editor publishes an item, the website performance goes down for a short period of time.
In this blog post I will describe why that happens and I will explain a proof of concept that I made that solves this issue.
A couple of weeks ago I walked into an open meeting room where a Sitecore training provided by Ruud was on a break. I had a quick peek of what they would be discussing after the break and had a moment of clarity. Can we have a field editor available on every component, without having to define all fields every single time?
Some users have been experiencing an issue with our URL Rewriter module that caused it to throw an exception during initialization that resulted in the module not working until the application pool was recycled.
We have released an update that should fix that issue for all instances.
Sitecore 7.5 ships with a new binary named Sitecore.Abstractions.dll This offers you abstractions for some parts of the Sitecore API that are implemented as static classes in the kernel.
Following up on my previous blog post about "Isolating Sitecore pipeline processors and event handlers", I'd also like to share this more generic way of making pipeline processors and event handlers configurable.
When I implement custom pipeline processors (or events), I like to isolate them so they are executed only for specific sites.
I've written an abstract class that I can use on all my pipeline processors to implement support for this type of isolation.
I recently came across a Sitecore instance that displayed information about the version of the custom binaries in the Sitecore login screen.
It seems like a useful thing to do, but I don't think a lot of people know how to do it (including me until I saw this instance).
Turns out it's very easy!
A quick heads up on how to always run Visual Studio with elevated permissions.
This article explains how to figure out exactly what source code has been changed in between two versions of Sitecore.
I find that it can be very useful in some cases and potentially save you a lot of time.
This article points out the fact that Sitecore configuration include files are loaded in alphabetical order and explain how to deal with this in your solution.