@
No worries and actually yes it was fixed actually after updating the plugin from v0.6 to v0.7. Thanks.