There's a wrong way to give plugin feedback on

Chris Lema

plugin-feedback-wordpressA lesson I learned a long time ago

Years ago I worked on a project that was specifically for the last group of scientists that had direct access to the President of the United States. It was a big deal to be working with these high energy physicists. So not only did we create a site to collect some key data from them, but I also offered to manage support on the project as well. My team would be the ones getting the emails and answering the phones.

I’m sure they didn’t love it, but I thought it was a critical enough project that we didn’t want anything to go wrong.

Now this was back in the early web days, somewhere around 1995 or 1996. So you can imagine the kinds of calls we got.

“My printer doesn’t work…”

But I recall one very clearly. The admin assistant for a high energy physicist on the East Coast called us to tell us that our web application wasn’t working. At the end of a multi-step data entry process, users were allowed to print the data they’d just submitted for their own records.

Well, according to her, the print button didn’t work. So we started going thru the normal steps.

  • Could she print another web page, like No.
  • Could she print from another application, like from Word? Nope.
  • Had she ever been able to print? Never.

In fact, that’s why she had been calling – because we now had promised (via the “Print this document” button on the page) that her printer would finally work, and it wasn’t.

I remember this story because I learned on that day that developers of any product will often get feedback and complaints about things that fall outside the scope of their work. That’s the nature of the beast.

But that didn’t stop me from trying to help her out. And it doesn’t stop plugin developers (the good ones) from trying to help users even if it’s not their plugin that’s creating the problem.

Misaligned Support Costs

I wonder (often) how much time the developers behind Gravity Forms, Easy Digital Downloads, or MemberPress have to spend to deal with issues that actually aren’t their own product?

Don’t answer that, if you know, because the answer will just be depressing.

People buy cruddy themes, written poorly but with 23 different sliders embedded in them, and then get mad when a plugin doesn’t work. And instead of complaining about their beautiful theme (which looks nothing like it did on the site they bought it from), they head over to and complain about the plugin.


Plugin Feedback, The Wrong Way

But it’s for that reason that I wanted to highlight a situation I often see on the plugin repository, where we can rate plugins. It turns out some people not only have unreasonable expectations, but don’t really understand how to best give plugin feedback.

So here are five ways to do it wrong.

  1. Rate the plugin poorly even if it does exactly what it says it will do.
  2. Rate the plugin poorly because it couldn’t predict your scenario.
  3. Rate the plugin poorly because you buy crappy hosting.
  4. Rate the plugin poorly because it conflicts with your other 74.
  5. Rate the plugin poorly because additional features cost money.

When you read them, they sound silly don’t they? And yet, I see it happen all the time.

That image, at the top of this post, is real. I didn’t make that up. A user decided that even though the plugin did exactly what it said it would do, it still deserved only a 3 – because they wanted something else beyond that.

Plugin Feedback the Right Way

Everyone knows that a plugin that works perfectly on a developer’s computer may still have an issue in your own environment. When something doesn’t work well, here are some simple steps you might follow before a rating entry.

  1. First, contact the plugin developer directly.
  2. Try to do this privately (email, ticket). Not on Twitter.
  3. Give them enough data for them to evaluate things.
  4. Offer to take screenshots or do a screen sharing session.
  5. Turn off plugins to eliminate cross-contamination.
  6. Check things with a simple theme, like TwentyEleven.
  7. Provide this data back to the developer. Share insights.
  8. Follow the directions (replies) from the developer.
  9. If things are fixed, thank them.
  10. If they’re not, and you plan to rate them, contextualize it.

See, if you do all of the above to try to mitigate an issue, you might discover that the issue was your plugin, or your theme, or your host. Then, if you want to give a plugin a rating record on, you can be specific.

“This plugin doesn’t work with my theme (xyz) and has a conflict with the infrastructure at my host (abc). The developer was helpful but couldn’t get it to work in my scenario. For that reason, this gets a 3 star rating.”

That’s a helpful review. Because it warns people with that theme or host, to be careful.

“This plugin does everything it says it does. For that I gave it a four star rating. I really wanted to give it five stars, but for me, a plugin that does xyz really should include abc in the core feature set and this one doesn’t do that (which they clearly state on their site).”

Now if someone reads that, they can determine if they agree that abc is needed or not.

More often than not, I’d hope we see high ratings that simply say things like this.

“I spent two hours testing different scenarios to find out that the plugin was right and my cruddy theme was causing the issues. Unfortunately, it wasn’t the theme developer who helped me with it, but instead was the plugin developer. I hate that I wasted their time, but five stars for great support and I’m waiting for their paypal email to send them cash.”

I mean, seriously, who wouldn’t want to read that review.

All that said, there’s a real art to writing a great review. I don’t have it. That’s why I stuck to the “what not to do” advice. If you want to talk about the master of positive review, Mark Jaquith is a member of the WordPress community and you should see his work.

Powered by the Rainmaker Platform

The Rainmaker Platform by Copyblogger Media is the complete website solution for building your own online marketing and sales platform. In short, it makes the technology part of running an online business simple so that online marketers and business owners can focus on building audiences and growing businesses.

Start your free 14-day trial

Join more than 5,000 others

My posts. Your inbox. Beautiful.


  1. I know that the main thing I’m guilty of is not taking the time to give feedback. Most times if a plugin doesn’t work for me or creates conflicts, I’ll just move on. Especially because for most needs, there are always more than one out there. Only the biggies or those that really stand alone get me to stop and take the extra time. And I’m not proud of this. This is a great reminder that as a community we should give support and take responsibility for improving the quality of the work out there, and sharing information that can be helpful to others.

  2. Yes, yes, yes.

    Seen various like the ones you’ve listed, and others.

    All-time memorable one: rate the plugin 1-star because it helpfully alerted the user that his WordPress setup had a problem, and the documentation page it sent him to to explain how to fix it was too long for the user to want to read.

  3. Interesting way to put it, kind of a reverse psychology method? What not to do is easier told than a list of a few ways to do it well :)

    We think there’s a lot of scope for improvement, especially in the documentation and procedure for WordPress users (admins), wherein the procedure to use various different debugging and fault finding tools could add more value. There’re a lot of Hosts who provide Staging versions of a live site, which too could be utilised well.

    There could be a checklist, above all, on the website to confirm (psychological barrier) before rating a particular plugin/theme lower than say 3/5. It can stop people from rating 1/5 without having done proper evaluation of the performance. #JustAThought

  4. Absolutely agreed. And try to avoid the “riddle with bugs” statement:

    Great post and great reminder, Chris!

  5. Really good points. I have to say though, that providing support for issues outside of the scope of our plugin (FooBox), is not only costly, but sometimes it’s also not the best service to the customer. Anytime an issue comes up with NextGen Gallery (which FooBox integrates with), I can help them out if it’s just a setting, but if the plugin is not behaving correctly I find it always more expedient for the customer for me to point them to the NextGen forum.

    But your main point is the feedback and THAT is 100% spot on. We’re trying to educate our customers more and more through the support request process on how to give good feedback, Thanks!

  6. There are a lot of problems with the feedback system. In addition to the feedback itself, the feedback system does not really account for time. What if a plugin is great for a while, gets good ratings, then falls off. Ratings are great, performance is poor. (NextGen).

    The reverse is true too…one bad release of a great plugin can make it seem, in the repo, like garbage when it is actually a great tool.

    That all said, I still think the WP Repo needs to allow sort or filter based on ratings.

  7. Unfortunately, I suspect those who need to read this are not part of your audience.

    I try to review plugins whenever I can, although I have been criticised for giving very low ratings for plugins I could not use due to failures in the plugin code. Usually things like debug errors and lack of https support make me plummet my ratings quite substantially (usually 1 or 2 stars) since the problems often make the plugin utterly useless to me.

  8. On the flipside, if you’re evaluating plugins, I find that it’s a good idea to actually read the reviews and not judge based solely on the average rating. Filter down to the one- or two-stars and look at what people are saying. Then do the same for the 4- and 5-star reviews. :)

  9. as @Ryan Hellyer pointed out – the main issue with this post ( which is excellent – btw! ) is also the main problem with both the WP review system and the support forums themselves – the technical knowledge gap between the suppliers ( developers ) and the consumers ( plugin user ).

    In some cases, the consumers have little above zero knowledge of what they are doing – WP made it easy for them to find, install and then slam a plugin that did not do everything the hoped that it might.

    The forums and rating system need a number of important changes to become relevant and truly useful to both parties ( here are a few of the many… ):

    – Automatic notification of new forum support topics for plugin developers – so basic, it’s crazy it does not work this way – users might wait weeks for the dev to actually spot that they’re raised a support issue – any response at this point is likely to be of little value.
    – A reminder to users leaving a support request that if they do not check the tiny little box asking them if they want to receive reminders about replies they will never remember where they posted their question and this will become yet another start, no reply – dead-end support request.
    – A better way for users and developers to track and maintain support requests – built into WordPress itself.
    – A better way to encourage ( reward? ) developers to offer support and to continue to maintain their plugins
    – a pay wall / process / thing – to stop people giving one star and then having no responsibility to explain or justify

    P.S – Here is my latest 1 star review:
    “Only exports what developers chose for it to export.”

    Sorry if my answer trailed off at the end – I got distracted with support requests!

  10. Interesting to see that two of my beta testers for and contributors to WP Post to PDF Enhanced have already posted comments here . :-)

    Indeed, a bad review can be almost as big a time-waster as fluff reviews which make everything sound great, until one gets into the throes of trying to get something to work or asking for support (which is why, quite often, the best review process is to cull through the support threads to see how responsive the developer is and what types of issues have been reported – as well as the types of WP users reporting).

    I came upon this post after posting my first truly thumbs-down review (which I hated to do, BTW). I tried to be as constructive as possible, and avoided base sarcasm and needless opining (I hope). Still, it pained me to have to write a negative review for a plugin which was once so great but now – in the hands of a new development team – has been turned to the Dark Side.

    The review system does need some embellishment; I concur. One of my suggestions would be a way for a previous reviewer to go back and modify his rating (as suggested, when plugins change in quality and features from one revision to the next, often a review for a previous version carries little weight for the current one).

    Anyway, thanks for the post. Great read.

  11. Thanks Chris. Great post. There seems to be a legitimate distinction that was glossed over. You wrote that it’s wrong to rate a plugin poorly if it does exactly what the developer ways it will. Later you had an example of an acceptable review that gave a low rating because of unincluded features (because it explained the reason for the poor rating).

    It seems that there’s generally no explicit guidelines for rating. Perhaps all rating systems should have 2 scores: one for features and one for performance.

    And Lewis R, I agree that reading the support threads could be a better indication than reviews.

  12. Hello,

    I was just yelled at by a developer on both Twitter/ for giving a one star review. I was suggested to read this link as a way to write a more detailed 1 star review.

    First, lets look at this issue from the customer point of view. We as technical people understand that many factors go into software issues. It becomes very frustrating when our users complain about the lousy system when they are the cause of the problem. Ok, I get that and why this article is written.

    However, the other side of this is that the majority of people using WordPress are non technical users and not only are they not able to write a detailed review, they don’t want to! Is it is the job of the person who isn’t being paid to support WordPress to contact the developer and work out the bug/make a technical support request? It is not.

    No one likes criticism, but sometimes criticism is justified and if you can’t take criticism then don’t release public software. Don’t make your customers your technical support. Nothing is perfect, but if a customer says they prefer something else then accept that and accept that there will always be those who disagree with your biased perceptions of your software.

    • Leaving a one-star review is fine, if it’s for appropriate reasons. Far too often people leave a one-star review because a plugin doesn’t do what “they” want, even if the description is clear on what it does. Or they leave a one-star review because they had a question and the answer was “no.” Since they didn’t like the answer, they left a poor review, even if the rating isn’t for emotional support. If a product is clear that it will accomplish X and it doesn’t do it, leave a poor rating and explicitly highlight what it doesn’t do.

  13. @Chris, when I read your post the first time, I was sceptical and thought that only very few (and literally idiot) people could leave a rating like that without using their common sense and that it happens extremely rare (by accident, lol). I released my first free WordPress plugin 2 months ago after countless hours of work and got positive feedback so far.

    I just got a “poor” rating because the person didn’t like how I phrased a text inside the plugin and he/she didn’t bother to understand how to use it when everything was completely clear. I wasn’t even contacted on the “Support” area about this. Moreover, he has spelling mistakes in his comment. Check out the 2 stars rating here: – Is there something we could do about these ratings? If they are non-sense, the WordPress stuff should review and consider removing them, or not?

Leave a Reply

Your email address will not be published. Required fields are marked *

Disclosure of Material Connection: Some of the links in the post above are “affiliate links.” This means if you click on the link and purchase the item, I will receive an affiliate commission. Regardless, I only recommend products or services I use personally and believe will add value to my readers. I am disclosing this in accordance with the Federal Trade Commission’s 16 CFR, Part 255: “Guides Concerning the Use of Endorsements and Testimonials in Advertising.”


I regularly schedule calls to answer your questions using
a service where you only pay per minute.

call me
  • People don’t fully grasp how strategic Chris is. I love that about him and count on it all the time.

    Karim Marucchi
  • Chris often breaks paradigms and has me rethinking the way I approach my business.

    Jeff Zinn
  • Chris always gives me something to think about – a new lens through which to examine my business.

    Lucy Beer
  • Chris’s advice has helped me to make better decisions about my business, and manage my clients better.

    Natalie MacLees
  • Chris has been a source of wisdom and insight in business and product strategy, startups, entrepreneurship, and more.

    Austin Gunter
  • Chris is one of those rare people who can take a difficult subject and make it easy to learn and remember.

    Dave Jesch
  • Chris has a heart of gold and is willing to reach out and help. He has helped me in several ways both in WordPress coding and consulting with me on my business. He has been a blessing in my life and look forward to a long friendship with him.

    Gregg Franklin
  • Chris Lema always drops knowledge bombs that makes me think about how I can evolve my WordPress-powered business. Even more valuable is that he does it in a way that makes drastic change seem achievable.

    Chris Ford
  • Whether it's product strategy or a question about which plugin to use, I know Chris will get me an answer faster than anyone else.

    Steve Zehngut
  • Chris is a great mentor, instructor and friend. He fills all these roles with a down to earth style and ease that actually encourages you to believe that success is within your grasp.

    Alex Vasquez