[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:73 peterwilsoncc]:
 > For copy, some options are:
 >
 > * display the generated title if it exists
 > * the first N characters of the content if it exists
 > * (Post type) @ (long form date)

 1. The generated title obviously should be displayed when available (not
 available by default), but what we are assuming here is the absence of it,
 and how to deal with the original fallback (ie `Auto Draft`, which
 currently is deceiving and rubbishy).

 2. Hoping that there is content at least, otherwise, we will drop into no
 title at all, which leads back to the original discussion  I commented in
 my previous message)

 3. A somewhat random sequence could be another copy solution for the
 troubles stated with SEO.

 > I recently messed up the SEO for some post types that don't support
 titles

 It's kind of strange to see a `no titles` support CPT + titles being shown
 in the template = angry because all titles are identical (`Auto Draft` or
 whatever are the same), and we trying to fix such a number of wrong
 decisions… As you said you messed up adding unhandled no titles support,
 and for some reason, your template for such CPT displayed titles... Also
 the SEO "troubles" are going to be affecting just those pages, should not
 be a big deal and SEO tools will be informing you about this, which is
 good because you will be able to spot the issue (you left your template
 showing wrong titles). So you had a free debugger, and now we could be
 planning to obscure this great information?

 Anyway, almost anything, except for `(no title)`, is better than `Auto
 Draft`.
 Even adding a 👍 emoji will do the trick... Currently we have left
 unmerged with the worst copy of all scenarios, `Auto Draft`

 Replying to [comment:72 mindctrl]:
 > `get_the_title()` provides an empty string for the title if one does not
 exist on the post object.

 Yes, this is what I was expecting originally. It seems that templates
 should deal with this. Here we are just informing about what is currently
 happening with titles.

 But we must also consider what @peterwilsoncc suggested also: if titles
 are not supported, because we are managing internally such titles, and
 they must be displayed in the admin posts table, we should not be messing
 up with this.

 I'm still trying to grasp why `(no title supported)` is still not the
 option

 I remember some weeks ago when Adam Silverstein was asking which copy we
 should use for the new gutenberg notes. People were proposing ofering
 convoluted ideas like "Editorial Comments", and someone just said: "why
 not simply naming them Notes". @marybaum and me
 [https://wordpress.slack.com/archives/C02RQBWTW/p1759332386138469 were
 agreeing with this] because it was so simple and obvious. Here it feels
 just about the same. We could choose among a range of similar simple
 options like:

 - `(not supported)`: implicit given the position in the table
 - `(unsupported)` again implicit
 - `(title not supported)`: which was discarded by @bridgetwillard
 - `(title unsupported)`: similar fashion but shorter.

 Anyway, let's hear more about copy feedback.

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