If you've ever spent time screwing around with javascript and custom columns trying to get color coding functionality out of a Sharepoint calendar, you will LOVE Mark Wilson's Colour Calendar v2.3.
It's a nicely packaged solution that works on both WSS3.0 and MOSS2007 and seems to work quite well. I've been playing around with it on a test server for a couple of days now and I'm really impressed with how easily it just works. You basically deploy the feature on the site, Activate it, and enable it on whatever Calendar you want - and it takes it from there. It creates custom lists and content types and ties everything together so you basically don't have to do anything manually if you don't want to. After activation, adding new calendar entries will give you a new dropdown/choice field for Event Category that controls what color is shown. There are several defaults included, or you can modify/create your own.
I do have one question I need to ask Mark though about using custom color lists instead of inheriting the defaults from the root site. Most of our sites are full Site Collections off the root/sites/.. setup - and whenever I Activate the feature on a Site Collection, it sets everything up and works just fine.. but it strangly creates a Color Mapping List that it simply doesn't use. By default it's pointed back to the root site's List - and I've tried changing the one at the Site Collection level and then pointing it to this modified List - but it doesn't seem to like it... but you can create a brand new Color Mapping List in your Site Collection - and it seems to take that one just fine.
So anyway, I'm sure there's some method to the madness. I probably just haven't spent enough time with it to get my head around it.
It could probably use a little more detail in the documentation concerning setting up/modifying these Custom Color Mapping Lists - but aside from that, the thing still works beautifully. Especially if you don't want custom colors - then it's a total no-brainer. I'm sure my situation is simply "Operator Error".
0 comments:
Post a Comment