Teams
-
Core
The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team makes WordPress. Whether you’re a seasoned PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php, HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites., 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 or CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. developer or are just learning to code, we’d love to have you on board. You can write code, fix bugs, debate decisions, and help with development.
-
Design
The design group is focused on the designing and developing the user interface. It’s a home for designers and UXers alike. There are regular discussions about mockups, design, and user testing.
-
Mobile
The mobile team builds the iOSiOS The operating system used on iPhones and iPads. and Android apps. Lend them your Kotlin, Swift, or ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org Native skills. The team also needs designers, UXUX UX is an acronym for User Experience – the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. experts, and testers to give users a smooth experience on every device.
-
Accessibility
The a11yAccessibility 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) group provides 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) expertise across the project. They make sure that WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and all of WordPress’ resources are accessible.
-
Polyglots
WordPress is used all over the world in many different languages. If you’re a polyglot, you can help by translating WordPress into your own language or contributing to the GlotPress project, making translations easier and more effective for everyone.
-
Support
Answering questions in the support forums, IRC, or 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/ is one of the easiest ways to start contributing. Everyone knows the answer to something! Since the forums run on bbPress, you can also contribute by helping make the software behind them even better.
View all teams and their meetings
Latest activity
See the latest happenings across the entire project.
Introducing SMTP: a community-maintained way to send WordPress email reliably
Email is one of those things WordPress needs to just work. Password resets, new user notifications, form submissions, order receipts: they all go through wp_mail(), which by default relies on PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php’s mail() function.
On a growing number of servers, that is no longer an option. Many hosts disable mail() or 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. outbound port 25 to prevent abuse. Containerized and cloud setups often have no local mail transfer agent at all. When that happens, WordPress fails quietly. The site looks fine, but nobody gets the password reset.
Today the Plugins Team is sharing a new 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. built for exactly this case: SMTP, available now in the Plugin Directory and developed in the open on GitHub.
Why this matters
Sending WordPress email through SMTP is one of the most common needs in the ecosystem. The most popular SMTP plugins in the Directory add up to well over five million active installations. Requests to add SMTP settings to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. have come up over the years (see #7284, #29069 and its duplicates). Core’s long-standing position is that this belongs in plugin territory, and we agree.
What has been missing is a simple, neutral option that belongs to the community. It configures the mailer WordPress already ships with, and nothing more.
What it does
- Any SMTP server. Host, port, encryption (none, SSLSSL Secure Socket Layer – Encryption from the server to the browser and back. Prevents prying eyes from seeing what you are sending between your browser and the server. or TLS), username, password and From address.
- Configuration in wp-config.php. Constants such as SMTP_HOST, SMTP_USER or SMTP_PASSWORD override saved values and lock the field in the settings screen. This is the recommended approach for production.
- Careful handling of secrets. On WordPress 7.2 and later, passwords and other credentials are stored through the new core Secrets API, encrypted at rest, so they no longer sit in plain text in the database or in backups. On earlier versions they are stored apart from the other settings. In both cases they are never printed back into the page, and they are redacted from the test email’s connection log.
- Email log of recipient, subject, status and error. Message bodies, headers and attachments are never stored. Entries are purged after 30 days by default.
- Failure alerts outside email. A broken mailer can’t report itself, so the plugin can notify a 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 when wp_mail() fails. Alerts are throttled to avoid flooding.
- 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/ support: wp smtp settings set, wp smtp test and wp smtp status, built for provisioning and automation. Passwords are read from STDIN rather than passed as arguments.
- ExtensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software.. Providers and alert channels can be added through filters (smtp_providers, smtp_alert_channels).
It requires WordPress 6.3+ and PHP 7.4+, and is licensed GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples.-2.0-or-later.
Calling all email providers
SMTP is built around a small provider 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.. Each provider declares its own fields, required values and wp-config.php constants, and configures the PHPMailer instance used by wp_mail(). The built-in Generic SMTP provider is registered through the same smtp_providers 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. any provider can use.
That means email services don’t need to ship a separate plugin to offer a smooth setup in WordPress. If you run an email delivery service, we invite you to contribute a provider for it to the repository:
- SMTP-based providers can be added today. A provider definition is a label, a few fields, and a configure callback that sets the host, port and credentials.
- API-based providers, which send over 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. instead of SMTP, aren’t supported yet. Designing that layer is the next big step, and it’s being discussed in #1. Providers who want to see their API supported are very welcome to help shape it.
Contributed providers go through the same pull request review as any other code, and need to:
- follow WordPress coding standardsWordPress Coding Standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards.;
- include tests;
- keep secrets out of the page and out of logs;
- contain no tracking, upsells or promotional content.
The goal is a neutral plugin where every provider sits on equal footing.
About the smtp slug
The plugin will be published under the existing smtp slug, which has a long history in the Directory. It was originally created by Serghei Iakovlev and later maintained for many years by Sorin Iclanzan, who has now given his approval for it to become a community plugin. We want to thank both of them for their work and for keeping it going all this time.
Existing users will upgrade in place. Their host, port, encryption and username are imported automatically. The legacy plugin encrypted passwords with mcrypt, which was removed in PHP 7.2, so on most servers the password can’t be migrated. In that case an admin notice will ask the site owner to enter it again.
A shared resource, maintained together
The Plugins Team has started this plugin, but it doesn’t belong to the team, and the team doesn’t provide support for it. Like WordPress itself, it belongs to the community, and its future depends on the people who use it and contribute to it.
There are many ways to help keep it healthy:
- Contribute code, fixes and tests through pull requests on GitHub.
- Review open pull requests and help triage issues.
- Help answer questions in the plugin’s support forumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations. on 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/.
- Contribute a provider for your email service, or help design API-based sending in #1.
- Translate it on translate.wordpress.org.
If sending email from WordPress matters to you, and it matters to almost everyone, this is a great place to give back.
Plugins Team: 16 Nov 2026
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. Status Change Stats
- Plugins requested : 1330
- Plugins rejected : 1749
- Plugins closed : 1071
- Plugins approved : 826
Plugin Queue Stats (current)
- Plugins in the queue (new and pending)* : 4702
- (older than 7 days ago)** : 3322
- (2026-11-09 – 2026-11-15) : 1000
- (new; not processed or replied to yet)* : 727
- (pending; replied to)* : 3975
- (pending; waiting on author)* : 3163
- (pending; waiting on reviewer)* : 627
- (pending; waiting on reviewer, email not yet sent)* : 185
Help Scout Queue Stats
- Total Conversations: 2632
- New Conversations: 1620
- Customers: 2318
- Conversations per Day: 329
- Busiest Day: Friday
- Messages Received: 1672
- Replies Sent: 4235
- Emails Created: 1326
* : Stat reflects current size of queue and does not take into account ‘date’ or ‘day’ interval** : Stat reflects activity only within the ‘recentdays’ from today
WordPress notifications and declared intent: proposal for the path forward
Summary
While work progressed on the WP Feature Notifications project, Matt raised the concern that the most pressing problem is that plugins from the directory fill the adminadmin (and super admin) dashboard with unnecessary promotional banners. 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. guidelines need to be updated and enforced to stop this. To enforce a guideline with tools, every plugin notification and admin notice needs a declared intent that tools can read.
This proposal attempts to reuse the work already completely in wp-feature-notifications, but to focus on the parts required to be able to declare intent, and update tooling to detect incorrect usage:
- Every notification channel declares an intent: why it sends notifications.
- An admin notice is one more surface where a channel’s messages can appear. It is not a separate system.
- WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s own admin notices are exempt. Only plugins must declare intent. This keeps changes to Core small.
Background
The idea of “declared intent” came up in the comments on @poligilad‘s Exploring a design for feature notifications post, and more specifically @davidperez’s suggestion that plugins should declare intent.
In the currently suggested implementation, channels group notifications by topic, such as core/updates, and plugins choose their names freely. To WordPress, acme/orders and acme/deals look the same. Channels are still the right place to declare intent: it is declared once, in a place tools can read without running the plugin.
Intents
David’s three suggested intents leave two gaps: activity from external sources (users, agents, comments, mentions), and confirmations of the user’s own actions (“Settings saved”). Ideally there should be five registered intents. Core should control the list, and it should not be filterable.
| Intent | Test: what triggered it? | Examples |
|---|---|---|
operational | The site or an automated process changed something, or something needs attention to keep the site working | Update available, backup failed, scheduled post published, import finished |
setup | Something is unfinished. It must stop once the task is done | “Connect your account”, “Finish configuring payments” |
activity | Another entity did something that involves you | New comment, mention, “Alex updated your page” |
feedback | You just did something, and this is the result | “Settings saved”, “Invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. email address” |
promotional | None of the above: the sender started it | Upsells, discounts, tips, “What’s new”, review requests, surveys |
Rules for choosing an intent
- Is an entity (person/agent) behind it? That decides between
activityandoperational. promotionalcovers everything else. There is no “informational” intent, because it would become a loophole. Plugin Check can’t tell an educational tip from a soft sell.- Intent is not urgency. A security alert is
operationalwith thealertseverityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs.. - One intent per channel. A message can’t change its channel’s intent. If a topic covers more than one intent, register one channel per intent.
Edge cases
| Notification | Intent | Why |
|---|---|---|
| “Your license expired, updates have stopped” | operational | Reports a real change in the site’s state |
| “Your license expires in 30 days, renew now” | promotional | Asks for money ahead of time |
| “Please rate our plugin” or “Take our survey” | promotional | Benefits the sender |
| “Allow usage tracking?” | promotional | Optional, and benefits the sender |
| A Site Health recommendation | operational | Low severity |
| “The page has been updated” (by you) | feedback | Inline only, never in the hub |
| “The page has been updated” (by another person) | activity | |
| “The page has been updated” (by a cron job, sync, or AI agent) | operational | The existing actor field shows what made the change |
Rules for each intent
Severities are a fixed list: alert, info, warning and success.
| Intent | Hub (notification centre) | Admin notice | Severity |
|---|---|---|---|
operational | ✅ | ✅ | Any |
setup | ✅ | ✅ Must be dismissible | Any except success |
activity | ✅ | ❌ | Any except success |
feedback | ❌ Never stored | ✅ Only right after the user’s own action | Any. The only intent that may use success |
promotional | ✅ | ⚠️ Hidden on core screens, always dismissible | info only, or none |
- Promotional severity. Limiting promotional messages to
inforeplaces David’s “promotional is never critical”. There’s no need to define “critical”, and the rule is the same on every surface. - Promotional screens. Core can’t tell which plugin added a menu page, so “only on the plugin’s own screens” can’t be checked at runtime. Instead, promotional notices are hidden on a fixed list of core screens, such as the Dashboard, Plugins, Posts and Settings. If plugins start promoting on each other’s screens, channels could later declare
screens, and Plugin Check could compare them with the plugin’s ownadd_menu_page()calls.
Core notices are exempt
WordPress Core’s own admin notices are allowed by default. Only plugins must declare intent.
- Core notices never pass a
channel, so none of the intent rules apply to them. - Plugin Check only scans plugins, so the exemption costs nothing on the static side.
- Core can adopt channels for its own notices later, if it wants to.
A notice without a channel could come from core or from a plugin. Telling them apart at runtime would need backtraces or callback file paths, which are slow and fragile. So undeclared plugin notices are left to Plugin Check and a directory review. They are not collapsed or hidden at runtime.
Proposed 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.
// Registered once, on init. Declares what the channel is for and where it may appear.
register_channel(
'acme/connect-account',
array(
'title' => __( 'Account connection', 'acme' ),
'intent' => 'setup',
'surfaces' => array( 'admin_notice', 'hub' ),
)
);
// Shown with the existing core helper, plus one new argument.
wp_admin_notice(
__( 'Connect your Acme account to finish setup.', 'acme' ),
array(
'channel' => 'acme/connect-account',
'type' => 'info',
'dismissible' => true,
)
);
Every wp_admin_notice() call from a plugin needs a channel, including feedback. Feedback can also be an error, such as “Invalid email address”, so type => 'success' can’t imply the intent. A plugin can register one general channel, such as acme/feedback, for these.
A channel is better than a bare intent argument. From the channel, WordPress gets the intent, a namespace that ties the notice to its plugin, persistent dismissals and per-user muting, all from one lookup.
No core update is needed for v1
wp_get_admin_notice() passes its arguments through wp_parse_args(), which keeps keys it doesn’t know. So the channel key already reaches two existing filters:
| 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. | What the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins does with it |
|---|---|
wp_admin_notice_args | Looks up the channel’s intent. Applies rules such as forcing dismissible, and maps type => 'error' to the severity alert. |
wp_admin_notice_markup | Returns '' to hide a notice that breaks a rule, for example a promotional notice on a core screen. |
On sites without the feature plugin, the channel key is silently ignored, so plugins can adopt it right away. A later core 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. would only need to merge the channel registry and document the channel argument. In core, register_channel() would need a prefixed global name, such as wp_register_notification_channel().
What we can reuse
Existing wp-feature-notifications code that can be reused to support this new proposal.
| Existing piece | Location | What it gives us |
|---|---|---|
| Channel registry | includes/class-channel-registry.php | Registration ahead of time, with names validated as namespace/name. |
Channel::$context (unused today) | includes/model/class-channel.php | Already described as a “default display context”. It becomes surfaces. |
| Display contexts in JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. | src/store/constants.ts, src/utils/init.tsx | addContext() already draws notifications into any #wp-notifications-{context} container. Admin notices become one more context. |
Message model | includes/model/class-message.php | Covers everything wp_admin_notice() takes, and more. The 255-character message limit blocks large HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. banners by design. |
Per-user queue (dismissed_at, displayed_at) | includes/database/class-schema.php | Dismissals that persist per user. Core admin notices don’t have this, so every plugin builds its own. Getting this for free is the main reason plugins would adopt the API. |
| Notification REST controller | includes/restapi/class-notification-controller.php | The endpoint the notice UIUI User interface calls to dismiss a notice. |
Subscriptions with snoozed_until | includes/model/class-subscription.php | Muting and snoozing per user and per channel. “Mute by intent” can build on it. |
| Channel REST controller | includes/restapi/class-channel-controller.php | Lists every registered channel and its intent, for auditing and a settings screen. |
What needs to be built
- Intent and surfaces on channels, and send-path validation. Covered by
Add "intent" and "surfaces" to channels, and validate the send path #659. - The
admin_noticesurface. Thewp_admin_notice_argsandwp_admin_notice_markupfilters, and persistent dismissals using the queue table. - Notices driven by a condition. The current model is event based: something happens, and a message is stored. Most admin notices don’t work like that. A
setupnotice should show while something is unfinished, and afeedbacknotice only lasts for one request. These notices are drawn whenwp_admin_notice()is called, or when a registeredconditioncallback returns true. The queue table only stores per-user state, such as dismissed. Event-based messages, such as “backup failed”, keep using the stored path. - Intent rules at runtime, as in the table above.
- Plugin Check rules TBD.
- A
Surfaceinterface and router, soemailandpushcan be added later without changing the plugin-facing API:
interface Surface {
public function get_name(): string;
public function supports( Model\Channel $channel ): bool;
public function deliver( Model\Message $message, array $recipients ): void;
}
How enforcement works
| Layer | What it checks |
|---|---|
| Plugin Check (without running code) | admin_notices callbacks that echo HTML. Every wp_admin_notice() call with no channel. A promotional channel used with any type other than info. Channels that aren’t namespaced to the plugin’s slug. |
| Runtime (the feature plugin) | _doing_it_wrong() for unregistered channels, unknown intents and severities that break the rules. Intent rules applied when a notice is drawn. Notices without a channel are left alone, because they may come from core. |
| Directory review | Updated Plugin Guideline 11 wording that refers to declared intent. Automated checks run on every plugin update. |
Two tracks: guidelines and code
Plugin guidelines can’t require an API that isn’t in core yet. So the work runs on two tracks:
- Guidelines, starting now. Update Guideline 11 with rules based on intent, for example: “promotional notices never on core screens, always dismissible, never styled as errors.” Human review enforces them at first.
- WP Feature Notifications plugin, next. Prove the registry, intent rules and dismissals here. Once plugins can rely on the API, Plugin Check can enforce the same rules automatically.
The notification centre, email, and mobile delivery build on the same registrations, and plugins don’t need to change anything.
Alternatives considered
- A bare
intentargument onwp_admin_notice(). Rejected: a channel carries the intent plus a namespace, dismissals, and muting. - A separate
register_admin_notice()API. Rejected: channels already do this job. - Moving all notices into the hub. Kept as the long-term direction, but too large a change for now.
- Collapsing undeclared notices at runtime (@poligilad‘s “5 notices” idea). Dropped: it needs core and plugin notices to be told apart at runtime.
Request for feedback
What do you think of this proposal? Please leave your thoughts in the comments by Monday November 30, 2026.
AI Assistance declaration
- AI assistance: Yes
- Tool(s): Claude Code using Opus 5.5 medium
- Used for: Initial research and drafting proposal copy and 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/ issue; final versions were reviewed, edited and approved by me.
Props to @dufresnesteven, @poligilad, and @annezazu for pre-publish review.
Update bundled @wordpress/* packages and @wordpress/build to fix CSS module class name collisions
If your 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. bundles its own copy of any package below, update to the listed version or later and release a new version of your plugin before WordPress 7.2.
| Package | First version with the fix |
|---|---|
@wordpress/ui | 0.26.0 |
@wordpress/dataviews | 22.0.0 |
@wordpress/admin-ui | 3.1.0 |
@wordpress/grid | 0.11.0 |
@wordpress/components* | 44.0.0 |
* If your plugin loads @wordpress/components through the wp-components script, WordPress 7.2 provides the fixed copy.
If your plugin compiles its own CSSCSS Cascading Style Sheets. modules with @wordpress/build, update to 0.27.0 or later and rebuild.
The problem
Some @wordpress/* packages are bundled into each plugin that uses them instead of being loaded once as shared scripts. 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. in @wordpress/build, the tool that compiles these packages, made bundled copies of a package at different versions share CSS module class names. Class names were meant to change whenever the CSS that defines them changes, so that each copy’s styles apply only to its own components. Instead, they depended only on the file path and the class name. When two copies with different styles were loaded on one page, for example one in WordPress and another bundled in a plugin, each copy’s styles also applied to the other copy’s components. The result could match neither version, such as a focus ring appearing on every hovered tab (#85896).
This affects every version of these packages published before the fix.
What changes in WordPress 7.2
Starting with WordPress 7.2, class names change whenever the CSS that defines them changes (#85900). Two copies share class names only when their CSS is identical, so a copy with different styles no longer affects the other.
The packages that ship with WordPress 7.2 are built this way. A copy your plugin bundled from an earlier version no longer collides with them. However, two copies built before the change can still collide with each other, for example when two plugins on the same site bundle different older versions of @wordpress/ui.
Props to @aduth for review.
A high school's first WordPress Credits cohort, students teaching students, and one campus event split across three labs
Meetup Organizer Newsletter | November 2026
Namaskar (नमस्कार), and hello. Welcome to your monthly roundup of practical ideas, community updates, and results from organizers around the WordPress community. This issue covers Oct 18 to Nov 15.
Worth celebrating
WordPress Credits passes 50 institutions. The program had two institutions in September 2025 and 27 by June 2026, and it passed 50 in October. As of Oct 19, its dashboard recorded institutions in 17 countries and 364 graduates, with student work across 18 WordPress teams. On Nov 4, the project also welcomed Akademia Śląska in Katowice, Poland. The program is free for partner institutions, so it is worth mentioning to a school near your group. Read the announcement.

A student’s first 66 photos. A final-year computer science student at Pundra University of Science & Technology in Bangladesh finished WordPress Credits on Nov 2. He set a goal of 30 photos for the WordPress Photo Directory and published 66, all CC0. He also contributed more than 400 Bengali translation strings and prepared a Bengali translation of a Learn WordPress lesson, which is waiting for review. You do not need to write code to contribute. Read the recap on WordPress Central.

50 websites and 50 new profiles in two days. Students at Presidency University in Dhaka built 50 websites and created their .Org profiles during Campus Connect on Oct 25 to 26, then talked through career paths in the WordPress ecosystem. The university has applied to join WordPress Credits. Read the recap.

A WordCamp without swag. WordCamp Sylhet 2026 in Bangladesh asked organizers and sponsors to skip swag, under the theme “back to basics” and the message “less show, more substance.” About 150 people joined Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ on Oct 2. An organizer’s recap says hallway conversations ran longer and questions after sessions were sharper. If you plan an event, it is one more format to weigh. Read the recap.

New groups, including one on the Caribbean coast. WordPress Meetup Limón, a new group in Puerto Viejo de Talamanca, Costa Rica, planned its very first event for Nov 14: a free, hands-on WordPress Studio workshop for local business owners, freelancers, and creatives. Welcome as well to the new groups in Joinville, Brazil, Austin, and Park City, Utah, which joined the chapter this month.
Students teaching students
The WordPress Student Club at Government Mahila Engineering College in Ajmer held its first session on Oct 22 with one idea: students learning from students. Two third-year students coordinate it, with support from the local WordPress community in Ajmer.
The club ran four sessions in about a week. The first covered the basics: what a website is, WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ versus .Org, domains, and hosting. The second, online on Oct 26, walked through installing WordPress Studio and the dashboard. Then on Oct 27 to 28, a fourth-year student led a two-day portfolio build. The club reports that every participant built their own portfolio site, with sections for projects and achievements, and the group explored contact forms along the way.

The college is one of the partner colleges in Campus Connect Ajmer, which has run at five colleges this edition, each with a seminar followed by a hands-on workshop where students build their first site. A campus event lasts a day, but a student club keeps going after the organizers leave. If you run Campus Connect, ask before you go who wants to lead the next session, and offer to come back as a guest instead of the teacher.
Three formats to borrow this month
- A WordPress Studio build session. Groups in Costa Rica and El Salvador picked this one. WordPress Puntarenas ran “From Idea to Online Store: WordPress + AI with Studio” on Oct 19 for 45 people from Costa Rica and other parts of Latin America. In El Salvador, a 90-minute hands-on Studio workshop on Oct 24 brought in 20 participants. Limón chose the same format for its first event. It works as a one-evening or one-morning plan: one tool, one goal, and everyone brings a laptop.
- An “Ask Anything” session. After flooding in Chiba Prefecture made travel uncertain, Chiba WordPress Meetup cancelled a planned photo walk and met online on Oct 18. Participants were invited to pitch in on any question that had come up while using WordPress. Almost everyone in the room was an experienced user, so it felt more like a casual chat than a consultation, which is the lesson: invite a few newer users who bring real questions. The photo walk is planned for the November meeting.
- A talk title that invites an argument. WordPress CDMX met in person on Oct 24 for a talk called “Is WordPress dead? Autopsy in AI times,” and reported a lot of good conversation about it. The same day, the 9th WordPress Tbilisi Meetup heard a walkthrough of a real project that went from an AI co-developer to an autonomous AI agent. A question people have opinions about gives quieter attendees something to reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org to.
Group of the Month: WordPress Kolhapur, India
WordPress Kolhapur had a month that shows a team that no longer needs its most experienced people in the room. On Oct 3, four of its organizers were away at WordCamp Rajasthan, and Campus Connect #3 went ahead anyway. Two organizers and the volunteers ran it, and 59 of 60 registered students came.

On Oct 17, at Campus Connect #4 at Dr. Bapuji Salunkhe Institute of Engineering and Technology, 56 of 78 registered students attended. Each computer lab fits about 20 to 25 students, so the team split them across three labs with three facilitators, one of them a first-timer. Smaller groups meant each facilitator could give real attention to their own students instead of moving around a big room helping people catch up. If your campus has small labs, this is worth copying. The group also shared a recap video.

Then on Oct 27, the group announced its October community get-together just two days ahead, and 17 people came anyway. They talked about going to WordCamp Bengaluru (seven or eight members are planning to attend), and started trading ideas for the next WordCamp Kolhapur.

Group of the Month is for a story another organizer can learn from, and you can put any group forward, including your own.
Also worth knowing
A privacy fix on ticket pages
Between May 20, 2025 and Oct 28, 2026, a bug listed some attendees on public Attendees pages even after they had opted out. The post says about 1,280 tickets across 168 events were affected, that about 8,580 were hidden when the issue was fixed on Oct 28, and how affected people can opt back in. If an attendee asks, point them to the post, and to [email protected] for privacy questions.
Request sponsor vetting from your event dashboard
You can now ask for a sponsor to be vetted straight from its record in your event dashboard, with no email or spreadsheet, and follow its progress there. Once it shows Approved, you can send the invoice.
Help test Badge Designer
Badge Designer is a new visual editor for WordCamp badges. Upload your own artwork, add attendee details and QR codes, check each badge on screen, and export a print-ready PDF. Feedback is wanted by Fri Nov 20.
QR code check-in and QR codes on badges
Volunteers can now check attendees in by scanning a QR code, and badges can print a QR code that links to each attendee’s profile.
Community Team Supporters check-in and a new cohort
The Community Team Supporters program is checking in on current Supporters and opening a new cohort. Replies and applications are due Nov 18.
Quick links
- Contributor Toolkit 2.0 has a redesigned app, is available in ten languages, and is built for first-time contributors, especially at Contributor Days.
- WordPress Credits sponsorship tiers are described for a 2027 pilot, which is useful context for local sponsors who already back your Campus Connect events.
- Paying vendors for Campus Connect in Indonesia: organizers there now have a local process where a mentorEvent Supporter Event Supporter (formerly Mentor) is someone who has already organised a WordCamp and has time to meet with their assigned mentee every 2 weeks, they talk over where they should be in their timeline, help them to identify their issues, and also identify solutions for their issues. pays vendors on behalf of each event.
- September’s Education Buzz Report covers Campus Connect, WordPress Credits, and Student Clubs.
By the numbers
718
groups in 100 countries, according to the events dashboard on Nov 15.
160
of those groups met in the last 30 days, according to the events dashboard.
364
graduates in WordPress Credits as of Oct 19, across 50+ institutions.
59 of 60
registered students came to Campus Connect #3 in Kolhapur on Oct 3.
57
websites built by about 90 students at Campus Connect Rajshahi at Varendra University on Oct 14.
MeetupsMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. of the Month










Coming up
| Date | Event | Where |
|---|---|---|
| Nov 20, 2026 | WordPress in Education Summit | Kaliro, Uganda |
| Nov 21 to 22, 2026 | WordCamp Bengaluru 2026 | Bengaluru, India |
| Nov 25, 2026 | WordPress Campus Connect SMK Tunas Pembangunan 2 Surakarta | Surakarta, Indonesia |
| Nov 27 to 28, 2026 | WordCamp Nairobi 2026 | Nairobi, Kenya |
| Nov 28, 2026 | WordPress Campus Connect Universitas Putra Bangsa | Kebumen, Indonesia |
| Nov 30, 2026 | WordPress Campus Connect Liceo la Paz A Coruña | A Coruña, Spain |
| Dec 3 to 13, 2026 | WordPress Campus Connect Universitas Brawijaya | Malang, Indonesia |
| Dec 5, 2026 | WordCamp Bandung 2026 | Bandung, Indonesia |
| Dec 11 to 12, 2026 | WordCamp Athens 2026 | Athens, Greece |
| Dec 12 to 13, 2026 | WordCamp Delhi 2026 | New Delhi, India |
Campus Connect series also continue through this window in Dhaka, Rajshahi, Kolhapur, Masaka, and across central and eastern Uganda. Local community events run in far more places than this. Everything, everywhere, is on events.wordpress.org.
Open calls for speakers
- WordCamp Mumbai 2027 (Feb 13): closes Nov 30. First-time speakers can get help shaping their talk before they submit, and there are 10-minute lightning talk slots.
- WordCamp Pune 2027 (Feb 6 to 7): closes Nov 30. First-time speakers are welcome.
- WordCamp Asia 2027 (Penang, Malaysia, Apr 9 to 11): the call now closes Jan 31, 2027. This is a change from the Nov 8 date we shared in October.
Over to you
Who did something for the first time in your group this month? A first talk, a first session they led, a first contribution.
Tell us who they are and what they did, with their okay, and we will celebrate them in December’s Worth celebrating.
We would also love your recaps and photos for the next issue, which publishes on Dec 15. A few lines about what you ran and what you learned is plenty, and a photo with your group’s okay makes it better. If you would like to co-author next month’s issue, say so in the comments or in #community-events and we will find a time to work on it together.
Reply in the comments below, in #community-events, or by email to [email protected], whichever you already use.
This newsletter is built from what you share!
Send your recaps and photos and your group goes in Meetups of the Month. Every group that shares one is included, so ask your group’s permission and send it. Group of the Month is for a story another organizer can learn from, and you can put any group forward, including your own.
Did we miss your event? Possibly, and we would rather know. Send your recap in #community-events or by email, and it goes in next month.
Tell us what you want to read here too. If there is a section missing, a format you want explained, or a question you wish someone would answer, say so and we will build it into the next issue.
Need support or guidance?
The Community Team is here to help. Email [email protected] or join us in #community-events on 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/.
Each issue opens with a greeting from a language spoken where one of the featured groups is based. This month it is Marathi, for the organizers in Kolhapur featured above. If you would like your language to open an issue, tell us.
Thanks for everything you do to grow and support the WordPress community.
A week in Openverse: 2026-11-09 – 2026-11-16
openverse
Merged PRs
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.
- #5741: Update dependency urllib3 to v2.8.0 [SECURITY]
- #5742: Update dependency cryptography to v49 [SECURITY]
- #5745: Update dependency pillow to v13 [SECURITY]
- #5746: Update dependency setuptools to v84 [SECURITY]
- #5753: Update dependency djangorestframework to v3.15.2 [SECURITY]
- #5754: Update dependency jwcrypto to v1.5.7 [SECURITY]
- #5755: Update dependency sqlparse to v0.5.4 [SECURITY]
- #5756: Update dependency tqdm to v4.66.3 [SECURITY]
- #5758: Update dependency deepdiff to v8.6.2 [SECURITY]
- #5760: Update dependency python-dotenv to v1.2.2 [SECURITY]
- #5761: Update dependency werkzeug to v3.1.6 [SECURITY]
- #5762: Update dependency graphql-coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to v3.2.12 [SECURITY]
- #5764: Update dependency werkzeug to v3.1.9 [SECURITY]
- #5766: Update dependency sqlparse to v0.6.0 [SECURITY]
- #5767: Update dependency cryptography to v50 [SECURITY]
- #5768: Update dependency oauthlib to v4 [SECURITY]
- #5769: Update dependency oauthlib to v4.0.1 [SECURITY]
- #5773: Publish changelog for api-2026.11.15.02.59.49
Catalog
- #5771: Publish changelog for catalog-2026.11.15.00.30.07
Documentation
- #5741: Update dependency urllib3 to v2.8.0 [SECURITY]
- #5747: Update dependency soupsieve to v4 [SECURITY]
- #5771: Publish changelog for catalog-2026.11.15.00.30.07
- #5772: Publish changelog for frontend-2026.11.15.02.59.47
- #5773: Publish changelog for api-2026.11.15.02.59.49
- #5774: Sign Nitro’s API requests instead of an internal route in the proxy plan
Frontend
- #5750: Update @openverseOpenverse Openverse is a search engine for openly-licensed media, including images and audio. Find Openverse on GitHub and at https://openverse.org./eslint-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.
- #5759: Disable the preferences switches until the page hydrates
- #5772: Publish changelog for frontend-2026.11.15.02.59.47
Management
- #5739: Update dependency torch to v2.13.0 [SECURITY]
- #5740: Update dependency tornado to v6.6.1 [SECURITY]
- #5741: Update dependency urllib3 to v2.8.0 [SECURITY]
- #5742: Update dependency cryptography to v49 [SECURITY]
- #5743: Update dependency filelock to v4 [SECURITY]
- #5744: Update dependency fsspec to v2026 [SECURITY]
- #5745: Update dependency pillow to v13 [SECURITY]
- #5746: Update dependency setuptools to v84 [SECURITY]
- #5747: Update dependency soupsieve to v4 [SECURITY]
- #5763: Update dependency mistune to v3.3.3 [SECURITY]
- #5765: Update dependency notebook to v7.6.3 [SECURITY]
- #5767: Update dependency cryptography to v50 [SECURITY]
Closed issues
openverse-infrastructure
Merged PRs
Catalog
- #1188: Bump catalog to Airflow 2.11.1
Infra
Management
What's new in Gutenberg 24.4? (12 November)
“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 Editor.

What’s new in
Gutenberg 24.4?
Gutenberg 24.4 is released and available for download!
This release adds emoji reactions and search to Notes, improves content-only editing across more blocks, and brings more controls in line with the WordPress Design System. The experimental Media Editor gains PDF previews and clearer file details. Draft content gets extra protection when restoring browser backups, while Rich Text and 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. parsing get performance improvements. Developers also get an experimental PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher runtime for wp-env. All of this thanks to a fantastic team of contributors, including five first-timers.
Find the right note faster
Notes gain search across comments, replies, and author names, plus filtering by open/resolved status.

Compact note emoji reaction picker
Reacting to notes now takes less space, with a compact horizontal emoji picker that keeps the conversation in view (#85819). New thumbs-up and plus reactions give you more ways to show agreement or support without adding another reply (#85565).
Understand what’s overriding your Global Styles
Global Styles now shows an “Overridden by” list for elements such as headings, links, and buttons, making it clearer when coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks have styles that take precedence (#84671). Each item links directly to the block’s style settings, so you can find and adjust the override without hunting through the block list.

Changelog
Features
- wp-env: Add an experimental runtime using locally installed PHP and SQLite. (85512)
Enhancements
Components
- RadioControl: Place group help text below the fieldset label and remove its legacy
components-base-control__helpclass. (85126) - UIUI User interface: Add Menu width presets and make Select and SelectControl popup presets size to content up to a maximum width. Use CSSCSS Cascading Style Sheets. when a fixed width is required. (84086)
- DataViews: Standardize action-label punctuation. Consumers should supply labels without ellipses; modal menu actions add translated ellipses. (85396)
- Align focus indicators across AlignmentMatrixControl, DataViews grids, FormToggle, Modal scrollable content, RangeControl, RotationRuler, and disabled items. (85528, 85364, 85285, 85251, 85536, 85535, 86125)
- Badge: Add optional infotips using a consumer-supplied Popover. (85309)
- Align Modal colors and corners, and Tooltip backgrounds, with the design system. (85855, 85858)
- Migrate CustomGradientPicker and BackgroundClipControl select controls to
@wordpress/ui. (85750, 86046) - DataViews: Migrate Sort by and relative-date Unit controls to
@wordpress/ui. (86167) - DataViews: Use
@wordpress/uibuttons in the bulk actions bar. (85939) - Align the standalone Spinner appearance with the design system and scale its stroke width with its size. (85859, 85378)
- Theme: Report insufficient contrast of focus-ring and strong brand-fill colors against theme surfaces. (85449)
- Use solid brand highlights for popup items. (84583)
Block Library
- Improve content-only editing for Button content, Comments Pagination link labels, and Query 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 pagination link labels. (84854, 86175, 70165)
- Add border support to Comments Pagination Numbers, and border and padding support to Query Pagination Numbers. (85164, 85245)
- Migrate select controls in the Archives, Audio, File, Latest Comments, List, Playlist, Post Author AvatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name., Social Icons, and Tag Cloud blocks to
@wordpress/ui. (86137, 86194, 86199, 86138, 86141, 86161, 86160, 86196, 86198) - Remove the Auto/Manual grid toggle and add an experimental Canvas variation of the Group block. (85985)
- Social Icon: Support editing the link from the inspector. (84860)
Block and Site Editors
- Rich Text: Give formats in the More dropdown a consistent order and reserve dedicated name-based toolbar slots for known core formats. (85843)
- Add an alignment-menu action to select the block constraining a child block’s width. (82607)
- Guard entity preload filters and share entity actions and fields logic. (85390)
- Experimental Site Editor v2: Unregister the View 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. action on the server. (85279)
Design Tools and Global Styles
- Show an icon for each aspect ratio option in the Dimensions tool. (85812)
- Global Styles: List core block types that override an element’s styles. (84671)
- Place background and text colors first in the color palette. (62548)
Media
- Experimental media editor: Show file type and size 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. and reposition the settings dropdown. (86154, 86020)
- Add PDF previews to the experimental media editor. (86002)
- Animate the media 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. when opening and closing it. (85889)
- Group Reset and Restore original under a History menu. (85891)
- Prevent MediaEdit item-removal animations. (85372)
Collaboration
- Hide collaborator avatars while typing. (83490)
- Notes: Add search and a status 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 the All Notes sidebar. (84060)
- Notes: Add thumbs-up and plus reactions, and show the reaction picker as a row of emoji. (85565, 85819)
Dashboard and Widgets
- WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Dashboard: Forward grid settings to the surface. Stop applying the automatic 600px and 960px breakpoints to numeric column counts; hosts that relied on them must supply a column-step map. Render positive row heights without snapping to presets. (85228)
- Add
useWidgetIdentityfor translated widget titles. (85729) - Support an
exampledeclaration inwidget.json. (85240) - Grid: Support column-count steps based on container width. (85216)
Icons
- Add the database icon and expose error, info, and postComments in the
core-admincollection. (85273, 85452) - Promote Dashicon replacements to the
core-admincollection and map their Dashicons. (85541)
Developer Tools
- Design System MCP: Add pattern tools using Storybook MDX manifest output. (84864)
- Storybook: Show icon details in the Icon Library. (86057)
- Limit wp-build esbuild concurrency. (79889)
Bug Fixes
Components
- CheckboxControl: Use design system color tokens; legacy
--wp-components-color-accentand--wp-components-color-accent-invertedoverrides no longer apply. Use ThemeProvider for customization. (85856) - Widget Dashboard: Give the footer strip a consistent height. (85237)
- BoxControl: Add fallback units for the input slider. (70288)
- DataViews: Correct filter-chip focus styling and prevent the remove button from overlapping chip text. (85374)
- ColorPicker: Preserve hex and RGB edits when the picker closes. (85734)
- ControlWithError: Skip unchanged validity-state updates. (85479)
- Core fields: Preserve status-icon sizing when labels wrap and remove extra spacing in slug inputs. (85828, 85935)
- DataViews: Use a page-number input for pagination above 100 pages. (85303)
- DropdownMenu: Account for Button borders in menu-item padding. (85503)
- Keep MenuItem and ToggleGroupControl widths stable when selection changes. (85831, 85454)
- Modal: Restore each modal’s
aria-hiddenstate when modals close out of order. (85720) - PaletteEdit: Preserve existing slugs when deduplicating presets. (85817)
- ToolsPanel: Keep Reset labels visible on highlighted menu items. (86045)
- Calendar: Show only the day number in day cells. (86010)
Block Library
- Table: Keep the selected cell on the first click into an unselected table. (86757)
This was introduced in 24.4.1. - Comment Author Avatar: Pass the configured size to
get_avatar(). (86113) - Comments Pagination Next: Remove the link filter from the correct hook. (85244)
- Cover: Prevent Navigation overlays from being clipped in Safari. (86041)
- Playlist: Preserve track metadata after failed replacement uploads, handle URLs containing query-string ampersands, and render tracks without attachment IDs. (86018, 85931, 83880)
- Table of Contents: Show previewed headings in published-post previews and keep list styles editable in templates. (86155, 86251)
- Heading: Preserve combining marks in generated anchors. (85096)
- Navigation Link: Preserve text formatting when editing in the sidebar. (85223)
- Page List: Keep pages visible in the Navigation sidebar. (85357)
- Paragraph: Support removing theme-disabled drop caps and avoid empty toolbar groups when alignment controls are unavailable. (84839, 85796)
- Social Icon: Prevent closing a popover from stealing focus. (86215)
- Social Links: Restore the larger icon size for the Logos Only style. (85506)
- Tabs: Correct the classic-theme selector for tab-button styles. (85504)
Editors and Saving
- Rich Text: Handle full-content deletion through
beforeinput, including Safari deletion commands. (85886) - Copy the text of bound fields. (85403)
- Preserve HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. anchors when editing as HTML and converting Classic blocks. (82836)
- Inserter: Keep focused results below the sticky search field. (85706)
- Link Control: Preserve preview focus while the selected post’s record loads. (85945)
- Match the block-visibility viewport once per canvas. (85808)
- Preserve child layout attributes when transforming a block. (85045)
- Rich Text: Remove stale format boundaries when a field loses selection. (86168)
- Correct non-breaking-space replacement behavior and its tooltip. (85873, 85777)
- Writing flow: Correct triple-click list selection, parent-block select-all behavior, and arrow-key navigation at viewport edges. (85569, 85987, 85408)
- Raw handling: Keep shortcodes within text inline. (85795)
- Vertically center the Categories loading spinner. (85563)
- Save current content before restoring a browser backup. (85406)
- Revisions: Include only revisioned metadata in revision REST responses. (85509)
- Command Palette: Correct the classic-theme guard for template commands. (86142)
Design Tools and Global Styles
- Apply globally: Show the block type’s current value. (84823)
- Contrast checker: Check the visible color of text clipped to its background. (86148)
- Global Styles: Preserve individual sides when editing padding and margin shorthand. (85437)
- Typography: Clear the synced link color when resetting all settings. (85376)
- Pass
blockNameto style-state inspector slots. (86084) - Allow separate row and column block gaps in the block-style 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. schema. (86044)
- Allow CSS custom properties when sanitizing block gaps. (82817)
- KSES: Allow CSS color functions in inline styles. (84213)
- Correct the deprecated duotone render wrapper’s arguments and document known limitations in deprecated duotone functions. (68397)
- Duotone: Avoid undefined-array-key warnings when parsing hue units. (68399)
Media
- Experimental media editor: Correct canvas border radii and footer controls. (86143)
- RotationRuler: Keep the center marker visible in forced-colors mode. (85546)
- Prevent endless image-sideloading loops when the browser cannot decode a large image. (83530)
Collaboration
- Notes: Handle inline notes in merged text. (85744)
- Notes: Handle notes shared by duplicated or split blocks. (85906)
- Notes: Share thread-focus recovery across actions. (85455)
- Notes: Correct reaction-deletion permissions, including author checks and preventing changes on resolved threads. (85415, 85883)
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.
- Ignore router regions and
attachTotargets insidedata-wp-htmlcontent. (84919) - Load Interactivity Router script modules without
eval()or WebAssembly to support Content Security Policy restrictions. (84056)
Developer Tools
- Storybook: Match icon labels when searching the icon library. (85399)
- Storybook: Remove BaseControl from the component manifest. (85847)
- Update the sprintf dependency to resolve TypeScript module-resolution issues. (85562)
- wp-env: Preserve Debian security updates in Bullseye-based images. (85469)
- wp-env: Report the PHP runtime’s actual automatically selected port and preserve it when resetting the site. (85574)
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)
- Prevent invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. LaTeX from trapping keyboard focus in the Math block and inline math controls. (86027)
- Migrate Separator and Table of Contents select controls to
@wordpress/ui. (86047) - Modal: Preserve dialog boundaries in forced-colors mode. (85888)
- UI: Add
Notice.Listwith live announcements. (85209) - Notes: Show reaction pills’ pressed state in forced-colors mode. (85904)
- Give URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org submit buttons consistent identification. (85725)
- Improve the accessibility and usability of the error copy button. (85477)
- Grid: Preserve tile content semantics when dragging is disabled. (84869)
Performance
- Reduce Rich Text initialization and editing overhead by batching DOM updates, parsing unfocused fields on mount, and simplifying field registration, event listeners, selection tracking, and undo handling. (85177, 85874, 86007, 86021, 85887, 85994, 85983)
- Reduce block action and store-subscription overhead. (85991, 85804)
- Preserve unchanged blocks when resetting content so undo does not re-render the entire post. (85427)
- Skip measuring the collaborators overlay when there is nothing to draw. (85179)
- ThemeProvider: Use prebuilt color ramps for the default seeds. (85182)
- withFilters: Track mounted instances in a Set. (86012)
- Log block migrations only when
SCRIPT_DEBUGis enabled. (85736) - Expose script exports on globals as data properties. (85180)
- Reduce parser memory use and processing time for documents with deeply nested, unclosed blocks. (74427)
Documentation
- Add agent guidance for escaping PHP output and preventing cross-site scripting. (84596)
- Add migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. guides for CustomSelectControl and SelectControl. (85377, 85220)
- Document
createInterpolateElementin the internationalization guide. (86015) - Clarify the design system introduction and document the legacy-component replacement process. (85764, 85480)
- Focus package changelogs on consumer-facing changes. (85079)
- Document SelectControl callbacks when reselecting the current value. (86200)
- Add DropdownMenu selection stories. (85551)
- Document the 7.1.4 security 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. releases. (85930)
- Add a Design System MCP page to Storybook. (85464)
- Add guidance for agents reading Storybook without 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. (85757)
- Complete Storybook guidance for copy-to-clipboard feedback. (85745)
- Correct minified component names in Storybook code snippets. (85966)
- Make the Save & Submit Canvas example fully copyable and add a Notice disclosure composition example. (85766, 84627)
- Keep documentation before attached, named MDX pages in Storybook. (85308)
- Remove ThemeProvider’s private badge in Storybook. (85529)
- Update Figma border-import documentation. (85304)
- Document
npm run other:cherry-pick -- --dry-runin the release guides. (85465)
Code Quality
Components
- Remove the public
checkbox-controlandradio-controlSass mixins from@wordpress/base-styles; their styles now live in CheckboxControl and RadioControl. (85248) - Require distinct aliases for legacy IconButton, Menu, Notice, Popover, Tabs, validated controls, Card, and VisuallyHidden imports. (85846, 85845, 85839, 85838, 85852, 85950, 85519, 85837)
- Replace legacy DataViews selection-indicator mixins. (85191)
- Deprecate the legacy FormToggle, Tooltip, ProgressBar, TabbableContainer, and CustomGradientPicker components. (85517, 85518, 85520, 85521, 85953)
- Restore change-case for component class-name generation. (85192)
Icons
- Update
lockto use the former outline artwork and remove thelockOutlineandlockSmallexports. (85740) - Remove the
insertBefore,insertAfter, andofflineicon exports. (85445)
Blocks and Editors
- Reduce effects in core blocks using render-time state, core-data,
useEvent, anduseRefEffect, and restrict new effects with a lint rule. (85814, 85864, 85810, 85862, 85867) - Remove unused Button outline styles and redundant Site Title fit-text CSS. (85471, 85166)
- Correct PHPDocPHPDoc (docblock, inline docs), private static access, redundant conditions, and return values in block rendering and style support. (86092, 86090, 86094, 86091)
- Use null-coalescing assignment for Navigation, Tab Panel, and background-size defaults. (86033, 85548)
- Navigation: Replace the button block appender with a dropdown appender. (70524)
- Remove ignored
parseFloatradix arguments and an unused SpacingSizesControl constant. (85163, 85877) - Centralize focus-capture prevention once per canvas. (85815)
- Remove non-iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. 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.-box code from Edit Post. (86009)
- Set welcome-guide preferences to false when closing the guides. (85742)
Media
- Simplify cropper state and instruction handling and remove unnecessary media-editor effects. (85881, 86147, 85882, 85880)
- Tidy cropper code before exposing it. (85429)
Styles and Server APIs
- Correct theme JSON types, cached-property PHPDoc, and private static calls, and simplify CSS-variable matching. (68407, 86111, 86096, 68386, 68401)
- Make PHP types explicit and simplify duotone, layout, shadow, style-variation, typography, and compatibility code. (68405, 68389, 68404, 68398, 68396, 68392, 86099)
- Remove the Global Styles inheritance-indicators experiment. (85884)
- Use
gutenberg_prepare_json_value_for_client()for view configurations and entity fields. (85206) - Move the Site patterns view-configuration change into the WordPress 7.2 compatibility directory. (85905)
- Remove obsolete
--wp-components-color-*overrides. (85938)
TypeScript
- Expand TypeScript coverage for block-editor components, core-data utilities and actions, Patterns stores, and Core Commands; add split TypeScript configuration and a typed test to Blocks. (84950, 85058, 85070, 85534, 85253, 84385)
- Convert package tests and test utilities to TypeScript across Components, DOM, LaTeX to MathML, Redux Routine, Element, API Fetch, Viewport, Plugins, E2E Test Utils, 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., and Preferences Persistence. (85150, 85161, 85084, 85121, 85159, 85145, 85115, 85088, 84917, 85141, 85162)
Tools
Testing
- Add split TypeScript configuration for most packages to support typed tests, and disable Vitest CommonJS globals injection. (85470, 85878)
- Add
npm run browsefor driving the local WordPress site from the command line. (85525) - Stabilize drag tests by handling insertion-indicator remounts and setting the initial caret position. (85270, 85988)
- Improve synchronization in autocomplete, rich-text selection, link-field, cut-and-paste, template, and editor-canvas tests. (85572, 85975, 85996, 85976, 85978, 85974)
- Stabilize the Interactivity Router URL-fragment navigation test. (85473)
- Replace the Page List unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. with end-to-end coverage, update entity-fields assertions for Core trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running “trunk”, then you are on the latest revision., and use real components in interface tests. (85564, 85201, 86171)
- Remove redundant Site Editor and comments-count checks and simplify entity-action loader test labels. (85259, 85979, 85798)
- Shrink and speed up the block Notes end-to-end tests. (86209)
- Measure page-load performance without tracing and record end-to-end traces only on failed-test retries. (86025, 85428)
- Run end-to-end tests in parallel with a separate wp-env site per two CPU cores. (85420)
- Stabilize web-editor selection tests in iOSiOS The operating system used on iPhones and iPads. Safari. (85461, 85481)
Build Tooling
- Docgen: Remove Babel core, project Babel-configuration support, and support for syntax requiring custom parsers, including Flow. (85183)
- Move theme build and Stylelint plugins to
@wordpress/theme-build-toolsand remove their old@wordpress/themeexports; consumers must update their imports. (83568) - wp-build: Pass
falseinstead of an empty string as the source inwp_register_script(). (86106) - Introduce PHPStan level-5 analysis, a dedicated tooling workspace, updated WordPress stubs, and corrected baseline configuration. (66693, 86222, 86109, 86093)
- Load Storybook previews from a Blueprint bundle. (85946)
- Update Storybook to 10.6.5 and
@storybook/iconsto 2.2.0, including Vitest addon fixes. (86172, 85741) - Update Vite to 8.3.5 and Vitest to 5.0.5. (85739, 86173)
- Streamline CI with lighter runners, scoped changelog checks, updated baseline tooling, and fresher reads of unfinished-job status. (85907, 85459, 85076, 85077)
- Warn when 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. fix’s new end-to-end test also passes on trunk. (85717)
- Migrate the build pipeline from esbuild to Rolldown. (85476)
- Remove the legacy Storybook manifest shim and type-check manifest post-processing scripts. (85778, 85769)
- Declare
@wordpress/themeas a peer dependency of@wordpress/theme-build-tools. (85388) - Update Terrazzo token-generation tools to 2.10.0. (85737)
- Remove redundant
tsconfig.test.jsonfiles from split packages. (85516) - Derive wp-build CSS-module class names from each stylesheet’s CSS. (85900)
- Improve ESLint component recommendations with migration-guide links,
getWpCompatOverlaySlotguidance, and per-import exceptions. (85752, 85835, 85188)
Repository and Release Management
- Update PHPStan tooling ownership rules. (86204, 86112)
- Move backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. changelog entries into the appropriate WordPress 7.2 and 7.3 directories. (85064, 85418)
- Configure the props bot’s introduction through the action input. (83917)
- Require a hash-prefixed issue number or full issue URL when assigning fixed issues. (86130)
- Correct the
.gitignorecomment about re-included.cachepaths. (85375)
First-time contributors
The following PRs were merged by first-time contributors:
- @justlevine: Add PHPStan static analysis at rule level 5. (66693)
- @lucatume: iOS tests: De-flake the selection handle test. (85461)
- @mattmiklic: Theme: Update Figma border import documentation. (85304)
- @RajkiranBagal: DataViews: Use a page number input in the footer pagination above 100 pages. (85303)
- @theritiktiwari: Fix typo in .gitignore comment about re-included .cache paths. (85375)
Contributors
The following contributors merged PRs in this release:
@00kaku @aaronrobertshaw @adamsilverstein @adamwoodnz @aduth @amitraj2203 @andrewserong @ciampo @CookieDarb @DAreRodz @desrosj @DevinWalker @dmsnell @draganescu @drewmt @ekamran @ellatrix @fushar @hbhalodia @himanshupathak95 @huubl @huzaifaalmesbah @im3dabasia @jasmussen @jeryj @jorgefilipecosta @jsnajdr @justlevine @karthikeya-io @kushagra-goyal-14 @lazerg @louwie17 @lucatume @luisherranz @Mamaduka @manzoorwanijk @mattmiklic @mcsf @mikachan @mirka @noruzzamans @ntsekouras @oandregal @peterwilsoncc @R1shabh-Gupta @RajkiranBagal @ramonjd @retrofox @SainathPoojary @salvatorecorsi @sarthaknagoshe2002 @shail-mehta @simison @singhakanshu00 @sirreal @Soean @stokesman @t-hamano @tellthemachines @theaminulai @theritiktiwari @USERSATOSHI @westonruter @yashjawale @youknowriad
Kudos to all the contributors that helped with the release! 👏
Introducing Mētis, Our New Flagship Theme
Mētis is a theme for creators in an unmapped moment: people who work in more than one form and keep finding their way as the work changes.
It began as our first direction for the next default theme. As we shared when we introduced Ipsum, Mētis continues on its own, and at @matt’s request it’s now our flagship theme. A default has to work for every site; a flagship can go further and show what the Editor can do today.
How We came to It
The theme is named after an ancient Greek word for cunning intelligence: reading a situation as it shifts and finding a way through with whatever is at hand. It is the adjective Homer uses to describe Odysseus in the “mother of all stories,” which inspired this project.
We started from that idea and from the people it describes: writers, designers, and makers whose work keeps changing shape, who hold many things at once and keep going without a complete map. We built the theme in the Site Editor, with real content from the start.



What’s Inside
Templates
Six starter sites, each one a page template and a page pattern you can drop into a new page:
- Business: the studio page, with services, the team, a testimonial, and pricing.
- News: the paper front page, with a featured story, the latest news, and the archive.
- Magazine: the magazine’s current issue, a 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. by categoryCategory The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., and the people who make it.
- Portfolio: The designer’s profile, selected work, awards, experience, and a playlist.
- Writer: The writer’s home, with a portrait, her new book and its reviews, then writings, books, and talks.
- Personal: The developer’s portrait, selected builds and her latest posts.
Around them sit the everyday templates. Single posts come in three layouts. Pages can show their title or hide it. Three headers and five footers put diversity into practice as templates change with a single swap.



Patterns
Mētis ships with fifty section patterns, grouped by category and named after their description to welcome users and AI agents. And with a few 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. styles to carry on the theme’s character.



Style variations
Six style variations change the type and color of the whole site at once. One is a dark version of the default, and visitors can switch to its colors through some headers and the navigation overlay. Each palette also pairs a day and a night duo to rule the sections with gradients, changing automatically when the visitor’s device switches to dark mode.
Behind all of them, nine open-source type families are bundled with the theme: old-style and blackletter-inspired serifs, geometric and grotesque sans serifs, and a monospace.



Development
As part of the 7.2 release, Carolina Nymark (@poena), Maggie Cabrera (@onemaggie), and Juanfra Aldasoro (@juanfra) are leading development, while Henrique Iamarino (@iamarinoh) is leading design and theme building. The current build reflects the design work; the formal development review comes next, folding in what we hear from you along the way—we look forward to your involvement throughout the process.
Learn more
For information about previous default themes, read the following posts:
- Ipsum
- Twenty Twenty-Five
- Twenty Twenty-Four
- Twenty Twenty-Three
- Twenty Twenty-Two
- Twenty Twenty-One
- Twenty Twenty
Here are a few resources if you’re interested in learning more about Block Themes and the Site Editor:
- Block Theme documentation
- Global Styles & theme.json documentation
- A Developers Guide to Block Themes
- Develop Your First Low-Code Block Theme
+make.wordpress.org/themes/#7-2, #bundled-theme, #core-themes, #ipsum, #metis
A memorable name and a modern, impressive design. I really like the first impression!
One small UX issue in my opinion:
While clicking around and testing the theme, it took me a moment to understand why it suddenly switched to dark mode.
It’s not immediately obvious that the button appearing after opening the hamburger menu serves two different purposes: closing the menu and switching between light and dark mode.
At first glance, it looks like a regular close button with an additional icon. I didn’t realize that the icon was actually a theme toggle.
I’d suggest making these two actions visually more distinct.
Looking at it again, I think the main UX issue is that the theme toggle and the close action are visually combined into what looks like a single button.
As users, we’re generally used to one button performing one action. Here, the sun icon and the CLOSE label share the same button background, with no visible separation suggesting that they are actually two independent clickable areas.
So when I clicked the sun icon, I didn’t realize I was activating a theme toggle. For a split second, I thought the page turning dark was just some kind of visual transition effect.
Then I clicked CLOSE, which also made the theme toggle disappear. I was suddenly in dark mode without immediately understanding what had happened or how to switch back.
I’d suggest either separating these into two visually distinct buttons or keeping the theme toggle permanently visible outside the menu.
Thank you for all the hard work and creativity that went into this beautiful theme. My only complaint is that you’re now making me choose between Ipsum and this for which theme to use.
While it looks nice, there’s a couple things I’ve noticed after browsing the demo site for less than 2 minutes, that need to be fixed before it’s ready for release.
– The (dark/Light) colour changer icon and the menu Close link are styled like they’re one single button, when they’re actually two separate links. It’s incredibly poor usability. There should be a clearer distinction that they’re two separate links, and they shouldn’t be styled like they’re part of one single button.
– The ‘Back to Top’ and the WordPress links don’t work in the footer. This is because that whopping big paragraph block at the very bottom of the site overlays them both.
matt’s request it’s now our flagship theme …
As part of the 7.2 release …
What are the differences between a default theme and a flagship theme? How are they bundled into a core release? Is the Mētis theme going to be a part of the WordPress 7.2 release?
The overlay menu needs attention (not entirely related to Mētis) – the UX of when you click the button to open and then the relation of where the ‘Close’ button and Dark/Light mode toggle sit is asking for the user to: Click open quick and accidentally click Dark/Light mode toggle quick. If they’re clicking around then they’ll get an odd experience. Get the positioning right and it’ll allow for better experience. Honestly, I’m not even sure the Dark/Light mode toggle is necessary.
[uk] Quality Assurance Audit of…
[uk] Quality Assurance Audit of WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Translation (6.8–7.0.x): Systemic Review Issues & Cleanup Request
Hello Polyglots TeamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/ and LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ Mentors,
I am writing to raise a serious concern regarding the current quality assurance (QA) and approval workflow for the Ukrainian (#uk) localizationLocalization Localization (sometimes shortened to “l10n“) is the process of adapting a product or service to a particular language, culture, and desired local “look-and-feel.” of WordPress Core.
A recent spot-check of approved stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in the 7.0.x Core branch revealed systemic quality issues that directly affect user experience, technical accuracy, and interface consistency. Please note that the 20 examples documented below represent only a fraction of the issues found during a brief sample audit — they are the tip of the iceberg, indicating a broader lack of editorial review before strings are approved.
Furthermore, this is not an isolated issue specific to the 7.0.x development cycle. Because GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. propagates approved strings forward between major releases, these exact mistranslations, broken date formats, and glossary violations have been carried over across multiple stable release cycles (6.8, 6.9, and now 7.0.x) without ever being caught or corrected by the current review process.
Below is a categorized breakdown of confirmed, approved strings in wp/7.0.x/uk/default with direct links, exact explanations of the errors, and standard corrections.
1. Critical Technical Bugs & Broken Formatting
- Broken PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php
date()format specifier (Dinstead ofd)- Link: Original #32876271
- Original (
Note date full date format):F j, Y g:i a - Approved:
D.m.Y H:i - Issue: In PHP
date()/wp_date(), uppercaseDoutputs an abbreviated weekday name (e.g., Чт), whereas lowercasedoutputs the day of the month. As approved, the UIUI UI is an acronym for User Interface – the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. outputs broken strings likeЧт.11.2026 14:35, completely omitting the day of the month and ignoring thefull date formatcontext. - Correction:
j F Y H:i(for full date format) ord.m.Y H:i(for numeric format).
2. Severe Mistranslations & Blind Machine Translation (Misleading UI)
- Core entity substitution:
file typetranslated as “Post Type”- Link: Original #32876386
- Original:
%s: Sorry, you are not allowed to upload this file type. - Approved:
%s: На жаль, вам не дозволено завантажувати цей тип записів. - Issue:
file typeis mistranslated as «тип записів» (Post Type), which is a completely different WordPress entity. Users attempting to upload a restricted file format receive a nonsensical error about “post types.” - Correction:
%s: На жаль, вам не дозволено завантажувати файли цього типу.
- Mistranslated error message:
set as thumbnailconfused with “size” + glossary violation- Link: Original #32876465
- Original:
Could not set that as the thumbnail image. Try a different attachment. - Approved:
Не вдається задати розмір мініатюри. Спробуйте інше долучення. - Issue:
set that as the thumbnail imagewas misread as “set thumbnail size” («задати розмір мініатюри»), misinforming the user about the cause of the error. Additionally,attachmentviolates the official#ukglossary, which defines it as вкладення rather than «долучення». - Correction:
Не вдалося встановити це зображення як мініатюру. Спробуйте інше вкладення.
- Double entity mistranslation in 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 UI (
block“locking”,document“documentation”)- Link: Original #32876337
- Original:
Access all block and document tools in a single place. - Approved:
Доступ до всіх інструментів блокування та документації в одному місці. - Issue: Unedited machine translation turned
block(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/ content block) into «блокування» (blocking/locking) anddocument(the current post/page being edited) into «документації» (technical documentation). - Correction:
Доступ до всіх інструментів блока і документа в одному місці.
- Nonsensical translation of
visual emphasisas “surveillance/supervision”- Link: Original #32876683
- Original (
block description):Give special visual emphasis to a quote from your text. - Approved:
Надайте особливий нагляд на цитату з тексту. - Issue:
visual emphasisis mistranslated as «нагляд» (supervision/surveillance), paired with an ungrammatical Ukrainian preposition structure («надайте … на»). - Correction:
Візуально виділіть цитату з вашого тексту.
- Technical term
tabs(tab characters) mistranslated as “browser tabs”- Link: Original #32876681
- Original (
block description):Add text that respects your spacing and tabs, and also allows styling. - Approved:
Додайте текст, який відповідає вашим інтервалам і вкладкам, а також дозволяє стилізувати. - Issue: In the context of the Preformatted block (
),tabsrefers to tab characters/indentation, not UI «вкладкам» (browser tabs). Furthermore,respects spacingis mistranslated as «відповідає вашим інтервалам» instead of preserving whitespace. - Correction:
Додайте текст, який зберігає ваші пробіли та символи табуляції, а також дозволяє налаштувати оформлення.
- Broken syntax and unedited machine output in Verse block description
- Link: Original #32876766
- Original (
block description):Insert poetry. Use special spacing formats. Or quote song lyrics. - Approved:
Вставити вірші. Використовуйте спеціальні формати інтервалу. Або цитата лірика пісні. - Issue: Mixes infinitive («Вставити») with imperative mood («Використовуйте») and ends with a completely broken, non-Ukrainian fragment («Або цитата лірика пісні» — literally “Or quote lyricist of a song”).
- Correction:
Вставте поезію. Використовуйте спеціальні формати інтервалів. Або процитуйте тексти пісень.
- Color name hallucinations & mistranslations (
Pale cyan blue,Light green cyan)- Link 1: Original #32876806
- Original (
Color name):Pale cyan blue - Approved:
Блідий зеленувато-блакитний(hallucinated “greenish” where none exists incyan blue). - Correction:
Блідий блакитно-синійorБлідо-блакитний.
- Original (
- Link 2: Original #32876804
- Original (
Color name):Light green cyan - Approved:
Легкий зелено-блакитний(translatesLightas “lightweight/easy” — «Легкий» — instead of “light/pale” — «Світлий»). - Correction:
Світлий зелено-блакитний.
- Original (
- Link 1: Original #32876806
- Literal calques distorting UI concepts (
break“recess/intermission”,separator“separator device”)- Link: Original #32876719
- Original (
block description):Create a break between ideas or sections with a horizontal separator. - Approved:
Створіть перерву між ідеями або розділами з горизонтальним сепаратором. - Issue:
breakis translated as «перерву» (a coffee/work break) instead of a visual break/divider («розрив» or «проміжок»), andseparatoris calqued as «сепаратором» (an industrial centrifuge/device) instead of the standard UI term «розділювач». - Correction:
Створіть розрив між думками або розділами за допомогою горизонтального розділювача.
- Inappropriate semantic choice for
override(“neglect/disregard”)- Link: Original #32876267
- Original:
Changes will apply to new posts only. Individual posts may override these settings. - Approved:
Зміни будуть застосовуватися лише до нових записів. Окремі записи можуть нехтувати цими налаштуваннями. - Issue:
overrideis translated as «нехтувати» (to neglect/disregard), which carries a negative colloquial meaning and breaks lexical compatibility with an inanimate subject (“posts”). Also uses a non-standard passive form instead of the Ukrainian impersonal predicate («Зміни буде застосовано…»). - Correction:
Зміни буде застосовано лише до нових записів. Окремі записи можуть перевизначати ці налаштування.
3. Direct Violations of the Official Ukrainian Glossary
Even terms explicitly defined in the #uk Locale Glossary are consistently ignored in approved Core strings:
- Double glossary violation in a single stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. (
Displayandfeed)- Link: Original #32876712
- Original (
block description):Display entries from any RSS or Atom feed. - Approved:
Показати елементи з будь-якої RSS- або Atom-стрічки. - Issue: Glossary defines
Displayas відображати (contextually Відображає, not «Показати») andfeedas канал (not «стрічки»). - Correction:
Відображає записи з будь-якого каналу RSS або Atom.
- Glossary violation (
Display) + Ukrainian euphony rule violation (вinstead ofу)- Link: Original #32876697
- Original (
block description):Display the total number of results in a query. - Approved:
Показати загальну кількість результатів в запиті. - Issue: Uses «Показати» instead of the glossary term відображати (Відображає), and violates mandatory Ukrainian phonetic alternation rules («результатів в запиті» instead of «результатів у запиті» between consonants).
- Correction:
Відображає загальну кількість результатів у запиті.
- Glossary violation (
media libraryreplaced with «Медіафайлів»)- Link: Original #32876774
- Original (
block description):Embed a video from your media library or upload a new one. - Approved:
Вставте відео з Медіафайлів або завантажте нове. - Issue: Ignores the official
#ukglossary entry formedia library(бібліотека медіа — note that the compound noun медіабібліотека is more natural in modern Ukrainian, yet the approved string violates even the official glossary by using «Медіафайлів» with inconsistent capitalization). - Correction:
Вставте відео з бібліотеки медіа або завантажте нове.
- Glossary violation (
custom«спеціальні» instead of «власні»)- Link: Original #32876726
- Original (
block description):Insert additional custom elements with a WordPress shortcode. - Approved:
Вставте додаткові спеціальні елементи за допомогою короткого коду WordPress. - Issue: Official glossary defines
customas власний (note: in modern technical Ukrainian, довільні would actually be more accurate in this context, showing that the glossary itself is outdated — yet the approved string violates even the official glossary by using «спеціальні» / special). - Correction:
Вставте додаткові власні елементи за допомогою короткого коду WordPress.
- Glossary violation (
deprecated«застарів» instead of «застарілий» &Columns«стовпці»)- Link: Original #32876763
- Original (
block title):Text Columns (deprecated) - Approved:
Текстові стовпці (застарів) - Issue: Official glossary defines
deprecatedas застарілий (not the finite verb «застарів») andcolumnas колонка (not «стовпці»). - Correction:
Текстові колонки (застарілий)
- Glossary violation (
Columns«стовпців» instead of «колонка», plus missing quotes/capitalization)- Link: Original #32876764
- Original (
block description):This block is deprecated. Please use the Columns block instead. - Approved:
Цей блок застарілий. Замість цього скористайтеся блоком стовпців. - Issue: Official glossary defines
columnas колонка. Furthermore, in Ukrainian UI typography, any inline reference to block names, sections, or menu items (when not standing alone as a heading or button) must be enclosed in guillemets with the first word capitalized (блок «Колонки»). - Correction:
Цей блок застарілий. Натомість використовуйте блок «Колонки».
4. Severe Inconsistency, Broken Syntax & Structural Calques
- Unjustified punctuation alteration (
(4:3)instead of— 4:3) + grammatical gender mismatch- Link 1: Original #32876810
- Original (
Aspect ratio name):Standard - 4:3Approved:Стандартний (4:3) - Correction:
Стандартне — 4:3
- Original (
- Link 2: Original #32876809
- Original (
Aspect ratio name):Square - 1:1Approved:Квадрат (1:1) - Correction:
Квадратне — 1:1
- Original (
- Issue: First, the
#ukglossary lacks an entry foraspect ratio(співвідношення сторін). Grammatical gender here depends on the implied head noun: masculine if tied to «формат» (format), or neuter if tied to «співвідношення сторін» (aspect ratio). Since «формат» is already reserved in WordPress for another entity (Post Format— формат запису), adjectives must agree with neuter «співвідношення сторін» (Стандартне,Квадратне). Instead, the approved strings replace the separator with parentheses (a structural calque from third-party localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/) and mix a masculine adjective («Стандартний») with a noun («Квадрат»). Furthermore, per Ukrainian orthography and typography rules, a spaced em-dash (—) must be used here—and generally across the UI for semantic pauses, value clarifications, and ranges—rather than an ASCII hyphen (-), which is strictly an intra-word sign.
- Link 1: Original #32876810
- Contradictory translations of
namein two adjacent strings of the same UI form- Link 1: Original #32876413
- Original:
This category already exists. Please use a different name.Approved:Ця категорія вже існує. Будь ласка, скористайтеся іншим ім'ям. - Correction:
Ця категорія вже існує. Введіть іншу назву.
- Original:
- Link 2: Original #32876412
- Original:
Please enter a new name for this category.Approved:Будь ласка, введіть нову назву для цієї категорії. - Correction:
Введіть нову назву для цієї категорії.
- Original:
- Issue: In two consecutive strings for the exact same field (
category name),nameis translated as «ім’ям» (personal name, incorrect for categories) in the first string and «назву» (correct term) in the second.
- Link 1: Original #32876413
- Broken verb agreement & colloquial register in session expiration notice
- Link: Original #32876474
- Original:
Your session has expired. You can log in again from this page or go to the login page. - Approved:
Ваша сесія скінчилася. Ви можете повторно увійти в систему з цієї сторінки або перейдіть на сторінку входу. - Issue: Broken grammatical coordination: «Ви можете увійти… або перейдіть» mixes an infinitive with an imperative mood after
or(should be або перейти). Also uses colloquial «скінчилася» instead of standard technical phrasing. - Correction:
Термін дії вашої сесії закінчився. Ви можете увійти знову з цієї сторінки або перейти на сторінку входу.
- Altered punctuation (breaking screen reader pauses), unidiomatic calques & semantic distortion
- Link: Original #32876468
- Original:
Number of media items displayed: %d. Scroll the page for more results. - Approved:
Число відображуваних медіаелементів: %d, прокрутіть сторінку для інших результатів. - Issue: Replaces the period after
%dwith a comma (degrading screen reader 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)), uses the unidiomatic calque «Число відображуваних…» instead of natural Ukrainian «Кількість відображених…», and mistranslatesmore results(додаткових/наступних результатів) as «інших результатів» (different/other results). - Correction:
Кількість відображених медіафайлів: %d. Прокрутіть сторінку, щоб переглянути більше результатів.
Summary & Request
The 20 examples above demonstrate that strings containing broken PHP date specifiers, unedited machine-translation hallucinations, broken Ukrainian grammar, and direct violations of the #uk glossary are regularly passing review into WordPress Core and propagating from version to version (6.8 6.9 7.0.x).
Because these strings were uncovered during a limited spot-check rather than an exhaustive audit, simply fixing these specific entries will not resolve the underlying issue. I ask the Polyglots Mentors and the #uk GTEGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale. team to:
- Review the current QA and approval standards for WordPress Core to prevent unedited machine translations and broken formatting from being approved.
- Enforce adherence to the official
#ukGlossary and standard Ukrainian technical orthography across active and propagated branches. - Initiate a systematic audit and cleanup of the
7.0.xCore branch to identify and correct the remaining unreviewed or broken translations before release.
Thank you for your time and attention to maintaining the quality of WordPress in Ukrainian.
Hi @zhdan
Thank you for this feedback.
All UI translations of WordPress are made by volunteers, with more or less time available.
Our Ukrainian team is very small, and they’re still working on reaching enough strings translated to have the current release of WordPress, 7.1, packaged in a translated version.
In general, we mostly concentrate on getting the current version of WordPress core in order. It’s still possible to fix errors in older versions, but that has much lower priority.
The best way to communicate effectively with the Ukrainian translation team is via chat on the global Slack instance for WordPress contributors.
So I’d suggest that you
1. Join Slack via https://make.wordpress.org/chat/
2. Then come to polyglots-uk where you can cooperate around bringing the Ukrainian translation to a release. And after that improving it further 🙂
FYI #uk
Hi @tobifjellner, thank you for the quick response.
I brought this audit directly to the Polyglots blog because I have already reached out to the local GTE regarding these quality issues, and my feedback was simply ignored without constructive engagement — even though raw, unedited machine translations (like the examples listed above) are routinely being approved in Core.
Because GlotPress propagates identical strings forward across branches, these exact broken translations (including the broken D.m.Y PHP date format and glossary violations) are already present in the current 7.1.x / dev branch that is being prepared for packaging.
I completely understand that the local team is small — that is precisely why I am offering practical help rather than just reporting issues. However, re-typing hundreds of systemic fixes one by one through the web form without clear review timelines is not a viable workflow when strings in #uk already sit unreviewed in the Waiting queue.
I am ready to help both finish the untranslated strings for 7.1 and clean up the broken approved strings. Using standard GlotPress .po batch imports (e.g., 100–200 vetted strings per batch) — or expanding the active #uk review team if current GTEs lack the bandwidth — would let us ensure the 7.1 Ukrainian release meets proper quality standards.
Hello! Thank you for taking the time to provide these specific examples. Some of them (particularly regarding terminology discrepancies, isolated cases of grammatical agreement, or date formatting) are indeed valid. This is natural for a massive body of text that has accumulated over the years in an open-source project and requires periodic review.
However, we emphasize that the solution to this issue does not lie in bulk-overwriting branches with raw machine translations generated via third-party prompts, but rather in targeted, systematic error correction that respects context.
Since you have both the time and the enthusiasm to improve the quality of WordPress in Ukrainian, we invite you to join the official localization team. Volunteers who are ready to dive deep into technical details, catch such bugs, and submit carefully verified fixes via the official `translate.wordpress.org` platform are always needed.
Please choose specific projects, submit your suggestions through the standard review interface, go through the moderation process, and work alongside the editors to bring the translation quality to perfection in practice.
If you have specific fixes to offer, welcome aboard through the official channels.
Hi @kovalets, thank you for acknowledging the validity of the examples in the audit.
First, let’s set the record straight: I never proposed overwriting branches with “raw machine translations.” On the contrary, my audit specifically highlights raw, unedited machine translations that are already approved in Core today (such as translating “lyricist quote” as “цитата лірика пісні” or breaking PHP date formatting with D.m.Y), which automatically propagate into 7.1.x / dev.
Second, importing vetted .po files containing only targeted, manually verified changes (in small batches of 100–200 strings) is a standard, built-in feature of translate.wordpress.org. It does not blindly overwrite an entire branch; it only updates the specific corrected strings, allowing editors to review and approve clean batches efficiently rather than spending months manually re-typing hundreds of fixes one by one in the web form.
I am ready to help both finish the untranslated strings for 7.1 and clean up these systemic errors in Core. Are you open to reviewing vetted .po patches in batches so we can ensure high translation quality for the 7.1 Ukrainian release?
Update for @tobifjellner and the Polyglots mentors:
While reviewing the status of my recent suggestions in GlotPress for 7.0.x, I found a clear pattern of attribution stripping. Instead of simply clicking Approve on valid fixes — which preserves the contributor’s credit in GlotPress — @kovalets is marking character-for-character identical suggestions as Rejected and re-entering the exact same string under his own account (Translated by: KOVALETS):
- Original ID 32876804 — exact same translation rejected and re-submitted by GTE
- Original ID 32876719 — exact same translation rejected and re-submitted by GTE
- Original ID 32876698 — exact same translation rejected and re-submitted by GTE
- Original ID 32876697 — exact same translation rejected and re-submitted by GTE
There is no technical reason in GlotPress to reject a 100% identical string just to re-type it under a GTE’s own name. Doing so strips contributor attribution and actively discourages people from helping improve the #uk locale. This is why #uk needs transparent review practices and additional active GTEs who support collaborative workflows.
@zhdan
Let’s clarify a few things. I can assure you that @sergeykovalets (Note: when you mention someone, you should use their profile slug) isn’t trying to steal any props. He simply doesn’t need that. The same thing would happen to me if I’d extract some good strings from 7.0 and upload them to 7.1. It’s just the quickest way to do it. The GlotPress interface is a bit clunky with regards to translation history (if you know that there was a good translation before, then you need to click through several page-loads to sustain a translation credit – when you’ve got hundreds of strings to fix, this becomes quite annoying).
I’m a bit surprised that you continue involving me and the global mentors’ team, where direct cooperation on Slack (please join if you can) would be more fruitful. And if you would had joined Slack, Sergey would probably have asked you to upload those strings (and get credited).
So: I’m grateful for your contribution, and so is Sergey. But let’s concentrate more on our shared goal of getting a good translation than fighting over a few credits. Soon enough, you’ll find cases where you’ll want to slightly improve on his translations, and you’ll get credited for the whole string, even if you just changed one word.
Thank you for the clarification, @tobifjellner, and for noting the correct profile slug for @sergeykovalets.
Fair point — my goal is indeed a clean, consistent Ukrainian translation rather than counting credits, and I appreciate the context on how bulk updates between branches work in GlotPress.
I’ll join the Ukrainian Slack channel to coordinate directly with Sergey on the remaining fixes and workflow. Thanks again for your time and guidance.
Request sponsor vetting right from your event dashboard
After some great work by @obenland, @clk87, @coreyhall93, and @velda, organizers can now request sponsor vetting from inside the sponsor record, without leaving the dashboard.
This is useful whether there’s a need to request sponsor vetting before creating invoices (most flagships), or if an event will be handling funds locally and not creating invoices in the event dashboard. Organizers should no longer send emails or spreadsheets to WordPress Community SupportWordPress Community Support WordPress Community Support PBC is a Public Benefit Corporation, created specifically to be the financial and legal support for WordCamps, WordPress Meetup groups, and any additional “official” events organized within the WordPress Community Events program. for sponsor vetting.
How it works (Here’s a short demo video, so you can see it in action)
- In your event dashboard, go to Sponsors and create a new sponsor (or open an existing one).
- Fill in the sponsor’s contact information: company name, website (this one is especially important), first and last name, email address, phone number, and address. A title also needs to be added in order to save a sponsor record. If
Save Draftis greyed out, that means you’ve missed a required input. - Click Save draft.
- In the right-hand 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., scroll down past Sponsor Agreement. You’ll find a new Sponsor Vetting panel.
- Once all the required fields are filled in and the record is saved, the Request vetting button appears. Click it, and the sponsor’s details go straight to the team that will be completing the vetting.
Tracking the status
Come back to the main sponsor dashboard (there’s now a new column with vetting statuses), or the individual sponsor record any time to check progress. The Sponsor Vetting panel shows where things stand, from Not Requested, to Waiting on Sponsor (indicating compliance has been requested), and finally Approved.
Once the panel says Approved, you can create the invoice and send it for approval or send it directly to the sponsor if running funds locally.
Approved Status Note: If a sponsor has been recently vetted, and the sponsor is compliant, Approved will appear in the Sponsor Vetting panel. This means, there’s no need to wait to create an invoice!
Questions? Drop them in the comments below!

Yani
Thanks for pushing this forward, Jonathan. As I maintain and develop All-in-One WP Migration, I am writing as someone whose plugin would be subject to these rules.
The proposal asks plugins to declare why they notify. I think it should also ask where, and treat that as the primary rule, the way Chromium extensions do.
In Chromium, an extension gets its own pages for free. Access to anything else must be declared as a host permission in the manifest, and broad access requires a written justification that reviewers read. The equivalent here would be:
a) Own screens are free. A plugin, theme, must use plugin or dropin may show inline admin notices on the screens it registers itself, with no approval needed.
b) The hub is open to everyone. It is the surface users control with mute and snooze, so cases like “backup failed” never need special access.
c) Everything else is declared and justified. Inline notices on the Dashboard or any other screen the plugin does not own require a declared `screens` list plus a short explanation, reviewed by the Plugins or Themes team. Adding a screen in an update triggers a new review.
d) One automatic grant. A dismissible `setup` notice on the Plugins screen right after activation is common enough to allow without review.
I think this is stronger than intent alone. Location is a fact, intent is a claim. “Your license expires in 7 days” can be argued as `operational`, `setup` or `promotional`. Whether a screen belongs to the plugin can be checked by Plugin Check against its `add_menu_page()` calls. The post already lists `screens` as an open question; I am suggesting it becomes the deny by default rule, with intent deciding what is acceptable once access is granted.
It reduces reviewer load. With the hub open, only plugins asking for inline space on screens they do not own enter the justification queue.
It can be shown to users. The directory listing could state “shows notices on: own screens, Dashboard (reason given)”, similar to permission warnings when installing an extension.
Two related suggestions:
1. Make the declaration static data. A `register_channel()` call can take computed arguments, which weakens the goal of reading intent without running the plugin. A JSON file or plugin header, in the manner of `block.json`, would be reliably machine readable.
2. Give site admins a grant screen. Must use plugins, dropins and anything distributed outside the directory have no reviewer. A settings screen listing each channel’s requested screens, with a revoke toggle, makes the site owner the approver in those cases.
One open question: how should addons be treated? An extension to WooCommerce showing notices on WooCommerce screens is on neither its own screen nor a core screen. Should the parent plugin be able to grant that access?
Happy to help test this in the feature plugin.
Reply
Joe Fusco
Thanks for writing this up, Jonathan. I maintain the Presence API feature plugin, and one rule here would block a notice it relies on.
When someone else changes the screen you have open, Presence shows a dismissible warning: “Alex updated this screen 2 minutes ago.” with a Reload button. Your edge-case table puts “The page has been updated (by another person)” under activity, and activity can’t be an admin notice. Moving it to the hub wouldn’t work, because the message only matters on that screen while you still have it open. By the time you read it in a notification centre, it’s out of date.
Could activity be allowed as an admin notice when it’s about what’s on the current screen, as long as it’s dismissible?
Also, that banner is drawn in JavaScript after a Heartbeat tick, so
wp_admin_notice_argsandwp_admin_notice_markupnever see it. The same goes for anything a plugin sends through the block editor’s core/notices store. Are client-side notices in scope for v1, or left to Plugin Check and directory review?Reply
David Perez
Thanks @psykro, great to see this moving forward!
Fewer intents. Five is too many. If developers have to think hard about which one fits, they’ll just pick one at random, and reviewers won’t be able to tell what’s right. I’d keep three:
operational,setupandpromotional.activityandfeedbackcould go intooperational. What makes them different today (only in the hub, never stored,successallowed) could come from the surface and the severity instead of a separate intent.Undeclared notices. If notices without a channel are left alone at runtime, the plugins that abuse the dashboard today can just skip declaring. All the enforcement then falls on Plugin Check and manual review. A few things would help:
operationalcan’t be caught with static checks, so we need a simple way to report misuse that ties into Guideline 11.Happy to help define the Plugin Check rules from the Plugins Team side.
Reply