@ James
I was able to locate and correct the bug! It is now fixed on your site and you no longer receive the error. The fix will be included in the next update as well. Thanks for your help!
