Hi ,
It looks like a separate fix in 4.13 has fixed this error. If you experience this error when 4.13 is live, please post back here and we will have another look.
Hi ,
It looks like a separate fix in 4.13 has fixed this error. If you experience this error when 4.13 is live, please post back here and we will have another look.