Auto-formatting of author bios reverted in 4.9.2

In WordPress 4.9.2 auto-formatting of author bios via get_the_author_description was removed after being introduced in WordPress 4.9.

Introducing auto-formatting broke a number of themes. Unfortunately, reverting it in 4.9.2 potentially breaks themes that had implemented a fix for this

For background, formatting was introduced in #40040 and reverted in #42578.

Maintaining auto-formatting

Theme authors wishing to maintain auto-formatting of author bios can add the following code to their theme's functions.php file.

add_filter( 'get_the_author_description', 'wptexturize' );
add_filter( 'get_the_author_description', 'convert_chars' );
add_filter( 'get_the_author_description', 'wpautop' );
add_filter( 'get_the_author_description', 'shortcode_unautop' );

#4-9, #4-9-2, #dev-notes

Dev Chat Agenda: January 17th (4.9.2 week 7)

This is the agenda for the weekly dev meeting on January 17, 2018 at 21:00 UTC / January 17, 2018 at 21:00 UTC:

  • 4.9.2 planning
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-2, #agenda, #core, #dev-chat

Dev Chat Summary: January 10th (4.9.2 week 6)

This post summarizes the dev chat meeting from January 10th (agenda, Slack archive).

4.9.2 planning

  • Tentative release timing of 1/16 for beta, 1/23 for RC, and 1/30 for release
  • 57 tickets currently on the milestone, @sergey will be reviewing them during a bug scrub on Friday (Jan 12th) at 19:00 UTC
  • Bug scrubs for future weeks will be scheduled around 19:00 UTC on Mondays, Wednesdays, and/or Fridays by @sergey and @desrosj

Updates from focus leads and component maintainers

  • Design team would like to check in with the other teams and see if anyone has projects they need designers for in the next couple months. If you have needs then please reach out in the #design channel.
  • REST API team would like to know if your work would be aided by API improvements or is blocked by API issues; if so, please come see them in #core-restapi.
  • Media and PHP teams have posted their meeting recaps from the past week for review.

Servehappy project

  • @schlessera: posted a Servehappy project overview
  • Our goal is to have a positive impact on PHP version distributions, to get a higher percentage of servers to run on supported PHP versions.
  • We have 3 main building blocks right now:
    • 1. information page about PHP, its versions, and upgrading them (see: draft)
    • 2. admin notices letting site owners know they run an old version
    • 3. plugin/theme requirements that prevent installation/updates when PHP version requirements are not met
  • @flixos90: Regarding #1, we have a Trac ticket in place. The page itself has two goals: Convince site owners that it's worth their time to take action, and then explain how they can proceed.
  • How and who do we approach to get it on wordpress.org infrastructure? Should it be hosted as an area inside .org or as a separate site with separate domain (if yes, which one)?
  • Plan to collaborate with Tide, in terms of preparing the PHP upgrade as users could check for their plugins and themes compatibility.
  • @stevenkword: We are also considering making the PHP Compatibility Checker plugin a consumer of Tide when it's production ready. Leveraging the cached results would really speed it up. We're pushing an update for 5.2 support this afternoon, and it will contain 7.1 and 7.2 checks
  • Anyone who's interested in helping out, please join our weekly meetings on Monday 16:00 UTC, and of course feel free to review what we currently have.

General announcements

  • @jorbin: I want to draw some early attention to a ticket that has the potential to impact all core contributions, especially related to JavaScript. Please take a read of #43055 and after reading it all, comment with any thoughts or concerns.
  • @audrasjb: when will we have a chance to know WP 5.0 delivery roadmap?
    • @jbpaul17: I’m not aware of any pending updates, so I’d suggest for now joining the conversation in #core-editor and helping with Gutenberg as any roadmap or timeline will come from the progress of development there.

Next meeting

The next meeting will take place on January 17, 2018 at 21:00 UTC / January 17, 2018 at 21:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#4-9-2, #core, #dev-chat, #summary

Dev Chat Agenda: January 10th (4.9.2 week 6)

This is the agenda for the weekly dev meeting on January 10, 2018 at 21:00 UTC / January 10, 2018 at 21:00 UTC:

  • 4.9.2 planning
  • Updates from focus leads and component maintainers
  • Servehappy project
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-2, #agenda, #core, #dev-chat

No Dev Chat This Week (4.9.2 week 5)

A reminder that there will be no devchat this week as we are on hiatus over the holidays.

 

The next devchat will be on January 10, 2018 at 21:00 UTC / January 10, 2018 at 21:00 UTC.

#4-9-2, #core, #dev-chat

No Dev Chat This Week (4.9.2 week 4)

A reminder that there will be no devchat this week as we are on hiatus over the holidays.

 

The next devchat will be on January 10, 2018 at 21:00 UTC / January 10, 2018 at 21:00 UTC.

#4-9-2, #core, #dev-chat

Dev Chat Summary: December 20th (4.9.2 week 3)

This post summarizes the dev chat meeting from December 20th (agenda, Slack archive).

4.9.2 planning

  • @sergey to be release lead, @williampatton to be deputy release lead
  • @desrosj able to help with bug scrubs
  • Tentative release timing of 1/16 for beta, 1/23 for RC, and 1/30 for release

Confirm definition of "minor release"

  • Confirmed definition: Bugfixes and enhancements that do not add new deployed files and are at the discretion of the release lead with suggestions/input from component maintainers and committers.
  • @jbpaul17 added that definition to the handbook for future reference (see here, here, and here)

Updates from focus leads and component maintainers

  • Team Editor (Gutenberg): They have no more meetings until January 3rd in #core-editor. The channel is of course open all the time, but meetings will resume then. They also have a request for assistance on video processing of the usability videos from WCUS. Please check the post if you’re available / have interest.
  • Teams Customize and REST API are both on hiatus through the holidays and have no updates this week.
  • Multisite published a post about their roadmap

Meeting hiatus over holidays

  • There will be a two week hiatus for devchat, final meeting for 2017 is today (December 20th). First meeting for 2018 will be January 10th.

General announcements

  • @presskopp looking for advice on getting patches reviewed. Advice given is to ping component maintainers, mention it during devchat's General announcements section, or mention it during a bug scrub.
  • @schlessera looking for advice on getting something on the devchat agenda for January 10th. Advice given is to ping @jbpaul17, mention it during devchat's General announcements section, or add it as a comment to the agenda post. Also noted that Make/Core posts can be a good idea for things that need some discussion and can happen at any time.
  • @schlessera to work on a Make/Core post around the topic of "Servehappy project – current status and how to proceed to have the effort blessed"

#4-9-2, #core, #dev-chat, #summary

Dev Chat Agenda: December 20th (4.9.2 week 3)

This is the agenda for the weekly dev meeting on December 20, 2017 at 21:00 UTC / December 20, 2017 at 21:00 UTC:

  • 4.9.2 planning: release lead, bug scrubs, timing
  • Confirm definition of "minor enhancements/features"
  • Updates from focus leads and component maintainers
  • Meeting hiatus over holidays
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-2, #agenda, #core, #dev-chat

Dev Chat Summary: December 13th (4.9.2 week 2)

This post summarizes the dev chat meeting from December 13th (Slack archive).

4.9.2 planning

  • @obenland available to volunteer as release lead, offline until January 8th
  • @westonruter planning to start committing fixes in January after reviewing patches in the 4.9.2 milestone
  • Potential release timing of 1/16 for beta, 1/23 for RC, and 1/30 for release could work

Devchat coordination

  • There will be a two week hiatus for devchat, final meeting for 2017 will be December 20th
  • First meeting for 2018 will be January 10th

General announcements

  • @paaljoachim asks if there is someone who has interest in helping lead work on the exporter / importer
    • @rmccue also started a similar project
    • project not likely to see significant progress until its made a focus
    • revamping the import/export workflow is a huge, not unrisky lift
    • the import/export work is a continuation of the previous work already done on the Export-API #22435
  • @paragoninitiativeenterprises noted plugin breakage concern with #42439 plus 4.9.2 release note recommendation
  • @paaljoachim asks if there is someone who has interest in helping lead work on the admin bar (#32678)
    • @danieltj is component maintainer, will look into it

#4-9-2, #core, #dev-chat, #summary

Dev Chat Summary: December 6th (4.9.2 week 1)

This post summarizes the dev chat meeting from December 6th (agenda, Slack archive).

4.9.2 ticket triage + timing

  • 41 tickets already marked for 4.9.2, minus fixed-major there are 39 tickets
  • #42586 is the only high priority ticket in the milestone
  • Aiming for 4.9.2 release toward the end of January 2018

Plan for 4.9.x minor releases

  • Will look to do 6-8 weeks for a release window with 4-6 weeks of work, week and a half of beta, half week of RC
  • From past experience, its best to have someone who isn’t the major release lead handle a minor release as it (1) gets the major release leads some rest and (2) gets more folks familiar with the release process
  • @kadamwhite @joemcgill @desrosj interested in helping as a minor release lead, but unavailable in January. @obenland available to lead a minor release, @sergey available as a backup lead.
  • If you have interest in being a minor release lead, please ping @jbpaul17 or mention in #core. Self-nominations are accepted and encouraged, you don't have to be an engineer, and commit access is not required but helpful.
  • We need to make sure we have people with WP.org access available for the builds, but anyone with the knowledge can organize/follow up on tickets in the lead up to a release and be a decision maker.
  • No rush to find someone with WP.org access to package a release until the week leading up to a release
  • Would be good to add a “next-minor” milestone to Trac so we could pull things into the 4.9.x milestone once they are actually resolved instead of mass punting

Definition of "minor" release

  • Bugfixes and minor enhancements/features that do not add new deployed files and are at the discretion of the release lead with suggestions/input from component maintainers.

Weekly updates from leads

  • Focus leads to provide weekly updates including:
    • what big things happened this week?
    • what needs eyes/testing?
    • what big challenges could the team use help with?
    • what decisions need feedback before being made?
  • Component leads to provide updates as necessary, though not required weekly, and focused mainly on big things or areas where we need coordination

#4-9-2, #dev-chat, #summary