Yeah, I'm unsure if this bug is new to this version or if it was present the whole time.
Awesome! thanks for letting me know about this issue! I've update the plugin to version 1.5.2, it should now resolve this problem ^^
It works! Thank you so much!
