Perhaps you missed all of the references to 1.6.2.2 posted for this issue? Did you actually *read* the posts in this bug?
Perhaps you missed all of the references to 1.6.2.2 posted for this issue? Did you actually *read* the posts in this bug?