WordPress / gutenberg

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

Jump to bottom

Allow customizing the no-results behavior of the query block #27302

Open

aristath opened this issue Nov 26, 2020 · 2 comments

Labels

[Block] Query [Feature] Full Site Editing [Type] Feature

Projects

Full site editing

Member

aristath commented Nov 26, 2020

Came up in #25790
We should allow users to customize the behavior of the query block when no results are found.

aristath added [Feature] Full Site Editing [Type] Feature [Block] Query labels

aristath mentioned this issue

Query block: Inspiration from Drupal's Views module #25790

Closed

9 of 12 tasks complete

gziolo mentioned this issue

Query and Loop Block: Tracking #24762

Closed

20 of 26 tasks complete

Contributor

annezazu commented Mar 3, 2021

Pulling from the FSE Outreach Program's latest call for testing, wanted to mention this piece of feedback as this issue is considered:

when a Query block has been inserted but is empty (i.e. no post content), markup for the block is still output to the front-end: <ul class=”wp-block-query-loop”></ul>. This will likely also create additional white-space on the front-end, due to a top margin being applied to the <ul> tag.

ntsekouras mentioned this issue

Print nothing in the front end if there are no results in Query block #29521

Merged

Contributor

ntsekouras commented Mar 3, 2021

when a Query block has been inserted but is empty (i.e. no post content), markup for the block is still output to the front-end: <ul class=”wp-block-query-loop”></ul>. This will likely also create additional white-space on the front-end, due to a top margin being applied to the <ul> tag.

Thanks for reporting this @annezazu! I created a small PR to fix this: #29521

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment