Hello,

> Has this bug fix now in 1.6.13 or 1.7.8 ?
> 
> We have confirmed this bug still exists inĀ 1.6.3.

Yes, the fix is in 1.7.4 and 1.6.12.



Regards,
Lukas

Reply via email to