Skip to content

Editor: Update the post editor preload paths for the DataForm inspector - #14494

Open
ntsekouras wants to merge 2 commits into
WordPress:trunkfrom
ntsekouras:update/post-editor-preloads-for-df-inspector
Open

ntsekouras wants to merge 2 commits into
WordPress:trunkfrom
ntsekouras:update/post-editor-preloads-for-df-inspector

Conversation

@ntsekouras

@ntsekouras ntsekouras commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Trac ticket: https://core.trac.wordpress.org/ticket/66339

Gutenberg stabilizes the DataForm-based editor inspector in WordPress/gutenberg#85081. This PR updates the post editor preload paths for the requests the new post summary makes on load:

  1. Adds the form view config of the post type.
  2. Removes the author path, which was used by the old author panel and is not requested anymore.

The new author field queries the users collection with who=authors (to work around https://core.trac.wordpress.org/ticket/56429), which is not preloaded for now because the who deprecation notice gets printed in the editor page during preloading.

This should be committed together with the Gutenberg packages update that includes WordPress/gutenberg#85081.

Use of AI Tools

Generated with Opus 5.5 and adjusted/reviewed manually.

@github-actions

github-actions Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props ntsekouras, oandregal, mamaduka.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Comment thread src/wp-admin/edit-form-blocks.php Outdated
'/wp/v2/users/%d?context=view&_fields=id,name',
(int) $post->post_author
// The post summary of the inspector queries the author through the users collection.
$preload_paths[] = add_query_arg(

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems who=authors passes who to WP_User_Query, which is deprecated since 5.9, and since preloading runs during the page render the notice gets printed in the editor page (that's what broke the e2e tests here).

I'm thinking we should remove this preload for now and handle who=authors in WP_REST_Users_Controller::get_items() in a separate ticket, then add it back. It would be one extra request on load until then. What do you think?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the preload, since the old author path isn't requested anymore and the new one prints the who deprecation notice. We can add it back once https://core.trac.wordpress.org/ticket/56429 is fixed and Gutenberg's AuthorView doesn't need who=authors.

@oandregal

Copy link
Copy Markdown
Member

This should be committed together with the Gutenberg packages update that includes WordPress/gutenberg#85081.

How do we make sure this happens? I know @Mamaduka may be aware of this personally, but wonder what system do we have in place so this is not missed.

@Mamaduka

Copy link
Copy Markdown
Member

Unfortunately, we don't have a system to queue related commits. This needs to be done manually.

@ntsekouras

Copy link
Copy Markdown
Contributor Author

Unfortunately, we don't have a system to queue related commits. This needs to be done manually.

@Mamaduka I guess that should be part of the SHA change commit in core or after that change?

@Mamaduka

Copy link
Copy Markdown
Member

@ntsekouras, I'll create a sync PR like #14497 after RC is released that includes that change. Once that's committed, we can commit this patch.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants