I am seeing a similar issue with version 6.0.2 for the same reason.Did
you end up applying that fix, some other, or just ignoring the issue in
the report? Thanks!
You are leaving our website
You are leaving our site and we cannot be held responsible for the content of external websites