Yes, it did. There was a whole slew of conflicts caused by trying to use disparate versions of jQuery (1.2.6 in CMSMain, 1.3 in the popup). I really wanted to be able to deploy the DatePickerField into CMSMain, and a lot of people were requesting it, so I had to make a compromise and use an older version of the jQuery UI package to agree with jQuery 1.2.6.

It's temporary, though. The overhaul on the SS javascript framework coming in 2.4 is going to turn this whole thing upside down. Rather than scratch my head over nuisance javascript errors, I'd much rather get something decent in place and wait for a much more functional and extensible foundation is laid down to make it pretty.

Yes I totally agree with your priorities. The thing was that I had some strange hybrid running that was a mix of my old hacks and your new updates. The Date picker still looked like the one from 1.7 but when I checked the scripts it said it was loading 1.6.

Then I did an SVN update and got the ugly one instead. I was just checking to see if this is the way it should be or if I'd wrecked something by mistake again.