Hi There!
Thanks for taking your time to report this.
We unfortunately are aware of this issue which was introduced by a conflict with the latest WooCommerce 3.2 update. Our dev team has already found a fix for it but will be available in our next maintenance release next week.
I will set this thread’s status to “Pending fix” and link it to the report so we can let you know once a bug fix is released.
In the meantime, the only workaround we’ve found so far is downgrading WooCommerce to the previous version 3.1.2
I apologise for this inconvenience and we’d appreciate your patience.
Best,
Victor