Agreed. This nearly prevented me from using the plugin, but it’s an easy fix and should be incorporated.
@mark done
@pau thanks for the temporary fix…
Same for me on upgrade from 2.0.5 to 2.1. Holding off on production site update until this is resolved.