Support Team Update for November 20th

Items discussed at the the Support meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on will help you find options in your area.:

Social Support

Should we make an effort to offer support on Twitter, Facebook, and LinkedIn?

The answer was pretty much an emphatic no even before the meetup. We’ve got the forums and IRC covered, which is where folks should be going for support.

LinkedIn is pretty well staffed by its own talented volunteers, Facebook is . . . Facebook, and Twitter presents the challenge of trying to cram an answer into 140 characters (which typically just results in directing folks to the forums anyway).

It sounds like @matt owns the Twitter account, so @macmanx reached out to him via SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at to ask if we could change the Twitter description to:

Updates and other fun stuff related to (that’s the self-hosted version). For support:

Update: The change is now live!

We would love to do the same for Facebook, but Facebook has recently chosen to limit Pages to only one website link.

There is really no need to do the same for LinkedIn since it’s a slightly different community geared more towards job posting and promotions, and less towards support.


We’d love to have custom shirts, but have agreed that it’s really super-low priority right now.

More Welcoming Handbook Welcome

The Support Handbook needs a more welcoming welcome. Since it can’t get much worse than it actually is, @macmanx will take a swing at it some time this week.

WordPress 4.0.1 and Family

The meetup ended with the release of WordPresses 4.0.1, 3.9.3, 3.8.5, and 3.7.5.

Changed Files:
Specific Changes:

At the time of this update, we have found one known issue worth highlighting:

The transcript of this meeting can be read at this Slack archive URL.