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

Better Multisite Module Management #866

richardmtl opened this Issue Jul 16, 2014 · 7 comments


None yet
10 participants

richardmtl commented Jul 16, 2014

A user, (who runs a multisite network), wrote in with the following suggestions (slightly edited for clarity):

I still have to go through each individual site and activate/deactivate modules, though from the network I have them all linked to my one account. It would be nice if on the network screen I could activate/deactivate the modules for each site OR there was just a single page with the modules active/inactive and all the sites shared the same module statuses.



This comment has been minimized.

mrjarbenne commented Jul 21, 2014

Rescuing @georgestephanis gif over to this issue from the now closed #247 because solidarity

@georgestephanis georgestephanis modified the milestones: 3.3, 3.2 Oct 1, 2014


This comment has been minimized.


georgestephanis commented Oct 1, 2014

Possibly would fit in 3.3, but we've got something else cooking up shortly that may serve the same use case. More to come shortly.


This comment has been minimized.

nicholasio commented Oct 9, 2014

This feature would be nice, I have a University Site and each sector and course has it's own site, but it's all linked to the main site. I'm using Jetpack but it's suck because I can't configure a module globally. We have more thah 80 sites in the network and it's difficulty to configure the same module on each site.


This comment has been minimized.

mrjarbenne commented Dec 16, 2014

Hey @georgestephanis, It doesn't look like this made it into 3.3. Do you have anything more you can share about the "something else cooking" you mentioned above?

Because this (among other things):

(As an aside, I've been using a variation of this: to block modules, thanks to @blobaugh for pointing me in that direction.)


@lezama lezama modified the milestones: 3.3, 3.4 Dec 16, 2014


This comment has been minimized.


jeherve commented Dec 16, 2014

@mrjarbenne I replied in the thread and created #1427

@jeherve jeherve added the Manage label Dec 16, 2014

@jeherve jeherve modified the milestones: 3.4, 3.5 Jan 28, 2015

@dereksmart dereksmart modified the milestones: 3.6, 3.7 Jun 25, 2015

@samhotchkiss samhotchkiss modified the milestones: 3.7, Needs Triage Aug 28, 2015

@samhotchkiss samhotchkiss removed this from the 3.7 milestone Aug 28, 2015


This comment has been minimized.

mrjarbenne commented Sep 29, 2015

The changelog had a bit of a clue today: "Enhancement: General: Added custom capabilities for module management on multi-site installs"; but I can't find any additional documentation.

Has there been movement in this area?

Updated: Found this: #2688


@zinigor zinigor modified the milestones: Not Core Jetpack Team, Needs Triage, vFuture Dec 1, 2015


This comment has been minimized.

stale bot commented Jul 7, 2018

This issue has been marked as stale. This happened because:

  • It has been inactive in the past 6 months.
  • It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

@stale stale bot added the [Status] Stale label Jul 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment