If you saw my post yesterday about adding a preview link to sites, you might come to the conclusion that I've added a 2^nd publishing target. Works great, but if publishable dates are set, nothing will get published to this new preview target. I've created a simple processor to handle this.

I've had a deluge of requests for a walkthrough of my latest module and the way it can help with excessive garbage data in the xDB. In this video I'll introduce the xDB to non-developers, talk about identifying the cyber attack, and how we can ignore/not capture the false traffic to your site.

It's taken years of managing Sitecore sites for this one to come across my desk, but apparently there's no protection for the UserAgent value being longer than the maximum allowed length when saving the User's session to the xDB. Though it's fixed since version 10, there's no patch for earlier instances, so we're going to have to add our own pipeline processor to cut the offending UserAgent values short.

Redirects can be managed in a few different ways, but when a client asked for hundreds of them to be authorable off the home page, well, that took my favourites out of the option list. This request is a little unique with the solution leveraging buckets and RedirectOnItemNotFound. 

Going live with a new Sitecore implementation and getting over 30 times the load you were expecting can be a bit of a shock! So, when we saw 120,000 hits per HOUR instead of the 3,000, we expected, adjustments needed to be made. Here's how we programmatically stored an array of 404 pages to drop demand on the servers in a huge way.

We recently migrated our DevOps instances which involved creating new pipelines, build agents, etc. On first run I started getting errors with the TDS projects that weren't happening on local, which weren't too descriptive. The solution was easy, but understanding what's wrong wasn't.

Sitecore won't handle a page request as a 404 if the context language is missing. So, what this means, is your Users will just see  a blank page should the item exist in English but there's no French version, and they're requesting the French page. We need to override HttpRequestProcessor and  ExecuteRequest to make this a friendly experience for your Users. Let's get started!

In my post, How to Add Custom Buttons to the Content Editor Ribbon, I showed a snippet near the end that executes an import function. One small problem I came across, is that an agent won't work well with a method that has optional parameters.

Since the release of Sitecore 9+ we're seeing a lot of people posting in forums cases where they see errors related to indexes not found. Correcting this Sitecore startup issue was simple to fix once I figured out what's going on, and it's nothing related to indexes at all! 

There's no reason why you shouldn't be bundling your assets as it cuts down on requests by your Users. One thing about it, is the bundles are defined in the BudleConfig class on application startup. This means you have to re-deploy if the bundles need changing, so let's use Sitecore Config and Pipelines instead.