WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 4 years ago

#28948 closed enhancement (worksforme)

Add support for an ID column in list tables

Reported by: krogsgard Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.9
Component: Administration Keywords: close
Focuses: administration Cc:

Description

A common developer frustration is to need to quickly reference post/attachment/CPT/term IDs.

I'd like to propose a Screen Option checkbox (off by default) that enables a column for referencing the ID of whatever the view is (first priority on post types vs terms).

For new media grid stuff in 4.0, it could work in the same way as other screen options (listed below the thumbnail) when enabled. List views would be a column.

Core territory? Would be super useful for developers and I also think so for advanced/super users.

Change History (5)

#2 follow-up: @helen
4 years ago

  • Keywords close added

I am not a fan of things that require you to specify an ID by hand - when is this needed in a user context?

#3 in reply to: ↑ 2 @wpkonsulent
4 years ago

Replying to helen:

I am not a fan of things that require you to specify an ID by hand - when is this needed in a user context?

I have clients with very large sites (non-blogs) where it is common practice to refer to content by ID. Said sites have many editors, and pages (and other content) are moved around quite often. That makes it nearly impossible to maintain thousands of internal links if they link by URL. So they link by ID using a custom shortcode, and then have the shortcode translate the ID into the real permalink. Links is just one example, there are many other use cases for referring to certain pieces of content where providing an ID is the only viable solution.

#4 @krogsgard
4 years ago

I'd agree that shortcodes are likely the most common use case.

I wouldn't absolutely not advocate this be a default "on" option, but having it tucked into screen options would be very handy.

I know it's borderline "user" majority scenario, at best. But I think it's valuable for when it's needed.

#5 @helen
4 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from new to closed

If a shortcode is dependent on an ID, I'd really much rather see that handled via UI. There are any number of plugins that do that, whether they insert a plain shortcode or translate into an MCE view. Expecting users to consult an ID from another screen is terrible UX, and I don't think core needs to support that. If your userbase really needs to reference the ID, I'd first suggest rethinking why they need to be referring to the ID from the all posts list, and then if you still think you need it, add the column yourself. Custom columns are supported, at least :)

Note: See TracTickets for help on using tickets.