@JanThiel opened this Issue on July 8th 2022

Plugins are currently globally activated and thus apply to each website in a single 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.

@MatomoForumNotifications commented on July 8th 2022

This issue has been mentioned on Matomo forums. There might be relevant details there:

https://forum.matomo.org/t/enable-disable-features-on-a-per-user-or-per-website-basis/40188/7

@sgiehl commented on July 11th 2022 Member

Hi @JanThiel
Thanks for your suggestion. I guess for now we need to leave that as it is, and plugin developers need to decide if they want to make their features site specific. Changing that would be a fundamental change in the logic we are currently using plugins. But our product team might consider this for future releases.

@MatomoForumNotifications commented on July 14th 2022

This issue has been mentioned on Matomo forums. There might be relevant details there:

https://forum.matomo.org/t/activate-a-plugin-for-just-one-proprty/46557/5

Powered by GitHub Issue Mirror