WordPress.org

Ready to get started?Download WordPress

Ideas

wordpress.org plugins compatibility widget

  1. sareiodata
    Member

    12345

    How about if the user wants to click broken, he **must** provide feedback?

    This feedback could take the form of a new topic in the support forums.

    This is a really good idea! +1

    Posted: 4 years ago #
  2. TobiasBg
    Member

    Hi,

    I agree that "broken" should force a feedback/problem description to be entered.

    I also would like to mark topics as "resolved", as well as I would like to remove/edit tags that users add to their support questions, because they use unneeded/wrong/misspelled/too many tags.

    Regards,
    Tobias

    Posted: 4 years ago #
  3. Truly a an excellent idea, but this comes against the fact that not all users have a proper wp.org account, and therefore either only the truly benevolent ones will leave a message, or the forum will be required to accept anonymous postings.

    As an aside, in the particular case of an anonymous "doesn't work" feedback, it would be nice for the started thread to gather the user's technical profile (sort of a simplified phpinfo + wp infos, anonymized?) that would only be visible to the developer ; giving him a chance to

    Thirdly, how about making it possible for devs to gain/regain "does work" status by asking verification to a team of "verified" users? A way to prove they did right, or that a given vote should not be taken into account.

    Posted: 4 years ago #
  4. TobiasBg
    Member

    @xibe

    Users can not vote without being logged in, so they need WP.org account anyway.

    And I guess that is another hurdle that might need to be discussed, as it pretty surely keeps users from voting (because they don't want to register for a site, just to be allow to perform a click).
    (I'm aware that the registering requirement keeps users from sending multiple votes though, which is good.)

    Regards,
    Tobias

    Posted: 4 years ago #
  5. logikal16
    Member

    12345

    If most people aren't crossing the WP.org sign-up barrier, what makes you think they'll *also* enter a description of why the plugin won't work?

    We should move this into core with the assumption that this will improve the quality of all plugins.

    An idea would be to list active plugins on the Dashboard, with "Works" or "Broken" buttons beside each. If broken, a "What's wrong?" box will appear and must be filled in to submit.

    Without requiring a WP.org account, the amount of participation will grow exponentially.

    Posted: 4 years ago #
  6. Peter Westwood
    WordPress Lead Developer

    It is frustrating to not get feedback as to why people don't think something is working.

    I'm not sure we need to mandate that people provide a reason why they are marking something as not working - you will get a lot of "It doesn't work" spam.

    It would be better to make it really easy to report an issue from the plugins page in a way that the plugin author gets to know about and can feedback on.

    Maybe we could also have a way of auto-closing threads based on code-checkins like we do with trac.

    Posted: 4 years ago #
  7. Mac_Boy
    Member

    I am user, have used lots of plugins at my company and deployed lots of 'apps' with WPMU-based blogs. When I eval plugins, I steadfastedly ignore the ratings and the Compatibility. Why?

    Guess why? Because just like me, many folks don't register to give 'positive' feedback. I just now registered to make this point.

    If the plugin developers are getting frustrated in zero-to-low quality feedback then perhaps the Compatibility section should be improved as suggested above: a "low" results in an auto-generated feedback form with the User's login auto-filled-in.

    Sincere appreciations too all of you plugin developers! We love you all. Sorry for not giving positive feedback or imrpovement suggestions in the past.

    My suggestion is to remove the compatibility mode. Go back to star ratings combined with an auto-forum posting for low star clicks. Combine that with a Developer's ability to "manage" their own plugin's feedback and forum postings.

    Posted: 4 years ago #
  8. I agree with Scribu and Mark Jaquith that marking a plugin "broken" should require a reason and open a thread in the support forums...and that we (plugin authors) need to be able to mark threads as solved.

    I think Westi took it to it's logical conclusion though, which would be to allow (encourage?) users to give this feedback right from the plugins page in WordPress. We'll have to work out a way to make it look nice and function well even though some plugins (ones that aren't in the repository) won't have the UI at all.

    Posted: 4 years ago #
  9. Robert Chapin
    Member

    12345

    Registration should still be required for voting.

    I think the "forced thread" idea will be a huge problem for stale plugins though.

    My idea is: Only do the "forced feedback" for plugins that are marked tested for that version by the author. If the author says the plugin is compatible to 2.8.6 then by all means let anyone spam up the Broken button for version 2.9.1.

    Posted: 4 years ago #
  10. Jeremy Clarke
    Member

    12345

    +1 for at least recommending that they tell you WTF is actually wrong with the plugin for them. I think making it mandatory is a good idea but just putting the form in their face is an excellent step in the right direction.

    In my experience seeing something like "okay, well what was wrong with it" tends to make me ask myself that question (duh) and when I do I often discover that I didn't really know the answer. This begins the process of me trying to figure out exactly what is wrong (otherwise known as testing). The result as often as not is that I figure out what was wrong with my own setup and fix it, come up with a workaround, or pinpoint the problem. By the time I'm ready to fill out the form (currently the 'form' is the comments on the plugin authors blog) I either have a fix ready or enough info to make it fast for the plugin author to fix it.

    So: Make sure that the 'it doesn't work' report isn't filed until after the person sees the request for more info, I think that would cause less broken claims to be filed because people would realize they are the problem before submitting the report.

    For bonus points it should lead them in the right direction by hinting at testing solutions in the reporting form, something like:

    Before we note that its broken please tell us what exactly is broken:

    What doesn't work? [textarea]
    Did previous versions of the plugin work? [yes/no]
    Did the plugin work with previous versions of WP? [yes/no]
    How to reproduce the problem? [textarea]

    [submit your report]

    [I don't want to add details, mark as broken without report]

    Posted: 4 years ago #

RSS feed for this topic

Topic Closed

This topic has been closed to new replies.

  • Rating

    12345
    22 Votes
  • Status

    Good idea! We're working on it