[irozum]

Summary

The classic editor wrapped the whole #titlediv (title field and the permalink/View box) in a post_type_supports( $post_type, 'title' ) check, so public post types without title support never showed their permalink. This keeps #titlediv always rendered and only gates #titlewrap (the title input) on title support. The permalink box, edit_form_before_permalink and the sample permalink nonce remain governed by the existing $viewable / public checks.

Notes

• edit_form_before_permalink now also fires for post types without title support, matching its documented purpose.
• Added a Playwright e2e test registering a title-less and a titled post type. The title-less test fails on trunk and passes with the change.
• Props grosbouff (original patch) and SirLouen (testing).

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

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Sonnet 5.5
Used for: Implementation, tests, and PR description.

---

This Pull Request is for code review only. Please do not merge this Pull Request on GitHub. Merging is handled via Trac and SVN.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

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

Props irozum.

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

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[github-actions]

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.