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.
I recently discovered a serious issue with our SEO-friendly URL module.
Solving that issue has taught me something new about the way Sitecore handles incoming requests, that Sitecore has recently made some changes to this behaviour and that you shouldn't use a certain combination of configuration.
Enough reason to share this information with others!
One of the most requested features for our Sitecore implementations is URL rewriting; the ability to permanently redirect a requested URL to a different URL.
We have built this functionality some time ago and recently decided to release it as a stand-alone module so that everyone can use it in their own Sitecore solution.
This blog post describes what the module does and how to use it.
The Sitecore Content Editor offers you commands to copy and paste items.
But what if you don't want to copy an entire item, but just one version?
Sitecore doesn't offer a solution for this out of the box.
Our Copy Version module adds a new version of the Copy, Paste and Copy To command that allow you to copy the latest version of an item to another item.
Pasting the version to an item will create a new version with a copy of the original version.
In ASP.NET applications you can catch all application exceptions in the Application_Error event handler in the global.asax.
When you use Sitecore MVC, this event is not fired by default.
It took me a while to figure out why this is, so I decided to write a short blog post about it.
A common requirement for many Sitecore solutions is applying caching to certain areas of the application.
For example, on a service manager, an abstraction layer inbetween external services and the web application.
This blog post describes an example of an implementation of a caching layer that is reusable and does not require the existing logic to be modified.
It works by adding an attribute to the method that needs to be cached, marking it as cacheable.
Here is another handy command for the Sitecore client.
It's added to the context menu of the Content Editor tree and expands all descendants of the selected item with one click.
We have release the SEO-friendly URL module that we use in all our Sitecore projects.
This blog post explains how it works and how you can use it in your own projects.
Today was an important day for all Sitecore enthusiasts; the long awaited Sitecore 7 was released to the public!
I was lucky enough to get an early peek at this release, as did all other MVP’s, and therefore new beforehand that this one would be well worth the waiting.
It comes with an exciting new – super fast – search API along with UI changes that enable content editors to use the search features for content management (or should I call it customer engagement these days?)
Yesterday, all European MVP's got the chance to meet with part of the Sitecore 7 development team at Sitecore's UK office in London for an in-depth insight in Sitecore’s new search features.
It was a fantastic session that went really deep into the mechanics of the search and we were left with a brain full of new information and almost no questions to ask.