Tag Archives: 5.6.1

Jb Audras 12:05 am on February 23, 2021
Tags: 5.6.1, ,   

A Week in Core – February 22, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between February 15 and February 22, 2021.

  • 41 commits
  • 63 contributors
  • 91 tickets created
  • 7 tickets reopened
  • 85 tickets closed

You might have noticed that the activity on Core continued to increase this week, as we are close to the end of WordPress 5.7 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. cycle. We’ll enter the Release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). cycle on February 23. Worth also noting that WordPress 5.6.2 was released earlier today.

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

Administration

  • Apply background color to updated message in pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party list table – #52452
  • Apply the months_dropdown_results filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. separately from pre_months_dropdown_query – #51660

Build/Test tools

  • Tests: Add missing @covers tags for files in phpunit/tests/http/ – #39265

Bundled Themes

  • Twenty Twenty-One: Add the px unit to the adminadmin (and super admin) bar height custom property – #52564
  • Twenty Nineteen: Add some space between the cookies checkbox and label in comment form – #46601
  • Twenty Twenty-One: Remove background color from Social Links the dark gray style – #52499
  • Twenty Ten: Correct the fallback to the default headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. if the featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. width is narrower than the twentyten_header_image_width setting – #52516
  • Twenty Eleven: Correct the fallback to the default header if the featured image width is narrower than the twentyeleven_header_image_width setting – #52516
  • Twenty Twenty: Make sure the RTL list styles are preserved after npm run build – #52401
  • Fix alignment and styles for quote, verse, and code blocks – #52009
  • Support font size option for code blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. – #52431
  • Twenty Thirteen: Fix alignment of child blocks within the Cover block – #51224
  • Twenty Twenty-One: Display inline-images inline – #52287
  • Twenty Twenty-One: Match bullets between editor and frontend – #52412
  • Twenty Twenty-One: Add CSSCSS Cascading Style Sheets. source map files to committed files – #52377

Cron APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.

  • Add a missing $wp_error parameter to the pre_reschedule_event filter – #52572

CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.

  • Bring admin color schemes back into the customizer – #52230

Editor

  • Additional tests for reusable blocks – #52364
  • Update packages with bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes to be included in WP 5.7 beta 3 – #52525

Embeds

  • Allow posts with a public custom post status to be embedded – #47574

External Libraries

  • Upgrade PHPMailer to version 6.3.0 – #52577
  • Revert the change to the tb_click() function in the Thickbox library – #51812
  • Further fix jQuery deprecations in WordPress core – #51812

Feeds

  • Fix the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org returned by get_feed_link() when pretty permalinks are not in use – #51839

Filesystem API

  • Make sure to only call fread() on non-empty files in the PclZip library – #52018

General

  • Add noindex robots metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) to search results – #52457

Internationalization

  • Remove extra spaces from translatable strings in Privacy help tabs – #52583

Media

  • Explicitly declare the $pagenow global in wp_get_attachment_url() – #52606
  • Associate upload errors and field with controls – #47120

Posts, Post Types

  • Rename the new post parent conditional tag functions for clarity – #33045
  • Prevent duplicates in sticky posts option – #52007
  • Update the styling of the legacy Links editing screen – #48782

Security

  • Fix bug in wp_is_local_html_output() – #52542

Site Health

  • Update loopback test to POST to wp-cron – #52547
  • Use home page for loopback test – #52547

Script Loader

  • Prevent wp_localize_script() warnings – #52534
  • Explicitly declare the $pagenow global in wp_deregister_script() – #52566

TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.

  • Optimize wp_delete_term() for large object counts without a default term – #52549
  • AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility): Correct keyboard navigation for the Tags meta box in classic editor – #52408

Users

  • Correctly display an error message after clicking the “Send Reset Link” button – #52573

XML-RPC

  • Pass the method arguments and the XML-RPC server instance to the xmlrpc_call action – #52524

Props

Thanks to the 63 people who contributed to WordPress Core on Trac last week:

@peterwilsoncc (10), @poena (10), @sabernhardt (7), @audrasjb (7), @mukesh27 (5), @SergeyBiryukov (5), @jrf (3), @paaljoachim (3), @talldanwp (2), @johnbillion (2), @macmanx (2), @ayeshrajans (2), @TimothyBlynJacobs (2), @melchoyce (2), @dd32 (2), @afragen (2), @kjellr (2), @kburgoine (1), @antonlukin (1), @tobifjellner (1), @cristinasoponar (1), @pbiron (1), @burnuser (1), @ryelle (1), @grzim (1), @DavidAnderson (1), @yakimun (1), @fierevere (1), @hauvong (1), @afercia (1), @anevins (1), @antpb (1), @adamsilverstein (1), @jeroenrotty (1), @mahfuz01 (1), @tejwanihemant (1), @patopaiar (1), @desrosj (1), @joedolson (1), @hellofromTonya (1), @abagtcs (1), @johnjamesjacoby (1), @lukecarbis (1), @tmatsuur (1), @clorith (1), @nico23 (1), @bernhard-reiter (1), @Levdbas (1), @rahmohn (1), @archon810 (1), @burtrw (1), @ryokuhi (1), @jonoaldersonwp (1), @goaroundagain (1), @xkon (1), @bordoni (1), @garrett-eclipse (1), @monikarao (1), @Boniu91 (1), @almendron (1), @jose64 (1), @alexstine (1), and @isabel_brison (1).

Please join me to say welcome to our 10 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@cristinasoponar, @burnuser, @grzim, @mahfuz01, @tejwanihemant, @abagtcs, @nico23, @goaroundagain, @almendron, and @jose64.

Core committers: @sergeybiryukov (18), @peterwilsoncc (9), @ryelle (7), @johnbillion (4), @flixos90 (1), @joedolson (1), and @youknowriad (1).

Please note: it only includes commits with proper props attribution.

#5-6-1, #5-7, #week-in-core

Jb Audras 10:43 pm on February 15, 2021
Tags: 5.6.1, ,   

A Week in Core – February 15, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between February 8 and February 15, 2021.

  • 36 commits
  • 43 contributors
  • 63 tickets created
  • 9 tickets reopened
  • 67 tickets closed

You might have noticed that the activity on Core continued to increase this week, due to WordPress 5.7 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. cycle.

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

Administration

  • Update color contrast on UIUI User interface elements – #52402

Bundled Themes

  • Support font size option for code blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. – #52431
  • Twenty Thirteen: Fix alignment of child blocks within the Cover block – #51224
  • Twenty Twenty-One: Correct accent marks in block pattern alt text – #52500
  • Twenty Twenty: Make ordered list styling in classic editor match the front-end style – #50454
  • Twenty Twenty-One: Use correct value for the global line-height CSSCSS Cascading Style Sheets. variable – #52477
  • Twenty Twenty-One: Update editor styles of search block – #52433
  • Twenty Twenty-One: Adapt vertical buttons to text length – #52432
  • Twenty Twenty-One: Support font size option for code block – #52431
  • Twenty Twenty-One: Prevent Dark Mode related JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. error – #52473

Build/Tests tools

  • Add missing @covers tags for files in phpunit/tests/http/ – #39265
  • Add missing @covers tags for files in phpunit/tests/hooks/ – #39265
  • Add missing @covers tags for files in phpunit/tests/general/ – #39265
  • Add missing @covers tags for files in phpunit/tests/external-http/ – #39265
  • Add missing @covers tags for files in phpunit/tests/error-protection/ – #39265
  • Add missing @covers tags for files in phpunit/tests/editor/ – #39265
  • Add missing @covers tags for files in phpunit/tests/dependencies/ – #39265
  • Add missing @covers tags for files in phpunit/tests/db/ – #39265
  • Install WordPress Importer pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party when installing the Docker-based local environment – #49720
  • Replace most instances of assertEquals() in phpunit/includes/ with assertSame() – #38266, #52482
  • Add missing @covers tags for files in phpunit/tests/date/ – #39265
  • Synchronize svn:ignore with .gitignore – #49784
  • Correct the test for NOT BETWEEN comparison operator in WP_Date_Query – #39265, #51802

Canonical

  • Rename wp_force_plain_ugly_permalink() to match UI terminology – #5272

Comments

  • Extend the duration of the window within which unapproved comments are visible by their author – #52406

Editor

  • Block Editor: Update packages with bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes to be included in WP 5.7 beta 3 – #52525
  • Block Editor: Remove extra quotes from the default font stack for editor styles – #46169

External Libraries

  • Further fix jQuery deprecations in WordPress core – #51812

Internationalization

  • Fix wp.i18n.isRTL() – #52441

Media

  • Make adjacent_image_link() include alt text when returning an image – #52387
  • Allow post_date to be respected in media_handle_sideload() – #50972

Posts, Post Types

  • Clarify the documentation about the return value of get_post() when a falsey value is passed – #33068
  • Improve documentation of get_posts() – #51852, #51800

Site Health

  • Update site-health script dependencies – #52483
  • Link to the support article on troubleshooting in “There has been a critical error” message – #52392
  • Site Health: Clarify the recommendation in file uploads test when post_max_size is defined as 0 – #51466

Props

Thanks to the 43 people who contributed to WordPress Core on Trac last week:

@jrf (11), @patopaiar (10), @poena (6), @hellofromTonya (6), @Clorith (4), @paaljoachim (4), @SergeyBiryukov (4), @mukesh27 (4), @audrasjb (4), @peterwilsoncc (4), @joedolson (3), @johnbillion (3), @kjellr (2), @dd32 (2), @jeroenrotty (2), @Mista-Flo (2), @sabernhardt (2), @justinahinon (1), @Rahe (1), @juliobox (1), @jonsurrell (1), @pixolin (1), @rolfsiebers (1), @jamesgol (1), @helen (1), @youknowriad (1), @ratneshk (1), @ocean90 (1), @hareesh-pillai (1), @dariak (1), @davidbaumwald (1), @alexstine (1), @imath (1), @Ipstenu (1), @acerempel (1), @sebastienserre (1), @geekzebre (1), @gmariani405 (1), @kafleg (1), @Joen (1), @isabel_brison (1), @melchoyce (1), and @dam6pl (1).

Please join me to say welcome to our 4 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@ratneshk, @acerempel, @geekzebre, and @dam6pl.

Core committers: @sergeybiryukov (17), @peterwilsoncc (7), @ryelle (3), @desrosj (3), @antpb (2), @johnbillion (2), @youknowriad (1), and @noisysocks (1).

Please note: it only includes commits with proper props attribution.

#5-6-1, #5-7, #week-in-core

Jb Audras 11:18 pm on February 10, 2021
Tags: 5.6.1, , ,   

DevChat meeting Summary – February 10, 2021

@marybaum and @metalandcoffee led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements and news

Amongst other news, there is one interesting news to share: according to W3Techs, 40% of the web uses WordPress 💥

As said in the W3Techs blogpost, “The incredible success story of WordPress continues by reaching another milestone: 2 out of every 5 websites use it now.”

Upcoming WordPress releases

WordPress 5.6.1

WordPress 5.6.1 was released on February 3, 2021.

The minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. squad plans to release a quick 5.6.2 after some issues were discovered with Classic Editor. A patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. is being worked on in ticketticket Created for both bug reports and feature development on the bug tracker. #52440.

WordPress 5.7

WordPress 5.7 beta 2 was released on February 9, 2021.

@metalandcoffee: BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3 is next, then RC1, RC2 and finale release.

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 9.9 was released last week! It’s the final release that will be included in 5.7 and contains some fun improvements and lots of bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes.

@melchoyce shared that the about page is in progress. The marketing team plan to work on the copy. @melchoyce asked to post the work-in-progress in ticket #52347.

@audrasjb started to work on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and to prepare the field guideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.. The first one was published a couple hours before the devchat. He will now reach out to ticket owners and component maintainers to ensure we have everything in time for RC1. Also, he started to identify what HelpHub pages (documentation for end-users) will need to be updated. @clorith mentioned the FAQ & Troubleshooting page, which is going to be recommended to users when there’s been a fatal error on their website.

Component maintainers updates

Build/Test Tools (@sergeybiryukov):

  • Work has completed on upgrading older branches to run on NodeJS LTS (currently 14.x), and backporting the local Docker environment to them. These changes unblock the ability to move automated testing over to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Actions. See tickets #52341, #48301, and #50401 for more details.
  • The WordPress Importer pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party is now installed when installing the Docker-based local environment. See ticket #49720 for more details.

Thanks to @desrosj who is working on these tasks!

Date/Time, General, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks (@sergeybiryukov): No major news this week.

Customize (@dlh): #50781 has a new patch that could use review and testing.

Site Health (@clorith): Nothing new and exciting to report this week, lots of late-cycle ticket made it in though.

Upgrade/Install (@afragen & @audrasjb):

Editor (@noisysocks):

  • There are some editor issues the editor team would like to draw attention to:
    • Image blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.: Duplicate copies of media files created in library #25805
    • Cover: 9.8 does not migrate content position correctly #28656
    • Reusable block can’t be converted to a regular block #26421
    • Can’t paste text into editor on IE 11 #26988

Open floor

WordPress 5.8 release squad:

Discussion about Internet Explorer 11 support:

  • Global usage is now 1%
  • It might go up again though
  • Let’s discuss during next release cycle
  • Let’s prepare a Make/Core post to announce a potential end of support for IE 11

News from Training/Learn WP, by @webcommsat: “We are also continuing to work with Training and Learn WordPress about how we can bring all the extra information and resources post release together to support users, and looking forward to continuing to chat to Support and Docs too. This kind of working together is great and thanks to everyone who has been involved.”

#5-6-1, #5-7, #dev-chat, #summary

Jb Audras 10:33 pm on February 8, 2021
Tags: 5.6.1, ,   

A Week in Core – February 8, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between February 1 and February 8, 2021.

  • 41 commits
  • 123 contributors
  • 64 tickets created
  • 9 tickets reopened
  • 79 tickets closed

You might have noticed that the activity on Core continued to increase this week, due to WordPress 5.7 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. cycle. Also, WordPress 5.6.1 was released on Wednesday 3, 2021.

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

Administration

  • Fix background color of pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party update row on small screens – #52452
  • New filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. ahead of the months drop-down – #51660
  • use shorthand css properties to improve readability – #52148
  • Coding Standards: Update links to be httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in package-lock.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. – [50163]

Build/Test Tools

  • Fix tests after [50185] – #52341
  • Specify a version range within engines for node and npm – #52455

Docs

  • Clarify the @return value for wp_get_attachment_image_url() and get_the_post_thumbnail_url() – #52183

Editor

  • Correct the check for unsaved content in wp.autosave.server.postChanged() – #52440

Media

  • Use a unique name for the nonce of the custom fields toggle form – #51483
  • Pause any playing media when closing the the media modal – #48562
  • Consistency in logic to pass wp_getimagesize() tests – #49889

Privacy

  • Remove gray left border on the inline notices in Privacy Policy Guide – #52430
  • Update URLs to the Privacy Policy Guide in help tabs – #52430
  • Rename the $send_confirmation_email parameter of wp_create_user_request() to $status, for clarity – #52430
  • Update colors to match new color palette – #52436
  • Redesign the Privacy settings pages – #49264

Security

  • add Content-Security-Policy script loaders – #39941

TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.

  • Add filter for post statuses when updating term count – #38843

Users

  • Allow the role of users to be bulk changed to no role from the Users listing screen – #52238

Props

Thanks to the 123 people (that’s HUGE) who contributed to WordPress Core on Trac last week:

@hellofromTonya (12), @xkon (10), @TimothyBlynJacobs (7), @audrasjb (6), @paaljoachim (5), @peterwilsoncc (5), @mukesh27 (5), @dd32 (4), @SergeyBiryukov (4), @hedgefield (4), @garrett-eclipse (4), @sabernhardt (4), @afragen (3), @birgire (3), @whyisjake (3), @johnbillion (3), @Mista-Flo (3), @desrosj (2), @poena (2), @davidbaumwald (2), @knutsp (2), @estelaris (2), @noisysocks (2), @flixos90 (2), @adamsilverstein (2), @dlh (2), @afercia (2), @Clorith (2), @kurtpayne (1), @jaymanpandya (1), @anyssa (1), @sippis (1), @AmethystAnswers (1), @timothyblynjacobs (1), @lukecavanagh (1), @magicroundabout (1), @erichmond (1), @DrewAPicture (1), @Ipstenu (1), @nico_martin (1), @eventualo (1), @bduclos (1), @yannkozon (1), @wonderboymusic (1), @ericlewis (1), @joyously (1), @pento (1), @tinodidriksen (1), @markhowellsmead (1), @jrf (1), @ianmjones (1), @nacin (1), @jeremyfelt (1), @prettyboymp (1), @r-a-y (1), @ryan (1), @dimadin (1), @stevenkword (1), @jfarthing84 (1), @aristath (1), @7studio (1), @kara.mcnair (1), @swissspidy (1), @pbiron (1), @Howdy_McGee (1), @netweblogic (1), @burtrw (1), @megabyterose (1), @souri_wpaustria (1), @pixelverbieger (1), @e_baker (1), @scruffian (1), @iprg (1), @Joen (1), @viablethought (1), @GunGeekATX (1), @mkaz (1), @jeroenrotty (1), @ovidiul (1), @bonniebeeman (1), @magnuswebdesign (1), @hmabpera (1), @worldedu (1), @dbtedg (1), @bartosz777 (1), @nwjames (1), @roger995 (1), @tonysandwich (1), @ibiza69 (1), @archon810 (1), @hwk-fr (1), @naveen17797 (1), @GeekPress (1), @vandestouwe (1), @amolv (1), @justinahinon (1), @davecpage (1), @tomdxw (1), @herregroen (1), @ankitmaru (1), @jnylen0 (1), @jason_the_adams (1), @mayankmajeji (1), @karmatosed (1), @wesselvandenberg (1), @allendav (1), @iandunn (1), @TZ-Media (1), @azaozz (1), @joedolson (1), @hareesh-pillai (1), @jadeddragoon (1), @geoffguillain (1), @jorbin (1), @antpb (1), @clorith (1), @ocean90 (1), @enricocarraro (1), @alinod (1), @epicfaace (1), @mallorydxw (1), @jrchamp (1), and @JoshuaWold (1).

And we also have a new Week in Core record! Please join me to say welcome to our 21 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@alinod, @jadeddragoon, @mallorydxw, @epicfaace, @hwk-fr, @enricocarraro, @geoffguillain, @nwjames, @GeekPress, @viablethought, @naveen17797, @ibiza69, @tonysandwich, @roger995, @bartosz777, @dbtedg, @worldedu, @hmabpera, @magnuswebdesign, @vandestouwe, and @bonniebeeman.

Core committers: @sergeybiryukov (14), @antpb (6), @desrosj (3), @timothyblynjacobs (3), @peterwilsoncc (3), @ryelle (2), @adamsilverstein (2), @whyisjake (2), @joemcgill (2), @ocean90 (1), @johnbillion (1), @jorbin (1), and @iandunn (1).

Please note: it only includes commits with proper props attribution.

#5-6-1, #5-7, #week-in-core

Abha Thakor 6:48 pm on February 4, 2021
Tags: 5.6.1, , , , plugin/theme rollback   

Devchat meeting summary – February 3, 2021

Agenda for the two meetings. Thanks to @thewebprincess and @hellofromtonya for leading the 05:00 and 20:00 UTC devchats respectively.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements and news

WordPress 5.7 Beta 1 is out and available for testing.

WordPress 5.6.1 landed after devchat.

Month in WordPress for January 2021 (published 3 February 2021)

Reminder from Marketing, @webcommsat: we start our marketing planning well in advance, so if you are working on something for later in the year or that could be in the Questions and Answers on 5.7 or 5.6.1, please let @webcommsat, @yvettesonneveld, and @meher know. 

Week in Core – edition 1 February 2021

What’s next in Gutenberg?

Full Site Editing (FSE)

Component maintainers and committers update

Post from @chanthaboune on encouraging and recognizing committers and maintainers following on from discussions – Committers, Maintainers and Emeriti. This will also help show which areas need support in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

  • Discussion during the meeting:
    • making it easier for people to see how they can become committers
    • using official emeritus status outside core for particular roles
  • Specific comments:
    • @hellofromtonya: Any concerns with deactivating their commit status with a path to reactivate when/if they become active again? No one in the meeting raised any concerns on this.
    • @sergey: A place to mentor potential new committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component..
    • @webcommsat: This would help so much with the recruitment and longer term contribution of committers too.
    • @nalininonstopnewsuk: Suggested more promotion on what skills and computer facilities potential committers would need. Supports the emeritus idea.
  • @annezazu and @hellofromtonya are interested in discussing a mentorship program.

Updates from component maintainers

@sergey

Build/Test Tools: The Sass implementation that Grunt uses has switched from node-sass to Dart Sass. That’s because LibSass and node-sass have been deprecated. Ticketticket Created for both bug reports and feature development on the bug tracker. #51763 for more details.

  • General: The get_home_url() function now consistently returns an httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org if the current request is already https, both for the adminadmin (and super admin) and front end. This fixes a previous inconsistency between the admin and front end URLs. See ticket #52421 for more details.
  • Date/Time, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks: No major news this week 

@audrasjb

Upgrade/Install, Menus & Widgets: no major new this week, except that all our enhancements and features were finally committed before 5.7 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1.

@hellofromtonya:

  • 5.7 Beta 1 is out in the wild and ready for you to test and give feedback
  • It includes 143 tickets with 68 new features and enhancements 
  • Now the focus shifts to defects as well as supporting your feedback on the beta releases
  • There are currently 118 tickets open in 5.7 [ listing ]. Please help get as many as we can into the release during the beta cycle.

Update on WordPress 5.6.1 from @audrasjb:

Update and discussion on PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/Theme Rollback

  • GitHub details on the plugin/ theme rollback update
  • @hellofromtonya: We had planned to include plugin/theme rollback in WordPress 5.7, but it will become a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. first. @afragen is doing the building, and it’s almost ready to submit to WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.
  • @ipstenu will flag it as an official beta for review
  • @davidbaumwald: is that plugin slated to roll over to the WordPress GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ account, or is it a gap-filler that doesn’t require that? @afragen: not sure it needs lots more actual work. But whatever the usual process is will be fine.
  • @hellofromtonya: currently, it’s set for feedback to validate if there are performance issues that could cause additional update failures.
  • Question: should it remain as a separate plugin repo (not on the WordPress GitHub) until we know more? Thoughts invited. @afragen: It will also be very difficult to evaluate that, but I’m open to saying if there’s a server timeout it could be related.
    • some support for moving it to WordPress GitHub account
    • @davidb suggested gaining more visibility would help and following view of the maintainers. Agreement from the meeting of the benefits of extra visibility. @audrasjb shared how promoting visibility had helped a lot for plugins and themes auto-updates, and he will share what was done for that feature plugin
    • @hellofromtonya: Getting more on it will also help us to further improve plugin and theme updates. Hoping to collect more information on the root causes for update failures
    • @sergeybiryukov: My concern is that the plugin in its current state doesn’t seem to follow the direction outlined in comment 56 on the ticket. More discussion planned for the next #core-auto-updates meeting.
    • #51857: Add rollback for failed plugin/theme updates – I don’t think that comment was as much about rollback as making the update process more robust. I think that was suggested as an alternative to rollback that would have fewer performance concerns. We could probably have both.
    • @hellofromtonya: improving the update process itself is important! If we get robust enough, it negates the need to rollback when a failure happens. That assumes though that failures will never happen, which not sure if that’s a reasonable assumption.

Next steps:

Open Floor

Who is moderating feedback on the Code Reference? @audrasjb once a week and @crstauf more regularly. This is part of the Docs Team’s work.

#5-6-1, #5-7, #dev-chat, #fse, #plugin-theme-rollback

Jb Audras 12:14 am on February 2, 2021
Tags: 5.6.1, ,   

A Week in Core – February 1st, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 25, 2021 and February 1st, 2021.

  • 57 commits
  • 93 contributors
  • 62 tickets created
  • 8 tickets reopened
  • 84 tickets closed

You might have noticed that the activity on Core increased this week. This is due to the end of the alpha cycle of WordPress 5.7 (next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.) and WordPress 5.6.1 (next minor) 🗓
5.7 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is planned for tomorrow and 5.6.1 is planned on Wednesday 3, 2021 🚀

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

Administration

  • Remove italic text to improve readability – #47327
  • Accommodate long translations of user roles in the “Role” list table column – #52184
  • Standardize colors used in CSSCSS Cascading Style Sheets. to a single palette – #49999
  • Respect the prefers-reduced-motion media query for update icon spinner animations – #52263

Application Passwords

  • Introduce fine grained capabilities – #51703
  • Introduce introspection endpoint – #52275
  • Improve validation and sanitization of the application name – #51941

Build/Test Tools

  • Replace node-sass with Dart Sass – #51763

Bundled Themes

  • Twenty Twenty-One: Correct filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. name in twenty_twenty_one_get_starter_content() DocBlockdocblock (phpdoc, xref, inline docs) – #52410
  • Twenty Twenty-One: Correct colors for the Menu button – #52374
  • Twenty Twenty: Remove aria-expanded on search modal close button – #52355

Comments

  • Introduce a method for commenters to opt-in to receiving an email notification when their moderated comment gets approved – #33717

Editor

  • Introduce a dynamic filter for the content of a single blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. – #46187
  • Update @wordpress npm packages – #52334
  • Add enableCustomSpacing – #51760

Docs

  • Switch a comment in WP_Media_List_Table::prepare_items() to multi-line format, per the documentation standards – #52025
  • Revert documentation change for wp_get_attachment_metadata() – #52196

Login

  • Enable filtering the back to blog link – #35449

Mail

  • Make sure the SMTP class is only required once if a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party requires wp-includes/class-smtp.php directly – #52369

Media

  • Remove unused refresh from _requery – #50025
  • Remove caching from filter by date in media library – #50025
  • Ensure that wp_get_attachment_metadata can return values from the global $post, if available – #52196

Menus

  • Add sticky footer to avoid duplicate save buttons – #51631

Plugins

  • Rotate the Updates icon in the adminadmin (and super admin) bar when performing inline updates on the Plugins screen – #51476

Posts, Post Types

  • Introduce new functions for determining if a post has a parent (has_post_parent()) and to fetch the post parent (get_post_parent()) – #33045
  • Introduce “Filter by date” and “Filter by categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.” as post type and taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. labels, respectively – #42421

Privacy

  • Ensure that exported user data reports can’t be found with directory listings – #52299

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.

  • Add batch image editing endpoints – #52192
  • Refactor rest_validate_value_from_schema into separate validation functions per-type – #52375
  • Introduce modified_before and modified_after query parameters for the posts endpoints – #50617

RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.

  • Address PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher/JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. errors when viewing autosave on imported posts – #31249
  • Generate correct number of columns in wp_text_diff – #25473

Robots

  • Add max-image-preview:large directive by default – #51511

Security

  • Allow short-circuiting the wp_update_https_detection_errors() process – #47577
  • Improve accuracy in messaging about HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. support – #47577

Site Health

  • Update the language around how PHP should be updated – #52327
  • Update php update strings to not overpromise performance – #52327
  • Only run the version checks on the main site – #52135

Taxonomy

  • Declare and document the sort and args properties of the WP_Taxonomy class – #52142

Upgrade/Install

  • Display correct message about the current version in the admin footer – #51976
  • Allow WordPress sites to opt-in to development releases – #51978

Users

  • Enable admins to send users a reset password link – #34281

Props

Thanks to everyone who contributed to WordPress Core on Trac last week:

@audrasjb (16), @SergeyBiryukov (10), @xkon (7), @hellofromTonya (6), @Mista-Flo (5), @afercia (5), @johnbillion (5), @adamsilverstein (5), @TimothyBlynJacobs (4), @sabernhardt (4), @whyisjake (4), @johnjamesjacoby (3), @joedolson (3), @timothyblynjacobs (3), @afragen (2), @kburgoine (2), @maxpertici (2), @garrett-eclipse (2), @DrewAPicture (2), @Clorith (2), @flixos90 (2), @peterwilsoncc (3), @poena (2), @teamdnk (2), @birgire (2), @hedgefield (2), @paaljoachim (2), @wonderboymusic (2), @knutsp (2), @mdwolinski (1), @cfinke (1), @melchoyce (1), @claytoncollie (1), @chanthaboune (1), @dilipbheda (1), @isabel_brison (1), @yakimun (1), @talldanwp (1), @youknowriad (1), @oellin (1), @mukesh27 (1), @freewebmentor (1), @lucasbustamante (1), @alexstine (1), @francina (1), @karmatosed (1), @engahmeds3ed (1), @notlaura (1), @danfarrow (1), @Boniu91 (1), @drw158 (1), @ravipatel (1), @Joen (1), @ibdz (1), @jeremyfelt (1), @zodiac1978 (1), @mehulkaklotar (1), @aaribaud (1), @Ipstenu (1), @dd32 (1), @gziolo (1), @gunnard (1), @eventualo (1), @ericlewis (1), @JoshuaWold (1), @iseulde (1), @ramiy (1), @sebastianpisula (1), @desrosj (1), @ajlende (1), @manzoorwanijk (1), @noisysocks (1), @pbiron (1), @azaozz (1), @nicolalaserra (1), @ebinnion (1), @Chaton666 (1), @nosolosw (1), @kebbet (1), @jeffr0 (1), @swissspidy (1), @mrahmadawais (1), @jdgrimes (1), @obenland (1), @Monika (1), @imath (1), @helen (1), @joostdevalk (1), @tweetythierry (1), @westonruter (1), @pinkalbeladiya (1), @davidbaumwald (1) and @greatsaltlake (1)

Please welcome our 8 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@teamdnk, @oellin, @engahmeds3ed, @aaribaud, @gunnard, @nicolalaserra, @pinkalbeladiya and @greatsaltlake.

Core committers: @sergeybiryukov (12), @whyisjake (5), @johnbillion (4), @antpb (4), @joedolson (4), @timothyblynjacobs (4), @adamsilverstein (3), @flixos90 (3), @ryelle (2), @noisysocks (2) and @peterwilsoncc (1).

Please note: it only includes commits with proper props attribution.

#5-6-1, #5-7, #week-in-core

Winstina 7:42 pm on January 28, 2021
Tags: 5.6.1, ,   

WordPress 5.6.1 RC1

WordPress 5.6.1 Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 (RC1) is available for you to test!

Here are two ways to test WordPress 5.6.1 RC1:

  • Use the WordPress Beta Tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (select the point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. nightlies option)
  • Download the release candidate here (zip)

What’s in this release candidate?

5.6.1 Release Candidate 1 features 20 bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes and small enhancements, as well as 7 bug fixes for the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor.

WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. changes on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:

  • #51056: Fetch_feed parsing of permalinks triggers simplepie preg_match warnings
  • #52327: Requested updates to the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher Update Alert
  • #51940: The schema for the taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. property of a term in the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. should not include all taxonomies
  • #51980: App Passwords: ‘Add New Application Password’ submit button is hidden on mobile devices in ‘User Profile’ page
  • #51995: WordPress 5.6: Classic editor menu is not sticky
  • #52003: Undefined index: PHP_AUTH_PW /wp-includes/user.php on line 469
  • #52013: Duplicate wp_authorize_application_password_form actions
  • #52030: Media metaboxes return fatal error if no author metadata present
  • #52038: Issue in WooCommerce with wp_editor() after update to WP 5.6
  • #52046: The Distraction Free Writing setting on the old Edit Post screen may be reset after page reload
  • #52065: Media gallery: ‘Align’ and ‘Link To’ fields missing from ‘Insert from URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org’
  • #52066: Application Passwords are unusable in combination with password protected /wp-adminadmin (and super admin)
  • #52075: Word Count on Classic Editor doesn’t update in real time on Firefox unless saved
  • #52097: Site Health Loopback Test doesn’t send admin cookies
  • #52135: False positive on `WP_Site_Health_Auto_Updates`
  • #52196: wp_get_attachment_metadata() is broken if no first argument is passed in.
  • #52205: REST API: Plugins Controller single plugin route fatal errors on multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site
  • #52299: Exported user data can be listed with directory listing
  • #52351: missing echo function for translate method
  • #52391: GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Updates for 5.6.1

Block editor changes from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/:

  • #27970: Fix editor crash when registering a block pattern without categories
  • #27733: Embed block: Add htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. and reusable support back
  • #27727: Add aria labels to box control component inputs/button
  • #27627: HTML Block: Fix editor styles
  • #27526: Core Data: Normalize _fields value for use in stableKey
  • #26705: Fix: Font size picker does not correctly handles big font sizes.
  • #26432: Edit Site: prevent inserter overscroll

What’s next?

The dev-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) is now in effect when making any changes to the 5.6 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

As per the proposed WordPress 5.6.1 schedule, the final release is expected for Wednesday, February 3, 2021, before or after the weekly devchat. Please note that this date/time can change depending on possible issues after RC1 is released.

#5-6-1, #minor-releases, #releases

Jb Audras 1:25 am on January 28, 2021
Tags: 5.6.1   

WordPress 5.6.1 maintenance release schedule

After WordPress 5.6 “Simone” was released, some tickets were opened reporting identified bugs, mostly concerning bundled themes.

Given the need for a fast-follow WordPress 5.6.1 release before the end of 2020 was ruled out as no tickets were identified as urgent, the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team decided to update Twenty Nineteen and Twenty Twenty-One Bundled Themes independently from WordPress Core.

Now, it’s time to merge these changes into a new WordPress minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. and to address the other tickets that have appeared in the meantime.

WordPress 5.6.1 milestone currently contains 22 bundled themes patches plus at least 23 other bugfixes reported after WP 5.6 was released.

The following release schedule is being proposed:

  • Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).: Thursday 28 January, 2021 around 17:00-19:00 UTC
  • Final release: Wednesday 3 February, 2021, after the weekly devchat

The full list of the tickets targeted for this maintenance release is available on the 5.6.1 tickets report on Trac.

#5-6-1

Jb Audras 11:58 pm on January 25, 2021
Tags: 5.6.1, ,   

A Week in Core – January 25, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 18, 2021 and January 25, 2021.

  • 22 commits
  • 31 contributors
  • 50 tickets created
  • 7 tickets reopened
  • 47 tickets closed

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

App Passwords

  • Extract Basic Auth check into a reusable filterable function – #52066
  • Use correct translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. function for a heading on Authorize Application screen – #52351

Blocks

  • Add automatic RTL handlind for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. styles registered from metadata – #52301
  • Blocks: Add i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. support to register_block_type_from_metadata – #52301

Bundled Themes

  • Twenty Twenty-One: Consistently use Yoda condition for display_title_and_tagline setting – #52329
  • Twenty Twenty-One: Add missing HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. comments for </header> tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) – #52328
  • Twenty Twenty-One: Add missing styles for <button> element – #52029
  • Twenty Twenty-One: Clean up Button styles – #51927

Docs

  • Correct default value for the number argument of wp_tag_cloud() – #52348
  • Document globals in dropdown_categories() and dropdown_link_categories() – #41504
  • Docs: Fix typo in WP_Links_List_Table DocBlockdocblock (phpdoc, xref, inline docs) – #52349

Export

  • Create an export-specific filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. for post titles – #52250

External Libraries

  • First pass at fixing jQuery deprecations in WordPress core and bundled themes – #51812

Media

  • Ensure get_post_status() does not contain half a comment – #52326
  • Ensure get_post_status() returns correct result for attachments – #52326

Menus

  • Fix linting errors introduced in [50013] – #52189
  • Make use of wp_resolve_post_date() when updating menu items – #52189

Posts

  • Create a new function for resolving the post date – #52187

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.

  • Support type coercion when validating the enum JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. Schema keyword – #51911
  • REST API: Support embedding links in rest_preload_api_request() – #51722

Robots

  • Introduce Robots APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. – #51511

Toolbar

  • Update Documentation and Support links – #52352

Upgrade/Install

  • Display version number on the “Re-install now” button on WordPress Updates screen – #51774

Props

Thanks to everyone who contributed to WordPress Core on Trac last week:

@audrasjb (5), @jmdodd (3), @SergeyBiryukov (2), @mukesh27 (2), @TimothyBlynJacobs (2), @poena (2), @ocean90 (2), @pawki07 (2), @swissspidy (2), @timothyblynjacobs (2), @megphillips91 (1), @scruffian (1), @flixos90 (1), @peterwilsoncc (1), @allancole (1), @slaFFik (1), @afragen (1), @westonruter (1), @azaozz (1), @adamsilverstein (1), @freewebmentor (1), @Clorith (1), @akramipro (1), @spacedmonkey (1), @lpawlik (1), @aaroncampbell (1), @archon810 (1), @SeBsZ (1), @umangvaghela123 (1), @yakimun (1) and @aristath (1).

Please welcome our new Core contributor of the week ♥️ @akramipro

Core committers: @sergeybiryukov (11), @pento (3), @timothyblynjacobs (3), @peterwilsoncc (2), @gziolo (2) and @flixos90 (1).

#5-6-1, #5-7, #week-in-core

marybaum 6:50 pm on January 22, 2021
Tags: 5.6.1, , , , ,   

Dev chat summary: January 21, 2021

The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team postponed the afternoon dev chat for 24 hours to get past the US presidential inauguration. @metalandcoffee, aka Ebonie Butler, led the meeting on this agenda.

Announcements and highlighted posts

@metalandcoffee brought the group’s attention to these items:

Ebonie also invited the group (and you, too, dear reader!) to stop by a 5.7 test scrub. There’s one every Friday at 13:30 UTC.

Releases

The Core team is busy with one minor and one major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.

WordPress 5.6.1

5.6.1 has a squad and is deciding on a date; here are the tickets for the milestone.

WordPress 5.7

BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 lands on February 2. Here are the tickets in the milestone.

Per @hellofromtonya, aka Tonya Mork, noted there are 66 open features and enhancements that need committing or punting by Beta 1. (Ed. note: Beta 1 imposes a feature freeze on the release. After that, commits are bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes only. RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 imposes a string freeze, so Polyglots can finish translations before final release.)

Tonya had more to share about the milestone tickets. See the full discussion and consider pitching in on some tickets, especially, as @metalandcoffee pointed out, if there’s something you really want to see in the release.

Updates from component maintainers

@sergeybiryukov kicked off the updates with a general announcement that as of January 21, WordPress Core has more than 50,000 commits and thanked every past, present and future contributor.

Sergey also reported in for Polyglots, which added support for Austria to remove_accents() in #49967.

@audrasjb reported in that Menus has two tickets ready for commit. In Upgrade/Install, JB recognized @dd32, aka Dion Hulse, for his helpful insights on rollbacks.

In Design, @estelaris, aka Estela Rueda, asked for testing to review this Core color-change pull request, based on a discussion in the Design channel that was happening at the same time as devchat.

@xkon reported in from Privacy, saying he’s pretty sure they’ll be punting some tickets from 5.7 that need more iteration. The team also expects inputs from other teams, which happens a lot with privacy.

Agenda comments

jQuery UIUI User interface and #52163

Between standard reports and Open Floor, devchat takes up items people add to the comments on the Agenda post—and other items people specifically add.

That happened with a question @hellofromtonya had on ticketticket Created for both bug reports and feature development on the bug tracker. #52163, which is about updating jQuery UI and removing jQuery migrate. All of that is getting punted to 5.8, but at the moment there’s no firm timeline for the new jQuery UI release. Follow the discussion as it happened here.

Consolidating instructions for local dev environments

Across the WordPress Project you can find several sets of instructions that will walk you through setting up a local development environment for building WordPress sites, themes, and plugins; contributing to all of those things plus Core; and doing lots of different kinds of testing.

Those local-environment instructions vary widely in age, approach and tooling.

@paaljoachim has started a Meta ticket (as opposed to a normal ticket) to discuss consolidating those instructions and would very much like feedback, comments and people to brainstorm with.

So far, @desrosj and @hellofromtonya have offered help. But this is a big, complicated thing — so please pitch in!

WordPress Importers

@pento offers this proposal to modernize the WordPress Importers, complete with a slew of links.

As he told the group, “

There’s a lot to read, but I’d appreciate folks taking the time to go through it. :slightly_smiling_face:2:44Much of it is fairly sensible, but the last post in the series does contain a proposal for writing exporters for CMSes that don’t provide an export option, which is a departure from our usual approach.”

See the real-time discussion here.

Visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. tests

@isabel_brison has a pull request that sets up visual regression testing in Core. The TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket is #49606.

@francina raised the point that some hosts are starting to do visual regression. See that discussion here.

BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based navigation

@metalandcoffee: “Daniel Richards wanted to let everyone know that work on the block-based Navigation screen has picked up again, and there’s a new channel for [it] ” — #feature-navigation-block-editor.

Here’s the GitHub project.

Thoughts on browser versions?

@desrosj would like some feedback on #52331: Consider using more precise browser versions for `browserslist`.

Open Floor

@sergeybiryukov reminded the group that Beta and RC releases used to come with a haiku. He wrote one for the 50,000th commit and would like Core to restart the tradition.

@metalandcoffee volunteered to do a haiku for Beta 1 and closed the chat.

#5-6-1, #5-7, #core, #dev-chat, #summary