Thanks, again, Frank. That, too, is a boo-boo. I've got it noted in the plugin's GitHub issues and hope to have a solution real-soon-now.