-
Notifications
You must be signed in to change notification settings - Fork 799
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
Blocks: deprecate the server-side rendered nudges #18054
Conversation
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.
Here are some suggested test cases for this PR.
Gutenberg extensions
- Use Core's block editor
- Use latest stable Gutenberg plugin
Blocks
- Tiled Gallery
- Business Hours
- Calendly
- Form
- Contact Info
- Eventbrite
- Google calendar
- Mailchimp
- Map
- OpenTable
- Podcast player
- Star rating
- Recurring Payments
- Repeat Visitor
- Revue
- Simple Payments
- Slideshow
Extensions
- Publicize
- Likes
If you think that suggestions should be improved please edit the configuration file here. You can also modify/add test-suites to be used in the configuration file.
Scheduled Jetpack release: January 12, 2021. Thank you for the great PR description! When this PR is ready for review, please apply the |
Nice, this would indeed allow us to get rid of a ton of code, and unblock the wordpress monorepo upgrade (#16763), without even needing the preparatory steps (#18024) which were all related to the upgrade nudge's server-side stuff. cc/ @anomiex @brbrr I don't know exactly how the upgrade nudge has changed since I implemented it, so I'm not totally familiar how (and under what circumstances) it works now -- meaning I can't really approve that aspect of the PR comfortably. I'll just note that the main reason for #16611 was to have the upgrade nudge rendered on the frontend (for logged-in users). It might be worth testing that nothing is broken there per this PR. LMK if you'd like me to review the technical removal bits 🙂 |
It is not used anymore since #16611, where we moved to a new upgrade nudge design for the blocks.
Since the block does not rely on shortcodes anymore, and since the Calypso classic editor has been deprecated, there are very few ways a site owner can end up inserting a Pay With PayPal shortcode on their site today. We may be able to simplify some things by moving back to a simple notice here.
We've now moved to new nudges in #16611.
0c8aa3b
to
a7bfad6
Compare
Putting this on hold for now, as per pcjTuq-8U-p2 |
Changes proposed in this Pull Request:
We've updated the way we display nudges in #16611, so it may make sense to move away from our custom implementation to simplify things a bit with our build.
This PR's counterpart was #13070, where most of this was introduced.
I'm now trying to:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions:
This will require some testing of:
add_filter( 'jetpack_block_editor_enable_upgrade_nudge', '__return_true' );
Proposed changelog entry for your changes: