-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Fix: Term Description block should only be available in the site editor #51053
Conversation
Flaky tests detected in c988f9d. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5265203395
|
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.
This looks good to me! It's a minimal and simple change, fixes the issue, and gets the job done the right way.
Thank you for working on this @carolinan! 👍
I'm not sure if the This change has introduced a regression, as the Term Description block now is not registered without an active Gutenberg plugin running. |
Reverts changes in #51053, to address a regression in which the Term Description block was only available in core when the Gutenberg plugin was active.
Reverts changes in #51053, to address a regression in which the Term Description block was only available in core when the Gutenberg plugin was active.
Reverts changes in #51053, to address a regression in which the Term Description block was only available in core when the Gutenberg plugin was active.
* Patterns: set context of pattern category api call to view so authors and contributors can access (#55553) * Query Loop: Disallow "enhanced pagination" with core blocks that may contain third-party blocks (#55539) * Update useContainsThirdPartyBlocks and texts * Improve texts a bit * Show the list of unsupported blocks * Use the BlockTitle component instead * Simplify modal text * Revert "Query Loop: Disallow "enhanced pagination" with core blocks that may contain third-party blocks (#55539)" This reverts commit f2dd6de. * Query Loop: Disallow "enhanced pagination" with core blocks that may contain third-party blocks (#55539) * Update useContainsThirdPartyBlocks and texts * Improve texts a bit * Show the list of unsupported blocks * Use the BlockTitle component instead * Simplify modal text * Revert CSS changes to show/hide embedded pdf (#55667) * Ensure Term Description block is available in core (#55669) Reverts changes in #51053, to address a regression in which the Term Description block was only available in core when the Gutenberg plugin was active. --------- Co-authored-by: Glen Davies <glendaviesnz@users.noreply.github.com> Co-authored-by: David Arenas <david.arenas@automattic.com>
What?
The term description block displays the description of taxonomies in archives, and does not output anything on the front
if it is used in any other context.
Closes #38552
Why?
It can be confusing if you add a block to the post content, that is visible in the editor but not the front.
How?
Adds
__experimental": "fse"
, to block.jsonTesting Instructions
Create a new post using the block editor.
Try to add a term description block. Confirm that the block is not available.
Go to the Site Editor and edit any template.
Try to add a term description block. Confirm that the block is available.
(if you view the front, it still wont show unless you are on an archive page for a taxonomy that has a description to show)