[wp-meta] [Making WordPress.org] #2653: 404 on Browse url

Making WordPress.org noreply at wordpress.org
Wed May 17 23:22:37 UTC 2017


#2653: 404 on Browse url
------------------------------+-------------------------------------------
 Reporter:  tellyworth        |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - Future
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-------------------------------------------

Comment (by joyously):

 > A redirect to https://wordpress.org/plugins/browse/featured/ slipped
 into r5248

 This is bad UX since it takes an inclusive URL and turns it into a dead
 end.
 I think the intent of a URL like `https://wordpress.org/plugins/browse/`
 is to show everything that there is. I always thought it should show the
 main taxonomy of the plugin directory, with counts, and no actual plugins.
 If that idea isn't popular, my fallback would be to have it show plugins
 ordered by plugin name, with an alphabet of links to jump to the sections
 for each letter.
 It definitely should not be the same as
 `https://wordpress.org/plugins/browse/new/`, although the Browse page
 could have links to other ways to browse like New or Popular. I think
 Updated can be very useful, but not promoted with a link. It should work,
 though, if you know the URL.

 By the way, looking at the Featured page, why do they never change? Who
 determines what goes here? And why the confusing language of having
 "feature plugins" under "Beta Testing" and a few big plugins under
 "Featured"? I think the plugins that could go into core would get more
 interest and feedback if they were shown by default (featured), instead of
 always showing the same 6 everyone knows about.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2653#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list