Goal: introduce a mechanism to disable plugin on upgrade to a more recent Piwik core version. This is part of making Piwik the best open platform for data analytics!
Example Use case
- A plugin requires Piwik`
=2.0,<2.4`
- User upgrades from Piwik 2.1.0 to 2.4.0
- On the page that says "Click to update automatically or download to update manually"
- we add the following message if any plugin requires a version that will not be met after upgrade.
- After the upgrade, Piwik core should detect that there is currently an "activated" plugin that does not meet the "require" found in plugin.json. Piwik core should then "deactivate" this plugin.
- In the "Manage > Plugins" screen, when user clicks "Activate" on the plugin, show the following message in the page (either full page error or notification are OK) "EnterpriseAdmin requires Piwik <= 2.2.0. Please [here to email $Developer_Name /email_link and enquire about an updated version of EnterpriseAdmin."
Message in the pre-Upgrade screen
Note: some plugins are not compatible with Piwik 2.4.0. They will be disabled when you upgrade:
- EnterpriseAdmin requires Piwik <= 2.2.0. Please [here to email $Developer_Name /email_link and enquire about an updated version of EnterpriseAdmin.
- Plugin2 requires Piwik <= 2.2.8. Please [here to email $Developer_Name /email_link and enquire about an updated version of Plugin2.
Refs
Goal: introduce a mechanism to disable plugin on upgrade to a more recent Piwik core version. This is part of making Piwik the best open platform for data analytics!
Example Use case
Message in the pre-Upgrade screen
Note: some plugins are not compatible with Piwik 2.4.0. They will be disabled when you upgrade:
Refs