-
Notifications
You must be signed in to change notification settings - Fork 800
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
My Jetpack: replace Creator card with Newsletter #38418
base: trunk
Are you sure you want to change the base?
Conversation
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
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. Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. |
f31d695
to
0896c03
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested mostly well, I left a few comments that i think are important enough to address or talk about before merging 😄
label: __( 'View', 'jetpack-my-jetpack' ), | ||
onClick: () => {}, | ||
}, | ||
[ PRODUCT_STATUSES.MODULE_DISABLED ]: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this PR we've gone towards allowing the user to "Activate" the module/plugin from My Jetpack if at all possible. Could we possibly continue that trend here? Would the activate function work here or is there a reason we need to have the user do it from the settings page?
type DisplayItemType = Record< | ||
// We don't have a card for Security or Extras, and scan is displayed as protect. | ||
Exclude< JetpackModule, 'extras' | 'scan' | 'security' >, | ||
Exclude< JetpackModule, ExcludedModules >, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice improvements with the excludes, thanks!
@@ -0,0 +1,36 @@ | |||
import { __ } from '@wordpress/i18n'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is a brand new file, what do you think about converting it to TypeScript since we are heading that direction in My Jetpack?
if ( Products::STATUS_MODULE_DISABLED === $status && ! Initializer::is_registered() ) { | ||
// If the site has never been connected before, show the "Learn more" CTA. | ||
// It should point to the settings page where the user can manage Newsletter | ||
$status = Products::STATUS_NEEDS_PURCHASE_OR_FREE; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This status has been replaced with STATUS_NEEDS_ACTIVATION in the PR I linked to in a previous comment FYI, you might want to rebase and update that so there are no issues with an undefined constant 😄
Just a note that we also need to update the emails we send when the user upgrades: Should I create a new issue for this, @IanRamosC ? |
Hi @IanRamosC, I just came across this and I'm wondering, what is the status of this work? Are we giving up on it or still want to move it forward? |
Paused until Nov. |
This PR has been marked as stale. This happened because:
If this PR is still useful, please do a [trunk merge or rebase](https://github.com/Automattic/jetpack/blob/trunk/docs/git-workflow.md#keeping-your-branch-up-to-date) and otherwise make sure it's up to date and has clear testing instructions. You may also want to ping possible reviewers in case they've forgotten about it. Please close this PR if you think it's not valid anymore — if you do, please add a brief explanation. If the PR is not updated (or at least commented on) in another month, it will be automatically closed. |
More context: p1HpG7-sYs-p2
Proposed changes:
Not connected:
User connected with settings off:
User connected with settings on:
Other information:
Jetpack product discussion
p1HpG7-sYs-p2
Does this pull request change what data or activity we track or use?
No
Testing instructions: