Matt wrote: > I too have noticed this but received no solution =\ I was running 1.2.0 Did you try it again after updating to the latest 1.2 release? Did you report the bug on the bug tracker and provide a backtrace so someone could try to fix it? If not, how did you expect a solution to be created? We aren't telepathic, you know :-)