0 Members and 1 Guest are viewing this topic.
Is the bug still there in the just released v2 of 3.2.2 update?