Justin, could you please untag this bug ? We already fixed it in v1.8.6.3, according to your suggestions. But this bug is still hanging over the package. How to mark it "fixed" or else ? Thanks Oleg