Hi @rbennett,
Thank you for bringing this to our attention. We apologize for any inconvenience caused by the recent plugin update. It’s great to hear that rolling back to version 2.0.11 resolved the critical error.
Can you please provide the details of the issues? Our development team is actively investigating the issue to identify and address the root cause of the problem. Your detailed feedback is valuable in helping us improve the stability and performance of our plugins.
If you encounter any further issues or have additional feedback, please don’t hesitate to reach out.
Best regards,
