[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 helen):

 Fascinating to see this pop up again :) 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 would like to take this back to @garrett-eclipse's comment early
 on in #[comment:12]:

 > the idea of making the string a customizable label when registering the
 post type seems like it could have some merit

 I also mentioned in my revert:

 > More broadly I do not love when CPTs do this and have the admin
 interface exposed without coming up with a user-friendly way of
 differentiating items. Not sure if there's also something we can do here
 to nudge them a certain way.

 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. Otherwise close this, no amount of back and forth is going to
 solve for a personal preference.

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