Make WordPress Plugins

Tagged: support Toggle Comment Threads | Keyboard Shortcuts

  • Ipstenu (Mika Epstein) 8:32 pm on September 12, 2016 Permalink
    Tags: , support   

    Forums Status Update (Sept 12) 

    Subscriptions should be working again.

    Feeds have _moved_ and I’m really sorry about that. Hopefully we’ll get an nginx redirect in there sooner rather than later but basically it’s this: https://wordpress.org/support/plugin/akismet/feed/

    We’re using WordPress now, so any time you see a view you want to follow in RSS, slap `/feed/` on the end and it will probably work.

    There’s also this URL: https://wordpress.org/support/plugin/akismet/active however, as you will notice, there is no ‘feed’ for it. Those are custom (non default WP) views and are all support threads with Closed and Resolvedt filtered out, then sorted by last reply. We’re working on feeds for those and the old plugin committer feeds. I want that back too. Right now, I suggest you use the per-plugin feed to get a list of your new bugs etc, and then subscribe to the post (or add it to favorites).

    Sadly, ‘cost overruns’ have been the story of this migration. We had hoped to be done with everything by the 5th, but that proved a gross underestimate.

    We know there are a lot of ‘smaller’ features everyone loves and have gotten used to making their lives easier that we’re now doing without. It sucks. Trust me here, the mods have ‘lost’ more tools than anyone else. This upgrade had to happen, though.

    Also the reason I’m closing these posts to comments when I make them is I have no additional information to provide. Historically, if I leave them open people will posts complaints and rants (which I can do nothing about save sympathize), bug report (which we either already know about, or should have been posted elsewhere), or ‘thanks’ (which we all appreciate, but get spammy). And pinging me on Slack won’t get you any answers more than I’ve posted. This is what I know as I know it.

    All I have for you now is a plea to be patient. This is a massive undertaking that for a long time was deemed impossible. But slowly, as we clean up the mess, things will get better and the pros of the move will reveal themselves. Like having Akismet actually catch spam for a change.

    Please check Support Forums: Meta Trac before filing a bug report/complaint. And if you have suggestions for fixes, jump in and let us know! The bonus of being on bbPress now is that if there are plugins that can do what we need, we can actually use them!


  • Ipstenu (Mika Epstein) 4:24 pm on May 3, 2016 Permalink |
    Tags: , support   

    Handling Bad Reviews 

    In general, the Plugin Review team is not the go-to recourse for bad reviews.  Instead, we have a totally brilliant forum support team! There’s some overlap of jurisdiction of course, and some of us are on both teams, but the point here is you should go to the right group to get the right help.

    I’m also going to put this out there. You will get a bad review. Most of the time, it will not be deleted. So before you get any further in this post, know that the way you chose to respond, in public, to a 1-star review of your plugin is your own choice.

    Our goal with the WordPress.org repository is to have a good place for users to get plugins that fulfill their needs. The reviews are an extension of that, and should viewed as a way for users to educate other users on their experiences. Also a review is about an experience. If someone’s experience with your product is poor, that doesn’t make their review invalid. And to go back to that previous statement, the way you react to those poor experiences is going to impact your reputation, and that of your plugin, a heck of a lot more than that review.

    Now, that said, we have a few ‘common’ types of problems with reviews. This post is going to help you handle them and explain when you should call for help, as well as from whom. Later on we’ll be adding it to our documentation, once it’s refined as best we can make it. Please remember, we do not want to make a ‘rule’ for everything. That just invites people to play rules-lawyers and tip over everyone’s cornflakes.

    Here’s how you do it and when and why.

    First off… How to add a tag!

    99.999999% of the time, you’re going to be adding ‘tags’ to posts. This is so easy, you may kick yourself for missing it. On a post, look on the right hand side, under About this Topic and you’ll see a section for Tags

    Tags are listed on the right hand side of a post

    This is a free-form field where you can add any tag you want. Anyone can add any tag. The forum moderators have an easy way to know who added what, though, so keep in mind we do monitor that. If you want to add a tag to a post and reply, add the tag, press the Add button, and THEN come back to reply. It works better.

    Tag abuse (that is calling moderators needlessly) is not okay. Be smart. Be thoughtful. Remember that every last member of the forum and plugin teams is a volunteer. We’re not being paid by Automattic to do this.

    The spam review

    This is easy. Don’t reply, just add the tag modlook to the post and walk away. The forum team will delete it. If you think it may not be obvious spam, add the tag spam as well.

    The sockpuppet review

    When a person (or group of persons) makes multiple accounts with the sole intention of leaving reviews on their own plugins (or leaving poor reviews on their competitors), this is called being a Sock Puppet.

    This behavior is expressly NOT welcome on the WordPress Forums as it is spamming. But it comes in two flavors:

    1. Someone 5-star spamming their own plugin
    2. Someone 1-star spamming their competition

    Both are bad behavior. Both will get plugins removed from the repository and a stern email from us. If you’re doing this, stop right away. Contact your team and tell them ‘Don’t do this!’ Also keep in mind, asking everyone in your company to 5-star review your own plugins is gauche. I mean, really. You’re stacking the deck on purpose and that’s not beneficial to anyone.

    Again, do not reply! Add the tag modlook AND sockpuppet to the post and walk away.

    The attack/troll review

    These are the worst. When someone attacks you and the review seems like all it exists for is to make you feel terrible, you’re going to have to take a deep breath and walk away. An attack is a troll, regardless of how the original poster (OP) feels, they’ve basically been a troll. They’re writing something they know will make you mad and hurt and angry, and they’re doing it on purpose. That’s a troll. And you shouldn’t feed the trolls. You won’t win, and you’ll just make yourself look bad.

    Again, do not reply! Add the tag modlook to the post and walk away. These are usually pretty self evident after all.

    The review that should have been a support post

    This includes the sub-genre “People who submit 1-star reviews in order to emotionally blackmail you for support.”

    We all get them.

    1. Reply with a link to the support section of your plugin (or directions on how to get support, or even a note that you don’t provide free support) and remind them that next time, they should ask for help before reviewing.
    2. See if you can fix the problem, but give it no more or less priority than you would any other support request.
    3. If you can solve it, ask them to modify their review. If they go back to https://wordpress.org/support/view/plugin-reviews/PLUGINNAME and scroll to the bottom, they can edit their reviews!

    You’ll notice we’re not telling you to tag the post? Right now we can’t move a review into the support forums and vice versa, so there’s really no point. The forum moderators won’t do anything about it except say “Well, that does suck.” If we could move them, we would, but right now we technically don’t have that ability.

    The review about your premium/pro version

    If you upsell your plugin’s pro version in the free one, and someone leaves a bad review because the pro version they bought, on the basis of your free one, is bad, congratulations. The review stays. You opened the door with your upsell, encouraging them to do this, and that experience reflects on your plugin as a whole.

    If you do not upsell, and there’s no direct link between the free and pro version, or the plugin having the issue is a premium only add-on, tag it modlook and someone will come take a look.

    The review about someone else’s plugin

    This one can be fixed! Reply and let them know it’s not your plugin, it’s the other one, and then tag it modlook and then use the tag wrongplugin (all one word) to let the mods know what’s going on.

    But I really need a plugin moderator!

    Okay. So you think you’re an exception? Use the tag pluginmod and a plugin admin will come take a look. Be prepared, though, as we generally will perform a full review on your plugin and any and all guideline violations will result in your plugin being removed until you fix them. Including using too many tags.

    • Austin Passy 4:39 pm on May 3, 2016 Permalink | Log in to Reply

      Thanks Mika!

      It’s good to know that these tags exist.

    • Phil Derksen 4:48 pm on May 3, 2016 Permalink | Log in to Reply

      Very helpful Mika. Thanks.

      I also found it helpful to use the #forums channel on wordpress.slack.com. Great place to discuss how to respond to negative reviews.

    • Syed Balkhi 5:06 pm on May 3, 2016 Permalink | Log in to Reply

      Thanks Mika – this would be very helpful.

    • dudo 5:20 pm on May 3, 2016 Permalink | Log in to Reply

      Hi Mika, thank you for sharing this.

      Some people just rate 1 star because there is not a function that they want/need.

      Does the pluginmod tag can be used in a case this?

      • dudo 5:21 pm on May 3, 2016 Permalink | Log in to Reply

        Sorry for typos

      • Ipstenu (Mika Epstein) 6:09 pm on May 3, 2016 Permalink | Log in to Reply

        No, do not use pluginmod for that. That would be the “People who submit 1-star reviews in order to emotionally blackmail you for support.” folk. We won’t remove them, but you can learn from them by either improving your documentation to be more clear about what features aren’t included, or maybe add them. Either way, that was someone’s experience. They used your plugin, they wanted it to have more to be truly functional for them.

    • Chad Butler 7:13 pm on May 3, 2016 Permalink | Log in to Reply

      Awesome information as usual Mika!

      I am in general agreeance with the policies, and having been around awhile, I know these have been the general policies for quite some time.

      My personal feeling is that the weakest point of the plugin review system is brought on by misuse by a small number of users in the community (most of whom aren’t really even participants in the community). In general, the community is great – and most people post worthwhile reviews.

      But there is a portion of the community that improperly uses the review system, as you’ve already pointed out – trolls, reviews that should be support questions, etc. And then there’s they guy who I place in a separate category – the useless review: 1 star, invalid complaint, never to be heard from again.

      Would it be possible to consider adding review voting to the system at some point in the future? Something similar to Amazon where people who read reviews can answer whether they found the review helpful or not.

      I think this would allow the community to self police this since the majority of the WP community are reasonable people.

      I was tremendously glad to see the addition of requiring an actual review in addition to just the star rating (that seems so long ago…). Would this be a next logical step?

      • Ipstenu (Mika Epstein) 11:15 pm on May 9, 2016 Permalink | Log in to Reply

        It’s a possibility, but it’s low on the to-do list. It would have to come well after the plugin revamp (in progress) and the forum rebuild (getting started).

        Limited resources.

    • Sakin Shrestha 1:37 am on May 4, 2016 Permalink | Log in to Reply

      Thanks Mika for sharing.

    • dartiss 8:31 am on May 4, 2016 Permalink | Log in to Reply

      That. Is. Brilliant. Never knew these existed but glad they do!

      • dartiss 8:36 am on May 4, 2016 Permalink | Log in to Reply

        One quick question – I have a review that I’d like looking at but it’s old enough that it’s closed so I can’t add tags. Is there a way around this?

    • Brad Touesnard 12:03 pm on May 4, 2016 Permalink | Log in to Reply

      Very helpful, thanks!

    • Maruti Mohanty 6:55 am on May 5, 2016 Permalink | Log in to Reply

      Superb. Thanks a ton

    • David Anderson 12:19 pm on May 6, 2016 Permalink | Log in to Reply

      One modest improvement I’d love to see to the review system, is that only reviews from the last 2 years (or some other value) affect a plugin’s rating.

      As it is currently, for mature plugins, there’ll be plenty of reviews which – whether for better or worse – are reviews of a plugin that doesn’t really exist any more. Currently, both good and bad reviews (fair or unfair) are part of a plugin’s rating forever.

      • Max Foundry 3:02 pm on May 6, 2016 Permalink | Log in to Reply

        I agree with this David.

      • Ipstenu (Mika Epstein) 11:13 pm on May 9, 2016 Permalink | Log in to Reply

        The reviews reflect the growth and development of the plugin in both code and attitude. For now, they bear weight as a historical basis.

        Maybe one day we’ll have ‘reviews for this version’ like Apple does. That would be more fair than just age, since not all plugins change that much 🙂

        • David Anderson 10:09 am on May 13, 2016 Permalink | Log in to Reply

          Hi Mika,

          I wasn’t suggesting removing old reviews – I agree that there’s value in seeing the growth/development. The suggestion was that they stop affecting the star rating after a reasonable amount of time. This allows the star rating to better reflect the current plugin, rather than being dragged towards a historical average which doesn’t affect what users can actually download and use.


    • screamingdev 8:13 pm on May 7, 2016 Permalink | Log in to Reply

      Wow Mika Epstein. This phrase really catched me: “and any and all guideline violations will result in your plugin being removed”. Maybe we can get in touch because I am serving codebook.cc which does and will do a lot of checks for your guidelines on many plugins 😉 Please ping me via reply or Twitter @ScreamingDev. Cheers!

    • Ahmad Awais 12:28 am on June 3, 2016 Permalink | Log in to Reply

      Thanks Mika for this one. I didn’t know a few of those.

    • hiddenpearls 10:55 pm on October 18, 2016 Permalink | Log in to Reply

      Thank Mika, I was not aware of these.

  • Ipstenu (Mika Epstein) 4:47 pm on February 26, 2015 Permalink |
    Tags: , support   

    Getting Support Notifications For Your Plugin 

    When you have a plugin, it’s important that you get notified when people have support questions. We have a way for you to keep up to date on these things and have since the Great Plugin Refresh of 2012. But for those of you who missed the news or need a refresher, here we go.

    All Plugins

    We’ve always had a couple convenience views of plugin-committers and plugin-contributors, and these are still there as well. Committers are managed in on the Admin tab (i.e. people who have access to commit code via SVN), while contributors are taken from readme.txt (which is why it’s important for you to use the proper WPORG forum ID, capitalization and all).

    Example URLS:

    Your username is case sensitive. Otto42 will work, otto42 will not. Not sure what yours is? Go to https://wordpress.org/support/profile/ (yes, that works for everyone) and look at the header:

    Example of Otto's profile, his name is capitalized

    The name in the grey header is capitalized, thus he must use a capital_O_dangit.

    Otto fixed this, lowercase works, still, check your login name because I know some of you have weird spaces and stuff

    Since anyone can add you as a plugin contributor, I recommend following plugin-committer.

    The RSS URLs for this look like https://wordpress.org/support/rss/view/plugin-committer/Otto42

    At this time, we don’t have email for this.

    Per Plugin

    Every single plugin allows you to follow it by email. Go to the Support Page for your plugin, scroll down to the bottom, and you’ll see this:

    Example of Email/RSS links

    RSS and email. Done. Even if there are no posts you can register for those emails, so make that a part of your workflow.

    • Lester Chan 4:59 pm on February 26, 2015 Permalink | Log in to Reply

      Thanks for this! It is a #TIL for me!

    • Chad Butler 5:16 pm on February 26, 2015 Permalink | Log in to Reply

      Great insight! Thanks for posting it. I was never aware of the “convenience” views before.

    • danieliser 5:36 pm on February 26, 2015 Permalink | Log in to Reply

      The one thing that is missing and I would desperately love to see is a new view for unresolved issues only. Would make sorting through hundreds of tickets much easier.

    • Samuel Wood (Otto) 5:44 pm on February 26, 2015 Permalink | Log in to Reply

      You know, if you would email me before writing these things, then I could go in and fix the bugs in them before you finish writing them. 😉

      I’ve just made two important corrections to this code:

      1. It no longer uses your login name. It uses your URL slug (aka “nicename” for those who know what that means). This would be the same as in the URL of your profiles page.

      So, my profiles page is https://profiles.wordpress.org/otto42 . This means that my feed would be https://wordpress.org/support/view/plugin-committer/otto42 .

      2. Because of this, the case-sensitivity is now gone. Or rather, it will redirect you to the lowercase URL instead. No more case-sensitive BS for us, not when we can avoid it.

      The associated RSS feed should also no longer be case sensitive.

    • Paul de Wouters 8:20 am on February 27, 2015 Permalink | Log in to Reply

      We have the RSS feed trigger a Slack notification with Zapier or IFTTT, which is handy.

    • Zane Matthew 2:43 am on December 2, 2015 Permalink | Log in to Reply

      Will the support forum ever be updated to something (anything) that resembles a modern day textarea (thinking of GitHub flavored markdown here). Currently its outdated to say the least.

      Also will the UI/UX ever be updated? This also is lacking.

    • agentevolution 9:24 pm on September 19, 2016 Permalink | Log in to Reply

      The feeds appear to have stopped working as of a couple weeks ago when the forums were updated and the RSS icons removed. Will this functionality be restored?

      • James Huff 5:46 am on October 4, 2016 Permalink | Log in to Reply

        The URL structure is a bit different now that we’re finally on the current version of bbPress, running as a plugin under WordPress.

        Just like with most WordPress feeds, simply add /feed/ to the end of the URL for the plugin’s support forum now.

  • Andrew Nacin 8:51 pm on May 19, 2012 Permalink |
    Tags: , support   

    Plugin Directory Refreshed — What It Means for Developers 

    Matt just announced on the WordPress Blog — and many of you have already noticed — a number of recent changes to the plugin directory, profiles, and the support forums. Now let’s go into detail all of the individual changes, and what it means for plugin developers.

    Design refresh for plugin pages.

    We’re glad to see so many of you use the plugin headers we launched in December. Now, we’ve provided a further refresh. We’ve made authors much more prominent and with bigger Gravatars and better placement, and cleaned up the styles for the ratings, support, and compatibility sections. There’s a great before-after shot in the announcement post.

    Support is now integrated into your plugin page.

    In the past, creating new support topics for plugins has been special, and not in a particularly good way. It had this specialness by overloading the tags in the support forums to indicate that a thread was about a particular plugin. No longer. We’ve promoted plugins up a notch and given them their own area.

    So now, on your plugin pages, you’ll see a “Support” menu in the header, and you’ll see the topics for that plugin in that tab. You’ll also find a submission form at the bottom of that tab, to add new support topics specifically for your plugin. Topics about plugins made from here get a special sidebar with links to the plugin, to the plugin’s FAQ page, and to the list of Support Threads for that plugin.

    While this section looks like it’s on the Plugin’s page, it’s not really. These support threads are actually in the same place they’ve always been, in the Support forums. What you’re seeing as far as the look and feel of that view of the support forums is just some clever trickery on our part. 🙂

    Akismet, for example, will have it’s “support forums” at this URL: https://wordpress.org/support/plugin/akismet.

    How to follow support threads for your plugins.

    You may want to take advantage of this by subscribing to the RSS feed for your plugin: https://wordpress.org/support/rss/plugin/akismet. Email subscriptions are not available for these yet, but we will be adding them this week.

    For plugin authors who have been using them, the old convenience views of plugin-committers and plugin-contributors are still there as well. (Committers are managed in on the Admin tab, while contributors are taken from readme.txt.) We’ll be exposing these links in more places, but you can use them with URLs similar to the following: https://wordpress.org/support/view/plugin-committer/Otto42 https://wordpress.org/support/view/plugin-contributor/Otto42. (RSS feeds exist for these as well.)

    Support statistics are now shown to users.

    You’ll notice a new area on the plugin page sidebar showing information about how many topics there are for your plugin, and how many of them have been marked as resolved. These are handy for users to see if questions are likely to get a response.

    You have had the ability to mark plugin support threads as resolved for some time now. It’s now really easy — you can mark a thread as resolved while making a post with a simple checkbox. Note that the user who opened the thread can also mark threads as resolved and unresolved. Threads that are marked “Not a support question,” such as suggestions or feedback, are not counted toward these stats and do not need to be marked resolved.

    Statistics will be based on a rolling two-month period, based on when the thread was opened. Currently, the statistics cover threads opened in the last two weeks, and will continue to increase until it reaches two months, to allow you some time to resolve existing threads.

    Managing your forum with sticky topics.

    You can now make threads “sticky”  threads to the top of your plugin’s support forum, just like the other forums on WordPress.org. (You’ll find a link “Stick topic to this plugin’s support forum” in the sidebar.) Threads marked as sticky will show at the top of your plugin’s Support tab. (They won’t be sticky on the regular forums.) We hope you find this handy for posting FAQs or other important information about your plugin.

    A new section for developers.

    Every plugin now has a Developers tab where you can find links for browsing the code in Subversion, the development log, and development versions. Here, you can now subscribe to get an email whenever a commit is made to a plugin repository, even if it isn’t yours. (You will of course continue to receive commits for your own plugins.)

    Favoriting plugins.

    As I’m sure you’ve now seen, plugins can now be favorited by logged-in users — and have been more than 2,000 times since we soft-launched this feature earlier in the week! When you favorite a plugin, it gets added to your profile. And if you’ve also rated that plugin, your rating gets shown.

    We expect to do a lot more with all of this in the future — favorites, plugins, support, and profiles. Until next time, we hope you enjoy these changes as much as we do!

    — written by Nacin, Otto, and Scott

    • Arnan de Gans 5:15 pm on May 21, 2012 Permalink | Log in to Reply

      So i guess you’ve just rendered my own forum useless? Because i don’t want to give my users the impression i ignore support. Which your support stats will suggest if i keep ignoring the WP forums and use my own setup…
      And what’s up with this whole overhaul anyway, pulling visitors away from my plugin page by adding all these features. 🙁

      • Andrew Nacin 10:02 pm on May 21, 2012 Permalink | Log in to Reply

        The plugins directory is a hosting site, not a listing site. Your “plugin page” is https://wordpress.org/extend/plugins/your-plugin/ — while it may provide you traffic to your own site, it’s designed to be a dedicated and trusted area for users. If plugin authors don’t keep up with support topics on WordPress.org, we can no longer glean any statistics, and it is more difficult for users to identify which plugins are supported. I have been really happy to see so many users already benefit from the new tools we are giving developers. That’s a win-win to me.

        We think — and I think you probably agree — that these changes provide a far better experience for individuals looking for help. By choosing to have two support forums, you’ve already fragmented the experience for your users. (I imagine they even need to create a second account to simply provide feedback or ask a question.) Now you are experiencing this same thing for yourself.

        We may consider the ability to specify a location for support in the future, but we’d like to try this out for a while. And at least on WordPress.org, we can also guarantee your users will be greeted with the proper spelling of WordPress. 😉

        • Jon Brown 4:20 am on May 22, 2012 Permalink | Log in to Reply

          Nacin – While that seems sensible on the surface, many plugins don’t lend themselves to a single forum for support and plugin author’s who’ve built forums with multiple topics…

          For example I note that both BuddyPress and bbPress link out to their own forums…. as they should since trying to answer the myriad of support requests under a single tag would be a nightmare. I am not a plugin author (yet), but I feel all plugin authors ought to have this same option available to them to link to their own support location.

          Further there is still no good easy way (that I know of) to search a single plugin’s forum to see if a topic has been mentioned and resolved previously which is what has always rendered the forums on WordPress.org minimally useful to me.

      • Marcus 12:24 pm on May 22, 2012 Permalink | Log in to Reply

        would definitely like this. tried resolving topics myself yesterday, not really up for it 🙂

        Touching on Arnan’s comment above, I must admit I do feel the same way somewhat. Whilst I do value being able to support on WP and agree that ideally (but may not be realistic) support should be on wp.org, I don’t think statistics is a productive feature, at least as it stands right now.

        Constructive criticism below:

        Take my (the author’s) point of view and my plugin – https://wordpress.org/extend/plugins/events-manager/

        The wp support forum is usually visited at least once a day during the week. I myself go through this plugin support forum every weekday when possible, yet as it stands right now the stats are:

        15 of 84 support threads in the last three weeks have been resolved.

        However, look at the forum, and you’ll see they’ve pretty much all been answered by me or angelonwl.

        There’s a few issues here right off the bat:

        • Various questions get resolved by the opener somehow, but the topic never gets updated.
        • Some things are just unreasonable to ask from the author (i.e. how do I completely change this plugin to do what I want?), yet they count as an unresolved question.
        • Various questions aren’t support questions.

        I’m sure there’s more, but the above is already enough to, in my opinion, make this a misleading bit of information.

        As an author, I’m now expected to keep track of 3 weeks of questions, and resolve them proactively, since <50% (way less) of users will update tickets when they resolve things themselves. What's worse, contributors can't help out. I think this is unreasonable, and whilst I don't mind making do, I think this will decrease the overall experience in WP, with some immediate downfalls:

        • Good plugins will likely get misleading support stats.
        • This will likely dishearten many authors, meaning less quality plugins being made for WP.
        • I’m sure you’ll see on the forum a “hey my issue isnt’ resolved!” because it’ll become tempted to resolve every topic one answers.

        I think the most important thing for you to implement to make this work would be some sort of auto-approve or nullify tickets that the creator doesn’t keep on top of (e.g. it becomes not a support question if the author doesn’t reply to our reply in say a week). Or maybe a response rate?

        Don’t even get me started on the works/doesn’t work stats too! 😉

        • Marcus 12:30 pm on May 22, 2012 Permalink | Log in to Reply

          by “would definitely like THIS”, i meant letting contributors be able to resolve tickets

        • Marcel 9:00 am on January 12, 2013 Permalink | Log in to Reply

          +1 for including response rate statistic. Many support requests cannot be resolved because users ask for functionality that the plugin does not, or never will, offer. A state like ’10 of 12 support threads answered by plugin contributor’ would give users a better insight in plugin contributors involvement.

    • Marcus 5:30 pm on May 21, 2012 Permalink | Log in to Reply

      Great work guys! The plugin page keeps looking better and better.

      Who can ‘resolve’ topics, by that I mean committers, contributors etc. of a plugin?

      Is there a way to add users that aren’t committers/contributors so topics can be resolved?

      • Andrew Nacin 6:41 pm on May 21, 2012 Permalink | Log in to Reply

        Committers can resolve topics. At the moment, there isn’t a way to grant someone permission to resolve topics without making them a committer. It might be something we add in the future.

    • Joost de Valk 6:37 pm on May 21, 2012 Permalink | Log in to Reply

      Awesome guys, thanks for all the hard work!

    • ray 8:57 pm on May 21, 2012 Permalink | Log in to Reply

      I’m looking for a like button on this page… thanks

    • Jason Caldwell 12:51 am on May 22, 2012 Permalink | Log in to Reply

      Just wanted to say thanks for the recent changes to the plugin directory, profiles, and the support forums. Great work over there!

      I do want to make a request though. PLEASE give plugin developers the ability to use their own external support forums. That is, please make it possible (perhaps through a readme.txt file), for developers to use an external support forum system of their own.

      Many of the best plugins thrive on support, and you can’t expect us to operate our support departments within an outline set forth by WordPress.org. That is, we can’t be expected to use the support system that WordPress.org uses (we need to use what works for us).

      I, like many other plugin developers, have my own administrative system, support forum system, along with employees to assist me. As the plugin directory exists now, all support is expected to take place at WordPress.org, which is just not realistic. This is only going to result in people getting the wrong impression about plugins in your directory, because they’re looking for (and expecting) support from the forums at WordPress.org. When, in reality, the support for many plugins occurs offsite. Let’s give plugin developers the ability to direct WordPress site owners to the proper location.

    • Myatu 6:40 am on May 22, 2012 Permalink | Log in to Reply

      Couple things…

      Is there a way to see how many people have actually marked a plugin as their favorite, and optionally, who?

      Also, I’d really like to see the email subscriptions for support threads back again, the sooner the better.

      As for support itself goes, that needs some work with respect to what the plugin developer wants (better said, can do). I can understand your point about the consistency in user experience across WordPress plugins and an ability to measure plugin quality, but at the same time, what if a plugin developer would like – or already uses – a ticket system, provides phone support, use their own forum or simply use good ‘ol email, then what? There’s currently no method to integrate that with WordPress.org’s plugin listings, nor do they count toward the quality measurements.

      Something to consider perhaps, is improve the way users can vote on a plugin. More often than not, people do not vote. They install, and use it. Don’t like it, uninstall. That’s it. So, if a user uninstalls, why not ask them “Why are you uninstalling this plugin?” – plugin developers and the community could do with that sort of feedback. And voting from within the WordPress plugins page would be another option, though some care has to be taken to avoid someone using a “bot” on that (which is detectable, and could perhaps be reason for removal).

    • Mike Challis 6:14 pm on May 25, 2012 Permalink | Log in to Reply

      As a plugin author, I now have the ability to make a sticky post. Thanks.
      But after 10 minutes(or 20 or whatever) I have no ability to edit any of my posts. A sticky post is not very useful if I will not be able to edit it later if needed. Please give plugin authors the ability to edit their own posts.

    • Ipstenu 8:16 pm on May 25, 2012 Permalink | Log in to Reply

      Forum mod hat 😉

      The support forums have always been there for plugins, whether or not you used them. So this does make them more prominent, but for now if you don’t want to use them (and you certainly dont have to) I would do this:

      1) Put a link to your support location in your readme. No support at all? Just say that too 🙂
      2) Make a sticky ‘This plugin not supported on these forums.’ And inside, a link to where it is.

      No, it’s not perfect, but when the mods come through and clean up snark like ‘Bob’s a bad dev! He doesn’t help me!’ we can say ‘Well, actually, RTFM. Bob said to go to bobplugins.com instead.’

    • zorro1965 4:32 am on December 14, 2012 Permalink | Log in to Reply

      I have been so waiting for this to become a feature. So much easier then trying to keep a place where you have all these plugin details archived.

      Being able to access these in the backend after you have them marked is HUGE…!

      Now I only have a few suggestions for future.

      1. Allow the member to have ability to create their own categories for favorites to help quickly sort through what you need for a kind of site you are working on or group them for other reasons.

      2. Have a different view choices to see excerpt of description, last updated, ratings, # downloads

      Thanks very much,


compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar