core/post-content block don't shows the correct content in pages (post type)

[diegosomar]

Description

If the core/query > core/post-content appears BEFORE the page core/post-content, it shows the page content instead the query loop item content.

This issue is probably related with #42862 and #40743.

Step-by-step reproduction instructions

1. In the page (post type) tamplate, use the core/post-content to show the page content;
2. Create a page and add some content;
3. In the header template, add a core/query block to show a different post type and in the loop, add the core/post-content block.
4. Go to the page and in the query loop you will see the current post content instead the query loop post content.

The query does not need to be in the header. It is enough that the query is above the content of the page, which will be enough to display the content of the page instead of displaying the content of the query.

Screenshots, screen recording, code snippet

wp-2022-10-14_10.22.14.mp4

Environment info

• WP version: 6.0.2;
• Plugins: only Gutenberg 14.3.0;
• Theme: TT2;
• Browser: Microsoft Edge (Ubuntu version).

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

[carolinan]

I am able to reproduce this with WP 6.1-RC1-54520, with and without Gutenberg active. I tried with a few different block themes.

• It only affects the first post in the query
• It doesn't happen with the post excerpt, only content
• It doesn't make a difference if the page is set as the home page or not (reading settings)

[skorasaurus]

I am admittedly fairly frustrated as I am experiencing this bug as well.

I want to display content from a custom post type on a website's frontpage and I cannot; content from the post type of 'post' is displayed instead.

Like @carolinan stated, this issue only affects the first post of the query loop but as a result of this bug, displaying content from a custom post type on the frontpage is futile. (if you alter your query loop to use an offset, the first post's content will still come from the post type of 'post'. regardless of what post type you select).

Interestingly, if you create the query loop (for the custom post type) and it is AFTER a query loop of post type post; the 2nd query loop will display content from the custom post type as intended.

An alternate, reduced test case :

Goal blocked by this bug: Display the post content from a custom post type's most recently published post on a website's frontpage.

1. create and register a custom post type. An example, with a custom post type named 'metric' is available at https://gist.github.com/skorasaurus/cad69d2c05f8db300e2bea69b8eff026

2. create and publish a new post of that custom post type. Any add content that you would like to your post's content.

3. In frontpage template of your block theme:
   Insert a query loop and:

• Select your custom post type (in this example, it is 'metric')
• include the post content block as a child block in your query loop
  (example image is below)
  

The content from your custom post type will display in the site editor.

4. save your site editor changes.

5. view the website as an end user; (e.g. example.test ) In the screenshot below, you'll see that the post content is from the post type of 'post' although the class given to the is from the custom post type (metric) and the post title from the custom post type is successfully retrieved and displayed

What I expected: The post content from my custom post type would display on the frontpage of the website.

I am able to to reproduce in WordPress 6.1.1; with and without Gutenberg 15.0.1 active; reproduced using the empty theme. and a custom FSE theme.

Technical context causing this is available at #42862 (comment)

[youknowriad]

Closing as fixed along with #42862: this is the same root cause tracked in #40743, which was confirmed resolved by #49904. The reproductions here are from 2022–2023, before that fix landed. Please reopen with fresh steps if the first Query Loop item still shows the wrong content on a current version.