December 8th Support Team Meeting Summary

Announcements

WordPress 4.7

Beyond the currently reported Genesis and W3 Total Cache issues, we have no trending and reproducible bugs to add to the known issues for 4.7.

To be clear, there are currently 31 reported bugs on track to be fixed in 4.7.1, but these haven’t been observed with enough consistency in the support forums to warrant listing in the known issues topic. To avoid cluttering the list with items that may only affect a handful of users, we list trending and reproducible issues only. You can see the known issues for 4.6 as an example of this.

Earlier today, there was a bug scrub focussing on all non-Customizer bugs, followed by a bug scrub of Customizer bugs tomorrow.

Badges

Automation of badges is still underway based on the criteria we all voted on for on August 18.

Until then, support liaisons can add them to the Google Sheet they have access to. Please ping @macmanx or @kenshino if you have any questions about that.

WCUS 2016 Recap

Contributor Day at WordCamp US 2016 was a great success for us! We have 5 new contributors, and one even wants to help out in IRC!

We also continued our efforts to be one of the most enjoyable teams at Contributor Day. 🙂

New Forum Theme

The new forum theme (see the November 10th meeting summary for details) will most likely be launching in a few weeks on the English forums. Once Meta Team is sure that everything is solid, it will then be launched on the not-English forums.

Please continue to test the new theme and file bug reports for now, following instructions in the linked to November 10th meeting summary.

Checkin with International Support Liaisons

  • The Italian and Russian support communities are doing well.
  • The Japanese support community is definitely looking forward to automated badges.

Attendance

@macmanx @otto42 @clorith @bethannon1 @jmdodd @lasacco @bcworkz @ipstenu @t-p @cristianozanca @numeeja @geoffreyshilling @hempsworth @jdembowski @christinedonovan @bdbrown @kenshino @heytheo @imazed @keesiemeijer @fierevere @sergeybiryukov @wido @sterndata @zoonini @hideokamoto @hardeepasrani @pixolin @liamdempsey @perezbox @samuelsidler @lukecavanagh attended.

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

#weekly-chat

Agenda for December 8th Support Meeting

  • General Announcements
  • WordPress 4.7
  • WordCamp 2016 Contributor Day Recap
  • Checkin with International Support Liaisons

For any other items to discuss please add them in the comments below, or bring them up in the meeting.

The meeting will be Thursday, December 8, 2016, 17:00 UTC in #forums on Slack. (a Slack account is required)

4.7 OMGWTFBBQ Draft Post

Here’s a rough draft of the 4.7 OMGWTFBBQ thread.

Thread Title: READ THIS FIRST WordPress 4.7 Master List

Hooray! FIX TITLE AND URL is here! But OMGWTFBBQ!? WordPress 4.7 broke everything?

Don’t Panic!

Before you go any further, make sure you’ve updated your plugins and themes to the latest versions, clear your browser’s cache and cookies and re-log into your WordPress dashboard.

Still having problems? Okay, read on!

This thread contains the known issues with plugins and themes found in 4.7. Please read this WHOLE topic and come back and check again later, as it will be updated.

Remember to be calm, be patient, and be respectful. Volunteers are out here to try and help you, but we need your help too. All of the normal forum rules still apply. Remember, you are just as important as everyone else.

If your post doesn’t show up right away, please be patient. With the higher than normal post volume, more posts get flagged as spam by our auto-spam tool. We’re working hard to keep the queue clear, but making multiple posts slows us down, as we have to go back and check if you already posted. Post once.

  • Do use proper capitalization in post titles and body. Punctuate your sentence properly and humanely, it helps us read.
  • Do use descriptive subject lines. “All permalinks broken since 4.6” is much better than “Augh! Help ASAP! This version is terrible!”
  • Do describe the problem clearly. Explain what you’re seeing, include error messages and link to screenshots if needed. Linking to your site, if the problem is on the front-end, also helps.
  • Do be patient. We know it sucks to be down, but posting multiple times doesn’t get you help any faster.
  • Do make your own topic unless you are using the exact same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme and configurations as the original poster. You may find it weird, but it will be easier for us to help you specifically if you have your own topic.
  • Do mark your topic as resolved when it’s fixed so we know not to come looking there anymore.
  • Do remember you’re not alone.

Also keep in mind that not liking the direction of WordPress’s design is a not a bug. If you don’t like a feature, please don’t make a series of posts complaining about it. Look and see if someone already did, and post there, or consider joining the process earlier on. What you’re seeing today is the result of thousands of hours of work and testing, and unless something is outright broken, it’s highly unlikely to be changed.

Again, before you post:

Make sure you’ve read this entire thread and FIX URL New Features in 4.7 Codex Article.

Go to your own install’s about page – `example.com/wp-admin/about.php` – to see what’s new.

And then make sure you’ve tried…

  • Flushing any caching plugins you might be running, as well as server and/or browser caches. Not just your browser, but any op cache or content network cache as well such as Cloudflare. That will solve many weird JavaScript issues.
  • If your host provider has a “Purge Varnish” option or if you can ask your provider to flush memcache on your server.
  • Deactivating all plugins (yes, all) to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s). If you can’t get into your admin dashboard, try resetting the plugins folder by SFTP/FTP or PhpMyAdmin (read “How to deactivate all plugins when you can’t log in to wp-admin” if you need help). Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to `mu-plugins-old`
  • Switching to the Twenty Seventeen theme to rule out any theme-specific problems. If you can’t log in to change themes, you can remove the theme folders via SFTP/FTP so the only one is `twentyseventeen`. That will force your site to use it.
  • Manually upgrading. When all else fails, download a fresh copy of the latest.zip file of 4.7 (top right on this page) to your computer, and use that to copy up. You may need to delete the wp-admin and wp-includes folders on your server (NOTE: do not delete the `wp-content` directory or your `wp-config.php` file) Read the Manual Update directions first.

Next section, posted as a reply:

Core Changes

In addition to new features highlighted in FIX URL the release post:

This Crazy Change: To be filled in later based on the release post.

This Other Crazy Change: Will there be more? Who knows?!

Next section, posted as a reply:

Not a Bug

I can’t add a video header to my theme: While WordPress 4.7 does introduce video headers, the theme you’re using must be built to support video headers. Contact your theme’s developer for details.

I can’t see the other Customizer features detailed in the release post: As with the video headers, the theme you’re using must be built to support these. Contact your theme’s developer for details.

I don’t see PDF previews: Although PDF previews are now a posibility, any already uploaded PDFs will not display thumbnails, and your server will have to be configured t osupport them (This means you need Imagik, ImageMagick and Ghostscript for thumbnails to be generated for you).

Alternative texts are no longer created automatically for my images: The alternative text auto-generated by WordPress was not good for accessibility, this is why we changed this to instead have a blank value (defining it as merely a visual element and not an important part) by default. This means we leave it to the poster to define the appropriate text for assisstive technologies to use.

The language of wp-admin changed: With 4.7, we’ve introduced the ability to change your personal languages preference for the admin areas. You may have saved your profile with a new language chosen, or the default language was not what you expected it to be.

Feature buttons are missing from the editor: To encourage proper use of HTML elements, and to reduce the misuse of confusing elements (such as underlines for example), the toolbars have been rearranged (and some options removed, although their keyboard shortcuts will continue to work as expected), and may be found by extending the toolbar at the top to show both lines of options.

Next section, posted as a reply:

Known Issues

  • There are no known consistent or reproducible known issues in the final release of WordPress 4.7 at this time.

Next section, posted as a reply:

Plugin and theme issues

  • There are no known consistent or reproducible plugin or theme issues in the final release of WordPress 4.7 at this time.

The final release of WordPress 4.7 is scheduled for December 6, 2016, so the content of this post may continue to change until then. Please use the comments below to suggest any alterations.

WCUS Support Breakfast

(Apologies to those of you not at WordCamp US this year, but this is the most efficient way to get the word out.)

If you’re a Support Contributor or Support Team Member at WordCamp US 2016, we’d love to get together for a breakfast Sunday at 8 AM at the Down Home Diner:

12 Filbert St
Philadelphia PA 19107

It’s a 5 minute walk from the convention center, which will be great for Support Team members, who should try to be at the convention center around 9 AM to meet eager new contributors before Contributor Day officially kicks off. The location also looks big enough to fit us.

One extra note, the breakfast won’t be a provided/free meal (sorry!), and if you can’t make it to breakfast, that’s fine, we all understand.

No need to RSVP, just stop by the Down Home Diner Sunday at 8 AM if you want to have some breakfast with your fellow Support friends. 🙂

November 24th Support Office Hour

Since the majority of our US-based Support Contributors will be celebrating a traditionally full-day holiday, we won’t be holding a formal meeting on November 24.

There is no agenda, and attendance will not be recorded, but if you want to discuss anything, please feel free to stop by #forums in Slack on Thursday, November 24, 2016, 17:00 UTC for an informal office hour. (a Slack account is required)

There will be no meeting the following Thursday, December 1, due to WordCamp US 2016 travel (any sort of WCUS-related coordination will be handled throughout the event in #forums on Slack).

November 17th Support Team Meeting Summary

Announcements

  • Please take the official WordPress 2016 Survey.
  • Please continue to test the new forum theme. (see previous meeting summaries for details)
  • Thursday next week will be a holiday for the US-based contributors who typically represent a majority of our attendance, but the Thursday after that is travel to WCUS for most who are attending. So, there will be a short office-hour/open-floor type meeting on November 24 (attendance will not be recorded, enjoy your holiday), and no meeting on December 1.

WordPress 4.7 Beta 4

The fourth WordPress 4.7 Beta is here, so please start testing.

More bug reports during the beta means less forum threads after the final release.

Support in Other Languages

Please remember that there are no rules against asking a question in a different language than what the specific forum represents (for example, asking a question in German on the English support forums).

If your preferred translator service makes a mess out of their support request, it’s perfectly fine to politely suggest that they ask in the forum which represents their language, but don’t close the topic for language alone.

WCUS 2016 Plans

Support Contributors at WordCamp US 2016 will gather for breakfast, either dine-in or take-out, at either 7 AM or 8 AM (depending on location) on Sunday (the morning of Contributor Day). Support Team members should plan on being at Contributor Day by 9 AM to greet new contributors, which is why the breakfast time depends on the breakfast location.

Final decisions will be solidified as we get closer to the actual day, but it will definitely be breakfast on Sunday. Look for an announcement in #forums on Slack no later than Saturday evening.

Plans for Contributor Day will generally involve improving the handbook and helping new contributors find their voice in the support forums. Final decisions will be solidified at the time itself, as they mostly depend on how many new contributors are interested in joining us.

Checkin with International Support Liaisons

  • The Portugues and Russian support communities are doing well.
  • The Spanish support community is getting organized to ensure that spam is cleared and threads are answered more frequently.

Attendance

@macmanx @clorith @jmdodd @bcworkz @nickduncan @denisco @sergeybiryukov @josearcos @pmfonseca @vitormadeira @numeeja @geoffreyshilling @ipstenu @cristianozanca @sterndata @fierevere @t-p @zoonini @bethannon1 @kidsguide @hardeepasrani @alchymyth @lukecavanagh @kafleg @jdembowski @jcastaneda @danhgilmore @kenshino attended.

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

#weekly-chat

Agenda for November 17th Support Meeting

  • General Announcements
  • Testing WordPress 4.7 Beta 4
  • Checkin with International Support Liaisons
  • WordCamp US 2016 Support Contributor Plans

For any other items to discuss please add them in the comments below, or bring them up in the meeting.

The meeting will be Thursday, November 17, 2016, 17:00 UTC in #forums on Slack. (a Slack account is required)

November 10th Support Team Meeting Summary

Announcement

WordPress 4.7 Beta 2

The second WordPress 4.7 Beta is here, so please start testing.

If you don’t have any room on your own server or hosting account, there are some great guides for setting up a local server environment.

More bug reports during the beta means less forum threads after the final release.

New Forum Theme

Please continue to test the forum redesign!

To start the fun, simply visit https://wordpress.org/support/?new-theme=1

It works off of a cookie, so if you need to switch back, simply visit https://wordpress.org/support/?new-theme=0

If you find anything broken, please open a ticket in Meta Trac (after searching first, of course) under the Support Forums component, and prepend the ticket’s title with “Support Theme:”. You can also use this pre-made query for viewing reported issues.

In addition to reporting bugs, we now have two master posts to aid in planning a new Forum Welcome and new forum descriptions.

This is how it’s launching for now (with a query string cookie toggle), and once everyone is confident that the bugs have been worked out, it will be launched for real! 🙂

WCUS 2016 Plans

We’ll be discussing our plans for WordCamp US 2016 during next week’s meeting, Thursday, November 17, 2016, 17:00 UTC in #forums on Slack.

Trolls and Harassment

If someone’s attacking you on the forums, following you off the forums, or otherwise making you scared to contribute, please speak up and let someone you trust know. If you want to tell someone privately, please DM a moderator.

You’re not alone on the forums. We’re a team for a reason.

Checkin with International Support Liaisons

Attendance

@macmanx @clorith @jmdodd @bcworkz @fierevere @ipstenu @lasacco @cristianozanca @sterndata @imazed @geoffreyshilling @songdogtech @jdembowski @zoonini @t-p @kidsguide @stephencottontail @d4z_c0nf @danhgilmore @lukecavanagh @georgestephanis @alchymyth attended.

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

#weekly-chat

Agenda for November 10th Support Meeting

  • General Announcements
  • Testing WordPress 4.7 Beta 2
  • Continue to Test the New Forum Theme
  • Checkin with International Support Liaisons

For any other items to discuss please add them in the comments below, or bring them up in the meeting.

The meeting will be Thursday, November 10, 2016, 17:00 UTC in #forums on Slack. (a Slack account is required)

November 3rd Support Team Meeting Summary

Announcement

WordPress 4.7 Beta 1

The first WordPress 4.7 Beta is here, so please start testing.

If you don’t have any room on your own server or hosting account, there are some great guides for setting up a local server environment.

More bug reports during the beta means less forum threads after the final release.

New Forum Theme

Please continue to test the forum redesign!

To start the fun, simply visit https://wordpress.org/support/?new-theme=1

It works off of a cookie, so if you need to switch back, simply visit https://wordpress.org/support/?new-theme=0

If you find anything broken, please open a ticket in Meta Trac (after searching first, of course) under the Support Forums component, and prepend the ticket’s title with “Support Theme:”. You can also use this pre-made query for viewing reported issues.

In addition to reporting bugs, we now have two master posts to aid in planning a new Forum Welcome and new forum descriptions.

This is how it’s launching for now (with a query string cookie toggle), and once everyone is confident that the bugs have been worked out, it will be launched for real! 🙂

Publicly Requesting/Posting Private Information

We have received some concerns of folks asking for and/or even providing other people’s private information, such as location, primarily in settings like IRC and Slack.

While we understand that this is typically being done in a friendly manner, please be aware that some folks would rather not share such things (even as broad as state or country) in a public setting, even despite being eventually conceded into doing so.

If it is not necessary to resolving their support issue (it rarely is), please just don’t ask, and if you catch anyone else asking, please convey this to them.

And never, under any circumstances, provide someone else’s private information. If you catch anyone doing that, please immediately report it to a moderator.

While many of us are friends, remember that not everyone wants the world to know their job, gender, living situation, location, etc. Be respectful. If it’s not your personal information, don’t talk about it in public.

WordPress Ideas Section

WordPress Ideas has been around for a long time. To the best of our knowledge, it’s not actively monitored, it only has two moderators, and it’s still on an old version of bbPress.

It sounds like there has been some discussion on replacing it, but nothing recent, so we had a discussion and a vote on what we’d like to do with it (understanding that the decision may be out of our hands).

If the decision does come down to us, by unanimous vote, we would like to retire the WordPress Ideas section in favor of the Requests and Feedback forum.

Update: Meta Ticket 2203 has been filed for this.

Twenty Seventeen Issues

There was some confusion around how to handle reported issues with the new Twenty Seventeen default theme now shipping in the 4.7 Beta, since the theme is not officially “live” yet.

Please report bugs in Trac using the Bundled Theme component.

If you’re already helping a user on the forums with the Twenty Seventeen theme, and want to crowdsource opinions before sending them off to Trac with a bug report, try #core-themes on Slack.

Post-DST Meeting Time Change

Starting next week, by 13 to 2 vote, our meetings will be at 17:00 UTC, which means the next meeting will be Thursday, November 10, 2016, 17:00 UTC.

Checkin with International Support Liaisons

Attendance

@macmanx @bcworkz @jmdodd @cais @lukecavanagh @bdbrown @geoffreyshilling @sterndata @kidsguide @cristianozanca @zoonini @danhgilmore @jdembowski @songdogtech @alchymyth @bethannon1 @stephencottontail @ipstenu @kenshino @jcastaneda @erricgunawan @t-p @tnash @numeeja @clorith @valeriosza @sergeybiryukov @zodiac1978 attended.

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

#weekly-chat