Hey Vladmir,
Thank you for reaching out to us!
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 and will be available in our next maintenance release during this week.
I will set this thread’s status to “Pending fix” and link it to our internal bug report so we can let you know once the fix is released.
In the meantime, Benjamin is correct: the only workaround available is downgrading WooCommerce to the previous version 3.1.2.
I apologize for this issue and appreciate your understanding and patience.
If you have any other questions in the meantime, please let me know and I’ll be happy to assist!
Best Regards,
Patricia