Hello Polyglots team,
\nI have submitted 150 translation suggestions for the Astra theme in Spanish (Costa Rica) and would appreciate editorial review. The suggestions are currently waiting in es_CR.
\nI reviewed the final set against the es_CR glossary, used the locale’s formal “usted” voice, preserved placeholders and HTML, and skipped ambiguous strings. This contribution is part of my WordPress Credits project, and I intentionally went beyond the 100-string course minimum to provide a stronger contribution and a practical review buffer.
\nProject: https://translate.wordpress.org/projects/wp-themes/astra/es-cr/default/
\nMy waiting suggestions: https://translate.wordpress.org/projects/wp-themes/astra/es-cr/default/?filters%5Bterm_scope%5D=scope_any&filters%5Bstatus%5D=waiting&filters%5Buser_login%5D=sergiocam1219&sort%5Bby%5D=translation_date_added&sort%5Bhow%5D=desc
\nThank you very much for your time and support!
\n\n #es_CR \n\n\n#editor-requests
", "id": 16883818, "pubDate": "Tue, 28 Jul 2026 06:11:01 GMT", "whenReceived": "Tue, 28 Jul 2026 06:13:22 GMT", "whenUpdated": "Tue, 28 Jul 2026 06:13:22 GMT", "likes": [], "metadata": { "wpPostId": 69002, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68998", "title": "PTE Request for Webcraft Forms", "link": "https://make.wordpress.org/polyglots/2026/07/28/pte-request-for-webcraft-forms/", "description": "I am the plugin author for Webcraft Forms. I have added the complete German translation for my plugin and would like to be able to review and approve it as PTE.
\nPlease add my WordPress.org user @kleinsascha as translation editor for the locale below:
\n\nhttps://wordpress.org/plugins/webcraft-forms/\n\n\n\n #de_DE – @kleinsascha\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16883819, "pubDate": "Tue, 28 Jul 2026 06:10:52 GMT", "whenReceived": "Tue, 28 Jul 2026 06:13:22 GMT", "whenUpdated": "Tue, 28 Jul 2026 06:13:22 GMT", "likes": [], "metadata": { "wpPostId": 68998, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68996", "title": "PTE Request for Ric Ultimate Cookie Consent", "link": "https://make.wordpress.org/polyglots/2026/07/28/pte-request-for-ric-ultimate-cookie-consent/", "description": "I would like to request Plugin Translation Editor (PTE) access for my plugin in the Bengali (bn_BD) locale.
\nPlugin: Ric Ultimate Cookie Consent
\nPlugin URL: https://wordpress.org/plugins/ric-ultimate-cookie-consent
I am the plugin author and would like to help maintain and approve Bengali translations for this plugin.
\nThank you for your time and support!
\n#editor-requests
", "id": 16883820, "pubDate": "Tue, 28 Jul 2026 06:10:44 GMT", "whenReceived": "Tue, 28 Jul 2026 06:13:22 GMT", "whenUpdated": "Tue, 28 Jul 2026 06:13:22 GMT", "likes": [], "metadata": { "wpPostId": 68996, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68994", "title": "Hey there, I am the…", "link": "https://make.wordpress.org/polyglots/2026/07/28/hey-there-i-am-the/", "description": "Hey there, I am the plugin author for “Digital Leap User Profile UX” and would like to review and approve German translations for it.
\n\nhttps://wordpress.org/plugins/digital-leap-user-profile-ux/\n\n\n\n #de_DE – @digitalleapgmbh\n\n\n#editor-requests
", "id": 16883821, "pubDate": "Tue, 28 Jul 2026 06:10:37 GMT", "whenReceived": "Tue, 28 Jul 2026 06:13:22 GMT", "whenUpdated": "Tue, 28 Jul 2026 06:13:22 GMT", "likes": [], "metadata": { "wpPostId": 68994, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/themes/feed/", "whenReceived": "Tue, 28 Jul 2026 03:28:12 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/themes/feed/", "guid": "https://make.wordpress.org/themes/?p=25118", "title": "Themes Team Meeting Agendas for July 28, 2026", "link": "https://make.wordpress.org/themes/2026/07/28/themes-team-meeting-agendas-for-july-28-2026/", "description": "The Themes Team holds meetings on the second and fourth Tuesdays of every month. As the second Tuesday meeting this month was cancelled, this will be the first meeting of the month and will take place on 28 July.
\n\n\n\nMeeting Details:
\n\n\n\n\nDate and Time: Tuesday, July 28 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\nAlongside 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\nWe 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\nI am looking forward to seeing you at the meeting!
\n#agenda, #themes-team
", "id": 16881978, "pubDate": "Tue, 28 Jul 2026 03:19:27 GMT", "whenReceived": "Tue, 28 Jul 2026 03:28:12 GMT", "whenUpdated": "Tue, 28 Jul 2026 03:28:12 GMT", "likes": [], "metadata": { "wpPostId": 25118, "wpSiteId": 31759950 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 28 Jul 2026 02:52:53 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69004", "title": "#editor-request Hi Polyglots team, I’m…", "link": "https://make.wordpress.org/polyglots/2026/07/28/editor-request-hi-polyglots-team-im/", "description": "Hi Polyglots team,
\nI’m the author of the plugin Grip Chatbot. I’ve submitted Japanese (ja) translations for it and would like to request PTE access so I can review and approve translations for this plugin.
\nPlugin: Grip Chatbot https://wordpress.org/plugins/grip-chatbot/
\nTranslation project: https://translate.wordpress.org/projects/wp-plugins/grip-chatbot/
\nI’ve imported translations for both the code (Stable & Development) and the readme (Stable & Development Readme).
\nPlease grant PTE for Japanese (ja) to:
\n\n #ja @gripspace \n\n\nThank you very much!
\n#editor-requests
", "id": 16881672, "pubDate": "Tue, 28 Jul 2026 02:02:58 GMT", "whenReceived": "Tue, 28 Jul 2026 02:52:53 GMT", "whenUpdated": "Tue, 28 Jul 2026 06:13:22 GMT", "likes": [], "metadata": { "wpPostId": 69004, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Tue, 28 Jul 2026 02:35:18 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124970", "title": "Dev Chat Agenda – July 28, 2026", "link": "https://make.wordpress.org/core/2026/07/28/dev-chat-agenda-july-28-2026/", "description": "The next WordPress Developers Chat will take place on Tuesday, July 28, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.
\n\n\n\nThe live meeting will focus on the discussion for upcoming releases, and have an open floor section.
\n\n\n\nThe 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\nNote: 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 3 was released on July 22nd\n\n\n\n7.1 Beta 4 is scheduled for release on Wednesday, July 29, at 15:00 UTC in core\n\n\n\nNew 7.1 Dev Notes:\n\nClient-Side Media Processing\n\n\n\nText shadow support in global styles\n\n\n\nMedia library infinite scroll enabled by default\n\n\n\nEditable blocks inside Custom HTML block\n\n\n\nEditor Components updates\n\n\n\nRegistering and rendering SVG icons\n\n\n\nMin width block support\n\n\n\nBackground gradient block support\n\n\n\n\n\n\nGeneral\n\n\n\n\nReact 19 punted, to be experimental in Gutenberg\n\n\n\nWhat’s new in Gutenberg 23.6\n\n\n\nWordPress 7.0 release retrospective is still open to responses (despite being past the stated deadline)\n\n\n\n\n\nDiscussions \n\n\n\nThe 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\nDevs: There are tickets still open for the 7.1 milestone. Most will be punted if not merged by the RC1 release next week.\n\n\n\nIssue #80491, raised in this comment\n\n\n\n\n\n\nOpen floor \n\n\n\nAny 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.
#7-1, #agenda, #core, #dev-chat
", "id": 16881383, "pubDate": "Tue, 28 Jul 2026 01:41:45 GMT", "whenReceived": "Tue, 28 Jul 2026 02:35:18 GMT", "whenUpdated": "Tue, 28 Jul 2026 02:35:18 GMT", "likes": [], "metadata": { "wpPostId": 124970, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 28 Jul 2026 01:12:27 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=69000", "title": "Translation Review Request – es_CR…", "link": "https://make.wordpress.org/polyglots/2026/07/28/translation-review-request-es_cr/", "description": "Translation Review Request – es_CR (WP Plugin: Rooster One)
\nHi! I’ve suggested translations for the WordPress plugin “Rooster One” (Stable sub-project) and would like to have them reviewed. I confirm that I’ve read the style guide and/or glossary for the es_CR locale.
\nProject: Rooster One — Stable (latest release)
\nURL: https://translate.wordpress.org/projects/wp-plugins/ai-eshop-optimizer/stable/es-cr/default/
I’ve suggested 300 translations across the plugin’s stable release, covering social media integrations, customer segmentation, ratings, marketing, and merchandising features. I noticed there are currently no dedicated editors for this project — happy to have anyone from the es_CR team take a look.
\n\n #es_cr\n\n\n#editor-requests
", "id": 16880433, "pubDate": "Tue, 28 Jul 2026 00:04:06 GMT", "whenReceived": "Tue, 28 Jul 2026 01:12:27 GMT", "whenUpdated": "Tue, 28 Jul 2026 06:13:22 GMT", "likes": [], "metadata": { "wpPostId": 69000, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68987", "title": "Plugin: Business Cloud ERP Integration for WooCommerce", "link": "https://make.wordpress.org/polyglots/2026/07/27/plugin-business-cloud-erp-integration-for-woocommerce/", "description": "https://wordpress.org/plugins/business-cloud-erp-integration/\n\n\nRequesting Project Translation Editor rights as the plugin author.
\n\n #el – @businesscloudgr (@tobifjellner)\n\n\n#editor-requests
", "id": 16873099, "pubDate": "Mon, 27 Jul 2026 17:39:25 GMT", "whenReceived": "Mon, 27 Jul 2026 18:30:52 GMT", "whenUpdated": "Mon, 27 Jul 2026 18:30:52 GMT", "likes": [], "metadata": { "wpPostId": 68987, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/training/feed/", "whenReceived": "Mon, 27 Jul 2026 16:02:55 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/training/feed/", "guid": "https://make.wordpress.org/training/?p=175420", "title": "Meeting agenda for July 28th, 2026", "link": "https://make.wordpress.org/training/2026/07/27/meeting-agenda-for-july-28th-2026/", "description": "This week’s meeting will be held on Tuesday, July 28th, 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\nThis week’s meeting will be hosted by @sumitsingh.
\n\n\n\n1. Intro/Welcome\n\n\n\nWelcome 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\nJuly 28th – @pravin1996\n\n\n\nAug 4th – @mohkatz\n\n\n\nAug 11th – @andrewssanya\n\n\n\nAug 18th – @sibokul\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?\n\nMore details are available here: https://github.com/WordPress/Learn/issues/3570\n\n\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: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\nYou 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": 16869401, "pubDate": "Mon, 27 Jul 2026 14:43:05 GMT", "whenReceived": "Mon, 27 Jul 2026 16:02:55 GMT", "whenUpdated": "Mon, 27 Jul 2026 16:02:55 GMT", "likes": [], "metadata": { "wpPostId": 175420, "wpSiteId": 46403572 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 27 Jul 2026 13:29:54 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68967", "title": "PTE Request for Multiple Projects (Norwegian Nynorsk)", "link": "https://make.wordpress.org/polyglots/2026/07/27/pte-request-for-multiple-projects-norwegian-nynorsk/", "description": "Hi Polyglots team,
\nI would like to request Project Translation Editor (PTE) permissions for the following project.
\nProject:
\n\nhttps://wordpress.org/plugins/spectra-blocks/\n\nhttps://wordpress.org/themes/astra/\n\nhttps://wordpress.org/themes/spectra-one/\n\nhttps://wordpress.org/plugins/fluentform/\n\n\nLocale:
\n\n #nn_NO @dmsandal\n\n\nI actively use these plugins and themes in my professional work building WordPress websites and have been contributing to the Norwegian Nynorsk translations. I would like to help maintain and review translations for these projects on an ongoing basis.
\nI plan to continue contributing translations for Norwegian Nynorsk and help improve translation quality and consistency across the WordPress ecosystem.
\nThank you for your consideration.
\n#editor-requests
", "id": 16865892, "pubDate": "Mon, 27 Jul 2026 12:19:17 GMT", "whenReceived": "Mon, 27 Jul 2026 13:29:54 GMT", "whenUpdated": "Mon, 27 Jul 2026 13:29:54 GMT", "likes": [], "metadata": { "wpPostId": 68967, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68969", "title": "PTE Request for Shenasar", "link": "https://make.wordpress.org/polyglots/2026/07/27/pte-request-for-shenasar/", "description": "I am the plugin author for Shenasar. We have a number of great translation editors that we’d like to be able to approve translation for our plugin. Please add the following WordPress.org users as translation editors for their respective locales:
\n\nhttps://wordpress.org/plugins/shenasar\n\n\n\n #fa_IR – @shenasar\n\n\n#editor-requests
", "id": 16865893, "pubDate": "Mon, 27 Jul 2026 12:19:04 GMT", "whenReceived": "Mon, 27 Jul 2026 13:29:54 GMT", "whenUpdated": "Mon, 27 Jul 2026 13:29:54 GMT", "likes": [], "metadata": { "wpPostId": 68969, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68976", "title": "Hello! I am the plugin…", "link": "https://make.wordpress.org/polyglots/2026/07/27/hello-i-am-the-plugin-14/", "description": "Hello! I am the plugin author and I would like to request PTE for the Ukrainian locale for my newly approved plugin.
\nPlugin: CatCode Order Notifications with Telegram for WooCommerce
\nProject: https://translate.wordpress.org/projects/wp-plugins/catcode-order-notifications-with-telegram-for-woocommerce/
A complete Ukrainian translation (83 strings + readme) is already imported and waiting for approval. I am already a PTE for my other plugins in uk ( catcode-order-sync-with-keycrm-for-woocommerce, catcode-iban-smart-invoice ).
\nThank you!
\n#editor-requests
", "id": 16863749, "pubDate": "Mon, 27 Jul 2026 11:48:14 GMT", "whenReceived": "Mon, 27 Jul 2026 11:49:32 GMT", "whenUpdated": "Mon, 27 Jul 2026 13:29:54 GMT", "likes": [], "metadata": { "wpPostId": 68976, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68971", "title": "PTE Request for Rank+ – Website Accessibility", "link": "https://make.wordpress.org/polyglots/2026/07/27/pte-request-for-rank-website-accessibility-2/", "description": "I am the plugin author for Rank+ – Website Accessibility.
\n\nhttps://wordpress.org/plugins/website-accessibility-by-rankplus/\n\n\n\n #ar – @rankplus (@tobifjellner)\n\n\n— de_DE – @rankplus
\n\n #he_IL – @rankplus\n\n\n1. The basic translation is indeed AI-based to save time. I then had a friends who speaks German + Arabic as a native speaker go over the translation before I uploaded the plugin.
\n2. I am aware of the translation guidelines and everything that is required. We went through them together to ensure correctness. And I am aware that AI-based translations that have not been checked by humans are not allowed.
\n3. About Hebrew – I speak Hebrew myself so no problem about translating Hebrew text.
If you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16863750, "pubDate": "Mon, 27 Jul 2026 11:05:19 GMT", "whenReceived": "Mon, 27 Jul 2026 11:49:32 GMT", "whenUpdated": "Mon, 27 Jul 2026 13:29:54 GMT", "likes": [], "metadata": { "wpPostId": 68971, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68955", "title": "Hi, I’m the author of…", "link": "https://make.wordpress.org/polyglots/2026/07/27/hi-im-the-author-of-7/", "description": "Hi, I’m the author of the PostNotify plugin – https://wordpress.org/plugins/postnotify/ ).
\nI’ve submitted the Italian (it_IT) translation and I’d like to request PTE for it_IT so I can manage the translation of my own plugin. I’m a native Italian speaker. Thanks!
\n\n #it_IT \n\n\n#editor-requests
", "id": 16861896, "pubDate": "Mon, 27 Jul 2026 08:37:41 GMT", "whenReceived": "Mon, 27 Jul 2026 10:08:39 GMT", "whenUpdated": "Mon, 27 Jul 2026 10:08:39 GMT", "likes": [], "metadata": { "wpPostId": 68955, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68957", "title": "Project Translation Editor (PTE)", "link": "https://make.wordpress.org/polyglots/2026/07/27/project-translation-editor-pte/", "description": "Hello,
\nI am the developer of the Yesh Invoice – WooCommerce Payment Gateway plugin.
\nI have submitted Hebrew translations, but they have been waiting for approval for over two weeks.
\nCould a Hebrew Translation Editor please review them?
\nIf possible, I would also like to request Project Translation Editor (PTE) permissions for this plugin so I can maintain the translations in the future.
\nPlugin: https://wordpress.org/plugins/yesh-invoice-payment-gateway/
\nThank you!
\n\n #he_IL \n\n\n#editor-requests
", "id": 16859849, "pubDate": "Mon, 27 Jul 2026 07:01:28 GMT", "whenReceived": "Mon, 27 Jul 2026 07:08:35 GMT", "whenUpdated": "Mon, 27 Jul 2026 10:08:39 GMT", "likes": [], "metadata": { "wpPostId": 68957, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68939", "title": "Translation Review Request – es_CR (20 WP Themes)", "link": "https://make.wordpress.org/polyglots/2026/07/27/translation-review-request-es_cr-20-wp-themes/", "description": "Hi! I’ve suggested translations for the following 20 WordPress themes and would like to have them reviewed. I confirm that I’ve read the style guide and/or glossary for the es_CR locale.
\nBeauty Parlour TWP: https://translate.wordpress.org/projects/wp-themes/beauty-parlour-twp/es-cr/default/
\nAgency TWP: https://translate.wordpress.org/projects/wp-themes/agency-twp/es-cr/default/
\nAutomobile Company: https://translate.wordpress.org/projects/wp-themes/automobile-company/es-cr/default/
\nAutomobile TWP: https://translate.wordpress.org/projects/wp-themes/automobile-twp/es-cr/default/
\nBlogger Lite: https://translate.wordpress.org/projects/wp-themes/blogger-lite/es-cr/default/
\nBusiness Blue: https://translate.wordpress.org/projects/wp-themes/business-blue/es-cr/default/
\nBusiness Company TWP: https://translate.wordpress.org/projects/wp-themes/business-company-twp/es-cr/default/
\nBusiness Green: https://translate.wordpress.org/projects/wp-themes/business-green/es-cr/default/
\nCleaning TWP: https://translate.wordpress.org/projects/wp-themes/cleaning-twp/es-cr/default/
\nConstruction TWP: https://translate.wordpress.org/projects/wp-themes/construction-twp/es-cr/default/
\nEducation TWP: https://translate.wordpress.org/projects/wp-themes/education-twp/es-cr/default/
\nEvent TWP: https://translate.wordpress.org/projects/wp-themes/event-twp/es-cr/default/
\nExperon Biz: https://translate.wordpress.org/projects/wp-themes/experon-biz/es-cr/default/
\nExperon Boxed: https://translate.wordpress.org/projects/wp-themes/experon-boxed/es-cr/default/
\nExperon Dark: https://translate.wordpress.org/projects/wp-themes/experon-edark/es-cr/default/
\nExperon eBlog: https://translate.wordpress.org/projects/wp-themes/experon-eblog/es-cr/default/
\nExperon eDark: https://translate.wordpress.org/projects/wp-themes/experon-edark/es-cr/default/
\nExperon eGrid: https://translate.wordpress.org/projects/wp-themes/experon-egrid/es-cr/default/
\nExperon eMagazine: https://translate.wordpress.org/projects/wp-themes/experon-emagazine/es-cr/default/
\nExperon Grid: https://translate.wordpress.org/projects/wp-themes/experon-grid/es-cr/default/
#editor-requests
", "id": 16858821, "pubDate": "Mon, 27 Jul 2026 04:55:15 GMT", "whenReceived": "Mon, 27 Jul 2026 05:28:11 GMT", "whenUpdated": "Mon, 27 Jul 2026 05:28:11 GMT", "likes": [], "metadata": { "wpPostId": 68939, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68935", "title": "Hello Polyglots, I am the…", "link": "https://make.wordpress.org/polyglots/2026/07/27/hello-polyglots-i-am-the-642/", "description": "Hello Polyglots,
\nI am the author of the RuCookie plugin. I have imported the Russian translations for the Stable Readme, and all 67 translations are currently waiting for review.
\nI would like to have these translations reviewed and approved. I would also like to become a Project Translation Editor (PTE) for the Russian translation of RuCookie so I can maintain and approve future translations.
\nPlugin: https://wordpress.org/plugins/rucookie/
\nTranslation project: https://translate.wordpress.org/projects/wp-plugins/rucookie/
\n\n #ru_RU @itobereg (@tobifjellner)\n\n\nI confirm that I am a native Russian speaker and can verify the quality of the translations.
\nThank you!
\n#editor-requests
", "id": 16858822, "pubDate": "Mon, 27 Jul 2026 04:54:22 GMT", "whenReceived": "Mon, 27 Jul 2026 05:28:11 GMT", "whenUpdated": "Mon, 27 Jul 2026 18:30:52 GMT", "likes": [], "metadata": { "wpPostId": 68935, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68941", "title": "Agenda: Weekly Polyglots Chat – July 29, 2026 (7:00 UTC)", "link": "https://make.wordpress.org/polyglots/2026/07/27/agenda-weekly-polyglots-chat-2/", "description": "This meeting will be held by text chat at Wednesday, July 29, 2026 at 07:00 AM UTC in the #polyglots channel in the Making WordPress Slack.
\n\n\n\n\nWelcome\n\n\n\nWeekly Locale Stats\n\n\n\nRelease: WordPress 7.1 progress\n\nBeta 3 is available\n\n\n\nWordPress 7.1 Release Party ScheduleIf 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.
#meeting-agenda, #polyglots-meeting, #weekly-meetings
", "id": 16858823, "pubDate": "Mon, 27 Jul 2026 04:51:14 GMT", "whenReceived": "Mon, 27 Jul 2026 05:28:11 GMT", "whenUpdated": "Mon, 27 Jul 2026 05:28:11 GMT", "likes": [], "metadata": { "wpPostId": 68941, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68927", "title": "PTE Request for Reinvent WP Text to Speech", "link": "https://make.wordpress.org/polyglots/2026/07/26/pte-request-for-reinvent-wp-text-to-speech/", "description": "Hello Polyglots team,
\nI am the plugin author for Reinvent WP Text to Speech:
\n\nhttps://wordpress.org/plugins/natural-text-to-speech/\n\n\nI have submitted 240 Stable Readme translations for each of the following locales. All were AI-assisted and require review by fluent human contributors.
\nIndonesian: Please review the waiting translations. If they meet the locale’s quality standards, please add @reinventwp as a Project Translation Editor so future Indonesian translations can be maintained:
\n\n #id_ID – @reinventwp\n\n\nRequesting review, but not PTE role, for the following locales:
\n#de_DE #da_DK #it_IT #fr_FR #es_ES #pt_BR #ja #nl_NL #pl_PL
Thank you!
\n#editor-requests
", "id": 16853347, "pubDate": "Sun, 26 Jul 2026 17:58:29 GMT", "whenReceived": "Sun, 26 Jul 2026 19:25:52 GMT", "whenUpdated": "Sun, 26 Jul 2026 19:25:52 GMT", "likes": [], "metadata": { "wpPostId": 68927, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68932", "title": "PTE Request for Codela Commerce Toolkit", "link": "https://make.wordpress.org/polyglots/2026/07/26/pte-request-for-codela-commerce-toolkit/", "description": "I am the plugin author and Turkish translation contributor for Codela Commerce Toolkit:
\n\nhttps://wordpress.org/plugins/codela-commerce-toolkit/\n\nhttps://translate.wordpress.org/projects/wp-plugins/codela-commerce-toolkit/\n\n\nI have submitted Turkish translations and would like to review and maintain them according to the Turkish glossary and style guide.
\nPlease add me as a Project Translation Editor for this project:
\n\n #tr_TR – @codela\n\n\nIf you have any questions or corrections, I will be happy to address them.
\nThank you!
\n#editor-requests
", "id": 16853348, "pubDate": "Sun, 26 Jul 2026 17:51:14 GMT", "whenReceived": "Sun, 26 Jul 2026 19:25:52 GMT", "whenUpdated": "Sun, 26 Jul 2026 19:25:52 GMT", "likes": [], "metadata": { "wpPostId": 68932, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Sun, 26 Jul 2026 13:16:47 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124676", "title": "New Block Support in WordPress 7.1: Background Gradient (background.gradient)", "link": "https://make.wordpress.org/core/2026/07/26/new-block-support-in-wordpress-7-1-background-gradient-background-gradient/", "description": "WordPress 7.1 introduces a new background.gradient block support. It gives blocks a gradient control in the Background panel of the block inspector. Unlike the existing gradient support, it can be combined with a background image so the two render together.
\n\n\n\nGitHub issue: #32787 | PR: #75859
\n\n\n\nBackground\n\n\n\nUntil now, the only way to apply a gradient to a block was through the Color panel’s color.gradient support. That value is stored at style.color.gradient and rendered as a background CSS shorthand.
\n\n\n\nThe background shorthand resets every background property, including background-image. This meant a gradient set through color.gradient would conflict with, and override, any background image on the same block. A block could show a gradient or an image, but not both.
\n\n\n\nWhat changed\n\n\n\nA new background.gradient block support is registered. It stores its value at style.background.gradient, separate from the existing style.color.gradient.
\n\n\n\nThe key difference is that the new support renders through the background-image longhand property instead of the background shorthand. Because it avoids the shorthand, it no longer resets the other background properties. The style engine can then output the gradient and any background image as comma-separated values in a single background-image declaration:
\n\n\n\nbackground-image: linear-gradient( 135deg, #000 0%, #fff 100% ), url( 'https://example.com/image.jpg' );\n\n\n\nThe gradient is layered over the image, and both render together.
\n\n\n\nKey behavior:
\n\n\n\n\nThe control appears in the Background panel, next to the existing background image control.\n\n\n\nWhen background.gradient is enabled for a block, the gradient tab in the Color panel is suppressed to avoid duplicate controls.\n\n\n\nGradient preset slugs resolve to CSS custom properties, for example var( --wp--preset--gradient--vivid-cyan-blue ).\n\n\n\nWhen only a gradient is set (no image), it renders on its own as the background-image value.\n\n\n\n\nHow to opt in\n\n\n\nAdd gradient under the background support in 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\nIn WordPress 7.1, the Group, Accordion, Pullquote, Post Content, and Quote blocks opt in to the new support.
\n\n\n\nIn theme.json, the gradient can be set through the background styles group, at the root or per block:
\n\n\n\n{\n\t\"styles\": {\n\t\t\"background\": {\n\t\t\t\"gradient\": \"linear-gradient( 135deg, #000 0%, #fff 100% )\"\n\t\t},\n\t\t\"blocks\": {\n\t\t\t\"core/group\": {\n\t\t\t\t\"background\": {\n\t\t\t\t\t\"gradient\": \"var:preset|gradient|vivid-cyan-blue\"\n\t\t\t\t}\n\t\t\t}\n\t\t}\n\t}\n}\n\n\n\nBlock-level values set in the editor override theme defaults, following the same cascade as other block supports.
\n\n\n\nHow it works\n\n\n\nFrontend output. Server-side rendering in the background block support reads the gradient value and passes it, together with any background image, to the style engine. The engine merges them into one comma-separated background-image value and injects the result as an inline style on the block wrapper. Serialization for the image and the gradient is checked independently, so a block can skip one while still rendering the other.
\n\n\n\nSanitization. Previously, safecss_filter_attr() stripped a background-image value that mixed a gradient function with a url(). In WordPress 7.1, safecss_filter_attr() is updated to allow these combined gradient + url() values, so no additional filter is required.
\n\n\n\nRelationship to color.gradient\n\n\n\nbackground.gradient is a separate support from color.gradient. Existing blocks that use color.gradient are unchanged and continue to work exactly as before.
\n\n\n\nThis new support also lays the groundwork for eventually migrating gradient handling from color.gradient to background.gradient across blocks, giving a single, more capable background styling system. That migration is not part of this change.
\n\n\n\nBackwards compatibility\n\n\n\nThese are additive changes. No existing blocks are broken, and no action is required for most blocks and themes. Blocks that do not opt in to background.gradient behave exactly as they did before, including any current use of color.gradient.
\n\n\n\nSummary\n\n\n\nItemValueblock.json support keysupports.background.gradientStyle storage pathstyle.background.gradienttheme.json pathstyles.background.gradient (and per block)Rendered CSS propertybackground-image (comma-separated with any image)Core adopters (7.1)core/group, core/accordion, core/pullquote, core/post-content, core/quote\n\n\n\nFurther Reading\n\n\n\n\nPR #75859: Block Supports: Add background gradient support that can combine with background images\n\n\n\nIssue #32787\n\n\n\n\n#7-1, #blocks, #dev-notes, #dev-notes-7-1
", "id": 16848745, "pubDate": "Sun, 26 Jul 2026 12:18:44 GMT", "whenReceived": "Sun, 26 Jul 2026 13:16:47 GMT", "whenUpdated": "Sun, 26 Jul 2026 13:16:47 GMT", "likes": [], "metadata": { "wpPostId": 124676, "wpSiteId": 38254163 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124685", "title": "New Block Support in WordPress 7.1: Minimum Width", "link": "https://make.wordpress.org/core/2026/07/26/new-block-support-in-wordpress-7-1-minimum-width/", "description": "WordPress 7.1 introduces a minWidth dimension block support, letting blocks opt in to setting a minimum width. This follows the same pattern as the existing minHeight support.
\n\n\n\nGitHub issue: #76525 | PR: #76949
\n\n\n\nBackground\n\n\n\nBlocks already support several dimension properties: height, minHeight, and width. There was no matching control for a minimum width. Setting a floor on a block’s width is a common CSS need. For example, you may want a container or layout element to stay usable and not collapse below a certain size on smaller viewports.
\n\n\n\nUntil now, achieving this required custom CSS or a custom block style, since the design tools did not expose a min-width option. This release handles it natively through a new block support.
\n\n\n\nWhat changed\n\n\n\nA new minWidth feature is registered under the existing dimensions block support. When a block opts in, a “Minimum width” control appears in the Dimensions panel, alongside the existing minimum height control. The value is applied as the CSS min-width property, and it supports dimension presets (dimensionSizes) where a theme provides them.
\n\n\n\nHow to use it\n\n\n\nA block opts in through its block.json supports, the same way it opts in to minHeight:
\n\n\n\n{\n\t\"supports\": {\n\t\t\"dimensions\": {\n\t\t\t\"minWidth\": true\n\t\t}\n\t}\n}\n\n\n\nTo enable the setting for all blocks that support it, use theme.json. You can turn it on directly, or through Appearance Tools:
\n\n\n\n{\n\t\"settings\": {\n\t\t\"dimensions\": {\n\t\t\t\"minWidth\": true\n\t\t}\n\t}\n}\n\n\n\nYou can also set a value in theme.json, either globally or per block:
\n\n\n\n{\n\t\"styles\": {\n\t\t\"dimensions\": {\n\t\t\t\"minWidth\": \"400px\"\n\t\t},\n\t\t\"blocks\": {\n\t\t\t\"core/group\": {\n\t\t\t\t\"dimensions\": {\n\t\t\t\t\t\"minWidth\": \"400px\"\n\t\t\t\t}\n\t\t\t}\n\t\t}\n\t}\n}\n\n\n\nIf the active theme defines dimensionSizes presets, the control offers those presets, and selecting one applies the matching --wp--preset--dimension--{slug} custom property.
\n\n\n\nWhere the control appears\n\n\n\nThe minimum width control follows the same visibility rules as other optional design tools:
\n\n\n\n\nIn the block inspector, the control is not shown by default. A block must opt in through __experimentalDefaultControls to show it automatically. Otherwise, you reveal it from the panel’s options menu (the three-dots menu on the Dimensions panel header).\n\n\n\nIn Global Styles (Site Editor), the control is shown by default.\n\n\n\n\nBlock-level values set in the editor override the theme defaults, following the same cascade as other block supports.
\n\n\n\nBackwards compatibility\n\n\n\nThese are additive changes. No existing blocks are broken, and no action is required for most blocks and themes. Blocks that do not opt in behave exactly as before. Themes that do not enable the setting see no change.
\n\n\n\nSummary\n\n\n\nLayerKeyblock.json supportsupports.dimensions.minWidththeme.json settingsettings.dimensions.minWidththeme.json stylestyles.dimensions.minWidthCSS propertymin-widthPreset sourcedimensionSizes (--wp--preset--dimension--{slug})\n\n\n\nFurther Reading\n\n\n\n\nPR: Block Supports: Add min width support to dimensions (#76949)\n\n\n\nIssue: #76525\n\n\n\n\n#7-1, #blocks, #dev-notes, #dev-notes-7-1
\n\n\n\n", "id": 16848746, "pubDate": "Sun, 26 Jul 2026 12:14:42 GMT", "whenReceived": "Sun, 26 Jul 2026 13:16:47 GMT", "whenUpdated": "Sun, 26 Jul 2026 13:16:47 GMT", "likes": [], "metadata": { "wpPostId": 124685, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Sun, 26 Jul 2026 11:04:31 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68924", "title": "PTE Request for Image Optimization…", "link": "https://make.wordpress.org/polyglots/2026/07/26/pte-request-for-image-optimization/", "description": "PTE Request for Image Optimization Plugins in #fa_IR
\nHello Polyglots team,
\nI hope you are doing well.
I would like to request Project Translation Editor (PTE) status for #fa_IR for the following plugins:
\nQuickWebP — https://fa.wordpress.org/plugins/quickwebp/
\nProject translation status: 100% + Readme 100% | My contribution: 100%
\nShortPixel Image Optimiser — https://fa.wordpress.org/plugins/shortpixel-image-optimiser/
\nProject translation status: 100% + Readme 100% | My contribution: 60%
\nCIMO Image Optimizer — https://fa.wordpress.org/plugins/cimo-image-optimizer/
\nProject translation status: 100% + Readme 100% | My contribution: 100%
\nEWWW Image Optimizer — https://fa.wordpress.org/plugins/ewww-image-optimizer/
\nProject translation status: 100% + Readme 100% | My contribution: 70%
\nI have contributed to the translation of these plugins as listed above, and the readme files have also been fully translated.
\nMy goal in requesting PTE access is not only to help with the current strings, but also to maintain these projects over time. I consider myself committed to keeping future translations for these plugins updated according to current standards, reviewing and approving upcoming submissions, updating newly added strings promptly, and maintaining consistency in terminology and style across these image optimization and performance-related plugins.
\nThese plugins are widely used and include many technical and user-facing strings, so having consistent, accurate, and up-to-date Persian translations can help improve usability for the fa_IR community.
\nProfile: https://profiles.wordpress.org/saeidafshari/
\nThank you very much for your time and consideration.
\nBest regards,
\nSaeid Afshari
\n\n #fa_ir \n\n\n#editor-requests
", "id": 16847232, "pubDate": "Sun, 26 Jul 2026 10:50:19 GMT", "whenReceived": "Sun, 26 Jul 2026 11:04:31 GMT", "whenUpdated": "Mon, 27 Jul 2026 07:08:35 GMT", "likes": [], "metadata": { "wpPostId": 68924, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68921", "title": "PTE Request for Rectus Content Access for MCP", "link": "https://make.wordpress.org/polyglots/2026/07/26/pte-request-for-rectus-content-access-for-mcp/", "description": "I am the plugin author for Rectus Content Access for MCP. 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\n #ja – @rectuswp (@tobifjellner)\n\n\nName: Rectus Content Access for MCP
\nURL: https://wordpress.org/plugins/rectus-content-access-for-mcp/
\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16843389, "pubDate": "Sun, 26 Jul 2026 02:08:19 GMT", "whenReceived": "Sun, 26 Jul 2026 02:43:05 GMT", "whenUpdated": "Mon, 27 Jul 2026 05:28:11 GMT", "likes": [], "metadata": { "wpPostId": 68921, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68903", "title": "PTE Request for Radermacher AI Media Marker", "link": "https://make.wordpress.org/polyglots/2026/07/25/pte-request-for-radermacher-ai-media-marker/", "description": "I am the plugin author for Radermacher AI Media Marker. I have imported a complete German translation (71 strings, informal and formal), which is currently waiting for review, and I would like to be able to maintain and approve translations for this plugin going forward.
\n\nhttps://wordpress.org/plugins/radermacher-ai-media-marker/\n\nhttps://translate.wordpress.org/projects/wp-plugins/radermacher-ai-media-marker/\n\n\n\n #de_DE – @chrisrade\n\n\nOne note for whoever reviews the strings: “suggestions” is translated as “Vorschläge” and carries the warning “The translation appears to be missing the initial lowercase”. That is a false positive – German capitalises all nouns.
\nThank you!
\n#editor-requests
", "id": 16840840, "pubDate": "Sat, 25 Jul 2026 20:36:31 GMT", "whenReceived": "Sat, 25 Jul 2026 21:41:56 GMT", "whenUpdated": "Sat, 25 Jul 2026 21:41:56 GMT", "likes": [], "metadata": { "wpPostId": 68903, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68905", "title": "Hi Polyglots, I am…", "link": "https://make.wordpress.org/polyglots/2026/07/25/hi-polyglots-i-am/", "description": "Link Map Insights – Japanese
\nHi Polyglots,
I am the plugin author for Link Map Insights.
\n\nhttps://wordpress.org/plugins/link-map-insights/\n\n\nI would like to request PTE for Japanese (ja) so that I can maintain the translations of my own plugin. Version 1.2.0 moved all interface strings to English in the source and ships a bundled Japanese translation, and I have submitted the Japanese translations for both the plugin strings and the readme on GlotPress (Stable, Stable Readme, Development and Development Readme are all at 100% and waiting for approval).
\n\n #ja @seoryco\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16840841, "pubDate": "Sat, 25 Jul 2026 20:36:21 GMT", "whenReceived": "Sat, 25 Jul 2026 21:41:56 GMT", "whenUpdated": "Sat, 25 Jul 2026 21:41:56 GMT", "likes": [], "metadata": { "wpPostId": 68905, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68908", "title": "Hi Polyglots team, I’m…", "link": "https://make.wordpress.org/polyglots/2026/07/25/hi-polyglots-team-im/", "description": "Cancello to Danish
\nHi Polyglots team,
I’m the author of the plugin “Cancello – Withdrawal & Returns for WooCommerce”
\nand would like PTE access to review/import translations for it.
Plugin: https://wordpress.org/plugins/cancello-for-woocommerce/
\n\n #da_DK @579aps\n\n\nI have a complete Danish translation ready to import. Thanks!
\n#editor-requests
", "id": 16840842, "pubDate": "Sat, 25 Jul 2026 20:36:08 GMT", "whenReceived": "Sat, 25 Jul 2026 21:41:56 GMT", "whenUpdated": "Sat, 25 Jul 2026 21:41:56 GMT", "likes": [], "metadata": { "wpPostId": 68908, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68911", "title": "PTE Request for Alynivo –…", "link": "https://make.wordpress.org/polyglots/2026/07/25/pte-request-for-alynivo/", "description": "PTE Request for Alynivo – Live Chat & AI Chatbots
\nI am the plugin author for Alynivo – Live Chat & AI Chatbots. I have submitted the German translation for the plugin’s readme (short description, description, FAQ, installation, privacy statement, screenshots) and would like review/PTE assignment so it can go live on the German plugin page.
\n\nhttps://wordpress.org/plugins/alynivo/\n\n\n\n #de_DE – @genco87\n\n\nThank you!
\n#editor-requests
", "id": 16840843, "pubDate": "Sat, 25 Jul 2026 20:35:54 GMT", "whenReceived": "Sat, 25 Jul 2026 21:41:56 GMT", "whenUpdated": "Sat, 25 Jul 2026 21:41:56 GMT", "likes": [], "metadata": { "wpPostId": 68911, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/training/feed/", "whenReceived": "Sat, 25 Jul 2026 14:54:21 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/training/feed/", "guid": "https://make.wordpress.org/training/?p=175408", "title": "Training Team Meeting Recap – 21st July 2026", "link": "https://make.wordpress.org/training/2026/07/25/training-team-meeting-recap-21st-july-2026/", "description": "Meeting Agenda: https://github.com/WordPress/Learn/issues/3562
\n\n\n\nSlack Log: https://wordpress.slack.com/archives/C02RW657Q/p1784617208318259
\n\n\n\nIntroductions and Welcome\n\n\n\nThere were 30 attendees in total: @noruzzaman, @sibokul, @jadavsanjay, @mirmpro, @vishitshah, @dhavalkapadane, @dilip2615, @jenish1234, @csheba, @nikola93n, @rjekic, @sumitsingh, @pravin1996, @rfluethi, @makanikaran, @ravigadhiyawp, @rollybueno, @mohkatz, @sonaliprajapati, @rithika3, @gohelkunjan, @webgrrrl (async), @palak678, @freewebmentor, @andrewssanya (async), @ursha (async), @dhrumilk, @valeriewandeler (async), @priyankaadbrains (async), @VasantRajput (async)
\n\n\n\nNewcomers: @drcwp, @upekar99, @jenish1234
\n\n\n\nNote taker: @sibokul
\n\n\n\nMeeting hosted by: @devmuhib
\n\n\n\nMeeting Note reviewer: @VasantRajput
\n\n\n\nWelcome! 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 or our Guide Program.
\n\n\n\nNews\n\n\n\nHere is our current note-taker roster:
\n\n\n\n\n21st July – @sibokul\n\n\n\n28th July – @pravin1996\n\n\n\n4th August – @mohkatz\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\n\nLooking for feedback\n\n\n\n\nThe Training Team is planning to host Office Hours on July 26, 2026, and is seeking community feedback and participation to make the session successful.\n\n\n\n\n\nContributors were asked to confirm whether they support the proposed date and to volunteer for key roles, including meeting host and note-taker. When asked about the meeting agenda, the organizers confirmed that the discussion topics will be shared in a dedicated post soon. In the meantime, contributors were directed to the list of ongoing Office Hours issues and the project board containing the planned discussion topics.\n\n\n\n\n\nThe team also invited feedback on how to improve future Office Hours and encourage greater community participation. Contributors are encouraged to share suggestions either during discussions or through the corresponding GitHub issue – https://github.com/WordPress/Learn/issues/3535\n\n\n\n\n\nThe Training Team is actively updating its handbooks and continues to welcome community contributions. Contributors are encouraged to share suggestions, improvements, and ideas to help enhance the handbook content. Feedback can be submitted through the https://github.com/WordPress/Learn/issues/3447 initiative and will play an important role in improving the documentation for the entire community.\n\n\n\n\nLooking for volunteers\n\n\n\n\nThe Training Team is looking for volunteers to support several ongoing initiatives aimed at improving Learn WordPress resources and maintaining the team’s GitHub repository.\n\n\n\n\n\nVolunteers are needed to review and consolidate existing content by joining one of two groups: one focused on updating the Training Team handbooks and another dedicated to reviewing course materials. The team will help organize contributors and guide them through the process.\n\n\n\n\n\nIn addition, contributors are invited to assist with creating thumbnails for Learn WordPress lessons that still need visual assets. This creative initiative is being coordinated through the Create Thumbnails for Learn WordPress Lessons (#3428) project.\n\n\n\n\n\nWe currently have 530 open issues. It would be great to get support in reviewing and reducing their number. You can help by:\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\n\nUpdate for last week’s triage squad\n\n\n\n\nThere were no meetings last week.\n\n\n\n\nOther news\n\n\n\n\nWe’re Looking for WCUS 2026 Contributor Day Table Leads! If you’re planning to attend and would like to represent Traning team, or know someone who would be a great fit, please submit a nomination. We’d love to have you join us!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#meeting-recap, #training-team
", "id": 16836244, "pubDate": "Sat, 25 Jul 2026 13:17:27 GMT", "whenReceived": "Sat, 25 Jul 2026 14:54:21 GMT", "whenUpdated": "Sat, 25 Jul 2026 14:54:21 GMT", "likes": [], "metadata": { "wpPostId": 175408, "wpSiteId": 46403572 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Fri, 24 Jul 2026 22:07:03 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68900", "title": "Hola, equip de traducció de català", "link": "https://make.wordpress.org/polyglots/2026/07/24/hola-equip-de-traduccio-de-catala/", "description": "Could you please review/approve PTE access for WordPress.org user bigtechnothanks for WP Statistics in Catalan (ca)?
\nThey have contributed ~900 translations and they are waiting for approval. Project: https://translate.wordpress.org/locale/ca/default/wp-plugins/wp-statistics/
#editor-requests
", "id": 16825632, "pubDate": "Fri, 24 Jul 2026 21:33:46 GMT", "whenReceived": "Fri, 24 Jul 2026 22:07:03 GMT", "whenUpdated": "Fri, 24 Jul 2026 22:07:03 GMT", "likes": [], "metadata": { "wpPostId": 68900, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68880", "title": "Hello Danish translation team,", "link": "https://make.wordpress.org/polyglots/2026/07/24/hello-danish-translation-team/", "description": "I have submitted 300 Danish translations for the Customer Reviews for WooCommerce plugin. They are currently waiting for review.
\nCould a Danish translation editor please review them?
\nBecause if everything is ok I want to continue to finish translate whole plugin into danish language.
Project: Customer Reviews for WooCommerce
\nURL: https://wordpress.org/plugins/customer-reviews-woocommerce/
Thank you!
\nSincerely, Catalin
\n#editor-requests
", "id": 16825633, "pubDate": "Fri, 24 Jul 2026 20:42:58 GMT", "whenReceived": "Fri, 24 Jul 2026 22:07:03 GMT", "whenUpdated": "Fri, 24 Jul 2026 22:07:03 GMT", "likes": [], "metadata": { "wpPostId": 68880, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68873", "title": "PTE Request for Destino Access Audit:", "link": "https://make.wordpress.org/polyglots/2026/07/24/pte-request-for-destino-access-audit/", "description": "I’m the author of the plugin Destino Access Audit:
\n\nhttps://wordpress.org/plugins/destino-access-audit/\n\n\nRequesting PTE for:
\n\n #es_ES – @destinoexterior\n\n\n#editor-requests
", "id": 16825634, "pubDate": "Fri, 24 Jul 2026 20:42:48 GMT", "whenReceived": "Fri, 24 Jul 2026 22:07:03 GMT", "whenUpdated": "Fri, 24 Jul 2026 22:07:03 GMT", "likes": [], "metadata": { "wpPostId": 68873, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Fri, 24 Jul 2026 21:57:32 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=88067", "title": "Proposal: Bringing Back the Meetup Organizer Newsletter", "link": "https://make.wordpress.org/community/2026/07/24/proposal-bringing-back-the-meetup-organizer-newsletter/", "description": "The Meetup Organizer Newsletter has been quiet since July 2025. Huge credit to @bjmcsherry, @josvelasco, and @peiraisotta for carrying that one.
\n\n\n\nAs we’re all thinking hard about reconnecting communities, a regular events roundup feels like something worth having again, and I’d like to help bring it back.
\n\n\n\nI’ve been getting more involved in community events (just got approved to organize a meetup in my area ), and I want to lead the charge on getting a V1 out.
\n\n\n\nWhat I’m thinking for V1\n\n\n\nKeeping it simple to start: a monthly post highlighting upcoming and recent events across meetups, WordCamps, Campus Connect, and the “next gen” formats, with the cool things organizers are actually doing front and center.
\n\n\n\nKeeping it sustainable\n\n\n\nFrom what I understand, the old one lapsed partly because it was a lot to put together by hand each month, and that got hard to keep up. One thing I’d like to use is Slack’s built-in AI, Slackbot. It can search across our event channels and pull together a surprisingly solid first draft in minutes. The idea is to let it do the heavy gathering, then a human pass to polish, fact-check, and pick photos, so it never falls entirely on one person to write from scratch.
\n\n\n\nNext steps\n\n\n\nI’m going to build a V1 and get a first issue out. To start, I’m planning to pull event updates from a few channels: #community-events, #campusconnect, #community-team, #student-clubs, and #contributor-day. I’ll share the first draft next week, and I’d love your input, now or once the draft is ready, on two things:
\n\n\n\n\nWhat made the old newsletter useful, or what you’d change.\n\n\n\nOther channels or sources I should add.\n\n\n\n\nAnd if you worked on it before, I especially want to hear from you.
\n\n\n#highlight, #proposal", "id": 16825457, "pubDate": "Fri, 24 Jul 2026 20:42:17 GMT", "whenReceived": "Fri, 24 Jul 2026 21:57:32 GMT", "whenUpdated": "Fri, 24 Jul 2026 21:57:32 GMT", "likes": [], "metadata": { "wpPostId": 88067, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Fri, 24 Jul 2026 22:07:03 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68882", "title": "Hi Polyglots, I am the…", "link": "https://make.wordpress.org/polyglots/2026/07/24/hi-polyglots-i-am-the-11/", "description": "Hi Polyglots,
\nI am the plugin author of Hirca Keywords Linker.
\nCould you please grant me PTE (Project Translation Editor) permissions for Persian (fa_IR) for my plugin?
Plugin: https://wordpress.org/plugins/hirca-keywords-linker/
\nWordPress.org username: @masoudb
Thank you!
\n#editor-requests
", "id": 16825635, "pubDate": "Fri, 24 Jul 2026 20:27:01 GMT", "whenReceived": "Fri, 24 Jul 2026 22:07:03 GMT", "whenUpdated": "Sat, 25 Jul 2026 21:41:56 GMT", "likes": [], "metadata": { "wpPostId": 68882, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68875", "title": "I am the plugin author.", "link": "https://make.wordpress.org/polyglots/2026/07/24/i-am-the-plugin-author-123/", "description": "I have completed translations for:
\n\n #es_ES\n\n\n— ja
\n— nl_NL
All strings are in Waiting. Please grant me PTE rights for these locales.
\nPlugin: https://wordpress.org/plugins/simple-connection-for-chronofresh-woocommerce/
\nThank you!
\n#editor-requests
", "id": 16819191, "pubDate": "Fri, 24 Jul 2026 16:29:07 GMT", "whenReceived": "Fri, 24 Jul 2026 17:06:11 GMT", "whenUpdated": "Sat, 25 Jul 2026 21:41:56 GMT", "likes": [], "metadata": { "wpPostId": 68875, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68871", "title": "I am the plugin author…", "link": "https://make.wordpress.org/polyglots/2026/07/24/i-am-the-plugin-author-122/", "description": "I am the plugin author of **SEV WebP Migrator for W3TC**.
\n\nhttps://wordpress.org/plugins/sev-webp-migrator-for-w3tc/\n\n\n\n #de_DE – @hfranz (@tobifjellner)\n\n #fr_FR – @hfranz\n\n\nThank you!
\n#editor-requests
", "id": 16819192, "pubDate": "Fri, 24 Jul 2026 16:07:49 GMT", "whenReceived": "Fri, 24 Jul 2026 17:06:11 GMT", "whenUpdated": "Fri, 24 Jul 2026 22:07:03 GMT", "likes": [], "metadata": { "wpPostId": 68871, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68860", "title": "PTE Request for Semantika AI Discovery Surfaces", "link": "https://make.wordpress.org/polyglots/2026/07/24/pte-request-for-semantika-ai-discovery-surfaces/", "description": "Hello Polyglots team,
\nI am the plugin author for Semantika AI Discovery Surfaces. I have submitted translations for Portuguese (Portugal) and would like to request a review of the waiting translations.
\nPlugin:
\n\nhttps://wordpress.org/plugins/semantika-ai-discovery-surfaces/\n\n\nTranslation project:
\n\nhttps://translate.wordpress.org/locale/pt/default/wp-plugins/semantika-ai-discovery-surfaces/\n\n\nThe following translations are currently waiting for review:
\n\nStable: 286 strings\n\nStable Readme: 52 strings\n\n\nThe translations were prepared using the Portuguese (Portugal) translation guide and locale glossary. Please review them and provide any corrections or feedback needed.
\nIf the translations meet the locale’s quality standards, please add the following WordPress.org user as a Project Translation Editor for this plugin:
\n\n #pt_PT – @buzzvel (@tobifjellner)\n\n\nI understand that the Portuguese translation team reviews contributions before granting PTE access. I am available to participate in the Portuguese WordPress community’s #traducao Slack channel and address any requested changes.
\nIf you have any questions, please comment here. Thank you!
\n#editor-requests
", "id": 16819195, "pubDate": "Fri, 24 Jul 2026 15:15:30 GMT", "whenReceived": "Fri, 24 Jul 2026 17:06:11 GMT", "whenUpdated": "Fri, 24 Jul 2026 22:07:03 GMT", "likes": [], "metadata": { "wpPostId": 68860, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68862", "title": "I am the author and…", "link": "https://make.wordpress.org/polyglots/2026/07/24/i-am-the-author-and/", "description": "I am the plugin author of several plugins.
\n\n**Simple Connection for ChronoFresh** https://wordpress.org/plugins/simple-connection-for-chronofresh-woocommerce/\n\n**Tlloancy Step Configurator for WooCommerce** https://wordpress.org/plugins/tlloancy-step-configurator-for-woocommerce/\n\n**Tlloancy Kitchen Line** https://wordpress.org/plugins/tlloancy-kitchen-line/\n\n\nCould you please grant me PTE status for locale **fr** so I can validate them?
\n\n #fr_FR \n\n\nThank you!
\n#editor-requests
", "id": 16816693, "pubDate": "Fri, 24 Jul 2026 14:40:39 GMT", "whenReceived": "Fri, 24 Jul 2026 15:26:09 GMT", "whenUpdated": "Fri, 24 Jul 2026 22:07:03 GMT", "likes": [], "metadata": { "wpPostId": 68862, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68852", "title": "PTE Request for Websel Sözleşmeler…", "link": "https://make.wordpress.org/polyglots/2026/07/24/pte-request-for-websel-sozlesmeler/", "description": "PTE Request for Websel Sözleşmeler
\nHello Polyglots!
\nI am the plugin author of Websel Sözleşmeler for WooCommerce
\n(https://wordpress.org/plugins/websel-sozlesmeler/). Please add my
\nWordPress.org user @webseldonusum as translation editor (PTE) for the
\nfollowing plugin and locale:
I have already submitted the Turkish readme translations (native
\nTurkish speaker; the plugin targets the Turkish market).
Thank you!
\n#editor-requests
", "id": 16814215, "pubDate": "Fri, 24 Jul 2026 12:55:51 GMT", "whenReceived": "Fri, 24 Jul 2026 13:46:04 GMT", "whenUpdated": "Fri, 24 Jul 2026 13:46:04 GMT", "likes": [], "metadata": { "wpPostId": 68852, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68856", "title": "PTE Request for Utopique plugins", "link": "https://make.wordpress.org/polyglots/2026/07/24/pte-request-for-utopique-plugins/", "description": "Hi Polyglots Team !
\nI am the plugin author for 8 plugins:
\n\nhttps://wordpress.org/plugins/better-comments/\n\nhttps://wordpress.org/plugins/flashspeed/\n\nhttps://wordpress.org/plugins/salesaver/\n\nhttps://wordpress.org/plugins/sitemapster/\n\nhttps://wordpress.org/plugins/sky-changelog-notifier/\n\nhttps://wordpress.org/plugins/sky-login-redirect/\n\nhttps://wordpress.org/plugins/spamjam/\n\nhttps://wordpress.org/plugins/typo-hunter/\n\n\nPlease add the following WordPress.org users as translation editors for their respective locales:
\n\n #fr_FR – @skyminds\n\n\n— en_GB – @skyminds
\nThank you!
\nBest regards,
\nMatt Biscay
#editor-requests
", "id": 16814216, "pubDate": "Fri, 24 Jul 2026 12:30:34 GMT", "whenReceived": "Fri, 24 Jul 2026 13:46:04 GMT", "whenUpdated": "Fri, 24 Jul 2026 22:07:03 GMT", "likes": [], "metadata": { "wpPostId": 68856, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68854", "title": "Hi Polyglots team 👋", "link": "https://make.wordpress.org/polyglots/2026/07/24/hi-polyglots-team-%f0%9f%91%8b-4/", "description": "
\nI’m the author of the plugin Comptabilité et Export FEC for WooCommerce (@studioferreiro). On July 14 I submitted a complete fr_FR translation â 105 strings (interface + readme) â but they’re all still Waiting:
\n – Readme / public page (63 strings): https://translate.wordpress.org/projects/wp-plugins/compta-fec-for-woocommerce/stable-readme/fr/default/
\n – Interface (42 strings): https://translate.wordpress.org/projects/wp-plugins/compta-fec-for-woocommerce/stable/fr/default/
I also posted a PTE request on July 14 at make.wordpress.org/polyglots, with no response yet.
\nThe plugin targets a French-only audience (the “FEC” is a French tax-filing obligation) and its UI is already in French; only the public repository page stays in English until the strings are approved.
\n Could someone from the French locale team please:
\n 1. approve the 105 pending fr_FR strings, and/or
\n 2. grant me PTE so I can manage future releases?
#fr_FR â @studioferreiro
\nThanks for your volunteer work ð
\n#editor-requests
", "id": 16811979, "pubDate": "Fri, 24 Jul 2026 11:06:19 GMT", "whenReceived": "Fri, 24 Jul 2026 12:05:51 GMT", "whenUpdated": "Fri, 24 Jul 2026 12:05:51 GMT", "likes": [], "metadata": { "wpPostId": 68854, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Fri, 24 Jul 2026 10:22:16 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124593", "title": "Registering and rendering SVG icons in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/07/24/registering-and-rendering-svg-icons-in-wordpress-7-1/", "description": "Icon collectionsCreating a collectionRemoving a collectionIconsAdding iconsRemoving an iconIcon block enhancementRendering an icon in PHPStyling iconsStyling React icons from @wordpress/iconsStyling the SVG returned by wp_get_icon()REST API\n\n\n\nWordPress 7.0 added a built-in set of SVG icons that the block editor and the core/icon block can use. In 7.1, this becomes a proper, public API: you can now add your own icons, group them, render them on the server, and read them over the REST API.
\n\n\n\nIcons are registered in one place and can then be used in several: the editor, the REST API, and your own PHP. This note covers the pieces you’ll work with:
\n\n\n\n\nCreating and removing icon collections.\n\n\n\nAdding and removing individual icons.\n\n\n\nBrowsing icons by collection in the Icon block’s picker.\n\n\n\nRendering an icon in PHP with wp_get_icon().\n\n\n\nThe REST API endpoints for collections and icons.\n\n\n\n\nIcon collections\n\n\n\nEvery icon belongs to a collection. A collection is just a named group of icons, and its name becomes a prefix: that’s what makes core/plus different from my-plugin/plus. This lets icons from different sources — WordPress, a plugin, or a third-party icon set — live side by side without clashing.
\n\n\n\nWordPress registers one collection by default, called core, with its own bundled icons.
\n\n\n\nCreating a collection\n\n\n\nAn icon can only be added to a collection that already exists, so start by registering the collection with wp_register_icon_collection().
\n\n\n\nfunction my_plugin_register_icon_collection() {\n\twp_register_icon_collection(\n\t\t'my-plugin',\n\t\tarray(\n\t\t\t'label' => __( 'My Plugin Icons', 'my-plugin' ),\n\t\t\t'description' => __( 'Icons provided by My Plugin.', 'my-plugin' ),\n\t\t)\n\t);\n}\nadd_action( 'init', 'my_plugin_register_icon_collection' );\n\n\n\nThe first argument is the collection name. It must start and end with a lowercase letter or digit, and in between may contain lowercase letters, digits, hyphens, and underscores. The second is an array with a required label and an optional description.
\n\n\n\nRemoving a collection\n\n\n\nUse wp_unregister_icon_collection() with the collection name. Removing a collection also removes every icon in it, so you don’t need to remove the icons one by one. Run this on the init hook, at a later priority than the registration so the collection already exists:
\n\n\n\nfunction my_plugin_unregister_icon_collection() {\n\twp_unregister_icon_collection( 'my-plugin' );\n}\nadd_action( 'init', 'my_plugin_unregister_icon_collection', 20 );\n\n\n\nIcons\n\n\n\nEvery icon name has the form collection/icon-name, for example my-plugin/star. The collection must already be registered when you register the icon.
\n\n\n\nThe icon-name part follows the same rule as a collection name: it must start and end with a lowercase letter or digit, and in between may contain lowercase letters, digits, hyphens, and underscores.
\n\n\n\nAdding icons\n\n\n\nRegister an icon with wp_register_icon(). You give it a label and the SVG itself — either inline as a string (content) or as an absolute path to an .svg file (file_path). Use one or the other, not both.
\n\n\n\nLike the other registration functions, wp_register_icon() returns true on success and false on failure, emitting a _doing_it_wrong() notice that explains why. Registration fails for an invalid name, a name that isn’t namespaced as collection/icon-name, a collection that isn’t registered, a duplicate icon, a missing label, unsupported argument keys, or providing neither content nor file_path (or both).
\n\n\n\nThe SVG is sanitized through wp_kses against a small allowlist: only the <svg>, <path>, and <polygon> elements survive, each limited to a fixed set of attributes. Anything outside that subset — other elements, inline styles, scripts, or event handlers — is stripped. This allowlist is intentionally conservative and may be broadened in the future to cover more shape elements and attributes; see https://github.com/WordPress/gutenberg/pull/75550 for the ongoing work.
\n\n\n\nNote that file_path is read lazily: the file isn’t opened at registration, only when the icon’s content is first needed, during REST retrieval or rendering. So registration can succeed even if the path is wrong; a missing or unreadable file surfaces later as empty content, not as a registration error. Make sure the path resolves on the environment where the icon is used.
\n\n\n\nIcons can go into any registered collection. Most of the time, registering them under your own collection keeps them clearly separated from core’s.
\n\n\n\nfunction my_plugin_register_icons() {\n\t// Register a custom collection first, then add icons to it.\n\twp_register_icon_collection(\n\t\t'my-plugin',\n\t\tarray(\n\t\t\t'label' => __( 'My Plugin Icons', 'my-plugin' ),\n\t\t)\n\t);\n\n\t// An icon from an inline SVG string.\n\twp_register_icon(\n\t\t'my-plugin/star',\n\t\tarray(\n\t\t\t'label' => __( 'Star', 'my-plugin' ),\n\t\t\t'content' => '<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 24 24\"><path d=\"M12 2l2.9 6.9 7.1.6-5.4 4.7 1.6 7L12 18l-6.2 3.2 1.6-7L2 9.5l7.1-.6z\" /></svg>',\n\t\t)\n\t);\n\n\t// An icon from an .svg file shipped with the plugin.\n\twp_register_icon(\n\t\t'my-plugin/heart',\n\t\tarray(\n\t\t\t'label' => __( 'Heart', 'my-plugin' ),\n\t\t\t'file_path' => plugin_dir_path( __FILE__ ) . 'icons/heart.svg',\n\t\t)\n\t);\n}\nadd_action( 'init', 'my_plugin_register_icons' );\n\n\n\nRemoving an icon\n\n\n\nRemove a single icon by name with wp_unregister_icon(), again on the init hook after the icon has been registered. Like the registration functions, it returns true on success and false on failure, emitting a _doing_it_wrong() notice; the only failure case is that the icon isn’t registered.
\n\n\n\nfunction my_plugin_unregister_icon() {\n\twp_unregister_icon( 'my-plugin/star' );\n}\nadd_action( 'init', 'my_plugin_unregister_icon', 20 );\n\n\n\nTo remove every icon in a collection at once, remove the collection instead (see Removing a collection).
\n\n\n\nIcon block enhancement\n\n\n\nThe icon picker in the core Icon block now groups icons by collection, so custom icons from plugins and themes appear alongside the core ones.
\n\n\n\nEach collection has its own tab, plus an “All” tab covering every collection at once. Search filters the selected collection; use the All tab to search across collections. The search query is preserved when switching tabs.
\n\n\n\n\n\n\n\nThe block itself picked up a few more changes:
\n\n\n\n\nFlip and rotate. The toolbar now has controls to flip the icon horizontally or vertically, and a button that rotates it 90 degrees at a time.\n\n\n\nDefault icon. A newly inserted Icon block now starts with core/info instead of an empty placeholder.\n\n\n\nServer rendering via wp_get_icon(). The block’s server-side render now delegates to wp_get_icon() to produce the SVG markup, so a block-rendered icon and one you print yourself with wp_get_icon() go through the same code path.\n\n\n\n\nRendering an icon in PHP\n\n\n\nUse wp_get_icon() to get the SVG markup for any registered icon, ready to print:
\n\n\n\n// A decorative icon at the default 24px size.\necho wp_get_icon( 'core/plus' );\n\n// A 32px icon with an accessible label and an extra CSS class.\necho wp_get_icon(\n\t'my-plugin/star',\n\tarray(\n\t\t'size' => 32,\n\t\t'label' => __( 'Featured', 'my-plugin' ),\n\t\t'class' => 'my-plugin-star',\n\t)\n);\n\n\n\nThe first argument is the icon name. If it isn’t registered, you get an empty string. The optional second argument accepts:
\n\n\n\n\nsize — Width and height in pixels. Defaults to 24. Pass null to keep the SVG’s own size.\n\n\n\nclass — Extra CSS class names for the <svg> element.\n\n\n\nlabel — An accessible label. If you provide one, the icon is announced to screen readers; if you leave it out, the icon is treated as decorative and hidden from them.\n\n\n\n\nStyling icons\n\n\n\nStyling React icons from @wordpress/icons\n\n\n\nSince version 15.0.0, each icon declares fill=\"currentColor\" on its outer <svg>, so a React-rendered icon follows the current text color out of the box. By default the icon inherits color from its ancestors. To apply a different color, set color rather than fill — pass style={ { color } } to the icon:
\n\n\n\nimport { Icon, plus } from '@wordpress/icons';\n\n<Icon icon={ plus } style={ { color: '#3858e9' } } />;\n\n\n\nStyling the SVG returned by wp_get_icon()\n\n\n\nThis markup is sanitized on registration, and the allowlist keeps fill only on the <path> and <polygon> shapes — not on the outer <svg> — and doesn’t permit stroke anywhere, so a stroke-based icon loses its stroke and you should stick to fill-based shapes for now. (This is a current limitation: the allowlist may be relaxed in the future to cover stroke and other attributes; see https://github.com/WordPress/gutenberg/pull/75550 for the ongoing work.) One upshot is that the fill=\"currentColor\" the React icons carry on their <svg> does not survive here, and wp_get_icon() doesn’t add one. That has two consequences:
\n\n\n\n\nInside the Icon block, coloring still works, because the block’s stylesheet sets fill: currentColor on .wp-block-icon svg. A block-rendered icon therefore follows the text color.\n\n\n\nA standalone wp_get_icon() call returns bare markup with no such rule, so by default it renders in the SVG’s own fill (black), not the surrounding text color.\n\n\n\n\nTo make a standalone icon follow the text color, you have two options.
\n\n\n\nSupply your own CSS. Render the icon with a class (wp_get_icon() puts it on the <svg>), then set fill on it — since fill is inherited, it cascades to the shapes:
\n\n\n\necho wp_get_icon( 'my-plugin/star', array( 'class' => 'my-icon' ) );\n\n\n\n.my-icon {\n\tfill: currentColor;\n}\n\n\n\nAlternatively, put fill=\"currentColor\" on the shape when you register the icon. The allowlist keeps fill on <path> and <polygon>, so it survives sanitization and the icon carries its own color behavior wherever it’s rendered:
\n\n\n\nwp_register_icon(\n\t'my-plugin/star',\n\tarray(\n\t\t'label' => __( 'Star', 'my-plugin' ),\n\t\t'content' => '<svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 24 24\"><path fill=\"currentColor\" d=\"M12 2l2.9 6.9 7.1.6-5.4 4.7 1.6 7L12 18l-6.2 3.2 1.6-7L2 9.5l7.1-.6z\" /></svg>',\n\t)\n);\n\n\n\nREST API\n\n\n\nThe editor reads icons and collections over the REST API, and your own code can too. These endpoints are read-only: every route is a GET, so you can browse registered icons and collections but can’t register or change them over REST. All endpoints are under wp/v2 and require an authenticated user who can edit_posts, or who holds the equivalent edit capability for any REST-visible (show_in_rest) post type.
\n\n\n\nCollections:
\n\n\n\n\nGET /wp/v2/icon-collections — All collections.\n\n\n\nGET /wp/v2/icon-collections/<collection> — A single collection.\n\n\n\n\nEach collection is returned as an object with slug, label, and description. For example, GET /wp/v2/icon-collections/core returns:
\n\n\n\n{\n\t\"slug\": \"core\",\n\t\"label\": \"WordPress\",\n\t\"description\": \"Default icon collection.\"\n}\n\n\n\nIcons:
\n\n\n\n\nGET /wp/v2/icons — All icons. (introduced in 7.0 with the name, label, and content fields and the search parameter; 7.1 adds the collection field and parameter)\n\n\n\nGET /wp/v2/icons/<collection> — Icons in one collection. (new in 7.1)\n\n\n\nGET /wp/v2/icons/<collection>/<name> — A single icon. (introduced in 7.0)\n\n\n\n\nEach icon is returned as an object with name (the full collection/icon-name), label, content (the sanitized SVG markup), and collection (the slug of the collection it belongs to). For example, GET /wp/v2/icons/core/plus returns:
\n\n\n\n{\n\t\"name\": \"core/plus\",\n\t\"label\": \"Plus\",\n\t\"content\": \"<svg xmlns=\\\"http://www.w3.org/2000/svg\\\" viewbox=\\\"0 0 24 24\\\"><path d=\\\"M11 12.5V17.5H12.5V12.5H17.5V11H12.5V6H11V11H6V12.5H11Z\\\" /></svg>\",\n\t\"collection\": \"core\"\n}\n\n\n\nThe icon list also accepts two query parameters: search to filter by name or label, and collection to limit results to one collection. For example:
\n\n\n\nGET /wp/v2/icons?collection=my-plugin&search=star\n\n\n\nProps to @tyxla for review.
\n#7-1, #dev-notes, #dev-notes-7-1
", "id": 16809793, "pubDate": "Fri, 24 Jul 2026 08:53:10 GMT", "whenReceived": "Fri, 24 Jul 2026 10:22:16 GMT", "whenUpdated": "Fri, 24 Jul 2026 10:22:16 GMT", "likes": [], "metadata": { "wpPostId": 124593, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Fri, 24 Jul 2026 06:25:31 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68848", "title": "PTE Request for OJapp PWA Marketing", "link": "https://make.wordpress.org/polyglots/2026/07/24/pte-request-for-ojapp-pwa-marketing/", "description": "I am the plugin author for [OJapp PWA Marketing]. 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/ojapp-pwa-marketing/\n\n\n\n #ja – @ojach\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16806906, "pubDate": "Fri, 24 Jul 2026 06:04:44 GMT", "whenReceived": "Fri, 24 Jul 2026 06:25:31 GMT", "whenUpdated": "Fri, 24 Jul 2026 06:25:31 GMT", "likes": [], "metadata": { "wpPostId": 68848, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Fri, 24 Jul 2026 06:37:21 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124768", "title": "React 19: punted beyond WordPress 7.1, experiment in Gutenberg", "link": "https://make.wordpress.org/core/2026/07/24/react-19-punted-beyond-wordpress-7-1-experiment-in-gutenberg/", "description": "WordPress 7.1 continues to use React 18.3\n\n\n\nReact 19 upgrade won’t be a part of WordPress 7.1. After briefly enabling it in Gutenberg we discovered unexpected incompatibilities in how old and new version of React interact with each other, and in the ways how plugins use React, and we were forced to revert the change. We’ll need a considerable testing period where we improve and fine-tune the compatibility layer that allows the existing plugins to run seamlessly.
\n\n\n\nExperimental flag in Gutenberg\n\n\n\nInstead, there is a new experiment in the Gutenberg plugin (since version 23.4) that enables React 19 on your WordPress site, intended for testing plugin compatibility. To enable the experiment, install the Gutenberg plugin and check a checkbox on the Gutenberg Experiments page (under Settings › Gutenberg):
\n\n\n\n\n\n\n\nTesting plugins\n\n\n\nTesting a plugin compatibility generally means trying to use all parts of the plugin that uses React, typically Gutenberg blocks and extensions, and also custom WP Admin pages, and verifying that the UI is not broken and there are no errors logged in the browser console.
\n\n\n\nWhat kind of errors to look for\n\n\n\nTypical failure modes for plugins are:
\n\n\n\n\nBundling the react/jsx-runtime code directly in the plugin JavaScript code instead of using the “externalized” react-jsx-runtime script provided by WordPress itself. Such bundling leads to a mixture of React 18 (bundled) and React 19 (provided by WordPress) running together and passing data structures created by the old version to the new runtime. If everyone was bundling their JavaScript correctly, the majority of compat issues wouldn’t happen at all.\n\n\n\nUsing really old React features that were removed in React 19, after being deprecated for a long time (at least 6 years). String refs, default props on function components, legacy ways of defining context, … Some of them we’re polyfilling in the compat layer. A more detailed overview can be found in the “Removed APIs” section of an earlier post about the React 19 upgrade.\n\n\n\n\nThere is also work in progress to automatically detect these issues as part of the Plugin Check plugin.
\n\n\n\nEveryone is invited to test and update their plugins, and report issues in the Gutenberg GitHub repo.
\n\n\n\n\n\n\n\nProps to @tyxla, @aduth, @simison, @wildworks and @mamaduka for contributions, feedback and code reviews.
\n\n\n\nProps to @tyxla and @aduth for reviewing a draft of this post.
\n#7-1, #dev-notes, #dev-notes-7-1
", "id": 16807083, "pubDate": "Fri, 24 Jul 2026 05:52:30 GMT", "whenReceived": "Fri, 24 Jul 2026 06:37:21 GMT", "whenUpdated": "Fri, 24 Jul 2026 06:37:21 GMT", "likes": [], "metadata": { "wpPostId": 124768, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 23 Jul 2026 20:23:45 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68836", "title": "PTE Request for Page Flipper", "link": "https://make.wordpress.org/polyglots/2026/07/23/pte-request-for-page-flipper/", "description": "Hi Polyglots Team,
\nI am the author of the Page Flipper plugin and would like to request Project Translation Editor (PTE) permissions for the following locales.
\nPlugin:
\n\nhttps://wordpress.org/plugins/page-flipper/\n\n\nRequested PTE:
\n\n #pt_BR – @willderazevedo\n\n\nThank you for your time and support!
\n#editor-requests
", "id": 16798757, "pubDate": "Thu, 23 Jul 2026 20:21:30 GMT", "whenReceived": "Thu, 23 Jul 2026 20:23:45 GMT", "whenUpdated": "Fri, 24 Jul 2026 13:46:04 GMT", "likes": [], "metadata": { "wpPostId": 68836, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Thu, 23 Jul 2026 19:06:53 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=88059", "title": "Rethinking our Monthly Team Meetings", "link": "https://make.wordpress.org/community/2026/07/23/rethinking-our-monthly-team-meetings/", "description": "The problem\n\n\n\nOver the past months we’ve tried two meeting slots at different times, then a 12-hour open window, hoping to catch more people across timezones. Neither change moved the needle. Attendance and participation remain low, and, as we discussed openly in the April meeting, most of the value of these meetings can already be absorbed by reading the agenda or the recap afterward. If a meeting can be fully replaced by a P2 post, it’s not really a meeting anymore.
\n\n\n\nWe (the 2026 Team Reps) have talked this through and want to propose splitting what today is a single monthly meeting into two separate, more focused things.
\n\n\n\nThe proposal\n\n\n\n1. A monthly written update (unchanged in spirit, clarified in purpose)\n\n\n\nWe’ll keep publishing a monthly post at the start of each month summarizing what the team has been working on: policy changes, WordCamps, meetups, Campus Connect recaps, education programs, and anything else worth surfacing for people who can’t follow every P2 post or Slack thread.
\n\n\n\nWhat changes: this stops being “the agenda for a meeting” and becomes its own thing: a monthly digest, written by a different volunteer each month. We think this is a great low-friction way for people to start contributing to team coordination without needing to run a live session.
\n\n\n\n2. Coworking sessions\n\n\n\nInstead of a status-update meeting, we want to try live coworking sessions: blocks of 1–2 hours where a group works together, in real time, on an actual team task.
\n\n\n\nRough shape:
\n\n\n\n\nShort kickoff (5–10 min): whoever’s hosting explains what we’re working on that session and why, and takes quick questions.\n\n\n\nFocused work block: everyone works (same or related tasks) with the channel/call open for “does anyone know how…” questions as they come up.\n\n\n\nWrap-up (10–15 min): quick share of what got done, what’s blocked, and what needs follow-up.\n\n\n\n\nWhy we think this could work\n\n\n\nThe core insight from the discussion was that people don’t show up for information they can get elsewhere, they show up when there’s something to do together, or someone to ask in real time. A status meeting competes with reading a P2 post, and loses. A working session doesn’t have that competition, because you can’t “read” your way into having helped triage the backlog.
\n\n\n\nWe’d love feedback before taking this further:
\n\n\n\n\nDoes the split between “written update” and “coworking” make sense to you?\n\n\n\nAny specific ideas about the coworking sessions format?\n\n\n\nAny concerns about coworking sessions being harder to join for volunteers in less common timezones (worse than a single meeting would be, since we’re not proposing multiple slots yet)?\n\n\n\nShould we pilot this for one or two months before committing, and if so, what would tell us it’s working better than the old format?\n\n\n\n\n\n\n\n\nThanks to @adityakane @thehopemonger and @webtechpooja for reviewing the proposal.
\n#coworking, #meeting, #proposal
", "id": 16796875, "pubDate": "Thu, 23 Jul 2026 18:54:27 GMT", "whenReceived": "Thu, 23 Jul 2026 19:06:53 GMT", "whenUpdated": "Thu, 23 Jul 2026 19:06:53 GMT", "likes": [], "metadata": { "wpPostId": 88059, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/themes/feed/", "whenReceived": "Thu, 23 Jul 2026 17:35:34 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/themes/feed/", "guid": "https://make.wordpress.org/themes/2026/07/23/xpost-accessibility-ready-theme-reviews-extending-the-deadline/", "title": "X-post: Accessibility-ready Theme Reviews: Extending the Deadline", "link": "https://make.wordpress.org/themes/2026/07/23/xpost-accessibility-ready-theme-reviews-extending-the-deadline/", "description": "X-comment from +make.wordpress.org/accessibility: Comment on Accessibility-ready Theme Reviews: Extending the Deadline
", "id": 16794591, "pubDate": "Thu, 23 Jul 2026 17:21:43 GMT", "whenReceived": "Thu, 23 Jul 2026 17:35:34 GMT", "whenUpdated": "Thu, 23 Jul 2026 17:35:34 GMT", "likes": [], "metadata": { "wpPostId": 25110, "wpSiteId": 31759950 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "whenReceived": "Thu, 23 Jul 2026 17:17:41 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "guid": "https://make.wordpress.org/accessibility/?p=17571", "title": "Accessibility-ready Theme Reviews: Extending the Deadline", "link": "https://make.wordpress.org/accessibility/2026/07/23/accessibility-ready-theme-reviews-extending-the-deadline/", "description": "When we announced the new accessibility-ready theme guidelines in May, the accessibility time set an ambitious timeline to re-review all themes and require action from theme authors by June 30th of this year.
\n\n\n\nWell, that date fled by three weeks ago, and the team hasn’t taken action yet to delist any themes.
\n\n\n\nThe team has found that we need more time to be able to reasonably go through all themes and make progress, so we’re extending this deadline until September 30th, 2026.
\n\n\n\nWhat does this deadline mean?\n\n\n\nAs a theme author, we expect you to have contacted the accessibility ready team using our theme accessibility review request form. That review indicates that you have taken steps to improve your theme and move towards the new requirements, and are engaging on the process. As long as you have submitted the form and begun the process of fixing your theme, your theme will not be delisted from the directory.
\n\n\n\nOn October 1st, any theme that has the accessibility-ready tag and has not requested a re-review will be de-listed.
\n\n\n\nWhat does “delisting” a theme mean?\n\n\n\nYour theme is no longer visible in the theme directory. You are still able to submit updates to your theme, and all existing installations of your theme will still receive updates. But it will not appear in any theme directory searches or tag views.
\n\n\n\nWhat if my theme meets the requirements, anyway?\n\n\n\nIf you believe your theme meets the requirements, then submit the request form! We’re logging all the requests, so we have records of everybody who has made this request.
\n\n\n\nIf I meet the old requirements, will I meet the new requirements?\n\n\n\nNo.
\n\n\n\nThere are several new requirements that did not apply to the tag previously, so we expect that all authors will need to make theme updates.
\n\n\n\n\nRead the Requirements\n\n\n\nRequest an Accessibility Review\n\n\n\n\nReviewed by @alh0319
\n\n\n\n\n#accessibility-ready
", "id": 16794169, "pubDate": "Thu, 23 Jul 2026 17:04:42 GMT", "whenReceived": "Thu, 23 Jul 2026 17:17:41 GMT", "whenUpdated": "Thu, 23 Jul 2026 17:17:41 GMT", "likes": [], "metadata": { "wpPostId": 17571, "wpSiteId": 29901991 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Thu, 23 Jul 2026 13:53:51 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124581", "title": "Editor components updates in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/07/23/editor-components-updates-in-wordpress-7-1/", "description": "40px default size for form controlsWhat changedWhat to doAffected componentsNot includedChanges for consumers styling with EmotionRemove NavigationRemove __experimentalApplyValueToSides\n\n\n\n40px default size for form controls\n\n\n\nStarting in WordPress 7.1, @wordpress/components form controls use a 40px default height unconditionally. The opt-in __next40pxDefaultSize prop is no longer needed and has no runtime effect when passed.
\n\n\n\nThis completes the rollout that followed the soft deprecation in WordPress 6.8. The prop was introduced in WordPress 6.7 so plugins could opt in early. Since 6.8, components that had not opted in logged a console warning.
\n\n\n\nWhat changed\n\n\n\n\nAffected components now render at 40px by default without the prop.\n\n\n\nPassing __next40pxDefaultSize is ignored at runtime.\n\n\n\nPassing __next40pxDefaultSize={ false } no longer opts out to the previous 36px height.\n\n\n\nOn BorderBoxControl, BorderControl, FontSizePicker, and ToggleGroupControl, the size prop is also deprecated and has no effect.\n\n\n\n\nWhat to do\n\n\n\nRemove __next40pxDefaultSize from your component usage. No replacement prop is needed.
\n\n\n\nIf you were passing size=\"__unstable-large\" on the components listed only to get 40px height, remove that as well.
\n\n\n\nAffected components\n\n\n\nFor links to the code changes, see tracking issue #65751.
\n\n\n\n@wordpress/components
\n\n\n\nBorderBoxControl, BorderControl, BoxControl, ComboboxControl, CustomSelectControl, FontSizePicker, FormFileUpload, FormTokenField, FocalPointPicker, InputControl, NumberControl, QueryControls, Radio, RangeControl, SearchControl, SelectControl, TextControl, ToggleGroupControl, TreeSelect, UnitControl
\n\n\n\n@wordpress/block-editor
\n\n\n\nFontAppearanceControl, FontFamilyControl, LetterSpacingControl, LineHeightControl
\n\n\n\nNot included\n\n\n\nThis rollout covers form controls only. Button still uses the opt-in prop and is unchanged.
\n\n\n\n\n\n\n\nChanges for consumers styling with Emotion\n\n\n\nA long-running migration has kickstarted in the @wordpress/components package, with the goal of refactoring all Emotion-based styles to SCSS modules.
\n\n\n\nMost consumers should not need to change anything, but if you do use Emotion to style your components, there are two migration details for code that relied on Emotion-specific behavior:
\n\n\n\n\nView still accepts the legacy css prop for type compatibility, but it is now a no-op. Use style for inline styles or className for CSS-based styling.\n\n\n\nWhen using cx() with Emotion css() fragments, compose source-order-dependent fragments into a single css() call before passing them to cx(). Passing separate fragments can change override order now that View no longer renders through Emotion.\n\n\n\n\nExample:
\n\n\n\nconst classes = cx(\n\tcss(\n\t\tbaseStyles,\n\t\tcondition && overrideStyles\n\t),\n\tclassName\n);\n\n\n\nThis keeps shorthand/longhand overrides and nested-selector overrides in one generated class, preserving the intended cascade order.
\n\n\n\nThe affected components are:
\n\n\n\n\nDivider\n\n\n\nSurface\n\n\n\nTruncate\n\n\n\nView\n\n\n\nFlex\n\n\n\nSpacer\n\n\n\n\nThe list is expected to grow as the migration continues. Follow #66806 for more details.
\n\n\n\n\n\n\n\nRemove Navigation\n\n\n\nStarting in WordPress 7.1, the deprecated Navigation component and its subcomponents are removed from @wordpress/components (#78529).
\n\n\n\nThe component has been deprecated since WordPress 6.8. Use the Navigator component instead.
\n\n\n\n\n\n\n\nRemove __experimentalApplyValueToSides\n\n\n\nStarting in WordPress 7.1, the __experimentalApplyValueToSides utility is removed from @wordpress/components (#78528).
\n\n\n\nThe utility has been deprecated since WordPress 6.8. BoxControl itself is unaffected.
\n\n\n\n\n\n\n\nCo-authored by @0mirka00 and @mciampini.
\n\n\n\nProps to @aduth for review.
\n\n\n\n\n#7-1, #dev-notes, #dev-notes-7-1
", "id": 16788762, "pubDate": "Thu, 23 Jul 2026 12:51:14 GMT", "whenReceived": "Thu, 23 Jul 2026 13:53:51 GMT", "whenUpdated": "Thu, 23 Jul 2026 13:53:51 GMT", "likes": [], "metadata": { "wpPostId": 124581, "wpSiteId": 38254163 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124817", "title": "Editable blocks inside the Custom HTML block", "link": "https://make.wordpress.org/core/2026/07/23/editable-blocks-inside-the-custom-html-block/", "description": "In WordPress 7.1, the Custom HTML block supports interleaving static HTML with regular, editable blocks (79115):
\n\n\n\n<!-- wp:html -->\n<div class=\"banner\"><h1>Static heading</h1><!-- wp:paragraph -->\n<p>Editable paragraph</p>\n<!-- /wp:paragraph --><footer>Static footer</footer></div>\n<!-- /wp:html -->\n\n\n\nIn the editor, the static markup renders inert while the inner blocks are editable in place — but locked: they can’t be moved, removed, or have siblings added. The surrounding structure stays intact. The full markup remains accessible in the “Edit HTML” modal, and serialization round-trips unchanged, so existing content is unaffected.
\n\n\n\nThis also makes block markup a friendlier target for AI tools: a model can generate one Custom HTML block mixing arbitrary markup with editable slots — no custom block, no build step — and the output is immediately safe to edit.
\n\n\n\nRegistering variations as “higher level blocks”\n\n\n\nBlock variations now accept an innerContent field (79659): an array of static HTML fragments where each null marks the position of the corresponding innerBlocks entry. This lets you ship a fixed markup shell with editable slots as its own inserter item — no custom block needed:
\n\n\n\nwp.blocks.registerBlockVariation( 'core/html', {\n name: 'testimonial-card',\n title: 'Testimonial Card',\n icon: 'format-quote',\n innerContent: [ '<div class=\"testimonial-card\">', null, '</div>' ],\n innerBlocks: [\n [ 'core/paragraph', { content: 'An inspiring quote.' } ],\n ],\n} );\n\n\n\nInserting the variation produces a Custom HTML block with the preset structure and an editable paragraph inside it. Unlike a pattern, the user can edit only the designated slots, not the structure.
\n\n\n\ninnerContent only applies to core/html variations; it is ignored elsewhere.
\n#7-1, #blocks, #dev-notes, #dev-notes-7-1
", "id": 16788763, "pubDate": "Thu, 23 Jul 2026 12:29:20 GMT", "whenReceived": "Thu, 23 Jul 2026 13:53:51 GMT", "whenUpdated": "Thu, 23 Jul 2026 13:53:51 GMT", "likes": [], "metadata": { "wpPostId": 124817, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 23 Jul 2026 13:16:06 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68827", "title": "PTE Request for…", "link": "https://make.wordpress.org/polyglots/2026/07/23/post-title-pte-request-for-73/", "description": "(Post Title) PTE Request for Invoicing Integration for sevDesk and WooCommerce
\nI am the plugin author for Invoicing Integration for sevDesk and WooCommerce. 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/invoicing-integration-for-sevdesk-and-woocommerce/\n\n\n\n #de_DE – @devikit\n\n\n#editor-requests
", "id": 16788018, "pubDate": "Thu, 23 Jul 2026 11:49:28 GMT", "whenReceived": "Thu, 23 Jul 2026 13:16:06 GMT", "whenUpdated": "Thu, 23 Jul 2026 13:42:22 GMT", "likes": [], "metadata": { "wpPostId": 68827, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68825", "title": "PTE Request for QuoteFrameShare & Contributor Photo Gallery", "link": "https://make.wordpress.org/polyglots/2026/07/23/pte-request-for-quoteframeshare-contributor-photo-gallery/", "description": "Please make me a PTE for my two plugins to add/moderate translations.
\n\nhttps://wordpress.org/plugins/contributor-photo-gallery/\n\nhttps://wordpress.org/plugins/quoteframeshare-blockquote-share-copy/\n\n\n\n #hi_IN \n\n\n#editor-requests
", "id": 16786079, "pubDate": "Thu, 23 Jul 2026 10:59:40 GMT", "whenReceived": "Thu, 23 Jul 2026 11:46:46 GMT", "whenUpdated": "Thu, 23 Jul 2026 20:23:45 GMT", "likes": [], "metadata": { "wpPostId": 68825, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Thu, 23 Jul 2026 10:33:07 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124703", "title": "Media Library infinite scrolling is now enabled by default, with a per-user opt-out", "link": "https://make.wordpress.org/core/2026/07/23/media-library-infinite-scrolling-is-now-enabled-by-default-with-a-per-user-opt-out/", "description": "Background\n\n\n\nThe grid view of the Media Library (including the Media Modal) has supported infinite scrolling for a long time, where attachments load automatically as you scroll instead of behind a Load more button. That behavior was controlled by the media_library_infinite_scrolling filter, which defaulted to false since WordPress 5.8 due to accessibility, performance, and usability concerns (#50105 / r50829 / #40330). As a result, infinite scrolling was effectively off for everyone unless a plugin or theme opted in via the filter.
\n\n\n\nThe Load more button has long been a friction point for users managing large media libraries, and the smoother infinite-scroll experience was hidden behind code that most sites never enabled.
\n\n\n\nWhat changed\n\n\n\nIn WordPress 7.1 (#65564):
\n\n\n\n\nInfinite scrolling is now enabled by default. The media_library_infinite_scrolling filter now defaults to true, so the grid view auto-loads attachments on scroll out of the box. This applies to both the Grid view of the Media Library, and the Media Modal.\n\n\n\nUsers can opt out individually. A new Infinite Scrolling personal option appears on the profile screen (Users > Profile), with a checkbox labeled “Disable infinite scrolling in the Media Library grid view” (unchecked by default). The option is only shown to users who have the upload_files capability, since the attachment grid is unreachable without it.\n\n\n\n\nPrecedence\n\n\n\nThe effective setting is resolved in this order, from highest priority to lowest:
\n\n\n\n\nThe media_library_infinite_scrolling filter: a hooked filter callback always wins.\n\n\n\nThe user’s opt-out preference: applies when no filter is hooked.\n\n\n\nThe default (true): applies when neither of the above is set.\n\n\n\n\nIn other words: filter > user preference > default.
\n\n\n\nDeveloper-facing details\n\n\n\nThe filter’s default changed\n\n\n\nIf your plugin or theme relies on the previous behavior (infinite scrolling off unless explicitly enabled), be aware that the default is now true. To force the previous behavior for all users regardless of their preference, you can use the filter, as it takes precedence over everything:
\n\n\n\n// Force infinite scrolling OFF for all users (restores to the behavior that was default between 5.8 and 7.1).\n\nadd_filter( 'media_library_infinite_scrolling', '__return_false' );\n\n// Force infinite scrolling ON for all users, ignoring per-user opt-out.\n\nadd_filter( 'media_library_infinite_scrolling', '__return_true' );\n\n\n\nBecause the filter runs after the per-user preference is read, adding a callback overrides any individual user’s choice.
\n\n\n\nThe new user option\n\n\n\nThe preference is stored as a user option under the meta key infinite_scrolling, as the string 'true' or 'false', consistent with how existing options such as syntax_highlighting and rich_editing are persisted. It is also wired consistently through the profile form (user-edit.php), the save handler (edit_user()), and persistence in wp_insert_user() and _get_additional_user_keys().
\n\n\n\nYou can read a user’s preference programmatically:
\n\n\n\n// The user setting is 'false' if the user has disabled infinite scrolling, 'true' (or empty) otherwise.\n\n$infinite_scrolling_disabled = 'false' === get_user_option( 'infinite_scrolling', $user_id );\n\n\n\nNote the direction of the stored value: 'false' means the user has disabled infinite scrolling. wp_enqueue_media() reads this option to determine the pre-filter default.
\n\n\n\nBackwards compatibility\n\n\n\n\nThe media_library_infinite_scrolling filter is unchanged in signature; only its default value changed (from false to true). Existing callbacks continue to work exactly as before and still take precedence.\n\n\n\nSites that had already opted in via __return_true see no change.\n\n\n\nSites that never touched the filter now get infinite scrolling by default; users who prefer the Load more button can opt out from their profile.\n\n\n\n\n\n\n\n\nProps to @youknowriad, @khokansardar, @wildworks, @davidbaumwald, @joedolson, @sabernhardt for reviewing.
\n#7-1, #dev-notes, #dev-notes-7-1, #media, #media-library, #media-grid
", "id": 16784375, "pubDate": "Thu, 23 Jul 2026 09:30:50 GMT", "whenReceived": "Thu, 23 Jul 2026 10:33:07 GMT", "whenUpdated": "Thu, 23 Jul 2026 17:14:59 GMT", "likes": [], "metadata": { "wpPostId": 124703, "wpSiteId": 38254163 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124682", "title": "Text Shadow Support in Global Styles", "link": "https://make.wordpress.org/core/2026/07/23/text-shadow-support-in-global-styles/", "description": "WordPress 7.1 introduces the ability to define a text-shadow value in Global Styles through theme.json. Themes can now set a text shadow globally, on specific blocks, and on elements such as links, without a plugin or custom stylesheet.
\n\n\n\nGitHub issue: #47904 | PR: #73320
\n\n\n\nThis is the first step of the text shadow feature. It covers theme.json styling only. A user interface, presets, and per-block-instance controls arrive in the next release. See the “What is not included yet” section below.
\n\n\n\nBackground\n\n\n\nThe CSS text-shadow property has been a frequently requested typography feature (see #47904). Until now, applying a text shadow through the block system was not possible. Theme authors had to add their own CSS to style text shadows, which kept the value outside of theme.json and Global Styles.
\n\n\n\nFully implementing text shadow raises questions that still need discussion, such as the right control for editing shadows and whether shadows should be stored as presets. To make progress without waiting on those decisions, this release adds the smallest useful piece: the ability to declare a text-shadow value directly in theme.json.
\n\n\n\nWhat changed\n\n\n\nA textShadow property is now recognized under styles.typography in theme.json. The value maps directly to the CSS text-shadow property, so any valid text-shadow value works, including multiple comma-separated shadows.
\n\n\n\nThe property is supported in the same places as other typography styles:
\n\n\n\n\nGlobal typography (styles.typography)\n\n\n\nPer-block styles (styles.blocks.<block>.typography)\n\n\n\nElement styles, including states such as :hover (styles.elements.<element>)\n\n\n\n\nThere is no block inspector control and no Global Styles interface for this in this release. The value is set in theme.json only.
\n\n\n\nHow to use it\n\n\n\nSet textShadow under styles.typography to apply a shadow to all text. The example below applies a global shadow, overrides it for the Paragraph block, and removes the shadow from links on hover.
\n\n\n\n{\n\t\"$schema\": \"https://schemas.wp.org/trunk/theme.json\",\n\t\"version\": 3,\n\t\"styles\": {\n\t\t\"typography\": {\n\t\t\t\"textShadow\": \"1px 1px 2px red, 0 0 1em blue, 0 0 0.2em blue\"\n\t\t},\n\t\t\"blocks\": {\n\t\t\t\"core/paragraph\": {\n\t\t\t\t\"typography\": {\n\t\t\t\t\t\"textShadow\": \"1px 1px 2px red, 0 0 1em red, 0 0 0.2em red\"\n\t\t\t\t}\n\t\t\t}\n\t\t},\n\t\t\"elements\": {\n\t\t\t\"link\": {\n\t\t\t\t\":hover\": {\n\t\t\t\t\t\"typography\": {\n\t\t\t\t\t\t\"textShadow\": \"none\"\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-level values override the global value, following the same cascade as other typography styles.
\n\n\n\nEditor behavior\n\n\n\nWhen a global text shadow is set, the shadow is removed from the empty rich text placeholder (for example the “Type / to choose a block” prompt). Without this reset, the placeholder text can become hard to read. The reset applies to the placeholder only. Actual content still renders with the configured shadow in both the editor and on the front end.
\n\n\n\nWhat is not included yet\n\n\n\nThis release covers theme.json styling only. The following are planned for the next release in #79584:
\n\n\n\n\nA text shadow control in the block inspector, so a shadow can be set on an individual block instance.\n\n\n\nA Global Styles interface for browsing, creating, and editing text shadow presets.\n\n\n\nText shadow presets in theme.json (settings.typography.textShadow, textShadowPresets, and defaultTextShadowPresets), each output as a var(--wp--preset--text-shadow--{slug}) custom property.\n\n\n\nA new supports.typography.textShadow block support, enabled first on the Paragraph and Heading blocks.\n\n\n\n\nUntil then, text shadow can be configured through theme.json styles as shown above.
\n\n\n\nBackwards compatibility\n\n\n\nThese are additive changes. No existing blocks or themes are affected, and no action is required. Themes that do not set textShadow behave exactly as before.
\n\n\n\nFurther Reading\n\n\n\n\nPR: Global Styles: Add textShadow style support (#73320)\n\n\n\nTracking issue: Typography: Add “Text shadow” support (#47904)\n\n\n\nFollow-up PR (next release): Add textShadow typography support and UI (#79584)\n\n\n\n\nProps to @wildworks for reviewing this post.
\n#dev-notes, #dev-notes-7-1
", "id": 16782817, "pubDate": "Thu, 23 Jul 2026 08:45:43 GMT", "whenReceived": "Thu, 23 Jul 2026 08:53:21 GMT", "whenUpdated": "Thu, 23 Jul 2026 08:53:21 GMT", "likes": [], "metadata": { "wpPostId": 124682, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 23 Jul 2026 10:06:23 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68819", "title": "PTE Request for Webzone Config Notes", "link": "https://make.wordpress.org/polyglots/2026/07/23/pte-request-for-webzone-config-notes/", "description": "Hi Polyglots,
\nI’m the author of the plugin below and I’d like to become the translation editor (PTE) for its Italian translation. I have already provided the full it_IT translation for the stable project.
\nPlugin:
\n-https://wordpress.org/plugins/webzone-config-notes/
Thank you!
\n#editor-requests
", "id": 16783874, "pubDate": "Thu, 23 Jul 2026 08:38:34 GMT", "whenReceived": "Thu, 23 Jul 2026 10:06:23 GMT", "whenUpdated": "Thu, 23 Jul 2026 10:06:23 GMT", "likes": [], "metadata": { "wpPostId": 68819, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68814", "title": "Hi Polyglots,", "link": "https://make.wordpress.org/polyglots/2026/07/23/hi-polyglots-122/", "description": "I’m the plugin author of Grip Popup Banner. My team and I have submitted the Japanese (ja) translation for the plugin and its readme (100% translated), and we’d like to maintain it going forward.
\nCould you please grant PTE (Project Translation Editor) for Japanese to the following WordPress.org account?
\n – Plugin: https://wordpress.org/plugins/grip-popup-banner/
\n – Locale: Japanese (ja)
\n – User (WordPress.org username): @gripspace
Thank you very much!
\n\n #ja\n\n\n#editor-requests
", "id": 16780501, "pubDate": "Thu, 23 Jul 2026 04:58:17 GMT", "whenReceived": "Thu, 23 Jul 2026 05:06:35 GMT", "whenUpdated": "Thu, 23 Jul 2026 06:46:34 GMT", "likes": [], "metadata": { "wpPostId": 68814, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68805", "title": "PTE Request for Soccr I…", "link": "https://make.wordpress.org/polyglots/2026/07/22/pte-request-for-soccr-i/", "description": "PTE Request for Soccr
\nI am the plugin author of Soccr and would like to become PTE for the plugin so I can approve the German (de_DE) translations. My wordpress.org username: rockschtar. Translation project: https://translate.wordpress.org/projects/wp-plugins/soccr/
#editor-requests
", "id": 16775649, "pubDate": "Wed, 22 Jul 2026 22:11:02 GMT", "whenReceived": "Wed, 22 Jul 2026 22:25:10 GMT", "whenUpdated": "Thu, 23 Jul 2026 00:05:45 GMT", "likes": [], "metadata": { "wpPostId": 68805, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68791", "title": "PTE Request for Zhekich Feed Generator for Dzen", "link": "https://make.wordpress.org/polyglots/2026/07/22/pte-request-for-zhekich-feed-generator-for-dzen/", "description": "I am the plugin author for Zhekich Feed Generator for Dzen. I’d like to be able to approve translations for my own plugin. Please add the following WordPress.org user as a translation editor for the respective locale:
\n\nhttps://wordpress.org/plugins/zhekich-feed-generator-for-dzen/\n\n\n\n #ru_RU – @e-krukov (@tobifjellner)\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16775650, "pubDate": "Wed, 22 Jul 2026 21:04:27 GMT", "whenReceived": "Wed, 22 Jul 2026 22:25:10 GMT", "whenUpdated": "Thu, 23 Jul 2026 22:03:53 GMT", "likes": [], "metadata": { "wpPostId": 68791, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/test/feed/", "whenReceived": "Wed, 22 Jul 2026 19:42:10 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/2026/07/22/xpost-client-side-media-processing-in-wordpress-7-1/", "title": "X-post: Client-Side Media Processing in WordPress 7.1", "link": "https://make.wordpress.org/test/2026/07/22/xpost-client-side-media-processing-in-wordpress-7-1/", "description": "X-comment from +make.wordpress.org/core: Comment on Client-Side Media Processing in WordPress 7.1
", "id": 16772308, "pubDate": "Wed, 22 Jul 2026 17:44:26 GMT", "whenReceived": "Wed, 22 Jul 2026 19:42:10 GMT", "whenUpdated": "Wed, 22 Jul 2026 19:42:10 GMT", "likes": [], "metadata": { "wpPostId": 12524, "wpSiteId": 255400204 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Wed, 22 Jul 2026 18:17:37 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124446", "title": "Client-Side Media Processing in WordPress 7.1", "link": "https://make.wordpress.org/core/2026/07/22/client-side-media-processing-in-wordpress-7-1/", "description": "WordPress 7.1 ships client-side media processing – a capability that handles image compression, resizing, format conversion, rotation, and thumbnail generation directly in the user’s browser using WebAssembly, rather than on the server. The feature is enabled by default in supporting browsers.
\n\n\n\nThis post outlines what’s changing, how it works, and what plugin and theme developers need to know.
\n\n\n\nWhat is client-side media processing?\n\n\n\nTraditionally, when a user uploads an image in the block editor, the file is sent to the server where PHP (using GD or Imagick) generates thumbnails (various image sizes for the front end), applies format conversions, handles EXIF rotation, and scales large images. This approach is limited by PHP memory constraints, server CPU availability, and the capabilities of the server’s installed image library.
\n\n\n\nClient-side media processing moves this work to the browser. Images are processed using wasm-vips, a WebAssembly compilation of the high-performance libvips image processing library. The processed images – including all thumbnails – are then uploaded to the server, which stores them. After all client-side operations complete, a finalize step applies the wp_generate_attachment_metadata filter with context 'update' so plugins see the full sub-sizes metadata. This mirrors how the server already handlesimage uploads, where sub-sizes trigger the same 'update' pass.
\n\n\n\n\n\n\n\nKey benefits\n\n\n\n\nConsistent, high-quality output with modern image support. All users get the same libvips powered processing regardless of whether the server has GD or Imagick, and regardless of which version is installed.\n\n\n\nFaster downloads for visitors. libvips produces better-compressed output than GD or Imagick (JPEGs are reduced ~15% with MozJPEG like encoding), so the generated images served to site visitors are smaller and load faster.\n\n\n\nNo more PHP memory limit failures. Large image processing that would exceed PHP’s memory limit now succeeds because it runs in the browser’s memory space.\n\n\n\nReduced server load. Image processing is offloaded to the user’s device, freeing server CPU and memory for other tasks.\n\n\n\niPhone photos just work. HEIC images can be decoded in the browser and converted to JPEG before upload, even on hosts without server-side HEIC support. Note: HEIC decode relies on platform codecs and is supported in Chromium browsers (Chrome, Edge, Brave) on macOS and on Windows with HEVC support, and in Safari on macOS. The full WASM pipeline (everything beyond HEIC) is Chromium-only – see Browser compatibility and fallback below.\n\n\n\nAVIF without server-side AVIF support. Hosts whose PHP image editor doesn’t support AVIF can still accept AVIF uploads when client-side processing is active. The MIME-type check is bypassed for client-decoded uploads – see the security FAQ below for details.\n\n\n\nAnimated GIFs become efficient video. Opaque animated GIFs can be converted in the browser to a companion MP4/WebM video that plays exactly like the original GIF, dramatically cutting the bytes visitors download, with no loss of the autoplay-loop GIF feel.\n\n\n\nMore resilient uploads. Sub-size uploads are independent requests, so a network hiccup mid-upload doesn’t lose the entire batch. Failed requests are retried automatically with exponential backoff, so transient network errors recover without user intervention. Uploads are paused if you go offline and resume when you come back online.\n\n\n\n\nWhat’s included\n\n\n\n\nBrowser-based image processing – Compression, resizing, cropping, format conversion (JPEG, PNG, WebP, AVIF, GIF), EXIF rotation, and progressive/interlaced encoding via WebAssembly in a Web Worker.\n\n\n\nThumbnail generation in the browser – All registered image sub-sizes are generated client-side and uploaded individually via a new sideload REST API endpoint. Sizes that share dimensions with built-in sizes (e.g. Twenty Eleven’s large matches medium_large) are deduplicated to a single physical file registered under all matching size names.\n\n\n\nHEIC/HEIF support – iPhone photos (image/heic, image/heif) are decoded in the browser and uploaded as web-ready JPEG. The original HEIC is kept as a companion file (source_image) and removed when the attachment is deleted.\n\n\n\nAVIF end-to-end uploads – AVIF can be decoded client-side, no longer requiring server-side AVIF support. High-bit-depth AVIF sources (10- or 12-bit, common for HDR photos) keep their bit depth in generated sub-sizes.\n\n\n\nGain Map HDR support – UltraHDR JPEGs embed a gain map alongside a standard SDR base image: a new, backwards-compatible way of adding HDR data to SDR images that is supported by Google (UltraHDR), Apple (Adaptive HDR), and Adobe (Camera Raw, Lightroom, and Photoshop). These files are detected on upload and preserved end-to-end: the original uploads unmodified, and every generated sub-size keeps its gain map, so thumbnails stay HDR. Format conversion via image_editor_output_format is intentionally skipped for these files, since converting to a different codec would strip the gain map.\n\n\n\nAutomatic format conversion – The existing image_editor_output_format filter is respected client-side, enabling automatic conversion (e.g., JPEG to WebP) during processing.\n\n\n\nAnimated GIF to video conversion – Opaque animated GIFs are converted in the browser to an MP4 (or WebM) using the native WebCodecs APIs and the mediabunny library. The GIF stays a single image/gif attachment; the converted video and a first-frame poster are sideloaded as companion files (media_details.animated_video / animated_video_poster). In the editor the block is optionally switched to a “GIF” variation of the Video block that autoplays, loops, and is muted – playing just like the original GIF – and the front end renders a native <video>. The swap is fully reversible via the block transform menu, transparent GIFs are left as images, and browsers without WebCodecs video encoding (e.g. Firefox) upload the original GIF unchanged.\n\n\n\nA cross-origin-isolated editor – To run the WASM pipeline, the editor needs SharedArrayBuffer, which browsers only expose to cross-origin-isolated documents. WordPress enables this with Document-Isolation-Policy: isolate-and-credentialless on block editor screens for Chromium 137+. Beyond media processing, this means SharedArrayBuffer and high-resolution timers are now available to any code running in the editor, so plugins can build their own multithreaded or WASM-backed features there. Because DIP is per-document, it provides this isolation without imposing the page-wide constraints of COOP/COEP. See Cross-origin isolation impact below for what extenders should watch for.\n\n\n\nServer-side hook compatibility – wp_generate_attachment_metadata fires the same way as for a server-side upload: once with context 'create' during the initial upload and again with 'update' after POST /wp/v2/media/{id}/finalize runs. Plugins that hook into it (watermarking, CDN sync, etc.) continue to work, the same way they already handle the deferred-subsize pass on big-image uploads.\n\n\n\nUpload progress feedback – A snackbar in the editor tracks batch upload progress, with a spinner while uploads run and a brief checkmark on completion. It works on both the client-side and server-side upload paths, and announces start and completion via wp.a11y.speak() for screen reader users.\n\n\n\nSmart fallback – Browsers that don’t support the required features automatically fall back to server-side processing with no user-facing change.\n\n\n\nImage quality filters honored – The standard wp_editor_set_quality and jpeg_quality filters flow through to client-side sub-size generation via a size-aware image_quality field in the upload response, so existing quality-tuning code works unchanged.\n\n\n\nServer-side import of external images – The Image block’s “Upload to Media Library” action and the pre-publish “External media” panel now send the image URL to the server, which downloads and sideloads it – avoiding browser CORS failures entirely (the old client-side fetch also could not work in the cross-origin-isolated editor).\n\n\n\n\nTechnical overview\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n@wordpress/upload-media – Manages the upload queue, concurrency (max 5 uploads, max 2 image processing operations), and orchestrates the pipeline.\n\n\n\n@wordpress/vips – Wraps wasm-vips in a Web Worker for non-blocking image processing. The WASM bundle is loaded lazily on first use and bundles vips.wasm and vips-heif.wasm (the latter is needed for AVIF decoding).\n\n\n\n@wordpress/media-utils – Handles HTTP transport to the WordPress REST API.\n\n\n\n@wordpress/video-conversion – Wraps the mediabunny library in a Web Worker (mirroring the @wordpress/vips pattern) to convert animated GIFs to MP4/WebM off the main thread, gated on WebCodecs ImageDecoder/VideoEncoder availability and run with a concurrency limit of 1.\n\n\n\n\nOn the PHP side:
\n\n\n\n\nwp_is_client_side_media_processing_enabled() – Feature gate, filterable via wp_client_side_media_processing_enabled.\n\n\n\nCross-origin isolation – wp_start_cross_origin_isolation_output_buffer() sends Document-Isolation-Policy on load-post.php, load-post-new.php, load-site-editor.php, and load-widgets.php for Chromium 137+. Only active when client side media is enabled.\n\n\n\nREST API extensions – New generate_sub_sizes and convert_format parameters, sideload endpoint (POST /wp/v2/media/{id}/sideload), finalize endpoint (POST /wp/v2/media/{id}/finalize), replace_file flag for HEIC companion uploads, and new response fields (exif_orientation, missing_image_sizes, filename, filesize).\n\n\n\n\nFor the full architecture deep-dive, see the client-side media processing architecture documentation.
\n\n\n\nWhat plugin developers need to know\n\n\n\nDisabling client-side processing\n\n\n\nIf your plugin needs to disable client-side media processing, use the wp_client_side_media_processing_enabled filter:
\n\n\n\nadd_filter( 'wp_client_side_media_processing_enabled', '__return_false' );\n\n\n\nServer-side hooks still fire\n\n\n\nA common concern: if client-side processing bypasses server-side image generation, do plugins that hook into wp_generate_attachment_metadata stop working? No – the filter fires the same way it does during a server-side upload, just with the work shifted around. WordPress fires it once with context 'create' during the initial upload (before the sub-sizes are created), and again with 'update' after the finalize endpoint runs (once all client-side sub-size sideloads are complete). Plugins for watermarking, CDN sync, custom metadata processing, and similar use cases continue to work without modification – write them idempotently so they handle both passes correctly. This double-fire pattern matches how WordPress already handles big-image uploads on the server, where sub-size generation is deferred and triggers a second 'update' pass.
\n\n\n\nIf finalize fails, the error is logged but the upload still succeeds – the call is best-effort so a plugin failure can’t block the user’s upload.
\n\n\n\nExisting filters still work\n\n\n\nClient-side processing reads settings from the server and respects:
\n\n\n\n\nbig_image_size_threshold – Maximum image dimension before scaling.\n\n\n\nimage_editor_output_format – Automatic format conversion.\n\n\n\nimage_save_progressive – Progressive/interlaced encoding.\n\n\n\nwp_image_maybe_exif_rotate – EXIF rotation.\n\n\n\nwp_editor_set_quality (and jpeg_quality for JPEG output) – Encode quality, resolved per registered size.\n\n\n\n\nThere is no client_side_supported_mime_types filter; the supported set (image/jpeg, image/png, image/gif, image/webp, image/avif) is fixed at CLIENT_SIDE_SUPPORTED_MIME_TYPES.
\n\n\n\n\n\n\n\nControlling image quality\n\n\n\nClient-side encoding honors the same PHP filters that control server-side quality: wp_editor_set_quality and, for JPEG output, jpeg_quality. The server resolves the filters per registered size and reports the result in the upload response’s size-aware image_quality field, which the client applies during sub-size resize and transcode. The same code that tunes server-side quality works unchanged:
\n\n\n\n/*\n * Size-aware: drop JPEG thumbnails (300px wide or less) to quality 60,\n * leave larger sizes untouched.\n */\nadd_filter(\n\t'wp_editor_set_quality',\n\tfunction ( $quality, $mime_type, $size ) {\n\t\tif ( 'image/jpeg' === $mime_type && isset( $size['width'] ) && $size['width'] <= 300 ) {\n\t\t\treturn 60;\n\t\t}\n\t\treturn $quality;\n\t},\n\t10,\n\t3\n);\n\n\n\n\nWhen the server doesn’t report the field, the client falls back to a default of 0.82.
\n\n\n\nCross-origin isolation impact\n\n\n\nWhen client-side media is active, WordPress sends Document-Isolation-Policy: isolate-and-credentialless on block editor screens for Chromium 137+. Since DIP is per-document, it doesn’t impose the page-wide constraints of COEP/COOP. Notable behavior:
\n\n\n\n\nExternal scripts loaded across origins automatically get a crossorigin=\"anonymous\" attribute via the server-side wp_add_crossorigin_attributes() output buffer and a client-side MutationObserver. <img> is excluded so external image previews aren’t affected.\n\n\n\nDIP is skipped on admin pages with an action other than edit, which keeps third-party page builders that rely on same-origin iframe access functional.\n\n\n\nExternal images are imported server-side. “Upload to Media Library” and the pre-publish “External media” panel POST the image URL to the media endpoint (a new url parameter) and the server downloads and sideloads it. Plugins importing remote media should do the same rather than fetch()ing image bytes in the browser – a cross-origin fetch is subject to CORS and fails in a credentialless isolated document.\n\n\n\n\nContent Security Policy (CSP)\n\n\n\nIf your plugin sets a Content Security Policy, ensure the worker-src directive includes blob::
\n\n\n\nContent-Security-Policy: worker-src 'self' blob:;\n\n\n\nWithout this, the WASM processing worker cannot be created and processing falls back to server-side.
\n\n\n\nServer specific hooks don’t fire\n\n\n\nBecause a server side editor is not used, wp_image_editors, image_memory_limit and image_make_intermediate_size never fire. A complete accounting of media hooks before and after this change is available in the handbook.
\n\n\n\n\n\n\n\nWhat theme developers need to know\n\n\n\nClient-side media processing is transparent to themes. Existing filters (big_image_size_threshold, image_editor_output_format, etc.) continue to work without modification. Image sizes registered via add_image_size() are automatically generated client-side, and sizes that share dimensions with built-in sizes are deduplicated to a single physical file.
\n\n\n\nBrowser compatibility and fallback\n\n\n\nClient-side processing depends on Document-Isolation-Policy to enable SharedArrayBuffer, which is currently only available in Chromium-based browsers.
\n\n\n\nBrowserMinimum VersionStatusChrome137+Full support via Document-Isolation-PolicyEdge137+Full support via Document-Isolation-PolicyFirefox–*Not supported (no Document-Isolation-Policy) – falls back to server-sideSafari–*Not supported (no Document-Isolation-Policy) – falls back to server-side. In-browser HEIC decode still works, since it does not require Document-Isolation-Policy.\n\n\n\nChrome and Edge have supported Document-Isolation-Policy since version 137 (released in mid-2025). As of this post’s publication, current stable Chrome and Edge are well past that, so the overwhelming majority of Chromium users already meet the requirement. Chrome on Android supports the feature from version 146. Document-Isolation-Policy is not yet tracked on caniuse; the most reliable place to check current and future browser support is the Chrome Platform Status entry.
\n\n\n\n\nOn unsupported browsers WordPress falls back to server-side processing automatically. Users see no difference in behavior. A plugin is available (wordpress.org version coming soon, available now on GitHub) to enable the client-side media feature in Firefox/Safari using COEP/COOP headers. These are not used by default because they create compatibility issues with embeds and other third party resources.\n\n\n\n\nFeature detection and limitations\n\n\n\nBeyond browser support, the client checks several runtime conditions before activating the WASM pipeline. Failing any check causes a transparent fallback to server-side processing – there is no user-facing change.
\n\n\n\nCheckThresholdWhyDevice memory> 2 GBWASM image processing can OOM on very low-memory devices.CPU cores≥ 2WASM image processing benefits from at least one core for the worker plus one for the UI thread.Networknot 2g/slow-2g, no Save-Data headerThe ~13 MB worker download is gated to faster connections; 3g is allowed.CSP blob: workersmust succeedThe worker is created from a blob URL; strict worker-src policies block it.\n\n\n\nFrequently asked questions\n\n\n\nIsn’t this just a bandwidth optimization?\n\n\n\nNot exactly. The client uploads the original plus every sub-size, so total bytes over the wire actually go up during uploads compared to the server-side path (which receives only the original). Bandwidth is saved when serving the images since encoding is better and modern images are always supported. For uploads the real win is server CPU and memory relief: hosts no longer pay the GD/Imagick cost of generating sub-sizes on upload, which is one of the most common causes of PHP timeouts and memory-limit failures on shared hosting. See “Key benefits” above.
\n\n\n\nDoesn’t the “never trust the client” rule apply here?\n\n\n\nClient-side processing is a performance optimization, not a trust boundary. The server still validates every uploaded file – MIME type, dimensions, capability checks, sanitization – and runs the same wp_generate_attachment_metadata filter chain. If the browser can’t or won’t process the file, WordPress falls back to server-side processing transparently.
\n\n\n\n\n\n\n\nWhat happens if the browser can’t process the image?\n\n\n\nServer-side processing runs as before. The fallback is automatic and transparent to the user – no UI change, no error. The exact gating (browser features, device memory, CPU cores, network class, CSP) is described in “Feature detection and limitations” above.
\n\n\n\nWill my plugin’s wp_generate_attachment_metadata hooks still run?\n\n\n\nYes. The filter fires the same way as during a server-side upload: once with context 'create' during the initial upload, and again with 'update' after the finalize endpoint runs (once all client-side sub-size sideloads complete). Watermarking, CDN sync, custom metadata processing, and similar plugins should keep working without modification, but should be checked to make sure they handle both passes. See “Server-side hooks still fire” above.
\n\n\n\nDoes this change the format my users upload?\n\n\n\nOnly if image_editor_output_format says so – the existing filter is honored client-side. There are two new behaviors. HEIC inputs are converted to JPEG before upload and the original is kept as a companion file. And opaque animated GIFs are converted to a companion video (see below). AVIF inputs upload as AVIF, even on hosts whose server-side image editor lacks AVIF support. HDR images using gain maps upload unmodified, so their HDR gain maps survive – including in every generated sub-size.
\n\n\n\nWhat happens to animated GIFs?\n\n\n\nOpaque animated GIFs are converted in the browser to a companion MP4/WebM video, and the editor offers a transform to convert the block to a “GIF” variation of the Video block that autoplays, loops, and is muted – so it behaves exactly like the original GIF while downloading far less data. Important details for extenders:
\n\n\n\n\nThe attachment is still a GIF. It stays a single image/gif attachment in the media library; the video and a first-frame poster are companion files recorded in media_details.animated_video / animated_video_poster, removed automatically when the GIF is deleted.\n\n\n\nThe front end is a real video block. The swap is a block switch in the editor, not a render-time filter, so the published markup is a native <video autoplay loop muted playsinline poster> – nothing GIF-specific to filter.\n\n\n\nIt’s reversible, transparent GIFs are left as images, and only standalone Image blocks are converted (GIFs inside a Gallery, Media & Text, or Cover are untouched).\n\n\n\nBrowser support. Conversion needs WebCodecs video encoding (ImageDecoder + VideoEncoder). Browsers without it – notably Firefox – upload the original GIF unchanged, with no error. There is no separate opt-out filter; disabling client-side media processing also disables GIF conversion.\n\n\n\n\nWhy aren’t Firefox and Safari supported?\n\n\n\nThey don’t ship Document-Isolation-Policy, which is what enables SharedArrayBuffer (required for the WASM pipeline). Users on those browsers get the existing server-side path – no regression. The HEIC canvas fallback still works in Safari for HEIC inputs. A plugin is available (wordpress.org version coming soon, available now on GitHub) to enable the client-side media feature in Firefox/Safari using COEP/COOP headers.
\n\n\n\nTesting and feedback\n\n\n\nWe encourage plugin and theme developers to test client-side media processing with their products. In particular:
\n\n\n\n\nVerify that uploads work with your plugin’s custom image sizes and format settings – including sizes that share dimensions with built-in sizes.\n\n\n\nTest HEIC uploads if you target sites with iPhone-using authors.\n\n\n\nTest AVIF uploads on hosts whose image editor lacks AVIF support.\n\n\n\nTest gain-mapped HDR photos (UltraHDR JPEGs) if your plugin transforms images – sub-sizes remain UltraHDR JPEGs with their gain maps, and format conversion is intentionally skipped for them.\n\n\n\nTest animated GIF uploads – confirm the block converts to a looping muted video, the round-trip back to a GIF works, and any plugin that post-processes attachments handles the companion video/poster correctly.\n\n\n\nCheck that cross-origin isolation doesn’t break any external resources or embeds your plugin loads in the editor.\n\n\n\nTest with wp_client_side_media_processing_enabled returning false to ensure your fallback path works.\n\n\n\n\nPlease report any issues on the Gutenberg GitHub repository. Related tracking issues:
\n\n\n\n\nClient-side media processing iteration for WordPress 7.1 (#76756)\n\n\n\nDocumentation tracking issue (#75111)\n\n\n\n\nFor detailed developer documentation, see:
\n\n\n\n\nArchitecture explanation\n\n\n\nDeveloper how-to guide\n\n\n\nEditor filters reference\n\n\n\n\nProps to @swissspidy, @andrewserong, and the many other contributors who worked on this feature. Thanks to @wildworks and @andrewserong for reviewing this post.
\n#7-1, #dev-notes, #dev-notes-7-1
", "id": 16770316, "pubDate": "Wed, 22 Jul 2026 17:24:03 GMT", "whenReceived": "Wed, 22 Jul 2026 18:17:37 GMT", "whenUpdated": "Wed, 22 Jul 2026 18:17:37 GMT", "likes": [], "metadata": { "wpPostId": 124446, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Wed, 22 Jul 2026 17:24:29 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68800", "title": "Request for Translation Editor Access for Chinese Locales", "link": "https://make.wordpress.org/polyglots/2026/07/22/request-for-translation-editor-access-for-chinese-locales/", "description": "Hello Polyglots Team, We are a WordPress plugin development team. Our WordPress.org account is tearsnow.
\nWe have already submitted multiple plugins and have requested translation permissions through https://make.wordpress.org/polyglots/. However, these requests have not been processed yet.
\nSince we will continue releasing more new plugins in the future, we would like to ask whether it is possible to upgrade our translation permissions so that we can automatically have translation access for all of our plugins.
\nThe main translation languages we contribute to are Chinese, including:
\n\n #zh_CN (Chinese – China) (@tobifjellner)\n\n #zh_HK (Chinese – Hong Kong)\n\n #zh_SG (Chinese – Singapore)\n\n #zh_TW (Chinese – Taiwan)\n\n\nOur currently published plugins include:
\n\nhttps://wordpress.org/plugins/tearsnow-mobile-theme-switcher/\n\nhttps://wordpress.org/plugins/tearsnow-site-icon-cleaner/\n\nhttps://wordpress.org/plugins/tearsnow-update-lock-cleaner/\n\nhttps://wordpress.org/plugins/tearsnow-wfw-commentapi-cleaner/\n\n\nWe would like to contribute more actively to WordPress Chinese translations. Based on our plugin development and translation contributions, we would appreciate your guidance on obtaining the appropriate translation permissions, including PTE or GTE if applicable.
\nThank you very much for your time and support.
\n#editor-requests
", "id": 16768964, "pubDate": "Wed, 22 Jul 2026 17:16:19 GMT", "whenReceived": "Wed, 22 Jul 2026 17:24:29 GMT", "whenUpdated": "Thu, 23 Jul 2026 22:03:53 GMT", "likes": [], "metadata": { "wpPostId": 68800, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://wordpress.org/news/podcast/feed/", "whenReceived": "Wed, 22 Jul 2026 16:54:30 GMT", "items": [ { "feedUrl": "https://wordpress.org/news/podcast/feed/", "guid": "https://wordpress.org/news/?p=21177", "title": "WordPress 7.1 Beta 3", "link": "https://wordpress.org/news/2026/07/wordpress-7-1-beta-3/", "description": "WordPress 7.1 Beta 3 is ready for download and testing!
\n\n\n\nThis beta release is intended for testing and development only. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, use a test environment or local site to explore the new features.
\n\n\n\nHow to Test WordPress 7.1 Beta 3\n\n\n\nYou can test WordPress 7.1 Beta 3 in any of the following ways:
\n\n\n\nWordPress Beta Tester PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. Select the “Bleeding edge” channel and “Beta/RC Only” stream.Direct DownloadDownload the Beta 3 version (zip) and install it on a WordPress website.Command Line (WP-CLI)Use this WP-CLI command: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\nFind out what’s new in WordPress 7.1: Read the Beta 1 announcement for details and highlights.
\n\n\n\nHow important is your testing?\n\n\n\nTesting for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute – whether or not you have experience. Details on what to test in WordPress 7.1 are available here.
\n\n\n\nIf you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bug report, you can do so via WordPress Trac. You can also check your issue against this list of known bugs.
\n\n\n\nCurious about testing releases in general and how to get started? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
\n\n\n\nWhat’s in WordPress 7.1 Beta 3?\n\n\n\nFor technical details on the more than 71 issues addressed since Beta 1, see the following links:
\n\n\n\n\nClosed 7.1 WordPress Core Trac tickets since July 15, 2026\n\n\n\n7.1 Gutenberg commits since July 15, 2026\n\n\n\n\nNote: Beta 2 was released on July 17, 2026, as part of the WordPress 7.0.2 release and includes important security fixes.
\n\n\n\nBeta 3 introduces two improvements to styling.\n\n\n\nApplying local style changes globally is no longer an all-or-nothing action. The Apply globally option in the block inspector now opens a quick review step, allowing you to choose which modified styles to apply globally while keeping the rest as local overrides.
\n\n\n\nOther notable fixes include improvements to media uploads: long animated GIF uploads no longer hang, images rotated using EXIF metadata are processed correctly, and uploading a single HEIC image in Safari no longer creates two entries.
\n\n\n\nThe editor also includes additional fixes for Notes, responsive styling, and custom CSS. For developers, WordPress Coding Standards has been updated to version 3.4.0.
\n\n\n\nUnicode email address support will not be included in WordPress 7.1. The work will continue in a community plugin, allowing broader testing of compatibility, security, and data-handling considerations.
\n\n\n\nA Beta 3 haiku\n\n\n\nFresh bugs surface now,
click by click, we chase them down—
codebase grows steady.
Props to @krupajnanda, @annezazu,
@wildworks, @amykamala for proofreading and review.
Request for Ticketleo Events — I’m the plugin author. Please add my wp.org user Hayloft as PTE for
\n— de_DE
\n\n #de_CH \n\n #de_AT \n\n\nPlugin: https://wordpress.org/plugins/ticketleo-events
\n#editor-requests
", "id": 16766324, "pubDate": "Wed, 22 Jul 2026 14:12:37 GMT", "whenReceived": "Wed, 22 Jul 2026 15:44:19 GMT", "whenUpdated": "Thu, 23 Jul 2026 00:05:45 GMT", "likes": [], "metadata": { "wpPostId": 68782, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Wed, 22 Jul 2026 14:57:16 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124627", "title": "What’s new in Gutenberg 23.6? (July 22, 2026)", "link": "https://make.wordpress.org/core/2026/07/22/whats-new-in-gutenberg-23-6-july-22-2026/", "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\nWhat’s New In
Gutenberg 23.6?
Gutenberg 23.6 has been released and is available for download!
\n\n\n\nThis release adds cropping controls to the Media editor, brings it to the Cover block, and extends responsive style states with aspect-ratio, flex-alignment, and text-shadow controls. Other changes include a minimum WordPress version bump to 6.9, Icon block transforms, and real-time collaboration improvements.
\n\n\n\n\nTry Gutenberg 23.6\n\n\n\n\nTable of contents
\n\n\n\n\nThe Playlist and Tabs blocks are now stable\n\n\n\nEnhancements to Notes\n\n\n\nA dynamic mode for the Gallery block\n\n\n\nIcon collections and a custom icon registration API\n\n\n\nOther Notable Highlights\n\n\n\n\nThe Playlist and Tabs blocks are now stable\n\n\n\nTwo blocks that have lived behind the block experiments flag are now part of the default block library, and are available to everyone without enabling an experiment.
\n\n\n\nThe Playlist block plays a list of audio tracks with track metadata, artwork, and the waveform and track length options. The tracklist itself is configurable: you can set the play order, and toggle the artwork, artist names, track numbers, and track length individually to suit the design of your page. For more details on where the block is headed, see the iteration issue for WordPress 7.1.
\n\n\n\n\n\n\n\nThe Tabs block family lets you organize content into tabbed sections, following the best practices set out in the tabs pattern from the W3C ARIA Authoring Practices Guide. Each panel accepts any blocks you like, and the tab buttons come with their own color, typography, border, and spacing controls, so the navigation can be styled to match your theme. For the details, see the tracking issue that drove the block toward stabilization.
\n\n\n\n\n\n\n\nEnhancements to Notes\n\n\n\nNotes continues to move toward a full commenting workflow, with two significant additions in this release.
\n\n\n\nInline notes let you attach a note to a specific text selection rather than to a whole block. Select part of a paragraph, add a note, and the highlight stays anchored to that text as you keep editing around it. A single block can carry multiple inline notes, sorted by the order they appear in the block, and none of the highlighting shows up in the published post. (#78218)
\n\n\n\n\n\n\n\n@mention autocomplete makes it possible to direct a note at a specific person. Typing @ inside a note opens an inline, keyboard-navigable list of users; selecting one inserts a mention chip that links to the user’s author page and carries the mentioned user’s ID. (#79604)
\n\n\n\n\n\n\n\nA dynamic mode for the Gallery block\n\n\n\nThe Gallery block can now display media dynamically instead of only the images you pick by hand. The new Dynamic Gallery variation shows all media currently attached to the post, in both the editor and on the frontend.
\n\n\n\nRather than being a separate block, it is a variation of the Gallery block, so you can move between the two without losing your settings: start a Dynamic Gallery from the block placeholder, and switch it to a regular gallery whenever you want to edit the list of images by hand. (#78796)
\n\n\n\n\n\n\n\nIcon collections and a custom icon registration API\n\n\n\nIcons can now be registered by plugins and themes, and are organized into collections.
\n\n\n\nAlongside the default core icons, the API has been extended and utility functions added so that you can publish an icon set of your own as a collection. Icons are shared data for the whole site, available in both the editor and on the frontend. (#77260)
\n\n\n\nThe icon picker has been updated to match. A new Collections tab lists collections in the sidebar — like the Pattern Explorer — so you can browse and search within one set rather than scrolling a single combined list. The collection containing the currently selected icon is opened by default, and icons load asynchronously to keep the UI responsive when a large number of them are registered. (79681) (#78332)
\n\n\n\n\n\n\n\nOther Notable Highlights\n\n\n\n\nCustomizable viewport sizes. Tablet and mobile preview widths can now be set in theme.json, so device previews can match your theme’s actual breakpoints. (#79104)\n\n\n\nThe admin bar is shown by default in both the Post Editor and the Site Editor. (#79197)\n\n\n\nApply Globally is now selective. When applying a block’s styles globally, you can choose which style properties to apply instead of applying all of them. (#79839)\n\n\n\nNew block support for the Custom HTML block. innerContent support for static inner blocks has been added and adopted by the HTML block. (#79115)\n\n\n\nBackground gradient support has been added to the Accordion, Post Content, Pullquote, Quote, and Verse blocks. (#79840, #79842, #79841, #79843, #79391)\n\n\n\nThe Post Editor is now always iframed, aligning its rendering with the Site Editor. (#74042)\n\n\n\n\nChangelog\n\n\n\nFeatures\n\n\n\nPost Editor\n\n\n\n\nAllow setting viewport tablet and mobile values in theme.json. (79104)\n\n\n\nExperimental: Expand DataForm inspector to patterns. (79452)\n\n\n\nNotes: Add @mention autocomplete. (79604)\n\n\n\nNotes: Inline (partial-text) notes via hybrid marker + strip-on-render approach. (78218)\n\n\n\nShow the admin bar in the Post and Site Editor by default. (79197)\n\n\n\n\nBlock Editor\n\n\n\n\nShare block-bindings context assembly between call sites. (79855)\n\n\n\n\nData Layer\n\n\n\n\nBlocks: Add innerContent support for static inner blocks, adopt it in the HTML block. (79115)\n\n\n\n\nComponents\n\n\n\n\nDataViews: Add a richtext control backed by a private RichTextControl shell in wordpress/components. (78471)\n\n\n\n\nBlock Library\n\n\n\n\nIcons: Add PHP method(s) for rendering inline SVG icons from the registry. (78332)\n\n\n\n\nEnhancements\n\n\n\n\nCSS: Follow-up fixes to split_selector_list(). (79723)\n\n\n\nDocument widget relevance, help. (80007)\n\n\n\nExpose widget category through the build pipeline and REST API. (79638)\n\n\n\nOmnibar: Move the ‘site icon in admin bar’ feature from experiment to 7.1 compat. (79807)\n\n\n\nScripts: Make ‘test-e2e’ run Playwright and remove Puppeteer. (80058)\n\n\n\nSite Editor v2 experiment: Hide admin bar in distraction-free mode. (79937)\n\n\n\nWidget Dashboard: Remove layout-settings editing. (79903)\n\n\n\nWidget Dashboard: Reserve paint space for tile focus rings. (79990)\n\n\n\nWidget Primitives: Add WidgetAttributeField for typed attribute schemas. (79544)\n\n\n\nWidgets: Add a declarative help metadata field, surfaced as a header infotip. (79830)\n\n\n\nWidgets: Add attribute relevance and inline editing in the tile toolbar. (79735)\n\n\n\nWidgets: Translate title, description, and keywords server-side. (79701)\n\n\n\n\nBlock Library\n\n\n\n\nAccordion block: Add background gradient support. (79840)\n\n\n\nAdd ariaLabel supports for Tab List Block. (79948)\n\n\n\nAdd icon state classes to Accordion block. (74257)\n\n\n\nAdd layout and block spacing support to Latest Posts block. (77989)\n\n\n\nAdd option to exclude current post from query block. (64916)\n\n\n\nAnimated GIF to video conversion (via mediabunny). (78410)\n\n\n\nClassic block: Remove migration notice and restore inserter availability. (79894)\n\n\n\nCover: Allow restricting video embed providers. (80092)\n\n\n\nFile Block: Deduplicate the file to audio/video/image transforms. (80158)\n\n\n\nGIF to video conversion: Make it opt-in. Switching via block transforms. (80072)\n\n\n\nGeneralize playlist block wording. (80071)\n\n\n\nIcons: Filter the icon library picker by collection. (79681)\n\n\n\nMake the Playlist blocks stable. (80203)\n\n\n\nMove styles into specific waveform styles dropdown area. (80060)\n\n\n\nPlaylist Block: Add artwork to play button. (79938)\n\n\n\nPlaylist Block: Add waveform and waveform background color options. (80065)\n\n\n\nPlaylist: Seek value text localization. (79834)\n\n\n\nPlaylist: Update waveform player dependency. (79825)\n\n\n\nPost Content block: Add background gradient support. (79842)\n\n\n\nPullquote block: Add background gradient support. (79841)\n\n\n\nQuote block: Add background gradient support. (79843)\n\n\n\nResponsive editing: Hide block toolbar slots when editing a responsive style state. (79998)\n\n\n\nSecond click or space/enter keypress on playing track pauses it. (80066)\n\n\n\nStabilize Tabs block. (80163)\n\n\n\nTabs: Combine and cleanup toolbar controls. (79537)\n\n\n\nTabs: RichText handlers for adding/removing tabs. (79583)\n\n\n\nTabs: Wrap tab list onto multiple lines by default. (80097)\n\n\n\nTerm Name: Migrate to textAlign block support. (76581)\n\n\n\nUse playlist icon for Playlist block. (80174)\n\n\n\nVerse block: Add background gradient support. (79391)\n\n\n\nIcon block: Show text and background color controls by default. (80251)\n\n\n\nTab List: Add toolbar buttons to reorder tabs. (80107)\n\n\n\n\nComponents\n\n\n\n\nBase Styles: Make Sass token fallbacks self-contained. (79651)\n\n\n\nBase Styles: Reapply wpds-var Sass helper. (79470)\n\n\n\nBorderBoxControl: Hard deprecate 40px default size. (79420)\n\n\n\nBorderControl: Hard deprecate 40px default size. (79418)\n\n\n\nButton: Align focus styles with design system. (78646)\n\n\n\nCheckbox: Add form primitive to wordpress/ui. (80039)\n\n\n\nComboboxControl: Hard deprecate 40px default size. (79636)\n\n\n\nComponents/Button: Don’t use box-shadow for secondary buttons. (79982)\n\n\n\nCustomSelectControl: Hard deprecate 40px default size. (79796)\n\n\n\nDS: Name font weight tokens by intent. (80093)\n\n\n\nFontSizePicker: Hard deprecate 40px default size. (79481)\n\n\n\nFormFileUpload: Hard deprecate 40px default size. (79655)\n\n\n\nFormTokenField: Hard deprecate 40px default size. (79720)\n\n\n\nInputControl: Hard deprecate 40px default size. (79962)\n\n\n\nNumberControl: Hard deprecate 40px default size. (79861)\n\n\n\nPackages: Update Ariakit to 0.4.32. (79860)\n\n\n\nRadio: Hard deprecate 40px default size. (79657)\n\n\n\nRangeControl: Hard deprecate 40px default size. (79590)\n\n\n\nSelectControl: Hard deprecate 40px default size. (79797)\n\n\n\nTheme: Remove elevation tokens. (80099)\n\n\n\nTheme: Restrict seed colors to opaque values. (79773)\n\n\n\nToggleGroupControl: Hard deprecate 40px default size. (79656)\n\n\n\nTreeSelect: Hard deprecate 40px default size. (79550)\n\n\n\nUI: Add LinkButton. (78944)\n\n\n\nUI: Add Skeleton component. (79671)\n\n\n\nUI: Update @base-ui/react to 1.6.0. (79408)\n\n\n\nUnitControl: Hard deprecate 40px default size. (79721)\n\n\n\ntheme: Validate npm publish surface. (79552)\n\n\n\nui/IconButton: Restore default tooltip delay. (79505)\n\n\n\nDataViews: Add shift-click range selection. (80046)\n\n\n\n\nPost Editor\n\n\n\n\nCommands: Add toggle for content-only pattern/template part editing. (78383)\n\n\n\nCommands: Suggest pattern editing toggle for selected patterns. (79566)\n\n\n\nEditor: Preload the view configuration form request for the DataForm inspector. (79910)\n\n\n\nMedia Inserter: Add pagination to core media inserter categories. (80038)\n\n\n\nMedia Inserter: Allow core media categories to subscribe to changes. (79921)\n\n\n\nNotes: Add a “Resolved” divider above resolved notes. (80019)\n\n\n\nNotes: Remove snackbar when resolving or reopening a note. (80017)\n\n\n\nPreview dropdown: Simplify viewport style state descriptions. (80146)\n\n\n\nRTC: Remove collaboration notification defaults filter. (79771)\n\n\n\nRename ‘Responsive editing’ toggle to ‘Responsive styles’. (80241)\n\n\n\nResponsive style states: Update responsive editing help text and avoid showing desktop badge. (79615)\n\n\n\nRestore responsive editing viewport dropdown copy changes. (79999)\n\n\n\nView config: Add better post type default form. (79625)\n\n\n\nVisual revisions: Label autosaves in the revisions timeline. (79950)\n\n\n\nVisual revisions: Make the autosave notice work with the visual revisions UI. (79947)\n\n\n\n[RTC] Add granular collaboration control. (79184)\n\n\n\nNotes: Remove “Add note” from the inline styles dropdown. (80531)\n\n\n\nDevice preview dropdown: Use active color for device icon when responsive styles are active. (80346)\n\n\n\nEditor: Allow selecting which block styles to apply globally. (79839)\n\n\n\nNotes: Add placeholders to the RichText fields. (80296)\n\n\n\nNotes: Increase contrast between avatar border colors. (80285)\n\n\n\n\nBlock Editor\n\n\n\n\nAdd contrast checking for viewport and pseudo states. (80223)\n\n\n\nBlock variations: Support innerContent for the Custom HTML block. (79659)\n\n\n\nBlock visibility: Add theme json opt out. (76559)\n\n\n\nClassic Block: Remove conversion from BlockInvalidWarning. (79500)\n\n\n\nColor popover: Move contrast warning notice to the bottom. (79512)\n\n\n\nEnable text alignment to be set by viewport state. (80037)\n\n\n\nFontAppearanceControl: Hard deprecate 40px default size. (79635)\n\n\n\nFontFamilyControl: Hard deprecate 40px default size. (79593)\n\n\n\nGrid: Add option to stretch columns with auto-fit for better layout flexibility. (79356)\n\n\n\nLetterSpacingControl: Hard deprecate 40px default size. (79533)\n\n\n\nLineHeightControl: Hard deprecate 40px default size. (79589)\n\n\n\nMedia Inserter: Guard attach, detach, and invalidate behind a ! isExternalResource check. (79978)\n\n\n\nPattern editing: Fade blocks outside the edited pattern in List View. (73997)\n\n\n\nResponsive editing: Add a Tooltip to the viewport / states badge. (80080)\n\n\n\nReflect inherited Global Styles values in block inspector controls. (80481)\n\n\n\n\nIcons\n\n\n\n\nAdd “sites” icon. (80094)\n\n\n\nAdd APIs for collection and icon registration. (77260)\n\n\n\nAdd Playlist icon. (80168)\n\n\n\nAdd repeat all icon. (79698)\n\n\n\nIcons Registry: Allow digits and underscores in icon slugs. (79623)\n\n\n\n\nDashboard\n\n\n\n\nWidget Dashboard: Anchor settings drawer to the right and toggle it from the gear. (79683)\n\n\n\nWidget Dashboard: Refactor tile header and toolbar chrome. (79639)\n\n\n\nWidget Primitives: Add a field type registry for widget attributes. (80148)\n\n\n\nWidget inserter: More accurate widget previews. (79517)\n\n\n\nWidgets: Auto-save inline attribute edits. (79808)\n\n\n\n\nPlugin\n\n\n\n\nExperiments: Move screen under Settings, drop top-level Gutenberg menu and Demo page. (79456)\n\n\n\nRelease: Harden all npm package release paths. (79905)\n\n\n\nRelease: Harden latest npm metadata publishing. (79904)\n\n\n\nRelease: Make npm publishing rerunnable. (80187)\n\n\n\nGlobal Styles: Limit the inherited value treatment to the Gutenberg plugin. (80555)\n\n\n\n\nSite Editor\n\n\n\n\nTheme: Fill semantic token state gaps. (79770)\n\n\n\nTheme: Make wordpress/theme ESM only. (80063)\n\n\n\n\nData Layer\n\n\n\n\nIcons: Add an icon collections REST endpoint and tighten name rules. (79686)\n\n\n\nPackages: Widen React peer dependency support to include React 19. (80024)\n\n\n\nClient Side Media: Honor image_strip_meta and image_max_bit_depth on the client upload path. (80218)\n\n\n\n\nGlobal Styles\n\n\n\n\nMigrate color palette tabs to wordpress/ui. (79281)\n\n\n\nShow skeleton placeholder while previews load. (79849)\n\n\n\n\nDataViews\n\n\n\n\nView Config: Add version handling. (79809)\n\n\n\n\nDesign Tools\n\n\n\n\nGlobal Styles: Match block panel order to the block inspector. (79794)\n\n\n\n\nExtensibility\n\n\n\n\nGuidelines: Add Blocks as a registry scope. (79709)\n\n\n\n\nMedia\n\n\n\n\nMedia Editor: Use new Tabs component from the ui package, and its minimal variant. (79664)\n\n\n\n\nConnectors screen\n\n\n\n\nConnectors: Add application password settings UI. (79403)\n\n\n\n\nClient Side Media\n\n\n\n\nMedia: Return the filtered wp_editor_set_quality value in the upload response. (78420)\n\n\n\n\nBug Fixes\n\n\n\n\nAbilities: Support URI schema format. (79555)\n\n\n\nCommand Palette: Show the search icon on desktop as well. (79881)\n\n\n\nFix: DataForm inspector shows raw “auto-draft” status for new posts. (79914)\n\n\n\nMedia: Fix fatal error from narrowed create_item_from_url() visibility. (79972)\n\n\n\nSite Editor: Update default theme color from fresh to modern. (79814)\n\n\n\ndesign-system-mcp: Use fixed version for alpha MCP server. (80061)\n\n\n\nlintstaged: Avoid appending filenames to the prelint:Js command. (79800)\n\n\n\nCore Abilities: Restore the ready promise and lazy-load via dynamic import. (79155)\n\n\n\n\nBlock Library\n\n\n\n\nAdd translation comment to waveform styles. (80112)\n\n\n\nBlock position: Allow options dropdown to flip. (79798)\n\n\n\nBlocks: Rename _gutenberg_apply_content_filters() to _wp_apply_content_filters(). (80191)\n\n\n\nCover Block: Fix unsaveable state when clearing an embed video background. (80184)\n\n\n\nEnable default gap processing on Gallery block. (79984)\n\n\n\nFile Block: Changed the context for fetching the media. (80085)\n\n\n\nFix – Accordion: Text in a closed accordion panel cannot be found via the browser search. (74744)\n\n\n\nFix and permit unitless zeros used in CSS calc functions. (79786)\n\n\n\nFix global gap styles for Gallery block. (80030)\n\n\n\nFix playlist artwork removal on track switch. (80025)\n\n\n\nFix playlist waveform artist rendering. (80104)\n\n\n\nGIF block variation: Remove icons from “Display as” toolbar buttons and only show when block can be inserted. (79985)\n\n\n\nIcon block: When the default icon is unregistered, nothing is displayed. (80166)\n\n\n\nLatest Posts: Parse blocks in full content display. (74866)\n\n\n\nMake playlist pause button visually match play button. (80217)\n\n\n\nNavigation Link/Submenu: Run post-status check also without Gutenberg plugin (draft/deleted links regression). (79748)\n\n\n\nNavigation Link: Fix “[object Object]” in link preview for untitled entities. (79616)\n\n\n\nPHP-Only blocks: Forward current post ID to server render. (78909)\n\n\n\nPlaylist block: Avoid laggy layout shift when changing tracks. (79497)\n\n\n\nPlaylist: Fix flashing track state when adding new track. (80076)\n\n\n\nPlaylist: Show album art thumbnails. (79942)\n\n\n\nPlaylist: Use PlainText v2 to avoid HTML entities. (80068)\n\n\n\nRemove Playlist border radius support. (79753)\n\n\n\nResponsive editing: Apply crop dimensions to image block placeholder. (80162)\n\n\n\nSelect tab panel when caret moves into tab. (79558)\n\n\n\nTab List: Fix render inline formatting on frontend. (79554)\n\n\n\nTabs: Fix active tab switching from a stale inner-block selection. (79981)\n\n\n\nTabs: Fix dirty editor state on mount caused by tab-list sync. (79540)\n\n\n\nTabs: Fix rich text label comparison when syncing the list. (79582)\n\n\n\nTabs: Prevent tab list from moving focus during revision navigation. (79730)\n\n\n\nTabs: Remove redundant block selection from Add/Remove tab actions. (79571)\n\n\n\nFix crashes when manipulating locked blocks. (80509)\n\n\n\nPlaylist: Fix playback of tracks served without CORS headers. (80533)\n\n\n\nFix default aspect ratio for lazy loaded Featured image. (80386)\n\n\n\nFix playlist block styling. (80312)\n\n\n\nFix: Allow icon labels to wrap with word breaks and no ellipsis. (80256)\n\n\n\nHide color controls for Navigation and Social Icons when viewport sta…. (80289)\n\n\n\nPlaylist: Fix track insertion. (80200)\n\n\n\nTry fixing responsive layout in Nav block. (80305)\n\n\n\nMedia: Remove the redundant __heicUploadSupport flag (#80452). (80486)\n\n\n\n\nComponents\n\n\n\n\nAutocomplete: Use regular weight for result items. (80196)\n\n\n\nBorderBoxControl: Fix unlink button positioning after View Emotion migration. (79967)\n\n\n\nButton: Fix corner artifacts by using background-clip: Border-box. (79524)\n\n\n\nButton: Fix focus ring for link. (79837)\n\n\n\nButton: Hide Core focus ring when button as link is pressed. (80082)\n\n\n\nDataViews: Fix infinite-scroll jump on async page loads. (79546)\n\n\n\nDivider: Restore lower border specificity. (79534)\n\n\n\nExternalLink: Stop setting default rel. (79743)\n\n\n\nIconButton: Use length zero for inline padding. (79722)\n\n\n\nPanel: Fix focus style for toggle button. (80064)\n\n\n\nSandBox: Inject resize script into head to stop it leaking as text. (79920)\n\n\n\nStorybook: Scope documentation theme providers. (79496)\n\n\n\nTabs: Fix stale overflow fade as content settles on load. (79856)\n\n\n\nTheme: Fix token story swatch accessibility. (79960)\n\n\n\nUI: Restore Link focus styles. (80091)\n\n\n\nuseMergeRefs: Apply ref changes after out-of-render attachment. (80133)\n\n\n\nContentEditableControl: Fix invalid label association with contenteditable div. (80441)\n\n\n\nBackport ColorPicker cursor shaking fix to WordPress 7.1. (80435)\n\n\n\nDataViews: Fix the list layout ignoring some settings when groupBy is set. (80255)\n\n\n\nDataViews: Fix the unintended gap between list layout items when groupBy is set. (80254)\n\n\n\nUI: Backport compat overlay fixes to WordPress 7.1. (80322)\n\n\n\nfix: Set dataviews popover hover text color. (80105)\n\n\n\n\nBlock Editor\n\n\n\n\nDimensionControl: Include styles in stylesheet. (79916)\n\n\n\nEditor: Use the DS focus color for all sidebar elements. (80087)\n\n\n\nFix clipped/doubled focus outline on inserter block list items. (79845)\n\n\n\nFix unsetting values in viewport states for grid and constrained layouts. (79520)\n\n\n\nHTML Block: Preserve innerContent when transforming to group, columns. (79887)\n\n\n\nMove inspector controls styles slot back to previous position. (80111)\n\n\n\nRender the selected static inner block synchronously. (79726)\n\n\n\nRich text: Cut through the record instead of execCommand. (80155)\n\n\n\nWriting flow: Fix selection end mapping at block boundaries. (80126)\n\n\n\nuseTypingObserver: Capture the window reference for cleanup. (78772)\n\n\n\nGlobal Styles: Resolve per-level heading element styles in block inspector controls. (80495)\n\n\n\nRedirect editing events to extension handlers under editableRoot. (80287)\n\n\n\nWriting flow: Fully select the items when a selection extends down into a nested item. (80492)\n\n\n\n\nPost Editor\n\n\n\n\nEditor: Render back button as proper , which cleans up custom CSS. (79862)\n\n\n\nEditor: Render post preview action as a menu item. (80195)\n\n\n\nFix clipped focus ring on the document bar. (80084)\n\n\n\nImage: Sideload external images on the server when uploading to the library. (79409)\n\n\n\nNotes: Allow canceling the autocompleter popover with Escape without dismissing the note form. (80224)\n\n\n\nDevice type preview: Fix collapsing to content height. (80553)\n\n\n\nNotes: Align floating threads with their inline marker. (79877)\n\n\n\nWrap notices in ThemeProvider with 0 corner radius. (80557)\n\n\n\nAutocompleters: Don’t pre-encode mention search terms. (80377)\n\n\n\nEditor: Disable canvas resizing while zoomed out. (80391)\n\n\n\nFix upload snackbar stuck in uploading state on server-side uploads. (80345)\n\n\n\nNotes: Finish WPDS treatment for mention chips. (80300)\n\n\n\nResponsive styles: Open inspector sidebar when toggling. (80307)\n\n\n\nResponsive styles: Use viewport dropdown to control states for in-editor global styles sidebar. (80339)\n\n\n\nFix upload snackbar double-counting a single HEIC upload in Safari. (80436)\n\n\n\nEditor: Restore fixed device preview height for mobile and tablet. (80466)\n\n\n\n\nSite Editor\n\n\n\n\nEditor: Fix regression and restore the back button focus ring. (80029)\n\n\n\nEditor: Render mobile back button as proper and remove custom CSS. (80032)\n\n\n\nEditor: restore the behavior of only showing back button focus ring on :Focus-visible. (80114)\n\n\n\nStyle Book: Pass site editor settings to StyleBookPreview on the styles route. (80035)\n\n\n\n\nMedia\n\n\n\n\nExperimental Media Modal: Ensure selection is properly cleared between open/close. (79731)\n\n\n\nMedia Modals: Invalidate attachment caches when closing the modal. (79844)\n\n\n\nMedia editor modal: Balance top padding for sidebar controls. (79660)\n\n\n\n\nClient Side Media\n\n\n\n\nApply and correct EXIF orientation for client side sub-sizes. (79384)\n\n\n\nMedia: Backport client-side media improvements from WordPress core backports. (79603)\n\n\n\nVips: Preserve bit depth of high-bit-depth AVIF in sub-sizes. (79556)\n\n\n\n\nIcons\n\n\n\n\nPlaylist icon: Fix bug with missing viewbox. (80180)\n\n\n\nStore the sanitized SVG content when registering an icon. (80508)\n\n\n\n\nBlock API\n\n\n\n\nBlock Supports: Ensure that custom CSS is output after the block library styles. (80062)\n\n\n\n\nGuidelines\n\n\n\n\nRender block icons like the editor so every icon displays correctly. (79738)\n\n\n\n\nCollaboration\n\n\n\n\nRTC: Fix autosave update with no content. (79591)\n\n\n\nNotes: Arm the mention kses allowance on REST note creation. (80221)\n\n\n\n\nStyle States\n\n\n\n\nStyle Engine: Preserve important gradient declarations. (79568)\n\n\n\nHide block style variations when state is enabled in global styles. (80341)\n\n\n\n\nData Layer\n\n\n\n\nRTC: Fix undo / redo breakage when plug-in with metabox is loaded. (79510)\n\n\n\n\nConnectors screen\n\n\n\n\nPrevent overscroll bounce for stage and inspector surfaces. (78587)\n\n\n\n\nGlobal Styles\n\n\n\n\nBlock Supports: Handle nested array block gap values properly. (80464)\n\n\n\nStyle Book: Restore live global styles updates on the styles route. (80459)\n\n\n\n\nAccessibility\n\n\n\nMedia\n\n\n\n\nMedia editor: Address accessibility review feedback. (79966)\n\n\n\n\nPost Editor\n\n\n\n\nEditor: Move focus to revisions slider when entering revisions mode. (79691)\n\n\n\nReplaces the title attributes used by revision inline diff annotations with aria-describedby. (80440)\n\n\n\nRevisions: Specify block level diff status via aria-label. (77779)\n\n\n\n\nComponents\n\n\n\n\nA11y: Replace local aria-live regions with speak(). (79600)\n\n\n\n\nBlock Library\n\n\n\n\nFocus first tab when adding Tabs block. (79507)\n\n\n\n\nPerformance\n\n\n\n\nCI: Avoid full-history checkout for the root-dependencies check. (79489)\n\n\n\n\nBlock Library\n\n\n\n\nLatest Posts: Fix slow category selection with large category lists. (80198)\n\n\n\n\nData Layer\n\n\n\n\nRTC: Only apply CRDT updates synchronously when collaborating. (79991)\n\n\n\n\nBlock API\n\n\n\n\nBlock Supports: Prevent Additional CSS duplication inside Query Loop. (78282)\n\n\n\n\nGlobal Styles\n\n\n\n\nprepend_to_selector: Optimized with str_replace(). (76556)\n\n\n\n\nExperiments\n\n\n\n\nMove long intro to content. (79578)\n\n\n\nShorten the page name. (79579)\n\n\n\n\nPost Editor\n\n\n\n\nAdd PluginPostStatusInfo in DataForm post summary. (79586)\n\n\n\nMedia Inserter: Try adding a simple Attachments category with attach and detach behaviour. (79336)\n\n\n\n\nGuidelines\n\n\n\n\nKnowledge: Dissolve the Guidelines singleton into per-scope rows. (79263)\n\n\n\nKnowledge: Rename the Guidelines CPT storage primitive to Knowledge. (79149)\n\n\n\n\nBlock Library\n\n\n\n\nDynamic Gallery Block: Attempt a dynamic mode of the gallery block. (78796)\n\n\n\n\nDocumentation\n\n\n\n\nAdd missing docblocks to client-assets.php. (80135)\n\n\n\nAdded Missing Global Documentation. (79827)\n\n\n\nBackfill unreleased changelog entries for the widget packages. (79909)\n\n\n\nBadge: Update storybook with “don’t use icons” example. (79585)\n\n\n\nComponents: Add missing descriptions for design system components. (79460)\n\n\n\nComponents: Document CSS module class composition. (79490)\n\n\n\nComponents: Link recommended UI component. (80127)\n\n\n\nDesign system MCP: Document Codex CLI prerequisite for MCP setup. (79917)\n\n\n\nDocs: Add a widget anatomy doc and lighten the widget system doc. (79435)\n\n\n\nDocs: Add image hosting guidance to the documentation contributors guide. (79574)\n\n\n\nDocs: Add missing since, param, and return tags in REST API compat file. (80079)\n\n\n\nDocs: Clarify release recovery steps. (79884)\n\n\n\nFix typo in inline comment in collaboration.php. (80147)\n\n\n\nPackages: Backport UI and theme release changelogs. (79690)\n\n\n\nPolish package changelog cleanup. (79826)\n\n\n\nTheme: Clarify focus token naming documentation. (79764)\n\n\n\nTheme: Correct documented default background seed. (80237)\n\n\n\nTheme: Document and test build plugin transform boundaries. (80088)\n\n\n\nTheme: Document ramp memoization contract. (79459)\n\n\n\nTheme: Document token naming grammar. (79769)\n\n\n\nTheme: Remove experimental package messaging. (80049)\n\n\n\nTheme: Update design token format links. (80052)\n\n\n\nTheme: Use token reference as documentation source. (79829)\n\n\n\nThemeProvider: Document wrapper customization scope. (79763)\n\n\n\nUpdating image urls. (79529)\n\n\n\nWP Build: Improve documentation for routes. (79688)\n\n\n\nstylelint-config: Enable token fallback rule. (79768)\n\n\n\ntheme: Clarify package documentation. (79961)\n\n\n\n\nCode Quality\n\n\n\n\nAdded Missing Global Documentation. (80033)\n\n\n\nBackport Changelog: Link Core PR #12007 for #75793. (78786)\n\n\n\nBase Styles: Disallow direct var(–wpds-*) usage. (79424)\n\n\n\nBuild: Move typescript and rimraf out of the root package.json. (80086)\n\n\n\nCODEOWNERS: Add ownership for widget dashboard areas. (79484)\n\n\n\nCode Modernization: Use str_starts_with() in WP_Theme_JSON and WP_Duotone. (79519)\n\n\n\nDedupe lockfile. (79618)\n\n\n\nDependencies: Fix bin resolution, type mismatch, and missing dependencies. (79806)\n\n\n\nDeprecate @wordpress/reusable-blocks public APIs. (79805)\n\n\n\nDuotone: Use HTML API class_list for duotone wrapper class handling. (79531)\n\n\n\nE2E: Ban uuid package via ESLint, use crypto.randomUUID() instead. (79673)\n\n\n\nJest: Add missing clsx dev dependency. (79677)\n\n\n\nLint-staged: Match lint:Css file globs. (79918)\n\n\n\nNotes: Simplify inline-note marker stripping to match core backport (#78218 follow-up). (79670)\n\n\n\nTheme: Use public design token stylesheet imports. (80050)\n\n\n\nUpdate webpack to 5.108.1. (79633)\n\n\n\nUpgrade browserslist to ^4.28.4. (79630)\n\n\n\nUse null coalescing operator instead of isset() ternaries. (79946)\n\n\n\nstylelint-config: Convert configuration to ESM. (79755)\n\n\n\nwp-build: Allow wordpress/theme 1.x peer versions. (80089)\n\n\n\nRelease: Resolve commander from the test file in the release CLI test. (80357)\n\n\n\n\nBlock Library\n\n\n\n\nBlocks package: Stabilize cloneSanitizedBlock and sanitizeBlockAttributes. (79928)\n\n\n\nBlocks: Rename _wp_apply_content_filters() to _wp_apply_block_content_filters(). (80225)\n\n\n\nButton: Fix suppressed ESLint errors. (79944)\n\n\n\nDedupe @testing-library/dom to a single 10.4.1 in the lockfile. (79631)\n\n\n\nEmbed: Refactor ‘EmbedPlaceholder’ to use recommended components. (79759)\n\n\n\nFix linting of waveform test. (80124)\n\n\n\nHeading: Fix ESLint warnings. (79694)\n\n\n\nIcons: Unify collection-scoping route param on collection and validate description. (80113)\n\n\n\nList: Fix suppressed ESLint errors. (79983)\n\n\n\nMedia Editor: Remove inline cropper (follow-up to #78653). (78654)\n\n\n\nPlaylist: Simplify block track state. (79448)\n\n\n\nPlaylist: Simplify waveform metadata updates. (80193)\n\n\n\nRemove redundant @jest-environment jsdom pragmas from unit tests. (79672)\n\n\n\nRemove redundant parentheses around assignments. (79516)\n\n\n\nReplace obsolete View primitive with plain div. (79767)\n\n\n\nStylelint: Enforce class naming for all stylesheets. (79900)\n\n\n\nTabs: Remove editor-only block context. (79848)\n\n\n\nTabs: Remove unnecessary callback memoization. (79567)\n\n\n\nUse modern PHP string functions instead of strpos/substr. (79927)\n\n\n\nMisc fixes for WordPress-Develop 7.0 merges. (80444)\n\n\n\nPlaylist: Update since tags to 7.1.0. (80317)\n\n\n\n\nComponents\n\n\n\n\nDeclare @types/node explicitly and harden no-unsafe-wp-apis. (79626)\n\n\n\nFocalPointPicker: Complete __next40pxDefaultSize cleanup. (79487)\n\n\n\nJest: Mock CSS module class names. (79535)\n\n\n\nMigrate Flex to SCSS module. (79450)\n\n\n\nMigrate Spacer to SCSS module. (79449)\n\n\n\nMigrate Surface to SCSS module. (79445)\n\n\n\nMigrate Theme away from Emotion. (79447)\n\n\n\nMigrate Truncate to SCSS module. (79446)\n\n\n\nMigrate View away from Emotion. (79443)\n\n\n\nQueryControls: Complete __next40pxDefaultSize cleanup. (79485)\n\n\n\nRemove unused FocalPointPicker style.scss. (79902)\n\n\n\nSearchControl: Complete __next40pxDefaultSize cleanup. (79538)\n\n\n\nStylelint: Enforce module class naming in UI packages. (79504)\n\n\n\nStylelint: Lint all CSS file extensions. (79957)\n\n\n\nTheme: Cover display contents wrapper focus behavior. (80056)\n\n\n\nTools: Restrict layout effect imports in UI and theme. (79476)\n\n\n\nUpdate @terrazzo/* to 2.4.0 and regenerate design tokens. (79627)\n\n\n\nUpdate stylelint to 16.26.1. (79648)\n\n\n\nRichTextControl: Replace DOM focus tracking with a single React-tree focus boundary. (80324)\n\n\n\n\nBlock Editor\n\n\n\n\nMedia Inserter: Omit page arg from requests for the first set of results. (80219)\n\n\n\nRich Text: Move RichTextShortcut and RichTextInputEvent into wordpress/rich-text. (79828)\n\n\n\nRich text: Synchronize the selection before events that consume it. (80151)\n\n\n\nSimplify layout panel selector getter. (80176)\n\n\n\nSubscribe to selectionchange permanently in rich text. (79712)\n\n\n\nTextIndentControl: Remove unnecessary __next40pxDefaultSize prop. (79597)\n\n\n\nTypewriter: Remove the block selection gate. (80130)\n\n\n\nUse core/registered-block in reducer tests. (79522)\n\n\n\n\nPost Editor\n\n\n\n\nDeclare undeclared workspace dependencies. (79684)\n\n\n\nEditor: saveDirtyEntities: Don’t allow onSave to filter records. (79850)\n\n\n\nObserve typing on the writing flow node. (80131)\n\n\n\nStyle Book: Migrate to Tabs from wordpress/ui. (80040)\n\n\n\nNotes: Render @ mentions as span chips and narrow the kses class allowance. (80528)\n\n\n\nNotes: Replace blur-deselect bookkeeping with useFocusOutside. (80222)\n\n\n\n\nIcons\n\n\n\n\nAdd Storybook React Vite dev dependency. (79506)\n\n\n\nIcons Registry test: Fix trigger_error suppression on WP < 7.0. (79607)\n\n\n\nValidate SVG icons include currentColor. (79751)\n\n\n\nBackport from Core: Improve icon name unit tests. (80552)\n\n\n\n\nDesign Tools\n\n\n\n\nBlock Style Variations: Simplify block style variation selector regex. (79924)\n\n\n\nBlock Supports: Guard elements hover rendering against missing hover selector. (79511)\n\n\n\n\nPlugin\n\n\n\n\nMove icon tests out of phpunit/experimental. (79695)\n\n\n\nMove real-time collaboration compat code to wordpress-7.1. (79863)\n\n\n\nIcons: Fix collection unregister not removing icons after core added its own registry. (80292)\n\n\n\n\nGuidelines\n\n\n\n\nGuidelines end-to-end Tests: Wait for boot to load copy page. (79663)\n\n\n\nUse str_starts_with() in is_block_meta_key(). (79491)\n\n\n\n\nDataViews\n\n\n\n\nSync changes from core for view-config version handling. (80170)\n\n\n\n\nWidgets Editor\n\n\n\n\nEdit Widgets: Remove unused customizer-edit-widgets-initializer style.scss. (79915)\n\n\n\n\nClient Side Media\n\n\n\n\nVips: Add positional-crop test for high-bit-depth AVIF. (79880)\n\n\n\nVips/upload-media: Consolidate optional params into options objects. (80330)\n\n\n\n\nData Layer\n\n\n\n\nPackages: Backport package release metadata. (79702)\n\n\n\n\nPatterns\n\n\n\n\nPattern editing: Use section block selector for pattern display identity. (79565)\n\n\n\n\nGlobal Styles\n\n\n\n\nReject non-string custom CSS in the REST controller. (80338)\n\n\n\n\nTools\n\n\n\n\nCODEOWNERS: Exclude eslint suppressions.json from /tools ownership. (80125)\n\n\n\nCODEOWNERS: Exclude stylelint suppressions.json from /tools ownership. (80171)\n\n\n\nProject automation: Stop flagging returning contributors as first-timers when they use hidden email addresses. (79987)\n\n\n\n\nTesting\n\n\n\n\nAdd an end-to-end test for single paragraph selection on triple click. (79706)\n\n\n\nAutomated Testing: Configure lint:Css to report needless disables. (79788)\n\n\n\nAutomated Testing: Enforce dependencies checks consistently for development files. (79703)\n\n\n\nAutomated Testing: Enforce no-unresolved checks for test files. (79718)\n\n\n\nAutomated Testing: Use three-dot diff comparison for changelog checks. (79548)\n\n\n\nFix flaky “can use appender in site editor sidebar list view” end-to-end test. (80044)\n\n\n\nFix flaky ‘Activate theme’ end-to-end test. (80090)\n\n\n\nFlaky tests: Fix rich text backtick undo. (80183)\n\n\n\nFlaky tests: Fix widgets global inserter. (80177)\n\n\n\nFlaky tests: Fix writing flow arrow navigation. (80179)\n\n\n\nIcons: Fix viewBox casing assertion in wp_get_icon test for older WP. (79576)\n\n\n\nImage: Use Playwright’s locator.drop for media placeholder drop test. (79733)\n\n\n\nPerf tests: Wait for upload queue to settle between media-upload iterations. (79952)\n\n\n\nRTC: Add RTC WebSocket tests to CI. (79757)\n\n\n\nRTC: Improve stress test flakines. (79954)\n\n\n\nSkip flakey collaboration end-to-end test. (79922)\n\n\n\nTests: Fix flaky ‘GIF to Video’ end-to-end test. (79758)\n\n\n\nTests: Honor waitForUploadQueueEmpty timeout in client-side media. (79783)\n\n\n\nUpgrade Playwright to v1.61. (78632)\n\n\n\nFix useHomeEnd on tabs in mac testing. (80374)\n\n\n\n\nBuild Tooling\n\n\n\n\nAdd more workflow file static analysis with Zizmor. (71523)\n\n\n\nBuild: Make installed-deps check layout-agnostic and surface opt-out env var. (79687)\n\n\n\nBuild: Support –skip-types in npm run dev. (79736)\n\n\n\nBuild: Upgrade to TypeScript 7.0. (80083)\n\n\n\nCI: Enforce pruned ESLint suppressions during lint. (79708)\n\n\n\nDocs: Generalize the npx guidance in AGENTS.md to cover wp-scripts. (79973)\n\n\n\nGithub workflows: Extend package changelog nudge to bundled packages. (78934)\n\n\n\nReact 19 patch: Log warnings when polyfills are hit. (79624)\n\n\n\nReact 19: Patch to support legacy inert attribute values. (79475)\n\n\n\nRelease: Revert to 23.5rc-3. (79741)\n\n\n\nUpdate actionlint to version 1.7.12. (79833)\n\n\n\ntheme: Protect design tokens CSS import. (79551)\n\n\n\nOnly include icon library SVGs listed as public in the Zip file published to GitHub Container Registry for wordpress-develop. (79338)\n\n\n\nRelease: Extract npm release lifecycle. (80190)\n\n\n\n\nData Layer\n\n\n\n\nBackport changelog and package version updates from NPM. (79816)\n\n\n\n\nComponents\n\n\n\n\nAdd an editableRoot block support for native cross-block selection. (79105)\n\n\n\n\nPost Editor\n\n\n\n\nAlways iframe. (74042)\n\n\n\n\nSecurity\n\n\n\n\nOpt in to npm v11 supply-chain security features. (79614)\n\n\n\nRevert npm v11 supply-chain settings (allow-git, allow-remote, allowScripts). (79667)\n\n\n\n\nnpm Packages\n\n\n\n\nBuild: Fix non-breaking npm audit vulnerability alerts. (79886)\n\n\n\n\nFirst-time contributors\n\n\n\nThe following PRs were merged by first-time contributors:
\n\n\n\n\n@bgrgicak: Backport changelog and package version updates from NPM. (79816)\n\n\n\n@deepakpra: Add icon state classes to Accordion block. (74257)\n\n\n\n@g-elwell: Add option to exclude current post from query block. (64916)\n\n\n\n@priethor: Project automation: Stop flagging returning contributors as first-timers when they use hidden email addresses. (79987)\n\n\n\n@saulirajala: Navigation Link/Submenu: Run post-status check also without Gutenberg plugin (draft/deleted links regression). (79748)\n\n\n\n@SohamPatel46: Fix – Accordion: Text in a closed accordion panel cannot be found via the browser search. (74744)\n\n\n\n@milindmore22: Fix: Allow icon labels to wrap with word breaks and no ellipsis. (80256)\n\n\n\n@Pranjal1423: fix: Set dataviews popover hover text color. (80105)\n\n\n\n\nContributors\n\n\n\nThe following contributors merged PRs in this release:
\n\n\n\n@aagam-shah @aaronrobertshaw @adamsilverstein @aduth @alecgeatches @andrewserong @annezazu @anomiex @arthur791004 @bgrgicak @cbravobernal @ciampo @danluu @deepakpra @desrosj @dmsnell @ellatrix @enejb @fushar @g-elwell @getdave @gziolo @himanshupathak95 @huzaifaalmesbah @im3dabasia @jasmussen @jeryj @johnbillion @jonathanbossenger @jorgefilipecosta @josephscott @jsnajdr @juanfra @juanmaguitar @Mamaduka @manzoorwanijk @mcsf @milindmore22 @mirka @Mustafabharmal @noruzzamans @ntsekouras @Pranjal1423 @prasadkarmalkar @priethor @ramonjd @retrofox @rohitmathur-7 @SainathPoojary @saulirajala @scruffian @shail-mehta @shekharnwagh @shrivastavanolo @simison @sirreal @Soean @SohamPatel46 @shimotmk @t-hamano @taipeicoder @talldan @tellthemachines @tyxla @xavier-lc @youknowriad
\n\n\n\nProps to @huzaifaalmesbah for reviewing.
\n\n\n\n#block-editor #core-editor #gutenberg #gutenberg-new
\n\n\n\n", "id": 16764915, "pubDate": "Wed, 22 Jul 2026 13:15:41 GMT", "whenReceived": "Wed, 22 Jul 2026 14:57:16 GMT", "whenUpdated": "Wed, 22 Jul 2026 14:57:16 GMT", "likes": [], "metadata": { "wpPostId": 124627, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Wed, 22 Jul 2026 10:57:16 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68771", "title": "PTE Request for MAD Event Mailer (zh_CN)", "link": "https://make.wordpress.org/polyglots/2026/07/22/pte-request-for-mad-event-mailer-zh_cn/", "description": "I am the plugin author and Simplified Chinese translator for MAD Event Mailer.
\nI have completed and submitted the zh_CN translations for the current stable release, including 235 plugin strings and 45 readme strings. All translations are currently waiting for review.
\nPlease review the submitted translations and add the following WordPress.org user as a Project Translation Editor for this plugin:
\n\nhttps://wordpress.org/plugins/mad-event-mailer/\n\n\n\n #zh_CN – @ruoqin\n\n\nThis will allow me to review and maintain the Simplified Chinese translations for future releases.
\nIf you have any questions or feedback regarding the translations, please leave a comment here. Thank you!
", "id": 16759236, "pubDate": "Wed, 22 Jul 2026 10:22:36 GMT", "whenReceived": "Wed, 22 Jul 2026 10:57:16 GMT", "whenUpdated": "Wed, 22 Jul 2026 15:44:19 GMT", "likes": [], "metadata": { "wpPostId": 68771, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68777", "title": "Hi dear mentors, We have…", "link": "https://make.wordpress.org/polyglots/2026/07/22/hi-dear-mentors-we-have-195/", "description": "Hi dear mentors,
\nWe have great translations that we’d like to integrate on translate.wordpress. Can you please add @wptranslationsorg as CLPTE for this project:
\nProject URL: https://wordpress.org/theme/member-read
\nTo make sure we can apply to this access we fulfilled answered all points below:
\n1. 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.
PS: Thanks for all previously accepted requests
\nThanks in advance
\nFX for the WP-Translations Team
#clpte
\n#editor-requests
", "id": 16759237, "pubDate": "Wed, 22 Jul 2026 09:56:30 GMT", "whenReceived": "Wed, 22 Jul 2026 10:57:16 GMT", "whenUpdated": "Wed, 22 Jul 2026 10:57:16 GMT", "likes": [], "metadata": { "wpPostId": 68777, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68775", "title": "Requesting PTE access for Kabook…", "link": "https://make.wordpress.org/polyglots/2026/07/22/requesting-pte-access-for-kabook/", "description": "Requesting PTE access for Kabook Bulk Discount (#fa_IR)
\nHello Polyglots team,
\nI am the author of the plugin Kabook Bulk Discount. I would like to request PTE (Project Translation Editor) access for the Persian (#fa_IR) locale to manage the translations for this plugin.
\nAs 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.
\nPlugin Link: https://wordpress.org/plugins/kabook-bulk-discount/
\nProfile: @saeidafshari
\nI am committed to following the Persian translation standards and ensuring the high quality of all translated strings.
Thank you for your time and help!
\nBest regards,
\nSaeid Afshari
\n#editor-requests
", "id": 16756307, "pubDate": "Wed, 22 Jul 2026 07:19:30 GMT", "whenReceived": "Wed, 22 Jul 2026 07:37:05 GMT", "whenUpdated": "Wed, 22 Jul 2026 10:57:16 GMT", "likes": [], "metadata": { "wpPostId": 68775, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68773", "title": "Hello,", "link": "https://make.wordpress.org/polyglots/2026/07/22/hello-115/", "description": "Dear Language Team in China，It’s still me。I’d like to become a PTE. I confirm that I’ve read the style guide and/or glossary for the China (CN) locale.I hope to translate and review themes and plugins for various projects.I’ve suggested translations for this Fluent Forms plugin and Astra Themes。would like to have them reviewed.
\n①Name: Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder
\nURL: https://translate.wordpress.org/projects/wp-plugins/fluentform/dev/zh-cn/default/
Theme Name:Astra
\nURL: https://translate.wordpress.org/locale/zh-cn/default/wp-themes/astra/
#editor-requests
", "id": 16756308, "pubDate": "Wed, 22 Jul 2026 06:14:57 GMT", "whenReceived": "Wed, 22 Jul 2026 07:37:05 GMT", "whenUpdated": "Wed, 22 Jul 2026 10:57:16 GMT", "likes": [], "metadata": { "wpPostId": 68773, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/hosting/feed/", "whenReceived": "Wed, 22 Jul 2026 05:57:09 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/hosting/feed/", "guid": "https://make.wordpress.org/hosting/?p=184809", "title": "Hosting Team Meeting Agenda 2026-07-22", "link": "https://make.wordpress.org/hosting/2026/07/22/hosting-team-meeting-agenda-2026-07-22/", "description": "Next Meeting\n\n\n\nThe next meetings will be in the #hosting channel on Wednesday, July 22, 2026 at 0900 UTC and Wednesday, July 22, 2026 at 1800 UTC.
\n\n\n\nAgenda\n\n\n\n\nWP 7.0.2 security release\n\n\n\nWP 7.1 Beta 3 release July 22\n\n\n\nTickets/PRs\n\n\n\nOpen Floor\n\n\n\n\n\nIdeas or suggestions\n\n\n\nAnything else? Please leave a comment with any additions or suggestions for the meeting.
\n\n\n\n\n#agenda, #hosting, #hosting-community, #meetings, #weekly-hosting-chat
", "id": 16755255, "pubDate": "Wed, 22 Jul 2026 03:39:42 GMT", "whenReceived": "Wed, 22 Jul 2026 05:57:09 GMT", "whenUpdated": "Wed, 22 Jul 2026 05:57:09 GMT", "likes": [], "metadata": { "wpPostId": 184809, "wpSiteId": 120824672 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Wed, 22 Jul 2026 00:28:55 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68758", "title": "PTE Request for HUP -…", "link": "https://make.wordpress.org/polyglots/2026/07/21/pte-request-for-hup/", "description": "PTE Request for HUP – Indicadores Económicos (Chile) and HUP Kit Ecommerce Chile
\nI am the plugin author for both plugins below. I have already submitted complete Spanish translations for both (readme + UI strings), currently waiting for review. I’d like to request Project Translation Editor access for my own account so I can approve them and maintain translations going forward.
\n\nhttps://wordpress.org/plugins/hup-indicadores-economicos-chile/\n\nhttps://wordpress.org/plugins/hup-kit-ecommerce-chile/\n\n\n\n #es_CL – @hazmeunapagina (@tobifjellner)\n\n #es_ES – @hazmeunapagina (@nilovelez)\n\n\nThank you!
\n#editor-requests
", "id": 16751321, "pubDate": "Tue, 21 Jul 2026 23:00:27 GMT", "whenReceived": "Wed, 22 Jul 2026 00:28:55 GMT", "whenUpdated": "Wed, 22 Jul 2026 12:30:21 GMT", "likes": [], "metadata": { "wpPostId": 68758, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68760", "title": "PTE Request for BSX File…", "link": "https://make.wordpress.org/polyglots/2026/07/21/pte-request-for-bsx-file/", "description": "PTE Request for BSX File Exchange (es / es_ES)
\nHello Polyglots team,
\nI am the author and maintainer of BSX File Exchange:
\n\nhttps://wordpress.org/plugins/bsx-file-exchange/\n\n\nWordPress.org username: @bs279
\nI would like to request the Plugin Translation Editor (PTE) role for:
\n\nPlugin: BSX File Exchange\n\nGlotPress: https://translate.wordpress.org/projects/wp-plugins/bsx-file-exchange/\n\n\n\n #es_ES \n\n\nI have already contributed 166 translations to the Stable sub-project (currently at 74%).
\nI have the complete Spanish readme translation ready to submit and approve.
Thank you!
\nbs279
#editor-requests
", "id": 16751322, "pubDate": "Tue, 21 Jul 2026 23:00:11 GMT", "whenReceived": "Wed, 22 Jul 2026 00:28:55 GMT", "whenUpdated": "Wed, 22 Jul 2026 00:28:55 GMT", "likes": [], "metadata": { "wpPostId": 68760, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Tue, 21 Jul 2026 20:47:53 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124734", "title": "Dev Chat summary: July 21, 2026", "link": "https://make.wordpress.org/core/2026/07/21/summary-dev-chat-july-21-2026/", "description": "Start of the meeting in Slack, facilitated by @audrasjb See the agenda post.
\n\n\n\n\nAnnouncements \n\n\n\n7.0.2\n\n\n\n\nWP 7.0.2 is available and it is an urgent security release!\n\n\n\n\n7.1\n\n\n\n\n7.1 beta 3 is due for release tomorrow (Wednesday, July 22). The release party starts at 15:00 UTC.Joe expects to land ticket #50921 later today, and will probably want a final review of that at some point.
\n\n\n\nThe goal is to ensure that the related API is as mature as possible, so I’m going to implement the mechanics @afercia describes for links, but not the implementations; that will go into a separate ticket. Noting that the API is already committed and has needs-dev-note workflow keyword ; this ticket is for the metaboxes. Joe won’t add the implementation for the media library icons as suggested in the current PR, though.
\n\n\n\nFrom @jonsurrell\n\n\n\nJon hopes to land some improvements to the documentation site for 7.1. @dmsnell and Jon collaborated during 7.0 fix and update the documentation parsing. Jon hopes to get those changes landed for the parser soon so its in a better state. More recently, @zieladam and him have been looking at interactive, runnable code examples in the documentation for Core. The Playground docs have this already, see this example. Those snippets are powered by Playground.
\n\n\n\nRight now, code snippets are typically done by using extra indentation in the phpdoc. What Adam and I have discussed is not to simply upgrade all the example code to these runnable snippets, but to require an opt-in style where we’d use php codefences like (slack markdown will mangle this):
\n\n\n\n```php interactive\n<?php echo \"example\";\n```\n\n\n\n\nThese changes happen across https://github.com/WordPress/phpdoc-parser/pull/258 (parse the new interactive snippets) and https://github.com/WordPress/wporg-developer/pull/567 (render the interactive snippets in the developer docs).
\n\n\n\nFor example, consider this page which has this snippet:
\n\n\n\n$p = WP_HTML_Processor::create_fragment( \"<div class='free <egg<\\tlang-en'>\" );\n$p->next_tag();\nforeach ( $p->class_list() as $class_name ) {\n echo \"{$class_name} \";\n}\n// Outputs: \"free <egg> lang-en \"\n\n\n\nThe idea is to just change that to be interactive. It’s extracted with the rest of the documentation and is rendered in a runnable snippet. The runner is entirely handled by playground.
\n\n\n\nSee this Slack thread for more info.
\n#7-0-2-2, #7-1, #core, #dev-chat
", "id": 16747578, "pubDate": "Tue, 21 Jul 2026 20:08:14 GMT", "whenReceived": "Tue, 21 Jul 2026 20:47:53 GMT", "whenUpdated": "Tue, 21 Jul 2026 20:47:53 GMT", "likes": [], "metadata": { "wpPostId": 124734, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 21 Jul 2026 20:12:12 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68735", "title": "I am the plugin author for consenteer.", "link": "https://make.wordpress.org/polyglots/2026/07/21/i-am-the-plugin-author-for-consenteer/", "description": "Please add the following WordPress.org users as translation editors.
\n\nhttps://wordpress.org/plugins/consenteer/\n\n\n\n #fr_FR @consenteer\n\n\n#editor-requests
", "id": 16746831, "pubDate": "Tue, 21 Jul 2026 19:51:13 GMT", "whenReceived": "Tue, 21 Jul 2026 20:12:12 GMT", "whenUpdated": "Tue, 21 Jul 2026 20:12:12 GMT", "likes": [], "metadata": { "wpPostId": 68735, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68739", "title": "PTE Request for Lima Labs…", "link": "https://make.wordpress.org/polyglots/2026/07/21/pte-request-for-lima-labs/", "description": "PTE Request for Lima Labs — AI Traffic & Revenue for WooCommerce
\nHello Polyglots! I am the plugin author for Lima Labs — AI Traffic & Revenue for WooCommerce ( https://wordpress.org/plugins/lima-labs-ai-traffic-revenue/ ). We have a complete set of es_ES translations (124 strings, currently waiting) that we’d love to get approved. Please add my WordPress.org user as translation editor for this plugin:
\n\n #es_ES – @limalabs\n\n\nIf you have any feedback on the translations, I’ll be happy to update them. Thank you!
\n#editor-requests
", "id": 16746832, "pubDate": "Tue, 21 Jul 2026 19:51:02 GMT", "whenReceived": "Tue, 21 Jul 2026 20:12:12 GMT", "whenUpdated": "Tue, 21 Jul 2026 20:12:12 GMT", "likes": [], "metadata": { "wpPostId": 68739, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68741", "title": "Plugin: Bloqcode Chile – RUT and Checkout Validation", "link": "https://make.wordpress.org/polyglots/2026/07/21/plugin-bloqcode-chile-rut-and-checkout-validation/", "description": "URL: https://wordpress.org/plugins/bloqcode-chile-rut-y-validacion-de-compra/
\nLocale: es_CL (Spanish – Chile)
\nUser: @bloqcode
I am the plugin author and I would like to become a PTE for this plugin in the es_CL locale to approve its Chilean Spanish translations.
\n\n #es_CL (@tobifjellner)\n\n\n#editor-requests
", "id": 16746833, "pubDate": "Tue, 21 Jul 2026 19:50:52 GMT", "whenReceived": "Tue, 21 Jul 2026 20:12:12 GMT", "whenUpdated": "Wed, 22 Jul 2026 02:35:42 GMT", "likes": [], "metadata": { "wpPostId": 68741, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Tue, 21 Jul 2026 14:06:55 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124715", "title": "Dev Chat Agenda – July 21, 2026", "link": "https://make.wordpress.org/core/2026/07/21/dev-chat-agenda-july-21-2026/", "description": "The next WordPress Developers Chat will take place on Tuesday, July 21, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.
\n\n\n\nThe live meeting will focus on the discussion for upcoming releases, and have an open floor section.
\n\n\n\nThe 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\nNote: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.
\n\n\n\n7.0.2\n\n\n\n\nWP 7.0.2 is available and it is an urgent security release\n\n\n\n\n7.1\n\n\n\n\n7.1 Beta 3 is due for release this Wednesday, July 22th. The release party starts at 15:00 UTC.\n\n\n\nFrom @adrianduffell:\n\nThere’s about 140 Trac tickets milestoned for 7.1. It would be good for owners to start punting the tickets that can be safely picked up in a future release. This will help to make the remaining 7.1 priorities clearer.\n\n\n\nHighlighting a few bugs with simple PRs needing review. It might be possible to merge them before beta 4 next week:\n\n#65417\n\n\n\n#62407\n\n\n\n#65345\n\n\n\n#64972\n\n\n\n\n\n\n\n\nGeneral\n\n\n\n\nPerformance Chat Summary: 14 July 2026\n\n\n\nGuide to WCUS 2026\n\n\n\n\n\nDiscussions \n\n\n\nThe 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\nAny 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.
#7-1, #agenda, #core, #dev-chat
", "id": 16737696, "pubDate": "Tue, 21 Jul 2026 13:25:05 GMT", "whenReceived": "Tue, 21 Jul 2026 14:06:55 GMT", "whenUpdated": "Tue, 21 Jul 2026 14:06:55 GMT", "likes": [], "metadata": { "wpPostId": 124715, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 21 Jul 2026 13:32:05 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68737", "title": "PTE Request for [TearSnow Mobile Theme Switcher]", "link": "https://make.wordpress.org/polyglots/2026/07/21/pte-request-for-tearsnow-mobile-theme-switcher/", "description": "I am the plugin author for [TearSnow Mobile Theme Switcher]. We have a number of great translation editors that we’d like to be able to approve translation for our plugin. Please add the following WordPress.org users as translation editors for their respective locales:
\n\nplugin directory： https://wordpress.org/plugins/tearsnow-mobile-theme-switcher/\n\n\n\n #zh_CN – @tearsnow , @leixue , @fanly\n\n #zh_HK – @tearsnow , @leixue , @fanly\n\n #zh_SG – @tearsnow , @leixue , @fanly\n\n #zh_TW – @tearsnow , @leixue , @fanly\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16736927, "pubDate": "Tue, 21 Jul 2026 12:45:49 GMT", "whenReceived": "Tue, 21 Jul 2026 13:32:05 GMT", "whenUpdated": "Tue, 21 Jul 2026 13:32:05 GMT", "likes": [], "metadata": { "wpPostId": 68737, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68715", "title": "Please add me as PTE for my plugin Pingvera", "link": "https://make.wordpress.org/polyglots/2026/07/21/please-add-me-as-pte-for-my-plugin-pingvera/", "description": "Plugin: Pingvera
\nPlugin URL: https://wordpress.org/plugins/pingvera/
\nGlotPress: https://translate.wordpress.org/projects/wp-plugins/pingvera/
I’m the plugin author and have prepared a full Russian translation of the readme.
\nThank you!
#editor-requests
", "id": 16731465, "pubDate": "Tue, 21 Jul 2026 08:02:02 GMT", "whenReceived": "Tue, 21 Jul 2026 08:30:55 GMT", "whenUpdated": "Tue, 21 Jul 2026 08:30:55 GMT", "likes": [], "metadata": { "wpPostId": 68715, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68720", "title": "#editor-requests Hi Polyglots team, I’d…", "link": "https://make.wordpress.org/polyglots/2026/07/21/editor-requests-hi-polyglots-team-id/", "description": "#editor-requests
\nHi Polyglots team,
\nI’d like to request PTE (Project Translation Editor) rights for the Japanese (ja) locale of my plugin, so I can approve the pending translations I’ve submitted.
\n Plugin: https://wordpress.org/plugins/grip-contact-form/
\n Locale: ja (Japanese)
\n Translators to grant PTE: @gripspace
Additional info:
\n GlotPress: https://translate.wordpress.org/projects/wp-plugins/grip-contact-form/
I’m a native Japanese speaker and the plugin’s author. The pending Japanese strings were written by me and already ship inside the plugin package.
\n\n #ja\n\n\nThank you!
\n#editor-requests
", "id": 16731466, "pubDate": "Tue, 21 Jul 2026 08:01:49 GMT", "whenReceived": "Tue, 21 Jul 2026 08:30:55 GMT", "whenUpdated": "Tue, 21 Jul 2026 08:30:55 GMT", "likes": [], "metadata": { "wpPostId": 68720, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68727", "title": "PTE Request for [Roper Buy…", "link": "https://make.wordpress.org/polyglots/2026/07/21/pte-request-for-roper-buy/", "description": "PTE Request for [Roper Buy It Now Button for WooCommerce]
\nPlugin Name: Roper Buy It Now Button for WooCommerce
\nPlugin URL: – https://wordpress.org/plugins/roper-buy-it-now-button/
\nLocale: zh_CN
\nWordPress.org Username: Roper
I am the plugin author and I have translated all strings. I would like to request PTE status for zh_CN to approve translations for my plugin. Thank you!
\n\n #zh_CN (@tobifjellner)\n\n\n#editor-requests
", "id": 16731467, "pubDate": "Tue, 21 Jul 2026 08:01:36 GMT", "whenReceived": "Tue, 21 Jul 2026 08:30:55 GMT", "whenUpdated": "Tue, 21 Jul 2026 21:08:19 GMT", "likes": [], "metadata": { "wpPostId": 68727, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68725", "title": "Title: PTE Request for elevenX Image Alt Manager", "link": "https://make.wordpress.org/polyglots/2026/07/21/title-pte-request-for-elevenx-image-alt-manager/", "description": "I’m the plugin author and will be personally reviewing the Spanish translations as a fluent speaker. Please add me as translation editor for the locales below.
\n\nhttps://wordpress.org/plugins/elevenx-image-alt-manager/\n\n\n\n #es_ES – @elevenxplugins\n\n #es_MX – @elevenxplugins\n\n\nThanks! Happy to answer any questions here.
\n#editor-requests
", "id": 16731468, "pubDate": "Tue, 21 Jul 2026 08:01:20 GMT", "whenReceived": "Tue, 21 Jul 2026 08:30:55 GMT", "whenUpdated": "Tue, 21 Jul 2026 08:30:55 GMT", "likes": [], "metadata": { "wpPostId": 68725, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/test/feed/", "whenReceived": "Tue, 21 Jul 2026 08:20:05 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/?p=12514", "title": "Test Chat Summary: July 16th, 2026", "link": "https://make.wordpress.org/test/2026/07/21/test-chat-summary-july-16th-2026/", "description": "On Thursday, 16 July 2026, 03:00 PM UTC, <test-chat> started in #core-test facilitated by @nikunj8866. The agenda can be found here.
\n\n\n\n1. Attendance\n\n\n\nIn attendance was:
@nikunj8866 @ozgursar @huzaifaalmesbah @r1k0 @andrewssanya @mosescursor (async)
This week’s Note-taker was @nikunj8866
\n\n\n\n3. Test Team Discussions\n\n\n\n\nOfficialize the Test Reports\n\n@huzaifaalmesbah suggested this should go through the Meta Team, or a Meta Trac ticket should be opened.\n\n\n\n@nikunj8866 will open a Meta Trac.\n\n\n\n\n\nFeature and enhancement testing Page\n\n@huzaifaalmesbah noted the existing Patch Testing page likely already covers this, and leaned toward improving it rather than creating a new page.\n\n\n\n@ozgursar referenced the recently updated Call for Testing page as relevant context.\n\n\n\nTeam agreed the existing documentation already covers the proposal.\n\n\n\nIssue closed by @nikunj8866, with a comment referencing today’s discussion.\n\n\n\n\n\nAdd page with current team goals/initiatives\n\n@ozgursar raised whether implementing @sirlouen suggestion would require switching from categories to tags – noting this has come up in prior test chats too.\n\n\n\n@r1k0 agreed with the tags approach and asked if a current “goals” post already exists – confirmed no.\n\n\n\nTeam agreed to follow @sirlouen suggestion: add a link to the initiatives tag in index.md.\n\n\n\nOpen to anyone – a PR is welcome for this change.\n\n\n\n\n\n\n4. Open Floor\n\n\n\nThere were no additional topics raised during the open floor session.
\n\n\n\n5. Announcements\n\n\n\nWordPress Ecosystem Announcements\n\n\n\n\nWordPress 7.0.1 RC1 is now available\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\nWordPress 7.1 Release Party Schedule\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.1 is now available\n\n\n\n\nTest Team Announcements\n\n\n\n\nMonth in Test: July 02, 2026\n\n\n\nTest Team Update: 16 July, 2026\n\n\n\n\nCall for Testing\n\n\n\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.2 milestone that need testing.\n\n\n\nWe also have a couple of Gutenberg Issues that need testing.\n\n\n\n\n6. Other Meetings\n\n\n\n\nThursday, 23 July 2026, 03:00 PM UTC – <patch-testing-scrub> in #core-test.\n\n\n\nThursday, 30 July 2026, 03:00 PM UTC – <test-chat> in #core-test.\n\n\n\n\n\n#core-test, #test-chat-summary
", "id": 16731299, "pubDate": "Tue, 21 Jul 2026 06:47:08 GMT", "whenReceived": "Tue, 21 Jul 2026 08:20:05 GMT", "whenUpdated": "Tue, 21 Jul 2026 08:20:05 GMT", "likes": [], "metadata": { "wpPostId": 12514, "wpSiteId": 255400204 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "whenReceived": "Tue, 21 Jul 2026 06:28:46 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "guid": "https://make.wordpress.org/accessibility/?p=17567", "title": "Accessibility Team Meeting Notes: July 16, 2026", "link": "https://make.wordpress.org/accessibility/2026/07/21/accessibility-team-meeting-notes-july-16-2026/", "description": "These is the bi-weekly notes for the Accessibility Team meeting that happens on alternate Thursday in #accessibility. You can read the full transcript here or see the full meeting schedule.
\n\n\n\nAnnouncements \n\n\n\n\nWordPress 7.1 Beta 1 is released\n\n\n\nGuide to WCUS 2026\n\n\n\nWordPress 7.0.1 Maintenance Release\n\n\n\n\nDiscussion on proposed team restructure
\n\n\n\nThe team discussed reorganizing the Accessibility Team’s focus areas on the Get Involved page by replacing the existing working groups with three primary focus areas:
\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\nDocs
\n\n\n\n\nSeveral accessibility documentation updates were published, including refreshed accessibility testing guides and an updated page on accessibility legislation.\n\n\n\nThe Accessibility Team Handbook is being migrated to GitHub and simplified to focus on team information and contributor onboarding, while accessibility guidance will remain on wpaccessibility.org.\n\n\n\nThe proposed handbook updates also reflect the team’s new focus areas in place of the previous working groups.\n\n\n\nDocumentation work will continue with improvements to content discoverability, including better cross-linking, a user sitemap, and an updated reading guide.\n\n\n\n\nGeneral & Gutenberg
\n\n\n\n\nWith WordPress 7.1 Beta 1 released, the team’s focus has shifted to bug fixes and accessibility testing ahead of RC1. One remaining enhancement is expected to be included in Beta 2.\n\n\n\nContributors were encouraged to review recently introduced features, including Notes, client-side media and media editing, lightbox captions, the Tabs and Playlist blocks, revisions, the Identity panel, and Command Palette updates.\n\n\n\nThe team also reviewed the progress of accessibility work for WordPress 7.1, with 24 accessibility-related Trac tickets completed and 16 still open for the release cycle.\n\n\n\n\nThemes
\n\n\n\n\nAccessibility-ready theme reviews continue to progress, though work remains slow due to the size of the existing backlog.The team discussed extending the review deadline, with the end of September suggested as a more realistic target. \n\n\n\nA formal announcement will be made once the new timeline is finalized.Review efforts will continue to prioritize themes whose authors have requested re-reviews, followed by themes that have shipped updates.\n\n\n\n\n\n\n\nNOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.
\n\n\n\n\n\n#accessibility, #meeting-notes
", "id": 16730051, "pubDate": "Tue, 21 Jul 2026 05:57:11 GMT", "whenReceived": "Tue, 21 Jul 2026 06:28:46 GMT", "whenUpdated": "Tue, 21 Jul 2026 06:28:46 GMT", "likes": [], "metadata": { "wpPostId": 17567, "wpSiteId": 29901991 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 20 Jul 2026 22:29:35 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68709", "title": "PTE Request for MantaWeb Consent Shield", "link": "https://make.wordpress.org/polyglots/2026/07/20/pte-request-for-mantaweb-consent-shield/", "description": "Hi Polyglots Team,
\nI am the plugin author of MantaWeb Consent Shield and I would like to request PTE access for Hebrew so I can review and approve translations for my own plugin.
Plugin: https://wordpress.org/plugins/mantaweb-consent-shield/
\nGlotPress: https://translate.wordpress.org/projects/wp-plugins/mantaweb-consent-shield/
I am a native Hebrew speaker. The plugin is built primarily for the Israeli market (it implements Israeli Privacy Law Amendment 13 compliance), so the Hebrew locale is the main audience for it.
\nThe Hebrew strings currently waiting were written by me and already ship inside the plugin package.
Thank you for your time.
\n\n #he_IL @mantaweb\n\n\n#editor-requests
", "id": 16724401, "pubDate": "Mon, 20 Jul 2026 21:39:38 GMT", "whenReceived": "Mon, 20 Jul 2026 22:29:35 GMT", "whenUpdated": "Mon, 20 Jul 2026 22:29:35 GMT", "likes": [], "metadata": { "wpPostId": 68709, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68711", "title": "PTE Request for Captcha by BestWebSoft plugin (fa_IR)", "link": "https://make.wordpress.org/polyglots/2026/07/20/pte-request-for-captcha-by-bestwebsoft-plugin-fa_ir/", "description": "Hello Polyglots team,
\nI am the plugin author/maintainer of the Captcha by BestWebSoft plugin for WordPress.
\nPlugin:
\n\nhttps://wordpress.org/plugins/captcha-bws/\n\n\nI would like to request Project Translation Editor (PTE) access for the fa_IR locale for this plugin.
\nI am currently completing the Persian translation for the plugin, and I am following the official WordPress Persian glossary and translation guidelines. I am committed to maintaining the translation, reviewing future translation suggestions, and keeping it up to date with new releases to ensure high-quality localization.
\nThank you for your time and consideration.
\n\n #fa_IR @daniyousefifar (@tobifjellner)\n\n\n#editor-requests
", "id": 16724402, "pubDate": "Mon, 20 Jul 2026 21:34:33 GMT", "whenReceived": "Mon, 20 Jul 2026 22:29:35 GMT", "whenUpdated": "Tue, 21 Jul 2026 21:08:19 GMT", "likes": [], "metadata": { "wpPostId": 68711, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68697", "title": "PTE Request for PLTarget – Post Links Target", "link": "https://make.wordpress.org/polyglots/2026/07/20/pte-request-for-pltarget-post-links-target/", "description": "Hello Polyglots team,
\nI am the plugin author for PLTarget – Post Links Target.
\nI would like to request PTE (Project Translation Editor) status for the Russian locale.
Thank you!
\n#editor-requests
", "id": 16715827, "pubDate": "Mon, 20 Jul 2026 15:51:56 GMT", "whenReceived": "Mon, 20 Jul 2026 15:59:06 GMT", "whenUpdated": "Mon, 20 Jul 2026 15:59:06 GMT", "likes": [], "metadata": { "wpPostId": 68697, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68699", "title": "PTE Request for SEV Rewrite-Free WebP for W3TC and Holiday Mode for WooCommerce", "link": "https://make.wordpress.org/polyglots/2026/07/20/post-title-pte-request-for-72/", "description": "I am the plugin author for SEV Rewrite-Free WebP for W3TC and Holiday Mode for WooCommerce. 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/sev-rewrite-free-webp-for-w3tc/\n\nhttps://wordpress.org/plugins/holiday-mode-for-woocommerce/\n\n\n\n #de_DE – @hfranz\n\n #de_CH – @hfranz\n\n #de_at – @hfranz\n\n #en_GB – @hfranz\n\n #es_ES – @hfranz (@nilovelez)\n\n #fr_FR – @hfranz\n\n #it_IT – @hfranz\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16713749, "pubDate": "Mon, 20 Jul 2026 14:30:50 GMT", "whenReceived": "Mon, 20 Jul 2026 14:33:42 GMT", "whenUpdated": "Mon, 20 Jul 2026 17:39:08 GMT", "likes": [], "metadata": { "wpPostId": 68699, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68693", "title": "Hello, I am the plugin…", "link": "https://make.wordpress.org/polyglots/2026/07/20/hello-i-am-the-plugin-13/", "description": "Hello,
\nI am the plugin author for ideo Field Porter ( https://wordpress.org/plugins/ideo-field-porter/ ). I am French and translate my own plugin’s strings into French myself.
\nI’ve imported/suggested the French (fr_FR) translations for the plugin on translate.wordpress.org and would like to request PTE (Project Translation Editor) status for fr_FR on this project, so I can review and approve them myself going forward.
\nI confirm I’ve read the French locale’s style guide and glossary.
\nThank you,
\njellob77
#editor-requests
", "id": 16713750, "pubDate": "Mon, 20 Jul 2026 13:00:45 GMT", "whenReceived": "Mon, 20 Jul 2026 14:33:42 GMT", "whenUpdated": "Mon, 20 Jul 2026 14:33:42 GMT", "likes": [], "metadata": { "wpPostId": 68693, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68688", "title": "PTE Request for Gravity PDF", "link": "https://make.wordpress.org/polyglots/2026/07/20/pte-request-for-gravity-pdf/", "description": "I am the plugin user for Gravity PDF. I am translation editor and like to be able to approve translation for that plugin. Please add me as translation editor for its respective locales:
\n\nhttps://wordpress.org/plugins/gravity-forms-pdf-extended/\n\n\n\n #ru_RU – @mahasvin, @anansi.pro\n\n\n#editor-requests
", "id": 16713751, "pubDate": "Mon, 20 Jul 2026 13:00:33 GMT", "whenReceived": "Mon, 20 Jul 2026 14:33:42 GMT", "whenUpdated": "Mon, 20 Jul 2026 14:33:42 GMT", "likes": [], "metadata": { "wpPostId": 68688, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/training/feed/", "whenReceived": "Mon, 20 Jul 2026 12:00:36 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/training/feed/", "guid": "https://make.wordpress.org/training/?p=175403", "title": "Meeting agenda for July 21st, 2026", "link": "https://make.wordpress.org/training/2026/07/20/meeting-agenda-for-july-21st-2026/", "description": "This week’s meeting will be held on Tuesday, July 21st, 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\nThis week’s meeting will be hosted by @devmuhib.
\n\n\n\n1. Intro/Welcome\n\n\n\nWelcome 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\nJuly 21st – @sibokul\n\n\n\nJuly 28th – @pravin1996\n\n\n\nAug 4th – @mohkatz\n\n\n\nAug 11th – Need Volunteer\n\n\n\nAug 18th – Need Volunteer\n\n\n\n\n\nLooking for feedback\n\nWe are planning to host Office Hours on July 26, 2026, but we need your help:\n\nDo you agree with the proposed date – July 26, 2026?\n\n\n\nWe need someone to host the meeting. Please state your interest and availability to host the Office Hours meeting\n\n\n\nWe need a note-taker for the Office Hours meeting. Please state your interest and availability.\n\n\n\nWe would like to know your opinion on how we can improve these meetings and encourage more members to join and participate actively. You can share your suggestion here or in this GitHub issue – https://github.com/WordPress/Learn/issues/3535. Big thank you to everyone who has shared feedback so far!\n\n\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\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: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\nYou 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": 16710659, "pubDate": "Mon, 20 Jul 2026 10:49:58 GMT", "whenReceived": "Mon, 20 Jul 2026 12:00:36 GMT", "whenUpdated": "Mon, 20 Jul 2026 12:00:36 GMT", "likes": [], "metadata": { "wpPostId": 175403, "wpSiteId": 46403572 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 20 Jul 2026 11:13:14 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68679", "title": "Hi Polyglots team,", "link": "https://make.wordpress.org/polyglots/2026/07/20/hi-polyglots-team-49/", "description": "I’m the author and committer of the plugins below and would like to become PTE for them so I can manage and review their translations. Requesting for myself.
\nPlugins:
\n\nWP RSS Aggregator — https://wordpress.org/plugins/wp-rss-aggregator/\n\nSpotlight Social Feeds — https://wordpress.org/plugins/spotlight-social-photo-feeds/\n\nBatchPilot — https://wordpress.org/plugins/batchpilot/\n\nVireo Analytics — https://wordpress.org/plugins/vireo-analytics/\n\nVerdix Reviews — https://wordpress.org/plugins/verdix-reviews/\n\nKatina Link Manager — https://wordpress.org/plugins/katina-link-manager/\n\nScheduled Content Dashboard — https://wordpress.org/plugins/scheduled-content-dashboard/\n\nShake Connect — https://wordpress.org/plugins/shake-connect/\n\n\nEditor / locales:
\n\n #es_ES – @jeangalea\n\n #de_DE – @jeangalea\n\n #fr_FR – @jeangalea\n\n #ja – @jeangalea\n\n #pt_PT – @jeangalea\n\n #pt_BR – @jeangalea\n\n #nl_NL – @jeangalea\n\n #it_IT – @jeangalea\n\n\nThanks!
\n#editor-requests
", "id": 16709670, "pubDate": "Mon, 20 Jul 2026 09:43:20 GMT", "whenReceived": "Mon, 20 Jul 2026 11:13:14 GMT", "whenUpdated": "Mon, 20 Jul 2026 11:13:14 GMT", "likes": [], "metadata": { "wpPostId": 68679, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/docs/feed/", "whenReceived": "Mon, 20 Jul 2026 10:15:29 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/docs/feed/", "guid": "https://make.wordpress.org/docs/2026/07/20/xpost-documentation-team-update-july-20-2026/", "title": "X-post: Documentation Team Update – July 20, 2026", "link": "https://make.wordpress.org/docs/2026/07/20/xpost-documentation-team-update-july-20-2026/", "description": "X-comment from +make.wordpress.org/updates: Comment on Documentation Team Update – July 20, 2026
", "id": 16708474, "pubDate": "Mon, 20 Jul 2026 08:48:41 GMT", "whenReceived": "Mon, 20 Jul 2026 10:15:29 GMT", "whenUpdated": "Mon, 20 Jul 2026 10:15:29 GMT", "likes": [], "metadata": { "wpPostId": 112728, "wpSiteId": 31760022 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/test/feed/", "whenReceived": "Mon, 20 Jul 2026 07:54:10 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/2026/07/20/xpost-help-us-test-the-new-wordpress-playground-ui/", "title": "X-post: Help Us Test the New WordPress Playground UI!", "link": "https://make.wordpress.org/test/2026/07/20/xpost-help-us-test-the-new-wordpress-playground-ui/", "description": "X-comment from +make.wordpress.org/playground: Comment on Help Us Test the New WordPress Playground UI!
", "id": 16706714, "pubDate": "Mon, 20 Jul 2026 06:17:45 GMT", "whenReceived": "Mon, 20 Jul 2026 07:54:10 GMT", "whenUpdated": "Mon, 20 Jul 2026 07:54:10 GMT", "likes": [], "metadata": { "wpPostId": 12513, "wpSiteId": 255400204 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 20 Jul 2026 06:12:24 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68685", "title": "PTE Request for Loco Translate", "link": "https://make.wordpress.org/polyglots/2026/07/20/pte-request-for-loco-translate-6/", "description": "As a translator who meets the Polyglots General Expectations, I would
\nlike to request PTE status for Loco Translate for the Arabic locale
I have submitted translation suggestions for this project, which can
\nbe reviewed here:
\nhttps://translate.wordpress.org/projects/wp-plugins/loco-translate/stable/ar/default/
My WordPress.org username: mokhtarbsaid
\nThank you
\n#ar
\n#editor-requests
", "id": 16705815, "pubDate": "Mon, 20 Jul 2026 06:04:28 GMT", "whenReceived": "Mon, 20 Jul 2026 06:12:24 GMT", "whenUpdated": "Mon, 20 Jul 2026 06:12:24 GMT", "likes": [], "metadata": { "wpPostId": 68685, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68675", "title": "PTE Request for Animation Addons for Elementor plugin (fa_IR)", "link": "https://make.wordpress.org/polyglots/2026/07/19/pte-request-for-animation-addons-for-elementor-plugin-fa_ir/", "description": "Hello Polyglots team,
\nI am the plugin author/maintainer of the Animation Addons for Elementor plugin for WordPress.
\nPlugin:
\n\nhttps://wordpress.org/plugins/animation-addons-for-elementor/\n\n\nI would like to request Project Translation Editor (PTE) access for the fa_IR locale for this plugin.
\nI am currently completing the Persian translation for the plugin, and I am following the official WordPress Persian glossary and translation guidelines. I am committed to maintaining the translation, reviewing future translation suggestions, and keeping it up to date with new releases to ensure high-quality localization.
\nProfile:
\nhttps://profiles.wordpress.org/daniyousefifar
Thank you for your time and consideration.
\n\n #fa_IR @daniyousefifar (@tobifjellner)\n\n\n#editor-requests
", "id": 16699330, "pubDate": "Sun, 19 Jul 2026 17:06:12 GMT", "whenReceived": "Sun, 19 Jul 2026 18:44:59 GMT", "whenUpdated": "Mon, 20 Jul 2026 00:07:05 GMT", "likes": [], "metadata": { "wpPostId": 68675, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68650", "title": "Translation Review / PTE Request for atshift Fields (Maintenance for Custom Field Suite)", "link": "https://make.wordpress.org/polyglots/2026/07/19/translation-review-pte-request-for-atshift-fields-maintenance-for-custom-field-suite/", "description": "Hello Polyglots team,
\nI am the plugin author/maintainer for atshift Fields (Maintenance for Custom Field Suite).
\n\nhttps://wordpress.org/plugins/atshift-fields-maintenance-for-custom-field-suite/\n\n\nI have imported translation suggestions for the plugin strings into Stable and Development for the locales below. For non-Japanese locales, these are imported suggestions from the bundled translation files in the release package, so please review and adjust them according to each locale’s glossary and style guide.
\n— ca
\n— de_DE
\n— es_ES
\n— fa_IR
\n— fr_FR
\n— hu_HU
\n— it_IT
\n— nl_NL
\n— pl_PL
\n— pt_BR
\n— ru_RU
\n— tr_TR
\n— zh_CN
\n— zh_TW
\n— ko_KR
\n— en_GB
For #ja, I have imported plugin strings and the Stable Readme / Development Readme strings. Since I maintain this plugin and can maintain the Japanese text going forward, I would also like to request PTE access for @shift for #ja on this plugin.
\n\n #ja @atshift \n\n\nThank you for your time.
\n#editor-requests
", "id": 16696688, "pubDate": "Sun, 19 Jul 2026 14:27:03 GMT", "whenReceived": "Sun, 19 Jul 2026 15:24:01 GMT", "whenUpdated": "Sun, 19 Jul 2026 15:24:01 GMT", "likes": [], "metadata": { "wpPostId": 68650, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68655", "title": "PTE Request for KXNotes Image Paste Optimizer", "link": "https://make.wordpress.org/polyglots/2026/07/19/pte-request-for-kxnotes-image-paste-optimizer/", "description": "Hello Polyglots,
\nI am the plugin author for KXNotes Image Paste Optimizer. I have submitted Simplified Chinese translations and would like to have them reviewed. I would also like to become a PTE for this plugin and locale.
\nPlugin: KXNotes Image Paste Optimizer
\nURL: https://wordpress.org/plugins/kxnotes-image-paste-optimizer/
There are currently 70 waiting translations in the Stable Readme project.
\nIf you have any questions, please comment here. Thank you!
\n#editor-requests
", "id": 16696689, "pubDate": "Sun, 19 Jul 2026 14:21:04 GMT", "whenReceived": "Sun, 19 Jul 2026 15:24:01 GMT", "whenUpdated": "Sun, 19 Jul 2026 15:24:01 GMT", "likes": [], "metadata": { "wpPostId": 68655, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68657", "title": "PTE Request for Concretus Copy Report", "link": "https://make.wordpress.org/polyglots/2026/07/19/pte-request-for-concretus-copy-report/", "description": "I am the plugin author of Concretus Copy Report – Copy Activity Insights. I have suggested Japanese translations for the Stable Readme and Development Readme and would like to maintain them going forward. Please review the pending translations and add my WordPress.org user @concretus as a Project Translation Editor for the following locale:
\nPlugin:
\n\nhttps://wordpress.org/plugins/concretus-copy-report/\n\n\nTranslations:
\n\nhttps://translate.wordpress.org/projects/wp-plugins/concretus-copy-report/stable-readme/ja/default/\n\nhttps://translate.wordpress.org/projects/wp-plugins/concretus-copy-report/dev-readme/ja/default/\n\n\n\n #ja – @concretus\n\n\nI have reviewed the Japanese translation style guide and glossary and will address any reviewer feedback.
\nThank you!
\n#editor-requests
", "id": 16696690, "pubDate": "Sun, 19 Jul 2026 14:20:00 GMT", "whenReceived": "Sun, 19 Jul 2026 15:24:01 GMT", "whenUpdated": "Sun, 19 Jul 2026 15:24:01 GMT", "likes": [], "metadata": { "wpPostId": 68657, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68631", "title": "PTE Request for CusRev", "link": "https://make.wordpress.org/polyglots/2026/07/18/pte-request-for-cusrev-2/", "description": "I’ve suggested translations for this CusRev plugin and would like to have them reviewed. I confirm that I’ve read the style guide and glossary for the locale.
\nPlugin: https://wordpress.org/plugins/customer-reviews-woocommerce/
\n\n #es_UY\n\n\n#editor-requests
", "id": 16685334, "pubDate": "Sat, 18 Jul 2026 17:04:52 GMT", "whenReceived": "Sat, 18 Jul 2026 18:29:16 GMT", "whenUpdated": "Sat, 18 Jul 2026 18:29:16 GMT", "likes": [], "metadata": { "wpPostId": 68631, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68634", "title": "PTE Request for Tanupom In-Place Converter for WebP", "link": "https://make.wordpress.org/polyglots/2026/07/18/pte-request-for-tanupom-in-place-converter-for-webp/", "description": "I am the plugin author of Tanupom In-Place Converter for WebP ( https://wordpress.org/plugins/tanupom-in-place-converter-for-webp/ ). I have suggested Japanese translations for this plugin and would like to maintain them going forward. Please add my WordPress.org user @tanupom as translation editor for the following locale:
\n\n #ja\n\n\nI have read the translation style guide and glossary for the locale.
\nThank you!
\n#editor-requests
", "id": 16685335, "pubDate": "Sat, 18 Jul 2026 17:04:39 GMT", "whenReceived": "Sat, 18 Jul 2026 18:29:16 GMT", "whenUpdated": "Sat, 18 Jul 2026 18:29:16 GMT", "likes": [], "metadata": { "wpPostId": 68634, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/training/feed/", "whenReceived": "Sat, 18 Jul 2026 11:06:33 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/training/feed/", "guid": "https://make.wordpress.org/training/?p=174416", "title": "Training Team Meeting Recap – 14th July 2026", "link": "https://make.wordpress.org/training/2026/07/18/training-team-meeting-recap-14th-july-2026/", "description": "This meeting followed this meeting agenda in GitHub. You can see conversations from the meeting in this Slack Log [Update Link]. (If you don’t have a Slack account, you can set one up.)
\n\n\n\nIntroductions and Welcome\n\n\n\nThere were 30 attendees: @rjekic, @vishitshah, @rfluethi, @ravigadhiyawp, @pooja-n, @noruzzaman, @sibokul, @webgrrrl, @sonaliprajapati, @dilip2615, @dhavalkapadane, @pravin1996, @ketanniruke, @freewebmentor, @andrewssanya, @sumitsingh, @rithika3, @mohkatz, @vasantrajput, @gohelkunjan(async), @vijay5696, @bigod(async), @jagirbahesh, @dhrumilk(async), @nitspatel(async), @palak678(async), @makanikaran(async), @harshjadav003(async), @valeriewandeler(async), @ursha(async)
\n\n\n\nLet’s welcome the new contributors who joined the Training channel this week:
\n\n\n\nNewcomers: @gohelkunjan, @saifullahnakiih, @dennistrama
\n\n\n\n\nWelcome all, let us know in the thread what brought you to the Training team and what you’d like to get involved with\n\n@rjekic – Welcome to this beautiful place! \n\n\n\n@sonaliprajapati – Welcome to Trainning Team\n\n\n\n@andrewssanya – Friends Welcome to the #training\n\n\n\n\n\n\nMeeting hosted by: @rjekic
\n\n\n\nNote Taker: @andrewssanya
\n\n\n\nNote Reviewer: @VasantRajput
\n\n\n\nWelcome! 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\nHere is our current note taker roster:
\n\n\n\n\nJuly 14th – @andrewssanya\n\n\n\nJuly 21st – @sibokul\n\n\n\nJuly 28th – @pravin1996\n\n\n\nAugust 4th @mohkatz\n\n\n\n\nImportant 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 to host Office Hours on July 26, 2026, but we need your help:\n\nDo you agree with the proposed date – July 26, 2026?\n\n\n\nWe need someone to host the meeting. Please state your interest and availability to host the Office Hours meeting\n\n\n\nWe need a note-taker for the Office Hours meeting. Please state your interest and availability.\n\n\n\nWe would like to know your opinion on how we can improve these meetings and encourage more members to join and participate actively. You can share your suggestion here or in this GitHub issue – Host Office Hours on July 26, 2026 #3535. Big thank you to everyone who has shared feedback so far!\n\n@sumitsingh – Who is planning to join the Office Hours meeting?I love to see some feedback from amazing team members \n\n\n\n@sibokul – I am very interested to join this office hours meeting\n\n\n\n@andrewssanya – I’ll be there.\n\n\n\n\n\nJust a reminder that the Office Hours meeting started as project that will strengthen the Training Team community and help you feel the Training Team vibe and realize that you are the important link in the chain \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 – Update Handbook : “Handbook” #3447\n\n\n\n\n\n\nLooking for volunteers\n\n\n\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 530 open issues. It would be great to get support in reviewing and reducing their number. You can help by:\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\n Let’s work together to clean up and keep the repository well-organized\n\n\n\n\nUpdates from last week’s Triage Squad session\n\n\n\n\nN/A\n\n\n\n\nOther News\n\n\n\n\nWe’re Looking for WCUS 2026 Contributor Day Table Leads! If you’re planning to attend and would like to represent the Training team, or know someone who would be a great fit, please submit a nomination. We’d love to have you join us!\n\n\n\nTraining Team Monthly update for June is published – make.wordpress.org/updates/…/training-team-update-july-5th-2026\n\n\n\nWordCamp Rajshahi Contributor Day Update: 10 contributors joined the Training Team table. Two new contributors started the Training Team Contributor Course, and @devmuhib009 supported the Team as a table lead.\n\n\n\nHow to Bring Your Community to Make WordPress Slack?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#meeting-recap, #training-team
", "id": 16679812, "pubDate": "Sat, 18 Jul 2026 09:50:35 GMT", "whenReceived": "Sat, 18 Jul 2026 11:06:33 GMT", "whenUpdated": "Sat, 18 Jul 2026 11:06:33 GMT", "likes": [], "metadata": { "wpPostId": 174416, "wpSiteId": 46403572 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Sat, 18 Jul 2026 00:22:07 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=88051", "title": "Help shape the next chapter of WP Credits: a developer track, and a pilot opportunity", "link": "https://make.wordpress.org/community/2026/07/17/help-shape-the-next-chapter-of-wp-credits-a-developer-track-and-a-pilot-opportunity/", "description": "WP Credits has been growing steadily, and now that we’ve proven the model works, it’s time to look at what the next evolution of the program could look like to better fit students’ needs. You can catch up on where things stand in the latest update post.
\nA pilot opportunity
\nA college in the US has expressed interest in the program, but their students need a developer-focused track. This is a great opportunity to pilot a dev-specific path within WP Credits.
\nWhere we need your help
\nThis is where the community comes in. If you’re a developer or a WP teacher, we’d love your input on what specific contributions could make up a dev track — what should students be working on to build real, job-relevant skills?
\nTaking it a step further: if we structure this as a 2–3 level path (beginner to advanced), what contributions would you place in each tier?
\nWe need at least the first tier defined by the end of August to stay on track for this pilot, so if you have thoughts, please share them soon.
\nNext steps
\nFollow along or get involved via the GitHub issue and in #wpcredits on Slack.
\nYour experience contributing and teaching WordPress is exactly what will make this pilot succeed, so thanks in advance for weighing in.
\nThe following people have contributed to writing/reviewing this post: @peiraisotta, @gomp, @webtechpooja, @francescodicandia. Thanks for reading!
\n#wpcredits
", "id": 16674071, "pubDate": "Fri, 17 Jul 2026 23:22:27 GMT", "whenReceived": "Sat, 18 Jul 2026 00:22:07 GMT", "whenUpdated": "Sat, 18 Jul 2026 00:22:07 GMT", "likes": [], "metadata": { "wpPostId": 88051, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Fri, 17 Jul 2026 22:28:35 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68621", "title": "PTE Request for WordSec", "link": "https://make.wordpress.org/polyglots/2026/07/17/pte-request-for-wordsec/", "description": "I am the plugin author for WordSec. Please add the following WordPress.org user as a Project Translation Editor (PTE) for the respective locales:
\n\nhttps://wordpress.org/plugins/wordsec/\n\n\n\n #tr_TR – @wordsec\n\n #de_DE – @wordsec\n\n #es_ES – @wordsec\n\n #fr_FR – @wordsec\n\n #pt_PT – @wordsec\n\n #ja – @wordsec\n\n #it_IT – @wordsec\n\n #nl_NL – @wordsec\n\n #pl_PL – @wordsec\n\n #ko_KR – @wordsec\n\n #id_ID – @wordsec\n\n #ru_RU – @wordsec\n\n #vi – @wordsec\n\n #zh_CN – @wordsec\n\n #ar – @wordsec\n\n #hi_IN – @wordsec\n\n #th – @wordsec\n\n #uk – @wordsec\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16672081, "pubDate": "Fri, 17 Jul 2026 21:36:29 GMT", "whenReceived": "Fri, 17 Jul 2026 22:28:35 GMT", "whenUpdated": "Fri, 17 Jul 2026 22:28:35 GMT", "likes": [], "metadata": { "wpPostId": 68621, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68625", "title": "PTE Request for AN|DES de BelleWeb", "link": "https://make.wordpress.org/polyglots/2026/07/17/pte-request-for-andes-de-belleweb/", "description": "Hello Polyglots team,
\nI am the plugin author for AN|DES de BelleWeb.
\nPlugin:
\n\nhttps://wordpress.org/plugins/andes-de-belleweb/\n\n\nTranslation project:
\n\nhttps://translate.wordpress.org/projects/wp-plugins/andes-de-belleweb/\n\n\n\n #es_ES @bellewebstudio (@nilovelez)\n\n\nI have translated the Stable Readme and the Stable plugin strings for Spanish (Spain). The Stable Readme has already been approved, and the Stable plugin strings are waiting for review.
\nCould you please review/approve the pending Spanish (Spain) translations, or assign me as PTE for this plugin so I can maintain the Spanish translations?
\nThank you.
\n#editor-requests
", "id": 16672082, "pubDate": "Fri, 17 Jul 2026 21:35:47 GMT", "whenReceived": "Fri, 17 Jul 2026 22:28:35 GMT", "whenUpdated": "Sat, 18 Jul 2026 08:27:51 GMT", "likes": [], "metadata": { "wpPostId": 68625, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://wordpress.org/news/podcast/feed/", "whenReceived": "Fri, 17 Jul 2026 19:09:36 GMT", "items": [ { "feedUrl": "https://wordpress.org/news/podcast/feed/", "guid": "https://wordpress.org/news/?p=21167", "title": "WordPress 7.0.2 Release", "link": "https://wordpress.org/news/2026/07/wordpress-7-0-2-release/", "description": "WordPress 7.0.2 is now available.\n\n\n\nThe 7.0.2 security release addresses one critical and one high severity security issue.
\n\n\n\nBecause this is a security release, it is recommended that you update your sites immediately. Due to the severity, the WordPress.org team have enabled forced updates via the auto-update system for sites running affected versions.
\n\n\n\nTo manually update you can visit your WordPress Dashboard, click “Updates”, and then click “Update Now”, or you can download WordPress 7.0.2 from WordPress.org. On sites that support automatic background updates, the update process will begin automatically.
\n\n\n\nSecurity updates included in this release\n\n\n\nThe 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\nA facilitated SQL injection issue reported as a team by TF1T, dtro, and haongo \n\n\n\nA REST API batch-route confusion and SQL injection issue leading to Remote Code Execution reported by Adam Kues at Assetnote / Searchlight Cyber\n\n\n\n\nFor more information on this release, please visit the HelpHub site.
\n\n\n\nBackports\n\n\n\n\nWordPress 6.9 is affected by both vulnerabilities. Version 6.9.5 has been released containing fixes for both.\n\n\n\nWordPress 6.8 is only affected by the first vulnerability. Version 6.8.6 has been released containing a fix.\n\n\n\nThe beta release of WordPress 7.1 is affected by both vulnerabilities. Version 7.1 beta2 has been released containing fixes for both.\n\n\n\nVersions of WordPress prior to 6.8 are not affected.\n\n\n\n\nCVE and GHSA references\n\n\n\n\nCVE-2026-60137 / GHSA-fpp7-x2x2-2mjf\n\n\n\nCVE-2026-63030 / GHSA-ff9f-jf42-662q\n\n\n\n\nThank you to these WordPress contributors\n\n\n\nThis release was led by John Blackbourn and Barry Abrahamson. In addition to the security researchers mentioned above, WordPress 7.0.2 would not have been possible without the significant contributions of the following people: Aaron Jorbin, Alex Concha, annezazu, Barry, David Baumwald, Dominik Schilling, Ehtisham Siddiqui, Joe Dolson, Joe Hoyle, John Blackbourn, Jonathan Desrosiers, Marius L. J., Matt Mullenweg, Mohammad Jangda, Peter Wilson, Sergey Biryukov, vortfu, Weston Ruter, plus representatives from Altis, Automattic, Bluehost, Cloudflare, GoDaddy, Hostinger, and WP Engine.
\n\n\n\n", "id": 16668166, "pubDate": "Fri, 17 Jul 2026 18:45:54 GMT", "whenReceived": "Fri, 17 Jul 2026 19:09:36 GMT", "whenUpdated": "Sat, 18 Jul 2026 01:44:46 GMT", "likes": [], "metadata": { "wpPostId": 21167, "wpSiteId": 14607090 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Fri, 17 Jul 2026 15:47:51 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68623", "title": "PTE Request for DentalZaikoMaker", "link": "https://make.wordpress.org/polyglots/2026/07/17/pte-request-for-dentalzaikomaker/", "description": "I am the plugin author for DentalZaikoMaker. I have submitted Japanese translations
\nfor the plugin’s readme and would like to be able to review and approve them.
\nPlease add the following WordPress.org user as translation editor:
The plugin is built for dental clinics and dental laboratories in Japan, so Japanese
\nis the only locale we target. Note that the plugin’s source strings are Japanese by
\ndesign (the UI ships in Japanese for the Japanese market), so the code project is not
\nthe target of this request — only the readme.
One thing I need to flag and apologise for: while trying to import the readme
\ntranslations I picked the wrong file and the wrong sub-project, and ended up
\nimporting about 1,150 “identity” strings (msgstr identical to the Japanese msgid)
\ninto “Development (trunk)”. They are all sitting as Waiting suggestions from
\n@creativestrategy24. They are harmless (identity strings change nothing even if
\napproved), but they are noise. I cannot reject my own suggestions as a regular
\ncontributor, so I would be grateful if you could remove them — or, once I have PTE
\nrights, I will reject all of them myself. Please do NOT approve them.
I have read the Japanese translation style guide and the glossary, and the submitted
\nreadme translations follow them. I am a native Japanese speaker and the author of the
\noriginal English readme, so I can confirm the translations against what the plugin
\nactually does.
If you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16663453, "pubDate": "Fri, 17 Jul 2026 15:18:01 GMT", "whenReceived": "Fri, 17 Jul 2026 15:47:51 GMT", "whenUpdated": "Sun, 19 Jul 2026 15:24:01 GMT", "likes": [], "metadata": { "wpPostId": 68623, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Fri, 17 Jul 2026 14:29:14 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=88041", "title": "Activity Tickets: self-service registration for Contributor Day and other side events feedback wanted", "link": "https://make.wordpress.org/community/2026/07/17/activity-tickets-self-service-registration-for-contributor-day-and-other-side-events-feedback-wanted/", "description": "Most WordCamps run free, capacity-limited extras alongside the main event – Contributor Day, a Social Dinner, a workshop. Those seats are meant for confirmed attendees, but CampTix has no built-in way to enforce that. So organizers improvise: a separate signup form anyone on the internet can fill in, a spreadsheet cross-checked against the attendee list by hand, or an honor system that quietly oversells the room. Non-attendees grab limited seats, organizers spend hours reconciling lists, and no-shows leave chairs empty that a real attendee could have used.
\n\n\n\nWe’ve built a CampTix addon that closes that gap, and before it goes to a pull request we’d like the community’s eyes on it especially from anyone who has run a Contributor Day or a side event and felt this pain firsthand.
\n\n\n\n\n\n\n\nThis has been asked for before\n\n\n\nThis isn’t a new idea. Issue #1371 “Tickets: Add the ability to handle secondary event tickets” – opened by a WCEU organizer in 2024 and discussed by CampTix maintainers – requests exactly this, and the addon meets all of that issue’s acceptance criteria. Along the way it also structurally resolves #598 (Contributor Day attendance stats – attendees of a side event become real CampTix attendees, so check-in and stats just work) and the side-event case of #623 (people no longer appear twice on the public Attendees page).
\n\n\n\n\n\n\n\nHow it works\n\n\n\nThe working name is activity tickets (more on the name below – it’s one of the things we want feedback on).
\n\n\n\nAn organizer creates the extras as ordinary CampTix tickets (price 0, quantity = capacity), then ticks which tickets are activity tickets under CampTix → Setup → Activity Tickets. Optionally, they can restrict which main tickets qualify. That’s the entire setup.
\n\n\n\nFrom then on, an activity ticket can only be registered by someone who is logged in with their WordPress.org account and already holds a confirmed main-event ticket from an earlier, completed order. Each person registers themselves, once per activity, and every activity registration is automatically linked to their main ticket.
\n\n\n\nWhat the attendee sees: buy a ticket → return to the Tickets page → register for the activities you want → done. Visitors who don’t qualify yet still see the activity tickets, with a notice explaining why they can’t register yet:
\n\n\n\n\n“Contributor Day can only be registered by attendees who already have an event ticket. Buy your ticket first, then come back to register.”
\n\n\n\n\nOn a later visit, tickets they already hold show an “Already registered” label instead of silently disappearing, and a notice up top lists everything they hold – with a manage link per ticket and an “Email me these links” action for anyone who lost their confirmation email.
\n\n\n\nWhat the organizer sees: attendee records show the link in both directions, the CSV/XML export gains “Activity of (main ticket #)” and “Activity tickets” columns, and – if the Admin Flags addon is active – the main attendee is auto-flagged per held activity (e.g. activity-contributor-day) for filtering and integrations.
\n\n\n\n\n\n\n\nThe rules, in plain terms\n\n\n\nScenarioWhat happensSomeone without an event ticket tries to registerBlocked, with a clear message to buy a ticket first. Activity tickets are never purchasable in the same cart as a main ticket.A company account buys 5 main ticketsEach teammate confirms their own ticket, logs in, and registers their own activities. Nobody can bulk-grab limited seats.Someone tries to register twice for the same activityBlocked – one registration per person, per activity.The main ticket is refunded or cancelledAll linked activity registrations are released automatically and the seats return to the pool.A ticket changes hands (edited over to another person)Activity registrations are personal – they’re released back to the pool, and the new holder registers themselves.Contributor Day is capped at 50Capacity is enforced per activity ticket, exactly like any other CampTix ticket.The require-login addon is offThe feature fails safe: registrations are blocked and organizers see a notice explaining the dependency. (require-login is on by default for WordCamps.)\n\n\n\n\n\n\n\nWhere it stands\n\n\n\nThe addon is built and fully verified locally – not yet merged. It passes WordPress coding standards cleanly, a 54-test automated suite, and a 40-check live end-to-end run against a real WordCamp site setup, including on the newest supported PHP version. A pull request against wordcamp.org will follow this feedback round.
\n\n\n\n\n\n\n\nWhat we’d like from you\n\n\n\n1. The name. “Activity ticket” is the current working name (an earlier round of feedback ruled out “Companion ticket” – it reads as a guest/plus-one ticket). Does “Activity ticket” read right to you, and does it translate well for your community? Suggestions welcome – the name is display-only and easy to change.
\n\n\n\n2. Your stories. If you’ve run a Contributor Day, a Social Dinner, or any capacity-limited side event: does this flow match how your event actually works? What edge cases have you hit – transfers, speakers and volunteers, walk-ins, waitlists – that we should think about?
\n\n\n\nPlease share your thoughts in the comments here. Thanks for reading!
", "id": 16661462, "pubDate": "Fri, 17 Jul 2026 13:31:39 GMT", "whenReceived": "Fri, 17 Jul 2026 14:29:14 GMT", "whenUpdated": "Fri, 17 Jul 2026 14:29:14 GMT", "likes": [], "metadata": { "wpPostId": 88041, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Fri, 17 Jul 2026 12:27:02 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68615", "title": "Titel: PTE Request for Brainwerk SEO Suite", "link": "https://make.wordpress.org/polyglots/2026/07/17/titel-pte-request-for-brainwerk-seo-suite/", "description": "I am the plugin author for Brainwerk SEO Suite. Please add the following
\nWordPress.org user as translation editor for the respective locale:
Thank you!
\n#editor-requests
", "id": 16658925, "pubDate": "Fri, 17 Jul 2026 12:04:38 GMT", "whenReceived": "Fri, 17 Jul 2026 12:27:02 GMT", "whenUpdated": "Fri, 17 Jul 2026 22:28:35 GMT", "likes": [], "metadata": { "wpPostId": 68615, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68591", "title": "Translation Review and PTE Request for Braspin Chat", "link": "https://make.wordpress.org/polyglots/2026/07/16/translation-review-and-pte-request-for-braspin-chat/", "description": "Hello Polyglots Team,
\nI am the plugin author for Braspin Chat:
\n\nhttps://wordpress.org/plugins/braspin-chat/\n\nhttps://translate.wordpress.org/projects/wp-plugins/braspin-chat/\n\n\nI have submitted translations for the plugin and would like to request a review for the following #pt_BR and #es_ES
\nI would also like to request PTE status for the WordPress.org user @braspin for the Portuguese (Brazil) locale:
\n\n #pt_BR – @braspin\n\n\nThe plugin source strings are written in English and use the braspin-chat text domain. The Brazilian Portuguese plugin interface currently has all available strings translated.
\nFor Spanish, I am requesting a review by the locale team. I am not requesting PTE status for Spanish at this time.
\nPlugin author: @braspin
\nThank you!
\n#editor-requests
", "id": 16647064, "pubDate": "Thu, 16 Jul 2026 21:17:51 GMT", "whenReceived": "Thu, 16 Jul 2026 22:18:52 GMT", "whenUpdated": "Thu, 16 Jul 2026 22:18:52 GMT", "likes": [], "metadata": { "wpPostId": 68591, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68585", "title": "PTE Request for BEARS – Block Editor Accessibility Repair System", "link": "https://make.wordpress.org/polyglots/2026/07/16/pte-request-for-bears-block-editor-accessibility-repair-system/", "description": "I am the plugin author for BEARS – Block Editor Accessibility Repair System. My co-author has already created a translation for the locale hu_HU. Please add me as PTE in order to accept the translation suggestions.
\n\nhttps://wordpress.org/plugins/bears-accessibility/\n\n\n\n #hu_HU – @kristofvarga (@tobifjellner)\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16647065, "pubDate": "Thu, 16 Jul 2026 21:17:39 GMT", "whenReceived": "Thu, 16 Jul 2026 22:18:52 GMT", "whenUpdated": "Thu, 16 Jul 2026 23:59:11 GMT", "likes": [], "metadata": { "wpPostId": 68585, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68581", "title": "PTE Request for Ashplug Orders Report for Snappay", "link": "https://make.wordpress.org/polyglots/2026/07/16/pte-request-for-ashplug-orders-report-for-snappay/", "description": "I’ve suggested Persian translations for Ashplug Orders Report for Snappay and would like to have them reviewed.
\nI’m the plugin author and would also like to become a PTE for this plugin. I confirm that I’ve reviewed the Persian translation guidelines and glossary and will keep the terminology consistent.
\nName: Ashplug Orders Report for Snappay
\nPlugin URL: https://wordpress.org/plugins/ashplug-orders-report-for-snappay/
\nTranslation URL: https://translate.wordpress.org/projects/wp-plugins/ashplug-orders-report-for-snappay/
Best Regards.
\n#editor-requests
", "id": 16647066, "pubDate": "Thu, 16 Jul 2026 21:17:28 GMT", "whenReceived": "Thu, 16 Jul 2026 22:18:52 GMT", "whenUpdated": "Thu, 16 Jul 2026 22:18:52 GMT", "likes": [], "metadata": { "wpPostId": 68581, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68579", "title": "PTE Request for Invoice and Partial Payments for Woocommerce – easyCredit Business Services", "link": "https://make.wordpress.org/polyglots/2026/07/16/pte-request-for-invoice-and-partial-payments-for-woocommerce-easycredit-business-services/", "description": "I am the plugin author for easyCredit Invoice and Partial Payments plugin . We would like to help provide and maintain translations for our plugin in the following locale:
\n\nhttps://de.wordpress.org/plugins/wc-easycredit/\n\n\n\n #de_DE – @netzkollektiv @ratenkaufbyeasycredit (@tobifjellner)\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16647067, "pubDate": "Thu, 16 Jul 2026 21:17:17 GMT", "whenReceived": "Thu, 16 Jul 2026 22:18:52 GMT", "whenUpdated": "Thu, 16 Jul 2026 23:59:11 GMT", "likes": [], "metadata": { "wpPostId": 68579, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/test/feed/", "whenReceived": "Thu, 16 Jul 2026 13:47:59 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/?p=12508", "title": "Team Chat Agenda: 16th July, 2026", "link": "https://make.wordpress.org/test/2026/07/16/team-chat-agenda-16th-july-2026/", "description": "Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 16 July 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 meetingIf any of the above apply, please leave a comment below.
\n#test-chat-agenda
", "id": 16634952, "pubDate": "Thu, 16 Jul 2026 13:14:11 GMT", "whenReceived": "Thu, 16 Jul 2026 13:47:59 GMT", "whenUpdated": "Thu, 16 Jul 2026 13:47:59 GMT", "likes": [], "metadata": { "wpPostId": 12508, "wpSiteId": 255400204 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/2026/07/16/xpost-test-team-update-16-july-2026/", "title": "X-post: Test Team Update: 16 July, 2026", "link": "https://make.wordpress.org/test/2026/07/16/xpost-test-team-update-16-july-2026/", "description": "X-post from +make.wordpress.org/updates: Test Team Update: 16 July, 2026
", "id": 16634953, "pubDate": "Thu, 16 Jul 2026 12:14:31 GMT", "whenReceived": "Thu, 16 Jul 2026 13:47:59 GMT", "whenUpdated": "Thu, 16 Jul 2026 13:47:59 GMT", "likes": [], "metadata": { "wpPostId": 12507, "wpSiteId": 255400204 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Thu, 16 Jul 2026 10:28:09 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68556", "title": "PTE Request for [MirooCRM Sync for Contact Form 7]", "link": "https://make.wordpress.org/polyglots/2026/07/16/pte-request-for-miroocrm-sync-for-contact-form-7/", "description": "Hi Polyglots team,
\nI’m the author of the plugin “MirooCRM Sync for Contact Form 7”:
\nhttps://translate.wordpress.org/projects/wp-plugins/miroocrm-sync-for-contact-form-7/
I’d like to request PTE (Project Translation Editor) rights for the Italian
\nlocale (it_IT) for this plugin. I’m the plugin owner (Doozy Service Srl), and
\nthe Italian translation is ready to be reviewed/imported.
Thanks in advance!
\n#editor-requests
", "id": 16630584, "pubDate": "Thu, 16 Jul 2026 10:09:42 GMT", "whenReceived": "Thu, 16 Jul 2026 10:28:09 GMT", "whenUpdated": "Thu, 16 Jul 2026 10:28:09 GMT", "likes": [], "metadata": { "wpPostId": 68556, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68559", "title": "PTE Request for", "link": "https://make.wordpress.org/polyglots/2026/07/16/pte-request-for-23/", "description": "Minimum Order Notice for WooCommerce
\n\nhttps://wordpress.org/plugins/sohan-minimum-order-notice/\n\n\nI am the plugin author of Minimum Order Notice for WooCommerce plugin. Please add me as a translation editor for the following locales:
\n\n #bn_BD (@tobifjellner)\n\n\n#editor-requests
", "id": 16630585, "pubDate": "Thu, 16 Jul 2026 10:09:31 GMT", "whenReceived": "Thu, 16 Jul 2026 10:28:09 GMT", "whenUpdated": "Thu, 16 Jul 2026 23:59:11 GMT", "likes": [], "metadata": { "wpPostId": 68559, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68569", "title": "PTE Request for CatCode IBAN Smart Invoice", "link": "https://make.wordpress.org/polyglots/2026/07/16/pte-request-for-catcode-iban-smart-invoice/", "description": "Hello Polyglots! I am the plugin author of CatCode IBAN Smart Invoice ( https://wordpress.org/plugins/catcode-iban-smart-invoice/ ).
\nWe have imported complete Ukrainian translations for both the plugin (Stable) and the readme, and would like to have translation editor rights so the locale can go live. Please add my WordPress.org user as PTE:
\n\n #uk @catcodestudio (@tobifjellner)\n\n\nThe translations were written by a native Ukrainian speaker; the plugin targets the Ukrainian market (IBAN / Monobank / Privat24 payments). Thank you!
\n#editor-requests
", "id": 16630586, "pubDate": "Thu, 16 Jul 2026 10:09:21 GMT", "whenReceived": "Thu, 16 Jul 2026 10:28:09 GMT", "whenUpdated": "Thu, 16 Jul 2026 23:59:11 GMT", "likes": [], "metadata": { "wpPostId": 68569, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68571", "title": "PTE Request for Translate Rocket", "link": "https://make.wordpress.org/polyglots/2026/07/16/pte-request-for-translate-rocket/", "description": "Hello Polyglots! I am the plugin author for Translate Rocket ( https://wordpress.org/plugins/translate-rocket/ ). I have suggested translations for the locales below (Italian already has 578 waiting strings) and would like to be able to review and approve them as PTE. Please add my WordPress.org user @federicodev as translation editor for the following locales:
\nName: Translate Rocket
\nURL: https://wordpress.org/plugins/translate-rocket/
If you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16630587, "pubDate": "Thu, 16 Jul 2026 10:09:06 GMT", "whenReceived": "Thu, 16 Jul 2026 10:28:09 GMT", "whenUpdated": "Thu, 16 Jul 2026 10:28:09 GMT", "likes": [], "metadata": { "wpPostId": 68571, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68561", "title": "PTE Request for Rank Math SEO", "link": "https://make.wordpress.org/polyglots/2026/07/15/pte-request-for-rank-math-seo-6/", "description": "As a translator who meets the Polyglots General Expectations, I would
\nlike to request PTE status for Rank Math SEO Forms for the Arabic locale
I have submitted translation suggestions for this project, which can
\nbe reviewed here:
https://translate.wordpress.org/projects/wp-plugins/seo-by-rank-math/stable/ar/default/
\nMy WordPress.org username: mokhtarbsaid
\nNotes:
\nWhile completing the remaining Arabic translation of the Rank Math SEO plugin, I noticed a number of issues in the existing translated strings. I wanted to bring them to your attention so they can be corrected and the overall quality of the Arabic translation can be improved.
I have already corrected them in my local copy. Below is a categorized list of the issues:
\n-Spelling mistakes (around 38 occurrences): Most of them involve using hamzat al-qat’ where hamzat al-wasl should be used, such as «إستخدام», «إستيراد», «إختيار», and «إستبدال». The correct forms are: استخدام, استيراد, اختيار, and استبدال. There are also obvious typos such as «تضيمن» (تضمين), «توجية» (توجيه), and «إرشيفات» (أرشيفات)
\n\nTranslating the brand name (around 30 occurrences): The translation uses “رانك ماث” and “رانك ماث برو”. However, according to the WordPress glossary, brand names should remain in Latin script, and the same translation file already uses Rank Math in Latin script in most places. The correct approach is to standardize them as Rank Math and Rank Math PRO\n\n\n\nOverly literal machine translation: The phrase “Rank Math’s SEO Score” was translated as “تصنيف الرياضيات SEO النتيجة”, which is a word-for-word translation of the brand name (Rank = تصنيف, Math = الرياضيات). The correct translation is: “درجة السيو من Rank Math”.\n\n\nUnsuitable literal translation: The term Breadcrumb was translated as “فتات الخبز” in five places. A more appropriate translation is “مسار التنقل”, which is also the term used elsewhere in the same translation file
\nI will pay close attention to these issues while completing the remaining translation and will do my best to improve
\nThank you
\n\n #ar (@tobifjellner)\n\n\n#editor-requests
", "id": 16616146, "pubDate": "Wed, 15 Jul 2026 17:08:34 GMT", "whenReceived": "Wed, 15 Jul 2026 18:25:35 GMT", "whenUpdated": "Thu, 16 Jul 2026 10:28:09 GMT", "likes": [], "metadata": { "wpPostId": 68561, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://wordpress.org/news/podcast/feed/", "whenReceived": "Wed, 15 Jul 2026 17:21:15 GMT", "items": [ { "feedUrl": "https://wordpress.org/news/podcast/feed/", "guid": "https://wordpress.org/news/?p=20987", "title": "WordPress 7.1 Beta 1", "link": "https://wordpress.org/news/2026/07/wordpress-7-1-beta-1/", "description": "WordPress 7.1 Beta 1 is ready for download and testing!
\n\n\n\nThis beta release is intended for testing and development only. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, use a test environment or local site to explore the new features.
\n\n\n\nHow to Test WordPress 7.1 Beta 1\n\n\n\nYou can test WordPress 7.1 Beta 1 in any of the following ways:
\n\n\n\nWordPress Beta Tester PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. Select the “Bleeding edge” channel and “Beta/RC Only” stream.Direct DownloadDownload the Beta 1 version (zip) and install it on a WordPress website.Command Line (WP-CLI)Use this WP-CLI command: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\nHow important is your testing?\n\n\n\nTesting for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute – whether or not you have experience. Details on what to test in WordPress 7.1 are available here.
\n\n\n\nIf you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bug report, you can do so via WordPress Trac. You can also check your issue against this list of known bugs.
\n\n\n\nCurious about testing releases in general and how to get started? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
\n\n\n\nWordPress 7.1 will include new features that were previously only available in the Gutenberg plugin. Learn more about Gutenberg updates since WordPress 7.0 in the What’s New in Gutenberg posts for versions 22.7, 22.8, 22.9, 23.0, 23.1, 23.2, 23.3, 23.4, 23.5 and 23.6.
\n\n\n\nWhat’s new in WordPress 7.1?\n\n\n\nWordPress 7.1 delivers a more complete set of styling controls, a smoother media experience, and a more personalized admin experience. Notes have evolved to add inline notes with @mentions and rich text formatting that make asynchronous feedback feel more powerful. New styling features unlock long requested features to style how blocks look across screen sizes and to style interactive states, all without writing custom CSS. Various client side media improvements means better format support, improved performance, and more resilient uploads when adding media to your site. A new inline cropping tool brings a fresh and more robust experience to editing images. Finally, the admin experience becomes easier to navigate with an ever present admin bar in the editors, improvements to the command palette, and various quality of life improvements. Underneath it all, developers get an expanding set of APIs to build on, and site owners get better support for a truly global audience.
\n\n\n\nNew suite of Notes features\n\n\n\nNotes continue to grow into a fuller collaboration experience, making asynchronous feedback between teams faster and more expressive.
\n\n\n\nText Formatting: Notes now support inline formatting like bold, italic, code, links and adding emoji; each with a respective keyboard shortcut, so feedback reads clearly without breaking your flow.
\n\n\n\n@mentions: Type “@” in a Note to pull up a searchable list of collaborators and tag someone directly, so feedback points at the right person without leaving the sidebar.
\n\n\n\nLeave notes anywhere: Start more than one conversation on the same block instead of folding every comment into a single thread, making it easier to track distinct pieces of feedback.
\n\n\n\nInline notes: Leave a note on a text selection instead of on an entire block.
\n\n\n\nShow more / show less: Long notes now collapse by default with a toggle to expand them, keeping the margin tidy while you write.
\n\n\n\nStyle it your way, on any screen\n\n\n\nWordPress 7.1 takes a major step toward built-in responsive design and interactive styling, letting you achieve looks that once required writing custom CSS.
\n\n\n\nResponsive styling: Define how a block looks at different screen sizes directly in the editor, for both Global Styles and individual blocks without the need of writing custom CSS.
\n\n\n\nViewport breakpoint customization: Theme authors can now define their own responsive breakpoints in theme.json, giving more flexibility for how responsive controls behave on a given site.
\n\n\n\nInteractive state styling: Style how blocks respond to interaction, like a button changing color on hover or focus, using a standardized set of controls for both Global Styles and individual block instances.
\n\n\n\nA smoother media experience\n\n\n\nUploading, editing, and browsing media keeps getting more capable and more reliable.
\n\n\n\n\nClient-side media processing: Image and media processing moves into the browser, now with broader format support that includes HEIC (the default format for iPhone photos), UltraHDR, AVIF and WebP support built in, plus GIF-to-video conversion for lighter, more efficient files. Uploads are also more resilient, with a progress indicator and automatic retries if your data connectivity drops off.\n\n\n\nNew Media Editor Modal: A dedicated modal for editing images replaces the inline cropping tool, bringing cropping, rotation, and metadata editing together in one streamlined workflow.\n\n\n\nSmarter galleries: Gallery blocks can automatically pull in and sort media already attached to the current post, cutting down on manual set-up.\n\n\n\nView attached images: After you upload images to a post, the inserter will automatically surface them in a new Attached images section to make it easier to find relevant images.\n\n\n\nInfinite scrolling by default: The Media Library grid view now loads additional items automatically as you scroll, rather than requiring a click on “Load more” especially handy for sites that handle large media libraries. This can be disabled under your user profile.\n\n\n\n\nA more personal, more navigable admin\n\n\n\nThese meaningful upgrades make the WordPress admin easier to move around in and more consistent with how you like to work.
\n\n\n\n\nPersistent toolbar (Omnibar): The admin toolbar now travels with you into the Site Editor and Block Editor, with a series of polish improvements throughout.\n\n\n\nCommand palette improvements: Moving through the dashboard and editor with the command palette (Ctrl/Cmd+K) is more refined to make finding what you need even faster! Now results are grouped into Recent, matching and Suggestions sections instead of one flat list.\n\n\n\nAdmin color scheme in the Site Editor: The Site Editor now reflects your chosen admin color scheme instead of always using a fixed background.\n\n\n\nDataViews and DataForms iterations: Continued refinement of the components behind managing lists of posts, pages, patterns, and templates, alongside the forms used to edit them.\n\n\n\nExcerpts in the Posts list: The Posts list view now shows a short excerpt for each entry, making it easier to identify the post you’re looking for without opening it.\n\n\n\nVisual revisions: This release adds a picker activity layout for browsing history in more detail, clearly labeled autosaves in the timeline, and an autosave notice that opens straight into the visual revisions view. Global Styles revisions get a small polish too, swapping the active style’s text label for a badge.\n\n\n\nA dedicated Identity section: Site identity settings like your title, tagline, and icon are now live in their own clearly labeled section of the Site Editor, making them easier to find and update.\n\n\n\nOn This Day Widget: A new widget resurfaces what you published on this date in past years, right on your dashboard. A small nudge to look back on what you’ve written, and a reason to write something new today.\n\n\n\nAllow Changing Comment Parent: Fixing a misthreaded comment used to mean editing the database directly. WordPress 7.1 adds an editable “In reply to” control to the Edit Comment screen, letting you pick a new parent from a dropdown of the post’s other comments. It’s scoped to the same post, so this is about untangling threads, not moving comments across posts.\n\n\n\n\nNew blocks and block-level enhancements\n\n\n\nWordPress 7.1 release brings a handful of block refinements that give more control with fewer steps.
\n\n\n\n\nPlaylist Block: A new block for adding a collection of audio files to a post or page, with an optional waveform visualization that shows the audio’s shape as it plays; a more visual way to present podcasts, music, or audio content without using any third-party plugins.\n\n\n\nTabs Block: A new block for organizing content into clickable tabbed panels instead of showing everything at once. It’s a cleaner way to present related content without overwhelming the page.\n\n\n\nBackground gradients: Background gradients and background images no longer conflict. The gradient used to get silently overridden by the image, but now they combine and display together. This fix extends beyond the Group block to Verse, Accordion, Pullquote, Post Content, and Quote block.\n\n\n\nHTML block editable content: The HTML block now supports editable nested blocks. This is great to use for AI-generated content, which often arrives as raw HTML.\n\n\n\n“Mark as decorative” for images: A new toggle on the Image block lets you hide purely decorative images from screen readers for a better accessibility experience.\n\n\n\nSmarter shortcode handling: Pasting or converting a shortcode into the Embed block now creates a proper Embed block instead of leaving raw shortcode text behind, and the Shortcode block gains block-specific transforms of its own.\n\n\n\n\nBuilt for a global audience\n\n\n\nWordPress 7.1 continues work to make Core reflect the full diversity of its worldwide community, with progress toward supporting Unicode email addresses so usernames, slugs, and email addresses can better represent users everywhere.
\n\n\n\nBuilt for developers\n\n\n\nWordPress 7.1 continues to expand the foundation developers build on.
\n\n\n\n\nAbilities API expansion: Continued refinement of the Abilities API with improved querying, filtering, and input validation, giving developers and AI tooling a more reliable foundation to build on.\n\n\n\nBlock Bindings for list items: Block Bindings now extend to List Item, making it possible to connect more block content to dynamic data sources without custom code.\n\n\n\nCustom icon registration: New functions let plugin and theme authors register their own icons for the Icons block for use throughout the block editor.\n\n\n\nEnforced iframed editor: The post editor now always runs inside an iframe, isolating the editing canvas from admin styles for more predictable rendering. Blocks using Block API v2 or lower should be updated to v3 for compatibility.\n\n\n\nwordpress/theme stabilization: Introduces design tokens and a stable React ThemeProvider to provide a more consistent, customizable foundation for WordPress admin interfaces.\n\n\n\nConnectors authentication improvements: The Connectors screen now also supports username and application-password login – a more familiar way to connect plugins and services. This release also closes a security gap where browsers could auto-suggest saved credentials into the API key field.\n\n\n\n\nWith so much in progress for WordPress 7.1 Beta 1, this is still only the beginning; expect continued refinement with each Beta and RC release ahead of the final release on August 19, 2026 at WordCamp US 2026.
\n\n\n\n\n\n\n\nJust for you: a Beta 1 haiku:\n\n\n\nSeeds of Seven-One,
Notes, styles, media, and tools—
Test, and watch them bloom.
Props to @benjamin_zekavica, @amykamala, @wildworks, @adamsilverstein, @annezazu, @fushar, @jorgefilipecosta, @joedolson for proofreading and review.
", "id": 16614407, "pubDate": "Wed, 15 Jul 2026 15:53:33 GMT", "whenReceived": "Wed, 15 Jul 2026 17:21:15 GMT", "whenUpdated": "Thu, 23 Jul 2026 19:50:23 GMT", "likes": [], "metadata": { "wpPostId": 20987, "wpSiteId": 14607090 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/test/feed/", "whenReceived": "Wed, 15 Jul 2026 11:08:17 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/test/feed/", "guid": "https://make.wordpress.org/test/?p=12271", "title": "Help Test WordPress 7.1", "link": "https://make.wordpress.org/test/2026/07/15/help-test-wordpress-7-1/", "description": "WordPress 7.1 — the second major release of 2026 — is coming fast. The official release will launch August 19, 2026.
\n\n\n\nWith 7.1 Beta 1 slated for release on the July 15th, your help testing is vital to ensuring a stable and reliable release that continues to benefit WordPress users across the globe.
\n\n\n\nEarly testing is critical.
\n\n\n\nEarly testing helps identify bugs, usability issues, and compatibility concerns while there’s still time to address them.
\n\n\n\nThen at launch, you’ll find your testing might have led to an improvement you can see and feel.
\n\n\n\nGot a few minutes? A few hours? Every bit of testing makes a big difference — possibly, the difference between a new feature landing in 7.1 or not.
\n\n\n\nStay informed!
\n\n\n\nThe WordPress 7.1 release schedule page has everything you need to know about the latest pre-release builds and milestones.
\n\n\n\nFor real-time updates, you can follow discussions and find collaboration opportunities in the #core-test and #core channels in the Making WordPress Slack. You might want to join both channels!
\n\n\n\nAlso, you are more than welcome at every upcoming release party, testing session, and test scrub throughout the release cycle and beyond.
\n\n\n\nThank you!
\n\n\n\nDid you know you’re already a hero? Anything you do — even just reading this post — helps shape WordPress 7.1 into the strongest, most polished release ever.
\n\n\n\nAnd with the new features coming in 7.1, you’ll help make it a blockbuster release for the entire community.
\n\n\n\n Testing TipsHow to test WordPress Beta Versions WP-PlaygroundA Local Site on your computerWP-CLITesting tickets in the browser General Testing ChecklistKey Features to TestCollaborationNew Notes featuresDesign & InterfaceResponsive stylingInteractive states stylingPersistent ToolbarDedicated Identity sectionAdmin color scheme reflected in the Site EditorCommand palette sections and Recently usedChoose which block styles to apply globallyMediaClient-side media processingMedia Editor ModalSmarter galleriesDashboardVisual Revisions improvementsUntitled posts show an excerpt in the Posts list“On This Day” dashboard widgetRe-parent a comment from the Edit Comment screenBlocksPlaylist blockTabs blockBackground gradients now work alongside background imagesImage block — “Mark as decorative” toggleEditable blocks inside the Custom HTML blockEmbed block — embed shortcode transformShortcode block — block-specific transformsWhat to NoticeWhere to Report FeedbackChangelog\n\n\n\n Testing Tips\n\n\n\nYou don’t need to be a certified software tester or QA professional, or any kind of expert, to help test WordPress.
\n\n\n\nSimply using WordPress as you would every day (on a test installation, of course!) can help identify any bottlenecks and bugs that a WordPress user may encounter. through processes that mimic your daily projects, workflows, and experiments and report any findings.
\n\n\n\nOr if you feel compelled, push WordPress to its limits. Try to break things. Have five editors in wp-admin at once, have someone relentlessly reload the home page, step outside standard practices and use WordPress in unexpected ways.
\n\n\n\nNotice something unexpected? Run into a bug? Is a feature not behaving the way you thought it would? Please consider reporting it to the Alpha/Beta area of the support forums, or directly to WordPress Trac if you are comfortable writing a reproducible bug report.
\n\n\n\nNot sure what the expected behavior should be? No problem! Join the conversation in the #core-test channel on the Making WordPress Slack, where contributors and developers are always happy to help. New tester? You have the global WordPress community at your service. Everyone in it is happy to welcome and support you. You’re also welcome and encouraged to join the #core-test Slack channel and ask questions about testing!
\n\n\n\nAgain — every report, question, or observation you submit makes a difference, and helps improve WordPress for hundreds of millions of users. Testing is a valuable way to contribute to the WordPress project, and testers are included in release credits on the final release.
\n\n\n\nRecommendations for Testing WordPress Beta/RC Versions:
\n\n\n\n\nTest the Core Features that Matter to You: Use your site the way you usually do. For instance, if you’re a blogger, running a social platform, or managing an e-commerce store, run your tests through those specific scenarios.\n\n\n\nSet up a staging site (ask your hosting provider if this is new to you). Do not test or update your live site with a beta version for testing; your users might see any issues that come up.\n\n\n\nUpdate WordPress in the staging environment. Keep using your site as normal. \n\n\n\nTake note of anything you experience after the update. Log any errors, alerts or strange behavior during your testing process, and the steps you took when you encountered the issue. \n\n\n\nUse the General Checklist below to verify everything works as you’d expect.\n\n\n\n\nHow to test WordPress Beta Versions \n\n\n\nYou can test WordPress Beta versions in several ways. Some are fast and easy; some let you run sophisticated tests on the latest backend features.
\n\n\n\nAll of them keep your live websites safe from the effects of any issues you find:
\n\n\n\nWP-Playground\n\n\n\nPlayground is a fast and easy way to spin up a test site — without setting up a full environment. Get started testing right away on WordPress Playground.
\n\n\n\nA Local Site on your computer\n\n\n\nSoftware like Local or wp-env lets you build a full WordPress site on your computer — no internet required.
How to set up your site:
Follow this guide for more detailed instructions.
\n\n\n\nWP-CLI\n\n\n\nAre you most at home in the command line? WP-CLI lets you install a WordPress beta version in record time.
\n\n\n\nSteps:
\n\n\n\n\nCreate a local WordPress site however you like to do it. Wait for the notification that your site is ready.\n\n\n\nOpen your terminal and navigate to the root directory of your WordPress installation.\n\n\n\n\nRun the following command to update to the latest beta version:
\n\n\n\nwp core update --version=7.1-beta1\n\n\n\nOr
\n\n\n\nwp core update --version=7.1-RC1\n\n\n\n(Replace the version number as needed, such as --version=7.1-beta2.)
\n\n\n\nWith WP-CLI, you can install several different versions and switch between them easily. That makes it much easier to test specific builds and compare them.
\n\n\n\nA Staging Site on your host
\n\n\n\nYou can build a staging site for your production/live site and test it with the WordPress beta/RC version — without affecting your live site.
\n\n\n\nThat way, you’ll be sure everything works the way it should — long before WordPress 7.1 lands in your production/live environment.
\n\n\n\nTesting Patches
\n\n\n\nA patch is a quick and smaller update that fixes security or other bugs. Maybe you don’t need to test an entire version of WordPress, but you do want to test one or more patches to see if a bug is fixed.
\n\n\n\nIn that case, you’ll need a specific local WordPress development environment.
\n\n\n\nFollow these instructions to set it up.
\n\n\n\nTesting tickets in the browser \n\n\n\nDo you have a particular PR in the wordpress-develop or gutenberg repo that you’d like to test in the browser?
\n\n\n\nYou can use Playground for that, and test any core tickets you like — without installing any software on your system. Just use these links:
\n\n\n\n\nhttps://playground.wordpress.net/wordpress.html \n\n\n\nhttps://playground.wordpress.net/gutenberg.html \n\n\n\n\nGeneral Testing Checklist\n\n\n\nWant to see how well your site runs on the very latest version of WordPress? Here’s a checklist that should give you an idea — and won’t take all day.
\n\n\n\nUse one of the methods above to set up your testing site, and update to the latest Beta/RC version.
\n\n\n\nEnable debugging in wp-config.php, and update your theme and plugins.
\n\n\n\n\nDid any plugins or themes deactivate automatically after the update?\n\n\n\nCheck the WordPress Site Health tool. Did you find any new warnings or issues?\n\n\n\nCheck templates and patterns, and then actual posts and pages, for layout problems. Are all the elements lined up properly? Is spacing correct?\n\n\n\nTest links and permalinks to ensure there are no 404 or other errors.\n\n\n\nDo design elements, images, and media look the way they should? Do media files load and play properly? How does the audio sound?\n\n\n\nHow are the sitemap and robots.txt files working?\n\n\n\nCan users at every permission level get to the admin dashboard without errors? Does each level show the right tools, and do they work?\n\n\n\nDoes your site have custom blocks? Add content to a new block. Edit it. Now edit a block that already has content.\n\n\n\nCreate a new post:\n\nAdd content.\n\n\n\nCopy some text and paste it.\n\n\n\nAdd a few different kinds of media files. \n\n\n\nSave the post and watch the console for any issues.\n\n\n\n\n\nCreate a new page.\n\nAdd content. \n\n\n\nOpen it in several different browsers. Does it look and feel right in each? Does the page function properly in each?\n\n\n\n\n\nOpen the browser’s developer tools. Check each tab, plus the console, for errors, warnings, or notices. Check any visible CSS or JavaScript for unexpected changes.\n\n\n\nCheck the error log file for notices, warnings, and errors — especially fatal errors.\n\n\n\nHave you set up scheduled posts or automated tasks (like backups)? Can you find them in the admin? Do they run on schedule? Do they work?\n\n\n\nCheck integrated services like payment gateways or analytics. Do they still connect? Do they execute? \n\n\n\nOpen your site in different browsers and make sure all functionalities work as expected — beyond the ones you checked on pages earlier.\n\n\n\nCheck site performance: page loading, API calls, database requests. You might want to check this on a few devices in real life. \n\n\n\nAlso, every browser has tools that let you simulate a variety of network conditions. How does your updated site handle low bandwidth?\n\n\n\nTest accessibility basics: keyboard navigation, contrast, screen-reader behavior — whatever assistive technology you have on hand.\n\n\n\nCheck your forms — contact forms, checkout forms, login forms, and more. Can you fill all the fields? Submit and clear? Does the data end up in the right place?\n\n\n\nCan you upload media? Edit images? Does gallery functionality work properly?\n\n\n\nCheck your theme. Does the basic theme look right? Did theme customizations — in the Site Editor, or the Customizer in Classic themes — change in the upgrade? Or did they sail through perfectly?\n\n\n\n\nKey Features to Test\n\n\n\nCollaboration\n\n\n\nNew Notes features\n\n\n\nNotes let people leave feedback directly in the editor. WordPress 7.1 makes them much richer: notes on specific words or across multiple blocks, rich text inside notes, @mentions, multiple note threads on the same block, a show more/less toggle for long notes, and a toolbar button that puts starting a note within easy reach.
\n\n\n\nTesting Steps
\n\n\n\n\nCreate a new post and add a few paragraphs of content.\n\n\n\nSelect some text inside a paragraph.\n\n\n\nOpen the block toolbar (or the ⋮ options menu) and choose Add note (look for a note/comment icon).\n\n\n\nType a note and save it. Confirm the note appears anchored to the text you selected.\n\n\n\nReply to your own note and confirm the reply shows in the thread.\n\n\n\nAdd formatting using keyboard shortcuts — there’s no visible toolbar. Select text and press ⌘/Ctrl + B (bold), ⌘/Ctrl + I (italic), or ⌘/Ctrl + K (link). To get code formatting, type text wrapped in backticks (`like this`). Confirm the formatting is kept after saving. (Formatting is intentionally limited to bold, italic, link, and code.)\n\n\n\nStart a second, separate thread on the same block and confirm both threads are tracked independently.\n\n\n\nAdd a note that spans more than one block and confirm it’s tracked correctly.\n\n\n\nAdd a long note and confirm the show more/less toggle collapses and expands it.\n\n\n\n@mention another user in a note and confirm the mention is inserted correctly.\n\n\n\n\nExpected:
\n\n\n\nNotes attach to the right content; replies, mentions with notifications, multiple threads per block, keyboard formatting, and the show more/less toggle all work as described.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow #76316 for more details.
\n\n\n\nDesign & Interface\n\n\n\nResponsive styling\n\n\n\nStyle a block differently for tablet and mobile directly in the editor — without custom CSS. Turn on Responsive editing from the device-preview dropdown, switch to Tablet or Mobile, and the change is saved only for that breakpoint.
\n\n\n\nDedicated Call for Testing post: Call for Testing: Responsive Styling — follow it for the full set of scenarios (resize handles + device view syncing, per-viewport styles, the viewport badge, hidden-on-device blocks, front-end checks, and notes for plugin/theme developers).
\n\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Reference PR #75121 for more details.
\n\n\n\nInteractive states styling\n\n\n\nYou can now style a Button’s interactive states — hover, focus, and active — without writing a single line of CSS. For example, a button that changes color the moment you hover over it.
\n\n\n\nThere are two layers to this:
\n\n\n\n\nGlobal Styles: set hover, focus, and active styles once and they apply to every Button across the whole site. \n\n\n\nIndividual block instance: A single Button can have its own hover, focus, and active styles that leave every other button untouched. Note that per-instance pseudo states are currently supported by the Button block only; other blocks don’t expose them yet.\n\n\n\n\nTesting Steps
\n\n\n\nGlobal Styles first (applies to all buttons)
\n\n\n\n\nOpen the Site Editor and go to Styles → Blocks → Button. \n\n\n\nUse the States selector to switch to the Hover state. \n\n\n\nWith Hover active, set a different Background and Text color (and any other styles you like). \n\n\n\nRepeat for the Focus and Active states, giving each its own look. \n\n\n\nSave the styles. \n\n\n\nOn the frontend, hover, focus, and click a button and confirm the correct styles appear for every button on the site.\n\n\n\n\nThen an individual Button instance (applies to one button only)
\n\n\n\n\nAdd two or more Button blocks to a post or page. \n\n\n\nSelect one of them and open its Styles settings. \n\n\n\nOpen the state selector in the block card header (a small three-dot menu) and switch to Hover. \n\n\n\nChange a style for example the Background color. The canvas should update immediately; toggle Show state on canvas off and on to confirm it’s previewing the hover look live. \n\n\n\nSave and view the post on the frontend. Hovering that one button should use the styles you set, while the other buttons stay unchanged. \n\n\n\nSwitch to Focus and Active and repeat, giving that single button its own states. \n\n\n\nReset the hover styles for that instance and confirm the other states and the global styles are unaffected.\n\n\n\n\nExpected:
\n\n\n\nGlobal hover, focus, and active styles apply to all buttons site-wide, while per-instance styles apply to only the selected button. The two layers combine sensibly, resetting one layer doesn’t disturb the others, and Show state on canvas previews the state in the editor without you having to actually hover.
Testing Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow issue #38277 (per-instance support landed in PR #76491) for more details.
\n\n\n\nPersistent Toolbar\n\n\n\nThe admin toolbar now appears inside the Post Editor and the Site Editor too — previously it disappeared in the Site Editor — along with a few visual refreshes: the home icon becomes your site icon (when set), your profile avatar is circular, and the command palette icon is removed from the editor toolbar.
\n\n\n\nTesting Steps
\n\n\n\n\nSet a Site Icon (Site Editor → Design → Identity, or Settings) if you haven’t already.\n\n\n\nOpen the Post Editor (edit any post) and confirm the admin bar is visible at the top.\n\n\n\nOpen the Site Editor (Appearance → Editor) and confirm the admin bar is visible there too (it used to disappear).\n\n\n\nConfirm the admin bar’s home item shows your site icon, not the old dashicon (with no site icon set, it falls back to the default icon).\n\n\n\nConfirm your profile avatar is a circle, not a square.\n\n\n\nConfirm there is no command palette icon in the editor toolbar anymore, and that the palette still opens with Cmd/Ctrl + K.\n\n\n\nSwitch your Admin Color Scheme (Users → Profile) and confirm the admin bar in both editors follows the scheme.\n\n\n\nResize to a narrow / mobile width and confirm the admin bar still looks correct in the editors.\n\n\n\n\nExpected:
\n\n\n\nThe admin bar is visible in both the Post and Site Editor, shows the site icon (when set) and a circular avatar, no longer carries the command-palette icon in the editor toolbar, and follows the chosen admin color scheme.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow issue #79036 for more details.
\n\n\n\nDedicated Identity section\n\n\n\nThe Design → Identity panel now lets you edit your Site Title and Site Tagline right alongside the existing Site Logo and Site Icon no need to jump over to Settings. Changes update the matching Site Title and Site Tagline blocks live in the editor preview.
\n\n\n\nTesting Steps
\n\n\n\n\n Open the WordPress Dashboard and go to Appearance → Editor.\n\n\n\nIn the Site Editor, go to Design → Identity. \n\n\n\nConfirm four fields appear in order: Site Title, Site Tagline, Site Logo, Site Icon. \n\n\n\nConfirm the description text below each field is the same size and style. \n\n\n\nEdit the Site Title and watch the Site Title block update in the preview. \n\n\n\nEdit the Site Tagline and watch the Site Tagline block update in the preview. \n\n\n\nClick Save and confirm all edited fields appear in the save panel. \n\n\n\nReload the editor and confirm your changes persisted.\n\n\n\n\nExpected:
\n\n\n\nSite Title and Site Tagline can be edited from the Identity panel, the preview updates as you type, and changes save and persist correctly.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow #76261 for more details.
\n\n\n\nAdmin color scheme reflected in the Site Editor\n\n\n\nThe Site Editor now follows your chosen WordPress admin color scheme instead of always showing a fixed dark interface. The sidebar and surrounding chrome pick up your scheme’s colours, while the editing canvas stays white for readability.
\n\n\n\nTesting Steps
\n\n\n\n\nGo to Users → Profile and pick an Admin Color Scheme (e.g. Modern, Blue, Coffee, Ectoplasm, Midnight, Ocean, Sunrise).\n\n\n\nOpen the Site Editor (Appearance → Editor).\n\n\n\nConfirm the sidebar and interface chrome reflect the chosen colour scheme, not a fixed dark background.\n\n\n\nConfirm the editing canvas / content area stays white and readable.\n\n\n\nSwitch to a different admin colour scheme and confirm the Site Editor updates to match.\n\n\n\nResize the browser to a narrow / mobile width and confirm the themed sidebar and white content still look correct.\n\n\n\n\nExpected:
\n\n\n\nThe Site Editor chrome matches your admin colour scheme across all schemes and at mobile widths, while the content canvas stays white.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow #78397 for more details.
\n\n\n\nCommand palette sections and Recently used\n\n\n\nThe command palette (Cmd/Ctrl + K) is easier to navigate: commands are now grouped into sections: Suggestions, Recent, and Results. The commands you use are remembered under Recent, saved to your user preferences. The palette is also a bit wider for easier scanning.
\n\n\n\nTesting Steps
\n\n\n\n\nIn the editor, press Cmd/Ctrl + K to open the command palette.\n\n\n\nRun a few different commands and close the palette.\n\n\n\nReopen it and confirm a Recently used section shows the commands you just ran.\n\n\n\nStart typing and confirm results are grouped into recent, suggested, and matching sections.\n\n\n\nReload the page (or start a new session) and confirm recently used commands persist.\n\n\n\nCheck the layout is readable and easy to scan.\n\n\n\n\nExpected:
\n\n\n\nCommands are grouped into clear sections, recently used commands persist under Recent and the palette is easier to scan.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow #75616 for more details.
\n\n\n\nChoose which block styles to apply globally\n\n\n\nThe block inspector’s Apply globally action used to be all-or-nothing: one click pushed every style you’d changed on the block into Global Styles, with no way to see what was about to change or to leave part of it behind.
\n\n\n\nWordPress 7.1 adds a review step. Apply globally now opens a modal that lists each changed style on its own row, showing the current value next to the new value, with a checkbox for each. Every row is selected by default, so you can deselect the ones you don’t want and apply only the styles you meant to. Anything you deselect stays as a local override on the block and isn’t pushed or cleared.
\n\n\n\nTesting Steps
\n\n\n\n\nAdd a Paragraph block to a post and select it.\n\n\n\nIn the block inspector (right sidebar), change a few different styles on the block — for example make the text uppercase, set a text colour, add some padding, and set a border colour.\n\n\n\nOpen the Advanced panel in the block inspector and click Apply globally.\n\n\n\nConfirm a modal opens (it no longer applies everything immediately), and that it lists one row per changed style, each showing the current value → the new value, with all rows checked by default.\n\n\n\nDeselect one row, then click Apply.\n\n\n\nConfirm only the checked styles were pushed to Global Styles, and that a snackbar appears. Click Undo in the snackbar and confirm the previous state is restored.\n\n\n\nConfirm the style you deselected is still set on the block as a local override — it should not have been pushed, and it should not have been cleared either.\n\n\n\nOpen Apply globally again and confirm the modal now lists only the style you didn’t push.\n\n\n\nDeselect every row and confirm the Apply button is disabled.\n\n\n\nReopen the modal and dismiss it with Cancel, the close (×) button, and the Escape key. Each time, confirm nothing changes on the block or in Global Styles.\n\n\n\nOn a block with no changed styles, confirm the Apply globally button is disabled.\n\n\n\nResize the browser to a narrow / mobile width and confirm the modal still displays correctly.\n\n\n\n\nExpected:
\n\n\n\nApply globally opens a review modal listing each changed style with its current and new values, all selected by default. Only the selected styles are pushed to Global Styles; deselected styles remain as local overrides on the block and are neither pushed nor cleared. Apply is disabled with nothing selected and when there are no changes to push, cancelling changes nothing, and Undo restores the previous state.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow PR #79839 for more details.
\n\n\n\nMedia\n\n\n\nClient-side media processing\n\n\n\nWhen you upload an image in the editor, your browser now decodes, resizes, and encodes all sub-sizes locally (via wasm-vips) before sending them to the server — with support for AVIF, WebP, HEIC, UltraHDR, JPEG XL, and GIF→video conversion. Browsers and devices that can’t handle it silently fall back to the existing server-side path. (Chromium browsers only; requires more than 2 GB RAM and a decent connection.)
\n\n\n\nDedicated Call for Testing post: Call for Testing: client-side media processing — follow it for the full set of scenarios (baseline uploads, HEIC from iPhone, modern output formats, Ultra HDR, JPEG XL, GIF→video, batch/concurrent uploads, resilience, fallback paths, extensibility, and low-powered devices).
\n\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here (tag them `[Feature] Client Side Media`). Follow #76756 for more details.
\n\n\n\nMedia Editor Modal\n\n\n\nA new Media Editor Modal replaces the old inline image cropper, bringing cropping, rotation, flip, zoom, and metadata editing together in one streamlined place. It opens from the Crop button on the Image block (and the Site Logo and Cover blocks).
\n\n\n\nDedicated Call for Testing post: Media Editor Modal: call for testing —follow it for the full set of flows (basic crop, details/metadata editing, preserving custom block alt/caption values, keyboard, and touch gestures).
\n\n\n\nTesting Steps
\n\n\n\n\nIn a post or page, add an Image block and upload or choose an image.\n\n\n\nClick the Crop button in the block toolbar and confirm a modal opens (instead of the old inline cropper).\n\n\n\nTry a freeform crop — drag the handles — and confirm it works.\n\n\n\nTry an aspect-ratio crop (a locked ratio) and confirm the crop constrains to that ratio.\n\n\n\nUse Rotate (and fine rotation / snap, where shown) and confirm the image rotates.\n\n\n\nUse Flip and confirm the image flips.\n\n\n\nUse the Zoom controls (+ / −) and confirm the image zooms within the crop frame.\n\n\n\nToggle the crop handles on/off, if available, and confirm they behave.\n\n\n\nEdit the metadata (for example, alt text or caption) in the modal, then Save.\n\n\n\nConfirm the cropped/edited image is applied to the block and persists after saving the post and reloading.\n\n\n\nRepeat from the Site Logo and Cover block crop buttons to confirm the modal opens there too.\n\n\n\n\nExpected:
\n\n\n\nThe Media Editor Modal opens from the Crop button, supports freeform and aspect-ratio cropping, rotation, flip, zoom, and metadata editing, saves the result back to the image, and is reachable from the Image, Site Logo, and Cover blocks.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow #73771 for more details.
\n\n\n\nSmarter galleries\n\n\n\nGallery blocks get smarter: a new Dynamic Gallery mode automatically displays all the media attached to the current post — in the editor and on the frontend — much like the classic gallery shortcode did. You can also manage a post’s attached images from a new Attachments category in the media inserter.
\n\n\n\nTesting Steps
\n\n\n\n\nCreate a post and upload a few images to it, so they become “attached” to the post.\n\n\n\nAdd a Gallery block and, in its empty/placeholder state, choose the Use attached images option (Dynamic Gallery).\n\n\n\nConfirm the gallery automatically shows all the images attached to the post.\n\n\n\nSave and confirm the same images appear on the frontend.\n\n\n\nOpen the block’s Source settings, change the sort order, and confirm the images re-order accordingly.\n\n\n\nConvert the Dynamic Gallery to a static gallery and confirm you can now add, remove, or reorder individual images.\n\n\n\nOpen the media inserter (the Media tab in the inserter) and find the new Attachments category.\n\n\n\nConfirm it lists the images attached to the current post.\n\n\n\nUse Attach to add an image and Detach to remove one, and confirm the Dynamic Gallery updates to match.\n\n\n\n\nExpected:
\n\n\n\nA Dynamic Gallery auto-displays all media attached to the post (editor and frontend), respects the sort setting, and can be converted to a static gallery. The media inserter’s Attachments category lists the post’s images and lets you attach/detach, which the Dynamic Gallery then reflects.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow issue #77117 for more details.
\n\n\n\nDashboard\n\n\n\nVisual Revisions improvements\n\n\n\nThe Visual Revisions view (from 7.0) lets you compare and restore past revisions visually, right in the editor. WordPress 7.1 polishes how autosaves fit into it. The autosave notice’s “View the autosave” now opens the visual revisions view (autosave selected, changes highlighted) instead of the classic screen, and restoring the autosave dismisses the notice — it falls back to the classic screen when visual revisions are off (e.g. classic meta boxes). The revisions timeline also shows an “Autosave” badge on autosave rows — visually and for screen readers — so they’re easy to tell apart from regular revisions.
\n\n\n\nTesting Steps
\n\n\n\n\nEdit a published post, change some content, and trigger a server autosave (wait for it, or run wp.data.dispatch( ‘core/editor’ ).autosave() in the console). Reload without saving.\n\n\n\nOn the autosave notice, click “View the autosave” and confirm the visual revisions view opens with the autosave selected and its changes highlighted (no page reload).\n\n\n\nClick Restore and confirm the autosave content is applied and the notice disappears.\n\n\n\nOn a post with visual revisions disabled (e.g. classic meta boxes), confirm “View the autosave” falls back to the classic revisions screen.\n\n\n\nOpen a post with both revisions and a recent autosave, open the revisions screen, and confirm the autosave row shows an “Autosave” badge (regular rows don’t), announced to screen readers too.\n\n\n\n\nExpected:
\n\n\n\n“View the autosave” opens the visual revisions view (falling back to the classic screen when visual revisions are off) and restoring dismisses the notice; autosave rows in the timeline are clearly labelled “Autosave” while regular revisions aren’t.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow #79120 (PR #79947, PR #79950) for more details.
\n\n\n\nUntitled posts show an excerpt in the Posts list\n\n\n\nPosts and pages with no title used to show only “(no title)” in the list table, making untitled items hard to tell apart. In Compact view, WordPress 7.1 now appends up to 15 words of the post’s trimmed excerpt after “(no title)” — so untitled posts are identifiable at a glance.
\n\n\n\nTesting Steps
\n\n\n\n\nCreate a few posts with no title and different opening content (plain text, blocks, an image). Go to Posts → All Posts in Compact view.\n\n\n\nConfirm each untitled row shows “(no title)” followed by the first part of its content (up to 15 words, ending in an ellipsis), in a lighter weight than a normal title. A post whose content starts with only an image should show just “(no title)”.\n\n\n\nAdd a post with a title and confirm no excerpt is appended — the feature only applies to untitled posts.\n\n\n\nSwitch to Extended view and confirm the trimmed excerpt is not appended (the full excerpt already shows on its own line there). Switch back to Compact and confirm it returns.\n\n\n\nCreate an untitled password-protected post and confirm it shows only “(no title)” — no excerpt.\n\n\n\nRepeat on Pages; trash an untitled post and confirm the excerpt still shows next to “(no title)” (the title isn’t linked in Trash, as expected).\n\n\n\nConfirm the list still sorts, searches, and paginates correctly, and that Quick Edit / Bulk Edit still work for untitled posts.\n\n\n\n\nExpected: In Compact view, untitled posts and pages show “(no title)” plus a trimmed excerpt; titled and password-protected posts don’t; Extended view, Trash, sorting, and Quick/Bulk Edit all still behave correctly.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow Trac #65022 (PR #11553) for more details.
\n\n\n\n“On This Day” dashboard widget\n\n\n\nA new “On This Day” dashboard widget shows posts published on today’s date in previous years — a look back at what was published on this day one, two, or more years ago. It only appears on your Dashboard when there are matching posts; otherwise it stays hidden by default (though it’s still listed under Screen Options). It shows published posts from all authors, grouped by year.
\n\n\n\nTesting Steps
\n\n\n\n\nSign in to wp-admin and open the Dashboard.\n\n\n\nIf today’s date has no posts from previous years, confirm the “On This Day” widget does not display by default — it is hidden (it’s still registered under Screen Options, but stays hidden until there is a matching post).\n\n\n\nPublish a post with its date set to today’s month and day in a previous year (for example, set the publish date to one year ago today).\n\n\n\nReload the Dashboard and confirm the “On This Day” widget now appears, with that year shown as a heading and the post listed under it.\n\n\n\nConfirm each post is a link that opens its permalink.\n\n\n\nIf a shown post was written by another user, confirm it displays “by [author name]” — posts written by you show no author label.\n\n\n\nAdd a few more posts for today’s date across different previous years and confirm they are grouped by year, newest year first (up to 10 posts).\n\n\n\nConfirm a post dated today this year (same month/day, current year) does not show — only previous years count.\n\n\n\nConfirm a post from a different month or day does not show.\n\n\n\n\nExpected:
The widget does not display by default when there are no matching posts (it is hidden). It appears only when published posts exist for today’s date in previous years, listing them grouped by year (newest first), from all authors, each linking to its permalink and showing “by [author]” only for posts written by others.
Testing Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow Trac #65116 for more details.
\n\n\n\nRe-parent a comment from the Edit Comment screen\n\n\n\nThe Edit Comment screen now lets you change which comment a reply is “In reply to” or set it to None to make it a top-level comment using a new dropdown in the Save box. Previously this couldn’t be done from the admin at all.
\n\n\n\nTesting Steps
\n\n\n\n\nOn a post with threaded comments, go to wp-admin → Comments and click Edit on a reply.\n\n\n\nIn the Save box, click Edit next to “In reply to:” and pick a different comment from the dropdown (the comment itself and its own replies are left out, so you can’t create a loop).\n\n\n\nClick OK, then Update.\n\n\n\nView the post on the frontend and confirm the comment is now nested under the new parent.\n\n\n\nEdit it again, set “In reply to:” to None, Update, and confirm it appears as a top-level comment.\n\n\n\n\nExpected: You can change a comment’s parent (or clear it to top-level) from the Edit Comment screen, and the new threading shows on the frontend.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow Trac #65570 (PR #12406) for more details.
\n\n\n\nBlocks\n\n\n\nPlaylist block\n\n\n\nThe Playlist block plays back a list of audio tracks with an interactive waveform player and a track list. Add your audio files and play them right in the editor and on the frontend, and customise the waveform and track list from the block settings. It’s made up of Playlist → Playlist track (one per track).
\n\n\n\nTesting Steps
\n\n\n\n\nAdd a Playlist block and upload a few audio files (e.g. MP3s). Confirm a track is added for each file, with a waveform player and a track list.\n\n\n\nPress play and confirm audio plays; click another track in the list and confirm it switches. Save and view on the frontend, and confirm playback works there too.\n\n\n\nIn the block settings, open the Waveform panel and switch the Visualization style (Bars, Mirror, Line, Blocks, Dots, Seekbar). Confirm the waveform updates in the editor and on the frontend.\n\n\n\nSet a waveform color and a waveform background color (try the gradient options too) and confirm they render in both the editor and the frontend.\n\n\n\nToggle the track-list options — Show tracklist, Show images (album-art thumbnails), Show artists, Show numbers, and Show track length — and confirm each shows or hides correctly.\n\n\n\nTurn on Show play button artwork and confirm the track’s artwork appears inside the play button.\n\n\n\nChange the font size in the typography settings and confirm it applies to the track list and the current track.\n\n\n\nSet a background color, padding/margin, and border on the block and confirm they apply in the editor and on the frontend.\n\n\n\n\nExpected:
\n\n\n\nAudio plays back in the editor and on the frontend; the waveform’s visualization style, colors, and background render correctly; the track-list toggles (tracklist, images, artists, numbers, track length) and play-button artwork all work; and the block’s color, spacing, border, and typography styling apply consistently across editor and frontend.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow the PR #80203 and the iteration issue #77421 for more details.
\n\n\n\nTabs block\n\n\n\nThe Tabs block shows a row of clickable tab labels above a set of content panels — click a tab to bring its panel into view. It’s made up of Tabs → Tab List (the tab buttons) and Tab Panels → Tab Panel (one panel per tab). The labels and panels stay automatically synchronised, so adding, removing, or reordering a tab updates its matching panel too.
\n\n\n\n
Testing Steps
Expected:
Tabs and panels stay synchronised, global Tab List styles apply to the tab buttons (overridable per instance, block gap excepted), tabs and panels are linked by correct IDs (custom IDs respected), and the block follows the W3C tabs pattern — focusable with Tab, navigable with arrows, activated with Enter, and announced by screen readers.
Testing Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow PR #80163 and the tracking issue #73230 for more details.
\n\n\n\nBackground gradients now work alongside background images\n\n\n\nBackground gradients and background images no longer conflict. The gradient used to get silently overridden by the image; now they combine and display together. This applies to the Group, Verse, Accordion, Pullquote, Post Content, and Quote blocks.
\n\n\n\nTesting Steps
\n\n\n\n\nAdd one of the supported blocks – for example, a Group block with some content inside.\n\n\n\nIn Styles, set a background image on the block.\n\n\n\nOn the same block, also set a background gradient.\n\n\n\nConfirm both the image and the gradient show together in the editor, with neither cancelling the other out. \n\n\n\nSave and view on the front end; confirm both render together. \n\n\n\nRepeat on at least one other supported block (Verse, Accordion, Pullquote, Post Content, or Quote) and try a couple of different gradient/image combinations.\n\n\n\n\nExpected:
\n\n\n\nEach supported block – Group, Verse, Accordion, Pullquote, Post Content, and Quote – can display a background image and a background gradient at the same time, in both the editor and on the front end.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow PR #75859, #79391, #79840, #79841, #79842, #79843 for more details.
\n\n\n\nImage block — “Mark as decorative” toggle\n\n\n\nThe Image block has a new “Mark as decorative” toggle that hides an image from screen readers. Use it for purely decorative images (backgrounds, flourishes) so assistive technology skips them an improved experience for screen-reader users.
\n\n\n\nTesting Steps
\n\n\n\n\nAdd an Image block and choose an image.\n\n\n\nOpen the block’s Settings sidebar and find the “Mark as decorative” toggle.\n\n\n\nTurn it on.\n\n\n\nInspect the image’s markup and confirm it gets an empty alt (or role=”presentation” / aria-hidden, depending on output) so screen readers ignore it.\n\n\n\nView the post on the frontend and confirm the decorative markup is present there too.\n\n\n\nTurn the toggle off again, add meaningful alt text, and confirm the image is announced to screen readers once more.\n\n\n\n\nExpected:
\n\n\n\nWith the toggle on, the image is hidden from screen readers (empty/presentation alt); with it off and alt text set, the image is announced normally.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow PR #78064 for more details.
\n\n\n\nEditable blocks inside the Custom HTML block\n\n\n\nThe Custom HTML block can now keep editable blocks inside an otherwise static HTML structure (powered by a new innerContent block support). This is ideal for AI-generated or hand-built markup, where most of the HTML stays as-is but you mark just some parts a paragraph, an image — as editable. The editable inner blocks sit at their exact position in your markup but are locked: they can’t be moved, removed, or inserted, and they offer no alignment controls.
You add an editable block by writing its block delimiter inside the Custom HTML’s code, for example <!-- wp:paragraph -->…<!-- /wp:paragraph -->.
Testing Steps
\n\n\n\n\nAdd a Custom HTML block to a post or page, then open its Edit HTML modal.\n\n\n\nPaste this code — it has a Paragraph block delimited inside static HTML — and click Update: <div class=\"banner\"><h1>Static heading</h1><!-- wp:paragraph --> <p>Editable paragraph</p> <!-- /wp:paragraph --><footer>Static footer</footer></div>\n\n\n\nConfirm the paragraph renders at its position inside the static markup and is editable in place (click into it and type).\n\n\n\nConfirm the paragraph cannot be moved or removed (no up/down movers, no Delete in its options menu) and offers no alignment controls.\n\n\n\nOpen the block’s inspector and confirm the inner blocks list appears, acting as a navigation aid to the editable parts.\n\n\n\nSave the post and reload the editor: the saved markup should be identical to what you entered, and your paragraph edit persists at its position.\n\n\n\nView the post on the frontend and confirm the full structure renders (the heading, the editable paragraph, and the footer).\n\n\n\nRegression check: create a plain Custom HTML block with normal static content, edit and save it the markup should be unchanged. Note that scripts no longer run in the editor canvas preview (styles still apply), although they still run on the frontend.\n\n\n\n\nExpected: Delimited blocks become editable in place inside the Custom HTML block, are locked against moving/removing/inserting, appear in the inspector’s inner-blocks list, and the saved markup stays byte-identical to what you entered. Plain static Custom HTML blocks remain unaffected.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow PR #79115 for more details.
\n\n\n\nEmbed block — embed shortcode transform\n\n\n\nPasting or converting an embed shortcode now produces a proper Embed block instead of leaving raw shortcode text behind.
\n\n\n\nTesting Steps
\n\n\n\n\nOpen Post editor \n\n\n\nSwitch to code editor.\n\n\n\nUse an embed shortcode like the one shown in the screenshot. \n\n\n\nSwitch back to the visual editor.\n\n\n\nClick on the “Convert to blocks” toolbar button on the classic editor.\n\n\n\nApply the transform and confirm the embed previews in the editor.\n\n\n\nConfirm the shortcode is correctly transformed to the appropriate embed block.\n\n\n\n\n\n\n\n\nExpected:
\n\n\n\nembed convert cleanly into Embed blocks that preview in the editor and render on the frontend.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow PR #77937 for more details.
\n\n\n\nShortcode block — block-specific transforms\n\n\n\nWhen the text inside a Shortcode block matches a registered shortcode (like gallery, audio, or video), the editor now offers a transform into the comparable block, making it much easier to modernise old shortcode-based content.
\n\n\n\nTesting Steps
\n\n\n\n\nAdd a Shortcode block containing a known shortcode.\n\n\n\nUse a supported shortcode like the one shown in the screenshot below.\n\n\n\nConfirm a transform option appears to convert it to the matching block (Gallery / Audio / etc.).\n\n\n\nApply the transform.\n\n\n\nConfirm the new block renders the same content.\n\n\n\nSave and view on the frontend to confirm the output matches the original shortcode’s result.\n\n\n\n\n\n\n\n\nExpected:
\n\n\n\nMatching shortcodes offer a one-click transform to the equivalent block, and the converted block renders the same content on the frontend.
\n\n\n\nTesting Instructions:
\n\n\n\n\t\t\n\t\t\t \n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\n\nIf you encounter any issues or unexpected behaviour while testing, please log them here. Follow PR #77944 for more details.
\n\n\n\nWhat to Notice\n\n\n\nWhile testing, keep an eye on:
\n\n\n\n\nCould you find all the features? Could you figure out how to use them just from the interface?\n\n\n\nHow did the workflows feel? Smooth and logical? Or were some slow, confusing, or broken?\n\n\n\nDid you notice visual regressions in the editor, admin screens, or frontend?\n\n\n\nHow did patterns, templates, and site editor changes behave when you changed style variations, or themes?\n\n\n\nDid you test any assistive devices or on-device accessibility settings (focus order, keyboard traps, missing labels, reduced‑motion, contrast settings)? How did the feature work under those conditions?\n\n\n\nDo you see PHP notices, warnings, or deprecations in logs or the debug console that weren’t there before? Did any show up on the front end, where visitors might see?\n\n\n\n\nMake notes of anything that feels off—even if you’re not sure it’s a bug.
\n\n\n\nWhere to Report Feedback\n\n\n\nPlease share everything that stands out — as a problem or a plus, or anything in between: issues, suggestions, and whatever else you find significant.
\n\n\n\nChoose any of these options:
\n\n\n\n\nPost in the #core-test & #core channel in the Making WordPress Slack to discuss issues in real time.\n\n\n\nCreate a trac ticket at https://core.trac.wordpress.org/ for WordPress Core issues.\n\n\n\nOpen a GitHub issue in the Gutenberg repository for editor‑related bugs.\n\n\n\n\nInclude as much detail as you can in your report:
\n\n\n\n\nWordPress version (e.g. 7.1‑beta1 or 7.1‑RC1).\n\n\n\nPHP version and database type/version.\n\n\n\nTheme and active plugins.\n\n\n\nExact steps to reproduce the issue.\n\n\n\nScreenshots, screen recordings, and any error messages/logs you could capture.\n\n\n\n\nChangelog\n\n\n\n1.0.0 – Initial Post
1.0.1 – Added a review step to Apply Globally.
Props to @nikunj8866 for creating several feature testing guides and videos, and to @amykamala, @krupajnanda, @annezazu, and @nikunj8866 for the pre-publish review of this post.
\n#7-1, #call-for-testing, #core, #release-field-guide
", "id": 16605011, "pubDate": "Wed, 15 Jul 2026 09:42:08 GMT", "whenReceived": "Wed, 15 Jul 2026 11:08:17 GMT", "whenUpdated": "Mon, 27 Jul 2026 14:17:50 GMT", "likes": [], "metadata": { "wpPostId": 12271, "wpSiteId": 255400204 }, "ctLikes": 0, "enclosure": { "url": "https://videos.files.wordpress.com/lb628FM1/admin-color-scheme-reflected-in-the-site-editor.mp4", "type": "video/mp4", "length": 18555413 } } ] }, { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "whenReceived": "Wed, 15 Jul 2026 06:16:45 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/accessibility/feed/", "guid": "https://make.wordpress.org/accessibility/?p=17556", "title": "Accessibility Team Meeting Agenda: July 16, 2026", "link": "https://make.wordpress.org/accessibility/2026/07/15/accessibility-team-meeting-agenda-july-16-2026/", "description": "This is the proposed agenda for the bi-weekly Accessibility Team meeting on Thursday, July 16, 2026 15:00 UTC
\n\n\n\nAnnouncements \n\n\n\n\nWordPress 7.1 Beta1 Release (scheduled for today – 15th July) The release party starts at 15:00 UTC.\n\n\n\nGuide to WCUS 2026\n\n\n\nWordPress 7.0.1 Maintenance Release\n\n\n\n\nProposed Discussion\n\n\n\nReview the working groups listed on the Get Involved page (some contacts/groups may be outdated, with Meta Working Group listed twice), and discuss consolidating them into 3 groups – General, Documentation, and a new Accessibility-ready Program group to make things more effective. (ref)
\n\n\n\nUpdates from the working group\n\n\n\n\nDocumentation\n\n\n\nGeneral\n\n\n\nGutenberg\n\n\n\nThemes\n\n\n\n\nOpen floor\n\n\n\nIf you want to have a topic added to the agenda, please mention it in the comments of this post.
\n\n\n\nThe 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": 16598672, "pubDate": "Wed, 15 Jul 2026 05:27:03 GMT", "whenReceived": "Wed, 15 Jul 2026 06:16:45 GMT", "whenUpdated": "Wed, 15 Jul 2026 06:16:45 GMT", "likes": [], "metadata": { "wpPostId": 17556, "wpSiteId": 29901991 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/hosting/feed/", "whenReceived": "Wed, 15 Jul 2026 06:20:57 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/hosting/feed/", "guid": "https://make.wordpress.org/hosting/?p=183493", "title": "Hosting Team Meeting Agenda 2026-07-15", "link": "https://make.wordpress.org/hosting/2026/07/15/hosting-team-meeting-agenda-2026-07-15/", "description": "Next Meeting\n\n\n\nThe next meetings will be in the #hosting channel on Wednesday, July 15, 2026 at 0900 UTC and Wednesday, July 15, 2026 at 1800 UTC.
\n\n\n\nAgenda\n\n\n\n\n7.0.1 is out and available for download\n\n\n\n7.1 Beta 1 release on July 15th\n\n\n\nNew 7.1 Dev Note: Consistent navigation in WordPress 7.1 with persistent toolbar\n\n\n\nGuide to WCUS 2026\n\n\n\nTickets/PRs\n\n\n\n\n\nOpen Floor\n\n\n\nIdeas or suggestions\n\n\n\nAnything else? Please leave a comment with any additions or suggestions for the meeting.
\n\n\n\nprops to @jazzs3quence for reviewing this post
\n\n\n\n\n#agenda, #hosting, #hosting-community, #meetings, #weekly-hosting-chat
", "id": 16598728, "pubDate": "Wed, 15 Jul 2026 03:02:21 GMT", "whenReceived": "Wed, 15 Jul 2026 06:20:57 GMT", "whenUpdated": "Wed, 15 Jul 2026 06:20:57 GMT", "likes": [], "metadata": { "wpPostId": 183493, "wpSiteId": 120824672 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 14 Jul 2026 20:21:32 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68534", "title": "PTE Request for Comptabilité et…", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-for-comptabilite-et/", "description": "PTE Request for Comptabilité et Export FEC for WooCommerce (French)
\nHello Polyglots team,
\nI am the plugin author of Comptabilité et Export FEC for WooCommerce.
\nI have just submitted the complete French translation: 105 strings
\n(63 for the readme, 42 for the plugin interface).
This plugin targets French e-commerce exclusively — it produces entries
\nfor the French chart of accounts and the FEC file required by French tax
\nlaw (article A. 47 A-1 du Livre des procédures fiscales). Its source
\nstrings are already written in French, and French is the only locale that
\nmatters for it.
I would like to be able to approve translations for my own plugin.
\n\nhttps://wordpress.org/plugins/compta-fec-for-woocommerce/\n\n\n\n #fr_FR – @studioferreiro\n\n\nThank you!
\n#editor-requests
", "id": 16590044, "pubDate": "Tue, 14 Jul 2026 19:22:28 GMT", "whenReceived": "Tue, 14 Jul 2026 20:21:32 GMT", "whenUpdated": "Tue, 14 Jul 2026 20:21:32 GMT", "likes": [], "metadata": { "wpPostId": 68534, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Tue, 14 Jul 2026 17:33:27 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124576", "title": "Performance Chat Summary: 14 July 2026", "link": "https://make.wordpress.org/core/2026/07/14/performance-chat-summary-14-july-2026/", "description": "The full chat log is available beginning here on Slack.
\n\n\n\nWordPress Performance Trac tickets\n\n\n\n\n@westonruter shared a late submission for inclusion in WordPress 7.1 and requested reviews for PR #12514, which provides a mechanism for hosting providers to change the default Speculative Loading eagerness and mode without requiring an mu-plugin.\n\n@swissspidy shared that Core was a bit hesitant in the past to introduce new constants, let alone environment variables, and asked whether this is something hosts could control with an mu-plugin instead.\n\n\n\n@westonruter replied that there is such an environment variable and constant for wp_get_environment_type().\n\n\n\n@westonruter shared that configuration of Realtime Collaboration was also being done via environment variables.\n\n\n\n@westonruter shared that the reason for the environment variable is explained in the Realtime Collaboration discussion, where a host may not be able to control all the PHP being used in a hosted site and hosts could potentially control the PHP being used but may not “manage” their hosted WordPress sites, so doing so would be a violation of sorts of what their customers expect.\n\n\n\n\n\n\nPerformance Lab Plugin (and other performance plugins)\n\n\n\n\n@westonruter shared that there are some new PRs that need reviewing, but has not had time to review them yet due to work on Core tickets and expressed hope that there would be more time available for reviews within the next week.\n\n\n\n\nOur next chat will be held on Tuesday, July 28, 2026 at 16:00 UTC in the #core-performance channel in Slack.
\n\n\n\n\n#core-performance, #hosting, #performance, #performance-chat, #summary
", "id": 16586173, "pubDate": "Tue, 14 Jul 2026 17:09:08 GMT", "whenReceived": "Tue, 14 Jul 2026 17:33:27 GMT", "whenUpdated": "Tue, 14 Jul 2026 17:33:27 GMT", "likes": [], "metadata": { "wpPostId": 124576, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 14 Jul 2026 15:20:39 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68531", "title": "PTE request for the Virtuaria…", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-for-the-virtuaria/", "description": "PTE request for the Virtuaria – Magalu Marketplace Integration
\nI am the author of the Virtuaria – Magalu Marketplace Integration plugin. We have several excellent translation editors and would like them to be able to approve translations for our plugin. Please add the following WordPress.org users as translation editors for their respective languages:
\n\nhttps://wordpress.org/plugins/virtuaria-magalu/\n\n\n\n #pt_BR – @viniciusvirtuaria\n\n\nThank you!
\n#editor-requests
", "id": 16582518, "pubDate": "Tue, 14 Jul 2026 14:55:46 GMT", "whenReceived": "Tue, 14 Jul 2026 15:20:39 GMT", "whenUpdated": "Tue, 14 Jul 2026 15:20:39 GMT", "likes": [], "metadata": { "wpPostId": 68531, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/docs/feed/", "whenReceived": "Tue, 14 Jul 2026 16:16:29 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/docs/feed/", "guid": "https://make.wordpress.org/docs/?p=108990", "title": "Documentation Team Summer Break: July 15 – August 31", "link": "https://make.wordpress.org/docs/2026/07/14/documentation-team-summer-break-july-15-august-31/", "description": "The Documentation team is taking a summer break starting July 15 and running through August 31. We’ll resume our regular weekly meetings on September 1.
\n\n\n\nWhat’s Continuing\n\n\n\nEven during the break, work doesn’t stop:
\n\n\n\n\nWordPress 7.1 documentation: work will continue as planned.\n\n\n\nOpen GitHub issues: the team will keep making progress on open items in the GitHub Issue tracker.\n\n\n\n\nWhat’s Changing\n\n\n\n\nNo weekly meetings for the duration of the break.\n\n\n\nInstead, our co-reps will open a weekly update thread in Slack each week, so everyone can stay in the loop without a scheduled call.\n\n\n\nReplies to comments and questions in Slack will be asynchronous, please allow some time for a response.\n\n\n\n\nQuestions?\n\n\n\nDrop a note in the Slack channel and someone will get back to you as soon as they can.
\n\n\n\nSee you back at regular meetings on September 1!
\n#docs-team
", "id": 16584021, "pubDate": "Tue, 14 Jul 2026 14:53:30 GMT", "whenReceived": "Tue, 14 Jul 2026 16:16:29 GMT", "whenUpdated": "Tue, 14 Jul 2026 16:16:29 GMT", "likes": [], "metadata": { "wpPostId": 108990, "wpSiteId": 31760022 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 14 Jul 2026 13:40:35 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68524", "title": "#pte-request Hi Polyglots, I’m the…", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-hi-polyglots-im-the/", "description": "Hi Polyglots,
\nI’m the author of Clarivo – AI Content Disclosure and I would like to request
\nPTE access for German so I can review and approve the translations for my own
\nplugin.
Plugin: https://wordpress.org/plugins/clarivo/
\nTranslation project: https://translate.wordpress.org/projects/wp-plugins/clarivo/
The plugin ships with a complete German translation (I am a native German speaker). I have already submitted 410 suggestions that are currently waiting for review.
\nThanks a lot!
\n#editor-requests
", "id": 16579893, "pubDate": "Tue, 14 Jul 2026 12:21:27 GMT", "whenReceived": "Tue, 14 Jul 2026 13:40:35 GMT", "whenUpdated": "Wed, 15 Jul 2026 01:22:39 GMT", "likes": [], "metadata": { "wpPostId": 68524, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68520", "title": "PTE Request for “Headingo” and “Toolbar Cleanup for Divi”", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-for-headingo-and-toolbar-cleanup-for-divi/", "description": "I am the plugin author for Headingo and Toolbar Cleanup for Divi. 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/headingo\n\nhttps://wordpress.org/plugins/toolbar-cleanup-for-divi\n\n\n[List of locale tags and the username(s) requested for PTE. The lower-case “o” in position 1 of each line will expand to a check-box that we use for the follow-up.]
\n\n #en_AU – @jdab\n\n #en_CA – @jdab\n\n #en_NZ – @jdab\n\n #en_ZA – @jdab\n\n #art_xemoji – @jdab\n\n\nIf you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16579895, "pubDate": "Tue, 14 Jul 2026 12:20:57 GMT", "whenReceived": "Tue, 14 Jul 2026 13:40:35 GMT", "whenUpdated": "Tue, 14 Jul 2026 13:40:35 GMT", "likes": [], "metadata": { "wpPostId": 68520, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68516", "title": "PTE Request for Prevent Browser Caching (Spanish, es_ES)", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-for-prevent-browser-caching-spanish-es_es/", "description": "Hi Polyglots team,
\nI’m the author of Prevent Browser Caching:
\n\nhttps://wordpress.org/plugins/prevent-browser-caching/\n\n\nI’ve prepared a Spanish (es_ES) translation of the plugin’s UI (100% of the strings)
\nand the current readme, and submitted it as suggestions.
I’m not a native Spanish speaker, so I prepared it carefully against the es_ES glossary and style guide (informal “tú”, Spanish « » quotation marks) rather than as raw machine output, and I reused the existing approved Spanish strings for consistency.
\nI’d be grateful if the Spanish team could review it — corrections very welcome — and, if it’s up to standard, consider PTE access so I can keep the plugin’s Spanish translation current after each release.
\n\nProject: https://translate.wordpress.org/projects/wp-plugins/prevent-browser-caching/\n\nLocale: Spanish (Spain) — es_ES\n\nMy WordPress.org username: kostyatereshchuk\n\n\nThank you for your time and for maintaining the Spanish locale.
\n\n #es_ES \n\n\n#editor-requests
", "id": 16575228, "pubDate": "Tue, 14 Jul 2026 08:50:44 GMT", "whenReceived": "Tue, 14 Jul 2026 09:42:48 GMT", "whenUpdated": "Tue, 14 Jul 2026 13:40:35 GMT", "likes": [], "metadata": { "wpPostId": 68516, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68503", "title": "PTE Request for Airygen SEO", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-for-airygen-seo/", "description": "I am the plugin author for airygen-seo. 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/airygen-seo/\n\n\n\n #zh_TW – @airygen, @terrylin\n\n #zh_CN – @airygen, @terrylin (@tobifjellner)\n\n\n— es_ES – @airygen, @terrylin (@nilovelez)
\n— de_DE – @airygen, @terrylin
— ru_RU – @airygen, @terrylin
\n\n #fr_FR – @airygen, @terrylin\n\n\n#editor-requests
", "id": 16573897, "pubDate": "Tue, 14 Jul 2026 07:39:22 GMT", "whenReceived": "Tue, 14 Jul 2026 08:02:24 GMT", "whenUpdated": "Wed, 15 Jul 2026 01:22:39 GMT", "likes": [], "metadata": { "wpPostId": 68503, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68491", "title": "PTE Request for Smart Booking", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-for-smart-booking/", "description": "Hello Polyglots,
\nI am the plugin author of Smart Booking ( https://wordpress.org/plugins/smart-booking/ ).
\nI have submitted Japanese translations for the plugin’s stable readme and would like to
\nreview/approve translations for this plugin myself.
Could I be added as a PTE for the following locale?
\n\n #ja\n\n\nMy WordPress.org username: liberdadeinc
\nThank you!
\n#editor-requests
", "id": 16573898, "pubDate": "Tue, 14 Jul 2026 07:37:27 GMT", "whenReceived": "Tue, 14 Jul 2026 08:02:24 GMT", "whenUpdated": "Tue, 14 Jul 2026 08:02:24 GMT", "likes": [], "metadata": { "wpPostId": 68491, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68493", "title": "PTE Request for Reviso – Client Feedback & Approvals", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-for-reviso-client-feedback-approvals/", "description": "Hi Polyglots,
\nI’m the plugin author. I’ve added translations for my plugin and would like to become PTE so I can review and approve them for these locales:
\nPlugin: https://wordpress.org/plugins/reviso-for-bricks/
\nTranslation project: https://translate.wordpress.org/projects/wp-plugins/reviso-for-bricks/
Requested locales:
\n— de_DE
\n\n #fr_FR \n\n #es_ES \n\n\nTranslators (me): @benelwoods
\nThe translations follow a maintained glossary (formal register throughout) and preserve all placeholders and HTML. Happy to coordinate with existing locale GTEs. Thanks!
\n#editor-requests
", "id": 16573899, "pubDate": "Tue, 14 Jul 2026 07:36:26 GMT", "whenReceived": "Tue, 14 Jul 2026 08:02:24 GMT", "whenUpdated": "Wed, 15 Jul 2026 01:22:39 GMT", "likes": [], "metadata": { "wpPostId": 68493, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68505", "title": "PTE Request: Australian translation verification", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-australian-translation-verification/", "description": "Hi team, I’ve done some translations for the CusRev (Customer Review) for WooCommerce plugin translation challenge, and would like to request someone from en_au to verify them.
\n\nhttps://translate.wordpress.org/locale/en-au/default/wp-plugins/customer-reviews-woocommerce/\n\n\n\n #en_AU \n\n\nThank you,
\nHoney
#editor-requests
", "id": 16573900, "pubDate": "Tue, 14 Jul 2026 07:07:54 GMT", "whenReceived": "Tue, 14 Jul 2026 08:02:24 GMT", "whenUpdated": "Tue, 14 Jul 2026 08:02:24 GMT", "likes": [], "metadata": { "wpPostId": 68505, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/core/feed", "whenReceived": "Tue, 14 Jul 2026 07:31:55 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/core/feed", "guid": "https://make.wordpress.org/core/?p=124572", "title": "Dev Chat Agenda – July 14, 2026", "link": "https://make.wordpress.org/core/2026/07/14/dev-chat-agenda-july-14-2026-2/", "description": "The next WordPress Developers Chat will take place on Tuesday, July 14, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.
\n\n\n\nThe live meeting will focus on the discussion for upcoming releases, and have an open floor section.
\n\n\n\nThe 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\nNote: 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 1 is due for release this Wednesday, July 15th. The release party starts at 15:00 UTC.\n\n\n\nNew Dev Note: Consistent navigation in WordPress 7.1 with persistent toolbar\n\n\n\n\nGeneral\n\n\n\n\n7.0.1 is now available for download\n\n\n\nTransitioning to rulesets in the Gutenberg repository\n\n\n\nGuide to WCUS 2026\n\n\n\n\n\nDiscussions \n\n\n\nThe 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\nAny 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.
#7-1, #agenda, #core, #dev-chat
", "id": 16573640, "pubDate": "Tue, 14 Jul 2026 07:04:51 GMT", "whenReceived": "Tue, 14 Jul 2026 07:31:55 GMT", "whenUpdated": "Tue, 14 Jul 2026 07:31:55 GMT", "likes": [], "metadata": { "wpPostId": 124572, "wpSiteId": 38254163 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Tue, 14 Jul 2026 04:42:00 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68495", "title": "PTE Request for Prime Cache (Japanese / ja)", "link": "https://make.wordpress.org/polyglots/2026/07/14/pte-request-for-prime-cache-japanese-ja/", "description": "I am the plugin author for Prime Cache. I have submitted the full
\nJapanese (ja) translation for the stable version (all strings), following
\nthe Japanese team’s translation guidelines and glossary.
Please add the following WordPress.org user as Project Translation Editor:
\n\n #ja – @rapls\n\n\nName: Prime Cache
\nURL: https://wordpress.org/plugins/prime-cache/
I already maintain the Japanese translation of my other plugin,
\nRapls AI Chatbot, as PTE for #ja.
If you have any questions, just comment here. Thank you!
\n#editor-requests
", "id": 16571783, "pubDate": "Tue, 14 Jul 2026 03:20:03 GMT", "whenReceived": "Tue, 14 Jul 2026 04:42:00 GMT", "whenUpdated": "Tue, 14 Jul 2026 04:42:00 GMT", "likes": [], "metadata": { "wpPostId": 68495, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/community/feed/", "whenReceived": "Tue, 14 Jul 2026 02:29:16 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/community/feed/", "guid": "https://make.wordpress.org/community/?p=88026", "title": "Meet the Community Agents: AI assistants for WordPress community workflows", "link": "https://make.wordpress.org/community/2026/07/14/meet-the-community-agents-ai-assistants-for-wordpress-community-workflows/", "description": "The WordPress Community Team handles a steady stream of repetitive, detail-heavy tasks: vetting event and organizer applications, reviewing budgets, and checking sites for licensing and trademark compliance. Each one requires careful research across many public sources, and each one takes time that could go toward supporting our community.
\n\n\n\nTo help with that, we’ve built Community Agents: a lightweight, community-owned platform of AI assistants that handle the legwork of these reviews while leaving every decision in human hands.
\n\n\n\nHow it works\n\n\n\nEach agent lives in a single Slack channel and is triggered with a simple slash command (for example, /tm-audit). It runs its research, visits the relevant public pages, and reports back its findings, clearly labeling what it has confirmed, what is unconfirmed, and what it couldn’t verify. A reviewer then confirms or corrects each step before anything is finalized. The agents are built on Python, Slack Bolt, and the Claude API.
\n\n\n\nTwo principles guide the whole platform:
\n\n\n\n\nHuman-in-the-loop. The agents gather and summarize; people decide. Nothing is auto-approved.\n\n\n\nPrivacy-conscious. The agents work only from what’s publicly available (names, WordPress.org profiles, public links) and deliberately don’t ask for personal data such as email or home addresses.\n\n\n\n\nThe agents so far\n\n\n\n\n/wc-vet: vets WordCamp organizer applications.\n\n\n\n/wpcc-vet: vets WordPress Campus Connect organizer applications.\n\n\n\n/sc-vet: vets WordPress Student Club organizer applications.\n\n\n\n/meetup-vet: vets WordPress Meetup organizer applications.\n\n\n\n/other-event-vet: vets other community events (Women WordPress Day, photo events, themed WordPress Days, etc).\n\n\n\n/wc-budget-review: reviews WordCamp budgets, with live currency and cost checks.\n\n\n\n/tm-audit: audits a website for GPL and WordPress trademark compliance.\n\n\n\n\nWant to use them, or have an idea?\n\n\n\nIf you’d like access to the Community Agents, or you have a manual, repetitive task you think an agent could help with, I’d love to hear from you: @clk87.
", "id": 16570472, "pubDate": "Tue, 14 Jul 2026 01:35:44 GMT", "whenReceived": "Tue, 14 Jul 2026 02:29:16 GMT", "whenUpdated": "Tue, 14 Jul 2026 02:29:16 GMT", "likes": [], "metadata": { "wpPostId": 88026, "wpSiteId": 42922441 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/cli/feed/", "whenReceived": "Mon, 13 Jul 2026 23:06:41 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/cli/feed/", "guid": "https://make.wordpress.org/cli/2026/07/13/xpost-hardening-github-actions-workflows-across-the-wordpress-organisation/", "title": "X-post: Hardening GitHub Actions workflows across the WordPress organisation", "link": "https://make.wordpress.org/cli/2026/07/13/xpost-hardening-github-actions-workflows-across-the-wordpress-organisation/", "description": "X-comment from +make.wordpress.org/security: Comment on Hardening GitHub Actions workflows across the WordPress organisation
", "id": 16567816, "pubDate": "Mon, 13 Jul 2026 21:30:51 GMT", "whenReceived": "Mon, 13 Jul 2026 23:06:41 GMT", "whenUpdated": "Mon, 13 Jul 2026 23:06:41 GMT", "likes": [], "metadata": { "wpPostId": 18562, "wpSiteId": 121810585 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 13 Jul 2026 22:01:20 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68474", "title": "PTE Request for Hook2Go Notifications", "link": "https://make.wordpress.org/polyglots/2026/07/13/pte-request-for-hook2go-notifications/", "description": "Hello Polyglots team!
\nI am the plugin author for Hook2Go Notifications:
\n\nhttps://wordpress.org/plugins/hook2go-notifications/\n\n\nI have prepared and imported the Russian translations for the Stable Readme of my plugin. I would like to become a Project Translation Editor for this plugin and the Russian locale.
\n\n #ru_RU @aleksman (@Aleksman)\n\n\nI will follow the Russian locale glossary and style guide.
\nThank you!
\n#editor-requests
", "id": 16566695, "pubDate": "Mon, 13 Jul 2026 21:06:44 GMT", "whenReceived": "Mon, 13 Jul 2026 22:01:20 GMT", "whenUpdated": "Tue, 14 Jul 2026 01:21:57 GMT", "likes": [], "metadata": { "wpPostId": 68474, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68472", "title": "PTE Request for Prevent Browser Caching", "link": "https://make.wordpress.org/polyglots/2026/07/13/pte-request-for-prevent-browser-caching/", "description": "Hi Polyglots team,
\nI’m the author of Prevent Browser Caching
\n( https://wordpress.org/plugins/prevent-browser-caching/ ).
I’ve prepared a full Ukrainian (uk) translation — 100% of the UI strings plus the
\ncurrent readme — and I’d like to help keep my plugin’s translations up to date.
Could a GTE please grant me PTE access for this project?
\n\nProject: https://translate.wordpress.org/projects/wp-plugins/prevent-browser-caching/\n\n\n\n #uk @kostyatereshchuk (@tobifjellner)\n\n\nThe translation is my own work, glossary-checked and reviewed by me as a native
\nspeaker; I’ll maintain it after each release and welcome any corrections from the
\nlocale team. More locales will follow as those drafts are ready.
Thank you!
\n#editor-requests
", "id": 16566696, "pubDate": "Mon, 13 Jul 2026 21:05:59 GMT", "whenReceived": "Mon, 13 Jul 2026 22:01:20 GMT", "whenUpdated": "Tue, 14 Jul 2026 08:02:24 GMT", "likes": [], "metadata": { "wpPostId": 68472, "wpSiteId": 31792945 }, "ctLikes": 0 }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68461", "title": "PTE Request for Conversion Connector by GLM-DEV", "link": "https://make.wordpress.org/polyglots/2026/07/13/pte-request-for-conversion-connector-by-glm-dev/", "description": "I am the plugin author for Conversion Connector by GLM-DEV. I have translated all 19 strings for Russian and would like to approve them. Please add the following WordPress.org user as translation editor:
\n\nhttps://wordpress.org/plugins/conversion-connector-by-glm-dev/\n\n\n\n #ru_RU – @glmdev\n\n\nAll translations are submitted and waiting for approval. Thank you!
\n#editor-requests
", "id": 16566697, "pubDate": "Mon, 13 Jul 2026 21:04:50 GMT", "whenReceived": "Mon, 13 Jul 2026 22:01:20 GMT", "whenUpdated": "Mon, 13 Jul 2026 22:01:20 GMT", "likes": [], "metadata": { "wpPostId": 68461, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/training/feed/", "whenReceived": "Mon, 13 Jul 2026 18:26:22 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/training/feed/", "guid": "https://make.wordpress.org/training/?p=173780", "title": "Meeting agenda for July 14th, 2026", "link": "https://make.wordpress.org/training/2026/07/13/meeting-agenda-for-july-14th-2026/", "description": "This week’s meeting will be held on Tuesday, July 14th, 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\nThis week’s meeting will be hosted by @rjekic.
\n\n\n\n1. Intro/Welcome\n\n\n\nWelcome 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\nJuly 14th – @andrewssanya\n\n\n\nJuly 21st – @sibokul\n\n\n\nJuly 28th – @pravin1996\n\n\n\n\n\nLooking for feedback\n\nWe are planning to host Office Hours on July 26, 2026, but we need your help:\n\nDo you agree with the proposed date – July 26, 2026?\n\n\n\nWe need someone to host the meeting. Please state your interest and availability to host the Office Hours meeting\n\n\n\nWe need a note-taker for the Office Hours meeting. Please state your interest and availability.\n\n\n\nWe would like to know your opinion on how we can improve these meetings and encourage more members to join and participate actively. You can share your suggestion here or in this GitHub issue – https://github.com/WordPress/Learn/issues/3535. Big thank you to everyone who has shared feedback so far!\n\n\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\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: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\nYou 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": 16562322, "pubDate": "Mon, 13 Jul 2026 17:49:45 GMT", "whenReceived": "Mon, 13 Jul 2026 18:26:22 GMT", "whenUpdated": "Mon, 13 Jul 2026 18:26:22 GMT", "likes": [], "metadata": { "wpPostId": 173780, "wpSiteId": 46403572 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "whenReceived": "Mon, 13 Jul 2026 15:20:55 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/polyglots/feed/", "guid": "https://make.wordpress.org/polyglots/?p=68467", "title": "PTE Request for Virtuaria Pix…", "link": "https://make.wordpress.org/polyglots/2026/07/13/pte-request-for-virtuaria-pix/", "description": "PTE Request for Virtuaria Pix Payments with Delfinance for WooCommerce
\nI am the plugin author for Virtuaria Pix Payments with Delfinance for WooCommerce. 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/virtuaria-delfinance/\n\n\n\n #pt_BR – @viniciusvirtuaria\n\n\nThank you!
\n#editor-requests
", "id": 16556670, "pubDate": "Mon, 13 Jul 2026 14:07:37 GMT", "whenReceived": "Mon, 13 Jul 2026 15:20:55 GMT", "whenUpdated": "Mon, 13 Jul 2026 22:01:20 GMT", "likes": [], "metadata": { "wpPostId": 68467, "wpSiteId": 31792945 }, "ctLikes": 0 } ] }, { "feedUrl": "https://wordpress.org/news/podcast/feed/", "whenReceived": "Mon, 13 Jul 2026 14:21:20 GMT", "items": [ { "feedUrl": "https://wordpress.org/news/podcast/feed/", "guid": "https://wordpress.org/news/?p=21007", "title": "Your Guide to WordCamp US 2026", "link": "https://wordpress.org/news/2026/07/wcus-2026-guide/", "description": "August 16-19, 2026 | Phoenix Convention Center, Phoenix, Arizona\n\n\n\nWordCamp US 2026 returns for another year, this time in Phoenix, Arizona, for four days, August 16 to 19. It comes at a moment of real energy for WordPress, as artificial intelligence reshapes everyday workflows, the business of building and maintaining sites is shifting, and new people keep discovering the platform every day. Four tracks address this moment, covering AI, Honing Your Skills, Technical WordPress, and Beginner WordPress. Between them, there is something for everyone, whether you lead an agency, freelance for local clients, write code for a living, or are building your very first site. Whatever draws you in, you will leave Phoenix better equipped and better connected than ever.
\n\n\n\n\nGet Your Tickets\n\n\n\nSign Up for Contributor Day\n\n\n\nSee the Schedule\n\n\n\n\nPhoenix itself rewards anyone who adds a day or two to their trip. The capital of Arizona sits in the Sonoran Desert and pairs a lively downtown with a rich arts and food scene. The Roosevelt Row arts district is known for its galleries, murals, and independent restaurants. It is also home to one of the largest art walks in the region. Nearby, Chase Field and the Footprint Center host professional baseball and live shows, and the surrounding desert offers striking scenery at places like Papago Park and the Desert Botanical Garden.
\n\n\n\n\n\n\n\nStart with Contributor Day\n\n\n\nThe week begins with Contributor Day, a full day set aside for giving back to the project that makes everything else possible. Attendees will gather in teams to improve WordPress itself, from Core code and documentation to design, training, accessibility, and translation.
\n\n\n\n\nWordPress is so unique because we’re not just a product; we’re a movement.
\nMatt Mullenweg, WordPress Cofounder\n\n\n\nContributor Day is open to everyone, whatever your skills, and whether or not you have ever contributed before. Come and experience the open source collaboration that is at the heart of the project. Signing up in advance helps us prepare our veteran contributors and provide you with the best experience.
\n\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\nExplore Real-World Projects on Showcase Day\n\n\n\nDay 2, Showcase Day, is dedicated to real-world WordPress projects and focuses on how teams develop features, manage publishing, and run demanding sites at scale. It brings to life the kind of work collected in the WordPress Showcase, the directory of standout sites built on the platform, from global brands like Disney to community publishers and institutions like NASA. Past WordCamp US Showcase days have brought teams from the likes of Wikimedia and CANCOM to explain how they manage large, high-traffic systems. Other sessions took a builder’s perspective on catching bugs faster with automated testing and even running the Block Editor inside a custom app.
\n\n\n\n\n\n\n\nDive Into Two Conference Days\n\n\n\nThe two main conference days will bring a full slate of sessions across four tracks. First among them is the AI track, which treats the technology as a tool to handle with care rather than a headline to chase. Its sessions set guardrails for AI-assisted development, prepare for a web where AI agents become the visitors a site must serve, and weigh the legal and ethical questions of putting AI tools in the hands of clients. Speakers from companies like Elementor will be taking a look at where the web is heading, while keeping the focus on what teams can adopt today without giving up control of their work.
\n\n\n\nThe Technical WordPress and Honing Your Skills tracks cover the craft and business of building with WordPress. On the technical side, sessions dig into modern development workflows, automated testing with tools like the browser-based WordPress Playground, and plugin pipelines. The Honing Your Skills track adds practical guidance on pricing, maintenance, and how the agency model is changing as clients ask for more. The Beginner WordPress track keeps the door open for newcomers, with approachable sessions that make your first WordCamp less daunting. Hands-on work runs through all of these tracks, so alongside the talks, attendees will find workshops and working sessions where they can build something real and leave ready to apply it to their own projects.
\n\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\n\t\t\t\n\t\t\t\t\n\t\t\t\n\t\t\n\n\n\n\nNot all of the value happens in the session rooms. On the show floor, the Happiness Bar is a free, drop-in help desk where you can sit down with a volunteer WordPress expert and work through whatever has you stuck. The Sponsor Hall next door is where many of the best unplanned conversations happen, and its Career Corner gives anyone weighing their next move a relaxed place to browse the job board, meet company reps, and see who is hiring across the ecosystem.
\n\n\n\nPlan Your Trip to Phoenix\n\n\n\nGetting to Phoenix is straightforward. The Phoenix Convention Center sits in the heart of downtown, less than five miles from Phoenix Sky Harbor International Airport (PHX) and about 15 minutes away on the Valley Metro light rail. WordCamp US has a room block at the Sheraton Phoenix Downtown, close to the convention center, so book your hotel before the block fills, and reserve your ticket if you have not already. The full event lineup and details live on the WordCamp US 2026 site, and the conference closes with an evening social before everyone heads home.
\n\n\n\n\n\n Reserve your ticket\n\n\n\n Find accommodations\n\n\n\n Plan your trip\n\n\n\nExplore Phoenix\n\n\n\n\n\n\n\n\n\nHelp Us Spread the Word!\n\n\n\nWhether attending in person or following along online, share your experience and help welcome others to the WordPress community. Use the #WCUS and #WordPress hashtags to tell your story on social.
", "id": 16555268, "pubDate": "Mon, 13 Jul 2026 13:07:07 GMT", "whenReceived": "Mon, 13 Jul 2026 14:21:20 GMT", "whenUpdated": "Thu, 23 Jul 2026 19:50:23 GMT", "likes": [], "metadata": { "wpPostId": 21007, "wpSiteId": 14607090 }, "ctLikes": 0 } ] }, { "feedUrl": "https://make.wordpress.org/docs/feed/", "whenReceived": "Mon, 13 Jul 2026 12:25:47 GMT", "items": [ { "feedUrl": "https://make.wordpress.org/docs/feed/", "guid": "https://make.wordpress.org/docs/2026/07/13/xpost-documentation-team-update-july-13-2026/", "title": "X-post: Documentation Team Update – July 13, 2026", "link": "https://make.wordpress.org/docs/2026/07/13/xpost-documentation-team-update-july-13-2026/", "description": "X-comment from +make.wordpress.org/updates: Comment on Documentation Team Update – July 13, 2026
", "id": 16552762, "pubDate": "Mon, 13 Jul 2026 12:03:43 GMT", "whenReceived": "Mon, 13 Jul 2026 12:25:47 GMT", "whenUpdated": "Mon, 13 Jul 2026 12:25:47 GMT", "likes": [], "metadata": { "wpPostId": 108021, "wpSiteId": 31760022 }, "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/" ] } }