Disable Term Query blocks in Widgets Editor#73449
Conversation
|
Size Change: +19 B (0%) Total Size: 2.54 MB
ℹ️ View Unchanged
|
|
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. |
t-hamano
left a comment
There was a problem hiding this comment.
Thanks for the PR!
I think we'll need to make a similar change here as well:
Perhaps coincidentally, the Terms Query block doesn't throw an error in the Customizer widget because the core/editor stores exist. Therefore, a Terms Query block registered in the Customizer widget will cause an error in the Widget Editor.
At the very least, I think the two widget editors need to have consistent functionality.
Additionally, custom queries should work without a post context. As a follow-up, it might be worth exploring whether we can get the Terms Query block working in the widget editors.
What?
Closes #73448
Why?
The widget editor will throw an error because there is no context such as
termId.As with other FSE blocks, the widget editor will exclude registration of term-related blocks.
How?
Exclude Term-related blocks from the widget editor.
This issue may be related to this issue.
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast