Thanks for the reply!
Just a suggestion — since this issue caused a fatal error and was fixed by removing a single line in a plugin file, it might be worth reviewing this in the plugin code so that other users don’t run into the same problem.
Would be great to see it fixed in a future update.
Thanks again!