-
Notifications
You must be signed in to change notification settings - Fork 805
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
Refresh the site's modules and settings after successful product activation #21886
Refresh the site's modules and settings after successful product activation #21886
Conversation
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 (other than "Required review") appearing at the bottom of this PR are passing or skipped. Jetpack plugin:
|
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.
Yes this works as expected. Jetpack Complete shows as the active plan and Instant search and filtering is enabled (automatically, without refreshing the page) after activating the Jetpack Complete license.
LGTM! 👍
It will be hard to test these changes with a JN site due to the reason explained in the PR's description (TL;DR: the request for activating Jetpack Complete times out). If you test it locally, you can hardcode a bigger timeout (say, to 20 seconds) and make it work. Another option is to apply D70690-code to your sandbox and make your JN site rely on it. That small patch should make the activation go faster.
Good catch. I fixed the instruction.
This is the result of the request failing due to the timeout.
Thanks for pointing this out. We will take care of investigating this issue. |
* master: (22 commits) Update storybook monorepo to v6.4.0 (#21897) Refresh the site's modules and settings after successful product activation (#21886) Plugin Install: Bump MC stat on success or fail. (#21893) Nav Unification: Use correct user capability for the Inbox menu item (#21882) Jetpack: Extend disconnection dialog component to handle multiple steps and accept more props (#21048) Disable CSSTidy property shorthand optimization in the editor or headstart (#21891) Connection UI: Update Composer instructions in README.md (#21890) Partner Compatibility: Adding a unique connection screen for customers who receive a coupon from a Jetpack partner (#21813) Search package: move search dashboard to package - the base (#21865) JITM: wrap CTA below text on small viewports (#21688) Licensing JS Package – fix icon positioning and width (#21878) JITM: new JS and CSS builder (#21874) Support site_intent for `/me/sites` endpoint (#21880) Don't render Critical CSS while generating CritCSS. (#21879) ConnectScreen: make button full width on small screens (#21683) Improve the copy of the license activation banner (#21876) Rename Webpack-built files back from `.min.js` and remove hashes (#21748) Search: Migrate more helper classes to package (#21751) Search: migrate/add search rest API (#21584) Add initial state to the connection package (#21864) ...
Fixes 1201096622142517-as-1201431693192886
Changes proposed in this Pull Request:
fetchModules
andfetchSettings
after successful activation of a product. We need these calls to provide a consistent UX that is aligned with the user's expectations. For example, after a user purchases Jetpack Complete, they will expect to have the search feature enabled and working. Without these calls, the user would have to refresh the page to see that. This PR prevents that.Note: there is a known issue that affects the activation of Jetpack Complete. Particularly, the request to activate the license times out. You can bypass that by increasing the timeout from 10 to 20-30 seconds in the
projects/packages/connection/src/class-client.php
file (line 82).Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions:
/wp-admin/admin.php?page=jetpack#/license/activation
.Instant search and filtering
card just below that.JetpackCompleteActivation.mp4