The issue is still present on version 3.13.1 of the plugin.
It seems that the 2.7.11 release fixed it? At least, I’ve not been able to replicate the issue on any recent versions.
-
This reply was modified 1 month, 3 weeks ago by devadddesign.
-
This reply was modified 1 month, 3 weeks ago by devadddesign.