Skip to content

Conversation

@mmtr
Copy link
Member

@mmtr mmtr commented Nov 19, 2025

Fixes DOTSITE-14

Proposed changes:

Registers a new "Users > Private Viewers" on private sites where users can view and manage the viewers that have access to the site:

Screenshot 2025-11-21 at 16 31 22

Since integrating the viewers in wp-admin/users.php screen is not worth it given the complexity required (see 171239-ghe-Automattic/wpcom), this PR explores a separate table as a middle ground solution.

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

N/A

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

No

Testing instructions:

  • Apply these changes to your WP.com private site
  • Go to wordpress.com/people/team and select your WP.com private site
  • Add some viewers
  • Go to Users > Private Viewers
  • Make sure you can see all the viewers
  • Make sure you can remove active viewers
  • Make sure you can resend invites to pending viewers
  • Make sure you can remove pending invites
  • Make sure the primary "Add viewer" button redirects to the relevant "add new user" screen depending on the site and admin interface
  • Go to Settings > Reading and make your site public
  • Make sure that Users > Private Viewers is not available
  • Make sure these changes work on both Simple and Atomic

@mmtr mmtr self-assigned this Nov 19, 2025
@mmtr mmtr added [Status] In Progress [Type] Task I don't care about code coverage for this PR Use this label to ignore the check for insufficient code coveage. labels Nov 19, 2025
@github-actions
Copy link
Contributor

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!

@github-actions
Copy link
Contributor

github-actions bot commented Nov 19, 2025

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 or WordPress.com Site Helper), and enable the dotsite-14-viewers-not-displayed-in-classic-wp-admin-dashboard branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack dotsite-14-viewers-not-displayed-in-classic-wp-admin-dashboard
bin/jetpack-downloader test jetpack-mu-wpcom-plugin dotsite-14-viewers-not-displayed-in-classic-wp-admin-dashboard

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

@jp-launch-control
Copy link

jp-launch-control bot commented Nov 19, 2025

Code Coverage Summary

Coverage changed in 1 file.

File Coverage Δ% Δ Uncovered
projects/packages/jetpack-mu-wpcom/src/class-jetpack-mu-wpcom.php 0/328 (0.00%) 0.00% 1 ❤️‍🩹

1 file is newly checked for coverage.

File Coverage
projects/packages/jetpack-mu-wpcom/src/features/private-viewers/private-viewers.php 0/32 (0.00%) 💔

Full summary · PHP report · JS report

Coverage check overridden by I don't care about code coverage for this PR Use this label to ignore the check for insufficient code coveage. .

Comment on lines +73 to +85
// Helper function to fetch a single batch of invites.
const fetchInvitesBatch = async ( offset: number ) => {
const path = addQueryArgs( `/sites/${ window.wpcomPrivateViewers.siteId }/invites`, {
offset,
number: batchSize,
status: 'all',
role: window.wpcomPrivateViewers.viewerRole,
} );
return await wpcomRequest< { invites: Invite[]; found: number } >( {
path,
apiVersion: '1',
} );
};
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some reason this request is not triggered on Atomic sites, even though there are no JS errors 🤔

Image

The wpcomPrivateViewers global is defined, so I don't know what's going here.

Image

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants