30-11-2012Door Martijn van der Put
In almost every Sitecore implementation there is the need to send personalised emails to the website visitor after filling in a webform, making a purchase or triggering some other kind of action which involves feedback through an email message.
By using Razor Templating Engine the emails can be setup in a very flexible and powerful way without the need to modify your sourcecode.
28-11-2012Door Martijn van der Put
A lot of times there is some ignorance with developers about the possible package installation options. This also included myself. Sort of like an old habit I always use the "overwrite" option for data templates and layouts and the merge-clear option for content-items. But there are more package installation options although the description in the installation wizard popup is a bit misleading.
20-11-2012Door Ruud van Falier
When Sitecore can't find the requested item, it will redirect the user to the page that is configured in the setting ItemNotFoundUrl. The problem is that redirecting will return an HTTP status code 302 (Moved Temporarily) and what we really want is the status code 404 (Not Found).
I've seen solutions where people will set the status code on the 'ItemNotFound' page. That does not solve anything because the client will still be redirected to the ItemNotFound page and the initial request will not be marked as not found.
To solve this problem you can implement this custom pipeline processor.