The Presence API feature plugin gives the WordPress admin real-time awareness of who is editing what, using a dedicated ephemeral table on a 60-second TTL instead of hammering wp_options. Here is what ships with it, and where it still gets confused.
The WordPress 7.0 Beta is live for Business and Commerce plans, and the change worth having is a one-click Deactivate button on the fatal error screen, instead of an SFTP session or a recovery mode email that never arrives.
Spry Fox has run the same WordPress blog since 2010, through hits, an acquisition and spin-outs. Why that outlasts social platforms, and how to cache a deep archive with the Transients API so an old database stays fast.
Gutenberg 23.0 adds an experimental revisions panel for templates, template parts and patterns, plus a flag that stops legacy meta boxes from disabling real-time collaboration. The Guidelines rename will catch you out on update.
WordPress 7.0 is on pause while Real-Time Collaboration is reworked. What the April 15 dev chat said about treating the next RC as a beta, the PR tagging problem, and core-abilities moving out of React.
WordPress 7.0 reworks the core design tools roster: Verse becomes Poetry, Accordion, Breadcrumbs and Math arrive with full design support, and pattern overrides are opt-in per attribute through a filter. Includes the updated support table and a registration snippet.
WooCommerce 10.7 drops an HPOS order request from 271 queries to 132, gives the Fulfillments API typed PHP methods, and hardens the REST API against XSS and CSRF. It also runs a database update, so stage it before you ship.
Notes from the April 21, 2026 performance chat: what auto sizes fixes about the sizes attribute, why the Gallery block is holding up a core merge, and a wp_calculate_image_sizes filter that beats regexing the_content.
The Core Dev Environment Toolkit gives contributors a one-click wordpress-develop setup. The less good news: the core privacy component has nobody maintaining it, two PRs are waiting on review, and the 7.0 release schedule still has not landed.
Nearly 800 documentation issues triaged and over 200 closed, plus the WP-Parser problem that keeps DevHub out of sync with core. Also the DocBlock format the parser expects, and the three handbooks carrying the biggest backlogs.