The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in our bug tracker.
We use Slack for real-time communication. Contributors live all over the world, so there are discussions happening at all hours of the day.
Our core development meetings are every Wednesday at 05:00 UTC and 20:00 UTC in the #core channel on Slack. Anyone can join and participate or listen in!
The first step was included with WordPress 5.5, which stopped enabling jQuery Migrate version 1.x by default.
As part of #50564, part two of this process was committed, which updated the bundled jQuery version to 3.5.1. Alongside this, jQuery Migrate was also updated to version 3.3.2.
For the duration of WordPress 5.6, the migrate script will remain enabled by default, to capture any unexpected uses of deprecated features.
Do note that the Migrate script for version 3 is not compatible with features that the previous migrate script provided a polyfill for. The features that previously were marked as deprecated are no longer available. The purpose of jQuery Migrate version 3.3.2 in WordPress 5.6 is to help with updating (migrating) all jQuery based JavaScriptJavaScriptJavaScript 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/. from jQuery version 1.12.4 to 3.5.1.
When testing the changes, it is recommended to enableSCRIPT_DEBUG. This will load jQuery Migrate in debug mode, and output stack traces in your JavaScript developer console.
As this is a major upgrade to the jQuery library, please make sure you test your plugins and themes as thoroughly as possible before the release of WordPress 5.6 to avoid any preventable breakage.
The jQuery Core Upgrade Guide provides details on what features are deprecated, and removed, and how to upgrade your code accordingly.
WordPress updates for CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., plugins, and themes are based on a number of Core classes:
Alongside these main classes are several other update-related classes and functions, including those for updating translations.
Which updates are we talking about?
The ability to manually update WordPress from the adminadmin(and super admin) area, and to install and update plugins and themes, has existed since 2.3 in 2007.
Auto-update features were added in WordPress 3.7 (for minor releases), extended in 5.5 (as opt-in for plugins and themes), and 5.6 (major releases). To make the user experience of auto-updates even better, and build trust with users and extenders, it’s important that this mechanism works well and provides all the failsafe checks needed.
The WordPress Core update has proven to be generally reliable, but it doesn’t actually have many tests nor is well documented. There are also some reliability concerns around adding new files and the overall number of changed files, which is the reason WordPress currently tries to keep the number of changed files in minor releases to a minimum.
Plugins and themes updaters are older: in general, all of them can be improved.
Why now?
With the introduction of auto-updates, these processes are run even more often. So relatively small issues get triggered more often, and with that become a bigger problem. They also now more often run unattended: an auto update that breaks could lead to quite problematic results.
As one of the most widely used plugins in the WordPress ecosystem, we have already experienced some pains related to these processes. That, combined with the fact that these processes will now trigger more often, made us decide to actively work on these issues. We believe that other pluginPluginA 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 and themes authors have gone through the same experiences and we hope they, and other interested people, will join us in this effort of updating the updater.
What are we working on
We are combing through TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. to find all open tickets: start with Core, then move to Plugins and eventually Themes.
We are reviewing all the classes involved to make sure their code is efficient and if there is room for improvement.
What are the next steps
This is a big project, one that can help other thousands of companies, so I hope you will join us in the effort. We have created a GitHubGitHubGitHub is a website that offers online implementation of git repositories that can 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/ repository under our company account. There, you will find a project board where we are documenting and managing all we are doing. Once the research part is over, and the steps to take to improve the updaters are clear, we will start weekly meetings in #core or a dedicated channel.
Timeline
January 2021 – February – Research and proposal phase
Color Scheming (#49999) – Visual RegressionregressionA 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. Testing (#49606)
The meeting was facilitated by @thewebprincess while @thelmachido took notes. Full meeting transcript on slack. Both groups followed the pre-prepared agenda
Highlighted Posts
A week in Core. Take a look at what changed on TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between November 16 and November 23, 2020
WP release cycle. If you work for a company whose product is influenced by WordPress releases, you are encouraged to join the discussion about aligning the WP release cycle with industry standards
PluginPluginA 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 and themes developers releases depend on CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., so it’s important that extenders reply.
With the 5.6 release scheduled for December 8th, let’s start planning for 5.7. What’s on your wish-list for version 5.7
The marketing team are starting working on ‘the Month in WordPress in their weekly meeting, please reach out if you have any contributions to share.
Last but not least, the PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 dev notedev noteEach 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
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. is now published. Folks are reminded to continue testing PHP 8
Component maintainers and focus leads
PHP 8 Dev Notesdev noteEach 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
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. @sergeybiryukov advised that PHP 8.0 release is scheduled for November 26. The dev note does a great job summarizing the changes and challenges PHP 8.0 brings for WordPress core and plugin or theme authors, so give it a read. There are a few components without a maintainer, and some that could use more maintainer support, a challenge was raised to people to consider contributing in this way, it’s not as hard as you might be thinking! See the discussion here and pick a component to dive into.
Open Floor
The Marketing Team is working on a social media pack on version 5.6, if anyone would like to support this, please let @lmurillom or @abhanonstopnewsuk know. Follow the conversation on slack
Questions and answers for version 5.6 Where uploaded yesterday on GithubGitHubGitHub is a website that offers online implementation of git repositories that can 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/. @abhanonstopnewsuk – “ l would like to thank everyone who has already helped with this from the release squad, core and marketing, and a big shout out to @vimes1984 and @meher who have led these questions and answers work with me over the last month.”
There are a number of tickets coming in since 5.6 RC1. @hellofromtonya will be scheduling a pre-RC2 Scrub Scheduled: Nov 30th @ 1900 UTC and will drop tickets into #core channel over the next few days to escalate.
GutenbergGutenbergThe 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.4.0 Recap
We reviewed @youknowriad‘s “What’s new in Gutenberg” post for November focusing mainly on the last major releasemajor releaseA 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. of Gutenberg 9.4.0. Highlights included:
Percentage widths for Buttons blockBlockBlock 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. buttons.
Ability to switch between block variations in the Navigation block once it is inserted.
Size support for Social Icons.
Font size support for the List Block.
Preparation for WordPress 5.6
WordPress 5.6 is due for release on the 8th December 2020.
Release candidaterelease candidateOne 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). #2 is due on 1st December.
As mentioned in previous meetings Beta 1 (October 20th) represented the cut-off point for new commits/features.
For Global Styles, focus remains on tightening up and fixing the flows, with the goal of preparing a v1 that can land as coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.patchpatchA 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. early in the 5.7 cycle.
Starting to think about how we can make alignments declarative (controllable by block containers and theme.jsonJSONJSON, 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.).
Widgets screen, Navigation screen and CustomizerCustomizerTool 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.
Updates on these projects were combined due to lower levels of activity. @andraganescu provided the update (also posted in the agenda):
work to improve the client side metadata and code, expose metadata wp-cliWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/ can use to know what parts of theme.json are translatable.
Will also review global styles related PR’s proposed by others.
Various bugbugA 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 including 5.6 issues.
light GitHubGitHubGitHub is a website that offers online implementation of git repositories that can 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/triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.,
Phase 1 tasks are created/tracked within the G2 Github repo. Tracking the next ones in the Gutenberg repo when it’s time. See this post for more information.
Working on the Featured ImageFeatured imageA 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. block flow.
@youknowriad asked if someone with a Windows environment could test it.
@frankklein queried the approach in the PR but @bobbingwide was happy with the current approach.
Issue with post-content and post-excerptExcerptAn excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. output in FSE
Looking for someone to help to resolve the problem.
Draft for What’s Next post for December?
@annezazu provided update on some items are currently on the list for the What’s Next post for December:
Addressing 5.6 feedback
Global Styles & Editor focused APIs
Full Site Editing (including Query Block)
WidgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Screen/editor
Requested input to gain clarity on current state of Widget Screen work.
@andraganescu agreed to provide the necessary information.
Automated “Welcome” messages in Core Editor SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.?
@annezazu suggested that it would be good to have some messages automatically sent to new people who join this channel.
Slack has a way to do that automatically.
Problem: any message sent to new people will unfurl the preview for certain links. Cannot disable this on a per-channel basis.
Might be regressionregressionA 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. / not in latest collection over broken.
As part of the 5.6 release, we’ll be hosting aRelease Candidaterelease candidateOne 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 focused test scrub on 11/27/2020 13:30 UTC in the #core channel on SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
There are tests for developers and users and depending on who will show up we decide on what we will work.
Tasks for developers
Tickets needing testing based on the TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. report https://core.trac.wordpress.org/tickets/needs-testing
Or, pick a component that you feel confident/passionate about, check what has changed before RC1 and continue testing to make sure that everything is still working.
To apply and test patches, you need a development environment.
Tasks for users
These are some of the test scenarios:
Upgrade to Release Candidate 1
Install Release Candidate 1 on a new website
Create a post or a page
Edit an existing post or page
Add, remove, edit users
Add, activate, deactivate, delete a a theme. From the repository or a zip upload.
Add, activate, deactivate, delete a pluginPluginA 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. From the repository or a zip upload.
Add, edit, remove a menu. Place it in a menu location and in a widgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user..
Edit your dashboard
Ecc…
What you need for user testing
A test website
WordPress 5.6 RC 1:
Try the WordPress Beta Tester plugin (choose the “Bleeding edgebleeding edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and BetaBetaA 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./RC Only” stream options)
This week we’ll be starting to plan the Privacy Components 5.7 milestone and would love your input. The overarching Roadmap will also be up for discussion.
GutenbergGutenbergThe 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.5 – will be released next week (1st Dec).
Monthly Plan for November 2020 and key project updates:
Full Site Editing.
Global Styles.
Widgets screen.
Navigation screen and Navigation blockBlockBlock 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..
CustomizerCustomizerTool 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. screen.
Task Coordination.
Open Floor.
If you can’t attend the meeting, you’re encouraged to share anything relevant for the discussion:
If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.
WordPress 5.6 introduces a new UIUIUser interface to allow website administrators to opt-in to major versions of automatic updates. As noted in a previous dev note, this feature follows the plugins and themes auto-updates user interface, which was shipped in WordPress 5.5. Both are part of the Nine WordPress Core projects for 2019-2020.
The scope of the feature changed during the BetaBetaA 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. phase of WordPress 5.6. This dev notedev noteEach 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
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. cancels and replaces the preceding one.
As announced by Executive Director @chanthaboune (see the related post below), the initial scope of CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. auto-updates has moved to:
Provide some updates to the design of the UI.
For existing installations, the behavior will remain the same as it is today: opted-in to minor updates by default, but a user must opt-in to major updates (constants and filters that are already in use by hosts or agencies will still take precedence).
For new installations, the default behavior will change: opted-in to minor updates by default and opted-in to major updates by default.
For more details about this decision and the roadmap for the next releases, please check the related post on Make/Core:
Major Core auto-updates UI changes in WordPress 5.6
How does it look?
The core auto-updates feature already exists for years in WordPress. WP 5.6 only introduces a new user interface to make it easier to opt-in to automatic updates for major versions.
By default, WordPress auto-updates itself, but only for minor releases. Developers can already opt-in to major releases auto-updates by setting up the existing WP_AUTO_UPDATE_CORE constant to true or by using the allow_major_auto_core_updates existing filterFilterFilters 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..
With WordPress 5.6, it’s possible for website administrators to opt-in/out to automatic updates for major versions, using a specific interface located on the Updates screen:
When the administrator clicks on the “Enable automatic updates for all new versions of WordPress” link, auto-updates for WordPress Core major versions are enabled:
It’s then possible to opt-out for major versions auto-updates by clicking the “Switch to automatic updates for maintenance and security releases only” link.
How to override the default settings using constants and filters?
This settings section adds some links to allow administrators to opt-in to major core auto-updates. But it also checks for any existing constant or filter and even to see whether the option should be available or not by default and whether it should be set up to enabled or disabled state, using the following order:
By default, auto-updates for major versions are:
Disabled for existing WordPress installations.
Disabled if a version controlversion controlA version control system keeps track of the source code and revisions to the source code. WordPress uses Subversion (SVN) for version control, with Git mirrors for most repositories. system is detected on the WordPress installation.
Enabled for fresh new installations.
If get_site_option( ‘auto_update_core_major’ ) returns true or enabled, auto-updates are enabled. Otherwise, they are disabled. This option is the one stored in the database when the UI is triggered. If this option is set, it overrides the above use cases.
If WP_AUTO_UPDATE_CORE constant returns true, beta, or rc, auto-updates are enabled. If the constant returns false, minor or is not defined, auto-updates are disabled. If this constant is set, it overrides the above parameters.
If allow_major_auto_core_updates filter returns true or enabled, auto-updates are enabled. If the filter returns false or is not used, auto-updates are disabled. If this filter is used, it overrides the above parameters.
To disable auto-updates for major versions by default, developers can set the WP_AUTO_UPDATE_CORE to false (to disable all auto-updates) or minor (to enable only minor core auto-updates, which is the default behavior). It has to be done using the wp-config.php file.
Developers can alternatively use the allow_major_auto_core_updates filter to set up core major versions auto-updates to true or false by default. Example:
In the following screenshot, auto-updates for major versions have been enabled programmatically using a filter or a constant:
In the following screenshot, auto-updates for major versions have been disabled programmatically using a filter or a constant:
How to extend the core auto-updates UI?
There is an action hook running right at the end of this settings section to add some options if needed. Using the after_core_auto_updates_settings action hook, developers can add other settings or texts.
For example, the following snippet adds a link to WordPress documentation about auto-updates.
function my_plugin_after_core_auto_updates_settings( $auto_update_settings ) {
?>
<p class="auto-update-status">
<?php _e( 'For more details about Core auto-updates, see <a href="https://wordpress.org/support/article/configuring-automatic-background-updates/">WordPress documentation</a>', 'my-plugin' ); ?>
</p>
<?php
}
add_action( 'after_core_auto_updates_settings', 'my_plugin_after_core_auto_updates_settings', 10, 1 );
WP 5.6 Field GuideField guideThe 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. – WordPress 5.6 Field Guide – Make WordPress Core
Dev Notesdev noteEach 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
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. continue to be updated ready for final release, here’s the latest dev-notes – Make WordPress Core
Calls from component maintainers and/or focus leads
Open Floor If you have something else you want to include to the agenda, please mention it in the comments below.
Welcome back to a new issue of Week in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between November 16 and November 23, 2020.
29 commits
76 contributors
72 tickets created
13 tickets reopened
129 tickets closed
TicketticketCreated for both bug reports and feature development on the bug tracker. numbers based on the Trac timeline for the period above. The following is a summary of commits, organized by component.
Code changes
Application Passwords
Regenerate the .htaccess file to add a new rule – #51723
Update the package.jsonengines to point to the new LTS versions of Node/NPM – #51749
Bundled Themes
Twenty Twenty-One: Sync the latest changes for 5.6 RC1 – #51526
CustomizerCustomizerTool 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.
Temporary fix for autosave restore notice not being removed
Add an early exit when calling RSS functions directly – #35835
General
Rename the wp_error_checked action to is_wp_error_instance for clarity – #40568
Code Modernization: Only call libxml_disable_entity_loader() in PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 < 8 – #50898
Help/About
Move trailing punctuation in the jQuery Migrate Helper pluginPluginA 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 link outside of the HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.tagtagA 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.) – #51813
Correct placeholder for the accessibilityAccessibilityAccessibility (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) statement feature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. link – #51415
Clarify accessibility features. Captions are uploaded in the blockBlockBlock 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, and not created in the editor. Avoid making an invalidinvalidA resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. claim of WCAGWCAGWCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.1 conformance or trivialize the efforts still required to build an accessible and compliant site – #51415
Internationalization
Avoid PHP notices for relative URLs in load_script_textdomain() – #49145
MultisitemultisiteUsed 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
More consistency for clean_dirsize_cache() – #19879
Permalinks
Prevent attachment pages 404ing following [49563] – #51776
Plugins
Check if _error_nonce is set before attempting to verify it – #43876
Make sure the HTML ID attributes for plugin checkboxes are unique – #51256
Site Health
Check if $core_updates is an array before iterating on it – #51818
Add missing i18ni18nInternationalization, 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. for the App Passwords documentation link – #51815
Upgrade/Install
Replace the conditionals that check the AUTOMATIC_UPDATER_DISABLED constant and the automatic_updater_disabledfilterFilterFilters 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. in update-core.php with a call to WP_Automatic_Updater::is_disabled(). This prevents a PHP warning, the logic, and considers wp_is_file_mod_allowed( 'automatic_updater' ) when determining the UIUIUser interface state – #51827
Consistent layout and accurate messages on the update screen – #51742
Users
Use do_action_ref_array() for pre_get_users and pre_get_terms actions – #50961
Props
Thanks to everyone who contributed to WordPress Core last week:
