Make WordPress Core

Opened 9 months ago

Closed 9 months ago

Last modified 8 months ago

#63552 closed enhancement (reported-upstream)

Plugin search should prioritize exact match by name

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

Description

I want to see smart results that show people what they're looking for, which is often popular plugins, but the search really really needs to show an exact match in 1st spot. It's the only way to bring any kind of fairness to small plugin developers.

If a new plugin is promoted by name, and users cannot find it without a more specific search, or by going to page 5 of the results, developers will have a really hard time being successful even if they promote themselves well.

I dug around for a random plugin that is not mine to prove my point and found this one:

The Stars at Night

If you search the above text, the plugin shows up in 10th place, rather than what you'd normally expect which is the first spot as an EXACT match for the name of the plugin.

Can we improve the plugin search to prioritize exact matches by name?

Attachments (1)

Screenshot 2025-06-09 at 15.00.13.png (465.4 KB) - added by andrewhoyer 9 months ago.
A screen shot of the plugin search described in the ticket.

Download all attachments as: .zip

Change History (7)

@andrewhoyer
9 months ago

A screen shot of the plugin search described in the ticket.

#1 @andrewhoyer
9 months ago

#62999 was marked as a duplicate.

#2 @SirLouen
9 months ago

@andrewhoyer the plugins page uses an API provided by the WP meta to get the plugins. WordPress core only handles and displays such response.

For this reason, I would suggest opening a ticket in the meta trac https://meta.trac.wordpress.org/
And then report here the number of such ticket

(I posted this in the other duplicate)

#3 @andrewhoyer
9 months ago

@SirLouen Thanks for noting that. I went over to WP Meta and dug around a bit. There seem to be many similar types of requests there. This one in particular has been going on for 8 years and is still open, and I believe it's a match for this ticket.

https://meta.trac.wordpress.org/ticket/2642

#4 @SirLouen
9 months ago

  • Resolution set to reported-upstream
  • Status changed from new to closed

It appears that there is a resolution there https://meta.trac.wordpress.org/changeset/13778

I'm closing this ticket because it has been already reported upstream as it seems

My recommendation is that you continue there the conversation and add more about this topic

#5 @davidbaumwald
9 months ago

  • Milestone Awaiting Review deleted

#6 @desrosj
8 months ago

#62999 was marked as a duplicate.

Note: See TracTickets for help on using tickets.