[wp-trac] [WordPress Trac] #45516: Auto Draft title issue for custom post types

[WordPress Trac]

#45516: Auto Draft title issue for custom post types
-------------------------------------------------+-------------------------
 Reporter:  rajanit2000                          |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Posts, Post Types                    |     Version:  5.0
 Severity:  minor                                |  Resolution:
 Keywords:  has-screenshots has-test-info has-   |     Focuses:
  patch has-unit-tests needs-copy-review         |  administration
-------------------------------------------------+-------------------------

Comment (by SirLouen):

 Replying to [comment:75 helen]:
 > Fascinating to see this pop up again :)
 And even more to pop up soon, I'm triaging through every single ticket in
 the post/post-types component. :)

 > I think the real problem here is that there is not an actual clearly
 defined problem trying to be solved besides "this phrase is not my
 preference" which is an inevitable endless debate.

 I'm not totally sure about this. The original problem we are completely
 ignoring is the fact that when you create a new post in a no-title support
 CPT, in the title appears `Auto Draft`. It's ultra misdirecting. As I told
 @wildworks: any solution, even a simple dot or an empty title will do way
 better than `Auto Draft`. We should not leave this alone.

 > Can we take the conversation to "how can users differentiate between
 items when a post type doesn't support the title in the editor" instead?
 For instance, as a seed idea but not a solution, should there be a
 `default_title` arg (that takes placeholders or some other way of
 programmatic generation) and we also update the core default to be
 generated in a way that allows for some kind of differentiation? From
 there you would need to identify all the places in which the code expects
 a specific string and understand why that assumption was made and whether
 the knock-on effects are accounted for in addition to repairing those
 assumptions.

 The problem as you exactly suggest, is that after "sorting" the `Auto
 Draft` thing, we want to go two steps forward, and sort it with a super-
 elegant and perfect solution. As I suggested to Aki I feel that we
 preferred to go in the road with the blown tire destroying our rims, than
 using a temporary wooden wheel. :)

 > Otherwise close this, no amount of back and forth is going to solve for
 a personal preference.

 I feel wrong for closing this and leaving the "Auto Draft" thing. Maybe is
 not a big deal because I doubt that many users remove titles from CPT and
 leave it unmanaged, but this is a wrong behavior, a bug that we are not
 simply addressing. It's at the tips of our hands with a tested patch and
 one return away from being shipped. From there, we could have a discussion
 on marvelous solutions that favor the UX. But first things first is fixing
 this bug.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45516#comment:76>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform