WordPress.org

Make WordPress Core

Opened 9 years ago

Last modified 7 months ago

#15971 new feature request

Add ability to rate and report compatibility of plugins from wp-admin

Reported by: jb510 Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 3.1
Component: Plugins Keywords: needs-patch
Focuses: Cc:
PR Number:

Description

For the millions of downloads some plugins get there are way to few ratings on them. I think the ability to rate and report the compatibility of plugs from the backend dashboard page would dramatically increase participation in rating.

This could be accomplished most easily placing a link to the "details" of a plug-in (like the one that appears while searching for a plug-in) after it is installed on plugins.php.

This could be accomplished even more effectively by showing direct link next to each listing on the plugins.php page link stars/compatibility and link text reading "rate now or "report compatibility now"...

For reference I point you to the excellent new to FireFox 4 (beta) add-on compatibility reporting features.

Attachments (1)

plugin-rating-mockup-1.png (35.1 KB) - added by jb510 8 years ago.
Draft mockup of Rating and Compatibility Column on plugin screen

Download all attachments as: .zip

Change History (22)

#1 @jb510
9 years ago

  • Cc jb510 added

#2 @kapeels
9 years ago

  • Keywords plugin star ratings compatibility report admin removed

#3 @scribu
9 years ago

  • Summary changed from Add abilty to rate and report compatibility of plugins to wordpress dashboard to Add abilty to rate and report compatibility of plugins from wp-admin

#4 @jane
9 years ago

  • Milestone changed from Awaiting Review to Future Release

Could have sworn we already had a ticket like this, but can't find it, so I guess it never made it from chat/blog to Trac. Yes, reporting on compatibility in the admin would be better, since most people don't bother to go back to the repo on .org to do so. Require a comment that describes the issue if reporting incompatibility.

#5 @strider72
9 years ago

If this link were added automatically for any plugins that are installed from WP-Extend, it would also serve as a subtle indication of which plugins are NOT managed/version checked by that system.

Just pointing out a small positive side-effect of this idea.

#6 @dremeda
8 years ago

  • Cc dre@… added

#8 @aaroncampbell
8 years ago

  • Cc aaroncampbell added

@jb510
8 years ago

Draft mockup of Rating and Compatibility Column on plugin screen

#9 @jb510
8 years ago

Is there any reference doc / API for interacting with .org? This is really way beyond my skills but I'd still be willing to try to get something started...

FWIW,
A rating URL looks like this:
http:// wordpress.org/extend/plugins/{plugin-slug}/?rate={1-5}&topic_id={#####}&_wpnonce={##########}

Compatibility URL:
http:// wordpress.org/extend/plugins/{plugin-slug}/?compatibility[version]={wp_version}1&compatibility[topic_version]={plugin_version}&compatibility[compatible]={0 doesn't or 1 works}

Things to think about:

  • In order to rate a plugin, one needs to be logged in to .org. Do we save those login credentials as part of their user profile or require them to login at the time of rating/reporting? Does that authorization get saved somewhere permanently or in a transient? (this is the stuff I have no idea on how to handle)
  • When an update is available we should probably display the report compatibility of the update.
  • I've never liked having the "Average Star" rating appear next to and separately from "your rating" on .org so I've proposed combining them or not showing average rating. I don't know that we need to show average rating to someone that has already installed the plugin.
  • If ratings and capability is show in it's own column we probably need a screen options settings to show/hide the ratings column like the description can be, sites built for professional clients will probably often want to hide this.

I've attached a first draft mockup.

#10 @SergeyBiryukov
7 years ago

#21896 was marked as a duplicate.

#11 @mordauk
6 years ago

  • Cc pippin@… added

#12 @nacin
6 years ago

#25437 was marked as a duplicate.

#13 @SergeyBiryukov
5 years ago

  • Summary changed from Add abilty to rate and report compatibility of plugins from wp-admin to Add ability to rate and report compatibility of plugins from wp-admin

#14 @chriscct7
4 years ago

  • Keywords needs-patch ui-feedback ux-feedback added

UX-feedback: is there really a need for this?
UI-feedback: need a design for it if there's a need.

#15 @SergeyBiryukov
4 years ago

#36541 was marked as a duplicate.

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


2 years ago

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


17 months ago

#18 follow-up: @boemedia
17 months ago

We discussed this ticket in design triage today. Since there have been multiple tickets opened on this topic, we acknowledge there's a need for this. However, we understand the problem @nacin mentions in #25437:

"The problem here is we would need to link an individual WordPress user (and potentially the same person using multiple user accounts across multiple installs) against a single WordPress.org user (as in, users on the actual website)."

Therefore, we can't really see a way of moving this away from the actual plugins-page on WordPress.org.

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


7 months ago

#20 @karmatosed
7 months ago

  • Keywords ui-feedback ux-feedback removed

Removing the labels as discussed in this week's design triage that for now design feedback isn't needed. This can absolutely be added back in should it be.

#21 in reply to: ↑ 18 @jb510
7 months ago

Replying to boemedia:

We discussed this ticket in design triage today. Since there have been multiple tickets opened on this topic, we acknowledge there's a need for this. However, we understand the problem @nacin mentions in #25437:

"The problem here is we would need to link an individual WordPress user (and potentially the same person using multiple user accounts across multiple installs) against a single WordPress.org user (as in, users on the actual website)."

Therefore, we can't really see a way of moving this away from the actual plugins-page on WordPress.org.

I'd missed this comment, sorry for the late reply.

I agree that @nacin identified a challenge in completing this in #25437 (the need to link to .org profiles), however is there a trac ticket for that specific portion (something global) of this ticket? Total side rant, but Trac still doesn't seem to have dependencies built into it to clearly indicated when "X is blocked by Y").

It would seem that UX feedback "logging in to .org" from the wp-admin is a good place to start. If a user wants to rate/review a plugin from the dashboard how should that be presented to them so it's clear what's happening. We obviously already have massive user confusion of users logging into their site vs. .com. Now they're going to have "3 wordpresses to log into", how that flows is going to be extremely important.

Note: See TracTickets for help on using tickets.