In my last post I covered sending data to a Send email list, and my last comment was about making sure Authors don't have to jump through hoops to get its Guid. In this post I'll share making this selection a custom field in Content Editor. 

I recently built a helper method for our Send gateway which adds or resubscribe users to specified lists. I reported a bug since resubscribing Users kept reverting to unsubscribed. I'll cover the workaround and the explanation from Send for this behaviour. 

In my last post, I shared a way to hide bucketed folders from Sitecore URLs to make them more SEO friendly. So how do we find an item if part of the standard URL is missing? In this post I'll show you how with the custom URL resolver.

If you've ever seen a bucketed URL, you'd know it. Dates are made to be part of the URL, which allows for a larger number of children under a single parent, when there's usually a limit of 100. This is common in areas like blog postings, press releases, etc. But did you know the date folders can be optional? In this first part of a two-part series, I'll show you how.

In the last article I introduced the Sitecore Auto Dictionary Module, explaining the benefits of using it over the out of the box Dictionary. Today I'll talk to those who are interested in the technical approach to this feature, covering the configuration and use of pipelines it employs.

I'm excited to release this module, because it has the power to save your team a great deal of development time. By using this in our last Sitecore project I saw a reduction in 220 hours of overall effort, which besides the cost savings incentive, gave us a big win by making things easier for the developers and content team. Introducing, the Sitecore Auto Dictionary!

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!

I was recently asked to provide a way for a User to execute a scheduled task immediately instead of waiting for the next scheduled run. Adding a button inside the Content Editor was a useful way to accomplish this, and since I found a few misleading guides online I thought I'd post my own, which is hopefully a lot clearer.