Plugins incompatible with new v0.21.0 API?

[mojolo]

Thank you for all your hard work in creating these awesome plugins. Unfortunately, none of my locally installed awesome plugins show up in Albert's plugin settings. Here's an example of the debut output for a few of them:

[warn:python] Plugin invalid: Incompatible major interface version. Expected 1, got 0. (/home/XXX/.local/share/albert/python/plugins/abbr)
[debg:python] Found valid Python plugin /home/XXX/.local/share/albert/python/plugins/abbr
[warn:python] Plugin invalid: Incompatible major interface version. Expected 1, got 0. (/home/XXX/.local/share/albert/python/plugins/colors)
[debg:python] Found valid Python plugin /home/XXX/.local/share/albert/python/plugins/colors
[warn:python] Plugin invalid: Incompatible major interface version. Expected 1, got 0. (/home/XXX/.local/share/albert/python/plugins/emoji)
[debg:python] Found valid Python plugin /home/XXX/.local/share/albert/python/plugins/emoji

I saw that awesome albert plugins were recently updated, per #20

It looks like Albert's plugin interface has changed again. See: v0.21.0 changelog:

[plugins]
    ...
    [python:1.8] Adopt API v0.21. New interface version iid 1.0
        Add Extension.cache-, config- and dataLocation
        Expose FallbackHandler
        Proper multi extension registration
        Move interface spec into python stub file (yay!)
        Expose TriggerQueryHandler
        Expose GlobalQueryHandler
        Expose QueryHandler
        Expose IndexQueryHandler
        Expose Item class entirely such that plugins can subclass it
        Use pointer for queries
        Remove global cache/config/data dir functions
    [all] Adopt API v0.21.0

I hope it is not too much work for you to have to update them again.

[bergercookie]

Hi there and sorry for the late reply. You're right. The albert python API changed literally after I migrated the plugins to the one before the 0.21.0 😓

At some point I'll port them to the new one but that may take a while.