There is a fix for this issue, but it was not included in the 4.5.2 release as the fix was made too late to include in the release. I have sent you an updated file in the backend ticket. If anyone else encounters this issue, please post here and I will get the fix to you.