WordPress.org

Making WordPress.org

Opened 4 years ago

Closed 3 years ago

Last modified 3 years ago

#1574 closed enhancement (fixed)

Search

Reported by: obenland Owned by: tellyworth
Milestone: Priority: normal
Component: Plugin Directory Keywords:
Cc:

Description

Implement a better way to search plugins than WordPress core or Sphinx. We should investigate alternatives and see what makes the best sense for us.

Change History (15)

#1 @jb510
4 years ago

I assume ElasticSearch and Solr are options on the table? or are there limitations?

Also.. is part of the search roadmap going to include searching and sorting by rating?

#2 @dd32
4 years ago

  • Owner set to tellyworth
  • Status changed from new to assigned

ElasticSearch has definitely been mentioned, it's widely used by WordPress agencies so has a fairly good libraries to seamlessly interact with WordPress Queries.

The existing plugin directory relies upon Spinx.

I expect whatever solution is chosen will open the door to further filters down the line, but the priority for the initial roadmap is to match the existing search performances.

#3 follow-up: @dustycat
4 years ago

I'd like to see the whole search interface improved

e.g. when I am looking for plugins and have entered a search term, the results list is in a random order as far as I can tell. If I click on 'Featured' or 'Popular' etc in the menu, my search term is lost and I am shown ALL plugins, not just ones relating to my search term.

So I'd like to see either that the 'Featured', 'Popular' etc can be searched within OR that once I have searched for a term, I can sort the results by star rating, number of downloads, last updated etc. That's got to make life easier than ploughing through 10 or more pages of results trying to find the 5* plugins.

Also, is there a way of making the plugin support forums more searchable? At the moment, when you go to the Support tab for a plugin, you can only see support tickets in reverse chronological order. We are warned to search to make sure we aren't opening a duplicate ticket, yet there isn't a way to search from that page. Going over to the support forum and trying to search there is nigh on impossible because you can't filter search results to only show the plugin that you are having problems with. Yes, you can try putting 'Plugin: plugin name' as part of your search criteria, but you still end up with potentially hundreds of irrelevant results.

#4 in reply to: ↑ 3 @joemilesxibo
4 years ago

I'd agree with this - it appears random at the moment.

Perhaps there could be options like Amazon search results where they have a drop-down menu with 'popularity' and 'rating' as options to sort by.

Replying to dustycat:

I'd like to see the whole search interface improved

e.g. when I am looking for plugins and have entered a search term, the results list is in a random order as far as I can tell. If I click on 'Featured' or 'Popular' etc in the menu, my search term is lost and I am shown ALL plugins, not just ones relating to my search term.

So I'd like to see either that the 'Featured', 'Popular' etc can be searched within OR that once I have searched for a term, I can sort the results by star rating, number of downloads, last updated etc. That's got to make life easier than ploughing through 10 or more pages of results trying to find the 5* plugins.

Also, is there a way of making the plugin support forums more searchable? At the moment, when you go to the Support tab for a plugin, you can only see support tickets in reverse chronological order. We are warned to search to make sure we aren't opening a duplicate ticket, yet there isn't a way to search from that page. Going over to the support forum and trying to search there is nigh on impossible because you can't filter search results to only show the plugin that you are having problems with. Yes, you can try putting 'Plugin: plugin name' as part of your search criteria, but you still end up with potentially hundreds of irrelevant results.

#5 @obenland
4 years ago

Work on this so far: [2924,2925,2934]

@tellyworth, would you mind referencing the appropriate ticket numbers in your commits? It helps future us to better understand why changes were made.

#6 @obenland
3 years ago

In 2972:

Plugins Directory: Avoid immediate dependency on Jetpack.

Fixes a fatal error when Jetpack is not activated on the site.

See #1574.

#7 @obenland
3 years ago

  • Milestone set to Plugin Directory v3 - M2

This ticket was mentioned in Slack in #meta by obenland. View the logs.


3 years ago

#9 @tellyworth
3 years ago

In 3073:

Search: ignore WP's default list of stopwords.

See #1574

#10 @tellyworth
3 years ago

In 3074:

Search: incorporate comment_count into score, as a proxy for popularity.

This should probably include the active install count as well, and perhaps some other factors.

See #1574

#11 @tellyworth
3 years ago

In 3075:

Add pagination links.

This is mainly for testing search, as the theme will soon be replaced.

See #1574

#12 @tellyworth
3 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

Closing this as ElasticSearch searching is now working well enough to call it complete.

There is still tweaking to be done and I expect some bugs, but those are best handled in separate tickets from now on.

This ticket was mentioned in Slack in #meta by obenland. View the logs.


3 years ago

#14 @dd32
3 years ago

In 3896:

Plugin Directory: We no longer need to let Jetpack Sync know about updated posts, as this now fatals, the newer versions of Jetpack automatically sync post updates.

See #1574

#15 @samuelsidler
3 years ago

  • Milestone Plugin Directory v3 - M2 deleted

Milestone Plugin Directory v3 - M2 deleted

Note: See TracTickets for help on using tickets.