-
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
Footnotes: Register format within the init function #63554
Conversation
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. |
Size Change: -3 B (0%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
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.
Thanks!
e22225b
to
9ed652a
Compare
Co-authored-by: youknowriad <[email protected]> Co-authored-by: ellatrix <[email protected]>
Address #51201 (comment)
Related #53874
What?
Some third-party editor uses the
@wordpress/block-library
package but only pick generic blocks from it. Things are WP specific like footnotes are not needed.The problem in trunk right now is that the "footnotes" format is registered as soon as you import the package regardless of whether you register the footnotes block or not which results in a 404 api request for all these editors.
This PR fixes that by moving the registration of the footnote format to the "init" function.
Testing Instructions
1- Check that footnotes still work in the post editor.
2- Check that when you type in the "storybook" example for block editors, you won't see any failed API request.