Hello everyone,
Thanks again @tom for the heads-up, and @freyalupen for finding specifically what the problem really was.
I just updated the plugin to the Version 0.4 with a simple hotfix. It should make the plugin fully functional again, and prevent similar problems from this nature again.
Thanks and let me now if anything unexpected arises again.
Cheers.