Yearly Archives: 2023

Josepha 8:58 pm on October 12, 2023
Tags: , ,   

WordPress 6.4 Beta 4

WordPress 6.4 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. 4 is ready for download and testing!

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you test Beta 4 on a test server and site.

You can test this WordPress 6.4 Beta in three ways:

  • Option 1: Install and activate 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 “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/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). Only” stream).
  • Option 2: Direct download the Beta 4 version (zip).
  • Option 3: Use the following WP-CLIWP-CLI WP-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/ command: wp core update --version=6.4-beta4

The current target for the final release is November 7, 2023, which is just over three weeks away. Your continued help with testing is vital to ensuring everything in this release is the best it can be.

Get an overview of the 6.4 release cycle, and check the Make WordPress Core blog for 6.4-related posts in the coming weeks for further details.

This is an extra beta

Testing for issues is a critical part of developing any software, and it’s a great way to start contributing to WordPress—now more than ever. This detailed guide is a great place to start if you’ve never tested a beta release.

This beta is in response to the WordPress 6.3.2 Maintenance and Security release released today; more information can be found on that release’s post.

The 6.4 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). is still scheduled for Tuesday, October 17, but as always depends on your confirmation during testing. So please download and test.

Thank you to the following contributors for their support on this release: @hellofromtonya

#6-4, #beta, #releases

Andrei Draganescu 7:26 am on October 12, 2023
Tags: , , , ,   

Editor chat summary: October 11th, 2023

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel, on Wednesday, October 11, 2023, 14:00 UTC moderated by @andraganescu

Accouncements

Async key project updates

Read the latest updates directly from the following tracking issues:

Sync project updates

@annezazu shared that:

  • A new label (Feature: Data Views) helps track various work around improving views across the WordPress experience. An overview issue is here. This relates more broadly to wp adminadmin (and super admin) redesign efforts and a recent PR was merged as an experiment bringing this to the Site Editor > Manage all pages view.
  • There are two new 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/ > Experiments to explore: Live Collaboration and offline persistence (available in current version) & New admin views (coming in 16.8).

@glendaviesnz shared an update around:

  • getting the code mirror inline code editing added to the custom css input box in global styles via lazy loading. If anyone has any thoughts on lazy loading a large lib like this feel free to comment on the PR

Open Floor

@colorful-tones suggested the example used 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. HooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. 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. to be changed from the current “Like button” to something static so that developers do not end up confused as to wether they need to use interactive blocks for block hooks.

@fabiankaegy raised awareness on a current 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. affecting WordPress 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. release where in a query block only the currently selected block renders styling and other updates. The issue already has a PR but we need to make sure there is enough focus on this to get it solved before the release is shipped.

@luminuu

  • raised awareness on the fact that the recently merged “Replace template” option not visible with Gutenberg 16.7.1
  • inquired about the current status of the lightbox feature in relation to WordPress 6.4 release.

@artemiosans shared in response that there’s only a couple of bugs left (PR#55212 and PR#5461).

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.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Abha Thakor 10:53 pm on October 11, 2023
Tags: , , , ,   

Dev Chat summary, October 11, 2023

Summary of the WordPress developers chat meeting in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel.

Key links

Start of the Dev Chat meeting on the Core Slack

Dev Chat agenda followed – thanks to @webcommsat for preparing.

Announcements

  • WordPress 6.4 Beta 3 is available: Please help test and make the release the best it can be! Thanks to everyone who contributed toward 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, as well as those who came and facilitated the release party on October 10. Note the Twenty Twenty Four images issue has been resolved, and the images are rendering correctly in Beta 3.
  • The WordPress 6.3.2 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. has moved to tomorrow, October 12, 2023 (more information under release updates to follow).

Highlighted Posts

  • Four Weeks in Core: Many thanks to @audrasjb for this update covering the amazing activity in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between September 4 and October 9, 2023:
    • 269 commits
    • 337 contributors
    • 295 tickets created
    • 43 tickets reopened
    • 277 tickets closed
  • Reminder: Hallway Hangout: Working session on consolidating various navigation modes: Taking place on November 15, 2023 at 16:00 UTC. This is part of efforts to improve 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) in the Site Editor.
  • The Dev Blog is looking for a writer for the following topic: How to add commands to the command palette. Please respond on the 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 by the repository owner. https://github.com/ ticketticket Created for both bug reports and feature development on the bug tracker. if you are interested.

Release Updates

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.: 6.4

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 is scheduled for next Tuesday, October 17, 2023. 

This hallway hangout is happening tomorrow, October 12, 2023: What’s new for developers in WordPress 6.4. 

Stay in the loopLoop The 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 with 6.4 by following:

6.4 tickets that need attention

@rajinsharwar highlighted #52529 and requested testing of the 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. to see if they can replicate the errors mentioned.

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.

@webcommsat for the release documentation group: A reminder that 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. is due to be published next week. This is so the link can be included in the release’s About Page. It would be great to have as many dev notes ready in draft as soon as possible, so they can have a final review and be published.

6.4 dev notes tracking project board for reviews and publishing is in progress.

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/ – Some Gutenberg tickets have already been labelled and clustered. There is a significant list that is being clustered and labelled, and these will then get added to the documentation tracker for 6.4. The tracker will show the edit, review and publish status of the dev notes – the view that will be most useful for this is ‘dev notes’. For Gutenberg, the wrangling and discussion on clustering and inclusions will happen in the Gutenberg tracker. Thanks to @bph who is going to be helping with this.

Core – If you are a component maintainer, and have not already shared that you are working on a dev notedev 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. relating to a Core Trac ticket or cluster of tickets, please add a comment on this issue and link any google docs, and we will populate the tracker with this.

For End user and Core tickets, the labelling is continuing. As we are being advised of dev notes needed or in progress by maintainers, they are being added to the documentation tracker.

For performance dev notes, issues are being added to the documentation tracker once confirmed for reviews and publishing purposes. Wrangling and discussion of inclusion of tickets is happening on the Performance GitHub ticket.

Reviews – If any devs are able to assist with technical reviews of dev notes if needed, let @webcommsat know to update the list.

Next minor release: 6.3.2

  • *A note on the 6.3.2 release schedule change:* In order to accommodate the need for hosts to deal with an important curl 8.4.0 security release on Wednesday, the 6.3.2 final release has been moved to Thursday, October 12, 2023.
  • Thanks to everyone who led, supported, helped test, raised issues, and helped to fix tickets in these releases! 

Gutenberg

Gutenberg 16.8.0 shipped during dev chat. An update on this release will be published soon and will be findable on the 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.) #gutenberg-new on the Make/ Core blogblog (versus network, site).

Component Maintainers requests

@rajinsharwar highlighted Trac ticket #55335. Requested confirmation if it should be considered a 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..

Open floor

No additional items were raised. A reminder of the Field Guide and dev notes was shared.

Props to @webcommsat for the agenda and summary, and to @ironprogrammer for facilitating the meeting and reviewing the summary.

#6-3, #6-4, #dev-chat, #meeting, #summary

Vicente Canales 10:53 pm on October 11, 2023
Tags: , , ,   

What’s new in Gutenberg 16.8? (11 October)

“What’s new in 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/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Site Editor project (formerly called Full Site Editing).

Gutenberg 16.8 has been released and is available for download!

This latest release includes many enhancements, 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, some new experiments, and essential groundwork for the future Phase 3.

  1. Cover block: automatically set overlay color when applying the initial background image
  2. Show template toggle when editing pages
  3. Font Library: add an Uploads tab
  4. Other notable highlights
  5. Changelog
  6. Contributors

Cover 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.: automatically set overlay color when applying the initial background image

The Cover Block just got a bit smarter by setting an Overlay color based on the background image. The Overlay color is extracted from the image via magic (actually, code, which you can see coming into existence here (#54054).

Show template toggle when editing pages

This great new option allows you to see your Pages within the Template context where they’re meant to be displayed while you edit them. As @noisysocks puts it:

Allows users to focus on their content when desired. Moreover, it is small a step towards one day unifying the post editor and site editor.

– @noisysocks (#52674)

Font Library: add an Uploads tab

All about decluttering: font uploads have been moved to a separate tab within the Font Library interface. The team has also worked on improving error messages and their visibility.

Other notable highlights

  • Footnotes now make use of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. revisioning capabilitiescapability A capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). when available. Gutenberg PR (#52988) and Trac Ticket (#20564).
  • Experiment: the first version of the pages list in the site editor (#54966). This experiment is one of many pieces of the Data Views work (#55083), crucial for Phase 3.
  • Add template replace flow to template inspector (#54609).

Changelog

Features

Block Editor

  • Adds ‘nofollow’ setting to Button block. (54110)

Site Editor

  • Add ‘Show template’ toggle when editing pages. (52674)

Enhancements

  • Update pattern import menu item. (54782)

Components

  • Adding label/description to BlockEditor/DuotoneControl. (54473)
  • Deprecating isPressed in Button component. (54740)
  • Follow ariakit best practices. (54696)
  • InputControl-based components: Add opt-in prop for next 40px default size. (53819)
  • Modal: Add contentWidth prop to support a selection of preset modal sizes. (54471)
  • Remove unused components from ui/. (54573)
  • Update ariakit to 0.3.3. (54818)
  • Update compact search control metrics. (54663)
  • Wrapped TextareaControl in a forwardRef call. (54975)

Block Library

  • Add a brief description to the Footnotes block. (54613)
  • Footnotes: Use core’s meta revisioning if available. (52988)
  • Login/out: Add spacing support. (45147)
  • Query view.js: Code quality. (54982)
  • Set custom color when applying initial background image. (54054)
  • Use wp_get_inline_script_tag() in build_dropdown_script_block_core_categories(). (54637)

Block Editor

  • Default suggested links to pages. (54622)
  • Remove base URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org from link control search results. (54553)
  • Simplify BlockHTMLConvertButton. (54972)
  • Update strings in blocks ‘RenameModal’ component. (54887)

Post Editor

  • Edit Post: Use hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. instead of HoCs in ‘PostStatus’ components. (54951)
  • Editor: Use hooks instead of HoCs in ‘PostSticky’ components. (54949)
  • Editor: Use hooks instead of HoCs in ‘PostSwitchToDraftButton’. (54695)
  • Show confirmation dialog when moving a post to the trashTrash Trash 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.. (50219)

Site Editor

  • Add template replace flow to template inspector. (54609)
  • [Site Editor]: Update copy of using the default template in a page. (54728)

Patterns

  • Remove categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. description in inserter panel. (54894)

Typography

  • Font Library: Refactor endpoint permissions. (54829)

Bug Fixes

  • Fix the ShortcutProvider usage. (54851)
  • Fix warning when a template calls a template area twice. (54861)
  • Revert “Fix warning when a template calls a template area twice”. (54926)

Block Library

  • All Nav block items to break long titles. (54866)
  • Fallback to Twitter provider when embedding X URLs. (54876)
  • Fix Deleted Navigation MenuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. warning string. (55033)
  • Fix Search Block not updating in Nav block. (54823)
  • Fix left and right aligmnent in children of Post Template. (54997)
  • Fix output of Navigation block classnames in the editor. (54992)
  • Fix overwriting of published post meta when previewing footnote changes. (54339)
  • Image: Ensure Expand on Click toggle is shown if block-level lightbox setting exists. (54878)
  • Image: Fix layout shift when lightbox is opened and closed. (53026)
  • Media & Text: Fix ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org warning. (55038)
  • Search block: Allow space for input field only when form expanded. (54846)
  • Search block: Update alignment and icon button width. (54773)

Site Editor

  • Avoid same key warnings in template parts area listings. (54863)
  • Avoid stale navigation block values when parsing entity record. (54996)
  • Don’t display the navigation section in template parts details when a menu is missing. (54993)
  • Fix ToolSelector popover variant. (54840)
  • Reset ‘Show template’ toggle when leaving edit mode. (54679)
  • remove overflow: Hidden from the entity title in the site editor sidebarSidebar A 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.. (54769)

Components

  • FormTokenField: Add box-sizing reset style and reset default padding. (54734)
  • Popover: Fix the styles for components that use emotion within popovers. (54912)
  • Remove hover style for secondary Button when aria-disabled is set. (54978)
  • Reverting addition of aria-selected style hook in Button. (54931)
  • SlotFill: Pass Component instance to unregisterSlot. (54765)

Block Editor

  • Avoid double-wrapping selectors when transforming the styles. (54981)
  • [Inserter]: Fix reset of registered media categories. (55012)

Typography

  • Font Library: Changed the OTF mime type expected value to be what PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher returns. (54886)
  • Font Library: Move font uploads to a new tab. (54655)

Global Styles

  • Block custom CSSCSS Cascading Style Sheets.: Fix incorrect CSS when multiple root selectors. (53602)
  • Image: Ensure false values are preserved in memory when defined in theme.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.. (54639)

List View

  • Fix performance issue when selecting all blocks. (54900)

Colors

  • Format Library: Try to fix highlight popover jumping. (54736)

Interactivity 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.

  • Image: Fix duotone not being applied to lightbox image. (54670)

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)

Block Library

  • Footnotes: Add aria-label to return links. (54843)

Components

  • HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. block: Fix accessibility issues on back-end. (54408)
  • Modal: Accessibly hide/show outer modal when nested. (54743)

Patterns

  • Use list role instead of listbox in patterns list. (54884)

Post Editor

  • Editor: Always render the ‘Switch to Draft’ button to avoid focus loss. (54722)

Block Editor

  • Block Switcher: Use a different label for multi-selection. (54692)

Performance

  • Tests: Support the Site Editor’s legacy spinner. (54784)
  • Use instanceOf over property_exists. (54835)

Block Editor

  • Subscribe only to block editor store in useBlockSync. (55041)

Experiments

Site Editor

  • al]: First version of pages list in site editor. (54966)

Block Editor

  • Expose getDuotoneFilter() as private API. (54905)

Documentation

  • Add a documentation page about the block editor settings. (54870)

Contributors

The following contributors merged PRs in this release:

@aaronrobertshaw @adamsilverstein @alexstine @andrewhayward @andrewserong @annezazu @anton-vlasenko @artemiomorales @aurooba @bangank36 @brookewp @c4rl0sbr4v0 @carolinan @chad1008 @ciampo @dcalhoun @derekblank @draganescu @ellatrix @fluiddot @fullofcaffeine @geriux @getdave @glendaviesnz @gziolo @jameskoster @jeryj @jsnajdr @juhi123 @kevin940726 @leemyongpakvn @madhusudhand @MaggieCabrera @Mamaduka @matiasbenedetto @michalczaplinski @mirka @mtias @mujuonly @ndiego @noahtallen @noisysocks @ntsekouras @oandregal @ockham @pbking @priethor @ramonjd @richtabor @scruffian @SiobhyB @spacedmonkey @stokesman @swissspidy @t-hamano @tellthemachines @tellyworth @them-es @torounit @tyxla @westonruter @WunderBart @youknowriad

Props to @joen for the visual assets and @annezazu for the help reviewing and collecting highlights!

#block-editor, #core-editor, #gutenberg, #gutenberg-new

Abha Thakor 8:07 am on October 11, 2023
Tags: , ,   

Dev Chat agenda, October 11, 2023

(Updated with Four Weeks in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. 2023/10/11)

The next weekly WordPress developers chat will take place on Wednesday, October 11, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Further items will continue to be added as they come up in core and release leads channels on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

Welcome and housekeeping

All are welcome to join Dev Chat.

Summary of Dev Chat, October 4, 2023 – thanks to @webcommsat and to @ironprogrammer for review.

Announcements

WordPress 6.4 Beta 3 is available – please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed towards 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 and those who came and facilitated the release party on October 10. Note the Twenty Twenty Four images issue has been resolved, and the images are rendering correctly in Beta 3.

The 6.3.2 release has moved to October 12, 2023 (more information under releases below)

Highlighted posts

Due to time constraints during a release and to prioritize 6.4 items, some of the highlighted posts may not be raised during the live Dev Chat meeting.

Four Weeks in Core – props to @audrasjb, covering from September 4 to October 9, 2023

  • 269 commits
  • 337 contributors
  • 295 tickets created
  • 43 tickets reopened
  • 277 tickets closed

Core Editor improvement: ensuring excellence in the writing experience.

  • As part of these efforts in the 6.4 release cycle there have been improvements with new keyboard shortcuts, smoother list merging, some key fixes, and more. This post published @annezazu includes a video demonstrating some of these enhancements
  • Current efforts can be followed in this Gutenberg tracking issue 53305. 
  • Call to continue sharing directly any issues you’re running into, whether a 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. to fix or an experience to polish. 

Reminder: Hallway Hangout – working session on consolidating modes. November 15, 2023. This is part of efforts to improve 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) of the Site Editor.   

The Dev Blogblog (versus network, site) is looking for a writer for the following topic: How to add commands to the command palette – please add to the 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 by the repository owner. https://github.com/ ticketticket Created for both bug reports and feature development on the bug tracker. if you are interested.

Forthcoming release updates

Next major WordPress release: 6.4

Forthcoming milestone: October 17, 2023 – 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

Any calls relating to 6.4 tickets?

For information (note these are for information identified from discussions in core, and may have moved on by the time of Dev Chat. Please check the actual ticket for the latest updates. If there are other tickets / core discussions which you feel should be highlighted on the Dev Chat agenda, please add them in comments).

Update on the Fonts Library from October 4, 2023 from @hellofromtonya

template-parts revisions issue discussion 1 The discussion continued in this release leads message thread.

Discussion on font-apis on core in Slack

Last bug scrub in core Slack before RCs. Scrub took place on October 10, 2023

Discussion on post testing and commit for Trac Ticket #56922 in core Slack, October 11, 2023

Core-performance is relooking at a performance issue after a fix was applied in the last beta. Original slack thread in core. Summary from Core-performance meeting, October 10, 2023.

Existing 6.4 useful links

Release parties schedule for 6.4

This detailed guide will walk you through testing features in WordPress 6.4.

Roadmap to 6.4 – this release is scheduled for November 7, 2023.

Bug Scrub Schedule 6.4

6.4 Development Cycle

Project Board for Editor Tasks for WordPress 6.4 on GitHub

Next 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.: 6.3.2

Please follow the 6.3 release channel on Slack for updates.

WordPress 6.3.2 RC1 is available – from October 6, 2023. Please help test!

Note update from Oct 9: In order to accommodate the need for hosts to deal with the pending curl 8.4.0 security release on Wednesday, the 6.3.2 final release date will be delayed to Thursday, Oct 12, 2023.

A special thanks to everyone who led, supported, helped test, raised issues, and helped to fix tickets.

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/

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.4 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticket if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

#6-4, #agenda, #dev-chat

Jb Audras 10:53 pm on October 10, 2023
Tags: , ,   

Four Weeks in Core – October 9, 2023

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 September 4 and October 9, 2023.

Please note that exceptionally and because of personal vacations, this Week in Core issue covers 4 weeks 😊

  • 269 commits
  • 337 contributors
  • 295 tickets created
  • 43 tickets reopened
  • 277 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 and/or focus.

Continue reading →

#6-4, #core, #week-in-core

Andrei Draganescu 6:29 pm on October 10, 2023
Tags:   

Editor Chat Agenda: 10 October 2023

Facilitator and notetaker: @andraganescu

This is the agenda for the weekly editor chat scheduled for Wednesday, October 4, 2023, 5:00 pm (UTC+03:00). This meeting is held in the #core-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

  • Announcements
  • Project updates
  • Task Coordination
  • Open Floor – extended edition.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share it as a comment or come prepared for the meeting itself.
  • 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.

#agenda, #core-editor, #core-editor-agenda, #meeting

#core-editor-agenda

Emily Clarke 4:07 pm on October 10, 2023
Tags: , , ,   

Performance Chat Summary: 10 October 2023

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • WordPress 6.4 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 today
  • Reminder about the Performance Hallway Hangout next week Thursday, October 19, 2023 at 04:00 PM GMT+1

Priority Projects

Server Response Time

Link to roadmap projects

Contributors: @joemcgill @spacedmonkey @swissspidy @thekt12 @mukesh27

  • @joemcgill Everything planned for 6.4 has been resolved. I’m keep an eye out for issues that come up during the last week of beta and 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).. Otherwise, am beginning to start focusing on opportunities for 6.5, like Improving Template Loading and Improvements to the way 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. widgets are registered (ex: #55595)
  • @spacedmonkey
  • @mukesh27 #59360 to be committed today. It was reopened for some concern that I’m looking into right now
  • @swissspidy Performant Translations is doing well. There are already PRs and tickets for all the relevant areas this touches. I’m working on further simplifying the 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. & coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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.. Once 6.4 is released we can continue with the next steps for a 6.5 merge.
  • @flixos90 I would like to flag this Slack thread – just spotted this literally 5 minutes ago, but it looks like the most significant performance fix for TT4 caused a 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., which now with the fix for that bug effectively may have reverted almost all the performance benefit
    • In my benchmark yesterday, TT4 was about ~10% slower than TT3. Now it’s again ~25% slower
    • @spacedmonkey to re-open #59541 to see if it helps
    • @joemcgill to run some profiles, but assuming it’s due to parse_blocks() being called way more often.
  • @thekt12 I have picked up https://github.com/WordPress/performance/issues/746 (just a while ago), checking through tickets that are still left

Database Optimization

Link to roadmap projects

Contributors: @spacedmonkey @mukesh27 @thekt12

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 & CSSCSS Cascading Style Sheets.

Link to roadmap project

Contributors: @mukesh27 @10upsimon @westonruter @spacedmonkey

  • @westonruter Yesterday I committed the removal of unload event listeners and use of pagehide and pageshow where appropriate for #55491 . In the best case this will improve performance by allowing bfcache to speed up page navigations. But as I mentioned before, bfcache is also disabled when Cache-Control: no-store is present, and this was added to all authenticated page requests in 6.3 with #21938. Lastly, the heartbeat script is only used on 0.25% of HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. Archive pages (which would be unauthenticated).  So in practice the performance benefits will be marginal. Nevertheless, the unload event is unreliable so the change is an improvement regardless.
  • @adamsilverstein I have been working on adoption of the script strategy feature with plugins and have been having some success. Its great how easy it is to layer on the new 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. without breaking old use cases (especially using `wp_script_add_data`). One potential issue I have discovered that could cause regressions has to do with dependencies and the footer attribute.
    • Here is the scenerio:
      • Popular plugin “Plugin A” currently enqueues a script on the front end, using `in_footer` => true, so the script is essentially non blocking
      • To get a slight performance gain, in WP >= 6.3 the plugin changes `in_footer` to `array( ‘strategy => ‘defer’ )`. Great, now the script is in the 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. so it can be discovered slightly earlier, and it is marked as `defer` so it is non-blocking.
    • Now… along comes “Plugin B”, they enqueue a script that depends on the script from “Plugin A”, and they still use `in_footer => true`. Now the script from “Plugin A” can no longer be deferred, so it is not – however it remains in the header. The result: we now have a new blocking script in the header.
    • I wonder if we had considered this during the design? Maybe in my scenario I should instead use `array( ‘strategy => ‘defer’, ‘in_fooer’ => true )`
    • @flixos90 I think opening a ticket would be good. If a script has defer, it should always be fine to load it in the footer (since with defer it only loads after the DOM anyway). So I think that would be a good fix: If a script is in the head and its defer is forced back to blocking, move it to the footer
    • @adamsilverstein I was thinking that also, but it might have other implications…Also in my testing I noticed that in_footer already has some dependency behavior built in that can move scripts to the header:
      Script A is marked for the footer. If script b depends on script a and is marked for the header, script a also gets put in the header
    • @10upsimon That makes sense @flixos90 I think we only never did that because by design you’d only usually have deferred in the header, generally, correct?
      • @flixos90 Not sure, I don’t remember us ever thinking about the head vs footer implication of a deferred script being forced back to blocking. So we may just have missed that consideration. To me what @adamsilverstein pointed out above is something we should be able to fix in a rather straightforward way
      • @adamsilverstein yea, I don’t think we considered that exact scenereo, I came across it trying to implement/use the feature
    • @flixos90 I think the latter has been the case forever, so that wouldn’t be a 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.
    • @joemcgill We could do some analysis of how many registered deferred scripts end up in the head, since we added some data attributes to track that sort of thing
    • @westonruter We don’t currently capture whether a script was originally registered with $in_footer in the data attributes like we do with the script strategies though
    • @flixos90 FWIW I cannot see any concerns with moving a head defer script to footer from a functional perspective. In both cases it would be loaded after the DOM. Not sure how important the impact research would be for that bug specifically
    • @adamsilverstein to open a ticket to discuss further

Images

Link to roadmap projects

Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill @pereirinha

  • @joemcgill I’m planning to follow up on two things we’ve discussed, related to improving how WordPress calculates the sizes attribute.
  • @adamsilverstein I’ve been testing the fetchpriority attribute and wanted to raise some potential issues. First: I created a simple plugin that adds an advanced image control that lets users set the fetchpriority manually for individual images – https://github.com/adamsilverstein/wp-fetchpriority-control
    • Noticed a few edge cases with our approach in testing –
    • I think these are all addressable in some form and the first may already be covered by an existing ticket; I’ll plan to open tickets for further discussion
  • @flixos90 I opened a new ticket yesterday for a recently found limitation of wp_get_loading_optimization_attributes() when it comes to images in block templates #59577 that affects TT4
  • @pereirinha I’m looking for good candidates to pick up, but nothing yet. Happy to assist here.

Measurement

Link to roadmap projects

Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90

  • @flixos90 Nothing from my end, other than running benchmarks on several tickets this week
  • @mukesh27 Planning to run benchmarks for beta 3 tomorrow.
  • @swissspidy Continuing working on documenting ways for improving the core performance test setup & reducing test variance. Nothing concrete right now
  • @joemcgill Another thing we’ve been discussing for the past few weeks is how to improve the confidence we have in our benchmarking setups. Many of us have been using an automated script that @swissspidy put together to run benchmarks for each release, and we’re getting consistent numbers, but those numbers are showing much bigger performance gains than what @flixos90 has been reporting with his local setup. I’m planning to dig into this a bit more today. @swissspidy I saw that you’re making good progress on converting performance tests to Playwrite. Anything we can help with there?

Ecosystem Tools

Link to roadmap projects

Contributors: @mukesh27 @swissspidy @westonruter

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27 @10upsimon

  • @10upsimon No major updates from me at the moment, I did decide to refactor some code to be more WordPress’y when it comes to the standalone plug-in card rendering within WPP settings screen, so I’ll open said PR for standalone plug-ins UIUI User interface soon, via a feature 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"..

Open Floor

  • @spacedmonkey I am changing roles ( I am leaving XWP ). I will not have sponsored time to work on this project. So as of the end of this week, I will be stepping down from this project. That means I will not be around to answer questions or code review. If you need anything, please message me before the end of the week.

Our next chat will be held on Tuesday, October 17, 2023 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary

Emily Clarke 9:27 am on October 10, 2023
Tags: , , ,   

Performance Chat Agenda: 10 October 2023

Here is the agenda for this week’s performance team meeting scheduled for Oct 10, 2023 at 15:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.

This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Ajit Bohra 3:39 pm on October 6, 2023
Tags: , , , ,   

Editor chat summary: October 04th, 2023

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel, on Wednesday, October 04, 2023, 14:00 UTC moderated by @ajitbohra

Accouncements

  • WordPress 6.4 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. 2 is available for testing.
  • WordPress 6.4 Editor Tasks Project Board.
  • Gutenberg 16.8.0 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 is available for testing.

Async key project updates

Read the latest updates directly from the following tracking issues:

@hellofromtonya

The Font Library’s 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/ has been significantly redesigned. It’ll need testing and release to gain wider in the wild testing.

Task Coordination

No updates.

Open Floor

@get_dave

I’m working on a PR which changes the Post Title in the Post Editor to render HTML in normal (“Visual”) mode and output raw HTML in “Code view” mode. It also strips all HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. from anything pasted into the title field in Visual mode. As this is a change that may impact editorial workflows I wanted to flag it for more visibility.

@vcanales
I’m wondering if we are open to releasing 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/ 16.8.0 on Monday rather than Wednesday so that the new 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. makes it to a release before Beta 3.

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.

Read complete transcript

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary