Skip to content
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

Hides the discover more section for non-admin users #41474

Conversation

jboland88
Copy link
Contributor

Proposed changes:

  • This PR hides the "discover more" section on My Jetpack for non-admins. Only admin users can install and activate new Jetpack products, so this section is really only useful for admin users.

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

No

Testing instructions:

  • Check out this branch using Jetpack Beta on a testing site
  • On My Jetpack as an admin user, confirm that you see the "discover more" section on My Jetpack of products the site does not have yet
  • Switch to a non-admin user and go back to My Jetpack. Confirm that the "discover more" section is no longer visible

Copy link
Contributor

github-actions bot commented Jan 31, 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 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 udpate/hide-discover-more-for-non-admins branch.

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

    bin/jetpack-downloader test jetpack udpate/hide-discover-more-for-non-admins
    

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

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 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.


🔴 Action required: Please add missing changelog entries for the following projects: projects/packages/my-jetpack

Use the Jetpack CLI tool to generate changelog entries by running the following command: jetpack changelog add.
Guidelines: /docs/writing-a-good-changelog-entry.md


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!

@github-actions github-actions bot added [Package] My Jetpack [Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you! labels Jan 31, 2025
Copy link
Contributor

github-actions bot commented Jan 31, 2025

Code Coverage Summary

Cannot generate coverage summary while tests are failing. 🤐

Please fix the tests, or re-run the Code coverage job if it was something being flaky.

Full summary · PHP report · JS report

Copy link
Contributor

@CodeyGuyDylan CodeyGuyDylan left a comment

Choose a reason for hiding this comment

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

The change works well, only requesting changes because of a type change that I believe is incorrect

@@ -455,7 +455,7 @@ interface Window {
isAtomic: boolean;
sandboxedDomain: string;
isDevVersion: boolean;
userIsAdmin: string;
userIsAdmin: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

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

This is actually a string
image

We could possibly change that if we wanted to 🤔 I do like booleans better for this sort of thing but currently it is a string 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ah, yep thanks - will put that back :)

#41445)

* Dont show stats module on my Jetpack if user does not have permissions to see it

* a few small updates to stats permission check
@jboland88 jboland88 force-pushed the udpate/hide-discover-more-for-non-admins branch from 0060d83 to 494c17e Compare January 31, 2025 22:28
Copy link
Contributor

@CodeyGuyDylan CodeyGuyDylan left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Contributor

@IanRamosC IanRamosC left a comment

Choose a reason for hiding this comment

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

LGTM!

@jboland88 jboland88 force-pushed the fix/my-jetpack-for-non-admins branch from 2f12118 to 4cc6acc Compare February 3, 2025 22:06
@jboland88 jboland88 merged commit 242b6a8 into fix/my-jetpack-for-non-admins Feb 4, 2025
12 of 14 checks passed
@jboland88 jboland88 deleted the udpate/hide-discover-more-for-non-admins branch February 4, 2025 22:42
@github-actions github-actions bot removed the [Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you! label Feb 4, 2025
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.

3 participants