-
Notifications
You must be signed in to change notification settings - Fork 846
Janitorial: clean up deprecated code #16434
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
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
Connection
- In-place connection with free plan
- In-place connection with paid plan
- In-place connection with product purchase
- Classic connection. Use Safari, or set a constant
JETPACK_SHOULD_NOT_USE_CONNECTION_IFRAMEto true - Disconnect/reconnect connection
- Secondary user connection
- Connection on multisite
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.
This is an automated check which relies on |
d1efebd to
a530616
Compare
|
Caution: This PR has changes that must be merged to WordPress.com |
f55d270 to
a19ff23
Compare
kraftbj
left a comment
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.
I'd like to see about running this realize against the Analyzer to see what might break. This would be a good thing to check it with. :)
Yes, that'd be nice, but last time I tried I ran out of memory and could not get it to work. @zinigor Do you still have your setup to analyze against all plugins in the directory? Do you think you could run it with this PR? |
|
Sure thing, I'll run it today and report my findings here. |
|
Thank you! |
|
I ran the analyzer, here's the results that it found in the updated WordPress plugins repo: The |
|
Putting this on hold since we'll need to make changes to Akismet and VaultPress first. |
We'll just leave the test in, since it could be useful in the future for other file deprecations.
|
@kraftbj Sorry, one of the tests was failing, I had to bring the provider back. This will consequently need another review. Thank you! |
|
r233300-wpcom |
|
@kraftbj I had to update a package's version number. Could I ask for one last review? :) Thank you! |
|
Great news! One last step: head over to your WordPress.com diff, D46167-code, and commit it. Thank you! |
…workflow # By Chris R (2) and others # Via GitHub * master: VaultPress: Update Changelog and stable tag for 2.2.0 release (#21413) Janitorial: clean up deprecated code (#16434) Update/boost Use Admin_UI package to register top level menu (#21345) package.json: fix spelling of deprecated in pnpm tasks (#21411) Heartbeat: fix typo in README (#21410) Premium Content Block: fix icon color (#21327) Decide CSS files to proxy on the client-side (#21392) # Conflicts: # projects/plugins/boost/composer.lock
This function has been deprecated since 9.5 and removed in 10.3. See Automattic/jetpack#16434
Notable changes: * Remove `Jetpack_User_Agent_Info::is_OperaMobile()`. #16434 removed the jetpack-device-detect function this was calling in October 2021, but missed this caller. * Remove `jetpack_server_sandbox()` and `jetpack_server_sandbox_request_parameters()`. Due to a wrong namespace in #21128, they'd have thrown fatals since October 2021. * Use `$skin` instead of `$upgrader->skin`, it's the same object but not typed as a parent class. Should be no change to functionality. * Add some missing methods to `WPCOM_JSON_API`. * Add some missing abstract methods to SAL_Site, and implement in Jetpack_Site. * Fix `SAL_Token::is_global()`. * Remove `views/admin/deactivation-dialog.php`, unused since #21048 in November 2021. * Add `@phan-var-force` in a lot of "template" files. I'm not entirely happy with this, it pollutes the global scope for any subsequent files processed, but short of writing a Phan plugin that somehow adjusts the scope for only the file I can't find a better idea.
Notable changes: * Remove `Jetpack_User_Agent_Info::is_OperaMobile()`. #16434 removed the jetpack-device-detect function this was calling in October 2021, but missed this caller. * Remove `jetpack_server_sandbox()` and `jetpack_server_sandbox_request_parameters()`. Due to a wrong namespace in #21128, they'd have thrown fatals since October 2021. * Use `$skin` instead of `$upgrader->skin`, it's the same object but not typed as a parent class. Should be no change to functionality. * Add some missing methods to `WPCOM_JSON_API`. * Add some missing abstract methods to SAL_Site, and implement in Jetpack_Site. * Fix `SAL_Token::is_global()`. * Remove `views/admin/deactivation-dialog.php`, unused since #21048 in November 2021. * Add `@phan-var-force` in a lot of "template" files. I'm not entirely happy with this, it pollutes the global scope for any subsequent files processed, but short of writing a Phan plugin that somehow adjusts the scope for only the file I can't find a better idea.
Changes proposed in this Pull Request:
I left out everything in the compat package.
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions: