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

WordPress Trac noreply at wordpress.org
Fri Nov 7 12: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:  Posts, Post Types                    |     Version:  5.0
 Severity:  minor                                |  Resolution:
 Keywords:  has-copy-review has-screenshots      |     Focuses:
  has-test-info has-patch has-unit-tests needs-  |  administration
  testing                                        |
-------------------------------------------------+-------------------------

Comment (by SirLouen):

 > Based on the discussions I've read, it seems that no research or testing
 has yet been conducted on the points mentioned above.

 I'm not sure what "Testing" should be driven in Gutenberg specifically.
 All tests have been actually done in Gutenberg as this is the default
 editor.

 If we check the code, Auto Drafts are still being executed when they
 should. The `(no title supported)` is only relevant when the post is
 actually saved, but there is no title support explicitly set at that exact
 moment. Currently it  will be set as `Auto Draft` generating a faulty
 behavior.

 Replying to [comment:55 wildworks]:
 > Perhaps, it might be possible to simply use `(no title)`?

 @wildworks the problem is that since this is not a dynamic field, this is
 only reflecting the current status when set.
 It's like `(Auto Draft)`. You could edit this in a million ways and still
 it will be saying "(Auto Draft)" until you manually change it.

 `(no title)` is not much descriptive in regards of what is happening but
 `(Auto Draft)` is actually misbehaving.

 So currently this is misbehaving and this patch will add a fix to this. It
 could always be reimproved but current situation is unstable.

 I still believe this is a commit, and it should be committed in 6.9

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


More information about the wp-trac mailing list