Skip to content

Connection: protected owner errors manual fix #43593

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

Open
wants to merge 12 commits into
base: trunk
Choose a base branch
from

Conversation

bindlegirl
Copy link
Contributor

@bindlegirl bindlegirl commented May 23, 2025

Related to: VULCAN-86
P2: pghT6q-3V-p2

Proposed changes:

  • Adding filter to Error_Handler class so wpcomsh can plug in with Protected owner errors.
  • Adapted js components to handle protected owner errors and display a different button that redirects users to account creation.

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:

Copy link
Contributor

github-actions bot commented May 23, 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 add/protected_owner_error_manual branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack add/protected_owner_error_manual
bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/protected_owner_error_manual

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 github-actions bot added [Package] Connection [Package] My Jetpack [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] In Progress Admin Page React-powered dashboard under the Jetpack menu labels May 23, 2025
Copy link
Contributor

github-actions bot commented May 23, 2025

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: June 3, 2025
    • Code freeze: June 2, 2025

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

@github-actions github-actions bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label May 23, 2025
Copy link

jp-launch-control bot commented May 23, 2025

Code Coverage Summary

Coverage changed in 3 files.

File Coverage Δ% Δ Uncovered
projects/plugins/jetpack/_inc/client/components/jetpack-notices/jetpack-connection-errors.jsx 2/17 (11.76%) -1.57% 2 ❤️‍🩹
projects/packages/my-jetpack/_inc/hooks/use-notification-watcher/use-connection-errors-notice.tsx 25/25 (100.00%) 100.00% -18 💚
projects/packages/connection/src/class-error-handler.php 186/244 (76.23%) 11.79% -22 💚

Full summary · PHP report · JS report

@bindlegirl bindlegirl force-pushed the add/protected_owner_error_manual branch from 46b524f to 108bade Compare May 26, 2025 11:09
@bindlegirl bindlegirl self-assigned this May 26, 2025
@bindlegirl bindlegirl requested a review from fgiannar May 26, 2025 11:10
@bindlegirl bindlegirl marked this pull request as ready for review May 26, 2025 11:45
@bindlegirl bindlegirl added [Type] Feature Development of a new feature [Status] Needs Review This PR is ready for review. and removed [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. [Status] In Progress labels May 26, 2025
@@ -11,7 +11,9 @@ import useRestoreConnection from '../../hooks/use-restore-connection/index.jsx';
*/
export default function useConnectionErrorNotice() {
const { connectionErrors } = useConnection( {} );

Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need these changes here?

'invalid_connection_owner',
);

// Automatically include any error codes that aren't in the default list
Copy link
Contributor

Choose a reason for hiding this comment

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

As we discussed, I think it's safer to hardcode the error code coming from wpcomsh here and also add it in the $known_errors list.
The concept of this class is that we only allow verified connection errors to show up.
An exception is the invalid_connection_owner which is not verified but is set by the same package so it's safe.
The filter we introduced is enough to allow wpcomsh to handle it's own connection errors without storing them but I don't see any other plugin handling connection errors.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed in latest comit

Copy link
Contributor

@fgiannar fgiannar left a comment

Choose a reason for hiding this comment

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

This is what I see when I create the missing user manually:

Screenshot 2025-05-29 at 15 28 58

I was testing with a secondary non-connected admin. I was under the impression that we only display errors for the current user when the error has user_id set. Isn't this the case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Admin Page React-powered dashboard under the Jetpack menu [JS Package] Connection [Package] Connection [Package] My Jetpack [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ RNA [Status] Needs Review This PR is ready for review. [Tests] Includes Tests [Type] Feature Development of a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants