April 20th Support Team Meeting Summary

Announcements

  • WordPress 4.7.4 has been released!
  • A quick reminder (because topics are beginning to appear) that the new Plugins search engine returns “the most relevant results based on a combination of many factors including version compatibility, recency, and popularity, in conjunction with text relevancy.”
  • Registration for WordCamp EU 2017‘s Contributor Day is open. Please register if you are attending WCEU this year and are available on June 15.

WordPress 4.7.4

We have nothing new to add to the known issues for 4.7 this week, but we did remove “MP3 uploads are split into two files: an MP3 with no cover image, and a corrupt JPG.” which was fixed in 4.7.4.

Checkin with International Support Liaisons

Attendance

@macmanx @bethannon1 @vishalmukadam @karpstrucking @erricgunawan @bcworkz @lasacco @clorith @vitormadeira @bdbrown @numeeja @sergeybiryukov @t-p @zoonini @glorialchemica @geoffreyshilling @jdembowski @francescodicandia @keesiemeijer @cristianozanca @jcastaneda @hardeepasrani @kidsguide @lukecavanagh attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat

April 13th Support Team Meeting Summary

Announcements

WordPress 4.7.3

We have nothing new to add to the known issues for 4.7 this week.

Moderator Queue Actions are now Explicit (aka, no more announcing)

We have exciting news by way of Meta ticket 2418! Spam/Unspam, Approve/Unapprove, and Archive/Unarchive (and the others) are now explicit actions, not toggles! 🎉

Previously, If Moderator1 and Moderator2 were to mark the same item as Spam simultaneously, it would ultimately result in the item being marked as Not Spam. (the first action would be Spam, but the second action would really be Unspam, because toggles) ☹️

Now, if Moderator1 and Moderator2 were to mark the same item as Spam simultaneously, it will still be marked as Spam! (because it’s an action and not a toggle, both Moderators are marking it as Spam, regardless of order) 👍

This means that there’s no more need to report when you’re checking the queues in Slack. You can run the Also Viewing script to avoid needlessly overlapping, but even if you aren’t, there’s no harm in two people operating in the same queue at the same time. 👏

🎊 Thanks @sergeybiryukov ! 🎊

Checkin with International Support Liaisons

Attendance

@macmanx @erricgunawan @bcworkz @pmfonseca @zodiac1978 @kidsguide @geoffreyshilling @cristianozanca @bdbrown @numeeja @lasacco @alchymyth @keesiemeijer @glorialchemica @lukecavanagh @contentiskey @kmessinger @sergeybiryukov @photoironic @sterndata @hardeepasrani @hideokamoto @tnash @jcastaneda attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat

April 6th Support Team Meeting Summary

Announcements

WordPress 4.7.3

We have nothing new to add to the known issues for 4.7 this week.

Checkin with International Support Liaisons

Attendance

@macmanx @bcworkz @pmfonseca @erricgunawan @bdbrown @t-p @kmessinger @sterndata @numeeja @danhgilmore @sergeybiryukov @geost @zoonini @lukecavanagh @hardeepasrani @contentiskey attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat

March 30th Support Team Meeting Summary

Announcements

WordPress 4.7.3

We have nothing new to add to the known issues for 4.7 this week.

Supporting Themes from Jetpack

There was some confusion around how to support the themes installed by Jetpack. Quoting Support Team member and Automattic Theme Whisperer @zoonini:

1. vast majority of those themes already in the .org repo
2. small number of themes either waiting in the review queue or not yet submitted (due to one theme in queue rule)
3. small number of themes forked but not different enough to submit back to .org

if you see any in categories #2 or #3, please just add “wpcom-theme” tag and I or one of my colleagues will be happy to reply if it’s not something you’d like to handle

And, of course, if it’s a theme covered by category #1, just direct them to the specific theme’s support forum on WordPress.org, just like any other theme in the official directory.

Theme Installation Confusion

Speaking of themes, we’re noticing an increase in folks mistaking the theme directory’s Upload Your Theme section for a way to install themes on their own site. For now, here’s a predef you can try:

https://wordpress.org/themes/getting-started/ is for developers to share the themes they make with the entire WordPress community.

To install themes on your site, follow this guide: https://codex.wordpress.org/Using_Themes#Adding_New_Themes

Additionally, please DM @jcastaneda in Slack with links to any reports of the confusion so the Theme Review Team can find the best way to improve the situation.

Meeting Time

We held the final courtesy “Is this still what we want?” vote regarding the decision to change the meeting time from the March 9 meeting. Holding the meeting at 16:00 UTC continued to receive majority support, so the meeting time will continue as-is, meaning that the next meeting will be Thursday, April 6, 2017, 16:00 UTC.

This was the final vote, so the meeting time will not be changed again until most of us switch back to Standard Time, or some other situation arises that would necessitate changing the meeting’s time.

Checkin with International Support Liaisons

Attendance

@macmanx @bcworkz @clorith @geost @jdembowski @t-p @bdbrown @kmessinger @zoonini @alchymyth @sterndata @contentiskey @sergeybiryukov @sage-chara @jcastaneda @lukecavanagh @bethannon1 @georgestephanis @kenshino @stephencottontail @abletec @fierevere @imazed @hardeepasrani @otto42 attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat

March 23rd Support Team Meeting Summary

Announcements

  • Please make sure that you’re using the latest Also Viewing script, released about a month ago.
  • We don’t know how much longer the Codex will be around, so please link to the new Forum Welcome in our Handbook for all appropriate instances, rather than the old one on the Codex.

WordPress 4.7.3

We added an issue where the “Select Files” button will not work under some Chrome configurations to the known issues for 4.7 this week.

Per-Forum Moderators

An enhancement has been released which will allow us to promote moderators of specific forum sections only. Admins can edit a forum section itself, like Developing WordPress, and enter usernames to promote for just that forum section as a comma-separated list in the new “Forum Moderators” box.

What about specific Plugin and Theme forums? Plugin and Theme authors and contributors currently have the power to mark threads as resolved and pin sticky topics within their own support forum. A ticket has been filed to also give them the power to Close and Archive (delete) topics.

Checkin with International Support Liaisons

  • The Russian and Portuguese support communities are doing well.
  • The Italian support community has adjusted its categories to be more in line with other support communities on the new forum theme.

Attendance

@macmanx @erricgunawan @vishalmukadam @pmfonseca @bcworkz @lasacco @bdbrown @kidsguide @kmessinger @t-p @cristianozanca @numeeja @fierevere @geoffreyshilling @zoonini @karpstrucking @sterndata @bethannon1 @stobrendo @lukecavanagh @jdembowski @sergeybiryukov @ramthas @geost @hardeepasrani @stephencottontail @ocean90 @tnash @jcastaneda attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat

March 16th Support Team Meeting Summary

Announcements

  • Please make sure that you’re using the latest Also Viewing script, released about a month ago.
  • We don’t know how much longer the Codex will be around, so please link to the new Forum Welcome in our Handbook for all appropriate instances, rather than the old one on the Codex.

WordPress 4.7.3

We have nothing new to add to the known issues for 4.7 this week.

Meeting Time

We held a courtesy “Is this still what we want?” vote regarding the decision to change the meeting time from last week. Holding the meeting at 16:00 UTC continued to receive majority support, so the meeting time will continue as-is, meaning that the next meeting will be Thursday, March 23, 2017, 16:00 UTC.

Another large portion of contributors will experience their Daylight Saving Time shift on March 26, so we’ll hold one more courtesy vote during the March 30 meeting.

Checkin with International Support Liaisons

Attendance

@macmanx @abletec @samuelsidler @bcworkz @jmdodd @voldemortensen @zodiac1978 @kidsguide @kmessinger @geoffreyshilling @geost @bdbrown @t-p @cristianozanca @numeeja @zoonini @keesiemeijer @liamdempsey @ipstenu @lasacco @lukecavanagh @jdembowski @alchymyth @sterndata @pmfonseca @hardeepasrani @hideokamoto @jcastaneda attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat

March 9th Support Team Meeting Summary

Announcements

  • Please make sure that you have upgraded to WordPress 4.7.3.
  • Please make sure that you’re using the latest Also Viewing script, released about a month ago (and most recently updated last week).
  • We don’t know how much longer the Codex will be around, so please link to the new Forum Welcome in our Handbook for all appropriate instances, rather than the old one on the Codex.
  • Please be aware of some proposals for deprecating support for certain browser versions.

WordPress 4.7.3

An issue affecting certain file uploads was fixed in WordPress 4.7.3, so it has been removed from the known issues for 4.7, but we have added an issue where MP3 uploads are split into two files.

Meeting Time Change

Daylight Savings Time will be arrive for many of our contributors on March 12 and for most of the rest of our contributors on March 26 (with a few lucky contributors who never have to observe Daylight Savings Time).

We held a vote on whether we should keep the meeting at 17:00 UTC or move it to 16:00 UTC, and moving the meeting to 16:00 UTC won with the most up-votes and absolutely no down-votes, so we’ll be moving the meeting to 16:00 UTC effective next week.

This means that the next meeting will be Thursday, March 16, 2017, 16:00 UTC, which is the really the same time for anyone who will have their Daylight Savings Time change on March 12, and only an hour earlier for the rest who won’t change until March 26 (unless you’re one of the lucky ones who doesn’t have to observe Daylight Savings Time).

Because time zones are complicated, we’ll hold a “Is this still what we want?” vote during the next meeting and again during the March 30 meeting.

Checkin with International Support Liaisons

Attendance

@macmanx @clorith @bcworkz @otto42 @jmdodd @zodiac1978 @katzwebdesign @bdbrown @t-p @liamdempsey @bethannon1 @geoffreyshilling @sage-chara @kmessinger @hardeepasrani @numeeja @zoonini @sergeybiryukov @kidsguide @abletec @sterndata @stephencottontail @logankipp @lukecavanagh @jdembowski @lasacco @samuelsidler @pmfonseca @jcastaneda attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat

March 2nd Support Team Meeting Summary

Announcement

  • Please make sure that you’re using the latest Also Viewing script, released about a month ago (and most recently updated yesterday).

WordPress 4.7.2

We have nothing new to add to the known issues for 4.7 this week.

2017 Community Summit

The Support Team’s invitations to the 2017 Community Summit, and topics which we would like to participate in (based on those that passed with a majority vote), have been officially proposed.

Handling Non-automated Spam from Flagged Users

If you encounter automated spam from bots (or really terrible users) that you intend to Block, please do mark it as Spam, that will never change.

However, if you encounter spam from a user that is most likely human who you intend to Flag (or who has already been Flagged), please simply Archive it. Spam is emptied regularly, which means we lose it as a historical record quite often, but the Archive is forever and handy to refer to for questions like “I wonder how bad that spam from this possibly reformed user was?”

Linking to the Forum Welcome/Guidelines/Rules

We don’t know how much longer the Codex will be around, so please link to the new Forum Welcome in our Handbook for all appropriate instances, rather than the old one on the Codex.

Checkin with International Support Liaisons

Attendance

@macmanx @samuelsidler @fierevere @sergeybiryukov @bcworkz @clorith @zodiac1978 @kidsguide @kmessinger @t-p @bdbrown @cristianozanca @hardeepasrani @voldemortensen @wido @abletec @zoonini @sterndata @otto42 @jdembowski @stephencottontail @bethannon1 @imazed @tnash @ipstenu @johnjamesjacoby attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat

February 23rd Support Team Meeting Summary

Announcements

  • The Theme Review Team is looking for FAQ suggestions.
  • Please make sure that you’re using the latest Also Viewing script, released about a month ago (and updated a few days ago to make the banner sticky).

WordPress 4.7.2

We have nothing new to add to the known issues for 4.7 this week.

2017 Community Summit

The next Community Summit has been announced, and we have been collecting support-related topics and issues for discussion in the comments of this post. We will continue to collect proposals for one more week, so please leave a proposal soon if you have one.

Additionally, if you did not attend the meeting today, but would be able to be in Paris on June 13 and 14 as a part of the Support Team, please DM @macmanx in Slack. (There will likely be a chance for scholarships and sponsorships, but please assume for now that you will need to pay for your own travel and lodging expenses. If you would like to attend, but finances are a problem, please feel free to let me know know and we’ll see what we can do.)

And last, but certainly not least, a big thanks to @clorith and @bethannon1 for offering to help with organizing the event!

Checkin with International Support Liaisons

Attendance

@macmanx @bcworkz @ipstenu @bdbrown @cristianozanca @kmessinger @numeeja @hardeepasrani @lasacco @kidsguide @jdembowski @sterndata @wido @keesiemeijer @lukecavanagh @zoonini @bethannon1 @t-p @stephencottontail @sergeybiryukov @logankipp @pmfonseca @clorith @fierevere attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat

February 16th Support Team Meeting Summary

Announcements

WordPress 4.7.2

We have nothing new to add to the known issues for 4.7 this week.

Checkin with International Support Liaisons

Attendance

@macmanx @t-p @numeeja @jcastaneda @kmessinger @hardeepasrani @lukecavanagh @jdembowski @sterndata @bdbrown @ipstenu @cristianozanca @kidsguide @prathameshp @lasacco @zoonini @stephencottontail @zodiac1978 @imazed @samuelsidler @geoffreyshilling @sergeybiryukov @pmfonseca attended

Read the meeting transcript in the Slack archives. (A Slack account is required)

#weekly-chat