Hi, I am facing with the same bug on 5.2.10.Final version. Are there any plans to fix it in future releases?
Thanks.