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 the newer 3.3.1 version.
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, and features previously marked as deprecated are no longer available.
When testing the changes, it is recommended to have SCRIPT_DEBUG defined and set to true, this will load jQuery Migrate in debug mode, and output stack traces in your 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/. 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.
With 5.6 officially kicked off, time to schedule the 5.6 sessions. These 5.6 specific ticketticketCreated for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.
Check this schedule often, as it will change to reflect the latest information.
Past Scrubs:
11/9/2020 19:00 UTC day before 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. 4
11/5/2020 15:00 UTC focus: 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. scrub
What about recurring component scrubs and triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?
The above 5.6 scheduled 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. scrubs are separate and in addition.
For your reference, here are some of the recurring sessions:
Design Triage: Every Tuesday 14:00 UTC in the #design channel (for both coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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/).
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) Scrub: Every Friday 14:00 UTC in the #accessibility channel.
APAC-friendly Scrub: Every Tuesday at 05:00 UTC in the #core channel. This scrub will continue during the cycle, alternating focus between core and editor.
Testing Scrub: Every Friday 13:30 UTC in the #core channel.
Want to lead a bug scrub?
Did you know that anyone can lead a bug scrub at anytime? Yes, you can!
How? PingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me (@hellofromtonya) 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/. and let me know the day and time you’re considering as well as the report or tickets you want to scrub.
Planning one that’s 5.6-focused? Awesome! We’ll add it to the schedule here along with your name. You’ll get well deserved props in the weekly Dev Chat, as well as in the #props Slack channel!
Where can you find tickets to scrub? All open tickets for 5.6, in order of priority, can be found here. Tickets that haven’t seen any love in a while are in particular need. Those can be found in this query.
Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the core handbook.
Questions?
Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to me (@hellofromtonya) on slack.
The following is a summary of the weekly media component meeting that occurred on Thursday, November 5, 2020 at 15:00 UTC. Weekly media meetings are held every Thursday at 15:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.
@mista-flo mentioned two tickets that were not included in the 5.6 milestone but should have. These have been committed as of today.
#39968 – Media Library: deleting all items on the last page loses the pagination/navigation buttons and shows message – The ticketticketCreated for both bug reports and feature development on the bug tracker. is related to existing changes in 5.6 and wasn’t added to the milestone. This has been reviewed and committed.
#51396 – [Media upload.php] Switch back from grid to list mode reopen the modal – Consensus from those present in the media meeting was that this was a safe change to include in the 5.6 milestone. It has since been committed.
Because there wasn’t time to complete the agenda item to review new tickets that require attention, @antpb is proposing 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. scrub away from the regular meeting times. The list has grown quite a bit, so any assistance is appreciated! Please leave a comment below with a time that works for you.
In particular, test different use-cases of the feature:
New installation for minor version
New installation for major version
Upgrade for major version
On single and 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.
If you want to contribute to this feature by testing, please join us and share your valuable feedback.
You can read more about auto-updates status and progress on two recent blogblog(versus network, site) posts
WordPress 5.6 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. 4 (coming out later today)
This meeting will be held in the #core-css channel in the Making WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
If there’s any topic you’d like to discuss, please leave a comment below!
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)
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. 4 pushed back WordPress 5.6 Beta 4 delayed from November 10th to November 12th, 2020 – Make WordPress Core – due to Auto update changes (see below)
These are the weekly notes for the Updates/Install component meeting that happened on Tuesday November 10, 2020. You can read the full transcript on the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.-auto-updatesSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.
The meeting was focused on the component’s major project for 5.6: an UIUIUser interface for opting in to core auto-updates. The feature was merged into core at the end of the alpha cycle of WordPress 5.6, when ticketticketCreated for both bug reports and feature development on the bug tracker.#50907 was committed.
As per the post previously published by @chanthaboune on Make/Core, there will be some changes in core auto-updates scope for WordPress 5.6.
Here is our goals for WP 5.6:
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, default behavior will change: opted-in to minor updates by default and opted-in to major updates by default.
On Monday 9, @audrasjb opened two tickets/patchs to handle those changes:
#51742: Make sure constants and filters are disabling the major auto-updates option
#51743: Auto-updates for major version is set by default to true for fresh installations
Both tickets can be merged independently. For the moment, ticket #51742 doesn’t address any UI change.
During the last devchat, @helen shared some concerns about the UI overload caused by the changes introduced in #50907. @karmatosed worked on some mockups to simplify the current interface. The intention is to get rid of the auto-updates section and to replace it with an action link when auto-updates are already activated:
After discussing those changes, the team agreed to consider using action links for both enable and disable actions, for better consistency. Indeed, it wouldn’t be great to have a full auto-updates section with a checkbox for enabling the feature, and a simple action link moved to the top of the screen to disable it. Replacing the section with a simple action link could also eases the burden caused by the multiple buttons on this screen.
Next steps until WP 5.6 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. 4 scheduled on Thursday:
Enabling auto-updates by default for fresh installs is a small 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., and it’s ready to be committed in ticket #51743
Taking into account constants/filters was already done in ticket #51743, but not committed yet.
[TODO] UI changes:
@audrasjb to update the patch in ticket #51743 to transform the form/checkbox interface to action links located in the main section on the top of the update-core screen.
@pbiron also raised ticket #50870 and @hellofromtonya provided some feedback after the office hour to help this ticket to move forward. The ticket is now marked as ready for commit.
Thank you to all of the contributors who tested 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. releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.
Project board to track issues for inclusion in WordPress 5.6.
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.3
The pace is increasing on the Full Site Editing related work, now FSE themes don’t need the experimental flag to work properly. A warning message about the experimental state is shown in the adminadmin(and super admin).
I expect some of us to focus more on template parts and templates auto-draft behavior (how to load theme templates and templates parts in the site editor).
I believe other folks are also working on the UIUIUser interface and the Query 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..
Bunch of fixes and tweaks for some minor issues related to the navigation sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. and template parts.
Here is an attempt to create wp_templates entries on theme updates instead of on each APIAPIAn 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. request
We started a new and simplified version of framework PR for introducing a custom status for templates provided by themes (or plugins) as HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. files, which haven’t been customized by the user yet
We now support other units and fluid typography on font size presets.
We now use the block settings on each global styles panel.
We now reference the preset variables on global styles so if for example global background color is set set to color X, and later we change color X, the background color also changes.
The UI is improved and we don’t show block panels without content.
We should have font family picker in the next few minutes (just finishing a last round of tests)
For Global Styles the current focus is on tighten up things and fixing the flows, specially by testing what we have with the TwentyTwentyOne blocks theme.
Task Coordination
Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.
I am also playing with taking screenshots of all e2e failures 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/ CI.
I’m also thinking about 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. for the APIs introduced on WP 5.6 and hoping to find time to write these next week. I believe we should start publishing some of the block editor dev notes.
I’m trying to do some PR trashTrashTrash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. pickups as go and level up my skills there, thank you to everyone that has supported me (special calls to @itsjonq and @joen) Also continuing to work on options and going to post some flow updates to that this week.
Release continues, so I’m also navigation around that.
Quieter week for me, Working with others on communication for 5.6.
some light triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. for unlabeled items, and some quick FSE focused testing.
Allow editing of extracted 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. in Post Excerpt block
Iterated and merged support for other units and fluid typography on font size presets.
Iterated and merged PR to use the block settings on each global styles panel.
Iterated and merged PR to reference the preset variables on global styles so if for example global background color is set set to color X, and later we change color X, the background color also changes.
Submitted and merged PR to don’t show block panels without conten
Rebased and Iterated on font family picker in the next few minutes (just finishing a last round of tests).
Reviewed multiple PR including the moment removal PR.
Submitted multiple small fixes/enhancements to Global styles
For the next week, I plan on testing 2021 blocks deeply with global styles and submit fixes either for the theme or to Gutenberg. I plan to continue the typography work with font weight and recheck a possible font loading global styles API.
Asked what’s the best way to register block for particular post type.
Current option is to loopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. through blocks and unregister undesored blocks for the posttype.
Some discussion around defining posttype via block.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. but no decision.
Hey Core contributorsCore ContributorsCore 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.! Last week in 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 was a lively (and lengthy) discussion on the auto-updates UIUIUser interface (transcript). This post summarizes the discussion and most reasonable options for moving forward, considering timing, availability, and level of effort for suggested changes.
Summarized Concerns
Is this implementation aligned with our long term goals: to have auto-updates widely available in order to increase the collective health of all WordPress sites, minimize the maintenance burden for users, and have greater security across the entire ecosystem.
Is this implementation aligned with our short term goals: to continue our existing progress around auto-updates for minor releases, plugins, and themes.
A desire to avoid reverting elements of the UI and auto-updates after the release.
There were a vast array of concerns around the implementation.
Path Forward
One of the clearest things that came up in the conversation during coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. chat is that this is a complex technical task, and there will be a need for some long term, dedicated time to keep driving this work forward. Specifically, there is a shared concern that there is a technically non-trivial combination of reassurance and repair features that need to be defined and executed on and will need a dedicated product owner (transcript).
This Release and Next
WP5.6: Provide some updates to the design of the UI.
WP5.6: 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).
WP5.6: For new installations, default behavior will change: opted-in to minor updates by default and opted-in to major updates by default.
WP5.x: In a future release, have a renewal flow after a certain period of time.
Planning for the Future
The subject of auto-updates has resulted in many complicated discussions. As I reminded the release squad, decisions like these require us to remember that we’re contributing to over 30% of the web, and we have to balance our immediate needs with long term planning.
It’s important that whatever we implement isn’t taking us further away from our long term goals of having seamless, auto-updates across the project. Auto-updates can help us have a more secure WordPress ecosystem, and in turn can help change the public perception of WordPress being an unsecure choice for users of any skill level.
To provide some clarification on the nine project goals set out in 2019, the wording there is specific about implementing “opt-in to automatic updates of major Core releases”. However, the long term goal (for Matt as well as many of the contributors to WP3.7) was to have all installations opted-in to auto-updates of WordPress core by default, and that is still the long term goal.
Props to the WordPress 5.6 release squad for bringing such care to this discussion, and to @helen for helping me on the implementation wording. Special thanks to @audrasjb and @davidbaumwald for editing, and @andreamiddleton, @daisyo, and @cbringmann for proofreading!
During the November 4th core chat, some questions were raised about the readiness of the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. auto-update feature, scheduled to land in WordPress 5.6. Questions ranged from the implementation of it to the scope of the output desired. A separate post is coming with more information on that discussion and the planned next steps.
In order to allow some more time to refine the work done so far, WordPress 5.6 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. 4 will be delayed from today, November 10th, to Thursday, November 12th, 2020.
At this moment, no delay is expected on the release: everyone is working to make WordPress 5.6 available on December 8th.
Thank you to @francina who helped me craft this draft. 🙂
WordPress 5.6 is closing in on 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. 4, and we are at a point where a final decision needs to be made about whether to include the Dark Mode functionality in the default theme, or whether it should ship separately in 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.
With this post, we are asking for your feedback, and ways that we can improve the user experience.
Since the last discussion, the Dark Mode functionality has been placed back into the theme to make it easier to test.
Two test scrubs have been completed and we have listened to the feedback and tried to make the setting easier to use.
Changes include:
Dark Mode Support is opt-in.
The button used to turn Dark Mode on or off was removed from 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.
In the 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. and on the front, the button is now placed at the bottom right (left on RTL). The button is hidden when you scroll down to not distract from reading.
We renamed the Customizer section to “Colors & Dark Mode” to make the setting easier to find.
The description in the Customizer was updated and includes a link to the themes support page.
A notice in the Customizer has been removed.
The Privacy Policy has been updated with information about LocalStorage.
Dark Mode Walkthrough
To test the latest changes, you need to download the development version of the theme from the GitHub repository.
Install and activate the theme. The colors will be the default mint green background and dark text.
Go to the Customizer and open the Colors & Dark Mode panel:
Here you can customize the background color. If the background is light, a dark text color is used.
If the background is changed to dark, the text color is white and the Dark Mode Support option is hidden.
The Dark Mode Support option is opt-in. When the option is enabled:
The colors respects the device settings.
A new button is visible on the front and in the Customizer. This button is used to turn Dark Mode on or off. This means that site owners and visitors can choose their preference independent of their device settings.
The same colors are used on the front, editor, and Customizer.
When Dark Mode is on, a dark grey background color is used. Images and borders also have a lower contrast.
When Dark Mode is off, the color in the background color option is used for the light background.
Monthly Plan for November 2020 and key project updates. With focus on issues, what is being done and help that is needed.
Global Styles.
Widgets screen.
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.
Full Site Editing.
Task Coordination
Open Floor
Even if you can’t make 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.
