This is likely the [following issue]( Version 1.5.1, 2.1.1 & 3.0.1 - Now Available! for Testing! page-5#post-5950703) which has been resolved as per the [following post]( Version 1.5.1, 2.1.1 & 3.0.1 - Now Available! for Testing! page-5#post-5950703).