I was able to identify the location of the issue from another poster. Thanks for the report, the issue should be fixed now.
