@webdesko. I have released version 3.0.1, which has the fix for that error. Please find the updated file at this direct link.

Thanks for reporting the issue. I apologize for the inconvenience.