Thanks for reporting this issue. We will fix this on our next plugin update.