I fixed this issue by applying the patch in Update#0, but if this is fixed in 3.2.5, then this bug can be closed.
I fixed this issue by applying the patch in Update#0, but if this is fixed in 3.2.5, then this bug can be closed.