My Jetpack | Enable access to My Jetpack on WP multisite

[manzoorwanijk]

Currently, access to My Jetpack is disabled. See #23069.

Fixes MYJP-105, MYJP-222

Proposed changes:

• Enable access to My Jetpack on multisite
• Show a warning for products and modules not available on multisite based on https://jetpack.com/support/multisite/#unsupported-features

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• Create a WP multisite on JN.
  • Expand the "Jetpack Live Branches" below
  • Under "Settings", check "Multisite based on subdirectories"
  • Then open the link to create the site
• Activate Jetpack Network wide.
• Apart from the main site, create another test site
• Go to its My Jetpack
• Confirm that the page is accessible
• Complete onboarding
• Goto Products tab
• Confirm that you see the unavailability warning for Backup, Firewall, and Ads as mentioned in support docs.

Small screens

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the fix/my-jetpack/multisite-access branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/my-jetpack/multisite-access

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: August 5, 2025
  • Code freeze: August 4, 2025

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Backup plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Boost plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Search plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Social plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Starter Plugin plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Protect plugin:

• Next scheduled release: September 1, 2025

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Videopress plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[Copilot]

Pull Request Overview

Enables the My Jetpack interface on WordPress Multisite and updates changelogs across plugins and packages.

• Remove the multisite guard in should_initialize() so My Jetpack loads on multisite sites
• Add consistent changelog entries in all affected plugins and the my-jetpack package
• Note: one plugin (jetpack) uses Type: enhancement while others use Type: changed

Reviewed Changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
projects/plugins/videopress/changelog/fix-my-jetpack-multisite-access	Add changelog entry enabling My Jetpack on multisite
projects/plugins/starter-plugin/changelog/fix-my-jetpack-multisite-access	Add changelog entry enabling My Jetpack on multisite
projects/plugins/social/changelog/fix-my-jetpack-multisite-access	Add changelog entry enabling My Jetpack on multisite
projects/plugins/search/changelog/fix-my-jetpack-multisite-access	Add changelog entry enabling My Jetpack on multisite
projects/plugins/protect/changelog/fix-my-jetpack-multisite-access	Add changelog entry enabling My Jetpack on multisite
projects/plugins/jetpack/changelog/fix-my-jetpack-multisite-access	Add changelog entry (Type: enhancement)
projects/plugins/boost/changelog/fix-my-jetpack-multisite-access	Add changelog entry enabling My Jetpack on multisite
projects/plugins/backup/changelog/fix-my-jetpack-multisite-access	Add changelog entry enabling My Jetpack on multisite
projects/packages/my-jetpack/src/class-initializer.php	Remove is_multisite() guard in should_initialize()
projects/packages/my-jetpack/changelog/fix-my-jetpack-multisite-access	Add changelog entry for multisite support

Comments suppressed due to low confidence (2)

projects/packages/my-jetpack/src/class-initializer.php:515

• Consider adding unit or integration tests to cover the multisite scenario for should_initialize(), ensuring that My Jetpack initializes correctly on multisite installations.

	public static function should_initialize() {

projects/packages/my-jetpack/src/class-initializer.php:518

• [nitpick] It may be helpful to document the removal of the multisite restriction here, explaining why My Jetpack now initializes on multisite contexts.

		// All options presented in My Jetpack require a connection to WordPress.com.

[jp-launch-control]

Code Coverage Summary

Coverage changed in 5 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/my-jetpack/_inc/components/my-jetpack-tab-panel/products/utils.ts	0/20 (0.00%)	0.00%	4 💔
projects/packages/my-jetpack/_inc/components/my-jetpack-tab-panel/products/constants.ts	0/8 (0.00%)	0.00%	2 ❤️‍🩹
projects/packages/my-jetpack/_inc/components/modules-list/index.tsx	0/9 (0.00%)	0.00%	1 ❤️‍🩹
projects/packages/my-jetpack/_inc/components/my-jetpack-tab-panel/products/product-card.tsx	0/4 (0.00%)	0.00%	1 ❤️‍🩹
projects/packages/my-jetpack/src/class-initializer.php	54/298 (18.12%)	-0.21%	-1 💚

1 file is newly checked for coverage.

File	Coverage
projects/packages/my-jetpack/_inc/components/modules-list/utils.ts	0/5 (0.00%) 💔

Full summary · PHP report · JS report

_{Coverage check overridden by Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR .}

[jeherve]

Some extra references that may be helpful: #35555, #43012

[robertsreberski]

I was able to activate all products and modules, no errors! thank you, it's a big milestone since we disabled it in 2022.

We should be sure to loop in our HEs (@StefMattana!) cause it will be a big change for our users, and we will need to update support docs.

[robertsreberski]

I think this function could be immutable, it might be easier to read and extend in the future

[manzoorwanijk]

I am not sure I understand what you mean by that.

[robertsreberski]

I meant that instead of using variables (let), we could just use early returns that will make it clearer (in my opinion) of what is actually the output of the function in every code path.

[StefMattana]

That's great @robertsreberski, thanks for the heads up!
I created a doc request for it: JPHDOC-190

I didn't set an ETA in the Doc Linear request above; I'll follow closely but happy to get a ping from you when it's ready to be deployed in a new JP plugin update 🙂

[robertsreberski]

A small remark about the code approach in functions. I do prefer to avoid using variables in js/ts when it's unnecessary

[robertsreberski]

I meant that instead of using variables (let), we could just use early returns that will make it clearer (in my opinion) of what is actually the output of the function in every code path.