Forums
(@tylerwm94)
2 years, 9 months ago
Thank you! Reverting to version 2.6.11 of the plugin fixed the issue. Hopefully, they will fix this bug in a future version.