So...is it fixed for 2.5.2 or for 2.6? because 2.6 isn't due out for nearly two months, which is quite a while to wait for a bug fix. Viper007Bond wrote: > Unless I'm missing something, this has been fixed for upcoming versions as > proven by Matt's blog, so.... >