WordPress / WordPress/gutenberg
Enable Support for Site-Specific Plugin Activation in Multisite
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 4.9k
- PR merge metrics
- PR metrics pending
Description
#What Problem Does This Address?
I am looking to utilize WooCommerce fully under the /store/ subdirectory of my WordPress Multisite setup to enhance performance. However, I have encountered a significant limitation: in a Multisite environment, plugins can only be activated at the network level. This means that all sites within the network share the same set of plugins, which can lead to performance issues. The inability to activate
specific plugins for individual sites restricts my ability to optimize each site's functionality based on its unique requirements.
#What Is Your Proposed Solution?
I propose the implementation of a feature that allows for the activation of different plugins on a per-site basis within a WordPress Multisite network. By enabling site-specific plugin management, I would be able to tailor the plugin usage for each site according to its specific needs. This flexibility would lead to significant performance improvements, as each site could utilize only the essential plugins required for its functionality, thereby reducing overhead and enhancing load times. This revised version clearly outlines the problem and proposed solution while maintaining a professional tone. It emphasizes the need for flexibility in plugin management within a Multisite environment and highlights the potential benefits of such a feature.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by reviewing how WordPress Multisite currently handles network-level plugin activation, then define the per-site activation behavior and tests needed to confirm that sites can use different plugin sets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wordpress
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100