chapcrap wrote:Gillipig wrote:And somebody should fix the underlying problem. This update is clearly not appreciated by the TO's, why else would the natural response be that it must be some kind of bug?
It's already been stated somewhere else that they are working on a fix for this.
I'm hoping it will come soon.
working, they were made aware this would be a problem 1 month prior to implementing this