Please also fix this in the next 5.2.13 release, thanks. As far as I can see this is not in the 5.2 branch yet...