Howdy Jim,
I’ll respond to your direct communication too, but for the sake of those searching, the feature still works. My initial thought for why it may not be working on your site is where the code is being placed.
Since you’re on a multisite setup, we need to make sure the code is running universally, likely in a mu-plugin.
I’m running into this issue too, and can’t find where this Multisite / Network default module setting is supposed to be managed, if it’s indeed working.
This feature appears to all be commented out in the code (I’m currently looking at Jetpack 4.0.3)? For example, the Jetpack_Nework->set_auto_activated_modules() method’s body is fully commented out, as is the jetpack_get_default_modules filter. The HTML itself for the settings’ form fields is commented out in jetpack/network-settings.php
If you search the codebase for the following text, you’ll find the commented-out features all have this note:
Remove the toggles for 2.9, re-evaluate how they're done and added for a 3.0 release. They don't feel quite right yet.
So is this something that’s been back-burnered, or am I just looking in the wrong places?
@adamnorwood We still haven’t added the UI back, as you’ve realized, but you can use the jetpack_get_default_modules filter to customize the modules enabled on each site in a Multisite network. The jetpack_get_available_modules filter can be useful too.
You could, for example, use the filter in a network enabled plugin or in a mu-plugin to apply the same customizations to each site in the network. Another option would be to create a plugin that would use the same filter, but apply different customizations based on the site ID in your network.
Here are a few resources that can help you:
https://jeremy.hu/customize-the-list-of-modules-available-in-jetpack/
https://developer.jetpack.com/hooks/jetpack_get_default_modules/
https://developer.jetpack.com/hooks/jetpack_get_available_modules/
