Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When a plugin activation will cause DB schema changes, issue a warning to user #9668

Open
mattab opened this issue Jan 31, 2016 · 0 comments
Labels
c: Performance For when we could improve the performance / speed of Matomo. c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Stability For issues that make Matomo more stable and reliable to run for sys admins.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Jan 31, 2016

As a user or administrator of Piwik, I can easily "Install" new plugins from the Marketplace. When I click "Install" it redirects to a page which contains the link "Activate plugin". Sometimes, Activating a plugin will cause DB schema change (such as adding new columns). When a plugin will trigger DB schema changes, I would expect to be notified by a warning message, that the process of activating the plugin will take some time.

Example of useful plugins who trigger large DB schema updates:

The Help message would

  • warn users of the risks of activating a plugin that will cause DB schema change (ie. this could take hours)
  • explain to users the risks, and how to run the ./console plugin:activate Plugin_Name command as an alternative to triggering activation via UI.
  • be displayed only there will be a DB schema change

Example failure use case

I have activated the plugin "CustomDimensions" on demo.piwik.org, kinda forgetting it would lead to hours of downtime. It would be nice to help our users prevent such technical challenge 👍

Not in scope

ideally we would follow up with an issue to investigate how to display such warning when updating a plugin to a new version that contains DB schema updates.

@mattab mattab added the c: Usability For issues that let users achieve a defined goal more effectively or efficiently. label Jan 31, 2016
@mattab mattab added this to the 3.0.0 milestone Mar 31, 2016
@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Mar 31, 2016
@mattab mattab added the c: Performance For when we could improve the performance / speed of Matomo. label Nov 4, 2019
@mattab mattab added c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. Stability For issues that make Matomo more stable and reliable to run for sys admins. labels Dec 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Performance For when we could improve the performance / speed of Matomo. c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Stability For issues that make Matomo more stable and reliable to run for sys admins.
Projects
None yet
Development

No branches or pull requests

1 participant