> This bug is definitely still open. I ran into the same exact issue
> today.

Hi,

did you find this issue in versions 3.2.x or only in 3.0.x ?

Cheers,
Xavier

Reply via email to