In the Summer of 2002, I was 24 years old, single, had a good number of friends who rode motorcycles, and my 1989 Suzuki GSXR 750 just broke down. I purchased the Yamaha Road Star (Star Cycles) Warrior in June, which, at the time, was one of the fastest and best handling power cruisers in the market. Being that I was coming from the sport bike realm, this was the bike for me.
I have a multi-lingual Sitecore (6.2) site that has been having many issues with item versions showing up in their site myseteriously. The client has over 12 languages in their site and certain items shouldn't be accessible to certain languages. Now, Sitecore says simply don't create a version of the item and it won't appear in the site for the language. Perfect? Nope.
This is a topic that I've been meaning to cover for some time now, but it is this post by John West that pushed me to do it sooner rather than later.
I spoke with Jens Mikkelsen and Jimmi Lhyne Anderson from LearnSitecore the other week about who I am, Dreamcore and Team Development for Sitecore.
As a Sitecore developer who is a fan of leveraging Lucene in my projects I've always been aggravated that, starting with Sitecore 6, I couldn't use Luke to view my indexes. As Jens Mikkelsen points out this was due to custom compression that Sitecore uses for the Lucene index.
For one of my the latest projects the content editors were always trying to get the actual URL to a Sitecore media library item, but there is no easy way to see this in Sitecore. As developers we know it is in the form of //media/[ShortID].ashx or //media/[Path].ashx, but editors don't want to think about that. They just want it figured out and displayed in front of them.
This is more of a 'note to self' type post, but I am sure some may find it helpful...
This post if mainly in response to a question that was asked, and subsequent tweet, during my session at Dreamcore 2010.
Disclaimer: While some of these guidelines may be applied to other Content Management Systems, or .net web forms in general, this is based on my experience with Sitecore.
I've recently been doing some work with the Web Forms for Marketers (2.0) module and I must say I was presently surprised! The first version of this module was a rather good first pass, but it typically came up short when we wanted to use it. Version 2 is a big step forward and we are just about to launch a site using it. While it is a great package, and I recommend everyone check it out, it does have some "gotchas."