Social | Enable connections management for WPCOM sites

[manzoorwanijk]

Related to 168243-ghe-Automattic/wpcom

Proposed changes:

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:

• Use the below matrix to conduct these tests
• Apply 168243-ghe-Automattic/wpcom to your sandbox
• Apply this branch to your sandbox while being on the above wpcom branch, instead of on trunk
• Point the public API to your sandbox
• Test the following on Jetpack, Simple and Atomic sites
• Point the site to your sandbox
• Goto connections management on Jetpack and Social admin page
• Confirm that the connections load fine
• Confirm the same in the editor
• Add/remove a connection
• Confirm that it works as expected
• Mark/unmark a connection as shared
• Confirm that it works fine
• Reload the page
• Confirm that the changes are retained.
• Test the above as an author account
• Verify that you are able to see the "Disconnect" button
• Verify that the author is not able see the "Disconnect" button for shared connections
• Break a few connections
  • For Mastodon, remove Jetpack here.
  • For Facebook, remove Jetpack here.
• Verify that broken connections are marked as such in the connections manage and in the editor notices

Jetpack plugin	Social Plugin	Block editor ✅	Classic editor ✅
Jetpack and Atomic sites
This branch	This branch
This branch	v4.x.x
v12.x.x	This branch

Simple sites
Block editor ✅	Classic editor ✅

[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 Team 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 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? 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 semi-continuously (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for February 4, 2025 (scheduled code freeze on undefined).

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

---

Wpcomsh plugin:

• Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2).

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

[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 WordPress.com Simple 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, and enable the update/social/enable-connections-management-for-wpcom branch.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack update/social/enable-connections-management-for-wpcom
  

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