Show reasons for why plugin is broken

  • This is a request for the www.ads-software.com website’s way of displaying plugin broken/working information.

    When someone claims that a plugin is broken, they should provide a link to a forum ticket where their problem is discussed. Once that ticket is resolved, they should be asked to reconsider their claim that the plugin is broken.

    This way, if anyone wants more information to help them decide whether to update a plugin, they can check the broken claims further.

    Alternatively, anyone submitting a “broken” claim should be prompted for the details, which can then be viewed by others.

    This prevents unsubstantiated claims and/or irrelevant ones, i.e. claims related to unique situations that don’t apply to my own sites and therefore don’t prevent me from updating.

    Thank you,
    Gal

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    When you mark a plugin as broken, you ARE prompted to make a post. Not everyone does. Can’t make ’em :/

    This prevents unsubstantiated claims and/or irrelevant ones, i.e. claims related to unique situations that don’t apply to my own sites and therefore don’t prevent me from updating.

    Honestly? You just described most ‘broken’ reports ?? Take them with a grain of salt.

    Thread Starter Gal Baras

    (@galbaras)

    I don’t recall ever seeing a report like this around the rating. Is this because nobody (sometimes out of 5 or 6) posted any feedback or because it’s not linked from the plugin page’s sidebar?

    Take Jetpack, for example, which is a very popular plugin and gets almost immediate feedback after each release. 5 people say the latest version is broken and 10 (!) say the previous one was broken. I can see reviews and ratings, and there is a link to the support forum for the plugin, but where is the direct feedback from those who marked the plugin as broken?

    Contact Form 7 is very similar. I can see everything else, but no direct feedback on the voted release combination.

    In fact, in the support forum, the plugin version is not a sortable or selectable field and in support threads, the plugin version is not listed unless the person who starts it bothers to include this information (which should be common practice, but happens rarely).

    If there’s a quick way to link a broken vote for a plugin with the reason given, I’d love to know about it. An example would be wonderful.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Show reasons for why plugin is broken’ is closed to new replies.