We became aware of this issue yesterday. There are a couple of work-arounds for now but we will be working on a free update to address the problem shortly as well. Let us know if you have difficulty implementing one of the proposed work arounds, or post a support incident for help with this directly.