Sorry for all the users who had to endure multiple updates last week. It was due to tracking down and fixing very elusive bug that was affecting small number of users. We are happy to report that in 2.2.8 this issue is no longer appears and we had verify with several users that indeed the problem was fixed. Thanks again for your patience!