Ready to get started?Download WordPress

Support Everything WordPress

Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • Jan Dembowski 10:30 am on July 18, 2014 Permalink | Log in to leave a Comment  

    Support Team Update for July 17th 

    Items discussed at the #wordpress-sfd meetup:

    Status of the handbooks (not just the Troubleshooting one)

    @samuelsidler (sams) asked about the difference between the handbooks and the organization of them. He was at WCKC and there was some confusion when trying to locate items in the handbooks.

    The Support Handbook really is for moderators and people providing support in that role. For example many of the pre-defined replies in that handbook deal with managing topics. That’s for solving forum problems. It’s written for moderators.

    The Troubleshooting Handbook in development is for people who want to assist others with WordPress problems. It’s a different audience and is definitely needed.

    This item neatly segued into the next topic of

    The Troubleshooting Handbook status

    It’s looking good and parts of the new handbook are fleshed out. It still needs content but as @Ipstenu reminded me release and iterate also applies to documentation too. Contributions don’t have to be perfect but they have to be started or things will never get done.

    That last sentence was more of a note to myself but all contributions to the handbook are welcomed. ;) If you want to contribute but don’t have access then contact me via the comments and we’ll figure something out.

    There was discussion of how and what belongs on the new handbook and the consensus was to keep it basic and inviting to new users.

    Portions of the new Troubleshooting Handbook that do a deep dive into setting up things like WAMP, LAMP, MAMP, VVV, etc. will be directed to other more technical resources. Their will be technical details there (see the break/fix examples) but the goal is to get users started and invite them to provide support.

    We all want to get more people helping and keeping it basic may get that started.

    Section topic titles

    The sections and examples were obtained from @Ipstenu‘s Break/Fix site. The titles work with the content of the article but some of them may be unclear when people are looking around. Those titles are fun though and when you get into the examples you’ll understand Mika’s gift for titles. ;)

    If you have a suggestion for modifying a title in the handbook please ping the gang here.


    I couldn’t figure out a good way to type that title with a Kirk “KHHAANNN!!!” effect.

    The WordPress 4.0 beta1 is out and please test and beat up. There are some nice enchantments (the media library made me yell “Oh that’s cool!”) and feed back is needed and bugs should be reported to the Alpha/Beta sub-forum. For a good status or progress on the beta consider subscribing to make/core.

    When you see topics in the Alpha/Beta sub-forum that have a ticket assigned and posted in that topic please mark that topic resolved. Don’t close the topic unless it becomes a run-away train or off topic in a bad way. Then the usual applies and that topic can be closed.

    The transcript for this meetup can be read at this link.

  • Jan Dembowski 10:21 am on July 16, 2014 Permalink | Log in to leave a Comment  

    Team chat agenda for week #29 

    For any items that you may want discussed in this week’s #wordpress-sfd meetup please reply in the comments below.

    • samuelsidler 12:41 pm on July 16, 2014 Permalink | Log in to Reply

      Can you add the support handbook (not troubleshooting handbook) to the agenda? Just a general checkup.

    • MacManX (James Huff) 2:44 pm on July 16, 2014 Permalink | Log in to Reply

      Sadly, I am 98% sure that I will have to miss this week due to an all-day meeting (insert witty comment here). I am holding out for the 2% that things will magically start an hour late over here, which is definitely a possibility, but will otherwise just catch up with the transcript.

    • Drew Jaynes (DrewAPicture) 4:29 pm on July 16, 2014 Permalink | Log in to Reply

      I’d like to propose that we start leveraging the Support P2 for more day-to-day use. The wp-forums list is nearly the last of the mailing lists to survive and it’s not been the greatest outlet to get input from multiple voices (back and forth email conversations make for a poor replacement for comments, for instance).

      • Ipstenu (Mika Epstein) 4:58 pm on July 16, 2014 Permalink | Log in to Reply

        That said, reporting things like “mod-watching user X” is … kind of better over there, and non-authors can bring up topics. Now… Should we bring that back here? Yes! (I really get grumpy at people who email me offlist about stuff that should be public chattered in the official places).

        We really need a better, sadly semi-private, way to talk about those things. It’s just too volatile.

        • Drew Jaynes (DrewAPicture) 6:41 pm on July 16, 2014 Permalink | Log in to Reply

          It’s more that there should be fewer general discussion topics on the list, and more on the P2. That’s what it’s for.

          • Ipstenu (Mika Epstein) 7:22 pm on July 16, 2014 Permalink | Log in to Reply

            Sure, BUT non-authors can’t post here. They can reply, so they’ll always be at the behest of people who CAN make a new post. So the barrier to get in a conversation is lower on a mailing list.

            And then of course the question is do we give access to everyone to make new posts? (I don’t feel we should)

            • MacManX (James Huff) 9:47 pm on July 16, 2014 Permalink

              do we give access to everyone to make new posts?

              [pretend this is an embedded Buzz Lightyear meme which says "Spam! Vast fields of spam!"]

  • Jerry Bates (jerrysarcastic) 12:40 am on July 15, 2014 Permalink | Log in to leave a Comment

    Troubleshooting Handbook – Progress Update 

    TL;DR The Troubleshooting Handbook is off to a great start and trucking along, but is also in need of your help. Contributors welcome!

    Why do we need a troubleshooting handbook?

    Whether energized by a local WordCamp or driven by their own desire to help others, many volunteers come to the WordPress.org Support Forums to show their WordPress love by giving back in the form of solving other’s issues.

    However, giving support is not something that we are all born with; If anything it is a learned skill. A desire to help goes a long way, but what about the other things that go into giving good support, such as:

    • Helpful tools and strategies for troubleshooting WordPress sites
    • Exercises on how to break a site (and then fix it) to gain a firsthand understanding common issues seen in support
    • Advice on effective communication styles and approaches to use when helping others
    • Tips and trick for working with the forum software (as a volunteer rather than a moderator) to make life easier.

    Currently, there is no go-to guide that collects all that information in one place for anyone starting out to benefit from; the Troubleshooting Handbook aims to fill this gap.

    Where we are now

    Work has finished on building the initial Handbook structure, as well as an import of content from Break/Fix (the inspiration for this project) which completes the first phase of this project.

    Many sections of the handbook (See spreadsheet) have pages that are in various stages of completion, and could use help to get the rest of the way. Here is a breakdown of were we could use your help.

    Section 1 – Getting started

    Ideally, this section should read like a “quick start” guide to volunteering in the forums, but it’s too disjointed to function that way currently. You can help by expanding content on the following pages:

    Section 2 – Break/fix lessons

    This section is meant to be a hands-on set of exercises on how break a site, with info on how to troubleshoot and fix it. This relates to common issues seen in WordPress support.

    Content in this section is fairly complete, owing to having been largely imported from breakfix.elftest.net but if you have an idea for an exercise you would like to contribute to expand this section or ideas on how to make the existing exercises better, let us know!

    Section 3 – Giving good support

    Most of the topics in Section 3 are without content, having only placeholder pages or article stubs. Feel free to check out any of the pages in this section to see if any interest you. They are all open to your contributions.

    Also, props to MacManX for kicking off the pre-defined replies page: http://make.wordpress.org/support/trouble/section-3-giving-good-support/pre-defined-replies/

    Giving Credit

    We have also added a credits page, which will expand over time, but for now reflects the hard work that has gotten us here so far. We’ve also including a shout-out to the original rockstar contributors to the Break/fix site this project derives it’s inspiration from. Check it out, and if you’d like to contribute, let us know in the comments.

    • samuelsidler 12:44 am on July 15, 2014 Permalink | Log in to Reply

      One of the things I noticed at the WCKC contributor day this weekend was that the predefined replies there are different than the ones in the support handbook. If we’re merging everything into the troubleshooting handbook, can we move it out of the support handbook and perhaps link to it in the support handbook?

      • MacManX (James Huff) 7:29 pm on July 15, 2014 Permalink | Log in to Reply

        The Stock Answers in the Support Handbook were geared towards Moderators and also include things only a moderator would need to post, so I wrote the predefs in the Troubleshooting Handbook to be more geared towards non-mods (like “This topic has now been closed . . .” in Stock Answers vs. “This topic will be closed . . .” in the Troubleshooting Handbook) and left the moderator-only stuff out.

        The Stock Answers section of the Support Handbook has stated the following at the top ever since the predef section went live in the Troubleshooting Handbook:

        Please note the following list includes common replies for forum moderators. Perhaps you were looking for common general support replies instead?

        Since this is designed to be used by everyone, it’s probably best to keep the moderator-only predefs out of this Troubleshooting Handbook section, but we also probably won’t make a firm decision on that until we’re done with everything.

      • Jerry Bates (jerrysarcastic) 8:04 pm on July 15, 2014 Permalink | Log in to Reply

        Regarding merging the two, that was my original suggestion (to expand the existing Support Handbook, not create a separate one) but that was not seen as a good solution by everyone. I can see the point, as it does make some sense to keep them separate (as James suggests) but I think the naming really fights this.

        Perhaps calling it the “Moderator Handbook” would help eliminate some confusion here? It’s probably hard to understand the distinction between a Support Handbook and a Troubleshooting Handbook. They both really sound like they would deal with the same thing.

  • Jan Dembowski 2:36 am on July 11, 2014 Permalink | Log in to leave a Comment  

    Support Team Update for July 10th 

    Items discussed at today’s #wordpress-sfd meetup:

    WordPress 4.0 Beta1 has dropped this morning

    Early today the release announcement for the next beta was posted. Please test and report any issues. You can install the WordPress Beta Tester plugin to do that easily.

    Forum moderators: if you see a topic in the Alpha/Beta sub-forum and a ticket has been created in trac then please mark that topic as “resolved” and post that link.

    Contributing to the Troubleshooting Handbook

    The troubleshooting handbook needs contributions and the topic was raised for how that can be accomplished. There’s not really a method to grant that access in a good way. If someone has some content they would like to contribute then perhaps posting it on their own site first may be how to get started.

    It’s easy to grant access to someone who has been collaborating with the different teams for years but granting that access to new people is delicate. It’s an idea that needs working on.

    Status of the Troubleshooting handbook

    @jerrysarcastic has generously offered to post a separate status update on that topic. ;)

    The transcript of today’s meetup can be read via this link.

  • Jan Dembowski 1:26 am on July 10, 2014 Permalink | Log in to leave a Comment  

    Team chat agenda for week #28 

    For any items that you may want discussed in this week’s #wordpress-sfd meetup please reply in the comments below.

    • Jan Dembowski 10:20 am on July 10, 2014 Permalink | Log in to Reply

      Adding this item to the agenda…

    • Jan Dembowski 11:49 am on July 10, 2014 Permalink | Log in to Reply

      Adds topic about how others can contribute to the Troubleshooting Handbook as asked about in this comment.

    • Matthew 2:28 pm on July 11, 2014 Permalink | Log in to Reply

      I would be nice if it was easier to find the Handbook.

    • Matthew 12:58 pm on July 12, 2014 Permalink | Log in to Reply

      Lately I have noticed that lots of people have been posting their support topics in the main support area instead of the individual plugin support forums. Because of this, the plugin contributor(s) can’t see the topic to help fix the persons problem.

      • Ipstenu (Mika Epstein) 3:54 pm on July 13, 2014 Permalink | Log in to Reply

        This has always been a problem.

        Short of hiring someone to sit by people when they post and yell “WROOOOOONNNNG” I really can’t think of anything more to to about it.

        When you find them, tag the post with the plugin slug and reply saying “I’ve tagged this for the developer…” GOOD theme and plugin devs suck up the spam and watch those tags :)

  • Jan Dembowski 2:01 am on July 4, 2014 Permalink | Log in to leave a Comment  

    Support Team Update for July 3rd 

    Items discussed at today’s #wordpress-sfd meetup:

    Domain trademark violations

    This comes up from time to time in the forums. Someone (well meaning I am sure) uses WordPress in their domain name and posts that link in the forums or in their forum profile. When that happens they usually get a reply such as “Hey, could you please stop using that domain name? Here’s some links explaining it better.”

    Volunteer support is not trademark police and I’ve not seen a case where someone didn’t correct that when pointed out. Support volunteers are there to help people and not really get into topics like that. But if necessary this link can be used to report that to the WordPress foundation.


    Again it’s not that support is to tell people right and wrong but if an instance needs to be escalated then that link should work.

    Troubleshooting Handbook status

    The new Troubleshooting Handbook is making progress and both @jerrysarcastic and @podz (Markr) have been working on it. It still needs contributors so please take some time to look it over and contribute where you can.


    Section 3 can use some attention and would really benefit from some content.

    For examples of good (and not so good) support it was discussed to possibly take topics from the forum and modify/anonymize the text so that the examples remain just examples. It’s important that the handbook doesn’t seem to call out people for their behaviour. It’s a handbook after all and everyone should benefit from the verbiage.

    Expiring topics earlier than 1 year?

    When a topic is a year old it gets expired meaning no one can reply to those topics anymore. Moderators can still edit the posts in the topic but not reply either. This morning on the wp-forums list the idea came up about the possibility of reducing that time.

    Expiring topics around 3 months was well recieved in IRC and that became 6 months after some talking it out. I suggested sending an email to the list asking Otto about it. His reply on the list touched on something important: what is the best experience for the users?

    Topics are expired because after a time they’re no longer useful. That time is currently 1 year but more or less could be a tough thing to nail down. It’s something that will continue to be discussed on the wp-forums list.

    This really isn’t a critical item (it only really came up today) and I think the 1 year age out will stay. Moderators can still close topics that have gone off the rails and are no longer productive.

    The transcript of today’s #wordpress-sfd meetup can be read at this link

  • Jan Dembowski 9:34 am on July 2, 2014 Permalink | Log in to leave a Comment  

    Team chat agenda for week #27 

    For any items that you may want discussed in this week’s #wordpress-sfd meetup please reply in the comments below.

  • Jan Dembowski 1:33 am on June 27, 2014 Permalink | Log in to leave a Comment  

    Support Team Update for June 26th 

    Items discussed at today’s #wordpress-sfd meetup.

    IRC escalation

    @Clorith brought up the point that sometimes the #wordpress IRC channel gets beset by spambots. If someone is around who can deal with that then it’s not a problem. When the channel IRC mods are not available it can become distracting.

    Except for pinging the wp-forums list or sending an email to IRC mods then there’s really not much to be done at this time. Forum moderators and IRC members with OP privileges are two separate groups. Using email is not ideal but a 4 hour later response time is better than no response at all.

    Cleaning up the no replies link?

    @jnhghy brought up the idea of making changes to the forum no replies view.

    The problem with filtering that view is that those old replies from way, way, way back still have no replies to them. The conversation talked about the difference between a topic that is marked as [closed] and an unmarked topic that is more than a year old. Those topics are expired and cannot take anymore replies. They are closed too.

    It may be possible to trim that view (plugin topics was recently removed from that view) but for now old topics will remain.

    The Troubleshooting Handbook Status

    @jerrysarcastic wasn’t able to attend today (and neither was I for that matter) but the new handbook was discussed.

    The Support Handbook is for moderators and “crazy people like us”. But for regular users who wish to jump into support the Troubleshooting Handbook is meant to be the place to go. Eventually when people want to get started they will be directed to this new handbook.

    There was some discussion regarding what kind of uploads are permitted (for example zips are not allowed) and what the current state is.

    Content is still needed and anyone who wishes to contribute will be encouraged. ;)

    The transcript of today’s meetup can be read at this link.

  • Jan Dembowski 12:55 am on June 25, 2014 Permalink | Log in to leave a Comment  

    Team chat agenda for week #26 

    For any items that you may want discussed in this week’s #wordpress-sfd meetup please reply in the comments below.


  • Jan Dembowski 1:37 am on June 20, 2014 Permalink | Log in to leave a Comment  

    Support Team Update for June 19th 

    I was unable to attend today’s #wordpress-sfd meetup but there was good representation and a lot was covered. Mika wrote a really good amount of material and sent it to the wp-forums list. I also wanted to thank @Ipstenu for driving the meetup but it’s really more than that.

    Mika? You’re fantastic and inspiring. Some days volunteer work (any work) can be a drag so if that happens just read this: Thank you for everything you do. It’s really appreciated. ;)

    The Troubleshooting Handbook

    Much of the Break/Fix site is now imported into the Troubleshooting Hanbdbook


    This is a work in progress please feel free to volunteer content. This remains a great idea.

    Sock Puppetry

    Sock Puppetry is when one person (or company) makes duplicate accounts to either troll others or bump their own plugin or theme. It’s not cool and those new accounts get blocked when found and their posts deleted.

    When a moderator comes across that and it’s related to a plugin author then please notify the plugin team at plugin [at] wordpress.org with the details. If a theme author is doing that then I think you can ping the theme reviewers list.

    I don’t think I’ve come across a theme author engaging in sock puppetry myself. You can always notify the wp-forums list if you’re not sure.

    How to Pick Moderators and some Handbook Cleanup

    Mika wrote a good and lengthy email to the wp-forums list and I’m going to include that here in today’s update.

    Since this DOES get asked now and then, we banged around an idea to not so much formalize the process, but explain what’s going on.

    That said, before I get to the new thing I’d like to add, I’ve fixed the structure of the handbook so we have forum moderation under the ‘Contributing to the WP Forums’ section. I also cleaned up a lot of the stuff that was in the “I …” format, since that was from my emails ages ago, and needed updating. I also consolidated some pages and added a couple new ones.





    Added: Rule 6: You’re here to help people, not preach about right and wrong.


    Added: We have guidelines, not rules, for a reason: guidelines should be followed, rules <em>must</em> be followed. Never let the literalness of the guideline override your common sense. After all, we’re here to help people, not build a wall to keep people out.


    Added a reminder: We don’t like to call it bozing in public (even on this list) becuase it’s 99.99999% of the time taken the worst way possible. Try to call it b-tagging, and never ever EVER tell them they were bozo’d, tell them their account was set to require moderator approval on posts.



    Forum Moderator:

    If you’re interested in being a forum moderator, that’s awesome! We don’t have a formalized process for getting new mods, but here’s how we handle it:

    We’re a team. We pick people we feel will work well with the current members, uphold the high level of support and friendliness of the forums, contribute with no adverse ulterior motive, and be a polite member of the forums in the face of raging anger.

    What do we mean by ‘adverse ulterior motive’? It’s actually pretty simple.

    • Contributing to the forums to help people while learning more about WordPress is good.
    • Posting replies only to get people to use your plugin/service/product is NOT good.
    • Using your moderator powers to determine a poster is hosted by your company, and asking them to contact you/your company is good.
    • Using your moderator powers to get a poster’s email address to contact THEM about your product/service is NOT good.
    • Asking to be a mod because you’ve been tagging posts for spam cleanup, email/personal information/passwords removal, and make sticky posts for major issues is good.
    • Asking to be a mod because it will make you contribute more is NOT good.

    If you can’t tell, the idea here is to do good for the sake of doing good. It’s not that we’re looking for people who have no higher aspirations, it’s that the aspiration we’re looking for is very self evident when it exists. And certainly you don’t have to be altruistic about WordPress to be a moderator. Some of us are encouraged by our companies to volunteer, in order to help the community. But that’s really the point. We’re looking for people whose goal matches ours: Make WordPress better for everyone.

    Not being asked doesn’t mean you lack those qualities, however, nor does it mean we feel you’re a bad person. There is no magical combination of actions to be picked as a mod, and many people, even those who ask about being one, are surprised the day that they’re asked if they’d like to be one. The reason is that the absolute best moderators are the ones who are just going to do what they do, regardless of formal recognition. They see something that needs doing, and they do it.

    And THAT is what we look for.

    Mika A Epstein (aka Ipstenu)

    The transcript of today’s #wordpress-sfd meetup can be read at this link.

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