-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Interactivity API: Rename data_wp_context
function
#59465
Conversation
This pull request has changed or added PHP files. Please confirm whether these changes need to be synced to WordPress Core, and therefore featured in the next release of WordPress. If so, it is recommended to create a new Trac ticket and submit a pull request to the WordPress Core Github repository soon after this pull request is merged. If you're unsure, you can always ask for help in the #core-editor channel in WordPress Slack. Thank you! ❤️ View changed files❔ lib/compat/wordpress-6.5/interactivity-api/interactivity-api.php |
Core change has been committed in https://core.trac.wordpress.org/changeset/57742 |
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
The sooner we merge, the fewer fatal errors there will be in Gutenberg + WP trunk! 😆 |
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.
LGTM ✅
@swissspidy, @youknowriad and @getdave, core blocks in WP core still use the old helper method which definitely breaks things. The best approach would be to publish npm packages with this commit and apply it WP core. Alternatively, we can revert the commit, and try again next time we sync changes from Gutenberg. |
We'll be publishing packages again on Tuesday prior to RC 1. How critical is it that we do another package update for this one change? |
@gziolo Right, of course! 🤦 Let me revert the core commit, that's the most straightforward way. Then we can introduce after the package update on Tuesday. |
Why the Gutenberg one? It has a compat copy in |
True, we don't |
Co-authored-by: c4rl0sbr4v0 <[email protected]> Co-authored-by: DAreRodz <[email protected]> Co-authored-by: swissspidy <[email protected]>
I just cherry-picked this PR to the update/packages-6.5-rc1 branch to get it included in the next release. |
Co-authored-by: c4rl0sbr4v0 <[email protected]> Co-authored-by: DAreRodz <[email protected]> Co-authored-by: swissspidy <[email protected]>
Is there a reason to not keep a copy of the old function in place with a We just hit an issue of this bricking a site when Gutenberg updated to 17.9 as the function wasn't defined. |
…59834) * Re-introduce `data_wp_context()` with `_deprecated_function()` call Following its removal in #59465 and release in Gutenberg 17.9, this can potentially result in fatal errors on sites where plugins or themes are calling `data_wp_context()` instead of the newer function name. This should backfill it in, and provide a reminder to update to the newer function. * Typo'd version number. * Adding deprecated to phpdoc. --------- Co-authored-by: georgestephanis <[email protected]> Co-authored-by: c4rl0sbr4v0 <[email protected]>
…ordPress#59834) * Re-introduce `data_wp_context()` with `_deprecated_function()` call Following its removal in WordPress#59465 and release in Gutenberg 17.9, this can potentially result in fatal errors on sites where plugins or themes are calling `data_wp_context()` instead of the newer function name. This should backfill it in, and provide a reminder to update to the newer function. * Typo'd version number. * Adding deprecated to phpdoc. --------- Co-authored-by: georgestephanis <[email protected]> Co-authored-by: c4rl0sbr4v0 <[email protected]>
What?
Update Core blocks to be compatible with the refactor done in Core.
WordPress/wordpress-develop#6205
Why?
Check ticket: https://core.trac.wordpress.org/ticket/60575
Testing Instructions
Contexts should appear in Navigation and Search block.
These should work as expected.
Testing Instructions for Keyboard
Screenshots or screencast