Hi @lortan29,
Thank you for bringing this issue to our attention!
We apologize for the trouble you are currently experiencing with our plugin. Luckily, a so-called “bug report” (a description of the issue, so we can fix it) is filed already.
What’s next?
Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate when they’ll start working on your report.
If you have any further information that may affect the prioritization or help our development team solve this bug, please feel invited to reply to this forum topic.
Hi @lortan29,
Breaking news!
We just released a new update v14.7 (changelog) few hours ago which should resolve the aforementioned error. Please update your plugin to this latest version and verify the fix.
Let us know if you’ve any further questions or require any assistance from us. We’re happy to help.
Thank you so much!!! All work!