Make WordPress Core

Opened 11 years ago

Last modified 22 months ago

#25582 new defect (bug)

Ping status always disabled when quick editing a post type that doesn't support trackbacks

Reported by: bradyvercher's profile bradyvercher Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Pings/Trackbacks Keywords: has-patch needs-refresh
Focuses: Cc:


There isn't much useful documentation for the "trackbacks" post type feature. I expected it to function similar to the "comments" feature, however, it appears to be for enabling the "Send Trackback" meta box on the edit screens.

That being the case, it's currently being used to prevent the "ping_status" check box from displaying in quick edit and bulk edit if a post type doesn't have the trackback feature support, causing the "ping_status" to be closed whenever a page is edited in one of those modes.

Steps to reproduce:

  1. Display the "Discussion" meta box on a page and allow trackbacks, but disable comments and update.
  2. Go back to the page list table and quick edit the same page (only the comments checkbox is available). Enable comments and save.
  3. Visit the edit screen again and trackbacks have been disabled.

Considering there aren't any instances in core where "default_ping_status" relies on a post type supporting the trackback feature, the "ping_status" checkbox should probably always be visible in quick edit and bulk edit modes.

Attachments (2)

25582.diff (3.0 KB) - added by bradyvercher 11 years ago.
25582.2.diff (3.0 KB) - added by bradyvercher 9 years ago.

Download all attachments as: .zip

Change History (5)

11 years ago

#1 @SergeyBiryukov
11 years ago

  • Component changed from Administration to Pings/Trackbacks
  • Keywords has-patch added

9 years ago

#2 @bradyvercher
9 years ago

I refreshed the patch on this. It's low priority, but should be easy to confirm and merge.

#3 @desrosj
22 months ago

  • Keywords needs-refresh added
  • Milestone set to Awaiting Review

Related: #31977.

I found the similar behavior described in #31977 is still happening. Would be great to confirm that this one is also still reproducible. It's also not entirely clear whether these are identical reports.

Note: See TracTickets for help on using tickets.