Make WordPress Core

Opened 5 years ago

Closed 4 years ago

#48538 closed enhancement (reported-upstream)

Making tags easier to use by adding a multi select drop down

Reported by: paaljoachim's profile paaljoachim Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Editor Keywords:
Focuses: Cc:


Various categories are listed with checkboxes beside them and one can easily select which category a post should belong to.
Tags shows a field box and the user is expected to know which tags are available or create new ones.

It would be better to have a multi select to where one can see a list of tags and choose the ones one want to use and if needed create additional tags.

For instance here is an issue I made in regards to WP Job Manager.

Adding multi select to WordPress will likely also benefit other areas as well.
Tags will very much benefit from it. Multi author posts can also benefit from it as well. We might perhaps also change categories to also use multi select.

Change History (7)

This ticket was mentioned in Slack in #design by paaljoachim. View the logs.

5 years ago

#2 @joyously
5 years ago

Showing all the existing tags could be a UI overload, similar to listing all the authors in a dropdown on a forum site with 10,000 users.
If any are to be listed, perhaps extracting the ones that a similar to the content or title would be a way to limit the list. But then this could be for a plugin to do, instead.

#3 @paaljoachim
5 years ago

As you mention Joy perhaps extracting certain tags would be a way to limit the list.
Perhaps the 10-15 most popular tags will be seen and the rest will not.

I added this trac ticket because tags are difficult to discover.

#4 @SergeyBiryukov
5 years ago

  • Component changed from General to Editor

#5 @noisysocks
4 years ago

@paaljoachim: Are you referring to the tag select component in the block editor? Or something else?

#6 @paaljoachim
4 years ago

Hey @noisysocks Thanks for checking in!

I am thinking about the tag select component in the block editor.
Here is the PR which has taken a few rounds. I believe the original contributor kinda gave up because we design folks went a bit forth and back on how to handle it, and new arguments also came up on why to continue using the tag cloud. I'll link to the last comment which in a sense creates a summary:

Version 0, edited 4 years ago by paaljoachim (next)

#7 @noisysocks
4 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to reported-upstream
  • Status changed from new to closed

Yes, let's track this in the Gutenberg GitHub repository since it relates to the block editor. Thanks!

Note: See TracTickets for help on using tickets.