Hey Mon10egro,
We would’ve been glad to offer support if you had asked – it’s always cool when folks can give plugin authors a chance to make an issue right before leaving a bad rating.
The issue was caused by the fact that we were calling load_plugin_textdomain for localization without any translation files present (no translations have been contributed so far, so the .pot isn’t in there yet either). We’ve just committed a new version which should resolve the error described above.
Mon10egro, if you would reconsider your 1-star we’d appreciate it, although of course you have the right to post whatever feedback you like. We wish you the best either way.
