{ "feeds": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Sat, 15 Aug 2026 10:15:08 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69785", "title": "Hi Polyglots! 👋", "link": "https://make.wordpress.org/polyglots/2026/08/15/hi-polyglots-%f0%9f%91%8b-3/", "description": "

I’m the author of the Captain Social Review plugin.

\n

Plugin: https://wordpress.org/plugins/captain-social-review

\n

I’d like to request Project Translation Editor (PTE) rights for the following locales:

\n\n #en_AU \n\n #en_CA \n\n #en_NZ \n\n #en_ZA \n\n #en_GB \n\n #art_xpirate \n\n #hi_IN \n\n #gu \n\n #mr \n\n #art_xemoji\n\n\n

I’d like to help maintain and improve the translations of this plugin across these locales.

\n

If a GTE or Locale Manager for any of these locales could grant me PTE access, I’d really appreciate it.

\n

Thank you for your time and support!

\n

#editor-requests

", "id": 17296572, "pubDate": "Sat, 15 Aug 2026 09:06:13 GMT", "whenReceived": "Sat, 15 Aug 2026 10:15:08 GMT", "whenUpdated": "Sat, 15 Aug 2026 10:15:08 GMT", "likes": [], "metadata": { "wpPostId": 69785, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69783", "title": "PTE Request for AIEL Smart Assistant", "link": "https://make.wordpress.org/polyglots/2026/08/15/pte-request-for-aiel-smart-assistant/", "description": "

I am the plugin author of AIEL Smart Assistant (智能秘書).

\n

AIEL Smart Assistant (智能秘書)

\n

\n

I have a complete zh_TW translation ready and I am a native Traditional
\nChinese speaker based in Taiwan. Please add me as translation editor for
\nthe locale below so I can import and maintain it:

\n\n #zh_tw – @aielapp\n\n\n

Thanks!

\n

#editor-requests

", "id": 17294811, "pubDate": "Sat, 15 Aug 2026 06:39:28 GMT", "whenReceived": "Sat, 15 Aug 2026 06:47:16 GMT", "whenUpdated": "Sat, 15 Aug 2026 06:47:16 GMT", "likes": [], "metadata": { "wpPostId": 69783, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69758", "title": "Hi,", "link": "https://make.wordpress.org/polyglots/2026/08/14/hi-134/", "description": "

We submitted translations for the FoodOrd plugin approximately two weeks ago. The Spanish translations have been reviewed, but the following translations are still waiting for approval:

\n

Turkish
\nFrench
\nHindi

\n

Could you please check whether these translation projects are awaiting an editor or require any additional action from us?

\n

Plugin: https://translate.wordpress.org/projects/wp-plugins/foodord/

\n

Tobi: We’ll handle this as a PTE request for Turkish:

\n\n #tr_TR \n\n\n

Thank you for your help.

\n

Best regards,
\nEyĂźp
\nFoodOrd Developer

\n

#editor-requests

", "id": 17291167, "pubDate": "Fri, 14 Aug 2026 22:16:51 GMT", "whenReceived": "Fri, 14 Aug 2026 23:40:18 GMT", "whenUpdated": "Fri, 14 Aug 2026 23:40:18 GMT", "likes": [], "metadata": { "wpPostId": 69758, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69755", "title": "Hello Polyglots team,", "link": "https://make.wordpress.org/polyglots/2026/08/14/hello-polyglots-team-99/", "description": "

I am the plugin author and Arabic translator for Aetos SEO. I have submitted the complete Arabic translations for both the Stable and Stable Readme projects.

\n

Current Arabic translation status:

\n\nStable: 1,068 strings waiting for review, 0 untranslated, 0 warnings.\n\nStable Readme: 112 strings waiting for review, 0 untranslated, 0 warnings.\n\n\n

Please review the Arabic translations and, if appropriate, assign the following WordPress.org user as a Project Translation Editor for this project so future Arabic updates can be maintained promptly.

\n\nhttps://wordpress.org/plugins/aetos-seo/\n\n\n\n #ar – @aetosseo\n\n\n

Translation projects:

\n\nhttps://translate.wordpress.org/projects/wp-plugins/aetos-seo/stable/ar/default/\n\nhttps://translate.wordpress.org/projects/wp-plugins/aetos-seo/stable-readme/ar/default/\n\n\n

If you have any questions or would like any translation adjusted, please comment here. Thank you.

\n

#editor-requests

", "id": 17291168, "pubDate": "Fri, 14 Aug 2026 22:16:23 GMT", "whenReceived": "Fri, 14 Aug 2026 23:40:18 GMT", "whenUpdated": "Fri, 14 Aug 2026 23:40:18 GMT", "likes": [], "metadata": { "wpPostId": 69755, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69763", "title": "I am the plugin author…", "link": "https://make.wordpress.org/polyglots/2026/08/14/i-am-the-plugin-author-126/", "description": "

I am the plugin author of **SEV Instructor Cockpit for LearnDash**.

\n\nhttps://wordpress.org/plugins/sev-instructor-cockpit-for-learndash/\n\n\n\n #de_DE – @hfranz (@tobifjellner)\n\n #de_AT – @hfranz\n\n #de_CH – @hfranz\n\n\n

Thank you!

\n

#editor-requests

", "id": 17289701, "pubDate": "Fri, 14 Aug 2026 21:55:07 GMT", "whenReceived": "Fri, 14 Aug 2026 21:56:07 GMT", "whenUpdated": "Sat, 15 Aug 2026 10:15:08 GMT", "likes": [], "metadata": { "wpPostId": 69763, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Fri, 14 Aug 2026 20:46:07 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=90194", "title": "WordCamp US opens, students ship 108 sites in Bangladesh, and a lesson in the dark", "link": "https://make.wordpress.org/community/2026/08/14/wordcamp-us-opens-students-ship-108-sites-in-bangladesh-and-a-lesson-in-the-dark/", "description": "

Meetup Organizer Newsletter | August 2026

\n\n\n\n

Oli otya, and hello. Here’s what organizers have been running around the world, plus what’s worth trying next.

\n\n\n\n\n\n\n\n\n\nWordCamp US opens Sunday\n\n\n\n

WordCamp US 2026 runs August 16 through 19 in Phoenix, opening with Contributor Day on Sunday. Tell your group about it even if nobody can travel, because Contributor Day is where a lot of people make their first contribution to WordPress and no experience is required. There is a Connector Table for anyone who arrives not knowing where to start.

\n\n\n\n\n\n\n\n\n\nThree events you could run, from easiest up\n\n\n\n

A WordCamp is not the only kind of WordPress event, and it is not the one most groups should start with.

\n\n\n\n\nCoffee and Code: The handbook’s description is hard to argue with: it “can be done in a coffee shop or any space where you can get coffee and they will let you use their wifi.” No speaker, no budget, no projector to fail on you. If your group has gone quiet, this is the one that restarts it. Eight more like it are in the event formats handbook.\n\n\n\nA translation session: The Chiba group in Japan translates English documentation into Japanese together. They have done it about once a year for four years. The next is August 23, and it needs no speaker either. An evening turns into a contribution that stays on the site.\n\n\n\nWalk into the college near you: Universidad del Valle de Guatemala hosted the country’s first Campus Connect on August 1. Nine teams spent half a day building sites for their own student associations, 44 students and 10 mentors in one room. It takes real planning, but the Community Team walks you through it.\n\n\n\n\n\n\n\n\n\n\nGroup of the Month: Bulamogi College Gadumire, Uganda\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tBulamogi College Gadumire (Uganda)\n\n\n\n

Their Campus Connect lost electricity partway through. No laptops, no slides, nothing to project. The team taught WordPress out loud to about a hundred students instead, finished the session, and everyone walked out with certificates. The room was the point.

\n\n\n\n\n\n\n\n\n\nAlso worth knowing\n\n\n\n\nYour meetup group can have its own channel in Make WordPress Slack:\n\n\n\n

The Community Team is creating channels for local meetup groups, locale communities and flagship events. To get one, join #community-slack-migration and post your group name, your Meetup.com URL, and the channels you want. Your existing message history can come with you, and Karen Arnold’s post covers the rest.

\n\n\n\n\n\nEleven ready-made sessions you can run without building one\n\n\n\n

Learn WordPress just published hands-on activity kits, built for exactly the meeting you do not have time to prepare. Eleven are live, each running 60 to 90 minutes, and each is a single download holding a facilitator guide and a slide deck. The guide already has the learning objectives, the setup notes, the step-by-step activities and the debrief questions in it. Pick one and run it. The announcement has the full list.

\n\n\n\n\n\nTip of the month for sustainable events:\n\n\n\n

Check whether your venue has somewhere people can refill a water bottle. The Sustainable Events Handbook asks for “a system for refilling water bottles that doesn’t rely on drums,” one of the few venue questions that costs nothing and cuts real waste.

\n\n\n\n\n\nWorth watching\n\n\n\n

Why the path from a classroom to a contributor matters.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nBy the numbers\n\n\n\n\n\n

108

\n\n\n\n

Websites built by students at two colleges in Kishoreganj, Bangladesh.

\n\n\n\n\n\n

9

\n\n\n\n

Event formats in the handbook, and most need no speaker at all.

\n\n\n\n\n\n

100

\n\n\n\n

Countries with a WordPress meetup group, across 707 groups.

\n\n\n\n\n\n

0

\n\n\n\n

Laptops at Bulamogi’s Campus Connect after the power cut. They ran it anyway.

\n\n\n\n\n\n\n\n\n\n\n\nMeetups of the Month\n\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tCampus Connect Tegal (Tegal, Indonesia)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tUniversidad del Valle de Guatemala (Guatemala)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tChiba WordPress Meetup (Chiba, Japan)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tCampus Connect Kyoto University of Advanced Science (Japan)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tCampus Connect Kolhapur (Kolhapur, India)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tWordPress Meetup Shanghai (Shanghai, China)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tCampus Connect Kishoreganj (Bangladesh)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tWordPress Nairobi Meetup (Nairobi, Kenya)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tWordPress Kolhapur Meetup (Kolhapur, India)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tWordPress Brisbane Meetup (Brisbane, Australia)\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\tWordPress Vadodara Meetup (Vadodara, India)\n\n\n\n\n\n\n\n\n\n\nComing up\n\n\n\nDateEventWhereAugust 15WordCamp EketEket, NigeriaAugust 16Campus ConnectDinajpur, BangladeshAugust 16 to 19WordCamp USPhoenix, United StatesAugust 16 to September 6Campus ConnectKathmandu, NepalAugust 23Contribute Through TranslationChiba, JapanAugust 28 to 29WordCamp PhilippinesIloilo City, PhilippinesAugust 29Campus ConnectEsparza, Costa RicaAugust 29WordPress Day CDMXMexico City, MexicoAugust 29Galicia WordPress DayOuteiro de Rei, SpainAugust 29 to 30WordCamp LiraLira, UgandaSeptember 1 to 15Campus ConnectBanyumas, IndonesiaSeptember 5WP Future ConclaveKozhikode, India\n\n\n\n

Local meetups run in far more places than this. Everything, everywhere, is on events.wordpress.org.

\n\n\n\n\nOpen calls for speakers:\n\n\n\n

Worth passing to your group. Someone who has never spoken before is usually one nudge away from it, and a first talk at a nearby WordCamp is how a lot of organizers started.

\n\n\n\n\n\nWordCamp Pisa and WordCamp Jinja both close August 15.\n\n\n\nWordCamp Sofia and WordCamp Wrocław both close August 31.\n\n\n\n\n

Not a talk, but the same shape: the WP Credits developer track wants input from developers and teachers by the end of August.

\n\n\n\n\n\n\n\n\n\nOver to you\n\n\n\n

What is the smallest event you have run that still felt worth doing? Tell us what it was and who showed up, and we will run the answers next month. Reply in the comments below, in #community-events, or by email to support@wordcamp.org, whichever you already use.

\n\n\n\n\n\n\n

This newsletter is built from what you share!

\n\n

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.

\n\n

Did we miss your event? Possibly, and we would rather know. Each issue is built from what gets posted in #community-events and #campusconnect, so anything that did not land there is invisible to us. Send it over and it goes in the next issue.

\n\n

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.

\n\n\n\n\n\n\n\n\n\n\nNeed support or guidance?\n\n\n\n

The Community Team is here to help. Email support@wordcamp.org or join us in #community-events on the Making WordPress Slack.

\n\n\n\n\n\n\n

Each issue opens with a greeting from a language spoken where one of the featured groups is based. This month it is Luganda, from Uganda. If you would like your language to open an issue, tell us.

\n\n\n\n\n

Thanks for everything you do to grow and support the WordPress community.

\n\n\n\n\n\n

#community-event, #community-team, #meetup-organizer-newsletter, #newsletter

", "id": 17288388, "pubDate": "Fri, 14 Aug 2026 19:55:04 GMT", "whenReceived": "Fri, 14 Aug 2026 20:46:07 GMT", "whenUpdated": "Sat, 15 Aug 2026 09:22:51 GMT", "likes": [], "metadata": { "wpPostId": 90194, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Fri, 14 Aug 2026 15:18:58 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125508", "title": "WordPress Contributor Toolkit 1.0: A smoother workflow for your first Core contribution", "link": "https://make.wordpress.org/core/2026/08/14/wordpress-contributor-toolkit-1-0-a-smoother-workflow-for-your-first-core-contribution/", "description": "

First introduced in April as the WordPress Core Dev Environment Toolkit, the WordPress Contributor Toolkit is an experimental desktop app that guides first-time contributors through setting up a full wordpress-develop environment. Git, Node.js, and npm are still involved under the hood, but the app provides and runs them for you. You do not have to install Git, Node.js, npm, or Docker on your machine.

\n\n\n\n

WordPress Contributor Toolkit 1.0 is now available for Windows, macOS (Apple Silicon) and Linux.

\n\n\n\n

The first releases concentrated on getting a newcomer from a fresh computer to a running WordPress development site. Version 1.0 carries that work through the contribution itself: link a TRAC ticket and see its details, pull requests, and patches; apply existing work and test it on the running site; create a diff or open a pull request directly from the app; and keep that first site current with the latest trunk, fetching only what changed instead of repeating a full clone and install.

\n\n\n\nA first Core contribution, from start to finish\n\n\n\n

Here is what the workflow looks like now.

\n\n\n\n1. Create the development environment\n\n\n\n

Click Create WordPress Core site and choose a folder. The app clones wordpress-develop, installs the dependencies, and runs the first build as one continuous setup. When setup finishes, click Start dev server and finish the wizard to complete the WordPress installation wizard that opens in your browser, and you are ready to start contributing.

\n\n\n\n

The interface draws attention to the next action with a yellow outline, and completed actions produce an accessible confirmation.

\n\n\n\n\n\n\n\n2. Link the site to a Trac ticket\n\n\n\n

You can link a Trac ticket when creating the site or at any time afterwards. Enter its ticket number or paste its Core Trac URL to bring its details, related pull requests, and attached patches into the Toolkit.

\n\n\n\n

The app reads the ticket’s details: summary, status and resolution, type, milestone, component, keywords, and age. These details help you understand the ticket before you start working: how long ago it was opened, whether it is still open or has already been resolved, and which part of WordPress Core it belongs to.

\n\n\n\n

If you do not have a ticket yet, the app links to the good first bugs report on Trac.

\n\n\n\n3. Check the work that already exists\n\n\n\n

A linked ticket shows the work that already exists:

\n\n\n\n\nPull requests on WordPress/wordpress-develop that reference the ticket, including their open, closed, or merged state.\n\n\n\nPatch files attached directly to Trac.\n\n\n\n\n

The newest work is marked Latest, based on the date of the newest commit. You can preview and apply a pull request or Trac patch from the same screen.

\n\n\n\n\n\n\n\n4. Apply and test an existing patch\n\n\n\n

Before applying a patch or a PR, the Toolkit previews the files a patch will touch, warns about collisions with your edits, identifies binary files it cannot apply, and checks whether a dependency install will be needed. “Apply and rebuild” then adds the changes and runs any required install or rebuild steps.

\n\n\n\n

If a patch cannot be applied, the app leaves the checkout unchanged and explains what failed so you can decide what to do next.

\n\n\n\n

Applied work keeps the patch or pull request’s identity attached to it. You can make your own changes on top and later remove that layer, but the app will not let you submit somebody else’s patch as if you wrote it.

\n\n\n\n\n\n\n\n5. Edit and debug the change\n\n\n\n

The site can be opened in a detected editor, another application of your choice, or the system file manager. The build watcher now has its own control, status, and log. Starting the development server starts the watcher too, but stopping the server leaves compile-on-save running if you still need it.

\n\n\n\n

The Toolkit also exposes the parts of a development environment that are useful in Core testing and development:

\n\n\n\n\nA direct link to wp-admin beside the site URL.\n\n\n\nA live debug.log tab with PHP notices, warnings, deprecations, stack traces, and fatal errors.\n\n\n\nAn embedded terminal for the supported install, build, test, watch, and Grunt commands, using the Node.js runtime bundled with the app.\n\n\n\nAdminer for inspecting the site’s SQLite database while the development server is running.\n\n\n\n\n

The development server can remain up while a patch is applied or trunk is updated. The app pauses and resumes the build watcher only when an operation needs exclusive access to the build or dependencies.

\n\n\n\n6. Review and send the contribution\n\n\n\n

Click Review & submit changes to inspect the complete diff, then choose who will send it:

\n\n\n\n\nOpen a GitHub pull request. The app uses GitHub’s device sign-in, creates the fork, commit, and pull request through the API, and forgets the token when the app quits. No push credential is written to disk. The pull request form asks for a title and optional notes for reviewers: what the change does and why, how to see it working, and anything you are unsure about. The app adds the Trac ticket and your WordPress.org username to the description, then points you back to Trac because Core pull requests are not monitored on GitHub alone.\n\n\n\nAttach a patch to Trac. The app saves the patch locally and opens the attachment page for the site’s linked ticket. From there, you’ll need to sign in and upload the saved file to the TRAC ticket yourself.\n\n\n\nHand the patch to a mentor. This path needs no GitHub or Trac account. The saved patch carries the contributor’s WordPress.org handle, event, ticket, base revision, and date so the authorship can follow the work when a mentor submits it.\n\n\n\n\n

The diff comes first on this screen. The destinations sit beside it, grouped by whether you or a mentor will do the sending.

\n\n\n\n\n\n\n\nOne site can hold work for many tickets\n\n\n\n

Creating a site is the expensive part: cloning wordpress-develop, installing its dependencies, and running the first build. Starting another ticket should not repeat all of that.

\n\n\n\n

In 1.0, every linked ticket gets its own branch inside the site. Unlinking a ticket parks its changes, and linking another swaps the files in seconds. The site shows the tickets that have work stored in it, so returning to one does not depend on remembering its number. Each ticket contains only that ticket’s changes.

\n\n\n\n\n\n\n\nKeep the environment without keeping an old copy of trunk\n\n\n\n

A site no longer has to stay on the snapshot of trunk it cloned. Update to latest trunk fetches current Core code, installs dependencies only if they changed, and rebuilds the site. Sites more than 14 days old show a warning that patches created from them may no longer apply cleanly.

\n\n\n\n

The Toolkit uses its own built-in Git implementation, so Git does not need to be installed on your computer. To keep the initial download small, it creates a depth-one shallow clone. If you do have Git installed and run it inside the site folder, history-based commands will be limited: git log sees only the current snapshot, while git blame and git bisect cannot work normally.

\n\n\n\n

Updating trunk does not silently rebase ticket work. The app parks the active ticket, updates the site, and returns to it on its original base. If trunk has moved since that ticket started, the Toolkit says so and explains the safe path to recreate the ticket on a fresh base.

\n\n\n\n\n\n\n\nMade for Contributor Days\n\n\n\n

Version 1.0 is available just in time for WordCamp US Contributor Day on August 16. If you are a first-time contributor planning to work with the Core team, the Test team, or another Contributor Day team working in wordpress-develop, download the app and create your first site before Sunday if you can. The Toolkit can help you find the pull requests and patches linked to a ticket, apply them, and test the result on a running site, even if you are not writing the fix yourself. The installer is self-contained, but the initial clone and dependency installation still need an internet connection and some time.

\n\n\n\n

For Contributor Day facilitators, the Toolkit is a simpler way to introduce people to Core contributions without spending the session on environment setup. Newcomers and testers can get straight to a ticket, try existing work, and contribute feedback with experienced contributors nearby.

\n\n\n\n

Downloads are available for:

\n\n\n\n\nmacOS on Apple Silicon\n\n\n\nWindows x64\n\n\n\nLinux x64 as an AppImage\n\n\n\n\n

Download WordPress Contributor Toolkit 1.0, then follow the getting started guide for installation and a first contribution walkthrough.

\n\n\n\nYour feedback shapes the next update\n\n\n\n

The app has no telemetry. Bug reports, release downloads, and direct feedback are the only signals about where it helps and where contributors still get stuck.

\n\n\n\n

You can share feedback through this form, open an issue in the repository, use the feedback button in the app, comment on this post, or ping @JuanMa in the #core channel on WordPress Slack.

\n\n\n\n

Feedback from WordCamp Contributor Days is particularly helpful, especially on whether the Toolkit enabled you to complete a contribution independently, where you still needed a facilitator, and what could have made the process easier.

\n\n\n\nResources\n\n\n\n\nDownload WordPress Contributor Toolkit v1.0\n\n\n\nFollow the Toolkit getting started guide (Docs)\n\n\n\nWordPress Contributor Toolkit GitHub Repo\n\n\n\nRead the v1.0 release notes\n\n\n\nLearn how to contribute code to WordPress Core\n\n\n\nBrowse good first bugs on Core Trac\n\n\n\nRead the FAQ for new Core contributors\n\n\n\n\n

Props to @greenshady,@bph and @softglaze for review and feedback

", "id": 17280808, "pubDate": "Fri, 14 Aug 2026 14:34:18 GMT", "whenReceived": "Fri, 14 Aug 2026 15:18:58 GMT", "whenUpdated": "Fri, 14 Aug 2026 17:03:42 GMT", "likes": [], "metadata": { "wpPostId": 125508, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Fri, 14 Aug 2026 15:00:40 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69753", "title": "Hello Polyglots,", "link": "https://make.wordpress.org/polyglots/2026/08/14/hello-polyglots-341/", "description": "

Please review and approve my translation of the theme CreceWeb Lumen https://translate.wordpress.org/locale/es/default/wp-themes/creceweb-lumen/
\nes_ES – @irinashl
\nThank you.

\n

#editor-requests

", "id": 17280552, "pubDate": "Fri, 14 Aug 2026 14:30:46 GMT", "whenReceived": "Fri, 14 Aug 2026 15:00:40 GMT", "whenUpdated": "Fri, 14 Aug 2026 15:00:40 GMT", "likes": [], "metadata": { "wpPostId": 69753, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69740", "title": "PTE Request for Cross-Sell with Discounts for WooCommerce", "link": "https://make.wordpress.org/polyglots/2026/08/14/pte-request-for-cross-sell-with-discounts-for-woocommerce/", "description": "

Hello Polyglots,
\nI’m the author of the plugin “Cross-Sell with Discounts for WooCommerce”. The plugin was originally written in German; I translated the source strings to English for the wp.org release and did the German translation myself as a German speaker. It’s already imported into GlotPress (currently pending) and I’ll keep it up to date.
\nI’d like to request PTE for German so I can review/approve and maintain the translation:

\n\n #de_DE – @sergej7 (@tobifjellner)\n\n\n

Plugin: ` https://wordpress.org/plugins/cross-sell-with-discounts-for-woocommerce/ `
\nTranslations: ` https://translate.wordpress.org/projects/wp-plugins/cross-sell-with-discounts-for-woocommerce/ `

\n

Thank you!

\n

#editor-requests

", "id": 17280553, "pubDate": "Fri, 14 Aug 2026 14:03:06 GMT", "whenReceived": "Fri, 14 Aug 2026 15:00:40 GMT", "whenUpdated": "Fri, 14 Aug 2026 23:40:18 GMT", "likes": [], "metadata": { "wpPostId": 69740, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69733", "title": "Microtango", "link": "https://make.wordpress.org/polyglots/2026/08/14/microtango/", "description": "

I am the author of the plugin Microtango and would like to request Project Translation Editor (PTE) rights.

\n\nhttps://wordpress.org/plugins/microtango/\n\n\n

Please add the following WordPress.org user as PTE for the listed locale:

\n\n #de_DE – @microtango (@tobifjellner)\n\n\n

If you have any questions, please comment here. Thank you!

\n

#editor-requests

", "id": 17280554, "pubDate": "Fri, 14 Aug 2026 14:01:44 GMT", "whenReceived": "Fri, 14 Aug 2026 15:00:40 GMT", "whenUpdated": "Fri, 14 Aug 2026 23:40:18 GMT", "likes": [], "metadata": { "wpPostId": 69733, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69736", "title": "PTE Request for Stobio", "link": "https://make.wordpress.org/polyglots/2026/08/14/pte-request-for-stobio/", "description": "

Hello Polyglots! I am the plugin author of Stobio. Please add my WordPress.org user stobio as translation editor (PTE) for the locale listed below. I have already imported the full set of translations (Stable + Readme, currently in “waiting” status) and will maintain them for future releases.

\n\n #tr_TR — @stobio\n\n\n

The plugin and its translations were prepared by a native Turkish speaker. Thank you!

\n

#editor-requests

", "id": 17280555, "pubDate": "Fri, 14 Aug 2026 14:01:01 GMT", "whenReceived": "Fri, 14 Aug 2026 15:00:40 GMT", "whenUpdated": "Fri, 14 Aug 2026 15:00:40 GMT", "likes": [], "metadata": { "wpPostId": 69736, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69745", "title": "Hi, I maintain Segurium (https://wordpress.org/plugins/segurium/)….", "link": "https://make.wordpress.org/polyglots/2026/08/14/hi-i-maintain-segurium-https-wordpress-org-plugins-segurium-2/", "description": "

Hi, I maintain Segurium (https://wordpress.org/plugins/segurium/).

\n\n #de_DE @rosenheinrich\n\n\n

Requesting PTE for de_DE native speaker @rosenheinrich. He will take care about correct translation of Segurium plugin.

\n

#editor-requests

", "id": 17280556, "pubDate": "Fri, 14 Aug 2026 13:32:24 GMT", "whenReceived": "Fri, 14 Aug 2026 15:00:40 GMT", "whenUpdated": "Fri, 14 Aug 2026 15:00:40 GMT", "likes": [], "metadata": { "wpPostId": 69745, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Fri, 14 Aug 2026 08:10:50 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=90294", "title": "What Comes After WordPress Credits", "link": "https://make.wordpress.org/community/2026/08/14/what-comes-after-wordpress-credits/", "description": "

WordPress Credits is working. Students around the world are contributing to real projects, earning academic recognition, and graduating with a WordPress.org profile they can point to. What we have not built yet is what happens after that.

\n\n\n\n

Right now, graduates leave the program with no defined next step. That means a lot of the momentum we built together such as the onboarding, the mentorship, the contribution work, stops at the exact moment a graduate is most capable of giving something back.

\n\n\n\n

This proposal is our attempt to change that: Proposal: WordPress Credits Graduate Retention Program

\n\n\n\n

The tracking issue for this work is on GitHub: https://github.com/WordPress/Community-Team/issues/1083

\n\n\n\nWhat We Are Proposing\n\n\n\n

We want to move WordPress Credits from a one-time experience to the first step in a longer contribution and career pathway. The proposal has three phases, starting with lightweight infrastructure changes and building toward a self-sustaining pipeline.

\n\n\n\n

Main takeaways:

\n\n\n\n

Give every graduate a clear next step. Right now the wrap-up flow ends without directing graduates anywhere specific. We want to change that with discipline-specific routing: dev-track graduates get pointed toward a WordPress Developer Certification and jobs.wordpress.net. Other tracks get equivalent routing based on what they contributed during the program.

\n\n\n\n

Build a credential pathway graduates can see. The arc we are working toward: WordPress Credits (contribution program) → continued contribution → Developer credential received → ecosystem opportunity. We want graduates to be able to see the full path at the moment they finish the program, not discover it piece by piece after the fact.

\n\n\n\n

Ensure students see their place in our contributing community. The arc we are working toward: WordPress Credits (contribution program) → continued contribution → peer mentoring → community leadership

\n\n\n\n

Create scoped graduate contribution projects with Make teams. One of the most consistent barriers to returning is not knowing where to start. We want to work with Make WordPress teams to identify and tag real, appropriately scoped tasks that graduates can pick up. These are not new contribution areas — they are existing work made more accessible as a defined entry point.

\n\n\n\n

Connect graduates to ecosystem opportunities. We are in conversations with ecosystem companies who have expressed interest in the WP Credits talent pipeline. The model we are exploring: companies fund certification exam seats for graduates, with one verifiable post-graduation contribution unlocking the seat. In return, companies get first access to graduates who pass and warm introductions to strong candidates. We are also pointing graduates to jobs.wordpress.net, where their WordPress.org contribution profile functions as a verified, public portfolio.

\n\n\n\nWhat We Are Looking For from the Community\n\n\n\n

This proposal touches several parts of the WordPress community, and we would love input before we move into execution:

\n\n\n\n

Make team members: We want to collaborate on scoped graduate contribution projects: real tasks your team needs done, tagged as appropriate entry points for graduates returning to contribution. If you are on a Make team and interested in being part of this, please comment below or reach out in #wpcredits.

\n\n\n\n

Ecosystem companies: If your company hires WordPress talent and is interested in exploring the exam seat model, we would love to talk. You can comment here or reach out directly.

\n\n\n\n

Experienced contributors: If you have been through a structured contribution program yourself, whether WordPress Credits or something similar, we would love to hear what would have brought you back after graduation, and what would not have.

\n\n\n\n

The full proposal includes a phased timeline, a tiered definition of what “returning to contribution” means, a 25% Tier 2 retention target for the dev-track pilot (benchmarked against comparable open source programs), and a research foundation grounded in what has worked at LFX Mentorship, Outreachy, and GitHub Campus Experts.

\n\n\n\n

We are not building everything at once. Phase 1 is infrastructure and one re-engagement message. Phase 2 is the dev-track pilot. Phase 3 is expansion to other tracks.

\n\n\n\n

Feedback at any of these stages is welcome.

\n\n\n\n\n\n\n\n

Questions or thoughts? Comment below or join the conversation in #wpcredits on the Making WordPress Slack.

\n\n\n\n

Props to @peiraisotta for reviewing this post and proposal, and @celigaroe @francescodicandia @roblesloaiza @alanabwarner for reviewing the proposal.

\n\n\n\n

Tags: #wpcredits, #proposal

", "id": 17272639, "pubDate": "Fri, 14 Aug 2026 08:04:01 GMT", "whenReceived": "Fri, 14 Aug 2026 08:10:50 GMT", "whenUpdated": "Fri, 14 Aug 2026 08:10:50 GMT", "likes": [], "metadata": { "wpPostId": 90294, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Fri, 14 Aug 2026 08:05:54 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69731", "title": "Hi, it’s me again, the…", "link": "https://make.wordpress.org/polyglots/2026/08/14/hi-its-me-again-the/", "description": "

Hi, it’s me again, the plugin author of sinnvoll Booking Flow. Please add my WordPress.org user also as translation editor for the following locale:

\n\nhttps://wordpress.org/plugins/sinnvoll-booking-flow/\n\n\n\n #de_AT – @rmiarka\n\n\n

The complete de_AT translation (704 strings, 100%) has already been uploaded
\nand is currently waiting for approval. It uses the informal address (du) in
\nline with the German style guide. German (de_DE) was approved earlier and is
\nalready imported.

\n

The de_AT strings are currently identical to de_DE, which is deliberate: the
\nplugin’s vocabulary (event registration, attendees, invoicing) contains no
\nterms that differ between the two variants, and month names come from
\nWordPress core, which already provides “Jänner” for de_AT. The one domain term
\nthat does differ – the VAT number – is written as “UID” (the Austrian form)
\nthroughout. I am based in Austria and will keep the de_AT catalog maintained
\nas the plugin grows.

\n

Thank you!

\n

#editor-requests

", "id": 17272615, "pubDate": "Fri, 14 Aug 2026 08:00:50 GMT", "whenReceived": "Fri, 14 Aug 2026 08:05:54 GMT", "whenUpdated": "Fri, 14 Aug 2026 08:05:54 GMT", "likes": [], "metadata": { "wpPostId": 69731, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69713", "title": "PTE Request for sinnvoll Booking Flow", "link": "https://make.wordpress.org/polyglots/2026/08/13/pte-request-for-sinnvoll-booking-flow/", "description": "

I am the plugin author of sinnvoll Booking Flow. Please add my WordPress.org user as translation editor for the following locale:

\n\n #de_DE – @rmiarka (@tobifjellner)\n\n\n

We maintain complete German translations and would like to import and approve them.

\n

#editor-requests

", "id": 17265154, "pubDate": "Thu, 13 Aug 2026 18:45:06 GMT", "whenReceived": "Thu, 13 Aug 2026 21:44:00 GMT", "whenUpdated": "Thu, 13 Aug 2026 23:27:36 GMT", "likes": [], "metadata": { "wpPostId": 69713, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "whenReceived": "Thu, 13 Aug 2026 18:26:17 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "guid": "https://make.wordpress.org/accessibility/2026/08/13/xpost-accessibility-improvements-in-wordpress-7-1/", "title": "X-post: Accessibility Improvements in WordPress 7.1", "link": "https://make.wordpress.org/accessibility/2026/08/13/xpost-accessibility-improvements-in-wordpress-7-1/", "description": "

X-comment from +make.wordpress.org/core: Comment on Accessibility Improvements in WordPress 7.1

", "id": 17260866, "pubDate": "Thu, 13 Aug 2026 16:43:50 GMT", "whenReceived": "Thu, 13 Aug 2026 18:26:17 GMT", "whenUpdated": "Thu, 13 Aug 2026 18:26:17 GMT", "likes": [], "metadata": { "wpPostId": 17618, "wpSiteId": 29901991 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Thu, 13 Aug 2026 18:14:57 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125420", "title": "Accessibility Improvements in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/08/13/accessibility-improvements-in-wordpress-7-1/", "description": "

WordPress 7.1 continues to polish accessibility across WordPress Core and Gutenberg, advancing the goals to meet accessibility standards. In this release, high-impact changes include the new accessible tooltips API, improved predictability for screen readers, and improved labeling in many places in the admin. The editor ships with new Tab and Playlist blocks and extensive improvements to editor navigation and interaction.

\n\n\n\nCore\n\n\n\n

Enhancements to WordPress core include 45 accessibility enhancements and bug fixes. Major changes include enhancements to focus states, improvements to screen reader support in post list tables, and the introduction of a tooltip mechanism for exposing accessible names in WordPress core.

\n\n\n\nMedia\n\n\n\n

WordPress 7.1 delivers an enhanced media experience including refined labels for caption fields to provide clearer usage guidance (#43178). Navigation within theme and media modals was adjusted to prevent single-key arrow interactions from conflicting with screen reader patterns (#63760). Technical fixes address duplicate ID elements in figcaption elements when reusing images (#65315) and ensure accurate visible labeling for untitled items in the grid view (#65438). In the image editor, the width input label was corrected (#65685). Improvements to the Media grid include resolving unlabeled date filters (#65711), styling fixes for bulk editing toolbars (#65732), and ensuring focus indicators remain fully visible (#65755).

\n\n\n\nClassic Editor\n\n\n\n

The editing environment is landing with architectural improvements, such as support for invoker command attributes in KSES (#64576) and the autofocus attribute for dialog elements (#65491). Classic editor users will benefit from layout enhancements to the Publish box visibility controls (#65530) and status dropdown menus (#65532).

\n\n\n\nList Tables\n\n\n\n

List table structures were updated to identify the post title cell as the row header instead of the selection checkboxes (#32892, #65743). To assist blind users, subpages in page lists now include proper structural indicators (#64932), while untitled posts can display an excerpt of the content in post lists (#65022).

\n\n\n\nLabeling and Accessible Names\n\n\n\n

Work continues on semantic clarity, addressing missing plural forms for specific strings (#29299) and adding necessary visible text to responsive preview icons in the Customizer (#36447). Core now includes a standardized mechanism for accessible tooltips (#51006), which has been applied to metabox order buttons (#50921) and the “Remember Me” login option (#55343).

\n\n\n\nUsers\n\n\n\n

The user management flow was improved with better guidance during user deletion (#56914) and clearer identification of links on the login page (#65075). The language switcher now consistently employs visible labels and icons (#65464), and the “Add User” screen no longer forces initial focus onto the password field (#65630).

\n\n\n\nAdministration\n\n\n\n

Administrative improvements focus on high contrast and consistency. Contrast in admin color schemes was boosted for sidebar compatibility with the block editor (#65382), and active states for buttons and tabs are now properly identified in Windows High Contrast Mode (#65153, #65419). UI inconsistencies during tag management (#63372), Quick Draft error handling (#64952), and Settings API section titles (#65027) have been resolved. Further enhancements include toolbar visibility in the Site Editor (#65091), standardized focus indicators of at least 2 CSS pixels (#65645), and labeling improvements for data export requests (#65246).

\n\n\n\n

Focus states on the admin bar and the admin menu have been improved (#65765, #65726, #65445), enhancing the usability of the now-universal toolbar. Mouse cursor interaction inconsistencies when the admin menu is collapsed have been fixed (#65250). Route-based admin pages now all render appropriate feedback when JavaScript rendering is not available or fails (#65690).

\n\n\n\n

The theme browser now has consistent navigation behavior when navigating from the first theme (#65715), and the scrollbar is no longer partially hidden in the plugin installer modal (#65334). When performing setup or installation, the language of the page is made available (#65454).

\n\n\n\nFront-end\n\n\n\n

On the front end, password-protected content receives styling and usability upgrades (#64569). The RSS widget was updated to prevent accessibility issues when multiple instances are present (#47670), and the comment reply link no longer triggers unexpectedly on touch interactions (#46713).

\n\n\n\nEditor\n\n\n\n

The editor includes 43 accessibility enhancements and bug fixes covering screen reader, forced colors, and keyboard navigation improvements, as well as shipping two new front-end blocks for post content. The editor changes in 7.1 greatly improve consistency on a number of fundamental components that should lead to a better experience for all.

\n\n\n\nEditing Experience\n\n\n\n

Refinements to the editing interface include fixing keyboard activation for template action previews (#78641) and resolving focus loss issues when dismissing the pattern creation dialog (#78957). Localized aria-live regions were replaced with the more robust speak() function to improve auditory feedback (#79600). The DataForm panel layout now correctly exposes accessible names via tooltips on edit buttons (#77024), and tooltips now also display keyboard shortcuts for block movement (#76992). 

\n\n\n\n

Visual and interaction fixes address cursor instability in the color picker (#80205) and prevent layout shifts by relocating contrast warnings within the color popover (#79512). Advanced contrast checking now extends to viewport and pseudo-states (#80223), while note selections are now preserved across browser tab transitions (#75955).

\n\n\n\n

Additional refinements include adding word-break support to screen reader classes (#75539) to prevent inconsistencies, and an error in spoken messages announced during block insertion was fixed (#79004).

\n\n\n\nBlocks\n\n\n\n

Block-level improvements focus on semantic accuracy and control. The Breadcrumbs block now hides decorative separators from assistive technology (#78524), while the icon browser provides full labels for better identification (#80256). The Image block introduces a dedicated toggle for marking media as decorative (#78064), and the Cover block gains attributes to restrict video providers, helping prevent inaccessible embeds (#80092). 

\n\n\n\n

In Accordion blocks, navigation shortcuts using arrows and the “home” and “end” keys were removed (#75891) due to conflicting behaviors, and a focus loss in settings was fixed in the Stretchy Text block (#75092).

\n\n\n\nAdmin Screens\n\n\n\n

Updates to admin screens emphasize readability and standard compliance. Centered text is removed from Connectors to improve scanning (#78125), and Page component headers are promoted to h1 by default to align with core semantic structures (#77617). Focus issues in the Font Library (#78671) and labeling mismatches in the NavigableRegion (#75899) have been addressed.

\n\n\n\nAdmin Components\n\n\n\n

The component library received numerous technical fixes. Focus traps broken by specific display properties were resolved (#77381), and invalid object-based labels in ValidatedRangeControl were corrected (#77042). Help text associations were improved for ComboboxControl (#76761) and ToggleGroupControl (#76740). RadioControl fieldsets now properly employ the radiogroup role (#76745).

\n\n\n\n

For users in High Contrast mode, focus rings are now consistently rendered on Tab panels and CollapsibleCard headers (#77469, #77468). 

\n\n\n\n

Button states were also refined, addressing focusable defaults when disabled (#78526), loading indicator visibility in forced colors (#78820), and click feedback styling (#76833). Furthermore, label associations in ContentEditableControl were fixed (#80344), Dialog components now prioritize focusing content over the close button (#76910), and screen reader text for DataForm card toggles was standardized (#76039).

\n\n\n\nVisual Revisions\n\n\n\n

The Visual Revisions experience received significant updates. Contrast for difference position marker stripes was increased (#78473), and title attributes were replaced with aria-describedby for better annotation support (#80440). The timeline now includes specific labels for autosaves (#79950). Navigation was improved by auto-focusing the revisions slider (#79691) when the editor is activated.

\n\n\n\n

Non-color indicators were added using CSS outlines as secondary indicators for document changes (#78393), and proper pluralization for revision count labels (#78382) was added. The Post Summary sidebar now includes an aria-label for the revisions trigger (#78140) to provide better context for screen reader users.

\n\n\n\nNew blocks\n\n\n\n

WordPress introduces new interactive elements, including a Playlist Block (#80203) and a Tabs Block (#80163). Both blocks have been tested for accessibility concerns, although feedback is always welcome.

\n\n\n\nKnown Accessibility Regression\n\n\n\n

In WordPress 7.1, the default behavior of the media library is being changed from including a load more button to having infinite scroll, a known inaccessible pattern. 

\n\n\n\n

To compensate for this, there is an option in the User Profile allowing individual users to turn it off. You can also use the existing filter media_library_infinite_scrolling to disable it by default, returning the value false.

\n\n\n\n

A feature has been added in the WP Accessibility plugin that inverts the logic, switching the default value to ‘false’ and altering the User Profile option to allow users to turn it on.

\n\n\n\n

You can also try the Gutenberg Experiment to replace the media library. This feature is still in development, and has not had a full accessibility review. The infinite scroll in the updated media library will be governed by an in-modal toggle, and is not currently enabled.

\n\n\n\n

There is also work continuing to try to add a similar toggle to the existing media library in #65775. That work is progressing, but the implementation did not reach consensus in time to land in WordPress 7.1

\n\n\n\n

Reviewed by @annezazu, @amykamala, @sabernhardt

\n\n\n\n

\n

#7-1, #accessibility, #dev-notes, #dev-notes-7-1

", "id": 17260620, "pubDate": "Thu, 13 Aug 2026 16:43:29 GMT", "whenReceived": "Thu, 13 Aug 2026 18:14:57 GMT", "whenUpdated": "Thu, 13 Aug 2026 18:14:57 GMT", "likes": [], "metadata": { "wpPostId": 125420, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 13 Aug 2026 16:32:24 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69710", "title": "PTE Alnora", "link": "https://make.wordpress.org/polyglots/2026/08/13/pte-request-de-fr-it-hi/", "description": "

Hi Polyglots — I’m the author of Alnora, a booking plugin for private medical clinics.

\n

I’ve submitted full readme translations for German, French and Italian (126 strings each, all currently waiting). They’re my own work, not machine output, and I’d be glad to have them reviewed before anything is approved.

\n

Project: https://translate.wordpress.org/projects/wp-plugins/alnora-clinic/

\n\n #de_DE \n\n #fr_FR \n\n #it_IT\n\n\n

Username: @alnoraclinic

\n

If PTE isn’t appropriate yet, a review of the waiting suggestions would be very welcome. Thank you for your time.

\n

#editor-requests

", "id": 17257965, "pubDate": "Thu, 13 Aug 2026 16:29:48 GMT", "whenReceived": "Thu, 13 Aug 2026 16:32:24 GMT", "whenUpdated": "Fri, 14 Aug 2026 06:22:21 GMT", "likes": [], "metadata": { "wpPostId": 69710, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://wordpress.org/news/podcast/feed/", "whenReceived": "Thu, 13 Aug 2026 17:12:42 GMT", "items": [ { "feedUrl": "https://wordpress.org/news/podcast/feed/", "guid": "https://wordpress.org/news/?p=21282", "title": "Introducing the WordPress Browser Extension", "link": "https://wordpress.org/news/2026/08/browser-extension/", "description": "

The official WordPress Browser Extension is now available for Google Chrome and Chromium-based browsers in the Chrome Web Store and for Safari on macOS in the Mac App Store. This new open source extension lets logged-in site users easily hide the admin bar while keeping its most helpful shortcuts in the browser toolbar, provides quick access to all of your WordPress sites, and adds helpful tools for developers and content creators.

\n\n\n\n\n\n\n\n

By default, the admin bar sits at the top of every page you view while signed in to WordPress, keeping the dashboard, the editor, and your profile within reach. That convenience carries a cost: the bar occupies the viewport, so the page on screen is never quite the page a visitor sees. On sites doing more interesting things with the viewport, such as sticky headers or scroll-driven effects, it can introduce artifacts that send you hunting for a bug that is not there. Further, the admin bar can sometimes grow unwieldy as plugins add their own features and shortcuts to it. Switching it off in your profile settings trades one problem for another, because the shortcuts leave with it.

\n\n\n\n

That problem was the spark for the creation of the WordPress Browser Extension. The extension hides the admin bar on the sites you choose, or everywhere by default, and keeps the most commonly used shortcuts one click away. Bringing the full bar back takes two clicks and no trip to the dashboard. What began as a fix for that one tradeoff grew into something broader: a way to recognize WordPress wherever you find it on the web, to jump into your own sites from anywhere, and to carry a small set of tools for testing and review.

\n\n\n\n\n\n\n\n

As you browse, the toolbar icon shows whether the current site runs WordPress and whether you are signed in, without being obtrusive. On a site you manage, opening the extension reveals shortcuts to the dashboard or to the editor for the exact post, page, taxonomy, or template in view, including template-backed pages that open in the Site Editor on block themes. A locally stored launcher remembers the sites you sign in to, so they stay available even when you are somewhere else entirely.

\n\n\n\n

A few tools also turn out to be a better fit for the browser than for a WordPress plugin. The extension can draw block boundaries over the rendered page, open a phone-sized preview window, reload with cache busting, or clear cookies and local storage for the site you are on. Some of that is hard to do from inside a site, and none of it requires a plugin or any other software installation, so the same tools are available on every WordPress site you visit.

\n\n\n\n\n\n\n\n

All of this happens on your device. The extension reads the page in front of it to work out what it is looking at, and when it needs more than the page can tell it, it asks the site. Your preferences, and the list of sites you sign in to, stay in your browser. Nothing is sent anywhere else, and there is no tracking or analytics of any kind.

\n\n\n\n

The extension began as an independent project and became an official project with active support from Matt Mullenweg. Notable contributors include Fabian Kägy, a core contributor and colleague at Fueled (formerly 10up), who helped shape much of its early design and architecture, and Khokan Sardar who contributed multiple patches. Several other Fueled colleagues provided comprehensive testing and influenced its final shape.

\n\n\n\n

You can follow along with its development on its GitHub repository, where bug reports and pull requests are welcome.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

", "id": 17259058, "pubDate": "Thu, 13 Aug 2026 16:29:42 GMT", "whenReceived": "Thu, 13 Aug 2026 17:12:42 GMT", "whenUpdated": "Thu, 13 Aug 2026 17:12:42 GMT", "likes": [], "metadata": { "wpPostId": 21282, "wpSiteId": 14607090 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Thu, 13 Aug 2026 16:54:13 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=90299", "title": "The WordPress Credits dashboard is live: see the program grow in real time", "link": "https://make.wordpress.org/community/2026/08/13/wpcredits-dashboard/", "description": "

For the past year we have been telling the story of WordPress Credits through updates and posts: students turning open source experience into skills that launch careers, institutions building contribution into their teaching, mentors guiding it all. Starting today, you don’t have to take our word for it.

\n\n\n\n

The WP Credits dashboard is now live, and it shows the growth and impact of the program as it happens: students enrolled, institutions involved, contributions flowing into WordPress, new sites built and skills unlocked, plus testimonials from the people living the experience. Data refreshes weekly, pulled directly from our program records and WordPress.org profiles, so what you see is always the current state of the program.

\n\n\n\nJoin us\n\n\n\n

The dashboard is public, and so is the invitation. There is room for you in this program:

\n\n\n\n\nUniversities and schools: bring real open source contribution into your curriculum and give your students experience they can stand behind. Find out how you can launch your WordPress Credits program and fill out our interest form, and we will get in touch.\n\n\n\nCompanies: sponsor the program and connect with an emerging generation of WordPress talent.\n\n\n\nMentors: share what you know with students taking their first steps into the community. Join us in the #wpcredits channel on Making WordPress Slack and apply to become a program mentor.\n\n\n\n\n

Take a look at the dashboard, share it with a school or company that should be part of this, and come build the next generation of WordPress contributors with us.

\n\n\n\nSee you at WCUS\n\n\n\n

If you are coming to WordCamp US, this is the easiest way to start the conversation. We will be at the Education Table during Contributor Day on Sunday, so come sit with us, explore the dashboard together, and see how you or your organization can get involved. The rest of the days you will find us around the venue, and we are always happy to talk students, schools, and contribution, so if you spot us (@peiraisotta and @gomp), stop us. We also deeply hope to meet in person some the students and mentors behind the numbers on the dashboard.

\n\n\n\n

Kudos to the following people for reviewing this post: @webtechpooja, @roblesloaiza, @francescodicandia

", "id": 17258566, "pubDate": "Thu, 13 Aug 2026 15:28:54 GMT", "whenReceived": "Thu, 13 Aug 2026 16:54:13 GMT", "whenUpdated": "Thu, 13 Aug 2026 16:54:13 GMT", "likes": [], "metadata": { "wpPostId": 90299, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 13 Aug 2026 16:32:24 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69708", "title": "Please could we add two…", "link": "https://make.wordpress.org/polyglots/2026/08/13/please-could-we-add-two/", "description": "

Please could we add two PTEs to the 11 PublishPress plugins, please: https://profiles.wordpress.org/publishpress/

\n

The two new PTEs can Germany-German and Switzerland-German which would be de_DE and de_CH.

\n

Simea: @simea
\nCorinne: @corinneulrich

\n\n #de_DE @simea @corinneulrich\n\n #de_CH @simea @corinneulrich\n\n\n

#editor-requests

", "id": 17257966, "pubDate": "Thu, 13 Aug 2026 14:56:57 GMT", "whenReceived": "Thu, 13 Aug 2026 16:32:24 GMT", "whenUpdated": "Thu, 13 Aug 2026 21:44:00 GMT", "likes": [], "metadata": { "wpPostId": 69708, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69704", "title": "WordPress 7.1 ready to be translated", "link": "https://make.wordpress.org/polyglots/2026/08/13/wordpress-7-1-ready-to-be-translated/", "description": "

WordPress 7.1, scheduled for August 19, 2026, is now ready to be translated on translate.wordpress.org!

\n\n\n\n

If you’re looking to work on the latest translations, you’ll find them in the development projects. Also, everything for the WordPress 7.0 version is now available in its own project, which you can access here.

\n\n\n\n

WordPress 7.1 introduces several new strings. Translations that were previously completed for the Gutenberg project have been copied to the new project. This means that fewer new strings should need translating.

\n\n\n\n

Let’s embrace the joy of translating together, thank you!

\n\n\n

#7-1, #announcement

", "id": 17255377, "pubDate": "Thu, 13 Aug 2026 14:18:58 GMT", "whenReceived": "Thu, 13 Aug 2026 14:48:24 GMT", "whenUpdated": "Thu, 13 Aug 2026 14:48:24 GMT", "likes": [], "metadata": { "wpPostId": 69704, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69700", "title": "Hi Polyglots Team, I am…", "link": "https://make.wordpress.org/polyglots/2026/08/13/hi-polyglots-team-i-am-5/", "description": "

Hi Polyglots Team,

\n

I am the plugin author of WM Form4Events:

\n\nhttps://wordpress.org/plugins/wm-form4events/\n\n\n

I have prepared the German translations for the plugin and would like to maintain and approve the translations myself.

\n

Please add the following WordPress.org user as Project Translation Editor (PTE) for German:

\n\n #de_DE – @wittemarketing\n\n\n

Plugin: WM Form4Events
\nPlugin slug: wm-form4events

\n

Thank you!

\n

#editor-requests

", "id": 17255378, "pubDate": "Thu, 13 Aug 2026 13:47:47 GMT", "whenReceived": "Thu, 13 Aug 2026 14:48:24 GMT", "whenUpdated": "Thu, 13 Aug 2026 14:48:24 GMT", "likes": [], "metadata": { "wpPostId": 69700, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/test/feed/", "whenReceived": "Thu, 13 Aug 2026 14:11:15 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/2026/08/13/xpost-test-team-update-13-august-2026/", "title": "X-post: Test Team Update: 13 August, 2026", "link": "https://make.wordpress.org/test/2026/08/13/xpost-test-team-update-13-august-2026/", "description": "

X-post from +make.wordpress.org/updates: Test Team Update: 13 August, 2026

", "id": 17254256, "pubDate": "Thu, 13 Aug 2026 13:11:00 GMT", "whenReceived": "Thu, 13 Aug 2026 14:11:15 GMT", "whenUpdated": "Thu, 13 Aug 2026 14:11:15 GMT", "likes": [], "metadata": { "wpPostId": 12577, "wpSiteId": 255400204 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 13 Aug 2026 10:35:02 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69662", "title": "Hello Arabic Polyglots team,", "link": "https://make.wordpress.org/polyglots/2026/08/13/hello-arabic-polyglots-team/", "description": "

I am the plugin author. I have submitted the full Arabic translation for this plugin and would like to have it reviewed.

\n

I would also like to request Project Translation Editor (PTE) access for the Arabic locale so that I can maintain the translation going forward.

\n\nhttps://wordpress.org/plugins/zozta-connector-for-woocommerce/\n\n\n\n #ar – @abdullahghanem (@tobifjellner)\n\n\n

The Stable project is fully covered: Waiting (154), Untranslated (0), Warnings (0), Changes requested (0). The translation ships bundled with the plugin and is already in use on production stores.

\n

If you have any questions or corrections, please let me know. Thank you!

\n

#editor-requests

", "id": 17249778, "pubDate": "Thu, 13 Aug 2026 10:07:06 GMT", "whenReceived": "Thu, 13 Aug 2026 10:35:02 GMT", "whenUpdated": "Thu, 13 Aug 2026 21:44:00 GMT", "likes": [], "metadata": { "wpPostId": 69662, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69660", "title": "PTE Request for orejime", "link": "https://make.wordpress.org/polyglots/2026/08/13/pte-request-for-orejime/", "description": "

We’re the plugin authors for orejime.

\n\nhttps://wordpress.org/plugins/orejime/\n\n\n

The plugin is localized in english by default, but the team is french.
\nWe are thus requesting PTE for ourselves, as we feel pretty confident that we would be able to translate our own plugin in our native language
\nCould you grant us the role?

\n\n #fr_FR – @boscop (@audrasjb)\n\n\n

Regards

\n

#editor-requests

", "id": 17249779, "pubDate": "Thu, 13 Aug 2026 10:06:57 GMT", "whenReceived": "Thu, 13 Aug 2026 10:35:02 GMT", "whenUpdated": "Thu, 13 Aug 2026 18:16:31 GMT", "likes": [], "metadata": { "wpPostId": 69660, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69652", "title": "PTE Request for Easy Content Linker Lite", "link": "https://make.wordpress.org/polyglots/2026/08/13/pte-request-for-easy-content-linker-lite/", "description": "

Hello Polyglots! I am the plugin author of Easy Content Linker Lite
\n( https://wordpress.org/plugins/easy-content-linker-lite/ ). We have
\nprepared translations for the plugin and would like to be able to
\napprove them. Please add my WordPress.org user (@tistou80) as Project
\nTranslation Editor (PTE) for the following locales:

\n\n #fr_FR\n\n #es_ES\n\n #de_DE\n\n\n

Thank you!

\n

#editor-requests

", "id": 17249780, "pubDate": "Thu, 13 Aug 2026 10:06:48 GMT", "whenReceived": "Thu, 13 Aug 2026 10:35:02 GMT", "whenUpdated": "Thu, 13 Aug 2026 10:35:02 GMT", "likes": [], "metadata": { "wpPostId": 69652, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69648", "title": "PTE Request for Keskintech Marketplaces", "link": "https://make.wordpress.org/polyglots/2026/08/13/pte-request-for-keskintech-marketplaces/", "description": "

I am the plugin author for Keskintech Marketplaces.
\nI would like to request PTE status for the following locale:

\n\nhttps://wordpress.org/plugins/keskintech-marketplaces/\n\n\n\n #tr_TR – @furkankeskintas\n\n\n

I would like to manage and review the Turkish translations for my plugin.
\nIf you have any questions, just comment here. Thank you!

\n

#editor-requests

", "id": 17249781, "pubDate": "Thu, 13 Aug 2026 10:06:40 GMT", "whenReceived": "Thu, 13 Aug 2026 10:35:02 GMT", "whenUpdated": "Thu, 13 Aug 2026 10:35:02 GMT", "likes": [], "metadata": { "wpPostId": 69648, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69642", "title": "PTE Request for Pukulink", "link": "https://make.wordpress.org/polyglots/2026/08/13/pte-request-for-pukulink/", "description": "

I am the plugin author for Pukulink. I have translated the plugin into
\nJapanese and would like to be able to approve translations for it.
\nPlease add the following WordPress.org user as a translation editor
\nfor the respective locale:

\n\nhttps://wordpress.org/plugins/pukulink/\n\n\n\n #ja – @pukuo\n\n\n

#editor-requests

", "id": 17249782, "pubDate": "Thu, 13 Aug 2026 10:06:31 GMT", "whenReceived": "Thu, 13 Aug 2026 10:35:02 GMT", "whenUpdated": "Thu, 13 Aug 2026 10:35:02 GMT", "likes": [], "metadata": { "wpPostId": 69642, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69640", "title": "PTE Request for Inlarge – Inline Image Zoom", "link": "https://make.wordpress.org/polyglots/2026/08/13/pte-request-for-inlarge-inline-image-zoom/", "description": "

I am the plugin author for Inlarge. I would like to become the PTE for this plugin I created myself.

\n\nhttps://wordpress.org/plugins/inlarge/\n\n\n\n #ja – @kyo-ichida\n\n\n

#editor-requests

", "id": 17249783, "pubDate": "Thu, 13 Aug 2026 10:06:22 GMT", "whenReceived": "Thu, 13 Aug 2026 10:35:02 GMT", "whenUpdated": "Thu, 13 Aug 2026 10:35:02 GMT", "likes": [], "metadata": { "wpPostId": 69640, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69619", "title": "PTE Request for Pihlfelt Image Assistant", "link": "https://make.wordpress.org/polyglots/2026/08/13/pte-request-for-pihlfelt-image-assistant/", "description": "

I am the plugin author for Pihlfelt Image Assistant ( https://wordpress.org/plugins/pihlfelt-image-assistant/ ). We have imported our own translations and would like to have them approved. Please add my WordPress.org username pihlfelt as translation editor (PTE) for the following locales:

\n\n #sv_SE (@tobifjellner)\n\n #de_DE\n\n #fr_FR\n\n\n

Thank you!

\n

#editor-requests

", "id": 17249784, "pubDate": "Thu, 13 Aug 2026 10:06:13 GMT", "whenReceived": "Thu, 13 Aug 2026 10:35:02 GMT", "whenUpdated": "Thu, 13 Aug 2026 10:35:02 GMT", "likes": [], "metadata": { "wpPostId": 69619, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69615", "title": "Hi, I’m the author of…", "link": "https://make.wordpress.org/polyglots/2026/08/13/hi-im-the-author-of-10/", "description": "

Hi,

\n

I’m the author of the plugin “QAS Domain Checker – WHOIS RDAP”
\n(slug: qas-domain-rdap-whois), WordPress.org username: qasolutions.

\n

I’d like to request Project Translation Editor (PTE) rights for the
\n[Spanish / Catalan / English] locale on this plugin, so I
\ncan review and approve translation suggestions directly — including
\nmy own, since I wrote the original source strings and know their
\nexact context (form labels, RDAP-specific terminology, error
\nmessages, etc.).

\n

Plugin project:

\n\nPlugin: https://wordpress.org/plugins/qas-domain-rdap-whois/\n\n\n\n #es_ES \n\n #ca \n\n #en_GB \n\n\n

Thank you!

\n

#editor-requests

", "id": 17249785, "pubDate": "Thu, 13 Aug 2026 10:06:03 GMT", "whenReceived": "Thu, 13 Aug 2026 10:35:02 GMT", "whenUpdated": "Thu, 13 Aug 2026 10:35:02 GMT", "likes": [], "metadata": { "wpPostId": 69615, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69650", "title": "Hallo zusammen Ich habe zwei…", "link": "https://make.wordpress.org/polyglots/2026/08/13/hallo-zusammen-ich-habe-zwei/", "description": "

Hallo zusammen

\n

Ich habe zwei Fragen zu meinem Plugin Fliegerlogin – SSO for Vereinsflieger (Slug sso-for-vereinsflieger, WordPress.org-Benutzername patois87).

\n

1. Das Unterprojekt „Stable (latest release)” für den Code fehlt.
\ndev, dev-readme und stable-readme sind vorhanden, nur stable liefert 404:
\nhttps://translate.wordpress.org/projects/wp-plugins/sso-for-vereinsflieger/stable/de/default/

\n

Der Stable-Tag scheint in Ordnung: tags/3.0.0/ existiert im SVN, Stable tag: 3.0.0 steht sowohl in trunk/readme.txt als auch in tags/3.0.0/readme.txt, und die Plugin-API fĂźhrt 3.0.0 als eigene Version neben trunk. Das Readme-Projekt fĂźr Stable wurde inzwischen angelegt, das Code-Projekt nicht. Fehlt da noch ein Schritt von meiner Seite, oder mĂźsste ein Reimport angestossen werden?

\n

2. PTE fĂźr de_CH.
\nFür de_DE habe ich die Rechte und dort ist alles freigegeben (62 von 62 Zeichenketten). Für Schweizerdeutsch habe ich die Übersetzung ebenfalls importiert — 62 Zeichenketten im Code-Projekt, 65 im Readme-Projekt —, sie liegt aber vollständig als waiting, weil mir dort die Rechte fehlen. Könnte ich PTE für de_CH bekommen? Die Fassung ist aus de_DE abgeleitet und unterscheidet sich nur in der Schreibung des Eszett.

\n

Die deutschen Übersetzungen habe ich nach dem Hinweis bei der PTE-Vergabe gegen Glossar und Style Guide durchgesehen und überarbeitet (unter anderem login → Anmeldung, user → Benutzer, account → Konto, Gedankenstrich statt Geviertstrich).

\n

Danke euch!

\n

#editor-requests

", "id": 17246987, "pubDate": "Thu, 13 Aug 2026 05:45:08 GMT", "whenReceived": "Thu, 13 Aug 2026 07:07:54 GMT", "whenUpdated": "Thu, 13 Aug 2026 07:07:54 GMT", "likes": [], "metadata": { "wpPostId": 69650, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Wed, 12 Aug 2026 18:54:03 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125465", "title": "WordPress 7.2 Call for Volunteers", "link": "https://make.wordpress.org/core/2026/08/12/wordpress-7-2-call-for-volunteers/", "description": "

Planning is underway for WordPress 7.2!  This post outlines the proposed schedule along with a call for volunteers to support the release process.

\n\n\n\n

Following the typical cadence, the proposed final release date for 7.2 is Wednesday, December 9, 2026.  This proposed timeline remains flexible for the resulting Release Squad and adjustments can be made if necessary as they determine what timeline works best for their schedule as well as adjustments in coordination with State of the Word.

\n\n\n\nProposed Schedule\n\n\n\nMilestoneDateAlpha BeginsImmediately (7.2-alpha began in trunk on August 10th with [63167])Beta 1October 20-22Beta 2October 27-29Beta 3November 3-5Beta 4November 10-12Release Candidate 1November 17-19Release Candidate 2November 24-26Release Candidate 3December 1-3Dry RunDecember 7-9Final ReleaseDecember 8-10\n\n\n\n

As always, all dates are subject to change based on development progress.

\n\n\n\n\n\n\n\nCall for Volunteers\n\n\n\n

Each WordPress release depends on contributors from across the project coming together to make it a success. 

\n\n\n\n

As with the 6.7, 6.8, 6.9, 7.0, and 7.1 release cycles, WordPress 7.2 will continue the approach of forming a smaller, focused Release Squad based on feedback received.  This streamlined structure places more emphasis on collaboration with the various Make Team Reps, who are encouraged to help coordinate efforts from within their respective teams.  The goals are to reduce the overhead on the Release Squad while still ensuring each team’s contributions and priorities are represented throughout the cycle, and to reduce overlap between a Make Team Rep and that team’s Release Squad Leads.  Noteworthy Contributors will be captured from Team Reps towards the end of the release cycle.

\n\n\n\n

While the end goal is to publish the final release of WordPress 7.2 at State of the Word (aka SotW), traveling to or attending SotW is not a requirement to serve on the release squad.  All communication related to the release process will continue to take place in the #core Slack channel.

\n\n\n\n

If you are interested in helping lead WordPress 7.2 in one of the following roles, please comment below or reach out in the #7-2-release-leads Slack channel:

\n\n\n\n\nRelease Lead – sets overall goals, makes final decisions on merging, gives final reviews where needed\n\n\n\nRelease Coordination – helps manage timelines, cross-team collaboration, and status updates\n\n\n\nTech Leads – oversees core development (including Gutenberg), triage, and critical issues\n\n\n\nTriage Lead – help monitor issues, shepherd patches, and guide contributors\n\n\n\nTest Lead – coordinates testing efforts across the community and test reports\n\n\n\n\n

Whether you have led a release before or are looking to get involved for the first time, there are many ways to contribute.  Volunteers of all backgrounds and experience levels are welcome!

\n\n\n\n

If you are interested in volunteering, please leave a comment below noting your preferred area(s) by Friday, August 28th. @4thhubbard (or a designee), will review the nominations shortly after to confirm and announce the release squad as soon as possible.

\n\n\n\n

Together we can make WordPress 7.2 the best one yet!

\n\n\n\n

Props to @4thhubbard @annezazu @jorbin @desrosj for reviewing this post.

\n

#7-2

", "id": 17235796, "pubDate": "Wed, 12 Aug 2026 18:12:07 GMT", "whenReceived": "Wed, 12 Aug 2026 18:54:03 GMT", "whenUpdated": "Wed, 12 Aug 2026 18:54:03 GMT", "likes": [], "metadata": { "wpPostId": 125465, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed/", "whenReceived": "Wed, 12 Aug 2026 16:31:03 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed/", "guid": "https://make.wordpress.org/core/?p=125449", "title": "WordPress 7.1 Release Candidate 3", "link": "https://make.wordpress.org/core/2026/08/12/wordpress-7-1-release-candidate-3/", "description": "

Note: This post has been published on Make/Core in light of the WordPress 7.0.4 security release. You can read more about the security release.
WordPress 7.1 RC2 was released on August 6, 2026, as part of the WordPress 7.0.3 security release.

\n\n\n\n\n

The third Release Candidate (“RC3”) for WordPress 7.1 is ready for download and testing!

\n\n\n\n

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

\n\n\n\n

Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 7.1 is the best it can be.

\n\n\n\n

You can test WordPress 7.1 RC3 in four ways:

\n\n\n\nPluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).Direct DownloadDownload the RC3 version (zip) and install it on a WordPress website.Command LineUse the following WP-CLI command: wp core update --version=7.1-RC3WordPress PlaygroundUse the 7.1 RC3 WordPress Playground instance to test the software directly in your browser without the need for a separate site or setup.\n\n\n\n

The scheduled final release date for WordPress 7.1 is August 19, 2026. The full release schedule can be found here. Your help testing RC versions is vital to making this release as stable and powerful as possible.

\n\n\n\n

Please continue checking the Make WordPress Core blog for 7.1-related posts for more updates and information.

\n\n\n\nWhat’s in WordPress 7.1 RC3?\n\n\n\n

WordPress 7.1 RC3 contains more than 90 updates and fixes since the RC1 release, including 37 in the Editor and 57 in Core.

\n\n\n\n

Want to look deeper into the details and technical notes for this release? Take a look at the WordPress 7.1 Field Guide. For technical information related to issues addressed since WordPress 7.1 RC1 release, you can browse the following links:

\n\n\n\n\nGutenberg commits for 7.1 since August 05\n\n\n\nClosed WordPress Core Trac tickets since August 05\n\n\n\n\nHow you can contribute\n\n\n\n

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

\n\n\n\nGet involved in testing\n\n\n\n

Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. 

\n\n\n\n

Your help testing the WordPress 7.1 RC3 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.1.

\n\n\n\n

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report.  You can also check your issue against a list of known bugs. 

\n\n\n\n

Curious about testing releases in general?  Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

\n\n\n\nUpdate your theme or plugin\n\n\n\n

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.

\n\n\n\n

Thanks for continuing to test your themes and plugins with the WordPress 7.1 beta releases. If you haven’t yet, make sure to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 7.1

\n\n\n\n

If you find compatibility issues, please post detailed information to the support forum.

\n\n\n\nTest on your hosting platforms\n\n\n\n

Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue.

\n\n\n\n

Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here. 

\n\n\n\nHelp translate WordPress\n\n\n\n

Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ?  You can help translate WordPress into more than 100 languages. This release milestone (RC3) also marks the hard string freeze point of the 7.1 release cycle.

\n\n\n\nAn RC3 haiku\n\n\n\n

Small cracks catch the light,
We polish, not propose—
Almost ready now.

\n\n\n\n

Props to @benjamin_zekavica, @amykamala, @wildworks and @annezazu for proofreading and review.

\n

#7-1, #development, #release

", "id": 17232166, "pubDate": "Wed, 12 Aug 2026 15:57:47 GMT", "whenReceived": "Wed, 12 Aug 2026 16:31:03 GMT", "whenUpdated": "Wed, 12 Aug 2026 16:31:03 GMT", "likes": [], "metadata": { "wpPostId": 125449, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/test/feed/", "whenReceived": "Wed, 12 Aug 2026 15:07:59 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/?p=12555", "title": "Test Chat Summary: August 6th, 2026", "link": "https://make.wordpress.org/test/2026/08/12/test-chat-summary-august-6th-2026/", "description": "

Huddle notes: 8/7/26 in #core-test. AI took notes for this huddle from 1:02:18 AM – 1:59:19 AM GMT+10. WordPress test team reviewed four GitHub issues, closed learner pathways, assigned handbook documentation for test flow plugin, and identified blockers requiring external team coordination.

\n\n\n\nAttendees\n\n\n\n

@MosesCursor, @ikamal, @huzaifaalmesbah, @ozgursar, @r1k0, @ismail0071, and @mbigul

\n\n\n\nSummary\n\n\n\nTest Handbook Restructuring for Multiple Domains\n\n\n\n\n@huzaifaalmesbah proposed keeping issue #111 open and splitting into sub-issues or assigning to new contributors for core testing guidance. [30:58]\n\n\n\n@ozgursar noted restructuring requires moving all current content under core directory, affecting entire handbook structure. [32:28]\n\n\n\n@huzaifaalmesbah and @ozgursar agreed to start with core and Gutenberg directories, deferring AI and performance sections until content exists. [33:31]\n\n\n\n@Moses Cursor proposed reaching out to AI and performance teams for testing content; team agreed external input is necessary before proceeding. [36:02]\n\n\n\n\nLearner Pathways Issue Closure\n\n\n\n\n@huzaifaalmesbah confirmed learner pathways look good for beginners and are ready to close. [26:16]\n\n\n\n@Moses Cursor closed issue after team confirmation. [26:51]\n\n\n\n\nTest Flow Plugin Documentation\n\n\n\n\n@ozgursar reported plugin is working and ready for use via playground; only handbook documentation remains. [39:33]\n\n\n\n@r1k0 suggested adding plugin documentation as a section in moderator guide rather than standalone page. [48:41]\n\n\n\n@huzaifaalmesbah proposed including test report plugin and chat monitor guide in patch testing section. [53:00]\n\n\n\n@ozgursar will submit plugin to WordPress directory from personal account after handbook documentation is complete. [45:08]\n\n\n\n\nTeam Goals and Initiatives Issue\n\n\n\n\n@Moses Cursor noted issue #9 is unclear and suggested retiring or deferring for internal discussion with Nikunj. [17:07]\n\n\n\n@huzaifaalmesbah recommended keeping issue open and following other teams’ goal structures before proceeding. [18:49]\n\n\n\n\nTags vs. Categories Discussion\n\n\n\n\n@ozgursar raised whether handbook switched from categories to tags; @r1k0 confirmed not yet and questioned necessity. [17:44]\n\n\n\n@r1k0 identified issue #109 as related tags discussion and committed to reviewing and posting feedback. [21:17]\n\n\n\n\nAnnouncements and Schedule\n\n\n\n\nWeekly patch testing scrub: 2nd and 4th Thursday at 15:00 UTC; weekly test chat: 3rd Thursday; monthly voice chat: 1st Thursday.\n\n\n\nMultiple calls for testing available including WordPress 7.1, media editor, and responsive styling.\n\n\n\n\nAction items\n\n\n\n\n@ikamal create handbook section documenting test flow plugin in moderator guide. [47:06]\n\n\n\n@ozgursar submit test flow plugin to WordPress directory after handbook documentation complete. [45:08]\n\n\n\n@Moses Cursor coordinate with AI and performance teams to identify testing content and requirements. [36:02]\n\n\n\n@r1k0 review issue #109 on tags and post feedback. [21:17]\n\n\n\n\nFiles and media\n\n\n\n\nhttps://make.wordpress.org/test/2026/08/06/team-chat-agenda-6th-august-2026/\n\n\n\nhttps://make.wordpress.org/test/handbook/test-reports/patch-testing/#generating-reports-with-the-test-reports-plugin\n\n\n\nhttps://make.wordpress.org/core/2026/07/01/whats-new-in-gutenberg-23-5-july-1-2026/\n\n\n\nhttps://make.wordpress.org/core/2026/07/02/merge-proposal-expanding-wordpress-core-abilities/\n\n\n\nhttps://make.wordpress.org/core/2026/07/03/bug-scrub-schedule-for-wordpress-7-1/\n\n\n\nhttps://make.wordpress.org/core/2026/07/07/the-classic-block-stays-in-the-inserter-for-wordpress-7-1/\n\n\n\nhttps://make.wordpress.org/test/2026/07/15/help-test-wordpress-7-1/\n\n\n\nhttps://make.wordpress.org/core/2026/05/21/media-editor-modal-call-for-testing/\n\n\n\nhttps://make.wordpress.org/core/2026/06/04/call-for-testing-client-side-media-processing/\n\n\n\nhttps://make.wordpress.org/test/2026/05/28/help-test-new-career-functionality-on-wordpress-org/\n\n\n\nhttps://make.wordpress.org/test/2026/07/03/call-for-testing-responsive-styling/\n\n

#test-chat-summary

", "id": 17229609, "pubDate": "Wed, 12 Aug 2026 14:47:52 GMT", "whenReceived": "Wed, 12 Aug 2026 15:07:59 GMT", "whenUpdated": "Wed, 12 Aug 2026 15:07:59 GMT", "likes": [], "metadata": { "wpPostId": 12555, "wpSiteId": 255400204 }, "ctLikes": 0 } ] }, { "feedUrl": "https://wordpress.org/news/podcast/feed/", "whenReceived": "Wed, 12 Aug 2026 16:25:25 GMT", "items": [ { "feedUrl": "https://wordpress.org/news/podcast/feed/", "guid": "https://wordpress.org/news/?p=21371", "title": "WordPress 7.0.4 Release", "link": "https://wordpress.org/news/2026/08/wordpress-7-0-4-release/", "description": "WordPress 7.0.4 is now available\n\n\n\n

WordPress 7.0.4 is now available which features a security fix. Because this is a security release, it is recommended that you update your sites immediately.

\n\n\n\n

You can update to WordPress 7.0.4 by downloading it from WordPress.org, or visiting your site’s Dashboard → Updates and clicking Update Now. Sites that support automatic background updates will begin updating shortly.

\n\n\n\n

For more information, please visit the WordPress 7.0.4 HelpHub site.

\n\n\n\nSecurity update included in this release\n\n\n\n

The security team would like to thank the team at pwn.ai for responsibly reporting the following vulnerability and allowing it to be fixed in this release:

\n\n\n\n\nAuthenticated Author+ remote code execution via malicious file upload on sites that use Imagick and Ghostscript.\n\n\n\n\nBackports\n\n\n\n

As a courtesy, these fixes are being backported through to the 4.7 branch and the 7.1 RC3 release that’s due later today. As a reminder, only the most recent version of WordPress is actively supported. The backports are in progress and will ship as they become ready.

\n\n\n\nCVE and GHSA references\n\n\n\n

Further details can be found in the advisory: CVE-2026-65640 / GHSA-8vr3-7mxf-gx8w.

\n\n\n\nThank you to these WordPress contributors\n\n\n\n

This release was led by John Blackbourn, with significant input from Dennis Snell and Jeremy Felt. In addition, WordPress 7.0.4 and its backports would not have been possible without the valuable contributions of the following people:

\n\n\n\n

Aaron D. Campbell, Aaron Jorbin, Adam Silverstein, Aki Hamano, Alex Concha, Barry, Dennis Snell, Ehtisham Siddiqui, Jeremy Felt, John Blackbourn, Jon Surrell, Jonathan Desrosiers, Lance Willett, Marin Atanasov, Mohammad Jangda, Sergey Biryukov, vortfu, Weston Ruter, and representatives from WP Engine.

\n\n\n\n

", "id": 17232047, "pubDate": "Wed, 12 Aug 2026 14:45:53 GMT", "whenReceived": "Wed, 12 Aug 2026 16:25:25 GMT", "whenUpdated": "Thu, 13 Aug 2026 17:12:42 GMT", "likes": [], "metadata": { "wpPostId": 21371, "wpSiteId": 14607090 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Wed, 12 Aug 2026 15:35:16 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69621", "title": "Hi Polyglots Team,", "link": "https://make.wordpress.org/polyglots/2026/08/12/hi-polyglots-team-54/", "description": "

I am the owner of the WordPress.org account @nsthemes, representing NoStudio S.r.l.s., an Italian company and plugin developer.

\n

Our profile currently shows:

\n

bg_BG – Bulgarian – Plugins Translation Editor

\n

However, we have never contributed to Bulgarian translations and we do not speak Bulgarian. This appears to be an old PTE assignment that is no longer relevant.

\n

Could you please remove the bg_BG PTE role from @nsthemes?

\n

The PTE assignment appears to be related to our plugin:

\n\nhttps://wordpress.org/plugins/ns-remove-related-products-for-woocommerce/\n\n\n

We would like to keep our account associated with Italian (it_IT), as we are an Italian company and our plugins are developed and maintained in Italian.

\n

Thank you for your help!

\n

Best regards,

\n

NsThemes Team
\n@nsthemes

\n

#request

", "id": 17230622, "pubDate": "Wed, 12 Aug 2026 14:45:27 GMT", "whenReceived": "Wed, 12 Aug 2026 15:35:16 GMT", "whenUpdated": "Wed, 12 Aug 2026 15:35:16 GMT", "likes": [], "metadata": { "wpPostId": 69621, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69613", "title": "PTE Request for Web Makinası – 404 Manager", "link": "https://make.wordpress.org/polyglots/2026/08/12/pte-request-for-web-makinasi-404-manager/", "description": "

I am the plugin author for

\n\nWeb Makinası – 404 Manager and\n\nWeb Makinası – Chat Button.\n\n\n

We have a number of great translation editors that we’d like to be able to approve translation for our plugin(s). Please add the following WordPress.org users as translation editors for their respective locales:

\n\nhttps://tr.wordpress.org/plugins/webmakinasi-404-manager/\n\n\n\n #tr_TR – @webmakinasi\n\n\n

If you have any questions, just comment here. Thank you!

\n

cc: @emre

\n

#editor-requests

", "id": 17222906, "pubDate": "Wed, 12 Aug 2026 10:23:32 GMT", "whenReceived": "Wed, 12 Aug 2026 10:24:43 GMT", "whenUpdated": "Wed, 12 Aug 2026 10:24:43 GMT", "likes": [], "metadata": { "wpPostId": 69613, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69611", "title": "Hello, I am the developer…", "link": "https://make.wordpress.org/polyglots/2026/08/12/hello-i-am-the-developer-2/", "description": "

Hello,

\n

I am the developer and maintainer of the **Mairie RĂŠservation de Salles** plugin, and I would like to become a **Translation Editor (PTE)** for this project.

\n

I am actively maintaining the plugin and its French translations, including the **Stable** and **Development Readme** projects. I have already prepared and reviewed the French translations and would like to be able to review and approve translations for this plugin directly.

\n

Becoming a Translation Editor would also allow me to review and validate **all pending French translations** for the plugin, ensuring that they can be approved and made available to users without unnecessary delays.

\n

As the plugin is primarily intended for French municipalities, I will ensure that the French translations remain accurate, consistent, clear, and appropriate for French municipalities and WordPress users.

\n

Plugin: https://wordpress.org/plugins/mairie-reservation-de-salles/

\n

“`text
\n#fr_FR @verturin (@verturin)
\n“`

\n

Thank you for considering my request.

\n

#editor-requests

", "id": 17222907, "pubDate": "Wed, 12 Aug 2026 09:59:44 GMT", "whenReceived": "Wed, 12 Aug 2026 10:24:43 GMT", "whenUpdated": "Wed, 12 Aug 2026 10:24:43 GMT", "likes": [], "metadata": { "wpPostId": 69611, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/hosting/feed/", "whenReceived": "Wed, 12 Aug 2026 09:02:04 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/hosting/feed/", "guid": "https://make.wordpress.org/hosting/?p=188317", "title": "Hosting Team Meeting Agenda 2026-08-12", "link": "https://make.wordpress.org/hosting/2026/08/12/hosting-team-meeting-agenda-2026-08-12/", "description": "Next Meeting\n\n\n\n

The next meetings will be in the #hosting channel on Wednesday, August 12, 2026 at 0900 UTC and Wednesday, August 12, 2026 at 1800 UTC. Hope to see you then!

\n\n\n\nAgenda\n\n\n\nWP\n\n\n\n\n\n7.0.3 security release\n\n\n\n7.1 RC1 and RC2 released last week.\n\n\n\nRC3 August 12th, final release August 19th at WCUS\n\n\n\nWordPress 7.1 Field Guide\n\n\n\nWhat’s new for developers? (August 2026)\n\n\n\n\nHosting Team\n\n\n\n\nWCUS Contributor Day prep\n\n\n\nTickets/PRs\n\n\n\n\nOpen Floor\n\n\n\n

Anything else? Please leave a comment with any additions or suggestions for the meeting.

\n\n\n\n


Props to @chaion07 for the pre-publish review.

\n

#agenda, #hosting, #hosting-community, #meetings, #weekly-hosting-chat

", "id": 17221397, "pubDate": "Wed, 12 Aug 2026 08:31:18 GMT", "whenReceived": "Wed, 12 Aug 2026 09:02:04 GMT", "whenUpdated": "Wed, 12 Aug 2026 09:02:04 GMT", "likes": [], "metadata": { "wpPostId": 188317, "wpSiteId": 120824672 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Wed, 12 Aug 2026 08:41:16 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69601", "title": "PTE Request for Atromax Theme", "link": "https://make.wordpress.org/polyglots/2026/08/12/pte-request-for-atromax-theme/", "description": "

I’ve suggested translations for the Atromax theme and would like to have them reviewed. I’d also like to become a PTE. I also confirm that I’ve read the style guide and glossary for the locales.

\n

Atromax : – https://wordpress.org/themes/atromax/

\n\n #ko_KR \n\n #zh_CN (@tobifjellner)\n\n #de_DE \n\n #ja\n\n\n

Thank you!

\n

#editor-requests

", "id": 17221177, "pubDate": "Wed, 12 Aug 2026 07:56:25 GMT", "whenReceived": "Wed, 12 Aug 2026 08:41:16 GMT", "whenUpdated": "Wed, 12 Aug 2026 08:41:16 GMT", "likes": [], "metadata": { "wpPostId": 69601, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69598", "title": "PTE Request for Xenon Comment Review Agent", "link": "https://make.wordpress.org/polyglots/2026/08/12/pte-request-for-xenon-comment-review-agent/", "description": "

PTE Request for Xenon Comment Review Agent
\nPlugin: https://wordpress.org/plugins/xenon-comment-review-agent/

\n\n #zh_CN @xenon2233 (@tobifjellner)\n\n\n

I’ve already submitted a complete zh_CN translation of the readme
\nas suggestions.

\n

#editor-requests

", "id": 17221178, "pubDate": "Wed, 12 Aug 2026 07:52:50 GMT", "whenReceived": "Wed, 12 Aug 2026 08:41:16 GMT", "whenUpdated": "Wed, 12 Aug 2026 08:41:16 GMT", "likes": [], "metadata": { "wpPostId": 69598, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69586", "title": "PTE Request for AILYS Lens", "link": "https://make.wordpress.org/polyglots/2026/08/12/pte-request-for-ailys-lens/", "description": "

Hello Polyglots! I am the plugin author for AILYS Lens ( https://wordpress.org/plugins/ailys-lens/ ). Please add my WordPress.org account as translation editor (PTE) for the following locale:

\n\n #ja @roadleon\n\n\n

I am a native Japanese speaker and will maintain the Japanese translations myself. Thank you!

\n

#editor-requests

", "id": 17221179, "pubDate": "Wed, 12 Aug 2026 07:27:06 GMT", "whenReceived": "Wed, 12 Aug 2026 08:41:16 GMT", "whenUpdated": "Wed, 12 Aug 2026 08:41:16 GMT", "likes": [], "metadata": { "wpPostId": 69586, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69584", "title": "PTE Request for Cookie Rocket", "link": "https://make.wordpress.org/polyglots/2026/08/12/pte-request-for-cookie-rocket/", "description": "

I am the plugin author for Cookie Rocket. I have prepared and reviewed the Spanish translation of the plugin and its readme, and I would like to be able to approve translations for it. Please add the following WordPress.org user as translation editor for the respective locales:

\n\nhttps://wordpress.org/plugins/cookie-rocket/\n\n\n\n #es_ES – @templatesrocketwp\n\n #es_MX – @templatesrocketwp\n\n\n

A note on how these were produced, for transparency: the interface strings were translated by hand for the plugin’s own bundled es_ES catalogue and have shipped with the plugin for several releases. The readme was drafted with machine assistance and then reviewed string by string against the es_ES glossary and style guide by me — I am a native Spanish speaker. I checked tuteo throughout, glossary terms (plugin, ajustes, banner, shortcode, Escritorio), HTML and shortcode integrity, and I corrected the entries the tooling flagged.

\n

All 515 strings per locale are currently waiting. Happy to make any changes the locale team asks for.

\n

If you have any questions, just comment here. Thank you!

\n

#editor-requests

", "id": 17221180, "pubDate": "Wed, 12 Aug 2026 07:26:54 GMT", "whenReceived": "Wed, 12 Aug 2026 08:41:16 GMT", "whenUpdated": "Wed, 12 Aug 2026 08:41:16 GMT", "likes": [], "metadata": { "wpPostId": 69584, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69582", "title": "Plugin name: AIEL Smart…", "link": "https://make.wordpress.org/polyglots/2026/08/12/plugin-name-aiel-smart/", "description": "

Plugin name: AIEL Smart Assistant (智能秘書)
\nPlugin URL: https://wordpress.org/plugins/aiel-smart-assistant/

\n\n #zh_TW @aielapp\n\n\n

I am the plugin author and would like to maintain the
\nTraditional Chinese translation for this plugin.

\n

#editor-requests

", "id": 17221181, "pubDate": "Wed, 12 Aug 2026 07:26:15 GMT", "whenReceived": "Wed, 12 Aug 2026 08:41:16 GMT", "whenUpdated": "Wed, 12 Aug 2026 08:41:16 GMT", "likes": [], "metadata": { "wpPostId": 69582, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69574", "title": "Japanese translation review and PTE request for 11 Neutrope plugins", "link": "https://make.wordpress.org/polyglots/2026/08/12/japanese-translation-review-and-pte-request-for-11-neutrope-plugins/", "description": "

Hello Japanese Polyglots team,

\n

I am the plugin author for the following 11 plugins. I have submitted Japanese translations for the Stable Readme short descriptions and would like to have them reviewed.

\n

I would also like to request Project Translation Editor (PTE) access for the Japanese locale so that I can maintain the Japanese descriptions for these plugins.

\n\nhttps://wordpress.org/plugins/neutrope-admin-post-lookup/\n\nhttps://wordpress.org/plugins/neutrope-blueprint-drafts/\n\nhttps://wordpress.org/plugins/neutrope-flow/\n\nhttps://wordpress.org/plugins/neutrope-japanese-invoice-pdfs-for-woocommerce/\n\nhttps://wordpress.org/plugins/neutrope-lead-desk-for-contact-form-7/\n\nhttps://wordpress.org/plugins/neutrope-marketing-desk/\n\nhttps://wordpress.org/plugins/neutrope-quiet-shield/\n\nhttps://wordpress.org/plugins/neutrope-redirect-flow-for-contact-form-7/\n\nhttps://wordpress.org/plugins/neutrope-seo-report-dashboard/\n\nhttps://wordpress.org/plugins/quick-stock-bridge/\n\nhttps://wordpress.org/plugins/teenybar/\n\n\n\n #ja – @neutropeinc\n\n\n

The submitted translations are limited to one Stable Readme short-description string per plugin. All 11 projects currently show Waiting (1) and Warnings (0).

\n

If you have any questions or corrections, please let me know. Thank you!

\n

#editor-requests

", "id": 17221182, "pubDate": "Wed, 12 Aug 2026 07:25:59 GMT", "whenReceived": "Wed, 12 Aug 2026 08:41:16 GMT", "whenUpdated": "Wed, 12 Aug 2026 08:41:16 GMT", "likes": [], "metadata": { "wpPostId": 69574, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "whenReceived": "Wed, 12 Aug 2026 08:06:18 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "guid": "https://make.wordpress.org/accessibility/?p=17609", "title": "Accessibility Team Meeting Agenda: August 13, 2026", "link": "https://make.wordpress.org/accessibility/2026/08/12/accessibility-team-meeting-agenda-august-13-2026/", "description": "

This is the proposed agenda for the bi-weekly Accessibility Team meeting on Thursday, August 13, 2026 15:00 UTC

\n\n\n\n Announcements\n\n\n\n\n7.1 RC3 is scheduled to be released on Wed Aug 12th (today)\n\n\n\n7.1 RC1 was released Wed August 5th.\n\n\n\nWordPress 7.1 Field Guide is published.\n\n\n\n7.1 Release Candidate phase\n\n\n\n7.0.3 Security release is released as part of WordPress 7.1 RC2\n\n\n\nWhat’s new in Gutenberg 23.7 is also published.\n\n\n\nWCUS 2026 is next week and WordPress 7.1 is planned to release live at WCUS on August 19th. The release time is yet to be announced.\n\n\n\n\nProposed Discussion\n\n\n\n

@annezazu has proposed the discuss around the accessibility lab

\n\n\n\nWorking groups\n\n\n\n\nWordPress Core and the Block Editor\n\n\n\nAccessibility-ready Program\n\n\n\nDocumentation about Web Accessibility\n\n\n\n\nOpen floor\n\n\n\n

If you want to have a topic added to the agenda, please mention it in the comments of this post.

\n\n\n\n

The Accessibility Team bug scrub is every Tuesday at 16:00 UTC, held in the #accessibility channel on the Make WordPress Slack (registration required).

\n

#accessibility, #agenda

", "id": 17220752, "pubDate": "Wed, 12 Aug 2026 06:36:15 GMT", "whenReceived": "Wed, 12 Aug 2026 08:06:18 GMT", "whenUpdated": "Thu, 13 Aug 2026 16:42:09 GMT", "likes": [], "metadata": { "wpPostId": 17609, "wpSiteId": 29901991 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/training/feed/", "whenReceived": "Wed, 12 Aug 2026 04:12:46 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/training/feed/", "guid": "https://make.wordpress.org/training/2026/08/12/xpost-hands-on-activity-kits-now-live-on-learn-wordpress/", "title": "X-post: Hands-on Activity Kits Now Live on Learn WordPress", "link": "https://make.wordpress.org/training/2026/08/12/xpost-hands-on-activity-kits-now-live-on-learn-wordpress/", "description": "

X-comment from +make.wordpress.org/community: Comment on Hands-on Activity Kits Now Live on Learn WordPress

", "id": 17218214, "pubDate": "Wed, 12 Aug 2026 02:49:29 GMT", "whenReceived": "Wed, 12 Aug 2026 04:12:46 GMT", "whenUpdated": "Wed, 12 Aug 2026 04:12:46 GMT", "likes": [], "metadata": { "wpPostId": 177262, "wpSiteId": 46403572 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Wed, 12 Aug 2026 03:32:08 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=90286", "title": "Hands-on Activity Kits Now Live on Learn WordPress", "link": "https://make.wordpress.org/community/2026/08/12/hands-on-activity-kits-now-live-on-learn-wordpress/", "description": "

Activity kits are now live on Learn WordPress, and we want to make sure community members know about them!

\n\n\n\n

A WordPress activity kit is a complete, ready-to-run session package for anyone (event organizers, facilitators, instructors, etc) who wants to teach about WordPress topics. Each kit includes a facilitator guide and slide deck, all within a single downloadable zip. This is everything you need to run a hands-on session without preparing materials from scratch. All kits are designed to work in WordPress Playground (no installation or accounts required) or an equivalent free environment, run in 60–90 minutes, and produce something tangible by the end.

\n\n\n\n

You can browse the full library at learn.wordpress.org/activity-library.

\n\n\n\n\n\n\n\nWhat’s available now\n\n\n\n

Eleven kits are ready to download and use:

\n\n\n\n\nContributor Onboarding: Participants explore the Make WordPress contributor pathways, create the accounts they need, and make their first real contribution before the session ends. (60 minutes, Beginner)\n\n\n\nAccessibility Testing in WordPress: Participants use the Accessibility Checker plugin to scan a page for issues, fix three common problems in the Block Editor, then test the page using only a keyboard. No prior accessibility knowledge required. (60 minutes, Beginner)\n\n\n\nContent Creation: Participants work through the full content lifecycle in WordPress — structuring posts with blocks, managing images accessibly, organizing with categories and tags, scheduling, and recovering from mistakes using revisions. (60 minutes, Beginner)\n\n\n\nDebugging for Site Owners: Participants learn a repeatable, tool-backed approach to diagnosing and fixing the most common WordPress problems, without needing FTP access, server knowledge, or a developer on call. (60 minutes, Beginner–Intermediate)\n\n\n\nDebugging for Developers: Participants work hands-on with four complementary debugging tools: WP_DEBUG, Query Monitor, browser DevTools, and Xdebug, and learn to match the right tool to each type of problem. (60 minutes, Developer)\n\n\n\neCommerce with WooCommerce: Participants learn about various WordPress eCommerce offerings in the ecosystem and configure WooCommerce using the setup wizard, add their first product, and complete a test purchase from store to confirmation page. (60 minutes, Beginner–Intermediate)\n\n\n\nManaging Your WordPress Site with AI: Participants use Claude Desktop and the WordPress MCP Adapter to manage a local WordPress site entirely through natural language conversation. Note: this kit requires a local WordPress environment and Node.js 22+. (80 minutes, Beginner–Intermediate)\n\n\n\nSEO Foundations: Participants audit the SEO features built into WordPress core, evaluate whether their site needs an SEO plugin, and configure the essentials using RankMath in WordPress Playground. (60 minutes, Beginner–Intermediate)\n\n\n\nUsing AI in Your WordPress Dashboard: Participants set up the WordPress AI plugin, connect it to a free AI provider, and use it to draft, revise, and summarize content without leaving the editor. (60 minutes, Beginner–Intermediate)\n\n\n\nWordPress Playground: Participants explore WordPress Playground for safe testing, version testing, and environment sharing — and leave with a shareable Playground link they built themselves. (60 minutes, All levels)\n\n\n\nWordPress Security Essentials: Participants audit a WordPress site’s security posture, apply essential hardening steps, and learn what to do when something goes wrong. (60 minutes, Beginner)\n\n\n\n\nHow to use a kit\n\n\n\n

Visit learn.wordpress.org/activity-library, choose a kit, and download the zip. Each kit page includes an overview of the activity, a preview of the facilitator guide and slide deck, and a download button for the full kit. The facilitator guide includes everything you need to run the session: learning objectives, setup notes, step-by-step participant activities, facilitator tips, and debrief questions.

\n\n\n\n

You do not need to be a WordPress expert to facilitate these sessions. The kits are designed to be used by anyone interested in teaching and learning about WordPress.

\n\n\n\nHelp us build and maintain the library\n\n\n\n

We have eleven kits live and we want more. Here’s how you can get involved:

\n\n\n\n

Facilitate a kit at your next event. Download one, run it at your local meetup, and tell us how it goes through our feedback form. Post in #community-team or #training on Making WordPress Slack with what you tried and what landed.

\n\n\n\n

Create a new kit. The Training Team has published a step-by-step handbook guide covering everything from topic selection to publishing on Learn WordPress. You can create a kit using the AI prompt package (compatible with Claude, Gemini, ChatGPT, and others) or the Claude Cowork plugin — both are available in the WordPress/Learn GitHub repository.

\n\n\n\n

Flag something that needs updating. Notice a broken step, an outdated plugin version, or a path that has changed since a kit was published? Post in #training with what you found. Keeping the kits current is an ongoing team effort.

\n\n\n\n

Questions? Reach out in #community-team or #training on Making WordPress Slack.

\n\n\n\nKudos\n\n\n\n

Thank you to the peer reviewers who helped shape our first kits: @mohkatz @rashunda @mayankmajeji @akshayar @rianrietveld @alh0319 @nilovelez @ekamran

\n\n\n\n

Thank you to our Meta team folks who helped get the Activity Library live on the Learn WordPress website by reviewing, providing guidance, and merging: @obenland @adamwood @paulkevan @dd32

\n\n\n\n

Thank you to the Polyglots who helped with translating our feedback form: @francescodicandia @fierevere @masino1967 @jensratzel

\n\n\n\n

Did I miss you? It wasn’t intentional! Please send me a ping so I can ensure you’re noted <3

", "id": 17217830, "pubDate": "Wed, 12 Aug 2026 02:49:02 GMT", "whenReceived": "Wed, 12 Aug 2026 03:32:08 GMT", "whenUpdated": "Wed, 12 Aug 2026 03:32:08 GMT", "likes": [], "metadata": { "wpPostId": 90286, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Wed, 12 Aug 2026 03:31:46 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69579", "title": "Agenda: Weekly Polyglots Chat – August 12, 2026 (13:00 UTC)", "link": "https://make.wordpress.org/polyglots/2026/08/12/agenda-weekly-polyglots-chat-august-12-2026-1300-utc/", "description": "

This meeting will be held by text chat at Wednesday, August 12, 2026, 13:00 GMT in the #polyglots channel in the Making WordPress Slack.

\n\n\n\n\nWelcome\n\n\n\nWeekly Locale Stats\n\n\n\nRelease\n\nWordPress 7.0.3 release\n\n\n\n\n\nHelp & Feedback Wanted\n\nWordPress 7.0.3 has been released\n\n\n\n\n\nFYI:\n\nOne year of working on documentation about accessibility for WordPress\n\n\n\nHow to Bring Your Community to Make WordPress Slack\n\n\n\n\n\nOpen floor / Achievement\n\n\n\n\n

If you have any additions to the agenda, please share them in the comments.

\n

#meeting-agenda, #polyglots, #polyglots-meeting, #weekly-meetings

", "id": 17217829, "pubDate": "Wed, 12 Aug 2026 02:46:07 GMT", "whenReceived": "Wed, 12 Aug 2026 03:31:46 GMT", "whenUpdated": "Wed, 12 Aug 2026 03:31:46 GMT", "likes": [], "metadata": { "wpPostId": 69579, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69569", "title": "PTE Request for Rapls Passkey", "link": "https://make.wordpress.org/polyglots/2026/08/12/pte-request-for-rapls-passkey/", "description": "

I’ve suggested translations for this plugin and would like to have them
\nreviewed. I’d also like to become a PTE. I confirm that I’ve read the style
\nguide and/or glossary for the Japanese locale.

\n

I am the plugin author.

\n

Name: Rapls Passkey

\n

URL: https://wordpress.org/plugins/rapls-passkey/

\n\n #ja (@tobifjellner)\n\n\n

#editor-requests

", "id": 17216726, "pubDate": "Wed, 12 Aug 2026 01:27:35 GMT", "whenReceived": "Wed, 12 Aug 2026 01:48:13 GMT", "whenUpdated": "Wed, 12 Aug 2026 08:41:16 GMT", "likes": [], "metadata": { "wpPostId": 69569, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69551", "title": "PTE Request for Vemoro SocialFeed", "link": "https://make.wordpress.org/polyglots/2026/08/11/pte-request-for-vemoro-socialfeed/", "description": "

Hello Polyglots,

\n

I am the plugin author for Vemoro SocialFeed and would like to manage the German translations for this plugin.

\n

Please add the following WordPress.org user as Project Translation Editor:

\n\nhttps://wordpress.org/plugins/vemoro-socialfeed/\n\n\n\n #de_DE – @vemoro (@tobifjellner)\n\n\n

Thank you!

\n

#editor-requests

", "id": 17211691, "pubDate": "Tue, 11 Aug 2026 19:33:20 GMT", "whenReceived": "Tue, 11 Aug 2026 20:37:48 GMT", "whenUpdated": "Tue, 11 Aug 2026 22:21:11 GMT", "likes": [], "metadata": { "wpPostId": 69551, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69520", "title": "PTE Request for Noniko Daily Meditation Companion", "link": "https://make.wordpress.org/polyglots/2026/08/11/pte-request-for-noniko-daily-meditation-companion/", "description": "

Hello Polyglots team,

\n

I am the plugin author for **Noniko Daily Meditation Companion** and I would like to request Project Translation Editor (PTE) access for the Polish locale.

\n

Plugin:

\n\nhttps://wordpress.org/plugins/noniko-daily-meditation-companion/\n\n\n

Translation project:

\n\nhttps://translate.wordpress.org/projects/wp-plugins/noniko-daily-meditation-companion/\n\n\n

Locale:

\n\n #pl_PL – @noniko9901 (@tobifjellner)\n\n\n

I have prepared the Polish translations for my plugin and would like to be able to translate and approve them for the Polish locale.

\n

Thank you for reviewing my request!

\n

#editor-requests

", "id": 17209024, "pubDate": "Tue, 11 Aug 2026 18:12:34 GMT", "whenReceived": "Tue, 11 Aug 2026 18:53:36 GMT", "whenUpdated": "Tue, 11 Aug 2026 18:53:36 GMT", "likes": [], "metadata": { "wpPostId": 69520, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed/", "whenReceived": "Tue, 11 Aug 2026 18:51:34 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed/", "guid": "https://make.wordpress.org/core/?p=125441", "title": "Performance Chat Summary: 11 August 2026", "link": "https://make.wordpress.org/core/2026/08/11/performance-chat-summary-11-august-2026/", "description": "

The full chat log is available beginning here on Slack.

\n\n\n\nWordPress Performance Trac tickets\n\n\n\n\n@b1ink0 asked whether there was anything the team would like to focus on for the WordPress 7.2 release, referencing the performance-focused Core Trac tickets. \n\n@westonruter said he would love to get script/style concatenation ripped out in favor of using preloads, which would be a big improvement to Core, especially from a tech debt perspective.\n\n\n\n\n\n\nPerformance Lab Plugin (and other performance plugins)\n\n\n\n\n@westonruter shared that he pushed out a security fix for Optimization Detective the previous week. That process brought to light a deficiency in the deploy script where it could inadvertently try to publish a release for an older version, so he opened PR #2620.\n\n\n\n\nOpen Floor\n\n\n\n\n@westonruter asked whether anyone else was planning to be at Contributor Day at WCUS on Sunday.\n\n\n\n\n

Our next chat will be held on Tuesday, August 25, 2026 at 16:00 UTC in the #core-performance channel in Slack.

\n

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

", "id": 17208959, "pubDate": "Tue, 11 Aug 2026 17:04:25 GMT", "whenReceived": "Tue, 11 Aug 2026 18:51:34 GMT", "whenUpdated": "Tue, 11 Aug 2026 18:51:34 GMT", "likes": [], "metadata": { "wpPostId": 125441, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 11 Aug 2026 17:21:41 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69507", "title": "PTE Request for Findit Order Sync for Bol.com", "link": "https://make.wordpress.org/polyglots/2026/08/11/pte-request-for-findit-order-sync-for-bol-com/", "description": "

I am the plugin author. Please add my WordPress.org user @finditnl as translation editor for this plugin:

\n\nhttps://wordpress.org/plugins/findit-order-sync-for-bol-com/\n\n\n\n #nl_NL – @finditnl\n\n\n

#editor-requests

", "id": 17205573, "pubDate": "Tue, 11 Aug 2026 16:57:29 GMT", "whenReceived": "Tue, 11 Aug 2026 17:21:41 GMT", "whenUpdated": "Tue, 11 Aug 2026 17:21:41 GMT", "likes": [], "metadata": { "wpPostId": 69507, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69504", "title": "Hi", "link": "https://make.wordpress.org/polyglots/2026/08/11/hi-133/", "description": "

Can I (pbearne) be added as an editor to en_GB so I can help keep it up along with en_CA

\n\n #en_GB \n\n\n

Paul

\n

#editor-requests

", "id": 17205574, "pubDate": "Tue, 11 Aug 2026 16:57:19 GMT", "whenReceived": "Tue, 11 Aug 2026 17:21:41 GMT", "whenUpdated": "Tue, 11 Aug 2026 17:21:41 GMT", "likes": [], "metadata": { "wpPostId": 69504, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69497", "title": "PTE Request for gRDV…", "link": "https://make.wordpress.org/polyglots/2026/08/11/pte-request-for-grdv/", "description": "

PTE Request for gRDV Messages

\n

I am the author of the gRDV Messages plugin:

\n\nhttps://wordpress.org/plugins/grdv-messages/\n\n\n

The plugin currently uses German source strings. I maintain the German identity translation as well as the English translations.

\n

Please add the following WordPress.org user as Project Translation Editor for this plugin:

\n\n #de_DE – @grdv (@tobifjellner)\n\n #en_GB – @grdv\n\n\n

I am a native German speaker and will maintain both translations according to the respective locale glossaries and style guides.

\n

Thank you!

\n

#editor-requests

", "id": 17205576, "pubDate": "Tue, 11 Aug 2026 16:56:58 GMT", "whenReceived": "Tue, 11 Aug 2026 17:21:41 GMT", "whenUpdated": "Tue, 11 Aug 2026 22:21:11 GMT", "likes": [], "metadata": { "wpPostId": 69497, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69509", "title": "Translation Validation Request for BotBlocker Security – Firewall & Bot Protection", "link": "https://make.wordpress.org/polyglots/2026/08/11/translation-validation-request-for-botblocker-security-firewall-bot-protection/", "description": "

Hi Polyglots team,

\n

I have submitted new translation strings for the plugin BotBlocker Security – Firewall & Bot Protection and they are currently waiting for review. Could the respective General Translation Editors (GTEs) please check and validate them?

\n\nPlugin URL: https://wordpress.org/plugins/botblocker-security/\n\nTranslation Project URL: https://translate.wordpress.org/projects/wp-plugins/botblocker-security/\n\n\n

Here are the locales with pending strings:

\n

#fr_FR
\n#pl_PL
\n#ar
\n#he_IL
\n#it_IT
\n#ja
\n#ko_KR
\n#pt_BR
\n#tr_TR
\n#zh_CN

\n

Thank you very much for your time and help in making the plugin available in your languages!

\n

#editor-requests

", "id": 17205577, "pubDate": "Tue, 11 Aug 2026 16:36:35 GMT", "whenReceived": "Tue, 11 Aug 2026 17:21:41 GMT", "whenUpdated": "Tue, 11 Aug 2026 17:21:41 GMT", "likes": [], "metadata": { "wpPostId": 69509, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69495", "title": "GTE Request for Persian (fa_IR) – mralidoosti", "link": "https://make.wordpress.org/polyglots/2026/08/11/gte-request-for-persian-fa_ir-mralidoosti/", "description": "GTE Request for Persian (`fa_IR`)\n\n\n

Hello Polyglots team,

\n

I would like to request General Translation Editor (GTE) access for the Persian (`fa_IR`) locale.

\n

My WordPress.org username is mralidoosti:

\n

https://profiles.wordpress.org/mralidoosti/

\n

I have been contributing to the WordPress ecosystem for several years, with a particular focus on WordPress development and localization. I have been contributing translations to the Persian locale and currently have PTE access for WP Bottom Menu.

\n

I have also contributed translations across several WordPress projects, including projects such as:

\n\nBuddyPress\n\nRank Math\n\nTutor LMS\n\nWP Bottom Menu\n\nand other WordPress plugins\n\n\n

I have an established history of Persian translation contributions and would like to take a more active role in maintaining and improving the quality of the `fa_IR` locale.

\n

I have reviewed the Persian translation guidelines, glossary, and the general expectations for WordPress translators. If granted GTE access, my intention would be to:

\n\nReview and approve high-quality Persian translations across WordPress projects.\n\nHelp maintain consistency with the Persian glossary and translation style.\n\nReview contributions from other translators and provide constructive feedback when necessary.\n\nHelp maintain the quality and consistency of existing Persian translations.\n\nSupport new Persian translation contributors.\n\nContribute to the long-term maintenance of the `fa_IR` locale.\n\n\n

I understand that GTE access carries responsibility for maintaining translation quality across the locale, rather than simply approving my own contributions. I am prepared to take on that responsibility and actively participate in the Persian translation team.

\n

I would appreciate it if the `fa_IR` team could review my request and consider granting me GTE access.

\n\n #fa_IR \n\n\n

Thank you for your time and for supporting the Persian WordPress community.

\n

Best regards,
\nMr. Alidoosti
\nWordPress.org username: mralidoosti

\n

#editor_requests

", "id": 17199193, "pubDate": "Tue, 11 Aug 2026 12:41:15 GMT", "whenReceived": "Tue, 11 Aug 2026 13:05:53 GMT", "whenUpdated": "Tue, 11 Aug 2026 17:21:41 GMT", "likes": [], "metadata": { "wpPostId": 69495, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/themes/feed/", "whenReceived": "Tue, 11 Aug 2026 07:39:49 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/themes/feed/", "guid": "https://make.wordpress.org/themes/?p=25136", "title": "Themes Team Meeting Agendas for August 11, 2026", "link": "https://make.wordpress.org/themes/2026/08/11/themes-team-meeting-agendas-for-august-11-2026/", "description": "

The Themes Team holds meetings on the second and fourth Tuesdays every month. For this month, this is the first meeting and is set to take place on 11 August.

\n\n\n\n

Meeting Details:

\n\n\n\n\nDate and Time: Tuesday, August 11 2026, 15:00 UTC\n\n\n\nChannel: #themes\n\n\n\n\n

(You need WordPress Slack and you need an account to participate. View here how to make a WordPress Slack account.)

\n\n\n\n

Alongside the scheduled agendas, we dedicate time at the end of each meeting for an open floor session, where you are invited to ask questions or share any themes-related updates.

\n\n\n\n

We strongly encourage all members and anyone interested in the themes to join in. If there are specific topics you’d like to see included in the agenda, please don’t hesitate to add them in the comment section below.

\n\n\n\nMeeting Agendas\n\n\n\n\nWeekly updates\n\n\n\nOpen Floor\n\n\n\n\n

I am looking forward to seeing you at the meeting!

\n

#agenda, #themes-team

", "id": 17193750, "pubDate": "Tue, 11 Aug 2026 07:17:35 GMT", "whenReceived": "Tue, 11 Aug 2026 07:39:49 GMT", "whenUpdated": "Tue, 11 Aug 2026 07:39:49 GMT", "likes": [], "metadata": { "wpPostId": 25136, "wpSiteId": 31759950 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Tue, 11 Aug 2026 05:51:08 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125434", "title": "Dev Chat Agenda – August 11, 2026", "link": "https://make.wordpress.org/core/2026/08/11/dev-chat-agenda-aug-11-2026/", "description": "

The next WordPress Developers Chat will take place on Tuesday, August 11, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

\n\n\n\n

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

\n\n\n\n

The various curated agenda sections below refer to additional items. If you have ticket requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

\n\n\n\nAnnouncements \n\n\n\n

Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

\n\n\n\n7.1\n\n\n\n\n7.1 RC1 was released Wed August 5th.\n\n\n\nA silent RC2 security release was released on August 6th.\n\n\n\nRC3 scheduled for Wednesday, August 12th.\n\n\n\nWordPress 7.1 Field Guide\n\n\n\n7.1 Release Candidate phase\n\n\n\nAs of Aug 10th, 7.1 is branched. Committers: Trunk is open for 7.2 and the 7.1 branch requires double sign off.\n\n\n\n\n\n\n\n\nGeneral\n\n\n\n\n7.0.3 Security release \n\n\n\nWhat’s new in Gutenberg 23.7 – Aug 5th.\n\n\n\nWCUS 2026 is next week!! (and WordPress 7.1 is slated for release live at WCUS on August 19th.)\n\n\n\n\n\nDiscussions \n\n\n\n

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

\n\n\n\n\n@wildworks is requesting assistance with PR #12795 and PR #12932 \n\n\n\n\n\n\nOpen floor  \n\n\n\n

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

\n\n

#7-1, #agenda, #core, #dev-chat

", "id": 17192688, "pubDate": "Tue, 11 Aug 2026 04:23:22 GMT", "whenReceived": "Tue, 11 Aug 2026 05:51:08 GMT", "whenUpdated": "Tue, 11 Aug 2026 05:51:08 GMT", "likes": [], "metadata": { "wpPostId": 125434, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://developer.wordpress.org/news/feed/", "whenReceived": "Mon, 10 Aug 2026 21:34:11 GMT", "items": [ { "feedUrl": "https://developer.wordpress.org/news/feed/", "guid": "https://developer.wordpress.org/news/?p=6352", "title": "What’s new for developers? (August 2026)", "link": "https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/", "description": "

August is a big month for WordPress. Version 7.1 is scheduled to land on August 19, and it’s arriving on the last day of WordCamp US in Phoenix, which runs August 16–19. Release day during the flagship event of the year is a nice bit of scheduling, and if you’re going to be there, you’ll get to watch it happen live.

\n\n\n\n

Both RC1 and RC2 have shipped in the last week. That means the feature set is locked and the Field Guide is out.

\n\n\n\n

Two security releases also landed in the past month. WordPress 7.0.2 arrived on July 17 to address one critical and one high severity issue. The severity was high enough that WordPress.org enabled forced updates for affected versions. Then WordPress 7.0.3 shipped on August 6 with a dozen more fixes. If any site you maintain somehow missed both auto-updates, go handle that before you read the rest of this post.

\n\n\n\n

With nine days left before 7.1 ships, this is your last comfortable window to test your plugins and themes against it. Let’s get into what’s new.

\n\n\n\n

As always, you can test the latest by running WordPress trunk along with the newest Gutenberg release, or by spinning up a Playground instance with no setup at all.

\n\n\n\n\n

Table of Contents

\n\n\nHighlightsThe 7.1 Field Guide is outResponsive block styles land in CorePseudo and custom style statesThe SVG Icon API now publicThe post editor is always iframedPlugins and toolsList table row headers have movedThe Abilities API updatesDesign System theming for admin interfacesComponents drop the 40px opt-in for goodAccessible tooltips arrive in the adminBlock API and editor extensibilityFiltering Site Editor screensWidget primitivesNotes and collaborationOther Core changes worth a lookReact 19 is punted againWordPress Coding StandardsThemesThree new design toolsThe Navigation block stops propagating font sizeGlobal Styles values show up in the inspectorPlaylist and Tabs are stableOther theme-facing changesPlaygroundA new interface, and a handbook to go with itProgrammatic site managementResourcesDeveloper BlogDeveloper notes\n\n\n\nHighlights\n\n\n\nThe 7.1 Field Guide is out\n\n\n\n

The WordPress 7.1 Field Guide is published, and it is the single most important thing to read this month. It collects every release dev note in one place: Media, Accessibility, the Abilities API, Global Styles, the SVG Icon API, DataViews and View Config, the Editor, the Design System, the persistent admin bar, and external libraries.

\n\n\n\n

The section on what didn’t make the release is equally useful. Real-time collaboration is not enabled in 7.1. The plan to hide the Classic block from the inserter was reverted. React 19 has been punted again. The On This Day dashboard widget didn’t land, and the Guidelines/Knowledge merge proposal continues to evolve. If you’ve been tracking any of those in these previous roundups, that’s where they stand.

\n\n\n\nResponsive block styles land in Core\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n

Responsive style states have been a work in progress in these roundups since spring. In WordPress 7.1, they ship.

\n\n\n\n

Styles can now be defined for tablet and mobile viewports, both in Global Styles per block type and on individual block instances. In theme.json, they’re nested under @mobile and @tablet keys:

\n\n\n\n\"styles\": {\n\t\"blocks\": {\n\t\t\"core/group\": {\n\t\t\t\"spacing\": {\n\t\t\t\t\"padding\": { \"top\": \"3rem\" }\n\t\t\t},\n\t\t\t\"@mobile\": {\n\t\t\t\t\"spacing\": {\n\t\t\t\t\t\"padding\": { \"top\": \"1rem\" }\n\t\t\t\t}\n\t\t\t}\n\t\t}\n\t}\n}\n\n\n\n

There is no @desktop key, and that’s on purpose. The block’s default style is the desktop style, and it continues to apply at every viewport for any property you don’t override.

\n\n\n\n

The part you might’ve been waiting for: themes can now configure the breakpoints themselves via a new top-level settings.viewport property in theme.json. The defaults are 480px for mobile and 782px for tablet. The values must be non-negative lengths in px, em, or rem. CSS functions, percentages, and unitless values are ignored. And if the tablet value is equal to or lower than the mobile value, only mobile is used. It’s a top-level setting, so you can’t configure it per block type.

\n\n\n\n

Blocks that use standard block supports get responsive styles for free. That covers typography, color, background, border, dimensions, spacing, and layout. Blocks with custom style controls do not. That’s the line to check your own blocks against.

\n\n\n\n

You can also turn off responsive editing for users with a quick filter:

\n\n\n\nadd_filter( 'block_editor_settings_all', 'example_disable_responsive_editing' );\n\nfunction example_disable_responsive_editing( $settings ) {\n\t$settings['responsiveEditingEnabled'] = false;\n\treturn $settings;\n}\n\n\n\n

Note that responsive styles support means changing block-level CSS in Core. Preset utility selectors are now wrapped in :where().

\n\n\n\nPseudo and custom style states\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n

Alongside responsive styles, another oft-requested theme dev feature has landed: support for pseudo-state styling. You can define :hover, :focus, :focus-visible, and :active in theme.json and via the editor. For now, this is limited to the Button and Navigation Link blocks.

\n\n\n\n

Here’s an example of styling :hover for a Button block (with responsive styling!):

\n\n\n\n\"core/button\": {\n\t\":hover\": {\n\t\t\"color\": { \"background\": \"var:preset|color|contrast\" }\n\t},\n\t\"@mobile\": {\n\t\t\":hover\": {\n\t\t\t\"color\": { \"background\": \"var:preset|color|contrast-2\" }\n\t\t}\n\t}\n}\n\n\n\n

There’s also an early custom states feature, currently theme.json-only with no user-facing UI, used by the Navigation Link block to style the current menu item via a -current property. Custom states use a - prefix and generate CSS that targets a class name declared through a block’s block.json selectors.states property. Worth knowing about now, even though it’s narrow today.

\n\n\n\n

Like responsive editing, this has its own opt-out: the blockStatesEditingEnabled editor setting.

\n\n\n\nThe SVG Icon API now public\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n

WordPress 7.0 shipped a bundled set of SVG icons for the editor and the Icon block. In 7.1, it becomes a proper public API that you can register into.

\n\n\n\n

Every icon belongs to a collection, and the collection name becomes a namespace prefix, which is what keeps my-plugin/star from colliding with core/star. Register the collection with wp_register_icon_collection(), then add icons with wp_register_icon(). And wp_get_icon() renders an icon anywhere in PHP with optional size, class, and label arguments.

\n\n\n\n

There are two limitations to plan around:

\n\n\n\n\nRegistered SVGs are sanitized through wp_kses against a deliberately conservative allowlist: only <svg>, <path>, and <polygon>. Work to broaden the allowlist is underway.\n\n\n\nfill is only allowed on the shapes, not the outer <svg>, and wp_get_icon() doesn’t add one. Inside the Icon block this doesn’t matter, because the block stylesheet sets it to the current color. But a standalone wp_get_icon() call renders in the SVG’s own fill (black), not the surrounding text color. Recommended: supply your own CSS against the class you pass in.\n\n\n\n\nThe post editor is always iframed\n\n\n\n

This one has been coming since the template editor moved into an iframe in WordPress 5.8. In 7.1, the post editor takes the final step: it is always iframed, regardless of theme type, the block API versions of registered blocks, or the block API versions of blocks in the content. Sites that register legacy meta boxes are included.

\n\n\n\n

In 7.0, the decision was made per post based on what blocks were inserted, which meant the editor could switch between iframed and non-iframed modes depending on content. That conditional behavior is gone.

\n\n\n\n

Most blocks already work without changes. The issues that do surface almost always trace back to one root cause: the iframe has its own document and window, separate from the admin page where editor scripts run. Code reaching for the global document or window to touch the canvas is looking at the wrong document. The usual fixes are getting the canvas document from an element inside it via ownerDocument and defaultView, and using useRefEffect to attach and clean up listeners on canvas elements. The handbook’s technical considerations for the iframe editor covers the full list.

\n\n\n\nPlugins and tools\n\n\n\nList table row headers have moved\n\n\n\n

This is the change most likely to quietly break something you maintain. In changeset 62838, the primary th scope=\"row\" in post list tables moved from the checkbox column to the title column. The checkbox cell is now a td, the title cell is now a th carrying an aria-label with the post title, and collapsed cells in the responsive view use flex layout.

\n\n\n\n

It’s a real accessibility win: screen readers now identify each row by the post rather than by a checkbox that may not even be present. But this is markup that has been largely stable since 2010, and plenty of extensions depend on it implicitly. Check any CSS or JavaScript selecting th.check-column, or expecting row actions and post titles inside a td.

\n\n\n\nThe Abilities API updates\n\n\n\n

The Abilities API shipped as infrastructure in WordPress 6.9. In 7.1 it picks up nearly everything you’d need to actually build against it: a filterable execution lifecycle, custom validation, and a shared discovery pipeline. If you’re building AI integrations, automation tooling, or protocol adapters, this is the release where the API stops being a foundation and starts being a toolkit.

\n\n\n\n

Five dev notes cover it, and they’re worth reading in this order:

\n\n\n\n\nNew execution lifecycle filters\n\n\n\nAbilities API improvements\n\n\n\nFiltering registered abilities with wp_get_abilities()\n\n\n\nA unified public exposure flag\n\n\n\nJSON Schema preparation for client compatibility\n\n\n\n\nDesign System theming for admin interfaces\n\n\n\n

WordPress 7.1 ships foundational support for theming admin interface components, covering color, roundness, and cursor styles. Note that this has nothing to do with the front end. “Theming” in this instance is directly related to the admin.

\n\n\n\n

The wp-theme stylesheet provides a full set of semantic design tokens as CSS custom properties, so you can reference them instead of hardcoding values. The wp-theme script handle provides a ThemeProvider React component that wraps a section of a page and overrides those token values. Give it a pair of seed colors and it generates a harmonious ramp for you. 

\n\n\n\n

For plugin authors who’ve wanted their admin screens to carry their own brand while still looking like they belong in WordPress, this is the first real opening. The token reference lists what’s available.

\n\n\n\nComponents drop the 40px opt-in for good\n\n\n\n

The __next40pxDefaultSize prop has finished its journey. It was introduced in 6.7, soft-deprecated in 6.8, and as of 7.1 it’s a no-op. 

\n\n\n\n

Form controls render at 40px unconditionally, and passing __next40pxDefaultSize={false} no longer opts back out to 36px. Remove the prop from your usage; there’s no replacement. If you were passing size=\"__unstable-large\" only to get the taller control, remove that too. On BorderBoxControl, BorderControl, FontSizePicker, and ToggleGroupControl, the size prop is deprecated as well.

\n\n\n\nAccessible tooltips arrive in the admin\n\n\n\n

Tooltips have existed in the editor for a while, but not in the rest of wp-admin. WordPress 7.1 adds wp_get_tooltip() and wp_get_toggletip() to close that gap. The first gives a visible accessible name to icon-only controls; the second adds a triggerable button for extended help text. Core uses them on post meta box controls and the login screen’s “Remember Me” checkbox respectively.

\n\n\n\n

The CSS loads globally, but the JavaScript only loads where Core uses it. Elsewhere, enqueue wp-tooltip for both.

\n\n\n\nBlock API and editor extensibility\n\n\n\n

Several miscellaneous items are worth looking at that could affect your code:

\n\n\n\n\nBlock transforms can now target a specific variation via variationName, and switchToBlockType() accepts a variation as a third argument.\n\n\n\n__experimentalCloneSanitizedBlock and __experimentalSanitizeBlockAttributes are stabilized. The experimental names still work but now log deprecations.\n\n\n\nNon-paginated entities now return all records. If you were getting a truncated list of ten back from getEntityRecords(), you’ll now get everything, so check anywhere you render without your own limit.\n\n\n\nTemplate parts can opt out of content-only editing with the new disableContentOnlyForTemplateParts setting.\n\n\n\n\n

Elsewhere in Gutenberg 23.6 and 23.7: block bindings share context assembly between call sites, PHP-only blocks forward the current post ID to server render, the inspector controls styles slot moved back to its previous position, and PluginPostStatusInfo is now available in the DataForm post summary. The Interactivity API also refactored its directives into self-registering modules.

\n\n\n\nFiltering Site Editor screens\n\n\n\n

Four new filters let you configure the DataViews and DataForm components powering the Pages, Templates, Parts, and Patterns screens: 

\n\n\n\n\nget_entity_view_config_posttype_page\n\n\n\nget_entity_view_config_posttype_wp_template\n\n\n\nget_entity_view_config_posttype_wp_template_part\n\n\n\nget_entity_view_config_posttype_wp_block\n\n\n\n\n

Each can set default_view, default_layouts, view_list, and form, so you can control default layout and sort order, which layouts users can pick, the preconfigured views in the sidebar, and the Quick Edit form.

\n\n\n\n

Callbacks receive a config object with methods for merging patches, and they must return the container. The dev note has a working example, and the mechanism is designed to grow to other entities. On the Gutenberg side, view config also gained version handling and stricter merge semantics.

\n\n\n\nWidget primitives\n\n\n\n

Work on the widget dashboard continued through both Gutenberg releases, mostly in the direction of typed, declarative widget definitions:

\n\n\n\n\nWidget primitives now ship as a script module.\n\n\n\nNew WidgetAttributeField for typed attribute schemas, backed by a field type registry.\n\n\n\nThe widget category is exposed through the build pipeline and REST API.\n\n\n\nNew declarative help metadata field and relevance attribute.\n\n\n\ntitle, description, and keywords are translated server-side.\n\n\n\n\n

Dashboard widgets also picked up action href sanitization and help link sanitization.

\n\n\n\nNotes and collaboration\n\n\n\n

Real-time collaboration isn’t in 7.1, but Notes picked up two features since Beta 1: email notifications for @mentions and shareable revision links. Notes are also now excluded from comment feed queries, which relates to a disclosure issue patched in 7.0.3.

\n\n\n\nOther Core changes worth a look\n\n\n\n\nThe notify_post_author filter now has the final say. Approval status is folded into the default, so a __return_true callback will now also send mail for comments in moderation, spam, or trash.\n\n\n\nThe toolbar now persists across editor screens. If you extend it, test how your items behave during client-side navigation.\n\n\n\nSpeculative loading can be configured via environment variables and constants.\n\n\n\n_doing_it_wrong() messages in WP_Block_Type_Registry::register() gained context.\n\n\n\nget_file_data() now recognizes headers prefixed by a <? tag.\n\n\n\nTemplates gained a date field, and KSES allows autofocus on dialog elements.\n\n\n\n\nReact 19 is punted again\n\n\n\n

React 19 won’t ship in 7.1. It was briefly enabled in Gutenberg, then reverted after unexpected incompatibilities surfaced in how old and new versions of React interact and in how plugins consume React. WordPress 7.1 stays on 18.3.

\n\n\n\n

Testing hasn’t stopped, though. 

\n\n\n\n

Gutenberg 23.4 and later ship an experimental flag under Settings → Gutenberg that swaps in React 19 at runtime. The two failure modes to look for are bundling react/jsx-runtime directly instead of using the externalized script WordPress provides, and relying on React features removed in 19 like string refs or default props on function components. There’s also work underway to catch these automatically in Plugin Check.

\n\n\n\nWordPress Coding Standards\n\n\n\n

Two WordPressCS releases landed this month. 3.4.0 is a normal feature release, and 3.4.1 contains a security fix, so upgrade sooner rather than later.

\n\n\n\nThemes\n\n\n\nThree new design tools\n\n\n\n

WordPress 7.1 adds two block supports and one Global Styles property, and the gradient one solves a problem theme authors have been working around for years.

\n\n\n\n

background.gradient is a separate support from the existing color.gradient, and the difference is where the value lands in CSS. The old support renders through the background shorthand, which resets every background property including background-image, so a block could show a gradient or an image but never both. The new support renders through the background-image longhand instead, letting the style engine output the gradient and the image as comma-separated values in a single declaration. Opt in through block.json:

\n\n\n\n{\n\t\"supports\": {\n\t\t\"background\": {\n\t\t\t\"backgroundImage\": true,\n\t\t\t\"gradient\": true,\n\t\t\t\"__experimentalDefaultControls\": {\n\t\t\t\t\"backgroundImage\": true,\n\t\t\t\t\"gradient\": true\n\t\t\t}\n\t\t}\n\t}\n}\n\n\n\n

Core opts Group, Accordion, Pullquote, Post Content, and Quote in for 7.1. Values live at style.background.gradient and can be set in theme.json under the background styles group, at the root or per block. safecss_filter_attr() was updated to permit the combined gradient plus url() value, so no extra filtering is needed on your end.

\n\n\n\n

dimensions.minWidth follows the same pattern as minHeight, applies as CSS min-width, and picks up dimensionSizes presets when a theme provides them. Note that it’s hidden by default in the block inspector unless a block opts in through __experimentalDefaultControls, but shown by default in Global Styles. And text-shadow is now supported in Global Styles.

\n\n\n\nThe Navigation block stops propagating font size\n\n\n\n

The Navigation block no longer forces its font-size configuration onto the markup of core/navigation-link, core/navigation-submenu, core/page-list, and core/home-link. The old behavior compounded badly with relative units, multiplying 1.5em into 2.25em into 3.375em down a nested dropdown, and it caused the editor canvas and the front end to disagree about typography. The block now relies on standard CSS text inheritance.

\n\n\n\n

If your theme targets has-{slug}-font-size on nav items directly, the dev note includes a filter that restores the legacy classes on child blocks. The original discussion is in #76416.

\n\n\n\nGlobal Styles values show up in the inspector\n\n\n\n

Block inspector controls now reflect inherited Global Styles values rather than appearing empty when a value is coming from theme.json, with per-level heading element styles and link element styles for blocks that are links resolving correctly. The user-facing inheritance UI is behind a Gutenberg experiment for now, so this is one to watch rather than build against.

\n\n\n\n

Two related fixes landed in the same window: presets are selected by slug so two gradients sharing a value keep their identity, and the same problem is fixed for color presets sharing a hex.

\n\n\n\nPlaylist and Tabs are stable\n\n\n\n

Both blocks have been experimental for a while and have appeared in these roundups in that state. In Gutenberg 23.6, the Playlist blocks and the Tabs block were stabilized, and Tabs also picked up toolbar buttons for reordering tabs. Both are on the 7.1 roadmap. If you held off on styling them while the markup was still moving, now’s the time.

\n\n\n\nOther theme-facing changes\n\n\n\n\nThemes that use theme.json can now opt out of block visibility.\n\n\n\nCustom CSS is output after the block library styles, and Additional CSS no longer duplicates inside a Query Loop.\n\n\n\ncalc() expressions now accept unitless zeros.\n\n\n\nThe style engine preserves important gradient declarations, and block gap handles nested array values properly.\n\n\n\nTerm Name migrated to the text-align block support, continuing the standardization that’s been running since 7.0.\n\n\n\nLatest Posts gained layout and block spacing support.\n\n\n\nCover can now restrict which video embed providers are allowed.\n\n\n\nVideo handles a non-lowercase VIDEO tag in render_block_core_video().\n\n\n\nNavigation Link and Submenu run their post-status check without the Gutenberg plugin active, fixing a draft and deleted links regression.\n\n\n\nWP_Theme_JSON::to_ruleset() no longer coerces implicitly, and WP_Theme::get_post_templates() got faster for large themes.\n\n\n\n\nPlayground\n\n\n\nA new interface, and a handbook to go with it\n\n\n\n

WordPress Playground has had a busy month. The most visible change is a new interface, rebuilt around managing multiple sites rather than spinning up one throwaway instance at a time. Alongside it, there’s now a proper Playground Handbook.

\n\n\n\n

If you use Playground for demos, support reproductions, or testing against 7.1 RC builds, this is a good moment to kick the tires and tell them what breaks.

\n\n\n\nProgrammatic site management\n\n\n\n

The new Site Manager API lets you create, list, modify, and delete Playground sites from code rather than clicking through the UI, which opens the door to scripted test matrices and automated demo environments. Worth a look if you’ve been maintaining your own wrapper around Blueprints to do something similar.

\n\n\n\n

Two other resources landed:

\n\n\n\n\nOne Playground, three workflows covers a new version of the Playground agent skill and how guidance stays consistent across surfaces.\n\n\n\nA guide on importing content with Blueprints, which is something folks often ask about once they’ve built their first Blueprint.\n\n\n\n\n

Playground also remains the fastest way to test 7.1 without touching a server. The RC announcement links a preconfigured instance running the beta channel.

\n\n\n\nResources\n\n\n\nDeveloper Blog\n\n\n\n

Aside from the regular monthly roundup, three new posts landed on the Developer Blog in the last month:

\n\n\n\n\nOn-brand maintenance mode for WordPress Block Themes\n\n\n\nBuild your first AI-Powered WordPress plugin\n\n\n\nRethinking do_action(): Events as objects, hooks as class names\n\n\n\n\nDeveloper notes\n\n\n\n

Also, be sure to catch up on the WordPress 7.1 Dev Notes that apply to your work:

\n\n\n\n\nConsistent navigation in WordPress 7.1 with persistent toolbar\n\n\n\nClient-Side Media Processing in WordPress 7.1\n\n\n\nMedia Library infinite scrolling is now enabled by default, with a per-user opt-out\n\n\n\nText Shadow Support in Global Styles\n\n\n\nEditable blocks inside the Custom HTML block\n\n\n\nEditor components updates in WordPress 7.1\n\n\n\nRegistering and rendering SVG icons in WordPress 7.1\n\n\n\nReact 19: punted beyond WordPress 7.1, experiment in Gutenberg\n\n\n\nNew Block Support in WordPress 7.1: Background Gradient (background.gradient)\n\n\n\nNew Block Support in WordPress 7.1: Minimum Width\n\n\n\nNew execution lifecycle filters for the Abilities API in WordPress 7.1\n\n\n\njQuery UI updated to 1.14.2 in WordPress 7.1\n\n\n\nJSON Schema preparation for client compatibility in WordPress 7.1\n\n\n\nAbilities API improvements in WordPress 7.1\n\n\n\nDesign System Theming in WordPress 7.1\n\n\n\nFiltering Site Editor Screens in WordPress 7.1\n\n\n\nIframed Editor Changes in WordPress 7.1\n\n\n\nPost list tables row headers changed\n\n\n\nIntroducing name and informational tool tips in WordPress 7.1\n\n\n\nA unified public exposure flag for Abilities in WordPress 7.1\n\n\n\nMiscellaneous Editor Changes in WordPress 7.1\n\n\n\nResponsive block styles and configurable viewports in WordPress 7.1\n\n\n\nPseudo and custom style states in WordPress 7.1\n\n\n\nFiltering registered abilities with wp_get_abilities() in WordPress 7.1\n\n\n\nThe notify_post_author filter now has the final say on post author notifications\n\n\n\n\n

Props to @bph and @juanmaguitar for feedback and review on this post.

", "id": 17186636, "pubDate": "Mon, 10 Aug 2026 21:18:51 GMT", "whenReceived": "Mon, 10 Aug 2026 21:34:11 GMT", "whenUpdated": "Mon, 10 Aug 2026 21:34:11 GMT", "likes": [], "metadata": { "wpPostId": 6352, "wpSiteId": 208500394 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/training/feed/", "whenReceived": "Mon, 10 Aug 2026 21:40:17 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/training/feed/", "guid": "https://make.wordpress.org/training/?p=177240", "title": "Meeting agenda for August 11th, 2026", "link": "https://make.wordpress.org/training/2026/08/10/meeting-agenda-for-august-11th-2026/", "description": "

This week’s meeting will be held on Tuesday, August 4th, 2026, at 07:00 UTC. The meeting will be held on Slack, in the #training channel. Anyone is welcome to contribute to the meeting by commenting in Slack threads during the meeting and throughout the following days. Meeting notes will be published by the following Tuesday to incorporate these asynchronous conversations as well.

\n\n\n\n

This week’s meeting will be hosted by @rjekic.

\n\n\n\n1. Intro/Welcome\n\n\n\n

Welcome to all the new teammates who joined the Training Team this week!

\n\n\n\n2. News\n\n\n\n\nMeeting Note Takers\n\nAug 11th – @andrewssanya\n\n\n\nAug 18th – @sibokul\n\n\n\nAug 25th – @makanikaran\n\n\n\nSep 1st – @sonaliprajapati\n\n\n\n\n\nLooking for feedback\n\nWe are also planning an Office Hours session for August 22, 2026:\n\nTopic: Note-taking and publication workflow: Who does what, and how? More details are available here: https://github.com/WordPress/Learn/issues/3570\n\n\n\nWe have also reviewed several GitHub issues related to Office Hours. You can view all open Office Hours tickets and share your suggestions here: https://github.com/WordPress/Learn/issues?q=state%3Aopen%20label%3A%22Office%20Hours%22 \n\n\n\n\n\nWe have discussed starting a regular GitHub triage meeting, but this has not yet been confirmed.\n\nProposed schedule: Triage Squad GitHub triage – biweekly on Thursdays at 07:00 UTC.\n\n\n\nPlease let us know if you would be interested in joining this Slack meeting if we decide to move forward with it.\n\n\n\nWe’re actively updating the Training Team handbooks, and there’s still time to contribute. If you have any suggestions, improvements, or ideas, please share them – we’d greatly appreciate your input: https://github.com/WordPress/Learn/issues/3447. Big thank you to everyone who has shared feedback so far!\n\n\n\n\n\nOur colleague, @mebo, revived the Learning Pathway Course: Intermediate Plugin Developer Course – https://github.com/WordPress/Learn/issues/2044. She started working on course modules and lessons, and you can help her by suggesting and giving your opinion on newly created content – https://github.com/WordPress/Learn/issues/2182#issuecomment-5203614201\n\n\n\n\n\nLooking for volunteers\n\nWe need your help in finding all the content that could be updated and consolidated. We would love to have two groups of volunteers – one that will go through all the handbook content, and one that will check the courses. Please state your interest, and we will help you organize and start working on these important issues.\n\n\n\nAlso, we started working on creating thumbnails for all lessons that need them. You’re very welcome to join us and contribute to this important and creative project. Here’s the issue with details on how to work on the remaining thumbnails:
https://github.com/WordPress/Learn/issues/3428\n\n\n\nWe currently have 552 open issues. It would be most effective to divide them into smaller categories and work through them one by one.\n\nWe can start with a label that is suitable for everyone to review. We suggest this simple workflow:\n\nGoing through issues one by one\n\n\n\nIdentifying outdated or irrelevant issues\n\n\n\nSuggesting fixes or next steps\n\n\n\nAdding comments where needed (before closing or updating)\n\n\n\nWe labeled some of the issues as Good First Issues – if you want to start contributing, this is your starting point. Just go and find issues labeled as Good First Issue, particularly those that have Feedback in the issue title – help us verify them, and you will earn the Training Team Contributor badge in no time. Just follow this handbook article –https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues\n\n\n\n\n\nFor the upcoming sessions, we should divide the open issues into smaller groups and work through one category at a time. This should make the process more organised and easier for everyone to participate in.\n\nWe could begin with: [Content] Needs Translation Reviewer – https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22 – Based on feedback from our last meeting, @rfluethi suggested starting with issues in the Bug category, as these are both the highest priority and likely the easiest to address. Please review the open tickets and share any feedback or suggestions you may have.\n\n\n\n\n\nHowever, we would appreciate your suggestions on which category would be the easiest and most useful for everyone to start with. Other available categories include:\n\nIssues without a label\n\n\n\nAwaiting Triage\n\n\n\n[Content] Feedback\n\n\n\n[Type] Bug\n\n\n\n\n\nPlease share which category you think we should review first. Once selected, we can divide the issues and work through them together, one by one.\n\n\n\nLet’s work together to clean up and keep the repository well-organized\n\n\n\n\n\n\n\nUpdates from last week’s Triage Squad session\n\nWe are planning to start, so if you would be interested, then comment or join the #Training team channel on WordPress Slack\n\n\n\n\n\nOther announcements and news\n\nTraining Team Monthly update for July is published – Training Team Update – August 2nd, 2026\n\n\n\nOn 28 July, the Learn WordPress DACH team launched its first German-language course cohort, “Starten mit WordPress.” A huge thank you to everyone who signed up and to our cohort facilitators for helping bring this initiative to life. DACH team is looking forward to seven weeks of learning WordPress together through weekly live sessions and engaging asynchronous activities in between.\n\n\n\nWe successfully hosted our Office Hours session on 26 July 2026 and have published a recap post: https://make.wordpress.org/training/2026/07/30/office-hours-meeting-recap-26th-july-2026/. Thank you so much for the draft post, @rfluethi.\n\n\n\nThe Learn WordPress website is now 100% translated into Marathi! You can explore the Marathi version here: https://learn.wordpress.org/?locale=mr. A big thank you to @makarand  & everyone who contributed to reaching this milestone.\n\n\n\nJoin WordCamp US 2026 Contributor Day – https://us.wordcamp.org/2026/join-wordcamp-us-2026-contributor-day/\n\n\n\nPitching WordCamp US to Your Boss – https://us.wordcamp.org/2026/pitching-wordcamp-us-to-your-boss/\n\n\n\nHow to Bring Your Community to Make WordPress Slack?
https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/\n\n\n\n\n\n\n2. Come and Contribute\n\n\n\n\nContent ready for review\n\nSee Guidelines for reviewing content when reviewing content.\n\nWe have 9 issues ready for review\n\n\n\n\n\n\n\nFeedback awaiting validation\n\nSee Validating and Applying Content Feedback for step-by-step guidance on validating feedback.\n\nWe have 47 issues that require validation\n\n\n\n\n\n\n\nTopics awaiting vetting\n\nSee Vetting Topic Ideas for step-by-step guidance on vetting topic ideas.\n\nWe have 2 issues that require vetting\n\n\n\n\n\n\n\nValidated feedback awaiting fix\n\nContributors, see Validating and Applying Content Feedback for step-by-step guidance on applying feedback that has been validated.\n\nWe have 25 issues awaiting a fix\n\n\n\n\n\n\n\n\n3. Contribution Acknowledgement\n\n\n\n\nBadges awarded:\n\nNo badges awarded this week\n\n\n\n\n\n\n4. Project updates\n\n\n\n\nBuilding on the momentum of our last learning cohort (Block Theme Development Course cohort), we are excited to launch our next cohort focused on Plugin Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem.\n\n\n\nAlso, we are excited to launch our next cohort focused on Plugin Development next month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem.\n\n\n\n\n5. Upcoming Online Workshops\n\n\n\n\nWordCamp US 2026 Contributor Day Online, Sunday, August 16 – https://www.meetup.com/learn-wordpress-online-workshops/events/315907994\n\n\n\n\n6. Contributor Updates\n\n\n\n\nWhat have you been working on, and how has it been going?\n\n\n\nAnything you’ve accomplished since the last meeting?\n\n\n\nDo you have any blockers?\n\n\n\nCan other contributors or Training Team members help you in some way?\n\n\n\n\n7. Open Discussions\n\n\n\n

If you have topics you’d like discussed in the meeting, please leave them as a comment on this post.

\n\n\n\n\n\n\n\n

You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, then come walk through our onboarding program to get to know the team and how we work. And if you have questions, feel free to reach out in the #training Slack channel at any time.

", "id": 17186737, "pubDate": "Mon, 10 Aug 2026 20:05:40 GMT", "whenReceived": "Mon, 10 Aug 2026 21:40:17 GMT", "whenUpdated": "Tue, 11 Aug 2026 07:57:43 GMT", "likes": [], "metadata": { "wpPostId": 177240, "wpSiteId": 46403572 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 10 Aug 2026 20:15:15 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69444", "title": "Hi Arabic Polyglots team! 👋", "link": "https://make.wordpress.org/polyglots/2026/08/10/hi-arabic-polyglots-team-%f0%9f%91%8b/", "description": "

I submitted a translation correction for WordPress Core (Administration) in Arabic (ar).

\n

Context: Plugins list bulk actions / links (wp-admin/includes/class-wp-plugins-list-table.php:632)

\n

Original English: Deactivate

\n

Current Translation: تم تعطيل (State / Past tense)

\n

Suggested Fix: تعطيل (Action / Imperative)

\n

GlotPress Link: https://translate.wordpress.org/projects/wp/dev/admin/ar/default/?filters%5Bterm%5D=Deactivate&filters%5Bterm_scope%5D=scope_any&filters%5Bstatus%5D=current_or_waiting_or_fuzzy_or_untranslated&filters%5Buser_login%5D=&filter=Apply+Filters&sort%5Bby%5D=priority&sort%5Bhow%5D=desc

\n

Could a Translation Editor (GTE/PTE) please review and approve it when you get a chance?

\n\n #ar \n\n\n

Thank you!

\n

#editor-requests

", "id": 17184999, "pubDate": "Mon, 10 Aug 2026 19:54:11 GMT", "whenReceived": "Mon, 10 Aug 2026 20:15:15 GMT", "whenUpdated": "Mon, 10 Aug 2026 20:15:15 GMT", "likes": [], "metadata": { "wpPostId": 69444, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69479", "title": "PTE Request for ElállásiGomb – Online Elállás for WooCommerce", "link": "https://make.wordpress.org/polyglots/2026/08/10/pte-request-for-elallasigomb-online-elallas-for-woocommerce/", "description": "

I’m the author of this plugin and would like to request Project
\nTranslation Editor (PTE) rights for the following locale:

\n\nhttps://wordpress.org/plugins/elallasigomb-online-elallas-for-woocommerce/\n\n\n\n #hu_HU @bshhun (@tobifjellner)\n\n\n

Happy to answer any questions.

\n

#editor-requests

", "id": 17185000, "pubDate": "Mon, 10 Aug 2026 19:53:07 GMT", "whenReceived": "Mon, 10 Aug 2026 20:15:15 GMT", "whenUpdated": "Mon, 10 Aug 2026 22:23:00 GMT", "likes": [], "metadata": { "wpPostId": 69479, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69473", "title": "PTE Request for OMS Labels AI Transparency", "link": "https://make.wordpress.org/polyglots/2026/08/10/pte-request-for-oms-labels-ai-transparency/", "description": "

Hello Polyglots team,

\n

I am the plugin author of OMS Labels AI Transparency. I have submitted complete German translations for both Stable (509 strings) and Stable Readme (53 strings). All 562 translations are currently waiting and the automated checks report 0 warnings.

\n

Plugin:

\n\nhttps://wordpress.org/plugins/oms-labels-ai-transparency/\n\n\n

Translation project:

\n\nhttps://translate.wordpress.org/projects/wp-plugins/oms-labels-ai-transparency/\n\n\n

Please review the translations and add the following WordPress.org user as Project Translation Editor for German:

\n\n #de_DE – @stewn (@tobifjellner)\n\n\n

I will follow the German glossary and style guide and am happy to address any feedback.

\n

Thank you!

\n

#editor-requests

", "id": 17185001, "pubDate": "Mon, 10 Aug 2026 19:52:57 GMT", "whenReceived": "Mon, 10 Aug 2026 20:15:15 GMT", "whenUpdated": "Mon, 10 Aug 2026 23:37:23 GMT", "likes": [], "metadata": { "wpPostId": 69473, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69458", "title": "Hi Polyglots, I am…", "link": "https://make.wordpress.org/polyglots/2026/08/10/hi-polyglots-i-am-2/", "description": "

Hi Polyglots, I am the plugin author for Japan Clickable Map.
\nI have submitted a Japanese translation for my plugin and would like to
\nrequest PTE for it.
\nPlugin: https://wordpress.org/plugins/japan-clickable-map/
\nTranslation: https://translate.wordpress.org/projects/wp-plugins/japan-clickable-map/

\n\n #ja @plugear \n\n\n

Thank you!

\n

#editor-requests

", "id": 17182747, "pubDate": "Mon, 10 Aug 2026 16:56:25 GMT", "whenReceived": "Mon, 10 Aug 2026 18:32:29 GMT", "whenUpdated": "Mon, 10 Aug 2026 18:32:29 GMT", "likes": [], "metadata": { "wpPostId": 69458, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69460", "title": "PTE Request for Fense Block VPN & Proxy", "link": "https://make.wordpress.org/polyglots/2026/08/10/pte-request-for-fense-block-vpn-proxy/", "description": "

I am the plugin author for Fense Block VPN & Proxy. I would like to be able to
\napprove translations for my plugin. Please add the following WordPress.org user
\nas translation editor for the locales below:

\n\nhttps://wordpress.org/plugins/fense-block-vpn-proxy/\n\n\n\n #ar – @devozon (@devozon)\n\n #fr_FR – @devozon\n\n #zh_CN – @devozon (@devozon)\n\n\n

— ja – @devozon

\n

If you have any questions, just comment here. Thank you!

\n

#editor-requests

", "id": 17182748, "pubDate": "Mon, 10 Aug 2026 16:55:23 GMT", "whenReceived": "Mon, 10 Aug 2026 18:32:29 GMT", "whenUpdated": "Tue, 11 Aug 2026 14:48:41 GMT", "likes": [], "metadata": { "wpPostId": 69460, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69464", "title": "Hi Polyglots,", "link": "https://make.wordpress.org/polyglots/2026/08/10/hi-polyglots-126/", "description": "

I’m the plugin author of SparkElevate Notice Control, which was approved and released today. I have prepared complete translations for five locales and would like to import and maintain them myself.

\n\nhttps://wordpress.org/plugins/sparkelevate-notice-control/\n\nhttps://translate.wordpress.org/projects/wp-plugins/sparkelevate-notice-control/\n\n\n

Please consider adding me as PTE for the following locales:

\n\n #de_DE – @damianstrohmaier (@tobifjellner)\n\n\n

Each locale is complete at 115/115 strings, including the plural forms and the plugin header. Product name, author name and URLs are intentionally kept identical across locales.

\n

I’m happy to answer any questions, and of course fine with the translations being reviewed before approval.

\n

Thank you!

\n

#editor-requests

", "id": 17182749, "pubDate": "Mon, 10 Aug 2026 16:53:24 GMT", "whenReceived": "Mon, 10 Aug 2026 18:32:29 GMT", "whenUpdated": "Mon, 10 Aug 2026 23:37:23 GMT", "likes": [], "metadata": { "wpPostId": 69464, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69462", "title": "PTE Request for Seory Posts to Markdown", "link": "https://make.wordpress.org/polyglots/2026/08/10/pte-request-for-seory-posts-to-markdown/", "description": "

I am the plugin author for Seory Posts to Markdown. I have submitted Japanese translations for the plugin (Stable, Development and both Readme projects) and they are currently waiting for approval. I would like to become a Project Translation Editor so I can review and approve translations for my own plugin.

\n

Name: Seory Posts to Markdown
\nURL: https://wordpress.org/plugins/seory-posts-to-markdown/

\n\n #ja\n\n\n

Thank you!

\n

#editor-requests

", "id": 17180427, "pubDate": "Mon, 10 Aug 2026 15:10:35 GMT", "whenReceived": "Mon, 10 Aug 2026 16:49:51 GMT", "whenUpdated": "Mon, 10 Aug 2026 16:49:51 GMT", "likes": [], "metadata": { "wpPostId": 69462, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69452", "title": "Hi! I’m the author of…", "link": "https://make.wordpress.org/polyglots/2026/08/10/hi-im-the-author-of-9/", "description": "

Hi! I’m the author of the eShopLogistic Shipping Calculator plugin
\n( https://wordpress.org/plugins/eshoplogisticru/ ) and would like to
\nrequest PTE status to translate its readme (and eventually the
\nplugin strings) into Russian.

\n\n #ru_RU – @eshoplogistic (@tobifjellner)\n\n\n

#editor-requests

", "id": 17175683, "pubDate": "Mon, 10 Aug 2026 12:15:53 GMT", "whenReceived": "Mon, 10 Aug 2026 13:24:43 GMT", "whenUpdated": "Mon, 10 Aug 2026 18:32:29 GMT", "likes": [], "metadata": { "wpPostId": 69452, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69450", "title": "Hi dear mentors, We have…", "link": "https://make.wordpress.org/polyglots/2026/08/10/hi-dear-mentors-we-have-196/", "description": "

Hi dear mentors,

\n

We have great translations that we’d like to integrate on translate.wordpress. Can you please add @wptranslationsorg as CLPTE for this project:

\n

Project URL: https://wordpress.org/theme/happiness-coach

\n

To make sure we can apply to this access we fulfilled answered all points below:

\n

1. Our translators use/created community-style guides and glossaries. They are all GTEs or PTEs of their respective locales already. More info about our team members (https://wp-translations.pro/team/)
\n2. Sources of translation are available on TranslationsPress (https://www.translationspress.com/wp-translations/)
\n3. The review process with GTEs and PTEs is handled in translate.wordpress (see details in 4)
\n4. In case of need any locales GTEs or PTEs can get in touch directly here on make or on Slack via @wptranslationsorg
\nOur contact form page (https://wp-translations.pro/contact/) is also available.
\n5. General Translation Editors will be noticed of each locale after imports of course.

\n

PS: Thanks for all previously accepted requests

\n

Thanks in advance
\nFX for the WP-Translations Team

\n

#clpte

\n

#editor-requests

", "id": 17173594, "pubDate": "Mon, 10 Aug 2026 10:30:43 GMT", "whenReceived": "Mon, 10 Aug 2026 11:41:47 GMT", "whenUpdated": "Mon, 10 Aug 2026 11:41:47 GMT", "likes": [], "metadata": { "wpPostId": 69450, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/training/feed/", "whenReceived": "Mon, 10 Aug 2026 09:28:24 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/training/feed/", "guid": "https://make.wordpress.org/training/?p=177223", "title": "Training Team Meeting Recap – 4th August 2026", "link": "https://make.wordpress.org/training/2026/08/10/training-team-meeting-recap-4th-august-2026/", "description": "

This meeting followed this meeting agenda. You can see conversations from the meeting in this Slack Log. (If you don’t have a Slack account, you can set one up.)

\n\n\n\nIntroductions and Welcome\n\n\n\n

There were 30 attendees: @pravin1996, @jenish1234, @sonaliprajapati, @alkesh7, @dhavalkapadane, @ravigadhiyawp, @fahimmurshed, @sumitsingh, @rithika3, @rfluethi, @jadavsanjay, @huzaifaalmesbah, @dilip2615, @rjekic, @gohelkunjan, @andrewssanya, @makanikaran, @Ibrahimkh4l33l, @palak678, @nikola93n, @mehrazmorshed, @mosescursor, @sibokul, @mohkatz (async), @mebo (async), @ursha (async), @valeriewandeler (async), @nitspatel (async), @vishitshah (async), @VasantRajput (async)

\n\n\n\n

Newcomers: @alanabwarner, @simea, @nityasaha

\n\n\n\n

Meeting hosted by: @SumitSingh

\n\n\n\n

Note Taker: @mohkatz

\n\n\n\n

Note Reviewer: @VasantRajput

\n\n\n\n

The icebreaker question was: What is one WordPress feature or tool you recently discovered that made your work easier? Contributors mentioned tools and features including the WordPress Site Editor, Block Editor, connectors screen, ACF, Full Site Editing, and other tools that have helped make development, design, and workflow tasks easier.

\n\n\n\n

Welcome! Please post in the #training channel or reach out to a team member to help you with contributing. Resources to check out our onboarding program, and our Guide Program.

\n\n\n\nNews\n\n\n\nMeeting Note Takers\n\n\n\n

Here is our current note taker roster:

\n\n\n\n\n11th August – @andrewssanya\n\n\n\n18th August – @sibokul\n\n\n\n25th August – @makanikaran\n\n\n\n1st September – @sonaliprajapati\n\n\n\n8th September – @priyankaadbrains\n\n\n\n15th September – @palak678\n\n\n\n\n

Important note: If anyone needs to know more about note-taking and needs guidance in creating a Recap Note Post, they can DM @VasantRajput. He will guide you for a Recap Note and he will review & publish your Recap Post.

\n\n\n\nLooking for feedback\n\n\n\n\nWe are planning an Office Hours session for August 22, 2026.\n\nTopic: Note-taking and publication workflow: Who does what, and how?\n\n\n\nMore details are available here: Office Hours #3570\n\n\n\n\n\nSeveral GitHub issues related to Office Hours have also been reviewed.\n\nYou can view all open Office Hours tickets and share suggestions here: Office Hours issues list\n\n\n\n\n\nWe have discussed starting a regular GitHub triage meeting, but this has not yet been confirmed.\n\nProposed schedule: Triage Squad GitHub triage – biweekly on Thursdays at 07:00 UTC\n\n\n\nPlease share if you would be interested in joining this Slack meeting if the team decides to move forward with it.\n\n\n\n\n\nBig thank you to everyone who has shared feedback so far in Training Team Office Hours #3535.\n\n\n\nThe team is actively updating the Training Team handbooks, and there is still time to contribute.\n\nIf you have suggestions, improvements, or ideas, please share them in Update the Training Team Handbook #3447.\n\n\n\n\n\n\nLooking for volunteers\n\n\n\n\nWe need help finding content that could be updated and consolidated.\n\nOne group can review all the Training Team handbook content.\n\n\n\nOne group can review the courses.\n\n\n\n\n\nThe team has started creating thumbnails for lessons that still need them.\n\nYou are welcome to contribute to this important and creative project.\n\n\n\nSee Create Thumbnails for Learn WordPress Lessons #3428 for details on how to work on the remaining thumbnails.\n\n\n\n\n\nWe currently have around 555 open issues, and it may be more effective to divide them into smaller categories and work through them one by one.\n\nGoing through issues one by one\n\n\n\nIdentifying outdated or irrelevant issues\n\n\n\nSuggesting fixes or next steps\n\n\n\nAdding comments where needed before closing or updating\n\n\n\n\n\nSome issues have been labelled Good First Issue.\n\nIf you want to start contributing, look for issues with this label, particularly those with “Feedback” in the issue title.\n\n\n\nYou can help verify them by following the handbook guidance on validating content feedback issues.\n\n\n\n\n\nFor upcoming sessions, the proposal is to divide open issues into smaller groups and work through one category at a time.\n\nThe team could begin with [Content] Needs Translation Reviewer, based on feedback from the last meeting.\n\n\n\nOther available categories include:\n\nIssues without a label\n\n\n\nAwaiting Triage\n\n\n\n[Content] Feedback\n\n\n\n[Type] Bug\n\n\n\n\n\n\n\nPlease share which category you think should be reviewed first. Once selected, the team can divide the issues and work through them together, one by one.\n\n\n\n\nUpdates from last week’s Triage Squad session\n\n\n\n\nThe team is planning to start Triage Squad GitHub triage, biweekly on Thursdays at 07:00 UTC.\n\n\n\nIf you are interested, please comment or share feedback in the #training channel on WordPress Slack.\n\n\n\n\nOther News\n\n\n\n\nThe Training Team Monthly Update for August has been published: Training Team Update – August 2nd, 2026\n\n\n\nThe Learn WordPress DACH team launched its first German-language course cohort, Starten mit WordPress, on July 28, 2026. The program is currently running, and discussions with participants are already producing real insights into WordPress.\n\n\n\nThe team successfully hosted the Office Hours session on July 26, 2026 and published a recap post: Office Hours Meeting Recap – 26th July 2026\n\n\n\nThe Learn WordPress website is now 100% translated into Marathi. You can explore the Marathi version here: Learn WordPress in Marathi. A big thank you to @makarand and everyone who contributed to reaching this milestone.\n\n\n\nContributors are invited to join WordCamp US 2026 Contributor Day\n\n\n\nIf you are looking for support to attend WordCamp US, see Pitching WordCamp US to Your Boss\n\n\n\nLocal WordPress communities can now learn How to Bring Your Community to Make WordPress Slack\n\n\n\n\nCome and Contribute\n\n\n\nThis week’s contribution focus area\n\n\n\n\nContent ready for review\n\nSee Guidelines for reviewing content when reviewing content.\n\n\n\nWe have 9 issues ready for review\n\n\n\n\n\nFeedback awaiting validation\n\nSee Validating and Applying Content Feedback for step-by-step guidance on validating feedback.\n\n\n\nWe have 48 issues that require validation\n\n\n\n\n\nTopics awaiting vetting\n\nSee Vetting Topic Ideas for step-by-step guidance on vetting topic ideas.\n\n\n\nWe have 2 issues that require vetting\n\n\n\n\n\nValidated feedback awaiting fix\n\nContributors, see Validating and Applying Content Feedback for step-by-step guidance on applying feedback that has been validated.\n\n\n\nWe have 25 issues awaiting a fix\n\n\n\n\n\n\nContribution Acknowledgement\n\n\n\n\nBadges awarded:\n\nNo badges were awarded this week.\n\n\n\n\n\nGive Props:\n\n@sumitsingh: Props to @rjekic for writing and publishing the Training Team Monthly Update for August.\n\n\n\n@sumitsingh: Props to @rfluethi for drafting the post for the Office Hours session on July 26, 2026.\n\n\n\n\n\n\nProject updates\n\n\n\n\nBuilding on the momentum of the Block Theme Development Course cohort, the team is preparing to launch its next cohort focused on Plugin Development.\n\n\n\nThe team looks forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem.\n\n\n\n\nUpcoming Online Workshops\n\n\n\n\nWordCamp US 2026 Contributor Day Online, Sunday, August 16\n\n\n\n\nContributor Updates\n\n\n\n\nWhat have you been working on, and how has it been going?\n\n@mebo shared that they are continuing work on Module 13’s “Rendering plugin data” lesson, building from Jonathan’s initial draft and expanding the remaining sections. The lesson covers theme templates, Site Editor templates, custom blocks, shortcodes, template tags, and hooking into the_content, with each approach supported by a working code example. There are no blockers, but feedback is welcome on whether the lesson should remain as one lesson or be split, given the number of rendering approaches covered. Review is requested in Rendering plugin data #2182.\n\n\n\n\n\nAnything you’ve accomplished since the last meeting?\n\n\n\nDo you have any blockers?\n\n\n\nCan another contributor or a Training Team member help you in some way?\n\n\n\n\nOpen Discussions\n\n\n\n\nIf you have topics you’d like discussed in the meeting, please leave them as a comment on this issue.\n\n\n\nCurrently, no new topics have been raised, but asynchronous contributions are welcome via the Slack thread to continue the discussion.\n\n\n\n\n\n\n\n\n

You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, then come walk through our onboarding program to get to know the team and how we work. And if you have questions, feel free to reach out in the #training Slack channel at any time.

\n\n\n\n

\n

#meeting-recap, #training, #training-team

", "id": 17170972, "pubDate": "Mon, 10 Aug 2026 08:51:00 GMT", "whenReceived": "Mon, 10 Aug 2026 09:28:24 GMT", "whenUpdated": "Mon, 10 Aug 2026 09:28:24 GMT", "likes": [], "metadata": { "wpPostId": 177223, "wpSiteId": 46403572 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Sun, 09 Aug 2026 07:54:41 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69440", "title": "#pte-request Hi Polyglots, I’m the…", "link": "https://make.wordpress.org/polyglots/2026/08/09/pte-request-hi-polyglots-im-the-3/", "description": "

#pte-request

\n

Hi Polyglots, I’m the plugin author of Dashboard for Availio and I’d like to request PTE access for Swiss German so I can approve the translations for my own plugin.

\n

Plugin: https://wordpress.org/plugins/dashboard-for-availio/
\nGlotPress: https://translate.wordpress.org/projects/wp-plugins/dashboard-for-availio/
\nLocale: #de_CH
\nWordPress.org username: gianlucad

\n

I’m already PTE for #de_DE for this plugin. The full Swiss German readme translation is imported and currently waiting for approval. I’m based in Switzerland, so I can maintain the de_CH strings (Swiss spelling). Thank you!

\n

#editor-requests

", "id": 17154681, "pubDate": "Sun, 09 Aug 2026 07:48:31 GMT", "whenReceived": "Sun, 09 Aug 2026 07:54:41 GMT", "whenUpdated": "Sun, 09 Aug 2026 07:54:41 GMT", "likes": [], "metadata": { "wpPostId": 69440, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69414", "title": "PTE Request for Fliegerlogin – SSO for Vereinsflieger", "link": "https://make.wordpress.org/polyglots/2026/08/08/pte-request-for-fliegerlogin-sso-for-vereinsflieger/", "description": "

I am the plugin author. I have imported an existing German translation that I maintained before the plugin was hosted on WordPress.org, and I would like to be able to review and approve it.

\n

Name: Fliegerlogin – SSO for Vereinsflieger
\nURL: https://wordpress.org/plugins/sso-for-vereinsflieger/
\nTranslation URL: https://translate.wordpress.org/projects/wp-plugins/sso-for-vereinsflieger/
\nGlotPress username: @patois87

\n\n #de_DE (@tobifjellner)\n\n #de_CH\n\n\n

Thank you!

\n

#editor-requests

", "id": 17148293, "pubDate": "Sat, 08 Aug 2026 18:01:47 GMT", "whenReceived": "Sat, 08 Aug 2026 18:19:02 GMT", "whenUpdated": "Sat, 08 Aug 2026 20:01:00 GMT", "likes": [], "metadata": { "wpPostId": 69414, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69418", "title": "PTE Request for yaxii-smart-form-lite", "link": "https://make.wordpress.org/polyglots/2026/08/08/pte-request-for-yaxii-smart-form-lite/", "description": "

Hello Polyglots,

\n

I am the author/representative for https://wordpress.org/plugins/yaxii-smart-form-lite/ .

\n

We have submitted translations via our translation account (@ghost4tech) and would like to request Project Translation Editor (PTE) permissions so @ghost4tech can manage and approve translations for this plugin.

\n

Requested User:
\n— ar – @ghost4tech

\n\n #fr_FR – @ghost4tech\n\n\n

Thank you!

\n

#editor-requests

", "id": 17148295, "pubDate": "Sat, 08 Aug 2026 17:55:38 GMT", "whenReceived": "Sat, 08 Aug 2026 18:19:02 GMT", "whenUpdated": "Sat, 08 Aug 2026 21:42:03 GMT", "likes": [], "metadata": { "wpPostId": 69418, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69416", "title": "PTE Request for kabook Rebuy Discount", "link": "https://make.wordpress.org/polyglots/2026/08/08/pte-request-for-kabook-rebuy-discount/", "description": "

Hello Polyglots team,

\n

I am the author of the plugin Kabook Rebuy Discount. I would like to request PTE (Project Translation Editor) access for the Persian (#fa_IR) locale to manage the translations for this plugin.

\n

As I am actively developing the plugin, having PTE access will allow me to ensure that the translation terminology remains consistent with the plugin’s user interface and overall user experience.

\n

Plugin Link: https://wordpress.org/plugins/kabook-rebuy-discount/

\n

Profile: @saeidafshari

\n

I am an active PTE for the #fa_IR locale, and I am committed to following the Persian translation standards and ensuring the high quality of all translated strings for this project.

\n\n #fa_IR (@tobifjellner)\n\n\n

Thank you for your time and help!

\n

Best regards,

\n

Saeid Afshari

\n

#editor-requests

", "id": 17142994, "pubDate": "Sat, 08 Aug 2026 10:45:31 GMT", "whenReceived": "Sat, 08 Aug 2026 11:19:34 GMT", "whenUpdated": "Sat, 08 Aug 2026 18:19:02 GMT", "likes": [], "metadata": { "wpPostId": 69416, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69389", "title": "#pte-request I’m the author of…", "link": "https://make.wordpress.org/polyglots/2026/08/08/pte-request-im-the-author-of/", "description": "

I’m the author of this plugin and a native Norwegian speaker. I’d like to become PTE for my own plugin in nn_NO and nb_NO.

\n

Plugin: https://wordpress.org/plugins/mountaineering-labs-stock-sync/

\n\n #nn_NO\n\n\n

— nb_NO

\n

Username: @mountaineeringlabs

\n

The translations are my own work. Thanks!

\n

#editor-requests

", "id": 17141853, "pubDate": "Sat, 08 Aug 2026 08:31:45 GMT", "whenReceived": "Sat, 08 Aug 2026 09:38:43 GMT", "whenUpdated": "Sat, 08 Aug 2026 18:19:02 GMT", "likes": [], "metadata": { "wpPostId": 69389, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69397", "title": "PTE Request for ShopZone Theme", "link": "https://make.wordpress.org/polyglots/2026/08/08/pte-request-for-shopzone-theme-2/", "description": "

I’ve suggested translations for the ShopZone theme and would like to have them reviewed. I’d also like to become a PTE. I also confirm that I’ve read the style guide and glossary for the locales.

\n

Theme URL: – https://wordpress.org/themes/shopzone/

\n\n #ko_KR \n\n\n

— ar

\n\n #he_IL \n\n\n

#editor-requests

", "id": 17140934, "pubDate": "Sat, 08 Aug 2026 05:59:00 GMT", "whenReceived": "Sat, 08 Aug 2026 07:30:29 GMT", "whenUpdated": "Sat, 08 Aug 2026 20:01:00 GMT", "likes": [], "metadata": { "wpPostId": 69397, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69382", "title": "PTE Request for Oneguard for WooCommerce (German)", "link": "https://make.wordpress.org/polyglots/2026/08/07/pte-request-for-oneguard-for-woocommerce-german/", "description": "https://wordpress.org/plugins/oneguard-for-woocommerce/\n\n\n\n #de_DE (@tobifjellner)\n\n\n

#editor-requests

", "id": 17129401, "pubDate": "Fri, 07 Aug 2026 15:30:14 GMT", "whenReceived": "Fri, 07 Aug 2026 17:00:55 GMT", "whenUpdated": "Sat, 08 Aug 2026 20:01:00 GMT", "likes": [], "metadata": { "wpPostId": 69382, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69380", "title": "Hi Polyglots 👋", "link": "https://make.wordpress.org/polyglots/2026/08/07/hi-polyglots-%f0%9f%91%8b/", "description": "

I’m the author of Alnora — Doctor Appointment Booking & Clinic Management ( https://wordpress.org/plugins/alnora-clinic/ ).
\nI’ve prepared translations for the plugin and its readme and would like PTE rights so I can review, approve and maintain them going forward.

\n

Plugin: alnora-clinic
\nURL: – https://wordpress.org/plugins/alnora-clinic/
\nMy WordPress.org username: @alnoraclinic
\nLocales requested:

\n

— de_DE

\n\n #fr_FR\n\n #es_ES\n\n #it_IT\n\n\n

— nl_NL
\n— pl_PL
\n— sv_SE

\n\n #da_DK\n\n #nb_NO (@tobifjellner)\n\n\n

— uk
\n— ru_RU

\n

The plugin ships in these languages already, and the translations are professionally prepared; I’ll keep them accurate as the plugin evolves. Thank you!

\n

#editor-requests

", "id": 17129402, "pubDate": "Fri, 07 Aug 2026 15:26:59 GMT", "whenReceived": "Fri, 07 Aug 2026 17:00:55 GMT", "whenUpdated": "Sat, 08 Aug 2026 18:19:02 GMT", "likes": [], "metadata": { "wpPostId": 69380, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69374", "title": "Access for German, for both branches.", "link": "https://make.wordpress.org/polyglots/2026/08/07/cess-for-german-for-both-branches/", "description": "https://wordpress.org/plugins/leadlotse/\n\nhttps://translate.wordpress.org/projects/wp-plugins/leadlotse/\n\n\n\n #de_DE – @hafenstudios\n\n\n

Both branches are already fully translated and waiting for approval: 225 of 229 strings each. The four remaining originals are the plugin name, the author name and two URLs, which we deliberately leave untranslated.

\n

The two branches are genuinely different texts, not one text copied twice. The informal branch uses “du” with the matching verb forms throughout, the formal branch uses “Sie”. Both were written by native German speakers, following the German style guide and glossary.

\n

A note on the validation warnings, so nobody has to guess:

\n

The block keywords “contact”, “form” and “lead” are translated as “Kontakt”, “Formular” and “Lead”. German capitalises nouns, so the initial uppercase is correct here even though the English original is lowercase. The double opt-in email body starts lowercase because it continues the salutation “Hallo,” / “Guten Tag,”, which is rendered from a separate string. Lowercase continuation after the salutation comma is standard German letter style.

\n

Happy to correct anything that does not match the style guide or the glossary.

\n

Thanks a lot for your work,
\nHorst

\n

#editor-requests

", "id": 17119437, "pubDate": "Fri, 07 Aug 2026 08:08:42 GMT", "whenReceived": "Fri, 07 Aug 2026 08:33:29 GMT", "whenUpdated": "Sat, 08 Aug 2026 09:38:43 GMT", "likes": [], "metadata": { "wpPostId": 69374, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69370", "title": "PTE Request for ClickBlog AI Auto Poster", "link": "https://make.wordpress.org/polyglots/2026/08/07/pte-request-for-clickblog-ai-auto-poster/", "description": "

Hi Polyglots,

\n

I am the plugin author for ClickBlog AI Auto Poster. I would like to request
\nPTE access so that I can review and approve translations for my own plugin.

\n

Name: ClickBlog AI Auto Poster
\nURL: https://wordpress.org/plugins/clickblog/
\nTranslation project: https://translate.wordpress.org/projects/wp-plugins/clickblog/

\n\n #ko_KR — @artgrafy\n\n\n

I am a native Korean speaker and the plugin is primarily aimed at Korean users.
\nI have a complete Korean translation ready for all 124 strings, prepared against
\nthe WordPress core Korean glossary (post → 글, draft → 임시글, private → 비공개),
\nand I will import it as soon as access is granted. I am happy to have it reviewed
\nby a GTE first if the locale team prefers that.

\n

If you have any questions, just let me know here. Thank you for your time!
\n #editor-requests

", "id": 17119438, "pubDate": "Fri, 07 Aug 2026 08:08:29 GMT", "whenReceived": "Fri, 07 Aug 2026 08:33:29 GMT", "whenUpdated": "Fri, 07 Aug 2026 08:33:29 GMT", "likes": [], "metadata": { "wpPostId": 69370, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69372", "title": "PTE Request for Ploto Theme", "link": "https://make.wordpress.org/polyglots/2026/08/07/pte-request-for-ploto-theme-4/", "description": "

I’ve suggested translations for the Ploto theme and would like to have them reviewed. I’d also like to become a PTE. I also confirm that I’ve read the style guide and glossary for the locales.

\n

Ploto : – https://wordpress.org/themes/ploto/

\n\n #ar\n\n #da_dk\n\n\n

Thank you!

\n

#editor-requests

", "id": 17119439, "pubDate": "Fri, 07 Aug 2026 07:01:30 GMT", "whenReceived": "Fri, 07 Aug 2026 08:33:29 GMT", "whenUpdated": "Fri, 07 Aug 2026 08:33:29 GMT", "likes": [], "metadata": { "wpPostId": 69372, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69368", "title": "WordPress 7.0.3 has been released….", "link": "https://make.wordpress.org/polyglots/2026/08/06/wordpress-7-0-3-has-been-released/", "description": "

WordPress 7.0.3 has been released. It is a security release. There are no new strings in the main project.

\n

In order to benefit from the automated release process it could be possible that you have to prepare your locale first. Please make sure that your locale is prepared.

\n

WordPress 7.0.3 release

\n

", "id": 17110557, "pubDate": "Thu, 06 Aug 2026 19:34:06 GMT", "whenReceived": "Thu, 06 Aug 2026 20:45:30 GMT", "whenUpdated": "Thu, 06 Aug 2026 20:45:30 GMT", "likes": [], "metadata": { "wpPostId": 69368, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69353", "title": "Finnish – EU Order Withdrawal Button for WooCommerce", "link": "https://make.wordpress.org/polyglots/2026/08/06/finnish-eu-order-withdrawal-button-for-woocommerce/", "description": "

PTE Request for EU Order Withdrawal Button for WooCommerce

\n

Some people have suggested translations for this plugin and I would like to have them reviewed. I’d also like to become a PTE. I confirm that I’ve read the style guide and/or glossary for the fi locale.

\n

Name: EU Order Withdrawal Button for WooCommerce

\n

URL: https://wordpress.org/plugins/eu-order-withdrawal-button-for-woocommerce/

\n\n #fi\n\n\n

#editor-requests

", "id": 17108423, "pubDate": "Thu, 06 Aug 2026 19:00:59 GMT", "whenReceived": "Thu, 06 Aug 2026 19:03:06 GMT", "whenUpdated": "Thu, 06 Aug 2026 19:03:06 GMT", "likes": [], "metadata": { "wpPostId": 69353, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://wordpress.org/news/podcast/feed/", "whenReceived": "Thu, 06 Aug 2026 18:57:06 GMT", "items": [ { "feedUrl": "https://wordpress.org/news/podcast/feed/", "guid": "https://wordpress.org/news/?p=21327", "title": "WordPress 7.0.3 release", "link": "https://wordpress.org/news/2026/08/wordpress-7-0-3-release/", "description": "WordPress 7.0.3 is now available\n\n\n\n

WordPress 7.0.3 is now available which features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.

\n\n\n\n

You can update to WordPress 7.0.3 by downloading it from WordPress.org, or visiting your site’s Dashboard → Updates and clicking Update Now. Sites that support automatic background updates will begin updating shortly.

\n\n\n\n

For more information, please visit the WordPress 7.0.3 HelpHub site.

\n\n\n\nSecurity updates included in this release\n\n\n\n

The security team would like to thank the following people for responsibly reporting vulnerabilities and allowing them to be fixed in this release:

\n\n\n\n\nPre-auth reflected cross-site scripting (XSS) on the login screen with potential to lead to PHP code execution reported by the team at pwn.ai.\n\n\n\nContributor+ stored cross-site scripting (XSS) in posts via the emoji settings element reported by Asaf Mozes (amosec)\n\n\n\nContributor+ stored cross-site scripting (XSS) in the Post Content block reported by N05ec@LZU\n\n\n\nContributor+ stored cross-site scripting (XSS) in Quick Edit on sites with a large number of users reported by Naveen S and Ajmal Moochingal\n\n\n\nContributor+ stored cross-site scripting (XSS) in the Post Date block reported by Alex Concha of the WordPress Security Team\n\n\n\nA privilege escalation issue on multisite networks with user registration enabled, allowing a user to create a new site reported by Aikido Security\n\n\n\nAn information disclosure issue in the Latest Comments block exposing comments on password-protected posts reported by Ehtisham Siddiqui of the WordPress Security Team\n\n\n\nEnumeration of post slugs reported by HDWSec\n\n\n\nDisclosure of notes in comment feeds reported by Elio Gubser\n\n\n\nAuthor+ CSS injection via a bypass of the safe CSS attribute filter reported by Anthropic\n\n\n\nBypass of the email address confirmation flow reported by Omar Hasan\n\n\n\nA server-side request forgery (SSRF) issue in URL validation allowing requests to link-local ranges reported by Andrew Mohawk and multiple independent reporters\n\n\n\n\nBackports\n\n\n\n

As a courtesy, these fixes are being backported, where necessary, to all branches eligible to receive security fixes (currently through 4.7). As a reminder, only the most recent version of WordPress is actively supported. The backports are in progress and will ship as they become ready.

\n\n\n\n

WordPress 7.1 RC2 has also been released, containing all applicable fixes.

\n\n\n\nCVE and GHSA references\n\n\n\n

Details of the login screen XSS vulnerability can be found in the advisory: CVE-2026-64638 / GHSA-52p2-r8wf-jcrf.

\n\n\n\nThank you to these WordPress contributors\n\n\n\n

This release was led by John Blackbourn. In addition to the security researchers mentioned above, WordPress 7.0.3 and its backports would not have been possible without the significant contributions of the following people:
Aaron D. Campbell, Aaron Jorbin, Adam Silverstein, adrianmoldovanwp, Aki Hamano, Alex Concha, Andrew Duthie, Andrew Serong, annezazu, Barry, Bernie Reiter, Daniel, Daniel Richards, David Biňovec, Dennis Snell, Ehtisham Siddiqui, Erwan Le Rousseau, Fabian Kaegy, fiocavallari, George Mamadashvili, gubser, Isabel Brison, Jarda Snajdr, Jb Audras, Jeremy Felt, Joe Dolson, Joe Hoyle, John Blackbourn, Jon Surrell, Jonathan Desrosiers, Khokan Sardar, Lance Willett, lucasbustamante, lucatume, Marco Ciampini, Marin Atanasov, Mohammad Jangda, Mukesh Panchal, Paul Kevan, Peter Wilson, ramonopoly, SergeyBiryukov, vortfu, Weston Ruter

\n\n\n\n\nJoin us for the launch of WordPress 7.1 at WordCamp US 2026, August 16–19.", "id": 17108290, "pubDate": "Thu, 06 Aug 2026 18:55:30 GMT", "whenReceived": "Thu, 06 Aug 2026 18:57:06 GMT", "whenUpdated": "Fri, 07 Aug 2026 10:09:44 GMT", "likes": [], "metadata": { "wpPostId": 21327, "wpSiteId": 14607090 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Thu, 06 Aug 2026 18:00:03 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=90272", "title": "First Coworking Session: Thursday, August 13", "link": "https://make.wordpress.org/community/2026/08/06/first-coworking-session-thursday-august-13/", "description": "

Following up on “Rethinking our Monthly Team Meetings“, we’re running our first coworking session next Thursday, August 13th.

\n

Time: 11:30 UTC

\n

What we’ll work on: the handbooks restructure proposal, picking up the audit work and moving pieces of it forward together.

\n

Format: short kickoff to align on what we’re tackling, then a focused work block, then a quick wrap-up on what got done and what’s still open.

\n

This is a first test of the new format, so expect some rough edges, and feel free to just show up even if you haven’t been involved in the handbooks proposal before. All you need is some available time and curiosity.

\n

We’ll follow up here with a short recap after the session.

\n

h/t @unintended8

", "id": 17106956, "pubDate": "Thu, 06 Aug 2026 17:07:59 GMT", "whenReceived": "Thu, 06 Aug 2026 18:00:03 GMT", "whenUpdated": "Thu, 06 Aug 2026 18:00:03 GMT", "likes": [], "metadata": { "wpPostId": 90272, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/test/feed/", "whenReceived": "Thu, 06 Aug 2026 17:42:51 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/?p=12552", "title": "Team Chat Agenda: 6th August, 2026", "link": "https://make.wordpress.org/test/2026/08/06/team-chat-agenda-6th-august-2026/", "description": "

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 6 August 2026, 03:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

\n\n\n\nAgenda\n\n\n\n\nAttendance\n\nAttendance check in with the wp.org username\n\n\n\n\n\nNote-taker and facilitator selection for the next meeting
We encourage all members to contribute to the team chat, and we now welcome Note Takers and Facilitators. This is a great time to get involved in the core test team. Have you recently joined, and you don’t know where to go? Start here (No Skills Required)\n\nThis week’s facilitator and note-taker is – @mosescursor\n\n\n\nNext week’s facilitator note-taker is – Looking for a volunteer ( Ping us #core-test to volunteer)\n\n\n\n\n\nTest Team Discussions\n\nOfficialize the Test Reports\n\n\n\nFeature and enhancement testing Page\n\n\n\nAdd page with current team goals/initiatives\n\n\n\n\n\nOpen Floor\n\nGot a topic? Add in comments below, or bring it up live during the chat.\n\n\n\n\n\nWordPress Ecosystem Announcements\n\nWordPress 7.1 Beta 4\n\n\n\nWhat’s new in Gutenberg 23.5? (July 1, 2026)\n\n\n\nMerge Proposal: Expanding WordPress Core Abilities\n\n\n\nBug Scrub Schedule for WordPress 7.1\n\n\n\nThe Classic block stays in the inserter for WordPress 7.1\n\n\n\nMerge Proposal: Design System Theming\n\n\n\nTransitioning To Rulesets In The Gutenberg Repository\n\n\n\nConsistent navigation in WordPress 7.1 with persistent toolbar\n\n\n\nHardening GitHub Actions workflows across the WordPress organisation\n\n\n\nWhat’s new for developers (July 2026)\n\n\n\nOn-brand maintenance mode for WordPress Block Themes\n\n\n\nWordPress 7.0.2 is now available.\n\n\n\n\n\nTest Team Announcements\n\nWeekly Patch Testing Scrub: Second and Fourth Thursday of the Month at 15:00 UTC\n\n\n\nWeekly Test Chat: Third Thursday of the Month at 15:00 UTC\n\n\n\nMonthly Voice Test Chat: First Thursday of each month at 15:00 UTC\n\n\n\n\n\nCall for Testing\n\nHelp Test WordPress 7.1\n\n\n\nMedia Editor Modal: call for testing\n\n\n\nCall for Testing: client-side media processing\n\n\n\nHelp test new career functionality on WordPress.org\n\n\n\nCall for Testing: Responsive Styling\n\n\n\nWe have Patch Testing issues for the WordPress 7.0.3 milestone that need testing.\n\n\n\nWe also have a couple of Gutenberg Issues that need testing.\n\n\n\n\n\n\nLeave a Comment\n\n\n\n\nDo you have something to propose for the agenda?\n\n\n\nCan’t make the meeting, but have a question for the Test Team?\n\n\n\n\n

If any of the above apply, please leave a comment below.

\n

#test-chat-agenda

", "id": 17106585, "pubDate": "Thu, 06 Aug 2026 14:51:13 GMT", "whenReceived": "Thu, 06 Aug 2026 17:42:51 GMT", "whenUpdated": "Thu, 06 Aug 2026 17:42:51 GMT", "likes": [], "metadata": { "wpPostId": 12552, "wpSiteId": 255400204 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 06 Aug 2026 15:40:57 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69344", "title": "PTE Request for WPNordic Login Designer", "link": "https://make.wordpress.org/polyglots/2026/08/06/pte-request-for-wpnordic-login-designer/", "description": "

I am the plugin author for WPNordic Login Designer. I would like to be able to approve Danish translations for my plugin. Please add the following WordPress.org user as translation editor for the respective locale:

\n\nhttps://wordpress.org/plugins/wpnordic-login-designer/\n\n\n\n #da_DK – @wpnordic\n\n\n

If you have any questions, just comment here. Thank you!

\n

#editor-requests

", "id": 17103609, "pubDate": "Thu, 06 Aug 2026 14:22:51 GMT", "whenReceived": "Thu, 06 Aug 2026 15:40:57 GMT", "whenUpdated": "Thu, 06 Aug 2026 15:40:57 GMT", "likes": [], "metadata": { "wpPostId": 69344, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69346", "title": "PTE Request for Kakunin Modal…", "link": "https://make.wordpress.org/polyglots/2026/08/06/pte-request-for-kakunin-modal/", "description": "

PTE Request for Kakunin Modal for Contact Form 7

\n

Hello Polyglots,

\n

I am the plugin author for Kakunin Modal for Contact Form 7.

\n\nhttps://wordpress.org/plugins/kakunin-modal-for-contact-form-7/\n\n\n

I have submitted Japanese translations for the Stable and Development projects (48/48 strings) and would like to request PTE access so I can review and approve them. I am a native Japanese speaker.

\n

Please add my WordPress.org user as Project Translation Editor for the following locale:

\n\n #ja — @torigoedesign\n\n\n

Thank you!

\n

#editor-requests

", "id": 17103610, "pubDate": "Thu, 06 Aug 2026 14:22:41 GMT", "whenReceived": "Thu, 06 Aug 2026 15:40:57 GMT", "whenUpdated": "Thu, 06 Aug 2026 15:40:57 GMT", "likes": [], "metadata": { "wpPostId": 69346, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69342", "title": "PTE Request for Feedivo", "link": "https://make.wordpress.org/polyglots/2026/08/06/pte-request-for-feedivo/", "description": "

Hi Polyglots,

\n

I’m the plugin author of Feedivo. I have prepared a complete German
\ntranslation of the plugin and would like to be able to import and
\nvalidate it myself, so it stays in sync with every release.

\n

Plugin: Feedivo — https://wordpress.org/plugins/feedivo/
\nSlug: feedivo
\nTranslation project: https://translate.wordpress.org/projects/wp-plugins/feedivo/

\n

Please add the following WordPress.org user as Project Translation Editor:

\n\n #de_DE — @feedivo (@tobifjellner)\n\n\n

I’m a native German speaker and the author of the plugin. The translation
\nuses the informal “du” form, matching the de_DE locale, and follows the
\nGerman style guide and glossary. I’ll also take care of the readme
\nsub-projects so the plugin page is available in German.

\n

Thanks a lot for your time!

\n

#editor-requests

", "id": 17103611, "pubDate": "Thu, 06 Aug 2026 14:22:32 GMT", "whenReceived": "Thu, 06 Aug 2026 15:40:57 GMT", "whenUpdated": "Thu, 06 Aug 2026 20:45:30 GMT", "likes": [], "metadata": { "wpPostId": 69342, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "whenReceived": "Thu, 06 Aug 2026 14:18:06 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "guid": "https://make.wordpress.org/accessibility/?p=17591", "title": "One year of working on documentation about accessibility for WordPress", "link": "https://make.wordpress.org/accessibility/2026/08/06/one-year-of-working-on-documentation-about-accessibility-for-wordpress/", "description": "

At WordCamp Europe Torino ’24, Joe Dolson asked Rian Rietveld to review the documentation about accessibility on the WordPress.org website. What she found was that the information was hard to find, scattered all around the place, with duplicated and incomplete information.

\n\n\n\n

At WordCamp Basel ’25, we worked out a plan to improve the documentation for WordPress’ accessibility.

\n\n\n\n

Last year we centralized, reviewed and updated this documentation, creating one source of truth: The WP Accessibility Knowledge Base on wpaccessibility.org.

\n\n\n\n

The goal is for WordPress community to have consistant, easy to find, reliable, and up-to-date information about what is important to create sites, blocks, themes, admin functions, or plugins everyone can use.

\n\n\n\n

Thank you Kinsta, Human Made, GoDaddy and Aiwos for sponsoring Joe and Rian to work on this documentation.

\n\n\n\nLast year: Reorganize, review, update and extend\n\n\n\nAccessibility team Handbook\n\n\n\n

The Accessibility Team Handbook on WordPress.org now only contains information about the accessibility team, the WordPress accessibility coding standard and about how to contribute.

\n\n\n\n

The advantage of updating everything is that you get new insights. Instead of 7 working groups, the team now has 3 focus groups: The accessibility of WordPress, The accessibility-ready program and Documentation and education. With each group its own contact person.

\n\n\n\nTheme accessibility-ready guidelines\n\n\n\n

Amber Hinds and Joe Dolson updated the theme accessibility-ready guidelines. These new requirements aare now published in the WP Accessibility Knowledge Base.

\n\n\n\nWP Accessibility Knowledge Base\n\n\n\n

All information about accessibility itself, originally in the handbook, has been moved to the WP Accessibility Knowledge Base on wpaccessibility.org. The content is written in markdown and lives on the GitHub pages of the repository wp-a11y-docs, owned by the accessibility team. Many people helped getting this documentation out there, thank you!

\n\n\n\n\n\n\n\n

The WP Accessibility Knowledge Base now contains info about:

\n\n\n\n\nStart with accessibility, with an introduction to WCAG, 7 quick wins, the business case, how to get training and eduction and also our opinion about overlays.\n\n\n\nAccessibility-ready program, with the theme requirements, testing process and how to find accessibility-ready themes.\n\n\n\nStandards and best practice, for content & images, design & user experience, frontend code, web forms, legislation and how to document accessibility.\n\n\n\nTest for accessibility, about automated testing, checks for content, design and frontend, WordPress plugins for accessibility testing, how to test with a keyboard and with a screen reader and links to complete WCAG checklists.\n\n\n\nWordPress and Accessibility, about WordPress, WCAG and compliance, links to the accessibility team and team handbook and an overview of plugins that help support accessibility.\n\n\n\n\n

We are still in the process of updating and extending the content, but much of it is done or almost done.

\n\n\n\nWork in process\n\n\n\n

The Accessibility Handbook will move to a GitHub repository on the WordPress organisation later this year.

\n\n\n\n

When all the documentation in the Knowledge Base has been reviewed and updated, the relevant documentation will be copied to a new section called “Accessibility” on developer.wordpress.org. So, in fact, we return the updated info to wordpress.org, where it belongs and also will be easier to find.

\n\n\n\n

After this, all the old documentation about accessibility on make.wordpress.org needs to be updated to point to this new accessibility section.

\n\n\n\n

Proper documentation is an ongoing job, we need to keep updating, reviewing and extending. The web, WordPress itself, support for HTML, CSS and ARIA, assistive technology, the way people use the web, the use of AI, it all changes. It’s a work in progess.

\n\n\n\nHow can you help\n\n\n\n

Read what’s there, on wpaccessibility.org, and give us feedback. We are writing this for you, please let us know if you can understand and use it.

\n\n\n\n

WordCamps are the best. Last WordCamp Europe, at the contributor day, a table full of people reviewed the Knowledge Base and came back with useful feedback. When you are at a WordCamp contributor day, please join the accessibility table to give feedback on wpaccessibility.org.

\n\n\n\n

Request content. Do you need information about a specific topic? Are there discussions on how to handle a specific topic or component? Ask us for help and documentation, resources, or what else you need. Open an issue in the wp-a11y-docs GitHub repository with your request or ping @rianrietveld in WordPress Slack.

\n\n\n\n

Are you a core developer? Help us with examples, or point us to good examples to add to the docs.

\n\n\n\n

WordPress agencies: consider sponsoring Joe and Rian. Or give your developers, designers or content creators time to work on the documentation.

\n\n\n\n

But most off all: you can help us by using the documentation for your work, let’s make WordPress usable for everyone.

\n

#wp-a11y-docs

", "id": 17101483, "pubDate": "Thu, 06 Aug 2026 13:46:22 GMT", "whenReceived": "Thu, 06 Aug 2026 14:18:06 GMT", "whenUpdated": "Thu, 06 Aug 2026 14:18:06 GMT", "likes": [], "metadata": { "wpPostId": 17591, "wpSiteId": 29901991 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 06 Aug 2026 14:00:00 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69348", "title": "#uk_UA Hello Polyglots! I am…", "link": "https://make.wordpress.org/polyglots/2026/08/06/uk_ua-hello-polyglots-i-am/", "description": "

Hello Polyglots! I am the plugin author. Please add me as PTE for the Ukrainian locale for my plugin:

\n\nhttps://wordpress.org/plugins/catcode-delivery-with-nova-poshta-for-woocommerce/\n\n\n

GlotPress: – https://translate.wordpress.org/projects/wp-plugins/catcode-delivery-with-nova-poshta-for-woocommerce/

\n

Username: catcodestudio

\n

The full Ukrainian translation is already submitted and waiting (stable 120/120, readme 45/45). Ukrainian is our own working language — the plugin is built for Ukrainian shops using the Nova Poshta carrier. Thank you!

\n\n #uk (@tobifjellner)\n\n\n

#editor-requests

", "id": 17101074, "pubDate": "Thu, 06 Aug 2026 13:05:31 GMT", "whenReceived": "Thu, 06 Aug 2026 14:00:00 GMT", "whenUpdated": "Thu, 06 Aug 2026 15:40:57 GMT", "likes": [], "metadata": { "wpPostId": 69348, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed/", "whenReceived": "Thu, 06 Aug 2026 08:29:24 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed/", "guid": "https://make.wordpress.org/core/?p=125396", "title": "What’s new in Gutenberg 23.7? (05 August)", "link": "https://make.wordpress.org/core/2026/08/06/whats-new-in-gutenberg-23-7-05-august/", "description": "

“What’s new in 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.

\n\n\n\n\n\n

What’s New In
Gutenberg 23.7?

\n\n\n\n\n\n

Gutenberg 23.7 has been released and is available for download!

\n\n\n\n

Version 23.7 includes many improvements over features added with 23.6, with updates to the Block Editor, the new Gallery block’s dynamic mode, user control to enable the Global Styles inheritance UI, and a series of smaller visible editor layout fixes.

\n\n\n\n\nTry Gutenberg 23.7\n\n\n\n\nVarious editor improvements\n\n\n\n

Much of the 23.7 cycle has been focused on smaller visual editor improvements. Floated blocks no longer overlap sticky blocks, the empty block appender now sits in the right place inside blocks that capture their own toolbars, and the Pullquote block finally honors a custom line height in the editor so it matches the front end. Fixed device preview heights are also restored for the mobile and tablet views.

\n\n\n\n\n\n\n\nGallery block dynamic mode improvements\n\n\n\n

The new Gallery block dynamic mode that shipped in Gutenberg 23.6 had an ambiguous “Convert to images” toolbar button that didn’t describe what it actually did. That button has been renamed to “Detach”, and a modal appears to better explain to the user what happens when detaching images

\n\n\n\n\n\n\n\n\n\n\n\n\n\nOther Notable Highlights\n\n\n\n\nGlobal Styles inheritance UI. This experimental feature is now opt-in, and is enabled from the Gutenberg Experiments settings page (#80815).\n\n\n\nMath block: LaTeX errors stop interrupting you. Parse errors no longer fire on every keystroke — LaTeX input now uses ValidatedTextareaControl, so feedback is deferred until the field first loses focus and the per-keystroke screen reader announcement is gone (#80500).\n\n\n\nGrouped options across the form primitives. Combobox, Select, and SelectControl gain Group and GroupLabel subcomponents, so grouped options compose consistently across the item-popup families (#80574).\n\n\n\n\nChangelog\n\n\n\nEnhancements\n\n\n\n\nBase styles: Allow overriding focus ring color in outset-ring__focus. (80587)\n\n\n\nWidget Dashboard: Measure the header fit and document the chrome. (80423)\n\n\n\nWidget Primitives: Ship as a script module. (80149)\n\n\n\n\nComponents\n\n\n\n\nCombobox, Select, SelectControl: Add Group and GroupLabel. (80574)\n\n\n\nDataViews/Font Library: Give search fields a fixed width to stop layout shift. (80315)\n\n\n\nDataViewsPicker: Add Shift+Click range selection to the picker-table, picker-grid, and picker-activity layouts. (80413)\n\n\n\nEnhance sandbox component to accept sandbox prop. (69617)\n\n\n\nInput: Hide native spin controls for type=”number”. (80646)\n\n\n\nSearchControl: Render the suffix only if there’s one. (80356)\n\n\n\nUI: Add Autocomplete.Row primitive. (80490)\n\n\n\n\nBlock Library\n\n\n\n\nAdd Table of Contents end-to-end user story coverage. (80199)\n\n\n\nMath: Use ValidatedTextareaControl for LaTeX input. (80500)\n\n\n\n\nPost Editor\n\n\n\n\nAdd a responsiveEditingEnabled editor setting to hide the Responsive styles option. (80814)\n\n\n\n\nFont Library\n\n\n\n\nFix navigation page select font size to match DataViews. (80617)\n\n\n\n\nCollaboration\n\n\n\n\nRTC: Disable Quick Edit while a post is being edited. (80016)\n\n\n\n\nGlobal Styles\n\n\n\n\nExtract shared preset management from shadows and font sizes. (79810)\n\n\n\n\nBlock Editor\n\n\n\n\nReflect inherited Global Styles values in block inspector controls. (77894)\n\n\n\n\nBug Fixes\n\n\n\n\nBlock Editor: Fix floated blocks overlapping sticky blocks. (80749)\n\n\n\nUpdate view configuration API versioning. (80319)\n\n\n\nView config: Reject shape-mismatched merges, define empty-array semantics, strip nulls from appended members. (80571)\n\n\n\ncreateInterpolateElement: Handle unmatched closing tags gracefully. (80618)\n\n\n\n\nBlock Library\n\n\n\n\nAccount for non-lowercase VIDEO tag in render_block_core_video(). (80537)\n\n\n\nCover/Accordion: Exit on Enter. (77301)\n\n\n\nDynamic Gallery: Rename toolbar button to Detach and add a modal explaining what will happen. (80727)\n\n\n\nFix: Pullquote custom line height in the editor. (80586)\n\n\n\nGallery: Make dynamic mode conversion a single undo level. (80665)\n\n\n\nList Block: Preserve ordered type on indent. (75353)\n\n\n\nMedia Editor: Show a loading state while the cropped file loads. (80460)\n\n\n\nMedia: Remove the redundant __heicUploadSupport flag. (80452)\n\n\n\nNavigation: Fix missing ‘Add block’ option in Link UI when inside template parts. (78427)\n\n\n\nPlaylist: Shorten track toolbar button label. (80759)\n\n\n\nQuery Loop: Add translation context to the ‘Offset’ setting label. (80582)\n\n\n\nSocial Link: Fix stray closing tag in Tumblr icon markup. (80257)\n\n\n\n\nBlock Editor\n\n\n\n\nBackground image control: Remove duplicated focus ring. (80671)\n\n\n\nBlock Tools: Fix empty block appender position inside blocks that capture toolbars. (80592)\n\n\n\nFix cursor position during forward delete of empty blocks. (77525)\n\n\n\nFix preset round-trip test imports after preset utils consolidation. (80589)\n\n\n\nGlobal Styles panels: Fix wrong preset committed and shown when two color presets share a hex. (80497)\n\n\n\nGlobal Styles: Resolve link element styles in block inspector controls for blocks that are links. (80607)\n\n\n\nRTC: Prevent controlled block synchronization from intercepting undo. (80503)\n\n\n\nRich text: Remove tabIndex from editable elements again to fix shift+click selection. (80651)\n\n\n\nWriting flow: Extend block selections with shift+arrow when there is no native selection. (80687)\n\n\n\nWriting flow: Mark shift+click as a multi-selection gesture. (80286)\n\n\n\nWriting flow: Stop the page scrolling on caret moves within blocks taller than the viewport. (80708)\n\n\n\nRichText: Don’t apply input transform when there’s no onReplace. (80978)\n\n\n\nRichText: Fix paste handler crash when pasting files. (81010)\n\n\n\n\nPost Editor\n\n\n\n\nEditor: Leave undo to the browser in fields that handle their own undo. (80768)\n\n\n\nEditor: Restore fixed device preview height for mobile and tablet. (80271)\n\n\n\nMeta boxes: Match heading styles with Gutenberg panels. (80670)\n\n\n\nNotes: Capture the target block before saving a block-level note. (80690)\n\n\n\nNotes: Register the inline note format at import time. (80576)\n\n\n\nNotes: Report save success consistently from note actions. (80748)\n\n\n\nNotes: Sync the sidebar selection to the inline marker under the caret. (80610)\n\n\n\nPost Lock: Fix modal flipping to “Someone else has taken over” for a locked-out viewer. (79997)\n\n\n\nWrap notices in ThemeProvider with 0 corner radius. (79523)\n\n\n\niOS: Remove jumping hack, add typewriter. (74596)\n\n\n\n\nComponents\n\n\n\n\nDataForm: Stop card and details validation from hijacking focus. (80685)\n\n\n\nFix Root .prettierrc.js override issue. (80422)\n\n\n\nGradientPicker: Select by slug so two presets sharing a gradient keep their identity. (80554)\n\n\n\nStorybook: Fix Emotion jsxImportSource. (80426)\n\n\n\nToolsPanel: Migrate styles to an SCSS Module. (80445)\n\n\n\n\nClient Side Media\n\n\n\n\nFix upload hang when converting long animated GIFs: Decode only the first frame for still outputs. (80260)\n\n\n\nMedia: Stop forcing crossorigin on IMG tags in media templates. (80532)\n\n\n\nwp-build: Sync the page template preload field list with core-data. (80648)\n\n\n\n\nCollaboration\n\n\n\n\nNotes: Detach core’s mention kses filter in the baseline strip test. (80656)\n\n\n\nRTC: Compact during serialization. (80707)\n\n\n\n\nMedia\n\n\n\n\nMedia REST API: Backport sideload from URL path upload size check. (80659)\n\n\n\n\nGlobal Styles\n\n\n\n\nTheme JSON: Level block-level preset class specificity with :Where(). (80657)\n\n\n\n\nData Layer\n\n\n\n\nRTC: Preserve collaborators’ unsaved edits when another user saves. (79936)\n\n\n\n\nAccessibility\n\n\n\nBlock Library\n\n\n\n\nImprove the various Alignment controls props handling. (63696)\n\n\n\nNavigation: Fixes aria-expanded not updating on hover submenu inside overlay. (77563)\n\n\n\n\nPerformance\n\n\n\nBlock Editor\n\n\n\n\nRich text: Read the contentEditable attribute in ownsSelection to avoid forced layout. (80549)\n\n\n\nTry to fix typing performance regression. (80507)\n\n\n\n\nPost Editor\n\n\n\n\nEditor: Avoid unnecessary term re-fetches in FlatTermSelector. (80623)\n\n\n\n\nData Layer\n\n\n\n\nCore Data: Move EntitiesSavedState component out of editor (rebase of #71948). (80485)\n\n\n\n\nExperiments\n\n\n\nDashboard\n\n\n\n\nDashboard Widgets: Harden action href sanitization. (80510)\n\n\n\nDashboard Widgets: Sanitize help link hrefs. (80409)\n\n\n\n\nBlock Editor\n\n\n\n\nGlobal Styles: Put the inheritance UI behind a Gutenberg experiment. (80815)\n\n\n\n\nDocumentation\n\n\n\n\nAdd nvm use instructions to AGENTS.md. (80755)\n\n\n\nAdd progressive-discovery pattern for agent instructions and skills. (80650)\n\n\n\nAdded Missing Global Documentation in table-of-contents/index.php. (80442)\n\n\n\nDocs: Add missing file-level and class-level docblocks to WP_Icon_Collections_Registry. (80172)\n\n\n\nDocs: Clarify agent guidance discovery. (80753)\n\n\n\nDocs: Clarify getBlock behavior with inner block controllers. (80773)\n\n\n\nDocs: Expand the back-porting to WP Core guide. (80593)\n\n\n\nDocs: Require view configuration filter callbacks to return the container. (80642)\n\n\n\nDocs: Update iframe guidance for Gutenberg 23.6. (80629)\n\n\n\nTheme: Update Storybook admin color scheme examples. (80569)\n\n\n\nUI: Add dialog vs drawer design guidance. (80783)\n\n\n\nUpdate documentation for server-side view configuration filters. (80744)\n\n\n\nUsed link for URL in inline documentation. (80716)\n\n\n\n\nCode Quality\n\n\n\n\nESLint: Add missing not-recommended components to denylist. (80754)\n\n\n\nFix: Update webpack-dev-server to ^5.2.1 to help with dep alerts. (80347)\n\n\n\nGitHub workflows: Fix changelog checks for forked PRs. (80538)\n\n\n\nInteractivity API: Refactor directives into self-registering modules. (79975)\n\n\n\nRTC: Use array_any() for newer-compaction check in polling sync server. (80522)\n\n\n\nRTC: Use str_contains() in WP_Sync_Config. (80476)\n\n\n\nStorybook: Build the resolve specifier as a URL-style string. (80416)\n\n\n\nTools: Resolve dependencies independently of the node_modules layout. (80414)\n\n\n\n\nComponents\n\n\n\n\nAutocomplete: Reference the suggestions list with aria-controls and aria-haspopup. (80403)\n\n\n\nExternalLink: Use shared focus ring mixin. (80573)\n\n\n\nMake useSelectionProps hook layout agnostic. (80677)\n\n\n\nMigrate Disabled to SCSS module. (80643)\n\n\n\nMigrate FormTokenField to SCSS module. (80472)\n\n\n\nMigrate SearchControl to SCSS module. (80474)\n\n\n\nPackages: Update date-fns to 4.4.0. (80763)\n\n\n\nTheme: Update Color.js to 0.7.1. (80762)\n\n\n\nTheme: Update colorjs.io dependency and drop bug workaround. (80272)\n\n\n\nUI: Improve component code readability in Storybook by using arrays for children. (80352)\n\n\n\ntheme: Disallow src in published package. (80213)\n\n\n\n\nBlock Library\n\n\n\n\nGuards against error throwing attribute values. (80558)\n\n\n\nMake editableRoot a private block setting rather than a public support. (80820)\n\n\n\nMisc fixes for WordPress-Develop 7.0 merges. (75985)\n\n\n\nPage List: Use null coalescing operator for parentPageID attribute. (80728)\n\n\n\nRemove redundant @jest-environment jsdom pragma and lint against it. (80676)\n\n\n\nRemove unnecessary __next40pxDefaultSize props from form controls. (80540)\n\n\n\nTable of Contents: Use str_contains() instead of strpos() check. (80418)\n\n\n\nTabs : Remove default paragraph from tab-panel template. (80565)\n\n\n\n\nBlock Editor\n\n\n\n\nDuotone: Dedupe duotone utils into global-styles-engine. (80598)\n\n\n\nReduce duplicated preset utility implementations. (80245)\n\n\n\nRefactor ‘URLInput’ to function component. (80721)\n\n\n\n\nPost Editor\n\n\n\n\nIcons: Validate SVG icons include viewBox. (80273)\n\n\n\nNotes: Cancel in-flight hover highlight when focus leaves a note thread. (80752)\n\n\n\n\nData Layer\n\n\n\n\nPackages: Update memize to 2.1.1. (80764)\n\n\n\n\nGlobal Styles\n\n\n\n\nRename unit test files and drop .spec.js suffix. (80711)\n\n\n\n\nSite Editor\n\n\n\n\nEdit Site: Replace Theme usage in canvas loader with CSS. (80688)\n\n\n\n\nCollaboration\n\n\n\n\nMove real-time collaboration code to lib/experimental/collaboration. (80469)\n\n\n\n\nTools\n\n\n\n\nDocs: Update the release form screenshot for GitHub’s new Release label UI. (80567)\n\n\n\nRelease: Require a working GitHub CLI for cherry-picking. (80568)\n\n\n\n\nBuild Tooling\n\n\n\n\nBuild: Add independent react-18 vendor package. (80367)\n\n\n\nBuild: Handle project paths containing spaces in dev script. (80519)\n\n\n\nComponents: Skip polymorphism prop typings on intersection. (80364)\n\n\n\nDependencyExtractionWebpackPlugin: Include extracted styles in the asset version hash. (80601)\n\n\n\nReact 19: Add end-to-end compat test for boolean inert attribute. (80397)\n\n\n\nResolve Prettier explicitly for isolated layout. (80529)\n\n\n\nStorybook: Remove Emotion as JSX import source. (80647)\n\n\n\nWP Build: Avoid infinite worker build loop. (80361)\n\n\n\nImprove pre-flight npm access checks. (80334)\n\n\n\n\nTesting\n\n\n\n\nJest: Fix ignore pattern for TypeScript declaration files. (80737)\n\n\n\nJest: Update to v30 (breaking). (80767)\n\n\n\nOnly use Flakiness.io in canonical Gutenberg repo. (80816)\n\n\n\nPerf Tests: Fix ‘Selecting blocks’ metric reporting 0 ms. (80524)\n\n\n\nRTC: Fix deleted-user test on multisite. (80463)\n\n\n\nSite Editor: Add end-to-end coverage for view configuration extensibility. (80577)\n\n\n\n\nVarious\n\n\n\nComponents\n\n\n\n\nBase Styles: Remove accent color parameter from input-control. (80595)\n\n\n\nRemove private Theme component. (80691)\n\n\n\n\nFirst-time contributors\n\n\n\n

The following PRs were merged by first-time contributors:

\n\n\n\n\n@dilipom13: Meta boxes: Match heading styles with Gutenberg panels. (80670)\n\n\n\n@faisalahammad: Editor: Restore fixed device preview height for mobile and tablet. (80271)\n\n\n\n@nickchomey: Interactivity API: Refactor directives into self-registering modules. (79975)\n\n\n\n\nContributors\n\n\n\n

The following contributors merged PRs in this release:

\n\n\n\n

@aaronrobertshaw @adamsilverstein @aduth @andrewserong @chriszarate @ciampo @CookieDarb @DarkMatter-999 @desrosj @dhananjaykuber @dilipom13 @dpmehta @ellatrix @enejb @faisalahammad @getdave @himanshupathak95 @i-am-chitti @im3dabasia @Imran92 @jeryj @jorgefilipecosta @jsnajdr @juanfra @Kgupta62 @MaggieCabrera @Mamaduka @manzoorwanijk @maxschmeling @mirka @Mustafabharmal @nickchomey @noruzzamans @ntsekouras @oandregal @obenland @ocean90 @peterwilsoncc @ramonjd @retrofox @scruffian @shail-mehta @shekharnwagh @shimotmk @simison @sirreal @Soean @t-hamano @westonruter @yashjawale

\n\n\n\n

Props to @mamaduka for reviewing.

\n\n\n\n

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

", "id": 17093788, "pubDate": "Thu, 06 Aug 2026 07:34:42 GMT", "whenReceived": "Thu, 06 Aug 2026 08:29:24 GMT", "whenUpdated": "Thu, 06 Aug 2026 08:29:24 GMT", "likes": [], "metadata": { "wpPostId": 125396, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 06 Aug 2026 02:10:47 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69338", "title": "PTE Request for WordPress.org, Theme…", "link": "https://make.wordpress.org/polyglots/2026/08/06/pte-request-for-wordpress-org-theme/", "description": "

PTE Request for WordPress.org, Theme Directory, and Plugin Directory (bn_BD)

\n

Hello Polyglots Team,

\n

I would like to request Project Translation Editor (PTE) permissions for the following projects in the Bengali (bn_BD) locale:

\n\nWordPress.org (Main Site): https://translate.wordpress.org/locale/bn/default/meta/wordpress-org/\n\nWordPress Theme Directory: https://translate.wordpress.org/locale/bn/default/meta/themes/\n\nWordPress Plugin Directory: https://translate.wordpress.org/locale/bn/default/meta/plugins-v3/\n\n\n

I have been actively contributing Bengali translations and would like to help maintain these projects. These are some of the most important parts of WordPress.org, used daily by millions of users, theme authors, and plugin developers.

\n

I want to help ensure that new strings are translated accurately, consistently, and naturally in Bengali, while also helping reduce the review backlog by reviewing translations more promptly.

\n\n #bn_BD\n\n\n

Thank you for your time and consideration.

\n

#editor-requests

", "id": 17090240, "pubDate": "Thu, 06 Aug 2026 01:46:36 GMT", "whenReceived": "Thu, 06 Aug 2026 02:10:47 GMT", "whenUpdated": "Thu, 06 Aug 2026 07:14:56 GMT", "likes": [], "metadata": { "wpPostId": 69338, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69334", "title": "Title: PTE Request for Homepage…", "link": "https://make.wordpress.org/polyglots/2026/08/06/title-pte-request-for-homepage/", "description": "

Title: PTE Request for Homepage Popup Notice & xiaochen – Auto Writer & Comment Reply
\nďťż
\nHello Polyglots,
\nďťż
\nI am the author of the plugin Homepage Popup Notice & xiaochen – Auto Writer & Comment Reply. I have suggested translations for the following locale(s) and would like to request Project Translation Editor (PTE) status to approve and maintain them.
\nďťż
\nPlugin: https://wordpress.org/plugins/homepage-popup-notice/
\nPlugin: https://wordpress.org/plugins/xiaochen-auto-writer-comment-reply/
\nďťż

\n\n #zh_CN @tsxcc \n\n\n

#editor-requests

", "id": 17090241, "pubDate": "Thu, 06 Aug 2026 01:19:18 GMT", "whenReceived": "Thu, 06 Aug 2026 02:10:47 GMT", "whenUpdated": "Thu, 06 Aug 2026 07:14:56 GMT", "likes": [], "metadata": { "wpPostId": 69334, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69329", "title": "PTE Request for SEO’n’AI – AI Image check&mark", "link": "https://make.wordpress.org/polyglots/2026/08/05/pte-request-for-seonai-ai-image-checkmark/", "description": "

Hello Polyglots,

\n

I am the plugin author of SEO’n’AI – AI Image check&mark. We have a complete German translation ready to import, and I would like to become PTE for my plugin so I can approve it. As a native German speaker from Austria, please add my WordPress.org user Gwalter75 as translation editor for the following locales:

\n

Plugin URL: https://wordpress.org/plugins/seonai-ai-image-checkmark/

\n\n #de_DE (@tobifjellner)\n\n #de_AT\n\n #de_CH\n\n\n

Thanks a lot and best regards,
\nGerald

\n

#editor-requests

", "id": 17085417, "pubDate": "Wed, 05 Aug 2026 21:05:04 GMT", "whenReceived": "Wed, 05 Aug 2026 21:06:40 GMT", "whenUpdated": "Thu, 06 Aug 2026 20:45:30 GMT", "likes": [], "metadata": { "wpPostId": 69329, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69320", "title": "PTE Request for wp-410", "link": "https://make.wordpress.org/polyglots/2026/08/05/pte-request-for-wp-410/", "description": "

I am the plugin author for HTTP 410 (Gone) responses. We have a number of great translation editors that we’d like to be able to approve translation for our plugin(s). Please add the following WordPress.org users as translation editors for their respective locales:

\n\nhttps://wordpress.org/plugins/wp-410/\n\n\n\n #en_GB – @xandercalvert (@tobifjellner)\n\n #it_IT – @xandercalvert\n\n\n

— ja – @xandercalvert

\n

If you have any questions, just comment here. Thank you!

\n

#editor-requests

", "id": 17085418, "pubDate": "Wed, 05 Aug 2026 19:30:22 GMT", "whenReceived": "Wed, 05 Aug 2026 21:06:40 GMT", "whenUpdated": "Thu, 06 Aug 2026 20:45:30 GMT", "likes": [], "metadata": { "wpPostId": 69320, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69316", "title": "Hej!", "link": "https://make.wordpress.org/polyglots/2026/08/05/hej/", "description": "

Jag skulle vilja ansÜka om att bli Project Translation Editor (PTE) fÜr den svenska Üversättningen av pluginet GiveWP, sü att jag kan godkänna mina egna och teamets Üversättningar direkt.

\n\n #sv_SE \n\n\n

Plugin-länk: https://wordpress.org/plugins/give/

\n

Min WordPress.org-profil: @cremaninnovation

\n

Tack pĂĽ fĂśrhand!
\nChrister

\n

#editor-requests

", "id": 17085419, "pubDate": "Wed, 05 Aug 2026 19:30:11 GMT", "whenReceived": "Wed, 05 Aug 2026 21:06:40 GMT", "whenUpdated": "Wed, 05 Aug 2026 21:06:40 GMT", "likes": [], "metadata": { "wpPostId": 69316, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69314", "title": "PTE Request for Embed Privacy", "link": "https://make.wordpress.org/polyglots/2026/08/05/pte-request-for-embed-privacy/", "description": "

I am a long term advanced user of the plugin Embed Privacy on multiple sites, and being a native Danish speaker, I would like to be able to approve Danish translations for that plugin.

\n

I already use these translations in production, so they are being tested in real life on a regular basis.

\n

Please add the following WordPress.org users as translation editors for their respective locales:

\n

Link to plugin

\n\nhttps://wordpress.org/plugins/embed-privacy/\n\n\n

List of locale tags and the username(s) requested for PTE.

\n\n #da_DK – @oldrup (@tobifjellner)\n\n\n

#editor-requests

", "id": 17085420, "pubDate": "Wed, 05 Aug 2026 19:29:56 GMT", "whenReceived": "Wed, 05 Aug 2026 21:06:40 GMT", "whenUpdated": "Wed, 05 Aug 2026 21:06:40 GMT", "likes": [], "metadata": { "wpPostId": 69314, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/plugins/feed/", "whenReceived": "Wed, 05 Aug 2026 17:00:46 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/plugins/feed/", "guid": "https://make.wordpress.org/plugins/?p=5112", "title": "Plugins Directory Release Process Issues", "link": "https://make.wordpress.org/plugins/2026/08/05/plugins-directory-release-process-issues/", "description": "

The Plugins Team is aware of an issue currently affecting plugin releases and is actively investigating it.

\n\n\n\n

At this time, newly released plugin ZIP files are not being generated as expected. We are also aware that some users are experiencing issues accessing SVN.

\n\n\n\n

We will provide updates by editing this post as more information becomes available.

\n\n\n\n

Thank you for your patience while we work to resolve the problem.

\n\n\n\nTimeline\n\n\n\n\n5 August, 15:15–15:54 UTC: Multiple plugin authors reported the issue in the #pluginreview Slack channel and via email.\n\n\n\n5 August, 16:07 UTC: The Meta Team confirmed they were aware of the issue and escalated it to the Systems Team for investigation.\n\n\n\n5 August, 16:54 UTC: The Plugins Team deployed an automated email response to help manage the high volume of incoming messages and direct users to this status post for updates.\n\n\n\n5 August, 16:56 UTC: Systems and Meta confirmed that the zip generation is fixed.\n\n\n\n5 August, 17:09 UTC: Still investigating the SVN issues. A fix was applied, we are verifying it.\n\n\n\n5 August, 17:39 UTC: Several users reported that this was solved.\n\n\n\n\n

To help us keep communication channels available for new reports and other requests, please do not email the Plugins Team about this issue. We will continue to update this post as more information becomes available.

\n\n\n\nDone!\n\n\n\n

This issue has now been resolved. Sorry for the inconvenience, and thank you for bringing it to our attention.

", "id": 17079823, "pubDate": "Wed, 05 Aug 2026 16:54:29 GMT", "whenReceived": "Wed, 05 Aug 2026 17:00:46 GMT", "whenUpdated": "Wed, 05 Aug 2026 18:41:58 GMT", "likes": [], "metadata": { "wpPostId": 5112, "wpSiteId": 31760039 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Wed, 05 Aug 2026 17:00:49 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125339", "title": "WordPress 7.1 Release Candidate Phase", "link": "https://make.wordpress.org/core/2026/08/05/wordpress-7-1-release-candidate-phase/", "description": "

The 7.1 branch was created on 08/10/2026 09:34:18 PM and trunk was made open for 7.2 alpha at 08/10/2026 11:06:18 PM.

\n\n\n\n\n

Now that WordPress 7.1 has entered the Release Candidate phase, the following policies are in place.

\n\n\n\n

These policies mainly cover how and when Core committers can commit. For non-committing contributors, this post may help explain why Core committers make certain decisions.

\n\n\n\nCommitting to Trunk\n\n\n\n

In order to not interfere with ongoing efforts to improve github actions, branching has been delayed until early next week. This post will be updated after the branch is created.

\n\n\n\n

As a result, all commits to trunk will require double sign-off by two core committers until the 7.1 branch is created.

\n\n\n\n

The dev-feedback keyword should be used to request a second committer’s review, dev-reviewed should be added to indicate a second committer has reviewed and approved the commit to trunk. Commits to the test suite do not require double sign-off. Only committers should add the dev-feedback and dev-reviewed keywords.

\n\n\n\nString Freeze\n\n\n\n

RC1 release marks the hard string freeze point of the release cycle. While this normally means the Polyglots team can begin translating strings from the upcoming release into their local language, a version-specific branch is required. As a result, strings will not be available for translation until the 7.1 branch is created.

\n\n\n\n

Despite this, the normal rules for hard string freeze will be followed:

\n\n\n\n\nNo new strings are permitted. Exceptions can be made for critical strings (the About page, for example) provided they are properly tagged with the i18n-change keyword in Trac and the Polyglot team is made aware.\n\n\n\nExisting strings can be removed and/or duplicated if needed.\n\n\n\n\n

Seek guidance from the Polyglots team reps for any strings reported as buggy. A buggy string is one that can not be translated to all languages in its current form. 

\n\n\n\nTickets on the WordPress 7.1 milestone\n\n\n\n

Only two types of tickets may be placed on/remain on the 7.1 milestone:

\n\n\n\n\nRegressions: bugs that have been introduced during the WordPress 7.1 development cycle, either to existing or new features.\n\n\n\nTest suite expansion: tests can be committed at any time without regard to code or string freezes. This can cover either new or existing features.\n\n\n\n\nBumping Trunk to WordPress 7.2-alpha\n\n\n\n

After the 7.1 branch is created, this post will be updated and a @committers announcement will be made in slack informing everyone that trunk is open for commits related to the next version of the software.

\n\n\n\n

Props @joedolson for peer review.

\n\n\n\n

\n

#7-1

", "id": 17079824, "pubDate": "Wed, 05 Aug 2026 15:39:08 GMT", "whenReceived": "Wed, 05 Aug 2026 17:00:49 GMT", "whenUpdated": "Mon, 10 Aug 2026 23:22:09 GMT", "likes": [], "metadata": { "wpPostId": 125339, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://wordpress.org/news/podcast/feed/", "whenReceived": "Wed, 05 Aug 2026 16:32:27 GMT", "items": [ { "feedUrl": "https://wordpress.org/news/podcast/feed/", "guid": "https://wordpress.org/news/?p=21248", "title": "WordPress 7.1 Release Candidate 1", "link": "https://wordpress.org/news/2026/08/wordpress-7-1-release-candidate-1/", "description": "

The first Release Candidate (“RC1”) for WordPress 7.1 is ready for download and testing!

\n\n\n\n

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

\n\n\n\n

WordPress 7.1 RC1 can be tested using any of the following methods:

\n\n\n\nPluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the RC1 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command:
wp core update --version=7.1-RC1WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser.  No setup required – just click and go! \n\n\n\n

The scheduled final release date for WordPress 7.1 is August 19, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who contributes by testing!

\n\n\n\n

Please continue checking the Make WordPress Core blog for 7.1-related posts in the coming weeks for more information.

\n\n\n\nWhat’s in WordPress 7.1 RC1?\n\n\n\n

WordPress 7.1 RC1 contains more than 145 updates and fixes since the Beta 4 release, including 57 in the Editor and 88 in Core.

\n\n\n\n

For an overview of what’s new in WordPress 7.1, read the Beta 1 announcement and the WordPress 7.1 Dev Notes. For a comprehensive summary, see the WordPress 7.1 Field Guide.

\n\n\n\n

You can also explore the technical details of all issues addressed since Beta 4 using the links below:

\n\n\n\n\nGitHub commits for 7.1 since July 29, 2026\n\n\n\nClosed Trac tickets for 7.1 since July 29, 2026\n\n\n\n\nNew Features since Beta 1\n\n\n\n\nIcons API: New APIs for registering icons and icon collections in Core, ready for plugins to extend.\n\n\n\nSpeculative loading configuration: Speculative loading defaults can now be configured via environment variables and constants.\n\n\n\nEmail notifications for @mentions: Email notifications have been introduced when mentioned in a Note.\n\n\n\nShareable Revisions: Share links to specific revisions for faster collaboration.\n\n\n\n\n

Want to look deeper into the details and technical notes for this release? These tickets and pull requests are just some of the latest updates:

\n\n\n\n\n#GB-79839: Apply globally: choose which modified block styles to apply\n\n\n\n#GB-80814: New responsiveEditingEnabled editor setting to hide responsive styles\n\n\n\n#GB-80107: Tabs: toolbar buttons to reorder tabs\n\n\n\n#GB-80046: DataViews: shift-click range selection\n\n\n\n#65636: Preload REST API requests fetched on editor load\n\n\n\n#65613: Notes are excluded from comment feed queries\n\n\n\n#65491: KSES allows the autofocus attribute on dialog elements\n\n\n\n#65517: Multisite upload limits are enforced when sideloading media from a URL\n\n\n\n#62757: Update the jQuery UI library to version 1.14.2\n\n\n\n\nHow you can contribute\n\n\n\n

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

\n\n\n\nGet involved in testing\n\n\n\n

Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. 

\n\n\n\n

Your help testing the WordPress 7.1 RC1 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.1.

\n\n\n\nUpdate your theme or plugin\n\n\n\n

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.

\n\n\n\n

Thanks for continuing to test your themes and plugins with the WordPress 7.1 beta releases. With RC1, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 7.1.

\n\n\n\n

If you find compatibility issues, please post detailed information to the support forum.

\n\n\n\nTest on your hosting platforms\n\n\n\n

Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue.

\n\n\n\n

Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here. Thank you to all web hosts who help test WordPress!

\n\n\n\n

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

\n\n\n\nAn RC1 haiku\n\n\n\n

A candidate stands
the desert sun tests its strength
Arizona waits

\n\n\n\n

Props to @krupajnanda, @annezazu,
@amykamala, @wildworks and @masteradhoc for collaboration and review

\n\n\n\n\nJoin us for the launch of WordPress 7.1 at WordCamp US 2026, August 16–19.", "id": 17079099, "pubDate": "Wed, 05 Aug 2026 15:37:33 GMT", "whenReceived": "Wed, 05 Aug 2026 16:32:27 GMT", "whenUpdated": "Wed, 05 Aug 2026 16:32:27 GMT", "likes": [], "metadata": { "wpPostId": 21248, "wpSiteId": 14607090 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Wed, 05 Aug 2026 15:19:39 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124988", "title": "WordPress 7.1 Field Guide", "link": "https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/", "description": "

This guide outlines major developer features and breaking changes in 7.1 and is published during the Release Candidate phase to help inform WordPress extenders, Core developers, and everyone else interested in the latest WordPress development.

\n\n\n\n

There are more than 310 Core Trac tickets included in WordPress 7.1, over 100 of which are enhancements and feature requests, and more than 180 bug fixes. This release includes 40+ tickets focused on the Editor, with the most attention going to accessibility (46), UI (40), and administration (28) focuses. Additionally, this release includes almost 600 enhancements and more than 630 bug fixes, coming from Gutenberg.

\n\n\n\n

A quick search of the diff between 7.0.2 and the current trunk (7.1-beta4) reveals 20 new hooks (19 filters and 1 action), 1480 total files changed with 88163 insertions and 18601 deletions. Kudos to everyone who contributed to the 7.1 release, in any way, shape, or form.

\n\n\n\n

Below is a breakdown of the most important developer-related changes included in WordPress 7.1.

\n\n\nMediaClient-side media processingMedia libraryAccessibilityAdministrationAccessible tooltips in coreAbilities APIGlobal stylesSVG Icon APIDataViews, DataForm, and View Config APIsEditorNew Block SupportEnforced iframed editorEditor componentsDesign SystemPersistent Admin BarExternal librariesOther updatesBut wait, there’s more!What changes didn't make the 7.1 releaseClassic blockReal-time collaboration\"On This Day\" widgetMerge proposals\n\n\n\nMedia\n\n\n\n

WordPress 7.1 continues the modernisation of media workflows across the editor, REST API, and Media Library. The release introduces client-side processing capabilities, improves the handling and registration of image sizes, and changes the default Media Library browsing experience.

\n\n\n\nClient-side media processing\n\n\n\n

New client-side media processing APIs allow supported image operations to happen in the browser before a file is uploaded. Related REST API changes support validating image dimensions, selecting size-aware encoding quality, and registering a sideloaded file for multiple image sizes.

\n\n\n\n\nClient-Side Media Processing in WordPress 7.1\n\n\n\n\n

Related tickets:

\n\n\n\n\n#64798 — REST API: Add dimension validation to sideload endpoint\n\n\n\n#65262 — REST API: expose size-aware encode quality on attachment responses\n\n\n\n#65481 — REST API: Support registering one sideloaded file under multiple image sizes\n\n\n\n\nMedia library\n\n\n\n

Infinite scrolling is enabled by default in the Media Library grid, with a per-user option to restore the previous pagination behaviour. The release also includes fixes for upload counts, duplicate caption IDs, and other media-management details.

\n\n\n\n\nMedia Library infinite scrolling is now enabled by default, with a per-user opt-out\n\n\n\n\n

Other media changes:

\n\n\n\n\n#65053 – Correct the media-upload count when uploading multiple files from the post editor\n\n\n\n#65315 – Prevent duplicate figcaption IDs when the same image has different captions\n\n\n\n\n\n\nAccessibility\n\n\n\n

WordPress 7.1 includes accessibility improvements across administration screens, list tables, setup flows, widgets, navigation, and editor-related interfaces. The changes improve semantics, keyboard and pointer interaction, focus behaviour, contrast, and the presentation of contextual information.

\n\n\n\nAdministration\n\n\n\n

Administration improvements make hierarchical relationships and table structure clearer to assistive technologies. They also refine focus behaviour, controls, contrast, and interaction patterns across several screens.

\n\n\n\n\nPost list tables row headers changed\n\n\n\n\nAccessible tooltips in core\n\n\n\n

WordPress 7.1 introduces a shared mechanism for accessible name and informational tooltips. Core now uses this mechanism in selected interfaces, giving developers a consistent pattern for presenting supplementary information without relying on inaccessible title attributes or pointer-only interactions.

\n\n\n\n\nIntroducing name and informational tool tips in WordPress 7.1\n\n\n\n\n\n#51006 — Add a mechanism for accessible tooltips in core\n\n\n\n#55343 — Add Tooltip to “Remember Me” (WP Login Form)\n\n\n\n#50921 — Consider adding tooltips for metabox order buttons\n\n\n\n\n

Other accessibility improvements:

\n\n\n\n\n#64932 – Make subpage hierarchy in post list tables accessible.\n\n\n\n#65027 – Add IDs to section titles generated by the Settings API\n\n\n\n#65250 – Correct mouse interaction for the first submenu item when “Collapse Menu” is enabled\n\n\n\n#65382 – Improve admin colour scheme contrast for the editor chrome.\n\n\n\n#65454 – Improve accessibility of setup-config.php and install.php\n\n\n\n#47670 – Fix the accessibility problem caused by multiple RSS widgets\n\n\n\nImproving visibility, contrast, layout, and overall accessibility in #65419, #65530, #65532, #65630 and more.\n\n\n\n\n\nAccessibility Improvements in WordPress 7.1\n\n\n\n\n\n\nAbilities API\n\n\n\n

WordPress 7.1 builds on the Abilities API introduced in WordPress 6.9, making abilities easier to discover, expose, validate, and integrate with external clients. The release adds filtering to wp_get_abilities(), execution lifecycle hooks, a unified public exposure flag, client-compatible JSON Schema preparation, and several smaller API refinements.

\n\n\n\n\nJSON Schema preparation for client compatibility in WordPress 7.1\n\n\n\n\n\nFiltering registered abilities with wp_get_abilities() in WordPress 7.1\n\n\n\n\n\nNew execution lifecycle filters for the Abilities API in WordPress 7.1\n\n\n\n\n\nA unified public exposure flag for Abilities in WordPress 7.1\n\n\n\n\n\nAbilities API improvements in WordPress 7.1\n\n\n\n\n\n\nGlobal styles\n\n\n\n

WordPress 7.1 expands the styling tools available to block and theme developers, with responsive style variations, configurable viewports, additional interaction states, and text-shadow support. These changes give themes and blocks more expressive styling options while keeping their configuration within the Global Styles system.

\n\n\n\n\nResponsive block styles and configurable viewports in WordPress 7.1\n\n\n\n\n\nPseudo and custom style states in WordPress 7.1\n\n\n\n\n\nText Shadow Support in Global Styles\n\n\n\n\n\nSVG Icon API\n\n\n\n

Starting with WordPress 7.1, the SVG Icon API provides a standardised way to register and render custom icons in WordPress.

\n\n\n\n\nRegistering and rendering SVG icons in WordPress 7.1\n\n\n\n\nDataViews, DataForm, and View Config APIs\n\n\n\n

The DataViews and DataForm APIs continue to mature in WordPress 7.1, alongside new View Config capabilities for controlling Site Editor screens. Developers can use the expanded APIs to customize data-driven interfaces and filter which views and layouts are available in supported editor contexts.

\n\n\n\n\nFiltering Site Editor Screens in WordPress 7.1\n\n\n\n\nEditor\n\n\n\n

WordPress 7.1 includes a broad collection of editor improvements spanning block behaviour, extensibility APIs, interface components, styling tools, and the editing environment itself. The sections below highlight the changes most likely to affect block, theme, and plugin developers.

\n\n\n\n\nNew Block Support\n\n\n\n

WordPress 7.1 adds block support for background gradients and minimum width, allowing blocks to opt into these design controls through their metadata. The release also improves the Custom HTML block by allowing supported blocks to remain editable inside its preview.

\n\n\n\n\nNew Block Support in WordPress 7.1: Background Gradient (background.gradient)\n\n\n\n\n\nNew Block Support in WordPress 7.1: Minimum Width\n\n\n\n\n\nEditable blocks inside the Custom HTML block\n\n\n\n\n\nEnforced iframed editor\n\n\n\n

WordPress 7.1 completes the move to an iframe-based post editor, including for sites that register legacy meta boxes. This creates a more consistent editing environment, but plugins that rely on reaching across the editor document boundary should review their JavaScript and CSS for compatibility.

\n\n\n\n\nIframed Editor Changes in WordPress 7.1\n\n\n\n\nEditor components\n\n\n\n

The editor component library receives new features, refinements, and API updates in WordPress 7.1. Developers building editor interfaces should review the component changes for new capabilities, updated behaviour, and any migration considerations.

\n\n\n\n\nEditor components updates in WordPress 7.1\n\n\n\n\n\nMiscellaneous Editor Changes in WordPress 7.1\n\n\n\n\nDesign System\n\n\n\n

WordPress 7.1 introduces a theming foundation for the WordPress Design System. The new approach uses design tokens and shared styles to make interfaces more consistent while giving supported environments a structured way to apply different visual themes.

\n\n\n\n\nDesign System Theming in WordPress 7.1\n\n\n\n\nPersistent Admin Bar\n\n\n\n

The WordPress toolbar now remains available while navigating supported editor screens, creating a more consistent path between the front end, administration area, Site Editor, and Block Editor. Developers extending the toolbar should review how their items behave across these contexts and during client-side navigation.

\n\n\n\n\nConsistent navigation in WordPress 7.1 with persistent toolbar\n\n\n\n\nExternal libraries \n\n\n\n

WordPress 7.1 updates bundled third-party dependencies to improve compatibility, maintenance, and security. The most notable change is the update to jQuery UI 1.14.2, which may require testing for plugins that depend on jQuery UI behaviour or styling.

\n\n\n\n\njQuery UI updated to 1.14.2 in WordPress 7.1\n\n\n\n\nOther updates\n\n\n\n

Several developer-facing changes in WordPress 7.1 do not fall under any of the larger feature areas but may still affect existing integrations. These include adjustments to notification filtering and other focused API or behavioural changes.

\n\n\n\n\nThe notify_post_author filter now has the final say on post author notifications\n\n\n\n\nBut wait, there’s more!\n\n\n\n

7.1 offers so much more! More than 180 Core bugs, over 630 Gutenberg bugs, 100 enhancements and feature requests, and more than 20 blessed tasks have been marked as fixed in WordPress 7.1.

\n\n\n\n

The following highlights call attention to smaller changes that may affect integrations, expected return values, generated markup, compatibility, or established developer workflows:

\n\n\n\n

AI – #65504 – AI Client – updates execute_abilities() to mirror has_ability_calls() by checking is_ability_call() before executing, and adds regression coverage for mixed ability and non-ability calls.

\n\n\n\n

Comments – #65392 – “Show more comments” fails for comment types other than comment

\n\n\n\n

Editor and blocks:

\n\n\n\n\n#64838 – Prevent block pseudo-state styles from being applied to the default state\n\n\n\n#65039 – Add context to _doing_it_wrong() messages in WP_Block_Type_Registry::register()\n\n\n\n#65373 – Query Loop block: add an option to exclude the current post\n\n\n\n\n

Formatting and compatibility – #42517 – Make sure get_file_data() recognises headers prefixed by a <? tag.

\n\n\n\n

Login, installation, and multisite – #65506 – Fix incorrect HTTP URLs in multisite signup and activation when SSL is enabled

\n\n\n\n\n\n\n\n\n\n

Privacy

\n\n\n\n\n#44498 – Run _wp_personal_data_cleanup_requests() on cron\n\n\n\n#44723 – Return the WP_User_Request user ID as the documented type\n\n\n\n\n

REST API and XML

\n\n\n\n\n#65536 – XML-RPC: fix the argument mismatch in _multisite_getUsersBlogs\n\n\n\n#65670 – Prevent WP_REST_Attachments_Controller::get_attachment_filesize() from failing on non-integer metadata\n\n\n\n\n

Themes and templates

\n\n\n\n\n#42513 – Improve WP_Theme::get_post_templates() performance for large themes\n\n\n\n#64848 – Prevent implicit coercion in WP_Theme_JSON::to_ruleset()\n\n\n\n#65049 – Templates: add a date field\n\n\n\n\nWhat changes didn’t make the 7.1 release\n\n\n\n

Not every feature explored during the release cycle was ultimately included in WordPress 7.1. The following initiatives were deferred, changed direction, or remained experimental, giving contributors more time to validate their design and implementation before they reach Core.

\n\n\n\n\n

… as sometimes what we don’t add is more valuable than what we do.

\nAnne McCarthy in #7-1-release-leads\n\n\n\n\nRoadmap to 7.1\n\n\n\n\nClassic block\n\n\n\n

An initial proposal would have hidden the Classic block from the inserter for new content while preserving existing instances. After further discussion and testing, the change was reverted, so the Classic block remains available in WordPress 7.1.

\n\n\n\n\nHiding the Classic block from the inserter in WordPress 7.1\n\n\n\n\n\nThe Classic block stays in the inserter for WordPress 7.1\n\n\n\n\n

The React 19 upgrade was also deferred beyond WordPress 7.1 and continues as an experiment in the Gutenberg plugin.

\n\n\n\n\nReact 19: punted beyond WordPress 7.1, experiment in Gutenberg\n\n\n\n\nReal-time collaboration\n\n\n\n

Real-time collaborative editing received extensive testing and feedback during the WordPress 7.1 cycle, but it is not enabled in the final release. Work continues on the editing experience, conflict handling, compatibility, and the path toward a future Core integration.

\n\n\n\n\nAnnouncing a collaborative editing outreach effort for 7.1\n\n\n\n\n“On This Day” widget\n\n\n\n

The proposed “On This Day” dashboard widget was considered during the WordPress 7.1 cycle but was not included in the release. Further work and discussion can continue in the associated Trac ticket #65801.

\n\n\n\nMerge proposals\n\n\n\n

Several projects presented merge proposals during the WordPress 7.1 cycle. Some related foundations were included in the release, while the broader proposals continue to evolve and may be considered again after further testing, documentation, and feedback.

\n\n\n\n\nMerge Proposal: Guidelines built on Knowledge\n\n\n\n\n\nMerge Proposal: Design System Theming\n\n\n\n\n

\n\n\n\n

Thank you to everyone who contributed to this version of WordPress, whether through code, testing, or something else – your contributions matter and help Make WordPress.

\n\n\n\n

Props to @joedolson and @benjamin_zekavica for collaboration and review.

\n\n\n\n

\n

#7-1, #field-guide

", "id": 17077362, "pubDate": "Wed, 05 Aug 2026 14:42:44 GMT", "whenReceived": "Wed, 05 Aug 2026 15:19:39 GMT", "whenUpdated": "Thu, 13 Aug 2026 22:01:50 GMT", "likes": [], "metadata": { "wpPostId": 124988, "wpSiteId": 38254163 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125358", "title": "The notify_post_author filter now has the final say on post author notifications", "link": "https://make.wordpress.org/core/2026/08/05/the-notify_post_author-filter-now-has-the-final-say-on-post-author-notifications/", "description": "

WordPress 7.1 changes when wp_new_comment_notify_postauthor() checks a comment’s approval status: the check now happens before the notify_post_author filter is applied, rather than after. As a result, the filter receives an accurate default value, and its return value fully determines whether a notification is sent. See #64217.

\n\n\n\nPrevious behavior\n\n\n\n

The filter received a default derived only from the comments_notify option (or the wp_notes_notify option for notes). The comment’s approval status was checked after the filter ran, which had two consequences:

\n\n\n\n\nThe filter received a misleading default of true for unapproved comments whenever the option was enabled, even though no notification would be sent.\n\n\n\nReturning true from the filter could not force a notification for an unapproved comment – the return value was silently discarded.\n\n\n\n\nNew behavior in 7.1\n\n\n\n

The approval status is now incorporated into the default value passed to the filter, and the filter’s return value is final:

\n\n\n\n\nThe default is false for comments that are not approved, including those held in moderation, marked as spam, or trashed.\n\n\n\nThe default for approved comments continues to follow the comments_notify option, and the default for notes continues to follow the wp_notes_notify option regardless of approval status.\n\n\n\nReturning true from the filter now sends the notification, even for an unapproved comment.\n\n\n\n\n

Two smaller changes ship alongside this:

\n\n\n\n\nThe default passed to the filter is now always a strict boolean. Previously the raw option value (for example the string '1') could be passed through, so callbacks that strictly compare the incoming $maybe_notify value should compare against true/false.\n\n\n\nWhen the passed comment ID does not resolve to a valid comment, the function now returns false immediately without applying the filter. Previously, the filter still fired in this case.\n\n\n\n\nWho is affected\n\n\n\n

Sites or plugins using a callback such as __return_true on notify_post_author to force notifications will now also receive emails for comments held in moderation, marked as spam, or trashed. If that is not desired, the callback should check the comment’s approval status:

\n\n\n\nadd_filter(\n\t'notify_post_author',\n\tfunction ( $maybe_notify, $comment_id ) {\n\t\t$comment = get_comment( $comment_id );\n\n\t\t// Only force notifications for approved comments.\n\t\tif ( $comment && '1' === $comment->comment_approved ) {\n\t\t\treturn true;\n\t\t}\n\n\t\treturn $maybe_notify;\n\t},\n\t10,\n\t2\n);\n\n\n\n

Callbacks that only suppress notifications (returning false) are unaffected, as are sites that do not filter notify_post_author at all.

\n\n\n\n

Props to @milana_cap for peer review.

\n\n\n\n

\n

#7-1, #dev-notes, #dev-notes-7-1

", "id": 17075005, "pubDate": "Wed, 05 Aug 2026 12:22:02 GMT", "whenReceived": "Wed, 05 Aug 2026 13:38:24 GMT", "whenUpdated": "Wed, 05 Aug 2026 13:38:24 GMT", "likes": [], "metadata": { "wpPostId": 125358, "wpSiteId": 38254163 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125319", "title": "Filtering registered abilities with wp_get_abilities() in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/08/05/filtering-registered-abilities-with-wp_get_abilities-in-wordpress-7-1/", "description": "

WordPress 7.1 extends wp_get_abilities() with a standard way to filter registered abilities.

\n\n\n\n

The function now accepts an optional $args array that can filter abilities by category, namespace, or metadata. It also supports callbacks for custom per-item filtering and final result processing.

\n\n\n\n

Two new WordPress filters allow plugins to influence ability retrieval across the site:

\n\n\n\n\nwp_get_abilities_item_include\n\n\n\nwp_get_abilities_result\n\n\n\n\n

The REST API’s abilities list controller now uses wp_get_abilities() instead of implementing category filtering separately. It also supports filtering abilities by namespace.

\n\n\nWhy was this change needed?Filtering by categoryFiltering by namespaceFiltering by metadataCombining declarative filtersCustom per-item filteringProcessing the complete resultNew global filterswp_get_abilities_item_includewp_get_abilities_resultFiltering orderDiscovery over RESTBuilt-in annotation typesBackward compatibilityRetrieving the raw registryFiltering does not replace authorisationWhen to use each option\n\n\nWhy was this change needed?\n\n\n\n

Before WordPress 7.1, there were two ways to retrieve abilities:

\n\n\n\n// Retrieve every registered ability.\n$abilities = wp_get_abilities();\n\n// Retrieve one named ability.\n$ability = wp_get_ability( 'my-plugin/export-users' );\n\n\n\n

wp_get_abilities() always returned the complete registry. A caller needing a subset had to retrieve every ability and filter the result manually:

\n\n\n\n$abilities = array_filter(\n\twp_get_abilities(),\n\tfunction ( WP_Ability $ability ): bool {\n\t\treturn 'data-export' === $ability->get_category();\n\t}\n);\n\n\n\n

Several consumers developed their own versions of this pattern for category, namespace, and metadata checks. The REST abilities controller also performed its own category filtering after retrieving the complete registry.

\n\n\n\n

This led to:

\n\n\n\n\nDuplicated filtering code.\n\n\n\nInconsistent filtering semantics between consumers.\n\n\n\nDifferent behaviour between the PHP and REST APIs.\n\n\n\nNo standard extension points for ability selection.\n\n\n\nAdditional filtering passes over the registry.\n\n\n\n\n

WordPress 7.1 moves this work into wp_get_abilities(), providing one shared filtering pipeline for Core and plugins.

\n\n\n\nFiltering by category\n\n\n\n

Pass a category slug using the category argument:

\n\n\n\n$abilities = wp_get_abilities(\n\tarray(\n\t\t'category' => 'data-export',\n\t)\n);\n\n\n\n

The comparison is exact. Only abilities whose category exactly matches the supplied string are returned.

\n\n\n\n

The category must be passed as a single string. Arrays of category slugs are not supported.

\n\n\n\nFiltering by namespace\n\n\n\n

Use namespace to retrieve abilities registered under a particular namespace:

\n\n\n\n$abilities = wp_get_abilities(\n\tarray(\n\t\t'namespace' => 'my-plugin',\n\t)\n);\n\n\n\n

The namespace is passed without the trailing slash. Both of the following values are normalised to the same namespace:

\n\n\n\n'namespace' => 'my-plugin',\n'namespace' => 'my-plugin/',\n\n\n\n

An ability such as my-plugin/export-users matches, while another-plugin/export-users does not.

\n\n\n\n

Namespace matching includes the namespace delimiter. Passing my-plugin does not accidentally match an ability registered under a similarly named my-plugin-extra namespace.

\n\n\n\nFiltering by metadata\n\n\n\n

The meta argument selects abilities whose metadata contains the specified key-value pairs:

\n\n\n\n$abilities = wp_get_abilities(\n\tarray(\n\t\t'meta' => array(\n\t\t\t'public' => true,\n\t\t),\n\t)\n);\n\n\n\n

All supplied metadata conditions must match:

\n\n\n\n$abilities = wp_get_abilities(\n\tarray(\n\t\t'meta' => array(\n\t\t\t'public' => true,\n\t\t\t'show_in_rest' => true,\n\t\t),\n\t)\n);\n\n\n\n

Nested metadata is supported:

\n\n\n\n$abilities = wp_get_abilities(\n\tarray(\n\t\t'meta' => array(\n\t\t\t'my_client' => array(\n\t\t\t\t'public' => true,\n\t\t\t),\n\t\t),\n\t)\n);\n\n\n\n

Metadata comparisons are strict. The value true does not match 1, and false does not match 0.

\n\n\n\n

The metadata filter checks that every requested condition exists and matches. An ability may contain additional metadata that was not included in the query.

\n\n\n\nCombining declarative filters\n\n\n\n

The category, namespace, and meta arguments can be combined:

\n\n\n\n$abilities = wp_get_abilities(\n\tarray(\n\t\t'category' => 'data-export',\n\t\t'namespace' => 'my-plugin',\n\t\t'meta' => array(\n\t\t\t'public' => true,\n\t\t),\n\t)\n);\n\n\n\n

Conditions are combined using AND logic. An ability must satisfy every supplied argument to be included.

\n\n\n\n

In this example, the result contains only abilities that:

\n\n\n\n\nBelong to the data-export category.\n\n\n\nUse the my-plugin namespace.\n\n\n\nHave resolved public metadata set to true.\n\n\n\n\nCustom per-item filtering\n\n\n\n

Conditions that cannot be expressed using the declarative arguments can be handled with item_include_callback:

\n\n\n\n$abilities = wp_get_abilities(\n\tarray(\n\t\t'namespace' => 'my-plugin',\n\t\t'item_include_callback' => function (\n\t\t\tWP_Ability $ability\n\t\t): bool {\n\t\t\treturn my_plugin_should_include_ability( $ability );\n\t\t},\n\t)\n);\n\n\n\n

The callback runs once for every ability that passed the declarative filters. It receives the WP_Ability instance and must return a boolean:

\n\n\n\n\nReturn true to include the ability.\n\n\n\nReturn false to exclude it.\n\n\n\n\n

This callback is scoped to the current wp_get_abilities() call. It does not affect ability retrieval elsewhere.

\n\n\n\n

Use it for conditions such as:

\n\n\n\n\nCustom metadata relationships.\n\n\n\nContext-dependent visibility.\n\n\n\nIntegration-specific rules.\n\n\n\nConditions involving more than one ability property.\n\n\n\n\nProcessing the complete result\n\n\n\n

Use result_callback when an operation requires the complete matched array:

\n\n\n\n$abilities = wp_get_abilities(\n\tarray(\n\t\t'namespace' => 'my-plugin',\n\t\t'result_callback' => function ( array $abilities ): array {\n\t\t\tuasort(\n\t\t\t\t$abilities,\n\t\t\t\tfunction (\n\t\t\t\t\tWP_Ability $first,\n\t\t\t\t\tWP_Ability $second\n\t\t\t\t): int {\n\t\t\t\t\treturn strcasecmp(\n\t\t\t\t\t\t$first->get_label(),\n\t\t\t\t\t\t$second->get_label()\n\t\t\t\t\t);\n\t\t\t\t}\n\t\t\t);\n\n\t\t\treturn array_slice(\n\t\t\t\t$abilities,\n\t\t\t\t0,\n\t\t\t\t10,\n\t\t\t\ttrue\n\t\t\t);\n\t\t},\n\t)\n);\n\n\n\n

The result callback runs after all per-item matching has completed. It is suitable for:

\n\n\n\n\nSorting.\n\n\n\nSlicing or pagination.\n\n\n\nReordering.\n\n\n\nOther final result transformations.\n\n\n\n\n

Like item_include_callback, result_callback applies only to the current function call.

\n\n\n\n

Registered abilities are normally returned in an associative array keyed by ability name. When sorting or slicing the result, preserve those keys when downstream code depends on them.

\n\n\n\nNew global filters\n\n\n\n

WordPress 7.1 also introduces two filters for plugins that need to affect ability retrieval beyond a single call site.

\n\n\n\nwp_get_abilities_item_include\n\n\n\n

The wp_get_abilities_item_include filter runs for every ability that passed the declarative conditions and the caller’s item_include_callback:

\n\n\n\nadd_filter(\n\t'wp_get_abilities_item_include',\n\tfunction (\n\t\tbool $include,\n\t\tWP_Ability $ability,\n\t\tarray $args\n\t): bool {\n\t\tif ( 'my-plugin/private-operation' === $ability->get_name() ) {\n\t\t\treturn false;\n\t\t}\n\n\t\treturn $include;\n\t},\n\t10,\n\t3\n);\n\n\n\n

The filter receives:

\n\n\n\n\n$include: Whether the ability should currently be included.\n\n\n\n$ability: The ability being evaluated.\n\n\n\n$args: The complete arguments passed to wp_get_abilities().\n\n\n\n\n

Because declarative mismatches are removed before this filter runs, the filter cannot add an ability that failed category, namespace, or meta matching. It can influence the inclusion of abilities that have reached this stage, as well as their global exclusion.

\n\n\n\nwp_get_abilities_result\n\n\n\n

The wp_get_abilities_result filter receives the complete result after the caller’s result_callback:

\n\n\n\nadd_filter(\n\t'wp_get_abilities_result',\n\tfunction ( array $abilities, array $args ): array {\n\t\t// Apply site-wide result processing when appropriate.\n\t\treturn $abilities;\n\t},\n\t10,\n\t2\n);\n\n\n\n

The filter receives:

\n\n\n\n\n$abilities: The final matched array.\n\n\n\n$args: The complete arguments passed to wp_get_abilities().\n\n\n\n\n

It can be used for site-wide sorting, reordering, or other final processing.

\n\n\n\n

These are global filters. Plugins should use them only when the behaviour is intended to affect every relevant caller. For logic that belongs to one operation, prefer item_include_callback or result_callback.

\n\n\n\nFiltering order\n\n\n\n

The complete pipeline runs in the following order:

\n\n\n\n\nMatch the category argument.\n\n\n\nMatch the namespace argument.\n\n\n\nMatch the meta argument.\n\n\n\nRun item_include_callback.\n\n\n\nApply wp_get_abilities_item_include.\n\n\n\nAdd included abilities to the matched result.\n\n\n\nRun result_callback on the complete result.\n\n\n\nApply wp_get_abilities_result.\n\n\n\n\n

The declarative checks, item callback, and item filter run within a single pass over the registry.

\n\n\n\n

This avoids the separate array_filter() passes that consumers previously had to implement.

\n\n\n\nDiscovery over REST\n\n\n\n

The REST collection endpoint delegates to wp_get_abilities() and exposes the declarative filters as query parameters:

\n\n\n\nGET /wp-json/wp-abilities/v1/abilities?namespace=my-plugin\nGET /wp-json/wp-abilities/v1/abilities?category=my-plugin-content\nGET /wp-json/wp-abilities/v1/abilities?meta[annotations][readonly]=true\n\n\n\n

Parameters can be combined and use the same AND logic.

\n\n\n\n?category=data-export&namespace=my-plugin\n\n\n\n

Every collection request also forces meta.show_in_rest = true internally. Supplying another metadata query can’t reveal an ability that is hidden from REST. The endpoint still requires an authenticated WordPress user, and executing a listed ability still requires its permission callback to pass.

\n\n\n\n

Custom metadata needs a REST parameter schema if its query-string values should be coerced before strict comparison. Without one, 'true' will never match boolean true. The rest_abilities_collection_params filter extends the collection argument schema:

\n\n\n\nadd_filter(\n\t'rest_abilities_collection_params',\n\tstatic function ( array $params ): array {\n\t\t$params['meta']['properties']['my_plugin'] = array(\n\t\t\t'type' => 'object',\n\t\t\t'properties' => array(\n\t\t\t\t'enabled' => array(\n\t\t\t\t\t'type' => 'boolean',\n\t\t\t\t),\n\t\t\t),\n\t\t);\n\t\treturn $params;\n\t}\n);\n\n\n\n

After that declaration, the REST API casts \"true\" to a boolean true before the value reaches the metadata-matching logic.

\n\n\n\nGET /wp-json/wp-abilities/v1/abilities?meta[my_plugin][enabled]=true\n\n\n\nBuilt-in annotation types\n\n\n\n

The known readonly, destructive, and idempotent annotation values are coerced from query strings to boolean values before strict matching. Core declares the schema for these standard ability annotations.

\n\n\n\n

Each accepts a boolean or null, so REST can correctly cast their query values without a plugin extending the schema:

\n\n\n\n?meta[annotations][readonly]=true\n\n\n\n

Use rest_abilities_collection_params filter when making additional metadata fields queryable, especially boolean, integer, number, array, or object values that cannot be matched correctly as untyped query strings.

\n\n\n\nBackward compatibility\n\n\n\n

The $args parameter is optional:

\n\n\n\n$abilities = wp_get_abilities();\n\n\n\n

Existing calls remain valid, and the function still returns an array of WP_Ability instances keyed by ability name.

\n\n\n\n

Code that manually filters the result can continue to work:

\n\n\n\n$abilities = array_filter(\n\twp_get_abilities(),\n\t'my_plugin_filter_abilities'\n);\n\n\n\n

However, plugins should migrate common category, namespace, and metadata checks to the new arguments. Doing so reduces duplicated code and allows Core and other integrations to use consistent matching behaviour.

\n\n\n\n

One behavioural detail deserves particular attention: the two new global filters run even when wp_get_abilities() is called without arguments.

\n\n\n\n

As a result, the following call now means “retrieve abilities through the standard filtering pipeline”:

\n\n\n\n$abilities = wp_get_abilities();\n\n\n\n

It does not necessarily mean “retrieve raw registry contents,” because another plugin can alter the result through wp_get_abilities_item_include and wp_get_abilities_result.

\n\n\n\nRetrieving the raw registry\n\n\n\n

Code that specifically needs the complete, unfiltered registry can use WP_Abilities_Registry::get_all_registered():

\n\n\n\n$registry = WP_Abilities_Registry::get_instance();\n$abilities = $registry->get_all_registered();\n\n\n\n

This bypasses:

\n\n\n\n\nDeclarative filtering.\n\n\n\nCaller callbacks.\n\n\n\nwp_get_abilities_item_include\n\n\n\nwp_get_abilities_result\n\n\n\n\n

Most application and integration code should continue using wp_get_abilities(). Direct registry access is appropriate only when raw registered state is explicitly required, such as low-level debugging or registry inspection.

\n\n\n\nFiltering does not replace authorisation\n\n\n\n

Filtering controls which abilities are returned during discovery. It does not determine whether the current user may execute an ability.

\n\n\n\n

An ability’s permission_callback remains responsible for authorisation:

\n\n\n\n'permission_callback' => function (): bool {\n\treturn current_user_can( 'manage_options' );\n},\n\n\n\n

Developers should not assume that an ability returned by wp_get_abilities() is executable by the current user.

\n\n\n\n

Similarly, excluding an ability from a filtered result is not a security boundary. Any sensitive operation must enforce its permissions when the ability is executed.

\n\n\n\nWhen to use each option\n\n\n\n

Use declarative arguments for standard selection:

\n\n\n\nwp_get_abilities(\n\tarray(\n\t\t'category' => 'data-export',\n\t\t'namespace' => 'my-plugin',\n\t\t'meta' => array(\n\t\t\t'public' => true,\n\t\t),\n\t)\n);\n\n\n\n

Use item_include_callback for custom conditions that apply to one call:

\n\n\n\nwp_get_abilities(\n\tarray(\n\t\t'item_include_callback' => 'my_plugin_should_include_ability',\n\t)\n);\n\n\n\n

Use result_callback for call-specific sorting or slicing:

\n\n\n\nwp_get_abilities(\n\tarray(\n\t\t'result_callback' => 'my_plugin_prepare_ability_results',\n\t)\n);\n\n\n\n

Use wp_get_abilities_item_include or wp_get_abilities_result only for behaviour intended to affect ability retrieval across callers.

\n\n\n\n

Use WP_Abilities_Registry::get_all_registered() only when code explicitly requires raw, unfiltered registry data.

\n\n\n\n

Together, these changes make wp_get_abilities() the shared discovery and filtering primitive for the Abilities API, replacing duplicated filtering implementations with a consistent, extensible pipeline.

\n\n\n\n

These changes were introduced in changeset [62420] for Trac ticket #64990.

\n\n\n\n

Props to @benjamin_zekavica for peer review, and @gziolo for review, technical guidance, and suggested improvements.

\n\n\n\n

\n

#abilities-api, #7-1, #dev-notes, #dev-notes-7-1, #rest-api

", "id": 17075006, "pubDate": "Wed, 05 Aug 2026 11:55:27 GMT", "whenReceived": "Wed, 05 Aug 2026 13:38:24 GMT", "whenUpdated": "Wed, 05 Aug 2026 17:00:49 GMT", "likes": [], "metadata": { "wpPostId": 125319, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Wed, 05 Aug 2026 10:58:18 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69309", "title": "PTE Request for RatingStar.de Seal", "link": "https://make.wordpress.org/polyglots/2026/08/05/pte-request-for-ratingstar-de-seal/", "description": "

Hi Polyglots, I’m the plugin author of RatingStar.de Seal.
\nThe plugin is a connector for a German review platform, so German is its
\nmain audience. I have complete translations ready for both the plugin
\nstrings and the readme, and would like to maintain them myself.

\n

Please add me as PTE for the following locales:

\n

Plugin: https://wordpress.org/plugins/ratingstar-de-seal/
\nProject: https://translate.wordpress.org/projects/wp-plugins/ratingstar-de-seal/

\n\n #de_DE @phillipb (@tobifjellner)\n\n\n

Thanks a lot!

\n

#editor-requests

", "id": 17071470, "pubDate": "Wed, 05 Aug 2026 09:45:50 GMT", "whenReceived": "Wed, 05 Aug 2026 10:58:18 GMT", "whenUpdated": "Wed, 05 Aug 2026 21:06:40 GMT", "likes": [], "metadata": { "wpPostId": 69309, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/hosting/feed/", "whenReceived": "Wed, 05 Aug 2026 11:00:09 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/hosting/feed/", "guid": "https://make.wordpress.org/hosting/?p=187385", "title": "Hosting Team Meeting Agenda 2026-08-05", "link": "https://make.wordpress.org/hosting/2026/08/05/hosting-team-meeting-agenda-2026-08-05/", "description": "Next Meeting\n\n\n\n

The next meetings will be in the #hosting channel on Wednesday, August 5, 2026 at 0900 UTC and Wednesday, August 5, 2026 at 1800 UTC. Hope to see you then!

\n\n\n\nAgenda\n\n\n\n\nWordPress News\n\n\n\n\n7.1 RC1\n\n\n\nNew 7.1 Dev Notes:\n\nNew execution lifecycle filters for the Abilities API in WordPress 7.1\n\n\n\njQuery UI updated to 1.14.2 in WordPress 7.1\n\n\n\nLeaner, steadier PHPUnit runs for upcoming releases\n\n\n\nFiltering Site Editor Screens in WordPress 7.1\n\n\n\nDesign System Theming in WordPress 7.1\n\n\n\nAbilities API improvements in WordPress 7.1\n\n\n\nJSON Schema preparation for client compatibility in WordPress 7.1\n\n\n\nIframed Editor Changes in WordPress 7.1\n\n\n\nPost list tables row headers changed\n\n\n\nIntroducing name and informational tool tips in WordPress 7.1\n\n\n\nMiscellaneous Editor Changes in WordPress 7.1\n\n\n\nA unified public exposure flag for Abilities in WordPress 7.1\n\n\n\n\n\nDefensive Data Design\n\n\n\n\nHosting Team\n\n\n\n\nWordCamp US 2026 Contributor Day\n\n\n\nTickets/PRs\n\n\n\n\nOpen Floor\n\n\n\nIdeas or suggestions\n\n\n\n

Anything else? Please leave a comment with any additions or suggestions for the meeting.

\n

#agenda, #hosting, #hosting-community, #meetings, #weekly-hosting-chat

", "id": 17071511, "pubDate": "Wed, 05 Aug 2026 07:50:59 GMT", "whenReceived": "Wed, 05 Aug 2026 11:00:09 GMT", "whenUpdated": "Wed, 05 Aug 2026 11:00:09 GMT", "likes": [], "metadata": { "wpPostId": 187385, "wpSiteId": 120824672 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Wed, 05 Aug 2026 08:23:05 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=90244", "title": "Monthly Education Buzz Report – July 2026", "link": "https://make.wordpress.org/community/2026/08/05/monthly-education-buzz-report-july-2026/", "description": "

Welcome to the Monthly Education Buzz Report, your go-to source for highlights and updates on the WordPress Campus Connect, WordPress Credits, and WordPress Student Club education initiatives within the WordPress community. This report aims to celebrate, promote, and inform individuals across the WordPress community and beyond about the diverse educational endeavors underway.

\n\n\n\nWordPress Campus Connect\n\n\n\n

WordPress Campus Connect (WPCC) had a busy July, with new campuses joining the program on four continents. If you would like to help shape one of these events, join the conversation in #campusconnect on the Make WordPress Slack.

\n\n\n\n\n\n\n\n

Bangladesh saw two more campuses join WPCC Kishoreganj 2026, organized by Muhibul Haque (@devmuhib). The first event, held at Kishoreganj University, brought speakers Nasim Miah (@muddassirnasim) and Mehraz Morshed (@mehrazmorshed) together with volunteer Mehrab Morshed (@mehrabmorshed). for a session on the WordPress ecosystem, careers, and open source contribution. Students there built 38 websites. Two weeks later, the series moved to Kishoreganj Polytechnic Institute, where speaker Shipon Karmakar (@shiponkarmakar) traveled more than 80 kilometers to join as a guest expert and students built nearly 70 websites. Across the two campuses, the success stories page now lists more than 200 participating students and over 100 published sites, with two more institutions, Government Mohila College and Pouromohila College Kishoreganj, still to come.

\n\n\n\n

Japan held its second Campus Connect event of the year at Kyoto University of Advanced Science on July 4. The session was organized entirely by students from the campus’s Open Source circle, with Kaito Hanamori (@kaitohm) sharing the recap and thanking staff members Hiroshi Sato and Shohei Tanaka for their support.

\n\n\n\n

In Spain, Josep MorĂĄn (@josepmoran) led a Campus Connect at Escola Pia Sta. Anna in MatarĂł for 100 higher-level vocational students studying network management and marketing. Over two four-hour sessions, students compared WordPress.com and WordPress.org, learned about WordPress Credits and WordPress Student Clubs, and used Playground and AI assistance to build a functional plugin that calculates the best time for shore fishing in the city. Students and faculty alike called out the career opportunities tied to the WordPress ecosystem and the official certificate they received.

\n\n\n\n

Uganda’s Central and Eastern Uganda schools series added Bulamogi College Gadumire on July 29, and the full recap is worth reading in full. Organizer Moses Cursor Ssebunya (@mosescursor) and his team lost power on arrival, so they scrapped the planned demonstrations and instead opened the floor to questions from more than 100 learners. Fellow organizer Stephen Dumba, national coordinator of the ICT Teachers Association of Uganda, stepped in to keep the group focused once the power went out. The room, in the organizers’ words, “exploded” with curiosity, and first-time volunteers Mariam Nairuba and John Wayera helped carry the day. The school’s governing body received a Certificate of Appreciation in return for hosting.

\n\n\n\n

A few more campuses are moving through planning, including a first-ever event proposed for Penang, Malaysia, by Ben Leow (@surf7net) ahead of WordCamp Asia 2027, and an event at UVG Guatemala coordinated by Lidia Arroyo Vargas (@lidarroy). If you have a connection to a college or university and want to help bring WordPress to campus, the #campusconnect channel is the place to start.

\n\n\n\n\nKyoto University of Advanced Science\n\n\n\nKyoto University of Advanced Science\n\n\n\nWPCC Kishoreganj 2026\n\n\n\nWPCC Kishoreganj 2026\n\n\n\n\n\nCampus Connect Escola Pia Sta. Anna MatarĂł\n\n\n\nCampus Connect Escola Pia Sta. Anna MatarĂł\n\n\n\n\nWordPress Credits\n\n\n\n

WordPress Credits kept building on its first-half momentum in July, with two new pilot projects, a call for a developer track, and a preview of what the program will bring to WordCamp US.

\n\n\n\n

July was the strongest month of the year so far by several measures, according to an update from Maciej Pilarski (@gomp). Partner institutions grew from 28 to 38, up 10 in a single month and now spanning 16 countries, with 18 more institutions entering the pipeline, the strongest intake month of 2026. Active mentors reached 91, up from 83 in June, on the strength of 11 new mentor applications, while 62 new students started their WordPress Credits internship, the second-largest monthly intake of the year after May. Graduates reached 226, up from 199 in June, with 26 more students in pending graduation. Two applications that came out of the WordCamp Europe Education Table in Kraków, Haaga-Helia University of Applied Sciences in Finland and SAE Athens in Greece, are now confirmed partners, and Institut Teknologi Tangerang Selatan in Indonesia became the first Campus Connect host school to convert into a WordPress Credits partner institution, signing on July 20 after hosting a Campus Connect event on June 18. That signing also gave Indonesia its first spot on the partner map. Separately, CUNY City Tech signed on as the program’s first partnership with a public university system in the United States, arriving just ahead of the WordCamp US Contributor Day push.

\n\n\n\n

Rita Robles Loaiza (@roblesloaiza) shared the first two pilots she has been running as Program Manager for WordPress Credits in Latin America. The first grew out of Patrones Hermosos, an international camp run by TecnolĂłgico de Monterrey and MIT that came to Costa Rica for the first time this year. Three students from the second WordPress Credits cohort at Universidad FidĂŠlitas designed and delivered a three-session WordPress workshop for 40 high school students, who each built and presented their own website by the end, with a 100 percent satisfaction rate. The team turned that experience into a fully replicable guide that any student, university, or local community can reuse. The second pilot brings Liceo Experimental BilingĂźe JosĂŠ Figueres Ferrer, the first high school in the Americas to join WordPress Credits, into the Polyglots contribution area, where 13 students are working with the Costa Rican Spanish Polyglots team to localize WordPress.org into es_CR as part of their community service program.

\n\n\n\n\nUniversidad FidĂŠlitas\n\n\n\nUniversidad FidĂŠlitas\n\n\n\n\n

The program is also looking ahead to a developer-focused track. A US college has expressed interest in WordPress Credits but needs a path built around real, job-relevant development work, and the call for input is open now. The team is looking for ideas on what a beginner-to-advanced tier structure could include, with the first tier needed by the end of August to keep the pilot on schedule. You can weigh in through the GitHub issue or in #wpcredits on Slack.

\n\n\n\n

Looking toward WordCamp US, the Education working group announced a dedicated table at Contributor Day on August 16 in Phoenix. Isotta Peira (@peiraisotta) and Maciej Pilarski (@gomp) will be on hand throughout the event to talk through WordPress Credits, Campus Connect, Student Clubs, Faculty Training, and the new AI Literacy through WordPress course on Learn WordPress. The group is looking for US-based mentors, connections to local meetups for students, introductions to colleges and universities, and companies interested in sponsoring the programs.

\n\n\n\n

July also brought a steady flow of new students into the program, joining from Nepal, Costa Rica, Spain, India, and the US, including a professor at Drew University in New Jersey who found the program through a WP Tavern Jukebox episode featuring Ivana Ćirković. Among them, Víctor Rodríguez of Universidad Fidélitas in Costa Rica wrapped up his internship with the Polyglots team, submitting 386 translation suggestions for WooCommerce in Spanish (Costa Rica) and documenting his progress along the way. Anne McCarthy (@annezazu), the WordPress 7.1 release lead, kept up her behind-the-scenes updates for students so they can shadow the release process firsthand.

\n\n\n\nWordPress Student Clubs\n\n\n\n

A Student Club at Ahmad’s Education in Dhaka, Bangladesh, used its weekly session to dig into how WordPress works as an open source project, discussing how the platform has grown through the contributions of millions of people and how club members can start contributing themselves. Organizer Atikur Rahman shared that the group is now preparing for an upcoming WordPress Campus Connect event at the same institution, with members working to bring in more classmates and build on the momentum from the discussion.

\n\n\n\nGet Involved\n\n\n\n

WordPress Credits
WordPress Campus Connect
WordPress Student Clubs

\n\n\n\n

See something in the community that should be noted here or in a future newsletter? Comment below!

\n\n\n\n

Stay tuned for next month’s update!

\n\n\n\nTags\n\n\n\n

#education-buzz, #campusconnect, #wpcredits

", "id": 17068983, "pubDate": "Wed, 05 Aug 2026 07:08:17 GMT", "whenReceived": "Wed, 05 Aug 2026 08:23:05 GMT", "whenUpdated": "Thu, 06 Aug 2026 04:53:36 GMT", "likes": [], "metadata": { "wpPostId": 90244, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed/", "whenReceived": "Wed, 05 Aug 2026 08:29:16 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed/", "guid": "https://make.wordpress.org/core/?p=124535", "title": "Responsive block styles and configurable viewports in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/08/05/responsive-block-styles-and-configurable-viewports-in-wordpress-7-1/", "description": "

WordPress 7.1 introduces responsive style states for blocks. Styles can now be defined for Tablet and Mobile viewports both through Global Styles for each block type and on individual block instances. They can be applied to all block types (and their block style variations) that use core block supports such as typography, color, background, border, dimensions, spacing, and layout.

\n\n\n\n

The default style remains the base style and applies at every viewport. Tablet and Mobile styles override that base within their respective breakpoint ranges.

\n\n\n\n

It is now also possible to define custom values for the Tablet and Mobile viewports, using px, em or rem units.

\n\n\n\nDefining responsive block styles in `theme.json`\n\n\n\n\"styles\": {\n\t\t\"blocks\": {\n\t\t\t\"core/group\": {\n\t\t\t\t\"spacing\": {\n\t\t\t\t\t\"padding\": {\n\t\t\t\t\t\t\"top\": \"3rem\",\n\t\t\t\t\t\t\"right\": \"3rem\",\n\t\t\t\t\t\t\"bottom\": \"3rem\",\n\t\t\t\t\t\t\"left\": \"3rem\"\n\t\t\t\t\t}\n\t\t\t\t},\n\t\t\t\t\"@mobile\": {\n\t\t\t\t\t\"spacing\": {\n\t\t\t\t\t\t\"padding\": {\n\t\t\t\t\t\t\t\"top\": \"1rem\",\n\t\t\t\t\t\t\t\"right\": \"1rem\",\n\t\t\t\t\t\t\t\"bottom\": \"1rem\",\n\t\t\t\t\t\t\t\"left\": \"1rem\"\n\t\t\t\t\t\t}\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t}\n\t\t}\n\t}\n\n\n\n

Responsive and pseudo-states are nested from viewport to pseudo-state:

\n\n\n\n\"styles\": {\n\t\t\"blocks\": {\n\t\t\t\"core/button\": {\n\t\t\t\t\"@mobile\": {\n\t\t\t\t\t\":hover\": {\n\t\t\t\t\t\t\"color\": {\n\t\t\t\t\t\t\t\"background\": \"var:preset|color|contrast\",\n\t\t\t\t\t\t\t\"text\": \"var:preset|color|base\"\n\t\t\t\t\t\t}\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t}\n\t\t}\n\t}\n\n\n\nBlock instance attributes\n\n\n\n

Responsive styles for an individual block are stored in the block’s existing style attribute, using the same @mobile and @tablet keys as Global Styles:

\n\n\n\n<!-- wp:paragraph {\"style\":{\"@mobile\":{\"typography\":{\"fontSize\":\"1rem\"}}}} -->\n<p>Text with a responsive font size.</p>\n<!-- /wp:paragraph -->\n\n\n\n

On the frontend, WordPress generates media-query-scoped CSS for the responsive values and adds a stable, generated class to the rendered block. Non-layout per-instance state declarations are marked `!important` so they can override the block’s default inline styles. Responsive layout values and `blockGap` are processed by the existing layout support and scoped with the block’s generated container class.

\n\n\n\nConfigurable breakpoints\n\n\n\n

WordPress provides two responsive style breakpoints by default:

\n\n\n\nStateMedia query@mobile@media (width <= 480px)@tablet@media (480px < width <= 782px)\n\n\n\n

There is no @desktop style key. The block’s default style is the desktop/base style and continues to apply at smaller sizes for any property that is not overridden.

\n\n\n\n

Themes can customize the breakpoint widths with the new top-level settings.viewport values:

\n\n\n\n\"settings\": {\n\t\t\"viewport\": {\n\t\t\t\"mobile\": \"30rem\",\n\t\t\t\"tablet\": \"45rem\"\n\t\t}\n\t}\n\n\n\n

This produces the following ranges:

\n\n\n\n@media (width <= 30rem) { /* Mobile */ }\n@media (30rem < width <= 45rem) { /* Tablet */ }\n\n\n\n

Breakpoint values must be non-negative numeric lengths using px, em, or rem. CSS functions, percentages, unitless values, and other units are ignored.

\n\n\n\n

If only one valid breakpoint is configured, it keeps its viewport name and uses a single maximum-width query. If neither value is valid, the defaults are used. When both are valid but the Tablet value is smaller than or equal to the Mobile value, only the Mobile breakpoint is used.

\n\n\n\n

The configured viewport widths are used by responsive block styles and block visibility, and are previewable via the editor’s device preview.

\n\n\n\n

settings.viewport is a top-level setting. It cannot be configured separately for individual block types.

\n\n\n\nOpting out of responsive editing\n\n\n\n

Sites that need to prevent users from making viewport-based styling changes can turn off responsive style editing with the responsiveEditingEnabled editor setting, which defaults to true:

\n\n\n\nfunction example_disable_responsive_editing( $settings ) {\n\t$settings['responsiveEditingEnabled'] = false;\n\treturn $settings;\n}\nadd_filter( 'block_editor_settings_all', 'example_disable_responsive_editing' );\n\n\n\n

When it is false, both entry points for choosing a viewport are removed: the “Responsive styles” toggle in the Editor’s View menu, and the “Viewport” group in the “States” dropdown in Global Styles. Device previews still work, and pseudo states such as Hover remain available.

\n\n\n\n

The setting governs the editing interface only. Responsive styles already saved in theme.json, in Global Styles, or in a block’s style attribute are left untouched, and the media-query CSS described above is still generated for them, so existing content renders exactly as before both in the Editor and on the front end.

\n\n\n\n

Reviewed by @tyxla; props @ramonopoly, @wildworks

\n

#7-1, #dev-notes, #dev-notes-7-1

", "id": 17069099, "pubDate": "Wed, 05 Aug 2026 06:50:06 GMT", "whenReceived": "Wed, 05 Aug 2026 08:29:16 GMT", "whenUpdated": "Thu, 06 Aug 2026 18:53:06 GMT", "likes": [], "metadata": { "wpPostId": 124535, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Wed, 05 Aug 2026 08:13:02 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125119", "title": "Pseudo and custom style states in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/08/05/pseudo-and-custom-style-states-in-wordpress-7-1/", "description": "Pseudo states\n\n\n\n

In WordPress 7.1, users have more power over styling the pseudo states of blocks. Currently limited to the Button and Navigation Link blocks, users are able to apply styles to ‘hover’, ‘focus’, ‘focus-visible’ and ‘active’ states.

\n\n\n\n

Pseudo states support definitions in theme.json for themers, and block styling in global styles and on block instances for users.

\n\n\n\nDefining pseudo states for blocks in theme.json \n\n\n\n

Define pseudo states within the block object using the properties “:hover”, “:focus”, “:focus-visible”, and “:active”. Pseudo state names are always prefixed with a :.

\n\n\n\n\"styles\": {\n\t\"blocks\": {\n\t\t\"core/button\": {\n\t\t\t\"color\": {\n\t\t\t\t\"background\": \"black\",\n\t\t\t\t\"text\": \"white\"\n\t\t\t},\n\t\t\t\":hover\": {\n\t\t\t\t\"color\": {\n\t\t\t\t\t\"background\": \"blue\"\n\t\t\t\t}\n\t\t\t},\n\t\t\t\":focus\": {\n\t\t\t\t\"color\": {\n\t\t\t\t\t\"background\": \"purple\"\n\t\t\t\t}\n\t\t\t}\n\t\t}\n\t}\n}\n\n\n\n\n

Pseudo states can also be nested within responsive states:

\n\n\n\n\"styles\": {\n\t\"blocks\": {\n\t\t\"core/button\": {\n\t\t\t\"@mobile\": {\n\t\t\t\t\":hover\": {\n\t\t\t\t\t\"color\": {\n\t\t\t\t\t\t\"background\": \"var:preset|color|contrast\",\n\t\t\t\t\t\t\"text\": \"var:preset|color|base\"\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t}\n\t\t}\n\t}\n}\n\n\n\nBlock instance attributes\n\n\n\n

The structure for block instance attributes is very similar to the theme.json definition with :hover properties used inside the style attribute:

\n\n\n\n<!-- wp:button {\"backgroundColor\":\"accent-3\",\"style\":{\":hover\":{\"color\":{\"background\":\"var:preset|color|accent-2\"}}}} -->\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link has-accent-3-background-color has-background wp-element-button\">Button with pseudo state background</a></div>\n<!-- /wp:button -->\n\n\n\nCustom style states\n\n\n\n

Custom states are an early feature limited to theme.json definition only (no user facing features are exposed) and only the navigation link block. The navigation block uses this to allow styling of the current menu item – that is the menu item whose link matches that of the currently viewed page.

\n\n\n\nDefining custom states for the navigation link block in theme.json\n\n\n\n

Styles for the current menu item can be defined using the -current property. Custom states always use the -prefix.

\n\n\n\n\"styles\": {\n\t\"blocks\": {\n\t\t\"core/navigation-link\": {\n\t\t\t\"-current\": {\n\t\t\t\t\"color\": {\n\t\t\t\t\t\"text\": \"var:preset|color|contrast\"\n\t\t\t\t},\n\t\t\t\t\":hover\": {\n\t\t\t\t\t\"color\": {\n\t\t\t\t\t\t\"text\": \"var:preset|color|accent-1\"\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t}\n\t\t}\n\t}\n}\n\n\n\n

As shown above, pseudo states can be nested within custom states. Custom states can also be nested within responsive states.

\n\n\n\nStyle generation\n\n\n\n

The styles defined for custom states generate css that targets a class name selector. For the navigation link block, that would expand to something like .wp-block-navigation-link .current-menu-item { // styles ... }.

\n\n\n\n

The styles css class name that’s generated in the selector would be declared on supported blocks via a block’s block.json selectors property:

\n\n\n\n\"selectors\": {\n\t\"states\": {\n\t\t\"-current\": \".wp-block-navigation-link .current-menu-item\"\n\t}\n}\n\n\n\nOpting out of style state editing\n\n\n\n

Sites can prevent users from styling block states via the blockStatesEditingEnabled editor setting:

\n\n\n\nfunction example_disable_block_states_editing( $settings ) {\n\t$settings['blockStatesEditingEnabled'] = false;\n\treturn $settings;\n}\nadd_filter( 'block_editor_settings_all', 'example_disable_block_states_editing' );\n\n\n\n

blockStatesEditingEnabled defaults to true.

\n\n\n\n

When it is false, both the state dropdown in the block inspector’s block card, and the pseudo state options in the “States” dropdown in Global Styles under Styles > Blocks are hidden.

\n\n\n\n

The states affected are the pseudo states, Hover, Focus, Focus-visible and Active, which currently apply to the Button and Navigation Link blocks. In the future this will extend to other states present in the dropdown, like the ability for users to set styles for the Navigation Link’s ‘Current’ state.

\n\n\n\n

This setting does not affect viewport states. Those are controlled separately by responsiveEditingEnabled. Set both to false to remove the state editing interface entirely.

\n\n\n\n

The setting governs the editing interface only. State styles already saved in theme.json, in Global Styles, or in a block’s style attribute are left untouched and are still applied, so existing content renders exactly as before both in the Editor and on the front end.

\n\n\n\n

Reviewed by @ramonopoly, @andrewserong; props @wildworks

\n

#7-1, #dev-notes, #dev-notes-7-1

", "id": 17068835, "pubDate": "Wed, 05 Aug 2026 06:49:35 GMT", "whenReceived": "Wed, 05 Aug 2026 08:13:02 GMT", "whenUpdated": "Wed, 05 Aug 2026 08:13:02 GMT", "likes": [], "metadata": { "wpPostId": 125119, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 04 Aug 2026 21:29:03 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69296", "title": "Hi team, I am the…", "link": "https://make.wordpress.org/polyglots/2026/08/04/hi-team-i-am-the/", "description": "

Hi team,

\n

I am the plugin author for ImagePipe Lite. I have translated the plugin
\ninto French myself and would like to be able to approve these
\ntranslations.

\n\nhttps://wordpress.org/plugins/imagepipe-lite/\n\n\n\n #fr_FR – @cyril974\n\n\n

#editor-requests

", "id": 17060510, "pubDate": "Tue, 04 Aug 2026 21:00:22 GMT", "whenReceived": "Tue, 04 Aug 2026 21:29:03 GMT", "whenUpdated": "Tue, 04 Aug 2026 21:29:03 GMT", "likes": [], "metadata": { "wpPostId": 69296, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69293", "title": "PTE Request for StoreStack Attribute Fees for WooCommerce", "link": "https://make.wordpress.org/polyglots/2026/08/04/pte-request-for-storestack-attribute-fees-for-woocommerce/", "description": "

Hello,

\n

I am the author of StoreStack Attribute Fees for WooCommerce and I have submitted translations for the plugin. I’d like to kindly ask to become a PTE so I can review and approve the translations for my own plugin.

\n

Name: StoreStack Attribute Fees for WooCommerce
\nURL: https://wordpress.org/plugins/storestack-attribute-fees-for-woocommerce

\n\n #pt_BR – @storestack, @tiagosartor3\n\n\n

#editor-requests

", "id": 17060511, "pubDate": "Tue, 04 Aug 2026 21:00:13 GMT", "whenReceived": "Tue, 04 Aug 2026 21:29:03 GMT", "whenUpdated": "Wed, 05 Aug 2026 00:50:52 GMT", "likes": [], "metadata": { "wpPostId": 69293, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69291", "title": "Patu Optimizer – Hi Polyglots team,", "link": "https://make.wordpress.org/polyglots/2026/08/04/patu-optimizer-hi-polyglots-team/", "description": "

I’m the author of the plugin “Patu Optimizer” and I’d like to become a Project Translation Editor (PTE) for it, so I can review and validate its translations.

\n

Name: Patu Optimizer
\nURL: https://wordpress.org/plugins/patu-optimizer/
\nRequested locales:

\n\n #fr_FR \n\n\n

— es_ES
\n— de_DE
\n— pt_PT
\n— it_IT

\n

Username: @gheop

\n

I’ve already submitted the French UI strings (waiting) and will add the others. Thank you!

\n

#editor-requests

", "id": 17060512, "pubDate": "Tue, 04 Aug 2026 21:00:01 GMT", "whenReceived": "Tue, 04 Aug 2026 21:29:03 GMT", "whenUpdated": "Wed, 05 Aug 2026 10:58:18 GMT", "likes": [], "metadata": { "wpPostId": 69291, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69283", "title": "Avalio Hi Polyglots, I’m the…", "link": "https://make.wordpress.org/polyglots/2026/08/04/pte-request-hi-polyglots-im-the-2/", "description": "

Avalio!
\nHi Polyglots,

\n

I’m the plugin author of Dashboard for Availio and would like to request PTE access so I can approve the translations for my own plugin.

\n

Plugin: https://wordpress.org/plugins/dashboard-for-availio/
\nGlotPress: https://translate.wordpress.org/projects/wp-plugins/dashboard-for-availio/

\n\n #de_DE (@tobifjellner)\n\n #de_CH\n\n\n

WordPress.org username: @gianlucad

\n

I’ve already imported the full German readme translations (de_DE and de_CH); they’re currently waiting for approval. Thank you!

\n

#editor-requests

", "id": 17050611, "pubDate": "Tue, 04 Aug 2026 13:30:57 GMT", "whenReceived": "Tue, 04 Aug 2026 14:44:13 GMT", "whenUpdated": "Tue, 04 Aug 2026 23:09:51 GMT", "likes": [], "metadata": { "wpPostId": 69283, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69275", "title": "Title: PTE Request for Web…", "link": "https://make.wordpress.org/polyglots/2026/08/04/title-pte-request-for-web/", "description": "

Title: PTE Request for Web Makinasi – Sohbet Butonu

\n

Hello Polyglots,

\n

I am the author of the plugin Web Makinasi – Sohbet Butonu. I have suggested translations for the following locale(s) and would like to request Project Translation Editor (PTE) status to approve and maintain them.

\n\nPlugin: https://wordpress.org/plugins/webmakinasi-sohbet-butonu/\n\n\n\n #tr_TR @webmakinasi (@tobifjellner)\n\n\n

#editor-requests

", "id": 17050612, "pubDate": "Tue, 04 Aug 2026 13:26:23 GMT", "whenReceived": "Tue, 04 Aug 2026 14:44:13 GMT", "whenUpdated": "Wed, 05 Aug 2026 21:06:40 GMT", "likes": [], "metadata": { "wpPostId": 69275, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Tue, 04 Aug 2026 13:22:53 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125285", "title": "A unified public exposure flag for Abilities in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/08/04/a-unified-public-exposure-flag-for-abilities-in-wordpress-7-1/", "description": "

WordPress 7.1 introduces a new public metadata flag for abilities. The flag provides a single, high-level way to indicate that an ability is intended to be available to external clients such as the REST API, MCP adapters, and AI agents.

\n\n\n\n

Table of contents:

\n\n\nRegistering a public abilityHow exposure defaults are resolvedWhat problem does this change fix?Using public in other integrationsExposure is not authorisationChanges to resolved metadataBackward compatibilityExisting Core abilitiesWhen to use each flag\n\n\n

Previously, ability authors had to express that intent separately for every exposure channel. For example, an ability exposed through the REST API needed to set show_in_rest directly:

\n\n\n\n'meta' => array(\n\t'show_in_rest' => true,\n),\n\n\n\n

As the Abilities API gains more client integrations, repeating the same intent through several channel-specific flags becomes difficult to maintain. The new public flag establishes a common default while preserving granular control for each channel.

\n\n\n\nRegistering a public ability\n\n\n\n

An ability intended for client exposure can now set meta.public when it is registered:

\n\n\n\nfunction my_plugin_register_abilities(): void {\n\twp_register_ability(\n\t\t'my-plugin/export-users',\n\t\tarray(\n\t\t\t'label' => __( 'Export users', 'my-plugin' ),\n\t\t\t'description' => __( 'Exports user data as CSV.', 'my-plugin' ),\n\t\t\t'category' => 'data-export',\n\t\t\t'execute_callback' => 'my_plugin_export_users',\n\t\t\t'permission_callback' => function (): bool {\n\t\t\t\treturn current_user_can( 'export' );\n\t\t\t},\n\t\t\t'meta' => array(\n\t\t\t\t'public' => true,\n\t\t\t),\n\t\t)\n\t);\n}\n\nadd_action( 'wp_abilities_api_init', 'my_plugin_register_abilities' );\n\n\n\n

For the REST API, setting public to true makes show_in_rest default to true. The ability can therefore be discovered and invoked through the REST abilities endpoints, subject to its permission callback.

\n\n\n\nHow exposure defaults are resolved\n\n\n\n

Channel-specific settings take precedence over the general public setting. The effective REST exposure value is resolved as follows:

\n\n\n\n$show_in_rest = $meta['show_in_rest'] ?? $meta['public'] ?? false;\n\n\n\n

For example, an ability that is generally public but must not be exposed through REST can use:

\n\n\n\n'meta' => array(\n\t'public' => true,\n\t'show_in_rest' => false,\n),\n\n\n\n

The explicit show_in_rest value wins over public.

\n\n\n\n

Conversely, an ability that is not generally public can still opt into REST specifically:

\n\n\n\n'meta' => array(\n\t'public' => false,\n\t'show_in_rest' => true,\n),\n\n\n\n

The resolution uses null-coalescing semantics so an explicit false is preserved. It is not treated as a missing value.

\n\n\n\n

A null value is treated as unset and falls back to the next value in the chain.

\n\n\n\n

In practical terms:

\n\n\n\nRegistration metadataEffective publicEffective show_in_restNo exposure metadatafalsefalsepublic => truetruetruepublic => falsefalsefalseshow_in_rest => truefalsetruepublic => true, show_in_rest => falsetruefalsepublic => false, show_in_rest => truefalsetrue\n\n\n\n

This precedence allows for a broad exposure default while opting in or out of individual channels.

\n\n\n\nWhat problem does this change fix?\n\n\n\n

Ability metadata already contained channel-specific exposure settings such as show_in_rest. As support for MCP, AI agents, and other clients develops, requiring ability authors to configure each channel independently would duplicate the same policy across multiple properties:

\n\n\n\n'meta' => array(\n\t'show_in_rest' => true,\n\t'mcp' => array(\n\t\t'public' => true,\n\t),\n\t// Additional flags for future clients.\n),\n\n\n\n

This also makes it difficult for a newly introduced channel to determine whether an existing ability was intended for external use.

\n\n\n\n

The public flag fixes this by recording the ability author’s general exposure intent in one stable location:

\n\n\n\n'meta' => array(\n\t'public' => true,\n),\n\n\n\n

Individual integrations can use that value as their default while retaining a more specific channel-level override.

\n\n\n\n

REST is the first built-in consumer of this behaviour. Other integrations can adopt the same default without adding channel-specific logic to WordPress Core.

\n\n\n\nUsing public in other integrations\n\n\n\n

The resolved public value remains available in the ability’s metadata. Client integrations can inspect this value when determining whether an ability should be exposed.

\n\n\n\n

The WordPress MCP Adapter will respect the unified public flag starting with its next release. WP-CLI does not apply this exposure check because its ability-listing functionality returns all registered abilities.

\n\n\n\n

Other integrations should generally resolve exposure when abilities are selected for that integration:

\n\n\n\nfunction my_plugin_is_ability_exposed(\n\tWP_Ability $ability,\n\tstring $channel\n): bool {\n\t$meta = $ability->get_meta();\n\n\treturn $meta[ $channel ]['public'] ?? $meta['public'] ?? false;\n}\n\n\n\n

Integrations that need to derive their own channel-specific metadata during registration can use the existing wp_register_ability_args filter:

\n\n\n\nadd_filter(\n\t'wp_register_ability_args',\n\tfunction ( array $args, string $name ): array {\n\t\tif (\n\t\t\t! isset( $args['meta']['my_client']['public'] )\n\t\t\t&& isset( $args['meta']['public'] )\n\t\t) {\n\t\t\t$args['meta']['my_client']['public'] =\n\t\t\t\t(bool) $args['meta']['public'];\n\t\t}\n\n\t\treturn $args;\n\t},\n\t10,\n\t2\n);\n\n\n\n

An integration should follow the same precedence rule as REST:

\n\n\n\n\nUse an explicit channel-specific value when present.\n\n\n\nOtherwise, inherit public.\n\n\n\nOtherwise, use the channel’s built-in default.\n\n\n\n\n

Integrations should not overwrite an explicit channel opt-out merely because public is true.

\n\n\n\nExposure is not authorisation\n\n\n\n

The public flag controls discoverability and client exposure. It does not make an ability executable without authorisation, and it does not replace the ability’s permission_callback.

\n\n\n\n

Every ability must continue to implement an appropriate permission check:

\n\n\n\n'permission_callback' => function (): bool {\n\treturn current_user_can( 'manage_options' );\n},\n\n\n\n

An ability with public => true may be visible through a client while still requiring authentication and specific WordPress capabilities to execute.

\n\n\n\n

Developers should not treat public, show_in_rest, or any other exposure flag as a security boundary. Authorisation must be enforced by the ability itself.

\n\n\n\nChanges to resolved metadata\n\n\n\n

In WordPress 7.1, the resolved metadata for every ability includes a boolean public property. It defaults to false when it is not supplied during registration.

\n\n\n\n

For example:

\n\n\n\n$ability = wp_get_ability( 'my-plugin/export-users' );\n$meta = $ability->get_meta();\n\n$is_public = $meta['public']; // Always a boolean in WordPress 7.1.\n\n\n\n

This gives consumers a consistent value to inspect without having to test whether the key exists.

\n\n\n\n

The new property is also declared in the REST API’s ability metadata schema, allowing REST clients to inspect the general exposure intent.

\n\n\n\nBackward compatibility\n\n\n\n

The change does not alter the signature or return value of wp_register_ability() or other Abilities API functions.

\n\n\n\n

Existing channel-specific registrations continue to work:

\n\n\n\n'meta' => array(\n\t'show_in_rest' => true,\n),\n\n\n\n

An explicit show_in_rest value remains authoritative. Plugins are not required to replace it with public.

\n\n\n\n

Abilities that previously supplied neither public nor show_in_rest remain unavailable through REST. Their resolved metadata now contains public => false, but their exposure behaviour is unchanged.

\n\n\n\n

Developers should consider migrating from show_in_rest => true to public => true when an ability is generally intended for use by multiple client types. Continue using show_in_rest directly when exposure is intentionally limited to REST or when overriding the general policy.

\n\n\n\nExisting Core abilities\n\n\n\n

The following abilities included with WordPress now use meta.public instead of setting meta.show_in_rest directly:

\n\n\n\n\ncore/get-site-info\n\n\n\ncore/get-user-info\n\n\n\ncore/get-environment-info\n\n\n\n\n

Their REST availability has not changed. Because public => true supplies the default for show_in_rest, these abilities remain exposed through REST as before.

\n\n\n\n

Using the high-level flag also allows other client integrations to recognise that these Core abilities are intended for external use.

\n\n\n\nWhen to use each flag\n\n\n\n

Use public when the ability is generally intended for consumption by external clients.

\n\n\n\n

Use a channel-specific flag when:

\n\n\n\n\nThe ability should be exposed through only that channel.\n\n\n\nThe ability needs to opt out of a channel despite being generally public.\n\n\n\nA client integration provides behaviour that cannot be represented by the general flag.\n\n\n\n\n

The change was introduced in changeset [62729], with Core abilities migrated in changeset [62737]. See Trac ticket #65568 for the complete discussion.

\n\n\n\n

Props to @gziolo and @benjamin_zekavica for peer review.

\n\n\n\n

\n

#abilities-api, #7-1, #dev-notes, #dev-notes-7-1, #rest-api

", "id": 17048760, "pubDate": "Tue, 04 Aug 2026 12:49:37 GMT", "whenReceived": "Tue, 04 Aug 2026 13:22:53 GMT", "whenUpdated": "Wed, 05 Aug 2026 17:00:49 GMT", "likes": [], "metadata": { "wpPostId": 125285, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 04 Aug 2026 13:02:26 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69277", "title": "Agenda: Weekly Polyglots Chat – August 5, 2026 (7:00 UTC)", "link": "https://make.wordpress.org/polyglots/2026/08/04/agenda-weekly-polyglots-chat-august-5-2026/", "description": "

This meeting will be held by text chat at Wednesday, August 5, 2026, 07:00 GMT in the #polyglots channel in the Making WordPress Slack.

\n\n\n\n\nWelcome\n\n\n\nWeekly Locale Stats\n\n\n\nRelease\n\nWordPress 7.1 Release Party Schedule
(RC1: Aug 5 Today, RC2: Aug 12, final release: Aug 19 at WordCamp US)\n\n\n\n\n\nHelp & Feedback Wanted\n\nCall for Polyglots Meeting Facilitators – Join Us in Leading the Conversation! – We’re still looking for a volunteer to help facilitate the Europe-timezone weekly chat. The next Europe slot is Aug 12, 13:00 UTC.\n\n\n\n\n\nOpen floor / Achievement\n\n\n\n\n

If you have any additions to the agenda, please share them in the comments!
Also — if there’s anything you think we should be tracking or discussing that’s
not listed here, please flag it in the comments too. Always happy to expand this.

\n\n\n\n

#meeting-agenda, #polyglots-meeting, #weekly-meetings

", "id": 17048289, "pubDate": "Tue, 04 Aug 2026 11:47:47 GMT", "whenReceived": "Tue, 04 Aug 2026 13:02:26 GMT", "whenUpdated": "Tue, 04 Aug 2026 13:02:26 GMT", "likes": [], "metadata": { "wpPostId": 69277, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Tue, 04 Aug 2026 11:41:20 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124861", "title": "Miscellaneous Editor Changes in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/08/04/miscellaneous-block-editor-changes-in-wordpress-7-1/", "description": "

In this post, you will find dev notes for smaller changes to the editor in WordPress 7.1.

\n\n\n\n

Table of contents

\n\n\nBlocksNavigation block stops propagating font-size to child itemsTargeting Block Variations in Block TransformsStabilize cloneSanitizedBlock and sanitizeBlockAttributesUpdated Markdown parsing libraryEditorTemplate parts can opt out of content-only editingGlobal StylesBlock-level preset classes now match root-level specificityCore DataNon-paginated entities now return all recordsDeprecating legacy editor packages@wordpress/nux: Now a no-op compatibility package@wordpress/reusable-blocks: Public APIs now log deprecation warnings\n\n\nBlocks\n\n\n\n\nNavigation block stops propagating font-size to child items\n\n\n\n

The Navigation block will no longer forcefully propagate its font-size configurations down to the markup of individual child blocks (core/navigation-link, core/navigation-submenu, core/page-list, and core/home-link).

\n\n\n\n

Currently, font size is propagated to every navigation item. Because relative units multiply against their parent container’s computed size, this caused extreme compounding (e.g., 1.5em → 2.25em → 3.375em), severely breaking the layout of deeply nested dropdown menus.

\n\n\n\n

By removing the explicit application on child items, the Navigation block now safely relies on standard CSS text inheritance. This fixes an issue where the editor canvas and the frontend displayed mismatched typography sizes when child links had their own explicit font sizes overridden by parent propagation.

\n\n\n\n

As for backwards compatibility, theme developers can restore the legacy font-size propagation behavior by applying the following filter in their functions.php:

\n\n\n\n/**\n * Restores font size classes on Navigation child blocks.\n * Use this if your theme targets has-{slug}-font-size on nav items directly.\n */\nfunction restore_nav_item_font_size( $block_content, $parsed_block, $block ) {\n $context = $block->context;\n\n $has_named_font_size = array_key_exists( 'fontSize', $context );\n $has_custom_font_size = isset( $context['style']['typography']['fontSize'] );\n\n if ( ! $has_named_font_size && ! $has_custom_font_size ) {\n return $block_content;\n }\n\n $target_tag = 'core/page-list' === $block->name ? 'UL' : 'LI';\n\n $processor = new WP_HTML_Tag_Processor( $block_content );\n\n if ( ! $processor->next_tag() || $target_tag !== $processor->get_tag() ) {\n return $block_content;\n }\n\n if ( $has_named_font_size ) {\n $processor->add_class( sprintf( 'has-%s-font-size', $context['fontSize'] ) );\n } elseif ( $has_custom_font_size ) {\n $existing_style = $processor->get_attribute( 'style' ) ?? '';\n $font_size_style = sprintf(\n 'font-size: %s;',\n wp_get_typography_font_size_value(\n array( 'size' => $context['style']['typography']['fontSize'] )\n )\n );\n $processor->set_attribute( 'style', $existing_style . $font_size_style );\n }\n\n return $processor->get_updated_html();\n}\n\nadd_filter( 'render_block_core/navigation-link', 'restore_nav_item_font_size', 10, 3 );\nadd_filter( 'render_block_core/navigation-submenu', 'restore_nav_item_font_size', 10, 3 );\nadd_filter( 'render_block_core/home-link', 'restore_nav_item_font_size', 10, 3 );\nadd_filter( 'render_block_core/page-list', 'restore_nav_item_font_size', 10, 3 );\n\n\n\n

References:

\n\n\n\n\nNavigation block: Stop font size setup propagation to children blocks (causes font size multiplication issue!)\n\n\n\nPrevent font-size propagation in Navigation items causing em compounding\n\n\n\n\n\n\nTargeting Block Variations in Block Transforms\n\n\n\n

It’s now possible to target a specific block variation in a block transform, via the optional variationName property:

\n\n\n\ntransforms: {\n\tto: [\n\t\t{\n\t\t\ttype: 'block',\n\t\t\tblocks: [ 'core/group' ],\n\t\t\tvariationName: 'group-grid',\n\t\t\ttransform: ( attributes, innerBlocks ) => {\n\t\t\t\treturn createBlock(\n\t\t\t\t\t'core/group',\n\t\t\t\t\t{\n\t\t\t\t\t\t...attributes,\n\t\t\t\t\t\tlayout: { type: 'grid' },\n\t\t\t\t\t},\n\t\t\t\t\tinnerBlocks\n\t\t\t\t);\n\t\t\t},\n\t\t},\n\t],\n}\n\n\n\n

For programmatic transforms, switchToBlockType now accepts the target variation name as an optional third argument:

\n\n\n\nswitchToBlockType( blocks, 'core/group', 'group-grid' );\n\n\n\n

References:

\n\n\n\n\nAdd Transform from Columns -> Grid\n\n\n\nTry allowing transforms to a variation of another block\n\n\n\n\n\n\nStabilize cloneSanitizedBlock and sanitizeBlockAttributes\n\n\n\n

The @wordpress/blocks package and wp.blocks global have two functions, __experimentalCloneSanitizedBlock and __experimentalSanitizeBlockAttributes.

\n\n\n\n

These functions will continue to work in WordPress 7.1, but they will now log deprecation messages to the console. The functions have been replaced with stable versions that do not have the __experimental prefix.

\n\n\n\n

Developers should replace any usage of __experimentalCloneSanitizedBlock with cloneSanitizedBlock and __experimentalSanitizeBlockAttributes with sanitizeBlockAttributes.

\n\n\n\n

References:

\n\n\n\n\nBlocks package: Stabilize cloneSanitizedBlock and sanitizeBlockAttributes\n\n\n\n\n\n\nUpdated Markdown parsing library\n\n\n\n

@wordpress/blocks replaced showdown with marked for parsing pasted Markdown. The parser is internal to pasteHandler() and was never exported, so no code changes are needed.

\n\n\n\n

Output should be equivalent, but edge cases now follow the CommonMark and GFM specs. Consumers calling pasteHandler() directly should re-test representative Markdown input against the blocks it produces.

\n\n\n\n

References:

\n\n\n\n\nBlocks: Migrate Markdown converter from showdown to marked\n\n\n\n\nEditor\n\n\n\n\n\nTemplate parts can opt out of content-only editing\n\n\n\n

WordPress 7.1 introduces a disableContentOnlyForTemplateParts editor setting, letting themes and plugins restore standard block editing for Template Parts instead of the content-only editing used by default.

\n\n\n\n

Set it via the block_editor_settings_all filter in PHP:

\n\n\n\nadd_filter( 'block_editor_settings_all', function ( $settings ) {\n\t$settings['disableContentOnlyForTemplateParts'] = true;\n\treturn $settings;\n} );\n\n\n\n

Or at runtime from JavaScript:

\n\n\n\nwp.data.dispatch( 'core/block-editor' ).updateSettings( {\n\tdisableContentOnlyForTemplateParts: true,\n} );\n\n\n\n

When the editor is in template-locked rendering mode, content-only editing for Template Parts is always disabled regardless of this setting.

\n\n\n\n

There is no impact on backward compatibility: leaving the setting unset preserves the existing default behavior.

\n\n\n\n

For a session-only toggle while editing, the command palette also offers an “Enable/Disable content-only editing for patterns and template parts” command.

\n\n\n\n

References:

\n\n\n\n\nBlock Editor: disableContentOnlyForTemplateParts cannot be overridden via PHP filter\n\n\n\nBlock Editor: Allow overriding disableContentOnlyForTemplateParts setting\n\n\n\n\n\nGlobal Styles\n\n\n\n\nBlock-level preset classes now match root-level specificity\n\n\n\n

WordPress 7.1 lowers the CSS specificity of the preset utility classes (.has-*-color, -background-color, -border-color, -gradient-background, -font-size, -font-family) generated for block-level presets, so they match the specificity of top-level (root) presets.

\n\n\n\n

Presets defined at the block level, that is, via theme.json settings.blocks.<block> or the wp_theme_json_data_* filters, used to prepend the block selector to the preset class, raising its specificity above top-level presets.

\n\n\n\n

The block selector is now wrapped in :where(), which contributes no specificity.

\n\n\n\n

Before:

\n\n\n\n.has-accent-color { color: … !important; } /* top level: 0-1-0 */\np.has-accent-color { color: … !important; } /* block level: 0-1-1 */\n.wp-block-group.has-accent-color { color: … !important; } /* block level: 0-2-0 */\n\n\n\n

After:

\n\n\n\n:where(p).has-accent-color { color: … !important; } /* 0-1-0 */\n:where(.wp-block-group).has-accent-color { color: … !important; } /* 0-1-0 */\n\n\n\n

Scoping is unchanged. The rule still only matches the class on/within that block. Top-level presets are unchanged.

\n\n\n\n

The reason for the change is that block-level presets out-ranking top-level ones was inconsistent and broke the responsive style states also landing in 7.1. Preset classes and responsive state styles both use !important, so specificity picked the winner. For example, a block-level palette colour set for Desktop overrode one set for Mobile. At equal specificity the responsive rule now wins on source order, as intended.

\n\n\n\n

Affected are themes and plugins that register block-level presets and depend on their former, higher specificity. For example custom CSS written to slot between a top-level and a block-level preset. Such rules now tie block-level presets at 0-1-0.

\n\n\n\n

The risk of regression is relatively contained because:

\n\n\n\n\npresets flow through CSS variables, so only collision tie-breaks change, not rendered values.\n\n\n\nonly !important author CSS ever competed with presets, and the drop is a single component in each case: 0-1-1 to 0-1-0 for element-based block selectors, 0-2-0 to 0-1-0 for class-based ones.\n\n\n\n:where() is already used throughout Gutenberg to manage specificity.\n\n\n\nRealistic collisions are dominated by the responsive-states bug this fixes. Responsive states are new to 7.1.\n\n\n\n\n

References:

\n\n\n\n\n7.1 Bug when using JSON filter for text colors in Responsive style states for blocks\n\n\n\nTheme JSON: Level block-level preset class specificity with :where()\n\n\n\n\nCore Data\n\n\n\n\n\nNon-paginated entities now return all records\n\n\n\n

Several REST API endpoints ignore the page and per_page collection parameters and always return the entire collection. getEntityRecords() applied client-side pagination to every entity, slicing responses to the default per_page of 10 and ignoring remaining records. That was a bug.

\n\n\n\n

The unintended behavior has been corrected: slicing now only happens for entities that declare supportsPagination: true, and everything else returns the full collection.

\n\n\n\n

The common per_page: -1 workaround is no longer necessary, though passing it remains harmless. If you were getting a short list back from one of these entities, you’ll now get all of them, so take a look anywhere you render or loop over the results without setting your own limit. Custom entities backed by a non-paginated REST route should declare supportsPagination: false.

\n\n\n\n

References:

\n\n\n\n\ngetPostTypes() limited to 10\n\n\n\nCore Data: Fix incorrect pagination for non-paginated entities\n\n\n\n\n\nDeprecating legacy editor packages\n\n\n\n\n@wordpress/nux: Now a no-op compatibility package\n\n\n\n

Starting in WordPress 7.1, the @wordpress/nux package becomes a no-op compatibility package.

\n\n\n\n

The package has been deprecated since WordPress 5.4. It remains available so existing imports and script dependencies do not break, but it no longer displays tips or guides.

\n\n\n\n

If you still rely on NUX for onboarding, migrate to the Guide component from @wordpress/components instead.

\n\n\n\n

References:

\n\n\n\n\nMake @wordpress/nux a no-op compatibility package\n\n\n\n\n\n\n@wordpress/reusable-blocks: Public APIs now log deprecation warnings\n\n\n\n

The @wordpress/reusable-blocks package components and data APIs will log deprecation warnings starting from WordPress 7.1.

\n\n\n\n

The package only exposed experimental APIs, and it hasn’t been used by the core since 2023. If your code needs to fetch or update Synced Patterns (formerly known as Reusable Blocks) on the client side, use the standard core entity methods.

\n\n\n\n

This deprecation prepares the packages for a no-op backward compatibility update, similar to @wordpress/nux.

\n\n\n\n

References:

\n\n\n\n\nDeprecate @wordpress/reusable-blocks public APIs\n\n\n\n\n\n

Props to @ellatrix, @isabel_brison, @mamaduka, @ramonopoly, @sarthaknagoshe2002, @talldanwp, and @0mirka00 for content, and to @ramonopoly and @tyxla for review.

\n

#7-1, #dev-notes, #dev-notes-7-1

", "id": 17046500, "pubDate": "Tue, 04 Aug 2026 11:10:09 GMT", "whenReceived": "Tue, 04 Aug 2026 11:41:20 GMT", "whenUpdated": "Wed, 05 Aug 2026 17:00:49 GMT", "likes": [], "metadata": { "wpPostId": 124861, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 04 Aug 2026 06:11:02 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69272", "title": "PTE Request for NotifReach: Push Notifications", "link": "https://make.wordpress.org/polyglots/2026/08/04/pte-request-for-notifreach-push-notifications/", "description": "

I am the plugin author for NotifReach: Push Notifications.

\n

I have translated my plugin in French (fr_FR) and submitted all the translations, but it is waiting to be approved. I’d like to be able to approve translations for this plugin and the other ones to come. Please add the following WordPress.org users as translation editors for their respective locales:
\nLink to the plugin URL:

\n\nhttps://wordpress.org/plugins/notifreach-push-notifications\n\n\n\n #fr_FR – @icodeplugins\n\n\n

If you have any questions, just comment here. Thank you!

\n

#editor-requests

", "id": 17042074, "pubDate": "Tue, 04 Aug 2026 06:02:44 GMT", "whenReceived": "Tue, 04 Aug 2026 06:11:02 GMT", "whenUpdated": "Tue, 04 Aug 2026 06:11:02 GMT", "likes": [], "metadata": { "wpPostId": 69272, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Tue, 04 Aug 2026 04:13:56 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125265", "title": "Dev Chat Agenda – August 4, 2026", "link": "https://make.wordpress.org/core/2026/08/04/dev-chat-agenda-aug-04-2026/", "description": "

The next WordPress Developers Chat will take place on Tuesday, August 4, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

\n\n\n\n

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

\n\n\n\n

The various curated agenda sections below refer to additional items. If you have ticket requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

\n\n\n\nAnnouncements \n\n\n\n

Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

\n\n\n\n7.1\n\n\n\n\n7.1 Beta 4 was released on July 29, 2026\n\n\n\n7.1 RC1 is scheduled for release on Wednesday August 5, 2026\n\n\n\nNew 7.1 Dev Notes:\n\nNew execution lifecycle filters for the Abilities API\n\n\n\njQuery UI updated to 1.14.2\n\n\n\nFiltering Site Editor Screens\n\n\n\nDesign System Theming\n\n\n\nAbilities API improvements\n\n\n\nJSON Schema preparation for client compatibility\n\n\n\nIframed editor changes\n\n\n\nChanges to row headers in post list tables\n\n\n\nName and info tooltips\n\n\n\n\n\n\nGeneral\n\n\n\n\nDefensive Data Design\n\n\n\nLeaner, steadier PHPUnit runs for upcoming releases\n\n\n\n\n\nDiscussions \n\n\n\n

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

\n\n\n\n\n\nOpen floor  \n\n\n\n

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

\n\n

#7-1, #agenda, #core, #dev-chat

", "id": 17040882, "pubDate": "Tue, 04 Aug 2026 03:34:42 GMT", "whenReceived": "Tue, 04 Aug 2026 04:13:56 GMT", "whenUpdated": "Tue, 04 Aug 2026 04:13:56 GMT", "likes": [], "metadata": { "wpPostId": 125265, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/test/feed/", "whenReceived": "Tue, 04 Aug 2026 03:55:58 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/?p=12531", "title": "Month in Test: August 03, 2026", "link": "https://make.wordpress.org/test/2026/08/04/month-in-test-august-03-2026/", "description": "

Hello and welcome to another edition of Month in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

\n\n\n\n

Table of Contents

\n\n\n\n\nCalls for Testing \n\n\n\nTest Handbook\n\nMerging of Test Handbook in Github\n\n\n\n\n\nWeekly Testing Roundup \n\n1. WordPress Core Testing\n\na. Patch Testing \n\n\n\nb. Bug Reproduction\n\n\n\nc. Test Team Issues\n\n\n\n\n\n2. Gutenberg Testing\n\na. Gutenberg Bug Reproduction Testing\n\n\n\nb. Gutenberg Patch Testing\n\n\n\n\n\n\n\nProfile Badge Awards \n\n\n\nRead/Watch/Listen \n\n\n\nUpcoming Meetings \n\n\n\n\nCalls for Testing \n\n\n\n

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

\n\n\n\n\nHelp Test WordPress 7.1 Beta 4\n\n\n\nCall for Testing: Responsive Styling\n\n\n\nMedia Editor Modal: call for testing\n\n\n\nWordPress 7.0 Updates & Testing – FAQ\n\n\n\nCall for Testing: client-side media processing\n\n\n\nHelp test new career functionality on WordPress.org\n\n\n\n\nTest Handbook \n\n\n\nMerging of Test Handbook in Github\n\n\n\n

For the last few months, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

\n\n\n\n\nWe want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.\n\n\n\nFeel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.\n\nYou can send a PR with the fix, or simply send the issue, and we will check it\n\n\n\n\n\n\nWeekly Testing Roundup \n\n\n\n

Bi-Weekly update: Test Team Update

\n\n\n\n

Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to the Test Team are also a fantastic way to level up your WordPress knowledge and skills? Dive in to contribute, and gain coveted props  for a coming release.

\n\n\n\n1. WordPress Core Testing\n\n\n\na. Patch Testing \n\n\n\n

Who? All contributors (not just developers) who can set up a local testing environment. Why?
It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

\n\n\n\n

The following tickets (15) have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

\n\n\n\n\n#64707 – Site Health: Opcode cache test reports a false negative when OPcache runs in file-cache-only mode\n\n\n\n#65515 – ThickBox ReferenceError: imgLoader is not defined due to “use strict” contamination in load-scripts.php\n\n\n\n#63256 – Unnecessary array_map() call in get_terms() when object_ids is not set\n\n\n\n#65051 – $_REQUEST[‘term’] used unsanitized in user search query\n\n\n\n\nb. Bug Reproduction\n\n\n\n

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

\n\n\n\n

The following tickets (133) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:

\n\n\n\n\n#60478 – Upgrade to jQuery 4.0\n\n\n\n#65626 – 7.0.1 9.9797 lagging at WP_Query->get_posts() on site with 16K= posts\n\n\n\n#17382 – XMLRPC wp_getUsersBlogs Scalability\n\n\n\n#65480 – Custom HTML Block hangs when switching tabs and scrolling (Gutenberg/WordPress 7.0)\n\n\n\n#65381 – Uncaught TypeError: Cannot read properties of undefined (reading ‘borderColor’) in block-editor.min.js on WordPress 7.0\n\n\n\n\nc. Test Team Issues\n\n\n\n

Here are the current activities being discussed in the Test Team Github:

\n\n\n\n\nWe need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.\n\n\n\n\n\nTest Team Discussions (8 Open)\n\nRecognize WordPress 7.0 Test Contributors — Badge Awards & Blog Post\n\n\n\nProposal: Building a Test Chat and Bug Scrub Facilitator Plugin\n\n\n\nProposal: Restructure Test Handbook to Support Multiple Testing Domains\n\n\n\nDiscussion: Using tags instead of categories for regular post types on make.wordpress.org/test\n\n\n\nEnd-to-end (E2E) testing\n\n\n\n\n\n\n2. Gutenberg Testing\n\n\n\n

Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

\n\n\n\na. Gutenberg Bug Reproduction Testing\n\n\n\n

The following tickets (14) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

\n\n\n\n\ngetQueryArgs discards everything after the second = in a query argument value\n\n\n\nText in Gutenberg UI intermittently appears blurry in Chromium-based browsers\n\n\n\nScroll gets stuck when cursor is over the in-between block inserter (possible regression of #63260)\n\n\n\nSticky Post does not work correctly with loop (2 issues!)\n\n\n\nNotes: Backtick markdown code formatting strips/deletes pasted text content upon saving\n\n\n\n\nb. Gutenberg Patch Testing\n\n\n\n

All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

\n\n\n\n

The following tickets (1) have been reviewed, and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

\n\n\n\n\nSuggest mode: combined feature branch for Playground testing (draft)\n\n\n\n\nProfile Badge Awards \n\n\n\n

Congratulations to the recipients of the Test Contributor Badge

\n\n\n\n

@khushdoms, @jsmansart, @ankitkumarshah, @soyebsalar01, @poojapadamad, @gaurangsondagar, @manhar, @westonruter, @khushi1501

\n\n\n\n

– Kindly find the Contribution Guidelines here

\n\n\n\nRead/Watch/Listen \n\n\n\n\nWordPress Ecosystem Announcements\n\nWordPress 7.1 Beta 4\n\n\n\nWhat’s new in Gutenberg 23.5? (July 1, 2026)\n\n\n\nMerge Proposal: Expanding WordPress Core Abilities\n\n\n\nBug Scrub Schedule for WordPress 7.1\n\n\n\nThe Classic block stays in the inserter for WordPress 7.1\n\n\n\nMerge Proposal: Design System Theming\n\n\n\nTransitioning To Rulesets In The Gutenberg Repository\n\n\n\nConsistent navigation in WordPress 7.1 with persistent toolbar\n\n\n\nHardening GitHub Actions workflows across the WordPress organisation\n\n\n\nWhat’s new for developers (July 2026)\n\n\n\nOn-brand maintenance mode for WordPress Block Themes\n\n\n\nWordPress 7.0.2 is now available.\n\n\n\n\n\nTest Team Announcements\n\nWeekly Patch Testing Scrub: Second and Fourth Thursday of the Month at 15:00 UTC\n\n\n\nWeekly Test Chat: Third Thursday of the Month at 15:00 UTC\n\n\n\nMonthly Voice Test Chat: First Thursday of each month at 15:00 UTC\n\n\n\n\n\nCall for Testing\n\nHelp Test WordPress 7.1\n\n\n\nMedia Editor Modal: call for testing\n\n\n\nCall for Testing: client-side media processing\n\n\n\nHelp test new career functionality on WordPress.org\n\n\n\nCall for Testing: Responsive Styling\n\n\n\nWe have Patch Testing issues for the WordPress 7.0.3 milestone that need testing.\n\n\n\nWe also have a couple of Gutenberg Issues that need testing.\n\n\n\n\n\n\nUpcoming Meetings \n\n\n\n

There will be regular #core-test meetings. The schedule is being worked on and final schedule will be shared after finalizing the discussion

\n\n\n\n

Current 2026 Schedule:

\n\n\n\n\nThursday, 6 August 2026, 03:00 PM UTC – <voice-test-chat> in #core-test.\n\n\n\nThursday, 13 August 2026, 03:00 PM UTC – <Patch-testing-Scrub> in #core-test.\n\n\n\n\n

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

\n\n\n\n

props to @sajib1223 @huzaifaalmesbah @nikunj8866 for peer reviewing this post

\n\n\n\n

\n

#core-test, #fse-outreach-program, #gutenberg, #make-wordpress-orgupdates

", "id": 17040650, "pubDate": "Tue, 04 Aug 2026 03:00:00 GMT", "whenReceived": "Tue, 04 Aug 2026 03:55:58 GMT", "whenUpdated": "Tue, 04 Aug 2026 08:42:53 GMT", "likes": [], "metadata": { "wpPostId": 12531, "wpSiteId": 255400204 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed/", "whenReceived": "Tue, 04 Aug 2026 02:02:00 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed/", "guid": "https://make.wordpress.org/core/?p=125273", "title": "Defensive Data Design", "link": "https://make.wordpress.org/core/2026/08/04/defensive-data-design/", "description": "

As we go into a world where agents will be doing more things, how can we make the defaults as safe (and secure) as possible? Some points to consider:

\n\nPutting something in the trash should be easy; deleting should be very hard.\nProposing a draft should be easy; publishing to the world should be hard.\nChanges should be reversible and visible wherever possible.\nHow can we show the data behind the object in a way that makes it more legible and understandable, not less?\nError messages should be how you’d describe it to a friend. And have a copy-to-clipboard next to it, so people can put into search/AI/whatever.\nIf you error out, say the why not just the what.\nFail gracefully, in a way that minimizes harm or exposure.\nAssume everything (networking / formatting / structure) is not just unreliable, but actually hostile.\nUse the space you have, don’t make people click when you could have shown them something directly.\nPlain language, make it obvious, natural. (And also fun.)", "id": 17039315, "pubDate": "Tue, 04 Aug 2026 01:06:46 GMT", "whenReceived": "Tue, 04 Aug 2026 02:02:00 GMT", "whenUpdated": "Tue, 04 Aug 2026 02:02:00 GMT", "likes": [], "metadata": { "wpPostId": 125273, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 03 Aug 2026 23:25:55 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69265", "title": "PTE Request for BumpMint -…", "link": "https://make.wordpress.org/polyglots/2026/08/03/pte-request-for-bumpmint/", "description": "

PTE Request for BumpMint – Order Bump for WooCommerce

\n

Hello Polyglots,

\n

I am the plugin author of BumpMint – Order Bump for WooCommerce. I have submitted the Brazilian Portuguese translations for the plugin, which are currently waiting for review.

\n

I would like to request a translation review and PTE access so I can maintain the Brazilian Portuguese translations as the plugin evolves.

\n\nhttps://wordpress.org/plugins/bumpmint-order-bump-for-woocommerce/\n\n\n\n #pt_BR – @andrewaires\n\n\n

Thank you very much!

\n

#editor-requests

", "id": 17037394, "pubDate": "Mon, 03 Aug 2026 21:42:29 GMT", "whenReceived": "Mon, 03 Aug 2026 23:25:55 GMT", "whenUpdated": "Mon, 03 Aug 2026 23:25:55 GMT", "likes": [], "metadata": { "wpPostId": 69265, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69257", "title": "PTE Request for Init Plugin Suite (12 plugins)", "link": "https://make.wordpress.org/polyglots/2026/08/03/pte-request-for-init-plugin-suite-12-plugins/", "description": "

I am the plugin author for the following plugins. I would like to become PTE for the Vietnamese locale so I can review and approve translations myself.

\n\nhttps://wordpress.org/plugins/init-ad-engine/\n\nhttps://wordpress.org/plugins/init-chat-engine/\n\nhttps://wordpress.org/plugins/init-content-protector/\n\nhttps://wordpress.org/plugins/init-embed-posts/\n\nhttps://wordpress.org/plugins/init-fx-engine/\n\nhttps://wordpress.org/plugins/init-live-search/\n\nhttps://wordpress.org/plugins/init-pulse-for-discord/\n\nhttps://wordpress.org/plugins/init-reading-position/\n\nhttps://wordpress.org/plugins/init-recent-comments/\n\nhttps://wordpress.org/plugins/init-review-system/\n\nhttps://wordpress.org/plugins/init-user-engine/\n\nhttps://wordpress.org/plugins/init-view-count/\n\n\n\n #vi – @brokensmile2103-1\n\n\n

If you have any questions, just comment here. Thank you!

\n

#editor-requests

", "id": 17035631, "pubDate": "Mon, 03 Aug 2026 21:42:19 GMT", "whenReceived": "Mon, 03 Aug 2026 21:45:20 GMT", "whenUpdated": "Mon, 03 Aug 2026 21:45:20 GMT", "likes": [], "metadata": { "wpPostId": 69257, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://developer.wordpress.org/news/feed/", "whenReceived": "Mon, 03 Aug 2026 21:42:33 GMT", "items": [ { "feedUrl": "https://developer.wordpress.org/news/feed/", "guid": "https://developer.wordpress.org/news/?p=6338", "title": "Rethinking do_action(): Events as objects, hooks as class names", "link": "https://developer.wordpress.org/news/2026/08/rethinking-do_action-events-as-objects-hooks-as-class-names/", "description": "

For a recent project, I explored the concept of building an event dispatcher for WordPress following the PSR-14 standard. You may be asking why I would even attempt that when WordPress already has its own system that dispatches events, called actions.

\n\n\n\n

It was part fun exploration, part for my own edification. And I learned a lot along the way.

\n\n\n\n

If you build on top of WordPress, you’ve used do_action(). You might have called it a hundred times. Maybe even thousands. And you’ve probably written custom hooks in your own plugins and themes so other code can hang behavior off yours. It’s one of the oldest extensibility tricks in WordPress, and it still works as beautifully as it did when it was introduced in WordPress 1.2.0.

\n\n\n\n

But somewhere along the way, we all quietly accepted a few rough edges as just “how hooks work.”

\n\n\n\n

A tiny change to how you call do_action() — passing a plain object instead of a fistful of arguments — smooths every one of them out. It needs no custom library. No framework. No new dependency. Just a better default for a function you already use.

\n\n\n\n

As I explored my own event dispatcher, it turned out that nearly all the value lived in one small habit. Let me walk through what I mean.

\n\n\n\n\n

Table of Contents

\n\n\nThe hooks to tolerateThe one-line ideaNaming the hook: the class, or a custom stringDispatching an event-based hookListening to an event-based hookWhat the event object bought youAn old idea that WordPress had earlyHow far this approach can take youWhere to go from here\n\n\n\nThe hooks to tolerate\n\n\n\n

Suppose you’re building a plugin that registers new members. Let’s look at examples of a couple of custom hooks that might appear in that plugin.

\n\n\n\n

First, you might that announce that a registration happened:

\n\n\n\ndo_action( 'myplugin_member_registered', $userId, $plan );\n\n\n\n

And another plugin might listen:

\n\n\n\nadd_action( 'myplugin_member_registered', static function ( $userId, $plan ) {\n\t// ...\n}, 10, 2 );\n\n\n\n

Second, your plugin needs an answer back, not just a notice: should this member get a welcome email? That’s a decision, so you apply filters instead:

\n\n\n\n$sendWelcomeEmail = apply_filters( 'myplugin_send_welcome_mail', true, $userId, $plan );\n\nif ( $sendWelcomeEmail ) {\n\t// ...queue the welcome email.\n}\n\n\n\n

And another plugin listens, changing the value based on the arguments provided:

\n\n\n\nadd_filter( 'myplugin_send_welcome_email', static function ( $send, $userId, $plan ) {\n\tif ( 'free' === $plan ) {\n\t\t$send = false;\n\t}\n\n\treturn $send;\n}, 10, 3 );\n\n\n\n

Both of these techniques are fine, and they’re on par with how WordPress itself fires its own hooks. They’re also carrying the same small annoyances that’s easy to stop noticing:

\n\n\n\n\nThe arguments are positional: Was the order $userId, $plan or $plan, $userId? How many were there? You have to go read the call to be sure, and remember to pass 10, 2 (or 10, 3 for the filter) so that every argument gets passed along.\n\n\n\nThe name lives in the global scope: myplugin_member_registered and myplugin_send_welcome_mail each share one flat namespace with every other plugin on the site. You prefix them and hope.\n\n\n\nNothing is typed: $plan could be anything, such as a string, an ID, an object. Most code editors can’t help you, because as far as they know, it’s just a variable named $plan.\n\n\n\n\n

The filter adds a fourth papercut all its own: you have to remember to return the value. If you forget return $send;, it breaks any filter along the chain, and it’s hard to trace the problem back to the filter you added.

\n\n\n\n

None of these are hook problems. They’re payload problems, and they show up whether the hook is an action or a filter. A hook can carry a single object just as easily as it can carry multiple loose arguments. And an object fixes all of it at once.

\n\n\n\nThe one-line idea\n\n\n\n

Instead of passing loose arguments, pass one object that describes what happened. And instead of inventing a string name, use the object’s own class name as the hook:

\n\n\n\ndo_action( $event::class, $event );\n\n\n\n

That’s the whole idea. The payload of the hook is now a single, typed object. The name is the class of that object, so it’s namespaced by construction. No other plugin’s FullyQualified\\ClassName is going to collide with yours without a fatal error.

\n\n\n\n

Notice this is still do_action(), not apply_filters(). That’s not an oversight. Part of the merit of this technique is that a mutable property on the event can stand in for whatever a filter’s return value would otherwise carry, minus the return-discipline problem the filter version has. We’ll watch that play out with the welcome-email decision in a moment.

\n\n\n\nNaming the hook: the class, or a custom string\n\n\n\n

There are two good ways to name the hook, and the choice comes down to a single question: do you want a name that’s guaranteed never to change?

\n\n\n\n

Every hook in WordPress is global. Anyone can call add_action() on any name. So this isn’t about who’s allowed to listen; it’s about whether the name stays put when you refactor.

\n\n\n\n

Use the class name when you’re fine with the hook name tracking the class:

\n\n\n\ndo_action( MemberRegistered::class, $event );\n\n\n\n

It’s zero ceremony, it’s namespaced for free, and when you rename or move the class, your IDE renames the hook right along with it. The catch is exactly that: the tag is the class path, so the day you move MemberRegistered into another namespace or rename it, the hook name changes too. Then, any add_action() still pointed at the old name silently stops matching. Of course, solid deprecation procedures in your code should mitigate issues like this, but that’s a topic for another day.

\n\n\n\n

Use a custom string when you want the name locked down for good:

\n\n\n\ndo_action( 'myplugin/member-registered', $event );\n\n\n\n

Because the tag is myplugin/member-registered and not the class path, you can rename or relocate MemberRegistered however you like and the hook name never moves. It’s guaranteed to be stable by definition. A listener can hardcode myplugin/member-registered and never reference your class at all.

\n\n\n\n

The rule of thumb: ::class when you don’t mind the name following the class, a fixed string when you want it to never change.

\n\n\n\nDispatching an event-based hook\n\n\n\n

Let’s put together a slimmed down example of registering a new member to showcase how the concept works. It’s small enough to follow in one sitting, and the shape maps onto a signup flow you’ve probably seen before: create the account, announce it, then let listeners decide what happens next.

\n\n\n\n

All the example classes live in one namespace, MyPlugin\\Members, which is what keeps the eventual hook name unique.

\n\n\n\n

First, let’s look at the event itself, which is a plain object. It carries the two facts a listener needs to know (who registered and on what plan) plus one property listeners are allowed to change (whether to send a welcome email):

\n\n\n\nnamespace MyPlugin\\Members;\n\nfinal class MemberRegistered\n{\n\tpublic function __construct(\n\t\tpublic readonly int $userId,\n\t\tpublic readonly string $plan,\n\t\tpublic bool $sendWelcomeEmail = true,\n\t) {}\n}\n\n\n\n

Notice the two kinds of properties:

\n\n\n\n\n$userId and $plan are readonly. This is the context a listener reads to make a decision, not something it should rewrite. \n\n\n\n$sendWelcomeEmail is mutable on purpose: it’s the “answer” the plugin reads back after dispatch, and flipping it off is how a listener says “skip the welcome email for this one.” That’s filter-like behavior coming out of a plain action because the property is writable.\n\n\n\n\n

MemberRegistered is a class like any other. I’ve kept it to public properties because that’s all this event needs, but nothing stops you from giving an event custom methods, exactly as you would with other classes. When you want to guard how a value changes, make the property private and expose a setter that validates it. When a value is derived, add a getter. When listeners keep repeating the same dance, wrap it in a helper method. Public properties are just the basic end of the spectrum, not a special rule for events.

\n\n\n\n

Here’s where the member gets registered and the event goes out: a small registrar class creates the account, then fires the event right after registration, and reads the result back before deciding whether to queue a welcome email:

\n\n\n\nnamespace MyPlugin\\Members;\n\nfinal class MemberRegistrar\n{\n\tpublic function register( int $userId, string $plan ): void\n\t{\n\t\t// ...create the account, assign the plan, etc.\n\n\t\t$event = new MemberRegistered( userId: $userId, plan: $plan );\n\n\t\t// The member is registered. Announce it before anything else\n\t\t// happens, and let anything interested read or adjust it.\n\t\tdo_action( $event::class, $event );\n\n\t\tif ( $event->sendWelcomeEmail ) {\n\t\t\t// ...queue the welcome email.\n\t\t}\n\t}\n}\n\n\n\n

That’s really the technique in a nutshell. You’re just passing a single event object into do_action():

\n\n\n\ndo_action( $event::class, $event );\n\n\n\n

Compare this to the function signature of do_action():

\n\n\n\ndo_action( string $hook_name, mixed ...$arg );\n\n\n\n

$hook_name is just a string, which $event::class satisfies. And $arg is a mixed variadic. So the $event object is passed as $arg[0] with no validation or conversion on WordPress’s end.

\n\n\n\n

Your plugin would naturally have the account-creation and plan-assignment logic in place before this point, and the email-sending logic itself living somewhere else, but that’s outside the scope of the technique described here.

\n\n\n\n

Notice there’s no apply_filters() call anywhere in MemberRegistrar. The $sendWelcomeEmail property is doing that job instead: a listener customizes it, MemberRegistrar reads it back after do_action() has executed, and there’s no return for any listener to forget along the way.

\n\n\n\nListening to an event-based hook\n\n\n\n

Now that you’re passing event objects via action hooks, other code can react using the event object itself. There are two shapes a listener takes, and this pattern supports both.

\n\n\n\n

A listener that observes reads the event and reacts, but leaves it alone. Here, a logging listener records every registration for auditing:

\n\n\n\nuse MyPlugin\\Members\\MemberRegistered;\n\nadd_action( MemberRegistered::class, static function ( MemberRegistered $event ): void {\n\terror_log( sprintf(\n\t\t'Member #%d registered on the %s plan.',\n\t\t$event->userId,\n\t\t$event->plan\n\t) );\n} );\n\n\n\n

It reads $event->userId and $event->plan and reacts, but never touches $sendWelcomeEmail. That’s an observer: it responds to the event without changing it.

\n\n\n\n

And a listener that mutates changes the event, and because objects pass by handle, the MemberRegistrar reads the change back. Here, free-plan members skip the paid welcome sequence without the registrar knowing anything about plans:

\n\n\n\nuse MyPlugin\\Members\\MemberRegistered;\n\nadd_action( MemberRegistered::class, function ( MemberRegistered $event ): void {\n\t// Free-plan members skip the paid welcome sequence.\n\tif ( 'free' === $event->plan ) {\n\t\t$event->sendWelcomeEmail = false;\n\t}\n} );\n\n\n\n

Look at that second listener’s signature: function ( MemberRegistered $event ). Your editor now autocompletes $event->userId and $event->plan. No positional arguments to memorize. No 10, 3 to remember. No guessing what’s in the payload.

\n\n\n\nWhat the event object bought you\n\n\n\n

Step back and count what changed by passing an object instead of loose arguments:

\n\n\n\n\nTyped listeners/actions: Every callback type-hints the event, so you get autocomplete and static analysis on the payload instead of untyped variables you have to trace by hand.\n\n\n\nCollision-free names: The hook is a fully-qualified class name (or a namespaced string of your own). No myplugin_ prefix roulette.\n\n\n\nFilter-like mutation through a plain action: This is the underrated one. A listener can change the event, and because objects pass by handle, the code that dispatched it reads those changes back. And you decide exactly what’s mutable by which properties you leave writable.\n\n\n\n\n

All of that from one convention, using functions that shipped with WordPress years ago.

\n\n\n\n

Assuming you’re following standard PHP coding practice, it’s worth noting each event/hook would have its own file. A side benefit of this is that your extension points become self-documenting. As your code base grows, you may even decide to split them into their own Event or Hook subfolder.

\n\n\n\nAn old idea that WordPress had early\n\n\n\n

If the words event, listener, and dispatcher are ringing a bell, it’s because this is one of the oldest patterns in software design. The broader programming world calls it by various names, depending on who you ask and how you squint. The names change; the idea doesn’t.

\n\n\n\n

One part of a program announces that something happened, and any number of other parts, which the first part knows nothing about, get a chance to respond.

\n\n\n\n\nAn event is an object carrying information about something that happened.\n\n\n\nA listener is any callable that receives the event and reacts.\n\n\n\nA dispatcher hands the event to the listeners.\n\n\n\n\n

That’s essentially how do_action() and add_action() work. And here’s the part I find genuinely remarkable: WordPress has had this since the Plugin API landed in version 1.2, back in 2004. It’s easy to forget how early WordPress bet on extensibility.

\n\n\n\n

Passing a typed object under its own class name isn’t some clever hack bolted onto hooks. It’s the same mental model the rest of the PHP world standardized on in PSR-14, expressed in the API WordPress has had all along. You’re not adopting a new paradigm. You’re finally using the one you’ve been standing on for years, and letting the object carry its weight.

\n\n\n\n

I don’t want to oversell the resemblance. PSR-14 is a formal contract with parts that don’t exist in WordPress. I’ll get to what’s missing in a moment. But the core shape (event, listener, dispatcher) is right there in do_action(), and it always has been.

\n\n\n\nHow far this approach can take you\n\n\n\n

Honestly? This covers the majority of custom hooks you’ll probably ever write. The two genuinely hard problems — safe names and structured, typed payloads — are solved the moment you pass an object under its class name. And for the hooks that would otherwise have been filters, you get a third win for free: no return value for a listener to forget, since the object itself carries the answer.

\n\n\n\n

What you’re not getting (if you go looking) is most of what a formal event system like PSR-14 adds on top:

\n\n\n\n\nPropagation control: a listener saying “stop, no one else runs”. This goes beyond what remove_action() and priorities already give you.\n\n\n\nCustom listener providers that decide which listeners apply to an event.\n\n\n\nSubscriber objects that register a batch of listeners at once (though you could bolt a form of this onto action hooks).\n\n\n\nA swappable dispatcher you can replace wholesale, for example, to capture events in a test.\n\n\n\n\n

Here’s the thing: most hooks never need any of that, and every bit of it can be layered on later without throwing away what you’ve written. You’re not painting yourself into a corner. You’re picking a better default while keeping the door open.

\n\n\n\nWhere to go from here\n\n\n\n

If you find yourself wanting a listener to halt the rest, wiring up dozens of listeners across a large codebase by hand, or wishing you could swap the whole dispatch mechanism for tests, you’ve probably outgrown the convention. From there, it’s worth considering a fuller event system, with a dispatcher, a listener provider, and subscriber classes.

\n\n\n\n

But that’s a decision for the day you actually hit the wall. Until then, the next time you reach for do_action(), try reaching for an event object too. It’s the same hook you already know, just sending a better payload.

\n\n\n\n

Props to @juanmaguitar and @bph for feedback on this post.

", "id": 17035592, "pubDate": "Mon, 03 Aug 2026 21:00:34 GMT", "whenReceived": "Mon, 03 Aug 2026 21:42:33 GMT", "whenUpdated": "Wed, 05 Aug 2026 15:36:36 GMT", "likes": [], "metadata": { "wpPostId": 6338, "wpSiteId": 208500394 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 03 Aug 2026 17:21:47 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69260", "title": "PTE Request for Link Nacional File Browser", "link": "https://make.wordpress.org/polyglots/2026/08/03/title-pte-request-for-link-nacional-file-browser/", "description": "

Hello Polyglots team,

\n

I am the author of Link Nacional File Browser and I would like to request PTE (Project Translation Editor) status for my account to manage and approve the translations.

\n\nPlugin Name: Link Nacional File Browser\n\nSlug: linknacional-file-browser\n\nPlugin URL: https://wordpress.org/plugins/linknacional-file-browser/\n\nWordPress.org Username: @linknacional\n\n\n

I would like to be added as a PTE for the following locale(s):

\n\n #pt_BR (Portuguese – Brazil)\n\n\n

Thank you!

\n

#editor-requests

", "id": 17030063, "pubDate": "Mon, 03 Aug 2026 16:14:06 GMT", "whenReceived": "Mon, 03 Aug 2026 17:21:47 GMT", "whenUpdated": "Mon, 03 Aug 2026 17:21:47 GMT", "likes": [], "metadata": { "wpPostId": 69260, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Mon, 03 Aug 2026 15:44:17 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=125207", "title": "Introducing name and informational tool tips in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/08/03/introducing-name-and-informational-tool-tips-in-wordpress-7-1/", "description": "

WordPress 7.1 comes with two new functions for rendering tool tips and informational help in core. Similar tool tips already exist in the editor, but were not available in the rest of the administration. This change brings improved accessibility for icon-only controls and situations where further explanation of a user interface element is needed.

\n\n\n\n

Inf #51006, two new functions were added: wp_get_tooltip() and wp_get_toggletip().

\n\n\n\n

The first function, wp_get_tooltip(), provides name visibility for buttons or links are otherwise only represented as icons. The second, wp_get_toggletip(), adds a button that can be triggered to view extended information about related controls.

\n\n\n\n

In 7.1, each function has one relevant implementation. wp_get_tooltip() has been implemented on post meta box controls (move up, move down, and show/hide) to make those accessible names visible. wp_get_toggletip() has been added on the main login screen to provide an extended description of what the “Remember Me” checkbox does.

\n\n\n\nEnqueuing Required scripts and styles\n\n\n\n

The required CSS for tooltips is loaded globally, but the JavaScript is only loaded by default where post meta boxes are used and in the login screen.

\n\n\n\n

You can enqueue required CSS on the front-end using:

\n\n\n\n

wp_enqueue_style( 'wp-tooltip' );

\n\n\n\n

You can enqueue required JavaScript as needed using:

\n\n\n\n

wp_enqueue_script( 'wp-tooltip' );

\n\n\n\nAccessibility Notes\n\n\n\n

Both of these functions exist to provide support for gaps in accessibility support. It is always preferable for interface controls to have visible, persistent text labels, and it is also preferable to user interfaces to be structured so that additional help information is not required or is provided as visible descriptive text associated with the relevant input field.

\n\n\n\n

However, we understand that space can be at a premium in complex web interfaces, and it is not always feasible to provide text labels for all controls. It is also a common case that explanatory text does not directly relate to one specific input, so that the aria-describedby solution is not practical. Using these functions can help make sure that the information provided for users is as accessible as possible within an interface that is imposing other limitations.

\n\n\n\nTooltips\n\n\n\n

The function for adding tooltips is wp_get_tooltip(), and is only intended to provide visibility for controls that do not have a visible accessible name. For accessibility, it is still always the more accessible choice for a control to have persistently visible text.

\n\n\n\nParameters for wp_get_tooltip()\n\n\n\n\nstring $content Plain-text tool tip content.\n\n\n\narray $args An array of optional arguments for this tooltip.\n\nstring $id A unique ID for the popover element containing the tooltip. Default is a generated unique ID.\n\n\n\nstring $button Existing button or a markup. Used instead of a generated button.\n\n\n\nstring $label Unused for tool tips, but documented as part of the helper function.\n\n\n\nstring $close_label Unused for tool tips, but documented as part of the helper function.\n\n\n\nstring $icon A dashicons icon class for the toggle button. Default is dashicons-editor-help.\n\n\n\nstring $class Additional classes.\n\n\n\n\n\n\n

No additional arguments are required for wp_get_tooltip(); it will render a button with a tooltip control when only passed the $content argument. The $button parameter is available to make it easier to pass existing controls into the rendering button, and will be processed using the WP_HTML_Tag_Processor to add required attributes.

\n\n\n\nParameters for wp_get_toggletip()\n\n\n\n

The function for adding information help text is intended for exposing additional help information.

\n\n\n\n\nstring $content Plain-text tool tip content.\n\n\n\narray $args An array of arguments for this tooltip.\n\nstring $id A unique ID for the popover element containing the tooltip. Default is a generated unique ID.\n\n\n\nstring $button Existing button or a markup. Used instead of a generated button.\n\n\n\nstring $label Accessible label for the toggle button. Default ‘Help’, matching the default icon. Ignored for tooltips.\n\n\n\nstring $close_label Accessible label for the close button. Default ‘Close’.\n\n\n\nstring $icon A dashicons icon class for the toggle button. Default is dashicons-editor-help.\n\n\n\nstring $class Additional classes.\n\n\n\n\n\n\nExample Usages\n\n\n\nGenerate a button with a tooltip using a menu icon.\n\n\n\nwp_get_tooltip(\n __( 'Show/Hide Menu', 'my-text-domain' ),\n array(\n 'icon' => 'dashicons-menu',\n )\n);\n\n\n\nOutput\n\n\n\n<span class=\"wp-tooltip wp-is-tooltip\">\n <button class=\"wp-tooltip__toggle\" type=\"button\" aria-label=\"Show/Hide Menu\">\n <span class=\"dashicons dashicons-menu\" aria-hidden=\"true\"></span>\n </button>\n <span popover=\"hint\" id=\"wp-tooltip-1\" class=\"wp-tooltip__bubble\" role=\"tooltip\">\n <span id=\"wp-tooltip-1-text\" class=\"wp-tooltip__text\">Show/Hide Menu</span>\n </span>\n</span>\n\n\n\n

Note: All generic markup uses span elements, to ensure that the control can be validly inserted inside any element. Using div or other sectioning elements would disallow usage within a paragraph.

\n\n\n\nGenerate a button with a toggle tip.\n\n\n\nwp_get_toggletip(\n __( 'Selecting \"Remember Me\" reduces the number of times you&#8217;ll be asked to log in using this device. To keep your account secure, use this option only on your personal devices.', 'my-text-domain' ),\n array(\n 'id' => 'rememberme-help-toggletip',\n 'label' => 'Learn More',\n 'icon' => 'dashicons-welcome-learn-more',\n )\n);\n\n\n\nOutput\n\n\n\n<span class=\"wp-tooltip wp-is-toggletip\">\n <button aria-haspopup=\"dialog\" class=\"wp-tooltip__toggle\" popovertarget=\"rememberme-help-toggletip\" type=\"button\" aria-label=\"Learn More\">\n <span class=\"dashicons dashicons-welcome-learn-more\" aria-hidden=\"true\"></span>\n </button>\n <span popover=\"auto\" id=\"rememberme-help-toggletip\" class=\"wp-tooltip__bubble\" role=\"dialog\" aria-label=\"Learn More\" tabindex=\"-1\" autofocus=\"\">\n <span id=\"rememberme-help-toggletip-text\" class=\"wp-tooltip__text\">Selecting \"Remember Me\" reduces the number of times you’ll be asked to log in using this device. To keep your account secure, use this option only on your personal devices.</span>\n <button type=\"button\" class=\"wp-tooltip__close\" popovertarget=\"rememberme-help-toggletip\" popovertargetaction=\"hide\" aria-label=\"Close\">\n <span class=\"dashicons dashicons-no-alt\" aria-hidden=\"true\"></span>\n </button>\n </span>\n</span>\n\n\n\n

Reviewed by @afercia, Props @wongjn

\n

#7-1, #dev-notes, #dev-notes-7-1

", "id": 17027635, "pubDate": "Mon, 03 Aug 2026 15:28:48 GMT", "whenReceived": "Mon, 03 Aug 2026 15:44:17 GMT", "whenUpdated": "Tue, 04 Aug 2026 10:00:09 GMT", "likes": [], "metadata": { "wpPostId": 125207, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed/", "whenReceived": "Mon, 03 Aug 2026 15:55:24 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed/", "guid": "https://make.wordpress.org/core/?p=124832", "title": "Post list tables row headers changed", "link": "https://make.wordpress.org/core/2026/08/03/post-list-tables-row-headers-changed/", "description": "

The column used as the primary list table th with scope=\"row\" was moved from the first column, containing the selection checkbox, to the second column, containing the post title and row actions in #32892.

\n\n\n\n

This change significantly improves accessibility for post list tables by ensuring that the naming used for screen readers to identify the current row refers consistently to the name of the relevant post, rather than referring to a selection checkbox that may not be present if the post is not currently available for editing.

\n\n\n\n

This is expected to have an impact on extenders who assign custom styles or use JavaScript to register events using the th.check-column selector or similar selectors that expect a checkbox inside the th in a posts row.

\n\n\n\n

This is also potentially going to impact extenders who target row actions or post titles with the expectation they are inside a td.

\n\n\n\n

Additionally, the CSS for collapsed table cells in the responsive view port has been updated to use flex layout.

\n\n\n\nWhat you may need to change\n\n\n\n

CSS and JS selectors targeting check columns should look for selectors targeting th.check-column or th input[type=\"checkbox\"].

\n\n\n\n

CSS and JS selectors targeting titles or row actions should look for selectors targeting td.title, td.column-title, td.page-title, td.column-primary, td .row-title, td .post-state, td .row-actions, or other similar selection patterns.

\n\n\n\n

Retaining both td and th selectors will support retaining compatibility with versions of WordPress prior to 7.1.

\n\n\n\nBefore and After\n\n\n\nCode Before Change\n\n\n\n<tr>\n <th scope=\"row\" class=\"check-column\">\n <input type=\"checkbox\" name=\"post[]\" value=\"123\">\n </th>\n <td class=\"title column-title column-primary page-title\">\n <a class=\"row-title\" href=\"...\">Hello world!</a>\n </td>\n <td class=\"author column-author\">admin</td>\n</tr>\n\n\n\n

The th is in the first column, followed by a td with the column title.

\n\n\n\nCode After Change\n\n\n\n<tr>\n <td class=\"check-column\">\n <input type=\"checkbox\" name=\"post[]\" value=\"123\">\n </td>\n <th scope=\"row\" class=\"title column-title column-primary page-title\" aria-label=\"Hello world!\">\n <a class=\"row-title\" href=\"...\">Hello world!</a>\n </th>\n <td class=\"author column-author\">admin</td>\n</tr>\n\n\n\n

The th is in the second column, with an aria-label containing the post title. The check-column is now a td.

\n\n\n\n

Reviewed by @wildworks.

\n

#7-1, #dev-notes, #dev-notes-7-1

", "id": 17027950, "pubDate": "Mon, 03 Aug 2026 15:27:57 GMT", "whenReceived": "Mon, 03 Aug 2026 15:55:24 GMT", "whenUpdated": "Mon, 03 Aug 2026 15:55:24 GMT", "likes": [], "metadata": { "wpPostId": 124832, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 03 Aug 2026 13:58:57 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69251", "title": "Hi! I’m a long-time WordPress…", "link": "https://make.wordpress.org/polyglots/2026/08/03/hi-im-a-long-time-wordpress/", "description": "

Hi! I’m a long-time WordPress developer and I’m fluent in Persian (fa_IR), Wolof (wol), and Picard / Ch’ti (pcd). I’d love to contribute by improving translations and helping make WordPress more accessible for speakers of these languages. I’m looking forward to collaborating with the Polyglots team .

\n\n #fa_IR \n\n\n

#editor-requests

", "id": 17025148, "pubDate": "Mon, 03 Aug 2026 13:29:22 GMT", "whenReceived": "Mon, 03 Aug 2026 13:58:57 GMT", "whenUpdated": "Mon, 03 Aug 2026 13:58:57 GMT", "likes": [], "metadata": { "wpPostId": 69251, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69249", "title": "PTE Request for ORECTIC SEO CHECK", "link": "https://make.wordpress.org/polyglots/2026/08/03/pte-request-for-orectic-seo-check/", "description": "

Hello Polyglots! I am the plugin author for ORECTIC SEO CHECK ( https://wordpress.org/plugins/orectic-seo-check/ ). Please add me as translation editor for my plugin in the following locale:

\n\n #ja – @masakazuimai\n\n\n

I am a native Japanese speaker and have already prepared the full Japanese translation for both the plugin strings and the readme. Thank you!

\n

#editor-requests

", "id": 17025149, "pubDate": "Mon, 03 Aug 2026 13:29:10 GMT", "whenReceived": "Mon, 03 Aug 2026 13:58:57 GMT", "whenUpdated": "Mon, 03 Aug 2026 13:58:57 GMT", "likes": [], "metadata": { "wpPostId": 69249, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69245", "title": "PTE Request for Verifactu para WooCommerce – Finseed", "link": "https://make.wordpress.org/polyglots/2026/08/03/pte-request-for-verifactu-para-woocommerce-finseed/", "description": "

Hi Polyglots,

\n

I’m the plugin author of Verifactu para WooCommerce – Finseed:

\n\nhttps://wordpress.org/plugins/finseed-facturas-verifactu/\n\n\n

I’ve prepared and submitted a full Spanish translation of the plugin’s stable readme (117 strings) as suggestions, and would like to be able to review and approve future translation updates myself instead of adding to the es_ES team’s queue every release.

\n

My WordPress.org username: finseed

\n\n #es_ES – @finseed\n\n\n

If you have any questions, just comment here. Thank you!

\n

#editor-requests

", "id": 17025150, "pubDate": "Mon, 03 Aug 2026 13:28:58 GMT", "whenReceived": "Mon, 03 Aug 2026 13:58:57 GMT", "whenUpdated": "Mon, 03 Aug 2026 13:58:57 GMT", "likes": [], "metadata": { "wpPostId": 69245, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69242", "title": "Translation review request: Prevent Browser Caching, 10 locales", "link": "https://make.wordpress.org/polyglots/2026/08/03/translation-review-request-prevent-browser-caching-10-locales/", "description": "

Hi Polyglots,

\n

I’m the author of Prevent Browser Caching:

\n\nhttps://wordpress.org/plugins/prevent-browser-caching/\n\n\n

I’ve prepared translations of the plugin’s UI (86 strings) and current readme (95 strings) and submitted them as suggestions for the locales below. Each queue has 181 strings waiting in Stable + Stable Readme. I’m not a speaker of these languages, so I’d be grateful if the teams could review the suggestions and approve them if they’re correct and worth having.

\n\nProject: https://translate.wordpress.org/projects/wp-plugins/prevent-browser-caching/\n\nMy WordPress.org username: kostyatereshchuk\n\n\n\n #ja\n\n #de_DE\n\n #fr_FR\n\n #pt_BR\n\n #it_IT\n\n #pl_PL\n\n #tr_TR\n\n #vi\n\n #id_ID\n\n #pt_PT\n\n\n

Thank you for your time!

\n

#editor-requests

", "id": 17025151, "pubDate": "Mon, 03 Aug 2026 12:31:01 GMT", "whenReceived": "Mon, 03 Aug 2026 13:58:57 GMT", "whenUpdated": "Mon, 03 Aug 2026 13:58:57 GMT", "likes": [], "metadata": { "wpPostId": 69242, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/training/feed/", "whenReceived": "Mon, 03 Aug 2026 12:58:44 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/training/feed/", "guid": "https://make.wordpress.org/training/?p=177211", "title": "Meeting agenda for August 4th, 2026", "link": "https://make.wordpress.org/training/2026/08/03/meeting-agenda-for-august-4th-2026/", "description": "

This week’s meeting will be held on Tuesday, August 4th, 2026, at 07:00 UTC. The meeting will be held on Slack, in the #training channel. Anyone is welcome to contribute to the meeting by commenting in Slack threads during the meeting and throughout the following days. Meeting notes will be published by the following Tuesday to incorporate these asynchronous conversations as well.

\n\n\n\n

This week’s meeting will be hosted by @sumitsingh.

\n\n\n\n1. Intro/Welcome\n\n\n\n

Welcome to all the new teammates who joined the Training Team this week!

\n\n\n\n2. News\n\n\n\n\nMeeting Note Takers\n\nAug 4th – @mohkatz\n\n\n\nAug 11th – @andrewssanya\n\n\n\nAug 18th – @sibokul\n\n\n\nAug 25th – @makanikaran\n\n\n\n\n\nLooking for feedback\n\nWe are also planning an Office Hours session for August 22, 2026:\n\nTopic: Note-taking and publication workflow: Who does what, and how? More details are available here: https://github.com/WordPress/Learn/issues/3570\n\n\n\nWe have also reviewed several GitHub issues related to Office Hours. You can view all open Office Hours tickets and share your suggestions here: https://github.com/WordPress/Learn/issues?q=state%3Aopen%20label%3A%22Office%20Hours%22 \n\n\n\n\n\nWe have discussed starting a regular GitHub triage meeting, but this has not yet been confirmed.\n\nProposed schedule: Triage Squad GitHub triage – biweekly on Thursdays at 07:00 UTC.\n\n\n\nPlease let us know if you would be interested in joining this Slack meeting if we decide to move forward with it.\n\n\n\nhttps://github.com/WordPress/Learn/issues/3535. Big thank you to everyone who has shared feedback so far!\n\n\n\nWe’re actively updating the Training Team handbooks, and there’s still time to contribute. If you have any suggestions, improvements, or ideas, please share them – we’d greatly appreciate your input: https://github.com/WordPress/Learn/issues/3447\n\n\n\n\n\n\n\nLooking for volunteers\n\nWe need your help in finding all the content that could be updated and consolidated. We would love to have two groups of volunteers – one that will go through all the handbook content, and one that will check the courses. Please state your interest, and we will help you organize and start working on these important issues.\n\n\n\nAlso, we started working on creating thumbnails for all lessons that need them. You’re very welcome to join us and contribute to this important and creative project. Here’s the issue with details on how to work on the remaining thumbnails:
https://github.com/WordPress/Learn/issues/3428\n\n\n\nWe currently have around 555 open issues, and I think it would be more effective to divide them into smaller categories and work through them one by one.\n\nWe can start with a simple label that is suitable for everyone to review. My suggestion is:\n\nGoing through issues one by one\n\n\n\nIdentifying outdated or irrelevant issues\n\n\n\nSuggesting fixes or next steps\n\n\n\nAdding comments where needed (before closing or updating)\n\n\n\nWe labeled some of the issues as Good First Issues – if you want to start contributing, this is your starting point. Just go and find issues labeled as Good First Issue, particularly those that have Feedback in the issue title – help us verify them, and you will earn the Training Team Contributor badge in no time. Just follow this handbook article –https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues\n\n\n\n\n\nFor the upcoming sessions, I am proposing that we divide the open issues into smaller groups and work through one category at a time. This should make the process more organised and easier for everyone to participate in.\n\nWe could begin with: [Content] Needs Translation Reviewer – https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22 – Based on feedback from our last meeting, @rfluethi suggested starting with issues in the Bug category, as these are both the highest priority and likely the easiest to address. Please review the open tickets and share any feedback or suggestions you may have.\n\n\n\n\n\nHowever, I would appreciate your suggestions on which category would be the easiest and most useful for everyone to start with. Other available categories include:\n\nIssues without a label\n\n\n\nAwaiting Triage\n\n\n\n[Content] Feedback\n\n\n\n[Type] Bug\n\n\n\n\n\nPlease share which category you think we should review first. Once selected, we can divide the issues and work through them together, one by one.\n\n\n\nLet’s work together to clean up and keep the repository well-organized\n\n\n\n\n\n\n\nUpdates from last week’s Triage Squad session\n\nWe are planning to start, so if you would be interested, then comment or join the #Training team channel on WordPress Slack\n\n\n\n\n\nOther announcements and news\n\nTraining Team Monthly update for August is published – Training Team Update – August 2nd, 2026\n\n\n\nOn 28 August, the Learn WordPress DACH team will launch its first German-language course cohort, “Starten mit WordPress.” A huge thank you to everyone who signed up and to our cohort facilitators for helping bring this initiative to life. DACH team is looking forward to seven weeks of learning WordPress together through weekly live sessions and engaging asynchronous activities in between.\n\n\n\nWe successfully hosted our Office Hours session on 26 July 2026 and have published a recap post: https://make.wordpress.org/training/2026/07/30/office-hours-meeting-recap-26th-july-2026/. Thank you so much for the draft post, @rfluethi.\n\n\n\nThe Learn WordPress website is now 100% translated into Marathi! You can explore the Marathi version here: https://learn.wordpress.org/?locale=mr. A big thank you to @makarand  & everyone who contributed to reaching this milestone.\n\n\n\nJoin WordCamp US 2026 Contributor Day – https://us.wordcamp.org/2026/join-wordcamp-us-2026-contributor-day/\n\n\n\nPitching WordCamp US to Your Boss – https://us.wordcamp.org/2026/pitching-wordcamp-us-to-your-boss/\n\n\n\nHow to Bring Your Community to Make WordPress Slack?
https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/\n\n\n\n\n\n\n2. Come and Contribute\n\n\n\n\nContent ready for review\n\nSee Guidelines for reviewing content when reviewing content.\n\nWe have 9 issues ready for review\n\n\n\n\n\n\n\nFeedback awaiting validation\n\nSee Validating and Applying Content Feedback for step-by-step guidance on validating feedback.\n\nWe have 47 issues that require validation\n\n\n\n\n\n\n\nTopics awaiting vetting\n\nSee Vetting Topic Ideas for step-by-step guidance on vetting topic ideas.\n\nWe have 2 issues that require vetting\n\n\n\n\n\n\n\nValidated feedback awaiting fix\n\nContributors, see Validating and Applying Content Feedback for step-by-step guidance on applying feedback that has been validated.\n\nWe have 25 issues awaiting a fix\n\n\n\n\n\n\n\n\n3. Contribution Acknowledgement\n\n\n\n\nBadges awarded:\n\nNo badges awarded this week\n\n\n\n\n\n\n4. Project updates\n\n\n\n\nBuilding on the momentum of our last learning cohort (Block Theme Development Course cohort), we are excited to launch our next cohort focused on Plugin Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem.\n\n\n\nAlso, we are excited to launch our next cohort focused on Plugin Development next month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem.\n\n\n\n\n5. Upcoming Online Workshops\n\n\n\n\nWordCamp US 2026 Contributor Day Online, Sunday, August 16 – https://www.meetup.com/learn-wordpress-online-workshops/events/315907994\n\n\n\n\n6. Contributor Updates\n\n\n\n\nWhat have you been working on, and how has it been going?\n\n\n\nAnything you’ve accomplished since the last meeting?\n\n\n\nDo you have any blockers?\n\n\n\nCan other contributors or Training Team members help you in some way?\n\n\n\n\n7. Open Discussions\n\n\n\n

If you have topics you’d like discussed in the meeting, please leave them as a comment on this post.

\n\n\n\n\n\n\n\n

You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, then come walk through our onboarding program to get to know the team and how we work. And if you have questions, feel free to reach out in the #training Slack channel at any time.

", "id": 17023890, "pubDate": "Mon, 03 Aug 2026 11:59:28 GMT", "whenReceived": "Mon, 03 Aug 2026 12:58:44 GMT", "whenUpdated": "Mon, 03 Aug 2026 12:58:44 GMT", "likes": [], "metadata": { "wpPostId": 177211, "wpSiteId": 46403572 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/docs/feed/", "whenReceived": "Mon, 03 Aug 2026 10:42:47 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/docs/feed/", "guid": "https://make.wordpress.org/docs/2026/08/03/xpost-documentation-team-update-august-3-2026/", "title": "X-post: Documentation Team Update – August 3, 2026", "link": "https://make.wordpress.org/docs/2026/08/03/xpost-documentation-team-update-august-3-2026/", "description": "

X-comment from +make.wordpress.org/updates: Comment on Documentation Team Update – August 3, 2026

", "id": 17020963, "pubDate": "Mon, 03 Aug 2026 09:55:23 GMT", "whenReceived": "Mon, 03 Aug 2026 10:42:47 GMT", "whenUpdated": "Mon, 03 Aug 2026 10:42:47 GMT", "likes": [], "metadata": { "wpPostId": 118736, "wpSiteId": 31760022 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 03 Aug 2026 10:36:46 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69230", "title": "Hello Polyglots! I am the…", "link": "https://make.wordpress.org/polyglots/2026/08/03/hello-polyglots-i-am-the-643/", "description": "

Hello Polyglots! I am the plugin author for Sawir Referral. We have a contributor who translated the plugin into Persian and I’d like them to be added as PTE:

\n\nhttps://wordpress.org/plugins/sawir-referral/\n\n\n\n #fa_IR @duvenhage\n\n\n

They also submitted the current fa_IR translations now in “waiting” status — please review those as well.

\n

Thank you!

", "id": 17020851, "pubDate": "Mon, 03 Aug 2026 09:24:08 GMT", "whenReceived": "Mon, 03 Aug 2026 10:36:46 GMT", "whenUpdated": "Mon, 03 Aug 2026 10:36:46 GMT", "likes": [], "metadata": { "wpPostId": 69230, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed/", "whenReceived": "Mon, 03 Aug 2026 06:53:36 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed/", "guid": "https://make.wordpress.org/core/?p=124614", "title": "Iframed Editor Changes in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/08/03/iframed-editor-changes-in-wordpress-7-1/", "description": "OverviewCurrent SituationWhat's changing in WordPress 7.1What should block developers do?\n\n\n

Previous posts on this topic:

\n\n\n\n\nIframed Editor Changes in WordPress 7.0 (February 2026)\n\n\n\nPreparing the Post Editor for Full iframe Integration (November 2025)\n\n\n\nBlocks in an iframed (template) editor (June 2021)\n\n\n\n\nOverview\n\n\n\n

For several releases, WordPress has been moving its editors into an iframe, starting with the template editor back in 5.8. In WordPress 7.1, the post editor takes the final step: it is now always iframed.

\n\n\n\n

If you want the full reasoning behind the move, see Benefits of the iframe editor.

\n\n\n\nCurrent Situation\n\n\n\n

Every editor except the post editor — the site editor, the template editor, and all block template, and device previews — has been iframed unconditionally for some time. The post editor was the exception, and until now, whether it was iframed depended on the environment: whether the Gutenberg plugin was active and the blocks in use.

\n\n\n\n\nIn WordPress 7.0, the decision was based on the block API versions of the blocks actually inserted in the post. If every inserted block was API version 3 or higher, the post editor was iframed; if any lower-version block was present, the iframe was dropped to preserve compatibility.\n\n\n\nThe Gutenberg plugin has been ahead of core here: since Gutenberg 22.6, when the plugin is active the post editor is forced to be iframed regardless of the theme type or the block API versions in use, so that compatibility issues surface early and can be reported before the change reaches core.\n\n\n\n\n

This conditional behavior kept older blocks working, but it also meant the post editor could switch between iframed and non-iframed modes depending on a post’s content.

\n\n\n\nWhat’s changing in WordPress 7.1\n\n\n\n

Starting in WordPress 7.1, the post editor is always iframed, regardless of the theme type, the block API versions of the registered blocks, or the block API versions of the blocks in the content.

\n\n\n\n

Starting in WordPress 7.1, the post editor is always iframed, regardless of the theme type, the block API versions of the registered blocks, or the block API versions of the blocks in the content. The site editor, template editor, and device previews have been iframed for a long time, so much of this ground is already well tested. Even so, please test that your custom blocks — and any plugins that extend blocks — work correctly in the fully iframed post editor. See WordPress/gutenberg#74042 for more details.

\n\n\n\n

The site editor, template editor, and device previews have been iframed for a long time, so much of this ground is already well tested. Even so, please test that your custom blocks — and any plugins that extend blocks — work correctly in the fully iframed post editor.

\n\n\n\n

See WordPress/gutenberg#74042 for more details.

\n\n\n\nWhat should block developers do?\n\n\n\n

Most blocks already work in the iframed editor without any changes. The issues that do come up almost always trace back to the same root cause: the iframe has its own document and window, separate from the admin page where editor scripts run. Code that reaches for the global document or window to touch the editor canvas will be looking at the wrong document.

\n\n\n\n

The usual fixes are:

\n\n\n\n\nGet the canvas document from an element inside it, via ownerDocument and its defaultView, rather than the global document/window.\n\n\n\nUse useRefEffect to attach and clean up event listeners on canvas elements.\n\n\n\n\n

For the full list of things to watch for and how to resolve them, see Technical considerations for the iframe editor.

\n\n\n\n

Props to @tyxla for review.

\n

#7-1, #dev-notes, #dev-notes-7-1

", "id": 17018218, "pubDate": "Mon, 03 Aug 2026 05:55:01 GMT", "whenReceived": "Mon, 03 Aug 2026 06:53:36 GMT", "whenUpdated": "Wed, 05 Aug 2026 16:14:15 GMT", "likes": [], "metadata": { "wpPostId": 124614, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Sun, 02 Aug 2026 20:13:20 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69216", "title": "PTE Request for NitroSearch for WooCommerce", "link": "https://make.wordpress.org/polyglots/2026/08/02/pte-request-for-nitrosearch-for-woocommerce/", "description": "

I am the plugin author. We have professionally reviewed translations ready to import and I’d like to request PTE status for this plugin for the following locales:

\n

Plugin link: https://wordpress.org/plugins/nitrosearch-for-woocommerce/

\n\n #es_ES \n\n #fr_FR \n\n\n

— de_DE

\n\n #it_IT \n\n\n

— nl_NL
\n— pl_PL

\n\n #pt_PT \n\n #pt_BR\n\n\n

Thank you!

\n

#editor-requests

", "id": 17012018, "pubDate": "Sun, 02 Aug 2026 20:03:14 GMT", "whenReceived": "Sun, 02 Aug 2026 20:13:20 GMT", "whenUpdated": "Mon, 03 Aug 2026 10:36:46 GMT", "likes": [], "metadata": { "wpPostId": 69216, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69212", "title": "PTE Request for Scanoria Accessibility Audit", "link": "https://make.wordpress.org/polyglots/2026/08/02/pte-request-for-scanoria-accessibility-audit/", "description": "

I am the plugin author for Scanoria Accessibility Audit. I have submitted the Japanese translation for the Stable Readme project.

\n

Please review the waiting strings and add the following WordPress.org user as Project Translation Editor (PTE) for Japanese:

\n\nhttps://wordpress.org/plugins/scanoria-accessibility-audit/\n\n\n\n #ja – @salaoo36\n\n\n

The Stable Readme project has 55 waiting strings with no warnings. The 39 UI strings of the Stable project are translated as well, and I will submit them as soon as GlotPress picks up the release I published today, which added them.

\n

Japanese is my native language and I have read the Japanese translation style guide. Every string was checked against it before submission, in particular rules 1-2 (half-width alphanumerics, symbols and question marks), 1-4 (a half-width space between half-width and full-width characters), 1-5 (half-width parentheses with surrounding spaces) and 1-9 (no space around half-width numerals).

\n

If you have any questions, just comment here. Thank you!

\n

#editor-requests

", "id": 17012019, "pubDate": "Sun, 02 Aug 2026 19:59:24 GMT", "whenReceived": "Sun, 02 Aug 2026 20:13:20 GMT", "whenUpdated": "Sun, 02 Aug 2026 20:13:20 GMT", "likes": [], "metadata": { "wpPostId": 69212, "wpSiteId": 31792945 }, "ctLikes": 0 } ] } ], "metadata": { "cachekey": "category:cagrimmett/make-wordpress", "feedUrlList": [ "https://developer.wordpress.org/news/feed/", "https://make.wordpress.org/accessibility/feed/", "https://make.wordpress.org/cli/feed/", "https://make.wordpress.org/community/feed/", "https://make.wordpress.org/core/feed", "https://make.wordpress.org/core/feed/", "https://make.wordpress.org/design/feed/", "https://make.wordpress.org/docs/feed/", "https://make.wordpress.org/hosting/feed/", "https://make.wordpress.org/marketing/feed/", "https://make.wordpress.org/meta/feed/", "https://make.wordpress.org/mobile/feed/", "https://make.wordpress.org/openverse/feed/", "https://make.wordpress.org/performance/feed/", "https://make.wordpress.org/photos/feed/", "https://make.wordpress.org/plugins/feed/", "https://make.wordpress.org/polyglots/feed/", "https://make.wordpress.org/support/feed/", "https://make.wordpress.org/sustainability/feed/", "https://make.wordpress.org/test/feed/", "https://make.wordpress.org/themes/feed/", "https://make.wordpress.org/tide/feed/", "https://make.wordpress.org/training/feed/", "https://make.wordpress.org/tv/feed/", "https://wordpress.org/news/podcast/feed/" ] } }