Query Loop does not display on site if Inherit query from template is enabled

[masperber]

Quick summary

When using a Query Loop Block, the Query Loop is hidden from the live site if the Inherit query from template option is selected from the Block settings.

Steps to reproduce

1. On a site with any theme, add a Query Loop to a blank page.
2. Choose any of the default templates
3. Leave the Inherit query from template option enabled
4. View the live page or preview

What you expected to happen

The Query Loop should display posts as it does in the editor.

What actually happened

The Query Loop does not appear on the live site or preview at all.

Context

Customer report 37468979-hc

Confirmed on my test sites, both Atomic and simple, using Classic, Hybrid, and FSE themes.

Platform (Simple, Atomic, or both?)

Simple, Atomic

Theme-specific issue?

No response

Browser, operating system and other notes

No response

Reproducibility

Consistent

Severity

All

Available workarounds?

Yes, difficult to implement

Workaround details

The Query Loop displays if the Inherit query from template option is disabled. However, this option is enabled by default, which could lead to considerable user confusion.

[cuemarie]

📌 SCRUBBING : RESULT

• Tested on Simple: Replicated
• Tested on AT: Replicated
• Tested on Self-hosted: Replicated
• Replicable on Core? Yes

📌 FINDINGS/SCREENSHOTS/VIDEO

• Replicated in all test environments, no matter the theme.

AT Example

Simple Example

📌 ACTIONS

• Marked as Triaged for Quality Squad review

📌 Message to Author/Quality Squad

• it's possible this is by design; as the query loop is being added to a page, it's best attempt would be to pull from the page template.
• I found it noted here Query block: Editor preview is different from the frontend WordPress/gutenberg#29438 (comment) that:

In a single page there is no much use in having an inherit Query, but instead a custom one.

In general we need to find a way to detect the context a Query lives (page/archive) and set the inherit option accordingly, but this is not yet implemented.

• that context detection has an open issue here: Context detection for Query block WordPress/gutenberg#30369

[arthur791004]

I've also encountered this issue since Gutenberg v13.7 above. The root cause might probably be use_global_query from WordPress/gutenberg#32514. But I'm not sure why it makes the posts become empty if inherit query is enabled

[vinnykaur]

Another one at zen-5774388

[github-actions]

Support References

This comment is automatically generated. Please do not edit it.

• 5820182-zen
• 6550825-zen
• 6776963-zen

[rinazrina]

Another report: #5820182-zen

[jartes]

Another one on 42594789-hc

[jamiepalatnik]

Another report: 6550825-zd-woothemes

[masperber]

@cuemarie Do you think we might be able to get an assignee for this? I think it's pretty unfortunate that Query Loops just don't work at all when used by a page unless you disable Inherit query from template, which is on by default. Turning this option off by default, or even better removing it entirely when the block is placed on a page, would be really helpful.

[cuemarie]

Hey @masperber ! Looks like the underlying issue here is in Gutenberg Core, so I'm not sure if this is something that can be addressed just within WordPress.com.

Looping in @liviopv though, who might be able to help give this request (as well as the Core counterpart, here: WordPress/gutenberg#30369 ) more support in conversations between .com and .org. Your thoughts or help escalating this would be much appreciated! Thanks for taking a look!

📌 ACTIONS

• I've lowered the priority label to 'normal' and removed the 'bug' label to make the labeling here more accurate, even though this improvement would be really helpful for lots of customers!

[Gustavo-Hilario]

Another report: 6776963-zen

[annezazu]

Noting that this is related to adding a query loop to a page rather than a template with a fix in progress here: WordPress/gutenberg#65067