[wp-trac] [WordPress Trac] #45516: Auto Draft title issue for custom post types
WordPress Trac
noreply at wordpress.org
Sun Nov 30 22:13:15 UTC 2025
#45516: Auto Draft title issue for custom post types
-------------------------------------------------+-------------------------
Reporter: rajanit2000 | Owner:
| SergeyBiryukov
Type: defect (bug) | Status: reopened
Priority: normal | Milestone: 7.0
Component: Administration | Version: 5.0
Severity: normal | Resolution:
Keywords: has-screenshots has-test-info has- | Focuses:
patch has-unit-tests commit |
-------------------------------------------------+-------------------------
Changes (by SirLouen):
* focuses: administration =>
* component: Posts, Post Types => Administration
Comment:
Replying to [comment:78 peterwilsoncc]:
> I'd like to go back to first principals and consider what exactly the
problem is that needs to be solved.
>
>
> I believe the issue is that "Auto Draft" is technical details AND that
there is no way to differentiate between posts when viewing the admin
screen.
>
> The issue with `(no title supported)` was similar: it's a technical
detail AND there was no way to differentiate between posts when viewing
the admin screen.
>
> Wrapping the title in brackets isn't great. `No title` or `Untitled` is
an improvement on the earlier version but still lacks a way of
differentiating the posts in the admin.
>
> An additional question to ask is this: Is this a bug in WordPress or
themes/plugins developing CPTs without title support? WordPress provides
numerous filters to modify the title display; is it reasonable to expect
these to be used (I believe it is).
>
> Regarding the default themes, I'm not overly concerned about them
displaying the default value on the front end. WordPress default themes
are designed to support WordPress default post types which support titles.
To be clear, I don't 100% understand what you are expecting from this.
I'm going to try to guess what your proposal is: switching from `(no
title)` to `No title`?
`(no title)` in the Admin dashboard, has been the default for centuries
when no title has been set.
If this is what you have in mind, basically you are going out of scope of
this ticket. The right way to proceed is to open a new ticket focusing on
this change if you think this will bring a legibility improvement.
But this ticket is trying to fix a singular defect. I don't understand why
we must solve 2 or 3 things at a time. We should aim to do atomic changes,
which are easier to review, easier to test and unit test, and easier to
track back and understand when git blaming. If we fix this, switching from
`Auto Draft` to an empty string (which results, by default, in `(no
title)` then we can steer into `No Title` or whatever idea, but in another
ticket.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/45516#comment:79>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list