@hpvd do you know if we currently check for new updates for deactivated plugins? we definitely should, I guess.

I think Piwik doesn't check and doesn't update deactivated plugins -that's why I opened this issues...
(but as always I didn't check the code if it shouldn't do)
btw: merry x-mas!

imho this is pretty important and one should not push this to the far future... (see the 3 reasons above)
What do you think?

AFAIK and I had a rough look in the code we do check for all plugins here: https://github.com/piwik/piwik/blob/3.0.0/plugins/Marketplace/Plugins.php#L167-L169 This should include deactivated ones.

Many thanks for looking in the code!

I just had a deeper look too:
You are right! It's no general problem.
Most are updated but not all.

e.g. in my installation AOM plugin is installed, but deactivated and it's not updated.
Noticed that there are several new versions by looking at it's github page.

Looking in Piwik's integrated Marketplace, I couldn't even find it anymore.
("huu... was it banned for some reason?")
Looking for it on https://plugins.piwik.org directly I managed to find it.
("hmm, why is there a difference to internal view?")

When looking into it's details I realized that it has requirements Piwik <3.0.0b1

So there is simply no compatibility version for Piwik 3.

=> With this we need a better handling not for deactivated,
but for deactivated and not compatible anymore plugins.

some ideas:

• should one update them even if latest version is not compatible to current piwik version (e.g. for security reason)?
• do not show "activate"-Link in list of installed plugins if not compatible to current version
• show a hint instead "not compatible to current piwik version"
• do not make them disappear in internal marketplace view, make it transparent and show "not compatible for your piwik version"
• add a filter for plugin search "not compatible"/"other piwik versions" (so one can still find the plugin and ask the author for an update...)

So it should already more or less work. AOM wasn't updated because there was no 3.0 compatible release at the time. Closing this issue @hpvd but feel free to open separate requests for your suggestions / the ones you think are most important.