0 Members and 2 Guests are viewing this topic.
So according to that this issue was fixed a while back, we need to update.