From noreply at wordpress.org  Fri May  1 00:47:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 00:47:04 -0000
Subject: [wp-trac] [WordPress Trac] #65124: Please include additional
 data validation in class-IXR-server.php
In-Reply-To: <057.4b26f520c07119a980e9344a815d2305@wordpress.org>
References: <057.4b26f520c07119a980e9344a815d2305@wordpress.org>
Message-ID: <072.77a403d47bbf7b3d0fc252eb64219a66@wordpress.org>

#65124: Please include additional data validation in class-IXR-server.php
---------------------------+--------------------------------
 Reporter:  eeeeeeeeeeeee  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  4.7
 Severity:  normal         |  Resolution:
 Keywords:  needs-patch    |     Focuses:  php-compatibility
---------------------------+--------------------------------

Comment (by galbaras):

 Here's the error message, just to help people find this ticket:

 {{{
 [23-Apr-2026 14:53:07 UTC] PHP Fatal error:  Uncaught TypeError: count():
 Argument #1 ($value) must be of type Countable|array, null given in ROOT
 /wp-includes/IXR/class-IXR-server.php:95
 Stack trace:
 #0 ROOT/wp-includes/IXR/class-IXR-server.php(207): IXR_Server->call()
 #1 ROOT/wp-includes/IXR/class-IXR-server.php(109): IXR_Server->multiCall()
 #2 ROOT/wp-includes/IXR/class-IXR-server.php(59): IXR_Server->call()
 #3 ROOT/wp-includes/IXR/class-IXR-server.php(27): IXR_Server->serve()
 #4 ROOT/wp-includes/IXR/class-IXR-server.php(35):
 IXR_Server->__construct()
 #5 ROOT/wp-includes/class-wp-xmlrpc-server.php(246):
 IXR_Server->IXR_Server()
 #6 ROOT/xmlrpc.php(85): wp_xmlrpc_server->serve_request()
 #7 {main}
   thrown in ROOT/wp-includes/IXR/class-IXR-server.php on line 95
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65124#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 03:27:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 03:27:28 -0000
Subject: [wp-trac] [WordPress Trac] #65145: Plugins: Display plugin
 slug/identifier in Installed Plugins row meta
In-Reply-To: <052.c963c996c75cb96bcb429195e4caec32@wordpress.org>
References: <052.c963c996c75cb96bcb429195e4caec32@wordpress.org>
Message-ID: <067.9d0e2ef00f891e60e7eb7dad4fcc4715@wordpress.org>

#65145: Plugins: Display plugin slug/identifier in Installed Plugins row meta
-------------------------+-----------------------------
 Reporter:  crweiner     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  administration
-------------------------+-----------------------------
Changes (by westonruter):

 * milestone:  Awaiting Review => Future Release


Comment:

 The plugin identifiers can be whatever the array keys for what is returned
 by `get_plugins()`.

 The `WP_Plugins_List_Table::single_row()` function is already passed a
 tuple which of `array( $plugin_file, $plugin_data )`. The `$plugin_file`
 is how to uniquely identify a plugin.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65145#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 03:41:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 03:41:29 -0000
Subject: [wp-trac] [WordPress Trac] #65118: Docs: Correct
 WP_Network_Query params comments
In-Reply-To: <062.bc857a5e1fc74eb71c058f3d42270cc9@wordpress.org>
References: <062.bc857a5e1fc74eb71c058f3d42270cc9@wordpress.org>
Message-ID: <077.2709011cec46dd959e2f80827cbb22db@wordpress.org>

#65118: Docs: Correct WP_Network_Query params comments
----------------------------+----------------------------------------------
 Reporter:                  |       Owner:  westonruter
  baikare.sandeep007        |
     Type:  enhancement     |      Status:  reviewing
 Priority:  normal          |   Milestone:  7.1
Component:  Networks and    |     Version:  4.6
  Sites                     |
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs, administration, multisite
----------------------------+----------------------------------------------
Changes (by westonruter):

 * owner:  (none) => westonruter
 * status:  new => reviewing


Comment:

 Queueing up for 7.1

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65118#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 04:53:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 04:53:25 -0000
Subject: [wp-trac] [WordPress Trac] #64987: Admin Reskin: Add more
 margin below the plugin card header
In-Reply-To: <053.b1d5d7c143cf639af6b45eb03cf6d81a@wordpress.org>
References: <053.b1d5d7c143cf639af6b45eb03cf6d81a@wordpress.org>
Message-ID: <068.3a3eab1025a6103024c1c8e23a778629@wordpress.org>

#64987: Admin Reskin: Add more margin below the plugin card header
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch commit dev-   |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  admin-reskin has-patch commit dev-feedback => admin-reskin
     has-patch commit dev-reviewed


Comment:

 Second committer sign-off: This looks good to me 👍

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64987#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 05:54:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 05:54:48 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.ea66a63d02348e1a5a05ff4ba8072ccd@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+----------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  7.0
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+----------------------
Changes (by gaurangsondagar):

 * Attachment "admin-dashboard-widgets-drag-issue.mp4" added.

 Admin Dashboard Widgets Drag issue

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 05:57:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 05:57:01 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.a17418d7b573a205eb1a8a5c7e20f5a2@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+----------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  7.0
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+----------------------

Comment (by gaurangsondagar):

 **Patch Testing Report:**

 **Patch Tested:** https://core.trac.wordpress.org/ticket/65151

 **Environment:**
 - PHP: 8.2.29
 - WordPress: 7.0-RC2-62242
 - Web server: Apache
 - Database: MySQL
 - Browser: Chrome
 - OS: Ubuntu 22.04.5 LTS

 **Steps I followed:**
 - Performed random drag-and-drop actions with widgets on the admin
 dashboard
 - Noticed that when scrolling is required during dragging, the widget does
 not always drop in the intended location
 - The issue was successfully reproduced

 **Result:**
 The drag issue was successfully reproduced, please review the following
 video attachment as a reference.

 https://core.trac.wordpress.org/attachment/ticket/65151/admin-dashboard-
 widgets-drag-issue.mp4

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 06:28:45 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 06:28:45 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.4f1a95d3c223f18f5743f0a82b422d75@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+----------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  7.0
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+----------------------

Comment (by huzaifaalmesbah):

 Hello @gaurangsondagar Just to clarify, no patch has been submitted for
 this ticket so far.

 The report you shared appears to be a Reproduction Report, showing how the
 issue occurs, rather than a patch test.

 Thanks for providing report.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 07:22:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 07:22:21 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.fa00a73ea6f9f299ab8a0d4389aa2636@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+----------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  7.0
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+----------------------

Comment (by gaurangsondagar):

 Hi @huzaifaalmesbah Thanks for correcting me. I have updated my reproduce
 report.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 08:11:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 08:11:52 -0000
Subject: [wp-trac] [WordPress Trac] #64872: WP AI Client: Add AI REST
 API Endpoints (`wp-ai/v1`)
In-Reply-To: <050.632db09585bed6c19d723e601c3f6ab6@wordpress.org>
References: <050.632db09585bed6c19d723e601c3f6ab6@wordpress.org>
Message-ID: <065.3f2870eddaba614e588853b9b782a52d@wordpress.org>

#64872: WP AI Client: Add AI REST API Endpoints (`wp-ai/v1`)
-------------------------------------------------+-------------------------
 Reporter:  gziolo                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  ai-client has-patch has-unit-tests   |     Focuses:  rest-api
  2nd-opinion                                    |
-------------------------------------------------+-------------------------

Comment (by darshitrajyaguru97):

 Following up on the previous feedback, I looked into a few areas that
 might help improve this further:

 === **1. Capability handling ===

 Using `manage_options` for `prompt_ai` feels a bit too broad, especially
 since AI usage can have cost implications.

 It might be better to introduce a separate capability like
 `use_ai_features` and map it using `map_meta_cap()`. This would:
 * Give more control over who can use AI features
 * Make it easier to adjust permissions in the future (per role or per
 site)
 * Follow how capabilities are usually handled in Core

 === **2. Providers and models endpoints ===

 Right now, `list_ai_providers` and `list_ai_models` are separate. This
 might be more complex than needed.

 We could simplify this by having a single endpoint (for example
 `/ai/providers`) that returns providers along with their models. This
 would:
 * Reduce duplicate logic
 * Avoid multiple API calls from the client

 If there’s a reason to keep them separate (like performance or different
 auth needs), it would be helpful to mention that.

 === **3. Capability checks implementation ===

 Using `map_meta_cap` instead of `user_has_cap` would be more in line with
 Core standards and ensure consistent behavior.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64872#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 08:26:26 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 08:26:26 -0000
Subject: [wp-trac] [WordPress Trac] #64924: Add a `has_ai_credentials()`
 function to WordPress core that plugins can use to check if AI credentials
 are available.
In-Reply-To: <055.27be0ae421a3dd47e68ac187c824a251@wordpress.org>
References: <055.27be0ae421a3dd47e68ac187c824a251@wordpress.org>
Message-ID: <070.a0a65fed770e4d29f143627eaa1907f5@wordpress.org>

#64924: Add a `has_ai_credentials()` function to WordPress core that plugins can
use to check if AI credentials are available.
----------------------------------------------+----------------------------
 Reporter:  raftaar1191                       |       Owner:  (none)
     Type:  enhancement                       |      Status:  new
 Priority:  normal                            |   Milestone:  Awaiting
                                              |  Review
Component:  AI                                |     Version:  trunk
 Severity:  normal                            |  Resolution:
 Keywords:  connectors ai-client 2nd-opinion  |     Focuses:
                                              |  sustainability
----------------------------------------------+----------------------------

Comment (by darshitrajyaguru97):

 Adds `has_ai_credentials()` to core in `wp-includes/connectors.php`.

 - Implements credential detection via `wp_get_connectors()`
 - Supports API key-based authentication
 - Includes `wpai_has_ai_credentials` filter for extensibility
 - Adds defensive checks for connector structure
 - Includes unit tests for:
   - No connectors
   - Missing credentials
   - Valid credentials
   - Filter override

 This aligns with the Connectors API and avoids duplicating logic currently
 present in the AI plugin.

 **Note:** The filter passes the computed `$has_credentials` value rather
 than a hardcoded `false`, allowing partial detection logic to be preserved
 while still enabling overrides.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64924#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 14:43:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 14:43:59 -0000
Subject: [wp-trac] [WordPress Trac] #65157: Blocks: WordPress prevent videos
 from being set as backgrounds
Message-ID: <049.b5992ec627f0854820bdf57a9285b790@wordpress.org>

#65157: Blocks: WordPress prevent videos from being set as backgrounds
------------------------------------------+-----------------------------
 Reporter:  wurds                         |      Owner:  (none)
     Type:  feature request               |     Status:  new
 Priority:  normal                        |  Milestone:  Awaiting Review
Component:  Media                         |    Version:  6.9.4
 Severity:  normal                        |   Keywords:
  Focuses:  ui, administration, template  |
------------------------------------------+-----------------------------
 I'm attempting to set a video as the background for a block.
 this block is a group which is nested inside a row.

 A filter is being applied to the media gallery which makes it so only
 images can be picked.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65157>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 17:34:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 17:34:20 -0000
Subject: [wp-trac] [WordPress Trac] #64983: Scale needs gettext
In-Reply-To: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
References: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
Message-ID: <067.cf0c44c1d8378df033a14c7a41846be0@wordpress.org>

#64983: Scale needs gettext
--------------------------+-----------------------
 Reporter:  timse201      |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  7.0
Component:  I18N          |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------
Changes (by shailu25):

 * keywords:  changes-requested has-patch => has-patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64983#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 18:19:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 18:19:31 -0000
Subject: [wp-trac] [WordPress Trac] #65157: Blocks: WordPress prevent
 videos from being set as backgrounds
In-Reply-To: <049.b5992ec627f0854820bdf57a9285b790@wordpress.org>
References: <049.b5992ec627f0854820bdf57a9285b790@wordpress.org>
Message-ID: <064.c4d471f8b2669b99d3b624af1bd2a65e@wordpress.org>

#65157: Blocks: WordPress prevent videos from being set as backgrounds
-----------------------------+-------------------------------------------
 Reporter:  wurds            |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Media            |     Version:  6.9.4
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  ui, administration, template
-----------------------------+-------------------------------------------

Comment (by blackstar1991):

 It's not a bug.
 This is normal behavior of the component.
 If you need a full-width video component, you can create it yourself or
 download the plugin.
 The image can be set because there is a [background
 https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties
 /background-image] property for CSS. You cannot put a video file in this
 property.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65157#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 18:48:35 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 18:48:35 -0000
Subject: [wp-trac] [WordPress Trac] #65053: Media upload from the post
 edit screen shows an inaccurate number when uploading multiple media files
In-Reply-To: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
References: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
Message-ID: <068.3f33ffc32b746c0e23efc1f42c6c8eea@wordpress.org>

#65053: Media upload from the post edit screen shows an inaccurate number when
uploading multiple media files
--------------------------+------------------------------
 Reporter:  Dharm1025     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Upload        |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, javascript
--------------------------+------------------------------

Comment (by adamsilverstein):

 @hbhalodia - nice work.

 The fix in https://github.com/WordPress/wordpress-develop/pull/11585 looks
 good! I added some tests in https://github.com/WordPress/wordpress-
 develop/compare/trunk...adamsilverstein:wordpress-develop:trac-65053
 -attachments-count if you want to add them to your pr. They fail before
 the pr changes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65053#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 18:50:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 18:50:08 -0000
Subject: [wp-trac] [WordPress Trac] #65053: Media upload from the post
 edit screen shows an inaccurate number when uploading multiple media files
In-Reply-To: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
References: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
Message-ID: <068.58ccf3a769ee8441cb78f5017d84a2a2@wordpress.org>

#65053: Media upload from the post edit screen shows an inaccurate number when
uploading multiple media files
-------------------------------------------------+-------------------------
 Reporter:  Dharm1025                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Upload                               |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests has-      |     Focuses:  ui,
  test-info                                      |  javascript
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * keywords:  has-patch => has-patch needs-unit-tests has-test-info


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65053#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 18:50:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 18:50:50 -0000
Subject: [wp-trac] [WordPress Trac] #65053: Media upload from the post
 edit screen shows an inaccurate number when uploading multiple media files
In-Reply-To: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
References: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
Message-ID: <068.8f8f693e2e7413c7bfbe875290eb76b2@wordpress.org>

#65053: Media upload from the post edit screen shows an inaccurate number when
uploading multiple media files
-------------------------------------------------+-------------------------
 Reporter:  Dharm1025                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Upload                               |     Version:  6.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests has-      |     Focuses:  ui,
  test-info                                      |  javascript
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * version:  trunk => 6.3
 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65053#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 18:51:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 18:51:11 -0000
Subject: [wp-trac] [WordPress Trac] #65053: Media upload from the post
 edit screen shows an inaccurate number when uploading multiple media files
In-Reply-To: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
References: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
Message-ID: <068.379711da0fdf58b21e995ad46141f5e3@wordpress.org>

#65053: Media upload from the post edit screen shows an inaccurate number when
uploading multiple media files
-------------------------------------------------+-------------------------
 Reporter:  Dharm1025                            |       Owner:
                                                 |  adamsilverstein
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  7.1
Component:  Upload                               |     Version:  6.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests has-      |     Focuses:  ui,
  test-info                                      |  javascript
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * owner:  (none) => adamsilverstein
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65053#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 23:38:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 23:38:37 -0000
Subject: [wp-trac] [WordPress Trac] #65131: Administration: Spinners are
 misaligned
In-Reply-To: <053.8909cf9fe91d2de421593bc947a3a237@wordpress.org>
References: <053.8909cf9fe91d2de421593bc947a3a237@wordpress.org>
Message-ID: <068.defb305d5b1bdb53afe0aabc7c8068bd@wordpress.org>

#65131: Administration: Spinners are misaligned
------------------------------------+-----------------------------
 Reporter:  wildworks               |       Owner:  SergeyBiryukov
     Type:  defect (bug)            |      Status:  closed
 Priority:  normal                  |   Milestone:  7.0
Component:  Administration          |     Version:
 Severity:  normal                  |  Resolution:  fixed
 Keywords:  admin-reskin has-patch  |     Focuses:  ui
------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62291" 62291]:
 {{{
 #!CommitTicketReference repository="" revision="62291"
 Admin Reskin: Correct alignment for spinners across the admin.

 Follow-up to [61646].

 Props wildworks, anupkankale, shailu25, gaurangsondagar, jadavsanjay,
 SergeyBiryukov.
 Fixes #65131.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65131#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  1 23:40:35 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 01 May 2026 23:40:35 -0000
Subject: [wp-trac] [WordPress Trac] #65131: Administration: Spinners are
 misaligned
In-Reply-To: <053.8909cf9fe91d2de421593bc947a3a237@wordpress.org>
References: <053.8909cf9fe91d2de421593bc947a3a237@wordpress.org>
Message-ID: <068.228e291a0a23dcc591282e6c4738b44d@wordpress.org>

#65131: Administration: Spinners are misaligned
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Administration                       |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch commit dev-   |     Focuses:  ui
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * keywords:  admin-reskin has-patch => admin-reskin has-patch commit dev-
     feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for 7.0 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65131#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 01:30:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 01:30:50 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.05d52be2c30f0b6b3c98b7184445ea1c@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+----------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  7.0
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+----------------------
Changes (by yusufmudagal):

 * Attachment "65151.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 02:47:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 02:47:00 -0000
Subject: [wp-trac] [WordPress Trac] #65117: Proposal: Hook Permissions
 Layer
In-Reply-To: <058.1dbd21cd15065ddb6712c145e34a008f@wordpress.org>
References: <058.1dbd21cd15065ddb6712c145e34a008f@wordpress.org>
Message-ID: <073.a8b95aa84b02d3736b541bcea202eca0@wordpress.org>

#65117: Proposal: Hook Permissions Layer
---------------------------------------+------------------------------
 Reporter:  namith.jawahar             |       Owner:  (none)
     Type:  feature request            |      Status:  new
 Priority:  normal                     |   Milestone:  Awaiting Review
Component:  Plugins                    |     Version:
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:
---------------------------------------+------------------------------

Comment (by namith.jawahar):

 I think tracking ownership changes (going by the recent events) and
 outgoing http calls and making this passive rather than active (no
 blocking actions, but blocking auto updates if one of the trigger get
 hit).  Giving easier to understand information in the plugin details popup
 along with visible traffic light like alerts would make it pretty helpful.
 More like a gatekeeper rather than an active firewall.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65117#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 05:16:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 05:16:17 -0000
Subject: [wp-trac] [WordPress Trac] #64898: PHPStan code quality
 improvements for 7.1
In-Reply-To: <051.14621a206a2a689950362f87fda1495c@wordpress.org>
References: <051.14621a206a2a689950362f87fda1495c@wordpress.org>
Message-ID: <066.1f5fdd6f14d1882f9393a80273741bf8@wordpress.org>

#64898: PHPStan code quality improvements for 7.1
--------------------------------------+-------------------------------
 Reporter:  desrosj                   |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  General                   |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  coding-standards
--------------------------------------+-------------------------------

Comment (by westonruter):

 In [changeset:"62292" 62292]:
 {{{
 #!CommitTicketReference repository="" revision="62292"
 Build/Test Tools: Honor `@global` docblock tags in PHPStan analysis.

 This adds a PHPStan extension with a parser-node visitor that bridges
 WordPress core's `@global Type $varname` PHPDoc convention to PHPStan's
 variable type resolution, eliminating 3,784 spurious errors caused by
 globals resolving as `mixed` when on rule level 10 (out of 40,069 errors
 total, so a 9.4% reduction). This avoids the need to add `/** @var Type
 $varname */` annotations with each global variable.

 Developed in https://github.com/WordPress/wordpress-develop/pull/11692

 Props westonruter, apermo, szepeviktor.
 See #64898.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64898#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 05:54:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 05:54:54 -0000
Subject: [wp-trac] [WordPress Trac] #65015: Connectors: Several strings
 are not translated
In-Reply-To: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
References: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
Message-ID: <066.37ef03a367fa1d0d2344ac6e78de60d3@wordpress.org>

#65015: Connectors: Several strings are not translated
-------------------------------------------------+-------------------------
 Reporter:  369work                              |       Owner:
                                                 |  westonruter
     Type:  defect (bug)                         |      Status:  closed
 Priority:  high                                 |   Milestone:  7.0
Component:  I18N                                 |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests connectors  |     Focuses:
  commit needs-dev-note fixed-major dev-         |
  reviewed                                       |
-------------------------------------------------+-------------------------

Comment (by westonruter):

 In [changeset:"62293" 62293]:
 {{{
 #!CommitTicketReference repository="" revision="62293"
 I18N: Harden against undefined index in
 `_load_script_textdomain_from_src()`.

 This guards against an undefined index warning being raised when a script
 or script module is registered with a URL that lacks a path component.

 This also adds full PHPStan type definitions for `wp_parse_url()`,
 ensuring that the `_load_script_textdomain_from_src()` function has no
 PHPStan errors at rule level 10.

 Developed in https://github.com/WordPress/wordpress-develop/pull/11690

 Follow-up to r62278.

 Props westonruter, manzoorwanijk, mukesh27.
 See #65015, #64238.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65015#comment:51>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 05:54:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 05:54:53 -0000
Subject: [wp-trac] [WordPress Trac] #64238: PHPStan code quality
 improvements for 7.0
In-Reply-To: <058.3d898e5edbfd206122933e3b070d763b@wordpress.org>
References: <058.3d898e5edbfd206122933e3b070d763b@wordpress.org>
Message-ID: <073.0146e92a3e7aea15a745f21d8137936b@wordpress.org>

#64238: PHPStan code quality improvements for 7.0
--------------------------------------+-------------------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  closed
 Priority:  normal                    |   Milestone:  7.0
Component:  General                   |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  coding-standards
--------------------------------------+-------------------------------

Comment (by westonruter):

 In [changeset:"62293" 62293]:
 {{{
 #!CommitTicketReference repository="" revision="62293"
 I18N: Harden against undefined index in
 `_load_script_textdomain_from_src()`.

 This guards against an undefined index warning being raised when a script
 or script module is registered with a URL that lacks a path component.

 This also adds full PHPStan type definitions for `wp_parse_url()`,
 ensuring that the `_load_script_textdomain_from_src()` function has no
 PHPStan errors at rule level 10.

 Developed in https://github.com/WordPress/wordpress-develop/pull/11690

 Follow-up to r62278.

 Props westonruter, manzoorwanijk, mukesh27.
 See #65015, #64238.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64238#comment:125>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 05:56:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 05:56:06 -0000
Subject: [wp-trac] [WordPress Trac] #65015: Connectors: Several strings
 are not translated
In-Reply-To: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
References: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
Message-ID: <066.6b899484d5385e94cdff7657110c00c0@wordpress.org>

#65015: Connectors: Several strings are not translated
-------------------------------------------------+-------------------------
 Reporter:  369work                              |       Owner:
                                                 |  westonruter
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  high                                 |   Milestone:  7.0
Component:  I18N                                 |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests connectors  |     Focuses:
  commit needs-dev-note fixed-major dev-         |
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by westonruter):

 * keywords:
     has-patch has-unit-tests connectors commit needs-dev-note fixed-major
     dev-reviewed
     =>
     has-patch has-unit-tests connectors commit needs-dev-note fixed-major
     dev-feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Re-opening to backport follow-up [62293] to 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65015#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 06:10:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 06:10:24 -0000
Subject: [wp-trac] [WordPress Trac] #65157: Blocks: WordPress prevent
 videos from being set as backgrounds
In-Reply-To: <049.b5992ec627f0854820bdf57a9285b790@wordpress.org>
References: <049.b5992ec627f0854820bdf57a9285b790@wordpress.org>
Message-ID: <064.f89604f19f521951b2cd65bf84c1243f@wordpress.org>

#65157: Blocks: WordPress prevent videos from being set as backgrounds
-------------------------------+-------------------------------------------
 Reporter:  wurds              |       Owner:  (none)
     Type:  feature request    |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui, administration, template
-------------------------------+-------------------------------------------
Changes (by westonruter):

 * keywords:   => reporter-feedback
 * version:  6.9.4 =>


Comment:

 The Cover block actually does allow you to set a video as the background.

 Please try that block.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65157#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 08:48:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 08:48:50 -0000
Subject: [wp-trac] [WordPress Trac] #65124: Please include additional
 data validation in class-IXR-server.php
In-Reply-To: <057.4b26f520c07119a980e9344a815d2305@wordpress.org>
References: <057.4b26f520c07119a980e9344a815d2305@wordpress.org>
Message-ID: <072.ffca6f52e23fd12035d667b9d5343b6b@wordpress.org>

#65124: Please include additional data validation in class-IXR-server.php
---------------------------+--------------------------------
 Reporter:  eeeeeeeeeeeee  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  4.7
 Severity:  normal         |  Resolution:
 Keywords:  needs-patch    |     Focuses:  php-compatibility
---------------------------+--------------------------------
Changes (by yasirkhalifa):

 * Attachment "65124.patch" added.

 patch file

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65124>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 08:49:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 08:49:22 -0000
Subject: [wp-trac] [WordPress Trac] #65124: Please include additional
 data validation in class-IXR-server.php
In-Reply-To: <057.4b26f520c07119a980e9344a815d2305@wordpress.org>
References: <057.4b26f520c07119a980e9344a815d2305@wordpress.org>
Message-ID: <072.01bf42a1e5e70e9130585d0f6142a4a8@wordpress.org>

#65124: Please include additional data validation in class-IXR-server.php
---------------------------+--------------------------------
 Reporter:  eeeeeeeeeeeee  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  4.7
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  php-compatibility
---------------------------+--------------------------------
Changes (by yasirkhalifa):

 * keywords:  needs-patch => has-patch


Comment:

 Adds validation for malformed XML-RPC arguments before count() is called
 in IXR_Server, preventing fatal errors when non-countable values are
 received from invalid requests.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65124#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 10:56:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 10:56:05 -0000
Subject: [wp-trac] [WordPress Trac] #65078: get_page_by_title should not
 be deprecated
In-Reply-To: <056.d665d726d481dfa9f969409926dd87c1@wordpress.org>
References: <056.d665d726d481dfa9f969409926dd87c1@wordpress.org>
Message-ID: <071.4e2c89cf7d7608b6ab7d33e0b5005d3f@wordpress.org>

#65078: get_page_by_title should not be deprecated
-------------------------------+------------------------------
 Reporter:  hybridwebdev       |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:  6.2
 Severity:  normal             |  Resolution:
 Keywords:  close              |     Focuses:
-------------------------------+------------------------------
Changes (by SirLouen):

 * keywords:  2nd-opinion => close


Comment:

 > Finally, low level methods like this serve a specific purpose. They're
 not intended to catch edge cases. That responsibility is on the code that
 uses the method.

 These direct methods introduced some flaky issues very hard to maintain as
 suggested by @peterwilsoncc back in the day. I cannot see the problem of a
 more generalistic solution for this trivial thing.

 > Deprecating this function effectively requires developers to reimplement
 its logic. This leads to duplicated boilerplate and inconsistent
 implementations across codebases.

 It's a very trivial implementation, and deprecated things never fade in WP
 so you can basically keep using it despite you will get the deprecated
 messages in the log.

 The deprecation was for good, and many legacy things still need some
 degree of deprecation yet, but there isn't much time for devs to go
 through all of them.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65078#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 12:57:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 12:57:01 -0000
Subject: [wp-trac] [WordPress Trac] #62950: PHP deprecation warning in
 /wp-admin/includes/class-automatic-upgrader-skin.php
In-Reply-To: <053.b8c0bf70653bdc9905e117173b5f777c@wordpress.org>
References: <053.b8c0bf70653bdc9905e117173b5f777c@wordpress.org>
Message-ID: <068.a04d8b27c872a5e10c9c043ed65da435@wordpress.org>

#62950: PHP deprecation warning in /wp-admin/includes/class-automatic-upgrader-
skin.php
-----------------------------+------------------------------
 Reporter:  nexbridge        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  6.7.2
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by ankitv):

 The root cause is in the else branch — when $feedback is null, it gets
 assigned directly to $string, which then gets passed to str_contains()
 and trim(), both triggering PHP 8.2 deprecation warnings.

 Fix: cast $feedback to string in the else branch:

     $string = (string) $feedback;

 This coerces null to '' at the point of assignment, consistent with the
 @param string|array|WP_Error $feedback docblock.

 https://github.com/Anny0007/AV-wordpress-develop/pull/1/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62950#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 13:06:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 13:06:29 -0000
Subject: [wp-trac] [WordPress Trac] #62950: PHP deprecation warning in
 /wp-admin/includes/class-automatic-upgrader-skin.php
In-Reply-To: <053.b8c0bf70653bdc9905e117173b5f777c@wordpress.org>
References: <053.b8c0bf70653bdc9905e117173b5f777c@wordpress.org>
Message-ID: <068.e4800bec3c82489fe274ee0fdcd3a63a@wordpress.org>

#62950: PHP deprecation warning in /wp-admin/includes/class-automatic-upgrader-
skin.php
-----------------------------+------------------------------
 Reporter:  nexbridge        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  6.7.2
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+------------------------------
Changes (by ankitv):

 * keywords:   => has-patch


Comment:

 Could a contributor please update the keywords to has-patch?
 Patch is available via PR: https://github.com/Anny0007/AV-wordpress-
 develop/pull/1/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62950#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 15:35:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 15:35:30 -0000
Subject: [wp-trac] [WordPress Trac] #64984: reply needs gettext
In-Reply-To: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
References: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
Message-ID: <067.35fe6a10fe524752a95ebb8f89458a6a@wordpress.org>

#64984: reply needs gettext
------------------------------+-----------------------
 Reporter:  timse201          |       Owner:  audrasjb
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  7.0
Component:  I18N              |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------

Comment (by shailu25):

 Gutenberg PR Link [https://github.com/WordPress/gutenberg/pull/77891
 77891]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64984#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  2 22:45:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 02 May 2026 22:45:11 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.c51d9146d7775fdb997d1a84bc3ed45b@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
------------------------------------+---------------------
 Reporter:  wildworks               |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  7.0
Component:  General                 |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  admin-reskin has-patch  |     Focuses:
------------------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"62294" 62294]:
 {{{
 #!CommitTicketReference repository="" revision="62294"
 Admin Reskin: Standardize theme install overlay button height on mobile.

 Follow-up to [61646].

 Props abcd95, wildworks, mosescursor, sainathpoojary, SergeyBiryukov.
 See #64999.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 00:18:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 00:18:59 -0000
Subject: [wp-trac] [WordPress Trac] #65130: Plugin search (term) in
 wp-admin lacks normalization, causing fragile keyword matching
In-Reply-To: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
References: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
Message-ID: <066.169944fc3ae41940b3f3bcd5190d4dd6@wordpress.org>

#65130: Plugin search (term) in wp-admin lacks normalization, causing fragile
keyword matching
----------------------------+------------------------------
 Reporter:  369work         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:
----------------------------+------------------------------
Changes (by yusufmudagal):

 * Attachment "65130.diff" added.

 Patch to normalize plugin keyword search terms by stripping spaces/hyphens
 before sending the query to the WordPress.org Plugin API.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65130>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 01:11:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 01:11:30 -0000
Subject: [wp-trac] [WordPress Trac] #64924: Add a `has_ai_credentials()`
 function to WordPress core that plugins can use to check if AI credentials
 are available.
In-Reply-To: <055.27be0ae421a3dd47e68ac187c824a251@wordpress.org>
References: <055.27be0ae421a3dd47e68ac187c824a251@wordpress.org>
Message-ID: <070.6da26c9243d1eeeeac95778f0c3e42fb@wordpress.org>

#64924: Add a `has_ai_credentials()` function to WordPress core that plugins can
use to check if AI credentials are available.
----------------------------------------------+----------------------------
 Reporter:  raftaar1191                       |       Owner:  (none)
     Type:  enhancement                       |      Status:  new
 Priority:  normal                            |   Milestone:  Awaiting
                                              |  Review
Component:  AI                                |     Version:  trunk
 Severity:  normal                            |  Resolution:
 Keywords:  connectors ai-client 2nd-opinion  |     Focuses:
                                              |  sustainability
----------------------------------------------+----------------------------

Comment (by raftaar1191):

 @darshitrajyaguru97 are you working on this? if yes please let me know I
 can test it as well

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64924#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 12:11:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 12:11:30 -0000
Subject: [wp-trac] [WordPress Trac] #65144: Passwords: trim() asymmetry
 between wp_hash_password() and wp_check_password() introduced in 6.8
In-Reply-To: <055.d4a4047f036fcce65d14783e8d81d2c2@wordpress.org>
References: <055.d4a4047f036fcce65d14783e8d81d2c2@wordpress.org>
Message-ID: <070.031fa5567d19e159dc0010bba85410cf@wordpress.org>

#65144: Passwords: trim() asymmetry between wp_hash_password() and
wp_check_password() introduced in 6.8
--------------------------+------------------------------
 Reporter:  mkultraware   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.8
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------

Comment (by ankitv):

 The asymmetry is in the bcrypt path only. wp_hash_password()
 calls trim() before hash_hmac() but wp_check_password() does not,
 causing login failures for passwords with leading/trailing
 whitespace when wp_check_password() is called directly.

 Fix: add trim() to the password argument in wp_check_password()
 to match wp_hash_password().


 Patch submitted via PR: https://github.com/Anny0007/AV-wordpress-
 develop/pull/2

 Please update keywords to has-patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65144#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 14:39:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 14:39:32 -0000
Subject: [wp-trac] [WordPress Trac] #65158: Tortoise appears to be granting
 access to folders that don't belong to the user
Message-ID: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>

#65158: Tortoise appears to be granting access to folders that don't belong to the
user
--------------------------+-----------------------------
 Reporter:  pontocinza    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  6.9.4
 Severity:  major         |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 I don't know what happened, but it seems to be entirely wrong.

 First image: my own folder.
 Second image: a glimpse on a folder that don't belong to me.

 If this is nothing to worry about, I apologize for opening this ticket.
 I'm using Windows 10 and the latest version of Tortoise.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65158>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 14:40:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 14:40:14 -0000
Subject: [wp-trac] [WordPress Trac] #65158: Tortoise appears to be
 granting access to folders that don't belong to the user
In-Reply-To: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
References: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
Message-ID: <069.593336733a261ff82b0b0cff3a281c63@wordpress.org>

#65158: Tortoise appears to be granting access to folders that don't belong to the
user
--------------------------+------------------------------
 Reporter:  pontocinza    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  major         |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by pontocinza):

 * Attachment "2026-05-03_112055.png" added.

 My own folder.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65158>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 14:41:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 14:41:21 -0000
Subject: [wp-trac] [WordPress Trac] #65158: Tortoise appears to be
 granting access to folders that don't belong to the user
In-Reply-To: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
References: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
Message-ID: <069.7f6b27a601882b8981c86eb0c139cf0c@wordpress.org>

#65158: Tortoise appears to be granting access to folders that don't belong to the
user
--------------------------+------------------------------
 Reporter:  pontocinza    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  major         |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by pontocinza):

 * Attachment "2026-05-03_112116.png" added.

 This folder doesn't belong to me.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65158>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 16:02:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 16:02:25 -0000
Subject: [wp-trac] [WordPress Trac] #65158: Tortoise appears to be
 granting access to folders that don't belong to the user
In-Reply-To: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
References: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
Message-ID: <069.717f439f96e5a93c8d8a05cd4f2e5739@wordpress.org>

#65158: Tortoise appears to be granting access to folders that don't belong to the
user
--------------------------+------------------------------
 Reporter:  pontocinza    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  major         |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by pontocinza):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 I apologize for opening this ticket. After further investigation, I
 realized that the WordPress.org SVN repository is public and read-
 accessible to everyone by design. What I saw was simply another plugin's
 folder in the public repository. iT's not a security issue. I'm closing
 this ticket as invalid. Sorry for the noise.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65158#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 19:11:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 19:11:06 -0000
Subject: [wp-trac] [WordPress Trac] #65003: next/prev for enlarged image
 needs context
In-Reply-To: <052.b63525ba9b3238159791aa05ff965555@wordpress.org>
References: <052.b63525ba9b3238159791aa05ff965555@wordpress.org>
Message-ID: <067.5223a6cf98e2738d5d7e8ffe325a996c@wordpress.org>

#65003: next/prev for enlarged image needs context
--------------------------+---------------------
 Reporter:  timse201      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0
Component:  I18N          |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+---------------------
Changes (by yusufmudagal):

 * Attachment "65003.diff" added.

 Add translation context for the Previous and Next lightbox navigation
 labels.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65003>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 19:11:55 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 19:11:55 -0000
Subject: [wp-trac] [WordPress Trac] #65073: Connectors: reference to AI
 plugin uses old `ai` slug instead of correct `ai-wp-admin` slug
In-Reply-To: <052.ad97c034b09747ca93f06d7293e387ff@wordpress.org>
References: <052.ad97c034b09747ca93f06d7293e387ff@wordpress.org>
Message-ID: <067.a5dd4fdc3d223c5b75898233b31f7e1a@wordpress.org>

#65073: Connectors: reference to AI plugin uses old `ai` slug instead of correct
`ai-wp-admin` slug
------------------------------+-----------------------
 Reporter:  JeffPaul          |       Owner:  dkotter
     Type:  defect (bug)      |      Status:  assigned
 Priority:  normal            |   Milestone:  7.0
Component:  AI                |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  connectors close  |     Focuses:
------------------------------+-----------------------
Changes (by yusufmudagal):

 * Attachment "65073.diff" added.

 Update the AI plugin reference from the old ai slug to the correct ai-wp-
 admin slug in connectors home.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65073>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 19:30:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 19:30:00 -0000
Subject: [wp-trac] [WordPress Trac] #64977: The `core/get-site-info`
 ability returns wrong locale code in the admin
In-Reply-To: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
References: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
Message-ID: <066.5235577657329428fbbd8e3a75d7b83a@wordpress.org>

#64977: The `core/get-site-info` ability returns wrong locale code in the admin
---------------------------------+---------------------
 Reporter:  afercia              |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  7.1
Component:  Abilities API        |     Version:  6.9
 Severity:  normal               |  Resolution:
 Keywords:  abilities has-patch  |     Focuses:
---------------------------------+---------------------

Comment (by yusufmudagal):

 Tested PR https://github.com/WordPress/wordpress-develop/pull/11388

 In a local test environment, I set the site locale to `it_IT` and the
 admin user locale to `es_ES`.

 Before the patch, `wp_get_ability( 'core/get-site-info' )->execute()`
 returned `language => es` in admin context.
 After the patch, the same ability returned `language => it-IT`, matching
 the site locale instead of the user locale.

 Patch tests well for me.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64977#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 19:30:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 19:30:15 -0000
Subject: [wp-trac] [WordPress Trac] #65084: Update error message for
 disallowed username characters
In-Reply-To: <049.08ea48590412276562d442dabf255033@wordpress.org>
References: <049.08ea48590412276562d442dabf255033@wordpress.org>
Message-ID: <064.edc9fe4c2154cac4e2f5b5cc3f6f8da9@wordpress.org>

#65084: Update error message for disallowed username characters
-------------------------------------------------+-------------------------
 Reporter:  Marc4                                |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch reporter-feedback has-     |     Focuses:  ui-copy
  unit-tests needs-refresh                       |
-------------------------------------------------+-------------------------

Comment (by yusufmudagal):

 Tested PR https://github.com/WordPress/wordpress-develop/pull/11668

 Before the patch, invalid username messages used "illegal characters" in
 both `register_new_user()` and
 `WP_REST_Users_Controller::check_username()`.
 After the patch, both now say "disallowed characters".

 Patch tests well for me.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65084#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 19:30:23 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 19:30:23 -0000
Subject: [wp-trac] [WordPress Trac] #52976: user emails comparison
 should be case insensitive
In-Reply-To: <050.7727b644129a97f4082fdf76cb8aa740@wordpress.org>
References: <050.7727b644129a97f4082fdf76cb8aa740@wordpress.org>
Message-ID: <065.daaced886b45a2318aa1d235f5373d3c@wordpress.org>

#52976: user emails comparison should be case insensitive
-------------------------------------+-------------------------------------
 Reporter:  asaifm                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Users                    |     Version:  4.3
 Severity:  normal                   |  Resolution:
 Keywords:  good-first-bug has-      |     Focuses:  administration,
  patch has-screenshots has-unit-    |  coding-standards
  tests                              |
-------------------------------------+-------------------------------------

Comment (by yusufmudagal):

 Tested PR https://github.com/WordPress/wordpress-develop/pull/11697

 I created a user with `testcase at example.com`, set `user_activation_key` to
 `key`, and then updated the email to `TestCase at Example.COM`.

 Before the patch, the `send_email_change_email` flow fired for this case-
 only change and the activation key was cleared.
 After the patch, the notification flow does not fire and the activation
 key remains `key`.

 Patch tests well for the case-only email change scenario.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52976#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 19:30:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 19:30:07 -0000
Subject: [wp-trac] [WordPress Trac] #65050: REST API: Comments
 controller returns 403 instead of 404 for invalid post ID in update_item()
In-Reply-To: <057.d01cd307fcdefb847d0c0d7b8f496018@wordpress.org>
References: <057.d01cd307fcdefb847d0c0d7b8f496018@wordpress.org>
Message-ID: <072.2a9e4954f31c87de75870432e3d35c6d@wordpress.org>

#65050: REST API: Comments controller returns 403 instead of 404 for invalid post
ID in update_item()
-----------------------------------------+-------------------------------
 Reporter:  saratheonline                |       Owner:  saratheonline
     Type:  defect (bug)                 |      Status:  assigned
 Priority:  normal                       |   Milestone:  7.1
Component:  REST API                     |     Version:  trunk
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch changes-requested  |     Focuses:  coding-standards
-----------------------------------------+-------------------------------

Comment (by yusufmudagal):

 Tested PR https://github.com/WordPress/wordpress-develop/pull/11529

 I created a post and comment locally, then called
 `WP_REST_Comments_Controller::update_item()` with that comment ID and
 `post => 999999`.

 Before the patch, the response was `rest_comment_invalid_post_id` with
 status `403`.
 After the patch, the same error code returns status `404`.

 This matches the behavior in `get_item()` and looks correct to me. Patch
 tests well.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65050#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 19:30:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 19:30:33 -0000
Subject: [wp-trac] [WordPress Trac] #65123: Having a malformed post type
 query in $_GET or $_POST yields a critical error
In-Reply-To: <055.29dc7cdfbf1c0409285d3c1ace563536@wordpress.org>
References: <055.29dc7cdfbf1c0409285d3c1ace563536@wordpress.org>
Message-ID: <070.b83fe7ee95fd468d3dfb385d7831edff@wordpress.org>

#65123: Having a malformed post type query in $_GET or $_POST yields a critical
error
--------------------------------------+---------------------
 Reporter:  hheuzebrutc               |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Permalinks                |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by yusufmudagal):

 Tested PR https://github.com/WordPress/wordpress-develop/pull/11650

 Before the patch, passing a non-scalar `attachment` value to
 `WP_Query::parse_query()` set `is_attachment` and `is_single`, and
 constructing a custom post type query with an array query var triggered a
 fatal error in `sanitize_title_for_query()`.
 After the patch, `attachment` is normalized to an empty string, both flags
 remain false, and the custom post type query completes without a fatal
 error.

 Patch tests well for me.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65123#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 20:09:36 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 20:09:36 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.3a8745e3b5a9ec1b6eb9567fc02ea8f8@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+-------------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  closed
 Priority:  normal                        |   Milestone:  7.0
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:  worksforme
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+-------------------------
Changes (by rafaeldella):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 Hello @yusufmudagal ,
 I tested this on my local environment (running WordPress 7.0-alpha/trunk)
 and was unable to reproduce the issue. In my case, the Dashboard widgets
 are draggable and behave as expected across all columns.
 You can see the screen recording of my test here:
 [https://vimeo.com/1188861508/e37502ff31]

 Environment details:
 * OS: Windows 10 (WSL2)
 * Browser: Chrome
 * Local Setup: wp-env / Docker

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 20:10:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 20:10:29 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.5b19f9ac54602bf7afa69c8982f62f56@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+-----------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  reopened
 Priority:  normal                        |   Milestone:  7.0
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+-----------------------
Changes (by rafaeldella):

 * status:  closed => reopened
 * resolution:  worksforme =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 20:15:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 20:15:11 -0000
Subject: [wp-trac] [WordPress Trac] #65158: Tortoise appears to be
 granting access to folders that don't belong to the user
In-Reply-To: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
References: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
Message-ID: <069.8153ed8a40c29ee67fea156294a32df3@wordpress.org>

#65158: Tortoise appears to be granting access to folders that don't belong to the
user
--------------------------+------------------------------
 Reporter:  pontocinza    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  major         |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by tobifjellner):

 @pontocinza
 A couple of comments for next time:
 1. Bugs/feature requests for the wordpress.org sites would rather belong
 under https://meta.trac.wordpress.org/
 2. If you believe you've stumbled upon a security issue in WordPress core
 or the wordpress.org network, then you should not report it publicly, but
 instead use https://hackerone.com/wordpress - this would allow the
 security team to investigate and fix problems before they get widely
 known.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65158#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 20:50:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 20:50:28 -0000
Subject: [wp-trac] [WordPress Trac] #64986: preview needs gettext
In-Reply-To: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
References: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
Message-ID: <067.4394fc34555acf9cccb8c2188422fa12@wordpress.org>

#64986: preview needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch changes-    |     Focuses:
  requested                                      |  accessibility
-------------------------------------------------+-------------------------

Comment (by rafaeldella):

 I tested PR #11700 in my local environment (WordPress 7.0-alpha/trunk via
 wp-env).

 I've verified the changes in the source code (e.g., in the post list
 table) and confirmed that the _x() function is now correctly implementing
 context for the "Preview" strings. I also navigated through the dashboard
 (Posts, Editor, and Themes) and everything is working perfectly. No
 regressions were found.

 My environment:
 * OS: Windows 10 (WSL2)
 * Browser: Chrome
 * Setup: Docker / wp-en

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64986#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 21:47:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 21:47:12 -0000
Subject: [wp-trac] [WordPress Trac] #65158: Tortoise appears to be
 granting access to folders that don't belong to the user
In-Reply-To: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
References: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
Message-ID: <069.41c273b191236acf507b4550ff32133f@wordpress.org>

#65158: Tortoise appears to be granting access to folders that don't belong to the
user
--------------------------+------------------------------
 Reporter:  pontocinza    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  major         |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by pontocinza):

 Understood. Thank you.

 Replying to [comment:2 tobifjellner]:
 > @pontocinza
 > A couple of comments for next time:
 > 1. Bugs/feature requests for the wordpress.org sites would rather belong
 under https://meta.trac.wordpress.org/
 > 2. If you believe you've stumbled upon a security issue in WordPress
 core or the wordpress.org network, then you should not report it publicly,
 but instead use https://hackerone.com/wordpress - this would allow the
 security team to investigate and fix problems before they get widely
 known.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65158#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 22:16:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 22:16:46 -0000
Subject: [wp-trac] [WordPress Trac] #65046: get_weekstartend() has
 swapped variable names and comments for month and day
In-Reply-To: <057.a04ab5ef592944628bef1cd9cd93c2e5@wordpress.org>
References: <057.a04ab5ef592944628bef1cd9cd93c2e5@wordpress.org>
Message-ID: <072.02cc1f8f22ed844bc8dae0c236aaafd0@wordpress.org>

#65046: get_weekstartend() has swapped variable names and comments for month and
day
-------------------------------------+-------------------------------------
 Reporter:  saratheonline            |       Owner:  westonruter
     Type:  defect (bug)             |      Status:  reviewing
 Priority:  normal                   |   Milestone:  7.1
Component:  Date/Time                |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  sustainability,
  commit                             |  coding-standards
-------------------------------------+-------------------------------------
Changes (by westonruter):

 * keywords:  has-patch needs-testing => has-patch needs-testing commit
 * owner:  saratheonline => westonruter
 * status:  assigned => reviewing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65046#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 22:36:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 22:36:18 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2364689=3A_Customizer_?=
 =?utf-8?q?=E2=80=9CPublish=E2=80=9D_button_size_appears_larger_in_7=2E0_c?=
 =?utf-8?q?ompared_to_6=2E9=2E1?=
In-Reply-To: <052.73b260729ea404b08fe598cc7f376a7e@wordpress.org>
References: <052.73b260729ea404b08fe598cc7f376a7e@wordpress.org>
Message-ID: <067.f6b129e159cc362f8d3ee1c3950e643a@wordpress.org>

#64689: Customizer “Publish” button size appears larger in 7.0 compared to 6.9.1
--------------------------------+-----------------------------
 Reporter:  mohitbsf            |       Owner:  SergeyBiryukov
     Type:  defect (bug)        |      Status:  closed
 Priority:  normal              |   Milestone:  7.0
Component:  Customize           |     Version:  trunk
 Severity:  normal              |  Resolution:  fixed
 Keywords:  close admin-reskin  |     Focuses:  css
--------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62295" 62295]:
 {{{
 #!CommitTicketReference repository="" revision="62295"
 Admin Reskin: Correct Customizer “Publish” button size.

 Follow-up to [61646].

 Props mohitbsf, wildworks, joedolson, audrasjb, huzaifaalmesbah,
 SergeyBiryukov.
 Fixes #64689.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64689#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 22:37:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 22:37:20 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2364689=3A_Customizer_?=
 =?utf-8?q?=E2=80=9CPublish=E2=80=9D_button_size_appears_larger_in_7=2E0_c?=
 =?utf-8?q?ompared_to_6=2E9=2E1?=
In-Reply-To: <052.73b260729ea404b08fe598cc7f376a7e@wordpress.org>
References: <052.73b260729ea404b08fe598cc7f376a7e@wordpress.org>
Message-ID: <067.54c9dabfcf9f6969f571bd536a700697@wordpress.org>

#64689: Customizer “Publish” button size appears larger in 7.0 compared to 6.9.1
-------------------------------------------------+-------------------------
 Reporter:  mohitbsf                             |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Customize                            |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch commit dev-   |     Focuses:  css
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * keywords:  close admin-reskin => admin-reskin has-patch commit dev-
               feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for 7.0 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64689#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May  3 22:45:58 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 03 May 2026 22:45:58 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.66760a1d0aed6f591a5dfb216de2e199@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+-----------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  reopened
 Priority:  normal                        |   Milestone:  7.0
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+-----------------------

Comment (by siliconforks):

 Replying to [comment:6 rafaeldella]:
 > I tested this on my local environment (running WordPress
 7.0-alpha/trunk) and was unable to reproduce the issue. In my case, the
 Dashboard widgets are draggable and behave as expected across all columns.
 > You can see the screen recording of my test here:
 [https://vimeo.com/1188861508/e37502ff31]

 That looks like version 6.9.4.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 01:47:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 01:47:22 -0000
Subject: [wp-trac] [WordPress Trac] #65012: Fix: Register Akismet
 Anti-Spam as a connector
In-Reply-To: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
References: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
Message-ID: <075.139a436ab17c4022ec435cc141ec6fee@wordpress.org>

#65012: Fix: Register Akismet Anti-Spam as a connector
---------------------------------------------+-----------------------------
 Reporter:  jorgefilipecosta                 |       Owner:
                                             |  jorgefilipecosta
     Type:  feature request                  |      Status:  reopened
 Priority:  normal                           |   Milestone:  7.0
Component:  Plugins                          |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------------

Comment (by wildworks):

 The AI plugin callout section states, "Connect a provider below to
 generate featured images, alt text, titles, excerpts, and more." However,
 in my understanding, even if the Akismet API key is set, no AI features
 can be utilized. This could potentially confuse users. At the very least,
 the text in the callout section may need improvement.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65012#comment:55>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 02:34:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 02:34:46 -0000
Subject: [wp-trac] [WordPress Trac] #64683: _print_scripts should use
 the wp_inline_script_attributes filter
In-Reply-To: <051.b101eb3cd239e67d8a67df5ddf22e3ba@wordpress.org>
References: <051.b101eb3cd239e67d8a67df5ddf22e3ba@wordpress.org>
Message-ID: <066.80d853b4a01bc238f888e60943ec34dc@wordpress.org>

#64683: _print_scripts should use the wp_inline_script_attributes filter
---------------------------+--------------------------
 Reporter:  galaxor        |       Owner:  westonruter
     Type:  enhancement    |      Status:  accepted
 Priority:  normal         |   Milestone:  7.1
Component:  Script Loader  |     Version:  2.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+--------------------------
Changes (by westonruter):

 * owner:  (none) => westonruter
 * status:  new => accepted
 * focuses:   => javascript
 * version:  6.9.1 => 2.8
 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64683#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 02:36:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 02:36:44 -0000
Subject: [wp-trac] [WordPress Trac] #64683: _print_scripts should use
 the wp_inline_script_attributes filter
In-Reply-To: <051.b101eb3cd239e67d8a67df5ddf22e3ba@wordpress.org>
References: <051.b101eb3cd239e67d8a67df5ddf22e3ba@wordpress.org>
Message-ID: <066.e3df7510676c1360433a7c98f8a9066d@wordpress.org>

#64683: _print_scripts should use the wp_inline_script_attributes filter
---------------------------+-------------------------
 Reporter:  galaxor        |       Owner:  galaxor
     Type:  enhancement    |      Status:  assigned
 Priority:  normal         |   Milestone:  7.1
Component:  Script Loader  |     Version:  2.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+-------------------------
Changes (by westonruter):

 * owner:  westonruter => galaxor
 * status:  accepted => assigned


Comment:

 @galaxor Sorry for the delay. Yes, it would be great if `_print_scripts()`
 was updated to use `wp_print_inline_script_tag()` and
 `wp_print_script_tag()` instead of manually constructing the script tags.
 Please do open a PR.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64683#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 02:41:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 02:41:59 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.0654808124075683dba92da712b2d7de@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-----------------------------------------+-------------------------------
 Reporter:  iamadisingh                  |       Owner:  jorgefilipecosta
     Type:  defect (bug)                 |      Status:  closed
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  AI                           |     Version:  trunk
 Severity:  normal                       |  Resolution:  fixed
 Keywords:  connectors has-patch commit  |     Focuses:
-----------------------------------------+-------------------------------

Comment (by wildworks):

 Is [62288] intended to be backported to 7.0? If so, let's reopen this
 ticket.

 By the way, I discovered an issue on the Gutenberg plugin side where all
 default connectors are unintentionally considered "active" because the
 default connector does not have an `is_active` callback added. This should
 be fixed in https://github.com/WordPress/gutenberg/pull/77897.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 02:48:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 02:48:59 -0000
Subject: [wp-trac] [WordPress Trac] #32067: Remove inline javascript
 from WP-Core to allow CSP protection
In-Reply-To: <063.18fc05ba9c7fbd492e391e0defbcb68f@wordpress.org>
References: <063.18fc05ba9c7fbd492e391e0defbcb68f@wordpress.org>
Message-ID: <078.cb9c9427779a58dc642040473fef4d78@wordpress.org>

#32067: Remove inline javascript from WP-Core to allow CSP protection
---------------------------------+-----------------------------
 Reporter:  anonymized_14391430  |       Owner:  (none)
     Type:  feature request      |      Status:  assigned
 Priority:  normal               |   Milestone:  Future Release
Component:  Security             |     Version:
 Severity:  normal               |  Resolution:
 Keywords:  close                |     Focuses:  javascript
---------------------------------+-----------------------------
Changes (by westonruter):

 * keywords:   => close


Comment:

 I believe this is largely resolved with #39941 and #58664, with the
 exception of #64683 for concatenated scripts. Most scripts are now printed
 via `wp_get_inline_script_tag()` and `wp_get_script_tag()` which include
 filters for the attributes so that the CSP `nonce` can be inserted. This
 includes `wp_localize_script()`.

 What is remaining is #59446 to ensure that scripts constructed in the
 admin use the helper functions. Also, #51407 is open for tracking the
 removal of inline event handlers which cannot be marked as secure with
 nonces.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32067#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 02:50:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 02:50:02 -0000
Subject: [wp-trac] [WordPress Trac] #64683: _print_scripts should use
 the wp_inline_script_attributes filter
In-Reply-To: <051.b101eb3cd239e67d8a67df5ddf22e3ba@wordpress.org>
References: <051.b101eb3cd239e67d8a67df5ddf22e3ba@wordpress.org>
Message-ID: <066.66b4ab8129617bbc05674d2f1364d01c@wordpress.org>

#64683: _print_scripts should use the wp_inline_script_attributes filter
---------------------------+-------------------------
 Reporter:  galaxor        |       Owner:  galaxor
     Type:  enhancement    |      Status:  assigned
 Priority:  normal         |   Milestone:  7.1
Component:  Script Loader  |     Version:  2.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+-------------------------

Comment (by westonruter):

 Note that in #57548 we may discontinue script concatenation. But using the
 correct functions for printing scripts should be done here, and throughout
 the admin.

 For related tickets to enable CSP in the admin: #59446 and #51407.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64683#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 03:47:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 03:47:08 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.8ddf2debeb1adf14bb0afa81e95d5c22@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+-----------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  reopened
 Priority:  normal                        |   Milestone:  7.0
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+-----------------------
Changes (by siliconforks):

 * Attachment "65151-remove-overflow-hidden.diff" added.

 I noticed that removing `overflow: hidden` from the `#dashboard-widgets-
 wrap` element seems to make the drag and drop a lot less glitchy.  Anyone
 have any thoughts on whether it is safe to remove this?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 04:02:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 04:02:14 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.b4a4680ed66582a91a949426191d828f@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
------------------------------------+---------------------
 Reporter:  wildworks               |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  7.0
Component:  General                 |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  admin-reskin has-patch  |     Focuses:
------------------------------------+---------------------

Comment (by wildworks):

 I propose to backport [62294] to 7.0, as this will align the customizer's
 publish button with its size. See [62295].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 04:03:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 04:03:30 -0000
Subject: [wp-trac] [WordPress Trac] #64984: reply needs gettext
In-Reply-To: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
References: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
Message-ID: <067.f65889e56eb91ed014025bf444a8fa6a@wordpress.org>

#64984: reply needs gettext
------------------------------+-----------------------
 Reporter:  timse201          |       Owner:  audrasjb
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  7.0
Component:  I18N              |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------

Comment (by wildworks):

 > Gutenberg PR Link [https://github.com/WordPress/gutenberg/pull/77891
 77891]

 The Gutenberg PR has been merged and backported to 7.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64984#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 04:35:23 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 04:35:23 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2364689=3A_Customizer_?=
 =?utf-8?q?=E2=80=9CPublish=E2=80=9D_button_size_appears_larger_in_7=2E0_c?=
 =?utf-8?q?ompared_to_6=2E9=2E1?=
In-Reply-To: <052.73b260729ea404b08fe598cc7f376a7e@wordpress.org>
References: <052.73b260729ea404b08fe598cc7f376a7e@wordpress.org>
Message-ID: <067.83305f2166a2aa7528cc37a9b5f66ebf@wordpress.org>

#64689: Customizer “Publish” button size appears larger in 7.0 compared to 6.9.1
-------------------------------------------------+-------------------------
 Reporter:  mohitbsf                             |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Customize                            |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch commit dev-   |     Focuses:  css
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  admin-reskin has-patch commit dev-feedback => admin-reskin
     has-patch commit dev-reviewed


Comment:

 r62295 approved for merge to the 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64689#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 05:08:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 05:08:54 -0000
Subject: [wp-trac] [WordPress Trac] #65130: Plugin search (term) in
 wp-admin lacks normalization, causing fragile keyword matching
In-Reply-To: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
References: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
Message-ID: <066.6c22a8d929a352417363ce962ffd8f36@wordpress.org>

#65130: Plugin search (term) in wp-admin lacks normalization, causing fragile
keyword matching
----------------------------+------------------------------
 Reporter:  369work         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+------------------------------
Changes (by 369work):

 * keywords:  needs-patch => has-patch


Comment:

 A patch has been attached by @yusufmudagal. Updating keyword to has-patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65130#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 05:25:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 05:25:00 -0000
Subject: [wp-trac] [WordPress Trac] #65130: Plugin search (term) in
 wp-admin lacks normalization, causing fragile keyword matching
In-Reply-To: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
References: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
Message-ID: <066.be9dd3c04f671cfa2db73a2ea6e8164e@wordpress.org>

#65130: Plugin search (term) in wp-admin lacks normalization, causing fragile
keyword matching
----------------------------+------------------------------
 Reporter:  369work         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+------------------------------

Comment (by 369work):

 Tested the patch on a local WordPress trunk installation.

 Results:
 - "multibyte" → WP Multibyte Patch found ✅
 - "multi byte" → WP Multibyte Patch found ✅
 - "multi-byte" → WP Multibyte Patch found ✅
 - "multi" → Too many results (5000+) to confirm, but no regression
 observed
 - "multi patch" → Not found ❌ (expected, as the API does not support
 multi-token matching)

 The patch works as intended for the core use case (space/hyphen
 normalization).
 The "multi patch" case would require server-side improvements, which is
 out of scope for this ticket as noted in the description.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65130#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 09:19:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 09:19:01 -0000
Subject: [wp-trac] [WordPress Trac] #65130: Plugin search (term) in
 wp-admin lacks normalization, causing fragile keyword matching
In-Reply-To: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
References: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
Message-ID: <066.cd10f28ced3d565b15b300749439b590@wordpress.org>

#65130: Plugin search (term) in wp-admin lacks normalization, causing fragile
keyword matching
-------------------------+------------------------------
 Reporter:  369work      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  administration
-------------------------+------------------------------
Changes (by sabernhardt):

 * keywords:  has-patch =>
 * focuses:   => administration
 * component:  Administration => Plugins
 * version:  trunk =>


Old description:

> == Problem ==
>
> The plugin search box in wp-admin (`Plugins > Add New`) produces
> unreliable results when searching by keyword (term). A user searching for
> "WP Multibyte Patch" gets very different results depending on minor
> variations in their query:
>
> | Query         | Result      |
> |---------------|-------------|
> | `multibyte`   | Found       |
> | `multi byte`  | Not found   |
> | `multi`       | Not found   |
> | `multi patch` | Not found   |
>
> The root cause is that the search term is passed to the WordPress.org
> Plugin API with no normalization whatsoever.
>
> == Root cause (confirmed in source) ==
>
> In `wp-admin/includes/class-wp-plugin-install-list-table.php`, the
> `prepare_items()` method handles the search tab as follows:
>
> {{{
> // Line 161-169
> $type = isset( $_REQUEST['type'] ) ? wp_unslash( $_REQUEST['type'] ) :
> 'term';
> $term = isset( $_REQUEST['s'] )    ? wp_unslash( $_REQUEST['s'] )    :
> '';
>
> switch ( $type ) {
>     case 'tag':
>         $args['tag'] = sanitize_title_with_dashes( $term ); // sanitized
>         break;
>     case 'term':
>         $args['search'] = $term; // ← NO processing at all
>         break;
>     case 'author':
>         $args['author'] = $term; // no processing
>         break;
> }
> }}}
>
> Note the inconsistency: the `tag` type applies
> `sanitize_title_with_dashes()`, which strips spaces and normalizes the
> string, while `term` (keyword search) receives NO processing. This
> asymmetry appears unintentional.
>
> The raw `$args` is then passed directly to `plugins_api( 'query_plugins',
> $args )`, which forwards the search string as-is to
> `https://api.wordpress.org/plugins/info/1.2/`.
>
> == Proposed fix ==
>
> The fix is a single line change in `class-wp-plugin-install-list-
> table.php`:
>
> {{{
> // Before (line 169):
> $args['search'] = $term;
>
> // After:
> $args['search'] = preg_replace( '/\s+/', '', $term );
> }}}
>
> This strips whitespace between words before sending the query to the API,
> so "multi byte" becomes "multibyte" — matching the plugin slug and name
> as indexed by WordPress.org.
>
> A more robust approach could also apply `sanitize_text_field()` for
> consistency with the `tag` type, and potentially send a secondary query
> with the original term to merge results.
>
> == Files affected ==
>
> * `wp-admin/includes/class-wp-plugin-install-list-table.php` — line 169
> (primary fix)
> * `wp-admin/includes/plugin-install.php` — `plugins_api()` (no change
> needed; normalization should happen before this call)
>
> == Note on server-side improvements ==
>
> Deeper fuzzy search improvements (stemming, partial matching, relevance
> ranking) would require changes on the Meta/Plugin Directory side
> (`api.wordpress.org`). This ticket focuses solely on the low-risk, one-
> line client-side normalization that can ship independently.

New description:

 == Problem ==

 The plugin search box in wp-admin (`Plugins > Add New`) produces
 unreliable results when searching by keyword (term). A user searching for
 "WP Multibyte Patch" gets very different results depending on minor
 variations in their query:

 ||= Query       =||= Result   =||
 || `multibyte`   || Found      ||
 || `multi byte`  || Not found  ||
 || `multi`       || Not found  ||
 || `multi patch` || Not found  ||

 The root cause is that the search term is passed to the WordPress.org
 Plugin API with no normalization whatsoever.

 == Root cause (confirmed in source) ==

 In `wp-admin/includes/class-wp-plugin-install-list-table.php`, the
 `prepare_items()` method handles the search tab as follows:

 {{{
 // Line 161-169
 $type = isset( $_REQUEST['type'] ) ? wp_unslash( $_REQUEST['type'] ) :
 'term';
 $term = isset( $_REQUEST['s'] )    ? wp_unslash( $_REQUEST['s'] )    : '';

 switch ( $type ) {
     case 'tag':
         $args['tag'] = sanitize_title_with_dashes( $term ); // sanitized
         break;
     case 'term':
         $args['search'] = $term; // ← NO processing at all
         break;
     case 'author':
         $args['author'] = $term; // no processing
         break;
 }
 }}}

 Note the inconsistency: the `tag` type applies
 `sanitize_title_with_dashes()`, which strips spaces and normalizes the
 string, while `term` (keyword search) receives NO processing. This
 asymmetry appears unintentional.

 The raw `$args` is then passed directly to `plugins_api( 'query_plugins',
 $args )`, which forwards the search string as-is to
 `https://api.wordpress.org/plugins/info/1.2/`.

 == Proposed fix ==

 The fix is a single line change in `class-wp-plugin-install-list-
 table.php`:

 {{{
 // Before (line 169):
 $args['search'] = $term;

 // After:
 $args['search'] = preg_replace( '/\s+/', '', $term );
 }}}

 This strips whitespace between words before sending the query to the API,
 so "multi byte" becomes "multibyte" — matching the plugin slug and name as
 indexed by WordPress.org.

 A more robust approach could also apply `sanitize_text_field()` for
 consistency with the `tag` type, and potentially send a secondary query
 with the original term to merge results.

 == Files affected ==

 * `wp-admin/includes/class-wp-plugin-install-list-table.php` — line 169
 (primary fix)
 * `wp-admin/includes/plugin-install.php` — `plugins_api()` (no change
 needed; normalization should happen before this call)

 == Note on server-side improvements ==

 Deeper fuzzy search improvements (stemming, partial matching, relevance
 ranking) would require changes on the Meta/Plugin Directory side
 (`api.wordpress.org`). This ticket focuses solely on the low-risk, one-
 line client-side normalization that can ship independently.

--

Comment:

 65130.diff would introduce a new problem with some queries that work
 correctly now. If someone enters multiple words of the plugin name, the
 edited keyword search query could yield zero results.
 - "wp multibyte patch"
 - "wp multibyte"
 - "multibyte patch"

 I expect that keyword search queries for other plugins' names would have
 similar problems with the patch.

 In the case of WP Multibyte Patch, the plugin has more than one million
 installations. Many people successfully find it (possibly because more
 people would search for it in Japanese than in English).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65130#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 09:48:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 09:48:37 -0000
Subject: [wp-trac] [WordPress Trac] #65130: Plugin search (term) in
 wp-admin lacks normalization, causing fragile keyword matching
In-Reply-To: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
References: <051.fabd8d9a751389bbebe628cdcacd4b6b@wordpress.org>
Message-ID: <066.85b5b0f396c1f5c68e93d69b81b6e072@wordpress.org>

#65130: Plugin search (term) in wp-admin lacks normalization, causing fragile
keyword matching
-------------------------+------------------------------
 Reporter:  369work      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  administration
-------------------------+------------------------------

Comment (by 369work):

 Thank you for the review.
 You're right — stripping all spaces unconditionally breaks multi-word
 queries that already work (e.g. "wp multibyte patch"). That was a mistake
 in the proposed fix.
 Instead, I'd propose keeping the original $term for the first query, and
 only retrying with spaces/hyphens removed if the result is empty. This
 avoids breaking existing queries while still recovering zero-result cases
 caused by unintentional spacing.

 "wp multibyte patch" → first query succeeds ✅
 "multi byte" → fallback strips spaces → "multibyte" ✅

 That said, partial queries like "wp multi" or "multibyte-pa" can't be
 fixed this way — that would require prefix/partial matching on the
 api.wordpress.org side.
 If this direction seems reasonable, would it be worth pursuing a revised
 patch using the fallback approach?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65130#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 10:10:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 10:10:19 -0000
Subject: [wp-trac] [WordPress Trac] #65159: User deletion confirmation page
 never finishes loading in Chromium-based browsers;
 confirm button missing when it does load (works in Firefox)
Message-ID: <052.6d9af540221c58c5d7f4b9562d2ce240@wordpress.org>

#65159: User deletion confirmation page never finishes loading in Chromium-based
browsers; confirm button missing when it does load (works in Firefox)
--------------------------+-----------------------------
 Reporter:  sirlefou      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Users         |    Version:  6.9.4
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 == Summary
 When deleting a user from the WordPress admin, the confirmation page
 (`/wp-admin/users.php?action=delete&user=<ID>`) **never finishes loading**
 in Chromium-based browsers (Chrome, Edge, Brave, Opera), or takes an
 extremely long time to do so. When loading does eventually complete, **the
 “Confirm Deletion” button is missing from the rendered page**, making it
 impossible for the administrator to complete the action.

 The same flow works correctly and instantly in Firefox.

 No JavaScript error is logged in the DevTools console.


 == Steps to reproduce
 1. Log in to `/wp-admin` as an Administrator.
 2. Go to **Users → All Users**.
 3. Click **Delete** under a user (or use the **Delete** bulk action).
 4. The browser navigates to the deletion confirmation page.
 5. Wait.


 == Expected behavior
 The confirmation page loads quickly and displays the **Confirm Deletion**
 button (as it does in Firefox).


 == Actual behavior
 - The page load spinner runs indefinitely, or for tens of seconds /
 minutes.
 - If the page eventually finishes loading, the **Confirm Deletion** button
 is not present in the DOM.
 - The console reports no error.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65159>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 12:37:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 12:37:33 -0000
Subject: [wp-trac] [WordPress Trac] #22623: Some string tweaks -
 duplicity, context, mistake
In-Reply-To: <053.2bcc7b117c4d6ad5f95fc71abfcf9f97@wordpress.org>
References: <053.2bcc7b117c4d6ad5f95fc71abfcf9f97@wordpress.org>
Message-ID: <068.e47625930d6b061284d1788955745f15@wordpress.org>

#22623: Some string tweaks - duplicity, context, mistake
-------------------------------------+-------------------------------------
 Reporter:  pavelevap                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Future Release
Component:  Administration           |     Version:  3.0
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-unit-      |     Focuses:  administration,
  tests good-first-bug               |  multisite, ui-copy
-------------------------------------+-------------------------------------
Changes (by arifrahman1):

 * focuses:  ui-copy => administration, multisite, ui-copy


Comment:

 I have opened a Pull Request for this ticket on GitHub:
 https://github.com/WordPress/wordpress-develop/pull/11705

 **Changes made:**
 * **Improved Tone:** Updated informal strings like "Gimme a site!" to
 "Give me a site!" for a more professional tone.
 * **Added Context:** Replaced `_e()` with `_ex()` to provide 'Multisite
 signup' context for better translation clarity.
 * **Consistency:** Ensured the `$domain` variable is used correctly within
 the function.

 Please let me know if any further adjustments are needed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/22623#comment:38>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 12:54:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 12:54:02 -0000
Subject: [wp-trac] [WordPress Trac] #65160: Misleading error message on user
 screen actions, if no role has been selected
Message-ID: <053.1f519b6db1ee8564919c90337a59d520@wordpress.org>

#65160: Misleading error message on user screen actions, if no role has been
selected
--------------------------+-----------------------------
 Reporter:  Presskopp     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Users         |    Version:
 Severity:  normal        |   Keywords:
  Focuses:  ui            |
--------------------------+-----------------------------
 similar to #64659, when on `users.php` no bulk action and also no role was
 selected, and the 'Change' button gets pressed, an error maessage appears
 claiming "Please select a bulk action to perform.". It's misleading
 because the underlying issue is that no user has been selected. Even when
 you select a bulk action like "Send password reset", the same error
 message will appear, which totally makes no sense.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65160>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 13:55:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 13:55:15 -0000
Subject: [wp-trac] [WordPress Trac] #62622: Bump minimum PHP version to
 7.4
In-Reply-To: <054.0e8fc3c3ef21a16174aab98b36d22a1d@wordpress.org>
References: <054.0e8fc3c3ef21a16174aab98b36d22a1d@wordpress.org>
Message-ID: <069.19314cf04aceb128166cd6aaa357fa63@wordpress.org>

#62622: Bump minimum PHP version to 7.4
-------------------------------------------------+-------------------------
 Reporter:  justlevine                           |       Owner:
                                                 |  johnbillion
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests add-to-     |     Focuses:
  field-guide                                    |
-------------------------------------------------+-------------------------

Comment (by samiamnot):

 Updated for early May 2026 based on [https://wordpress.org/about/stats/
 WordPress stats]. The stats page changed design this month and no longer
 show anything below 7.0, so I will not longer be updating the older
 versions. The way the page calculates the figures seem to have changed as
 well, and show a much slower decline than in the past. This will hopefully
 be the last post on this ticket, with next month's stats posted to #64494.

 7.2 + 7.3 that are slated to be the next PHP versions no longer supported
 by WordPress, continued dropping and reached 3.47%, a reduction of 0.04%
 since last month.

 ||='''Month/Year'''=||='''PHP 7.2'''=||='''PHP 7.3'''=||='''PHP 7.2 +
 7.3'''=||
 ||Jul 2023|| 6.48|| 8.16|| '''14.64%'''||
 ||Aug 2023|| 5.64|| 7.62|| '''13.26%'''||
 ||Sep 2023|| 5.55|| 7.18|| '''12.73%'''||
 ||Oct 2023|| 5.31|| 6.87|| '''12.18%'''||
 ||Nov 2023|| 5.20|| 6.51|| '''11.71%'''||
 ||Dec 2023|| 5.08|| 6.17|| '''11.25%'''||
 ||Jan 2024|| 4.79|| 5.90|| '''10.69%'''||
 ||Feb 2024|| 4.67|| 5.54|| '''10.21%'''||
 ||Mar 2024|| 4.30|| 5.11|| '''9.41%'''||
 ||Apr 2024|| 3.80|| 4.79|| '''8.59%'''||
 ||May 2024|| 3.63|| 4.52|| '''8.15%'''||
 ||Jun 2024|| 3.46|| 4.30|| '''7.76%'''||
 ||Jul 2024|| 3.33|| 4.10|| '''7.43%'''||
 ||Aug 2024|| 3.18|| 3.90|| '''7.08%'''||
 ||Sep 2024|| 3.05|| 3.73|| '''6.78%'''||
 ||Oct 2024|| 2.93|| 3.56|| '''6.49%'''||
 ||Nov 2024|| 2.83|| 3.40|| '''6.23%'''||
 ||Dec 2024|| 2.76|| 3.26|| '''6.02%'''||
 ||Jan 2025|| 2.68|| 3.14|| '''5.82%'''||
 ||Feb 2025|| 2.63|| 3.04|| '''5.67%'''||
 ||Mar 2025|| 2.50|| 2.93|| '''5.43%'''||
 ||Apr 2025|| 2.39|| 2.77|| '''5.16%'''||
 ||May 2025|| 2.30|| 2.67|| '''4.97%'''||
 ||Jun 2025|| 2.22|| 2.56|| '''4.78%'''||
 ||Jul 2025|| 2.16|| 2.47|| '''4.63%'''||
 ||Aug 2025|| 2.11|| 2.42|| '''4.53%'''||
 ||Sep 2025|| 2.05|| 2.34|| '''4.39%'''||
 ||Oct 2025|| 1.99|| 2.26|| '''4.25%'''||
 ||Nov 2025|| 1.93|| 2.19|| '''4.12%'''||
 ||Dec 2025|| 1.87|| 2.11|| '''3.98%'''||
 ||Jan 2026|| 1.82|| 2.05|| '''3.87%'''||
 ||Feb 2026|| 1.77|| 1.99|| '''3.76%'''||
 ||Mar 2026|| 1.72|| 1.91|| '''3.63%'''||
 ||Apr 2026|| 1.68|| 1.83|| '''3.51%'''||
 ||May 2026|| 1.67|| 1.81|| '''3.47%'''||

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62622#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 14:25:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 14:25:07 -0000
Subject: [wp-trac] [WordPress Trac] #65161: Give an error message when a
 non-image is uploaded for site icon
Message-ID: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>

#65161: Give an error message when a non-image is uploaded for site icon
--------------------------+-----------------------------
 Reporter:  Presskopp     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Media         |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Just like #39625, when you are on `General Settings` to `Choose a Site
 Icon`, then choose `Upload files` and select a non-image file, you'll get
 to a ugly looking page showing a non helping error message. See attached
 video.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65161>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 14:25:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 14:25:19 -0000
Subject: [wp-trac] [WordPress Trac] #65161: Give an error message when a
 non-image is uploaded for site icon
In-Reply-To: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
References: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
Message-ID: <068.407313f29ea0c573042bebfc4276ace0@wordpress.org>

#65161: Give an error message when a non-image is uploaded for site icon
--------------------------+------------------------------
 Reporter:  Presskopp     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by Presskopp):

 * Attachment "non-image.mp4" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65161>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 14:25:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 14:25:39 -0000
Subject: [wp-trac] [WordPress Trac] #39625: Give an error message when a
 non-image is uploaded for featured image
In-Reply-To: <054.0f5337fc17e748a8726bef1b9555ab81@wordpress.org>
References: <054.0f5337fc17e748a8726bef1b9555ab81@wordpress.org>
Message-ID: <069.6f4f392a80261edebe9b1c92d5708269@wordpress.org>

#39625: Give an error message when a non-image is uploaded for featured image
-------------------------------------------------+-------------------------
 Reporter:  karmatosed                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-screenshots          |     Focuses:
  changes-requested                              |
-------------------------------------------------+-------------------------

Comment (by Presskopp):

 related: #65161

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39625#comment:29>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 15:35:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 15:35:25 -0000
Subject: [wp-trac] [WordPress Trac] #65162: /wp-includes/theme.json, line 296
Message-ID: <050.97bb4ff393b639a25a1fe617d4592e3d@wordpress.org>

#65162: /wp-includes/theme.json, line 296
--------------------------+-----------------------------
 Reporter:  jlwilz        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Formatting    |    Version:  6.9.4
 Severity:  normal        |   Keywords:  needs-patch
  Focuses:                |
--------------------------+-----------------------------
 /wp-includes/theme.json, line 296

 The fallback theme.json file in in WordPress core includes explicit values
 for button text and background colors. These are applied in front-end CSS,
 causing buttons to be styled with these colors even when neither the theme
 nor the user has selected a value. This is an overly opinionated default
 that, due to CSS specificity rules, also risks breaking existing themes in
 a way that is not easy to diagnose or remedy.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65162>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 17:25:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 17:25:22 -0000
Subject: [wp-trac] [WordPress Trac] #64066: Speculative Loading: Change
 default eagerness from conservative to moderate when caching is detected
In-Reply-To: <055.974cf881d7a7e6cda196590bc4005f8a@wordpress.org>
References: <055.974cf881d7a7e6cda196590bc4005f8a@wordpress.org>
Message-ID: <070.5a70e5c5db72fd1d567a347de1bb9c71@wordpress.org>

#64066: Speculative Loading: Change default eagerness from conservative to moderate
when caching is detected
-------------------------------------+-------------------------------------
 Reporter:  westonruter              |       Owner:  westonruter
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  Future Release
Component:  General                  |     Version:  6.8
 Severity:  normal                   |  Resolution:
 Keywords:  2nd-opinion has-patch    |     Focuses:  performance,
  early has-unit-tests               |  sustainability
-------------------------------------+-------------------------------------

Comment (by westonruter):

 Some key Shopify data that @gilbertococchi shared:
 [https://performance.shopify.com/blogs/blog/faster-storefront-navigations-
 with-moderate-speculation-rules Faster storefront navigations with
 moderate speculation rules]

 > The desktop result is the one that stands out. Across the curve, the
 median gain is -285ms TTFB, -224ms FCP, and -228ms LCP. Median TTFB for a
 speculated navigation is now close to zero, which means the HTML response
 often arrives before the buyer even commits to clicking. For roughly 10%
 of speculated navigations, TTFB is exactly 0: the response is already
 sitting in the cache when the navigation fires.

 Gains for mobile are less, as expected, due to the lack of a link hover
 heuristic.

 As for the increase in pages served due unused speculations:

 > Prefetching earlier means the browser occasionally fetches a page the
 buyer never ends up visiting. At the same volume of actual page views,
 moderate triggers nearly 4x as many speculated requests as conservative on
 desktop, while on mobile the volume barely moves. In our case, that
 translated to about a 14% increase in the total number of HTML requests.
 Those numbers will depend on multiple factors: share of same-site
 navigations and browser mix, to name a few. The desktop-versus-mobile gap
 is also wide enough to raise a question: should the API let authors set a
 different eagerness per device type?
 >
 > For us, the tradeoff is acceptable from both infrastructure and user
 perspectives. Still, your mileage may vary.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64066#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 17:29:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 17:29:07 -0000
Subject: [wp-trac] [WordPress Trac] #65163: Force URLs/URIs of Posts and
 Feeds to Redirect (301) to All Lowercase
Message-ID: <055.90b8fe4d2faca78d7632413df74e3cb8@wordpress.org>

#65163: Force URLs/URIs of Posts and Feeds to Redirect (301) to All Lowercase
--------------------------+-----------------------------
 Reporter:  chiarella86   |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  6.9.4
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Two problems exist with the current WordPress setup:

 1. An otherwise correct write-up of an RSS feed that has some uppercase
 letters will result in a 404. This is very bad for user experience. I can
 set up redirects to ignore casing for the “wrong” version for the redirect
 (so that `/feed/`, `/FEED/`, `/Feed/`, and `/fEed` can go to `/feed`^1),
 but if I have a redirect that ignores casing on `/feed` and redirects to
 `/feed` or make a redirect that ignores casing and trailing slash for
 `/feed` or `/feed/` that redirects to `/feed`, then I have created a loop.
 An infinite loop creates breakage because “Ignore Case” will also redirect
 the correct version to itself, and then again to itself, and yet again, ad
 infinitum.
   I have no way to redirect all instances except the correct one. I can
 only redirect URLs/URIs that have right or wrong casing *and also* the
 wrong presence or absence of a trailing slash.

 2. All posts, regular posts, create duplicates with the wrong case. This
 means that `https://www.example.com/bar` and `https://www.example.com/Bar`
 both exist, and that destroys page ranking. Incorrect absence of a
 trailing slash will 301 to the other version, but it will not fix the
 casing. If the presence or absence of a trailing slash is right, then
 nothing happens not all. The URL/URI goes through and the page loads a
 duplicate of the canonical version.

 **Hence, the site should force lowercase on everything (both feeds and
 posts, as well as pages).**

 I would even say it is good universally if the user knows that all media
 library assets must be in lowercase. (In a more complicated way, WordPress
 would have to rename all previously uploaded files and check for conflicts
 before flipping a mandatory switch, but that solution is a major request.)

 Thank you for your time.

 ^1: By the way, I set up permalinks etc. to not add a trailing slash.
 Also, I prefer the slash-less version of the feed(s), and WordPress makes
 both version anyway, and so I set up redirects there in any case, with the
 Redirection plugin from John Godley.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65163>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 17:53:43 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 17:53:43 -0000
Subject: [wp-trac] [WordPress Trac] #65161: Give an error message when a
 non-image is uploaded for site icon
In-Reply-To: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
References: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
Message-ID: <068.d7ad87d8cbeb159fac129a2f38928752@wordpress.org>

#65161: Give an error message when a non-image is uploaded for site icon
--------------------------+------------------------------
 Reporter:  Presskopp     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by sabernhardt):

 If someone uploads a text file (or other non-image) for a site icon and
 selects it, then the 'Crop image' dialog shows the `<img>` alternative
 text:
 > Image crop area preview. Requires mouse interaction.

 The button text remains the same as it was in the Upload part of the
 dialog, and clicking the button has no effect.
 - "Select" in the Customizer
 - "Set as Site Icon" in General Settings

 Interestingly, if I resize the window height while the dialog is on the
 'Crop image' step, the button text switches to "Crop image" and clicking
 that gives an error message.
 {{{
 <div class="upload-error">
         <span class="upload-error-filename word-wrap-break-
 word">sample.txt</span>
         <span class="upload-error-message">There has been an error
 cropping your image.</span>
 </div>
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65161#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 18:16:58 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 18:16:58 -0000
Subject: [wp-trac] [WordPress Trac] #65163: Force URLs/URIs of Posts and
 Feeds to Redirect (301) to All Lowercase
In-Reply-To: <055.90b8fe4d2faca78d7632413df74e3cb8@wordpress.org>
References: <055.90b8fe4d2faca78d7632413df74e3cb8@wordpress.org>
Message-ID: <070.2990d64ca696e6135d61459570755410@wordpress.org>

#65163: Force URLs/URIs of Posts and Feeds to Redirect (301) to All Lowercase
--------------------------+------------------------------
 Reporter:  chiarella86   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Description changed by sabernhardt:

Old description:

> Two problems exist with the current WordPress setup:
>
> 1. An otherwise correct write-up of an RSS feed that has some uppercase
> letters will result in a 404. This is very bad for user experience. I can
> set up redirects to ignore casing for the “wrong” version for the
> redirect (so that `/feed/`, `/FEED/`, `/Feed/`, and `/fEed` can go to
> `/feed`^1), but if I have a redirect that ignores casing on `/feed` and
> redirects to `/feed` or make a redirect that ignores casing and trailing
> slash for `/feed` or `/feed/` that redirects to `/feed`, then I have
> created a loop. An infinite loop creates breakage because “Ignore Case”
> will also redirect the correct version to itself, and then again to
> itself, and yet again, ad infinitum.
>   I have no way to redirect all instances except the correct one. I can
> only redirect URLs/URIs that have right or wrong casing *and also* the
> wrong presence or absence of a trailing slash.
>
> 2. All posts, regular posts, create duplicates with the wrong case. This
> means that `https://www.example.com/bar` and
> `https://www.example.com/Bar` both exist, and that destroys page ranking.
> Incorrect absence of a trailing slash will 301 to the other version, but
> it will not fix the casing. If the presence or absence of a trailing
> slash is right, then nothing happens not all. The URL/URI goes through
> and the page loads a duplicate of the canonical version.
>
> **Hence, the site should force lowercase on everything (both feeds and
> posts, as well as pages).**
>
> I would even say it is good universally if the user knows that all media
> library assets must be in lowercase. (In a more complicated way,
> WordPress would have to rename all previously uploaded files and check
> for conflicts before flipping a mandatory switch, but that solution is a
> major request.)
>
> Thank you for your time.
>
> ^1: By the way, I set up permalinks etc. to not add a trailing slash.
> Also, I prefer the slash-less version of the feed(s), and WordPress makes
> both version anyway, and so I set up redirects there in any case, with
> the Redirection plugin from John Godley.

New description:

 Two problems exist with the current WordPress setup:

 1. An otherwise correct write-up of an RSS feed that has some uppercase
 letters will result in a 404. This is very bad for user experience. I can
 set up redirects to ignore casing for the “wrong” version for the redirect
 (so that `/feed/`, `/FEED/`, `/Feed/`, and `/fEed` can go to
 `/feed`^[#note1 1]^), but if I have a redirect that ignores casing on
 `/feed` and redirects to `/feed` or make a redirect that ignores casing
 and trailing slash for `/feed` or `/feed/` that redirects to `/feed`, then
 I have created a loop. An infinite loop creates breakage because “Ignore
 Case” will also redirect the correct version to itself, and then again to
 itself, and yet again, ad infinitum. \\ \\
   I have no way to redirect all instances except the correct one. I can
 only redirect URLs/URIs that have right or wrong casing *and also* the
 wrong presence or absence of a trailing slash. \\ \\
 2. All posts, regular posts, create duplicates with the wrong case. This
 means that `https://www.example.com/bar` and `https://www.example.com/Bar`
 both exist, and that destroys page ranking. Incorrect absence of a
 trailing slash will 301 to the other version, but it will not fix the
 casing. If the presence or absence of a trailing slash is right, then
 nothing happens not all. The URL/URI goes through and the page loads a
 duplicate of the canonical version.

 **Hence, the site should force lowercase on everything (both feeds and
 posts, as well as pages).**

 I would even say it is good universally if the user knows that all media
 library assets must be in lowercase. (In a more complicated way, WordPress
 would have to rename all previously uploaded files and check for conflicts
 before flipping a mandatory switch, but that solution is a major request.)

 Thank you for your time.

 [=#note1 ^1^] By the way, I set up permalinks etc. to not add a trailing
 slash. Also, I prefer the slash-less version of the feed(s), and WordPress
 makes both version anyway, and so I set up redirects there in any case,
 with the Redirection plugin from John Godley.

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65163#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 20:01:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 20:01:42 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.600f8bcf3948eab3e6970b0a55c7ac73@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
------------------------------------+---------------------
 Reporter:  wildworks               |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  7.0
Component:  General                 |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  admin-reskin has-patch  |     Focuses:
------------------------------------+---------------------

Comment (by mosescursor):

 Replying to [comment:15 wildworks]:
 > I propose to backport [62294] to 7.0, as this will align the
 customizer's publish button with its size. See [62295].

 I will agree with @wildworks on this

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 20:08:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 20:08:14 -0000
Subject: [wp-trac] [WordPress Trac] #65099: Fix: Only auto register
 settings if the plugin the connector references is installed and active
In-Reply-To: <060.0b8a8e3426646ee12db1e6e829f3d840@wordpress.org>
References: <060.0b8a8e3426646ee12db1e6e829f3d840@wordpress.org>
Message-ID: <075.bacd9bac96c13b9b1b4490c2c37b2802@wordpress.org>

#65099: Fix: Only auto register settings if the plugin the connector references is
installed and active
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests commit      |     Focuses:
  dev-feedback fixed-major                       |
-------------------------------------------------+-------------------------
Changes (by JeffPaul):

 * keywords:  has-patch has-unit-tests commit => has-patch has-unit-tests
     commit dev-feedback fixed-major
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for merge to the 7.0 branch pending committer sign off.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65099#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 20:09:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 20:09:38 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.6d587e7f7c2c93e9b80bae5779ffd1c0@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  connectors has-patch commit has-     |     Focuses:
  unit-tests dev-feedback fixed-major            |
-------------------------------------------------+-------------------------
Changes (by JeffPaul):

 * keywords:  connectors has-patch commit has-unit-tests => connectors has-
     patch commit has-unit-tests dev-feedback fixed-major
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for merge to the 7.0 branch pending committer sign off.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 23:46:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 23:46:37 -0000
Subject: [wp-trac] [WordPress Trac] #64685: Bulk Edit dropdown height
 increased compared to previous version
In-Reply-To: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
References: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
Message-ID: <067.edbf22857b4febf964f000a48fe9d950@wordpress.org>

#64685: Bulk Edit dropdown height increased compared to previous version
-------------------------------------------+------------------------
 Reporter:  mohitbsf                       |       Owner:  joedolson
     Type:  defect (bug)                   |      Status:  closed
 Priority:  normal                         |   Milestone:  7.0
Component:  Quick/Bulk Edit                |     Version:  trunk
 Severity:  minor                          |  Resolution:  fixed
 Keywords:  admin-reskin has-patch commit  |     Focuses:  css
-------------------------------------------+------------------------
Changes (by SergeyBiryukov):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62296" 62296]:
 {{{
 #!CommitTicketReference repository="" revision="62296"
 Quick/Bulk Edit: Restore compact size of inline edit select.

 Follow-up to [61827], [62171].

 Props wildworks, mukesh27, audrasjb, SergeyBiryukov.
 Fixes #64685.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64685#comment:31>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May  4 23:47:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 04 May 2026 23:47:04 -0000
Subject: [wp-trac] [WordPress Trac] #64685: Bulk Edit dropdown height
 increased compared to previous version
In-Reply-To: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
References: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
Message-ID: <067.80c57a92f8ba9d9ca0f0c764690b5871@wordpress.org>

#64685: Bulk Edit dropdown height increased compared to previous version
-------------------------------------------------+-------------------------
 Reporter:  mohitbsf                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Quick/Bulk Edit                      |     Version:  trunk
 Severity:  minor                                |  Resolution:
 Keywords:  admin-reskin has-patch commit dev-   |     Focuses:  css
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * keywords:  admin-reskin has-patch commit => admin-reskin has-patch commit
     dev-feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for 7.0 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64685#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 03:07:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 03:07:02 -0000
Subject: [wp-trac] [WordPress Trac] #65162: /wp-includes/theme.json,
 line 296
In-Reply-To: <050.97bb4ff393b639a25a1fe617d4592e3d@wordpress.org>
References: <050.97bb4ff393b639a25a1fe617d4592e3d@wordpress.org>
Message-ID: <065.5c8a6b925635b195dd4eca2e9d1944ae@wordpress.org>

#65162: /wp-includes/theme.json, line 296
--------------------------+------------------------------
 Reporter:  jlwilz        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Themes        |     Version:  6.9.4
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by dd32):

 * component:  Formatting => Themes


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65162#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 03:12:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 03:12:17 -0000
Subject: [wp-trac] [WordPress Trac] #65164: Responsive styles for blocks
Message-ID: <057.94189ed46fcce5e0a926e370ea84412d@wordpress.org>

#65164: Responsive styles for blocks
---------------------------+-----------------------------
 Reporter:  isabel_brison  |      Owner:  (none)
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:  7.1
Component:  Editor         |    Version:  trunk
 Severity:  normal         |   Keywords:  gutenberg-merge
  Focuses:                 |
---------------------------+-----------------------------
 Tracking the needed core updates to implement responsive style states for
 blocks, as described in
 https://github.com/WordPress/gutenberg/issues/77817.

 The first part of the work in in
 https://github.com/WordPress/gutenberg/pull/77513.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65164>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 04:57:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 04:57:10 -0000
Subject: [wp-trac] [WordPress Trac] #64977: The `core/get-site-info`
 ability returns wrong locale code in the admin
In-Reply-To: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
References: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
Message-ID: <066.b2cb4b869ef48f5c3eb74f68010b84e7@wordpress.org>

#64977: The `core/get-site-info` ability returns wrong locale code in the admin
---------------------------------+---------------------
 Reporter:  afercia              |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  7.1
Component:  Abilities API        |     Version:  6.9
 Severity:  normal               |  Resolution:
 Keywords:  abilities has-patch  |     Focuses:
---------------------------------+---------------------

Comment (by r1k0):

 == Patch Testing Report

 Patch Tested: https://github.com/WordPress/wordpress-develop/pull/11502

 === Environment
 - WordPress: 7.1-alpha-62161-src
 - PHP: 8.3.30
 - Server: nginx/1.29.5
 - Database: mysqli (Server: 8.4.8 / Client: mysqlnd 8.3.30)
 - Browser: Chrome 147.0.0.0
 - OS: Windows 10/11
 - Theme: Twenty Twenty-Five 1.4
 - MU Plugins: None activated
 - Plugins:
   * Test Reports 1.2.1

 === Steps taken
 1. In WP Admin > Settings > General, set the Site Language to a language
 other than English, e.g., Italian.
 2. In WP Admin > Users > Profile, set the Language to a different language
 e.g., French.
 3. Used the code provided by the reporter and created a plugin.
 {{{#!php
 <?php
 /**
  * Plugin Name: Test Language Locale
  * Description: Difference in language locale
  * Version: 1.0
 */

 add_action( 'wp_footer', 'language_locale' );

 add_action( 'admin_footer', 'language_locale' );

 function language_locale () {
         $ability = wp_get_ability( 'core/get-site-info' );
         $result  = $ability->execute();
         var_dump( $result['language'] );
 }
 }}}
 4. Head over to the footer of the site on the frontend and observe the
 returned language before and after the patch.
 5. Head over to the admin dashboard, scroll down to the end of the page
 and observe the returned language before and after the patch.
 2. ✅ Patch is solving the problem

 === Expected result
 - The site locale should be returned in the admin dashboard instead of the
 user-specific admin locale.

 === Additional Notes
 - None

 === Screenshots/Screencast with results
 - Before:
 [[Image(https://i.ibb.co/bMPDq4Zf/language-locale-before.png)]]

 - After:
 [[Image(https://i.ibb.co/Xx2NMzTG/language-locale-after.png)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64977#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 05:49:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 05:49:37 -0000
Subject: [wp-trac] [WordPress Trac] #64685: Bulk Edit dropdown height
 increased compared to previous version
In-Reply-To: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
References: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
Message-ID: <067.3f32982b07518d22401ea197b7654d2a@wordpress.org>

#64685: Bulk Edit dropdown height increased compared to previous version
-------------------------------------------------+------------------------
 Reporter:  mohitbsf                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Quick/Bulk Edit                      |     Version:  trunk
 Severity:  minor                                |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:  css
-------------------------------------------------+------------------------
Changes (by wildworks):

 * keywords:  admin-reskin has-patch commit dev-feedback => admin-reskin
     has-patch dev-reviewed


Comment:

 [62296] seems to be good to backport to 7.0

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64685#comment:33>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 06:20:55 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 06:20:55 -0000
Subject: [wp-trac] [WordPress Trac] #65073: Connectors: reference to AI
 plugin uses old `ai` slug instead of correct `ai-wp-admin` slug
In-Reply-To: <052.ad97c034b09747ca93f06d7293e387ff@wordpress.org>
References: <052.ad97c034b09747ca93f06d7293e387ff@wordpress.org>
Message-ID: <067.4b2915203a0b81f358d57e8e5aebd278@wordpress.org>

#65073: Connectors: reference to AI plugin uses old `ai` slug instead of correct
`ai-wp-admin` slug
------------------------------+-----------------------
 Reporter:  JeffPaul          |       Owner:  dkotter
     Type:  defect (bug)      |      Status:  assigned
 Priority:  normal            |   Milestone:  7.0
Component:  AI                |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  connectors close  |     Focuses:
------------------------------+-----------------------

Comment (by wildworks):

 Thank you for your work on this, @yusufmudagal. However, this code is
 auto-generated by the build process, so it cannot be directly edited.

 This ticket does not require any action at this time. We will confirm the
 issue is resolved after the Gutenberg sync runs and then close it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65073#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 06:50:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 06:50:48 -0000
Subject: [wp-trac] [WordPress Trac] #65162: /wp-includes/theme.json,
 line 296
In-Reply-To: <050.97bb4ff393b639a25a1fe617d4592e3d@wordpress.org>
References: <050.97bb4ff393b639a25a1fe617d4592e3d@wordpress.org>
Message-ID: <065.743156997daf0bd02c27aba7d8949a7a@wordpress.org>

#65162: /wp-includes/theme.json, line 296
--------------------------+------------------------------
 Reporter:  jlwilz        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Themes        |     Version:  6.9.4
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by sukhendu2002):

 * keywords:  has-patch has-unit-tests =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65162#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 07:26:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 07:26:11 -0000
Subject: [wp-trac] [WordPress Trac] #65159: User deletion confirmation
 page never finishes loading in Chromium-based browsers;
 confirm button missing when it does load (works in Firefox)
In-Reply-To: <052.6d9af540221c58c5d7f4b9562d2ce240@wordpress.org>
References: <052.6d9af540221c58c5d7f4b9562d2ce240@wordpress.org>
Message-ID: <067.00b680afaf7f44a0dd56c639b13be653@wordpress.org>

#65159: User deletion confirmation page never finishes loading in Chromium-based
browsers; confirm button missing when it does load (works in Firefox)
-------------------------------------------+------------------------------
 Reporter:  sirlefou                       |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  new
 Priority:  normal                         |   Milestone:  Awaiting Review
Component:  Users                          |     Version:  6.9.4
 Severity:  normal                         |  Resolution:
 Keywords:  has-test-info has-screenshots  |     Focuses:
-------------------------------------------+------------------------------
Changes (by sukhendu2002):

 * keywords:   => has-test-info has-screenshots


Comment:

 == Reproduction Report
 === Description
 This report validates whether the issue can be reproduced.

 === Environment
 - WordPress: 6.9.4
 - PHP: 8.2.29
 - Server: nginx/1.26.1
 - Database: mysqli (Server: 8.0.35 / Client: mysqlnd 8.2.29)
 - Browser: Chrome 147.0.0.0
 - OS: macOS
 - Theme: Twenty Twenty-Five 1.4
 - MU Plugins: None activated
 - Plugins:
   * Test Reports 1.2.0

 === Actual Results
     1. ❌ Could not reproduce the issue.

 === Additional Notes
     - Navigated to Users → All Users → Delete on a user.
     - The confirmation page loaded immediately on all attempts.
     - The "Confirm Deletion" button was present and functional in the DOM.
     - Tested in Chrome and Brave — all loaded correctly.
     - No console errors observed.
     - Could not trigger the described loading spinner behavior or missing
 button

 === Supplemental Artifacts
 Screencast:
 https://utfs.io/f/o9kzPXfbC7I8pGiWUG7FQGtcloWL6Rhwq1nAHuSEJD9famjT

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65159#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 07:40:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 07:40:27 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.6c85f8cf3562c5ee12da8fc46dfa8055@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
------------------------------------+---------------------
 Reporter:  wildworks               |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  7.0
Component:  General                 |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  admin-reskin has-patch  |     Focuses:
------------------------------------+---------------------

Comment (by wildworks):

 It seems that [62294] can be backported to 7.0. However, please note that
 [62294] alone cannot close this ticket, as there are still many issues to
 address within this ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 08:04:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 08:04:51 -0000
Subject: [wp-trac] [WordPress Trac] #65159: User deletion confirmation
 page never finishes loading in Chromium-based browsers;
 confirm button missing when it does load (works in Firefox)
In-Reply-To: <052.6d9af540221c58c5d7f4b9562d2ce240@wordpress.org>
References: <052.6d9af540221c58c5d7f4b9562d2ce240@wordpress.org>
Message-ID: <067.379f668b74faf0cbec2c6aa20a44b573@wordpress.org>

#65159: User deletion confirmation page never finishes loading in Chromium-based
browsers; confirm button missing when it does load (works in Firefox)
-------------------------------------------+------------------------------
 Reporter:  sirlefou                       |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  new
 Priority:  normal                         |   Milestone:  Awaiting Review
Component:  Users                          |     Version:  6.9.4
 Severity:  normal                         |  Resolution:
 Keywords:  has-test-info has-screenshots  |     Focuses:
-------------------------------------------+------------------------------

Comment (by sirlefou):

 After further testing, this only happens if the user has content. Here is
 a video of the problem https://streamable.com/8y1q9l

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65159#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 09:17:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 09:17:46 -0000
Subject: [wp-trac] [WordPress Trac] #65159: User deletion confirmation
 page never finishes loading in Chromium-based browsers;
 confirm button missing when it does load (works in Firefox)
In-Reply-To: <052.6d9af540221c58c5d7f4b9562d2ce240@wordpress.org>
References: <052.6d9af540221c58c5d7f4b9562d2ce240@wordpress.org>
Message-ID: <067.2f6c1c63ff47d6694b206ffcbea229b1@wordpress.org>

#65159: User deletion confirmation page never finishes loading in Chromium-based
browsers; confirm button missing when it does load (works in Firefox)
-------------------------------------------+------------------------------
 Reporter:  sirlefou                       |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  new
 Priority:  normal                         |   Milestone:  Awaiting Review
Component:  Users                          |     Version:  6.9.4
 Severity:  normal                         |  Resolution:
 Keywords:  has-test-info has-screenshots  |     Focuses:
-------------------------------------------+------------------------------

Comment (by sukhendu2002):

 I’m still unable to reproduce the issue on my end, even when the user has
 associated content.

 [[Image(https://utfs.io/f/o9kzPXfbC7I8ndOufTX5c6RfIZKYukied2jX4gvoVAHpFzT8)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65159#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 09:43:55 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 09:43:55 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies may
 be unavailable on evaluation
Message-ID: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
---------------------------+--------------------
 Reporter:  jonsurrell     |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  7.0
Component:  Script Loader  |    Version:  trunk
 Severity:  normal         |   Keywords:
  Focuses:  javascript     |
---------------------------+--------------------
 [61587] / #61500 added `module_dependencies` to classic scripts, allowing
 for scripts to depend on registered modules.

 Scripts with module dependencies may throw:

 > TypeError: Failed to resolve module specifier 'example-module'


 For example:

 {{{#!php
 <?php
 wp_register_script_module(
     'example-module',
     '/path/to/example-module.mjs',
     array(),
     VERSION
 );
 wp_register_script(
     'test-script-module-dependency',
     false,
     array(),
     false,
     array(
         'module_dependencies' => array( 'example-module' ),

         // ‼️ Enabling one or both of these fixes the issue
         // 'in_footer' => true,
         // 'strategy' => 'defer',
     ),
 );

 wp_enqueue_script( 'test-script-module-dependency' );
 wp_add_inline_script(
     'test-script-module-dependency',
     <<<'JAVASCRIPT'
     (async () => {
         const m = await import('example-module');
         console.log(m);
     })();
     JAVASCRIPT
 );
 }}}

 This eagerly evaluated script will attempt to resolve the `'example-
 module'` module specifier before the importmap has been printed and will
 throw the above error. The HTML will be printed like this:

 {{{#!xml
 <head>
   <!-- … -->
   <script id="test-script-module-dependency-js-after">/*…*/</script>
 </head>
 <body>
   <!-- … -->
   <script type="importmap">{"imports":{"…":"…"}}</script>
 </body>
 }}}

 Note that the exact ordering depends on several conditions, such as
 whether the request is in the WP Admin area, or on the frontend whether or
 not a block theme is used. However, in my testing the importmap is
 consistently being printed after the dependent script.

 Note the comment in the example. It seems that if the dependent script is
 deferred or printed in the footer (or ideally, both) then the problem
 seems to be resolved because the importmap will have been printed already.

 Scripts dependencies on modules are a new feature planned for 7.0 added in
 [61587].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 10:03:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 10:03:06 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.39e443023005cf28208d7486d6e00927@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
---------------------------+-------------------------
 Reporter:  jonsurrell     |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  7.0
Component:  Script Loader  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+-------------------------

Comment (by jonsurrell):

 There is a difficult balance we've already observed with script modules
 and blocks where it's important to print the importmap late enough that
 all module dependencies have already been discovered, but early enough
 that it can be used by scripts and modules that require it.

 All major browsers now support multiple import maps with the notable
 exception of Firefox. Firefox 150 (the current version) has added support
 for multiple import maps, but it's behind a configuration flag that
 defaults to disabled.

 Using multiple import maps is ideal, allowing for multiple importmaps to
 be printed as necessary. [https://github.com/guybedford/es-module-shims
 There is a robust polyfill] that was already added ([57492]) and later
 removed ([58952]) due to good browser support for basic importmap
 functionality. It may be worth adding the polyfil for the multiple
 importmap support.

 -----

 Some possible paths forward in no particular order:

 a. Revert [61587] for 7.0, removing the script->module dependency feature
 and the bug.
 b. Add the polyfill and print multiple importmaps as needed.
 c. Always defer scripts that have a dependency on a script module. (This
 seems heavy handed and likely to introduce bugs.)
 d. Document the situation and do nothing. Scripts can depend on modules,
 but authors must understand this limitation and can apply workarounds such
 as deferring their script or waiting for `DOMContentLoaded` before
 attempting to import a module. (This seems undesirable for a number of
 reasons.)

 Options `a` or `b` seem preferable. Removing the feature from 7.0 is safe.
 `b` will require more development late in the 7.0 cycle to address this
 issue.

 I'd welcome other folks ideas and opinions here.

 -----

 [https://github.com/WordPress/ai/pull/482#discussion_r3182513240 This was
 discovered here] with help from @dkotter and @gziolo.

 FYI @westonruter.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 10:06:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 10:06:05 -0000
Subject: [wp-trac] [WordPress Trac] #61500: Script Modules: Allow
 scripts to depend on modules
In-Reply-To: <054.e8b09b0f13f70f37b69bc17945d82c17@wordpress.org>
References: <054.e8b09b0f13f70f37b69bc17945d82c17@wordpress.org>
Message-ID: <069.1b2f878595e4388b1b617d96b413cfeb@wordpress.org>

#61500: Script Modules: Allow scripts to depend on modules
-------------------------------------+-------------------------------------
 Reporter:  jonsurrell               |       Owner:  westonruter
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  7.0
Component:  Script Loader            |     Version:  6.5
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-patch has-unit-      |     Focuses:  javascript,
  tests commit needs-dev-note        |  performance
-------------------------------------+-------------------------------------

Comment (by jonsurrell):

 #65165 documents an issue with script to module dependencies.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61500#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 12:07:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 12:07:54 -0000
Subject: [wp-trac] [WordPress Trac] #12799: Allow gallery shortcode to
 accept a maximum number of items
In-Reply-To: <052.316e30701f6d21d4d29fe2b0bc2c314a@wordpress.org>
References: <052.316e30701f6d21d4d29fe2b0bc2c314a@wordpress.org>
Message-ID: <067.6f8f81dfee7bb94ede363cb14b99671a@wordpress.org>

#12799: Allow gallery shortcode to accept a maximum number of items
-------------------------------------------------+-------------------------
 Reporter:  dtorbert                             |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Gallery                              |     Version:  2.9
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch changes-requested close    |     Focuses:
  good-first-bug has-unit-tests                  |
-------------------------------------------------+-------------------------

Comment (by micahele):

 I opened a refreshed PR for this ticket:
 https://github.com/WordPress/wordpress-develop/pull/11710

 The PR adds a `limit` attribute to the gallery shortcode, allowing
 galleries to cap the maximum number of images displayed, e.g. `[gallery
 limit="2"]`.

 A few implementation notes:
 - Values less than `1` are treated as unlimited, matching the default
 behavior.
 - The default value is `-1`, so existing galleries are unaffected.
 - For normal galleries and `exclude`, the limit is passed into the
 attachment query.
 - For `include` / `ids`, the limit is applied after fetching because
 `get_posts()` ignores `numberposts` when `include` is used.

 The PR also includes PHPUnit coverage for default/no limit behavior,
 `ids`, `include`, `exclude`, and `orderby="rand"` cases.

 Tests run:
 - `php -l src/wp-includes/media.php`
 - `php -l tests/phpunit/tests/media.php`
 - `vendor/bin/phpunit tests/phpunit/tests/media.php
 --filter=test_gallery_shortcode`
 - `git diff --check -- src/wp-includes/media.php
 tests/phpunit/tests/media.php`

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/12799#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 13:33:26 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 13:33:26 -0000
Subject: [wp-trac] [WordPress Trac] #65161: Give an error message when a
 non-image is uploaded for site icon
In-Reply-To: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
References: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
Message-ID: <068.0969c84b16ee8e5ebc9a414ab8c9100a@wordpress.org>

#65161: Give an error message when a non-image is uploaded for site icon
--------------------------+------------------------------
 Reporter:  Presskopp     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by intenzi):

 I was able to identify that this issue extends to "Customizer -> Site
 Identity -> Select Logo selection" and "Customizer -> Header Media -> Add
 Header Image" selection as well apart from Select Site Icon in General
 Settings, Customizer.

 I am working on a fix for the same.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65161#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 13:37:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 13:37:15 -0000
Subject: [wp-trac] [WordPress Trac] #65166: Editor: Hide Classic Block from
 the inserter
Message-ID: <049.e73799323dcde0c21174fe1f992e1b69@wordpress.org>

#65166: Editor: Hide Classic Block from the inserter
-------------------------+---------------------------------------
 Reporter:  tyxla        |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  7.1
Component:  Editor       |    Version:  trunk
 Severity:  normal       |   Keywords:  has-patch gutenberg-merge
  Focuses:               |
-------------------------+---------------------------------------
 This ticket tracks the backport of PHP files for the following Gutenberg
 update:

 https://github.com/WordPress/gutenberg/pull/77911

 We're hiding the Classic block in the block editor inserter by default.

 We're also introducing a new `wp_classic_block_supports_inserter` filter
 that allows overriding that behavior globally or per post.

 See https://github.com/WordPress/gutenberg/pull/77911 for the full
 context.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65166>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 16:18:26 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 16:18:26 -0000
Subject: [wp-trac] [WordPress Trac] #65167: WP_Hook: Self-removing callback
 causes the next priority to be skipped
Message-ID: <052.b7f8d166b58e6801290eb26c84abd56c@wordpress.org>

#65167: WP_Hook: Self-removing callback causes the next priority to be skipped
--------------------------+-----------------------------
 Reporter:  obenland      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Plugins       |    Version:  4.7
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 When a callback running inside `apply_filters()` is the only one at its
 priority and it removes itself (or another callback empties that bucket),
 `WP_Hook` silently skips the callbacks at the next remaining priority, but
 only when at least one earlier-priority callback has already run.

 ==== Conditions to reproduce

 - A filter has callbacks at three priorities, e.g. 5, 10, 20.
 - The callback at priority 10 is the only one at that priority and calls
 `remove_filter()` on itself.
 - During `apply_filters()`, the callback at priority 20 is silently
 skipped.

 If priority 5 is removed from the example, all callbacks fire correctly.
 The bug only manifests when at least one earlier-priority callback has
 already run.

 ==== Root cause

 The bug predates `WP_Hook`. The pre-WP_Hook array-based `apply_filters()`
 had the same misbehavior: when a callback unset the priority bucket the
 internal array pointer was on, PHP silently auto-advanced the pointer to
 the next valid key, and the trailing `next()` then overshot it. `WP_Hook`
 (introduced in [38571] / 4.7.0) replaced PHP's implicit auto-advance with
 an explicit forward-walk in `resort_active_iterations()`, but preserved
 the same overshoot. The add-side of `resort_active_iterations()` already
 has symmetric handling for callbacks added at the current priority during
 iteration; the remove side is missing the equivalent fix.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65167>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 16:20:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 16:20:11 -0000
Subject: [wp-trac] [WordPress Trac] #65167: WP_Hook: Self-removing
 callback causes the next priority to be skipped
In-Reply-To: <052.b7f8d166b58e6801290eb26c84abd56c@wordpress.org>
References: <052.b7f8d166b58e6801290eb26c84abd56c@wordpress.org>
Message-ID: <067.f04ad09dbc26af493a60e32863c6e276@wordpress.org>

#65167: WP_Hook: Self-removing callback causes the next priority to be skipped
--------------------------+------------------------------
 Reporter:  obenland      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by obenland):

 * version:  4.7 =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65167#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 16:23:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 16:23:07 -0000
Subject: [wp-trac] [WordPress Trac] #64696: Real time collboration
 effectively disables persistent post caches while anyone edits a post
In-Reply-To: <057.05b7879d9d7300bfeccbd48dcfe7237b@wordpress.org>
References: <057.05b7879d9d7300bfeccbd48dcfe7237b@wordpress.org>
Message-ID: <072.9a17603d994b4f24b74516ec1a86a61f@wordpress.org>

#64696: Real time collboration effectively disables persistent post caches while
anyone edits a post
--------------------------------------+--------------------------
 Reporter:  peterwilsoncc             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.0
Component:  Posts, Post Types         |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by blackstar1991):

 Sorry for my naive question. - "Will this problem be reproduced with
 taxonomy elements? Has anyone done any testing?"

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64696#comment:163>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 17:01:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 17:01:01 -0000
Subject: [wp-trac] [WordPress Trac] #65167: WP_Hook: Self-removing
 callback causes the next priority to be skipped
In-Reply-To: <052.b7f8d166b58e6801290eb26c84abd56c@wordpress.org>
References: <052.b7f8d166b58e6801290eb26c84abd56c@wordpress.org>
Message-ID: <067.2fcd83e115ce059d68d5ec645c382ccf@wordpress.org>

#65167: WP_Hook: Self-removing callback causes the next priority to be skipped
--------------------------------------+------------------------------
 Reporter:  obenland                  |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Plugins                   |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------------

Comment (by siliconforks):

 Is this the same as #64653?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65167#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 17:12:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 17:12:39 -0000
Subject: [wp-trac] [WordPress Trac] #65167: WP_Hook: Self-removing
 callback causes the next priority to be skipped
In-Reply-To: <052.b7f8d166b58e6801290eb26c84abd56c@wordpress.org>
References: <052.b7f8d166b58e6801290eb26c84abd56c@wordpress.org>
Message-ID: <067.33a6243bbca46cac5d3224e9c0e164e4@wordpress.org>

#65167: WP_Hook: Self-removing callback causes the next priority to be skipped
--------------------------------------+------------------------
 Reporter:  obenland                  |       Owner:  (none)
     Type:  defect (bug)              |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Plugins                   |     Version:
 Severity:  normal                    |  Resolution:  duplicate
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------
Changes (by obenland):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 Duplicate of #64653.

 It is! I have no idea how I missed that, it should have come up in my
 searches. Thanks for the flag.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65167#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 17:18:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 17:18:59 -0000
Subject: [wp-trac] [WordPress Trac] #65168: AI Client: Unable to reliably
 select model for providers (model preference ignored / inconsistent API)
Message-ID: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>

#65168: AI Client: Unable to reliably select model for providers (model preference
ignored / inconsistent API)
--------------------------+-----------------------------
 Reporter:  jabir20       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  AI            |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Environment:
 - WordPress: 7.0-beta
 - AI Client: Core AI component
 - Provider: AI Provider for Google (Gemini)
 - Setup: Docker (local)

 Issue:

 When using the AI Client API, there is no consistent or working way to
 explicitly select a model.

 Attempt 1:
 Using ->model() results in a fatal-style error:

 "Method model does not exist on
 WordPress\AiClient\Builders\PromptBuilder."

 Attempt 2:
 Using ->using_model_preference('gemini-2.5-flash') does not reliably
 override the provider's default model.
 The provider still attempts to use "gemini-2.5-pro", resulting in quota
 errors (429).

 Example code:

 $result = wp_ai_client_prompt('Say hello')
     ->using_model_preference('gemini-2.5-flash')
     ->generate_text();

 Result:
 WP_Error with Gemini API 429 quota exceeded on model gemini-2.5-pro

 Expected behavior:

 - Developers should be able to explicitly set the model per request
 - The selected model should be respected by the provider
 - The API should provide a consistent method (e.g. ->model()) or
 documented alternative

 Actual behavior:

 - No stable API for model selection
 - Provider may ignore model preference
 - Leads to unexpected failures depending on provider defaults

 Notes:

 - The same API key works correctly when calling Gemini directly outside
 WordPress
 - This makes it difficult to build plugins that depend on predictable
 model usage
 - Also impacts multi-plugin environments where different plugins may
 require different models/providers

 Suggested improvement:

 - Provide a stable and documented method for model selection in AI Client
 - Ensure providers must respect explicit model selection
 - Optionally support per-plugin or per-request provider configuration

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65168>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 17:19:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 17:19:17 -0000
Subject: [wp-trac] [WordPress Trac] #62450: TinyMCE editor doesn't load
 properly when initializing on Visual Tab (Firefox) [again]
In-Reply-To: <053.adb147ac24c665ebddad0288fe483599@wordpress.org>
References: <053.adb147ac24c665ebddad0288fe483599@wordpress.org>
Message-ID: <068.850ae08463834ad38fa3a2f1038a4706@wordpress.org>

#62450: TinyMCE editor doesn't load properly when initializing on Visual Tab
(Firefox) [again]
-------------------------------------+-------------------------------------
 Reporter:  patkemper                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  TinyMCE                  |     Version:  6.7
 Severity:  major                    |  Resolution:
 Keywords:  reporter-feedback        |     Focuses:  javascript,
  needs-test-info needs-screenshots  |  administration
-------------------------------------+-------------------------------------

Comment (by vage91):

 I have the same bug, but with ACF installed.

 fix based on @trepidationcouk code that works also when switching between
 Visual and Code mode:


 {{{
 <?php
 add_action('acf/input/admin_footer', function() {
     ?>
     <script type="text/javascript">
     (function($){

         if (typeof acf === 'undefined') return;

         function initFieldTinyMCE(editorId, textareaVal) {
             if (typeof tinymce === 'undefined') return;

             var ed = tinymce.get(editorId);
             if (ed) {
                 ed.setContent(textareaVal);
                 return;
             }

             if (window.tinyMCEPreInit && tinyMCEPreInit.mceInit &&
 tinyMCEPreInit.mceInit[editorId]) {
                 tinymce.init(tinyMCEPreInit.mceInit[editorId]);

                 setTimeout(function() {
                     var newEd = tinymce.get(editorId);
                     if (newEd) newEd.setContent(textareaVal);
                 }, 100);
             }
         }

         $(document).on('click', '.wp-switch-editor.switch-tmce',
 function(e){
             const $wrap = $(this).closest('.wp-editor-wrap');
             const $acfField = $wrap.closest('.acf-field');

             if (!$wrap.length || !$acfField.length) return;

             const textarea = $wrap.find('textarea.wp-editor-area');
             const editorId = textarea.attr('id');

             e.preventDefault();
             e.stopImmediatePropagation();

             $wrap.removeClass('html-active').addClass('tmce-active');

             let val = textarea.val();
             if (typeof switchEditors !== 'undefined') {
                 val = switchEditors.wpautop(val);
             }

             setTimeout(function(){
                 initFieldTinyMCE(editorId, val);
             }, 60);
         });

         $(document).on('click', '.wp-switch-editor.switch-html',
 function(e){
             const $wrap = $(this).closest('.wp-editor-wrap');
             const $acfField = $wrap.closest('.acf-field');

             if (!$wrap.length || !$acfField.length) return;

             const textarea = $wrap.find('textarea.wp-editor-area');
             const editorId = textarea.attr('id');

             e.preventDefault();
             e.stopImmediatePropagation();

             $wrap.removeClass('tmce-active').addClass('html-active');

             const ed = tinymce.get(editorId);
             if (ed) {
                 ed.save();

                 if (typeof switchEditors !== 'undefined') {
                     let val = textarea.val();
                     val = switchEditors.pre_wpautop(val);
                     textarea.val(val);
                 }
             }
         });

     })(jQuery);
     </script>
     <?php
 });
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62450#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 17:42:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 17:42:04 -0000
Subject: [wp-trac] [WordPress Trac] #65169: support attachment pages is
 disabled by default since 6.4,
 so why then offer image be viewed in attachment pages?
Message-ID: <057.7df136539a2d43e5cd9542bd9d0d8404@wordpress.org>

#65169: support attachment pages is disabled by default since 6.4, so why then
offer image be viewed in attachment pages?
---------------------------+-----------------------------
 Reporter:  ignatiusjeroe  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  General        |    Version:  trunk
 Severity:  normal         |   Keywords:
  Focuses:  template       |
---------------------------+-----------------------------
 I've been playing around in the block editor.
 in the image/gallery block toolbar a hyperlink can be added (see link
 icon)to the image/gallery. Option 'link to attachment page' doesnt work as
 expected. It just opens the media file directly instead of using the
 attachment template. This is caused by the settings option
 '''wp_attachment_pages_enabled''' that has been set to 0 since WP 6.4.
 This causes function redirect_canonical(...) to redirect to the attachment
 source instead of returning the attachment template.

 My question is, why is the usage of attachment pages disabled by default
 when in different pages the option to use attachment pages is still
 offered? There is also no notice given (in the image/gallery toolbar) that
 the option might not work due to the disabling of
 ''wp_attachment_pages_enabled''.

 Another place in the backend were this is an issue is the media edit page.
 The media permalink clearly points to the attachment page. But when
 clicked the media file is directly opened.

 My suggestion is:
 - either turn back on the support of the usage of attachment pages
 - add an option to the Settings page with which the admin can
 enable/disable support for use of attachment pages
 - disable the option 'link to attachment page' in the image/gallery block
 toolbar

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65169>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 18:38:40 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 18:38:40 -0000
Subject: [wp-trac] [WordPress Trac] #20859: Theme Installer: Preview
 should be scrollable on iPad and Kindle Fire
In-Reply-To: <055.d6cb8397455a4c42e0d59759c958531a@wordpress.org>
References: <055.d6cb8397455a4c42e0d59759c958531a@wordpress.org>
Message-ID: <070.e313ddc90f61ffcd2fce1fd4ba9c57bb@wordpress.org>

#20859: Theme Installer: Preview should be scrollable on iPad and Kindle Fire
---------------------------------------+-----------------------------
 Reporter:  koopersmith                |       Owner:  (none)
     Type:  defect (bug)               |      Status:  new
 Priority:  normal                     |   Milestone:
Component:  Themes                     |     Version:  3.4
 Severity:  normal                     |  Resolution:
 Keywords:  needs-patch needs-testing  |     Focuses:  administration
---------------------------------------+-----------------------------

Comment (by sainathpoojary):

 Just tested this on iPad with the latest trunk (7.1-alpha) and everything
 works great now! The theme preview scrolls smoothly and I can see all the
 content without any issues. Looks like this got fixed somewhere along the
 way probably when -webkit-overflow-scrolling: touch was added to the theme
 overlay CSS.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/20859#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 19:13:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 19:13:48 -0000
Subject: [wp-trac] [WordPress Trac] #65161: Give an error message when a
 non-image is uploaded for site icon
In-Reply-To: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
References: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
Message-ID: <068.46716b945aef09b308769f4c0901ebdb@wordpress.org>

#65161: Give an error message when a non-image is uploaded for site icon
--------------------------+------------------------------
 Reporter:  Presskopp     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------

Comment (by Presskopp):

 Nice approach, but I assume you should avoid using `window.alert()`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65161#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 21:02:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 21:02:15 -0000
Subject: [wp-trac] [WordPress Trac] #65170: Add unit tests for
 iis7_delete_rewrite_rule()
Message-ID: <051.40c3fa19202e62a1d179c021246da251@wordpress.org>

#65170: Add unit tests for iis7_delete_rewrite_rule()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the IIS7 delete rewrite rule
 function in wp-admin/includes/misc.php to ensure correct XML manipulation
 in web.config files.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65170>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 21:12:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 21:12:28 -0000
Subject: [wp-trac] [WordPress Trac] #65171: wp_check_post_lock_window filter
 values below 120s break post lock detection in backgrounded tabs
Message-ID: <051.da93c0bf97890d05b794aa302384a283@wordpress.org>

#65171: wp_check_post_lock_window filter values below 120s break post lock
detection in backgrounded tabs
----------------------------+-----------------------------
 Reporter:  katag9k         |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Editor          |    Version:
 Severity:  normal          |   Keywords:  needs-patch
  Focuses:  ui, javascript  |
----------------------------+-----------------------------
 == Summary ==

 When `wp_check_post_lock_window` is filtered to a value lower than the
 maximum heartbeat interval (120s), post lock detection silently breaks for
 users editing in backgrounded tabs. A second editor opening the same post
 sees no "Currently being edited" modal, walks into the editor, and on the
 next heartbeat takes over the lock — silently overwriting any unsaved
 changes the first editor had typed.

 == Steps to reproduce ==

 Add the following to a theme or plugin:

 {{{
   add_filter( 'wp_check_post_lock_window', function() { return 30; } );
 }}}

 1. User A opens `/wp-admin/post.php?post=N&action=edit`. `_edit_lock` is
 set with the current timestamp.
 2. User A switches to a different tab/window so the editor tab is
 backgrounded. `heartbeat.js` overrides `interval` to 120000ms.
 3. After 30 seconds, the lock is considered expired by
 `wp_check_post_lock()` (uses the filtered window).
 4. User A's lock is not refreshed until 120s elapse (next backgrounded
 heartbeat).
 5. Between t=30s and t=120s, user B opens the same post.
 `wp_check_post_lock()` returns false. No takeover modal appears. B walks
 into the
   editor.
 6. B's first heartbeat claims the lock. A's next heartbeat receives
 `lock_error` and A is shown the takeover modal — losing any unsaved
 changes.

 I reproduced this end-to-end by logging both heartbeat traffic and
 `wp_check_post_lock_window` calls. The 120s gap between A's heartbeats is
 exactly what `heartbeat.js:512` produces; the lack of modal for B is
 exactly what `post.php` produces when the lock has aged past 30s.

 == Code paths ==

 The defect is two pieces of core that have no shared awareness:

 `src/wp-admin/includes/post.php`, `wp_check_post_lock()`:

 {{{
   $time_window = apply_filters( 'wp_check_post_lock_window', 150 );

   if ( $time && $time > time() - $time_window && get_current_user_id() !==
 $user ) {
       return $user;
   }
 }}}

 The filter has no documented minimum value.

 `src/js/_enqueues/wp/heartbeat.js`, `scheduleNextTick()`:

 {{{
   if ( ! settings.hasFocus ) {
       interval = 120000; // 120 seconds. Post locks expire after 150
 seconds.
   }
 }}}

 The 120000 constant is hardcoded; the comment confirms the design
 implicitly assumes the lock window is always 150s. There is no mechanism
 for a customised lock window to reach the JS layer.

 `src/wp-includes/general-template.php`, `wp_heartbeat_settings()`, does
 not expose the lock window — it only sets `ajaxurl` and `nonce`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65171>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 21:14:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 21:14:29 -0000
Subject: [wp-trac] [WordPress Trac] #65172: Tests: Add unit tests for
 iis7_add_rewrite_rule()
Message-ID: <051.1b5b0cfbe3a564da35c1617993e72761@wordpress.org>

#65172: Tests: Add unit tests for iis7_add_rewrite_rule()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the iis7_add_rewrite_rule()
 function in wp-admin/includes/misc.php to ensure correct addition of
 WordPress rewrite rules to IIS7 web.config files, including handling of
 missing configuration elements.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65172>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 21:29:40 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 21:29:40 -0000
Subject: [wp-trac] [WordPress Trac] #65173: Add unit tests for
 saveDomDocument()
Message-ID: <051.e349c787e2022e6a81302b61e3896975@wordpress.org>

#65173: Add unit tests for saveDomDocument()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the saveDomDocument() function in wp-
 admin/includes/misc.php. These tests ensure that the function correctly
 saves a DOMDocument to a file and properly converts line endings to CRLF.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65173>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 21:35:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 21:35:38 -0000
Subject: [wp-trac] [WordPress Trac] #65174: Add unit tests for
 update_recently_edited()
Message-ID: <051.77812eccd422fa18a7117a567cbfa172@wordpress.org>

#65174: Add unit tests for update_recently_edited()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the update_recently_edited() function in
 wp-admin/includes/misc.php. These tests ensure that the function correctly
 manages the list of recently edited files in the recently_edited option,
 maintaining order and a maximum of 5 items.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65174>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 21:44:47 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 21:44:47 -0000
Subject: [wp-trac] [WordPress Trac] #65175: Tests: Add unit tests for
 wp_make_theme_file_tree()
Message-ID: <051.9f2e73e6f851710a20c5296c36bee115@wordpress.org>

#65175: Tests: Add unit tests for wp_make_theme_file_tree()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the wp_make_theme_file_tree() function in
 wp-admin/includes/misc.php. This function is responsible for converting a
 flat list of theme files into a tree structure for use in the theme
 editor.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65175>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 21:54:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 21:54:02 -0000
Subject: [wp-trac] [WordPress Trac] #65035: Abilities: Strip internal
 schema keywords from abilities REST responses
In-Reply-To: <060.11365645bf003f62fe2c244d23d3172e@wordpress.org>
References: <060.11365645bf003f62fe2c244d23d3172e@wordpress.org>
Message-ID: <075.933699e1bd24acdc61e2051a9d3f5f9e@wordpress.org>

#65035: Abilities: Strip internal schema keywords from abilities REST responses
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Abilities API                        |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests fixed-      |     Focuses:
  major dev-feedback                             |
-------------------------------------------------+-------------------------
Changes (by JeffPaul):

 * keywords:  has-patch has-unit-tests dev-reviewed => has-patch has-unit-
     tests fixed-major dev-feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for merge to the 7.0 branch pending committer sign off.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65035#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 22:07:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 22:07:32 -0000
Subject: [wp-trac] [WordPress Trac] #65176: Tests: Add unit tests for
 wp_make_plugin_file_tree(
Message-ID: <051.b65d4a2d994257ad60d94d5d35d91484@wordpress.org>

#65176: Tests: Add unit tests for wp_make_plugin_file_tree(
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the wp_make_plugin_file_tree() function in
 wp-admin/includes/misc.php. This function is responsible for converting a
 flat list of plugin files into a tree structure for use in the plugin
 editor.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65176>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May  5 23:17:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 05 May 2026 23:17:18 -0000
Subject: [wp-trac] [WordPress Trac] #53010: Tests: introduce namespacing
 for the test classes
In-Reply-To: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
References: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
Message-ID: <062.6ad6b13a08d8580c1575230d3ab8d417@wordpress.org>

#53010: Tests: introduce namespacing for the test classes
--------------------------------------+------------------------------------
 Reporter:  jrf                       |       Owner:  SergeyBiryukov
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  docs, coding-
                                      |  standards
--------------------------------------+------------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"62297" 62297]:
 {{{
 #!CommitTicketReference repository="" revision="62297"
 Tests: Rename the `wpGetPluginActionButton.php` test file to match the new
 pattern.

 This aims to make the test suite directory and file structure more
 intuitive for new contributors to work with, as well as follow the PHPUnit
 recommended test class name pattern with having `Test` as the end of the
 class name.

 Follow-up to [58396], [61407].

 See #53010.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53010#comment:60>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 00:30:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 00:30:06 -0000
Subject: [wp-trac] [WordPress Trac] #64622: Real-time collaboration: Add
 new REST endpoints, setting, and registered post meta
In-Reply-To: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
References: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
Message-ID: <066.81aa11e37f8c0b23e8bb8617667cfc3c@wordpress.org>

#64622: Real-time collaboration: Add new REST endpoints, setting, and registered
post meta
-------------------------------------------------+-------------------------
 Reporter:  czarate                              |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests add-to-     |     Focuses:
  field-guide needs-dev-note                     |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 In [changeset:"62298" 62298]:
 {{{
 #!CommitTicketReference repository="" revision="62298"
 REST API/RTC: Fix divergence when two offline users reconnect.

 Prevent Real-Time Collaboration sessions from becoming out of sync when an
 offline editor returns to an online state. The change ensures that the
 updates are merged rather than discarded when each client is at a
 different cursor after reconnecting or experiencing slow network
 conditions.

 Props alecgeatches, peterwilsoncc, maxschmeling, joefusco.
 See #64622.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64622#comment:80>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 00:31:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 00:31:25 -0000
Subject: [wp-trac] [WordPress Trac] #64622: Real-time collaboration: Add
 new REST endpoints, setting, and registered post meta
In-Reply-To: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
References: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
Message-ID: <066.55b463841720680018932a7fd48bbc4b@wordpress.org>

#64622: Real-time collaboration: Add new REST endpoints, setting, and registered
post meta
-------------------------------------------------+-------------------------
 Reporter:  czarate                              |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests add-to-     |     Focuses:
  field-guide needs-dev-note dev-feedback        |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests add-to-field-guide needs-dev-note =>
     has-patch has-unit-tests add-to-field-guide needs-dev-note dev-
     feedback


Comment:

 Requesting review from another committer for merging r62298 to the 7.0
 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64622#comment:81>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 00:47:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 00:47:12 -0000
Subject: [wp-trac] [WordPress Trac] #64771: Existing block level custom
 CSS in a post breaks when the post is edited by user without
 unfiltered_html
In-Reply-To: <056.6cde4cb4d3674a3ab453a19d1888b21e@wordpress.org>
References: <056.6cde4cb4d3674a3ab453a19d1888b21e@wordpress.org>
Message-ID: <071.0dfdacaeca84ce7a26794f2e4343a2e2@wordpress.org>

#64771: Existing block level custom CSS in a post breaks when the post is edited by
user without unfiltered_html
-------------------------------------------------+-------------------------
 Reporter:  glendaviesnz                         |       Owner:  ramonopoly
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  high                                 |   Milestone:  7.0
Component:  Editor                               |     Version:  trunk
 Severity:  critical                             |  Resolution:
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:
  feedback                                       |
-------------------------------------------------+-------------------------

Comment (by ramonopoly):

 > I can get a quick changeset up to update the comment for trunk if that
 helps.


 Patch for that here: https://github.com/WordPress/wordpress-
 develop/pull/11725


 @audrasjb [https://make.wordpress.org/core/handbook/best-practices
 /backporting-commits/#backport-process The docs] say that a different
 committer should backport [https://core.trac.wordpress.org/changeset/62257
 the original patch] to the release branch.

 Is that still the case? If so can someone help out? Thanks!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64771#comment:68>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 01:23:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 01:23:16 -0000
Subject: [wp-trac] [WordPress Trac] #65157: Blocks: WordPress prevent
 videos from being set as backgrounds
In-Reply-To: <049.b5992ec627f0854820bdf57a9285b790@wordpress.org>
References: <049.b5992ec627f0854820bdf57a9285b790@wordpress.org>
Message-ID: <064.cc07ee535c7d7c00e6cd1de19966362e@wordpress.org>

#65157: Blocks: WordPress prevent videos from being set as backgrounds
-------------------------------+-------------------------------------------
 Reporter:  wurds              |       Owner:  (none)
     Type:  feature request    |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui, administration, template
  close                        |
-------------------------------+-------------------------------------------
Changes (by wildworks):

 * keywords:  reporter-feedback => reporter-feedback close


Comment:

 In WordPress 7.0, the cover block allows several providers to be embedded
 as background videos. See
 https://github.com/WordPress/gutenberg/pull/73023 for more details.

 I believe this ticket can be closed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65157#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 01:41:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 01:41:46 -0000
Subject: [wp-trac] [WordPress Trac] #65177: Adminbar: Unnatural focus
 outline in frontend
Message-ID: <053.761bf75e2bb92c14494464a5c083ae76@wordpress.org>

#65177: Adminbar: Unnatural focus outline in frontend
----------------------------+-----------------------------
 Reporter:  wildworks       |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 The admin bar menu items are expected to change color when focused.
 However, on the front end, the browser's default outline is also displayed
 along with the color change.

 To ensure consistency between the frontend and the dashboard, I believe
 this outline should be removed. This issue does not occur on the dashboard
 because it has styles that reset the outline.

 https://github.com/WordPress/wordpress-
 develop/blob/3b11171716f83efa10787a24ef8a9dae53463a61/src/wp-
 admin/css/common.css#L270

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65177>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 01:42:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 01:42:28 -0000
Subject: [wp-trac] [WordPress Trac] #65177: Adminbar: Unnatural focus
 outline in frontend
In-Reply-To: <053.761bf75e2bb92c14494464a5c083ae76@wordpress.org>
References: <053.761bf75e2bb92c14494464a5c083ae76@wordpress.org>
Message-ID: <068.7645bc3f5a360514b154c855bef12ea2@wordpress.org>

#65177: Adminbar: Unnatural focus outline in frontend
----------------------------+------------------------------
 Reporter:  wildworks       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------
Changes (by wildworks):

 * Attachment "admin-bar-focus-outline.png" added.

 Differences in focus styles between front-end and back-end

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65177>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 03:09:47 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 03:09:47 -0000
Subject: [wp-trac] [WordPress Trac] #65177: Adminbar: Unnatural focus
 outline in frontend
In-Reply-To: <053.761bf75e2bb92c14494464a5c083ae76@wordpress.org>
References: <053.761bf75e2bb92c14494464a5c083ae76@wordpress.org>
Message-ID: <068.e3c57a07af263bfea032559fd6667966@wordpress.org>

#65177: Adminbar: Unnatural focus outline in frontend
----------------------------+------------------------------
 Reporter:  wildworks       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------

Comment (by joedolson):

 Are you sure you're not getting a style leak from the theme? It's common
 for theme styles to apply to the admin bar.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65177#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 04:10:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 04:10:00 -0000
Subject: [wp-trac] [WordPress Trac] #64771: Existing block level custom
 CSS in a post breaks when the post is edited by user without
 unfiltered_html
In-Reply-To: <056.6cde4cb4d3674a3ab453a19d1888b21e@wordpress.org>
References: <056.6cde4cb4d3674a3ab453a19d1888b21e@wordpress.org>
Message-ID: <071.470b35ee5260548ebed5420fcb37879d@wordpress.org>

#64771: Existing block level custom CSS in a post breaks when the post is edited by
user without unfiltered_html
-------------------------------------------------+-------------------------
 Reporter:  glendaviesnz                         |       Owner:  ramonopoly
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  high                                 |   Milestone:  7.0
Component:  Editor                               |     Version:  trunk
 Severity:  critical                             |  Resolution:
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests dev-feedback => has-patch has-unit-
     tests dev-reviewed


Comment:

 Approving r62257 and r62299 for merging to the 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64771#comment:71>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 04:29:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 04:29:18 -0000
Subject: [wp-trac] [WordPress Trac] #64771: Existing block level custom
 CSS in a post breaks when the post is edited by user without
 unfiltered_html
In-Reply-To: <056.6cde4cb4d3674a3ab453a19d1888b21e@wordpress.org>
References: <056.6cde4cb4d3674a3ab453a19d1888b21e@wordpress.org>
Message-ID: <071.0c16b829a37172c974ccd33e8905507a@wordpress.org>

#64771: Existing block level custom CSS in a post breaks when the post is edited by
user without unfiltered_html
-------------------------------------------------+-------------------------
 Reporter:  glendaviesnz                         |       Owner:  ramonopoly
     Type:  defect (bug)                         |      Status:  closed
 Priority:  high                                 |   Milestone:  7.0
Component:  Editor                               |     Version:  trunk
 Severity:  critical                             |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by ramonopoly):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62300" 62300]:
 {{{
 #!CommitTicketReference repository="" revision="62300"
 Block Supports: strip custom CSS from blocks for users without edit_css
 capability

 Adds capability-gated CSS stripping so that when a user without `edit_css`
 saves a post, any `style.css` block attributes are removed from block
 comments using `WP_Block_Parser::next_token()`.

 Reviewed by audrasjb, peterwilsoncc.
 Merges [62257], [62299] to the 7.0 branch.

 Props aaronrobertshaw, audrasjb, dmsnell, glendaviesnz, jonsurrell,
 ozgursar, ramonopoly, shailu25, westonruter.

 Follow-up to [64544].

 Fixes #64771.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64771#comment:72>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 04:30:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 04:30:46 -0000
Subject: [wp-trac] [WordPress Trac] #64771: Existing block level custom
 CSS in a post breaks when the post is edited by user without
 unfiltered_html
In-Reply-To: <056.6cde4cb4d3674a3ab453a19d1888b21e@wordpress.org>
References: <056.6cde4cb4d3674a3ab453a19d1888b21e@wordpress.org>
Message-ID: <071.d771b2610bd8ba91e6ce31f447ee6ea0@wordpress.org>

#64771: Existing block level custom CSS in a post breaks when the post is edited by
user without unfiltered_html
-------------------------------------------------+-------------------------
 Reporter:  glendaviesnz                         |       Owner:  ramonopoly
     Type:  defect (bug)                         |      Status:  closed
 Priority:  high                                 |   Milestone:  7.0
Component:  Editor                               |     Version:  trunk
 Severity:  critical                             |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------

Comment (by ramonopoly):

 Thanks to everyone who helped on this one!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64771#comment:73>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 04:58:35 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 04:58:35 -0000
Subject: [wp-trac] [WordPress Trac] #65177: Adminbar: Unnatural focus
 outline in frontend
In-Reply-To: <053.761bf75e2bb92c14494464a5c083ae76@wordpress.org>
References: <053.761bf75e2bb92c14494464a5c083ae76@wordpress.org>
Message-ID: <068.c790277cb87702791ac2a16ad205c27e@wordpress.org>

#65177: Adminbar: Unnatural focus outline in frontend
----------------------------+------------------------------
 Reporter:  wildworks       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------

Comment (by hbhalodia):

 Hi @joedolson, I can confirm the issue shared by @wildworks exists. I can
 see the styles are being applied and there is no any style leak from
 theme. The outline style attached to the frontend admin bar is coming from
 the browser default outline style.

 I have worked on it and added the style to remove the outline from here
 `src/wp-includes/css/admin-bar.css` particularly targeting the admin bar.

 Let me know the fix added is in correct file or it should be moved
 somewhere else, I would be happy to update the PR as per feedback.

 Thanks,

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65177#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:02:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:02:18 -0000
Subject: [wp-trac] [WordPress Trac] #64622: Real-time collaboration: Add
 new REST endpoints, setting, and registered post meta
In-Reply-To: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
References: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
Message-ID: <066.860a241e5f260820aba73e81f5ff7190@wordpress.org>

#64622: Real-time collaboration: Add new REST endpoints, setting, and registered
post meta
-------------------------------------------------+-------------------------
 Reporter:  czarate                              |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests add-to-     |     Focuses:
  field-guide needs-dev-note dev-feedback        |
-------------------------------------------------+-------------------------

Comment (by ramonopoly):

 The [https://core.trac.wordpress.org/changeset/62298 changeset] looks good
 to me to backport. The original patch was well tested and approved by 3
 reviewers.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64622#comment:84>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:04:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:04:27 -0000
Subject: [wp-trac] [WordPress Trac] #64622: Real-time collaboration: Add
 new REST endpoints, setting, and registered post meta
In-Reply-To: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
References: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
Message-ID: <066.d8d6f158629f35872ffb94f1ee91a3e4@wordpress.org>

#64622: Real-time collaboration: Add new REST endpoints, setting, and registered
post meta
-------------------------------------------------+-------------------------
 Reporter:  czarate                              |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests add-to-     |     Focuses:
  field-guide needs-dev-note dev-reviewed        |
-------------------------------------------------+-------------------------
Changes (by ramonopoly):

 * keywords:
     has-patch has-unit-tests add-to-field-guide needs-dev-note dev-
     feedback
     =>
     has-patch has-unit-tests add-to-field-guide needs-dev-note dev-
     reviewed


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64622#comment:85>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:06:36 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:06:36 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2364689=3A_Customizer_?=
 =?utf-8?q?=E2=80=9CPublish=E2=80=9D_button_size_appears_larger_in_7=2E0_c?=
 =?utf-8?q?ompared_to_6=2E9=2E1?=
In-Reply-To: <052.73b260729ea404b08fe598cc7f376a7e@wordpress.org>
References: <052.73b260729ea404b08fe598cc7f376a7e@wordpress.org>
Message-ID: <067.ed245e62f1de457b263bb754feb3c653@wordpress.org>

#64689: Customizer “Publish” button size appears larger in 7.0 compared to 6.9.1
-------------------------------------------------+-------------------------
 Reporter:  mohitbsf                             |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Customize                            |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  admin-reskin has-patch commit dev-   |     Focuses:  css
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62301" 62301]:
 {{{
 #!CommitTicketReference repository="" revision="62301"
 Admin Reskin: Correct Customizer “Publish” button size.

 Follow-up to [61646].

 Reviewed by peterwilsoncc.
 Merges r62295 to the 7.0 branch.

 Props mohitbsf, wildworks, joedolson, audrasjb, huzaifaalmesbah,
 SergeyBiryukov.
 Fixes #64689.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64689#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:07:57 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:07:57 -0000
Subject: [wp-trac] [WordPress Trac] #65141: Fix alignment for sortable
 metabox on post and page edit screen with classic editor
In-Reply-To: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
References: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
Message-ID: <071.1f7106128b48c27deb8a3db59c21b62b@wordpress.org>

#65141: Fix alignment for sortable metabox on post and page edit screen with
classic editor
------------------------------------+-----------------------------
 Reporter:  umesh.nevase            |       Owner:  SergeyBiryukov
     Type:  defect (bug)            |      Status:  reopened
 Priority:  normal                  |   Milestone:  7.0
Component:  Editor                  |     Version:  trunk
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch admin-reskin  |     Focuses:  ui, css
------------------------------------+-----------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch admin-reskin commit dev-reviewed => has-patch admin-
     reskin


Comment:

 Doing some keyword management to tidy up the workflow report.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65141#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:09:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:09:39 -0000
Subject: [wp-trac] [WordPress Trac] #64987: Admin Reskin: Add more
 margin below the plugin card header
In-Reply-To: <053.b1d5d7c143cf639af6b45eb03cf6d81a@wordpress.org>
References: <053.b1d5d7c143cf639af6b45eb03cf6d81a@wordpress.org>
Message-ID: <068.e8180045c1ed26582c3be295430cc0d4@wordpress.org>

#64987: Admin Reskin: Add more margin below the plugin card header
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  admin-reskin has-patch commit dev-   |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62302" 62302]:
 {{{
 #!CommitTicketReference repository="" revision="62302"
 Admin Reskin: Add more spacing below the plugin card header.

 Follow-up to [61646].

 Reviewed by audrasjb.
 Merges r62290 to the 7.0 branch.

 Props wildworks, mukesh27, shailu25, noruzzaman, darshitrajyaguru97,
 SergeyBiryukov.
 Fixes #64987.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64987#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:16:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:16:48 -0000
Subject: [wp-trac] [WordPress Trac] #65131: Administration: Spinners are
 misaligned
In-Reply-To: <053.8909cf9fe91d2de421593bc947a3a237@wordpress.org>
References: <053.8909cf9fe91d2de421593bc947a3a237@wordpress.org>
Message-ID: <068.00ebf7a4c25abd28d39e826fdca65475@wordpress.org>

#65131: Administration: Spinners are misaligned
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Administration                       |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch commit dev-   |     Focuses:  ui
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  admin-reskin has-patch commit dev-feedback => admin-reskin
     has-patch commit dev-reviewed


Comment:

 r62291 approved for merge to the 7.0 brnahc.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65131#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:18:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:18:31 -0000
Subject: [wp-trac] [WordPress Trac] #65131: Administration: Spinners are
 misaligned
In-Reply-To: <053.8909cf9fe91d2de421593bc947a3a237@wordpress.org>
References: <053.8909cf9fe91d2de421593bc947a3a237@wordpress.org>
Message-ID: <068.536c35b3afc63e28bd2c9471a71fce56@wordpress.org>

#65131: Administration: Spinners are misaligned
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Administration                       |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  admin-reskin has-patch commit dev-   |     Focuses:  ui
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62303" 62303]:
 {{{
 #!CommitTicketReference repository="" revision="62303"
 Admin Reskin: Correct alignment for spinners across the admin.

 Follow-up to [61646].

 Reviewed by peterwilsoncc.
 Merges r62291 to the 7.0 branch.

 Props wildworks, anupkankale, shailu25, gaurangsondagar, jadavsanjay,
 SergeyBiryukov.
 Fixes #65131.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65131#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:27:35 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:27:35 -0000
Subject: [wp-trac] [WordPress Trac] #64622: Real-time collaboration: Add
 new REST endpoints, setting, and registered post meta
In-Reply-To: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
References: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
Message-ID: <066.8ad033e41c9a51ebcd11612b104c283e@wordpress.org>

#64622: Real-time collaboration: Add new REST endpoints, setting, and registered
post meta
-------------------------------------------------+-------------------------
 Reporter:  czarate                              |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests add-to-     |     Focuses:
  field-guide needs-dev-note dev-reviewed        |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 In [changeset:"62304" 62304]:
 {{{
 #!CommitTicketReference repository="" revision="62304"
 REST API/RTC: Fix divergence when two offline users reconnect.

 Prevent Real-Time Collaboration sessions from becoming out of sync when an
 offline editor returns to an online state. The change ensures that the
 updates are merged rather than discarded when each client is at a
 different cursor after reconnecting or experiencing slow network
 conditions.

 Reviewed by ramonopoly.
 Merges r62298 to the 7.0 branch.

 Props alecgeatches, peterwilsoncc, maxschmeling, joefusco.
 See #64622.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64622#comment:86>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:29:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:29:17 -0000
Subject: [wp-trac] [WordPress Trac] #64622: Real-time collaboration: Add
 new REST endpoints, setting, and registered post meta
In-Reply-To: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
References: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
Message-ID: <066.22f2a94e0edac5f5e6e4edeae8e4431f@wordpress.org>

#64622: Real-time collaboration: Add new REST endpoints, setting, and registered
post meta
-------------------------------------------------+-------------------------
 Reporter:  czarate                              |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  add-to-field-guide needs-dev-note    |     Focuses:
  close                                          |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:
     has-patch has-unit-tests add-to-field-guide needs-dev-note dev-
     reviewed
     => add-to-field-guide needs-dev-note close


Comment:

 Keyword management following commit and backport above.

 This can probably be closed off and any further issues raised in follow up
 tickets.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64622#comment:87>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 05:37:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 05:37:30 -0000
Subject: [wp-trac] [WordPress Trac] #65160: Misleading error message on
 user screen actions, if no role has been selected
In-Reply-To: <053.1f519b6db1ee8564919c90337a59d520@wordpress.org>
References: <053.1f519b6db1ee8564919c90337a59d520@wordpress.org>
Message-ID: <068.9591ca3acc4ea635f8170fc414cdcfcb@wordpress.org>

#65160: Misleading error message on user screen actions, if no role has been
selected
--------------------------+------------------------------
 Reporter:  Presskopp     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Users         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  ui
--------------------------+------------------------------

Comment (by hbhalodia):

 Hi @Presskopp,

 I’m not entirely sure what the exact issue is here, as the current wording
 looks correct to me. I reviewed the following test cases, and all of them
 appear to behave as expected without showing misleading messages.

 Could you please review the cases below and clarify what specifically
 needs to be updated? Once clarified, we can also check with the wider team
 to determine whether other users feel the wording should be changed.

 1. No bulk action selected, no role change selected, no users selected —
 Click **Apply**
     - Message: `Please select a bulk action to perform.` — Does not appear
 misleading.
 2. No bulk action selected, no role change selected, no users selected —
 Click **Change**
     * Message: `Please select a bulk action to perform.` — Does not appear
 misleading.
 3. No bulk action selected, no role change selected, users selected —
 Click **Apply**
     * Message: `Please select a bulk action to perform.` — Does not appear
 misleading.
 4. No bulk action selected, no role change selected, users selected —
 Click **Change**
     * Message: `Please select a bulk action to perform.` — Does not appear
 misleading.
 5. Password Reset bulk action selected, no role change selected, no users
 selected — Click **Apply**
     * Message: `Please select at least one item to perform this action
 on.` — Does not appear misleading.
 6. Password Reset bulk action selected, no role change selected, no users
 selected — Click **Change**
     * Message: `Please select a bulk action to perform.` — Does not appear
 misleading, as no role change was selected.
 7. Password Reset bulk action selected, no role change selected, users
 selected — Click **Apply**
     * Message: `Password reset links sent to n users.` — Does not appear
 misleading.
 8. Password Reset bulk action selected, no role change selected, users
 selected — Click **Change**
     * Message: `Please select a bulk action to perform.` — Does not appear
 misleading, as no role change was selected.
 9. No bulk action selected, Subscriber role selected, no users selected —
 Click **Apply**
     * Message: `Please select a bulk action to perform.` — Does not appear
 misleading.
 10. No bulk action selected, Subscriber role selected, no users selected —
 Click **Change**
     * Message: `Please select at least one item to perform this action
 on.` — Does not appear misleading.
 11. No bulk action selected, Subscriber role selected, users selected —
 Click **Apply**
     * Message: `Please select a bulk action to perform.` — Does not appear
 misleading, as the role change option was selected but the bulk action
 button was clicked.
 12. No bulk action selected, Subscriber role selected, users selected —
 Click **Change**
     * Message: `Changed roles.` — Does not appear misleading.
 13. Password Reset bulk action selected, Subscriber role selected, no
 users selected — Click **Apply**
     * Message: `Please select at least one item to perform this action
 on.` — Does not appear misleading.
 14. Password Reset bulk action selected, Subscriber role selected, no
 users selected — Click **Change**
     * Message: `Please select at least one item to perform this action
 on.` — Does not appear misleading.
 15. Password Reset bulk action selected, Subscriber role selected, users
 selected — Click **Apply**
     * Message: `Password reset links sent to n users.` — Does not appear
 misleading.
 16. Password Reset bulk action selected, Subscriber role selected, users
 selected — Click **Change**
     * Message: `Changed roles.` — Does not appear misleading.

 I believe I have covered all possible cases, and I do not currently see
 any misleading messages. The only scenario that may be worth reconsidering
 is when users click **Change** or **Apply** without making any selection,
 as both currently display the same message:

 `Please select a bulk action to perform.`

 Perhaps when clicking **Change**, the message could instead be something
 like:

 `Please select a role to change.`

 That is the only potential improvement I can currently identify.

 Thanks,

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65160#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 06:06:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 06:06:44 -0000
Subject: [wp-trac] [WordPress Trac] #65160: Misleading error message on
 user screen actions, if no role has been selected
In-Reply-To: <053.1f519b6db1ee8564919c90337a59d520@wordpress.org>
References: <053.1f519b6db1ee8564919c90337a59d520@wordpress.org>
Message-ID: <068.519167c997b00a79deb3542363d68319@wordpress.org>

#65160: Misleading error message on user screen actions, if no role has been
selected
--------------------------+------------------------------
 Reporter:  Presskopp     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Users         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui
--------------------------+------------------------------

Comment (by hbhalodia):

 Hi @Presskopp, As per the above comment, I have added a PR which shows the
 correct message when user clicks role to change or a bulk action to
 change. You can test the PR and also check all the test cases and share
 any misleading message or improvement needed.

 Thanks,

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65160#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 07:54:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 07:54:02 -0000
Subject: [wp-trac] [WordPress Trac] #65145: Plugins: Display plugin
 slug/identifier in Installed Plugins row meta
In-Reply-To: <052.c963c996c75cb96bcb429195e4caec32@wordpress.org>
References: <052.c963c996c75cb96bcb429195e4caec32@wordpress.org>
Message-ID: <067.5db3fc5f0b0b70c336f29e8677855145@wordpress.org>

#65145: Plugins: Display plugin slug/identifier in Installed Plugins row meta
-------------------------+-----------------------------
 Reporter:  crweiner     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  administration
-------------------------+-----------------------------

Comment (by hbhalodia):

 Hi Team, I have updated the PR to add the slug column after `Name` and
 before `Description`. Also added option to hide the slug by default for
 all users when the feature lands. User can enable/disable using screen
 options as shared.

 Refer PR description for detailed screencast on the functionality -
 https://github.com/WordPress/wordpress-develop/pull/11674

 As @westonruter mentioned, to uniquely identify the plugin, we need to use
 `$plugin_file` variable. So I have used that, so we have detailed plugin
 slug info.

 Thanks,

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65145#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 09:21:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 09:21:22 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.ff9bdb44dfa187b497989207cfde4df5@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------
Changes (by wildworks):

 * keywords:  admin-reskin has-patch => admin-reskin has-patch dev-reviewed


Comment:

 This is a second committer sign-off. Approving [62294] for 7.0 backport.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 09:28:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 09:28:27 -0000
Subject: [wp-trac] [WordPress Trac] #65150: Issue with copy_dir()
 function t does not skips folders.
In-Reply-To: <051.3ea19f390e67542b3753efde0bd26330@wordpress.org>
References: <051.3ea19f390e67542b3753efde0bd26330@wordpress.org>
Message-ID: <066.f056968764400db0aa85a5dcc4496a6a@wordpress.org>

#65150: Issue with copy_dir() function  t does not skips folders.
----------------------------+------------------------------
 Reporter:  neo2k23         |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Filesystem API  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+------------------------------

Comment (by hbhalodia):

 Replying to [comment:9 neo2k23]:
 > @hbhalodia
 >
 > I am flabbergasted that this bug exists since wp 3.7.0 (october 24 2013)
 and nobody ever noticed this.By accident I stumbled across this, because
 the theme activated was using a renamed _theme_copy_dir function in its
 code to copy files and I wanted to get rid of it by calling the default wp
 code.
 >
 > I am glad it will be resolved soon in a WordPress update.


 Yes @neo2k23, That's surprise for me as well.

 Let's wait for a core committer/ wider team to validate this indeed an
 issue or it was an oversight/ known thing they kept it so long.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65150#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 10:02:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 10:02:59 -0000
Subject: [wp-trac] [WordPress Trac] #65035: Abilities: Strip internal
 schema keywords from abilities REST responses
In-Reply-To: <060.11365645bf003f62fe2c244d23d3172e@wordpress.org>
References: <060.11365645bf003f62fe2c244d23d3172e@wordpress.org>
Message-ID: <075.569b83137ea4c38a20611523166a3f45@wordpress.org>

#65035: Abilities: Strip internal schema keywords from abilities REST responses
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Abilities API                        |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests fixed-      |     Focuses:
  major dev-reviewed                             |
-------------------------------------------------+-------------------------
Changes (by gziolo):

 * keywords:  has-patch has-unit-tests fixed-major dev-feedback => has-patch
     has-unit-tests fixed-major dev-reviewed


Comment:

 Let's make sure this is included in WP 7.0. Changes look good!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65035#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 12:41:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 12:41:10 -0000
Subject: [wp-trac] [WordPress Trac] #65168: AI Client: Unable to
 reliably select model for providers (model preference ignored /
 inconsistent API)
In-Reply-To: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
References: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
Message-ID: <066.e201c3175820454442211e204a1f7cc4@wordpress.org>

#65168: AI Client: Unable to reliably select model for providers (model preference
ignored / inconsistent API)
--------------------------+------------------------------
 Reporter:  jabir20       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  AI            |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by westonruter):

 > 7.0-beta

 Have you tried with 7.0-RC2?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65168#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 12:48:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 12:48:31 -0000
Subject: [wp-trac] [WordPress Trac] #65161: Give an error message when a
 non-image is uploaded for site icon
In-Reply-To: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
References: <053.5e3d8db5c1e2d386a67423cd39cf7f40@wordpress.org>
Message-ID: <068.2b2dfdb8d577041f341297f5180e2f0d@wordpress.org>

#65161: Give an error message when a non-image is uploaded for site icon
--------------------------+------------------------------
 Reporter:  Presskopp     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------

Comment (by intenzi):

 Thankyou, I went with `window.alert()` as the media selection modal
 overlays on top and thus existing notification systems like the
 `wp.Customize.notification` one would get hidden if utilised. This appears
 to be the correct way to display the error message to the user. Always
 open to any suggestions if you know of a way it can be improved!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65161#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 14:28:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 14:28:14 -0000
Subject: [wp-trac] [WordPress Trac] #64083: Trim the GitHub Actions
 workflows for older branches (and possibly `trunk`)
In-Reply-To: <055.d1f6227d749409a50dba173f85029277@wordpress.org>
References: <055.d1f6227d749409a50dba173f85029277@wordpress.org>
Message-ID: <070.04b19a01bffbc4cf965a276ec64c528d@wordpress.org>

#64083: Trim the GitHub Actions workflows for older branches (and possibly `trunk`)
------------------------------+--------------------------
 Reporter:  johnbillion       |       Owner:  johnbillion
     Type:  task (blessed)    |      Status:  closed
 Priority:  normal            |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------
Changes (by johnbillion):

 * status:  reopened => closed
 * resolution:   => fixed


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64083#comment:71>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 15:34:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 15:34:46 -0000
Subject: [wp-trac] [WordPress Trac] #65168: AI Client: Unable to
 reliably select model for providers (model preference ignored /
 inconsistent API)
In-Reply-To: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
References: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
Message-ID: <066.6c540376cea49fcdba3c62a6fc832d89@wordpress.org>

#65168: AI Client: Unable to reliably select model for providers (model preference
ignored / inconsistent API)
--------------------------+------------------------------
 Reporter:  jabir20       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  AI            |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by jabir20):

 Thanks for checking.

 Yes — I tested again on WordPress 7.0-RC2, and I can confirm the issue
 still reproduces in my setup.

 Environment

 * WordPress: 7.0-RC2
 * AI Provider: AI Provider for Google (Gemini)
 * Local Docker setup
 * Same Gemini API key/project used successfully outside WordPress

 Observed behavior in RC2

 * `->model(...)` is still not available on `PromptBuilder`.
 * `->using_model_preference(...)` does not reliably force the selected
 model in my runtime path.
 * Requests still execute against `gemini-2.5-pro` in failure cases,
 resulting in:

   * `429 Too Many Requests`
   * quota errors specifically referencing `gemini-2.5-pro`

 Example:

 ```php
 $result = wp_ai_client_prompt( 'Say hello' )
     ->using_model_preference(
         'gemini-2.5-flash',
         'gemini-2.0-flash',
         'gemini-1.5-flash'
     )
     ->generate_text();
 ```

 Even with Flash models explicitly preferred, the runtime may still route
 to `gemini-2.5-pro`.

 Investigation
 I reviewed the `AI Provider for Google` plugin source and found that model
 sorting currently prioritizes `-pro` models before `-flash` models in
 `modelSortCallback()`.

 This appears to contribute to fallback/default selection behavior when
 explicit per-request preference is not honored consistently.

 Local workaround tested successfully
 I implemented a provider-side fallback patch locally, and this resolved
 the issue in RC2 while preserving the current “Pro-first” behavior.

 Changed file:
 `src/Models/GoogleTextGenerationModel.php`

 Summary of changes:

 1. `generateTextResult()` updated to:

 * try the primary model first (existing behavior)
 * on quota/rate-limit failure for `-pro` models, automatically retry Flash
 models

 2. Added helper:
    `sendGenerateContentRequest()`

 Used to execute requests against alternative fallback model IDs.

 3. Added helper:
    `shouldAttemptFlashFallback()`

 Triggers fallback only for:

 * `429`
 * `too many requests`
 * `quota`
 * `resource_exhausted`
 * `rate limit`

 4. Added helper:
    `getFlashFallbackModelIds()`

 Fallback order:

 * same-version flash model if available

   * example: `gemini-2.5-flash` for `gemini-2.5-pro`
 * `gemini-2.5-flash`
 * `gemini-2.0-flash`
 * `gemini-1.5-flash`

 Result after patch
 Requests that previously failed with:

 * `429 quota exceeded`
 * `gemini-2.5-pro`

 now successfully complete through Flash fallback models without requiring
 shortcode/plugin changes.

 Why this matters
 This impacts developers building plugins against the AI Client because:

 * model selection is not predictable
 * free-tier Gemini keys can fail unexpectedly
 * providers may override intended runtime model choice
 * multiple plugins sharing one provider configuration can conflict

 Suggested improvements

 * Provide a guaranteed and documented per-request model selection API
 * Ensure providers honor explicit model preferences consistently
 * Consider provider/core fallback handling for quota-restricted models
 (e.g. Pro → Flash)

 Happy to provide full patch diff or additional reproduction steps if
 useful.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65168#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 16:57:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 16:57:12 -0000
Subject: [wp-trac] [WordPress Trac] #65178: Tests: Add unit tests for
 wp_print_theme_file_tree()
Message-ID: <051.c4236ebe44b505feda4bc59991a6db63@wordpress.org>

#65178: Tests: Add unit tests for wp_print_theme_file_tree()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the wp_print_theme_file_tree() function in
 wp-admin/includes/misc.php. This function is responsible for outputting
 the hierarchical file list for the theme editor.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65178>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 16:59:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 16:59:54 -0000
Subject: [wp-trac] [WordPress Trac] #65168: AI Client: Unable to
 reliably select model for providers (model preference ignored /
 inconsistent API)
In-Reply-To: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
References: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
Message-ID: <066.3e7bc397dbd64f4cdf163d3fca487d17@wordpress.org>

#65168: AI Client: Unable to reliably select model for providers (model preference
ignored / inconsistent API)
--------------------------+---------------------
 Reporter:  jabir20       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0
Component:  AI            |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------
Changes (by jorbin):

 * milestone:  Awaiting Review => 7.0


Comment:

 Moving to 7.0 for visibility.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65168#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 17:13:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 17:13:48 -0000
Subject: [wp-trac] [WordPress Trac] #64622: Real-time collaboration: Add
 new REST endpoints, setting, and registered post meta
In-Reply-To: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
References: <051.c19624bf5d15fd463891edf06b71d30c@wordpress.org>
Message-ID: <066.0e77022785a0b1bd0f33353cc8c4a00e@wordpress.org>

#64622: Real-time collaboration: Add new REST endpoints, setting, and registered
post meta
-------------------------------------------------+-------------------------
 Reporter:  czarate                              |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  add-to-field-guide needs-dev-note    |     Focuses:
  close                                          |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 Going to close this out in an effort to clear the milestone. Please open
 separate follow up tickets for any related issues.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64622#comment:88>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 17:40:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 17:40:30 -0000
Subject: [wp-trac] [WordPress Trac] #65015: Connectors: Several strings
 are not translated
In-Reply-To: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
References: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
Message-ID: <066.b98c54330eaec4ed3d2d061da451aa14@wordpress.org>

#65015: Connectors: Several strings are not translated
-------------------------------------------------+-------------------------
 Reporter:  369work                              |       Owner:
                                                 |  westonruter
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  high                                 |   Milestone:  7.0
Component:  I18N                                 |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests connectors  |     Focuses:
  commit needs-dev-note fixed-major dev-         |
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:
     has-patch has-unit-tests connectors commit needs-dev-note fixed-major
     dev-feedback
     =>
     has-patch has-unit-tests connectors commit needs-dev-note fixed-major
     dev-reviewed


Comment:

 [62293] looks good to backport to the 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65015#comment:54>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 17:42:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 17:42:15 -0000
Subject: [wp-trac] [WordPress Trac] #65138: RTC: Real-time collaboration
 bug sprint for 7.0
In-Reply-To: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
References: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
Message-ID: <066.7e9736063593f10a98dc66e940a4342d@wordpress.org>

#65138: RTC: Real-time collaboration bug sprint for 7.0
-------------------------------------------------+-------------------------
 Reporter:  dmsnell                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests gutenberg-  |     Focuses:  tests
  merge                                          |
-------------------------------------------------+-------------------------

Comment (by desrosj):

 @dmsnell Will this race condition still be relevant if the architecture
 moves towards tables/transients instead?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65138#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 17:44:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 17:44:51 -0000
Subject: [wp-trac] [WordPress Trac] #64980: Notes needs gettext
In-Reply-To: <052.bebd4bef753cdda60cb3e99a230ce2bc@wordpress.org>
References: <052.bebd4bef753cdda60cb3e99a230ce2bc@wordpress.org>
Message-ID: <067.a29e0829c09bd48a1dd02fa0660ad435@wordpress.org>

#64980: Notes needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch i18n-change dev-reviewed   |     Focuses:
  commit                                         |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch dev-feedback i18n-change => has-patch i18n-change
     dev-reviewed commit


Comment:

 [62185] looks good for backporting.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64980#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 17:49:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 17:49:05 -0000
Subject: [wp-trac] [WordPress Trac] #65035: Abilities: Strip internal
 schema keywords from abilities REST responses
In-Reply-To: <060.11365645bf003f62fe2c244d23d3172e@wordpress.org>
References: <060.11365645bf003f62fe2c244d23d3172e@wordpress.org>
Message-ID: <075.e212b27ad3fb9da6e621bf10728b95c4@wordpress.org>

#65035: Abilities: Strip internal schema keywords from abilities REST responses
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Abilities API                        |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests fixed-      |     Focuses:
  major dev-reviewed                             |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62305" 62305]:
 {{{
 #!CommitTicketReference repository="" revision="62305"
 Abilities: Strip internal schema keywords from abilities REST responses.

 Remove WordPress-internal properties (`sanitize_callback`,
 `validate_callback`, `arg_options`) from ability `input_schema` and
 `output_schema` fields in REST responses. These properties are used
 server-side but are not valid JSON Schema keywords and cause client-side
 validators to fail.

 Reviewed by gziolo, desrosj.
 Merges [62221] to the 7.0 branch.

 Props jorgefilipecosta, ocean90, gziolo, desrosj.
 Fixes #65035.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65035#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 17:51:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 17:51:18 -0000
Subject: [wp-trac] [WordPress Trac] #65099: Fix: Only auto register
 settings if the plugin the connector references is installed and active
In-Reply-To: <060.0b8a8e3426646ee12db1e6e829f3d840@wordpress.org>
References: <060.0b8a8e3426646ee12db1e6e829f3d840@wordpress.org>
Message-ID: <075.3f0cc9701ec8f557c904070c0e09518d@wordpress.org>

#65099: Fix: Only auto register settings if the plugin the connector references is
installed and active
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests commit      |     Focuses:
  fixed-major dev-reviewed                       |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch has-unit-tests commit dev-feedback fixed-major =>
     has-patch has-unit-tests commit fixed-major dev-reviewed


Comment:

 [62289] looks good to backport.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65099#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 17:53:03 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 17:53:03 -0000
Subject: [wp-trac] [WordPress Trac] #65099: Fix: Only auto register
 settings if the plugin the connector references is installed and active
In-Reply-To: <060.0b8a8e3426646ee12db1e6e829f3d840@wordpress.org>
References: <060.0b8a8e3426646ee12db1e6e829f3d840@wordpress.org>
Message-ID: <075.104865ad53639edadbddcc4496c73fde@wordpress.org>

#65099: Fix: Only auto register settings if the plugin the connector references is
installed and active
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit      |     Focuses:
  fixed-major dev-reviewed                       |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62306" 62306]:
 {{{
 #!CommitTicketReference repository="" revision="62306"
 Connectors: Gate default setting auto-registration on `is_active`.

 Update `_wp_register_default_connector_settings()` to register a
 connector's default API key setting only when the connector's
 `plugin.is_active` callback returns `true`.

 Add tests covering the gate's branches: setting skipped when `is_active`
 returns `false`, setting registered when it returns `true`.

 Reviewed by desrosj.
 Merges [62289] to the 7.0 branch.

 Props jorgefilipecosta, gziolo, peterwilsoncc.
 Fixes #65099.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65099#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 17:54:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 17:54:14 -0000
Subject: [wp-trac] [WordPress Trac] #64980: Notes needs gettext
In-Reply-To: <052.bebd4bef753cdda60cb3e99a230ce2bc@wordpress.org>
References: <052.bebd4bef753cdda60cb3e99a230ce2bc@wordpress.org>
Message-ID: <067.5b75a5481f7a3200b2346d6be7830865@wordpress.org>

#64980: Notes needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch i18n-change dev-reviewed   |     Focuses:
  commit fixed-major                             |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch i18n-change dev-reviewed commit => has-patch i18n-
     change dev-reviewed commit fixed-major


Comment:

 Adding `fixed-major` so the ticket is properly
 [https://core.trac.wordpress.org/tickets/major/workflow grouped by
 workflow reports].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64980#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 18:03:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 18:03:49 -0000
Subject: [wp-trac] [WordPress Trac] #65179: Tests: Add unit tests for
 wp_print_plugin_file_tree()
Message-ID: <051.a62171d4b5f99c442dfa662dc6e65ed2@wordpress.org>

#65179: Tests: Add unit tests for wp_print_plugin_file_tree()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the wp_print_plugin_file_tree() function
 in wp-admin/includes/misc.php. This function is responsible for outputting
 the hierarchical file list for the plugin editor.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65179>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 18:09:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 18:09:13 -0000
Subject: [wp-trac] [WordPress Trac] #65168: AI Client: Unable to
 reliably select model for providers (model preference ignored /
 inconsistent API)
In-Reply-To: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
References: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
Message-ID: <066.74ad8a785bd497f32d849c34581f54a7@wordpress.org>

#65168: AI Client: Unable to reliably select model for providers (model preference
ignored / inconsistent API)
-----------------------------------+---------------------
 Reporter:  jabir20                |       Owner:  (none)
     Type:  defect (bug)           |      Status:  new
 Priority:  normal                 |   Milestone:  7.0
Component:  AI                     |     Version:  trunk
 Severity:  normal                 |  Resolution:
 Keywords:  ai-client needs-patch  |     Focuses:
-----------------------------------+---------------------
Changes (by JeffPaul):

 * keywords:   => ai-client needs-patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65168#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 18:10:26 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 18:10:26 -0000
Subject: [wp-trac] [WordPress Trac] #65168: AI Client: Unable to
 reliably select model for providers (model preference ignored /
 inconsistent API)
In-Reply-To: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
References: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
Message-ID: <066.df957486f45c7675cb5b6212b066d514@wordpress.org>

#65168: AI Client: Unable to reliably select model for providers (model preference
ignored / inconsistent API)
-----------------------------------+---------------------
 Reporter:  jabir20                |       Owner:  (none)
     Type:  defect (bug)           |      Status:  new
 Priority:  normal                 |   Milestone:  7.0
Component:  AI                     |     Version:  trunk
 Severity:  normal                 |  Resolution:
 Keywords:  ai-client needs-patch  |     Focuses:
-----------------------------------+---------------------

Comment (by jason_the_adams):

 Hi @jabir20!

 I'm admittedly confused. I see you're expecting a `->model()` method,
 which you're right there isn't one. But there is a `->using_model()`
 method. Is that not working?

 Did you see a `model()` method documented somewhere? Or simply not notice
 there's a `using_model()` method? I just want to make sure we're not
 causing this confusion somewhere. 🙂

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65168#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 18:16:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 18:16:01 -0000
Subject: [wp-trac] [WordPress Trac] #65168: AI Client: Unable to
 reliably select model for providers (model preference ignored /
 inconsistent API)
In-Reply-To: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
References: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
Message-ID: <066.51cccaf1417535c03c828575728444b2@wordpress.org>

#65168: AI Client: Unable to reliably select model for providers (model preference
ignored / inconsistent API)
--------------------------+---------------------
 Reporter:  jabir20       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0
Component:  AI            |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------
Changes (by dkotter):

 * keywords:  ai-client needs-patch =>


Comment:

 Yeah, to Jason's point, there currently isn't a `model` method on the
 `PromptBuilder` class, which is why you get a fatal error when trying to
 use that. The correct method to use is `using_model`. Example:

 {{{#!php
 <?php
 use WordPress\AiClient\AiClient;

 $prompt_builder = wp_ai_client_prompt( 'Hello' )
         ->using_model( AiClient::defaultRegistry()->getProviderModel(
 'openai', 'gpt-4.1-nano' )
         ->generate_text();
 }}}

 In regards to `using_model_preference`, I've not seen that issue myself,
 the AI Client will always respect the model preferences you set there
 assuming that model is available and meets the requirements.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65168#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 18:36:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 18:36:01 -0000
Subject: [wp-trac] [WordPress Trac] #65121: Command Palette: Label can
 be incorrect for sites served over a CDN
In-Reply-To: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
References: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
Message-ID: <072.b84784622dbc419d5f2bf236b84c7270@wordpress.org>

#65121: Command Palette: Label can be incorrect for sites served over a CDN
------------------------------------+----------------------------
 Reporter:  peterwilsoncc           |       Owner:  peterwilsoncc
     Type:  defect (bug)            |      Status:  reopened
 Priority:  normal                  |   Milestone:  7.0
Component:  Toolbar                 |     Version:  trunk
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+----------------------------

Comment (by desrosj):

 I ran this through Claude and it pointed out a few things that I've
 confirmed and tested.

 - I noticed that the PHP-based Regex has `/i` but the JavaScript pattern
 does not. Is this intentional? If not, we should probably also be case
 insensitive in the JavaScript.
 - It seems that it's possible to encounter a `TypeError` if a plugin or
 theme manipulates the admin bar and `querySelector` is unable to find the
 element.

 I've created a PR with both of these fixes.

 A few other things Claude noted that aren't blockers (in my opinion):
 - `navigator.userAgent` is being deprecated in favor of
 `navigator.userAgentData`. Not an issue today, but possibly in the future.
 - The pattern does not cover older iPads. While newer iPads report
 desktop-like UA values, older ones use `iPad`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65121#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 18:56:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 18:56:24 -0000
Subject: [wp-trac] [WordPress Trac] #65180: Tests: Add unit tests for
 wp_reset_vars()
Message-ID: <051.4cf0339cdd8e9bce630bf5914d78c61a@wordpress.org>

#65180: Tests: Add unit tests for wp_reset_vars()
-----------------------------+-----------------------------
 Reporter:  pbearne          |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Administration   |    Version:
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 This ticket adds unit tests for the wp_reset_vars() function in wp-
 admin/includes/misc.php. This function resets global variables based on
 $_GET and $_POST values.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65180>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:02:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:02:44 -0000
Subject: [wp-trac] [WordPress Trac] #64957: Connectors:
 `WP_Connector_Registry::register()` ignores custom `setting_name`
In-Reply-To: <060.efba94ef2ed1670ece3ced63ea3ce35e@wordpress.org>
References: <060.efba94ef2ed1670ece3ced63ea3ce35e@wordpress.org>
Message-ID: <075.79251c29a34b014d2e4281bb2c500f1b@wordpress.org>

#64957: Connectors: `WP_Connector_Registry::register()` ignores custom
`setting_name`
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  closed
 Priority:  high                                 |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch dev-reviewed has-unit-     |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------

Comment (by jorbin):

 @jorgefilipecosta Please remember to follow the commit message guidelines
 https://make.wordpress.org/core/handbook/best-practices/commit-messages/
 so that it's easy to track what has been merged.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64957#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:06:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:06:21 -0000
Subject: [wp-trac] [WordPress Trac] #65002: Connectors: Replace
 plugin.slug with plugin.file and harden plugin data handling
In-Reply-To: <060.a8d38794450573f71fbec1ec7c7a0f56@wordpress.org>
References: <060.a8d38794450573f71fbec1ec7c7a0f56@wordpress.org>
Message-ID: <075.83d559ff337bceb0f1ccf0891ffa3a76@wordpress.org>

#65002: Connectors: Replace plugin.slug with plugin.file and harden plugin data
handling
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------

Comment (by jorbin):

 @jorgefilipecosta Please remember to follow the commit message guidelines
 ​https://make.wordpress.org/core/handbook/best-practices/commit-messages/
 so that it's easy to track what has been merged.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65002#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:26:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:26:06 -0000
Subject: [wp-trac] [WordPress Trac] #65181: Tests: Add unit tests for
 show_message()
Message-ID: <051.f4efc02401b1c52cd03c880e35d04cd4@wordpress.org>

#65181: Tests: Add unit tests for show_message()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the show_message() function in wp-
 admin/includes/misc.php. This function is responsible for displaying
 administration messages and handling WP_Error objects.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65181>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:26:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:26:29 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.c496286f78ccc2578ca69103f15cebdf@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------

Comment (by jorbin):

 I think It would be best to get all of the remaining issues resolved so
 that it can be backported in one go before the next beta

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:27:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:27:15 -0000
Subject: [wp-trac] [WordPress Trac] #64685: Bulk Edit dropdown height
 increased compared to previous version
In-Reply-To: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
References: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
Message-ID: <067.05d7df1523c9973aca900b8479241ba1@wordpress.org>

#64685: Bulk Edit dropdown height increased compared to previous version
-------------------------------------------------+-------------------------
 Reporter:  mohitbsf                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Quick/Bulk Edit                      |     Version:  trunk
 Severity:  minor                                |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:  css
  fixed-major                                    |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  admin-reskin has-patch dev-reviewed => admin-reskin has-patch
     dev-reviewed fixed-major


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64685#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:27:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:27:18 -0000
Subject: [wp-trac] [WordPress Trac] #65168: AI Client: Unable to
 reliably select model for providers (model preference ignored /
 inconsistent API)
In-Reply-To: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
References: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
Message-ID: <066.3190507a817c69cd23bf5a6896387241@wordpress.org>

#65168: AI Client: Unable to reliably select model for providers (model preference
ignored / inconsistent API)
--------------------------+---------------------
 Reporter:  jabir20       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0
Component:  AI            |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------

Comment (by jabir20):

 Thanks for the clarification.

 I retested on WordPress 7.0-RC2 and realized my earlier report mixed two
 different things.

 First, I incorrectly tried `->model()`. I now understand the correct API
 is `->using_model()`.

 I tested with:

 ``php
 $model =
 \WordPress\AiClient\AiClient::defaultRegistry()->getProviderModel(
     'google',
     'gemini-2.5-flash'
 );

 $result = wp_ai_client_prompt( 'Say hello' )
     ->using_model( $model )
     ->generate_text();
 ``

 This does appear to explicitly select the requested model in RC2.

 The new error I receive is:

 ``text
 Forbidden (403) - Your project has been denied access. Please contact
 support.
 ``

 So I believe the explicit model selection issue is not a Core bug. This
 now looks more like a Google/Gemini API project access or provider
 configuration issue on my side.

 I will continue testing `using_model_preference()` separately, but for now
 I think the `->model()` part of my report can be ignored as my
 misunderstanding.

 Thanks for helping point me in the right direction.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65168#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:38:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:38:44 -0000
Subject: [wp-trac] [WordPress Trac] #64685: Bulk Edit dropdown height
 increased compared to previous version
In-Reply-To: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
References: <052.53b49d25a3b1c1e2b2913b40d78297d6@wordpress.org>
Message-ID: <067.53a3e28beaaa63a2cd6f483142ec6575@wordpress.org>

#64685: Bulk Edit dropdown height increased compared to previous version
-------------------------------------------------+-------------------------
 Reporter:  mohitbsf                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Quick/Bulk Edit                      |     Version:  trunk
 Severity:  minor                                |  Resolution:  fixed
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:  css
  fixed-major                                    |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62307" 62307]:
 {{{
 #!CommitTicketReference repository="" revision="62307"
 Quick/Bulk Edit: Restore compact size of inline edit select.

 Follow-up to [61827], [62171].

 Reviewed-by wildworks, jorbin.
 Merges [62296] to the 7.0 branch.

 Props wildworks, mukesh27, audrasjb, SergeyBiryukov.
 Fixes #64685.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64685#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:44:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:44:24 -0000
Subject: [wp-trac] [WordPress Trac] #65181: Tests: Add unit tests for
 show_message()
In-Reply-To: <051.f4efc02401b1c52cd03c880e35d04cd4@wordpress.org>
References: <051.f4efc02401b1c52cd03c880e35d04cd4@wordpress.org>
Message-ID: <066.eaefca0da93fe3814f3966d0aea00832@wordpress.org>

#65181: Tests: Add unit tests for show_message()
----------------------------+------------------------------
 Reporter:  pbearne         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  dev-feedback    |     Focuses:
----------------------------+------------------------------
Changes (by pbearne):

 * keywords:   => dev-feedback


Comment:

 The show_message() function is currently difficult to test because it has
 two major side effects:
 1. Direct Output: It uses echo to print the message, requiring output
 buffering to capture it.
 2. Buffer Flushing: It calls wp_ob_end_flush_all() and flush(), which
 force-closes all active output buffers. This interferes with PHPUnit's own
 output handling and makes it impossible to reliably use ob_start() within
 a test to capture the output.
 **Proposed Refactoring**
 To make show_message() testable while maintaining backward compatibility,
 we can split the formatting logic from the output logic.
 Option 1: Add a return parameter (Recommended) We can add an optional
 second parameter $echo that defaults to true. When set to false, the
 function returns the HTML string instead of printing and flushing.
 {{{#!php
 <?php
 function show_message( $message, $echo = true ) {
     if ( is_wp_error( $message ) ) {
         if ( $message->get_error_data() && is_string(
 $message->get_error_data() ) ) {
             $message = $message->get_error_message() . ': ' .
 $message->get_error_data();
         } else {
             $message = $message->get_error_message();
         }
     }

     $output = "<p>$message</p>\n";

     if ( ! $echo ) {
         return $output;
     }

     echo $output;
     wp_ob_end_flush_all();
     flush();
 }
 }}}

 Option 2: Extract a "get" version Create a new function get_show_message()
 that handles the string conversion and wrapping, and have show_message()
 call it.
 {{{#!php
 <?php
 function get_show_message( $message ) {
     if ( is_wp_error( $message ) ) {
         if ( $message->get_error_data() && is_string(
 $message->get_error_data() ) ) {
             return $message->get_error_message() . ': ' .
 $message->get_error_data();
         }
         return $message->get_error_message();
     }
     return $message;
 }

 function show_message( $message ) {
     echo "<p>" . get_show_message( $message ) . "</p>\n";
     wp_ob_end_flush_all();
     flush();
 }
 }}}

 Why Option 1 is better for WordPress Core:

 * It's a common pattern in WordPress (e.g., wp_dropdown_categories(),
 get_the_tag_list()).
 * It allows tests to call show_message( $msg, false ) and assert the
 returned string without causing "risky" test warnings in PHPUnit.
 * It doesn't introduce a new global function that might have naming
 conflicts or limited utility.
 Would you like me to implement one of these changes and update the tests
 accordingly?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65181#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:47:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:47:18 -0000
Subject: [wp-trac] [WordPress Trac] #65182: Tests: Add unit tests for
 wp_doc_link_parse()
Message-ID: <051.3b6f31d5da7294aff99af0c5a5275f58@wordpress.org>

#65182: Tests: Add unit tests for wp_doc_link_parse()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the wp_doc_link_parse()
 function in wp-admin/includes/misc.php to ensure it correctly identifies
 function calls while ignoring local definitions and class methods.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65182>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:53:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:53:49 -0000
Subject: [wp-trac] [WordPress Trac] #65183: Tests: Add unit tests for
 set_screen_options()
Message-ID: <051.a40b531f0c39207a5e8a88fb2d669e2e@wordpress.org>

#65183: Tests: Add unit tests for set_screen_options()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the set_screen_options() function in wp-
 admin/includes/misc.php. The tests will cover saving screen options,
 handling missing or invalid data, and verifying user authentication and
 nonce checks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65183>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:55:03 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:55:03 -0000
Subject: [wp-trac] [WordPress Trac] #65012: Fix: Register Akismet
 Anti-Spam as a connector
In-Reply-To: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
References: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
Message-ID: <075.11d6063f3929e159c771c3516ef4c9db@wordpress.org>

#65012: Fix: Register Akismet Anti-Spam as a connector
---------------------------------------------+-----------------------------
 Reporter:  jorgefilipecosta                 |       Owner:
                                             |  jorgefilipecosta
     Type:  feature request                  |      Status:  reopened
 Priority:  normal                           |   Milestone:  7.0
Component:  Plugins                          |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------------

Comment (by desrosj):

 In [changeset:"62308" 62308]:
 {{{
 #!CommitTicketReference repository="" revision="62308"
 Connectors: Partial backport of [62210].

 This merges the modifications from [62210] that were not directly
 reverting the changes in [62193] to the 7.0 branch.

 While [62193] never made its way into the 7.0 branch, these changes are
 needed to ensure backports touching these lines are able to complete
 without merge conflicts.

 Reviewed by desrosj.
 Partially merges [62210] to the 7.0 branch.

 Props peterwilsoncc, jorgefilipecosta, johnbillion, eclev91, desrosj,
 davidbaumwald, jorbin.
 See #65012.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65012#comment:57>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:55:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:55:48 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.e1d2d648dfefbc1fa8ee5ca09a7746b7@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  connectors has-patch commit has-     |     Focuses:
  unit-tests fixed-major dev-reviewed            |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  connectors has-patch commit has-unit-tests dev-feedback fixed-
     major => connectors has-patch commit has-unit-tests fixed-major dev-
     reviewed


Comment:

 [62288] looks good for backporting.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:56:56 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:56:56 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.726af0b5b79b4a4c35e7c9a6dcf0fe3d@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  connectors has-patch commit has-     |     Focuses:
  unit-tests fixed-major dev-reviewed            |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62309" 62309]:
 {{{
 #!CommitTicketReference repository="" revision="62309"
 Connectors: Add `is_active` callback support to plugin registration.

 Adds an optional `is_active` callable to the `plugin` definition accepted
 by `WP_Connector_Registry::register()`. The callback receives no
 arguments, must return a boolean, and is used by the Connectors screen to
 decide whether a connector's backing plugin is currently active. When
 omitted, it defaults to `__return_true`; when provided but not callable,
 registration fails with a `_doing_it_wrong()` notice.

 Developed in: https://github.com/WordPress/wordpress-develop/pull/11565

 Reviewed by desrosj.
 Merges [62288] to the 7.0 branch.

 Props iamadisingh, jorgefilipecosta, mukesh27, gziolo, desrosj.
 Fixes #65020.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 19:57:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 19:57:15 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.e6b2d1fda62bceeaa1128eafc9498919@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  connectors has-patch has-unit-tests  |     Focuses:
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  connectors has-patch commit has-unit-tests fixed-major dev-
     reviewed => connectors has-patch has-unit-tests
 * status:  closed => reopened
 * resolution:  fixed =>
 * milestone:  Awaiting Review => 7.0


Comment:

 Reopening to consider the remaining feedback.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 20:27:57 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 20:27:57 -0000
Subject: [wp-trac] [WordPress Trac] #65184: Tests: Add unit tests for
 admin_color_scheme_picker()
Message-ID: <051.7695af797e0a55f44e0713d17de2d542@wordpress.org>

#65184: Tests: Add unit tests for admin_color_scheme_picker()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the admin_color_scheme_picker() function
 in wp-admin/includes/misc.php. The tests will cover the correct sorting of
 color schemes, the default selection, and the HTML output generation
 including nonces and radio buttons.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65184>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 20:58:58 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 20:58:58 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.d88665308c86b7ae27f0c26194675a20@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
---------------------------+-------------------------
 Reporter:  jonsurrell     |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  high           |   Milestone:  7.0
Component:  Script Loader  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+-------------------------
Changes (by jorbin):

 * priority:  normal => high


Comment:

 How much effort would be needed to update [61611] if the feature is
 reverted? If it's low/medium effort, then option A seems like the best
 option.

 Otherwise, I would like to also propose an Option E: Throw a
 `doing_it_wrong` if `module_dependencies` is set without `in_footer` as
 `true` or `strategy` set as `defer`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:14:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:14:08 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.8aaa36a6f285a97e500a6d1b0af7e5aa@wordpress.org>

#64536: About Page - 7.0
----------------------------+---------------------
 Reporter:  desrosj         |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:
----------------------------+---------------------
Changes (by jorbin):

 * keywords:   => needs-patch


Comment:

 Given the short time remaining, I think we need to move to code and get
 this committed quickly.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:26:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:26:15 -0000
Subject: [wp-trac] [WordPress Trac] #64904: Real time collboration:
 determine approach for opt in setting for users in Settings > Writing
In-Reply-To: <052.0bbda23d420073a23acb5985c10fd47e@wordpress.org>
References: <052.0bbda23d420073a23acb5985c10fd47e@wordpress.org>
Message-ID: <067.90bca0df0bd92cf5e2d6cb7f22f18492@wordpress.org>

#64904: Real time collboration: determine approach for opt in setting for users in
Settings > Writing
----------------------------+--------------------------------
 Reporter:  annezazu        |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  7.0
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  ui, accessibility
----------------------------+--------------------------------

Comment (by jorbin):

 These "new" badges are something that doesn't exist yet so it is going to
 need to take into account every color scheme.

 Also, the transport is only known client side, so I think we would need to
 bootstrap the entire editor in order to know what transport is being used.
 I don't think that is worth it.

 Unless there is a patch in the next ~24 hours, I don't think it's worth
 changing the design at this point and we should just adjust the order so
 this is at the top of the page.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64904#comment:51>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:30:43 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:30:43 -0000
Subject: [wp-trac] [WordPress Trac] #65185: Tests: Add unit tests for
 wp_color_scheme_settings()
Message-ID: <051.f0d42d9f5b9084ddbb75ad84ab34a6d9@wordpress.org>

#65185: Tests: Add unit tests for wp_color_scheme_settings()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the wp_color_scheme_settings() function in
 wp-admin/includes/misc.php. The tests will verify that the function
 correctly outputs the color scheme picker and manages the associated
 scripts and settings for the user profile.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65185>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:35:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:35:05 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.8f34b9bf6c754ff53016b0f344567ada@wordpress.org>

#65151: Dashboard Widgets not draggable
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Administration                       |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-screenshots 2nd-    |     Focuses:  ui, css
  opinion                                        |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  admin-reskin has-screenshots => admin-reskin has-screenshots
     2nd-opinion


Comment:

 Tested using playground and Chrome on macOS and each of the oddities with
 drag and drop that I see is also present in 6.9, so I'm not sure if this
 is a regression in 7.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:38:43 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:38:43 -0000
Subject: [wp-trac] [WordPress Trac] #65186: Tests: Add unit tests for
 extract_from_markers()
Message-ID: <051.b94ac652cf391f0d7cbf6e66d888a16f@wordpress.org>

#65186: Tests: Add unit tests for extract_from_markers()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the extract_from_markers()
 function in wp-admin/includes/misc.php. The tests will cover extracting
 content between custom markers, handling missing files, empty markers, and
 various line formats (including comments).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65186>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:39:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:39:33 -0000
Subject: [wp-trac] [WordPress Trac] #65168: AI Client: Unable to
 reliably select model for providers (model preference ignored /
 inconsistent API)
In-Reply-To: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
References: <051.28acdff48d0591ac6d70f34c82bed104@wordpress.org>
Message-ID: <066.527df8a7c18a5d71d3bc27500b69fb66@wordpress.org>

#65168: AI Client: Unable to reliably select model for providers (model preference
ignored / inconsistent API)
--------------------------+----------------------
 Reporter:  jabir20       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  AI            |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by jorbin):

 * status:  new => closed
 * version:  trunk =>
 * resolution:   => invalid
 * milestone:  7.0 =>


Comment:

 Based on the latest comments, this does not seem to be a valid issue that
 is actionable, so I am closing this ticket.  Thank you @jason_the_adams
 @dkotter and @jabir20 for getting to the bottom of it!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65168#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:45:09 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:45:09 -0000
Subject: [wp-trac] [WordPress Trac] #65012: Fix: Register Akismet
 Anti-Spam as a connector
In-Reply-To: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
References: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
Message-ID: <075.245345d3801745e005db84c381470427@wordpress.org>

#65012: Fix: Register Akismet Anti-Spam as a connector
---------------------------------------------+-----------------------------
 Reporter:  jorgefilipecosta                 |       Owner:
                                             |  jorgefilipecosta
     Type:  feature request                  |      Status:  reopened
 Priority:  normal                           |   Milestone:  7.0
Component:  Plugins                          |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------------

Comment (by jorgefilipecosta):

 In [changeset:"62310" 62310]:
 {{{
 #!CommitTicketReference repository="" revision="62310"
 Connectors: Register Akismet Anti-Spam as a connector.

 Akismet is bundled with WordPress core, but it wasn't appearing on the
 Connectors screen even when present on the file system.

 Partially reverts [62210], bringing back the main part of [62193].
 Follow-up to [62210], [62193].
 Developed in https://github.com/WordPress/wordpress-develop/pull/11688.

 Props audrasjb, bluefuton, davidbaumwald, desrosj, eclev91, gziolo,
 johnbillion, jorbin, jorgefilipecosta, lukecarbis, matt, matveb,
 peterwilsoncc, westonruter.
 See #65012.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65012#comment:58>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:45:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:45:54 -0000
Subject: [wp-trac] [WordPress Trac] #65186: Tests: Add unit tests for
 _customizer_mobile_viewport_meta() (was: Tests: Add unit tests for
 extract_from_markers())
In-Reply-To: <051.b94ac652cf391f0d7cbf6e66d888a16f@wordpress.org>
References: <051.b94ac652cf391f0d7cbf6e66d888a16f@wordpress.org>
Message-ID: <066.b1c705054a906bd860794e10abe796dc@wordpress.org>

#65186: Tests: Add unit tests for _customizer_mobile_viewport_meta()
----------------------------+------------------------------
 Reporter:  pbearne         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------
Description changed by pbearne:

Old description:

> This ticket adds comprehensive unit tests for the extract_from_markers()
> function in wp-admin/includes/misc.php. The tests will cover extracting
> content between custom markers, handling missing files, empty markers,
> and various line formats (including comments).

New description:

 This ticket adds unit tests for the _customizer_mobile_viewport_meta()
 function in wp-admin/includes/misc.php. The tests will verify that the
 function correctly appends the mobile-specific viewport settings to the
 existing viewport meta string.

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65186#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:55:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:55:32 -0000
Subject: [wp-trac] [WordPress Trac] #65138: RTC: Real-time collaboration
 bug sprint for 7.0
In-Reply-To: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
References: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
Message-ID: <066.e4d9b6cb3abc3740fcef5196be988b42@wordpress.org>

#65138: RTC: Real-time collaboration bug sprint for 7.0
-------------------------------------------------+-------------------------
 Reporter:  dmsnell                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests gutenberg-  |     Focuses:  tests
  merge                                          |
-------------------------------------------------+-------------------------

Comment (by dmsnell):

 In [changeset:"62311" 62311]:
 {{{
 #!CommitTicketReference repository="" revision="62311"
 RTC: Promote auto-draft posts on first autosave for collaborative sessions
 to avoid post loss.

 When an RTC session in the editor saves edits on a draft post, they always
 save into an autosave revision. This prevents a sync but where storing to
 the post itself would lead to duplicate edits. This was set in
 wordpress/gutenberg commit 9df142b839320316b406ee1a02e23704d42f8719.
 However, there is an exception to this rule: the first session to save
 edits needs to promote the autosave revision into a real draft post, if a
 post doesn’t exist. The reason is that WordPress hides autosaves.

 That is, multiple people could be editing a draft post and then once they
 close it, never be able to find it again. While the data is still in the
 database, this is a loss of the post from a practical standpoint.

 This change introduces an exception where the first time a collaborative
 session is saving draft edits, the autodraft is promoted to a real draft
 post, making it visible in the post list.

 AI Disclaimer: This bug was detected in a fuzzing system built by AI
 models and the fix was first proposed by an AI model.

 Developed in: https://github.com/WordPress/gutenberg/pull/77865
 Discussed in: https://core.trac.wordpress.org/ticket/65138
 See also: https://github.com/WordPress/gutenberg/pull/77716

 Follow-up to [61680].
 Props danluu, dmsnell.
 See #65138.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65138#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:58:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:58:08 -0000
Subject: [wp-trac] [WordPress Trac] #65138: RTC: Real-time collaboration
 bug sprint for 7.0
In-Reply-To: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
References: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
Message-ID: <066.e1cd83910bdcb7793851d7dffbf96e32@wordpress.org>

#65138: RTC: Real-time collaboration bug sprint for 7.0
-------------------------------------------------+-------------------------
 Reporter:  dmsnell                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests gutenberg-  |     Focuses:  tests
  merge dev-feedback                             |
-------------------------------------------------+-------------------------
Changes (by dmsnell):

 * keywords:  has-patch has-unit-tests gutenberg-merge => has-patch has-
     unit-tests gutenberg-merge dev-feedback


Comment:

 Adding `dev-feedback` for backport of [62311] into 7.0. It is merged into
 Gutenberg and merged into `trunk`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65138#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 21:59:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 21:59:41 -0000
Subject: [wp-trac] [WordPress Trac] #65187: Tests: Add unit tests for
 wp_admin_viewport_meta()
Message-ID: <051.9f5ded5d422cf8280c03edf700e7b61a@wordpress.org>

#65187: Tests: Add unit tests for wp_admin_viewport_meta()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the wp_admin_viewport_meta()
 function in wp-admin/includes/misc.php. The tests will cover the default
 meta tag generation, the admin_viewport_meta filter, and proper attribute
 escaping.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65187>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 22:00:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 22:00:59 -0000
Subject: [wp-trac] [WordPress Trac] #65138: RTC: Real-time collaboration
 bug sprint for 7.0
In-Reply-To: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
References: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
Message-ID: <066.5ad9e067ba412582e260991214e3202e@wordpress.org>

#65138: RTC: Real-time collaboration bug sprint for 7.0
-------------------------------------------------+-------------------------
 Reporter:  dmsnell                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests gutenberg-  |     Focuses:  tests
  merge dev-feedback                             |
-------------------------------------------------+-------------------------

Comment (by dmsnell):

 @desrosj we have a few hundred identified bugs and are grouping them in
 this ticket. at least //most// of them would remain after a change to
 transients or a table.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65138#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 22:08:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 22:08:27 -0000
Subject: [wp-trac] [WordPress Trac] #65121: Command Palette: Label can
 be incorrect for sites served over a CDN
In-Reply-To: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
References: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
Message-ID: <072.6bcd63393a63beef1f37d9f909af54e1@wordpress.org>

#65121: Command Palette: Label can be incorrect for sites served over a CDN
------------------------------------+----------------------------
 Reporter:  peterwilsoncc           |       Owner:  peterwilsoncc
     Type:  defect (bug)            |      Status:  reopened
 Priority:  normal                  |   Milestone:  7.0
Component:  Toolbar                 |     Version:  trunk
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+----------------------------

Comment (by westonruter):

 @desrosj PR approved, though not sure about the changes to `.github`.

 Regarding `navigator.userAgentData`, this is not supported by Safari or
 Firefox: https://caniuse.com/mdn-api_navigator_useragentdata

 I don't think it is actually deprecated. At least, it is not noted as such
 in MDN: https://developer.mozilla.org/en-
 US/docs/Web/API/Navigator/userAgent

 I think the desire was to deprecate it to try to move away from
 fingerprinting, but and this seems to have been short-lived and it seems
 it is not discouraged: https://stackoverflow.com/a/43754322

 This was also discussed on the merged PR (in a resolved comment):
 https://github.com/WordPress/wordpress-
 develop/pull/11636#discussion_r3144372264

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65121#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 22:10:35 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 22:10:35 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.5af6895d96c5fcbbfa676a8b7c9583f0@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests 2nd-opinion               |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  has-screenshots admin-reskin has-patch has-unit-tests => has-
     screenshots admin-reskin has-patch has-unit-tests 2nd-opinion


Comment:

 Each of these proposed solutions is a fairly large, and we are only two
 days away from the new beta 1.  I think reverting [62025] and punting this
 to 7.1 is the safest solution.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 22:12:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 22:12:54 -0000
Subject: [wp-trac] [WordPress Trac] #65012: Fix: Register Akismet
 Anti-Spam as a connector
In-Reply-To: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
References: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
Message-ID: <075.0bc71ea555f8c49f5b56cb97a25e0536@wordpress.org>

#65012: Fix: Register Akismet Anti-Spam as a connector
---------------------------------------------+-----------------------------
 Reporter:  jorgefilipecosta                 |       Owner:
                                             |  jorgefilipecosta
     Type:  feature request                  |      Status:  reopened
 Priority:  normal                           |   Milestone:  7.0
Component:  Plugins                          |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------------

Comment (by jorgefilipecosta):

 Replying to [comment:55 wildworks]:
 > The AI plugin callout section states, "Connect a provider below to
 generate featured images, alt text, titles, excerpts, and more." However,
 in my understanding, even if the Akismet API key is set, no AI features
 can be utilized. This could potentially confuse users. At the very least,
 the text in the callout section may need improvement.


 Thank you for raising this issue, @wildworks. The banner code is on the
 Gutenberg repo; I proposed a small improvement there.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65012#comment:59>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 22:15:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 22:15:14 -0000
Subject: [wp-trac] [WordPress Trac] #65100: Accessibility issues in
 admin Font Library
In-Reply-To: <053.fd1c73df50e7a84ff15cd733e2c7ac6f@wordpress.org>
References: <053.fd1c73df50e7a84ff15cd733e2c7ac6f@wordpress.org>
Message-ID: <068.577026e0f03d6518deb65133ad2278b4@wordpress.org>

#65100: Accessibility issues in admin Font Library
--------------------------+----------------------------
 Reporter:  joedolson     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0
Component:  Themes        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility
--------------------------+----------------------------
Changes (by jorbin):

 * keywords:  has-patch =>


Comment:

 As this needs to be fixed in Gutenberg, I'm removing the `has-patch`
 keyword.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65100#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 22:19:58 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 22:19:58 -0000
Subject: [wp-trac] [WordPress Trac] #65138: RTC: Real-time collaboration
 bug sprint for 7.0
In-Reply-To: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
References: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
Message-ID: <066.b2619ce3db4e4305ec8e1bf56f8a8802@wordpress.org>

#65138: RTC: Real-time collaboration bug sprint for 7.0
-------------------------------------------------+-------------------------
 Reporter:  dmsnell                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests gutenberg-  |     Focuses:  tests
  merge fixed-major dev-reviewed                 |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  has-patch has-unit-tests gutenberg-merge dev-feedback => has-
     patch has-unit-tests gutenberg-merge fixed-major dev-reviewed


Comment:

 [62311] looks good for backport to 7.0

 @dmsnell It may make sense to open separate tickets for each issue,
 otherwise the keywords are going to get tricky and it may be easy to miss
 some backports.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65138#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 22:27:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 22:27:39 -0000
Subject: [wp-trac] [WordPress Trac] #64948: Media Modal: Can no longer
 set attachment filters
In-Reply-To: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
References: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
Message-ID: <074.42763e65603022e028e5fa1c70869b79@wordpress.org>

#64948: Media Modal: Can no longer set attachment filters
------------------------------+-------------------------
 Reporter:  Bernhard Reiter   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  7.0
Component:  Media             |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  javascript
------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  has-patch => has-patch commit


Comment:

 https://github.com/WordPress/wordpress-develop/pull/11415/ has an approval
 and test reports, so I think this is good to move forward.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64948#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 22:33:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 22:33:29 -0000
Subject: [wp-trac] [WordPress Trac] #65138: RTC: Real-time collaboration
 bug sprint for 7.0
In-Reply-To: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
References: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
Message-ID: <066.81c4f64d48881fb6b30fa7a893078c6c@wordpress.org>

#65138: RTC: Real-time collaboration bug sprint for 7.0
-------------------------------------------------+-------------------------
 Reporter:  dmsnell                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests gutenberg-  |     Focuses:  tests
  merge fixed-major dev-reviewed                 |
-------------------------------------------------+-------------------------

Comment (by dmsnell):

 thanks @jorbin — would there be another way I could create or prep a
 backport rather than creating a bunch of Trac tickets? I can see where
 some things would be very much clearer with a separate one, but already
 we’re talking about two PRs and a Trac ticket for each of these bugs, and
 they are all basically just things that appear in testing the
 collaborative editing.

 I’ll try and keep up with all the accounting; but if we can figure out a
 way that meets everyone’s needs without it, that would give that time back
 to finding and fixing the bugs before the release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65138#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 22:33:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 22:33:34 -0000
Subject: [wp-trac] [WordPress Trac] #65140: Toolbar: Icon color is
 inncorrect in mobile layout
In-Reply-To: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
References: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
Message-ID: <068.010b0b14424276ba23bb30fb0a88007b@wordpress.org>

#65140: Toolbar: Icon color is inncorrect in mobile layout
--------------------------+----------------------
 Reporter:  wildworks     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0
Component:  Toolbar       |     Version:  4.3
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, css
--------------------------+----------------------
Changes (by sabernhardt):

 * focuses:  ui => ui, css


Comment:

 #64762 should not need to delay this ticket now. If [62025] is reverted,
 it would not cause conflicts in the CSS file. (Or if the other ticket's
 patch is updated, the Sass should include additional changes.)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65140#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 23:05:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 23:05:50 -0000
Subject: [wp-trac] [WordPress Trac] #64983: Scale needs gettext
In-Reply-To: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
References: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
Message-ID: <067.1710022597f7d388a8fa2bbd67a0b5d5@wordpress.org>

#64983: Scale needs gettext
--------------------------+-----------------------
 Reporter:  timse201      |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  7.0
Component:  I18N          |     Version:  trunk
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------
Changes (by jorbin):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62312" 62312]:
 {{{
 #!CommitTicketReference repository="" revision="62312"
 I18N: Add translator context to scale strings in image editor

 Props shailu25, audrasjb, timse201, sanketparmar.
 Fixes #64983.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64983#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 23:07:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 23:07:24 -0000
Subject: [wp-trac] [WordPress Trac] #64983: Scale needs gettext
In-Reply-To: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
References: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
Message-ID: <067.48e88826698a4abe387da1b948db2646@wordpress.org>

#64983: Scale needs gettext
------------------------------------------------+-----------------------
 Reporter:  timse201                            |       Owner:  audrasjb
     Type:  defect (bug)                        |      Status:  reopened
 Priority:  normal                              |   Milestone:  7.0
Component:  I18N                                |     Version:  trunk
 Severity:  normal                              |  Resolution:
 Keywords:  has-patch fixed-major dev-feedback  |     Focuses:
------------------------------------------------+-----------------------
Changes (by jorbin):

 * keywords:  has-patch => has-patch fixed-major dev-feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening back backport consideration.

 Also noting that the GB related change has not been merged. I added that
 to the 7.0 project board.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64983#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 23:10:56 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 23:10:56 -0000
Subject: [wp-trac] [WordPress Trac] #59649: PHP 8.0: improvements to
 allow for named parameters in 7.0
In-Reply-To: <058.85960e921b358d30433c0c36ec591c46@wordpress.org>
References: <058.85960e921b358d30433c0c36ec591c46@wordpress.org>
Message-ID: <073.7b3329a130fcac47c71efee9ada1f520@wordpress.org>

#59649: PHP 8.0: improvements to allow for named parameters in 7.0
--------------------------------------------+------------------------------
 Reporter:  hellofromTonya                  |       Owner:  (none)
     Type:  task (blessed)                  |      Status:  new
 Priority:  normal                          |   Milestone:  7.1
Component:  General                         |     Version:
 Severity:  normal                          |  Resolution:
 Keywords:  php80 has-patch has-unit-tests  |     Focuses:  php-
                                            |  compatibility
--------------------------------------------+------------------------------
Changes (by jorbin):

 * milestone:  7.0 => 7.1


Comment:

 Bumping to 7.1 since there was no commit made during 7.0

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/59649#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 23:14:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 23:14:16 -0000
Subject: [wp-trac] [WordPress Trac] #64538: memoize wp_normalize_path
In-Reply-To: <055.d0a68ae7d0a278908d25712bd31f710d@wordpress.org>
References: <055.d0a68ae7d0a278908d25712bd31f710d@wordpress.org>
Message-ID: <070.30071b506be49d4a0f59592e6ab83ea0@wordpress.org>

#64538: memoize wp_normalize_path
--------------------------------------+--------------------------
 Reporter:  josephscott               |       Owner:  dmsnell
     Type:  defect (bug)              |      Status:  closed
 Priority:  normal                    |   Milestone:  7.0
Component:  General                   |     Version:  3.9
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------
Changes (by jorbin):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 Since there have been no further reports, I'm reclosing this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64538#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 23:17:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 23:17:06 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.1776a7b7a4c2266e3433f5eb4fba8f50@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------
Changes (by jorbin):

 * priority:  normal => high


Comment:

 Moving up in priority since as @wildworks notes "there are still many
 issues to address within this ticket"

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 23:20:45 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 23:20:45 -0000
Subject: [wp-trac] [WordPress Trac] #53010: Tests: introduce namespacing
 for the test classes
In-Reply-To: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
References: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
Message-ID: <062.08e46863bf5c6c2a9fdf14c298a35b0c@wordpress.org>

#53010: Tests: introduce namespacing for the test classes
--------------------------------------+------------------------------------
 Reporter:  jrf                       |       Owner:  SergeyBiryukov
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  docs, coding-
                                      |  standards
--------------------------------------+------------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"62313" 62313]:
 {{{
 #!CommitTicketReference repository="" revision="62313"
 Tests: Split the `admin/includesMisc.php` test file to match the new
 pattern.

 This aims to make the test suite directory and file structure more
 intuitive for new contributors to work with, as well as follow the PHPUnit
 recommended test class name pattern with having `Test` as the end of the
 class name.

 Follow-up to [434/tests], [57283].

 See #53010.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53010#comment:62>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May  6 23:20:58 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 06 May 2026 23:20:58 -0000
Subject: [wp-trac] [WordPress Trac] #65141: Fix alignment for sortable
 metabox on post and page edit screen with classic editor
In-Reply-To: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
References: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
Message-ID: <071.bff5b6c1a289f08a3c4a231435f596d7@wordpress.org>

#65141: Fix alignment for sortable metabox on post and page edit screen with
classic editor
-------------------------------------------------+-------------------------
 Reporter:  umesh.nevase                         |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Editor                               |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin changes-requested has-  |     Focuses:  ui, css
  patch                                          |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  has-patch admin-reskin => admin-reskin changes-requested has-
     patch


Comment:

 As noted, the patch needs an update. @umeshnevase - Are you able to handle
 that?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65141#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 00:01:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 00:01:11 -0000
Subject: [wp-trac] [WordPress Trac] #53010: Tests: introduce namespacing
 for the test classes
In-Reply-To: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
References: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
Message-ID: <062.1fd1138c280b794537a4df169eeb66e2@wordpress.org>

#53010: Tests: introduce namespacing for the test classes
--------------------------------------+------------------------------------
 Reporter:  jrf                       |       Owner:  SergeyBiryukov
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  docs, coding-
                                      |  standards
--------------------------------------+------------------------------------

Comment (by peterwilsoncc):

 In [changeset:"62314" 62314]:
 {{{
 #!CommitTicketReference repository="" revision="62314"
 Tests/Build Tools: Coding standards, typo fixes following r62313.

 Follow up to r62313.

 See #53010.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53010#comment:64>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 04:47:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 04:47:12 -0000
Subject: [wp-trac] [WordPress Trac] #64983: Scale needs gettext
In-Reply-To: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
References: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
Message-ID: <067.83441e9026d4726cfeb07d9ca1ef4862@wordpress.org>

#64983: Scale needs gettext
------------------------------------------------+-----------------------
 Reporter:  timse201                            |       Owner:  audrasjb
     Type:  defect (bug)                        |      Status:  reopened
 Priority:  normal                              |   Milestone:  7.0
Component:  I18N                                |     Version:  trunk
 Severity:  normal                              |  Resolution:
 Keywords:  has-patch fixed-major dev-reviewed  |     Focuses:
------------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch fixed-major dev-feedback => has-patch fixed-major
     dev-reviewed


Comment:

 Marking as reviewed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64983#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 04:48:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 04:48:25 -0000
Subject: [wp-trac] [WordPress Trac] #64983: Scale needs gettext
In-Reply-To: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
References: <052.e53f02387eb408cdbc6651e425f128e1@wordpress.org>
Message-ID: <067.5d5d59220bca1fe568e532027c75d78a@wordpress.org>

#64983: Scale needs gettext
------------------------------------------------+-----------------------
 Reporter:  timse201                            |       Owner:  audrasjb
     Type:  defect (bug)                        |      Status:  closed
 Priority:  normal                              |   Milestone:  7.0
Component:  I18N                                |     Version:  trunk
 Severity:  normal                              |  Resolution:  fixed
 Keywords:  has-patch fixed-major dev-reviewed  |     Focuses:
------------------------------------------------+-----------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62315" 62315]:
 {{{
 #!CommitTicketReference repository="" revision="62315"
 I18N: Add translator context to scale strings in image editor.

 Reviewed by jorbin, audrasjb.
 Merges [62312] to the 7.0 branch.
 Props shailu25, audrasjb, timse201, sanketparmar.
 Fixes #64983.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64983#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 04:55:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 04:55:16 -0000
Subject: [wp-trac] [WordPress Trac] #64980: Notes needs gettext
In-Reply-To: <052.bebd4bef753cdda60cb3e99a230ce2bc@wordpress.org>
References: <052.bebd4bef753cdda60cb3e99a230ce2bc@wordpress.org>
Message-ID: <067.0be38b2a11f1250737f4ff289db10bae@wordpress.org>

#64980: Notes needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch i18n-change dev-reviewed   |     Focuses:
  commit fixed-major                             |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62316" 62316]:
 {{{
 #!CommitTicketReference repository="" revision="62316"
 I18N: Provide gettext context to disambiguate translation strings for
 "Notes".

 "Notes" translation string is used in both the Notes features and in the
 Link Manager, and they can have different meaning in some Locales, like in
 German for example. This changeset helps disambuguating these different
 contexts.

 Reviewed by desrosj, audrasjb.
 Merges [62185] to the 7.0 branch.
 Props timse201, sanketparmar.
 Fixes #64980.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64980#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 05:54:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 05:54:00 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.0b6231cf47aede7477a25ff60865f827@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------
Changes (by mukesh27):

 * owner:  (none) => mukesh27
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 06:02:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 06:02:39 -0000
Subject: [wp-trac] [WordPress Trac] #65177: Adminbar: Unnatural focus
 outline in frontend
In-Reply-To: <053.761bf75e2bb92c14494464a5c083ae76@wordpress.org>
References: <053.761bf75e2bb92c14494464a5c083ae76@wordpress.org>
Message-ID: <068.77ba4b1e3e3d85b7929de19ecc92e1c7@wordpress.org>

#65177: Adminbar: Unnatural focus outline in frontend
----------------------------+---------------------
 Reporter:  wildworks       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  7.1
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------
Changes (by wildworks):

 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65177#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 06:12:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 06:12:08 -0000
Subject: [wp-trac] [WordPress Trac] #65140: Toolbar: Icon color is
 inncorrect in mobile layout
In-Reply-To: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
References: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
Message-ID: <068.3199346f878b5b8dc7bb55a32ea22666@wordpress.org>

#65140: Toolbar: Icon color is inncorrect in mobile layout
--------------------------+----------------------
 Reporter:  wildworks     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0
Component:  Toolbar       |     Version:  4.3
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, css
--------------------------+----------------------

Comment (by wildworks):

 We are only two days away from the new beta 1, so let's resolve this
 ticket first.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65140#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 07:01:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 07:01:59 -0000
Subject: [wp-trac] [WordPress Trac] #65140: Toolbar: Icon color is
 inncorrect in mobile layout
In-Reply-To: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
References: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
Message-ID: <068.53cd97b736e9a7f88781a358ab943213@wordpress.org>

#65140: Toolbar: Icon color is inncorrect in mobile layout
--------------------------+------------------------
 Reporter:  wildworks     |       Owner:  wildworks
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  7.0
Component:  Toolbar       |     Version:  4.3
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |     Focuses:  ui, css
--------------------------+------------------------
Changes (by wildworks):

 * owner:  (none) => wildworks
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62317" 62317]:
 {{{
 #!CommitTicketReference repository="" revision="62317"
 Toolbar: Fix icon colors in mobile layout.

 Swap the default and hover color rules for admin bar icons on mobile so
 icons use `$menu-icon` by default and `$menu-submenu-focus-text` on hover.

 Props sabernhardt, peterwilsoncc, wildworks.
 Fixes #65140.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65140#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 07:02:45 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 07:02:45 -0000
Subject: [wp-trac] [WordPress Trac] #65140: Toolbar: Icon color is
 inncorrect in mobile layout
In-Reply-To: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
References: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
Message-ID: <068.923eb197c3713709eed32ac72eef4423@wordpress.org>

#65140: Toolbar: Icon color is inncorrect in mobile layout
------------------------------------+------------------------
 Reporter:  wildworks               |       Owner:  wildworks
     Type:  defect (bug)            |      Status:  reopened
 Priority:  normal                  |   Milestone:  7.0
Component:  Toolbar                 |     Version:  4.3
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:  ui, css
------------------------------------+------------------------
Changes (by wildworks):

 * keywords:  has-patch => has-patch dev-feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening #65140 to request backporting [62317] to the 7.0 branch

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65140#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 07:21:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 07:21:07 -0000
Subject: [wp-trac] [WordPress Trac] #65140: Toolbar: Icon color is
 inncorrect in mobile layout
In-Reply-To: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
References: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
Message-ID: <068.abce1ff27e1a0419444069e49f1f5798@wordpress.org>

#65140: Toolbar: Icon color is inncorrect in mobile layout
------------------------------------------------+------------------------
 Reporter:  wildworks                           |       Owner:  wildworks
     Type:  defect (bug)                        |      Status:  reopened
 Priority:  normal                              |   Milestone:  7.0
Component:  Toolbar                             |     Version:  4.3
 Severity:  normal                              |  Resolution:
 Keywords:  has-patch dev-reviewed fixed-major  |     Focuses:  ui, css
------------------------------------------------+------------------------
Changes (by audrasjb):

 * keywords:  has-patch dev-feedback => has-patch dev-reviewed fixed-major


Comment:

 Adding second committer sign-off.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65140#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 07:37:43 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 07:37:43 -0000
Subject: [wp-trac] [WordPress Trac] #65140: Toolbar: Icon color is
 inncorrect in mobile layout
In-Reply-To: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
References: <053.6248a4acdfd28154e0622c885840600c@wordpress.org>
Message-ID: <068.419acd6d1d93fc327cb48a5b95571a45@wordpress.org>

#65140: Toolbar: Icon color is inncorrect in mobile layout
------------------------------------------------+------------------------
 Reporter:  wildworks                           |       Owner:  wildworks
     Type:  defect (bug)                        |      Status:  closed
 Priority:  normal                              |   Milestone:  7.0
Component:  Toolbar                             |     Version:  4.3
 Severity:  normal                              |  Resolution:  fixed
 Keywords:  has-patch dev-reviewed fixed-major  |     Focuses:  ui, css
------------------------------------------------+------------------------
Changes (by wildworks):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62318" 62318]:
 {{{
 #!CommitTicketReference repository="" revision="62318"
 Toolbar: Fix icon colors in mobile layout.

 Swap the default and hover color rules for admin bar icons on mobile so
 icons use `$menu-icon` by default and `$menu-submenu-focus-text` on hover.

 Reviewed by audrasjb.
 Merges [62317] to the 7.0 branch.

 Props sabernhardt, peterwilsoncc, wildworks.
 Fixes #65140.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65140#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 08:08:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 08:08:24 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.f517d7191b1cade02740a74e1556dffb@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------

Comment (by wildworks):

 The priority for correction should be the unintended reduction in the
 height of interactive elements to less than 40px in the mobile layout due
 to the application of the new design system.


 I don't think elements that weren't previously 40px need to be
 standardized to 40px right away.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 09:02:40 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 09:02:40 -0000
Subject: [wp-trac] [WordPress Trac] #65180: Tests: Add unit tests for
 wp_reset_vars()
In-Reply-To: <051.4cf0339cdd8e9bce630bf5914d78c61a@wordpress.org>
References: <051.4cf0339cdd8e9bce630bf5914d78c61a@wordpress.org>
Message-ID: <066.9491ace3e9cc5cc0afccdd8ffde4bc40@wordpress.org>

#65180: Tests: Add unit tests for wp_reset_vars()
--------------------------------------+------------------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  feature request           |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------------

Comment (by darshitrajyaguru97):

 Tested the patch locally and confirmed the new `wp_reset_vars()` tests are
 passing successfully.

 Environment:

 * WordPress: trunk
 * PHP: 8.2.29
 * Database: MySQL
 * PHPUnit: latest Core test suite

 The added coverage looks solid overall, especially around documenting the
 current `empty()` behavior for values like `'0'` and `''`.

 A few additional edge cases may be worth considering, either in this patch
 or a potential follow-up:

 * `false`
 * `0` (integer)
 * `null`
 * array values

 Additionally, in `tear_down()`, previously unset globals could potentially
 be restored using `unset()` instead of assigning `null`, which may help
 preserve the original global state more accurately.

 Patch tests successfully.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65180#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 09:21:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 09:21:04 -0000
Subject: [wp-trac] [WordPress Trac] #65188: Uploading PNG images with a
 larger number of colors causes timeouts and eventually CPU starvation
Message-ID: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>

#65188: Uploading PNG images with a larger number of colors causes timeouts and
eventually CPU starvation
---------------------------+-----------------------------
 Reporter:  romainmrhenry  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Upload         |    Version:  6.8
 Severity:  normal         |   Keywords:
  Focuses:  performance    |
---------------------------+-----------------------------
 Since WordPress 6.8 there is new handling of PNG images.

 Specifically in `thumbnail_image` at `wp-includes/class-wp-image-editor-
 imagick.php:403`

 Uploading a png image with a large number of colors, for example a
 photographic image in .png format, causes the `getImageColors()` step at
 line 506 to be extremely slow.

 This seems to be the result of the chosen filter `FILTER_TRIANGLE`.


 A standalone version of this function with some extra log lines:

 {{{#!php
 <?php

 $image = new \Imagick( realpath( './foo.png' ) );

 thumbnail_image( $image, 2048, 2048 );

 function thumbnail_image( $image, $dst_w, $dst_h, $filter_name =
 'FILTER_TRIANGLE' ) {
         error_log( 'a' );
         $current_colors = $image->getImageColors();
         error_log( 'b' );
         error_log( $current_colors );

         $allowed_filters = array(
                 'FILTER_POINT',
                 'FILTER_BOX',
                 'FILTER_TRIANGLE',
                 'FILTER_HERMITE',
                 'FILTER_HANNING',
                 'FILTER_HAMMING',
                 'FILTER_BLACKMAN',
                 'FILTER_GAUSSIAN',
                 'FILTER_QUADRATIC',
                 'FILTER_CUBIC',
                 'FILTER_CATROM',
                 'FILTER_MITCHELL',
                 'FILTER_LANCZOS',
                 'FILTER_BESSEL',
                 'FILTER_SINC',
         );

         /**
          * Set the filter value if '$filter_name' name is in the allowed
 list and the related
          * Imagick constant is defined or fall back to the default filter.
          */
         if ( in_array( $filter_name, $allowed_filters, true ) && defined(
 'Imagick::' . $filter_name ) ) {
                 $filter = constant( 'Imagick::' . $filter_name );
         } else {
                 $filter = defined( 'Imagick::FILTER_TRIANGLE' ) ?
 Imagick::FILTER_TRIANGLE : false;
         }

         try {
                 $size = null;
                 try {
                         error_log( '1' );
                         $size = $image->getImageGeometry();
                         error_log( '2' );
                 } catch ( Exception $e ) {
                         return new WP_Error( 'invalid_image', __( 'Could
 not read image size.' ) );
                 }

                 /*
                         * To be more efficient, resample large images to
 5x the destination size before resizing
                         * whenever the output size is less that 1/3 of the
 original image size (1/3^2 ~= .111),
                         * unless we would be resampling to a scale smaller
 than 128x128.
                         */
                 if ( is_callable( array( $image, 'sampleImage' ) ) ) {
                         $resize_ratio  = ( $dst_w / $size['width'] ) * (
 $dst_h / $size['height'] );
                         $sample_factor = 5;

                         if ( $resize_ratio < .111 && ( $dst_w *
 $sample_factor > 128 && $dst_h * $sample_factor > 128 ) ) {
                                 error_log( '3' );
                                 $image->sampleImage( $dst_w *
 $sample_factor, $dst_h * $sample_factor );
                                 error_log( '4' );
                         }
                 }

                 /*
                         * Use resizeImage() when it's available and a
 valid filter value is set.
                         * Otherwise, fall back to the scaleImage() method
 for resizing, which
                         * results in better image quality over
 resizeImage() with default filter
                         * settings and retains backward compatibility with
 pre 4.5 functionality.
                         */
                 if ( is_callable( array( $image, 'resizeImage' ) ) &&
 $filter ) {
                         error_log( '5' );
                         $image->setOption( 'filter:support', '2.0' );
                         $image->resizeImage( $dst_w, $dst_h, $filter, 1 );
                         error_log( '6' );
                 } else {
                         error_log( '7' );
                         $image->scaleImage( $dst_w, $dst_h );
                         error_log( '8' );
                 }

                 error_log( '9' );
                 $image->setOption( 'png:compression-filter', '5' );
                 $image->setOption( 'png:compression-level', '9' );
                 $image->setOption( 'png:compression-strategy', '1' );
                 error_log( '10' );
                 // Check to see if a PNG is indexed, and find the pixel
 depth.
                 if ( is_callable( array( $image, 'getImageDepth' ) ) ) {
                         error_log( '11' );
                         $indexed_pixel_depth = $image->getImageDepth();
                         error_log( $indexed_pixel_depth );
                         error_log( '12' );

                         // Indexed PNG files get some additional handling.
                         if ( 0 < $indexed_pixel_depth && 8 >=
 $indexed_pixel_depth ) {
                                 // Check for an alpha channel.
                                 error_log( '13' );
                                 if (
                                         is_callable( array( $image,
 'getImageAlphaChannel' ) )
                                         && $image->getImageAlphaChannel()
                                 ) {
                                         $image->setOption( 'png:include-
 chunk', 'tRNS' );
                                 } else {
                                         $image->setOption( 'png:exclude-
 chunk', 'all' );
                                 }
                                 error_log( '14' );

                                 // Reduce colors in the images to maximum
 needed, using the global colorspace.
                                 $max_colors = pow( 2, $indexed_pixel_depth
 );
                                 error_log( $max_colors );
                                 if ( is_callable( array( $image,
 'getImageColors' ) ) ) {
                                         $current_colors =
 $image->getImageColors();
                                         error_log( $current_colors );
                                         $max_colors = min( $max_colors,
 $current_colors );
                                 }
                                 error_log( $max_colors );

                                 error_log( '15' );
                                 $image->quantizeImage( $max_colors,
 $image->getColorspace(), 0, false, false );
                                 error_log( '16' );

                                 error_log( 'c' );
                                 $current_colors =
 $image->getImageColors();
                                 error_log( 'd' );
                                 error_log( $current_colors );

                                 /**
                                  * If the colorspace is 'gray', use the
 png8 format to ensure it stays indexed.
                                  */
                                 if ( Imagick::COLORSPACE_GRAY ===
 $image->getImageColorspace() ) {
                                         $image->setOption( 'png:format',
 'png8' );
                                 }
                         }
                 }

                 /*
                         * If alpha channel is not defined, set it opaque.
                         *
                         * Note that Imagick::getImageAlphaChannel() is
 only available if Imagick
                         * has been compiled against ImageMagick version
 6.4.0 or newer.
                         */
                 if ( is_callable( array( $image, 'getImageAlphaChannel' )
 )
                         && is_callable( array( $image,
 'setImageAlphaChannel' ) )
                         && defined( 'Imagick::ALPHACHANNEL_UNDEFINED' )
                         && defined( 'Imagick::ALPHACHANNEL_OPAQUE' )
                 ) {
                         if ( $image->getImageAlphaChannel() ===
 Imagick::ALPHACHANNEL_UNDEFINED ) {
                                 $image->setImageAlphaChannel(
 Imagick::ALPHACHANNEL_OPAQUE );
                         }
                 }

                 // Limit the bit depth of resized images.
                 if ( is_callable( array( $image, 'getImageDepth' ) ) &&
 is_callable( array( $image, 'setImageDepth' ) ) ) {
                         /**
                          * Filters the maximum bit depth of resized
 images.
                          *
                          * This filter only applies when resizing using
 the Imagick editor since GD
                          * does not support getting or setting bit depth.
                          *
                          * Use this to adjust the maximum bit depth of
 resized images.
                          *
                          * @since 6.8.0
                          *
                          * @param int $max_depth   The maximum bit depth.
 Default is the input depth.
                          * @param int $image_depth The bit depth of the
 original image.
                          */
                         $max_depth = $image->getImageDepth();
                         $image->setImageDepth( $max_depth );
                 }
         } catch ( Exception $e ) {
                 return new WP_Error( 'image_resize_error',
 $e->getMessage() );
         }
 }
 }}}


 -------

 It also seems that there is some confusion around channel depth and colors
 in this function.
 The `$max_colors` is a value per channel while `$current_colors` is for
 all channels combined.

 I think `$max_colors` should be multiplied by 3.


 -----

 It is extremely easy to DOS a WordPress server that allows file uploads by
 feeding it photographic PNG images.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65188>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 09:34:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 09:34:44 -0000
Subject: [wp-trac] [WordPress Trac] #65188: Uploading PNG images with a
 larger number of colors causes timeouts and eventually CPU starvation
In-Reply-To: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
References: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
Message-ID: <072.0d56fe14cb112a66fb547d8a0cdc799f@wordpress.org>

#65188: Uploading PNG images with a larger number of colors causes timeouts and
eventually CPU starvation
---------------------------+------------------------------
 Reporter:  romainmrhenry  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Upload         |     Version:  6.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  performance
---------------------------+------------------------------

Comment (by blackstar1991):

 Could you please provide a sample image to demonstrate the issue? You can
 test this on a blank WordPress site without any other plugins. *If you're
 using an uncompressed image larger than 1 Mb, this is expected behavior.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65188#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 09:43:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 09:43:19 -0000
Subject: [wp-trac] [WordPress Trac] #65188: Uploading PNG images with a
 larger number of colors causes timeouts and eventually CPU starvation
In-Reply-To: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
References: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
Message-ID: <072.732ff385a7a56cd2ac00e19b68e99d9c@wordpress.org>

#65188: Uploading PNG images with a larger number of colors causes timeouts and
eventually CPU starvation
---------------------------+------------------------------
 Reporter:  romainmrhenry  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Upload         |     Version:  6.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  performance
---------------------------+------------------------------

Comment (by romainmrhenry):

 `2048x2048` is one of the sizes used by WordPress.

 > If you're using an uncompressed image larger than 1 Mb, this is expected
 behavior.

 What do you mean?
 Do you mean that it is expected that any upload larger than 1 Mb gives a
 timeout?
 That seems wild to me.

 ----

 Sample image:

 https://storage.googleapis.com/shared-files-mrhenry/romain/witty-
 hammerhead-shark-30e776b1bf.png

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65188#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 09:46:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 09:46:51 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.ae8b0e093fe5ee355e2e5e57673c2ea3@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------

Comment (by abcd95):

 I was taking a look at addressing some of the remaining issues for this
 ticket, specifically investigating `.customize-control .date-time-fields
 select`, which is hardcoded to `height: 39px` in the mobile. Upon
 inspecting the computed styles, the element actually resolves to a total
 height of 40px, and this happens because the global min-height of 40px is
 applied to select from the core forms. Everything else appears to either
 be intentional or correctly saved by the global min-height.

 could you point out which specific pages or components you have noticed
 are still experiencing the unintended height reduction to less than 40px?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 10:00:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 10:00:50 -0000
Subject: [wp-trac] [WordPress Trac] #65188: Uploading PNG images with a
 larger number of colors causes timeouts and eventually CPU starvation
In-Reply-To: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
References: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
Message-ID: <072.b890082e9f51f52dca4257bec59eda8c@wordpress.org>

#65188: Uploading PNG images with a larger number of colors causes timeouts and
eventually CPU starvation
---------------------------+------------------------------
 Reporter:  romainmrhenry  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Upload         |     Version:  6.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  performance
---------------------------+------------------------------

Comment (by blackstar1991):

 It looks like your pages are using very large image files. Unless your
 website is specifically a high-definition photo gallery or an art
 exhibition, images of this scale are generally unnecessary and can
 significantly slow down your site.

 Since most screens won’t even display those extra pixels, your users don't
 get the benefit of the large file size, but they do suffer the slower
 loading times. If you run a Google PageSpeed Insights test, you’ll likely
 see recommendations to "serve images in next-gen formats" or "properly
 size images."

 My Recommendation:
 I suggest compressing your images before uploading them to the site. A
 great free tool for this is [Squoosh.app | https://squoosh.app/], which
 allows you to reduce file size without losing noticeable quality.

 Note: This isn't a technical bug within the system; it’s a matter of
 optimizing your assets to ensure the best possible user experience.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65188#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 10:09:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 10:09:15 -0000
Subject: [wp-trac] [WordPress Trac] #65188: Uploading PNG images with a
 larger number of colors causes timeouts and eventually CPU starvation
In-Reply-To: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
References: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
Message-ID: <072.480b7a5631325a22ffb39d7fc788304a@wordpress.org>

#65188: Uploading PNG images with a larger number of colors causes timeouts and
eventually CPU starvation
---------------------------+------------------------------
 Reporter:  romainmrhenry  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Upload         |     Version:  6.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  performance
---------------------------+------------------------------

Comment (by romainmrhenry):

 I am sorry but your response is completely detached from the report.

 2048x2048 is one of the default sizes generated by WordPress.
 It is independent of themes or plugins.

 The linked source image is 1600x2000 which is smaller than this default
 size generated by WordPress.
 If such sizes are so problematic (they really aren't) then why is this a
 default in WordPress?

 This definitely is a technical bug.
 Please don't blame the user and actually investigate the issue.

 We also know many ways to circumvent the issue that doesn't take away that
 there is a problem in WordPress core.
 The existence of a workaround doesn't magically makes bugs go away.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65188#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 10:24:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 10:24:18 -0000
Subject: [wp-trac] [WordPress Trac] #65188: Uploading PNG images with a
 larger number of colors causes timeouts and eventually CPU starvation
In-Reply-To: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
References: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
Message-ID: <072.03e9d47919b4084a66f36551cc9a0c7d@wordpress.org>

#65188: Uploading PNG images with a larger number of colors causes timeouts and
eventually CPU starvation
---------------------------+------------------------------
 Reporter:  romainmrhenry  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Upload         |     Version:  6.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  performance
---------------------------+------------------------------

Comment (by siliconforks):

 Replying to [ticket:65188 romainmrhenry]:
 > Uploading a png image with a large number of colors, for example a
 photographic image in .png format, causes the `getImageColors()` step at
 line 506 to be extremely slow.

 You're using version 6.8?  This is a known issue in 6.8.  See
 https://core.trac.wordpress.org/ticket/63481#comment:5

 Can you update to version 6.9?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65188#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 10:26:45 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 10:26:45 -0000
Subject: [wp-trac] [WordPress Trac] #65188: Uploading PNG images with a
 larger number of colors causes timeouts and eventually CPU starvation
In-Reply-To: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
References: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
Message-ID: <072.7bdaed81141cfd5344e2c61759d65b37@wordpress.org>

#65188: Uploading PNG images with a larger number of colors causes timeouts and
eventually CPU starvation
---------------------------+------------------------------
 Reporter:  romainmrhenry  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Upload         |     Version:  6.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  performance
---------------------------+------------------------------

Comment (by romainmrhenry):

 Thank you @siliconforks, we indeed intend to update to 6.9 in the coming
 months.

 Could this be backported to 6.8?

 Happy to already know that eventually this issue will be resolved for us
 when we update.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65188#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 10:39:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 10:39:22 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.e042908873ab3812dd1d84da4ec32c3b@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------

Comment (by wildworks):

 > could you point out which specific pages or components you have noticed
 are still experiencing the unintended height reduction to less than 40px?


 I used AI to identify interactive elements that were unintentionally made
 smaller than 40px.

 - Appearance > Themes: Search field
 - Plugins > Add Plugin: Search field, Keyword dropdown, Pager input field,
 Install button
 - Media Library > Grid: Filter dropdown, Bulk select button, Search field
 - General Settings > Date format input field, Time format input field

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 10:39:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 10:39:49 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.366342be345f466f44b2ae51521f4b76@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------
Changes (by wildworks):

 * Attachment "button-size-comparison.png" added.

 buttom-size-comparison

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 10:42:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 10:42:59 -0000
Subject: [wp-trac] [WordPress Trac] #65188: Uploading PNG images with a
 larger number of colors causes timeouts and eventually CPU starvation
In-Reply-To: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
References: <057.0459ba4ab358c63b866d22a2f0838c56@wordpress.org>
Message-ID: <072.83e40eaf3ab96d552f106560fc8f0874@wordpress.org>

#65188: Uploading PNG images with a larger number of colors causes timeouts and
eventually CPU starvation
---------------------------+------------------------------
 Reporter:  romainmrhenry  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Upload         |     Version:  6.8
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  performance
---------------------------+------------------------------

Comment (by siliconforks):

 Replying to [comment:6 romainmrhenry]:
 > Could this be backported to 6.8?

 I doubt that would ever be backported - older versions of WordPress (like
 6.8) are not really supported any more, they only receive updates for
 critical bug fixes.

 If you really want that fixed in 6.8, you could probably just replace the
 file `class-wp-image-editor-imagick.php` with the new version from 6.9:

 https://raw.githubusercontent.com/WordPress/wordpress-
 develop/refs/tags/6.9.4/src/wp-includes/class-wp-image-editor-imagick.php

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65188#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 11:11:56 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 11:11:56 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.5c11dca6e9a4461fb1d8579e6ed78dd9@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------

Comment (by wildworks):

 I propose that we address all issues with the following two PRs:

 - [https://github.com/WordPress/wordpress-develop/pull/11461 PR 11461]:
 This focuses on fixing the list table page.
 - Submit a new PR to fix all other issues.

 After these two are addressed, we can backport these two commits to 7.0 in
 a single commit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 11:16:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 11:16:30 -0000
Subject: [wp-trac] [WordPress Trac] #65012: Fix: Register Akismet
 Anti-Spam as a connector
In-Reply-To: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
References: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
Message-ID: <075.f671815ebd5c41343c0e23e5a655eba4@wordpress.org>

#65012: Fix: Register Akismet Anti-Spam as a connector
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  feature request                      |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests commit      |     Focuses:
  dev-reviewed                                   |
-------------------------------------------------+-------------------------
Changes (by gziolo):

 * keywords:  has-patch has-unit-tests commit => has-patch has-unit-tests
     commit dev-reviewed


Comment:

 [62310] Looks good to me for inclusion in WP 7.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65012#comment:60>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 11:19:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 11:19:46 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.bd8d7c57e6c681756a3d0b5dfec94697@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
---------------------------+-------------------------
 Reporter:  jonsurrell     |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  high           |   Milestone:  7.0
Component:  Script Loader  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+-------------------------

Comment (by jonsurrell):

 Replying to [comment:4 jorbin]:
 > How much effort would be needed to update [61611] if the feature is
 reverted? If it's low/medium effort, then option A seems like the best
 option.

 I espree could be bundled into the
 [https://core.trac.wordpress.org/browser/trunk/src/js/_enqueues/lib/codemirror
 /javascript-lint.js javascript-lint.js] instead of using a dynamic import.
 @westonruter I'd love your thought on this.

 That should resolve any downsides and seems straightforward.

 This ties in with some thoughts I have about private modules. I'd like to
 be careful and judicious about what modules Core exposes and espree may
 not make a lot of sense as a Core module.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 11:51:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 11:51:54 -0000
Subject: [wp-trac] [WordPress Trac] #65012: Fix: Register Akismet
 Anti-Spam as a connector
In-Reply-To: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
References: <060.46689c302968272609f7f5709dd06b43@wordpress.org>
Message-ID: <075.d6ca5d7de9bb2d9f9b7b50bacc74b8cc@wordpress.org>

#65012: Fix: Register Akismet Anti-Spam as a connector
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:
                                                 |  jorgefilipecosta
     Type:  feature request                      |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit      |     Focuses:
  dev-reviewed                                   |
-------------------------------------------------+-------------------------
Changes (by jorgefilipecosta):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62319" 62319]:
 {{{
 #!CommitTicketReference repository="" revision="62319"
 Connectors: Register Akismet Anti-Spam as a connector.

 Akismet is bundled with WordPress core, but it wasn't appearing on the
 Connectors screen even when present on the file system.

 Partially reverts [62210], bringing back the main part of [62193].
 Follow-up to [62210], [62193].
 Developed in https://github.com/WordPress/wordpress-develop/pull/11688.

 Reviewed by gziolo.
 Merges [62310] to the 7.0 branch.

 Props audrasjb, bluefuton, davidbaumwald, desrosj, eclev91, gziolo,
 johnbillion, jorbin, jorgefilipecosta, lukecarbis, matt, matveb,
 peterwilsoncc, westonruter.
 Fixes #65012.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65012#comment:61>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 12:22:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 12:22:39 -0000
Subject: [wp-trac] [WordPress Trac] #64904: Real time collboration:
 determine approach for opt in setting for users in Settings > Writing
In-Reply-To: <052.0bbda23d420073a23acb5985c10fd47e@wordpress.org>
References: <052.0bbda23d420073a23acb5985c10fd47e@wordpress.org>
Message-ID: <067.9e90f1e5c74c1de682cb248d363634da@wordpress.org>

#64904: Real time collboration: determine approach for opt in setting for users in
Settings > Writing
----------------------------+--------------------------------
 Reporter:  annezazu        |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  7.0
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  ui, accessibility
----------------------------+--------------------------------

Comment (by fcoveram):

 > These "new" badges are something that doesn't exist yet so it is going
 to need to take into account every color scheme.

 To make sure it supports all color schemes and meet the a11y requirements.
 We could use the text color as a background and white text over it.
 Similarly to the translation icon in Site Language field in Settings >
 General.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64904#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 12:28:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 12:28:34 -0000
Subject: [wp-trac] [WordPress Trac] #65189: create pattern issue
Message-ID: <059.eefb39b025f2070137510d45ec552592@wordpress.org>

#65189: create pattern issue
------------------------------+-----------------------------
 Reporter:  sonaliprajapati   |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  General           |    Version:
 Severity:  normal            |   Keywords:
  Focuses:  coding-standards  |
------------------------------+-----------------------------
 When I try to create a pattern, it doesn’t get created successfully.
 Instead, it throws an error.

 https://prnt.sc/WamFt98ubM_7

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65189>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 12:46:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 12:46:54 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.26e18f2abb1b79241b055e744b2ab7fc@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by fcoveram):

 I updated a few words in the main document as these changes happened in
 the design file. The document is the same as the linked above by @mukesh27
 (https://docs.google.com/document/d/1LLziX7fdw9iftLOtbpkZ2TN8FfOS3sDVX4nIuJCwBV4/edit?tab=t.ok56kf4oaexa#heading=h.66j85f6jwwxu)

 The design file has the assets for this page marked as "ready for dev".
 Here a link to the assets page:
 https://www.figma.com/design/aeMDWlqrwWarqDQaTwB0Nh/7.0-Highlight-Grid--
 Microsite--About-Page?node-id=6006-5640

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 13:31:57 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 13:31:57 -0000
Subject: [wp-trac] [WordPress Trac] #23562: Using Speech Recognition
 Software with the Add Media Panel
In-Reply-To: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
References: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
Message-ID: <073.62af6e4431f163bdc9244916f792242a@wordpress.org>

#23562: Using Speech Recognition Software with the Add Media Panel
--------------------------------------------+----------------------------
 Reporter:  grahamarmfield                  |       Owner:  joedolson
     Type:  defect (bug)                    |      Status:  closed
 Priority:  normal                          |   Milestone:  7.0
Component:  Media                           |     Version:  3.5.1
 Severity:  normal                          |  Resolution:  fixed
 Keywords:  has-patch has-test-info commit  |     Focuses:  accessibility
--------------------------------------------+----------------------------

Comment (by arielmaidana):

 Feedback received that the new visible Media Library grid labels can make
 the thumbnail view feel cluttered, especially for users who preferred the
 previous image-only grid view. A built-in option to hide the labels or
 reduce their visual prominence, while preserving accessibility for voice-
 control users, would be helpful.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/23562#comment:63>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 13:51:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 13:51:53 -0000
Subject: [wp-trac] [WordPress Trac] #37376: Make it possible for custom
 post type to have an archive but no single
In-Reply-To: <059.7c4dac95c5995a4ce30b729d7ac186b3@wordpress.org>
References: <059.7c4dac95c5995a4ce30b729d7ac186b3@wordpress.org>
Message-ID: <074.cb3f7f48ec4ca9c62777fd3dffc99ff2@wordpress.org>

#37376: Make it possible for custom post type to have an archive but no single
----------------------------------------+------------------------------
 Reporter:  jason_the_adams             |       Owner:  (none)
     Type:  feature request             |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Posts, Post Types           |     Version:  4.6
 Severity:  normal                      |  Resolution:
 Keywords:  needs-unit-tests has-patch  |     Focuses:
----------------------------------------+------------------------------
Changes (by bacoords):

 * Attachment "37376.2.patch" added.

 Updated patch based on the latest trunk changes

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37376>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 13:55:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 13:55:00 -0000
Subject: [wp-trac] [WordPress Trac] #37376: Make it possible for custom
 post type to have an archive but no single
In-Reply-To: <059.7c4dac95c5995a4ce30b729d7ac186b3@wordpress.org>
References: <059.7c4dac95c5995a4ce30b729d7ac186b3@wordpress.org>
Message-ID: <074.afb04c42812f455b4de6417ec23ba69b@wordpress.org>

#37376: Make it possible for custom post type to have an archive but no single
----------------------------------------+------------------------------
 Reporter:  jason_the_adams             |       Owner:  (none)
     Type:  feature request             |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Posts, Post Types           |     Version:  4.6
 Severity:  normal                      |  Resolution:
 Keywords:  needs-unit-tests has-patch  |     Focuses:
----------------------------------------+------------------------------

Comment (by bacoords):

 I've been working on refreshing this patch and wanted to document some
 findings about the broader implications.

 === Core Approach ===

 The patch adds a `has_single` property (boolean, default `true`) to
 `register_post_type()`. When `false`:
 * No rewrite rules are generated for single post views
 * `get_permalink()` / `get_post_permalink()` return `false`
 * `wp_get_shortlink()` returns empty string

 === The `is_post_type_viewable()` Problem ===

 A key decision: '''`is_post_type_viewable()` intentionally does NOT check
 `has_single`'''.

 This function is used for two distinct purposes:
 1. "Can users view this post type on the front-end?" (REST API, Query
 Loop, archives)
 2. "Does this post type have single post views?" (View links, sitemaps,
 permalinks)

 If we made `is_post_type_viewable()` return `false` for `has_single =>
 false` post types, it would break:
 * REST API public access
 * Query Loop blocks
 * Archive pages
 * Any code checking general "publicness"

 Instead, places that specifically care about single views must check
 '''both''' `is_post_type_viewable()` AND `has_single`:

 {{{
 if ( is_post_type_viewable( $post_type ) && $post_type->has_single ) {
     // Show view link, add to sitemap, etc.
 }
 }}}

 === The Permalink Assumption ===

 WordPress core assumes `get_permalink()` always returns a URL string. This
 patch changes that - it can now return `false`. Places generating links
 must check:

 {{{
 $permalink = get_permalink( $post );
 if ( $permalink ) {
     echo '<a href="' . esc_url( $permalink ) . '">View</a>';
 }
 }}}

 === Files Changed in This Patch ===

 '''Post type registration:'''
 * `class-wp-post-type.php` - Adds property, skips single rewrite rules

 '''Permalink functions:'''
 * `link-template.php` - `get_post_permalink()`, `wp_get_shortlink()`,
 `get_preview_post_link()` return false/empty

 '''Admin UI:'''
 * `edit-form-advanced.php` - Hides preview/view links in editor
 * `meta-boxes.php` - Hides Preview button
 * `class-wp-posts-list-table.php` - Hides View/Preview row actions

 '''REST API:'''
 * `class-wp-rest-posts-controller.php` - No alternate link header, no
 `permalink_template`/`generated_slug` fields

 '''Sitemaps:'''
 * `class-wp-sitemaps-posts.php` - Excludes post types with `has_single =>
 false`

 === Gutenberg PR Required ===

 Many core blocks also assume permalinks exist for all post types. These
 blocks need updates in the Gutenberg repo:
 * `post-title` - Link option
 * `post-excerpt` - "Read more" link
 * `post-featured-image` - Link option
 * `post-date` - Link option
 * `read-more` - Entire block purpose is linking
 * `latest-posts` - Post title links
 * `breadcrumbs` - Ancestor links

 The fix is straightforward - check if `get_the_permalink()` returns a
 value before wrapping in `<a>`. I'll open a companion PR in Gutenberg.

 === Testing ===

 Register a test post type:

 {{{
 register_post_type( 'no_single', array(
     'label'       => 'No Single',
     'public'      => true,
     'has_archive' => true,
     'has_single'  => false,
     'show_in_rest' => true,
 ) );
 }}}

 Verify:
 * Archive page works
 * REST API returns posts
 * Query Loop displays posts
 * No "View" links in admin
 * Not in sitemaps
 * Single URLs 404 (no rewrite rules)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37376#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 14:19:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 14:19:52 -0000
Subject: [wp-trac] [WordPress Trac] #65189: create pattern issue
In-Reply-To: <059.eefb39b025f2070137510d45ec552592@wordpress.org>
References: <059.eefb39b025f2070137510d45ec552592@wordpress.org>
Message-ID: <074.53dbb2c6bf7dab897c7ddbe2dacce1ae@wordpress.org>

#65189: create pattern issue
-----------------------------+-------------------------------
 Reporter:  sonaliprajapati  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  coding-standards
-----------------------------+-------------------------------

Comment (by darshitrajyaguru97):

 I tested this issue further directly on the WordPress.org Pattern Creator
 and was able to consistently reproduce it.

 == Testing Performed ==

 * Opened the WordPress.org Pattern Creator
 * Created a new pattern with all required information
 * Submitted the pattern normally

 == Observed Behavior ==

 * After submission, a “Thank you for submit” message appears briefly
 * A few seconds later, the editor shows an error state, and the pattern is
 not created successfully
 "There is an issue with your pattern.
 Updating failed. Sorry, you are not allowed to edit the
 jetpack_post_was_ever_published custom field."

 == Console / Network Findings ==

 On further inspection in the browser console and network tab, several REST
 /API-related issues appeared during the submission process.

 Most relevant finding:

 {{{
 POST https://wordpress.org/patterns/wp-json/wp/v2/users/me?_locale=user
 404 (Not Found)
 }}}

 Additionally:

 {{{
 wp-json/wp/v2/media?... 403 (Forbidden)
 wp-json/wp/v2/wporg-pattern/{id}?_locale=user 403 (Forbidden)
 }}}

 There are also multiple async/runtime listener errors and failed resource
 requests occurring after submission.

 == Notes ==

 * Issue tested directly on WordPress.org Pattern Creator (not local
 environment)
 * Reproducible consistently
 * Tested in Chrome on Windows
 * The pattern submission initially appears successful before failing
 during subsequent API/editor requests

 Based on the testing, this may be related to:

 * REST API routing
 * Authentication/nonce handling
 * Permission validation
 * Post-submit editor requests on WordPress.org infrastructure

 The `users/me` request returning `404` and related `403` API responses may
 help identify the root cause.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65189#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 15:01:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 15:01:00 -0000
Subject: [wp-trac] [WordPress Trac] #65190: Add komoot to the oEmbed
 provider allowlist
Message-ID: <057.3ad57a6099d748d11f937c1077d560cb@wordpress.org>

#65190: Add komoot to the oEmbed provider allowlist
---------------------------+-----------------------------
 Reporter:  federicofonta  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Embeds         |    Version:
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 komoot (https://www.komoot.com) is a route-planning and outdoor navigation
 platform with public tour, smarttour, collection, and guide pages.

 komoot now provides an oEmbed-compatible JSON endpoint:

 https://www.komoot.com/oembed

 Supported URL examples:

 - https://www.komoot.com/tour/2766645113
 - https://www.komoot.com/smarttour/e1239517945
 - https://www.komoot.de/collection/2050920
 - https://www.komoot.com/guide/1006/dolomites-mountain-passes

 The endpoint follows the oEmbed spec:

 - `format=json`
 - `type=rich`
 - returns `html` containing an iframe, `width`, `height`, `provider_name`,
 `provider_url`, `cache_age`
 - returns `thumbnail_url` for tour and smarttour embeds
 - sends `Access-Control-Allow-Origin: *`
 - sends cacheable responses via `Cache-Control: public, max-age=3600,
 s-maxage=86400`

 Example request:

 https://www.komoot.com/oembed?url=https%3A%2F%2Fwww.komoot.com%2Ftour%2F2766645113&format=json

 Example response includes:

 {{{
 <iframe
 src="https://www.komoot.com/tour/2766645113/embed?layout=classic&embed_source=oembed&profile=1"
 width="640" height="700" frameborder="0" scrolling="no" allowfullscreen
 referrerpolicy="strict-origin-when-cross-origin"></iframe>
 }}}

 Discovery tags are also present on canonical embeddable pages:

 {{{
 <link rel="alternate" type="application/json+oembed"
 href="https://www.komoot.com/oembed?url=..." title="..." />
 }}}

 Adding komoot to the trusted providers list would let WordPress users
 paste komoot URLs directly into the editor and get a rich
 route/collection/guide embed without installing a plugin.

 Suggested provider pattern:

 {{{
 #https?://(www\.)?komoot\.(com|de|es|fr|it|nl|pl|jp|kr)/(tour|smarttour|collection|guide)/.*#i
 }}}

 Suggested endpoint:

 {{{
 https://www.komoot.com/oembed
 }}}

 How to test:

 1. Apply the provider allowlist patch.
 2. Open a new post in Gutenberg.
 3. Paste one supported komoot URL on its own line, for example:
    - https://www.komoot.com/tour/2766645113
    - https://www.komoot.de/collection/2050920
    - https://www.komoot.com/guide/1006/dolomites-mountain-passes
 4. Confirm WordPress resolves the URL to an embed block.
 5. Confirm the front-end post output contains the iframe from the oEmbed
 response.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65190>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 15:05:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 15:05:13 -0000
Subject: [wp-trac] [WordPress Trac] #65191: deletePluginSuccess does not
 update counts for custom plugin_status groups
Message-ID: <052.d4bbf842536c16e47061eee401603e57@wordpress.org>

#65191: deletePluginSuccess does not update counts for custom plugin_status groups
--------------------------+---------------------------------------
 Reporter:  andrew.p      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Plugins       |    Version:
 Severity:  minor         |   Keywords:  needs-testing needs-patch
  Focuses:                |
--------------------------+---------------------------------------
 #60495 added the `plugins_list_status_text` filter, so plugins can
 register custom group tabs on `plugins.php` by adding entries to the array
 passed through `plugins_list` and supplying a label through the new
 filter.

 The server side works. The count badge is right on initial load, and
 `?plugin_status=<custom>` filters the list as expected.

 The AJAX delete flow does not keep up. `wp.updates.deletePluginSuccess` in
 `wp-admin/js/updates.js` only decrements counts for the hardcoded buckets
 (`upgrade`, `inactive`, `active`, `recently_activated`). Anything added
 through `plugins_list` is skipped, so the badge on the custom tab stays
 stale until the page reloads.

 == Steps to reproduce ==

 1. Drop the snippet below into a must-use plugin to register a sample
 group.

 {{{
 #!php
 <?php
 add_filter( 'plugins_list', function( $plugins ) {
         if ( empty( $plugins['all'] ) ) {
                 return $plugins;
         }

         $plugins['demo_group'] = array_filter(
                 $plugins['all'],
                 static function ( $data, $file ) {
                         return str_starts_with( $file, 'a' );
                 },
                 ARRAY_FILTER_USE_BOTH
         );

         return $plugins;
 } );

 add_filter( 'plugins_list_status_text', function( $text, $count, $type ) {
         return $type === 'demo_group' ? 'Demo Group' : $text;
 }, 10, 3 );
 }}}

 2. Install two plugins whose folder starts with `a`, plus one that does
 not.
 3. Visit `wp-admin/plugins.php`. The "Demo Group (2)" tab shows the right
 count.
 4. Click the tab. Delete one of the listed plugins from the row actions.
 5. The row fades out, but the tab still reads "(2)".
 6. Reload the page. The tab now reads "(1)", matching what the server
 returns.

 The hardcoded tabs (`Active`, `Inactive`) decrement correctly in the same
 flow.

 == Cause ==

 In `wp-admin/js/updates.js`, `deletePluginSuccess` checks four buckets and
 stops:

 {{{
 #!js
 if ( -1 !== _.indexOf( plugins.upgrade, response.plugin ) ) { ... }
 if ( -1 !== _.indexOf( plugins.inactive, response.plugin ) ) { ... }
 if ( -1 !== _.indexOf( plugins.active, response.plugin ) ) { ... }
 if ( -1 !== _.indexOf( plugins.recently_activated, response.plugin ) ) {
 ... }
 }}}

 Other keys present in `plugins` are not iterated.

 == Suggested approach ==

 After the existing blocks, walk any remaining keys and apply the same
 pattern. Hardcoded keys keep their explicit path, so existing sites see no
 behavior change.

 {{{
 #!js
 var knownKeys = [ 'all', 'search', 'upgrade', 'active', 'inactive',
         'recently_activated', 'mustuse', 'dropins', 'paused',
         'auto-update-enabled', 'auto-update-disabled' ];

 _.each( _.keys( plugins ), function( key ) {
         if ( -1 !== _.indexOf( knownKeys, key ) ) {
                 return;
         }
         if ( ! _.isArray( plugins[ key ] ) ) {
                 return;
         }
         if ( -1 === _.indexOf( plugins[ key ], response.plugin ) ) {
                 return;
         }

         plugins[ key ] = _.without( plugins[ key ], response.plugin );

         var $tab = $views.find( '.' + key );

         if ( plugins[ key ].length ) {
                 $tab.find( '.count' ).text( '(' + plugins[ key ].length +
 ')' );
         } else {
                 $tab.remove();
         }
 } );
 }}}

 The activate, deactivate, and update success callbacks likely have the
 same gap. Happy to roll those into one patch if reviewers want a single
 sweep, otherwise this ticket can stay scoped to delete.

 == Notes ==

 `wp-plugin-delete-success` is already triggered as a jQuery event, so
 individual plugins can shim this on the client. With #60495 turning custom
 groups into a documented extension point, asking every consumer to ship
 the same workaround does not feel right.

 == Test plan ==

 - Hardcoded tabs: delete still decrements `Active`, `Inactive`, and
 `Update available` exactly as before.
 - Custom group registered via `plugins_list`: the count drops on delete,
 and the tab disappears when it reaches zero.
 - Sites with no custom group: no change, no extra DOM lookups.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65191>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 15:05:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 15:05:49 -0000
Subject: [wp-trac] [WordPress Trac] #65191: deletePluginSuccess does not
 update counts for custom plugin_status groups
In-Reply-To: <052.d4bbf842536c16e47061eee401603e57@wordpress.org>
References: <052.d4bbf842536c16e47061eee401603e57@wordpress.org>
Message-ID: <067.7d3cdfa1a602e987d55960a0270dbf79@wordpress.org>

#65191: deletePluginSuccess does not update counts for custom plugin_status groups
---------------------------------------+------------------------------
 Reporter:  andrew.p                   |       Owner:  (none)
     Type:  defect (bug)               |      Status:  new
 Priority:  normal                     |   Milestone:  Awaiting Review
Component:  Plugins                    |     Version:
 Severity:  minor                      |  Resolution:
 Keywords:  needs-testing needs-patch  |     Focuses:
---------------------------------------+------------------------------
Changes (by andrew.p):

 * Attachment "wp-core-fix-deletePluginSuccess.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65191>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 15:32:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 15:32:39 -0000
Subject: [wp-trac] [WordPress Trac] #65192: Tests: Add unit tests for
 wp_admin_canonical_url()
Message-ID: <051.8cc9c0effb5bff62a8d0821e6a44adc3@wordpress.org>

#65192: Tests: Add unit tests for wp_admin_canonical_url()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the wp_admin_canonical_url()
 function in wp-admin/includes/misc.php. The tests will cover the default
 URL generation, handling of query parameters, and the
 wp_admin_canonical_url filter.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65192>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 15:48:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 15:48:34 -0000
Subject: [wp-trac] [WordPress Trac] #65193: Tests: Add unit tests for
 wp_page_reload_on_back_button_js()
Message-ID: <051.5aae89aca4ab44ce78353fe0a50cb02c@wordpress.org>

#65193: Tests: Add unit tests for wp_page_reload_on_back_button_js()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the wp_page_reload_on_back_button_js()
 function in wp-admin/includes/misc.php. The tests will verify the correct
 HTML/JavaScript output.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65193>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 15:54:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 15:54:28 -0000
Subject: [wp-trac] [WordPress Trac] #65194: Tests: Add unit tests for
 update_home_siteurl()
Message-ID: <051.68d7dedf7b5b3ed7f984df5a6af91088@wordpress.org>

#65194: Tests: Add unit tests for update_home_siteurl()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds unit tests for the update_home_siteurl() function in wp-
 admin/includes/misc.php. The tests will verify that rewrite rules are
 correctly flushed (or the rewrite_rules option is deleted in multisite)
 when site URLs change, while respecting the installation state.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65194>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 16:12:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 16:12:50 -0000
Subject: [wp-trac] [WordPress Trac] #65195: Tests: Add unit tests for
 wp_check_locked_posts()
Message-ID: <051.8ee433f6e44e262b36cceab40fbe6587@wordpress.org>

#65195: Tests: Add unit tests for wp_check_locked_posts()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the wp_check_locked_posts()
 function in wp-admin/includes/misc.php. These tests ensure that the
 function correctly identifies locked posts, handles missing or invalid
 data in Heartbeat requests, and verifies that the correct user information
 (including avatars and collaboration status) is returned based on user
 permissions and site options.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65195>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 16:20:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 16:20:44 -0000
Subject: [wp-trac] [WordPress Trac] Batch modify: #65195, #65194, #65193,
 #65192, #65187, ...
In-Reply-To: <389.dc98d78118b811d5a652d636f8da8659@wordpress.org>
References: <389.dc98d78118b811d5a652d636f8da8659@wordpress.org>
Message-ID: <404.6aeb02abb8cd060386afabdffe838b8c@wordpress.org>

Batch modification to #65195, #65194, #65193, #65192, #65187, #65186, #65185, #65184, #65183, #65182, #65181, #65180, #65179, #65178, #65176, #65175, #65174, #65173, #65172, #65170, #65148, #65147, #65146, #65137, #65136, #65135, #65134, #60828, #60177, #60114, #59854, #59851, #59829, #59820, #59792, #59790, #59788, #59775, #59752, #59721, #59710, #59709, #59707, #59700, #59699, #59697, #59637, #59623, #57264, #57263, #57224, #57081, #56047, #55729, #55192, #54754, #54490, #54359 by desrosj:


Comment:
Adding the `tests` focus, which is used to indicate a ticket is solely focused on adding tests.

-- 
Tickets URL: <https://core.trac.wordpress.org/query?id=65195%2C65194%2C65193%2C65192%2C65187%2C65186%2C65185%2C65184%2C65183%2C65182%2C65181%2C65180%2C65179%2C65178%2C65176%2C65175%2C65174%2C65173%2C65172%2C65170%2C65148%2C65147%2C65146%2C65137%2C65136%2C65135%2C65134%2C60828%2C60177%2C60114%2C59854%2C59851%2C59829%2C59820%2C59792%2C59790%2C59788%2C59775%2C59752%2C59721%2C59710%2C59709%2C59707%2C59700%2C59699%2C59697%2C59637%2C59623%2C57264%2C57263%2C57224%2C57081%2C56047%2C55729%2C55192%2C54754%2C54490%2C54359>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 16:21:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 16:21:50 -0000
Subject: [wp-trac] [WordPress Trac] Batch modify: #54180, #53927, #46639,
 #42058
In-Reply-To: <065.6c71bb8c210059b045046796466177c8@wordpress.org>
References: <065.6c71bb8c210059b045046796466177c8@wordpress.org>
Message-ID: <080.bf951a83ba6ae8ed1a8eeeed89fc7c36@wordpress.org>

Batch modification to #54180, #53927, #46639, #42058 by desrosj:


Comment:
Adding the `tests` focus, which is used to indicate a ticket is solely focused on adding tests.

-- 
Tickets URL: <https://core.trac.wordpress.org/query?id=54180%2C53927%2C46639%2C42058>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 16:29:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 16:29:05 -0000
Subject: [wp-trac] [WordPress Trac] #65196: Tests: Add unit tests for
 wp_refresh_post_lock()
Message-ID: <051.17ba63f01ac397e8b926bf29997134e7@wordpress.org>

#65196: Tests: Add unit tests for wp_refresh_post_lock()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the wp_refresh_post_lock()
 function in wp-admin/includes/misc.php. These tests ensure that the
 function correctly updates the post lock, handles invalid post IDs, and
 returns the appropriate Heartbeat response data (including updated lock
 and nonces if necessary).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65196>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 16:34:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 16:34:38 -0000
Subject: [wp-trac] [WordPress Trac] #65197: Tests: Add unit tests for
 wp_refresh_post_nonces()
Message-ID: <051.49f8cac5d266dca5c189706aea86cf97@wordpress.org>

#65197: Tests: Add unit tests for wp_refresh_post_nonces()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the wp_refresh_post_nonces()
 function in wp-admin/includes/misc.php. These tests ensure that the
 function correctly returns refreshed nonces for post locking and unlocking
 when appropriate Heartbeat data is provided and the user has the necessary
 permissions.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65197>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 16:36:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 16:36:21 -0000
Subject: [wp-trac] [WordPress Trac] #65121: Command Palette: Label can
 be incorrect for sites served over a CDN
In-Reply-To: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
References: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
Message-ID: <072.1d2dcd9c8ae3fb5a5065be4cdd82c015@wordpress.org>

#65121: Command Palette: Label can be incorrect for sites served over a CDN
------------------------------------+----------------------------
 Reporter:  peterwilsoncc           |       Owner:  peterwilsoncc
     Type:  defect (bug)            |      Status:  closed
 Priority:  normal                  |   Milestone:  7.0
Component:  Toolbar                 |     Version:  trunk
 Severity:  normal                  |  Resolution:  fixed
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+----------------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62320" 62320]:
 {{{
 #!CommitTicketReference repository="" revision="62320"
 Toolbar: Improvements to changes in [62282].

 This updates the JavaScript based regular expression to be case-
 insensitive, which matches the corresponding PHP pattern.

 A defensive check has alos been added to avoid a `TypeError` if the admin
 bar is manipulated in a way that changes the path of the targeted element.

 Follow up to [62282].

 Props westonruter.
 Fixes #65121.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65121#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 16:36:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 16:36:51 -0000
Subject: [wp-trac] [WordPress Trac] #65121: Command Palette: Label can
 be incorrect for sites served over a CDN
In-Reply-To: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
References: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
Message-ID: <072.aaecd84e623474d17d3d4017cd0af8fb@wordpress.org>

#65121: Command Palette: Label can be incorrect for sites served over a CDN
-------------------------------------------------+-------------------------
 Reporter:  peterwilsoncc                        |       Owner:
                                                 |  peterwilsoncc
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch fixed-major commit dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch dev-feedback => has-patch fixed-major commit dev-
     reviewed
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening to backport both [62282] and [62320].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65121#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 16:52:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 16:52:46 -0000
Subject: [wp-trac] [WordPress Trac] #65121: Command Palette: Label can
 be incorrect for sites served over a CDN
In-Reply-To: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
References: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
Message-ID: <072.680f41c3ec757d44e4d44e4cb6dc5455@wordpress.org>

#65121: Command Palette: Label can be incorrect for sites served over a CDN
-------------------------------------------------+-------------------------
 Reporter:  peterwilsoncc                        |       Owner:
                                                 |  peterwilsoncc
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch fixed-major commit dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------

Comment (by jorbin):

 [62282] and [62320] look good for backport to the 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65121#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 16:55:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 16:55:16 -0000
Subject: [wp-trac] [WordPress Trac] #65198: Tests: Add unit tests for
 wp_refresh_metabox_loader_nonces()
Message-ID: <051.5ec3846a3993e112ac91b9eaef65125f@wordpress.org>

#65198: Tests: Add unit tests for wp_refresh_metabox_loader_nonces()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the
 wp_refresh_metabox_loader_nonces() function in wp-admin/includes/misc.php.
 These tests ensure that the function correctly returns refreshed nonces
 (meta-box-loader and update-post_{$post_id}) when valid data is provided
 and the user has edit permissions.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65198>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:01:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:01:34 -0000
Subject: [wp-trac] [WordPress Trac] #53010: Tests: introduce namespacing
 for the test classes
In-Reply-To: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
References: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
Message-ID: <062.149c5092a33d023ae908c8ab86b76e31@wordpress.org>

#53010: Tests: introduce namespacing for the test classes
--------------------------------------+------------------------------------
 Reporter:  jrf                       |       Owner:  SergeyBiryukov
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  docs, coding-
                                      |  standards
--------------------------------------+------------------------------------

Comment (by pbearne):

 Are we starting on this?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53010#comment:65>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:02:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:02:22 -0000
Subject: [wp-trac] [WordPress Trac] #65103: Single-page admin screens
 (Connectors,
 Font Library) fail to mount in Chrome when @wordpress/boot wins a race
 against its classic-script deps
In-Reply-To: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
References: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
Message-ID: <070.b31066a9ab683eab67c13c051e0bccf4@wordpress.org>

#65103: Single-page admin screens (Connectors, Font Library) fail to mount in
Chrome when @wordpress/boot wins a race against its classic-script deps
-------------------------------------------------+-------------------------
 Reporter:  fabiankaegy                          |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  Script Loader                        |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  script-modules has-patch changes-    |     Focuses:
  requested                                      |  administration
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * priority:  normal => high


Comment:

 As this issues means that a new 7.0 feature is broken, I am bumping up the
 prioirty.

 @khokansardar are you able to follow up on the changes that @westonruter
 suggested above?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65103#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:04:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:04:00 -0000
Subject: [wp-trac] [WordPress Trac] #65198: Tests: Add unit tests for
 wp_refresh_metabox_loader_nonces()
In-Reply-To: <051.5ec3846a3993e112ac91b9eaef65125f@wordpress.org>
References: <051.5ec3846a3993e112ac91b9eaef65125f@wordpress.org>
Message-ID: <066.a4503dffaa351df02f53b65b4d96b8fc@wordpress.org>

#65198: Tests: Add unit tests for wp_refresh_metabox_loader_nonces()
----------------------------+------------------------------
 Reporter:  pbearne         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  tests
----------------------------+------------------------------
Changes (by pbearne):

 * focuses:   => tests


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65198#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:06:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:06:14 -0000
Subject: [wp-trac] [WordPress Trac] #64789: Security audit for API key
 storage on the Connectors screen
In-Reply-To: <050.2dc2adeded3d033a30689e22ac0c9ef2@wordpress.org>
References: <050.2dc2adeded3d033a30689e22ac0c9ef2@wordpress.org>
Message-ID: <065.9fb67fcb062836f31305b81b72734cb9@wordpress.org>

#64789: Security audit for API key storage on the Connectors screen
-------------------------+-------------------------------------------------
 Reporter:  gziolo       |       Owner:  (none)
     Type:  task         |      Status:  new
  (blessed)              |
 Priority:  normal       |   Milestone:  Future Release
Component:  Security     |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:  2nd-opinion  |     Focuses:  ui, administration, rest-api,
                         |  privacy
-------------------------+-------------------------------------------------
Changes (by jorbin):

 * milestone:  7.0 => Future Release


Comment:

 Based on @johnbillion and @flixos90's comments and the fact that we are
 quickly approaching 7.0 RC3 (new beta 1), I am moving this to future
 release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64789#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:06:47 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:06:47 -0000
Subject: [wp-trac] [WordPress Trac] #64393: Change how we include
 Gutenberg in Core
In-Reply-To: <055.264b0dba638f7c3f5a9d3208ee755072@wordpress.org>
References: <055.264b0dba638f7c3f5a9d3208ee755072@wordpress.org>
Message-ID: <070.6eeb474e0bdc1419eac3d70d5af9b1b1@wordpress.org>

#64393: Change how we include Gutenberg in Core
------------------------------+--------------------------
 Reporter:  youknowriad       |       Owner:  youknowriad
     Type:  task (blessed)    |      Status:  closed
 Priority:  high              |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  blocker           |  Resolution:  fixed
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------

Comment (by desrosj):

 In [changeset:"62321" 62321]:
 {{{
 #!CommitTicketReference repository="" revision="62321"
 Build/Test Tools: Remove `gutenberg:verify` script on `postinstall`.

 In [61458], a `postinstall` script was introduced that ensured the source
 code from the `gutenberg` repository was present before attempting to run
 the build script.

 The WordPress.org Hosting Tests surfaced an edge case where the
 `postinstall` script was failing when `nodevenv` is used. Because it
 serves as a wrapper for Node.js, `NPM_CONFIG_PREFIX` is set to the virual
 envirnoment directory and not the actual project source directory.

 This removes `gutenberg:verify` from `postinstall` entirely.
 `gutenberg:verify` is responsible for confirming that the `gutenberg`
 directory exists, that the commit SHA value in `gutenberg/.gutenberg-hash`
 matches `gutenberg.sha` in the `package.json` file, and it downloads a
 fresh copy if not.

 While this will result in the necessary files not being present locally
 after running `npm install`, `gutenberg:verify` is specified as the first
 task executed when the `build` and `build:dev` scripts are run. Running
 either build script has been a requirement to run WordPress locally for
 some time now, so this does not introduce a new required step. It simply
 delays when the built asset will be retrieved from the GitHub Container
 Registry when necessary.

 `postinstall` scripts should also be avoided entirely due to their
 significantly insecure nature (see #64543).

 Follow up to [61492], [61873], and [62021].

 Props jorbin, johnbillion.
 Fixes #64874. See #64393, #64543.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64393#comment:259>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:06:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:06:48 -0000
Subject: [wp-trac] [WordPress Trac] #64874: `postinstall` scripts are
 failing in some environments
In-Reply-To: <051.f17b58ad2a5d24c0f8bb62395bfd934d@wordpress.org>
References: <051.f17b58ad2a5d24c0f8bb62395bfd934d@wordpress.org>
Message-ID: <066.313e159db0057938bd3a355928a206f2@wordpress.org>

#64874: `postinstall` scripts are failing in some environments
------------------------------+----------------------
 Reporter:  desrosj           |       Owner:  desrosj
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch         |     Focuses:
------------------------------+----------------------
Changes (by desrosj):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62321" 62321]:
 {{{
 #!CommitTicketReference repository="" revision="62321"
 Build/Test Tools: Remove `gutenberg:verify` script on `postinstall`.

 In [61458], a `postinstall` script was introduced that ensured the source
 code from the `gutenberg` repository was present before attempting to run
 the build script.

 The WordPress.org Hosting Tests surfaced an edge case where the
 `postinstall` script was failing when `nodevenv` is used. Because it
 serves as a wrapper for Node.js, `NPM_CONFIG_PREFIX` is set to the virual
 envirnoment directory and not the actual project source directory.

 This removes `gutenberg:verify` from `postinstall` entirely.
 `gutenberg:verify` is responsible for confirming that the `gutenberg`
 directory exists, that the commit SHA value in `gutenberg/.gutenberg-hash`
 matches `gutenberg.sha` in the `package.json` file, and it downloads a
 fresh copy if not.

 While this will result in the necessary files not being present locally
 after running `npm install`, `gutenberg:verify` is specified as the first
 task executed when the `build` and `build:dev` scripts are run. Running
 either build script has been a requirement to run WordPress locally for
 some time now, so this does not introduce a new required step. It simply
 delays when the built asset will be retrieved from the GitHub Container
 Registry when necessary.

 `postinstall` scripts should also be avoided entirely due to their
 significantly insecure nature (see #64543).

 Follow up to [61492], [61873], and [62021].

 Props jorbin, johnbillion.
 Fixes #64874. See #64393, #64543.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64874#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:06:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:06:48 -0000
Subject: [wp-trac] [WordPress Trac] #64543: Implement `ignore-scripts`
 to harden npm usage
In-Reply-To: <055.6dcb52fa376eb7fffd4085d384323858@wordpress.org>
References: <055.6dcb52fa376eb7fffd4085d384323858@wordpress.org>
Message-ID: <070.f56ece56228775446d719c26aa3072b8@wordpress.org>

#64543: Implement `ignore-scripts` to harden npm usage
------------------------------+------------------------------
 Reporter:  johnbillion       |       Owner:  (none)
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:  javascript
------------------------------+------------------------------

Comment (by desrosj):

 In [changeset:"62321" 62321]:
 {{{
 #!CommitTicketReference repository="" revision="62321"
 Build/Test Tools: Remove `gutenberg:verify` script on `postinstall`.

 In [61458], a `postinstall` script was introduced that ensured the source
 code from the `gutenberg` repository was present before attempting to run
 the build script.

 The WordPress.org Hosting Tests surfaced an edge case where the
 `postinstall` script was failing when `nodevenv` is used. Because it
 serves as a wrapper for Node.js, `NPM_CONFIG_PREFIX` is set to the virual
 envirnoment directory and not the actual project source directory.

 This removes `gutenberg:verify` from `postinstall` entirely.
 `gutenberg:verify` is responsible for confirming that the `gutenberg`
 directory exists, that the commit SHA value in `gutenberg/.gutenberg-hash`
 matches `gutenberg.sha` in the `package.json` file, and it downloads a
 fresh copy if not.

 While this will result in the necessary files not being present locally
 after running `npm install`, `gutenberg:verify` is specified as the first
 task executed when the `build` and `build:dev` scripts are run. Running
 either build script has been a requirement to run WordPress locally for
 some time now, so this does not introduce a new required step. It simply
 delays when the built asset will be retrieved from the GitHub Container
 Registry when necessary.

 `postinstall` scripts should also be avoided entirely due to their
 significantly insecure nature (see #64543).

 Follow up to [61492], [61873], and [62021].

 Props jorbin, johnbillion.
 Fixes #64874. See #64393, #64543.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64543#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:07:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:07:59 -0000
Subject: [wp-trac] [WordPress Trac] #65199: Tests: Add unit tests for
 wp_refresh_heartbeat_nonces()
Message-ID: <051.63c2699c6e4ee5eb797882912e57f78a@wordpress.org>

#65199: Tests: Add unit tests for wp_refresh_heartbeat_nonces()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 This ticket adds unit tests for the wp_refresh_heartbeat_nonces() function
 in wp-admin/includes/misc.php. These tests will verify that the function
 correctly refreshes the Heartbeat nonce and returns it in the response
 data.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65199>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:08:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:08:11 -0000
Subject: [wp-trac] [WordPress Trac] #64874: `postinstall` scripts are
 failing in some environments
In-Reply-To: <051.f17b58ad2a5d24c0f8bb62395bfd934d@wordpress.org>
References: <051.f17b58ad2a5d24c0f8bb62395bfd934d@wordpress.org>
Message-ID: <066.6b58c8c561bf460321e214f942147a94@wordpress.org>

#64874: `postinstall` scripts are failing in some environments
-------------------------------------------------+-------------------------
 Reporter:  desrosj                              |       Owner:  desrosj
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Build/Test Tools                     |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback commit        |     Focuses:
  fixed-major                                    |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch => has-patch dev-feedback commit fixed-major
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening to consider for backporting.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64874#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:11:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:11:04 -0000
Subject: [wp-trac] [WordPress Trac] #65200: Tests: Add unit tests for
 wp_heartbeat_set_suspension()
Message-ID: <051.95a72c11b11ee45e117268c654f22cc3@wordpress.org>

#65200: Tests: Add unit tests for wp_heartbeat_set_suspension()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 This ticket adds unit tests for the wp_heartbeat_set_suspension() function
 in wp-admin/includes/misc.php. The tests will verify that the function
 correctly modifies the Heartbeat settings to disable suspension when on
 post.php or post-new.php, and leaves them unchanged otherwise.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65200>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:13:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:13:02 -0000
Subject: [wp-trac] [WordPress Trac] #65121: Command Palette: Label can
 be incorrect for sites served over a CDN
In-Reply-To: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
References: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
Message-ID: <072.d2bec36cdce5db8198b7a477720161f2@wordpress.org>

#65121: Command Palette: Label can be incorrect for sites served over a CDN
-------------------------------------------------+-------------------------
 Reporter:  peterwilsoncc                        |       Owner:
                                                 |  peterwilsoncc
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch fixed-major commit dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62322" 62322]:
 {{{
 #!CommitTicketReference repository="" revision="62322"
 Toolbar: Add JavaScript fallback for determining command palette icon.

 Introduces a JavaScript fallback for determining whether the command
 palette icon in the toolbar should display ⌘Kfor Apple devices.

 This is to account for sites behind a CDN as it's common for the User-
 Agent header to be stripped from the request sent to the application
 server in order to increase cache hits on the edge.

 Reviewed by westonruter, desrosj.
 Merges [62282] to the 7.0 branch.

 Props peterwilsoncc, westonruter, mukesh27, ramonopoly, desrosj.
 Fixes #65121.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65121#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:14:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:14:20 -0000
Subject: [wp-trac] [WordPress Trac] #65201: Tests: Add unit tests for
 heartbeat_autosave()
Message-ID: <051.799506c4ea86a1cd6d15002df41570e2@wordpress.org>

#65201: Tests: Add unit tests for heartbeat_autosave()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the heartbeat_autosave()
 function in wp-admin/includes/misc.php. These tests will verify that the
 function correctly triggers wp_autosave() and returns the appropriate
 Heartbeat response for success, error, and empty states.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65201>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:14:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:14:52 -0000
Subject: [wp-trac] [WordPress Trac] #65121: Command Palette: Label can
 be incorrect for sites served over a CDN
In-Reply-To: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
References: <057.7e3cb1dd81bd572af308eb2d325d069c@wordpress.org>
Message-ID: <072.346b00cb810b9327ebc0fb5f3202ef8f@wordpress.org>

#65121: Command Palette: Label can be incorrect for sites served over a CDN
-------------------------------------------------+-------------------------
 Reporter:  peterwilsoncc                        |       Owner:
                                                 |  peterwilsoncc
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch fixed-major commit dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------

Comment (by desrosj):

 In [changeset:"62323" 62323]:
 {{{
 #!CommitTicketReference repository="" revision="62323"
 Toolbar: Improvements to changes in [62282].

 This updates the JavaScript based regular expression to be case-
 insensitive, which matches the corresponding PHP pattern.

 A defensive check has alos been added to avoid a `TypeError` if the admin
 bar is manipulated in a way that changes the path of the targeted element.

 Follow up to [62282].

 Reviewed by westonruter, desrosj, jorbin.
 Merges [62320] to the 7.0 branch.

 Props westonruter, dersosj, jorbin.
 Fixes #65121.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65121#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:21:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:21:29 -0000
Subject: [wp-trac] [WordPress Trac] #65202: Tests: Add unit tests for
 wp_privacy_generate_personal_data_export_group_html()
Message-ID: <051.9948697a3015d1530eb133401e5eefa7@wordpress.org>

#65202: Tests: Add unit tests for
wp_privacy_generate_personal_data_export_group_html()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 his ticket adds unit tests for the
 wp_privacy_generate_personal_data_export_group_html() function in wp-
 admin/includes/misc.php. The tests will verify the correct generation of
 HTML for different data types (lists and tables) and ensure proper
 escaping of data.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65202>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:39:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:39:08 -0000
Subject: [wp-trac] [WordPress Trac] #65202: Tests: Add unit tests for
 _wp_privacy_settings_filter_draft_page_titles() (was: Tests: Add unit tests
 for wp_privacy_generate_personal_data_export_group_html())
In-Reply-To: <051.9948697a3015d1530eb133401e5eefa7@wordpress.org>
References: <051.9948697a3015d1530eb133401e5eefa7@wordpress.org>
Message-ID: <066.d4bbfcb74642ec20aa2bfb78b9c91d81@wordpress.org>

#65202: Tests: Add unit tests for _wp_privacy_settings_filter_draft_page_titles()
----------------------------+------------------------------
 Reporter:  pbearne         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  tests
----------------------------+------------------------------
Description changed by pbearne:

Old description:

> his ticket adds unit tests for the
> wp_privacy_generate_personal_data_export_group_html() function in wp-
> admin/includes/misc.php. The tests will verify the correct generation of
> HTML for different data types (lists and tables) and ensure proper
> escaping of data.

New description:

 This ticket adds unit tests for the
 _wp_privacy_settings_filter_draft_page_titles() function in wp-
 admin/includes/misc.php.

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65202#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:44:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:44:05 -0000
Subject: [wp-trac] [WordPress Trac] #65203: Tests: Add unit tests for
 wp_check_php_version()
Message-ID: <051.d12790340ad3f067c63aa183a99c6f2c@wordpress.org>

#65203: Tests: Add unit tests for wp_check_php_version()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 This ticket adds comprehensive unit tests for the wp_check_php_version()
 function in wp-admin/includes/misc.php. The tests will cover API response
 handling, transient caching, the wp_is_php_version_acceptable filter, and
 future minimum version logic (e.g., forcing warnings for PHP < 8.0).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65203>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:48:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:48:28 -0000
Subject: [wp-trac] [WordPress Trac] #64142: Transients inconsistency
 since 6.9-beta1
In-Reply-To: <050.c02095cfbccc222b949bb36fbea4fa62@wordpress.org>
References: <050.c02095cfbccc222b949bb36fbea4fa62@wordpress.org>
Message-ID: <065.b7d0ff860e5bd87c5b9edbb0bb74b461@wordpress.org>

#64142: Transients inconsistency since 6.9-beta1
-------------------------------------+----------------------
 Reporter:  nico23                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  Cache API                |     Version:
 Severity:  normal                   |  Resolution:  invalid
 Keywords:  reporter-feedback close  |     Focuses:  tests
-------------------------------------+----------------------

Comment (by nico23):

 Seems this changed AGAIN. I adjusted my test code for this, now with
 7.0-RC2 this adjustment is not needed anymore.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64142#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 17:57:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 17:57:24 -0000
Subject: [wp-trac] [WordPress Trac] #64683: _print_scripts should use
 the wp_inline_script_attributes filter
In-Reply-To: <051.b101eb3cd239e67d8a67df5ddf22e3ba@wordpress.org>
References: <051.b101eb3cd239e67d8a67df5ddf22e3ba@wordpress.org>
Message-ID: <066.2b25b1bb935856698a26acd28f9882f2@wordpress.org>

#64683: _print_scripts should use the wp_inline_script_attributes filter
---------------------------------------------+--------------------------
 Reporter:  galaxor                          |       Owner:  westonruter
     Type:  enhancement                      |      Status:  reviewing
 Priority:  normal                           |   Milestone:  7.1
Component:  Script Loader                    |     Version:  2.8
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  javascript
---------------------------------------------+--------------------------
Changes (by westonruter):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests commit
 * owner:  galaxor => westonruter
 * status:  assigned => reviewing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64683#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 18:21:26 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 18:21:26 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.c465c995af2ea715f4cc4af145aae0d3@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
---------------------------+-------------------------
 Reporter:  jonsurrell     |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  high           |   Milestone:  7.0
Component:  Script Loader  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+-------------------------

Comment (by jonsurrell):

 [https://github.com/WordPress/gutenberg/issues/78041#issuecomment-4397768303
 There's a related issue described in this Gutenberg issue] that may be
 addressed by including the polyfill for Firefox.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 19:12:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 19:12:37 -0000
Subject: [wp-trac] [WordPress Trac] #62835: Remove title attributes from
 author link functions
In-Reply-To: <055.11f6fedc8818f923405c82cd932147f5@wordpress.org>
References: <055.11f6fedc8818f923405c82cd932147f5@wordpress.org>
Message-ID: <070.bc627696d14f1eb879073a0570fc6198@wordpress.org>

#62835: Remove title attributes from author link functions
-------------------------------------------------+-------------------------
 Reporter:  sabernhardt                          |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Users                                |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  title-attribute has-patch has-unit-  |     Focuses:
  tests needs-dev-note commit                    |  accessibility
-------------------------------------------------+-------------------------

Comment (by sabernhardt):

 I started a late
 [https://make.wordpress.org/core/?p=123096&preview=1&_ppp=07abef59a7 draft
 for the dev note], which probably would belong on its own (not part of the
 miscellaneous note).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62835#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 20:30:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 20:30:51 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.92d50f43d3c8b1ccae971d0d8682b7ca@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
---------------------------+-------------------------
 Reporter:  jonsurrell     |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  high           |   Milestone:  7.0
Component:  Script Loader  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+-------------------------

Comment (by jorbin):

 It is sounding more and more like the polyfill is going to be the best
 option.

 > This ties in with some thoughts I have about private modules. I'd like
 to be careful and judicious about what modules Core exposes and espree may
 not make a lot of sense as a Core module.

 @jonsurrell Could you go into a little more details about what you are
 thinking here? What are the risks associated with espree being available
 outside of core?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 20:35:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 20:35:15 -0000
Subject: [wp-trac] [WordPress Trac] #64874: `postinstall` scripts are
 failing in some environments
In-Reply-To: <051.f17b58ad2a5d24c0f8bb62395bfd934d@wordpress.org>
References: <051.f17b58ad2a5d24c0f8bb62395bfd934d@wordpress.org>
Message-ID: <066.13546a0a144127bfef439819607f9e2c@wordpress.org>

#64874: `postinstall` scripts are failing in some environments
-------------------------------------------------+-------------------------
 Reporter:  desrosj                              |       Owner:  desrosj
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Build/Test Tools                     |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch commit fixed-major dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  has-patch dev-feedback commit fixed-major => has-patch commit
     fixed-major dev-reviewed


Comment:

 [62321] Looks good for backport to 7.0

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64874#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 20:47:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 20:47:41 -0000
Subject: [wp-trac] [WordPress Trac] #64984: reply needs gettext
In-Reply-To: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
References: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
Message-ID: <067.cf88efd0c5fc3f4ccee5665c1bf675e8@wordpress.org>

#64984: reply needs gettext
------------------------------+-----------------------
 Reporter:  timse201          |       Owner:  audrasjb
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  7.0
Component:  I18N              |     Version:  trunk
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------
Changes (by jorbin):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62324" 62324]:
 {{{
 #!CommitTicketReference repository="" revision="62324"
 I18N: Add translator context to the use of "Reply".

 Props timse201, audrasjb, sanketparmar.
 Fixes #64984.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64984#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 20:47:57 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 20:47:57 -0000
Subject: [wp-trac] [WordPress Trac] #64986: preview needs gettext
In-Reply-To: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
References: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
Message-ID: <067.508300e7c78e7e6c2919ec74da42fc66@wordpress.org>

#64986: preview needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch changes-    |     Focuses:
  requested                                      |  accessibility
-------------------------------------------------+-------------------------

Comment (by jorbin):

 Add suggestions to the pr to simplify the context.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64986#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 20:48:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 20:48:37 -0000
Subject: [wp-trac] [WordPress Trac] #64984: reply needs gettext
In-Reply-To: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
References: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
Message-ID: <067.3df49fbed64cdd1d41d76abd93935967@wordpress.org>

#64984: reply needs gettext
--------------------------------------+-----------------------
 Reporter:  timse201                  |       Owner:  audrasjb
     Type:  defect (bug)              |      Status:  reopened
 Priority:  normal                    |   Milestone:  7.0
Component:  I18N                      |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  dev-feedback fixed-major  |     Focuses:
--------------------------------------+-----------------------
Changes (by jorbin):

 * keywords:  has-patch commit => dev-feedback fixed-major
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for backport consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64984#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:22:23 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:22:23 -0000
Subject: [wp-trac] [WordPress Trac] #65015: Connectors: Several strings
 are not translated
In-Reply-To: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
References: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
Message-ID: <066.bb449823ccc466633e253db93e287463@wordpress.org>

#65015: Connectors: Several strings are not translated
-------------------------------------------------+-------------------------
 Reporter:  369work                              |       Owner:
                                                 |  westonruter
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  high                                 |   Milestone:  7.0
Component:  I18N                                 |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests connectors  |     Focuses:
  commit needs-dev-note fixed-major dev-         |
  reviewed                                       |
-------------------------------------------------+-------------------------

Comment (by jorbin):

 In [changeset:"62325" 62325]:
 {{{
 #!CommitTicketReference repository="" revision="62325"
 I18N: Harden against undefined index in
 _load_script_textdomain_from_src().

 This guards against an undefined index warning being raised when a script
 or script module is registered with a URL that lacks a path component.

 This also adds full PHPStan type definitions for wp_parse_url(), ensuring
 that the _load_script_textdomain_from_src() function has no PHPStan errors
 at rule level 10.

 Developed in https://github.com/WordPress/wordpress-develop/pull/11690

 Follow-up to r62278.

 Reviewed by desrosj, jorbin.
 Merges [62293] to the 7.0 branch.

 Props westonruter, manzoorwanijk, mukesh27.
 See #65015, #64238.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65015#comment:55>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:22:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:22:22 -0000
Subject: [wp-trac] [WordPress Trac] #64238: PHPStan code quality
 improvements for 7.0
In-Reply-To: <058.3d898e5edbfd206122933e3b070d763b@wordpress.org>
References: <058.3d898e5edbfd206122933e3b070d763b@wordpress.org>
Message-ID: <073.bd531f0789d185f3bf9b8fe859e8e0d4@wordpress.org>

#64238: PHPStan code quality improvements for 7.0
--------------------------------------+-------------------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  closed
 Priority:  normal                    |   Milestone:  7.0
Component:  General                   |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  coding-standards
--------------------------------------+-------------------------------

Comment (by jorbin):

 In [changeset:"62325" 62325]:
 {{{
 #!CommitTicketReference repository="" revision="62325"
 I18N: Harden against undefined index in
 _load_script_textdomain_from_src().

 This guards against an undefined index warning being raised when a script
 or script module is registered with a URL that lacks a path component.

 This also adds full PHPStan type definitions for wp_parse_url(), ensuring
 that the _load_script_textdomain_from_src() function has no PHPStan errors
 at rule level 10.

 Developed in https://github.com/WordPress/wordpress-develop/pull/11690

 Follow-up to r62278.

 Reviewed by desrosj, jorbin.
 Merges [62293] to the 7.0 branch.

 Props westonruter, manzoorwanijk, mukesh27.
 See #65015, #64238.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64238#comment:126>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:22:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:22:42 -0000
Subject: [wp-trac] [WordPress Trac] #64984: reply needs gettext
In-Reply-To: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
References: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
Message-ID: <067.8ab8bbf7181daad838f9337e9c69b7cc@wordpress.org>

#64984: reply needs gettext
--------------------------------------+-----------------------
 Reporter:  timse201                  |       Owner:  audrasjb
     Type:  defect (bug)              |      Status:  reopened
 Priority:  normal                    |   Milestone:  7.0
Component:  I18N                      |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  fixed-major dev-reviewed  |     Focuses:
--------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  dev-feedback fixed-major => fixed-major dev-reviewed


Comment:

 This is a second committer sign-off.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64984#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:22:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:22:54 -0000
Subject: [wp-trac] [WordPress Trac] #64984: reply needs gettext
In-Reply-To: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
References: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
Message-ID: <067.2bc6732e40e31857ea69b9545531ee7f@wordpress.org>

#64984: reply needs gettext
--------------------------------------------------+-----------------------
 Reporter:  timse201                              |       Owner:  audrasjb
     Type:  defect (bug)                          |      Status:  reopened
 Priority:  normal                                |   Milestone:  7.0
Component:  I18N                                  |     Version:  trunk
 Severity:  normal                                |  Resolution:
 Keywords:  fixed-major dev-reviewed i18n-change  |     Focuses:
--------------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  fixed-major dev-reviewed => fixed-major dev-reviewed i18n-
               change


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64984#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:24:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:24:25 -0000
Subject: [wp-trac] [WordPress Trac] #65015: Connectors: Several strings
 are not translated
In-Reply-To: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
References: <051.2cae6bb1ea9ab32f5657833b0f9263d3@wordpress.org>
Message-ID: <066.79d63f88835280d83545ff809396e465@wordpress.org>

#65015: Connectors: Several strings are not translated
-------------------------------------------------+-------------------------
 Reporter:  369work                              |       Owner:
                                                 |  westonruter
     Type:  defect (bug)                         |      Status:  closed
 Priority:  high                                 |   Milestone:  7.0
Component:  I18N                                 |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests connectors  |     Focuses:
  commit needs-dev-note fixed-major dev-         |
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * status:  reopened => closed
 * resolution:   => fixed


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65015#comment:56>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:35:55 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:35:55 -0000
Subject: [wp-trac] [WordPress Trac] #64948: Media Modal: Can no longer
 set attachment filters
In-Reply-To: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
References: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
Message-ID: <074.6b4a8859aa3b569f7cfdfc6e2cbbb9d3@wordpress.org>

#64948: Media Modal: Can no longer set attachment filters
------------------------------+-------------------------
 Reporter:  Bernhard Reiter   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  7.0
Component:  Media             |     Version:  trunk
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:  javascript
------------------------------+-------------------------
Changes (by joedolson):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62326" 62326]:
 {{{
 #!CommitTicketReference repository="" revision="62326"
 Media: Restore usage of attachment filters in media modal.

 [61757] wrapped the media attachment filters, which changed the return
 value of toolbar filters from `AttachmentFilters` to a `wp.media.View`
 instance, breaking the API to customize media library filters.

 Reverts the shape change in the attachment filter return value and
 implements CSS based positioning for the visible labels.

 Props bernhard-reiter, joedolson, ozgursar, audrasjb, darshitrajyaguru97,
 jorbin.
 Fixes #64948.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64948#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:37:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:37:13 -0000
Subject: [wp-trac] [WordPress Trac] #64948: Media Modal: Can no longer
 set attachment filters
In-Reply-To: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
References: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
Message-ID: <074.51fac938b942cff6351202e5d917471e@wordpress.org>

#64948: Media Modal: Can no longer set attachment filters
-------------------------------------------+-------------------------
 Reporter:  Bernhard Reiter                |       Owner:  joedolson
     Type:  defect (bug)                   |      Status:  reopened
 Priority:  normal                         |   Milestone:  7.0
Component:  Media                          |     Version:  trunk
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch commit dev-feedback  |     Focuses:  javascript
-------------------------------------------+-------------------------
Changes (by joedolson):

 * keywords:  has-patch commit => has-patch commit dev-feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Re-opening for dev review to commit to the 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64948#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:38:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:38:14 -0000
Subject: [wp-trac] [WordPress Trac] #64948: Media Modal: Can no longer
 set attachment filters
In-Reply-To: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
References: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
Message-ID: <074.d83e18640f753c69d16090eba4c69b94@wordpress.org>

#64948: Media Modal: Can no longer set attachment filters
-------------------------------------------------+-------------------------
 Reporter:  Bernhard Reiter                      |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch commit dev-reviewed        |     Focuses:  javascript
  fixed-major                                    |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  has-patch commit dev-feedback => has-patch commit dev-reviewed
     fixed-major


Comment:

 [62326] looks good for backport to the 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64948#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:41:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:41:32 -0000
Subject: [wp-trac] [WordPress Trac] #64948: Media Modal: Can no longer
 set attachment filters
In-Reply-To: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
References: <059.043db9fa3e3bcd837140db59ad9266de@wordpress.org>
Message-ID: <074.8feb986ccb82cc78c46247e3655f6503@wordpress.org>

#64948: Media Modal: Can no longer set attachment filters
-------------------------------------------------+-------------------------
 Reporter:  Bernhard Reiter                      |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch commit dev-reviewed        |     Focuses:  javascript
  fixed-major                                    |
-------------------------------------------------+-------------------------
Changes (by joedolson):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62327" 62327]:
 {{{
 #!CommitTicketReference repository="" revision="62327"
 Media: Restore usage of attachment filters in media modal.

 [61757] wrapped the media attachment filters, which changed the return
 value of toolbar filters from `AttachmentFilters` to a `wp.media.View`
 instance, breaking the API to customize media library filters.

 Reverts the shape change in the attachment filter return value and
 implements CSS based positioning for the visible labels.

 Reviewed by jorbin.
 Merges [62326] to the 7.0 branch.

 Props bernhard-reiter, joedolson, ozgursar, audrasjb, darshitrajyaguru97,
 jorbin.
 Fixes #64948.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64948#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:45:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:45:38 -0000
Subject: [wp-trac] [WordPress Trac] #53010: Tests: introduce namespacing
 for the test classes
In-Reply-To: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
References: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
Message-ID: <062.0cec9656d29b373841bb7faa9066c0a5@wordpress.org>

#53010: Tests: introduce namespacing for the test classes
--------------------------------------+------------------------------------
 Reporter:  jrf                       |       Owner:  SergeyBiryukov
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  docs, coding-
                                      |  standards
--------------------------------------+------------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"62328" 62328]:
 {{{
 #!CommitTicketReference repository="" revision="62328"
 Tests: Rename the `admin/includesComment.php` test file to match the new
 pattern.

 This aims to make the test suite directory and file structure more
 intuitive for new contributors to work with, as well as follow the PHPUnit
 recommended test class name pattern with having `Test` as the end of the
 class name.

 Follow-up to [34456].

 Props poena.
 See #53010.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53010#comment:66>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 21:50:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 21:50:49 -0000
Subject: [wp-trac] [WordPress Trac] #64696: Real time collboration
 effectively disables persistent post caches while anyone edits a post
In-Reply-To: <057.05b7879d9d7300bfeccbd48dcfe7237b@wordpress.org>
References: <057.05b7879d9d7300bfeccbd48dcfe7237b@wordpress.org>
Message-ID: <072.9dd1dceaf299aa82de3954e4f3e4c2c2@wordpress.org>

#64696: Real time collboration effectively disables persistent post caches while
anyone edits a post
--------------------------------------+--------------------------
 Reporter:  peterwilsoncc             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.0
Component:  Posts, Post Types         |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by peterwilsoncc):

 Replying to [comment:163 blackstar1991]:
 > Sorry for my naive question. - "Will this problem be reproduced with
 taxonomy elements? Has anyone done any testing?"

 This is all very deep in the weeds, there's no need to apologize for not
 having a complete understanding.

 In the current state, it would not affect taxonomies as the rooms and
 updates are stored in the post meta so do not touch taxonomies/terms.

 However, it's likely we'll be going with a custom table.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64696#comment:171>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 22:01:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 22:01:38 -0000
Subject: [wp-trac] [WordPress Trac] #64696: Real time collboration
 effectively disables persistent post caches while anyone edits a post
In-Reply-To: <057.05b7879d9d7300bfeccbd48dcfe7237b@wordpress.org>
References: <057.05b7879d9d7300bfeccbd48dcfe7237b@wordpress.org>
Message-ID: <072.77f12938ef154a72f8702bf68b0df287@wordpress.org>

#64696: Real time collboration effectively disables persistent post caches while
anyone edits a post
--------------------------------------+--------------------------
 Reporter:  peterwilsoncc             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.0
Component:  Posts, Post Types         |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by peterwilsoncc):

 Commit process for custom table:

 1. Obtain approval of structure from @matt
 2. Commit [https://github.com/WordPress/gutenberg/pull/78045 GB PR] to
 trunk, backport
 3. Commit [https://github.com/WordPress/wordpress-develop/pull/11599 WP-
 Dev PR] to trunk, backport
 4. Upgrade GB hash in WP-Dev, backport
 5. Remove shim for `wp-sync` in WP-Dev in trunk
 6. Backport to 7.0

 The follow up commit will help ensure that continue to pass during the
 commit process.

 I will try to do some dry runs in advance.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64696#comment:172>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 23:00:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 23:00:49 -0000
Subject: [wp-trac] [WordPress Trac] #65204: Custom Bulk Actions missing from
 Grid View
Message-ID: <051.521019e1602b9796bfa9f0b8c9d08a00@wordpress.org>

#65204: Custom Bulk Actions missing from Grid View
--------------------------------------------+-----------------------------
 Reporter:  takshil                         |      Owner:  takshil
     Type:  defect (bug)                    |     Status:  assigned
 Priority:  normal                          |  Milestone:  Awaiting Review
Component:  Media                           |    Version:  trunk
 Severity:  major                           |   Keywords:
  Focuses:  ui, javascript, administration  |
--------------------------------------------+-----------------------------
 The Media Library list view allows plugins to register custom bulk actions
 via the bulk_actions-upload and handle_bulk_actions-upload PHP filters.
 However, the grid view (wp-admin/upload.php?mode=grid) does not reflect
 those bulk actions. The toolbar in bulk select mode is hardcoded to only
 show the Delete button.

 This means plugins which add bulk actions like the AI Experiments
 plugin's(e.g. "Generate Alt Text") to the Media page, will simply not show
 up on the grid view.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65204>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 23:12:09 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 23:12:09 -0000
Subject: [wp-trac] [WordPress Trac] #65204: Custom Bulk Actions missing
 from Grid View
In-Reply-To: <051.521019e1602b9796bfa9f0b8c9d08a00@wordpress.org>
References: <051.521019e1602b9796bfa9f0b8c9d08a00@wordpress.org>
Message-ID: <066.7dd194db1c8669db09b48f27900f3403@wordpress.org>

#65204: Custom Bulk Actions missing from Grid View
--------------------------+---------------------------------------------
 Reporter:  takshil       |       Owner:  takshil
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  trunk
 Severity:  major         |  Resolution:
 Keywords:                |     Focuses:  ui, javascript, administration
--------------------------+---------------------------------------------

Comment (by takshil):

 Sample plugin to test this issue:

 {{{#!php
 <?php
 /**
  * Plugin Name: Test Media Grid Bulk Action
  * Description: Test plugin for the media grid bulk actions bridge.
 Registers a
  *              single "Generate Alt Text" bulk action via PHP filters.
 With the
  *              core patch, this automatically appears in both list and
 grid views.
  * Version: 1.0.0
  * Author: Test
  */

 if ( ! defined( 'ABSPATH' ) ) {
         exit;
 }

 function test_mgba_add_list_view_bulk_action( $actions ) {
         $actions['generate_alt_text'] = __( 'Generate Alt Text' );
         return $actions;
 }
 add_filter( 'bulk_actions-upload', 'test_mgba_add_list_view_bulk_action'
 );


 function test_mgba_handle_list_view_bulk_action( $redirect_url, $action,
 $post_ids ) {
         if ( 'generate_alt_text' !== $action ) {
                 return $redirect_url;
         }

         // In a real plugin, this would process the attachments.
         $redirect_url = add_query_arg( 'generate_alt_text_count', count(
 $post_ids ), $redirect_url );

         return $redirect_url;
 }
 add_filter( 'handle_bulk_actions-upload',
 'test_mgba_handle_list_view_bulk_action', 10, 3 );
 }}}

 [[Image()]][[Image()]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65204#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 23:14:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 23:14:04 -0000
Subject: [wp-trac] [WordPress Trac] #65204: Custom Bulk Actions missing
 from Grid View
In-Reply-To: <051.521019e1602b9796bfa9f0b8c9d08a00@wordpress.org>
References: <051.521019e1602b9796bfa9f0b8c9d08a00@wordpress.org>
Message-ID: <066.262a3a0dbbb61e2487182060a5be1303@wordpress.org>

#65204: Custom Bulk Actions missing from Grid View
--------------------------+---------------------------------------------
 Reporter:  takshil       |       Owner:  takshil
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  trunk
 Severity:  major         |  Resolution:
 Keywords:                |     Focuses:  ui, javascript, administration
--------------------------+---------------------------------------------
Changes (by takshil):

 * Attachment "Screenshot 2026-05-08 at 4.42.59 AM.png" added.

 Normal Bulk actions available in the Bulk actions selector in the legacy
 List View

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65204>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 23:14:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 23:14:38 -0000
Subject: [wp-trac] [WordPress Trac] #65204: Custom Bulk Actions missing
 from Grid View
In-Reply-To: <051.521019e1602b9796bfa9f0b8c9d08a00@wordpress.org>
References: <051.521019e1602b9796bfa9f0b8c9d08a00@wordpress.org>
Message-ID: <066.e6761f75c218bead5f6248796d0864f4@wordpress.org>

#65204: Custom Bulk Actions missing from Grid View
--------------------------+---------------------------------------------
 Reporter:  takshil       |       Owner:  takshil
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  trunk
 Severity:  major         |  Resolution:
 Keywords:                |     Focuses:  ui, javascript, administration
--------------------------+---------------------------------------------
Changes (by takshil):

 * Attachment "589073656-12f2c878-02f6-4860-885f-8f04b9795122.png" added.

 Custom Bulk Action missing from the Grid View Bulk actions

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65204>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May  7 23:50:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 07 May 2026 23:50:29 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time Collaboration
 from WordPress Core
Message-ID: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
-----------------------------+--------------------
 Reporter:  jorbin           |      Owner:  (none)
     Type:  task (blessed)   |     Status:  new
 Priority:  highest omg bbq  |  Milestone:  7.0
Component:  Editor           |    Version:
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+--------------------
 Per @matt, RTC is not shipping with 7.0 and the code associated with it
 needs to be removed.

 See messages starting at
 https://wordpress.slack.com/archives/C07NVJ51X6K/p1778196273902419

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 00:07:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 00:07:34 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time
 Collaboration from WordPress Core
In-Reply-To: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
References: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
Message-ID: <065.54f5abaef99cff6bf8b129a99d41bb03@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
-----------------------------+---------------------
 Reporter:  jorbin           |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  highest omg bbq  |   Milestone:  7.0
Component:  Editor           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+---------------------

Comment (by jorbin):

 Related tickets with commits that will need to be removed (possibly not
 exhaustive):

 #64622
 #64696
 #64887
 #64949
 #65008
 #64696
 #64783
 #64845
 #64904
 #64949

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 00:39:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 00:39:59 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.a2067a6b0831911b3bc8f93a999ddaee@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by peterwilsoncc):

 Per Matt, the Real Time Collaboration feature has been pulled from the
 release, see
 [https://wordpress.slack.com/archives/C07NVJ51X6K/p1778196327707499 this
 Slack comment onwards].

 The copy will either need to be dropped or replaced in the about page:
 both in the intro and the dedicated paragraphs.

 cc @mukesh27 @fcoveram

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:38>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 01:24:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 01:24:05 -0000
Subject: [wp-trac] [WordPress Trac] #64393: Change how we include
 Gutenberg in Core
In-Reply-To: <055.264b0dba638f7c3f5a9d3208ee755072@wordpress.org>
References: <055.264b0dba638f7c3f5a9d3208ee755072@wordpress.org>
Message-ID: <070.6c379baadeda89960e10f01d531b8e51@wordpress.org>

#64393: Change how we include Gutenberg in Core
------------------------------+--------------------------
 Reporter:  youknowriad       |       Owner:  youknowriad
     Type:  task (blessed)    |      Status:  closed
 Priority:  high              |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  blocker           |  Resolution:  fixed
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------

Comment (by desrosj):

 In [changeset:"62329" 62329]:
 {{{
 #!CommitTicketReference repository="" revision="62329"
 Delete the `fixes-64393-restore-version-history` branch.

 This branch has served its purpose and is no longer required. Deleting to
 avoid other potential issues like the one experienced in
 https://make.wordpress.org/systems/2026/05/06/automated-7-0-branch-
 nightly-generation-broken/.

 Props dd32, dmsnell.
 See #64393.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64393#comment:261>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 01:34:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 01:34:08 -0000
Subject: [wp-trac] [WordPress Trac] #54660: Comment is missing for the
 bulk_footer function
In-Reply-To: <057.90c54554c94c7534a909dc1a82c58a86@wordpress.org>
References: <057.90c54554c94c7534a909dc1a82c58a86@wordpress.org>
Message-ID: <072.9d4e63a53263c6c0393d2f6f5933239c@wordpress.org>

#54660: Comment is missing for the bulk_footer function
----------------------------+------------------------------
 Reporter:  yagniksangani   |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:  fixed
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+------------------------------
Changes (by joedolson):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 These are no longer issues; fixed in [58082].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54660#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 01:40:36 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 01:40:36 -0000
Subject: [wp-trac] [WordPress Trac] #13429: Updating Link URL on image
 within Admin with Gallery
In-Reply-To: <052.a24e7a3341b6fb35af544c0c334fa4c6@wordpress.org>
References: <052.a24e7a3341b6fb35af544c0c334fa4c6@wordpress.org>
Message-ID: <067.0029fa55bb9494ffbfa12c0fb60f253c@wordpress.org>

#13429: Updating Link URL on image within Admin with Gallery
-----------------------------------------+-----------------------------
 Reporter:  vshoward                     |       Owner:  (none)
     Type:  defect (bug)                 |      Status:  new
 Priority:  normal                       |   Milestone:  Future Release
Component:  Gallery                      |     Version:  2.9.2
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch 2nd-opinion close  |     Focuses:
-----------------------------------------+-----------------------------
Changes (by joedolson):

 * keywords:  has-patch 2nd-opinion => has-patch 2nd-opinion close


Comment:

 I'd argue that while this hasn't been fixed in the classic editor, it is
 no longer an issue in the block editor, where you can edit the links for
 individual images in a gallery using the Gallery block.

 Recommending to close.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/13429#comment:78>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 01:45:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 01:45:07 -0000
Subject: [wp-trac] [WordPress Trac] #65206: Site Editor: preload initial
 canvas REST data
Message-ID: <054.e66da5fd138b4a58b8bd59be08147558@wordpress.org>

#65206: Site Editor: preload initial canvas REST data
-------------------------+-----------------------------
 Reporter:  extrachill   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Editor       |    Version:  trunk
 Severity:  normal       |   Keywords:  has-patch
  Focuses:  performance  |
-------------------------+-----------------------------
 This ticket tracks the WordPress Core sync/backport for a Gutenberg Site
 Editor preload change.

 The Gutenberg issue/PR are already filed here:

  * https://github.com/WordPress/gutenberg/issues/78074
  * https://github.com/WordPress/gutenberg/pull/78075

 This Core ticket is needed for the corresponding wordpress-develop PR that
 syncs the PHP preload change into {{{src/wp-admin/site-editor.php}}}.

 The Site Editor currently misses several REST API preload paths used
 during the initial editor canvas load, causing avoidable follow-up REST
 requests for individual template part records, Query Loop post
 collections, and public taxonomies.

 Observed late REST routes included:

  * {{{/wp/v2/template-parts/<template-part-id>?context=edit}}}
  *
 {{{/wp/v2/posts?context=edit&offset=0&order=desc&orderby=date&per_page=10&ignore_sticky=false}}}
  *
 {{{/wp/v2/posts?context=edit&offset=0&order=desc&orderby=date&per_page=3&ignore_sticky=false}}}
  * {{{/wp/v2/taxonomies?context=view}}}

 Validation against a Site Editor load benchmark showed the candidate
 reducing measured load time from 1235ms to 914ms (-321ms / -26.0%) and
 eliminating the observed late REST resources (5 -> 0).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65206>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 01:50:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 01:50:29 -0000
Subject: [wp-trac] [WordPress Trac] #19691: Cannot modify admin messages
 for /wp-admin/edit.php
In-Reply-To: <056.9065e80f20c3c6fda9a7d306beae4307@wordpress.org>
References: <056.9065e80f20c3c6fda9a7d306beae4307@wordpress.org>
Message-ID: <071.e837abf434e870103fa29bd87edf45ba@wordpress.org>

#19691: Cannot modify admin messages for /wp-admin/edit.php
------------------------------------------------+---------------------
 Reporter:  mikeschinkel                        |       Owner:  (none)
     Type:  enhancement                         |      Status:  closed
 Priority:  normal                              |   Milestone:
Component:  Administration                      |     Version:  3.3
 Severity:  normal                              |  Resolution:  fixed
 Keywords:  dev-feedback has-patch 2nd-opinion  |     Focuses:
------------------------------------------------+---------------------
Changes (by joedolson):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Since #57791 was resolved, all admin notices are run through
 `wp_admin_notice()` and, correspondingly, through the `wp_admin_notice`
 action and the `wp_admin_notice_args` and `wp_admin_notice_markup`
 filters.

 Other context should be available environmentally, so I think this can be
 closed.

 Feel free to comment or re-open. if there are gaps that still can't be
 achieve.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19691#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 01:58:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 01:58:20 -0000
Subject: [wp-trac] [WordPress Trac] #29299: Plural forms not available
 for some strings
In-Reply-To: <053.9ff6d5b895e831814b541c6770d26c9e@wordpress.org>
References: <053.9ff6d5b895e831814b541c6770d26c9e@wordpress.org>
Message-ID: <068.486f436d50831f1567a064b955dee590@wordpress.org>

#29299: Plural forms not available for some strings
-------------------------------------+-------------------------------------
 Reporter:  pavelevap                |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  7.1
Component:  Options, Meta APIs       |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch 2nd-opinion    |     Focuses:  administration, ui-
  settings-api                       |  copy
-------------------------------------+-------------------------------------
Changes (by joedolson):

 * owner:  SergeyBiryukov => joedolson
 * status:  reviewing => accepted
 * milestone:  Future Release => 7.1


Comment:

 Three of these are still present, and worth addressing: the two
 unassociated strings in `options-reading.php`, and the string about
 comment spam.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/29299#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:05:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:05:50 -0000
Subject: [wp-trac] [WordPress Trac] #30798: Ideas for improvements to to
 wp_die() usages
In-Reply-To: <059.d71e21f54a5dc12a9fee8f032687cacc@wordpress.org>
References: <059.d71e21f54a5dc12a9fee8f032687cacc@wordpress.org>
Message-ID: <074.c7cd9a52e4b2530e4835bf3b010270e6@wordpress.org>

#30798: Ideas for improvements to to wp_die() usages
-----------------------------+---------------------
 Reporter:  johnjamesjacoby  |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  2nd-opinion      |     Focuses:
-----------------------------+---------------------

Comment (by joedolson):

 Many error messages were fixed in [42648], and the phrase 'Cheatin' uh?'
 no longer appears in the codebase.

 @johnjamesjacoby There are undoubtedly still cases where the error
 messages are unhelpful, but I think a significant volume of the problem
 has been improved; do you think this still needs to stay open?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/30798#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:06:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:06:44 -0000
Subject: [wp-trac] [WordPress Trac] #30798: Ideas for improvements to to
 wp_die() usages
In-Reply-To: <059.d71e21f54a5dc12a9fee8f032687cacc@wordpress.org>
References: <059.d71e21f54a5dc12a9fee8f032687cacc@wordpress.org>
Message-ID: <074.cd4da1c158f692305b2536c3cfc348a3@wordpress.org>

#30798: Ideas for improvements to to wp_die() usages
-------------------------------+---------------------
 Reporter:  johnjamesjacoby    |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:
Component:  General            |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  2nd-opinion close  |     Focuses:
-------------------------------+---------------------
Changes (by joedolson):

 * keywords:  2nd-opinion => 2nd-opinion close


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/30798#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:10:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:10:05 -0000
Subject: [wp-trac] [WordPress Trac] #31980: Customizer Theme Switcher
 Details Modal: previous/next/close buttons require double taps on IOS
In-Reply-To: <056.05f0de3c36e5a122f27ce2726b5fb37e@wordpress.org>
References: <056.05f0de3c36e5a122f27ce2726b5fb37e@wordpress.org>
Message-ID: <071.88035d4376fca278eda64db5bcd64661@wordpress.org>

#31980: Customizer Theme Switcher Details Modal: previous/next/close buttons
require double taps on IOS
-------------------------------------------+-------------------------
 Reporter:  DrewAPicture                   |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  closed
 Priority:  normal                         |   Milestone:
Component:  Customize                      |     Version:  4.2
 Severity:  normal                         |  Resolution:  worksforme
 Keywords:  needs-patch reporter-feedback  |     Focuses:  ui
-------------------------------------------+-------------------------
Changes (by joedolson):

 * status:  new => closed
 * resolution:   => worksforme
 * milestone:  Future Release =>


Comment:

 Confirmed that this is no longer an issue; closing.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/31980#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:11:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:11:16 -0000
Subject: [wp-trac] [WordPress Trac] #64393: Change how we include
 Gutenberg in Core
In-Reply-To: <055.264b0dba638f7c3f5a9d3208ee755072@wordpress.org>
References: <055.264b0dba638f7c3f5a9d3208ee755072@wordpress.org>
Message-ID: <070.43f22697bca989c29ed44a3af845b587@wordpress.org>

#64393: Change how we include Gutenberg in Core
------------------------------+--------------------------
 Reporter:  youknowriad       |       Owner:  youknowriad
     Type:  task (blessed)    |      Status:  closed
 Priority:  high              |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  blocker           |  Resolution:  fixed
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------

Comment (by desrosj):

 In [changeset:"62330" 62330]:
 {{{
 #!CommitTicketReference repository="" revision="62330"
 Build/Test Tools: Remove `gutenberg:verify` script on `postinstall`.

 In [61458], a `postinstall` script was introduced that ensured the source
 code from the `gutenberg` repository was present before attempting to run
 the build script.

 The WordPress.org Hosting Tests surfaced an edge case where the
 `postinstall` script was failing when `nodevenv` is used. Because it
 serves as a wrapper for Node.js, `NPM_CONFIG_PREFIX` is set to the virual
 envirnoment directory and not the actual project source directory.

 This removes `gutenberg:verify` from `postinstall` entirely.
 `gutenberg:verify` is responsible for confirming that the `gutenberg`
 directory exists, that the commit SHA value in `gutenberg/.gutenberg-hash`
 matches `gutenberg.sha` in the `package.json` file, and it downloads a
 fresh copy if not.

 While this will result in the necessary files not being present locally
 after running `npm install`, `gutenberg:verify` is specified as the first
 task executed when the `build` and `build:dev` scripts are run. Running
 either build script has been a requirement to run WordPress locally for
 some time now, so this does not introduce a new required step. It simply
 delays when the built asset will be retrieved from the GitHub Container
 Registry when necessary.

 `postinstall` scripts should also be avoided entirely due to their
 significantly insecure nature (see #64543).

 Follow up to [61492], [61873], and [62021].

 Reviewed by jorbin.
 Merges [62321] to the 7.0.

 Props jorbin, johnbillion, desrosj.
 Fixes #64874. See #64393, #64543.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64393#comment:262>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:11:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:11:16 -0000
Subject: [wp-trac] [WordPress Trac] #64874: `postinstall` scripts are
 failing in some environments
In-Reply-To: <051.f17b58ad2a5d24c0f8bb62395bfd934d@wordpress.org>
References: <051.f17b58ad2a5d24c0f8bb62395bfd934d@wordpress.org>
Message-ID: <066.bb1260e1131b562e9724aa540e27219e@wordpress.org>

#64874: `postinstall` scripts are failing in some environments
-------------------------------------------------+-------------------------
 Reporter:  desrosj                              |       Owner:  desrosj
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Build/Test Tools                     |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch commit fixed-major dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62330" 62330]:
 {{{
 #!CommitTicketReference repository="" revision="62330"
 Build/Test Tools: Remove `gutenberg:verify` script on `postinstall`.

 In [61458], a `postinstall` script was introduced that ensured the source
 code from the `gutenberg` repository was present before attempting to run
 the build script.

 The WordPress.org Hosting Tests surfaced an edge case where the
 `postinstall` script was failing when `nodevenv` is used. Because it
 serves as a wrapper for Node.js, `NPM_CONFIG_PREFIX` is set to the virual
 envirnoment directory and not the actual project source directory.

 This removes `gutenberg:verify` from `postinstall` entirely.
 `gutenberg:verify` is responsible for confirming that the `gutenberg`
 directory exists, that the commit SHA value in `gutenberg/.gutenberg-hash`
 matches `gutenberg.sha` in the `package.json` file, and it downloads a
 fresh copy if not.

 While this will result in the necessary files not being present locally
 after running `npm install`, `gutenberg:verify` is specified as the first
 task executed when the `build` and `build:dev` scripts are run. Running
 either build script has been a requirement to run WordPress locally for
 some time now, so this does not introduce a new required step. It simply
 delays when the built asset will be retrieved from the GitHub Container
 Registry when necessary.

 `postinstall` scripts should also be avoided entirely due to their
 significantly insecure nature (see #64543).

 Follow up to [61492], [61873], and [62021].

 Reviewed by jorbin.
 Merges [62321] to the 7.0.

 Props jorbin, johnbillion, desrosj.
 Fixes #64874. See #64393, #64543.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64874#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:11:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:11:16 -0000
Subject: [wp-trac] [WordPress Trac] #64543: Implement `ignore-scripts`
 to harden npm usage
In-Reply-To: <055.6dcb52fa376eb7fffd4085d384323858@wordpress.org>
References: <055.6dcb52fa376eb7fffd4085d384323858@wordpress.org>
Message-ID: <070.09ad307de54e9e4028fd5f8e9d4d7f9e@wordpress.org>

#64543: Implement `ignore-scripts` to harden npm usage
------------------------------+------------------------------
 Reporter:  johnbillion       |       Owner:  (none)
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:  javascript
------------------------------+------------------------------

Comment (by desrosj):

 In [changeset:"62330" 62330]:
 {{{
 #!CommitTicketReference repository="" revision="62330"
 Build/Test Tools: Remove `gutenberg:verify` script on `postinstall`.

 In [61458], a `postinstall` script was introduced that ensured the source
 code from the `gutenberg` repository was present before attempting to run
 the build script.

 The WordPress.org Hosting Tests surfaced an edge case where the
 `postinstall` script was failing when `nodevenv` is used. Because it
 serves as a wrapper for Node.js, `NPM_CONFIG_PREFIX` is set to the virual
 envirnoment directory and not the actual project source directory.

 This removes `gutenberg:verify` from `postinstall` entirely.
 `gutenberg:verify` is responsible for confirming that the `gutenberg`
 directory exists, that the commit SHA value in `gutenberg/.gutenberg-hash`
 matches `gutenberg.sha` in the `package.json` file, and it downloads a
 fresh copy if not.

 While this will result in the necessary files not being present locally
 after running `npm install`, `gutenberg:verify` is specified as the first
 task executed when the `build` and `build:dev` scripts are run. Running
 either build script has been a requirement to run WordPress locally for
 some time now, so this does not introduce a new required step. It simply
 delays when the built asset will be retrieved from the GitHub Container
 Registry when necessary.

 `postinstall` scripts should also be avoided entirely due to their
 significantly insecure nature (see #64543).

 Follow up to [61492], [61873], and [62021].

 Reviewed by jorbin.
 Merges [62321] to the 7.0.

 Props jorbin, johnbillion, desrosj.
 Fixes #64874. See #64393, #64543.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64543#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:13:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:13:54 -0000
Subject: [wp-trac] [WordPress Trac] #32750: If changing the checkbox
 state "organize my uploads..." in the media preferences the thumbnails
 aren't shown anymore
In-Reply-To: <063.bc372c88cecee94d47b96340a4a8f3a4@wordpress.org>
References: <063.bc372c88cecee94d47b96340a4a8f3a4@wordpress.org>
Message-ID: <078.d1c052332d44edc7d3bd8ab06a49f48b@wordpress.org>

#32750: If changing the checkbox state "organize my uploads..." in the media
preferences the thumbnails aren't shown anymore
---------------------------------+-------------------------
 Reporter:  anonymized_13423376  |       Owner:  (none)
     Type:  defect (bug)         |      Status:  closed
 Priority:  normal               |   Milestone:
Component:  Media                |     Version:  4.2.2
 Severity:  normal               |  Resolution:  worksforme
 Keywords:  reporter-feedback    |     Focuses:
---------------------------------+-------------------------
Changes (by joedolson):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 As of 2026, I'm unable to reproduce this issue. Given the length of time
 since the report and the lack of follow-up since then, I don't believe
 this is currently an issue.

 Closing; feel free to comment or re-open if this is still a problem.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32750#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:21:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:21:11 -0000
Subject: [wp-trac] [WordPress Trac] #64984: reply needs gettext
In-Reply-To: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
References: <052.8e2371a87eccd18086892c909f989418@wordpress.org>
Message-ID: <067.eb639b6420e7f4223ce66a8d4bf5b93f@wordpress.org>

#64984: reply needs gettext
--------------------------------------------------+-----------------------
 Reporter:  timse201                              |       Owner:  audrasjb
     Type:  defect (bug)                          |      Status:  closed
 Priority:  normal                                |   Milestone:  7.0
Component:  I18N                                  |     Version:  trunk
 Severity:  normal                                |  Resolution:  fixed
 Keywords:  fixed-major dev-reviewed i18n-change  |     Focuses:
--------------------------------------------------+-----------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62331" 62331]:
 {{{
 #!CommitTicketReference repository="" revision="62331"
 I18N: Add translator context to the use of "Reply".

 Reviewed by audrasjb, desrosj.
 Merges [62324] to the 7.0 branch.

 Props timse201, audrasjb, sanketparmar, jorbin, desrosj.
 Fixes #64984.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64984#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:21:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:21:41 -0000
Subject: [wp-trac] [WordPress Trac] #65138: RTC: Real-time collaboration
 bug sprint for 7.0
In-Reply-To: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
References: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
Message-ID: <066.038e637593d649cd6f909f9c0b890bc9@wordpress.org>

#65138: RTC: Real-time collaboration bug sprint for 7.0
-------------------------------------------------+-------------------------
 Reporter:  dmsnell                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests gutenberg-  |     Focuses:  tests
  merge                                          |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  has-patch has-unit-tests gutenberg-merge fixed-major dev-
     reviewed => has-patch has-unit-tests gutenberg-merge


Comment:

 In light of the decision to not ship RTC, I am withdrawing my review for
 backporting and noting that this needs to be reverted.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65138#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:23:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:23:59 -0000
Subject: [wp-trac] [WordPress Trac] #35651: No longer any consistent way
 to add content to bottom of comments form
In-Reply-To: <053.9ff848006595292165dcba3ca102f3e6@wordpress.org>
References: <053.9ff848006595292165dcba3ca102f3e6@wordpress.org>
Message-ID: <068.31d3004e797491bd75bb6c730c709a14@wordpress.org>

#35651: No longer any consistent way to add content to bottom of comments form
-------------------------------------------------+-------------------------
 Reporter:  smerriman                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  Comments                             |     Version:  4.4
 Severity:  normal                               |  Resolution:
 Keywords:  2nd-opinion has-patch has-           |     Focuses:
  screenshots close                              |
-------------------------------------------------+-------------------------
Changes (by joedolson):

 * keywords:  2nd-opinion has-patch has-screenshots => 2nd-opinion has-patch
     has-screenshots close


Comment:

 There was a filter added in 4.2.0, `comment_form_submit_button`, that
 allows you to filter the submit button itself. This should make it fully
 manageable to insert fields above the submit button in the HTML of that
 return value.

 Is there any reason that filter isn't viable for what's being discussed
 here?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35651#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:25:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:25:02 -0000
Subject: [wp-trac] [WordPress Trac] #35793: Something Wrong with UI in
 Administration
In-Reply-To: <051.290ef60d687ade9a1854cb218eacb3fc@wordpress.org>
References: <051.290ef60d687ade9a1854cb218eacb3fc@wordpress.org>
Message-ID: <066.b008e55407f03f6faefda8ca1ddc881c@wordpress.org>

#35793: Something Wrong with UI in Administration
-------------------------------+-------------------------
 Reporter:  zjhzxhz            |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Administration     |     Version:
 Severity:  normal             |  Resolution:  worksforme
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+-------------------------
Changes (by joedolson):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 With no follow-up, this seems likely to be a one-off error or an extender
 conflict.

 Closing. Feel free to comment or re-open if this is still a concern.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35793#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:28:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:28:46 -0000
Subject: [wp-trac] [WordPress Trac] #35837: The auto-update in media
 editor rewrites user inputs
In-Reply-To: <050.2d661bd6f391610a908a6e16bb5708b4@wordpress.org>
References: <050.2d661bd6f391610a908a6e16bb5708b4@wordpress.org>
Message-ID: <065.39867b24985819db3095506f18347ddb@wordpress.org>

#35837: The auto-update in media editor rewrites user inputs
-----------------------------+---------------------------------------------
 Reporter:  o----o           |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Media            |     Version:  4.4.2
 Severity:  normal           |  Resolution:  fixed
 Keywords:  reporter-        |     Focuses:  ui, javascript, administration
  feedback                   |
-----------------------------+---------------------------------------------
Changes (by joedolson):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 The video is no longer available, but this sounds similar to an issue
 resolved in [55299].

 Closing, as I believe this is resolved. Feel free to comment or re-open if
 you feel this is still a concern.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35837#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:36:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:36:28 -0000
Subject: [wp-trac] [WordPress Trac] #40688: there is a bug in deleting a
 photo and replacing it by the new photo with the same name
In-Reply-To: <057.8efa491915bccb75a478c8c9992d10c6@wordpress.org>
References: <057.8efa491915bccb75a478c8c9992d10c6@wordpress.org>
Message-ID: <072.d2c66b2917c8f378675fcb588a30454b@wordpress.org>

#40688: there is a bug in deleting a photo and replacing it by the new photo with
the same name
-------------------------------+-------------------------
 Reporter:  Navid.abazari      |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Media              |     Version:  4.7.4
 Severity:  normal             |  Resolution:  worksforme
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+-------------------------
Changes (by joedolson):

 * status:  new => closed
 * resolution:   => worksforme
 * milestone:  Awaiting Review =>


Comment:

 With no follow-up, I'm inclined to close this as 'worksforme'. Please feel
 free to comment if you feel this is still an issue that needs to be
 addressed.

 However, based on the description, it sounds like either a situation that
 WordPress doesn't address (replacing image URLs when an image is replaced)
 or a caching issue, as even if you replace an image with one of the same
 name, your browser may still deliver the previous image temporarily, due
 to browser caching.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40688#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:49:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:49:20 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.2412d048414fd7b060de1c413bb55966@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests                           |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-screenshots admin-reskin has-patch has-unit-tests 2nd-
     opinion => has-screenshots admin-reskin has-patch has-unit-tests


Comment:

 Replying to [comment:49 jorbin]:
 > Each of these proposed solutions is a fairly large, and we are only two
 days away from the new beta 1.  I think reverting [62025] and punting this
 to 7.1 is the safest solution.

 I tend to agree with this. Since this element has not matched the color
 scheme in the past, I think it's not surprising to a user if it does not
 after updating. Reverting gives us more time to find a better solution to
 this.

 If we could find a minimal way to change the admin bar solely in the admin
 and leave it as it was in 6.9 on the front end for 7.0, I think that I
 would be in favor of that as an incremental step. But given that we're now
 less than 24 hours from the next pre-release, it's getting down to the
 wire.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:50>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 02:50:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 02:50:11 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time
 Collaboration from WordPress Core
In-Reply-To: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
References: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
Message-ID: <065.bf86ec91c1ad7c3b9e2ae8198cf284d3@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
-----------------------------+---------------------
 Reporter:  jorbin           |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  highest omg bbq  |   Milestone:  7.0
Component:  Editor           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+---------------------

Comment (by jorbin):

 The second piece of this work will be removing all of the code from
 Gutenbeg so when the hash is updated, none of the client side RTC code
 ships with core.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 03:04:56 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 03:04:56 -0000
Subject: [wp-trac] [WordPress Trac] #34753: Remove use of "Toggle" in
 strings
In-Reply-To: <048.5754bd53bdeffca661dc3ecceed5ae57@wordpress.org>
References: <048.5754bd53bdeffca661dc3ecceed5ae57@wordpress.org>
Message-ID: <063.ec5976efc3d76ce0949e711d1c17686c@wordpress.org>

#34753: Remove use of "Toggle" in strings
-------------------------------------+-------------------------------------
 Reporter:  xibe                     |       Owner:  joedolson
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  7.1
Component:  Administration           |     Version:  4.4
 Severity:  normal                   |  Resolution:
 Keywords:  dev-feedback has-        |     Focuses:  ui, javascript, ui-
  screenshots                        |  copy
-------------------------------------+-------------------------------------
Changes (by joedolson):

 * owner:  (none) => joedolson
 * status:  new => accepted
 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/34753#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 04:52:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 04:52:38 -0000
Subject: [wp-trac] [WordPress Trac] #64439: Add admin download
 functionality for themes in wp-admin
In-Reply-To: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
References: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
Message-ID: <074.835ff49d779120e6a335cd51f6e8376b@wordpress.org>

#64439: Add admin download functionality for themes in wp-admin
------------------------------------------+------------------------------
 Reporter:  solankisoftware               |       Owner:  (none)
     Type:  enhancement                   |      Status:  new
 Priority:  normal                        |   Milestone:  Awaiting Review
Component:  Themes                        |     Version:
 Severity:  normal                        |  Resolution:
 Keywords:  2nd-opinion needs-unit-tests  |     Focuses:  administration
------------------------------------------+------------------------------
Changes (by sanayasir):

 * Attachment "Download button on wordpress Playground.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64439>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 04:53:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 04:53:18 -0000
Subject: [wp-trac] [WordPress Trac] #64439: Add admin download
 functionality for themes in wp-admin
In-Reply-To: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
References: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
Message-ID: <074.4e9a911f3be8ed93afe5548bd4922c5d@wordpress.org>

#64439: Add admin download functionality for themes in wp-admin
-----------------------------+------------------------------------------
 Reporter:  solankisoftware  |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Themes           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  administration, performance
-----------------------------+------------------------------------------
Changes (by sanayasir):

 * keywords:  2nd-opinion needs-unit-tests => has-patch
 * focuses:  administration => administration, performance


Comment:

 Hi, I’m Sana Yasir, and I’m new to WordPress Core contribution. Thank you
 to everyone for the helpful discussions and contributions on this ticket.

 **Test Report**

 I tested the latest patch on both WordPress Playground and a local
 WordPress setup.

 Environment:

 * WordPress trunk / latest nightly
 * Default theme
 * No active plugins

 Results:
 ✅ The “Download Theme” button appears correctly in the Theme File Editor
 screen.
 ✅ Clicking the button successfully downloads the selected theme as a ZIP
 file.
 ✅ The downloaded ZIP extracts properly and contains all expected theme
 files.
 ✅ I tested with both active and inactive themes, and the functionality
 worked as expected.
 ✅ I did not notice any PHP warnings, notices, or UI issues during
 testing.

 UX Feedback:
 The current placement of the Download Theme button in the Theme File
 Editor feels appropriate and user-friendly. It is easy to discover and
 works well alongside the existing editor actions.

 I also tested this feature in WordPress Playground, and the download
 functionality behaved correctly there as well.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64439#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 05:27:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 05:27:06 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.601d39b5110e0b525a0537608d741a88@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
---------------------------+--------------------------
 Reporter:  jonsurrell     |       Owner:  westonruter
     Type:  defect (bug)   |      Status:  accepted
 Priority:  high           |   Milestone:  7.0
Component:  Script Loader  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+--------------------------
Changes (by westonruter):

 * owner:  (none) => westonruter
 * status:  new => accepted


Comment:

 I've followed up
 [https://github.com/WordPress/gutenberg/issues/78041#issuecomment-4401603045
 on the Gutenberg issue] and aforementioned
 [https://github.com/WordPress/ai/pull/482#discussion_r3182513240 on the AI
 issue], but I haven't yet dug into this ticket specifically. Neither of
 those seem to be directly related to the `module_dependencies` arg for
 registering scripts.

 My plan is to continue following up on this tomorrow.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 06:24:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 06:24:48 -0000
Subject: [wp-trac] [WordPress Trac] #65111: Twenty Sixteen: Center text
 in image captions
In-Reply-To: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
References: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
Message-ID: <071.7fe9e133e8207f81304b5d1239cace26@wordpress.org>

#65111: Twenty Sixteen: Center text in image captions
-----------------------------------------+------------------------------
 Reporter:  gaelbonithon                 |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Bundled Theme                |     Version:  4.4
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch close 2nd-opinion  |     Focuses:  css
-----------------------------------------+------------------------------
Changes (by sabernhardt):

 * keywords:  has-patch close => has-patch close 2nd-opinion


Comment:

 I almost closed the ticket, but I thought of another possibility to
 consider first.

 To add a control for the **user** to select text alignment, a block style
 variation could be added in `twentysixteen_setup()`.

 {{{
 register_block_style(
         'core/image',
         array(
                 'name'         => 'caption-center',
                 'label'        => __( 'Text align center', 'twentysixteen'
 ),
                 'inline_style' => '.wp-block-image.is-style-caption-center
 figcaption { text-align: center; }',
         )
 );
 }}}

 It still would not be available for someone who wants the Rounded style,
 and it is not as efficient as creating a control for use with any theme
 (GB12997).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65111#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 06:25:09 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 06:25:09 -0000
Subject: [wp-trac] [WordPress Trac] #65111: Twenty Sixteen: Center text
 in image captions
In-Reply-To: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
References: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
Message-ID: <071.ebf4a278766658b9759138cd502e6fa0@wordpress.org>

#65111: Twenty Sixteen: Center text in image captions
-----------------------------------------+------------------------------
 Reporter:  gaelbonithon                 |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Bundled Theme                |     Version:  4.4
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch close 2nd-opinion  |     Focuses:  css
-----------------------------------------+------------------------------
Changes (by sabernhardt):

 * Attachment "image-block-style-text-center.png" added.

 Block style variation for centering caption text in the theme

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65111>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 06:49:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 06:49:53 -0000
Subject: [wp-trac] [WordPress Trac] #65190: Add komoot to the oEmbed
 provider allowlist
In-Reply-To: <057.3ad57a6099d748d11f937c1077d560cb@wordpress.org>
References: <057.3ad57a6099d748d11f937c1077d560cb@wordpress.org>
Message-ID: <072.55ce44c28b833d4ef28a653f51228e5e@wordpress.org>

#65190: Add komoot to the oEmbed provider allowlist
---------------------------+------------------------------
 Reporter:  federicofonta  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Embeds         |     Version:
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by sukhendu2002):

 Hi @federicofonta , welcome to WordPress Trac.

 We have a dedicated oEmbed questionnaire. Can you please answer the
 questions from ​[https://make.wordpress.org/core/handbook/contribute
 /design-decisions/#adding-new-oembed-providers Adding new oEmbed
 providers]?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65190#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 07:05:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 07:05:16 -0000
Subject: [wp-trac] [WordPress Trac] #65111: Twenty Sixteen: Center text
 in image captions
In-Reply-To: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
References: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
Message-ID: <071.c44c0a441cbf996a45ca97bfc0f321dc@wordpress.org>

#65111: Twenty Sixteen: Center text in image captions
-----------------------------------------+------------------------------
 Reporter:  gaelbonithon                 |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Bundled Theme                |     Version:  4.4
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch close 2nd-opinion  |     Focuses:  css
-----------------------------------------+------------------------------

Comment (by gaelbonithon):

 Yeah, that would be nice, although it would obviously be better to have
 that option regardless of the theme (along with the other alignment
 options, at least right-aligned). Patch updated.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65111#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 07:27:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 07:27:52 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.068973e949b1fcb51c2c0b00239e3e37@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by fcoveram):

 Thanks for the heads up @peterwilsoncc. I will work on this now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 08:01:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 08:01:10 -0000
Subject: [wp-trac] [WordPress Trac] #58223: Twenty Twenty:
 twentytwenty_get_post_meta needs global $has_meta
In-Reply-To: <054.8dc5e2859238efe95951a70357db46d6@wordpress.org>
References: <054.8dc5e2859238efe95951a70357db46d6@wordpress.org>
Message-ID: <069.f2dae5f8d396567896b6fd3851acbd86@wordpress.org>

#58223: Twenty Twenty: twentytwenty_get_post_meta needs global $has_meta
---------------------------+------------------------------
 Reporter:  chiefastro     |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  template
---------------------------+------------------------------

Comment (by shreya0shrivastava):

 Hi, I've submitted a patch for this issue.

 The root cause is that `$has_meta` is a local flag that only flips to
 `true` when default meta fields are present, meaning the output buffer
 from the action hooks gets discarded when no default meta exists.

 Rather than using a global (which would pollute the global namespace and
 create implicit coupling), the fix checks whether the output buffer
 contains any content after stripping tags, and returns the meta wrapper if
 either default meta or hook content is present.

 Happy to make any changes based on feedback.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/58223#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 08:11:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 08:11:21 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.960742f1be224065dbf5f8818e217df9@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
---------------------------+--------------------------
 Reporter:  jonsurrell     |       Owner:  westonruter
     Type:  defect (bug)   |      Status:  accepted
 Priority:  high           |   Milestone:  7.0
Component:  Script Loader  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+--------------------------

Comment (by jonsurrell):

 Replying to [comment:7 jorbin]:
 > > This ties in with some thoughts I have about private modules. I'd like
 to be careful and judicious about what modules Core exposes and espree may
 not make a lot of sense as a Core module.
 >
 > Could you go into a little more details about what you are thinking
 here? What are the risks associated with espree being available outside of
 core?

 The general idea is that any modules exposed by Core become part of the
 WordPress public API. Then it's much more difficult to modify them in any
 way due to backwards compatibility concerns.

 To use `espree` in a hypothetical example, the latest version is `11.2.0`.
 If version `12.0.0` comes out soon and is full of nice improvements and
 breaking changes, then Core has a difficult decision to make if it wants
 to upgrade. Assuming `espree at 11.2.0` has become part of Core's public API,
 can Core upgrade without breaking a backwards compatibility? Does it need
 to add `espree12` as another Core module and leave `espree` as the v11
 module indefinitely?

 I don't think WordPress Core actually has any business providing an
 `espree` module for extenders. Exposing it as a Core module is really an
 undesired effect of the current limitations of WordPress' module system.

 I'd like to expose some modules as "Core-only" by scoping them to be
 available only to Core. [https://developer.mozilla.org/en-
 US/docs/Web/HTML/Reference/Elements/script/type/importmap#scoped_module_specifier_mapsThis
 can be achieved technically by using importmap scopes:]

 {{{#!xml
 <script type="importmap">
   {
     "imports": {
       "…no espree here…": "…"
     },
     "scopes": {
       "/wp-includes/js/": {
         "espree": "/path/to/espree.js?v=123"
       }
     }
   }
 </script>
 }}}

 This makes it clear that `espree` is private, it's only exposed to
 JavaScript under the `/wp-includes/js/` path. Extenders cannot access it.
 `espree` is clearly private and there are no longer backwards
 compatibility concers. Core is free to update, change, or remove it at any
 time in the future.

 A more interesting case than espree is when considering syntax
 highlighting for code editors. It's a similar situation where I don't
 think Core has any desire to expose a code editor library to extenders,
 but does have reason to use one internally. A code editor library is more
 likely to bundle functionality and it would be good to have flexibility to
 change the exposed functionality or split up the bundle in different ways
 to optimize its size or loading characteristics.

 There are a number of tricky questions to work out, like scoped modules
 that may be served from a CDN or how a private modules API could be
 exposed to extenders. For most extenders, there's likely littler reason to
 use private modules and the global `imports: {}` is fine. However, I
 suspect framework-like plugins would likely find private modules useful to
 differentiate their public modules from internal, private ones.

 This is worth a ticket of its own, but I'm glad to share these ideas 🙂

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 08:34:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 08:34:16 -0000
Subject: [wp-trac] [WordPress Trac] #65190: Add komoot to the oEmbed
 provider allowlist
In-Reply-To: <057.3ad57a6099d748d11f937c1077d560cb@wordpress.org>
References: <057.3ad57a6099d748d11f937c1077d560cb@wordpress.org>
Message-ID: <072.90c5dc90219a0b18a4a040cf8bc0cc2b@wordpress.org>

#65190: Add komoot to the oEmbed provider allowlist
---------------------------+------------------------------
 Reporter:  federicofonta  |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Embeds         |     Version:
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Changes (by federicofonta):

 * type:  defect (bug) => enhancement


Comment:

 Thanks @sukhendu2002!

 Answers to the oEmbed provider questionnaire:

 **Is the service well-established, popular, and mainstream?**

 Yes. komoot is a long-running route-planning and outdoor navigation
 platform for hiking, cycling, bike touring, gravel, MTB, and running. It
 is widely used in Europe and internationally, with public route,
 smarttour, collection, and guide pages that are commonly linked from
 blogs, destination pages, tourism sites, clubs, and local businesses.

 **How does it compare to similar supported services?**

 For outdoor route/location content, komoot is comparable in role to other
 map/media providers already supported by WordPress oEmbed: it provides
 rich, interactive embeddable content that is useful in editorial posts and
 travel/outdoor guides. The embed is a hosted iframe, so WordPress sites do
 not need to run any komoot code directly.

 **Does the service have an established social media presence?**

 Yes. komoot maintains official channels and a broad user/community
 presence across major social platforms.

 **Is the oEmbed endpoint clearly established and documented?**

 Yes. The endpoint is live at:

 https://www.komoot.com/oembed

 Example:

 https://www.komoot.com/oembed?url=https%3A%2F%2Fwww.komoot.com%2Ftour%2F2766645113&format=json

 It follows the oEmbed JSON flow and returns `type=rich`, `version=1.0`,
 `provider_name`, `provider_url`, `cache_age`, `width`, `height`, and
 `html` containing an iframe. For tours and smarttours it also returns
 thumbnail fields.

 Supported URL families are intentionally scoped to public embeddable
 content:

 - `https://www.komoot.com/tour/<id>`
 - `https://www.komoot.com/smarttour/<id>`
 - `https://www.komoot.com/collection/<id>(/<slug>)?`
 - `https://www.komoot.com/guide/<id>(/<slug>)?`

 The endpoint also supports localized komoot TLDs and locale-prefixed
 paths.

 **Does the endpoint work with WordPress oEmbed auto-discovery?**

 Yes. Canonical embeddable pages include a discovery tag such as:

 {{{
 <link rel="alternate" type="application/json+oembed"
 href="https://www.komoot.com/oembed?url=..." title="..." />
 }}}

 This was verified in production on:

 https://www.komoot.com/tour/2766645113

 The discovery tag is not rendered on iframe pages or noindex/private
 pages.

 **Does the service make an effort to build relationships with developers,
 such as through robust APIs?**

 Yes. komoot exposes public embed URLs and public share URLs for
 route/collection/guide content. The oEmbed endpoint was added specifically
 to support standard publishing workflows and avoid custom WordPress
 plugins or manual iframe copy-paste.

 **How old is the service?**

 komoot has been operating for well over a decade.

 **Does it have a well-established Wikipedia article?**

 Yes:

 https://en.wikipedia.org/wiki/Komoot

 **Has anyone written a WordPress plugin that leverages the service?**

 There are third-party WordPress plugins and site-specific integrations
 that embed or link komoot content, but the current common workflow is
 manual iframe copy-paste. Adding komoot as a trusted oEmbed provider would
 make this native for WordPress users and avoid per-site plugin
 requirements.

 **Is the provider frequently proposed?**

 This ticket is being opened by komoot after shipping and verifying a
 production oEmbed endpoint. The intended use case is common among
 travel/outdoor WordPress publishers: paste a public komoot route,
 smarttour, collection, or guide URL and get an interactive embed.

 **Security / trust notes**

 The oEmbed response returns a komoot-hosted iframe. The endpoint does not
 fetch arbitrary upstream data or proxy third-party HTML. It only accepts
 known komoot URL shapes and returns `404` for unsupported URLs, including
 highlights and user/profile pages. The iframe route remains the
 visibility/auth boundary for private or unavailable content.

 Production smoke checks completed:

 - Tour oEmbed: `200`
 - Tour discovery tag: present
 - Tour iframe route: `200`
 - Collection oEmbed: `200`
 - Guide oEmbed: `200`
 - Highlight oEmbed: `404` as unsupported

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65190#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 08:52:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 08:52:01 -0000
Subject: [wp-trac] [WordPress Trac] #63017: Compression via PHP
 documented and in URL but not used anymore
In-Reply-To: <054.f15abf26659e994b306c244b2336980e@wordpress.org>
References: <054.f15abf26659e994b306c244b2336980e@wordpress.org>
Message-ID: <069.1cbc0cc2e8c113dae7efeb59fa545dbf@wordpress.org>

#63017: Compression via PHP documented and in URL but not used anymore
--------------------------------------+-----------------------------
 Reporter:  zodiac1978                |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Future Release
Component:  Script Loader             |     Version:  5.0
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch needs-dev-note  |     Focuses:
--------------------------------------+-----------------------------

Comment (by dpknauss):

 I opened a related documentation-focused PR (https://github.com/WordPress
 /Advanced-administration-handbook/pull/485) to clarify the current
 `WP_CACHE` behavior and distinguish page cache vs. object cache semantics.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63017#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 09:12:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 09:12:19 -0000
Subject: [wp-trac] [WordPress Trac] #63017: Compression via PHP
 documented and in URL but not used anymore
In-Reply-To: <054.f15abf26659e994b306c244b2336980e@wordpress.org>
References: <054.f15abf26659e994b306c244b2336980e@wordpress.org>
Message-ID: <069.1282f26582db063434a19563eb5771e9@wordpress.org>

#63017: Compression via PHP documented and in URL but not used anymore
--------------------------------------+-----------------------------
 Reporter:  zodiac1978                |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Future Release
Component:  Script Loader             |     Version:  5.0
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch needs-dev-note  |     Focuses:
--------------------------------------+-----------------------------
Changes (by dpknauss):

 * Attachment "63017-small-core-clarification.diff" added.

 Small Core clarification patch: comments/docblocks, bootstrap clarity, and
 tests; no behavior changes intended.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63017>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 10:00:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 10:00:32 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.ef3a32e4121cbe66573edfd0b1d6a0e2@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests                           |
-------------------------------------------------+-------------------------

Comment (by wildworks):

 One drawback of reverting [62025] is that it causes a color theme mismatch
 between the frontend and backend. Specifically, the backend will use
 modern colors while the frontend will be stuck with the legacy fresh
 colors. This default color discrepancy did not occur in 6.9. As a more
 conservative approach, I've tried a PR that simply changes the frontend
 color theme to modern colors.

 https://github.com/WordPress/wordpress-develop/pull/11771

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 10:17:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 10:17:06 -0000
Subject: [wp-trac] [WordPress Trac] #42187: Multisite - Wordpress
 Importer Unavailable
In-Reply-To: <052.80a478b660468f8139173229a1c9b273@wordpress.org>
References: <052.80a478b660468f8139173229a1c9b273@wordpress.org>
Message-ID: <067.1200542c195a956a29a02657581708c1@wordpress.org>

#42187: Multisite - Wordpress Importer Unavailable
--------------------------------+----------------------------------------
 Reporter:  dtiziani            |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Networks and Sites  |     Version:  4.8.2
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:  administration, multisite
--------------------------------+----------------------------------------

Comment (by realloc):

 I tested the ticket and I can confirm that as a Site Admin, you initially
 get the following content:


 > **Import**
 >
 > If you have posts or comments in another system, WordPress can import
 those into this site. To get started, choose a system to import from
 below:
 > No importers are available.

 After the Network Admin installs the WordPress Importer plugin, the Site
 Admin still gets the same error message. Only after the Network Admin has
 opened the Importer once does the Site Admin finally gain access to use
 it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42187#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 10:18:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 10:18:22 -0000
Subject: [wp-trac] [WordPress Trac] #65169: support attachment pages is
 disabled by default since 6.4,
 so why then offer image be viewed in attachment pages?
In-Reply-To: <057.7df136539a2d43e5cd9542bd9d0d8404@wordpress.org>
References: <057.7df136539a2d43e5cd9542bd9d0d8404@wordpress.org>
Message-ID: <072.3281d16971c1d8e454efdd213dc93b50@wordpress.org>

#65169: support attachment pages is disabled by default since 6.4, so why then
offer image be viewed in attachment pages?
--------------------------------------+------------------------------
 Reporter:  ignatiusjeroe             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  General                   |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  template
--------------------------------------+------------------------------

Comment (by shreyasikhar26):

 I have created a PR here https://github.com/WordPress/wordpress-
 develop/pull/11772 to respect the option `wp_attachment_pages_enabled` in
 both the editor permalink UI and Media Library templates.

 I want to know if we need to add a setting to manually enable/disable
 attachment pages which will control the `wp_attachment_pages_enabled`
 option value.

 Also, we will need similar changes on the gutenberg codebase. I will be
 working on that.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65169#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 10:19:40 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 10:19:40 -0000
Subject: [wp-trac] [WordPress Trac] #42187: Multisite - Wordpress
 Importer Unavailable
In-Reply-To: <052.80a478b660468f8139173229a1c9b273@wordpress.org>
References: <052.80a478b660468f8139173229a1c9b273@wordpress.org>
Message-ID: <067.e2e11a1e414116cd51ee60ffddf70be6@wordpress.org>

#42187: Multisite - Wordpress Importer Unavailable
--------------------------------+----------------------------------------
 Reporter:  dtiziani            |       Owner:  realloc
     Type:  defect (bug)        |      Status:  accepted
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Networks and Sites  |     Version:  4.8.2
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:  administration, multisite
--------------------------------+----------------------------------------
Changes (by realloc):

 * owner:  (none) => realloc
 * status:  new => accepted


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42187#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 10:39:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 10:39:12 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.2876f4258a06b9fc3d10c308a34ad6e8@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  connectors has-patch has-unit-tests  |     Focuses:
-------------------------------------------------+-------------------------

Comment (by wildworks):

 In [changeset:"62332" 62332]:
 {{{
 #!CommitTicketReference repository="" revision="62332"
 Connectors: Refine plugin install check and PHPStan types.

 Replace `file_exists()` with `validate_plugin()` in the connectors script
 module data, and refine PHPStan type definitions in the connectors code to
 better reflect the actual shape of registered connector data.

 Follow-up to [62288].

 Props jorgefilipecosta, mukesh27, peterwilsoncc, westonruter, wildworks.
 See #65020.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 10:42:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 10:42:53 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.ee63ced549c74442a6c88f47ffa0ffed@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  connectors has-patch has-unit-tests  |     Focuses:
  dev-feedback                                   |
-------------------------------------------------+-------------------------
Changes (by wildworks):

 * keywords:  connectors has-patch has-unit-tests => connectors has-patch
     has-unit-tests dev-feedback


Comment:

 Requesting another committer's sign-off to backport 62332 to 7.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 10:43:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 10:43:00 -0000
Subject: [wp-trac] [WordPress Trac] #65169: support attachment pages is
 disabled by default since 6.4,
 so why then offer image be viewed in attachment pages?
In-Reply-To: <057.7df136539a2d43e5cd9542bd9d0d8404@wordpress.org>
References: <057.7df136539a2d43e5cd9542bd9d0d8404@wordpress.org>
Message-ID: <072.a700b6aba94ee9619a7fcca9303cd62c@wordpress.org>

#65169: support attachment pages is disabled by default since 6.4, so why then
offer image be viewed in attachment pages?
--------------------------------------+------------------------------
 Reporter:  ignatiusjeroe             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  General                   |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  template
--------------------------------------+------------------------------

Comment (by shreyasikhar26):

 Update:
 I have now added a setting to manually enable/disable attachment pages
 which will control the `wp_attachment_pages_enabled` option value in the
 same PR.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65169#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 10:45:35 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 10:45:35 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time
 Collaboration from WordPress Core
In-Reply-To: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
References: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
Message-ID: <065.b6c82c6374197ff93d6beb3d076ca2ea@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
-----------------------------+---------------------
 Reporter:  jorbin           |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  highest omg bbq  |   Milestone:  7.0
Component:  Editor           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+---------------------

Comment (by ellatrix):

 I'm handling the GB in https://github.com/WordPress/gutenberg/pull/78085
 (removing wp.sync exposure by bundling the sync script in core-data) and
 https://github.com/WordPress/wordpress-develop/pull/11760 (syncing GB).
 This will not disable RTC, that part will have to be done in core itself.
 I believe the consensus is to leave RTC code in GB in place and disable
 RTC, maybe add additional guards later if needed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 10:46:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 10:46:08 -0000
Subject: [wp-trac] [WordPress Trac] #49936: Add "deactivate" & "archive"
 bulk options to network site management
In-Reply-To: <048.c1a478357b1f24799ec1b4859da9c559@wordpress.org>
References: <048.c1a478357b1f24799ec1b4859da9c559@wordpress.org>
Message-ID: <063.4990b6096129764e00acc44443fc02cb@wordpress.org>

#49936: Add "deactivate" & "archive" bulk options to network site management
--------------------------------+------------------------------
 Reporter:  afoc                |       Owner:  (none)
     Type:  enhancement         |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Networks and Sites  |     Version:  5.4
 Severity:  minor               |  Resolution:
 Keywords:                      |     Focuses:  multisite
--------------------------------+------------------------------

Comment (by realloc):

 I can confirm that the bulk actions on the Sites list table are not
 coherent with the single-site actions available under each site's row
 actions.

 The current bulk actions are: **Deactivate**, **Archive**, **Spam**,
 **Delete**.
 The single-site row actions are: **Flag for Deletion**, **Archive**,
 **Spam**, **Delete Permanently**.

 At a minimum, the labels should be aligned between bulk and row actions.
 Beyond that, it would be worth discussing whether additional actions (like
 "Activate" / "Unarchive" / "Not Spam") should also be available as bulk
 actions, as the original ticket suggests.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49936#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 11:00:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 11:00:41 -0000
Subject: [wp-trac] [WordPress Trac] #50694: Impossible to add user to
 network site when username / email are both emails and different values
In-Reply-To: <049.38c9293018c388185ca117eea56bcff4@wordpress.org>
References: <049.38c9293018c388185ca117eea56bcff4@wordpress.org>
Message-ID: <064.4434db940790ac414757d680b5c8a8d5@wordpress.org>

#50694: Impossible to add user to network site when username / email are both
emails and different values
--------------------------------+----------------------------------------
 Reporter:  elrae               |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  reporter-feedback   |     Focuses:  administration, multisite
--------------------------------+----------------------------------------
Changes (by realloc):

 * keywords:   => reporter-feedback


Comment:

 I was unable to reproduce this. When trying to create a user with an email
 address as the username, WordPress returns the error:

 ''Usernames can only contain lowercase letters (a-z) and numbers.''

 This suggests the validation already prevents the scenario described in
 this ticket. If it was ever possible to use an email as a username, it
 appears to have been addressed since. I'd recommend closing this as a non-
 issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50694#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 11:03:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 11:03:51 -0000
Subject: [wp-trac] [WordPress Trac] #50694: Impossible to add user to
 network site when username / email are both emails and different values
In-Reply-To: <049.38c9293018c388185ca117eea56bcff4@wordpress.org>
References: <049.38c9293018c388185ca117eea56bcff4@wordpress.org>
Message-ID: <064.05c3f2762f6ea70f8cc977fd60726d98@wordpress.org>

#50694: Impossible to add user to network site when username / email are both
emails and different values
--------------------------------+----------------------------------------
 Reporter:  elrae               |       Owner:  realloc
     Type:  defect (bug)        |      Status:  assigned
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  reporter-feedback   |     Focuses:  administration, multisite
--------------------------------+----------------------------------------
Changes (by realloc):

 * owner:  (none) => realloc
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50694#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 11:06:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 11:06:01 -0000
Subject: [wp-trac] [WordPress Trac] #50694: Impossible to add user to
 network site when username / email are both emails and different values
In-Reply-To: <049.38c9293018c388185ca117eea56bcff4@wordpress.org>
References: <049.38c9293018c388185ca117eea56bcff4@wordpress.org>
Message-ID: <064.62a81e0a1f0db15520c8f5b400ad7f5e@wordpress.org>

#50694: Impossible to add user to network site when username / email are both
emails and different values
----------------------------------+----------------------------------------
 Reporter:  elrae                 |       Owner:  realloc
     Type:  defect (bug)          |      Status:  assigned
 Priority:  normal                |   Milestone:  Awaiting Review
Component:  Networks and Sites    |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  reporter-feedback     |     Focuses:  administration, multisite
  close                           |
----------------------------------+----------------------------------------
Changes (by realloc):

 * keywords:  reporter-feedback => reporter-feedback close


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50694#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 11:49:58 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 11:49:58 -0000
Subject: [wp-trac] [WordPress Trac] #64595: Update Gutenberg ref in
 package.json
In-Reply-To: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
References: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
Message-ID: <067.7a8ad98ac961abe590b29852ce59e9be@wordpress.org>

#64595: Update Gutenberg ref in package.json
----------------------------+---------------------
 Reporter:  ellatrix        |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  7.0
Component:  General         |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------

Comment (by ellatrix):

 In [changeset:"62333" 62333]:
 {{{
 #!CommitTicketReference repository="" revision="62333"
 Editor: Bump pinned hash for the Gutenberg repository.
 This updates the pinned hash from the `gutenberg` from
 `e2970ba736edb99e08fb369d4fb0c378189468ee ` to
 `c15cef1d6b07f666df28dac0383bafb0edfe0914`.

 The following changes are included:

 - RTC: Predefined retry schedules for disconnect dialog, make more lenient
 (https://github.com/WordPress/gutenberg/pull/76966)
 - Block Editor: Prevent Enter key from inserting paragraphs in contentOnly
 sections (https://github.com/WordPress/gutenberg/pull/76989)
 - Cover block: fix embed video background Error 153 in editor
 (https://github.com/WordPress/gutenberg/pull/76904)
 - Restore original template registration tests alongside activation
 variants (https://github.com/WordPress/gutenberg/pull/77068)
 - Avoid stale values in core/cover block for RTC compatibility
 (https://github.com/WordPress/gutenberg/pull/76916)
 - Bump oras-project/setup-oras
 (https://github.com/WordPress/gutenberg/pull/77096)
 (https://github.com/WordPress/gutenberg/pull/77110)
 - RTC: Change SyncConnectionModal to isSyncConnectionErrorHandled filter
 and drop IS_GUTENBERG_PLUGIN check
 (https://github.com/WordPress/gutenberg/pull/76853)
 - contentOnly template lock: Fix block insertion and removal rules
 (https://github.com/WordPress/gutenberg/pull/77119)
 - Global Styles Revisions: Fix footer overflow
 (https://github.com/WordPress/gutenberg/pull/77103)
 - Revision: Fix 'Show changes' button reset state
 (https://github.com/WordPress/gutenberg/pull/77122)
 - Link picker: Decode HTML entities in link preview title
 (https://github.com/WordPress/gutenberg/pull/77170)
 - Connectors: don't clobber third-party custom render in
 registerDefaultConnectors
 (https://github.com/WordPress/gutenberg/pull/77116)
 - Connectors: Replace speak() with notice store for state changes
 (https://github.com/WordPress/gutenberg/pull/77174)
 - Core Data: Fix 'useEntityProp' for raw attributes
 (https://github.com/WordPress/gutenberg/pull/77120)
 - Fix PatternsActions prop name from postType to type
 (https://github.com/WordPress/gutenberg/pull/77251)
 - Fix: restore editor canvas padding in classic themes
 (https://github.com/WordPress/gutenberg/pull/76864)
 - RTC: Add filterable flag for meta box RTC compatibility
 (https://github.com/WordPress/gutenberg/pull/76939)
 - Fix failing 'WP_HTTP_Polling_Sync_Server' unit test
 (https://github.com/WordPress/gutenberg/pull/77025)
 (https://github.com/WordPress/gutenberg/pull/77325)
 - Edit Post: Fix warning in 'useMetaBoxInitialization' hook
 (https://github.com/WordPress/gutenberg/pull/77311)
 - Update the page slug we link to for the AI plugin after the plugin has
 been installed and activated
 (https://github.com/WordPress/gutenberg/pull/77336)
 - Test: Connectors Point to the righ page.
 (https://github.com/WordPress/gutenberg/pull/77272)
 - Post Editor: Store metaboxes RTC-compatible flag on location entries
 (https://github.com/WordPress/gutenberg/pull/77361)
 - Core Abilities: Export initialization promise as `ready`
 (https://github.com/WordPress/gutenberg/pull/77254)
 - Block Editor: Strip per-block custom CSS on save for users without
 edit_css (https://github.com/WordPress/gutenberg/pull/76650)
 - Add heading level 1 for the fonts page
 (https://github.com/WordPress/gutenberg/pull/77482)
 - Connectors: Treat network-active plugins as active in plugin status
 check (https://github.com/WordPress/gutenberg/pull/77661)
 - RTC: Fix disconnect dialog due to uneditable entity
 (https://github.com/WordPress/gutenberg/pull/77242)
 - RTC: Fix "Connection Lost" dialog when too many entities are loaded
 (https://github.com/WordPress/gutenberg/pull/77631)
 - RTC: Fix "Edit as HTML" content reset during collaboration
 (https://github.com/WordPress/gutenberg/pull/77043)
 - RTC: Add optional `shouldSync` function to entity sync config
 (https://github.com/WordPress/gutenberg/pull/76947)
 - RTC: Fixed orphaned meta causing dirty editor state
 (https://github.com/WordPress/gutenberg/pull/77529)
 - Ensure "Retry" button is stable during retries
 (https://github.com/WordPress/gutenberg/pull/77234)
 - Patterns: add confirmation dialog before disconnecting/detaching
 (https://github.com/WordPress/gutenberg/pull/75713)
 - Template parts: make 'Detach' context menu item consistent across
 patterns and template parts
 (https://github.com/WordPress/gutenberg/pull/77581)
 - Remove sandbox `allow-same-origin` for core/html blocks (Merge
 https://github.com/WordPress/gutenberg/pull/77212 to `wp/7.0`)
 (https://github.com/WordPress/gutenberg/pull/77699)
 - Added Context for Next/Prev Enlarge Image
 (https://github.com/WordPress/gutenberg/pull/76967)
 - Backport: Writing Flow: fix arrow keys skipping paragraph containing
 link (https://github.com/WordPress/gutenberg/pull/77478)
 - Revisions: Improve screen reader accessibility for diff markers region
 and slider (https://github.com/WordPress/gutenberg/pull/77660)
 - Connectors: Add role="list" wrapper to connector cards for valid ARIA
 structure (https://github.com/WordPress/gutenberg/pull/77689)
 - Command Palette: Fix macOs label for sites unable to determine UA via
 PHP (https://github.com/WordPress/gutenberg/pull/77638)
 - RTC: Fix inline inserter reset on update sync
 (https://github.com/WordPress/gutenberg/pull/76980)
 (https://github.com/WordPress/gutenberg/pull/77706)
 - Connectors: keep focus on action Button during install
 (https://github.com/WordPress/gutenberg/pull/77544)
 - Added Translator Context for Reply
 (https://github.com/WordPress/gutenberg/pull/77891)
 - Editor: Improve revisions diff pairing performance
 (https://github.com/WordPress/gutenberg/pull/77126)
 - Core Data: Treat single-item responses specially
 (https://github.com/WordPress/gutenberg/pull/76318)
 - Site editor: preserve non-global styles in pattern previews
 (https://github.com/WordPress/gutenberg/pull/77957)
 - RTC: Fix divergence when two offline users reconnect
 (https://github.com/WordPress/gutenberg/pull/77980)
 - RTC: Fix compaction unit test
 (https://github.com/WordPress/gutenberg/pull/77986)
 - Connectors: Stop e2e capability restriction from leaking across specs
 (https://github.com/WordPress/gutenberg/pull/77857)
 - Connectors: Clarify AI plugin callout copy
 (https://github.com/WordPress/gutenberg/pull/78043)
 - Fix: Only auto register settings if the plugin the connector references
 is installed and active.
 (https://github.com/WordPress/gutenberg/pull/77273)
 - Connectors: Add is_active callback support to plugin registration
 (https://github.com/WordPress/gutenberg/pull/77897)
 - RTC: Fix race condition on room creation which can cause a split update
 log (https://github.com/WordPress/gutenberg/pull/77675)
 - RTC: Fix find_canonical_storage_post_id() always returning null
 (https://github.com/WordPress/gutenberg/pull/78053)
 - i18n: add context to scale
 (https://github.com/WordPress/gutenberg/pull/76917)
 - Revisions: Simplify fetching
 (https://github.com/WordPress/gutenberg/pull/77086)
 - e2e: Add e2e tests for template and template part revisions
 (https://github.com/WordPress/gutenberg/pull/76923)
 - Editor: Paginate revisions slider by 100 per page
 (https://github.com/WordPress/gutenberg/pull/77200)
 (https://github.com/WordPress/gutenberg/pull/78070)
 - Revisions: Add diagonal stripe patterns to diff markers to avoid color-
 only distinction (https://github.com/WordPress/gutenberg/pull/77904)
 - Revision: Fix failing e2e test
 (https://github.com/WordPress/gutenberg/pull/78079)
 - Real-time collaboration: Bundle @wordpress/sync instead of exposing as
 wp.sync (https://github.com/WordPress/gutenberg/pull/78085)

 A full list of changes can be found on GitHub:
 https://github.com/WordPress/gutenberg/compare/e2970ba736edb99e08fb369d4fb0c378189468ee…c15cef1d6b07f666df28dac0383bafb0edfe0914.

 Log created with:

 git log --reverse --format="- %s"
 e2970ba736edb99e08fb369d4fb0c378189468ee..c15cef1d6b07f666df28dac0383bafb0edfe0914
 | sed
 's|#\([0-9][0-9]*\)|https://github.com/WordPress/gutenberg/pull/\1|g;
 /github\.com\/WordPress\/gutenberg\/pull/!d' | pbcopy

 See #64595.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64595#comment:55>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 13:20:36 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 13:20:36 -0000
Subject: [wp-trac] [WordPress Trac] #59272: wp-admin search/column order
 not working when running not on port 80
In-Reply-To: <049.0b43d396d16a0e2d63efb880060507ac@wordpress.org>
References: <049.0b43d396d16a0e2d63efb880060507ac@wordpress.org>
Message-ID: <064.ff53993dd1d24619fbcdc5dbc226cdb1@wordpress.org>

#59272: wp-admin search/column order not working when running not on port 80
----------------------------+------------------------------
 Reporter:  canic           |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  6.3.1
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  administration
----------------------------+------------------------------

Comment (by jdeep):

 Hi. I have tested this on WordPress 6.9.4 but was not able to reproduce
 it. Could you please confirm if you are still experiencing this issue on
 the latest WordPress release?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/59272#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 13:31:45 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 13:31:45 -0000
Subject: [wp-trac] [WordPress Trac] #46058: Extra database calls when
 use get_the_excerpt() and posts have images
In-Reply-To: <054.57997a1e427cc3f026a808dae2916966@wordpress.org>
References: <054.57997a1e427cc3f026a808dae2916966@wordpress.org>
Message-ID: <069.27699eab76bf7348db03e4d10794ffc8@wordpress.org>

#46058: Extra database calls when use get_the_excerpt() and posts have images
--------------------------+------------------------------
 Reporter:  kg69design    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.0.3
 Severity:  major         |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------

Comment (by jdeep):

 Hi. I have attempted to reproduce this issue by following your steps
 exactly, but I was unable to replicate the extra database calls on
 WordPress 6.9 using the Twenty Nineteen classic theme.

 Could you provide a bit more information?

 - Current WordPress Version: Are you still able to reproduce this issue on
 the latest version of WordPress (6.9)?

 - Theme: Which specific theme were you using when you originally
 encountered this?

 - Environment Setup: Are you using any persistent object caching (e.g.,
 Redis or Memcached) in your test environment?

 - Plugins: Was this on a completely fresh install with zero active
 plugins, or were there any utility/developer plugins active?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46058#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 13:37:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 13:37:13 -0000
Subject: [wp-trac] [WordPress Trac] #65189: create pattern issue
In-Reply-To: <059.eefb39b025f2070137510d45ec552592@wordpress.org>
References: <059.eefb39b025f2070137510d45ec552592@wordpress.org>
Message-ID: <074.1f1c631bb97130dfa4e0fede39c19261@wordpress.org>

#65189: create pattern issue
-----------------------------+----------------------
 Reporter:  sonaliprajapati  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |     Version:
 Severity:  normal           |  Resolution:  invalid
 Keywords:                   |     Focuses:
-----------------------------+----------------------
Changes (by wildworks):

 * status:  new => closed
 * focuses:  coding-standards =>
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Hi @sonaliprajapati, the reason for that error is that the word
 "wordpress" is included in the title. Please look at this code.

 https://github.com/WordPress/pattern-
 directory/blob/416e65f748e0159f94b710c3f242776438a25721/public_html/wp-
 content/plugins/pattern-directory/includes/pattern-
 validation.php#L427-L429

 In any case, this is not an issue with the WordPress core.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65189#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 13:50:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 13:50:01 -0000
Subject: [wp-trac] [WordPress Trac] #65169: support attachment pages is
 disabled by default since 6.4,
 so why then offer image be viewed in attachment pages?
In-Reply-To: <057.7df136539a2d43e5cd9542bd9d0d8404@wordpress.org>
References: <057.7df136539a2d43e5cd9542bd9d0d8404@wordpress.org>
Message-ID: <072.98e29599ddc83197706fafba08678e9a@wordpress.org>

#65169: support attachment pages is disabled by default since 6.4, so why then
offer image be viewed in attachment pages?
--------------------------------------+------------------------------
 Reporter:  ignatiusjeroe             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  General                   |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  template
--------------------------------------+------------------------------

Comment (by shreyasikhar26):

 I have created a similar issue on Gutenberg:
 https://github.com/WordPress/gutenberg/issues/78100 and added a PR for the
 same: https://github.com/WordPress/gutenberg/pull/78101

 Adding these details here for easy reference.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65169#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 13:57:23 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 13:57:23 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.48b64aeb82457690446ff395f35d241d@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  connectors has-patch has-unit-tests  |     Focuses:
  dev-feedback fixed-major                       |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  connectors has-patch has-unit-tests dev-feedback => connectors
     has-patch has-unit-tests dev-feedback fixed-major


Comment:

 Adding `fixed-major` so it shows up in the correct group for reports
 organized by workflow (such as
 [https://core.trac.wordpress.org/tickets/major/workflow
 tickets/major/workflow].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:00:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:00:44 -0000
Subject: [wp-trac] [WordPress Trac] #65207: Introduce utility class to
 handle 32px form elements on mobile layouts
Message-ID: <053.722dd94060d7d1277c235cb4a3fe0d29@wordpress.org>

#65207: Introduce utility class to handle 32px form elements on mobile layouts
--------------------------------+-----------------------------
 Reporter:  wildworks           |      Owner:  (none)
     Type:  enhancement         |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  General             |    Version:
 Severity:  normal              |   Keywords:  admin-reskin
  Focuses:  ui, administration  |
--------------------------------+-----------------------------
 Form element sizes are basically `40px`, but `32px` is used in some
 places.

 {{{
 #!css
 // CSS specificity: 0,2,1
 .selector input[type="search"] {
         min-height: 32px;
 }
 }}}

 On mobile layouts, the following style expects all form elements to be
 `40px`:

 {{{
 #!css
 // CSS specificity: 0,1,1
 @media screen and (max-width: 782px) {
         input[type="search"] {
                 min-height: 40px;
         }
 }
 }}}

 However, this has lower specificity than the CSS above, so it doesn't
 apply. As a result, an individual override style like the following is
 required for mobile layouts:

 {{{
 #!css
 @media screen and (max-width: 782px) {
         .selector input[type="search"] {
                 min-height: 40px;
         }
 }
 }}}

 This is very easy to overlook, and as reported in #64999, mobile layout
 styles are sometimes missing.

 To solve these issues, I propose adding a new utility class, like `form-
 compact`, for cases where `32px` form elements are needed. For example:

 {{{
 #!css
 .form-compact {
         min-height: 32px;
 }
 @media screen and (max-width: 782px) {
         .form-compact {
                 min-height: 40px;
         }
 }
 }}}

 A similar utility class `.button-compact` exists for buttons.

 cc @sabernhardt @fabiankaegy @joedolson

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65207>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:03:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:03:33 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time
 Collaboration from WordPress Core
In-Reply-To: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
References: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
Message-ID: <065.cfc347dbdf01e1f8b0f9002d10ca41d9@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
--------------------------------------+-----------------------
 Reporter:  jorbin                    |       Owner:  ellatrix
     Type:  task (blessed)            |      Status:  closed
 Priority:  highest omg bbq           |   Milestone:  7.0
Component:  Editor                    |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------
Changes (by ellatrix):

 * owner:  (none) => ellatrix
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62334" 62334]:
 {{{
 #!CommitTicketReference repository="" revision="62334"
 Remove real-time collaboration.

 Removes all RTC related code from core. There will still be RTC related
 code in Gutenberg, but effectively disabled for core since nothing turns
 it on. The wp.sync global has also been hidden by bundling in
 https://github.com/WordPress/gutenberg/pull/78085.

 Developed in: https://github.com/WordPress/wordpress-develop/pull/11774.

 Props maxschmeling, ellatrix, mukesh27.
 Fixes #65205.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:03:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:03:51 -0000
Subject: [wp-trac] [WordPress Trac] #64595: Update Gutenberg ref in
 package.json
In-Reply-To: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
References: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
Message-ID: <067.df29469e7e87f6e5d86af8018869f8a5@wordpress.org>

#64595: Update Gutenberg ref in package.json
-------------------------------------------------+-------------------------
 Reporter:  ellatrix                             |       Owner:  (none)
     Type:  task (blessed)                       |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch fixed-major dev-feedback   |     Focuses:
  commit                                         |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch => has-patch fixed-major dev-feedback commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64595#comment:56>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:04:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:04:18 -0000
Subject: [wp-trac] [WordPress Trac] #64595: Update Gutenberg ref in
 package.json
In-Reply-To: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
References: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
Message-ID: <067.6614908d85435661f12cb8d9098de10d@wordpress.org>

#64595: Update Gutenberg ref in package.json
-------------------------------------------------+-------------------------
 Reporter:  ellatrix                             |       Owner:  (none)
     Type:  task (blessed)                       |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch fixed-major commit dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch fixed-major dev-feedback commit => has-patch fixed-
     major commit dev-reviewed


Comment:

 [62333] looks good to backport. Going to handle that now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64595#comment:57>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:05:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:05:17 -0000
Subject: [wp-trac] [WordPress Trac] #65169: support attachment pages is
 disabled by default since 6.4,
 so why then offer image be viewed in attachment pages?
In-Reply-To: <057.7df136539a2d43e5cd9542bd9d0d8404@wordpress.org>
References: <057.7df136539a2d43e5cd9542bd9d0d8404@wordpress.org>
Message-ID: <072.2b8380d8d7249ed15be85792a7c42e9e@wordpress.org>

#65169: support attachment pages is disabled by default since 6.4, so why then
offer image be viewed in attachment pages?
--------------------------------------+--------------------------------
 Reporter:  ignatiusjeroe             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  General                   |     Version:  trunk
 Severity:  normal                    |  Resolution:  reported-upstream
 Keywords:  has-patch has-unit-tests  |     Focuses:  template
--------------------------------------+--------------------------------
Changes (by Mamaduka):

 * status:  new => closed
 * resolution:   => reported-upstream
 * milestone:  Awaiting Review =>


Comment:

 Here's already an issue for this -
 https://github.com/WordPress/gutenberg/issues/56019.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65169#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:05:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:05:32 -0000
Subject: [wp-trac] [WordPress Trac] #64595: Update Gutenberg ref in
 package.json
In-Reply-To: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
References: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
Message-ID: <067.b26bf617e25f38fcf73efd3ebcf72e59@wordpress.org>

#64595: Update Gutenberg ref in package.json
-------------------------------------------------+-------------------------
 Reporter:  ellatrix                             |       Owner:  (none)
     Type:  task (blessed)                       |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch fixed-major commit dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------

Comment (by desrosj):

 In [changeset:"62335" 62335]:
 {{{
 #!CommitTicketReference repository="" revision="62335"
 Editor: Bump pinned hash for the Gutenberg repository.
 This updates the pinned hash from the `gutenberg` from
 `e2970ba736edb99e08fb369d4fb0c378189468ee ` to
 `c15cef1d6b07f666df28dac0383bafb0edfe0914`.

 The following changes are included:

 - RTC: Predefined retry schedules for disconnect dialog, make more lenient
 (https://github.com/WordPress/gutenberg/pull/76966)
 - Block Editor: Prevent Enter key from inserting paragraphs in contentOnly
 sections (https://github.com/WordPress/gutenberg/pull/76989)
 - Cover block: fix embed video background Error 153 in editor
 (https://github.com/WordPress/gutenberg/pull/76904)
 - Restore original template registration tests alongside activation
 variants (https://github.com/WordPress/gutenberg/pull/77068)
 - Avoid stale values in core/cover block for RTC compatibility
 (https://github.com/WordPress/gutenberg/pull/76916)
 - Bump oras-project/setup-oras
 (https://github.com/WordPress/gutenberg/pull/77096)
 (https://github.com/WordPress/gutenberg/pull/77110)
 - RTC: Change SyncConnectionModal to isSyncConnectionErrorHandled filter
 and drop IS_GUTENBERG_PLUGIN check
 (https://github.com/WordPress/gutenberg/pull/76853)
 - contentOnly template lock: Fix block insertion and removal rules
 (https://github.com/WordPress/gutenberg/pull/77119)
 - Global Styles Revisions: Fix footer overflow
 (https://github.com/WordPress/gutenberg/pull/77103)
 - Revision: Fix 'Show changes' button reset state
 (https://github.com/WordPress/gutenberg/pull/77122)
 - Link picker: Decode HTML entities in link preview title
 (https://github.com/WordPress/gutenberg/pull/77170)
 - Connectors: don't clobber third-party custom render in
 registerDefaultConnectors
 (https://github.com/WordPress/gutenberg/pull/77116)
 - Connectors: Replace speak() with notice store for state changes
 (https://github.com/WordPress/gutenberg/pull/77174)
 - Core Data: Fix 'useEntityProp' for raw attributes
 (https://github.com/WordPress/gutenberg/pull/77120)
 - Fix PatternsActions prop name from postType to type
 (https://github.com/WordPress/gutenberg/pull/77251)
 - Fix: restore editor canvas padding in classic themes
 (https://github.com/WordPress/gutenberg/pull/76864)
 - RTC: Add filterable flag for meta box RTC compatibility
 (https://github.com/WordPress/gutenberg/pull/76939)
 - Fix failing 'WP_HTTP_Polling_Sync_Server' unit test
 (https://github.com/WordPress/gutenberg/pull/77025)
 (https://github.com/WordPress/gutenberg/pull/77325)
 - Edit Post: Fix warning in 'useMetaBoxInitialization' hook
 (https://github.com/WordPress/gutenberg/pull/77311)
 - Update the page slug we link to for the AI plugin after the plugin has
 been installed and activated
 (https://github.com/WordPress/gutenberg/pull/77336)
 - Test: Connectors Point to the righ page.
 (https://github.com/WordPress/gutenberg/pull/77272)
 - Post Editor: Store metaboxes RTC-compatible flag on location entries
 (https://github.com/WordPress/gutenberg/pull/77361)
 - Core Abilities: Export initialization promise as `ready`
 (https://github.com/WordPress/gutenberg/pull/77254)
 - Block Editor: Strip per-block custom CSS on save for users without
 edit_css (https://github.com/WordPress/gutenberg/pull/76650)
 - Add heading level 1 for the fonts page
 (https://github.com/WordPress/gutenberg/pull/77482)
 - Connectors: Treat network-active plugins as active in plugin status
 check (https://github.com/WordPress/gutenberg/pull/77661)
 - RTC: Fix disconnect dialog due to uneditable entity
 (https://github.com/WordPress/gutenberg/pull/77242)
 - RTC: Fix "Connection Lost" dialog when too many entities are loaded
 (https://github.com/WordPress/gutenberg/pull/77631)
 - RTC: Fix "Edit as HTML" content reset during collaboration
 (https://github.com/WordPress/gutenberg/pull/77043)
 - RTC: Add optional `shouldSync` function to entity sync config
 (https://github.com/WordPress/gutenberg/pull/76947)
 - RTC: Fixed orphaned meta causing dirty editor state
 (https://github.com/WordPress/gutenberg/pull/77529)
 - Ensure "Retry" button is stable during retries
 (https://github.com/WordPress/gutenberg/pull/77234)
 - Patterns: add confirmation dialog before disconnecting/detaching
 (https://github.com/WordPress/gutenberg/pull/75713)
 - Template parts: make 'Detach' context menu item consistent across
 patterns and template parts
 (https://github.com/WordPress/gutenberg/pull/77581)
 - Remove sandbox `allow-same-origin` for core/html blocks (Merge
 https://github.com/WordPress/gutenberg/pull/77212 to `wp/7.0`)
 (https://github.com/WordPress/gutenberg/pull/77699)
 - Added Context for Next/Prev Enlarge Image
 (https://github.com/WordPress/gutenberg/pull/76967)
 - Backport: Writing Flow: fix arrow keys skipping paragraph containing
 link (https://github.com/WordPress/gutenberg/pull/77478)
 - Revisions: Improve screen reader accessibility for diff markers region
 and slider (https://github.com/WordPress/gutenberg/pull/77660)
 - Connectors: Add role="list" wrapper to connector cards for valid ARIA
 structure (https://github.com/WordPress/gutenberg/pull/77689)
 - Command Palette: Fix macOs label for sites unable to determine UA via
 PHP (https://github.com/WordPress/gutenberg/pull/77638)
 - RTC: Fix inline inserter reset on update sync
 (https://github.com/WordPress/gutenberg/pull/76980)
 (https://github.com/WordPress/gutenberg/pull/77706)
 - Connectors: keep focus on action Button during install
 (https://github.com/WordPress/gutenberg/pull/77544)
 - Added Translator Context for Reply
 (https://github.com/WordPress/gutenberg/pull/77891)
 - Editor: Improve revisions diff pairing performance
 (https://github.com/WordPress/gutenberg/pull/77126)
 - Core Data: Treat single-item responses specially
 (https://github.com/WordPress/gutenberg/pull/76318)
 - Site editor: preserve non-global styles in pattern previews
 (https://github.com/WordPress/gutenberg/pull/77957)
 - RTC: Fix divergence when two offline users reconnect
 (https://github.com/WordPress/gutenberg/pull/77980)
 - RTC: Fix compaction unit test
 (https://github.com/WordPress/gutenberg/pull/77986)
 - Connectors: Stop e2e capability restriction from leaking across specs
 (https://github.com/WordPress/gutenberg/pull/77857)
 - Connectors: Clarify AI plugin callout copy
 (https://github.com/WordPress/gutenberg/pull/78043)
 - Fix: Only auto register settings if the plugin the connector references
 is installed and active.
 (https://github.com/WordPress/gutenberg/pull/77273)
 - Connectors: Add is_active callback support to plugin registration
 (https://github.com/WordPress/gutenberg/pull/77897)
 - RTC: Fix race condition on room creation which can cause a split update
 log (https://github.com/WordPress/gutenberg/pull/77675)
 - RTC: Fix find_canonical_storage_post_id() always returning null
 (https://github.com/WordPress/gutenberg/pull/78053)
 - i18n: add context to scale
 (https://github.com/WordPress/gutenberg/pull/76917)
 - Revisions: Simplify fetching
 (https://github.com/WordPress/gutenberg/pull/77086)
 - e2e: Add e2e tests for template and template part revisions
 (https://github.com/WordPress/gutenberg/pull/76923)
 - Editor: Paginate revisions slider by 100 per page
 (https://github.com/WordPress/gutenberg/pull/77200)
 (https://github.com/WordPress/gutenberg/pull/78070)
 - Revisions: Add diagonal stripe patterns to diff markers to avoid color-
 only distinction (https://github.com/WordPress/gutenberg/pull/77904)
 - Revision: Fix failing e2e test
 (https://github.com/WordPress/gutenberg/pull/78079)
 - Real-time collaboration: Bundle @wordpress/sync instead of exposing as
 wp.sync (https://github.com/WordPress/gutenberg/pull/78085)

 A full list of changes can be found on GitHub:
 https://github.com/WordPress/gutenberg/compare/e2970ba736edb99e08fb369d4fb0c378189468ee…c15cef1d6b07f666df28dac0383bafb0edfe0914.

 Log created with:

 git log --reverse --format="- %s"
 e2970ba736edb99e08fb369d4fb0c378189468ee..c15cef1d6b07f666df28dac0383bafb0edfe0914
 | sed
 's|#\([0-9][0-9]*\)|https://github.com/WordPress/gutenberg/pull/\1|g;
 /github\.com\/WordPress\/gutenberg\/pull/!d' | pbcopy

 Reviewed by desrosj.
 Merges [62333] to the 7.0 branch.

 Props ellatrix, desrosj.
 See #64595.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64595#comment:58>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:06:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:06:52 -0000
Subject: [wp-trac] [WordPress Trac] #64595: Update Gutenberg ref in
 package.json
In-Reply-To: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
References: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
Message-ID: <067.786762969c2d2537aa3fe6f1ac7d28fb@wordpress.org>

#64595: Update Gutenberg ref in package.json
----------------------------+---------------------
 Reporter:  ellatrix        |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  7.0
Component:  General         |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------
Changes (by desrosj):

 * keywords:  has-patch fixed-major commit dev-reviewed => has-patch


Comment:

 Resetting the keywords for the next hash bump.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64595#comment:59>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:09:57 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:09:57 -0000
Subject: [wp-trac] [WordPress Trac] #64225: Test tool and unit test
 improvements for 7.0
In-Reply-To: <051.28fbf0171a541ddf5270c1ae9d69b8e7@wordpress.org>
References: <051.28fbf0171a541ddf5270c1ae9d69b8e7@wordpress.org>
Message-ID: <066.1574cda38919451a54f9332c48a708a5@wordpress.org>

#64225: Test tool and unit test improvements for 7.0
--------------------------------------+---------------------
 Reporter:  desrosj                   |       Owner:  (none)
     Type:  task (blessed)            |      Status:  closed
 Priority:  normal                    |   Milestone:  7.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------
Changes (by desrosj):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 I'm going to close this out to help clear the milestone with RCs starting
 again in a few hours. It can always be reopened or referenced in a commit
 before the final 7.0 release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64225#comment:78>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:18:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:18:08 -0000
Subject: [wp-trac] [WordPress Trac] #65208: Introduce namespacing for the
 test classes for 7.1
Message-ID: <051.7cf0adfda1ef78da6d78fc912696ab00@wordpress.org>

#65208: Introduce namespacing for the test classes for 7.1
------------------------------+--------------------
 Reporter:  desrosj           |      Owner:  (none)
     Type:  task (blessed)    |     Status:  new
 Priority:  normal            |  Milestone:  7.1
Component:  Build/Test Tools  |    Version:
 Severity:  normal            |   Keywords:
  Focuses:  tests             |
------------------------------+--------------------
 This ticket is for continuing to introduce namespacing for test classes
 during the 7.1 release cycle.

 Previous releases:
 - 7.0: #53010

 Overview copied directly from #53010 (please read the discussion on that
 ticket):

 Introducing namespaces in the production code for WordPress Core is a hot
 topic, so I very purposely do NOT want to touch that in this ticket.

 However, for the test suite, which doesn't get shipped with the WordPress
 production code, it's a whole other matter.

 == Benefits

 Using namespaces in the test suite provides us with the following
 benefits:
 1. If used consistently and providing they follow a set pattern (more
 about this below), they will make it very easy for contributors to find
 the test files/classes they are looking for.
 2. It will allow for shorter file and test class names, while those will
 still be descriptive.
 3. And... it will allow for mocking PHP native functions by declaring a
 namespaced version of that same function in the test class.
 4. It will also allow more easily for multiple test classes to be created
 to test one particular feature/function, which the current naming scheme
 does not allow for. This will allow for tests for the same functionality,
 but which need different fixtures (setup/teardown) to be encapsulated in
 their own test classes.

 == Caveats:

 As the WordPress Core test suite is used not only by Core, but also by
 plugins and themes for integration tests, the test class namespacing
 should be reserved for actual test classes and - for now - not be applied
 to test utility classes / Abstract base test classes (i.e. the
 `tests/phpunit/includes` directory should NOT be touched for now).

 == Proposed pattern

 The current directory structure for tests is, to put it mildly, confusing
 and inconsistent.

 To solve that, I would like to propose the following pattern:
 * File paths:
 `tests/phpunit/tests/wp-[includes|admin]/[SubFolder/]*Class_Under_Test/FunctionUnderTest[OptionalSubsetIndicator]Test.php`
 * Namespace:
 `WordPress\Tests\WP_[Includes|Admin]\[SubFolder\]*Class_Under_Test`
 * Classname: `FunctionUnderTest[OptionalSubsetIndicator]Test`

 For WP Core files which only contain functions outside of a class
 structure, the following pattern is proposed:
 * File paths:
 `tests/phpunit/tests/wp-[includes|admin]/[SubFolder/]*Functions_FileName/FunctionUnderTest[OptionalSubsetIndicator]Test.php`
 * Namespace:
 `WordPress\Tests\WP_[Includes|Admin]\[SubFolder\]*Functions_FileName`
 * Classname: `FunctionUnderTest[OptionalSubsetIndicator]Test`


 The pattern I'm proposing does imply a re-organisation of the test suite
 directory and file structure, but that IMO is for the better.

 It also follows a PSR4-like pattern which will be more intuitive for new
 contributors to work with, as well as follow the PHPUnit recommended test
 class name pattern with having the `Test` as the end of the class name.

 This will also allow for using PSR-4 autoloading for the tests classes and
 adding the `autoload-dev` directive to the `composer.json` file.



 == Planning

 This should be regarded as a small project and not all renaming needs to
 be done at the same time.

 New tests should start following the above proposed pattern as soon as
 consensus has been reached about this proposal.
 Existing tests can be gradually switched over to the new pattern over
 time.

 == Additional tasks associated with this project

 - [ ] Updating the contributors handbook for Core.
 - [ ] Verify that the WordPressCS sniffs will validate this pattern
 correctly.
 - [ ] Write a Make post about the decision once consensus has been
 reached.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65208>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:19:47 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:19:47 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.4286a9732800da34344d86a63510bfab@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  connectors has-patch has-unit-tests  |     Focuses:
  fixed-major dev-reviewed                       |
-------------------------------------------------+-------------------------
Changes (by ellatrix):

 * keywords:  connectors has-patch has-unit-tests dev-feedback fixed-major
     => connectors has-patch has-unit-tests fixed-major dev-reviewed


Comment:

 I don't know much about the Connectors code, but this was reviewed by both
 @westonruter and @jorgefilipecosta, and created by Aki, who are all
 committers, so I'll backport this to the 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:29>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:22:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:22:48 -0000
Subject: [wp-trac] [WordPress Trac] #53010: Introduce namespacing for
 the test classes (was: Tests: introduce namespacing for the test classes)
In-Reply-To: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
References: <047.d5d3b65b3ad41914c1603c5422892100@wordpress.org>
Message-ID: <062.7b8bdd249efc79e11d21b933a61ad994@wordpress.org>

#53010: Introduce namespacing for the test classes
-------------------------------------+-------------------------------------
 Reporter:  jrf                      |       Owner:  SergeyBiryukov
     Type:  task (blessed)           |      Status:  closed
 Priority:  normal                   |   Milestone:  7.0
Component:  Build/Test Tools         |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-patch has-unit-      |     Focuses:  tests, docs, coding-
  tests                              |  standards
-------------------------------------+-------------------------------------
Changes (by desrosj):

 * status:  assigned => closed
 * focuses:  docs, coding-standards => tests, docs, coding-standards
 * resolution:   => fixed


Comment:

 With 7.0 RCs resuming in a few hours and this ticket having commits that
 were made during the 7.0 release cycle, I am going to close this ticket
 out.

 I have opened #65208 to continue working on this during the 7.1 release.
 For now I have just copied this ticket's entire description and included
 some context above that. But it should be updated to include a summary of
 the direction that was chosen and the tasks required going forward.

 I also upated every pull request referencing this ticket to now reference
 the new one so they are not lost in the transition.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53010#comment:67>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:24:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:24:12 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.e2d98a665a1fd00ed1a7f1af708c8d9b@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  connectors has-patch has-unit-tests  |     Focuses:
  fixed-major dev-reviewed                       |
-------------------------------------------------+-------------------------

Comment (by ellatrix):

 In [changeset:"62336" 62336]:
 {{{
 #!CommitTicketReference repository="" revision="62336"
 Connectors: Refine plugin install check and PHPStan types.

 Replace `file_exists()` with `validate_plugin()` in the connectors script
 module data, and refine PHPStan type definitions in the connectors code to
 better reflect the actual shape of registered connector data.

 Follow-up to [62288].

 Reviewed by ellatrix.
 Merges [62332] to the 7.0 branch.

 Props jorgefilipecosta, mukesh27, peterwilsoncc, westonruter, wildworks.
 See #65020.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:31>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:24:36 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:24:36 -0000
Subject: [wp-trac] [WordPress Trac] #65208: Introduce namespacing for
 the test classes for 7.1
In-Reply-To: <051.7cf0adfda1ef78da6d78fc912696ab00@wordpress.org>
References: <051.7cf0adfda1ef78da6d78fc912696ab00@wordpress.org>
Message-ID: <066.c6cc6fe7c773ee8b0a04e0815d283093@wordpress.org>

#65208: Introduce namespacing for the test classes for 7.1
------------------------------+---------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  7.1
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:  tests
------------------------------+---------------------
Changes (by desrosj):

 * keywords:  has-patch has-unit-tests =>


Old description:

> This ticket is for continuing to introduce namespacing for test classes
> during the 7.1 release cycle.
>
> Previous releases:
> - 7.0: #53010
>
> Overview copied directly from #53010 (please read the discussion on that
> ticket):
>
> Introducing namespaces in the production code for WordPress Core is a hot
> topic, so I very purposely do NOT want to touch that in this ticket.
>
> However, for the test suite, which doesn't get shipped with the WordPress
> production code, it's a whole other matter.
>
> == Benefits
>
> Using namespaces in the test suite provides us with the following
> benefits:
> 1. If used consistently and providing they follow a set pattern (more
> about this below), they will make it very easy for contributors to find
> the test files/classes they are looking for.
> 2. It will allow for shorter file and test class names, while those will
> still be descriptive.
> 3. And... it will allow for mocking PHP native functions by declaring a
> namespaced version of that same function in the test class.
> 4. It will also allow more easily for multiple test classes to be created
> to test one particular feature/function, which the current naming scheme
> does not allow for. This will allow for tests for the same functionality,
> but which need different fixtures (setup/teardown) to be encapsulated in
> their own test classes.
>
> == Caveats:
>
> As the WordPress Core test suite is used not only by Core, but also by
> plugins and themes for integration tests, the test class namespacing
> should be reserved for actual test classes and - for now - not be applied
> to test utility classes / Abstract base test classes (i.e. the
> `tests/phpunit/includes` directory should NOT be touched for now).
>
> == Proposed pattern
>
> The current directory structure for tests is, to put it mildly, confusing
> and inconsistent.
>
> To solve that, I would like to propose the following pattern:
> * File paths:
> `tests/phpunit/tests/wp-[includes|admin]/[SubFolder/]*Class_Under_Test/FunctionUnderTest[OptionalSubsetIndicator]Test.php`
> * Namespace:
> `WordPress\Tests\WP_[Includes|Admin]\[SubFolder\]*Class_Under_Test`
> * Classname: `FunctionUnderTest[OptionalSubsetIndicator]Test`
>
> For WP Core files which only contain functions outside of a class
> structure, the following pattern is proposed:
> * File paths:
> `tests/phpunit/tests/wp-[includes|admin]/[SubFolder/]*Functions_FileName/FunctionUnderTest[OptionalSubsetIndicator]Test.php`
> * Namespace:
> `WordPress\Tests\WP_[Includes|Admin]\[SubFolder\]*Functions_FileName`
> * Classname: `FunctionUnderTest[OptionalSubsetIndicator]Test`
>

> The pattern I'm proposing does imply a re-organisation of the test suite
> directory and file structure, but that IMO is for the better.
>
> It also follows a PSR4-like pattern which will be more intuitive for new
> contributors to work with, as well as follow the PHPUnit recommended test
> class name pattern with having the `Test` as the end of the class name.
>
> This will also allow for using PSR-4 autoloading for the tests classes
> and adding the `autoload-dev` directive to the `composer.json` file.
>

>
> == Planning
>
> This should be regarded as a small project and not all renaming needs to
> be done at the same time.
>
> New tests should start following the above proposed pattern as soon as
> consensus has been reached about this proposal.
> Existing tests can be gradually switched over to the new pattern over
> time.
>
> == Additional tasks associated with this project
>
> - [ ] Updating the contributors handbook for Core.
> - [ ] Verify that the WordPressCS sniffs will validate this pattern
> correctly.
> - [ ] Write a Make post about the decision once consensus has been
> reached.

New description:

 This ticket is for continuing to introduce namespacing for test classes
 during the 7.1 release cycle.

 Previous releases:
 - 7.0: #53010

 Overview copied directly from #53010 (please read the discussion on that
 ticket):

 > Introducing namespaces in the production code for WordPress Core is a
 hot topic, so I very purposely do NOT want to touch that in this ticket.
 >
 > However, for the test suite, which doesn't get shipped with the
 WordPress production code, it's a whole other matter.
 >
 > == Benefits
 >
 > Using namespaces in the test suite provides us with the following
 benefits:
 > 1. If used consistently and providing they follow a set pattern (more
 about this below), they will make it very easy for contributors to find
 the test files/classes they are looking for.
 > 2. It will allow for shorter file and test class names, while those will
 still be descriptive.
 > 3. And... it will allow for mocking PHP native functions by declaring a
 namespaced version of that same function in the test class.
 > 4. It will also allow more easily for multiple test classes to be
 created to test one particular feature/function, which the current naming
 scheme does not allow for. This will allow for tests for the same
 functionality, but which need different fixtures (setup/teardown) to be
 encapsulated in their own test classes.
 >
 > == Caveats:
 >
 > As the WordPress Core test suite is used not only by Core, but also by
 plugins and themes for integration tests, the test class namespacing
 should be reserved for actual test classes and - for now - not be applied
 to test utility classes / Abstract base test classes (i.e. the
 `tests/phpunit/includes` directory should NOT be touched for now).
 >
 > == Proposed pattern
 >
 > The current directory structure for tests is, to put it mildly,
 confusing and inconsistent.
 >
 > To solve that, I would like to propose the following pattern:
 > * File paths:
 `tests/phpunit/tests/wp-[includes|admin]/[SubFolder/]*Class_Under_Test/FunctionUnderTest[OptionalSubsetIndicator]Test.php`
 > * Namespace:
 `WordPress\Tests\WP_[Includes|Admin]\[SubFolder\]*Class_Under_Test`
 > * Classname: `FunctionUnderTest[OptionalSubsetIndicator]Test`
 >
 > For WP Core files which only contain functions outside of a class
 structure, the following pattern is proposed:
 > * File paths:
 `tests/phpunit/tests/wp-[includes|admin]/[SubFolder/]*Functions_FileName/FunctionUnderTest[OptionalSubsetIndicator]Test.php`
 > * Namespace:
 `WordPress\Tests\WP_[Includes|Admin]\[SubFolder\]*Functions_FileName`
 > * Classname: `FunctionUnderTest[OptionalSubsetIndicator]Test`
 >
 >
 > The pattern I'm proposing does imply a re-organisation of the test suite
 directory and file structure, but that IMO is for the better.
 >
 > It also follows a PSR4-like pattern which will be more intuitive for new
 contributors to work with, as well as follow the PHPUnit recommended test
 class name pattern with having the `Test` as the end of the class name.
 >
 > This will also allow for using PSR-4 autoloading for the tests classes
 and adding the `autoload-dev` directive to the `composer.json` file.
 >
 >
 >
 > == Planning
 >
 > This should be regarded as a small project and not all renaming needs to
 be done at the same time.
 >
 > New tests should start following the above proposed pattern as soon as
 consensus has been reached about this proposal.
 > Existing tests can be gradually switched over to the new pattern over
 time.
 >
 > == Additional tasks associated with this project
 >
 > - [ ] Updating the contributors handbook for Core.
 > - [ ] Verify that the WordPressCS sniffs will validate this pattern
 correctly.
 > - [ ] Write a Make post about the decision once consensus has been
 reached.

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65208#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:25:40 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:25:40 -0000
Subject: [wp-trac] [WordPress Trac] #65191: deletePluginSuccess does not
 update counts for custom plugin_status groups
In-Reply-To: <052.d4bbf842536c16e47061eee401603e57@wordpress.org>
References: <052.d4bbf842536c16e47061eee401603e57@wordpress.org>
Message-ID: <067.6cc0e440a96e9ba8627fda6a123457a7@wordpress.org>

#65191: deletePluginSuccess does not update counts for custom plugin_status groups
-------------------------------------+------------------------------
 Reporter:  andrew.p                 |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Plugins                  |     Version:
 Severity:  minor                    |  Resolution:
 Keywords:  needs-testing has-patch  |     Focuses:
-------------------------------------+------------------------------

Comment (by alessioarzentondev):

 Worked on this during WordPress Contributor Day, Torino 2026.

 While testing the previous PR, we noticed that when a plugin is deleted
 and the corresponding <li> is removed from the WP_List_Table filters via
 Ajax, the | separator on the preceding <li> was left behind, because it
 was injected via PHP and therefore not aware of subsequent DOM changes.

 Since it's purely a visual element, we think it belongs in CSS instead.

 Moving it to a stylesheet keeps structure and presentation separated,
 makes the separator easier to restyle or remove, and handles the last item
 automatically without any special PHP logic. Nothing changes visually for
 the user, and the markup ends up a bit cleaner — including for screen
 readers and copy/paste, since the | is no longer part of the text content.

 Props andrew.p, alessioarzentondev, gabrieleburgarella, enzo2018, lopo,
 realloc, f94leonardo.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65191#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:26:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:26:20 -0000
Subject: [wp-trac] [WordPress Trac] #65020: Connectors: Support custom
 plugin is_active callback in connector registry and plugin status output
In-Reply-To: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
References: <055.d405075069acea8d9ef2197fb71ff599@wordpress.org>
Message-ID: <070.e052513fe5c73c15ca112e90a193503a@wordpress.org>

#65020: Connectors: Support custom plugin is_active callback in connector registry
and plugin status output
-------------------------------------------------+-------------------------
 Reporter:  iamadisingh                          |       Owner:
                                                 |  jorgefilipecosta
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  connectors has-patch has-unit-tests  |     Focuses:
  fixed-major dev-reviewed                       |
-------------------------------------------------+-------------------------
Changes (by wildworks):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 Since [https://github.com/WordPress/wordpress-develop/pull/11701 PR 11701]
 was committed to both trunk and 7.0, I think this ticket can be closed
 again.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65020#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:26:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:26:29 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time
 Collaboration from WordPress Core
In-Reply-To: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
References: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
Message-ID: <065.b45ec380c4034b06e2918c160f39e53e@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
---------------------------------------------------+-----------------------
 Reporter:  jorbin                                 |       Owner:  ellatrix
     Type:  task (blessed)                         |      Status:  reopened
 Priority:  highest omg bbq                        |   Milestone:  7.0
Component:  Editor                                 |     Version:
 Severity:  normal                                 |  Resolution:
 Keywords:  has-patch has-unit-tests dev-feedback  |     Focuses:
---------------------------------------------------+-----------------------
Changes (by ellatrix):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests dev-
     feedback
 * status:  closed => reopened
 * resolution:  fixed =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:28:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:28:12 -0000
Subject: [wp-trac] [WordPress Trac] #64904: Real time collboration:
 determine approach for opt in setting for users in Settings > Writing
In-Reply-To: <052.0bbda23d420073a23acb5985c10fd47e@wordpress.org>
References: <052.0bbda23d420073a23acb5985c10fd47e@wordpress.org>
Message-ID: <067.ee81ae7e229cf0bfcb3c52f7349915e2@wordpress.org>

#64904: Real time collboration: determine approach for opt in setting for users in
Settings > Writing
----------------------------+--------------------------------
 Reporter:  annezazu        |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  7.1
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  ui, accessibility
----------------------------+--------------------------------
Changes (by ellatrix):

 * milestone:  7.0 => 7.1


Comment:

 Punting to 7.1, see #65205.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64904#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:28:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:28:27 -0000
Subject: [wp-trac] [WordPress Trac] #65138: RTC: Real-time collaboration
 bug sprint for 7.0
In-Reply-To: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
References: <051.909ebea669937619aa3dbdcbd67aaafc@wordpress.org>
Message-ID: <066.41965499108cb09bea302bf9a5d3f30b@wordpress.org>

#65138: RTC: Real-time collaboration bug sprint for 7.0
-------------------------------------------------+-------------------------
 Reporter:  dmsnell                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests gutenberg-  |     Focuses:  tests
  merge                                          |
-------------------------------------------------+-------------------------
Changes (by ellatrix):

 * milestone:  7.0 => 7.1


Comment:

 Punting to 7.1, see #65205.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65138#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:29:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:29:05 -0000
Subject: [wp-trac] [WordPress Trac] #64696: Real time collboration
 effectively disables persistent post caches while anyone edits a post
In-Reply-To: <057.05b7879d9d7300bfeccbd48dcfe7237b@wordpress.org>
References: <057.05b7879d9d7300bfeccbd48dcfe7237b@wordpress.org>
Message-ID: <072.90f1d77110e79b146df6200b41a81d09@wordpress.org>

#64696: Real time collboration effectively disables persistent post caches while
anyone edits a post
--------------------------------------+--------------------------
 Reporter:  peterwilsoncc             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Posts, Post Types         |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------
Changes (by ellatrix):

 * milestone:  7.0 => 7.1


Comment:

 Punting to 7.1, see #65205.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64696#comment:173>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:32:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:32:41 -0000
Subject: [wp-trac] [WordPress Trac] #65100: Accessibility issues in
 admin Font Library
In-Reply-To: <053.fd1c73df50e7a84ff15cd733e2c7ac6f@wordpress.org>
References: <053.fd1c73df50e7a84ff15cd733e2c7ac6f@wordpress.org>
Message-ID: <068.b8cb1a6594458a42ce6b41a5e6d6d53c@wordpress.org>

#65100: Accessibility issues in admin Font Library
--------------------------+----------------------------
 Reporter:  joedolson     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0
Component:  Themes        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility
--------------------------+----------------------------

Comment (by wildworks):

 This ticket raises three issues:

 1. The main heading needs to be changed to an "h1" instead of using an
 "h2".
 2. The "header" element is inappropriate in this context
 3. Avoid using full white for the page background.

 The first and second issues have already been fixed upstream and have been
 backported to 7.0.

 https://github.com/WordPress/gutenberg/pull/78002

 The third point will probably also need to be fixed upstream.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65100#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:32:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:32:48 -0000
Subject: [wp-trac] [WordPress Trac] #65207: Introduce utility class to
 handle 32px form elements on mobile layouts
In-Reply-To: <053.722dd94060d7d1277c235cb4a3fe0d29@wordpress.org>
References: <053.722dd94060d7d1277c235cb4a3fe0d29@wordpress.org>
Message-ID: <068.6a5a2ee110a0286566501a67886cac0e@wordpress.org>

#65207: Introduce utility class to handle 32px form elements on mobile layouts
--------------------------+---------------------------------
 Reporter:  wildworks     |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  admin-reskin  |     Focuses:  ui, administration
--------------------------+---------------------------------

Comment (by joedolson):

 This makes sense to me. A utility class can help centralize sizing so that
 we can make all of this more consistent.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65207#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:35:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:35:12 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time
 Collaboration from WordPress Core
In-Reply-To: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
References: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
Message-ID: <065.f6e5e332d71df9afb9aa6d40c1e9c464@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
-------------------------------------------------+-------------------------
 Reporter:  jorbin                               |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  highest omg bbq                      |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:
  feedback fixed-major commit                    |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch has-unit-tests dev-feedback => has-patch has-unit-
     tests dev-feedback fixed-major commit


Comment:

 Adding `fixed-major commit` so this one shows up in the correct group for
 reports organized by workflow (such as
 [https://core.trac.wordpress.org/tickets/major/workflow
 tickets/major/workflow].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:48:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:48:27 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.fd735fc94b3d65627155d87485e29e59@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------
Changes (by wildworks):

 * priority:  high => normal


Comment:

 Perhaps it might be better to introduce utility classes for form elements
 first. See #65207.

 This would also make it easier to address this ticket. Fortunately, there
 are no major layout issues on the mobile layout, so let's revert the
 priority to normal.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 14:51:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 14:51:20 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time
 Collaboration from WordPress Core
In-Reply-To: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
References: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
Message-ID: <065.306f3fadf507e02ae7810431af7b0ac0@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
-------------------------------------------------+-------------------------
 Reporter:  jorbin                               |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  highest omg bbq                      |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:
  feedback fixed-major commit                    |
-------------------------------------------------+-------------------------

Comment (by ellatrix):

 In [changeset:"62337" 62337]:
 {{{
 #!CommitTicketReference repository="" revision="62337"
 Properly delete RTC files after [62334].

 Props desrosj.
 See #65205.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 15:40:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 15:40:51 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.cc38049c7148ca6cb8d97990df22f002@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests                           |
-------------------------------------------------+-------------------------

Comment (by sabernhardt):

 I would prefer to revert [62025], even if the ticket stays in 7.0 (or
 moves to 7.1 and back to 7.0 if a patch is ready in time). Then the
 differences from 6.9 would be clearer.

 > PR that simply changes the frontend color theme to modern colors.

 Anyone who purposely returns to the Fresh scheme should not have the
 Modern scheme CSS.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 15:47:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 15:47:49 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.645561f369fd0eaf7af42f3cf7669cca@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests                           |
-------------------------------------------------+-------------------------

Comment (by wildworks):

 > > PR that simply changes the frontend color theme to modern colors.

 > Anyone who purposely returns to the Fresh scheme should not have the
 Modern scheme CSS.

 You're right. Indeed, it seems best to revert [62025] for now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:54>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 15:57:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 15:57:10 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time
 Collaboration from WordPress Core
In-Reply-To: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
References: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
Message-ID: <065.6908daee599b6feaba25a7a5b758463a@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
-------------------------------------------------+-------------------------
 Reporter:  jorbin                               |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  highest omg bbq                      |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests fixed-      |     Focuses:
  major commit dev-reviewed                      |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch has-unit-tests dev-feedback fixed-major commit =>
     has-patch has-unit-tests fixed-major commit dev-reviewed


Comment:

 [62334] and [62337] look good for backport. Handling that now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 15:59:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 15:59:06 -0000
Subject: [wp-trac] [WordPress Trac] #65205: Remove Real Time
 Collaboration from WordPress Core
In-Reply-To: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
References: <050.12981e04c95f83cb631331103e122bbb@wordpress.org>
Message-ID: <065.911eb1fb261adfa2040a00a80c398aa2@wordpress.org>

#65205: Remove Real Time Collaboration from WordPress Core
-------------------------------------------------+-------------------------
 Reporter:  jorbin                               |       Owner:  ellatrix
     Type:  task (blessed)                       |      Status:  closed
 Priority:  highest omg bbq                      |   Milestone:  7.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests fixed-      |     Focuses:
  major commit dev-reviewed                      |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62338" 62338]:
 {{{
 #!CommitTicketReference repository="" revision="62338"
 Remove real-time collaboration.

 Removes all RTC related code from core. There will still be RTC related
 code in Gutenberg, but effectively disabled for core since nothing turns
 it on. The `wp.sync` global has also been hidden by bundling in
 https://github.com/WordPress/gutenberg/pull/78085.

 Developed in: https://github.com/WordPress/wordpress-develop/pull/11774.

 Reviewed by desrosj.
 Merges [62334], [62337] to the 7.0 branch.

 Props maxschmeling, ellatrix, mukesh27.
 Fixes #65205.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65205#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 16:04:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 16:04:33 -0000
Subject: [wp-trac] [WordPress Trac] #65209: Connectors: Expose
 isFileModDisabled flag to connector script module data.
Message-ID: <060.cb590e149a9788ce40c3331ee619316f@wordpress.org>

#65209: Connectors: Expose isFileModDisabled flag to connector script module data.
------------------------------+--------------------
 Reporter:  jorgefilipecosta  |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:  7.0
Component:  General           |    Version:  trunk
 Severity:  normal            |   Keywords:
  Focuses:                    |
------------------------------+--------------------
 Backports PR https://github.com/WordPress/gutenberg/pull/77521.
 Makes an enhacement so the connectors screen say if the website has
 disallowed file modifications.

 The connectors admin screen needs to know whether file modifications are
 permitted (e.g. when `DISALLOW_FILE_MODS` is set, when the filesystem is
 not writable, or when the `file_mod_allowed` filter denies it) so the UI
 can adapt accordingly — for example, surfacing the appropriate messaging
 or disabling plugin-install affordances when those operations are not
 allowed.


   == Proposed change ==
 Expose a new `isFileModDisabled` boolean on the connectors script module
 data, derived from `wp_is_file_mod_allowed( 'install_plugins' )`:

   {{{#!php
   <?php
   $data['isFileModDisabled'] = ! wp_is_file_mod_allowed( 'install_plugins'
 );
   }}}


   == Testing ==

    1. Load the connectors admin screen and inspect the script module data
       payload — `isFileModDisabled` should be present and `false` on a
       standard install.
    2. Add `define( 'DISALLOW_FILE_MODS', true );` to `wp-config.php` and
       reload — `isFileModDisabled` should now be `true`.
    3. Confirm the value also flips when a filter denies the
       `install_plugins` context, e.g.:
       {{{#!php
       <?php
       add_filter( 'file_mod_allowed', function ( $allowed, $context ) {
           return 'install_plugins' === $context ? false : $allowed;
       }, 10, 2 );
       }}}

   == Patch ==

   GitHub PR: [https://github.com/WordPress/wordpress-develop/pull/11779

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65209>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 16:21:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 16:21:14 -0000
Subject: [wp-trac] [WordPress Trac] #65208: Introduce namespacing for
 the test classes for 7.1
In-Reply-To: <051.7cf0adfda1ef78da6d78fc912696ab00@wordpress.org>
References: <051.7cf0adfda1ef78da6d78fc912696ab00@wordpress.org>
Message-ID: <066.b96935a434314b4cebdc663a1edd88dc@wordpress.org>

#65208: Introduce namespacing for the test classes for 7.1
------------------------------+---------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  7.1
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:  tests
------------------------------+---------------------

Comment (by pbearne):

 Looking forward to being able to work on this :-)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65208#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 17:35:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 17:35:08 -0000
Subject: [wp-trac] [WordPress Trac] #65210: Change Plugin's review paradigm
Message-ID: <053.3ba3b8010ce152e71a70016e5e5e2cc7@wordpress.org>

#65210: Change Plugin's review paradigm
-----------------------------+-----------------------------
 Reporter:  ridesirat        |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Plugins          |    Version:
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 The current volume of plugin submissions is reaching unsustainable levels,
 with plugins remaining the primary vector for site instability and
 security vulnerabilities. To optimize resource allocation, there could be
 a paradigm shift from manual pre-review to a community-driven sandbox
 model:

 Sandbox Environment: New plugins are uploaded to an isolated sandbox where
 users can test functionality without site risk.

 Community Validation: Implement a robust voting and evaluation system.
 Only plugins that reach a specific community threshold proceed to a formal
 "Special Review" for inclusion in the main repository.

 Soft Transition: Immediately transition to a "Not Reviewed" status for new
 entries, marked with a prominent alert symbol, allowing the review team to
 reallocate focus toward core security and architecture.

 This model shifts the burden of initial vetting to the community while
 maintaining high standards for the most popular tools.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65210>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 18:09:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 18:09:22 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
Message-ID: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>

#65211: Font upload shows failure message but font is added to library
--------------------------+-----------------------------
 Reporter:  369work       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  trunk
 Severity:  normal        |   Keywords:  needs-testing
  Focuses:                |
--------------------------+-----------------------------
 Description:
 When uploading a font from Appearance > Fonts, WordPress shows an upload
 failure error.
 However, the uploaded font is actually added to the Font Library list.

 Steps to reproduce:
 1. Go to Appearance > Fonts.
 2. Click upload/add new font.
 3. Upload ShipporiMincho-Regular.woff2.
 4. Upload MPLUSRounded1c-Regular.woff2.
 5. Upload NotoSerifJP-VariableFont_wght.woff2.

 Actual result:
 - Upload failed error is shown in the UI on every upload.
 - Browser console shows: Cannot read properties of undefined (reading
 'styles').
 - All uploaded fonts still appear in the Font Library list.

 Uploaded files:
 - ShipporiMincho-Regular.woff2
 - MPLUSRounded1c-Regular.woff2
 - NotoSerifJP-VariableFont_wght.woff2

 Expected result:
 - If the font is successfully stored and listed, no failure error should
 be shown.
 - The UI result and backend result should be consistent.

 Environment:
 - WordPress version: 7.0 RC3
 - Theme: TT5
 - Active plugins: all plugins disabled
 - Browser/OS: Edge

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 18:10:36 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 18:10:36 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.a70873874eef79aa172e5572e7a19352@wordpress.org>

#65211: Font upload shows failure message but font is added to library
---------------------------+------------------------------
 Reporter:  369work        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------
Changes (by 369work):

 * Attachment "font6.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 18:11:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 18:11:04 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.d8a2d3003b1d7751fd8eb19775bc1455@wordpress.org>

#65211: Font upload shows failure message but font is added to library
---------------------------+------------------------------
 Reporter:  369work        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------
Changes (by 369work):

 * Attachment "font5.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 18:12:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 18:12:17 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.42353c94c103cca0aeddd69c34c45408@wordpress.org>

#65211: Font upload shows failure message but font is added to library
---------------------------+------------------------------
 Reporter:  369work        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------

Comment (by amykamala):

 Thanks for reporting this! The alert is citing that properties of styles
 can not be read. The font is a Japanese font, .woff2 file, while other
 .woff2 files were tested during the release party and did not get the same
 alert. Here is the slack thread for reference:
 https://wordpress.slack.com/archives/C02RQBWTW/p1778261887176439

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 19:02:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 19:02:24 -0000
Subject: [wp-trac] [WordPress Trac] #65209: Connectors: Expose
 isFileModDisabled flag to connector script module data.
In-Reply-To: <060.cb590e149a9788ce40c3331ee619316f@wordpress.org>
References: <060.cb590e149a9788ce40c3331ee619316f@wordpress.org>
Message-ID: <075.f2d6bd947394876b5526973e48977d83@wordpress.org>

#65209: Connectors: Expose isFileModDisabled flag to connector script module data.
------------------------------+---------------------
 Reporter:  jorgefilipecosta  |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  7.0
Component:  General           |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+---------------------

Comment (by jorgefilipecosta):

 In [changeset:"62341" 62341]:
 {{{
 #!CommitTicketReference repository="" revision="62341"
 Connectors: Expose `isFileModDisabled` flag to connector script module
 data.

 Adds an `isFileModDisabled` boolean — derived from
 `wp_is_file_mod_allowed(   'install_plugins' )` — to the data exposed via
 the `script_module_data_options-connectors-wp-admin` filter, so the
 connectors UI can adapt when file modifications are disabled.

 Props jorgefilipecosta, westonruter, jeffpaul.
 See #65209.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65209#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 20:20:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 20:20:10 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.fc557cc3b4372f5f6c2a49b915c524e9@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
---------------------------+--------------------------
 Reporter:  jonsurrell     |       Owner:  westonruter
     Type:  defect (bug)   |      Status:  accepted
 Priority:  high           |   Milestone:  7.0
Component:  Script Loader  |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript
---------------------------+--------------------------

Comment (by westonruter):

 Replying to [comment:4 jorbin]:
 > Otherwise, I would like to also propose an Option E: Throw a
 `doing_it_wrong` if `module_dependencies` is set without `in_footer` as
 `true` or `strategy` set as `defer`.

 I like this suggestion, along with documentation that
 `module_dependencies` requires footer printing or `defer` loading
 strategy. Eventually, when browsers all support multiple import maps and
 we just-in-time print `importmap` scripts before printing scripts and
 script modules, we can remove this warning. It's true that a script
 //may// work around this by waiting to `import()` until
 `DOMContentLoaded`. But we can't know that, so better to warn. We won't
 block it, so the script may still work correctly, and the
 `doing_it_wrong_trigger_error` filter can be used to suppress the warning.
 However, this won't be needed if we do:

 > b. Add the polyfill and print multiple importmaps as needed.

 This would nicely eliminate the timing issues for ensuring that the
 `importmap` script is printed after all modules.

 > I don't think WordPress Core actually has any business providing an
 espree module for extenders. Exposing it as a Core module is really an
 undesired effect of the current limitations of WordPress' module system.

 This is true, but core has many libraries it makes available in default
 scripts which extenders can use. So adding espree is no different from
 previous such libraries (not to say we should keep doing this forever).

 In regard to scoped modules, we wouldn't actually have to register espree
 as a module to begin with. Inside of `wp_enqueue_code_editor()` we could
 include the full URL to the `espree.js` file among the data that gets
 exported from PHP to JS via the `wp.codeEditor` global. Then the relevant
 JS could do `await import( wp.codeMirror.path.to.espreeUrl )` as opposed
 to `await import( 'espree' )`.

 ----


 For 7.0, I think the least impactful to go with the documentation and
 `_doing_it_wrong()` to warn if `module_dependencies` is being used without
 `in_footer` or `defer`. For performance, we really want classic scripts to
 be using these anyway as a best practice, since it eliminates a blocking
 script from the critical rendering path. Then in 7.1 we can explore adding
 the printing of multiple `importmap` scripts along with the polyfill and
 remove the restriction.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 20:45:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 20:45:06 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.3eeacf1e71439026aa674d1fec0c98ce@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch commit            |  administration
-------------------------------------+-------------------------------------
Changes (by hiroshisato):

 * Attachment "スクリーンショット 2026-05-09 4.46.13.png" added.

 Elementor

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 20:45:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 20:45:50 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.d2ea056b1625ec85a85eb5b3482844e4@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch commit            |  administration
-------------------------------------+-------------------------------------
Changes (by hiroshisato):

 * Attachment "スクリーンショット 2026-05-09 4.47.05.png" added.

 MonsterInsights

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 20:48:03 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 20:48:03 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.e6ec2420b0014951e1c916d8f79b0a80@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch commit            |  administration
-------------------------------------+-------------------------------------
Changes (by hiroshisato):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 It looks like this issue has reappeared in WordPress 7.0 RC3.

 The plugin name and the “Install Now” button are overlapping again on the
 Add Plugins screen.

 In the previous discussion, this issue was not limited to Japanese.
 Similar layout problems were also reported in other locales, so this
 regression may affect languages other than Japanese as well.

 This is not a major functional bug, but it is a visible layout issue on a
 screen that many users interact with. A broken layout on the plugin
 installation screen can make WordPress appear less polished.

 I think this should be fixed before the final release if possible.

 I reopened this ticket because the issue appears to be the same
 regression. However, if it would be better to handle this as a separate
 issue, I’m happy to create a new ticket or rewrite the report accordingly.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 20:49:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 20:49:50 -0000
Subject: [wp-trac] [WordPress Trac] #24552: Taking over a locked post
 does not always load the most recent revision
In-Reply-To: <055.e616da5efaef717dcf31290205f8ec8e@wordpress.org>
References: <055.e616da5efaef717dcf31290205f8ec8e@wordpress.org>
Message-ID: <070.92e01c7d873a9acbcc99e5eef4066f8c@wordpress.org>

#24552: Taking over a locked post does not always load the most recent revision
--------------------------+------------------------------
 Reporter:  johnbillion   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Autosave      |     Version:  3.6
 Severity:  major         |  Resolution:
 Keywords:  needs-patch   |     Focuses:  administration
--------------------------+------------------------------

Comment (by abhishekfdd):

 Confirming the reproduction report from r1k0 in comment:9 and the earlier
 note from jackreichert in comment:6 against current trunk (6.9). Both
 reported symptoms are resolved:

 1. The "There is an autosave of this post that is more recent than the
    version below. View the autosave" notice is shown after a takeover.

 2. The notice is rendered by the standard autosave check on the edit
    screen — independent of how the editor was loaded — so the takeover
    path inherits it automatically. The check lives in both editor
    bootstrap files:

    - Classic editor: `src/wp-admin/edit-form-advanced.php`, the
      `wp_get_post_autosave()` call followed by the
      `mysql2date( 'U', $autosave->post_modified_gmt, false ) >
      mysql2date( 'U', $post->post_modified_gmt, false )` comparison
      that emits the "View the autosave" notice.

    - Block editor: `src/wp-admin/edit-form-blocks.php`, same timestamp
      comparison feeding the editor's autosave-exists state.

    `_admin_notice_post_locked()` in `src/wp-admin/includes/post.php`
    handles only the takeover modal itself and does not need to be
    autosave-aware — by the time the takeover redirect lands on the
    edit screen, the autosave check above runs as it would for any
    other load.

 3. The residual race — User A hasn't autosaved yet when User B clicks
    "Take over", so there is no server-side autosave for User B to be
    offered — was acknowledged as architectural in comment:1 (autosave
    runs on a fixed interval, A's pending changes only persist after
    B has already loaded) and explicitly declined as a fix path in
    comment:3 (the "request to take over" handshake was rejected at
    dev-chat). User A's unsaved keystrokes only exist in their browser
    at that moment; there is nothing on the server for core to load.

 The related concern about User A's stale tab continuing to autosave
 after a takeover and clobbering User B's changes is a different bug
 and is tracked in #55659; it shouldn't gate this ticket.

 Suggesting `worksforme` as the resolution.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/24552#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 21:51:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 21:51:34 -0000
Subject: [wp-trac] [WordPress Trac] #65145: Plugins: Display plugin
 slug/identifier in Installed Plugins row meta
In-Reply-To: <052.c963c996c75cb96bcb429195e4caec32@wordpress.org>
References: <052.c963c996c75cb96bcb429195e4caec32@wordpress.org>
Message-ID: <067.ec7acc89f39b49bcbcc25431679a78d6@wordpress.org>

#65145: Plugins: Display plugin slug/identifier in Installed Plugins row meta
--------------------------------------+-----------------------------
 Reporter:  crweiner                  |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Future Release
Component:  Plugins                   |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  administration
--------------------------------------+-----------------------------

Comment (by crweiner):

 As above, I had a slightly different implementation, and opened this PR:
 https://github.com/WordPress/wordpress-develop/pull/11780

 The main difference is that this patch adds a hidden-by-default `File`
 column using `$plugin_file`, instead of adding a `Slug` column. And it ads
 it at the end of the plugin table.

 I also noticed a bug with the "Automatic Updates" Screen Option
 responsiveness on small/mobile devices, and patched that as a part of this
 PR as well.

 This PR also adds PHPUnit coverage, per the Automated Testing handbook:
 https://make.wordpress.org/core/handbook/testing/automated-testing/

 This is my first time attempting to contribute code to WP.org and did use
 AI for assistance, as disclosed in the PR.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65145#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May  8 23:53:56 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 08 May 2026 23:53:56 -0000
Subject: [wp-trac] [WordPress Trac] #65208: Introduce namespacing for
 the test classes for 7.1
In-Reply-To: <051.7cf0adfda1ef78da6d78fc912696ab00@wordpress.org>
References: <051.7cf0adfda1ef78da6d78fc912696ab00@wordpress.org>
Message-ID: <066.64616b3db2f11e7cc2485ee7c481cbb0@wordpress.org>

#65208: Introduce namespacing for the test classes for 7.1
------------------------------+---------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  7.1
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:  tests
------------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"62342" 62342]:
 {{{
 #!CommitTicketReference repository="" revision="62342"
 Tests: Rename some newly added files as per the proposed directory
 structure.

 This aims to make the test suite directory and file structure more
 intuitive for new contributors to work with, as well as follow the PHPUnit
 recommended test class name pattern with having `Test` as the end of the
 class name.

 Follow-up to [61407], [62096], [62297], [62313], [62328].

 See #65208.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65208#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 00:02:43 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 00:02:43 -0000
Subject: [wp-trac] [WordPress Trac] #40199: Customize: collapse
 suggested and previously uploaded header images with accordions
In-Reply-To: <060.eaba736056d3ea9a0b2f38e37835d701@wordpress.org>
References: <060.eaba736056d3ea9a0b2f38e37835d701@wordpress.org>
Message-ID: <075.a02e63f5ae5776f95a6ae4088f22872f@wordpress.org>

#40199: Customize: collapse suggested and previously uploaded header images with
accordions
-------------------------------+-------------------------
 Reporter:  celloexpressions   |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Customize          |     Version:  3.9
 Severity:  normal             |  Resolution:  maybelater
 Keywords:  needs-patch close  |     Focuses:  ui
-------------------------------+-------------------------
Changes (by sabernhardt):

 * status:  new => closed
 * resolution:   => maybelater
 * milestone:  Future Release =>


Comment:

 This might still be worth revisiting later (after #36581), but I agree to
 close the ticket for now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40199#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 00:04:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 00:04:49 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.efd167cb1c17f4654af54c08d4eda18e@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch commit            |  administration
-------------------------------------+-------------------------------------

Comment (by 369work):

 I'd like to suggest a structural fix that prevents the overlap from
 recurring regardless of locale or button label length.

 The current layout breaks differently depending on screen width:

  * '''Desktop (>1100px):''' `.action-links` is `position: absolute; width:
 120px`. "Install Now" fits, but translated labels — "今すぐインストール"
 (JA), "Jetzt installieren" (DE), "Installer maintenant" (FR) — overflow
 into the description area.
  * '''Tablet (782–1100px):''' Switches to `position: static; margin-left:
 148px`, which avoids the overlap but crushes the plugin name into an
 extremely narrow column, causing it to wrap across many lines.
  * '''Mobile (<480px):''' Same `margin-left: 148px` rule applies. The
 description area is also unnecessarily narrow.

 In short, there is no viewport width where the current layout works
 correctly.

 '''Proposed fix: CSS only — no PHP or HTML changes required'''

 Instead of fighting the existing `position: absolute` on `.action-links`,
 we keep it and simply move the button coordinates to sit directly below
 the plugin icon. The description's unnecessary `margin-right` compensation
 is also removed.

 Tested on desktop (Nest Hub Max 1280×800 where the overlap was confirmed)
 and mobile (375px).

 (See attached screenshots: desktop before/after and mobile before/after.)

 {{{
 /* Desktop: move button below icon, remove description margin compensation
 */
 @media (min-width: 1101px) {
     .plugin-card .action-links {
         position: absolute;
         top: 152px;
         left: 20px;
         right: auto;
         width: 128px;
     }
     .plugin-card .desc > p, .plugin-card .name {
         margin-right: 0;
     }
 }

 /* Tablet and mobile: widen description area */
 @media (max-width: 1100px) and (min-width: 782px), (max-width: 480px) {
     .plugin-card .action-links {
         margin-left: 148px;
         width: calc(100% - 148px);
     }
     .plugin-card .desc > p {
         margin-left: 0;
     }
 }
 }}}

 This approach:
  * Permanently fixes the overlap for all locales on desktop
  * Improves the description width on tablet and mobile
  * Changes only `wp-admin/css/list-table.css` — no PHP or HTML
 modifications required

 Happy to prepare a formal patch if this direction looks good.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 00:08:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 00:08:19 -0000
Subject: [wp-trac] [WordPress Trac] #54660: Comment is missing for the
 bulk_footer function
In-Reply-To: <057.90c54554c94c7534a909dc1a82c58a86@wordpress.org>
References: <057.90c54554c94c7534a909dc1a82c58a86@wordpress.org>
Message-ID: <072.bd9879447573bcdb444785815c8fa7aa@wordpress.org>

#54660: Comment is missing for the bulk_footer function
----------------------------+---------------------
 Reporter:  yagniksangani   |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  6.6
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:  fixed
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------
Changes (by sabernhardt):

 * milestone:  Awaiting Review => 6.6


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54660#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 00:10:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 00:10:10 -0000
Subject: [wp-trac] [WordPress Trac] #49526: Misaligned theme count on
 Add Themes screen on iPhone X
In-Reply-To: <054.3c38ce0c1cda33c9918d2c0825c81527@wordpress.org>
References: <054.3c38ce0c1cda33c9918d2c0825c81527@wordpress.org>
Message-ID: <069.cf6b6c8eac7c524ce934b96dd30f21ee@wordpress.org>

#49526: Misaligned theme count on Add Themes screen on iPhone X
---------------------------------------+---------------------------------
 Reporter:  sumitsingh                 |       Owner:  (none)
     Type:  defect (bug)               |      Status:  closed
 Priority:  normal                     |   Milestone:  6.8
Component:  Themes                     |     Version:
 Severity:  normal                     |  Resolution:  fixed
 Keywords:  has-screenshots has-patch  |     Focuses:  ui, administration
---------------------------------------+---------------------------------
Changes (by sabernhardt):

 * milestone:  Awaiting Review => 6.8


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49526#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 00:12:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 00:12:22 -0000
Subject: [wp-trac] [WordPress Trac] #65158: Tortoise appears to be
 granting access to folders that don't belong to the user
In-Reply-To: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
References: <054.c018c65f2236eaf539abcd3dab4274bc@wordpress.org>
Message-ID: <069.4171f30467d0bde3532074ea1b9ff2ab@wordpress.org>

#65158: Tortoise appears to be granting access to folders that don't belong to the
user
--------------------------+----------------------
 Reporter:  pontocinza    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  6.9.4
 Severity:  major         |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by sabernhardt):

 * milestone:  Awaiting Review =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65158#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 00:13:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 00:13:10 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.bccefe1d342bffc6b1d4065940007e34@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch commit            |  administration
-------------------------------------+-------------------------------------

Comment (by 369work):

 [Imgur](https://imgur.com/RputFFi)
 [Imgur](https://imgur.com/AFawwEm)
 [Imgur](https://imgur.com/eloOGOk)
 [Imgur](https://imgur.com/4yVXIor)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 07:34:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 07:34:53 -0000
Subject: [wp-trac] [WordPress Trac] #65088: Toolbar: Replace home
 dashicon with site icon in the admin bar
In-Reply-To: <052.76cb989887be1f889167c61a5aa6324a@wordpress.org>
References: <052.76cb989887be1f889167c61a5aa6324a@wordpress.org>
Message-ID: <067.b44d7786f8f20f0b1e444fdf43477af0@wordpress.org>

#65088: Toolbar: Replace home dashicon with site icon in the admin bar
-------------------------+-------------------------------------
 Reporter:  lucasmdo     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Toolbar      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, css
-------------------------+-------------------------------------
Changes (by fushar):

 * Attachment "Screenshot 2026-05-09 at 14.33.46.png" added.

 site-icon-before-after

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65088>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 07:37:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 07:37:42 -0000
Subject: [wp-trac] [WordPress Trac] #65088: Toolbar: Replace home
 dashicon with site icon in the admin bar
In-Reply-To: <052.76cb989887be1f889167c61a5aa6324a@wordpress.org>
References: <052.76cb989887be1f889167c61a5aa6324a@wordpress.org>
Message-ID: <067.d50f08a7f4a1986b681294c143712963@wordpress.org>

#65088: Toolbar: Replace home dashicon with site icon in the admin bar
-------------------------+-------------------------------------
 Reporter:  lucasmdo     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Toolbar      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, css
-------------------------+-------------------------------------

Comment (by fushar):

 Hi @lucasmdo let's start with showing site icon when it's set, and keep
 the original behavior (home/odometer dashicon) if not set. I opened
 https://github.com/WordPress/wordpress-develop/pull/11781 for that.

 I think we can tackle the generated one-letter site icon as separate
 ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65088#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 09:44:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 09:44:33 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.775e36cbcb6bcffc27de8bf9ad91ac5b@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch commit            |  administration
-------------------------------------+-------------------------------------
Changes (by huzaifaalmesbah):

 * Attachment "Huzaifa-20260509153909.png" added.

 Hi, this issue is still present. I checked on 7.0 RC3 at 1280 px and 1600
 px resolutions, and I can see the issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 11:46:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 11:46:39 -0000
Subject: [wp-trac] [WordPress Trac] #65212: Uncaught exception TypeError in
 formatting.php
Message-ID: <056.8ec695052ef9f9dd0ec6d09ae69f7db7@wordpress.org>

#65212: Uncaught exception TypeError in formatting.php
--------------------------+-----------------------------
 Reporter:  harishtewari  |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  6.9.4
 Severity:  critical      |   Keywords:  has-patch
  Focuses:                |
--------------------------+-----------------------------
 Error message:
 Uncaught exception 'TypeError' with message 'strip_tags(): Argument #1
 ($string) must be of type string, array given' in /var/www/wp-
 includes/formatting.php

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65212>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 13:03:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 13:03:17 -0000
Subject: [wp-trac] [WordPress Trac] #65209: Connectors: Expose
 isFileModDisabled flag to connector script module data.
In-Reply-To: <060.cb590e149a9788ce40c3331ee619316f@wordpress.org>
References: <060.cb590e149a9788ce40c3331ee619316f@wordpress.org>
Message-ID: <075.c5672f2237dc63eb8f2934a81446e150@wordpress.org>

#65209: Connectors: Expose isFileModDisabled flag to connector script module data.
----------------------------------------------------+---------------------
 Reporter:  jorgefilipecosta                        |       Owner:  (none)
     Type:  defect (bug)                            |      Status:  new
 Priority:  normal                                  |   Milestone:  7.0
Component:  General                                 |     Version:  trunk
 Severity:  normal                                  |  Resolution:
 Keywords:  has-patch dev-reviewed gutenberg-merge  |     Focuses:
----------------------------------------------------+---------------------
Changes (by wildworks):

 * keywords:  has-patch => has-patch dev-reviewed gutenberg-merge


Comment:

 r62341 looks good to be backported to 7.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65209#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 13:06:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 13:06:27 -0000
Subject: [wp-trac] [WordPress Trac] #65073: Connectors: reference to AI
 plugin uses old `ai` slug instead of correct `ai-wp-admin` slug
In-Reply-To: <052.ad97c034b09747ca93f06d7293e387ff@wordpress.org>
References: <052.ad97c034b09747ca93f06d7293e387ff@wordpress.org>
Message-ID: <067.5228b2d76606642dfa7cbd2fd5cc4c45@wordpress.org>

#65073: Connectors: reference to AI plugin uses old `ai` slug instead of correct
`ai-wp-admin` slug
--------------------------+----------------------
 Reporter:  JeffPaul      |       Owner:  dkotter
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  7.0
Component:  AI            |     Version:  trunk
 Severity:  normal        |  Resolution:  fixed
 Keywords:  connectors    |     Focuses:
--------------------------+----------------------
Changes (by wildworks):

 * keywords:  connectors close => connectors
 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 Confirmed that the Connectors page is linking to the correct AI plugin
 settings page in 7.0 RC3.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65073#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 13:51:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 13:51:22 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.74d1e8ed648cd6c29e8f6e5f5bfbff66@wordpress.org>

#65211: Font upload shows failure message but font is added to library
---------------------------+------------------------------
 Reporter:  369work        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------

Comment (by wildworks):

 I tried using [https://fonts.google.com/noto/specimen/Noto+Serif+JP Noto
 Serif Japanese], but I couldn't reproduce the issue. Information like the
 following would be helpful in identifying the problem:

 - Where did you download the font from?
 - Does this issue occur with fonts other than Japanese fonts?
 - Does this issue occur with WordPress versions 6.9 and below?
 - Does the problem occur across all browsers?
 - Does the same issue occur in the Site Editor and the Global Styles
 sidebar?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 14:16:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 14:16:19 -0000
Subject: [wp-trac] [WordPress Trac] #65212: Uncaught exception TypeError
 in formatting.php
In-Reply-To: <056.8ec695052ef9f9dd0ec6d09ae69f7db7@wordpress.org>
References: <056.8ec695052ef9f9dd0ec6d09ae69f7db7@wordpress.org>
Message-ID: <071.15156254b5712adc7b84fab8b90222ce@wordpress.org>

#65212: Uncaught exception TypeError in formatting.php
--------------------------+------------------------------
 Reporter:  harishtewari  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------
Changes (by knutsp):

 * severity:  critical => normal


Comment:

 This is not a bug. The patch will just hide the error.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65212#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 14:16:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 14:16:54 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.a7d4453df5d4ba6acd5e46475a9d298e@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch                   |  administration
-------------------------------------+-------------------------------------
Changes (by wildworks):

 * keywords:  has-screenshots admin-reskin has-patch commit => has-
     screenshots admin-reskin has-patch


Comment:

 It appears that two issues are being discussed here.


 The first issue is the spacing between the plugin header and the plugin
 description text. This problem should have been resolved in both [61729]
 and [62290].

 The second issue is that the plugin title and the "Install Now" button
 overlap. This problem became prominent with the introduction of the new
 design system in WordPress 7.0, but it was likely a latent issue that
 existed before. Therefore, strictly speaking, there are no longer any new
 regressions occurring in 7.0.

 The second issue is that there's no fundamental solution as long as
 [https://github.com/WordPress/wordpress-
 develop/blob/9f32f0d5b4dbfd95c71cd29a165b4dcbc7a8cae6/src/wp-admin/css
 /list-tables.css#L1682-L1687 the plugin action links are absolutely
 positioned]. This is because even if we change the margins or width to
 avoid overlap, it may not be optimal for all locales.

 It would be best to rebuild the entire plugin card using a flex layout,
 but I'm unsure if that would be acceptable for the 7.0 release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 16:24:35 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 16:24:35 -0000
Subject: [wp-trac] [WordPress Trac] #64848: WP_Theme_JSON: Prevent
 implicit coercion in to_ruleset
In-Reply-To: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
References: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
Message-ID: <069.cc56e672399ce3e19c494486e55ff6c2@wordpress.org>

#64848: WP_Theme_JSON: Prevent implicit coercion in to_ruleset
-------------------------------------------------+-------------------------
 Reporter:  ramonopoly                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Themes                               |     Version:  5.8
 Severity:  minor                                |  Resolution:
 Keywords:  has-patch gutenberg-merge has-unit-  |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------

Comment (by Presskopp):

 The warning mentioned in [#3] is appearing for a split second when you
 edit a post under PHP 8.5.1 (WP 7.0-RC3-62340)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64848#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 16:29:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 16:29:14 -0000
Subject: [wp-trac] [WordPress Trac] #64848: WP_Theme_JSON: Prevent
 implicit coercion in to_ruleset
In-Reply-To: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
References: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
Message-ID: <069.33ddf275cede068a2ae7663cd34c02c6@wordpress.org>

#64848: WP_Theme_JSON: Prevent implicit coercion in to_ruleset
-------------------------------------------------+-------------------------
 Reporter:  ramonopoly                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Themes                               |     Version:  5.8
 Severity:  minor                                |  Resolution:
 Keywords:  has-patch gutenberg-merge has-unit-  |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------
Changes (by Presskopp):

 * Attachment "deprecated.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64848>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 16:40:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 16:40:01 -0000
Subject: [wp-trac] [WordPress Trac] #64848: WP_Theme_JSON: Prevent
 implicit coercion in to_ruleset
In-Reply-To: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
References: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
Message-ID: <069.1b9998c5ca1f688ec350f78c254d6b1f@wordpress.org>

#64848: WP_Theme_JSON: Prevent implicit coercion in to_ruleset
-------------------------------------------------+-------------------------
 Reporter:  ramonopoly                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Themes                               |     Version:  5.8
 Severity:  minor                                |  Resolution:
 Keywords:  has-patch gutenberg-merge has-unit-  |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------

Comment (by Presskopp):

 see https://github.com/WordPress/gutenberg/issues/78124

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64848#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 18:23:26 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 18:23:26 -0000
Subject: [wp-trac] [WordPress Trac] #65213: Uncaught exception 'Error' with
 message 'Call to undefined function get_the_block_template_html()
Message-ID: <056.56f8bfd20d598a94cdf522ad07953c09@wordpress.org>

#65213: Uncaught exception 'Error' with message 'Call to undefined function
get_the_block_template_html()
--------------------------+-----------------------------
 Reporter:  harishtewari  |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  trunk
 Severity:  normal        |   Keywords:  has-patch
  Focuses:  performance   |
--------------------------+-----------------------------
 Error message:

 Uncaught exception 'Error' with message 'Call to undefined function
 get_the_block_template_html()' in /var/www/wp-includes/template-
 canvas.php:12

 https://github.com/WordPress/wordpress-develop/pull/11784

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65213>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 19:21:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 19:21:01 -0000
Subject: [wp-trac] [WordPress Trac] #65213: Uncaught exception 'Error'
 with message 'Call to undefined function get_the_block_template_html()
In-Reply-To: <056.56f8bfd20d598a94cdf522ad07953c09@wordpress.org>
References: <056.56f8bfd20d598a94cdf522ad07953c09@wordpress.org>
Message-ID: <071.f92717a4325074c8aa8875335f98d740@wordpress.org>

#65213: Uncaught exception 'Error' with message 'Call to undefined function
get_the_block_template_html()
--------------------------+------------------------------
 Reporter:  harishtewari  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------
Changes (by westonruter):

 * focuses:  performance =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65213#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 19:23:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 19:23:16 -0000
Subject: [wp-trac] [WordPress Trac] #65213: Uncaught exception 'Error'
 with message 'Call to undefined function get_the_block_template_html()
In-Reply-To: <056.56f8bfd20d598a94cdf522ad07953c09@wordpress.org>
References: <056.56f8bfd20d598a94cdf522ad07953c09@wordpress.org>
Message-ID: <071.38090deec306bd3bb4efeae0305d22af@wordpress.org>

#65213: Uncaught exception 'Error' with message 'Call to undefined function
get_the_block_template_html()
-----------------------------+------------------------------
 Reporter:  harishtewari     |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |     Focuses:
-----------------------------+------------------------------
Changes (by westonruter):

 * keywords:  has-patch => has-patch close


Comment:

 The function should always exist there. If it doesn't for you, then
 something strange is going on. The fix isn't what you proposed in the
 attached PR.

 This should probably get closed as invalid.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65213#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 20:14:26 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 20:14:26 -0000
Subject: [wp-trac] [WordPress Trac] #65213: Uncaught exception 'Error'
 with message 'Call to undefined function get_the_block_template_html()
In-Reply-To: <056.56f8bfd20d598a94cdf522ad07953c09@wordpress.org>
References: <056.56f8bfd20d598a94cdf522ad07953c09@wordpress.org>
Message-ID: <071.95488c37d36fb3edb2147a5e6d359311@wordpress.org>

#65213: Uncaught exception 'Error' with message 'Call to undefined function
get_the_block_template_html()
-----------------------------+------------------------
 Reporter:  harishtewari     |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:  duplicate
 Keywords:  has-patch close  |     Focuses:
-----------------------------+------------------------
Changes (by westonruter):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 Ah, well the issue is probably that someone is making a direct request to
 `/wp-includes/template-canvas.php`. Since this doesn't load WordPress, it
 doesn't require any other files that have this function defined. This is
 hardly unique to `template-canvas.php`, however. The same thing happens
 when attempting to access `/wp-includes/template-canvas.php` or many other
 PHP files in WordPress core. This has previously been reported. I'm
 closing this as a duplicate of #62722.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65213#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 21:58:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 21:58:19 -0000
Subject: [wp-trac] [WordPress Trac] #65213: Uncaught exception 'Error'
 with message 'Call to undefined function get_the_block_template_html()
In-Reply-To: <056.56f8bfd20d598a94cdf522ad07953c09@wordpress.org>
References: <056.56f8bfd20d598a94cdf522ad07953c09@wordpress.org>
Message-ID: <071.697f6d69a96e16dccb426f789e22036d@wordpress.org>

#65213: Uncaught exception 'Error' with message 'Call to undefined function
get_the_block_template_html()
-----------------------------+------------------------
 Reporter:  harishtewari     |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:  duplicate
 Keywords:  has-patch close  |     Focuses:
-----------------------------+------------------------

Comment (by szepe.viktor):

 Try blocking request to inner core files.
 Please see https://github.com/szepeviktor/debian-server-
 tools/blob/master/webserver/apache-conf-
 available/wordpress.inc.conf#L13-L85

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65213#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 22:23:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 22:23:49 -0000
Subject: [wp-trac] [WordPress Trac] #65214: Refine the help text wording for
 backend editor
Message-ID: <052.d2683f1a171f23484391f486bd93f219@wordpress.org>

#65214: Refine the help text wording for backend editor
-------------------------------+-----------------------------
 Reporter:  timse201           |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Administration     |    Version:
 Severity:  normal             |   Keywords:
  Focuses:  ui, accessibility  |
-------------------------------+-----------------------------
 actually we use the wording "The top section controls the editor within
 the dashboard" for the help text on wp-admin/options-writing.php:24.
 That's not very precise and confuses newcomers.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65214>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 22:53:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 22:53:37 -0000
Subject: [wp-trac] [WordPress Trac] #65203: Tests: Add unit tests for
 wp_check_php_version()
In-Reply-To: <051.d12790340ad3f067c63aa183a99c6f2c@wordpress.org>
References: <051.d12790340ad3f067c63aa183a99c6f2c@wordpress.org>
Message-ID: <066.06227ce722961c01cfba946240456ad6@wordpress.org>

#65203: Tests: Add unit tests for wp_check_php_version()
--------------------------------------+---------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65203#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat May  9 23:02:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 09 May 2026 23:02:05 -0000
Subject: [wp-trac] [WordPress Trac] #65203: Tests: Add unit tests for
 wp_check_php_version()
In-Reply-To: <051.d12790340ad3f067c63aa183a99c6f2c@wordpress.org>
References: <051.d12790340ad3f067c63aa183a99c6f2c@wordpress.org>
Message-ID: <066.d90bb0ae5c9c448d8c4bdb6b172899d7@wordpress.org>

#65203: Tests: Add unit tests for wp_check_php_version()
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  SergeyBiryukov
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62343" 62343]:
 {{{
 #!CommitTicketReference repository="" revision="62343"
 Tests: Add unit tests for `wp_check_php_version()`.

 Follow-up to [44735].

 Props pbearne.
 Fixes #65203.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65203#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 01:03:55 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 01:03:55 -0000
Subject: [wp-trac] [WordPress Trac] #65214: Refine the help text wording
 for backend editor
In-Reply-To: <052.d2683f1a171f23484391f486bd93f219@wordpress.org>
References: <052.d2683f1a171f23484391f486bd93f219@wordpress.org>
Message-ID: <067.260fdcc8820184560a571e8081d3d10c@wordpress.org>

#65214: Refine the help text wording for backend editor
--------------------------+------------------------------------------
 Reporter:  timse201      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Help/About    |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, administration, ui-copy
--------------------------+------------------------------------------
Changes (by sabernhardt):

 * focuses:  ui, accessibility => ui, administration, ui-copy
 * component:  Administration => Help/About


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65214#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 04:25:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 04:25:07 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.c0d903e56bc9225f51e946a97fca4ba4@wordpress.org>

#65211: Font upload shows failure message but font is added to library
---------------------------+------------------------------
 Reporter:  369work        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------

Comment (by 369work):

 Where did you download that font from?

 Google
 ------------- Does this problem occur with fonts other than Japanese
 fonts?

 It also occurred with newsreader-v26-latin.

 ------------- Does the same problem occur in the site editor and the
 global style sidebar?

 1. It occurs in "Appearance" > "Fonts".

 2. "Appearance" > "Editor" > "Style" > "Typography" > "Fonts" works fine.

 (The banner says "Fonts were installed successfully.")
 (I was surprised because I hadn't tried it.)
 ---------------------
 Does this problem occur in all browsers?

 It occurs in Edge.
 Chrome works fine.
 ---------------------
 I deleted the font and uploaded the same font in Edge, and it worked fine.
 This might be due to the success in Edge (step 2).
 I can no longer reproduce the error no matter how many times I delete it.

 ------------------------
 Does this also occur in versions prior to 6.9?

 1. I can't test it because "Appearance" > "Fonts" is not available.
 2. "Appearance" > "Editor" > "Style" > "Typography" > "Fonts"
 It worked correctly in Edge & Chrome.
 (The banner says "Fonts were installed successfully.")

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 10:08:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 10:08:49 -0000
Subject: [wp-trac] [WordPress Trac] #64817: Bump default theme versions
 for WordPress 7.0
In-Reply-To: <052.c63f6cd5170af975f4f240cb6bb1d2a1@wordpress.org>
References: <052.c63f6cd5170af975f4f240cb6bb1d2a1@wordpress.org>
Message-ID: <067.013bfa130ed79d3bb734c3de238d560b@wordpress.org>

#64817: Bump default theme versions for WordPress 7.0
----------------------------+-------------------------
 Reporter:  shailu25        |       Owner:  karmatosed
     Type:  task (blessed)  |      Status:  closed
 Priority:  normal          |   Milestone:  7.0
Component:  Bundled Theme   |     Version:
 Severity:  normal          |  Resolution:  fixed
 Keywords:  has-patch       |     Focuses:
----------------------------+-------------------------
Changes (by karmatosed):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62344" 62344]:
 {{{
 #!CommitTicketReference repository="" revision="62344"
 Bundled themes: Version bumps for version 7.0.

 This bumps the version for the upcoming release WordPress 7.0.
 Twenty Ten: 4.6.
 Twenty Eleven: 5.1.
 Twenty Twelve: 4.8.
 Twenty Thirteen: 4.6.
 Twenty Fourteen: 4.5.
 Twenty Fifteen: 4.2.
 Twenty Sixteen: 3.8.
 Twenty Seventeen: 4.1.
 Twenty Nineteen: 3.3.
 Twenty Twenty: 3.1.
 Twenty Twenty-One: 2.8.
 Twenty Twenty-Two: 2.1.
 Twenty Twenty-Three: 1.6.
 Twenty Twenty-Four: 1.5.
 Twenty Twenty-Five: 1.5.

 Props sabernhardt, shailu25, audrasjb.
 Fixes #64817.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64817#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 10:41:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 10:41:15 -0000
Subject: [wp-trac] [WordPress Trac] #64817: Bump default theme versions
 for WordPress 7.0
In-Reply-To: <052.c63f6cd5170af975f4f240cb6bb1d2a1@wordpress.org>
References: <052.c63f6cd5170af975f4f240cb6bb1d2a1@wordpress.org>
Message-ID: <067.e3ed32fede8ff6a478e82aaa9a05f827@wordpress.org>

#64817: Bump default theme versions for WordPress 7.0
----------------------------+-------------------------
 Reporter:  shailu25        |       Owner:  karmatosed
     Type:  task (blessed)  |      Status:  reopened
 Priority:  normal          |   Milestone:  7.0
Component:  Bundled Theme   |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-------------------------
Changes (by shailu25):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I think this should be considered for backport, so I’m reopening this
 ticket. (same as previous theme tickets)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64817#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 12:42:40 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 12:42:40 -0000
Subject: [wp-trac] [WordPress Trac] #65103: Single-page admin screens
 (Connectors,
 Font Library) fail to mount in Chrome when @wordpress/boot wins a race
 against its classic-script deps
In-Reply-To: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
References: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
Message-ID: <070.844483ac3a24aadbe3b3586f53b324c6@wordpress.org>

#65103: Single-page admin screens (Connectors, Font Library) fail to mount in
Chrome when @wordpress/boot wins a race against its classic-script deps
-------------------------------------------------+-------------------------
 Reporter:  fabiankaegy                          |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  Script Loader                        |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  script-modules has-patch changes-    |     Focuses:
  requested                                      |  administration
-------------------------------------------------+-------------------------

Comment (by khokansardar):

 hey @jorbin I've added the changes here - https://github.com/WordPress
 /wordpress-
 develop/pull/11611/changes/94a8ed5f4f6a99e3651b36d1a298652794a37b6d Could
 you please take a look. Replying to [comment:7 jorbin]:
 > As this issues means that a new 7.0 feature is broken, I am bumping up
 the prioirty.
 >
 > @khokansardar are you able to follow up on the changes that @westonruter
 suggested above?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65103#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 16:07:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 16:07:05 -0000
Subject: [wp-trac] [WordPress Trac] #65103: Single-page admin screens
 (Connectors,
 Font Library) fail to mount in Chrome when @wordpress/boot wins a race
 against its classic-script deps
In-Reply-To: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
References: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
Message-ID: <070.21eb8acf8875e7479c3ec958e64f8341@wordpress.org>

#65103: Single-page admin screens (Connectors, Font Library) fail to mount in
Chrome when @wordpress/boot wins a race against its classic-script deps
-------------------------------------------------+-------------------------
 Reporter:  fabiankaegy                          |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  Script Loader                        |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  script-modules has-patch changes-    |     Focuses:
  requested                                      |  administration
-------------------------------------------------+-------------------------

Comment (by westonruter):

 @khokansardar These changes need to be made in the Gutenberg repo, as far
 as I know.

 This is the template code needing to be modified:
 https://github.com/WordPress/gutenberg/blob/5fc7223e96b2751c57b6c4ae840bb9e838bee9f0/packages
 /wp-build/templates/page-wp-admin.php.template#L156-L164

 Note that you can also now indent the PHP nowdoc strings with the
 [https://wiki.php.net/rfc/flexible_heredoc_nowdoc_syntaxes flexible
 syntax] thanks to WordPress increasing the minimum PHP version to 7.4.

 So you can indent consistently like this, adding indents to your patch:

 {{{#!php
 <?php
                 /*
                  * Add inline script to initialize the app using
 initSinglePage (no menuItems).
                  * The dynamic import is deferred until DOMContentLoaded
 so that all classic
                  * script dependencies of @wordpress/boot (wp-private-
 apis, wp-components,
                  * wp-theme, etc.) have finished parsing and executing
 before the boot module
                  * evaluates. Otherwise, a modulepreloaded @wordpress/boot
 can win the race
                  * against the classic-script-printing pass on fast CDN-
 fronted hosts in
                  * Chrome, evaluating before wp.theme.privateApis is
 defined and throwing
                  * "Cannot unlock an undefined object". See #65103.
                  */
                 $init_js_function = <<<'JS'
                 ( mountId, routes ) => {
                         const run = async () => {
                                 const mod = await import(
 "@wordpress/boot" );
                                 mod.initSinglePage( { mountId, routes } );
                         };
                         if ( document.readyState === "loading" ) {
                                 document.addEventListener(
 "DOMContentLoaded", run );
                         } else {
                                 run();
                         }
                 }
                 JS;
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65103#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 22:02:35 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 22:02:35 -0000
Subject: [wp-trac] [WordPress Trac] #65215: Connectors: REST API responses
 on the Connectors screen should be preloaded
Message-ID: <055.ffa9695b8ee4a5ec363fdcb07d69a8ff@wordpress.org>

#65215: Connectors: REST API responses on the Connectors screen should be preloaded
--------------------------+-------------------------
 Reporter:  westonruter   |      Owner:  westonruter
     Type:  defect (bug)  |     Status:  assigned
 Priority:  normal        |  Milestone:  7.0
Component:  AI            |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:  performance   |
--------------------------+-------------------------
 For screenshots and for what this backports, see
 [https://github.com/WordPress/gutenberg/pull/77353 Gutenberg PR].

 == What? ==

 The Connectors screen (`options-general.php?page=options-connectors-wp-
 admin`) fires several REST API requests after hydration, delaying the
 Largest Contentful Paint.

 Specifically: `GET /wp/v2/settings` (site entity), `OPTIONS
 /wp/v2/plugins` (the `canUser( 'create', 'plugin' )` check), a hardcoded
 `GET /wp/v2/plugins/ai/ai` used by the AI-plugin callout, and one `GET
 /wp/v2/plugins/<basename>` per registered connector — five sequential
 round-trips with the default connectors.

 == Why? ==

 These responses are all trivially knowable at render time on the server,
 so they should be embedded in the initial HTML via
 `createPreloadingMiddleware` rather than re-fetched by the client after
 hydration. This also reduces the number of requests on the server,
 reducing server load.

 === Measured impact (median LCP over 10 runs) ===

 || '''Scenario''' || '''Trunk''' || '''This PR''' || '''Δ''' ||
 || Fast 4G || 1523 ms || 1150 ms || −373 ms (≈24.5%) ||
 || No throttling || 743 ms || 518 ms || −225 ms (≈30.3%) ||

 == How? ==

 Adds a `{page-slug}-wp-admin_preload_paths` filter to the `wp-build`
 `page-wp-admin` template so any generated admin page can register page-
 specific preload paths. Hooks it in the Connectors loader to preload the
 five paths listed in '''What?''' above (the existing hardcoded preload in
 the template only covers the root site fields, not the settings entity the
 UI actually resolves, so `/wp/v2/settings` is added too).

 After the change, none of the connector-related REST requests fire on page
 load — they are served from the preload middleware.

 The two remaining requests come from `@wordpress/core-abilities`, which
 Gutenberg enqueues on every admin page — out of scope here, but a
 candidate for similar preloading.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65215>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 22:58:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 22:58:13 -0000
Subject: [wp-trac] [WordPress Trac] #65202: Tests: Add unit tests for
 _wp_privacy_settings_filter_draft_page_titles()
In-Reply-To: <051.9948697a3015d1530eb133401e5eefa7@wordpress.org>
References: <051.9948697a3015d1530eb133401e5eefa7@wordpress.org>
Message-ID: <066.7675f44922999e3ed45c33898cbed863@wordpress.org>

#65202: Tests: Add unit tests for _wp_privacy_settings_filter_draft_page_titles()
--------------------------------------+---------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65202#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 23:01:23 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 23:01:23 -0000
Subject: [wp-trac] [WordPress Trac] #65202: Tests: Add unit tests for
 _wp_privacy_settings_filter_draft_page_titles()
In-Reply-To: <051.9948697a3015d1530eb133401e5eefa7@wordpress.org>
References: <051.9948697a3015d1530eb133401e5eefa7@wordpress.org>
Message-ID: <066.ef11a491967cb8146850827e3a69bc13@wordpress.org>

#65202: Tests: Add unit tests for _wp_privacy_settings_filter_draft_page_titles()
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  SergeyBiryukov
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62345" 62345]:
 {{{
 #!CommitTicketReference repository="" revision="62345"
 Tests: Add unit tests for
 `_wp_privacy_settings_filter_draft_page_titles()`.

 Follow-up to [43376].

 Props pbearne.
 Fixes #65202.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65202#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun May 10 23:42:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 10 May 2026 23:42:38 -0000
Subject: [wp-trac] [WordPress Trac] #65202: Tests: Add unit tests for
 _wp_privacy_settings_filter_draft_page_titles()
In-Reply-To: <051.9948697a3015d1530eb133401e5eefa7@wordpress.org>
References: <051.9948697a3015d1530eb133401e5eefa7@wordpress.org>
Message-ID: <066.a3acc1293b1b8bfd78cb97d5e889b96d@wordpress.org>

#65202: Tests: Add unit tests for _wp_privacy_settings_filter_draft_page_titles()
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  SergeyBiryukov
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 In [changeset:"62346" 62346]:
 {{{
 #!CommitTicketReference repository="" revision="62346"
 Coding Standards: Correct alignment in
 `_wp_privacy_settings_filter_draft_page_titles()` tests.

 This resolves a WPCS warning:
 {{{
 Array double arrow not aligned correctly
 }}}

 Follow-up to [62345].

 Props peterwilsoncc.
 See #65202.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65202#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:03:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:03:24 -0000
Subject: [wp-trac] [WordPress Trac] #65216: There has been a critical error
 on our website
Message-ID: <061.3b70f206114fd3e9ede374e00d62f281@wordpress.org>

#65216: There has been a critical error on our website
-------------------------------+-----------------------------
 Reporter:  socialshatsonline  |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  General            |    Version:
 Severity:  normal             |   Keywords:
  Focuses:                     |
-------------------------------+-----------------------------
 There has been a critical error on our website. [[Image(Screenshot
 2026-05-11 at 8.00.53 AM)]][doree.com.au]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65216>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:03:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:03:42 -0000
Subject: [wp-trac] [WordPress Trac] #65216: There has been a critical
 error on our website
In-Reply-To: <061.3b70f206114fd3e9ede374e00d62f281@wordpress.org>
References: <061.3b70f206114fd3e9ede374e00d62f281@wordpress.org>
Message-ID: <076.a84eb85b8226451c37b79518019f122e@wordpress.org>

#65216: There has been a critical error on our website
-------------------------------+------------------------------
 Reporter:  socialshatsonline  |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  General            |     Version:
 Severity:  normal             |  Resolution:
 Keywords:                     |     Focuses:
-------------------------------+------------------------------
Changes (by socialshatsonline):

 * Attachment "Screenshot 2026-05-11 at 8.00.53 AM.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65216>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:13:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:13:49 -0000
Subject: [wp-trac] [WordPress Trac] #65215: Connectors: REST API
 responses on the Connectors screen should be preloaded
In-Reply-To: <055.ffa9695b8ee4a5ec363fdcb07d69a8ff@wordpress.org>
References: <055.ffa9695b8ee4a5ec363fdcb07d69a8ff@wordpress.org>
Message-ID: <070.578c7b93c0e65e528851e779fd576704@wordpress.org>

#65215: Connectors: REST API responses on the Connectors screen should be preloaded
--------------------------------------+------------------------------------
 Reporter:  westonruter               |       Owner:  westonruter
     Type:  defect (bug)              |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.0
Component:  AI                        |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  rest-api, performance
--------------------------------------+------------------------------------
Changes (by westonruter):

 * focuses:  performance => rest-api, performance


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65215#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:31:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:31:06 -0000
Subject: [wp-trac] [WordPress Trac] #65206: Site Editor: preload initial
 canvas REST data
In-Reply-To: <054.e66da5fd138b4a58b8bd59be08147558@wordpress.org>
References: <054.e66da5fd138b4a58b8bd59be08147558@wordpress.org>
Message-ID: <069.676adb0ef49c04b1db1c07e22d0fe4b4@wordpress.org>

#65206: Site Editor: preload initial canvas REST data
-------------------------+-----------------------------
 Reporter:  extrachill   |       Owner:  extrachill
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  Future Release
Component:  Editor       |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  performance
-------------------------+-----------------------------
Changes (by westonruter):

 * owner:  (none) => extrachill
 * status:  new => assigned
 * milestone:  Awaiting Review => Future Release


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65206#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:31:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:31:54 -0000
Subject: [wp-trac] [WordPress Trac] #65215: Connectors: REST API
 responses on the Connectors screen should be preloaded
In-Reply-To: <055.ffa9695b8ee4a5ec363fdcb07d69a8ff@wordpress.org>
References: <055.ffa9695b8ee4a5ec363fdcb07d69a8ff@wordpress.org>
Message-ID: <070.ea581730fd82c8c8103247c2e4402a06@wordpress.org>

#65215: Connectors: REST API responses on the Connectors screen should be preloaded
--------------------------------------+------------------------------------
 Reporter:  westonruter               |       Owner:  westonruter
     Type:  defect (bug)              |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.0
Component:  AI                        |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  rest-api, performance
--------------------------------------+------------------------------------

Comment (by westonruter):

 cc @chubes4 as this relates to #65206

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65215#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:35:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:35:25 -0000
Subject: [wp-trac] [WordPress Trac] #45194: [Gutenberg] Preload
 wp/v2/media using the OPTIONS method to manage `upload_files` capability
In-Reply-To: <049.78810533a003e36ade28451177cf1392@wordpress.org>
References: <049.78810533a003e36ade28451177cf1392@wordpress.org>
Message-ID: <064.c21c36fc94425633e55429c0b0f81d06@wordpress.org>

#45194: [Gutenberg] Preload wp/v2/media using the OPTIONS method to manage
`upload_files` capability
------------------------------------------------+--------------------------
 Reporter:  imath                               |       Owner:
                                                |  danielbachhuber
     Type:  enhancement                         |      Status:  closed
 Priority:  normal                              |   Milestone:  5.0
Component:  Editor                              |     Version:  5.0
 Severity:  normal                              |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests fixed-5.0  |     Focuses:  rest-api
------------------------------------------------+--------------------------

Comment (by westonruter):

 Follow-up: #65215, which goes beyond allowing the method to be specified
 to also allow non-OK responses to be sent to the preload middleware.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45194#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:37:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:37:14 -0000
Subject: [wp-trac] [WordPress Trac] #65215: Connectors: REST API
 responses on the Connectors screen should be preloaded
In-Reply-To: <055.ffa9695b8ee4a5ec363fdcb07d69a8ff@wordpress.org>
References: <055.ffa9695b8ee4a5ec363fdcb07d69a8ff@wordpress.org>
Message-ID: <070.967ca8d0db61c2202ef7b28021b53f3c@wordpress.org>

#65215: Connectors: REST API responses on the Connectors screen should be preloaded
--------------------------------------+------------------------------------
 Reporter:  westonruter               |       Owner:  westonruter
     Type:  defect (bug)              |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.0
Component:  AI                        |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  rest-api, performance
--------------------------------------+------------------------------------
Description changed by westonruter:

Old description:

> For screenshots and for what this backports, see
> [https://github.com/WordPress/gutenberg/pull/77353 Gutenberg PR].
>
> == What? ==
>
> The Connectors screen (`options-general.php?page=options-connectors-wp-
> admin`) fires several REST API requests after hydration, delaying the
> Largest Contentful Paint.
>
> Specifically: `GET /wp/v2/settings` (site entity), `OPTIONS
> /wp/v2/plugins` (the `canUser( 'create', 'plugin' )` check), a hardcoded
> `GET /wp/v2/plugins/ai/ai` used by the AI-plugin callout, and one `GET
> /wp/v2/plugins/<basename>` per registered connector — five sequential
> round-trips with the default connectors.
>
> == Why? ==
>
> These responses are all trivially knowable at render time on the server,
> so they should be embedded in the initial HTML via
> `createPreloadingMiddleware` rather than re-fetched by the client after
> hydration. This also reduces the number of requests on the server,
> reducing server load.
>
> === Measured impact (median LCP over 10 runs) ===
>
> || '''Scenario''' || '''Trunk''' || '''This PR''' || '''Δ''' ||
> || Fast 4G || 1523 ms || 1150 ms || −373 ms (≈24.5%) ||
> || No throttling || 743 ms || 518 ms || −225 ms (≈30.3%) ||
>
> == How? ==
>
> Adds a `{page-slug}-wp-admin_preload_paths` filter to the `wp-build`
> `page-wp-admin` template so any generated admin page can register page-
> specific preload paths. Hooks it in the Connectors loader to preload the
> five paths listed in '''What?''' above (the existing hardcoded preload in
> the template only covers the root site fields, not the settings entity
> the UI actually resolves, so `/wp/v2/settings` is added too).
>
> After the change, none of the connector-related REST requests fire on
> page load — they are served from the preload middleware.
>
> The two remaining requests come from `@wordpress/core-abilities`, which
> Gutenberg enqueues on every admin page — out of scope here, but a
> candidate for similar preloading.

New description:

 For screenshots and for what this backports, see
 [https://github.com/WordPress/gutenberg/pull/77353 Gutenberg PR].

 == What? ==

 The Connectors screen (`options-general.php?page=options-connectors-wp-
 admin`) fires several REST API requests after hydration, delaying the
 Largest Contentful Paint.

 Specifically: `GET /wp/v2/settings` (site entity), `OPTIONS
 /wp/v2/plugins` (the `canUser( 'create', 'plugin' )` check), a hardcoded
 `GET /wp/v2/plugins/ai/ai` used by the AI-plugin callout, and one `GET
 /wp/v2/plugins/<basename>` per registered connector — five sequential
 round-trips with the default connectors.

 == Why? ==

 These responses are all trivially knowable at render time on the server,
 so they should be embedded in the initial HTML via
 `createPreloadingMiddleware` rather than re-fetched by the client after
 hydration. This also reduces the number of requests on the server,
 reducing server load.

 === Measured impact (median LCP over 10 runs) ===

 || '''Scenario''' || '''Trunk''' || '''This PR''' || '''Δ''' ||
 || Fast 4G || 1523 ms || 1150 ms || −373 ms (≈24.5%) ||
 || No throttling || 743 ms || 518 ms || −225 ms (≈30.3%) ||

 == How? ==

 Adds a `{page-slug}-wp-admin_preload_paths` filter to the `wp-build`
 `page-wp-admin` template so any generated admin page can register page-
 specific preload paths. Hooks it in the Connectors loader to preload the
 five paths listed in '''What?''' above (the existing hardcoded preload in
 the template only covers the root site fields, not the settings entity the
 UI actually resolves, so `/wp/v2/settings` is added too).

 After the change, none of the connector-related REST requests fire on page
 load — they are served from the preload middleware.

 The two remaining requests come from `@wordpress/core-abilities`, which
 Gutenberg enqueues on every admin page — out of scope here, but a
 candidate for similar preloading.

 ----

 To achieve the following, REST API responses for `404 Not Found` need to
 be served to the preload middleware. This is a follow up to r44123 and
 r44172.

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65215#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:39:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:39:28 -0000
Subject: [wp-trac] [WordPress Trac] #64544: Core GB backport -
 individual block custom CSS
In-Reply-To: <056.72603e7ab1651a8e30467405450b7b4a@wordpress.org>
References: <056.72603e7ab1651a8e30467405450b7b4a@wordpress.org>
Message-ID: <071.a52d0533222fbc21169b6bd3bc996589@wordpress.org>

#64544: Core GB backport - individual block custom CSS
---------------------------------------+-----------------------
 Reporter:  glendaviesnz               |       Owner:  ellatrix
     Type:  enhancement                |      Status:  closed
 Priority:  normal                     |   Milestone:  7.0
Component:  General                    |     Version:  trunk
 Severity:  normal                     |  Resolution:  fixed
 Keywords:  has-patch gutenberg-merge  |     Focuses:
---------------------------------------+-----------------------

Comment (by westonruter):

 Performance follow-up in https://github.com/WordPress/wordpress-
 develop/pull/11686

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64544#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:51:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:51:49 -0000
Subject: [wp-trac] [WordPress Trac] #65103: Single-page admin screens
 (Connectors,
 Font Library) fail to mount in Chrome when @wordpress/boot wins a race
 against its classic-script deps
In-Reply-To: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
References: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
Message-ID: <070.e434a60b27580a2642046b26205b3606@wordpress.org>

#65103: Single-page admin screens (Connectors, Font Library) fail to mount in
Chrome when @wordpress/boot wins a race against its classic-script deps
-------------------------------------------------+-------------------------
 Reporter:  fabiankaegy                          |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  7.0
Component:  Script Loader                        |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  script-modules has-patch has-test-   |     Focuses:
  info                                           |  administration
-------------------------------------------------+-------------------------
Changes (by westonruter):

 * keywords:  script-modules has-patch changes-requested => script-modules
     has-patch has-test-info


Comment:

 I've adapted the changes over to a Gutenberg PR:
 https://github.com/WordPress/gutenberg/pull/78136

 @fabiankaegy Can you test that to see if it fixes the issue you observed?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65103#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 00:52:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 00:52:42 -0000
Subject: [wp-trac] [WordPress Trac] #65103: Single-page admin screens
 (Connectors,
 Font Library) fail to mount in Chrome when @wordpress/boot wins a race
 against its classic-script deps
In-Reply-To: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
References: <055.fd5b7dce505f7cac5b5fa322aadd0fb6@wordpress.org>
Message-ID: <070.0624cb3f0c1d97d6d10786261fdde3f0@wordpress.org>

#65103: Single-page admin screens (Connectors, Font Library) fail to mount in
Chrome when @wordpress/boot wins a race against its classic-script deps
--------------------------------------+-----------------------------
 Reporter:  fabiankaegy               |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  high                      |   Milestone:  7.0
Component:  Script Loader             |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  script-modules has-patch  |     Focuses:  administration
--------------------------------------+-----------------------------
Changes (by westonruter):

 * keywords:  script-modules has-patch has-test-info => script-modules has-
     patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65103#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 01:18:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 01:18:27 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.ed8b9ad354a8129cd1583565425200ff@wordpress.org>

#65211: Font upload shows failure message but font is added to library
---------------------------+------------------------------
 Reporter:  369work        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------

Comment (by wildworks):

 Thanks for the information.

 > It also occurred with newsreader-v26-latin.

 This indicates that the problem is not specific to Japanese fonts.

 > I can no longer reproduce the error no matter how many times I delete
 it.

 It would be great if there were reliable steps to reproduce the issue. If
 not, we might be able to close this ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 01:44:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 01:44:48 -0000
Subject: [wp-trac] [WordPress Trac] #64848: WP_Theme_JSON: Prevent
 implicit coercion in to_ruleset
In-Reply-To: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
References: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
Message-ID: <069.5d394698299b6bfdf89e26cf66955fd6@wordpress.org>

#64848: WP_Theme_JSON: Prevent implicit coercion in to_ruleset
-------------------------------------------------+-------------------------
 Reporter:  ramonopoly                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Themes                               |     Version:  5.8
 Severity:  minor                                |  Resolution:
 Keywords:  has-patch gutenberg-merge has-unit-  |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------

Comment (by ramonopoly):

 > see https://github.com/WordPress/gutenberg/issues/78124

 Thanks @Presskopp I suspect it's unrelated directly to this issue.

 I created a PR in GB to wrap those calls

 - https://github.com/WordPress/gutenberg/pull/78137

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64848#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 01:57:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 01:57:28 -0000
Subject: [wp-trac] [WordPress Trac] #65216: There has been a critical
 error on our website
In-Reply-To: <061.3b70f206114fd3e9ede374e00d62f281@wordpress.org>
References: <061.3b70f206114fd3e9ede374e00d62f281@wordpress.org>
Message-ID: <076.48f66882c2a7937b5e017e4cfca5d929@wordpress.org>

#65216: There has been a critical error on our website
-------------------------------+----------------------
 Reporter:  socialshatsonline  |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  General            |     Version:
 Severity:  normal             |  Resolution:  invalid
 Keywords:                     |     Focuses:
-------------------------------+----------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Hi @socialshatsonline and welcome to Trac!

 I'm sorry to see you have got errors with your site, I understand you may
 need help fixing it. However, this place is for development of the the
 core software, and not for support or help with individual sites. That's
 for the support forums, with a lot of experts who are happy to guide you.

 This error is indicative of a PHP Fatal error which is usually caused by a
 Plugin or theme update that's incompatible with your hosting environment.

 Please visit https://wordpress.org/support/forum/how-to-and-
 troubleshooting/ to either search or submit a request.

 Closing this as "invalid", an internal status meaning your issue is not
 something that can be taken action on here on Trac.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65216#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 02:04:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 02:04:21 -0000
Subject: [wp-trac] [WordPress Trac] #64848: WP_Theme_JSON: Prevent
 implicit coercion in to_ruleset
In-Reply-To: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
References: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
Message-ID: <069.3c3b1349cb2c9e82549de4f93e900600@wordpress.org>

#64848: WP_Theme_JSON: Prevent implicit coercion in to_ruleset
-------------------------------------------------+-------------------------
 Reporter:  ramonopoly                           |       Owner:  ramonopoly
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.1
Component:  Themes                               |     Version:  5.8
 Severity:  minor                                |  Resolution:  fixed
 Keywords:  has-patch gutenberg-merge has-unit-  |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------
Changes (by ramonopoly):

 * owner:  (none) => ramonopoly
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62347" 62347]:
 {{{
 #!CommitTicketReference repository="" revision="62347"
 WP_Theme_JSON: Prevent implicit coercion in to_ruleset

 `to_ruleset` used string concatenation (`$element['name'] . ': ' .
 $element['value'] . ';'`), so PHP implicitly coerced non-string values
 (e.g. booleans → `'1'`/`''`, arrays → `'Array'`). That could emit invalid
 or misleading CSS.

 At the same time, pass a `style` theme.json path in
 `test_get_styles_with_appearance_tools()` to simulate a style node. Before
 it was `settings`.

 Props ramonopoly, andrewserong, isabel_brison.

 Fixes #64848.

  --This line, and those below, will be ignored--

 M    src/wp-includes/class-wp-theme-json.php
 M    tests/phpunit/tests/theme/wpThemeJson.php
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64848#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 02:41:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 02:41:33 -0000
Subject: [wp-trac] [WordPress Trac] #64848: WP_Theme_JSON: Prevent
 implicit coercion in to_ruleset
In-Reply-To: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
References: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
Message-ID: <069.a4b7a3f8e6287bcdcaac9a71356a80cf@wordpress.org>

#64848: WP_Theme_JSON: Prevent implicit coercion in to_ruleset
-------------------------------------------------+-------------------------
 Reporter:  ramonopoly                           |       Owner:  ramonopoly
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.1
Component:  Themes                               |     Version:  5.8
 Severity:  minor                                |  Resolution:
 Keywords:  has-patch gutenberg-merge has-unit-  |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------
Changes (by ramonopoly):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening. There's a block on committing to trunk until 7.0. I'll revert

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64848#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 02:45:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 02:45:01 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.95e1b357c002e82622b2552d8d776e8e@wordpress.org>

#65211: Font upload shows failure message but font is added to library
---------------------------+------------------------------
 Reporter:  369work        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------

Comment (by 369work):

 I can reproduce this issue multiple times, so I will explain the steps.

 1. Install WordPress Studio 7.0RC3.

 2. Select Upload from Appearance > Fonts.

 3. Upload the font.

 4. Cannot read properties of undefined (reading styles)

 Expected behavior:
 Success banner

 Windows 11

 Edge

 However, uploading via Appearance > Editor > Style > Typography > Fonts is
 successful.

 After this, uploading via Appearance > Fonts is successful, and the error
 no longer occurs.

 [https://youtu.be/CVrGBME3rxw]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 03:04:57 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 03:04:57 -0000
Subject: [wp-trac] [WordPress Trac] #65003: next/prev for enlarged image
 needs context
In-Reply-To: <052.b63525ba9b3238159791aa05ff965555@wordpress.org>
References: <052.b63525ba9b3238159791aa05ff965555@wordpress.org>
Message-ID: <067.f6494f3ac7a031e25810afa33f47597f@wordpress.org>

#65003: next/prev for enlarged image needs context
--------------------------+---------------------
 Reporter:  timse201      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  7.0
Component:  I18N          |     Version:  trunk
 Severity:  normal        |  Resolution:  fixed
 Keywords:  close         |     Focuses:
--------------------------+---------------------
Changes (by wildworks):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 I have confirmed that this issue has been resolved with the GB update.

 https://build.trac.wordpress.org/browser/branches/7.0/wp-
 includes/blocks/image.php?marks=209#L205

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65003#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 03:05:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 03:05:04 -0000
Subject: [wp-trac] [WordPress Trac] #65003: next/prev for enlarged image
 needs context
In-Reply-To: <052.b63525ba9b3238159791aa05ff965555@wordpress.org>
References: <052.b63525ba9b3238159791aa05ff965555@wordpress.org>
Message-ID: <067.25bd31c08f2272bedee0b2421503d9a3@wordpress.org>

#65003: next/prev for enlarged image needs context
--------------------------+---------------------
 Reporter:  timse201      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  7.0
Component:  I18N          |     Version:  trunk
 Severity:  normal        |  Resolution:  fixed
 Keywords:                |     Focuses:
--------------------------+---------------------
Changes (by wildworks):

 * keywords:  close =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65003#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 03:13:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 03:13:39 -0000
Subject: [wp-trac] [WordPress Trac] #64817: Bump default theme versions
 for WordPress 7.0
In-Reply-To: <052.c63f6cd5170af975f4f240cb6bb1d2a1@wordpress.org>
References: <052.c63f6cd5170af975f4f240cb6bb1d2a1@wordpress.org>
Message-ID: <067.02d5124220011eb1da15ce8ac319c366@wordpress.org>

#64817: Bump default theme versions for WordPress 7.0
------------------------------------------------+-------------------------
 Reporter:  shailu25                            |       Owner:  karmatosed
     Type:  task (blessed)                      |      Status:  reopened
 Priority:  normal                              |   Milestone:  7.0
Component:  Bundled Theme                       |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  has-patch dev-feedback fixed-major  |     Focuses:
------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch dev-feedback fixed-major


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64817#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 03:16:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 03:16:48 -0000
Subject: [wp-trac] [WordPress Trac] #64848: WP_Theme_JSON: Prevent
 implicit coercion in to_ruleset
In-Reply-To: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
References: <054.efd4b191bdfc96e0d33888edcce767d0@wordpress.org>
Message-ID: <069.8e859d33ddbd64b7d17b816874d27bfb@wordpress.org>

#64848: WP_Theme_JSON: Prevent implicit coercion in to_ruleset
-------------------------------------------------+-------------------------
 Reporter:  ramonopoly                           |       Owner:  ramonopoly
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.1
Component:  Themes                               |     Version:  5.8
 Severity:  minor                                |  Resolution:
 Keywords:  has-patch gutenberg-merge has-unit-  |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------

Comment (by ramonopoly):

 In [changeset:"62348" 62348]:
 {{{
 #!CommitTicketReference repository="" revision="62348"
 [REVERT] WP_Theme_JSON: Prevent implicit coercion in to_ruleset

 Reverts r62347. The fix the patch proposes is destined for 7.1. There is a
 general block for such patches until the 7.0 general release.

 Props ramonopoly, andrewserong, westonruter.

 See #64848.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64848#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 03:17:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 03:17:20 -0000
Subject: [wp-trac] [WordPress Trac] #64817: Bump default theme versions
 for WordPress 7.0
In-Reply-To: <052.c63f6cd5170af975f4f240cb6bb1d2a1@wordpress.org>
References: <052.c63f6cd5170af975f4f240cb6bb1d2a1@wordpress.org>
Message-ID: <067.2cb73e4d4398c85a95067af44042f5f3@wordpress.org>

#64817: Bump default theme versions for WordPress 7.0
------------------------------------------------+-------------------------
 Reporter:  shailu25                            |       Owner:  karmatosed
     Type:  task (blessed)                      |      Status:  reopened
 Priority:  normal                              |   Milestone:  7.0
Component:  Bundled Theme                       |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  has-patch fixed-major dev-reviewed  |     Focuses:
------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch dev-feedback fixed-major => has-patch fixed-major
     dev-reviewed


Comment:

 This is a second committer sign-off to backport [62344] to branch 7.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64817#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 04:45:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 04:45:37 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.23b5344eccac76f268952921e4470d4c@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by mukesh27):

 @fcoveram Let me know once the copy updated.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:40>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 06:21:55 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 06:21:55 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity section
 alignment issue.
Message-ID: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
--------------------------------+-----------------------------
 Reporter:  gaurangsondagar     |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  General             |    Version:
 Severity:  normal              |   Keywords:
  Focuses:  ui, administration  |
--------------------------------+-----------------------------
 I upgraded to **WordPress RC3**, and while testing the admin panel, I
 noticed a UI glitch in the **Activity section of the Admin Dashboard**.

 The WordPress RC3 version was upgraded using the following CLI command:

 {{{
 wp core update --version=7.0-RC3
 }}}

 I tried debugging the UI issue and noticed that when I commented out the
 following CSS rule (**margin: 0 -12px;**), the layout appeared correctly.

 File path: **/wp-admin/css/dashboard.css(line no: 1085)**

 **Before:**
 {{{
 #latest-comments #the-comment-list {
     position: relative;
     margin: 0 -12px;
 }
 }}}

 **After:**

 {{{
 #latest-comments #the-comment-list {
     position: relative;
 }
 }}}
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 06:24:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 06:24:02 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity
 section alignment issue.
In-Reply-To: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
References: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
Message-ID: <074.829884a2138a1d78d80518cf9073450e@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
-----------------------------+---------------------------------
 Reporter:  gaurangsondagar  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  ui, administration
-----------------------------+---------------------------------
Changes (by gaurangsondagar):

 * Attachment "Screenshot from 2026-05-11 11-53-05.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 06:24:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 06:24:29 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity
 section alignment issue.
In-Reply-To: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
References: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
Message-ID: <074.b4799fbce6eb361454450b7c72d871e9@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
-----------------------------+---------------------------------
 Reporter:  gaurangsondagar  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  ui, administration
-----------------------------+---------------------------------
Changes (by gaurangsondagar):

 * Attachment "Screenshot from 2026-05-11 11-53-23.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 06:24:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 06:24:49 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity
 section alignment issue.
In-Reply-To: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
References: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
Message-ID: <074.8cf2ec396f46924cee860a3cd9ca53bc@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
-----------------------------+---------------------------------
 Reporter:  gaurangsondagar  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  ui, administration
-----------------------------+---------------------------------
Changes (by gaurangsondagar):

 * Attachment "Screenshot from 2026-05-11 11-52-49.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 06:24:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 06:24:39 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity
 section alignment issue.
In-Reply-To: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
References: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
Message-ID: <074.0c2ff8d38c808a9d11a96e2c923d2a2f@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
-----------------------------+---------------------------------
 Reporter:  gaurangsondagar  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  ui, administration
-----------------------------+---------------------------------
Changes (by gaurangsondagar):

 * Attachment "Screenshot from 2026-05-11 11-53-28.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 06:29:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 06:29:38 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity
 section alignment issue.
In-Reply-To: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
References: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
Message-ID: <074.1813a96a39f7f0d57e3ac35571ab8b7d@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
-----------------------------+---------------------------------
 Reporter:  gaurangsondagar  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  ui, administration
-----------------------------+---------------------------------

Comment (by gaurangsondagar):

 The **environment** I am using below:

 - PHP: 8.2.29
 - WordPress: 7.0-RC3-62340
 - Web server: Apache
 - Database: MySQL
 - Browser: Chrome
 - OS: Ubuntu 22.04.5 LTS
 - Theme: Twenty Twenty-Five

 I have attached two screenshots showing the layout with the existing CSS
 applied, and another two screenshots after removing the CSS mentioned
 below, where the **Activity section** left and right side alignment looks
 fine.


 {{{
 #latest-comments #the-comment-list {
     position: relative;
 }
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 09:05:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 09:05:27 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity
 section alignment issue.
In-Reply-To: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
References: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
Message-ID: <074.4cbacea3ecbeebfb9a91f2c2e444b187@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
-----------------------------+---------------------------------
 Reporter:  gaurangsondagar  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-test-info    |     Focuses:  ui, administration
-----------------------------+---------------------------------
Changes (by abcd95):

 * keywords:   => has-test-info


Comment:

 == Reproduction Report
 === Description
 This report validates whether the issue can be reproduced.

 === Environment
 - WordPress: 7.0-RC3
 - PHP: 8.3.30
 - Server: PHP.wasm
 - Database: WP_SQLite_Driver (Server: 8.0.38 / Client: 3.51.0)
 - Browser: Chrome 147.0.0.0
 - OS: macOS
 - Theme: Twenty Twenty-Five 1.4
 - MU Plugins: None activated
 - Plugins:
   * AI 0.9.0
   * AI Provider for Google 1.0.3
   * AI Provider for OpenAI 1.0.2
   * Test Reports 1.2.1

 === Actual Results
 ❌ Error condition does not occur.

 Is there anything else I need to replicate?

 === Additional Notes
 With the same plugins installed, I did not observe the error.

 === Supplemental Artifacts
 [[Image(https://i.ibb.co/MxPCG4Sb/Screenshot-2026-05-11-at-14-29-51.png)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 09:36:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 09:36:51 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity
 section alignment issue.
In-Reply-To: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
References: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
Message-ID: <074.05f2f9b9601f46344be191d9c39d3525@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
-----------------------------+---------------------------------
 Reporter:  gaurangsondagar  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-test-info    |     Focuses:  ui, administration
-----------------------------+---------------------------------

Comment (by gaurangsondagar):

 Hi @abcd95

 Thanks for sharing your concern.

 I have already shared the environment details where I am experiencing the
 issue. I have also prepared a short video that may help you reproduce the
 problem.

 https://www.awesomescreenshot.com/video/52413172?key=56373bc3c08a0b339e68f2e91a9258c6

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 09:51:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 09:51:44 -0000
Subject: [wp-trac] [WordPress Trac] #64835: Parent menu item is still
 rendered as dropdown when all submenu items are hidden
In-Reply-To: <053.b4fb2430436a11c6bec641ae71f415cc@wordpress.org>
References: <053.b4fb2430436a11c6bec641ae71f415cc@wordpress.org>
Message-ID: <068.bb36ec0e263c5866c9a7fbfd33b93882@wordpress.org>

#64835: Parent menu item is still rendered as dropdown when all submenu items are
hidden
--------------------------+------------------------------
 Reporter:  benniledl     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by devasheeshkaul):

 Thank you for sharing the report. I've also created an issue with a fix PR
 on Gutenberg repo for the same to be handled there as well.

 Issue: https://github.com/WordPress/gutenberg/issues/78147
 PR: https://github.com/WordPress/gutenberg/pull/78148

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64835#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 12:46:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 12:46:17 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.1b111eef3c078227a1f38cb0614b2070@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests                           |
-------------------------------------------------+-------------------------

Comment (by wildworks):

 In [changeset:"62349" 62349]:
 {{{
 #!CommitTicketReference repository="" revision="62349"
 Toolbar: Revert add CSS from admin color scheme on front-end.

 The implementation issues a server-side HTTP request on every front-end
 page load and extracts the toolbar CSS via fragile substring matching.
 Alternatives are too large to land this late in the release cycle, so the
 fix is deferred to a future release.

 Reverts [62025].

 Props desrosj, jorbin, mukesh27, sabernhardt, wildworks.

 See #64762.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:57>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 12:47:55 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 12:47:55 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.dd6637473574d68e8d862dc4b8830a2d@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests dev-feedback              |
-------------------------------------------------+-------------------------
Changes (by wildworks):

 * keywords:  has-screenshots admin-reskin has-patch has-unit-tests => has-
     screenshots admin-reskin has-patch has-unit-tests dev-feedback


Comment:

 I propose backporting [62349] to the 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:58>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 13:42:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 13:42:01 -0000
Subject: [wp-trac] [WordPress Trac] #65209: Connectors: Expose
 isFileModDisabled flag to connector script module data.
In-Reply-To: <060.cb590e149a9788ce40c3331ee619316f@wordpress.org>
References: <060.cb590e149a9788ce40c3331ee619316f@wordpress.org>
Message-ID: <075.9be38ad5b9ca6ffe5416c66dd2d48bf5@wordpress.org>

#65209: Connectors: Expose isFileModDisabled flag to connector script module data.
-------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                     |       Owner:  wildworks
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch dev-reviewed gutenberg-    |     Focuses:
  merge                                          |
-------------------------------------------------+-------------------------
Changes (by wildworks):

 * owner:  (none) => wildworks
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62350" 62350]:
 {{{
 #!CommitTicketReference repository="" revision="62350"
 Connectors: Expose `isFileModDisabled` flag to connector script module
 data.

 Adds an `isFileModDisabled` boolean — derived from
 `wp_is_file_mod_allowed(   'install_plugins' )` — to the data exposed via
 the `script_module_data_options-connectors-wp-admin` filter, so the
 connectors UI can adapt when file modifications are disabled.

 Reviewed by wildworks.
 Merges [62341] to the 7.0 branch.

 Props jorgefilipecosta, westonruter, jeffpaul.
 Fixes #65209.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65209#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 13:58:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 13:58:25 -0000
Subject: [wp-trac] [WordPress Trac] #65218: update-core.php - plugin slug is
 not clean
Message-ID: <052.e5421224b0bc586e44ea72067b8417cf@wordpress.org>

#65218: update-core.php - plugin slug is not clean
----------------------------+-----------------------------
 Reporter:  timse201        |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:  trunk
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 The plugin slug we use to generate the link is not clean on update core.
 It includes the parent folder. e.g. /plugin/plugin.php. The API is smart
 enough to redirect to the en_us page.
 On the plugins screen, we use a clean one.


 $plugin_data->update->slug

 https://github.com/WordPress/wordpress-
 develop/blob/5e7fd3f6a7caf06e55b4b2781bd42a26165e5b3e/src/wp-admin/update-
 core.php#L570

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65218>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 15:28:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 15:28:34 -0000
Subject: [wp-trac] [WordPress Trac] #23562: Using Speech Recognition
 Software with the Add Media Panel
In-Reply-To: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
References: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
Message-ID: <073.0bacd44631b69dc90d81be252bf143f0@wordpress.org>

#23562: Using Speech Recognition Software with the Add Media Panel
--------------------------------------------+----------------------------
 Reporter:  grahamarmfield                  |       Owner:  joedolson
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:  7.0
Component:  Media                           |     Version:  3.5.1
 Severity:  normal                          |  Resolution:
 Keywords:  has-patch has-test-info commit  |     Focuses:  accessibility
--------------------------------------------+----------------------------
Changes (by wildworks):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 r61757 appears to display an unintended scrollbar. This is due to the
 `overflow:hidden` property being changed to `auto`.

 {{{
 .media-toolbar {
         overflow: auto;
 }
 }}}

 I understand [https://github.com/WordPress/wordpress-
 develop/pull/10832#issuecomment-3961724891 this change was intentional],
 but I didn't anticipate it affecting the desktop layout. This is
 particularly noticeable on Windows, where overflowed elements get
 scrollbars by default. Let's explore if there are any better approaches
 for the 7.0 release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/23562#comment:64>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 15:29:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 15:29:21 -0000
Subject: [wp-trac] [WordPress Trac] #23562: Using Speech Recognition
 Software with the Add Media Panel
In-Reply-To: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
References: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
Message-ID: <073.0b4230e3506545e8776a61c2102299ad@wordpress.org>

#23562: Using Speech Recognition Software with the Add Media Panel
--------------------------------------------+----------------------------
 Reporter:  grahamarmfield                  |       Owner:  joedolson
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:  7.0
Component:  Media                           |     Version:  3.5.1
 Severity:  normal                          |  Resolution:
 Keywords:  has-patch has-test-info commit  |     Focuses:  accessibility
--------------------------------------------+----------------------------
Changes (by wildworks):

 * Attachment "media-overflow.png" added.

 Comparison of media headers in versions 6.9 and 7.0

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/23562>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 15:56:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 15:56:16 -0000
Subject: [wp-trac] [WordPress Trac] #23562: Using Speech Recognition
 Software with the Add Media Panel
In-Reply-To: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
References: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
Message-ID: <073.bae2d7a61afc3216518635664a5740a3@wordpress.org>

#23562: Using Speech Recognition Software with the Add Media Panel
--------------------------------------------+----------------------------
 Reporter:  grahamarmfield                  |       Owner:  joedolson
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:  7.0
Component:  Media                           |     Version:  3.5.1
 Severity:  normal                          |  Resolution:
 Keywords:  has-patch has-test-info commit  |     Focuses:  accessibility
--------------------------------------------+----------------------------
Changes (by sabernhardt):

 * Attachment "23562.increase-height.diff" added.

 increases height by 12 pixels to reduce the need for scrollbars

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/23562>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 16:02:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 16:02:34 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.b47dfe3e03ff2e06260df11518ebd7fd@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests dev-feedback fixed-major  |
-------------------------------------------------+-------------------------
Changes (by JeffPaul):

 * keywords:  has-screenshots admin-reskin has-patch has-unit-tests dev-
     feedback =>
     has-screenshots admin-reskin has-patch has-unit-tests dev-feedback
     fixed-major


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:59>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 16:04:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 16:04:50 -0000
Subject: [wp-trac] [WordPress Trac] #65215: Connectors: REST API
 responses on the Connectors screen should be preloaded
In-Reply-To: <055.ffa9695b8ee4a5ec363fdcb07d69a8ff@wordpress.org>
References: <055.ffa9695b8ee4a5ec363fdcb07d69a8ff@wordpress.org>
Message-ID: <070.ff06b590e4e570a264c1b24af5adbd2a@wordpress.org>

#65215: Connectors: REST API responses on the Connectors screen should be preloaded
-------------------------------------------------+-------------------------
 Reporter:  westonruter                          |       Owner:
                                                 |  westonruter
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  7.0
Component:  AI                                   |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  connectors has-patch has-unit-tests  |     Focuses:  rest-api,
                                                 |  performance
-------------------------------------------------+-------------------------
Changes (by JeffPaul):

 * keywords:  has-patch has-unit-tests => connectors has-patch has-unit-
               tests


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65215#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 16:08:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 16:08:12 -0000
Subject: [wp-trac] [WordPress Trac] #23562: Using Speech Recognition
 Software with the Add Media Panel
In-Reply-To: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
References: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
Message-ID: <073.da66bd4bbcb1f9520a9211767ce02ea3@wordpress.org>

#23562: Using Speech Recognition Software with the Add Media Panel
--------------------------------------------+----------------------------
 Reporter:  grahamarmfield                  |       Owner:  joedolson
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:  7.0
Component:  Media                           |     Version:  3.5.1
 Severity:  normal                          |  Resolution:
 Keywords:  has-patch has-test-info commit  |     Focuses:  accessibility
--------------------------------------------+----------------------------

Comment (by wildworks):

 It looks like
 [https://core.trac.wordpress.org/attachment/ticket/23562/23562.increase-
 height.diff 23562.increase-height.diff] and [https://github.com/WordPress
 /wordpress-develop/pull/11797/ PR 11797] have the exact same changes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/23562#comment:66>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 16:10:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 16:10:34 -0000
Subject: [wp-trac] [WordPress Trac] #23562: Using Speech Recognition
 Software with the Add Media Panel
In-Reply-To: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
References: <058.865fbcf63f850102b3f5edf1ad23198a@wordpress.org>
Message-ID: <073.3f1ccf41a1b65be44acbe33922b7899b@wordpress.org>

#23562: Using Speech Recognition Software with the Add Media Panel
-------------------------------------+----------------------------
 Reporter:  grahamarmfield           |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Media                    |     Version:  3.5.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-test-info  |     Focuses:  accessibility
-------------------------------------+----------------------------
Changes (by sabernhardt):

 * keywords:  has-patch has-test-info commit => has-patch has-test-info


Comment:

 Ha! Then test PR 11797 :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/23562#comment:67>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 16:13:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 16:13:34 -0000
Subject: [wp-trac] [WordPress Trac] #65053: Media upload from the post
 edit screen shows an inaccurate number when uploading multiple media files
In-Reply-To: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
References: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
Message-ID: <068.901e215a2cdd6f571fd37aebe7412920@wordpress.org>

#65053: Media upload from the post edit screen shows an inaccurate number when
uploading multiple media files
-------------------------------------------------+-------------------------
 Reporter:  Dharm1025                            |       Owner:
                                                 |  adamsilverstein
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  7.1
Component:  Upload                               |     Version:  6.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-test-info has-unit-    |     Focuses:  ui,
  tests commit                                   |  javascript
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * keywords:  has-patch needs-unit-tests has-test-info => has-patch has-
     test-info has-unit-tests commit


Comment:

 This fix looks ready to me, I will get it committed for 7.1.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65053#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 16:38:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 16:38:11 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.9976d4f29876c38bd762d1ce41bd1127@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by amykamala):

 Timing is pretty tight here. RC4 is slated for release this Thursday (the
 14th) and then the final release is less than a week later with dry run
 starting on the 19th. Thank you for prioritizing this!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 16:43:43 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 16:43:43 -0000
Subject: [wp-trac] [WordPress Trac] #65214: Refine the help text wording
 for backend editor
In-Reply-To: <052.d2683f1a171f23484391f486bd93f219@wordpress.org>
References: <052.d2683f1a171f23484391f486bd93f219@wordpress.org>
Message-ID: <067.9ca24a70c58e71100e7ea5f37614bf91@wordpress.org>

#65214: Refine the help text wording for backend editor
--------------------------+------------------------------------------
 Reporter:  timse201      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Help/About    |     Version:  3.3
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, administration, ui-copy
--------------------------+------------------------------------------
Changes (by sabernhardt):

 * version:   => 3.3


Comment:

 [19507] changed "within these administration screens" to "within the
 dashboard"; however,
 - [https://wordpress.org/documentation/article/administration-screens/
 HelpHub's article] uses the term "Administration Screen" and
 - [https://core.trac.wordpress.org/ticket/63048#comment:6 Ticket 63048]
 avoided "dashboard" in favor of "administration" when referring to
 administration color schemes.

 I am not sure "backend editor" would help.
 - I did not find "backend" (or "back end" or "back-end") in any user-
 facing strings.
 - The post editor technically can be added on the front end.

 Something like "the interface you use when adding and editing posts" could
 describe the post editor (I pulled that from the first two sentences in
 the [https://wordpress.org/documentation/article/settings-writing-screen/
 Writing Settings article]).

 Other parts of the string could be edited, too.
 - Both Post via Email and Update Services can be removed via filter.
 Without either of those displaying, "top section" and "the rest" would not
 fit.
 - When real-time collaboration has an opt-in setting (#64904), the help
 text might mention that.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65214#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 18:14:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 18:14:28 -0000
Subject: [wp-trac] [WordPress Trac] #48684: Twenty Twenty: Issue with
 primary color in the block editor
In-Reply-To: <055.9aa549977ed52fd06e06946fe18303c4@wordpress.org>
References: <055.9aa549977ed52fd06e06946fe18303c4@wordpress.org>
Message-ID: <070.d9b50aba55d2a54ddbd596753d62f061@wordpress.org>

#48684: Twenty Twenty: Issue with primary color in the block editor
-----------------------------------------+------------------------------
 Reporter:  grafruessel                  |       Owner:  (none)
     Type:  defect (bug)                 |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Bundled Theme                |     Version:  5.3
 Severity:  normal                       |  Resolution:
 Keywords:  has-screenshots needs-patch  |     Focuses:  css
-----------------------------------------+------------------------------
Changes (by sabernhardt):

 * Attachment "48684.wp-block.diff" added.

 applies color rule only to blocks (that do not have the text color class)
 in editor

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48684>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 18:15:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 18:15:19 -0000
Subject: [wp-trac] [WordPress Trac] #48684: Twenty Twenty: Issue with
 primary color in the block editor
In-Reply-To: <055.9aa549977ed52fd06e06946fe18303c4@wordpress.org>
References: <055.9aa549977ed52fd06e06946fe18303c4@wordpress.org>
Message-ID: <070.d71486ddd0cb3a3395f675cbcbdb0fba@wordpress.org>

#48684: Twenty Twenty: Issue with primary color in the block editor
-----------------------------------------+------------------------------
 Reporter:  grafruessel                  |       Owner:  (none)
     Type:  defect (bug)                 |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Bundled Theme                |     Version:  5.3
 Severity:  normal                       |  Resolution:
 Keywords:  has-screenshots needs-patch  |     Focuses:  css
-----------------------------------------+------------------------------
Changes (by sabernhardt):

 * Attachment "48684.exclude-components.diff" added.

 applies color rule to any element except for editor components and
 anything within them

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48684>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 19:36:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 19:36:15 -0000
Subject: [wp-trac] [WordPress Trac] #48684: Twenty Twenty: Issue with
 primary color in the block editor
In-Reply-To: <055.9aa549977ed52fd06e06946fe18303c4@wordpress.org>
References: <055.9aa549977ed52fd06e06946fe18303c4@wordpress.org>
Message-ID: <070.33e2cf6da5e4d270982263853d3bcb54@wordpress.org>

#48684: Twenty Twenty: Issue with primary color in the block editor
---------------------------------------+-----------------------------
 Reporter:  grafruessel                |       Owner:  (none)
     Type:  defect (bug)               |      Status:  new
 Priority:  normal                     |   Milestone:  Future Release
Component:  Bundled Theme              |     Version:  5.3
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:  css
---------------------------------------+-----------------------------
Changes (by sabernhardt):

 * keywords:  has-screenshots needs-patch => has-screenshots has-patch
 * milestone:  Awaiting Review => Future Release


Comment:

 [https://github.com/WordPress/twentytwenty/pull/980 PR 980] added the
 selectors for automatic contrast.

 I think all the elements that would need the text color have a `wp-block`
 class in the editor.
 {{{
 .wp-block:where(:not(.has-text-color))
 }}}

 To be more thorough, the selectors could use `:not()` for the editor's
 control components and anything inside them.
 {{{
 *:where(:not([class^="components-"]):not([class^="components-"] *)):not
 (.has-text-color)
 }}}

 I used `:where()` to avoid changing the specificity.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48684#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 22:21:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 22:21:21 -0000
Subject: [wp-trac] [WordPress Trac] #65200: Tests: Add unit tests for
 wp_heartbeat_set_suspension()
In-Reply-To: <051.95a72c11b11ee45e117268c654f22cc3@wordpress.org>
References: <051.95a72c11b11ee45e117268c654f22cc3@wordpress.org>
Message-ID: <066.90f434a190bb5eabb57800dcd4e92588@wordpress.org>

#65200: Tests: Add unit tests for wp_heartbeat_set_suspension()
--------------------------------------+---------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65200#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon May 11 22:23:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 11 May 2026 22:23:18 -0000
Subject: [wp-trac] [WordPress Trac] #65200: Tests: Add unit tests for
 wp_heartbeat_set_suspension()
In-Reply-To: <051.95a72c11b11ee45e117268c654f22cc3@wordpress.org>
References: <051.95a72c11b11ee45e117268c654f22cc3@wordpress.org>
Message-ID: <066.6f6c895904fd0bde7c46c91eae5cbb6f@wordpress.org>

#65200: Tests: Add unit tests for wp_heartbeat_set_suspension()
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  SergeyBiryukov
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62351" 62351]:
 {{{
 #!CommitTicketReference repository="" revision="62351"
 Tests: Add unit tests for `wp_heartbeat_set_suspension()`.

 Follow-up to [26428], [26549].

 Props pbearne.
 Fixes #65200.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65200#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 01:22:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 01:22:07 -0000
Subject: [wp-trac] [WordPress Trac] #65219: Make command palette node more
 prominent in the center of the admin bar
Message-ID: <050.43a907ebae6bf360d272160cd7e4f8a7@wordpress.org>

#65219: Make command palette node more prominent in the center of the admin bar
-------------------------+-----------------------------
 Reporter:  fushar       |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Toolbar      |    Version:
 Severity:  normal       |   Keywords:
  Focuses:  ui, css      |
-------------------------+-----------------------------
 We want to update the design of the command palette node in the admin bar,
 by making it more prominent in the center.

 This is a continuation of https://core.trac.wordpress.org/ticket/64672,
 where we decided to make it a simple icon node at that time.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65219>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 02:13:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 02:13:33 -0000
Subject: [wp-trac] [WordPress Trac] #65091: Toolbar: Display the toolbar
 in the Site Editor and Block Editor
In-Reply-To: <052.ac01559e4f77c9901d3bb3cf47d7d4d3@wordpress.org>
References: <052.ac01559e4f77c9901d3bb3cf47d7d4d3@wordpress.org>
Message-ID: <067.7fee5dc074789b12ba6e3d9e645124cb@wordpress.org>

#65091: Toolbar: Display the toolbar in the Site Editor and Block Editor
-------------------------+------------------------------------------------
 Reporter:  lucasmdo     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Toolbar      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:  ui, accessibility, administration
-------------------------+------------------------------------------------

Comment (by fushar):

 For now, I added a Gutenberg experiment that shows the admin bar in
 edtors, in this PR: https://github.com/WordPress/gutenberg/pull/77964.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65091#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 02:49:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 02:49:29 -0000
Subject: [wp-trac] [WordPress Trac] #65053: Media upload from the post
 edit screen shows an inaccurate number when uploading multiple media files
In-Reply-To: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
References: <053.9dbb6fc319de35dce28f39fb3ef8f2fb@wordpress.org>
Message-ID: <068.774a78c317894919050a3c98f71b910f@wordpress.org>

#65053: Media upload from the post edit screen shows an inaccurate number when
uploading multiple media files
-------------------------------------------------+-------------------------
 Reporter:  Dharm1025                            |       Owner:
                                                 |  adamsilverstein
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  7.1
Component:  Upload                               |     Version:  6.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-test-info has-unit-    |     Focuses:  ui,
  tests commit                                   |  javascript
-------------------------------------------------+-------------------------

Comment (by hbhalodia):

 Thanks @adamsilverstein

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65053#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 02:58:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 02:58:13 -0000
Subject: [wp-trac] [WordPress Trac] #65220: Toolbar: Show site title always
 even on mobile viewport, by moving shortcut menus under site menu
Message-ID: <050.8131bf27548d72928bdacaf59e24bfec@wordpress.org>

#65220: Toolbar: Show site title always even on mobile viewport, by moving shortcut
menus under site menu
-------------------------+-----------------------------
 Reporter:  fushar       |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Toolbar      |    Version:
 Severity:  normal       |   Keywords:
  Focuses:  ui, css      |
-------------------------+-----------------------------
 ==== Problem

 On wp-admin pages in mobile resolution (<= 782px), when we have many sites
 (e.g. on a multi-site network), it's not easy to quickly identify which
 site we're currently working on, because the site title is only displayed
 in desktop viewport.

 ==== Proposed Solution

 Show the site title in all resolutions. To make room for it:

 1. Move the "shortcut menus" (Updates, Comments, New, etc) as submenus
 under it. I believe it's a valid tradeoff. I feel it's more important to
 be able to see the site title, than having quick access to Comments / New.
 Also, on narrow resolutions, we already hide such icons progressively,
 e.g. this CSS (https://github.com/WordPress/wordpress-
 develop/blob/7938204d20159fa863e6d34af352bb7557524354/src/wp-includes/css
 /admin-bar.css#L1135-L1140)

 2. Move the command palette search icon to the top-secondary (right). The
 whole top-right nodes should cover the site title if it's too long.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65220>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 04:29:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 04:29:27 -0000
Subject: [wp-trac] [WordPress Trac] #64667: Refine the user dropdown CSS,
 make the avatar circular
In-Reply-To: <048.ded5eb0d757a00ae5b972ddf79211675@wordpress.org>
References: <048.ded5eb0d757a00ae5b972ddf79211675@wordpress.org>
Message-ID: <063.e9bb93e34838cd412b332cc7e22d5426@wordpress.org>

#64667: Refine the user dropdown CSS, make the avatar circular
-------------------------+------------------------------
 Reporter:  Joen         |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Toolbar      |     Version:
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, css
-------------------------+------------------------------

Comment (by fushar):

 Hi @Joen! The original PR is not compatible with certain color schemes, as
 I commented in the PR. I suggest we keep this proposal small: let's start
 with making the avatar circular only.

 I am proposing a new PR which does that + adjusted the size and padding to
 make the circular avatar balanced in the admin bar.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64667#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 05:36:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 05:36:27 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.64c66509df459ebef1358e89b41e96c2@wordpress.org>

#65211: Font upload shows failure message but font is added to library
---------------------------+------------------------------
 Reporter:  369work        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------
Changes (by sanayasir):

 * Attachment "Fonts Successfully uploaded.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 05:36:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 05:36:41 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.9bee73903b3f73b151b4de3fb001b8ca@wordpress.org>

#65211: Font upload shows failure message but font is added to library
-----------------------------+------------------------------
 Reporter:  369work          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  performance
-----------------------------+------------------------------
Changes (by sanayasir):

 * keywords:  needs-testing => has-screenshots
 * focuses:   => performance


Comment:

 Tested this issue on WordPress 7.0 RC3 with TT5 theme and all plugins
 disabled.

 Steps tested:

 * Navigated to Appearance > Fonts
 * Uploaded the provided font files:

   * ShipporiMincho-Regular.woff2
   * MPLUSRounded1c-Regular.woff2
   * NotoSerifJP-VariableFont_wght.woff2

 Result:

 * Fonts uploaded successfully
 * Uploaded fonts appeared correctly in the Font Library
 * No upload failure message was displayed
 * Browser console did not show the reported `Cannot read properties of
 undefined (reading 'styles')` error during testing

 Additionally:

 * Tested with multiple additional `.woff2` font files
 * Additional fonts were also uploaded and applied successfully
 * No installation or UI errors appeared during repeated testing

 The behavior is working as expected according to the ticket requirements.

 Screenshots attached for reference.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 06:40:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 06:40:24 -0000
Subject: [wp-trac] [WordPress Trac] #64667: Refine the user dropdown CSS,
 make the avatar circular
In-Reply-To: <048.ded5eb0d757a00ae5b972ddf79211675@wordpress.org>
References: <048.ded5eb0d757a00ae5b972ddf79211675@wordpress.org>
Message-ID: <063.4805d2026a5764e0bfe2014e226f304c@wordpress.org>

#64667: Refine the user dropdown CSS, make the avatar circular
-------------------------+------------------------------
 Reporter:  Joen         |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Toolbar      |     Version:
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, css
-------------------------+------------------------------

Comment (by Joen):

 Sounds good! I'm happy to close the PR in favor of yours; the motivation
 is the circular avatar!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64667#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 07:32:26 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 07:32:26 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.42de486e468785b930282caffd29ad36@wordpress.org>

#65211: Font upload shows failure message but font is added to library
-----------------------------+------------------------------
 Reporter:  369work          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  performance
-----------------------------+------------------------------

Comment (by 369work):

 I want to clarify that this is not an environment-specific issue.
 The browser console clearly shows:
 Cannot read properties of undefined (reading 'styles')
 This is a JavaScript error — meaning the code itself is crashing, not the
 environment misbehaving.
 The key condition to reproduce is "first upload ever, via Appearance >
 Fonts, before any upload via the Editor".
 Once a font has been uploaded via Appearance > Editor > Style > Typography
 > Fonts, the error disappears — even in Edge.
 This strongly suggests that the two upload paths initialize state
 differently.
 The Editor path hydrates some font family data into state first.
 The Appearance > Fonts path does not — and when it tries to read .styles
 from that uninitialized data, it throws.
 Testers who cannot reproduce this may already have font upload history in
 their environment, which means the state is already initialized before
 testing.
 Additionally, Edge and Chrome are both Chromium-based, so the difference
 between them is unlikely to be a compatibility issue.
 A more likely explanation is a timing difference in async/Promise
 execution order:

 Chrome: state is initialized before the upload response is processed →
 .styles exists → no error
 Edge: upload response is processed before state initialization completes →
 .styles is undefined → crash

 This is a classic race condition pattern — same engine, different
 execution timing, undefined property.
 The fix would be to guard against undefined before reading .styles, or
 ensure state is initialized before processing the upload response,
 regardless of execution order.
 This is a reproducible code-path bug, not a browser or environment issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 07:53:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 07:53:31 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.9d3d9e45137eb6cc2323a2e756f16d12@wordpress.org>

#65211: Font upload shows failure message but font is added to library
-----------------------------+------------------------------
 Reporter:  369work          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  performance
-----------------------------+------------------------------

Comment (by wildworks):

 == Reproduction Report
 This report validates that the issue can be reproduced.

 === Environment
 - OS: Windows 11 Home
 - Local environment: Studio 1.9.0 (Windows on Intel/AMD)
 - Web Server: Server Name PHP.wasm
 - PHP: 8.4.20 (Supports 64bit values)
 - WordPress: 7.0 RC-3
 - Browser: Edge 148.0.3967.54 (Official build) (64-bit)
 - Theme: Twenty Twenty-Five
 - Active Plugins: Beta Tester

 === Actual Results
 ❌ No errors occurred.

 === Test procedure

 1. Create a new site
 2. Update to 7.0 RC-3 via the Beta Tester plugin
 3. Download the [https://fonts.google.com/noto/specimen/Noto+Serif+JP Noto
 Serif Japanese] font.
 4. Access Appearance > Font
 5. Oopen the Upload tab
 6. Unzip the downloaded zip file and upload hoge from within it.
 7. No errors occurred.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 07:57:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 07:57:30 -0000
Subject: [wp-trac] [WordPress Trac] #65212: Uncaught exception TypeError
 in formatting.php
In-Reply-To: <056.8ec695052ef9f9dd0ec6d09ae69f7db7@wordpress.org>
References: <056.8ec695052ef9f9dd0ec6d09ae69f7db7@wordpress.org>
Message-ID: <071.59fe9f0ae4b6ba7a1779c2840d63015f@wordpress.org>

#65212: Uncaught exception TypeError in formatting.php
--------------------------+------------------------------
 Reporter:  harishtewari  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------

Comment (by wildworks):

 It is natural for an error to occur when a value with a type that the
 function does not expect is passed as an argument. It is not a good
 approach to hide errors.

 @harishtewari, could you provide more details about the test procedure and
 the circumstances under which this error occurred?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65212#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 08:10:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 08:10:22 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.981acd5ff8dd4d1dca7c92e9b3ff16be@wordpress.org>

#65211: Font upload shows failure message but font is added to library
-----------------------------+------------------------------
 Reporter:  369work          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  performance
-----------------------------+------------------------------

Comment (by 369work):

 Thank you for your cooperation with the test. However, it's possible that
 the reproduction conditions I mentioned in my previous comment haven't
 been met.

 Could you please confirm that you have never uploaded fonts via Appearance
 > Editor > Style > Typography > Fonts before testing?

 This error seems to occur only during the initial upload attempt via
 Appearance > Fonts, i.e., when the font library hasn't been initialized
 via the editor. This matches a race condition, and the error disappears
 once initialization is complete in either way.
 //////////////////////
 OS: Windows 11 Pro
 Local Environment: Studio 1.8.0 (Intel/AMD Windows)
 PHP: 8.4.20 (64-bit compatible)
 WordPress: 7.0 RC-3
 Browser: Edge  148.0.3967.54
 Theme: TT5
 Active Plugins: Beta Tester
 /////////////////////
 Note that on our end, the same UI error occurs even when installing a
 fresh 7.0RC3. However, this error disappears once the upload via Style is
 successful.


 The observed difference may point to a race condition in async/Promise
 execution order — but this is a hypothesis based on behavior, not a
 confirmed root cause.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 08:53:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 08:53:39 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.1edcb04a539e8c4778ba730d1f62334c@wordpress.org>

#65211: Font upload shows failure message but font is added to library
-----------------------------+------------------------------
 Reporter:  369work          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  performance
-----------------------------+------------------------------

Comment (by wildworks):

 > Could you please confirm that you have never uploaded fonts via
 Appearance > Editor > Style > Typography > Fonts before testing?


 I have already confirmed it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 09:33:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 09:33:48 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.35c648a495eabacddf38779d138b444a@wordpress.org>

#65211: Font upload shows failure message but font is added to library
-----------------------------+------------------------------
 Reporter:  369work          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  performance
-----------------------------+------------------------------

Comment (by 369work):

 Update: We tested on Local by Flywheel 10.0.0 with the same WordPress 7.0
 RC-3 (updated via Beta Tester plugin), and the font upload was successful
 without any errors.
 This suggests the issue may be specific to WordPress Studio, rather than
 WordPress core itself.
 ----
 EnvironmentResultWordPress Studio 1.8.0 + 7.0 RC-3  ❌ UI error / race
 condition
 Local by Flywheel 10.0.0 + 7.0 RC-3                 ✅ Success
 ----
 It may be worth investigating whether Studio handles the font library
 state initialization differently from other local environments.


 Additional finding during testing on Local by Flywheel:
 In Appearance > Fonts, the tab labels and their content are not
 translated.
 This appears to be a separate issue discovered during the same testing
 process — please let us know if this should be filed as a separate ticket.

 [Imgur](https://imgur.com/u758uQV)
 [Imgur](https://imgur.com/5X2SgeH)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 10:07:56 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 10:07:56 -0000
Subject: [wp-trac] [WordPress Trac] #64439: Add admin download
 functionality for themes in wp-admin
In-Reply-To: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
References: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
Message-ID: <074.7a50704d1b9b89c02112fa3ed46b89c3@wordpress.org>

#64439: Add admin download functionality for themes in wp-admin
-----------------------------+------------------------------------------
 Reporter:  solankisoftware  |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Themes           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  administration, performance
-----------------------------+------------------------------------------
Changes (by gaurangsondagar):

 * Attachment "Screenshot from 2026-05-12 15-28-11.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64439>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 10:09:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 10:09:42 -0000
Subject: [wp-trac] [WordPress Trac] #64439: Add admin download
 functionality for themes in wp-admin
In-Reply-To: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
References: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
Message-ID: <074.fb4c7e697ff7436ebe37641e189bac14@wordpress.org>

#64439: Add admin download functionality for themes in wp-admin
-----------------------------+------------------------------------------
 Reporter:  solankisoftware  |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Themes           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  administration, performance
-----------------------------+------------------------------------------

Comment (by gaurangsondagar):

 **Patch testing report:**

 **Patch tested:** https://github.com/WordPress/wordpress-
 develop/pull/10731#issuecomment-3776414377

 **Environment:**
 - PHP: 8.2.29
 - WordPress: 7.1-alpha-20260512.152605
 - Web server: Apache
 - Database: MySQL
 - Browser: Chrome
 - OS: Ubuntu 22.04.5 LTS
 - Theme: Twenty Twenty-Five

 **Steps Followed:**
 - In the latest development trunk, the 'Download Theme' button was not
 visible before applying the patch.
 - After applying the patch, the 'Download Theme' button appeared correctly
 in the Theme File Editor.

 **Result:**
 - The applied patch works as expected and successfully displays the
 “Download Theme” button in the Theme File Editor.

 I have attached a screenshot for reference.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64439#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 10:25:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 10:25:42 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity
 section alignment issue.
In-Reply-To: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
References: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
Message-ID: <074.31dd1528c6b7a7fee79ec2de5f72ec94@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
-------------------------------------+---------------------------------
 Reporter:  gaurangsondagar          |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  General                  |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-test-info has-patch  |     Focuses:  ui, administration
-------------------------------------+---------------------------------
Changes (by gaurangsondagar):

 * Attachment "Screenshot from 2026-05-12 15-49-48.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 10:30:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 10:30:38 -0000
Subject: [wp-trac] [WordPress Trac] #65217: Admin Dashboard Activity
 section alignment issue.
In-Reply-To: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
References: <059.5cd12dfcead0f6e7f36c1a6fc41b2750@wordpress.org>
Message-ID: <074.623faf965cf91e766554aa122a546632@wordpress.org>

#65217: Admin Dashboard Activity section alignment issue.
-------------------------------------+---------------------------------
 Reporter:  gaurangsondagar          |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  General                  |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-test-info has-patch  |     Focuses:  ui, administration
-------------------------------------+---------------------------------
Changes (by gaurangsondagar):

 * version:   => trunk


Comment:

 Hi @khokansardar

 Thank you for sharing the patch details. I tested it, and it works
 perfectly on my end.

 **Patch testing report:**

 **Patch tested:** https://github.com/WordPress/wordpress-
 develop/pull/11794

 **Environment:**
 - PHP: 8.2.29
 - WordPress: 7.0-RC3-62340
 - Web server: Apache
 - Database: MySQL
 - Browser: Chrome
 - OS: Ubuntu 22.04.5 LTS
 - Theme: Twenty Twenty-Five

 **Steps Followed:**
 - Before applying the patch, I was experiencing an alignment issue in the
 Admin Dashboard Activity section.
 - After applying the patch, the alignment issue was resolved.

 **Result:**
 - The applied patch works as expected and successfully fixes the alignment
 issue in the Admin Dashboard Activity section.

 I have attached a screenshot for reference.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65217#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 11:11:45 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 11:11:45 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.34e12c73cebefe58ba0deb6027da96b4@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin needs-patch                 |  administration
-------------------------------------+-------------------------------------
Changes (by wildworks):

 * keywords:  has-screenshots admin-reskin has-patch => has-screenshots
     admin-reskin needs-patch


Comment:

 One short-term solution is to increase the right margin for specific
 languages.

 {{{
 #!css
 @media (min-width: 1101px) {
         .plugin-card .name, .plugin-card .desc > p {
                 margin-right: 128px;
         }

         .plugin-card .name:lang(ja), .plugin-card .desc > p:lang(ja) {
                 margin-right: 138px;
         }
 }
 }}}


 The approach using the `lang` pseudo-class is also used on the about page.
 See [58979]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 13:17:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 13:17:06 -0000
Subject: [wp-trac] =?utf-8?q?=5BWordPress_Trac=5D_=2365221=3A_Stored_XSS_i?=
 =?utf-8?q?ssue_=E2=80=93_Script_tag_executes_inside_WordPress_post_Title?=
Message-ID: <053.c9790431a82d9251d41a6bb06c022db0@wordpress.org>

#65221: Stored XSS issue – Script tag executes inside WordPress post Title
--------------------------+-----------------------------
 Reporter:  vivekawsm     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 A Stored XSS issue occurs when a <script>alert('test')</script> tag is
 added inside the WordPress post title.
 The script executes successfully on the frontend instead of being
 sanitized or escaped.

 Test Payload:

 <script>alert('test')</script>

 Environment
 WordPress: 6.9.4
 PHP: 8.5.3
 Server: TasteWP-S6 Official/3.0.0 (nginx fork)
 Database: mysqli (Server: 8.0.45-0ubuntu0.24.04.1 / Client: mysqlnd 8.5.3)
 Browser: Firefox 150.0
 OS: Windows 10/11
 Theme: Twenty Twenty-Three 1.6
 MU Plugins: None activated

 Steps to Reproduce
 Login to the WordPress admin dashboard.
 Navigate to Posts → Add New.
 Create a new post.
 Add the following payload inside the Post Title field:
 <script>alert('test')</script>
 Add normal content inside the post body.
 Publish the post.
 Open the published post on the frontend.

 Bug occurs — the JavaScript alert executes successfully.



 Expected Results

  The application should sanitize or escape <script> tags in the post
 title.
 JavaScript execution should be blocked.
 The payload should display as plain text or be removed.

 Actual Results

  The <script> tag executes from the post title.
  An alert popup appears on the frontend.
 User-supplied JavaScript is rendered without sanitization

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65221>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 13:21:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 13:21:16 -0000
Subject: [wp-trac] [WordPress Trac] #65222: Request for review regarding PDF
 rendering behavior in WordPress File Block
Message-ID: <059.35d2778977af3da5d9162f72020a2736@wordpress.org>

#65222: Request for review regarding PDF rendering behavior in WordPress File Block
-----------------------------+-----------------------------
 Reporter:  shilpaashokan94  |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  General          |    Version:  6.9.4
 Severity:  major            |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 I previously submitted a private report through the WordPress HackerOne
 program regarding PDF rendering behavior observed in the WordPress File
 Block and would like to request clarification/review from the appropriate
 team.

 HackerOne Report ID: 3657944

 Test Environment:

 WordPress 6.9.4
 Default Gutenberg/File Block
 No external PDF plugins
 Chrome browser

 Observed Behavior:
 When PDF files containing active content are uploaded through the File
 Block and opened from the frontend, script execution behavior may occur
 depending on browser rendering.

 I am intentionally avoiding public disclosure of detailed proof-of-concept
 files or technical payload information because the matter was already
 reported privately through HackerOne.

 This ticket is only intended as a follow-up/request for review and
 guidance regarding the observed behavior and whether additional
 investigation is required.

 Please let me know if further details should be shared privately with the
 security team.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65222>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 13:25:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 13:25:37 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2365221=3A_Stored_XSS_?=
 =?utf-8?q?issue_=E2=80=93_Script_tag_executes_inside_WordPress_post_Title?=
In-Reply-To: <053.c9790431a82d9251d41a6bb06c022db0@wordpress.org>
References: <053.c9790431a82d9251d41a6bb06c022db0@wordpress.org>
Message-ID: <068.5587b35fc0fdb2dedcbe3c493734ad6f@wordpress.org>

#65221: Stored XSS issue – Script tag executes inside WordPress post Title
--------------------------+------------------------------
 Reporter:  vivekawsm     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by vivekawsm):

 * version:   => 6.9.4


Comment:

 Recording for the above issue is attached
 https://jam.dev/c/942bf03a-c08d-45a7-966d-b5812dfc0a36

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65221#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 13:53:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 13:53:30 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.1b8e8cad34166ad9b5d0f94602d308b7@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by fcoveram):

 A new version of the content is in the Google Doc file (tab "version 3"):
 https://docs.google.com/document/d/1LLziX7fdw9iftLOtbpkZ2TN8FfOS3sDVX4nIuJCwBV4/edit?tab=t.o44yk44ibs12#heading=h.66j85f6jwwxu

 Most pieces are untouched, but we moved the position of features and add a
 new one in replacement of real-time collaboration. Please also pay
 attention to "Performance" and "Accessibility" sections as I am unaware of
 possible changes in those two areas.

 A design is coming soon to show how each feature looks. Regardless, the
 document is ready for its implementation.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:42>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 14:00:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 14:00:14 -0000
Subject: [wp-trac] [WordPress Trac] #65221: Unify the UI of the frontend
 search with command palette
Message-ID: <050.80d55be901827b73204d1302423ab102@wordpress.org>

#65221: Unify the UI of the frontend search with command palette
-------------------------+-----------------------------
 Reporter:  fushar       |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Toolbar      |    Version:
 Severity:  normal       |   Keywords:
  Focuses:  ui, css      |
-------------------------+-----------------------------
 This is a continuation of https://core.trac.wordpress.org/ticket/65219.
 After making the command palette more prominent in the center of the admin
 bar, let's also make the frontend search box to look the same visually.

 For now, unlike the command palette which opens an overlay modal, we can
 make the frontend search box to be a true input form, following the
 current behavior. In the future, maybe we can unify the UX more
 consistently.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65221>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 16:18:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 16:18:32 -0000
Subject: [wp-trac] [WordPress Trac] #65100: Accessibility issues in
 admin Font Library
In-Reply-To: <053.fd1c73df50e7a84ff15cd733e2c7ac6f@wordpress.org>
References: <053.fd1c73df50e7a84ff15cd733e2c7ac6f@wordpress.org>
Message-ID: <068.868b29e530ad47fdf7e2278103366eeb@wordpress.org>

#65100: Accessibility issues in admin Font Library
--------------------------+----------------------------
 Reporter:  joedolson     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  7.0
Component:  Themes        |     Version:
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |     Focuses:  accessibility
--------------------------+----------------------------
Changes (by joedolson):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 I think that there's a larger underlying tension that needs to be resolved
 concerning how to mesh the two designs. The current background isn't
 preferred - it doesn't match the slightly softer color palette in
 Gutenberg at `#fcfcfc` nor does it match the core background at `#f0f0f0`.
 But there are other differences as well that should be addressed to better
 synchronize the two designs, such as the main heading style & the border
 radius on the content area.

 I think that we should consider this ticket to be closed, and open a new
 ticket for 7.1 to address smoothing out these design differences with
 accessibility in mind.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65100#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 16:23:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 16:23:15 -0000
Subject: [wp-trac] [WordPress Trac] #65222: Polish discrepances between new
 and old settings pages
Message-ID: <053.7a4b7ab1d71f5fe627f4d73d925c9ff4@wordpress.org>

#65222: Polish discrepances between new and old settings pages
------------------------------------------------+--------------------------
 Reporter:  joedolson                           |      Owner:  (none)
     Type:  enhancement                         |     Status:  new
 Priority:  normal                              |  Milestone:  7.1
Component:  Administration                      |    Version:  trunk
 Severity:  normal                              |   Keywords:  needs-design
  Focuses:  accessibility, css, administration  |
------------------------------------------------+--------------------------
 As discussed in #65100, there are numerous differences in the design of
 newer settings pages that create tension between different parts of the
 WordPress admin.

 Three prominent differences include

 1) The main heading font and style.
 2) The background color.
 3) The incorporation of a border radius in the content region.

 These should be evened out to make the admin more uniform.

 @fabian-kaegy has an opened ticket (#64641) already for incorporating some
 additional changes in core, but the use of the hard white background is a
 problem for accessibility, and should be softened.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65222>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 16:25:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 16:25:20 -0000
Subject: [wp-trac] [WordPress Trac] #65223: Connectors plugin install flow
 does not show filesystem credentials form when FTP is required
Message-ID: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>

#65223: Connectors plugin install flow does not show filesystem credentials form
when FTP is required
-------------------------------------+-------------------------------------
 Reporter:  ekamran                  |      Owner:  (none)
     Type:  defect (bug)             |     Status:  new
 Priority:  normal                   |  Milestone:  Awaiting Review
Component:  AI                       |    Version:  trunk
 Severity:  normal                   |   Keywords:  needs-patch has-test-
  Focuses:  javascript,              |  info
  administration                     |
-------------------------------------+-------------------------------------
 When installing a connector plugin from Settings > Connectors on a site
 that requires filesystem credentials, the install attempt fails with a
 generic notice instead of showing the standard "Connection Information"
 filesystem credentials form.

 The regular Plugins > Add Plugin installer shows the credentials form
 correctly for the same plugin in the same environment.

 == Steps to Reproduce ==
 1. Install WordPress 7.0-RC3.
 2. Log in as an administrator.
 3. Force filesystem credentials, for example by setting FS_METHOD to
 ftpext in wp-config.php.
 4. Ensure the AI plugin is installed and active.
 5. Ensure one connector provider plugin is not installed, for example ai-
 provider-for-anthropic.
 6. Go to Settings > Connectors.
 7. Click Install for Anthropic.

 == Actual Results ==
 The page stays on Settings > Connectors and shows a generic notice:

 {{{
 Failed to install plugin for Anthropic.
 }}}

 No filesystem credentials modal is shown.

 == Expected Results ==
 The Connectors install flow should surface the standard WordPress
 "Connection Information" modal so the administrator can enter FTP
 credentials, matching the behavior of Plugins > Add Plugin.

 == Control Test ==
 Using the same environment and the same plugin:

 1. Go to Plugins > Add Plugin.
 2. Search for ai-provider-for-anthropic.
 3. Click Install Now.

 This correctly opens the "Connection Information" dialog with Hostname,
 FTP Username, FTP Password, and Connection Type fields.

 == Environment ==
 WordPress: 7.0-RC3
 AI plugin: 0.9.0
 Connector tested: AI Provider for Anthropic 1.0.2
 Filesystem method: ftpext
 Environment: Local Docker wp-env

 == Notes ==
 This appears to affect the Connectors page install flow that uses the REST
 plugin save flow. The standard plugin installer handles the filesystem
 credentials case correctly, so this may need special handling in the
 Connectors install action.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65223>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 16:36:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 16:36:05 -0000
Subject: [wp-trac] [WordPress Trac] #16191: Uploaded files with quote
 marks in the filename are undisplayable in MS
In-Reply-To: <057.cf21d82e917631f220a3703cf1be84a5@wordpress.org>
References: <057.cf21d82e917631f220a3703cf1be84a5@wordpress.org>
Message-ID: <072.6f5a0597983531c86958c597588acdb9@wordpress.org>

#16191: Uploaded files with quote marks in the filename are undisplayable in MS
-------------------------------------------------+-------------------------
 Reporter:  simonwheatley                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Upload                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch good-first-bug needs-      |     Focuses:
  refresh close                                  |
-------------------------------------------------+-------------------------

Comment (by jonsurrell):

 As of 6.9.4, the original issue seems to be fixed.

 Uploading a file like `"css".png` results in a filename like `22css22.png`
 on the server and a matching URL. The file remains accessible.

 There does seem to be a related issue described in [#comment:9].
 `"css".png` becoming `22css22.png` does not seem correct or desirable. I
 would expect a result like `css.png` or a similar name on the server.

 The main issue is fixed and this ticket can likely be closed since doesn't
 seem to have been an issue since WordPress 4.4. However, it would be nice
 to open a ticket for the remaining filename issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/16191#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 16:42:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 16:42:04 -0000
Subject: [wp-trac] [WordPress Trac] #65219: Make command palette node
 more prominent in the center of the admin bar
In-Reply-To: <050.43a907ebae6bf360d272160cd7e4f8a7@wordpress.org>
References: <050.43a907ebae6bf360d272160cd7e4f8a7@wordpress.org>
Message-ID: <065.1c9d9a92f2c2fb6cd91e8a84c0197d50@wordpress.org>

#65219: Make command palette node more prominent in the center of the admin bar
-----------------------------+------------------------------
 Reporter:  fushar           |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Toolbar          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |     Focuses:  ui, css
-----------------------------+------------------------------
Changes (by westonruter):

 * keywords:  has-patch => has-patch close


Comment:

 This has been previously discussed, in part:

 * https://github.com/WordPress/wordpress-
 develop/pull/11171#pullrequestreview-3917555903
 * https://github.com/WordPress/wordpress-
 develop/pull/11171#issuecomment-4003269084
 * https://github.com/WordPress/wordpress-
 develop/pull/11171#pullrequestreview-3894717813

 Plugins very often add admin bar menu items, which puts real estate in the
 admin bar at a premium. This is especially so on smaller screen sizes, and
 extremely so for mobile. There would be no room for such a faux command
 palette search bar on mobile (although you are accounting for in
 [https://github.com/WordPress/wordpress-develop/pull/11796 your PR]). To
 me there seems to be very little value to have a wide command palette bar
 taking up room in the admin bar which only serves the purpose as being a
 very large button which opens the actual command palette in a modal with
 its own input field. With the keyboard shortcut appearing in the admin
 bar, the intention is for users to use the keyboard to invoke the command
 palette anyway, and not to click the admin bar anyway.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65219#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 17:08:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 17:08:27 -0000
Subject: [wp-trac] [WordPress Trac] #64439: Add admin download
 functionality for themes in wp-admin
In-Reply-To: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
References: <059.256aa89b6e9d05ddac12fe185eb1c349@wordpress.org>
Message-ID: <074.9c43af98be96673c02689556dd4b3731@wordpress.org>

#64439: Add admin download functionality for themes in wp-admin
-----------------------------+------------------------------
 Reporter:  solankisoftware  |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Themes           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  administration
-----------------------------+------------------------------
Changes (by westonruter):

 * focuses:  administration, performance => administration


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64439#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 17:09:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 17:09:22 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.48b480a26df2fc0a91cf362f1f4895cf@wordpress.org>

#65211: Font upload shows failure message but font is added to library
-----------------------------+------------------------------
 Reporter:  369work          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+------------------------------
Changes (by westonruter):

 * focuses:  performance =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 17:37:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 17:37:54 -0000
Subject: [wp-trac] [WordPress Trac] #62515: 6.7.1. Pictures height
In-Reply-To: <050.4cbd5f4ea05f090b8d249efcdf88ec74@wordpress.org>
References: <050.4cbd5f4ea05f090b8d249efcdf88ec74@wordpress.org>
Message-ID: <065.05d739b72790a3eb8b0dbf2b453e7a53@wordpress.org>

#62515: 6.7.1. Pictures height
-------------------------------------------------+-------------------------
 Reporter:  fredel                               |       Owner:  joemcgill
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Media                                |     Version:  6.7.1
 Severity:  normal                               |  Resolution:
 Keywords:  has-test-info has-screenshots        |     Focuses:
  reporter-feedback needs-patch                  |
-------------------------------------------------+-------------------------

Comment (by devede):

 I've got a similar problem with WordPress 6.9.4, with Firefox 150.0.2.
 See https://bugzilla.mozilla.org/show_bug.cgi?id=2038497

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62515#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 18:26:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 18:26:17 -0000
Subject: [wp-trac] [WordPress Trac] #65219: Make command palette node
 more prominent in the center of the admin bar
In-Reply-To: <050.43a907ebae6bf360d272160cd7e4f8a7@wordpress.org>
References: <050.43a907ebae6bf360d272160cd7e4f8a7@wordpress.org>
Message-ID: <065.c06e781a2b3a607328a44990424aa54a@wordpress.org>

#65219: Make command palette node more prominent in the center of the admin bar
-----------------------------+------------------------------
 Reporter:  fushar           |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Toolbar          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |     Focuses:  ui, css
-----------------------------+------------------------------

Comment (by joedolson):

 I agree with @westonruter; the command palette is intended to be a
 mechanism that intentionally occupies a minimal surface in the UI,
 offering a quick access via keyboard. Giving it a large UI priority in a
 heavily used area doesn't seem helpful.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65219#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 18:29:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 18:29:08 -0000
Subject: [wp-trac] [WordPress Trac] #65224: Add support for testing unmerged
 changes from Gutenberg
Message-ID: <051.67117d30612d0aa1b44471e443f905b1@wordpress.org>

#65224: Add support for testing unmerged changes from Gutenberg
------------------------------+-----------------------
 Reporter:  desrosj           |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:  7.1
Component:  Build/Test Tools  |    Version:
 Severity:  normal            |   Keywords:  has-patch
  Focuses:                    |
------------------------------+-----------------------
 It's currently impossible to test unmerged changes from the Gutenberg
 repository because changes are published to the GitHub Container Registry
 only when `trunk`, `wp/*`, or `release/*` branches are updated.

 Publishing built assets for pull requests and introducing new mutable tags
 is [https://github.com/WordPress/gutenberg/pull/78211 being explored
 upstream].

 This ticket is to track the necessary changes for `wordpress-develop` to
 support these.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65224>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 19:53:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 19:53:10 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.c8c940be2454713ffa4b3aa638cc2563@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by markoserb):

 I am adding a few suggestions for the about page based on latest
 information as in next message.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:43>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 19:53:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 19:53:48 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.1e5eb071d83285816f8e5ce3a3687395@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------
Changes (by markoserb):

 * Attachment "About Page - may 12.jpg" added.

 About page _ May 12

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 22:04:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 22:04:22 -0000
Subject: [wp-trac] [WordPress Trac] #65225: tests: Add unit tests for
 wp_ajax_date_format()
Message-ID: <051.4c9531ffc501edf899ea06d38d4439f3@wordpress.org>

#65225: tests: Add unit tests for wp_ajax_date_format()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 The function wp_ajax_date_format() in src/wp-admin/includes/ajax-
 actions.php currently lacks unit test coverage. This task involves adding
 tests to verify that it correctly handles date format validation and
 returns the expected response.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65225>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 22:18:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 22:18:34 -0000
Subject: [wp-trac] [WordPress Trac] #65186: Tests: Add unit tests for
 _customizer_mobile_viewport_meta()
In-Reply-To: <051.b94ac652cf391f0d7cbf6e66d888a16f@wordpress.org>
References: <051.b94ac652cf391f0d7cbf6e66d888a16f@wordpress.org>
Message-ID: <066.e4b1b25026f54279db78c441cb80a328@wordpress.org>

#65186: Tests: Add unit tests for _customizer_mobile_viewport_meta()
--------------------------------------+---------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65186#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 22:19:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 22:19:33 -0000
Subject: [wp-trac] [WordPress Trac] #65186: Tests: Add unit tests for
 _customizer_mobile_viewport_meta()
In-Reply-To: <051.b94ac652cf391f0d7cbf6e66d888a16f@wordpress.org>
References: <051.b94ac652cf391f0d7cbf6e66d888a16f@wordpress.org>
Message-ID: <066.dbc60c1529e08fb2c282677f9a043177@wordpress.org>

#65186: Tests: Add unit tests for _customizer_mobile_viewport_meta()
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  SergeyBiryukov
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62352" 62352]:
 {{{
 #!CommitTicketReference repository="" revision="62352"
 Tests: Add unit tests for `_customizer_mobile_viewport_meta()`.

 Follow-up to [48412].

 Props pbearne.
 Fixes #65186.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65186#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 22:49:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 22:49:46 -0000
Subject: [wp-trac] [WordPress Trac] #65226: Build/Test Tools: Move AJAX unit
 tests to mirror source structure
Message-ID: <051.271108c0878ccd595b4c0a927c58741a@wordpress.org>

#65226: Build/Test Tools: Move AJAX unit tests to mirror source structure
------------------------------+-----------------------------
 Reporter:  pbearne           |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  Build/Test Tools  |    Version:
 Severity:  normal            |   Keywords:
  Focuses:  tests             |
------------------------------+-----------------------------
 Currently, AJAX unit tests are located in tests/phpunit/tests/ajax/. To
 follow the project's testing guidelines and mirror the source structure
 (src/wp-admin/includes/ajax-actions.php), these tests should be moved to
 tests/phpunit/tests/admin/includes/ajax-actions/.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65226>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 22:52:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 22:52:24 -0000
Subject: [wp-trac] [WordPress Trac] #65225: tests: Add unit tests for
 wp_ajax_date_format()
In-Reply-To: <051.4c9531ffc501edf899ea06d38d4439f3@wordpress.org>
References: <051.4c9531ffc501edf899ea06d38d4439f3@wordpress.org>
Message-ID: <066.8cf472e38b4160046e02d13f71abeafc@wordpress.org>

#65225: tests: Add unit tests for wp_ajax_date_format()
----------------------------+------------------------------
 Reporter:  pbearne         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  tests
----------------------------+------------------------------
Changes (by pbearne):

 * keywords:  has-patch has-unit-tests =>


Comment:

 https://github.com/WordPress/wordpress-develop/pull/11811

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65225#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 23:18:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 23:18:37 -0000
Subject: [wp-trac] [WordPress Trac] #65227: Tests: Add unit tests for
 wp_ajax_wp_compression_test()
Message-ID: <051.1a189e9131d5f6683cdc553e0f962a40@wordpress.org>

#65227: Tests: Add unit tests for wp_ajax_wp_compression_test()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 The function wp_ajax_wp_compression_test() in src/wp-admin/includes/ajax-
 actions.php currently lacks formal unit test coverage in the correct
 location. This task involves adding/moving tests to verify that it
 correctly handles compression testing via AJAX.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65227>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue May 12 23:39:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 12 May 2026 23:39:27 -0000
Subject: [wp-trac] [WordPress Trac] #65228: Tests: Add unit tests for
 wp_ajax_time_format()
Message-ID: <051.8e95e553c21516b3818c38c3266f5141@wordpress.org>

#65228: Tests: Add unit tests for wp_ajax_time_format()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 The function wp_ajax_time_format() in src/wp-admin/includes/ajax-
 actions.php currently lacks unit test coverage. This task involves adding
 tests to verify that it correctly handles time format validation and
 returns the expected response.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65228>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 02:47:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 02:47:37 -0000
Subject: [wp-trac] [WordPress Trac] #65032: View transition admin bar
 quirks
In-Reply-To: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
References: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
Message-ID: <067.10b78a6f1c341dc66d87790fde3982a0@wordpress.org>

#65032: View transition admin bar quirks
----------------------------+------------------------
 Reporter:  zieladam        |       Owner:  audrasjb
     Type:  defect (bug)    |      Status:  reviewing
 Priority:  normal          |   Milestone:  7.0
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  ui
----------------------------+------------------------

Comment (by audrasjb):

 Thanks for the PR but to be honest, in my testing I'm not sure I can see
 any difference between the current visual implementation and the one
 proposed in the PR, and how it's supposed to improve the navigation. I was
 about to share two before/after videos but the visual feeling is pretty
 the same. Does anyone notice any difference before/after the patch is
 applied?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65032#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 03:02:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 03:02:52 -0000
Subject: [wp-trac] [WordPress Trac] #64986: preview needs gettext
In-Reply-To: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
References: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
Message-ID: <067.64b126a89dc14ae99dce956fbe737361@wordpress.org>

#64986: preview needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  good-first-bug has-patch changes-    |     Focuses:
  requested                                      |  accessibility
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62353" 62353]:
 {{{
 #!CommitTicketReference repository="" revision="62353"
 I18N: Add translator context to disambiguate translation strings for
 "Preview".

 This changeset disambiguates translation strings for "Preview" by adding a
 verb|noun context to its occurrences.

 Props timse201, audrasjb, anupkankale, mohamedahamed, rafaeldella,
 motylanogha, wildworks, jorbin, khokansardar, sergeybiryukov.
 Fixes #64986.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64986#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 03:03:56 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 03:03:56 -0000
Subject: [wp-trac] [WordPress Trac] #64986: preview needs gettext
In-Reply-To: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
References: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
Message-ID: <067.1a7276dc6a0b8af54b8bde219418fe45@wordpress.org>

#64986: preview needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch dev-        |     Focuses:
  feedback fixed-major i18n-change               |  accessibility
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  good-first-bug has-patch changes-requested => good-first-bug
     has-patch dev-feedback fixed-major i18n-change
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for second committer sign-off and backport to branch 7.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64986#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 03:26:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 03:26:08 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.0e02ce55ec07c2fa3457a3679856cac6@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests fixed-major dev-reviewed  |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:
     has-screenshots admin-reskin has-patch has-unit-tests dev-feedback
     fixed-major
     =>
     has-screenshots admin-reskin has-patch has-unit-tests fixed-major dev-
     reviewed


Comment:

 Marking as `dev-reviewed`. Let's backport [62349] to branch 7.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:60>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 03:28:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 03:28:29 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.c2618bf1d0989f253147808511dbf0ec@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-------------------------------------------------+-------------------------
 Reporter:  huzaifaalmesbah                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  Toolbar                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots admin-reskin has-    |     Focuses:  ui, css
  patch has-unit-tests fixed-major dev-reviewed  |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 In [changeset:"62354" 62354]:
 {{{
 #!CommitTicketReference repository="" revision="62354"
 Toolbar: Revert add CSS from admin color scheme on front-end.

 The implementation issues a server-side HTTP request on every front-end
 page load and extracts the toolbar CSS via fragile substring matching.
 Alternatives are too large to land this late in the release cycle, so the
 fix is deferred to a future release.

 Reverts [62025].

 Reviewed by audrasjb, wildworks.
 Merges [62349] to the 7.0 branch.
 Props desrosj, jorbin, mukesh27, sabernhardt, wildworks.
 See #64762.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:61>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 03:29:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 03:29:32 -0000
Subject: [wp-trac] [WordPress Trac] #64762: Frontend admin toolbar not
 using updated admin color scheme
In-Reply-To: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
References: <059.0e31afc455ee11847f5a061f732569ee@wordpress.org>
Message-ID: <074.48c0fdfc93d36d03ff085f141fb9a17f@wordpress.org>

#64762: Frontend admin toolbar not using updated admin color scheme
-----------------------------+-----------------------
 Reporter:  huzaifaalmesbah  |       Owner:  audrasjb
     Type:  defect (bug)     |      Status:  reopened
 Priority:  normal           |   Milestone:  7.0.1
Component:  Toolbar          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  admin-reskin     |     Focuses:  ui, css
-----------------------------+-----------------------
Changes (by audrasjb):

 * keywords:
     has-screenshots admin-reskin has-patch has-unit-tests fixed-major dev-
     reviewed
     => admin-reskin
 * milestone:  7.0 => 7.0.1


Comment:

 I backported the [62349] revert to 7.0. Moving this ticket to 7.0.1 for
 further development.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64762#comment:62>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 04:27:36 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 04:27:36 -0000
Subject: [wp-trac] [WordPress Trac] #65229: Remove WordPress.org IP from
 function documentation
Message-ID: <048.852c75db714f15cd01915b327fd6f63b@wordpress.org>

#65229: Remove WordPress.org IP from function documentation
--------------------------+-----------------------------
 Reporter:  dd32          |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  HTTP API      |    Version:
 Severity:  trivial       |   Keywords:
  Focuses:  docs          |
--------------------------+-----------------------------
 A WordPress.org IP address (which may change over time) is currently in
 use in some function documentation.

 We might as well update that to point to a TEST-NET-xx address.

 I've randomly chosen `198.51.100.50` based on a google suggestion, to
 differentiate from 192.xxxxx that might be thought to be local at first
 glance.

 We could also use TEST-NET-3 if a more obviously public IP range is
 wanted:
 {{{
 TEST-NET-1: 192.0.2.0 - 192.0.2.255 (192.0.2.0/24)
 TEST-NET-2: 198.51.100.0 - 198.51.100.255 (198.51.100.0/24)
 TEST-NET-3: 203.0.113.0 - 203.0.113.255 (203.0.113.0/24)
 }}}

 PR attached.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65229>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 04:43:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 04:43:14 -0000
Subject: [wp-trac] [WordPress Trac] #65230: `redirect_canonical()` fails to
 redirect slug-based attachment URLs when `wp_attachment_pages_enabled` is
 disabled
Message-ID: <048.cfff71d2bf3e3525a104fb04952f7e3a@wordpress.org>

#65230: `redirect_canonical()` fails to redirect slug-based attachment URLs when
`wp_attachment_pages_enabled` is disabled
--------------------------+-----------------------------
 Reporter:  dd32          |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Media         |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 When attachment pages are disabled (`wp_attachment_pages_enabled = 0`) and
 pretty permalinks are in use, visiting an attachment via its slug URL
 (e.g. `/my-image-jpg/`) returns a 200 with the attachment page rendered,
 instead of redirecting to the file. The query-string form
 (`?attachment_id=123`) for the same attachment correctly redirects.

 This is a follow-up to #59866, which addressed the logged-in/anonymous
 discrepancy but did not cover the slug-URL code path.

 **Steps to reproduce**

 1. Enable pretty permalinks (e.g. `/%postname%/`).
 2. Set `wp_attachment_pages_enabled` to `0`.
 3. Upload any media file.
 4. Visit the attachment's pretty permalink, e.g. `/my-image-jpg/`.

 **Expected:** 301 redirect to the file URL (e.g. `/wp-
 content/uploads/2026/05/my-image.jpg`).
 **Actual:** 200 response with an attachment page rendered.

 **Cause**

 In `src/wp-includes/canonical.php` (~line 553), inside the
 `is_attachment() && ! get_option( 'wp_attachment_pages_enabled' )` block:

 {{{#!php
 $attachment_id   = get_query_var( 'attachment_id' );
 $attachment_post = get_post( $attachment_id );
 }}}

 `get_query_var( 'attachment_id' )` is only populated for
 `?attachment_id=ID` URLs. For slug-based URLs the query var is empty, so
 `get_post( '' )` returns `null`, `$attachment_url` is falsy, and the
 redirect branch silently falls through.

 **Prior tickets**

 - #59866 — Attachment pages are only disabled for users that are logged in
 (fixed in 6.4.3; this ticket covers the slug-URL gap missed there)
 - #57913 — Attachment pages need to have an "on" toggle (introduced the
 option)

 ''Note: AI was used in the preparation of this ticket.''

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65230>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 04:44:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 04:44:27 -0000
Subject: [wp-trac] [WordPress Trac] #65230: `redirect_canonical()` fails
 to redirect slug-based attachment URLs when `wp_attachment_pages_enabled`
 is disabled
In-Reply-To: <048.cfff71d2bf3e3525a104fb04952f7e3a@wordpress.org>
References: <048.cfff71d2bf3e3525a104fb04952f7e3a@wordpress.org>
Message-ID: <063.e44d71a33678b6f32f2b170340814e23@wordpress.org>

#65230: `redirect_canonical()` fails to redirect slug-based attachment URLs when
`wp_attachment_pages_enabled` is disabled
--------------------------+------------------------------
 Reporter:  dd32          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  6.4
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by dd32):

 * version:   => 6.4


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65230#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 04:48:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 04:48:30 -0000
Subject: [wp-trac] [WordPress Trac] #65231: Add Plugins > Favourites: Input
 field and Submit button are not properly horizontally aligned
Message-ID: <053.c1f3ff7c8f97857b0dc3e92d8d9fd822@wordpress.org>

#65231: Add Plugins > Favourites: Input field and Submit button are not properly
horizontally aligned
--------------------------+-----------------------------
 Reporter:  bayejid00     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:  ui            |
--------------------------+-----------------------------
 == Description ==

 On the '''Add Plugins > Favourites''' tab, the "Your WordPress.org
 username:" input field and the "Get Favorites" submit button are not
 properly horizontally aligned with each other. The button appears to be
 vertically offset relative to the input field, resulting in an
 inconsistent and visually unpolished UI.

 == Environment ==
 WP Version: 7.0-RC3
 PHP Version: 8.3

 == Steps to Reproduce ==

 Navigate to wp-admin > Plugins > Add New.
 Click on the "Favourites" tab.
 Observe the "Your WordPress.org username:" input field and the "Get
 Favorites" button.
 == Expected Result ==

 The input field and the "Get Favorites" button should be perfectly aligned
 on the same horizontal baseline.

 == Actual Result ==

 The "Get Favorites" button is not vertically centered with the input
 field, causing a misalignment in the layout.

 == Screenshot ==

 https://prnt.sc/zDQinNEC_7-V

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65231>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 06:00:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 06:00:04 -0000
Subject: [wp-trac] [WordPress Trac] #65032: View transition admin bar
 quirks
In-Reply-To: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
References: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
Message-ID: <067.504dc32fd3ceb02170d7b099a542c07c@wordpress.org>

#65032: View transition admin bar quirks
----------------------------+------------------------
 Reporter:  zieladam        |       Owner:  audrasjb
     Type:  defect (bug)    |      Status:  reviewing
 Priority:  normal          |   Milestone:  7.0
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  ui
----------------------------+------------------------

Comment (by nikunj8866):

 @audrasjb I've shared before/after screencasts here:
 https://core.trac.wordpress.org/ticket/65032#comment:14

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65032#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 06:23:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 06:23:38 -0000
Subject: [wp-trac] [WordPress Trac] #65162: /wp-includes/theme.json,
 line 296
In-Reply-To: <050.97bb4ff393b639a25a1fe617d4592e3d@wordpress.org>
References: <050.97bb4ff393b639a25a1fe617d4592e3d@wordpress.org>
Message-ID: <065.5ce6f50394d501af84a2426b74d8c1bd@wordpress.org>

#65162: /wp-includes/theme.json, line 296
-------------------------------+------------------------------
 Reporter:  jlwilz             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Themes             |     Version:  6.9.4
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by poena):

 * keywords:   => reporter-feedback


Comment:

 Hi @jlwilz
 Thank you for your suggestion.

 There are no current plans to remove or update the defaults. Do you have a
 suggestion specifically about changing the specificity?

 Like you already mentioned, the CSS was added to make sure that the
 elements are styled when neither the theme or the user adds styling.
 This is to make sure that the button blocks are are accessible, and that
 they have a default style that is distinct from regular links.
 The specificity is chosen so that it can be overwritten by the settings in
 the interface, and programmatically.


 Pinging @aaronrobertshaw in case you have anything to add.


 (I also want to add a note that changes to blocks, the block editor or
 theme.json need to be managed in the Gutenberg GitHub repository. Changes
 are tested in the plugin before they are merged into WordPress core.)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65162#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 06:27:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 06:27:01 -0000
Subject: [wp-trac] [WordPress Trac] #65162: Button block has overly
 opinionated default styling (was: /wp-includes/theme.json, line 296)
In-Reply-To: <050.97bb4ff393b639a25a1fe617d4592e3d@wordpress.org>
References: <050.97bb4ff393b639a25a1fe617d4592e3d@wordpress.org>
Message-ID: <065.29f1a048c62505fa60daac06ba5594cb@wordpress.org>

#65162: Button block has overly opinionated default styling
-------------------------------+------------------------------
 Reporter:  jlwilz             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Themes             |     Version:  6.9.4
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65162#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 06:28:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 06:28:18 -0000
Subject: [wp-trac] [WordPress Trac] #65157: Blocks: WordPress prevent
 videos from being set as backgrounds
In-Reply-To: <049.b5992ec627f0854820bdf57a9285b790@wordpress.org>
References: <049.b5992ec627f0854820bdf57a9285b790@wordpress.org>
Message-ID: <064.9c15d210c6e90801350134c2c92a9ccc@wordpress.org>

#65157: Blocks: WordPress prevent videos from being set as backgrounds
-------------------------------+-------------------------------------------
 Reporter:  wurds              |       Owner:  (none)
     Type:  feature request    |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Media              |     Version:
 Severity:  normal             |  Resolution:  wontfix
 Keywords:  reporter-feedback  |     Focuses:  ui, administration, template
  close                        |
-------------------------------+-------------------------------------------
Changes (by poena):

 * status:  new => closed
 * resolution:   => wontfix
 * milestone:  Awaiting Review =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65157#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 06:44:36 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 06:44:36 -0000
Subject: [wp-trac] [WordPress Trac] #65111: Twenty Sixteen: Center text
 in image captions
In-Reply-To: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
References: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
Message-ID: <071.2d04485e8f27aae06ea75d95ecd89e9b@wordpress.org>

#65111: Twenty Sixteen: Center text in image captions
-------------------------------------------------+-------------------------
 Reporter:  gaelbonithon                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Bundled Theme                        |     Version:  4.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch close 2nd-opinion needs-   |     Focuses:  css
  refresh                                        |
-------------------------------------------------+-------------------------
Changes (by poena):

 * keywords:  has-patch close 2nd-opinion => has-patch close 2nd-opinion
     needs-refresh


Comment:

 Using a block style is a good suggestion.


 @gaelbonithon I would suggest moving the registration outside of the theme
 setup and use the init hook.
 register_block_style was introduced in WP 5.3, and Twenty Sixteen supports
 WP version 4.4, so it needs to be wrapped in an {{{if ( function_exists(
 'register_block_style' ) ) {}}} condition, please see Twenty Thirteen for
 an example.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65111#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 06:48:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 06:48:14 -0000
Subject: [wp-trac] [WordPress Trac] #64986: preview needs gettext
In-Reply-To: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
References: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
Message-ID: <067.a4a01b44f2dfaaef5fd89d24819723ba@wordpress.org>

#64986: preview needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch fixed-      |     Focuses:
  major i18n-change dev-reviewed                 |  accessibility
-------------------------------------------------+-------------------------
Changes (by wildworks):

 * keywords:  good-first-bug has-patch dev-feedback fixed-major i18n-change
     => good-first-bug has-patch fixed-major i18n-change dev-reviewed


Comment:

 This is the second committer sign-off for [62353].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64986#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 07:13:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 07:13:41 -0000
Subject: [wp-trac] [WordPress Trac] #65108: Twenty Sixteen: barely
 visible bold text in 'blockquote'
In-Reply-To: <056.b4f29e9067554142b8542b27cd2c3419@wordpress.org>
References: <056.b4f29e9067554142b8542b27cd2c3419@wordpress.org>
Message-ID: <071.35bb81ac3ee380d37080ddcd79a72aec@wordpress.org>

#65108: Twenty Sixteen: barely visible bold text in 'blockquote'
-----------------------------------------------------+---------------------
 Reporter:  gaelbonithon                             |       Owner:  (none)
     Type:  enhancement                              |      Status:  new
 Priority:  normal                                   |   Milestone:  7.1
Component:  Bundled Theme                            |     Version:  4.4
 Severity:  normal                                   |  Resolution:
 Keywords:  has-patch has-test-info has-screenshots  |     Focuses:  css
-----------------------------------------------------+---------------------
Changes (by poena):

 * milestone:  Awaiting Review => 7.1


Comment:

 Hi
 I don't feel strongly either way, pinging @iamtakashi @karmatosed as it is
 their theme, in case they have any opinions about the design of the
 quotes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65108#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 07:20:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 07:20:07 -0000
Subject: [wp-trac] [WordPress Trac] #64986: preview needs gettext
In-Reply-To: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
References: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
Message-ID: <067.a1a5b55dc708fc7f89f380dd151cd6cf@wordpress.org>

#64986: preview needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  good-first-bug has-patch fixed-      |     Focuses:
  major i18n-change dev-reviewed                 |  accessibility
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62355" 62355]:
 {{{
 #!CommitTicketReference repository="" revision="62355"
 I18N: Add translator context to disambiguate translation strings for
 "Preview".

 This changeset disambiguates translation strings for "Preview" by adding a
 verb|noun context to its occurrences.

 Reviewed by audrasjb, wildworks.
 Merges [62353] to the 7.0 branch.
 Props timse201, audrasjb, anupkankale, mohamedahamed, rafaeldella,
 motylanogha, wildworks, jorbin, khokansardar, sergeybiryukov.
 Fixes #64986.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64986#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 08:03:47 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 08:03:47 -0000
Subject: [wp-trac] [WordPress Trac] #65107: Twenty Sixteen: italics lost
 in 'blockquote cite'
In-Reply-To: <056.76190b8b93b06d61c688feba76f9b9c9@wordpress.org>
References: <056.76190b8b93b06d61c688feba76f9b9c9@wordpress.org>
Message-ID: <071.c2e517c1d0510d04ff5d3e6db2ba48ef@wordpress.org>

#65107: Twenty Sixteen: italics lost in 'blockquote cite'
-----------------------------------+---------------------
 Reporter:  gaelbonithon           |       Owner:  (none)
     Type:  defect (bug)           |      Status:  new
 Priority:  normal                 |   Milestone:  7.1
Component:  Bundled Theme          |     Version:  4.4
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch 2nd-opinion  |     Focuses:  css
-----------------------------------+---------------------
Changes (by poena):

 * milestone:  Awaiting Review => 7.1


Comment:

 I was not able to apply the patch cleanly, but the actual change works
 well and I think this is a good solution.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65107#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 08:06:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 08:06:10 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.9c6867bdf94c6eb7a97acec350448cb5@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by fcoveram):

 Very nice. Great work. I'm confident going with this version.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:44>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 08:12:43 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 08:12:43 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.ebd2cb3816738a2424572e1156f792a3@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by Benjamin_Zekavica):

 @markoserb Great job! I’m happy with this version too. Thanks for updating
 the design.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:45>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 08:33:55 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 08:33:55 -0000
Subject: [wp-trac] [WordPress Trac] #65199: Tests: Add unit tests for
 wp_refresh_heartbeat_nonces()
In-Reply-To: <051.63c2699c6e4ee5eb797882912e57f78a@wordpress.org>
References: <051.63c2699c6e4ee5eb797882912e57f78a@wordpress.org>
Message-ID: <066.0dbc81676f33b1367bbf9bd5b3868f4a@wordpress.org>

#65199: Tests: Add unit tests for wp_refresh_heartbeat_nonces()
--------------------------------------+---------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65199#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 08:38:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 08:38:42 -0000
Subject: [wp-trac] [WordPress Trac] #65199: Tests: Add unit tests for
 wp_refresh_heartbeat_nonces()
In-Reply-To: <051.63c2699c6e4ee5eb797882912e57f78a@wordpress.org>
References: <051.63c2699c6e4ee5eb797882912e57f78a@wordpress.org>
Message-ID: <066.ad927c16ec51c8db2bd6302e1f80cab4@wordpress.org>

#65199: Tests: Add unit tests for wp_refresh_heartbeat_nonces()
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  SergeyBiryukov
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62356" 62356]:
 {{{
 #!CommitTicketReference repository="" revision="62356"
 Tests: Add unit tests for `wp_refresh_heartbeat_nonces()`.

 Follow-up to [44275].

 Props pbearne.
 Fixes #65199.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65199#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 08:57:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 08:57:27 -0000
Subject: [wp-trac] [WordPress Trac] #65232: Abilities API: Add a fast site
 health summary to `core/get-environment-info`
Message-ID: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>

#65232: Abilities API: Add a fast site health summary to `core/get-environment-
info`
---------------------------+--------------------
 Reporter:  gziolo         |      Owner:  (none)
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:  7.1
Component:  Abilities API  |    Version:  6.9
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+--------------------
 Extend `core/get-environment-info` with two additive changes:

  1. An optional `fields` input parameter that filters the response
 (mirroring `core/get-site-info`).
  2. A new `site_health` output field returning a high-level, LLM-friendly
 Site Health overview — "is everything working, what to improve, what is
 broken" — populated entirely from cached data.

 == Background ==

 `core/get-environment-info` shipped in 6.9 as part of the orientation
 layer for AI agents. Adding a cached Site Health summary lets agents
 answer "is anything on fire?" in the same call they already make for
 runtime context, without paying for a synchronous test run.

 Related discussion: [https://github.com/WordPress/ai/issues/40
 WordPress/ai#40].

 == Proposed shape ==

 {{{#!json
 {
   "environment": "production",
   "php_version": "8.2.10",
   "db_server_info": "mysql 8.0.35",
   "wp_version": "7.1.0",
   "site_health": {
     "status": "recommended",
     "counts": { "good": 12, "recommended": 3, "critical": 0 },
     "issues": [
       {
         "label": "Background updates are not working as expected.",
         "severity": "recommended",
         "recommendation": "Contact your hosting provider to ensure WP-Cron
 can run."
       }
     ],
     "truncated": false
   }
 }
 }}}

 == Behavioral rules ==

  * '''Read cache only.''' Populate `site_health` from WordPress's cached
 Site Health results — the same cache the admin dashboard widget reads.
 Never trigger a synchronous test run from this ability.
  * '''Unknown when uncached.''' If no cached results exist, return
 `status: "unknown"` with empty `counts` and `issues`, so the agent can
 distinguish "no data" from "clean bill of health".
  * '''Only actionable issues listed.''' `counts` covers all severities;
 `issues` includes only `recommended` and `critical` entries.
  * '''Bounded payload.''' Cap the `issues` list at 10 entries with
 `truncated: true` when exceeded.
  * '''Included by default.''' Omitting `fields` returns all properties
 including `site_health`, matching `core/get-site-info`. Passing `fields:
 ["php_version"]` filters down to just that property.

 Capability check unchanged: the existing `manage_options` gate on `core
 /get-environment-info` covers Site Health access.

 == Open question ==

 `core/get-environment-info` declares `idempotent: true`. The `site_health`
 field can vary across calls as the cache refreshes. The annotation remains
 accurate in the "no state change" sense but the response is not byte-
 stable. Worth documenting in the field description so adapters can
 communicate the nuance.

 == Acceptance criteria ==

  * `core/get-environment-info` accepts an optional `fields` input
 parameter that filters the response.
  * When `fields` is omitted, the response includes all properties — the
 existing 6.9 fields plus `site_health`.
  * `site_health` reads cached Site Health results only; no synchronous
 test execution under any input.
  * JSON Schema documents the new field with `title` and `description` on
 each sub-property so adapters can surface them to agents.
  * Unit tests cover: `fields` filtering, `site_health` with cached
 results, `site_health` with no cache, bounded `issues` list with
 `truncated: true`, and confirmation that no synchronous evaluation is
 triggered.
  * Documentation updated on the Abilities API reference pages (separate
 task).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65232>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:00:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:00:00 -0000
Subject: [wp-trac] [WordPress Trac] #36273: update_attached_file() on
 Windows will result in invalid image path when using native Windows
 directory separators
In-Reply-To: <050.4adc2ecadd40c52e986fa6f04690dbfd@wordpress.org>
References: <050.4adc2ecadd40c52e986fa6f04690dbfd@wordpress.org>
Message-ID: <065.6c9142d438e87a14e8eb80f65680621c@wordpress.org>

#36273: update_attached_file() on Windows will result in invalid image path when
using native Windows directory separators
----------------------------------------+------------------------------
 Reporter:  Whissi                      |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Media                       |     Version:  4.4.2
 Severity:  normal                      |  Resolution:
 Keywords:  needs-unit-tests has-patch  |     Focuses:
----------------------------------------+------------------------------

Comment (by shreya0shrivastava):

 Hi, I was able to reproduce this issue on 7.1-alpha-62161-src and
 confirmed the bug is still present.

 The fix passes $file through wp_normalize_path() after
 _wp_relative_upload_path(),
 which converts all backslashes to forward slashes before the value is
 stored
 in postmeta, preventing wp_unslash() from corrupting the path.

 Submitted a patch. Happy to make any changes based on feedback!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36273#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:03:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:03:24 -0000
Subject: [wp-trac] [WordPress Trac] #65232: Abilities API: Add a fast
 site health summary to `core/get-environment-info`
In-Reply-To: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
References: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
Message-ID: <065.b950f4982ab6a6470638354131e80ba1@wordpress.org>

#65232: Abilities API: Add a fast site health summary to `core/get-environment-
info`
---------------------------+-----------------------
 Reporter:  gziolo         |       Owner:  gziolo
     Type:  enhancement    |      Status:  assigned
 Priority:  normal         |   Milestone:  7.1
Component:  Abilities API  |     Version:  6.9
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+-----------------------
Changes (by gziolo):

 * owner:  (none) => gziolo
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65232#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:04:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:04:51 -0000
Subject: [wp-trac] [WordPress Trac] #64596: Abilities API: Allow ability
 names to contain multiple slug fragments (2-4 segments)
In-Reply-To: <060.74f0d53f8f168f6d8e4740aae322ab76@wordpress.org>
References: <060.74f0d53f8f168f6d8e4740aae322ab76@wordpress.org>
Message-ID: <075.514e3bef5966c7a53c74e7c5d19cc9dd@wordpress.org>

#64596: Abilities API: Allow ability names to contain multiple slug fragments (2-4
segments)
------------------------------------------------+------------------------
 Reporter:  jorgefilipecosta                    |       Owner:  justlevin
     Type:  enhancement                         |      Status:  assigned
 Priority:  normal                              |   Milestone:  7.1
Component:  Abilities API                       |     Version:  6.9
 Severity:  normal                              |  Resolution:
 Keywords:  abilities has-patch has-unit-tests  |     Focuses:
------------------------------------------------+------------------------
Changes (by gziolo):

 * owner:  jorgefilipecosta => justlevin
 * status:  reopened => assigned
 * version:  trunk => 6.9
 * milestone:   => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64596#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:05:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:05:22 -0000
Subject: [wp-trac] [WordPress Trac] #64596: Abilities API: Allow ability
 names to contain multiple slug fragments (2-4 segments)
In-Reply-To: <060.74f0d53f8f168f6d8e4740aae322ab76@wordpress.org>
References: <060.74f0d53f8f168f6d8e4740aae322ab76@wordpress.org>
Message-ID: <075.cbbc3c6a9c4fec1e3890be0cdd8179ab@wordpress.org>

#64596: Abilities API: Allow ability names to contain multiple slug fragments (2-4
segments)
------------------------------------------------+-------------------------
 Reporter:  jorgefilipecosta                    |       Owner:  justlevine
     Type:  enhancement                         |      Status:  assigned
 Priority:  normal                              |   Milestone:  7.1
Component:  Abilities API                       |     Version:  6.9
 Severity:  normal                              |  Resolution:
 Keywords:  abilities has-patch has-unit-tests  |     Focuses:
------------------------------------------------+-------------------------
Changes (by gziolo):

 * owner:  justlevin => justlevine


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64596#comment:29>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:23:56 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:23:56 -0000
Subject: [wp-trac] [WordPress Trac] #65111: Twenty Sixteen: Center text
 in image captions
In-Reply-To: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
References: <056.c3ba973b7320165fb70c9efb0d35f5aa@wordpress.org>
Message-ID: <071.a00943cae4adc673909112b328bf7a84@wordpress.org>

#65111: Twenty Sixteen: Center text in image captions
-------------------------------------------------+-------------------------
 Reporter:  gaelbonithon                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Bundled Theme                        |     Version:  4.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch close 2nd-opinion needs-   |     Focuses:  css
  refresh                                        |
-------------------------------------------------+-------------------------

Comment (by gaelbonithon):

 Replying to [comment:7 poena]:
 > Using a block style is a good suggestion.
 >
 >
 > @gaelbonithon I would suggest moving the registration outside of the
 theme setup and use the init hook.
 > register_block_style was introduced in WP 5.3, and Twenty Sixteen
 supports WP version 4.4, so it needs to be wrapped in an {{{if (
 function_exists( 'register_block_style' ) ) {}}} condition, please see
 Twenty Thirteen for an example.
 >

 Thanks for review, patch updated. I added `@since Twenty Sixteen 3.9`
 based on `readme.txt`; I hope that's correct.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65111#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:31:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:31:18 -0000
Subject: [wp-trac] [WordPress Trac] #64977: The `core/get-site-info`
 ability returns wrong locale code in the admin
In-Reply-To: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
References: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
Message-ID: <066.7e007d7b93e674801c16b8d31bf7aca2@wordpress.org>

#64977: The `core/get-site-info` ability returns wrong locale code in the admin
---------------------------------+---------------------
 Reporter:  afercia              |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  7.1
Component:  Abilities API        |     Version:  6.9
 Severity:  normal               |  Resolution:
 Keywords:  abilities has-patch  |     Focuses:
---------------------------------+---------------------

Comment (by gziolo):

 I see multiple patches attached to this ticket.
 https://github.com/WordPress/wordpress-develop/pull/11388 looks the
 closest, but it still would benefit from a unit test that covers this edge
 case. https://github.com/WordPress/wordpress-develop/pull/11502 seems
 correct, but it uses a subset of functionality that the former covers
 through `get_locale()` call. @afercia, does it fix the issue for you as
 well?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64977#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:32:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:32:00 -0000
Subject: [wp-trac] [WordPress Trac] #64616: Abilities API: Add
 core/update-settings ability
In-Reply-To: <060.cd320ddc5b3bb5e4352fe09a8b00fa9f@wordpress.org>
References: <060.cd320ddc5b3bb5e4352fe09a8b00fa9f@wordpress.org>
Message-ID: <075.907cfb4f1ec1b1fa552fa70e7552eaee@wordpress.org>

#64616: Abilities API: Add core/update-settings ability
------------------------------------------------+--------------------------
 Reporter:  jorgefilipecosta                    |       Owner:
                                                |  jorgefilipecosta
     Type:  enhancement                         |      Status:  assigned
 Priority:  normal                              |   Milestone:  7.1
Component:  Abilities API                       |     Version:  trunk
 Severity:  normal                              |  Resolution:
 Keywords:  abilities has-patch has-unit-tests  |     Focuses:
------------------------------------------------+--------------------------
Changes (by gziolo):

 * owner:  (none) => jorgefilipecosta
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64616#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:32:44 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:32:44 -0000
Subject: [wp-trac] [WordPress Trac] #64605: Add: WordPress Core get
 settings ability
In-Reply-To: <060.ca8183a5810b9dd79e27f9d24dd1d90b@wordpress.org>
References: <060.ca8183a5810b9dd79e27f9d24dd1d90b@wordpress.org>
Message-ID: <075.7fa63d9f49fa1519eafb9c96cc38db9f@wordpress.org>

#64605: Add: WordPress Core get settings ability
------------------------------------------------+--------------------------
 Reporter:  jorgefilipecosta                    |       Owner:
                                                |  jorgefilipecosta
     Type:  enhancement                         |      Status:  reopened
 Priority:  normal                              |   Milestone:  7.1
Component:  Abilities API                       |     Version:  trunk
 Severity:  normal                              |  Resolution:
 Keywords:  abilities has-patch has-unit-tests  |     Focuses:
------------------------------------------------+--------------------------
Changes (by gziolo):

 * version:   => trunk
 * milestone:  Future Release => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64605#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:37:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:37:15 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
Message-ID: <053.99059f8a98e642b44458327936606426@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
--------------------------------+----------------------------
 Reporter:  wildworks           |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  7.0
Component:  General             |    Version:
 Severity:  normal              |   Keywords:  good-first-bug
  Focuses:  ui, administration  |
--------------------------------+----------------------------
 This is likely due to the button height being standardized to 40px in
 version 7.0. I propose we take this opportunity to refactor the two
 buttons using a flex layout. The current approach of using line-height for
 alignment is unstable.

 === Steps to reproduce

 1. Access Posts > Tags
 2. Create a tag.
 3. Edit the tag.
 4. Check the Alignment of the delete button.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:37:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:37:52 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.de96ff93d879b3cc0519fdad69ae6e34@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
----------------------------+---------------------------------
 Reporter:  wildworks       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  7.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  good-first-bug  |     Focuses:  ui, administration
----------------------------+---------------------------------
Changes (by wildworks):

 * Attachment "delete-button-alignment.png" added.

 Comparison of the delete button's position between 6.9 and 7.0

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:43:09 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:43:09 -0000
Subject: [wp-trac] [WordPress Trac] #65105: Details Block - Enhancement
 Request
In-Reply-To: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
References: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
Message-ID: <065.de65b6caa3348f4e0a50bf6da9196b15@wordpress.org>

#65105: Details Block - Enhancement Request
-------------------------------------+------------------------------
 Reporter:  mowill                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Editor                   |     Version:  6.9.4
 Severity:  normal                   |  Resolution:
 Keywords:  close reporter-feedback  |     Focuses:
-------------------------------------+------------------------------
Changes (by poena):

 * keywords:   => close reporter-feedback
 * component:  Posts, Post Types => Editor


Comment:

 Hi
 Is this specifically for the WordPress training team or campus connect
 sites?

 For support about styling blocks, please use the support forums.
 https://wordpress.org/support/forums/
 The details block already has a border style option, that you will need to
 use to set the border.
 The border can be set either using the settings in the interface, or using
 code.
 https://wordpress.org/documentation/article/details-block/#border


 Changes to blocks are first tested in the Gutenberg plugin.
 All feature requests and bug reports related to blocks need to be reported
 in the Gutenberg GitHub repository.
 This also includes suggestions for new blocks.
 Please use the search first to make sure that it has not already been
 reported.

 https://github.com/WordPress/gutenberg/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BBlock%5D%20Details%22

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65105#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:43:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:43:39 -0000
Subject: [wp-trac] [WordPress Trac] #65234: Abilities API: Expand
 `core/get-user-info` with profile fields and filtering
Message-ID: <050.41c4d727ae3ba530fe2d59628873aa0a@wordpress.org>

#65234: Abilities API: Expand `core/get-user-info` with profile fields and
filtering
---------------------------+----------------------
 Reporter:  gziolo         |      Owner:  (none)
     Type:  enhancement    |     Status:  assigned
 Priority:  normal         |  Milestone:  7.1
Component:  Abilities API  |    Version:  6.9
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+----------------------
 Two additive changes to `core/get-user-info` (shipped in 6.9):

  1. Expand the response with five standard profile fields: `first_name`,
 `last_name`, `nickname`, `description`, `user_url`.
  2. Add an optional `fields` input parameter that filters the response to
 a subset of properties, mirroring the pattern already used by `core/get-
 site-info`.

 Field naming follows WP-CLI conventions: `wp_users` columns keep their
 `user_` prefix (`user_url`); user-meta fields are unprefixed
 (`first_name`, `last_name`, `nickname`, `description`).

 == Proposed shape ==

 Default response (no `fields` parameter) after the change:

 {{{#!json
 {
   "id": 1,
   "display_name": "Jane Doe",
   "user_nicename": "jane-doe",
   "user_login": "jane",
   "roles": ["administrator"],
   "locale": "en_US",
   "first_name": "Jane",
   "last_name": "Doe",
   "nickname": "Jane",
   "description": "Site administrator and contributor.",
   "user_url": "https://example.com"
 }
 }}}

 Filtered response with `fields: ["display_name", "first_name",
 "last_name"]`:

 {{{#!json
 {
   "display_name": "Jane Doe",
   "first_name": "Jane",
   "last_name": "Doe"
 }
 }}}

 == Behavioral rules ==

  * '''Included by default, opt-out via `fields`.''' Omitting `fields`
 returns all properties, matching `core/get-site-info`. Passing `fields:
 ["display_name"]` filters down to just that property.
  * '''Schema-validated field names.''' Each entry in `fields` must be one
 of the declared output properties; invalid names are rejected by JSON
 Schema `enum` validation.
  * Capability check unchanged: `is_user_logged_in()`.
  * Annotations unchanged: `readonly: true`, `destructive: false`,
 `idempotent: true`.

 == Acceptance criteria ==

  * `core/get-user-info` returns the five additional fields (`first_name`,
 `last_name`, `nickname`, `description`, `user_url`) alongside the existing
 6.9 fields.
  * `core/get-user-info` accepts an optional `fields` input parameter that
 filters the response to the requested subset.
  * When `fields` is omitted, the response includes all properties.
  * Invalid field names in `fields` are rejected via schema validation
 before execution.
  * JSON Schema documents each new field with `title` and `description` so
 adapters (MCP, WebMCP) can surface them.
  * Unit test coverage in `tests/phpunit/tests/abilities-api/` for:
 expanded read output, `fields` filtering with valid subset, schema
 rejection of invalid field names, and unauthenticated denial.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65234>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:44:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:44:02 -0000
Subject: [wp-trac] [WordPress Trac] #65234: Abilities API: Expand
 `core/get-user-info` with profile fields and filtering
In-Reply-To: <050.41c4d727ae3ba530fe2d59628873aa0a@wordpress.org>
References: <050.41c4d727ae3ba530fe2d59628873aa0a@wordpress.org>
Message-ID: <065.2cace49bb3710be9fa8ed17e80dd7ac3@wordpress.org>

#65234: Abilities API: Expand `core/get-user-info` with profile fields and
filtering
---------------------------+-----------------------
 Reporter:  gziolo         |       Owner:  gziolo
     Type:  enhancement    |      Status:  assigned
 Priority:  normal         |   Milestone:  7.1
Component:  Abilities API  |     Version:  6.9
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+-----------------------
Changes (by gziolo):

 * owner:  (none) => gziolo


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65234#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:44:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:44:31 -0000
Subject: [wp-trac] [WordPress Trac] #64977: The `core/get-site-info`
 ability returns wrong locale code in the admin
In-Reply-To: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
References: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
Message-ID: <066.ed8c598f02ad3fc22eb7ed2ace6b5f65@wordpress.org>

#64977: The `core/get-site-info` ability returns wrong locale code in the admin
---------------------------------+-----------------------
 Reporter:  afercia              |       Owner:  gziolo
     Type:  defect (bug)         |      Status:  assigned
 Priority:  normal               |   Milestone:  7.1
Component:  Abilities API        |     Version:  6.9
 Severity:  normal               |  Resolution:
 Keywords:  abilities has-patch  |     Focuses:
---------------------------------+-----------------------
Changes (by gziolo):

 * owner:  (none) => gziolo
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64977#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:46:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:46:52 -0000
Subject: [wp-trac] [WordPress Trac] #64209: Allow abilities to be
 deprecated
In-Reply-To: <050.a391ff877fb79c2a859ee999e4a9d48c@wordpress.org>
References: <050.a391ff877fb79c2a859ee999e4a9d48c@wordpress.org>
Message-ID: <065.9b37f273b6187c3b4a6a009450d5f2d5@wordpress.org>

#64209: Allow abilities to be deprecated
---------------------------------+---------------------
 Reporter:  jorbin               |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  7.1
Component:  Abilities API        |     Version:  6.9
 Severity:  normal               |  Resolution:
 Keywords:  abilities has-patch  |     Focuses:
---------------------------------+---------------------

Comment (by gziolo):

 @jason_the_adams, is that something on your radar for inclusion in
 WordPress 7.1? Can I assign it to you?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64209#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 09:50:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 09:50:00 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.2d00f766e3e47950faee8beaa7f3cfa3@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by parinpanjari):

 @markoserb Yes, this updated version looks great. Thanks for the updated
 design.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 10:20:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 10:20:53 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.765d4062ed2a2efb83a5f68cf7d898fc@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
--------------------------------------+---------------------------------
 Reporter:  wildworks                 |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.0
Component:  General                   |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  ui, administration
--------------------------------------+---------------------------------

Comment (by tusharbharti):

 Seems like the PR description rendering broke 😅

 [[Image(https://i.ibb.co/j9kPRXYP/image.png)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 10:49:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 10:49:30 -0000
Subject: [wp-trac] [WordPress Trac] #65105: Details Block - Enhancement
 Request
In-Reply-To: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
References: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
Message-ID: <065.2a9f39d074bd3b4e6f3229aecb344787@wordpress.org>

#65105: Details Block - Enhancement Request
-------------------------------------+------------------------------
 Reporter:  mowill                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Editor                   |     Version:  6.9.4
 Severity:  normal                   |  Resolution:
 Keywords:  close reporter-feedback  |     Focuses:
-------------------------------------+------------------------------

Comment (by mowill):

 No, this is for anyone who creates courses and are WordPress users.

 Think about it. There websites out there now called "Teachable," "Kajabi,"
 and "Thinkific" to name a few where we can create courses. Why should I
 have to use a 3rd party company when WordPess can create a block for some
 basic functionality.

 Is there a particular reason why this area has not been addressed?

 We have to buy a subscription to those websites because WordPress cannot
 natively let you create a course. It's 2026. There are millions of
 WordPress users and a good bit of us have websites were we are teaching
 material on how to do something. Why make us go buy another plugin when
 WordPress can have some basic functionality on creating a course?

 All we need is a way to format the course with a Module level and then a
 sub-level to add the lessons.

 The Details block is very close to being in a course format to use for a
 learning path or a general course. Whatever users are calling it.



 Replying to [comment:3 poena]:
 > Hi
 > Is this specifically for the WordPress training team or campus connect
 sites?
 >
 > For support about styling blocks, please use the support forums.
 > https://wordpress.org/support/forums/
 > The details block already has a border style option, that you will need
 to use to set the border.
 > The border can be set either using the settings in the interface, or
 using code.
 > https://wordpress.org/documentation/article/details-block/#border
 >
 >
 > Changes to blocks are first tested in the Gutenberg plugin.
 > All feature requests and bug reports related to blocks need to be
 reported in the Gutenberg GitHub repository.
 > This also includes suggestions for new blocks.
 > Please use the search first to make sure that it has not already been
 reported.
 >
 >
 https://github.com/WordPress/gutenberg/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BBlock%5D%20Details%22
 >
 >
 >

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65105#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 10:49:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 10:49:54 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.2539b817b271339183e0c04fc61ed615@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
---------------------------------------------+-----------------------------
 Reporter:  wildworks                        |       Owner:  (none)
     Type:  defect (bug)                     |      Status:  new
 Priority:  normal                           |   Milestone:  7.0
Component:  General                          |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  good-first-bug has-patch commit  |     Focuses:  ui,
                                             |  administration
---------------------------------------------+-----------------------------
Changes (by mukesh27):

 * keywords:  good-first-bug has-patch => good-first-bug has-patch commit


Comment:

 Mark ready for commit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 11:27:58 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 11:27:58 -0000
Subject: [wp-trac] [WordPress Trac] #65105: Details Block - Enhancement
 Request
In-Reply-To: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
References: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
Message-ID: <065.528eba9d69765538fa634dbee966946b@wordpress.org>

#65105: Details Block - Enhancement Request
-------------------------+------------------------------
 Reporter:  mowill       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:  6.9.4
 Severity:  normal       |  Resolution:
 Keywords:  close        |     Focuses:
-------------------------+------------------------------
Changes (by poena):

 * keywords:  close reporter-feedback => close


Comment:

 Hi
 Suggestions for new blocks needs to be submitted in the Gutenberg GitHub
 repository.
 It is not possible to keep track of discussions concerning multiple tasks
 in more than one location.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65105#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 11:46:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 11:46:00 -0000
Subject: [wp-trac] [WordPress Trac] #4328: Redirect Old Slugs feature
 needs to redirect slugs for pages, not just posts,
 and redirect old permalink structure
In-Reply-To: <061.08e3249ecdbdaa249399b8a86780b12d@wordpress.org>
References: <061.08e3249ecdbdaa249399b8a86780b12d@wordpress.org>
Message-ID: <076.15be726f03a534281688ee316230bd26@wordpress.org>

#4328: Redirect Old Slugs feature needs to redirect slugs for pages, not just
posts, and redirect old permalink structure
-------------------------------------------------+-------------------------
 Reporter:  Denis-de-Bernardy                    |       Owner:
                                                 |  SergeyBiryukov
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Canonical                            |     Version:  2.2
 Severity:  normal                               |  Resolution:
 Keywords:  needs-unit-tests needs-patch early   |     Focuses:
  has-test-info                                  |
-------------------------------------------------+-------------------------
Changes (by sukhendu2002):

 * keywords:  needs-unit-tests needs-patch early => needs-unit-tests needs-
     patch early has-test-info


Comment:

 == Reproduction Report

 === Description
 Testing whether visiting an old page slug after a slug change results in a
 404,
 as originally reported.

 === Environment
 - WordPress: 7.1-alpha-62161-src
 - PHP: 8.3.31
 - Server: nginx/1.29.8
 - Database: mysqli (Server: 8.4.9 / Client: mysqlnd 8.3.31)
 - Browser: Chrome 147.0.0.0
 - OS: macOS
 - Theme: Twenty Twenty-Five 1.5
 - MU Plugins: None activated
 - Plugins:
   * Test Reports 1.2.0

 === Steps to Reproduce
 1. Navigate to Pages → Add New, create a page with slug `test-page-
 original`, and publish it.
 2. Visit the page URL (e.g. `https://example.com/test-page-original/`).
 3. Edit the page and change its slug to `test-page-renamed`. Update/save.
 4. Navigate to the old URL `https://example.com/test-page-original/`.

 === Actual Results
 1. ❌ Error condition does not occur (cannot reproduce). Visiting
 `https://example.com/test-page-original/` correctly issues a 301 redirect
 to `https://example.com/test-page-renamed/`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/4328#comment:64>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 11:59:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 11:59:39 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.2df194d4ad01b9a005dd8a95fcfc1814@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
---------------------------------------------+-----------------------------
 Reporter:  wildworks                        |       Owner:  wildworks
     Type:  defect (bug)                     |      Status:  closed
 Priority:  normal                           |   Milestone:  7.0
Component:  General                          |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  good-first-bug has-patch commit  |     Focuses:  ui,
                                             |  administration
---------------------------------------------+-----------------------------
Changes (by wildworks):

 * owner:  (none) => wildworks
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62357" 62357]:
 {{{
 #!CommitTicketReference repository="" revision="62357"
 Taxonomy: Fix delete button alignment on Edit Tag screen.

 The delete button on the Edit Tag screen was misaligned after the form
 control updates in [61645]. Switch the action buttons row to a flexbox
 layout for stable alignment.

 Follow-up to [61645].

 Props mukesh27, tusharbharti, wildworks.
 Fixes #65233.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 12:00:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 12:00:25 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.4c9994d5395628ceeae01cf57c022ba1@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:  wildworks
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch dev-        |     Focuses:  ui,
  feedback                                       |  administration
-------------------------------------------------+-------------------------
Changes (by wildworks):

 * keywords:  good-first-bug has-patch commit => good-first-bug has-patch
     dev-feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening #65233 to request backporting [62357] to the 7.0 branch

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 12:26:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 12:26:52 -0000
Subject: [wp-trac] [WordPress Trac] #64986: preview needs gettext
In-Reply-To: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
References: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
Message-ID: <067.e59189a01f711a8bab3e8cabe5887b8d@wordpress.org>

#64986: preview needs gettext
-------------------------------------------------+-------------------------
 Reporter:  timse201                             |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  I18N                                 |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch fixed-      |     Focuses:
  major i18n-change dev-reviewed                 |  accessibility
-------------------------------------------------+-------------------------
Changes (by timse201):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Thanks for your work.
 But the initial ticket was about preview "%s". We need a fix for this,
 too.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64986#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 13:29:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 13:29:31 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.ae8e7078adc93f832b5ccd5026d5aea5@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by fcoveram):

 The version shared above by @markoserb is in the
 [https://www.figma.com/design/aeMDWlqrwWarqDQaTwB0Nh/7.0-Highlight-Grid--
 Microsite--About-Page?node-id=6006-5640&m=dev main page in Figma] with the
 rest of assets.

 Please use that link as a source of truth.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:47>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 13:52:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 13:52:12 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.e5609c894cde28d86ac7cbe789932bc7@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:  wildworks
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch dev-        |     Focuses:  ui,
  feedback                                       |  administration
-------------------------------------------------+-------------------------

Comment (by tusharbharti):

 Hi @wildworks, Just to confirm, should I open a backport PR for 7.0, or
 will the maintainers handle it?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 13:58:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 13:58:28 -0000
Subject: [wp-trac] [WordPress Trac] #65083: Toolbar: Simplify profile
 item by removing "Howdy, <UserName>" text and using a circular avatar
In-Reply-To: <052.c183d6662a08679fa3f3f68694d851e3@wordpress.org>
References: <052.c183d6662a08679fa3f3f68694d851e3@wordpress.org>
Message-ID: <067.06646882cafc61150df24b7d7184dfe5@wordpress.org>

#65083: Toolbar: Simplify profile item by removing "Howdy, <UserName>" text and
using a circular avatar
-------------------------------------+-------------------------------------
 Reporter:  lucasmdo                 |       Owner:  audrasjb
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Toolbar                  |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-design-  |     Focuses:  ui, accessibility,
  feedback                           |  css, administration
-------------------------------------+-------------------------------------

Comment (by Joen):

 > Howdy has a long tradition of being in WordPress. It's a part of the
 flavor of WordPress. It helps set the tone and humanizes the experience of
 using WordPress.This WordCamp talk from a committer emeritus lays out why
 it's valuable and thus should absolutly stay. It's also something that a
 number of localizations get to have some fun with to really make WordPress
 feel at home. Howzit, G'day, and Ahoy all help users feel at home inside
 WordPress.

 This is a solid comment, and I'd like to respond to it. Because I think
 it's pretty critical that this aspect be addressed head-on. If we lose the
 flavor, or "character" of WordPress, we lose something special, we don't
 want that.

 Where I agree with the direction of this issue, however, is that it
 shouldn't stay in the toolbar where it is today. It should move into
 places where that character has a chance to shine and actually be
 meaningful.

 The thing is, the adminbar is a permanent fixture; it's like the app-bar
 at the top of MacOS: logo in the top left, menu items next to it, widgets
 on the right. It is **prime real-estate**, the most important part of your
 screen, because it is always there. Howdy is not a good fit there, just
 like the username itself isn't, because it takes up a lot of horisontal
 space that is more meaningfully leveraged by plugins, or future WordPress
 core features such as notifications or improved help. It also doesn't
 belong there because through always being there, instead of being a moment
 of character, we are actively diluting that character.

 Where "Howdy [username]" would be meaningful, however, could be in the
 menu that opened as soon as you click or hover the avatar. Simply moving
 it inside the menu, for me, bridges the gap. It's there when you are
 likely to engage with it, but it isn't permanently reserving key real-
 estate.

 I would go on to add, it feels like an obvious phrase to open WordPress
 itself with: instead of the dashboard having a plain "Dashboard" title,
 say "Howdy Lucas" there.

 Those are crucial moments where the user is in a mindset to absorb and
 appreciate the character.

 What do you think?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65083#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 14:05:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 14:05:10 -0000
Subject: [wp-trac] [WordPress Trac] #65105: Details Block - Enhancement
 Request
In-Reply-To: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
References: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
Message-ID: <065.8ef0a7edffb92228c18fe41fac7a275d@wordpress.org>

#65105: Details Block - Enhancement Request
-------------------------+------------------------------
 Reporter:  mowill       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:  6.9.4
 Severity:  normal       |  Resolution:
 Keywords:  close        |     Focuses:
-------------------------+------------------------------

Comment (by mowill):

 Replying to [comment:5 poena]:
 > Hi
 > Suggestions for new blocks needs to be submitted in the Gutenberg GitHub
 repository.
 > It is not possible to keep track of discussions concerning multiple
 tasks in more than one location.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65105#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 14:06:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 14:06:06 -0000
Subject: [wp-trac] [WordPress Trac] #65105: Details Block - Enhancement
 Request
In-Reply-To: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
References: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
Message-ID: <065.2c9086b04719a47f65b8893074106230@wordpress.org>

#65105: Details Block - Enhancement Request
-------------------------+------------------------------
 Reporter:  mowill       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:  6.9.4
 Severity:  normal       |  Resolution:
 Keywords:  close        |     Focuses:
-------------------------+------------------------------

Comment (by mowill):

 Replying to [comment:5 poena]:
 > Hi
 > Suggestions for new blocks needs to be submitted in the Gutenberg GitHub
 repository.
 > It is not possible to keep track of discussions concerning multiple
 tasks in more than one location.

 I apologize. I don't know what that means. I don't know where the
 Gutenberg github repository is. Please advise on how to do this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65105#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 14:07:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 14:07:10 -0000
Subject: [wp-trac] [WordPress Trac] #64600: [E_WARNING] Undefined array
 key "full" in wp-includes/media.php on line 4678
In-Reply-To: <050.0f1e82e2eac77bb297fdd19fa394d0b2@wordpress.org>
References: <050.0f1e82e2eac77bb297fdd19fa394d0b2@wordpress.org>
Message-ID: <065.1fc95057443531e6483179a03d39fd75@wordpress.org>

#64600: [E_WARNING] Undefined array key "full" in wp-includes/media.php on line
4678
--------------------------+------------------------------
 Reporter:  ArtZ91        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  6.9.1
 Severity:  minor         |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------

Comment (by mikemeinz):

 I am seeing this on WordPress version 6.9.4 in my debug.log.

 {{{
 PHP Warning:  Undefined array key "full" in
 /home/<myservername>/public_html/wp-includes/media.php on line 4678
 }}}

 There is no information on what is calling a function in media.php just
 that one line error message.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64600#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 14:07:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 14:07:41 -0000
Subject: [wp-trac] [WordPress Trac] #65105: Details Block - Enhancement
 Request
In-Reply-To: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
References: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
Message-ID: <065.b50f428d44655ca5efce4c03dfeb74aa@wordpress.org>

#65105: Details Block - Enhancement Request
-------------------------+------------------------------
 Reporter:  mowill       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:  6.9.4
 Severity:  normal       |  Resolution:
 Keywords:  close        |     Focuses:
-------------------------+------------------------------

Comment (by mowill):

 Replying to [comment:5 poena]:
 > Hi
 > Suggestions for new blocks needs to be submitted in the Gutenberg GitHub
 repository.
 > It is not possible to keep track of discussions concerning multiple
 tasks in more than one location.

 I'm confused. This form has an option to submit a new enhancement request.
 Are you saying this is not the place to request a new enhancement?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65105#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 14:08:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 14:08:15 -0000
Subject: [wp-trac] [WordPress Trac] #65235: Upload error in UI should
 specifically convey if a status 413 was received
Message-ID: <050.aa32f2afaf23da6c8580baae1448cc54@wordpress.org>

#65235: Upload error in UI should specifically convey if a status 413 was received
-------------------------+-----------------------------
 Reporter:  leedxw       |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Upload       |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 In the event that a user attempts to upload a media file that is below the
 maximum php filesize, but where the POST is above the limit set by the web
 server, the error message (en) is:

 > Unexpected response from the server. The file may have been uploaded
 successfully. Check in the Media Library or reload the page.


 (It's a common configuration in web servers to set the max post/body sizes
 to be the same value as the maximum file size, but - since there's an
 overhead - files that appear to be just below the advertised limit will
 fail to upload.)

 When {{{/wp-admin/async-upload.php}}} receives a 413 code the user
 presented error message should include this code and the explanation -
 such as "413 Request Entity Too Large" (en) - since this is the
 information that will be useful for whoever does technical support for the
 site.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65235>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 14:15:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 14:15:15 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.38e69de8fdf015d514e47ec6d354793e@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:  wildworks
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch dev-        |     Focuses:  ui,
  feedback                                       |  administration
-------------------------------------------------+-------------------------

Comment (by wildworks):

 @tusharbharti, you don't need to create a backport PR. Another committer
 will approve the commit to the trunk branch and then commit it to 7.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 14:21:09 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 14:21:09 -0000
Subject: [wp-trac] [WordPress Trac] #64779: Notes can be edited and
 deleted by other users
In-Reply-To: <052.5551217cf4306aea1e0cf167b5c43983@wordpress.org>
References: <052.5551217cf4306aea1e0cf167b5c43983@wordpress.org>
Message-ID: <067.6d7f592c79bee8ca1f32a1d0d998d092@wordpress.org>

#64779: Notes can be edited and deleted by other users
--------------------------------------+---------------------
 Reporter:  mindctrl                  |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Comments                  |     Version:  6.9
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by mindctrl):

 Replying to [comment:7 manfcarlo]:
 > I think the pre-existing behaviour (any user able to delete any note) is
 correct. If someone leaves a note with profanity or personal attacks, or a
 typo, it should be easy for others to delete/correct without having to
 contact someone with higher privileges. If someone is maliciously deleting
 or changing other users' notes, they would be better off having their
 editing access to the whole post revoked.

 While I agree that malicious users should have their access revoked, it
 doesn't solve the problem outlined above. To restate my concern:

 Since comments have no revision history, there's no way to see that a note
 was changed or what it originally said. A Contributor, for example, could
 edit an Admin's note on their own draft to say something the Admin never
 wrote, and anyone reviewing the post later would have no way of knowing.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64779#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 14:21:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 14:21:48 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.12e67fb3d2a4b42fe39fa05728d05557@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:  wildworks
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch dev-        |     Focuses:  ui,
  feedback                                       |  administration
-------------------------------------------------+-------------------------

Comment (by tusharbharti):

 Got it!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 15:23:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 15:23:27 -0000
Subject: [wp-trac] [WordPress Trac] #65212: Uncaught exception TypeError
 in formatting.php
In-Reply-To: <056.8ec695052ef9f9dd0ec6d09ae69f7db7@wordpress.org>
References: <056.8ec695052ef9f9dd0ec6d09ae69f7db7@wordpress.org>
Message-ID: <071.4b7f8e8703a25db37031af616f55d4eb@wordpress.org>

#65212: Uncaught exception TypeError in formatting.php
--------------------------+------------------------------
 Reporter:  harishtewari  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  6.9.4
 Severity:  normal        |  Resolution:  invalid
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------
Changes (by harishtewari):

 * status:  new => closed
 * resolution:   => invalid


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65212#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 15:24:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 15:24:13 -0000
Subject: [wp-trac] [WordPress Trac] #65231: Add Plugins > Favourites:
 Input field and Submit button are not properly horizontally aligned
In-Reply-To: <053.c1f3ff7c8f97857b0dc3e92d8d9fd822@wordpress.org>
References: <053.c1f3ff7c8f97857b0dc3e92d8d9fd822@wordpress.org>
Message-ID: <068.b698ffad6161391f231496aabda7340e@wordpress.org>

#65231: Add Plugins > Favourites: Input field and Submit button are not properly
horizontally aligned
--------------------------+--------------------------------------
 Reporter:  bayejid00     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0.1
Component:  Plugins       |     Version:
 Severity:  minor         |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, css, administration
--------------------------+--------------------------------------
Changes (by sabernhardt):

 * focuses:  ui => ui, css, administration
 * component:  General => Plugins
 * severity:  normal => minor
 * version:  trunk =>
 * milestone:  Awaiting Review => 7.0.1


Comment:

 The misalignment already occurred in 6.9 on small screens up to 782 pixels
 wide. With 7.0, the submit button can be slightly lower than the search
 text field in Chrome on larger screens when the paragraph height is 40.5
 pixels (it seems to happen when the top paragraph is either one or three
 lines, but not two or four lines). With Firefox and Windows 11, I only
 experience the misalignment at narrower screen widths.

 PR 11817 can fix the issue, but I do not think that `buttons.css` in `wp-
 includes` is the best place for a ruleset that applies to only one
 administration screen. I probably would add it to either `list-tables.css`
 or `common.css` in `wp-admin`, and the specificity could be reduced.

 I would have suggested using `flex`, similar to PR 11818, and I would like
 to consider both options.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65231#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 15:31:20 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 15:31:20 -0000
Subject: [wp-trac] [WordPress Trac] #45354: Adding index for meta_key
 and post_id in postmeta
In-Reply-To: <056.ed0283820e92025f40a31fbe52b0dd88@wordpress.org>
References: <056.ed0283820e92025f40a31fbe52b0dd88@wordpress.org>
Message-ID: <071.dd7b95d747c22d5ff3624bd6e2e99ce6@wordpress.org>

#45354: Adding index for meta_key and post_id in postmeta
-------------------------------------------------+-------------------------
 Reporter:  DuckDagobert                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Database                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing dev-feedback has-      |     Focuses:
  patch has-unit-tests                           |  performance
-------------------------------------------------+-------------------------
Changes (by ozgursar):

 * Attachment "before.png" added.

 Before patch PR10987

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45354>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 15:31:28 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 15:31:28 -0000
Subject: [wp-trac] [WordPress Trac] #65236: Tests: Add unit tests for
 wp_ajax_nopriv_heartbeat()
Message-ID: <051.b0f635c595e22d3640bebfa405563e23@wordpress.org>

#65236: Tests: Add unit tests for wp_ajax_nopriv_heartbeat()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 This ticket aims to add comprehensive unit test coverage for the
 wp_ajax_nopriv_heartbeat() function in src/wp-admin/includes/ajax-
 actions.php, which handles Heartbeat API requests in a no-privilege
 (logged-out) context.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65236>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 15:31:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 15:31:51 -0000
Subject: [wp-trac] [WordPress Trac] #45354: Adding index for meta_key
 and post_id in postmeta
In-Reply-To: <056.ed0283820e92025f40a31fbe52b0dd88@wordpress.org>
References: <056.ed0283820e92025f40a31fbe52b0dd88@wordpress.org>
Message-ID: <071.8e143d58e81ae59520b98ee4e2975555@wordpress.org>

#45354: Adding index for meta_key and post_id in postmeta
-------------------------------------------------+-------------------------
 Reporter:  DuckDagobert                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Database                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing dev-feedback has-      |     Focuses:
  patch has-unit-tests                           |  performance
-------------------------------------------------+-------------------------
Changes (by ozgursar):

 * Attachment "after.png" added.

 After patch PR 10987

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45354>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 15:32:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 15:32:21 -0000
Subject: [wp-trac] [WordPress Trac] #45354: Adding index for meta_key
 and post_id in postmeta
In-Reply-To: <056.ed0283820e92025f40a31fbe52b0dd88@wordpress.org>
References: <056.ed0283820e92025f40a31fbe52b0dd88@wordpress.org>
Message-ID: <071.cd7957d2c2f7dd871a037285a258a927@wordpress.org>

#45354: Adding index for meta_key and post_id in postmeta
-------------------------------------------------+-------------------------
 Reporter:  DuckDagobert                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Database                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing dev-feedback has-      |     Focuses:
  patch has-unit-tests                           |  performance
-------------------------------------------------+-------------------------
Changes (by ozgursar):

 * Attachment "seed-and-schema.jpg" added.

 Seed database and apply schema

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45354>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 15:39:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 15:39:42 -0000
Subject: [wp-trac] [WordPress Trac] #65171: wp_check_post_lock_window
 filter values below 120s break post lock detection in backgrounded tabs
In-Reply-To: <051.da93c0bf97890d05b794aa302384a283@wordpress.org>
References: <051.da93c0bf97890d05b794aa302384a283@wordpress.org>
Message-ID: <066.a31f9fc6afdbc3e2e9b08b0b95e89439@wordpress.org>

#65171: wp_check_post_lock_window filter values below 120s break post lock
detection in backgrounded tabs
-------------------------------------------------+-------------------------
 Reporter:  katag9k                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests needs-    |     Focuses:  ui,
  testing                                        |  javascript
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * keywords:  has-patch => has-patch needs-unit-tests needs-testing


Comment:

 @sukhendu2002 - the [https://github.com/WordPress/wordpress-
 develop/pull/11732 patch] looks good. It would be nice to add some unit
 tests, ideally reproducing the issue / fixed by the patch.

 @katag9k thanks for opening the ticket. Can you check if the patch from
 @sukhendu2002 fixes the issue for you?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65171#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 15:44:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 15:44:18 -0000
Subject: [wp-trac] [WordPress Trac] #45354: Adding index for meta_key
 and post_id in postmeta
In-Reply-To: <056.ed0283820e92025f40a31fbe52b0dd88@wordpress.org>
References: <056.ed0283820e92025f40a31fbe52b0dd88@wordpress.org>
Message-ID: <071.2cbbb25e5a50f7debbe4c12ec6ceaef9@wordpress.org>

#45354: Adding index for meta_key and post_id in postmeta
-------------------------------------------------+-------------------------
 Reporter:  DuckDagobert                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  7.1
Component:  Database                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing dev-feedback has-      |     Focuses:
  patch has-unit-tests                           |  performance
-------------------------------------------------+-------------------------

Comment (by ozgursar):

 == Patch Testing Report

 Patch Tested: https://github.com/WordPress/wordpress-develop/pull/10987

 === Environment
 - WordPress: 7.1-alpha-62161-src
 - PHP: 8.2.29
 - Server: nginx/1.29.4
 - Database: mysqli (Server: 8.4.7 / Client: mysqlnd 8.2.29)
 - Browser: Chrome 148.0.0.0
 - OS: macOS
 - Theme: Twenty Twenty-Five 1.5
 - MU Plugins: None activated
 - Plugins:
   * Code Snippets 3.9.6
   * Test Reports 1.2.1

 I created a benchmark tool using Claude that seeds the db and applies the
 key in the patch.

 === Steps taken
 1. Add the code snippet to your active theme's functions.php or using Code
 Snippets plugin from the GitHub Gist
 https://gist.github.com/ozgursar/a798c60cf3f8391de37895658e5e4c80
 2. Navigate to ''Tools > Postmeta Benchmark''
 3. Click ''Seed data'' to add 500 posts and 7500 meta rows to the database
 4. Click ''Run benchmark''
 5. Observe the keys and results
 6. Apply the patch
 7. Click `Apply schema (dbDelta)` to ensure composite key in the patch is
 applied to the db
 8. Run benchmark again and observe the key sizes and results.
 9. ✅ Patch is solving the problem

 === Expected result
 - The `Double JOIN` query should show the largest improvement after
 applying the patch, as it is the pattern most affected by the missing
 composite index.

 - MySQL previously had to scan all postmeta rows for each join condition
 separately. The `meta_key_id` index should appear in the active indexes
 list and the Size per index table after running Apply schema (dbDelta).

 === Additional Notes
 - The benchmark applies the schema using dbDelta( `wp_get_db_schema()` ),
 so it tests the exact index defined in the patch.

 === Screenshots/Screencast with results
 Before patch
 [[Image(https://core.trac.wordpress.org/raw-
 attachment/ticket/45354/before.png)]]

 Seeding DB and Applying Schema
 [[Image(https://core.trac.wordpress.org/raw-attachment/ticket/45354/seed-
 and-schema.jpg)]]

 After patch
 [[Image(https://core.trac.wordpress.org/raw-
 attachment/ticket/45354/after.png)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45354#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 17:00:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 17:00:15 -0000
Subject: [wp-trac] [WordPress Trac] #64966: Post-branching tasks
In-Reply-To: <051.a82468cb49b4755fefe8dd930932053e@wordpress.org>
References: <051.a82468cb49b4755fefe8dd930932053e@wordpress.org>
Message-ID: <066.1d9dd98b392835043bbe175e0f211214@wordpress.org>

#64966: Post-branching tasks
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  desrosj
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by desrosj):

 I'm going to update the relevant workflows to test `7.0-RC3` and then I am
 going to close this out in favor of a new ticket for post release so that
 the milestone can be cleared.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64966#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 17:03:56 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 17:03:56 -0000
Subject: [wp-trac] [WordPress Trac] #64966: Post-branching tasks
In-Reply-To: <051.a82468cb49b4755fefe8dd930932053e@wordpress.org>
References: <051.a82468cb49b4755fefe8dd930932053e@wordpress.org>
Message-ID: <066.da0cc014f9d2165be31e20dfba5e72b2@wordpress.org>

#64966: Post-branching tasks
----------------------------+----------------------
 Reporter:  desrosj         |       Owner:  desrosj
     Type:  task (blessed)  |      Status:  closed
 Priority:  normal          |   Milestone:  7.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:  fixed
 Keywords:  has-patch       |     Focuses:
----------------------------+----------------------
Changes (by desrosj):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62358" 62358]:
 {{{
 #!CommitTicketReference repository="" revision="62358"
 Build/Test Tools: Test against `7.0-RC3`.

 This updates the upgrade testing workflows to test against RC3. After 7.0
 final release, this should be updated to test `7.0` proper.

 Fixes #64966.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64966#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 18:39:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 18:39:10 -0000
Subject: [wp-trac] [WordPress Trac] #65237: Tests: Add unit tests for
 wp_ajax_fetch_list()
Message-ID: <051.22f3ca0fde3d38e298863529c192a38c@wordpress.org>

#65237: Tests: Add unit tests for wp_ajax_fetch_list()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 This ticket aims to add unit test coverage for the wp_ajax_fetch_list()
 function in src/wp-admin/includes/ajax-actions.php, which handles fetching
 list tables via AJAX.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65237>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 19:29:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 19:29:46 -0000
Subject: [wp-trac] [WordPress Trac] #64544: Core GB backport -
 individual block custom CSS
In-Reply-To: <056.72603e7ab1651a8e30467405450b7b4a@wordpress.org>
References: <056.72603e7ab1651a8e30467405450b7b4a@wordpress.org>
Message-ID: <071.9ae25c5c698a0d1575484a1d57ff96cf@wordpress.org>

#64544: Core GB backport - individual block custom CSS
---------------------------------------+-----------------------
 Reporter:  glendaviesnz               |       Owner:  ellatrix
     Type:  enhancement                |      Status:  closed
 Priority:  normal                     |   Milestone:  7.0
Component:  General                    |     Version:  trunk
 Severity:  normal                     |  Resolution:  fixed
 Keywords:  has-patch gutenberg-merge  |     Focuses:
---------------------------------------+-----------------------

Comment (by westonruter):

 In [changeset:"62359" 62359]:
 {{{
 #!CommitTicketReference repository="" revision="62359"
 Block Supports: Improve performance and hardening of block-level custom
 CSS rendering.

 Short-circuits the custom CSS support filter before the more expensive
 lookups so blocks without custom CSS return faster.

 Replaces the regex class name parsing in
 `wp_render_custom_css_class_name()` with a cheap `str_contains()` guard
 followed by an HTML spec-compliant `strtok()` walk over the className
 tokens. This avoids the regex engine for the common case where no `wp-
 custom-css-` class is present, and correctly handles tab/form-feed/CR/LF
 separators as well as classes such as `my-wp-custom-css-*` that merely
 contain the prefix as a substring after a hyphen.

 Also hardens both functions against malformed parsed blocks (non-string
 `className`, missing keys), tightens `@phpstan-param` array shapes, and
 corrects the `block_has_support()` `@param` to allow `WP_Block_Type|null`.
 Lastly, a `@return Generator<int, non-empty-string>` phpdoc tag is added
 to `WP_HTML_Tag_Processor::class_list()`.

 Developed in https://github.com/WordPress/wordpress-develop/pull/11686 and
 https://github.com/WordPress/gutenberg/pull/78217

 Follow-up to r61678.

 Props mukesh27, westonruter, ramonopoly, jonsurrell.
 See #64544, #64238.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64544#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 19:29:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 19:29:46 -0000
Subject: [wp-trac] [WordPress Trac] #64238: PHPStan code quality
 improvements for 7.0
In-Reply-To: <058.3d898e5edbfd206122933e3b070d763b@wordpress.org>
References: <058.3d898e5edbfd206122933e3b070d763b@wordpress.org>
Message-ID: <073.d253f53270a54c4f521bb671caf32c19@wordpress.org>

#64238: PHPStan code quality improvements for 7.0
--------------------------------------+-------------------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  closed
 Priority:  normal                    |   Milestone:  7.0
Component:  General                   |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  coding-standards
--------------------------------------+-------------------------------

Comment (by westonruter):

 In [changeset:"62359" 62359]:
 {{{
 #!CommitTicketReference repository="" revision="62359"
 Block Supports: Improve performance and hardening of block-level custom
 CSS rendering.

 Short-circuits the custom CSS support filter before the more expensive
 lookups so blocks without custom CSS return faster.

 Replaces the regex class name parsing in
 `wp_render_custom_css_class_name()` with a cheap `str_contains()` guard
 followed by an HTML spec-compliant `strtok()` walk over the className
 tokens. This avoids the regex engine for the common case where no `wp-
 custom-css-` class is present, and correctly handles tab/form-feed/CR/LF
 separators as well as classes such as `my-wp-custom-css-*` that merely
 contain the prefix as a substring after a hyphen.

 Also hardens both functions against malformed parsed blocks (non-string
 `className`, missing keys), tightens `@phpstan-param` array shapes, and
 corrects the `block_has_support()` `@param` to allow `WP_Block_Type|null`.
 Lastly, a `@return Generator<int, non-empty-string>` phpdoc tag is added
 to `WP_HTML_Tag_Processor::class_list()`.

 Developed in https://github.com/WordPress/wordpress-develop/pull/11686 and
 https://github.com/WordPress/gutenberg/pull/78217

 Follow-up to r61678.

 Props mukesh27, westonruter, ramonopoly, jonsurrell.
 See #64544, #64238.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64238#comment:127>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 19:30:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 19:30:27 -0000
Subject: [wp-trac] [WordPress Trac] #64544: Core GB backport -
 individual block custom CSS
In-Reply-To: <056.72603e7ab1651a8e30467405450b7b4a@wordpress.org>
References: <056.72603e7ab1651a8e30467405450b7b4a@wordpress.org>
Message-ID: <071.f2a5a2e2c267823b33151733680c1d6a@wordpress.org>

#64544: Core GB backport - individual block custom CSS
-------------------------------------------------+-------------------------
 Reporter:  glendaviesnz                         |       Owner:  ellatrix
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch gutenberg-merge fixed-     |     Focuses:
  major dev-feedback                             |
-------------------------------------------------+-------------------------
Changes (by westonruter):

 * keywords:  has-patch gutenberg-merge => has-patch gutenberg-merge fixed-
     major dev-feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Re-opening for merging r62359 into the `7.0` branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64544#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 20:09:09 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 20:09:09 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.bc4f0bf514da3a8b076c5a4828ab2c6a@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch                   |  administration
-------------------------------------+-------------------------------------
Changes (by sabernhardt):

 * Attachment "64686.wrap.diff" added.

 allows wide `.button` link text to wrap to another line, and aligns text
 to `start` instead of the right

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 20:11:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 20:11:00 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.1b8956589cf47e99a5fc982270334e7a@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch                   |  administration
-------------------------------------+-------------------------------------
Changes (by sabernhardt):

 * Attachment "wrapping-wide-button-text.png" added.

 wrapping long link text to another line in French, at 1600 pixels wide
 with the admin menu collapsed

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 20:14:45 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 20:14:45 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.5d37e6f91e92310f0a094c32097da1e9@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch                   |  administration
-------------------------------------+-------------------------------------

Comment (by sabernhardt):

 It is very late to redo the layout for next week's release, and PR 11820
 is not ready anyway.

 > One short-term solution is to increase the right margin for specific
 languages.

 My "Update Now" link in French, with the icon, is more than 188 pixels
 wide. The translation lengths are highly variable, and they can change at
 any time.

 The "Update Now" string with the 'plugin' context is only on the plugin
 install screen, so removing "now" from some long translations might be an
 option. However, "Install Now" is used on other screens, where it probably
 should not be abbreviated.

 Allowing the `.button` link text to wrap to another line seems to be the
 safest //temporary// change. It still is not good, but it prevents
 overlapping. The worst part of this idea is probably when someone clicks
 the link and it changes height along with the text as it progresses from
 "Update Now" to "Updating..." to "Updated!" (or "Install Now", etc.).

 I also considered adding a white background to these links. That probably
 is not safe enough, and the links still would overlap plugin names as they
 did in 6.9 (with an additional four pixels to their width).
 {{{
 .plugin-action-buttons li .button:not(.button-primary) {
         background: #fff;
 }
 }}}

 Partially related: #48648

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 22:12:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 22:12:22 -0000
Subject: [wp-trac] [WordPress Trac] #65238: Negative post id get_post is
 always false
Message-ID: <054.73245a6d04753314567b8d8e00205770@wordpress.org>

#65238: Negative post id get_post is always false
--------------------------+-----------------------------
 Reporter:  programmin    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  6.9.4
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Since https://github.com/WordPress/wordpress-
 develop/commit/450524a5a7a0708875f82ee5e75bb90c04049dbe, (WordPress 6.9?)
 there is no way to put in references to negative id post. This was used on
 numerous sites to show posts in the usual way on frontend and queries,
 without having to create actual posts in the WP database (queries to other
 systems for example.)

 Since WP_Post is a final class, there doesn't seem to be a way to patch
 this to not return false out of WP_Post::get_instance(). And there isn't a
 way to set transient external data on a search or result page with

 wp_cache_set($nonPostId, new WP_Post($post), 'posts');

 as in every version of WordPress before.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65238>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 22:24:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 22:24:02 -0000
Subject: [wp-trac] [WordPress Trac] #65223: Connectors plugin install
 flow does not show filesystem credentials form when FTP is required
In-Reply-To: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
References: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
Message-ID: <066.6e30070e7107cc1f211b165786e41569@wordpress.org>

#65223: Connectors plugin install flow does not show filesystem credentials form
when FTP is required
-------------------------------------+-------------------------------------
 Reporter:  ekamran                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  7.0
Component:  AI                       |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch has-test-    |     Focuses:  javascript,
  info                               |  administration
-------------------------------------+-------------------------------------
Changes (by westonruter):

 * milestone:  Awaiting Review => 7.0


Comment:

 Related: https://github.com/WordPress/gutenberg/issues/77352

 If we can't fix this for 7.0 properly, at least we could treat a
 `FS_METHOD` of `ftpext` as being the same as `DISALLOW_FILE_MODS`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65223#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 22:26:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 22:26:39 -0000
Subject: [wp-trac] [WordPress Trac] #65223: Connectors plugin install
 flow does not show filesystem credentials form when FTP is required
In-Reply-To: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
References: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
Message-ID: <066.1f56e3adb7ef19a7a01d034c82002836@wordpress.org>

#65223: Connectors plugin install flow does not show filesystem credentials form
when FTP is required
-------------------------------------+-------------------------------------
 Reporter:  ekamran                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  7.0
Component:  AI                       |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch has-test-    |     Focuses:  javascript,
  info                               |  administration
-------------------------------------+-------------------------------------

Comment (by westonruter):

 The actual work for this would need to be done in the Gutenberg repo. For
 a recent PR touching these files, see
 https://github.com/WordPress/gutenberg/pull/77521

 See also https://github.com/WordPress/wordpress-develop/pull/11779

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65223#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 22:39:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 22:39:17 -0000
Subject: [wp-trac] [WordPress Trac] #65238: Negative post id get_post is
 always false
In-Reply-To: <054.73245a6d04753314567b8d8e00205770@wordpress.org>
References: <054.73245a6d04753314567b8d8e00205770@wordpress.org>
Message-ID: <069.1949e3ac418a0df0506de37946f270e8@wordpress.org>

#65238: Negative post id get_post is always false
--------------------------+------------------------
 Reporter:  programmin    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  6.9.4
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by westonruter):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 I think this is already being requested in #64362.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65238#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 22:44:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 22:44:52 -0000
Subject: [wp-trac] [WordPress Trac] #65159: User deletion confirmation
 page never finishes loading in Chromium-based browsers;
 confirm button missing when it does load (works in Firefox)
In-Reply-To: <052.6d9af540221c58c5d7f4b9562d2ce240@wordpress.org>
References: <052.6d9af540221c58c5d7f4b9562d2ce240@wordpress.org>
Message-ID: <067.c293b10fe6929c43255944285aec234d@wordpress.org>

#65159: User deletion confirmation page never finishes loading in Chromium-based
browsers; confirm button missing when it does load (works in Firefox)
-------------------------------------------+-------------------------
 Reporter:  sirlefou                       |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  closed
 Priority:  normal                         |   Milestone:
Component:  Users                          |     Version:  6.9.4
 Severity:  normal                         |  Resolution:  worksforme
 Keywords:  has-test-info has-screenshots  |     Focuses:
-------------------------------------------+-------------------------
Changes (by westonruter):

 * status:  new => closed
 * resolution:   => worksforme
 * milestone:  Awaiting Review =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65159#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 22:55:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 22:55:00 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.c98efb1f950892c9917f77beefba366b@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by ryelle):

 Hi folks, I've been quiet lately but saw the discussion in #core today -
 I'm happy to help out with commits (whether CDN or the About page PR). I
 saw the PR will be updated, I'll be around for another couple hours today,
 and can check in in the morning US-time before the RC (though, probably
 not that much earlier).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 23:03:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 23:03:42 -0000
Subject: [wp-trac] [WordPress Trac] #64260: Default filter
 `doing_it_wrong_trigger_error` for REST request cause no notice at all.
In-Reply-To: <049.133812aede8422193f5b7ef313adb64d@wordpress.org>
References: <049.133812aede8422193f5b7ef313adb64d@wordpress.org>
Message-ID: <064.d605791f3bd5110e6835e4d3a6661dd1@wordpress.org>

#64260: Default filter `doing_it_wrong_trigger_error` for REST request cause no
notice at all.
--------------------------+-----------------------
 Reporter:  okvee         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.1
Component:  REST API      |     Version:  4.4
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  rest-api
--------------------------+-----------------------

Comment (by ioclaudio):

 Hi all,
 PR #10537 has been updated to address all review feedback (moved logging
 into rest_handle_doing_it_wrong(), added PHP Notice: prefix, included
 caller location via debug_backtrace()).
 https://github.com/WordPress/wordpress-develop/pull/10537

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64260#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed May 13 23:29:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 13 May 2026 23:29:24 -0000
Subject: [wp-trac] [WordPress Trac] #65163: Force URLs/URIs of Posts and
 Feeds to Redirect (301) to All Lowercase
In-Reply-To: <055.90b8fe4d2faca78d7632413df74e3cb8@wordpress.org>
References: <055.90b8fe4d2faca78d7632413df74e3cb8@wordpress.org>
Message-ID: <070.ea0568141c0456b569c5cedad4ead3db@wordpress.org>

#65163: Force URLs/URIs of Posts and Feeds to Redirect (301) to All Lowercase
--------------------------+------------------------------
 Reporter:  chiarella86   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Canonical     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by westonruter):

 * version:  6.9.4 =>
 * component:  General => Canonical


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65163#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 02:09:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 02:09:48 -0000
Subject: [wp-trac] [WordPress Trac] #64835: Parent menu item is still
 rendered as dropdown when all submenu items are hidden
In-Reply-To: <053.b4fb2430436a11c6bec641ae71f415cc@wordpress.org>
References: <053.b4fb2430436a11c6bec641ae71f415cc@wordpress.org>
Message-ID: <068.cd8af3db28601f640a3eb38082d19366@wordpress.org>

#64835: Parent menu item is still rendered as dropdown when all submenu items are
hidden
--------------------------+--------------------------------
 Reporter:  benniledl     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:  reported-upstream
 Keywords:                |     Focuses:
--------------------------+--------------------------------
Changes (by talldanwp):

 * status:  new => closed
 * resolution:   => reported-upstream
 * milestone:  Awaiting Review =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64835#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:06:50 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:06:50 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.2d92f53ce25fbdcb682c96a1f31512c6@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:  wildworks
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch dev-        |     Focuses:  ui,
  feedback                                       |  administration
-------------------------------------------------+-------------------------

Comment (by manhar):

 Tested the fix from [62357] on WordPress 7.0 RC3. The Delete link aligns
 correctly with the Update button after applying the patch. The flexbox
 approach is clean and low-risk. +1 for backporting to the 7.0 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:13:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:13:39 -0000
Subject: [wp-trac] [WordPress Trac] #65239: Add support for style states on
 block instances
Message-ID: <057.956830a256fc88ed2cad50ec44c3c0a9@wordpress.org>

#65239: Add support for style states on block instances
---------------------------+-----------------------------
 Reporter:  isabel_brison  |      Owner:  (none)
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:  7.1
Component:  Editor         |    Version:  trunk
 Severity:  normal         |   Keywords:  gutenberg-merge
  Focuses:                 |
---------------------------+-----------------------------
 https://github.com/WordPress/gutenberg/pull/76491 adds a new "states"
 block support, intended to allow styling pseudo states, custom block
 states such as "current menu item" and specific viewport sizes. This needs
 adding to core.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65239>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:24:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:24:31 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.07547dbb3ec5a381c0797108b3848f81@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
--------------------------------------+--------------------------
 Reporter:  jonsurrell                |       Owner:  westonruter
     Type:  defect (bug)              |      Status:  accepted
 Priority:  high                      |   Milestone:  7.0
Component:  Script Loader             |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  javascript
--------------------------------------+--------------------------

Comment (by westonruter):

 The latest state of the [https://github.com/WordPress/wordpress-
 develop/pull/11788 PR] is:

 1. A warning is issued when using `module_dependencies` without
 `in_footer` or `strategy=defer`.
 2. The `module_dependencies` arg is removed from the `codemirror` entirely
 in favor of passing the full module URL via the “jshint” config. This is
 because `codemirror` is printed in the `head`, which violates the proposed
 constraint.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:27:43 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:27:43 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.de2896193dc0626997d24f8bc9c3bd9d@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch                   |  administration
-------------------------------------+-------------------------------------

Comment (by audrasjb):

 Hello, I think it's a bit too late for this to be fixed in 7.0, as we
 don't have a solid and long term solution for now.
 What I suggest is to move this ticket to 7.0.1 and to post a heads up in
 the #polyglots Slack channel. For example, on our side, we could update
 the fr_FR translation strings to remove "Now" (which translates
 "Maintenant") from our translation strings and just keep "Update",
 "Install", etc., as the interface is not designed to accept any text
 length.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:29:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:29:13 -0000
Subject: [wp-trac] [WordPress Trac] #65151: Dashboard Widgets not
 draggable
In-Reply-To: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
References: <053.4ebfa4149ba2f1d9f36f7cdbdf8c4670@wordpress.org>
Message-ID: <068.95367bb55c6c8b0fff30e71ace220a81@wordpress.org>

#65151: Dashboard Widgets not draggable
------------------------------------------+-----------------------
 Reporter:  Presskopp                     |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  reopened
 Priority:  normal                        |   Milestone:  7.1
Component:  Administration                |     Version:  trunk
 Severity:  normal                        |  Resolution:
 Keywords:  admin-reskin has-screenshots  |     Focuses:  ui, css
------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  admin-reskin has-screenshots 2nd-opinion => admin-reskin has-
     screenshots
 * milestone:  7.0 => 7.1


Comment:

 After testing on 6.9, I concur with @jorbin: this was also an issue
 previously. Let's move it to 7.1 as it is not a critical issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65151#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:31:47 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:31:47 -0000
Subject: [wp-trac] [WordPress Trac] #65032: View transition admin bar
 quirks
In-Reply-To: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
References: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
Message-ID: <067.03ab198a1b94f4d1fb9c4ce334002f35@wordpress.org>

#65032: View transition admin bar quirks
----------------------------+------------------------
 Reporter:  zieladam        |       Owner:  audrasjb
     Type:  defect (bug)    |      Status:  reviewing
 Priority:  normal          |   Milestone:  7.0
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  ui
----------------------------+------------------------

Comment (by audrasjb):

 @nikunj8866 I don't understand. In these screencasts, it looks like you
 compare 6.9 to 7.0 with this patch. Of course the transition is more fluid
 with the patch.

 My point is that when you compare 7.0 without and with this patch, I don't
 see any difference.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65032#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:33:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:33:13 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.d622b4326469a422fa66183a8afa92c3@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch                   |  administration
-------------------------------------+-------------------------------------

Comment (by wildworks):

 > Allowing the `.button` link text to wrap to another line seems to be the
 safest //temporary// change.

 This feels very unnatural to me. The space between the wrapped text is too
 large because the current button is [https://github.com/WordPress
 /wordpress-develop/blob/20b5d10910b0d598b99313bc27f16a52cfb8f476/src/wp-
 includes/css/buttons.css#L50 using a very large value for line-height to
 express its height], in addition to `min-height`. In other words, the
 current button is not designed to have its text wrap.

 > What I suggest is to move this ticket to 7.0.1 and to post a heads up in
 the #polyglots Slack channel.

 I agree with this

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:35:36 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:35:36 -0000
Subject: [wp-trac] [WordPress Trac] #65174: Add unit tests for
 update_recently_edited()
In-Reply-To: <051.77812eccd422fa18a7117a567cbfa172@wordpress.org>
References: <051.77812eccd422fa18a7117a567cbfa172@wordpress.org>
Message-ID: <066.e67b2a388e3ea7bc15b90d53525c7b98@wordpress.org>

#65174: Add unit tests for update_recently_edited()
--------------------------------------+------------------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+------------------------------

Comment (by westonruter):

 @pbearne I think it would be preferable to instead open these PRs as part
 of the overall #64894 ticket. This will reduce the amount of work for you.
 You wouldn't have to open any of these tickets: #65170, #65171, #65172,
 #65173, #65174, #65175, #65176.

 @desrosj Is this a blessed use of that catchall ticket?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65174#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:45:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:45:32 -0000
Subject: [wp-trac] [WordPress Trac] #65141: Fix alignment for sortable
 metabox on post and page edit screen with classic editor
In-Reply-To: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
References: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
Message-ID: <071.cb210a25d901208285809920740c234c@wordpress.org>

#65141: Fix alignment for sortable metabox on post and page edit screen with
classic editor
-------------------------------------------+-----------------------------
 Reporter:  umesh.nevase                   |       Owner:  SergeyBiryukov
     Type:  defect (bug)                   |      Status:  reopened
 Priority:  normal                         |   Milestone:  7.0
Component:  Editor                         |     Version:  trunk
 Severity:  normal                         |  Resolution:
 Keywords:  admin-reskin has-patch commit  |     Focuses:  ui, css
-------------------------------------------+-----------------------------
Changes (by audrasjb):

 * keywords:  admin-reskin changes-requested has-patch => admin-reskin has-
     patch commit


Comment:

 I think we can go with PR11689.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65141#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:46:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:46:14 -0000
Subject: [wp-trac] [WordPress Trac] #65220: Toolbar: Show site title
 always even on mobile viewport, by moving shortcut menus under site menu
In-Reply-To: <050.8131bf27548d72928bdacaf59e24bfec@wordpress.org>
References: <050.8131bf27548d72928bdacaf59e24bfec@wordpress.org>
Message-ID: <065.d1b15040699166539709ae872e430e8d@wordpress.org>

#65220: Toolbar: Show site title always even on mobile viewport, by moving shortcut
menus under site menu
--------------------------------------+------------------------------
 Reporter:  fushar                    |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Toolbar                   |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  ui, css
--------------------------------------+------------------------------

Comment (by westonruter):

 Replying to [ticket:65220 fushar]:
 > ==== Problem
 >
 > On wp-admin pages in mobile resolution (<= 782px), when we have many
 sites (e.g. on a multi-site network), it's not easy to quickly identify
 which site we're currently working on, because the site title is only
 displayed in desktop viewport.

 Isn't this what the browser's URL bar is for?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65220#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 05:47:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 05:47:30 -0000
Subject: [wp-trac] [WordPress Trac] #64986: preview needs gettext
In-Reply-To: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
References: <052.86455e444a3819f06c00aef779dc6226@wordpress.org>
Message-ID: <067.91043679762eb0b37bde75b1b55deb03@wordpress.org>

#64986: preview needs gettext
--------------------------+----------------------------
 Reporter:  timse201      |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:  7.0.1
Component:  I18N          |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  accessibility
--------------------------+----------------------------
Changes (by audrasjb):

 * keywords:  good-first-bug has-patch fixed-major i18n-change dev-reviewed
     => needs-patch
 * milestone:  7.0 => 7.0.1


Comment:

 We're a bit too close from RC4.
 Let's delay this change to 7.0.1, unless a patch is provided in the next
 few hours we have before RC4. In that case, feel free to replace it to
 milestone 7.0 and we should be able to commit it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64986#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 06:11:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 06:11:06 -0000
Subject: [wp-trac] [WordPress Trac] #64999: Admin reskin: Form elements
 are not standardized in the mobile viewport.
In-Reply-To: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
References: <053.6afa9d79ed563c578a97c68f2ee8cfe3@wordpress.org>
Message-ID: <068.d379530d66a43dffb9169cb89b0940dd@wordpress.org>

#64999: Admin reskin: Form elements are not standardized in the mobile viewport.
-------------------------------------------------+---------------------
 Reporter:  wildworks                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  admin-reskin has-patch dev-reviewed  |     Focuses:
-------------------------------------------------+---------------------

Comment (by wildworks):

 The issue we are trying to resolve with this ticket is not critical. It
 does not prevent the functionality of the mobile layout and simply
 corrects the height of an interactive element. It can likely be postponed
 to 7.0.1 without any issues.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64999#comment:31>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 06:27:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 06:27:19 -0000
Subject: [wp-trac] [WordPress Trac] #65223: Connectors plugin install
 flow does not show filesystem credentials form when FTP is required
In-Reply-To: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
References: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
Message-ID: <066.46e15ff5ace6884d8b7678117e3bada2@wordpress.org>

#65223: Connectors plugin install flow does not show filesystem credentials form
when FTP is required
-------------------------------------+-------------------------------------
 Reporter:  ekamran                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  7.0
Component:  AI                       |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch has-test-    |     Focuses:  javascript,
  info                               |  administration
-------------------------------------+-------------------------------------

Comment (by manhar):

 Confirmed the bug on WordPress 7.0-RC3. No patch exists yet — I'm looking
 into the Connectors install flow in Gutenberg. The relevant files appear
 to be touched in gutenberg/pull/77521. Will follow up with a patch if
 feasible.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65223#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 07:33:45 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 07:33:45 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.9a3b267db1c23673f0638a43d3db2d2f@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by fcoveram):

 From the screenshot attached above, the content looks good.

 Just noting that header shows the 6.9 image and heading says WordPress
 7.1. You likely know that, but sharing it anyways.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:51>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 08:02:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 08:02:51 -0000
Subject: [wp-trac] [WordPress Trac] #65153: Identify selected buttons
 (.active in button groups) in Windows High Contrast Mode
In-Reply-To: <055.31a39574f4a6e19d1248494470c837e6@wordpress.org>
References: <055.31a39574f4a6e19d1248494470c837e6@wordpress.org>
Message-ID: <070.c88e50aa750596881b309e00b7710d6b@wordpress.org>

#65153: Identify selected buttons (.active in button groups) in Windows High
Contrast Mode
----------------------------+---------------------------------
 Reporter:  sabernhardt     |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  accessibility, css
----------------------------+---------------------------------

Comment (by manhar):

 Agreed with @wildworks — the third approach feels the most natural. Tested
 it in Windows High Contrast Mode and the active button state is clearly
 distinguishable without conflicting with the focus outline. The teal
 border works well for indicating the selected state.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65153#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 08:11:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 08:11:49 -0000
Subject: [wp-trac] [WordPress Trac] #65129: Improve maintainability of
 DOCTYPE quirks mode detection in `WP_HTML_Doctype_Info` class
In-Reply-To: <062.4222a143c45d82e1e02b722fdcd453bf@wordpress.org>
References: <062.4222a143c45d82e1e02b722fdcd453bf@wordpress.org>
Message-ID: <077.8027c1c2f901b0e0f4f1e5450f15f54b@wordpress.org>

#65129: Improve maintainability of DOCTYPE quirks mode detection in
`WP_HTML_Doctype_Info` class
-------------------------------------------+-------------------------------
 Reporter:  baikare.sandeep007             |       Owner:  (none)
     Type:  enhancement                    |      Status:  closed
 Priority:  normal                         |   Milestone:
Component:  HTML API                       |     Version:  6.7
 Severity:  normal                         |  Resolution:  invalid
 Keywords:  has-patch needs-testing close  |     Focuses:  coding-standards
-------------------------------------------+-------------------------------
Changes (by jonsurrell):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65129#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 08:20:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 08:20:52 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.420c90b824701a7dd4f4e17678b151a6@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by audrasjb):

 Replying to [comment:51 fcoveram]:
 > Just noting that header shows the 6.9 image and heading says WordPress
 7.1. You likely know that, but sharing it anyways.

 Yes it's because the patch was done against trunk, which shows images from
 6.9 and a dynamic WordPress Version number (so 7.1 as trunk is 7.1 alpha).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 08:56:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 08:56:08 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.28225e24ce96cab209e6ae5f8ea36347@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
--------------------------------------+--------------------------
 Reporter:  jonsurrell                |       Owner:  westonruter
     Type:  defect (bug)              |      Status:  accepted
 Priority:  high                      |   Milestone:  7.0
Component:  Script Loader             |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  javascript
--------------------------------------+--------------------------

Comment (by jonsurrell):

 For 7.0, I agree with the `_doing_it_wrong()` approach. Its impact is
 minimal and should help to address the root of the problem. The downside
 is that it's possible to use module dependencies correctly without loading
 in the footer, to the warnings may produce noise in valid cases. At this
 point in the release cycle that tradeoff seems acceptable.

 For a future release, I'd like to see an improved solution that leverages
 multiple importmaps that can be printed as necessary.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 09:11:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 09:11:32 -0000
Subject: [wp-trac] [WordPress Trac] #65232: Abilities API: Add a fast
 site health summary to `core/get-environment-info`
In-Reply-To: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
References: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
Message-ID: <065.4d1605a95c67d91e3986ad2249b46178@wordpress.org>

#65232: Abilities API: Add a fast site health summary to `core/get-environment-
info`
---------------------------+-----------------------
 Reporter:  gziolo         |       Owner:  gziolo
     Type:  enhancement    |      Status:  assigned
 Priority:  normal         |   Milestone:  7.1
Component:  Abilities API  |     Version:  6.9
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+-----------------------

Comment (by karunyachavan84):

 While reviewing this, I noticed that the existing `health-check-site-
 status-result` transient currently only stores aggregate counts (`good`,
 `recommended`, `critical`) and does not persist the underlying issue
 details needed for the proposed `site_health.issues` response (`label`,
 `severity`, `recommendation`).
 Since the proposal also explicitly requires that `site_health` be
 populated entirely from cached data and never trigger synchronous Site
 Health tests, it seems like we would first need to expand the Site Health
 caching mechanism itself (likely during the scheduled health check cron
 run and related persistence flows) to store normalized actionable issue
 summaries alongside the counts.
 Just wanted to confirm whether that scope expansion is expected here, or
 if there’s another existing cached source I may be missing.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65232#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 09:26:00 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 09:26:00 -0000
Subject: [wp-trac] [WordPress Trac] #65129: Improve maintainability of
 DOCTYPE quirks mode detection in `WP_HTML_Doctype_Info` class
In-Reply-To: <062.4222a143c45d82e1e02b722fdcd453bf@wordpress.org>
References: <062.4222a143c45d82e1e02b722fdcd453bf@wordpress.org>
Message-ID: <077.7c89f5067669ce635a6b5428c2962441@wordpress.org>

#65129: Improve maintainability of DOCTYPE quirks mode detection in
`WP_HTML_Doctype_Info` class
-------------------------------------------+-------------------------------
 Reporter:  baikare.sandeep007             |       Owner:  (none)
     Type:  enhancement                    |      Status:  closed
 Priority:  normal                         |   Milestone:
Component:  HTML API                       |     Version:  6.7
 Severity:  normal                         |  Resolution:  invalid
 Keywords:  has-patch needs-testing close  |     Focuses:  coding-standards
-------------------------------------------+-------------------------------

Comment (by jonsurrell):

 @baikaresandeep007 If you'd like to get involved with devloping the HTML
 API, ticket #64504 may be a good starting point.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65129#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 09:33:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 09:33:46 -0000
Subject: [wp-trac] [WordPress Trac] #65120: Add
 `wp_elements_block_supports_class_name` filter to
 `wp_get_elements_class_name()`
In-Reply-To: <062.c5c4315f56dd742dd7ff410a88a4ea8d@wordpress.org>
References: <062.c5c4315f56dd742dd7ff410a88a4ea8d@wordpress.org>
Message-ID: <077.2dd34859b49e588a7e8ef63545815254@wordpress.org>

#65120: Add `wp_elements_block_supports_class_name` filter to
`wp_get_elements_class_name()`
-------------------------------------+-------------------------------------
 Reporter:  baikare.sandeep007       |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Editor                   |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css, performance,
  has-test-info dev-feedback         |  coding-standards
-------------------------------------+-------------------------------------
Changes (by sanayasir):

 * keywords:  has-patch needs-testing has-test-info 2nd-opinion => has-patch
     needs-testing has-test-info dev-feedback
 * focuses:  template, performance, coding-standards => css, performance,
     coding-standards


Comment:

 Tested the patch by applying the proposed filter:

 ```php
 add_filter(
     'wp_elements_block_supports_class_name',
     function( $class_name, $block ) {
         return 'my-test-class';
     },
     10,
     2
 );
 ```

 Expected result:
 The generated `wp-elements-*` class should be replaced with the custom
 class name (`my-test-class`).

 Actual result:
 After applying the patch and clearing caches, the updated CSS class was
 not generated in either the editor DOM or the frontend output. The
 original generated class behavior remained unchanged.

 Additional notes:

 * Tested multiple times with different callback return values.
 * No custom class name appeared in the rendered markup.
 * It appears that the filter may not be executed in the current rendering
 path, or the generated class is not being applied to the final output.
 * Further verification may be needed to confirm where
 `wp_get_elements_class_name()` is triggered and whether it applies across
 all supported block rendering contexts.

 Areas that may need additional investigation:

 * frontend rendering flow
 * supported block types
 * block supports integration
 * editor vs frontend rendering behavior
 * filter execution path

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65120#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 09:44:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 09:44:31 -0000
Subject: [wp-trac] [WordPress Trac] #65220: Toolbar: Show site title
 always even on mobile viewport, by moving shortcut menus under site menu
In-Reply-To: <050.8131bf27548d72928bdacaf59e24bfec@wordpress.org>
References: <050.8131bf27548d72928bdacaf59e24bfec@wordpress.org>
Message-ID: <065.d9d8500860eb320e41c314e59f6c3b02@wordpress.org>

#65220: Toolbar: Show site title always even on mobile viewport, by moving shortcut
menus under site menu
--------------------------------------+------------------------------
 Reporter:  fushar                    |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Toolbar                   |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  ui, css
--------------------------------------+------------------------------

Comment (by Joen):

 Appreciate the attention to the adminbar. It's gone unloved for quite a
 while, it's good to see some energy applied to it.

 For this issue in particular, I like the general direction it's heading.
 It feels, paired with the other work you've done, like it's systematising
 teh adminbar a bit; logo, site title, contextual actions, command palette,
 plugin actions, account/profile.

 In this case, it does feel valid to me to hide many of the contextual
 actions on mobile to fit the site title. This is also in response to
 @westonruter who makes a good point about the browser URL bar. Some
 feedback I've seen in various support sessions over the years, were when
 power-users had multiple WordPress installs and tabbed between them, then
 accidentally uploaded private information to the wrong WordPress site
 because there wasn't clear enough visual distinction between the tabs. It
 is for that reason I appreciate some attention to this.

 However there are a couple of details to get right, which feel not quite
 right yet. Whether they need to happen as part of this issue or followups,
 I'll defer to more veteran core contributors. But coming to mind:

 1. **Showing the site title helps, but showing a site logo would help even
 more**. The "house" dashicon tells us nothing, and there's no reason that
 couldn't be the site logo instead. This would also be helpful in cases
 where we simply have to elide the site title in order to fit it.
 2. As a heavy WordPress user myself, I find myself not missing the plus
 button, or the comment button on mobile: I'd want to enter the dashboard
 proper in order to engage with that. But on the frontend, I might miss the
 Edit button. There may be a way, though spacings overall (not in this PR)
 to fit not only the command palette icon, but the contextual edit button,
 while still having both site logo and site title. This is not strongly
 felt, but it's the only button I might miss here. Putting it inside the
 submenus might also be fine in practice, so it can be a fine place to
 start.
 3. I'm missing the WordPress logo as a fix-point. This is almost certainly
 something to look at separately, but my mental appraoch to the adminbar is
 it's WordPress' answer to the Apple app-bar. Top of MacOS shows you the
 Apple logo, then contextual actions, a spacer, then the equivalent of
 plugins actions. Honestly the WordPress adminbar could/should be the same,
 and for that reason I'd not only want to retain the logo, but actually
 move it to the left of the burger menu. It's WordPress, it's always there,
 but the burger menu then collapses the contextual items, so hierarchically
 the menu doesn't shift around even on mobile.

 What do you think?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65220#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 09:59:23 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 09:59:23 -0000
Subject: [wp-trac] [WordPress Trac] #65220: Toolbar: Show site title
 always even on mobile viewport, by moving shortcut menus under site menu
In-Reply-To: <050.8131bf27548d72928bdacaf59e24bfec@wordpress.org>
References: <050.8131bf27548d72928bdacaf59e24bfec@wordpress.org>
Message-ID: <065.5726d56bd1c60bcc3f184b8d34d8e898@wordpress.org>

#65220: Toolbar: Show site title always even on mobile viewport, by moving shortcut
menus under site menu
--------------------------------------+------------------------------
 Reporter:  fushar                    |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Toolbar                   |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  ui, css
--------------------------------------+------------------------------

Comment (by fushar):

 > Showing the site title helps, but showing a site logo would help even
 more. The "house" dashicon tells us nothing, and there's no reason that
 couldn't be the site logo instead. This would also be helpful in cases
 where we simply have to elide the site title in order to fit it.

 Yep! We have a separate issue for this here:
 https://core.trac.wordpress.org/ticket/65088

 > Honestly the WordPress adminbar could/should be the same, and for that
 reason I'd not only want to retain the logo, but actually move it to the
 left of the burger menu

 I'm not sure I agree with this. On mobile, the hamburger menu
 opens/collapses the left sidebar. Wouldn't it be confusing if it's not the
 leftmost item that triggers the behavior?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65220#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 11:09:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 11:09:05 -0000
Subject: [wp-trac] [WordPress Trac] #65120: Add
 `wp_elements_block_supports_class_name` filter to
 `wp_get_elements_class_name()`
In-Reply-To: <062.c5c4315f56dd742dd7ff410a88a4ea8d@wordpress.org>
References: <062.c5c4315f56dd742dd7ff410a88a4ea8d@wordpress.org>
Message-ID: <077.2998be2b7b9e20f766bff5a3aa6db7cb@wordpress.org>

#65120: Add `wp_elements_block_supports_class_name` filter to
`wp_get_elements_class_name()`
-------------------------------------+-------------------------------------
 Reporter:  baikare.sandeep007       |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Editor                   |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css, performance,
  has-test-info dev-feedback         |  coding-standards
-------------------------------------+-------------------------------------
Changes (by sanayasir):

 * Attachment "Wp-elements.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65120>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 12:13:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 12:13:48 -0000
Subject: [wp-trac] [WordPress Trac] #65224: Add support for testing
 unmerged changes from Gutenberg
In-Reply-To: <051.67117d30612d0aa1b44471e443f905b1@wordpress.org>
References: <051.67117d30612d0aa1b44471e443f905b1@wordpress.org>
Message-ID: <066.9ca9cf6122236336d8625419f227e0d7@wordpress.org>

#65224: Add support for testing unmerged changes from Gutenberg
------------------------------+---------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  7.1
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+---------------------

Comment (by manhar):

 Tested on: Ubuntu 24.04, Node v20.19.5, npm 10.8.2
 - Set gutenberg.sha to pr-78211 and ran npm run gutenberg:download
 - Mutable tag resolved correctly, downloaded and built without any errors.
 blocks generated, all files copied successfully.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65224#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 12:35:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 12:35:49 -0000
Subject: [wp-trac] [WordPress Trac] #65240: REST API:
 WP_REST_Plugins_Controller::create_item() fatals when plugins_api response
 lacks language_packs property
Message-ID: <056.90c9a6140d80d74227fef02e3e83c419@wordpress.org>

#65240: REST API: WP_REST_Plugins_Controller::create_item() fatals when plugins_api
response lacks language_packs property
-----------------------------------------+-----------------------------
 Reporter:  flipcreative                 |      Owner:  (none)
     Type:  defect (bug)                 |     Status:  new
 Priority:  normal                       |  Milestone:  Awaiting Review
Component:  REST API                     |    Version:  6.9.4
 Severity:  normal                       |   Keywords:  needs-patch
  Focuses:  rest-api, php-compatibility  |
-----------------------------------------+-----------------------------
 When installing a plugin via the REST endpoint `POST /wp/v2/plugins`,
 `WP_REST_Plugins_Controller::create_item()` calls `plugins_api(
 'plugin_information', ... )` requesting `language_packs => true`, then
 immediately runs `array_map()` over `$api->language_packs` without
 checking whether the property is set or is an array.

 If the API response does not include a populated `language_packs` key —
 which can happen when the plugin has no translation packs on
 translate.wordpress.org for any installed locale, when wp.org returns a
 partial response, or when the result is filtered by a third party —
 accessing `$api->language_packs` produces a PHP Warning, then immediately
 triggers a Fatal TypeError on the array_map call. Both originate from the
 same request.

 The install itself has already succeeded by the time the fatal fires —
 `$upgrader->install( $api->download_link )` runs and completes before the
 language pack section is reached, so the plugin files are on disk. The
 REST response returns a 500 even though the install succeeded. This causes
 spurious error UI in any caller that uses this endpoint and produces noisy
 logs in production. We are seeing this consistently in the wild from at
 least one widely deployed third-party caller (Elementor One's app
 installer) and the volume is enough that one major managed WordPress host
 has flagged the resulting 500 spike to customers.

 **File:** `wp-includes/rest-api/endpoints/class-wp-rest-plugins-
 controller.php`

 **Offending code (around lines 380–385):**

 ```php
 $language_packs = array_map(
     static function ( $item ) {
         return (object) $item;
     },
     $api->language_packs
 );
 ```

 **Error output:**

 ```
 PHP Warning: Undefined property: stdClass::$language_packs in
   /wp-includes/rest-api/endpoints/class-wp-rest-plugins-controller.php on
 line 387

 PHP Fatal error: Uncaught TypeError: array_map(): Argument #2 ($array)
 must be of type
   array, null given in /wp-includes/rest-api/endpoints/class-wp-rest-
 plugins-controller.php:383
 ```

 **Steps to reproduce:**

 1. Send an authenticated `POST` request to `/wp-json/wp/v2/plugins` with a
 `slug` for a plugin whose `plugins_api` response does not contain a
 populated `language_packs` array.
 2. Observe that the plugin is correctly installed to `wp-content/plugins`.
 3. Observe that the REST request returns HTTP 500.
 4. Observe the warning and fatal in the PHP error log.

 **Suggested fix:**

 Guard the array_map call:

 ```php
 $language_packs = array();
 if ( ! empty( $api->language_packs ) && is_array( $api->language_packs ) )
 {
     $language_packs = array_map(
         static function ( $item ) {
             return (object) $item;
         },
         $api->language_packs
     );
 }
 ```

 Alternatively, normalize the `plugins_api` response so that
 `language_packs` is always present as an array (even empty) when requested
 via the `fields` parameter.

 **Environment:**

 - WordPress 6.9.4
 - PHP 8.x (the strict TypeError behavior requires PHP 8.0+)
 - Reproduced on WP Engine hosting

 **Related tickets (same defensive-coding pattern):**

 - #44582 — Undefined property stdClass::$plugin
 - #59413 — Undefined property stdClass::$plugin in class-wp-automatic-
 updater.php
 - #46382 — Undefined property stdClass::$current in class-walker-nav-
 menu.php

 This is part of a broader pattern of WP core code paths that trust
 stdClass properties on API responses without guards. The fix here is one-
 line and low-risk.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65240>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 12:45:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 12:45:15 -0000
Subject: [wp-trac] [WordPress Trac] #65233: Taxonomy: Delete button is
 misaligned
In-Reply-To: <053.99059f8a98e642b44458327936606426@wordpress.org>
References: <053.99059f8a98e642b44458327936606426@wordpress.org>
Message-ID: <068.621841cd97123b99b3e833bc33bd924a@wordpress.org>

#65233: Taxonomy: Delete button is misaligned
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:  wildworks
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch dev-        |     Focuses:  ui,
  feedback                                       |  administration
-------------------------------------------------+-------------------------

Comment (by gaurangsondagar):

 **Patch Testing Report:**

 **Patch Tested:** https://github.com/WordPress/wordpress-
 develop/pull/11823

 **Environement:**
 - PHP: 8.2.29
 - WordPress: 7.0-RC3-62350
 - Web server: Apache
 - Database: MySQL
 - Browser: Chrome
 - OS: Ubuntu 22.04.5 LTS
 - Theme: Twenty Twenty-Five

 Steps I Followed:
 - Go to > Posts > Tags
 - Edit the tag
 - Check the alignment of the delete button.

 **Result:**
 - After applying the patch, the alignment issue has been fixed and is now
 working perfectly.

 Please review the screenshots below for reference.:

 Before Applying the patch:
 - https://snipboard.io/BpVixN.jpg
 - https://snipboard.io/GRJyot.jpg

 After applying the patch:
 - https://snipboard.io/yaHmNi.jpg
 - https://snipboard.io/JfAZRF.jpg

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65233#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 12:53:07 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 12:53:07 -0000
Subject: [wp-trac] [WordPress Trac] #64595: Update Gutenberg ref in
 package.json
In-Reply-To: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
References: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
Message-ID: <067.15b14f793c0cd237148de61257edf4ad@wordpress.org>

#64595: Update Gutenberg ref in package.json
----------------------------+---------------------
 Reporter:  ellatrix        |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  7.0
Component:  General         |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------

Comment (by ellatrix):

 In [changeset:"62360" 62360]:
 {{{
 #!CommitTicketReference repository="" revision="62360"
 Editor: Bump pinned hash for the Gutenberg repository.
 This updates the pinned hash from the `gutenberg` from
 `c15cef1d6b07f666df28dac0383bafb0edfe0914 ` to
 `3a4e8d1418d25da83b70158bcaabf65580690b6b`.

 The following changes are included:

 - [WP.7.0] Admin UI: Backport accessibility fixes
 (https://github.com/WordPress/gutenberg/pull/77617,
 https://github.com/WordPress/gutenberg/pull/78001)
 (https://github.com/WordPress/gutenberg/pull/78002)
 - Fix: Shortcode block does not render in Navigation Overlay
 (https://github.com/WordPress/gutenberg/pull/77511)
 - feat: Enhance Connectors page on read-only file system
 (https://github.com/WordPress/gutenberg/pull/77521)
 - Connectors: Avoid using centered text
 (https://github.com/WordPress/gutenberg/pull/78125)
 - Revisions: Add tooltip to diff marker buttons
 (https://github.com/WordPress/gutenberg/pull/77690)
 - Add backport for WP_ALLOW_COLLABORATION
 (https://github.com/WordPress/gutenberg/pull/78160)
 - Add aria-label to Revisions button in Post Summary sidebar
 (https://github.com/WordPress/gutenberg/pull/78140)
 - Revisions diff markers: enforce 24×24px minimum target size (WCAG 2.5.8)
 (https://github.com/WordPress/gutenberg/pull/77671)
 - Connectors: Replace @wordpress/ui Link and Notice usage
 (https://github.com/WordPress/gutenberg/pull/78117)
 - Connectors: Increase right padding of callout for mobile layout
 (https://github.com/WordPress/gutenberg/pull/78126)
 - isFulfilled: don't change resolution state, call in resolveSelect
 (https://github.com/WordPress/gutenberg/pull/78201)
 - Connectors: Restyle AI plugin callout with pastel background and beaker
 decoration (https://github.com/WordPress/gutenberg/pull/78243)
 - Block supports: Optimize custom CSS class rendering and parsing
 (https://github.com/WordPress/gutenberg/pull/78217)
 - Block Inspector: Hide Styles tab in preview mode
 (https://github.com/WordPress/gutenberg/pull/78230)
 - Navigation Link: Preserve custom labels during link updates
 (https://github.com/WordPress/gutenberg/pull/77186)
 - Editor: Fix Visual Revisions meta keys overlap
 (https://github.com/WordPress/gutenberg/pull/78156)
 - Editor: Disable Visual Revisions when classic meta boxes are present
 (https://github.com/WordPress/gutenberg/pull/78249)
 (https://github.com/WordPress/gutenberg/pull/78286)
 - Revisions: Scale diff markers width with user text-size preference
 (https://github.com/WordPress/gutenberg/pull/78273)

 A full list of changes can be found on GitHub:
 https://github.com/WordPress/gutenberg/compare/c15cef1d6b07f666df28dac0383bafb0edfe0914…3a4e8d1418d25da83b70158bcaabf65580690b6b.

 Log created with:

 git log --reverse --format="- %s"
 c15cef1d6b07f666df28dac0383bafb0edfe0914..3a4e8d1418d25da83b70158bcaabf65580690b6b
 | sed
 's|#\([0-9][0-9]*\)|https://github.com/WordPress/gutenberg/pull/\1|g;
 /github\.com\/WordPress\/gutenberg\/pull/!d' | pbcopy

 See #64595.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64595#comment:61>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 13:46:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 13:46:10 -0000
Subject: [wp-trac] [WordPress Trac] #64595: Update Gutenberg ref in
 package.json
In-Reply-To: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
References: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
Message-ID: <067.f9bae6370552b30fea860a264498e3a2@wordpress.org>

#64595: Update Gutenberg ref in package.json
-------------------------------------------------+-------------------------
 Reporter:  ellatrix                             |       Owner:  (none)
     Type:  task (blessed)                       |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch commit fixed-major dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-patch => has-patch commit fixed-major dev-reviewed


Comment:

 [62360] looks good to backport, but it looks like it was committed
 directly to the `7.0` branch. I am going to forward-merge this to `trunk`.

 There is
 [https://wordpress.slack.com/archives/C02RQBWTW/p1778765640815739?thread_ts=1778765534.658469&cid=C02RQBWTW
 some initial discussion in Slack] about the right process for this. It's
 likely that committing SHA bumps from the respective `wp/X.Y` branches
 directly to numbered branches is the right thing to do. But there are some
 nuances and edge cases that need to be discussed and documented first.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64595#comment:62>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 13:49:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 13:49:08 -0000
Subject: [wp-trac] [WordPress Trac] #64595: Update Gutenberg ref in
 package.json
In-Reply-To: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
References: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
Message-ID: <067.5a5e53e26308a374e3c794852ff89b90@wordpress.org>

#64595: Update Gutenberg ref in package.json
-------------------------------------------------+-------------------------
 Reporter:  ellatrix                             |       Owner:  (none)
     Type:  task (blessed)                       |      Status:  new
 Priority:  normal                               |   Milestone:  7.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch commit fixed-major dev-    |     Focuses:
  reviewed                                       |
-------------------------------------------------+-------------------------

Comment (by desrosj):

 In [changeset:"62361" 62361]:
 {{{
 #!CommitTicketReference repository="" revision="62361"
 Editor: Bump pinned hash for the Gutenberg repository.

 This updates the pinned hash from the `gutenberg` from
 `c15cef1d6b07f666df28dac0383bafb0edfe0914 ` to
 `3a4e8d1418d25da83b70158bcaabf65580690b6b`.

 The following changes are included:

 - [WP.7.0] Admin UI: Backport accessibility fixes
 (https://github.com/WordPress/gutenberg/pull/77617,
 https://github.com/WordPress/gutenberg/pull/78001)
 (https://github.com/WordPress/gutenberg/pull/78002)
 - Fix: Shortcode block does not render in Navigation Overlay
 (https://github.com/WordPress/gutenberg/pull/77511)
 - feat: Enhance Connectors page on read-only file system
 (https://github.com/WordPress/gutenberg/pull/77521)
 - Connectors: Avoid using centered text
 (https://github.com/WordPress/gutenberg/pull/78125)
 - Revisions: Add tooltip to diff marker buttons
 (https://github.com/WordPress/gutenberg/pull/77690)
 - Add backport for WP_ALLOW_COLLABORATION
 (https://github.com/WordPress/gutenberg/pull/78160)
 - Add aria-label to Revisions button in Post Summary sidebar
 (https://github.com/WordPress/gutenberg/pull/78140)
 - Revisions diff markers: enforce 24×24px minimum target size (WCAG 2.5.8)
 (https://github.com/WordPress/gutenberg/pull/77671)
 - Connectors: Replace @wordpress/ui Link and Notice usage
 (https://github.com/WordPress/gutenberg/pull/78117)
 - Connectors: Increase right padding of callout for mobile layout
 (https://github.com/WordPress/gutenberg/pull/78126)
 - isFulfilled: don't change resolution state, call in resolveSelect
 (https://github.com/WordPress/gutenberg/pull/78201)
 - Connectors: Restyle AI plugin callout with pastel background and beaker
 decoration (https://github.com/WordPress/gutenberg/pull/78243)
 - Block supports: Optimize custom CSS class rendering and parsing
 (https://github.com/WordPress/gutenberg/pull/78217)
 - Block Inspector: Hide Styles tab in preview mode
 (https://github.com/WordPress/gutenberg/pull/78230)
 - Navigation Link: Preserve custom labels during link updates
 (https://github.com/WordPress/gutenberg/pull/77186)
 - Editor: Fix Visual Revisions meta keys overlap
 (https://github.com/WordPress/gutenberg/pull/78156)
 - Editor: Disable Visual Revisions when classic meta boxes are present
 (https://github.com/WordPress/gutenberg/pull/78249)
 (https://github.com/WordPress/gutenberg/pull/78286)
 - Revisions: Scale diff markers width with user text-size preference
 (https://github.com/WordPress/gutenberg/pull/78273)

 A full list of changes can be found on GitHub:
 https://github.com/WordPress/gutenberg/compare/c15cef1d6b07f666df28dac0383bafb0edfe0914…3a4e8d1418d25da83b70158bcaabf65580690b6b.

 Log created with:

 `git log --reverse --format="- %s"
 c15cef1d6b07f666df28dac0383bafb0edfe0914..3a4e8d1418d25da83b70158bcaabf65580690b6b
 | sed
 's|#\([0-9][0-9]*\)|https://github.com/WordPress/gutenberg/pull/\1|g;
 /github\.com\/WordPress\/gutenberg\/pull/!d' | pbcopy`

 Reviewed by desrosj.
 Merges [62360] to `trunk`.

 See #64595.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64595#comment:63>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 13:51:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 13:51:01 -0000
Subject: [wp-trac] [WordPress Trac] #64595: Update Gutenberg ref in
 package.json
In-Reply-To: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
References: <052.77ee8574fdbbcf6ccf6ecf00bf3f7a14@wordpress.org>
Message-ID: <067.bc26623a335610577804858d299a837b@wordpress.org>

#64595: Update Gutenberg ref in package.json
----------------------------+---------------------
 Reporter:  ellatrix        |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  7.0
Component:  General         |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------
Changes (by desrosj):

 * keywords:  has-patch commit fixed-major dev-reviewed => has-patch


Comment:

 Resetting keywords for the next hash bump.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64595#comment:64>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 13:52:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 13:52:17 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.355983996ec241b5ec91b90e98172ba2@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by ryelle):

 I'll upload the images to the CDN now.

 The header images can be optimized by switching to webp, and they could be
 renamed to "about-header-*" instead of "7-0-*".

 I would also suggest using the `has-subtle-background-color` class and
 updating the `--subtle-background` variable for the "and more" section so
 that the change also applies to the same styled box on Get Involved.

 Once I get the images added, is this ready for commit? I can make these
 changes and commit, if so - I know it's close to commit freeze.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:55>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 13:52:23 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 13:52:23 -0000
Subject: [wp-trac] [WordPress Trac] #57152: Trying to access array
 offset on value of type bool (class-wp-recovery-mode-email-service.php)
In-Reply-To: <052.7055a57c2d4e8e8d49edd1fa8672fc5d@wordpress.org>
References: <052.7055a57c2d4e8e8d49edd1fa8672fc5d@wordpress.org>
Message-ID: <067.f6ffd679985e138f74498df278feb642@wordpress.org>

#57152: Trying to access array offset on value of type bool (class-wp-recovery-
mode-email-service.php)
--------------------------+------------------------
 Reporter:  Mayhem30      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Site Health   |     Version:  6.1.1
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by sabernhardt):

 * status:  new => closed
 * resolution:   => duplicate
 * component:  General => Site Health
 * milestone:  Awaiting Review =>


Comment:

 Thanks for the report!

 #62816 updated the condition to make sure `$plugin` is an array,
 preventing warnings about it being boolean (false).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57152#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 14:33:46 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 14:33:46 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.91f6bc048c77e86e1e18fdeb282ac95a@wordpress.org>

#64536: About Page - 7.0
----------------------------+-----------------------
 Reporter:  desrosj         |       Owner:  mukesh27
     Type:  task (blessed)  |      Status:  closed
 Priority:  normal          |   Milestone:  7.0
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:  fixed
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------
Changes (by ryelle):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62362" 62362]:
 {{{
 #!CommitTicketReference repository="" revision="62362"
 Help/About: Update the About page for 7.0.

 Introducing the new content for the 7.0 About page.

 Fixes #64536.
 Props mukesh27, audrasjb, jorbin, ankit-k-gupta, parinpanjari, fcoveram,
 joen, markoserb, Benjamin_Zekavica, westonruter, peterwilsoncc, JeffPaul.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:56>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 14:35:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 14:35:16 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.ec692d5aa08e55b86446d23a7d77ff0e@wordpress.org>

#64536: About Page - 7.0
------------------------------------+-----------------------
 Reporter:  desrosj                 |       Owner:  mukesh27
     Type:  task (blessed)          |      Status:  closed
 Priority:  normal                  |   Milestone:  7.0
Component:  Help/About              |     Version:
 Severity:  normal                  |  Resolution:  fixed
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+-----------------------
Changes (by ryelle):

 * keywords:  has-patch => has-patch dev-feedback


Comment:

 Reopening to backport [62362]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:57>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 14:35:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 14:35:24 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.a088e59acb33050eaa90c6f6f4525dae@wordpress.org>

#64536: About Page - 7.0
------------------------------------+-----------------------
 Reporter:  desrosj                 |       Owner:  mukesh27
     Type:  task (blessed)          |      Status:  reopened
 Priority:  normal                  |   Milestone:  7.0
Component:  Help/About              |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+-----------------------
Changes (by ryelle):

 * status:  closed => reopened
 * resolution:  fixed =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:58>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 14:47:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 14:47:49 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.40d9ce482c23b8e645918b11f7a299f6@wordpress.org>

#64536: About Page - 7.0
------------------------------------+-----------------------
 Reporter:  desrosj                 |       Owner:  mukesh27
     Type:  task (blessed)          |      Status:  reopened
 Priority:  normal                  |   Milestone:  7.0
Component:  Help/About              |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-reviewed  |     Focuses:
------------------------------------+-----------------------
Changes (by ellatrix):

 * keywords:  has-patch dev-feedback => has-patch dev-reviewed


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:59>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 14:50:19 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 14:50:19 -0000
Subject: [wp-trac] [WordPress Trac] #64536: About Page - 7.0
In-Reply-To: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
References: <051.70759fa0a8836490f78fb36a7530ec61@wordpress.org>
Message-ID: <066.c7a71396df44aa5d5171a8117a6e1357@wordpress.org>

#64536: About Page - 7.0
------------------------------------+-----------------------
 Reporter:  desrosj                 |       Owner:  mukesh27
     Type:  task (blessed)          |      Status:  closed
 Priority:  normal                  |   Milestone:  7.0
Component:  Help/About              |     Version:
 Severity:  normal                  |  Resolution:  fixed
 Keywords:  has-patch dev-reviewed  |     Focuses:
------------------------------------+-----------------------
Changes (by ellatrix):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62363" 62363]:
 {{{
 #!CommitTicketReference repository="" revision="62363"
 Help/About: Update the About page for 7.0.

 Introducing the new content for the 7.0 About page.

 Reviewed by ellatrix.
 Merges [62362] to the 7.0 branch.
 Fixes #64536.
 Props mukesh27, audrasjb, jorbin, ankit-k-gupta, parinpanjari, fcoveram,
 joen, markoserb, Benjamin_Zekavica, westonruter, peterwilsoncc, JeffPaul.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64536#comment:60>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 14:52:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 14:52:17 -0000
Subject: [wp-trac] [WordPress Trac] #65241: get_editable_roles() returns
 empty array in multisite
Message-ID: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>

#65241: get_editable_roles() returns empty array in multisite
--------------------------+-----------------------------
 Reporter:  neo2k23       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 I have no clue where to look for this issue so i am posting the question
 here.

 My website moved from the old server to the new one.  Its a multisite.

 But get_editable_roles() now returns a empty array.  No roles.

 I tried latest trunk 7.1 reverted to 6.9.4 but now roles are returned.

 If i install a plugin like "user roles" the roles are also gone.

 Even the woocommerce shop roles are gone.

 How to fix this? Any idea's how to deal with this?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65241>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 14:52:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 14:52:34 -0000
Subject: [wp-trac] [WordPress Trac] #65241: get_editable_roles() returns
 empty array in multisite
In-Reply-To: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
References: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
Message-ID: <066.e5496125c46408be99fed58ca12282e4@wordpress.org>

#65241: get_editable_roles() returns empty array in multisite
--------------------------+------------------------------
 Reporter:  neo2k23       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by neo2k23):

 * Attachment "userroles.jpg" added.

 Missing user roles

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65241>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 14:56:39 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 14:56:39 -0000
Subject: [wp-trac] [WordPress Trac] #65241: get_editable_roles() returns
 empty array in multisite
In-Reply-To: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
References: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
Message-ID: <066.be31db7d49595a7aef870a6c0cad7451@wordpress.org>

#65241: get_editable_roles() returns empty array in multisite
--------------------------+------------------------------
 Reporter:  neo2k23       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by neo2k23):

 If i goto users in a subsite the user role dropdown is also empty. If i
 create a new user it also shows no roles in the dropdown.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65241#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 14:57:04 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 14:57:04 -0000
Subject: [wp-trac] [WordPress Trac] #65241: get_editable_roles() returns
 empty array in multisite
In-Reply-To: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
References: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
Message-ID: <066.c65c95c56528485b9e7d57544c62ba18@wordpress.org>

#65241: get_editable_roles() returns empty array in multisite
--------------------------+------------------------------
 Reporter:  neo2k23       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by neo2k23):

 * Attachment "user-settings.jpg" added.

 user roles missing in user settings

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65241>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 15:16:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 15:16:15 -0000
Subject: [wp-trac] [WordPress Trac] #62835: Remove title attributes from
 author link functions
In-Reply-To: <055.11f6fedc8818f923405c82cd932147f5@wordpress.org>
References: <055.11f6fedc8818f923405c82cd932147f5@wordpress.org>
Message-ID: <070.1f7237ae65eb311455ea1c4d4e715ce3@wordpress.org>

#62835: Remove title attributes from author link functions
-------------------------------------------------+-------------------------
 Reporter:  sabernhardt                          |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Users                                |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  title-attribute has-patch has-unit-  |     Focuses:
  tests commit has-dev-note                      |  accessibility
-------------------------------------------------+-------------------------
Changes (by sabernhardt):

 * keywords:  title-attribute has-patch has-unit-tests needs-dev-note commit
     => title-attribute has-patch has-unit-tests commit has-dev-note


Comment:

 Dev note published:
 https://make.wordpress.org/core/2026/05/14/removing-title-attributes-in-
 author-link-functions/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62835#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 15:54:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 15:54:01 -0000
Subject: [wp-trac] [WordPress Trac] #64686: Plugin name and description
 overlap with "Install Now" button in Japanese locale
In-Reply-To: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
References: <055.0b2d7cdf69a96d6d8e8ff7352546b94c@wordpress.org>
Message-ID: <070.d61338e2b05d35159ae436973b6fbbc5@wordpress.org>

#64686: Plugin name and description overlap with "Install Now" button in Japanese
locale
-------------------------------------+-------------------------------------
 Reporter:  hiroshisato              |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  7.0.1
Component:  Administration           |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots admin-   |     Focuses:  ui, css,
  reskin has-patch                   |  administration
-------------------------------------+-------------------------------------
Changes (by sabernhardt):

 * milestone:  7.0 => 7.0.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64686#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:08:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:08:31 -0000
Subject: [wp-trac] [WordPress Trac] #65044: get_post_custom_values()
 missing array check, inconsistent with get_post_custom_keys()
In-Reply-To: <057.4a59bcc730ee55ef2108915dd95410cb@wordpress.org>
References: <057.4a59bcc730ee55ef2108915dd95410cb@wordpress.org>
Message-ID: <072.66122bddf63374a4aa9dfabeb36f2f43@wordpress.org>

#65044: get_post_custom_values() missing array check, inconsistent with
get_post_custom_keys()
-------------------------------------------------+-------------------------
 Reporter:  saratheonline                        |       Owner:
                                                 |  saratheonline
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  7.1
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-test-    |     Focuses:
  info has-unit-tests                            |
-------------------------------------------------+-------------------------

Comment (by ozgursar):

 == Patch Testing Report

 Patch Tested: https://github.com/WordPress/wordpress-develop/pull/11496

 === Environment
 - WordPress: 7.1-alpha-62161-src
 - PHP: 8.2.29
 - Server: nginx/1.29.4
 - Database: mysqli (Server: 8.4.7 / Client: mysqlnd 8.2.29)
 - Browser: Opera
 - OS: macOS
 - Theme: Twenty Twenty-Five 1.5
 - MU Plugins: None activated
 - Plugins:
   * Code Snippets 3.9.6
   * Test Reports 1.2.1

 === Steps taken
 1. Add the following code snippet to your active theme's `functions.php`
 or via Code Snippets plugin:

 {{{#!php
 add_action( 'init', function () {
     // Confirm what get_post_custom() returns for both PR cases
     unset( $GLOBALS['post'] );
     $case1 = get_post_custom( 0 );
     error_log( '[65044] Case 1 — invalid post ID 0: (' . gettype( $case1 )
 . ') ' . var_export( $case1, true ) );

     add_filter( 'get_post_metadata', '__return_empty_string', 1 );
     $case2 = get_post_custom( 1 );
     remove_filter( 'get_post_metadata', '__return_empty_string', 1 );
     error_log( '[65044] Case 2 — filter returns "": (' . gettype( $case2 )
 . ') ' . var_export( $case2, true ) );

     // Detect whether the is_array guard exists in get_post_custom_values
     $src = file_get_contents( ABSPATH . 'wp-includes/post.php' );
     preg_match( '/function get_post_custom_values.*?(?=\nfunction )/s',
 $src, $m );
     $guarded = isset( $m[0] ) && str_contains( $m[0], 'is_array' );
     error_log( '[65044] is_array guard in get_post_custom_values: ' . (
 $guarded ? 'PATCHED' : 'UNPATCHED' ) );
 } );
 }}}


 2. Ensure `WP_DEBUG` and `WP_DEBUG_LOG` are set to `true` in wp-
 config.php, then visit any page as an admin and check wp-content/debug.log
 3. Apply the patch and reload the page to observe the change in
 `debug.log`
 4. ✅ Patch is solving the problem

 === Expected result
 - debug.log before patch:

 [14-May-2026 15:55:09 UTC] [65044] Case 1 — invalid post ID 0: (boolean)
 false
 [14-May-2026 15:55:09 UTC] [65044] Case 2 — filter returns "": (string) ''
 [14-May-2026 15:55:09 UTC] [65044] is_array guard in
 get_post_custom_values: UNPATCHED


 - debug.log after patch:

 [14-May-2026 15:56:04 UTC] [65044] Case 1 — invalid post ID 0: (boolean)
 false
 [14-May-2026 15:56:04 UTC] [65044] Case 2 — filter returns "": (string) ''
 [14-May-2026 15:56:04 UTC] [65044] is_array guard in
 get_post_custom_values: PATCHED

 === Additional Notes
 - Case 1: `get_post_custom(0)` returns `false` because
 `get_metadata_raw()` short-circuits
   immediately when the post ID resolves to `0` (no global `$post`, no
 explicit ID passed).
 - Case 2: `get_post_custom()` returns `""` when a filter on
 `get_post_metadata` short-circuits the metadata lookup.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65044#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:09:08 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:09:08 -0000
Subject: [wp-trac] [WordPress Trac] #65051: $_REQUEST['term'] used
 unsanitized in user search query
In-Reply-To: <052.48e93b7172e09acbd378dc6d127d732f@wordpress.org>
References: <052.48e93b7172e09acbd378dc6d127d732f@wordpress.org>
Message-ID: <067.d56168cd2bb61e61fd0894ff4b700965@wordpress.org>

#65051: $_REQUEST['term'] used unsanitized in user search query
-------------------------------------+-------------------------------------
 Reporter:  rajeshcp                 |       Owner:  rajeshcp
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  7.1
Component:  Networks and Sites       |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  multisite, coding-
  has-test-info has-unit-tests has-  |  standards
  screenshots                        |
-------------------------------------+-------------------------------------
Changes (by vgnavada):

 * keywords:  has-patch needs-testing has-test-info has-unit-tests => has-
     patch needs-testing has-test-info has-unit-tests has-screenshots


Comment:

 == Test Report
 === Description
 This report validates whether the indicated patch works as expected.

 Patch tested: https://github.com/WordPress/wordpress-develop/pull/11530

 === Environment
 - WordPress: 7.1-alpha-20260409.114541
 - PHP: 8.3.30
 - Server: PHP.wasm
 - Database: WP_SQLite_Driver (Server: 8.0.38 / Client: 3.51.0)
 - Browser: Chrome 148.0.0.0
 - OS: macOS
 - Theme: Twenty Twenty-Five 1.4
 - MU Plugins: None activated
 - Plugins:
   * Test Reports 1.2.1
 - Testing setup: WordPress Playground with Multisite enabled

 === Actual Results
 1. ✅ Patch works as expected based on functional Playground testing.

 **Test 1: Malicious payload through browser console**

 Tested the `autocomplete-user` AJAX action using the following payload:

 `<script>alert('XSS')</script>Admin`

 The request completed successfully and returned an empty array:

 `[] success`

 No alert was triggered, no malicious autocomplete suggestion was rendered,
 and no visible console error was observed.

 [[Image(https://i.ibb.co/679vhfqr/image.png)]]

 **Test 2: Normal term through the browser console**

 Tested the same `autocomplete-user` AJAX action using a normal term:

 `admin`

 with `autocomplete_type` set to `add`.

 The request completed successfully and returned an empty array:

 `[] success`

 This is not treated as a failure because, in the Playground setup, the
 `admin` user is already part of `site_id: 1`, so the add-user autocomplete
 flow may exclude that user from the result.

 [[Image(https://i.ibb.co/CsV780c2/image.png)]]

 **Test 3: Manual UI input test**
 Tested the payload directly in the Network Admin user autocomplete input
 field:

 `<script>alert('XSS')</script>Admin`

 The field accepted the typed value, which is expected for a text input. No
 alert was triggered, no script was executed, no malicious autocomplete
 suggestion was rendered, and the page did not break.

 [[Image(https://i.ibb.co/GQKvvYHN/image.png)]]

 === Additional Notes
 - Tested using WordPress Playground with [https://github.com/WordPress
 /wordpress-develop/pull/11530 PR: 11530] and Multisite enabled.
 - The first console screenshot shows the malicious payload test returning
 `[] success`.
 - The second console screenshot shows the normal `admin` term test
 returning `[] success`.
 - This Playground test confirms the visible browser and AJAX behavior.
 - Based on the Playground test, the patch does not visibly break the
 autocomplete-user AJAX action, and the malicious payload does not execute
 or render in the browser.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65051#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:16:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:16:41 -0000
Subject: [wp-trac] [WordPress Trac] #65241: get_editable_roles() returns
 empty array in multisite
In-Reply-To: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
References: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
Message-ID: <066.29cd00c8b09e7acbcbc0664af67b7fcc@wordpress.org>

#65241: get_editable_roles() returns empty array in multisite
--------------------------+------------------------------
 Reporter:  neo2k23       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by neo2k23):

 never mind i restored another backup. issue resolved. please close

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65241#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:21:10 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:21:10 -0000
Subject: [wp-trac] [WordPress Trac] #65141: Fix alignment for sortable
 metabox on post and page edit screen with classic editor
In-Reply-To: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
References: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
Message-ID: <071.3cd4cdc654522fea16a3d12db35d8dae@wordpress.org>

#65141: Fix alignment for sortable metabox on post and page edit screen with
classic editor
-------------------------------------------+-----------------------------
 Reporter:  umesh.nevase                   |       Owner:  SergeyBiryukov
     Type:  defect (bug)                   |      Status:  reopened
 Priority:  normal                         |   Milestone:  7.0
Component:  Editor                         |     Version:  trunk
 Severity:  normal                         |  Resolution:
 Keywords:  admin-reskin has-patch commit  |     Focuses:  ui, css
-------------------------------------------+-----------------------------

Comment (by jadavsanjay):

 == Test Report
 === Description
 This report validates whether the indicated patch works as expected.

 Patch tested: https://core.trac.wordpress.org/ticket/65141

 === Environment
 - WordPress: 7.1-alpha-20260507.074835
 - PHP: 7.4.33
 - Server: PHP.wasm
 - Database: WP_SQLite_Driver (Server: 8.0.38 / Client: 3.51.0)
 - Browser: Chrome 148.0.0.0
 - OS: Windows 10/11
 - Theme: Twenty Twenty-Five 1.4
 - MU Plugins: None activated
 - Plugins:
   * Classic Editor 1.6.7
   * Test Reports 1.2.1

 === Actual Results
 1.  ✅ Issue resolved with patch.

 === Additional Notes
 - After applying the patch, the issue with the alignment of the sortable
 metabox on the post and page edit screen in the Classic Editor has been
 fixed.

 === Supplemental Artifacts

 [[Image(https://i.postimg.cc/kVN7q4TF/patch-1.png)]]
 [[Image(https://i.postimg.cc/xkG9nC65/patch-2.png)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65141#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:30:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:30:42 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.343c0cd8f2d27287a66ce68902f6753f@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
-------------------------------------------------+-------------------------
 Reporter:  jonsurrell                           |       Owner:
                                                 |  westonruter
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  high                                 |   Milestone:  7.0
Component:  Script Loader                        |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:  javascript
  note                                           |
-------------------------------------------------+-------------------------
Changes (by jorbin):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests needs-
     dev-note


Comment:

 > For a future release, I'd like to see an improved solution that
 leverages multiple importmaps that can be printed as necessary.

 100% agree. This might be something we just get when Firefox rolls out
 it's support more broadly so we should follow things there and potentially
 just wait, but I think it's worth ticketing for 7.1 so a proper decision
 can be made.

 I am adding `needs-devnote` since I think this would be good to document.
 I see that module_dependencies don't have a devnote, so if it is getting
 one, I am very ok with this being a part of that.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:47:40 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:47:40 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.544802ac9e5cc4ffa749547329163364@wordpress.org>

#65211: Font upload shows failure message but font is added to library
-----------------------------+------------------------------
 Reporter:  369work          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+------------------------------

Comment (by 369work):

 This issue did not occur in 7.0RC4, so is it okay to wait and see until
 the 7.0 release?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:49:23 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:49:23 -0000
Subject: [wp-trac] [WordPress Trac] #64977: The `core/get-site-info`
 ability returns wrong locale code in the admin
In-Reply-To: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
References: <051.fa74e7932cff36205e00e2d2015b7211@wordpress.org>
Message-ID: <066.f04fadfee93975302342bfa025213f3b@wordpress.org>

#64977: The `core/get-site-info` ability returns wrong locale code in the admin
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  gziolo
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  7.1
Component:  Abilities API                        |     Version:  6.9
 Severity:  normal                               |  Resolution:
 Keywords:  abilities has-patch has-unit-tests   |     Focuses:
  commit                                         |
-------------------------------------------------+-------------------------
Changes (by gziolo):

 * keywords:  abilities has-patch => abilities has-patch has-unit-tests
               commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64977#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:49:48 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:49:48 -0000
Subject: [wp-trac] [WordPress Trac] #65232: Abilities API: Add a fast
 site health summary to `core/get-environment-info`
In-Reply-To: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
References: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
Message-ID: <065.392a0eebfe1eeb5eea45d22b1465adad@wordpress.org>

#65232: Abilities API: Add a fast site health summary to `core/get-environment-
info`
--------------------------------------+-----------------------
 Reporter:  gziolo                    |       Owner:  gziolo
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.1
Component:  Abilities API             |     Version:  6.9
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------

Comment (by westonruter):

 Replying to [comment:2 karunyachavan84]:
 > While reviewing this, I noticed that the existing `health-check-site-
 status-result` transient currently only stores aggregate counts (`good`,
 `recommended`, `critical`) and does not persist the underlying issue
 details needed for the proposed `site_health.issues` response (`label`,
 `severity`, `recommendation`).
 > Since the proposal also explicitly requires that `site_health` be
 populated entirely from cached data and never trigger synchronous Site
 Health tests, it seems like we would first need to expand the Site Health
 caching mechanism itself (likely during the scheduled health check cron
 run and related persistence flows) to store normalized actionable issue
 summaries alongside the counts.
 > Just wanted to confirm whether that scope expansion is expected here, or
 if there’s another existing cached source I may be missing.

 Yes, I think we should be caching the entire Site Health results in a
 transient, not just the aggregate counts. This would be very helpful to
 implement #64066. You can see from the [https://github.com/WordPress
 /wordpress-develop/pull/10123 PR] for that ticket, it had to resort to
 adding a new transient specifically for `health_check_page_cache_detail`
 since the results as a whole aren't cached. If we had caching, then this
 wouldn't be needed.

 The transient should also store a timestamp for when the results were
 obtained, so the Ability can indicate how stale the results are. For sites
 that have broken WP-Cron and no traffic, it could be that the results
 become quite stale.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65232#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:51:23 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:51:23 -0000
Subject: [wp-trac] [WordPress Trac] #64066: Speculative Loading: Change
 default eagerness from conservative to moderate when caching is detected
In-Reply-To: <055.974cf881d7a7e6cda196590bc4005f8a@wordpress.org>
References: <055.974cf881d7a7e6cda196590bc4005f8a@wordpress.org>
Message-ID: <070.325fc0b24f09d858b8d34cded150477e@wordpress.org>

#64066: Speculative Loading: Change default eagerness from conservative to moderate
when caching is detected
-------------------------------------+-------------------------------------
 Reporter:  westonruter              |       Owner:  westonruter
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  Future Release
Component:  General                  |     Version:  6.8
 Severity:  normal                   |  Resolution:
 Keywords:  2nd-opinion has-patch    |     Focuses:  performance,
  early has-unit-tests               |  sustainability
-------------------------------------+-------------------------------------

Comment (by westonruter):

 Note: #65232 proposes caching all Site Health results in a transient
 instead of just the aggregate summary. This could be leveraged by this PR
 instead introducing a new `health_check_page_cache_detail` transient.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64066#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 16:57:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 16:57:34 -0000
Subject: [wp-trac] [WordPress Trac] #65232: Abilities API: Add a fast
 site health summary to `core/get-environment-info`
In-Reply-To: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
References: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
Message-ID: <065.06c27b9d885fa2e91a38cee3ac985de5@wordpress.org>

#65232: Abilities API: Add a fast site health summary to `core/get-environment-
info`
--------------------------------------+-----------------------
 Reporter:  gziolo                    |       Owner:  gziolo
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.1
Component:  Abilities API             |     Version:  6.9
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------

Comment (by gziolo):

 > The transient should also store a timestamp for when the results were
 obtained, so the Ability can indicate how stale the results are. For sites
 that have broken WP-Cron and no traffic, it could be that the results
 become quite stale.

 If that was in place, we would include that as part of the site health
 object. On its own that could be also another site health metric.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65232#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 17:23:12 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 17:23:12 -0000
Subject: [wp-trac] [WordPress Trac] #65086: Add action hooks to media
 modal attachment details templates for field extensibility
In-Reply-To: <054.7fabfdfcb46f5e6537471a8076c5d178@wordpress.org>
References: <054.7fabfdfcb46f5e6537471a8076c5d178@wordpress.org>
Message-ID: <069.5ff0c52097738157aff6b2239a607ed2@wordpress.org>

#65086: Add action hooks to media modal attachment details templates for field
extensibility
-------------------------------------+---------------------
 Reporter:  kaavyaiyer               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  7.1
Component:  Media                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------
Changes (by JeffPaul):

 * keywords:  has-patch => has-patch needs-testing
 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65086#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 20:32:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 20:32:53 -0000
Subject: [wp-trac] [WordPress Trac] #65242: Test: Add unit tests for
 wp_ajax_logged_in()
Message-ID: <051.097e8a3c51608cfe1097e8df1baac4f6@wordpress.org>

#65242: Test: Add unit tests for wp_ajax_logged_in()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 The function wp_ajax_logged_in() in src/wp-admin/includes/ajax-actions.php
 currently lacks unit test coverage. This task involves adding tests to
 verify its behavior for both logged-in and logged-out users.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65242>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 21:01:09 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 21:01:09 -0000
Subject: [wp-trac] [WordPress Trac] #65243: Test: Add unit tests for
 wp_ajax_rest_nonce()
Message-ID: <051.34cb416168384a1523e6a13afbe2b933@wordpress.org>

#65243: Test: Add unit tests for wp_ajax_rest_nonce()
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 The function wp_ajax_rest_nonce() in src/wp-admin/includes/ajax-
 actions.php currently lacks unit test coverage. This task involves adding
 tests to verify that it correctly returns a REST API nonce for logged-in
 users and is inaccessible to logged-out users.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65243>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 21:51:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 21:51:32 -0000
Subject: [wp-trac] [WordPress Trac] #65187: Tests: Add unit tests for
 wp_admin_viewport_meta()
In-Reply-To: <051.9f5ded5d422cf8280c03edf700e7b61a@wordpress.org>
References: <051.9f5ded5d422cf8280c03edf700e7b61a@wordpress.org>
Message-ID: <066.15c4b6ebe7128c8ff773fd2a36f85ddd@wordpress.org>

#65187: Tests: Add unit tests for wp_admin_viewport_meta()
--------------------------------------+---------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65187#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 21:54:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 21:54:02 -0000
Subject: [wp-trac] [WordPress Trac] #65187: Tests: Add unit tests for
 wp_admin_viewport_meta()
In-Reply-To: <051.9f5ded5d422cf8280c03edf700e7b61a@wordpress.org>
References: <051.9f5ded5d422cf8280c03edf700e7b61a@wordpress.org>
Message-ID: <066.fdd88918ff84baa54b83c01220f00ff2@wordpress.org>

#65187: Tests: Add unit tests for wp_admin_viewport_meta()
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  SergeyBiryukov
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62366" 62366]:
 {{{
 #!CommitTicketReference repository="" revision="62366"
 Tests: Add unit tests for `wp_admin_viewport_meta()`.

 Follow-up to [48412].

 Props pbearne.
 Fixes #65187.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65187#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 22:24:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 22:24:59 -0000
Subject: [wp-trac] [WordPress Trac] #65044: get_post_custom_values()
 missing array check, inconsistent with get_post_custom_keys()
In-Reply-To: <057.4a59bcc730ee55ef2108915dd95410cb@wordpress.org>
References: <057.4a59bcc730ee55ef2108915dd95410cb@wordpress.org>
Message-ID: <072.2448b82f0684ef15101924896e008d3f@wordpress.org>

#65044: get_post_custom_values() missing array check, inconsistent with
get_post_custom_keys()
-------------------------------------------------+-------------------------
 Reporter:  saratheonline                        |       Owner:
                                                 |  westonruter
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  7.1
Component:  Posts, Post Types                    |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-test-info has-unit-    |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------
Changes (by westonruter):

 * keywords:  has-patch needs-testing has-test-info has-unit-tests => has-
     patch has-test-info has-unit-tests
 * owner:  saratheonline => westonruter
 * status:  assigned => reviewing


Comment:

 Once `trunk` is open for 7.1 commits, I can commit this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65044#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 22:26:35 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 22:26:35 -0000
Subject: [wp-trac] [WordPress Trac] #65120: Add
 `wp_elements_block_supports_class_name` filter to
 `wp_get_elements_class_name()`
In-Reply-To: <062.c5c4315f56dd742dd7ff410a88a4ea8d@wordpress.org>
References: <062.c5c4315f56dd742dd7ff410a88a4ea8d@wordpress.org>
Message-ID: <077.28402bbf7dd2b2c66b3a6322ef580477@wordpress.org>

#65120: Add `wp_elements_block_supports_class_name` filter to
`wp_get_elements_class_name()`
-------------------------------------+-------------------------------------
 Reporter:  baikare.sandeep007       |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Editor                   |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css, performance,
  has-test-info 2nd-opinion          |  coding-standards
-------------------------------------+-------------------------------------
Changes (by westonruter):

 * keywords:  has-patch needs-testing has-test-info dev-feedback => has-
     patch needs-testing has-test-info 2nd-opinion


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65120#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 22:32:51 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 22:32:51 -0000
Subject: [wp-trac] [WordPress Trac] #65165: Script module dependencies
 may be unavailable on evaluation
In-Reply-To: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
References: <054.e1da24747137f01d2e3792002fbd79af@wordpress.org>
Message-ID: <069.c105b62b011c21c9f6fccceb72687c6c@wordpress.org>

#65165: Script module dependencies may be unavailable on evaluation
-------------------------------------------------+-------------------------
 Reporter:  jonsurrell                           |       Owner:
                                                 |  westonruter
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  high                                 |   Milestone:  7.0
Component:  Script Loader                        |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:  javascript
  note                                           |
-------------------------------------------------+-------------------------

Comment (by westonruter):

 Replying to [comment:15 jorbin]:
 > I am adding `needs-devnote` since I think this would be good to
 document. I see that module_dependencies don't have a devnote, so if it is
 getting one, I am very ok with this being a part of that.

 The keyword is also on #61500 which introduced `module_dependencies`. I am
 still planning to write a dev note for that, but I was first working on
 the dev note for the CodeMirror upgrade, which I'm also behind on!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65165#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 22:44:47 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 22:44:47 -0000
Subject: [wp-trac] [WordPress Trac] #65032: View transition admin bar
 quirks
In-Reply-To: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
References: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
Message-ID: <067.a377bebbdf77febba3aff2f24892ea21@wordpress.org>

#65032: View transition admin bar quirks
----------------------------+------------------------
 Reporter:  zieladam        |       Owner:  audrasjb
     Type:  defect (bug)    |      Status:  reviewing
 Priority:  normal          |   Milestone:  7.0
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  ui
----------------------------+------------------------
Changes (by westonruter):

 * Attachment "admin-bar-view-transition-slow-motion.mp4" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65032>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 22:55:03 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 22:55:03 -0000
Subject: [wp-trac] [WordPress Trac] #65032: View transition admin bar
 quirks
In-Reply-To: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
References: <052.d3976b04de79bffe571991b0af018a96@wordpress.org>
Message-ID: <067.a2021f5a04cb259bd389353a457f520b@wordpress.org>

#65032: View transition admin bar quirks
-----------------------------+--------------------------
 Reporter:  zieladam         |       Owner:  westonruter
     Type:  defect (bug)     |      Status:  reviewing
 Priority:  normal           |   Milestone:  7.0
Component:  Administration   |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |     Focuses:  ui
-----------------------------+--------------------------
Changes (by westonruter):

 * keywords:  has-patch => has-patch close
 * owner:  audrasjb => westonruter


Comment:

 I zoomed in to the original and stepped through it frame-by-frame at
 around 2 seconds into the video. See [attachment:"admin-bar-view-
 transition-slow-motion.mp4"].

 @zieladam Please confirm this is what you were referring to: The dashicons
 in the admin bar appear to not be initialized when first landing on the
 target page, which causes the admin bar items to appear to shift left and
 right during some navigations.

 I think I can reproduce this locally, but:

 1. I have to open DevTools
 2. I have to enable 4x CPU throttling
 3. I have to disable cache.

 So this all seems to boil down to rendering delay for the Dashicons font.
 Given that the font will be loaded on the first admin page view and
 subsequent page views will have it in cache (unless you've disabled cache
 via DevTools), then I do not think this is an actual issue that users will
 experience.

 So I'm suggesting that we close this as worksforme.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65032#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu May 14 23:08:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 14 May 2026 23:08:53 -0000
Subject: [wp-trac] [WordPress Trac] #64260: Default filter
 `doing_it_wrong_trigger_error` for REST request cause no notice at all.
In-Reply-To: <049.133812aede8422193f5b7ef313adb64d@wordpress.org>
References: <049.133812aede8422193f5b7ef313adb64d@wordpress.org>
Message-ID: <064.66a81df719edc2d3603ee5c9630ce249@wordpress.org>

#64260: Default filter `doing_it_wrong_trigger_error` for REST request cause no
notice at all.
--------------------------+--------------------------
 Reporter:  okvee         |       Owner:  westonruter
     Type:  defect (bug)  |      Status:  reviewing
 Priority:  normal        |   Milestone:  7.1
Component:  REST API      |     Version:  4.4
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  rest-api
--------------------------+--------------------------
Changes (by westonruter):

 * owner:  (none) => westonruter
 * status:  new => reviewing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64260#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 00:07:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 00:07:54 -0000
Subject: [wp-trac] [WordPress Trac] #65105: Details Block - Enhancement
 Request
In-Reply-To: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
References: <050.87c17924a66786e661708ecaabdc0354@wordpress.org>
Message-ID: <065.06516b40ea1ee38222c74f27fc5126aa@wordpress.org>

#65105: Details Block - Enhancement Request
-------------------------+------------------------------
 Reporter:  mowill       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:  6.9.4
 Severity:  normal       |  Resolution:
 Keywords:  close        |     Focuses:
-------------------------+------------------------------

Comment (by westonruter):

 @mowill Specifically the best place to request a new block would be the
 Gutenberg repo on GitHub here:
 https://github.com/WordPress/gutenberg/issues

 I don't know if this block specifically warrants being in core or if it
 would be better as a plugin, however.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65105#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 04:44:55 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 04:44:55 -0000
Subject: [wp-trac] [WordPress Trac] #65141: Fix alignment for sortable
 metabox on post and page edit screen with classic editor
In-Reply-To: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
References: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
Message-ID: <071.63221748792414ded7d1fc3fbac77b35@wordpress.org>

#65141: Fix alignment for sortable metabox on post and page edit screen with
classic editor
-------------------------------------------+-----------------------------
 Reporter:  umesh.nevase                   |       Owner:  SergeyBiryukov
     Type:  defect (bug)                   |      Status:  reopened
 Priority:  normal                         |   Milestone:  7.0
Component:  Editor                         |     Version:  trunk
 Severity:  normal                         |  Resolution:
 Keywords:  admin-reskin has-patch commit  |     Focuses:  ui, css
-------------------------------------------+-----------------------------

Comment (by khokansardar):

 ## Patch testing report

 **Patch / PR tested**
 - https://github.com/WordPress/wordpress-develop/pull/11689 (diff against
 trunk as of <date or commit SHA you tested>)

 **Environment**
 - WordPress: trunk @ ( commit or "Playground PR build" )
 - PHP: 8.2
 - Server: nginx / Playground
 - OS: macOS 15
 - Browser: Chrome 136, Safari 18

 **Steps**
 1. Open Posts → Edit a post that uses the classic metabox layout (or
 install/enable classic editing if your test site uses blocks only).
 2. Note alignment between editor area and right-hand metabox column at
 full width and after narrowing the window.
 3. Toggle metabox columns if available; expand/collapse postboxes.
 4. Drag a metabox to reorder (if applicable).

 **Results**
 - Before patch (or on current trunk without PR): describe misalignment if
 you still see it on trunk
 - With PR #11689: aligned / no regression
 - Drag-and-drop / metabox UI: OK or issue

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65141#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 06:01:24 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 06:01:24 -0000
Subject: [wp-trac] [WordPress Trac] #65244: Bulk Select button is vertically
 misaligned in Media Library toolbar
Message-ID: <056.3cc9648d7d7b0099dca7e2539b975999@wordpress.org>

#65244: Bulk Select button is vertically misaligned in Media Library toolbar
--------------------------+-----------------------------
 Reporter:  tusharaddweb  |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  trunk
 Severity:  normal        |   Keywords:  needs-patch
  Focuses:  ui, css       |
--------------------------+-----------------------------
 The "Bulk Select" button in the Media Library toolbar appears vertically
 misaligned. It does not align with the "Filter by type" and "Filter by
 date" dropdowns that are present in the same toolbar row.


 == Steps to Reproduce ==
 1. Go to Media Library
 2. Observe the toolbar containing "Filter by type", "Filter by date"
 dropdowns and "Bulk select" button

 == Expected Behavior ==
 All toolbar controls (dropdowns and button) should be vertically
 centered/aligned on the same baseline.

 == Actual Behavior ==
 The "Bulk select" button appears vertically misaligned compared to the
 filter dropdowns in the toolbar.

 Please refer to the attached image for visual reference.

 https://postimg.cc/68qPZxmv

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65244>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 06:12:42 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 06:12:42 -0000
Subject: [wp-trac] [WordPress Trac] #64725: Background block support:
 render uploaded images as <img> for responsive image support
In-Reply-To: <054.4ec927981671a52de09e5994d9618d4f@wordpress.org>
References: <054.4ec927981671a52de09e5994d9618d4f@wordpress.org>
Message-ID: <069.0980d0915d6fe0d2ed7f42611feae7a0@wordpress.org>

#64725: Background block support: render uploaded images as <img> for responsive
image support
-------------------------+-------------------------------------------------
 Reporter:  JosVelasco   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  javascript, css, tests,
                         |  performance
-------------------------+-------------------------------------------------
Changes (by sanayasir):

 * keywords:  has-patch has-unit-tests needs-testing => has-patch


Comment:

 Tested this patch on WordPress Beta 7 and verified that the implementation
 behaves as expected and aligns with the requirements outlined in the
 ticket.

 Tested scenarios
 Group block with background image using cover and no-repeat
 Group block with background image using contain and no-repeat
 Background images using explicit tiling values: repeat, repeat-x, and
 repeat-y
 Background images with background-attachment: fixed
 Results
 Confirmed that background images using cover or contain without tiling are
 now rendered using a native <img> element instead of a CSS background-
 image.
 Verified that the rendered <img> includes responsive and performance-
 related attributes such as srcset, sizes, loading="lazy", and
 decoding="async".
 Confirmed that no-repeat is treated equivalently to an unset repeat value.
 Verified that explicit tiling values and background-attachment: fixed
 correctly continue using the CSS background-image rendering path.
 Confirmed that position: relative is applied to the wrapper only when
 necessary and does not override any existing position styles.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64725#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 06:17:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 06:17:06 -0000
Subject: [wp-trac] [WordPress Trac] #64725: Background block support:
 render uploaded images as <img> for responsive image support
In-Reply-To: <054.4ec927981671a52de09e5994d9618d4f@wordpress.org>
References: <054.4ec927981671a52de09e5994d9618d4f@wordpress.org>
Message-ID: <069.7b2867b98735d45d5a2995e24f07a708@wordpress.org>

#64725: Background block support: render uploaded images as <img> for responsive
image support
-------------------------+-------------------------------------------------
 Reporter:  JosVelasco   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  javascript, css, tests,
                         |  performance
-------------------------+-------------------------------------------------
Changes (by sanayasir):

 * Attachment "Backgorund image tag.mp4" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64725>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 07:05:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 07:05:30 -0000
Subject: [wp-trac] [WordPress Trac] #65245: Accented or special characters
 issue
Message-ID: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>

#65245: Accented or special characters issue
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  (none)
  clementpolito          |
     Type:  defect       |     Status:  new
  (bug)                  |
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:
 Severity:  normal       |   Keywords:  has-screenshots needs-patch needs-
  Focuses:               |  testing
-------------------------+-------------------------------------------------
 On WordPress 7.0-RC4, on the page /wp-admin/credits.php, I encounter an
 issue with some characters.

 At first, I thought there might be a character encoding issue with my
 database tables on my end, but in fact, some accented characters are
 displaying correctly elsewhere on the page. And @audrasjb reproduce the
 issue.

 In the screenshots :
 - "Fabian Kägy" should be "Fabian Kaegy"
 - "Albert Juhﾃｩ Lluveras" should be "Albert Juhé Lluveras"
 - "Alvaro Gﾃｳmez" should be "Alvaro Gómez"
 - "Béryl de La Grandière" is ok
 - "Eliezer Peﾃｱa" should be "Eliezer Peña"
 - "Johannes Jﾃｼlg" should be "Johannes Jülg"
 - Etc.

 By switching into French language to have a lot of accents, I reproduce
 the issue on the contributors name, but I have more correct accents in
 this page, and I didn't detect the issue elsewhere in others admin pages.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65245>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 07:06:43 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 07:06:43 -0000
Subject: [wp-trac] [WordPress Trac] #65245: Accented or special
 characters issue
In-Reply-To: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
References: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
Message-ID: <072.a2d7f3598fa6f1eda815effb60d58261@wordpress.org>

#65245: Accented or special characters issue
-------------------------------------------------+-------------------------
 Reporter:  clementpolito                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots needs-patch needs-   |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by clementpolito):

 * Attachment "01-wp-7-0-rc4-character-issue-noteworthy-contributors.jpg"
 added.

 Character issue in noteworthy contributors

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65245>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 07:07:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 07:07:13 -0000
Subject: [wp-trac] [WordPress Trac] #65245: Accented or special
 characters issue
In-Reply-To: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
References: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
Message-ID: <072.4f129e76d83000d84ef95627535b18af@wordpress.org>

#65245: Accented or special characters issue
-------------------------------------------------+-------------------------
 Reporter:  clementpolito                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots needs-patch needs-   |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by clementpolito):

 * Attachment "02-wp-7-0-rc4-character-issue-core-contributors.jpg" added.

 Character issue in core contributors

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65245>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 07:08:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 07:08:05 -0000
Subject: [wp-trac] [WordPress Trac] #65245: Accented or special
 characters issue
In-Reply-To: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
References: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
Message-ID: <072.3bb18e3f7b315af383d24793ebef695d@wordpress.org>

#65245: Accented or special characters issue
-------------------------------------------------+-------------------------
 Reporter:  clementpolito                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots needs-patch needs-   |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by clementpolito):

 * Attachment "03-wp-7-0-rc4-character-issue-french-example.jpg" added.

 Example in French language

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65245>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 07:16:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 07:16:53 -0000
Subject: [wp-trac] [WordPress Trac] #65241: get_editable_roles() returns
 empty array in multisite
In-Reply-To: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
References: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
Message-ID: <066.76b279d7c6c1c7f8a43c566a2f305ad8@wordpress.org>

#65241: get_editable_roles() returns empty array in multisite
--------------------------+------------------------------
 Reporter:  neo2k23       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+------------------------------
Changes (by sukhendu2002):

 * keywords:   => close


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65241#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 07:16:59 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 07:16:59 -0000
Subject: [wp-trac] [WordPress Trac] #65245: Accented or special
 characters issue
In-Reply-To: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
References: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
Message-ID: <072.fd4ceba72b4b174f99e5dc9fff822d9d@wordpress.org>

#65245: Accented or special characters issue
-------------------------------------------------+-------------------------
 Reporter:  clementpolito                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots needs-patch needs-   |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------

Comment (by ocean90):

 Fabian Kägy is actually correct. ä is a German umlaut. :)

 For the other ones, this looks more like an issue on WordPress.org since
 the API already returns the incorrect encoding, see
 https://api.wordpress.org/core/credits/1.1/?version=6.9.
 The profiles, e.g. https://profiles.wordpress.org/aljullu/ and
 https://profiles.wordpress.org/anlino/, are looking ok though.

 /cc @dd32 since you have worked on this before, IIRC

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65245#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 07:22:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 07:22:32 -0000
Subject: [wp-trac] [WordPress Trac] #65141: Fix alignment for sortable
 metabox on post and page edit screen with classic editor
In-Reply-To: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
References: <056.a2041e2c35d0005f2c335a081657df6e@wordpress.org>
Message-ID: <071.c8e0361b85604565daca888f2bbd31e1@wordpress.org>

#65141: Fix alignment for sortable metabox on post and page edit screen with
classic editor
-------------------------------------------+-----------------------------
 Reporter:  umesh.nevase                   |       Owner:  SergeyBiryukov
     Type:  defect (bug)                   |      Status:  reopened
 Priority:  normal                         |   Milestone:  7.0
Component:  Editor                         |     Version:  trunk
 Severity:  normal                         |  Resolution:
 Keywords:  admin-reskin has-patch commit  |     Focuses:  ui, css
-------------------------------------------+-----------------------------

Comment (by darshitrajyaguru97):

 == Patch Testing Report ==

 '''Patch tested:'''
 https://github.com/WordPress/wordpress-develop/pull/11689

 === **Environment ===

 * WordPress: trunk (Playground PR build)
 * PHP: 8.2
 * Server: nginx / Playground
 * OS: Windows 11
 * Browser: Chrome

 === **Testing Performed ===

 * Opened the post editor using the classic metabox layout
 * Verified editor and metabox column alignment at multiple viewport widths
 * Tested expand/collapse functionality for postboxes
 * Tested metabox column toggling
 * Verified drag-and-drop metabox reordering behavior

 === **Results ===

 * On current trunk, minor alignment inconsistencies were still noticeable
 when narrowing the editor width.
 * With PR #11689 applied, the editor area and metabox column alignment
 appeared consistent across tested layouts and screen sizes.
 * Drag-and-drop functionality and general metabox interactions worked
 correctly without any noticeable regressions.

 === Summary ===
 Patch tested successfully and worked as expected in the tested
 environment.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65141#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 07:40:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 07:40:32 -0000
Subject: [wp-trac] [WordPress Trac] #65231: Add Plugins > Favourites:
 Input field and Submit button are not properly horizontally aligned
In-Reply-To: <053.c1f3ff7c8f97857b0dc3e92d8d9fd822@wordpress.org>
References: <053.c1f3ff7c8f97857b0dc3e92d8d9fd822@wordpress.org>
Message-ID: <068.ff78e1d5a0d185d33281a3317eda3b3a@wordpress.org>

#65231: Add Plugins > Favourites: Input field and Submit button are not properly
horizontally aligned
--------------------------+--------------------------------------
 Reporter:  bayejid00     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0.1
Component:  Plugins       |     Version:
 Severity:  minor         |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, css, administration
--------------------------+--------------------------------------

Comment (by tusharaddweb):

 I tested this issue on WordPress 7.0-RC3 and I was able to reproduce the
 misalignment.

 Refer Below Images :

 Before Patch :
 https://postimg.cc/9rGhF7k5

 After-Patch :
 https://postimg.cc/569h1RLG

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65231#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 08:14:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 08:14:53 -0000
Subject: [wp-trac] [WordPress Trac] #65246: Add Data Export Request:
 Confirmation email checkbox is not properly aligned
Message-ID: <056.37fb1cb7fca9dce3cdd221f3a980df7d@wordpress.org>

#65246: Add Data Export Request: Confirmation email checkbox is not properly
aligned
--------------------------+-----------------------------
 Reporter:  soyebsalar01  |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:  needs-patch
  Focuses:  ui, css       |
--------------------------+-----------------------------
 The checkbox on the "Add Data Export Request" page is not
 properly vertically aligned with the "Send personal data
 export confirmation email." label text.

 == Steps To Reproduce ==

 1. Go to Tools > Export Personal Data.
 2. Observe the "Confirmation email" field.
 3. Check the alignment of the checkbox with the label text.

 Refer Bolow Image :

 https://postimg.cc/xkmS4pz9

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65246>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 08:18:17 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 08:18:17 -0000
Subject: [wp-trac] [WordPress Trac] #65244: Bulk Select button is
 vertically misaligned in Media Library toolbar
In-Reply-To: <056.3cc9648d7d7b0099dca7e2539b975999@wordpress.org>
References: <056.3cc9648d7d7b0099dca7e2539b975999@wordpress.org>
Message-ID: <071.ea13140d0b2d9bcb629eb4b0b52940e0@wordpress.org>

#65244: Bulk Select button is vertically misaligned in Media Library toolbar
--------------------------+------------------------------
 Reporter:  tusharaddweb  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:  duplicate
 Keywords:  needs-patch   |     Focuses:  ui, css
--------------------------+------------------------------
Changes (by Presskopp):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Duplicate of #64936.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65244#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 08:19:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 08:19:53 -0000
Subject: [wp-trac] [WordPress Trac] #65246: Add Data Export Request:
 Confirmation email checkbox is not properly aligned
In-Reply-To: <056.37fb1cb7fca9dce3cdd221f3a980df7d@wordpress.org>
References: <056.37fb1cb7fca9dce3cdd221f3a980df7d@wordpress.org>
Message-ID: <071.27655fcc5035d6c0f9b4159beec39592@wordpress.org>

#65246: Add Data Export Request: Confirmation email checkbox is not properly
aligned
--------------------------+------------------------------
 Reporter:  soyebsalar01  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  ui, css
--------------------------+------------------------------
Changes (by soyebsalar01):

 * version:   => trunk


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65246#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 09:50:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 09:50:11 -0000
Subject: [wp-trac] [WordPress Trac] #65241: get_editable_roles() returns
 empty array in multisite
In-Reply-To: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
References: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
Message-ID: <066.8ff2d63f5d469ace2474d4ef985c5823@wordpress.org>

#65241: get_editable_roles() returns empty array in multisite
--------------------------+------------------------------
 Reporter:  neo2k23       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+------------------------------

Comment (by neo2k23):

 I want to reopen this ticket.  as i discovered the why this happened.

 Its a bug in cpanel copy when it changes the wp prefix.  It forgets to
 change the old prefix in the options_table for the multisite
 old_prefix_xx_user_roles

 f.e. in a multisite the user roles are stored in my case in
 OLDPREFIX_33_user_roles.  After the database prefix changed to NEWPREFIX
 that option should have also been changed to  NEWPREFIX_33_user_roles. but
 it remained OLDPREFIX_33_user_roles.

 Since wordpress is calling databaseprefix_site_id_user_roles where site_id
 is a number of the site in the multisite it gets a empty user role list
 calling get_editable_roles()

 **The question is why does wordpress add the site_id into the option that
 stores the user roles as they are store in the option table of the sub
 site in the multi site and not in the main option table of the first site
 in the multi_site.  It is not needed to add the site_id into that
 variable.**

 So why is the site_id number added into that variable?  Its the only
 variable in the complete options stored that has this site_id added.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65241#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 10:02:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 10:02:11 -0000
Subject: [wp-trac] [WordPress Trac] #65241: get_editable_roles() returns
 empty array in multisite
In-Reply-To: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
References: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
Message-ID: <066.0f22e91cfa193024049a922e045f2cb6@wordpress.org>

#65241: get_editable_roles() returns empty array in multisite
--------------------------+------------------------------
 Reporter:  neo2k23       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by sukhendu2002):

 * keywords:  close =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65241#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 10:13:47 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 10:13:47 -0000
Subject: [wp-trac] [WordPress Trac] #65241: get_editable_roles() returns
 empty array in multisite
In-Reply-To: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
References: <051.0e835c52fa9c3ca23876ef3057503450@wordpress.org>
Message-ID: <066.5b3263f5ac49a81aa8f221cb317801c1@wordpress.org>

#65241: get_editable_roles() returns empty array in multisite
--------------------------+------------------------------
 Reporter:  neo2k23       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by neo2k23):

 * Attachment "multi-site-optiontabel-user_roles.jpg" added.

 _wp_user_roles _wp_xx_user_roles not changed

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65241>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 10:32:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 10:32:06 -0000
Subject: [wp-trac] [WordPress Trac] #65191: deletePluginSuccess does not
 update counts for custom plugin_status groups
In-Reply-To: <052.d4bbf842536c16e47061eee401603e57@wordpress.org>
References: <052.d4bbf842536c16e47061eee401603e57@wordpress.org>
Message-ID: <067.3322de4127d29ff901779ed10fc1ca09@wordpress.org>

#65191: deletePluginSuccess does not update counts for custom plugin_status groups
-------------------------------------+-----------------------------
 Reporter:  andrew.p                 |       Owner:  SergeyBiryukov
     Type:  defect (bug)             |      Status:  reviewing
 Priority:  normal                   |   Milestone:  7.1
Component:  Plugins                  |     Version:
 Severity:  minor                    |  Resolution:
 Keywords:  needs-testing has-patch  |     Focuses:
-------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => reviewing
 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65191#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 11:06:15 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 11:06:15 -0000
Subject: [wp-trac] [WordPress Trac] #65232: Abilities API: Add a fast
 site health summary to `core/get-environment-info`
In-Reply-To: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
References: <050.beb10c4bb418839c8b4c35da3fe56f5b@wordpress.org>
Message-ID: <065.77091a4ea7fba9253f015f6b6c2f8be3@wordpress.org>

#65232: Abilities API: Add a fast site health summary to `core/get-environment-
info`
--------------------------------------+-----------------------
 Reporter:  gziolo                    |       Owner:  gziolo
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.1
Component:  Abilities API             |     Version:  6.9
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------

Comment (by soyebsalar01):

 Document cache staleness directly in the JSON Schema description, not just
 the ticket.
 Confirm counts always shows full totals even when issues is capped at 10.
 Mark recommendation as nullable — not all Site Health tests have a
 remediation step.
 Add status: "unknown" as an explicit unit test case.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65232#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 11:09:33 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 11:09:33 -0000
Subject: [wp-trac] [WordPress Trac] #65247: Black screen briefly appears on
 Connectors screen in WP 7.1-alpha
Message-ID: <054.9b8cad5288e4ed81cd23748aee013f5d@wordpress.org>

#65247: Black screen briefly appears on Connectors screen in WP 7.1-alpha
-------------------------------------------------+-------------------------
 Reporter:  sumitsingh                           |      Owner:  (none)
     Type:  defect (bug)                         |     Status:  new
 Priority:  normal                               |  Milestone:  Awaiting
                                                 |  Review
Component:  Administration                       |    Version:  trunk
 Severity:  normal                               |   Keywords:  has-
  Focuses:  ui, accessibility, administration,   |  screenshots
  performance, coding-standards                  |
-------------------------------------------------+-------------------------
 When navigating to the Connectors screen in WordPress 7.1-alpha (build
 62366), the screen briefly shows a black flash before rendering content.
 This seems like a rendering or initialization issue in the admin interface
 and could confuse users.

 **Steps to reproduce:**
 Install WordPress 7.1-alpha-62366.
 Log in to the admin dashboard.
 Navigate to Connectors.
 Observe the black screen that appears briefly before the interface loads.

 **Expected behavior:**
 The Connectors screen should render smoothly without any black flash.

 **Observed behavior:**
 A black screen appears for a short time before the content loads.

 **Environment:**
 WordPress version: 7.1-alpha-62366
 Site language: en_US
 User language: en_US
 Timezone: UTC+0
 Home URL: https://playground.wordpress.net/scope:generous-noisy-garden
 Site URL: https://playground.wordpress.net/scope:generous-noisy-garden
 Permalink structure: /%year%/%monthnum%/%day%/%postname%/
 HTTPS: Yes
 Multisite: No
 Registration allowed: No
 Discourage search engines: No
 Default comment status: Open
 Environment type: Production
 User count: 1
 Communication with WordPress.org: Reachable


 **Quick recording available for reference.**

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65247>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 11:10:03 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 11:10:03 -0000
Subject: [wp-trac] [WordPress Trac] #65247: Black screen briefly appears
 on Connectors screen in WP 7.1-alpha
In-Reply-To: <054.9b8cad5288e4ed81cd23748aee013f5d@wordpress.org>
References: <054.9b8cad5288e4ed81cd23748aee013f5d@wordpress.org>
Message-ID: <069.9e90ea8751a570beb99093aad0682e51@wordpress.org>

#65247: Black screen briefly appears on Connectors screen in WP 7.1-alpha
-------------------------+-------------------------------------------------
 Reporter:  sumitsingh   |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:               |     Version:  trunk
  Administration         |
 Severity:  normal       |  Resolution:
 Keywords:  has-         |     Focuses:  ui, accessibility, administration,
  screenshots            |  performance, coding-standards
-------------------------+-------------------------------------------------
Changes (by sumitsingh):

 * Attachment "WordPress Playground.mp4" added.

 Black screen briefly appears on Connectors screen

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65247>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 11:15:31 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 11:15:31 -0000
Subject: [wp-trac] [WordPress Trac] #65247: Black screen briefly appears
 on Connectors screen in WP 7.1-alpha
In-Reply-To: <054.9b8cad5288e4ed81cd23748aee013f5d@wordpress.org>
References: <054.9b8cad5288e4ed81cd23748aee013f5d@wordpress.org>
Message-ID: <069.0987765a48f6c76a8cb8c6623047c813@wordpress.org>

#65247: Black screen briefly appears on Connectors screen in WP 7.1-alpha
-------------------------+-------------------------------------------------
 Reporter:  sumitsingh   |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:               |     Version:  trunk
  Administration         |
 Severity:  normal       |  Resolution:
 Keywords:  has-         |     Focuses:  ui, accessibility, administration,
  screenshots            |  coding-standards
-------------------------+-------------------------------------------------
Changes (by mukesh27):

 * focuses:  ui, accessibility, administration, performance, coding-
     standards => ui, accessibility, administration, coding-standards


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65247#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 11:38:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 11:38:16 -0000
Subject: [wp-trac] [WordPress Trac] #65248: Abilities API: add
 `wp_ability_invoked` action for pipeline-entry observers
Message-ID: <050.60981f9a1640d459a6a07bf1a6d6c922@wordpress.org>

#65248: Abilities API: add `wp_ability_invoked` action for pipeline-entry observers
---------------------------+--------------------
 Reporter:  gziolo         |      Owner:  (none)
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:  7.1
Component:  Abilities API  |    Version:  6.9
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+--------------------
 The execution lifecycle filters proposed in #64989 give the Abilities API
 four
 seams: `wp_pre_execute_ability`, `wp_before_execute_ability`,
 `wp_after_execute_ability`,
 and `wp_execute_ability_result`. `wp_before_execute_ability` fires after
 input
 normalization, validation, and the permission check — its contract is
 "execution is
 imminent." That contract is correct: rate-limiter, cached-response, and
 dry-run observers
 all rely on it not firing for calls that exit early.

 That leaves a gap for audit and snapshot observers, which need the
 opposite signal: "the
 pipeline received this invocation, regardless of outcome." They want a
 hook that fires
 for every call — approval-pending, rate-limited, cached, dry-run, and
 normal — so the
 audit row exists no matter how the call exits, and fires before
 normalization so the
 input is captured raw.

 == Proposal ==

 Add a `wp_ability_invoked` action at the top of `WP_Ability::execute()`,
 before
 `wp_pre_execute_ability` runs:

 {{{
 #!php
 do_action( 'wp_ability_invoked', $this->name, $input, $this );
 }}}

 The argument shape mirrors `wp_before_execute_ability` so observers can
 attach the same
 callback signature to both hooks. The past-tense verb communicates
 "entered the pipeline"
 without implying the call will execute.

 == Lifecycle position ==

 {{{
 execute( $input ) {
     do_action( 'wp_ability_invoked', ... );      // new — every call, raw
 input
     apply_filters( 'wp_pre_execute_ability', ... ); // existing — short-
 circuit seam
     // normalize_input → validate_input → check_permissions
     do_action( 'wp_before_execute_ability', ... ); // existing — execution
 imminent
     // execute_callback
     do_action( 'wp_after_execute_ability', ... );
     return apply_filters( 'wp_execute_ability_result', ... );
 }
 }}}

 == Motivation ==

 Surfaced in
 [https://github.com/WordPress/ai/discussions/477#discussioncomment-16900589
 WordPress/ai#477]. The AbilityGuard plugin currently writes its audit row
 inline inside
 its `wp_pre_execute_ability` handler because no earlier signal exists,
 which conflates
 "build the approval envelope" with "record that an invocation happened."
 Landing
 `wp_ability_invoked` lets that work move to a dedicated observer listener
 and keeps the
 pre-execute handler focused on its short-circuit responsibility.

 The same signal benefits any observability layer that needs invocation
 entry counts
 independent of outcome (telemetry, rate-limit accounting that includes
 rejected calls,
 etc.).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65248>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 11:39:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 11:39:52 -0000
Subject: [wp-trac] [WordPress Trac] #65248: Abilities API: add
 `wp_ability_invoked` action for pipeline-entry observers
In-Reply-To: <050.60981f9a1640d459a6a07bf1a6d6c922@wordpress.org>
References: <050.60981f9a1640d459a6a07bf1a6d6c922@wordpress.org>
Message-ID: <065.a62840a6e520d491658f5b3dee1f1f21@wordpress.org>

#65248: Abilities API: add `wp_ability_invoked` action for pipeline-entry observers
---------------------------+---------------------
 Reporter:  gziolo         |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  7.1
Component:  Abilities API  |     Version:  6.9
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+---------------------
Description changed by gziolo:

Old description:

> The execution lifecycle filters proposed in #64989 give the Abilities API
> four
> seams: `wp_pre_execute_ability`, `wp_before_execute_ability`,
> `wp_after_execute_ability`,
> and `wp_execute_ability_result`. `wp_before_execute_ability` fires after
> input
> normalization, validation, and the permission check — its contract is
> "execution is
> imminent." That contract is correct: rate-limiter, cached-response, and
> dry-run observers
> all rely on it not firing for calls that exit early.
>
> That leaves a gap for audit and snapshot observers, which need the
> opposite signal: "the
> pipeline received this invocation, regardless of outcome." They want a
> hook that fires
> for every call — approval-pending, rate-limited, cached, dry-run, and
> normal — so the
> audit row exists no matter how the call exits, and fires before
> normalization so the
> input is captured raw.
>
> == Proposal ==
>
> Add a `wp_ability_invoked` action at the top of `WP_Ability::execute()`,
> before
> `wp_pre_execute_ability` runs:
>
> {{{
> #!php
> do_action( 'wp_ability_invoked', $this->name, $input, $this );
> }}}
>
> The argument shape mirrors `wp_before_execute_ability` so observers can
> attach the same
> callback signature to both hooks. The past-tense verb communicates
> "entered the pipeline"
> without implying the call will execute.
>
> == Lifecycle position ==
>
> {{{
> execute( $input ) {
>     do_action( 'wp_ability_invoked', ... );      // new — every call, raw
> input
>     apply_filters( 'wp_pre_execute_ability', ... ); // existing — short-
> circuit seam
>     // normalize_input → validate_input → check_permissions
>     do_action( 'wp_before_execute_ability', ... ); // existing —
> execution imminent
>     // execute_callback
>     do_action( 'wp_after_execute_ability', ... );
>     return apply_filters( 'wp_execute_ability_result', ... );
> }
> }}}
>
> == Motivation ==
>
> Surfaced in
> [https://github.com/WordPress/ai/discussions/477#discussioncomment-16900589
> WordPress/ai#477]. The AbilityGuard plugin currently writes its audit row
> inline inside
> its `wp_pre_execute_ability` handler because no earlier signal exists,
> which conflates
> "build the approval envelope" with "record that an invocation happened."
> Landing
> `wp_ability_invoked` lets that work move to a dedicated observer listener
> and keeps the
> pre-execute handler focused on its short-circuit responsibility.
>
> The same signal benefits any observability layer that needs invocation
> entry counts
> independent of outcome (telemetry, rate-limit accounting that includes
> rejected calls,
> etc.).

New description:

 The execution lifecycle filters proposed in #64989 give the Abilities API
 four seams: `wp_pre_execute_ability`, `wp_before_execute_ability`,
 `wp_after_execute_ability`, and `wp_execute_ability_result`.
 `wp_before_execute_ability` fires after input normalization, validation,
 and the permission check — its contract is "execution is imminent." That
 contract is correct: rate-limiter, cached-response, and dry-run observers
 all rely on it not firing for calls that exit early.

 That leaves a gap for audit and snapshot observers, which need the
 opposite signal: "the pipeline received this invocation, regardless of
 outcome." They want a hook that fires for every call — approval-pending,
 rate-limited, cached, dry-run, and normal — so the audit row exists no
 matter how the call exits, and fires before normalization so the input is
 captured raw.

 == Proposal ==

 Add a `wp_ability_invoked` action at the top of `WP_Ability::execute()`,
 before `wp_pre_execute_ability` runs:

 {{{
 #!php
 do_action( 'wp_ability_invoked', $this->name, $input, $this );
 }}}

 The argument shape mirrors `wp_before_execute_ability` so observers can
 attach the same callback signature to both hooks. The past-tense verb
 communicates "entered the pipeline" without implying the call will
 execute.

 == Lifecycle position ==

 {{{
 execute( $input ) {
     do_action( 'wp_ability_invoked', ... );      // new — every call, raw
 input
     apply_filters( 'wp_pre_execute_ability', ... ); // existing — short-
 circuit seam
     // normalize_input → validate_input → check_permissions
     do_action( 'wp_before_execute_ability', ... ); // existing — execution
 imminent
     // execute_callback
     do_action( 'wp_after_execute_ability', ... );
     return apply_filters( 'wp_execute_ability_result', ... );
 }
 }}}

 == Motivation ==

 Surfaced in
 [https://github.com/WordPress/ai/discussions/477#discussioncomment-16900589
 WordPress/ai#477]. The AbilityGuard plugin currently writes its audit row
 inline inside its `wp_pre_execute_ability` handler because no earlier
 signal exists, which conflates "build the approval envelope" with "record
 that an invocation happened." Landing `wp_ability_invoked` lets that work
 move to a dedicated observer listener and keeps the pre-execute handler
 focused on its short-circuit responsibility.

 The same signal benefits any observability layer that needs invocation
 entry counts independent of outcome (telemetry, rate-limit accounting that
 includes rejected calls, etc.).

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65248#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 11:42:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 11:42:22 -0000
Subject: [wp-trac] [WordPress Trac] #65248: Abilities API: add
 `wp_ability_invoked` action for pipeline-entry observers
In-Reply-To: <050.60981f9a1640d459a6a07bf1a6d6c922@wordpress.org>
References: <050.60981f9a1640d459a6a07bf1a6d6c922@wordpress.org>
Message-ID: <065.e01ca2c897455014f6b8fc821b000654@wordpress.org>

#65248: Abilities API: add `wp_ability_invoked` action for pipeline-entry observers
---------------------------+---------------------
 Reporter:  gziolo         |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  7.1
Component:  Abilities API  |     Version:  6.9
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+---------------------
Description changed by gziolo:

Old description:

> The execution lifecycle filters proposed in #64989 give the Abilities API
> four seams: `wp_pre_execute_ability`, `wp_before_execute_ability`,
> `wp_after_execute_ability`, and `wp_execute_ability_result`.
> `wp_before_execute_ability` fires after input normalization, validation,
> and the permission check — its contract is "execution is imminent." That
> contract is correct: rate-limiter, cached-response, and dry-run observers
> all rely on it not firing for calls that exit early.
>
> That leaves a gap for audit and snapshot observers, which need the
> opposite signal: "the pipeline received this invocation, regardless of
> outcome." They want a hook that fires for every call — approval-pending,
> rate-limited, cached, dry-run, and normal — so the audit row exists no
> matter how the call exits, and fires before normalization so the input is
> captured raw.
>
> == Proposal ==
>
> Add a `wp_ability_invoked` action at the top of `WP_Ability::execute()`,
> before `wp_pre_execute_ability` runs:
>
> {{{
> #!php
> do_action( 'wp_ability_invoked', $this->name, $input, $this );
> }}}
>
> The argument shape mirrors `wp_before_execute_ability` so observers can
> attach the same callback signature to both hooks. The past-tense verb
> communicates "entered the pipeline" without implying the call will
> execute.
>
> == Lifecycle position ==
>
> {{{
> execute( $input ) {
>     do_action( 'wp_ability_invoked', ... );      // new — every call, raw
> input
>     apply_filters( 'wp_pre_execute_ability', ... ); // existing — short-
> circuit seam
>     // normalize_input → validate_input → check_permissions
>     do_action( 'wp_before_execute_ability', ... ); // existing —
> execution imminent
>     // execute_callback
>     do_action( 'wp_after_execute_ability', ... );
>     return apply_filters( 'wp_execute_ability_result', ... );
> }
> }}}
>
> == Motivation ==
>
> Surfaced in
> [https://github.com/WordPress/ai/discussions/477#discussioncomment-16900589
> WordPress/ai#477]. The AbilityGuard plugin currently writes its audit row
> inline inside its `wp_pre_execute_ability` handler because no earlier
> signal exists, which conflates "build the approval envelope" with "record
> that an invocation happened." Landing `wp_ability_invoked` lets that work
> move to a dedicated observer listener and keeps the pre-execute handler
> focused on its short-circuit responsibility.
>
> The same signal benefits any observability layer that needs invocation
> entry counts independent of outcome (telemetry, rate-limit accounting
> that includes rejected calls, etc.).

New description:

 The execution lifecycle filters proposed in #64989 give the Abilities API
 four seams: `wp_pre_execute_ability`, `wp_before_execute_ability`,
 `wp_after_execute_ability`, and `wp_execute_ability_result`.
 `wp_before_execute_ability` fires after input normalization, validation,
 and the permission check — its contract is "execution is imminent." That
 contract is correct: rate-limiter, cached-response, and dry-run observers
 all rely on it not firing for calls that exit early.

 That leaves a gap for audit and snapshot observers, which need the
 opposite signal: "the pipeline received this invocation, regardless of
 outcome." They want a hook that fires for every call — approval-pending,
 rate-limited, cached, dry-run, and normal — so the audit row exists no
 matter how the call exits, and fires before normalization so the input is
 captured raw.

 == Proposal ==

 Add a `wp_ability_invoked` action at the top of `WP_Ability::execute()`,
 before `wp_pre_execute_ability` runs:

 {{{
 #!php
 do_action( 'wp_ability_invoked', $this->name, $input, $this );
 }}}

 The argument shape mirrors `wp_before_execute_ability` so observers can
 attach the same callback signature to both hooks. The past-tense verb
 communicates "entered the pipeline" without implying the call will
 execute.

 == Lifecycle position ==

 {{{
 execute( $input ) {
     do_action( 'wp_ability_invoked', ... );      // new — every call, raw
 input
     apply_filters( 'wp_pre_execute_ability', ... ); // existing — short-
 circuit seam
     // normalize_input → validate_input → check_permissions
     do_action( 'wp_before_execute_ability', ... ); // existing — execution
 imminent
     // execute_callback
     do_action( 'wp_after_execute_ability', ... );
     return apply_filters( 'wp_execute_ability_result', ... );
 }
 }}}

 == Motivation ==

 Surfaced in
 [https://github.com/WordPress/ai/discussions/477#discussioncomment-16900589
 WordPress/ai#477]. The AbilityGuard plugin currently writes its audit row
 inline inside its `wp_pre_execute_ability` handler because no earlier
 signal exists, which conflates "build the approval envelope" with "record
 that an invocation happened." Landing `wp_ability_invoked` lets that work
 move to a dedicated observer listener and keeps the pre-execute handler
 focused on its short-circuit responsibility.

 The same signal benefits any observability layer that needs invocation
 entry counts independent of outcome (telemetry, rate-limit accounting that
 includes rejected calls, etc.).

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65248#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 11:49:16 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 11:49:16 -0000
Subject: [wp-trac] [WordPress Trac] #65211: Font upload shows failure
 message but font is added to library
In-Reply-To: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
References: <051.80538e54c1cc6402cdc2203b3ec261e3@wordpress.org>
Message-ID: <066.c31969d216a8807df8c66b9ebe74f72e@wordpress.org>

#65211: Font upload shows failure message but font is added to library
-----------------------------+-------------------------
 Reporter:  369work          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |     Version:  trunk
 Severity:  normal           |  Resolution:  worksforme
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+-------------------------
Changes (by wildworks):

 * status:  new => closed
 * resolution:   => worksforme
 * milestone:  Awaiting Review =>


Comment:

 We are unable to identify which WordPress version this issue occurs in or
 the specific steps to reproduce it. Therefore, it is difficult to
 investigate this issue further. Let's close this for now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65211#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 12:06:41 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 12:06:41 -0000
Subject: [wp-trac] [WordPress Trac] #65249: View transition in wp-admin
 doesn't work on Firefox
Message-ID: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>

#65249: View transition in wp-admin doesn't work on Firefox
----------------------------+-----------------------------
 Reporter:  jsmansart       |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 I've tested the view transition in Chrome, Safari, Firefox and Firefox
 developer edition.

 Transitions are OK in Chrome and Safari.

 Transitions are not OK in both versions of Firefox.

 On Firefox, it's like there are no transitions at all, like it was in
 previous version of WordPress

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65249>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 12:07:53 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 12:07:53 -0000
Subject: [wp-trac] [WordPress Trac] #65249: View transition in wp-admin
 doesn't work on Firefox
In-Reply-To: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
References: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
Message-ID: <068.692ac025df281d1de866c0e5d419423a@wordpress.org>

#65249: View transition in wp-admin doesn't work on Firefox
----------------------------+------------------------------
 Reporter:  jsmansart       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------
Changes (by jsmansart):

 * Attachment "Enregistrement de l’écran 2026-05-15 à 14.07.24.mov" added.

 View transitions in Chrome

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65249>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 12:08:13 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 12:08:13 -0000
Subject: [wp-trac] [WordPress Trac] #65249: View transition in wp-admin
 doesn't work on Firefox
In-Reply-To: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
References: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
Message-ID: <068.324399d05bf09e3529316fbe19eeee4a@wordpress.org>

#65249: View transition in wp-admin doesn't work on Firefox
----------------------------+------------------------------
 Reporter:  jsmansart       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------
Changes (by jsmansart):

 * Attachment "Enregistrement de l’écran 2026-05-15 à 14.06.14.mov" added.

 View transitions in Firefox

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65249>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 12:09:14 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 12:09:14 -0000
Subject: [wp-trac] =?utf-8?q?=5BWordPress_Trac=5D_=2365250=3A_Mouse_cursor?=
 =?utf-8?q?_interaction_inconsistency_for_the_first_submenu_item_when_?=
 =?utf-8?q?=E2=80=9CCollapse_Menu=E2=80=9D_is_enabled_in_the_WP-Admin?=
Message-ID: <058.3044e04f60bbcddf6ec8dfae8e4e277d@wordpress.org>

#65250: Mouse cursor interaction inconsistency for the first submenu item when
“Collapse Menu” is enabled in the WP-Admin
-------------------------------------+-----------------------------
 Reporter:  mazharulrobeen           |      Owner:  (none)
     Type:  defect (bug)             |     Status:  new
 Priority:  normal                   |  Milestone:  Awaiting Review
Component:  General                  |    Version:  trunk
 Severity:  normal                   |   Keywords:
  Focuses:  ui, css, administration  |
-------------------------------------+-----------------------------
 **Summary**:
 When the “Collapse Menu” option is enabled in WP-Admin, the first submenu
 item under certain admin menu sections does not display a clickable cursor
 on hover, while the remaining submenu items behave correctly.

 **Description**:
 While testing the latest WordPress development version(7.0-RC4), I noticed
 an inconsistency in submenu hover interactions when the admin sidebar is
 collapsed using the “Collapse Menu” option.

 After collapsing the admin menu:

 Hover over a menu item that contains submenus (for example: Tools)
 The submenu panel appears as expected
 However, the first submenu item does not display the expected clickable
 pointer cursor behavior on hover
 The remaining submenu items correctly show the interactive hover/click
 cursor

 The submenu item itself still appears functional/clickable, but the cursor
 behavior creates a minor UI inconsistency and may affect perceived
 usability.

 This issue appears to affect only the first submenu item in the expanded
 flyout menu.

 Steps to Reproduce:

 Install the latest WordPress development version (7.0-RC4)
 Log in to WP-Admin
 Enable “Collapse Menu” from the admin sidebar
 Hover over a menu item with submenus (e.g. Tools)
 Move the mouse over the first submenu item
 Observe that the cursor does not behave consistently compared to the other
 submenu items

 **Video Demonstration**: https://www.youtube.com/watch?v=eg2lBtBrKHg
 (YouTube Unlisted URL)

 **Expected Behavior**:
 All submenu items should display consistent hover and clickable cursor
 behavior.

 **Actual Behavior**:
 The first submenu item does not show the expected interactive cursor
 behavior, while the remaining submenu items behave correctly.

 **Environment**:
 WordPress Version: Latest development version: (7.0-RC4)
 Browser: Chrome: Version 148.0.7778.168
 Operating System: macOS: 15.7.3
 Active Theme: Twenty Twenty-FiveVersion: 1.4
 Active Plugins: N/A

 **Additional Notes**:
 The issue appears to be UI/UX related rather than functional
 The submenu item remains clickable despite the cursor inconsistency
 The behavior appears specifically when the admin sidebar is collapsed
 Other submenu items in the same flyout menu appear unaffected

 Suggested Improvement:
 Review the hover/cursor interaction behavior for the first submenu item in
 collapsed admin sidebar flyout menus to ensure consistent UI feedback and
 interaction behavior across all submenu items.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65250>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 12:14:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 12:14:29 -0000
Subject: [wp-trac] [WordPress Trac] #65249: View transition in wp-admin
 doesn't work on Firefox
In-Reply-To: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
References: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
Message-ID: <068.aaff00cccddfb0d1c37f98c0d9067d2a@wordpress.org>

#65249: View transition in wp-admin doesn't work on Firefox
----------------------------+------------------------------
 Reporter:  jsmansart       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------

Comment (by wildworks):

 The View transition doesn't work in Firefox, but this is a known issue.
 See #64470.

 > The feature is [https://caniuse.com/cross-document-view-transitions now
 implemented] in all browsers, except for Firefox (see
 [https://bugzilla.mozilla.org/show_bug.cgi?id=1860854 Bugzilla 1860854]).
 Nevertheless, it is purely a progressive enhancement, the same as
 Speculative Loading, so Firefox users will not experience a degraded
 experience.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65249#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 12:24:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 12:24:25 -0000
Subject: [wp-trac] [WordPress Trac] #65249: View transition in wp-admin
 doesn't work on Firefox
In-Reply-To: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
References: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
Message-ID: <068.4f7b13f05fc01a01ba5b62733d532866@wordpress.org>

#65249: View transition in wp-admin doesn't work on Firefox
----------------------------+------------------------------
 Reporter:  jsmansart       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------

Comment (by jsmansart):

 OK, thanks @wildworks for the comment !

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65249#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 12:38:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 12:38:01 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2365250=3A_Mouse_curso?=
 =?utf-8?q?r_interaction_inconsistency_for_the_first_submenu_item_when_?=
 =?utf-8?q?=E2=80=9CCollapse_Menu=E2=80=9D_is_enabled_in_the_WP-Admin?=
In-Reply-To: <058.3044e04f60bbcddf6ec8dfae8e4e277d@wordpress.org>
References: <058.3044e04f60bbcddf6ec8dfae8e4e277d@wordpress.org>
Message-ID: <073.87ce83dd15832a1cdeea9c0413823b4d@wordpress.org>

#65250: Mouse cursor interaction inconsistency for the first submenu item when
“Collapse Menu” is enabled in the WP-Admin
----------------------------+--------------------------------------
 Reporter:  mazharulrobeen  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  General         |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  2nd-opinion     |     Focuses:  ui, css, administration
----------------------------+--------------------------------------
Changes (by sumitsingh):

 * keywords:   => 2nd-opinion


Comment:

 I have also noticed and issue detected for  menu cursor issue. Also top
 sub menu in more space under bottom.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65250#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 12:38:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 12:38:18 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2365250=3A_Mouse_curso?=
 =?utf-8?q?r_interaction_inconsistency_for_the_first_submenu_item_when_?=
 =?utf-8?q?=E2=80=9CCollapse_Menu=E2=80=9D_is_enabled_in_the_WP-Admin?=
In-Reply-To: <058.3044e04f60bbcddf6ec8dfae8e4e277d@wordpress.org>
References: <058.3044e04f60bbcddf6ec8dfae8e4e277d@wordpress.org>
Message-ID: <073.a505b4fde3dcaf2b337d9fcd3d6422dc@wordpress.org>

#65250: Mouse cursor interaction inconsistency for the first submenu item when
“Collapse Menu” is enabled in the WP-Admin
----------------------------+--------------------------------------
 Reporter:  mazharulrobeen  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  General         |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  ui, css, administration
----------------------------+--------------------------------------
Changes (by sumitsingh):

 * keywords:  2nd-opinion =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65250#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 12:38:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 12:38:34 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2365250=3A_Mouse_curso?=
 =?utf-8?q?r_interaction_inconsistency_for_the_first_submenu_item_when_?=
 =?utf-8?q?=E2=80=9CCollapse_Menu=E2=80=9D_is_enabled_in_the_WP-Admin?=
In-Reply-To: <058.3044e04f60bbcddf6ec8dfae8e4e277d@wordpress.org>
References: <058.3044e04f60bbcddf6ec8dfae8e4e277d@wordpress.org>
Message-ID: <073.771a362c3dccbff64c4c25ea30c99c65@wordpress.org>

#65250: Mouse cursor interaction inconsistency for the first submenu item when
“Collapse Menu” is enabled in the WP-Admin
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  (none)
  mazharulrobeen         |
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui, accessibility, css,
                         |  administration
-------------------------+-------------------------------------------------
Changes (by sumitsingh):

 * focuses:  ui, css, administration => ui, accessibility, css,
              administration


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65250#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 13:07:38 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 13:07:38 -0000
Subject: [wp-trac] [WordPress Trac] #64763: Admin reskin: Remove
 line-height from input elements
In-Reply-To: <053.33512a6ca36e38016e9b90c1ba2deee3@wordpress.org>
References: <053.33512a6ca36e38016e9b90c1ba2deee3@wordpress.org>
Message-ID: <068.f2e8f4d15c163c1c6446433751d0ee04@wordpress.org>

#64763: Admin reskin: Remove line-height from input elements
-------------------------------------------------+-------------------------
 Reporter:  wildworks                            |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  7.0
Component:  Administration                       |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  admin-reskin good-first-bug has-     |     Focuses:
  patch dev-reviewed                             |
-------------------------------------------------+-------------------------

Comment (by manhar):

 @wildworks and @audrasjb I still found this issue in my latest trunk.

 can we reopen this ticket again ? or can anyone please confirm this issue
 is still persist on latest environment or not ??

 I also attach one image below for reference :

 https://postimg.cc/V5czJmXX

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64763#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 13:57:34 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 13:57:34 -0000
Subject: [wp-trac] [WordPress Trac] #64908: PHP Warnings in Site Health
 information copy button
In-Reply-To: <049.8a122cee96642d87a2b7d0b6e8957776@wordpress.org>
References: <049.8a122cee96642d87a2b7d0b6e8957776@wordpress.org>
Message-ID: <064.1cb79685e62fce2ac922ec798bb8a9b3@wordpress.org>

#64908: PHP Warnings in Site Health information copy button
--------------------------+------------------------------------------------
 Reporter:  tunyk         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Site Health   |     Version:  6.9.4
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  administration, php-compatibility
--------------------------+------------------------------------------------
Changes (by tunyk):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Solved after a long search for the cause. The cause was in the Polylang
 code, but it was not possible to clarify it on this page and in the logs

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64908#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 14:29:06 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 14:29:06 -0000
Subject: [wp-trac] [WordPress Trac] #65251: Response from media library API
 query includes an empty array rather than an empty object
Message-ID: <060.19ac4687d79526b90198eb8d0949dc37@wordpress.org>

#65251: Response from media library API query includes an empty array rather than
an empty object
------------------------------+-----------------------------
 Reporter:  frankieandshadow  |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  REST API          |    Version:  6.9.4
 Severity:  normal            |   Keywords:
  Focuses:                    |
------------------------------+-----------------------------
 In the response to a media library query over the REST API, I am seeing
 that $wpimage->media_details->sizes is an empty array when there are no
 sizes, rather than an empty object (as a non-empty instance is an object).
 This discrepancy is inconsistent and breaks my recipient code. It's
 characteristic of json_encode being used on a keyed PHP array, when it
 can't tell the difference between keys and numeric indexes when empty.

 I asked claude.ai to locate the bug to make it easy for you to fix. It
 agreed with my diagnosis and said:

 File: wp-includes/rest-api/endpoints/class-wp-rest-attachments-
 controller.php

 Method: prepare_item_for_response()

 The bug: when wp_get_attachment_metadata() returns metadata with an empty
 sizes array (image too small for sub-sizes), the method populates
 `$data['media_details']` from that metadata but never explicitly sets
 `$data['media_details']['sizes']` to new stdClass. The `else {
 $data['media_details']['sizes'] = new stdClass; }` branch is only reached
 when $metadata itself is empty/falsy. The result is that sizes is either
 absent or an empty PHP array `[]` in the JSON output, rather than `{}`.

 Prior art: reference Trac #51393, which addressed a related inconsistency
 but didn't fix this code path.

 Your fix suggestion: initialise `$data['media_details']['sizes']` to `new
 stdClass` (or cast with (object)) before the loop that populates it, so
 the empty case is covered unconditionally.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65251>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 15:34:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 15:34:32 -0000
Subject: [wp-trac] [WordPress Trac] #65247: Black screen briefly appears
 on Connectors screen in WP 7.1-alpha
In-Reply-To: <054.9b8cad5288e4ed81cd23748aee013f5d@wordpress.org>
References: <054.9b8cad5288e4ed81cd23748aee013f5d@wordpress.org>
Message-ID: <069.2293671aaff10484d1865d02f43e5bcf@wordpress.org>

#65247: Black screen briefly appears on Connectors screen in WP 7.1-alpha
-------------------------+-------------------------------------------------
 Reporter:  sumitsingh   |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:               |     Version:  trunk
  Administration         |
 Severity:  normal       |  Resolution:
 Keywords:  has-         |     Focuses:  ui, administration, coding-
  screenshots            |  standards
-------------------------+-------------------------------------------------
Changes (by joedolson):

 * focuses:  ui, accessibility, administration, coding-standards => ui,
     administration, coding-standards


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65247#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 15:55:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 15:55:52 -0000
Subject: [wp-trac] [WordPress Trac] #64493: Plugin dependencies: better
 messaging or management of plugin active states
In-Reply-To: <053.bc55e50ba63bcf75ba42b40d3ded614f@wordpress.org>
References: <053.bc55e50ba63bcf75ba42b40d3ded614f@wordpress.org>
Message-ID: <068.4de7bdb7ad79939a1f258132adc0daf3@wordpress.org>

#64493: Plugin dependencies: better messaging or management of plugin active states
--------------------------+--------------------------------------
 Reporter:  joedolson     |       Owner:  joedolson
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Plugins       |     Version:  6.5
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  administration, ui-copy
--------------------------+--------------------------------------
Changes (by joedolson):

 * owner:  (none) => joedolson
 * status:  assigned => accepted


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64493#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 15:56:01 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 15:56:01 -0000
Subject: [wp-trac] [WordPress Trac] #64493: Plugin dependencies: better
 messaging or management of plugin active states
In-Reply-To: <053.bc55e50ba63bcf75ba42b40d3ded614f@wordpress.org>
References: <053.bc55e50ba63bcf75ba42b40d3ded614f@wordpress.org>
Message-ID: <068.34f31ea72c72966c38ca730974f8b45f@wordpress.org>

#64493: Plugin dependencies: better messaging or management of plugin active states
--------------------------+--------------------------------------
 Reporter:  joedolson     |       Owner:  joedolson
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  7.1
Component:  Plugins       |     Version:  6.5
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  administration, ui-copy
--------------------------+--------------------------------------
Changes (by joedolson):

 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64493#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 16:14:37 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 16:14:37 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2365250=3A_Mouse_curso?=
 =?utf-8?q?r_interaction_inconsistency_for_the_first_submenu_item_when_?=
 =?utf-8?q?=E2=80=9CCollapse_Menu=E2=80=9D_is_enabled_in_the_WP-Admin?=
In-Reply-To: <058.3044e04f60bbcddf6ec8dfae8e4e277d@wordpress.org>
References: <058.3044e04f60bbcddf6ec8dfae8e4e277d@wordpress.org>
Message-ID: <073.1171a8c1595bfdd6aaa286bc0c830cad@wordpress.org>

#65250: Mouse cursor interaction inconsistency for the first submenu item when
“Collapse Menu” is enabled in the WP-Admin
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  (none)
  mazharulrobeen         |
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:               |     Version:  5.9
  Administration         |
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui, accessibility, css,
                         |  administration
-------------------------+-------------------------------------------------
Changes (by sabernhardt):

 * version:  trunk => 5.9
 * component:  General => Administration


Comment:

 [51684] correctly removed the pointer cursor from //any// list item, but
 [https://github.com/WordPress/wordpress-
 develop/blob/b0990925d7d5f0ec7dfee2dcb28ec8b63541429e/src/js/_enqueues/admin/common.js#L870-L872
 common.js] makes the `.wp-submenu-head` item clickable.

 This could add the cursor rule for the special case, only when JS is
 enabled:
 {{{
 .js #adminmenu .wp-submenu .wp-submenu-head {
         cursor: pointer;
 }
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65250#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 18:03:02 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 18:03:02 -0000
Subject: [wp-trac] [WordPress Trac] #65223: Connectors plugin install
 flow does not show filesystem credentials form when FTP is required
In-Reply-To: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
References: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
Message-ID: <066.e6844e1c56b038100d47abab6381c9a3@wordpress.org>

#65223: Connectors plugin install flow does not show filesystem credentials form
when FTP is required
-------------------------------------+-------------------------------------
 Reporter:  ekamran                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  7.0
Component:  AI                       |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch has-test-    |     Focuses:  javascript,
  info                               |  administration
-------------------------------------+-------------------------------------

Comment (by westonruter):

 In order to test this out myself, I wanted to ensure that my wordpress-
 develop environment was configured with a live FTP filesystem method. I
 created a repo with instructions for how to set this up:
 https://github.com/westonruter/wordpress-develop-ftp-fs

 With that active, I can confirm when attempting to install the Open AI
 provider I get an error:

 > Failed to install plugin for OpenAI.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65223#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 18:11:25 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 18:11:25 -0000
Subject: [wp-trac] [WordPress Trac] #65223: Connectors plugin install
 flow does not show filesystem credentials form when FTP is required
In-Reply-To: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
References: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
Message-ID: <066.92121c29297b3374a425eae6916f0a83@wordpress.org>

#65223: Connectors plugin install flow does not show filesystem credentials form
when FTP is required
-------------------------------------+-------------------------------------
 Reporter:  ekamran                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  7.0
Component:  AI                       |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch has-test-    |     Focuses:  javascript,
  info                               |  administration
-------------------------------------+-------------------------------------

Comment (by ekamran):

 Thanks for confirming this.

 I re-tested this against WordPress 7.0-RC4 and can still reproduce the
 same behavior with `FS_METHOD` set to `ftpext`.

 In this setup, the standard Plugins > Add Plugin flow opens the expected
 “Connection Information” FTP credentials modal, but installing a provider
 from Settings > Connectors still stays on the Connectors screen and shows
 the generic error notice instead.

 I’m happy to help test a patch for this flow, or help with a Gutenberg-
 side fix if that would be useful.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65223#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 19:23:54 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 19:23:54 -0000
Subject: [wp-trac] [WordPress Trac] #65247: Black screen briefly appears
 on Connectors screen in WP 7.1-alpha
In-Reply-To: <054.9b8cad5288e4ed81cd23748aee013f5d@wordpress.org>
References: <054.9b8cad5288e4ed81cd23748aee013f5d@wordpress.org>
Message-ID: <069.6d5aec2414eab12f7d24b16a3795d25b@wordpress.org>

#65247: Black screen briefly appears on Connectors screen in WP 7.1-alpha
-------------------------+-------------------------------------------------
 Reporter:  sumitsingh   |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:               |     Version:  trunk
  Administration         |
 Severity:  normal       |  Resolution:
 Keywords:  has-         |     Focuses:  ui, administration, coding-
  screenshots            |  standards
-------------------------+-------------------------------------------------

Comment (by westonruter):

 This may be addressed by #65215 through preloading the REST API requests
 for the plugins used on the Connectors screen.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65247#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 19:43:21 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 19:43:21 -0000
Subject: [wp-trac] [WordPress Trac] #65223: Connectors plugin install
 flow does not show filesystem credentials form when FTP is required
In-Reply-To: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
References: <051.35f71798276e160eabbc4e30917c3c80@wordpress.org>
Message-ID: <066.15ec81bc3d745e1d37a49d3c22dd8deb@wordpress.org>

#65223: Connectors plugin install flow does not show filesystem credentials form
when FTP is required
---------------------------------+-----------------------------------------
 Reporter:  ekamran              |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  7.0
Component:  AI                   |     Version:  trunk
 Severity:  normal               |  Resolution:
 Keywords:  has-test-info has-   |     Focuses:  javascript, administration
  patch                          |
---------------------------------+-----------------------------------------
Changes (by westonruter):

 * keywords:  needs-patch has-test-info => has-test-info has-patch


Comment:

 @ekamran Thanks!

 I have created a Gutenberg PR (with the help of Claude):
 https://github.com/WordPress/gutenberg/pull/78367

 Please test.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65223#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 20:27:05 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 20:27:05 -0000
Subject: [wp-trac] [WordPress Trac] #64908: PHP Warnings in Site Health
 information copy button
In-Reply-To: <049.8a122cee96642d87a2b7d0b6e8957776@wordpress.org>
References: <049.8a122cee96642d87a2b7d0b6e8957776@wordpress.org>
Message-ID: <064.16206da06c095336fa269ffdb41c5d47@wordpress.org>

#64908: PHP Warnings in Site Health information copy button
--------------------------+------------------------------------------------
 Reporter:  tunyk         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Site Health   |     Version:  6.9.4
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  administration, php-compatibility
--------------------------+------------------------------------------------

Comment (by sabernhardt):

 The Polylang issue was also reported in a
 [https://wordpress.org/support/topic/php-8-5-warnings/ support forum
 topic], and it apparently was fixed a few weeks ago in the
 [https://github.com/polylang/polylang/issues/1860 GitHub repository].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64908#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 20:41:30 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 20:41:30 -0000
Subject: [wp-trac] [WordPress Trac] #65252: Test Progress:
 src/wp-admin/includes/ajax-actions.php
Message-ID: <051.a5cd04cd7aee8a3571dcfbfeb2bded30@wordpress.org>

#65252: Test Progress: src/wp-admin/includes/ajax-actions.php
----------------------------+-----------------------------
 Reporter:  pbearne         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  tests           |
----------------------------+-----------------------------
 == Test Progress: src/wp-admin/includes/ajax-actions.php ==

 This file tracks the status of unit tests for functions in ''src/wp-
 admin/includes/ajax-actions.php''.

 === Completed Functions (Tests Found) ===

 ||=Function=||=Status=||
 || wp_ajax_ajax_tag_search || ✅ Found
 || wp_ajax_wp_compression_test || ✅ Found
 || _wp_ajax_delete_comment_response || ✅ Found
 || wp_ajax_delete_comment || ✅ Found
 || wp_ajax_dim_comment || ✅ Found
 || wp_ajax_add_tag || ✅ Found
 || wp_ajax_get_comments || ✅ Found
 || wp_ajax_replyto_comment || ✅ Found
 || wp_ajax_edit_comment || ✅ Found
 || wp_ajax_add_meta || ✅ Found
 || wp_ajax_inline_save || ✅ Found
 || wp_ajax_image_editor || ✅ Found
 || wp_ajax_set_attachment_thumbnail || ✅ Found
 || wp_ajax_send_attachment_to_editor || ✅ Found
 || wp_ajax_heartbeat || ✅ Found
 || wp_ajax_crop_image || ✅ Found
 || wp_ajax_update_theme || ✅ Found
 || wp_ajax_update_plugin || ✅ Found
 || wp_ajax_delete_plugin || ✅ Found
 || wp_ajax_wp_privacy_export_personal_data || ✅ Found
 || wp_ajax_wp_privacy_erase_personal_data || ✅ Found
 || wp_ajax_parse_media_shortcode || ✅ Found


 === Missing Functions (Tests Not Found) ===

 These tests were moved to ''tests/phpunit/tests/admin/includes/ajax-
 actions'' in [https://core.trac.wordpress.org/ticket/65226 ticket 65226].

 || Function || Status || Ticket || Pull Request || Commited
 || wp_ajax_nopriv_heartbeat || created || ✅
 [65236](https://core.trac.wordpress.org/ticket/65236) || 65236-ajax-
 actions-wp_ajax_nopriv_heartbeat ||
 || wp_ajax_fetch_list || created || ✅
 [65237](https://core.trac.wordpress.org/ticket/65237) || 65237-ajax-
 actions-wp_ajax_fetch_list ||
 || wp_ajax_imgedit_preview || ❌ Missing ||  ||  ||
 || wp_ajax_oembed_cache || ❌ Missing ||  ||  ||
 || wp_ajax_autocomplete_user || ❌ Missing ||  ||  ||
 || wp_ajax_get_community_events || ❌ Missing ||  ||  ||
 || wp_ajax_dashboard_widgets || ❌ Missing ||  ||  ||
 || wp_ajax_logged_in || created || ✅
 [65242](https://core.trac.wordpress.org/ticket/65242) || 65242-ajax-
 actions-wp_ajax_logged_in ||
 || _wp_ajax_add_hierarchical_term || ❌ Missing ||  ||  ||
 || wp_ajax_delete_tag || ❌ Missing ||  ||  ||
 || wp_ajax_delete_link || ❌ Missing ||  ||  ||
 || wp_ajax_delete_meta || ❌ Missing ||  ||  ||
 || wp_ajax_delete_post || ❌ Missing ||  ||  ||
 || wp_ajax_trash_post || ❌ Missing ||  ||  ||
 || wp_ajax_untrash_post || ❌ Missing ||  ||  ||
 || wp_ajax_delete_page || ❌ Missing ||  ||  ||
 || wp_ajax_add_link_category || ❌ Missing ||  ||  ||
 || wp_ajax_get_tagcloud || ❌ Missing ||  ||  ||
 || wp_ajax_add_menu_item || ❌ Missing ||  ||  ||
 || wp_ajax_add_user || ❌ Missing ||  ||  ||
 || wp_ajax_closed_postboxes || ❌ Missing ||  ||  ||
 || wp_ajax_hidden_columns || ❌ Missing ||  ||  ||
 || wp_ajax_update_welcome_panel || ❌ Missing ||  ||  ||
 || wp_ajax_menu_get_metabox || ❌ Missing ||  ||  ||
 || wp_ajax_wp_link_ajax || ❌ Missing ||  ||  ||
 || wp_ajax_menu_locations_save || ❌ Missing ||  ||  ||
 || wp_ajax_meta_box_order || ❌ Missing ||  ||  ||
 || wp_ajax_menu_quick_search || ❌ Missing ||  ||  ||
 || wp_ajax_get_permalink || ❌ Missing ||  ||  ||
 || wp_ajax_sample_permalink || ❌ Missing ||  ||  ||
 || wp_ajax_inline_save_tax || ❌ Missing ||  ||  ||
 || wp_ajax_find_posts || ❌ Missing ||  ||  ||
 || wp_ajax_widgets_order || ❌ Missing ||  ||  ||
 || wp_ajax_save_widget || ❌ Missing ||  ||  ||
 || wp_ajax_update_widget || ❌ Missing ||  ||  ||
 || wp_ajax_delete_inactive_widgets || ❌ Missing ||  ||  ||
 || wp_ajax_media_create_image_subsizes || ❌ Missing ||  ||  ||
 || wp_ajax_upload_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_set_post_thumbnail || ❌ Missing ||  ||  ||
 || wp_ajax_get_post_thumbnail_html || ❌ Missing ||  ||  ||
 || wp_ajax_date_format || created || ✅
 [65225](https://core.trac.wordpress.org/ticket/65225) || [65225-ajax-
 date_format](https://github.com/WordPress/wordpress-develop/pull/11811) ||
 || wp_ajax_time_format || created || ✅
 [65228](https://core.trac.wordpress.org/ticket/65228) || [65228-ajax-
 time_format](https://github.com/WordPress/wordpress-develop/pull/11814) ||
 || wp_ajax_wp_fullscreen_save_post || ❌ Missing ||  ||  ||
 || wp_ajax_wp_remove_post_lock || ❌ Missing ||  ||  ||
 || wp_ajax_dismiss_wp_pointer || ❌ Missing ||  ||  ||
 || wp_ajax_get_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_query_attachments || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment_compat || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment_order || ❌ Missing ||  ||  ||
 || wp_ajax_send_link_to_editor || ❌ Missing ||  ||  ||
 || wp_ajax_get_revision_diffs || ❌ Missing ||  ||  ||
 || wp_ajax_save_user_color_scheme || ❌ Missing ||  ||  ||
 || wp_ajax_query_themes || ❌ Missing ||  ||  ||
 || wp_ajax_parse_embed || ❌ Missing ||  ||  ||
 || wp_ajax_destroy_sessions || ❌ Missing ||  ||  ||
 || wp_ajax_generate_password || ❌ Missing ||  ||  ||
 || wp_ajax_nopriv_generate_password || ❌ Missing ||  ||  ||
 || wp_ajax_save_wporg_username || ❌ Missing ||  ||  ||
 || wp_ajax_install_theme || ❌ Missing ||  ||  ||
 || wp_ajax_delete_theme || ❌ Missing ||  ||  ||
 || wp_ajax_install_plugin || ❌ Missing ||  ||  ||
 || wp_ajax_activate_plugin || ❌ Missing ||  ||  ||
 || wp_ajax_search_plugins || ❌ Missing ||  ||  ||
 || wp_ajax_search_install_plugins || ❌ Missing ||  ||  ||
 || wp_ajax_edit_theme_plugin_file || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_dotorg_communication || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_background_updates || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_loopback_requests || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_site_status_result || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_get_sizes || ❌ Missing ||  ||  ||
 || wp_ajax_rest_nonce || created || ✅
 [65243](https://core.trac.wordpress.org/ticket/65243) || 65243-ajax-
 actions-wp_ajax_rest_nonce ||
 || wp_ajax_toggle_auto_updates || ❌ Missing ||  ||  ||
 || wp_ajax_send_password_reset || ❌ Missing ||  ||  ||

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65252>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 20:42:18 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 20:42:18 -0000
Subject: [wp-trac] [WordPress Trac] #65252: Test Progress:
 src/wp-admin/includes/ajax-actions.php
In-Reply-To: <051.a5cd04cd7aee8a3571dcfbfeb2bded30@wordpress.org>
References: <051.a5cd04cd7aee8a3571dcfbfeb2bded30@wordpress.org>
Message-ID: <066.3daf1bb0de3bfb78bc051aab108bc653@wordpress.org>

#65252: Test Progress: src/wp-admin/includes/ajax-actions.php
----------------------------+------------------------------
 Reporter:  pbearne         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  tests
----------------------------+------------------------------
Description changed by pbearne:

Old description:

> == Test Progress: src/wp-admin/includes/ajax-actions.php ==
>
> This file tracks the status of unit tests for functions in ''src/wp-
> admin/includes/ajax-actions.php''.
>
> === Completed Functions (Tests Found) ===
>
> ||=Function=||=Status=||
> || wp_ajax_ajax_tag_search || ✅ Found
> || wp_ajax_wp_compression_test || ✅ Found
> || _wp_ajax_delete_comment_response || ✅ Found
> || wp_ajax_delete_comment || ✅ Found
> || wp_ajax_dim_comment || ✅ Found
> || wp_ajax_add_tag || ✅ Found
> || wp_ajax_get_comments || ✅ Found
> || wp_ajax_replyto_comment || ✅ Found
> || wp_ajax_edit_comment || ✅ Found
> || wp_ajax_add_meta || ✅ Found
> || wp_ajax_inline_save || ✅ Found
> || wp_ajax_image_editor || ✅ Found
> || wp_ajax_set_attachment_thumbnail || ✅ Found
> || wp_ajax_send_attachment_to_editor || ✅ Found
> || wp_ajax_heartbeat || ✅ Found
> || wp_ajax_crop_image || ✅ Found
> || wp_ajax_update_theme || ✅ Found
> || wp_ajax_update_plugin || ✅ Found
> || wp_ajax_delete_plugin || ✅ Found
> || wp_ajax_wp_privacy_export_personal_data || ✅ Found
> || wp_ajax_wp_privacy_erase_personal_data || ✅ Found
> || wp_ajax_parse_media_shortcode || ✅ Found
>

> === Missing Functions (Tests Not Found) ===
>
> These tests were moved to ''tests/phpunit/tests/admin/includes/ajax-
> actions'' in [https://core.trac.wordpress.org/ticket/65226 ticket 65226].
>
> || Function || Status || Ticket || Pull Request || Commited
> || wp_ajax_nopriv_heartbeat || created || ✅
> [65236](https://core.trac.wordpress.org/ticket/65236) || 65236-ajax-
> actions-wp_ajax_nopriv_heartbeat ||
> || wp_ajax_fetch_list || created || ✅
> [65237](https://core.trac.wordpress.org/ticket/65237) || 65237-ajax-
> actions-wp_ajax_fetch_list ||
> || wp_ajax_imgedit_preview || ❌ Missing ||  ||  ||
> || wp_ajax_oembed_cache || ❌ Missing ||  ||  ||
> || wp_ajax_autocomplete_user || ❌ Missing ||  ||  ||
> || wp_ajax_get_community_events || ❌ Missing ||  ||  ||
> || wp_ajax_dashboard_widgets || ❌ Missing ||  ||  ||
> || wp_ajax_logged_in || created || ✅
> [65242](https://core.trac.wordpress.org/ticket/65242) || 65242-ajax-
> actions-wp_ajax_logged_in ||
> || _wp_ajax_add_hierarchical_term || ❌ Missing ||  ||  ||
> || wp_ajax_delete_tag || ❌ Missing ||  ||  ||
> || wp_ajax_delete_link || ❌ Missing ||  ||  ||
> || wp_ajax_delete_meta || ❌ Missing ||  ||  ||
> || wp_ajax_delete_post || ❌ Missing ||  ||  ||
> || wp_ajax_trash_post || ❌ Missing ||  ||  ||
> || wp_ajax_untrash_post || ❌ Missing ||  ||  ||
> || wp_ajax_delete_page || ❌ Missing ||  ||  ||
> || wp_ajax_add_link_category || ❌ Missing ||  ||  ||
> || wp_ajax_get_tagcloud || ❌ Missing ||  ||  ||
> || wp_ajax_add_menu_item || ❌ Missing ||  ||  ||
> || wp_ajax_add_user || ❌ Missing ||  ||  ||
> || wp_ajax_closed_postboxes || ❌ Missing ||  ||  ||
> || wp_ajax_hidden_columns || ❌ Missing ||  ||  ||
> || wp_ajax_update_welcome_panel || ❌ Missing ||  ||  ||
> || wp_ajax_menu_get_metabox || ❌ Missing ||  ||  ||
> || wp_ajax_wp_link_ajax || ❌ Missing ||  ||  ||
> || wp_ajax_menu_locations_save || ❌ Missing ||  ||  ||
> || wp_ajax_meta_box_order || ❌ Missing ||  ||  ||
> || wp_ajax_menu_quick_search || ❌ Missing ||  ||  ||
> || wp_ajax_get_permalink || ❌ Missing ||  ||  ||
> || wp_ajax_sample_permalink || ❌ Missing ||  ||  ||
> || wp_ajax_inline_save_tax || ❌ Missing ||  ||  ||
> || wp_ajax_find_posts || ❌ Missing ||  ||  ||
> || wp_ajax_widgets_order || ❌ Missing ||  ||  ||
> || wp_ajax_save_widget || ❌ Missing ||  ||  ||
> || wp_ajax_update_widget || ❌ Missing ||  ||  ||
> || wp_ajax_delete_inactive_widgets || ❌ Missing ||  ||  ||
> || wp_ajax_media_create_image_subsizes || ❌ Missing ||  ||  ||
> || wp_ajax_upload_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_set_post_thumbnail || ❌ Missing ||  ||  ||
> || wp_ajax_get_post_thumbnail_html || ❌ Missing ||  ||  ||
> || wp_ajax_date_format || created || ✅
> [65225](https://core.trac.wordpress.org/ticket/65225) || [65225-ajax-
> date_format](https://github.com/WordPress/wordpress-develop/pull/11811)
> ||
> || wp_ajax_time_format || created || ✅
> [65228](https://core.trac.wordpress.org/ticket/65228) || [65228-ajax-
> time_format](https://github.com/WordPress/wordpress-develop/pull/11814)
> ||
> || wp_ajax_wp_fullscreen_save_post || ❌ Missing ||  ||  ||
> || wp_ajax_wp_remove_post_lock || ❌ Missing ||  ||  ||
> || wp_ajax_dismiss_wp_pointer || ❌ Missing ||  ||  ||
> || wp_ajax_get_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_query_attachments || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment_compat || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment_order || ❌ Missing ||  ||  ||
> || wp_ajax_send_link_to_editor || ❌ Missing ||  ||  ||
> || wp_ajax_get_revision_diffs || ❌ Missing ||  ||  ||
> || wp_ajax_save_user_color_scheme || ❌ Missing ||  ||  ||
> || wp_ajax_query_themes || ❌ Missing ||  ||  ||
> || wp_ajax_parse_embed || ❌ Missing ||  ||  ||
> || wp_ajax_destroy_sessions || ❌ Missing ||  ||  ||
> || wp_ajax_generate_password || ❌ Missing ||  ||  ||
> || wp_ajax_nopriv_generate_password || ❌ Missing ||  ||  ||
> || wp_ajax_save_wporg_username || ❌ Missing ||  ||  ||
> || wp_ajax_install_theme || ❌ Missing ||  ||  ||
> || wp_ajax_delete_theme || ❌ Missing ||  ||  ||
> || wp_ajax_install_plugin || ❌ Missing ||  ||  ||
> || wp_ajax_activate_plugin || ❌ Missing ||  ||  ||
> || wp_ajax_search_plugins || ❌ Missing ||  ||  ||
> || wp_ajax_search_install_plugins || ❌ Missing ||  ||  ||
> || wp_ajax_edit_theme_plugin_file || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_dotorg_communication || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_background_updates || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_loopback_requests || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_site_status_result || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_get_sizes || ❌ Missing ||  ||  ||
> || wp_ajax_rest_nonce || created || ✅
> [65243](https://core.trac.wordpress.org/ticket/65243) || 65243-ajax-
> actions-wp_ajax_rest_nonce ||
> || wp_ajax_toggle_auto_updates || ❌ Missing ||  ||  ||
> || wp_ajax_send_password_reset || ❌ Missing ||  ||  ||

New description:

 == Test Progress: src/wp-admin/includes/ajax-actions.php ==

 This file tracks the status of unit tests for functions in ''src/wp-
 admin/includes/ajax-actions.php''.

 === Completed Functions (Tests Found) ===

 ||=Function=||=Status=||
 || wp_ajax_ajax_tag_search || ✅ Found
 || wp_ajax_wp_compression_test || ✅ Found
 || _wp_ajax_delete_comment_response || ✅ Found
 || wp_ajax_delete_comment || ✅ Found
 || wp_ajax_dim_comment || ✅ Found
 || wp_ajax_add_tag || ✅ Found
 || wp_ajax_get_comments || ✅ Found
 || wp_ajax_replyto_comment || ✅ Found
 || wp_ajax_edit_comment || ✅ Found
 || wp_ajax_add_meta || ✅ Found
 || wp_ajax_inline_save || ✅ Found
 || wp_ajax_image_editor || ✅ Found
 || wp_ajax_set_attachment_thumbnail || ✅ Found
 || wp_ajax_send_attachment_to_editor || ✅ Found
 || wp_ajax_heartbeat || ✅ Found
 || wp_ajax_crop_image || ✅ Found
 || wp_ajax_update_theme || ✅ Found
 || wp_ajax_update_plugin || ✅ Found
 || wp_ajax_delete_plugin || ✅ Found
 || wp_ajax_wp_privacy_export_personal_data || ✅ Found
 || wp_ajax_wp_privacy_erase_personal_data || ✅ Found
 || wp_ajax_parse_media_shortcode || ✅ Found

 These tests were moved to ''tests/phpunit/tests/admin/includes/ajax-
 actions'' in [https://core.trac.wordpress.org/ticket/65226 ticket 65226].


 === Missing Functions (Tests Not Found) ===

 || Function || Status || Ticket || Pull Request || Commited
 || wp_ajax_nopriv_heartbeat || created || ✅
 [65236](https://core.trac.wordpress.org/ticket/65236) || 65236-ajax-
 actions-wp_ajax_nopriv_heartbeat ||
 || wp_ajax_fetch_list || created || ✅
 [65237](https://core.trac.wordpress.org/ticket/65237) || 65237-ajax-
 actions-wp_ajax_fetch_list ||
 || wp_ajax_imgedit_preview || ❌ Missing ||  ||  ||
 || wp_ajax_oembed_cache || ❌ Missing ||  ||  ||
 || wp_ajax_autocomplete_user || ❌ Missing ||  ||  ||
 || wp_ajax_get_community_events || ❌ Missing ||  ||  ||
 || wp_ajax_dashboard_widgets || ❌ Missing ||  ||  ||
 || wp_ajax_logged_in || created || ✅
 [65242](https://core.trac.wordpress.org/ticket/65242) || 65242-ajax-
 actions-wp_ajax_logged_in ||
 || _wp_ajax_add_hierarchical_term || ❌ Missing ||  ||  ||
 || wp_ajax_delete_tag || ❌ Missing ||  ||  ||
 || wp_ajax_delete_link || ❌ Missing ||  ||  ||
 || wp_ajax_delete_meta || ❌ Missing ||  ||  ||
 || wp_ajax_delete_post || ❌ Missing ||  ||  ||
 || wp_ajax_trash_post || ❌ Missing ||  ||  ||
 || wp_ajax_untrash_post || ❌ Missing ||  ||  ||
 || wp_ajax_delete_page || ❌ Missing ||  ||  ||
 || wp_ajax_add_link_category || ❌ Missing ||  ||  ||
 || wp_ajax_get_tagcloud || ❌ Missing ||  ||  ||
 || wp_ajax_add_menu_item || ❌ Missing ||  ||  ||
 || wp_ajax_add_user || ❌ Missing ||  ||  ||
 || wp_ajax_closed_postboxes || ❌ Missing ||  ||  ||
 || wp_ajax_hidden_columns || ❌ Missing ||  ||  ||
 || wp_ajax_update_welcome_panel || ❌ Missing ||  ||  ||
 || wp_ajax_menu_get_metabox || ❌ Missing ||  ||  ||
 || wp_ajax_wp_link_ajax || ❌ Missing ||  ||  ||
 || wp_ajax_menu_locations_save || ❌ Missing ||  ||  ||
 || wp_ajax_meta_box_order || ❌ Missing ||  ||  ||
 || wp_ajax_menu_quick_search || ❌ Missing ||  ||  ||
 || wp_ajax_get_permalink || ❌ Missing ||  ||  ||
 || wp_ajax_sample_permalink || ❌ Missing ||  ||  ||
 || wp_ajax_inline_save_tax || ❌ Missing ||  ||  ||
 || wp_ajax_find_posts || ❌ Missing ||  ||  ||
 || wp_ajax_widgets_order || ❌ Missing ||  ||  ||
 || wp_ajax_save_widget || ❌ Missing ||  ||  ||
 || wp_ajax_update_widget || ❌ Missing ||  ||  ||
 || wp_ajax_delete_inactive_widgets || ❌ Missing ||  ||  ||
 || wp_ajax_media_create_image_subsizes || ❌ Missing ||  ||  ||
 || wp_ajax_upload_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_set_post_thumbnail || ❌ Missing ||  ||  ||
 || wp_ajax_get_post_thumbnail_html || ❌ Missing ||  ||  ||
 || wp_ajax_date_format || created || ✅
 [65225](https://core.trac.wordpress.org/ticket/65225) || [65225-ajax-
 date_format](https://github.com/WordPress/wordpress-develop/pull/11811) ||
 || wp_ajax_time_format || created || ✅
 [65228](https://core.trac.wordpress.org/ticket/65228) || [65228-ajax-
 time_format](https://github.com/WordPress/wordpress-develop/pull/11814) ||
 || wp_ajax_wp_fullscreen_save_post || ❌ Missing ||  ||  ||
 || wp_ajax_wp_remove_post_lock || ❌ Missing ||  ||  ||
 || wp_ajax_dismiss_wp_pointer || ❌ Missing ||  ||  ||
 || wp_ajax_get_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_query_attachments || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment_compat || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment_order || ❌ Missing ||  ||  ||
 || wp_ajax_send_link_to_editor || ❌ Missing ||  ||  ||
 || wp_ajax_get_revision_diffs || ❌ Missing ||  ||  ||
 || wp_ajax_save_user_color_scheme || ❌ Missing ||  ||  ||
 || wp_ajax_query_themes || ❌ Missing ||  ||  ||
 || wp_ajax_parse_embed || ❌ Missing ||  ||  ||
 || wp_ajax_destroy_sessions || ❌ Missing ||  ||  ||
 || wp_ajax_generate_password || ❌ Missing ||  ||  ||
 || wp_ajax_nopriv_generate_password || ❌ Missing ||  ||  ||
 || wp_ajax_save_wporg_username || ❌ Missing ||  ||  ||
 || wp_ajax_install_theme || ❌ Missing ||  ||  ||
 || wp_ajax_delete_theme || ❌ Missing ||  ||  ||
 || wp_ajax_install_plugin || ❌ Missing ||  ||  ||
 || wp_ajax_activate_plugin || ❌ Missing ||  ||  ||
 || wp_ajax_search_plugins || ❌ Missing ||  ||  ||
 || wp_ajax_search_install_plugins || ❌ Missing ||  ||  ||
 || wp_ajax_edit_theme_plugin_file || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_dotorg_communication || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_background_updates || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_loopback_requests || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_site_status_result || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_get_sizes || ❌ Missing ||  ||  ||
 || wp_ajax_rest_nonce || created || ✅
 [65243](https://core.trac.wordpress.org/ticket/65243) || 65243-ajax-
 actions-wp_ajax_rest_nonce ||
 || wp_ajax_toggle_auto_updates || ❌ Missing ||  ||  ||
 || wp_ajax_send_password_reset || ❌ Missing ||  ||  ||

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65252#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 21:04:49 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 21:04:49 -0000
Subject: [wp-trac] [WordPress Trac] #65252: Test Progress:
 src/wp-admin/includes/ajax-actions.php
In-Reply-To: <051.a5cd04cd7aee8a3571dcfbfeb2bded30@wordpress.org>
References: <051.a5cd04cd7aee8a3571dcfbfeb2bded30@wordpress.org>
Message-ID: <066.5b0331a20e104aa08ea3cc9f64d4f8d0@wordpress.org>

#65252: Test Progress: src/wp-admin/includes/ajax-actions.php
----------------------------+------------------------------
 Reporter:  pbearne         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  tests
----------------------------+------------------------------
Changes (by pbearne):

 * keywords:  has-patch has-unit-tests =>


Old description:

> == Test Progress: src/wp-admin/includes/ajax-actions.php ==
>
> This file tracks the status of unit tests for functions in ''src/wp-
> admin/includes/ajax-actions.php''.
>
> === Completed Functions (Tests Found) ===
>
> ||=Function=||=Status=||
> || wp_ajax_ajax_tag_search || ✅ Found
> || wp_ajax_wp_compression_test || ✅ Found
> || _wp_ajax_delete_comment_response || ✅ Found
> || wp_ajax_delete_comment || ✅ Found
> || wp_ajax_dim_comment || ✅ Found
> || wp_ajax_add_tag || ✅ Found
> || wp_ajax_get_comments || ✅ Found
> || wp_ajax_replyto_comment || ✅ Found
> || wp_ajax_edit_comment || ✅ Found
> || wp_ajax_add_meta || ✅ Found
> || wp_ajax_inline_save || ✅ Found
> || wp_ajax_image_editor || ✅ Found
> || wp_ajax_set_attachment_thumbnail || ✅ Found
> || wp_ajax_send_attachment_to_editor || ✅ Found
> || wp_ajax_heartbeat || ✅ Found
> || wp_ajax_crop_image || ✅ Found
> || wp_ajax_update_theme || ✅ Found
> || wp_ajax_update_plugin || ✅ Found
> || wp_ajax_delete_plugin || ✅ Found
> || wp_ajax_wp_privacy_export_personal_data || ✅ Found
> || wp_ajax_wp_privacy_erase_personal_data || ✅ Found
> || wp_ajax_parse_media_shortcode || ✅ Found
>
> These tests were moved to ''tests/phpunit/tests/admin/includes/ajax-
> actions'' in [https://core.trac.wordpress.org/ticket/65226 ticket 65226].
>

> === Missing Functions (Tests Not Found) ===
>
> || Function || Status || Ticket || Pull Request || Commited
> || wp_ajax_nopriv_heartbeat || created || ✅
> [65236](https://core.trac.wordpress.org/ticket/65236) || 65236-ajax-
> actions-wp_ajax_nopriv_heartbeat ||
> || wp_ajax_fetch_list || created || ✅
> [65237](https://core.trac.wordpress.org/ticket/65237) || 65237-ajax-
> actions-wp_ajax_fetch_list ||
> || wp_ajax_imgedit_preview || ❌ Missing ||  ||  ||
> || wp_ajax_oembed_cache || ❌ Missing ||  ||  ||
> || wp_ajax_autocomplete_user || ❌ Missing ||  ||  ||
> || wp_ajax_get_community_events || ❌ Missing ||  ||  ||
> || wp_ajax_dashboard_widgets || ❌ Missing ||  ||  ||
> || wp_ajax_logged_in || created || ✅
> [65242](https://core.trac.wordpress.org/ticket/65242) || 65242-ajax-
> actions-wp_ajax_logged_in ||
> || _wp_ajax_add_hierarchical_term || ❌ Missing ||  ||  ||
> || wp_ajax_delete_tag || ❌ Missing ||  ||  ||
> || wp_ajax_delete_link || ❌ Missing ||  ||  ||
> || wp_ajax_delete_meta || ❌ Missing ||  ||  ||
> || wp_ajax_delete_post || ❌ Missing ||  ||  ||
> || wp_ajax_trash_post || ❌ Missing ||  ||  ||
> || wp_ajax_untrash_post || ❌ Missing ||  ||  ||
> || wp_ajax_delete_page || ❌ Missing ||  ||  ||
> || wp_ajax_add_link_category || ❌ Missing ||  ||  ||
> || wp_ajax_get_tagcloud || ❌ Missing ||  ||  ||
> || wp_ajax_add_menu_item || ❌ Missing ||  ||  ||
> || wp_ajax_add_user || ❌ Missing ||  ||  ||
> || wp_ajax_closed_postboxes || ❌ Missing ||  ||  ||
> || wp_ajax_hidden_columns || ❌ Missing ||  ||  ||
> || wp_ajax_update_welcome_panel || ❌ Missing ||  ||  ||
> || wp_ajax_menu_get_metabox || ❌ Missing ||  ||  ||
> || wp_ajax_wp_link_ajax || ❌ Missing ||  ||  ||
> || wp_ajax_menu_locations_save || ❌ Missing ||  ||  ||
> || wp_ajax_meta_box_order || ❌ Missing ||  ||  ||
> || wp_ajax_menu_quick_search || ❌ Missing ||  ||  ||
> || wp_ajax_get_permalink || ❌ Missing ||  ||  ||
> || wp_ajax_sample_permalink || ❌ Missing ||  ||  ||
> || wp_ajax_inline_save_tax || ❌ Missing ||  ||  ||
> || wp_ajax_find_posts || ❌ Missing ||  ||  ||
> || wp_ajax_widgets_order || ❌ Missing ||  ||  ||
> || wp_ajax_save_widget || ❌ Missing ||  ||  ||
> || wp_ajax_update_widget || ❌ Missing ||  ||  ||
> || wp_ajax_delete_inactive_widgets || ❌ Missing ||  ||  ||
> || wp_ajax_media_create_image_subsizes || ❌ Missing ||  ||  ||
> || wp_ajax_upload_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_set_post_thumbnail || ❌ Missing ||  ||  ||
> || wp_ajax_get_post_thumbnail_html || ❌ Missing ||  ||  ||
> || wp_ajax_date_format || created || ✅
> [65225](https://core.trac.wordpress.org/ticket/65225) || [65225-ajax-
> date_format](https://github.com/WordPress/wordpress-develop/pull/11811)
> ||
> || wp_ajax_time_format || created || ✅
> [65228](https://core.trac.wordpress.org/ticket/65228) || [65228-ajax-
> time_format](https://github.com/WordPress/wordpress-develop/pull/11814)
> ||
> || wp_ajax_wp_fullscreen_save_post || ❌ Missing ||  ||  ||
> || wp_ajax_wp_remove_post_lock || ❌ Missing ||  ||  ||
> || wp_ajax_dismiss_wp_pointer || ❌ Missing ||  ||  ||
> || wp_ajax_get_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_query_attachments || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment_compat || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment_order || ❌ Missing ||  ||  ||
> || wp_ajax_send_link_to_editor || ❌ Missing ||  ||  ||
> || wp_ajax_get_revision_diffs || ❌ Missing ||  ||  ||
> || wp_ajax_save_user_color_scheme || ❌ Missing ||  ||  ||
> || wp_ajax_query_themes || ❌ Missing ||  ||  ||
> || wp_ajax_parse_embed || ❌ Missing ||  ||  ||
> || wp_ajax_destroy_sessions || ❌ Missing ||  ||  ||
> || wp_ajax_generate_password || ❌ Missing ||  ||  ||
> || wp_ajax_nopriv_generate_password || ❌ Missing ||  ||  ||
> || wp_ajax_save_wporg_username || ❌ Missing ||  ||  ||
> || wp_ajax_install_theme || ❌ Missing ||  ||  ||
> || wp_ajax_delete_theme || ❌ Missing ||  ||  ||
> || wp_ajax_install_plugin || ❌ Missing ||  ||  ||
> || wp_ajax_activate_plugin || ❌ Missing ||  ||  ||
> || wp_ajax_search_plugins || ❌ Missing ||  ||  ||
> || wp_ajax_search_install_plugins || ❌ Missing ||  ||  ||
> || wp_ajax_edit_theme_plugin_file || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_dotorg_communication || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_background_updates || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_loopback_requests || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_site_status_result || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_get_sizes || ❌ Missing ||  ||  ||
> || wp_ajax_rest_nonce || created || ✅
> [65243](https://core.trac.wordpress.org/ticket/65243) || 65243-ajax-
> actions-wp_ajax_rest_nonce ||
> || wp_ajax_toggle_auto_updates || ❌ Missing ||  ||  ||
> || wp_ajax_send_password_reset || ❌ Missing ||  ||  ||

New description:

 == Test Progress: src/wp-admin/includes/ajax-actions.php ==

 This file tracks the status of unit tests for functions in ''src/wp-
 admin/includes/ajax-actions.php''.

 === Completed Functions (Tests Found) ===

 ||=Function=||=Status=||
 || wp_ajax_ajax_tag_search || ✅ Found
 || wp_ajax_wp_compression_test || ✅ Found
 || _wp_ajax_delete_comment_response || ✅ Found
 || wp_ajax_delete_comment || ✅ Found
 || wp_ajax_dim_comment || ✅ Found
 || wp_ajax_add_tag || ✅ Found
 || wp_ajax_get_comments || ✅ Found
 || wp_ajax_replyto_comment || ✅ Found
 || wp_ajax_edit_comment || ✅ Found
 || wp_ajax_add_meta || ✅ Found
 || wp_ajax_inline_save || ✅ Found
 || wp_ajax_image_editor || ✅ Found
 || wp_ajax_set_attachment_thumbnail || ✅ Found
 || wp_ajax_send_attachment_to_editor || ✅ Found
 || wp_ajax_heartbeat || ✅ Found
 || wp_ajax_crop_image || ✅ Found
 || wp_ajax_update_theme || ✅ Found
 || wp_ajax_update_plugin || ✅ Found
 || wp_ajax_delete_plugin || ✅ Found
 || wp_ajax_wp_privacy_export_personal_data || ✅ Found
 || wp_ajax_wp_privacy_erase_personal_data || ✅ Found
 || wp_ajax_parse_media_shortcode || ✅ Found

 These tests were moved to ''tests/phpunit/tests/admin/includes/ajax-
 actions'' in [https://core.trac.wordpress.org/ticket/65226 ticket 65226].


 === Missing Functions (Tests Not Found) ===

 || Function || Status || Ticket || Pull Request || Commited
 || wp_ajax_nopriv_heartbeat || created || ✅
 [65236](https://core.trac.wordpress.org/ticket/65236) || 65236-ajax-
 actions-wp_ajax_nopriv_heartbeat ||
 || wp_ajax_fetch_list || created || ✅
 [65237](https://core.trac.wordpress.org/ticket/65237) || 65237-ajax-
 actions-wp_ajax_fetch_list ||
 || wp_ajax_imgedit_preview || created ||
 [65252](https://core.trac.wordpress.org/ticket/65252) | ||
 [11845](https://github.com/WordPress/wordpress-develop/pull/11845) | ||
 || wp_ajax_oembed_cache || ❌ Missing ||  ||  ||
 || wp_ajax_autocomplete_user || ❌ Missing ||  ||  ||
 || wp_ajax_get_community_events || ❌ Missing ||  ||  ||
 || wp_ajax_dashboard_widgets || ❌ Missing ||  ||  ||
 || wp_ajax_logged_in || created || ✅
 [65242](https://core.trac.wordpress.org/ticket/65242) || 65242-ajax-
 actions-wp_ajax_logged_in ||
 || _wp_ajax_add_hierarchical_term || ❌ Missing ||  ||  ||
 || wp_ajax_delete_tag || ❌ Missing ||  ||  ||
 || wp_ajax_delete_link || ❌ Missing ||  ||  ||
 || wp_ajax_delete_meta || ❌ Missing ||  ||  ||
 || wp_ajax_delete_post || ❌ Missing ||  ||  ||
 || wp_ajax_trash_post || ❌ Missing ||  ||  ||
 || wp_ajax_untrash_post || ❌ Missing ||  ||  ||
 || wp_ajax_delete_page || ❌ Missing ||  ||  ||
 || wp_ajax_add_link_category || ❌ Missing ||  ||  ||
 || wp_ajax_get_tagcloud || ❌ Missing ||  ||  ||
 || wp_ajax_add_menu_item || ❌ Missing ||  ||  ||
 || wp_ajax_add_user || ❌ Missing ||  ||  ||
 || wp_ajax_closed_postboxes || ❌ Missing ||  ||  ||
 || wp_ajax_hidden_columns || ❌ Missing ||  ||  ||
 || wp_ajax_update_welcome_panel || ❌ Missing ||  ||  ||
 || wp_ajax_menu_get_metabox || ❌ Missing ||  ||  ||
 || wp_ajax_wp_link_ajax || ❌ Missing ||  ||  ||
 || wp_ajax_menu_locations_save || ❌ Missing ||  ||  ||
 || wp_ajax_meta_box_order || ❌ Missing ||  ||  ||
 || wp_ajax_menu_quick_search || ❌ Missing ||  ||  ||
 || wp_ajax_get_permalink || ❌ Missing ||  ||  ||
 || wp_ajax_sample_permalink || ❌ Missing ||  ||  ||
 || wp_ajax_inline_save_tax || ❌ Missing ||  ||  ||
 || wp_ajax_find_posts || ❌ Missing ||  ||  ||
 || wp_ajax_widgets_order || ❌ Missing ||  ||  ||
 || wp_ajax_save_widget || ❌ Missing ||  ||  ||
 || wp_ajax_update_widget || ❌ Missing ||  ||  ||
 || wp_ajax_delete_inactive_widgets || ❌ Missing ||  ||  ||
 || wp_ajax_media_create_image_subsizes || ❌ Missing ||  ||  ||
 || wp_ajax_upload_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_set_post_thumbnail || ❌ Missing ||  ||  ||
 || wp_ajax_get_post_thumbnail_html || ❌ Missing ||  ||  ||
 || wp_ajax_date_format || created || ✅
 [65225](https://core.trac.wordpress.org/ticket/65225) || [65225-ajax-
 date_format](https://github.com/WordPress/wordpress-develop/pull/11811) ||
 || wp_ajax_time_format || created || ✅
 [65228](https://core.trac.wordpress.org/ticket/65228) || [65228-ajax-
 time_format](https://github.com/WordPress/wordpress-develop/pull/11814) ||
 || wp_ajax_wp_fullscreen_save_post || ❌ Missing ||  ||  ||
 || wp_ajax_wp_remove_post_lock || ❌ Missing ||  ||  ||
 || wp_ajax_dismiss_wp_pointer || ❌ Missing ||  ||  ||
 || wp_ajax_get_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_query_attachments || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment_compat || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment_order || ❌ Missing ||  ||  ||
 || wp_ajax_send_link_to_editor || ❌ Missing ||  ||  ||
 || wp_ajax_get_revision_diffs || ❌ Missing ||  ||  ||
 || wp_ajax_save_user_color_scheme || ❌ Missing ||  ||  ||
 || wp_ajax_query_themes || ❌ Missing ||  ||  ||
 || wp_ajax_parse_embed || ❌ Missing ||  ||  ||
 || wp_ajax_destroy_sessions || ❌ Missing ||  ||  ||
 || wp_ajax_generate_password || ❌ Missing ||  ||  ||
 || wp_ajax_nopriv_generate_password || ❌ Missing ||  ||  ||
 || wp_ajax_save_wporg_username || ❌ Missing ||  ||  ||
 || wp_ajax_install_theme || ❌ Missing ||  ||  ||
 || wp_ajax_delete_theme || ❌ Missing ||  ||  ||
 || wp_ajax_install_plugin || ❌ Missing ||  ||  ||
 || wp_ajax_activate_plugin || ❌ Missing ||  ||  ||
 || wp_ajax_search_plugins || ❌ Missing ||  ||  ||
 || wp_ajax_search_install_plugins || ❌ Missing ||  ||  ||
 || wp_ajax_edit_theme_plugin_file || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_dotorg_communication || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_background_updates || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_loopback_requests || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_site_status_result || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_get_sizes || ❌ Missing ||  ||  ||
 || wp_ajax_rest_nonce || created || ✅
 [65243](https://core.trac.wordpress.org/ticket/65243) || 65243-ajax-
 actions-wp_ajax_rest_nonce ||
 || wp_ajax_toggle_auto_updates || ❌ Missing ||  ||  ||
 || wp_ajax_send_password_reset || ❌ Missing ||  ||  ||

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65252#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 21:10:32 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 21:10:32 -0000
Subject: [wp-trac] [WordPress Trac] #65252: Test Progress:
 src/wp-admin/includes/ajax-actions.php
In-Reply-To: <051.a5cd04cd7aee8a3571dcfbfeb2bded30@wordpress.org>
References: <051.a5cd04cd7aee8a3571dcfbfeb2bded30@wordpress.org>
Message-ID: <066.0cba8ff6413c37c645737ce9b83e5224@wordpress.org>

#65252: Test Progress: src/wp-admin/includes/ajax-actions.php
----------------------------+------------------------------
 Reporter:  pbearne         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  tests
----------------------------+------------------------------
Changes (by pbearne):

 * keywords:  has-patch has-unit-tests =>


Old description:

> == Test Progress: src/wp-admin/includes/ajax-actions.php ==
>
> This file tracks the status of unit tests for functions in ''src/wp-
> admin/includes/ajax-actions.php''.
>
> === Completed Functions (Tests Found) ===
>
> ||=Function=||=Status=||
> || wp_ajax_ajax_tag_search || ✅ Found
> || wp_ajax_wp_compression_test || ✅ Found
> || _wp_ajax_delete_comment_response || ✅ Found
> || wp_ajax_delete_comment || ✅ Found
> || wp_ajax_dim_comment || ✅ Found
> || wp_ajax_add_tag || ✅ Found
> || wp_ajax_get_comments || ✅ Found
> || wp_ajax_replyto_comment || ✅ Found
> || wp_ajax_edit_comment || ✅ Found
> || wp_ajax_add_meta || ✅ Found
> || wp_ajax_inline_save || ✅ Found
> || wp_ajax_image_editor || ✅ Found
> || wp_ajax_set_attachment_thumbnail || ✅ Found
> || wp_ajax_send_attachment_to_editor || ✅ Found
> || wp_ajax_heartbeat || ✅ Found
> || wp_ajax_crop_image || ✅ Found
> || wp_ajax_update_theme || ✅ Found
> || wp_ajax_update_plugin || ✅ Found
> || wp_ajax_delete_plugin || ✅ Found
> || wp_ajax_wp_privacy_export_personal_data || ✅ Found
> || wp_ajax_wp_privacy_erase_personal_data || ✅ Found
> || wp_ajax_parse_media_shortcode || ✅ Found
>
> These tests were moved to ''tests/phpunit/tests/admin/includes/ajax-
> actions'' in [https://core.trac.wordpress.org/ticket/65226 ticket 65226].
>

> === Missing Functions (Tests Not Found) ===
>
> || Function || Status || Ticket || Pull Request || Commited
> || wp_ajax_nopriv_heartbeat || created || ✅
> [65236](https://core.trac.wordpress.org/ticket/65236) || 65236-ajax-
> actions-wp_ajax_nopriv_heartbeat ||
> || wp_ajax_fetch_list || created || ✅
> [65237](https://core.trac.wordpress.org/ticket/65237) || 65237-ajax-
> actions-wp_ajax_fetch_list ||
> || wp_ajax_imgedit_preview || created ||
> [65252](https://core.trac.wordpress.org/ticket/65252) | ||
> [11845](https://github.com/WordPress/wordpress-develop/pull/11845) | ||
> || wp_ajax_oembed_cache || ❌ Missing ||  ||  ||
> || wp_ajax_autocomplete_user || ❌ Missing ||  ||  ||
> || wp_ajax_get_community_events || ❌ Missing ||  ||  ||
> || wp_ajax_dashboard_widgets || ❌ Missing ||  ||  ||
> || wp_ajax_logged_in || created || ✅
> [65242](https://core.trac.wordpress.org/ticket/65242) || 65242-ajax-
> actions-wp_ajax_logged_in ||
> || _wp_ajax_add_hierarchical_term || ❌ Missing ||  ||  ||
> || wp_ajax_delete_tag || ❌ Missing ||  ||  ||
> || wp_ajax_delete_link || ❌ Missing ||  ||  ||
> || wp_ajax_delete_meta || ❌ Missing ||  ||  ||
> || wp_ajax_delete_post || ❌ Missing ||  ||  ||
> || wp_ajax_trash_post || ❌ Missing ||  ||  ||
> || wp_ajax_untrash_post || ❌ Missing ||  ||  ||
> || wp_ajax_delete_page || ❌ Missing ||  ||  ||
> || wp_ajax_add_link_category || ❌ Missing ||  ||  ||
> || wp_ajax_get_tagcloud || ❌ Missing ||  ||  ||
> || wp_ajax_add_menu_item || ❌ Missing ||  ||  ||
> || wp_ajax_add_user || ❌ Missing ||  ||  ||
> || wp_ajax_closed_postboxes || ❌ Missing ||  ||  ||
> || wp_ajax_hidden_columns || ❌ Missing ||  ||  ||
> || wp_ajax_update_welcome_panel || ❌ Missing ||  ||  ||
> || wp_ajax_menu_get_metabox || ❌ Missing ||  ||  ||
> || wp_ajax_wp_link_ajax || ❌ Missing ||  ||  ||
> || wp_ajax_menu_locations_save || ❌ Missing ||  ||  ||
> || wp_ajax_meta_box_order || ❌ Missing ||  ||  ||
> || wp_ajax_menu_quick_search || ❌ Missing ||  ||  ||
> || wp_ajax_get_permalink || ❌ Missing ||  ||  ||
> || wp_ajax_sample_permalink || ❌ Missing ||  ||  ||
> || wp_ajax_inline_save_tax || ❌ Missing ||  ||  ||
> || wp_ajax_find_posts || ❌ Missing ||  ||  ||
> || wp_ajax_widgets_order || ❌ Missing ||  ||  ||
> || wp_ajax_save_widget || ❌ Missing ||  ||  ||
> || wp_ajax_update_widget || ❌ Missing ||  ||  ||
> || wp_ajax_delete_inactive_widgets || ❌ Missing ||  ||  ||
> || wp_ajax_media_create_image_subsizes || ❌ Missing ||  ||  ||
> || wp_ajax_upload_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_set_post_thumbnail || ❌ Missing ||  ||  ||
> || wp_ajax_get_post_thumbnail_html || ❌ Missing ||  ||  ||
> || wp_ajax_date_format || created || ✅
> [65225](https://core.trac.wordpress.org/ticket/65225) || [65225-ajax-
> date_format](https://github.com/WordPress/wordpress-develop/pull/11811)
> ||
> || wp_ajax_time_format || created || ✅
> [65228](https://core.trac.wordpress.org/ticket/65228) || [65228-ajax-
> time_format](https://github.com/WordPress/wordpress-develop/pull/11814)
> ||
> || wp_ajax_wp_fullscreen_save_post || ❌ Missing ||  ||  ||
> || wp_ajax_wp_remove_post_lock || ❌ Missing ||  ||  ||
> || wp_ajax_dismiss_wp_pointer || ❌ Missing ||  ||  ||
> || wp_ajax_get_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_query_attachments || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment_compat || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment_order || ❌ Missing ||  ||  ||
> || wp_ajax_send_link_to_editor || ❌ Missing ||  ||  ||
> || wp_ajax_get_revision_diffs || ❌ Missing ||  ||  ||
> || wp_ajax_save_user_color_scheme || ❌ Missing ||  ||  ||
> || wp_ajax_query_themes || ❌ Missing ||  ||  ||
> || wp_ajax_parse_embed || ❌ Missing ||  ||  ||
> || wp_ajax_destroy_sessions || ❌ Missing ||  ||  ||
> || wp_ajax_generate_password || ❌ Missing ||  ||  ||
> || wp_ajax_nopriv_generate_password || ❌ Missing ||  ||  ||
> || wp_ajax_save_wporg_username || ❌ Missing ||  ||  ||
> || wp_ajax_install_theme || ❌ Missing ||  ||  ||
> || wp_ajax_delete_theme || ❌ Missing ||  ||  ||
> || wp_ajax_install_plugin || ❌ Missing ||  ||  ||
> || wp_ajax_activate_plugin || ❌ Missing ||  ||  ||
> || wp_ajax_search_plugins || ❌ Missing ||  ||  ||
> || wp_ajax_search_install_plugins || ❌ Missing ||  ||  ||
> || wp_ajax_edit_theme_plugin_file || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_dotorg_communication || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_background_updates || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_loopback_requests || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_site_status_result || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_get_sizes || ❌ Missing ||  ||  ||
> || wp_ajax_rest_nonce || created || ✅
> [65243](https://core.trac.wordpress.org/ticket/65243) || 65243-ajax-
> actions-wp_ajax_rest_nonce ||
> || wp_ajax_toggle_auto_updates || ❌ Missing ||  ||  ||
> || wp_ajax_send_password_reset || ❌ Missing ||  ||  ||

New description:

 == Test Progress: src/wp-admin/includes/ajax-actions.php ==

 This file tracks the status of unit tests for functions in ''src/wp-
 admin/includes/ajax-actions.php''.

 === Completed Functions (Tests Found) ===

 ||=Function=||=Status=||
 || wp_ajax_ajax_tag_search || ✅ Found
 || wp_ajax_wp_compression_test || ✅ Found
 || _wp_ajax_delete_comment_response || ✅ Found
 || wp_ajax_delete_comment || ✅ Found
 || wp_ajax_dim_comment || ✅ Found
 || wp_ajax_add_tag || ✅ Found
 || wp_ajax_get_comments || ✅ Found
 || wp_ajax_replyto_comment || ✅ Found
 || wp_ajax_edit_comment || ✅ Found
 || wp_ajax_add_meta || ✅ Found
 || wp_ajax_inline_save || ✅ Found
 || wp_ajax_image_editor || ✅ Found
 || wp_ajax_set_attachment_thumbnail || ✅ Found
 || wp_ajax_send_attachment_to_editor || ✅ Found
 || wp_ajax_heartbeat || ✅ Found
 || wp_ajax_crop_image || ✅ Found
 || wp_ajax_update_theme || ✅ Found
 || wp_ajax_update_plugin || ✅ Found
 || wp_ajax_delete_plugin || ✅ Found
 || wp_ajax_wp_privacy_export_personal_data || ✅ Found
 || wp_ajax_wp_privacy_erase_personal_data || ✅ Found
 || wp_ajax_parse_media_shortcode || ✅ Found

 These tests were moved to ''tests/phpunit/tests/admin/includes/ajax-
 actions'' in [https://core.trac.wordpress.org/ticket/65226 ticket 65226].


 === Missing Functions (Tests Not Found) ===

 || Function || Status || Ticket || Pull Request || Commited
 || wp_ajax_nopriv_heartbeat || created || ✅
 [65236](https://core.trac.wordpress.org/ticket/65236) || 65236-ajax-
 actions-wp_ajax_nopriv_heartbeat ||
 || wp_ajax_fetch_list || created || ✅
 [65237](https://core.trac.wordpress.org/ticket/65237) || 65237-ajax-
 actions-wp_ajax_fetch_list ||
 || wp_ajax_imgedit_preview || created ||
 [65252](https://core.trac.wordpress.org/ticket/65252) | ||
 [11845](https://github.com/WordPress/wordpress-develop/pull/11845) | ||
 || wp_ajax_oembed_cache ||  created ||
 [65252](https://core.trac.wordpress.org/ticket/65252) | ||
 [11846](https://github.com/WordPress/wordpress-develop/pull/11846) | ||
 || wp_ajax_autocomplete_user || ❌ Missing ||  ||  ||
 || wp_ajax_get_community_events || ❌ Missing ||  ||  ||
 || wp_ajax_dashboard_widgets || ❌ Missing ||  ||  ||
 || wp_ajax_logged_in || created || ✅
 [65242](https://core.trac.wordpress.org/ticket/65242) || 65242-ajax-
 actions-wp_ajax_logged_in ||
 || _wp_ajax_add_hierarchical_term || ❌ Missing ||  ||  ||
 || wp_ajax_delete_tag || ❌ Missing ||  ||  ||
 || wp_ajax_delete_link || ❌ Missing ||  ||  ||
 || wp_ajax_delete_meta || ❌ Missing ||  ||  ||
 || wp_ajax_delete_post || ❌ Missing ||  ||  ||
 || wp_ajax_trash_post || ❌ Missing ||  ||  ||
 || wp_ajax_untrash_post || ❌ Missing ||  ||  ||
 || wp_ajax_delete_page || ❌ Missing ||  ||  ||
 || wp_ajax_add_link_category || ❌ Missing ||  ||  ||
 || wp_ajax_get_tagcloud || ❌ Missing ||  ||  ||
 || wp_ajax_add_menu_item || ❌ Missing ||  ||  ||
 || wp_ajax_add_user || ❌ Missing ||  ||  ||
 || wp_ajax_closed_postboxes || ❌ Missing ||  ||  ||
 || wp_ajax_hidden_columns || ❌ Missing ||  ||  ||
 || wp_ajax_update_welcome_panel || ❌ Missing ||  ||  ||
 || wp_ajax_menu_get_metabox || ❌ Missing ||  ||  ||
 || wp_ajax_wp_link_ajax || ❌ Missing ||  ||  ||
 || wp_ajax_menu_locations_save || ❌ Missing ||  ||  ||
 || wp_ajax_meta_box_order || ❌ Missing ||  ||  ||
 || wp_ajax_menu_quick_search || ❌ Missing ||  ||  ||
 || wp_ajax_get_permalink || ❌ Missing ||  ||  ||
 || wp_ajax_sample_permalink || ❌ Missing ||  ||  ||
 || wp_ajax_inline_save_tax || ❌ Missing ||  ||  ||
 || wp_ajax_find_posts || ❌ Missing ||  ||  ||
 || wp_ajax_widgets_order || ❌ Missing ||  ||  ||
 || wp_ajax_save_widget || ❌ Missing ||  ||  ||
 || wp_ajax_update_widget || ❌ Missing ||  ||  ||
 || wp_ajax_delete_inactive_widgets || ❌ Missing ||  ||  ||
 || wp_ajax_media_create_image_subsizes || ❌ Missing ||  ||  ||
 || wp_ajax_upload_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_set_post_thumbnail || ❌ Missing ||  ||  ||
 || wp_ajax_get_post_thumbnail_html || ❌ Missing ||  ||  ||
 || wp_ajax_date_format || created || ✅
 [65225](https://core.trac.wordpress.org/ticket/65225) || [65225-ajax-
 date_format](https://github.com/WordPress/wordpress-develop/pull/11811) ||
 || wp_ajax_time_format || created || ✅
 [65228](https://core.trac.wordpress.org/ticket/65228) || [65228-ajax-
 time_format](https://github.com/WordPress/wordpress-develop/pull/11814) ||
 || wp_ajax_wp_fullscreen_save_post || ❌ Missing ||  ||  ||
 || wp_ajax_wp_remove_post_lock || ❌ Missing ||  ||  ||
 || wp_ajax_dismiss_wp_pointer || ❌ Missing ||  ||  ||
 || wp_ajax_get_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_query_attachments || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment_compat || ❌ Missing ||  ||  ||
 || wp_ajax_save_attachment_order || ❌ Missing ||  ||  ||
 || wp_ajax_send_link_to_editor || ❌ Missing ||  ||  ||
 || wp_ajax_get_revision_diffs || ❌ Missing ||  ||  ||
 || wp_ajax_save_user_color_scheme || ❌ Missing ||  ||  ||
 || wp_ajax_query_themes || ❌ Missing ||  ||  ||
 || wp_ajax_parse_embed || ❌ Missing ||  ||  ||
 || wp_ajax_destroy_sessions || ❌ Missing ||  ||  ||
 || wp_ajax_generate_password || ❌ Missing ||  ||  ||
 || wp_ajax_nopriv_generate_password || ❌ Missing ||  ||  ||
 || wp_ajax_save_wporg_username || ❌ Missing ||  ||  ||
 || wp_ajax_install_theme || ❌ Missing ||  ||  ||
 || wp_ajax_delete_theme || ❌ Missing ||  ||  ||
 || wp_ajax_install_plugin || ❌ Missing ||  ||  ||
 || wp_ajax_activate_plugin || ❌ Missing ||  ||  ||
 || wp_ajax_search_plugins || ❌ Missing ||  ||  ||
 || wp_ajax_search_install_plugins || ❌ Missing ||  ||  ||
 || wp_ajax_edit_theme_plugin_file || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_dotorg_communication || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_background_updates || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_loopback_requests || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_site_status_result || ❌ Missing ||  ||  ||
 || wp_ajax_health_check_get_sizes || ❌ Missing ||  ||  ||
 || wp_ajax_rest_nonce || created || ✅
 [65243](https://core.trac.wordpress.org/ticket/65243) || 65243-ajax-
 actions-wp_ajax_rest_nonce ||
 || wp_ajax_toggle_auto_updates || ❌ Missing ||  ||  ||
 || wp_ajax_send_password_reset || ❌ Missing ||  ||  ||

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65252#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 21:41:27 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 21:41:27 -0000
Subject: [wp-trac] [WordPress Trac] #65245: Accented or special
 characters issue
In-Reply-To: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
References: <057.0dc186de7c671176f0e5387284158ec6@wordpress.org>
Message-ID: <072.e6a39f8a39dc55ae02a180571649ef84@wordpress.org>

#65245: Accented or special characters issue
-------------------------------------------------+-------------------------
 Reporter:  clementpolito                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots needs-patch needs-   |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------

Comment (by jonsurrell):

 Agree with @ocean90, this belongs on meta trac.

 [https://meta.trac.wordpress.org/browser/sites/trunk/api.wordpress.org/public_html/core/credits
 /wp-credits.php?annotate=blame#L386 This line looks suspicious.] It hasn't
 changed in a long time, but changes to underlying language data or
 functionality could plausibly produce different results. In particular,
 listing `JIS` before `UTF-8` in the from encoding seems problematic. Maybe
 the conversion can be dropped completely if the data is already UTF-8.

 {{{#!php
 <?php
 $raw = 'é1234567890';
 echo mb_convert_encoding($raw, 'UTF-8', 'ASCII, JIS, UTF-8, Windows-1252,
 ISO-8859-1') . "\n";
 // ﾃｩ1234567890
 echo mb_convert_encoding($raw, 'UTF-8', 'ASCII, UTF-8, JIS, Windows-1252,
 ISO-8859-1') . "\n";
 // é1234567890
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65245#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 22:06:09 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 22:06:09 -0000
Subject: [wp-trac] [WordPress Trac] #65252: Test Progress:
 src/wp-admin/includes/ajax-actions.php
In-Reply-To: <051.a5cd04cd7aee8a3571dcfbfeb2bded30@wordpress.org>
References: <051.a5cd04cd7aee8a3571dcfbfeb2bded30@wordpress.org>
Message-ID: <066.2870e106656c891c62243edf7a9d2d34@wordpress.org>

#65252: Test Progress: src/wp-admin/includes/ajax-actions.php
----------------------------+------------------------------
 Reporter:  pbearne         |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  tests
----------------------------+------------------------------

Old description:

> == Test Progress: src/wp-admin/includes/ajax-actions.php ==
>
> This file tracks the status of unit tests for functions in ''src/wp-
> admin/includes/ajax-actions.php''.
>
> === Completed Functions (Tests Found) ===
>
> ||=Function=||=Status=||
> || wp_ajax_ajax_tag_search || ✅ Found
> || wp_ajax_wp_compression_test || ✅ Found
> || _wp_ajax_delete_comment_response || ✅ Found
> || wp_ajax_delete_comment || ✅ Found
> || wp_ajax_dim_comment || ✅ Found
> || wp_ajax_add_tag || ✅ Found
> || wp_ajax_get_comments || ✅ Found
> || wp_ajax_replyto_comment || ✅ Found
> || wp_ajax_edit_comment || ✅ Found
> || wp_ajax_add_meta || ✅ Found
> || wp_ajax_inline_save || ✅ Found
> || wp_ajax_image_editor || ✅ Found
> || wp_ajax_set_attachment_thumbnail || ✅ Found
> || wp_ajax_send_attachment_to_editor || ✅ Found
> || wp_ajax_heartbeat || ✅ Found
> || wp_ajax_crop_image || ✅ Found
> || wp_ajax_update_theme || ✅ Found
> || wp_ajax_update_plugin || ✅ Found
> || wp_ajax_delete_plugin || ✅ Found
> || wp_ajax_wp_privacy_export_personal_data || ✅ Found
> || wp_ajax_wp_privacy_erase_personal_data || ✅ Found
> || wp_ajax_parse_media_shortcode || ✅ Found
>
> These tests were moved to ''tests/phpunit/tests/admin/includes/ajax-
> actions'' in [https://core.trac.wordpress.org/ticket/65226 ticket 65226].
>

> === Missing Functions (Tests Not Found) ===
>
> || Function || Status || Ticket || Pull Request || Commited
> || wp_ajax_nopriv_heartbeat || created || ✅
> [65236](https://core.trac.wordpress.org/ticket/65236) || 65236-ajax-
> actions-wp_ajax_nopriv_heartbeat ||
> || wp_ajax_fetch_list || created || ✅
> [65237](https://core.trac.wordpress.org/ticket/65237) || 65237-ajax-
> actions-wp_ajax_fetch_list ||
> || wp_ajax_imgedit_preview || created ||
> [65252](https://core.trac.wordpress.org/ticket/65252) | ||
> [11845](https://github.com/WordPress/wordpress-develop/pull/11845) | ||
> || wp_ajax_oembed_cache ||  created ||
> [65252](https://core.trac.wordpress.org/ticket/65252) | ||
> [11846](https://github.com/WordPress/wordpress-develop/pull/11846) | ||
> || wp_ajax_autocomplete_user || ❌ Missing ||  ||  ||
> || wp_ajax_get_community_events || ❌ Missing ||  ||  ||
> || wp_ajax_dashboard_widgets || ❌ Missing ||  ||  ||
> || wp_ajax_logged_in || created || ✅
> [65242](https://core.trac.wordpress.org/ticket/65242) || 65242-ajax-
> actions-wp_ajax_logged_in ||
> || _wp_ajax_add_hierarchical_term || ❌ Missing ||  ||  ||
> || wp_ajax_delete_tag || ❌ Missing ||  ||  ||
> || wp_ajax_delete_link || ❌ Missing ||  ||  ||
> || wp_ajax_delete_meta || ❌ Missing ||  ||  ||
> || wp_ajax_delete_post || ❌ Missing ||  ||  ||
> || wp_ajax_trash_post || ❌ Missing ||  ||  ||
> || wp_ajax_untrash_post || ❌ Missing ||  ||  ||
> || wp_ajax_delete_page || ❌ Missing ||  ||  ||
> || wp_ajax_add_link_category || ❌ Missing ||  ||  ||
> || wp_ajax_get_tagcloud || ❌ Missing ||  ||  ||
> || wp_ajax_add_menu_item || ❌ Missing ||  ||  ||
> || wp_ajax_add_user || ❌ Missing ||  ||  ||
> || wp_ajax_closed_postboxes || ❌ Missing ||  ||  ||
> || wp_ajax_hidden_columns || ❌ Missing ||  ||  ||
> || wp_ajax_update_welcome_panel || ❌ Missing ||  ||  ||
> || wp_ajax_menu_get_metabox || ❌ Missing ||  ||  ||
> || wp_ajax_wp_link_ajax || ❌ Missing ||  ||  ||
> || wp_ajax_menu_locations_save || ❌ Missing ||  ||  ||
> || wp_ajax_meta_box_order || ❌ Missing ||  ||  ||
> || wp_ajax_menu_quick_search || ❌ Missing ||  ||  ||
> || wp_ajax_get_permalink || ❌ Missing ||  ||  ||
> || wp_ajax_sample_permalink || ❌ Missing ||  ||  ||
> || wp_ajax_inline_save_tax || ❌ Missing ||  ||  ||
> || wp_ajax_find_posts || ❌ Missing ||  ||  ||
> || wp_ajax_widgets_order || ❌ Missing ||  ||  ||
> || wp_ajax_save_widget || ❌ Missing ||  ||  ||
> || wp_ajax_update_widget || ❌ Missing ||  ||  ||
> || wp_ajax_delete_inactive_widgets || ❌ Missing ||  ||  ||
> || wp_ajax_media_create_image_subsizes || ❌ Missing ||  ||  ||
> || wp_ajax_upload_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_set_post_thumbnail || ❌ Missing ||  ||  ||
> || wp_ajax_get_post_thumbnail_html || ❌ Missing ||  ||  ||
> || wp_ajax_date_format || created || ✅
> [65225](https://core.trac.wordpress.org/ticket/65225) || [65225-ajax-
> date_format](https://github.com/WordPress/wordpress-develop/pull/11811)
> ||
> || wp_ajax_time_format || created || ✅
> [65228](https://core.trac.wordpress.org/ticket/65228) || [65228-ajax-
> time_format](https://github.com/WordPress/wordpress-develop/pull/11814)
> ||
> || wp_ajax_wp_fullscreen_save_post || ❌ Missing ||  ||  ||
> || wp_ajax_wp_remove_post_lock || ❌ Missing ||  ||  ||
> || wp_ajax_dismiss_wp_pointer || ❌ Missing ||  ||  ||
> || wp_ajax_get_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_query_attachments || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment_compat || ❌ Missing ||  ||  ||
> || wp_ajax_save_attachment_order || ❌ Missing ||  ||  ||
> || wp_ajax_send_link_to_editor || ❌ Missing ||  ||  ||
> || wp_ajax_get_revision_diffs || ❌ Missing ||  ||  ||
> || wp_ajax_save_user_color_scheme || ❌ Missing ||  ||  ||
> || wp_ajax_query_themes || ❌ Missing ||  ||  ||
> || wp_ajax_parse_embed || ❌ Missing ||  ||  ||
> || wp_ajax_destroy_sessions || ❌ Missing ||  ||  ||
> || wp_ajax_generate_password || ❌ Missing ||  ||  ||
> || wp_ajax_nopriv_generate_password || ❌ Missing ||  ||  ||
> || wp_ajax_save_wporg_username || ❌ Missing ||  ||  ||
> || wp_ajax_install_theme || ❌ Missing ||  ||  ||
> || wp_ajax_delete_theme || ❌ Missing ||  ||  ||
> || wp_ajax_install_plugin || ❌ Missing ||  ||  ||
> || wp_ajax_activate_plugin || ❌ Missing ||  ||  ||
> || wp_ajax_search_plugins || ❌ Missing ||  ||  ||
> || wp_ajax_search_install_plugins || ❌ Missing ||  ||  ||
> || wp_ajax_edit_theme_plugin_file || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_dotorg_communication || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_background_updates || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_loopback_requests || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_site_status_result || ❌ Missing ||  ||  ||
> || wp_ajax_health_check_get_sizes || ❌ Missing ||  ||  ||
> || wp_ajax_rest_nonce || created || ✅
> [65243](https://core.trac.wordpress.org/ticket/65243) || 65243-ajax-
> actions-wp_ajax_rest_nonce ||
> || wp_ajax_toggle_auto_updates || ❌ Missing ||  ||  ||
> || wp_ajax_send_password_reset || ❌ Missing ||  ||  ||

New description:

 == Test Progress: src/wp-admin/includes/ajax-actions.php ==

 This file tracks the status of unit tests for functions in ''src/wp-
 admin/includes/ajax-actions.php''.

 === Completed Functions (Tests Found) ===

 ||=Function=||=Status=||
 || wp_ajax_ajax_tag_search || ✅ Found ||
 || wp_ajax_wp_compression_test || ✅ Found ||
 || _wp_ajax_delete_comment_response || ✅ Found ||
 || wp_ajax_delete_comment || ✅ Found ||
 || wp_ajax_dim_comment || ✅ Found ||
 || wp_ajax_add_tag || ✅ Found ||
 || wp_ajax_get_comments || ✅ Found ||
 || wp_ajax_replyto_comment || ✅ Found ||
 || wp_ajax_edit_comment || ✅ Found ||
 || wp_ajax_add_meta || ✅ Found ||
 || wp_ajax_inline_save || ✅ Found ||
 || wp_ajax_image_editor || ✅ Found ||
 || wp_ajax_set_attachment_thumbnail || ✅ Found ||
 || wp_ajax_send_attachment_to_editor || ✅ Found ||
 || wp_ajax_heartbeat || ✅ Found ||
 || wp_ajax_crop_image || ✅ Found ||
 || wp_ajax_update_theme || ✅ Found ||
 || wp_ajax_update_plugin || ✅ Found ||
 || wp_ajax_delete_plugin || ✅ Found ||
 || wp_ajax_wp_privacy_export_personal_data || ✅ Found ||
 || wp_ajax_wp_privacy_erase_personal_data || ✅ Found ||
 || wp_ajax_parse_media_shortcode || ✅ Found ||

 These tests were moved to ''tests/phpunit/tests/admin/includes/ajax-
 actions'' in [https://core.trac.wordpress.org/ticket/65226 ticket 65226].


 === Missing Functions (Tests Not Found) ===

 ||= Function =||= Status =||= Ticket =||= Pull Request =||= Committed =||
 || wp_ajax_nopriv_heartbeat || created || ✅ #65236 || 65236-ajax-actions-
 wp_ajax_nopriv_heartbeat ||  ||
 || wp_ajax_fetch_list || created || ✅ #65237 || 65237-ajax-actions-
 wp_ajax_fetch_list ||  ||
 || wp_ajax_imgedit_preview || created || #65252 ||
 [https://github.com/WordPress/wordpress-develop/pull/11845 11845] || ||
 || wp_ajax_oembed_cache ||  created || #65252 ||
 [https://github.com/WordPress/wordpress-develop/pull/11846 11846] ||  ||
 || wp_ajax_autocomplete_user || ❌ Missing ||  ||  ||  ||
 || wp_ajax_get_community_events || ❌ Missing ||  ||  ||  ||
 || wp_ajax_dashboard_widgets || ❌ Missing ||  ||  ||  ||
 || wp_ajax_logged_in || created || ✅ #65242 || 65242-ajax-actions-
 wp_ajax_logged_in ||  ||
 || _wp_ajax_add_hierarchical_term || ❌ Missing ||  ||  ||  ||
 || wp_ajax_delete_tag || ❌ Missing ||  ||  ||  ||
 || wp_ajax_delete_link || ❌ Missing ||  ||  ||  ||
 || wp_ajax_delete_meta || ❌ Missing ||  ||  ||  ||
 || wp_ajax_delete_post || ❌ Missing ||  ||  ||  ||
 || wp_ajax_trash_post || ❌ Missing ||  ||  ||  ||
 || wp_ajax_untrash_post || ❌ Missing ||  ||  ||  ||
 || wp_ajax_delete_page || ❌ Missing ||  ||  ||  ||
 || wp_ajax_add_link_category || ❌ Missing ||  ||  ||  ||
 || wp_ajax_get_tagcloud || ❌ Missing ||  ||  ||  ||
 || wp_ajax_add_menu_item || ❌ Missing ||  ||  ||  ||
 || wp_ajax_add_user || ❌ Missing ||  ||  ||  ||
 || wp_ajax_closed_postboxes || ❌ Missing ||  ||  ||  ||
 || wp_ajax_hidden_columns || ❌ Missing ||  ||  ||
 || wp_ajax_update_welcome_panel || ❌ Missing ||  ||  ||
 || wp_ajax_menu_get_metabox || ❌ Missing ||  ||  ||  ||
 || wp_ajax_wp_link_ajax || ❌ Missing ||  ||  ||  ||
 || wp_ajax_menu_locations_save || ❌ Missing ||  ||  ||  ||
 || wp_ajax_meta_box_order || ❌ Missing ||  ||  ||  ||
 || wp_ajax_menu_quick_search || ❌ Missing ||  ||  ||  ||
 || wp_ajax_get_permalink || ❌ Missing ||  ||  ||  ||
 || wp_ajax_sample_permalink || ❌ Missing ||  ||  ||  ||
 || wp_ajax_inline_save_tax || ❌ Missing ||  ||  ||  ||
 || wp_ajax_find_posts || ❌ Missing ||  ||  ||  ||
 || wp_ajax_widgets_order || ❌ Missing ||  ||  ||
 || wp_ajax_save_widget || ❌ Missing ||  ||  ||  ||
 || wp_ajax_update_widget || ❌ Missing ||  ||  ||  ||
 || wp_ajax_delete_inactive_widgets || ❌ Missing ||  ||  ||  ||
 || wp_ajax_media_create_image_subsizes || ❌ Missing ||  ||  ||  ||
 || wp_ajax_upload_attachment || ❌ Missing ||  ||  ||  ||
 || wp_ajax_set_post_thumbnail || ❌ Missing ||  ||  ||  ||
 || wp_ajax_get_post_thumbnail_html || ❌ Missing ||  ||  ||  ||
 || wp_ajax_date_format || created || ✅ #65225 ||
 [https://github.com/WordPress/wordpress-develop/pull/11811 65225-ajax-
 date_format] ||  ||
 || wp_ajax_time_format || created || ✅ #65228 ||
 [https://github.com/WordPress/wordpress-develop/pull/11814 65228-ajax-
 time_format] ||  ||
 || wp_ajax_wp_fullscreen_save_post || ❌ Missing ||  ||  ||  ||
 || wp_ajax_wp_remove_post_lock || ❌ Missing ||  ||  ||  ||
 || wp_ajax_dismiss_wp_pointer || ❌ Missing ||  ||  ||  ||
 || wp_ajax_get_attachment || ❌ Missing ||  ||  ||  ||
 || wp_ajax_query_attachments || ❌ Missing ||  ||  ||  ||
 || wp_ajax_save_attachment || ❌ Missing ||  ||  ||  ||
 || wp_ajax_save_attachment_compat || ❌ Missing ||  ||  ||  ||
 || wp_ajax_save_attachment_order || ❌ Missing ||  ||  ||  ||
 || wp_ajax_send_link_to_editor || ❌ Missing ||  ||  ||  ||
 || wp_ajax_get_revision_diffs || ❌ Missing ||  ||  ||  ||
 || wp_ajax_save_user_color_scheme || ❌ Missing ||  ||  ||  ||
 || wp_ajax_query_themes || ❌ Missing ||  ||  ||  ||
 || wp_ajax_parse_embed || ❌ Missing ||  ||  ||  ||
 || wp_ajax_destroy_sessions || ❌ Missing ||  ||  ||  ||
 || wp_ajax_generate_password || ❌ Missing ||  ||  ||  ||
 || wp_ajax_nopriv_generate_password || ❌ Missing ||  ||  ||  ||
 || wp_ajax_save_wporg_username || ❌ Missing ||  ||  ||  ||
 || wp_ajax_install_theme || ❌ Missing ||  ||  ||  ||
 || wp_ajax_delete_theme || ❌ Missing ||  ||  ||  ||
 || wp_ajax_install_plugin || ❌ Missing ||  ||  ||  ||
 || wp_ajax_activate_plugin || ❌ Missing ||  ||  ||  ||
 || wp_ajax_search_plugins || ❌ Missing ||  ||  ||  ||
 || wp_ajax_search_install_plugins || ❌ Missing ||  ||  ||  ||
 || wp_ajax_edit_theme_plugin_file || ❌ Missing ||  ||  ||  ||
 || wp_ajax_health_check_dotorg_communication || ❌ Missing ||  ||  ||  ||
 || wp_ajax_health_check_background_updates || ❌ Missing ||  ||  ||  ||
 || wp_ajax_health_check_loopback_requests || ❌ Missing ||  ||  ||  ||
 || wp_ajax_health_check_site_status_result || ❌ Missing ||  ||  ||  ||
 || wp_ajax_health_check_get_sizes || ❌ Missing ||  ||  ||  ||
 || wp_ajax_rest_nonce || created || ✅ #65243 || 65243-ajax-actions-
 wp_ajax_rest_nonce ||  ||
 || wp_ajax_toggle_auto_updates || ❌ Missing ||  ||  ||  ||
 || wp_ajax_send_password_reset || ❌ Missing ||  ||  ||  ||

--

Comment (by sabernhardt):

 (adjusted to Trac [https://core.trac.wordpress.org/wiki/WikiFormatting
 WikiFormatting] for links and tables)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65252#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 22:45:11 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 22:45:11 -0000
Subject: [wp-trac] [WordPress Trac] #65251: Response from media library
 API query includes an empty array rather than an empty object
In-Reply-To: <060.19ac4687d79526b90198eb8d0949dc37@wordpress.org>
References: <060.19ac4687d79526b90198eb8d0949dc37@wordpress.org>
Message-ID: <075.2bae4eaa56959720adfdb1b2f699509b@wordpress.org>

#65251: Response from media library API query includes an empty array rather than
an empty object
------------------------------+------------------------------
 Reporter:  frankieandshadow  |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  REST API          |     Version:  6.9.4
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by westonruter):

 Related: #54484

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65251#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 22:56:52 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 22:56:52 -0000
Subject: [wp-trac] [WordPress Trac] #65249: View transition in wp-admin
 doesn't work on Firefox
In-Reply-To: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
References: <053.69b1bc2d5ca4b3be1851232c225338b3@wordpress.org>
Message-ID: <068.17bb1ad14ce07104f1cb6ebc9d8491d9@wordpress.org>

#65249: View transition in wp-admin doesn't work on Firefox
----------------------------+----------------------
 Reporter:  jsmansart       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:  wontfix
 Keywords:                  |     Focuses:
----------------------------+----------------------
Changes (by westonruter):

 * status:  new => closed
 * resolution:   => wontfix
 * milestone:  Awaiting Review =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65249#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 23:46:29 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 23:46:29 -0000
Subject: [wp-trac] [WordPress Trac] #65193: Tests: Add unit tests for
 wp_page_reload_on_back_button_js()
In-Reply-To: <051.5aae89aca4ab44ce78353fe0a50cb02c@wordpress.org>
References: <051.5aae89aca4ab44ce78353fe0a50cb02c@wordpress.org>
Message-ID: <066.59242d374a2d948cabbba2273b78a8cb@wordpress.org>

#65193: Tests: Add unit tests for wp_page_reload_on_back_button_js()
--------------------------------------+---------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 7.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65193#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri May 15 23:47:22 2026
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 15 May 2026 23:47:22 -0000
Subject: [wp-trac] [WordPress Trac] #65193: Tests: Add unit tests for
 wp_page_reload_on_back_button_js()
In-Reply-To: <051.5aae89aca4ab44ce78353fe0a50cb02c@wordpress.org>
References: <051.5aae89aca4ab44ce78353fe0a50cb02c@wordpress.org>
Message-ID: <066.ce3ebf175f0005f63816b534ebc08d63@wordpress.org>

#65193: Tests: Add unit tests for wp_page_reload_on_back_button_js()
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  SergeyBiryukov
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  7.1
Component:  Administration            |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  tests
--------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"62367" 62367]:
 {{{
 #!CommitTicketReference repository="" revision="62367"
 Tests: Add unit tests for `wp_page_reload_on_back_button_js()`.

 Follow-up to [37619].

 Props pbearne.
 Fixes #65193.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65193#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

