Enable/Disable features on a per 'user' or per 'website' basis?

JThiel · July 8, 2022, 1:19pm

@heurteph-ei Thanks for your feedback.

With >2k open issues on Github I was not convinced that posting there would do any good. But hey, let’s give it a try

github.com/matomo-org/matomo

Allow Plugins to be enabled/disabled on a website level in addition to the default global scope

opened 01:17PM - 08 Jul 22 UTC

JanThiel

Enhancement

Plugins are currently globally activated and thus apply to each website in a sin…gle Matomo installation. There are features delivered via Plugins which might not be required or wanted on a single website. This is kind of the case with the built-in "ecommerce" features which can be enabled on a per site base. ## Summary I propose to add the ability to add Plugins on a per site base in addition to the current only existing default of a "global" activation. This would allow Matomo Admins to optimize larger installations by limiting additional features only to those websites which actually require them. In theory this should allow peformance boosts in the processing as well as the UI. As less features should result in better processing and loading times. I would suggest to allow Plugin devs to determine whether their plugin supports a "global", a "single website" or "both" modes. Whereas a globally activated plugin cannot be disabled for a single website. There are concepts like these in major systems like WordPress. Which allows a much more granular control of the code being executed in the context of a single website. As I do see strong parallels of a WordPress Multisite setup to the way Matomo works for several websites, it would be a beneficial addition to add this level of control. This would also raise the awareness of developers that there is a differentiation required between global settings and per site settings. We just came across such an issue with one of the official Matomo Premium plugins where this was kind of "overlooked" and site specific configs were setup and stored globally. Thus leading to data being globally accessible by admins of a single site who should not have access to the information of other sites.