Ari Stathopoulos 6:38 am on December 20, 2022  

Help us test the SQLite implementation

A few months ago, a proposal was published to make WordPress officially support SQLite. After the proposal received a lot of positive feedback from the community, we started working on an implementation to make that happen.

Instead of releasing a separate feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins., it was deemed preferable to implement this as a module in the Performance Lab 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. As of version 1.8.0 of the Performance Lab plugin, the module is now available for testing.

We would like to urge hosts, plugin authors, and theme developers to test the implementation and help us move forward with this project – with the hope of merging an SQLite implementation in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. in a future release.

How to test the SQLite implementation

In order to test using an SQLite database instead of MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. for your WordPress site, you will need to follow the steps below:

  1. Install and activate the Performance Lab plugin on your site.
  2. Navigate from your dashboard to Settings > Performance.
  3. Enable the SQLite module, and click “Save changes”.
  4. As soon as you save your changes, the plugin will automatically copy the db.php file in your wp-content folder, copy the data for the current user and site title, and also log you in for a more streamlined experience.

Important note: When activating SQLite, your site will create an entirely separate and fresh database. We have implemented a basic setup so that you don’t have to go through the installation screens, but nothing else is migrated from the original database beyond that.

Frequently asked questions

Will I lose any data?

No. When you activate the SQLite module, a new database is created. Your old database remains unaltered, and when you disable the module, your site gets back to using its previous, unaffected MySQL database.

I had data on my old database, and I don’t see my posts, pages, users, etc, on my SQLite site.

The SQLite implementation does not include a way to migrate data from one database to another. Since this is a proposal for an implementation to be merged in WordPress Core, we need to follow the WordPress Core principles. Data migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. is not something that Core should do; it is clearly plugin territory. Your data remains safely in your previous database, and you can access it again by disabling the SQLite module.

When SQLite gets merged in Core, migration and backup plugins will add support for it.

Will this work if I have another db.php file in my wp-content folder?

No. If your site already includes a db.php file in the wp-content folder, you will not be able to test SQLite on your site.

You can check if your site already includes a db.php file from another plugin by going from your dashboard to the plugins screen and then navigating to the Drop-in tab.

Keep in mind that this limitation only applies because the implementation is in a plugin, and therefore it needs the drop-in file. Once SQLite is part of Core, this will not be the case.

Historical/Implementation details

The code for the SQLite implementation was copied from https://github.com/aaemnnosttv/wp-sqlite-db/blob/master/src/db.php by Evan Mattson, which is a fork of the original work on the sqlite-integration plugin by Kojima Toshiyasu. It was then refactored, coding standards were applied, and an integration with the Performance Lab plugin was built.

The SQLite code used has been in use for many years and has been battle-tested. We opted to start with a tried solution instead of starting from scratch because many of the problems we would have encountered have already been addressed and solved in the pre-existing implementation.

Where to report issues and feedback

If there are issues that should be addressed, please create a new issue in the plugin’s GitHub repository. When you do, please be sure to mention your SQLite version. You can find it by going from your Dashboard to Tools > Site Health > Info > Database, while the SQLite module is active.

Props @flixos90 and @olliejones for reviewing this post.

Abha Thakor 12:08 am on December 20, 2022
Tags: , ,   

Dev chat agenda, December 21, 2022

The weekly WordPress developers chats happen at 20:00 UTC in the core channel on the Make WordPress Slack. Note from team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @marybaum: Officially the chats last an hour, but occasionally a few people will keep a particularly lively discussion going for a few minutes longer. The chat is not for developers only; it’s for everyone who’s interested. So please join the meeting live if you can, or catch up via the summary, which generally goes up within a day.

The meeting on December 21 will be the last one in 2022. The chat will return January 4, 2023.

About Dev Chat.

  1. Welcome

2. Announcements

3. Blogblog (versus network, site) posts

4. Updates on forthcoming releases

5. Component maintainers’ updates, tickets to highlight/calls for help

You can also add your updates and requests to the comments below.

6. Open Floor

  • Discussion for an APAC-friendly new-contributors’ meeting in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • Please add your items to the comments.  

Thanks to @marybaum for review.

#agenda, #core, #dev-chat

Jb Audras 11:16 pm on December 19, 2022
Tags: , ,   

Two Weeks in Core – December 19, 2022

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 December 5 and December 19, 2022. This post exceptionally covers two weeks since we weren’t able to put together the recap last week.

  • 50 commits
  • 50 contributors
  • 81 tickets created
  • 7 tickets reopened
  • 70 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.

Code changes

Build/Test Tools

  • Run Xdebug tests on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.2 – #56009
  • Remove 3.7-4.0 branches from scheduled test runs – #57228
  • Refactor test for multiple location headers – #57306, #56793
  • Change the wp_cache_get_multiple function to get cache keys in a single request – #54864
  • Correct a flaky wp_nonce_field() test – #56793
  • Temporarily disable a WP_Http test for multiple Location headers – #57306
  • Use more descriptive name for a wp_new_comment() test – #56793

Bundled Themes

  • Twenty Seventeen: Document the $twentyseventeencounter global – #57069, #56792

Code Modernization

  • Rename parameters that use reserved keywords in wp-includes/class-wpdb.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/l10n.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/link-template.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/load.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/ms-blogs.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/ms-deprecated.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/ms-site.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/option.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/php-compat/readonly.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/pluggable.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/pomo/po.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/pomo/streams.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/post-template.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/post.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/query.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/rest-api.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/rest-api/class-wp-rest-server.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/rest-api/endpoints/class-wp-rest-controller.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/rest-api/endpoints/class-wp-rest-revisions-controller.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/rest-api/endpoints/class-wp-rest-widget-types-controller.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/rest-api/endpoints/class-wp-rest-widgets-controller.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/rewrite.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/sitemaps/class-wp-sitemaps.php – #56788

Docs

  • Add missing type for $_wp_theme_features in WP_Debug_Data::debug_data() – #57069, #56792
  • Improve DocBlockdocblock (phpdoc, xref, inline docs) formatting for get_post_class() – #56792
  • Improve various globals documentation, as per docblock standards – #57069, #56792
  • Improve various globals documentation, as per documentation standards – #57069, #56792
  • Mark some optional parameters as such in wp-includes/comment-template.php – #56792
  • Update docs for image_sideload_extensions filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to include webp in the list of allowed extensions – #57346, #56792

External Libraries

  • Update Requests library to version 2.0.0 – #54504
  • Upgrade PHPMailer to version 6.7 – #57281

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

  • Adds BC-layer /library/Requests.php file – #57341

Media

  • Use featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. if available for attachment as preview instead of icon – #49852
  • Account for legacy calls to nav_menu_css_class filter – #56926, #28620
  • Prevent infinite 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. in menus – #56926, #28620
  • Reset menu_item_parent to 0 when the parent is set to the item itself – #57169

Options, 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. APIs

  • Correct the documented return type for get_settings_errors() – #57323

Quick edit

  • Fix cases where the author field is empty when the user no longer has edit capabilities – #56819

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

  • Use update_post_author_caches in wp_prepare_revisions_for_js function – #56978

Site Health

  • Remove the WordPress 5.2 reference from the email sent on fatal errors – #57327, #54961

Themes

  • Adds outline CSSCSS Cascading Style Sheets. properties support 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. – #57354
  • Improve performance of _add_block_template_part_area_info and _add_block_template_info functions – #57077

Users

  • Clear the user_meta cache when clean_user_cache function is called – #54316

Props

Thanks to the 50 people who contributed to WordPress Core on Trac last week: @sergeybiryukov (32), @jrf (26), @justinahinon (23), @poena (23), @aristath (23), @peterwilsoncc (9), @spacedmonkey (5), @costdev (5), @azaozz (4), @dd32 (4), @hellofromTonya (4), @audrasjb (3), @ironprogrammer (3), @desrosj (2), @johnbillion (2), @JeffPaul (2), @upadalavipul (2), @NekoJonez (2), @mukesh27 (2), @samful (1), @mcaskill (1), @TobiasBg (1), @swissspidy (1), @JavierCasares (1), @onemaggie (1), @cadic (1), @seanchayes (1), @antpb (1), @szepeviktor (1), @benjgrolleau (1), @Synchro (1), @OllieJones (1), @sabernhardt (1), @antonvlasenko (1), @jmdodd (1), @soulseekah (1), @dustinrue (1), @wojsmol (1), @datagutten (1), @schlessera (1), @flixos90 (1), @priethor (1), @mhkuu (1), @david.binda (1), @mrwweb (1), @kebbet (1), @jb510 (1), @dimadin (1), @bjorsch (1), and @iamjaydip (1).

Congrats and welcome to our 2 new contributors of the week: @mcaskill, @cadic ♥️

Core committers: @sergeybiryukov (32), @peterwilsoncc (4), @spacedmonkey (4), @hellofromtonya (3), @audrasjb (3), @azaozz (2), @desrosj (1), and @johnbillion (1).

#6-2, #core, #week-in-core

Bethany Chobanian Lang 4:00 pm on December 19, 2022
Tags: , , ,   

Performance Chat Agenda: 20 December 2022

Here is the agenda for this week’s performance team meeting scheduled for December 20, 2022, at 16:00 UTC.

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

annezazu 6:22 am on December 16, 2022
Tags: , ,   

Hallway Hangout: Performance Considerations for Block Themes

As more is being done to work on performance as it relates to 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. themes, a hallway hangout has been planned to bring together folks from various backgrounds to see what else can be worked on, unblocked, and better understood. This is meant to be both a knowledge sharing and alignment creating session between folks from various areas including but not limited to @flixos90 @adamsilverstein @spacedmonkey @youknowriad @desrosj @tweetythierry @oandregal @aristath.

If you’re interested in joining, the Hallway Hangout will happen on 2023-01-10 14:30. a Zoom link will be shared in the #core-performance 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 before starting.

At a high level, we’ll go through general intros (what each person does/focuses on), current work underway to address performance, what work is being done specifically for block themes, and general open Q&A. Hallway hangouts are meant to be casual and collaborative so come prepared with a kind, curious mind along with any questions or items you want to demo/discuss.

This post will be updated with a recording of the hangout after it completes.

#hallwayhangout, #performance

David Potter 9:37 pm on December 14, 2022
Tags: 6.1.2, , , ,   

Dev Chat summary: Wednesday, December 14, 2022

Summary of the weekly WordPress developers’ chat in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel at 20:00 UTC.

1) Welcome

If you’re new to dev chat, you can find out more about this weekly meeting in the handbook.

Meeting facilitators: @marybaum and @webcommsat.

Agenda followed; thanks to @marybaum for preparing it.

Start of the meeting in the core channel of the Make 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/..

Summary from the December 7, 2022 dev chat.

2) Announcements

The State of The Word approaches! It happens 18:00 – 19:30 UTC on December 15, 2022 (1.00 – 2.30 PM EST).

There are just two days left to get your choices in for Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for 2023. Voting closes Friday, December 16 at 23:59 UTC.

What’s new in Gutenberg 14.7 post.

3) Blogblog (versus network, site) posts of note

The WordPress Survey is available. Share it, fill it in, and help take the WordPress project further.

There is a proposal for Enhancing the Scripts API with a loading strategy from @adamsilverstein

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. about content locking and other such enhancements.

The FSE program is seeking volunteers to use replay-io-for-capturing-bugs.

There is an open retrospective about the WordPress 6.1 release process. Feedback is welcome.

4) Upcoming releases

a) The 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. is 6.2

Core team rep @marybaum encourages contributors to help with getting new features ready early and work on tickets while there is time between releases.

b) The next 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. will be 6.1.2

This will likely be in January 2023 per the 6.1-release-leads channel – Slack link.

5) Components and tickets

a) Components

Build/Test Tools – @sergeybiryukov

  • Xdebug tests now run on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.2 too. Thanks @desrosj! Ticketticket Created for both bug reports and feature development on the bug tracker. #56009 has more details.
  • An issue in WP_HTTP unit tests with api.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ no longer returning the expected response after nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. update was identified and fixed. Ticket #57306 has more details.

General – @sergeybiryukov

  • Work has continued on renaming parameters that use reserved PHP keywords. Ticket #56788 has more details.

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

  • No major news this week.

Help/ About – @webcommsat

  • Maintainers been looking at some tickets awaiting review and at a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. in another ticket. If anyone has a view on this ticket #24567, it will be reviewed next.

Quick /Bulk Edit – @webcommsat

  • Maintainers been looking at this updated ticket #12940.

5b) Tickets assistance / highlight

No tickets were raised

6) Open floor

No issues were raised.

The next dev chat will be on December 21, 2022 at 20:00 UTC in the core Slack channel. This will be the last developers chat for 2022. It will restart in January 2023.

Props to: @marybaum and @webcommsat for running dev chat, @dpotter05 for the summary, and to @webcommsat and @marybaum for review.

#6-1-2-2, #6-2, #core, #dev-chat, #summary

marybaum 1:33 am on December 14, 2022
Tags: , , ,   

Dev Chat agenda, December 14, 2022

1. Welcome

There are just two more devchats in 2022—this one and December 21. Traditionally the group takes the last week of December off.

Here’s what happened last week.

2. Announcements

The State of The WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. approaches! It happens Thursday.

And there are just two days left to get your choices in for Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for 2023. Voting closes Friday, December 16.

3. Blogblog (versus network, site) posts of note

Also, with the end of the year comes the WordPress Survey. This is your chance to make your voice heard on matters large and small, and there is a further section for contributors.

@adamsilverstein has a proposal for scripts.

@ramonopoly has 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. about content locking and other such enhancements.

Here’s the release post for Gutenberg 14.7.

And @annezazu is looking for more people who want to learn time travel! Well, actually, just time travel in JS—on the FSE Outreach program, with replay.io.

4. Upcoming releases

The next major is 6.2; the next minor is 6.1.2.

5. Tickets and components

Time marches on! It’s still early, but it won’t be for too much longer. Get eyes on your favorite tickets now!

6. Open Floor

Got something to talk about? Drop it in the comments!

#agenda, #core, #dev-chat, #meeting

Jorge Costa 9:27 pm on December 13, 2022
Tags: , , ,   

Editor Chat Agenda: December 14, 2022

Facilitator and notetaker: @jorgefilipecosta.

This is the agenda for the weekly editor chat scheduled for Wednesday, December 14, 2022 at 15:00 CET. 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/..

General Announcements.


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/ 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 14.7.

State of the word 2022 is going to happen on 15 December.

Holiday break on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor chat.

Key project updates.

Task Coordination.

Open Floor – extended edition.

If you cannot attend the meeting, you are encouraged to share anything relevant to 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

Bethany Chobanian Lang 5:14 pm on December 13, 2022
Tags: , , , , , , ,   

Performance Chat Summary: 13 December 2022

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

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

  • @pbearne: Can we get the Media Library patch for dominant color merged? https://github.com/WordPress/performance/pull/587
    • @adamsilverstein: Not working yet, did the template replacing work but not the actual dominant colors
    • @pbearne will try to update this week

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

  • @spacedmonkey: Need code review for merge on:
    • https://github.com/WordPress/wordpress-develop/pull/3544
    • https://github.com/WordPress/wordpress-develop/pull/3365
    • https://github.com/WordPress/wordpress-develop/pull/3743
  • @spacedmonkey: Been trying to add caching to get_adjacent_post but filters make it hard

Feedback requested

Measurement

N/A

GitHub project

  • @joegrainger: Started engineering on PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Check this week, building out initial infrastructure
  • @flixos90: Server-Timing API PR has gotten some reviews and is lined up for Monday’s 1.8.0 release
    • Should help us significantly in assessing server timing metrics in the field; we’re currently extremely limited in that regard as the usual tools only give us client-side performance metrics
    • For example, other than baseline PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher execution time and DB query time metrics, it also includes one more specific metric, to measure the autoloaded options query (which will help us assess the potential impact of https://github.com/WordPress/performance/issues/526)
    • Very large PR (like SQLite) so the more reviews the better, hoping to merge tomorrow for 1.8.0, otherwise will need to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) to 1.9.0
    • Will be part of the plugin’s infrastructure, so other modules will be able to leverage it to add server timing metrics around their own behavior and validate how much a certain module improves server-side performance in the field

Feedback requested

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

@aristath @sergiomdgomes

GitHub project

  • @mxbclang: Blog post on enhancing the Scripts API with a loading strategy
    • Proposal from @adamsilverstein on a new approach; please take time to review and comment
    • @adamsilverstein: Next step is a ticketticket Created for both bug reports and feature development on the bug tracker./code proposal, thinking a new TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket might be best
    • @mxbclang and @flixos90 agree on a new Trac ticket
    • @spacedmonkey: Is there a plan to use the defer 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. in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. themes and plugins? Useful for developers to see it in action and provide a good example
      • @adamsilverstein: Yes, that’s the plan, to use it wherever we can in core, including themes
    • @spacedmonkey: Might be worth reaching out to the 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/ team to see if blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor could use this
      • @adamsilverstein: Greg was always asking for it and commented on the original proposal; will be sure to keep them 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.
    • @johnbillion: Have any scripts in default themes been identified as being able to support defer? Probably fewer can support async
      • @adamsilverstein: For sure things like commenting script, but haven’t looked at core themes yet. Probably lots of things in wp-adminadmin (and super admin), as well.

Feedback requested

Database

@olliejones

GitHub project

  • @olliejones: @aristath finished the SQLite module https://github.com/WordPress/performance/pull/547 and we would welcome additional testing in advance of Monday’s release
    • @flixos90: Important to test the user experience on module activation. You’ll get an entirely new DB with some added logic to make the transition as seamless as possible. This is only the install; no content migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies..
    • @spacedmonkey: Do we run unit tests with SQLite enabled?
      • @flixos90: We don’t, but that’s a great idea. Maybe we can add an extra scenario to the GH action for PHPUnit that always has the SQLite database active so we can spot any inconsistencies.
      • @spacedmonkey to open an issue

Feedback requested

Infrastructure

@flixos90

GitHub project

  • @flixos90: A few PRs have landed that fixed some issues with tests since PHP 8.2 caused breakage; kudos to @mukesh27 for working on those
  • @adamsilverstein: Proposed a new plan for A/B testing capability in the plugin https://github.com/WordPress/performance/issues/597 and would appreciate feedback

Feedback requested

Open floor

  • @spacedmonkey: Would love review on https://github.com/WordPress/wordpress-develop/pull/3609, one line of code that would result in big wins

Our next chat will be held on Tuesday, December 20, 2022 at 16:00 UTC in the #core-performance channel in Slack.

#core-js, #core-media, #performance, #performance-chat, #summary, #hosting-community

#core-performance, #meta

Bethany Chobanian Lang 1:04 pm on December 12, 2022
Tags: , , ,   

Performance Chat Agenda: 13 December 2022

Here is the agenda for this week’s performance team meeting scheduled for December 13, 2022, at 16:00 UTC.

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