"Query Type" missing from Query Loop block; can no longer use it to inherit current query?

[cheestudio]

Description

I went to create a Template Part for Search Results and I noticed I was not able to allow the Query Loop block to inherit the current query. I then went to multiple sites running 6.7.1 and found the same result.

I disabled all plugins and used TwentyTwentyThree to rule out any plugins or theme conflicts. This setting is 100% missing.

Step-by-step reproduction instructions

1. Add a Query Loop
2. Notice the setting is missing

Screenshots, screen recording, code snippet

Environment info

No response

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

• Yes

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[cheestudio]

Follow up: I now see that the "default behavior" is to have the query loop inherit by default:

https://make.wordpress.org/core/2024/09/23/core-editor-improvement-simplified-query-loop-block-with-smarter-defaults-intuitive-settings/

The documentation has not been updated, which is very confusing:

https://wordpress.org/documentation/article/query-loop-block/#inherit-query-from-template

Anyway, this would be fine, except it doesn't actually work; I'm adding it to a Template Part and it's wanting to just query a post type and it's not reacting to user searches.

[jeflopodev]

This one is also about Query Loop & Template parts: #38684

[carolinan]

I am not able to reproduce this issue:

Activate Twenty Twenty-Three.
Go to Appearance > Editor > Patterns
Click on the button "Add new pattern": Select "Add New Template part".
Select the "general" area and add a name. Select "Add".

In the editor, add a query loop.
The option "Query Type" is available and Default is enabled.
Save.

Go back to Appearance > Editor > Templates and select the Search Results template.
Insert a template part block. Select "Choose" and then select the part you just created.
Select the query block inside the part.
The option "Query Type" is available and Default is enabled.
Save.

Go to the front of the website and perform a search.
Confirm that the newly added query displays the search results.

[carolinan]

It is not possible to use the query loop's standard interface controls to query search results for a custom post type.
The block can not both inherit the query and use a custom query for post types.

Can you please help narrow down what the issue is? Because I don't believe that the problem is that the control in the sidebar is not showing.
It would be helpful if you could describe in detail what you are trying to accomplish.

[carolinan]

I believe what you want to look at is this: #40585

[rinkalpagdar]

Hello @cheestudio, I can't able to reproduce the issue. For me, the setting is showing.

=== Environment

• WordPress: 6.7
• PHP: 8.1.23
• Server: nginx/1.16.0
• Database: mysqli (Server: 8.0.16 / Client: mysqlnd 8.1.23)
• Browser: Chrome 131.0.0.0
• OS: macOS
• Theme: Twenty Twenty-Five 1.0
• MU Plugins: None activated
• Plugins:
  • Gutenberg 19.9.0
  • Test Reports 1.2.0

[cheestudio]

@carolinan and @rinkalpagdar

I am running a Hybrid and it looks like this deals with having parts already defined in the theme, but then are editing within the dashboard, that seem to upset the inheritance of the search part. My template part was defined prior with the following:

But after the part was edited, I copied it back to the HTML file and noticed this:

So something about editing the part changed that default value to false. Since the toggle is removed now due to it inheriting by default, I was forced to change it manually, remove the part from the theme and dashboard entirely, and then re-add it with the updated version that I was wanting to use.

Perhaps it's my hybrid theme, although I have no functions where I can see that would incur this behavior and I don't have problems with parts in general otherwise. It feels like a bug.

Ultimately I abandoned this process entirely, as the Query Loop doesn't support multiple post types anyway, and my search result needed to be scoped to multiple post types and variations. It seems I just hit a limit of what FSE capabilities can do in this case.

[carolinan]

Please understand that when you use screenshots of code, it makes it impossible for contributors who are blind to access the code;
And impossible for sighted contributors to copy the code for testing.

So something about editing the part changed that default value to false.

Without knowing what was edited, it makes it impossible to reproduce with exact steps.

[Mamaduka]

I think this is a duplicate of #66790. The "Query type" settings are only displayed when a Query loop block is used in archive/index templates.

See this comment for additional details - #66790 (comment).

[carolinan]

I don't think the issue is that the setting is not showing, but that they are asking for help with a custom query.
I think it can be closed.

[Mamaduka]

Let's see if we can get any additional info. Otherwise, we can close it 👍

[genemma]

I believe I am seeing the same issue as @cheestudio and I agree with him that it seems like a bug. To outline:

• I am developing a classic theme.
• I have a added a query loop block to my posts page using the block editor.
• My posts page shows the appropriate posts. However, my search and archive pages (which are using the same template as the posts page, i.e. index.php) do not display any posts. The query loop block is rendering, but it contains no posts.
• When switching the the code editor, I see that the inherit attribute is set to false.
• I use the code editor to set the inherit attribute to true and save the page. My search and archive pages now list the appropriate posts.
• However, as soon as I exit the code editor, the inherit attribute reverts to false, and my search and archive pages no longer work.

This is an issue as I am building a theme for a client and I can't ask them to change the attribute in the code editor anytime they want to edit the page.