From noreply at wordpress.org  Tue Mar  1 01:47:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 01:47:18 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly with
 Odysee.com (half working)
Message-ID: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+-----------------------------
 Reporter:  tomatodysee  |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Embeds       |    Version:
 Severity:  normal       |   Keywords:
  Focuses:  ui           |
-------------------------+-----------------------------
 Hey guys, we recently added oembed / embedly support but odysee.com links
 don’t work properly due to the iframe settings you are pulling in.

 Can they be setup to match youtube? Either need to remove the allow-
 scripts, or add: sandbox=’allow-scripts allow-same-origin allow-popups
 allow-presentation’

 Example: https://tomzarebczan.wordpress.com/2022/02/28/test-odysee-post/ –
 you’ll see the errors in console.

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

From noreply at wordpress.org  Tue Mar  1 04:40:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 04:40:24 -0000
Subject: [wp-trac] [WordPress Trac] #55279: 5.9.1 introduced bug of
 numerious <style>. wp-container-xxxxx etc</style> in html
Message-ID: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>

#55279: 5.9.1 introduced bug of numerious <style>. wp-container-xxxxx etc</style>
in html
--------------------------+-----------------------------
 Reporter:  carasmo       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.1
 Severity:  major         |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 In 5.9.0 this does not happen, however in 5.9.1 a bazillion <style>. wp-
 container-xxxxx ...</style> in the html. With each refresh more are added.
 Logged in or not logged in. With zero plugins.

 [[Image()]]

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

From noreply at wordpress.org  Tue Mar  1 04:40:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 04:40:41 -0000
Subject: [wp-trac] [WordPress Trac] #55279: 5.9.1 introduced bug of
 numerious <style>. wp-container-xxxxx etc</style> in html
In-Reply-To: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
References: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
Message-ID: <066.178389f17db9816f9040f8c163010ba2@wordpress.org>

#55279: 5.9.1 introduced bug of numerious <style>. wp-container-xxxxx etc</style>
in html
--------------------------+------------------------------
 Reporter:  carasmo       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  major         |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by carasmo):

 * Attachment "Screen Shot 2022-02-28 at 11.17.39 PM.png" added.


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

From noreply at wordpress.org  Tue Mar  1 04:57:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 04:57:35 -0000
Subject: [wp-trac] [WordPress Trac] #55279: 5.9.1 introduced bug of
 numerious <style>. wp-container-xxxxx etc</style> in html
In-Reply-To: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
References: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
Message-ID: <066.d4ee56b9b803fe62f75bd47d430af5fc@wordpress.org>

#55279: 5.9.1 introduced bug of numerious <style>. wp-container-xxxxx etc</style>
in html
--------------------------+------------------------------
 Reporter:  carasmo       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  major         |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by carasmo):

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


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

From noreply at wordpress.org  Tue Mar  1 04:58:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 04:58:24 -0000
Subject: [wp-trac] [WordPress Trac] #55279: 5.9.1 introduced bug of
 numerious <style>. wp-container-xxxxx etc</style> in html
In-Reply-To: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
References: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
Message-ID: <066.c87a0328a31661ab2e61ff8a99a0b05a@wordpress.org>

#55279: 5.9.1 introduced bug of numerious <style>. wp-container-xxxxx etc</style>
in html
--------------------------+------------------------------
 Reporter:  carasmo       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  major         |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by carasmo):

 It's Genesis framework. I have just checked with the 2022 theme and this
 bug is not there but as soon as I change the active theme to the Genesis
 parent theme, it's there.

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

From noreply at wordpress.org  Tue Mar  1 05:41:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 05:41:20 -0000
Subject: [wp-trac] [WordPress Trac] #55279: 5.9.1 introduced bug of
 numerious <style>. wp-container-xxxxx etc</style> in html
In-Reply-To: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
References: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
Message-ID: <066.04aa390917841ab4ec93f33106eee175@wordpress.org>

#55279: 5.9.1 introduced bug of numerious <style>. wp-container-xxxxx etc</style>
in html
--------------------------+------------------------------
 Reporter:  carasmo       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  major         |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by carasmo):

 Hopefully WPEngine/StudioPress will correct this. In my child theme
 functions I've added the following to correct this:

 `//Fixes 5.9.1 bug in Genesis`
 `remove_filter( 'render_block', 'wp_render_layout_support_flag', 10, 2 );`

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

From noreply at wordpress.org  Tue Mar  1 09:23:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 09:23:07 -0000
Subject: [wp-trac] [WordPress Trac] #52202: Block Editor interprets
 German gendering asterix as list sign
In-Reply-To: <055.54edda8158c76777dd7f6b160779b860@wordpress.org>
References: <055.54edda8158c76777dd7f6b160779b860@wordpress.org>
Message-ID: <070.b8025980d6add0259810389665a10ff5@wordpress.org>

#52202: Block Editor interprets German gendering asterix as list sign
--------------------------+------------------------------
 Reporter:  pflanzenoma   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.6
 Severity:  normal        |  Resolution:  worksforme
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by zodiac1978):

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


Comment:

 Hi @pflanzenoma

 thank you for the report!

 I tried to reproduce the problem, but with the latest WordPress 5.9 I
 can't see it.

 I tried to paste the word and I tried to manually type it. I even tried it
 with a space before or after the asterisk and the block editor does not
 make a list out of it.

 If the problem is still valid for you, please re-open the ticket and share
 more details on how to reproduce the problem. Thank you again!

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

From noreply at wordpress.org  Tue Mar  1 09:30:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 09:30:26 -0000
Subject: [wp-trac] [WordPress Trac] #55280: Unsupported operand types in
 Site Health
Message-ID: <047.c67a89e097654f10a542cad7a02b6cf7@wordpress.org>

#55280: Unsupported operand types in Site Health
---------------------------------------+-----------------------------
 Reporter:  lw5                        |      Owner:  (none)
     Type:  defect (bug)               |     Status:  new
 Priority:  normal                     |  Milestone:  Awaiting Review
Component:  Site Health                |    Version:  5.9.1
 Severity:  normal                     |   Keywords:
  Focuses:  administration, multisite  |
---------------------------------------+-----------------------------
 I get the following error:

 AH01071: Got error 'PHP message: PHP Fatal error: Uncaught TypeError:
 Unsupported operand types: string - int in [..]/wp-admin/includes/class-
 wp-site-health.php:2521
 Stack trace:
 0 [..]/wp-admin/includes/class-wp-site-health.php(1728):
 WP_Site_Health->has_missed_cron()
 1 [..]/wp-admin/includes/class-wp-site-health.php(192):
 WP_Site_Health->get_test_scheduled_events()
 2 [..]/wp-admin/includes/class-wp-site-health.php(137):
 WP_Site_Health->perform_test()
 3 [..]/wp-includes/class-wp-hook.php(307):
 WP_Site_Health->enqueue_scripts()
 4 [..]/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
 5 [..]/wp-includes/plugin.php(474): WP_Hook->do_action()
 6 [..]/wp-admin/admin-header....', referer: https://[..]/wp-admin/

 This is on a WordPress 5.9.1 multisite running on PHP 8.0.13 which was
 just upgraded from WP 5.5.8/PHP 7.3.33.

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

From noreply at wordpress.org  Tue Mar  1 09:54:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 09:54:24 -0000
Subject: [wp-trac] [WordPress Trac] #55280: Unsupported operand types in
 Site Health
In-Reply-To: <047.c67a89e097654f10a542cad7a02b6cf7@wordpress.org>
References: <047.c67a89e097654f10a542cad7a02b6cf7@wordpress.org>
Message-ID: <062.929cf22c4b95973e130fe26e4bb2ee2b@wordpress.org>

#55280: Unsupported operand types in Site Health
--------------------------+----------------------------------------
 Reporter:  lw5           |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Site Health   |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  administration, multisite
--------------------------+----------------------------------------
Description changed by SergeyBiryukov:

Old description:

> I get the following error:
>
> AH01071: Got error 'PHP message: PHP Fatal error: Uncaught TypeError:
> Unsupported operand types: string - int in [..]/wp-admin/includes/class-
> wp-site-health.php:2521
> Stack trace:
> 0 [..]/wp-admin/includes/class-wp-site-health.php(1728):
> WP_Site_Health->has_missed_cron()
> 1 [..]/wp-admin/includes/class-wp-site-health.php(192):
> WP_Site_Health->get_test_scheduled_events()
> 2 [..]/wp-admin/includes/class-wp-site-health.php(137):
> WP_Site_Health->perform_test()
> 3 [..]/wp-includes/class-wp-hook.php(307):
> WP_Site_Health->enqueue_scripts()
> 4 [..]/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
> 5 [..]/wp-includes/plugin.php(474): WP_Hook->do_action()
> 6 [..]/wp-admin/admin-header....', referer: https://[..]/wp-admin/
>
> This is on a WordPress 5.9.1 multisite running on PHP 8.0.13 which was
> just upgraded from WP 5.5.8/PHP 7.3.33.

New description:

 I get the following error:
 {{{
 AH01071: Got error 'PHP message: PHP Fatal error: Uncaught TypeError:
 Unsupported operand types: string - int in [..]/wp-admin/includes/class-
 wp-site-health.php:2521
 Stack trace:
 0 [..]/wp-admin/includes/class-wp-site-health.php(1728):
 WP_Site_Health->has_missed_cron()
 1 [..]/wp-admin/includes/class-wp-site-health.php(192):
 WP_Site_Health->get_test_scheduled_events()
 2 [..]/wp-admin/includes/class-wp-site-health.php(137):
 WP_Site_Health->perform_test()
 3 [..]/wp-includes/class-wp-hook.php(307):
 WP_Site_Health->enqueue_scripts()
 4 [..]/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
 5 [..]/wp-includes/plugin.php(474): WP_Hook->do_action()
 6 [..]/wp-admin/admin-header....', referer: https://[..]/wp-admin/
 }}}
 This is on a WordPress 5.9.1 multisite running on PHP 8.0.13 which was
 just upgraded from WP 5.5.8/PHP 7.3.33.

--

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

From noreply at wordpress.org  Tue Mar  1 09:57:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 09:57:22 -0000
Subject: [wp-trac] [WordPress Trac] #55279: 5.9.1 introduced bug of
 numerious <style>. wp-container-xxxxx etc</style> in html
In-Reply-To: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
References: <051.e745794decbe73c1c916cff9612f5a6e@wordpress.org>
Message-ID: <066.a4578152ca4bad003664d3bba748464a@wordpress.org>

#55279: 5.9.1 introduced bug of numerious <style>. wp-container-xxxxx etc</style>
in html
--------------------------+----------------------
 Reporter:  carasmo       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.9.1
 Severity:  major         |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review =>


Comment:

 Hi there, welcome back to WordPress Trac!

 Thanks for the follow-up! Glad you were able to identify and resolve the
 issue.

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

From noreply at wordpress.org  Tue Mar  1 10:08:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 10:08:37 -0000
Subject: [wp-trac] [WordPress Trac] #55281: Twenty Twenty One Theme:
 Consider decreasing the selector specificity
Message-ID: <054.2cd3b060f536076375e187aa82fd077d@wordpress.org>

#55281: Twenty Twenty One Theme: Consider decreasing the selector specificity
---------------------------+-----------------------------------------
 Reporter:  orkunaybek     |      Owner:  (none)
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Bundled Theme  |    Version:  5.9.1
 Severity:  normal         |   Keywords:  has-screenshots needs-patch
  Focuses:  css            |
---------------------------+-----------------------------------------
 There is a css selector that selects almost any a tags and applies white
 background on focus. This forces users to use at least 4 classes on
 elements to override by specificity and complicate the code. You can see
 mentioned selector and how it overrides the focus color of a button with 3
 classes already in attached screenshots. Why such strong selector is used
 there, is it really necessary, can we remove it or decrease the
 specificity?

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

From noreply at wordpress.org  Tue Mar  1 10:09:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 10:09:13 -0000
Subject: [wp-trac] [WordPress Trac] #55281: Twenty Twenty One Theme:
 Consider decreasing the selector specificity
In-Reply-To: <054.2cd3b060f536076375e187aa82fd077d@wordpress.org>
References: <054.2cd3b060f536076375e187aa82fd077d@wordpress.org>
Message-ID: <069.231d570055300a704159c0185c5be7e4@wordpress.org>

#55281: Twenty Twenty One Theme: Consider decreasing the selector specificity
-----------------------------------------+------------------------------
 Reporter:  orkunaybek                   |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Bundled Theme                |     Version:  5.9.1
 Severity:  normal                       |  Resolution:
 Keywords:  has-screenshots needs-patch  |     Focuses:  css
-----------------------------------------+------------------------------
Changes (by orkunaybek):

 * Attachment "selector.png" added.


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

From noreply at wordpress.org  Tue Mar  1 10:09:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 10:09:21 -0000
Subject: [wp-trac] [WordPress Trac] #55281: Twenty Twenty One Theme:
 Consider decreasing the selector specificity
In-Reply-To: <054.2cd3b060f536076375e187aa82fd077d@wordpress.org>
References: <054.2cd3b060f536076375e187aa82fd077d@wordpress.org>
Message-ID: <069.50edcf7ed3d3cebed76548019a95104a@wordpress.org>

#55281: Twenty Twenty One Theme: Consider decreasing the selector specificity
-----------------------------------------+------------------------------
 Reporter:  orkunaybek                   |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Bundled Theme                |     Version:  5.9.1
 Severity:  normal                       |  Resolution:
 Keywords:  has-screenshots needs-patch  |     Focuses:  css
-----------------------------------------+------------------------------
Changes (by orkunaybek):

 * Attachment "effect.png" added.


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

From noreply at wordpress.org  Tue Mar  1 10:36:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 10:36:50 -0000
Subject: [wp-trac] [WordPress Trac] #55282: Block Theme "Customize" and
 "Widgets" Menus have same $position
Message-ID: <057.2189dcb1e78138c428cb708433c5cd90@wordpress.org>

#55282: Block Theme "Customize" and "Widgets" Menus have same $position
----------------------------+-----------------------------
 Reporter:  domainsupport   |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:  trunk
 Severity:  normal          |   Keywords:
  Focuses:  administration  |
----------------------------+-----------------------------
 Hello,

 On line 221 of **/wp-admin/menu.php** the "Customize" admin menu item is
 added if a plugin or theme is using **customize_register** hook ...

 {{{#!php
 <?php
 if ( ! wp_is_block_theme() || has_action( 'customize_register' ) ) {
         $position = wp_is_block_theme() ? 7 : 6;

         $submenu['themes.php'][ $position ] = array( __( 'Customize' ),
 'customize', esc_url( $customize_url ), '', 'hide-if-no-customize' );
 }
 }}}


 ... where it gives the menu item the position ID of "7" if it's a block
 theme. This is a problem because on line 5198 of **/wp-
 includes/functions.php** ...

 {{{#!php
 <?php
         $submenu['themes.php'][7] = array( __( 'Widgets' ),
 'edit_theme_options', 'widgets.php' );
 }}}


 ... the same position is used for the "Widgets" admin menu item (if a
 sidebar has been registered) and so the "Customize" admin menu item is
 overridden.

 I suggest this line is changed to ...

 {{{#!php
 <?php
         $position = wp_is_block_theme() ? 8 : 7;
         $submenu['themes.php'][$position] = array( __( 'Widgets' ),
 'edit_theme_options', 'widgets.php' );
 }}}

 Oliver

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

From noreply at wordpress.org  Tue Mar  1 10:38:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 10:38:07 -0000
Subject: [wp-trac] [WordPress Trac] #52423: Editing a category or a tag,
 and getting error message "You need a higher level of permission.
 Sorry, you are not allowed to edit this item."
In-Reply-To: <054.830e4883156008ed2da3c0ae50db1854@wordpress.org>
References: <054.830e4883156008ed2da3c0ae50db1854@wordpress.org>
Message-ID: <069.f14dfe08c3500c1b726cd06a9701f13e@wordpress.org>

#52423: Editing a category or a tag, and getting error message "You need a higher
level of permission. Sorry, you are not allowed to edit this item."
--------------------------+-----------------------
 Reporter:  webtechIMT    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Taxonomy      |     Version:  5.6
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Changes (by webtechIMT):

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


Comment:

 Hello,

 I still have the bug...
 No one is answering to #46297.

 Is there anybody out there ?

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

From noreply at wordpress.org  Tue Mar  1 10:57:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 10:57:24 -0000
Subject: [wp-trac] [WordPress Trac] #55283: Text not aligned properly in the
 mobile view
Message-ID: <052.59dd929e29ac220c37e9249958cab8d0@wordpress.org>

#55283: Text not aligned properly in the mobile view
-------------------------+-------------------------------------------------
 Reporter:  hilayt24     |      Owner:  (none)
     Type:  defect       |     Status:  new
  (bug)                  |
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:
 Severity:  normal       |   Keywords:  needs-patch needs-design-feedback
  Focuses:  ui, css      |  has-screenshots
-------------------------+-------------------------------------------------
 The button text in the menu is not properly aligned in the smaller screens
 till 353px.

 Link to the issue:
 https://www.awesomescreenshot.com/image/23201555?key=8558a9d0ff72e5fab0e7a5428c4f270d

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

From noreply at wordpress.org  Tue Mar  1 11:14:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 11:14:14 -0000
Subject: [wp-trac] [WordPress Trac] #55284: thumbnails issue
Message-ID: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>

#55284: thumbnails issue
---------------------------------+-----------------------------
 Reporter:  simobenedettidesign  |      Owner:  (none)
     Type:  defect (bug)         |     Status:  new
 Priority:  normal               |  Milestone:  Awaiting Review
Component:  Post Thumbnails      |    Version:  5.9.1
 Severity:  major                |   Keywords:
  Focuses:                       |
---------------------------------+-----------------------------
 After updating to the latest version of wordpress, the space between
 elements in the frontend is not respected. For example, the thumbnails of
 image galleries created with WordPress blocks are aligned abnormally,
 spaces are not respected. See Attachment.

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

From noreply at wordpress.org  Tue Mar  1 11:14:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 11:14:32 -0000
Subject: [wp-trac] [WordPress Trac] #55284: thumbnails issue
In-Reply-To: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
References: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
Message-ID: <078.290b6e894a9c8d89b8f818fe9fdeaad5@wordpress.org>

#55284: thumbnails issue
---------------------------------+------------------------------
 Reporter:  simobenedettidesign  |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  Awaiting Review
Component:  Post Thumbnails      |     Version:  5.9.1
 Severity:  major                |  Resolution:
 Keywords:                       |     Focuses:
---------------------------------+------------------------------
Changes (by simobenedettidesign):

 * Attachment "Cattura.JPG" added.


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

From noreply at wordpress.org  Tue Mar  1 11:19:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 11:19:28 -0000
Subject: [wp-trac] [WordPress Trac] #55284: thumbnails issue
In-Reply-To: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
References: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
Message-ID: <078.b60114103674e7134906a5e5f403bcf2@wordpress.org>

#55284: thumbnails issue
---------------------------------+------------------------------
 Reporter:  simobenedettidesign  |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  Awaiting Review
Component:  Post Thumbnails      |     Version:  5.9.1
 Severity:  major                |  Resolution:
 Keywords:                       |     Focuses:
---------------------------------+------------------------------

Comment (by hilayt24):

 Hi @simobenedettidesign, Can you please provide information regarding the
 enviorment in which this is appearing.

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

From noreply at wordpress.org  Tue Mar  1 12:40:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 12:40:41 -0000
Subject: [wp-trac] [WordPress Trac] #55248: Ajax call has stop to work
 (single custom post content)
In-Reply-To: <049.42f2c3f83990a87a3534d4e78e944cf2@wordpress.org>
References: <049.42f2c3f83990a87a3534d4e78e944cf2@wordpress.org>
Message-ID: <064.1a7be8d277ac85cb541da34ed07279eb@wordpress.org>

#55248: Ajax call has stop to work (single custom post content)
-------------------------------+------------------------------
 Reporter:  zak87              |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:  5.9.1
 Severity:  normal             |  Resolution:
 Keywords:                     |     Focuses:
-------------------------------+------------------------------

Comment (by zak87):

 *Update

 I have fixed this (fixed my code - it can be closed).

 But the point is:
 I am using from WP 5.2 in all my themes this line of code:

 {{{
 wp_body_open();
 }}}

 but it looks like it has not working at all until WP 5.9.1.

 I will try to explain.
 I hade in the theme a Ajax call which was calling a full single (single-
 portfolio.php) page (header + content + footer) and than I have used
 jQuery to get just some content from that full/whole page. And all that
 was working until WP 5.9.

 Now, with latest update 5.9.1 that code has stop to work because of:

 {{{
 wp_body_open();
 }}}

 because I am calling/getting a full page (with header and footer - wrong
 way to do that). That has been fixed by calling/getting just a content
 part (without header/footer).

 So, it looks like the **wp_body_open();** has not been working correctly
 until WP 5.9.1.

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

From noreply at wordpress.org  Tue Mar  1 12:55:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 12:55:37 -0000
Subject: [wp-trac] [WordPress Trac] #55282: Block Theme "Customize" and
 "Widgets" Menus have same $position
In-Reply-To: <057.2189dcb1e78138c428cb708433c5cd90@wordpress.org>
References: <057.2189dcb1e78138c428cb708433c5cd90@wordpress.org>
Message-ID: <072.89bbd69a457403e255f80d94de958e64@wordpress.org>

#55282: Block Theme "Customize" and "Widgets" Menus have same $position
----------------------------+------------------------------
 Reporter:  domainsupport   |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:  duplicate
 Keywords:                  |     Focuses:  administration
----------------------------+------------------------------
Changes (by azouamauriac):

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


Comment:

 Duplicate of #54916.

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

From noreply at wordpress.org  Tue Mar  1 12:56:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 12:56:08 -0000
Subject: [wp-trac] [WordPress Trac] #51585: Make beta & RC releases
 available in Github
In-Reply-To: <052.8470f79b374e5543a7a93fb2379d5123@wordpress.org>
References: <052.8470f79b374e5543a7a93fb2379d5123@wordpress.org>
Message-ID: <067.2d281d82e601d7628c360faebb07722e@wordpress.org>

#51585: Make beta & RC releases available in Github
-----------------------------+------------------------------
 Reporter:  malthert         |       Owner:  (none)
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by malthert):

 @priethor as release coordinator for 6.0, could you make this happen
 (starting with Beta 1 of 6.0)?

 I guess that there are some internal docs (since releases get tagged just
 fine), so we'd just need to amend them - to ensure that beta/RC releases
 are tagged the same way that releases are tagged.
 If these guidelines are public and open to contribution I'd do that
 myself, I just couldn't find anything anywhere.

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

From noreply at wordpress.org  Tue Mar  1 13:00:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 13:00:44 -0000
Subject: [wp-trac] [WordPress Trac] #55280: Unsupported operand types in
 Site Health
In-Reply-To: <047.c67a89e097654f10a542cad7a02b6cf7@wordpress.org>
References: <047.c67a89e097654f10a542cad7a02b6cf7@wordpress.org>
Message-ID: <062.f1065420e6b4648ebd6762570266b0e0@wordpress.org>

#55280: Unsupported operand types in Site Health
-------------------------------+----------------------------------------
 Reporter:  lw5                |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Site Health        |     Version:  5.9.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  administration, multisite
-------------------------------+----------------------------------------
Changes (by azouamauriac):

 * keywords:   => reporter-feedback


Comment:

 Hello there, welcome to WordPress trac and thanks for the report.

 Please can you confirm the issue when you downgrade PHP version under 8?
 Thanks.

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

From noreply at wordpress.org  Tue Mar  1 13:07:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 13:07:15 -0000
Subject: [wp-trac] [WordPress Trac] #55280: Unsupported operand types in
 Site Health
In-Reply-To: <047.c67a89e097654f10a542cad7a02b6cf7@wordpress.org>
References: <047.c67a89e097654f10a542cad7a02b6cf7@wordpress.org>
Message-ID: <062.335e055d1bbe4c1595f8b17c1ab76f79@wordpress.org>

#55280: Unsupported operand types in Site Health
-------------------------------+----------------------------------------
 Reporter:  lw5                |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Site Health        |     Version:  5.9.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  administration, multisite
-------------------------------+----------------------------------------

Comment (by lw5):

 When I downgrade the issue turn into a warning:

 {{{
 Warning: A non-numeric value encountered in [..]/wp-admin/includes/class-
 wp-site-health.php on line 2521
 }}}

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

From noreply at wordpress.org  Tue Mar  1 13:21:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 13:21:40 -0000
Subject: [wp-trac] [WordPress Trac] #55219:
 "current_theme_supports-{$feature}" filter doesn't run if no $args are
 passed
In-Reply-To: <058.658784bbdb049263899782fed472c729@wordpress.org>
References: <058.658784bbdb049263899782fed472c729@wordpress.org>
Message-ID: <073.481b3b7a14e565667c1cddb09d290a59@wordpress.org>

#55219: "current_theme_supports-{$feature}" filter doesn't run if no $args are
passed
----------------------------+---------------------
 Reporter:  helgatheviking  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:
----------------------------+---------------------
Changes (by pavanpatil1):

 * Attachment "55219.diff" added.

 Created patch

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

From noreply at wordpress.org  Tue Mar  1 13:22:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 13:22:42 -0000
Subject: [wp-trac] [WordPress Trac] #55285: Add image brakes page
Message-ID: <049.56dc316bdc3e69cacadbbad114d908f2@wordpress.org>

#55285: Add image brakes page
--------------------------+-----------------------------
 Reporter:  Gugan         |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Editor        |    Version:  5.9.1
 Severity:  blocker       |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hello there,
 i've problems with adding images using the default block and acf add image
 functions. After clicking no modal appears anche the page brokes and i
 have to reload the page. I did a downgrade to 5.9.0 and everything works
 greate.

 Hope this helps

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

From noreply at wordpress.org  Tue Mar  1 13:23:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 13:23:14 -0000
Subject: [wp-trac] [WordPress Trac] #55285: Add image brakes page
In-Reply-To: <049.56dc316bdc3e69cacadbbad114d908f2@wordpress.org>
References: <049.56dc316bdc3e69cacadbbad114d908f2@wordpress.org>
Message-ID: <064.e7fa28797230af3b3b4cfa7ccf1497d6@wordpress.org>

#55285: Add image brakes page
--------------------------+------------------------------
 Reporter:  Gugan         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  blocker       |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by Gugan):

 * Attachment "Screenshot 2022-03-01 at 14-21-51 Modifica pagina “Test
 Pagina Marco” ‹ Playground - Stage & Learn — WordPress.png" added.

 broken backend after clic to add image button

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

From noreply at wordpress.org  Tue Mar  1 13:24:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 13:24:17 -0000
Subject: [wp-trac] [WordPress Trac] #55219:
 "current_theme_supports-{$feature}" filter doesn't run if no $args are
 passed
In-Reply-To: <058.658784bbdb049263899782fed472c729@wordpress.org>
References: <058.658784bbdb049263899782fed472c729@wordpress.org>
Message-ID: <073.f403cbd72a82e6c4c128eb1318063ab1@wordpress.org>

#55219: "current_theme_supports-{$feature}" filter doesn't run if no $args are
passed
----------------------------+----------------------
 Reporter:  helgatheviking  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  6.0
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:  invalid
 Keywords:  has-patch       |     Focuses:
----------------------------+----------------------
Changes (by pavanpatil1):

 * keywords:  needs-patch => has-patch
 * status:  new => closed
 * resolution:   => invalid


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

From noreply at wordpress.org  Tue Mar  1 13:25:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 13:25:25 -0000
Subject: [wp-trac] [WordPress Trac] #55219:
 "current_theme_supports-{$feature}" filter doesn't run if no $args are
 passed
In-Reply-To: <058.658784bbdb049263899782fed472c729@wordpress.org>
References: <058.658784bbdb049263899782fed472c729@wordpress.org>
Message-ID: <073.0f1437a21b0cae65663467e8bf8974ee@wordpress.org>

#55219: "current_theme_supports-{$feature}" filter doesn't run if no $args are
passed
----------------------------+-----------------------
 Reporter:  helgatheviking  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  reopened
 Priority:  normal          |   Milestone:  6.0
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------
Changes (by pavanpatil1):

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


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

From noreply at wordpress.org  Tue Mar  1 13:39:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 13:39:58 -0000
Subject: [wp-trac] [WordPress Trac] #55284: thumbnails issue
In-Reply-To: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
References: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
Message-ID: <078.32897dab624447fb64fb9ac67e67fd87@wordpress.org>

#55284: thumbnails issue
---------------------------------+------------------------------
 Reporter:  simobenedettidesign  |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  Awaiting Review
Component:  Post Thumbnails      |     Version:  5.9.1
 Severity:  major                |  Resolution:
 Keywords:                       |     Focuses:
---------------------------------+------------------------------

Comment (by simobenedettidesign):

 Replying to [comment:1 hilayt24]:
 > Hi @simobenedettidesign, Can you please provide information regarding
 the enviorment in which this is appearing.


 Server Architecture
 Linux 3.10.0-862.2.3.el7.x86_64 x86_64
 Server web
 Apache
 PHP Version
 8.0.15

 Do you need more information?

 Thanks

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

From noreply at wordpress.org  Tue Mar  1 14:04:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 14:04:38 -0000
Subject: [wp-trac] [WordPress Trac] #54673: Improve formatting in
 `/wp-admin/user-edit.php`.
In-Reply-To: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
References: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
Message-ID: <066.4c0b3740989080d1b15cc20eda19be77@wordpress.org>

#54673: Improve formatting in `/wp-admin/user-edit.php`.
-----------------------------+-------------------------------
 Reporter:  costdev          |       Owner:  audrasjb
     Type:  enhancement      |      Status:  reviewing
 Priority:  normal           |   Milestone:  6.0
Component:  Administration   |     Version:  5.9
 Severity:  normal           |  Resolution:
 Keywords:  has-patch early  |     Focuses:  coding-standards
-----------------------------+-------------------------------
Changes (by johnregan3):

 * Attachment "54673-1.diff" added.

 Updated to fix merge conflicts

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

From noreply at wordpress.org  Tue Mar  1 14:07:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 14:07:53 -0000
Subject: [wp-trac] [WordPress Trac] #54673: Improve formatting in
 `/wp-admin/user-edit.php`.
In-Reply-To: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
References: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
Message-ID: <066.3aa444e161d07ddbe8e2a2edd523ad1c@wordpress.org>

#54673: Improve formatting in `/wp-admin/user-edit.php`.
-----------------------------+-------------------------------
 Reporter:  costdev          |       Owner:  audrasjb
     Type:  enhancement      |      Status:  reviewing
 Priority:  normal           |   Milestone:  6.0
Component:  Administration   |     Version:  5.9
 Severity:  normal           |  Resolution:
 Keywords:  has-patch early  |     Focuses:  coding-standards
-----------------------------+-------------------------------
Changes (by johnregan3):

 * Attachment "54673-2.diff" added.

 Removed errant personal .gitignore changes.

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

From noreply at wordpress.org  Tue Mar  1 14:09:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 14:09:59 -0000
Subject: [wp-trac] [WordPress Trac] #54775: Allow int/float for esc_
 functions
In-Reply-To: <052.d31d6f3ef2ab6e369a064d261311e94a@wordpress.org>
References: <052.d31d6f3ef2ab6e369a064d261311e94a@wordpress.org>
Message-ID: <067.65035c40aeafa753b6182af894583637@wordpress.org>

#54775: Allow int/float for esc_ functions
-------------------------+-------------------------------
 Reporter:  malthert     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Security     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  close        |     Focuses:  coding-standards
-------------------------+-------------------------------

Comment (by chesio):

 > The type is not unknown, the type is int/float. In fact esc_html will
 convert those to string anyway.

 If you know that something is int/float, why would you want to pass it
 through `esc_html`? Escaping int/float values does not make any sense.

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

From noreply at wordpress.org  Tue Mar  1 14:17:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 14:17:49 -0000
Subject: [wp-trac] [WordPress Trac] #55286: Rest Cannot Create Application
 Passwords
Message-ID: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>

#55286: Rest Cannot Create Application Passwords
----------------------------+-----------------------------
 Reporter:  gonza.ar        |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  REST API        |    Version:  5.9.1
 Severity:  normal          |   Keywords:
  Focuses:  docs, rest-api  |
----------------------------+-----------------------------
 Hi!

 When an api call is made to create an application password, the response
 is:


 {{{
 {
     "code": "rest_cannot_create_application_passwords",
     "message": "Sorry, you are not allowed to create application passwords
 for this user.",
     "data": {
         "status": 401
     }
 }
 }}}


 Api call:

 https://example.com/wp-json/wp/v2/users/1/application-passwords?name=test

 The problem is in the file:
 /wp-includes/rest-api/endpoints/class-wp-rest-application-passwords-
 controller.php
 line 119 method "get_items_permissions_check"

 before this line the $user variable has all the information about the user
 but when the function "current_user_can" is called, another function
 "wp_get_current_user" retrieves the current user from the global variable
 $current_user, and is empty. Consequently, a non-existent user is assigned
 or created, different from the admin user, who has all the permissions to
 make the request to the api.

 Regards


 Note: WordPress Version 5.9.1

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

From noreply at wordpress.org  Tue Mar  1 14:18:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 14:18:55 -0000
Subject: [wp-trac] [WordPress Trac] #55286: Rest Cannot Create
 Application Passwords
In-Reply-To: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
References: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
Message-ID: <067.dab5dbb0909cfddbcb5cedfd624f03b5@wordpress.org>

#55286: Rest Cannot Create Application Passwords
--------------------------+------------------------------
 Reporter:  gonza.ar      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  REST API      |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  docs, rest-api
--------------------------+------------------------------
Changes (by gonza.ar):

 * Attachment "Imagen_1_3_22_11_15_pegada.jpg" added.

 Position when is using the global current user and not the user that is in
 the url

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

From noreply at wordpress.org  Tue Mar  1 14:19:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 14:19:28 -0000
Subject: [wp-trac] [WordPress Trac] #55286: Rest Cannot Create
 Application Passwords
In-Reply-To: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
References: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
Message-ID: <067.773332df8f21405f600bae9bf33eaeda@wordpress.org>

#55286: Rest Cannot Create Application Passwords
--------------------------+------------------------------
 Reporter:  gonza.ar      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  REST API      |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  docs, rest-api
--------------------------+------------------------------
Changes (by gonza.ar):

 * Attachment "Imagen_1_3_22_11_13_pegada.jpg" added.

 Here the user is assigned to the variable

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

From noreply at wordpress.org  Tue Mar  1 14:20:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 14:20:48 -0000
Subject: [wp-trac] [WordPress Trac] #55286: Rest Cannot Create
 Application Passwords
In-Reply-To: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
References: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
Message-ID: <067.6e4fa72bfe56acd65fd2c5d6f97bbb98@wordpress.org>

#55286: Rest Cannot Create Application Passwords
--------------------------+------------------------------
 Reporter:  gonza.ar      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  REST API      |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  docs, rest-api
--------------------------+------------------------------
Changes (by gonza.ar):

 * Attachment "Imagen_1_3_22_11_14_pegada.jpg" added.

 Here is when makes the validation if the admin user (insider args) has
 capabilities, but inside the destination function another variable is used

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

From noreply at wordpress.org  Tue Mar  1 15:21:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:21:59 -0000
Subject: [wp-trac] [WordPress Trac] #51324: sitemap.xml and sitemap-xml
 headers return html as content type
In-Reply-To: <057.3fcd6f1d7dc4a4b9596e7ef7e6392c11@wordpress.org>
References: <057.3fcd6f1d7dc4a4b9596e7ef7e6392c11@wordpress.org>
Message-ID: <072.a5db2a117df65cf61a4e53b838cf0a54@wordpress.org>

#51324: sitemap.xml and sitemap-xml headers return html as content type
---------------------------+------------------------------
 Reporter:  superpoincare  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Sitemaps       |     Version:  5.5
 Severity:  normal         |  Resolution:  wontfix
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by RavanH):

 @SergeyBiryukov you're right I did not read the last sentence of the
 ticket. The discussion would then be about whether a Content-Type header
 alongside a Location header makes any sense at all (there being no content
 sent) :)

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

From noreply at wordpress.org  Tue Mar  1 15:29:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:29:35 -0000
Subject: [wp-trac] [WordPress Trac] #54010: Redirect from /sitemap.xml
 to /wp-sitemap.xml needs to be 301 and not 302
In-Reply-To: <053.48cf7c57e939295bd42cb467b20167de@wordpress.org>
References: <053.48cf7c57e939295bd42cb467b20167de@wordpress.org>
Message-ID: <068.3bb944d99870f5d9c748d57d1007f43b@wordpress.org>

#54010: Redirect from /sitemap.xml to /wp-sitemap.xml needs to be 301 and not 302
--------------------------+------------------------------
 Reporter:  RedBMedia     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Sitemaps      |     Version:  5.5
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by RavanH):

 I've tested on several sites and have seen no issues reported by GSC about
 the 302 redirect.

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

From noreply at wordpress.org  Tue Mar  1 15:33:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:33:53 -0000
Subject: [wp-trac] [WordPress Trac] #55250: Avoid sending empty script
 translations
In-Reply-To: <051.c70c175c4cc365c6efdc917141cf72df@wordpress.org>
References: <051.c70c175c4cc365c6efdc917141cf72df@wordpress.org>
Message-ID: <066.69cc9f65082d199acd93ac6d16f80cdd@wordpress.org>

#55250: Avoid sending empty script translations
--------------------------+---------------------
 Reporter:  jsnajdr       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  I18N          |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------
Changes (by ocean90):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Tue Mar  1 15:34:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:34:25 -0000
Subject: [wp-trac] [WordPress Trac] #55057: WebP EXIF data missing and
 images are not rotated in the same way JPEG images are rotated. (was:
 Uploaded WebP images are not rotated in the same way JPEG images are
 rotated.)
In-Reply-To: <050.cb1caad48c4abb96a7d234f408387e2f@wordpress.org>
References: <050.cb1caad48c4abb96a7d234f408387e2f@wordpress.org>
Message-ID: <065.6f2518c077b50cbd263b23e1532ac76f@wordpress.org>

#55057: WebP EXIF data missing and images are not rotated in the same way JPEG
images are rotated.
--------------------------+------------------------------
 Reporter:  mitogh        |       Owner:  adamsilverstein
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Media         |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  performance
--------------------------+------------------------------

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

From noreply at wordpress.org  Tue Mar  1 15:38:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:38:14 -0000
Subject: [wp-trac] [WordPress Trac] #55280: Unsupported operand types in
 Site Health
In-Reply-To: <047.c67a89e097654f10a542cad7a02b6cf7@wordpress.org>
References: <047.c67a89e097654f10a542cad7a02b6cf7@wordpress.org>
Message-ID: <062.9f2b806456a851b0fe88ccf63915a587@wordpress.org>

#55280: Unsupported operand types in Site Health
--------------------------+----------------------------------------
 Reporter:  lw5           |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Site Health   |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:  php8          |     Focuses:  administration, multisite
--------------------------+----------------------------------------
Changes (by SergeyBiryukov):

 * keywords:  reporter-feedback => php8


Comment:

 Hi there, thanks for the report.

 It looks like this can happen if one of the entries in the cron array is
 not an integer timestamp as it's supposed to be, but a non-numeric string
 instead.

 This was fixed in [33936] / #33475 for WordPress 4.4, and a descriptive
 error message was added in [50143] / #49961 for WordPress 5.7. However,
 the current fix just means that new events cannot be scheduled with a non-
 numeric timestamp. If there is already an existing event like that, it
 remains in the array.

 I'm open to suggestions on what a correct fix here would be. I think just
 hiding the notice in Site Health would not be ideal, we may need an
 upgrade routine to clean up the cron array and remove any events with an
 invalid timestamp.

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

From noreply at wordpress.org  Tue Mar  1 15:40:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:40:11 -0000
Subject: [wp-trac] [WordPress Trac] #54483: On logout input fields have
 aria described login_error
In-Reply-To: <056.5f153943b56f0aa9c5ef66da1cbf5e6b@wordpress.org>
References: <056.5f153943b56f0aa9c5ef66da1cbf5e6b@wordpress.org>
Message-ID: <071.dd706c7fdb2b92bcd57d4ed0046796ae@wordpress.org>

#54483: On logout input fields have aria described login_error
------------------------------------+--------------------------------
 Reporter:  patrickgroot            |       Owner:  alexstine
     Type:  defect (bug)            |      Status:  accepted
 Priority:  normal                  |   Milestone:  6.0
Component:  Login and Registration  |     Version:  5.8.2
 Severity:  trivial                 |  Resolution:
 Keywords:  has-patch               |     Focuses:  ui, accessibility
------------------------------------+--------------------------------
Changes (by afercia):

 * Attachment "54483.3.diff" added.


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

From noreply at wordpress.org  Tue Mar  1 15:42:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:42:32 -0000
Subject: [wp-trac] [WordPress Trac] #51211: Implement a consistent
 function to obtain the sitemap location
In-Reply-To: <055.0624876834d8c6a40e99f22d89bf4de8@wordpress.org>
References: <055.0624876834d8c6a40e99f22d89bf4de8@wordpress.org>
Message-ID: <070.3b2e994c4c3d727a98ec074534a73be3@wordpress.org>

#51211: Implement a consistent function to obtain the sitemap location
-------------------------+------------------------------
 Reporter:  GreatBlakes  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Sitemaps     |     Version:  5.5.1
 Severity:  trivial      |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------------------

Comment (by RavanH):

 Nice work on https://github.com/WordPress/wordpress-develop/pull/514

 (consider this a +1)

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

From noreply at wordpress.org  Tue Mar  1 15:43:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:43:00 -0000
Subject: [wp-trac] [WordPress Trac] #51324: sitemap.xml and sitemap-xml
 headers return html as content type
In-Reply-To: <057.3fcd6f1d7dc4a4b9596e7ef7e6392c11@wordpress.org>
References: <057.3fcd6f1d7dc4a4b9596e7ef7e6392c11@wordpress.org>
Message-ID: <072.6aeb42377199f9f3954078bbd361b997@wordpress.org>

#51324: sitemap.xml and sitemap-xml headers return html as content type
---------------------------+----------------------
 Reporter:  superpoincare  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  Sitemaps       |     Version:  5.5
 Severity:  normal         |  Resolution:  wontfix
 Keywords:                 |     Focuses:
---------------------------+----------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review =>


Comment:

 Forgot to remove the milestone in my previous comment; discussion can
 continue on a closed ticket until there is any interest in reopening it.

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

From noreply at wordpress.org  Tue Mar  1 15:44:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:44:30 -0000
Subject: [wp-trac] [WordPress Trac] #54483: On logout input fields have
 aria described login_error
In-Reply-To: <056.5f153943b56f0aa9c5ef66da1cbf5e6b@wordpress.org>
References: <056.5f153943b56f0aa9c5ef66da1cbf5e6b@wordpress.org>
Message-ID: <071.dc3c26e8a1cca1df59079f9dea2f4a86@wordpress.org>

#54483: On logout input fields have aria described login_error
------------------------------------+--------------------------------
 Reporter:  patrickgroot            |       Owner:  alexstine
     Type:  defect (bug)            |      Status:  accepted
 Priority:  normal                  |   Milestone:  6.0
Component:  Login and Registration  |     Version:  5.8.2
 Severity:  trivial                 |  Resolution:
 Keywords:  has-patch               |     Focuses:  ui, accessibility
------------------------------------+--------------------------------

Comment (by afercia):

 Given that the value of `aria-describedby` should point to the ID of an
 element present on the page, I'd like to propose a different approach in
 [attachment:"54483.3.diff"]. This updated patch should cover the case of
 the login and logout.

 Worth noting there are at least 3 more cases where input fields aren't
 connected to messages displayed on the page:
 - lost password: this page shows a default message and potential errors,
 however the input field is not connected to any description.
 - reset password: the password field is connected to the password strength
 meter, which is also an aria-live region.
 - register: this page shows a default message and potential errors,
 however the two input fields are not connected to any description.

 I'm not sure these cases should be addressed in the context of this ticket
 though.

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

From noreply at wordpress.org  Tue Mar  1 15:55:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:55:09 -0000
Subject: [wp-trac] [WordPress Trac] #55287: Allow for DISTINCT in WP_Query
 method
Message-ID: <054.50212460af26f10a8457cc3c6e422e1a@wordpress.org>

#55287: Allow for DISTINCT in WP_Query method
-------------------------------+-----------------------------
 Reporter:  simbaclaws         |      Owner:  (none)
     Type:  feature request    |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Posts, Post Types  |    Version:  trunk
 Severity:  normal             |   Keywords:  needs-patch
  Focuses:                     |
-------------------------------+-----------------------------
 Dear wordpress developers,

 Currently I'm working with a plugin to create designs.
 This plugin has an element called a repeater element that basically makes
 use of the core WP_Query method in order to fetch custom post types or
 normal post types.

 However, since I'm using this page builder or theme builder, I am in no
 way capable of using DISTINCT within the filter
 https://developer.wordpress.org/reference/hooks/posts_distinct/
 Because this requires me to send the WP_Query instance, which is basically
 only used within the repeater element and can not be set to a variable in
 this particular case.

 This means I'll have to rebuild everything through code, instead of being
 able to use my page or theme builder.

 Now I get the idea of saying this is a bug with the page or theme builder
 plugin.
 But in fact, what I want to know is why are we using a filter to create a
 DISTINCT query inside of WP_Query? Isn't it possible to implement this
 inside of the WP_Query arguments instead? I basically want to say: fetch
 posts with unique titles. This seems much more logical as the SQL query is
 build from WP_Query...

 I've already looked through the entire codex, and couldn't find any
 possible parameter that could be used for this...

 My question to you is: Can this please be added to wordpress core?
 I find it highly frustrating that WP_Query doesn't have this sort of
 capabilities out of the box.

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

From noreply at wordpress.org  Tue Mar  1 15:56:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:56:38 -0000
Subject: [wp-trac] [WordPress Trac] #55247: SVG logos generate warnings
 from _wp_get_image_size_from_meta()
In-Reply-To: <055.dded4e2c58bc7e8ccc9f58ab7706cd9e@wordpress.org>
References: <055.dded4e2c58bc7e8ccc9f58ab7706cd9e@wordpress.org>
Message-ID: <070.2974e1ca315290a67821221517978207@wordpress.org>

#55247: SVG logos generate warnings from _wp_get_image_size_from_meta()
--------------------------+------------------------------
 Reporter:  gillespieza   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9
 Severity:  minor         |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by gillespieza):

 Ah, thanks. No, I'm not using a plugin for that, but a code snippet that
 filters `upload_mimes` and `wp_check_filetype_and_ext`. You wouldn't
 happen to know, off-hand, what filter I should use to set a height/width?
 I'm guessing `wp_update_attachment_metadata`?

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

From noreply at wordpress.org  Tue Mar  1 15:57:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 15:57:46 -0000
Subject: [wp-trac] [WordPress Trac] #55219:
 "current_theme_supports-{$feature}" filter doesn't run if no $args are
 passed
In-Reply-To: <058.658784bbdb049263899782fed472c729@wordpress.org>
References: <058.658784bbdb049263899782fed472c729@wordpress.org>
Message-ID: <073.9243f4f76022fe6def17c557f65a0bfb@wordpress.org>

#55219: "current_theme_supports-{$feature}" filter doesn't run if no $args are
passed
----------------------------+-----------------------------
 Reporter:  helgatheviking  |       Owner:  SergeyBiryukov
     Type:  defect (bug)    |      Status:  reviewing
 Priority:  normal          |   Milestone:  6.0
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  reopened => reviewing


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

From noreply at wordpress.org  Tue Mar  1 16:01:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 16:01:57 -0000
Subject: [wp-trac] [WordPress Trac] #55239: Filter hook
 wp_sitemaps_taxonomies_entry passes Term ID not Object
In-Reply-To: <050.d931e8ac6d10c2579ccf77882f678437@wordpress.org>
References: <050.d931e8ac6d10c2579ccf77882f678437@wordpress.org>
Message-ID: <065.062e56455664e2ea2e62c3ef43dd8a8f@wordpress.org>

#55239: Filter hook wp_sitemaps_taxonomies_entry passes Term ID not Object
-------------------------------------+---------------------
 Reporter:  RavanH                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Sitemaps                 |     Version:  5.9.1
 Severity:  minor                    |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  docs
-------------------------------------+---------------------

Comment (by RavanH):

 During testing, I just noticed that setting `$args['fields'] = 'all'`
 (back to its original intended value?) reduces the number of DB queries by
 a huge number on large taxonomy term sitemaps. Just as an added bonus :)

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

From noreply at wordpress.org  Tue Mar  1 16:05:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 16:05:29 -0000
Subject: [wp-trac] [WordPress Trac] #55219:
 "current_theme_supports-{$feature}" filter doesn't run if no $args are
 passed
In-Reply-To: <058.658784bbdb049263899782fed472c729@wordpress.org>
References: <058.658784bbdb049263899782fed472c729@wordpress.org>
Message-ID: <073.3fdeaf55cec1c11949af2d0df8db2dff@wordpress.org>

#55219: "current_theme_supports-{$feature}" filter doesn't run if no $args are
passed
----------------------------+-----------------------------
 Reporter:  helgatheviking  |       Owner:  SergeyBiryukov
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  6.0
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:  fixed
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52812" 52812]:
 {{{
 #!CommitTicketReference repository="" revision="52812"
 Themes: Make sure the `current_theme_supports-{$feature}` filter is
 consistently applied.

 Previously, the filter was not applied if there are no arguments passed to
 `current_theme_supports()`.

 Follow-up to [12350], [19682].

 Props helgatheviking, azouamauriac, pavanpatil1, SergeyBiryukov.
 Fixes #55219.
 }}}

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

From noreply at wordpress.org  Tue Mar  1 16:06:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 16:06:24 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.ea3e6b8bff984b967aa4379e4011ed4b@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------+----------------------------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  accessibility, javascript
----------------------------+----------------------------------------
Changes (by johnregan3):

 * Attachment "55078.diff" added.

 Initial patch

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

From noreply at wordpress.org  Tue Mar  1 16:08:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 16:08:35 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.12c8e35a429efeffc40c5fee9a5c0c31@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------+----------------------------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  accessibility, javascript
----------------------------+----------------------------------------

Comment (by johnregan3):

 Added initial patch. I'm not satisfied with the naming
 ("data_is_success_message"), but for now I wanted to use something clear
 while evaluating this approach to a solution for this ticket.  Definitely
 open to input.  @SergeyBiryukov

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

From noreply at wordpress.org  Tue Mar  1 16:11:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 16:11:53 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.1d1be81451b1dab3134f20f966869bbf@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------+----------------------------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  accessibility, javascript
----------------------------+----------------------------------------

Comment (by johnregan3):

 Also, I think I'd like to replace the `compact()` on line 1120 and replace
 it with something more readable.
 {{{
 'supplemental' => array(
      'parents'                 => $parents,
      'noparents'               => $noparents,
      'data_is_success_message' => true,
 )
 }}}

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

From noreply at wordpress.org  Tue Mar  1 16:31:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 16:31:17 -0000
Subject: [wp-trac] [WordPress Trac] #55247: SVG logos generate warnings
 from _wp_get_image_size_from_meta()
In-Reply-To: <055.dded4e2c58bc7e8ccc9f58ab7706cd9e@wordpress.org>
References: <055.dded4e2c58bc7e8ccc9f58ab7706cd9e@wordpress.org>
Message-ID: <070.f443714f71c0207e8c39061a41e12fd3@wordpress.org>

#55247: SVG logos generate warnings from _wp_get_image_size_from_meta()
--------------------------+------------------------------
 Reporter:  gillespieza   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9
 Severity:  minor         |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by nosilver4u):

 The two plugins I've looked at recently hook into
 wp_generate_attachment_metadata. Here's one example:
 https://plugins.trac.wordpress.org/browser/safe-svg/trunk/safe-
 svg.php#L371

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

From noreply at wordpress.org  Tue Mar  1 16:56:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 16:56:22 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.9def73bebac60f005df40f96a043231b@wordpress.org>

#36949: Term exists should use get_terms internally
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  2.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note commit                                    |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 I have actioned feedback from @peterwilsoncc. If now uses
 `$_wp_suspend_cache_invalidation` global. This makes the code a lot
 cleaner and means I could add a unit test.

 If now means if you want an uncached term_exists call you can do this.

 {{{#!php
    wp_suspend_cache_invalidation( true );
    $term = term_exists( 'thing' );
    wp_suspend_cache_invalidation( false );
 }}}

 Which might be useful for devs.

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

From noreply at wordpress.org  Tue Mar  1 17:03:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 17:03:18 -0000
Subject: [wp-trac] [WordPress Trac] #55286: Rest Cannot Create
 Application Passwords
In-Reply-To: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
References: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
Message-ID: <067.53fbbfde22827212fe4fa4947f42c534@wordpress.org>

#55286: Rest Cannot Create Application Passwords
--------------------------+-----------------------------
 Reporter:  gonza.ar      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  REST API      |     Version:  5.7
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  docs, rest-api
--------------------------+-----------------------------
Changes (by TimothyBlynJacobs):

 * status:  new => closed
 * version:  5.9.1 => 5.7
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Hi gonza.ar,

 Welcome to Trac and thanks for the ticket!

 This is intentional and is behaving as expected, you can see it covered by
 unit tests here: https://github.com/WordPress/wordpress-
 develop/blob/f0dfa682a5cf2004f468c18ba8d5c87c463cdeea/tests/phpunit/tests
 /rest-api/rest-application-passwords-controller.php#L313

 The context provided to the `current_user_can` check is the user that the
 Application Password is being created for. This allows for using
 `map_meta_cap` to further customize the capabilities required, see #51703.

 If the global current user is empty, that means you aren't authenticated.
 You'll need to authenticate before creating Application Passwords,
 typically using cookies and a nonce: https://developer.wordpress.org/rest-
 api/using-the-rest-api/authentication/

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

From noreply at wordpress.org  Tue Mar  1 17:29:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 17:29:55 -0000
Subject: [wp-trac] [WordPress Trac] #55286: Rest Cannot Create
 Application Passwords
In-Reply-To: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
References: <052.d816772d80d6b22f7c6e03987bf7cd8a@wordpress.org>
Message-ID: <067.4d2d94bebff860eaa948e5b935863cca@wordpress.org>

#55286: Rest Cannot Create Application Passwords
--------------------------+-----------------------------
 Reporter:  gonza.ar      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  REST API      |     Version:  5.7
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  docs, rest-api
--------------------------+-----------------------------

Comment (by gonza.ar):

 Hi Timothy! Ok Thanks!

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

From noreply at wordpress.org  Tue Mar  1 17:46:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 17:46:03 -0000
Subject: [wp-trac] [WordPress Trac] #54878: Don't show links to the
 Customizer when installing themes using api.wordpress.org
In-Reply-To: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
References: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
Message-ID: <072.e3dd88a78c92305a40dde4eb5494d3b0@wordpress.org>

#54878: Don't show links to the Customizer when installing themes using
api.wordpress.org
-------------------------------------+---------------------
 Reporter:  antonvlasenko            |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Themes                   |     Version:  5.9
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------

Comment (by antonvlasenko):

 Thank you so much for testing, @ironprogrammer!
 I've fixed the issue you mentioned.
 @costdev Would it be possible to move this track ticket to the 5.9.2
 milestone, please?
 This trac issue and https://core.trac.wordpress.org/ticket/54578 (which is
 in the 5.9.2 milestone) are related, and both of them fix similar issues.

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

From noreply at wordpress.org  Tue Mar  1 18:32:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 18:32:04 -0000
Subject: [wp-trac] [WordPress Trac] #4476: Delete Cache by Group
In-Reply-To: <052.9c32d35acb1b4c9e1b3f760350cee416@wordpress.org>
References: <052.9c32d35acb1b4c9e1b3f760350cee416@wordpress.org>
Message-ID: <067.dc96b44759cb58e47bd029047417a5c2@wordpress.org>

#4476: Delete Cache by Group
--------------------------------------+------------------------------
 Reporter:  filosofo                  |       Owner:  (none)
     Type:  enhancement               |      Status:  reopened
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Cache API                 |     Version:  2.2
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------------

Comment (by spacedmonkey):

 I understand the desire for this ticket to go into core. But apart from
 the redis examples seen  in this ticket, how would this work in other
 object cache drop-ins. How would this work for a memcache implementation?
 If someone could link to or provide a code snippet for a memcache or other
 object cache implement, that would be helpful.

 If we can reliably have a way for keys in a group to be in core, then
 sadly, this function can not live core. The worry is that someone calls
 `wp_cache_delete_group` and it simply does not work. If this function
 existing in core, we could need some way to backfill / pollyfil, like done
 in wp_cache_get_multiple patch. Again, a can't think of a good way to do
 this without massively refactoring the internals of the object cache.

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

From noreply at wordpress.org  Tue Mar  1 18:47:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 18:47:29 -0000
Subject: [wp-trac] [WordPress Trac] #55288: Site Editor on 5.9.1 fails to
 find homepage template for FSE themes, on WP subdirectory installation
Message-ID: <055.066d0ca728e3fb5959c659d12bba3c2b@wordpress.org>

#55288: Site Editor on 5.9.1 fails to find homepage template for FSE themes, on WP
subdirectory installation
--------------------------------------+-----------------------------
 Reporter:  andronocean               |      Owner:  (none)
     Type:  defect (bug)              |     Status:  new
 Priority:  normal                    |  Milestone:  Awaiting Review
Component:  Editor                    |    Version:  5.9.1
 Severity:  major                     |   Keywords:
  Focuses:  administration, template  |
--------------------------------------+-----------------------------
 I'm getting an error when launching the site editor on 5.9.1, stating “The
 editor is unable to find a block template for the homepage”. This happens
 on both Twenty-Twenty-Two and a custom FSE theme (otherwise functional,
 has templates/single.html and templates/index.html). **My WP installation
 is in a subdirectory**, using the
 [[https://github.com/roots/bedrock|Bedrock]] site structure, so the editor
 URL is `https://example.test/wp/wp-admin/themes.php?page=gutenberg-edit-
 site`

 I've tried it on PHP 7.4.25 and 8.0.14. I've confirmed it still happens
 with all plugins deactivated.

 Notably, activating the Gutenberg plugin version 12.6.1 eliminates the
 error and the editor loads correctly.

 There are several other reports of the same error in this Twenty-Twenty-
 Two forum thread: https://wordpress.org/support/topic/the-editor-is-
 unable-to-find-a-block-template-for-the-homepage/

 The error code output from the copy button is

 {{{
 Error: `getHomepageParams`: HTTP status error, 404
     at https://example.test/wp/wp-includes/js/dist/edit-
 site.js?ver=403e01f2b098b6a656118a51787581cb:8766:13
     at async getHomepageParams (https://example.test/wp/wp-
 includes/js/dist/edit-
 site.js?ver=403e01f2b098b6a656118a51787581cb:8762:20)
     at async redirectToHomepage (https://example.test/wp/wp-
 includes/js/dist/edit-
 site.js?ver=403e01f2b098b6a656118a51787581cb:8797:28)
     at async reinitializeEditor (https://example.test/wp/wp-
 includes/js/dist/edit-site.js?ver=403e01f2b098b6a656118a51787581cb:9067:5)
 }}}

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

From noreply at wordpress.org  Tue Mar  1 19:06:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 19:06:30 -0000
Subject: [wp-trac] [WordPress Trac] #54878: Don't show links to the
 Customizer when installing themes using api.wordpress.org
In-Reply-To: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
References: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
Message-ID: <072.e2c0e5f7a7f4b6e608218f6ff7f7d215@wordpress.org>

#54878: Don't show links to the Customizer when installing themes using
api.wordpress.org
---------------------------------------+---------------------
 Reporter:  antonvlasenko              |       Owner:  (none)
     Type:  defect (bug)               |      Status:  new
 Priority:  normal                     |   Milestone:  6.0
Component:  Themes                     |     Version:  5.9
 Severity:  normal                     |  Resolution:
 Keywords:  has-patch has-screenshots  |     Focuses:
---------------------------------------+---------------------
Changes (by ironprogrammer):

 * keywords:  has-patch needs-testing => has-patch has-screenshots


Comment:

 👍🏻 LGTM! The PR update has addressed the removal of the preview button
 immediately following installation of a block theme.

 == Test Report

 [https://github.com/WordPress/wordpress-develop/pull/2349 PR 2349]

 === Env
 * WordPress 6.0-alpha-52448-src
 * Safari 15.3 (w/ cleared cache)
 * Chrome 98.0.4758.109
 * macOS 12.2.1 (Monterey)
 * Theme: Twenty Twenty-Two
 * Gutenberg DISABLED 🔴

 === Steps to Test
 1. On ''Appearance > Themes'' activate "Twenty Twenty-Two" theme.
 2. Click **Add New** and search for "tt1" ("TT1 Blocks" theme).
 3. Click **Install** for "TT1 Blocks" theme.
 4. Observe the **Preview** button is removed, and not replaced with **Live
 Preview**. ✅
 5. Refresh page (Reload or repeat Steps 1-3).
 6. Observe **Live Preview** button is removed. ✅

 === Screenshots

 [[Image(https://cldup.com/MOQIYHJAfW.gif)]]
 ''On `theme-install.php`, **Preview** and **Live Preview** buttons are
 removed after block theme installation.''

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

From noreply at wordpress.org  Tue Mar  1 20:03:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 20:03:02 -0000
Subject: [wp-trac] [WordPress Trac] #54843: Add end to end test case for
 Trash a single post and restore post from trash
In-Reply-To: <055.17005acbdcc9a6c1a08cd0e490b0b9e0@wordpress.org>
References: <055.17005acbdcc9a6c1a08cd0e490b0b9e0@wordpress.org>
Message-ID: <070.e4124b997da9950cd1674ae32c1c3f74@wordpress.org>

#54843: Add end to end test case for Trash a single post and restore post from
trash
--------------------------------------+---------------------
 Reporter:  pavanpatil1               |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Tue Mar  1 21:10:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 21:10:31 -0000
Subject: [wp-trac] [WordPress Trac] #54775: Allow int/float for esc_
 functions
In-Reply-To: <052.d31d6f3ef2ab6e369a064d261311e94a@wordpress.org>
References: <052.d31d6f3ef2ab6e369a064d261311e94a@wordpress.org>
Message-ID: <067.88037a0f6b7aa03382e8f965a10c6919@wordpress.org>

#54775: Allow int/float for esc_ functions
-------------------------+-------------------------------
 Reporter:  malthert     |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Security     |     Version:
 Severity:  normal       |  Resolution:  wontfix
 Keywords:  close        |     Focuses:  coding-standards
-------------------------+-------------------------------
Changes (by johnbillion):

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


Comment:

 This conversation isn't really going anywhere so I'll close off this
 ticket. As mentioned a few times, if you know the type is an integer or
 float then it can be handled accordingly, no need to pass it through
 `esc_html()`.

 Cheers!

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

From noreply at wordpress.org  Tue Mar  1 21:41:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 21:41:41 -0000
Subject: [wp-trac] [WordPress Trac] #55289: Large image fails to create a
 `scaled` version and subsizes
Message-ID: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>

#55289: Large image fails to create a `scaled` version and subsizes
--------------------------+-----------------------------
 Reporter:  mitogh        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Media         |    Version:  5.9.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 When uploading a large image into WordPress it fails to create the
 `scaled` version, due to the usage of too many resources, because the
 `-scaled` resized version can't be created, no additional subsize is
 created.

 The resize fails with the following error message:

 > cache resources exhausted


 Even with the resized failure, only the full-size image is uploaded and no
 additional image sizes are generated.

 Steps to recreate the problem:

 1. Upload the provided image.
 2. Inspect the metadata of the image and observe no `-scaled` version was
 created and no subsizes was created either.

 Observe how only the full image size is uploaded, no `-scaled` version
 can't be found.

 == Problems

 1. As described before the full size image is uploaded and no `scaled`
 version is created.
 2. When loading the media library the full image size is loaded due no
 subsizes were created.
 3. No subsizes are created for this image due to the resized image failing
 to be created.


 == Setup

 Sharing the details of my current setup:


 {{{

 ### wp-core ###

 version: 5.9.1
 site_language: en_US
 user_language: en_US
 timezone: +00:00
 permalink: /%year%/%monthnum%/%day%/%postname%/
 https_status: true
 multisite: false
 user_registration: 0
 blog_public: 1
 default_comment_status: open
 environment_type: production
 user_count: 1
 dotorg_communication: true

 ### wp-paths-sizes ###

 wordpress_path: /app
 wordpress_size: 152.90 MB (160327567 bytes)
 uploads_path: /app/wp-content/uploads
 uploads_size: 22.75 MB (23851112 bytes)
 themes_path: /app/wp-content/themes
 themes_size: 6.47 MB (6780262 bytes)
 plugins_path: /app/wp-content/plugins
 plugins_size: 208.42 MB (218539593 bytes)
 database_size: 3.96 MB (4149380 bytes)
 total_size: 394.49 MB (413647914 bytes)

 ### wp-active-theme ###

 name: Twenty Twenty-Two (twentytwentytwo)
 version: 1.0 (latest version: 1.1)
 author: the WordPress team
 author_website: https://wordpress.org/
 parent_theme: none
 theme_features: core-block-patterns, post-thumbnails, responsive-embeds,
 editor-styles, html5, automatic-feed-links, block-templates, widgets-
 block-editor, wp-block-styles, editor-style
 theme_path: /app/wp-content/themes/twentytwentytwo
 auto_update: Disabled

 ### wp-themes-inactive (3) ###

 Twenty Nineteen: version: 2.2, author: the WordPress team, Auto-updates
 disabled
 Twenty Twenty: version: 1.9, author: the WordPress team, Auto-updates
 disabled
 Twenty Twenty-One: version: 1.5, author: the WordPress team, Auto-updates
 disabled


 ### wp-plugins-inactive (1) ###

 Performance Lab: version: 1.0.0-beta.1, author: WordPress Performance
 Group, Auto-updates disabled

 ### wp-media ###

 image_editor: WP_Image_Editor_Imagick
 imagick_module_version: 1691
 imagemagick_version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25
 https://imagemagick.org
 imagick_version: 3.7.0
 file_uploads: File uploads is turned off
 post_max_size: 100M
 upload_max_filesize: 100M
 max_effective_size: 100 MB
 max_file_uploads: 20
 imagick_limits:
         imagick::RESOURCETYPE_AREA: 122 MB
         imagick::RESOURCETYPE_DISK: 1073741824
         imagick::RESOURCETYPE_FILE: 786432
         imagick::RESOURCETYPE_MAP: 512 MB
         imagick::RESOURCETYPE_MEMORY: 256 MB
         imagick::RESOURCETYPE_THREAD: 1
 imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, AVI,
 AVIF, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS,
 CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUR, CUT, DATA, DCM,
 DCR, DCX, DDS, DFONT, DJVU, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS,
 EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FILE, FITS,
 FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV,
 H, HALD, HDR, HEIC, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO,
 ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG,
 JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, LABEL, M2V,
 M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV,
 MP4, MPC, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF,
 PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF,
 PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA,
 PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM,
 PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS,
 RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML,
 SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA,
 THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY,
 VDA, VICAR, VID, VIDEO, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ,
 WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV
 gd_version: bundled (2.1.0 compatible)
 gd_formats: GIF, JPEG, PNG, WebP, BMP
 ghostscript_version: 9.53.3

 ### wp-server ###

 server_architecture: Linux 5.15.12-1-MANJARO x86_64
 httpd_software: nginx/1.17.10
 php_version: 7.4.28 64bit
 php_sapi: fpm-fcgi
 max_input_variables: 10000
 time_limit: 3
 memory_limit: 1G
 max_input_time: 900
 upload_max_filesize: 100M
 php_post_max_size: 100M
 curl_version: 7.74.0 OpenSSL/1.1.1k
 suhosin: false
 imagick_availability: true
 pretty_permalinks: true

 ### wp-database ###

 extension: mysqli
 server_version: 10.3.27-MariaDB
 client_version: mysqlnd 7.4.28
 max_allowed_packet: 33554432
 max_connections: 151

 ### wp-constants ###

 WP_HOME: undefined
 WP_SITEURL: undefined
 WP_CONTENT_DIR: /app/wp-content
 WP_PLUGIN_DIR: /app/wp-content/plugins
 WP_MEMORY_LIMIT: 40M
 WP_MAX_MEMORY_LIMIT: 1G
 WP_DEBUG: true
 WP_DEBUG_DISPLAY: true
 WP_DEBUG_LOG: true
 SCRIPT_DEBUG: false
 WP_CACHE: false
 CONCATENATE_SCRIPTS: undefined
 COMPRESS_SCRIPTS: undefined
 COMPRESS_CSS: undefined
 WP_ENVIRONMENT_TYPE: Undefined
 DB_CHARSET: utf8mb4
 DB_COLLATE: undefined

 ### wp-filesystem ###

 wordpress: writable
 wp-content: writable
 uploads: writable
 plugins: writable
 themes: writable
 mu-plugins: writable

 }}}

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

From noreply at wordpress.org  Tue Mar  1 21:42:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 21:42:03 -0000
Subject: [wp-trac] [WordPress Trac] #55289: Large image fails to create
 a `scaled` version and subsizes
In-Reply-To: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
References: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
Message-ID: <065.f2cf019e85e00b69acc72fcd803dcb4c@wordpress.org>

#55289: Large image fails to create a `scaled` version and subsizes
--------------------------+------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by mitogh):

 * Attachment "photo-1644433329707-2b528437a7e7.jpg" added.

 Media picture to test the failure

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

From noreply at wordpress.org  Tue Mar  1 22:05:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 22:05:28 -0000
Subject: [wp-trac] [WordPress Trac] #55290: Not all image edits are applied
 to all subsizes
Message-ID: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>

#55290: Not all image edits are applied to all subsizes
-----------------------------------------+-----------------------------
 Reporter:  mitogh                       |      Owner:  (none)
     Type:  defect (bug)                 |     Status:  new
 Priority:  normal                       |  Milestone:  Awaiting Review
Component:  Media                        |    Version:  5.9.1
 Severity:  normal                       |   Keywords:
  Focuses:  administration, performance  |
-----------------------------------------+-----------------------------
 When editing an image using the admin editor, not all edits are applied
 correctly to all image subsizes. Specifically, the problem occurs when an
 edit results in a smaller size than the defined image size. Given the
 following image subsizes, and the attached image.


 {{{
 => array(6) {
   ["thumbnail"]=>
   array(3) {
     ["width"]=>
     int(150)
     ["height"]=>
     int(150)
     ["crop"]=>
     bool(true)
   }
   ["medium"]=>
   array(3) {
     ["width"]=>
     int(300)
     ["height"]=>
     int(300)
     ["crop"]=>
     bool(false)
   }
   ["medium_large"]=>
   array(3) {
     ["width"]=>
     int(768)
     ["height"]=>
     int(0)
     ["crop"]=>
     bool(false)
   }
   ["large"]=>
   array(3) {
     ["width"]=>
     int(1024)
     ["height"]=>
     int(1024)
     ["crop"]=>
     bool(false)
   }
   ["1536x1536"]=>
   array(3) {
     ["width"]=>
     int(1536)
     ["height"]=>
     int(1536)
     ["crop"]=>
     bool(false)
   }
   ["2048x2048"]=>
   array(3) {
     ["width"]=>
     int(2048)
     ["height"]=>
     int(2048)
     ["crop"]=>
     bool(false)
   }
 }
 }}}


 ''The defined sizes above are the ones coming by default with the setting
 provided below.
 ''

 == Steps to replicate the problem:

 1. Upload the image into your installation.
 2. After the image is uploaded, click on edit to open the image editor or
 go to the image editor from within the media library.
 3. Click on Edit image
 4. Click on rotate image (either right or left) only once.
 5. Make sure the changes are applied to all images by checking that the
 setting Apply changes to: All image sizes is set
 6. Click on save

 After the image is saved observe the changes were applied only to the
 following image sizes:

 - `thumbnail`
 - `medium`
 - `large`
 - `full`

 The only size that was not updated as expected was:

 - `medium_large`

 == Setup


 {{{
 ### wp-core ###

 version: 5.9.1
 site_language: en_US
 user_language: en_US
 timezone: +00:00
 permalink: /%year%/%monthnum%/%day%/%postname%/
 https_status: true
 multisite: false
 user_registration: 0
 blog_public: 1
 default_comment_status: open
 environment_type: production
 user_count: 1
 dotorg_communication: true

 ### wp-paths-sizes ###

 wordpress_path: /app
 wordpress_size: 152.90 MB (160327567 bytes)
 uploads_path: /app/wp-content/uploads
 uploads_size: 22.75 MB (23851112 bytes)
 themes_path: /app/wp-content/themes
 themes_size: 6.47 MB (6780262 bytes)
 plugins_path: /app/wp-content/plugins
 plugins_size: 208.42 MB (218539593 bytes)
 database_size: 3.96 MB (4149380 bytes)
 total_size: 394.49 MB (413647914 bytes)

 ### wp-active-theme ###

 name: Twenty Twenty-Two (twentytwentytwo)
 version: 1.0 (latest version: 1.1)
 author: the WordPress team
 author_website: https://wordpress.org/
 parent_theme: none
 theme_features: core-block-patterns, post-thumbnails, responsive-embeds,
 editor-styles, html5, automatic-feed-links, block-templates, widgets-
 block-editor, wp-block-styles, editor-style
 theme_path: /app/wp-content/themes/twentytwentytwo
 auto_update: Disabled

 ### wp-themes-inactive (3) ###

 Twenty Nineteen: version: 2.2, author: the WordPress team, Auto-updates
 disabled
 Twenty Twenty: version: 1.9, author: the WordPress team, Auto-updates
 disabled
 Twenty Twenty-One: version: 1.5, author: the WordPress team, Auto-updates
 disabled


 ### wp-plugins-inactive (1) ###

 Performance Lab: version: 1.0.0-beta.1, author: WordPress Performance
 Group, Auto-updates disabled

 ### wp-media ###

 image_editor: WP_Image_Editor_Imagick
 imagick_module_version: 1691
 imagemagick_version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25
 https://imagemagick.org
 imagick_version: 3.7.0
 file_uploads: File uploads is turned off
 post_max_size: 100M
 upload_max_filesize: 100M
 max_effective_size: 100 MB
 max_file_uploads: 20
 imagick_limits:
         imagick::RESOURCETYPE_AREA: 122 MB
         imagick::RESOURCETYPE_DISK: 1073741824
         imagick::RESOURCETYPE_FILE: 786432
         imagick::RESOURCETYPE_MAP: 512 MB
         imagick::RESOURCETYPE_MEMORY: 256 MB
         imagick::RESOURCETYPE_THREAD: 1
 imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, AVI,
 AVIF, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS,
 CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUR, CUT, DATA, DCM,
 DCR, DCX, DDS, DFONT, DJVU, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS,
 EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FILE, FITS,
 FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV,
 H, HALD, HDR, HEIC, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO,
 ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG,
 JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, LABEL, M2V,
 M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV,
 MP4, MPC, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF,
 PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF,
 PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA,
 PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM,
 PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS,
 RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML,
 SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA,
 THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY,
 VDA, VICAR, VID, VIDEO, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ,
 WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV
 gd_version: bundled (2.1.0 compatible)
 gd_formats: GIF, JPEG, PNG, WebP, BMP
 ghostscript_version: 9.53.3

 ### wp-server ###

 server_architecture: Linux 5.15.12-1-MANJARO x86_64
 httpd_software: nginx/1.17.10
 php_version: 7.4.28 64bit
 php_sapi: fpm-fcgi
 max_input_variables: 10000
 time_limit: 3
 memory_limit: 1G
 max_input_time: 900
 upload_max_filesize: 100M
 php_post_max_size: 100M
 curl_version: 7.74.0 OpenSSL/1.1.1k
 suhosin: false
 imagick_availability: true
 pretty_permalinks: true

 ### wp-database ###

 extension: mysqli
 server_version: 10.3.27-MariaDB
 client_version: mysqlnd 7.4.28
 max_allowed_packet: 33554432
 max_connections: 151

 ### wp-constants ###

 WP_HOME: undefined
 WP_SITEURL: undefined
 WP_CONTENT_DIR: /app/wp-content
 WP_PLUGIN_DIR: /app/wp-content/plugins
 WP_MEMORY_LIMIT: 40M
 WP_MAX_MEMORY_LIMIT: 1G
 WP_DEBUG: true
 WP_DEBUG_DISPLAY: true
 WP_DEBUG_LOG: true
 SCRIPT_DEBUG: false
 WP_CACHE: false
 CONCATENATE_SCRIPTS: undefined
 COMPRESS_SCRIPTS: undefined
 COMPRESS_CSS: undefined
 WP_ENVIRONMENT_TYPE: Undefined
 DB_CHARSET: utf8mb4
 DB_COLLATE: undefined

 ### wp-filesystem ###

 wordpress: writable
 wp-content: writable
 uploads: writable
 plugins: writable
 themes: writable
 mu-plugins: writable
 }}}

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

From noreply at wordpress.org  Tue Mar  1 22:05:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 22:05:50 -0000
Subject: [wp-trac] [WordPress Trac] #55290: Not all image edits are
 applied to all subsizes
In-Reply-To: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
References: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
Message-ID: <065.55f0466b0f73c0e809816db6e6640f83@wordpress.org>

#55290: Not all image edits are applied to all subsizes
--------------------------+------------------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  administration, performance
--------------------------+------------------------------------------
Changes (by mitogh):

 * Attachment "leafs.jpg" added.


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

From noreply at wordpress.org  Tue Mar  1 22:26:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 22:26:58 -0000
Subject: [wp-trac] [WordPress Trac] #50284: A fix to the
 CPT-no-create-when-submenu-child problem.
In-Reply-To: <052.1a795aee56423f1d425da148db4dbd38@wordpress.org>
References: <052.1a795aee56423f1d425da148db4dbd38@wordpress.org>
Message-ID: <067.8286fdca3b5a269874ebaaf65ae35267@wordpress.org>

#50284: A fix to the CPT-no-create-when-submenu-child problem.
----------------------------+---------------------------------
 Reporter:  mort1305        |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  5.5
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  ui, administration
----------------------------+---------------------------------

Comment (by lovecomm):

 Ditto what @mort1305 says. Would be intereseted in the status of this as
 well, and also have no idea how core development works. Ran into this
 issue with a clients site. Running 5.9.1

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

From noreply at wordpress.org  Tue Mar  1 22:30:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 22:30:40 -0000
Subject: [wp-trac] [WordPress Trac] #53450: [WP_Meta_Query] Add faster
 LIKE based 'STARTSWITH' and 'ENDSWITH' compare modes for value query
In-Reply-To: <052.221d7b56bb4342e1eb298b920051d5d7@wordpress.org>
References: <052.221d7b56bb4342e1eb298b920051d5d7@wordpress.org>
Message-ID: <067.3aeb24aa35a28bf71e2dfaf93ca9b00f@wordpress.org>

#53450: [WP_Meta_Query] Add faster LIKE based 'STARTSWITH' and 'ENDSWITH' compare
modes for value query
-------------------------------------------------+-------------------------
 Reporter:  janthiel                             |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Query                                |     Version:  5.7.2
 Severity:  trivial                              |  Resolution:
 Keywords:  dev-feedback has-patch needs-docs    |     Focuses:
  needs-codex has-unit-tests early early-like-   |  performance
  actually-early needs-testing                   |
-------------------------------------------------+-------------------------
Changes (by ironprogrammer):

 * keywords:
     dev-feedback has-patch needs-docs needs-codex has-unit-tests early
     early-like-actually-early
     =>
     dev-feedback has-patch needs-docs needs-codex has-unit-tests early
     early-like-actually-early needs-testing


Comment:

 Making sure this bubbles up in test circles..

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

From noreply at wordpress.org  Tue Mar  1 23:50:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 01 Mar 2022 23:50:27 -0000
Subject: [wp-trac] [WordPress Trac] #54878: Don't show links to the
 Customizer when installing themes using api.wordpress.org
In-Reply-To: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
References: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
Message-ID: <072.46a302e83be5089c1b36a15d889b5937@wordpress.org>

#54878: Don't show links to the Customizer when installing themes using
api.wordpress.org
----------------------------------------------+---------------------
 Reporter:  antonvlasenko                     |       Owner:  (none)
     Type:  defect (bug)                      |      Status:  new
 Priority:  normal                            |   Milestone:  5.9.2
Component:  Themes                            |     Version:  5.9
 Severity:  normal                            |  Resolution:
 Keywords:  has-patch has-screenshots commit  |     Focuses:
----------------------------------------------+---------------------
Changes (by costdev):

 * keywords:  has-patch has-screenshots => has-patch has-screenshots commit
 * milestone:  6.0 => 5.9.2


Comment:

 Thanks for the test reports @ironprogrammer!

 @antonvlasenko Moving to the 5.9.2 milestone and flagging for `commit`
 consideration.

 For committers: This ticket's issue has been identified, reproduced,
 patched, tested, improved, tested and confirmed. No outstanding issues or
 newly introduced regressions have been identified.

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

From noreply at wordpress.org  Wed Mar  2 05:58:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 05:58:57 -0000
Subject: [wp-trac] [WordPress Trac] #55272: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
References: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
Message-ID: <074.f1a18389197e64875ce0302c9ec5eb6f@wordpress.org>

#55272: The New Layout Fix For Plugin Install Page
-------------------------------------+-------------------------------------
 Reporter:  sharjeelkhanvmi          |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Plugins                  |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  reporter-feedback        |     Focuses:  ui, css,
  needs-design-feedback              |  administration
-------------------------------------+-------------------------------------

Comment (by sharjeelkhanvmi):

 Hello
 I did not get your first point.
 Yes, it Looks good in smaller windows as well.
 Yes, right I need to rearrange elements but I do not know where to change
 them.

 Yes if we add more description lines to show then it mismatches the
 alignment of the boxes yes it will be great to show the version number
 below the description as well.


 Replying to [comment:4 joyously]:
 > Does the new look account for the error messages that can be shown? The
 plugin can have a message about mismatched versions.
 > Also, does this still look good on smaller windows?
 > Also, if you want to rearrange the elements, change the HTML instead of
 using CSS, for accessibility reasons.
 >
 > My own opinion is that the short description should not be chopped
 midsentence since it is already so short. I would rather see the version
 number in addition to what is already shown.

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

From noreply at wordpress.org  Wed Mar  2 05:59:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 05:59:37 -0000
Subject: [wp-trac] [WordPress Trac] #55272: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
References: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
Message-ID: <074.2b5411f374e0d9e0fd317c4628e7dcc6@wordpress.org>

#55272: The New Layout Fix For Plugin Install Page
-------------------------------------+-------------------------------------
 Reporter:  sharjeelkhanvmi          |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Plugins                  |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  reporter-feedback        |     Focuses:  ui, css,
  needs-design-feedback              |  administration
-------------------------------------+-------------------------------------

Comment (by sharjeelkhanvmi):

 What's that?
 Replying to [comment:5 SergeyBiryukov]:

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

From noreply at wordpress.org  Wed Mar  2 07:57:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 07:57:44 -0000
Subject: [wp-trac] [WordPress Trac] #55291: Can't access Custom CSS with
 theme Twenty Twenty-Two
Message-ID: <056.1ac2611b59cebcd2a6941a3ceb32d710@wordpress.org>

#55291: Can't access Custom CSS with theme Twenty Twenty-Two
--------------------------+-----------------------------
 Reporter:  DeveloperWil  |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Themes        |    Version:  5.9.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 The TT2 theme hides the customizer because the block theme replicates
 (most) of the functionality, however, if I switch from an existing theme
 to TT2 I lose access to all my Custom CSS that I previously had in
 Customizer.

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

From noreply at wordpress.org  Wed Mar  2 08:39:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 08:39:53 -0000
Subject: [wp-trac] [WordPress Trac] #55292: Custom REST Endpoints without
 Regex
Message-ID: <053.48cf4ce289a9f2343520900eb4ab9307@wordpress.org>

#55292: Custom REST Endpoints without Regex
-------------------------------------+-----------------------------
 Reporter:  encoredev                |      Owner:  (none)
     Type:  feature request          |     Status:  assigned
 Priority:  normal                   |  Milestone:  Awaiting Review
Component:  REST API                 |    Version:  5.9.1
 Severity:  normal                   |   Keywords:  2nd-opinion
  Focuses:  accessibility, rest-api  |
-------------------------------------+-----------------------------
 The current way of defining the path for the REST endpoints requires regex
 expressions to define the route variables. That feels like a very
 convoluted way for such a simple and a common task.
 Here is the example from the docs:
 {{{
 /author/(?P<id>\d+)
 }}}
 What I am suggesting is to allow a second way of defining the path which
 will look like that:
 {{{
 /author/{id}
 }}}
 Then this can be parsed and all of the sections in curly braces can be
 replaced with regex expressions matching a string value like that:
 {{{
 /author/(?P<id>\S+).
 }}}
 Which worked fine even with more complicated examples like:
 {{{
 "/author/{category}/{subcategory}/{id}" turns into
 "/author/(?P<category>\S+)/(?P<subcategory>\S+)/(?P<id>\S+)"
 }}}

 And here is the implementation of the parsing function:
 {{{#!php
 <?php
         protected function path_add_regex( string $path ): string {
                 $path_elements = preg_split( '/({[^}]*})/', $path, 0,
 PREG_SPLIT_DELIM_CAPTURE );
                 foreach ( $path_elements as &$element ) {
                         if ( str_contains( $element, '{' ) &&
 str_contains( $element, '}' ) ) {
                                 $element = str_replace( '{', '', $element
 );
                                 $element = str_replace( '}', '', $element
 );
                                 $element = "(?P<{$element}>\S+)";
                         }
                 }
                 $path = implode( '', $path_elements );
                 return $path;
         }
 }}}

 So far I have got around 40 routes defined in the suggested way. They are
 of various complexity and I have never needed to use regex for any of
 them.

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

From noreply at wordpress.org  Wed Mar  2 08:52:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 08:52:00 -0000
Subject: [wp-trac] [WordPress Trac] #54953: Custom css variables in
 theme.json have different keys in 5.9
In-Reply-To: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
References: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
Message-ID: <064.a06bc4639f911ab3814d64ffa5dbab14@wordpress.org>

#54953: Custom css variables in theme.json have different keys in 5.9
--------------------------+---------------------
 Reporter:  walbo         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.2
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------
Changes (by Clorith):

 * milestone:  Awaiting Review => 5.9.2


Comment:

 Upstream report to the Gutenberg repo at
 https://github.com/WordPress/gutenberg/issues/39155

 Adding to the 5.9.2 milestone for tracking until we have a clear direction
 here.

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

From noreply at wordpress.org  Wed Mar  2 10:28:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 10:28:19 -0000
Subject: [wp-trac] [WordPress Trac] #55292: Custom REST Endpoints
 without Regex
In-Reply-To: <053.48cf4ce289a9f2343520900eb4ab9307@wordpress.org>
References: <053.48cf4ce289a9f2343520900eb4ab9307@wordpress.org>
Message-ID: <068.eebcb62ef6729890c04dc86ba0ce12f3@wordpress.org>

#55292: Custom REST Endpoints without Regex
-----------------------------+--------------------------------------
 Reporter:  encoredev        |       Owner:  (none)
     Type:  feature request  |      Status:  closed
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  REST API         |     Version:  5.9.1
 Severity:  normal           |  Resolution:  invalid
 Keywords:  2nd-opinion      |     Focuses:  accessibility, rest-api
-----------------------------+--------------------------------------
Changes (by encoredev):

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


Comment:

 Please delete this ticket

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

From noreply at wordpress.org  Wed Mar  2 10:41:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 10:41:09 -0000
Subject: [wp-trac] [WordPress Trac] #54379: `get_comment_ID()` can cause
 a notice within the `comment_text` filter
In-Reply-To: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
References: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
Message-ID: <063.f47d42e1e72b72fe39f2063e621faec7@wordpress.org>

#54379: `get_comment_ID()` can cause a notice within the `comment_text` filter
--------------------------+---------------------
 Reporter:  dd32          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Comments      |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Wed Mar  2 11:25:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 11:25:14 -0000
Subject: [wp-trac] [WordPress Trac] #22176: Cache the results of the
 posts_request_ids query
In-Reply-To: <048.5df67ddca93554b06d2a0f4b237307c0@wordpress.org>
References: <048.5df67ddca93554b06d2a0f4b237307c0@wordpress.org>
Message-ID: <063.7794c8c086f5aa6e37ca1309673668ff@wordpress.org>

#22176: Cache the results of the posts_request_ids query
-------------------------------------------------+-------------------------
 Reporter:  ryan                                 |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Query                                |     Version:  3.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch 2nd-opinion has-unit-      |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

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


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

From noreply at wordpress.org  Wed Mar  2 11:25:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 11:25:24 -0000
Subject: [wp-trac] [WordPress Trac] #22176: Cache the results of the
 posts_request_ids query
In-Reply-To: <048.5df67ddca93554b06d2a0f4b237307c0@wordpress.org>
References: <048.5df67ddca93554b06d2a0f4b237307c0@wordpress.org>
Message-ID: <063.bff422460451f17d0a4f722a9e4c9127@wordpress.org>

#22176: Cache the results of the posts_request_ids query
-------------------------------------------------+-------------------------
 Reporter:  ryan                                 |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Query                                |     Version:  3.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch 2nd-opinion has-unit-      |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * milestone:  Future Release => 6.0


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

From noreply at wordpress.org  Wed Mar  2 11:26:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 11:26:10 -0000
Subject: [wp-trac] [WordPress Trac] #22176: Cache the results of the
 posts_request_ids query
In-Reply-To: <048.5df67ddca93554b06d2a0f4b237307c0@wordpress.org>
References: <048.5df67ddca93554b06d2a0f4b237307c0@wordpress.org>
Message-ID: <063.c86413a98fd82e350c38b6c8a815f2bf@wordpress.org>

#22176: Cache the results of the posts_request_ids query
-------------------------------------------------+-------------------------
 Reporter:  ryan                                 |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Query                                |     Version:  3.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch 2nd-opinion has-unit-      |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * milestone:  6.0 => Future Release


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

From noreply at wordpress.org  Wed Mar  2 11:30:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 11:30:39 -0000
Subject: [wp-trac] [WordPress Trac] #55283: Text not aligned properly in
 the mobile view
In-Reply-To: <052.59dd929e29ac220c37e9249958cab8d0@wordpress.org>
References: <052.59dd929e29ac220c37e9249958cab8d0@wordpress.org>
Message-ID: <067.a0ca3fc17f68ab4ae8c2369a0dc53615@wordpress.org>

#55283: Text not aligned properly in the mobile view
-------------------------------------------------+-------------------------
 Reporter:  hilayt24                             |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch needs-design-feedback    |     Focuses:  ui, css
  has-screenshots                                |
-------------------------------------------------+-------------------------

Comment (by aezazshekh):

 Hello @hilayt24

 You create this ticket in meta ticket. Because this issue is of meta.

 Thanks.

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

From noreply at wordpress.org  Wed Mar  2 11:44:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 11:44:10 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.02f98d91fd299f0e2a5c913c31fbb876@wordpress.org>

#36907: Improved sticky post query
----------------------------------------+---------------------------
 Reporter:  spacedmonkey                |       Owner:  spacedmonkey
     Type:  enhancement                 |      Status:  assigned
 Priority:  normal                      |   Milestone:  6.0
Component:  Query                       |     Version:  3.5
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:  performance
----------------------------------------+---------------------------
Changes (by spacedmonkey):

 * owner:  (none) => spacedmonkey
 * status:  new => assigned
 * milestone:   => 6.0


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

From noreply at wordpress.org  Wed Mar  2 11:50:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 11:50:21 -0000
Subject: [wp-trac] [WordPress Trac] #22174: _get_non_cached_ids() should
 use wp_cache_get_multi(), if available.
In-Reply-To: <048.9654c1c67804027a34cb6daee918bb2f@wordpress.org>
References: <048.9654c1c67804027a34cb6daee918bb2f@wordpress.org>
Message-ID: <063.70dd2f9e049f76e4134000eaf7707bba@wordpress.org>

#22174: _get_non_cached_ids() should use wp_cache_get_multi(), if available.
--------------------------+------------------------
 Reporter:  ryan          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Cache API     |     Version:  3.4.2
 Severity:  normal        |  Resolution:  duplicate
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------
Changes (by spacedmonkey):

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


Comment:

 Duplicate of #50352.

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

From noreply at wordpress.org  Wed Mar  2 11:51:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 11:51:14 -0000
Subject: [wp-trac] [WordPress Trac] #22174: _get_non_cached_ids() should
 use wp_cache_get_multi(), if available.
In-Reply-To: <048.9654c1c67804027a34cb6daee918bb2f@wordpress.org>
References: <048.9654c1c67804027a34cb6daee918bb2f@wordpress.org>
Message-ID: <063.631a8efe1d6b699cb0e6ff0aafc43816@wordpress.org>

#22174: _get_non_cached_ids() should use wp_cache_get_multi(), if available.
--------------------------+------------------------
 Reporter:  ryan          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Cache API     |     Version:  3.4.2
 Severity:  normal        |  Resolution:  duplicate
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------

Comment (by spacedmonkey):

 Fixed in [48055]

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

From noreply at wordpress.org  Wed Mar  2 12:08:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 12:08:53 -0000
Subject: [wp-trac] [WordPress Trac] #36905: Add caching to
 get_page_by_title
In-Reply-To: <056.ef040fcd3b1e628ea8b55361c56dd2ea@wordpress.org>
References: <056.ef040fcd3b1e628ea8b55361c56dd2ea@wordpress.org>
Message-ID: <071.d64d06f1f547ea0ffba1194f4a8386a7@wordpress.org>

#36905: Add caching to get_page_by_title
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  igmoweb
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Posts, Post Types                    |     Version:  2.1
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch good-first-bug has-unit-   |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 @igmoweb Are you willing to work on this patch still? I am willing to pick
 it up otherwise.

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

From noreply at wordpress.org  Wed Mar  2 12:54:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 12:54:05 -0000
Subject: [wp-trac] [WordPress Trac] #55294: Origin theme's Infinite Scroll
 does not work properly
Message-ID: <060.4a179ceeefacc3eb60689e39bc2ec046@wordpress.org>

#55294: Origin theme's Infinite Scroll does not work properly
------------------------------+-----------------------------
 Reporter:  benflooringgroup  |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  General           |    Version:
 Severity:  normal            |   Keywords:
  Focuses:                    |
------------------------------+-----------------------------
 Hello there

 For our website, www.theflooringgroup.co.uk, the Infinite Scroll does not
 always work properly - for example, on this page;
 https://www.theflooringgroup.co.uk/category/portfolio/portfolio-carpets/,
 the scroll does not go down further at the moment then it should do.

 We have found this to be very temperamental - sometimes it does scroll all
 the way down and sometimes it doesn't.

 Thereby, can you assist in this please?

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

From noreply at wordpress.org  Wed Mar  2 13:21:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 13:21:06 -0000
Subject: [wp-trac] [WordPress Trac] #55220: Legacy widgets lack access
 to some usual server-side globals
In-Reply-To: <054.43d150aa3ca3b7b75495953f66eec8e4@wordpress.org>
References: <054.43d150aa3ca3b7b75495953f66eec8e4@wordpress.org>
Message-ID: <069.799b7a02b162e9b4eecf2aa450330bd0@wordpress.org>

#55220: Legacy widgets lack access to some usual server-side globals
--------------------------+-----------------------------
 Reporter:  noisysocks    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Widgets       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * keywords:   => needs-patch


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

From noreply at wordpress.org  Wed Mar  2 13:24:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 13:24:16 -0000
Subject: [wp-trac] [WordPress Trac] #55291: Can't access Custom CSS with
 theme Twenty Twenty-Two
In-Reply-To: <056.1ac2611b59cebcd2a6941a3ceb32d710@wordpress.org>
References: <056.1ac2611b59cebcd2a6941a3ceb32d710@wordpress.org>
Message-ID: <071.948a37aac668bde325626ebaa9445786@wordpress.org>

#55291: Can't access Custom CSS with theme Twenty Twenty-Two
-------------------------------+------------------------------
 Reporter:  DeveloperWil       |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Themes             |     Version:  5.9.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by audrasjb):

 * keywords:   => reporter-feedback


Comment:

 Hello and welcome back to WordPress Core Trac @DeveloperWil,

 I'm not sure I completely understand you point, but as far as I know (and
 even before block themes appeared), you always loose Custom CSS added with
 the customizer when you switch theme.

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

From noreply at wordpress.org  Wed Mar  2 13:24:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 13:24:35 -0000
Subject: [wp-trac] [WordPress Trac] #55291: Can't access Custom CSS with
 theme Twenty Twenty-Two
In-Reply-To: <056.1ac2611b59cebcd2a6941a3ceb32d710@wordpress.org>
References: <056.1ac2611b59cebcd2a6941a3ceb32d710@wordpress.org>
Message-ID: <071.aba82aaf9e453dad5a0e45c29f60ffb5@wordpress.org>

#55291: Can't access Custom CSS with theme Twenty Twenty-Two
-------------------------------+------------------------------
 Reporter:  DeveloperWil       |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Themes             |     Version:  5.9
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by audrasjb):

 * version:  5.9.1 => 5.9


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

From noreply at wordpress.org  Wed Mar  2 14:36:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 14:36:53 -0000
Subject: [wp-trac] [WordPress Trac] #10886: WordPress should not
 unnecessarily query posts at page load
In-Reply-To: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
References: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
Message-ID: <068.343360098ead2f89f553ce96b9d0e68d@wordpress.org>

#10886: WordPress should not unnecessarily query posts at page load
-------------------------------------------------+-------------------------
 Reporter:  junsuijin                            |       Owner:
                                                 |  spacedmonkey
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Bootstrap/Load                       |     Version:  2.8.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests early has-patch       |     Focuses:
  needs-dev-note                                 |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * owner:  (none) => spacedmonkey


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

From noreply at wordpress.org  Wed Mar  2 14:48:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 14:48:01 -0000
Subject: [wp-trac] [WordPress Trac] #55295: Child Thema can't export
 templates
Message-ID: <051.01327736193964661bf3f8f42b1c4b01@wordpress.org>

#55295: Child Thema can't export templates
--------------------------+-----------------------------
 Reporter:  emeldir       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Themes        |    Version:  5.9.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 I added a child theme for twenty twenty-two. When I tried to export the
 template part I was working on, it failed. It either produced a zip you
 could not open or gave a generic error message "An error occurred while
 creating the site export."
 Switching back to the parent theme resolves the issue, export is working
 fine there.

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

From noreply at wordpress.org  Wed Mar  2 14:58:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 14:58:25 -0000
Subject: [wp-trac] [WordPress Trac] #55212: PHP Notice: Array to string
 conversion in admin ajax points.
In-Reply-To: <048.1eddc1f78fdac1ef1b1389f7d6a0dfd0@wordpress.org>
References: <048.1eddc1f78fdac1ef1b1389f7d6a0dfd0@wordpress.org>
Message-ID: <063.018c9cd55eebb49f8ebb8c545d6be738@wordpress.org>

#55212: PHP Notice: Array to string conversion in admin ajax points.
----------------------------+-----------------------------
 Reporter:  dd32            |       Owner:  SergeyBiryukov
     Type:  defect (bug)    |      Status:  closed
 Priority:  lowest          |   Milestone:  6.0
Component:  Administration  |     Version:
 Severity:  trivial         |  Resolution:  fixed
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52813" 52813]:
 {{{
 #!CommitTicketReference repository="" revision="52813"
 Administration: Require a valid action parameter to be set for `admin-
 ajax.php` requests.

 This avoids `Array to string conversion` PHP notices when an array is
 passed as the `action` parameter.

 Additionally, send an appropriate HTTP response status code when an
 invalid action is passed to `admin-post.php`.

 Follow-up to [13175], [19738], [41120], [41926].

 Props dd32.
 Fixes #55212.
 }}}

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

From noreply at wordpress.org  Wed Mar  2 15:00:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 15:00:58 -0000
Subject: [wp-trac] [WordPress Trac] #55272: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
References: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
Message-ID: <074.284dead2bc3d089548d4d66aea2bdcf9@wordpress.org>

#55272: The New Layout Fix For Plugin Install Page
-------------------------------------+-------------------------------------
 Reporter:  sharjeelkhanvmi          |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Plugins                  |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  reporter-feedback        |     Focuses:  ui, css,
  needs-design-feedback              |  administration
-------------------------------------+-------------------------------------

Comment (by joyously):

 > I did not get your first point.

 The mismatched version error is shown at the top of the box. This alone
 can make the boxes uneven.
 ''(This screenshot is my normal window width.)''
 [[Image(https://i.postimg.cc/8zsLdQjp/Add-Plugins.jpg)]]
 ------

 > Yes if we add more description lines to show then it mismatches the
 alignment of the boxes

 I think it's more important to see the complete sentence of the
 description than to have even boxes.

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

From noreply at wordpress.org  Wed Mar  2 15:11:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 15:11:03 -0000
Subject: [wp-trac] [WordPress Trac] #10886: WordPress should not
 unnecessarily query posts at page load
In-Reply-To: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
References: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
Message-ID: <068.cec9e95b7b7a7a5d79309e87c67cc5f2@wordpress.org>

#10886: WordPress should not unnecessarily query posts at page load
-------------------------------------------------+-------------------------
 Reporter:  junsuijin                            |       Owner:
                                                 |  spacedmonkey
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Bootstrap/Load                       |     Version:  2.8.4
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-unit-tests early has-patch       |     Focuses:
  needs-dev-note                                 |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

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


Comment:

 In [changeset:"52814" 52814]:
 {{{
 #!CommitTicketReference repository="" revision="52814"
 Bootstrap/Load: Stop unnecessary queries when using the `do_parse_request`
 filter.

 Developers of plugins and themes can use the `do_parse_request` filter to
 hot-wire requests and hook in early to render custom pages. However, even
 through these request may not need post queries and 404 lookups to be run,
 they run anyway. This can results in unnecessary SQL queries running on
 these requests. By adding a return value to the `parse_request` method of
 the `WP` class, these queries can now be skipped.

 Props junsuijin, ryan, westi, sivel, dd32, wonderboymusic, arnee, tyxla,
 DrewAPicture, lukecavanagh, SergeyBiryukov, davidbaumwald, Spacedmonkey,
 pbearne.
 Fixes #10886.
 }}}

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

From noreply at wordpress.org  Wed Mar  2 15:38:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 15:38:41 -0000
Subject: [wp-trac] [WordPress Trac] #10886: WordPress should not
 unnecessarily query posts at page load
In-Reply-To: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
References: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
Message-ID: <068.16cd64f96f24a6b05b09f58240bf5ca2@wordpress.org>

#10886: WordPress should not unnecessarily query posts at page load
-------------------------------------------------+-------------------------
 Reporter:  junsuijin                            |       Owner:
                                                 |  spacedmonkey
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Bootstrap/Load                       |     Version:  2.8.4
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-unit-tests early has-patch       |     Focuses:
  needs-dev-note                                 |  performance
-------------------------------------------------+-------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52815" 52815]:
 {{{
 #!CommitTicketReference repository="" revision="52815"
 Docs: Add a `@since` note for `WP::parse_request()` about the new return
 value.

 Includes minor code layout fixes for consistency. Additionally, this moves
 a more general unit test above the more specific one.

 Follow-up to [52814].

 See #10886.
 }}}

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

From noreply at wordpress.org  Wed Mar  2 15:44:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 15:44:38 -0000
Subject: [wp-trac] [WordPress Trac] #55295: Editor: Child Theme can't
 export templates (was: Child Thema can't export templates)
In-Reply-To: <051.01327736193964661bf3f8f42b1c4b01@wordpress.org>
References: <051.01327736193964661bf3f8f42b1c4b01@wordpress.org>
Message-ID: <066.7332d307e3bedaea764d73efb4c54c43@wordpress.org>

#55295: Editor: Child Theme can't export templates
--------------------------+------------------------------
 Reporter:  emeldir       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by emeldir):

 * component:  Themes => Editor


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

From noreply at wordpress.org  Wed Mar  2 16:03:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 16:03:40 -0000
Subject: [wp-trac] [WordPress Trac] #55272: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
References: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
Message-ID: <074.17d2cbd9880f03eae1aed6dcfa9026d9@wordpress.org>

#55272: The New Layout Fix For Plugin Install Page
-------------------------------------+-------------------------------------
 Reporter:  sharjeelkhanvmi          |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Plugins                  |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  reporter-feedback        |     Focuses:  ui, css,
  needs-design-feedback              |  administration
-------------------------------------+-------------------------------------

Comment (by SergeyBiryukov):

 Replying to [comment:7 sharjeelkhanvmi]:
 > What's that?

 Just editing the keywords and focus for better visibility, see
 [https://make.wordpress.org/core/handbook/contribute/trac/keywords/ Trac
 Workflow Keywords].

 Replying to [comment:8 joyously]:
 > I think it's more important to see the complete sentence of the
 description than to have even boxes.

 I tend to agree, even boxes may look nice at a glance but it seems like
 they are not really feasible if we take full descriptions and plugin
 compatibility notices into account.

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

From noreply at wordpress.org  Wed Mar  2 16:05:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 16:05:29 -0000
Subject: [wp-trac] [WordPress Trac] #55294: Origin theme's Infinite
 Scroll does not work properly
In-Reply-To: <060.4a179ceeefacc3eb60689e39bc2ec046@wordpress.org>
References: <060.4a179ceeefacc3eb60689e39bc2ec046@wordpress.org>
Message-ID: <075.bdd50a647923ffec62b6ca858387bc6e@wordpress.org>

#55294: Origin theme's Infinite Scroll does not work properly
------------------------------+----------------------
 Reporter:  benflooringgroup  |       Owner:  (none)
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  General           |     Version:
 Severity:  normal            |  Resolution:  invalid
 Keywords:                    |     Focuses:
------------------------------+----------------------
Changes (by SergeyBiryukov):

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


Comment:

 Hi there, welcome to WordPress Trac! Thanks for the ticket.

 I'm sorry to hear you are having issues with your website. Please note
 that this Trac is used for enhancements and bug reporting for the
 WordPress core software, not for individual support questions.

 Please try the support forums to get help with your site:
 https://wordpress.org/support/forums/.

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

From noreply at wordpress.org  Wed Mar  2 16:43:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 16:43:49 -0000
Subject: [wp-trac] [WordPress Trac] #55289: Large image fails to create
 a `scaled` version and subsizes
In-Reply-To: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
References: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
Message-ID: <065.02b3eb75eed3ff6779546c5d34e6b9d0@wordpress.org>

#55289: Large image fails to create a `scaled` version and subsizes
--------------------------+------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by adamsilverstein):

 * Attachment "Media Library ‹ test — WordPress 2022-03-02 09-43-29.jpg"
 added.


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

From noreply at wordpress.org  Wed Mar  2 16:45:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 16:45:34 -0000
Subject: [wp-trac] [WordPress Trac] #55289: Large image fails to create
 a `scaled` version and subsizes
In-Reply-To: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
References: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
Message-ID: <065.99e403bbe0836673fab3300b04c3f3f2@wordpress.org>

#55289: Large image fails to create a `scaled` version and subsizes
--------------------------+------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by adamsilverstein):

 @mitogh thanks for raising this issue.

 in my testing, when I uploaded a VERY large image, I got an error "{file}
 exceeds the maximum upload size for this site." when I tested with your
 image, I got a server error that at least suggested I try a smaller image:
 "The server cannot process the image. This can happen if the server is
 busy or does not have enough resources to complete the task. Uploading a
 smaller image may help. Suggested maximum size is 2560 pixels."

 How would you propose improving this?

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

From noreply at wordpress.org  Wed Mar  2 16:47:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 16:47:31 -0000
Subject: [wp-trac] [WordPress Trac] #55295: Editor: Child Theme can't
 export templates
In-Reply-To: <051.01327736193964661bf3f8f42b1c4b01@wordpress.org>
References: <051.01327736193964661bf3f8f42b1c4b01@wordpress.org>
Message-ID: <066.82c41b470241616cc2d18968dbd8f732@wordpress.org>

#55295: Editor: Child Theme can't export templates
--------------------------+------------------------------
 Reporter:  emeldir       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by emeldir):

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


Comment:

 Added this over at the Gutenberg repro.
 Prob fits better there.

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

From noreply at wordpress.org  Wed Mar  2 17:04:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:04:17 -0000
Subject: [wp-trac] [WordPress Trac] #36905: Add caching to
 get_page_by_title
In-Reply-To: <056.ef040fcd3b1e628ea8b55361c56dd2ea@wordpress.org>
References: <056.ef040fcd3b1e628ea8b55361c56dd2ea@wordpress.org>
Message-ID: <071.44cd12acf94779a0bd23b055e8518c80@wordpress.org>

#36905: Add caching to get_page_by_title
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  igmoweb
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Posts, Post Types                    |     Version:  2.1
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch good-first-bug has-unit-   |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------

Comment (by igmoweb):

 @spacedmonkey Feel free to take it again, thanks :)

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

From noreply at wordpress.org  Wed Mar  2 17:13:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:13:15 -0000
Subject: [wp-trac] [WordPress Trac] #55290: Not all image edits are
 applied to all subsizes
In-Reply-To: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
References: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
Message-ID: <065.6a6cb386f5149272e750367977331279@wordpress.org>

#55290: Not all image edits are applied to all subsizes
--------------------------+------------------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  administration, performance
--------------------------+------------------------------------------

Comment (by adamsilverstein):

 Good catch @mitogh! Looks like some conditional checks for in image-
 edit.php aren't working as expected.

 In my testing this happened when the i rotated to the vertical position.
 rotating again and saving my medium_large size was correctly edited.
 flipping images always seemed to work. cropping worked until i tried a
 vertical thin crop, then some sizes were saved and others not.

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

From noreply at wordpress.org  Wed Mar  2 17:22:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:22:19 -0000
Subject: [wp-trac] [WordPress Trac] #55296: Issue with Images
Message-ID: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>

#55296: Issue with Images
--------------------------+-----------------------------
 Reporter:  lyntreeio     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.1
 Severity:  critical      |   Keywords:  needs-patch
  Focuses:                |
--------------------------+-----------------------------
 Hello,

 I've have two clients report to me there websites are missing image links.
 I've spoken to my host and they think it could be a cache issue. Images
 are on the media library but on the website they have all broken links?

 https://i0.wp.com/smoothssecrets.co.uk/wp-
 content/uploads/2020/11/rsz_1lady.png?w=1019&ssl=1

 Why would my client, have images coming from that address when the images
 are hosted directly on the server?

 I have tried fixing the database and no php errors are showing apart from
 this.  I had to restore the last clients website and will have to do the
 same thing.

 Can you please look into this, both websites are running the latest
 version of WordPress and I do not know when this happened apart from the
 last 6 months.

 It has also been ruled out as a plugin

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

From noreply at wordpress.org  Wed Mar  2 17:24:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:24:27 -0000
Subject: [wp-trac] [WordPress Trac] #55296: Issue with Images
In-Reply-To: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
References: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
Message-ID: <068.dcc006bb50b484fe98c8fb6ee960a253@wordpress.org>

#55296: Issue with Images
--------------------------+------------------------------
 Reporter:  lyntreeio     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  critical      |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by lyntreeio):

 * Attachment "Screenshot 2022-03-02 at 17.23.19.png" added.


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

From noreply at wordpress.org  Wed Mar  2 17:24:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:24:37 -0000
Subject: [wp-trac] [WordPress Trac] #55296: Issue with Images
In-Reply-To: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
References: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
Message-ID: <068.94edd89d6226751a110e8bf49d509246@wordpress.org>

#55296: Issue with Images
--------------------------+------------------------------
 Reporter:  lyntreeio     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  critical      |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by lyntreeio):

 * Attachment "Screenshot 2022-03-02 at 17.23.27.png" added.


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

From noreply at wordpress.org  Wed Mar  2 17:24:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:24:45 -0000
Subject: [wp-trac] [WordPress Trac] #55296: Issue with Images
In-Reply-To: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
References: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
Message-ID: <068.fe8ff0b9af15d20141c733e2a158cf0a@wordpress.org>

#55296: Issue with Images
--------------------------+------------------------------
 Reporter:  lyntreeio     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  critical      |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by lyntreeio):

 * Attachment "Screenshot 2022-03-02 at 17.23.36.png" added.


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

From noreply at wordpress.org  Wed Mar  2 17:26:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:26:44 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
Message-ID: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------+-------------------------------------------------
 Reporter:  costdev      |      Owner:  (none)
     Type:  defect       |     Status:  new
  (bug)                  |
 Priority:  normal       |  Milestone:  6.0
Component:  General      |    Version:  trunk
 Severity:  normal       |   Keywords:  good-first-bug needs-patch needs-
  Focuses:               |  testing has-testing-info
-------------------------+-------------------------------------------------
 `$is_edge` is `true` when "Edge" is detected.

 However, user agents for Edge have changed such that "Edg" is the only
 consistent substring across devices. As a result, `$is_edge` returns
 `false`.

 Changing the substring to "Edg" in `src/wp-includes/vars.php:68` seems to
 fix this.

 Steps to reproduce and test the solution:
 1. Add this to `functions.php`:

 {{{#!php
 global $is_edge;
 die( var_export( $is_edge, true ) );
 }}}

 2. Load any page. `false` should be displayed.
 3. Change "Edge" to "Edg" in `src/wp-includes/vars.php:68`.
 4. Reload the page. `true` should now be displayed.

 Reference: [https://docs.microsoft.com/en-us/microsoft-edge/web-platform
 /user-agent-guidance#identifiers-for-microsoft-edge-on-various-platforms
 Microsoft Docs - Identifiers for Microsoft Edge on various platforms]

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

From noreply at wordpress.org  Wed Mar  2 17:35:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:35:54 -0000
Subject: [wp-trac] [WordPress Trac] #55290: Not all image edits are
 applied to all subsizes
In-Reply-To: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
References: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
Message-ID: <065.6d9eda8ba69cf4bbb947101aab2ecdaa@wordpress.org>

#55290: Not all image edits are applied to all subsizes
--------------------------+------------------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  administration, performance
--------------------------+------------------------------------------

Comment (by mitogh):

 Right, it seems like the issue happens for rotation specifically on images
 that do not have dimensions like a landscape or portrait image if is
 rotated the dimensions are different, flip works normally on my end due to
 the image dimensions are not modified from the original image.

 Let me know in case you have any additional questions.  @adamsilverstein,
 thanks for taking a look and replicating the steps for this issue.

 ''If time allows I can try to find a patch for this one as well.''

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

From noreply at wordpress.org  Wed Mar  2 17:55:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:55:17 -0000
Subject: [wp-trac] [WordPress Trac] #55298: How do I turn off this mandatory
 verification for new users accessing the site?
Message-ID: <053.c0dd536325457d2abae6a247b525c107@wordpress.org>

#55298: How do I turn off this mandatory verification for new users accessing the
site?
---------------------------+-----------------------------
 Reporter:  jason7912      |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  General        |    Version:  5.9.1
 Severity:  normal         |   Keywords:
  Focuses:  accessibility  |
---------------------------+-----------------------------
 **Our system thinks you might be a robot!
 We're really sorry about this, but it's getting harder and harder to tell
 the difference between humans and bots these days.
 Please complete the captcha below to prove you're a human and proceed to
 the page you're trying to reach.


 This page requires cookies to be enabled in your browser settings. Please
 check this setting and enable cookies (if disabled). sid:343---**
 Why do buyers get this message when they visit my website? In between, the
 visiting user is also required to enter a verification code. What is the
 best way to turn off this mandatory input? Please help!

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

From noreply at wordpress.org  Wed Mar  2 17:56:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 17:56:26 -0000
Subject: [wp-trac] [WordPress Trac] #55298: How do I turn off this
 mandatory verification for new users accessing the site?
In-Reply-To: <053.c0dd536325457d2abae6a247b525c107@wordpress.org>
References: <053.c0dd536325457d2abae6a247b525c107@wordpress.org>
Message-ID: <068.0a7e170997dba1cbef5c6085b8884519@wordpress.org>

#55298: How do I turn off this mandatory verification for new users accessing the
site?
--------------------------+------------------------------
 Reporter:  jason7912     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility
--------------------------+------------------------------
Changes (by jason7912):

 * Attachment "微信图片_20220303015535.png" added.


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

From noreply at wordpress.org  Wed Mar  2 18:01:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 18:01:27 -0000
Subject: [wp-trac] [WordPress Trac] #55296: Issue with Images
In-Reply-To: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
References: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
Message-ID: <068.4cb0883313d77819b2932fd96fb9656a@wordpress.org>

#55296: Issue with Images
--------------------------+------------------------------
 Reporter:  lyntreeio     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  critical      |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+------------------------------
Changes (by SergeyBiryukov):

 * keywords:  needs-patch => close


Comment:

 Replying to [ticket:55296 lyntreeio]:
 > https://i0.wp.com/smoothssecrets.co.uk/wp-
 content/uploads/2020/11/rsz_1lady.png?w=1019&ssl=1
 >
 > Why would my client, have images coming from that address when the
 images are hosted directly on the server?

 Hi there, welcome to WordPress Trac! Thanks for the ticket.

 I'm sorry to hear you are having issues with your website. The site
 appears to use the [https://jetpack.com/support/site-accelerator/ Jetpack
 Site Accelerator] module (formerly Photon).

 Opening the linked image URL displays an error message:
 {{{
 We cannot complete this request, remote server returned an unexpected
 status code (400)
 }}}

 WordPress core does not have a CDN module like that, so I would suggest
 trying the support forums to get help with your site:
 https://wordpress.org/support/forums/, or the
 [https://wordpress.org/support/plugin/jetpack/ Jetpack support forums]
 specifically.

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

From noreply at wordpress.org  Wed Mar  2 18:01:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 18:01:55 -0000
Subject: [wp-trac] [WordPress Trac] #48634: Images disappeared after
 updating to 5.3
In-Reply-To: <058.860d3673e341d8451f5823d2c4db7c10@wordpress.org>
References: <058.860d3673e341d8451f5823d2c4db7c10@wordpress.org>
Message-ID: <073.9778261fa57daf999378ece602f5d1c0@wordpress.org>

#48634: Images disappeared after updating to 5.3
----------------------------+----------------------
 Reporter:  bluerootsradio  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Media           |     Version:  5.3
 Severity:  major           |  Resolution:  invalid
 Keywords:                  |     Focuses:
----------------------------+----------------------
Changes (by SergeyBiryukov):

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


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

From noreply at wordpress.org  Wed Mar  2 18:07:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 18:07:41 -0000
Subject: [wp-trac] [WordPress Trac] #55298: How do I turn off this
 mandatory verification for new users accessing the site?
In-Reply-To: <053.c0dd536325457d2abae6a247b525c107@wordpress.org>
References: <053.c0dd536325457d2abae6a247b525c107@wordpress.org>
Message-ID: <068.eaed4deb17498657cecb38720226597d@wordpress.org>

#55298: How do I turn off this mandatory verification for new users accessing the
site?
--------------------------+----------------------------
 Reporter:  jason7912     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.9.1
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  accessibility
--------------------------+----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 Hi there, welcome to WordPress Trac! Thanks for the ticket.

 I'm sorry to hear you are having issues with your website. WordPress core
 does not have a verification page like that, it may be created by a plugin
 or your hosting provider. Please note that this Trac is used for
 enhancements and bug reporting for the WordPress core software, not for
 individual support questions.

 Please try the support forums to get help with your site:
 https://wordpress.org/support/forums/.

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

From noreply at wordpress.org  Wed Mar  2 18:11:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 18:11:01 -0000
Subject: [wp-trac] [WordPress Trac] #55296: Issue with Images
In-Reply-To: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
References: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
Message-ID: <068.2e79e601d7d247e2d4c18c88efcf3cc8@wordpress.org>

#55296: Issue with Images
--------------------------+------------------------------
 Reporter:  lyntreeio     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  critical      |  Resolution:  worksforme
 Keywords:  close         |     Focuses:
--------------------------+------------------------------
Changes (by lyntreeio):

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


Comment:

 Hi,

 Thank you for letting me know this, I'll take it up directly with JetPack
 and see what can be done to resolve this issue. Kindest Regards, Bridget

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

From noreply at wordpress.org  Wed Mar  2 18:43:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 18:43:25 -0000
Subject: [wp-trac] [WordPress Trac] #55289: Large image fails to create
 a `scaled` version and subsizes
In-Reply-To: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
References: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
Message-ID: <065.198d7f73afdf0b93cec45d2612b7c509@wordpress.org>

#55289: Large image fails to create a `scaled` version and subsizes
--------------------------+------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by mitogh):

 @adamsilverstein interesting I was not able to face any of those errors
 and the image was uploaded, the problem was that the subsizes where not
 created, my current size limit is 100MB tho, in my setup Imagemagick is
 used to process the images.

 Looking into more detail (specifically into the Imagemagick
 implementation) looks like the problem is because it creates a larger
 image 5 times larger actually than the uploaded image, which for larger
 images like the one from this issue consumes large portion of memory.

 - https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-
 includes/class-wp-image-editor-imagick.php#L363

 From my point of view, when a large image is uploaded or when the image is
 bigger than the threshold there's no real need/benefit in resampling as
 images are going to be created in smaller sizes instead.

 I can explore a bit more for imagemagick, but just commenting that line of
 code makes the rest of the subsizes work as expected. Maybe some
 additional logic can be added in place to consider the scenario when the
 resampling is not required.

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

From noreply at wordpress.org  Wed Mar  2 18:51:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 18:51:25 -0000
Subject: [wp-trac] [WordPress Trac] #55299: website shutdown
Message-ID: <058.1bf21ea580d37b4be203eb8d7c598bab@wordpress.org>

#55299: website shutdown
----------------------------+-----------------------------
 Reporter:  arnaudtexier64  |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Plugins         |    Version:
 Severity:  blocker         |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 Hi,

 my website is down due to a problem I can't fix. I updated my PHP to 7.4
 (stable64) but impossible to find a solution, and access to my recovery
 mode)
 Can you help me ?

 cheers,

 Arnaud

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

From noreply at wordpress.org  Wed Mar  2 18:57:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 18:57:47 -0000
Subject: [wp-trac] [WordPress Trac] #55300: tests for WP_List_Util::pluck
 and WP_List_Util::sort
Message-ID: <051.dd5ff02912bce1bb03a5640324c5d38c@wordpress.org>

#55300: tests for WP_List_Util::pluck and WP_List_Util::sort
------------------------------+-----------------------------
 Reporter:  pbearne           |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  Build/Test Tools  |    Version:
 Severity:  normal            |   Keywords:
  Focuses:                    |
------------------------------+-----------------------------
 I created so test for the WP_List_Util::pluck and WP_List_Util::sort
 function and fixed a couple of edge cases

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

From noreply at wordpress.org  Wed Mar  2 19:01:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 19:01:36 -0000
Subject: [wp-trac] [WordPress Trac] #55299: website shutdown
In-Reply-To: <058.1bf21ea580d37b4be203eb8d7c598bab@wordpress.org>
References: <058.1bf21ea580d37b4be203eb8d7c598bab@wordpress.org>
Message-ID: <073.eddcc9b1573260beb4e60b0065d3f3bf@wordpress.org>

#55299: website shutdown
----------------------------+----------------------
 Reporter:  arnaudtexier64  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  General         |     Version:
 Severity:  normal          |  Resolution:  invalid
 Keywords:                  |     Focuses:
----------------------------+----------------------
Changes (by costdev):

 * status:  new => closed
 * resolution:   => invalid
 * component:  Plugins => General
 * severity:  blocker => normal
 * milestone:  Awaiting Review =>


Comment:

 Hi @arnaudtexier64, welcome to Trac!

 Sorry to hear that you're having trouble with your website.

 Trac is for the development of WordPress Core rather than providing
 WordPress support. You can get some help from the folks over on
 [https://wordpress.org/support/forums/ the support forums].

 Best of luck!

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

From noreply at wordpress.org  Wed Mar  2 19:13:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 19:13:41 -0000
Subject: [wp-trac] [WordPress Trac] #55293: Getting malware attack per
 day
In-Reply-To: <054.69fd4c507263fa6692f6b4e6859b9f3e@wordpress.org>
References: <054.69fd4c507263fa6692f6b4e6859b9f3e@wordpress.org>
Message-ID: <069.d63d3800b021e31b9104d068136f718d@wordpress.org>

#55293: Getting malware attack per day
--------------------------+----------------------
 Reporter:  ravipaswan    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by costdev):

 * status:  new => closed
 * focuses:  performance, privacy =>
 * severity:  critical => normal
 * component:  Security => General
 * version:  5.9.1 =>
 * milestone:  Awaiting Review =>
 * resolution:   => invalid


Comment:

 Hi @ravipaswan, welcome to Trac!

 Sorry to hear that you're having trouble with your website.

 Trac is for the development of WordPress Core rather than providing
 WordPress support. You can get some help from the folks over on
 [https://wordpress.org/support/forums/ the support forums].

 Best of luck!

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

From noreply at wordpress.org  Wed Mar  2 19:45:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 19:45:42 -0000
Subject: [wp-trac] [WordPress Trac] #54915: Username,
 email and password fields must be ltr in rtl locale
In-Reply-To: <053.4f38abea21a29f9eb209358027b8e501@wordpress.org>
References: <053.4f38abea21a29f9eb209358027b8e501@wordpress.org>
Message-ID: <068.b5cfccadf9b5cb7f5f42d6c09ec0a653@wordpress.org>

#54915: Username, email and password fields must be ltr in rtl locale
-------------------------------------+-------------------------------------
 Reporter:  man4toman                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch has-         |     Focuses:  ui, css, rtl,
  screenshots has-testing-info       |  administration
-------------------------------------+-------------------------------------
Changes (by sabernhardt):

 * Attachment "54915.diff" added.


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

From noreply at wordpress.org  Wed Mar  2 19:47:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 19:47:40 -0000
Subject: [wp-trac] [WordPress Trac] #54915: Username,
 email and password fields must be ltr in rtl locale
In-Reply-To: <053.4f38abea21a29f9eb209358027b8e501@wordpress.org>
References: <053.4f38abea21a29f9eb209358027b8e501@wordpress.org>
Message-ID: <068.6a2407445420e69e56d35a6ce3dce7f2@wordpress.org>

#54915: Username, email and password fields must be ltr in rtl locale
-------------------------------------+-------------------------------------
 Reporter:  man4toman                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots has-     |     Focuses:  ui, css, rtl,
  testing-info has-patch             |  administration
-------------------------------------+-------------------------------------
Changes (by sabernhardt):

 * keywords:  needs-patch has-screenshots has-testing-info => has-
     screenshots has-testing-info has-patch
 * milestone:  Awaiting Review => 6.0


Comment:

 The common.css file has had a `.ltr` class for this, but that is not
 included on the login screen. I added the class to forms.css and included
 password-type inputs.

 {{{
 /* rtl:ignore */
 .ltr,
 input[type="password"],
 input[type="email"],
 input[type="url"] {
         direction: ltr;
 }
 }}}

 The patch adds the `ltr` class to several inputs.
 **Login:** username, password
 **Install:** username, password
 **User Edit (Profile):** username, password, application password
 **New User:** username, password

 I expect I missed at least one more input that needs the class, too.

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

From noreply at wordpress.org  Wed Mar  2 19:52:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 19:52:09 -0000
Subject: [wp-trac] [WordPress Trac] #55289: Large image fails to create
 a `scaled` version and subsizes
In-Reply-To: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
References: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
Message-ID: <065.4681f3f101b8fcb1706a374625d9a6a6@wordpress.org>

#55289: Large image fails to create a `scaled` version and subsizes
--------------------------+------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by adamsilverstein):

 Interesting! The comment there implies this makes resizing more
 efficient..

 This was introduced in https://github.com/WordPress/wordpress-
 develop/commit/e2d2c45c6b7ed013139be7ab8f3833750684e28d maybe we can skip
 doing this when the original file is already so large? cc: @mikeschroder

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

From noreply at wordpress.org  Wed Mar  2 19:54:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 19:54:58 -0000
Subject: [wp-trac] [WordPress Trac] #9883: Password shows under Settings
 / Writing
In-Reply-To: <051.e255d5d4a3c9798d3dd132222867f489@wordpress.org>
References: <051.e255d5d4a3c9798d3dd132222867f489@wordpress.org>
Message-ID: <066.0a11d3f53a3740f8d16d5ad652b932e2@wordpress.org>

#9883: Password shows under Settings / Writing
-------------------------------------------------+-------------------------
 Reporter:  mastrup                              |       Owner:  (none)
     Type:  enhancement                          |      Status:  assigned
 Priority:  low                                  |   Milestone:  6.0
Component:  Administration                       |     Version:  2.7.1
 Severity:  trivial                              |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:  ui,
  testing-info                                   |  accessibility
-------------------------------------------------+-------------------------

Comment (by sabernhardt):

 The updated patch has a problem with password managers, just as the login
 screen does (#48222). The previous version of the PR used code from the
 Profile screen's New Password visibility button instead of the login's
 icon-only style.

 I also have these concerns with the latest version:
 1. When the page loads, it automatically focuses on the password field,
 but there are important fields before that.
 2. The `ltr` class should not be removed from the text/password input. See
 #54915.

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

From noreply at wordpress.org  Wed Mar  2 20:30:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 20:30:19 -0000
Subject: [wp-trac] [WordPress Trac] #53965: Legacy widgets used inside a
 normal block fail when salts are changed
In-Reply-To: <055.b722b642096472f6051cf9982a1f780f@wordpress.org>
References: <055.b722b642096472f6051cf9982a1f780f@wordpress.org>
Message-ID: <070.d370e86e96fcad15cf4e980ea64fb565@wordpress.org>

#53965: Legacy widgets used inside a normal block fail when salts are changed
--------------------------+---------------------------------------
 Reporter:  Enchiridion   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Widgets       |     Version:  5.8
 Severity:  major         |  Resolution:
 Keywords:                |     Focuses:  administration, rest-api
--------------------------+---------------------------------------

Comment (by CockpitSeeker):

 +1 This is big and was unavoidable here after switching to the block
 system with pre-existing legacy widgets. I would go as far as saying this
 is a major deterrent against the whole block paradigm adoption. Suffice to
 say, at this date the "Classic Widgets" plugin has 900,000+ installs...

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

From noreply at wordpress.org  Wed Mar  2 21:24:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 21:24:14 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.957eb22afabfd317d782e95f3a9a93e0@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug needs-patch needs-    |     Focuses:
  testing has-testing-info                       |
-------------------------------------------------+-------------------------
Changes (by abdullahramzan):

 * Attachment "55297-03032022.diff" added.

 Fix for 55297

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

From noreply at wordpress.org  Wed Mar  2 21:27:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 21:27:12 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.7b83d2525e136e872b241442b8699e44@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch                                      |
-------------------------------------------------+-------------------------
Changes (by abdullahramzan):

 * keywords:  good-first-bug needs-patch needs-testing has-testing-info =>
     good-first-bug has-testing-info has-patch


Comment:

 Hi @costdev,

 Thanks for submitting the ticket with a useful guide & test information. I
 have created a patch & tested it locally. It looks good to me. Webpage
 returning true when opening in Microsoft Edge.

 Best Regards,

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

From noreply at wordpress.org  Wed Mar  2 21:46:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 21:46:56 -0000
Subject: [wp-trac] [WordPress Trac] #54042: Extending wpdb::prepare() to
 support table/field names, and IN() operator
In-Reply-To: <056.f04485e63ca681f362f38671080f1fa1@wordpress.org>
References: <056.f04485e63ca681f362f38671080f1fa1@wordpress.org>
Message-ID: <071.946387c8b149b5a8b5957e894e386283@wordpress.org>

#54042: Extending wpdb::prepare() to support table/field names, and IN() operator
-------------------------------------------------+-------------------------
 Reporter:  craigfrancis                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Database                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:
  testing early has-unit-tests                   |
-------------------------------------------------+-------------------------
Changes (by craigfrancis):

 * milestone:  Future Release => 6.0


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

From noreply at wordpress.org  Wed Mar  2 22:21:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 22:21:44 -0000
Subject: [wp-trac] [WordPress Trac] #42952: Add comments about JS
 removal of message query_arg
In-Reply-To: <054.9aa6fe6f3265ee6371064cceb1a710a2@wordpress.org>
References: <054.9aa6fe6f3265ee6371064cceb1a710a2@wordpress.org>
Message-ID: <069.0abe71b93c62e1f7f3cf1a5f4c156198@wordpress.org>

#42952: Add comments about JS removal of message query_arg
----------------------------+-----------------------------------
 Reporter:  davidsword      |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  4.9.1
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  docs, administration
----------------------------+-----------------------------------
Changes (by davidbaumwald):

 * keywords:   => needs-patch
 * component:  Comments => Administration


Comment:

 @davidsword Thanks for the ticket!  This technically is not related to the
 `Comments` component and pertains to docs-type comments, which I think is
 what you're requesting.  Setting the component to `Administration` so it
 can be picked up by that group.

 Specifically looking at this issue, it seems the needs to document this a
 bit better was realized back in [25819].

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

From noreply at wordpress.org  Wed Mar  2 22:23:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 22:23:22 -0000
Subject: [wp-trac] [WordPress Trac] #54379: `get_comment_ID()` can cause
 a notice within the `comment_text` filter
In-Reply-To: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
References: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
Message-ID: <063.c5d56a639989087893b05039ce97915f@wordpress.org>

#54379: `get_comment_ID()` can cause a notice within the `comment_text` filter
--------------------------+----------------------------
 Reporter:  dd32          |       Owner:  davidbaumwald
     Type:  defect (bug)  |      Status:  reviewing
 Priority:  normal        |   Milestone:  6.0
Component:  Comments      |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+----------------------------
Changes (by davidbaumwald):

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


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

From noreply at wordpress.org  Wed Mar  2 23:22:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 02 Mar 2022 23:22:51 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly
 with Odysee.com (half working)
In-Reply-To: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
References: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
Message-ID: <070.d74d0c0109f13984350972fb7289ee89@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+------------------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+------------------------------

Comment (by peterwilsoncc):

 Can you please answer each of the questions of the
 [https://make.wordpress.org/core/handbook/contribute/design-decisions
 /#adding-new-oembed-providers checklist for adding new oEmbed providers]
 to the allow list?

 The quickest way to get embeds working for your site would be to limit the
 HTML to the allowed list of tags for auto-discovery, this includes links,
 blockquotes and iframes with a limited set of attributes. See
 https://github.com/WordPress/wordpress-
 develop/blob/107050f7a34d0b728e4c38bfc946e3339578ea6f/src/wp-
 includes/embed.php#L921-L936

 For iframes, you'd also need to ensure any JavaScript and other code
 within the embed can be run in iframes with the attributes `sandbox
 ="allow-scripts" security="restricted"`.

 By enabling auto-discovery, your site's embeds will work on both WordPress
 versions below 6.0 and you won't need to go through the checklist above.

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

From noreply at wordpress.org  Thu Mar  3 00:54:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 00:54:38 -0000
Subject: [wp-trac] [WordPress Trac] #54379: `get_comment_ID()` can cause
 a notice within the `comment_text` filter
In-Reply-To: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
References: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
Message-ID: <063.53f609fcca0acd74cc3b0c3cd7fa811f@wordpress.org>

#54379: `get_comment_ID()` can cause a notice within the `comment_text` filter
-------------------------------------+----------------------------
 Reporter:  dd32                     |       Owner:  davidbaumwald
     Type:  defect (bug)             |      Status:  reviewing
 Priority:  normal                   |   Milestone:  6.0
Component:  Comments                 |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+----------------------------
Changes (by davidbaumwald):

 * keywords:  has-patch => has-patch needs-refresh


Comment:

 @dd32 After [52205], the
 [https://core.trac.wordpress.org/attachment/ticket/54379/54379.2.diff
 54379.2.diff] doesn't apply cleanly.

 More importantly, the inline docs there were updated to have the
 `$comment_ID` param to expect a `string`.  Should this be corrected back
 to `int` while also casting the `$comment_ID` to an `(int)`?

 Is it your preference to handle the other related notices here as well, or
 should those be split off into separate tickets?

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

From noreply at wordpress.org  Thu Mar  3 02:03:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 02:03:34 -0000
Subject: [wp-trac] [WordPress Trac] #55289: Large image fails to create
 a `scaled` version and subsizes
In-Reply-To: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
References: <050.475807dd2487e5fcc54fab63c254fe95@wordpress.org>
Message-ID: <065.07e4f994c6d2a683d20ccc730069b01f@wordpress.org>

#55289: Large image fails to create a `scaled` version and subsizes
--------------------------+------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by mikeschroder):

 Replying to [comment:3 adamsilverstein]:
 > Interesting! The comment there implies this makes resizing more
 efficient..
 >
 > This was introduced in https://github.com/WordPress/wordpress-
 develop/commit/e2d2c45c6b7ed013139be7ab8f3833750684e28d maybe we can skip
 doing this when the original file is already so large? cc: @mikeschroder

 Thanks for the ping! I can't remember why it would make it more efficient
 off the top of my head, unless maybe there was more multi-sampling going
 on if it's not set.

 I'll look into this.

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

From noreply at wordpress.org  Thu Mar  3 02:05:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 02:05:12 -0000
Subject: [wp-trac] [WordPress Trac] #54379: `get_comment_ID()` can cause
 a notice within the `comment_text` filter
In-Reply-To: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
References: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
Message-ID: <063.4ab925efacff2384d38d47632055bf37@wordpress.org>

#54379: `get_comment_ID()` can cause a notice within the `comment_text` filter
--------------------------+----------------------------
 Reporter:  dd32          |       Owner:  davidbaumwald
     Type:  defect (bug)  |      Status:  reviewing
 Priority:  normal        |   Milestone:  6.0
Component:  Comments      |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+----------------------------

Comment (by dd32):

 Replying to [comment:6 davidbaumwald]:
 > More importantly, the inline docs there were updated to have the
 `$comment_ID` param to expect a `string`.  Should this be corrected back
 to `int` while also casting the `$comment_ID` to an `(int)`?

 While I don't agree with the whole `A numeric string, for compatibility
 reasons.` stuff, I don't see any benefit in casting to an int here, might
 as well just continue the status-quo of a numeric string.

 > Is it your preference to handle the other related notices here as well,
 or should those be split off into separate tickets?

 I don't see the harm in fixing multiple similar things in a singular
 ticket. I'd just manually apply the diff if I was committing this.. but
 happy to refresh it for you.

 Looks like [attachment:"54379.comments_open.diff"] was handled in [52223].

 https://github.com/WordPress/wordpress-develop/pull/2373 should be the
 remaining diffs from the attachments here.

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

From noreply at wordpress.org  Thu Mar  3 03:39:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 03:39:16 -0000
Subject: [wp-trac] [WordPress Trac] #55301: Provide an API to prevent
 certain blocks being shown in Widget Areas
Message-ID: <054.c9987188ae18b3032cf99143e88d3151@wordpress.org>

#55301: Provide an API to prevent certain blocks being shown in Widget Areas
-------------------------+-------------------------
 Reporter:  noisysocks   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  6.0
Component:  Editor       |    Version:
 Severity:  normal       |   Keywords:  needs-patch
  Focuses:               |
-------------------------+-------------------------
 Copied from https://github.com/WordPress/gutenberg/issues/28517. See
 discussion there.

 ---

 ## What problem does this address?
 With the introduction of Widget Areas, Gutenberg assumes all existing
 blocks will work in this context. We have a use case where some blocks may
 not work as widgets, or may conflict with legacy widgets or things such as
 shortcodes.

 https://github.com/woocommerce/woocommerce-gutenberg-products-
 block/pull/3737

 Gutenberg does provide the `widgets_to_exclude_from_legacy_widget_block `
 filter, but this only works on widgets.

 Unlike in the post editor screen (which provides `allowed_block_types `)
 there doesn't appear to be an filter, supports variable, or any API we can
 use to state that a block should not appear in this context.

 ## What is your proposed solution?
 Some form of supports flag when the block is registered, or an
 allow/denylist where the block can be excluded from the widget area block
 inserter.

 Our current solution/workaround is to check if `'themes.php' === $pagenow`
 and not register the block.

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

From noreply at wordpress.org  Thu Mar  3 03:53:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 03:53:58 -0000
Subject: [wp-trac] [WordPress Trac] #55301: Provide an API to prevent
 certain blocks being shown in Widget Areas
In-Reply-To: <054.c9987188ae18b3032cf99143e88d3151@wordpress.org>
References: <054.c9987188ae18b3032cf99143e88d3151@wordpress.org>
Message-ID: <069.95f822f2560f908b25d9cb19a4d47951@wordpress.org>

#55301: Provide an API to prevent certain blocks being shown in Widget Areas
-----------------------------------------------------+---------------------
 Reporter:  noisysocks                               |       Owner:  (none)
     Type:  enhancement                              |      Status:  new
 Priority:  normal                                   |   Milestone:  6.0
Component:  Editor                                   |     Version:
 Severity:  normal                                   |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-note  |     Focuses:
-----------------------------------------------------+---------------------
Changes (by noisysocks):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests needs-
     dev-note


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

From noreply at wordpress.org  Thu Mar  3 04:56:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 04:56:51 -0000
Subject: [wp-trac] [WordPress Trac] #55302: Improve media library upload
 progress indicator
Message-ID: <059.94226db16681b851e6132e94d124d7cc@wordpress.org>

#55302: Improve media library upload progress indicator
-----------------------------+-----------------------------
 Reporter:  adamsilverstein  |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Media            |    Version:
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 When uploading in the media library, the progress bar shows the ''upload
 progress'' of the image.

 Once the image is fully uploaded WordPress creates the sub-sized images
 used to serve images on the front end. Depending on your configuration
 (theme, plugins, server), and the upload size this can take quite a while
 to complete. During sub-sized image creation, the progress bar for the
 image shows as "full". Finally, when the image sub size generation
 completes, the image changes from a gray box to the thumbnail of the
 uploaded image and if multiple images have been uploaded, the uploader
 moves on to the next image. Screencast attached.

 The problem here is that no progress is shown for the image regeneration
 phase.

 Uploading in the block editor works a bit differently: as soon as the
 image is dropped onto the editor to upload, a grayed out version of the
 image is shown with a spinner. The spinner spins during the upload and
 continues spinning during sub-size creation. Finally, when all sub sizes
 are created, the image becomes fully saturated and the spinner goes away.
 **Looks like this is changing to a progress bar though**, see
 https://github.com/WordPress/gutenberg/issues/13984 &
 https://github.com/WordPress/gutenberg/tree/trunk/packages/block-
 editor/src/components/media-upload-progress

 Two potential improvements we could make in the media library:
 1. immediately show the thumbnail of the dropped image instead of the gray
 box
 2. switch to a spinner entirely, or for the image regeneration phase or
 try to show actual progress. The challenge with showing progress is we
 don't know how long the request will take on the server.

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

From noreply at wordpress.org  Thu Mar  3 04:57:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 04:57:15 -0000
Subject: [wp-trac] [WordPress Trac] #55302: Improve media library upload
 progress indicator
In-Reply-To: <059.94226db16681b851e6132e94d124d7cc@wordpress.org>
References: <059.94226db16681b851e6132e94d124d7cc@wordpress.org>
Message-ID: <074.73eb791f0f7cb3e1d68b821a9a3440a9@wordpress.org>

#55302: Improve media library upload progress indicator
-----------------------------+------------------------------
 Reporter:  adamsilverstein  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Media            |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------
Changes (by adamsilverstein):

 * Attachment "media-uploads.mp4" added.


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

From noreply at wordpress.org  Thu Mar  3 04:57:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 04:57:25 -0000
Subject: [wp-trac] [WordPress Trac] #55302: Improve media library upload
 progress indicator
In-Reply-To: <059.94226db16681b851e6132e94d124d7cc@wordpress.org>
References: <059.94226db16681b851e6132e94d124d7cc@wordpress.org>
Message-ID: <074.b47bddbcb8e2079b1527b8a392b14eaf@wordpress.org>

#55302: Improve media library upload progress indicator
-----------------------------+------------------------------
 Reporter:  adamsilverstein  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Media            |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------
Changes (by adamsilverstein):

 * Attachment "cat.mp4" added.


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

From noreply at wordpress.org  Thu Mar  3 05:57:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 05:57:53 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly
 with Odysee.com (half working)
In-Reply-To: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
References: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
Message-ID: <070.04ad81149cac4c01be05ca1d20df2660@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+------------------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+------------------------------

Comment (by tomatodysee):

 Replying to [comment:2 peterwilsoncc]:
 > Can you please answer each of the questions of the
 [https://make.wordpress.org/core/handbook/contribute/design-decisions
 /#adding-new-oembed-providers checklist for adding new oEmbed providers]
 to the allow list?
 >
 > The quickest way to get embeds working for your site would be to limit
 the HTML to the allowed list of tags for auto-discovery, this includes
 links, blockquotes and iframes with a limited set of attributes. See
 https://github.com/WordPress/wordpress-
 develop/blob/107050f7a34d0b728e4c38bfc946e3339578ea6f/src/wp-
 includes/embed.php#L921-L936
 >
 > For iframes, you'd also need to ensure any JavaScript and other code
 within the embed can be run in iframes with the attributes `sandbox
 ="allow-scripts" security="restricted"`.
 >
 > By enabling auto-discovery, your site's embeds will work on both
 WordPress versions below 6.0 and you won't need to go through the
 checklist above.

 Hey Peter, thanks so much for the reply!

 From our research about how "allow same origin" works with sandboxing, it
 should be safe to use if site A and embed site B are on different domains.
 Source: https://stackoverflow.com/questions/28332829/can-an-iframe-
 release-itself-from-allow-same-origin /
 https://www.html5rocks.com/en/tutorials/security/sandboxed-iframes/

 "Note, however, that you need to be very careful when dealing with framed
 content that comes from the same origin as the parent. If a page on
 https://example.com/ frames another page on the same origin with a sandbox
 that includes both the allow-same-origin and allow-scripts flags, then the
 framed page can reach up into the parent, and remove the sandbox attribute
 entirely."

 I have read other places that say it's not recommended, but they usually
 don't mention the same origin caveat.

 Do you have any more information on this?

 Right now our iframes fail with: ```Uncaught DOMException: Failed to read
 the 'cookie' property from 'Document': The document is sandboxed and lacks
 the 'allow-same-origin' flag.``` since we use cookies on the site.

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

From noreply at wordpress.org  Thu Mar  3 06:07:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 06:07:29 -0000
Subject: [wp-trac] [WordPress Trac] #55272: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
References: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
Message-ID: <074.258a9c4244b26a9ef29bac9ec9f8a53b@wordpress.org>

#55272: The New Layout Fix For Plugin Install Page
-------------------------------------+-------------------------------------
 Reporter:  sharjeelkhanvmi          |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Plugins                  |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  reporter-feedback        |     Focuses:  ui, css,
  needs-design-feedback              |  administration
-------------------------------------+-------------------------------------

Comment (by sharjeelkhanvmi):

 Okay, Then I need to fix the boxes sizes with the error message okay let
 me check what I can do then I update here.

 Replying to [comment:8 joyously]:
 > > I did not get your first point.
 >
 > The mismatched version error is shown at the top of the box. This alone
 can make the boxes uneven.
 > ''(This screenshot is my normal window width.)''
 > [[Image(https://i.postimg.cc/8zsLdQjp/Add-Plugins.jpg)]]
 > ------
 >
 > > Yes if we add more description lines to show then it mismatches the
 alignment of the boxes
 >
 > I think it's more important to see the complete sentence of the
 description than to have even boxes.

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

From noreply at wordpress.org  Thu Mar  3 07:00:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 07:00:43 -0000
Subject: [wp-trac] [WordPress Trac] #55272: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
References: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
Message-ID: <074.f2b5b1d159803292448d03106ca83bd7@wordpress.org>

#55272: The New Layout Fix For Plugin Install Page
-------------------------------------+-------------------------------------
 Reporter:  sharjeelkhanvmi          |       Owner:  (none)
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Plugins                  |     Version:
 Severity:  normal                   |  Resolution:  invalid
 Keywords:  reporter-feedback        |     Focuses:  ui, css,
  needs-design-feedback              |  administration
-------------------------------------+-------------------------------------
Changes (by sharjeelkhanvmi):

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


Comment:

 Here is the Updated Code And New Fixes
 You can check the errors and all the description is showing and all the
 layout will be now responsive it will be grid base now. here is the
 Screenshot: https://snipboard.io/fJvOE2.jpg
 [[Image(https://i.snipboard.io/fJvOE2.jpg)]]

 /*CSS CODE*/
 div#the-list
 {
     display: grid;
     grid-template-columns: repeat(auto-fill,minmax(30rem,1fr));
     grid-gap: 20px 10px;
 }
 .plugin-card .name
 {
     min-height: 30px;
     height: auto;
     margin-right: 0;
 }
 .widefat p
 {
     margin-top: 0;
     margin-bottom: 60px;
 }
 .plugin-card
 {
     border-radius: 6px;
     position: relative;
     display: grid;
     margin: 0 !important;
 }
 .plugin-card .desc
 {
     margin-right: 00;
 }
 .plugin-card .action-links
 {
     position: absolute;
     bottom: 0;
     left: auto;
     top: auto;
     width: 300px;
 }
 .plugin-action-buttons
 {
     display: flex;
     flex-direction: row-reverse;
     vertical-align: bottom;
 }
 .plugin-action-buttons li
 {
     margin: 0px 8px;
     position: relative;
     vertical-align: bottom;
 }
 .plugin-action-buttons .thickbox.open-plugin-details-modal
 {
     position: relative;
     top: 10px;
 }
 .plugin-card .desc
 {
     display: flex;
     flex-direction: column-reverse;
 }
 .plugin-icon
 {
     border-radius: 6px;
     border: 1px solid #dcdcde;
 }
 .plugin-card-bottom
 {
     border-radius: 0px 0px 6px 6px;
     position: relative;
     order: 3;
 }
 .plugin-card h3
 {
     margin-bottom: 0;
 }
 .widefat p.authors
 {
     height: auto;
     margin-top: 8px;
     margin-bottom: 10px;
 }
 .plugin-card .notice p
 {
     margin: 0;
     height: auto;
     overflow: initial;
     width: 100%;
 }
 .plugin-card .notice
 {
     display: flex;
     vertical-align: middle;
     margin: 0;
     margin-top: 0px;
     order: 1;
     border: unset;
 }
 .plugin-card
 {
     width: 100%;
 }

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

From noreply at wordpress.org  Thu Mar  3 08:28:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 08:28:08 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.0629b7de5314d67b0db6123bbc7a5e5f@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch needs-testing                        |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  good-first-bug has-testing-info has-patch => good-first-bug
     has-testing-info has-patch needs-testing


Comment:

 Thanks for the patch @abdullahramzan!

 I'm confident that this solution works, but let's add `needs-testing` so
 that the original issue is reproduced and the solution is tested by
 someone other than myself as the reporter and yourself as the patcher.

 I'll post in the `core-test` Slack channel to help move this ticket along
 more quickly.

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

From noreply at wordpress.org  Thu Mar  3 09:34:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 09:34:16 -0000
Subject: [wp-trac] [WordPress Trac] #55284: thumbnails issue
In-Reply-To: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
References: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
Message-ID: <078.fa24567ea62ad711ccf3f4b883258469@wordpress.org>

#55284: thumbnails issue
---------------------------------+------------------------------
 Reporter:  simobenedettidesign  |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  Awaiting Review
Component:  Editor               |     Version:  5.9.1
 Severity:  major                |  Resolution:
 Keywords:                       |     Focuses:
---------------------------------+------------------------------
Changes (by costdev):

 * component:  Post Thumbnails => Editor


Comment:

 Hi @simobenedettidesign, welcome to Trac!

 Please provide the following additional information:

 - What theme are you using?
 - How are you setting the space between elements?
 - Are you using one Gallery block? If not, please tell us the blocks that
 you're using.
 - What browser(s) does this issue appear in?
 - Is the Gutenberg plugin installed and activated, or not?

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

From noreply at wordpress.org  Thu Mar  3 10:03:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 10:03:00 -0000
Subject: [wp-trac] [WordPress Trac] #55291: Can't access Custom CSS with
 theme Twenty Twenty-Two
In-Reply-To: <056.1ac2611b59cebcd2a6941a3ceb32d710@wordpress.org>
References: <056.1ac2611b59cebcd2a6941a3ceb32d710@wordpress.org>
Message-ID: <071.2788dbeb4db69ffcb06efb77c7185c36@wordpress.org>

#55291: Can't access Custom CSS with theme Twenty Twenty-Two
-------------------------------------+------------------------------
 Reporter:  DeveloperWil             |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Themes                   |     Version:  5.9
 Severity:  normal                   |  Resolution:
 Keywords:  reporter-feedback close  |     Focuses:
-------------------------------------+------------------------------
Changes (by costdev):

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


Comment:

 Hi @DeveloperWil, welcome to Trac!

 @audrasjb is correct.

 - Additional CSS is theme-specific.
 - If you add Additional CSS to Twenty Eleven then switch to Twenty Twelve,
 the Additional CSS that you added will not be available.
 - If you switch back to Twenty Eleven, the Additional CSS that you added
 will be available again.

 For block themes, if you do not wish to create a child theme and add your
 custom CSS there, you can access some styling options in the Editor by
 clicking the Styles icon at the top right of the Editor.

 If you are using a block theme and you still want access to Additional CSS
 via the Customizer:

 1. Create a folder called `enable-customizer` in `wp-content/plugins`.
 2. Inside this folder, create a new file called `enable-customizer.php`.
 3. Paste the following code into the file and save.

 {{{#!php
 <?php

 /**
  * Plugin Name: Enable Customizer
  * Description: Enables the Customizer.
  * Author:      WordPress Contributors
  * Author URI:  https://www.wordpress.org
  * License:     GPLv2 or later
  * Version:     1.0.0
  */

 add_action( 'customize_register', '__return_true' );
 }}}

 4. In the WordPress Admin, navigate to `Plugins > Installed Plugins` and
 activate the Enable Customizer plugin.

 You should now be able to navigate to `Appearance > Customize` and access
 the Additional CSS panel.

 This doesn't appear to be a valid bug, but is actually the intended
 behaviour of the Additional CSS panel.

 I'll add the `close` keyword for now, pending `reporter-feedback`.

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

From noreply at wordpress.org  Thu Mar  3 11:05:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:05:54 -0000
Subject: [wp-trac] [WordPress Trac] #17025: wp_list_authors() is not
 filterable
In-Reply-To: <050.d34f9cbe54586689fc5b43e8aeb543db@wordpress.org>
References: <050.d34f9cbe54586689fc5b43e8aeb543db@wordpress.org>
Message-ID: <065.ecda54021a1c2aa78489fda43a5d2b5e@wordpress.org>

#17025: wp_list_authors() is not filterable
-------------------------------------------+-----------------------------
 Reporter:  kevinB                         |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  normal                         |   Milestone:  Future Release
Component:  Query                          |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch early needs-refresh  |     Focuses:
-------------------------------------------+-----------------------------

Comment (by Mte90):

 Just checking this ticket has two patch one to add the filter by the
 ticket name and another one to change the user name.

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

From noreply at wordpress.org  Thu Mar  3 11:06:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:06:57 -0000
Subject: [wp-trac] [WordPress Trac] #55303: Update
 WP_Block_Patterns_Registry::register() docs to include the blockTypes
 property
Message-ID: <054.5a2b39867af933a35c3aa88c756a9bd9@wordpress.org>

#55303: Update WP_Block_Patterns_Registry::register() docs to include the
blockTypes property
-------------------------+-----------------------------
 Reporter:  vlad.olaru   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Editor       |    Version:
 Severity:  normal       |   Keywords:
  Focuses:  docs         |
-------------------------+-----------------------------
 Since WordPress 5.8, block patterns can declare a `blockTypes` property to
 allow blocks to use those patterns in other contexts, besides the
 inserter. The `WP_Block_Patterns_Registry::register()` function is missing
 the documentation about this logic.

 Here is the discussion related to `blockTypes`
 https://github.com/WordPress/gutenberg/pull/30471

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

From noreply at wordpress.org  Thu Mar  3 11:07:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:07:24 -0000
Subject: [wp-trac] [WordPress Trac] #17019: add hooks for Media Library
 attachment counts
In-Reply-To: <050.e810527b0b849d77615783c435c285b6@wordpress.org>
References: <050.e810527b0b849d77615783c435c285b6@wordpress.org>
Message-ID: <065.e5f6975aeefd0c651e4b19f3c6f30153@wordpress.org>

#17019: add hooks for Media Library attachment counts
-------------------------------------------------+-------------------------
 Reporter:  kevinB                               |       Owner:
                                                 |  SergeyBiryukov
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Query                                |     Version:  2.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:
  tests early needs-testing-info                 |
-------------------------------------------------+-------------------------

Comment (by Mte90):

 @SergeyBiryukov there are updates for this patch?

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

From noreply at wordpress.org  Thu Mar  3 11:07:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:07:34 -0000
Subject: [wp-trac] [WordPress Trac] #37189: In wp_term_query on cache ids
In-Reply-To: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
References: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
Message-ID: <071.7fcebcff37fed151b45f614204d7c837@wordpress.org>

#37189: In wp_term_query on cache ids
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Taxonomy                             |     Version:  4.6
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 @boonebgorges Is there any chance you could take a look at my PR
 [https://github.com/WordPress/wordpress-develop/pull/2346 #2346]. It is
 very close to being mergeable.

 Working noting, in my testing, this PR does increase the number of SQL
 queries. The use of `_prime_term_caches`, means one query for getting the
 ids and another for get term data. This is likely to be a benefit in my
 cases. Get term data via `_prime_term_caches` and `get_term` means that
 any term loaded into cache on a request will not be reloaded again. This
 is an expected behaviour.

 The key goal of this ticket is not to store massive term objects in cache.
 There are limits to what can be stored in object caches. Not to mention,
 the fact if terms are updated, these caches may not be correctly
 invalidated.

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

From noreply at wordpress.org  Thu Mar  3 11:13:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:13:47 -0000
Subject: [wp-trac] [WordPress Trac] #55303: Update
 WP_Block_Patterns_Registry::register() docs to include the blockTypes
 property
In-Reply-To: <054.5a2b39867af933a35c3aa88c756a9bd9@wordpress.org>
References: <054.5a2b39867af933a35c3aa88c756a9bd9@wordpress.org>
Message-ID: <069.9478cc94d38405cc466deebf9fcc5425@wordpress.org>

#55303: Update WP_Block_Patterns_Registry::register() docs to include the
blockTypes property
-------------------------+---------------------
 Reporter:  vlad.olaru   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  docs
-------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Thu Mar  3 11:22:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:22:07 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.75488236630b51813aa6ff6d12daafd3@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch needs-testing                        |
-------------------------------------------------+-------------------------

Comment (by mukesh27):

 Hi there!

 The patch looks good to me.

 The latest user agents for Edge - https://www.whatismybrowser.com/guides
 /the-latest-user-agent/edge

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

From noreply at wordpress.org  Thu Mar  3 11:30:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:30:43 -0000
Subject: [wp-trac] [WordPress Trac] #55300: tests for
 WP_List_Util::pluck and WP_List_Util::sort
In-Reply-To: <051.dd5ff02912bce1bb03a5640324c5d38c@wordpress.org>
References: <051.dd5ff02912bce1bb03a5640324c5d38c@wordpress.org>
Message-ID: <066.e6261aa5f3082f56def6ea2e979cef5c@wordpress.org>

#55300: tests for WP_List_Util::pluck and WP_List_Util::sort
--------------------------------------+---------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Thu Mar  3 11:38:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:38:01 -0000
Subject: [wp-trac] [WordPress Trac] #55304: Remove error logging in
 sanitize_post
Message-ID: <052.ec02ef13047a37b27a4e9486ec206bd7@wordpress.org>

#55304: Remove error logging in sanitize_post
-------------------------------+-----------------------------
 Reporter:  legalweb           |      Owner:  (none)
     Type:  enhancement        |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Posts, Post Types  |    Version:  5.9.1
 Severity:  normal             |   Keywords:
  Focuses:                     |
-------------------------------+-----------------------------
 There is a error_log call in the method sanitize_post in post.php which is
 not needed in generall. it only spams the debug.log file

 {{{#!php
 <?php
 foreach ( array_keys( get_object_vars( $post ) ) as $field ) {
                         error_log("sanitize_post_field(field: ".$field.",
 postId:".$post->ID.")");
                         $post->$field = sanitize_post_field( $field,
 $post->$field, $post->ID, $context );
                 }
 }}}

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

From noreply at wordpress.org  Thu Mar  3 11:44:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:44:37 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.48401677b7f4dc68a6658c7f9f2cbdd5@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------

Comment (by afercia):

 Testing a bit the latest patch, I noticed a couple issues:
 - The close on Escape feature works also for the 'Quick Edit' textarea so
 the text of the JavaScript confirmation wouldn't be fully appropriate, as
 it refers only to 'Reply'.
 - More importantly: when editing multiple comments, there will be multiple
 JavaScript confirmation dialog. I think this is because of the way the JS
 event is currently attached to the textarea, which doesn't seem ideal.
 This would need some more refactoring to be solved, which is something I'd
 not recommend. To reproduce:
   - Apply the latest patch and build.
   - Reply to (or Quick Edit) a comment.
   - Enter some text.
   - Press the Escape key.
   - Click OK in the JavaScript confirm dialog.
   - Reply to another comment (or even to the same comment).
   - Enter some text.
   - Press the Escape key.
   - Click OK in the JavaScript confirm dialog.
   - At this point, you will get one more confirm dialog.
   - Repeat the steps above a few times and you will get as many confirm
 dialog as the amount of times you replied to a comment.

 Thinking a bit at the patch approach, I'd like to propose a new direction.
 After all, pressing Escape is generally used in software to 'cancel' the
 current operation. In this context, it does the same thing the 'Cancel'
 button (the one placed after the textarea) does. I'm not sure we should
 change this behavior.

 Instead, I'd say the actual problem that needs to be solved is the issue
 with Input Method Editor (IME) converters. Will submit a patch shortly.

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

From noreply at wordpress.org  Thu Mar  3 11:45:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:45:06 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.bc9a62dac886b569ea441d0fa6de08d8@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------
Changes (by afercia):

 * Attachment "54548.2.diff" added.


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

From noreply at wordpress.org  Thu Mar  3 11:52:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:52:39 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.aeabc3ef0f2e8f645fafbf1753b9d21d@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------

Comment (by afercia):

 [attachment:"54548.2.diff"] prevents the textarea from closing when
 pressing the escape key and while characters are being composed with an
 Input Method Editor. I can't test this with a real IME so this would need
 to be tested by someone else.

 For some background on this approach, see the discussion on
 https://core.trac.wordpress.org/ticket/45371

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

From noreply at wordpress.org  Thu Mar  3 11:53:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:53:00 -0000
Subject: [wp-trac] [WordPress Trac] #55290: Not all image edits are
 applied to all subsizes
In-Reply-To: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
References: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
Message-ID: <065.6cf34e0522871b23be60f5ed2c8cde3c@wordpress.org>

#55290: Not all image edits are applied to all subsizes
--------------------------+------------------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  administration, performance
--------------------------+------------------------------------------
Changes (by SergeyBiryukov):

 * keywords:   => needs-patch
 * milestone:  Awaiting Review => Future Release


Comment:

 Hi there, welcome back to WordPress Trac! Thanks for the ticket.

 Just noting that I was able to reproduce the issue with the steps
 described. I was also able to confirm comment:1.

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

From noreply at wordpress.org  Thu Mar  3 11:53:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:53:08 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.11b3087cb5dbdf2086152b86e9a63333@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch commit                               |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  good-first-bug has-testing-info has-patch needs-testing =>
     good-first-bug has-testing-info has-patch commit


Comment:

 Thanks @mukesh27!

 Marking for `commit` consideration.

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

From noreply at wordpress.org  Thu Mar  3 11:54:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:54:42 -0000
Subject: [wp-trac] [WordPress Trac] #55305: request
Message-ID: <051.a829ec910d2685382707429de4c168b0@wordpress.org>

#55305: request
--------------------------+-----------------------------
 Reporter:  egyreda       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 hello every one

 http://balawi-group.ml/?i=1
 could you check plz this is my first website
 everytime i try to access appears message
 (There has been a critical error on this website.)

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

From noreply at wordpress.org  Thu Mar  3 11:56:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 11:56:20 -0000
Subject: [wp-trac] [WordPress Trac] #55305: request
In-Reply-To: <051.a829ec910d2685382707429de4c168b0@wordpress.org>
References: <051.a829ec910d2685382707429de4c168b0@wordpress.org>
Message-ID: <066.7de6044f1496aee142477b8366ec4822@wordpress.org>

#55305: request
--------------------------+----------------------
 Reporter:  egyreda       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by costdev):

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


Old description:

> hello every one
>
> http://balawi-group.ml/?i=1
> could you check plz this is my first website
> everytime i try to access appears message
> (There has been a critical error on this website.)

New description:

 hello every one

 **link removed**
 could you check plz this is my first website
 everytime i try to access appears message
 (There has been a critical error on this website.)

--

Comment:

 Hi @egyreda, welcome to Trac!

 Sorry to hear that you're having trouble with your website.

 Trac is for the development of WordPress Core rather than providing
 WordPress support. You can get some help from the folks over on
 [https://wordpress.org/support/forums/ the support forums].

 Best of luck!

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

From noreply at wordpress.org  Thu Mar  3 12:14:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 12:14:45 -0000
Subject: [wp-trac] [WordPress Trac] #54878: Don't show links to the
 Customizer when installing themes using api.wordpress.org
In-Reply-To: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
References: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
Message-ID: <072.3fa99ebe9fe97d7add0c6f8884064b7d@wordpress.org>

#54878: Don't show links to the Customizer when installing themes using
api.wordpress.org
----------------------------------------------+---------------------
 Reporter:  antonvlasenko                     |       Owner:  (none)
     Type:  defect (bug)                      |      Status:  new
 Priority:  normal                            |   Milestone:  5.9.2
Component:  Themes                            |     Version:  5.9
 Severity:  normal                            |  Resolution:
 Keywords:  has-patch has-screenshots commit  |     Focuses:
----------------------------------------------+---------------------
Description changed by SergeyBiryukov:

Old description:

> I found this while working on
> https://core.trac.wordpress.org/ticket/54578
>
> Steps to reproduce the bug:
> 1. Go to `Appearance -> Themes` page.
> 2. Click on the `Add New` button, then find the `TT1` theme using the
> search functionality.
> 3. Install the theme.
>
> Expected result:
> The `Live Preview` button is not displayed for block-based themes.
>
> Actual result:
> The `Live Preview` button is displayed for block-based themes.
>
> Also, the `Customize` button is displayed for installed block themes when
> browsing the available themes. It also has to be removed.

New description:

 I found this while working on #54578.

 Steps to reproduce the bug:
 1. Go to `Appearance -> Themes` page.
 2. Click on the `Add New` button, then find the `TT1` theme using the
 search functionality.
 3. Install the theme.

 Expected result:
 The `Live Preview` button is not displayed for block-based themes.

 Actual result:
 The `Live Preview` button is displayed for block-based themes.

 Also, the `Customize` button is displayed for installed block themes when
 browsing the available themes. It also has to be removed.

--

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

From noreply at wordpress.org  Thu Mar  3 12:21:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 12:21:43 -0000
Subject: [wp-trac] [WordPress Trac] #55306: Before posts/pages listing if
 there multiple filter drop-downs,
 view of pagination buttons are not better looking.
Message-ID: <056.8adbf93b287eda30c45b130923837f18@wordpress.org>

#55306: Before posts/pages listing if there multiple filter drop-downs, view of
pagination buttons are not better looking.
-------------------------------------+-----------------------------
 Reporter:  haritpanchal             |      Owner:  (none)
     Type:  enhancement              |     Status:  new
 Priority:  normal                   |  Milestone:  Awaiting Review
Component:  Posts, Post Types        |    Version:  5.9.1
 Severity:  normal                   |   Keywords:
  Focuses:  ui, css, administration  |
-------------------------------------+-----------------------------
 While working on multiple drop-downs for particular post type, I came to
 find this bug when there is pagination is involved, UI is slightly
 damaged.

 Check the attachments for more details.

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

From noreply at wordpress.org  Thu Mar  3 12:22:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 12:22:52 -0000
Subject: [wp-trac] [WordPress Trac] #55306: Before posts/pages listing
 if there multiple filter drop-downs,
 view of pagination buttons are not better looking.
In-Reply-To: <056.8adbf93b287eda30c45b130923837f18@wordpress.org>
References: <056.8adbf93b287eda30c45b130923837f18@wordpress.org>
Message-ID: <071.3a962726bbcda874eed0d0a164a89120@wordpress.org>

#55306: Before posts/pages listing if there multiple filter drop-downs, view of
pagination buttons are not better looking.
-------------------------------+--------------------------------------
 Reporter:  haritpanchal       |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:  5.9.1
 Severity:  normal             |  Resolution:
 Keywords:                     |     Focuses:  ui, css, administration
-------------------------------+--------------------------------------
Changes (by haritpanchal):

 * Attachment "WP Margin Issue for Pagination.png" added.

 What issue is

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

From noreply at wordpress.org  Thu Mar  3 12:30:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 12:30:22 -0000
Subject: [wp-trac] [WordPress Trac] #55230: Release 5.9.1 breaks
 administration login.
In-Reply-To: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
References: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
Message-ID: <072.92c6e54486e5867c93508f76726db05e@wordpress.org>

#55230: Release 5.9.1 breaks administration login.
------------------------------------+-----------------------------
 Reporter:  carlduranleau           |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  5.9.2
Component:  Login and Registration  |     Version:  5.9.1
 Severity:  blocker                 |  Resolution:
 Keywords:  needs-patch             |     Focuses:  administration
------------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 Hi there, welcome to WordPress Trac! Thanks for the report.

 Could you share the steps to reproduce the issue on a clean install?

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

From noreply at wordpress.org  Thu Mar  3 12:39:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 12:39:32 -0000
Subject: [wp-trac] [WordPress Trac] #55306: Before posts/pages listing
 if there multiple filter drop-downs,
 view of pagination buttons are not better looking.
In-Reply-To: <056.8adbf93b287eda30c45b130923837f18@wordpress.org>
References: <056.8adbf93b287eda30c45b130923837f18@wordpress.org>
Message-ID: <071.fa8dc46f3c6408184095566aa69dce5c@wordpress.org>

#55306: Before posts/pages listing if there multiple filter drop-downs, view of
pagination buttons are not better looking.
-------------------------------+--------------------------------------
 Reporter:  haritpanchal       |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:  5.9.1
 Severity:  normal             |  Resolution:
 Keywords:  needs-patch        |     Focuses:  ui, css, administration
-------------------------------+--------------------------------------
Changes (by haritpanchal):

 * keywords:   => needs-patch


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

From noreply at wordpress.org  Thu Mar  3 12:56:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 12:56:04 -0000
Subject: [wp-trac] [WordPress Trac] #55189: Automatic removal of
 "Zero-width non-joiner" in URL
In-Reply-To: <053.3e9eb622a7f5219df8181821b4d758f9@wordpress.org>
References: <053.3e9eb622a7f5219df8181821b4d758f9@wordpress.org>
Message-ID: <068.f9e6e95c4cd07fa40e7d4c2a62fc3063@wordpress.org>

#55189: Automatic removal of "Zero-width non-joiner" in URL
--------------------------+---------------------
 Reporter:  man4toman     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.2
Component:  Permalinks    |     Version:  5.9
 Severity:  critical      |  Resolution:
 Keywords:  2nd-opinion   |     Focuses:
--------------------------+---------------------

Comment (by SergeyBiryukov):

 Thanks for the follow-up!

 I was able to reproduce the issue with the steps from comment:3, and
 [51984] indeed appears to be the related changeset. It's worth noting this
 only happens with pages, because the old slug redirect feature does not
 work for them yet, see #4328 for that. In testing with posts, the old slug
 does redirect as expected to the new slug.

 Related: #50924, which is apparently now fixed as of [51984] / #47912.

 I'm not quite sure how to proceed here, as #50924 suggested this character
 should be removed from URLs, while this one suggests that it should not
 (if I understand correctly). Maybe fixing #4328 would be the way to go
 here, so that the old slug redirect feature works for pages too?

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

From noreply at wordpress.org  Thu Mar  3 13:23:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 13:23:13 -0000
Subject: [wp-trac] [WordPress Trac] #55304: Remove error logging in
 sanitize_post
In-Reply-To: <052.ec02ef13047a37b27a4e9486ec206bd7@wordpress.org>
References: <052.ec02ef13047a37b27a4e9486ec206bd7@wordpress.org>
Message-ID: <067.d1219b8fc5837dcd6477c8898bd97be3@wordpress.org>

#55304: Remove error logging in sanitize_post
-------------------------------+----------------------
 Reporter:  legalweb           |       Owner:  (none)
     Type:  enhancement        |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Posts, Post Types  |     Version:  5.9.1
 Severity:  normal             |  Resolution:  invalid
 Keywords:                     |     Focuses:
-------------------------------+----------------------
Changes (by swissspidy):

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


Comment:

 Hi there, welcome to WordPress Trac!

 Could it be that this file was manually edited on your site?

 This function does not include any `error_log()` call in WordPress.

 See https://github.com/WordPress/wordpress-
 develop/blob/b28dcfd83243459e9cc08f46f70418ebfde9dde8/src/wp-
 includes/post.php#L2711-L2723

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

From noreply at wordpress.org  Thu Mar  3 13:27:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 13:27:16 -0000
Subject: [wp-trac] [WordPress Trac] #55304: Remove error logging in
 sanitize_post
In-Reply-To: <052.ec02ef13047a37b27a4e9486ec206bd7@wordpress.org>
References: <052.ec02ef13047a37b27a4e9486ec206bd7@wordpress.org>
Message-ID: <067.ea6ba8ab338ac83c57736e920ffd9b1e@wordpress.org>

#55304: Remove error logging in sanitize_post
-------------------------------+----------------------
 Reporter:  legalweb           |       Owner:  (none)
     Type:  enhancement        |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Posts, Post Types  |     Version:  5.9.1
 Severity:  normal             |  Resolution:  invalid
 Keywords:                     |     Focuses:
-------------------------------+----------------------

Comment (by legalweb):

 hi!

 i've checked it and have this line on 2 different installations on the
 same hoster. but if i check the lastet wordpress zip package, it's not
 present.
 seems that the hoster added this. sorry for this false positive.

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

From noreply at wordpress.org  Thu Mar  3 13:31:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 13:31:16 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
Message-ID: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+-----------------------------
 Reporter:  zippy1970        |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:  5.9
 Severity:  major            |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 I upgraded my production server from Debian 10 (Buster) to Debian 11
 (Bullseye) a few days ago. At first, none of the hosted WordPress sites
 worked. All gave me an error about a missing mysql module. As it turned
 out, I needed to install php7.4-mysqli.

 But then when I wanted to update the WordPress sites from v5.9.0 to
 v5.9.1, all failed:

 {{{
 Downloading update from
 https://downloads.wordpress.org/release/wordpress-5.9.1-no-content.zip…

 The authenticity of wordpress-5.9.1-no-content.zip could not be verified
 as no signature was found.

 Unpacking the update…

 Verifying the unpacked files…

 The update could not be unpacked.

 Installation failed.
 }}}

 I took me quite a while to figure out what actually was going on. Now I
 know, I have no idea if this is a bug in WordPress, or caused by something
 else.

 The error message WP is giving, is actually ''incorrect''. As it turns
 out, it is able to unpack the update just fine in the wp-content/upgrade
 folder. But it’s when it checks if the files have actually unpacked, where
 it goes wrong. The problem lies in this piece of code in update-core.php:

 {{{#!php
 <?php
   foreach ( $roots as $root ) {
     if ( $wp_filesystem->exists( $from . $root . 'readme.html' )
        && $wp_filesystem->exists( $from . $root . 'wp-
 includes/version.php' )
      ) {
        $distro = $root;
        break;
      }
    }

    if ( ! $distro ) {
      $wp_filesystem->delete( $from, true );
      return new WP_Error( 'insane_distro', __( 'The update could not be
 unpacked.' ) );
    }
 }}}

 What it does here, is simply check if two files exists in the folder it
 has just unpacked the zip file to. This fails. And the reason is as
 follows:

 I use FTP method for installing updates. So when I tell it to update, it
 first figures out the folder it should download the zipfile to. This
 folder is stored in **$working_dir** in {{{wp-admin/includes/class-wp-
 upgrader.php -> unpack_package()}}}. The full path on the server is
 **/domains/domainname.com/htdocs/wp-content/upgrade/** but since FTP users
 are chrooted, WP finds and stores **/htdocs/wp-content/upgrade/** instead.
 The update file is downloaded to this folder and then unpacked.

 Next it does the above check in {{{wp-admin/includes/update-core.php ->
 update_core()}}}. And that failes because it tries to find a file in
 **/htdocs/wp-content/upgrade/** while the true location is
 **/domains/domainname.com/htdocs/wp-content/upgrade/**.

 Updating through FTP used to work fine in Debian 10 but in Debian 11,
 something broke...

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

From noreply at wordpress.org  Thu Mar  3 14:15:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 14:15:49 -0000
Subject: [wp-trac] [WordPress Trac] #55308: Update WordPress version URL
 target
Message-ID: <053.b8de66dd15e6204fc2c92a329b0c3c45@wordpress.org>

#55308: Update WordPress version URL target
-------------------------------+-----------------------------
 Reporter:  gazthink3          |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  General            |    Version:  trunk
 Severity:  normal             |   Keywords:  2nd-opinion
  Focuses:  ui, accessibility  |
-------------------------------+-----------------------------
 It's always frustrating when the WordPress version URL opens up in the
 same tab; we can open the `$version_url` in a new tab by changing the
 target. It's a small change but will be helpful for some people.

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

From noreply at wordpress.org  Thu Mar  3 14:36:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 14:36:00 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.6ba533cfc49b6ad0b06aefeeae89cb6b@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------
Changes (by costdev):

 * keywords:   => needs-testing


Comment:

 Hi @zippy1970, welcome to Trac!

 I'll add `needs-testing` so that we can try to get the issue reproduced
 and see where the problem should be resolved.

 In the meantime, would you be able to set up a website using
 [https://wordpress.org/download/releases/ WordPress 5.7.5] on Debian 11
 and try to upgrade to 5.8? This would let us confirm that the issue only
 lies within Debian 11, and not a mixture of Debian 11 and WordPress 5.9,
 and allow us to assign the `Version` property of the ticket accurately.

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

From noreply at wordpress.org  Thu Mar  3 14:39:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 14:39:56 -0000
Subject: [wp-trac] [WordPress Trac] #55308: Update WordPress version URL
 target
In-Reply-To: <053.b8de66dd15e6204fc2c92a329b0c3c45@wordpress.org>
References: <053.b8de66dd15e6204fc2c92a329b0c3c45@wordpress.org>
Message-ID: <068.5e4d80aa0993958b28f95f2646bd1a9f@wordpress.org>

#55308: Update WordPress version URL target
-----------------------------------+--------------------------------
 Reporter:  gazthink3              |       Owner:  (none)
     Type:  defect (bug)           |      Status:  new
 Priority:  normal                 |   Milestone:  Awaiting Review
Component:  General                |     Version:  trunk
 Severity:  minor                  |  Resolution:
 Keywords:  2nd-opinion has-patch  |     Focuses:  ui, accessibility
-----------------------------------+--------------------------------
Changes (by gazthink3):

 * severity:  normal => minor


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

From noreply at wordpress.org  Thu Mar  3 15:11:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 15:11:44 -0000
Subject: [wp-trac] [WordPress Trac] #46297: Unable to edit specific
 terms : rest_cannot_assign_term OR 403
In-Reply-To: <049.2c16ca488f09279f482af9c6a35d7dfb@wordpress.org>
References: <049.2c16ca488f09279f482af9c6a35d7dfb@wordpress.org>
Message-ID: <064.ece3a063923fc4a27419a8dab72ac733@wordpress.org>

#46297: Unable to edit specific terms : rest_cannot_assign_term OR 403
--------------------------+----------------------------------
 Reporter:  enps5         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Taxonomy      |     Version:  4.1
 Severity:  major         |  Resolution:
 Keywords:                |     Focuses:  multisite, rest-api
--------------------------+----------------------------------
Changes (by webtechIMT):

 * severity:  normal => major


Comment:

 Hello,

 I'm trying to edit a category and at line 39 of wp-admin/term.php : the
 function current_user_can( 'edit_term', $tag->term_id ) returns false.

 I'm yet logged with administrator capabilities (as I can see in the
 database in wp_usermeta, key wp_capabilities and value :
 a:3:{s:13:"administrator";b:1;s:19:"manage_translations";b:1;s:9:"translate";b:1;})...

 Could you help me please ?

 PS : WP version is the latest : 5.9.1

 Thank you,
 Olivier.

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

From noreply at wordpress.org  Thu Mar  3 15:22:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 15:22:13 -0000
Subject: [wp-trac] [WordPress Trac] #49612: wpmu_new_blog hook has been
 deprecated. Use wp_initialize_site instead.
In-Reply-To: <055.59b98c6521117940d257195c928551f9@wordpress.org>
References: <055.59b98c6521117940d257195c928551f9@wordpress.org>
Message-ID: <070.87696ad92516f19f81f46cd120d1d60f@wordpress.org>

#49612: wpmu_new_blog hook has been deprecated. Use wp_initialize_site instead.
--------------------------------+------------------------------
 Reporter:  asaquzzaman         |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:  multisite
--------------------------------+------------------------------

Comment (by MadtownLems):

 I've been cleaning up old plugins of wpmu_new_blog, and came here to make
 this exact request.  Suggesting wp_insert_site is NOT a good replacement.
 The suggestion should absolutely be wp_initialize_site instead! (or at
 least mention both and let people see which makes sense for their specific
 case)

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

From noreply at wordpress.org  Thu Mar  3 15:55:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 15:55:54 -0000
Subject: [wp-trac] [WordPress Trac] #49612: wpmu_new_blog hook has been
 deprecated. Use wp_initialize_site instead.
In-Reply-To: <055.59b98c6521117940d257195c928551f9@wordpress.org>
References: <055.59b98c6521117940d257195c928551f9@wordpress.org>
Message-ID: <070.e57222e9c51e126ed47f76d587320a8e@wordpress.org>

#49612: wpmu_new_blog hook has been deprecated. Use wp_initialize_site instead.
--------------------------------+------------------------
 Reporter:  asaquzzaman         |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  6.0
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:  multisite
--------------------------------+------------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Thu Mar  3 15:56:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 15:56:22 -0000
Subject: [wp-trac] [WordPress Trac] #49612: wpmu_new_blog hook has been
 deprecated. Use wp_initialize_site instead.
In-Reply-To: <055.59b98c6521117940d257195c928551f9@wordpress.org>
References: <055.59b98c6521117940d257195c928551f9@wordpress.org>
Message-ID: <070.0b7627d934958e44ac95b10f4fad6ecc@wordpress.org>

#49612: wpmu_new_blog hook has been deprecated. Use wp_initialize_site instead.
--------------------------------+-----------------------------
 Reporter:  asaquzzaman         |       Owner:  SergeyBiryukov
     Type:  defect (bug)        |      Status:  closed
 Priority:  normal              |   Milestone:  6.0
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:  fixed
 Keywords:                      |     Focuses:  multisite
--------------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52816" 52816]:
 {{{
 #!CommitTicketReference repository="" revision="52816"
 Networks and Sites: Suggest `wp_initialize_site` as an alternative for the
 deprecated `wpmu_new_blog` action.

 The previously suggested alternative, `wp_insert_site`, does not get
 passed enough arguments and runs before the new site initialization
 routine is actually executed.

 Follow-up to [43654].

 Props asaquzzaman, henry.wright, MadtownLems.
 Fixes #49612.
 }}}

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

From noreply at wordpress.org  Thu Mar  3 16:01:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 16:01:17 -0000
Subject: [wp-trac] [WordPress Trac] #49349: wpmu_new_blog deprecated
 notice
In-Reply-To: <056.718ddc9c84290ab7e9886de7ab4a2bff@wordpress.org>
References: <056.718ddc9c84290ab7e9886de7ab4a2bff@wordpress.org>
Message-ID: <071.8612a9fee40f8b34b5ff972459001cfa@wordpress.org>

#49349: wpmu_new_blog deprecated notice
--------------------------------+------------------------
 Reporter:  henry.wright        |       Owner:  (none)
     Type:  defect (bug)        |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:  duplicate
 Keywords:                      |     Focuses:  multisite
--------------------------------+------------------------
Changes (by SergeyBiryukov):

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


Comment:

 Thanks for the ticket! This is now fixed in [52816] / #49612. The other
 ticket had a patch and a bit more traction, so I think this one can be
 closed.

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

From noreply at wordpress.org  Thu Mar  3 16:11:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 16:11:58 -0000
Subject: [wp-trac] [WordPress Trac] #49612: wpmu_new_blog hook has been
 deprecated. Use wp_initialize_site instead.
In-Reply-To: <055.59b98c6521117940d257195c928551f9@wordpress.org>
References: <055.59b98c6521117940d257195c928551f9@wordpress.org>
Message-ID: <070.14c9487c1ef74f530d71a66217799b47@wordpress.org>

#49612: wpmu_new_blog hook has been deprecated. Use wp_initialize_site instead.
--------------------------------+-----------------------------
 Reporter:  asaquzzaman         |       Owner:  SergeyBiryukov
     Type:  defect (bug)        |      Status:  closed
 Priority:  normal              |   Milestone:  6.0
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:  fixed
 Keywords:                      |     Focuses:  multisite
--------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52817" 52817]:
 {{{
 #!CommitTicketReference repository="" revision="52817"
 Docs: Update the DocBlock for the `wpmu_new_blog` action to suggest
 `wp_initialize_site` as an alternative.

 Follow-up to [43654], [52816].

 See #49612.
 }}}

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

From noreply at wordpress.org  Thu Mar  3 16:29:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 16:29:07 -0000
Subject: [wp-trac] [WordPress Trac] #55309: Incorrect post comment count
 after deleting comment with replies
Message-ID: <047.ce61b02f20ee5d83afb18a2cd1b37113@wordpress.org>

#55309: Incorrect post comment count after deleting comment with replies
--------------------------+-----------------------------
 Reporter:  jwz           |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Comments      |    Version:  5.9.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 If you move a comment to the trash, and that comment has sub-comments,
 none of those comments are visible (which is desired) but
 post->comment_count is reduced by 1 rather than by the total number of
 comments that have now been hidden.

 For example: post has 1 comment with 3 replies. Comment count is 4. Delete
 the first comment. Now no comments are visible but comment count is 3.

 The first comment has comment_approved set to 'trash' but the other 3
 comments are still '1'. Perhaps the right fix is that when trashing a
 comment, all of its sub-comments are also trashed explicitly rather than
 implicitly.

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

From noreply at wordpress.org  Thu Mar  3 17:44:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 17:44:29 -0000
Subject: [wp-trac] [WordPress Trac] #55310: Multi-date scheduled content
 blocks don't work as expected
Message-ID: <058.66f5aca6d80a01e8025caa4e4654b51f@wordpress.org>

#55310: Multi-date scheduled content blocks don't work as expected
----------------------------+-----------------------------
 Reporter:  shawnwrightres  |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:  5.9.1
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 I have a page where I want each month to show a different block, so each
 block I've created has two dates, basically a start (visible) and stop
 (hidden) date, so that each month the content will change, but no
 intervention will be needed that whole time by an author. However, it
 doesn't seem to be working as expected for future dates. See screenshot
 which shows the settings for the April content block (visible on 4/1,
 hidden on 5/1), except that it's March and it's showing. I tried inverting
 the logic (hidden 4/1, visible 5/1) in case I have it backwards but that
 didn't change the behavior. Single dates work fine. I can have each block
 appear in its proper month, but I want the previous month's block to then
 disappear. IMO something is wrong here. Either my use of the block in this
 way is as intended and it's not working, OR, the intent of multiple dates
 is not clear and it needs to be made more clear.

 I may have miscategorized this ticket by choosing the wrong component, but
 wasn't sure which to use, please correct.

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

From noreply at wordpress.org  Thu Mar  3 17:46:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 17:46:09 -0000
Subject: [wp-trac] [WordPress Trac] #55310: Multi-date scheduled content
 blocks don't work as expected
In-Reply-To: <058.66f5aca6d80a01e8025caa4e4654b51f@wordpress.org>
References: <058.66f5aca6d80a01e8025caa4e4654b51f@wordpress.org>
Message-ID: <073.7d2044c75a446b0b6d91bf13a37a5a41@wordpress.org>

#55310: Multi-date scheduled content blocks don't work as expected
----------------------------+------------------------------
 Reporter:  shawnwrightres  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  5.9.1
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------
Changes (by shawnwrightres):

 * Attachment "Screenshot 2022-03-03 113418.jpg" added.

 Web page showing both March and April scheduled content blocks even though
 April is set for April 1st visibility and May 1st hidden.

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

From noreply at wordpress.org  Thu Mar  3 17:47:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 17:47:49 -0000
Subject: [wp-trac] [WordPress Trac] #55310: Multi-date scheduled content
 blocks don't work as expected
In-Reply-To: <058.66f5aca6d80a01e8025caa4e4654b51f@wordpress.org>
References: <058.66f5aca6d80a01e8025caa4e4654b51f@wordpress.org>
Message-ID: <073.409112f8fae7b74737942eab4673c2fe@wordpress.org>

#55310: Multi-date scheduled content blocks don't work as expected
----------------------------+------------------------------
 Reporter:  shawnwrightres  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  5.9.1
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------
Changes (by shawnwrightres):

 * Attachment "Screenshot 2022-03-03 113425.jpg" added.

 Scheduled content block settings showing April 1 visible, May 1 hidden,
 yet the block is currently visible.

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

From noreply at wordpress.org  Thu Mar  3 17:50:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 17:50:55 -0000
Subject: [wp-trac] [WordPress Trac] #55309: Incorrect post comment count
 after deleting comment with replies
In-Reply-To: <047.ce61b02f20ee5d83afb18a2cd1b37113@wordpress.org>
References: <047.ce61b02f20ee5d83afb18a2cd1b37113@wordpress.org>
Message-ID: <062.ccc8af02200a54178375b2579416a64c@wordpress.org>

#55309: Incorrect post comment count after deleting comment with replies
--------------------------+------------------------------
 Reporter:  jwz           |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Comments      |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |     Focuses:
--------------------------+------------------------------
Changes (by davidbaumwald):

 * keywords:   => dev-feedback


Comment:

 @jwz I'm going to tag this for `dev-feedback` to see if a conversation can
 be sparked to determine _if_ this should be done.  I agree, it seems
 reasonable since those comments are no longer visible.

 In the interim, you could always filter the number of comments for each
 post when the count is updated by using the
 [https://developer.wordpress.org/reference/hooks/pre_wp_update_comment_count_now/
 pre_wp_update_comment_count_now] hook and checking the parent comment of
 each child comment's status.

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

From noreply at wordpress.org  Thu Mar  3 18:02:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 18:02:48 -0000
Subject: [wp-trac] [WordPress Trac] #43936: Settings: Warn when open
 registration and new user default is privileged
In-Reply-To: <051.6cb6d8867fe37496c3fb9d274b59f535@wordpress.org>
References: <051.6cb6d8867fe37496c3fb9d274b59f535@wordpress.org>
Message-ID: <066.0f49f596634e62d59fb19f25c45e8a1d@wordpress.org>

#43936: Settings: Warn when open registration and new user default is privileged
-------------------------------------+-----------------------------
 Reporter:  kraftbj                  |       Owner:  SergeyBiryukov
     Type:  feature request          |      Status:  reviewing
 Priority:  normal                   |   Milestone:  Future Release
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  administration
-------------------------------------+-----------------------------

Comment (by verygoode):

 Checking in on this one. Ideally, we'd prevent any privileged role from
 being set as `default_role`.

 However, for now, perhaps a site health warning might help.
 @SergeyBiryukov

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

From noreply at wordpress.org  Thu Mar  3 18:43:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 18:43:28 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
Message-ID: <052.71705d312df930659699caa7e0d22c46@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
--------------------------+-----------------------------
 Reporter:  pgpagely      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.1
 Severity:  major         |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Both CSS and JS URLs are totally broken for some of the newer blocks (the
 most obvious one being the navigation block in the 2022 theme) when WP
 core is outside of the current directory in a different prefix.

 The issue happens because of the use of `realpath()` when trying to detect
 these paths which results in `$is_core_block` being false and then
 generating a weird URL because of that.

 The simplest reproduction case is as follows:

 - Install WP 5.9.1
 - Execute `mv wp-includes ../wp-includes-test`
 - Execute `ln -s ../wp-includes-test wp-includes`
 - The navigation styles/JS will now be broken on the 2022 theme

 For us, we are running WP inside docker, and our WP core files exist at
 `/wordpress-versions/5.9/` in the container, but the web root is at
 `/httpdocs`, we have the use the following to make things work:

 {{{#!php
 add_filter("block_type_metadata", function ($meta) {
     if (!empty($meta["file"])) {
         $meta["file"] = preg_replace("#/wordpress-versions/[0-9.]+/#",
 ABSPATH, $meta["file"]);
     }
     return $meta;
 });
 }}}

 If we don't do this then an example URI that is generated for one of the
 styles is this:

 `/wp-content/plugins/wordpress-versions/5.9/wp-
 includes/blocks/navigation/view.min.js?ver=3776ea67846b3bb10fe8f7cdd486b0ba`

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

From noreply at wordpress.org  Thu Mar  3 18:54:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 18:54:31 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.53e20e6f11f6f577bf85e9ff3d2198d1@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Changes (by pgpagely):

 * component:  General => Script Loader


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

From noreply at wordpress.org  Thu Mar  3 19:31:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 19:31:17 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.5d050c2848805dbaea08ff971ec1be13@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by afragen):

 Is there some reason you must use the FTP option to upgrade? Does
 upgrading work if you set the following in your
 `wp-config.php`?


 {{{
 define('FS_METHOD','direct');
 }}}

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

From noreply at wordpress.org  Thu Mar  3 20:32:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 20:32:36 -0000
Subject: [wp-trac] [WordPress Trac] #54379: `get_comment_ID()` can cause
 a notice within the `comment_text` filter
In-Reply-To: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
References: <048.a5a43ec46ccd37ba92f364c4ec0e8156@wordpress.org>
Message-ID: <063.0060efe3dd57e3be38cbe41fd153c8c4@wordpress.org>

#54379: `get_comment_ID()` can cause a notice within the `comment_text` filter
--------------------------+----------------------------
 Reporter:  dd32          |       Owner:  davidbaumwald
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  6.0
Component:  Comments      |     Version:
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |     Focuses:
--------------------------+----------------------------
Changes (by davidbaumwald):

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


Comment:

 In [changeset:"52818" 52818]:
 {{{
 #!CommitTicketReference repository="" revision="52818"
 Comments: Guard against potential PHP notices in `get_comment_author` and
 `get_comment_ID`.

 In both `get_comment_author` and `get_comment_ID`, it's possible that
 these functions are called without a comment context.  Specifically,
 `get_comment_author` can be called without passing the `$comment_ID`
 parameter, and `get_comment_ID` relies on the `comment` global if there's
 no `$comment` parameter supplied.  This leads to a PHP notice of "Trying
 to get property of a non-object."

 This change adds a check to both functions to ensure the
 `$comment->comment_ID` property is not empty before actually using its
 value.

 Follow-up to [52223].

 Props dd32.
 Fixes #54379.
 }}}

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

From noreply at wordpress.org  Thu Mar  3 20:35:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 20:35:33 -0000
Subject: [wp-trac] [WordPress Trac] #55310: Multi-date scheduled content
 blocks don't work as expected
In-Reply-To: <058.66f5aca6d80a01e8025caa4e4654b51f@wordpress.org>
References: <058.66f5aca6d80a01e8025caa4e4654b51f@wordpress.org>
Message-ID: <073.57d94175285fe61429a0b58b26a6e13d@wordpress.org>

#55310: Multi-date scheduled content blocks don't work as expected
----------------------------+----------------------
 Reporter:  shawnwrightres  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Administration  |     Version:  5.9.1
 Severity:  normal          |  Resolution:  invalid
 Keywords:                  |     Focuses:
----------------------------+----------------------
Changes (by swissspidy):

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


Comment:

 Hi there and welcome to WordPress Trac!

 Please note that this bug tracker is used to discuss issues in WordPress
 core itself.

 For issues with the [https://wordpress.org/plugins/schedule-content-block/
 Schedule Content Block plugin], you'll need to report this to that plugin
 directly, for example on [https://github.com/goiblas/Schedule-Content-
 Block its GitHub repo] or [https://wordpress.org/support/plugin/schedule-
 content-block/ support forum].

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

From noreply at wordpress.org  Thu Mar  3 21:06:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 21:06:13 -0000
Subject: [wp-trac] [WordPress Trac] #55312: Image not rendering properly
Message-ID: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>

#55312: Image not rendering properly
--------------------------+-----------------------------
 Reporter:  rthaena       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Media         |    Version:  5.9.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 We noticed that our hero images weren't rendering properly on mobile &
 tablet sizes. When we rolled back to the version 5.9.0, the issue was
 resolved. Please take a look at the screenshots of the image and the
 details in the web inspector.

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

From noreply at wordpress.org  Thu Mar  3 21:06:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 21:06:55 -0000
Subject: [wp-trac] [WordPress Trac] #55312: Image not rendering properly
In-Reply-To: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
References: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
Message-ID: <066.a0e40cefa4cf0eb66d528ccf359b59af@wordpress.org>

#55312: Image not rendering properly
--------------------------+------------------------------
 Reporter:  rthaena       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by rthaena):

 * Attachment "img-container.jpg" added.


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

From noreply at wordpress.org  Thu Mar  3 21:07:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 21:07:02 -0000
Subject: [wp-trac] [WordPress Trac] #55312: Image not rendering properly
In-Reply-To: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
References: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
Message-ID: <066.1c36714489bd210daa2699995c8a1d3d@wordpress.org>

#55312: Image not rendering properly
--------------------------+------------------------------
 Reporter:  rthaena       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by rthaena):

 * Attachment "back.jpg" added.


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

From noreply at wordpress.org  Thu Mar  3 21:08:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 21:08:04 -0000
Subject: [wp-trac] [WordPress Trac] #55312: Image not rendering properly
In-Reply-To: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
References: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
Message-ID: <066.ea15ec4bade29788dc6513e8de7a3a25@wordpress.org>

#55312: Image not rendering properly
--------------------------+------------------------------
 Reporter:  rthaena       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by rthaena):

 Replying to [ticket:55312 rthaena]:
 > We noticed that our hero images weren't rendering properly on mobile &
 tablet sizes. When we rolled back to the version 5.9.0, the issue was
 resolved. Please take a look at the screenshots of the image and the
 details in the web inspector.

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

From noreply at wordpress.org  Thu Mar  3 21:08:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 21:08:43 -0000
Subject: [wp-trac] [WordPress Trac] #55312: Image not rendering properly
In-Reply-To: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
References: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
Message-ID: <066.df03538ed4863f26a14aa2e70049face@wordpress.org>

#55312: Image not rendering properly
--------------------------+------------------------------
 Reporter:  rthaena       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by rthaena):

 You can refer to https://kiddieacademy.com/ to see how the hero images are
 rendering in WP core version 5.9.0.

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

From noreply at wordpress.org  Thu Mar  3 21:26:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 21:26:57 -0000
Subject: [wp-trac] [WordPress Trac] #55312: Image not rendering properly
In-Reply-To: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
References: <051.276550cf49bb97bbba7cd34047c505e7@wordpress.org>
Message-ID: <066.68a4ae905873d1a3adcd054d283abe88@wordpress.org>

#55312: Image not rendering properly
--------------------------+------------------------------
 Reporter:  rthaena       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by tflight):

 Hi  @rthaena ,

 I believe you are likely seeing what is being discussed in these
 locations:

 https://core.trac.wordpress.org/ticket/55229
 https://github.com/WordPress/gutenberg/issues/39021
 https://github.com/WordPress/gutenberg/pull/39045

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

From noreply at wordpress.org  Thu Mar  3 21:40:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 21:40:43 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.026bc9cf03cb29cf0f9f9bca36faba7c@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 Replying to [comment:2 afragen]:
 > Is there some reason you must use the FTP option to upgrade?

 If I use the direct method, I first get this:

 {{{
 Downloading update from
 https://downloads.wordpress.org/release/wordpress-5.9.1-no-content.zip…

 The authenticity of wordpress-5.9.1-no-content.zip could not be verified
 as no signature was found.

 Unpacking the update…

 Could not create directory.

 Installation failed.
 }}}

 So next I do {{{chmod 0777 wp-content/upgrade}}} and then I get this:

 {{{
 Downloading update from
 https://downloads.wordpress.org/release/wordpress-5.9.1-no-content.zip…

 The authenticity of wordpress-5.9.1-no-content.zip could not be verified
 as no signature was found.

 Unpacking the update…

 Verifying the unpacked files…

 Preparing to install the latest version…

 The update cannot be installed because we will be unable to copy some
 files. This is usually due to inconsistent file permissions.: wp-includes
 /block-supports/elements.php, wp-includes/block-supports/duotone.php, wp-
 includes/block-supports/layout.php, wp-includes/default-filters.php, wp-
 includes/block-template.php, wp-includes/css/dist/edit-site/style-
 rtl.min.css, wp-includes/css/dist/edit-site/style.min.css, wp-
 includes/css/dist/edit-site/style-rtl.css, wp-includes/css/dist/edit-
 site/style.css, wp-includes/css/dist/block-library/editor.min.css, wp-
 includes/css/dist/block-library/style-rtl.min.css, wp-includes/css/dist
 /block-library/common-rtl.min.css, wp-includes/css/dist/block-
 library/editor.css, wp-includes/css/dist/block-library/common.css, wp-
 includes/css/dist/block-library/style.min.css, wp-includes/css/dist/block-
 library/editor-rtl.css, wp-includes/css/dist/block-library/editor-
 rtl.min.css, wp-includes/css/dist/block-library/style-rtl.css, wp-
 includes/css/dist/block-library/common.min.css, wp-includes/css/dist
 /block-library/common-rtl.css, wp-includes/css/dist/block-
 library/style.css, wp-includes/css/dist/components/style-rtl.min.css, wp-
 includes/css/dist/components/style.min.css, wp-
 includes/css/dist/components/style-rtl.css, wp-
 includes/css/dist/components/style.css, wp-includes/css/dist/block-editor
 /style-rtl.min.css, wp-includes/css/dist/block-editor/style.min.css, wp-
 includes/css/dist/block-editor/style-rtl.css, wp-includes/css/dist/block-
 editor/style.css, wp-includes/class-wp-theme-json.php, wp-includes/script-
 loader.php, wp-includes/assets/script-loader-packages.php, wp-
 includes/blocks/gallery/style-rtl.min.css, wp-
 includes/blocks/gallery/style.min.css, wp-includes/blocks/gallery/style-
 rtl.css, wp-includes/blocks/gallery/style.css, wp-includes/blocks/site-
 title.php, wp-includes/blocks/page-list/editor.min.css, wp-includes/blocks
 /page-list/editor.css, wp-includes/blocks/page-list/editor-rtl.css, wp-
 includes/blocks/page-list/editor-rtl.min.css, wp-includes/blocks/page-
 list.php, wp-includes/blocks/search.php, wp-includes/blocks/post-template
 /style-rtl.min.css, wp-includes/blocks/post-template/style.min.css, wp-
 includes/blocks/post-template/style-rtl.css, wp-includes/blocks/post-
 template/style.css, wp-includes/blocks/post-featured-image/editor.min.css,
 wp-includes/blocks/post-featured-image/editor.css, wp-includes/blocks
 /post-featured-image/editor-rtl.css, wp-includes/blocks/post-featured-
 image/editor-rtl.min.css, wp-includes/blocks/index.php, wp-
 includes/blocks/image/style-rtl.min.css, wp-
 includes/blocks/image/style.min.css, wp-includes/blocks/image/style-
 rtl.css, wp-includes/blocks/image/style.css, wp-includes/blocks/cover
 /style-rtl.min.css, wp-includes/blocks/cover/style.min.css, wp-
 includes/blocks/cover/style-rtl.css, wp-includes/blocks/cover/style.css,
 wp-includes/blocks/site-logo.php, wp-
 includes/blocks/spacer/editor.min.css, wp-
 includes/blocks/spacer/block.json, wp-includes/blocks/spacer/editor.css,
 wp-includes/blocks/spacer/editor-rtl.css, wp-includes/blocks/spacer
 /editor-rtl.min.css, wp-includes/deprecated.php, wp-includes/version.php,
 wp-includes/class-wp-theme-json-resolver.php, wp-includes/rest-
 api/endpoints/class-wp-rest-global-styles-controller.php, wp-includes
 /block-editor.php, wp-includes/post.php, wp-includes/global-styles-and-
 settings.php, wp-includes/js/dist/core-data.js, wp-
 includes/js/dist/components.js, wp-includes/js/dist/edit-site.min.js, wp-
 includes/js/dist/block-library.min.js, wp-includes/js/dist/edit-
 post.min.js, wp-includes/js/dist/block-editor.min.js, wp-includes/js/dist
 /core-data.min.js, wp-includes/js/dist/components.min.js, wp-
 includes/js/dist/editor.min.js, wp-includes/js/dist/edit-site.js, wp-
 includes/js/dist/block-editor.js, wp-includes/js/dist/block-library.js,
 wp-includes/js/dist/editor.js, wp-includes/js/dist/edit-post.js, wp-
 includes/js/wp-ajax-response.min.js, wp-includes/js/jquery/ui/effect-
 fade.js, wp-includes/js/jquery/ui/controlgroup.min.js, wp-
 includes/js/jquery/ui/effect-highlight.min.js, wp-includes/js/jquery/ui
 /effect-clip.js, wp-includes/js/jquery/ui/effect-highlight.js, wp-
 includes/js/jquery/ui/button.js, wp-includes/js/jquery/ui/tabs.min.js, wp-
 includes/js/jquery/ui/selectable.min.js, wp-
 includes/js/jquery/ui/draggable.js, wp-
 includes/js/jquery/ui/droppable.min.js, wp-
 includes/js/jquery/ui/effect.js, wp-includes/js/jquery/ui/spinner.js, wp-
 includes/js/jquery/ui/effect-explode.min.js, wp-
 includes/js/jquery/ui/accordion.js, wp-includes/js/jquery/ui/core.min.js,
 wp-includes/js/jquery/ui/effect-pulsate.min.js, wp-
 includes/js/jquery/ui/mouse.min.js, wp-includes/js/jquery/ui/effect-
 puff.min.js, wp-includes/js/jquery/ui/effect-shake.js, wp-
 includes/js/jquery/ui/menu.js, wp-includes/js/jquery/ui/draggable.min.js,
 wp-includes/js/jquery/ui/selectmenu.js, wp-
 includes/js/jquery/ui/sortable.js, wp-includes/js/jquery/ui/core.js, wp-
 includes/js/jquery/ui/effect-slide.min.js, wp-includes/js/jquery/ui
 /effect-drop.js, wp-includes/js/jquery/ui/effect-size.js, wp-
 includes/js/jquery/ui/autocomplete.js, wp-
 includes/js/jquery/ui/menu.min.js, wp-includes/js/jquery/ui/tabs.js, wp-
 includes/js/jquery/ui/effect-bounce.min.js, wp-includes/js/jquery/ui
 /effect-drop.min.js, wp-includes/js/jquery/ui/selectable.js, wp-
 includes/js/jquery/ui/dialog.js, wp-includes/js/jquery/ui/effect-
 fold.min.js, wp-includes/js/jquery/ui/checkboxradio.min.js, wp-
 includes/js/jquery/ui/effect-puff.js, wp-
 includes/js/jquery/ui/autocomplete.min.js, wp-
 includes/js/jquery/ui/slider.js, wp-includes/js/jquery/ui/tooltip.min.js,
 wp-includes/js/jquery/ui/sortable.min.js, wp-
 includes/js/jquery/ui/droppable.js, wp-includes/js/jquery/ui/effect-
 blind.min.js, wp-includes/js/jquery/ui/effect-pulsate.js, wp-
 includes/js/jquery/ui/resizable.min.js, wp-
 includes/js/jquery/ui/datepicker.js, wp-includes/js/jquery/ui/effect-
 scale.js, wp-includes/js/jquery/ui/checkboxradio.js, wp-
 includes/js/jquery/ui/spinner.min.js, wp-
 includes/js/jquery/ui/button.min.js, wp-
 includes/js/jquery/ui/progressbar.min.js, wp-
 includes/js/jquery/ui/tooltip.js, wp-includes/js/jquery/ui/effect.min.js,
 wp-includes/js/jquery/ui/effect-transfer.js, wp-
 includes/js/jquery/ui/accordion.min.js, wp-includes/js/jquery/ui/effect-
 fade.min.js, wp-includes/js/jquery/ui/effect-fold.js, wp-
 includes/js/jquery/ui/effect-transfer.min.js, wp-
 includes/js/jquery/ui/mouse.js, wp-includes/js/jquery/ui/controlgroup.js,
 wp-includes/js/jquery/ui/progressbar.js, wp-includes/js/jquery/ui/effect-
 clip.min.js, wp-includes/js/jquery/ui/effect-scale.min.js, wp-
 includes/js/jquery/ui/selectmenu.min.js, wp-includes/js/jquery/ui/effect-
 blind.js, wp-includes/js/jquery/ui/effect-explode.js, wp-
 includes/js/jquery/ui/resizable.js, wp-
 includes/js/jquery/ui/dialog.min.js, wp-includes/js/jquery/ui/effect-
 slide.js, wp-includes/js/jquery/ui/slider.min.js, wp-includes/js/jquery/ui
 /effect-bounce.js, wp-includes/js/jquery/ui/effect-size.min.js, wp-
 includes/js/jquery/ui/datepicker.min.js, wp-includes/js/jquery/ui/effect-
 shake.min.js, wp-includes/js/wp-ajax-response.js, wp-includes/option.php,
 wp-admin/css/dashboard-rtl.css, wp-admin/css/dashboard-rtl.min.css, wp-
 admin/css/dashboard.min.css, wp-admin/css/dashboard.css, wp-
 admin/about.php, wp-admin/update-core.php, wp-admin/includes/upgrade.php,
 wp-admin/includes/update-core.php, wp-admin/includes/class-core-
 upgrader.php, wp-admin/includes/file.php, wp-admin/edit-form-blocks.php

 Installation failed.
 }}}

 I'm sure I can get this to work by setting the proper file permissions,
 but I remember now why I chose FTP: security. Can't remember exactly what
 the security concern was, but this is a webserver with multiple virtual
 hosts all running WordPress.

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

From noreply at wordpress.org  Thu Mar  3 21:42:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 21:42:14 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.99335abc7093e0fe0b68e6b048757431@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 Replying to [comment:1 costdev]:
 > In the meantime, would you be able to set up a website using
 [https://wordpress.org/download/releases/ WordPress 5.7.5] on Debian 11
 and try to upgrade to 5.8? This would let us confirm that the issue only
 lies within Debian 11, and not a mixture of Debian 11 and WordPress 5.9,
 and allow us to assign the `Version` property of the ticket accurately.

 I'll try setting up a website using 5.7.5 and try to upgrade it to 5.8.
 Will return with the results.

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

From noreply at wordpress.org  Thu Mar  3 22:37:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 22:37:27 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.bf4e0be0c64e36d74b44bd15a89ad3c7@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 Ok, I installed WordPress 5.7.5 and tried to update it to 5.9.1. Got the
 exact same error:

 {{{
 Downloading update from
 https://downloads.wordpress.org/release/wordpress-5.9.1-new-bundled.zip…

 The authenticity of wordpress-5.9.1-new-bundled.zip could not be verified
 as no signature was found.

 Unpacking the update…

 Verifying the unpacked files…

 The update could not be unpacked

 Installation failed.
 }}}

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

From noreply at wordpress.org  Thu Mar  3 22:38:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 22:38:28 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.31f832d1719ba17627706ff897a80d87@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 Oh wait, did you want me to try to update to 5.8 or 5.9?

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

From noreply at wordpress.org  Thu Mar  3 23:31:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 23:31:00 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly
 with Odysee.com (half working)
In-Reply-To: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
References: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
Message-ID: <070.fbdb49e11625222716647d20741e4fed@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+------------------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+------------------------------

Comment (by peterwilsoncc):

 The [https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe
 #attr-sandbox sandbox attribute documentation] on MDN is pretty clear
 about this:

 > When the embedded document has the same origin as the embedding page, it
 is strongly discouraged to use both allow-scripts and allow-same-origin,
 **as that lets the embedded document remove the sandbox attribute** —
 making it no more secure than not using the sandbox attribute at all.

 (my emphasis)

 Locking down access to `window.parent` within auto-discovered embeds is
 quite intentional. The `sandbox` attribute's settings were discussed in
 #32522 but it's quite lengthy.

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

From noreply at wordpress.org  Thu Mar  3 23:54:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 23:54:33 -0000
Subject: [wp-trac] [WordPress Trac] #55284: thumbnails issue
In-Reply-To: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
References: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
Message-ID: <078.e95ad8560deb88c2f94afa42f15f31b5@wordpress.org>

#55284: thumbnails issue
---------------------------------+------------------------------
 Reporter:  simobenedettidesign  |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  Awaiting Review
Component:  Editor               |     Version:  5.9.1
 Severity:  major                |  Resolution:
 Keywords:                       |     Focuses:
---------------------------------+------------------------------

Comment (by simobenedettidesign):

 Hi there,

 - I am using Divi theme
 - The spacing between thumbnails is automatically set (I am using WP
 Gallery block). I have no issues with my current WordPress installation
 (5.8.3), the spacing between elements is respected but if I try to upgrade
 to the latest version (5.9.1) the spacing is lost
 - I have tested with Chrome, Firefox, Opera and Edge, the issue occurs
 with every browser
 - Gutenberg? I only have the WordPress editor, I have no extra plugins
 installed with this name

 Thanks for your help

 Replying to [comment:3 costdev]:
 > Hi @simobenedettidesign, welcome to Trac!
 >
 > Please provide the following additional information:
 >
 > - What theme are you using?
 > - How are you setting the space between elements?
 > - Are you using one Gallery block? If not, please tell us the blocks
 that you're using.
 > - What browser(s) does this issue appear in?
 > - Is the Gutenberg plugin installed and activated, or not?

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

From noreply at wordpress.org  Thu Mar  3 23:57:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 03 Mar 2022 23:57:57 -0000
Subject: [wp-trac] [WordPress Trac] #55313: Fix PHP Plugin
Message-ID: <053.c6421cf766a1fb9860c631944634d9b1@wordpress.org>

#55313: Fix PHP Plugin
--------------------------+-----------------------------
 Reporter:  ppatel821     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.1
 Severity:  blocker       |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Since the most recent Word Press update, I am receiving multiple errors on
 my site:

 Deprecated: Required parameter $args follows optional parameter $depth in
 /home4/parasand/public_html/wp-
 content/themes/grandwedding/lib/menu.lib.php on line 22

 Deprecated: Required parameter $output follows optional parameter $depth
 in /home4/parasand/public_html/wp-
 content/themes/grandwedding/lib/menu.lib.php on line 22

 Warning: Cannot modify header information - headers already sent by
 (output started at /home4/parasand/public_html/wp-
 content/themes/grandwedding/lib/menu.lib.php:22) in
 /home4/parasand/public_html/wp-includes/pluggable.php on line 1355

 Warning: Cannot modify header information - headers already sent by
 (output started at /home4/parasand/public_html/wp-
 content/themes/grandwedding/lib/menu.lib.php:22) in
 /home4/parasand/public_html/wp-includes/pluggable.php on line 1358

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

From noreply at wordpress.org  Fri Mar  4 00:09:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 00:09:24 -0000
Subject: [wp-trac] [WordPress Trac] #55314: When saving edits to the footer
 in editor (beta), saving fails
Message-ID: <056.753a6a76dc6ce66f94beaaf18dd3993e@wordpress.org>

#55314: When saving edits to the footer in editor (beta), saving fails
--------------------------+-----------------------------
 Reporter:  garnitchique  |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Editor        |    Version:  5.9.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 When editing the page template, saving changes made to the footer fails
 while saving changes to other blocks works. When saving changes to the
 footer, this request



 {{{
 POST    https://apgtest.dreamhosters.com/wp-json/wp/v2/template-
 parts/twentytwentytwo//footer?_locale=user
 }}}



 {{{
 <!-- wp:group
 {"style":{"spacing":{"padding":{"top":"var(\u002d\u002dwp\u002d\u002dcustom\u002d\u002dspacing\u002d\u002dlarge,
 8rem)"}}},"layout":{"inherit":true}} --><div class="wp-block-group" style
 ="padding-top:var(--wp--custom--spacing--large, 8rem)"><!-- wp:group
 {"align":"full","layout":{"inherit":true}} --><div class="wp-block-group
 alignfull"><!-- wp:group
 {"align":"wide","style":{"spacing":{"padding":{"top":"4rem","bottom":"4rem"}}},"layout":{"type":"flex","justifyContent
 ":"space-between"}} --><div class="wp-block-group alignwide" style
 ="padding-top:4rem;padding-bottom:4rem"><!-- wp:site-title {"level":0}
 /--><!-- wp:image {"id":8,"sizeSlug":"large","linkDestination":"none"}
 --><figure class="wp-block-image size-large"><img
 src="https://apgtest.dreamhosters.com/wp-
 content/uploads/2022/03/Artboard-1-1024x665.png" alt="" /></figure><!--
 /wp:image --><!-- wp:paragraph {"align":"right"} --><p class="has-text-
 align-right">Proudly powered by <a href="https://wordpress.org"
 rel="nofollow">WordPress</a></p><!-- /wp:paragraph --></div><!-- /wp:group
 --></div><!-- /wp:group --></div><!-- /wp:group -->
 }}}


 results in this response


 {{{
 418 I'm a teapot
 }}}

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

From noreply at wordpress.org  Fri Mar  4 00:11:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 00:11:38 -0000
Subject: [wp-trac] [WordPress Trac] #55315: SVGs in editor (beta)
Message-ID: <056.f77e6c1530c05f415f8c8b819ea0ee15@wordpress.org>

#55315: SVGs in editor (beta)
--------------------------+-----------------------------
 Reporter:  garnitchique  |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Editor        |    Version:  5.9.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 When adding an SVG to the header as logo or image, it uploads fine (after
 installing an SVG plugin) and is displayed when viewing the site, but it
 disappears in the editor.

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

From noreply at wordpress.org  Fri Mar  4 00:40:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 00:40:57 -0000
Subject: [wp-trac] [WordPress Trac] #55313: Fix PHP Plugin
In-Reply-To: <053.c6421cf766a1fb9860c631944634d9b1@wordpress.org>
References: <053.c6421cf766a1fb9860c631944634d9b1@wordpress.org>
Message-ID: <068.a266dc59b8fcf3cc1c9a19e54d97acfb@wordpress.org>

#55313: Fix PHP Plugin
--------------------------+------------------------------
 Reporter:  ppatel821     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  blocker       |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by joyously):

 The problem is in the theme. Due to the deprecation notice being output,
 the "headers already sent" warning is output.
 Fix the theme, and turn off the error display so this isn't a problem
 later.

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

From noreply at wordpress.org  Fri Mar  4 01:20:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 01:20:26 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is not
 updated after a plugin is deleted
Message-ID: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
--------------------------------+-----------------------------
 Reporter:  mitogh              |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  Plugins             |    Version:  5.9.1
 Severity:  normal              |   Keywords:
  Focuses:  ui, administration  |
--------------------------------+-----------------------------
 == Context

 When a plugin is deleted, the total count is updated correctly on the left
 count, however, the total count is not updated correctly on the right
 count (as you can see on the screenshot) and by following the steps to
 replicate this problem.


 == Steps to replicate.

 1. Install any plugin
 2. Activate the plugin
 3. Go to the plugin lists
 4. Deactivate the plugin
 5. Observe the total count of active plugins
 6. Click on Delete and accept the prompt to remove it.
 7. Observe how the total count decreased by 1 but the total items count on
 the right was not modified after the plugin was deleted.

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

From noreply at wordpress.org  Fri Mar  4 01:20:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 01:20:36 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.e43f4a311ef68deff6fae4efb8225f73@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
--------------------------+---------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Plugins       |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  ui, administration
--------------------------+---------------------------------
Changes (by mitogh):

 * Attachment "2022-03-03_19-17.png" added.


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

From noreply at wordpress.org  Fri Mar  4 01:24:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 01:24:42 -0000
Subject: [wp-trac] [WordPress Trac] #53685: Update the `caniuse`
 database when running `grunt precommit:css`
In-Reply-To: <051.13fbecdfcc2de797d45f32da538db2f7@wordpress.org>
References: <051.13fbecdfcc2de797d45f32da538db2f7@wordpress.org>
Message-ID: <066.2843a57e54ce9224d8180f06f876eff4@wordpress.org>

#53685: Update the `caniuse` database when running `grunt precommit:css`
------------------------------+------------------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:  css
------------------------------+------------------------------

Comment (by ironprogrammer):

 Hi, @desrosj 👋🏻:

 In my testing with npm v6.14.16, it is still an issue where `package-
 lock.json` indentation is converted to 2 spaces. This can be worked around
 by first deleting the lock file, where the `browserslist` update will copy
 the indentation from `package.json` (as expected) while regenerating the
 lock file. (See "Short Term Maintenance" below.)

 On the other hand, in npm v7-8, the indentation issue appears to have been
 fixed. During the lock file update, tabs are preserved, but v7 introduced
 `"lockFileVersion": 2` to `package.json`. It would seem that in order to
 support a pre-commit check for the latest `caniuse-lite` data, it would
 need to happen ''after'' migrating npm to a higher version.

 === Short Term Maintenance

 I've prepared a patch ([https://core.trac.wordpress.org/ticket/53685 PR
 2379]) for the `caniuse-lite` DB with npm 6.14.16, if we ''only'' wanted
 to bring the browsers list up to date. Here is the list of changes as of
 today:

 {{{
 Target browser changes:
 - and_chr 91
 + and_chr 98
 - and_uc 12.12
 - android 91
 + android 98
 - chrome 91
 - chrome 90
 + chrome 98
 + chrome 97
 + chrome 96
 - edge 91
 - edge 90
 + edge 98
 + edge 97
 + edge 96
 - firefox 90
 - firefox 89
 + firefox 97
 + firefox 96
 + firefox 95
 - ios_saf 14.5-14.7
 - ios_saf 14.0-14.4
 + ios_saf 15.2-15.3
 + ios_saf 15.0-15.1
 + ios_saf 14.5-14.8
 - opera 77
 - opera 76
 + opera 83
 + opera 82
 - safari 14
 + safari 15.2-15.3
 + safari 15.1
 - samsung 14.0
 + samsung 16.0
 }}}

 I know this doesn't address the need to update `precommit:css`, but offers
 some additional time while an update to npm is considered.

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

From noreply at wordpress.org  Fri Mar  4 01:28:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 01:28:35 -0000
Subject: [wp-trac] [WordPress Trac] #53685: Update the `caniuse`
 database when running `grunt precommit:css`
In-Reply-To: <051.13fbecdfcc2de797d45f32da538db2f7@wordpress.org>
References: <051.13fbecdfcc2de797d45f32da538db2f7@wordpress.org>
Message-ID: <066.70825a4c93bf2ea157b42c2a16fe446d@wordpress.org>

#53685: Update the `caniuse` database when running `grunt precommit:css`
------------------------------+------------------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:  css
------------------------------+------------------------------

Comment (by ironprogrammer):

 > {{{#!comment
 > 1058732087
 > }}}
 > [https://github.com/dream-encode dream-encode] commented on
 [https://github.com/WordPress/wordpress-
 develop/pull/2379#issuecomment-1058732087 PR #2379]:

 Hi, @dream-encode:

 Yes, sorry my explanation of why this might be a short-term maintenance
 item was taking a bit long to compose 😅 I do understand what the
 underlying objective is. This would be purely short term maintenance.

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

From noreply at wordpress.org  Fri Mar  4 01:43:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 01:43:47 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.9a485fa9c7ffe5e428041a3b761f2211@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------

Comment (by BettyJJ):

 Replying to [comment:9 afercia]:
 Thanks for your effort. I tried your patch and it does not seem to work.
 It seems that `event.isComposing` will become false when `esc` is pressed.
 See a minimal demo here: https://jsfiddle.net/Lgv7sayq/1/ Tested with the
 default Chinese IME shipped with Windows 10.

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

From noreply at wordpress.org  Fri Mar  4 02:04:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 02:04:30 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.3925bd293a4fffce766e72929d755967@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch commit                               |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 This code may need to be more specific.

 Via a [http://useragentstring.com/pages/useragentstring.php?name=All list
 of user agents chosen at random], I discovered there is an old version of
 Ubuntu called `Edgy Eft`.

 It's an edge case (pun intended) but the change should probably account
 for the version of Firefox that include the OS name.

 Maybe check for `Edg/`, `EdgiOS/` and `EdgA/`. The annoyance here is that
 you'll probably need to include the previous check for `edge` for older
 versions.

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

From noreply at wordpress.org  Fri Mar  4 02:04:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 02:04:45 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.0027805dd83c596733b82d3ef9651a2c@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch                                      |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  good-first-bug has-testing-info has-patch commit => good-
     first-bug has-testing-info has-patch


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

From noreply at wordpress.org  Fri Mar  4 02:09:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 02:09:13 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.d769ddd5b328761d8fca3c986eab0ece@wordpress.org>

#36949: Term exists should use get_terms internally
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  2.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note                                           |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests needs-dev-note commit => has-patch
     has-unit-tests needs-dev-note


Comment:

 I pushed an intentionally broken test to [https://github.com/WordPress
 /wordpress-develop/pull/2318 PR#2318] earlier today to demonstrate a
 question I had about `get_term()` -- ie, the singular. I'll remove the
 commit keyword for now.

 Do yell out if I am highlighting something that is intentionally out of
 scope.

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

From noreply at wordpress.org  Fri Mar  4 02:30:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 02:30:03 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.5f0b194f692f8ef76b16a6362ce87e23@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch                                      |
-------------------------------------------------+-------------------------

Comment (by costdev):

 `Edgy Eft` uses `Ubuntu-edgy`:

 Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20060601
 Firefox/2.0.0.1 (Ubuntu-edgy)

 Since `strpos()` is case sensitive, it returns `false`:
 [https://3v4l.org/LVH3U 3v4l]

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

From noreply at wordpress.org  Fri Mar  4 02:50:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 02:50:11 -0000
Subject: [wp-trac] [WordPress Trac] #54770: The term "Current Theme" is
 ambiguous
In-Reply-To: <053.98abc1a7fac13c318ce11d048f7e3568@wordpress.org>
References: <053.98abc1a7fac13c318ce11d048f7e3568@wordpress.org>
Message-ID: <068.964b1a30da3cbc62bf887c5476e4b427@wordpress.org>

#54770: The term "Current Theme" is ambiguous
-------------------------+---------------------------------
 Reporter:  Presskopp    |       Owner:  audrasjb
     Type:  enhancement  |      Status:  reopened
 Priority:  normal       |   Milestone:  6.0
Component:  Themes       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, administration
-------------------------+---------------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch commit => has-patch


Comment:

 To keep the report accurate, I am removing the commit keyword while
 discussion ensues.

 FWIW, I think "active" is a fine term. The number of items permitted to be
 active at any one time doesn't affect whether they are active.

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

From noreply at wordpress.org  Fri Mar  4 02:51:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 02:51:39 -0000
Subject: [wp-trac] [WordPress Trac] #54878: Don't show links to the
 Customizer when installing themes using api.wordpress.org
In-Reply-To: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
References: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
Message-ID: <072.089cc51a559048aeebd872d21a35f7d9@wordpress.org>

#54878: Don't show links to the Customizer when installing themes using
api.wordpress.org
-------------------------------------------------+-------------------------
 Reporter:  antonvlasenko                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  5.9.2
Component:  Themes                               |     Version:  5.9
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-screenshots commit     |     Focuses:
  fixed-major                                    |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-screenshots commit => has-patch has-screenshots
     commit fixed-major


Comment:

 Committed in [52819] but waiting for trac to catch up:

 > Themes: Hide block themes' live preview link following installation.
 >
 > Prevent the Customizer/Live Preview button from showing for installed
 block themes when on the theme installation page.
 >
 > Props antonvlasenko, costdev, ironprogrammer.
 > Fixes #54878.

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

From noreply at wordpress.org  Fri Mar  4 03:01:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 03:01:12 -0000
Subject: [wp-trac] [WordPress Trac] #54673: Improve formatting in
 `/wp-admin/user-edit.php`.
In-Reply-To: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
References: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
Message-ID: <066.338d71f4dfaf226d54087dcb2d44bb23@wordpress.org>

#54673: Improve formatting in `/wp-admin/user-edit.php`.
-----------------------------+-------------------------------
 Reporter:  costdev          |       Owner:  audrasjb
     Type:  enhancement      |      Status:  reviewing
 Priority:  normal           |   Milestone:  6.0
Component:  Administration   |     Version:  5.9
 Severity:  normal           |  Resolution:
 Keywords:  has-patch early  |     Focuses:  coding-standards
-----------------------------+-------------------------------
Changes (by peterwilsoncc):

 * Attachment "trunk-edit-user.png" added.

 Edit user screen (trunk)

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

From noreply at wordpress.org  Fri Mar  4 03:01:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 03:01:34 -0000
Subject: [wp-trac] [WordPress Trac] #54673: Improve formatting in
 `/wp-admin/user-edit.php`.
In-Reply-To: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
References: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
Message-ID: <066.0e41f164959c1177c0019a05ff78acf1@wordpress.org>

#54673: Improve formatting in `/wp-admin/user-edit.php`.
-----------------------------+-------------------------------
 Reporter:  costdev          |       Owner:  audrasjb
     Type:  enhancement      |      Status:  reviewing
 Priority:  normal           |   Milestone:  6.0
Component:  Administration   |     Version:  5.9
 Severity:  normal           |  Resolution:
 Keywords:  has-patch early  |     Focuses:  coding-standards
-----------------------------+-------------------------------
Changes (by peterwilsoncc):

 * Attachment "pr-edit-user.png" added.

 Edit user screen (pull request)

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

From noreply at wordpress.org  Fri Mar  4 03:11:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 03:11:54 -0000
Subject: [wp-trac] [WordPress Trac] #54673: Improve formatting in
 `/wp-admin/user-edit.php`.
In-Reply-To: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
References: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
Message-ID: <066.a7838b5dad1605255eff68537b58f6a7@wordpress.org>

#54673: Improve formatting in `/wp-admin/user-edit.php`.
------------------------------------+-------------------------------
 Reporter:  costdev                 |       Owner:  audrasjb
     Type:  enhancement             |      Status:  reviewing
 Priority:  normal                  |   Milestone:  6.0
Component:  Administration          |     Version:  5.9
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch early commit  |     Focuses:  coding-standards
------------------------------------+-------------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch early => has-patch early commit


Comment:

 Reviewed linked pull request with white space suppressed.

 The changes look good to me. Screenshots comparing the screens between the
 proposed changes and trunk show no apparent difference.

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

From noreply at wordpress.org  Fri Mar  4 04:56:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 04:56:43 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly
 with Odysee.com (half working)
In-Reply-To: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
References: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
Message-ID: <070.1b45d1250a561dd56f6b4344f566bc88@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+------------------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+------------------------------

Comment (by tomatodysee):

 Replying to [comment:4 peterwilsoncc]:
 > The [https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe
 #attr-sandbox sandbox attribute documentation] on MDN is pretty clear
 about this:
 >
 > > When the embedded document has the same origin as the embedding page,
 it is strongly discouraged to use both allow-scripts and allow-same-
 origin, **as that lets the embedded document remove the sandbox
 attribute** — making it no more secure than not using the sandbox
 attribute at all.
 >
 > (my emphasis)
 >
 > Locking down access to `window.parent` within auto-discovered embeds is
 quite intentional. The `sandbox` attribute's settings were discussed in
 #32522 but it's quite lengthy.

 My emphasis:
 > **When the embedded document has the same origin as the embedding
 page**, it is strongly discouraged to use both allow-scripts and allow-
 same-origin, as that lets the embedded document remove the sandbox
 attribute — making it no more secure than not using the sandbox attribute
 at all.

 So since wordpress and odysee are not the same origin (domain), this
 doesn't apply from what I understand.

 From https://core.trac.wordpress.org/changeset/34903, it also sounds like
 it's possible to embed wordpress on other sites, and that embed has the
 proper security restrictions.

 Is the concern that someone may embed a wordpress page on odysee, and then
 that is embedded on another wordpress site? Or someone embedding a
 wordpress site that has an odysee embed, on Odysee? The first isn't
 possible because we don't support iframes/oembed consumers, and the 2nd
 would be protected by the wordpress iframe security settings.

 I don't mean to stir up confusion or rehashing of an old decision about
 this, it's just that iframes + iframe security are fairly complicated, and
 hence, misunderstood. All my research has shown similar findings to the
 above arguement about it being on different domains.

 Our embeds also work via iframes if users have a paid wordpress account,
 so we'd have the same security vulnerability there if this were true (and
 it would also apply to other, more malicious sites/actors).

 We're just trying to make it easier out of the box by using the Odysee
 URLs vs embed code. If going down the oembed provider path is the only
 way, we can try to do that, but it sounds overkill + will take quite a bit
 of time.

 Appreciate your time and feedback once again!

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

From noreply at wordpress.org  Fri Mar  4 05:50:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 05:50:48 -0000
Subject: [wp-trac] [WordPress Trac] #46907: Pass current request object
 to rest_authentication_errors filter
In-Reply-To: <051.b14ce9f322f5118cf8a2e0feff3db4d6@wordpress.org>
References: <051.b14ce9f322f5118cf8a2e0feff3db4d6@wordpress.org>
Message-ID: <066.f5794a761782161b002b3d5836fe48b0@wordpress.org>

#46907: Pass current request object to rest_authentication_errors filter
-------------------------+-----------------------
 Reporter:  ocean90      |       Owner:  ocean90
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  REST API     |     Version:
 Severity:  normal       |  Resolution:  wontfix
 Keywords:  needs-patch  |     Focuses:  rest-api
-------------------------+-----------------------

Comment (by kakomap):

 Hi here,
 I've followed this and I'd like to add a use-case where the `$request`
 might be useful. A plugin might, like in my case, want to have the REST
 API restricted for all API requests except some particular endpoints.

 The plugin needs to hook into `rest_authentication_errors` but needs to
 return `WP_Error|null|true` based on the request being processed.

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

From noreply at wordpress.org  Fri Mar  4 06:28:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 06:28:10 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.e0c6f493cd71cf6b8d8113a43efd4c03@wordpress.org>

#36907: Improved sticky post query
----------------------------------------+---------------------------
 Reporter:  spacedmonkey                |       Owner:  spacedmonkey
     Type:  enhancement                 |      Status:  assigned
 Priority:  normal                      |   Milestone:  6.0
Component:  Query                       |     Version:  3.5
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:  performance
----------------------------------------+---------------------------
Changes (by rehanali):

 * Attachment "#36907.patch" added.

 Added patch

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

From noreply at wordpress.org  Fri Mar  4 06:48:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 06:48:57 -0000
Subject: [wp-trac] [WordPress Trac] #17851: Wrapping Sections with
 add_settings_section
In-Reply-To: <053.ac36c57cc64378fd983a2bf637f0d159@wordpress.org>
References: <053.ac36c57cc64378fd983a2bf637f0d159@wordpress.org>
Message-ID: <068.1b508226951285d8ecc39c8ba38e1464@wordpress.org>

#17851: Wrapping Sections with add_settings_section
-------------------------------------------------+-------------------------
 Reporter:  griffinjt                            |       Owner:  chriscct7
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:
Component:  Administration                       |     Version:  3.1.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch good-first-bug needs-      |     Focuses:
  unit-tests needs-testing                       |
-------------------------------------------------+-------------------------
Changes (by rehanali):

 * Attachment "#17851.patch" added.

 Added patch

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

From noreply at wordpress.org  Fri Mar  4 06:55:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 06:55:12 -0000
Subject: [wp-trac] [WordPress Trac] #41594: Edit tag form limited to
 800px width
In-Reply-To: <054.392b0b5071a914217061e13ae2e3d37c@wordpress.org>
References: <054.392b0b5071a914217061e13ae2e3d37c@wordpress.org>
Message-ID: <069.f15353ad2d2f823d60d8c2237187bde6@wordpress.org>

#41594: Edit tag form limited to 800px width
-------------------------------------+-------------------------------------
 Reporter:  fabienlege               |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Taxonomy                 |     Version:  4.8.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-           |     Focuses:  ui, administration,
  screenshots                        |  template
-------------------------------------+-------------------------------------
Changes (by rehanali):

 * Attachment "#41594.patch" added.

 Added patch

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

From noreply at wordpress.org  Fri Mar  4 07:09:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 07:09:19 -0000
Subject: [wp-trac] [WordPress Trac] #55317: get_header() function does not
 work with block based themes
Message-ID: <062.58263221eb1cd35a6d4cc3b2c0b3bc71@wordpress.org>

#55317: get_header() function does not work with block based themes
--------------------------------+-----------------------------
 Reporter:  randhirexpresstech  |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  General             |    Version:  5.9.1
 Severity:  blocker             |   Keywords:
  Focuses:  template            |
--------------------------------+-----------------------------
 Block based themes like Twenty Twenty-Two do not contain php templates.
 Since,get_header() function use php header templates, it generate a
 warning
 "Deprecated: Theme without header.php is deprecated since version 3.0.0
 with no alternative available. Please include a header.php template in
 your theme."

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

From noreply at wordpress.org  Fri Mar  4 09:27:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 09:27:25 -0000
Subject: [wp-trac] [WordPress Trac] #55318: Do Something of site hack..
Message-ID: <052.62632ab68275c6017968b4bc3b7a4306@wordpress.org>

#55318: Do Something of site hack..
-----------------------------+-----------------------------
 Reporter:  hkdhvani         |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  General          |    Version:  5.9.1
 Severity:  normal           |   Keywords:  dev-feedback
  Focuses:                   |
-----------------------------+-----------------------------
 I have made too many sites using WordPress , every time my E-Commerce site
 get hacked and its hacked like , I have to add old backup which leads my
 clients to loss.. Please solve this hacking issues in WordPress Site and
 provide something that can secure WordPress like other CMS Platforms..
 Because of often site hacking , Users are changing their CMS Platform from
 WordPress to another..

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

From noreply at wordpress.org  Fri Mar  4 09:43:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 09:43:51 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.888a631a97ec83adc22c623a1b7d55d1@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by pgpagely):

 An additional finding is that if the `gutenberg` plugin is enabled then
 the following hack is needed so that the `view.min.js` URL is not broken
 (with `gutenberg` disabled only the hack in the original message is
 needed):

 {{{#!php
 add_filter("script_loader_src", function ($src) {
     return preg_replace("#/wp-includes/wordpress-versions/[0-9.]+/#", "/",
 $src);
 });
 }}}

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

From noreply at wordpress.org  Fri Mar  4 10:12:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 10:12:26 -0000
Subject: [wp-trac] [WordPress Trac] #55318: Do Something of site hack..
In-Reply-To: <052.62632ab68275c6017968b4bc3b7a4306@wordpress.org>
References: <052.62632ab68275c6017968b4bc3b7a4306@wordpress.org>
Message-ID: <067.6abbd59a6331390a36d697abeae7db20@wordpress.org>

#55318: Do Something of site hack..
--------------------------------+------------------------------
 Reporter:  hkdhvani            |       Owner:  (none)
     Type:  feature request     |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  General             |     Version:  trunk
 Severity:  normal              |  Resolution:
 Keywords:  dev-feedback close  |     Focuses:
--------------------------------+------------------------------
Changes (by costdev):

 * keywords:  dev-feedback => dev-feedback close
 * version:  5.9.1 => trunk


Comment:

 Hi @hkdhvani, welcome to Trac!

 Sorry to hear that you've been experiencing attacks on your clients'
 websites.

 If you have a specific potential security vulnerability to report, please
 read [https://make.wordpress.org/core/handbook/testing/reporting-security-
 vulnerabilities/ Reporting Security Vulnerabilities].

 Otherwise, please take a look at [https://wordpress.org/support/article
 /hardening-wordpress/ Hardening WordPress]. You may particularly benefit
 from the [https://wordpress.org/support/article/hardening-
 wordpress/#firewall Firewall] section.

 As Trac is for the development of WordPress Core rather than for support
 or resolving security vulnerabilities, you can get some help from the
 folks over on [https://wordpress.org/support/forums/ the support forums].

 I'll leave this ticket open for another core developer to give their
 feedback, but I propose that this ticket is closed.

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

From noreply at wordpress.org  Fri Mar  4 10:12:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 10:12:48 -0000
Subject: [wp-trac] [WordPress Trac] #55318: Do Something of site hack..
In-Reply-To: <052.62632ab68275c6017968b4bc3b7a4306@wordpress.org>
References: <052.62632ab68275c6017968b4bc3b7a4306@wordpress.org>
Message-ID: <067.652f5fc148a8941bbed636aed3a25e98@wordpress.org>

#55318: Do Something of site hack..
--------------------------------+------------------------------
 Reporter:  hkdhvani            |       Owner:  (none)
     Type:  feature request     |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Security            |     Version:  trunk
 Severity:  normal              |  Resolution:
 Keywords:  dev-feedback close  |     Focuses:
--------------------------------+------------------------------
Changes (by costdev):

 * component:  General => Security


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

From noreply at wordpress.org  Fri Mar  4 10:19:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 10:19:44 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.5ec000d041aec10ecfa661c41761f1d5@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------+---------------------------------
 Reporter:  mitogh       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui, administration
-------------------------+---------------------------------
Changes (by costdev):

 * version:  5.9.1 =>
 * type:  defect (bug) => enhancement
 * milestone:  Awaiting Review => 6.0


Comment:

 == Reproc Report

 === Env
 * Web Server: Apache (Linux)
 * WordPress: 6.0-alpha-52448-src
 * Browser: Chrome
 * OS: Windows 10
 * Theme: Twenty Twenty-Two
 * Plugins: Enable Customizer

 === Steps to test
 1. Navigate to `Plugins > Installed Plugins`.
 2. Observe the total count of "All" plugins.
 3. Click on Delete and accept the prompt to remove it.
 4. Observe how the total count decreased by 1 but the total items count on
 the right was not modified after the plugin was deleted.

 === Results
 1. The count on the right is not updated. Issue reproduced. ✅

 Milestoning for 6.0 and removing the version as this will have existed for
 quite some time.

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

From noreply at wordpress.org  Fri Mar  4 10:23:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 10:23:45 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.99b81e2ba7167bc1cedc1a57770929f4@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------+---------------------------------
 Reporter:  mitogh       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui, administration
-------------------------+---------------------------------
Changes (by costdev):

 * Attachment "55316.diff" added.

 Update item count upon plugin deletion. Do not commit this patch - it
 needs review for i18n.

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

From noreply at wordpress.org  Fri Mar  4 10:26:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 10:26:24 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.0241a6410f974c793820ecd9f43790ee@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:   => needs-testing has-testing-info needs-refresh


Comment:

 Patch [https://core.trac.wordpress.org/attachment/ticket/55316/55316.diff
 55316.diff] should update the item count when a plugin is deleted.

 However, this does not account for i18n/rtl and will need some input from
 a developer familiar with this.

 Steps to test:

 1. Navigate to `Plugins > Installed Plugins`.
 2. Observe the total count of "All" plugins.
 3. Click on Delete and accept the prompt to remove it.
 4. Observe how the total count decreased by 1 but the total items count on
 the right was not modified after the plugin was deleted.
 5. Apply
 [https://core.trac.wordpress.org/attachment/ticket/55316/55316.diff
 55316.diff].
 6. Run `npm run build:dev`.
 7. Navigation to `Plugins > Installed Plugins`.
 8. Do a hard refresh to ensure that scripts have been refreshed.
 9. Repeat steps 2-4. This time, the item count should decrease by 1 as
 expected.

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

From noreply at wordpress.org  Fri Mar  4 10:34:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 10:34:30 -0000
Subject: [wp-trac] [WordPress Trac] #55319: Add filter to
 get_block_wrapper_attributes function
Message-ID: <055.c3dd2dc2cdc0efb693ac3992b1d4f938@wordpress.org>

#55319: Add filter to get_block_wrapper_attributes function
-------------------------+-----------------------------
 Reporter:  fabiankaegy  |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Editor       |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 **What problem does this address?**

 It is currently possible to add custom classnames to static blocks using
 the blocks.getSaveContent.extraProps filter in JS. This is super useful
 when working with custom block supports. And even core uses this system in
 js to add the classnames generated for for example the color classes.

 In PHP however, for custom blocks this is all hardcoded in the
 get_block_wrapper_attributes function. Specifically inside the
 WP_Block_Supports Class here:
 https://github.com/WordPress/WordPress/blob/92f0b0cb48a3de660655cc658fc739695a393096
 /wp-includes/class-wp-block-supports.php#L93-L128

 This approach makes it impossible for custom supports that plugins develop
 to apply to custom blocks.

 **What is your proposed solution?**

 This could be solved by adding a new hook in PHP to the
 get_block_wrapper_attributes function which should work the same as the
 blocks.getSaveContent.extraProps hook in js.


 This ticket was first created in GitHub on the Gutenberg repository in
 [#38830](https://github.com/WordPress/gutenberg/issues/38830) but as the
 code no longer exists in Gutenberg since it was moved to core in 5.8 it
 was suggested that the change needs to happen in core directly.

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

From noreply at wordpress.org  Fri Mar  4 10:35:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 10:35:43 -0000
Subject: [wp-trac] [WordPress Trac] #55319: Add filter to
 get_block_wrapper_attributes function
In-Reply-To: <055.c3dd2dc2cdc0efb693ac3992b1d4f938@wordpress.org>
References: <055.c3dd2dc2cdc0efb693ac3992b1d4f938@wordpress.org>
Message-ID: <070.d4b31bc3bae716d73fc4c0b84eebf4dd@wordpress.org>

#55319: Add filter to get_block_wrapper_attributes function
-------------------------+------------------------------
 Reporter:  fabiankaegy  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by fabiankaegy):

 This ticket and how it should be approached was discussed in slack here:
 https://wordpress.slack.com/archives/C02QB2JS7/p1646070868485339

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

From noreply at wordpress.org  Fri Mar  4 10:50:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 10:50:21 -0000
Subject: [wp-trac] [WordPress Trac] #55023: get_header() notice: Theme
 without header.php is deprecated (was: deprecated issue on multisite
 reqgister page.)
In-Reply-To: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
References: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
Message-ID: <064.0a9c504f6964eeeb679d00feda6552ee@wordpress.org>

#55023: get_header() notice: Theme without header.php is deprecated
--------------------------+------------------------
 Reporter:  kpdaa         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.2
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  multisite
--------------------------+------------------------

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

From noreply at wordpress.org  Fri Mar  4 10:51:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 10:51:00 -0000
Subject: [wp-trac] [WordPress Trac] #55317: get_header() function does
 not work with block based themes
In-Reply-To: <062.58263221eb1cd35a6d4cc3b2c0b3bc71@wordpress.org>
References: <062.58263221eb1cd35a6d4cc3b2c0b3bc71@wordpress.org>
Message-ID: <077.86c1fd7de23e889c465814a53d482659@wordpress.org>

#55317: get_header() function does not work with block based themes
--------------------------------+------------------------
 Reporter:  randhirexpresstech  |       Owner:  (none)
     Type:  defect (bug)        |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  Themes              |     Version:  5.9.1
 Severity:  blocker             |  Resolution:  duplicate
 Keywords:                      |     Focuses:  template
--------------------------------+------------------------
Changes (by SergeyBiryukov):

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


Comment:

 Hi there, welcome to WordPress Trac!

 Thanks for the report, we're already tracking this issue in #55023.

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

From noreply at wordpress.org  Fri Mar  4 11:05:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 11:05:16 -0000
Subject: [wp-trac] [WordPress Trac] #50924: Do not use ZWNJ and ZWJ in
 post name (slug and url)
In-Reply-To: <053.89897d2f271d4c2edcec77b3858b6ff9@wordpress.org>
References: <053.89897d2f271d4c2edcec77b3858b6ff9@wordpress.org>
Message-ID: <068.168cef77a02f190fd234dfa9d0877859@wordpress.org>

#50924: Do not use ZWNJ and ZWJ in post name (slug and url)
-------------------------------------------------+-------------------------
 Reporter:  behzadian                            |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:
Component:  Permalinks                           |     Version:
 Severity:  normal                               |  Resolution:  duplicate
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing-info                                   |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * status:  accepted => closed
 * resolution:   => duplicate
 * milestone:  Future Release =>


Comment:

 This appears to be resolved as part of [51984] / #47912.

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

From noreply at wordpress.org  Fri Mar  4 11:22:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 11:22:24 -0000
Subject: [wp-trac] [WordPress Trac] #54673: Improve formatting in
 `/wp-admin/user-edit.php`.
In-Reply-To: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
References: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
Message-ID: <066.f7f9f7a716fb7c1736165e5a76e07b1c@wordpress.org>

#54673: Improve formatting in `/wp-admin/user-edit.php`.
------------------------------------+-------------------------------
 Reporter:  costdev                 |       Owner:  audrasjb
     Type:  enhancement             |      Status:  reviewing
 Priority:  normal                  |   Milestone:  6.0
Component:  Administration          |     Version:  5.9
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch early commit  |     Focuses:  coding-standards
------------------------------------+-------------------------------

Comment (by audrasjb):

 Alright, let's commit this PR.

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

From noreply at wordpress.org  Fri Mar  4 11:28:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 11:28:09 -0000
Subject: [wp-trac] [WordPress Trac] #54673: Improve formatting in
 `/wp-admin/user-edit.php`.
In-Reply-To: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
References: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
Message-ID: <066.eac293f29aaab2f27bb62d32b5cf6c2a@wordpress.org>

#54673: Improve formatting in `/wp-admin/user-edit.php`.
------------------------------------+-------------------------------
 Reporter:  costdev                 |       Owner:  audrasjb
     Type:  enhancement             |      Status:  closed
 Priority:  normal                  |   Milestone:  6.0
Component:  Administration          |     Version:  5.9
 Severity:  normal                  |  Resolution:  fixed
 Keywords:  has-patch early commit  |     Focuses:  coding-standards
------------------------------------+-------------------------------
Changes (by audrasjb):

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


Comment:

 In [changeset:"52820" 52820]:
 {{{
 #!CommitTicketReference repository="" revision="52820"
 Coding Standards: Improve formatting in `/wp-admin/user-edit.php`.

 This change improves the formatting of `/wp-admin/user-edit.php` to avoid
 PHPCS failures when adding new code, which previously required new code to
 be indented multiple times, breaking alignment of the HTML parts. This
 change avoids disabling/enabling PHPCS for failing sniffs.

 Props costdev, johnregan3, peterwilsoncc.
 Fixes #54673.
 }}}

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

From noreply at wordpress.org  Fri Mar  4 13:29:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 13:29:33 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.d65f33b69999fc59c233b636eaffaa73@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:
                                                 |  johnbillion
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:
  refresh                                        |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch dev-feedback => has-patch dev-feedback needs-refresh
 * milestone:  Future Release => 6.0


Comment:

 Moving for 6.0 consideration
 Also marking as `needs-refresh` since it doesn't apply anymore against
 trunk.
 (see https://wordpress.slack.com/archives/C02RQBWTW/p1646400165837319).

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

From noreply at wordpress.org  Fri Mar  4 13:39:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 13:39:24 -0000
Subject: [wp-trac] [WordPress Trac] #55320: Twenty Twenty-Two
Message-ID: <051.3c0096ce451f3d88c60ff2d61518c871@wordpress.org>

#55320: Twenty Twenty-Two
---------------------------+-----------------------------
 Reporter:  daveydo        |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Bundled Theme  |    Version:
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 The monitor of the Twenty Twenty-Two forum asked me to relay this
 information to you:

 t-p wrote:

 If the theme is to be as flexible as suggested by the authors then the
 Drop cap as an option should be set true from the start so that all users
 can benefit, irrespective of technical knowledge.
 Please report that via https://core.trac.wordpress.org/newticket

 Please use the “Bundled Theme” component and start the Summary field with
 Twenty Twenty-Two

 Post Link: https://wordpress.org/support/topic/theme-upgrades-
 please/?view=all#post-15424860
 -----------

 Thank you.

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

From noreply at wordpress.org  Fri Mar  4 13:42:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 13:42:29 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.7a81d685f6a04c39de7b9764104b7aae@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch                                      |
-------------------------------------------------+-------------------------

Comment (by Boniu91):

 == Test Report

 === Env
 * WordPress 5.9 with patch applied
 * Edge 98.0.1108.62
 * Theme: Twenty Twenty One

 === Steps to test
 1. Added the following code to functions.php:
 {{{#!php
 global $is_edge;
 die( var_export( $is_edge, true ) );
 }}}
 2. Visited the page using Edge
 3. `true` is displayed

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

From noreply at wordpress.org  Fri Mar  4 13:51:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 13:51:41 -0000
Subject: [wp-trac] [WordPress Trac] #55320: Twenty Twenty-Two: Add Drop
 cap feature and the ability to change color of individual words other than
 links (was: Twenty Twenty-Two)
In-Reply-To: <051.3c0096ce451f3d88c60ff2d61518c871@wordpress.org>
References: <051.3c0096ce451f3d88c60ff2d61518c871@wordpress.org>
Message-ID: <066.89b4facacc8b89fa193d7cf6aa5948d4@wordpress.org>

#55320: Twenty Twenty-Two: Add Drop cap feature and the ability to change color of
individual words other than links
---------------------------+------------------------------
 Reporter:  daveydo        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

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

From noreply at wordpress.org  Fri Mar  4 14:10:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 14:10:15 -0000
Subject: [wp-trac] [WordPress Trac] #47912: Non-visible chars in title
 creates some encoded values in permalink
In-Reply-To: <054.413ca78da8b94d51590f3a3095f7726f@wordpress.org>
References: <054.413ca78da8b94d51590f3a3095f7726f@wordpress.org>
Message-ID: <069.ebae7a48afad5933371edf8951942787@wordpress.org>

#47912: Non-visible chars in title creates some encoded values in permalink
-------------------------------------+-------------------------------------
 Reporter:  dhanendran               |       Owner:  SergeyBiryukov
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:  5.9
Component:  Permalinks               |     Version:  5.2.2
 Severity:  major                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-      |     Focuses:  ui, rtl,
  tests commit has-testing-info      |  administration
-------------------------------------+-------------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52821" 52821]:
 {{{
 #!CommitTicketReference repository="" revision="52821"
 Docs: Add inline comments for non-visible characters in
 `sanitize_title_with_dashes()`.

 This aims to clarify the list of characters that are stripped from URLs or
 converted to a hyphen.

 Follow-up to [51984].

 See #47912, #54729.
 }}}

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

From noreply at wordpress.org  Fri Mar  4 14:10:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 14:10:15 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.1c8391e86a7af8917ffa90dea8b6e5b9@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  docs
----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52821" 52821]:
 {{{
 #!CommitTicketReference repository="" revision="52821"
 Docs: Add inline comments for non-visible characters in
 `sanitize_title_with_dashes()`.

 This aims to clarify the list of characters that are stripped from URLs or
 converted to a hyphen.

 Follow-up to [51984].

 See #47912, #54729.
 }}}

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

From noreply at wordpress.org  Fri Mar  4 14:16:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 14:16:09 -0000
Subject: [wp-trac] [WordPress Trac] #55313: Fix PHP Plugin
In-Reply-To: <053.c6421cf766a1fb9860c631944634d9b1@wordpress.org>
References: <053.c6421cf766a1fb9860c631944634d9b1@wordpress.org>
Message-ID: <068.fee840896547b68e9d57405832de34ff@wordpress.org>

#55313: Fix PHP Plugin
--------------------------+------------------------------
 Reporter:  ppatel821     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+------------------------------
Changes (by azouamauriac):

 * keywords:   => close
 * severity:  blocker => normal


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

From noreply at wordpress.org  Fri Mar  4 15:19:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 15:19:30 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.532ff1baf2336cce1e3cbc3f7bd86be0@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------
Changes (by azouamauriac):

 * Attachment "Screenshot at Mar 04 15-32-01 before patch.png" added.

 before patch

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

From noreply at wordpress.org  Fri Mar  4 15:20:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 15:20:14 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.0c5f43e2fff1edf10a6ee05050fa1daa@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------
Changes (by azouamauriac):

 * Attachment "Screenshot at Mar 04 15-52-01 after_patch_55316.png" added.

 After patch

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

From noreply at wordpress.org  Fri Mar  4 15:22:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 15:22:54 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.acbd88423b91ffa237036a108c823f51@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------
Changes (by azouamauriac):

 * Attachment "Screenshot at Mar 04 15-55-36
 after_patch_not_work_for_recent_active.png" added.

 After patch 'Recently Active' tab (it seems like patch does not work there
 )

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

From noreply at wordpress.org  Fri Mar  4 15:24:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 15:24:31 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.7b62c0b902eccb5dab7cb183e85dde70@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------
Changes (by azouamauriac):

 * Attachment "Screenshot at Mar 04 15-55-36
 after_patch_working_for_auto_disable.png" added.

 After patch; 'Auto-updates Disabled' tab (patch works)

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

From noreply at wordpress.org  Fri Mar  4 15:32:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 15:32:25 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.d8548ebcc48030b5f495423bbd4f225b@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------

Comment (by azouamauriac):

 Above some test result.

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

From noreply at wordpress.org  Fri Mar  4 15:38:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 15:38:13 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.1df59db113115764f7ac475fc7a86646@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------

Comment (by costdev):

 Thanks for the tests @azouamauriac!

 The patch is changing the value to `plugins.all.length`.

 That's why it looked like the patch worked in your second test, when in
 fact it was a coincedence that **All** and **Auto-updates Disabled** were
 the same number. I've have another look at the patch.

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

From noreply at wordpress.org  Fri Mar  4 15:53:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 15:53:16 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.4528ac88d17974bac11ebb4640462e58@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------
Changes (by costdev):

 * Attachment "55316.2.diff" added.

 Patch updated to use the count of the current view. Still needs a refresh
 for i18n if anyone is familiar with this.

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

From noreply at wordpress.org  Fri Mar  4 15:56:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 15:56:05 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.ba5e6d14d43bf2e31ddf30c111a6ff37@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------

Comment (by costdev):

 Patch updated if you have time to run more tests @azouamauriac

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

From noreply at wordpress.org  Fri Mar  4 16:04:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 16:04:43 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.a1712a84c5a086b1904c1f0627ba56af@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------

Comment (by swissspidy):

 For proper i18n you'll need to use `wp.i18n._n()` together with
 `wp.i18n.sprintf`. Make sure `wp-i18n` is a dependency of the `updates.js`
 script if not already the case.

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

From noreply at wordpress.org  Fri Mar  4 16:18:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 16:18:30 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.f28e43a81e11a20fa7fadb028fcee46c@wordpress.org>

#36949: Term exists should use get_terms internally
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  2.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note                                           |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 Thanks @peterwilsoncc . It is was a good spot. I have refactor the patch
 to remove usage of `get_term` and now everything uses `get_terms`. Unit
 tests are passing now

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

From noreply at wordpress.org  Fri Mar  4 16:18:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 16:18:48 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.39f300d92bb6bbf8ca2d0416d6c2a41b@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------

Comment (by costdev):

 Thanks @swissspidy! I'll take a look at this now.

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

From noreply at wordpress.org  Fri Mar  4 16:22:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 16:22:49 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.c208f7b6138661399cd699c8e3368689@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------
Changes (by azouamauriac):

 * Attachment "Screenshot at Mar 04 17-16-45
 after_patch_2_recently_active_works.png" added.

 after patch 55316.2.diff; same result for following tab: 'Inactive',
 'Auto-updates Disabled'. The patch works

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

From noreply at wordpress.org  Fri Mar  4 16:27:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 16:27:34 -0000
Subject: [wp-trac] [WordPress Trac] #55196: Twenty Twenty-Two - Search
 Magnifying SVG icon
In-Reply-To: <050.906544f38ac4c2f87c212c7e1f45cbe1@wordpress.org>
References: <050.906544f38ac4c2f87c212c7e1f45cbe1@wordpress.org>
Message-ID: <065.7f9158a496ee9bd6bb84939ec425a7d5@wordpress.org>

#55196: Twenty Twenty-Two - Search Magnifying SVG icon
--------------------------+--------------------------------
 Reporter:  utz119        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  reported-upstream
 Keywords:                |     Focuses:  accessibility
--------------------------+--------------------------------
Changes (by ryokuhi):

 * status:  new => closed
 * resolution:   => reported-upstream
 * milestone:  5.9.2 =>


Comment:

 We reviewed this ticket today during the Accessibility Team's bug-scrub.
 As the problem has been solved (and, as such, reported) in Gutenberg, we
 think this ticket might be closed.

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

From noreply at wordpress.org  Fri Mar  4 16:28:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 16:28:03 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.bd7b8018eb50ae274bdf42c42160a008@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------

Comment (by azouamauriac):

 Replying to [comment:5 costdev]:
 > Patch updated if you have time to run more tests @azouamauriac
 Done! Patch works on my side.

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

From noreply at wordpress.org  Fri Mar  4 16:34:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 16:34:14 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.85846dcc8256499038c490358a34fdec@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------

Comment (by costdev):

 Thanks @azouamauriac!

 I'll work on i18n and try to get this patch ready for further testing.

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

From noreply at wordpress.org  Fri Mar  4 16:47:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 16:47:02 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.374451f89969c17e8045cf015bed6a29@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------
Changes (by costdev):

 * Attachment "55316.3.diff" added.

 Patch updated with i18n.

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

From noreply at wordpress.org  Fri Mar  4 18:00:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 18:00:00 -0000
Subject: [wp-trac] [WordPress Trac] #55308: Update WordPress version URL
 target
In-Reply-To: <053.b8de66dd15e6204fc2c92a329b0c3c45@wordpress.org>
References: <053.b8de66dd15e6204fc2c92a329b0c3c45@wordpress.org>
Message-ID: <068.c661bcb288a3e2031280d6a78bf22182@wordpress.org>

#55308: Update WordPress version URL target
--------------------------+------------------------------------------------
 Reporter:  gazthink3     |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:                |     Version:
  Upgrade/Install         |
 Severity:  minor         |  Resolution:
 Keywords:  2nd-opinion   |     Focuses:  ui, accessibility, administration
  has-patch               |
--------------------------+------------------------------------------------
Changes (by sabernhardt):

 * type:  defect (bug) => enhancement
 * focuses:  ui, accessibility => ui, accessibility, administration
 * component:  General => Upgrade/Install
 * version:  trunk =>


Comment:

 Changing to enhancement, to consider the modal implementation (or
 something else other than `target="_blank"`)

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

From noreply at wordpress.org  Fri Mar  4 18:24:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 18:24:38 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.98fa0245016ba2483eaa6ea3e16910c9@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
--------------------------------------------+------------------------------
 Reporter:  mitogh                          |       Owner:  (none)
     Type:  enhancement                     |      Status:  new
 Priority:  normal                          |   Milestone:  6.0
Component:  Plugins                         |     Version:
 Severity:  normal                          |  Resolution:
 Keywords:  needs-testing has-testing-info  |     Focuses:  ui,
                                            |  administration
--------------------------------------------+------------------------------
Changes (by costdev):

 * keywords:  needs-testing has-testing-info needs-refresh => needs-testing
     has-testing-info


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

From noreply at wordpress.org  Fri Mar  4 19:24:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 19:24:42 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.8a0f73398ef70aa0c5bcea888c0c8b22@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------
Changes (by kebbet):

 * keywords:  needs-testing has-testing-info => needs-testing has-testing-
     info needs-refresh


Comment:

 Perhaps use {{{_nx()}}} in combination with {{{number_format_i18n()}}}
 instead of just {{{_n()}}}? That way a comment can be added that the items
 word in this case means plugins, and the counter is displayed in the
 locales number format.

 https://developer.wordpress.org/reference/functions/_nx/
 https://developer.wordpress.org/reference/functions/number_format_i18n/

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

From noreply at wordpress.org  Fri Mar  4 20:32:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 20:32:41 -0000
Subject: [wp-trac] [WordPress Trac] #51805: Clarify the prerequisites
 for updating the .htaccess file in flush_rewrite_rules()
In-Reply-To: <058.c9c541e7ab5b975da6eb6b33eee08d39@wordpress.org>
References: <058.c9c541e7ab5b975da6eb6b33eee08d39@wordpress.org>
Message-ID: <073.fdce5435343113a3d1b85d6661148a9e@wordpress.org>

#51805: Clarify the prerequisites for updating the .htaccess file in
flush_rewrite_rules()
----------------------------+-----------------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Future Release
Component:  Rewrite Rules   |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  docs
----------------------------+-----------------------------

Comment (by bwmarkle):

 +1

 Usually it's Stack Overflow that answers all my questions, but today it
 was this trac ticket!

 I'm creating a REST call to allow changing of a siteurl, and
 flush_rewrite_rules() wasn't working as expected. I ended up writing a
 wrapper function.

 {{{#!php
 <?php
 /**
  * A wrapper for WordPress' flush_rewrite_rules.
  *
  * Wrapper function is necessary because rewriting the .htaccess only
 works if the
  * save_mod_rewrite_rules() function exists, which only does in admin.
 This method ensures it's
  * there.
  *
  * @link https://core.trac.wordpress.org/ticket/51805
  *
  * @param bool $hard Whether to update .htaccess (hard flush) or just
 update rewrite_rules option
  *                   (soft flush).
  */
 public static function flush_rewrite_rules( $hard = true ) {
         // A requirement for rewriting the .htaccess file.
         if ( $hard && ! function_exists( 'save_mod_rewrite_rules' ) ) {
                 require_once ABSPATH . 'wp-admin/includes/misc.php';
         }

         flush_rewrite_rules( $hard );
 }
 }}}

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

From noreply at wordpress.org  Fri Mar  4 21:27:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 21:27:49 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.7a02e98ed4f9e4f94b4ca61ce6d791c5@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by afragen):

 Did you need to setup the chroot after your Debian upgrade? It seems that
 might be where your issue is, especially as downloaded file are in the
 expected locations.

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

From noreply at wordpress.org  Fri Mar  4 21:41:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 21:41:52 -0000
Subject: [wp-trac] [WordPress Trac] #33566: Keyboard shortcuts for all
 functionality on the dashboard
In-Reply-To: <048.074625b96bd37e525488ae07b55f8a58@wordpress.org>
References: <048.074625b96bd37e525488ae07b55f8a58@wordpress.org>
Message-ID: <063.8334334a54bafa42ea6f9d8a60c8c862@wordpress.org>

#33566: Keyboard shortcuts for all functionality on the dashboard
----------------------------+--------------------------------
 Reporter:  tady            |       Owner:  (none)
     Type:  enhancement     |      Status:  reopened
 Priority:  normal          |   Milestone:  Future Release
Component:  Administration  |     Version:  4.3
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  ui, accessibility
----------------------------+--------------------------------

Comment (by iandunn):

 GitHub [https://docs.github.com/en/get-started/using-github/github-
 command-palette recently launched an intent-driven interface].

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

From noreply at wordpress.org  Fri Mar  4 22:35:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 04 Mar 2022 22:35:16 -0000
Subject: [wp-trac] [WordPress Trac] #55264: Twenty Twenty-Two Looks Bad
 on Firefox
In-Reply-To: <052.c49ea7b317e9670bf4de4997faf4f168@wordpress.org>
References: <052.c49ea7b317e9670bf4de4997faf4f168@wordpress.org>
Message-ID: <067.eed80a5503aa2897673318ed2a4853b5@wordpress.org>

#55264: Twenty Twenty-Two Looks Bad on Firefox
-------------------------------+------------------------------
 Reporter:  aichedvs           |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Bundled Theme      |     Version:  5.9
 Severity:  critical           |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by aichedvs):

 Replying to [comment:6 aichedvs]:
 > Replying to [comment:4 audrasjb]:
 > > Hello and welcome to WordPress Core Trac @aichedvs,
 > >
 > > Replying to [comment:2 aichedvs]:
 > > > But the other issue I reported, with the pages loading first in
 plain text before quickly becoming formatted, is also occurring with
 Firefox (as well as Chrome and Edge).  This I consider an annoyance rather
 than a show stopper, but it should be addressed by the WordPress/Gutenberg
 folks.
 > >
 > > Does it also occur on a fresh install without any plugin? I can't
 reproduce the issue on my side in any browser.
 >
 > Removing plugins does not help.  The same issue has been posted by
 others in the Twenty Twenty-Two Support Forum with the title "Website
 content flickers when loaded".

 The site has been updated to WP 5.9.1 and the flicker problem appears to
 have gone away.  The site now looks good on the three browsers (Chrome,
 Edge, and Firefox), and the iPhone.

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

From noreply at wordpress.org  Sat Mar  5 00:36:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 00:36:20 -0000
Subject: [wp-trac] [WordPress Trac] #55189: Automatic removal of
 "Zero-width non-joiner" in URL
In-Reply-To: <053.3e9eb622a7f5219df8181821b4d758f9@wordpress.org>
References: <053.3e9eb622a7f5219df8181821b4d758f9@wordpress.org>
Message-ID: <068.60d15bb18b5d2ddd0fe0941b4e3a6f09@wordpress.org>

#55189: Automatic removal of "Zero-width non-joiner" in URL
--------------------------+---------------------
 Reporter:  man4toman     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.2
Component:  Permalinks    |     Version:  5.9
 Severity:  critical      |  Resolution:
 Keywords:  2nd-opinion   |     Focuses:
--------------------------+---------------------

Comment (by ironprogrammer):

 #50924 focused on the unsightly encoding of ZWNJ in the sample paths (e.g.
 `/پیامک%e2%80%8cها/`). The update provided by #47912 addresses that, but
 does so in a heavy-handed way: it strips them all out, disregarding
 context.

 As @SergeyBiryukov noted, #4328 has the potential to address the
 SEO/redirect concern reported. Though the age of that ticket isn't
 encouraging 😔 A simpler short-term fix could help impacted site owners.

 Also, apart from the [important] redirect concern, is there a concern
 about how this change to slugs may impact the "meaning" of paths in URLs?
 How important is it that the intended word(s) be maintained in the slug?
 [https://www.searchenginejournal.com/technical-seo/url-structure/ It's
 suggested that keywords in URLs these days don't impact SERPs], but that
 doesn't mean the words in paths should be inaccurate.

 ----

 For example, to expand on @man4toman's report, removing ZWNJ from slugs
 (or a `-` replacement) can change the meaning of the words used*:

   "Word"
   کلمه‌ای

 Removal of ZWNJ:

   "Cabbages"
   کلمهای

 In a post:

 [[Image(https://cldup.com/0OmYevLiq0.thumb.jpg, 50%)]]
 ''Post title is changed to a different word in slug.''

 This can also impact categories and tags, for example:

 [[Image(https://cldup.com/5kjEmgVY0Q.png, 75%)]]
 ''Potentially misleading category slug.''

 ''(*My apologies to Persian speakers for any translation inaccuracies
 above 😅. I used DuckDuckGo's translator for the meanings to illustrate
 this point.)''

 ----

 Related: According to Iran's NIC,
 [https://www.nic.ir/idn/#Rules_and_Restrictions IRNIC], the use of ZWNJ is
 acceptable in Persian domain names.

 I couldn't find domain rules related to ZWNJ in Arabic, but understand its
 use is less common than in Persian.

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

From noreply at wordpress.org  Sat Mar  5 00:58:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 00:58:31 -0000
Subject: [wp-trac] [WordPress Trac] #55189: Automatic removal of
 "Zero-width non-joiner" in URL
In-Reply-To: <053.3e9eb622a7f5219df8181821b4d758f9@wordpress.org>
References: <053.3e9eb622a7f5219df8181821b4d758f9@wordpress.org>
Message-ID: <068.96d5f4203a56e249fd45281800c24b6b@wordpress.org>

#55189: Automatic removal of "Zero-width non-joiner" in URL
--------------------------+---------------------
 Reporter:  man4toman     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.2
Component:  Permalinks    |     Version:  5.9
 Severity:  critical      |  Resolution:
 Keywords:  2nd-opinion   |     Focuses:
--------------------------+---------------------

Comment (by SergeyBiryukov):

 Replying to [comment:5 ironprogrammer]:
 > Also, apart from the [important] redirect concern, is there a concern
 about how this change to slugs may impact the "meaning" of paths in URLs?
 How important is it that the intended word(s) be maintained in the slug?
 [https://www.searchenginejournal.com/technical-seo/url-structure/ It's
 suggested that keywords in URLs these days don't impact SERPs], but that
 doesn't mean the words in paths should be inaccurate.

 Good point, we might need to check the locale and keep the character in
 certain locales if it changes the meaning of a post slug.

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

From noreply at wordpress.org  Sat Mar  5 01:11:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 01:11:03 -0000
Subject: [wp-trac] [WordPress Trac] #30580: wp_extract_urls not
 returning full URL with &amp; query separator
In-Reply-To: <051.51c6e567e72b36f7a4c97869788883ee@wordpress.org>
References: <051.51c6e567e72b36f7a4c97869788883ee@wordpress.org>
Message-ID: <066.ffc02109a3f0554262110253421a44a4@wordpress.org>

#30580: wp_extract_urls not returning full URL with &amp; query separator
----------------------------------------------------+---------------------
 Reporter:  trex005                                 |       Owner:  (none)
     Type:  defect (bug)                            |      Status:  new
 Priority:  normal                                  |   Milestone:
Component:  Formatting                              |     Version:  3.7
 Severity:  normal                                  |  Resolution:
 Keywords:  has-patch has-unit-tests needs-testing  |     Focuses:
----------------------------------------------------+---------------------
Changes (by ironprogrammer):

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


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

From noreply at wordpress.org  Sat Mar  5 01:17:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 01:17:12 -0000
Subject: [wp-trac] [WordPress Trac] #53218: Make apply_filters() variadic
In-Reply-To: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
References: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
Message-ID: <070.a615b8c49908c7b23192c0fb75a78e53@wordpress.org>

#53218: Make apply_filters() variadic
------------------------------------------+---------------------
 Reporter:  johnbillion                   |       Owner:  (none)
     Type:  enhancement                   |      Status:  new
 Priority:  normal                        |   Milestone:  6.0
Component:  Plugins                       |     Version:  5.3
 Severity:  normal                        |  Resolution:
 Keywords:  has-patch early dev-feedback  |     Focuses:
------------------------------------------+---------------------
Changes (by johnbillion):

 * keywords:  has-patch early => has-patch early dev-feedback


Comment:

 I'd like to get this in. Any objections?

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

From noreply at wordpress.org  Sat Mar  5 01:23:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 01:23:28 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in releases
 without a global theme auto-update setting renders installations insecure
Message-ID: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
---------------------------+-----------------------------
 Reporter:  bertvandepoel  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Themes         |    Version:
 Severity:  normal         |   Keywords:
  Focuses:  ui             |
---------------------------+-----------------------------
 I'm a member of a student organisation offering hosting to other student
 organisations at a Belgian university. Thanks to WordPress, organisation
 with a complete lack of technical ability are able to maintain a website,
 largely through enabling automatic updates of WordPress, its plugins and
 its themes.

 I understand it's a conscious choice of WordPress to add a theme every
 year through its releases. While I'm personally not a huge fan of these
 themes being added, I understand there isn't much we can do about that.
 However, many of our organisations assume that once they have enabled
 auto-updates, they're largely safe from maintenance issues. This isn't the
 case however since our a twentytwentytwo has only been installed a few
 months ago and very recently received its first update.

 There doesn't seem to be a global setting to enable all auto-updates or
 auto-updating for all themes anywhere in the web interface of WordPress.
 This will mean that we will have to email each organisation to try to
 explain what they have to do and how. This seems contradictory to the idea
 of WordPress being very user-friendly even for those with little technical
 skills.

 I would therefore either recommend a global setting concerning auto-
 updates, or ending the practise of adding a new theme every year without
 user consent.

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

From noreply at wordpress.org  Sat Mar  5 02:54:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 02:54:39 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in
 releases without a global theme auto-update setting renders installations
 insecure
In-Reply-To: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
References: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
Message-ID: <072.5ba1e81acb597a8e26056b9abccfdf59@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
-------------------------------+------------------------------
 Reporter:  bertvandepoel      |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Themes             |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+------------------------------
Changes (by costdev):

 * keywords:   => reporter-feedback
 * type:  defect (bug) => enhancement


Comment:

 Hi @bertvandepoel, welcome to Trac!

 There are numerous plugins to enable automatic updates. However, these
 tend to offer additional options that you may simply not need.

 You can alternatively save this code to a file called `enable-automatic-
 updates.php`, ZIP it and distribute it to the other organisations to
 install via the `Plugins > Add New > Upload`.

 {{{#!php
 <?php
 /**
  * Plugin Name: Automatic Theme Updates
  * Description: Enable automatic updating of all themes on your website.
  * Author:      WordPress Contributors
  * Author URI:  https://www.wordpress.org
  * License:     GPLv2 or later
  * License URI: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html
  * Version:     1.0.0
  */

 if ( defined( 'AUTOMATIC_UPDATER_DISABLED' ) && false ===
 AUTOMATIC_UPDATER_DISABLED ) {

     add_action(
         'admin_notices',
         static function() {
             $notice  = '<div class="notice notice-info is-dismissible">';
             $notice .= "<p><code>AUTOMATIC_UPDATER_DISABLED</code> is set
 and can't be overridden. Please delete the line from <code>wp-
 config.php</code>.</p>";
             $notice .= '</div>';
             echo $notice;
         }
     );

 } else {

     add_filter( 'auto_update_theme', '__return_true' );

 }
 }}}

 However, you can also simply disable the installation of themes bundled in
 upgrades if that is your preference.

 Add this to `wp-config.php`:
 {{{#!php
 define( 'CORE_UPGRADE_SKIP_NEW_BUNDLED', true );
 }}}

 Or create a plugin like the above if you want it to be easier for the
 organisations to make the change themselves.

 Note: If adding to a plugin, use:
 {{{#!php
 if ( ! defined( 'CORE_UPGRADE_SKIP_NEW_BUNDLED' ) ) {
     define( 'CORE_UPGRADE_SKIP_NEW_BUNDLED', true );
 }
 }}}

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

From noreply at wordpress.org  Sat Mar  5 05:36:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 05:36:31 -0000
Subject: [wp-trac] [WordPress Trac] #55230: Release 5.9.1 breaks
 administration login.
In-Reply-To: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
References: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
Message-ID: <072.04745d5273e27932755018d0f9c7568c@wordpress.org>

#55230: Release 5.9.1 breaks administration login.
------------------------------------+-----------------------------
 Reporter:  carlduranleau           |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  5.9.2
Component:  Login and Registration  |     Version:  5.9.1
 Severity:  blocker                 |  Resolution:
 Keywords:  needs-patch             |     Focuses:  administration
------------------------------------+-----------------------------

Comment (by kapilpaul):

 Could not reproduced it. Please share the reproduce steps as
 @SergeyBiryukov mentioned.

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

From noreply at wordpress.org  Sat Mar  5 08:30:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 08:30:14 -0000
Subject: [wp-trac] [WordPress Trac] #55322: The Class WP-Post List
 Table(Method - Column_Default) Contains Irrelevant Keyword 'return'
Message-ID: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>

#55322: The Class WP-Post List Table(Method - Column_Default) Contains Irrelevant
Keyword 'return'
----------------------------+--------------------------------------
 Reporter:  cu121           |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:  5.9.1
 Severity:  normal          |   Keywords:  dev-feedback needs-patch
  Focuses:  administration  |
----------------------------+--------------------------------------
 The Class WP-Post-List-Table has a method 'Column_Default' which contains
 a 'return' statement that prevents hooks from being fired like(hooks:-
 manage_pages_custom_column, manage_posts_custom_column,
 manage_{$post->post_type}_posts_custom_column). The return statement is on
 line number 1302, File-Name:- class-wp-posts-list-table.php.

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

From noreply at wordpress.org  Sat Mar  5 11:22:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 11:22:20 -0000
Subject: [wp-trac] [WordPress Trac] #55230: Release 5.9.1 breaks
 administration login.
In-Reply-To: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
References: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
Message-ID: <072.2ec750e7a064ef6e88990d4329430066@wordpress.org>

#55230: Release 5.9.1 breaks administration login.
-------------------------------------------+-----------------------------
 Reporter:  carlduranleau                  |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  new
 Priority:  normal                         |   Milestone:  5.9.2
Component:  Login and Registration         |     Version:  5.9.1
 Severity:  blocker                        |  Resolution:
 Keywords:  needs-patch reporter-feedback  |     Focuses:  administration
-------------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * keywords:  needs-patch => needs-patch reporter-feedback


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

From noreply at wordpress.org  Sat Mar  5 12:05:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 12:05:20 -0000
Subject: [wp-trac] [WordPress Trac] #55284: thumbnails issue
In-Reply-To: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
References: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
Message-ID: <078.ce905b92b0691eb0c6ae5ce497205cb3@wordpress.org>

#55284: thumbnails issue
---------------------------------+------------------------------
 Reporter:  simobenedettidesign  |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  Awaiting Review
Component:  Editor               |     Version:  5.9.1
 Severity:  major                |  Resolution:
 Keywords:  needs-testing        |     Focuses:
---------------------------------+------------------------------
Changes (by costdev):

 * keywords:   => needs-testing


Comment:

 Thanks very much for this additional information @simobenedettidesign!

 I was unable to reproduce the issue on 5.9.1 with a bundled theme and a
 gallery block.

 Does the issue occur for newly inserted Gallery blocks, or only those that
 existed prior to upgrading to 5.9?

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

From noreply at wordpress.org  Sat Mar  5 13:42:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 13:42:18 -0000
Subject: [wp-trac] [WordPress Trac] #55322: The Class WP-Post List
 Table(Method - Column_Default) Contains Irrelevant Keyword 'return'
In-Reply-To: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
References: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
Message-ID: <064.dead04a6b2bc9617c2baafd25fcf3fb5@wordpress.org>

#55322: The Class WP-Post List Table(Method - Column_Default) Contains Irrelevant
Keyword 'return'
--------------------------------------+------------------------------
 Reporter:  cu121                     |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Posts, Post Types         |     Version:  3.5
 Severity:  normal                    |  Resolution:
 Keywords:  dev-feedback needs-patch  |     Focuses:  administration
--------------------------------------+------------------------------
Changes (by SergeyBiryukov):

 * version:  5.9.1 => 3.5
 * component:  Administration => Posts, Post Types


Comment:

 Hi there, welcome back to WordPress Trac! Thanks for the report.

 For reference, the `return` statement was technically added in [32740] /
 #29881, but it replaced an earlier `break` statement added in [21788] /
 #21240, so WordPress 3.5 appears to be the earliest affected version here.

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

From noreply at wordpress.org  Sat Mar  5 15:33:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 15:33:20 -0000
Subject: [wp-trac] [WordPress Trac] #55100: `get_queried_object()`
 doesn't work for `author_name` before `WP_Query::get_posts()`
In-Reply-To: <048.4819f7a15a5e5209e8e95acef483b158@wordpress.org>
References: <048.4819f7a15a5e5209e8e95acef483b158@wordpress.org>
Message-ID: <063.8abe60fa48f13f428cefffa742f235dc@wordpress.org>

#55100: `get_queried_object()` doesn't work for `author_name` before
`WP_Query::get_posts()`
--------------------------------------+-----------------------------
 Reporter:  dd32                      |       Owner:  SergeyBiryukov
     Type:  defect (bug)              |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Query                     |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52822" 52822]:
 {{{
 #!CommitTicketReference repository="" revision="52822"
 Query: Make sure `WP_Query::get_queried_object()` works for `author_name`
 before `::get_posts()` is run.

 Previously, the queried object with author data was not available before
 the posts loop when `author_name` is used in the query instead of
 `author`. With block themes, this use case appears to be more common to
 display the author name in the header.

 This commit adjusts the logic in `WP_Query::get_queried_object()` to fall
 back to the `author_name` field if `author` is not present, similar to how
 taxonomy slugs are handled.

 Follow-up to [1728], [3290], [10992].

 Props dd32, swissspidy, SergeyBiryukov.
 Fixes #55100.
 }}}

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

From noreply at wordpress.org  Sat Mar  5 15:42:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 15:42:40 -0000
Subject: [wp-trac] [WordPress Trac] #55323: Ei buyog
Message-ID: <052.b815ac36bddb316160dcf84a6ddafff3@wordpress.org>

#55323: Ei buyog
-------------------------------------------------+-------------------------
 Reporter:  underwer                             |      Owner:  (none)
     Type:  defect (bug)                         |     Status:  new
 Priority:  normal                               |  Milestone:  Awaiting
                                                 |  Review
Component:  General                              |    Version:  trunk
 Severity:  normal                               |   Keywords:  reporter-
  Focuses:  ui, css, docs, multisite, coding-    |  feedback
  standards                                      |
-------------------------------------------------+-------------------------
 bug tracker//https://org.com

 issue
 <e>1
 <b>2
 <g>3

 imp: time running 01/05
 enpt error 02/03/04

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

From noreply at wordpress.org  Sat Mar  5 15:43:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 15:43:48 -0000
Subject: [wp-trac] [WordPress Trac] #55323: Ei buyog
In-Reply-To: <052.b815ac36bddb316160dcf84a6ddafff3@wordpress.org>
References: <052.b815ac36bddb316160dcf84a6ddafff3@wordpress.org>
Message-ID: <067.7de1c933a55d890b778604c4de4c3374@wordpress.org>

#55323: Ei buyog
-------------------------------------+-------------------------------------
 Reporter:  underwer                 |       Owner:  (none)
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  General                  |     Version:  trunk
 Severity:  normal                   |  Resolution:  duplicate
 Keywords:  reporter-feedback has-   |     Focuses:  ui, css, docs,
  patch                              |  multisite, coding-standards
-------------------------------------+-------------------------------------
Changes (by underwer):

 * keywords:  reporter-feedback => reporter-feedback has-patch
 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Duplicate of #1.

 Replying to [ticket:55323 underwer]:
 > bug tracker//https://org.com
 >
 > issue
 > <e>1
 > <b>2
 > <g>3
 >
 > imp: time running 01/05
 > enpt error 02/03/04

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

From noreply at wordpress.org  Sat Mar  5 16:46:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 16:46:43 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.849f9f95a49be316bdb6d013cc2259c1@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 No, FTP users have always been chrooted. Nothing changed there.

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

From noreply at wordpress.org  Sat Mar  5 19:27:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 19:27:51 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.d0fca930a2e59dceeb402ea74a3ca266@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------
Changes (by costdev):

 * version:  5.9 => trunk


Comment:

 Ok so we can be sure that it's not a 5.9 issue as the error occurs when
 upgrading from 5.7.5 to 5.8.

 Changing version to `trunk` for now while we determine if something needs
 to change in Core, your permissions, or if it's a Debian 11 issue.

 From [https://wordpress.org/support/article/changing-file-permissions/
 Changing File Permissions]:

 > If WordPress is running as the FTP account, that account needs to have
 write access, i.e., be the owner of the files, or belong to a group that
 has write access. In the latter case, that would mean permissions are set
 more permissively than default (for example, 775 rather than 755 for
 folders, and 664 instead of 644).

 Let's see if the issue still occurs if you use 775 for folders and 664 for
 files:

 {{{#!bash
 cd /path/to/wordpress
 find . -type d -exec chmod 775 {} \;
 find . -type f -exec chmod 664 {} \;
 }}}

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

From noreply at wordpress.org  Sat Mar  5 19:35:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 19:35:52 -0000
Subject: [wp-trac] [WordPress Trac] #27111: Turning off global comments
 should include existing content
In-Reply-To: <051.58cfc992f6ca783003cd41478fc733ed@wordpress.org>
References: <051.58cfc992f6ca783003cd41478fc733ed@wordpress.org>
Message-ID: <066.16b8cc9be97e7fc58e0e01b23a6e7694@wordpress.org>

#27111: Turning off global comments should include existing content
-------------------------+-----------------------------
 Reporter:  jenmylo      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Comments     |     Version:  3.9
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  administration
-------------------------+-----------------------------

Comment (by jb510):

 Two plugin solutions for disabling comments https://wordpress.org/plugins
 /disable-comments/ and https://wordpress.org/plugins/disable-comments-rb/
 have been taken over by new developers and quickly turned into a bloated
 mess.  Nobody needs a web app built into their dashboard just to "disable
 comments".

 Usually, these ancient tickets seem like a lost cause though.  Is there
 any hope for a patch for this actually making its way into core at this
 point?

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

From noreply at wordpress.org  Sat Mar  5 20:09:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 20:09:31 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.4f0c1984fc598390f3c65bbcd6ce96d8@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 Actually, I've done some testing and I now know exactly what is causing
 the problem.

 ftp_nlist() ''**always**'' returns false when the second parameter is a
 file instead of a directory on my system.

 {{{#!php
 <?php
 $ftp_server = "ftp.myserver.com";
 $ftp_user_name = "myusername";
 $ftp_user_pass = "mypassword";

 $ftp = ftp_connect($ftp_server);
 $login_result = ftp_login($ftp, $ftp_user_name, $ftp_user_pass);

 // check connection
 if ((!$ftp) || (!$login_result)) {
     echo "FTP connection has failed!\n";
     exit;
 } else {
     echo "Connected.\n";
 }
 ftp_pasv( $ftp, true );

 $list = ftp_nlist( $ftp, '/' );
 if( empty( $list ) ) {
   echo "File list is empty.\n";

 } else {
   foreach( $list as $file ) {
     echo "$file\n";
   }

   $list = ftp_nlist( $ftp, '/ftptest.php' );
   if( ! $list ) {
     echo "\nNot found.\n";
   } else {
     echo "\nFound!\n";
   }


 }

 // close the FTP connection
 ftp_close($ftp);
 >
 }}}

 On my server, the output is:


 {{{
 Connected.
 /.
 /..
 /htdocs
 /cgi-bin
 /logs
 /ftptest.php

 Not found.
 }}}

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

From noreply at wordpress.org  Sat Mar  5 20:29:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 20:29:26 -0000
Subject: [wp-trac] [WordPress Trac] #55322: The Class WP-Post List
 Table(Method - Column_Default) Contains Irrelevant Keyword 'return'
In-Reply-To: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
References: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
Message-ID: <064.3f6dbe5dfd5050fe5b634db9ee5c6d16@wordpress.org>

#55322: The Class WP-Post List Table(Method - Column_Default) Contains Irrelevant
Keyword 'return'
--------------------------------------+------------------------------
 Reporter:  cu121                     |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Posts, Post Types         |     Version:  3.5
 Severity:  normal                    |  Resolution:
 Keywords:  dev-feedback needs-patch  |     Focuses:  administration
--------------------------------------+------------------------------

Comment (by joyously):

 The return isn't irrelevant.
 That if statement handles only taxonomy columns, and it runs the
 appropriate filter.
 The actions further down are for custom columns, which the taxonomy column
 is not, so they should not be run in that case.

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

From noreply at wordpress.org  Sat Mar  5 20:36:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 20:36:57 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.31e6d5e9171ae052343e74ee6f421aac@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by costdev):

 In
 `WP_Filesystem_FTPext::exists()`[https://developer.wordpress.org/reference/classes/wp_filesystem_ftpext/exists/
 Docs], it calls `$list = ftp_nlist( $this->link, $file )`, which returns
 `false`.

 The result is checked against `empty( $list ) && $this->is_dir( $file )`,
 which passes the first condition and fails the second.

 Then the `WP_Filesystem_FTPext::exists()` returns `! empty( $list );`.

 `! false` === `true` === the file exists, so this shouldn't be causing the
 problem here.

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

From noreply at wordpress.org  Sat Mar  5 20:46:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 20:46:16 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.c7e32465404d4c16b6e97436675b2af4@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by costdev):

 Does adding this before the call to `ftp_pasv()` change the result for
 you?

 {{{
 ftp_set_option( $ftp, FTP_USEPASVADDRESS, false );
 }}}

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

From noreply at wordpress.org  Sat Mar  5 21:07:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 21:07:09 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.8590da92f6d6e4bbc59dd82b89d73ee7@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 Replying to [comment:12 costdev]:
 > Does adding this before the call to `ftp_pasv()` change the result for
 you?
 >
 > {{{
 > ftp_set_option( $ftp, FTP_USEPASVADDRESS, false );
 > }}}

 No, ftp_nlist() (in **class-wp-filesystem-ftpext.php**) still returns
 false on a file.

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

From noreply at wordpress.org  Sat Mar  5 22:27:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 05 Mar 2022 22:27:11 -0000
Subject: [wp-trac] [WordPress Trac] #55284: thumbnails issue
In-Reply-To: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
References: <063.e399559b1f6ad4fa66f589f48f6f9bd1@wordpress.org>
Message-ID: <078.25a790988b39b7a00a545b906425ac3f@wordpress.org>

#55284: thumbnails issue
---------------------------------+------------------------------
 Reporter:  simobenedettidesign  |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  Awaiting Review
Component:  Editor               |     Version:  5.9.1
 Severity:  major                |  Resolution:
 Keywords:  needs-testing        |     Focuses:
---------------------------------+------------------------------

Comment (by simobenedettidesign):

 Replying to [comment:5 costdev]:
 > Thanks very much for this additional information @simobenedettidesign!
 >
 > I was unable to reproduce the issue on 5.9.1 with a bundled theme and a
 gallery block.
 >
 > Does the issue occur for newly inserted Gallery blocks, or only those
 that existed prior to upgrading to 5.9?


 It does not occur in old entries that have already been published prior to
 5.9.1 upgrading.
 However, it occurs in old posts if I open them in the WP editor and click
 on 'post preview'.
 As for the new entries, it occurs in new posts both in preview mode and
 after their publication.

 That's weird but hope this helps!

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

From noreply at wordpress.org  Sun Mar  6 01:31:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 01:31:01 -0000
Subject: [wp-trac] [WordPress Trac] #55323: When an image is edited the URL
 of the image is not updated
Message-ID: <050.79ed9f05007caabff54b42e46b07c848@wordpress.org>

#55323: When an image is edited the URL of the image is not updated
--------------------------------+-----------------------------
 Reporter:  mitogh              |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  Media               |    Version:  5.9.1
 Severity:  normal              |   Keywords:
  Focuses:  ui, administration  |
--------------------------------+-----------------------------
 When an image is edited from the image editor, after an edit has been
 applied, the URL of the image is not updated due it always references back
 to the original image instead of referencing the image to the updated
 image (when the edit has been applied to all images sizes).


 == Steps to replicate the problem.

 1. Upload an image into the media library
 2. After the image is uploaded into the media library click on Edit image
 3. Apply an edit to the image, either rotate, flip or crop,
 4. Make sure that the option is applied to all images sizes.
 5. Click on Save
 6. Observe how the URL of the image (see attached image), by clicking on
 Copy URL to the clipboard
 7. Open the copied URL into a new tab the copied URL still references to
 the original image, and not the edited image instead.

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

From noreply at wordpress.org  Sun Mar  6 01:31:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 01:31:13 -0000
Subject: [wp-trac] [WordPress Trac] #55323: When an image is edited the
 URL of the image is not updated
In-Reply-To: <050.79ed9f05007caabff54b42e46b07c848@wordpress.org>
References: <050.79ed9f05007caabff54b42e46b07c848@wordpress.org>
Message-ID: <065.df0d0d64a6f42c3af5ffe8e28e4d484a@wordpress.org>

#55323: When an image is edited the URL of the image is not updated
--------------------------+---------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  ui, administration
--------------------------+---------------------------------
Changes (by mitogh):

 * Attachment "2022-03-05_19-24.png" added.


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

From noreply at wordpress.org  Sun Mar  6 03:09:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 03:09:16 -0000
Subject: [wp-trac] [WordPress Trac] #55322: The Class WP-Post List
 Table(Method - Column_Default) Contains Irrelevant Keyword 'return'
In-Reply-To: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
References: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
Message-ID: <064.bf36d2133dd9101e50dc6a4d209f3639@wordpress.org>

#55322: The Class WP-Post List Table(Method - Column_Default) Contains Irrelevant
Keyword 'return'
--------------------------------------+------------------------------
 Reporter:  cu121                     |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Posts, Post Types         |     Version:  3.5
 Severity:  normal                    |  Resolution:
 Keywords:  dev-feedback needs-patch  |     Focuses:  administration
--------------------------------------+------------------------------

Comment (by cu121):

 I see I was checking for taxonomy basically. I guess this ticket can be
 closed.
 Thank You For The Explaination

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

From noreply at wordpress.org  Sun Mar  6 03:49:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 03:49:15 -0000
Subject: [wp-trac] [WordPress Trac] #55322: The Class WP-Post List
 Table(Method - Column_Default) Contains Irrelevant Keyword 'return'
In-Reply-To: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
References: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
Message-ID: <064.27b82bfe8fd94134b19cb1039f336cb8@wordpress.org>

#55322: The Class WP-Post List Table(Method - Column_Default) Contains Irrelevant
Keyword 'return'
-------------------------------+-----------------------------
 Reporter:  cu121              |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Posts, Post Types  |     Version:  3.5
 Severity:  normal             |  Resolution:  invalid
 Keywords:                     |     Focuses:  administration
-------------------------------+-----------------------------
Changes (by costdev):

 * keywords:  dev-feedback needs-patch =>
 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Thanks for opening this ticket @cu121!

 As @joyously explained:

 - When the column is `categories`, `post_tags`, or starts with
 `taxonomy-`:
   - Handle the taxonomy and return.
 - Otherwise:
   - Run an appropriate action hook depending on whether the post type is
 hierarchical (yes = Pages hook, no = Posts hook).
   - Finally, run the action hook for the specific post type.

 I'll close this ticket as `invalid`, as the method returns at an
 appropriate time.

 Thanks to all for their insight on this.

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

From noreply at wordpress.org  Sun Mar  6 03:51:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 03:51:27 -0000
Subject: [wp-trac] [WordPress Trac] #55322: The Class WP-Post List
 Table(Method - Column_Default) Contains Irrelevant Keyword 'return'
In-Reply-To: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
References: <049.d17a527bafb33c93e80ff7088b5d9c4f@wordpress.org>
Message-ID: <064.13e340b1e0c0e101ec3b4dbdd50e9187@wordpress.org>

#55322: The Class WP-Post List Table(Method - Column_Default) Contains Irrelevant
Keyword 'return'
-------------------------------+-----------------------------
 Reporter:  cu121              |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Posts, Post Types  |     Version:  3.5
 Severity:  normal             |  Resolution:  invalid
 Keywords:                     |     Focuses:  administration
-------------------------------+-----------------------------

Comment (by cu121):

 @costdev thank you so much for the explanation :)

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

From noreply at wordpress.org  Sun Mar  6 08:56:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 08:56:27 -0000
Subject: [wp-trac] [WordPress Trac] #55324: Twenty Twenty: Scroll to top not
 working
Message-ID: <053.fa149de27f743cf9d574f331ee5a4827@wordpress.org>

#55324: Twenty Twenty: Scroll to top not working
---------------------------+-----------------------------
 Reporter:  Presskopp      |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Bundled Theme  |    Version:
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 For whatever reason, in my installation the scroll to top arrow doesn't
 work. I changed

 {{{#!php
 <a class="to-the-top" href="#site-header">
 }}}

 to

 {{{#!php
 <a class="to-the-top" href="#">
 }}}

 and it was working again. Maybe worth patching?

 Another alternative would be

 {{{#!php
 <a class="to-the-top" href="#top">
 }}}

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

From noreply at wordpress.org  Sun Mar  6 11:01:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 11:01:45 -0000
Subject: [wp-trac] [WordPress Trac] #10886: WordPress should not
 unnecessarily query posts at page load
In-Reply-To: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
References: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
Message-ID: <068.b98c9be4365e9c7a1a27899bbc3867aa@wordpress.org>

#10886: WordPress should not unnecessarily query posts at page load
-------------------------------------------------+-------------------------
 Reporter:  junsuijin                            |       Owner:
                                                 |  spacedmonkey
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Bootstrap/Load                       |     Version:  2.8.4
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-unit-tests early has-patch       |     Focuses:
  needs-dev-note                                 |  performance
-------------------------------------------------+-------------------------

Comment (by lkraav):

 Was there also some commit in core that demonstrates using `$parsed`? For
 example, to optimize the infamous
 [https://twitter.com/kovshenin/status/1466732748517822464?ref_src=twsrc%5Etfw
 robots.txt loading process], or something else?

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

From noreply at wordpress.org  Sun Mar  6 12:04:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 12:04:34 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.465b32a06366b25dec49d0e5506ff667@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 Ok, it turns out to be a "problem" with the new version of Pure-FTPd that
 was installed with Debian 11. It installs v1.0.49 (previously installed
 version was v1.0.47) and according to their changelog
 [https://www.pureftpd.org/project/pure-ftpd/news/#version-1048-released
 here], globbing was removed from the NLST command in v1.0.48 (which makes
 sense since it's actually not allowed according to the RFC).

 So it's weird that this problem hasn't been reported numerous times before
 since everybody who uses the FTP method to update and also uses Pure-
 FTPd,will have this problem...

 The only solution is a rewrite of the code in class-wp-filesystem-
 ftpext.php, or switching to the direct method of updating. Which sucks
 because that opens a whole can of worms of secutiry issues.

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

From noreply at wordpress.org  Sun Mar  6 12:46:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 12:46:03 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.a990a18f0ef806a75f95e396463c9b40@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by ocean90):

 Replying to [comment:14 zippy1970]:
 > So it's weird that this problem hasn't been reported numerous times
 before since everybody who uses the FTP method to update and also uses
 Pure-FTPd, will have this problem...

 Sounds like we already have report for it in #51170. Can you confirm?

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

From noreply at wordpress.org  Sun Mar  6 12:47:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 12:47:26 -0000
Subject: [wp-trac] [WordPress Trac] #47280: SQL_CALC_FOUND_ROWS is
 deprecated as of MySQL 8.0.17
In-Reply-To: <053.464f3453501834c73527d32600b297e3@wordpress.org>
References: <053.464f3453501834c73527d32600b297e3@wordpress.org>
Message-ID: <068.cb8c54c8af2cf89c7e06df8e95f31712@wordpress.org>

#47280: SQL_CALC_FOUND_ROWS is deprecated as of MySQL 8.0.17
--------------------------------------+-----------------------------
 Reporter:  javorszky                 |       Owner:  johnbillion
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  Future Release
Component:  Database                  |     Version:
 Severity:  major                     |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+-----------------------------

Comment (by misterwebdeveloper):

 Hi,

 Experienced software developer of 20 years here. I just want to start by
 saying MySQL is a crazy good open source platform and kudos to everyone
 involved building it.

 Sorry if I'm posting this in the wrong place...

 Let me play devil's advocate.

 As far as I can see the recommendation is to break DRY and duplicate
 SELECT statements.
 Presumably this feature was orignally added to prevent that.

 The MYSQL recommendation: duplicate the original query. So a SQL statement
 using SQL_CALC_FOUND_ROWS is 150 lines, most of those lines should be
 duplicated? This isn't a pragmatic solution. What if an existing system is
 using 50k lines? Is there something I'm missing here?

 Another suggestion is to rewrite systems to use lazy loading. Not all
 systems are lazily loaded social media platforms. Pagination still has
 it's place and isn't going anywhere long term.

 Is it possible to fix/improve the performance issues in this feature? How
 about MySQL re-runs the proc in the background without the LIMIT code when
 it encounters SQL_CALC_FOUND_ROWS? That way there the dev doesn't need to
 duplicate the code.

 My regards

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

From noreply at wordpress.org  Sun Mar  6 13:06:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 13:06:43 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.5cdeeb6453108b1f0b41ebf6eb7356bf@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 In **class-wp-filesystem-ftpext.php** I replaced the ''exists()'' function
 with my own version (below) and the update succeeded without a hitch.

 {{{#!php
 <?php
         public function exists( $file ) {
           $retval = false;

           $list = ftp_nlist( $this->link, $file );
           if( ! empty( $list ) ) {
             // if ftp_nlist returns *something*, the file or directory
 exists, on any FTP server
             $retval = true;
           } else {
             // if ftp_nlist returns nothing, either the file/dir doesn't
 exist or it's a file and
             // the FTP server's NLST command doesn't support globbing
 (i.e. Pure-FTPD > v1.0.47)
             // Check if it'a file
             if( ftp_size( $this->link, $file ) >= 0 ) {
               $retval = true;
             }
           }
           return $retval;

         }

 }}}

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

From noreply at wordpress.org  Sun Mar  6 13:27:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 13:27:29 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.dc3ec6592cab5f0db2a4bb89c9967b9e@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------------

Comment (by zippy1970):

 Replying to [comment:15 ocean90]:
 > Sounds like we already have report for it in #51170. Can you confirm?

 Yes, that's it. If they would have made a comment that this causes updates
 to fail, that would have saved me a lot of trouble. :)

 Apparently they changed the exists() function in the exact same way I did.

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

From noreply at wordpress.org  Sun Mar  6 14:41:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 14:41:24 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.601e2cdd95f0765ddd96c78a59861b78@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:  duplicate
 Keywords:  needs-testing    |     Focuses:
-----------------------------+------------------------
Changes (by SergeyBiryukov):

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


Comment:

 Thanks for the confirmation! Let's continue in #51170 then, as it already
 has a patch.

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

From noreply at wordpress.org  Sun Mar  6 14:42:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 14:42:01 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.f80bcec89ce4624cb5f67b8708ef6e67@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
-------------------------------------------------+-------------------------
 Reporter:  giox069                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Filesystem API                       |     Version:  3.7
 Severity:  normal                               |  Resolution:
 Keywords:  reporter-feedback dev-feedback has-  |     Focuses:
  patch                                          |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Sun Mar  6 14:48:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 14:48:36 -0000
Subject: [wp-trac] [WordPress Trac] #55307: After upgrading Debian,
 WordPress sites no longer update through FTP
In-Reply-To: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
References: <053.758b8f5288fccbf09c38e68a6aafd535@wordpress.org>
Message-ID: <068.8e43d6b43484284dd2094c66e002026d@wordpress.org>

#55307: After upgrading Debian, WordPress sites no longer update through FTP
-----------------------------+------------------------
 Reporter:  zippy1970        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  major            |  Resolution:  duplicate
 Keywords:                   |     Focuses:
-----------------------------+------------------------
Changes (by costdev):

 * keywords:  needs-testing =>


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

From noreply at wordpress.org  Sun Mar  6 15:13:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 15:13:39 -0000
Subject: [wp-trac] [WordPress Trac] #55325: Theme Editor: Add file
 description for theme.json
Message-ID: <051.9b415a9f143e2ed1e9bda377b1fab3ad@wordpress.org>

#55325: Theme Editor: Add file description for theme.json
----------------------------+----------------------------------------
 Reporter:  ocean90         |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Future Release
Component:  Themes          |    Version:
 Severity:  normal          |   Keywords:  needs-patch good-first-bug
  Focuses:  administration  |
----------------------------+----------------------------------------
 It would be nice to show a description for `theme.json` in the theme
 editor instead of only `theme.json`.

 The current list of file descriptions:
 https://core.trac.wordpress.org/browser/tags/5.9.1/src/wp-
 admin/includes/file.php?marks=14-65#L14

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

From noreply at wordpress.org  Sun Mar  6 15:14:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 15:14:38 -0000
Subject: [wp-trac] [WordPress Trac] #55325: Theme Editor: Add file
 description for theme.json
In-Reply-To: <051.9b415a9f143e2ed1e9bda377b1fab3ad@wordpress.org>
References: <051.9b415a9f143e2ed1e9bda377b1fab3ad@wordpress.org>
Message-ID: <066.fc5bc4afae1bd851ff49f15a917fa07d@wordpress.org>

#55325: Theme Editor: Add file description for theme.json
----------------------------------------+-----------------------------
 Reporter:  ocean90                     |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  Future Release
Component:  Themes                      |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:  administration
----------------------------------------+-----------------------------
Changes (by ocean90):

 * Attachment "55325.png" added.

 File tree of Twenty Twenty-Two

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

From noreply at wordpress.org  Sun Mar  6 16:08:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 16:08:05 -0000
Subject: [wp-trac] [WordPress Trac] #54164: Consistently fire user role
 hooks
In-Reply-To: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
References: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
Message-ID: <063.bab5f04fae8580621208190b89b9b033@wordpress.org>

#54164: Consistently fire user role hooks
-------------------------+---------------------
 Reporter:  dd32         |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:  4.3
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Sun Mar  6 16:09:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 16:09:21 -0000
Subject: [wp-trac] [WordPress Trac] #54164: Consistently fire user role
 hooks
In-Reply-To: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
References: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
Message-ID: <063.5b3f68d298ef558664a0b495bd902883@wordpress.org>

#54164: Consistently fire user role hooks
-------------------------+-----------------------------
 Reporter:  dd32         |       Owner:  SergeyBiryukov
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:  4.3
 Severity:  normal       |  Resolution:  fixed
 Keywords:  has-patch    |     Focuses:
-------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52823" 52823]:
 {{{
 #!CommitTicketReference repository="" revision="52823"
 Users: Bring some consistency to user role hooks.

 This standardizes the actions that one needs to hook to for tracking user
 role changes:

 * `add_user_role` is only fired when the user has actually gained a new
 role.
 * `remove_user_role` is only fired when the role was actually removed.

 Both actions are now fired in `WP_User::set_role()` as appropriate.

 Props dd32, SergeyBiryukov.
 Fixes #54164.
 }}}

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

From noreply at wordpress.org  Sun Mar  6 16:37:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 16:37:00 -0000
Subject: [wp-trac] [WordPress Trac] #51857: Add rollback for failed
 plugin/theme updates
In-Reply-To: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
References: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
Message-ID: <065.249079fd3411b1b17575fabfcd8e20dd@wordpress.org>

#51857: Add rollback for failed plugin/theme updates
-------------------------------------------------+-------------------------
 Reporter:  pbiron                               |       Owner:  pbiron
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  early has-testing-info needs-unit-   |     Focuses:
  tests needs-testing has-patch                  |
-------------------------------------------------+-------------------------
Changes (by pbiron):

 * Attachment "pr-2225.diff" added.


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

From noreply at wordpress.org  Sun Mar  6 16:41:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 16:41:29 -0000
Subject: [wp-trac] [WordPress Trac] #51857: Add rollback for failed
 plugin/theme updates
In-Reply-To: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
References: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
Message-ID: <065.bb5ce9185082212e36e4c2a794024d0a@wordpress.org>

#51857: Add rollback for failed plugin/theme updates
-------------------------------------------------+-------------------------
 Reporter:  pbiron                               |       Owner:  pbiron
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  early has-testing-info needs-unit-   |     Focuses:
  tests needs-testing has-patch                  |
-------------------------------------------------+-------------------------

Comment (by pbiron):

 For some reason, I'm not able to push changes to the
 [https://github.com/WordPress/wordpress-
 develop/pull/2225#issuecomment-1027369433 latest PR] (get a "permission
 denied" error).  So, I'm uploading them here as patch.

 Could @afragen or @SergeyBiryukov please update the PR accordingly.

 The patch doesn't change the rollback functionality, it just fixes some
 things with the changes to `site health` in the PR:

 1. fixes minor HTML errors in 2 of the new site health tests
 2. adds `WP_RUNTIME_ENVIRONMENT` to the `WordPress Constants` section of
 the site health `debug data` screen

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

From noreply at wordpress.org  Sun Mar  6 17:10:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 17:10:05 -0000
Subject: [wp-trac] [WordPress Trac] #55276: :where is easily being
 overridden
In-Reply-To: <056.93699acdb4e9548e4b4c0571a260c817@wordpress.org>
References: <056.93699acdb4e9548e4b4c0571a260c817@wordpress.org>
Message-ID: <071.3420298efda4437be32699d4a9be837b@wordpress.org>

#55276: :where is easily being overridden
--------------------------+------------------------------
 Reporter:  vijayhardaha  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.1
 Severity:  normal        |  Resolution:  worksforme
 Keywords:                |     Focuses:  css
--------------------------+------------------------------
Changes (by vijayhardaha):

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


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

From noreply at wordpress.org  Sun Mar  6 18:01:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 18:01:43 -0000
Subject: [wp-trac] [WordPress Trac] #55326: Conditional classes directives
 in formatting
Message-ID: <056.5d933fd28bb30679974960b53abccade@wordpress.org>

#55326: Conditional classes directives in formatting
------------------------------+-----------------------------
 Reporter:  vijayhardaha      |      Owner:  (none)
     Type:  feature request   |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  Formatting        |    Version:  5.9.1
 Severity:  normal            |   Keywords:
  Focuses:  coding-standards  |
------------------------------+-----------------------------
 Hey people,

 I am here with a suggestion and core feature request for conditional
 classes directive for HTML class attribute. Similar to [Laraval
 conditional-classes](https://laravel.com/docs/9.x/blade#conditional-
 classes)

 If this function is already available in WP then please let me know about
 it, I wasn't able to find a similar function.

 There are many cases in development where we're creating a `$clasess`
 array variable and then with if-else or using conditional statements
 adding classes into it.

 While working with PHP code the code/file format in files look good and
 it's easy to manage but sometimes with HTML and PHP combination writing
 inline if-else make the code/file format ugly. and we also have to repeat
 the escape and echo things again n again if we have a couple of
 conditional CSS to write.

 I have created this custom code to use in my custom development, which
 allows passing set or array or single sting or strings with comma/space
 and then it conditional validate and output the string.

 {{{#!php
 <?php
 /**
  * Returns/echo Conditional HTML Classes.
  *
  * @param array|string $classes    Array of classes, single string or
 strings with comma.
  * @param bool         $echo       If true then echo the output otherwise
 return it.
  * @return string                  HTML classes string.
  */
 function html_class( $classes = array(), $echo = true ) {
         // Define default output.
         $output = '';

         // Make a type and empty check validation.
         if ( ( is_array( $classes ) || is_string( $classes ) ) && ! empty(
 $classes ) ) {
                 /**
                  * If string then parse it comman and space.
                  * otherwise keep the array.
                  */
                 $classes = is_string( $classes ) ? wp_parse_list( $classes
 ) : (array) $classes;

                 // Do an empty check.
                 if ( ! empty( $classes ) ) {
                         // Storing var for valid classess.
                         $class_set = array();

                         // Loop through all classes.
                         foreach ( $classes as $key => $class_name ) {
                                 // Check if array has integer key, which
 means no conditions
                                 // are set for this class, if class is not
 empty then keep it.
                                 if ( is_int( $key ) && is_string(
 $class_name ) && ! empty( $class_name ) ) {
                                         $class_set[] = trim( $class_name
 );
                                 } elseif ( ! empty( $class_name ) && !
 empty( $key ) ) {
                                         $class_set[] = trim( $key );
                                 }
                         }

                         /**
                          * Filter array with empty values.
                          * Make array unique.
                          * Sanitize class name.
                          * Implode by space.
                          */
                         $output = implode( ' ', array_map(
 'sanitize_html_class', array_unique( array_filter( $class_set ) ) ) );
                 }
         }

         if ( $echo ) {
                 echo esc_attr( $output );
         } else {
                 return esc_attr( $output );
         }
 }
 }}}

 so using this function we could save time to not write a few lines of if-
 else and keep the code look clean and simple as well, e.g.
 {{{#!php
 <?php
 $classes   = array();
 $classes[] = array( 'post-title' );
 if ( has_post_thumbnail() ) {
         $classes[] = 'has-thumbnail';
 }
 if ( has_term( 'featured', 'category' ) ) {
         $classes[] = 'is-featured';
 }

 echo '<div class="' . esc_attr( join( ' ', $classes ) ) . '">';
 }}}


 this will convert into this.
 {{{#!php
 <?php
 $classes = array(
         array(
                 'post-title',
                 'has-thumbnail' => has_post_thumbnail(),
                 'is-featured'   => has_term( 'featured', 'category' ),
         ),
 );

 echo '<div class="' . html_class( $classes, false ).'">; // false is for
 returning the values.
 }}}

 however, it does not save too many lines but we are repeating things less
 and I feel it looks clean in code reading. :)

 But this function can be very useful while writing mixed HTML and php.
 {{{#!php
 <?php
 <div class="col-12
 <?php
 if ( is_sidebar_active( 'right-sidebar' ) && is_sidebar_active( 'righleft-
 sidebar' ) ) {
         echo 'col-md-6';
 } elseif ( ! is_sidebar_active( 'right-sidebar' ) && is_sidebar_active(
 'left-sidebar' ) ) {
         echo 'col-md-8';
 } elseif ( is_sidebar_active( 'right-sidebar' ) && ! is_sidebar_active(
 'left-sidebar' ) ) {
         echo 'col-md-8 md-offset-4';
 } else {
         echo 'col-md-8 md-offset-2';
 }
 ?>
 "></div>
 }}}


 {{{#!php
 <?php
 $clasess = array(
         'col-12',
         'col-md-6'             => is_sidebar_active( 'right-sidebar' ) &&
 is_sidebar_active( 'righleft-sidebar' ),
         'col-md-8'             => ! is_sidebar_active( 'right-sidebar' )
 && is_sidebar_active( 'righleft-sidebar' ),
         'col-md-8 md-offset-4' => is_sidebar_active( 'right-sidebar' ) &&
 ! is_sidebar_active( 'righleft-sidebar' ),
         'col-md-8 md-offset-2' => ! ( is_sidebar_active( 'right-sidebar' )
 && is_sidebar_active( 'righleft-sidebar' ) ),
 );
 ?>
 <div class="<?php html_class( $clasess ); ?>"></div>
 }}}


 Please let me know what you people think about having a directive function
 for classes.

 Thanks,

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

From noreply at wordpress.org  Sun Mar  6 18:09:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 18:09:40 -0000
Subject: [wp-trac] [WordPress Trac] #55230: Release 5.9.1 breaks
 administration login.
In-Reply-To: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
References: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
Message-ID: <072.ec284cb78c4350f637c87c74eb920d92@wordpress.org>

#55230: Release 5.9.1 breaks administration login.
-------------------------------------------+-----------------------------
 Reporter:  carlduranleau                  |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  new
 Priority:  normal                         |   Milestone:  5.9.2
Component:  Login and Registration         |     Version:  5.9.1
 Severity:  blocker                        |  Resolution:
 Keywords:  needs-patch reporter-feedback  |     Focuses:  administration
-------------------------------------------+-----------------------------

Comment (by carlduranleau):

 To reproduce this error, I only had to access the admin login page: /wp-
 login.php. With the DEBUG flag set, I had many warnings showing at he top
 of the login page. All warnings were the same: "Cannot modify header
 information – headers already sent by...". Even if I was able to enter my
 username and password, the login button was always returning me back to
 the same page.

 Maybe I should have added my configuration in the ticket. Our website is
 using Corpera 1.0.2 theme with these plugins:

 - Elementor 3.1.1
 - LiteSpeed Cache 4.4.1
 - WP Google Maps 8.1.11
 - Wpazure Kit 1.1.2
 - WPForms Lite 1.6.7

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

From noreply at wordpress.org  Sun Mar  6 19:37:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 19:37:25 -0000
Subject: [wp-trac] [WordPress Trac] #54164: Consistently fire user role
 hooks
In-Reply-To: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
References: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
Message-ID: <063.6d39523376cf97f3ddd30565e7a39825@wordpress.org>

#54164: Consistently fire user role hooks
-------------------------+-----------------------------
 Reporter:  dd32         |       Owner:  SergeyBiryukov
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:  4.3
 Severity:  normal       |  Resolution:  fixed
 Keywords:  has-patch    |     Focuses:
-------------------------+-----------------------------

Comment (by azouamauriac):

 Replying to [comment:2 SergeyBiryukov]:
 > In [changeset:"52823" 52823]

 Hi can we merge these two if controle [https://prnt.sc/VLGhGiND77NH] ?

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

From noreply at wordpress.org  Sun Mar  6 19:47:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 19:47:06 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.c0733c4ce7538e3b54bc2f532cee6528@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  docs
----------------------------+---------------------
Changes (by azouamauriac):

 * Attachment "54729.diff" added.

 in src/wp-includes/class-wp-user.php use third person in function docblock

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

From noreply at wordpress.org  Sun Mar  6 22:35:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 22:35:52 -0000
Subject: [wp-trac] [WordPress Trac] #54164: Consistently fire user role
 hooks
In-Reply-To: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
References: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
Message-ID: <063.cb85ed367cec8b340ccf3ed4bd3fd64c@wordpress.org>

#54164: Consistently fire user role hooks
-------------------------+-----------------------------
 Reporter:  dd32         |       Owner:  SergeyBiryukov
     Type:  enhancement  |      Status:  reopened
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:  4.3
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+-----------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch => needs-patch
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening as the Multisite [https://github.com/WordPress/wordpress-
 develop/actions?query=branch%3Atrunk tests started failing] following this
 commit.

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

From noreply at wordpress.org  Sun Mar  6 23:02:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 23:02:26 -0000
Subject: [wp-trac] [WordPress Trac] #54164: Consistently fire user role
 hooks
In-Reply-To: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
References: <048.73bcce5eb7d3a2a2a40d4e1f3a611ec4@wordpress.org>
Message-ID: <063.3a9b028e9342aaa416f15465e775d9c4@wordpress.org>

#54164: Consistently fire user role hooks
-------------------------+-----------------------------
 Reporter:  dd32         |       Owner:  SergeyBiryukov
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:  4.3
 Severity:  normal       |  Resolution:  fixed
 Keywords:  needs-patch  |     Focuses:
-------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52824" 52824]:
 {{{
 #!CommitTicketReference repository="" revision="52824"
 Tests: Restore the original user role in the `(add|remove)_user_role`
 hooks test.

 This makes sure the test does not unintentionally affect other tests.

 Follow-up to [52823].

 Fixes #54164.
 }}}

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

From noreply at wordpress.org  Sun Mar  6 23:18:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 06 Mar 2022 23:18:12 -0000
Subject: [wp-trac] [WordPress Trac] #27111: Turning off global comments
 should include existing content
In-Reply-To: <051.58cfc992f6ca783003cd41478fc733ed@wordpress.org>
References: <051.58cfc992f6ca783003cd41478fc733ed@wordpress.org>
Message-ID: <066.b28700e641906d96a6939473e441379e@wordpress.org>

#27111: Turning off global comments should include existing content
-------------------------+-----------------------------
 Reporter:  jenmylo      |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Comments     |     Version:  3.9
 Severity:  normal       |  Resolution:  wontfix
 Keywords:  has-patch    |     Focuses:  administration
-------------------------+-----------------------------
Changes (by peterwilsoncc):

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


Comment:

 Replying to [comment:31 jb510]:
 > [snip]
 > Usually, these ancient tickets seem like a lost cause though.  Is there
 any hope for a patch for this actually making its way into core at this
 point?

 Honestly, I think it unlikely.

 My view is that the option is fairly clear that the setting is the default
 for new posts.

 Changing how the option works to apply to all posts would break backward
 compatibility and become problematic for sites deliberately choosing to
 enable comments on some posts. My specific thought is news-type sites
 which enable comments on analysis articles but not general news articles.

 Adding an additional "all posts" option seems unhelpful for a couple of
 lines of code. I'll see if I can get [https://github.com/peterwilsoncc
 /rapid-disable-comments this in the repo] to leave neglected and forget to
 update the supported version for. ;)

 I'm going to close this as ''wontfix'' to match the reality given there
 has been no movement for seven years.

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

From noreply at wordpress.org  Mon Mar  7 00:15:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 00:15:01 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.be54953863f8fc22c5afbcaec0be6cbc@wordpress.org>

#36949: Term exists should use get_terms internally
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  2.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note needs-testing                             |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests needs-dev-note => has-patch has-unit-
     tests needs-dev-note needs-testing


Comment:

 Replying to [comment:29 spacedmonkey]:
 > Thanks @peterwilsoncc . It is was a good spot. I have refactor the patch
 to remove usage of `get_term` and now everything uses `get_terms`. Unit
 tests are passing now

 Thanks, both for the updated code and taking my push of a broken test to
 your branch in the spirit intended.

 The code looks good to me, I've added the needs-testing keyword on this in
 the hope some of the testing folk can take a look at your branch before
 committing.

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

From noreply at wordpress.org  Mon Mar  7 00:51:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 00:51:26 -0000
Subject: [wp-trac] [WordPress Trac] #27111: Turning off global comments
 should include existing content
In-Reply-To: <051.58cfc992f6ca783003cd41478fc733ed@wordpress.org>
References: <051.58cfc992f6ca783003cd41478fc733ed@wordpress.org>
Message-ID: <066.a31b98ae6ec408a61695f41c6d5bff32@wordpress.org>

#27111: Turning off global comments should include existing content
-------------------------+-----------------------------
 Reporter:  jenmylo      |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Comments     |     Version:  3.9
 Severity:  normal       |  Resolution:  wontfix
 Keywords:  has-patch    |     Focuses:  administration
-------------------------+-----------------------------

Comment (by jb510):

 @peterwilsoncc this was marked a duplicate of
 https://core.trac.wordpress.org/ticket/32375 and
 https://core.trac.wordpress.org/ticket/53185 which is why I commented
 here. Although those tickets are a bit more clear about what I think is
 generally needed: A check box to disable all comment functionality
 sitewide.

 The point here is there ought to be a core method to completely disable
 comments on a site (brand new site or otherwise) and not rely on the
 increasingly spammy plugins to do so.  The other tickets were a bit more
 clear about this need than this ticket.

 I think we all understand a huge number of sites these days have zero need
 for comments at all. This means no need to accept comment spam requests to
 the API, no need to count comments, no need really to load even 1 line of
 comment-related code or make queries looking for comments.

 On many sites, comments are more of an attractive nuisance than something
 anyone wants to manage. Or they're disabling WP comments in favor of sass
 solutions like Disqus.

 Comments were unquestionably a unique and huge benefit in the early blog-
 focused days of WordPress.  They're not obsolete on all sites (like links
 became), just obsolete on a lot of sites.

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

From noreply at wordpress.org  Mon Mar  7 01:44:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 01:44:22 -0000
Subject: [wp-trac] [WordPress Trac] #55326: Conditional classes
 directives in formatting
In-Reply-To: <056.5d933fd28bb30679974960b53abccade@wordpress.org>
References: <056.5d933fd28bb30679974960b53abccade@wordpress.org>
Message-ID: <071.3ed9b3317934fc5461280bd6233cb59f@wordpress.org>

#55326: Conditional classes directives in formatting
-----------------------------+-------------------------------
 Reporter:  vijayhardaha     |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Formatting       |     Version:  5.9.1
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  coding-standards
-----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 Hi there, welcome back to WordPress Trac! Thanks for the ticket.

 Just linking to a related ticket here: #50867.

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

From noreply at wordpress.org  Mon Mar  7 01:45:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 01:45:17 -0000
Subject: [wp-trac] [WordPress Trac] #50867: An API which encourages
 automatic escaping of HTML
In-Reply-To: <054.c2c4be12d3b282e664a3ec46964ce574@wordpress.org>
References: <054.c2c4be12d3b282e664a3ec46964ce574@wordpress.org>
Message-ID: <069.4c1535bd23d7e0469e93cf0f09746fda@wordpress.org>

#50867: An API which encourages automatic escaping of HTML
-------------------------------------------------+-------------------------
 Reporter:  noisysocks                           |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests needs-    |     Focuses:
  docs dev-feedback 2nd-opinion                  |
-------------------------------------------------+-------------------------

Comment (by SergeyBiryukov):

 Related: #55326

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

From noreply at wordpress.org  Mon Mar  7 02:02:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 02:02:56 -0000
Subject: [wp-trac] [WordPress Trac] #55326: Conditional classes
 directives in formatting
In-Reply-To: <056.5d933fd28bb30679974960b53abccade@wordpress.org>
References: <056.5d933fd28bb30679974960b53abccade@wordpress.org>
Message-ID: <071.9e604182741288790126975df46d04c3@wordpress.org>

#55326: Conditional classes directives in formatting
-----------------------------+-------------------------------
 Reporter:  vijayhardaha     |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Formatting       |     Version:  5.9.1
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  coding-standards
-----------------------------+-------------------------------

Comment (by vijayhardaha):

 Replying to [comment:1 SergeyBiryukov]:
 > Hi there, welcome back to WordPress Trac! Thanks for the ticket.
 >
 > Just linking to a related ticket here: #50867.

 Thanks.

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

From noreply at wordpress.org  Mon Mar  7 02:18:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 02:18:54 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.c0155bf59ef6661b1e1c7ecd13b78bfb@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch commit                               |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  good-first-bug has-testing-info has-patch => good-first-bug
     has-testing-info has-patch commit


Comment:

 Thanks @costdev and @Boniu91

 > Since strpos() is case sensitive, it returns false

 Yes, indeed, excellent point.

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

From noreply at wordpress.org  Mon Mar  7 02:36:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 02:36:17 -0000
Subject: [wp-trac] [WordPress Trac] #55297: The $is_edge global returns
 false.
In-Reply-To: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
References: <051.29214e1e9bc4c759af0f30a0367db32f@wordpress.org>
Message-ID: <066.27a927e8d7bfb86bb99f6ed2f3578d9d@wordpress.org>

#55297: The $is_edge global returns false.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:
                                                 |  peterwilsoncc
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  good-first-bug has-testing-info      |     Focuses:
  has-patch commit                               |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

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


Comment:

 In [changeset:"52825" 52825]:
 {{{
 #!CommitTicketReference repository="" revision="52825"
 General: Improve MS Edge user-agent sniff.

 Update the `$is_edge` global to be `true` if the browser's user-agent
 contains `Edg` rather than `Edge`. Microsoft have dropped an E from the UA
 string.

 Refer to [https://docs.microsoft.com/en-us/microsoft-edge/web-platform
 /user-agent-guidance#identifiers-for-microsoft-edge-on-various-platforms
 Microsoft's documentation on detecting edge].

 Props costdev, abdullahramzan, mukesh27, Boniu91.
 Fixes #55297.
 }}}

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

From noreply at wordpress.org  Mon Mar  7 04:11:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 04:11:52 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to allow
 for named parameters in WP 6.0
Message-ID: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
----------------------------+--------------------
 Reporter:  peterwilsoncc   |      Owner:  (none)
     Type:  task (blessed)  |     Status:  new
 Priority:  normal          |  Milestone:  6.0
Component:  General         |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+--------------------
 Follow up to #51553, quoted in full below:

 > PHP 8.0 introduces the ability to pass named parameters to function
 calls.
 > Ref: https://wiki.php.net/rfc/named_params
 >
 > Code example:
 > {{{#!php
 > <?php
 > // Using positional arguments:
 > array_fill(0, 100, 50);
 >
 > // Using named arguments:
 > array_fill(start_index: 0, num: 100, value: 50);
 >
 > // Named arguments do not have to follow the same order as positional
 arguments:
 > array_fill(value: 50, num: 100, start_index: 0);
 > }}}
 >
 > **More than anything, this means that, as of PHP 8.0, renaming a
 parameter in a function declaration is a backward-compatibility break! **
 >
 > This should most definitely get prominent  mention in the PHP8 dev-note
 as a lot of Core/plugin/theme developers will not be aware of this at this
 time.
 >
 >
 > I'm opening this ticket to address a number of issues this brings up for
 WordPress Core.
 >
 > I've so far identified three tasks which should be executed ASAP to
 prepare for named parameters in function calls.
 >
 > == Task 1: Review Function Signatures of methods in child classes
 >
 > Methods in child classes may use different parameter names than those
 used for the same method by its parent. Similarly, classes implementing an
 interface do not have to use the same parameter names.
 >
 > While this does not change in PHP 8, it could create problems when the
 method is called using named parameters.
 >
 > To quote from
 [https://wiki.php.net/rfc/named_params#parameter_name_changes_during_inheritance
 the RFC]:
 >
 > > If an inheriting class changes a parameter name, calls using named
 arguments might fail, thus violating the Liskov substitution principle
 (LSP).
 >
 > > PHP will silently accept parameter name changes during inheritance,
 which may result in call-time exceptions when methods with renamed
 parameters are called
 >
 > Code sample:
 > {{{#!php
 > <?php
 > interface I {
 >     public function test($foo, $bar);
 > }
 >
 > class C implements I {
 >     public function test($a, $b) {}
 > }
 >
 > $obj = new C;
 >
 > // Pass params according to I::test() contract
 > $obj->test(foo: "foo", bar: "bar"); // ERROR!
 > }}}
 >
 >
 > **Note: For variadic functions this will not cause an error, but will
 move the unrecognized names to be part of the variadic argument, which can
 cause all sorts of problems.**
 > Code sample
 [https://twitter.com/giveupalready/status/1312139952776306688 courtesy of
 Chris Riley] illustrating the problem: https://3v4l.org/MhJ79
 >
 > With regards to WordPress, I'd like to propose making the parameter
 names in child classes/classes implementing an interface consistent to
 prevent such issues.
 >
 >
 >
 >
 > == Task 2: Review Other Function Signatures
 >
 > 1. The function signatures of existing functions and methods of all
 WordPress code should be examined and non-descriptive parameter names
 should be fixed (renamed) **NOW** as later will no longer be an option
 without creating a BC-break.
 > 2. While using reserved keywords as parameter name labels is allowed, in
 the context of function calls using named parameters, this will easily
 lead to confusion. I'd like to recommend to rename function parameters
 which use reserved keywords to remove this confusion.
 > {{{#!php
 > <?php
 > function array_foobar($toggle = false, $array = []) {}
 >
 > array_foobar(array: $value);
 > }}}
 >
 >
 > == Task 3: Review all uses of `call_user_func_array()`
 >
 > Named parameters cause a BC-break for `call_user_func_array()` when
 passing an associative array.
 > In previous PHP versions, the array keys would have been ignored. In PHP
 8, string keys will be interpreted as parameter name labels.
 >
 > For more detail, see:
 https://wiki.php.net/rfc/named_params#call_user_func_and_friends
 >
 > Basically, we need to make sure that any array passed to
 `call_user_func_array()` does NOT have string keys. If it does or if the
 format of the array is unknown (like when it is passed in via a function
 parameter), we need to add extra safeguards to make the code cross-version
 compatible.
 > A typical way to do this would be to use `array_values()` on the array
 before passing it to `call_user_func_array()`, though beware that
 ''**will**'' break code written for PHP 8 which actually expects the label
 to be used.
 >
 >
 >
 >
 >
 >
 > == Other references:
 >
 > * https://twitter.com/CiaranMcNulty/status/1312087225857970182
 >
 >
 > Related Trac tickets: #50913, #50531

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

From noreply at wordpress.org  Mon Mar  7 04:13:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 04:13:06 -0000
Subject: [wp-trac] [WordPress Trac] #51553: PHP 8.0: code improvements
 to allow for named parameters in function calls
In-Reply-To: <047.9c6819ebb0901d74d5899f7d01667014@wordpress.org>
References: <047.9c6819ebb0901d74d5899f7d01667014@wordpress.org>
Message-ID: <062.c066160c6ff3e43401ddb79a4542f607@wordpress.org>

#51553: PHP 8.0: code improvements to allow for named parameters in function calls
-------------------------------------------------+-------------------------
 Reporter:  jrf                                  |       Owner:
                                                 |  hellofromTonya
     Type:  task (blessed)                       |      Status:  closed
 Priority:  normal                               |   Milestone:  5.9
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  php8 needs-codex early needs-dev-    |     Focuses:  coding-
  note needs-patch                               |  standards
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * status:  reviewing => closed
 * resolution:   => fixed
 * milestone:  6.0 => 5.9


Comment:

 There were a bunch of commits made to this ticket in the 5.9 milestone.

 So the commits don't get misplaced during `git bisect/blame` excursions
 I'm going to move this ticket back to 5.9, close it and create a follow up
 ticket.

 For the follow up work in WP 6.0, please refer to #55327.

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

From noreply at wordpress.org  Mon Mar  7 10:17:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 10:17:07 -0000
Subject: [wp-trac] [WordPress Trac] #55328: Vepament
Message-ID: <054.695f3ec1e10e8bc0c353b7f85e6717e6@wordpress.org>

#55328: Vepament
------------------------------------+-----------------------------
 Reporter:  mahdi10458              |      Owner:  (none)
     Type:  defect (bug)            |     Status:  assigned
 Priority:  normal                  |  Milestone:  Awaiting Review
Component:  Login and Registration  |    Version:
 Severity:  normal                  |   Keywords:  needs-refresh
  Focuses:  accessibility           |
------------------------------------+-----------------------------
 موقع ثبت نام با اشکال مهم روبرو میشم

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

From noreply at wordpress.org  Mon Mar  7 12:34:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 12:34:54 -0000
Subject: [wp-trac] [WordPress Trac] #55328: PHP warning on rename() inside
 download_url() in /wp-admin/includes/file.php
Message-ID: <049.27f741c9d9e05d7605195a9120b52d68@wordpress.org>

#55328: PHP warning on rename() inside download_url() in /wp-
admin/includes/file.php
----------------------------+-----------------------------
 Reporter:  devbd           |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Filesystem API  |    Version:  5.9
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 Hi, I struggle with the following warning on my WordPress site (version
 5.9.0 and currently 5.9.1) whenever I update the plugins:


 {{{
 PHP Warning: rename(/tmp/plugin-name.tmp,plugin-name.plugin-version.zip):
 Permission denied in /wp-admin/includes/file.php on line 1201, referer:
 siteURL/wp-admin/plugins.php
 }}}


 The warning is triggered by rename() function inside download_url()in /wp-
 admin/includes/file.php on line 1201. It's been logged on the site since
 support for Content-Disposition filename was added in WP 5.9:
 developer.wordpress.org/reference/functions/download_url/ The warning is
 also getting logged in WP 5.9.1.

 My site uses ftpext filesystem and I believe this is why 'permission
 denied' warning is triggered. The plugins update successfully, with no
 other issues, however, the above warning is logged every single time.
 Would it be possible to exclude Content-Disposition filename support if
 website uses ftpext filesystem method?

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

From noreply at wordpress.org  Mon Mar  7 12:39:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 12:39:22 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.cbd59944caf9b7c81221a234fb750010@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by audrasjb):

 Thanks @azouamauriac, I'll commit this patch right now 👍

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

From noreply at wordpress.org  Mon Mar  7 12:56:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 12:56:12 -0000
Subject: [wp-trac] [WordPress Trac] #54673: Improve formatting in
 `/wp-admin/user-edit.php`.
In-Reply-To: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
References: <051.47d1f662ecfd8b9a5732f68c3237f001@wordpress.org>
Message-ID: <066.1a3e80c22be68491c95f17c159f73cad@wordpress.org>

#54673: Improve formatting in `/wp-admin/user-edit.php`.
------------------------------------+-------------------------------
 Reporter:  costdev                 |       Owner:  audrasjb
     Type:  enhancement             |      Status:  closed
 Priority:  normal                  |   Milestone:  6.0
Component:  Administration          |     Version:  5.9
 Severity:  normal                  |  Resolution:  fixed
 Keywords:  has-patch early commit  |     Focuses:  coding-standards
------------------------------------+-------------------------------

Comment (by audrasjb):

 In [changeset:"52826" 52826]:
 {{{
 #!CommitTicketReference repository="" revision="52826"
 Docs: Correct the indentation in `delete_term_relationships` filter.

 See #54673.
 }}}

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

From noreply at wordpress.org  Mon Mar  7 13:06:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 13:06:07 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.ed07e25481c77994b5b4efba58a827a6@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by audrasjb):

 In [changeset:"52827" 52827]:
 {{{
 #!CommitTicketReference repository="" revision="52827"
 Docs: Use third-person singular verbs for function descriptions in `wp-
 includes/class-wp-user.php`.

 Props azouamauriac.
 See #54729.
 }}}

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

From noreply at wordpress.org  Mon Mar  7 13:59:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 13:59:36 -0000
Subject: [wp-trac] [WordPress Trac] #55329: add_clean_index function throws
 PHP notice error
Message-ID: <056.15bb84f0857f77dfff6c09fd584c15c1@wordpress.org>

#55329: add_clean_index function throws PHP notice error
-----------------------------+-----------------------------
 Reporter:  gvgvgvijayan     |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:
 Severity:  normal           |   Keywords:
  Focuses:  administration   |
-----------------------------+-----------------------------
 When I tried to add index for newly created column my error log filled
 with php notice 25 times because of the function `drop_index` which is
 called inside the function `add_clean_index`.

 Sample snippet:
 {{{#!php
 <?php
 function add_country_iso_code_column() {
         if ( ! function_exists( 'maybe_add_column' ) ) {
                 require_once ABSPATH . 'wp-admin/includes/upgrade.php';
         }

         global $wpdb;

         $table_name  = $wpdb->base_prefix . 'defender_lockout_log';
         $column_name = 'country_iso_code';
         $create_ddl  = "ALTER TABLE {$table_name} ADD {$column_name}
 CHAR(2) DEFAULT NULL";

         maybe_add_column( $table_name, $column_name, $create_ddl );
         add_clean_index( $table_name, $column_name );
 }
 }}}

 Error:

 {{{
 [Mon Mar 07 18:45:40.809008 2022] [php:notice] [pid 1167] [client
 127.0.0.1:48886] WordPress database error Can't DROP 'country_iso_code_1';
 check that column/key exists for query ALTER TABLE
 `wp_defender_lockout_log` DROP INDEX `country_iso_code_1` made by
 require_once('wp-admin/network/admin.php'), require_once('wp-
 admin/admin.php'), require_once('wp-load.php'), require_once('wp-
 config.php'), require_once('wp-settings.php'), do_action('init'),
 WP_Hook->do_action, WP_Hook->apply_filters, WP_Defender\\Upgrader->run,
 WP_Defender\\Upgrader->upgrade_2_8_1,
 WP_Defender\\Upgrader->add_country_iso_code_column, add_clean_index,
 drop_index, referer: http://multi.test/wp-admin/network/update.php?action
 =upload-plugin&package=55&overwrite=update-plugin&_wpnonce=c8b371f5b8
 }}}

 ----

 Error log screenshot:
 [https://i.postimg.cc/2jqsb3Z4/bug-report.png]

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

From noreply at wordpress.org  Mon Mar  7 14:18:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 14:18:55 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.93418d3f56528ce1897ef36e02942a9b@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:
                                                 |  johnbillion
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback has-unit-     |     Focuses:
  tests needs-testing                            |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

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


Comment:

 The above PR refreshes the last patch proposed by @johnbillion.
 Adding `needs-testing` keyword.

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

From noreply at wordpress.org  Mon Mar  7 14:36:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 14:36:00 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.f4aa5b9a51d39e15e7f6d99d234da41c@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:
                                                 |  johnbillion
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback has-unit-     |     Focuses:
  tests needs-testing                            |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 > One test fails: http://example.mp3 incorrectly results in an extension
 of mp3, but this isn't strictly related to this change and AFAIK none of
 the extensions in wp_get_mime_types() are valid TLDs anyway.

 👆 this is still an issue with the current PR. @johnbillion should we just
 remove the failing test?

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

From noreply at wordpress.org  Mon Mar  7 14:42:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 14:42:29 -0000
Subject: [wp-trac] [WordPress Trac] #43716: Not work
 "option_active_plugins" filter in front-end
In-Reply-To: <054.1b96fa5f3f024717a48e63207d879f49@wordpress.org>
References: <054.1b96fa5f3f024717a48e63207d879f49@wordpress.org>
Message-ID: <069.6e0974d9a1871d1292256920397c7ff1@wordpress.org>

#43716: Not work "option_active_plugins" filter in front-end
-------------------------------+------------------------------
 Reporter:  hamedmoodi         |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Plugins            |     Version:  4.9.5
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by azouamauriac):

 * keywords:   => reporter-feedback


Comment:

 Hi there, welcome to WordPress Trac, thanks for the report! I'm not able
 to reproduce the issue, so can you provide more detail about how to
 reproduce it?
 Thanks.

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

From noreply at wordpress.org  Mon Mar  7 14:42:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 14:42:38 -0000
Subject: [wp-trac] [WordPress Trac] #51657: Correct displaying the
 _doing_it_wrong() message for add_theme_support( 'html5' )
In-Reply-To: <058.e8ff2e7a9c63b3b4ccf47937ea402cbd@wordpress.org>
References: <058.e8ff2e7a9c63b3b4ccf47937ea402cbd@wordpress.org>
Message-ID: <073.1fe273b7f35ad80e50c2275f9e96cfa3@wordpress.org>

#51657: Correct displaying the _doing_it_wrong() message for add_theme_support(
'html5' )
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch needs-     |     Focuses:
  dev-note needs-refresh needs-unit-tests        |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * milestone:  Future Release => 6.0


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

From noreply at wordpress.org  Mon Mar  7 14:43:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 14:43:04 -0000
Subject: [wp-trac] [WordPress Trac] #51657: Correct displaying the
 _doing_it_wrong() message for add_theme_support( 'html5' )
In-Reply-To: <058.e8ff2e7a9c63b3b4ccf47937ea402cbd@wordpress.org>
References: <058.e8ff2e7a9c63b3b4ccf47937ea402cbd@wordpress.org>
Message-ID: <073.c7a3f6925eaba42f43b5de9e19bccf6c@wordpress.org>

#51657: Correct displaying the _doing_it_wrong() message for add_theme_support(
'html5' )
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-screenshots has-patch needs-     |     Focuses:
  dev-note needs-refresh needs-unit-tests        |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52828" 52828]:
 {{{
 #!CommitTicketReference repository="" revision="52828"
 Themes: Correct the logic for displaying a `_doing_it_wrong()` notice for
 `add_theme_support( 'html5' )`.

 * Calling `add_theme_support( 'html5' )` without passing an array of
 supported types should throw a `_doing_it_wrong()` notice: "You need to
 pass an array of types".
 * If the second parameter is not specified, it should fall back to an
 array of `comment-list`, `comment-form`, and `search-form` for backward
 compatibility.
 * If the second parameter is not an array, the function should return
 `false`.

 The latter two points are covered by existing unit tests. The first one is
 now addressed by `@expectedIncorrectUsage`.

 Follow-up to [25193], [25235], [25785].

 Props audrasjb, peterwilsoncc, SergeyBiryukov.
 Fixes #51657.
 }}}

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

From noreply at wordpress.org  Mon Mar  7 14:43:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 14:43:22 -0000
Subject: [wp-trac] [WordPress Trac] #51657: Correct displaying the
 _doing_it_wrong() message for add_theme_support( 'html5' )
In-Reply-To: <058.e8ff2e7a9c63b3b4ccf47937ea402cbd@wordpress.org>
References: <058.e8ff2e7a9c63b3b4ccf47937ea402cbd@wordpress.org>
Message-ID: <073.a9a3acc763dc1127bcbd1f0dfb913e27@wordpress.org>

#51657: Correct displaying the _doing_it_wrong() message for add_theme_support(
'html5' )
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-screenshots has-patch needs-     |     Focuses:
  dev-note                                       |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * keywords:
     has-screenshots has-patch needs-dev-note needs-refresh needs-unit-
     tests
     => has-screenshots has-patch needs-dev-note


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

From noreply at wordpress.org  Mon Mar  7 15:37:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 15:37:45 -0000
Subject: [wp-trac] [WordPress Trac] #45853: Videos embedded in a plugins
 readme.txt does not load while searching for a plugin in an actual WP
 install (not wp.org)
In-Reply-To: <054.efae7ef8699cc0a2ca018b7115a6047d@wordpress.org>
References: <054.efae7ef8699cc0a2ca018b7115a6047d@wordpress.org>
Message-ID: <069.9beabb0852af54e39330a7257f7987e9@wordpress.org>

#45853: Videos embedded in a plugins readme.txt does not load while searching for a
plugin in an actual WP install (not wp.org)
--------------------------+------------------------------
 Reporter:  thememason    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Plugins       |     Version:  5.0.2
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  administration
--------------------------+------------------------------
Changes (by azouamauriac):

 * keywords:   => needs-patch
 * focuses:   => administration


Comment:

 Hi there welcome to wordpress trac! thanks for the report.
 Replying to [ticket:45853 thememason]:
 > videos do not load when you're searching for a plugin via an actual
 WordPress install.

 I don't really get this one, can you explain more?


 > In addition, if you install a plugin and click on "View Details" to
 learn more about the plugin, the video also does not load here either.
 Inspect element shows an empty span tag:
 >
 > {{{
 > <span class="embed-youtube"></span>
 > }}}
 >
 > This should either embed the video or at the least display a link to the
 video.
 >
 > Here's an example plugin for reference: https://wordpress.org/plugins
 /simple-icons/
 I'm able to reproduce this one.

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

From noreply at wordpress.org  Mon Mar  7 16:26:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 16:26:50 -0000
Subject: [wp-trac] [WordPress Trac] #55324: Twenty Twenty: Scroll to top
 not working
In-Reply-To: <053.fa149de27f743cf9d574f331ee5a4827@wordpress.org>
References: <053.fa149de27f743cf9d574f331ee5a4827@wordpress.org>
Message-ID: <068.4ca4ad0578323b1176710fb8e83510d4@wordpress.org>

#55324: Twenty Twenty: Scroll to top not working
-------------------------------+------------------------------
 Reporter:  Presskopp          |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Bundled Theme      |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by sabernhardt):

 * keywords:   => reporter-feedback


Comment:

 The `header` element has `id="site-header"` in
 [https://core.trac.wordpress.org/browser/trunk/src/wp-
 content/themes/twentytwenty/header.php?rev=52013#L33 Twenty Twenty's
 header.php].

 Does a plugin (or child theme) change that ID?

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

From noreply at wordpress.org  Mon Mar  7 17:36:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 17:36:35 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.d1ac217e38ee43367a4b2d6566baf81a@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by Mamaduka):

 I was able to reproduce the issue.

 Based on my quick tests, the issue is fixed if I update the following code
 to use `realpath`.


 {{{
 $wpinc_path_norm = wp_normalize_path( realpath( ABSPATH . WPINC ) );
 }}}


 Cc. @aristath and @gziolo, since you're more familiar with this part of
 the codebase.

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

From noreply at wordpress.org  Mon Mar  7 17:48:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 17:48:17 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.cbc06ce504ed9bf37f458238da5f3e75@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by pgpagely):

 I can confirm this looks like it fixes the issue on our side when applied
 like this as well. It would be great to get this out in the next
 maintenance release if it is passing tests because right now it is a
 breaking change as far as I can tell.

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

From noreply at wordpress.org  Mon Mar  7 18:14:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 18:14:13 -0000
Subject: [wp-trac] [WordPress Trac] #55330: Set global_styles_svg_filters
 transient to return true causing symbol `1` to be appeared on the screen in
 a production mode
Message-ID: <060.aaacdb7d2decfa020f9284bbed451de7@wordpress.org>

#55330: Set global_styles_svg_filters transient to return true causing symbol `1`
to be appeared on the screen in a production mode
------------------------------+-----------------------------
 Reporter:  aliakseyenkaihar  |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  General           |    Version:  5.9.1
 Severity:  trivial           |   Keywords:
  Focuses:                    |
------------------------------+-----------------------------
 WordPress 5.9.1
 PHP 8.0.15

 When I set `global_styles_svg_filters` to return true (to prevent from
 being set - I don't use `theme.json` but request is sending so I want to
 disable it) it renders `1` at the top of the website

 Steps to reproduce on TwentyTwentyTwo theme:

 1. Paste these lines in `functions.php`

 {{{#!php
 <?php
 // @see https://github.com/WordPress/WordPress/blob/master/wp-
 includes/option.php#L131
 $theme = get_stylesheet();
 add_filter( "pre_transient_global_styles_svg_filters_{$theme}",
 '__return_true' );
 }}}

 You will see `1` at the top of any screen on site's front

 If you define `WP_DEBUG` as `true` or `WP_ENVIRONMENT_TYPE` as
 `development` it will dissapear

 It happens [here](https://github.com/WordPress/WordPress/blob/master/wp-
 includes/script-loader.php#L2361) - `wp_get_global_styles_svg_filters()`
 function will return `true` (as I manually set transient) so `$cached`
 [will](https://github.com/WordPress/WordPress/blob/2399966d8ce0f89e3989360929fa01edf86e15c0
 /wp-includes/global-styles-and-settings.php#L172) be `true` as well.
 Therefore it echoing as 1

 It is so minor and specific but it happened to me :) So because I may set
 any return type for this transient my guess there is no need for extra
 check but for a filter. For example

 {{{#!php
 <?php
 // script-loader.php
 $svg_filters = wp_get_global_styles_svg_filters();
 $filters = apply_filters( 'wp_get_global_styles_svg_filters', $svg_filters
 );
 }}}

 This way I will control svg filters output myself

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

From noreply at wordpress.org  Mon Mar  7 18:17:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 18:17:37 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.6808f0a719b4c5c43c2c62173edb6b6f@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:
                                                 |  johnbillion
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by johnbillion):

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


Comment:

 Yes let's remove that test please and get this in 👍

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

From noreply at wordpress.org  Mon Mar  7 19:14:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 19:14:33 -0000
Subject: [wp-trac] [WordPress Trac] #55323: When an image is edited the
 URL of the image is not updated
In-Reply-To: <050.79ed9f05007caabff54b42e46b07c848@wordpress.org>
References: <050.79ed9f05007caabff54b42e46b07c848@wordpress.org>
Message-ID: <065.cc168091f9c9ba00396f32893ed228b3@wordpress.org>

#55323: When an image is edited the URL of the image is not updated
--------------------------+---------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  ui, administration
--------------------------+---------------------------------

Comment (by adamsilverstein):

 Should the URL show the edited image url, or should the header for the
 field be updated to indicate it is the "original" image (if that is what
 it is)? So instead of "File URL" maybe "Original file URL"?

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

From noreply at wordpress.org  Mon Mar  7 19:16:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 19:16:43 -0000
Subject: [wp-trac] [WordPress Trac] #55324: Twenty Twenty: Scroll to top
 not working
In-Reply-To: <053.fa149de27f743cf9d574f331ee5a4827@wordpress.org>
References: <053.fa149de27f743cf9d574f331ee5a4827@wordpress.org>
Message-ID: <068.8c49f38a14e5b4e640edafa225885a32@wordpress.org>

#55324: Twenty Twenty: Scroll to top not working
-------------------------------+------------------------------
 Reporter:  Presskopp          |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Bundled Theme      |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by Presskopp):

 It has the ID, but - don't ask me why - it's not working as is

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

From noreply at wordpress.org  Mon Mar  7 19:34:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 19:34:24 -0000
Subject: [wp-trac] [WordPress Trac] #55323: When an image is edited the
 URL of the image is not updated
In-Reply-To: <050.79ed9f05007caabff54b42e46b07c848@wordpress.org>
References: <050.79ed9f05007caabff54b42e46b07c848@wordpress.org>
Message-ID: <065.8e83fc01d73b13fe3680ebb12bbacf16@wordpress.org>

#55323: When an image is edited the URL of the image is not updated
--------------------------+---------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  ui, administration
--------------------------+---------------------------------

Comment (by mitogh):

 > Should the URL show the edited image url, or should the header for the
 field be updated to indicate it is the "original" image (if that is what
 it is)? So instead of "File URL" maybe "Original file URL"?

 The URL should use the rotated version as the URL as when you reload the
 page after the edit has been completed the URL now uses the rotated
 version.

 Same for the File URL when the page is refreshed the File URL now
 references the rotated version, so in this case both fields should be
 updated to reflect the new values for:

 - File URL
 - Filename
 - File size
 - Dimensions

 From my perspective, the expected result is the same as if you refresh the
 page and new values are populated in the areas described above.

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

From noreply at wordpress.org  Mon Mar  7 19:38:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 19:38:35 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.ccf725abd2c93286765854e27b999869@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:
                                                 |  johnbillion
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note commit                                    |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests needs-testing => has-patch has-unit-
     tests needs-dev-note commit


Comment:

 Alright the tests are passing now and I tested the patch successfully.
 Marking for a mention in the Misc changes devnote.
 Self assigning for `commit`.

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

From noreply at wordpress.org  Mon Mar  7 19:38:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 19:38:43 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.e755785ef37fc4fe304d4b7e7c1dff93@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note commit                                    |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * owner:  johnbillion => audrasjb
 * status:  reviewing => accepted


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

From noreply at wordpress.org  Mon Mar  7 20:20:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 20:20:56 -0000
Subject: [wp-trac] [WordPress Trac] #55330: Set
 global_styles_svg_filters transient to return true causing symbol `1` to be
 appeared on the screen in a production mode
In-Reply-To: <060.aaacdb7d2decfa020f9284bbed451de7@wordpress.org>
References: <060.aaacdb7d2decfa020f9284bbed451de7@wordpress.org>
Message-ID: <075.28a380bb1284f07936abbdbc51658da8@wordpress.org>

#55330: Set global_styles_svg_filters transient to return true causing symbol `1`
to be appeared on the screen in a production mode
------------------------------+------------------------------
 Reporter:  aliakseyenkaihar  |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  General           |     Version:  5.9.1
 Severity:  trivial           |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by vijayhardaha):

 Hey @aliakseyenkaihar, May I ask why `__return_true` instead of setting
 `__return_false` ? as you mentioned **to prevent from being set** that can
 be done by setting false, since you're setting it true that's validated
 the if condition and you returned content is being printed as 1.

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

From noreply at wordpress.org  Mon Mar  7 21:11:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 21:11:25 -0000
Subject: [wp-trac] [WordPress Trac] #55324: Twenty Twenty: Scroll to top
 not working
In-Reply-To: <053.fa149de27f743cf9d574f331ee5a4827@wordpress.org>
References: <053.fa149de27f743cf9d574f331ee5a4827@wordpress.org>
Message-ID: <068.c89ea275e7b0a08886150cd85fac9774@wordpress.org>

#55324: Twenty Twenty: Scroll to top not working
-------------------------------+------------------------------
 Reporter:  Presskopp          |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Bundled Theme      |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by sabernhardt):

 1. Which browser(s) and operating system do you use when it does not work?
 2. If you look at the browser console, does it show any errors? (this
 might relate to the JavaScript scroll effect)

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

From noreply at wordpress.org  Mon Mar  7 21:36:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 21:36:42 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.fb168452999adede9da3ebc803e2ad62@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------+----------------------------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  accessibility, javascript
----------------------------+----------------------------------------
Changes (by johnregan3):

 * Attachment "55078-1.diff" added.

 Updated version of previous patch.

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

From noreply at wordpress.org  Mon Mar  7 21:37:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 21:37:44 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.190dc9a06c82b47512182499e20d74b7@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------+----------------------------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  accessibility, javascript
----------------------------+----------------------------------------

Comment (by johnregan3):

 This new patch (55078-1) fixes an error in the original patch.

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

From noreply at wordpress.org  Mon Mar  7 21:39:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 21:39:22 -0000
Subject: [wp-trac] [WordPress Trac] #21077: Add support for custom ports
 in multisite site addresses
In-Reply-To: <050.da44ba80528d7e12580241ce17e26436@wordpress.org>
References: <050.da44ba80528d7e12580241ce17e26436@wordpress.org>
Message-ID: <065.97a4afef99f369bd8c95e92755a65806@wordpress.org>

#21077: Add support for custom ports in multisite site addresses
----------------------------------------+-----------------------------
 Reporter:  djzone                      |       Owner:  (none)
     Type:  enhancement                 |      Status:  reopened
 Priority:  normal                      |   Milestone:  Future Release
Component:  Bootstrap/Load              |     Version:  3.4
 Severity:  normal                      |  Resolution:
 Keywords:  needs-unit-tests has-patch  |     Focuses:  multisite
----------------------------------------+-----------------------------

Comment (by Clorith):

 I'll add a note that multisite with custom ports appear to work out of the
 box, but requires you to edit the `wp_sites` database entry, and add the
 `:<port>` your self. This is because the sanitize on save function in
 multisite strips out `:`, leaving you with a `url<port>` instead of
 `url:<port>` db entry if using the interface.

 I'm not sure if there's any other issue besides this one, if there's any
 concerns beyond back-compat then this is the place to outline them, but
 from some preliminary testing it would appear that updating the filters to
 allow a format of `:[0-9]+` to pass through the sanitizer on save
 shouldn't break anything, and open things up for custom ports to the users
 hearts desire 🤔

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

From noreply at wordpress.org  Mon Mar  7 21:42:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 21:42:56 -0000
Subject: [wp-trac] [WordPress Trac] #54924: [video] shortcode with vimeo
 url
In-Reply-To: <049.db37046112dcb75b85eda256e8d811c7@wordpress.org>
References: <049.db37046112dcb75b85eda256e8d811c7@wordpress.org>
Message-ID: <064.68356afd90ec1faeee1c570c54ca75ce@wordpress.org>

#54924: [video] shortcode with vimeo url
------------------------------------------------+--------------------------
 Reporter:  elpix                               |       Owner:  (none)
     Type:  defect (bug)                        |      Status:  new
 Priority:  normal                              |   Milestone:  Awaiting
                                                |  Review
Component:  Embeds                              |     Version:  5.9
 Severity:  critical                            |  Resolution:
 Keywords:  has-testing-info reporter-feedback  |     Focuses:  ui
------------------------------------------------+--------------------------

Comment (by vijayhardaha):

 after 4.8 or 4.9 changes were made due to some issue with ME.js, details
 are available here
 https://core.trac.wordpress.org/ticket/40866
 {{{#!php
 <?php
 // Remove all query arguments and force SSL - see #40866.
 $parsed_vimeo_url = wp_parse_url( $atts['src'] );
 $vimeo_src        = 'https://' . $parsed_vimeo_url['host'] .
 $parsed_vimeo_url['path'];

 // Add loop param for mejs bug - see #40977, not needed after #39686.
 $loop        = $atts['loop'] ? '1' : '0';
 $atts['src'] = add_query_arg( 'loop', $loop, $vimeo_src );
 }}}
 This part of the code changes the src of vimeo urls.

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

From noreply at wordpress.org  Mon Mar  7 21:59:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 21:59:44 -0000
Subject: [wp-trac] [WordPress Trac] #52423: Editing a category or a tag,
 and getting error message "You need a higher level of permission.
 Sorry, you are not allowed to edit this item."
In-Reply-To: <054.830e4883156008ed2da3c0ae50db1854@wordpress.org>
References: <054.830e4883156008ed2da3c0ae50db1854@wordpress.org>
Message-ID: <069.3b9f2761e232a037a9508afa92b31921@wordpress.org>

#52423: Editing a category or a tag, and getting error message "You need a higher
level of permission. Sorry, you are not allowed to edit this item."
--------------------------+-----------------------
 Reporter:  webtechIMT    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Taxonomy      |     Version:  5.6
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------

Comment (by vijayhardaha):

 Try this solution on a staging website
 https://stackoverflow.com/a/44175853/11848895

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

From noreply at wordpress.org  Mon Mar  7 22:13:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 22:13:42 -0000
Subject: [wp-trac] [WordPress Trac] #46297: Unable to edit specific
 terms : rest_cannot_assign_term OR 403
In-Reply-To: <049.2c16ca488f09279f482af9c6a35d7dfb@wordpress.org>
References: <049.2c16ca488f09279f482af9c6a35d7dfb@wordpress.org>
Message-ID: <064.951d1dd3c324d75b9c1bb48b1b3e80b2@wordpress.org>

#46297: Unable to edit specific terms : rest_cannot_assign_term OR 403
--------------------------+----------------------------------
 Reporter:  enps5         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Taxonomy      |     Version:  4.1
 Severity:  major         |  Resolution:
 Keywords:                |     Focuses:  multisite, rest-api
--------------------------+----------------------------------
Description changed by SergeyBiryukov:

Old description:

> This bug seems to be related to this changeset :
> https://core.trac.wordpress.org/changeset/30056
>

> When i try create a new post with gutenberg and categorize the post
> taxonomy "bibliografía" i've this error :
>
> {{{
> Updating failed
> }}}
>
> The request body is :
>
> {{{
> {"status":"draft","title":"test","excerpt":"","categories":[4092],"content":"<!--
> wp:paragraph -->\n<p>test</p>\n<!-- /wp:paragraph -->","id":1552}
> }}}
>
> Response from wordpress :
>
> {{{
> {"code":"rest_cannot_assign_term","message":"Sorry, you are not allowed
> to assign the provided terms.","data":{"status":403}}
> }}}
>
> On a WordPress network, when i attempt to edit the category as a
> wordpress super-user (this time i use the term.php's file)  :
> https://DOMAIN.TLD/wp-
> admin/term.php?taxonomy=category&tag_ID=4092&post_type=post&wp_http_referer
> =%2Fwp-admin%2Fedit-
> tags.php%3Ftaxonomy%3Dcategory%26post_type%3Dpost%26s%3Dbibliograf%25C3%25ADa
> Wordpress return :
>
> {{{
> You need a higher level of permission.
>
> Sorry, you are not allowed to edit this item.
> }}}
>
> A further look inside MySQL shows :
>
> {{{
> SELECT * FROM wp_2635_terms where term_id = 4092 ;
> +---------+---------------+--------------+------------+
> | term_id | name          | slug         | term_group |
> +---------+---------------+--------------+------------+
> |    4092 | bibliografía  | bibliografia |          0 |
> +---------+---------------+--------------+------------+
>
> SELECT * FROM wp_2635_term_taxonomy where term_id = 4092 ;
> +------------------+---------+----------+-------------+--------+-------+
> | term_taxonomy_id | term_id | taxonomy | description | parent | count |
> +------------------+---------+----------+-------------+--------+-------+
> |              254 |    4092 | category |             |      0 |     1 |
> |              197 |    4092 | post_tag |             |      0 |     1 |
> +------------------+---------+----------+-------------+--------+-------+
>
> SELECT * FROM wp_2635_term_taxonomy GROUP BY term_id HAVING
> COUNT(term_id) > 1;
> +------------------+---------+----------+-------------+--------+-------+
> | term_taxonomy_id | term_id | taxonomy | description | parent | count |
> +------------------+---------+----------+-------------+--------+-------+
> |              254 |    4092 | category |             |      0 |     1 |
> |              205 |    4191 | category |             |      0 |     7 |
> |              357 |   52788 | category |             |      0 |     1 |
> |              196 |   57611 | category |             |      0 |     4 |
> |              354 |  226144 | category |             |      0 |     6 |
> |              355 |  955714 | category |             |      0 |     2 |
> |              298 | 1595453 | category |             |      0 |     2 |
> |              313 | 1595513 | category |             |      0 |     8 |
> |              177 | 1595576 | category |             |      0 |    12 |
> |              379 | 1939409 | category |             |      0 |     6 |
> |              329 | 1939420 | category |             |      0 |     4 |
> |              312 | 1939471 | category |             |      0 |     2 |
> |              314 | 1939479 | category |             |      0 |     4 |
> |              359 | 2399420 | category |             |      0 |     1 |
> |              438 | 2454276 | category |             |      0 |     1 |
> +------------------+---------+----------+-------------+--------+-------+
> 15 rows in set (0.00 sec)
>
> select term_id,slug,COUNT(slug) from wp_2635_terms group by slug having
> count(slug) > 1;
> +---------+------------------------------+-------------+
> | term_id | slug                         | COUNT(slug) |
> +---------+------------------------------+-------------+
> |    4191 | antropologia                 |           4 |
> | 1595576 | antropologia-linguistica     |           2 |
> | 1595401 | audios                       |           3 |
> |    4092 | bibliografia                 |           2 |
> |  809963 | canal-uned                   |           3 |
> |   52788 | cervantes                    |           2 |
> | 2454276 | coelei                       |           2 |
> | 1595453 | curso-de-verano              |           2 |
> | 1939479 | edicion-de-textos            |           2 |
> | 1595578 | etnografia-del-habla         |           3 |
> | 1595478 | etnolinguistica              |           3 |
> | 1939420 | eugenio-de-salazar           |           2 |
> | 1939409 | glosonimia                   |           2 |
> |  465167 | jornadas                     |           3 |
> | 1595513 | lexicografia                 |           2 |
> | 1595414 | metodologia-docente          |           3 |
> | 1595416 | nuevas-propuestas-didacticas |           3 |
> | 1595417 | paper-li                     |           3 |
> |  200504 | proyectos                    |           3 |
> |   57611 | publicaciones                |           2 |
> | 2399420 | tecnolecto-marinero          |           2 |
> |  226144 | uned                         |           2 |
> | 1939471 | universidad-del-pacifico     |           2 |
> |  955714 | vocabulario                  |           2 |
> +---------+------------------------------+-------------+
>
> desc wp_2635_terms ;
> +------------+---------------------+------+-----+---------+----------------+
> | Field      | Type                | Null | Key | Default | Extra
> |
> +------------+---------------------+------+-----+---------+----------------+
> | term_id    | bigint(20) unsigned | NO   | PRI | NULL    |
> auto_increment |
> | name       | varchar(200)        | NO   | MUL |         |
> |
> | slug       | varchar(200)        | NO   | MUL |         |
> |
> | term_group | bigint(10)          | NO   |     | 0       |
> |
> +------------+---------------------+------+-----+---------+----------------+
> 4 rows in set (0.01 sec)
>
> desc wp_2635_term_taxonomy ;
> +------------------+---------------------+------+-----+---------+----------------+
> | Field            | Type                | Null | Key | Default | Extra
> |
> +------------------+---------------------+------+-----+---------+----------------+
> | term_taxonomy_id | bigint(20) unsigned | NO   | PRI | NULL    |
> auto_increment |
> | term_id          | bigint(20) unsigned | NO   | MUL | 0       |
> |
> | taxonomy         | varchar(32)         | NO   | MUL |         |
> |
> | description      | longtext            | NO   |     | NULL    |
> |
> | parent           | bigint(20) unsigned | NO   |     | 0       |
> |
> | count            | bigint(20)          | NO   |     | 0       |
> |
> +------------------+---------------------+------+-----+---------+----------------+
>
> show create table  wp_2635_terms \G
> *************************** 1. row ***************************
>        Table: wp_2635_terms
> Create Table: CREATE TABLE `wp_2635_terms` (
>   `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
>   `name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
>   `slug` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
>   `term_group` bigint(10) NOT NULL DEFAULT '0',
>   PRIMARY KEY (`term_id`),
>   KEY `slug` (`slug`(191)),
>   KEY `name` (`name`(191))
> ) ENGINE=InnoDB AUTO_INCREMENT=2454306 DEFAULT CHARSET=utf8mb4
> COLLATE=utf8mb4_unicode_ci
> 1 row in set (0.00 sec)
>

> show create table  wp_2635_term_taxonomy \G
> *************************** 1. row ***************************
>        Table: wp_2635_term_taxonomy
> Create Table: CREATE TABLE `wp_2635_term_taxonomy` (
>   `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
>   `term_id` bigint(20) unsigned NOT NULL DEFAULT '0',
>   `taxonomy` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
>   `description` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
>   `parent` bigint(20) unsigned NOT NULL DEFAULT '0',
>   `count` bigint(20) NOT NULL DEFAULT '0',
>   PRIMARY KEY (`term_taxonomy_id`),
>   UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`),
>   KEY `taxonomy` (`taxonomy`)
> ) ENGINE=InnoDB AUTO_INCREMENT=462 DEFAULT CHARSET=utf8mb4
> COLLATE=utf8mb4_unicode_ci
> 1 row in set (0.00 sec)
>
> }}}
>

> If i delete (via MySQL delete statement) the post_tag with the term_id
> 4092, i can edit again the category. I had trouble reproducing the bug or
> to simply to identify the cause of the problem.
>
> We're running a WordPress Network with ~5000blogs, i've identified this
> problem on 1300 sites.
> We work with MySQL "classic replication" (master / slave), we already had
> a master x3 configuration with Galera Cluster. This can be an interesting
> element.
>
> I remain available for aby further information.

New description:

 This bug seems to be related to this changeset : [30056]


 When i try create a new post with gutenberg and categorize the post
 taxonomy "bibliografía" i've this error :

 {{{
 Updating failed
 }}}

 The request body is :

 {{{
 {"status":"draft","title":"test","excerpt":"","categories":[4092],"content":"<!--
 wp:paragraph -->\n<p>test</p>\n<!-- /wp:paragraph -->","id":1552}
 }}}

 Response from wordpress :

 {{{
 {"code":"rest_cannot_assign_term","message":"Sorry, you are not allowed to
 assign the provided terms.","data":{"status":403}}
 }}}

 On a WordPress network, when i attempt to edit the category as a wordpress
 super-user (this time i use the term.php's file)  :
 https://DOMAIN.TLD/wp-
 admin/term.php?taxonomy=category&tag_ID=4092&post_type=post&wp_http_referer
 =%2Fwp-admin%2Fedit-
 tags.php%3Ftaxonomy%3Dcategory%26post_type%3Dpost%26s%3Dbibliograf%25C3%25ADa
 Wordpress return :

 {{{
 You need a higher level of permission.

 Sorry, you are not allowed to edit this item.
 }}}

 A further look inside MySQL shows :

 {{{
 SELECT * FROM wp_2635_terms where term_id = 4092 ;
 +---------+---------------+--------------+------------+
 | term_id | name          | slug         | term_group |
 +---------+---------------+--------------+------------+
 |    4092 | bibliografía  | bibliografia |          0 |
 +---------+---------------+--------------+------------+

 SELECT * FROM wp_2635_term_taxonomy where term_id = 4092 ;
 +------------------+---------+----------+-------------+--------+-------+
 | term_taxonomy_id | term_id | taxonomy | description | parent | count |
 +------------------+---------+----------+-------------+--------+-------+
 |              254 |    4092 | category |             |      0 |     1 |
 |              197 |    4092 | post_tag |             |      0 |     1 |
 +------------------+---------+----------+-------------+--------+-------+

 SELECT * FROM wp_2635_term_taxonomy GROUP BY term_id HAVING COUNT(term_id)
 > 1;
 +------------------+---------+----------+-------------+--------+-------+
 | term_taxonomy_id | term_id | taxonomy | description | parent | count |
 +------------------+---------+----------+-------------+--------+-------+
 |              254 |    4092 | category |             |      0 |     1 |
 |              205 |    4191 | category |             |      0 |     7 |
 |              357 |   52788 | category |             |      0 |     1 |
 |              196 |   57611 | category |             |      0 |     4 |
 |              354 |  226144 | category |             |      0 |     6 |
 |              355 |  955714 | category |             |      0 |     2 |
 |              298 | 1595453 | category |             |      0 |     2 |
 |              313 | 1595513 | category |             |      0 |     8 |
 |              177 | 1595576 | category |             |      0 |    12 |
 |              379 | 1939409 | category |             |      0 |     6 |
 |              329 | 1939420 | category |             |      0 |     4 |
 |              312 | 1939471 | category |             |      0 |     2 |
 |              314 | 1939479 | category |             |      0 |     4 |
 |              359 | 2399420 | category |             |      0 |     1 |
 |              438 | 2454276 | category |             |      0 |     1 |
 +------------------+---------+----------+-------------+--------+-------+
 15 rows in set (0.00 sec)

 select term_id,slug,COUNT(slug) from wp_2635_terms group by slug having
 count(slug) > 1;
 +---------+------------------------------+-------------+
 | term_id | slug                         | COUNT(slug) |
 +---------+------------------------------+-------------+
 |    4191 | antropologia                 |           4 |
 | 1595576 | antropologia-linguistica     |           2 |
 | 1595401 | audios                       |           3 |
 |    4092 | bibliografia                 |           2 |
 |  809963 | canal-uned                   |           3 |
 |   52788 | cervantes                    |           2 |
 | 2454276 | coelei                       |           2 |
 | 1595453 | curso-de-verano              |           2 |
 | 1939479 | edicion-de-textos            |           2 |
 | 1595578 | etnografia-del-habla         |           3 |
 | 1595478 | etnolinguistica              |           3 |
 | 1939420 | eugenio-de-salazar           |           2 |
 | 1939409 | glosonimia                   |           2 |
 |  465167 | jornadas                     |           3 |
 | 1595513 | lexicografia                 |           2 |
 | 1595414 | metodologia-docente          |           3 |
 | 1595416 | nuevas-propuestas-didacticas |           3 |
 | 1595417 | paper-li                     |           3 |
 |  200504 | proyectos                    |           3 |
 |   57611 | publicaciones                |           2 |
 | 2399420 | tecnolecto-marinero          |           2 |
 |  226144 | uned                         |           2 |
 | 1939471 | universidad-del-pacifico     |           2 |
 |  955714 | vocabulario                  |           2 |
 +---------+------------------------------+-------------+

 desc wp_2635_terms ;
 +------------+---------------------+------+-----+---------+----------------+
 | Field      | Type                | Null | Key | Default | Extra
 |
 +------------+---------------------+------+-----+---------+----------------+
 | term_id    | bigint(20) unsigned | NO   | PRI | NULL    | auto_increment
 |
 | name       | varchar(200)        | NO   | MUL |         |
 |
 | slug       | varchar(200)        | NO   | MUL |         |
 |
 | term_group | bigint(10)          | NO   |     | 0       |
 |
 +------------+---------------------+------+-----+---------+----------------+
 4 rows in set (0.01 sec)

 desc wp_2635_term_taxonomy ;
 +------------------+---------------------+------+-----+---------+----------------+
 | Field            | Type                | Null | Key | Default | Extra
 |
 +------------------+---------------------+------+-----+---------+----------------+
 | term_taxonomy_id | bigint(20) unsigned | NO   | PRI | NULL    |
 auto_increment |
 | term_id          | bigint(20) unsigned | NO   | MUL | 0       |
 |
 | taxonomy         | varchar(32)         | NO   | MUL |         |
 |
 | description      | longtext            | NO   |     | NULL    |
 |
 | parent           | bigint(20) unsigned | NO   |     | 0       |
 |
 | count            | bigint(20)          | NO   |     | 0       |
 |
 +------------------+---------------------+------+-----+---------+----------------+

 show create table  wp_2635_terms \G
 *************************** 1. row ***************************
        Table: wp_2635_terms
 Create Table: CREATE TABLE `wp_2635_terms` (
   `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
   `name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
   `slug` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
   `term_group` bigint(10) NOT NULL DEFAULT '0',
   PRIMARY KEY (`term_id`),
   KEY `slug` (`slug`(191)),
   KEY `name` (`name`(191))
 ) ENGINE=InnoDB AUTO_INCREMENT=2454306 DEFAULT CHARSET=utf8mb4
 COLLATE=utf8mb4_unicode_ci
 1 row in set (0.00 sec)


 show create table  wp_2635_term_taxonomy \G
 *************************** 1. row ***************************
        Table: wp_2635_term_taxonomy
 Create Table: CREATE TABLE `wp_2635_term_taxonomy` (
   `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
   `term_id` bigint(20) unsigned NOT NULL DEFAULT '0',
   `taxonomy` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
   `description` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
   `parent` bigint(20) unsigned NOT NULL DEFAULT '0',
   `count` bigint(20) NOT NULL DEFAULT '0',
   PRIMARY KEY (`term_taxonomy_id`),
   UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`),
   KEY `taxonomy` (`taxonomy`)
 ) ENGINE=InnoDB AUTO_INCREMENT=462 DEFAULT CHARSET=utf8mb4
 COLLATE=utf8mb4_unicode_ci
 1 row in set (0.00 sec)

 }}}


 If i delete (via MySQL delete statement) the post_tag with the term_id
 4092, i can edit again the category. I had trouble reproducing the bug or
 to simply to identify the cause of the problem.

 We're running a WordPress Network with ~5000blogs, i've identified this
 problem on 1300 sites.
 We work with MySQL "classic replication" (master / slave), we already had
 a master x3 configuration with Galera Cluster. This can be an interesting
 element.

 I remain available for aby further information.

--

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

From noreply at wordpress.org  Mon Mar  7 22:14:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 22:14:09 -0000
Subject: [wp-trac] [WordPress Trac] #52423: Editing a category or a tag,
 and getting error message "You need a higher level of permission.
 Sorry, you are not allowed to edit this item."
In-Reply-To: <054.830e4883156008ed2da3c0ae50db1854@wordpress.org>
References: <054.830e4883156008ed2da3c0ae50db1854@wordpress.org>
Message-ID: <069.3af9a24e57521c2ef76533280623b227@wordpress.org>

#52423: Editing a category or a tag, and getting error message "You need a higher
level of permission. Sorry, you are not allowed to edit this item."
--------------------------+-----------------------
 Reporter:  webtechIMT    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Taxonomy      |     Version:  5.6
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Description changed by SergeyBiryukov:

Old description:

> I'm using WordPress multi-sites and in one of the 300 sites when I want
> to edit a category or a tag, I get error message "You need a higher level
> of permission. Sorry, you are not allowed to edit this item."
>

> As I saw in the bug [https://core.trac.wordpress.org/ticket/46297], I
> used the plugin wp-find-shared-terms (https://github.com/jjeaton/wp-find-
> shared-terms) and click "Split shared items" button, but it splits none :
>
>     Splitting all shared terms
>     Process complete!
>     Processed: 42
>     Split: 0
>     Skipped: 42
>     Errors: 0
>
> And the bug remains when I want to edit a category (I get the error
> message "You need a higher level of permission. Sorry, you are not
> allowed to edit this item.").

New description:

 I'm using WordPress multi-sites and in one of the 300 sites when I want to
 edit a category or a tag, I get error message "You need a higher level of
 permission. Sorry, you are not allowed to edit this item."


 As I saw in the bug #46297, I used the plugin wp-find-shared-terms
 (https://github.com/jjeaton/wp-find-shared-terms) and click "Split shared
 items" button, but it splits none :

     Splitting all shared terms
     Process complete!
     Processed: 42
     Split: 0
     Skipped: 42
     Errors: 0

 And the bug remains when I want to edit a category (I get the error
 message "You need a higher level of permission. Sorry, you are not allowed
 to edit this item.").

--

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

From noreply at wordpress.org  Mon Mar  7 22:32:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 22:32:54 -0000
Subject: [wp-trac] [WordPress Trac] #55331: Blocks for video platforms as
 Bilibili.com and Nicovideo.jp
Message-ID: <055.50d93a7a7ff2849614c24004c1a965d3@wordpress.org>

#55331: Blocks for video platforms as Bilibili.com and Nicovideo.jp
--------------------------+-----------------------------
 Reporter:  jordiparera   |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 It would be great to add Gutenberg specific blocks for video sharing on
 WordPress (as now with YouTube and Vimeo) for video platforms like
 Bilibili (www.bilibili.com) and Nico (www.nicovideo.jp).

 Do you think that would be possible?

 Thank you!

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

From noreply at wordpress.org  Mon Mar  7 22:50:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 22:50:36 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.2351235effa3435cd7954de4767e686d@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note commit                                    |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

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


Comment:

 In [changeset:"52829" 52829]:
 {{{
 #!CommitTicketReference repository="" revision="52829"
 Media: Allow `wp_check_filetype()` to support query strings in URLs.

 This changeset adjusts the regex in `wp_check_filetype()` to support query
 strings in URLs.

 Follow-up to [30640], [32172].

 Props voldemortensen, johnbillion, layotte, dd32, atomicjack,
 supercleanse, spencercameron, ianmjones, audrasjb.
 Fixes #30377.
 }}}

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

From noreply at wordpress.org  Mon Mar  7 22:56:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 22:56:11 -0000
Subject: [wp-trac] [WordPress Trac] #55332: problem with quick comment
 discarded changes
Message-ID: <058.2f7bdc1f4e323213023eacb06be99d1d@wordpress.org>

#55332: problem with quick comment discarded changes
-------------------------------+-----------------------------
 Reporter:  LinuxArchitect     |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Posts, Post Types  |    Version:  5.9.1
 Severity:  minor              |   Keywords:
  Focuses:  javascript         |
-------------------------------+-----------------------------
 The function discardCommentChanges in js/edit-comments.js does not seem to
 be working as intended. When using the quick comment editor, the function
 is called when an edit is started, and it does nothing at that point as
 expected. But if you click away from the form, nothing stops you and you
 lose your comment changes.

 On the other hand, if a plugin enqueues edit-comment.js, buddyboss-
 platform does (I don't know how/why), and you are editing a post (my
 attached example is an event venue), the function is triggered on update.
 With no comments involved, the original content is an empty string and the
 editied comment is undefined and that triggers the popup warning that
 changes might be lost.

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

From noreply at wordpress.org  Mon Mar  7 22:57:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 22:57:10 -0000
Subject: [wp-trac] [WordPress Trac] #55332: problem with quick comment
 discarded changes
In-Reply-To: <058.2f7bdc1f4e323213023eacb06be99d1d@wordpress.org>
References: <058.2f7bdc1f4e323213023eacb06be99d1d@wordpress.org>
Message-ID: <073.9a1b1b75f4aef52c383fa704452d6f4d@wordpress.org>

#55332: problem with quick comment discarded changes
-------------------------------+------------------------------
 Reporter:  LinuxArchitect     |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:  5.9.1
 Severity:  minor              |  Resolution:
 Keywords:                     |     Focuses:  javascript
-------------------------------+------------------------------
Changes (by LinuxArchitect):

 * Attachment "quick comment error.png" added.

 screenshot of popup warning while editing a post type unrelated to
 comments

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

From noreply at wordpress.org  Mon Mar  7 22:58:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 22:58:50 -0000
Subject: [wp-trac] [WordPress Trac] #55332: problem with quick comment
 discarded changes
In-Reply-To: <058.2f7bdc1f4e323213023eacb06be99d1d@wordpress.org>
References: <058.2f7bdc1f4e323213023eacb06be99d1d@wordpress.org>
Message-ID: <073.41d45c28b26e5ffb6b9746b092dc90d4@wordpress.org>

#55332: problem with quick comment discarded changes
-------------------------------+------------------------------
 Reporter:  LinuxArchitect     |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:  5.9.1
 Severity:  minor              |  Resolution:
 Keywords:                     |     Focuses:  javascript
-------------------------------+------------------------------
Changes (by LinuxArchitect):

 * Attachment "edit-comments.js.patch" added.

 a quick hack patch that prevents the popup when not editing comments

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

From noreply at wordpress.org  Mon Mar  7 23:57:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 07 Mar 2022 23:57:05 -0000
Subject: [wp-trac] [WordPress Trac] #55290: Not all image edits are
 applied to all subsizes
In-Reply-To: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
References: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
Message-ID: <065.160febf3cb8d51539c1fcd7a0c86b951@wordpress.org>

#55290: Not all image edits are applied to all subsizes
--------------------------+------------------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  administration, performance
--------------------------+------------------------------------------
Changes (by mitogh):

 * Attachment "image-edits.patch" added.


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

From noreply at wordpress.org  Tue Mar  8 00:02:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 00:02:27 -0000
Subject: [wp-trac] [WordPress Trac] #55290: Not all image edits are
 applied to all subsizes
In-Reply-To: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
References: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
Message-ID: <065.d8b240c147d61f7c4902cacc9167573a@wordpress.org>

#55290: Not all image edits are applied to all subsizes
--------------------------+------------------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  administration, performance
--------------------------+------------------------------------------
Changes (by mitogh):

 * keywords:  needs-patch => has-patch


Comment:

 I've added a patch with a suggested fix. The suggested fix follows the
 same approach as WordPress follows when the image is uploaded for the
 first time, this approach is basically that when an uploaded image is
 smaller in dimensions than an image size the image size is not created for
 the image, which was the case for this image when the image Was rotated it
 was smaller in dimensions that the failed size creating an error and not
 saving the edit.

 As described this approach would not save any image that was errored out
 by the editors, images would remain in the backup sizes and can be
 restored at any point in time, by rolling back an existing size.

 The function `wp_get_additional_image_sizes` was replaced with
 `wp_get_registered_image_subsizes`  in order to have a more accurate
 access to the defined image sizes by the user.

 Cast of values to `int` was introduced as well in order to make sure
 settings (as strings) were converted to integers.

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

From noreply at wordpress.org  Tue Mar  8 00:30:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 00:30:23 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.3a625060fa4e20877bdd91f64ef418d5@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note commit                                    |
-------------------------------------------------+-------------------------
Changes (by dd32):

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


Comment:

 @audrasjb Unfortunately this causes a PHP Fatal error for `ms-files.php`:

 {{{
 Uncaught Error: Call to undefined function strip_fragment_from_url() in
 wp-includes/functions.php:3009
 Stack trace:
 #0 wp-includes/ms-files.php(32): wp_check_filetype('wp-include...')
 #1 {main}
  thrown

 Source: GET https://make.wordpress.org/core/files/2022/01/list-view-
 keyboard-focus-1.mp4
 Timestamp: Tue, 08 Mar 2022 00:28:30 +0000 (1646699310)
 File: wp-includes/functions.php
 Line: 3009
 }}}

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

From noreply at wordpress.org  Tue Mar  8 00:47:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 00:47:57 -0000
Subject: [wp-trac] [WordPress Trac] #55290: Not all image edits are
 applied to all subsizes
In-Reply-To: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
References: <050.be681f53cfaf80199513d03ac9b6588a@wordpress.org>
Message-ID: <065.f7b846094d93900f2a79e20a8392fc0b@wordpress.org>

#55290: Not all image edits are applied to all subsizes
--------------------------+------------------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Media         |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  administration, performance
--------------------------+------------------------------------------
Changes (by SergeyBiryukov):

 * milestone:  Future Release => 6.0


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

From noreply at wordpress.org  Tue Mar  8 00:49:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 00:49:34 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.aa9f7b0be44fb8fd02c56e286e18a822@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests needs-dev-note commit => has-unit-
     tests needs-dev-note needs-patch


Comment:

 I am being a little tedious to keep the milestone report keywords clean.

 I think we'd need e2e tests to test this use case as I don't think
 phpunit's ms-files tests use `SHORTINIT`.

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

From noreply at wordpress.org  Tue Mar  8 00:56:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 00:56:21 -0000
Subject: [wp-trac] [WordPress Trac] #55333: PHP Notice in
 strip_fragment_from_url() when schemeless URI is passed
Message-ID: <048.25aa8f86a7de9a1a0f3e9340346a5763@wordpress.org>

#55333: PHP Notice in strip_fragment_from_url() when schemeless URI is passed
--------------------------+-----------------------------
 Reporter:  dd32          |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Canonical     |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Related to [52829] is this PHP Notice that seems to be triggering on a
 `the_content` filter after that change:

 {{{
 GET https://wordpress.org/news/2014/04/smith/

 E_NOTICE: Undefined index: scheme in wp-includes/canonical.php:854
 Undefined index: scheme
 }}}

 The input in this case is a URL such as
 `//wordpress.org/news/files/2014/04/widgets.mp4`.

 I also note that `strip_fragment_from_url()` doesn't use `wp_parse_url()`
 but uses `parse_url()` directly.

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

From noreply at wordpress.org  Tue Mar  8 00:58:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 00:58:22 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.2adea71fe5f2ae92877d1766743df591@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------

Comment (by dd32):

 #55333 is a php notice that this change started triggering on
 WordPress.org, but is 'unrelated'.

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

From noreply at wordpress.org  Tue Mar  8 01:15:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 01:15:03 -0000
Subject: [wp-trac] [WordPress Trac] #55288: Site Editor on 5.9.1 fails
 to find homepage template for FSE themes, on WP subdirectory installation
In-Reply-To: <055.066d0ca728e3fb5959c659d12bba3c2b@wordpress.org>
References: <055.066d0ca728e3fb5959c659d12bba3c2b@wordpress.org>
Message-ID: <070.a27885c697d1d39f7009cb6d8cf57f6f@wordpress.org>

#55288: Site Editor on 5.9.1 fails to find homepage template for FSE themes, on WP
subdirectory installation
--------------------------+---------------------------------------
 Reporter:  andronocean   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:  administration, template
--------------------------+---------------------------------------
Changes (by Enchiridion):

 * severity:  major => critical


Comment:

 I'm also getting this error.  My stack trace is a little different,
 probably because I'm using Firefox.  Like others in the linked forum
 thread, I'm using WordPress in a subdirectory.  What's odd is both 5.9 and
 5.9.1 make an XHR request to `/wp?_wp-find-template=true`, which 404s but
 also returns the requested JSON data.  Seems only 5.9.1 actually fails
 because of this.

 On 5.9.1 I can't edit any templates the site editor just crashes unless I
 have an direct link to the template to edit `/wp/wp-admin/site-
 editor.php?postId=site%2F%2F404&postType=wp_template`

 I've had to roll back to 5.9 in order to keep site dev going.

 Error from the Copy Error button:
 {{{
 IqXm/zr/r<@https://example.com/wp/wp-includes/js/dist/edit-
 site.min.js?ver=403e01f2b098b6a656118a51787581cb:2:121078
 promise callback*IqXm/zr/t<@https://example.com/wp/wp-includes/js/dist
 /edit-site.min.js?ver=403e01f2b098b6a656118a51787581cb:2:121054
 async*zr at https://example.com/wp/wp-includes/js/dist/edit-
 site.min.js?ver=403e01f2b098b6a656118a51787581cb:2:121424
 qr at https://example.com/wp/wp-includes/js/dist/edit-
 site.min.js?ver=403e01f2b098b6a656118a51787581cb:2:121896
 $r at https://example.com/wp/wp-includes/js/dist/edit-
 site.min.js?ver=403e01f2b098b6a656118a51787581cb:2:122936
 @https://example.com/wp/wp-admin/site-editor.php:2201:16
 EventListener.handleEvent*r at https://example.com/wp/wp-includes/js/dist
 /dom-ready.min.js?ver=ecda74de0221e1c2ce5c57cbb5af09d5:2:1121
 @https://example.com/wp/wp-admin/site-editor.php:2200:4

 }}}

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

From noreply at wordpress.org  Tue Mar  8 01:31:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 01:31:01 -0000
Subject: [wp-trac] [WordPress Trac] #22176: Cache the results of the
 posts_request_ids query
In-Reply-To: <048.5df67ddca93554b06d2a0f4b237307c0@wordpress.org>
References: <048.5df67ddca93554b06d2a0f4b237307c0@wordpress.org>
Message-ID: <063.0acf92801ad6b6a44e3502e365d3f713@wordpress.org>

#22176: Cache the results of the posts_request_ids query
-------------------------------------------------+-------------------------
 Reporter:  ryan                                 |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Query                                |     Version:  3.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch 2nd-opinion has-unit-      |     Focuses:
  tests early                                    |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch 2nd-opinion has-unit-tests => has-patch 2nd-opinion
     has-unit-tests early


Comment:

 This sprung to mind as there are a few ''add caching to some post
 function'' tickets that would be covered by this.

 I've put the early keyword on it as it involves both caching and Query.

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

From noreply at wordpress.org  Tue Mar  8 01:43:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 01:43:48 -0000
Subject: [wp-trac] [WordPress Trac] #48222: "Show password" button
 overlaps with the LastPass icon
In-Reply-To: <058.0d699b3273d056c061d95a9b99cee6c0@wordpress.org>
References: <058.0d699b3273d056c061d95a9b99cee6c0@wordpress.org>
Message-ID: <073.2dd480c8a09086c272deffc949b7aaf3@wordpress.org>

#48222: "Show password" button overlaps with the LastPass icon
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:
                                                 |  sabernhardt
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Login and Registration               |     Version:  5.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch needs-     |     Focuses:  ui
  design-feedback needs-testing early            |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * Attachment "48222.10.diff" added.


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

From noreply at wordpress.org  Tue Mar  8 01:47:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 01:47:16 -0000
Subject: [wp-trac] [WordPress Trac] #48222: "Show password" button
 overlaps with the LastPass icon
In-Reply-To: <058.0d699b3273d056c061d95a9b99cee6c0@wordpress.org>
References: <058.0d699b3273d056c061d95a9b99cee6c0@wordpress.org>
Message-ID: <073.6ef8c0dc00f91fa5a3bff0f4c4d6f7db@wordpress.org>

#48222: "Show password" button overlaps with the LastPass icon
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:
                                                 |  sabernhardt
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Login and Registration               |     Version:  5.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch needs-     |     Focuses:  ui
  design-feedback needs-testing early            |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 [attachment:"48222.10.diff"] is [attachment:"48222.9.diff"] but refreshed
 against trunk to remove offsets, clean up line ending types.

 @sabernhardt do you need anything other than design feedback to take this
 forward?

 While testing, the screenshots @poena uploaded a few months ago appear to
 still be representative.

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

From noreply at wordpress.org  Tue Mar  8 03:21:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 03:21:43 -0000
Subject: [wp-trac] [WordPress Trac] #44591: PHP notice if optional
 argument isn't passed to map_meta_cap()
In-Reply-To: <056.313e6e825d638ddee4053b7cd5f8819f@wordpress.org>
References: <056.313e6e825d638ddee4053b7cd5f8819f@wordpress.org>
Message-ID: <071.342bb0f75eb95b951b98da5761a28ffc@wordpress.org>

#44591: PHP notice if optional argument isn't passed to map_meta_cap()
--------------------------------------+-----------------------------
 Reporter:  henry.wright              |       Owner:  SergeyBiryukov
     Type:  defect (bug)              |      Status:  accepted
 Priority:  normal                    |   Milestone:  6.0
Component:  Users                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------------

Comment (by peterwilsoncc):

 In the [https://github.com/WordPress/wordpress-develop/pull/2386 linked
 pull request]:

 [attachment:"44591-3.diff"] with the following changes:
 * version updated to 6.0.0
 * removed escaping of translations, core trusts translations
 * added unit tests to ensure the affected caps contain `do_not_allow` and
 throw a doing it wrong
 * fixed `test_taxonomy_meta_capabilities_with_non_existent_terms` to
 expect the error

 > I'll just suggest that as the guard's code is repetitive if we can wrap
 it into a function to respect DRY principe it will be good.

 @azouamauriac you're right, it's repetitious. For now I think it's fine to
 keep the repetition rather than set up a specific function to wrap
 `_doing_it_wrong()`. It's a borderline call, so please feel free to push
 back on this if you wish.

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

From noreply at wordpress.org  Tue Mar  8 03:42:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 03:42:26 -0000
Subject: [wp-trac] [WordPress Trac] #55334: Attempt to read property
 "term_id" on null in "mywordpress/wp-includes/deprecated.php" on line 87
Message-ID: <051.d11fddf68aaa8c704930464151e2973a@wordpress.org>

#55334: Attempt to read property "term_id" on null in "mywordpress/wp-
includes/deprecated.php" on line 87
--------------------------+-----------------------------
 Reporter:  bcue015       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.1
 Severity:  minor         |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Title says it all. Error occurs whenever I uploaded "guppy.jpg" image. And
 I have a Guppy Categories with guppy slug. I also have a category-
 guppy.php in my template file. And heres the line 87 pointing out
 [[Image(https://i.ibb.co/K5Nmvy3/line87.png)]]

 And the result whenever I went to my guppy category link is this
 [[Image(https://i.ibb.co/LQfZ71Q/Untitled.png)]]

 It'll try to pull in my single.php cause thats what my single.php looks
 like.
 And I had no idea why the error was in my metabox so I'll just have to
 show you the code anyway. Here it is
 [[Image(https://i.ibb.co/XtyqQtx/theline.png)]]

 I think categories had something to do with this. And by the way Im using
 the latest wordpress 5.9.1 version with the following updated and
 activated plugins:
 Advanced Custom Fields
 All-in-One WP Migration
 Crop Thumbnails
 Regenerate Thumbnails
 Manual Image Crop
 WP Migrate DB

 I already resolve this by changing the name of my image as long as it is
 not guppy. You can close this ticket cause I just want to let you guys
 know.

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

From noreply at wordpress.org  Tue Mar  8 03:54:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 03:54:39 -0000
Subject: [wp-trac] [WordPress Trac] #43706: Email with link to change
 admin email does not include proposed new email address.
In-Reply-To: <051.e8674074507faa5f4788d57d47e5a1c5@wordpress.org>
References: <051.e8674074507faa5f4788d57d47e5a1c5@wordpress.org>
Message-ID: <066.14f4d3ec1c571294212b7f2c1a8823ac@wordpress.org>

#43706: Email with link to change admin email does not include proposed new email
address.
-------------------------------------------------+-------------------------
 Reporter:  sshanky                              |       Owner:
                                                 |  SergeyBiryukov
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Users                                |     Version:  4.9.5
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch needs-      |     Focuses:
  refresh                                        |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  good-first-bug has-patch => good-first-bug has-patch needs-
     refresh


Comment:

 Thanks for the patch @tremidkhar!

 While changing the `###EMAIL###` placeholder to `###NEW_EMAIL###` makes
 sense, you'll need to include a little bit of work to make sure that the
 code doesn't break for developers using the `new_admin_email_content`
 filter.

 I suggest `###EMAIL###` be considered deprecated in favour of
 `###NEW_EMAIL###`.

 Immediately following the filter a new line of code can be added to
 replace the old with the new, for example:

 {{{#!php
 <?php
 $content = apply_filters( 'new_admin_email_content', $email_text,
 $new_admin_email );
 // EMAIL placeholder has been deprecated in favour of NEW_EMAIL
 placeholder.
 $content = str_replace( '###EMAIL###', '###NEW_EMAIL###', $content );
 }}}

 @SergeyBiryukov @audrasjb @johnbillion  Do you know if a placeholder like
 this has been deprecated in the past? I'm wondering what to do with regard
 to throwing a warning. There doesn't seem to be an appropriate
 `_deprectated_*()` function.

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

From noreply at wordpress.org  Tue Mar  8 03:56:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 03:56:54 -0000
Subject: [wp-trac] [WordPress Trac] #55335: $user_login double escaped with
 incorrect/empty password in wp-login.php
Message-ID: <059.17cf1f26b07863758356afb40a2d904d@wordpress.org>

#55335: $user_login double escaped with incorrect/empty password in wp-login.php
------------------------------------+-----------------------------
 Reporter:  johnjamesjacoby         |      Owner:  (none)
     Type:  defect (bug)            |     Status:  new
 Priority:  normal                  |  Milestone:  Awaiting Review
Component:  Login and Registration  |    Version:
 Severity:  normal                  |   Keywords:
  Focuses:                          |
------------------------------------+-----------------------------
 First:

 {{{

                 if ( isset( $_POST['log'] ) ) {
                         $user_login = ( 'incorrect_password' ===
 $errors->get_error_code() || 'empty_password' ===
 $errors->get_error_code() ) ? esc_attr( wp_unslash( $_POST['log'] ) ) :
 '';
                 }

 }}}

 Then:
 {{{
 <input type="text" name="log" id="user_login"<?php echo
 $aria_describedby_error; ?> class="input" value="<?php echo esc_attr(
 $user_login ); ?>" size="20" autocapitalize="off" />
 }}}

 Fix is to late escape only, and remove the top one.

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

From noreply at wordpress.org  Tue Mar  8 04:00:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 04:00:35 -0000
Subject: [wp-trac] [WordPress Trac] #55335: $user_login double escaped
 with incorrect/empty password in wp-login.php
In-Reply-To: <059.17cf1f26b07863758356afb40a2d904d@wordpress.org>
References: <059.17cf1f26b07863758356afb40a2d904d@wordpress.org>
Message-ID: <074.1d7d14cfb831e9a7a6a373a59b0448d8@wordpress.org>

#55335: $user_login double escaped with incorrect/empty password in wp-login.php
------------------------------------+------------------------------
 Reporter:  johnjamesjacoby         |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Login and Registration  |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:                          |     Focuses:
------------------------------------+------------------------------

Comment (by johnjamesjacoby):

 Relatedly, `'register'` action is double `wp_unslash()`ing `$user_email`
 and `$user_login`.

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

From noreply at wordpress.org  Tue Mar  8 04:21:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 04:21:10 -0000
Subject: [wp-trac] [WordPress Trac] #55162: Incorrect parameter passed
 to update_term_cache from _prime_term_caches
In-Reply-To: <055.1c067dc2bc1f79347ffb1d64d38e4564@wordpress.org>
References: <055.1c067dc2bc1f79347ffb1d64d38e4564@wordpress.org>
Message-ID: <070.baa60409c8114c32ae3935a8c4925151@wordpress.org>

#55162: Incorrect parameter passed to update_term_cache from _prime_term_caches
-----------------------------------+---------------------
 Reporter:  david.binda            |       Owner:  (none)
     Type:  defect (bug)           |      Status:  new
 Priority:  normal                 |   Milestone:  6.0
Component:  Taxonomy               |     Version:  4.6
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch 2nd-opinion  |     Focuses:
-----------------------------------+---------------------

Comment (by peterwilsoncc):

 Replying to [comment:2 azouamauriac]:
 > Also it seems like ''_prime_term_caches'' is the only function which
 uses ''update_term_cache'' with the second parameter, so I think we can
 remove safely its second parameter "$taxonomy" in
 > ''update_term_cache''.

 WordPress tends to keep the deprecated parameters listed to future proof
 against any upcoming changes:

 `fn( $string, $object, $array )` might have the final argument deprecated
 `fn( $string, $object, $deprecated )`. The deprecated parameter needs to
 be keep as a placeholder in case a new parameter is added at a later date,
 eg `fn( $string, $object, $deprecated, $boolean )`

 There's a little judgement involved each time.

 However, it doesn't look like the `$taxonomy` argument was formally
 deprecated in `update_term_cache()` so perhaps you could look at that on
 another ticket.

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

From noreply at wordpress.org  Tue Mar  8 04:23:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 04:23:48 -0000
Subject: [wp-trac] [WordPress Trac] #55162: Incorrect parameter passed
 to update_term_cache from _prime_term_caches
In-Reply-To: <055.1c067dc2bc1f79347ffb1d64d38e4564@wordpress.org>
References: <055.1c067dc2bc1f79347ffb1d64d38e4564@wordpress.org>
Message-ID: <070.0be4433ff53975234f57c2769f785203@wordpress.org>

#55162: Incorrect parameter passed to update_term_cache from _prime_term_caches
-----------------------------------+----------------------------
 Reporter:  david.binda            |       Owner:  peterwilsoncc
     Type:  defect (bug)           |      Status:  closed
 Priority:  normal                 |   Milestone:  6.0
Component:  Taxonomy               |     Version:  4.6
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  has-patch 2nd-opinion  |     Focuses:
-----------------------------------+----------------------------
Changes (by peterwilsoncc):

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


Comment:

 In [changeset:"52830" 52830]:
 {{{
 #!CommitTicketReference repository="" revision="52830"
 Taxonomy: Improve code quality within `_prime_term_caches()`.

 Remove the second parameter on the call to `update_term_cache()` from
 within the function `_prime_term_caches()`. The since deprecated parameter
 of the former was at one point a string, never a boolean.

 Props david.binda, SergeyBiryukov, azouamauriac.
 Fixes #55162.
 }}}

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

From noreply at wordpress.org  Tue Mar  8 05:57:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 05:57:09 -0000
Subject: [wp-trac] [WordPress Trac] #55207: WP_Query returns published
 sticky posts when post_status is set to draft
In-Reply-To: <052.c676576c2767ef4d8d1a735f953c8fae@wordpress.org>
References: <052.c676576c2767ef4d8d1a735f953c8fae@wordpress.org>
Message-ID: <067.eb2b6c363fcd6df6269549f3e2f3a0a8@wordpress.org>

#55207: WP_Query returns published sticky posts when post_status is set to draft
--------------------------+---------------------
 Reporter:  NomNom99      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Query         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  early         |     Focuses:
--------------------------+---------------------
Changes (by peterwilsoncc):

 * keywords:   => early
 * version:  5.9 =>
 * milestone:  Awaiting Review => 6.0


Comment:

 Replying to [comment:2 azouamauriac]:
 > After some search, the code was introduced here [8546]/#7457, originally
 called ''caller_get_posts'' and renamed ''ignore_sticky_posts'' here
 [15589]/#14624

 Thanks for digging in to the history.

 The version tag applies to when the bug was introduced, as it looks like
 this bug has been around prior to WP 5.9 I'll remove the version and
 update it once I have done some additional checking.

 Moving on to the 6.0 milestone for visibility. As this involves the
 `WP_Query` class, I've also added the early keyword so any bug fix can be
 well tested prior to release.

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

From noreply at wordpress.org  Tue Mar  8 06:49:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 06:49:38 -0000
Subject: [wp-trac] [WordPress Trac] #55330: Set
 global_styles_svg_filters transient to return true causing symbol `1` to be
 appeared on the screen in a production mode
In-Reply-To: <060.aaacdb7d2decfa020f9284bbed451de7@wordpress.org>
References: <060.aaacdb7d2decfa020f9284bbed451de7@wordpress.org>
Message-ID: <075.60d77640ce9b2292af553dcc251b361f@wordpress.org>

#55330: Set global_styles_svg_filters transient to return true causing symbol `1`
to be appeared on the screen in a production mode
------------------------------+------------------------------
 Reporter:  aliakseyenkaihar  |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  General           |     Version:  5.9.1
 Severity:  trivial           |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by aliakseyenkaihar):

 Hey @vijayhardaha

 I'm actually need anything but false to satisfy `false !== $pre`
 condition. See [here](https://github.com/WordPress/WordPress/blob/master
 /wp-includes/option.php#L847). I tested with null - `1` is NOT appearing
 but the call to update transient is present - and my personal goal is to
 prevent it

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

From noreply at wordpress.org  Tue Mar  8 07:19:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 07:19:09 -0000
Subject: [wp-trac] [WordPress Trac] #55207: WP_Query returns published
 sticky posts when post_status is set to draft
In-Reply-To: <052.c676576c2767ef4d8d1a735f953c8fae@wordpress.org>
References: <052.c676576c2767ef4d8d1a735f953c8fae@wordpress.org>
Message-ID: <067.bffd4989de683cea7244d6ce46dd7cc3@wordpress.org>

#55207: WP_Query returns published sticky posts when post_status is set to draft
--------------------------+---------------------
 Reporter:  NomNom99      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Query         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  early         |     Focuses:
--------------------------+---------------------

Comment (by NomNom99):

 Thanks @peterwilsoncc

 I created a patch. It doesn't have any tests for now, figured it'll be
 better to move ahead once the issue is confirmed.

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

From noreply at wordpress.org  Tue Mar  8 07:19:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 07:19:42 -0000
Subject: [wp-trac] [WordPress Trac] #55207: WP_Query returns published
 sticky posts when post_status is set to draft
In-Reply-To: <052.c676576c2767ef4d8d1a735f953c8fae@wordpress.org>
References: <052.c676576c2767ef4d8d1a735f953c8fae@wordpress.org>
Message-ID: <067.a7f1d287bb0d8e283ed9c43ebdeb2394@wordpress.org>

#55207: WP_Query returns published sticky posts when post_status is set to draft
--------------------------+---------------------
 Reporter:  NomNom99      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Query         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  early         |     Focuses:
--------------------------+---------------------
Changes (by NomNom99):

 * Attachment "patch-1.diff" added.


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

From noreply at wordpress.org  Tue Mar  8 09:18:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 09:18:23 -0000
Subject: [wp-trac] [WordPress Trac] #55336: Query strings with reserved
 characters get wrongly redirected to encoded variant at the root level.
Message-ID: <053.11d5ce4bde2445cb0e260ad0a7f506a9@wordpress.org>

#55336: Query strings with reserved characters get wrongly redirected to encoded
variant at the root level.
--------------------------+-----------------------------
 Reporter:  madstegge     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 The asterisk ("*", ASCII 2A hex) and exclamation mark ("!" , ASCII 21 hex)
 are reserved for use as having special significance within specific
 schemes. Source:
 https://www.w3.org/Addressing/URL/4_URI_Recommentations.html

 More here: https://developers.google.com/maps/url-encoding

 WordPress however, redirects to a URI encoded variant when the query
 string at the root level contains these reserved characters.

 So, https://wordpress.org/plugins/?test=123*456 doesn't redirect.

 While https://wordpress.org/?test=123*456 redirects to
 https://wordpress.org/?test=123%2A456.

 This is quite problematic for all WordPress sites that use for example
 Google Analytics 4 (GA4) cross-domain tracking. GA4 relies on a query
 string containing asterisks. Source:
 https://support.google.com/analytics/answer/10071811?hl=en

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

From noreply at wordpress.org  Tue Mar  8 10:17:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 10:17:36 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.c9d4438b74b4858d0353c8c4d0eef36e@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 @dd32 I'm trying to reproduce the issue but I'm struggling a bit with ms-
 files.php, it's pretty hard to reproduce on a new install. Do you have an
 easy to reproduce use case (I mean outside w.org)?

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

From noreply at wordpress.org  Tue Mar  8 10:49:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 10:49:43 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for post
 and site editors
Message-ID: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>

#55337: Optimize preload paths for post and site editors
--------------------------+-----------------------------
 Reporter:  jsnajdr       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Editor        |    Version:  trunk
 Severity:  normal        |   Keywords:  has-patch
  Focuses:                |
--------------------------+-----------------------------
 The preloaded REST responses (api-fetch preloading middleware) are a bit
 out of sync with the real requests that the post and site editors are
 sending, and they should be optimized them. See the description of the
 attached PR, and also of this Gutenberg PR
 (https://github.com/WordPress/gutenberg/pull/39256), for more details.

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

From noreply at wordpress.org  Tue Mar  8 10:50:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 10:50:26 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Invalid use of display and float
 together in style.css file
Message-ID: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>

#55338: Invalid use of display and float together in style.css file
-------------------------+-----------------------------
 Reporter:  kajalgohel   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Themes       |    Version:
 Severity:  normal       |   Keywords:  needs-patch
  Focuses:               |
-------------------------+-----------------------------
 In the theme Twenty Eleven, there is an invalid use of float and display
 inline-block together in the CSS style sheet.


 {{{
 .indexed.format-image div.entry-meta {
         display: inline-block;
         float: left;
         width: 35%;
 }
 }}}

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

From noreply at wordpress.org  Tue Mar  8 10:53:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 10:53:30 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Invalid use of display and
 float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.077f93ff3263b16651d976a32181b985@wordpress.org>

#55338: Invalid use of display and float together in style.css file
-------------------------+------------------------------
 Reporter:  kajalgohel   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Themes       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+------------------------------
Changes (by kajalgohel):

 * Attachment "#55338.patch" added.

 display: inline-block property is removed.

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

From noreply at wordpress.org  Tue Mar  8 10:54:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 10:54:09 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Invalid use of display and
 float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.51bc15861a48438eb1efce53e7ff690e@wordpress.org>

#55338: Invalid use of display and float together in style.css file
-------------------------------------+------------------------------
 Reporter:  kajalgohel               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Themes                   |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+------------------------------
Changes (by kajalgohel):

 * keywords:  needs-patch => has-patch needs-testing


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

From noreply at wordpress.org  Tue Mar  8 11:36:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 11:36:25 -0000
Subject: [wp-trac] [WordPress Trac] #49412: Store filesize media metadata
In-Reply-To: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
References: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
Message-ID: <063.8a734d88aff9eae8cf59e6057219ac59@wordpress.org>

#49412: Store filesize media metadata
--------------------------------------+-----------------------------
 Reporter:  Cybr                      |       Owner:  spacedmonkey
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  Future Release
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+-----------------------------
Changes (by spacedmonkey):

 * owner:  johnwatkins0 => spacedmonkey


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

From noreply at wordpress.org  Tue Mar  8 11:38:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 11:38:20 -0000
Subject: [wp-trac] [WordPress Trac] #49412: Store filesize media metadata
In-Reply-To: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
References: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
Message-ID: <063.f393101ee3bd37a60d354c215647186d@wordpress.org>

#49412: Store filesize media metadata
--------------------------------------+-----------------------------
 Reporter:  Cybr                      |       Owner:  spacedmonkey
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  Future Release
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+-----------------------------

Comment (by spacedmonkey):

 I spent some time on this ticket today. Updated the patch
 [https://github.com/WordPress/wordpress-develop/pull/2367 #2367]. I think
 the patch is good to merge. I will wait a day for feedback, other, I will
 merged.

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

From noreply at wordpress.org  Tue Mar  8 11:46:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 11:46:59 -0000
Subject: [wp-trac] [WordPress Trac] #49412: Store filesize media metadata
In-Reply-To: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
References: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
Message-ID: <063.f7b3d29bb8ee3e73a54111549330a7f3@wordpress.org>

#49412: Store filesize media metadata
--------------------------------------+---------------------------
 Reporter:  Cybr                      |       Owner:  spacedmonkey
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------
Changes (by spacedmonkey):

 * milestone:  Future Release => 6.0


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

From noreply at wordpress.org  Tue Mar  8 11:54:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 11:54:11 -0000
Subject: [wp-trac] [WordPress Trac] #55339: Date changes to ordered list
 (and default 1. 1.) when at beginning of line
Message-ID: <049.a7717b1de6318d538ffff53fa5cfcb21@wordpress.org>

#55339: Date changes to ordered list (and default 1. 1.) when at beginning of line
--------------------------+-----------------------------
 Reporter:  jhn11         |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Date/Time     |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hi,

 I have found that when I write a date (e.g. "5. dubna 2022" that is 5th of
 April, but in Czech format) at the beginning of line in post that
 WordPress renders it to default 1.1. at frontend.

 Text remains the same at backend but generated post at frontend:
 - changes to 1. 1. 2022
 - and in html code there is ordered list

 When any characters are before the date on that line, nothing changes at
 frontend.

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

From noreply at wordpress.org  Tue Mar  8 11:55:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 11:55:12 -0000
Subject: [wp-trac] [WordPress Trac] #55339: Date changes to ordered list
 (and default 1. 1.) when at beginning of line
In-Reply-To: <049.a7717b1de6318d538ffff53fa5cfcb21@wordpress.org>
References: <049.a7717b1de6318d538ffff53fa5cfcb21@wordpress.org>
Message-ID: <064.f35df198928065060b7b9f3040ca7055@wordpress.org>

#55339: Date changes to ordered list (and default 1. 1.) when at beginning of line
--------------------------+------------------------------
 Reporter:  jhn11         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Date/Time     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by jhn11):

 * Attachment "Screenshot 2022-03-08 at 12-44-55 6x jarní ArcGIS Jak udělat
 mapu hezčí, Map Viewer, hostované vrstvy prvků, instantní appk[...].png"
 added.

 frontend - rendered post

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

From noreply at wordpress.org  Tue Mar  8 11:55:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 11:55:44 -0000
Subject: [wp-trac] [WordPress Trac] #55339: Date changes to ordered list
 (and default 1. 1.) when at beginning of line
In-Reply-To: <049.a7717b1de6318d538ffff53fa5cfcb21@wordpress.org>
References: <049.a7717b1de6318d538ffff53fa5cfcb21@wordpress.org>
Message-ID: <064.443f63b41e8df8f991d12faf93eebb76@wordpress.org>

#55339: Date changes to ordered list (and default 1. 1.) when at beginning of line
--------------------------+------------------------------
 Reporter:  jhn11         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Date/Time     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by jhn11):

 * Attachment "Screenshot 2022-03-08 at 12-45-51 Upravit příspěvek “6x
 jarní ArcGIS Jak udělat mapu hezčí, Map Viewer, hostované vrstvy
 pr[...].png" added.

 backend - text in editor

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

From noreply at wordpress.org  Tue Mar  8 11:56:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 11:56:15 -0000
Subject: [wp-trac] [WordPress Trac] #55339: Date changes to ordered list
 (and default 1. 1.) when at beginning of line
In-Reply-To: <049.a7717b1de6318d538ffff53fa5cfcb21@wordpress.org>
References: <049.a7717b1de6318d538ffff53fa5cfcb21@wordpress.org>
Message-ID: <064.737644b5f6bb00020d619ac5462ab900@wordpress.org>

#55339: Date changes to ordered list (and default 1. 1.) when at beginning of line
--------------------------+------------------------------
 Reporter:  jhn11         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Date/Time     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by jhn11):

 * Attachment "code.jpg" added.

 frontend - html code of post

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

From noreply at wordpress.org  Tue Mar  8 12:25:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 12:25:05 -0000
Subject: [wp-trac] [WordPress Trac] #55162: Incorrect parameter passed
 to update_term_cache from _prime_term_caches
In-Reply-To: <055.1c067dc2bc1f79347ffb1d64d38e4564@wordpress.org>
References: <055.1c067dc2bc1f79347ffb1d64d38e4564@wordpress.org>
Message-ID: <070.af20e55280747b13a2a3066c2e3b00cf@wordpress.org>

#55162: Incorrect parameter passed to update_term_cache from _prime_term_caches
--------------------------+----------------------------
 Reporter:  david.binda   |       Owner:  peterwilsoncc
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  6.0
Component:  Taxonomy      |     Version:  4.6
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |     Focuses:
--------------------------+----------------------------
Changes (by azouamauriac):

 * keywords:  has-patch 2nd-opinion => has-patch


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

From noreply at wordpress.org  Tue Mar  8 13:22:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 13:22:46 -0000
Subject: [wp-trac] [WordPress Trac] #55221: Feature image does not load
 media library in correct view.
In-Reply-To: <053.98376a7f1298436d309ce5717cb6aa0e@wordpress.org>
References: <053.98376a7f1298436d309ce5717cb6aa0e@wordpress.org>
Message-ID: <068.48dab0d662f3193ba34275cb87f22600@wordpress.org>

#55221: Feature image does not load media library in correct view.
---------------------------+------------------------------
 Reporter:  jhall_3rd      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Media          |     Version:  5.8.2
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------
Changes (by hellofromTonya):

 * keywords:   => needs-testing
 * component:  Editor => Media


Comment:

 Hello @jhall_3rd 👋,

 Welcome to WordPress Core's Trac! Thank you for the ticket and providing
 steps to reproduce and a video showing the issue you are reporting - well
 done 👏⭐

 The Test Team is currently testing to attempt to reproduce the reported
 issue. Test Reports will follow.

 I've also adjusted some info in the ticket for better discoverable.

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

From noreply at wordpress.org  Tue Mar  8 13:38:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 13:38:19 -0000
Subject: [wp-trac] [WordPress Trac] #55221: Feature image does not load
 media library in correct view.
In-Reply-To: <053.98376a7f1298436d309ce5717cb6aa0e@wordpress.org>
References: <053.98376a7f1298436d309ce5717cb6aa0e@wordpress.org>
Message-ID: <068.48b3900df753c85aa27c316683082d8d@wordpress.org>

#55221: Feature image does not load media library in correct view.
---------------------------+------------------------------
 Reporter:  jhall_3rd      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Media          |     Version:  5.8.2
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------

Comment (by Boniu91):

 Not able to reproduce it on the newest version.

 == Test Report

 === Env
 * WordPress 5.9.1
 * Chrome 99.0.4844.51
 * Windows 10
 * Theme: Twenty Twenty One

 === Steps to test
 1. Add new post with featured image using Classic Editor
 2. Click on the Featured Image in order to edit it
 3. Correct view with all uploaded media is displayed

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

From noreply at wordpress.org  Tue Mar  8 13:57:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 13:57:49 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.eef1e47c86e5b30ea5552e9313c01d06@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------

Comment (by SergeyBiryukov):

 As noted in comment:10, this was previously attempted in [30640] and
 reverted in [32171] as a security fix for
 [https://wordpress.org/news/2015/04/wordpress-4-1-2/ WordPress 4.1.2]. It
 would be great to confirm with the Security Team that [52829] does not
 reintroduce any issues.

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

From noreply at wordpress.org  Tue Mar  8 14:02:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:02:00 -0000
Subject: [wp-trac] [WordPress Trac] #55271: Featured Image Section
 Disappears In Block Editor
In-Reply-To: <052.3ab4cf29bbac4776757c20c1fed09569@wordpress.org>
References: <052.3ab4cf29bbac4776757c20c1fed09569@wordpress.org>
Message-ID: <067.744fba9e7e1012759638d8051c31ddc8@wordpress.org>

#55271: Featured Image Section Disappears In Block Editor
-------------------------------------------------+-------------------------
 Reporter:  zennie62                             |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing-info reporter-         |     Focuses:
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * keywords:   => needs-testing-info reporter-feedback
 * component:  General => Editor


Comment:

 Hello @zennie62

 Welcome to WordPress Core's Trac. Thank you for the ticket.

 During today's testing session, the Test Team was unable to reproduce the
 reported issue (test report to follow) when using Twenty Twenty-Two theme
 and no plugins activated. The featured image area in the sidebar of the
 `Posts` editor displays with a block theme activated and using 5.9 and
 5.9.1.

 Can you provide step-by-step instructions including the theme and plugins
 you're using? Also a video, gif, and/or screenshots are helpful. The more
 information you can provide, the more this helps testers in their effort
 to reproduce and contributors to diagnose.

 What happens when you deactivate all of the plugins? Does the problem go
 away?

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

From noreply at wordpress.org  Tue Mar  8 14:04:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:04:53 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file (was: Invalid use of
 display and float together in style.css file)
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.84bdf7fc6907ef22f0b181a95ab130f4@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------+---------------------
 Reporter:  kajalgohel               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * component:  Themes => Bundled Theme
 * milestone:  Awaiting Review => 6.0


Comment:

 Hi there, welcome back to WordPress Trac! Thanks for the patch.

 Introduced in [17776] / #17198.

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

From noreply at wordpress.org  Tue Mar  8 14:06:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:06:33 -0000
Subject: [wp-trac] [WordPress Trac] #55244: Non-editable title.
In-Reply-To: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
References: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
Message-ID: <066.3ebf0665130b17142715f5994ad1f1e4@wordpress.org>

#55244: Non-editable title.
--------------------------+----------------------------------------
 Reporter:  krilike       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility, javascript
--------------------------+----------------------------------------

Comment (by juhise):

 Hey @krilike

 Thanks for reporting the issue

 We tried to reproduce this issue on WP 5.9.1 and 5.8.2 but couldn't
 reproduce

 == Test Report

 === Env
 * WordPress 5.8.2 and 5.9.1
 * Chrome 98.0.4758.109
 * macOS Monterey
 * Theme: Twenty Twenty One
 * Gutenberg Editor
 * Plugin: WP Downgrade

 === Steps to test
 1. Opened the post
 2. Clicked on title and press CTRL+A
 3. Was able to edit the title

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

From noreply at wordpress.org  Tue Mar  8 14:09:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:09:36 -0000
Subject: [wp-trac] [WordPress Trac] #55271: Featured Image Section
 Disappears In Block Editor
In-Reply-To: <052.3ab4cf29bbac4776757c20c1fed09569@wordpress.org>
References: <052.3ab4cf29bbac4776757c20c1fed09569@wordpress.org>
Message-ID: <067.dbc96b5b5a4bb0b91962778fbbf6fd69@wordpress.org>

#55271: Featured Image Section Disappears In Block Editor
-------------------------------------------------+-------------------------
 Reporter:  zennie62                             |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing-info reporter-         |     Focuses:
  feedback                                       |
-------------------------------------------------+-------------------------

Comment (by juhise):

 Hey @zennie62

 Thanks for reporting the issue

 We tried to reproduce this issue on WP 5.9.1 and 5.8.2 but couldn't
 reproduce

 == Test Report

 === Env
 * WordPress 5.8.2 and 5.9.1
 * Chrome 98.0.4758.109
 * macOS Monterey
 * Theme: Twenty Twenty One
 * Gutenberg Editor
 * Plugin: WP Downgrade

 === Steps to test
 1. Added the `Post Featured Image` block
 2. Featured image appears as expected


 Screenshot: https://nimb.ws/ANTcas

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

From noreply at wordpress.org  Tue Mar  8 14:16:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:16:16 -0000
Subject: [wp-trac] [WordPress Trac] #55271: Featured Image Section
 Disappears In Block Editor
In-Reply-To: <052.3ab4cf29bbac4776757c20c1fed09569@wordpress.org>
References: <052.3ab4cf29bbac4776757c20c1fed09569@wordpress.org>
Message-ID: <067.a3b7bafaf867cd7ec54cbe8cd998ba2c@wordpress.org>

#55271: Featured Image Section Disappears In Block Editor
-------------------------------------------------+-------------------------
 Reporter:  zennie62                             |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing-info reporter-         |     Focuses:
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * Attachment "55271-cant-reproduce-test-report1.png" added.

 Test Report: can't reproduce - results shown in Chrome, Edge, Firefox, and
 Safari. Works for me

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

From noreply at wordpress.org  Tue Mar  8 14:18:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:18:33 -0000
Subject: [wp-trac] [WordPress Trac] #55271: Featured Image Section
 Disappears In Block Editor
In-Reply-To: <052.3ab4cf29bbac4776757c20c1fed09569@wordpress.org>
References: <052.3ab4cf29bbac4776757c20c1fed09569@wordpress.org>
Message-ID: <067.0fd75cf3b2121cc16d922dc69bb8dd4b@wordpress.org>

#55271: Featured Image Section Disappears In Block Editor
-------------------------------------------------+-------------------------
 Reporter:  zennie62                             |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing-info reporter-         |     Focuses:
  feedback                                       |
-------------------------------------------------+-------------------------

Comment (by hellofromTonya):

 == Test Report

 === Env

 * OS: macOS Big Sur
 * WordPress: 5.9 and 5.9.1
 * Localhost: wp-env and Local
 * Browsers: Chrome, Edge, Firefox, Safari
 * Theme: Twenty Twenty-Two (TT2)
 * Plugins: none activated

 === Steps to Test

 1. Navigate to Posts > Add New
 2. In the `Post` tab of the right sidebar, the Feature image area should
 be there.

 === Results

 I can't reproduce the reported issue. It works for me.

 The Feature image area is present in the Post editor with a block theme
 activated. See [attachment:"55271-cant-reproduce-test-report1.png"] for
 test results in 4 different browsers.

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

From noreply at wordpress.org  Tue Mar  8 14:20:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:20:53 -0000
Subject: [wp-trac] [WordPress Trac] #55336: Query strings with reserved
 characters get wrongly redirected to encoded variant at the root level.
In-Reply-To: <053.11d5ce4bde2445cb0e260ad0a7f506a9@wordpress.org>
References: <053.11d5ce4bde2445cb0e260ad0a7f506a9@wordpress.org>
Message-ID: <068.239dbc75b21dcd72062f7655b4765b1e@wordpress.org>

#55336: Query strings with reserved characters get wrongly redirected to encoded
variant at the root level.
--------------------------+------------------------------
 Reporter:  madstegge     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by SergeyBiryukov):

 Hi there, welcome to WordPress Trac! Thanks for the report.

 Replying to [ticket:55336 madstegge]:
 > WordPress however, redirects to a URI encoded variant when the query
 string at the root level contains these reserved characters.
 >
 > So, https://wordpress.org/plugins/?test=123*456 doesn't redirect.
 >
 > While https://wordpress.org/?test=123*456 redirects to
 https://wordpress.org/?test=123%2A456.

 I could not reproduce the issue on a clean install. Testing with some
 other sites like https://ma.tt/?test=123*456, they don't redirect either.

 WordPress.org does indeed redirect as noted, but I think that might be
 something specific to that particular network.

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

From noreply at wordpress.org  Tue Mar  8 14:21:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:21:07 -0000
Subject: [wp-trac] [WordPress Trac] #55340: Bad wording in translation string
Message-ID: <057.c93becc09b6c5313400771d2ab426527@wordpress.org>

#55340: Bad wording in translation string
---------------------------+-----------------------------
 Reporter:  pedromendonca  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  I18N           |    Version:  trunk
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 The below string needs improvement:
 ''Whether to make the post type ~~is~~ available for selection in
 navigation menus.''

 Suggestion:
 ''Whether to make the post type available for selection in navigation
 menus.
 ''
 Source:
 https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes
 /rest-api/endpoints/class-wp-rest-post-types-controller.php#L371

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

From noreply at wordpress.org  Tue Mar  8 14:48:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:48:06 -0000
Subject: [wp-trac] [WordPress Trac] #37189: In wp_term_query on cache ids
In-Reply-To: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
References: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
Message-ID: <071.d1c721b128d3dfb80731eaca001061c5@wordpress.org>

#37189: In wp_term_query on cache ids
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Taxonomy                             |     Version:  4.6
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-08 at 14.46.00.png" added.

 Before patch applied

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

From noreply at wordpress.org  Tue Mar  8 14:48:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:48:20 -0000
Subject: [wp-trac] [WordPress Trac] #37189: In wp_term_query on cache ids
In-Reply-To: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
References: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
Message-ID: <071.9eee273a8018a7299a392144088c2acd@wordpress.org>

#37189: In wp_term_query on cache ids
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Taxonomy                             |     Version:  4.6
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-08 at 14.46.37.png" added.

 After patch was applied

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

From noreply at wordpress.org  Tue Mar  8 14:48:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:48:55 -0000
Subject: [wp-trac] [WordPress Trac] #55340: Bad wording in translation
 string
In-Reply-To: <057.c93becc09b6c5313400771d2ab426527@wordpress.org>
References: <057.c93becc09b6c5313400771d2ab426527@wordpress.org>
Message-ID: <072.0a4978bd0e6619be19c1afa09fc4c516@wordpress.org>

#55340: Bad wording in translation string
---------------------------+---------------------
 Reporter:  pedromendonca  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  I18N           |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Tue Mar  8 14:49:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:49:57 -0000
Subject: [wp-trac] [WordPress Trac] #55340: Bad wording in translation
 string
In-Reply-To: <057.c93becc09b6c5313400771d2ab426527@wordpress.org>
References: <057.c93becc09b6c5313400771d2ab426527@wordpress.org>
Message-ID: <072.29b0a8b060286a2338f11645cf37b4e6@wordpress.org>

#55340: Bad wording in translation string
---------------------------+-----------------------------
 Reporter:  pedromendonca  |       Owner:  SergeyBiryukov
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:  6.0
Component:  I18N           |     Version:  trunk
 Severity:  normal         |  Resolution:  fixed
 Keywords:  has-patch      |     Focuses:
---------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52831" 52831]:
 {{{
 #!CommitTicketReference repository="" revision="52831"
 REST API: Correct the wording for `show_in_nav_menus` property description
 in post type visibility settings.

 Follow-up to [51959].

 Props pedromendonca.
 Fixes #55340.
 }}}

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

From noreply at wordpress.org  Tue Mar  8 14:53:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:53:11 -0000
Subject: [wp-trac] [WordPress Trac] #55341: Auto update bundled core themes
 by default
Message-ID: <054.e2ce5cbf96e7fbed423e1b0676cd0590@wordpress.org>

#55341: Auto update bundled core themes by default
-----------------------------+-----------------------------
 Reporter:  JosVelasco       |      Owner:  (none)
     Type:  enhancement      |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 After a core auto update runs and a new theme is installed it won't auto
 update by default.

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

From noreply at wordpress.org  Tue Mar  8 14:55:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:55:08 -0000
Subject: [wp-trac] [WordPress Trac] #55340: Bad wording in translation
 string
In-Reply-To: <057.c93becc09b6c5313400771d2ab426527@wordpress.org>
References: <057.c93becc09b6c5313400771d2ab426527@wordpress.org>
Message-ID: <072.9f54065f2bbc8ca89d6d76934eca5511@wordpress.org>

#55340: Bad wording in translation string
---------------------------+-----------------------------
 Reporter:  pedromendonca  |       Owner:  SergeyBiryukov
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:  6.0
Component:  I18N           |     Version:  trunk
 Severity:  normal         |  Resolution:  fixed
 Keywords:  has-patch      |     Focuses:
---------------------------+-----------------------------

Comment (by pedromendonca):

 Thanks @SergeyBiryukov! :-)

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

From noreply at wordpress.org  Tue Mar  8 14:55:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 14:55:40 -0000
Subject: [wp-trac] [WordPress Trac] #55221: Feature image does not load
 media library in correct view.
In-Reply-To: <053.98376a7f1298436d309ce5717cb6aa0e@wordpress.org>
References: <053.98376a7f1298436d309ce5717cb6aa0e@wordpress.org>
Message-ID: <068.4a615821a0fddb0231e02b17047e8631@wordpress.org>

#55221: Feature image does not load media library in correct view.
--------------------------+------------------------
 Reporter:  jhall_3rd     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Media         |     Version:  5.8.2
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by hellofromTonya):

 * keywords:  needs-testing =>
 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 Following up:
 This issue was reported in #53765 and a fix shipped in 5.9 with [52384]
 changeset.

 I'll close this ticket as a duplicate.

 @jhall_3rd upgrading to 5.9.1 should resolve the issue you're
 experiencing. If no, please re-open the ticket for further investigation.
 Thank you!

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

From noreply at wordpress.org  Tue Mar  8 15:05:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 15:05:52 -0000
Subject: [wp-trac] [WordPress Trac] #55245: All images not showing since
 Update to WP 5.9.1
In-Reply-To: <056.ef03e33ec49f0e88be8ebbb10a80a9c6@wordpress.org>
References: <056.ef03e33ec49f0e88be8ebbb10a80a9c6@wordpress.org>
Message-ID: <071.588b938c48b13f65fc940f693d19dc5c@wordpress.org>

#55245: All images not showing since Update to WP 5.9.1
-------------------------------+------------------------------
 Reporter:  cswebdesigns       |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:  5.9.1
 Severity:  trivial            |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by hellofromTonya):

 * keywords:   => reporter-feedback
 * component:  General => Media


Comment:

 Hello @cswebdesigns,

 Welcome to WordPress Core's Trac. Thank you for the ticket.

 I'm sorry you're site is having issues after upgrading to 5.9.1. During
 today's triage session, the Test Team was unable to reproduce this issue
 using a default setup of no plugins activated and a default bundled theme
 like Twenty Twenty-Two or Twenty Twenty-One.

 Wondering if this issue is caused by either an incomplete upgrade or a
 conflict from a plugin or theme.

 Some things to try:

 * Reinstall 5.9.1. Does the problem resolve?
 * Deactivate all plugins. Does the problem resolve?
 * Try to switch to a bundled theme. Does the problem resolve?
 * Are there any errors in your browser's console tab (in Dev tools)? If
 yes, please share a screenshot.

 How did you manually change each image? Can you share the steps you did?

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

From noreply at wordpress.org  Tue Mar  8 15:12:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 15:12:44 -0000
Subject: [wp-trac] [WordPress Trac] #55296: Issue with Images
In-Reply-To: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
References: <053.7360aba65b1e779496171c1e9ef6b671@wordpress.org>
Message-ID: <068.9f336ae772887dd12599f1e12da6459c@wordpress.org>

#55296: Issue with Images
--------------------------+-------------------------
 Reporter:  lyntreeio     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Media         |     Version:  5.9.1
 Severity:  critical      |  Resolution:  worksforme
 Keywords:  close         |     Focuses:
--------------------------+-------------------------
Changes (by SergeyBiryukov):

 * component:  General => Media
 * milestone:  Awaiting Review =>


Comment:

 Thanks for the follow-up!

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

From noreply at wordpress.org  Tue Mar  8 15:16:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 15:16:34 -0000
Subject: [wp-trac] [WordPress Trac] #55341: Auto update bundled core
 themes by default
In-Reply-To: <054.e2ce5cbf96e7fbed423e1b0676cd0590@wordpress.org>
References: <054.e2ce5cbf96e7fbed423e1b0676cd0590@wordpress.org>
Message-ID: <069.22e08870c5de024813b0efbd5b3665bf@wordpress.org>

#55341: Auto update bundled core themes by default
-----------------------------+------------------------
 Reporter:  JosVelasco       |       Owner:  (none)
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:  duplicate
 Keywords:                   |     Focuses:
-----------------------------+------------------------
Changes (by SergeyBiryukov):

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


Comment:

 Hi there, welcome back to WordPress Trac!

 Thanks for the ticket, we're already tracking this enhancement in #55321.

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

From noreply at wordpress.org  Tue Mar  8 15:24:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 15:24:47 -0000
Subject: [wp-trac] [WordPress Trac] #55336: Query strings with reserved
 characters get wrongly redirected to encoded variant at the root level.
In-Reply-To: <053.11d5ce4bde2445cb0e260ad0a7f506a9@wordpress.org>
References: <053.11d5ce4bde2445cb0e260ad0a7f506a9@wordpress.org>
Message-ID: <068.1ac22fe8b050eecbda3dafe272a8fdf0@wordpress.org>

#55336: Query strings with reserved characters get wrongly redirected to encoded
variant at the root level.
--------------------------+------------------------------
 Reporter:  madstegge     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by madstegge):

 Replying to [comment:1 SergeyBiryukov]:
 > I could not reproduce the issue on a clean install. Testing with some
 other sites like https://ma.tt/?test=123*456, they don't redirect either.
 >
 > WordPress.org does indeed redirect as noted, but I think that might be
 something specific to that particular network.
 That's interesting. All WordPress sites that I know of present this
 behavior. But it might be caused by a widespread plugin then. I'm not a
 developer, so can't give any more details about the affected
 configurations.

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

From noreply at wordpress.org  Tue Mar  8 15:27:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 15:27:11 -0000
Subject: [wp-trac] [WordPress Trac] #55336: Query strings with reserved
 characters get wrongly redirected to encoded variant at the root level.
In-Reply-To: <053.11d5ce4bde2445cb0e260ad0a7f506a9@wordpress.org>
References: <053.11d5ce4bde2445cb0e260ad0a7f506a9@wordpress.org>
Message-ID: <068.ad8ab2b7de7d19395b39343a6abfe911@wordpress.org>

#55336: Query strings with reserved characters get wrongly redirected to encoded
variant at the root level.
--------------------------+------------------------------
 Reporter:  madstegge     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by madstegge):

 The good news is that Google Analytics seems to handle the encoded query
 string correctly after all. But it might cause difficulties for other
 applications...

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

From noreply at wordpress.org  Tue Mar  8 15:48:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 15:48:30 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.1bf00740d2c8d51388d2196d6b40d975@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  Future Release
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute needs-patch              |  javascript
-------------------------------------+-------------------------------------
Changes (by afercia):

 * Attachment "35483.2.diff" added.


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

From noreply at wordpress.org  Tue Mar  8 15:50:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 15:50:57 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.3349d681018ca18fb6e7b09a3b29cb82@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch needs-testing  |  javascript
-------------------------------------+-------------------------------------
Changes (by afercia):

 * keywords:  has-screenshots title-attribute needs-patch => has-screenshots
     title-attribute has-patch needs-testing
 * owner:  (none) => afercia
 * milestone:  Future Release => 6.0


Comment:

 Looking back at this ticket, the list of posts to be bulk-edited is still
 not operable with a keyboard. This needs to be fixed.

 The two remaining points that still need to be solved are:
 1. Initial focus when opening Bulk Edit.
 2. Escaping of emojis and special characters in the post title.

 In [attachment:"35483.2.diff"]
 - Both Bulk Edit and Quick Edit are now wrapped within a new `<div>`
 element with class `inline-edit-wrapper`.
 - This new `<div>` element:
   - Has a `role="region"` attribute.
   - It's labelled with and `aria-labelledby` attribute that points to the
 visible first fieldset legend e.g. 'BULK EDIT'.
   - Thanks to these two attributes, it becomes an ARIA landmark, which is
 an added bonus as landmarks can be easily found by assistive technology
 users.
 - Initial focus for Bulk Edit:
   - As pointed out in the previous comments, there's no clear 'default
 action' where to move focus to.
   - Therefore, the new patch sets initial focus on the ARIA region that
 wraps Bulk Edit.
   - When the ARIA region receives focus, screen readers will announce the
 region role and label.
   - The ARIA region will also show a clear focus style.
 - Initial focus for Quick Edit:
   - No change: the post title field will receive initial focus.
   - I'd recommend to consider to set initial focus to the ARIA region also
 in this case, for consistency.
 - Escaping of emojis and special characters:
   - The remove buttons don't use an `aria-label` attribute any longer so
 there's no need to escape the post title for use in a HTML attribute.
   - Instead, the buttons now use visually hidden text: this is content, no
 different from the visible post title, and can contain emojis and special
 characters.


 Some code review and testing would be greatly appreciated.

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

From noreply at wordpress.org  Tue Mar  8 15:51:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 15:51:44 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.774105d53e6ccee1b4c61fadcc9b001c@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch needs-testing  |  javascript
-------------------------------------+-------------------------------------
Changes (by afercia):

 * Attachment "before.png" added.

 Before the patch.

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

From noreply at wordpress.org  Tue Mar  8 15:52:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 15:52:25 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.02322df18148e431dbd53fa095cab2b7@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch needs-testing  |  javascript
-------------------------------------+-------------------------------------
Changes (by afercia):

 * Attachment "after.png" added.

 After the patch, with visible focus on the new ARIA region.

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

From noreply at wordpress.org  Tue Mar  8 16:04:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 16:04:51 -0000
Subject: [wp-trac] [WordPress Trac] #55342: If the contextual help panel is
 open and then I scroll, I have to click on help twice to close the panel
Message-ID: <051.2181a15c6ebcad26d40e92f871666359@wordpress.org>

#55342: If the contextual help panel is open and then I scroll, I have to click on
help twice to close the panel
--------------------------+-----------------------------
 Reporter:  mikecho       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Help/About    |    Version:  5.9.1
 Severity:  minor         |   Keywords:
  Focuses:  ui            |
--------------------------+-----------------------------
 Steps to reproduce:
 1. click "Help" to open a contextual help panel
 2. scroll
 3. click "Help" to close the panel; note that it does not close
 4. click "Help" again; note that it does close this time

 This is annoying for the user--can this be solved so that it only takes
 one click to close the contextual help after scrolling?

 In our plugin, we are using enough contextual help on one page that you
 have to scroll to reach the "Help" button (#contextual-help-link") to
 close it again.

 Further notes: I have a live expression for document.activeElement in the
 console. On the first attempt to close the section, the
 document.activeElement shows:

 {{{
 button#contextual-help-link.button.show-settings.screen-meta-active
 }}}


 on the second, click it shows:


 {{{
 button#contextual-help-link.button.show-settings
 }}}

 More info:
 happens in several tested themes (2022, 2021, 2020)
 happens when all plugins are deactivated
 Chrome/Edge/Firefox, Windows 10, Ubuntu 20.04

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

From noreply at wordpress.org  Tue Mar  8 16:33:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 16:33:44 -0000
Subject: [wp-trac] [WordPress Trac] #55343: Add Tooltip to "Remember Me" (WP
 Login Form)
Message-ID: <053.b5a11e22532e0c787bec386d453e28ca@wordpress.org>

#55343: Add Tooltip to "Remember Me" (WP Login Form)
-------------------------+-------------------------------------------------
 Reporter:  generosus    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Security     |    Version:  5.9.1
 Severity:  normal       |   Keywords:  dev-feedback 2nd-opinion needs-docs
  Focuses:               |  needs-codex
-------------------------+-------------------------------------------------
 Currently, WordPress' login form has a checkbox labeled "Remember Me."

 Over the years, there's been some debate over the verbiage used for
 "Remember Me" (say, versus "Stay Logged In" or "Keep Me Logged In") and
 what it really means.

 To eliminate any confusion, this is to request the [https://ibb.co/fkqN7Vz
 /addition of a tooltip] next to "Remember Me" in the form of a question
 (?) mark. Further, the tooltip can offer a security warning to all users.

 The content (text) for the tooltip could be:

 "**Selecting Remember Me reduces the number of times you’ll be asked to
 log in using this device. To keep your account secure, use this option
 only on your personal devices.**"

 Also, in anticipation that this enhancement request will be approved, I
 would like to recommend updating the
 [https://developer.wordpress.org/reference/functions/wp_login_form
 /affected codex page] for the login form to add a code snippet that will
 allow developers to change the content (text) of the tooltip to suit their
 needs.

 The above would be a nice addition or update to WordPress' login form.

 Thank you.

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

From noreply at wordpress.org  Tue Mar  8 16:36:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 16:36:49 -0000
Subject: [wp-trac] [WordPress Trac] #55343: Add Tooltip to "Remember Me"
 (WP Login Form)
In-Reply-To: <053.b5a11e22532e0c787bec386d453e28ca@wordpress.org>
References: <053.b5a11e22532e0c787bec386d453e28ca@wordpress.org>
Message-ID: <068.4375c4005e545ae885cbf4761347b398@wordpress.org>

#55343: Add Tooltip to "Remember Me" (WP Login Form)
--------------------------+------------------------------
 Reporter:  generosus     |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Security      |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |     Focuses:
--------------------------+------------------------------
Changes (by generosus):

 * keywords:  dev-feedback 2nd-opinion needs-docs needs-codex => dev-
               feedback


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

From noreply at wordpress.org  Tue Mar  8 16:59:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 16:59:05 -0000
Subject: [wp-trac] [WordPress Trac] #55343: Add Tooltip to "Remember Me"
 (WP Login Form)
In-Reply-To: <053.b5a11e22532e0c787bec386d453e28ca@wordpress.org>
References: <053.b5a11e22532e0c787bec386d453e28ca@wordpress.org>
Message-ID: <068.c2a70f6f6febde590fe3c1388fa5375c@wordpress.org>

#55343: Add Tooltip to "Remember Me" (WP Login Form)
--------------------------+------------------------------
 Reporter:  generosus     |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Security      |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |     Focuses:
--------------------------+------------------------------

Comment (by generosus):

 **Correction:**

 If approved, these are the affected WordPress documents:

 [https://developer.wordpress.org/reference/functions/wp_login_form /Code
 Reference Page]
 [https://codex.wordpress.org/Customizing_the_Login_Form /Codex Page]

 Thank you.

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

From noreply at wordpress.org  Tue Mar  8 17:10:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 17:10:45 -0000
Subject: [wp-trac] [WordPress Trac] #54423: Add Site Health test for
 full page caching (advanced cache)
In-Reply-To: <055.1a40931285f63f7119be6a62995a057e@wordpress.org>
References: <055.1a40931285f63f7119be6a62995a057e@wordpress.org>
Message-ID: <070.9bf41e783d23216ac93e18c8fa54614f@wordpress.org>

#54423: Add Site Health test for full page caching (advanced cache)
-------------------------+------------------------------
 Reporter:  westonruter  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Site Health  |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-docs   |     Focuses:  performance
-------------------------+------------------------------

Comment (by westonruter):

 Cross-posted in [https://github.com/WordPress/performance/issues/220
 WordPress/performance#220].

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

From noreply at wordpress.org  Tue Mar  8 17:29:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 17:29:04 -0000
Subject: [wp-trac] [WordPress Trac] #54476: Improve image engine
 detection when output format adjusted with filter.
In-Reply-To: <059.dd466e6070f6af55c5f5b41615375d51@wordpress.org>
References: <059.dd466e6070f6af55c5f5b41615375d51@wordpress.org>
Message-ID: <074.9212e153ababb7136ad3db3312a955f5@wordpress.org>

#54476: Improve image engine detection when output format adjusted with filter.
-------------------------------------+---------------------
 Reporter:  adamsilverstein          |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.8
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+---------------------
Changes (by adamsilverstein):

 * keywords:  has-patch => has-patch needs-refresh
 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Tue Mar  8 17:29:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 17:29:07 -0000
Subject: [wp-trac] [WordPress Trac] #54476: Improve image engine
 detection when output format adjusted with filter.
In-Reply-To: <059.dd466e6070f6af55c5f5b41615375d51@wordpress.org>
References: <059.dd466e6070f6af55c5f5b41615375d51@wordpress.org>
Message-ID: <074.d8cb1e5b01e3e65f4e1306f2034708ba@wordpress.org>

#54476: Improve image engine detection when output format adjusted with filter.
-------------------------------------+------------------------------
 Reporter:  adamsilverstein          |       Owner:  adamsilverstein
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.8
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+------------------------------
Changes (by adamsilverstein):

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


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

From noreply at wordpress.org  Tue Mar  8 17:39:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 17:39:03 -0000
Subject: [wp-trac] [WordPress Trac] #55344: Resources for hidden widgets are
 loaded on WP dashboard
Message-ID: <053.4ed27fa406a39cbf13813ae1048c8a9f@wordpress.org>

#55344: Resources for hidden widgets are loaded on WP dashboard
----------------------------+-----------------------------
 Reporter:  josklever       |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:  5.9.1
 Severity:  normal          |   Keywords:
  Focuses:  performance     |
----------------------------+-----------------------------
 When plugins are placing widgets on the WordPress dashboard and these are
 hidden via the Screen Options the resources of those widgets are still
 loaded.

 In the Sources tab of the browser console this can easily be checked. I've
 noticed this with multiple plugins, so it looks like a core bug.

 It would save resources and increase performance of the dashboard if
 hidden items are not loaded.

 I've asked in the #performance Slack channel, where I was asked to create
 a ticket to report this as a bug.

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

From noreply at wordpress.org  Tue Mar  8 17:45:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 17:45:56 -0000
Subject: [wp-trac] [WordPress Trac] #55345: When uploading image through
 featured image section, the image item count is wrong.
Message-ID: <059.ca1c40cbbd8bb6a42956106d68a510e2@wordpress.org>

#55345: When uploading image through featured image section, the image item count
is wrong.
-----------------------------+-----------------------------------------
 Reporter:  alanjacobmathew  |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Media            |    Version:
 Severity:  normal           |   Keywords:  has-screenshots needs-patch
  Focuses:                   |
-----------------------------+-----------------------------------------
 When uploading image through featured image section, the image item count
 is wrong.

 === Env
 * 5.9.1
 * Brave, Chromium
 * Win 10
 * Theme : TT2
 * Plugins: None

 === Test Instruction

 * Open Post Editor and click on 'Set featured image' option.
 * Notice the total number of existing images
 * Upload a new image into the featured image section.
 * Now notice the number of images (+2)


 * Reload the page, and now the count corrects itself.



 When uploading image directly to the featured image section of the post
 editor, the media item count works correctly.

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

From noreply at wordpress.org  Tue Mar  8 17:46:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 17:46:36 -0000
Subject: [wp-trac] [WordPress Trac] #55345: When uploading image through
 featured image section, the image item count is wrong.
In-Reply-To: <059.ca1c40cbbd8bb6a42956106d68a510e2@wordpress.org>
References: <059.ca1c40cbbd8bb6a42956106d68a510e2@wordpress.org>
Message-ID: <074.7c97a152b80d74a5791fade9893570fc@wordpress.org>

#55345: When uploading image through featured image section, the image item count
is wrong.
-----------------------------------------+------------------------------
 Reporter:  alanjacobmathew              |       Owner:  (none)
     Type:  defect (bug)                 |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Media                        |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  has-screenshots needs-patch  |     Focuses:
-----------------------------------------+------------------------------
Changes (by alanjacobmathew):

 * Attachment "Media item count.gif" added.

 Featured image wrong image count

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

From noreply at wordpress.org  Tue Mar  8 18:20:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 18:20:14 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly
 with Odysee.com (half working)
In-Reply-To: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
References: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
Message-ID: <070.958b4fa6a764a7f2f7d6f40898335b9b@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+------------------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+------------------------------

Comment (by tomatodysee):

 @peterwilsoncc answering the questions as you asked, let me know if this
 works:

 Is the service is popular enough for core developers to have heard of it
 before? Is it “mainstream?”
 Odysee has been around for 1.5 years now and evolved from lbry.tv (~2019,
 now sunset) and a LBRY Desktop application in 2016. Today, Odysee.com has
 over 32M+ monthly unique visitors and is used by prominent content
 creators, many of which have millions of youtube subscribers.

 If similar services are already supported, how does this service compare
 in terms of size, features, and backing?
 No, this is new.

 Does this service have a large following on Twitter, Facebook, or other
 social media?  Is its Twitter account verified?
 Twitter account is verified and has over 55K followers:
 https://twitter.com/OdyseeTeam . This is our main social media platform,
 and on our own site, we have over 1.3M followers:
 https://odysee.com/@Odysee:8

 Is its oEmbed endpoint clearly established and properly documented?
 (Sometimes, they are just a developer’s pet project that may not be
 supported.)
 Oembed implementation can be found here: https://github.com/OdyseeTeam
 /odysee-frontend/blob/master/web/src/oEmbed.js
 We are also supported on embed.ly, and you can validate our URLs here:
 http://debug.iframely.com/?uri=https%3A%2F%2Fodysee.com%2F%40veritasium%3Af%2Fwe
 %27re-building-computers-wrong-%28for%3Af

 Does the oEmbed endpoint work with WordPress’ oEmbed auto-discovery? If
 not, could it be made to work with additional HTML tags or attributes
 being added to the allow-list?
 No, only works via paid wordpress accounts + via our embed code. Our
 iframes use cookies, and require the same-site origin flag which, as
 discussed
 above, is not secure enough based on WordPress standards.

 Does the service make an effort to build relationships with developers,
 such as through robust APIs?
 Majority of our code is open source, and we work with outside contributors
 all the time!

 How old is the service?
 1.5+ years, but LBRY has been around since 2016.

 Does it have a well-established Wikipedia article? (Seriously.)
 Right now it’s under LBRY, but we hope someone will correct that. Odysee
 is now a separate company outside of LBRY Inc (for the past ~6 months).
 https://en.wikipedia.org/wiki/LBRY

 Has anyone written a WordPress plugin that leverages the service in some
 way, whether adding it as an oEmbed provider, creating a shortcode, or
 leveraging other APIs of the service? Do these plugins have any noticeable
 adoption or traction that would indicate usage and demand?
 There’s a wordpress plugin for LBRY: https://github.com/lbryio/lbrypress,
 but it didn’t get much traction. LBRY Inc is revamping it to make it
 easier to use/integrate.

 Is the provider frequently proposed?
 We get many requests from users and creators to support Odysee links on
 WordPress!

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

From noreply at wordpress.org  Tue Mar  8 19:08:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 19:08:18 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
Message-ID: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------+----------------------------------
 Reporter:  fs5ve         |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Privacy       |    Version:  5.9
 Severity:  major         |   Keywords:  needs-privacy-review
  Focuses:                |
--------------------------+----------------------------------
 Hi,

 We, a group of researchers from University of virginia and John hopkins
 university are investigating the GDPR compliance issue for wordpress
 plugins. During the investigation,
 I have installed wordpresss 5.9 in my local machine. Later, I created one
 root and one regular user account in my local machine. After that, I
 installed profilepress (https://wordpress.org/plugins/wp-user-avatar/)
 plugin and activated it. By this time, I have some information (personal
 information) stored in the database. These days, to comply with GDPR,
 wordpress comes with data deletion and data access feature. So, to test
 that, I have made a request to delete my regular user from the database
 and approved it. In the request table, it showed the status to
 “completed”. But later when I select the data access, it exported that
 user’s data. I checked the database, I can still see all the information
 related to that user.

 Note that, I haven’t modified my code from the wordpress core, other than
 the configuration file.

 Can you please take a look at this issue? I can also share the screenshot
 of the whole process if needed. Please let me know if any other
 information needed.

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

From noreply at wordpress.org  Tue Mar  8 19:11:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 19:11:32 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.8169a62d791dcb837ba0de827feab8a2@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------+------------------------------
 Reporter:  fs5ve         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Privacy       |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+------------------------------
Changes (by swissspidy):

 * keywords:  needs-privacy-review => close
 * severity:  major => normal


Comment:

 Hi there,

 Thanks for opening this. Since WordPress cannot know what type of data
 plugins store, it's up to the plugins to hook into the data export /
 erasure process offered by WordPress. See
 https://developer.wordpress.org/plugins/privacy/ for details.

 So in this case, you'd want to reach out to ProfilePress so they can look
 into this and make any necessary changes to their plugin.

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

From noreply at wordpress.org  Tue Mar  8 20:29:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 20:29:32 -0000
Subject: [wp-trac] [WordPress Trac] #54926: Deprecated: WP_User_Query
 was called with an argument that is deprecated since version 5.9.0!
In-Reply-To: <056.fa02f8e32cf7adff226e382fb685c1c7@wordpress.org>
References: <056.fa02f8e32cf7adff226e382fb685c1c7@wordpress.org>
Message-ID: <071.d2b066f621397c638e554123513002e5@wordpress.org>

#54926: Deprecated: WP_User_Query was called with an argument that is deprecated
since version 5.9.0!
--------------------------+----------------------
 Reporter:  sonjaysarker  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Users         |     Version:  5.9
 Severity:  normal        |  Resolution:  invalid
 Keywords:  has-patch     |     Focuses:
--------------------------+----------------------

Comment (by iandunn):

 I'm also seeing this intermittently, and it looks like
 [https://github.com/WordPress/gutenberg/search?q=who:authors Gutenberg may
 still have several `who:author` queries]. I haven't had time to dig in
 further, though.

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

From noreply at wordpress.org  Tue Mar  8 22:09:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 22:09:59 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in
 releases without a global theme auto-update setting renders installations
 insecure
In-Reply-To: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
References: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
Message-ID: <072.aa788ef700e15cec323154da48348e23@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
-------------------------------+-----------------------
 Reporter:  bertvandepoel      |       Owner:  pbiron
     Type:  enhancement        |      Status:  assigned
 Priority:  normal             |   Milestone:  6.0
Component:  Upgrade/Install    |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+-----------------------
Changes (by pbiron):

 * owner:  (none) => pbiron
 * status:  new => assigned
 * component:  Themes => Upgrade/Install
 * milestone:  Awaiting Review => 6.0


Comment:

 Hi @bertvandepoel, this ticket was discussed during the
 [https://wordpress.slack.com/archives/CULBN711P/p1646760805500679
 Upgrade/Install component meeting]  earlier today.

 We decided to try to get a solution to this in the next major version of
 WP, no promises, but we'll try.

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

From noreply at wordpress.org  Tue Mar  8 22:26:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 22:26:08 -0000
Subject: [wp-trac] [WordPress Trac] #22316: Plugin Dependencies (Yet
 Another Plugin Dependencies Ticket)
In-Reply-To: <056.dd52dedca2457b5bc3a0cb986370b731@wordpress.org>
References: <056.dd52dedca2457b5bc3a0cb986370b731@wordpress.org>
Message-ID: <071.25e65103116a1177e2bf6bfe965cd3c9@wordpress.org>

#22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)
------------------------------------------+-----------------------------
 Reporter:  Viper007Bond                  |       Owner:  (none)
     Type:  enhancement                   |      Status:  new
 Priority:  normal                        |   Milestone:  Future Release
Component:  Upgrade/Install               |     Version:  3.4.2
 Severity:  normal                        |  Resolution:
 Keywords:  dev-feedback has-patch early  |     Focuses:
------------------------------------------+-----------------------------
Changes (by afragen):

 * milestone:  6.0 => Future Release


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

From noreply at wordpress.org  Tue Mar  8 22:28:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 22:28:41 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.2033040e69100380e3fb3c0b6d6dbc8d@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------+---------------------
 Reporter:  kajalgohel               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------

Comment (by audrasjb):

 Hello and thank you for opening this ticket and for the patch!

 However, I reproduced the context (image post format and blog/archive
 page) and it looks like we shouldn't remove this since it applies to both
 `.entry-meta` divs. Removing this CSS declaration breaks the design of the
 meta box on my side.

 See the animated screenshot below

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

From noreply at wordpress.org  Tue Mar  8 22:29:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 22:29:09 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.15c21b92ebbc5d7f9b5f7ffd824b66d5@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------+---------------------
 Reporter:  kajalgohel               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------
Changes (by audrasjb):

 * Attachment "16c4d8dd4b8e6390250e32311204a1fb.gif" added.


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

From noreply at wordpress.org  Tue Mar  8 22:32:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 22:32:46 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.3f73e72416e2c5b394ceb264dba80981@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------+----------------------
 Reporter:  fs5ve         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Privacy       |     Version:  5.9
 Severity:  normal        |  Resolution:  invalid
 Keywords:  close         |     Focuses:
--------------------------+----------------------
Changes (by johnbillion):

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


Comment:

 @fs5ve Please note that you received the same response for your previous
 report at #52024. Please ensure you direct your reports to the affected
 plugins instead. Thank you.

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

From noreply at wordpress.org  Tue Mar  8 22:34:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 22:34:24 -0000
Subject: [wp-trac] [WordPress Trac] #55347: they should be filter for image
 tag in wp_filter_content_tags()
Message-ID: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>

#55347: they should be filter for image tag in wp_filter_content_tags()
-------------------------+-----------------------------
 Reporter:  pbearne      |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Media        |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------


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

From noreply at wordpress.org  Tue Mar  8 22:34:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 22:34:43 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags() (was: they should be filter for image
 tag in wp_filter_content_tags())
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.c580c052038318849674cdffbd3cf587@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
-------------------------+------------------------------
 Reporter:  pbearne      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Media        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

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

From noreply at wordpress.org  Tue Mar  8 23:07:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 08 Mar 2022 23:07:53 -0000
Subject: [wp-trac] =?utf-8?q?=5BWordPress_Trac=5D_=2355348=3A_Deneme_?=
 =?utf-8?b?w7bEn3Jlbm1leWUgw6dhbMSxxZ/EsXlvcnVt?=
Message-ID: <054.9903837a707caa0eebd6977eca7337f7@wordpress.org>

#55348: Deneme öğrenmeye çalışıyorum
-----------------------------+-----------------------------
 Reporter:  volkan7934       |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Administration   |    Version:  5.9.1
 Severity:  normal           |   Keywords:  has-patch
  Focuses:                   |
-----------------------------+-----------------------------
 Kusura bakmayin
 iyi çalışmalar

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

From noreply at wordpress.org  Wed Mar  9 00:46:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 00:46:38 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.d4545c8a5b06f73b18981ef9df9b3325@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 In [changeset:"52832" 52832]:
 {{{
 #!CommitTicketReference repository="" revision="52832"
 Media: Revert query string support for `wp_check_filetype()`.

 Revert [52829] due to fatal errors in some Multisite configurations.

 Props dd32, SergeyBiryukov, audrasjb.
 See #30377.
 }}}

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

From noreply at wordpress.org  Wed Mar  9 01:08:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 01:08:39 -0000
Subject: [wp-trac] [WordPress Trac] #55341: Auto update bundled core
 themes by default
In-Reply-To: <054.e2ce5cbf96e7fbed423e1b0676cd0590@wordpress.org>
References: <054.e2ce5cbf96e7fbed423e1b0676cd0590@wordpress.org>
Message-ID: <069.4de38d094d8e9b29ceaaf39a0c628a76@wordpress.org>

#55341: Auto update bundled core themes by default
-----------------------------+------------------------
 Reporter:  JosVelasco       |       Owner:  (none)
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:  duplicate
 Keywords:                   |     Focuses:
-----------------------------+------------------------

Comment (by Otto42):

 We have never turned on auto-updates for any theme. Ever. It seems way too
 dangerous. People modify their themes. Plugins tend to not be directly
 changed.

 This is just my opinion, updating themes directly loses any customizations
 they may have made to files in the theme folder. It's risky. Very, very
 risky.

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

From noreply at wordpress.org  Wed Mar  9 01:17:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 01:17:13 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in
 releases without a global theme auto-update setting renders installations
 insecure
In-Reply-To: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
References: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
Message-ID: <072.778a65b7217d20a24a1bc14d8f74fc77@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
-------------------------------+-----------------------
 Reporter:  bertvandepoel      |       Owner:  pbiron
     Type:  enhancement        |      Status:  assigned
 Priority:  normal             |   Milestone:  6.0
Component:  Upgrade/Install    |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+-----------------------

Comment (by Otto42):

 We have never turned on auto-updates for any theme. Ever. It seems way too
 dangerous. People modify their themes. Plugins tend to not be directly
 changed.

 This is just my opinion, updating themes directly loses any customizations
 they may have made to files in the theme folder. It's risky. Very, very
 risky.

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

From noreply at wordpress.org  Wed Mar  9 01:21:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 01:21:48 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.6a6f6a70f18a052a2723f2558f1e4344@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------

Comment (by dd32):

 Replying to [comment:58 audrasjb]:
 > @dd32 I'm trying to reproduce the issue but I'm struggling a bit with
 ms-files.php, it's pretty hard to reproduce on a new install.

 Unfortunately I'm not aware of how to setup Multisite using ms-files.php,
 You probably need to manually flip the `ms_files_rewriting` site option,
 or perhaps even just request `ms-
 files.php?file=relative/path/to/file.ext`. I can say that
 `strip_fragment_from_url` is in canonical and not loaded in multisite
 SHORTINIT though.

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

From noreply at wordpress.org  Wed Mar  9 04:20:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 04:20:28 -0000
Subject: [wp-trac] [WordPress Trac] #55349: Not able to embed videos
Message-ID: <052.fa9fd9c46f123877f72c619166e3398c@wordpress.org>

#55349: Not able to embed videos
--------------------------+-----------------------------
 Reporter:  nm977890      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Embeds        |    Version:  5.8.3
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 When I attempt to embed a video, all that shows up is a small 20 x 20px
 square with no functionality and does not show up when previewing the
 post. I am not an admin. When attempting to embed the video all I do is
 copy the embed text, switch from visual to text, paste the embed text, and
 switch back to visual.

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

From noreply at wordpress.org  Wed Mar  9 04:21:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 04:21:02 -0000
Subject: [wp-trac] [WordPress Trac] #55349: Not able to embed videos
In-Reply-To: <052.fa9fd9c46f123877f72c619166e3398c@wordpress.org>
References: <052.fa9fd9c46f123877f72c619166e3398c@wordpress.org>
Message-ID: <067.37d932369032631e73f03eb21c176645@wordpress.org>

#55349: Not able to embed videos
--------------------------+------------------------------
 Reporter:  nm977890      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Embeds        |     Version:  5.8.3
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by nm977890):

 * Attachment "Screen Shot 2022-03-08 at 11.01.28 PM.png" added.


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

From noreply at wordpress.org  Wed Mar  9 06:42:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 06:42:01 -0000
Subject: [wp-trac] [WordPress Trac] #55351: The New Layout Fix For Plugin
 Install Page
Message-ID: <059.800b911ae628dfad4064e3217fe6242f@wordpress.org>

#55351: The New Layout Fix For Plugin Install Page
------------------------------+-----------------------------
 Reporter:  sharjeelkhanvmi   |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  General           |    Version:  5.9.1
 Severity:  normal            |   Keywords:  has-screenshots
  Focuses:  ui, css, ui-copy  |
------------------------------+-----------------------------
 Hello, I have done some changes to CSS in the install-plugin.php page you
 can view the after before screenshot here:
 Before View of Install Plugin Page: https://i.snipboard.io/DMpixC.jpg
 After View of Install Plugin Page: https://snipboard.io/fJvOE2.jpg
 Basically what i have done is move the Install button with a more detail
 button to the bottom and align all the boxes with the same height hide
 extra text in the plugin title and description and give some border-radius
 on the page.
 Thanks you :)

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

From noreply at wordpress.org  Wed Mar  9 06:42:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 06:42:40 -0000
Subject: [wp-trac] [WordPress Trac] #55351: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.800b911ae628dfad4064e3217fe6242f@wordpress.org>
References: <059.800b911ae628dfad4064e3217fe6242f@wordpress.org>
Message-ID: <074.57538ab22c453959d6b000c12c24abd6@wordpress.org>

#55351: The New Layout Fix For Plugin Install Page
-----------------------------+-------------------------------
 Reporter:  sharjeelkhanvmi  |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:  5.9.1
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  ui, css, ui-copy
-----------------------------+-------------------------------
Changes (by sharjeelkhanvmi):

 * Attachment "CSS.css" added.

 CSS FOR PLUGIN INSTALL PAGE NEW DESIGN FIX CSS 2022 FOR VERSION 5.9.1

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

From noreply at wordpress.org  Wed Mar  9 07:14:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 07:14:53 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.96842b0ef02b35049286301e0a1acf28@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------+---------------------
 Reporter:  kajalgohel               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------

Comment (by kajalgohel):

 Hi @audrasjb

 Can u please provide the steps for testing ?

 Thanks

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

From noreply at wordpress.org  Wed Mar  9 07:34:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 07:34:59 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.e8415583e2606afbf8056f3267b6c37a@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------

Comment (by Ruxton):

 With the knowledge of what @dd32 just mentioned, it seems the viable
 solution outside of moving strip_fragment_from_url out of canonical (which
 is excessive) is to strip the fragment and beyond with strpos, etc. as the
 query string was.

 {{{#!php
 <?php
 $frag_pos = strpos( $filename, '#' );

 if ( false !== $frag_pos) {
   $filename = substr($filename,0, $frag_pos-1)
 }
 ?>
 }}}

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

From noreply at wordpress.org  Wed Mar  9 07:52:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 07:52:07 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.51fc4e78d648180a9133910d04845544@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------

Comment (by dd32):

 Replying to [comment:62 Ruxton]:
 > With the knowledge of what dd32 just mentioned, it seems the viable
 solution outside of moving strip_fragment_from_url out of canonical (which
 is excessive) is to strip the fragment and beyond with strpos, etc. as the
 query string was.

 Using string functions to remove parts of a URL (both `?...` and `#...`)
 is a potential security issue here (and why it would've  been reverted
 prevously), as it's possible to cause it to strip more than anticipated
 and result in operating on the incorrect filename. You should really use
 `wp_parse_url()` instead too (It's kind of like parsing HTML with Regex,
 possible, but should be avoided).

 Additionally, since the parameter can be a Filename, Path, or URL, you
 need to restrict any URL handling to URLs only, not filenames.

 If a filename on disk ''looks like'' a url (You can have a filename on
 Linux that IS a url), you can't treat it as a URL either. If the filename
 came from an untrusted location, you can't treat it as a URL unless it's
 known to be intentionally a URL.

 Pulling out two comments from above:
  - [comment:19 Comment by me]: I'd personally prefer to add an explicit
 `wp_check_url_filetype()` function instead, one which extracts the actual
 filename from the URL and passes it along to `wp_check_filetype()` (if
 appropriate, or duplicates parts of it)
  - [comment:27 Comment by Helen]: Changing to enhancement, as
 `wp_check_filetype()` was never meant for URLs and the solution in this
 case is to introduce something else that does work for URLs.

 Even if the existing function is being passed URLs, it's not intentionally
 supposed to be used for URLs, and performing processing like this is
 doomed for failure.

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

From noreply at wordpress.org  Wed Mar  9 08:21:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 08:21:42 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.2ba5741a039c8eb458941b9443efb485@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------

Comment (by Ruxton):

 All very fair, someone actually wrote a patch with what you want and you
 responded to it at the time, then it somehow just drifted away from that.

 If patch 3 is the solution you want, should we refresh that and include
 the tests from John's patch? Would that get us to a better place?

 I'm just trying to get this across the line. It's old, annoying and a
 resolution is needed.

 Replying to [comment:63 dd32]:
 >
 > Pulling out two comments from above:
 >  - [comment:19 Comment by me]: I'd personally prefer to add an explicit
 `wp_check_url_filetype()` function instead, one which extracts the actual
 filename from the URL and passes it along to `wp_check_filetype()` (if
 appropriate, or duplicates parts of it)
 >  - [comment:27 Comment by Helen]: Changing to enhancement, as
 `wp_check_filetype()` was never meant for URLs and the solution in this
 case is to introduce something else that does work for URLs.
 >
 > Even if the existing function is being passed URLs, it's not
 intentionally supposed to be used for URLs, and performing processing like
 this is doomed for failure.

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

From noreply at wordpress.org  Wed Mar  9 09:35:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 09:35:06 -0000
Subject: [wp-trac] [WordPress Trac] #52423: Editing a category or a tag,
 and getting error message "You need a higher level of permission.
 Sorry, you are not allowed to edit this item."
In-Reply-To: <054.830e4883156008ed2da3c0ae50db1854@wordpress.org>
References: <054.830e4883156008ed2da3c0ae50db1854@wordpress.org>
Message-ID: <069.ee0b2e6af64c110bc592b01776fea6e8@wordpress.org>

#52423: Editing a category or a tag, and getting error message "You need a higher
level of permission. Sorry, you are not allowed to edit this item."
--------------------------+-----------------------
 Reporter:  webtechIMT    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Taxonomy      |     Version:  5.6
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------

Comment (by webtechIMT):

 Thank you,

 But when you try the solution described in
 [https://stackoverflow.com/a/44175853/11848895], you lose data:
 For example, I have the bug with a category A and a tag with the same name
 A and I have to choose wich one I have to deleted to solve the bug.
 If I choose for example to delete the tag, I lose association of all my
 posts with the tag A...

 Is there any solution without losing data ?

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

From noreply at wordpress.org  Wed Mar  9 09:38:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 09:38:20 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.60a5128604417904fe2a7436cb151792@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------+---------------------
 Reporter:  kajalgohel               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------

Comment (by audrasjb):

 1. Use Twenty Eleven on your website
 2. Publish a post with the "Image" post format
 3. Go to front-end
 4. Inspect the `entry-meta` zone (see animated screenshot above)

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

From noreply at wordpress.org  Wed Mar  9 09:52:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 09:52:07 -0000
Subject: [wp-trac] [WordPress Trac] #49364: dbDelta() should not change
 display width for integer data types on MySQL 8.0.17+
In-Reply-To: <058.57d558b174285895243858ce4a230956@wordpress.org>
References: <058.57d558b174285895243858ce4a230956@wordpress.org>
Message-ID: <073.d2e1fae6d1e99791c2e7803fadaba11d@wordpress.org>

#49364: dbDelta() should not change display width for integer data types on MySQL
8.0.17+
----------------------------+---------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Database        |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------

Comment (by JavierCasares):

 I'm having this problems with MariaDB 10.5.

 https://make.wordpress.org/hosting/test-results/r52797/wpsabot-r52797/

 I think this may be related with

 {{{
 @@SQL_MODE:
 STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
 }}}

 Mainly: STRICT_TRANS_TABLES. MariaDB 10.2.4+ has the STRICT_TRANS_TABLES
 by default...

 https://mariadb.com/kb/en/sql-mode/#strict_trans_tables

 Strict mode. Statements with invalid or missing data are aborted and
 rolled back, except that for non-transactional storage engines and
 statements affecting multiple rows where the invalid or missing data is
 not the first row, MariaDB will convert the invalid value to the closest
 valid value, or, if a value is missing, insert the column default value.
 Default since MariaDB 10.2.4.

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

From noreply at wordpress.org  Wed Mar  9 10:38:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 10:38:48 -0000
Subject: [wp-trac] [WordPress Trac] #49364: dbDelta() should not change
 display width for integer data types on MySQL 8.0.17+
In-Reply-To: <058.57d558b174285895243858ce4a230956@wordpress.org>
References: <058.57d558b174285895243858ce4a230956@wordpress.org>
Message-ID: <073.21503bc67161ddb6376f166849db703f@wordpress.org>

#49364: dbDelta() should not change display width for integer data types on MySQL
8.0.17+
----------------------------+---------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Database        |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------

Comment (by SergeyBiryukov):

 Replying to [comment:12 JavierCasares]:
 > I'm having this problems with MariaDB 10.5.
 >
 > https://make.wordpress.org/hosting/test-results/r52797/wpsabot-r52797/
 >
 > I think this may be related with
 >
 > {{{
 > @@SQL_MODE:
 STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
 > }}}
 >
 > Mainly: STRICT_TRANS_TABLES. MariaDB 10.2.4+ has the STRICT_TRANS_TABLES
 by default...

 Thanks! I'm not sure it's related to `STRICT_TRANS_TABLES` though, as
 WordPress specifically disables this and other incompatible modes as of
 [27072] / #26847.

 It's interesting that the failure messages are the exact opposite of what
 I had in the ticket description.

 MySQL 8.0.17 changes from `bigint(20)` to `bigint`:
 {{{
 Tests_dbDelta::test_column_type_change
 Failed asserting that two arrays are equal.
 --- Expected
 +++ Actual
 @@ @@
  Array (
 -    'wptests_dbdelta_test.id' => 'Changed type of wptests_dbdelta_test.id
 from bigint(20) to int(11)'
 +    'wptests_dbdelta_test.id' => 'Changed type of wptests_dbdelta_test.id
 from bigint to int(11)'
  )
 }}}

 MariaDB 10.5.15 changes from `bigint` to `bigint(20)`:
 {{{
 Tests_dbDelta::test_column_type_change
 Failed asserting that two arrays are identical.
 --- Expected
 +++ Actual
 @@ @@
  Array &0 (
 -    'wptests_dbdelta_test.id' => 'Changed type of wptests_dbdelta_test.id
 from bigint to int(11)'
 +    'wptests_dbdelta_test.id' => 'Changed type of wptests_dbdelta_test.id
 from bigint(20) to int(11)'
  )
 }}}

 It also looks like the same tests do successfully pass on another host:
 https://make.wordpress.org/hosting/test-results/r52797/cloudingbot-r52797/

 I think the test changes in [47184] may need some adjustment, specifically
 this check:
 {{{
 if ( version_compare( $db_version, '8.0.17', '<' ) ) {
         // Prior to MySQL 8.0.17, default width of 20 digits was used:
 BIGINT(20).
         $this->bigint_display_width = '(20)';
 }
 }}}
 However, it's not quite clear to me why this works for me locally with
 MariaDB 10.4.12, as well as on some hosts with MariaDB 10.5.15, but not on
 the one with the failures.

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

From noreply at wordpress.org  Wed Mar  9 10:40:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 10:40:51 -0000
Subject: [wp-trac] [WordPress Trac] #55352: Improve cache key generation in
 WP_Term_Query
Message-ID: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>

#55352: Improve cache key generation in WP_Term_Query
--------------------------+----------------------------
 Reporter:  spacedmonkey  |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:  Future Release
Component:  Taxonomy      |    Version:  4.7
 Severity:  normal        |   Keywords:
  Focuses:  performance   |
--------------------------+----------------------------
 Using the WP_Term_Query, caches are generated using the args passed to the
 class instance. However, there are a number of params passed, that would
 not affect the cache but would create a new cache key. Couple of example
 of these are.

 - pad_counts
 - update_term_meta_cache

 These params can be removed from the cache key with no affect to cache.

 There are other params such as slug and term_taxonomy_id, that can be both
 string and array. If all these were convert to arrays, it would improve
 the likelyhood that would be a cache hit.

 There are likely more wins to be had to improve caches here.

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

From noreply at wordpress.org  Wed Mar  9 10:42:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 10:42:15 -0000
Subject: [wp-trac] [WordPress Trac] #55352: Improve cache key generation
 in WP_Term_Query
In-Reply-To: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
References: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
Message-ID: <071.21078ae033650f3efd51538dc96a2956@wordpress.org>

#55352: Improve cache key generation in WP_Term_Query
------------------------------------------+-----------------------------
 Reporter:  spacedmonkey                  |       Owner:  (none)
     Type:  enhancement                   |      Status:  new
 Priority:  normal                        |   Milestone:  Future Release
Component:  Taxonomy                      |     Version:  4.7
 Severity:  normal                        |  Resolution:
 Keywords:  needs-patch needs-unit-tests  |     Focuses:  performance
------------------------------------------+-----------------------------
Changes (by spacedmonkey):

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


Comment:

 CC @peterwilsoncc

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

From noreply at wordpress.org  Wed Mar  9 10:45:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 10:45:25 -0000
Subject: [wp-trac] [WordPress Trac] #55353: Theme Twenty-Eleven - issue in
 image block in styles option
Message-ID: <054.ce1e9580b6a57fa37ec66387a66965a2@wordpress.org>

#55353: Theme Twenty-Eleven - issue in image block in styles option
--------------------------+-----------------------------------------
 Reporter:  kajalgohel    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Themes        |    Version:
 Severity:  normal        |   Keywords:  needs-patch has-screenshots
  Focuses:                |
--------------------------+-----------------------------------------
 In twenty-eleven theme, the image size option values of Image block is
 overlapped, and the **Large** text is not seen properly. actually the
 **g** word of **Large** text is not seen proper.

 For better understanding I provide the screenshot of that.

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

From noreply at wordpress.org  Wed Mar  9 10:45:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 10:45:54 -0000
Subject: [wp-trac] [WordPress Trac] #55353: Theme Twenty-Eleven - issue
 in image block in styles option
In-Reply-To: <054.ce1e9580b6a57fa37ec66387a66965a2@wordpress.org>
References: <054.ce1e9580b6a57fa37ec66387a66965a2@wordpress.org>
Message-ID: <069.8669124d27086c518ffb735b3ec0976c@wordpress.org>

#55353: Theme Twenty-Eleven - issue in image block in styles option
-----------------------------------------+------------------------------
 Reporter:  kajalgohel                   |       Owner:  (none)
     Type:  defect (bug)                 |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Themes                       |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  needs-patch has-screenshots  |     Focuses:
-----------------------------------------+------------------------------
Changes (by kajalgohel):

 * Attachment "Screenshot 2022-03-09 at 2.03.31 PM.png" added.


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

From noreply at wordpress.org  Wed Mar  9 10:46:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 10:46:53 -0000
Subject: [wp-trac] [WordPress Trac] #55353: Theme Twenty-Eleven - issue
 in image block in styles option
In-Reply-To: <054.ce1e9580b6a57fa37ec66387a66965a2@wordpress.org>
References: <054.ce1e9580b6a57fa37ec66387a66965a2@wordpress.org>
Message-ID: <069.935f051e3db3325b16bb6789b1cbd86f@wordpress.org>

#55353: Theme Twenty-Eleven - issue in image block in styles option
-------------------------------------------------+-------------------------
 Reporter:  kajalgohel                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch has-screenshots needs-   |     Focuses:
  design-feedback                                |
-------------------------------------------------+-------------------------
Changes (by kajalgohel):

 * keywords:  needs-patch has-screenshots => needs-patch has-screenshots
     needs-design-feedback


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

From noreply at wordpress.org  Wed Mar  9 10:53:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 10:53:21 -0000
Subject: [wp-trac] [WordPress Trac] #49364: dbDelta() should not change
 display width for integer data types on MySQL 8.0.17+
In-Reply-To: <058.57d558b174285895243858ce4a230956@wordpress.org>
References: <058.57d558b174285895243858ce4a230956@wordpress.org>
Message-ID: <073.4436f621f8deab5d5f12710485f22c50@wordpress.org>

#49364: dbDelta() should not change display width for integer data types on MySQL
8.0.17+
----------------------------+---------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Database        |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------

Comment (by JavierCasares):

 I can try to change the SQL_MODE in my machine (I don't have anything in
 this machine, is only to do tests). So I can try and check changing this
 option.

 I'll do a manual test and leave the report here.

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

From noreply at wordpress.org  Wed Mar  9 11:12:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 11:12:50 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.f3da73a46cf9f4e5cd50dd777851f7b1@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------+---------------------
 Reporter:  kajalgohel               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------
Changes (by kajalgohel):

 * Attachment "#55338.2.patch" added.

 width decrease by 1% and float: left removed.

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

From noreply at wordpress.org  Wed Mar  9 11:13:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 11:13:21 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.e2555c0e67dea0cfbbe0f89c2829d6e0@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------------------+-------------------------
 Reporter:  kajalgohel                           |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:
  design-feedback                                |
-------------------------------------------------+-------------------------
Changes (by kajalgohel):

 * keywords:  has-patch needs-testing => has-patch needs-testing needs-
     design-feedback


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

From noreply at wordpress.org  Wed Mar  9 11:33:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 11:33:35 -0000
Subject: [wp-trac] [WordPress Trac] #55354: wordpress 5.9 with php 8.1
Message-ID: <061.b1f6d6c45e1f7889811f7f263e001a55@wordpress.org>

#55354: wordpress 5.9 with php 8.1
-------------------------------+-----------------------------
 Reporter:  vbss2018wordpress  |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  General            |    Version:  5.9.1
 Severity:  normal             |   Keywords:
  Focuses:                     |
-------------------------------+-----------------------------
 wordpress 5.9.1 does not work with php 8.1
 php database not found

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

From noreply at wordpress.org  Wed Mar  9 11:40:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 11:40:00 -0000
Subject: [wp-trac] [WordPress Trac] #49364: dbDelta() should not change
 display width for integer data types on MySQL 8.0.17+
In-Reply-To: <058.57d558b174285895243858ce4a230956@wordpress.org>
References: <058.57d558b174285895243858ce4a230956@wordpress.org>
Message-ID: <073.23faf643f9206894a483e18000eb9179@wordpress.org>

#49364: dbDelta() should not change display width for integer data types on MySQL
8.0.17+
----------------------------+---------------------
 Reporter:  SergeyBiryukov  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Database        |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------

Comment (by JavierCasares):

 Well... after testing it without the `STRICT_TRANS_TABLES` it gave me the
 same errors... so, no, it seems not to be that. I'm going to do some more
 testing and configurations.

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

From noreply at wordpress.org  Wed Mar  9 11:53:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 11:53:32 -0000
Subject: [wp-trac] [WordPress Trac] #55353: Theme Twenty-Eleven - issue
 in image block in Image size option (was: Theme Twenty-Eleven - issue in
 image block in styles option)
In-Reply-To: <054.ce1e9580b6a57fa37ec66387a66965a2@wordpress.org>
References: <054.ce1e9580b6a57fa37ec66387a66965a2@wordpress.org>
Message-ID: <069.ba1e189cbd43e7a21607eddad77936f7@wordpress.org>

#55353: Theme Twenty-Eleven - issue in image block in Image size option
-------------------------------------------------+-------------------------
 Reporter:  kajalgohel                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch has-screenshots needs-   |     Focuses:
  design-feedback                                |
-------------------------------------------------+-------------------------

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

From noreply at wordpress.org  Wed Mar  9 13:36:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 13:36:51 -0000
Subject: [wp-trac] [WordPress Trac] #30377: wp_check_filetype is broken
 when checking urls with parameters
In-Reply-To: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
References: <056.c092dedebd826c904e4a06f6059bc1b1@wordpress.org>
Message-ID: <071.ad4619a869f37820aa3212a42e0d91fa@wordpress.org>

#30377: wp_check_filetype is broken when checking urls with parameters
-------------------------------------------------+-------------------------
 Reporter:  supercleanse                         |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-patch                                    |
-------------------------------------------------+-------------------------

Comment (by SergeyBiryukov):

 Replying to [comment:64 Ruxton]:
 > If patch 3 is the solution you want, should we refresh that and include
 the tests from John's patch? Would that get us to a better place?

 Yes, I think that would be the preferred direction here.

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

From noreply at wordpress.org  Wed Mar  9 13:51:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 13:51:48 -0000
Subject: [wp-trac] [WordPress Trac] #55354: wordpress 5.9 with php 8.1
In-Reply-To: <061.b1f6d6c45e1f7889811f7f263e001a55@wordpress.org>
References: <061.b1f6d6c45e1f7889811f7f263e001a55@wordpress.org>
Message-ID: <076.c8a164003dda6886ded02b887c35b441@wordpress.org>

#55354: wordpress 5.9 with php 8.1
-------------------------------+------------------------
 Reporter:  vbss2018wordpress  |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Database           |     Version:  5.9.1
 Severity:  normal             |  Resolution:  duplicate
 Keywords:  php81              |     Focuses:
-------------------------------+------------------------
Changes (by SergeyBiryukov):

 * keywords:   => php81
 * resolution:   => duplicate
 * status:  new => closed
 * component:  General => Database
 * milestone:  Awaiting Review =>


Comment:

 Hi there, welcome back to WordPress Trac! Thanks for the report.

 Looks like you've submitted a similar ticket before: #55208, let's
 continue there.

 Just to clarify, while WordPress 5.9.x is not ''fully'' compatible with
 PHP 8.1, it does succesfully run on that version in general, with some
 deprecation notices, as seen in [https://github.com/WordPress/wordpress-
 develop/runs/5473490381?check_suite_focus=true#step:20:1 automated test
 runs].

 You can find more details in this post:
 [https://make.wordpress.org/core/2022/01/10/wordpress-5-9-and-php-8-0-8-1/
 WordPress 5.9 and PHP 8.0-8.1].

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

From noreply at wordpress.org  Wed Mar  9 13:57:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 13:57:55 -0000
Subject: [wp-trac] [WordPress Trac] #55208: WordPress 5.9 on PHP 8.1
In-Reply-To: <061.0ce7a45d468f27bdf6ae05f5e7849b2e@wordpress.org>
References: <061.0ce7a45d468f27bdf6ae05f5e7849b2e@wordpress.org>
Message-ID: <076.d7043b14b386261997aad052e80a4e34@wordpress.org>

#55208: WordPress 5.9 on PHP 8.1
-------------------------------+------------------------------
 Reporter:  vbss2018wordpress  |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Upgrade/Install    |     Version:  5.9
 Severity:  normal             |  Resolution:
 Keywords:  php81              |     Focuses:
-------------------------------+------------------------------
Changes (by SergeyBiryukov):

 * keywords:   => php81


Comment:

 Hi there, welcome back to WordPress Trac! Thanks for the report.

 Just to clarify, while WordPress 5.9.x is not ''fully'' compatible with
 PHP 8.1, it does succesfully run on that version in general, with some
 deprecation notices, as seen in [https://github.com/WordPress/wordpress-
 develop/runs/5473490381?check_suite_focus=true#step:20:1 automated test
 runs].

 You can find more details in this post:
 [https://make.wordpress.org/core/2022/01/10/wordpress-5-9-and-php-8-0-8-1/
 WordPress 5.9 and PHP 8.0-8.1].

 I think the issue might be specific to your server configuration. If you
 need help with your site, I would suggest trying the support forums:
 https://wordpress.org/support/forums/.

 #51988 might also be related.

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

From noreply at wordpress.org  Wed Mar  9 14:03:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 14:03:04 -0000
Subject: [wp-trac] [WordPress Trac] #48644: Establish guidelines for
 button order
In-Reply-To: <050.cf5f54b222bbdf09d47c69a2f77220ee@wordpress.org>
References: <050.cf5f54b222bbdf09d47c69a2f77220ee@wordpress.org>
Message-ID: <065.ce9dff34355f4b5c52603fdf5d6035d3@wordpress.org>

#48644: Establish guidelines for button order
-------------------------------------------------+-------------------------
 Reporter:  drw158                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Administration                       |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-design-feedback a11y-          |     Focuses:  ui,
  proximity                                      |  accessibility
-------------------------------------------------+-------------------------
Changes (by afercia):

 * keywords:  needs-design-feedback => needs-design-feedback a11y-proximity


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

From noreply at wordpress.org  Wed Mar  9 14:06:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 14:06:54 -0000
Subject: [wp-trac] [WordPress Trac] #55351: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.800b911ae628dfad4064e3217fe6242f@wordpress.org>
References: <059.800b911ae628dfad4064e3217fe6242f@wordpress.org>
Message-ID: <074.f08f2e24dd0b34caae84529178906a41@wordpress.org>

#55351: The New Layout Fix For Plugin Install Page
-----------------------------+--------------------------------------
 Reporter:  sharjeelkhanvmi  |       Owner:  (none)
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Plugins          |     Version:  5.9.1
 Severity:  normal           |  Resolution:  duplicate
 Keywords:  has-screenshots  |     Focuses:  ui, css, administration
-----------------------------+--------------------------------------
Changes (by SergeyBiryukov):

 * status:  new => closed
 * resolution:   => duplicate
 * focuses:  ui, css, ui-copy => ui, css, administration
 * component:  General => Plugins
 * milestone:  Awaiting Review =>


Comment:

 Hi there, welcome back to WordPress Trac!

 It looks like you've submitted a similar ticket before: #55272, let's
 continue there.

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

From noreply at wordpress.org  Wed Mar  9 14:07:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 14:07:11 -0000
Subject: [wp-trac] [WordPress Trac] #55272: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
References: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
Message-ID: <074.186ff1c52efef49b434f1830b43ba564@wordpress.org>

#55272: The New Layout Fix For Plugin Install Page
-------------------------------------+-------------------------------------
 Reporter:  sharjeelkhanvmi          |       Owner:  (none)
     Type:  enhancement              |      Status:  reopened
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Plugins                  |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  reporter-feedback        |     Focuses:  ui, css,
  needs-design-feedback              |  administration
-------------------------------------+-------------------------------------
Changes (by SergeyBiryukov):

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


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

From noreply at wordpress.org  Wed Mar  9 15:01:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 15:01:05 -0000
Subject: [wp-trac] [WordPress Trac] #54905: PHP notice while accessing
 Customizer
In-Reply-To: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
References: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
Message-ID: <066.583884b2180b9520763f003052a8ed7a@wordpress.org>

#54905: PHP notice while accessing Customizer
-------------------------------------------------+-------------------------
 Reporter:  Boniu91                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  5.9.2
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info                                   |
-------------------------------------------------+-------------------------

Comment (by huskyr):

 I'm having the same issue without the WooCommerce plugin, with a custom
 theme. I don't get the issue when switching to one of the standard themes.
 Is there a workaround without waiting for the upgrade?

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

From noreply at wordpress.org  Wed Mar  9 15:05:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 15:05:48 -0000
Subject: [wp-trac] [WordPress Trac] #55333: PHP Notice in
 strip_fragment_from_url() when schemeless URI is passed
In-Reply-To: <048.25aa8f86a7de9a1a0f3e9340346a5763@wordpress.org>
References: <048.25aa8f86a7de9a1a0f3e9340346a5763@wordpress.org>
Message-ID: <063.a46550a99b0e8a56c11d5b764baa6f0d@wordpress.org>

#55333: PHP Notice in strip_fragment_from_url() when schemeless URI is passed
--------------------------+---------------------
 Reporter:  dd32          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Canonical     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Wed Mar  9 15:06:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 15:06:23 -0000
Subject: [wp-trac] [WordPress Trac] #55333: PHP Notice in
 strip_fragment_from_url() when schemeless URI is passed
In-Reply-To: <048.25aa8f86a7de9a1a0f3e9340346a5763@wordpress.org>
References: <048.25aa8f86a7de9a1a0f3e9340346a5763@wordpress.org>
Message-ID: <063.a678eb24d36fddbe23c8a2bcf5aa7476@wordpress.org>

#55333: PHP Notice in strip_fragment_from_url() when schemeless URI is passed
--------------------------+-----------------------------
 Reporter:  dd32          |       Owner:  SergeyBiryukov
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  6.0
Component:  Canonical     |     Version:
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52833" 52833]:
 {{{
 #!CommitTicketReference repository="" revision="52833"
 Canonical: Check if the URL scheme exists in `strip_fragment_from_url()`.

 This avoids an "Undefined index" PHP notice when a schemeless URI is
 passed.

 Props dd32, SergeyBiryukov.
 Fixes #55333.
 }}}

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

From noreply at wordpress.org  Wed Mar  9 15:13:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 15:13:31 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in
 releases without a global theme auto-update setting renders installations
 insecure
In-Reply-To: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
References: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
Message-ID: <072.5939faf8492fb51b7d4a0143b03425a9@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
-------------------------------+-----------------------
 Reporter:  bertvandepoel      |       Owner:  pbiron
     Type:  enhancement        |      Status:  assigned
 Priority:  normal             |   Milestone:  6.0
Component:  Upgrade/Install    |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+-----------------------

Comment (by JosVelasco):

 An alternative would be to send a reminder in the e-mail that includes an
 update with a new bundled theme to activate automatic updates.

 Also, maybe include the suggestion in the WordPress Site Health as well.

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

From noreply at wordpress.org  Wed Mar  9 15:14:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 15:14:28 -0000
Subject: [wp-trac] [WordPress Trac] #55355: Typo in wp_parse_url()
 description
Message-ID: <058.e52f7667345cd88706ac3cb46f78749b@wordpress.org>

#55355: Typo in wp_parse_url() description
----------------------------+----------------------------------------
 Reporter:  SergeyBiryukov  |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  6.0
Component:  HTTP API        |    Version:  4.7
 Severity:  trivial         |   Keywords:  needs-patch good-first-bug
  Focuses:  docs            |
----------------------------+----------------------------------------
 `wp_parse_url()` description includes this sentence:

 > Secondly, across various PHP versions, schemeless URLs starting
 containing a ":" in the query are being handled inconsistently.

 "starting containing" appears to be a typo, it should probably be just
 "containing" instead.

 Follow-up to [38726] / #36356.

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

From noreply at wordpress.org  Wed Mar  9 15:59:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 15:59:48 -0000
Subject: [wp-trac] [WordPress Trac] #55272: The New Layout Fix For
 Plugin Install Page
In-Reply-To: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
References: <059.77915a7719fefa82183f9912ec945915@wordpress.org>
Message-ID: <074.594f286af4c9906c1aa89f17e0dec45a@wordpress.org>

#55272: The New Layout Fix For Plugin Install Page
-------------------------------------+-------------------------------------
 Reporter:  sharjeelkhanvmi          |       Owner:  (none)
     Type:  enhancement              |      Status:  reopened
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Plugins                  |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  reporter-feedback        |     Focuses:  ui, css,
  needs-design-feedback              |  administration
-------------------------------------+-------------------------------------

Comment (by joyously):

 I do not agree that the actionable elements should be moved.
 The current way is that the title is first (clickable to get to plugin
 page), followed by the buttons to More Details or Install Now. This is
 good for visually parsing the page.
 If you move the buttons to the bottom, the user has more to parse to find
 the buttons.

 I think this page is fine. Don't try to fix what is not broken.

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

From noreply at wordpress.org  Wed Mar  9 16:58:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 16:58:09 -0000
Subject: [wp-trac] [WordPress Trac] #55353: issue in image block in
 Image size option (was: Theme Twenty-Eleven - issue in image block in Image
 size option)
In-Reply-To: <054.ce1e9580b6a57fa37ec66387a66965a2@wordpress.org>
References: <054.ce1e9580b6a57fa37ec66387a66965a2@wordpress.org>
Message-ID: <069.7a6c6aa6352fda9995bfa25523f73ee8@wordpress.org>

#55353: issue in image block in Image size option
-----------------------------+--------------------------------
 Reporter:  kajalgohel       |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Editor           |     Version:
 Severity:  normal           |  Resolution:  reported-upstream
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+--------------------------------
Changes (by sabernhardt):

 * status:  new => closed
 * component:  Themes => Editor
 * milestone:  Awaiting Review =>
 * keywords:  needs-patch has-screenshots needs-design-feedback => has-
     screenshots
 * resolution:   => reported-upstream


Comment:

 Thanks for the report! I see the same with the lowercase ''g'' in "Large"
 and "Image" in Chrome/Windows.

 This is a problem with the block editor, not the theme. The GitHub
 repository already has an issue for it, and it still needs to be fixed
 there. If you would like to add to the conversation, see:
 https://github.com/WordPress/gutenberg/issues/27194

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

From noreply at wordpress.org  Wed Mar  9 17:15:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 17:15:12 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.12c6dc2de1cb8a74e898eae20f19046a@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------------------+-------------------------
 Reporter:  kajalgohel                           |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:
  design-feedback                                |
-------------------------------------------------+-------------------------
Changes (by sabernhardt):

 * Attachment "55338.3.patch" added.

 moving `display: inline-block` to (only) the second `.entry-meta` div

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

From noreply at wordpress.org  Wed Mar  9 17:51:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 17:51:50 -0000
Subject: [wp-trac] [WordPress Trac] #55356: Use safecss_filter_attr()
 instead of wp_strip_all_tags() in wp_get_layout_style()
Message-ID: <058.9be881feebf632f30b5f6d8b3964ad18@wordpress.org>

#55356: Use safecss_filter_attr() instead of wp_strip_all_tags() in
wp_get_layout_style()
----------------------------+-----------------------------
 Reporter:  grapplerulrich  |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Formatting      |    Version:  5.9
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 Now that [https://core.trac.wordpress.org/ticket/46197 #46197] has been
 patched, `safecss_filter_attr()` can be used instead of
 `wp_strip_all_tags()`.

 Introduced in [https://github.com/WordPress/gutenberg/pull/33359
 Gutenberg#33359].


 https://github.com/WordPress/WordPress/blob/5.9-branch/wp-includes/block-
 supports/layout.php#L57

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

From noreply at wordpress.org  Wed Mar  9 18:23:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 18:23:40 -0000
Subject: [wp-trac] [WordPress Trac] #55357: Add object_id property to
 WP_Term class
Message-ID: <056.7fe5b6eb2da6e602c92dd9f1fec29be1@wordpress.org>

#55357: Add object_id property to WP_Term class
--------------------------+------------------------------------------------
 Reporter:  spacedmonkey  |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Taxonomy      |    Version:
 Severity:  normal        |   Keywords:  php81 needs-patch needs-unit-tests
  Focuses:                |
--------------------------+------------------------------------------------
 When calling `get_terms` and `WP_Term_Query` with `fields` equal to
 `all_with_object_id`, the array of `WP_Term` objects that are returned,
 also have a `object_id` property set. This property is not defined as part
 of the class. WordPress should not be defining dynamically properties like
 this.

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

From noreply at wordpress.org  Wed Mar  9 18:31:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 18:31:11 -0000
Subject: [wp-trac] [WordPress Trac] #55358: Passing int term term_exists
 parent param not respected
Message-ID: <056.053df80178f2a2e14c198dd898dde7a0@wordpress.org>

#55358: Passing int term term_exists parent param not respected
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  (none)
  spacedmonkey           |
     Type:  defect       |     Status:  new
  (bug)                  |
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Taxonomy     |    Version:
 Severity:  normal       |   Keywords:  needs-patch needs-unit-tests good-
  Focuses:               |  first-bug
-------------------------+-------------------------------------------------
 If a developer calls terms_exists, with an int as term and parent as an
 int, the parent value is not respected. So example this will not work.

 {{{#!php
  $term = term_exists( 123, 'category', 1);
 }}}

 The code will check to see if term 123 exists, but will ignore parent
 value. This may result in correct / unexpected results.

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

From noreply at wordpress.org  Wed Mar  9 18:33:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 18:33:47 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.10d19f68893854e8260960ab7c5efcd2@wordpress.org>

#36949: Term exists should use get_terms internally
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  2.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note needs-testing                             |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 While working on this ticket, I found a weird behaviour. If you pass an
 int value as the term, parent value is not respected. I have created issue
 for this behaviour. #55358

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

From noreply at wordpress.org  Wed Mar  9 18:43:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 18:43:08 -0000
Subject: [wp-trac] [WordPress Trac] #14148: wp_get_attachment_url() is
 not url encoding
In-Reply-To: <052.842e78081d022e44455551aa59ca71c3@wordpress.org>
References: <052.842e78081d022e44455551aa59ca71c3@wordpress.org>
Message-ID: <067.f420145a15716ca80b9c465cbba6fd68@wordpress.org>

#14148: wp_get_attachment_url() is not url encoding
-------------------------------------------------+-------------------------
 Reporter:  danorton                             |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Media                                |     Version:  3.0
 Severity:  major                                |  Resolution:
 Keywords:  has-patch needs-testing dev-         |     Focuses:
  feedback has-unit-tests                        |
-------------------------------------------------+-------------------------

Comment (by Mte90):

 I did a PR https://github.com/WordPress/wordpress-develop/pull/2377 that
 include a unit test but just use `àìòù` and I am using `rawurlencode`.

 Probably can be improved and added more tests but is now open for
 feedbacks.

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

From noreply at wordpress.org  Wed Mar  9 19:03:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 19:03:48 -0000
Subject: [wp-trac] [WordPress Trac] #54905: PHP notice while accessing
 Customizer
In-Reply-To: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
References: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
Message-ID: <066.8b7ade65699487ad67b6d8432638bf92@wordpress.org>

#54905: PHP notice while accessing Customizer
-------------------------------------------------+-------------------------
 Reporter:  Boniu91                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  5.9.2
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info                                   |
-------------------------------------------------+-------------------------

Comment (by ironprogrammer):

 Hi, @huskyr:

 As this ticket addresses a PHP notice, it shouldn't impact site
 performance or the frontend. If the notice is visible in the admin UI, you
 could disable `WP_DEBUG` or `WP_DEBUG_DISPLAY` in `wp-config.php`.

 I'm not aware of a workaround or fix you could apply to the custom theme,
 but if you wanted the proposed fix sooner than it ships, then you could
 apply the patch directly.

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

From noreply at wordpress.org  Wed Mar  9 19:16:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 19:16:10 -0000
Subject: [wp-trac] [WordPress Trac] #55359: get_option return value wrong
Message-ID: <052.f58357c9eaf3e06cc65da3a5859e9bba@wordpress.org>

#55359: get_option return value wrong
--------------------------------+-----------------------------
 Reporter:  malthert            |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  Options, Meta APIs  |    Version:
 Severity:  normal              |   Keywords:
  Focuses:                      |
--------------------------------+-----------------------------
 https://developer.wordpress.org/reference/functions/get_option/

 says it can return scalar including integer, which is false.

 get_option can only return:
 bool|null|string|array|object

 Need to fix in phpdoc and documentation.

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

From noreply at wordpress.org  Wed Mar  9 19:22:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 19:22:51 -0000
Subject: [wp-trac] [WordPress Trac] #55359: get_option return value wrong
In-Reply-To: <052.f58357c9eaf3e06cc65da3a5859e9bba@wordpress.org>
References: <052.f58357c9eaf3e06cc65da3a5859e9bba@wordpress.org>
Message-ID: <067.a97f3c10c8283fb2fbfeedf1b87c2891@wordpress.org>

#55359: get_option return value wrong
--------------------------------+------------------------------
 Reporter:  malthert            |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Options, Meta APIs  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:
--------------------------------+------------------------------

Comment (by malthert):

 EDIT, it's actually:
 bool|string|array|object

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

From noreply at wordpress.org  Wed Mar  9 20:06:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 20:06:22 -0000
Subject: [wp-trac] [WordPress Trac] #54905: PHP notice while accessing
 Customizer
In-Reply-To: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
References: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
Message-ID: <066.969c1d78b77f0df00c8fc4e03ff442df@wordpress.org>

#54905: PHP notice while accessing Customizer
-------------------------------------------------+-------------------------
 Reporter:  Boniu91                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  5.9.2
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info has-screenshots                   |
-------------------------------------------------+-------------------------
Changes (by ironprogrammer):

 * keywords:  has-patch needs-testing has-testing-info => has-patch needs-
     testing has-testing-info has-screenshots


Comment:

 Adding screenshots that help clarify when these notices would appear. When
 the menus in question aren't enabled, their underlying markup is still
 emitted to the page, which triggers the notices.

 === Screenshots
  [[Image(https://cldup.com/dDsgVHq1mk.png, 30%)]]
  ''Classic theme active, with Menus and Widgets support.''

  [[Image(https://cldup.com/FvnX8gxkah.png, 30%)]]
  ''Block theme active (or classic theme w/o Menus and/or Widgets support),
 which triggers notice(s).''

  [[Image(https://cldup.com/E2f4skQfQR.png, 50%)]]
  ''Example DOM footprint of a disabled `customize-action` with PHP notice
 (no Customizer widgets support).''

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

From noreply at wordpress.org  Wed Mar  9 20:13:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 20:13:06 -0000
Subject: [wp-trac] [WordPress Trac] #55356: Use safecss_filter_attr()
 instead of wp_strip_all_tags() in wp_get_layout_style()
In-Reply-To: <058.9be881feebf632f30b5f6d8b3964ad18@wordpress.org>
References: <058.9be881feebf632f30b5f6d8b3964ad18@wordpress.org>
Message-ID: <073.f614424b42a1a52bfe46edd444f4c2fb@wordpress.org>

#55356: Use safecss_filter_attr() instead of wp_strip_all_tags() in
wp_get_layout_style()
----------------------------+---------------------
 Reporter:  grapplerulrich  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Formatting      |     Version:  5.9
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


Old description:

> Now that [https://core.trac.wordpress.org/ticket/46197 #46197] has been
> patched, `safecss_filter_attr()` can be used instead of
> `wp_strip_all_tags()`.
>
> Introduced in [https://github.com/WordPress/gutenberg/pull/33359
> Gutenberg#33359].
>

> https://github.com/WordPress/WordPress/blob/5.9-branch/wp-includes/block-
> supports/layout.php#L57

New description:

 Now that #46197 has been patched, `safecss_filter_attr()` can be used
 instead of `wp_strip_all_tags()`.

 Introduced in [https://github.com/WordPress/gutenberg/pull/33359
 Gutenberg#33359].


 https://github.com/WordPress/WordPress/blob/5.9-branch/wp-includes/block-
 supports/layout.php#L57

--

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

From noreply at wordpress.org  Wed Mar  9 20:18:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 20:18:04 -0000
Subject: [wp-trac] [WordPress Trac] #55333: PHP Notice in
 strip_fragment_from_url() when schemeless URI is passed
In-Reply-To: <048.25aa8f86a7de9a1a0f3e9340346a5763@wordpress.org>
References: <048.25aa8f86a7de9a1a0f3e9340346a5763@wordpress.org>
Message-ID: <063.f9ce959287c581d88af4c7b38f1572a8@wordpress.org>

#55333: PHP Notice in strip_fragment_from_url() when schemeless URI is passed
--------------------------+-----------------------------
 Reporter:  dd32          |       Owner:  SergeyBiryukov
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  6.0
Component:  Canonical     |     Version:
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------

Comment (by SergeyBiryukov):

 For reference, `strip_fragment_from_url()` was added in [35770] / #19918.

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

From noreply at wordpress.org  Wed Mar  9 20:58:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 20:58:27 -0000
Subject: [wp-trac] [WordPress Trac] #55208: WordPress 5.9 on PHP 8.1
In-Reply-To: <061.0ce7a45d468f27bdf6ae05f5e7849b2e@wordpress.org>
References: <061.0ce7a45d468f27bdf6ae05f5e7849b2e@wordpress.org>
Message-ID: <076.74bd1f195c83fcc2211f67029d1baeb4@wordpress.org>

#55208: WordPress 5.9 on PHP 8.1
-------------------------------+------------------------------
 Reporter:  vbss2018wordpress  |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Upgrade/Install    |     Version:  5.9
 Severity:  normal             |  Resolution:
 Keywords:  close              |     Focuses:
-------------------------------+------------------------------
Changes (by jrf):

 * keywords:  php81 => close


Comment:

 Eh.. the MySQL extension was removed from PHP when PHP 7.0 was released.


 This doesn't sound like an issue with WordPress, but as an issue with a
 misconfigured hosting account in which the (required) `mysqli` extension
 has not been enabled (on PHP 8.1 or at all).

 You may want to have a read through the documentation on installing
 WordPress: https://wordpress.org/support/article/how-to-install-wordpress/

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

From noreply at wordpress.org  Wed Mar  9 20:59:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 20:59:19 -0000
Subject: [wp-trac] [WordPress Trac] #55357: Add object_id property to
 WP_Term class
In-Reply-To: <056.7fe5b6eb2da6e602c92dd9f1fec29be1@wordpress.org>
References: <056.7fe5b6eb2da6e602c92dd9f1fec29be1@wordpress.org>
Message-ID: <071.d0ae095c92ded2830645322e85c79ee0@wordpress.org>

#55357: Add object_id property to WP_Term class
------------------------------------------------+--------------------------
 Reporter:  spacedmonkey                        |       Owner:  (none)
     Type:  defect (bug)                        |      Status:  new
 Priority:  normal                              |   Milestone:  Awaiting
                                                |  Review
Component:  Taxonomy                            |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  php82 needs-patch needs-unit-tests  |     Focuses:
------------------------------------------------+--------------------------
Changes (by jrf):

 * keywords:  php81 needs-patch needs-unit-tests => php82 needs-patch needs-
     unit-tests


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

From noreply at wordpress.org  Wed Mar  9 21:33:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 21:33:37 -0000
Subject: [wp-trac] [WordPress Trac] #55288: Site Editor on 5.9.1 fails
 to find homepage template for FSE themes, on WP subdirectory installation
In-Reply-To: <055.066d0ca728e3fb5959c659d12bba3c2b@wordpress.org>
References: <055.066d0ca728e3fb5959c659d12bba3c2b@wordpress.org>
Message-ID: <070.9d0f254da0493e6679a10cba18db16c8@wordpress.org>

#55288: Site Editor on 5.9.1 fails to find homepage template for FSE themes, on WP
subdirectory installation
--------------------------+---------------------------------------
 Reporter:  andronocean   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:  administration, template
--------------------------+---------------------------------------

Comment (by westonruter):

 I'm also seeing this issue. My WP install is in a subdirectory (using the
 [https://github.com/GoogleChromeLabs/wordpressdev/
 GoogleChromeLabs/wordpressdev] environment).

 My home URL is `http://wordpressdev.lndo.site/` but my site URL is
 `https://wordpressdev.lndo.site/core-dev/src/`.

 When I open the Site Editor at `https://wordpressdev.lndo.site/core-
 dev/src/wp-admin/site-editor.php` the console gives an error:

 {{{
 Mixed Content: The page at 'https://wordpressdev.lndo.site/core-dev/src
 /wp-admin/site-editor.php' was loaded over HTTPS, but requested an
 insecure resource 'http://wordpressdev.lndo.site/core-dev/src/?_wp-find-
 template=true'. This request has been blocked; the content must be served
 over HTTPS.
 }}}

 The request using HTTP instead of HTTPS is the problem for me. If I try
 manually going to `https://wordpressdev.lndo.site/core-dev/src/?_wp-find-
 template=true` then the request succeeds. I haven't been able to pinpoint
 where the wrong URL scheme is being supplied.

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

From noreply at wordpress.org  Wed Mar  9 22:37:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 09 Mar 2022 22:37:04 -0000
Subject: [wp-trac] [WordPress Trac] #42916: Terms for taxonomy with
 show_in_quick_edit = false still load in inline data
In-Reply-To: <050.fc9de16bceda865d19fceb02648cc2ac@wordpress.org>
References: <050.fc9de16bceda865d19fceb02648cc2ac@wordpress.org>
Message-ID: <065.39e442c62fce15b0d24fd16336656198@wordpress.org>

#42916: Terms for taxonomy with show_in_quick_edit = false still load in inline
data
-------------------------------------+--------------------------
 Reporter:  jazbek                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:  4.9.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  performance
-------------------------------------+--------------------------
Description changed by SergeyBiryukov:

Old description:

> The show_in_quick_edit property was introduced for taxonomies in 4.2 with
> changeset:
>
> https://core.trac.wordpress.org/changeset/31307
>
> This changeset removed the taxonomy from the inline edit form, but the
> terms for the taxonomy are still being populated in the data for each row
> via the `get_inline_data()` function, which only respects
> `$taxonomy->show_ui`.
>
> One reason people may want to remove a taxonomy from quick edit is for
> performance reasons, when the number of terms fore each post are huge.
> However, the terms are still being loaded, and the page can take a huge
> performance hit.
>
> For example, I have a custom post type where each one is assigned
> thousands of zip codes via a custom taxonomy. I set show_in_quick_edit to
> false on the taxonomy, but the post listing was still loading very slow.
> I looked at the source code, and saw thousands of zip codes being
> rendered in a hidden div on each row.

New description:

 The show_in_quick_edit property was introduced for taxonomies in 4.2 with
 changeset: [31307].

 This changeset removed the taxonomy from the inline edit form, but the
 terms for the taxonomy are still being populated in the data for each row
 via the `get_inline_data()` function, which only respects
 `$taxonomy->show_ui`.

 One reason people may want to remove a taxonomy from quick edit is for
 performance reasons, when the number of terms fore each post are huge.
 However, the terms are still being loaded, and the page can take a huge
 performance hit.

 For example, I have a custom post type where each one is assigned
 thousands of zip codes via a custom taxonomy. I set show_in_quick_edit to
 false on the taxonomy, but the post listing was still loading very slow. I
 looked at the source code, and saw thousands of zip codes being rendered
 in a hidden div on each row.

--

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

From noreply at wordpress.org  Thu Mar 10 00:14:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 00:14:12 -0000
Subject: [wp-trac] [WordPress Trac] #55360: Add limit to query in
 WP_Tax_Query
Message-ID: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>

#55360: Add limit to query in WP_Tax_Query
--------------------------+-----------------------------
 Reporter:  spacedmonkey  |      Owner:  spacedmonkey
     Type:  enhancement   |     Status:  assigned
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Taxonomy      |    Version:  4.7
 Severity:  normal        |   Keywords:
  Focuses:  performance   |
--------------------------+-----------------------------
 The call to get_terms in WP_Tax_Query, does not currently have a limit
 set. This because some taxonomies are hierarchical and could have nested
 terms. But for none hierarchical taxonomies, a limit can and should be
 set. This limit will improve query performance and will improve likely of
 hitting an existing term query cache.

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

From noreply at wordpress.org  Thu Mar 10 00:14:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 00:14:14 -0000
Subject: [wp-trac] [WordPress Trac] #55288: Site Editor on 5.9.1 fails
 to find homepage template for FSE themes, on WP subdirectory installation
In-Reply-To: <055.066d0ca728e3fb5959c659d12bba3c2b@wordpress.org>
References: <055.066d0ca728e3fb5959c659d12bba3c2b@wordpress.org>
Message-ID: <070.cdf8502e8cda28d99a1c26c5b9ee4bd7@wordpress.org>

#55288: Site Editor on 5.9.1 fails to find homepage template for FSE themes, on WP
subdirectory installation
--------------------------+---------------------------------------
 Reporter:  andronocean   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:  administration, template
--------------------------+---------------------------------------

Comment (by westonruter):

 I don't get this issue in Gutenberg, however.

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

From noreply at wordpress.org  Thu Mar 10 00:21:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 00:21:24 -0000
Subject: [wp-trac] [WordPress Trac] #55360: Add limit to query in
 WP_Tax_Query
In-Reply-To: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
References: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
Message-ID: <071.73cc328c6b6d35a95bc2e11773318eaa@wordpress.org>

#55360: Add limit to query in WP_Tax_Query
--------------------------+------------------------------
 Reporter:  spacedmonkey  |       Owner:  spacedmonkey
     Type:  enhancement   |      Status:  assigned
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Taxonomy      |     Version:  4.7
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  performance
--------------------------+------------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-10 at 00.19.50.png" added.

 After patch

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

From noreply at wordpress.org  Thu Mar 10 00:22:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 00:22:00 -0000
Subject: [wp-trac] [WordPress Trac] #55360: Add limit to query in
 WP_Tax_Query
In-Reply-To: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
References: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
Message-ID: <071.1c82cf8145d1aba146ff216602ad083b@wordpress.org>

#55360: Add limit to query in WP_Tax_Query
--------------------------+------------------------------
 Reporter:  spacedmonkey  |       Owner:  spacedmonkey
     Type:  enhancement   |      Status:  assigned
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Taxonomy      |     Version:  4.7
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  performance
--------------------------+------------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-10 at 00.20.13.png" added.

 Before patch

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

From noreply at wordpress.org  Thu Mar 10 01:16:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 01:16:03 -0000
Subject: [wp-trac] [WordPress Trac] #37189: In wp_term_query on cache ids
In-Reply-To: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
References: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
Message-ID: <071.6ee5d2292b66e70e17ba37a0e614af9d@wordpress.org>

#37189: In wp_term_query on cache ids
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  4.6
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:
  tests commit                                   |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch needs-testing has-unit-tests => has-patch needs-
     testing has-unit-tests commit
 * owner:  (none) => spacedmonkey
 * status:  new => assigned
 * milestone:  Future Release => 6.0


Comment:

 The [https://github.com/WordPress/wordpress-develop/pull/2367/ linked pull
 request] looks good for commit. I'll leave you to do the honors
 @spacedmonkey

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

From noreply at wordpress.org  Thu Mar 10 01:27:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 01:27:04 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.0f033dce0f649c2061947f513a71a6c2@wordpress.org>

#36949: Term exists should use get_terms internally
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  2.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note needs-testing commit                      |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests needs-dev-note needs-testing => has-
     patch has-unit-tests needs-dev-note needs-testing commit


Comment:

 Marking this as commit ready for the [https://github.com/WordPress
 /wordpress-develop/pull/2318 linked pull request], @spacedmonkey are you
 able to do the honors?

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

From noreply at wordpress.org  Thu Mar 10 01:54:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 01:54:18 -0000
Subject: [wp-trac] [WordPress Trac] #53705: Plugin upgrade deletes files
 from other in-progress upgrades
In-Reply-To: <051.3864d53d4c261f039340696626d8cf5c@wordpress.org>
References: <051.3864d53d4c261f039340696626d8cf5c@wordpress.org>
Message-ID: <066.8edd47fd81a5c1bf2981bbe873d2a1c0@wordpress.org>

#53705: Plugin upgrade deletes files from other in-progress upgrades
-----------------------------+---------------------
 Reporter:  bpayton          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  5.8
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+---------------------

Comment (by peterwilsoncc):

 @bpayton Have you tested the patch you supplied in production on WP.com or
 did you end up taking another approach/wait for the core fix?

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

From noreply at wordpress.org  Thu Mar 10 03:03:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 03:03:21 -0000
Subject: [wp-trac] [WordPress Trac] #54984: wp_update_user doesn't work
 properly with current user instance
In-Reply-To: <051.92bddc0d644a48440a60de1fba687faf@wordpress.org>
References: <051.92bddc0d644a48440a60de1fba687faf@wordpress.org>
Message-ID: <066.d28e0f18f7f24c6df7db756ec1acb7de@wordpress.org>

#54984: wp_update_user doesn't work properly with current user instance
--------------------------+---------------------
 Reporter:  oztaser       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Users         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------
Changes (by peterwilsoncc):

 * Attachment "54984.diff" added.


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

From noreply at wordpress.org  Thu Mar 10 03:12:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 03:12:36 -0000
Subject: [wp-trac] [WordPress Trac] #54984: wp_update_user doesn't work
 properly with current user instance
In-Reply-To: <051.92bddc0d644a48440a60de1fba687faf@wordpress.org>
References: <051.92bddc0d644a48440a60de1fba687faf@wordpress.org>
Message-ID: <066.d64d047be9eb40efe4d19e5cbdd09870@wordpress.org>

#54984: wp_update_user doesn't work properly with current user instance
--------------------------+---------------------
 Reporter:  oztaser       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Users         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------

Comment (by peterwilsoncc):

 Thanks for providing an mu-plugin as a proof of concept, @oztaser, it was
 a great help.

 The bug seems to be caused by the combination of two things:
 * objects are passed by reference
 * since 5.8 WP has used the same user object for the current user whenever
 possible.

 The result is that in this block of code, the old user data object is no
 such thing: it's simply a reference to the modified object that has been
 passed to the function.


 {{{#!php
 <?php

 // In `wp_update_user()`

 // First, get all of the original fields.
 $user_obj = get_userdata( $user_id );
 if ( ! $user_obj ) {
         return new WP_Error( 'invalid_user_id', __( 'Invalid user ID.' )
 );
 }
 }}}

 [https://github.com/WordPress/WordPress/blob/fcf2500f49341dfce84c3ac68d963a6a92874f64
 /wp-includes/user.php#L2350-L2354 reference]

 ----

 In [attachment:"54984.diff"] I've worked around this by creating a new
 `WP_User` object for the purpose of obtaining the old data.

 However, I am not sure this is an ideal solution as `get_userdata()` and
 related functions are pluggable so there is no way of knowing if the data
 returned by `new WP_User( $user_id )` is what is returned by
 `get_userdata()`.

 A technique to force an uncached copy of the user data is what is needed
 to fix this though.

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

From noreply at wordpress.org  Thu Mar 10 03:59:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 03:59:50 -0000
Subject: [wp-trac] [WordPress Trac] #55239: Filter hook
 wp_sitemaps_taxonomies_entry passes Term ID not Object
In-Reply-To: <050.d931e8ac6d10c2579ccf77882f678437@wordpress.org>
References: <050.d931e8ac6d10c2579ccf77882f678437@wordpress.org>
Message-ID: <065.f70b6aaccd5a68c6b61ed3ff983abc9a@wordpress.org>

#55239: Filter hook wp_sitemaps_taxonomies_entry passes Term ID not Object
-------------------------------------+----------------------------
 Reporter:  RavanH                   |       Owner:  peterwilsoncc
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Sitemaps                 |     Version:  5.9.1
 Severity:  minor                    |  Resolution:  fixed
 Keywords:  has-patch needs-refresh  |     Focuses:  docs
-------------------------------------+----------------------------
Changes (by peterwilsoncc):

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


Comment:

 In [changeset:"52834" 52834]:
 {{{
 #!CommitTicketReference repository="" revision="52834"
 Sitemaps: Pass term object to `wp_sitemaps_taxonomies_entry` filter.

 Add a forth parameter to the `wp_sitemaps_taxonomies_entry` filter to pass
 the entire `WP_Term` object.

 Correct the documentation for the second parameter of the
 `wp_sitemaps_taxonomies_entry` filter to indicate it is a term ID rather
 than term object.

 Props RavanH, swissspidy, audrasjb.
 Fixes #55239.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 04:07:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 04:07:18 -0000
Subject: [wp-trac] [WordPress Trac] #53705: Plugin upgrade deletes files
 from other in-progress upgrades
In-Reply-To: <051.3864d53d4c261f039340696626d8cf5c@wordpress.org>
References: <051.3864d53d4c261f039340696626d8cf5c@wordpress.org>
Message-ID: <066.122d615cdf84c668e4e94bb7fc6e6898@wordpress.org>

#53705: Plugin upgrade deletes files from other in-progress upgrades
-----------------------------+---------------------
 Reporter:  bpayton          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  5.8
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+---------------------

Comment (by bpayton):

 @peterwilsoncc yes, the patch was tested in production on a kind of
 standalone WP.com site (separate from the large multisite instance run by
 WP.com). The standalone sites, basically core WP plus a number of platform
 mu-plugins, are where we were seeing this issue. With the patch applied,
 we no longer experienced this issue, but because we prefer to run
 unaltered WP core releases, we did not apply the patch to all sites in
 production.

 In the meantime, we were able to reduce this issue enough to live with it.
 It is a core issue but was greatly exacerbated by Jetpack making
 concurrent plugin update attempts. Those attempts could conflict with
 other Jetpack-driven plugin update attempts or core auto update attempts.
 We addressed this by updating Jetpack to share WP's `auto_updater` lock
 and adding some other Jetpack-specific locking to avoid conflicts.

 This evening, I reran
 [https://core.trac.wordpress.org/ticket/53705#comment:7 the repro
 instructions] after you messaged and still encountered the errors
 mentioned in this ticket. After applying the patch, repeatedly rerunning
 the repro instructions yielded none of the errors.

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

From noreply at wordpress.org  Thu Mar 10 05:20:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 05:20:06 -0000
Subject: [wp-trac] [WordPress Trac] #54174: Twenty Twenty-One: @media
 (prefers-reduced-motion) in sass/07-utilities/a11y.scss breaks some plugins
In-Reply-To: <060.0f73c0dd7192c7bf0f4a7f6cce838ac2@wordpress.org>
References: <060.0f73c0dd7192c7bf0f4a7f6cce838ac2@wordpress.org>
Message-ID: <075.fc24812dc334365306339ca109dd79ad@wordpress.org>

#54174: Twenty Twenty-One: @media (prefers-reduced-motion) in
sass/07-utilities/a11y.scss breaks some plugins
-------------------------------------+-------------------------------------
 Reporter:  gregoiresailland         |       Owner:  peterwilsoncc
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:  5.6
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-patch needs-testing  |     Focuses:  ui, accessibility, css
-------------------------------------+-------------------------------------
Changes (by peterwilsoncc):

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


Comment:

 In [changeset:"52835" 52835]:
 {{{
 #!CommitTicketReference repository="" revision="52835"
 Twenty Twenty-One: Reverse logic for `prefers-reduced-motion` media query.

 Reverse the logic of the `prefers-reduced-motion` to enable transitions
 based on `no-preference` rather than disable them based on the `reduce`
 preference. This removes the need to disable transitions with the `!
 important` tag and unintended interactions with plugins as a result.

 Props gregoiresailland, sabernhardt, ryokuhi.
 Fixes #54174.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 06:39:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 06:39:27 -0000
Subject: [wp-trac] [WordPress Trac] #55355: Typo in wp_parse_url()
 description
In-Reply-To: <058.e52f7667345cd88706ac3cb46f78749b@wordpress.org>
References: <058.e52f7667345cd88706ac3cb46f78749b@wordpress.org>
Message-ID: <073.511214f154dfd47527b29c4b730eb50a@wordpress.org>

#55355: Typo in wp_parse_url() description
---------------------------------------------+-----------------------
 Reporter:  SergeyBiryukov                   |       Owner:  audrasjb
     Type:  defect (bug)                     |      Status:  assigned
 Priority:  normal                           |   Milestone:  6.0
Component:  HTTP API                         |     Version:  4.7
 Severity:  trivial                          |  Resolution:
 Keywords:  good-first-bug has-patch commit  |     Focuses:  docs
---------------------------------------------+-----------------------
Changes (by mukesh27):

 * keywords:  good-first-bug has-patch => good-first-bug has-patch commit
 * owner:  (none) => audrasjb
 * status:  new => assigned


Comment:

 Hi there!

 The patch looks fine to me and ready to marge in Core.

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

From noreply at wordpress.org  Thu Mar 10 06:54:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 06:54:36 -0000
Subject: [wp-trac] [WordPress Trac] #55356: Use safecss_filter_attr()
 instead of wp_strip_all_tags() in wp_get_layout_style()
In-Reply-To: <058.9be881feebf632f30b5f6d8b3964ad18@wordpress.org>
References: <058.9be881feebf632f30b5f6d8b3964ad18@wordpress.org>
Message-ID: <073.5eb8e0fce3d80813c6f41e7ce21e0734@wordpress.org>

#55356: Use safecss_filter_attr() instead of wp_strip_all_tags() in
wp_get_layout_style()
------------------------------+---------------------
 Reporter:  grapplerulrich    |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  6.0
Component:  Formatting        |     Version:  5.9
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+---------------------
Changes (by mukesh27):

 * keywords:  has-patch => has-patch commit


Comment:

 Hi there!

 Thanks for the ticket and patch.

 The patch looks good to me. Mark as `commit`.

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

From noreply at wordpress.org  Thu Mar 10 07:36:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 07:36:34 -0000
Subject: [wp-trac] [WordPress Trac] #55361: WordPress database error
 Deadlock found when trying to get lock on wp_get_global_styles_svg_filters
Message-ID: <051.582d560266492f6fe783d1213d401ddf@wordpress.org>

#55361: WordPress database error Deadlock found when trying to get lock on
wp_get_global_styles_svg_filters
--------------------------+-----------------------------
 Reporter:  BackuPs       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 I don't know where to ask this question but i have these error messages in
 my log file.

 The template just calls wp_body_open after the body tag. I can see a
 filter is added for body open that renders svg filters in the
 default_filters.php in wordpress.

 https://share.getcloudapp.com/5zuLpONl

 https://share.getcloudapp.com/6quZ7Jvz

 But how do i get rid of these entries in the error log and where are they
 coming from?  It seems that wordpress is triggering these.

 Can you please advice on how to get rid of these messages in the error log


                 WordPress database error Deadlock found when trying to get
 lock; try restarting transaction for query DELETE FROM `wp_options` WHERE
 `option_name` = '_transient_global_styles_svg_filters_champion' made by
 require('wp-blog-header.php'), require_once('wp-includes/template-
 loader.php'), include('/themes/champion/template_sections.php'),
 get_header, locate_template, load_template,
 require_once('/themes/champion/header.php'), wp_body_open,
 do_action('wp_body_open'), WP_Hook->do_action, WP_Hook->apply_filters,
 wp_global_styles_render_svg_filters, wp_get_global_styles_svg_filters,
 get_transient, delete_option

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

From noreply at wordpress.org  Thu Mar 10 08:57:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 08:57:31 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid use of
 display and float together in style.css file
Message-ID: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
---------------------------+---------------------------------------
 Reporter:  kajalgohel     |      Owner:  (none)
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Bundled Theme  |    Version:
 Severity:  normal         |   Keywords:  has-screenshots has-patch
  Focuses:                 |
---------------------------+---------------------------------------
 In the theme Twenty Thirteen, there is an invalid use of float and display
 inline-block together in the CSS style sheet.


 {{{
 .attachment .entry-title {
         display: inline-block;
         float: left;
         font: 300 italic 30px "Source Sans Pro", Helvetica, sans-serif;
         margin: 0;
 }
 }}}


 {{{
 .comment-reply-title small a {
         color: #131310;
         display: inline-block;
         float: right;
         height: 16px;
         overflow: hidden;
         width: 16px;
 }
 }}}

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

From noreply at wordpress.org  Thu Mar 10 08:59:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 08:59:06 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.429cd40d8759ec1d0b4dc0c8225ad390@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
---------------------------------------+------------------------------
 Reporter:  kajalgohel                 |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:  Awaiting Review
Component:  Bundled Theme              |     Version:
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:
---------------------------------------+------------------------------
Changes (by kajalgohel):

 * Attachment "Screenshot 2022-03-10 at 2.22.27 PM.png" added.

 display: inline-block property is removed, and design is not breaking.
 display: none override the display: inline-block property

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

From noreply at wordpress.org  Thu Mar 10 09:00:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 09:00:01 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.c3978444bab01b22197096107f2348fa@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
---------------------------------------+------------------------------
 Reporter:  kajalgohel                 |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:  Awaiting Review
Component:  Bundled Theme              |     Version:
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:
---------------------------------------+------------------------------
Changes (by kajalgohel):

 * Attachment "Screenshot 2022-03-10 at 2.19.47 PM.png" added.

 display: inline-block property is removed, design is not breaking.

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

From noreply at wordpress.org  Thu Mar 10 09:01:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 09:01:08 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.f367964eddef0ad38586959d92cfecd6@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
---------------------------------------+------------------------------
 Reporter:  kajalgohel                 |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:  Awaiting Review
Component:  Bundled Theme              |     Version:
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:
---------------------------------------+------------------------------
Changes (by kajalgohel):

 * Attachment "#55362.patch" added.

 display: inline-block property is removed.

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

From noreply at wordpress.org  Thu Mar 10 09:01:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 09:01:37 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.7a0bf00dd964649aed31c9daf25110f1@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
-------------------------------------------------+-------------------------
 Reporter:  kajalgohel                           |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Bundled Theme                        |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch needs-     |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by kajalgohel):

 * keywords:  has-screenshots has-patch => has-screenshots has-patch needs-
     testing


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

From noreply at wordpress.org  Thu Mar 10 09:43:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 09:43:50 -0000
Subject: [wp-trac] [WordPress Trac] #55363: Date Format for Month "F"
 incorrect when using Site Language of "English (South Africa)"
Message-ID: <054.0e74fec27f7bc9afbc6015da8f660b1d@wordpress.org>

#55363: Date Format for Month "F" incorrect when using Site Language of "English
(South Africa)"
--------------------------+-----------------------------
 Reporter:  milkisgood    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Date/Time     |    Version:
 Severity:  normal        |   Keywords:  needs-patch
  Focuses:                |
--------------------------+-----------------------------
 Date Format for Month "F" incorrect when using Site Language of "English
 (South Africa)"

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

From noreply at wordpress.org  Thu Mar 10 09:43:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 09:43:54 -0000
Subject: [wp-trac] [WordPress Trac] #53218: Make apply_filters() variadic
In-Reply-To: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
References: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
Message-ID: <070.abfc226e721e237c7b6dd6c06aa46766@wordpress.org>

#53218: Make apply_filters() variadic
------------------------------------------+---------------------
 Reporter:  johnbillion                   |       Owner:  (none)
     Type:  enhancement                   |      Status:  new
 Priority:  normal                        |   Milestone:  6.0
Component:  Plugins                       |     Version:  5.3
 Severity:  normal                        |  Resolution:
 Keywords:  has-patch early dev-feedback  |     Focuses:
------------------------------------------+---------------------

Comment (by dingo_d):

 This would be a great addition, especially from the perspective of static
 analysis tools like PHPStan.

 Currently, you get tons of false positives when passing more than two
 arguments, and you need to ignore the rule altogether, which diminishes
 the use of the tool.

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

From noreply at wordpress.org  Thu Mar 10 09:44:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 09:44:41 -0000
Subject: [wp-trac] [WordPress Trac] #55363: Date Format for Month "F"
 incorrect when using Site Language of "English (South Africa)"
In-Reply-To: <054.0e74fec27f7bc9afbc6015da8f660b1d@wordpress.org>
References: <054.0e74fec27f7bc9afbc6015da8f660b1d@wordpress.org>
Message-ID: <069.66d28d0555b37702c11a363bafcd20e1@wordpress.org>

#55363: Date Format for Month "F" incorrect when using Site Language of "English
(South Africa)"
--------------------------+------------------------------
 Reporter:  milkisgood    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Date/Time     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by milkisgood):

 * Attachment "photo_2022-03-10_11-05-43.jpg" added.

 Note the Month output is incorrect

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

From noreply at wordpress.org  Thu Mar 10 09:50:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 09:50:59 -0000
Subject: [wp-trac] [WordPress Trac] #54905: PHP notice while accessing
 Customizer
In-Reply-To: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
References: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
Message-ID: <066.20c461c9d1c8516ca691dc5f7bc96ebe@wordpress.org>

#54905: PHP notice while accessing Customizer
-------------------------------------------------+-------------------------
 Reporter:  Boniu91                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  5.9.2
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info has-screenshots                   |
-------------------------------------------------+-------------------------

Comment (by huskyr):

 Hey [comment:18 ironprogrammer], thanks for the extensive explanation and
 screenshots! You're right, i don't see the notice on my production server
 because WP_DEBUG is indeed disabled there.

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

From noreply at wordpress.org  Thu Mar 10 09:54:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 09:54:48 -0000
Subject: [wp-trac] [WordPress Trac] #49687: wp_mail() - Why is no
 envelope sender defined?
In-Reply-To: <048.3946f892e5f69f332e0c5196f58bf2c6@wordpress.org>
References: <048.3946f892e5f69f332e0c5196f58bf2c6@wordpress.org>
Message-ID: <063.6fcea71e7a17d0f564e41063a859cd2f@wordpress.org>

#49687: wp_mail() - Why is no envelope sender defined?
----------------------------------------+------------------------------
 Reporter:  vbbp                        |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Mail                        |     Version:  5.4
 Severity:  minor                       |  Resolution:
 Keywords:  dev-feedback needs-testing  |     Focuses:
----------------------------------------+------------------------------

Comment (by kub1x):

 Replying to [comment:5 SergeyBiryukov]:
 > Hi there, welcome to WordPress Trac! Thanks for the report.
 >
 > Replying to [ticket:49687 vbbp]:
 > > Unfortunately, the current implementation of wp_mail() explicitly sets
 that 3rd parameter to false, which prevents the envelope sender from being
 set (see https://core.trac.wordpress.org/browser/trunk/src/wp-
 includes/pluggable.php?rev=47494#L358).
 >
 > Just noting that this was an intentional change in [38286] / #37736.

 Without the envelope sender being set (falling back to some default
 value), the requests are being rejected. Namely "sezman.cz" and "ovh.net"
 SMTP servers do reject those messages (log line below). Gmail won't look
 at the envelope sender and gladly accept the header from the message
 header.

 {{{
 Mar 10 10:36:52 localhost sm-mta[1763825]: 229JUjTK112345:
 to=<myemailaddress at seznam.cz>, ctladdr=<www-data at localhost.localdomain>
 (33/33), delay=14:06:07, xdelay=00:00:00, mailer=esmtp, pri=7770908,
 relay=mx2.seznam.cz., dsn=4.0.0, stat=Deferred: 451 4.4.8 Unroutable email
 address.
 }}}

 To me it causes just more harm. Only harm to be correct ;) Removing the
 false fixes everything in my case. But still have to go with coding it
 into plugin using the phpmailer_init action to keep the change
 permanent...

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

From noreply at wordpress.org  Thu Mar 10 10:27:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 10:27:41 -0000
Subject: [wp-trac] [WordPress Trac] #54953: Custom css variables in
 theme.json have different keys in 5.9
In-Reply-To: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
References: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
Message-ID: <064.6e795bf485b94999631392dc8f5fa0c7@wordpress.org>

#54953: Custom css variables in theme.json have different keys in 5.9
--------------------------+---------------------
 Reporter:  walbo         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.2
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------

Comment (by oandregal):

 WordPress 5.8 had a bug by which front-end styles and editor styles were
 different. We fixed this in 5.9. See more details at
 https://github.com/WordPress/gutenberg/issues/39155#issuecomment-1063880553

 The plan is to update the devnote for theme.json v2 including this bugfix
 https://make.wordpress.org/core/2022/01/08/updates-for-settings-styles-
 and-theme-json/

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

From noreply at wordpress.org  Thu Mar 10 10:46:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 10:46:18 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
Message-ID: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-----------------------------+-----------------------------
 Reporter:  afercia          |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Quick/Bulk Edit  |    Version:
 Severity:  normal           |   Keywords:  a11y-proximity
  Focuses:  accessibility    |
-----------------------------+-----------------------------
 See tracking ticket #40822.
 See also #45972.

 In the Quick Edit and Bulk Edit forms, the Submit and Cancel buttons are
 placed at the opposite sides of the form.

 As mentioned in the tracking ticket #40822, proximity of related
 information is an universal design principle which benefits everyone and
 it's particularly important for users with a reduced visual field, low
 vision, or other vision or cognitive impairments.

 User interface controls that are logically grouped should be placed close
 each other. For more details and related WCAG recommendations, please see
 the tracking ticket #40822.

 The primary action button should be on the left. See the detailed design
 feedback in https://core.trac.wordpress.org/ticket/40822#comment:9

 In #45972 / [44757] the Comment form was changed to align the button on
 the left. See screenshots:

 Comment form before:

 [[Image(http://cldup.com/9vOa-gSotk.png)]]

 Comment form after:

 [[Image(http://cldup.com/KymCNBNbsL.png)]]

 The same change should be implemented for the Quick Edit and Bulk Edit
 forms.

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

From noreply at wordpress.org  Thu Mar 10 10:54:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 10:54:07 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.a0b6b988845efec78a5cc5cec9573c73@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-----------------------------+------------------------------
 Reporter:  afercia          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  a11y-proximity   |     Focuses:  accessibility
-----------------------------+------------------------------
Changes (by afercia):

 * Attachment "55364.diff" added.


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

From noreply at wordpress.org  Thu Mar 10 10:55:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 10:55:56 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.893e26352391da69932f3f979285d40c@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------
Changes (by afercia):

 * keywords:  a11y-proximity => a11y-proximity has-patch has-screenshots


Comment:

 [attachment:"55364.diff"] switches the buttons order and aligns them to
 the left. See screenshots below.

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

From noreply at wordpress.org  Thu Mar 10 10:56:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 10:56:24 -0000
Subject: [wp-trac] [WordPress Trac] #37189: In wp_term_query on cache ids
In-Reply-To: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
References: <056.9cb46f772aefbfd9a9c1002a26f3bac6@wordpress.org>
Message-ID: <071.a8df4e0935509e81619845e69e5dc3f9@wordpress.org>

#37189: In wp_term_query on cache ids
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  4.6
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:
  tests commit                                   |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

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


Comment:

 In [changeset:"52836" 52836]:
 {{{
 #!CommitTicketReference repository="" revision="52836"
 Taxonomy: Only store term_ids and object_ids in `WP_Term_Query` query
 caches.

 The query cache currently implemented in `WP_Term_Query` caches the final
 output of the query, depending on what fields are requested. This is
 wasteful, as if a user requests `fields` => `all`, then an unlimited array
 of `WP_Term` objects could be stored in the object cache. Instead of
 storing the whole WP_Term object, this change only the term_id is stored.
 To get an array the full WP_Term objects, the `_prime_term_caches`
 function is called with an array of ids. In instances where a persistent
 object cache is not in use, then this will result in another SQL query to
 be run. After `_prime_term_caches` is called if this term is requested
 again in the same page load, then it will already be loaded into memory.
 If a user runs `WP_Term_Query` with the fields param set to
 `all_with_object_id`, an array of objects containing both the term_id and
 object_ids are stored in cache.

 This change also improves the logic to load term meta caches. This change
 ensures that term meta is always primed for all terms loaded in the term
 query.

 Props Spacedmonkey, boonebgorges, jbpaul17, peterwilsoncc, flixos90,
 pbearne.
 Fixes #37189.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 10:56:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 10:56:36 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.2181a98dc873570531d8eee29ea37bc5@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------
Changes (by afercia):

 * Attachment "quick edit.png" added.

 Quick edit form with the patch applied.

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

From noreply at wordpress.org  Thu Mar 10 10:56:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 10:56:59 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.a067593412f7d45d9630ef2a5e615a97@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------
Changes (by afercia):

 * Attachment "bulk edit.png" added.

 Bulk edit form with the patch applied.

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

From noreply at wordpress.org  Thu Mar 10 11:03:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 11:03:03 -0000
Subject: [wp-trac] [WordPress Trac] #55244: Non-editable title.
In-Reply-To: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
References: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
Message-ID: <066.1d86b9aa12b37ec298453b014833d24f@wordpress.org>

#55244: Non-editable title.
--------------------------+----------------------------------------
 Reporter:  krilike       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility, javascript
--------------------------+----------------------------------------

Comment (by krilike):

 Hey @juhise

 Please try the following steps:

 1) Open the post.
 2) Add a couple of paragraphs.
 3) Important! Click somewhere around here https://prnt.sc/FP8tdoBgjAjc (so
 as not to touch the text).
 4) Press CTRL+A to highlight the paragraphs, as in this screenshot
 https://prnt.sc/b34gZ8ISRuNG
 5) Try to edit the heading.


 ----
 Env:
 Wordpress 5.9.1
 Firefox 97.0.2, Chrome 99.0.4844.51, Opera 84.0.4316.31, Edge 99.0.1150.36
 Windows 11
 Themes: Twenty Twenty-One, Twenty Twenty-Two
 Gutenberg Editor
 Plugins: ---

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

From noreply at wordpress.org  Thu Mar 10 11:06:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 11:06:25 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.706c29d652c5c3103db9ff5f959ad8fb@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------

Comment (by afercia):

 Note: props should go also to @landwire who made
 [https://github.com/WordPress/wordpress-develop/pull/601 a PR on the
 GitHub repository] a while ago. See ticket:40822#comment:22

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

From noreply at wordpress.org  Thu Mar 10 11:06:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 11:06:48 -0000
Subject: [wp-trac] [WordPress Trac] #55359: get_option return value wrong
In-Reply-To: <052.f58357c9eaf3e06cc65da3a5859e9bba@wordpress.org>
References: <052.f58357c9eaf3e06cc65da3a5859e9bba@wordpress.org>
Message-ID: <067.b3c29e86a79c0081b7295bcafca3ca89@wordpress.org>

#55359: get_option return value wrong
--------------------------------+------------------------------
 Reporter:  malthert            |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Options, Meta APIs  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:  docs
--------------------------------+------------------------------
Changes (by johnbillion):

 * focuses:   => docs


Comment:

 This function can return a value of any type because of the `$default`
 parameter:

 {{{#!php
 get_option( 'i_dont_exist', 123 );
 }}}

 The `@return` documentation could do with improvement here but the return
 types look correct.

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

From noreply at wordpress.org  Thu Mar 10 11:25:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 11:25:38 -0000
Subject: [wp-trac] [WordPress Trac] #55355: Typo in wp_parse_url()
 description
In-Reply-To: <058.e52f7667345cd88706ac3cb46f78749b@wordpress.org>
References: <058.e52f7667345cd88706ac3cb46f78749b@wordpress.org>
Message-ID: <073.49ab0e30eb84f59f587e5c25721f4bdf@wordpress.org>

#55355: Typo in wp_parse_url() description
---------------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov                   |       Owner:  hellofromTonya
     Type:  defect (bug)                     |      Status:  reviewing
 Priority:  normal                           |   Milestone:  6.0
Component:  HTTP API                         |     Version:  4.7
 Severity:  trivial                          |  Resolution:
 Keywords:  good-first-bug has-patch commit  |     Focuses:  docs
---------------------------------------------+-----------------------------
Changes (by hellofromTonya):

 * owner:  audrasjb => hellofromTonya
 * status:  assigned => reviewing


Comment:

 Hello @mehedi890,

 Welcome back to WordPress Core Trac. Congrats on your first contribution
 🌟 🎉 .

 Thank you for the patching this ticket. I reviewed and approved
 [https://github.com/WordPress/wordpress-develop/pull/2397 PR 2397]. As
 @mukesh27 noted, it's ready for commit.

 What's the next step? I'll prepare a commit and add your change to the
 WordPress codebase.

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

From noreply at wordpress.org  Thu Mar 10 11:31:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 11:31:40 -0000
Subject: [wp-trac] [WordPress Trac] #55355: Typo in wp_parse_url()
 description
In-Reply-To: <058.e52f7667345cd88706ac3cb46f78749b@wordpress.org>
References: <058.e52f7667345cd88706ac3cb46f78749b@wordpress.org>
Message-ID: <073.a6bacb5bfc2e1def2b44c7027ebea2f7@wordpress.org>

#55355: Typo in wp_parse_url() description
---------------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov                   |       Owner:  hellofromTonya
     Type:  defect (bug)                     |      Status:  reviewing
 Priority:  normal                           |   Milestone:  6.0
Component:  HTTP API                         |     Version:  4.7
 Severity:  trivial                          |  Resolution:
 Keywords:  good-first-bug has-patch commit  |     Focuses:  docs
---------------------------------------------+-----------------------------

Comment (by mehedi890):

 Thank you @hellofromTonya

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

From noreply at wordpress.org  Thu Mar 10 13:08:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 13:08:34 -0000
Subject: [wp-trac] [WordPress Trac] #49412: Store filesize media metadata
In-Reply-To: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
References: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
Message-ID: <063.403685f6344ede04e7d1e0329ac22da5@wordpress.org>

#49412: Store filesize media metadata
---------------------------------------------+---------------------------
 Reporter:  Cybr                             |       Owner:  spacedmonkey
     Type:  feature request                  |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------
Changes (by spacedmonkey):

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


Comment:

 In [changeset:"52837" 52837]:
 {{{
 #!CommitTicketReference repository="" revision="52837"
 Media: Store attachment’s file size in metadata.

 Store the file size of all newly uploaded attachments, as part of the
 metadata stored in post meta. Storing file size means, developers will not
 have to resort to doing `filesize` function calls, that can be time
 consuming on assets on offloaded to services like Amazon’s S3.

 This change also introduces a new helper function called, `wp_filesize`.
 This is a wrapper around the `filesize` php function, that adds some
 helpful filters and ensures the return value is an integer.

 Props Cybr, Spacedmonkey, SergeyBiryukov, johnwatkins0, swissspidy,
 desrosj, joemcgill, azaozz, antpb, adamsilverstein, uday17035.
 Fixes #49412.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 14:25:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 14:25:57 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.1930134186cc45fe0cd0d4c92ef45cfa@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
-----------------------------------------------------+---------------------
 Reporter:  kajalgohel                               |       Owner:  (none)
     Type:  enhancement                              |      Status:  new
 Priority:  normal                                   |   Milestone:  6.0
Component:  Bundled Theme                            |     Version:
 Severity:  normal                                   |  Resolution:
 Keywords:  has-screenshots has-patch needs-testing  |     Focuses:
-----------------------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Thu Mar 10 15:39:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 15:39:25 -0000
Subject: [wp-trac] [WordPress Trac] #49746: Widening WordPress Limits
 and Compatibility
In-Reply-To: <052.fef0b722c86840b055afb9451e70e166@wordpress.org>
References: <052.fef0b722c86840b055afb9451e70e166@wordpress.org>
Message-ID: <067.d86064f10565bab863382518f65db751@wordpress.org>

#49746: Widening WordPress Limits and Compatibility
-------------------------------+------------------------------
 Reporter:  ulike123           |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:  5.4
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by antpb):

 * keywords:  has-dev-note => reporter-feedback


Comment:

 Hi @ulike123 ! Thanks for your ticket! We discussed this ticket in the
 recent media meeting and we were having some difficulty finding the issue
 you are facing.

 Which screen are you on when you are seeing the "select image" button?
 There are several places this may render so I want to make sure we are in
 alignment.

 Are you requesting better support of URL targets using the OS file
 uploader? Could you describe more about how you are using this?

 Thank you!

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

From noreply at wordpress.org  Thu Mar 10 15:46:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 15:46:55 -0000
Subject: [wp-trac] [WordPress Trac] #49729: Warning: fread() expects
 parameter 1 to be resource,
 bool given in \wp-includes\functions.php on line 5785
In-Reply-To: <054.426954a0952c78ec8a20f28e20beb2a7@wordpress.org>
References: <054.426954a0952c78ec8a20f28e20beb2a7@wordpress.org>
Message-ID: <069.32979b3aa8e386a2721321ac7625784c@wordpress.org>

#49729: Warning: fread() expects parameter 1 to be resource, bool given in \wp-
includes\functions.php on line 5785
-------------------------------+------------------------------
 Reporter:  DrLightman         |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Plugins            |     Version:  5.3.2
 Severity:  minor              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  administration
-------------------------------+------------------------------
Changes (by azouamauriac):

 * keywords:   => reporter-feedback


Comment:

 Hello @DrLightman thanks for the report, are you still able to reproduce
 this one? could you provide the steps to reproduce it?

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

From noreply at wordpress.org  Thu Mar 10 15:48:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 15:48:40 -0000
Subject: [wp-trac] [WordPress Trac] #49779: Add a filter that controls
 the size of the images on the Attachment pages
In-Reply-To: <055.52471db82a4c28b8d0e4d61896ad89af@wordpress.org>
References: <055.52471db82a4c28b8d0e4d61896ad89af@wordpress.org>
Message-ID: <070.888920c859f7e58ddc1d08700d39b6f2@wordpress.org>

#49779: Add a filter that controls the size of the images on the Attachment pages
-------------------------+------------------------------
 Reporter:  pikamander2  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Media        |     Version:
 Severity:  major        |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by joedolson):

 Is there any reason you can't resolve this problem via either editing or
 adding an attachments template to your theme?

 The theme's `attachment.php` template file allows you to pass whatever
 size you want for the attachment page; I can't see a reason you'd ever
 need to edit core files for this.

 More details: https://developer.wordpress.org/themes/template-files-
 section/attachment-template-files/

 If there's something special about the scenario that means you can't solve
 this within the theme, please provide those details.

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

From noreply at wordpress.org  Thu Mar 10 15:49:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 15:49:23 -0000
Subject: [wp-trac] [WordPress Trac] #49779: Add a filter that controls
 the size of the images on the Attachment pages
In-Reply-To: <055.52471db82a4c28b8d0e4d61896ad89af@wordpress.org>
References: <055.52471db82a4c28b8d0e4d61896ad89af@wordpress.org>
Message-ID: <070.bde0ddf170df25b3e83b20d347bb3f60@wordpress.org>

#49779: Add a filter that controls the size of the images on the Attachment pages
-------------------------------+------------------------------
 Reporter:  pikamander2        |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by joedolson):

 * keywords:   => reporter-feedback


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

From noreply at wordpress.org  Thu Mar 10 15:49:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 15:49:32 -0000
Subject: [wp-trac] [WordPress Trac] #49779: Add a filter that controls
 the size of the images on the Attachment pages
In-Reply-To: <055.52471db82a4c28b8d0e4d61896ad89af@wordpress.org>
References: <055.52471db82a4c28b8d0e4d61896ad89af@wordpress.org>
Message-ID: <070.5283e4e0103f0f8b2b3f76c38872ff30@wordpress.org>

#49779: Add a filter that controls the size of the images on the Attachment pages
-------------------------------+------------------------------
 Reporter:  pikamander2        |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  template
-------------------------------+------------------------------
Changes (by joedolson):

 * focuses:   => template


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

From noreply at wordpress.org  Thu Mar 10 15:57:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 15:57:25 -0000
Subject: [wp-trac] [WordPress Trac] #49830: Store rotation data for
 uploaded videos
In-Reply-To: <056.bf2dffc877d125deb9e118a781e08ecd@wordpress.org>
References: <056.bf2dffc877d125deb9e118a781e08ecd@wordpress.org>
Message-ID: <071.55b2cc37bdf9bf8a674c1b520115c7c0@wordpress.org>

#49830: Store rotation data for uploaded videos
--------------------------+-----------------------------
 Reporter:  spacedmonkey  |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------------
Changes (by antpb):

 * keywords:  needs-patch 2nd-opinion => needs-patch
 * type:  defect (bug) => enhancement
 * milestone:  Awaiting Review => Future Release


Comment:

 This sounds like a great enhancement and has prior prescient with the
 length property in videos. I could see more available meta being super
 useful. Marking future release for now. If anyone wants to grab this for
 6.0 feel free to ping the Media team at any time in #core-media for a
 review.

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

From noreply at wordpress.org  Thu Mar 10 16:00:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 16:00:44 -0000
Subject: [wp-trac] [WordPress Trac] #55355: Typo in wp_parse_url()
 description
In-Reply-To: <058.e52f7667345cd88706ac3cb46f78749b@wordpress.org>
References: <058.e52f7667345cd88706ac3cb46f78749b@wordpress.org>
Message-ID: <073.cdaf8e1cbf142f23cf804e6a45d8bf2d@wordpress.org>

#55355: Typo in wp_parse_url() description
---------------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov                   |       Owner:  hellofromTonya
     Type:  defect (bug)                     |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  HTTP API                         |     Version:  4.7
 Severity:  trivial                          |  Resolution:  fixed
 Keywords:  good-first-bug has-patch commit  |     Focuses:  docs
---------------------------------------------+-----------------------------
Changes (by hellofromTonya):

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


Comment:

 In [changeset:"52838" 52838]:
 {{{
 #!CommitTicketReference repository="" revision="52838"
 HTTP API: Fix typo in and improve readability of `wp_parse_url()`
 docblock.

 Removes the "starting" word from "starting containing" as this is a typo.
 Includes minor formatting adjustments to improve readability.

 Follow-up to [38726].

 Props mehedi890, SergeyBiryukov, mukesh27.
 Fixes #55355.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 16:11:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 16:11:46 -0000
Subject: [wp-trac] [WordPress Trac] #54843: Add end to end test case for
 Trash a single post and restore post from trash
In-Reply-To: <055.17005acbdcc9a6c1a08cd0e490b0b9e0@wordpress.org>
References: <055.17005acbdcc9a6c1a08cd0e490b0b9e0@wordpress.org>
Message-ID: <070.2a6d284d50d1198696a0584da76e89e4@wordpress.org>

#54843: Add end to end test case for Trash a single post and restore post from
trash
---------------------------------------------+-----------------------------
 Reporter:  pavanpatil1                      |       Owner:  hellofromTonya
     Type:  enhancement                      |      Status:  reviewing
 Priority:  normal                           |   Milestone:  6.0
Component:  Build/Test Tools                 |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------------
Changes (by hellofromTonya):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests commit
 * owner:  (none) => hellofromTonya
 * status:  new => reviewing


Comment:

 [https://github.com/WordPress/wordpress-develop/pull/2186 PR 2186] has
 been approved by @kevin940726 (Thank you Kai!). Marking for commit.
 Prepping commit now.

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

From noreply at wordpress.org  Thu Mar 10 16:27:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 16:27:11 -0000
Subject: [wp-trac] [WordPress Trac] #54843: Add end to end test case for
 Trash a single post and restore post from trash
In-Reply-To: <055.17005acbdcc9a6c1a08cd0e490b0b9e0@wordpress.org>
References: <055.17005acbdcc9a6c1a08cd0e490b0b9e0@wordpress.org>
Message-ID: <070.e2c29ae926a4274842602d3e60ce122a@wordpress.org>

#54843: Add end to end test case for Trash a single post and restore post from
trash
---------------------------------------------+-----------------------------
 Reporter:  pavanpatil1                      |       Owner:  hellofromTonya
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Build/Test Tools                 |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------------
Changes (by hellofromTonya):

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


Comment:

 In [changeset:"52839" 52839]:
 {{{
 #!CommitTicketReference repository="" revision="52839"
 Build/Test Tools: Add trash and restore of a single post e2e tests.

 Adds an end-to-end (e2e) test case for:
 * Emptying a post from the trash.
 * Restoring a post from the trash.

 Props pavanpatil1, pooja1210, justinahinon, kevin940726.
 Fixes #54843.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 16:30:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 16:30:35 -0000
Subject: [wp-trac] [WordPress Trac] #54953: Custom css variables in
 theme.json have different keys in 5.9
In-Reply-To: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
References: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
Message-ID: <064.c928753e0162b4a051209fd064e01381@wordpress.org>

#54953: Custom css variables in theme.json have different keys in 5.9
--------------------------+---------------------
 Reporter:  walbo         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.2
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------

Comment (by oandregal):

 As reported upstream the devnote has been updated and this is the correct
 behavior.

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

From noreply at wordpress.org  Thu Mar 10 16:31:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 16:31:27 -0000
Subject: [wp-trac] [WordPress Trac] #54953: Custom css variables in
 theme.json have different keys in 5.9
In-Reply-To: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
References: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
Message-ID: <064.f438d964155df551e0ed7a3855a604ae@wordpress.org>

#54953: Custom css variables in theme.json have different keys in 5.9
--------------------------+---------------------
 Reporter:  walbo         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.2
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------

Comment (by oandregal):

 I'm unable to close the issue. I can mark it as "wontfix" or "worksforme"
 labels but that feels wrong. Sharing in case anyone can close it.

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

From noreply at wordpress.org  Thu Mar 10 16:35:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 16:35:34 -0000
Subject: [wp-trac] [WordPress Trac] #49779: Add a filter that controls
 the size of the images on the Attachment pages
In-Reply-To: <055.52471db82a4c28b8d0e4d61896ad89af@wordpress.org>
References: <055.52471db82a4c28b8d0e4d61896ad89af@wordpress.org>
Message-ID: <070.701f63feff8842e7f92bff12e20c1737@wordpress.org>

#49779: Add a filter that controls the size of the images on the Attachment pages
-------------------------------+------------------------------
 Reporter:  pikamander2        |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  template
-------------------------------+------------------------------

Comment (by pikamander2):

 I'm sure that it's also possible to edit the attachment file directly, but
 adding a filter here would create a very simple, straightforward way to
 edit the image sizes that's in line with many of WordPress's other
 filters.

 A common use-case is that somebody downloads a theme, generates a child
 theme for it, and then makes a few simple edits to the child theme's
 functions.php without ever needing to dig into other files. This also
 allows them to keep their custom code consolidated in one easy place for
 easier access/review later on. Not everyone's looking for a total theme
 overhaul with customized template files.

 So while it may not be strictly necessary, I do think that it would
 beneficial for the sake of ease-of-use.

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

From noreply at wordpress.org  Thu Mar 10 17:30:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 17:30:20 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.575bf0d2dcc1addc6dc530c4b62b1ba5@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by davidbaumwald):

 In [changeset:"52840" 52840]:
 {{{
 #!CommitTicketReference repository="" revision="52840"
 Coding Standards: Fix minor alignment issue in `wp_ajax_install_theme()`.

 Follow-up to [52819].

 See #54728.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 17:35:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 17:35:03 -0000
Subject: [wp-trac] [WordPress Trac] #54725: Test tool and unit test
 improvements for 6.0
In-Reply-To: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
References: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
Message-ID: <073.1e11ea7d87c409b04745628c5e37c22f@wordpress.org>

#54725: Test tool and unit test improvements for 6.0
--------------------------------------+---------------------
 Reporter:  hellofromTonya            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------
Changes (by azouamauriac):

 * Attachment "54725.4.diff" added.

 Remove some unused variables; some history: [31014]; [29422]

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

From noreply at wordpress.org  Thu Mar 10 18:19:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 18:19:21 -0000
Subject: [wp-trac] [WordPress Trac] #42916: Terms for taxonomy with
 show_in_quick_edit = false still load in inline data
In-Reply-To: <050.fc9de16bceda865d19fceb02648cc2ac@wordpress.org>
References: <050.fc9de16bceda865d19fceb02648cc2ac@wordpress.org>
Message-ID: <065.b32808551b7ffcec4fffc4a87463d3c5@wordpress.org>

#42916: Terms for taxonomy with show_in_quick_edit = false still load in inline
data
-------------------------------------+--------------------------
 Reporter:  jazbek                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:  4.9.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  performance
-------------------------------------+--------------------------

Comment (by SergeyBiryukov):

 Hi there, welcome back to WordPress Trac!

 Thanks for the ticket, sorry it took so long for someone to get back to
 you.

 The patch does fix the issue in my testing.

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

From noreply at wordpress.org  Thu Mar 10 18:19:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 18:19:33 -0000
Subject: [wp-trac] [WordPress Trac] #49701: Quick Edit fails to populate
 taxonomy terms when show_in_quick_edit = true, and show_ui = false
In-Reply-To: <053.7075fc8321dab02b14977698926a16e8@wordpress.org>
References: <053.7075fc8321dab02b14977698926a16e8@wordpress.org>
Message-ID: <068.83864c5bde6d1128a1601992438180d7@wordpress.org>

#49701: Quick Edit fails to populate taxonomy terms when show_in_quick_edit = true,
and show_ui = false
-----------------------------+---------------------
 Reporter:  figureone        |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Quick/Bulk Edit  |     Version:  5.4
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


Old description:

> Aloha, we discovered that the `show_in_quick_edit` property is not being
> checked when populating a post's taxonomy terms in `/wp-admin/edit.php`.
> As a consequence, if `show_in_quick_edit` is true, but `show_ui` is false
> for a given taxonomy, the Quick Edit UI will not check any of the term
> checkboxes, which can result in losing existing terms when a post is
> updated via Quick Edit.
>
> Likely this was just an oversight when `show_in_quick_edit` was
> introduced here:
> https://core.trac.wordpress.org/changeset/31307
>
> And it should be an easy fix to check `show_in_quick_edit` instead of
> `show_ui` here:
> https://github.com/WordPress/WordPress/blob/5.3.2/wp-
> admin/includes/template.php#L343
> https://github.com/WordPress/WordPress/blob/5.3.2/wp-
> admin/includes/template.php#L354
>
> `show_in_quick_edit` defaults to the value of `show_ui` if it isn't
> specified, so this change shouldn't introduce any issues.
> https://github.com/WordPress/WordPress/blob/5.3.2/wp-includes/class-wp-
> taxonomy.php#L334
>
> Our use case:
> We have a taxonomy and terms defined in a plugin that is not meant to be
> edited in the WordPress UI. However, we do want users to be able to
> assign taxonomy terms to posts in the Quick Edit UI.
>
> Extra details if needed:
> When clicking the Quick Edit button, `inline-edit-post.js` refers to the
> term divs to mark the correct checkboxes:
> https://github.com/WordPress/WordPress/blob/5.3.2/wp-admin/js/inline-
> edit-post.js#L305-L316
> Term divs are echoed here:
> https://github.com/WordPress/WordPress/blob/5.3.2/wp-
> admin/includes/template.php#L343-L364

New description:

 Aloha, we discovered that the `show_in_quick_edit` property is not being
 checked when populating a post's taxonomy terms in `/wp-admin/edit.php`.
 As a consequence, if `show_in_quick_edit` is true, but `show_ui` is false
 for a given taxonomy, the Quick Edit UI will not check any of the term
 checkboxes, which can result in losing existing terms when a post is
 updated via Quick Edit.

 Likely this was just an oversight when `show_in_quick_edit` was introduced
 here:
 [31307].

 And it should be an easy fix to check `show_in_quick_edit` instead of
 `show_ui` here:
 https://github.com/WordPress/WordPress/blob/5.3.2/wp-
 admin/includes/template.php#L343
 https://github.com/WordPress/WordPress/blob/5.3.2/wp-
 admin/includes/template.php#L354

 `show_in_quick_edit` defaults to the value of `show_ui` if it isn't
 specified, so this change shouldn't introduce any issues.
 https://github.com/WordPress/WordPress/blob/5.3.2/wp-includes/class-wp-
 taxonomy.php#L334

 Our use case:
 We have a taxonomy and terms defined in a plugin that is not meant to be
 edited in the WordPress UI. However, we do want users to be able to assign
 taxonomy terms to posts in the Quick Edit UI.

 Extra details if needed:
 When clicking the Quick Edit button, `inline-edit-post.js` refers to the
 term divs to mark the correct checkboxes:
 https://github.com/WordPress/WordPress/blob/5.3.2/wp-admin/js/inline-edit-
 post.js#L305-L316
 Term divs are echoed here:
 https://github.com/WordPress/WordPress/blob/5.3.2/wp-
 admin/includes/template.php#L343-L364

--

Comment:

 Hi there, welcome back to WordPress Trac!

 Thanks for the ticket, sorry it took so long for someone to get back to
 you.

 The patch does fix the issue in my testing.

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

From noreply at wordpress.org  Thu Mar 10 18:20:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 18:20:49 -0000
Subject: [wp-trac] [WordPress Trac] #42916: Terms for taxonomy with
 show_in_quick_edit = false still load in inline data
In-Reply-To: <050.fc9de16bceda865d19fceb02648cc2ac@wordpress.org>
References: <050.fc9de16bceda865d19fceb02648cc2ac@wordpress.org>
Message-ID: <065.b13b5a9406128d1985c8a8943baeabe6@wordpress.org>

#42916: Terms for taxonomy with show_in_quick_edit = false still load in inline
data
-------------------------------------+-----------------------------
 Reporter:  jazbek                   |       Owner:  SergeyBiryukov
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:  4.9.1
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-patch needs-testing  |     Focuses:  performance
-------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52841" 52841]:
 {{{
 #!CommitTicketReference repository="" revision="52841"
 Quick/Bulk Edit: Check the `show_in_quick_edit` taxonomy property when
 populating the data for the posts list table.

 Previously, setting the `show_in_quick_edit` property to `false` removed
 the taxonomy from the inline edit form, but the terms were still being
 populated in the data for each table row via the `get_inline_data()`
 function, which only checked the `$taxonomy->show_ui` property.

 This commit:
 * Improves performance by ensuring that taxonomy terms are not
 unnecessarily populated for each table row when `show_in_quick_edit` is
 `false`.
 * Properly populates the taxonomy terms when `show_in_quick_edit` is
 `true` and `show_ui` is `false`.

 Follow-up to [31307].

 Props jazbek, figureone, sabernhardt, ovidiul, webcommsat, SergeyBiryukov.
 Fixes #42916, #49701.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 18:20:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 18:20:49 -0000
Subject: [wp-trac] [WordPress Trac] #49701: Quick Edit fails to populate
 taxonomy terms when show_in_quick_edit = true, and show_ui = false
In-Reply-To: <053.7075fc8321dab02b14977698926a16e8@wordpress.org>
References: <053.7075fc8321dab02b14977698926a16e8@wordpress.org>
Message-ID: <068.57a4810c85c92e440f61ee99258775bc@wordpress.org>

#49701: Quick Edit fails to populate taxonomy terms when show_in_quick_edit = true,
and show_ui = false
-----------------------------+-----------------------------
 Reporter:  figureone        |       Owner:  SergeyBiryukov
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  6.0
Component:  Quick/Bulk Edit  |     Version:  5.4
 Severity:  normal           |  Resolution:  fixed
 Keywords:                   |     Focuses:
-----------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52841" 52841]:
 {{{
 #!CommitTicketReference repository="" revision="52841"
 Quick/Bulk Edit: Check the `show_in_quick_edit` taxonomy property when
 populating the data for the posts list table.

 Previously, setting the `show_in_quick_edit` property to `false` removed
 the taxonomy from the inline edit form, but the terms were still being
 populated in the data for each table row via the `get_inline_data()`
 function, which only checked the `$taxonomy->show_ui` property.

 This commit:
 * Improves performance by ensuring that taxonomy terms are not
 unnecessarily populated for each table row when `show_in_quick_edit` is
 `false`.
 * Properly populates the taxonomy terms when `show_in_quick_edit` is
 `true` and `show_ui` is `false`.

 Follow-up to [31307].

 Props jazbek, figureone, sabernhardt, ovidiul, webcommsat, SergeyBiryukov.
 Fixes #42916, #49701.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 18:23:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 18:23:13 -0000
Subject: [wp-trac] [WordPress Trac] #54426: Add a "Copy URL to
 clipboard" row action in Media > Library...similar to the botton on the
 Edit Media screen
In-Reply-To: <050.9285dabd471bc0880785e0ab08880a2b@wordpress.org>
References: <050.9285dabd471bc0880785e0ab08880a2b@wordpress.org>
Message-ID: <065.3b6bca8b88e24256e2c98658452cd81d@wordpress.org>

#54426: Add a "Copy URL to clipboard" row action in Media > Library...similar to
the botton on the Edit Media screen
-------------------------------------+-------------------------------------
 Reporter:  pbiron                   |       Owner:  davidbaumwald
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-screenshots has-     |     Focuses:  ui, accessibility,
  patch needs-testing                |  javascript
-------------------------------------+-------------------------------------
Changes (by davidbaumwald):

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


Comment:

 In [changeset:"52842" 52842]:
 {{{
 #!CommitTicketReference repository="" revision="52842"
 Media: Add a "Copy URL to clipboard" function to the list table view.

 Previously, a button was added to the modal view for a single media item
 in the "grid" view to copy the file URL to the user's clipboard.  This
 change adds a similar function to the "list" view for each media item.

 Follow-up to [48232].

 Props pbiron, ravipatel, alexstine, afercia.
 Fixes #54426.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 18:42:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 18:42:02 -0000
Subject: [wp-trac] [WordPress Trac] #54426: Add a "Copy URL to
 clipboard" row action in Media > Library...similar to the botton on the
 Edit Media screen
In-Reply-To: <050.9285dabd471bc0880785e0ab08880a2b@wordpress.org>
References: <050.9285dabd471bc0880785e0ab08880a2b@wordpress.org>
Message-ID: <065.2dcb0aac808c6c23cb5bc1170a2b8e5d@wordpress.org>

#54426: Add a "Copy URL to clipboard" row action in Media > Library...similar to
the botton on the Edit Media screen
-------------------------------------+-------------------------------------
 Reporter:  pbiron                   |       Owner:  davidbaumwald
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-screenshots has-     |     Focuses:  ui, accessibility,
  patch needs-testing                |  javascript
-------------------------------------+-------------------------------------

Comment (by davidbaumwald):

 In [changeset:"52843" 52843]:
 {{{
 #!CommitTicketReference repository="" revision="52843"
 Media: Note `ClipboardJS` as a global in /js/_enqueues/admin/media.js.

 Follow-up to [52842].

 See #54426.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 19:18:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 19:18:13 -0000
Subject: [wp-trac] [WordPress Trac] #54426: Add a "Copy URL to
 clipboard" row action in Media > Library...similar to the botton on the
 Edit Media screen
In-Reply-To: <050.9285dabd471bc0880785e0ab08880a2b@wordpress.org>
References: <050.9285dabd471bc0880785e0ab08880a2b@wordpress.org>
Message-ID: <065.aec66d370d46d099d049af55bb67d014@wordpress.org>

#54426: Add a "Copy URL to clipboard" row action in Media > Library...similar to
the botton on the Edit Media screen
-------------------------------------+-------------------------------------
 Reporter:  pbiron                   |       Owner:  davidbaumwald
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-screenshots has-     |     Focuses:  ui, accessibility,
  patch needs-testing needs-dev-     |  javascript
  note                               |
-------------------------------------+-------------------------------------
Changes (by pbiron):

 * keywords:  has-screenshots has-patch needs-testing => has-screenshots
     has-patch needs-testing needs-dev-note


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

From noreply at wordpress.org  Thu Mar 10 19:20:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 19:20:06 -0000
Subject: [wp-trac] [WordPress Trac] #53032: Privacy: "Retry" action link
 on "Export Personal Data" page does not work
In-Reply-To: <057.722394d81a0a931a52db81970d332d01@wordpress.org>
References: <057.722394d81a0a931a52db81970d332d01@wordpress.org>
Message-ID: <072.11cf53247815059071aa64b8f5288473@wordpress.org>

#53032: Privacy: "Retry" action link on "Export Personal Data" page does not work
-------------------------------------+----------------------------
 Reporter:  davidbaumwald            |       Owner:  davidbaumwald
     Type:  defect (bug)             |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Privacy                  |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-patch needs-testing  |     Focuses:  javascript
-------------------------------------+----------------------------
Changes (by davidbaumwald):

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


Comment:

 In [changeset:"52846" 52846]:
 {{{
 #!CommitTicketReference repository="" revision="52846"
 Privacy: Fix "Retry" action after a personal data export failure.

 When exporting personal data for a user request, if the export fails for
 any reason, a "Retry" link is displayed inline.  However, up to this
 point, clicking this link performed no action.  This change adds the
 `export-personal-data-handle` CSS class to the link to make sure it's
 picked up by the same delegated listener as the initial action.  Clicking
 this link will now retry the export.

 Props hellofromTonya, nomnom99, rafiahmedd, SergeyBiryukov,
 hasanuzzamanshamim.
 Fixes #53032.
 }}}

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

From noreply at wordpress.org  Thu Mar 10 19:41:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 19:41:12 -0000
Subject: [wp-trac] [WordPress Trac] #49701: Quick Edit fails to populate
 taxonomy terms when show_in_quick_edit = true, and show_ui = false
In-Reply-To: <053.7075fc8321dab02b14977698926a16e8@wordpress.org>
References: <053.7075fc8321dab02b14977698926a16e8@wordpress.org>
Message-ID: <068.947f17e1810414dd6022a676873b06fa@wordpress.org>

#49701: Quick Edit fails to populate taxonomy terms when show_in_quick_edit = true,
and show_ui = false
-----------------------------+-----------------------------
 Reporter:  figureone        |       Owner:  SergeyBiryukov
     Type:  defect (bug)     |      Status:  reopened
 Priority:  normal           |   Milestone:  6.0
Component:  Quick/Bulk Edit  |     Version:  5.4
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 Reopening to review and commit the unit tests from
 [https://github.com/WordPress/wordpress-develop/pull/205 PR #205].

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

From noreply at wordpress.org  Thu Mar 10 19:41:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 19:41:53 -0000
Subject: [wp-trac] [WordPress Trac] #55365: meta field in media via REST API
Message-ID: <053.6519fbb86d9b032c7819cebb2bd39452@wordpress.org>

#55365: meta field in media via REST API
----------------------------------------+-----------------------------
 Reporter:  millerf01                   |      Owner:  (none)
     Type:  defect (bug)                |     Status:  new
 Priority:  normal                      |  Milestone:  Awaiting Review
Component:  REST API                    |    Version:
 Severity:  normal                      |   Keywords:
  Focuses:  javascript, docs, rest-api  |
----------------------------------------+-----------------------------
 Hi there,

 I found either a bug or a documentation issue.

 The codex https://developer.wordpress.org/rest-api/reference/media/ refers
 to a `meta` that is both editable and readable.

 I am writing a Gutenberg block and wanted to store data in the `meta`
 field. I am using:

 {{{
 #!div style="font-size: 80%"
 Code highlighting:
   {{{#!javascript
 apiFetch( {
                 path: '/wp/v2/media/' + mediaId,
                 method: 'POST',
                 data: {
                         title: title,
                         description: description,
                         meta: {
                              some_data: "some_value"
                         }
                 }
         } )
 }}}
 }}}

 However, it always returns an empty array as `meta`

 [[Image(https://imgur.com/a/8XcUJ5b)]]

 I also tried setting some custom field

 {{{
 #!div style="font-size: 80%"
 Code highlighting:
   {{{#!javascript

 register_meta( 'media', 'some_data', array(
         'type' => 'string',
         'description' => 'Some data',
         'single' => true,
         'show_in_rest' => true
 ) );
 }}}
 }}}

 I eventually tried  format the `meta` field I am sending

 {{{
 #!div style="font-size: 80%"
 Code highlighting:
   {{{#!javascript
 meta: [{
 some_data: "some_value"
 }]
 }}}
 }}}

 or

 {{{
 #!div style="font-size: 80%"
 Code highlighting:
   {{{#!javascript
 meta: [{
 key: "some_data",
 value: "some_value"
 }]
 }}}
 }}}

 But still nothing.

 Do you have any idea?

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

From noreply at wordpress.org  Thu Mar 10 19:43:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 19:43:57 -0000
Subject: [wp-trac] [WordPress Trac] #55365: meta field in media via REST
 API
In-Reply-To: <053.6519fbb86d9b032c7819cebb2bd39452@wordpress.org>
References: <053.6519fbb86d9b032c7819cebb2bd39452@wordpress.org>
Message-ID: <068.3c264f1286c67aea95c60989d6258486@wordpress.org>

#55365: meta field in media via REST API
--------------------------+-----------------------------------------
 Reporter:  millerf01     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  REST API      |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  javascript, docs, rest-api
--------------------------+-----------------------------------------

Comment (by millerf01):

 Sorry, here is the image I was supposed to have linked up there

 [[Image(https://i.imgur.com/RyO4eVo.png)]]

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

From noreply at wordpress.org  Thu Mar 10 20:39:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 20:39:35 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.a2ccbe29c324ad0bd99cf02a5719dc72@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by paapst):

 * keywords:  close => has-privacy-review 2nd-opinion
 * status:  closed => reopened
 * resolution:  invalid =>
 * severity:  normal => major


Comment:

 Hi @fs5ve

 Thank you for this report. I have reproduced this problem on a website
 without any additional plugins.
 I created a new user, with all kinds of extra personal information
 attached to its profile. After that, I went to "Erase personal data".  I
 entered the username, send the request to erase the data about this user.
 Then it showed "Erasure completed" and it showed a notice that no personal
 data was found for this user.

 Afterwards, I went to the menu item "Export Personal Data", entered the
 username, and voila... all the information was still there. Conclusion:
 nothing about this user has been deleted or anonimyzed.

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

From noreply at wordpress.org  Thu Mar 10 21:39:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 21:39:34 -0000
Subject: [wp-trac] [WordPress Trac] #46982: Avoid loading dot files in
 the mu-plugins directory.
In-Reply-To: <051.62106f23ba5d0cd7316d3b91702de3a5@wordpress.org>
References: <051.62106f23ba5d0cd7316d3b91702de3a5@wordpress.org>
Message-ID: <066.1b0eab92cc7097747bd1ccc4849fa5e7@wordpress.org>

#46982: Avoid loading dot files in the mu-plugins directory.
-------------------------------------------------+-------------------------
 Reporter:  dcavins                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Plugins                              |     Version:  2.8
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-refresh needs-       |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by azouamauriac):

 * keywords:  has-patch => has-patch needs-refresh needs-testing


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

From noreply at wordpress.org  Thu Mar 10 21:41:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 21:41:15 -0000
Subject: [wp-trac] [WordPress Trac] #46982: Avoid loading dot files in
 the mu-plugins directory.
In-Reply-To: <051.62106f23ba5d0cd7316d3b91702de3a5@wordpress.org>
References: <051.62106f23ba5d0cd7316d3b91702de3a5@wordpress.org>
Message-ID: <066.7ccf33e5d754c44a8e5da9427c4c4f55@wordpress.org>

#46982: Avoid loading dot files in the mu-plugins directory.
-------------------------------------------------+-------------------------
 Reporter:  dcavins                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Plugins                              |     Version:  2.8
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-refresh needs-       |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------

Comment (by azouamauriac):

 May be this is related to #41638

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

From noreply at wordpress.org  Thu Mar 10 22:17:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 22:17:43 -0000
Subject: [wp-trac] [WordPress Trac] #55366: WordPress auto-updated plugin
 with auto-updates disabled
Message-ID: <052.f3fd6e11fc81b43131a305be0476583b@wordpress.org>

#55366: WordPress auto-updated plugin with auto-updates disabled
--------------------------+-----------------------------
 Reporter:  vtxtools      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hello,

 As there are some updates that can break our site, we have automatic
 updates disabled for all plugins. Today, the plugin "Woocommerce" updated
 from version 6.3.0 to 6.3.1 automatically, causing a critical issue on our
 site. I looked at the changelog for this version, and it appears there was
 a fix for a security issue. So I am wondering if there is some criteria
 that would allow an automatic update of a plugin even if automatic updates
 are disabled. We understand the need to keep plugins up to date, I'm just
 curious if security was the reason for this unexpected behavior or if it's
 a bug.

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

From noreply at wordpress.org  Thu Mar 10 22:24:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 22:24:29 -0000
Subject: [wp-trac] [WordPress Trac] Batch modify: #52409, #54878, #54905,
 #54916, #54939, ...
In-Reply-To: <167.4d84b76e22f33cb3f6d93fe094508063@wordpress.org>
References: <167.4d84b76e22f33cb3f6d93fe094508063@wordpress.org>
Message-ID: <182.8a9619e626f3d649b0cd7a5e87ea0e2f@wordpress.org>

Batch modification to #52409, #54878, #54905, #54916, #54939, #54953, #55015, #55023, #55053, #55117, #55121, #55163, #55172, #55189, #55195, #55203, #55229, #55230, #55231, #55241, #55262 by audrasjb:
milestone to 5.9.3

Comment:
Moving to milestone 5.9.3 since we're about to release 5.9.2.

-- 
Tickets URL: <https://core.trac.wordpress.org/query?id=52409%2C54878%2C54905%2C54916%2C54939%2C54953%2C55015%2C55023%2C55053%2C55117%2C55121%2C55163%2C55172%2C55189%2C55195%2C55203%2C55229%2C55230%2C55231%2C55241%2C55262>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 10 22:36:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 22:36:50 -0000
Subject: [wp-trac] [WordPress Trac] #55366: WordPress auto-updated
 plugin with auto-updates disabled
In-Reply-To: <052.f3fd6e11fc81b43131a305be0476583b@wordpress.org>
References: <052.f3fd6e11fc81b43131a305be0476583b@wordpress.org>
Message-ID: <067.a7dd954204b235959f82cc5ab033a44a@wordpress.org>

#55366: WordPress auto-updated plugin with auto-updates disabled
--------------------------+----------------------
 Reporter:  vtxtools      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by Otto42):

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


Comment:

 The default setting for auto-updates is not "disabled". The default is to
 follow the recommendation of the WordPress.org systems. So yes, an
 automatic update was sent for WooCommerce starting to day for the security
 issue.
 https://developer.woocommerce.com/2022/03/10/woocommerce-3-5-10-6-3-1
 -security-releases/

 WordPress has had auto-updating for plugins since WordPress 3.7. You can
 read more about this here: https://make.wordpress.org/plugins/2015/03/14
 /plugin-automatic-security-updates/

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

From noreply at wordpress.org  Thu Mar 10 22:45:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 22:45:55 -0000
Subject: [wp-trac] [WordPress Trac] #55366: WordPress auto-updated
 plugin with auto-updates disabled
In-Reply-To: <052.f3fd6e11fc81b43131a305be0476583b@wordpress.org>
References: <052.f3fd6e11fc81b43131a305be0476583b@wordpress.org>
Message-ID: <067.cccf1432dca5a37497eb0c77bdba8e00@wordpress.org>

#55366: WordPress auto-updated plugin with auto-updates disabled
--------------------------+----------------------
 Reporter:  vtxtools      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by SergeyBiryukov):

 * component:  General => Plugins


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

From noreply at wordpress.org  Thu Mar 10 22:50:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 22:50:43 -0000
Subject: [wp-trac] [WordPress Trac] #53952: Reusable blocks - removing
 from a page treated as an edit of the re-usable block
In-Reply-To: <052.989c7dd361ad4356d4d813c7a1740e19@wordpress.org>
References: <052.989c7dd361ad4356d4d813c7a1740e19@wordpress.org>
Message-ID: <067.3688bd09b3991e725fcd0ac52e4219a6@wordpress.org>

#53952: Reusable blocks - removing from a page treated as an edit of the re-usable
block
--------------------------+------------------------------
 Reporter:  jonnie45      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:
 Severity:  critical      |  Resolution:  worksforme
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by maxparsimony):

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


Comment:

 **SOLUTION:**
 ==   I had the same problem, it drove me crazy, and I finally found the
 solution. It seems this is not really a bug, it's just a little cryptic.

 First, you have to open relevant WordPress page in 'list view' (near top
 left of screen, select the menu item that looks like a 3-line outline
 icon).

 This should open a list of page elements on left of screen.

 In the list at left of screen, find and select the row (the outline level)
 that corresponds to the ENTIRE reusable block, not the elements within it
 (it should be pretty clearly labeled).

 With that line selected at left, on your content page (at right) you
 should now see an outline box drawn around the ENTIRE reusable block. Just
 move your cursor over that outlined block (don't click anything, it's
 already highlighted). And press your 'delete' key. Also works to click
 Ctrl-C or Ctrl-X etc.

 The result is that you still have your reusable block intact, but it is no
 longer SHOWN on this individual page.

 Sorry to shill, but I invite you to check out my project to fund a crucial
 bioinformatics project with NFT 'art sale.' Really cool art and science
 coming together with two scoops of gratitude: https://cryptosteam.org/

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

From noreply at wordpress.org  Thu Mar 10 23:01:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 10 Mar 2022 23:01:53 -0000
Subject: [wp-trac] [WordPress Trac] #55343: Add Tooltip to "Remember Me"
 (WP Login Form)
In-Reply-To: <053.b5a11e22532e0c787bec386d453e28ca@wordpress.org>
References: <053.b5a11e22532e0c787bec386d453e28ca@wordpress.org>
Message-ID: <068.4a2a597e1dbe2fa23bbb57076e8157eb@wordpress.org>

#55343: Add Tooltip to "Remember Me" (WP Login Form)
------------------------------------+------------------------------
 Reporter:  generosus               |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Login and Registration  |     Version:  5.9.1
 Severity:  normal                  |  Resolution:
 Keywords:  dev-feedback            |     Focuses:
------------------------------------+------------------------------
Changes (by generosus):

 * component:  Security => Login and Registration


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

From noreply at wordpress.org  Fri Mar 11 03:30:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 03:30:38 -0000
Subject: [wp-trac] [WordPress Trac] #54984: wp_update_user doesn't work
 properly with current user instance
In-Reply-To: <051.92bddc0d644a48440a60de1fba687faf@wordpress.org>
References: <051.92bddc0d644a48440a60de1fba687faf@wordpress.org>
Message-ID: <066.1b425a4b85dd8a3303c4aac6837b86dc@wordpress.org>

#54984: wp_update_user doesn't work properly with current user instance
--------------------------+---------------------
 Reporter:  oztaser       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Users         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+---------------------

Comment (by dd32):

 > However, I am not sure this is an ideal solution as get_userdata() and
 related functions are pluggable so there is no way of knowing if the data
 returned by new WP_User( $user_id ) is what is returned by get_userdata().

 Thinking out-loud here: If we're only expecting a `WP_User` object in
 these places/globals, and since we've got a `WP_User::__set()` that takes
 care of `$user->user_pass = 12345;`, `WP_User` could create a copy of the
 user-data prior to altering fields values and a `WP_User::has_changed(
 'user_pass' )` could be used to detect if the object has changed / what
 fields have changed.

 That doesn't take care of a situation where `$user->data->user_pass` is
 changed directly though.

 So perhaps [attachment:"54984.diff"] is indeed the ideal way forward.

 > However, I am not sure this is an ideal solution as get_userdata() and
 related functions are pluggable so there is no way of knowing if the data
 returned by new WP_User( $user_id ) is what is returned by get_userdata().

 Correct me if I'm wrong, but in those cases, this could've previously been
 an issue too, right?

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

From noreply at wordpress.org  Fri Mar 11 04:16:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 04:16:48 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
Message-ID: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
--------------------------+-----------------------------
 Reporter:  talldanwp     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  REST API      |    Version:  trunk
 Severity:  normal        |   Keywords:  needs-patch
  Focuses:                |
--------------------------+-----------------------------
 The Gutenberg e2e tests seem to have caught a bug with the `media/edit`
 endpoint.

 The endpoint is now returning a `500` status for most use cases.

 Creating a ticket here as I was able to ascertain that it works on a past
 commit of `wordpress-develop`, but is broken on the latest commit, so it's
 not a Gutenberg bug.

 To reproduce:
 1. Open the browser dev tools to the network tab
 2. In the post editor, add an image block and upload an image
 3. Select ‘Crop’ from the toolbar and adjust the zoom on the image
 4. Click ‘Apply’
 5. Observe that the request to the media endpoint returns a `500` status

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

From noreply at wordpress.org  Fri Mar 11 04:17:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 04:17:46 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.d2437a980932eb4130d78bb84b784fa8@wordpress.org>

#55337: Optimize preload paths for post and site editors
--------------------------+---------------------
 Reporter:  jsnajdr       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.3
Component:  Editor        |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------
Changes (by noisysocks):

 * milestone:  Awaiting Review => 5.9.3


Comment:

 Optimistically plopping this in 5.9.3 for if it happens but 6.0 would also
 be fine.

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

From noreply at wordpress.org  Fri Mar 11 04:23:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 04:23:05 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
In-Reply-To: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
References: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
Message-ID: <068.df79d0419b4778b1d1fb8460deb4aca0@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
--------------------------+------------------------------
 Reporter:  talldanwp     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  REST API      |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------

Comment (by talldanwp):

 From what I can tell, the bug was introduced with this commit -
 https://github.com/WordPress/wordpress-
 develop/commit/7fc225aa87c80680df01a0a82e6bb94b7773a34c.

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

From noreply at wordpress.org  Fri Mar 11 04:31:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 04:31:39 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
In-Reply-To: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
References: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
Message-ID: <068.16d74c4a77cdeabad021384f773dad3f@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
--------------------------+---------------------
 Reporter:  talldanwp     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  REST API      |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+---------------------
Changes (by peterwilsoncc):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Fri Mar 11 05:02:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:02:20 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.200c9f6a4a99bd7b5254a1aa2c482c38@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
-----------------------------------------------------+---------------------
 Reporter:  kajalgohel                               |       Owner:  (none)
     Type:  enhancement                              |      Status:  new
 Priority:  normal                                   |   Milestone:  6.0
Component:  Bundled Theme                            |     Version:
 Severity:  normal                                   |  Resolution:
 Keywords:  has-screenshots has-patch needs-testing  |     Focuses:
-----------------------------------------------------+---------------------
Changes (by rehanali):

 * Attachment "#55362.2.patch" added.

 Added patch

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

From noreply at wordpress.org  Fri Mar 11 05:05:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:05:47 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.d9d8bb11302380bbfff9e474a737abaa@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------+---------------------
 Reporter:  kajalgohel               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css
-------------------------------------+---------------------
Changes (by rehanali):

 * Attachment "#55338.4.patch" added.

 Added patch

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

From noreply at wordpress.org  Fri Mar 11 05:11:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:11:38 -0000
Subject: [wp-trac] [WordPress Trac] #55257: map_deep() function
 incompatibility with incomplete objects in PHP 8.0+
In-Reply-To: <051.b532a9e5801b9736d644eef83c48757f@wordpress.org>
References: <051.b532a9e5801b9736d644eef83c48757f@wordpress.org>
Message-ID: <066.816f87dc5220a699b88fb35e9cca12c0@wordpress.org>

#55257: map_deep() function incompatibility with incomplete objects in PHP 8.0+
----------------------------+---------------------
 Reporter:  codex-m         |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Formatting      |     Version:  5.9.1
 Severity:  major           |  Resolution:
 Keywords:  has-patch php8  |     Focuses:
----------------------------+---------------------
Changes (by rehanali):

 * Attachment "#55257.patch" added.

 Added patch

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

From noreply at wordpress.org  Fri Mar 11 05:30:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:30:16 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.1880ac97a87b39c0f7c1c81e921a18c6@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  (none)
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch has-unit-   |     Focuses:  ui-copy
  tests                                          |
-------------------------------------------------+-------------------------

Comment (by mirkolofio):

 Replying to [comment:37 azouamauriac]:
 > this is still good-first-bug?

 Nice question. I have another one for @audrasjb:

 Given the huge perimeter of this change, how does a new contributor (like
 me) know when it's time to give it a boost?

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

From noreply at wordpress.org  Fri Mar 11 05:36:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:36:32 -0000
Subject: [wp-trac] [WordPress Trac] #55368: Handle ajax failure when doing
 actions on themes/plugins
Message-ID: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>

#55368: Handle ajax failure when doing actions on themes/plugins
-------------------------------------------------+-------------------------
 Reporter:  mirkolofio                           |      Owner:  (none)
     Type:  defect (bug)                         |     Status:  new
 Priority:  normal                               |  Milestone:  Awaiting
                                                 |  Review
Component:  Text Changes                         |    Version:  5.9.2
 Severity:  normal                               |   Keywords:
  Focuses:  javascript, administration, ui-copy  |
-------------------------------------------------+-------------------------
 When maintenance mode is active or the server is unresponsive for any
 reason, there are some ui issues in ajax-related messages like:

 - When trying to delete a plugin: "Deleting..." forever. No error shown.
 - When trying to enable auto-updates on a plugin: "Enabling..." forever.
 "The request could not be completed" error is shown. Same for disabling.
 - When trying to delete a theme: "Deletion failed: undefined" error shown.
 - When trying to enable a theme: "Enabling..." forever. "The request could
 not be completed." error shown. Same for disabling.

 Check the screenshots attached below.


 I tried to stay short in title description but I'm not sure it's 100%
 clear.

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

From noreply at wordpress.org  Fri Mar 11 05:37:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:37:21 -0000
Subject: [wp-trac] [WordPress Trac] #55368: Handle ajax failure when
 doing actions on themes/plugins
In-Reply-To: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
References: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
Message-ID: <069.b42e4dae4409a5a313af08e4045ae80c@wordpress.org>

#55368: Handle ajax failure when doing actions on themes/plugins
-------------------------+-------------------------------------------------
 Reporter:  mirkolofio   |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Text         |     Version:  5.9.2
  Changes                |
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  javascript, administration, ui-
                         |  copy
-------------------------+-------------------------------------------------
Changes (by mirkolofio):

 * Attachment "Screenshot 2022-03-11 at 06.02.39.png" added.

 Plugin delete failure

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

From noreply at wordpress.org  Fri Mar 11 05:37:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:37:42 -0000
Subject: [wp-trac] [WordPress Trac] #55368: Handle ajax failure when
 doing actions on themes/plugins
In-Reply-To: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
References: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
Message-ID: <069.2792391feed5b648dcc682b8bd380df6@wordpress.org>

#55368: Handle ajax failure when doing actions on themes/plugins
-------------------------+-------------------------------------------------
 Reporter:  mirkolofio   |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Text         |     Version:  5.9.2
  Changes                |
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  javascript, administration, ui-
                         |  copy
-------------------------+-------------------------------------------------
Changes (by mirkolofio):

 * Attachment "Screenshot 2022-03-11 at 06.02.02.png" added.

 Plugin enable auto-updates failure

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

From noreply at wordpress.org  Fri Mar 11 05:37:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:37:59 -0000
Subject: [wp-trac] [WordPress Trac] #55368: Handle ajax failure when
 doing actions on themes/plugins
In-Reply-To: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
References: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
Message-ID: <069.aace0a1fe7478305cb1dfe1c93704898@wordpress.org>

#55368: Handle ajax failure when doing actions on themes/plugins
-------------------------+-------------------------------------------------
 Reporter:  mirkolofio   |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Text         |     Version:  5.9.2
  Changes                |
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  javascript, administration, ui-
                         |  copy
-------------------------+-------------------------------------------------
Changes (by mirkolofio):

 * Attachment "Screenshot 2022-03-11 at 06.01.15.png" added.

 Theme delete failure

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

From noreply at wordpress.org  Fri Mar 11 05:38:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:38:18 -0000
Subject: [wp-trac] [WordPress Trac] #55368: Handle ajax failure when
 doing actions on themes/plugins
In-Reply-To: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
References: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
Message-ID: <069.23e660aa04d5da18bf316c31c709f6c0@wordpress.org>

#55368: Handle ajax failure when doing actions on themes/plugins
-------------------------+-------------------------------------------------
 Reporter:  mirkolofio   |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Text         |     Version:  5.9.2
  Changes                |
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  javascript, administration, ui-
                         |  copy
-------------------------+-------------------------------------------------
Changes (by mirkolofio):

 * Attachment "Screenshot 2022-03-11 at 06.00.57.png" added.

 Theme enable failure

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

From noreply at wordpress.org  Fri Mar 11 05:40:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:40:33 -0000
Subject: [wp-trac] [WordPress Trac] #55368: Handle ajax failure when
 doing actions on themes/plugins
In-Reply-To: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
References: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
Message-ID: <069.aee1d186f63b6999f23c28c57c03e75f@wordpress.org>

#55368: Handle ajax failure when doing actions on themes/plugins
-------------------------+-------------------------------------------------
 Reporter:  mirkolofio   |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Text         |     Version:  5.9.2
  Changes                |
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  javascript, administration, ui-
                         |  copy
-------------------------+-------------------------------------------------

Comment (by mirkolofio):

 > - When trying to delete a plugin: "Deleting..." forever. No error shown.

 There an error there: "Deletion failed: Briefly unavailable for scheduled
 maintenance. Check back in a minute."

 It's on the top of the page, I missed it.

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

From noreply at wordpress.org  Fri Mar 11 05:45:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 05:45:10 -0000
Subject: [wp-trac] [WordPress Trac] #55369: Block styles preview are
 unstyled since 5.9 if styles are in a global editor styles css
Message-ID: <051.5ede700cf0456f967f7dd00194ce2be4@wordpress.org>

#55369: Block styles preview are unstyled since 5.9 if styles are in a global
editor styles css
--------------------------+-----------------------------
 Reporter:  JohnDBB       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hello,

 Block stlyes registered with


 {{{
     wp.blocks.registerBlockStyle( 'acf/featured-news', {
         name: 'featured-news-black',
         label: 'Featured news black',
         isDefault: false,
     } );
 }}}

 Editor stylesheet enqueued with:


 {{{
 function legit_block_editor_styles() {
         wp_enqueue_style( 'legit-editor-styles', get_theme_file_uri(
 '/style-editor.css' ), false, '11.0', 'all' );
 }

 add_action( 'enqueue_block_editor_assets', 'legit_block_editor_styles' );
 }}}

 Since WordPress 5.9 the iframe that shows the block styles show them
 unstyled as doesn't include the style-editor.css

 Thank you

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

From noreply at wordpress.org  Fri Mar 11 06:29:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 06:29:26 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
Message-ID: <051.dc03991af641b6ff50232695165f265e@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
-----------------------------+-----------------------------
 Reporter:  crs1138          |      Owner:  (none)
     Type:  enhancement      |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Role/Capability  |    Version:  5.8.3
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 We have created a custom collapsible block, but the Gutenberg validation
 fails as the `aria-controls` and `aria-expanded` attributes are stripped
 from the saved content if the block is used by a user with role below
 _super administrator_.

 Could these attributes be added to the list of allowed attributes?

 Our problem is described in more detail at
 https://github.com/WordPress/gutenberg/issues/39351 at @ocean90
 recommended opening a ticket in Trac.

 Similar topic has been discussed at
 https://core.trac.wordpress.org/ticket/30421

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

From noreply at wordpress.org  Fri Mar 11 07:40:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 07:40:06 -0000
Subject: [wp-trac] [WordPress Trac] #54905: PHP notice while accessing
 Customizer
In-Reply-To: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
References: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
Message-ID: <066.7b8652d6cc3d727c72d86ca2d9a34731@wordpress.org>

#54905: PHP notice while accessing Customizer
-------------------------------------------------+-------------------------
 Reporter:  Boniu91                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info has-screenshots                   |
-------------------------------------------------+-------------------------

Comment (by azouamauriac):

 Hi there, to reproduce the issue you should follow this step:
 ''WordPress 5.9 hides the Customize menu item, if you are using a Full
 Site Editing theme, so you need to then access the /wp-admin/customize.php
 address manually to fully test this out.''
 as per this slack chat
 [https://wordpress.slack.com/archives/C02RQBWTW/p1645644792576189]

 Replying to [comment:14 rafiahmedd]:
 > @Boniu91 couldn't reproduce the same issue in my environment. Which
 version of PHP you are running?

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

From noreply at wordpress.org  Fri Mar 11 07:58:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 07:58:39 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.4ed99144b4d486dbe61661a101ae7f49@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by fs5ve):

 * Attachment "exported_data.png" added.

 Exported File

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

From noreply at wordpress.org  Fri Mar 11 07:58:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 07:58:48 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.0b16cf64f5d636454a1c58131353cf33@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by fs5ve):

 * Attachment "user_creation.png" added.


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

From noreply at wordpress.org  Fri Mar 11 07:58:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 07:58:54 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.fe516dff348fdc08fb0fb2820dc3b609@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by fs5ve):

 * Attachment "user_creation_console.png" added.


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

From noreply at wordpress.org  Fri Mar 11 07:58:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 07:58:59 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.fea907e69db8ca07c8ccf2689f221dbe@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by fs5ve):

 * Attachment "user_creation_database.png" added.


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

From noreply at wordpress.org  Fri Mar 11 07:59:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 07:59:06 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.7d5437f7862cf48ba70be6d7af098054@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by fs5ve):

 * Attachment "user_data_export_after_deletion.png" added.


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

From noreply at wordpress.org  Fri Mar 11 07:59:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 07:59:14 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.4460f2a80d077598203eb6174c71320c@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by fs5ve):

 * Attachment "user_db_still_exist.png" added.


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

From noreply at wordpress.org  Fri Mar 11 07:59:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 07:59:24 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.b7caf0b91daa1a5e9f91629b1e84e224@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by fs5ve):

 * Attachment "user_deletion_console.png" added.


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

From noreply at wordpress.org  Fri Mar 11 07:59:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 07:59:33 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.59ee26101b84e814eaa7ab4cd4e1e2d1@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by fs5ve):

 * Attachment "user_export_data.png" added.


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

From noreply at wordpress.org  Fri Mar 11 08:09:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 08:09:50 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.1ca41d9d0b74bfa9b273d4470e5cc99b@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------

Comment (by fs5ve):

 Hi @johnbillion , @swissspidy ,

 It actually doesn't depend on the installed plugin. Sorry I wrote the
 description in a way which mislead you. I have uploaded some screenshots
 showing the problem of data deletion and export. In summary the problem
 can be reproduced by following-

 1. Register a new user (say it is dummyuser). I tried with subscriber
 role, but I believe the problem is not related to the user role. While
 registering I provided first name and lastname, also email and password.
 2. Later from the tools -> export personal data, I have exported the data
 related to dummyuser.
 3. Then I make a request to delete data for this user. And in the console,
 it says "No Personal Data is found for this user".
 4. Again, I make a export request for dummyuser.
 5. It generated a export.json file which contains the same data as before
 the deletion.

 To me, it seems like the data deletion in the WordPress is not working as
 it supposed to be. May be you can try to follow the above step to re-
 create the problem. If you are not able to re-produce it let me know.

 Note that, during the whole process, I haven't installed/activated any
 other plugins/themes.


 Hi @paapst ,

 Thanks for letting us know that you were able to reproduce the problem.

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

From noreply at wordpress.org  Fri Mar 11 09:02:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 09:02:41 -0000
Subject: [wp-trac] [WordPress Trac] #55368: Handle ajax failure when
 doing actions on themes/plugins
In-Reply-To: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
References: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
Message-ID: <069.495c64ad159cc9e411517b9ccec40f0d@wordpress.org>

#55368: Handle ajax failure when doing actions on themes/plugins
-------------------------+-------------------------------------------------
 Reporter:  mirkolofio   |       Owner:  (none)
     Type:  defect       |      Status:  closed
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Text         |     Version:  5.9.2
  Changes                |
 Severity:  normal       |  Resolution:  invalid
 Keywords:               |     Focuses:  javascript, administration, ui-
                         |  copy
-------------------------+-------------------------------------------------
Changes (by azouamauriac):

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


Comment:

 Hello there, welcome to WordPress's trac! Thanks for the report, this
 seems to be an expected behavior.

 If you think I'm wrong feel free to reopen the ticket and may be explain
 more deeply what's the bug.

 Thanks.

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

From noreply at wordpress.org  Fri Mar 11 09:05:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 09:05:10 -0000
Subject: [wp-trac] [WordPress Trac] #27316: Add search for favourite
 plugins
In-Reply-To: <054.22ffcffc5fa2449f3964b1103c021677@wordpress.org>
References: <054.22ffcffc5fa2449f3964b1103c021677@wordpress.org>
Message-ID: <069.eb817cc2c0127d668ad3cacdff6f00ae@wordpress.org>

#27316: Add search for favourite plugins
-------------------------------------+-----------------------------
 Reporter:  mirkolofio               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  Plugins                  |     Version:  3.8
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  administration
-------------------------------------+-----------------------------
Changes (by azouamauriac):

 * keywords:  has-patch => has-patch needs-refresh


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

From noreply at wordpress.org  Fri Mar 11 09:28:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 09:28:47 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
In-Reply-To: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
References: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
Message-ID: <066.f9a532e154322f2c1b78a23bf5b3b6f1@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
-------------------------+------------------------------
 Reporter:  crs1138      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Formatting   |     Version:  5.8.3
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  accessibility
-------------------------+------------------------------
Changes (by sabernhardt):

 * focuses:   => accessibility
 * component:  Role/Capability => Formatting


Old description:

> We have created a custom collapsible block, but the Gutenberg validation
> fails as the `aria-controls` and `aria-expanded` attributes are stripped
> from the saved content if the block is used by a user with role below
> _super administrator_.
>
> Could these attributes be added to the list of allowed attributes?
>
> Our problem is described in more detail at
> https://github.com/WordPress/gutenberg/issues/39351 at @ocean90
> recommended opening a ticket in Trac.
>
> Similar topic has been discussed at
> https://core.trac.wordpress.org/ticket/30421

New description:

 We have created a custom collapsible block, but the Gutenberg validation
 fails as the `aria-controls` and `aria-expanded` attributes are stripped
 from the saved content if the block is used by a user with role below
 ''super administrator''.

 Could these attributes be added to the list of allowed attributes?

 Our problem is described in more detail at
 [https://github.com/WordPress/gutenberg/issues/39351 Gutenberg issue
 39351] and @ocean90 recommended opening a ticket in Trac.

 Similar topic has been discussed at Trac #30421

--

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

From noreply at wordpress.org  Fri Mar 11 09:53:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 09:53:03 -0000
Subject: [wp-trac] [WordPress Trac] #55368: Handle ajax failure when
 doing actions on themes/plugins
In-Reply-To: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
References: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
Message-ID: <069.8729dba936939baaae24205243f16548@wordpress.org>

#55368: Handle ajax failure when doing actions on themes/plugins
-------------------------+-------------------------------------------------
 Reporter:  mirkolofio   |       Owner:  (none)
     Type:  defect       |      Status:  reopened
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Text         |     Version:  5.9.2
  Changes                |
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  javascript, administration, ui-
                         |  copy
-------------------------+-------------------------------------------------
Changes (by mirkolofio):

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


Comment:

 Reopening this. It's not expected at all, let me better explain.

 Example on **Plugin enable auto-updates failure**

 Current behaviour:
 - Button switched to "Deleting..." forever
 - Error message shown: "The request could not be completed"

 Expected behavior:
 - Button switched to "Deleting..."
 - Error message should be: "The request could not be completed. Please
 retry."
 - The button should be switched back to "Delete"


 Another example on **Theme delete failure**

 Current behaviour:
 - Error message shown "Deletion failed: undefined"

 Expected behaviour:
 - At least we don't want to show "undefined" for sure.

 And so on...

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

From noreply at wordpress.org  Fri Mar 11 09:55:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 09:55:15 -0000
Subject: [wp-trac] [WordPress Trac] #55368: Handle ajax failure when
 doing actions on themes/plugins
In-Reply-To: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
References: <054.f09904b6870ad85efc4f0b5be93db193@wordpress.org>
Message-ID: <069.cdca182f0bc1c8612c4576c7c87d59dc@wordpress.org>

#55368: Handle ajax failure when doing actions on themes/plugins
-------------------------+-------------------------------------------------
 Reporter:  mirkolofio   |       Owner:  (none)
     Type:  defect       |      Status:  reopened
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Text         |     Version:  5.9.2
  Changes                |
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  javascript, administration, ui-
                         |  copy
-------------------------+-------------------------------------------------

Comment (by mirkolofio):

 Since maintenance is frequently due because of a plugin/theme/core update
 in progress and it's usually a matter of seconds, the messages should be
 clear enough to permit the user to retry just a second later.

 Please not that if you click on the "Deleting..." button once again it
 works, it's not a matter of feature though, it's just some bad/confusing
 UI/UX.

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

From noreply at wordpress.org  Fri Mar 11 10:58:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 10:58:15 -0000
Subject: [wp-trac] [WordPress Trac] #55371: HTML code in page title causes
 error in Dashboard
Message-ID: <052.c11ca67039be4565b142110a6999ad86@wordpress.org>

#55371: HTML code in page title causes error in Dashboard
-------------------------------+-----------------------------
 Reporter:  ecparkin           |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Posts, Post Types  |    Version:  5.9.2
 Severity:  normal             |   Keywords:
  Focuses:                     |
-------------------------------+-----------------------------
 Whenever I try to edit a few of my pages that have some HTML code as part
 of their title - in order to have an image/logo to appear with the title
 and change the color of one word of the title - I get the error message
 attached.

 When I remove the HTML code with a img src= from the title, the page can
 be edited as usual again.

 Any other pages where I did not place some code as part of the title work
 as expected.

 This error only started happening in the last two weeks or so, possibly
 related to the recent WordPress update?

 When I click on "Copy Error" - here is the output:

 TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not
 of type 'Node'.
     at se (https://c0.wp.com/c/5.9.1/wp-includes/js/dist/rich-
 text.min.js:2:21283)
     at ae (https://c0.wp.com/c/5.9.1/wp-includes/js/dist/rich-
 text.min.js:2:20218)
     at ge (https://c0.wp.com/c/5.9.1/wp-includes/js/dist/rich-
 text.min.js:2:21723)
     at he (https://c0.wp.com/c/5.9.1/wp-includes/js/dist/rich-
 text.min.js:2:22161)
     at x (https://c0.wp.com/c/5.9.1/wp-includes/js/dist/rich-
 text.min.js:2:33710)
     at L (https://c0.wp.com/c/5.9.1/wp-includes/js/dist/rich-
 text.min.js:2:34956)
     at https://c0.wp.com/c/5.9.1/wp-includes/js/dist/rich-
 text.min.js:2:36207
     at https://c0.wp.com/c/5.9.1/wp-includes/js/dist/compose.min.js:2:6078
     at A (https://c0.wp.com/c/5.9.1/wp-
 includes/js/dist/compose.min.js:2:9347)
     at https://c0.wp.com/c/5.9.1/wp-includes/js/dist/compose.min.js:2:9803

 Thanks.

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

From noreply at wordpress.org  Fri Mar 11 10:58:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 10:58:43 -0000
Subject: [wp-trac] [WordPress Trac] #55371: HTML code in page title
 causes error in Dashboard
In-Reply-To: <052.c11ca67039be4565b142110a6999ad86@wordpress.org>
References: <052.c11ca67039be4565b142110a6999ad86@wordpress.org>
Message-ID: <067.84b5accb5c68de088e5d355fd8f49873@wordpress.org>

#55371: HTML code in page title causes error in Dashboard
-------------------------------+------------------------------
 Reporter:  ecparkin           |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:  5.9.2
 Severity:  normal             |  Resolution:
 Keywords:                     |     Focuses:
-------------------------------+------------------------------
Changes (by ecparkin):

 * Attachment "Screenshot 2022-03-11 115709.jpg" added.

 Dashboard error when trying to edit page with HTML code in page title

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

From noreply at wordpress.org  Fri Mar 11 11:05:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 11:05:17 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.ea3eb26df25939454094dc7544d78c9d@wordpress.org>

#36949: Term exists should use get_terms internally
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  2.3
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note needs-testing commit                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

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


Comment:

 In [changeset:"52921" 52921]:
 {{{
 #!CommitTicketReference repository="" revision="52921"
 Taxonomy: Use `get_terms` instead of a database lookup in `term_exists()`.

 Replace raw SQL queries to the terms table, with a call to the `get_terms`
 function. Using `get_terms` means that `term_exists` is now cached. For
 developers using `term_exists` where cache invalidation is disabled, such
 as importing, a workaround was added to ensure that queries are uncached.

 Props Spacedmonkey, boonebgorges, flixos90, peterwilsoncc.
 Fixes #36949.
 }}}

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

From noreply at wordpress.org  Fri Mar 11 11:10:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 11:10:11 -0000
Subject: [wp-trac] [WordPress Trac] #55258: No child pages indication
 after sorting the pages in the admin page list
In-Reply-To: <055.44ad2f59a2eda190cd1ccd7f1e802803@wordpress.org>
References: <055.44ad2f59a2eda190cd1ccd7f1e802803@wordpress.org>
Message-ID: <070.071f42fa069dc68e1cd8cd2c9a22a762@wordpress.org>

#55258: No child pages indication after sorting the pages in the admin page list
-------------------------------+---------------------------------
 Reporter:  askaryabbas        |       Owner:  (none)
     Type:  enhancement        |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Posts, Post Types  |     Version:  5.9.1
 Severity:  normal             |  Resolution:  duplicate
 Keywords:  has-screenshots    |     Focuses:  ui, administration
-------------------------------+---------------------------------

Comment (by askaryabbas):

 Sure, thank you.
 Replying to [comment:1 SergeyBiryukov]:
 > Hi there, welcome back to WordPress Trac! Thanks for the ticket.
 >
 > This was previously raised in #29640, that ticket is currently closed
 but can be reopened if there is consensus on a path forward. Let's
 continue the discussion there.

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

From noreply at wordpress.org  Fri Mar 11 11:30:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 11:30:15 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
Message-ID: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
--------------------------+-----------------------------
 Reporter:  spacedmonkey  |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Menus         |    Version:  3.0
 Severity:  normal        |   Keywords:
  Focuses:  performance   |
--------------------------+-----------------------------
 Remove usage of `get_objects_in_term` and replace with a tax_query. This
 adds a level of consistency and will improve caching.

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

From noreply at wordpress.org  Fri Mar 11 11:36:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 11:36:15 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.1f63316142fd642f8d351370f5c8337d@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * keywords:   => has-patch needs-unit-tests good-first-bug


Comment:

 Created a PR [https://github.com/WordPress/wordpress-develop/pull/2399
 #2399]

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

From noreply at wordpress.org  Fri Mar 11 11:38:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 11:38:17 -0000
Subject: [wp-trac] [WordPress Trac] #55373: Attachment template: Rename from
 "Media" to "Attachment"
Message-ID: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>

#55373: Attachment template: Rename from "Media" to "Attachment"
-------------------------+-----------------------------
 Reporter:  scruffian    |      Owner:  (none)
     Type:  enhancement  |     Status:  assigned
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Editor       |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 This came up in https://github.com/WordPress/gutenberg/pull/39353.

 Theme Authors might find the name "Attachment" easier to understand
 because of how it relates to the template hierarchy.

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

From noreply at wordpress.org  Fri Mar 11 11:38:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 11:38:34 -0000
Subject: [wp-trac] [WordPress Trac] #55373: Attachment template: Rename
 from "Media" to "Attachment"
In-Reply-To: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
References: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
Message-ID: <068.e0d725d05592b29953afd0f103b2e8a5@wordpress.org>

#55373: Attachment template: Rename from "Media" to "Attachment"
-------------------------+------------------------------
 Reporter:  scruffian    |       Owner:  (none)
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------
Changes (by scruffian):

 * Attachment "patch.diff" added.

 Text change

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

From noreply at wordpress.org  Fri Mar 11 11:39:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 11:39:27 -0000
Subject: [wp-trac] [WordPress Trac] #55373: Attachment template: Rename
 from "Media" to "Attachment"
In-Reply-To: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
References: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
Message-ID: <068.c70c9c91e3d72709289d52bbd3e6641d@wordpress.org>

#55373: Attachment template: Rename from "Media" to "Attachment"
-------------------------+------------------------------
 Reporter:  scruffian    |       Owner:  (none)
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------
Changes (by scruffian):

 * Attachment "patch.2.diff" added.

 Remove unconnected changed

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

From noreply at wordpress.org  Fri Mar 11 11:41:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 11:41:11 -0000
Subject: [wp-trac] [WordPress Trac] #55374: Site Editor Templates: Fix typo
Message-ID: <053.56ba7b66ce6128aee09f00202c5e4103@wordpress.org>

#55374: Site Editor Templates: Fix typo
--------------------------+-----------------------------
 Reporter:  scruffian     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  assigned
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Editor        |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 There is a typo in the description of the tag template.

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

From noreply at wordpress.org  Fri Mar 11 11:41:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 11:41:21 -0000
Subject: [wp-trac] [WordPress Trac] #55374: Site Editor Templates: Fix
 typo
In-Reply-To: <053.56ba7b66ce6128aee09f00202c5e4103@wordpress.org>
References: <053.56ba7b66ce6128aee09f00202c5e4103@wordpress.org>
Message-ID: <068.615f56f20d13895928b730779b87ad9d@wordpress.org>

#55374: Site Editor Templates: Fix typo
--------------------------+------------------------------
 Reporter:  scruffian     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by scruffian):

 * Attachment "patch.diff" added.

 Fixes a typo

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

From noreply at wordpress.org  Fri Mar 11 13:00:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 13:00:31 -0000
Subject: [wp-trac] [WordPress Trac] #47280: SQL_CALC_FOUND_ROWS is
 deprecated as of MySQL 8.0.17
In-Reply-To: <053.464f3453501834c73527d32600b297e3@wordpress.org>
References: <053.464f3453501834c73527d32600b297e3@wordpress.org>
Message-ID: <068.4dd678af951d2c823074200af511418f@wordpress.org>

#47280: SQL_CALC_FOUND_ROWS is deprecated as of MySQL 8.0.17
--------------------------------------+-----------------------------
 Reporter:  javorszky                 |       Owner:  johnbillion
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  Future Release
Component:  Database                  |     Version:
 Severity:  major                     |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+-----------------------------

Comment (by johnbillion):

 Replying to [comment:20 xParham]:
 > Hey @johnbillion, can we also maybe add `count` as an option for the
 `fields` query parameter

 Interesting idea! I'll open a follow-up ticket for that so we keep this
 one focused.

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

From noreply at wordpress.org  Fri Mar 11 13:03:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 13:03:12 -0000
Subject: [wp-trac] [WordPress Trac] #47280: SQL_CALC_FOUND_ROWS is
 deprecated as of MySQL 8.0.17
In-Reply-To: <053.464f3453501834c73527d32600b297e3@wordpress.org>
References: <053.464f3453501834c73527d32600b297e3@wordpress.org>
Message-ID: <068.32fe70e73d0a2ad65a2b22d6b6896fa2@wordpress.org>

#47280: SQL_CALC_FOUND_ROWS is deprecated as of MySQL 8.0.17
--------------------------------------+-----------------------------
 Reporter:  javorszky                 |       Owner:  johnbillion
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  Future Release
Component:  Database                  |     Version:
 Severity:  major                     |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+-----------------------------

Comment (by johnbillion):

 Replying to [comment:21 misterwebdeveloper]:

 Thanks for the comment. I don't think any of this is relevant to this
 particular ticket, which is about implementing the MySQL change into the
 WordPress software. Cheers!

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

From noreply at wordpress.org  Fri Mar 11 13:16:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 13:16:14 -0000
Subject: [wp-trac] [WordPress Trac] #55375: Element <style> not allowed as
 child of element <body> in this context.
Message-ID: <053.47f8ac57c9c0ea768eb23a3ba1fb1e0c@wordpress.org>

#55375: Element <style> not allowed as child of element <body> in this context.
---------------------------+-----------------------------
 Reporter:  Klemart3D      |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Script Loader  |    Version:  5.9.2
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 The last WP version (v5.9.2) not passing the W3C validator, following
 error appears: "Element style not allowed as child of element body in this
 context. (Suppressing further errors from this subtree.)"

 It comes from <style> tags for `.wp-container` blocks loaded in the footer
 of the pages.

 You can see this error on front of https://wordpress.org:
 See: https://validator.w3.org/nu/?doc=https%3A%2F%2Fwordpress.org%2F

 May be related with #55148 and #53494

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

From noreply at wordpress.org  Fri Mar 11 14:20:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 14:20:31 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
In-Reply-To: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
References: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
Message-ID: <068.8ad42259ee95fd7154cf9e0133b8ba0b@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
--------------------------------------+---------------------
 Reporter:  talldanwp                 |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  REST API                  |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by spacedmonkey):

 Worked out the issue. Was getting a function does not exist message.
 Moving the function to functions.php seems to do the trick. Also makes
 sense to live there, this function is useful everywhere.

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

From noreply at wordpress.org  Fri Mar 11 14:42:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 14:42:42 -0000
Subject: [wp-trac] [WordPress Trac] #55376: Use wp_filesize in core
Message-ID: <056.56612536c597c54c37ea175736f1b4de@wordpress.org>

#55376: Use wp_filesize in core
--------------------------+----------------------------------------
 Reporter:  spacedmonkey  |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:  good-first-bug needs-patch
  Focuses:                |
--------------------------+----------------------------------------
 Introduced in [52837] as part of #49412, the `wp_filesize` function is a
 wrapper around filesize. It has some improves on this function, like
 casting to int and filters. The filesize function is call throughout core
 functions. This function may be useful in more contexts.

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

From noreply at wordpress.org  Fri Mar 11 14:42:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 14:42:52 -0000
Subject: [wp-trac] [WordPress Trac] #55376: Use wp_filesize in core
In-Reply-To: <056.56612536c597c54c37ea175736f1b4de@wordpress.org>
References: <056.56612536c597c54c37ea175736f1b4de@wordpress.org>
Message-ID: <071.a3f65b1f0a771f64b4f919ff5b7f6c6f@wordpress.org>

#55376: Use wp_filesize in core
----------------------------------------+------------------------------
 Reporter:  spacedmonkey                |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  General                     |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  good-first-bug needs-patch  |     Focuses:
----------------------------------------+------------------------------

Comment (by spacedmonkey):

 CC @flixos90

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

From noreply at wordpress.org  Fri Mar 11 14:43:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 14:43:03 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.20ad3b27ed3e23d192e7298e71d6f5a1@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------

Comment (by afercia):

 @BettyJJ thank you for testing, much appreciated.

 I was able to so some testing on macOS. Interestingly, seems to me the IME
 user interface reacts to keyboard events differently depending on the
 language. See the animated GIF attached below.

 Please consider I have no idea what I'm actually typing while using the
 IME :) I'm just trying to use it for testing purposes.

 Japanese:
 - The first Escape key does NOT close the comment textarea.
 - At that point, `isComposing` is still true.

 Chinese:
 - The first Escape key DOES close the comment textarea.
 - At that point, `isComposing` is false.

 More inconsistencies may occur across browsers and operating systems.
 Basically, detecting the start of a composition seems reliable. Instead,
 determining whether a `keyup` event on the Escape key happens before or
 after the composition end appears to be highly unreliable.

 Given the above, I'd tend to think the most sensible thing to do is to
 disable the 'Close on Escape' behavior when an IME is in use. Will upload
 a patch shortly. Any feedback and thoughts are very welcome.

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

From noreply at wordpress.org  Fri Mar 11 14:43:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 14:43:34 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.0e02d796c20565bf9e284c57c3b8177b@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------
Changes (by afercia):

 * Attachment "japanese.gif" added.

 Japanese – Kana

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

From noreply at wordpress.org  Fri Mar 11 14:43:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 14:43:52 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.d3119ce4825da424a6176d129b71fc6d@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------
Changes (by afercia):

 * Attachment "chinese.gif" added.

 Chinese – Cangjie

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

From noreply at wordpress.org  Fri Mar 11 14:46:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 14:46:29 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.dfcc116bd3e4b6a4d74c8960966f83f1@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------
Changes (by afercia):

 * Attachment "54548.3.diff" added.


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

From noreply at wordpress.org  Fri Mar 11 14:49:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 14:49:08 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.7f04c8a92e5446ac09a5d2aec6009bce@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------

Comment (by afercia):

 [attachment:"54548.3.diff"] disables the 'Close on Escape' behavior when
 an IME composition has started. Some testing would be appreciated.

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

From noreply at wordpress.org  Fri Mar 11 15:03:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 15:03:19 -0000
Subject: [wp-trac] [WordPress Trac] #55373: Attachment template: Rename
 from "Media" to "Attachment"
In-Reply-To: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
References: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
Message-ID: <068.039850b50349baf038131335aeb11eb8@wordpress.org>

#55373: Attachment template: Rename from "Media" to "Attachment"
-------------------------+-----------------------
 Reporter:  scruffian    |       Owner:  (none)
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  6.0
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+-----------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Fri Mar 11 15:05:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 15:05:55 -0000
Subject: [wp-trac] [WordPress Trac] #55374: Site Editor Templates: Fix
 typo
In-Reply-To: <053.56ba7b66ce6128aee09f00202c5e4103@wordpress.org>
References: <053.56ba7b66ce6128aee09f00202c5e4103@wordpress.org>
Message-ID: <068.db6decfddafa648e3d9f4d170bee4fd9@wordpress.org>

#55374: Site Editor Templates: Fix typo
--------------------------+-----------------------
 Reporter:  scruffian     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  6.0
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


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

From noreply at wordpress.org  Fri Mar 11 15:22:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 15:22:43 -0000
Subject: [wp-trac] [WordPress Trac] #55374: Site Editor Templates: Fix
 typo
In-Reply-To: <053.56ba7b66ce6128aee09f00202c5e4103@wordpress.org>
References: <053.56ba7b66ce6128aee09f00202c5e4103@wordpress.org>
Message-ID: <068.f4904b26c423f323996f9adaf4d9fc2e@wordpress.org>

#55374: Site Editor Templates: Fix typo
--------------------------+-----------------------------
 Reporter:  scruffian     |       Owner:  SergeyBiryukov
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  6.0
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:  fixed
 Keywords:                |     Focuses:
--------------------------+-----------------------------
Changes (by SergeyBiryukov):

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


Comment:

 In [changeset:"52922" 52922]:
 {{{
 #!CommitTicketReference repository="" revision="52922"
 Site Editor: Fix typo in the description of the tag template.

 Follow-up to [52331].

 Props scruffian.
 Fixes #55374.
 }}}

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

From noreply at wordpress.org  Fri Mar 11 15:30:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 15:30:47 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.98a6e44a0877af52c14d52bd2c62bb53@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------

Comment (by afercia):

 Note: [attachment:"55364.diff"] needs to be updated to take into account
 also the Quick Edit form in `edit-tags.php`.

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

From noreply at wordpress.org  Fri Mar 11 15:41:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 15:41:38 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.9a0f89f361725cd530efd9540234d3ea@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------
Changes (by afercia):

 * Attachment "55364.2.diff" added.


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

From noreply at wordpress.org  Fri Mar 11 15:42:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 15:42:58 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.0c7b2797eba17ce2ada1fa27e66b5d17@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------

Comment (by afercia):

 [attachment:"55364.2.diff"] adjusts position and order of the buttons also
 for the 'edit tags' Quick Edit form. See attached screenshot.

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

From noreply at wordpress.org  Fri Mar 11 15:43:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 15:43:32 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.86de016f6f2249f85c4eadfbdf2c7813@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------
Changes (by afercia):

 * Attachment "edit tags quick edit.png" added.

 Edit tags Quick Edit form

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

From noreply at wordpress.org  Fri Mar 11 15:49:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 15:49:23 -0000
Subject: [wp-trac] [WordPress Trac] #55377: Crop area does not appear in
 Customizer while cropping the Site Logo, if the Site Logo is larger in size
Message-ID: <052.d93a6028a6dbfee43c296699d47c526e@wordpress.org>

#55377: Crop area does not appear in Customizer while cropping the Site Logo, if
the Site Logo is larger in size
----------------------------+-----------------------------
 Reporter:  ajmaurya        |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Customize       |    Version:
 Severity:  normal          |   Keywords:  needs-patch
  Focuses:  administration  |
----------------------------+-----------------------------
 The crop area does not appear sometimes while cropping the site icon in
 the Admin Customizer screen. Also noticed the behavior - when changing a
 window size slightly, the crop area appears!

 **Steps to Reproduce**

 - Upload a wide image and keep the window size narrow or vice versa.
 - Try to select and crop the image.
 - The crop area does not appear.
 - Slightly change the window size.
 - Crop are appears.

 Check the below video and gif.
 https://share.getcloudapp.com/8LuD4LWm
  ![Missing Crop Screen](https://user-
 images.githubusercontent.com/25176325/157882498-264ec5c9-20bf-
 46f8-be44-5ee334bbb470.gif)

 **Dimensions I faced an issue with.**

 - Image size - 2560 by 1707 pixels
 - Screen Size - 780 by 550 pixels

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

From noreply at wordpress.org  Fri Mar 11 15:50:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 15:50:35 -0000
Subject: [wp-trac] [WordPress Trac] #55377: Crop area does not appear in
 Customizer while cropping the Site Logo, if the Site Logo is larger in size
In-Reply-To: <052.d93a6028a6dbfee43c296699d47c526e@wordpress.org>
References: <052.d93a6028a6dbfee43c296699d47c526e@wordpress.org>
Message-ID: <067.f40980c797f2333dcb72aa0cd64dbb0d@wordpress.org>

#55377: Crop area does not appear in Customizer while cropping the Site Logo, if
the Site Logo is larger in size
--------------------------+------------------------------
 Reporter:  ajmaurya      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Customize     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  administration
--------------------------+------------------------------
Changes (by ajmaurya):

 * Attachment "crop-issue.gif" added.

 Crop Screen not appearing.

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

From noreply at wordpress.org  Fri Mar 11 16:01:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 16:01:45 -0000
Subject: [wp-trac] [WordPress Trac] #32747: WP Admin Menus/SubMenus
 Overlap in small screen
In-Reply-To: <053.19f81590b59ff77c2a9b31983b4caf91@wordpress.org>
References: <053.19f81590b59ff77c2a9b31983b4caf91@wordpress.org>
Message-ID: <068.6d3f29101e12e1180f56d539b1c5fd7e@wordpress.org>

#32747: WP Admin Menus/SubMenus Overlap in small screen
----------------------------+-------------------------------------
 Reporter:  turtlepod       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Administration  |     Version:  4.2.2
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  ui, accessibility, css
----------------------------+-------------------------------------

Comment (by collieit):

 I digt a bit in the issue.
 I found out that

 {{{
 <ul class="wp-submenu wp-submenu-wrap" style=""></ul>
 }}}

 can get a melformed css. Looking like (-113px is an exemple)

 {{{
 Element {
     margin-top: -113px;
 }
 }}}

 The margin-top is calculate. If you go deeper in the menu list the problem
 get worse.

 I think this will be done via the js submenu close and open method. The
 calculation missmatched the realty exspecialy in cases with long submenues
 that hits the page end.

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

From noreply at wordpress.org  Fri Mar 11 16:13:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 16:13:22 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.649d34051a2bee32cdbe104ed9c6626b@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots needs-testing                      |  accessibility
-------------------------------------------------+-------------------------
Changes (by ryokuhi):

 * keywords:  a11y-proximity has-patch has-screenshots => a11y-proximity
     has-patch has-screenshots needs-testing
 * milestone:  Awaiting Review => 6.0


Comment:

 Hello @afercia,
 happy to have you back onboard!
 We reviewed this ticket today during the accessibility team's weekly bug-
 scrub.
 As this ticket already has a patch, I'm moving it to the 6.0 milestone and
 adding the `needs-testing` label.

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

From noreply at wordpress.org  Fri Mar 11 16:20:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 16:20:50 -0000
Subject: [wp-trac] [WordPress Trac] #38741: Introduce the concept of a
 large site in order to speed up the Users screen when there are many users
In-Reply-To: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
References: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
Message-ID: <070.17b901cb5d670b193a19e3e75f7d2ec6@wordpress.org>

#38741: Introduce the concept of a large site in order to speed up the Users screen
when there are many users
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  (none)
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  early has-patch dev-     |     Focuses:  administration,
  feedback needs-testing 2nd-        |  multisite, performance
  opinion needs-refresh              |
-------------------------------------+-------------------------------------
Changes (by costdev):

 * keywords:  early has-patch dev-feedback needs-testing 2nd-opinion =>
     early has-patch dev-feedback needs-testing 2nd-opinion needs-refresh


Comment:

 Patch
 [https://core.trac.wordpress.org/attachment/ticket/38741/38741.11.diff
 38741.11.diff] no longer applies cleanly against trunk. Needs a considered
 refresh.

 @johnbillion Once the patch is refreshed, what do you think are the next
 steps for this ticket? Does it just need testing, or do the meta tickets
 in @SergeyBiryukov's comment above have an impact on the path forward?

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

From noreply at wordpress.org  Fri Mar 11 16:21:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 16:21:10 -0000
Subject: [wp-trac] [WordPress Trac] #54028: Fix improper use of the
 hooks API
In-Reply-To: <050.a5b774ca0bae1254e082498489808619@wordpress.org>
References: <050.a5b774ca0bae1254e082498489808619@wordpress.org>
Message-ID: <065.146dd9c1c1e4f056d2620ec9ec7474b5@wordpress.org>

#54028: Fix improper use of the hooks API
--------------------------+---------------------
 Reporter:  azaozz        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  General       |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  docs
--------------------------+---------------------

Comment (by johnregan3):

 PR issued for discussion. @azaozz @donmhico

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

From noreply at wordpress.org  Fri Mar 11 16:31:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 16:31:04 -0000
Subject: [wp-trac] [WordPress Trac] #55378: WordPress Embed Doesn't Work on
 Mobile
Message-ID: <056.3b26a4dd9ecb978a87c1c4512baa0f1d@wordpress.org>

#55378: WordPress Embed Doesn't Work on Mobile
--------------------------+-----------------------------
 Reporter:  upintheskynl  |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Embeds        |    Version:  5.9.2
 Severity:  major         |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hi,

 For our news website (https://www.upinthesky.nl), we often link to an
 older article using the WordPress Embed block. For an example, please
 view: https://www.upinthesky.nl/2022/03/08/kaag-klm-gaat-zelf-over-
 bedrijfsmodel/.

 The embed is a great way to feature another article, however there is
 currently a problem with the block. On desktop/laptop it works fine.
 However, on mobile devices, it is not possible to click on it (the link
 within the header doesn't work) and thus there's no way to actually go to
 the article. Could this please be fixed asap, as it currently affects all
 of our news articles that have such an embed in it?

 Thank you very much in advance!

 Kind regards,
 Sytse Sijbesma

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

From noreply at wordpress.org  Fri Mar 11 16:40:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 16:40:33 -0000
Subject: [wp-trac] [WordPress Trac] #55379: Issue with images since 5.9.1 -
 persists in 5.9.2. Please remove this css code as described here on the
 next wordpress version. Thanks
Message-ID: <059.b7c53bfb43abd5383f4145f1fb4f6fda@wordpress.org>

#55379: Issue with images since 5.9.1 - persists in 5.9.2. Please remove this css
code as described here on the next wordpress version. Thanks
-----------------------------+-----------------------------------------
 Reporter:  seamlessdigital  |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Media            |    Version:  5.9.2
 Severity:  critical         |   Keywords:  needs-patch has-copy-review
  Focuses:                   |
-----------------------------+-----------------------------------------
 Since the update lots of site broke due to this change from core wordpress
 code:

 {{{
 html :where(img){ height: auto; max-width: 100% }
 }}}
  that was added to
 {{{
 wp-includes/css/dist/block-library/style.min.css
 }}}
 .
 Since then lots of site broke with images looking extremely large. I've
 already reported this here: https://wordpress.org/support/topic/wordpress-
 image-issue-on-v5-9-1/#post-15415040 but this has been frustrating.

 Lots of sites especially legacy sites were broken due to this addition and
 we had to fix them twice, we've added them also a patch but that's not a
 good solution. Can you please remove this piece of css code on your next
 wordpress version release? Thanks.

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

From noreply at wordpress.org  Fri Mar 11 16:44:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 16:44:16 -0000
Subject: [wp-trac] [WordPress Trac] #55379: Issue with images since
 5.9.1 - persists in 5.9.2. Please remove this css code as described here on
 the next wordpress version. Thanks
In-Reply-To: <059.b7c53bfb43abd5383f4145f1fb4f6fda@wordpress.org>
References: <059.b7c53bfb43abd5383f4145f1fb4f6fda@wordpress.org>
Message-ID: <074.f32f59475423bef1d99b08baa35fbd63@wordpress.org>

#55379: Issue with images since 5.9.1 - persists in 5.9.2. Please remove this css
code as described here on the next wordpress version. Thanks
-----------------------------+------------------------
 Reporter:  seamlessdigital  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Media            |     Version:  5.9.1
 Severity:  normal           |  Resolution:  duplicate
 Keywords:                   |     Focuses:  css
-----------------------------+------------------------
Changes (by davidbaumwald):

 * status:  new => closed
 * focuses:   => css
 * severity:  critical => normal
 * version:  5.9.2 => 5.9.1
 * milestone:  Awaiting Review =>
 * keywords:  needs-patch has-copy-review =>
 * resolution:   => duplicate


Comment:

 @seamlessdigital Welcome to WordPress Core Trac, and thanks for the
 ticket!  This is already being tracked in #55229.  Closing this ticket in
 favor of the work already in progress there.

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

From noreply at wordpress.org  Fri Mar 11 17:03:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 17:03:18 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.e0260b6ec689ea4d453394dbcece8006@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots needs-testing                      |  accessibility
-------------------------------------------------+-------------------------
Changes (by joedolson):

 * owner:  (none) => joedolson
 * status:  new => accepted


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

From noreply at wordpress.org  Fri Mar 11 17:07:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 17:07:05 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.76ad87e60a86dc48be4f45609be0491d@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------------+----------------------------------------
 Reporter:  SergeyBiryukov        |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:  6.0
Component:  Administration        |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  has-patch needs-      |     Focuses:  accessibility, javascript
  testing                         |
----------------------------------+----------------------------------------
Changes (by sabernhardt):

 * keywords:   => has-patch needs-testing


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

From noreply at wordpress.org  Fri Mar 11 17:07:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 17:07:30 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
In-Reply-To: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
References: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
Message-ID: <066.9a3b47dffa0c7582df4fb5bc85b39018@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
----------------------------------------+----------------------------
 Reporter:  crs1138                     |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:  5.8.3
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:  accessibility
----------------------------------------+----------------------------
Changes (by ryokuhi):

 * keywords:   => needs-patch good-first-bug
 * milestone:  Awaiting Review => 6.0


Comment:

 Hello @crs1138, and thanks for opening this ticket after bringing up
 discussion in the Gutenberg repository.
 We reviewed this ticket today during the accessibility team's weekly bug-
 scrub.
 We agreed that both `aria-expanded` and `aria-controls`, but also `aria-
 current`, should be added to the list of allowed attributes.
 As the related patch seems to be very easy to create and test, we're
 milestoning this ticket for 6.0 and adding the `good-first-bug` label.

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

From noreply at wordpress.org  Fri Mar 11 17:28:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 17:28:11 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.86dd931c46e8ee37941c048158a96cbe@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------------+----------------------------------------
 Reporter:  SergeyBiryukov        |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:  6.0
Component:  Administration        |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  has-patch needs-      |     Focuses:  accessibility, javascript
  testing                         |
----------------------------------+----------------------------------------

Comment (by SergeyBiryukov):

 Thanks for the patch! This looks like a good start to me, but I think it
 would be a bit cleaner if the `message` parameter of `supplemental`
 contained the message itself, instead of it being passed in the `data`
 parameter.

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

From noreply at wordpress.org  Fri Mar 11 17:29:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 17:29:13 -0000
Subject: [wp-trac] [WordPress Trac] #55375: Element <style> not allowed
 as child of element <body> in this context.
In-Reply-To: <053.47f8ac57c9c0ea768eb23a3ba1fb1e0c@wordpress.org>
References: <053.47f8ac57c9c0ea768eb23a3ba1fb1e0c@wordpress.org>
Message-ID: <068.249fbd7f37d3f5899e548bff12bf8e01@wordpress.org>

#55375: Element <style> not allowed as child of element <body> in this context.
---------------------------+--------------------------------
 Reporter:  Klemart3D      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  Script Loader  |     Version:  5.9
 Severity:  normal         |  Resolution:  reported-upstream
 Keywords:                 |     Focuses:
---------------------------+--------------------------------
Changes (by costdev):

 * status:  new => closed
 * version:  5.9.2 => 5.9
 * resolution:   => reported-upstream
 * milestone:  Awaiting Review =>


Comment:

 Hi @Klemart3D, welcome to Trac!

 This has been reported upstream in
 [https://github.com/WordPress/gutenberg/issues/38917 GB 38917]. Let's
 continue the discussion there.

 I'll close this ticket so that discussion is focused over on
 [https://github.com/WordPress/gutenberg/issues/38917 GB 38917].

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

From noreply at wordpress.org  Fri Mar 11 17:29:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 17:29:18 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.2626d11463f7b15256249ea29750f5f3@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------------+----------------------------------------
 Reporter:  SergeyBiryukov        |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:  6.0
Component:  Administration        |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  has-patch needs-      |     Focuses:  accessibility, javascript
  testing                         |
----------------------------------+----------------------------------------

Comment (by johnregan3):

 @SergeyBiryukov Gladly. I went that route bc that's how the JS was written
 originally. I'll issue a patch within the next business day or two.

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

From noreply at wordpress.org  Fri Mar 11 17:43:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 17:43:29 -0000
Subject: [wp-trac] [WordPress Trac] #50163: Perform a canonical redirect
 when paginated states of the front page are not found
In-Reply-To: <048.165d8bffb8836886d21b5da24cca372d@wordpress.org>
References: <048.165d8bffb8836886d21b5da24cca372d@wordpress.org>
Message-ID: <063.39f224e52a3e31ab58ec05e8a5fe8d19@wordpress.org>

#50163: Perform a canonical redirect when paginated states of the front page are
not found
-------------------------------------------------+-------------------------
 Reporter:  dd32                                 |       Owner:
                                                 |  hellofromTonya
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Canonical                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-screenshots needs-     |     Focuses:
  unit-tests early                               |
-------------------------------------------------+-------------------------

Comment (by Mte90):

 Any updates for this? maybe for 6.0?

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

From noreply at wordpress.org  Fri Mar 11 18:07:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 18:07:54 -0000
Subject: [wp-trac] [WordPress Trac] #55371: HTML code in page title
 causes error in Dashboard
In-Reply-To: <052.c11ca67039be4565b142110a6999ad86@wordpress.org>
References: <052.c11ca67039be4565b142110a6999ad86@wordpress.org>
Message-ID: <067.926d264d2bd5279cd2f634abd91296b3@wordpress.org>

#55371: HTML code in page title causes error in Dashboard
--------------------------+--------------------------------
 Reporter:  ecparkin      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:  5.9.2
 Severity:  normal        |  Resolution:  reported-upstream
 Keywords:                |     Focuses:
--------------------------+--------------------------------
Changes (by costdev):

 * status:  new => closed
 * resolution:   => reported-upstream
 * component:  Posts, Post Types => Editor
 * milestone:  Awaiting Review =>


Comment:

 Hi @ecparkin, welcome to Trac!

 This appears to have been introduced in WordPress 5.9 when changes
 included in Gutenberg 11.4.0 were added to WordPress.

 On WordPress 5.9, the error is shown.
 On WordPress 5.8, the error is not shown.
 On WordPress 5.8 with Gutenberg 11.3.0, the error is not shown.
 On WordPress 5.8 with Gutenberg 11.4.0, the error is shown.

 I have opened [https://github.com/WordPress/gutenberg/issues/39395 an
 issue on the Gutenberg repository] so that the folks over there can
 investigate this further.

 I'll close this ticket so that discussion can be focused over there.

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

From noreply at wordpress.org  Fri Mar 11 18:21:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 18:21:27 -0000
Subject: [wp-trac] [WordPress Trac] #55369: Block styles preview are
 unstyled since 5.9 if styles are in a global editor styles css
In-Reply-To: <051.5ede700cf0456f967f7dd00194ce2be4@wordpress.org>
References: <051.5ede700cf0456f967f7dd00194ce2be4@wordpress.org>
Message-ID: <066.0b37edc476e3bdb9379b8b51f8aa1fec@wordpress.org>

#55369: Block styles preview are unstyled since 5.9 if styles are in a global
editor styles css
-------------------------------+------------------------------
 Reporter:  JohnDBB            |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Editor             |     Version:  5.9.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by costdev):

 * keywords:   => reporter-feedback
 * component:  General => Editor


Comment:

 Hi @JohnDBB, welcome to Trac!

 Can you please install the latest version of the Gutenberg plugin and if
 the issue still occurs, please open an issue on the
 [https://github.com/WordPress/gutenberg/issues/new?assignees=&labels=&template=Bug_report.yml
 Gutenberg repository] to allow the team to investigate this further.

 If you do create an issue on the Gutenberg repository, please paste the
 link into a new comment on this ticket. If you don't plan to create an
 issue, please let us know. I'll leave this ticket open until then.

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

From noreply at wordpress.org  Fri Mar 11 18:49:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 18:49:16 -0000
Subject: [wp-trac] [WordPress Trac] #55369: Block styles preview are
 unstyled since 5.9 if styles are in a global editor styles css
In-Reply-To: <051.5ede700cf0456f967f7dd00194ce2be4@wordpress.org>
References: <051.5ede700cf0456f967f7dd00194ce2be4@wordpress.org>
Message-ID: <066.052e48d49fb8e264ccffa56b9ada2b5e@wordpress.org>

#55369: Block styles preview are unstyled since 5.9 if styles are in a global
editor styles css
-------------------------------+------------------------------
 Reporter:  JohnDBB            |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Editor             |     Version:  5.9.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by JohnDBB):

 Thank you @costdev I have installed the latest version of the Gutenberg
 plugin and it seems that they have completely removed the styles preview!
 Now there are just buttons with the name of the style on them.

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

From noreply at wordpress.org  Fri Mar 11 19:02:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 19:02:28 -0000
Subject: [wp-trac] [WordPress Trac] #55380:
 https://profiles.wordpress.org/mcmm2022
Message-ID: <052.008321dd035621b5e91bd40fac02d1de@wordpress.org>

#55380: https://profiles.wordpress.org/mcmm2022
--------------------------+-----------------------------
 Reporter:  mcmm2022      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 [https://profiles.wordpress.org/mcmm2022]

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

From noreply at wordpress.org  Fri Mar 11 19:56:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 19:56:19 -0000
Subject: [wp-trac] [WordPress Trac] #46057: Remove self-references
 ("we") in text in core
In-Reply-To: <055.675410e1a7b30657f2327896dc28409d@wordpress.org>
References: <055.675410e1a7b30657f2327896dc28409d@wordpress.org>
Message-ID: <070.35387d4e6c093285d1759e05fdd56268@wordpress.org>

#46057: Remove self-references ("we") in text in core
-----------------------------------------+------------------------------
 Reporter:  johnbillion                  |       Owner:  johnjamesjacoby
     Type:  enhancement                  |      Status:  reopened
 Priority:  normal                       |   Milestone:  6.0
Component:  Administration               |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+------------------------------

Comment (by costdev):

 It looks like the strings mentioned in
 [https://core.trac.wordpress.org/ticket/46057#comment:17 comment 17] need
 review to see if they should be changed.

 I'm not sure if any of them ''should'' change, but here's how they could:

 {{{
 Don&#8217;t you wish all software came with these freedoms? So do we! For
 more information, check out the <a href="https://www.fsf.org/">Free
 Software Foundation</a>.

 // Remove "So do we!"

 Don&#8217;t you wish all software came with these freedoms? For more
 information, check out the <a href="https://www.fsf.org/">Free Software
 Foundation</a>.
 }}}

 {{{
 It seems we can&rsquo;t find what you&rsquo;re looking for. Perhaps
 searching can help.

 // Replace "It seems we can&rsquo;t find what you&rsquo;re looking for."
 with:

 404.php
 This page could not be found. Perhaps searching can help.

 content-none.php
 No posts were found. Perhaps searching can help.
 }}}

 {{{
 WordPress grows when people like you tell their friends about it, and the
 thousands of businesses and services that are built on and around
 WordPress share that fact with their users. We&#8217;re flattered every
 time someone spreads the good word, just make sure to <a href="%s">check
 out our trademark guidelines</a> first.

 // Replace "We&#8217;re flattered" with "It&#8217;s flattering" and "our
 trademark guidelines" with "the trademark guidelines.

 WordPress grows when people like you tell their friends about it, and the
 thousands of businesses and services that are built on and around
 WordPress share that fact with their users. It&#8217;s flattering every
 time someone spreads the good word, just make sure to <a href="%s">check
 out the trademark guidelines</a> first.
 }}}

 What are your thoughts @johnjamesjacoby?

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

From noreply at wordpress.org  Fri Mar 11 21:14:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 21:14:36 -0000
Subject: [wp-trac] [WordPress Trac] #55380: Updating from 5.8.2 to 5.9.2
 breaks default website (no additional plugins)
Message-ID: <052.c6a71f0ac7f5f88861caa6135aa449fa@wordpress.org>

#55380: Updating from 5.8.2 to 5.9.2 breaks default website (no additional plugins)
-----------------------------+-----------------------------
 Reporter:  rinart73         |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:  5.9.2
 Severity:  major            |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 I wanted to test some plugins on my local server. I had old WordPress
 5.8.2 archive. I installed it and then it automatically updated.
 Immediatelly after that my website broke. I didn't install any additional
 plugins.

 Server: Apache 2.4
 PHP: 7.4
 MySQL: 8.0

 {{{
 Fatal error: Uncaught Error: Call to a member function switch_to_blog() on
 null in C:\OpenServer\domains\visualelementor.nodomain.me\wp-
 includes\cache.php:239 Stack trace: #0
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-
 includes\load.php(727): wp_cache_switch_to_blog() #1
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-settings.php(131):
 wp_start_object_cache() #2
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-config.php(95):
 require_once('C:\\OpenServer\\d...') #3
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-load.php(50):
 require_once('C:\\OpenServer\\d...') #4
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-admin\admin.php(34):
 require_once('C:\\OpenServer\\d...') #5
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-admin\index.php(10):
 require_once('C:\\OpenServer\\d...') #6 {main} thrown in
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-includes\cache.php on
 line 239

 Fatal error: Uncaught Error: Call to undefined function __() in
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-includes\class-wp-
 fatal-error-handler.php:188 Stack trace: #0
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-includes\class-wp-
 fatal-error-handler.php(152):
 WP_Fatal_Error_Handler->display_default_error_template() #1
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-includes\class-wp-
 fatal-error-handler.php(57):
 WP_Fatal_Error_Handler->display_error_template() #2 [internal function]:
 WP_Fatal_Error_Handler->handle() #3 {main} thrown in
 C:\OpenServer\domains\visualelementor.nodomain.me\wp-includes\class-wp-
 fatal-error-handler.php on line 188
 }}}

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

From noreply at wordpress.org  Fri Mar 11 21:25:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 21:25:08 -0000
Subject: [wp-trac] [WordPress Trac] #55380: Updating from 5.8.2 to 5.9.2
 breaks default website (no additional plugins)
In-Reply-To: <052.c6a71f0ac7f5f88861caa6135aa449fa@wordpress.org>
References: <052.c6a71f0ac7f5f88861caa6135aa449fa@wordpress.org>
Message-ID: <067.83453a6ebc1486bb977fa6cc31b9e728@wordpress.org>

#55380: Updating from 5.8.2 to 5.9.2 breaks default website (no additional plugins)
-----------------------------+------------------------------
 Reporter:  rinart73         |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9.2
 Severity:  major            |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by costdev):

 Hi @rinart73, welcome to Trac!

 Sorry to hear you had trouble upgrading to WordPress 5.9.

 The `switch_to_blog()` fatal error was reported in ticket #54969 and may
 have been caused by a failed installation.

 If possible, please try the installation again and let us know whether it
 was successful.

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

From noreply at wordpress.org  Fri Mar 11 21:50:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 21:50:02 -0000
Subject: [wp-trac] [WordPress Trac] #55378: WordPress Embed Doesn't Work
 on Mobile
In-Reply-To: <056.3b26a4dd9ecb978a87c1c4512baa0f1d@wordpress.org>
References: <056.3b26a4dd9ecb978a87c1c4512baa0f1d@wordpress.org>
Message-ID: <071.317decec77067f9574998c9804a5341d@wordpress.org>

#55378: WordPress Embed Doesn't Work on Mobile
--------------------------+----------------------
 Reporter:  upintheskynl  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Embeds        |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by costdev):

 * status:  new => closed
 * version:  5.9.2 =>
 * resolution:   => invalid
 * severity:  major => normal
 * milestone:  Awaiting Review =>


Comment:

 Hi @upintheskynl, welcome to Trac!

 I saw the issue on your website using Chrome on Android, but I was unable
 to reproduce this issue on a new installation of WordPress 5.9.2.

 This may be due to a plugin or theme conflict. You can get some help with
 this issue from the folks over on [https://wordpress.org/support/forums/
 the support forums].

 If, after speaking to the folks on the support forums, it's determined to
 be a bug in WordPress, this should be reported on
 [https://github.com/wordpress/gutenberg/issues the Gutenberg repository],
 which handles block-related issues.


 I'll close ticket as this may be due to a plugin or theme conflict. This
 is therefore likely a support issue, whereas Trac is for the development
 of WordPress Core.

 Best of luck!

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

From noreply at wordpress.org  Fri Mar 11 22:32:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 22:32:30 -0000
Subject: [wp-trac] [WordPress Trac] #55373: Attachment template: Rename
 from "Media" to "Attachment"
In-Reply-To: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
References: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
Message-ID: <068.1e1d9f48def604295d43ea88eb26a3f6@wordpress.org>

#55373: Attachment template: Rename from "Media" to "Attachment"
-------------------------+-----------------------
 Reporter:  scruffian    |       Owner:  (none)
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  6.0
Component:  Editor       |     Version:  5.9
 Severity:  normal       |  Resolution:
 Keywords:  commit       |     Focuses:
-------------------------+-----------------------
Changes (by costdev):

 * keywords:   => commit
 * version:   => 5.9


Comment:

 This makes sense to me.

 This was the only key in the array whose value differed, and this also
 fits with the established "Attachment" page terminology (`attachment.php`,
 "View attachment page",  linking to "Attachment Page", etc).

 The description states "media items or attachments", so this doesn't
 deviate from the description and, in fact, simply chooses the descriptor
 that is more commonly used in the context of templates.

 Tested the patch and it works as expected.

 Unless there are objections / additional strings to update, this is a
 reasonable and straightforward change. Marking for `commit` consideration.

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

From noreply at wordpress.org  Fri Mar 11 22:33:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 22:33:26 -0000
Subject: [wp-trac] [WordPress Trac] #55373: Attachment template: Rename
 from "Media" to "Attachment"
In-Reply-To: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
References: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
Message-ID: <068.0c1f46250350fa2986fb7595770b4692@wordpress.org>

#55373: Attachment template: Rename from "Media" to "Attachment"
-------------------------+-----------------------
 Reporter:  scruffian    |       Owner:  (none)
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  6.0
Component:  Editor       |     Version:  5.9
 Severity:  normal       |  Resolution:
 Keywords:  commit       |     Focuses:
-------------------------+-----------------------
Changes (by costdev):

 * Attachment "55373-before-after.jpg" added.

 Before and after patch.2.diff

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

From noreply at wordpress.org  Fri Mar 11 22:40:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 22:40:37 -0000
Subject: [wp-trac] [WordPress Trac] #55373: Attachment template: Rename
 from "Media" to "Attachment"
In-Reply-To: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
References: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
Message-ID: <068.52becbe95fcd092f2e2785e0d10c3762@wordpress.org>

#55373: Attachment template: Rename from "Media" to "Attachment"
-------------------------+----------------------------
 Reporter:  scruffian    |       Owner:  davidbaumwald
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  6.0
Component:  Editor       |     Version:  5.9
 Severity:  normal       |  Resolution:
 Keywords:  commit       |     Focuses:
-------------------------+----------------------------
Changes (by davidbaumwald):

 * owner:  (none) => davidbaumwald
 * status:  assigned => accepted


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

From noreply at wordpress.org  Fri Mar 11 22:54:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 22:54:14 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
In-Reply-To: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
References: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
Message-ID: <068.8019874bf9b5e30f49169c1aef1c315a@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
--------------------------------------+---------------------
 Reporter:  talldanwp                 |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  REST API                  |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by costdev):

 == Test Report

 === Env
 * Web Server: Apache (Linux)
 * WordPress: 6.0-alpha-52448-src
 * Browser: Chrome
 * OS: Windows 10
 * Theme: Twenty Twenty-Two
 * Plugins: None activated.

 === Steps to test
 1. Open the browser dev tools to the `Network` tab.
 2. In the post editor, add an image block and upload an image.
 3. Select `Crop` from the toolbar and adjust the zoom on the image.
 4. Click `Apply`.
 5. Observe that the request to the media endpoint returns a `500` status.
 6. Apply [https://github.com/WordPress/wordpress-develop/pull/2400 PR
 2400]
 7. Observe that the request to the media endpoint no longer returns a
 `500` status.
 === Results
 1. Before [https://github.com/WordPress/wordpress-develop/pull/2400 PR
 2400]: Received a `500` status.
 2. After [https://github.com/WordPress/wordpress-develop/pull/2400 PR
 2400]: Did not receive a `500` status.

 PR resolves the issue. 👍

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

From noreply at wordpress.org  Fri Mar 11 22:55:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 22:55:30 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
In-Reply-To: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
References: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
Message-ID: <068.1908f6c70d2a9c81f073ceb6fa3d4f91@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
--------------------------------------+---------------------
 Reporter:  talldanwp                 |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  REST API                  |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------
Changes (by costdev):

 * Attachment "55367-before-after-pr-2400.jpg" added.

 Before / After PR 2400

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

From noreply at wordpress.org  Fri Mar 11 23:18:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 23:18:17 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.4957d111e936bdbd79ab583ea82483d3@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
---------------------------------------+---------------------
 Reporter:  kajalgohel                 |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:  6.0
Component:  Bundled Theme              |     Version:  3.6
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:
---------------------------------------+---------------------
Changes (by costdev):

 * keywords:  has-screenshots has-patch needs-testing => has-screenshots
     has-patch
 * version:   => 3.6


Comment:

 == Test Report

 === Env
 * Web Server: Apache (Linux)
 * WordPress: 6.0-alpha-52448-src
 * Browser: Chrome
 * OS: Windows 10
 * Theme: Twenty Thirteen
 * Plugins: None activated.

 === Steps to test
 1. View a post on the frontend.
 2. Scroll to the comments section.
 3. Add a comment.
 4. Click "Reply" under the comment you just created. The `X` button should
 appear to the right.
 5. Apply
 [https://core.trac.wordpress.org/attachment/ticket/55362/%2355362.patch
 55362.patch].
 6. Refresh the page.
 7. Click "Reply". The `X` button should not have changed in any way.

 Tested in responsive mode also.

 === Results
 1. No visible regressions.
 2. [https://core.trac.wordpress.org/attachment/ticket/55362/%2355362.patch
 55362.patch] seems to cleanly resolve the invalid use of `inline-block`
 and `float` per [https://developer.mozilla.org/en-US/docs/Web/CSS/float
 MDN Reference: `float`].

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

From noreply at wordpress.org  Fri Mar 11 23:28:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 23:28:58 -0000
Subject: [wp-trac] [WordPress Trac] #55373: Attachment template: Rename
 from "Media" to "Attachment"
In-Reply-To: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
References: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
Message-ID: <068.6f6d6810e51bf5fe9bb388402ef717d5@wordpress.org>

#55373: Attachment template: Rename from "Media" to "Attachment"
-------------------------+----------------------------
 Reporter:  scruffian    |       Owner:  davidbaumwald
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  6.0
Component:  Editor       |     Version:  5.9
 Severity:  normal       |  Resolution:  fixed
 Keywords:  commit       |     Focuses:
-------------------------+----------------------------
Changes (by davidbaumwald):

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


Comment:

 In [changeset:"52923" 52923]:
 {{{
 #!CommitTicketReference repository="" revision="52923"
 Site Editor: Rename the default attachment template from "Media" to
 "Attachment".

 Follow-up to [52062].

 Props scruffian, costdev.
 Fixes #55373.
 }}}

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

From noreply at wordpress.org  Fri Mar 11 23:30:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 23:30:09 -0000
Subject: [wp-trac] [WordPress Trac] #55349: Not able to embed videos
In-Reply-To: <052.fa9fd9c46f123877f72c619166e3398c@wordpress.org>
References: <052.fa9fd9c46f123877f72c619166e3398c@wordpress.org>
Message-ID: <067.7e9354bb153a06108f05a0820a16e7e2@wordpress.org>

#55349: Not able to embed videos
--------------------------+----------------------
 Reporter:  nm977890      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Embeds        |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by costdev):

 * status:  new => closed
 * version:  5.8.3 =>
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Hi @nm977890, welcome to Trac!

 Sorry to hear you're having trouble viewing an embedded video.

 Trac is for the development of WordPress Core, whereas the problem that
 you have encountered is a support issue, possibly due to a problem with
 the embed code you're using.

 Please head on over to [https://wordpress.org/support/forums/ the support
 forums] to get some help tracking down the issue from the folks there.

 I'll close this ticket, but if your discussions on the support forums
 point to an issue in WordPress Core, you can reopen this ticket to report
 all of the information that you've found out.

 Best of luck!

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

From noreply at wordpress.org  Fri Mar 11 23:36:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 23:36:40 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.2037bfa2349a2f2bb2c75db81d5442e3@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------+---------------------
 Reporter:  kajalgohel               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:  3.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css
-------------------------------------+---------------------
Changes (by costdev):

 * version:   => 3.2


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

From noreply at wordpress.org  Fri Mar 11 23:49:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 11 Mar 2022 23:49:43 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.279679da22aa54cdb218119b28a093fc@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
---------------------------------------+---------------------
 Reporter:  kajalgohel                 |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:  6.0
Component:  Bundled Theme              |     Version:  3.6
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:  css
---------------------------------------+---------------------
Changes (by costdev):

 * focuses:   => css


Comment:

 Adding `css` focus to get feedback on whether this change should be made.

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

From noreply at wordpress.org  Sat Mar 12 00:09:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 00:09:48 -0000
Subject: [wp-trac] [WordPress Trac] #55356: Use safecss_filter_attr()
 instead of wp_strip_all_tags() in wp_get_layout_style()
In-Reply-To: <058.9be881feebf632f30b5f6d8b3964ad18@wordpress.org>
References: <058.9be881feebf632f30b5f6d8b3964ad18@wordpress.org>
Message-ID: <073.81f3c176faf37cc6e0c4a88ecc4dbbee@wordpress.org>

#55356: Use safecss_filter_attr() instead of wp_strip_all_tags() in
wp_get_layout_style()
------------------------------+----------------------------
 Reporter:  grapplerulrich    |       Owner:  davidbaumwald
     Type:  defect (bug)      |      Status:  reviewing
 Priority:  normal            |   Milestone:  6.0
Component:  Formatting        |     Version:  5.9
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+----------------------------
Changes (by davidbaumwald):

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


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

From noreply at wordpress.org  Sat Mar 12 00:27:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 00:27:39 -0000
Subject: [wp-trac] [WordPress Trac] #55356: Use safecss_filter_attr()
 instead of wp_strip_all_tags() in wp_get_layout_style()
In-Reply-To: <058.9be881feebf632f30b5f6d8b3964ad18@wordpress.org>
References: <058.9be881feebf632f30b5f6d8b3964ad18@wordpress.org>
Message-ID: <073.7cdc81ca97d7a87f8ec2077cf1f0fab8@wordpress.org>

#55356: Use safecss_filter_attr() instead of wp_strip_all_tags() in
wp_get_layout_style()
------------------------------+----------------------------
 Reporter:  grapplerulrich    |       Owner:  davidbaumwald
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  6.0
Component:  Formatting        |     Version:  5.9
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:
------------------------------+----------------------------
Changes (by davidbaumwald):

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


Comment:

 In [changeset:"52924" 52924]:
 {{{
 #!CommitTicketReference repository="" revision="52924"
 Formatting: Use `safecss_filter_attr` in `wp_get_layout_style()`.

 Previously, `safecss_filter_attr` did not allow for `calc` and `var` in
 parsed CSS.  Because of this, `wp_strip_all_tags` was used in
 `wp_get_layout_style` to allow for the use of these CSS functions to
 account for responsive widths.  [50923] added support for both of these
 CSS functions in KSES, so `safecss_filter_attr` can now be used in
 `wp_get_layout_style` as originally intended.

 Follow-up to [52069].

 Props grapplerulrich.
 Fixes #55356.
 }}}

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

From noreply at wordpress.org  Sat Mar 12 01:32:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 01:32:09 -0000
Subject: [wp-trac] [WordPress Trac] #48030: HTML5 input types are not
 being reset when submitting the addtag form
In-Reply-To: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
References: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
Message-ID: <072.f04abb6e58e9aca1660b10cef001baea@wordpress.org>

#48030: HTML5 input types are not being reset when submitting the addtag form
-----------------------------+---------------------------------------------
 Reporter:  stevegrunwell    |       Owner:  davidbaumwald
     Type:  defect (bug)     |      Status:  reviewing
 Priority:  normal           |   Milestone:  6.0
Component:  Taxonomy         |     Version:
 Severity:  minor            |  Resolution:
 Keywords:  has-patch        |     Focuses:  ui, javascript, administration
  needs-testing              |
-----------------------------+---------------------------------------------
Changes (by davidbaumwald):

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


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

From noreply at wordpress.org  Sat Mar 12 01:40:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 01:40:10 -0000
Subject: [wp-trac] [WordPress Trac] #54435: admin-ajax.php : 404 Error
In-Reply-To: <052.ae447622d99701b5886e1aae8c32028c@wordpress.org>
References: <052.ae447622d99701b5886e1aae8c32028c@wordpress.org>
Message-ID: <067.d296ffb7f0fe588a1507294025f47059@wordpress.org>

#54435: admin-ajax.php : 404 Error
--------------------------+------------------------------
 Reporter:  Mayhem30      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by here):

 I found this investigating a similar issue and it turns out this behavior
 is as designed.

 Steps to repro:
 1. Open Customizer
 2. Click X to close Customizer

 Observed: 404 error requesting admin-ajax.php
 Expected: No errors

 For my case, searching for the admin-ajax action value used in the POST
 request "customize_dismiss_autosave_or_lock" leads to the associated core
 code.

 WordPress core code that is returning the 404 can be seen here,
 https://github.com/WordPress/WordPress/blob/99bac7e17cfb5d534b33ffc3a70bff9d9b86875d
 /wp-includes/class-wp-customize-manager.php#L3693-L3695

 Sample POST payload
 {{{
 wp_customize: on
 customize_theme: example-theme
 customize_changeset_uuid: ac3050d5-df08-4c20-a8e9-88fa37974652
 nonce: 6a2eb1176f
 dismiss_autosave: false
 dismiss_lock: true
 action: customize_dismiss_autosave_or_lock
 customize_preview_nonce: b43e42ab81
 }}}


 A sample request / response body is

 {{{
 $ curl 'https://example.com/wp-admin/admin-ajax.php'
 ...
 --data-raw 'wp_customize=on&customize_theme=example-
 theme&customize_changeset_uuid=9fd9e3ff-7209-4a6b-9a2e-
 708e5e2bf5fa&nonce=993d76371b&dismiss_autosave=false&dismiss_lock=true&action=customize_dismiss_autosave_or_lock&customize_preview_nonce=c893d9add4'
 \
 ...
 < HTTP/2 404
 ...
 {"success":false,"data":"no_auto_draft_to_delete"}
 }}}

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

From noreply at wordpress.org  Sat Mar 12 01:43:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 01:43:38 -0000
Subject: [wp-trac] [WordPress Trac] #42942: Provide a
 post_date_column_time hook for media files
In-Reply-To: <054.b8ba66020e3f87a90d888b926a23b5f9@wordpress.org>
References: <054.b8ba66020e3f87a90d888b926a23b5f9@wordpress.org>
Message-ID: <069.f537b2ce24c175c933d80f028fdc5d94@wordpress.org>

#42942: Provide a post_date_column_time hook for media files
------------------------------------+----------------------------
 Reporter:  ivanlutrov              |       Owner:  davidbaumwald
     Type:  feature request         |      Status:  reviewing
 Priority:  normal                  |   Milestone:  6.0
Component:  Administration          |     Version:  5.1
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+----------------------------
Changes (by davidbaumwald):

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


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

From noreply at wordpress.org  Sat Mar 12 01:46:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 01:46:24 -0000
Subject: [wp-trac] [WordPress Trac] #55105: Introduce a polyfill for
 `array_is_list()`.
In-Reply-To: <051.b8ae2c08f5ad2c8bbe71037bcf23450d@wordpress.org>
References: <051.b8ae2c08f5ad2c8bbe71037bcf23450d@wordpress.org>
Message-ID: <066.7c55e8ae766ed28cce390d0c9f48eeb5@wordpress.org>

#55105: Introduce a polyfill for `array_is_list()`.
---------------------------------------------------+---------------------
 Reporter:  costdev                                |       Owner:  (none)
     Type:  feature request                        |      Status:  new
 Priority:  normal                                 |   Milestone:  6.0
Component:  General                                |     Version:  5.9
 Severity:  minor                                  |  Resolution:
 Keywords:  has-patch has-unit-tests dev-feedback  |     Focuses:
---------------------------------------------------+---------------------
Changes (by davidbaumwald):

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


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

From noreply at wordpress.org  Sat Mar 12 01:50:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 01:50:05 -0000
Subject: [wp-trac] [WordPress Trac] #54987: Check if 'user_nicename' is
 not too long after the 'pre_user_nicename' filter
In-Reply-To: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
References: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
Message-ID: <073.f282ea5437d150001c26e4fb0d9e0d14@wordpress.org>

#54987: Check if 'user_nicename' is not too long after the 'pre_user_nicename'
filter
--------------------------------------+----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  davidbaumwald
     Type:  defect (bug)              |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Users                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+----------------------------
Changes (by davidbaumwald):

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


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

From noreply at wordpress.org  Sat Mar 12 01:54:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 01:54:27 -0000
Subject: [wp-trac] [WordPress Trac] #55300: tests for
 WP_List_Util::pluck and WP_List_Util::sort
In-Reply-To: <051.dd5ff02912bce1bb03a5640324c5d38c@wordpress.org>
References: <051.dd5ff02912bce1bb03a5640324c5d38c@wordpress.org>
Message-ID: <066.249bb0fbafeacf1df9100857ec1f3311@wordpress.org>

#55300: tests for WP_List_Util::pluck and WP_List_Util::sort
--------------------------------------+---------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by davidbaumwald):

 Related #54751.

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

From noreply at wordpress.org  Sat Mar 12 01:54:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 01:54:42 -0000
Subject: [wp-trac] [WordPress Trac] #54751: Invalid argument in
 class-wp-list-util.php
In-Reply-To: <049.3061f13327d6bc39d75916df3117d902@wordpress.org>
References: <049.3061f13327d6bc39d75916df3117d902@wordpress.org>
Message-ID: <064.ed8b6a0eb9a4e67c07bceae766d51f0b@wordpress.org>

#54751: Invalid argument in class-wp-list-util.php
-----------------------------------------------------+---------------------
 Reporter:  marv2                                    |       Owner:  (none)
     Type:  defect (bug)                             |      Status:  new
 Priority:  normal                                   |   Milestone:  6.0
Component:  General                                  |     Version:  3.1
 Severity:  normal                                   |  Resolution:
 Keywords:  good-first-bug has-patch has-unit-tests  |     Focuses:
-----------------------------------------------------+---------------------

Comment (by davidbaumwald):

 Related #55300.

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

From noreply at wordpress.org  Sat Mar 12 03:04:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 03:04:12 -0000
Subject: [wp-trac] [WordPress Trac] #55381: Title is replace by Quantcast
 all post title
Message-ID: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>

#55381: Title is replace by Quantcast all post title
--------------------------+-----------------------------
 Reporter:  shashi0       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  critical      |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Title is replace by Quantcast text all post title is being replaced by
 this word When I open post then title showing which I have put during
 article writing on post u can check.
 https://shashibhushan.com.np/csc-scholarship-china/

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

From noreply at wordpress.org  Sat Mar 12 03:04:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 03:04:40 -0000
Subject: [wp-trac] [WordPress Trac] #55381: Title is replace by
 Quantcast all post title
In-Reply-To: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
References: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
Message-ID: <066.a7be4bcf0274de161bcb64cf675e2d70@wordpress.org>

#55381: Title is replace by Quantcast all post title
--------------------------+------------------------------
 Reporter:  shashi0       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by shashi0):

 * Attachment
 "Screenshot_2022-03-11-23-10-17-33_40deb401b9ffe8e1df2f1cc5ba480b12.jpg"
 added.


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

From noreply at wordpress.org  Sat Mar 12 03:08:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 03:08:06 -0000
Subject: [wp-trac] [WordPress Trac] #55381: Title is replace by
 Quantcast all post title
In-Reply-To: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
References: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
Message-ID: <066.2da484cce548acc3ae6b75a33f17f9b8@wordpress.org>

#55381: Title is replace by Quantcast all post title
--------------------------+----------------------
 Reporter:  shashi0       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by costdev):

 * status:  new => closed
 * severity:  critical => normal
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Old description:

> Title is replace by Quantcast text all post title is being replaced by
> this word When I open post then title showing which I have put during
> article writing on post u can check.
> https://shashibhushan.com.np/csc-scholarship-china/

New description:

 Title is replace by Quantcast text all post title is being replaced by
 this word When I open post then title showing which I have put during
 article writing on post u can check.
 **website link removed**

--

Comment:

 Hi @shashi0, welcome to Trac!

 Trac is for the development of WordPress Core, whereas you appear to need
 some support.

 Please head on over to [https://wordpress.org/support/forums/ the support
 forums] to get help from the folks there.

 Best of luck!

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

From noreply at wordpress.org  Sat Mar 12 03:14:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 03:14:55 -0000
Subject: [wp-trac] [WordPress Trac] #55381: Title is replace by
 Quantcast all post title
In-Reply-To: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
References: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
Message-ID: <066.f3d1713d98de3631ff350bec78ff4ed2@wordpress.org>

#55381: Title is replace by Quantcast all post title
--------------------------+-----------------------
 Reporter:  shashi0       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Changes (by shashi0):

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


Comment:

 Replying to [comment:1 costdev]:
 > Hi @shashi0, welcome to Trac!
 >
 > Trac is for the development of WordPress Core, whereas you appear to
 need some support.
 >
 > Please head on over to [https://wordpress.org/support/forums/ the
 support forums] to get help from the folks there.
 >
 > Best of luck!

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

From noreply at wordpress.org  Sat Mar 12 03:18:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 03:18:07 -0000
Subject: [wp-trac] [WordPress Trac] #55381: Title is replace by
 Quantcast all post title
In-Reply-To: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
References: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
Message-ID: <066.2bb65aa943dbad194130e29e1fc93746@wordpress.org>

#55381: Title is replace by Quantcast all post title
-----------------------------+-----------------------
 Reporter:  shashi0          |       Owner:  (none)
     Type:  enhancement      |      Status:  reopened
 Priority:  normal           |   Milestone:
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+-----------------------
Changes (by shashi0):

 * keywords:   => has-screenshots
 * type:  defect (bug) => enhancement


Comment:

 Plz fixed my issues when I updated from that time this issues showing.

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

From noreply at wordpress.org  Sat Mar 12 04:03:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 04:03:17 -0000
Subject: [wp-trac] [WordPress Trac] #55381: Title is replace by
 Quantcast all post title
In-Reply-To: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
References: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
Message-ID: <066.e20e29a9f9337f9ce89bfc33fecde2cc@wordpress.org>

#55381: Title is replace by Quantcast all post title
-----------------------------+----------------------
 Reporter:  shashi0          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |     Version:
 Severity:  normal           |  Resolution:  invalid
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+----------------------
Changes (by costdev):

 * status:  reopened => closed
 * type:  enhancement => defect (bug)
 * resolution:   => invalid


Comment:

 @shashi0 See the highlighted section on [https://wordpress.org/plugins
 /quantcast-choice/ this page].

 The plugin you are using has not been tested with the latest 3 major
 releases of WordPress. This means it may have compatibility issues with
 newer versions of WordPress.

 I encourage you to post on [https://wordpress.org/support/plugin
 /quantcast-choice/ that plugin's support forum] and/or
 [https://wordpress.org/support/forums/ the WordPress support forums].

 Trac cannot provide support for your website or for plugins (especially
 those that have not been tested for several major releases of WordPress).

 Please request support from one of the support forums above, who are there
 to help you try to fix this type of issue.

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

From noreply at wordpress.org  Sat Mar 12 04:17:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 04:17:31 -0000
Subject: [wp-trac] [WordPress Trac] #55381: Title is replace by
 Quantcast all post title
In-Reply-To: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
References: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
Message-ID: <066.fff68a48fa3771da034b185cff98dbb7@wordpress.org>

#55381: Title is replace by Quantcast all post title
-----------------------------+-----------------------
 Reporter:  shashi0          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  reopened
 Priority:  normal           |   Milestone:
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+-----------------------
Changes (by shashi0):

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


Comment:

 Replying to [comment:4 costdev]:
 > @shashi0 See the highlighted section on [https://wordpress.org/plugins
 /quantcast-choice/ this page].
 >
 > The plugin you are using has not been tested with the latest 3 major
 releases of WordPress. This means it may have compatibility issues with
 newer versions of WordPress.
 >
 > I encourage you to post on [https://wordpress.org/support/plugin
 /quantcast-choice/ that plugin's support forum] and/or
 [https://wordpress.org/support/forums/ the WordPress support forums].
 >
 > Trac cannot provide support for your website or for plugins (especially
 those that have not been tested for several major releases of WordPress).
 >
 > Please request support from one of the support forums above, who are
 there to help you try to fix this type of issue.

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

From noreply at wordpress.org  Sat Mar 12 04:18:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 04:18:26 -0000
Subject: [wp-trac] [WordPress Trac] #55381: Title is replace by
 Quantcast all post title
In-Reply-To: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
References: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
Message-ID: <066.1ac299c48ec782d44a416f6fc3ac5f0d@wordpress.org>

#55381: Title is replace by Quantcast all post title
-----------------------------+-----------------------
 Reporter:  shashi0          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  reopened
 Priority:  normal           |   Milestone:
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+-----------------------

Comment (by shashi0):

 I am not using that plugin all article titles has been replaced by that
 Quantcast word.

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

From noreply at wordpress.org  Sat Mar 12 04:32:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 04:32:21 -0000
Subject: [wp-trac] [WordPress Trac] #55381: Title is replace by
 Quantcast all post title
In-Reply-To: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
References: <051.506f3a19d56814358f77d0c9a0b8416c@wordpress.org>
Message-ID: <066.377be3f7b20abbdc984f2ebde650f20b@wordpress.org>

#55381: Title is replace by Quantcast all post title
-----------------------------+----------------------
 Reporter:  shashi0          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  General          |     Version:
 Severity:  normal           |  Resolution:  invalid
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+----------------------
Changes (by costdev):

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


Comment:

 That plugin was installed and activated on your site, as it showed in the
 source code. The plugin has since been disabled.

 I remind you that Trac is not for website support, and you should instead
 ask for help with this issue on [https://wordpress.org/support/forums/ the
 WordPress support forums].

 Please do not keep reopening this ticket.

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

From noreply at wordpress.org  Sat Mar 12 09:41:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 09:41:20 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.85e859506f3ca20c9853635cdf51e287@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:  ui-copy
  refresh                                        |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  good-first-bug has-patch has-unit-tests => has-patch has-unit-
     tests needs-refresh
 * owner:  (none) => audrasjb
 * status:  reviewing => accepted


Comment:

 Self assigning to refresh the PR, and removing `good-first-bug` tag.

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

From noreply at wordpress.org  Sat Mar 12 10:01:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 10:01:48 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.f332cf849cb83c5089f00fdb4878616a@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  accepted
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------

Comment (by BettyJJ):

 @afercia Thank you very much. This new patch works for me. :)

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

From noreply at wordpress.org  Sat Mar 12 10:05:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 10:05:45 -0000
Subject: [wp-trac] [WordPress Trac] #40492: Twenty Fifteen: Jumping if
 there is content just before the closing body tag
In-Reply-To: <057.284cc44ea09922081368f4d3ce3a80d4@wordpress.org>
References: <057.284cc44ea09922081368f4d3ce3a80d4@wordpress.org>
Message-ID: <072.c1279ce541e9a87108d7757604387d88@wordpress.org>

#40492: Twenty Fifteen: Jumping if there is content just before the closing body
tag
-------------------------------------+-------------------------
 Reporter:  stephenharris            |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:  4.7.1
 Severity:  minor                    |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  javascript
-------------------------------------+-------------------------
Changes (by audrasjb):

 * Attachment "5bac9815a83620c97a0d9cef3efd6c57.mp4" added.

 Not reproductible on my side

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

From noreply at wordpress.org  Sat Mar 12 10:09:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 10:09:02 -0000
Subject: [wp-trac] [WordPress Trac] #40492: Twenty Fifteen: Jumping if
 there is content just before the closing body tag
In-Reply-To: <057.284cc44ea09922081368f4d3ce3a80d4@wordpress.org>
References: <057.284cc44ea09922081368f4d3ce3a80d4@wordpress.org>
Message-ID: <072.b3c10082b6033c59ec6e542fb4d99b17@wordpress.org>

#40492: Twenty Fifteen: Jumping if there is content just before the closing body
tag
-------------------------------------------------+-------------------------
 Reporter:  stephenharris                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:  4.7.1
 Severity:  minor                                |  Resolution:
 Keywords:  has-patch needs-testing dev-         |     Focuses:  javascript
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch needs-testing => has-patch needs-testing dev-
               feedback


Comment:

 Hi,

 I tried to reproduce the issue on Twenty Fifteen using the following hook
 but I wasn't able to see the bug (see the above video capture). Does it
 still occurs on your side @sabernhardt?


 {{{
 function sabwp_twenty_fifteen_top_link() {
         echo '<a href="#page"
 style="background:rgba(255,244,111,0.8);color:#157;position:fixed;bottom:10px;right:10px;padding:10px;">Back
 to top</a>';
 }
 add_action('wp_footer', 'sabwp_twenty_fifteen_top_link', 10);
 }}}

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

From noreply at wordpress.org  Sat Mar 12 16:15:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 16:15:42 -0000
Subject: [wp-trac] [WordPress Trac] #55382: WordPress 5.9.2 bug,
 conflict with LiteSpeed Cache
Message-ID: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>

#55382: WordPress 5.9.2 bug,conflict with LiteSpeed Cache
--------------------------+-----------------------------
 Reporter:  tatuatu       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  critical      |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 WordPress 5.9.2 broke my site,I went back to version 5.9.1 and everything
 is perfect

 Has a conflict with LiteSpeed Cache, if I disable it it returns to normal.

 I deleted the cache but it does the same, I uninstalled and reinstalled
 LiteSpeed Cache return to normal 2 minutes after it breaks again.
 version 5.9.1 no problems, it works perfectly.

 https://ibb.co/bs491Jj
 https://ibb.co/rvnStTC

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

From noreply at wordpress.org  Sat Mar 12 16:16:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 16:16:05 -0000
Subject: [wp-trac] [WordPress Trac] #55382: WordPress 5.9.2 bug,
 conflict with LiteSpeed Cache
In-Reply-To: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
References: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
Message-ID: <066.ca29d8677f7434e7ef69fbffcf459a58@wordpress.org>

#55382: WordPress 5.9.2 bug,conflict with LiteSpeed Cache
--------------------------+------------------------------
 Reporter:  tatuatu       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by tatuatu):

 * Attachment "222Untitled.png" added.


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

From noreply at wordpress.org  Sat Mar 12 16:16:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 16:16:17 -0000
Subject: [wp-trac] [WordPress Trac] #55382: WordPress 5.9.2 bug,
 conflict with LiteSpeed Cache
In-Reply-To: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
References: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
Message-ID: <066.afc0a29f4093758695d75f423d207948@wordpress.org>

#55382: WordPress 5.9.2 bug,conflict with LiteSpeed Cache
--------------------------+------------------------------
 Reporter:  tatuatu       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by tatuatu):

 * Attachment "111Untitled.png" added.


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

From noreply at wordpress.org  Sat Mar 12 17:11:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 17:11:24 -0000
Subject: [wp-trac] [WordPress Trac] #55382: WordPress 5.9.2 bug,
 conflict with LiteSpeed Cache
In-Reply-To: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
References: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
Message-ID: <066.2471b1e1aec2f19a2bb83536c9e2090c@wordpress.org>

#55382: WordPress 5.9.2 bug,conflict with LiteSpeed Cache
--------------------------+----------------------
 Reporter:  tatuatu       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by costdev):

 * status:  new => closed
 * resolution:   => invalid
 * component:  General => Plugins
 * severity:  critical => normal
 * milestone:  Awaiting Review =>


Comment:

 Hi @tatuatu, welcome to Trac!

 Trac is for the development of WordPress Core, whereas this issue may be a
 problem with the LiteSpeed Cache plugin itself. Please reach out to the
 LiteSpeed Cache plugin developers on [https://wordpress.org/support/plugin
 /litespeed-cache/ the LiteSpeed Cache plugin support forum].

 Some suggestions for your post on [https://wordpress.org/support/plugin
 /litespeed-cache/ the LiteSpeed Cache plugin support forum]:

 1. Read LiteSpeed Cache's [https://wordpress.org/support/topic/please-
 read-before-posting-89/ Please Read Before Posting] post.
 2. Explain what you mean by "breaks my site".
    - Does the site fail to load at all?
    - Do stylesheets or scripts fail to load?
    - Does it perform slower? etc.
 3. Clarify whether you are using the latest version of the LiteSpeed Cache
 plugin
    - The plugin was updated a couple of weeks ago.

 I'll close this ticket as this is a plugin support request. If after
 discussing the issue with the LiteSpeed Cache plugin team, they determine
 that there is an issue in WordPress Core, please return to Trac and let us
 know what has been discovered.

 Best of luck!

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

From noreply at wordpress.org  Sat Mar 12 17:23:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 17:23:31 -0000
Subject: [wp-trac] [WordPress Trac] #55373: Attachment template: Rename
 from "Media" to "Attachment"
In-Reply-To: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
References: <053.5badf15f4756f2e0685d9e3287845d07@wordpress.org>
Message-ID: <068.c0cf0e7f723f14a206adadfbb9795609@wordpress.org>

#55373: Attachment template: Rename from "Media" to "Attachment"
-------------------------+----------------------------
 Reporter:  scruffian    |       Owner:  davidbaumwald
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  6.0
Component:  Editor       |     Version:  5.9
 Severity:  normal       |  Resolution:  fixed
 Keywords:  commit       |     Focuses:
-------------------------+----------------------------

Comment (by azouamauriac):

 this one should be reported upstream, isn't?

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

From noreply at wordpress.org  Sat Mar 12 17:38:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 17:38:45 -0000
Subject: [wp-trac] [WordPress Trac] #52683: Twenty Twenty-One: Block
 "more" text in link can't be changed
In-Reply-To: <053.542859deaa6edd2ec48c5fd6868ec812@wordpress.org>
References: <053.542859deaa6edd2ec48c5fd6868ec812@wordpress.org>
Message-ID: <068.1c31539f813813021f65940eef65894b@wordpress.org>

#52683: Twenty Twenty-One: Block "more" text in link can't be changed
---------------------------+---------------------
 Reporter:  neokendev      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:  5.6.2
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------

Comment (by audrasjb):

 Self assigning for review.

 @sabernhardt thanks for the translation proposal, I approved the change on
 translate.wordpress.org👌

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

From noreply at wordpress.org  Sat Mar 12 17:38:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 17:38:51 -0000
Subject: [wp-trac] [WordPress Trac] #52683: Twenty Twenty-One: Block
 "more" text in link can't be changed
In-Reply-To: <053.542859deaa6edd2ec48c5fd6868ec812@wordpress.org>
References: <053.542859deaa6edd2ec48c5fd6868ec812@wordpress.org>
Message-ID: <068.6e1027654e7b217c35f0030ae69e443c@wordpress.org>

#52683: Twenty Twenty-One: Block "more" text in link can't be changed
---------------------------+------------------------
 Reporter:  neokendev      |       Owner:  audrasjb
     Type:  defect (bug)   |      Status:  reviewing
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:  5.6.2
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+------------------------
Changes (by audrasjb):

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


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

From noreply at wordpress.org  Sat Mar 12 17:51:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 17:51:24 -0000
Subject: [wp-trac] [WordPress Trac] #52683: Twenty Twenty-One: Block
 "more" text in link can't be changed
In-Reply-To: <053.542859deaa6edd2ec48c5fd6868ec812@wordpress.org>
References: <053.542859deaa6edd2ec48c5fd6868ec812@wordpress.org>
Message-ID: <068.14c4a67579db9fcd1acd821cf28a0914@wordpress.org>

#52683: Twenty Twenty-One: Block "more" text in link can't be changed
------------------------------------+------------------------
 Reporter:  neokendev               |       Owner:  audrasjb
     Type:  defect (bug)            |      Status:  reviewing
 Priority:  normal                  |   Milestone:  6.0
Component:  Bundled Theme           |     Version:  5.6.2
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+------------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch dev-feedback


Comment:

 @sabernhardt I tested 52683.diff, but using "Summary" option on Excerpt
 settings, I doesn't show any link at all: I have a customized read more
 block on one post, and a normal post with a lot of text, and in both case
 I don't have any "more" link. Is it expected?

 By the way, we can still commit the Translator string change since it's
 pretty confusing for translators. Maybe it's worth opening a new ticket
 for this change?

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

From noreply at wordpress.org  Sat Mar 12 18:16:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 18:16:15 -0000
Subject: [wp-trac] [WordPress Trac] #53951: Twenty Twenty: Search modal
 aria-expanded
In-Reply-To: <050.12159b56833732edace4c7af59831987@wordpress.org>
References: <050.12159b56833732edace4c7af59831987@wordpress.org>
Message-ID: <065.7bcfeaf109d5c4b6d0276d05e1795d76@wordpress.org>

#53951: Twenty Twenty: Search modal aria-expanded
-------------------------------------+-------------------------------------
 Reporter:  utz119                   |       Owner:  alexstine
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-testing-   |     Focuses:  accessibility,
  instructions dev-feedback          |  javascript
-------------------------------------+-------------------------------------
Changes (by audrasjb):

 * keywords:  has-patch has-testing-instructions needs-testing => has-patch
     has-testing-instructions dev-feedback


Comment:

 `53951-4.diff` works when pressing `esc` twice, but it doesn't remove the
 `aria-expanded="true"` attribute when I only press `esc` once. Is it
 expected?

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

From noreply at wordpress.org  Sat Mar 12 18:42:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 18:42:35 -0000
Subject: [wp-trac] [WordPress Trac] #54169: Twenty Nineteen: columns set
 to Full width extend beyond editor window bounds
In-Reply-To: <063.bacdd4520273721d5ae4a7d801402361@wordpress.org>
References: <063.bacdd4520273721d5ae4a7d801402361@wordpress.org>
Message-ID: <078.0313e89e3dfaaa0cbd2833557e2718b7@wordpress.org>

#54169: Twenty Nineteen: columns set to Full width extend beyond editor window
bounds
-------------------------------------+---------------------
 Reporter:  charleyparkerdesign      |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:  5.8.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css
-------------------------------------+---------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-12 à 19.38.40.png" added.

 Before applying the pull request

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

From noreply at wordpress.org  Sat Mar 12 18:42:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 18:42:59 -0000
Subject: [wp-trac] [WordPress Trac] #54169: Twenty Nineteen: columns set
 to Full width extend beyond editor window bounds
In-Reply-To: <063.bacdd4520273721d5ae4a7d801402361@wordpress.org>
References: <063.bacdd4520273721d5ae4a7d801402361@wordpress.org>
Message-ID: <078.d0bd2c806919a8044e070474c0a511b5@wordpress.org>

#54169: Twenty Nineteen: columns set to Full width extend beyond editor window
bounds
-------------------------------------+---------------------
 Reporter:  charleyparkerdesign      |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:  5.8.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css
-------------------------------------+---------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-12 à 19.41.42.png" added.

 After applying the pull request: it fixes the issue

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

From noreply at wordpress.org  Sat Mar 12 18:43:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 18:43:46 -0000
Subject: [wp-trac] [WordPress Trac] #54169: Twenty Nineteen: columns set
 to Full width extend beyond editor window bounds
In-Reply-To: <063.bacdd4520273721d5ae4a7d801402361@wordpress.org>
References: <063.bacdd4520273721d5ae4a7d801402361@wordpress.org>
Message-ID: <078.207dab5a1038e46f05953d91d6fd97d3@wordpress.org>

#54169: Twenty Nineteen: columns set to Full width extend beyond editor window
bounds
----------------------------------------------+-----------------------
 Reporter:  charleyparkerdesign               |       Owner:  audrasjb
     Type:  defect (bug)                      |      Status:  assigned
 Priority:  normal                            |   Milestone:  6.0
Component:  Bundled Theme                     |     Version:  5.8.1
 Severity:  normal                            |  Resolution:
 Keywords:  has-patch has-screenshots commit  |     Focuses:  css
----------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch needs-testing => has-patch has-screenshots commit
 * owner:  (none) => audrasjb
 * status:  new => assigned


Comment:

 The above PR fixes the issue.
 Self assigning for `commit`.

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

From noreply at wordpress.org  Sat Mar 12 19:11:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 19:11:47 -0000
Subject: [wp-trac] [WordPress Trac] #54169: Twenty Nineteen: columns set
 to Full width extend beyond editor window bounds
In-Reply-To: <063.bacdd4520273721d5ae4a7d801402361@wordpress.org>
References: <063.bacdd4520273721d5ae4a7d801402361@wordpress.org>
Message-ID: <078.a09180ab611730aefe65739b91521078@wordpress.org>

#54169: Twenty Nineteen: columns set to Full width extend beyond editor window
bounds
----------------------------------------------+-----------------------
 Reporter:  charleyparkerdesign               |       Owner:  audrasjb
     Type:  defect (bug)                      |      Status:  closed
 Priority:  normal                            |   Milestone:  6.0
Component:  Bundled Theme                     |     Version:  5.8.1
 Severity:  normal                            |  Resolution:  fixed
 Keywords:  has-patch has-screenshots commit  |     Focuses:  css
----------------------------------------------+-----------------------
Changes (by audrasjb):

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


Comment:

 In [changeset:"52925" 52925]:
 {{{
 #!CommitTicketReference repository="" revision="52925"
 Twenty Nineteen: avoid columns set to full width to extend beyond editor
 bounds.

 This changeset applies `max-width` and `margin` CSS rules when `block-
 editor-writing-flow` and `editor-styles-wrapper` classes are on the same
 element.

 Props charleyparkerdesign, sabernhardt, smit08, sclayf1.
 Fixes #54169.
 }}}

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

From noreply at wordpress.org  Sat Mar 12 19:14:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 19:14:08 -0000
Subject: [wp-trac] [WordPress Trac] #49985: REST API: Using _embed and
 _fields query parameters in the same query
In-Reply-To: <059.6e499a4b3c74df8b6283d93cb09764e4@wordpress.org>
References: <059.6e499a4b3c74df8b6283d93cb09764e4@wordpress.org>
Message-ID: <074.6b7755c332f615fe8d2b64e38019c188@wordpress.org>

#49985: REST API: Using _embed and _fields query parameters in the same query
--------------------------------------------+------------------------------
 Reporter:  anouarbenothman                 |       Owner:
                                            |  TimothyBlynJacobs
     Type:  defect (bug)                    |      Status:  assigned
 Priority:  normal                          |   Milestone:  6.0
Component:  REST API                        |     Version:  5.4
 Severity:  normal                          |  Resolution:
 Keywords:  early has-patch has-unit-tests  |     Focuses:  rest-api
--------------------------------------------+------------------------------

Comment (by costdev):

 @TimothyBlynJacobs [https://github.com/WordPress/wordpress-
 develop/pull/867 PR 867] was updated with some changes after your
 feedback. Are you available to do another review on the PR and we'll try
 to land this one in 6.0?

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

From noreply at wordpress.org  Sat Mar 12 19:24:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 19:24:11 -0000
Subject: [wp-trac] [WordPress Trac] #55382: WordPress 5.9.2 bug,
 conflict with LiteSpeed Cache
In-Reply-To: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
References: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
Message-ID: <066.d5a6f5894096041e3ad8e0cff862509a@wordpress.org>

#55382: WordPress 5.9.2 bug,conflict with LiteSpeed Cache
--------------------------+----------------------
 Reporter:  tatuatu       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------

Comment (by tatuatu):

 as I said above, no order works anymore, it is a sales site where you
 could not place orders, because the interface was defective, lite speed
 cache is not the problem, because it works perfectly with version 5.9 .1
 if I update to 5.9.2 the problem described above appears and looks like in
 the attached pictures.

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

From noreply at wordpress.org  Sat Mar 12 19:25:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 19:25:12 -0000
Subject: [wp-trac] [WordPress Trac] #55382: WordPress 5.9.2 bug,
 conflict with LiteSpeed Cache
In-Reply-To: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
References: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
Message-ID: <066.aeb8f35f5e9731c049352a8d97edea82@wordpress.org>

#55382: WordPress 5.9.2 bug,conflict with LiteSpeed Cache
--------------------------+-----------------------
 Reporter:  tatuatu       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Changes (by tatuatu):

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


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

From noreply at wordpress.org  Sat Mar 12 19:39:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 19:39:11 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.e13849964e0b052b228c7c60ded4ebdf@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------------+---------------------
 Reporter:  kajalgohel                     |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  normal                         |   Milestone:  6.0
Component:  Bundled Theme                  |     Version:  3.2
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch needs-testing close  |     Focuses:  css
-------------------------------------------+---------------------
Changes (by audrasjb):

 * keywords:  has-patch needs-testing => has-patch needs-testing close


Comment:

 I feel a bit hesitant about this change. Does it solves any known issue?
 Does it helps passing CSS validation? Does it brings more "quality" to the
 theme?

 If we can't find any relevant answer to these question, I'd suggest to
 close the ticket as `wontfix`.

 I feel a bit concerned about breaking things for people who override the
 default behavior of this theme using a child theme, without solving any
 identified issue.

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

From noreply at wordpress.org  Sat Mar 12 19:43:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 19:43:18 -0000
Subject: [wp-trac] [WordPress Trac] #55167: Twenty Sixteen: Fix button
 styles outside of entry-content
In-Reply-To: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
References: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
Message-ID: <067.f7633eebcb5575f1a0ca0d939f23df2e@wordpress.org>

#55167: Twenty Sixteen: Fix button styles outside of entry-content
---------------------------+------------------------
 Reporter:  mikachan       |       Owner:  audrasjb
     Type:  defect (bug)   |      Status:  reviewing
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:  5.0
 Severity:  minor          |  Resolution:
 Keywords:  has-patch      |     Focuses:  css
---------------------------+------------------------
Changes (by audrasjb):

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


Comment:

 Self assigning for review.

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

From noreply at wordpress.org  Sat Mar 12 20:02:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 20:02:35 -0000
Subject: [wp-trac] [WordPress Trac] #55382: WordPress 5.9.2 bug,
 conflict with LiteSpeed Cache
In-Reply-To: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
References: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
Message-ID: <066.43e505430c79026b6fa368b203ccdfe2@wordpress.org>

#55382: WordPress 5.9.2 bug,conflict with LiteSpeed Cache
--------------------------+-----------------------
 Reporter:  tatuatu       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Changes (by tatuatu):

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


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

From noreply at wordpress.org  Sat Mar 12 20:41:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 20:41:32 -0000
Subject: [wp-trac] [WordPress Trac] #55105: Introduce a polyfill for
 `array_is_list()`.
In-Reply-To: <051.b8ae2c08f5ad2c8bbe71037bcf23450d@wordpress.org>
References: <051.b8ae2c08f5ad2c8bbe71037bcf23450d@wordpress.org>
Message-ID: <066.5d92a1646bf060abaaa73fa8576d6e47@wordpress.org>

#55105: Introduce a polyfill for `array_is_list()`.
---------------------------------------------------+---------------------
 Reporter:  costdev                                |       Owner:  (none)
     Type:  feature request                        |      Status:  new
 Priority:  normal                                 |   Milestone:  6.0
Component:  General                                |     Version:  5.9
 Severity:  minor                                  |  Resolution:
 Keywords:  has-patch has-unit-tests dev-feedback  |     Focuses:
---------------------------------------------------+---------------------

Comment (by costdev):

 @jrf I tried to find a use case prior to writing the polyfill. I couldn't
 find one. Examples online seem to literally just reiterate what the
 function does, without providing use cases, and vaguely referring to "PHP
 security vulnerabilities caused by arrays that are not in order", without
 mentioning `array_values()` once.

 **''Why did I write it then?''**

 I'd just reviewed and written tests for some of the polyfills introduced
 in 5.9, and I wasn't quite done with my polyfilling-spree. It's there,
 with unit tests, if use cases are found.

 As we're still early enough in the release cycle, I'll leave this open in
 case someone sees value in introducing this polyfill to Core. If there are
 none provided as we approach feature freeze, I'll go ahead and close as
 `maybelater`, or punt to 6.1 if use cases are actively being discussed.

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

From noreply at wordpress.org  Sat Mar 12 21:45:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 21:45:30 -0000
Subject: [wp-trac] [WordPress Trac] #55167: Twenty Sixteen: Fix button
 styles outside of entry-content
In-Reply-To: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
References: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
Message-ID: <067.55c8e0659ac600ac9271eeb882162075@wordpress.org>

#55167: Twenty Sixteen: Fix button styles outside of entry-content
---------------------------+------------------------
 Reporter:  mikachan       |       Owner:  audrasjb
     Type:  defect (bug)   |      Status:  reviewing
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:  5.0
 Severity:  minor          |  Resolution:
 Keywords:  has-patch      |     Focuses:  css
---------------------------+------------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-12 à 22.40.47.png" added.

 Reproducing the issue by the steps described above by @costdev

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

From noreply at wordpress.org  Sat Mar 12 21:46:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 21:46:00 -0000
Subject: [wp-trac] [WordPress Trac] #55167: Twenty Sixteen: Fix button
 styles outside of entry-content
In-Reply-To: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
References: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
Message-ID: <067.70fc73dfb4123967751c47a02fc6a1f6@wordpress.org>

#55167: Twenty Sixteen: Fix button styles outside of entry-content
---------------------------+------------------------
 Reporter:  mikachan       |       Owner:  audrasjb
     Type:  defect (bug)   |      Status:  reviewing
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:  5.0
 Severity:  minor          |  Resolution:
 Keywords:  has-patch      |     Focuses:  css
---------------------------+------------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-12 à 22.41.46.png" added.

 Before applying the patch: the button styles are not applied :(

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55167>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 12 21:46:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 21:46:31 -0000
Subject: [wp-trac] [WordPress Trac] #55167: Twenty Sixteen: Fix button
 styles outside of entry-content
In-Reply-To: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
References: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
Message-ID: <067.002b2288786cf73691072cf0a07bba86@wordpress.org>

#55167: Twenty Sixteen: Fix button styles outside of entry-content
---------------------------+------------------------
 Reporter:  mikachan       |       Owner:  audrasjb
     Type:  defect (bug)   |      Status:  reviewing
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:  5.0
 Severity:  minor          |  Resolution:
 Keywords:  has-patch      |     Focuses:  css
---------------------------+------------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-12 à 22.44.51.png" added.

 After applying the patch: WORKS FINE \o/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55167>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 12 21:47:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 21:47:34 -0000
Subject: [wp-trac] [WordPress Trac] #55167: Twenty Sixteen: Fix button
 styles outside of entry-content
In-Reply-To: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
References: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
Message-ID: <067.eac186c7b251c880f97fedbc98ff9a92@wordpress.org>

#55167: Twenty Sixteen: Fix button styles outside of entry-content
----------------------------------------------+-----------------------
 Reporter:  mikachan                          |       Owner:  audrasjb
     Type:  defect (bug)                      |      Status:  accepted
 Priority:  normal                            |   Milestone:  6.0
Component:  Bundled Theme                     |     Version:  5.0
 Severity:  minor                             |  Resolution:
 Keywords:  has-patch has-screenshots commit  |     Focuses:  css
----------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch has-screenshots commit
 * status:  reviewing => accepted


Comment:

 The patch looks good to me. Let's ship this change 🚀

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55167#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 12 21:54:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 21:54:05 -0000
Subject: [wp-trac] [WordPress Trac] #55167: Twenty Sixteen: Fix button
 styles outside of entry-content
In-Reply-To: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
References: <052.c60f5b35e13b75e9ad58570c7ddc4daa@wordpress.org>
Message-ID: <067.da28b79a494a6c29acba2051ef2951b9@wordpress.org>

#55167: Twenty Sixteen: Fix button styles outside of entry-content
----------------------------------------------+-----------------------
 Reporter:  mikachan                          |       Owner:  audrasjb
     Type:  defect (bug)                      |      Status:  closed
 Priority:  normal                            |   Milestone:  6.0
Component:  Bundled Theme                     |     Version:  5.0
 Severity:  minor                             |  Resolution:  fixed
 Keywords:  has-patch has-screenshots commit  |     Focuses:  css
----------------------------------------------+-----------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52926" 52926]:
 {{{
 #!CommitTicketReference repository="" revision="52926"
 Twenty Sixteen: Remove `.entry-content` selector from button styles.

 This change applies the default button styles to all button blocks in
 Twenty Sixteen, instead of only targeting those in `entry-content`. This
 means that any buttons added outside of `.entry-content`, such as in a
 widget area, will be styled the same as any other button blocks. This
 change also makes the theme custom colors work outside of `.entry-
 content`.

 Follow-up to [44306].

 Props mikachan, costdev, audrasjb.
 Fixes #55167.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55167#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 12 22:27:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 22:27:31 -0000
Subject: [wp-trac] [WordPress Trac] #48697: Twenty Nineteen - Linked
 Image Block Images Display Issue
In-Reply-To: <051.82cdd0e98e4c4b6ec0d7fa28b68f427c@wordpress.org>
References: <051.82cdd0e98e4c4b6ec0d7fa28b68f427c@wordpress.org>
Message-ID: <066.c7021885978b7fd8005612d85d592f1a@wordpress.org>

#48697: Twenty Nineteen - Linked Image Block Images Display Issue
---------------------------+---------------------
 Reporter:  JarretC        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  css
---------------------------+---------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-12 à 23.19.07.png" added.

 Before patch: image with and without link weren't using the same size

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48697>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 12 22:28:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 22:28:46 -0000
Subject: [wp-trac] [WordPress Trac] #48697: Twenty Nineteen - Linked
 Image Block Images Display Issue
In-Reply-To: <051.82cdd0e98e4c4b6ec0d7fa28b68f427c@wordpress.org>
References: <051.82cdd0e98e4c4b6ec0d7fa28b68f427c@wordpress.org>
Message-ID: <066.e7050ea16c6dfb7a3fb43b6076185ca3@wordpress.org>

#48697: Twenty Nineteen - Linked Image Block Images Display Issue
---------------------------+---------------------
 Reporter:  JarretC        |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  css
---------------------------+---------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-12 à 23.26.31.png" added.

 After patch: same size applies to both images with or without link

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48697>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 12 22:30:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 22:30:22 -0000
Subject: [wp-trac] [WordPress Trac] #48697: Twenty Nineteen - Linked
 Image Block Images Display Issue
In-Reply-To: <051.82cdd0e98e4c4b6ec0d7fa28b68f427c@wordpress.org>
References: <051.82cdd0e98e4c4b6ec0d7fa28b68f427c@wordpress.org>
Message-ID: <066.0550c4336edb45781dfff07052490eba@wordpress.org>

#48697: Twenty Nineteen - Linked Image Block Images Display Issue
----------------------------------------------+-----------------------
 Reporter:  JarretC                           |       Owner:  audrasjb
     Type:  defect (bug)                      |      Status:  assigned
 Priority:  normal                            |   Milestone:  6.0
Component:  Bundled Theme                     |     Version:
 Severity:  normal                            |  Resolution:
 Keywords:  has-patch has-screenshots commit  |     Focuses:  css
----------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch has-screenshots commit
 * owner:  (none) => audrasjb
 * status:  new => assigned


Comment:

 Self assigning for commit consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48697#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 12 22:52:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 12 Mar 2022 22:52:08 -0000
Subject: [wp-trac] [WordPress Trac] #48697: Twenty Nineteen - Linked
 Image Block Images Display Issue
In-Reply-To: <051.82cdd0e98e4c4b6ec0d7fa28b68f427c@wordpress.org>
References: <051.82cdd0e98e4c4b6ec0d7fa28b68f427c@wordpress.org>
Message-ID: <066.07bf46fd401cc4937d433c21af683430@wordpress.org>

#48697: Twenty Nineteen - Linked Image Block Images Display Issue
----------------------------------------------+-----------------------
 Reporter:  JarretC                           |       Owner:  audrasjb
     Type:  defect (bug)                      |      Status:  closed
 Priority:  normal                            |   Milestone:  6.0
Component:  Bundled Theme                     |     Version:
 Severity:  normal                            |  Resolution:  fixed
 Keywords:  has-patch has-screenshots commit  |     Focuses:  css
----------------------------------------------+-----------------------
Changes (by audrasjb):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52927" 52927]:
 {{{
 #!CommitTicketReference repository="" revision="52927"
 Twenty Nineteen: Display Image block at the same size whether the image is
 linked or not.

 This change makes sure the `max-width` value is assigned for linked
 images.

 Props JarretC, sabernhardt.
 Fixes #48697.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48697#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 00:25:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 00:25:36 -0000
Subject: [wp-trac] [WordPress Trac] #55383: hello i cant put mi site in
 spanish is imposible
Message-ID: <050.ccf2c8157b5b42252140f58aaaf3a0f1@wordpress.org>

#55383: hello i cant put mi site in spanish is imposible
--------------------------+-----------------------------
 Reporter:  kchote        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 i put my wordpress in spanish and the wordpress return to english

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55383>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 00:58:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 00:58:08 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.ed7b9c4cc4615175e47a3f1b4b9df3a0@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------------+---------------------
 Reporter:  kajalgohel                     |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  normal                         |   Milestone:  6.0
Component:  Bundled Theme                  |     Version:  3.2
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch needs-testing close  |     Focuses:  css
-------------------------------------------+---------------------
Changes (by sabernhardt):

 * Attachment "55338.5.patch" added.

 removing float, with smaller width and vertical alignment

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55338>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 00:59:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 00:59:23 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.87c6ea956169021db92c02f404733c94@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------------+---------------------
 Reporter:  kajalgohel                     |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  normal                         |   Milestone:  6.0
Component:  Bundled Theme                  |     Version:  3.2
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch needs-testing close  |     Focuses:  css
-------------------------------------------+---------------------
Changes (by sabernhardt):

 * Attachment "floated-element-5.9.png" added.

 text in floated element (currently) can touch the next element

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55338>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 01:00:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 01:00:08 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.b3d8b31c4821ee0d3303c5b81476388f@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------------+---------------------
 Reporter:  kajalgohel                     |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  normal                         |   Milestone:  6.0
Component:  Bundled Theme                  |     Version:  3.2
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch needs-testing close  |     Focuses:  css
-------------------------------------------+---------------------

Comment (by sabernhardt):

 I lean toward closing, or at least I recommend against committing my
 earlier patch.

 The [https://jigsaw.w3.org/css-
 validator/validator?uri=https%3A%2F%2Fs0.wp.com%2Fwp-
 content%2Fthemes%2Fpub%2Ftwentyeleven%2Fstyle.css W3C CSS Validator] only
 labels the negative padding (#46771) and the `device-width` entries as
 errors, and the float/display combination does not appear in the warnings
 list either.

 Both [https://www.cssportal.com/css-validator/ CSS Portal] and
 [https://codebeautify.org/cssvalidate Code Beautify] alert about the
 floating under the message "Require properties appropriate for display"
 (one identifies it as an error, the other calls it a warning).

 I took another look at 55338.2.patch. As long as the vertical alignment is
 set, removing the float and reducing the width might be worth considering.
 Without floating, the two `inline-block` elements can have a slight space
 between them that is not always there on smaller screens (depending on
 content).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55338#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 03:59:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 03:59:37 -0000
Subject: [wp-trac] [WordPress Trac] #55383: hello i cant put mi site in
 spanish is imposible
In-Reply-To: <050.ccf2c8157b5b42252140f58aaaf3a0f1@wordpress.org>
References: <050.ccf2c8157b5b42252140f58aaaf3a0f1@wordpress.org>
Message-ID: <065.1bc0e1a0ce952b88d607e778068a85d3@wordpress.org>

#55383: hello i cant put mi site in spanish is imposible
--------------------------+----------------------
 Reporter:  kchote        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.9.2
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by sabernhardt):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Hi and welcome to Trac!

 Sorry to hear you are having trouble with your site. Unfortunately, Trac
 is not the right place to get help with this. Please visit the support
 forums and/or open a topic there.

 [https://es.wordpress.org/support Foros de soporte, en español]
 [https://wordpress.org/support/ support forums, in English]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55383#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 04:17:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 04:17:40 -0000
Subject: [wp-trac] [WordPress Trac] #54987: Check if 'user_nicename' is
 not too long after the 'pre_user_nicename' filter
In-Reply-To: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
References: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
Message-ID: <073.188eeab3b7f1234180c9efa64446003f@wordpress.org>

#54987: Check if 'user_nicename' is not too long after the 'pre_user_nicename'
filter
--------------------------------------+----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  davidbaumwald
     Type:  defect (bug)              |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Users                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+----------------------------
Changes (by SergeyBiryukov):

 * Attachment "54987.2.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54987>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 04:17:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 04:17:55 -0000
Subject: [wp-trac] [WordPress Trac] #54987: Check if 'user_nicename' is
 not too long after the 'pre_user_nicename' filter
In-Reply-To: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
References: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
Message-ID: <073.adfaacb40eae0e5bd9e0e5d7473ed9d2@wordpress.org>

#54987: Check if 'user_nicename' is not too long after the 'pre_user_nicename'
filter
--------------------------------------+----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  davidbaumwald
     Type:  defect (bug)              |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Users                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+----------------------------

Comment (by SergeyBiryukov):

 Thanks for the patches! It looks like most of them have changes that are a
 bit out of scope for this ticket:

 * [attachment:54987.patch] introduces a duplicate check instead of moving
 the existing one.
 * [attachment:54987.2.patch] moves the existing check, but no longer
 throws a WP_Error if the nicename is too long.
 * [attachment:54987.diff] has some formatting changes and renames a
 variable, which does not seem necessary here. It also adds validation for
 `$user_url`, but it was already added in [52650] / #44107.
 * [https://github.com/WordPress/wordpress-develop/pull/2244 PR #2244]
 introduces a new check that `user_nicename` cannot be empty. I think this
 would be better discussed in a separate ticket.

 For this ticket, I was thinking of just moving the existing check after
 the filter, like in [attachment:"54987.2.diff"].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54987#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 09:16:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 09:16:29 -0000
Subject: [wp-trac] [WordPress Trac] #49762: Twenty Thirteen: Add
 gradient background options that fit the theme color scheme
In-Reply-To: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
References: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
Message-ID: <070.62e238b5509733b4d72b3f94e493e507@wordpress.org>

#49762: Twenty Thirteen: Add gradient background options that fit the theme color
scheme
---------------------------+----------------------
 Reporter:  ianbelanger    |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  ui, css
---------------------------+----------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-13 à 10.04.46.png" added.

 Before patch: no theme specific pattern available

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49762>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 09:16:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 09:16:56 -0000
Subject: [wp-trac] [WordPress Trac] #49762: Twenty Thirteen: Add
 gradient background options that fit the theme color scheme
In-Reply-To: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
References: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
Message-ID: <070.8f2f80d186d1064ecb2d1e828510ec4c@wordpress.org>

#49762: Twenty Thirteen: Add gradient background options that fit the theme color
scheme
---------------------------+----------------------
 Reporter:  ianbelanger    |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  ui, css
---------------------------+----------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-13 à 10.15.30.png" added.

 After patch: theme specific patterns are available

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49762>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 09:17:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 09:17:45 -0000
Subject: [wp-trac] [WordPress Trac] #49762: Twenty Thirteen: Add
 gradient background options that fit the theme color scheme
In-Reply-To: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
References: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
Message-ID: <070.cf4fbe2ca66e27f7e37791d558e49e45@wordpress.org>

#49762: Twenty Thirteen: Add gradient background options that fit the theme color
scheme
---------------------------+----------------------
 Reporter:  ianbelanger    |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  ui, css
---------------------------+----------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-13 à 10.15.51.png" added.

 After patch: theme specific pattern works on front-end

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49762>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 09:18:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 09:18:51 -0000
Subject: [wp-trac] [WordPress Trac] #49762: Twenty Thirteen: Add
 gradient background options that fit the theme color scheme
In-Reply-To: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
References: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
Message-ID: <070.56026efabdb84c56166609a6e82bcb52@wordpress.org>

#49762: Twenty Thirteen: Add gradient background options that fit the theme color
scheme
-------------------------------------------------+-------------------------
 Reporter:  ianbelanger                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-refresh has-         |     Focuses:  ui, css
  screenshots                                    |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch needs-refresh has-screenshots


Comment:

 The patch works fine on my side, but I think the code needs to be
 refreshed to meet WordPress Coding Standards. New PR incoming.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49762#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 09:18:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 09:18:57 -0000
Subject: [wp-trac] [WordPress Trac] #49762: Twenty Thirteen: Add
 gradient background options that fit the theme color scheme
In-Reply-To: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
References: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
Message-ID: <070.bd739edc68e2148827e0025b88840c8e@wordpress.org>

#49762: Twenty Thirteen: Add gradient background options that fit the theme color
scheme
-------------------------------------------------+-------------------------
 Reporter:  ianbelanger                          |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-refresh has-         |     Focuses:  ui, css
  screenshots                                    |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49762#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 09:39:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 09:39:50 -0000
Subject: [wp-trac] [WordPress Trac] #54855: Ui issue on edit menu page
In-Reply-To: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
References: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
Message-ID: <069.865f9d3c87d6a3502aa6c43bef8bdf22@wordpress.org>

#54855: Ui issue on edit menu page
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Menus                    |     Version:  5.8.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots good-    |     Focuses:  ui, css,
  first-bug has-patch needs-refresh  |  administration
-------------------------------------+-------------------------------------
Changes (by audrasjb):

 * keywords:  has-screenshots good-first-bug has-patch => has-screenshots
     good-first-bug has-patch needs-refresh


Comment:

 Adding `needs-refresh` keyword as the above patch doesn't meet WordPress
 Coding Standards

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54855#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 09:40:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 09:40:00 -0000
Subject: [wp-trac] [WordPress Trac] #54855: Ui issue on edit menu page
In-Reply-To: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
References: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
Message-ID: <069.069af543b82cb1dc182ef86a678870cc@wordpress.org>

#54855: Ui issue on edit menu page
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  audrasjb
     Type:  enhancement              |      Status:  reviewing
 Priority:  normal                   |   Milestone:  6.0
Component:  Menus                    |     Version:  5.8.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots good-    |     Focuses:  ui, css,
  first-bug has-patch needs-refresh  |  administration
-------------------------------------+-------------------------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => reviewing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54855#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 09:46:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 09:46:49 -0000
Subject: [wp-trac] [WordPress Trac] #49762: Twenty Thirteen: Add
 gradient background options that fit the theme color scheme
In-Reply-To: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
References: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
Message-ID: <070.570997cda3158d2ebfcfad3fa37c69a0@wordpress.org>

#49762: Twenty Thirteen: Add gradient background options that fit the theme color
scheme
----------------------------------------------+-----------------------
 Reporter:  ianbelanger                       |       Owner:  audrasjb
     Type:  enhancement                       |      Status:  assigned
 Priority:  normal                            |   Milestone:  6.0
Component:  Bundled Theme                     |     Version:
 Severity:  normal                            |  Resolution:
 Keywords:  has-patch has-screenshots commit  |     Focuses:  ui, css
----------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch has-screenshots => has-patch has-screenshots commit


Comment:

 WPCS issues are fixed in the above PR.
 Marking for `commit`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49762#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 09:48:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 09:48:23 -0000
Subject: [wp-trac] [WordPress Trac] #49762: Twenty Thirteen: Add
 gradient background options that fit the theme color scheme
In-Reply-To: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
References: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
Message-ID: <070.ae6eb75308eb865a584eca242bf1d0d3@wordpress.org>

#49762: Twenty Thirteen: Add gradient background options that fit the theme color
scheme
----------------------------------------------+-----------------------
 Reporter:  ianbelanger                       |       Owner:  audrasjb
     Type:  enhancement                       |      Status:  closed
 Priority:  normal                            |   Milestone:  6.0
Component:  Bundled Theme                     |     Version:
 Severity:  normal                            |  Resolution:  fixed
 Keywords:  has-patch has-screenshots commit  |     Focuses:  ui, css
----------------------------------------------+-----------------------
Changes (by audrasjb):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52928" 52928]:
 {{{
 #!CommitTicketReference repository="" revision="52928"
 Twenty Thirteen: Add gradient background options using the theme color
 scheme.

 This change implements gradient background options that fit the color
 scheme used in Twenty Thirteen.

 Props ianbelanger, tomjdevisser, audrasjb.
 Fixes #49762.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49762#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 11:58:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 11:58:20 -0000
Subject: [wp-trac] [WordPress Trac] #55384: health-check : Warning Array to
 string conversion
Message-ID: <050.5be0474d26a08d459a86f27b13ece565@wordpress.org>

#55384: health-check : Warning Array to string conversion
--------------------------+-----------------------------
 Reporter:  stfa76        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Site Health   |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hi,

 When accessing Health Check page > Info tab
 These are the errors I see in Query Monitor:
 wp-content/plugins/health-check/includes/class-health-check-debug-
 data.php:1172
 wp-includes/formatting.php:1098

 See attached screenshot.

 WordPress: 5.9.2
 Web Server: Apache/2.4.25 (Debian)
 PHP: 8.0.16

 Best regard,
 Stephane.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55384>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 11:58:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 11:58:34 -0000
Subject: [wp-trac] [WordPress Trac] #55384: health-check : Warning Array
 to string conversion
In-Reply-To: <050.5be0474d26a08d459a86f27b13ece565@wordpress.org>
References: <050.5be0474d26a08d459a86f27b13ece565@wordpress.org>
Message-ID: <065.e0d632a71fc110dc717c23eda57999ca@wordpress.org>

#55384: health-check : Warning Array to string conversion
--------------------------+------------------------------
 Reporter:  stfa76        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Site Health   |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by stfa76):

 * Attachment "Site-Health-‹-DigitalCiné-—-WordPress.jpg" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55384>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 12:46:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 12:46:22 -0000
Subject: [wp-trac] [WordPress Trac] #26746: Avoid translating several
 times post type and taxonomy default labels
In-Reply-To: <050.ffb69c1467709412179c846d3531474f@wordpress.org>
References: <050.ffb69c1467709412179c846d3531474f@wordpress.org>
Message-ID: <065.d36d7034acf3a32c10f24b2c7b9d69fd@wordpress.org>

#26746: Avoid translating several times post type and taxonomy default labels
-------------------------------+-----------------------------
 Reporter:  Chouby             |       Owner:  SergeyBiryukov
     Type:  enhancement        |      Status:  reviewing
 Priority:  normal             |   Milestone:  6.0
Component:  Posts, Post Types  |     Version:  3.0
 Severity:  normal             |  Resolution:
 Keywords:  has-patch early    |     Focuses:  performance
-------------------------------+-----------------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-13 à 13.45.31.png" added.

 The current patch throws a fatal error

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/26746>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 12:46:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 12:46:45 -0000
Subject: [wp-trac] [WordPress Trac] #26746: Avoid translating several
 times post type and taxonomy default labels
In-Reply-To: <050.ffb69c1467709412179c846d3531474f@wordpress.org>
References: <050.ffb69c1467709412179c846d3531474f@wordpress.org>
Message-ID: <065.edf399dc439809fb8da453b53b981f1a@wordpress.org>

#26746: Avoid translating several times post type and taxonomy default labels
-------------------------------------------------+-------------------------
 Reporter:  Chouby                               |       Owner:
                                                 |  SergeyBiryukov
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Posts, Post Types                    |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch early needs-refresh        |     Focuses:
  needs-testing                                  |  performance
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch early => has-patch early needs-refresh needs-testing


Comment:

 The current patch throws a fatal error. Investigating…

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/26746#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 12:49:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 12:49:35 -0000
Subject: [wp-trac] [WordPress Trac] #26746: Avoid translating several
 times post type and taxonomy default labels
In-Reply-To: <050.ffb69c1467709412179c846d3531474f@wordpress.org>
References: <050.ffb69c1467709412179c846d3531474f@wordpress.org>
Message-ID: <065.cf2d0bf0a3a6dca0b85f555a83d0a7db@wordpress.org>

#26746: Avoid translating several times post type and taxonomy default labels
-------------------------------+-----------------------------
 Reporter:  Chouby             |       Owner:  SergeyBiryukov
     Type:  enhancement        |      Status:  reviewing
 Priority:  normal             |   Milestone:  6.0
Component:  Posts, Post Types  |     Version:  3.0
 Severity:  normal             |  Resolution:
 Keywords:  has-patch early    |     Focuses:  performance
-------------------------------+-----------------------------
Changes (by audrasjb):

 * keywords:  has-patch early needs-refresh needs-testing => has-patch early


Comment:

 The above bug was a merge issue on my side, locally.
 I can confirm the patch works fine on my side (it doesn't change anything,
 except it improves translation loading performance).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/26746#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 13:12:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 13:12:44 -0000
Subject: [wp-trac] [WordPress Trac] #55385: Error in Search
Message-ID: <061.caa3b2cb4d146df3b0520cddfdc2b8c5@wordpress.org>

#55385: Error in Search
-------------------------------+-----------------------------
 Reporter:  himanshushokhanda  |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Posts, Post Types  |    Version:
 Severity:  normal             |   Keywords:
  Focuses:                     |
-------------------------------+-----------------------------
 Hi Support,

 When we are searching any keyword which start from .profile it send the
 backend normal post and page search to the frontend not found. Instead it
 should stay on same page and show not found.

 For example please search this www.profile.com and it will send you to
 frontend.

 Can you please advise why it is happening ?

 Regards,
 Himanshu

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55385>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 13:49:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 13:49:00 -0000
Subject: [wp-trac] [WordPress Trac] #39733: List item separator should
 be a WP_Locale property
In-Reply-To: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
References: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
Message-ID: <073.117f4d4e47d9fa582941762a3f8f9ff6@wordpress.org>

#39733: List item separator should be a WP_Locale property
--------------------------------------+---------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  I18N                      |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+---------------------

Comment (by audrasjb):

 The above PR refreshes the previous patch against trunk and updates @since
 mentions. It also add again a removed translator comment.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39733#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 13:58:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 13:58:44 -0000
Subject: [wp-trac] [WordPress Trac] #55386: 5.9.2 broke theme editing
Message-ID: <055.52311849f755c94ae7fccc15ebf95908@wordpress.org>

#55386: 5.9.2 broke theme editing
--------------------------+-----------------------------
 Reporter:  jerrydurand   |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.2
 Severity:  major         |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 If I try to edit the site I receive this error

 TypeError: Failed to fetch
     at https://pyramidhope.ru/The_Workshop/wp-includes/js/dist/edit-
 site.min.js?ver=3884aac289e14bae7b23654cf1c8c474:2:121033
     at async Gr (https://pyramidhope.ru/The_Workshop/wp-includes/js/dist
 /edit-site.min.js?ver=3884aac289e14bae7b23654cf1c8c474:2:120779)
     at async Wr (https://pyramidhope.ru/The_Workshop/wp-includes/js/dist
 /edit-site.min.js?ver=3884aac289e14bae7b23654cf1c8c474:2:121927)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55386>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 14:12:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 14:12:10 -0000
Subject: [wp-trac] [WordPress Trac] #55384: health-check : Warning Array
 to string conversion
In-Reply-To: <050.5be0474d26a08d459a86f27b13ece565@wordpress.org>
References: <050.5be0474d26a08d459a86f27b13ece565@wordpress.org>
Message-ID: <065.9a558ad5df460f34bb438a839a22e103@wordpress.org>

#55384: health-check : Warning Array to string conversion
-------------------------------+------------------------------
 Reporter:  stfa76             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Site Health        |     Version:  5.9.2
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by audrasjb):

 * keywords:   => reporter-feedback


Comment:

 Hello @stfa76, and thank you for opening this ticket,

 It looks like the issue doesn't comes from WordPress Core but from the
 Site Health feature plugin (https://wordpress.org/plugins/health-check/).

 Could you please verify if it still occurs on the site health screen once
 this feature plugin is deactivated? Thank you :)

 (also, I'm pinging @Clorith for information 👆)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55384#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 14:16:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 14:16:04 -0000
Subject: [wp-trac] [WordPress Trac] #55382: WordPress 5.9.2 bug,
 conflict with LiteSpeed Cache
In-Reply-To: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
References: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
Message-ID: <066.eb93166061c3242f6fb8a484967ff8f5@wordpress.org>

#55382: WordPress 5.9.2 bug,conflict with LiteSpeed Cache
--------------------------+-----------------------
 Reporter:  tatuatu       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+-----------------------
Changes (by audrasjb):

 * keywords:   => close


Comment:

 What happens if you deactivate the plugin? Does your website works?
 In that case, this is probably an issue with this plugin. Please contact
 the plugin author via their support forums.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55382#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 14:43:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 14:43:45 -0000
Subject: [wp-trac] [WordPress Trac] #55384: health-check : Warning Array
 to string conversion
In-Reply-To: <050.5be0474d26a08d459a86f27b13ece565@wordpress.org>
References: <050.5be0474d26a08d459a86f27b13ece565@wordpress.org>
Message-ID: <065.17dab5325f7f01da95fe2f0b54d7a772@wordpress.org>

#55384: health-check : Warning Array to string conversion
-------------------------------+------------------------------
 Reporter:  stfa76             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Site Health        |     Version:  5.9.2
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by stfa76):

 Hello @audrasjb

 I should have seen the complete path to the plugin, sorry about that!
 Indeed, you are right, deactivating Health Check plugin removes the
 warnings.

 Regards,
 Stephane.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55384#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 15:02:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 15:02:18 -0000
Subject: [wp-trac] [WordPress Trac] #55384: health-check : Warning Array
 to string conversion
In-Reply-To: <050.5be0474d26a08d459a86f27b13ece565@wordpress.org>
References: <050.5be0474d26a08d459a86f27b13ece565@wordpress.org>
Message-ID: <065.726b5cebcd1d9805c52c136d53b61c07@wordpress.org>

#55384: health-check : Warning Array to string conversion
--------------------------+----------------------
 Reporter:  stfa76        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Site Health   |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by audrasjb):

 * keywords:  reporter-feedback =>
 * status:  new => closed
 * version:  5.9.2 =>
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Cool 👍
 Closing as invalid, thank you for checking! :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55384#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 15:15:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 15:15:56 -0000
Subject: [wp-trac] [WordPress Trac] #39733: List item separator should
 be a WP_Locale property
In-Reply-To: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
References: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
Message-ID: <073.ecde283128a63e827d8a82d5b82fdd37@wordpress.org>

#39733: List item separator should be a WP_Locale property
--------------------------------------+-----------------------
 Reporter:  SergeyBiryukov            |       Owner:  audrasjb
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:  6.0
Component:  I18N                      |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+-----------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => accepted


Comment:

 The patch works fine on my side using default themes or navigating through
 admin screens.
 Self assigning for `commit` consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39733#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 17:22:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 17:22:56 -0000
Subject: [wp-trac] [WordPress Trac] #55382: WordPress 5.9.2 bug,
 conflict with LiteSpeed Cache
In-Reply-To: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
References: <051.252fe86caa5a22f9626cc26255a8a9bd@wordpress.org>
Message-ID: <066.6b3d1e6b6157450059ec98b968db7f1c@wordpress.org>

#55382: WordPress 5.9.2 bug,conflict with LiteSpeed Cache
--------------------------+----------------------
 Reporter:  tatuatu       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:  close         |     Focuses:
--------------------------+----------------------

Comment (by tatuatu):

 yes, if I disable the plugin it works, at the moment I stay at version
 5.9.1 until a new update appears, I will try to get in touch with those
 from lite speed test, good day.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55382#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 17:27:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 17:27:23 -0000
Subject: [wp-trac] =?utf-8?b?W1dvcmRQcmVzcyBUcmFjXSAjNTUzODc6IOCmleCmvg==?=
 =?utf-8?b?4Kac4KeAIOCmqOCmnOCmsOCngeCmsuCnh+CmsCDgpqrgp4HgpqTgp43gprA=?=
 =?utf-8?b?4Kas4Kan4KeCIOCmieCmruCmviDgppXgpr7gppzgp4AgIOCmrOCmv+Cmpg==?=
 =?utf-8?b?4KeN4Kaw4KeL4Ka54KeAIOCmleCmrOCmvyDgppXgpr7gppzgp4Ag4Kao4Kac?=
 =?utf-8?b?4Kaw4KeB4KayIOCmh+CmuOCmsuCmvuCmruCmleCnhyDgprjgp4fgpqzgpr8=?=
 =?utf-8?b?4KaV4Ka+4Kaw?=
Message-ID: <055.8c83f661f6f99ce5b66bc0e2a056cbf1@wordpress.org>

#55387: কাজী নজরুলের পুত্রবধূ উমা কাজী  বিদ্রোহী কবি কাজী নজরুল ইসলামকে সেবিকার
--------------------------+-----------------------------
 Reporter:  padmameghna   |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 [কাজী নজরুলের
 পুত্রবধূ উমা কাজী]

 বিদ্রোহী কবি [কাজী নজরুল ইসলামকে] সেবিকার যত্নে, মায়ের স্নেহে আগলে
 রেখেছিলেন যিনি, তিনি উমা কাজী। এই ব্রাহ্মণ-কন্যাটি ছিলেন কবির পুত্র কাজী
 সব্যসাচীর স্ত্রী, বিদ্রোহী কবি নজরুলের পুত্রবধূ।
 “যেখানেতে দেখি যাহা;
 মা-এর মতন আহা।
 একটি কথায় এত সুধা মেশা নাই,
 মায়ের মতন এত
 আদর সোহাগ সে তো
 আর কোনোখানে কেহ পাইবে, ভাই !”
 কাজী নজরুল ইসলাম নিজের "মা"বাদেও আর একজন নারীর মধ্যে নিজের মাকে খোঁজে
 পেয়েছিলেন ! যে নারী সন্তানের মতো নির্বাক ও প্রায় স্মৃতিশক্তিহীন কবি
 নজরুলকে মায়ের ভালোবাসায় আবদ্ধ রেখেছিলেন। আর স্নেহ-মায়া, ভালোবাসায় দিয়ে, যে
 সমস্ত রকম ভেদাভেদ দূর করা যায়, তার উদাহরণ উমা কাজী এই মানুষটি!
 কাজী নজরুল-এর বড় ছেলে কাজী সব্যসাচীর স্ত্রী, অর্থাৎ নজরুলের পুত্রবধূ।
 আসলে, তিনি ছিলেন উমা মুখোপাধ্যায়। হিন্দু ও ব্রাহ্মণ পরিবারের কন্যা হয়েও
 মুসলিম পরিবারের পুত্রবধূ হয়েছিলেন ! সেই অনেক বছর আগে। উমার বাবা ছিলেন
 শ্যামাপ্রসাদ মুখোপাধ্যায় এবং মা বাদলা মুখোপাধ্যায়। তার জন্ম বর্ধমানের
 কাটোয়া অঞ্চলে।

 লেখাপড়া শেষ করে কলকাতার ‘লেডি ডাফরিন মেডিকেল হাসপাতাল’ থেকে ট্রেনিং নিয়ে
 নার্স হয়েছিলেন উমা মুখোপাধ্যায়। থাকতেন সেখানকার নার্সিং হোস্টেলেই। ছোটকাল,
 থেকেই সেবিকা হতে চাইতেন তিনি। সেখানকারই এক হেড নার্স ঊষা দিদি, উমাকে এক
 নতুন পথের দিশা দেখান। উমাকে তিনি নিয়ে যান অসুস্থ বিদ্রোহী কবি কাজী নজরুল
 ইসলামের বাড়ীতে। কবির সেবা করার জন্য প্রয়োজন ছিল এক নার্সের। নির্বাক কবি
 তখন কলকাতার মানিকতলায় থাকতেন। নানা অসুস্থতায় জর্জরিত হলেও, দুই বাংলাতেই
 সমান্তরারালে তখন কবিকে নিয়ে কোনো অংশে উন্মাদনা কম নয়!
 এমনই সময়ে কবির মাথার কাছে গিয়ে বসলেন তরুণী উমা। নজরুলের স্ত্রী প্রমীলা
 দেবী বলেছিলেন, “তুমি কি পারবে 'মা' কবির সেবা করতে ? ঐ যে দ্যাখো, উঁনি
 খবরের কাগজ ছিঁড়ছেন। উঁনি এখন শিশুর মতো।” এ প্রশ্নের উত্তরে উমা বলেছিলেন,
 “আমরা তো কলকাতার হাসপাতালে শিশু বিভাগেই ডিউটি করেছি। কবি যদি শিশুর মতো হন,
 তবে নিশ্চয়ই পারবো।”
 সেবা ও স্নেহের পথ পরিক্রমায় উমাই হয়ে উঠলেন কবি নজরুলের প্রিয় মানুষ। তাঁকে
 স্নান করানো, খাওয়ানো, দেখ-ভাল করা, গল্প শোনানো। উমার হাতের স্পর্শ যেন কবির
 কাছে মায়ের আঁচলের মতো হয়ে ওঠে। কিন্তু এরই মধ্যে উমার সেবার মনোবৃত্তি দেখে,
 মিষ্টি ব্যবহার দেখে কবির বড় ছেলে কাজী সব্যসাচী,উমার প্রেমে পড়ে গেলেন ।
 উমাও সব্যসাচীকে মন-প্রাণ দিয়ে ভালোবেসে ফেললেন।
 বিয়ে হল ব্রাহ্মণের মেয়ের সঙ্গে মুসলিম ছেলের। সৃষ্টিকর্তার উপর বিশ্বাস
 রেখে, উমা মুসলিম পরিবারকে আপন করে নিলেন। মুসলিম ধর্মান্তরে উমা মুখোপাধ্যায়
 হয়ে গেলেন, উমা কাজী। কবি ও কবিপত্নী প্রমীলা নজরুলও এমন এক মেয়েকে ঘরের বৌমা
 হিসেবে পেয়ে খুশি হলেন। উমা মুসলিম পদবী গ্রহণ করলেও, তাঁর নামে থেকে গেল
 দুর্গা'র চিহ্ন।
 শাশুড়ি প্রমীলাদেবী উমা বৌমাকে নিজের মেয়ের মতোই ভালোবাসতেন। এদিকে কবি নিজেও
 বৌমা অন্তঃপ্রাণ। বৌমা চন্দন সাবান দিয়ে গোসল করিয়ে না দিলে স্নান করবেন না
 নজরুল, দাঁড়ি বৌমাই কেটে দেবে, খাইয়ে দেবে বৌমা। আদরের বৌমার কাছে শিশুর মতো
 আবদার বায়না করতেন কবি। এমনকি পরিধেয় জামাকাপড়ে নীল বোতলের আতর-সুগন্ধিও
 বৌমাকেই লাগিয়ে দিতে হবে।
 উমা একদিকে নিজের নতুন সংসার সামলাচ্ছেন আর অন্যদিকে কবিকেও সামলাচ্ছেন। ধীরে
 ধীরে এল সব্যসাচী-উমার ঘরে তিন সন্তান,
 - মিষ্টি কাজী,
 - খিলখিল কাজী এবং
 - বাবুল কাজী। তিন নাতি-নাতনি দাদা নজরুলের কাছেই থাকত বেশি সময়। কবিও তো
 শিশুর মতোই। সন্তানদের সঙ্গেই কবিকেও আসন পেতে বসিয়ে ভাত খাইয়ে দিতেন উমা
 কাজী।

 পরবর্তীতে, বিদ্রোহী কবি কাজী নজরুল ইসলামকে সুস্থ করতে দুটি মেডিক্যাল বোর্ড
 গঠন করা হয়, যে বোর্ডের সদস্যদের কবির সমস্যাগুলি বুঝিয়ে দিতে যেতেন, উমা
 নিজেই । কিভাবে কবির স্মৃতিশক্তি ফেরানো যাবে, কথা বলানো যাবে, এ সব ভাল করে
 শুনে সেবার ধরণও বুঝে নিতেন উমা। পাশাপাশি স্বামীর খেয়াল রাখা থেকে
 ছেলেমেয়েদের পড়াশোনা, সবটাই দেখতেন উমা কাজী।
 এরি মধ্যে কবিপত্নী প্রমীলা দেবী অসুস্থ হয়ে পড়লেন। শাশুড়ির সব দেখভালের
 দায়িত্বও নিলেন উমা কাজীই। কবির আগেই চলে গেলেন কবিপত্নী। দীর্ঘ ৩৮ বছরের
 সংসার জীবনের পর, ১৯৬২ সালের ৩০শে জুন মাত্র ৫২ বছর বয়সে শেষ নিশ্বাস ত্যাগ
 করেন প্রমীলা কাজী। তাঁকে কলকাতা থেকে চুরুলিয়া নিয়ে যাওয়া হয়। সেখানে
 হাজী পাহালোয়ানের দরগার পাশে কবিপত্নীকে সমাহিত করা হয়।
 ১৯৭২ সালে বঙ্গবন্ধু শেখ মুজিবুর রহমান-এর উদ্যোগে স্বপরিবারে কবিকে
 বাংলাদেশে আনা হয়। ধানমন্ডির ২৮ নম্বর রোডে (বর্তমান নজরুল ইনস্টিটিউট
 সংলগ্ন) কবি ভবনে রাষ্ট্রীয় মর্যাদায় তাঁরা বসবাস শুরু করেন। কাজী সব্যসাচী
 কর্মসূত্রে কলকাতায় থেকে গেলেও উমা কাজী কবিকে দেখার জন্য ছেলেমেয়েদের নিয়ে
 ঢাকায় চলে আসেন। ধানমণ্ডির বাড়িতে নজরুল নাতি-নাতনি নিয়ে খেলা করতেন, বাগানে
 ঘুরে বেড়াতেন।
 কবির জন্মদিন পালন হতো বেশ বড় করে। অতিথিরা আসতেন, কবিকে সবাই মালা পরাতেন ।
 কবি সেইসব মালা পরে খিলখিল করে হাসতেন। হারমোনিয়াম দেখিয়ে সবাইকে বলতেন গান
 করতে। নাতি-নাতনিরাও নজরুল সঙ্গীত গাইতেন। নির্বাক কবিই কখনও হেসে উঠতেন আবার
 কখনও নির্বাক হয়ে অঝোর ধারায় কেঁদে যেতেন। একটার পর একটা নিজের সৃষ্টি শুনে।
 সব যন্ত্রণা যেন গানে গানে ঝরে পড়ত কবির চোখের জলে।
 জীবনের শেষ দিকে বিছানাতে স্থায়ী ঠিকানা হলো কবির। পরিষ্কার-পরিচ্ছন্ন করতেন
 উমা। তিনি যে সেবিকা থেকে ততদিনে তিনি যে কবির 'মা' হয়ে গিয়েছিলেন ! তাই, তো
 এত কিছুর মধ্যেও এতটুকু ফাঁক-ফোঁকর পড়েনি! ছেলে-মেয়েদেরকে বড় করার বা
 শাশুড়ির অবর্তমানে সমগ্র সংসার সামলানোর বা কাজী সব্যসাচীর যোগ্য সহধর্মিণী
 হয়ে উঠার।
 ২৯ আগস্ট ১৯৭৬ ইং বিদ্রোহী কবি কাজী নজরুল প্রয়াত হন। চির বিদায়ের শেষ সজ্জায়
 কবিকে সাজিয়েও দিয়েছেন উমা কাজী। তিন বছর পরে ১৯৭৯ সালের ২ মার্চ কলকাতায়
 মারা যান আবৃত্তিকার স্বামী কাজী সব্যসাচী। অকালেই চলে যান অসুখে। ফলে আরও
 কঠিন দায়িত্ব এসে পড়ে উমার কাঁধের উপর। তখন ম্লান হয়ে আসছে কাজী পরিবারের
 যশ-খ্যাতি। একা হাতে বিখ্যাত কবি পরিবারকে কঠিন
 ----

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55387>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 17:27:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 17:27:32 -0000
Subject: [wp-trac] [WordPress Trac] #54987: Check if 'user_nicename' is
 not too long after the 'pre_user_nicename' filter
In-Reply-To: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
References: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
Message-ID: <073.700d7c1075717395a605f6cfd224c15f@wordpress.org>

#54987: Check if 'user_nicename' is not too long after the 'pre_user_nicename'
filter
--------------------------------------+----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  davidbaumwald
     Type:  defect (bug)              |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Users                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+----------------------------
Changes (by csesumonpro):

 * Attachment "54987.3.diff" added.

 Patch added

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54987>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 18:59:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 18:59:33 -0000
Subject: [wp-trac] [WordPress Trac] #39733: List item separator should
 be a WP_Locale property
In-Reply-To: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
References: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
Message-ID: <073.539a3e4821cf194b60d526d7219082a1@wordpress.org>

#39733: List item separator should be a WP_Locale property
--------------------------------------+-----------------------
 Reporter:  SergeyBiryukov            |       Owner:  audrasjb
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:  6.0
Component:  I18N                      |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+-----------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-13 à 19.58.38.png" added.

 After patch: separator works on WP-Admin

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39733>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 19:00:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 19:00:43 -0000
Subject: [wp-trac] [WordPress Trac] #39733: List item separator should
 be a WP_Locale property
In-Reply-To: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
References: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
Message-ID: <073.6f39a3ee2cd457044b36fb7939523817@wordpress.org>

#39733: List item separator should be a WP_Locale property
--------------------------------------+-----------------------
 Reporter:  SergeyBiryukov            |       Owner:  audrasjb
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:  6.0
Component:  I18N                      |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+-----------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-13 à 19.58.57.png" added.

 After patch: separator works on front-end (example: Twenty Thirteen)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39733>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 19:14:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 19:14:25 -0000
Subject: [wp-trac] [WordPress Trac] #39733: List item separator should
 be a WP_Locale property
In-Reply-To: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
References: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
Message-ID: <073.b73480bf22e06f1581d924594d9a181d@wordpress.org>

#39733: List item separator should be a WP_Locale property
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  I18N                                 |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch commit      |     Focuses:
  has-screenshots                                |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  good-first-bug has-patch => good-first-bug has-patch commit
     has-screenshots


Comment:

 Manual tests are going well. Marking for `commit`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39733#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 19:22:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 19:22:48 -0000
Subject: [wp-trac] [WordPress Trac] #55387: $wp_filesystem->dirlist() can
 return false and that should be checked for before iterating over the
 return value
Message-ID: <050.c9ec73ed464d696944aea28f77bcf09c@wordpress.org>

#55387: $wp_filesystem->dirlist() can return false and that should be checked for
before iterating over the return value
----------------------------+----------------------
 Reporter:  pbiron          |      Owner:  pbiron
     Type:  defect (bug)    |     Status:  assigned
 Priority:  normal          |  Milestone:  6.0
Component:  Filesystem API  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+----------------------
 There are a number of cases in core (e.g.,
 https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes/class-
 wp-upgrader.php#L500) where the return value of
 `$wp_filesystem->dirlist()` is assumed to be an array.  But since that
 method can return `false`, we should always check for that before
 iterating (or calling `array_keys()` or `array_values()` on it) over the
 return value.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55387>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 19:22:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 19:22:59 -0000
Subject: [wp-trac] [WordPress Trac] #55387: $wp_filesystem->dirlist()
 can return false and that should be checked for before iterating over the
 return value
In-Reply-To: <050.c9ec73ed464d696944aea28f77bcf09c@wordpress.org>
References: <050.c9ec73ed464d696944aea28f77bcf09c@wordpress.org>
Message-ID: <065.5139a62865668b527f147135fe9b47af@wordpress.org>

#55387: $wp_filesystem->dirlist() can return false and that should be checked for
before iterating over the return value
----------------------------+-----------------------
 Reporter:  pbiron          |       Owner:  pbiron
     Type:  defect (bug)    |      Status:  assigned
 Priority:  normal          |   Milestone:  6.0
Component:  Filesystem API  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:
----------------------------+-----------------------
Changes (by pbiron):

 * keywords:   => needs-patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55387#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 20:01:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 20:01:20 -0000
Subject: [wp-trac] [WordPress Trac] #39733: List item separator should
 be a WP_Locale property
In-Reply-To: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
References: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
Message-ID: <073.974bbb79c47b7f2f843bc26d97fde4f7@wordpress.org>

#39733: List item separator should be a WP_Locale property
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  I18N                                 |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  good-first-bug has-patch commit      |     Focuses:
  has-screenshots                                |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52929" 52929]:
 {{{
 #!CommitTicketReference repository="" revision="52929"
 i18n: Define List item separator as a WP_Locale property.

 The list item separator is a locale property, and it doesn't make much
 sense to translate it separately in multiple projects. This changeset
 implements the following modifications:

 - Define list item separator as a new WP_Locale property
 - Add `wp_get_list_item_separator()` as a wrapper for
 `WP_Locale::get_list_item_separator`
 - Replace `$wp_locale->get_list_item_separator()` calls with
 `wp_get_list_item_separator()`
 - Added a compatibility layer for bundled themes

 Props SergeyBiryukov, swissspidy, rsiddharth, johnbillion, audrasjb.
 Fixes #39733.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39733#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 20:01:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 20:01:57 -0000
Subject: [wp-trac] [WordPress Trac] #39733: List item separator should
 be a WP_Locale property
In-Reply-To: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
References: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
Message-ID: <073.3b7d4c654bbf62f30b0b4611105938d8@wordpress.org>

#39733: List item separator should be a WP_Locale property
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  I18N                                 |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  good-first-bug has-patch commit      |     Focuses:
  has-screenshots needs-dev-note                 |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  good-first-bug has-patch commit has-screenshots => good-first-
     bug has-patch commit has-screenshots needs-dev-note


Comment:

 This change deserves a dev note or at least a mention in the Misc changes
 dev note.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39733#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 20:58:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 20:58:25 -0000
Subject: [wp-trac] [WordPress Trac] #54987: Check if 'user_nicename' is
 not too long after the 'pre_user_nicename' filter
In-Reply-To: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
References: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
Message-ID: <073.7a15dcc773fa3fd7294a327d84a01674@wordpress.org>

#54987: Check if 'user_nicename' is not too long after the 'pre_user_nicename'
filter
--------------------------------------+----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  davidbaumwald
     Type:  defect (bug)              |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Users                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+----------------------------

Comment (by azouamauriac):

 Replying to [comment:10 SergeyBiryukov]:
 > * [https://github.com/WordPress/wordpress-develop/pull/2244 PR #2244]
 introduces a new check that `$user_nicename` cannot be empty. I think this
 would be better discussed in a separate ticket.

 I don't think this worth another ticket, there is already a control above
 to make sure the nicename won't be empty
 [[Image(https://prnt.sc/B6DCuHPqSNDh)]]


 > For this ticket, I was thinking of just moving the existing check after
 the filter, like in [attachment:"54987.2.diff"].
 Agree. This LGTM.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54987#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 21:04:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 21:04:58 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.f9ecb4f46c8a491ea06caee578a3a2f7@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by audrasjb):

 In [changeset:"52930" 52930]:
 {{{
 #!CommitTicketReference repository="" revision="52930"
 Docs: Use third-person singular verbs for function descriptions in `wp-
 includes/class-wp-locale.php`.

 Follow-up to [52929].

 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 13 21:54:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 13 Mar 2022 21:54:28 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.f31693cb0a87a52cb034268cf49121e1@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by audrasjb):

 In [changeset:"52931" 52931]:
 {{{
 #!CommitTicketReference repository="" revision="52931"
 Docs: Miscellaneous fixes in `wp-admin/includes/plugin-install.php` and
 `wp-admin/includes/plugin.php`.

 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 05:03:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 05:03:30 -0000
Subject: [wp-trac] [WordPress Trac] #55388: Lost Password URL filtration
Message-ID: <052.31b16ee5de91bb7c754391b494e2fa07@wordpress.org>

#55388: Lost Password URL filtration
---------------------------------------------+-----------------------------
 Reporter:  wparslan                         |      Owner:  (none)
     Type:  enhancement                      |     Status:  new
 Priority:  normal                           |  Milestone:  Awaiting Review
Component:  Login and Registration           |    Version:
 Severity:  normal                           |   Keywords:
  Focuses:  accessibility, coding-standards  |
---------------------------------------------+-----------------------------
 We have a register URL filter to change the whole tag of register link on
 wp-login.php

 wp-login.php line 1450
 {{{#!php
 <?php
 $registration_url = sprintf( '<a href="%s">%s</a>', esc_url(
 wp_registration_url() ), __( 'Register' ) );

 /** This filter is documented in wp-includes/general-template.php */
 echo apply_filters( 'register', $registration_url );
 }}}

 So I suggest the lost password should also get the same treatment as well
 like;

 {{{#!php
 <?php
 $lost_password_url = sprintf( '<a href="%s">%s</a>', esc_url(
 wp_lostpassword_url() ), __( 'Lost your password?' ) );

 echo apply_filters( 'lost_password_url', $lost_password_url );
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55388>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 07:14:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 07:14:53 -0000
Subject: [wp-trac] [WordPress Trac] #55388: Lost Password URL filtration
In-Reply-To: <052.31b16ee5de91bb7c754391b494e2fa07@wordpress.org>
References: <052.31b16ee5de91bb7c754391b494e2fa07@wordpress.org>
Message-ID: <067.8dd19ebfad09c3ee5274882bbd788f3e@wordpress.org>

#55388: Lost Password URL filtration
------------------------------------+------------------------------
 Reporter:  wparslan                |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Login and Registration  |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  needs-patch             |     Focuses:
------------------------------------+------------------------------
Changes (by dingo_d):

 * keywords:   => needs-patch
 * focuses:  accessibility, coding-standards =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55388#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 08:09:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 08:09:32 -0000
Subject: [wp-trac] [WordPress Trac] #55389:
 "><svg/onload=alert(document.domain)>
Message-ID: <050.07d161edf2fb83247876385d51e51cb0@wordpress.org>

#55389: "><svg/onload=alert(document.domain)>
-------------------------+-------------------------------------------------
 Reporter:  g0urav       |      Owner:  (none)
     Type:  defect       |     Status:  new
  (bug)                  |
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |  "><svg/onload=alert(document.domain)>
-------------------------+-------------------------------------------------
 "><svg/onload=alert(document.domain)>

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55389>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 10:43:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 10:43:45 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.8c9262ebdb591b3e09597ec90f939be9@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  5.9
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------

Comment (by paapst):

 From the discussion on the #core-privacy channel, it now seems that this
 is not a bug but intended behaviour.  Basically in this particular case
 Core offers functionality to plugins that can not be used by core itself.
 A site owner that wants to comply with an erasure request from a user,
 needs to manually delete the user account, but can not use the "Erase
 personal data" Tool for that. To be honest, I would have never expected
 that.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55346#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 11:57:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 11:57:29 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
In-Reply-To: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
References: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
Message-ID: <068.abd4a6c4de0104a1a20dbcf7b4f379ea@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
--------------------------------------+---------------------
 Reporter:  talldanwp                 |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  REST API                  |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by antonvlasenko):

 Test Report

 Web Server: Apache
 WordPress: 6.0-alpha
 Browser: Chrome 99
 OS: macOS 12.2.1
 Theme: Twenty Twenty-Two
 Plugins: None.

 Steps to test:
 1. Open the browser dev tools to the network tab.
 2. In the post editor, add an image block and upload an image.
 3. Select ‘Crop’ from the toolbar and adjust the zoom on the image.
 4. Click ‘Apply’.
 5. Observe that the request to the media endpoint returns a 500 status.
 6. Apply [https://github.com/WordPress/wordpress-develop/pull/2400 2400]
 7. Repeat steps 1-4.
 8. Observe that the request ended successfully (200 response status).

 Before:
 [[Image(https://cldup.com/k3sr3UYtb0.png)]]

 After:
 [[Image(https://cldup.com/MiVoBtdmnB.png)]]

 The proposed [https://github.com/WordPress/wordpress-develop/pull/2400 PR]
 fixes the issue and therefore it should be merged.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55367#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 12:36:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 12:36:25 -0000
Subject: [wp-trac] [WordPress Trac] #54924: [video] shortcode with vimeo
 url
In-Reply-To: <049.db37046112dcb75b85eda256e8d811c7@wordpress.org>
References: <049.db37046112dcb75b85eda256e8d811c7@wordpress.org>
Message-ID: <064.52ac3392f3e076e2d03b80d40f4c47cb@wordpress.org>

#54924: [video] shortcode with vimeo url
------------------------------------------------+--------------------------
 Reporter:  elpix                               |       Owner:  (none)
     Type:  defect (bug)                        |      Status:  new
 Priority:  normal                              |   Milestone:  Awaiting
                                                |  Review
Component:  Embeds                              |     Version:  5.9
 Severity:  critical                            |  Resolution:
 Keywords:  has-testing-info reporter-feedback  |     Focuses:  ui
------------------------------------------------+--------------------------

Comment (by elpix):

 The fix could be : "If there are no parameters in the vimeo url => do the
 code"

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54924#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 12:59:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 12:59:04 -0000
Subject: [wp-trac] [WordPress Trac] #55346: Problem in GDPR regulations
 provided by core wordpress
In-Reply-To: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
References: <049.4665d62de08e126c2717ba46a53dea64@wordpress.org>
Message-ID: <064.d6c7bcf437953e3ec8afb738e5440cf5@wordpress.org>

#55346: Problem in GDPR regulations provided by core wordpress
--------------------------------------------+-----------------------
 Reporter:  fs5ve                           |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  reopened
 Priority:  normal                          |   Milestone:
Component:  Privacy                         |     Version:  4.9.6
 Severity:  major                           |  Resolution:
 Keywords:  has-privacy-review 2nd-opinion  |     Focuses:
--------------------------------------------+-----------------------
Changes (by johnbillion):

 * version:  5.9 => 4.9.6


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55346#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 13:29:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 13:29:20 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
In-Reply-To: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
References: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
Message-ID: <068.7e8bbcff2119a7108b9b2198510a04ec@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
---------------------------------------------+---------------------
 Reporter:  talldanwp                        |       Owner:  (none)
     Type:  defect (bug)                     |      Status:  new
 Priority:  normal                           |   Milestone:  6.0
Component:  REST API                         |     Version:  trunk
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+---------------------
Changes (by costdev):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests commit


Comment:

 Thanks for adding your test report @antonvlasenko!

 Marking for `commit` consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55367#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 14:35:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 14:35:04 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.52f4a237c64b55074e709cd68495f4a1@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------------+----------------------------------------
 Reporter:  SergeyBiryukov        |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:  6.0
Component:  Administration        |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  has-patch needs-      |     Focuses:  accessibility, javascript
  testing                         |
----------------------------------+----------------------------------------
Changes (by johnregan3):

 * Attachment "55078-2.diff" added.

 Updated patch using actual text as the message value.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55078>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 14:50:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 14:50:18 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
In-Reply-To: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
References: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
Message-ID: <068.598df39dc6769e15421aa30049e81cd1@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
---------------------------------------------+-----------------------------
 Reporter:  talldanwp                        |       Owner:  hellofromTonya
     Type:  defect (bug)                     |      Status:  reviewing
 Priority:  normal                           |   Milestone:  6.0
Component:  REST API                         |     Version:  trunk
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------------
Changes (by hellofromTonya):

 * owner:  (none) => hellofromTonya
 * status:  new => reviewing


Comment:

 Thank you @costdev @antonvlasenko for testing and test reports. Thank you
 @spacedmonkey for the PR.

 Assigning to me for commit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55367#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 16:30:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 16:30:50 -0000
Subject: [wp-trac] [WordPress Trac] #55367: Requests to the media/edit
 endpoint are returning a 500 status
In-Reply-To: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
References: <053.23a7d2d0c78151cf86a973265c4df7c1@wordpress.org>
Message-ID: <068.577ddf59b2174fb122ac9c0a31596c2a@wordpress.org>

#55367: Requests to the media/edit endpoint are returning a 500 status
---------------------------------------------+-----------------------------
 Reporter:  talldanwp                        |       Owner:  hellofromTonya
     Type:  defect (bug)                     |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  REST API                         |     Version:  trunk
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------------
Changes (by hellofromTonya):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52932" 52932]:
 {{{
 #!CommitTicketReference repository="" revision="52932"
 Media: Relocate `wp_filesize()` function for use in frontend and backend.

 A new function `wp_filesize()` was added with [52837]. The function lived
 in the `wp-admin/includes/file.php` file. However, this admin specific
 function is not loaded into memory when hitting `media/edit` endpoint. The
 result was a `500` Internal Server Error. Why? The function is invoked
 with that endpoint, but the function does not exist in memory.

 This commit relocates the new function to the `wp-includes/functions.php`
 file. In doing so, the function is available for both the frontend and
 backend.

 Follow-up to [52837].

 Props talldanwp, spacedmonkey, costdev, antonvlasenko.
 Fixes #55367.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55367#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 16:52:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 16:52:23 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.25434f00655ad80054e23bf6a58f58e8@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
--------------------------+----------------------------
 Reporter:  flixos90      |       Owner:  joedolson
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  6.0
Component:  Media         |     Version:  4.5
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  accessibility
--------------------------+----------------------------

Comment (by antonvlasenko):

 I'm able to reproduce this bug.
 I will try to work on a patch to see if I can move this issue forward.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 17:43:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 17:43:46 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly
 with Odysee.com (half working)
In-Reply-To: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
References: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
Message-ID: <070.da394a4b242078a35df8a7e50e18c72e@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+------------------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+------------------------------

Comment (by tomatodysee):

 Wondering if anyone had the time to review the above or has any questions?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55278#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 17:59:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 17:59:35 -0000
Subject: [wp-trac] [WordPress Trac] #39733: List item separator should
 be a WP_Locale property
In-Reply-To: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
References: <058.4b5a647d9482fc6b50f8b29351b60e83@wordpress.org>
Message-ID: <073.5b8576794e2548383bf8133f0787f0cc@wordpress.org>

#39733: List item separator should be a WP_Locale property
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  I18N                                 |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  good-first-bug has-patch commit      |     Focuses:
  has-screenshots needs-dev-note                 |
-------------------------------------------------+-------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52933" 52933]:
 {{{
 #!CommitTicketReference repository="" revision="52933"
 I18N: Move `wp_get_list_item_separator()` to a more appropriate place.

 Follow-up to [52929].

 See #39733.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39733#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 18:12:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 18:12:43 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.6780d8709b08c8294fe510d8a439793a@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52934" 52934]:
 {{{
 #!CommitTicketReference repository="" revision="52934"
 Docs: Further clarify the description for `install_dashboard()`.

 Follow-up to [52931].

 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:38>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 18:27:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 18:27:00 -0000
Subject: [wp-trac] [WordPress Trac] #55389: Move the introduction text from
 install_dashboard() to display_plugins_table()
Message-ID: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>

#55389: Move the introduction text from install_dashboard() to
display_plugins_table()
----------------------------+----------------------------------------
 Reporter:  SergeyBiryukov  |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  6.0
Component:  Plugins         |    Version:
 Severity:  trivial         |   Keywords:  needs-patch good-first-bug
  Focuses:  administration  |
----------------------------+----------------------------------------
 `install_dashboard()` starts with this text for the Featured tab of Add
 Plugins screen:
 > Plugins extend and expand the functionality of WordPress. You may
 automatically install plugins from the WordPress Plugin Directory or
 upload a plugin in .zip format by clicking the button at the top of this
 page.

 Some similar sentences are also found in the `display_plugins_table()`
 function:
 * For the Recommended tab: "These suggestions are based on the plugins you
 and other users have installed".
 * For the Beta Testing tab: "You are using a development version of
 WordPress. These feature plugins are also under development".

 To have these introductions in a single place, the first one should be
 moved to `display_plugins_table()` as well for consistency.

 Some history here: [9141], [30889], [36297].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55389>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 18:43:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 18:43:33 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.859e81e0e214bc54add9760455e25d96@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------------+----------------------------------------
 Reporter:  SergeyBiryukov        |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:  6.0
Component:  Administration        |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  has-patch needs-      |     Focuses:  accessibility, javascript
  testing                         |
----------------------------------+----------------------------------------
Changes (by johnregan3):

 * Attachment "55078-3.diff" added.

 Updated to pass Unit Tests

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55078>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 18:44:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 18:44:20 -0000
Subject: [wp-trac] [WordPress Trac] #55078: Remove hardcoded check for
 edit-tags.php from lib/ajax-response.js
In-Reply-To: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
References: <058.ad9ebf29f9a2167068d32b7d638bef84@wordpress.org>
Message-ID: <073.f67d0d1b14dd887c7c8e284b5e99a089@wordpress.org>

#55078: Remove hardcoded check for edit-tags.php from lib/ajax-response.js
----------------------------------+----------------------------------------
 Reporter:  SergeyBiryukov        |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:  6.0
Component:  Administration        |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  has-patch needs-      |     Focuses:  accessibility, javascript
  testing                         |
----------------------------------+----------------------------------------

Comment (by johnregan3):

 @SergeyBiryukov Updated patch to pass PHPUnit tests.  Also issued a PR for
 further discussion as needed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55078#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 21:37:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 21:37:01 -0000
Subject: [wp-trac] [WordPress Trac] #46057: Remove self-references
 ("we") in text in core
In-Reply-To: <055.675410e1a7b30657f2327896dc28409d@wordpress.org>
References: <055.675410e1a7b30657f2327896dc28409d@wordpress.org>
Message-ID: <070.73f65a4af7264035c8ea8f365215b510@wordpress.org>

#46057: Remove self-references ("we") in text in core
-----------------------------------------+------------------------------
 Reporter:  johnbillion                  |       Owner:  johnjamesjacoby
     Type:  enhancement                  |      Status:  reopened
 Priority:  normal                       |   Milestone:  6.0
Component:  Administration               |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+------------------------------

Comment (by peterwilsoncc):

 The "so do we" text on the freedoms pages was removed in [52626] so the
 need to change that can be discarded.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46057#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 22:27:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 22:27:28 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly
 with Odysee.com (half working)
In-Reply-To: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
References: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
Message-ID: <070.ffa0e1bcf25d6491ab23dd9ab277fd89@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+----------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:  wontfix
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+----------------------
Changes (by peterwilsoncc):

 * status:  new => closed
 * resolution:   => wontfix
 * milestone:  Awaiting Review =>


Comment:

 I don't think the service is popular or stable enough to be added to the
 allow list.

 I suggest either modifying your embed so it doesn't set cookies on the
 parent page or create a plugin for the official
 [https://wordpress.org/plugins WordPress plugins repository] to see if it
 gets traction there.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55278#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 23:43:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 23:43:23 -0000
Subject: [wp-trac] [WordPress Trac] #55213: Respect _fields query arg in
 preloaded requests
In-Reply-To: <051.d712b5ccb9e8118ed260725e0fdb22c9@wordpress.org>
References: <051.d712b5ccb9e8118ed260725e0fdb22c9@wordpress.org>
Message-ID: <066.3b80e84866cccf1e9b191abd776b5d1b@wordpress.org>

#55213: Respect _fields query arg in preloaded requests
-------------------------+---------------------
 Reporter:  jsnajdr      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  REST API     |     Version:  5.9
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------
Changes (by noisysocks):

 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55213#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 14 23:52:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 14 Mar 2022 23:52:54 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly
 with Odysee.com (half working)
In-Reply-To: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
References: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
Message-ID: <070.60e2e3fd219cdc56159d94bcf0cc8804@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+----------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:  wontfix
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+----------------------

Comment (by tomatodysee):

 May I ask what made you come to a conclusion about stability?

 35M+ unique visits a month is not enough for a video site? Only a few long
 standing alternatives can say the same, and this area needs competition
 for Google and the other big tech. Who can we escalate this to?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55278#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 00:44:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 00:44:16 -0000
Subject: [wp-trac] [WordPress Trac] #55352: Improve cache key generation
 in WP_Term_Query
In-Reply-To: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
References: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
Message-ID: <071.96990e769305ea03ccd67788e55c479e@wordpress.org>

#55352: Improve cache key generation in WP_Term_Query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  4.7
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------
Changes (by spacedmonkey):

 * keywords:  needs-unit-tests has-patch => has-patch has-unit-tests
 * owner:  (none) => spacedmonkey
 * status:  new => assigned
 * milestone:  Future Release => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55352#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 01:13:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 01:13:12 -0000
Subject: [wp-trac] [WordPress Trac] #55278: Fix Support for embed.ly
 with Odysee.com (half working)
In-Reply-To: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
References: <055.2409d41840aec0bf605a5521f83257c2@wordpress.org>
Message-ID: <070.d4ea76ecef12cc3b8997784e05fd0085@wordpress.org>

#55278: Fix Support for embed.ly with Odysee.com (half working)
-------------------------+----------------------
 Reporter:  tomatodysee  |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Embeds       |     Version:
 Severity:  normal       |  Resolution:  wontfix
 Keywords:  has-patch    |     Focuses:  ui
-------------------------+----------------------

Comment (by peterwilsoncc):

 Replying to [comment:9 tomatodysee]:
 > May I ask what made you come to a conclusion about stability?

 The name was changed recently, which suggests branding is still sorted
 out.

 > 35M+ unique visits a month is not enough for a video site? Only a few
 long standing alternatives can say the same, and this area needs
 competition for Google and the other big tech.

 No, it's not really enough visitors to add the site to the allow list.
 WordPress needs to be sure a service is going to stick around long term
 before adding a site to the supported embeds. Adding sites too early
 increases the risk we will need to remove them later.

 > Who can we escalate this to?

 There's not an escalation procedure. I did discuss your site with another
 committer/maintainer prior to my earlier reply for a logic check.

 As I said earlier, you're welcome to put a plugin in the official
 repository to see if if it gains traction.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55278#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 04:36:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 04:36:15 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in
 releases without a global theme auto-update setting renders installations
 insecure
In-Reply-To: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
References: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
Message-ID: <072.68fce635ec63b11e17cd53b2a5c53ce6@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
-------------------------------+-----------------------
 Reporter:  bertvandepoel      |       Owner:  pbiron
     Type:  enhancement        |      Status:  assigned
 Priority:  normal             |   Milestone:  6.0
Component:  Upgrade/Install    |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+-----------------------

Comment (by peterwilsoncc):

 I share @Otto42's concern about developers modifying themes directly. It's
 certainly something I did when I was less experienced. I'm asking around
 for some more anecdotes.

 @pbiron When the UI was introduced for plugins, do you recall what
 discussion was had about themes at the time?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55321#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 05:33:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 05:33:21 -0000
Subject: [wp-trac] [WordPress Trac] #6479: Encourage people to change
 default tagline
In-Reply-To: <055.e530d469b6d3d46c70a1707e6bd1ead0@wordpress.org>
References: <055.e530d469b6d3d46c70a1707e6bd1ead0@wordpress.org>
Message-ID: <070.c518a7b48e48ad1b7d834dde578293c8@wordpress.org>

#6479: Encourage people to change default tagline
-------------------------------------------------+-------------------------
 Reporter:  markjaquith                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  2.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-unit-  |     Focuses:
  tests needs-refresh                            |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch 2nd-opinion needs-testing needs-unit-tests => has-
     patch needs-testing needs-unit-tests needs-refresh
 * owner:  markjaquith => (none)


Comment:

 This was discussed today in a triage session.

 There's still a little to do prior to release but we can keep it on the
 milestone for now.

 * There are a few unit tests failing relating to `the_title`
 * If not already, adding the site tag to the installation screens would be
 good too
 * Ensure the tagline is optional

 props: @hilayt24, @chaion07, @mehedi890, @markparnell for contributing to
 discussion

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/6479#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 06:11:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 06:11:34 -0000
Subject: [wp-trac] [WordPress Trac] #32747: WP Admin Menus/SubMenus
 Overlap in small screen
In-Reply-To: <053.19f81590b59ff77c2a9b31983b4caf91@wordpress.org>
References: <053.19f81590b59ff77c2a9b31983b4caf91@wordpress.org>
Message-ID: <068.31b65f1f42ad35edf2d56a04d37fcf18@wordpress.org>

#32747: WP Admin Menus/SubMenus Overlap in small screen
----------------------------+-------------------------------------
 Reporter:  turtlepod       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Administration  |     Version:  4.2.2
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  ui, accessibility, css
----------------------------+-------------------------------------

Comment (by chaion07):

 Thanks @turtlepod for reporting this. We reviewed the ticket during a
 recent bug scrub session. Here's a summary of the feedback provided by the
 team:

 01. The issue can be reproduced on 5.9.2
 02. The issue seems to appear when you resize the window but when you
 reload then it seems to work just fine
 03. There are cases though when the issue would still appear after the
 page has been loaded- as long as the window is small enough in terms of
 width and height. Opening the submenus would produce the issue.
 04. Its more likely to happen with larger submenus (i.e. settings) or with
 multiple submenus open

 @mehedi890 has volunteered to work on this. Thanks!

 Props to @hilayt24, @mehedi890 & @markparnell

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32747#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 09:17:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 09:17:04 -0000
Subject: [wp-trac] [WordPress Trac] #6479: Encourage people to change
 default tagline
In-Reply-To: <055.e530d469b6d3d46c70a1707e6bd1ead0@wordpress.org>
References: <055.e530d469b6d3d46c70a1707e6bd1ead0@wordpress.org>
Message-ID: <070.3a05f7bad610da91290e7911aa248959@wordpress.org>

#6479: Encourage people to change default tagline
-------------------------------------------------+-------------------------
 Reporter:  markjaquith                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  2.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-unit-  |     Focuses:
  tests needs-refresh                            |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 Replying to [comment:37 peterwilsoncc]:
 > * If not already, adding the site tag to the installation screens would
 be good too

 Are you sure? Adding items to the installation screen is a critical change
 since each information addition to this screen could be considered as a
 threat for the "5 mins" installation process. I think this specific
 proposal needs to be discussed a lot more before implementing it :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/6479#comment:38>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 10:53:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 10:53:34 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.146e5b476d3fbfa0491397e3ab77c8af@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------
Changes (by azouamauriac):

 * Attachment "54729.2.diff" added.

 in src/wp-includes/post-template.php and src/wp-includes/post-thumbnail-
 template.php use third person in function docblock

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 11:01:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 11:01:43 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.1e8a2d66c1037d9f0815bdbabf27fe75@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by audrasjb):

 Thanks @azouamauriac, self assigning `54729.2.diff` for review/commit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 11:02:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 11:02:58 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.11ec1cf0254fcd80745994fb6f491df0@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by azouamauriac):

 Replying to [comment:39 audrasjb]:
 > Thanks @azouamauriac, self assigning `54729.2.diff` for review/commit.

 Thanks.👍

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:40>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 11:59:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 11:59:35 -0000
Subject: [wp-trac] [WordPress Trac] #55376: Use wp_filesize in core
In-Reply-To: <056.56612536c597c54c37ea175736f1b4de@wordpress.org>
References: <056.56612536c597c54c37ea175736f1b4de@wordpress.org>
Message-ID: <071.9d6f8dbaa8a7edef31edce9e829cd6ec@wordpress.org>

#55376: Use wp_filesize in core
--------------------------------------+------------------------------
 Reporter:  spacedmonkey              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  General                   |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+------------------------------

Comment (by spacedmonkey):

 I would consider using this function in the following places.

 https://github.com/WordPress/wordpress-
 develop/blob/8697aee5f9d834c1d7135524c7f13dc3c96f4d85/src/wp-includes
 /rest-api/endpoints/class-wp-rest-edit-site-export-controller.php#L87

 https://github.com/WordPress/wordpress-
 develop/blob/2648a5f984b8abf06872151898e3a61d3458a628/src/wp-includes/ms-
 files.php#L45

 https://github.com/WordPress/wordpress-
 develop/blob/ba518c2d86e62ed63b24e9a720d42aee3ab951fb/src/wp-
 admin/includes/class-wp-filesystem-direct.php#L490

 https://github.com/WordPress/wordpress-
 develop/blob/33048b933379ae48723f617588ed8aa996ca5d14/src/wp-
 admin/includes/class-wp-filesystem-ssh2.php#L649

 https://github.com/WordPress/wordpress-
 develop/blob/ba518c2d86e62ed63b24e9a720d42aee3ab951fb/src/wp-
 admin/includes/ms.php#L33

 https://github.com/WordPress/wordpress-
 develop/blob/ecf1d6a158c70dd7f10cc42c4b26ecb0fb22bb59/src/wp-includes
 /rest-api/endpoints/class-wp-rest-attachments-controller.php#L1287

 https://github.com/WordPress/wordpress-
 develop/blob/2d707c45127d204936eef48b3c9e133b60596b33/src/wp-
 admin/includes/update-core.php#L1256

 https://github.com/WordPress/wordpress-
 develop/blob/26bb0d7479e1dd08dd982513ee6bee94f4c6f13d/src/wp-
 admin/includes/plugin.php#L401

 https://github.com/WordPress/wordpress-
 develop/blob/6adff3d989319e633cfdcdb7aff4dc906087c230/src/wp-includes
 /script-loader.php#L2736

 https://github.com/WordPress/wordpress-
 develop/blob/8db1549c0f1af05fbb919ad2eeb7f7bff5a63da9/src/wp-includes
 /class-wp-customize-manager.php#L6035

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55376#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 12:12:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 12:12:22 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.d68f40a5c9a7106423b6396660d6ff6e@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 I would love the thoughts on @boonebgorges on this one.

 Basically, it makes more sense to use taxonomy query check. Tax queries
 are cached now and performance of them is pretty solid. Long term, I would
 like deprecate `get_objects_in_term`, as it is only used in two place (
 one them is here ).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 13:17:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 13:17:46 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.faf822f4ee2e3318f20de1443e717897@wordpress.org>

#54272: Allow block themes to be activated without index.php
--------------------------------------------------+-----------------------
 Reporter:  poena                                 |       Owner:  (none)
     Type:  enhancement                           |      Status:  new
 Priority:  normal                                |   Milestone:  6.0
Component:  Themes                                |     Version:
 Severity:  normal                                |  Resolution:
 Keywords:  has-patch dev-feedback needs-refresh  |     Focuses:  template
--------------------------------------------------+-----------------------
Changes (by scruffian):

 * Attachment "54272.2.diff" added.

 Rename block-templates to templates.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 13:18:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 13:18:07 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.988464675b71f3186ab839187b0b93f7@wordpress.org>

#54272: Allow block themes to be activated without index.php
--------------------------------------------------+-----------------------
 Reporter:  poena                                 |       Owner:  (none)
     Type:  enhancement                           |      Status:  new
 Priority:  normal                                |   Milestone:  6.0
Component:  Themes                                |     Version:
 Severity:  normal                                |  Resolution:
 Keywords:  has-patch dev-feedback needs-refresh  |     Focuses:  template
--------------------------------------------------+-----------------------

Comment (by scruffian):

 IMO we should remove the index.php requirement, I can't see what value it
 adds. I have added a new diff to achieve this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 13:21:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 13:21:58 -0000
Subject: [wp-trac] [WordPress Trac] #55390: Not able to choose Color picker
 in customizer when the blocks are added in widget
Message-ID: <051.4fe1d0e6f520345833d0438163c7fc6e@wordpress.org>

#55390: Not able to choose Color picker in customizer when the blocks are added in
widget
-------------------------+-------------------------------------------------
 Reporter:  nileshc      |      Owner:  (none)
     Type:  defect       |     Status:  new
  (bug)                  |
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Editor       |    Version:  5.9.2
 Severity:  major        |   Keywords:  needs-patch needs-testing needs-
  Focuses:  ui,          |  design-feedback has-screenshots needs-design
  javascript, css        |
-------------------------+-------------------------------------------------
 Hi Team,

 I hope you are doing well and safe!

 I would like to highlight an issue with the color picker in the customizer
 when using the blocks in widgets.

 1. For choosing the custom color, whenever you click on the color
 selection, it will trigger a click event where it will ask you to leave
 the site or not?
 Here is the screenshot: https://share.bsf.io/YEur81BW

 2. The color selection palette is not properly displayed.
 Here is the screenshot: https://share.bsf.io/wbuzJ0zq

 Furthermore, I have gone ahead and found that this issue is coming from
 WordPress version 5.9.2

 Also, I have demonstrated a video that would help you check it on your end
 too.

 This issue is occurring on default themes as well as other famous themes
 as well.

 Here is the screencast: https://share.bsf.io/yAuKoy2J

 I would suggest you please check this on priority and release a patch for
 this issue, as users are facing lots of issues due to this.

 Looking forward to your response.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55390>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 13:46:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 13:46:42 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in
 releases without a global theme auto-update setting renders installations
 insecure
In-Reply-To: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
References: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
Message-ID: <072.5017a0366ec3519ea4c791dd10a1133e@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
-------------------------------+-----------------------
 Reporter:  bertvandepoel      |       Owner:  pbiron
     Type:  enhancement        |      Status:  assigned
 Priority:  normal             |   Milestone:  6.0
Component:  Upgrade/Install    |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+-----------------------

Comment (by pbiron):

 Replying to [comment:8 peterwilsoncc]:
 > @pbiron When the UI was introduced for plugins, do you recall what
 discussion was had about themes at the time?

 Yes...I do.  Their is also a UI for enabling/disabling auto-updates for
 themes :-)

 On multisite, that UI looks just like it does for themes (and only from
 the `Network Admin > Themes`).  On single sites, there is an
 "Enable/Disable auto-updates" link on `Appearance > Themes > Theme
 Details`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55321#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 14:13:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 14:13:11 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.631bf405f9d49c9678a72781bdba23bc@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+-----------------------------
 Reporter:  isaumya                   |       Owner:  (none)
     Type:  feature request           |      Status:  new
 Priority:  normal                    |   Milestone:  Future Release
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+-----------------------------

Comment (by adamsilverstein):

 @westonruter - is [attachment:"53232.1.diff"] ready? I noticed a bunch of
 small changes in the test files, can we leave those off to make the patch
 smaller or are those matching existing test paths?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:38>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 14:13:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 14:13:35 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.389ad11a563f067728ee1043159a9b5e@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------
Changes (by adamsilverstein):

 * owner:  (none) => adamsilverstein
 * status:  new => assigned
 * milestone:  Future Release => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 14:19:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 14:19:21 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in
 releases without a global theme auto-update setting renders installations
 insecure
In-Reply-To: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
References: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
Message-ID: <072.29266c671d6312cc61f4246a70ebda95@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
-------------------------------+-----------------------
 Reporter:  bertvandepoel      |       Owner:  pbiron
     Type:  enhancement        |      Status:  assigned
 Priority:  normal             |   Milestone:  6.0
Component:  Upgrade/Install    |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+-----------------------

Comment (by pbiron):

 The reason I milestoned this for consideration in 6.0 is the following:

 1. a site running WP 5.8.3 already has an active theme
 2. they update to 5.9 (possibly even via an auto-update)
 3. unbeknownst to the site owner/admin, that update installed another
 theme

 I agree that the fact that people modify themes directly is a concern.
 But I also think that WP installing new bundled themes without explicit
 consent of the site owner/admin is a reason to **consider** enabling auto-
 updates for those new bundled themes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55321#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 14:34:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 14:34:24 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.7e1f52aea4bc82c1180e430c6ee9d095@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------
Changes (by adamsilverstein):

 * Attachment "53232.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 14:36:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 14:36:02 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.c698ce1d9c5b192d7ade2820bd8f88eb@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------

Comment (by adamsilverstein):

 [attachment:"53232.diff"] is a refresh against trunk with some unrelated
 path changes in test files removed. Pushed to https://github.com/WordPress
 /wordpress-develop/pull/2409 as well for test runs.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 14:43:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 14:43:22 -0000
Subject: [wp-trac] [WordPress Trac] #55023: get_header() notice: Theme
 without header.php is deprecated
In-Reply-To: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
References: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
Message-ID: <064.b3ab88e20bfe60201958563b6b136e22@wordpress.org>

#55023: get_header() notice: Theme without header.php is deprecated
--------------------------+------------------------
 Reporter:  kpdaa         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.3
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  multisite
--------------------------+------------------------
Changes (by johnregan3):

 * Attachment "screenshot-example.png" added.

 Example Screenshot from /wp-signup.php

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55023>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:02:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:02:06 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.60153d8a33c0839d15ded76a84f58883@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------
Changes (by adamsilverstein):

 * Attachment "53232.2.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:02:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:02:31 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.e25a6d2a41facd2836d81c4045a0469a@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------

Comment (by adamsilverstein):

 [attachment:"53232.2.diff"] fixes failing avatar test

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:42>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:19:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:19:28 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.aef7376906308fcd97f854c075f22e6c@wordpress.org>

#54272: Allow block themes to be activated without index.php
-------------------------------------------------+-------------------------
 Reporter:  poena                                |       Owner:
                                                 |  SergeyBiryukov
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:  template
  refresh                                        |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => reviewing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:20:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:20:27 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.7071f36b3826cbc3a38adb03c4d33951@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by audrasjb):

 In [changeset:"52935" 52935]:
 {{{
 #!CommitTicketReference repository="" revision="52935"
 Docs: Misc. fixes in `wp-includes/post-template.php` and `wp-includes
 /post-thumbnail-template.php`.

 Props azouamauriac, audrasjb.
 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:29:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:29:47 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.111ec4eeb8ce6bb716b562270f3f1971@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------

Comment (by isaumya):

 I am so happy to see that this is finally coming to life. Thank you
 everyone for your support and suggestions. Can't wait to experience this
 in v6.0 and finally removing the custom functions to removing the decoding
 async attribute from the img tags.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:43>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:34:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:34:06 -0000
Subject: [wp-trac] [WordPress Trac] #55389: Move the introduction text
 from install_dashboard() to display_plugins_table()
In-Reply-To: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
References: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
Message-ID: <073.f15be46c5d36a64109604051ffdc0333@wordpress.org>

#55389: Move the introduction text from install_dashboard() to
display_plugins_table()
----------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov              |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Plugins                     |     Version:
 Severity:  trivial                     |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:  administration
----------------------------------------+-----------------------------
Changes (by sabbir1991):

 * Attachment "55389.diff" added.

 Created a patch

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55389>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:36:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:36:24 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.cb0f91246303a7b136b001e0c2ec364d@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-15 at 15.35.15.png" added.

 Before change

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:36:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:36:39 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.6d0a27545d38c08c0bc6a1ab300ce4ec@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-15 at 15.33.56.png" added.

 After change

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:36:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:36:58 -0000
Subject: [wp-trac] [WordPress Trac] #55389: Move the introduction text
 from install_dashboard() to display_plugins_table()
In-Reply-To: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
References: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
Message-ID: <073.471467da6ae955b646d3cd501429dc4c@wordpress.org>

#55389: Move the introduction text from install_dashboard() to
display_plugins_table()
--------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Plugins                   |     Version:
 Severity:  trivial                   |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  administration
--------------------------------------+-----------------------------
Changes (by sabbir1991):

 * keywords:  needs-patch good-first-bug => good-first-bug has-patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55389#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:37:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:37:06 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.5160bf7ac697afb1a08dfdc28da7f373@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 This change removes 3 queries on a single page load.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:38:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:38:31 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.288110216274b1defef298f82e2bd45a@wordpress.org>

#54272: Allow block themes to be activated without index.php
-------------------------------------------------+-------------------------
 Reporter:  poena                                |       Owner:
                                                 |  SergeyBiryukov
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:  template
  refresh                                        |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * Attachment "54272.3.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:41:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:41:53 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.c42d2e887a1555c17c199956f45fe03b@wordpress.org>

#54272: Allow block themes to be activated without index.php
------------------------------+-----------------------------
 Reporter:  poena             |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  6.0
Component:  Themes            |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  template
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * keywords:  has-patch dev-feedback needs-refresh => has-patch commit


Comment:

 Thanks for the patches!

 [attachment:"54272.3.diff"] is a minor adjustment to make the "or" part of
 the string translatable too.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:51:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:51:07 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.c72c21b203f9dd4757815ebf1c1abff9@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
 Reporter:  ademos                    |       Owner:  gavinwye
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+------------------------------
Changes (by paaljoachim):

 * Attachment "Bulk-Edit-Tags.jpg" added.

 All Posts screen: Bulk Edit Tags

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:51:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:51:45 -0000
Subject: [wp-trac] [WordPress Trac] #55389: Move the introduction text
 from install_dashboard() to display_plugins_table()
In-Reply-To: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
References: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
Message-ID: <073.b832ab0b1499daf72d3bef0092109f18@wordpress.org>

#55389: Move the introduction text from install_dashboard() to
display_plugins_table()
--------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Plugins                   |     Version:
 Severity:  trivial                   |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  administration
--------------------------------------+-----------------------------

Comment (by kapilpaul):

 @sabbir1991

 Welcome to trac. Thanks for the patch.

 @SergeyBiryukov I have tested this patch and it's working as expected.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55389#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:52:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:52:40 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.4c96be88bd952365c9444b3258956e91@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
 Reporter:  ademos                    |       Owner:  gavinwye
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+------------------------------

Comment (by paaljoachim):

 We can add the same X icon as seen to the left of the posts into the tags
 field as I did in the above mockup.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:33>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:54:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:54:15 -0000
Subject: [wp-trac] [WordPress Trac] #55250: Avoid sending empty script
 translations
In-Reply-To: <051.c70c175c4cc365c6efdc917141cf72df@wordpress.org>
References: <051.c70c175c4cc365c6efdc917141cf72df@wordpress.org>
Message-ID: <066.0061b613f74b4d0360ae44556d720dd0@wordpress.org>

#55250: Avoid sending empty script translations
--------------------------+---------------------
 Reporter:  jsnajdr       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  I18N          |     Version:  5.0
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------
Changes (by ocean90):

 * version:  5.9 => 5.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55250#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:55:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:55:42 -0000
Subject: [wp-trac] [WordPress Trac] #38741: Introduce the concept of a
 large site in order to speed up the Users screen when there are many users
In-Reply-To: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
References: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
Message-ID: <070.49fb9b547f6f8b311c4c324f1332210d@wordpress.org>

#38741: Introduce the concept of a large site in order to speed up the Users screen
when there are many users
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  (none)
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  early has-patch dev-     |     Focuses:  administration,
  feedback needs-testing 2nd-        |  multisite, performance
  opinion                            |
-------------------------------------+-------------------------------------

Comment (by davidbaumwald):

 Per @spacedmonkey's suggestion, I created [https://github.com/WordPress
 /wordpress-develop/pull/2410 PR #2410] to get the ball rolling here again.
 This will need to move soon if it's to land `early` in 6.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38741#comment:68>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:55:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:55:43 -0000
Subject: [wp-trac] [WordPress Trac] #55389: Move the introduction text
 from install_dashboard() to display_plugins_table()
In-Reply-To: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
References: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
Message-ID: <073.2da8eb442e642faca552e49f010d46f4@wordpress.org>

#55389: Move the introduction text from install_dashboard() to
display_plugins_table()
--------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Plugins                   |     Version:
 Severity:  trivial                   |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  administration
--------------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 Hi there, welcome back to WordPress Trac! Thanks for the patch, it looks
 good to me too.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55389#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:56:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:56:51 -0000
Subject: [wp-trac] [WordPress Trac] #55389: Move the introduction text
 from install_dashboard() to display_plugins_table()
In-Reply-To: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
References: <058.d43df65d553eb13b0549929da8691ade@wordpress.org>
Message-ID: <073.fc0b12a0b7ed9906dc114d0cbec19303@wordpress.org>

#55389: Move the introduction text from install_dashboard() to
display_plugins_table()
--------------------------------------+-----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  SergeyBiryukov
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Plugins                   |     Version:
 Severity:  trivial                   |  Resolution:  fixed
 Keywords:  good-first-bug has-patch  |     Focuses:  administration
--------------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52936" 52936]:
 {{{
 #!CommitTicketReference repository="" revision="52936"
 Plugins: Move the introduction text from `install_dashboard()` to
 `display_plugins_table()`.

 This brings some consistency to how the introduction is displayed for the
 Beta Testing, Featured, and Recommended tabs of the Add Plugins screen.

 This commit also reorders the `switch` cases for the text in the same
 order as they are displayed.

 Follow-up to [9141], [30889], [36297].

 Props sabbir1991, kapilpaul.
 Fixes #55389.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55389#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 15:58:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 15:58:14 -0000
Subject: [wp-trac] [WordPress Trac] #55250: Avoid sending empty script
 translations
In-Reply-To: <051.c70c175c4cc365c6efdc917141cf72df@wordpress.org>
References: <051.c70c175c4cc365c6efdc917141cf72df@wordpress.org>
Message-ID: <066.f56c1c4854311cb4418669f9ae0fb850@wordpress.org>

#55250: Avoid sending empty script translations
--------------------------+----------------------
 Reporter:  jsnajdr       |       Owner:  ocean90
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  6.0
Component:  I18N          |     Version:  5.0
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |     Focuses:
--------------------------+----------------------
Changes (by ocean90):

 * owner:  (none) => ocean90
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52937" 52937]:
 {{{
 #!CommitTicketReference repository="" revision="52937"
 I18N, Script Loader: Don't register empty locale data objects.

 For `wp.i18n` the library [https://github.com/messageformat/Jed Jed] was
 initially used which was throwing an error if a domain was not registered
 but used in a translate function. Later, the library was replaced by
 [https://github.com/aduth/tannin Tannin] which no longer requires the
 domain to be registered and thus we can avoid printing an empty-ish
 translations script that doesn't add any translations.

 Props jsnajdr.
 Fixes #55250.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55250#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:09:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:09:45 -0000
Subject: [wp-trac] [WordPress Trac] #38741: Introduce the concept of a
 large site in order to speed up the Users screen when there are many users
In-Reply-To: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
References: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
Message-ID: <070.73c150e89578202e5e202a5de5331850@wordpress.org>

#38741: Introduce the concept of a large site in order to speed up the Users screen
when there are many users
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  (none)
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  early has-patch dev-     |     Focuses:  administration,
  feedback needs-testing 2nd-        |  multisite, performance
  opinion needs-unit-tests           |
-------------------------------------+-------------------------------------
Changes (by davidbaumwald):

 * keywords:  early has-patch dev-feedback needs-testing 2nd-opinion =>
     early has-patch dev-feedback needs-testing 2nd-opinion needs-unit-
     tests


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38741#comment:70>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:30:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:30:55 -0000
Subject: [wp-trac] [WordPress Trac] #55360: Add limit to query in
 WP_Tax_Query
In-Reply-To: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
References: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
Message-ID: <071.f0e6b15c692c5f3669402d8658c5ecae@wordpress.org>

#55360: Add limit to query in WP_Tax_Query
--------------------------------------+------------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Taxonomy                  |     Version:  4.7
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------
Changes (by spacedmonkey):

 * keywords:  has-patch => has-patch has-unit-tests


Comment:

 I recommend testing this ticket along side #55352.

 With this change in place, it means that the early call to `get_term_by`
 populates the cache for the taxonomy query. This means one less query per
 page on tag pages.

 Even without this benefit, limiting the query, makes the query return
 first, as SQL, stop processing once the limit is meet.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55360#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:33:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:33:00 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.0036cf8bc45fbed1c7753380b4b6b183@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Changes (by gziolo):

 * Attachment "55311.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:34:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:34:14 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <052.71705d312df930659699caa7e0d22c46@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Changes (by gziolo):

 * Attachment "55311.diff" removed.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:34:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:34:14 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.185c058b802d250e3f91cbbae8c1e777@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Changes (by gziolo):

 * Attachment "55311.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:35:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:35:49 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <052.71705d312df930659699caa7e0d22c46@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Changes (by gziolo):

 * Attachment "55311.diff" removed.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:35:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:35:49 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.09cba8204f092fa400a312cb0fa05f16@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Changes (by gziolo):

 * Attachment "55311.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:43:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:43:48 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.a1115d49b65ad0b845ac16e82ad3aa2d@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by gziolo):

 @Mamaduka, it looks like there are 3 places where we should wrap filepaths
 with `realpath`.

 Let's test the patch attached and plan to land it soon.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:43:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:43:56 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.edef095d5264f940bf9689e5e29eed60@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.2
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Changes (by gziolo):

 * version:  5.9.1 => 5.9.2


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:44:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:44:13 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.c046affddfa850e299839a1df4e3ccc5@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.2
 Severity:  major          |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+------------------------------
Changes (by gziolo):

 * keywords:   => has-patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:50:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:50:36 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.edd25710aea9ae52d9c64c9d226688ce@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+------------------------------
Changes (by gziolo):

 * version:  5.9.2 => 5.9.1


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 16:52:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 16:52:19 -0000
Subject: [wp-trac] [WordPress Trac] #55391: Image menu icon with empty alt
 text
Message-ID: <057.7d798a7e1714daac62cef69ff500f20b@wordpress.org>

#55391: Image menu icon with empty alt text
----------------------------+-----------------------------
 Reporter:  pedromendonca   |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 For menu items with image icon set, the alt text is hardcoded empty:
 https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-admin
 /menu-header.php#L126

 I suggest adding the Menu item name to it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55391>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 17:06:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 17:06:15 -0000
Subject: [wp-trac] [WordPress Trac] #55391: Image menu icon with empty
 alt text
In-Reply-To: <057.7d798a7e1714daac62cef69ff500f20b@wordpress.org>
References: <057.7d798a7e1714daac62cef69ff500f20b@wordpress.org>
Message-ID: <072.01e95d596c0cafe1fec4b53bd02b4f01@wordpress.org>

#55391: Image menu icon with empty alt text
----------------------------+------------------------------
 Reporter:  pedromendonca   |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+------------------------------

Comment (by pedromendonca):

 If redundancy is unwanted, which makes sense, should the empty alt text be
 kept?

 https://dequeuniversity.com/rules/axe/4.0/image-redundant-alt

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55391#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 17:08:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 17:08:14 -0000
Subject: [wp-trac] [WordPress Trac] #55391: Image menu icon with empty
 alt text
In-Reply-To: <057.7d798a7e1714daac62cef69ff500f20b@wordpress.org>
References: <057.7d798a7e1714daac62cef69ff500f20b@wordpress.org>
Message-ID: <072.4646b8e146be80412ec09775c14134dc@wordpress.org>

#55391: Image menu icon with empty alt text
----------------------------+------------------------------
 Reporter:  pedromendonca   |       Owner:  (none)
     Type:  enhancement     |      Status:  closed
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:  invalid
 Keywords:  has-patch       |     Focuses:
----------------------------+------------------------------
Changes (by pedromendonca):

 * status:  new => closed
 * resolution:   => invalid


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55391#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 17:14:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 17:14:59 -0000
Subject: [wp-trac] [WordPress Trac] #55385: Error in Search
In-Reply-To: <061.caa3b2cb4d146df3b0520cddfdc2b8c5@wordpress.org>
References: <061.caa3b2cb4d146df3b0520cddfdc2b8c5@wordpress.org>
Message-ID: <076.97cbffbc610b9338766cf2c3af7a2a15@wordpress.org>

#55385: Error in Search
-------------------------------+------------------------------
 Reporter:  himanshushokhanda  |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by costdev):

 * keywords:   => reporter-feedback


Comment:

 Hi @himanshushokhanda, welcome to Trac!

 I can't seem to reproduce this issue.

 === Env
 WordPress: 5.9.2
 OS: Linux
 Browser: Chrome
 Theme: Twenty-Twenty Two
 Plugins: None activated

 === Steps to reproduce the issue
 1. Navigate to `Posts > All Posts`.
 2. Search for `www.profile.com`. If brought to the frontend, the issue has
 been reproduced.

 3. Navigate to `Pages > All Pages`.
 4. Search for `www.profile.com`. If brought to the frontend, the issue has
 been reproduced.

 === Results
 - The page refreshed and displayed search results as expected. Issue not
 reproduced.

 -----

 @himanshushokhanda, can you tell us:

 - Are the above steps to reproduce the issue correct?
 - What version of WordPress are you using?
 - Have you tried disabling plugins in case one of these is causing an
 issue when searching posts?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55385#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 17:43:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 17:43:30 -0000
Subject: [wp-trac] [WordPress Trac] #54477: wp-cli vague: "Warning:
 Could not create directory."
In-Reply-To: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
References: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
Message-ID: <067.f9b517235e484c531ff56b42592a13ae@wordpress.org>

#54477: wp-cli vague: "Warning: Could not create directory."
-----------------------------+---------------------
 Reporter:  gunterer         |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  5.8
 Severity:  minor            |  Resolution:
 Keywords:  needs-patch      |     Focuses:
-----------------------------+---------------------

Comment (by n8finch):

 @gunterer thanks for creating this ticket!

 @SergeyBiryukov I'd like to work on this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54477#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 17:58:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 17:58:58 -0000
Subject: [wp-trac] [WordPress Trac] #38741: Introduce the concept of a
 large site in order to speed up the Users screen when there are many users
In-Reply-To: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
References: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
Message-ID: <070.32d18b64b98267df453954251ea27b56@wordpress.org>

#38741: Introduce the concept of a large site in order to speed up the Users screen
when there are many users
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  (none)
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  early has-patch dev-     |     Focuses:  administration,
  feedback needs-testing 2nd-        |  multisite, performance
  opinion needs-unit-tests           |
-------------------------------------+-------------------------------------

Comment (by spacedmonkey):

 I have created a scaled back patch at [https://github.com/WordPress
 /wordpress-develop/pull/2413 #2413]. It keeps support for multiple
 networks and doesn't break backwards compatibility.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38741#comment:72>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 17:59:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 17:59:06 -0000
Subject: [wp-trac] [WordPress Trac] #38741: Introduce the concept of a
 large site in order to speed up the Users screen when there are many users
In-Reply-To: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
References: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
Message-ID: <070.36dee58bca0b43fd6598e5d763cdfb86@wordpress.org>

#38741: Introduce the concept of a large site in order to speed up the Users screen
when there are many users
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  spacedmonkey
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  early has-patch dev-     |     Focuses:  administration,
  feedback needs-testing 2nd-        |  multisite, performance
  opinion needs-unit-tests           |
-------------------------------------+-------------------------------------
Changes (by spacedmonkey):

 * owner:  (none) => spacedmonkey


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38741#comment:73>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 18:02:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 18:02:07 -0000
Subject: [wp-trac] [WordPress Trac] #54477: wp-cli vague: "Warning:
 Could not create directory."
In-Reply-To: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
References: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
Message-ID: <067.a186b9dc4a5325ad9483207de187658a@wordpress.org>

#54477: wp-cli vague: "Warning: Could not create directory."
-----------------------------+---------------------
 Reporter:  gunterer         |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  5.8
 Severity:  minor            |  Resolution:
 Keywords:  needs-patch      |     Focuses:
-----------------------------+---------------------

Comment (by SergeyBiryukov):

 Replying to [comment:2 n8finch]:
 > I'd like to work on this.

 Great! If you submit a GitHub PR and mention this ticket's URL in the
 description, it will automatically get linked here, see
 [https://make.wordpress.org/core/handbook/contribute/git/github-pull-
 requests-for-code-review/ GitHub Pull Requests for Code Review] for more
 details.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54477#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 18:31:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 18:31:07 -0000
Subject: [wp-trac] [WordPress Trac] #55392: Performance improvements to
 get_user_data_from_wp_global_styles
Message-ID: <056.57bae6a7df58c6d652d0202830909485@wordpress.org>

#55392: Performance improvements to get_user_data_from_wp_global_styles
-------------------------------+-----------------------------
 Reporter:  spacedmonkey       |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Posts, Post Types  |    Version:  5.9
 Severity:  normal             |   Keywords:  has-patch
  Focuses:  performance        |
-------------------------------+-----------------------------
 The `get_user_data_from_wp_global_styles` in the `WP_Theme_JSON_Resolver`
 class have a number of performance issues. These include by are not
 limited to.

 The following params should be passing the WP_Query object to increase
 performance.
 {{{#!php
 'ignore_sticky_posts'    => true,
 'suppress_filters'       => false,
 'update_post_meta_cache' => false,
 'update_post_term_cache' => false,
 'lazy_load_term_meta'    => false,
 'no_found_rows'          => true,
 'suppress_filters'       => false,
 }}}
 - Cache invalidation now happens when posts are not updated and not just
 on an hour.
 - Handle if `wp_insert_posts` returns a WP_Error.
 - Only return ids in query, to make query simplifier.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55392>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 19:08:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 19:08:29 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
Message-ID: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>

#55393: File name URL overflow the container in the media editor
--------------------------------+-----------------------------
 Reporter:  mitogh              |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  Media               |    Version:  5.9.2
 Severity:  normal              |   Keywords:
  Focuses:  ui, administration  |
--------------------------------+-----------------------------
 When the filename is large the container where the link of the filename is
 presented overflow the container in the **Edit Media** area.

 == Steps to replicate.

 1. Upload the attached image to the media library
 2. Click on **Edit** to open the edit media area.
 3. Observe the result.

 Dimensions where the issue is happening: 16843x1417

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 19:09:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 19:09:04 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.b0a2a31fbda3f24f2c2d2d58fe2b0422@wordpress.org>

#55393: File name URL overflow the container in the media editor
--------------------------+---------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  ui, administration
--------------------------+---------------------------------
Changes (by mitogh):

 * Attachment "2022-03-15_13-03.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 19:09:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 19:09:11 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.e83044ad30ef6514e714bd83febd9bcd@wordpress.org>

#55393: File name URL overflow the container in the media editor
--------------------------+---------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  ui, administration
--------------------------+---------------------------------
Changes (by mitogh):

 * Attachment "unsplash-image-Zw3n0QGXMxs6230e225cd4620.78824906.jpeg"
 added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 21:00:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 21:00:57 -0000
Subject: [wp-trac] [WordPress Trac] #55250: Avoid sending empty script
 translations
In-Reply-To: <051.c70c175c4cc365c6efdc917141cf72df@wordpress.org>
References: <051.c70c175c4cc365c6efdc917141cf72df@wordpress.org>
Message-ID: <066.2b364ca1f6c628283f879a259c17bd80@wordpress.org>

#55250: Avoid sending empty script translations
--------------------------+-----------------------
 Reporter:  jsnajdr       |       Owner:  ocean90
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:  6.0
Component:  I18N          |     Version:  5.0
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------
Changes (by coffee2code):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 This change appears to have unintended side effects, breaking JS on a lot
 of w.org sites for any core-related JS functionality. Seems like the `wp`
 JS object doesn't get instantiated. See
 https://meta.trac.wordpress.org/ticket/6195.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55250#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 21:56:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 21:56:13 -0000
Subject: [wp-trac] [WordPress Trac] #53218: Make apply_filters() variadic
In-Reply-To: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
References: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
Message-ID: <070.4b1c8ab727c7d7cafeffafd9f707e894@wordpress.org>

#53218: Make apply_filters() variadic
------------------------------------+---------------------
 Reporter:  johnbillion             |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  6.0
Component:  Plugins                 |     Version:  5.3
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch early commit  |     Focuses:
------------------------------------+---------------------
Changes (by davidbaumwald):

 * keywords:  has-patch early dev-feedback => has-patch early commit


Comment:

 Took a look at the PR the PR and it looks good.  Tested locally and ran
 unit tests.  I feel like it's good to go.  Spoke with @johnbillion, and
 he'll be committing this soon!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53218#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 22:02:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 22:02:45 -0000
Subject: [wp-trac] [WordPress Trac] #55394: Change the export from .xtml
Message-ID: <054.4ee67075a45407009b4a6e6506c008da@wordpress.org>

#55394: Change the export from .xtml
-----------------------------+-----------------------------
 Reporter:  brandonbr1       |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  General          |    Version:
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 so .xtml is older than .html which is the newest format  having it as
 .html making it look better and newer and some hosting only allow .html
 .xtml is old

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55394>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 22:47:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 22:47:33 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.890877fe359a14cfd6aa33ba75f70a81@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
--------------------------------------+------------------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------------

Comment (by peterwilsoncc):

 @pbearne Are you able to add some background to the description so the
 ticket can be properly considered, possibly for 6.0? My understanding is
 it's come from the performance team but additional information would help.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 22:50:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 22:50:06 -0000
Subject: [wp-trac] [WordPress Trac] #55394: Change the export from .xtml
In-Reply-To: <054.4ee67075a45407009b4a6e6506c008da@wordpress.org>
References: <054.4ee67075a45407009b4a6e6506c008da@wordpress.org>
Message-ID: <069.e2fc0caea0808c6812e4e971c3bdc800@wordpress.org>

#55394: Change the export from .xtml
-----------------------------+------------------------------
 Reporter:  brandonbr1       |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Export           |     Version:  2.1
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |     Focuses:
-----------------------------+------------------------------
Changes (by costdev):

 * keywords:  has-patch => has-patch close
 * type:  feature request => enhancement
 * version:   => 2.1
 * component:  General => Export


Comment:

 Hi @brandonbr1, welcome to Trac!

 While HTML is the modern markup format for display, the Export feature is
 not intended for display, but for exporting data that can be easily
 imported into another WordPress installation.

 The Export feature uses an XML file in WordPress eXtended RSS (WXR) format
 to achieve this.

 See the description on the `Tools > Export` screen:

 >When you click the button below WordPress will create an XML file for you
 to save to your computer.
 >
 >This format, which we call WordPress eXtended RSS or WXR, will contain
 your posts, pages, comments, custom fields, categories, and tags.
 >
 >Once you’ve saved the download file, you can **use the Import function in
 another WordPress installation to import the content from this site**.
 (emphasis mine)

 As the existing format is fit for this purpose, whereas HTML is not, I
 propose that we `close` this proposed `enhancement` as `wontfix`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55394#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 23:09:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 23:09:51 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in
 releases without a global theme auto-update setting renders installations
 insecure
In-Reply-To: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
References: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
Message-ID: <072.b8ff575149e66fbf4a689211ed2c586c@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
-------------------------------+-----------------------
 Reporter:  bertvandepoel      |       Owner:  pbiron
     Type:  enhancement        |      Status:  assigned
 Priority:  normal             |   Milestone:  6.0
Component:  Upgrade/Install    |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+-----------------------

Comment (by bertvandepoel):

 Sorry everyone for the slow response on my end. I work with WordPress as a
 volunteer at a student non-profit, and my actual job and other
 responsibilities got a bit in the way.

 Our point of view very much is what @pbiron his last post describes. Most
 of the student organisations we host don't have a dedicated webmaster, and
 often it's "the boyfriend of a friend of a member who is a mathematician"
 and they vaguely understand. Often for them it's enabling auto-updates
 everywhere (after us pressuring them about security) and then only going
 to the dashboard to add a new post or update a page every few
 weeks/months.

 I understand that there are plenty of intermediate users who edit their
 themes, so I'm not asking to make auto-updating mandatory or anything like
 that (as some seem to fear). Mostly it's the fact that when a new version
 of WordPress is installed through auto-updates, it doesn't make sense that
 it brings along a new component that doesn't receive auto-updates and that
 can cause security issues without the user even knowing.

 There are several ways to solve this issue:
 * Imply auto-updates for themes based on the auto-update status of other
 times
 * Presume auto-update when the installation of the theme was through an
 auto-update
 * Have a global setting for auto-updates (in general or for themes
 specifically)
 * Do not install themes when auto-updating
 * Have a setting on the settings page to toggle auto-updates for newly
 installed themes/plugins
 * Probably more

 I personally have a preference for the last option. This would make it
 much easier for those wishing to have a full auto-update experience to not
 have to worry about it, while they can still disable auto-updates for very
 specific components.

 In my view it's awesome that WordPress makes it possible for those with
 few technical skills to actually maintain a website, but this specific
 issue is a burden to them that I think could be eased.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55321#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 23:16:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 23:16:36 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.b74339f4210ffaf95b897f955b709ff5@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------

Comment (by westonruter):

 Replying to [comment:38 adamsilverstein]:
 > I noticed a bunch of small changes in the test files, can we leave those
 off to make the patch smaller or are those matching existing test paths?

 Those changes can be left out, yes. I mentioned them in my
 [https://core.trac.wordpress.org/ticket/53232#comment:24 above comment].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:44>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 23:21:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 23:21:09 -0000
Subject: [wp-trac] [WordPress Trac] #55321: Adding new themes in
 releases without a global theme auto-update setting renders installations
 insecure
In-Reply-To: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
References: <057.da81e632b9250d96cb5eb1ff77566c9b@wordpress.org>
Message-ID: <072.479f8f7004cc0a2ed7540bbee49d3773@wordpress.org>

#55321: Adding new themes in releases without a global theme auto-update setting
renders installations insecure
-------------------------------+-----------------------
 Reporter:  bertvandepoel      |       Owner:  pbiron
     Type:  enhancement        |      Status:  assigned
 Priority:  normal             |   Milestone:  6.0
Component:  Upgrade/Install    |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  ui
-------------------------------+-----------------------

Comment (by Otto42):

 So, maybe this idea: starting with the "twentytwentythree" theme, if and
 when, auto updates are on by default. In the core code, that checkbox is
 flipped on. It's not us "pushing" anything from .org, just that it's on by
 default. Next new default theme, auto updates unless you turn it off.

 I'm perfectly okay with that. Discuss. 👍

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55321#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 23:37:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 23:37:37 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.f6d287905d0bea2a32d18dc6288f5bdc@wordpress.org>

#55393: File name URL overflow the container in the media editor
--------------------------+--------------------------------------
 Reporter:  mitogh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Media         |     Version:  5.4
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  ui, css, administration
--------------------------+--------------------------------------
Changes (by costdev):

 * focuses:  ui, administration => ui, css, administration
 * version:  5.9.2 => 5.4
 * milestone:  Awaiting Review => 6.0


Comment:

 == Issue Reproduction Report

 === Env
 * Web Server: Apache (Linux)
 * WordPress: 5.9.2
 * Browser: Firefox 98.0.1
 * OS: Windows 10
 * Theme: TT1 Blocks
 * Plugins: None activated.

 === Steps to reproduce
 1. Navigate to `Media > Add New`.
 2. Upload a large image with a long filename.
 3. Navigate to `Media > Library`.
 4. Click the "List Mode" icon.
 5. Click the "Edit" link for the image you uploaded.

 To the right, the "Original image:" link shuold overflow the container.

 === Results
 1. Issue reproduced in Firefox. ✅
 2. Could not reproduce in Chrome (incl. Edge, Brave). ❌

 === Notes
 1. Introduced in [https://core.trac.wordpress.org/changeset/47202 47202].
 2. `word-break: break-word` is used on the bolded "File name:" text above
 the link. This also works when applied to the "Original image:" link,
 however I personally think that `word-break: break-all` looks cleaner.
 3. Adding `css` focus for input on preference between `break-word` and
 `break-all`.
 4. [https://core.trac.wordpress.org/changeset/47202 47202] introduced this
 link in the three locations below. The patch should be tested all three of
 these.
   - [https://core.trac.wordpress.org/browser/trunk/src/wp-includes/media-
 template.php#L442 wp-includes/media-template.php:442].
   - [https://core.trac.wordpress.org/browser/trunk/src/wp-includes/media-
 template.php#L665 wp-includes/media-template.php:665].
   - [https://core.trac.wordpress.org/browser/trunk/src/wp-
 admin/includes/media.php#L3485 wp-admin/includes/media.php:3485] - This is
 the one reported in this ticket.
 5. Milestoning for `6.0`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 23:39:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 23:39:17 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.5cb27cd47af2b6f0f6e01813624bd122@wordpress.org>

#55393: File name URL overflow the container in the media editor
-------------------------------------+-------------------------------------
 Reporter:  mitogh                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch good-first-  |     Focuses:  ui, css,
  bug                                |  administration
-------------------------------------+-------------------------------------
Changes (by costdev):

 * keywords:   => needs-patch good-first-bug


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 15 23:50:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 15 Mar 2022 23:50:21 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.fc102ff4dcb4c08ca515d5052e1a953c@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
--------------------------------------+------------------------------
 Reporter:  pbearne                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------------

Comment (by pbearne):

 Without this filter, you have to duplicate the regex code from WP core and
 create a function like this

 {{{#!php
 <?php
         public function filter_content_tags( $content, $context = null ) {
                 if ( null === $context ) {
                         $context = current_filter();
                 }

                 if ( ! preg_match_all( '/<(img|iframe)\s[^>]+>/',
 $content, $matches, PREG_SET_ORDER ) ) {
                         return $content;
                 }

                 // List of the unique `img` tags found in $content.
                 $images = array();

                 // List of the unique `iframe` tags found in $content.
                 $iframes = array();

                 foreach ( $matches as $match ) {
                         list( $tag, $tag_name ) = $match;

                         switch ( $tag_name ) {
                                 case 'img':
                                         if ( preg_match( '/wp-
 image-([0-9]+)/i', $tag, $class_id ) ) {
                                                 $attachment_id = absint(
 $class_id[1] );

                                                 if ( $attachment_id ) {
                                                         // If exactly the
 same image tag is used more than once, overwrite it.
                                                         // All identical
 tags will be replaced later with 'str_replace()'.
                                                         $images[ $tag ] =
 $attachment_id;
                                                         break;
                                                 }
                                         }
                                         $images[ $tag ] = 0;
                                         break;
                         }
                 }

                 // Reduce the array to unique attachment IDs.
                 $attachment_ids = array_unique( array_filter(
 array_values( $images ) ) );

                 if ( count( $attachment_ids ) > 1 ) {
                         /*
                          * Warm the object cache with post and meta
 information for all found
                          * images to avoid making individual database
 calls.
                          */
                         _prime_post_caches( $attachment_ids, false, true
 );
                 }

                 // Iterate through the matches in order of occurrence as
 it is relevant for whether or not to lazy-load.
                 foreach ( $matches as $match ) {
                         // Filter an image match.
                         if ( isset( $images[ $match[0] ] ) ) {
                                 $filtered_image = $match[0];
                                 $attachment_id  = $images[ $match[0] ];
                                 /**
                                  * Filters img tag that will be injected
 into the content.
                                  *
                                  * @param string $filtered_image the img
 tag with attributes being created that will
                                  *
 replace the source img tag in the content.
                                  * @param string $context Optional.
 Additional context to pass to the filters.
                                  *                        Defaults to
 `current_filter()` when not set.
                                  * @param int $attachment_id the ID of the
 image attachment.
                                  *
                                  * @since 1.0.0
                                  *
                                  */
                                 $filtered_image = apply_filters(
 'wp_dominant_color_img_tag_add_adjust', $filtered_image, $context,
 $attachment_id );

                                 if ( $filtered_image !== $match[0] ) {
                                         $content = str_replace( $match[0],
 $filtered_image, $content );
                                 }
                         }
                 }

                 return $content;
         }
 }}}

 In this example, I have added a filtered in the same logical place as the
 requested change and I simple hook into it to add the additional tags to
 the images

 which has to be maintained if core updates the regex it's unlikely that
 plugin authors might miss it

 I hope this makes sense

 Info: We are working on a patch to add an images dominant color
 placeholder to lazy loaded images

 Paul

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 00:22:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 00:22:07 -0000
Subject: [wp-trac] [WordPress Trac] #42474: bulk_edit_posts should honor
 the show_in_quick_edit property of taxonomies
In-Reply-To: <050.81ed0281315d9cf8d32d1d2e89f90090@wordpress.org>
References: <050.81ed0281315d9cf8d32d1d2e89f90090@wordpress.org>
Message-ID: <065.9c9132594dade77c9eb27ed4b7c796ad@wordpress.org>

#42474: bulk_edit_posts should honor the show_in_quick_edit property of taxonomies
-------------------------------------+------------------------------
 Reporter:  Chouby                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  performance
-------------------------------------+------------------------------
Changes (by costdev):

 * Attachment "42474.2.diff" added.

 Patch refreshed against trunk.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42474>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 00:42:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 00:42:11 -0000
Subject: [wp-trac] [WordPress Trac] #53218: Make apply_filters() variadic
In-Reply-To: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
References: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
Message-ID: <070.144b590ffa78d2ec366ee931dd9dcb78@wordpress.org>

#53218: Make apply_filters() variadic
------------------------------------+--------------------------
 Reporter:  johnbillion             |       Owner:  johnbillion
     Type:  enhancement             |      Status:  assigned
 Priority:  normal                  |   Milestone:  6.0
Component:  Plugins                 |     Version:  5.3
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch early commit  |     Focuses:
------------------------------------+--------------------------
Changes (by peterwilsoncc):

 * owner:  (none) => johnbillion
 * status:  new => assigned


Comment:

 Assigning to @johnbillion for commit.

 The PR includes `.github/workflows/phpbench-tests.yml`, are you intending
 to include that as part of the commit or is it simply for generating the
 reports during development?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53218#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 00:51:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 00:51:50 -0000
Subject: [wp-trac] [WordPress Trac] #53152: wp_set_object_terms
 ampersand in term name
In-Reply-To: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
References: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
Message-ID: <067.eeaac13392cd3b2bc1872728989b2c60@wordpress.org>

#53152: wp_set_object_terms ampersand in term name
-------------------------------------------------+-------------------------
 Reporter:  kapacity                             |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  5.7.1
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:
  feedback                                       |  administration
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 In [52921] `term_exists()` was modified to use `get_terms()` rather than
 make a database query directly.

 Searching by name is sanitized in `WP_Term_Query`.
 [https://github.com/WordPress/wordpress-
 develop/blob/4a9f5fe3be47914b3f2b30aaf863761335cf1ad2/src/wp-includes
 /class-wp-term-query.php#L536 (source code ref)]

 Is this still needed?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53152#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 01:08:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 01:08:30 -0000
Subject: [wp-trac] [WordPress Trac] #54477: wp-cli vague: "Warning:
 Could not create directory."
In-Reply-To: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
References: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
Message-ID: <067.b622fc7d1172e15c8fa703a7a47d4226@wordpress.org>

#54477: wp-cli vague: "Warning: Could not create directory."
----------------------------------------+---------------------
 Reporter:  gunterer                    |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Upgrade/Install             |     Version:  5.8
 Severity:  minor                       |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:
----------------------------------------+---------------------
Changes (by peterwilsoncc):

 * keywords:  needs-patch => needs-patch good-first-bug


Comment:

 Labeling this as a good first bug.

 Each appearance of error messages will probably need to change to (pseudo
 code):

 {{{#!php
 <?php
 sprintf(
   __( 'Could not create directory: %s.' ),
   $failed_directory
 );
 }}}

 I count five appearances.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54477#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 01:13:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 01:13:12 -0000
Subject: [wp-trac] [WordPress Trac] #49412: Store filesize media metadata
In-Reply-To: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
References: <048.d8ea2d9b63398331a26540a3bcf35c2c@wordpress.org>
Message-ID: <063.eaa4f2e2892494fcdb6575e12a88cb39@wordpress.org>

#49412: Store filesize media metadata
---------------------------------------------+---------------------------
 Reporter:  Cybr                             |       Owner:  spacedmonkey
     Type:  feature request                  |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------

Comment (by dlh):

 Apologies if I missed it, but I'm curious what the reason is for using the
 error suppression operator with `filesize()` in [52837]? The two calls to
 `filesize()` that were replaced with `wp_filesize()` didn't use it, and it
 seems to go against other efforts such as #24780.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49412#comment:55>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 01:31:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 01:31:22 -0000
Subject: [wp-trac] [WordPress Trac] #55395: Update Twemoji for 6.0
Message-ID: <051.0a151d8a79573dfce6475fdf6f6bf51f@wordpress.org>

#55395: Update Twemoji for 6.0
-------------------------+--------------------
 Reporter:  kraftbj      |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  6.0
Component:  Emoji        |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+--------------------
 Twitter has released Twemoji 14.0 (and 14.0.1). We can upgrade to include
 the new Emoji 14 fun.

 Previously #52852

 This release will include a number of new emoji:

     🫠 Melting Face
     🫢 Face with Open Eyes and Hand Over Mouth
     🫣 Face with Peeking Eye
     🫡 Saluting Face
     🫥 Dotted Line Face
     🫤 Face with Diagonal Mouth
     🥹 Face Holding Back Tears
     🫱 Rightwards Hand
     🫲 Leftwards Hand
     🫳 Palm Down Hand
     🫴 Palm Up Hand
     🫰 Hand with Index Finger and Thumb Crossed
     🫵 Index Pointing at the Viewer
     🫶 Heart Hands
     🫦 Biting Lip
     🫅 Person with Crown
     🫃 Pregnant Man
     🫄 Pregnant Person
     🧌 Troll
     🪸 Coral
     🪷 Lotus
     🪹 Empty Nest
     🪺 Nest with Eggs
     🫘 Beans
     🫗 Pouring Liquid
     🫙 Jar
     🛝 Playground Slide
     🛞 Wheel
     🛟 Ring Buoy
     🪬 Hamsa
     🪩 Mirror Ball
     🪫 Low Battery
     🩼 Crutch
     🩻 X-Ray
     🫧 Bubbles
     🪪 Identification Card
     🟰 Heavy Equals Sign
     🫱🏻 Rightwards Hand: Light Skin Tone
     🫱🏼 Rightwards Hand: Medium-Light Skin Tone
     🫱🏽 Rightwards Hand: Medium Skin Tone
     🫱🏾 Rightwards Hand: Medium-Dark Skin Tone
     🫱🏿 Rightwards Hand: Dark Skin Tone
     🫲🏻 Leftwards Hand: Light Skin Tone
     🫲🏼 Leftwards Hand: Medium-Light Skin Tone
     🫲🏽 Leftwards Hand: Medium Skin Tone
     🫲🏾 Leftwards Hand: Medium-Dark Skin Tone
     🫲🏿 Leftwards Hand: Dark Skin Tone
     🫳🏻 Palm Down Hand: Light Skin Tone
     🫳🏼 Palm Down Hand: Medium-Light Skin Tone
     🫳🏽 Palm Down Hand: Medium Skin Tone
     🫳🏾 Palm Down Hand: Medium-Dark Skin Tone
     🫳🏿 Palm Down Hand: Dark Skin Tone
     🫴🏻 Palm Up Hand: Light Skin Tone
     🫴🏼 Palm Up Hand: Medium-Light Skin Tone
     🫴🏽 Palm Up Hand: Medium Skin Tone
     🫴🏾 Palm Up Hand: Medium-Dark Skin Tone
     🫴🏿 Palm Up Hand: Dark Skin Tone
     🫰🏻 Hand with Index Finger and Thumb Crossed: Light Skin Tone
     🫰🏼 Hand with Index Finger and Thumb Crossed: Medium-Light Skin Tone
     🫰🏽 Hand with Index Finger and Thumb Crossed: Medium Skin Tone
     🫰🏾 Hand with Index Finger and Thumb Crossed: Medium-Dark Skin Tone
     🫰🏿 Hand with Index Finger and Thumb Crossed: Dark Skin Tone
     🫵🏻 Index Pointing at the Viewer: Light Skin Tone
     🫵🏼 Index Pointing at the Viewer: Medium-Light Skin Tone
     🫵🏽 Index Pointing at the Viewer: Medium Skin Tone
     🫵🏾 Index Pointing at the Viewer: Medium-Dark Skin Tone
     🫵🏿 Index Pointing at the Viewer: Dark Skin Tone
     🫶🏻 Heart Hands: Light Skin Tone
     🫶🏼 Heart Hands: Medium-Light Skin Tone
     🫶🏽 Heart Hands: Medium Skin Tone
     🫶🏾 Heart Hands: Medium-Dark Skin Tone
     🫶🏿 Heart Hands: Dark Skin Tone
     🤝🏻 Handshake: Light Skin Tone
     🤝🏼 Handshake: Medium-Light Skin Tone
     🤝🏽 Handshake: Medium Skin Tone
     🤝🏾 Handshake: Medium-Dark Skin Tone
     🤝🏿 Handshake: Dark Skin Tone
     🫱🏻‍🫲🏼 Handshake: Light Skin Tone, Medium-Light Skin Tone
     🫱🏻‍🫲🏽 Handshake: Light Skin Tone, Medium Skin Tone
     🫱🏻‍🫲🏾 Handshake: Light Skin Tone, Medium-Dark Skin Tone
     🫱🏻‍🫲🏿 Handshake: Light Skin Tone, Dark Skin Tone
     🫱🏼‍🫲🏻 Handshake: Medium-Light Skin Tone, Light Skin Tone
     🫱🏼‍🫲🏽 Handshake: Medium-Light Skin Tone, Medium Skin Tone
     🫱🏼‍🫲🏾 Handshake: Medium-Light Skin Tone, Medium-Dark Skin Tone
     🫱🏼‍🫲🏿 Handshake: Medium-Light Skin Tone, Dark Skin Tone
     🫱🏽‍🫲🏻 Handshake: Medium Skin Tone, Light Skin Tone
     🫱🏽‍🫲🏼 Handshake: Medium Skin Tone, Medium-Light Skin Tone
     🫱🏽‍🫲🏾 Handshake: Medium Skin Tone, Medium-Dark Skin Tone
     🫱🏽‍🫲🏿 Handshake: Medium Skin Tone, Dark Skin Tone
     🫱🏾‍🫲🏻 Handshake: Medium-Dark Skin Tone, Light Skin Tone
     🫱🏾‍🫲🏼 Handshake: Medium-Dark Skin Tone, Medium-Light Skin Tone
     🫱🏾‍🫲🏽 Handshake: Medium-Dark Skin Tone, Medium Skin Tone
     🫱🏾‍🫲🏿 Handshake: Medium-Dark Skin Tone, Dark Skin Tone
     🫱🏿‍🫲🏻 Handshake: Dark Skin Tone, Light Skin Tone
     🫱🏿‍🫲🏼 Handshake: Dark Skin Tone, Medium-Light Skin Tone
     🫱🏿‍🫲🏽 Handshake: Dark Skin Tone, Medium Skin Tone
     🫱🏿‍🫲🏾 Handshake: Dark Skin Tone, Medium-Dark Skin Tone
     🫅🏻 Person with Crown: Light Skin Tone
     🫅🏼 Person with Crown: Medium-Light Skin Tone
     🫅🏽 Person with Crown: Medium Skin Tone
     🫅🏾 Person with Crown: Medium-Dark Skin Tone
     🫅🏿 Person with Crown: Dark Skin Tone
     🫃🏻 Pregnant Man: Light Skin Tone
     🫃🏼 Pregnant Man: Medium-Light Skin Tone
     🫃🏽 Pregnant Man: Medium Skin Tone
     🫃🏾 Pregnant Man: Medium-Dark Skin Tone
     🫃🏿 Pregnant Man: Dark Skin Tone
     🫄🏻 Pregnant Person: Light Skin Tone
     🫄🏼 Pregnant Person: Medium-Light Skin Tone
     🫄🏽 Pregnant Person: Medium Skin Tone
     🫄🏾 Pregnant Person: Medium-Dark Skin Tone
     🫄🏿 Pregnant Person: Dark Skin Tone



 source: https://blog.emojipedia.org/twemoji-14-0-emoji-changelog/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55395>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 01:53:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 01:53:19 -0000
Subject: [wp-trac] [WordPress Trac] #55395: Update Twemoji for 6.0
In-Reply-To: <051.0a151d8a79573dfce6475fdf6f6bf51f@wordpress.org>
References: <051.0a151d8a79573dfce6475fdf6f6bf51f@wordpress.org>
Message-ID: <066.db2de3bb632c55d42039d52bf51d8d0d@wordpress.org>

#55395: Update Twemoji for 6.0
-------------------------+-----------------------
 Reporter:  kraftbj      |       Owner:  kraftbj
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  6.0
Component:  Emoji        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+-----------------------
Changes (by kraftbj):

 * keywords:  has-patch =>
 * owner:  (none) => kraftbj
 * status:  new => accepted


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55395#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 01:54:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 01:54:23 -0000
Subject: [wp-trac] [WordPress Trac] #53152: wp_set_object_terms
 ampersand in term name
In-Reply-To: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
References: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
Message-ID: <067.69a17b93c296251139b7416ab9f9806b@wordpress.org>

#53152: wp_set_object_terms ampersand in term name
--------------------------------------+-----------------------------
 Reporter:  kapacity                  |       Owner:  (none)
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  5.7.1
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  administration
--------------------------------------+-----------------------------
Changes (by costdev):

 * keywords:  has-patch has-unit-tests dev-feedback => has-patch has-unit-
     tests
 * status:  new => closed
 * resolution:   => fixed


Comment:

 Good call @peterwilsoncc!

 Just tested on `trunk` using the same steps as before, which were:

 1. Run `wp_set_object_terms()` to set the category as `foo & bar`.
 2. Manually rename `foo & bar` to `this & that`, keep the slug as `foo-
 bar`.
 3. Run `wp_set_object_terms()` to set the category as `this & that`.

 Before [52921]:
 - Fails on 3: `A term with the name provided already exists with this
 parent.`. ❌

 After [52921]:
 - Succeeds on 3: The category is set to `this & that` (slug: `foo-bar`).
 ✅

 -----

 - Fixed in [52921].
 - Related ticket: #36949.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53152#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 01:55:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 01:55:24 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.c99365cea9c1297ae18faa3958c071cf@wordpress.org>

#36949: Term exists should use get_terms internally
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  2.3
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note needs-testing commit                      |  performance
-------------------------------------------------+-------------------------

Comment (by costdev):

 Related ticket #53152 is fixed by [52921].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36949#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 02:42:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 02:42:28 -0000
Subject: [wp-trac] [WordPress Trac] #53152: wp_set_object_terms
 ampersand in term name
In-Reply-To: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
References: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
Message-ID: <067.974d4260f61c5f2f21b201788abc1505@wordpress.org>

#53152: wp_set_object_terms ampersand in term name
--------------------------------------+-----------------------------
 Reporter:  kapacity                  |       Owner:  (none)
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  5.7.1
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  administration
--------------------------------------+-----------------------------

Comment (by peterwilsoncc):

 Thanks @costdev,

 I'll commit the tests in your pull request as it was a use case that was
 earlier missed. I'll add them as part of #54725.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53152#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 02:51:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 02:51:26 -0000
Subject: [wp-trac] [WordPress Trac] #53152: wp_set_object_terms
 ampersand in term name
In-Reply-To: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
References: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
Message-ID: <067.c271075aacba75236aca19a3b07d62d5@wordpress.org>

#53152: wp_set_object_terms ampersand in term name
--------------------------------------+-----------------------------
 Reporter:  kapacity                  |       Owner:  (none)
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  5.7.1
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  administration
--------------------------------------+-----------------------------
Changes (by peterwilsoncc):

 * Attachment "53152.diff" added.

 Tests only following fix in other ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53152>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 03:04:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 03:04:54 -0000
Subject: [wp-trac] [WordPress Trac] #53152: wp_set_object_terms
 ampersand in term name
In-Reply-To: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
References: <052.602aedbaaba2a33e20402a65f04cf960@wordpress.org>
Message-ID: <067.a20e04119fb8a1e0511e864648a4784c@wordpress.org>

#53152: wp_set_object_terms ampersand in term name
--------------------------------------+-----------------------------
 Reporter:  kapacity                  |       Owner:  peterwilsoncc
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  5.7.1
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  administration
--------------------------------------+-----------------------------
Changes (by peterwilsoncc):

 * owner:  (none) => peterwilsoncc


Comment:

 In [changeset:"52938" 52938]:
 {{{
 #!CommitTicketReference repository="" revision="52938"
 Tests: Include special characters in term names for
 `wp_set_term_objects()`.

 Test `wp_set_term_objects()` using terms with special characters in the
 name, for example ampersand, bullet and other symbols and punctuation.

 Props kapacity, costdev.
 Fixes #53152.
 See #54725.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53152#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 03:04:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 03:04:54 -0000
Subject: [wp-trac] [WordPress Trac] #54725: Test tool and unit test
 improvements for 6.0
In-Reply-To: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
References: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
Message-ID: <073.096d6faefbde54d80ab50c7123acb6c2@wordpress.org>

#54725: Test tool and unit test improvements for 6.0
--------------------------------------+---------------------
 Reporter:  hellofromTonya            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by peterwilsoncc):

 In [changeset:"52938" 52938]:
 {{{
 #!CommitTicketReference repository="" revision="52938"
 Tests: Include special characters in term names for
 `wp_set_term_objects()`.

 Test `wp_set_term_objects()` using terms with special characters in the
 name, for example ampersand, bullet and other symbols and punctuation.

 Props kapacity, costdev.
 Fixes #53152.
 See #54725.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54725#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 05:52:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 05:52:25 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.6abfb5c68c0a139e5b8f2af24e290edd@wordpress.org>

#55393: File name URL overflow the container in the media editor
-------------------------------------+-------------------------------------
 Reporter:  mitogh                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch good-first-  |     Focuses:  ui, css,
  bug                                |  administration
-------------------------------------+-------------------------------------
Changes (by kapilpaul):

 * Attachment "77EA961B-74BC-4FDF-8ABD-0DDFE4CECC7C.jpg" added.

 Able to reproduce this issue in chrome

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 05:58:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 05:58:13 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.23f0be3bb5cb0c4a0f582bc1037efa6a@wordpress.org>

#55393: File name URL overflow the container in the media editor
-------------------------------------+-------------------------------------
 Reporter:  mitogh                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch good-first-  |     Focuses:  ui, css,
  bug                                |  administration
-------------------------------------+-------------------------------------
Changes (by alamgircsebd):

 * Attachment "55393.diff" added.

 Created patch

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 05:59:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 05:59:03 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.8ff4726385a49eb4ca25f739453e1bc4@wordpress.org>

#55393: File name URL overflow the container in the media editor
-------------------------------------+-------------------------------------
 Reporter:  mitogh                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4
 Severity:  normal                   |  Resolution:
 Keywords:  good-first-bug has-      |     Focuses:  ui, css,
  patch                              |  administration
-------------------------------------+-------------------------------------
Changes (by alamgircsebd):

 * keywords:  needs-patch good-first-bug => good-first-bug has-patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 06:01:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 06:01:38 -0000
Subject: [wp-trac] [WordPress Trac] #55396: Automatically add table prefix
 on WordPress setup
Message-ID: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>

#55396: Automatically add table prefix on WordPress setup
-------------------------+-----------------------------
 Reporter:  sruthi89     |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Security     |    Version:
 Severity:  normal       |   Keywords:  needs-patch
  Focuses:               |
-------------------------+-----------------------------
 The default table prefix easily allows a SQL Injection vulnerability.
 Currently, on WordPress setup also, the default prefix is auto-filled,
 which users may ignore.

 So on WordPress setup, the table prefix can be auto-filled with randomly
 generated characters, preferably four characters, which will solve this
 issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55396>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 06:07:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 06:07:32 -0000
Subject: [wp-trac] [WordPress Trac] #55396: Automatically add table
 prefix on WordPress setup
In-Reply-To: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
References: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
Message-ID: <067.ac858a2cac3568f6327011bef2e25625@wordpress.org>

#55396: Automatically add table prefix on WordPress setup
-------------------------+------------------------------
 Reporter:  sruthi89     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Security     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+------------------------------
Changes (by nithi22):

 * Attachment "55396.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55396>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 06:08:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 06:08:06 -0000
Subject: [wp-trac] [WordPress Trac] #55396: Automatically add table
 prefix on WordPress setup
In-Reply-To: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
References: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
Message-ID: <067.4aa2f9c1cef7671f2ada6b84ba7f5cbb@wordpress.org>

#55396: Automatically add table prefix on WordPress setup
-------------------------+------------------------------
 Reporter:  sruthi89     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Security     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+------------------------------
Changes (by nithi22):

 * Attachment "default-prefix.png" added.

 Default prefix

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55396>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 06:08:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 06:08:30 -0000
Subject: [wp-trac] [WordPress Trac] #55396: Automatically add table
 prefix on WordPress setup
In-Reply-To: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
References: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
Message-ID: <067.5e91c90572efa6e9ba7f743d87c4b354@wordpress.org>

#55396: Automatically add table prefix on WordPress setup
-------------------------+------------------------------
 Reporter:  sruthi89     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Security     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+------------------------------
Changes (by nithi22):

 * Attachment "random-prefix.png" added.

 Random prefix

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55396>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 06:09:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 06:09:57 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.5a17591444b5d2d2cdb9b22b214d694a@wordpress.org>

#55393: File name URL overflow the container in the media editor
-------------------------------------+-------------------------------------
 Reporter:  mitogh                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4
 Severity:  normal                   |  Resolution:
 Keywords:  good-first-bug has-      |     Focuses:  ui, css,
  patch                              |  administration
-------------------------------------+-------------------------------------
Changes (by kapilpaul):

 * Attachment "BD68941D-6224-4D10-8057-DE5E96C14714.psd" added.

 comparison between break-all vs break-word

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 06:10:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 06:10:07 -0000
Subject: [wp-trac] [WordPress Trac] #55396: Automatically add table
 prefix on WordPress setup
In-Reply-To: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
References: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
Message-ID: <067.56097a737fcf33e2311fee0dcb7b4e61@wordpress.org>

#55396: Automatically add table prefix on WordPress setup
---------------------------------------+------------------------------
 Reporter:  sruthi89                   |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:  Awaiting Review
Component:  Security                   |     Version:
 Severity:  normal                     |  Resolution:
 Keywords:  has-patch has-screenshots  |     Focuses:
---------------------------------------+------------------------------
Changes (by nithi22):

 * keywords:  needs-patch => has-patch has-screenshots


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55396#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 06:10:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 06:10:52 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.020ee440284b0883f46cc6d96c4c2232@wordpress.org>

#55393: File name URL overflow the container in the media editor
-------------------------------------+-------------------------------------
 Reporter:  mitogh                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4
 Severity:  normal                   |  Resolution:
 Keywords:  good-first-bug has-      |     Focuses:  ui, css,
  patch                              |  administration
-------------------------------------+-------------------------------------
Changes (by kapilpaul):

 * Attachment "BD68941D-6224-4D10-8057-DE5E96C14714.jpg" added.

 comparison between break-all vs break-word

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 06:12:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 06:12:50 -0000
Subject: [wp-trac] [WordPress Trac] #55393: File name URL overflow the
 container in the media editor
In-Reply-To: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
References: <050.9ca5df95a7a2d33381179c3bdbbd4aa5@wordpress.org>
Message-ID: <065.970c851308d699995fcafdd48b1f8e9b@wordpress.org>

#55393: File name URL overflow the container in the media editor
-------------------------------------+-------------------------------------
 Reporter:  mitogh                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4
 Severity:  normal                   |  Resolution:
 Keywords:  good-first-bug has-      |     Focuses:  ui, css,
  patch                              |  administration
-------------------------------------+-------------------------------------

Comment (by kapilpaul):

 @costdev I have added a image for **break-all** vs **break-word**

 **break-word** looks much cleaner to me.

 The “word-break: break-all;” will break the word at any character so the
 result is to difficulty in reading whereas “word-wrap: break-word;” will
 split word without making the word not break in the middle and wrap it
 into next line.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55393#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 07:04:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 07:04:34 -0000
Subject: [wp-trac] [WordPress Trac] #33156: Allow admin-ajax crawling
In-Reply-To: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
References: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
Message-ID: <070.10b33c3a2f9cc7c5d5a2fcee6966808e@wordpress.org>

#33156: Allow admin-ajax crawling
-----------------------------------+-----------------------------
 Reporter:  joostdevalk            |       Owner:  SergeyBiryukov
     Type:  enhancement            |      Status:  closed
 Priority:  normal                 |   Milestone:  4.4
Component:  General                |     Version:
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  2nd-opinion has-patch  |     Focuses:
-----------------------------------+-----------------------------

Comment (by KnowingArt_com):

 It seems like all the comments of concern were ignored.

 WordPress does not need permission from robots.txt to access itself. Take
 a step back and ask yourself why robots are "allowed" access to wp-admin
 /admin-ajax.php. It makes no sense, as if people forgot the role of
 robots.txt

 Robots.txt does not exist to manage all conceivable non-human
 interactions. It was originally created to save bandwidth, because one gig
 of transfer could cost over $10. If you simply crawled somebody's website
 back in 1999, they might threaten to sue you. Ask me how I know. Frankly,
 bandwidth and CPU are cheap enough now that robots.txt should be obsolete.

 After some decades and bazillions of pageviews, I have never used a
 robots.txt, because I don't want to discourage robots from enjoying my
 content. I don't know the exact version of WordPress this changed, but it
 seems WordPress decided to make robots.txt mandatory. In my expert
 opinion, that was a foolish decision.

 Respectful bots will avoid /wp-admin/ without being told. Disrespectful
 bots will do whatever they want. This auto-generated robots.txt is
 unnecessary, it just creates confusion and solves nothing.

 I'm told the WordPress philosophy is to make decisions instead of offering
 options. You don't make certain decisions without asking my permission.
 I'm drawing the line at robots.txt, I see this as a violation where
 WordPress is claiming ownership of something that does not belong to
 WordPress. (My server, my choice.) If I "allow" a robot onto my server,
 that is my decision to make as a system admin. Just because the average
 WordPress user is not very sophisticated with technology, that doesn't
 mean you can just take control of whatever you want, just because I gave
 you permission to auto-install upgrades.

 What's next? Are you going to try creeping into php.ini? Seriously, this
 should be a concern as larger companies are allowed to submit code to
 WordPress. If you're going to draw a line somewhere, might as well draw
 the line with robots.txt

 As for admin-ajax.php, whoever added that line should at least include a
 robots.readme to explain why robots.txt is mandatory, why it makes no
 sense, the relationship to wp-sitemap.xml, and include a link back to this
 URL, because it took me two days to follow the breadcrumbs back to this
 ticket. To say the least, this is not how I wanted to spend my week. And
 after digging into pages and pages of explanations, I'm still wondering
 why anyone would add admin-ajax.php to robots.txt

 "Since it's often used on front-end."

 Like I said, the front-end has nothing to do with robots.txt

 "What might be the downside of allowing admin-ajax.php to be crawled? Any
 chance of unwanted content appearing in SERPs?"

 BINGO! I'm having a problem with DuckDuckGo right now, it's listing /wp-
 admin/ as the #1 search result for my domain.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33156#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 07:32:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 07:32:58 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.9492e4ac435e6f19493982806b1fa797@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------

Comment (by isaumya):

 Hi @adamsilverstein,
 I looked at your PR in GitHub and just have one question. So, when these
 changes are applied will it also work on images added by Gutenberg blocks
 like the image block, gallery block, cover block, etc.
 The reason I am asking this is that I saw that the changes have been made
 in `media.php` under `wp-includes` and within `tests`. But did not see any
 changes in the Gutenberg files.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 08:10:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 08:10:56 -0000
Subject: [wp-trac] [WordPress Trac] #55397: errore visibile su
 http://affittovillasicilia.altervista.org
Message-ID: <063.88f5475fa71ad1039a616fac89889d33@wordpress.org>

#55397: errore visibile su http://affittovillasicilia.altervista.org
---------------------------------+-----------------------------
 Reporter:  affittovillasicilia  |      Owner:  (none)
     Type:  feature request      |     Status:  new
 Priority:  normal               |  Milestone:  Awaiting Review
Component:  General              |    Version:  5.9.2
 Severity:  normal               |   Keywords:  needs-refresh
  Focuses:                       |
---------------------------------+-----------------------------
 Warning: file_get_contents(http://affittovillasicilia.altervista.org/wp-
 content/plugins/poll-wp/tspoll_json/tsp-themes.json): failed to open
 stream: HTTP request failed! HTTP/1.0 403 Forbidden in
 /membri/affittovillasicilia/wp-content/plugins/poll-wp/includes/class-
 ts_poll.php on line 242

 Dettagli dell'errore
 ====================
 Un errore di E_COMPILE_ERROR è stato causato nella linea 218 del file
 /membri/affittovillasicilia/wp-content/plugins/poll-wp/index.php.
 Messaggio di errore: require_once(): Failed opening required
 '/membri/affittovillasicilia/wp-content/plugins/poll-wp/Includes/Total-
 Soft-Poll-Media.php' (include_path='/membri/affittovillasicilia/wp-
 content/plugins/kirki/:/membri/affittovillasicilia/wp-
 content/plugins/kirki/core:.:')

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55397>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 08:47:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 08:47:07 -0000
Subject: [wp-trac] [WordPress Trac] #55396: Automatically add table
 prefix on WordPress setup
In-Reply-To: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
References: <052.90d1a362a0624a9ee0f81bee54894615@wordpress.org>
Message-ID: <067.2def1d6a7643f53b74d6160d508122eb@wordpress.org>

#55396: Automatically add table prefix on WordPress setup
---------------------------------------+------------------------
 Reporter:  sruthi89                   |       Owner:  (none)
     Type:  enhancement                |      Status:  closed
 Priority:  normal                     |   Milestone:
Component:  Security                   |     Version:
 Severity:  normal                     |  Resolution:  duplicate
 Keywords:  has-patch has-screenshots  |     Focuses:
---------------------------------------+------------------------
Changes (by swissspidy):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 Duplicate of #11454.

 The table prefix is not a security feature.

 Its purpose is to make it easier to run multiple WP installations in a
 single database, e.g. on a shared hosting environment.

 Thus it does not make sense to randomize it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55396#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 09:17:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 09:17:29 -0000
Subject: [wp-trac] [WordPress Trac] #55390: Not able to choose Color
 picker in customizer when the blocks are added in widget
In-Reply-To: <051.4fe1d0e6f520345833d0438163c7fc6e@wordpress.org>
References: <051.4fe1d0e6f520345833d0438163c7fc6e@wordpress.org>
Message-ID: <066.02ad296a23317ddb24792ac63968e98f@wordpress.org>

#55390: Not able to choose Color picker in customizer when the blocks are added in
widget
-------------------------------------------------+-------------------------
 Reporter:  nileshc                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Editor                               |     Version:  5.9.2
 Severity:  major                                |  Resolution:
 Keywords:  needs-patch needs-testing needs-     |     Focuses:  ui,
  design-feedback has-screenshots needs-design   |  javascript, css
-------------------------------------------------+-------------------------

Comment (by nileshc):

 Hello,

 Is there any update on this issue?

 Just following up on the issue that is reported, are there any findings
 that you would like to share?

 Looking forward to your response, as soon as possible.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55390#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 09:26:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 09:26:44 -0000
Subject: [wp-trac] [WordPress Trac] #55397: errore visibile su
 http://affittovillasicilia.altervista.org
In-Reply-To: <063.88f5475fa71ad1039a616fac89889d33@wordpress.org>
References: <063.88f5475fa71ad1039a616fac89889d33@wordpress.org>
Message-ID: <078.210c8848340a2668d7687ff1b8d5bfcd@wordpress.org>

#55397: errore visibile su http://affittovillasicilia.altervista.org
---------------------------------+----------------------
 Reporter:  affittovillasicilia  |       Owner:  (none)
     Type:  defect (bug)         |      Status:  closed
 Priority:  normal               |   Milestone:
Component:  General              |     Version:  5.9.2
 Severity:  normal               |  Resolution:  invalid
 Keywords:                       |     Focuses:
---------------------------------+----------------------
Changes (by sabernhardt):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>
 * keywords:  needs-refresh =>
 * type:  feature request => defect (bug)


Old description:

> Warning: file_get_contents(http://affittovillasicilia.altervista.org/wp-
> content/plugins/poll-wp/tspoll_json/tsp-themes.json): failed to open
> stream: HTTP request failed! HTTP/1.0 403 Forbidden in
> /membri/affittovillasicilia/wp-content/plugins/poll-wp/includes/class-
> ts_poll.php on line 242
>
> Dettagli dell'errore
> ====================
> Un errore di E_COMPILE_ERROR è stato causato nella linea 218 del file
> /membri/affittovillasicilia/wp-content/plugins/poll-wp/index.php.
> Messaggio di errore: require_once(): Failed opening required
> '/membri/affittovillasicilia/wp-content/plugins/poll-wp/Includes/Total-
> Soft-Poll-Media.php' (include_path='/membri/affittovillasicilia/wp-
> content/plugins/kirki/:/membri/affittovillasicilia/wp-
> content/plugins/kirki/core:.:')

New description:

 {{{
 Warning: file_get_contents([...]/wp-content/plugins/poll-wp/tspoll_json
 /tsp-themes.json): failed to open stream: HTTP request failed! HTTP/1.0
 403 Forbidden in /[...]/wp-content/plugins/poll-wp/includes/class-
 ts_poll.php on line 242

 Dettagli dell'errore
 ====================
 Un errore di E_COMPILE_ERROR è stato causato nella linea 218 del file
 /[...]/wp-content/plugins/poll-wp/index.php. Messaggio di errore:
 require_once(): Failed opening required '/[...]/wp-content/plugins/poll-
 wp/Includes/Total-Soft-Poll-Media.php' (include_path='/[...]/wp-
 content/plugins/kirki/:/[...]/wp-content/plugins/kirki/core:.:')
 }}}

--

Comment:

 Hi and welcome to Trac! Please use the support forums for help with
 individual sites.

 A similar report was opened on the TS Poll forum, so the problem is likely
 related to that plugin:
 https://wordpress.org/support/topic/plugin-doesnt-work-since-1-7-0/

 If that is not the same problem, you could try using one of these forums:
 [https://wordpress.org/support/plugin/poll-wp/ TS Poll support]
 [https://wordpress.org/support/plugin/kirki/ Kirki support]
 [https://it.wordpress.org/support/ Supporto per WordPress]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55397#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 10:21:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 10:21:28 -0000
Subject: [wp-trac] [WordPress Trac] #33156: Allow admin-ajax crawling
In-Reply-To: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
References: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
Message-ID: <070.d7a2160773b83e0d2c6efa82a6728477@wordpress.org>

#33156: Allow admin-ajax crawling
-----------------------------------+-----------------------------
 Reporter:  joostdevalk            |       Owner:  SergeyBiryukov
     Type:  enhancement            |      Status:  closed
 Priority:  normal                 |   Milestone:  4.4
Component:  General                |     Version:
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  2nd-opinion has-patch  |     Focuses:
-----------------------------------+-----------------------------

Comment (by nickdageekuk):

 Replying to [comment:22 KnowingArt_com]:
 > It seems like all the comments of concern were ignored.

 I would tend to agree considering that AJAX itself is a problem

 Known SQL injection exploit in AJAX see [https://www.exploit-
 db.com/exploits/48475]

 # Exploit Title: WordPress Plugin Ajax Load More 5.3.1 - '#1'
 Authenticated SQL Injection
 # Exploit Author: SunCSR (Sun* Cyber Security Research) - Nguyen Khang
 # Google Dork: N/A
 # Date: 2020-05-18
 # Vendor Homepage: https://connekthq.com/plugins/ajax-load-more/
 # Software Link: https://vi.wordpress.org/plugins/ajax-load-more/
 # Version: <= 5.3.1
 # Tested on: Ubuntu 18.04

 Description:
 A blind SQL injection vulnerability is present in Ajax load more.
 $wpdb->get_var("SELECT repeaterDefault FROM " . $table_name . " WHERE name
 = '$n'");

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33156#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 10:48:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 10:48:32 -0000
Subject: [wp-trac] [WordPress Trac] #55398: Spacer Block don't show
Message-ID: <050.ec3f17ac143069c8b351cebc58890ef9@wordpress.org>

#55398: Spacer Block don't show
--------------------------+-----------------------------
 Reporter:  ramo03        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hello.
 I have problem when i writing my article in WordPress 5.9.2 , tool Spacer
 Block don't show in the article page, so if you can help me please.
 my greetings.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55398>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 10:58:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 10:58:31 -0000
Subject: [wp-trac] [WordPress Trac] #55399: esc_xml() removes valid XML
 input ( input that is empty() )
Message-ID: <054.6f1ed67beb6072490bacc7335e1248d1@wordpress.org>

#55399: esc_xml() removes valid XML input ( input that is empty() )
--------------------------+-----------------------------
 Reporter:  rumpel2116    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.5
 Severity:  normal        |   Keywords:  needs-patch
  Focuses:                |
--------------------------+-----------------------------
 The with #50117 introduced function `esc_xml()` escapes/deletes some valid
 input: Input that results true if passed to `empty()`.
 `esc_xml('0')` and similar returns an empty string instead of returning
 `'0'` while `'0'` is perfectly XML-safe.

 There are two issues checking for empty regex groups that use PHPs
 `empty()`:
 {{{
 #!php
 $safe_text = (string) preg_replace_callback(
         $regex,
         static function( $matches ) {
                 if ( ! $matches[0] ) {
                         return '';
                 }

                 if ( ! empty( $matches['non_cdata'] ) ) {
                         // escape HTML entities in the non-CDATA Section.
                         return _wp_specialchars( $matches['non_cdata'],
 ENT_XML1 );
                 }

                 // Return the CDATA Section unchanged, escape HTML
 entities in the rest.
                 return _wp_specialchars(
 $matches['non_cdata_followed_by_cdata'], ENT_XML1 ) . $matches['cdata'];
         },
         $safe_text
 );
 }}}



 The first check is to skip further processing of empty strings I believe.
 Can easily be replaced by `! isset( $matches[0] )` as the group is not set
 if empty.

 The second check validates if there is no `non_cdata` (without any cdata),
 but uses `! empty()` explicitly. Same solution, using `! isset(
 $matches['non_cdata'] )` covers the case, if no `non_cdata` is captured,
 the regex-group is not set.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55399>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 11:32:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 11:32:26 -0000
Subject: [wp-trac] [WordPress Trac] #55398: Spacer Block don't show
In-Reply-To: <050.ec3f17ac143069c8b351cebc58890ef9@wordpress.org>
References: <050.ec3f17ac143069c8b351cebc58890ef9@wordpress.org>
Message-ID: <065.8a3f628e7dca0c7d17a44290bbd5e538@wordpress.org>

#55398: Spacer Block don't show
--------------------------+------------------------------
 Reporter:  ramo03        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+------------------------------
Changes (by azouamauriac):

 * keywords:   => close


Comment:

 Hi @ramo03, welcome to WordPress Trac!

 Sorry to hear that you're having trouble with your website.

 Trac is for the development of WordPress Core rather than providing
 WordPress support. You can get some help from the folks over on
 [https://wordpress.org/support/forums/ the support forums].

 If after that it's appear that your issue is related to WordPress core
 please get back us and let us know, and please provide enough of details
 that will help us to reproduce it.

 Best of luck!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55398#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 11:32:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 11:32:54 -0000
Subject: [wp-trac] [WordPress Trac] #55399: esc_xml() removes valid XML
 input ( input that is empty() )
In-Reply-To: <054.6f1ed67beb6072490bacc7335e1248d1@wordpress.org>
References: <054.6f1ed67beb6072490bacc7335e1248d1@wordpress.org>
Message-ID: <069.9323ea16fbe5aa5afba5e708d3e732fa@wordpress.org>

#55399: esc_xml() removes valid XML input ( input that is empty() )
--------------------------+---------------------
 Reporter:  rumpel2116    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Formatting    |     Version:  5.5
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------
Changes (by swissspidy):

 * component:  General => Formatting
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55399#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 11:35:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 11:35:13 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2334353=3A_redirect=5F?=
 =?utf-8?q?canonical=28=29_=E2=80=93_Undefined_indexes_=27host=27_and_=27s?=
 =?utf-8?q?cheme=27?=
In-Reply-To: <052.d2b94e26c7f4f17a6607f9d4a254dd3b@wordpress.org>
References: <052.d2b94e26c7f4f17a6607f9d4a254dd3b@wordpress.org>
Message-ID: <067.b7954140073d7e12bdc25e36fe19f1e0@wordpress.org>

#34353: redirect_canonical() – Undefined indexes 'host' and 'scheme'
------------------------------------------+-----------------------------
 Reporter:  theamila                      |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  reopened
 Priority:  normal                        |   Milestone:  Future Release
Component:  Canonical                     |     Version:  4.3.1
 Severity:  normal                        |  Resolution:
 Keywords:  needs-patch needs-unit-tests  |     Focuses:
------------------------------------------+-----------------------------

Comment (by stcn):

 Hi,

 I'm also having this issue :


 {{{
 [16-Mar-2022 04:02:38 UTC] PHP Warning:  Undefined array key "host" in
 /public_html/wp-includes/canonical.php on line 687
 [16-Mar-2022 04:02:38 UTC] PHP Warning:  Undefined array key "host" in
 /public_html/wp-includes/canonical.php on line 696
 [16-Mar-2022 04:02:38 UTC] PHP Warning:  Undefined array key "scheme" in
 /public_html/wp-includes/canonical.php on line 720
 }}}


 what is the problem? how can it be solved?

 Thanks!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/34353#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 11:39:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 11:39:53 -0000
Subject: [wp-trac] [WordPress Trac] #55400: PHP Warning: Attempt to read
 property "post_type"
Message-ID: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>

#55400: PHP Warning:  Attempt to read property "post_type"
--------------------------+-----------------------------
 Reporter:  stcn          |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hi,

  I  get this error:
 {{{
 PHP Warning:  Attempt to read property "post_type" on null in /public_html
 /wp-includes/class-wp-query.php on line 4273
 }}}

 what is the problem? how can it be solved?

 Thanks!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55400>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 11:46:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 11:46:52 -0000
Subject: [wp-trac] [WordPress Trac] #55400: PHP Warning: Attempt to read
 property "post_type"
In-Reply-To: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
References: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
Message-ID: <063.a1fe6b707f17db017e3a132298f8663c@wordpress.org>

#55400: PHP Warning:  Attempt to read property "post_type"
-------------------------------+------------------------------
 Reporter:  stcn               |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  General            |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by audrasjb):

 * keywords:   => reporter-feedback


Comment:

 Hello and welcome to WordPress Core Trac @stcn,

 Could you please provide more information to help contextualize the issue?
 Where does it happen? Could you provide a screenshot? Any particular
 action on you side? Does it occurs with a default theme and no plugin
 activated?

 Thank you

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55400#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 11:58:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 11:58:24 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.4b0042c4687fc53a12c568dd71835415@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
--------------------------------------+-----------------------
 Reporter:  Presskopp                 |       Owner:  audrasjb
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:  6.0
Component:  Administration            |     Version:  4.7
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  ui-copy
--------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests needs-refresh => has-patch has-unit-
     tests


Comment:

 @JeffPaul PR refreshed against trunk. It is available for final review :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 12:18:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 12:18:36 -0000
Subject: [wp-trac] [WordPress Trac] #55400: PHP Warning: Attempt to read
 property "post_type"
In-Reply-To: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
References: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
Message-ID: <063.58b0449022cd2f59fb12c5a9fa7a87a5@wordpress.org>

#55400: PHP Warning:  Attempt to read property "post_type"
-------------------------------------------+------------------------------
 Reporter:  stcn                           |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  new
 Priority:  normal                         |   Milestone:  Awaiting Review
Component:  General                        |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:  reporter-feedback needs-patch  |     Focuses:
-------------------------------------------+------------------------------
Changes (by azouamauriac):

 * keywords:  reporter-feedback => reporter-feedback needs-patch


Comment:

 Hi there and welcome to trac!

 It seems like we need some if statement in ''WP_Query::is_singular'' at
 line 4292 since ''WP_Query::get_queried_object'' can returns ''null'' I
 guess it was caused that.

 [[Image(https://prnt.sc/YvmBGT785JaJ)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55400#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 12:20:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 12:20:33 -0000
Subject: [wp-trac] [WordPress Trac] #55394: Change the export from .xml
 (was: Change the export from .xtml)
In-Reply-To: <054.4ee67075a45407009b4a6e6506c008da@wordpress.org>
References: <054.4ee67075a45407009b4a6e6506c008da@wordpress.org>
Message-ID: <069.4bb38fceeabead9b95c6f03ed5329d5d@wordpress.org>

#55394: Change the export from .xml
-----------------------------+----------------------
 Reporter:  brandonbr1       |       Owner:  (none)
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Export           |     Version:  2.1
 Severity:  normal           |  Resolution:  invalid
 Keywords:  has-patch close  |     Focuses:
-----------------------------+----------------------
Changes (by johnbillion):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Old description:

> so .xtml is older than .html which is the newest format  having it as
> .html making it look better and newer and some hosting only allow .html
> .xtml is old

New description:

 so .xml is older than .html which is the newest format  having it as .html
 making it look better and newer and some hosting only allow .html .xml is
 old

--

Comment:

 Thanks for the report @brandonbr1 and welcome to WordPress Trac.

 As Colin points out above this is not an HTML file but an XML file,
 therefore the extension is correct.

 Cheers!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55394#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 12:23:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 12:23:51 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.8ff06f81bac385366291b7f93969a900@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
---------------------------------------------------+-----------------------
 Reporter:  Presskopp                              |       Owner:  audrasjb
     Type:  enhancement                            |      Status:  accepted
 Priority:  normal                                 |   Milestone:  6.0
Component:  Administration                         |     Version:  4.7
 Severity:  normal                                 |  Resolution:
 Keywords:  has-patch has-unit-tests dev-feedback  |     Focuses:  ui-copy
---------------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests dev-
     feedback


Comment:

 Pinging:
 - @Presskopp as you opened the ticket
 - @JeffPaul as you previously reviewed the patch
 - @SergeyBiryukov for a second core committer review

 If everyone is fine with the current PR and since the current PR passes
 unit tests, I'm up to commit this now, so it could ship `early` in the
 release cycle :)

 PR: https://github.com/WordPress/wordpress-develop/pull/1840

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:42>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 12:25:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 12:25:19 -0000
Subject: [wp-trac] [WordPress Trac] #55400: PHP Warning: Attempt to read
 property "post_type"
In-Reply-To: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
References: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
Message-ID: <063.5064beabc0c2935f7cb41aec33081998@wordpress.org>

#55400: PHP Warning:  Attempt to read property "post_type"
--------------------------+------------------------------
 Reporter:  stcn          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by audrasjb):

 * keywords:  reporter-feedback needs-patch => needs-patch


Comment:

 Oh nice catch @azouamauriac. Wanna propose a patch for this issue?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55400#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 12:33:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 12:33:17 -0000
Subject: [wp-trac] [WordPress Trac] #55400: PHP Warning: Attempt to read
 property "post_type"
In-Reply-To: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
References: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
Message-ID: <063.d4dba32a9b9e2db9f763c2824054c416@wordpress.org>

#55400: PHP Warning:  Attempt to read property "post_type"
--------------------------+------------------------------
 Reporter:  stcn          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by azouamauriac):

 * Attachment "55400.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55400>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 12:40:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 12:40:23 -0000
Subject: [wp-trac] [WordPress Trac] #55400: PHP Warning: Attempt to read
 property "post_type"
In-Reply-To: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
References: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
Message-ID: <063.6cb40f292b1ffca44b7c6d733571d26d@wordpress.org>

#55400: PHP Warning:  Attempt to read property "post_type"
--------------------------+------------------------------
 Reporter:  stcn          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------
Changes (by azouamauriac):

 * keywords:  needs-patch => has-patch


Comment:

 Replying to [comment:3 audrasjb]:
 > Oh nice catch @azouamauriac. Wanna propose a patch for this issue?

 Done! Please let me know if it's fit for you.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55400#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 12:41:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 12:41:54 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.daa7e6b03b185d68a5c05251519d1523@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
---------------------------------------------------+-----------------------
 Reporter:  Presskopp                              |       Owner:  audrasjb
     Type:  enhancement                            |      Status:  accepted
 Priority:  normal                                 |   Milestone:  6.0
Component:  Administration                         |     Version:  4.7
 Severity:  normal                                 |  Resolution:
 Keywords:  has-patch has-unit-tests dev-feedback  |     Focuses:  ui-copy
---------------------------------------------------+-----------------------

Comment (by Presskopp):

 not sure of the can't => can not conversion, reading
 [https://core.trac.wordpress.org/ticket/38913#comment:35 #35]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:43>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 12:48:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 12:48:32 -0000
Subject: [wp-trac] [WordPress Trac] #55400: PHP Warning: Attempt to read
 property "post_type"
In-Reply-To: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
References: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
Message-ID: <063.7627e4b720ca48ac4e836570844968ab@wordpress.org>

#55400: PHP Warning:  Attempt to read property "post_type"
--------------------------+------------------------------
 Reporter:  stcn          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------

Comment (by azouamauriac):

 Some History: [15531]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55400#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 13:16:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 13:16:08 -0000
Subject: [wp-trac] [WordPress Trac] #55399: esc_xml() removes valid XML
 input ( input that is empty() )
In-Reply-To: <054.6f1ed67beb6072490bacc7335e1248d1@wordpress.org>
References: <054.6f1ed67beb6072490bacc7335e1248d1@wordpress.org>
Message-ID: <069.2c4aa1e2e45161941b6e38c2d2ba41b0@wordpress.org>

#55399: esc_xml() removes valid XML input ( input that is empty() )
--------------------------+---------------------
 Reporter:  rumpel2116    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Formatting    |     Version:  5.5
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------

Comment (by azouamauriac):

 Hello there welcome to trac, thanks for the report and patch! I have
 tested it and it works. No objection!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55399#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 13:38:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 13:38:38 -0000
Subject: [wp-trac] [WordPress Trac] #33156: Allow admin-ajax crawling
In-Reply-To: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
References: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
Message-ID: <070.c50a034a9a3b8b7e54392eb225c02f3d@wordpress.org>

#33156: Allow admin-ajax crawling
-----------------------------------+-----------------------------
 Reporter:  joostdevalk            |       Owner:  SergeyBiryukov
     Type:  enhancement            |      Status:  closed
 Priority:  normal                 |   Milestone:  4.4
Component:  General                |     Version:
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  2nd-opinion has-patch  |     Focuses:
-----------------------------------+-----------------------------

Comment (by dmchale):

 Replying to [comment:22 KnowingArt_com]:
 > I'm told the WordPress philosophy is to make decisions instead of
 offering options. You don't make certain decisions without asking my
 permission.

 In fairness, that's exactly what it means to make a decision and not offer
 an option.

 That said, this ticket was discussing the default behavior of the
 robots.txt file. You can short-circuit what WordPress does out of the box
 in one of two ways.

 1. Create a physical robots.txt file on your server. If WordPress detects
 a physical file at the web root, it will not add to / remove from / modify
 that file in any way (this includes any plugins that dynamically modify
 the robots.txt file as well)

 2. Use the `robots_txt` filter to modify the contents of the WordPress
 defaults https://developer.wordpress.org/reference/hooks/robots_txt/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33156#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 13:49:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 13:49:47 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.d683dbef24cfec5ac765b598ec7b5090@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
---------------------------------------------------+-----------------------
 Reporter:  Presskopp                              |       Owner:  audrasjb
     Type:  enhancement                            |      Status:  accepted
 Priority:  normal                                 |   Milestone:  6.0
Component:  Administration                         |     Version:  4.7
 Severity:  normal                                 |  Resolution:
 Keywords:  has-patch has-unit-tests dev-feedback  |     Focuses:  ui-copy
---------------------------------------------------+-----------------------

Comment (by JeffPaul):

 Interesting callout as I had missed Sergey's comment in #35, but yeah
 looks like maybe we should change `can't` to `cannot`?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:44>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 13:50:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 13:50:41 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.2b3c2008fba33335ac56c95bd58f8ac0@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
---------------------------------------------------+-----------------------
 Reporter:  Presskopp                              |       Owner:  audrasjb
     Type:  enhancement                            |      Status:  accepted
 Priority:  normal                                 |   Milestone:  6.0
Component:  Administration                         |     Version:  4.7
 Severity:  normal                                 |  Resolution:
 Keywords:  has-patch has-unit-tests dev-feedback  |     Focuses:  ui-copy
---------------------------------------------------+-----------------------

Comment (by JeffPaul):

 @audrasjb if you want, I can add another commit to your PR to make the
 change to `cannot` and let you handle review there?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:45>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 14:26:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 14:26:25 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.cccbd7344c6aaf3d968f0db31006f959@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------

Comment (by adamsilverstein):

 > So, when these changes are applied will it also work on images added by
 Gutenberg blocks like the image block, gallery block, cover block, etc.

 @isaumya yes - these changes are applied via a content filter so this
 should work for almost every image in the content, regardless of how you
 added it (Gutenberg, classic editor, etc). The only exception would be
 sites that disable "the_content" filtering.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:47>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 15:30:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 15:30:17 -0000
Subject: [wp-trac] [WordPress Trac] #55244: Non-editable title.
In-Reply-To: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
References: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
Message-ID: <066.f2777c4b101d7b32d201b1c5f03e970c@wordpress.org>

#55244: Non-editable title.
--------------------------+----------------------------------------
 Reporter:  krilike       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility, javascript
--------------------------+----------------------------------------

Comment (by afercia):

 I can reproduce this issue on latest trunk. Couldn't reproduce with the
 latest Gutenberg plugin activated though, so maybe it has been fixed in
 Gutenberg.

 See attached GIF:
 - Initially, the post title has a `contenteditable` HTML attribute, which
 makes it editable.
 - After pressing Ctrl (or Cmd on mac) + A, the `contenteditable` gets
 removed and it's never restored, not even when canceling the selection.
 - At that point, the post title stays non-editable

 Worth noting this issue has also been reported on the Gutenberg GitHub
 repository, see https://github.com/WordPress/gutenberg/issues/39292

 It would be good to ask the Editor team to confirm this issue has been
 fixed in Gutenberg and maybe consider to backport the fix as soon as
 possible.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55244#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 15:31:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 15:31:06 -0000
Subject: [wp-trac] [WordPress Trac] #55244: Non-editable title.
In-Reply-To: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
References: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
Message-ID: <066.0486bc5a42d60b1683d6da02e183433f@wordpress.org>

#55244: Non-editable title.
--------------------------+----------------------------------------
 Reporter:  krilike       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility, javascript
--------------------------+----------------------------------------
Changes (by afercia):

 * Attachment "title-not-editable.gif" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55244>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 15:37:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 15:37:16 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.4a4ab11f913157263dc74bc87dca9b4b@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
---------------------------------------------------+-----------------------
 Reporter:  Presskopp                              |       Owner:  audrasjb
     Type:  enhancement                            |      Status:  accepted
 Priority:  normal                                 |   Milestone:  6.0
Component:  Administration                         |     Version:  4.7
 Severity:  normal                                 |  Resolution:
 Keywords:  has-patch has-unit-tests dev-feedback  |     Focuses:  ui-copy
---------------------------------------------------+-----------------------

Comment (by audrasjb):

 @JeffPaul yes sure, it would be very appreciated, thank you :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 15:48:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 15:48:12 -0000
Subject: [wp-trac] [WordPress Trac] #55401: Subpages of a web page can be
 called twice
Message-ID: <055.3f14c28994df00d9eeb59ba7b17bab48@wordpress.org>

#55401: Subpages of a web page can be called twice
--------------------------+-------------------------------------
 Reporter:  manuel10503   |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Permalinks    |    Version:  5.9.2
 Severity:  major         |   Keywords:  needs-patch 2nd-opinion
  Focuses:                |
--------------------------+-------------------------------------
 Subpages of any website created with WordPress can be accessed twice.

 If you add a /0/ to the end of the regular URL, the same page can be
 called again.
 This page with /0/ at the end of the URL will also be indexed in Google.

 Example:
 https://wordpress.org/news/2022/03/wordpress-5-9-2-security-maintenance-
 release/

 https://wordpress.org/news/2022/03/wordpress-5-9-2-security-maintenance-
 release/0/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55401>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 15:59:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 15:59:21 -0000
Subject: [wp-trac] [WordPress Trac] #55400: PHP Warning: Attempt to read
 property "post_type"
In-Reply-To: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
References: <048.a26bb2a724092aaa95921fef7b357630@wordpress.org>
Message-ID: <063.731bb7a5f0725a4ca076a11dfee3e39a@wordpress.org>

#55400: PHP Warning:  Attempt to read property "post_type"
--------------------------+------------------------
 Reporter:  stcn          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Query         |     Version:
 Severity:  normal        |  Resolution:  duplicate
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------
Changes (by SergeyBiryukov):

 * status:  new => closed
 * resolution:   => duplicate
 * component:  General => Query
 * milestone:  Awaiting Review =>


Comment:

 Hi there, welcome to WordPress Trac!

 Thanks for the report and the patch, we're already tracking this issue in
 #29660.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55400#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:13:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:13:21 -0000
Subject: [wp-trac] [WordPress Trac] #55401: Subpages of a web page can
 be called twice
In-Reply-To: <055.3f14c28994df00d9eeb59ba7b17bab48@wordpress.org>
References: <055.3f14c28994df00d9eeb59ba7b17bab48@wordpress.org>
Message-ID: <070.1d427cbf60f322b5bf222b69f23b3a27@wordpress.org>

#55401: Subpages of a web page can be called twice
--------------------------+------------------------------
 Reporter:  manuel10503   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Permalinks    |     Version:  5.9.2
 Severity:  major         |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by SergeyBiryukov):

 * keywords:  needs-patch 2nd-opinion => needs-patch


Comment:

 Hi there, welcome to WordPress Trac! Thanks for the report.

 Good catch, a similar issue was fixed in [47727] / #40773 for URLs ending
 with `/2/` or `/3/` (unless they are intended to be paged). The redirect
 for `/1/` also works as expected, but apparently not for `/0/`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55401#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:14:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:14:50 -0000
Subject: [wp-trac] [WordPress Trac] #50061: Image_meta original_image as
 valid image_size
In-Reply-To: <051.fcac2d537ccf7d42b6074e7bff75a5fd@wordpress.org>
References: <051.fcac2d537ccf7d42b6074e7bff75a5fd@wordpress.org>
Message-ID: <066.0315373863fe28230906bd540cd6ec33@wordpress.org>

#50061: Image_meta original_image as valid image_size
--------------------------+-----------------------
 Reporter:  tomcent       |       Owner:  antpb
     Type:  enhancement   |      Status:  accepted
 Priority:  normal        |   Milestone:  6.0
Component:  Media         |     Version:  5.3
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |     Focuses:
--------------------------+-----------------------
Changes (by antpb):

 * owner:  (none) => antpb
 * status:  new => accepted
 * milestone:  Awaiting Review => 6.0


Comment:

 Great catch, I could see how this happens. Mentioned in the Media meeting
 @adamsilverstein  said it might be beneficial for a new separate function
 to get those original source images that way current behavior works while
 giving the data that you need.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50061#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:20:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:20:19 -0000
Subject: [wp-trac] [WordPress Trac] #50210: Image upload stuck - Upload
 files
In-Reply-To: <050.9838e3c419ff84a7df08d35109f35836@wordpress.org>
References: <050.9838e3c419ff84a7df08d35109f35836@wordpress.org>
Message-ID: <065.025a1b368068f95055dff7052dd465ac@wordpress.org>

#50210: Image upload stuck - Upload files
-------------------------------+------------------------------
 Reporter:  bustel             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:  5.4.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by antpb):

 * keywords:   => reporter-feedback


Comment:

 Hey @bustel ! Thanks for your first ticket! this has been routed to the
 Media team and we started discussing this issue in a meeting and were
 having a hard time reproducing the issue.

 Would it be possible for you to share error logs from your site or console
 errors you are seeing in the browser?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50210#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:23:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:23:30 -0000
Subject: [wp-trac] [WordPress Trac] #55402: Check for and retain custom
 indexes on version upgrades
Message-ID: <053.8d67039bf3e84faa0334edff5b0f930e@wordpress.org>

#55402: Check for and retain custom indexes on version upgrades
-------------------------+-----------------------------
 Reporter:  amykamala    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Database     |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 Currently Core database schema provides proper indexes for most tables and
 columns, however some core tables have columns that are not natively
 indexed, such as the _usermeta meta_value column. For larger enterprise
 sites that store a significant amount of user data, this becomes a
 potential performance bottleneck at-scale. As a solution, developers may
 add their own custom indexes to accommodate more efficient queries. Upon a
 core database upgrade, these custom indexes get removed and need to be re-
 added.

 To better support developers, WP may want to add a check for custom
 indexes prior to core DB updates, as well as retain or translate the
 schema customizations post-upgrade.

 https://core.trac.wordpress.org/browser/tags/5.8.1/src/wp-
 admin/includes/upgrade.php

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55402>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:27:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:27:29 -0000
Subject: [wp-trac] [WordPress Trac] #50238: Image rotation still an
 issue with images shot from above
In-Reply-To: <057.80150ec67e1be541f8e3bec875522dae@wordpress.org>
References: <057.80150ec67e1be541f8e3bec875522dae@wordpress.org>
Message-ID: <072.b5fd5b8c3d6dc09bc7726eca360f39cb@wordpress.org>

#50238: Image rotation still an issue with images shot from above
---------------------------+------------------------------
 Reporter:  wmassjunction  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Media          |     Version:  5.4.1
 Severity:  major          |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by joedolson):

 Related: https://core.trac.wordpress.org/ticket/14459

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50238#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:27:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:27:33 -0000
Subject: [wp-trac] [WordPress Trac] #50126: Latest large Image size
 compression generating incorrect file permissions
In-Reply-To: <057.1810435f3f7d949d184c52b815c8eaad@wordpress.org>
References: <057.1810435f3f7d949d184c52b815c8eaad@wordpress.org>
Message-ID: <072.ab3bf3261b78c1ee3551d8024e641d74@wordpress.org>

#50126: Latest large Image size compression generating incorrect file permissions
-------------------------------+------------------------------
 Reporter:  michael.moody      |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:  5.4.1
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by antpb):

 * keywords:   => reporter-feedback


Comment:

 Hi @michaelmoody first, sorry for the delay in response here. I am not an
 expert with IIS or have access so I might need some more info here.

 First, it has been a while 😅, are you still experiencing this? Going to
 do some research IIS and see if theres anything that stands out in the
 mean time.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50126#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:33:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:33:30 -0000
Subject: [wp-trac] [WordPress Trac] #55401: Subpages of a web page can
 be called twice
In-Reply-To: <055.3f14c28994df00d9eeb59ba7b17bab48@wordpress.org>
References: <055.3f14c28994df00d9eeb59ba7b17bab48@wordpress.org>
Message-ID: <070.5bc523190ec3c9814bfcdb31fc18691c@wordpress.org>

#55401: Subpages of a web page can be called twice
--------------------------+------------------------------
 Reporter:  manuel10503   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Permalinks    |     Version:  5.9.2
 Severity:  major         |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------

Comment (by manuel10503):

 Replying to [comment:1 SergeyBiryukov]:
 > Good catch, a similar issue was fixed in [47727] / #40773 for URLs
 ending with `/2/` or `/3/` (unless they are intended to be paged). The
 redirect  for `/1/` also works as expected, but apparently not for `/0/`.

 Thanks for the quick reply. When can I expect approximately a bugfix for
 this problem?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55401#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:38:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:38:31 -0000
Subject: [wp-trac] [WordPress Trac] #50238: Image rotation still an
 issue with images shot from above
In-Reply-To: <057.80150ec67e1be541f8e3bec875522dae@wordpress.org>
References: <057.80150ec67e1be541f8e3bec875522dae@wordpress.org>
Message-ID: <072.956fe8d2675e7b6d6b0c50c91b0b4b0c@wordpress.org>

#50238: Image rotation still an issue with images shot from above
-------------------------------+------------------------------
 Reporter:  wmassjunction      |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:  5.4.1
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by antpb):

 * keywords:   => reporter-feedback


Comment:

 It seems this issue was hit in this issue but it turned out to not be
 happening anymore. :
 https://core.trac.wordpress.org/ticket/48202#comment:5

 Can you confirm if this is still happening @wmassjunction or if your issue
 is similar to the one linked above?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50238#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:44:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:44:42 -0000
Subject: [wp-trac] [WordPress Trac] #55403: `wp_crop_image` returning
 incorrect file path when image formats filtered
Message-ID: <052.84b9aebdf6341160f1e508c9526bd17f@wordpress.org>

#55403: `wp_crop_image` returning incorrect file path when image formats filtered
--------------------------+-----------------------------
 Reporter:  Mat Lipe      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.8
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 The `wp_crop_image` function calculates the destination file path based on
 the source file's extension.

 Version 5.8.0 introduced a new `image_editor_output_format` filter which
 allows you to change the output format (extension) of generated image
 sizes. If the generated image extension is changed, `wp_crop_images` does
 not honor the change and returns a broken path to an image with the
 correct name but the source files original (now incorrect) extension.

 Example filter which converts the extensions to webp:

 {{{#!php
 <?php
 add_filter( 'image_editor_output_format', fn() => array_fill_keys( [
 'image/jpg', 'image/jpeg', 'image/png' ], 'image/webp' ) );
 }}}

 Recreate steps:
 1. Add the example filter.
 2. Upload a JPEG or PNG to media library.
 3. Edit the uploaded image via the media library.
 4. Crop the image and save it.
 5. Notice the image is now broken and errors will display in browser
 console.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55403>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:51:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:51:25 -0000
Subject: [wp-trac] [WordPress Trac] #50256: Inconsistent image handling
 in wp_create_image_subsizes.
In-Reply-To: <048.b927a2cdd4c5695d1ac73e8d834cd254@wordpress.org>
References: <048.b927a2cdd4c5695d1ac73e8d834cd254@wordpress.org>
Message-ID: <063.fb19165db8a8e57ebbdeb144e8a9cb55@wordpress.org>

#50256: Inconsistent image handling in wp_create_image_subsizes.
-------------------------------+------------------------------
 Reporter:  ddur               |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:  5.3
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by antpb):

 * keywords:   => reporter-feedback


Comment:

 Hello @ddur thank you for your ticket ! Can you give us a reproduction
 outline step by step?  (maybe some example files too!)

 I'm trying to understand what the bug is you are seeing and the expected
 results. Some reproduction steps with an example file would be very
 helpful! Thank you!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50256#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:56:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:56:30 -0000
Subject: [wp-trac] [WordPress Trac] #55404: Twenty Twenty-Two, Site Edit,
 Group with Background Color Overflows Page Size on Mobile
Message-ID: <053.51e62d08cd20bba6dbe82e617076bd65@wordpress.org>

#55404: Twenty Twenty-Two, Site Edit, Group with Background Color Overflows Page
Size on Mobile
-------------------------------+-----------------------------
 Reporter:  joshuanan          |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Formatting         |    Version:  5.9.2
 Severity:  minor              |   Keywords:
  Focuses:  ui, css, template  |
-------------------------------+-----------------------------
 When you add a group block with a background color to a footer template in
 the full site editor, the group block will overflow the page on a mobile
 device by a few pixels. For example, on a device that is 360 pixels wide
 will have approximately 10 pixels of overflow. The offending party is this
 CSS code:

 {{{
 .wp-site-blocks .alignfull, .wp-site-blocks > .wp-block-group.has-
 background, .wp-site-blocks > .wp-block-cover, .wp-site-blocks > .wp-
 block-template-part > .wp-block-group.has-background, .wp-site-blocks >
 .wp-block-template-part > .wp-block-cover, body > .is-root-container >
 .wp-block-cover, body > .is-root-container > .wp-block-template-part >
 .wp-block-group.has-background, body > .is-root-container > .wp-block-
 template-part > .wp-block-cover, .is-root-container .wp-block[data-
 align="full"] {
   margin-left: calc(-1 * var(--wp--custom--spacing--outer)) !important;
   margin-right: calc(-1 * var(--wp--custom--spacing--outer)) !important;
   width: unset;
 }
 }}}

 Where margin-right is the source of the problem. Turning that style off in
 my browser's developer console eliminates the extra space.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55404>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:56:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:56:49 -0000
Subject: [wp-trac] [WordPress Trac] #55404: Twenty Twenty-Two, Site Edit,
 Group with Background Color Overflows Page Size on Mobile
In-Reply-To: <053.51e62d08cd20bba6dbe82e617076bd65@wordpress.org>
References: <053.51e62d08cd20bba6dbe82e617076bd65@wordpress.org>
Message-ID: <068.9da57409a8d2d307426bf0e89eb01811@wordpress.org>

#55404: Twenty Twenty-Two, Site Edit, Group with Background Color Overflows Page
Size on Mobile
--------------------------+--------------------------------
 Reporter:  joshuanan     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Formatting    |     Version:  5.9.2
 Severity:  minor         |  Resolution:
 Keywords:                |     Focuses:  ui, css, template
--------------------------+--------------------------------
Changes (by joshuanan):

 * Attachment "Capture.PNG" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55404>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 16:56:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 16:56:56 -0000
Subject: [wp-trac] [WordPress Trac] #55404: Twenty Twenty-Two, Site Edit,
 Group with Background Color Overflows Page Size on Mobile
In-Reply-To: <053.51e62d08cd20bba6dbe82e617076bd65@wordpress.org>
References: <053.51e62d08cd20bba6dbe82e617076bd65@wordpress.org>
Message-ID: <068.b24b1b23a0ffe7daf89339c0d06a9942@wordpress.org>

#55404: Twenty Twenty-Two, Site Edit, Group with Background Color Overflows Page
Size on Mobile
--------------------------+--------------------------------
 Reporter:  joshuanan     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Formatting    |     Version:  5.9.2
 Severity:  minor         |  Resolution:
 Keywords:                |     Focuses:  ui, css, template
--------------------------+--------------------------------
Changes (by joshuanan):

 * Attachment "Capture2.PNG" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55404>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 17:01:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 17:01:27 -0000
Subject: [wp-trac] [WordPress Trac] #50264:
 wp_get_image_editor()->multi_resize() occasionally fails
In-Reply-To: <054.3d9d57316decca504d21e10168ed4014@wordpress.org>
References: <054.3d9d57316decca504d21e10168ed4014@wordpress.org>
Message-ID: <069.ac79e134e4cd751d69de2dbe081bca00@wordpress.org>

#50264: wp_get_image_editor()->multi_resize() occasionally fails
-------------------------------+------------------------------
 Reporter:  dangerd512         |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:  5.4.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by antpb):

 * keywords:   => reporter-feedback


Comment:

 Hello @dangerd512! Is your server configuration using GD or Imagick? Also
 is the failed image always the smallest size or always the last size
 generated?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50264#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 17:35:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 17:35:57 -0000
Subject: [wp-trac] [WordPress Trac] #55244: Non-editable title.
In-Reply-To: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
References: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
Message-ID: <066.ea85331f5076b830befaf1f059519ee6@wordpress.org>

#55244: Non-editable title.
----------------------------+----------------------------------------
 Reporter:  krilike         |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  5.9.2
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  accessibility, javascript
----------------------------+----------------------------------------
Changes (by marcorroma):

 * version:  5.9.1 => 5.9.2
 * component:  Editor => Administration


Comment:

 Replying to [comment:4 krilike]:  I have the same problem
 > Hey @juhise
 >
 > Please try the following steps:
 >
 > 1) Open the post.
 > 2) Add a couple of paragraphs.
 > 3) Important! Click somewhere around here https://prnt.sc/FP8tdoBgjAjc
 (so as not to touch the text).
 > 4) Press CTRL+A to highlight the paragraphs, as in this screenshot
 https://prnt.sc/b34gZ8ISRuNG
 > 5) Try to edit the heading.
 >
 >
 > ----
 > Env:
 > WordPress 5.9.1, 5.9.2
 > Firefox 97.0.2, Chrome 99.0.4844.51, Opera 84.0.4316.31, Edge
 99.0.1150.36
 > Windows 11
 > Themes: Twenty Twenty-One, Twenty Twenty-Two
 > Gutenberg Editor
 > Plugins: ---

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55244#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 17:43:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 17:43:54 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to
 allow for named parameters in WP 6.0
In-Reply-To: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
References: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
Message-ID: <072.8ce58557ce6370ceb1d27353b0ca7a94@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
----------------------------+---------------------
 Reporter:  peterwilsoncc   |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  php80           |     Focuses:
----------------------------+---------------------
Changes (by jrf):

 * keywords:   => php80


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55327#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 17:50:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 17:50:38 -0000
Subject: [wp-trac] [WordPress Trac] #55244: Non-editable title.
In-Reply-To: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
References: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
Message-ID: <066.a1fb8edaf1f3ee90759c552b39b268cd@wordpress.org>

#55244: Non-editable title.
--------------------------+----------------------------------------
 Reporter:  krilike       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility, javascript
--------------------------+----------------------------------------
Changes (by SergeyBiryukov):

 * component:  Administration => Editor


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55244#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 17:57:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 17:57:51 -0000
Subject: [wp-trac] [WordPress Trac] #30580: wp_extract_urls not
 returning full URL with &amp; query separator
In-Reply-To: <051.51c6e567e72b36f7a4c97869788883ee@wordpress.org>
References: <051.51c6e567e72b36f7a4c97869788883ee@wordpress.org>
Message-ID: <066.6b758efe7568cd736fae1be24274a1f1@wordpress.org>

#30580: wp_extract_urls not returning full URL with &amp; query separator
----------------------------------------------------+---------------------
 Reporter:  trex005                                 |       Owner:  (none)
     Type:  defect (bug)                            |      Status:  new
 Priority:  normal                                  |   Milestone:
Component:  Formatting                              |     Version:  3.7
 Severity:  normal                                  |  Resolution:
 Keywords:  has-patch has-unit-tests needs-testing  |     Focuses:
----------------------------------------------------+---------------------

Comment (by ironprogrammer):

 The proposed [https://github.com/WordPress/wordpress-develop/pull/2283 PR
 2283] has been updated to include backward compatibility support for the
 removal of unused semicolons (`;`).

 Props @costdev, @hellofromTonya

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/30580#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 18:00:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 18:00:54 -0000
Subject: [wp-trac] [WordPress Trac] #55244: Non-editable title.
In-Reply-To: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
References: <051.8532326a37a4edd0a95abd16ccccf792@wordpress.org>
Message-ID: <066.5a0e80ca216cc5e9760fb4b45f96c2d9@wordpress.org>

#55244: Non-editable title.
--------------------------+----------------------------------------
 Reporter:  krilike       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.1
 Severity:  normal        |  Resolution:  reported-upstream
 Keywords:                |     Focuses:  accessibility, javascript
--------------------------+----------------------------------------
Changes (by skorasaurus):

 * status:  new => closed
 * version:  5.9.2 => 5.9.1
 * resolution:   => reported-upstream


Comment:

 @krilike

 Thank you for reporting; tickets involving the Gutenberg editor are being
 recorded on the github tracker; and it's already been reported by another
 user at https://github.com/WordPress/gutenberg/issues/39292

 Thank you again for also providing the details to reproduce the issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55244#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 18:05:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 18:05:16 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.ff8ad9c4fa923861e808f43980276eb5@wordpress.org>

#54272: Allow block themes to be activated without index.php
------------------------------+-----------------------------
 Reporter:  poena             |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  6.0
Component:  Themes            |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  template
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * Attachment "54272.4.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 18:08:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 18:08:13 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>

#54272: Allow block themes to be activated without index.php
------------------------------+-----------------------------
 Reporter:  poena             |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  6.0
Component:  Themes            |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  template
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * Attachment "54272.4.diff" removed.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 18:08:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 18:08:13 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.2189e808ad3c196590a62eb35f178e93@wordpress.org>

#54272: Allow block themes to be activated without index.php
------------------------------+-----------------------------
 Reporter:  poena             |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  6.0
Component:  Themes            |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  template
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * Attachment "54272.4.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 18:09:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 18:09:41 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.0d0e827240acd03676a84e056def7694@wordpress.org>

#54272: Allow block themes to be activated without index.php
------------------------------+-----------------------------
 Reporter:  poena             |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  6.0
Component:  Themes            |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  template
------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 In [attachment:"54272.4.diff"]:
 * Check for `templates/index.html` first, as block themes would likely be
 more common in the future.
 * Update the documentation.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 18:15:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 18:15:52 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.ca50712f739327f3efa2bb2c129c0f8e@wordpress.org>

#54272: Allow block themes to be activated without index.php
------------------------------+-----------------------------
 Reporter:  poena             |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  6.0
Component:  Themes            |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  template
------------------------------+-----------------------------

Comment (by SergeyBiryukov):

 Replying to [comment:2 manfcarlo]:
 > What are the security implications of omitting index.php?

 I think including an empty `index.php` file to prevent directory listing
 may still be a good practice, but it does not have to be a requirement for
 themes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 18:29:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 18:29:00 -0000
Subject: [wp-trac] [WordPress Trac] #54272: Allow block themes to be
 activated without index.php
In-Reply-To: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
References: <049.474a9f3e2f58561a3c488042836071ca@wordpress.org>
Message-ID: <064.1fa0969b194b55d245d3fa592564a9b5@wordpress.org>

#54272: Allow block themes to be activated without index.php
------------------------------+-----------------------------
 Reporter:  poena             |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:  6.0
Component:  Themes            |     Version:
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:  template
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52940" 52940]:
 {{{
 #!CommitTicketReference repository="" revision="52940"
 Themes: Allow block themes to be activated without `index.php`.

 This removes the requirement for block themes to have an unused
 `index.php` template just for activation, as they use a
 `templates/index.html` file instead.

 The updated requirements are as follows:

 * Standalone themes need to have a `templates/index.html` or `index.php`
 template file.
 * Child themes need to have a `Template` header in the `style.css`
 stylesheet.

 Follow-up to [52069], [52247].

 Props poena, sabbirshouvo, scruffian, manfcarlo, overclokk, andraganescu,
 SergeyBiryukov.
 Fixes #54272.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54272#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 18:38:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 18:38:56 -0000
Subject: [wp-trac] [WordPress Trac] #55404: Twenty Twenty-Two, Site Edit,
 Group with Background Color Overflows Page Size on Mobile
In-Reply-To: <053.51e62d08cd20bba6dbe82e617076bd65@wordpress.org>
References: <053.51e62d08cd20bba6dbe82e617076bd65@wordpress.org>
Message-ID: <068.388bb75d55a44ac14bb03ec7efaf94b6@wordpress.org>

#55404: Twenty Twenty-Two, Site Edit, Group with Background Color Overflows Page
Size on Mobile
---------------------------+--------------------------------
 Reporter:  joshuanan      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:  5.9.2
 Severity:  minor          |  Resolution:
 Keywords:                 |     Focuses:  ui, css, template
---------------------------+--------------------------------
Changes (by SergeyBiryukov):

 * component:  Formatting => Bundled Theme


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55404#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 18:56:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 18:56:30 -0000
Subject: [wp-trac] [WordPress Trac] #50264:
 wp_get_image_editor()->multi_resize() occasionally fails
In-Reply-To: <054.3d9d57316decca504d21e10168ed4014@wordpress.org>
References: <054.3d9d57316decca504d21e10168ed4014@wordpress.org>
Message-ID: <069.7de0f6c5acf9f28195e11dfb71511858@wordpress.org>

#50264: wp_get_image_editor()->multi_resize() occasionally fails
-------------------------------+------------------------------
 Reporter:  dangerd512         |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Media              |     Version:  5.4.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by dangerd512):

 Replying to [comment:3 antpb]:
 > Hello @dangerd512! Is your server configuration using GD or Imagick?
 Also is the failed image always the smallest size or always the last size
 generated?

 It's totally random... Mostly it's okay, only sometimes I have this issue.
 A lot of photos are processing everyday.

 Imagick

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50264#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 19:21:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 19:21:47 -0000
Subject: [wp-trac] [WordPress Trac] #55405: i18n: Use a placeholder instead
 of 'Template' in a message in WP_Theme::__construct()
Message-ID: <058.95e80cfc4ea27e9f1dfb77507082860b@wordpress.org>

#55405: i18n: Use a placeholder instead of 'Template' in a message in
WP_Theme::__construct()
----------------------------+----------------------------------------
 Reporter:  SergeyBiryukov  |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  6.0
Component:  Themes          |    Version:
 Severity:  normal          |   Keywords:  needs-patch good-first-bug
  Focuses:                  |
----------------------------+----------------------------------------
 There is an error message in `WP_Theme::__construct()`:
 > `Template is missing. Standalone themes need to have a %1$s or %2$s
 template file. <a href="%3$s">Child themes</a> need to have a Template
 header in the %4$s stylesheet.`

 Since the `Template` word here is literal and is not meant to be
 translated, it should be moved out of the translatable string and replaced
 with a placeholder, similar to `index.php` or `style.css` in the same
 string.

 When working on a patch, please note that the translator comment above the
 string should be updated too.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55405>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 19:31:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 19:31:03 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.2d1e2c678aa2d576b5d051541fa36679@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52941" 52941]:
 {{{
 #!CommitTicketReference repository="" revision="52941"
 Docs: Add a `@since` note about Twenty Twenty-Two for
 `WP_Theme::$default_themes`.

 Follow-up to [51328], [52093].

 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:42>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 19:37:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 19:37:19 -0000
Subject: [wp-trac] [WordPress Trac] #13459: Conflict between post and
 page slugs/permalinks when permalink setting is set to /%postname%/
In-Reply-To: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
References: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
Message-ID: <071.51e7bd1cbd1dc844aacc873c260c3d7f@wordpress.org>

#13459: Conflict between post and page slugs/permalinks when permalink setting is
set to /%postname%/
--------------------------+-----------------------------
 Reporter:  jamescollins  |       Owner:  ericlewis
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  Future Release
Component:  Permalinks    |     Version:  2.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------

Comment (by wpmarkuk):

 I found this issue today too. Creating a page and a post with the same
 `slug` results in the post being inaccessible. This seems to be because
 both have the same slug and the page always wins.

 If the permalinks are set to `/%postname%/` the I am assuming that posts
 and pages are using the same "namespace".

 I think the solution here, is that if the permalink structure is set like
 this, when WordPress saves the post slug, it needs to check both posts and
 pages for others with the same slug. I assume this it is only checking
 posts at this time. This was probably a legacy as to when permalinks
 didn't allow `/%postname%/`.

 I don't know what happens when the slug is set, but I assume that there is
 a check for other posts with the same slug (maybe a query). If pages were
 included in this check it could solve the problem.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/13459#comment:62>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 20:03:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 20:03:37 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.c31ca0b95249a83622cf453582650afb@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------
Changes (by adamsilverstein):

 * Attachment "53232.3.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 20:04:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 20:04:44 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.c720d987bb6dbbfc41755e3cc7edf5c9@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
--------------------------------------+------------------------------
 Reporter:  isaumya                   |       Owner:  adamsilverstein
     Type:  feature request           |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+------------------------------

Comment (by adamsilverstein):

 [attachment:"53232.3.diff"] addresses feedback raised on the
 [https://github.com/WordPress/wordpress-develop/pull/2409 PR]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:48>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 20:05:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 20:05:41 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.e4335fe5da1d9e87f9da5d4d5e97cdab@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
---------------------------------------------+-----------------------------
 Reporter:  isaumya                          |       Owner:
                                             |  adamsilverstein
     Type:  feature request                  |      Status:  assigned
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+-----------------------------
Changes (by adamsilverstein):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 20:07:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 20:07:48 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.5cbb4520fbd2ae302c523a07c31f1b18@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
---------------------------------------------+-----------------------------
 Reporter:  isaumya                          |       Owner:
                                             |  adamsilverstein
     Type:  feature request                  |      Status:  assigned
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+-----------------------------

Comment (by adamsilverstein):

 @westonruter this looks good to me, marked for commit, nice work!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:50>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 21:41:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 21:41:51 -0000
Subject: [wp-trac] [WordPress Trac] #55399: esc_xml() removes valid XML
 input ( input that is empty() )
In-Reply-To: <054.6f1ed67beb6072490bacc7335e1248d1@wordpress.org>
References: <054.6f1ed67beb6072490bacc7335e1248d1@wordpress.org>
Message-ID: <069.5065dcd16fb2b5d274d0d7e2131e4559@wordpress.org>

#55399: esc_xml() removes valid XML input ( input that is empty() )
-------------------------------------+-----------------------
 Reporter:  rumpel2116               |       Owner:  pbiron
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Formatting               |     Version:  5.5
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+-----------------------
Changes (by pbiron):

 * keywords:  has-patch => has-patch needs-testing
 * owner:  (none) => pbiron
 * status:  new => assigned


Comment:

 @rumpel2116 Thanx for this ticket and the patch/PR.  At first glance it
 looks like the problem is real and the PR fixes.  I'll do some more
 extensive testing this week and hopefully we'll get this committed
 quickly.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55399#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 21:54:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 21:54:43 -0000
Subject: [wp-trac] [WordPress Trac] #55406: shorcodes don't work inside
 srcset attribute
Message-ID: <049.c652ade6e5f28e9792a4cbda780368e7@wordpress.org>

#55406: shorcodes don't work inside srcset attribute
--------------------------+-----------------------------
 Reporter:  XXVII         |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Shortcodes    |    Version:  5.8.3
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hello,
 I have a simple shortcodes which replaces [uploads_directory] with the
 actual path.
 It doesn't work if I put it in a srcset attribute, while it works fine in
 a src attribute.

 {{{
 <!-- this doesn't work -->
 <img srcset="[uploads_directory]/2022/03/image.webp 1x,
 [uploads_directory]/2022/03/image at 2x.webp 2x" />

 <!-- this is ok -->
 <img src="[uploads_directory]/2022/03/image.svg" />
 }}}


 This is the code of the shortcode function
 {{{#!php
 <?php
 function insert_get_uploads_directory() {
         $directory = wp_upload_dir();
         return $directory['baseurl'];
 }
 add_shortcode( 'uploads_directory', 'insert_get_uploads_directory' );
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55406>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 21:58:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 21:58:42 -0000
Subject: [wp-trac] [WordPress Trac] #13459: Conflict between post and
 page slugs/permalinks when permalink setting is set to /%postname%/
In-Reply-To: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
References: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
Message-ID: <071.b8bbe5f054e6e914ae101c67741a2f63@wordpress.org>

#13459: Conflict between post and page slugs/permalinks when permalink setting is
set to /%postname%/
--------------------------+-----------------------------
 Reporter:  jamescollins  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Permalinks    |     Version:  2.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------
Changes (by ericlewis):

 * owner:  ericlewis => (none)
 * status:  accepted => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/13459#comment:64>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 22:05:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 22:05:45 -0000
Subject: [wp-trac] [WordPress Trac] #55403: `wp_crop_image` returning
 incorrect file path when image formats filtered
In-Reply-To: <052.84b9aebdf6341160f1e508c9526bd17f@wordpress.org>
References: <052.84b9aebdf6341160f1e508c9526bd17f@wordpress.org>
Message-ID: <067.c3ab77129fd8d395f7648b2c9ce7bd40@wordpress.org>

#55403: `wp_crop_image` returning incorrect file path when image formats filtered
--------------------------------------+------------------------------
 Reporter:  Mat Lipe                  |       Owner:  adamsilverstein
     Type:  defect (bug)              |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  General                   |     Version:  5.8
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------------
Changes (by adamsilverstein):

 * owner:  (none) => adamsilverstein
 * status:  new => assigned
 * milestone:  Awaiting Review => 6.0


Comment:

 Hi @mat-lipe - thanks for opening this ticket. Indeed, I see the issue you
 identified, the the output path is changed on the fly during the save, so
 we should rely on the path returned from the save call instead of the
 original destination path.

 Fix in patch looks good to me, thanks for adding the test as well. I'd
 still like to test this via the steps you provided before committing;
 marking for 6.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55403#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 22:25:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 22:25:49 -0000
Subject: [wp-trac] [WordPress Trac] #33156: Allow admin-ajax crawling
In-Reply-To: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
References: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
Message-ID: <070.991aafce3f43ea3ea1e75d834d3a93e5@wordpress.org>

#33156: Allow admin-ajax crawling
-----------------------------------+-----------------------------
 Reporter:  joostdevalk            |       Owner:  SergeyBiryukov
     Type:  enhancement            |      Status:  closed
 Priority:  normal                 |   Milestone:  4.4
Component:  General                |     Version:
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  2nd-opinion has-patch  |     Focuses:
-----------------------------------+-----------------------------

Comment (by KnowingArt_com):

 Replying to [comment:22 KnowingArt_com]:
 > It seems like all the comments of concern were ignored.

 I'm starting to get a better understanding of the issue(s) that triggered
 this desire to sortof whitelist this ajax script for Googlebot. However,
 we should not pollute robots.txt to fix poorly-conceived AJAX themes that
 lazyload content without non-AJAX placeholder content, do not fail
 gracefully, or whatever happened to these themes.

 Likewise, robots.txt is not the best place for Googlebot-specific problems
 either. I think WordPress is big enough to work that out with Google
 directly. And for really specific problems, just use your web server
 config.

 I'm also thinking, if WordPress decides to back out of robots.txt, will
 that break stuff? I doubt it, but I don't know for sure. I think the
 alternative is worse. Because now you have wp-sitemap.xml in there, how
 deep will this rabbit hole go before all the custom robots.txt files out
 there the need to be rewritten to "catch up" with the auto-generated
 WordPress robots.txt?

 Also, I created this last night...

 https://wordpress.stackexchange.com/questions/403753/why-does-do-robots-
 allow-wp-admin-admin-ajax-php-by-default

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33156#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 22:53:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 22:53:21 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive elements
 for KSES
Message-ID: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>

#55407: Allow case-insensitive elements for KSES
--------------------------+-----------------------------
 Reporter:  r-a-y         |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Formatting    |    Version:
 Severity:  normal        |   Keywords:  has-patch
  Focuses:                |
--------------------------+-----------------------------
 I'm trying to allow some HTML elements that are capitalized.

 eg. `<Post attribute="value"></Post>`

 However, attempting to add a custom element with the
 `'wp_kses_allowed_html'` filter fails due to the `strtolower()` additions
 in `kses.php`. I've attached a patch, which removes these `strtolower()`
 calls. Let me know what you think.

 HTML elements do not have to be lowercase. The W3C notes this here:
 https://w3c.github.io/html-reference/documents.html#case-insensitivity

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 22:54:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 22:54:09 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive
 elements for KSES
In-Reply-To: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
References: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
Message-ID: <064.d0362edd3e555072838d65015f134e76@wordpress.org>

#55407: Allow case-insensitive elements for KSES
--------------------------+------------------------------
 Reporter:  r-a-y         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Formatting    |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------
Changes (by r-a-y):

 * Attachment "55407.01.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 23:05:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 23:05:00 -0000
Subject: [wp-trac] [WordPress Trac] #33156: Allow admin-ajax crawling
In-Reply-To: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
References: <055.e1a5e2c744fdc88a9bc1a7baba0d4c4c@wordpress.org>
Message-ID: <070.193edad2e2e0772b07029ca09c84b881@wordpress.org>

#33156: Allow admin-ajax crawling
-----------------------------------+-----------------------------
 Reporter:  joostdevalk            |       Owner:  SergeyBiryukov
     Type:  enhancement            |      Status:  closed
 Priority:  normal                 |   Milestone:  4.4
Component:  General                |     Version:
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  2nd-opinion has-patch  |     Focuses:
-----------------------------------+-----------------------------

Comment (by KnowingArt_com):

 Replying to [comment:24 dmchale]:
 > 1. Create a physical robots.txt file on your server. If WordPress
 detects a physical file at the web root, it will not add to / remove from
 / modify that file in any way (this includes any plugins that dynamically
 modify the robots.txt file as well)
 >
 > 2. Use the `robots_txt` filter to modify the contents of the WordPress
 defaults https://developer.wordpress.org/reference/hooks/robots_txt/

 1. Nice, but without comments in robots.txt, how will the casual user
 know? My first impression was to 'touch robots.txt' but...

 1a. How will anyone know this won't break wp-sitemap.xml? That's how I
 ended up here. Upon further investigation, it seems *Google* contributed
 the code that adds wp-sitemap.xml to robots.txt If a Google employee adds
 some code to the WordPress robots.txt, that tells me Google wants that
 code to be there, and I am going to think twice about removing it.

 1b. Also casual user: If I remove this weird ajax thing, am I going to
 break something? Maybe I should investigate further. And down the rabbit
 hole we go into ajax themes with broken Googlebot renderings :-(

 2. That was my first attempt, but a) I crashed my site by trying some
 random Stack Exchange solution, b) I have many blogs to manage on several
 servers, and what if the blog changes themes? Is there a "functions.php"
 that affects all themes?, c) I don't really want a filter, I want to
 completely disable the creation of robots.txt, which is probably harder
 than it sounds.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33156#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 23:07:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 23:07:26 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive
 elements for KSES
In-Reply-To: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
References: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
Message-ID: <064.216628d11504d674a76b8d1c8a856554@wordpress.org>

#55407: Allow case-insensitive elements for KSES
----------------------------------------+---------------------
 Reporter:  r-a-y                       |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+---------------------
Changes (by SergeyBiryukov):

 * keywords:  has-patch => has-patch needs-unit-tests
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 23:08:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 23:08:21 -0000
Subject: [wp-trac] [WordPress Trac] #53234: Application password access
 text is misleading for Super Admins
In-Reply-To: <055.0e9d1b8f7ea2e3fdeb10ed7ba49893b2@wordpress.org>
References: <055.0e9d1b8f7ea2e3fdeb10ed7ba49893b2@wordpress.org>
Message-ID: <070.80e811908331feedbf5aeb9b664480a3@wordpress.org>

#53234: Application password access text is misleading for Super Admins
----------------------------------------+------------------------
 Reporter:  johnbillion                 |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Application Passwords       |     Version:  5.6
 Severity:  normal                      |  Resolution:
 Keywords:  good-first-bug needs-patch  |     Focuses:  multisite
----------------------------------------+------------------------
Changes (by audrasjb):

 * keywords:  good-first-bug has-patch => good-first-bug needs-patch


Comment:

 Thanks for the patch @rsiddharth but the strings you added need to be
 ready for internationalization. There are not translatable for now in
 `53234.patch`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53234#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 23:15:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 23:15:27 -0000
Subject: [wp-trac] [WordPress Trac] #54825: Heartbeat minimalInterval
 option causing incorrect value of mainInterval
In-Reply-To: <052.178ab55ed3f5ca5a3f83240968007f51@wordpress.org>
References: <052.178ab55ed3f5ca5a3f83240968007f51@wordpress.org>
Message-ID: <067.7791d1588402bf6a70661589aabb072c@wordpress.org>

#54825: Heartbeat minimalInterval option causing incorrect value of mainInterval
-------------------------------------------------+-------------------------
 Reporter:  tabrisrp                             |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Autosave                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:  javascript
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch needs-testing => has-patch dev-feedback needs-
               testing


Comment:

 The PR provided by @tabrisrp looks good to me and fixes the underlined
 issue.
 If think it could use a second pair of eyes, just to check the overall
 logic, then we can ship it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54825#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 23:23:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 23:23:22 -0000
Subject: [wp-trac] [WordPress Trac] #46600: Twenty Nineteen: Flex order
 on comment form causes contents of comment_form_after to appear above the
 form
In-Reply-To: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
References: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
Message-ID: <074.8a9728b314376569c02b1d028ac2e978@wordpress.org>

#46600: Twenty Nineteen: Flex order on comment form causes contents of
comment_form_after to appear above the form
------------------------------------+---------------------------------
 Reporter:  garrett-eclipse         |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  6.0
Component:  Bundled Theme           |     Version:  5.0
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:  accessibility, css
------------------------------------+---------------------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch dev-feedback


Comment:

 @sabernhardt thanks, the patch looks great to me but I'm only wondering
 about replacing class `comment-form-flex` with `comment-form-wrapper`,
 since it would introduce a breaking change for people who customized this
 container. For the sake of backward compatibility, could we keep the
 previous class?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46600#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 23:40:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 23:40:02 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive
 elements for KSES
In-Reply-To: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
References: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
Message-ID: <064.b854b71d2e6a09d677bdc3445fa725a5@wordpress.org>

#55407: Allow case-insensitive elements for KSES
----------------------------------------+---------------------
 Reporter:  r-a-y                       |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+---------------------
Changes (by r-a-y):

 * Attachment "55407.02.patch" added.

 Removes strtolower() call in force_balance_tags() as well

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 23:51:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 23:51:15 -0000
Subject: [wp-trac] [WordPress Trac] #54953: Custom css variables in
 theme.json have different keys in 5.9
In-Reply-To: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
References: <049.37a4675c319af99e56ffdbb04ed088bc@wordpress.org>
Message-ID: <064.9184c693401eadaa16ac729e14f2f33e@wordpress.org>

#54953: Custom css variables in theme.json have different keys in 5.9
--------------------------+--------------------------------
 Reporter:  walbo         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:  reported-upstream
 Keywords:                |     Focuses:
--------------------------+--------------------------------
Changes (by davidbaumwald):

 * status:  new => closed
 * resolution:   => reported-upstream
 * milestone:  5.9.3 =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54953#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 16 23:54:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 16 Mar 2022 23:54:44 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive
 elements for KSES
In-Reply-To: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
References: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
Message-ID: <064.089ec8ad21f9c3661da277ed6f4606b1@wordpress.org>

#55407: Allow case-insensitive elements for KSES
----------------------------------------+---------------------
 Reporter:  r-a-y                       |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+---------------------

Comment (by peterwilsoncc):

 The proposed patch is problematic in that it will make KSES case
 sensitive.

 Consider the HTML `<DIV CLASS="55407"></DIV>`, the first altered line
 removes `strtolower()` from the check of allowed elements. This will cause
 a false negative and result in the element being removed.

 See https://3v4l.org/5X0OJ for an example of the difference.

 In it's current form, KSES will maintain the case in which the element is
 entered.

 {{{
 <DIV class="55407">Some div</DIV>

 <Not-Allowed>Not Allowed element</Not-AlloWed>
 }}}

 Is stored in the database as

 {{{
 <DIV class="55407">Some div</DIV>

 Not Allowed element
 }}}


 Adding elements to the allowed HTML array or via the appropriate filter do
 need to be in lowercase. I think this needs to remain the case as the
 allowed HTML shouldn't contain the same element in different cases, eg

 {{{#!php
 <?php
 $allowed_html = [
    'div' => [ /* etc */ ],
    'DIV' => [ /* etc */ ],
 ];
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 00:00:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 00:00:16 -0000
Subject: [wp-trac] [WordPress Trac] #53370: Theme thumbnail/screenshot
 does not contain version string
In-Reply-To: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
References: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
Message-ID: <066.fddda3d6a60fd68927f816191f9ffb08@wordpress.org>

#53370: Theme thumbnail/screenshot does not contain version string
-------------------------------------+---------------------
 Reporter:  codente                  |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Themes                   |     Version:  5.7.2
 Severity:  minor                    |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+---------------------
Changes (by davidbaumwald):

 * keywords:  has-patch => has-patch needs-refresh


Comment:

 Marking for a refresh, per
 [https://core.trac.wordpress.org/ticket/53370#comment:5 Sergey's comment],
 to hopefully gain some attention during this cycle.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53370#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 00:05:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 00:05:51 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive
 elements for KSES
In-Reply-To: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
References: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
Message-ID: <064.f8d3e327da209cadf472cd916704e6d9@wordpress.org>

#55407: Allow case-insensitive elements for KSES
----------------------------------------+---------------------
 Reporter:  r-a-y                       |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+---------------------

Comment (by r-a-y):

 > Consider the HTML <DIV CLASS="55407"></DIV>

 Ah, that's a good point for existing content that might have uppercase
 elements already. Not sure how many WP installations this would actually
 affect though.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 00:21:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 00:21:11 -0000
Subject: [wp-trac] [WordPress Trac] #53650: Incorrect quotation marks in
 many strings
In-Reply-To: <056.2f16afaee9e60e7a4de0b30328fb46d4@wordpress.org>
References: <056.2f16afaee9e60e7a4de0b30328fb46d4@wordpress.org>
Message-ID: <071.0b7ab55ee2145565158ab475828ff309@wordpress.org>

#53650: Incorrect quotation marks in many strings
-------------------------------------+-------------------------------
 Reporter:  tobifjellner             |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  I18N                     |     Version:  5.8
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  coding-standards
-------------------------------------+-------------------------------

Comment (by davidbaumwald):

 @sayedulsayem Thanks for the patch and the PR!  Per, Sergey's comment
 above:
 >IIRC, the consensus previously was to use “curly quotes” in user-facing
 strings for better typography. Developer notices and email subjects can
 probably continue using regular double quotes.
 I don't think the intention here is to simply remove all the quotes.

 The can remain as-is for any developer notices(i.e. WP_Errors, etc.) and
 email subjects, but any strings shows to users should use the relevant
 curly-quote entity(i.e. `&#8220;` and `&#8221;`).

 Marking this for as `needs-refresh` so that the patch can be adjusted a
 bit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53650#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 00:40:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 00:40:33 -0000
Subject: [wp-trac] [WordPress Trac] #13459: Conflict between post and
 page slugs/permalinks when permalink setting is set to /%postname%/
In-Reply-To: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
References: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
Message-ID: <071.37043f2b4ccc1806638680f4eb3627e5@wordpress.org>

#13459: Conflict between post and page slugs/permalinks when permalink setting is
set to /%postname%/
--------------------------+-----------------------------
 Reporter:  jamescollins  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Permalinks    |     Version:  2.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------

Comment (by peterwilsoncc):

 This was discussed in the
 [https://wordpress.slack.com/archives/C02RQBWTW/p1647464545410199 dev-chat
 in Slack earlier]. In an earlier comment additional conflicts are
 mentioned so it would be good to have each of these investigated too so
 the bug is fixed rather than half a bug.

 There are a number of [https://wordpress.org/support/article/using-
 permalinks/#structure-tags-1 structure tags] available on the permalinks
 screen, some notes on collisions for each would be valuable:

 * content slugs matching a custom post type's slug
 * pages with an apparent date structure: `/2022/some-page` (also consider
 months, days, etc)
 * including uncommon components such as author, category

 Setting up a pull requests with some initially broken tests would be most
 helpful. If it's decided that some items aren't in scope, then follow up
 tickets can be created.

 Any changes would need to be made to the function `wp_unique_post_slug()`

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/13459#comment:65>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 01:26:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 01:26:00 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.b70e941f68b726d962361ef97bbfa82a@wordpress.org>

#32998: What's a weblog?
-----------------------------------------+----------------------
 Reporter:  johnjamesjacoby              |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  low                          |   Milestone:  6.0
Component:  Options, Meta APIs           |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+----------------------

Comment (by costdev):

 Throwing my two cents in: I think this is both specific and broad enough
 to be fit for purpose.

  An avatar is an image that can be associated with a user across multiple
 websites. Here, you can enable the display of avatars for users who
 interact with this site.

 - "image":
   - Implies "visual". ✅
   - Could be a photo. ✅
   - Could be a logo. ✅
   - Could be a cat. 😸

 - "can be"
   - Acknowledges that the user may not use it on other websites. ✅
     - The avatar is associated with an email address that the user may
 only use on this website.
     - The site owner doesn't need to know that it's associated with the
 user's email address.
   - Acknowledges that other websites used by the user may not have avatars
 enabled. ✅
   - Acknowledges Gravatar's copy: "You choose what to display on Gravatar-
 enabled sites: what you share on your profile is open to the world." ✅

 - "associated":
   - Accounts for an avatar that represents the user. ✅
   - Accounts for an avatar that represents the user's group (company,
 department, gaming clan). ✅
   - Accounts for an avatar that represents nothing. ✅
   - Accounts for default avatars. ✅

 - "users who interact with this site"
   - Does not differentiate between registered users and other visitors. ❓
 - Is this correct?
   - Does not assume the species of the user. ✅
     - Democratising publishing means we welcome our inter-galactic
 visitors. 👽

 - Does not presume to know where the avatar will be used on the website.
 ✅

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 02:58:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 02:58:41 -0000
Subject: [wp-trac] [WordPress Trac] #55408: Error Formulario de Pago
 Woocommerce
Message-ID: <052.91c795e75031523fff44d6de590f4db0@wordpress.org>

#55408: Error Formulario de Pago Woocommerce
--------------------------+-----------------------------
 Reporter:  dantepgs      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Luego de llenar los datos en formulario de checkout de woorcommerce y hago
 click en botón de PayPal, no avanza y me aparece este mensaje:
 "CITY_REQUIRED The specified country requires a city
 (address.admin_area_2)"
 Por favor solicito ayuda de soporte

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55408>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 03:08:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 03:08:10 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.13c1d8daa1cf59cdc27b4dbdf3b792f1@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
---------------------------------------+---------------------
 Reporter:  kajalgohel                 |       Owner:  (none)
     Type:  enhancement                |      Status:  new
 Priority:  normal                     |   Milestone:  6.0
Component:  Bundled Theme              |     Version:  3.6
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:  css
---------------------------------------+---------------------

Comment (by peterwilsoncc):

 Thanks for testing Colin.

 It would be good to see some additional OS/Browser combinations so I'll
 hold off committing for now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55362#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 03:15:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 03:15:07 -0000
Subject: [wp-trac] [WordPress Trac] #55362: Twenty Thirteen : Invalid
 use of display and float together in style.css file
In-Reply-To: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
References: <054.d3f65df8f9b9f283e374f26b944ef9ed@wordpress.org>
Message-ID: <069.cf6a7d5a7dc4516990ee782c65a3d6db@wordpress.org>

#55362: Twenty Thirteen : Invalid use of display and float together in style.css
file
---------------------------------------------+---------------------
 Reporter:  kajalgohel                       |       Owner:  (none)
     Type:  enhancement                      |      Status:  new
 Priority:  normal                           |   Milestone:  6.0
Component:  Bundled Theme                    |     Version:  3.6
 Severity:  normal                           |  Resolution:
 Keywords:  has-screenshots has-patch close  |     Focuses:  css
---------------------------------------------+---------------------
Changes (by peterwilsoncc):

 * keywords:  has-screenshots has-patch => has-screenshots has-patch close


Comment:

 There's a discussion on #55338 as to whether a similar change should be
 made to Twenty Eleven or whether the ticket should be closed as wontfix.

 It seems sensible to make the same decision for both this and the other
 ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55362#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 03:15:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 03:15:40 -0000
Subject: [wp-trac] [WordPress Trac] #32315: $wpdb->insert fails without
 error msg
In-Reply-To: <050.458415d52e7c0d7f7499c16c77d7fd0c@wordpress.org>
References: <050.458415d52e7c0d7f7499c16c77d7fd0c@wordpress.org>
Message-ID: <065.8ee2c4710f5d601cb0db0149059b15eb@wordpress.org>

#32315: $wpdb->insert fails without error msg
---------------------------------------------+-----------------------------
 Reporter:  dlt101                           |       Owner:  hellofromTonya
     Type:  defect (bug)                     |      Status:  closed
 Priority:  normal                           |   Milestone:  5.9
Component:  Database                         |     Version:  4.2.1
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------------

Comment (by psufan):

 I can confirm 5.9.2 produces the new error message. Not really happy about
 it however haha. Had a user enter a string with ampersand which silently
 failed and now produces this error. Is ampersand a mysql reserved
 character? 5.9.2 will not insert() a string with an ampersand in it. What
 other characters are not allowed with insert()? We didn't agree to
 truncate the data and insert anyway?


 {{{
 WordPress database error: Processing the value for the following field
 failed: [COLUMN]. The supplied value may be too long or contains invalid
 data.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32315#comment:97>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 03:15:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 03:15:51 -0000
Subject: [wp-trac] [WordPress Trac] #55338: Twenty Eleven: Invalid use
 of display and float together in style.css file
In-Reply-To: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
References: <054.52ea2b5713d909b9de0cd129fecc2569@wordpress.org>
Message-ID: <069.d6e059301acfe6577dc5ae427a04935d@wordpress.org>

#55338: Twenty Eleven: Invalid use of display and float together in style.css file
-------------------------------------------+---------------------
 Reporter:  kajalgohel                     |       Owner:  (none)
     Type:  enhancement                    |      Status:  new
 Priority:  normal                         |   Milestone:  6.0
Component:  Bundled Theme                  |     Version:  3.2
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch needs-testing close  |     Focuses:  css
-------------------------------------------+---------------------

Comment (by peterwilsoncc):

 Re the `close` discussion, #55362 is very similar so it seems sensible to
 make the same decision for both.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55338#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 03:17:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 03:17:45 -0000
Subject: [wp-trac] [WordPress Trac] #55408: Error Formulario de Pago
 Woocommerce
In-Reply-To: <052.91c795e75031523fff44d6de590f4db0@wordpress.org>
References: <052.91c795e75031523fff44d6de590f4db0@wordpress.org>
Message-ID: <067.4eba6e7656e3e5740732af2c84f30270@wordpress.org>

#55408: Error Formulario de Pago Woocommerce
--------------------------+------------------------------
 Reporter:  dantepgs      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by dantepgs):

 El link de la página del error es: https://tienda.cipoa.org/checkout/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55408#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 03:35:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 03:35:27 -0000
Subject: [wp-trac] [WordPress Trac] #55301: Provide an API to prevent
 certain blocks being shown in Widget Areas
In-Reply-To: <054.c9987188ae18b3032cf99143e88d3151@wordpress.org>
References: <054.c9987188ae18b3032cf99143e88d3151@wordpress.org>
Message-ID: <069.3024ab2c248caa305e1ad10fcec23492@wordpress.org>

#55301: Provide an API to prevent certain blocks being shown in Widget Areas
-------------------------------------------------+-------------------------
 Reporter:  noisysocks                           |       Owner:  noisysocks
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note                                           |
-------------------------------------------------+-------------------------
Changes (by noisysocks):

 * owner:  (none) => noisysocks
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52942" 52942]:
 {{{
 #!CommitTicketReference repository="" revision="52942"
 Add WP_Block_Editor_Context::$name

 Adds a new `WP_Block_Editor_Context::$name` and field. This allows plugin
 developers to tell which block editor is being loaded when using filters
 such as
 `allowed_block_types_all` and `block_editor_rest_api_preload_paths`.

 Fixes #55301.
 Props talldanwp, gziolo, andraganescu.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55301#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 03:46:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 03:46:20 -0000
Subject: [wp-trac] [WordPress Trac] #55226: Update
 class-wp-site-query.php - Change function parse_orderby()
In-Reply-To: <053.ec450fb72885a823fd1521dec9619704@wordpress.org>
References: <053.ec450fb72885a823fd1521dec9619704@wordpress.org>
Message-ID: <068.248ed88651fa6b63e15ed11711ae1c5a@wordpress.org>

#55226: Update class-wp-site-query.php - Change function parse_orderby()
--------------------------------+---------------------
 Reporter:  lenasterg           |       Owner:  (none)
     Type:  enhancement         |      Status:  new
 Priority:  normal              |   Milestone:  6.0
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  has-patch           |     Focuses:
--------------------------------+---------------------

Comment (by peterwilsoncc):

 To try and avoid followup tickets, is the same needed for any/all of the
 other boolean fields in the table: mature, spam, archived, public?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55226#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 03:51:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 03:51:09 -0000
Subject: [wp-trac] =?utf-8?q?=5BWordPress_Trac=5D_=2355409=3A_Comment_link?=
 =?utf-8?q?_navigation_positioning_messed_with_comment=2C_when_i_try_optio?=
 =?utf-8?q?n_=E2=80=9Cbreak_comment_to_50_top_level=E2=80=9D?=
Message-ID: <051.58a80c5b0cc383e8f47be9f7fb1ac2e2@wordpress.org>

#55409: Comment link navigation positioning messed with comment, when i try option
“break comment to 50 top level”
--------------------------+-----------------------------
 Reporter:  mryudha       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Comments      |    Version:
 Severity:  normal        |   Keywords:
  Focuses:  css           |
--------------------------+-----------------------------
 Navigation on comment positioning is messed up. Check my screenshot here.
 https://prnt.sc/ErlX_M6nLwxL and here https://prnt.sc/OwxWUUTdMW_T and
 here https://prnt.sc/XZcJsPknS5zo

 those screenshot is from my live site. everything is updated to latest
 version.

 i also try to test it on local environment, the issue persist.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55409>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 03:57:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 03:57:26 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2355409=3A_Comment_lin?=
 =?utf-8?q?k_navigation_positioning_messed_with_comment=2C_when_i_try_opti?=
 =?utf-8?q?on_=E2=80=9Cbreak_comment_to_50_top_level=E2=80=9D?=
In-Reply-To: <051.58a80c5b0cc383e8f47be9f7fb1ac2e2@wordpress.org>
References: <051.58a80c5b0cc383e8f47be9f7fb1ac2e2@wordpress.org>
Message-ID: <066.65cc06665ca8b5514819a845370854c9@wordpress.org>

#55409: Comment link navigation positioning messed with comment, when i try option
“break comment to 50 top level”
--------------------------+------------------------------
 Reporter:  mryudha       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Comments      |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  css
--------------------------+------------------------------
Changes (by mryudha):

 * version:   => 5.9.2


Comment:

 Navigation on comment positioning is messed up. Check my screenshot here.
 https://prnt.sc/ErlX_M6nLwxL and here https://prnt.sc/OwxWUUTdMW_T and
 here https://prnt.sc/XZcJsPknS5zo

 those screenshot is from my live site. everything is updated to latest
 version.

 i also try to test it on local environment, the issue persist. I just
 imported xml from my live site to local test site. There is no plugin.

 also, i try a few FSE ready theme like blockbase, geologist and tt1 block.
 Issue persist.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55409#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 04:05:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 04:05:47 -0000
Subject: [wp-trac] [WordPress Trac] #46600: Twenty Nineteen: Flex order
 on comment form causes contents of comment_form_after to appear above the
 form
In-Reply-To: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
References: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
Message-ID: <074.0b3a3fd81d16c5c657c4eeb9fec4382c@wordpress.org>

#46600: Twenty Nineteen: Flex order on comment form causes contents of
comment_form_after to appear above the form
-----------------------------+---------------------------------
 Reporter:  garrett-eclipse  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Bundled Theme    |     Version:  5.0
 Severity:  normal           |  Resolution:
 Keywords:  needs-patch      |     Focuses:  accessibility, css
-----------------------------+---------------------------------
Changes (by sabernhardt):

 * keywords:  has-patch dev-feedback => needs-patch


Comment:

 I thought to switch classes for the structure, but did not account for
 several other possibilities (changing text or background color, adding a
 border, etc.).

 It probably should add a new class and keep the existing class, which
 requires a bit more CSS editing.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46600#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 04:11:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 04:11:41 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.c851e8313543d4930d31ebd635b54aa0@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by peterwilsoncc):

 In [changeset:"52943" 52943]:
 {{{
 #!CommitTicketReference repository="" revision="52943"
 Editor/Docs: Add `blockTypes` argument to
 `WP_Block_Patterns_Registry::register()` docblock.

 Add the optional `blockTypes` argument in the patten properties for
 `WP_Block_Patterns_Registry::register()`.

 Props vlad.olaru.
 Fixes #55303.
 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:43>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 04:11:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 04:11:42 -0000
Subject: [wp-trac] [WordPress Trac] #55303: Update
 WP_Block_Patterns_Registry::register() docs to include the blockTypes
 property
In-Reply-To: <054.5a2b39867af933a35c3aa88c756a9bd9@wordpress.org>
References: <054.5a2b39867af933a35c3aa88c756a9bd9@wordpress.org>
Message-ID: <069.5ab58a65aa174aafc212c413a74aba42@wordpress.org>

#55303: Update WP_Block_Patterns_Registry::register() docs to include the
blockTypes property
-------------------------+----------------------------
 Reporter:  vlad.olaru   |       Owner:  peterwilsoncc
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  6.0
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:  fixed
 Keywords:  has-patch    |     Focuses:  docs
-------------------------+----------------------------
Changes (by peterwilsoncc):

 * owner:  (none) => peterwilsoncc
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52943" 52943]:
 {{{
 #!CommitTicketReference repository="" revision="52943"
 Editor/Docs: Add `blockTypes` argument to
 `WP_Block_Patterns_Registry::register()` docblock.

 Add the optional `blockTypes` argument in the patten properties for
 `WP_Block_Patterns_Registry::register()`.

 Props vlad.olaru.
 Fixes #55303.
 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55303#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 04:26:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 04:26:58 -0000
Subject: [wp-trac] [WordPress Trac] #54971: Theme Details button cursor
 does not match cursor when hovering over screenshot
In-Reply-To: <057.2ac85ed39b5da1f2b0854c1ccc8f82b0@wordpress.org>
References: <057.2ac85ed39b5da1f2b0854c1ccc8f82b0@wordpress.org>
Message-ID: <072.877318f9bdfae8d26230dc86eaac3da3@wordpress.org>

#54971: Theme Details button cursor does not match cursor when hovering over
screenshot
-------------------------------------+-------------------------------------
 Reporter:  multidots1896            |       Owner:  peterwilsoncc
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Themes                   |     Version:  5.8
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots has-     |     Focuses:  ui, accessibility,
  patch commit                       |  css, administration
-------------------------------------+-------------------------------------
Changes (by peterwilsoncc):

 * keywords:  has-screenshots has-patch => has-screenshots has-patch commit
 * owner:  (none) => peterwilsoncc
 * status:  new => assigned


Comment:

 @ryokuhi Given your opinion matches @sabernhardt's, I think it's safe to
 consider the second opinion sort and provided.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54971#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 04:32:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 04:32:46 -0000
Subject: [wp-trac] [WordPress Trac] #54971: Theme Details button cursor
 does not match cursor when hovering over screenshot
In-Reply-To: <057.2ac85ed39b5da1f2b0854c1ccc8f82b0@wordpress.org>
References: <057.2ac85ed39b5da1f2b0854c1ccc8f82b0@wordpress.org>
Message-ID: <072.b3d48f338e4396ba4b470490304294b2@wordpress.org>

#54971: Theme Details button cursor does not match cursor when hovering over
screenshot
-------------------------------------+-------------------------------------
 Reporter:  multidots1896            |       Owner:  peterwilsoncc
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Themes                   |     Version:  5.8
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-screenshots has-     |     Focuses:  ui, accessibility,
  patch commit                       |  css, administration
-------------------------------------+-------------------------------------
Changes (by peterwilsoncc):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52944" 52944]:
 {{{
 #!CommitTicketReference repository="" revision="52944"
 Themes: Use pointer when hovering on theme details button.

 Use the pointer cursor when hovering over the theme details button for
 consistency with the theme card. Clicking in either area performs the same
 action.

 Props multidots1896, rehanali, ravipatel, sabernhardt, ryokuhi.
 Fixes #54971.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54971#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 04:47:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 04:47:59 -0000
Subject: [wp-trac] [WordPress Trac] #54746: Comment Error in wp-login.php
In-Reply-To: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
References: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
Message-ID: <066.a15074fe4e4c903bcde6d7049bd5cc1b@wordpress.org>

#54746: Comment Error in wp-login.php
------------------------------------+-------------------------------------
 Reporter:  alkesh7                 |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  6.0
Component:  Login and Registration  |     Version:
 Severity:  minor                   |  Resolution:
 Keywords:  has-patch               |     Focuses:  docs, coding-standards
------------------------------------+-------------------------------------

Comment (by peterwilsoncc):

 @Presskopp Yes, it's in several places in core. I found it in 49 files but
 some of those were third party libraries.

 For the purposes of this ticket, let's focus on wp-login.php and any
 further fixes can go on the generic coding standards fixes ticket #54728.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54746#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 04:52:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 04:52:41 -0000
Subject: [wp-trac] [WordPress Trac] #54746: Comment Error in wp-login.php
In-Reply-To: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
References: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
Message-ID: <066.c1f2a4adf7e0191db262644123c524e2@wordpress.org>

#54746: Comment Error in wp-login.php
------------------------------------+-------------------------------------
 Reporter:  alkesh7                 |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  6.0
Component:  Login and Registration  |     Version:
 Severity:  minor                   |  Resolution:
 Keywords:  has-patch               |     Focuses:  docs, coding-standards
------------------------------------+-------------------------------------
Changes (by peterwilsoncc):

 * Attachment "54746.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54746>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 04:56:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 04:56:02 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.1caecd876360c5d126663f88416bde20@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by peterwilsoncc):

 In [changeset:"52945" 52945]:
 {{{
 #!CommitTicketReference repository="" revision="52945"
 Registration/Login: Coding standards fixes for `wp-login.php`.

 Props alkesh7, Presskopp, audrasjb.
 Fixes #54746.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 04:56:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 04:56:02 -0000
Subject: [wp-trac] [WordPress Trac] #54746: Comment Error in wp-login.php
In-Reply-To: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
References: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
Message-ID: <066.0cebe6d1f84378cbe5984d4c7ea459c3@wordpress.org>

#54746: Comment Error in wp-login.php
------------------------------------+-------------------------------------
 Reporter:  alkesh7                 |       Owner:  peterwilsoncc
     Type:  enhancement             |      Status:  closed
 Priority:  normal                  |   Milestone:  6.0
Component:  Login and Registration  |     Version:
 Severity:  minor                   |  Resolution:  fixed
 Keywords:  has-patch               |     Focuses:  docs, coding-standards
------------------------------------+-------------------------------------
Changes (by peterwilsoncc):

 * owner:  (none) => peterwilsoncc
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52945" 52945]:
 {{{
 #!CommitTicketReference repository="" revision="52945"
 Registration/Login: Coding standards fixes for `wp-login.php`.

 Props alkesh7, Presskopp, audrasjb.
 Fixes #54746.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54746#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 08:09:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 08:09:12 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.58cca7e3942e526da549fedf8b9e478f@wordpress.org>

#32998: What's a weblog?
-----------------------------------------+----------------------
 Reporter:  johnjamesjacoby              |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  low                          |   Milestone:  6.0
Component:  Options, Meta APIs           |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+----------------------

Comment (by audrasjb):

 Speaking as a fr_FR GTE, the new string works for me in terms of i18n 👍

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 09:33:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 09:33:16 -0000
Subject: [wp-trac] [WordPress Trac] #55410: Update spacer block markup in
 patterns/templates registered by Twenty Twenty-Two and Core
Message-ID: <051.be435a9ce0bc8b07f88611d6558a384d@wordpress.org>

#55410: Update spacer block markup in patterns/templates registered by Twenty
Twenty-Two and Core
---------------------------+-----------------------------
 Reporter:  jsnajdr        |      Owner:  (none)
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Bundled Theme  |    Version:  trunk
 Severity:  normal         |   Keywords:  has-patch
  Focuses:                 |
---------------------------+-----------------------------
 The Twenty Twenty-Two theme registers block patterns and templates that
 contain deprecated markup for core/spacer blocks. They specify height
 attribute as a number ("height":50) instead of a string that includes
 units ("height":"50px"). Because of that, the block parser reports
 depreciation messages in browser console.

 The attached patch updates markup of block patterns and templates
 registered by modules that don't need to be compatible with pre-5.9
 WordPress: the Twenty Twenty-Two theme and Core itself.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55410>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 10:18:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 10:18:43 -0000
Subject: [wp-trac] [WordPress Trac] #55411: Deprecated error in WordPress
 5.9 on PHP 8.1
Message-ID: <057.e87e31fe46e8b38d8b6a8b2085d74bb7@wordpress.org>

#55411: Deprecated error in WordPress 5.9 on PHP 8.1
---------------------------+-----------------------------
 Reporter:  meysamnorouzi  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  General        |    Version:  5.9.2
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type
 string is deprecated in /opt/lampp/htdocs/wp/wp-includes/block-
 supports/layout.php on line 167

 Deprecated: setcookie(): Passing null to parameter #5 ($domain) of type
 string is deprecated in /opt/lampp/htdocs/wp/wp-includes/option.php on
 line 1109

 Deprecated: setcookie(): Passing null to parameter #5 ($domain) of type
 string is deprecated in /opt/lampp/htdocs/wp/wp-includes/option.php on
 line 1110

 Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string
 is deprecated in /opt/lampp/htdocs/wp/wp-includes/formatting.php on line
 2761

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55411>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 10:24:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 10:24:37 -0000
Subject: [wp-trac] [WordPress Trac] #55411: Deprecated error in
 WordPress 5.9 on PHP 8.1
In-Reply-To: <057.e87e31fe46e8b38d8b6a8b2085d74bb7@wordpress.org>
References: <057.e87e31fe46e8b38d8b6a8b2085d74bb7@wordpress.org>
Message-ID: <072.d6fc38d5116ff2f47416432ab13d2083@wordpress.org>

#55411: Deprecated error in WordPress 5.9 on PHP 8.1
---------------------------+------------------------------
 Reporter:  meysamnorouzi  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  5.9.2
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by meysamnorouzi):

 Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should
 either be compatible with ArrayAccess::offsetExists(mixed $offset): bool,
 or the #[\ReturnTypeWillChange] attribute should be used to temporarily
 suppress the notice in /opt/lampp/htdocs/wp/wp-
 includes/Requests/Cookie/Jar.php on line 63

 Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should
 either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or
 the #[\ReturnTypeWillChange] attribute should be used to temporarily
 suppress the notice in /opt/lampp/htdocs/wp/wp-
 includes/Requests/Cookie/Jar.php on line 73

 Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value)
 should either be compatible with ArrayAccess::offsetSet(mixed $offset,
 mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be
 used to temporarily suppress the notice in /opt/lampp/htdocs/wp/wp-
 includes/Requests/Cookie/Jar.php on line 89

 Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should
 either be compatible with ArrayAccess::offsetUnset(mixed $offset): void,
 or the #[\ReturnTypeWillChange] attribute should be used to temporarily
 suppress the notice in /opt/lampp/htdocs/wp/wp-
 includes/Requests/Cookie/Jar.php on line 102

 Deprecated: Return type of Requests_Cookie_Jar::getIterator() should
 either be compatible with IteratorAggregate::getIterator(): Traversable,
 or the #[\ReturnTypeWillChange] attribute should be used to temporarily
 suppress the notice in /opt/lampp/htdocs/wp/wp-
 includes/Requests/Cookie/Jar.php on line 111

 Deprecated: Return type of
 Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should
 either be compatible with ArrayAccess::offsetExists(mixed $offset): bool,
 or the #[\ReturnTypeWillChange] attribute should be used to temporarily
 suppress the notice in /opt/lampp/htdocs/wp/wp-
 includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

 Deprecated: Return type of
 Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either
 be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the
 #[\ReturnTypeWillChange] attribute should be used to temporarily suppress
 the notice in /opt/lampp/htdocs/wp/wp-
 includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

 Deprecated: Return type of
 Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should
 either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed
 $value): void, or the #[\ReturnTypeWillChange] attribute should be used to
 temporarily suppress the notice in /opt/lampp/htdocs/wp/wp-
 includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

 Deprecated: Return type of
 Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should
 either be compatible with ArrayAccess::offsetUnset(mixed $offset): void,
 or the #[\ReturnTypeWillChange] attribute should be used to temporarily
 suppress the notice in /opt/lampp/htdocs/wp/wp-
 includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55411#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 10:27:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 10:27:26 -0000
Subject: [wp-trac] [WordPress Trac] #13459: Conflict between post and
 page slugs/permalinks when permalink setting is set to /%postname%/
In-Reply-To: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
References: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
Message-ID: <071.26504b45c1397324edcaa1277e88a811@wordpress.org>

#13459: Conflict between post and page slugs/permalinks when permalink setting is
set to /%postname%/
--------------------------+-----------------------------
 Reporter:  jamescollins  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Permalinks    |     Version:  2.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------

Comment (by wpmarkuk):

 I am not sure how to to this:

 > Setting up a pull requests with some initially broken tests would be
 most helpful.

 Therefore, hopefully someone else can assist here.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/13459#comment:66>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 12:15:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 12:15:55 -0000
Subject: [wp-trac] [WordPress Trac] #54028: Fix improper use of the
 hooks API
In-Reply-To: <050.a5b774ca0bae1254e082498489808619@wordpress.org>
References: <050.a5b774ca0bae1254e082498489808619@wordpress.org>
Message-ID: <065.45818a8b72c4a1f7e655f4a37f6fb5be@wordpress.org>

#54028: Fix improper use of the hooks API
--------------------------+---------------------
 Reporter:  azaozz        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  General       |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  docs
--------------------------+---------------------

Comment (by audrasjb):

 I requested changes on a few Docblocks issues in the above PR, otherwise
 the patch looks good to me

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54028#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 12:21:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 12:21:57 -0000
Subject: [wp-trac] [WordPress Trac] #55412: Language "German (Austria)"
 outputs html lang incorrectly as "de-DE" not "de-AT" since WordPress
 version 5.9
Message-ID: <051.99371ec50aaee37bd8492a84a510e8a7@wordpress.org>

#55412: Language "German (Austria)" outputs html lang incorrectly as "de-DE" not
"de-AT" since WordPress version 5.9
--------------------------+-----------------------------
 Reporter:  simjost       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  I18N          |    Version:  5.9
 Severity:  major         |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Since version 5.9 including 5.9.1 and 5.9.2 the lang attribute in the html
 tag for the language/translation "German (Austria)" is incorrectly output
 as "de-DE". This would be correct for plain German, but for the region of
 Austria it should be "de-AT".

 Downgrading to 5.8.4 fixes the issue.
 Other languages/translations like "German (Swiss)" and "English (UK)" and
 "English (US)" don't have the same issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55412>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 12:34:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 12:34:52 -0000
Subject: [wp-trac] [WordPress Trac] #53370: Theme thumbnail/screenshot
 does not contain version string
In-Reply-To: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
References: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
Message-ID: <066.9cfcf0e5faaf67b44236fa9b5bf3535a@wordpress.org>

#53370: Theme thumbnail/screenshot does not contain version string
-------------------------+---------------------
 Reporter:  codente      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Themes       |     Version:  5.7.2
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------

Comment (by audrasjb):

 Patch refreshed via the above PR

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53370#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 12:59:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 12:59:36 -0000
Subject: [wp-trac] [WordPress Trac] #53370: Theme thumbnail/screenshot
 does not contain version string
In-Reply-To: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
References: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
Message-ID: <066.ed60ebe31675f6bd593c1509f754c4dc@wordpress.org>

#53370: Theme thumbnail/screenshot does not contain version string
-------------------------+-----------------------
 Reporter:  codente      |       Owner:  audrasjb
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  6.0
Component:  Themes       |     Version:  5.7.2
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+-----------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => accepted


Comment:

 Self assigning for final review and commit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53370#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 13:04:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 13:04:57 -0000
Subject: [wp-trac] [WordPress Trac] #55412: Language "German (Austria)"
 outputs html lang incorrectly as "de-DE" not "de-AT" since WordPress
 version 5.9
In-Reply-To: <051.99371ec50aaee37bd8492a84a510e8a7@wordpress.org>
References: <051.99371ec50aaee37bd8492a84a510e8a7@wordpress.org>
Message-ID: <066.b909f82ffcc3bb249191deb2392417c6@wordpress.org>

#55412: Language "German (Austria)" outputs html lang incorrectly as "de-DE" not
"de-AT" since WordPress version 5.9
--------------------------+----------------------
 Reporter:  simjost       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  I18N          |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by ocean90):

 * status:  new => closed
 * version:  5.9 =>
 * resolution:   => invalid
 * severity:  major => normal
 * milestone:  Awaiting Review =>


Comment:

 Hi @simjost, this attribute is a translatable string and I think a recent
 import of the de_DE translations has changed this accidentally. I have
 updated [https://translate.wordpress.org/projects/wp/dev/de-
 at/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=2379367&sort%5Bby%5D=translation_date_added&sort%5Bhow%5D=asc
 the translation] and also
 [https://translate.wordpress.org/projects/wp/dev/admin/de-
 at/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=4483146&sort%5Bby%5D=translation_date_added&sort%5Bhow%5D=asc
 this one].
 The new language pack with the updated translations should be available
 soon. cc: @pputzer

 Marking as invalid as it's not an issue with WordPress core.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55412#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 13:13:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 13:13:22 -0000
Subject: [wp-trac] [WordPress Trac] #54746: Comment Error in wp-login.php
In-Reply-To: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
References: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
Message-ID: <066.8797a619ee472ac79f7629a30259876d@wordpress.org>

#54746: Comment Error in wp-login.php
------------------------------------+-------------------------------------
 Reporter:  alkesh7                 |       Owner:  peterwilsoncc
     Type:  enhancement             |      Status:  reopened
 Priority:  normal                  |   Milestone:  6.0
Component:  Login and Registration  |     Version:
 Severity:  minor                   |  Resolution:
 Keywords:  has-patch               |     Focuses:  docs, coding-standards
------------------------------------+-------------------------------------
Changes (by SergeyBiryukov):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I think comments like "Main" have some benefit, as they denote various
 parts of the file, in this case separating function declarations from the
 main part.

 Instead of removing them, I think we can convert them to the multi-line
 format per the documentation standards:
 {{{
 /*
  * Main.
  */
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54746#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 13:36:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 13:36:16 -0000
Subject: [wp-trac] [WordPress Trac] #53370: Theme thumbnail/screenshot
 does not contain version string
In-Reply-To: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
References: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
Message-ID: <066.11d023d74cc8ebd8ff6bdd34955ce054@wordpress.org>

#53370: Theme thumbnail/screenshot does not contain version string
------------------------------+-----------------------
 Reporter:  codente           |       Owner:  audrasjb
     Type:  enhancement       |      Status:  accepted
 Priority:  normal            |   Milestone:  6.0
Component:  Themes            |     Version:  5.7.2
 Severity:  minor             |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch commit


Comment:

 I tested the last PR and it successfully adds the version string in each
 screenshot, on both WP-Admin and the Customizer.

 Marking as good for `commit`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53370#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 14:04:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 14:04:41 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.c1cd70ec68a6a7921fa6c3816dc22e70@wordpress.org>

#36949: Term exists should use get_terms internally
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  2.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note needs-testing commit                      |  performance
-------------------------------------------------+-------------------------
Changes (by Chouby):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 May I ask to introduce a new filter `term_exists_args`?

 Indeed each time `get_terms()` replaces a direct sql query, it introduces
 a breaking change. `get_terms()` is widely used and can be filtered with
 `terms_clauses`. The issue is that this filter will now be applied to
 `term_exists()` when it was not applied prior to [52921]. Currently there
 is no way to determine if the call to `get_terms()` is done by
 `term_exists()` or not, so we cannot disable the filter accordingly.
 Unless using an ugly hack with `debug_backtrace()`...

 A new filter `term_exists_args` would allow to work around the breaking
 chanege in an elegant way.

 Related:
 - [40994] introduced the filter `wp_get_object_term_args` after
 `wp_get_object_terms()` switched to use `get_terms()` since [38667].
 - #42104 Same issue for `transform_query()`
 - #54534 Same issue for `get_terms_by()`

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36949#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 14:19:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 14:19:06 -0000
Subject: [wp-trac] [WordPress Trac] #42104: Tax query transformations
 unintentionally filtered by 'terms_clauses'
In-Reply-To: <050.955ccf94f59ebc5bd90e9bfbcf94b923@wordpress.org>
References: <050.955ccf94f59ebc5bd90e9bfbcf94b923@wordpress.org>
Message-ID: <065.2aa410ccb2f65a8856288401d84ef4d6@wordpress.org>

#42104: Tax query transformations unintentionally filtered by 'terms_clauses'
--------------------------+------------------------------
 Reporter:  Chouby        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Taxonomy      |     Version:  4.9
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------
Changes (by Chouby):

 * Attachment "42104.2.patch" added.

 Add a new filter transform_query_args

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42104>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 14:26:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 14:26:36 -0000
Subject: [wp-trac] [WordPress Trac] #42104: Tax query transformations
 unintentionally filtered by 'terms_clauses'
In-Reply-To: <050.955ccf94f59ebc5bd90e9bfbcf94b923@wordpress.org>
References: <050.955ccf94f59ebc5bd90e9bfbcf94b923@wordpress.org>
Message-ID: <065.d3b0c1f01adf8c8dde801b1fa78f3132@wordpress.org>

#42104: Tax query transformations unintentionally filtered by 'terms_clauses'
--------------------------+------------------------------
 Reporter:  Chouby        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Taxonomy      |     Version:  4.9
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+------------------------------

Comment (by Chouby):

 To be consistent with what has been done with the filter
 `wp_get_object_terms_args` and the filter `get_term_by_args` I proposed in
 #54534 and `term_exists_args` I proposed in
 https://core.trac.wordpress.org/ticket/36949#comment:35, I propose to
 handle the issue by introducing a new filter `transform_query_args`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42104#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 14:42:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 14:42:14 -0000
Subject: [wp-trac] [WordPress Trac] #54788: Mute a video on WP with
 [video]
In-Reply-To: <051.bcfc6485b683c99e8d296f73cf338728@wordpress.org>
References: <051.bcfc6485b683c99e8d296f73cf338728@wordpress.org>
Message-ID: <066.9017fe8bec1a837810cb9f9b472830ab@wordpress.org>

#54788: Mute a video on WP with [video]
-------------------------+-----------------------
 Reporter:  prokium      |       Owner:  antpb
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  6.0
Component:  Media        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+-----------------------
Changes (by antpb):

 * owner:  (none) => antpb
 * status:  new => assigned


Comment:

 Assigning to myself to investigate landing this in 6.0

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54788#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 15:14:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 15:14:34 -0000
Subject: [wp-trac] [WordPress Trac] #54477: wp-cli vague: "Warning:
 Could not create directory."
In-Reply-To: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
References: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
Message-ID: <067.e21839210d2d334e99f24c52aedaf984@wordpress.org>

#54477: wp-cli vague: "Warning: Could not create directory."
----------------------------------------+---------------------
 Reporter:  gunterer                    |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Upgrade/Install             |     Version:  5.8
 Severity:  minor                       |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:
----------------------------------------+---------------------

Comment (by n8finch):

 @peterwilsoncc thanks! I'll be working on it in the next couple days.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54477#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 15:26:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 15:26:44 -0000
Subject: [wp-trac] [WordPress Trac] #55357: Add object_id property to
 WP_Term class
In-Reply-To: <056.7fe5b6eb2da6e602c92dd9f1fec29be1@wordpress.org>
References: <056.7fe5b6eb2da6e602c92dd9f1fec29be1@wordpress.org>
Message-ID: <071.7f484bef32831e1c70c65029949b6c4a@wordpress.org>

#55357: Add object_id property to WP_Term class
------------------------------------------------+--------------------------
 Reporter:  spacedmonkey                        |       Owner:  (none)
     Type:  defect (bug)                        |      Status:  new
 Priority:  normal                              |   Milestone:  Awaiting
                                                |  Review
Component:  Taxonomy                            |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  php82 needs-patch needs-unit-tests  |     Focuses:
------------------------------------------------+--------------------------

Comment (by jrf):

 @spacedmonkey I've done some test runs against PHP 8.2 already and guess
 what ? There are a hell of a lot more of these....

 I actually have prepared commits for the bulk of them already. Wouldn't
 mind doing a pair programming session to review them all. Would you be up
 for that ? /cc @hellofromTonya

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55357#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 15:28:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 15:28:22 -0000
Subject: [wp-trac] [WordPress Trac] #55357: Add object_id property to
 WP_Term class
In-Reply-To: <056.7fe5b6eb2da6e602c92dd9f1fec29be1@wordpress.org>
References: <056.7fe5b6eb2da6e602c92dd9f1fec29be1@wordpress.org>
Message-ID: <071.d79f81bf2adf6daa947683211d3804b9@wordpress.org>

#55357: Add object_id property to WP_Term class
------------------------------------------------+--------------------------
 Reporter:  spacedmonkey                        |       Owner:  (none)
     Type:  defect (bug)                        |      Status:  new
 Priority:  normal                              |   Milestone:  Awaiting
                                                |  Review
Component:  Taxonomy                            |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  php82 needs-patch needs-unit-tests  |     Focuses:
------------------------------------------------+--------------------------

Comment (by spacedmonkey):

 @jrf Do you have a ticket / patch that is ready for review?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55357#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 15:45:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 15:45:24 -0000
Subject: [wp-trac] [WordPress Trac] #55357: Add object_id property to
 WP_Term class
In-Reply-To: <056.7fe5b6eb2da6e602c92dd9f1fec29be1@wordpress.org>
References: <056.7fe5b6eb2da6e602c92dd9f1fec29be1@wordpress.org>
Message-ID: <071.ebe64f6c04458b8939504caca059e790@wordpress.org>

#55357: Add object_id property to WP_Term class
------------------------------------------------+--------------------------
 Reporter:  spacedmonkey                        |       Owner:  (none)
     Type:  defect (bug)                        |      Status:  new
 Priority:  normal                              |   Milestone:  Awaiting
                                                |  Review
Component:  Taxonomy                            |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  php82 needs-patch needs-unit-tests  |     Focuses:
------------------------------------------------+--------------------------

Comment (by jrf):

 @spacedmonkey No, I was waiting to open it for PHP 8.2 alpha 1, but we
 could transform this ticket to a meta ticket about dynamic properties and
 I could put a WIP branch up on GitHub and/or open a draft PR based on that
 branch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55357#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 16:07:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 16:07:07 -0000
Subject: [wp-trac] [WordPress Trac] #55411: Deprecated error in
 WordPress 5.9 on PHP 8.1
In-Reply-To: <057.e87e31fe46e8b38d8b6a8b2085d74bb7@wordpress.org>
References: <057.e87e31fe46e8b38d8b6a8b2085d74bb7@wordpress.org>
Message-ID: <072.ad9cd7590f6d0c890a1baa103d7e3eea@wordpress.org>

#55411: Deprecated error in WordPress 5.9 on PHP 8.1
---------------------------+------------------------------
 Reporter:  meysamnorouzi  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  5.9.2
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by DarkoG):

 Few more from me


 {{{
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Cookie_Jar::offsetExists($key) should either be compatible with
 ArrayAccess::offsetExists(mixed $offset): bool, or the
 #[\ReturnTypeWillChange] attribute should be used to temporarily suppress
 the notice in /home/vagrant/code/wp-includes/Requests/Cookie/Jar.php on
 line 63
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Cookie_Jar::offsetGet($key) should either be compatible with
 ArrayAccess::offsetGet(mixed $offset): mixed, or the
 #[\ReturnTypeWillChange] attribute should be used to temporarily suppress
 the notice in /home/vagrant/code/wp-includes/Requests/Cookie/Jar.php on
 line 73
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible
 with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the
 #[\ReturnTypeWillChange] attribute should be used to temporarily suppress
 the notice in /home/vagrant/code/wp-includes/Requests/Cookie/Jar.php on
 line 89
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Cookie_Jar::offsetUnset($key) should either be compatible with
 ArrayAccess::offsetUnset(mixed $offset): void, or the
 #[\ReturnTypeWillChange] attribute should be used to temporarily suppress
 the notice in /home/vagrant/code/wp-includes/Requests/Cookie/Jar.php on
 line 102
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Cookie_Jar::getIterator() should either be compatible with
 IteratorAggregate::getIterator(): Traversable, or the
 #[\ReturnTypeWillChange] attribute should be used to temporarily suppress
 the notice in /home/vagrant/code/wp-includes/Requests/Cookie/Jar.php on
 line 111
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should
 either be compatible with ArrayAccess::offsetExists(mixed $offset): bool,
 or the #[\ReturnTypeWillChange] attribute should be used to temporarily
 suppress the notice in /home/vagrant/code/wp-
 includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either
 be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the
 #[\ReturnTypeWillChange] attribute should be used to temporarily suppress
 the notice in /home/vagrant/code/wp-
 includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should
 either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed
 $value): void, or the #[\ReturnTypeWillChange] attribute should be used to
 temporarily suppress the notice in /home/vagrant/code/wp-
 includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should
 either be compatible with ArrayAccess::offsetUnset(mixed $offset): void,
 or the #[\ReturnTypeWillChange] attribute should be used to temporarily
 suppress the notice in /home/vagrant/code/wp-
 includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82
 [15-Mar-2022 22:22:33 UTC] PHP Deprecated:  Return type of
 Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be
 compatible with IteratorAggregate::getIterator(): Traversable, or the
 #[\ReturnTypeWillChange] attribute should be used to temporarily suppress
 the notice in /home/vagrant/code/wp-
 includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
 [15-Mar-2022 22:21:33 UTC] PHP Deprecated:  rtrim(): Passing null to
 parameter #1 ($string) of type string is deprecated in
 /home/vagrant/code/test/wp-includes/formatting.php on line 2761


 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55411#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 16:22:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 16:22:40 -0000
Subject: [wp-trac] [WordPress Trac] #55413: on user save apostrophes cause
 wp_mail error
Message-ID: <051.8003bc819a396728cbcaeef8b3e4971c@wordpress.org>

#55413: on user save apostrophes cause wp_mail error
----------------------------+-----------------------------
 Reporter:  dg12345         |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Users           |    Version:  5.9.2
 Severity:  normal          |   Keywords:  needs-patch
  Focuses:  administration  |
----------------------------+-----------------------------
 This is a follow-up to #18039.

 On user save from the admin the input is not unslashed and so the
 1. wordpress thinks that the email has changed, has it is compared against
 a unslashed value
 2. it uses the slashed input which isn't a valid email address to send the
 email was changed message

 Can we unslash the email input in the wp_insert_user and wp_update_user
 functions

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55413>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 16:32:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 16:32:14 -0000
Subject: [wp-trac] [WordPress Trac] #55414: Filter error suppression for
 individual DB query errors
Message-ID: <051.64447bc0d666004eb2821da1c21570a2@wordpress.org>

#55414: Filter error suppression for individual DB query errors
-------------------------+-----------------------------
 Reporter:  bpayton      |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:  5.9.2
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 Sometimes it is useful to suppress certain DB errors while logging others.

 For example, we have a set of standalone, core-like sites on WordPress.com
 where users can install arbitrary plugins and themes, and sometimes there
 are situations where query errors from third-party plugins flood a site's
 error logs. In some of those cases, the source of the error is not
 straightforward to address, and we would like to silence or throttle the
 errors so the site can continue using a given plugin without consuming its
 available disk space.

 Targeted suppression would be possible if WordPress supported a
 `suppress_query_error` filter that receives:
 * the current error suppression setting, defaulting to
 `$wpdb->suppress_errors`
 * the raw error string
 * the DB query associated with the error

 The result of filtering would determine whether `$wpdb->print_error()`
 returns early or logs the error, like `$wpdb->suppress_errors` does today.

 I have a patch for this and plan to submit a PR shortly after creating
 this ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55414>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 16:45:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 16:45:12 -0000
Subject: [wp-trac] [WordPress Trac] #55408: Error Formulario de Pago
 Woocommerce
In-Reply-To: <052.91c795e75031523fff44d6de590f4db0@wordpress.org>
References: <052.91c795e75031523fff44d6de590f4db0@wordpress.org>
Message-ID: <067.9f9a7309d4489a2e13ac9f00429774b9@wordpress.org>

#55408: Error Formulario de Pago Woocommerce
--------------------------+----------------------
 Reporter:  dantepgs      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by sabernhardt):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Hi and welcome to Trac!

 Sorry to hear you are having trouble with your site. Unfortunately, Trac
 is not the right place to get help with this. Please visit the support
 forums and/or open a topic there.

 [https://wordpress.org/support/plugin/woocommerce/ WooCommerce plugin
 support, (mostly) in English]
 [https://es.wordpress.org/support Foros de soporte (WordPress), en
 español]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55408#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 16:47:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 16:47:39 -0000
Subject: [wp-trac] [WordPress Trac] #55414: Filter error suppression for
 individual DB query errors
In-Reply-To: <051.64447bc0d666004eb2821da1c21570a2@wordpress.org>
References: <051.64447bc0d666004eb2821da1c21570a2@wordpress.org>
Message-ID: <066.ce62cc09bd2a232c2655f9e01a5d0305@wordpress.org>

#55414: Filter error suppression for individual DB query errors
--------------------------------------+------------------------------
 Reporter:  bpayton                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  General                   |     Version:  5.9.2
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------------

Comment (by bpayton):

 Created a PR here:
 https://github.com/WordPress/wordpress-develop/pull/2426

 This is the first time I've posted a PR instead of a patch. The PR seems
 easier to iterate on, but if you as maintainers prefer patches in Trac,
 please let me know. I'm happy to switch back to patches.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55414#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 17:46:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 17:46:55 -0000
Subject: [wp-trac] [WordPress Trac] #55415: Pluggable.php file is causing
 Fatal Errors
Message-ID: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>

#55415: Pluggable.php file is causing Fatal Errors
-----------------------------+-----------------------------
 Reporter:  ceceet           |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:
 Severity:  major            |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 I'm facing an issue with my WordPress install. I have two plugins getting
 a PHP Fatal Error due to the pluggable.php file on my site using PHP 8.0.
 My host is Closte (closte.com). The host doesn't allow changes to WP core
 files. The plugin developers are saying that the issue is WordPress and
 not the plugin. I'm using the latest versions of the plugins and the
 latest version of WP. Here is the error I'm seeing:

 1. PHP Fatal error: Uncaught Error: Call to undefined function
 wp_get_current_user() in /wp-content/plugins/updraftcentral/site-
 management.php:486

 Would really prefer not to downgrade my PHP version so any help would be
 appreciated.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 18:16:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 18:16:55 -0000
Subject: [wp-trac] [WordPress Trac] #55415: Pluggable.php file is
 causing Fatal Errors
In-Reply-To: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
References: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
Message-ID: <065.b9885088f7f26d7a33c7f450c63db24f@wordpress.org>

#55415: Pluggable.php file is causing Fatal Errors
-----------------------------+------------------------------
 Reporter:  ceceet           |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:
 Severity:  major            |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by afragen):

 The solution is to call your code in a callback from a hook like (`init`,
 `admin_init`, `plugins_loaded`) etc.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 18:29:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 18:29:03 -0000
Subject: [wp-trac] [WordPress Trac] #55415: Pluggable.php file is
 causing Fatal Errors
In-Reply-To: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
References: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
Message-ID: <065.ad33a189bcf1a40bf7d06ace699d8f09@wordpress.org>

#55415: Pluggable.php file is causing Fatal Errors
-----------------------------+------------------------------
 Reporter:  ceceet           |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:
 Severity:  major            |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by ceceet):

 Replying to [comment:1 afragen]:
 > The solution is to call your code in a callback from a hook like
 (`init`, `admin_init`, `plugins_loaded`) etc.


 Cool, thanks. I'll give that a shot.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 18:46:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 18:46:14 -0000
Subject: [wp-trac] [WordPress Trac] #55415: Pluggable.php file is
 causing Fatal Errors
In-Reply-To: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
References: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
Message-ID: <065.31c141d0f37d7e9a3bef201746525539@wordpress.org>

#55415: Pluggable.php file is causing Fatal Errors
-------------------------------+------------------------------
 Reporter:  ceceet             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Plugins            |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by costdev):

 * keywords:   => reporter-feedback
 * component:  Upgrade/Install => Plugins


Comment:

 Hi @ceceet! Welcome to Trac and thanks for opening this ticket.

 Some additional info:
 - The UpdraftCentral plugin calls `wp_get_current_user()` in a `shutdown`
 callback.
 - See [https://plugins.trac.wordpress.org/browser/updraftcentral/trunk
 /site-management.php#L484 here for the call] and
 [https://plugins.trac.wordpress.org/browser/updraftcentral/trunk/site-
 management.php#L136here for the hook].
 - This has existed within the plugin for quite a long time.

 -----

 I created a small plugin to test calling `wp_get_current_user()` in a
 `shutdown` callback:

 {{{#!php
 <?php
 /**
  * Plugin Name: #55415 - `wp_get_current_user()` in a `shutdown` callback.
  * Description: Runs `wp_get_current_user()` in a `shutdown` callback.
  * Author: WordPress Contributors
  */

 add_action( 'shutdown', 'try_wp_get_current_user' );

 function try_wp_get_current_user() {
         wp_get_current_user();
 }
 }}}

 There was no Fatal Error on PHP 7.4 or PHP 8.0.
 -----
 @ceceet if you have any additional information from the plugin developers
 about how they determined that this is an issue within WordPress Core
 rather than the plugin, that would be a big help in determining how best
 to resolve this issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 18:46:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 18:46:42 -0000
Subject: [wp-trac] [WordPress Trac] #55415: Pluggable.php file is
 causing Fatal Errors
In-Reply-To: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
References: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
Message-ID: <065.ca559020fc6a3be5166c4c9cba30d766@wordpress.org>

#55415: Pluggable.php file is causing Fatal Errors
-------------------------------+------------------------------
 Reporter:  ceceet             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Plugins            |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by SergeyBiryukov):

 Hi there, welcome to WordPress Trac! Thanks for the ticket.

 > The plugin developers are saying that the issue is WordPress and not the
 plugin.

 It looks like the issue comes from the
 [https://wordpress.org/plugins/updraftcentral/ UpdraftCentral Dashboard]
 plugin. Could the plugin authors explain what they think the issue is?

 Generally, this can happen if the plugin calls the `wp_get_current_user()`
 function too early. The solution to that, as noted above, would be to call
 it on the `plugins_loaded` hook or later.

 In this case, however, the plugin calls `wp_get_current_user()` in the
 [https://plugins.trac.wordpress.org/browser/updraftcentral/tags/0.8.19
 /site-management.php?marks=486#L481 UpdraftCentral::schedule_event()]
 method, which is
 [https://plugins.trac.wordpress.org/browser/updraftcentral/tags/0.8.19
 /site-management.php?marks=136#L134 attached to the 'shutdown' hook]. This
 should be OK, so there might be other things involved here. Maybe the
 error is only triggered when WordPress is loaded in the `SHORTINIT` mode
 (which skips most of the APIs), or maybe it's triggered by another plugin.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 18:50:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 18:50:49 -0000
Subject: [wp-trac] [WordPress Trac] #55415: Pluggable.php file is
 causing Fatal Errors
In-Reply-To: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
References: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
Message-ID: <065.e914deb146c3399f773b966dd597e261@wordpress.org>

#55415: Pluggable.php file is causing Fatal Errors
-------------------------------+------------------------------
 Reporter:  ceceet             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Plugins            |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by ceceet):

 Replying to [comment:3 costdev]:
 > Hi @ceceet! Welcome to Trac and thanks for opening this ticket.
 >
 > Some additional info:
 > - The UpdraftCentral plugin calls `wp_get_current_user()` in a
 `shutdown` callback.
 > - See [https://plugins.trac.wordpress.org/browser/updraftcentral/trunk
 /site-management.php#L484 here for the call] and
 [https://plugins.trac.wordpress.org/browser/updraftcentral/trunk/site-
 management.php#L136here for the hook].
 > - This has existed within the plugin for quite a long time.
 >
 > -----
 >
 > I created a small plugin to test calling `wp_get_current_user()` in a
 `shutdown` callback:
 >
 > {{{#!php
 > <?php
 > /**
 >  * Plugin Name: #55415 - `wp_get_current_user()` in a `shutdown`
 callback.
 >  * Description: Runs `wp_get_current_user()` in a `shutdown` callback.
 >  * Author: WordPress Contributors
 >  */
 >
 > add_action( 'shutdown', 'try_wp_get_current_user' );
 >
 > function try_wp_get_current_user() {
 >       wp_get_current_user();
 > }
 > }}}
 >
 > There was no Fatal Error on PHP 7.4 or PHP 8.0.
 > -----
 > @ceceet if you have any additional information from the plugin
 developers about how they determined that this is an issue within
 WordPress Core rather than the plugin, that would be a big help in
 determining how best to resolve this issue.

 Thanks for the detailed response! I submitted a support ticket to updraft
 and they just decided it was a problem the pluggable.php and not anything
 on their end. I kinda think they're full of it but thought I'd post here
 first. They didn't log into the site and try to change anything so I don't
 know how they really came to that decision.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 18:53:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 18:53:46 -0000
Subject: [wp-trac] [WordPress Trac] #55415: Pluggable.php file is
 causing Fatal Errors
In-Reply-To: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
References: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
Message-ID: <065.ba69d2721af6c163faa38409a38fad1d@wordpress.org>

#55415: Pluggable.php file is causing Fatal Errors
-------------------------------+------------------------------
 Reporter:  ceceet             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Plugins            |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by ceceet):

 Thanks for the detailed response! I submitted a support ticket to updraft
 and they just decided it was a problem with the pluggable.php and not
 anything on their end. I kinda think they're full of it but thought I'd
 post here first. They didn't log into the site and try to change anything
 so I don't know how they really came to that decision.

 Replying to [comment:4 SergeyBiryukov]:
 > Hi there, welcome to WordPress Trac! Thanks for the ticket.
 >
 > > The plugin developers are saying that the issue is WordPress and not
 the plugin.
 >
 > It looks like the issue comes from the
 [https://wordpress.org/plugins/updraftcentral/ UpdraftCentral Dashboard]
 plugin. Could the plugin authors explain what they think the issue is?
 >
 > Generally, this can happen if the plugin calls the
 `wp_get_current_user()` function too early. The solution to that, as noted
 above, would be to call it on the `plugins_loaded` hook or later.
 >
 > In this case, however, the plugin calls `wp_get_current_user()` in the
 [https://plugins.trac.wordpress.org/browser/updraftcentral/tags/0.8.19
 /site-management.php?marks=486#L481 UpdraftCentral::schedule_event()]
 method, which is
 [https://plugins.trac.wordpress.org/browser/updraftcentral/tags/0.8.19
 /site-management.php?marks=136#L134 attached to the 'shutdown' hook]. This
 should be OK, so there might be other things involved here. Maybe the
 error is only triggered when WordPress is loaded in the `SHORTINIT` mode
 (which skips most of the APIs), or maybe it's triggered by another plugin.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 19:04:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 19:04:51 -0000
Subject: [wp-trac] [WordPress Trac] #55415: Pluggable.php file is
 causing Fatal Errors
In-Reply-To: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
References: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
Message-ID: <065.21b241e4dc77b554f278e711085164d8@wordpress.org>

#55415: Pluggable.php file is causing Fatal Errors
-------------------------------+------------------------------
 Reporter:  ceceet             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Plugins            |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by costdev):

 I installed the plugin into 6.0-alpha (tested on PHP 8.0 and PHP 7.4) and
 I didn't get any errors before or after adding the shortcode as
 instructed.

 > Maybe the error is only triggered when WordPress is loaded in the
 `SHORTINIT` mode (which skips most of the APIs), or maybe it's triggered
 by another plugin.

 This is a good next step. @ceceet Have you tried disabling all other
 plugins and switching to a default theme?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 19:06:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 19:06:42 -0000
Subject: [wp-trac] [WordPress Trac] #55415: Pluggable.php file is
 causing Fatal Errors
In-Reply-To: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
References: <050.d3a04b1736323a240e8ce9817cf68690@wordpress.org>
Message-ID: <065.f1e3cbdd6007606a50c2e4fb2ed4ad56@wordpress.org>

#55415: Pluggable.php file is causing Fatal Errors
-------------------------------+------------------------------
 Reporter:  ceceet             |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Plugins            |     Version:
 Severity:  major              |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by ceceet):

 I currently have this installed on a multisite, so updraft only runs on
 the network admin as far as I know. I could try to disable the theme I'm
 using on the main site to see if that makes a difference if you think it
 would work.

 Replying to [comment:7 costdev]:
 > I installed the plugin into 6.0-alpha (tested on PHP 8.0 and PHP 7.4)
 and I didn't get any errors before or after adding the shortcode as
 instructed.
 >
 > > Maybe the error is only triggered when WordPress is loaded in the
 `SHORTINIT` mode (which skips most of the APIs), or maybe it's triggered
 by another plugin.
 >
 > This is a good next step. @ceceet Have you tried disabling all other
 plugins and switching to a default theme?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55415#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 19:30:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 19:30:30 -0000
Subject: [wp-trac] [WordPress Trac] #55416: Version 5.9.2 upgrade - Elementor
Message-ID: <055.4a1d874d1418a55db56d13844cde2fe6@wordpress.org>

#55416: Version 5.9.2 upgrade - Elementor
-----------------------------+-----------------------------
 Reporter:  juliekoehne      |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:  5.9.2
 Severity:  major            |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 After upgrading to WP Version 5.9.2, I noticed that anything new I add to
 the page that should be seen by all will not display until after I login.
 https://lawlibrary.hamiltoncountyohio.gov/cle-evaluation/
 Should display a Gravity form.  It only displays the title of the form.
 How can I fix this problem?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55416>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 20:08:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 20:08:59 -0000
Subject: [wp-trac] [WordPress Trac] #54916: Admin panel's "Customizer"
 sub menu is replaced with "Widgets" for block based themes
In-Reply-To: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
References: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
Message-ID: <066.47cf4a269da5a7bce68ad5c3f4e11b9a@wordpress.org>

#54916: Admin panel's "Customizer" sub menu is replaced with "Widgets" for block
based themes
-------------------------------------+-----------------------
 Reporter:  Rufus87                  |       Owner:  audrasjb
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  5.9.3
Component:  Administration           |     Version:  5.9
 Severity:  major                    |  Resolution:
 Keywords:  2nd-opinion needs-patch  |     Focuses:
-------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch 2nd-opinion => 2nd-opinion needs-patch
 * owner:  (none) => audrasjb
 * status:  new => accepted


Comment:

 As from @hellofromtonya’s comment in the existing PR, moving the widget
 position from 7 to 8 will probably introduce other regressions, so it’s
 better to try to find another option, something doable for a point
 release.

 I’d suggest to go with @ironprogrammer’s proposal:

 > Another option could be to remove the static position of that menu item.
 It would then fall in place where it currently is in a classic theme, or
 be “pushed down” by any extenders who are attempting to prioritize new
 menu items or set an explicit order. Worst case in this scenario is that
 “Widgets” doesn’t appear in an exact slot. But the benefit is that it
 would no longer be subject to being overwritten due to specific indexes.

 …and we can still use a wp_is_block_theme() check to make sure this is
 only applied to block based themes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54916#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 20:18:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 20:18:04 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to
 allow for named parameters in WP 6.0
In-Reply-To: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
References: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
Message-ID: <072.9409018e6676d016607f41746f06bca3@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
----------------------------+---------------------
 Reporter:  peterwilsoncc   |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  php80           |     Focuses:
----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52946" 52946]:
 {{{
 #!CommitTicketReference repository="" revision="52946"
 Code Modernization: Rename parameters that use reserved keywords in `wp-
 admin/includes/class-custom-image-header.php`.

 While using reserved PHP keywords as parameter name labels is allowed, in
 the context of function calls using named parameters in PHP 8.0+, this
 will easily lead to confusion. To avoid that, it is recommended not to use
 reserved keywords as function parameter names.

 This commit renames the `$object` variable in `Custom_Image_Header` class
 methods to `$attachment` for clarity and consistency, as the variable type
 is actually an array, and updates the documentation accordingly.

 Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
 See #55327.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55327#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 20:22:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 20:22:58 -0000
Subject: [wp-trac] [WordPress Trac] #55015: Site Editor not working for
 TwentyTwentyTwo Child theme
In-Reply-To: <057.2d2b97539ca085d46839b9afdcd566fc@wordpress.org>
References: <057.2d2b97539ca085d46839b9afdcd566fc@wordpress.org>
Message-ID: <072.2e3535f116c880400b2d6aade298c53e@wordpress.org>

#55015: Site Editor not working for TwentyTwentyTwo Child theme
---------------------------+---------------------
 Reporter:  mervinpraison  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  5.9.3
Component:  Bundled Theme  |     Version:  5.9
 Severity:  major          |  Resolution:
 Keywords:  needs-patch    |     Focuses:
---------------------------+---------------------

Comment (by audrasjb):

 I also reported this on Gutenberg repository, just in case it can be fixed
 directly upstream.
 https://github.com/WordPress/gutenberg/issues/39556

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55015#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 20:26:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 20:26:05 -0000
Subject: [wp-trac] [WordPress Trac] #55172: Twenty Twenty-Two: Add
 "Accessibility Ready" tag to theme in repository
In-Reply-To: <047.b9d143ec205798743730f710212f590b@wordpress.org>
References: <047.b9d143ec205798743730f710212f590b@wordpress.org>
Message-ID: <062.9d731ff40a51108fb6eed57d755d855b@wordpress.org>

#55172: Twenty Twenty-Two: Add "Accessibility Ready" tag to theme in repository
----------------------------+----------------------------
 Reporter:  bph             |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  5.9.3
Component:  Bundled Theme   |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  accessibility
----------------------------+----------------------------
Changes (by audrasjb):

 * type:  enhancement => task (blessed)


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55172#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 20:27:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 20:27:10 -0000
Subject: [wp-trac] [WordPress Trac] #55172: Twenty Twenty-Two: Add
 "Accessibility Ready" tag to theme in repository
In-Reply-To: <047.b9d143ec205798743730f710212f590b@wordpress.org>
References: <047.b9d143ec205798743730f710212f590b@wordpress.org>
Message-ID: <062.0fe445afdb17128897465bb812b6e93c@wordpress.org>

#55172: Twenty Twenty-Two: Add "Accessibility Ready" tag to theme in repository
----------------------------+----------------------------
 Reporter:  bph             |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  5.9.3
Component:  Bundled Theme   |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  accessibility
----------------------------+----------------------------

Comment (by audrasjb):

 I converted this to a task, since the Gutenberg team need to collaborate
 with the Theme and Accessibility teams to help moving this forward.
 Hopefully it can move toward a resolution in the next weeks :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55172#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 20:34:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 20:34:46 -0000
Subject: [wp-trac] [WordPress Trac] #54905: PHP notice while accessing
 Customizer
In-Reply-To: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
References: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
Message-ID: <066.ac1e4abd234f2f391fe4a22c0840836d@wordpress.org>

#54905: PHP notice while accessing Customizer
-------------------------------------------------+-------------------------
 Reporter:  Boniu91                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info has-screenshots                   |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 Hello @costdev, are you still working on this PR?

 Also @azouamauriac feel free to propose a new patch/PR to address the
 issue you underlined in the PR :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54905#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 20:40:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 20:40:45 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.a9d2623d17cee30b2bac03c4267b4948@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots needs-design-        |     Focuses:  ui, ui-
  feedback has-patch i18n-change needs-copy-     |  copy
  review                                         |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * owner:  (none) => marybaum
 * status:  new => assigned


Comment:

 As per today's bug scrub, I'maAssigning @marybaum for copy review.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:29>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 21:25:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 21:25:47 -0000
Subject: [wp-trac] [WordPress Trac] #55417: Text Highlighting Broken
Message-ID: <050.95d872d4aea23a3a846115c0c388e364@wordpress.org>

#55417: Text Highlighting Broken
-------------------------------+-----------------------------
 Reporter:  notgeo             |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Editor             |    Version:  5.9.2
 Severity:  normal             |   Keywords:
  Focuses:  ui, accessibility  |
-------------------------------+-----------------------------
 Trying to add a custom HEX, RGB, or HSL colors using the UI is just
 broken. Trying to input values or paste in values doesn't work. I have
 tried disabling all plugins and have tested it on multiple wordpress.org
 sites. Editing the value in the code editor still works, but it's just
 less convenient. Hopefully, this can get fixed next update, thanks!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55417>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 21:30:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 21:30:36 -0000
Subject: [wp-trac] [WordPress Trac] #55417: Text Highlighting Broken
In-Reply-To: <050.95d872d4aea23a3a846115c0c388e364@wordpress.org>
References: <050.95d872d4aea23a3a846115c0c388e364@wordpress.org>
Message-ID: <065.578f531847633e003f41f5e4180298b2@wordpress.org>

#55417: Text Highlighting Broken
--------------------------------+--------------------------------
 Reporter:  notgeo              |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Editor              |     Version:  5.9.2
 Severity:  normal              |  Resolution:
 Keywords:  needs-testing-info  |     Focuses:  ui, accessibility
--------------------------------+--------------------------------
Changes (by afragen):

 * keywords:   => needs-testing-info


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55417#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 22:07:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 22:07:17 -0000
Subject: [wp-trac] [WordPress Trac] #55414: Filter error suppression for
 individual DB query errors
In-Reply-To: <051.64447bc0d666004eb2821da1c21570a2@wordpress.org>
References: <051.64447bc0d666004eb2821da1c21570a2@wordpress.org>
Message-ID: <066.18a305dddb0213c7b26efcdbb9ff32f7@wordpress.org>

#55414: Filter error suppression for individual DB query errors
--------------------------------------+------------------------------
 Reporter:  bpayton                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  General                   |     Version:  5.9.2
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------------

Comment (by peterwilsoncc):

 Replying to [comment:2 bpayton]:
 > This is the first time I've posted a PR instead of a patch. The PR seems
 easier to iterate on, but if you as maintainers prefer patches in Trac,
 please let me know. I'm happy to switch back to patches.

 A PR is perfect, many of the maintainers and committers use GitHub rather
 than patches for the same reason.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55414#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 22:20:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 22:20:19 -0000
Subject: [wp-trac] [WordPress Trac] #53370: Theme thumbnail/screenshot
 does not contain version string
In-Reply-To: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
References: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
Message-ID: <066.dfd24aa794c917fa44292960a71e703b@wordpress.org>

#53370: Theme thumbnail/screenshot does not contain version string
------------------------------+-----------------------
 Reporter:  codente           |       Owner:  audrasjb
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:  6.0
Component:  Themes            |     Version:  5.7.2
 Severity:  minor             |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52947" 52947]:
 {{{
 #!CommitTicketReference repository="" revision="52947"
 Themes: Add version to theme screenshot URL for better browser cache
 handling.

 This change appends the theme version number to the URL of screenshots
 that appear in various place of the WordPress Admin. As a result, browsers
 will be able to refresh the screenshot as needed when the theme is
 updated.

 Props codente, desrosj, audrasjb, SergeyBiryukov.
 Fixes #53370.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53370#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 23:14:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 23:14:32 -0000
Subject: [wp-trac] [WordPress Trac] #51857: Add rollback for failed
 plugin/theme updates
In-Reply-To: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
References: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
Message-ID: <065.523412d09562360de5800fdbc0050a4b@wordpress.org>

#51857: Add rollback for failed plugin/theme updates
-------------------------------------------------+-------------------------
 Reporter:  pbiron                               |       Owner:  pbiron
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  early has-testing-info needs-unit-   |     Focuses:
  tests needs-testing has-patch dev-feedback     |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  early has-testing-info needs-unit-tests needs-testing has-
     patch =>
     early has-testing-info needs-unit-tests needs-testing has-patch dev-
     feedback


Comment:

 Per the discussion in the bug scrub, I'm adding the `dev-feedback` keyword
 to get as much input on this as possible. Take a look at the PR and the
 comments and give your thoughts to help us land this in 6.0!

 This touches several other tickets: #54166, #54543 and #54351. As such,
 this would greatly benefit from additional testing, particularly on
 different filesystems.

 @pbiron has extensively tested in `WP_Filesystem_ftpext`, and quite a few
 have tested with `WP_Filesystem_Direct` on Windows, Mac, Linux,
 VirtualBox, Hyper-V etc.

 Additional testing on `WP_Filesystem_ftpsockets` and `WP_Filesystem_ssh2`
 to ensure that subtle differences don't cause any issues would be great!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51857#comment:199>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 23:25:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 23:25:49 -0000
Subject: [wp-trac] [WordPress Trac] #54351: Checking for temp update
 directories may throw warnings
In-Reply-To: <051.12da4c47867c774d67084d53e0d23918@wordpress.org>
References: <051.12da4c47867c774d67084d53e0d23918@wordpress.org>
Message-ID: <066.60626ccf99a8f44d1e3091f999ebe3f2@wordpress.org>

#54351: Checking for temp update directories may throw warnings
-------------------------------------------------+-------------------------
 Reporter:  Clorith                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Site Health                          |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch needs-testing early      |     Focuses:
  dev-feedback                                   |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  needs-patch needs-testing early => needs-patch needs-testing
     early dev-feedback
 * version:  5.9 => trunk


Comment:

 Per the discussion in the bug scrub, I'm adding the `dev-feedback` keyword
 to get as much input on this as possible.

 See [https://github.com/WordPress/wordpress-develop/pull/2225 PR 2225],
 which touches this ticket as well as #54166, #54543 and #51857. As such,
 this would greatly benefit from additional testing, particularly on
 different filesystems.

 @pbiron has extensively tested in `WP_Filesystem_ftpext` and may be able
 to expand more on results pertinent to this ticket.

 Changing the version to `trunk` as [51815] was reverted in [52351] prior
 to 5.9's release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54351#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 23:26:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 23:26:58 -0000
Subject: [wp-trac] [WordPress Trac] #51857: Add rollback for failed
 plugin/theme updates
In-Reply-To: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
References: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
Message-ID: <065.6d752a96339ba15a518ae0bd426f96e1@wordpress.org>

#51857: Add rollback for failed plugin/theme updates
-------------------------------------------------+-------------------------
 Reporter:  pbiron                               |       Owner:  pbiron
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  early has-testing-info needs-unit-   |     Focuses:
  tests needs-testing has-patch dev-feedback     |
-------------------------------------------------+-------------------------

Comment (by pbiron):

 Replying to [comment:199 costdev]:
 > @pbiron has extensively tested in `WP_Filesystem_ftpext`, and quite a
 few have tested with `WP_Filesystem_Direct` on Windows, Mac, Linux,
 VirtualBox, Hyper-V etc.
 >
 > Additional testing on `WP_Filesystem_ftpsockets` and
 `WP_Filesystem_ssh2` to ensure that subtle differences don't cause any
 issues would be great!

 I'll be able to do testing on `WP_Filesystem_ftpsockets` and
 `WP_Filesystem_ssh2` this weekend.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51857#comment:200>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 23:28:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 23:28:45 -0000
Subject: [wp-trac] [WordPress Trac] #54166: Updating errors due to PHP
 timeouts
In-Reply-To: <052.3e7bf041d237a674c47a46aaf40d2b72@wordpress.org>
References: <052.3e7bf041d237a674c47a46aaf40d2b72@wordpress.org>
Message-ID: <067.ad731575f7d7a53e917d09a0a314103b@wordpress.org>

#54166: Updating errors due to PHP timeouts
-------------------------------------------------+-------------------------
 Reporter:  aristath                             |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch early needs-testing dev-   |     Focuses:
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  has-patch early needs-testing => has-patch early needs-testing
     dev-feedback
 * version:  5.9 => trunk


Comment:

 Per the discussion in the bug scrub, I'm adding the `dev-feedback` keyword
 to get as much input on this as possible.

 This ticket is touched by [https://github.com/WordPress/wordpress-
 develop/pull/2225 PR 2225]. As such, this would greatly benefit from
 additional testing, particularly on different filesystems. See
 [https://core.trac.wordpress.org/ticket/51857#comment:199 this comment]
 for the current state of things.

 Changing the version to `trunk` as [51815] was reverted in [52351] prior
 to 5.9's release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54166#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 23:34:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 23:34:07 -0000
Subject: [wp-trac] [WordPress Trac] #49278: Improve meta query
In-Reply-To: <053.f456e8069a5775465fadeab7ad94e33c@wordpress.org>
References: <053.f456e8069a5775465fadeab7ad94e33c@wordpress.org>
Message-ID: <068.78d43e9c6a0f60b637496aaee9eb8c1c@wordpress.org>

#49278: Improve meta query
-------------------------------------------------+-------------------------
 Reporter:  jillebehm                            |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Query                                |     Version:  5.3.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback early early-  |     Focuses:
  like-actually-early has-unit-tests             |  performance
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  has-patch dev-feedback early early-like-actually-early => has-
     patch dev-feedback early early-like-actually-early has-unit-tests


Comment:

 Per the discussion in the bug scrub:

 - I'm adding the `needs-unit-tests` keyword so that this can be evaluated
 by the test team.
 - @craigfrancis has kindly offered to take a look at the patch when he's
 available.
 - While this ticket already has the `performance` focus, it may be worth
 reaching out in `#performance` to get eyes on this ticket when the
 approach has been given feedback.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49278#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 23:39:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 23:39:09 -0000
Subject: [wp-trac] [WordPress Trac] #46748: authenticate filter hook
 does not behave as expected for priority values less than 20
In-Reply-To: <056.7e637e992c6213b69d9dc692003b41c1@wordpress.org>
References: <056.7e637e992c6213b69d9dc692003b41c1@wordpress.org>
Message-ID: <071.c33acf3cac641213c33531abe50a5e03@wordpress.org>

#46748: authenticate filter hook does not behave as expected for priority values
less than 20
-------------------------------------------------+-------------------------
 Reporter:  robert.peake                         |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Login and Registration               |     Version:  3.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests early needs-patch     |     Focuses:
  dev-feedback                                   |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  has-unit-tests early needs-patch => has-unit-tests early
     needs-patch dev-feedback


Comment:

 Per the discussion in the bug scrub, I'm adding `dev-feedback` to this
 ticket to clarify its current state.

 @SergeyBiryukov has kindly offered to take a look at the issue to help
 move this one forward. Everyone reading this ticket is encouraged to take
 a look through the discussion above and [https://github.com/WordPress
 /wordpress-develop/pull/1903#discussion_r750797774 this discussion] on the
 PR. All input and feedback is welcome to help us land this in 6.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46748#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 17 23:54:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 17 Mar 2022 23:54:19 -0000
Subject: [wp-trac] [WordPress Trac] #54589: Audit and preload current
 "from" version files into memory before upgrading filesystem to the "to"
 version
In-Reply-To: <058.2a41f8a958a91084b1dda258d6b2cacc@wordpress.org>
References: <058.2a41f8a958a91084b1dda258d6b2cacc@wordpress.org>
Message-ID: <073.fc3b17a1cf3ba2d1a0827a56768ec448@wordpress.org>

#54589: Audit and preload current "from" version files into memory before upgrading
filesystem to the "to" version
--------------------------------------------+---------------------
 Reporter:  hellofromTonya                  |       Owner:  (none)
     Type:  enhancement                     |      Status:  new
 Priority:  normal                          |   Milestone:  6.0
Component:  Upgrade/Install                 |     Version:  2.7
 Severity:  normal                          |  Resolution:
 Keywords:  early has-patch has-unit-tests  |     Focuses:
--------------------------------------------+---------------------
Changes (by costdev):

 * version:   => 2.7
 * type:  defect (bug) => enhancement


Comment:

 Per the discussion on the bug scrub, I'm changing this ticket to an
 `enhancement`, as it proposes a general improvement as a follow-up to
 #54546 and changing the `Version` to `2.7`.

 While the `WP_Upgrader` and `Core_Upgrader` classes were introduced in
 `2.8`, `wp-admin/includes/update-core.php` was introduced in `2.7`, and
 the copying of Core files via `_copy_dir()` - initially, `copy_dir()` -
 was introduced in [8595]. From this point onwards, there was no mechanism
 to ensure required resources were preloaded.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54589#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 00:29:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 00:29:33 -0000
Subject: [wp-trac] [WordPress Trac] #13459: Conflict between post and
 page slugs/permalinks when permalink setting is set to /%postname%/
In-Reply-To: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
References: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
Message-ID: <071.eeaeadea5adc527d01e9fbb9fc115fc4@wordpress.org>

#13459: Conflict between post and page slugs/permalinks when permalink setting is
set to /%postname%/
--------------------------+-----------------------------
 Reporter:  jamescollins  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Permalinks    |     Version:  2.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------

Comment (by webcommsat):

 I think this post by @desrosj might help @wpmarkuk. Also welcome to Core
 Trac and thanks for being involved to help move this issue forward.
 Replying to [comment:66 wpmarkuk]:
 > I am not sure how to to this:
 >
 > > Setting up a pull requests with some initially broken tests would be
 most helpful.
 >
 > Therefore, hopefully someone else can assist here.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/13459#comment:67>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 01:18:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 01:18:04 -0000
Subject: [wp-trac] [WordPress Trac] #32747: WP Admin Menus/SubMenus
 Overlap in small screen
In-Reply-To: <053.19f81590b59ff77c2a9b31983b4caf91@wordpress.org>
References: <053.19f81590b59ff77c2a9b31983b4caf91@wordpress.org>
Message-ID: <068.81c482ba4e4078c05e231526d952bd20@wordpress.org>

#32747: WP Admin Menus/SubMenus Overlap in small screen
----------------------------+-------------------------------------
 Reporter:  turtlepod       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Administration  |     Version:  4.2.2
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  ui, accessibility, css
----------------------------+-------------------------------------

Comment (by webcommsat):

 Really happy to find this ticket getting some attention in the scrub
 earlier. Thanks @chaion07 and everyone at the scrub. I can replicate the
 issues as reported in 5.9.2 and two earlier versions. I have experienced
 this issue for a long time when using a smaller window on handheld and
 tablet devices, and  even when the page is reloaded. Thanks for moving
 this forward.

 Replying to [comment:15 chaion07]:
 > Thanks @turtlepod for reporting this. We reviewed the ticket during a
 recent bug scrub session. Here's a summary of the feedback provided by the
 team:
 >
 > 01. The issue can be reproduced on 5.9.2
 > 02. The issue seems to appear when you resize the window but when you
 reload then it seems to work just fine
 > 03. There are cases though when the issue would still appear after the
 page has been loaded- as long as the window is small enough in terms of
 width and height. Opening the submenus would produce the issue.
 > 04. Its more likely to happen with larger submenus (i.e. settings) or
 with multiple submenus open
 >
 > @mehedi890 has volunteered to work on this. Thanks!
 >
 > Props to @hilayt24, @mehedi890 & @markparnell

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32747#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 03:17:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 03:17:11 -0000
Subject: [wp-trac] [WordPress Trac] #54746: Comment Error in wp-login.php
In-Reply-To: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
References: <051.661f8373bb0391b330a2dc9d38d527ba@wordpress.org>
Message-ID: <066.cfeb30c253a6b830073b84dcf6043359@wordpress.org>

#54746: Comment Error in wp-login.php
------------------------------------+-------------------------------------
 Reporter:  alkesh7                 |       Owner:  SergeyBiryukov
     Type:  enhancement             |      Status:  assigned
 Priority:  normal                  |   Milestone:  6.0
Component:  Login and Registration  |     Version:
 Severity:  minor                   |  Resolution:
 Keywords:                          |     Focuses:  docs, coding-standards
------------------------------------+-------------------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch =>
 * owner:  peterwilsoncc => SergeyBiryukov
 * status:  reopened => assigned


Comment:

 Replying to [comment:8 SergeyBiryukov]:
 > I think comments like "Main" have some benefit, as they denote various
 parts of the file, in this case separating function declarations from the
 main part.

 With the additional context they do, on it's own the word main is
 meaningless.

 > Instead of removing them, I think we can convert them to the multi-line
 format per the documentation standards:
 > {{{
 > /*
 >  * Main.
 >  */
 > }}}

 The point is to meet the coding standards by avoiding single line comments
 of that format. Given that the additional context is needed for the
 comment to make sense, I think it best revised as a multi-line comment
 anyway.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54746#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 08:28:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 08:28:15 -0000
Subject: [wp-trac] [WordPress Trac] #55226: Update
 class-wp-site-query.php - Change function parse_orderby()
In-Reply-To: <053.ec450fb72885a823fd1521dec9619704@wordpress.org>
References: <053.ec450fb72885a823fd1521dec9619704@wordpress.org>
Message-ID: <068.03c6c242b176172cee5b6be1fbe5f73c@wordpress.org>

#55226: Update class-wp-site-query.php - Change function parse_orderby()
--------------------------------+---------------------
 Reporter:  lenasterg           |       Owner:  (none)
     Type:  enhancement         |      Status:  new
 Priority:  normal              |   Milestone:  6.0
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  has-patch           |     Focuses:
--------------------------------+---------------------

Comment (by lenasterg):

 Hi,
 I think you are right about that. It's better to do it for all the
 fieldes.

 Replying to [comment:3 peterwilsoncc]:
 > To try and avoid followup tickets, is the same needed for any/all of the
 other boolean fields in the table: mature, spam, archived, public?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55226#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 10:15:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 10:15:24 -0000
Subject: [wp-trac] [WordPress Trac] #13459: Conflict between post and
 page slugs/permalinks when permalink setting is set to /%postname%/
In-Reply-To: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
References: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
Message-ID: <071.b86bfedb071e13667c94af8e352bfdf7@wordpress.org>

#13459: Conflict between post and page slugs/permalinks when permalink setting is
set to /%postname%/
--------------------------+-----------------------------
 Reporter:  jamescollins  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Permalinks    |     Version:  2.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------

Comment (by bobbingwide):

 I've documented my view of the problem at https://herbmiller.me
 /requirements-for-permalink-postname/

 In the post I list several steps to reproduce the problem, what I believe
 to be the requirements to be satisfied and have tabulated some of the
 alternative permalink structures and the results obtained accessing
 duplicated entries.

 I've briefly considered two different approaches to the problem. I'm
 coming to the conclusion that `parse_request()` needs to be changed. The
 logic associated with `use_verbose_page_rules` being the main sticking
 point when duplicates exist.

 In my opinion any broken tests should cover the round trip, confirming
 that the post being requested is the one that's returned to the user.

 If required I'll copy paste my post into this TRAC.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/13459#comment:69>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 10:32:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 10:32:13 -0000
Subject: [wp-trac] [WordPress Trac] #53628: Maintenance Free Updates -
 Zero downtime
In-Reply-To: <060.bfc746c6f8f53f13fee28ae650f2b634@wordpress.org>
References: <060.bfc746c6f8f53f13fee28ae650f2b634@wordpress.org>
Message-ID: <075.ca500228dfaa0f7fcd901224153646e3@wordpress.org>

#53628: Maintenance Free Updates - Zero downtime
------------------------------+------------------------------
 Reporter:  billybigpotatoes  |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Plugins           |     Version:  5.8
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by billybigpotatoes):

 FYI We have now been running this process for several months and it is
 working well for us.  Keen to discuss how to move this forward to more
 people can benefit

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53628#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 10:52:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 10:52:28 -0000
Subject: [wp-trac] [WordPress Trac] #55419: Persistant Object Cache / APCu /
 Performance Lab Plugin
Message-ID: <051.93712b1f9011c82fdfc1162ca1d051c3@wordpress.org>

#55419: Persistant Object Cache / APCu / Performance Lab Plugin
--------------------------+-----------------------------
 Reporter:  pat2021       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  critical      |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 I have activated APCu and tried different PHP versions 7.4 to 8.1 but I
 always get the error in WordPress that I should use a persistant object
 cache with the Performance Lab plugin.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55419>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 11:36:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 11:36:12 -0000
Subject: [wp-trac] [WordPress Trac] #55420: Warning thrown by method
 get_the_modified_author if author was removed
Message-ID: <057.5250e72891a355c33e2e698948be4843@wordpress.org>

#55420: Warning thrown by method get_the_modified_author if author was removed
----------------------------+-----------------------------
 Reporter:  juanlopez4691   |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Users           |    Version:  5.9.2
 Severity:  normal          |   Keywords:
  Focuses:  administration  |
----------------------------+-----------------------------
 If a post has been last modified by a removed author, method
 `get_the_modified_author` throws a warning:

 Warning: Attempt to read property "display_name" on bool in htdocs/wp-
 includes/author-template.php on line 104

 This happens because `get_userdata` returns false if the user that
 modified the post last no longer exists.

 A possible solution:

 Modify file `wp-includes/author-template.php`, line 104, from
 `return apply_filters( 'the_modified_author', $last_user->display_name );`
 to
 `return apply_filters( 'the_modified_author', $last_user ?
 $last_user->display_name : '' );`

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55420>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 11:40:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 11:40:51 -0000
Subject: [wp-trac] [WordPress Trac] #55420: Warning thrown by method
 get_the_modified_author if author was removed
In-Reply-To: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
References: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
Message-ID: <072.530d1693dd48078e53bb7e490f14eb04@wordpress.org>

#55420: Warning thrown by method get_the_modified_author if author was removed
---------------------------+------------------------------
 Reporter:  juanlopez4691  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Users          |     Version:  5.9.2
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  administration
---------------------------+------------------------------
Changes (by juanlopez4691):

 * Attachment "author-template.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55420>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 12:10:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 12:10:28 -0000
Subject: [wp-trac] [WordPress Trac] #53370: Theme thumbnail/screenshot
 does not contain version string
In-Reply-To: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
References: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
Message-ID: <066.f5dc858d652de7b4f57bbe78a2455e50@wordpress.org>

#53370: Theme thumbnail/screenshot does not contain version string
-------------------------+-----------------------
 Reporter:  codente      |       Owner:  audrasjb
     Type:  enhancement  |      Status:  reopened
 Priority:  normal       |   Milestone:  6.0
Component:  Themes       |     Version:  5.7.2
 Severity:  minor        |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch commit => needs-patch
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I spotted at least one missed file. Reopening for follow-up fixes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53370#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 12:16:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 12:16:36 -0000
Subject: [wp-trac] [WordPress Trac] #55421: Different CSS order causes
 inconsistency between editor and actual page
Message-ID: <050.570ab78d2ee09e523109adc1fff8b2fa@wordpress.org>

#55421: Different CSS order causes inconsistency between editor and actual page
--------------------------+-----------------------------
 Reporter:  asafm7        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Editor        |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Fresh WordPress, 2022 theme, no plugins.

 There are some styles loaded as an external file by "load-styles.php" in
 the editor while being inlined in the actual page.

 This creates different cascading between editor and actual page, and hence
 a different design.

 About the screenshot - the margin above the image disappears on the actual
 page because of the issue described. There is no way of recreating it
 without custom CSS.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55421>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 12:16:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 12:16:46 -0000
Subject: [wp-trac] [WordPress Trac] #55421: Different CSS order causes
 inconsistency between editor and actual page
In-Reply-To: <050.570ab78d2ee09e523109adc1fff8b2fa@wordpress.org>
References: <050.570ab78d2ee09e523109adc1fff8b2fa@wordpress.org>
Message-ID: <065.6f12f22acfd74c8072ecce8eda28b2de@wordpress.org>

#55421: Different CSS order causes inconsistency between editor and actual page
--------------------------+------------------------------
 Reporter:  asafm7        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by asafm7):

 * Attachment "Screenshot 2022-03-18 120835.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55421>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 12:19:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 12:19:46 -0000
Subject: [wp-trac] [WordPress Trac] #55416: Version 5.9.2 upgrade -
 Elementor
In-Reply-To: <055.4a1d874d1418a55db56d13844cde2fe6@wordpress.org>
References: <055.4a1d874d1418a55db56d13844cde2fe6@wordpress.org>
Message-ID: <070.41e966ab46e4cb9cf2680f945e34e7a6@wordpress.org>

#55416: Version 5.9.2 upgrade - Elementor
-----------------------------+------------------------------
 Reporter:  juliekoehne      |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  5.9.2
 Severity:  major            |  Resolution:  invalid
 Keywords:                   |     Focuses:
-----------------------------+------------------------------
Changes (by juliekoehne):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 It has been resolved.  The problem was our Siteground Optimizer plugin and
 a caching setting.  Once I cleared the cache it works correctly.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55416#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 12:26:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 12:26:18 -0000
Subject: [wp-trac] [WordPress Trac] #54698: Add 'ruby' tag and its
 friends to kses
In-Reply-To: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
References: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
Message-ID: <066.ff55f6f5b1aa90076fadb68640f53178@wordpress.org>

#54698: Add 'ruby' tag and its friends to kses
-------------------------+---------------------
 Reporter:  upsuper      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Formatting   |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------

Comment (by upsuper):

 Any update here?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54698#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 12:26:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 12:26:29 -0000
Subject: [wp-trac] [WordPress Trac] #54699: dir, lang,
 and xml:lang should be global attributes supported on all tags
In-Reply-To: <051.3929a185f51eb57c38100444430ddf90@wordpress.org>
References: <051.3929a185f51eb57c38100444430ddf90@wordpress.org>
Message-ID: <066.333ad95614634419a95a9b6f802f8161@wordpress.org>

#54699: dir, lang, and xml:lang should be global attributes supported on all tags
-------------------------------------------------+-------------------------
 Reporter:  upsuper                              |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Formatting                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-docs  |     Focuses:
  needs-dev-note                                 |
-------------------------------------------------+-------------------------

Comment (by upsuper):

 Any update here?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54699#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 12:42:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 12:42:53 -0000
Subject: [wp-trac] [WordPress Trac] #53370: Theme thumbnail/screenshot
 does not contain version string
In-Reply-To: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
References: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
Message-ID: <066.b2d9e390bf4d4f72a6785eaeb143ecc3@wordpress.org>

#53370: Theme thumbnail/screenshot does not contain version string
-------------------------+-----------------------
 Reporter:  codente      |       Owner:  audrasjb
     Type:  enhancement  |      Status:  reopened
 Priority:  normal       |   Milestone:  6.0
Component:  Themes       |     Version:  5.7.2
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+-----------------------

Comment (by audrasjb):

 In [changeset:"52948" 52948]:
 {{{
 #!CommitTicketReference repository="" revision="52948"
 Themes: Add version to theme screenshot URL in `WP_Themes_List_Table`.

 Follow-up to [52947].

 See #53370.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53370#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 12:45:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 12:45:54 -0000
Subject: [wp-trac] [WordPress Trac] #54699: dir, lang,
 and xml:lang should be global attributes supported on all tags
In-Reply-To: <051.3929a185f51eb57c38100444430ddf90@wordpress.org>
References: <051.3929a185f51eb57c38100444430ddf90@wordpress.org>
Message-ID: <066.a01b055300843b73d222643e15dbc05a@wordpress.org>

#54699: dir, lang, and xml:lang should be global attributes supported on all tags
-------------------------------------------------+-------------------------
 Reporter:  upsuper                              |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Formatting                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-docs  |     Focuses:
  needs-dev-note                                 |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 Hello @upsuper, thanks for the heads up.
 I think we're good to go.
 I self assigned the ticket but I'm only waiting for another committer
 review before shipping it to milestone 6.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54699#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 13:42:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 13:42:50 -0000
Subject: [wp-trac] [WordPress Trac] #53370: Theme thumbnail/screenshot
 does not contain version string
In-Reply-To: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
References: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
Message-ID: <066.b030bed8dda47a4d203e17bd53e0e5a3@wordpress.org>

#53370: Theme thumbnail/screenshot does not contain version string
-------------------------+-----------------------
 Reporter:  codente      |       Owner:  audrasjb
     Type:  enhancement  |      Status:  reopened
 Priority:  normal       |   Milestone:  6.0
Component:  Themes       |     Version:  5.7.2
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+-----------------------

Comment (by SergeyBiryukov):

 In [changeset:"52949" 52949]:
 {{{
 #!CommitTicketReference repository="" revision="52949"
 Themes: Use `esc_url()` for theme screenshots on the Themes screen.

 This brings consistency with how screenshots are escaped elsewhere.

 Follow-up to [52020], [52947].

 See #53370.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53370#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 13:43:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 13:43:29 -0000
Subject: [wp-trac] [WordPress Trac] #55420: Warning thrown by method
 get_the_modified_author if author was removed
In-Reply-To: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
References: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
Message-ID: <072.431637efa93f11a8519689de1b0552dd@wordpress.org>

#55420: Warning thrown by method get_the_modified_author if author was removed
---------------------------+-----------------------------
 Reporter:  juanlopez4691  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Users          |     Version:  5.9.2
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  administration
---------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55420#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 13:58:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 13:58:14 -0000
Subject: [wp-trac] [WordPress Trac] #55419: Persistant Object Cache /
 APCu / Performance Lab Plugin
In-Reply-To: <051.93712b1f9011c82fdfc1162ca1d051c3@wordpress.org>
References: <051.93712b1f9011c82fdfc1162ca1d051c3@wordpress.org>
Message-ID: <066.dfe29e002692d6c0871d443d7f6fcbfd@wordpress.org>

#55419: Persistant Object Cache / APCu / Performance Lab Plugin
--------------------------+----------------------
 Reporter:  pat2021       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  critical      |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by johnbillion):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Thanks for helping test the Performance Lab plugin @pat2021 !

 Have you installed a corresponding APCu plugin so WordPress can talk to
 APCu? If not then that's likely the issue.

 If that's not the problem, please post a new thread on the Performance Lab
 plugin forum at https://wordpress.org/support/plugin/performance-lab/.

 Cheers!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55419#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 15:06:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 15:06:25 -0000
Subject: [wp-trac] [WordPress Trac] #47018: No error message provided
 upon incomplete input in Tags Administration Screen
In-Reply-To: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
References: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
Message-ID: <068.035eaa6376060426ba863cd0d46e17ca@wordpress.org>

#47018: No error message provided upon incomplete input in Tags Administration
Screen
-------------------------------------+-------------------------------------
 Reporter:  conner_bw                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Future Release
Component:  Taxonomy                 |     Version:  5.1.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots input-   |     Focuses:  ui, accessibility,
  validation                         |  administration
-------------------------------------+-------------------------------------

Comment (by afercia):

 Looking back into this, seems to me there's some some parts of the related
 code are pretty old and maybe some overlap has occurred over time, which
 is perfectly understandable in a so large project with lots of legacy ode.

 In `src/js/_enqueues/admin/tags.js`:
 - When submitting the form, `window.validateForm` is called to check
 whether the 'Name' input field is empty.
 - If it's empty, the code in `tags.js` returns false. thus preventing the
 Ajax call and the form submission.

 Actually, this prevents the 'add tag' Ajax action from doing its job.
 Seems everything we need is already there:
 - The Ajax response properly returns success or error messages.
 - `window.wpAjax` parses the response and appends the messages at the top
 of the page.
 - There are already audible messages for screen readers via
 `wp.a11y.speak`.
 - The form submission is already prevented.

 All the above doesn't run just because of the `return false` in `tags.js`.
 I do realize the current code 'saves' one Ajax request when the field is
 empty but that comes at the cost of missing feedback for users.

 Removing the `return false` does allow the Ajax request to run and return
 the error messages.  Seems to me this would be more inline with the
 purpose of the existing Ajax response.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47018#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 15:08:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 15:08:54 -0000
Subject: [wp-trac] [WordPress Trac] #47018: No error message provided
 upon incomplete input in Tags Administration Screen
In-Reply-To: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
References: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
Message-ID: <068.e6cc8e3eac8c67215a05c1bca7e1ad81@wordpress.org>

#47018: No error message provided upon incomplete input in Tags Administration
Screen
-------------------------------------+-------------------------------------
 Reporter:  conner_bw                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Future Release
Component:  Taxonomy                 |     Version:  5.1.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots input-   |     Focuses:  ui, accessibility,
  validation                         |  administration
-------------------------------------+-------------------------------------
Changes (by afercia):

 * Attachment "47018.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47018>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 15:18:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 15:18:07 -0000
Subject: [wp-trac] [WordPress Trac] #47018: No error message provided
 upon incomplete input in Tags Administration Screen
In-Reply-To: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
References: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
Message-ID: <068.db3d9cff347bfdda6e33e79de6672d20@wordpress.org>

#47018: No error message provided upon incomplete input in Tags Administration
Screen
-------------------------------------+-------------------------------------
 Reporter:  conner_bw                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:  5.1.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots input-   |     Focuses:  ui, accessibility,
  validation has-patch               |  javascript, administration
-------------------------------------+-------------------------------------
Changes (by afercia):

 * keywords:  has-screenshots input-validation => has-screenshots input-
     validation has-patch
 * focuses:  ui, accessibility, administration => ui, accessibility,
     javascript, administration
 * milestone:  Future Release => 6.0


Comment:

 [attachment:"47018.diff"]

 - Allows the add tag Ajax request to run also when the form is submitted
 with the Name field left empty.
 - This way, the response is now able to return error messages.
 - Note that this will trigger an Ajax call every time the form is
 submitted with the 'Name' field empty.

 Additionally:
 - Updates the CSS classes of the notices: 'error' and 'updated' are legacy
 and shouldn't be used any longer.
 - Adds audible messages for 3 more cases so that they're now announced by
 screen readers:
   - No permissions error: 'Sorry, you are not allowed to do that.'
   - Broken error: 'Something went wrong.'
   - When the response returns an error with a custom message.
 - Updates the styling of the error red 'border', ot make it more
 consistent with the 'border' used for the focus style.
 - Adds `wp-a11y` as dependency for the `wp-ajax-response` script.

 See attached screenshot for the error message and the new red border
 style.

 Moving to 6.0 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47018#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 15:18:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 15:18:22 -0000
Subject: [wp-trac] [WordPress Trac] #47018: No error message provided
 upon incomplete input in Tags Administration Screen
In-Reply-To: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
References: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
Message-ID: <068.949e518924ab27e36a88789b29bc28b3@wordpress.org>

#47018: No error message provided upon incomplete input in Tags Administration
Screen
-------------------------------------+-------------------------------------
 Reporter:  conner_bw                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:  5.1.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots input-   |     Focuses:  ui, accessibility,
  validation has-patch               |  javascript, administration
-------------------------------------+-------------------------------------
Changes (by afercia):

 * Attachment "47018.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47018>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 15:30:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 15:30:55 -0000
Subject: [wp-trac] [WordPress Trac] #55418: Persistant Object Cache and
 APCu not working
In-Reply-To: <051.14b678f3892aa9a822fa7937a10f8d96@wordpress.org>
References: <051.14b678f3892aa9a822fa7937a10f8d96@wordpress.org>
Message-ID: <066.44422435159006a53d592f405432768f@wordpress.org>

#55418: Persistant Object Cache and APCu not working
--------------------------+------------------------
 Reporter:  pat2021       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.9.2
 Severity:  critical      |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by SergeyBiryukov):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 Hi there, welcome to WordPress Trac!

 This appears to be a duplicate of #55419, let's continue there.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55418#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:13:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:13:24 -0000
Subject: [wp-trac] [WordPress Trac] #55417: Text Highlighting Broken
In-Reply-To: <050.95d872d4aea23a3a846115c0c388e364@wordpress.org>
References: <050.95d872d4aea23a3a846115c0c388e364@wordpress.org>
Message-ID: <065.4138eda13c28507fa8d4a4068c6d9467@wordpress.org>

#55417: Text Highlighting Broken
-------------------------------------------------+-------------------------
 Reporter:  notgeo                               |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Editor                               |     Version:  5.9.2
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing-info reporter-         |     Focuses:  ui
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by ryokuhi):

 * keywords:  needs-testing-info => needs-testing-info reporter-feedback
 * focuses:  ui, accessibility => ui


Comment:

 Hello @notgeo, and welcome on WordPress Trac!
 Thanks for spending part of your time to report this issue, which we
 reviewed today during the accessibility team's bug-scrub.

 Unfortunately, we aren't able to completely understand the problem you are
 facing. Can you please provide a step-by-step list of instructions that we
 can follow to reproduce the bug?

 From the little we were able to understand, anyway, we think that this
 isn't an accessibility issue, that is, an issue that mainly affects people
 with disabilities.

 As such, I'm removing the accessibility focus, but please add more
 detailled instructions to reproduce and, in case you think this is really
 an accessiblity issue, feel free to add the focus back.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55417#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:16:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:16:48 -0000
Subject: [wp-trac] [WordPress Trac] #15134: WordPress should not try to
 remove themes or plugins recursively if the directory is a symlink
In-Reply-To: <063.b4790b9dde77a313ebcfce1c9b3877f0@wordpress.org>
References: <063.b4790b9dde77a313ebcfce1c9b3877f0@wordpress.org>
Message-ID: <078.2d8d4b1a482ce3bb334c0f43eb290dfc@wordpress.org>

#15134: WordPress should not try to remove themes or plugins recursively if the
directory is a symlink
-------------------------------------+-----------------------
 Reporter:  vladimir_kolesnikov      |       Owner:  pbiron
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Upgrade/Install          |     Version:
 Severity:  major                    |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+-----------------------

Comment (by jqz):

 This has become more of an issue now automatic plugin/theme updates are an
 option, and now that on occasion a plugin author may choose to force an
 update to patch a security vulnerability even if automatic updates are
 disabled - see https://github.com/woocommerce/woocommerce/issues/32111 -
 this can lead to a broken site that could go undetected for days.

 Replying to [comment:1 Denis-de-Bernardy]:
 > Seems to me that this is a use-case where site admins shouldn't be
 allowed to upgrade plugins, and where all installs should be maintained
 from the shell using svn, git, or scripts.

 No, it is possible have some common plugins symlinked, whilst others are
 updated in the usual WordPress way.

 > The risk is quite huge in that setup: only one site gets put on
 maintenance mode, even though the plugin update could be affecting dozens
 of sites.

 I disagree.  `plugins/some-plugin/` can symlink to `~/shared-plugins/some-
 plugin/` which in turn symlinks to `~/shared-plugins/some-plugin-1.0/`.
 Then to upgrade it is only necessary to relink `~/shared-plugins/some-
 plugin/` to `~/shared-plugins/some-plugin-1.1/`.  There is no downtime at
 all and therefore no need for maintenance mode.

 There is a very small risk that any HTTP requests in progress at the time
 of the relinking may end up parsing newer versions of any PHP files it
 hadn't already parsed.  However, that and other problems could happen
 anyway with the normal WordPress update procedure if a separate process
 was in the middle of serving an HTTP request at the time the update was
 triggered.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/15134#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:19:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:19:14 -0000
Subject: [wp-trac] [WordPress Trac] #45387: Valid HTML get mangled on
 the frontend
In-Reply-To: <055.2a35e0590263ff99e4936e1328abc1ed@wordpress.org>
References: <055.2a35e0590263ff99e4936e1328abc1ed@wordpress.org>
Message-ID: <070.fd4a052d9140cf8150c7bf305b109d42@wordpress.org>

#45387: Valid HTML get mangled on the frontend
--------------------------+------------------------------
 Reporter:  youknowriad   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by joshuanan):

 I hope this will get more attention soon. The issue @mcsf mentioned is
 really a pain for JS conditional logic. Consider that the following code
 will throw an error ("Uncaught SyntaxError: '#' not followed by
 identifier") when entered into a Gutenberg HTML block directly or as the
 output of a short code entered in Gutenberg, because & is converted to an
 HTML entity.


 {{{
 <script>

 x = 5;
 y = 10;
 z = 10

 if (x < y) {

   console.log("X is Greater than Y.");
 }
 else if (x !== y && x !== z) {

   console.log("X is Less than Y, But Unique.");
 }
 </script>
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45387#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:21:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:21:51 -0000
Subject: [wp-trac] [WordPress Trac] #53628: Maintenance Free Updates -
 Zero downtime
In-Reply-To: <060.bfc746c6f8f53f13fee28ae650f2b634@wordpress.org>
References: <060.bfc746c6f8f53f13fee28ae650f2b634@wordpress.org>
Message-ID: <075.375a79f5174279b2edf7268561659588@wordpress.org>

#53628: Maintenance Free Updates - Zero downtime
------------------------------+------------------------------
 Reporter:  billybigpotatoes  |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Plugins           |     Version:  5.8
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by SergeyBiryukov):

 Hi there, welcome to WordPress Trac! Thanks for the ticket.

 Just noting that some related work is being done in #51857, feel free to
 join the discussion there if you'd like. The latest activity for that
 ticket is on [https://github.com/WordPress/wordpress-develop/pull/2225 PR
 #2225].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53628#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:32:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:32:37 -0000
Subject: [wp-trac] [WordPress Trac] #47018: No error message provided
 upon incomplete input in Tags Administration Screen
In-Reply-To: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
References: <053.f1bf88ff1edccbddf10be7d2b29a23ca@wordpress.org>
Message-ID: <068.6863bda250f6757de0409dd2e416f372@wordpress.org>

#47018: No error message provided upon incomplete input in Tags Administration
Screen
-------------------------------------+-------------------------------------
 Reporter:  conner_bw                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:  5.1.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots input-   |     Focuses:  ui, accessibility,
  validation has-patch needs-        |  javascript, administration
  testing                            |
-------------------------------------+-------------------------------------
Changes (by ryokuhi):

 * keywords:  has-screenshots input-validation has-patch => has-screenshots
     input-validation has-patch needs-testing


Comment:

 We reviewed this ticket today during the accessibiltiy team's bug-scrub.

 I'm adding the `needs-testing` label, so that, if the patch is valid, it
 can be committed before the next release.

 As ticket #54394, also milestoned for 6.0, adds a "core way" to mark
 required fields, maybe this is a nice use case for the new functions.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47018#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:37:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:37:37 -0000
Subject: [wp-trac] [WordPress Trac] #42942: Provide a
 post_date_column_time hook for media files
In-Reply-To: <054.b8ba66020e3f87a90d888b926a23b5f9@wordpress.org>
References: <054.b8ba66020e3f87a90d888b926a23b5f9@wordpress.org>
Message-ID: <069.a15a8e6ecf29c68ba2a302a714778b33@wordpress.org>

#42942: Provide a post_date_column_time hook for media files
------------------------------------+----------------------------
 Reporter:  ivanlutrov              |       Owner:  davidbaumwald
     Type:  feature request         |      Status:  closed
 Priority:  normal                  |   Milestone:  6.0
Component:  Administration          |     Version:  5.1
 Severity:  normal                  |  Resolution:  fixed
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+----------------------------
Changes (by davidbaumwald):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52950" 52950]:
 {{{
 #!CommitTicketReference repository="" revision="52950"
 Administration: Add a `media_date_column_time` filter to the media list
 table date column.

 Similar to the existing `post_date_column_time` filter in the posts list
 table, this change adds a new hook to filter the "Date" column output in
 the media list view.

 Props ivanlutrov, lopo, audrasjb.
 Fixes #42942.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42942#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:39:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:39:01 -0000
Subject: [wp-trac] [WordPress Trac] #42942: Provide a
 post_date_column_time hook for media files
In-Reply-To: <054.b8ba66020e3f87a90d888b926a23b5f9@wordpress.org>
References: <054.b8ba66020e3f87a90d888b926a23b5f9@wordpress.org>
Message-ID: <069.7687979aba3585e62ce4e1b85c0c0181@wordpress.org>

#42942: Provide a post_date_column_time hook for media files
-------------------------------------------------+-------------------------
 Reporter:  ivanlutrov                           |       Owner:
                                                 |  davidbaumwald
     Type:  feature request                      |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  5.1
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch dev-feedback needs-dev-    |     Focuses:
  note                                           |
-------------------------------------------------+-------------------------
Changes (by davidbaumwald):

 * keywords:  has-patch dev-feedback => has-patch dev-feedback needs-dev-
               note


Comment:

 Marking `needs-dev-note` as this at least deserves a small mention in the
 Misc Dev Note.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42942#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:47:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:47:44 -0000
Subject: [wp-trac] [WordPress Trac] #54621: Unsaved comment warning
 without any changes made when click on Publish, Update or Preview Buttons
In-Reply-To: <055.386610e23ea6bfe627367705a9dc1d4d@wordpress.org>
References: <055.386610e23ea6bfe627367705a9dc1d4d@wordpress.org>
Message-ID: <070.c16286aee0a64d42036e240306a277bf@wordpress.org>

#54621: Unsaved comment warning without any changes made when click on Publish,
Update or Preview Buttons
-------------------------------------+-------------------------------------
 Reporter:  askaryabbas              |       Owner:  (none)
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Comments                 |     Version:  4.6
 Severity:  major                    |  Resolution:
 Keywords:  needs-patch reporter-    |     Focuses:  javascript,
  feedback                           |  administration
-------------------------------------+-------------------------------------
Changes (by davidbaumwald):

 * milestone:  6.0 => Awaiting Review


Comment:

 Moving this out of the current milestone until this is confirmed as a bug.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54621#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:54:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:54:55 -0000
Subject: [wp-trac] [WordPress Trac] #3534: Hide password in
 setup-config.php
In-Reply-To: <051.2cebc3b9bf8bcb4948a7ebdd9a7db537@wordpress.org>
References: <051.2cebc3b9bf8bcb4948a7ebdd9a7db537@wordpress.org>
Message-ID: <066.2295ac57b07fb8532a3d45441f61f3c7@wordpress.org>

#3534: Hide password in setup-config.php
-------------------------------------------------+-------------------------
 Reporter:  xmarcos                              |       Owner:  rob1n
     Type:  enhancement                          |      Status:  reopened
 Priority:  low                                  |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:  2.1
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info                                   |  accessibility
-------------------------------------------------+-------------------------

Comment (by ryokuhi):

 We reviewed this ticekt today during the accessibiltiy team's bug-scrub.

 The team suggests to first test that @costdev's patch works, and then make
 a decision about how to make the interfaces consistent, which is also
 important for accessibility.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/3534#comment:44>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 16:55:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 16:55:58 -0000
Subject: [wp-trac] [WordPress Trac] #54607: Attempt to read property
 "comment_ID" on null
In-Reply-To: <061.6d0b9eb5e2a5735c586d69465feaa898@wordpress.org>
References: <061.6d0b9eb5e2a5735c586d69465feaa898@wordpress.org>
Message-ID: <076.32177c656ad6e966f9c1dbc933b2030e@wordpress.org>

#54607: Attempt to read property "comment_ID" on null
-------------------------------+------------------------
 Reporter:  Grzegorz.Janoszka  |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Comments           |     Version:
 Severity:  minor              |  Resolution:  duplicate
 Keywords:  php8               |     Focuses:
-------------------------------+------------------------
Changes (by davidbaumwald):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  6.0 =>


Comment:

 Duplicate of #54379.

 @grzegorzjanoszka It looks like this should have been resolved by
 [https://core.trac.wordpress.org/changeset/52818 r52818].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54607#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 17:48:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 17:48:38 -0000
Subject: [wp-trac] [WordPress Trac] #54421: Deprecate skip link focus fix
In-Reply-To: <055.6c042611127adb964b8ae0345aeca614@wordpress.org>
References: <055.6c042611127adb964b8ae0345aeca614@wordpress.org>
Message-ID: <070.9794027b25902412b364121f74c5b9fb@wordpress.org>

#54421: Deprecate skip link focus fix
-------------------------+-------------------------------------------------
 Reporter:  westonruter  |       Owner:  westonruter
     Type:  enhancement  |      Status:  closed
 Priority:  low          |   Milestone:
Component:  Bundled      |     Version:  3.6
  Theme                  |
 Severity:  minor        |  Resolution:  wontfix
 Keywords:  has-patch    |     Focuses:  accessibility, javascript,
                         |  performance
-------------------------+-------------------------------------------------
Changes (by ryokuhi):

 * status:  accepted => closed
 * resolution:   => wontfix
 * milestone:  6.0 =>


Comment:

 We reviewed again this ticket today during the accessibility team's bug-
 scrub.

 While we understand that there might be some performance improvements in
 dropping this hack, we agreed that the improvement is probably going to be
 marginal.

 On the other side, that would require to make an exception to the policy
 about not making changes because of dropping support.

 As such, we agreed to close this ticket as `wontfix`: in case, this ticket
 can always be reopened and re-reviewed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54421#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 17:48:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 17:48:50 -0000
Subject: [wp-trac] [WordPress Trac] #55288: Site Editor on 5.9.1 fails
 to find homepage template for FSE themes, on WP subdirectory installation
In-Reply-To: <055.066d0ca728e3fb5959c659d12bba3c2b@wordpress.org>
References: <055.066d0ca728e3fb5959c659d12bba3c2b@wordpress.org>
Message-ID: <070.568de49e50d3cdaf9362709084524e80@wordpress.org>

#55288: Site Editor on 5.9.1 fails to find homepage template for FSE themes, on WP
subdirectory installation
--------------------------+---------------------------------------
 Reporter:  andronocean   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.2
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:  administration, template
--------------------------+---------------------------------------
Changes (by Enchiridion):

 * version:  5.9.1 => 5.9.2


Comment:

 This bug still exists is WP 5.9.2 and according to posts on the original
 support thread, occurs even with the stock Twenty-Twenty-Two theme.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55288#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:05:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:05:44 -0000
Subject: [wp-trac] [WordPress Trac] #53218: Make apply_filters() variadic
In-Reply-To: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
References: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
Message-ID: <070.c680aefd0c7703e0cee1ccb92b0f7c77@wordpress.org>

#53218: Make apply_filters() variadic
------------------------------------+--------------------------
 Reporter:  johnbillion             |       Owner:  johnbillion
     Type:  enhancement             |      Status:  assigned
 Priority:  normal                  |   Milestone:  6.0
Component:  Plugins                 |     Version:  5.3
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch early commit  |     Focuses:
------------------------------------+--------------------------

Comment (by johnbillion):

 Replying to [comment:14 peterwilsoncc]:
 > The PR includes `.github/workflows/phpbench-tests.yml`, are you
 intending to include that as part of the commit or is it simply for
 generating the reports during development?

 Just for development 👍

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53218#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:13:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:13:01 -0000
Subject: [wp-trac] [WordPress Trac] #54548: The Close on Escape
 "feature" on the admin comments page is annoying
In-Reply-To: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
References: <051.7f976d4b19f9f1b8dacdd8f98070a8a5@wordpress.org>
Message-ID: <066.1d006d386c6d89e9f46cc272d6886006@wordpress.org>

#54548: The Close on Escape "feature" on the admin comments page is annoying
-------------------------+-------------------------------------------------
 Reporter:  BettyJJ      |       Owner:  alexstine
     Type:  defect       |      Status:  closed
  (bug)                  |
 Priority:  normal       |   Milestone:  6.0
Component:  Comments     |     Version:
 Severity:  normal       |  Resolution:  fixed
 Keywords:  has-patch    |     Focuses:  ui, accessibility, javascript,
                         |  administration
-------------------------+-------------------------------------------------
Changes (by davidbaumwald):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52951" 52951]:
 {{{
 #!CommitTicketReference repository="" revision="52951"
 Comments: Disable "close on escape" for inline replies when using an IME.

 When using an Input Method Editor(IME), pressing escape to perform actions
 in the IME is common.  However, if this was done while replying to a
 comment, the "close on escape" feature was also triggered which cleared
 the current textarea and closed it.

 This change checks if an IME is in use by binding the `compositionstart`
 event to the reply text box and setting a flag if it's triggered.  The
 "close on escape" feature will now only be triggered if this new flag is
 not set after typing a reply.

 Props BettyJJ, sabernhardt, alexstine, konradyoast, audrasjb, rafiahmedd,
 afercia.
 Fixes #54548.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54548#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:21:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:21:05 -0000
Subject: [wp-trac] [WordPress Trac] #54699: dir, lang,
 and xml:lang should be global attributes supported on all tags
In-Reply-To: <051.3929a185f51eb57c38100444430ddf90@wordpress.org>
References: <051.3929a185f51eb57c38100444430ddf90@wordpress.org>
Message-ID: <066.8eca1bffc512aa851293903f10fb5aaa@wordpress.org>

#54699: dir, lang, and xml:lang should be global attributes supported on all tags
-------------------------------------------------+-------------------------
 Reporter:  upsuper                              |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Formatting                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-docs  |     Focuses:
  needs-dev-note commit                          |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * keywords:  has-patch has-unit-tests needs-docs needs-dev-note => has-
     patch has-unit-tests needs-docs needs-dev-note commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54699#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:21:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:21:55 -0000
Subject: [wp-trac] [WordPress Trac] #53218: Make apply_filters() variadic
In-Reply-To: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
References: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
Message-ID: <070.0d307ec89676d1c3c4d6cce8f43658c6@wordpress.org>

#53218: Make apply_filters() variadic
------------------------------------+--------------------------
 Reporter:  johnbillion             |       Owner:  johnbillion
     Type:  enhancement             |      Status:  closed
 Priority:  normal                  |   Milestone:  6.0
Component:  Plugins                 |     Version:  5.3
 Severity:  normal                  |  Resolution:  fixed
 Keywords:  has-patch early commit  |     Focuses:
------------------------------------+--------------------------
Changes (by johnbillion):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52952" 52952]:
 {{{
 #!CommitTicketReference repository="" revision="52952"
 Plugins: Convert `apply_filters()` into a proper variadic function.

 This makes its signature more correct by implementing the spread operator,
 and adjusts the internal logic correspondingly without affecting
 performance.

 Props jrf, SergeyBiryukov, davidbaumwald, mauriac, johnbillion

 Fixes #53218
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53218#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:24:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:24:45 -0000
Subject: [wp-trac] [WordPress Trac] #54698: Add 'ruby' tag and its
 friends to kses
In-Reply-To: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
References: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
Message-ID: <066.6abd88065e0e144cee70ca75f23e09f1@wordpress.org>

#54698: Add 'ruby' tag and its friends to kses
-------------------------+---------------------
 Reporter:  upsuper      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Formatting   |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "54698.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54698>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:25:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:25:01 -0000
Subject: [wp-trac] [WordPress Trac] #54698: Add 'ruby' tag and its
 friends to kses
In-Reply-To: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
References: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
Message-ID: <066.7a52e4fe6e685b4250ff61ef0bf770e8@wordpress.org>

#54698: Add 'ruby' tag and its friends to kses
-------------------------+-----------------------------
 Reporter:  upsuper      |       Owner:  SergeyBiryukov
     Type:  enhancement  |      Status:  reviewing
 Priority:  normal       |   Milestone:  6.0
Component:  Formatting   |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => reviewing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54698#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:31:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:31:34 -0000
Subject: [wp-trac] [WordPress Trac] #54698: Add 'ruby' tag and its
 friends to kses
In-Reply-To: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
References: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
Message-ID: <066.45167fb80246394fbab718ed2c43a80f@wordpress.org>

#54698: Add 'ruby' tag and its friends to kses
------------------------------+-----------------------------
 Reporter:  upsuper           |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  6.0
Component:  Formatting        |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * keywords:  has-patch => has-patch commit


Comment:

 Replying to [comment:4 upsuper]:
 > Indeed that `<ruby>` is the ancestor for all the other elements, but I'm
 confused by your patch. It seems to me that the second level of arrays are
 for attributes of the tag, not possible child tags, and `<table>` which
 has a similar structure as `<ruby>` doesn't contain any such child element
 either.

 You're right, the first PR here appears to be correct as is.

 [attachment:"54698.diff"] adds a unit test. This can be committed after
 #54699, as the test relies on the changes from that ticket.

 > The set of elements to enable such functionality consists of `<ruby>`,
 `<rt>`, and `<rp>` in the [https://html.spec.whatwg.org/multipage/text-
 level-semantics.html#the-ruby-element HTML Standard], while some browsers
 (like Firefox) also supports additional ones `<rb>` and `<rtc>` for more
 advanced formatting, which are not yet included in the official HTML spec,
 but can be found in a [https://www.w3.org/TR/html-ruby-extensions/ W3C
 extension].

 I'm not 100% sure we should add elements that are not in the official HTML
 spec, but don't see any harm in adding the `<rb>` and `<rtc>` tags either.
 If anyone has strong feelings either way, please comment :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54698#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:41:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:41:44 -0000
Subject: [wp-trac] [WordPress Trac] #53094: Twenty Twenty-One: Dark mode
 issue
In-Reply-To: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
References: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
Message-ID: <064.126dbdad4fdddd83b7e483f460c637c7@wordpress.org>

#53094: Twenty Twenty-One: Dark mode issue
---------------------------------------+---------------------
 Reporter:  kpdaa                      |       Owner:  (none)
     Type:  defect (bug)               |      Status:  new
 Priority:  normal                     |   Milestone:  6.0
Component:  Bundled Theme              |     Version:  5.7.1
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:  css
---------------------------------------+---------------------
Changes (by davidbaumwald):

 * Attachment "core-trac-53094-pre-patch.png" added.

 Pre-patch

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53094>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:43:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:43:43 -0000
Subject: [wp-trac] [WordPress Trac] #53094: Twenty Twenty-One: Dark mode
 issue
In-Reply-To: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
References: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
Message-ID: <064.a80f7e850df61c25306f811d0d993a6d@wordpress.org>

#53094: Twenty Twenty-One: Dark mode issue
---------------------------------------+---------------------
 Reporter:  kpdaa                      |       Owner:  (none)
     Type:  defect (bug)               |      Status:  new
 Priority:  normal                     |   Milestone:  6.0
Component:  Bundled Theme              |     Version:  5.7.1
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:  css
---------------------------------------+---------------------
Changes (by davidbaumwald):

 * Attachment "core-trac-53094-post-patch.png" added.

 Post-patch

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53094>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 18:48:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 18:48:26 -0000
Subject: [wp-trac] [WordPress Trac] #53094: Twenty Twenty-One: Dark mode
 issue
In-Reply-To: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
References: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
Message-ID: <064.b372e8851d7e5951645ca52f7fdedf8a@wordpress.org>

#53094: Twenty Twenty-One: Dark mode issue
---------------------------------------+---------------------
 Reporter:  kpdaa                      |       Owner:  (none)
     Type:  defect (bug)               |      Status:  new
 Priority:  normal                     |   Milestone:  6.0
Component:  Bundled Theme              |     Version:  5.7.1
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:  css
---------------------------------------+---------------------

Comment (by davidbaumwald):

 I followed reproduction steps in
 [https://core.trac.wordpress.org/ticket/53094#comment:2 comment 2]
 precisely except for _not_ using an image.
 [https://core.trac.wordpress.org/attachment/ticket/53094/core-trac-53094
 -pre-patch.png The first screenshot] shows what happens before applying
 the patch, and [https://core.trac.wordpress.org/attachment/ticket/53094
 /core-trac-53094-post-patch.png the second screenshot] shows the change
 after applying the latest patch.

 @sabernhardt Is this what you were expecting?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53094#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 19:38:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 19:38:36 -0000
Subject: [wp-trac] [WordPress Trac] #53094: Twenty Twenty-One: Dark mode
 issue
In-Reply-To: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
References: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
Message-ID: <064.d95041643b3a1c4d2c431bac8e9c7fe5@wordpress.org>

#53094: Twenty Twenty-One: Dark mode issue
-----------------------------+---------------------
 Reporter:  kpdaa            |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Bundled Theme    |     Version:  5.7.1
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  css
-----------------------------+---------------------
Changes (by sabernhardt):

 * keywords:  has-screenshots has-patch => has-screenshots


Comment:

 That looks the way I expected it ''without'' the background image.
 However, I apparently failed to test the patch ''with'' an image to
 discover that it can affect those blocks, too. Cover blocks are meant to
 have an image or video (otherwise a Group block could be more
 appropriate), so it would need stricter matching to avoid changing the
 block when used as intended.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53094#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 19:44:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 19:44:11 -0000
Subject: [wp-trac] [WordPress Trac] #54344: Required inputs on multisite
 site registration page lack required attribute
In-Reply-To: <057.bd0effb842bcae7ad8f0aff04da118fd@wordpress.org>
References: <057.bd0effb842bcae7ad8f0aff04da118fd@wordpress.org>
Message-ID: <072.396504eb602949e59fdfc4818e99029a@wordpress.org>

#54344: Required inputs on multisite site registration page lack required attribute
---------------------------------------+-----------------------------------
 Reporter:  SteelWagstaff              |       Owner:  (none)
     Type:  defect (bug)               |      Status:  new
 Priority:  normal                     |   Milestone:  6.0
Component:  Login and Registration     |     Version:  5.8.1
 Severity:  normal                     |  Resolution:
 Keywords:  required-fields has-patch  |     Focuses:  accessibility, ui-
                                       |  copy
---------------------------------------+-----------------------------------

Comment (by davidbaumwald):

 Looks like the `required` attributes are included in the patch, but I
 agree that there should be some helpful text to prevent users from
 entering the entire URL for subdomains.  The `span.suffix_address` makes
 this clear to non-assistive users, but it should be made clear to all that
 only the subdirectory or subdomain should be entered.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54344#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 20:10:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 20:10:58 -0000
Subject: [wp-trac] [WordPress Trac] #48030: HTML5 input types are not
 being reset when submitting the addtag form
In-Reply-To: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
References: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
Message-ID: <072.9d269d733f5079c0b7de70e430dda241@wordpress.org>

#48030: HTML5 input types are not being reset when submitting the addtag form
-----------------------------+---------------------------------------------
 Reporter:  stevegrunwell    |       Owner:  davidbaumwald
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  6.0
Component:  Taxonomy         |     Version:
 Severity:  minor            |  Resolution:  fixed
 Keywords:  has-patch        |     Focuses:  ui, javascript, administration
  needs-testing              |
-----------------------------+---------------------------------------------
Changes (by davidbaumwald):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52953" 52953]:
 {{{
 #!CommitTicketReference repository="" revision="52953"
 Taxonomy: Consider HTML5 input types when resetting form values after
 adding a new tag.

 When adding a new tag, the form is reset by clearing values for
 `input[type=text]` and `textarea`s.  However, the reset doesn't account
 for any HTML5 input types, like `number` or `url`, that may be added by
 plugins or themes.

 This change updates the form resetting jQuery to clear any values from
 `input` types that are not hidden and neither a `checkbox` nor `radio`
 type.

 Props stevegrunwell.
 Fixes #48030.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48030#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 20:25:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 20:25:01 -0000
Subject: [wp-trac] [WordPress Trac] #46600: Twenty Nineteen: Flex order
 on comment form causes contents of comment_form_after to appear above the
 form
In-Reply-To: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
References: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
Message-ID: <074.c0b70fad67e6d6c0e5568777929a4568@wordpress.org>

#46600: Twenty Nineteen: Flex order on comment form causes contents of
comment_form_after to appear above the form
-----------------------------+---------------------------------
 Reporter:  garrett-eclipse  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Bundled Theme    |     Version:  5.0
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  accessibility, css
-----------------------------+---------------------------------
Changes (by sabernhardt):

 * Attachment "46600-pr2431-override-flex.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46600>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 20:42:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 20:42:57 -0000
Subject: [wp-trac] [WordPress Trac] #54987: Check if 'user_nicename' is
 not too long after the 'pre_user_nicename' filter
In-Reply-To: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
References: <058.4d8567dab45144c9e4e0cdf1ce5eca91@wordpress.org>
Message-ID: <073.72c2001469e665f09b220f9843922800@wordpress.org>

#54987: Check if 'user_nicename' is not too long after the 'pre_user_nicename'
filter
--------------------------------------+----------------------------
 Reporter:  SergeyBiryukov            |       Owner:  davidbaumwald
     Type:  defect (bug)              |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Users                     |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+----------------------------
Changes (by davidbaumwald):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52954" 52954]:
 {{{
 #!CommitTicketReference repository="" revision="52954"
 Users: Check maximum length of `user_nicename` after filters are applied.

 Similar to other checks on `user_login` and `user_url`, this change moves
 the maximum length check on `user_nicename` after the `pre_user_nicename`
 filter has been applied, to account for any changes to the value prior to
 saving.

 Props SergeyBiryukov, ravipatel, muhammadfaizanhaidar, mukesh27,
 csesumonpro, azouamauriac.
 Fixes #54987.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54987#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 20:46:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 20:46:31 -0000
Subject: [wp-trac] [WordPress Trac] #40875: Add a petabyte constant
In-Reply-To: <056.d28c7a3a7d68d425d37fb637695b2b65@wordpress.org>
References: <056.d28c7a3a7d68d425d37fb637695b2b65@wordpress.org>
Message-ID: <071.f9e44325e164bb92ecc4381c21239d32@wordpress.org>

#40875: Add a petabyte constant
--------------------------------------+--------------------------
 Reporter:  henry.wright              |       Owner:  johnbillion
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Formatting                |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+--------------------------
Changes (by johnbillion):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52955" 52955]:
 {{{
 #!CommitTicketReference repository="" revision="52955"
 Formatting: Add support for formatting sizes as PB, EB, ZB, and YB.

 Props henry.wright, Presskopp

 Fixes #40875
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40875#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 21:17:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 21:17:05 -0000
Subject: [wp-trac] [WordPress Trac] #54564: Avoid translating several
 times wp_locale strings
In-Reply-To: <050.1abc24d2c05f548c565fa4e6ec82e160@wordpress.org>
References: <050.1abc24d2c05f548c565fa4e6ec82e160@wordpress.org>
Message-ID: <065.acb71b4968d979ebf4e12b4bd39eece5@wordpress.org>

#54564: Avoid translating several times wp_locale strings
-------------------------+--------------------------
 Reporter:  Chouby       |       Owner:  johnbillion
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  6.0
Component:  I18N         |     Version:  1.5
 Severity:  normal       |  Resolution:  fixed
 Keywords:  has-patch    |     Focuses:  performance
-------------------------+--------------------------
Changes (by johnbillion):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52956" 52956]:
 {{{
 #!CommitTicketReference repository="" revision="52956"
 I18N: Avoid translating `wp_locale` strings several times.

 This avoids 26 unnecessary duplicate translations.

 Props Chouby

 Fixes #54564
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54564#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 22:16:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 22:16:55 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs file
Message-ID: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
-------------------------+-----------------------------
 Reporter:  helen        |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:
 Severity:  minor        |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 While we still use SVN and Trac as our sources of truth in core
 development, plenty of contributors use GitHub for their contribution
 workflows. GitHub is currently rolling out support for a Git-standard
 `.git-blame-ignore-revs` file in visual blame and
 [https://github.com/github/feedback/discussions/5033#discussioncomment-2318478
 it has been turned on for the WordPress org per the Gutenberg team's
 request]. It would be nice to have a file with things like the classic
 "pinking shears" commits and others that are purely formatting changes.
 Examples would be [34534] and [42343].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 22:39:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 22:39:29 -0000
Subject: [wp-trac] [WordPress Trac] #54028: Fix improper use of the
 hooks API
In-Reply-To: <050.a5b774ca0bae1254e082498489808619@wordpress.org>
References: <050.a5b774ca0bae1254e082498489808619@wordpress.org>
Message-ID: <065.15375382deeb526f2ce7f78411964920@wordpress.org>

#54028: Fix improper use of the hooks API
--------------------------+---------------------
 Reporter:  azaozz        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  General       |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  docs
--------------------------+---------------------
Changes (by johnregan3):

 * Attachment "54028.diff" added.

 Diff of what is included in github PR 2401

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54028>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 22:44:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 22:44:38 -0000
Subject: [wp-trac] [WordPress Trac] #53218: Make apply_filters() variadic
In-Reply-To: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
References: <055.a6bc37eac8878e850ce543a48e7ba79c@wordpress.org>
Message-ID: <070.5b90294b1f911671ef67606446cc6b45@wordpress.org>

#53218: Make apply_filters() variadic
------------------------------------+--------------------------
 Reporter:  johnbillion             |       Owner:  johnbillion
     Type:  enhancement             |      Status:  closed
 Priority:  normal                  |   Milestone:  6.0
Component:  Plugins                 |     Version:  5.3
 Severity:  normal                  |  Resolution:  fixed
 Keywords:  has-patch early commit  |     Focuses:
------------------------------------+--------------------------

Comment (by azouamauriac):

 Replying to [comment:16 johnbillion]:
 > Props jrf, SergeyBiryukov, davidbaumwald, mauriac, johnbillion
 Not sure we can fix this, but just let you know, my username is
 [https://profiles.wordpress.org/azouamauriac/ @azouamauriac] not mauriac.
 thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53218#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 22:47:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 22:47:03 -0000
Subject: [wp-trac] [WordPress Trac] #55423: Gallery Block Issue
Message-ID: <053.35441a37a6642a61596ba7361ace4617@wordpress.org>

#55423: Gallery Block Issue
--------------------------+-----------------------------
 Reporter:  papazetis     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Gallery       |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 After updating to v5.9.2, the gallery block returns an error on the rest
 API and doesn't load image sizes. This affects only existing libraries,
 not ones you create after the update.

 https://prnt.sc/RKLUuLJAivIy

 Try to select any image within the library and you'll get a rest API error
 on the console

 https://prnt.sc/UOEddnBnX9br
 https://prnt.sc/LQnsBIZIQ6Me

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55423>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 18 22:59:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 18 Mar 2022 22:59:27 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs
 file
In-Reply-To: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
References: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
Message-ID: <064.8e107c6bb404ea954d15e8bedcbb6f74@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
-------------------------+------------------------------
 Reporter:  helen        |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------------------

Comment (by helen):

 My initial PR is not a complete list of commits, though it does include
 all the commits I found for "pinking shears" with the exception of one
 that I noticed contained other changes. I would really love some help
 double checking these commits to make sure we're not including any that
 are anything besides whitespace/style fixes; it's better to be
 conservative to start. Would also like feedback / suggestions on the
 format of the file, particularly around the comments and how we label
 things to be able to maintain this file now and into the future.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 19 03:31:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 19 Mar 2022 03:31:58 -0000
Subject: [wp-trac] [WordPress Trac] #55417: Text Highlighting Broken
In-Reply-To: <050.95d872d4aea23a3a846115c0c388e364@wordpress.org>
References: <050.95d872d4aea23a3a846115c0c388e364@wordpress.org>
Message-ID: <065.636d99349250b9157aa14b3cdb61dea1@wordpress.org>

#55417: Text Highlighting Broken
-------------------------------------------------+-------------------------
 Reporter:  notgeo                               |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Editor                               |     Version:  5.9.2
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing-info reporter-         |     Focuses:  ui
  feedback                                       |
-------------------------------------------------+-------------------------

Comment (by vijayhardaha):

 I think Its Style(Beta) features a color picker Issue. maybe it's already
 reported before and I have seen it somewhere.

 I am writing the steps to reproduce the issue so that someone can identify
 if it's a duplicate.

 1. Activate Twenty Twenty Two theme
 2. Go to Customize Page
 3. Toggle styles panel from the top bar.
 4. Choose colors component
 5. Create a new custom color.
 6. Where the color picker is open, toggle show details input from the icon
 button. (Make sure HEX is selected in the dropdown)
 7. Copy HEX `#f5f5f5`

 You'll see `#f5f5f5` is changed to `#f5f5f` that is not what we expect
 there.

 for RGB and HSL I think single Input is missing so you can't just paste
 colors that you already have saved or you're copying from somewhere else.
 currently, you'll have to add each individual value in 3 different inputs.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55417#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 19 06:46:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 19 Mar 2022 06:46:45 -0000
Subject: [wp-trac] [WordPress Trac] #55424: plugin issuef
Message-ID: <050.acc565679be6632054ea08b9817e9688@wordpress.org>

#55424: plugin issuef
--------------------------+-----------------------------
 Reporter:  sherax        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Gallery       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:  template      |
--------------------------+-----------------------------
 I installed tutor lms and it was on auto update. after updation. my course
 profile is not showing on the home page. is there anyway to solve it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55424>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 19 13:50:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 19 Mar 2022 13:50:47 -0000
Subject: [wp-trac] [WordPress Trac] #55023: get_header() notice: Theme
 without header.php is deprecated
In-Reply-To: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
References: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
Message-ID: <064.f2c47b2a58f6f64ed91b050eab48d378@wordpress.org>

#55023: get_header() notice: Theme without header.php is deprecated
--------------------------+------------------------
 Reporter:  kpdaa         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.3
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  multisite
--------------------------+------------------------

Comment (by ipapproval):

 Hope this isn't too 'off topic'..

 We use {{{add_action('get_header', 'function');}}}   in our ip-
 approval.php file, to trigger the plugin to run **before** a page or post
 is loaded. Because {{{get_header();}}} is not called our plugin fails to
 execute.

 Being that the header is currently required, our plugin should work fine
 will any Theme. This change will break our plugin's functionality.

 Technically we can use  {{{add_action('get_head', 'function');}}}
 however loading the plugin **before** the page/post starts to load would
 be preferred.

 That said, if we do not use one of the two above **add_action**'s, to
 trigger our plugin on a page/post, and just try to use   {{{is_page()}}}
 is_page does not work.   {{{is_page()}}} will be false (or at least not
 true) even though it is a page.

 For reference, at the bottom of our ip-approval.php file, we have the
 following code (non-explanatory code omitted);


 {{{
 /*  Add IP Approval IP Checker to page/post
 --------------------------------------------------------------------*/
 add_action('wp_header', 'ip_checker_action');
 function ip_checker_action(){
     if (is_page()){
         // if it is a page, do page stuff
     }
     else {
         // else it is a post, do post stuff
     }
 }

 /*  Add IP Approval IP Checker to login
 --------------------------------------------------------------------*/
 add_filter('login_init', 'ip_login_action');
 function ip_login_action() {
     // triggered only on the login page
 }
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55023#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 19 14:51:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 19 Mar 2022 14:51:48 -0000
Subject: [wp-trac] [WordPress Trac] #54855: Ui issue on edit menu page
In-Reply-To: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
References: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
Message-ID: <069.81be659ef595de64936d6ba71e40a360@wordpress.org>

#54855: Ui issue on edit menu page
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  audrasjb
     Type:  enhancement              |      Status:  reviewing
 Priority:  normal                   |   Milestone:  6.0
Component:  Menus                    |     Version:  5.8.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots good-    |     Focuses:  ui, css,
  first-bug has-patch needs-refresh  |  administration
-------------------------------------+-------------------------------------

Comment (by pbiron):

 @priyank9033 I see 3 WPCS problems with the patch, all easy to fix:

 1. remove the space before the semi-colon in `margin: calc( 1em + 9px ) 0
 ;`
 2. remove the blank line before `#nav-menu-footer {`
 3. add a space after the colon in `padding:5px 10px;`

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54855#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 19 17:51:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 19 Mar 2022 17:51:47 -0000
Subject: [wp-trac] [WordPress Trac] #55425: Customize: Fetch presence of
 published pages more optimally (refactor)
Message-ID: <050.79f4190ca6567d9d247a2239b48b872b@wordpress.org>

#55425: Customize: Fetch presence of published pages more optimally (refactor)
-------------------------+-----------------------------
 Reporter:  nagpai       |      Owner:  nagpai
     Type:  enhancement  |     Status:  assigned
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Customize    |    Version:  5.9.2
 Severity:  normal       |   Keywords:  needs-patch
  Focuses:               |
-------------------------+-----------------------------
 The function [https://core.trac.wordpress.org/browser/branches/5.9/src/wp-
 includes/class-wp-customize-manager.php#L5743 has_published_pages] on line
 [https://core.trac.wordpress.org/browser/branches/5.9/src/wp-includes
 /class-wp-customize-manager.php#L5753 5753] seems to fetch all the data of
 pages, whereas what is needed is only whether published pages exist or
 not.

 While this may not matter much in sites that have fewer pages, on website
 that has too many pages, it may create an out of memory error. I will test
 and submit a patch to fetch only the count of published pages that will
 help improve efficiency.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55425>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 19 19:33:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 19 Mar 2022 19:33:56 -0000
Subject: [wp-trac] =?utf-8?q?=5BWordPress_Trac=5D_=2355426=3A_Two_Categori?=
 =?utf-8?q?es_in_one_URL=3B_Shows_Posts_that_are_in_BOTH_Categories_doesn?=
 =?utf-8?b?4oCZdCB3b3Jr?=
Message-ID: <052.b660308ba71f82752846ccca94c32639@wordpress.org>

#55426: Two Categories in one URL; Shows Posts that are in BOTH Categories doesn’t
work
--------------------------+-----------------------------
 Reporter:  gooloode      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hey,

 so usually i was able to add two categories in the URL and it would only
 show Posts, that are listed in BOTH categories. The Link was always
 domain.com/category/cat1+cat2 and worked for years. When using that link
 it would only show the posts that are marked in BOTH categories.

 But i just tried to look for a post this way and that simply doesn’t work
 anymore. It only uses the first Category and ignores the Seconds. Has
 there been a change in the WP Core that i’m not aware of and is there a
 way to get back to that?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55426>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 19 20:30:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 19 Mar 2022 20:30:25 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.76e9b28d68f87d66d6c294f3128c5253@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52957" 52957]:
 {{{
 #!CommitTicketReference repository="" revision="52957"
 Coding Standards: Use `esc_url()` instead of `esc_attr()` for some URLs.

 Follow-up to [2063], [2182], [4656], [6952], [9098], [11109], [11204],
 [17887], [22505],

 Props kebbet.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 19 20:32:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 19 Mar 2022 20:32:52 -0000
Subject: [wp-trac] [WordPress Trac] #55424: plugin issuef
In-Reply-To: <050.acc565679be6632054ea08b9817e9688@wordpress.org>
References: <050.acc565679be6632054ea08b9817e9688@wordpress.org>
Message-ID: <065.ac4fdd1f76f1b4e0395efe38ea510a3f@wordpress.org>

#55424: plugin issuef
--------------------------+-----------------------
 Reporter:  sherax        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  template
--------------------------+-----------------------
Changes (by sabernhardt):

 * status:  new => closed
 * resolution:   => invalid
 * component:  Gallery => Plugins
 * milestone:  Awaiting Review =>


Comment:

 Hi and welcome to Trac!

 Sorry to hear you are having trouble with your site. Unfortunately, Trac
 is not the best place for site support. Please use the
 [https://docs.themeum.com/tutor-lms/ Tutor LMS plugin support] or the
 [https://wordpress.org/support/forums/ WordPress support forums].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55424#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 19 23:20:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 19 Mar 2022 23:20:11 -0000
Subject: [wp-trac] [WordPress Trac] #54477: wp-cli vague: "Warning:
 Could not create directory."
In-Reply-To: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
References: <052.a28934f7fb8bd1877b06f8203559a20c@wordpress.org>
Message-ID: <067.7f3183d6361a1c932bd719c96a498f7e@wordpress.org>

#54477: wp-cli vague: "Warning: Could not create directory."
----------------------------------------+---------------------
 Reporter:  gunterer                    |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Upgrade/Install             |     Version:  5.8
 Severity:  minor                       |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:
----------------------------------------+---------------------
Changes (by n8finch):

 * type:  enhancement => defect (bug)


Comment:

 @SergeyBiryukov I was testing this and can't replicate it.

 Here's what I did:
 - Changed the permissions on the `wp-plugins` directory to 444.
 - ran `wp plugin install gutenberg --activate` (and I tested several other
 plugins)
 - Got the following:


 {{{
 Installing the plugin...
 Warning: Could not create directory upgrader. "/Users/natefinch/Local
 Sites/wpcli-bug-fix/app/wordpress-develop/src/wp-
 content/plugins/gutenberg/"
 Plugin installation failed.
 Warning: The 'gutenberg' plugin could not be found.
 Error: No plugins installed.
 }}}


 Looking at the code for this particular notification, the directory is
 already in error notification with `$remote_destination`:
 https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-
 admin/includes/class-wp-upgrader.php#L591

 This is also the case in the other files (wp-admin/includes/file.php and
 wp-admin/includes/update-core.php).

 These were added 8 years ago by Andrew Nacin:
 https://core.trac.wordpress.org/changeset/25780

 Since the error strings already exits with the $filenames, I think this
 ticket can be closed, or perhaps someone else can check it out.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54477#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 06:00:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 06:00:39 -0000
Subject: [wp-trac] [WordPress Trac] #53234: Application password access
 text is misleading for Super Admins
In-Reply-To: <055.0e9d1b8f7ea2e3fdeb10ed7ba49893b2@wordpress.org>
References: <055.0e9d1b8f7ea2e3fdeb10ed7ba49893b2@wordpress.org>
Message-ID: <070.0530769671c3d464e943786b7546bcc8@wordpress.org>

#53234: Application password access text is misleading for Super Admins
----------------------------------------+------------------------
 Reporter:  johnbillion                 |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Application Passwords       |     Version:  5.6
 Severity:  normal                      |  Resolution:
 Keywords:  good-first-bug needs-patch  |     Focuses:  multisite
----------------------------------------+------------------------
Changes (by rsiddharth):

 * Attachment "53234.2022032000.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53234>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 06:03:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 06:03:39 -0000
Subject: [wp-trac] [WordPress Trac] #53234: Application password access
 text is misleading for Super Admins
In-Reply-To: <055.0e9d1b8f7ea2e3fdeb10ed7ba49893b2@wordpress.org>
References: <055.0e9d1b8f7ea2e3fdeb10ed7ba49893b2@wordpress.org>
Message-ID: <070.52981f94879fecf325286fbca69b352a@wordpress.org>

#53234: Application password access text is misleading for Super Admins
--------------------------------------+------------------------
 Reporter:  johnbillion               |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Application Passwords     |     Version:  5.6
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  multisite
--------------------------------------+------------------------
Changes (by rsiddharth):

 * keywords:  good-first-bug needs-patch => good-first-bug has-patch


Comment:

 Replying to [comment:5 audrasjb]:
 > Thanks for the patch @rsiddharth but the strings you added need to be
 ready for internationalization. There are not translatable for now in
 `53234.patch`.

 @audrasjb, Thank you for reviewing the patch. I've uploaded a new patch.
 See if it looks good.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53234#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 06:59:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 06:59:24 -0000
Subject: [wp-trac] [WordPress Trac] #46600: Twenty Nineteen: Flex order
 on comment form causes contents of comment_form_after to appear above the
 form
In-Reply-To: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
References: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
Message-ID: <074.dc786466d7b1dbca51cf899ecf0a8c09@wordpress.org>

#46600: Twenty Nineteen: Flex order on comment form causes contents of
comment_form_after to appear above the form
-------------------------------------+---------------------------------
 Reporter:  garrett-eclipse          |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:  5.0
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  accessibility, css
-------------------------------------+---------------------------------
Changes (by sabernhardt):

 * keywords:  has-patch => has-patch needs-refresh


Comment:

 The print styles apparently do not need editing with this way. Both
 `.comment-form-flex` and `.comment-form-wrapper` have the same level of
 specificity.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46600#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 14:55:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 14:55:21 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.09e1f3157971dc9e1450f91a1fc33892@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52958" 52958]:
 {{{
 #!CommitTicketReference repository="" revision="52958"
 Coding Standards: Rename the `$cat_ID` argument to `$cat_id` in
 `get_the_category_by_ID()`.

 This fixes a `Variable "$cat_ID" is not in valid snake_case format` WPCS
 warning.

 Props azouamauriac.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:31>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 15:03:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 15:03:57 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.82578aefee66a74dca32b672a1b27dc3@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52959" 52959]:
 {{{
 #!CommitTicketReference repository="" revision="52959"
 Docs: Correct variable references in `get_category_feed_link()` and
 `get_term_feed_link()` `@return` tags.

 The `$cat_id` and `$term_id` variables were replaced by `$cat` and
 `$term`, respectively.

 Follow-up to [52180].

 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:44>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 15:35:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 15:35:31 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.8b81290db66ada3e45a8f01bfde2680c@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52960" 52960]:
 {{{
 #!CommitTicketReference repository="" revision="52960"
 Coding Standards: Rename the `$bodyStarted` variable to `$body_started` in
 `WP_Http_Streams::request()`.

 This fixes a `Variable "$bodyStarted" is not in valid snake_case format`
 WPCS warning.

 Follow-up to [17555], [51825], [51929], [51940].

 Props azouamauriac.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:33>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 15:42:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 15:42:04 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.0ba9dcec4df26eba4a89ed3ce17e26d7@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52961" 52961]:
 {{{
 #!CommitTicketReference repository="" revision="52961"
 Coding Standards: Rename the `$requestPath` variable to `$request_path` in
 `WP_Http_Streams::request()`.

 This fixes a `Variable "$requestPath" is not in valid snake_case format`
 WPCS warning.

 Follow-up to [8516], [51825], [51929], [51940], [52960].

 Props azouamauriac.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 15:48:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 15:48:42 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.24dd4a4a26276d3f6c899cd51d1eac1c@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52962" 52962]:
 {{{
 #!CommitTicketReference repository="" revision="52962"
 Coding Standards: Rename the `$strHeaders` variable to `$headers` in
 `WP_Http_Streams::request()`.

 This fixes a `Variable "$strHeaders" is not in valid snake_case format`
 WPCS warning.

 Follow-up to [8516], [51825], [51929], [51940], [52960], [52961].

 Props azouamauriac.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 15:50:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 15:50:57 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.aebf9fb6f87829062bf09c38854c6169@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52963" 52963]:
 {{{
 #!CommitTicketReference repository="" revision="52963"
 Coding Standards: Rename the `$headerValue` variable to `$header_value` in
 `WP_Http_Streams::request()`.

 This fixes a `Variable "$headerValue" is not in valid snake_case format`
 WPCS warning.

 Follow-up to [8516], [51825], [51929], [51940], [52960], [52961], [52962].

 Props azouamauriac.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 16:01:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 16:01:17 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.64d3e31e4498478847a4fca3bb66114f@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52964" 52964]:
 {{{
 #!CommitTicketReference repository="" revision="52964"
 Coding Standards: Rename the `$strResponse` variable to `$response` in
 `WP_Http_Streams::request()`.

 This fixes a `Variable "$strResponse" is not in valid snake_case format`
 WPCS warning.

 For consistency, this commit also renames the `WP_Http::processResponse()`
 argument to `$response`.

 Follow-up to [8516], [51825], [51929], [51940], [52025], [52960], [52961],
 [52962], [52963].

 Props azouamauriac.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 16:04:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 16:04:47 -0000
Subject: [wp-trac] [WordPress Trac] #55427: Make .wp-block-post stylable via
 theme.json
Message-ID: <057.fb998f3d5443fde321d262c424a5e2cb@wordpress.org>

#55427: Make .wp-block-post stylable via theme.json
-----------------------------+-----------------------------
 Reporter:  Clarus Dignus    |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Themes           |    Version:  5.9.2
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 I can style various aspects of the Query Loop block via theme.json.

 E.g. core/post-template styles .wp-block-post-template, core/post-title
 styles .wp-block-post-title, etc.


 {{{
 "blocks": {
         "core/post-template": {
                 "border": {
                         "style": "solid",
                         "width": "1px",
                         "color": "#000"
                 }
         },
         "core/post-title": {
                 "border": {
                         "style": "solid",
                         "width": "1px",
                         "color": "#000"
                 }
         }
 }
 }}}


 However, core/post doesn't style .wp-block-post.


 {{{
 "blocks": {
         "core/post": {
                 "border": {
                         "style": "solid",
                         "width": "1px",
                         "color": "#000"
                 }
         }
 }
 }}}


 .wp-block-post is the container of each post outputted by the Query Loop
 block, i.e., it contains each post's title, featured image, date, excerpt,
 etc.

 Please make .wp-block-post stylable via theme.json like the elements it's
 within and elements within it.

 Currently, I'm limited to styling .wp-block-template via style.css. One of
 the downsides of this is that the style doesn't apply in the editor.

 core/post isn't a block in the sense that it can be selected and edited
 via the editor.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55427>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 16:10:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 16:10:38 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.d18d42d4d1e33e51cf5cda6a8435a7b4@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52965" 52965]:
 {{{
 #!CommitTicketReference repository="" revision="52965"
 Coding Standards: Rename the `$theBody` variable to `$body` in
 `WP_Http_Curl::request()`.

 This fixes a `Variable "$theBody" is not in valid snake_case format` WPCS
 warning.

 Follow-up to [8516], [51825], [51929], [51931], [51940], [52025], [52960],
 [52961], [52962], [52963], [52964].

 Props azouamauriac.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:38>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 16:23:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 16:23:13 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.2b03be894b1f6de61dbd03be75aa767b@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52966" 52966]:
 {{{
 #!CommitTicketReference repository="" revision="52966"
 Coding Standards: Use strict comparison in `wp-includes/class-wp-http-
 curl.php`.

 Follow-up to [17692], [25303], [29968].

 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 17:37:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 17:37:36 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.bfe9ba70e110b38ad74cda0e9da159dd@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52967" 52967]:
 {{{
 #!CommitTicketReference repository="" revision="52967"
 Coding Standards: Escape the comment post URL in
 `_wp_dashboard_recent_comments_row()`.

 Follow-up to [6705].

 Props kebbet.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 21:28:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 21:28:40 -0000
Subject: [wp-trac] [WordPress Trac] #55416: Version 5.9.2 upgrade -
 Elementor
In-Reply-To: <055.4a1d874d1418a55db56d13844cde2fe6@wordpress.org>
References: <055.4a1d874d1418a55db56d13844cde2fe6@wordpress.org>
Message-ID: <070.3e244ebc8df697cd77ddd2a48f3f6d03@wordpress.org>

#55416: Version 5.9.2 upgrade - Elementor
-----------------------------+----------------------
 Reporter:  juliekoehne      |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Upgrade/Install  |     Version:  5.9.2
 Severity:  major            |  Resolution:  invalid
 Keywords:                   |     Focuses:
-----------------------------+----------------------
Changes (by peterwilsoncc):

 * milestone:  Awaiting Review =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55416#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 20 23:57:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 20 Mar 2022 23:57:59 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.03253e33d7489f15d010f4312aed29dd@wordpress.org>

#32998: What's a weblog?
-----------------------------------------+----------------------
 Reporter:  johnjamesjacoby              |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  low                          |   Milestone:  6.0
Component:  Options, Meta APIs           |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+----------------------

Comment (by webcommsat):

 I would make two further suggestions to avoid the word 'here' which can
 cause confusion for accessibility and expectation.

 From my understanding of what will happen, suggest revising the text to:
 'In this area [use name if it has one], you can choose to display avatars
 of users who interact with the site.'

 Replying to [comment:10 costdev]:
 > Throwing my two cents in: I think this is both specific and broad enough
 to be fit for purpose.
 >
 >  An avatar is an image that can be associated with a user across
 multiple websites. Here, you can enable the display of avatars for users
 who interact with this site.
 >
 > - "image":
 >   - Implies "visual". ✅
 >   - Could be a photo. ✅
 >   - Could be a logo. ✅
 >   - Could be a cat. 😸
 >   - "visual representation" could mean an animated character - Think
 game console profiles.
 >   - In my experience, "visual representation" is not accessible
 language, and often needs further, specific explanation.
 >   - "image", on the other hand, is widely understood, second only to
 something like "pic" in English.
 >
 > - "can be"
 >   - Acknowledges that the user may not use it on other websites. ✅
 >     - The avatar is associated with an email address that the user may
 only use on this website.
 >     - The site owner doesn't need to know that it's associated with the
 user's email address.
 >   - Acknowledges that other websites used by the user may not have
 avatars enabled. ✅
 >   - Acknowledges Gravatar's copy: "You choose what to display on
 Gravatar-enabled sites: what you share on your profile is open to the
 world." ✅
 >
 > - "associated":
 >   - Accounts for an avatar that represents the user. ✅
 >   - Accounts for an avatar that represents the user's group (company,
 department, gaming clan). ✅
 >   - Accounts for an avatar that represents nothing. ✅
 >   - Accounts for default avatars. ✅
 >
 > - "users who interact with this site"
 >   - Does not differentiate between registered users and other visitors.
 ❓ - Is this correct?
 >   - Does not assume the species of the user. ✅
 >     - Democratising publishing means we welcome our inter-galactic
 visitors. 👽
 >
 > - Does not presume to know where the avatar will be used on the website.
 ✅

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 00:11:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 00:11:23 -0000
Subject: [wp-trac] [WordPress Trac] #54699: dir, lang,
 and xml:lang should be global attributes supported on all tags
In-Reply-To: <051.3929a185f51eb57c38100444430ddf90@wordpress.org>
References: <051.3929a185f51eb57c38100444430ddf90@wordpress.org>
Message-ID: <066.6a42c9349eff1b68239309668a95e8e2@wordpress.org>

#54699: dir, lang, and xml:lang should be global attributes supported on all tags
-------------------------------------------------+-------------------------
 Reporter:  upsuper                              |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Formatting                           |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests needs-docs  |     Focuses:
  needs-dev-note commit                          |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52968" 52968]:
 {{{
 #!CommitTicketReference repository="" revision="52968"
 KSES: Allow `lang`, `xml:lang`, `dir` attributes globally.

 Globally permit the `lang`, `xml:lang`, and `dir` attributes on all
 elements rather than a subset in accordance with the HTML specification.

 Props upsuper, SergeyBiryukov, mukesh27, audrasjb.
 Fixes #54699.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54699#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 00:29:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 00:29:11 -0000
Subject: [wp-trac] [WordPress Trac] #54698: Add 'ruby' tag and its
 friends to kses
In-Reply-To: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
References: <051.ded7cc606721b8ff42fbbebaeefc723d@wordpress.org>
Message-ID: <066.81a35a947ee9d1801ba722e58e5fa71f@wordpress.org>

#54698: Add 'ruby' tag and its friends to kses
------------------------------+-----------------------------
 Reporter:  upsuper           |       Owner:  SergeyBiryukov
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:  6.0
Component:  Formatting        |     Version:
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52969" 52969]:
 {{{
 #!CommitTicketReference repository="" revision="52969"
 KSES: Add support for `<ruby>` and related elements.

 `<ruby>` element and its friends are used to attach annotation text onto a
 piece of text. This is especially commonly used in Japanese content, but
 it can also been seen in content of other languages like Chinese.

 The set of elements to enable such functionality consists of `<ruby>`,
 `<rt>`, and `<rp>` in the [https://html.spec.whatwg.org/multipage/text-
 level-semantics.html#the-ruby-element HTML Standard], while some browsers
 (like Firefox) additionally support `<rb>` and `<rtc>` for more advanced
 formatting, which are not yet included in the official HTML spec, but can
 be found in a [https://www.w3.org/TR/html-ruby-extensions/ W3C extension].

 Props upsuper, mukesh27, SergeyBiryukov.
 Fixes #54698.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54698#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 00:36:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 00:36:33 -0000
Subject: [wp-trac] [WordPress Trac] #51142: Invalid Moment.js locale
 from get_user_locale()
In-Reply-To: <058.2846ac89cb2c84cdad00d08c8829781c@wordpress.org>
References: <058.2846ac89cb2c84cdad00d08c8829781c@wordpress.org>
Message-ID: <073.494d886a677ed9b775fe7967092460b1@wordpress.org>

#51142: Invalid Moment.js locale from get_user_locale()
--------------------------------+------------------------------
 Reporter:  slightlyfaulty      |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  External Libraries  |     Version:  5.0
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:  javascript
--------------------------------+------------------------------

Comment (by noisysocks):

 > `moment.defineLocale( 'en_US', { parentLocale: 'en' } )` should be
 called before `moment.updateLocale( 'en_US', {...} )`

 This makes sense to me!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51142#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 01:30:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 01:30:24 -0000
Subject: [wp-trac] [WordPress Trac] #55428: Improve cache priming in
 wp_get_nav_menu_items
Message-ID: <056.daace05c4d79828512617a4516e19c3a@wordpress.org>

#55428: Improve cache priming in wp_get_nav_menu_items
--------------------------+-----------------------------
 Reporter:  spacedmonkey  |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Menus         |    Version:  3.0
 Severity:  normal        |   Keywords:
  Focuses:  performance   |
--------------------------+-----------------------------
 In the `wp_get_nav_menu_items`, there are calls to get_terms and get_posts
 to prime object caches. There are new and better functions calls,
 `_prime_post_caches` and `_prime_term_caches` to prime caches.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55428>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 02:01:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 02:01:57 -0000
Subject: [wp-trac] [WordPress Trac] #55423: Gallery Block Issue
In-Reply-To: <053.35441a37a6642a61596ba7361ace4617@wordpress.org>
References: <053.35441a37a6642a61596ba7361ace4617@wordpress.org>
Message-ID: <068.d37114c77015e817d21e9b3b95eeecff@wordpress.org>

#55423: Gallery Block Issue
--------------------------+------------------------------
 Reporter:  papazetis     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Gallery       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by glendaviesnz):

 I wasn't able to replicate this on a fresh 5.9.2 install.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55423#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 02:04:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 02:04:05 -0000
Subject: [wp-trac] [WordPress Trac] #54572: Add a function for updating
 the existing role instead of removing, then adding one
In-Reply-To: <056.b2c66fa027339f31f120bd3712e73851@wordpress.org>
References: <056.b2c66fa027339f31f120bd3712e73851@wordpress.org>
Message-ID: <071.311a4d8e8e787785d26b46b33fabc6ac@wordpress.org>

#54572: Add a function for updating the existing role instead of removing, then
adding one
--------------------------------------+--------------------------
 Reporter:  maksimkuzmin              |       Owner:  audrasjb
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Role/Capability           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by peterwilsoncc):

 Thanks for the patch, @maksimkuzmin

 Based on a quick review, I have a few suggestions for improving your
 patch:

 * `update_role()` -- function's display name parameter can default to
 `null` to match the `WP_Roles::update_role()` method
 * It would be good to split the test up a bit. The first time an assertion
 fails in a test PHP Unit stops running the test (it knows it's failed). In
 this case, if the code to update the display names breaks, it would be
 handy to know whether the capabilities update code is working too.
 * The `empty( $role )` could be replaced by something more precise (ask
 yourself what you wish to test for). At the moment it could pass with `[
 54572 ]` which no body wants. I noticed this comes from `add_role` so it's
 possible that WordPress is stuck with it.

 The patch looks fairly close, thank you, it's a little tidying around the
 edges.

 Also, feel free to use a pull request on GitHub if you will find that
 easier, you'll just need to post a link to this ticket in the description.
 Most committers use the modern tools as much as possible.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54572#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 02:14:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 02:14:19 -0000
Subject: [wp-trac] [WordPress Trac] #45915: Update "New Admin Email
 Address" Email Wording
In-Reply-To: <053.1ee102959895e693e40e7504c2b36e7c@wordpress.org>
References: <053.1ee102959895e693e40e7504c2b36e7c@wordpress.org>
Message-ID: <068.4a73f7e95cd5eada477dfaa80f94804b@wordpress.org>

#45915: Update "New Admin Email Address" Email Wording
-------------------------+---------------------
 Reporter:  TwisterMc    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------

Comment (by peterwilsoncc):

 Related #43706.

 It also proposes changes to the new email message. Ideally both changes
 would go in to the same release to avoid doubling up the work for
 translators.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45915#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 02:14:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 02:14:38 -0000
Subject: [wp-trac] [WordPress Trac] #43706: Email with link to change
 admin email does not include proposed new email address.
In-Reply-To: <051.e8674074507faa5f4788d57d47e5a1c5@wordpress.org>
References: <051.e8674074507faa5f4788d57d47e5a1c5@wordpress.org>
Message-ID: <066.1c464b1a0f6cd623f245e1eb752bdb90@wordpress.org>

#43706: Email with link to change admin email does not include proposed new email
address.
-------------------------------------------------+-------------------------
 Reporter:  sshanky                              |       Owner:
                                                 |  SergeyBiryukov
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Users                                |     Version:  4.9.5
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch needs-      |     Focuses:
  refresh                                        |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 Related #45915.

 It also proposes changes to the new email message. Ideally both changes
 would go in to the same release to avoid doubling up the work for
 translators.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43706#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 02:21:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 02:21:02 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.f37958964fcfc4ff2915a671e143f6fd@wordpress.org>

#36949: Term exists should use get_terms internally
----------------------------+---------------------------
 Reporter:  spacedmonkey    |       Owner:  spacedmonkey
     Type:  enhancement     |      Status:  reopened
 Priority:  normal          |   Milestone:  6.0
Component:  Taxonomy        |     Version:  2.3
 Severity:  normal          |  Resolution:
 Keywords:  needs-dev-note  |     Focuses:  performance
----------------------------+---------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests needs-dev-note needs-testing commit
     => needs-dev-note


Comment:

 Replying to [comment:35 Chouby]:
 > May I ask to introduce a new filter `term_exists_args`?

 I think that makes sense, possibly with the `wp_` prefix to be polite to
 plugins. @spacedmonkey, would you be able to look at this?

 ----

 I've done a little keyword tidy up to reflect the need for a filter patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36949#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 02:28:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 02:28:48 -0000
Subject: [wp-trac] [WordPress Trac] #54034: Update jQuery UI Touch Punch
 to the latest version
In-Reply-To: <058.8b64e35a4ad4981e30adc18db2ff645d@wordpress.org>
References: <058.8b64e35a4ad4981e30adc18db2ff645d@wordpress.org>
Message-ID: <073.f54d7c8d0f3d6ac0c75b202663240615@wordpress.org>

#54034: Update jQuery UI Touch Punch to the latest version
-------------------------------------------------+-------------------------
 Reporter:  Hareesh Pillai                       |       Owner:  Hareesh
                                                 |  Pillai
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  External Libraries                   |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:
  testing-info dev-feedback                      |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 @azaozz and @Clorith do you have thoughts on updating jQuery UI Touch
 Punch?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54034#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 02:37:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 02:37:45 -0000
Subject: [wp-trac] [WordPress Trac] #54371: Add posts_results-like
 filters to WP_Query when return fields are ids or id=>parent
In-Reply-To: <055.7b327cf3f971cd1bc82c01df4c95cce4@wordpress.org>
References: <055.7b327cf3f971cd1bc82c01df4c95cce4@wordpress.org>
Message-ID: <070.ca4ded093f58c6e78ee87e0a9c72d554@wordpress.org>

#54371: Add posts_results-like filters to WP_Query when return fields are ids or
id=>parent
-------------------------+---------------------
 Reporter:  sc0ttkclark  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Query        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------

Comment (by peterwilsoncc):

 @spacedmonkey if you have any bandwidth, are you able to take a look at
 this? Both the related tickets Scott mentions in the description are
 yours.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54371#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 02:58:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 02:58:55 -0000
Subject: [wp-trac] [WordPress Trac] #54447: Site Icons on My Sites in
 multisite network causing performance issue
In-Reply-To: <051.d687bf3f592aa0cf10f2ef4a5216d7a0@wordpress.org>
References: <051.d687bf3f592aa0cf10f2ef4a5216d7a0@wordpress.org>
Message-ID: <066.1dd0c6b329f4ffe038a976688c0cbebe@wordpress.org>

#54447: Site Icons on My Sites in multisite network causing performance issue
-------------------------+-------------------------------------
 Reporter:  wslyhbb      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Toolbar      |     Version:  5.8
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  multisite, performance
-------------------------+-------------------------------------

Comment (by peterwilsoncc):

 Just to have it documented, the `lazy` loading mentioned in the thread
 above is a nice to have for frontend performance.

 The initial report related to PHP/backend performance from the
 `get_site_icon_url()` calls.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54447#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 03:14:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 03:14:07 -0000
Subject: [wp-trac] [WordPress Trac] #53370: Theme thumbnail/screenshot
 does not contain version string
In-Reply-To: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
References: <051.3a06ddf426d345c79d48278599045119@wordpress.org>
Message-ID: <066.bf0fbd254146349d73e4cbf4c6bd3616@wordpress.org>

#53370: Theme thumbnail/screenshot does not contain version string
-------------------------+-----------------------
 Reporter:  codente      |       Owner:  audrasjb
     Type:  enhancement  |      Status:  reopened
 Priority:  normal       |   Milestone:  6.0
Component:  Themes       |     Version:  5.7.2
 Severity:  minor        |  Resolution:
 Keywords:               |     Focuses:
-------------------------+-----------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch =>


Comment:

 Do additional items need a version string or is this ticket ready to
 close?

 The only additional location I could find was the theme REST endpoint.

 https://github.com/WordPress/wordpress-
 develop/blob/8db1549c0f1af05fbb919ad2eeb7f7bff5a63da9/src/wp-includes
 /rest-api/endpoints/class-wp-rest-themes-controller.php#L265-L268

 If the version string is required everywhere, then including the hash in a
 backward compatible fashion in `WP_Themes::get_screenshot()` seems a more
 sensible approach.

 Each of the items `has-patch` applies to has been committed, so I am
 removing the keyword to reflect any future work that might be required.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53370#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 03:38:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 03:38:13 -0000
Subject: [wp-trac] [WordPress Trac] #54561: Avoid translating several
 times widget media default strings
In-Reply-To: <050.8194aa47e159010e88e89c613a42c1b9@wordpress.org>
References: <050.8194aa47e159010e88e89c613a42c1b9@wordpress.org>
Message-ID: <065.518f42ed22c17aa75884fb0fb2e6b329@wordpress.org>

#54561: Avoid translating several times widget media default strings
-------------------------+--------------------------
 Reporter:  Chouby       |       Owner:  audrasjb
     Type:  enhancement  |      Status:  reviewing
 Priority:  normal       |   Milestone:  6.0
Component:  Widgets      |     Version:  4.8
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  performance
-------------------------+--------------------------

Comment (by peterwilsoncc):

 Does the static need to be cleared on `change_locale` to account for
 language switching plugins or similar? I set my site's language to
 Français and it all seemed good but I'd rather ask as others on this
 ticket deal with translations more often than I.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54561#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 03:53:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 03:53:48 -0000
Subject: [wp-trac] [WordPress Trac] #55352: Improve cache key generation
 in WP_Term_Query
In-Reply-To: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
References: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
Message-ID: <071.ae263c519fea3e2f20f6068dad7a597a@wordpress.org>

#55352: Improve cache key generation in WP_Term_Query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  4.7
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------
Changes (by peterwilsoncc):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52970" 52970]:
 {{{
 #!CommitTicketReference repository="" revision="52970"
 Taxonomy: Increase cache hits in `WP_Term_Query`.

 Increase the number of cache hits in `WP_Term_Query` by normalizing data
 included in the cache key.

 Arguments that do not affect the SQL query, eg `update_term_meta_cache`,
 are removed from cache key generation. Arguments that are accepted in
 multiple formats, eg a string and an array, are normalized for both the
 cache key and the SQL query.

 Props spacedmonkey.
 Fixes #55352.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55352#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 04:24:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 04:24:51 -0000
Subject: [wp-trac] [WordPress Trac] #55420: Warning thrown by method
 get_the_modified_author if author was removed
In-Reply-To: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
References: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
Message-ID: <072.9a8da2f9388134b2e900d5f8519ffba0@wordpress.org>

#55420: Warning thrown by method get_the_modified_author if author was removed
---------------------------+-----------------------------
 Reporter:  juanlopez4691  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Users          |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  administration
---------------------------+-----------------------------
Changes (by mukesh27):

 * version:  5.9.2 =>


Comment:

 Hi there!

 Welcome to Trac and thanks for the ticket and patch.

 Can you please share steps to replicate the issue because I can't
 replicate it from the given instruction?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55420#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 04:38:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 04:38:13 -0000
Subject: [wp-trac] [WordPress Trac] #29660: Functions in
 wp_includes/query.php assume non-null return value from get_queried_object
In-Reply-To: <050.b5a9fadf07eae567951b5c03e7027e68@wordpress.org>
References: <050.b5a9fadf07eae567951b5c03e7027e68@wordpress.org>
Message-ID: <065.4f27b349a1e775c6be4cf5544d9d1e4f@wordpress.org>

#29660: Functions in wp_includes/query.php assume non-null return value from
get_queried_object
-------------------------------------------------+-------------------------
 Reporter:  yellyc                               |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Query                                |     Version:  4.0
 Severity:  normal                               |  Resolution:
 Keywords:  2nd-opinion has-patch has-unit-      |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------

Comment (by zikubd):

 I'm getting similar warnings while trying to call this function on PHP
 version 8:
 {{{
 Warning: Attempt to read property "ID" on null in
 /Users/wedevs/Sites/Theme_Rat/wp-includes/class-wp-query.php on line 4123
 Warning: Attempt to read property "post_title" on null in
 /Users/wedevs/Sites/Theme_Rat/wp-includes/class-wp-query.php on line 4125
 Warning: Attempt to read property "post_name" on null in
 /Users/wedevs/Sites/Theme_Rat/wp-includes/class-wp-query.php on line 4127
 }}}

 How to reproduce this warning:

 {{{
 add_action( 'posts_results', 'my_prefix_func_name', 10, 2 );
 function my_prefix_func_name( $posts, $query ) {
     if ( is_page() ) { // here those warnings are triggred
         // extra logic
     }
     return $posts;
 }
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/29660#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 04:54:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 04:54:28 -0000
Subject: [wp-trac] [WordPress Trac] #48030: HTML5 input types are not
 being reset when submitting the addtag form
In-Reply-To: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
References: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
Message-ID: <072.38683e6e1598065c1de65998b9e64cbe@wordpress.org>

#48030: HTML5 input types are not being reset when submitting the addtag form
-----------------------------+---------------------------------------------
 Reporter:  stevegrunwell    |       Owner:  davidbaumwald
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  6.0
Component:  Taxonomy         |     Version:
 Severity:  minor            |  Resolution:  fixed
 Keywords:  has-patch        |     Focuses:  ui, javascript, administration
  needs-testing              |
-----------------------------+---------------------------------------------
Changes (by peterwilsoncc):

 * Attachment "48030.gif" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48030>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 05:00:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 05:00:23 -0000
Subject: [wp-trac] [WordPress Trac] #48030: HTML5 input types are not
 being reset when submitting the addtag form
In-Reply-To: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
References: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
Message-ID: <072.8bc54989ad1781374b48e957e77888e7@wordpress.org>

#48030: HTML5 input types are not being reset when submitting the addtag form
-------------------------------------+-------------------------------------
 Reporter:  stevegrunwell            |       Owner:  davidbaumwald
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:
 Severity:  minor                    |  Resolution:
 Keywords:  needs-testing needs-     |     Focuses:  ui, javascript,
  patch                              |  administration
-------------------------------------+-------------------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch needs-testing => needs-testing needs-patch
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 The selector is a little eager and removes the text from the submit button
 too. I've added a gif above to illustrate.

 I suggest
 * include the parent `div.form-field > ` in the selector
 * exclude button `type`s, including submit, reset, etc.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48030#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 08:43:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 08:43:47 -0000
Subject: [wp-trac] [WordPress Trac] #55420: Warning thrown by method
 get_the_modified_author if author was removed
In-Reply-To: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
References: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
Message-ID: <072.1260cddfdb5b970e67c833d580df89a1@wordpress.org>

#55420: Warning thrown by method get_the_modified_author if author was removed
---------------------------+-----------------------------
 Reporter:  juanlopez4691  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Users          |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  administration
---------------------------+-----------------------------

Comment (by juanlopez4691):

 @mukesh27 You can try as follows:
 1. Log in admin create a post with any existing user.
 2. Create a new user.
 3. Logout and login back as user /2/.
 4. Modify the post created in /1/
 5. Log out and login back as user /1/ (should have administrator role).
 6. Delete user #2.

 The result is:
 - `postmeta` field `_edit_last` for the modified post is still holding the
 removed user /2/.
 - Using method `get_the_modified_author` to retrieve the name of the user
 who last modified post #1 raises a warning, as described in the ticket.

 My proposed patch is just a defensive measure similar to what is applied
 in method `get_the_author_meta`, line 175 ([https://bit.ly/3N91DIi]).

 Another possible solution could be to modify file `wp-includes/author-
 template.php`, line 104, from
 `return apply_filters( 'the_modified_author', $last_user->display_name );`
 to
 `return apply_filters( 'the_modified_author', empty( $last_user ) ? '' :
 $last_user->display_name );`

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55420#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 08:53:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 08:53:13 -0000
Subject: [wp-trac] [WordPress Trac] #55420: Warning thrown by method
 get_the_modified_author if author was removed
In-Reply-To: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
References: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
Message-ID: <072.3bf2101c117fb4cd80cce010184696ed@wordpress.org>

#55420: Warning thrown by method get_the_modified_author if author was removed
---------------------------+-----------------------------
 Reporter:  juanlopez4691  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Users          |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  administration
---------------------------+-----------------------------

Comment (by mukesh27):

 Thanks for the steps.

 If I try to remove a user from WordPress it shows me the attached screen
 in which the first option removes posts/content that the user added on the
 site. If you select the 2nd option then it will assign a new author in the
 post/content which old author created.

 How do you delete the user?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55420#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 08:54:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 08:54:29 -0000
Subject: [wp-trac] [WordPress Trac] #55420: Warning thrown by method
 get_the_modified_author if author was removed
In-Reply-To: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
References: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
Message-ID: <072.3e51bb673f2815ee4c7379118dcfeae8@wordpress.org>

#55420: Warning thrown by method get_the_modified_author if author was removed
---------------------------+-----------------------------
 Reporter:  juanlopez4691  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Users          |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  administration
---------------------------+-----------------------------
Changes (by mukesh27):

 * Attachment "Delete User.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55420>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 09:01:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 09:01:18 -0000
Subject: [wp-trac] [WordPress Trac] #55420: Warning thrown by method
 get_the_modified_author if author was removed
In-Reply-To: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
References: <057.5250e72891a355c33e2e698948be4843@wordpress.org>
Message-ID: <072.3f0eb0b98229cdf7e074a719b4b7ba76@wordpress.org>

#55420: Warning thrown by method get_the_modified_author if author was removed
---------------------------+-----------------------------
 Reporter:  juanlopez4691  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Users          |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  administration
---------------------------+-----------------------------

Comment (by juanlopez4691):

 @mukesh27 Just the same way. The problem is that attributing a new user to
 all posts created by the removed user do not fix the `_edit_last` postmeta
 entries for those posts. It just updates column `post_author` in the
 `posts` table.

 Is not about who created the posts, but who modified them the last.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55420#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 09:15:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 09:15:09 -0000
Subject: [wp-trac] [WordPress Trac] #55429: Coding Standard: Use spaces for
 JSON instead of tabs
Message-ID: <053.ee2c94b037d4924223611baa8c7f77b3@wordpress.org>

#55429: Coding Standard: Use spaces for JSON instead of tabs
-----------------------------+-----------------------------
 Reporter:  scruffian        |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  General          |    Version:
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 When PHP outputs JSON using `json_encode`, there's no option to output it
 with tabs instead of spaces. This is particularly relevant in since
 https://github.com/WordPress/gutenberg/pull/39048 merged - we now convert
 theme.json files that were using tabs to spaces.

 We could use a regex to convert these spaces back to tabs, but maybe its
 simpler to default to spaces for JSON files since that is the format that
 PHP uses.

 Opening this ticket to start the discussion...

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55429>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 09:15:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 09:15:22 -0000
Subject: [wp-trac] [WordPress Trac] #55429: Coding Standard: Use spaces
 for JSON instead of tabs
In-Reply-To: <053.ee2c94b037d4924223611baa8c7f77b3@wordpress.org>
References: <053.ee2c94b037d4924223611baa8c7f77b3@wordpress.org>
Message-ID: <068.86f8e9781eaaa58bfa15c11b200dcf4a@wordpress.org>

#55429: Coding Standard: Use spaces for JSON instead of tabs
-----------------------------+------------------------------
 Reporter:  scruffian        |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------
Changes (by scruffian):

 * Attachment "json.patch" added.

 Coding standards change

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55429>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 09:50:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 09:50:34 -0000
Subject: [wp-trac] [WordPress Trac] #54572: Add a function for updating
 the existing role instead of removing, then adding one
In-Reply-To: <056.b2c66fa027339f31f120bd3712e73851@wordpress.org>
References: <056.b2c66fa027339f31f120bd3712e73851@wordpress.org>
Message-ID: <071.36a91b9725ca5eda6690dbf650e6d42a@wordpress.org>

#54572: Add a function for updating the existing role instead of removing, then
adding one
--------------------------------------+--------------------------
 Reporter:  maksimkuzmin              |       Owner:  (none)
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Role/Capability           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------
Changes (by audrasjb):

 * owner:  audrasjb => (none)


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54572#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 10:02:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 10:02:44 -0000
Subject: [wp-trac] [WordPress Trac] #55423: Gallery Block Issue
In-Reply-To: <053.35441a37a6642a61596ba7361ace4617@wordpress.org>
References: <053.35441a37a6642a61596ba7361ace4617@wordpress.org>
Message-ID: <068.2753004eab379892d80346de6e70de38@wordpress.org>

#55423: Gallery Block Issue
--------------------------+------------------------------
 Reporter:  papazetis     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Gallery       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by papazetis):

 Replying to [comment:2 glendaviesnz]:
 > I wasn't able to replicate this on a fresh 5.9.2 install.

 That happened when I updated Wp from 5.8.4 to 5.9.2
 All existing galleries return these errors.

 I can't reproduce it either on a fresh install.
 I installed 5.8.4, created a gallery and updated wp to 5.9.2

 On the website that I have the issue with, I deactivated all plugins and
 used the default twenty theme and I am still getting these errors.

 I'll do some new tests and try to reproduce it.

 https://prnt.sc/_DRvgnNHPmok

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55423#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 10:11:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 10:11:58 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.69be6dc3b1a415459fda2c70d9f4917e@wordpress.org>

#36949: Term exists should use get_terms internally
----------------------------+---------------------------
 Reporter:  spacedmonkey    |       Owner:  spacedmonkey
     Type:  enhancement     |      Status:  reopened
 Priority:  normal          |   Milestone:  6.0
Component:  Taxonomy        |     Version:  2.3
 Severity:  normal          |  Resolution:
 Keywords:  needs-dev-note  |     Focuses:  performance
----------------------------+---------------------------

Comment (by spacedmonkey):

 @Chouby @peterwilsoncc

 I am happy to add a new filter. But I think the change should be tracked
 by a new ticket. Any chance we could create a new ticket for this and I
 will start work on a patch?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36949#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 10:14:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 10:14:11 -0000
Subject: [wp-trac] [WordPress Trac] #54855: Ui issue on edit menu page
In-Reply-To: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
References: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
Message-ID: <069.58a694dd490342637ff8ff4e4a69aef3@wordpress.org>

#54855: Ui issue on edit menu page
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  audrasjb
     Type:  enhancement              |      Status:  reviewing
 Priority:  normal                   |   Milestone:  6.0
Component:  Menus                    |     Version:  5.8.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots good-    |     Focuses:  ui, css,
  first-bug has-patch                |  administration
-------------------------------------+-------------------------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-21 à 11.10.22.png" added.

 Before patch

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54855>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 10:14:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 10:14:45 -0000
Subject: [wp-trac] [WordPress Trac] #54855: Ui issue on edit menu page
In-Reply-To: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
References: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
Message-ID: <069.a281df69146e9f5fd484614d360f4b41@wordpress.org>

#54855: Ui issue on edit menu page
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  audrasjb
     Type:  enhancement              |      Status:  reviewing
 Priority:  normal                   |   Milestone:  6.0
Component:  Menus                    |     Version:  5.8.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots good-    |     Focuses:  ui, css,
  first-bug has-patch                |  administration
-------------------------------------+-------------------------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-21 à 11.09.51.png" added.

 After patch: better padding for bulk actions label

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54855>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 10:15:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 10:15:25 -0000
Subject: [wp-trac] [WordPress Trac] #54855: Ui issue on edit menu page
In-Reply-To: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
References: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
Message-ID: <069.6251cdaec0056d7df80b178adc57e820@wordpress.org>

#54855: Ui issue on edit menu page
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  audrasjb
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Menus                    |     Version:  5.8.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots good-    |     Focuses:  ui, css,
  first-bug has-patch                |  administration
-------------------------------------+-------------------------------------
Changes (by audrasjb):

 * status:  reviewing => accepted


Comment:

 Patch looks good to go. Committing right now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54855#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 10:15:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 10:15:34 -0000
Subject: [wp-trac] [WordPress Trac] #54855: Ui issue on edit menu page
In-Reply-To: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
References: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
Message-ID: <069.99b50e7eaa014dff6fbec3613d631923@wordpress.org>

#54855: Ui issue on edit menu page
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  audrasjb
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Menus                    |     Version:  5.8.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots good-    |     Focuses:  ui, css,
  first-bug has-patch commit         |  administration
-------------------------------------+-------------------------------------
Changes (by audrasjb):

 * keywords:  has-screenshots good-first-bug has-patch => has-screenshots
     good-first-bug has-patch commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54855#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 10:31:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 10:31:11 -0000
Subject: [wp-trac] [WordPress Trac] #54855: Ui issue on edit menu page
In-Reply-To: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
References: <054.813cf9be581003ec861bd268829e09ee@wordpress.org>
Message-ID: <069.16763d9f8647ea1043c7dfa8c9918e8f@wordpress.org>

#54855: Ui issue on edit menu page
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  audrasjb
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Menus                    |     Version:  5.8.3
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-screenshots good-    |     Focuses:  ui, css,
  first-bug has-patch commit         |  administration
-------------------------------------+-------------------------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52971" 52971]:
 {{{
 #!CommitTicketReference repository="" revision="52971"
 Menus: Improve padding on bulk action labels for small screens.

 Props sumitsingh, sabernhardt, ryokuhi, priyank9033, audrasjb, pbiron.
 Fixes #54855.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54855#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 11:13:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 11:13:22 -0000
Subject: [wp-trac] [WordPress Trac] #55429: Coding Standard: Use spaces
 for JSON instead of tabs
In-Reply-To: <053.ee2c94b037d4924223611baa8c7f77b3@wordpress.org>
References: <053.ee2c94b037d4924223611baa8c7f77b3@wordpress.org>
Message-ID: <068.ae25f882145ea87186c1c4777a16d404@wordpress.org>

#55429: Coding Standard: Use spaces for JSON instead of tabs
-----------------------------+------------------------------
 Reporter:  scruffian        |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  needs-refresh    |     Focuses:
-----------------------------+------------------------------
Changes (by SergeyBiryukov):

 * keywords:   => needs-refresh


Comment:

 Thanks for the patch! It looks like it has some unrelated changes from
 [52940] / #54272, marking as `needs-refresh`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55429#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 11:52:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 11:52:56 -0000
Subject: [wp-trac] [WordPress Trac] #55352: Improve cache key generation
 in WP_Term_Query
In-Reply-To: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
References: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
Message-ID: <071.d9a3bcd544f8de6824ae7c050618da1a@wordpress.org>

#55352: Improve cache key generation in WP_Term_Query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  4.7
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------

Comment (by SergeyBiryukov):

 Lines like this seem a bit too hard to read for me without spending some
 time to parse the logic:
 {{{
 $args['term_taxonomy_id'] = is_string( $args['term_taxonomy_id'] ) && 0
 === strlen( $args['term_taxonomy_id'] ) ? array() : array_map( 'intval',
 (array) $args['term_taxonomy_id'] );
 }}}

 I think this can be simplified to:
 {{{
 if ( '' === $args['term_taxonomy_id'] ) {
         $args['term_taxonomy_id'] = array();
 } else {
         $args['term_taxonomy_id'] = array_map( 'intval', (array)
 $args['term_taxonomy_id'] );
 }
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55352#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 11:54:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 11:54:17 -0000
Subject: [wp-trac] [WordPress Trac] #55352: Improve cache key generation
 in WP_Term_Query
In-Reply-To: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
References: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
Message-ID: <071.ed358028ecb8a0cb05099689485b4eca@wordpress.org>

#55352: Improve cache key generation in WP_Term_Query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  4.7
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52972" 52972]:
 {{{
 #!CommitTicketReference repository="" revision="52972"
 Coding Standards: Simplify some long conditions in `wp-includes/class-wp-
 term-query.php`.

 This aims to improve readability and make the logic easier to parse at a
 glance.

 Follow-up to [40293], [52970].

 See #55352, #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55352#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 11:54:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 11:54:18 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.d9dc0739020c3ea0bd3765bba37856f9@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52972" 52972]:
 {{{
 #!CommitTicketReference repository="" revision="52972"
 Coding Standards: Simplify some long conditions in `wp-includes/class-wp-
 term-query.php`.

 This aims to improve readability and make the logic easier to parse at a
 glance.

 Follow-up to [40293], [52970].

 See #55352, #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:44>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 12:03:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 12:03:43 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.fd2fcfc7a6e3e84524a2def269a9757b@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52973" 52973]:
 {{{
 #!CommitTicketReference repository="" revision="52973"
 Coding Standards: Wrap the `$this->request` property in `wp-includes
 /class-wp-*-query.php`.

 This aims to improve readability by fitting the values on a single screen
 to avoid horizontal scrolling.

 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:45>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 12:05:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 12:05:30 -0000
Subject: [wp-trac] [WordPress Trac] #55399: esc_xml() removes valid XML
 input ( input that is empty() )
In-Reply-To: <054.6f1ed67beb6072490bacc7335e1248d1@wordpress.org>
References: <054.6f1ed67beb6072490bacc7335e1248d1@wordpress.org>
Message-ID: <069.ba9c4f64d403a574526eb6db56a59b9d@wordpress.org>

#55399: esc_xml() removes valid XML input ( input that is empty() )
-------------------------------------------------+-------------------------
 Reporter:  rumpel2116                           |       Owner:  pbiron
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Formatting                           |     Version:  5.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:
  tests                                          |
-------------------------------------------------+-------------------------
Changes (by rumpel2116):

 * keywords:  has-patch needs-testing => has-patch needs-testing has-unit-
     tests


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55399#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 12:20:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 12:20:36 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.b5384331d606787fd7175eed929a5376@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52974" 52974]:
 {{{
 #!CommitTicketReference repository="" revision="52974"
 Coding Standards: Remove a one-time `$pieces` variable in `wp-includes
 /class-wp-*-query.php`.

 Use the existing `$clauses` variable instead for consistency.

 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 12:22:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 12:22:30 -0000
Subject: [wp-trac] [WordPress Trac] #55429: Coding Standard: Use spaces
 for JSON instead of tabs
In-Reply-To: <053.ee2c94b037d4924223611baa8c7f77b3@wordpress.org>
References: <053.ee2c94b037d4924223611baa8c7f77b3@wordpress.org>
Message-ID: <068.b2a508a7edadda79c96943e8653a35bf@wordpress.org>

#55429: Coding Standard: Use spaces for JSON instead of tabs
------------------------------+------------------------------
 Reporter:  scruffian         |       Owner:  (none)
     Type:  feature request   |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  needs-refresh     |     Focuses:
------------------------------+------------------------------
Changes (by johnbillion):

 * component:  General => Build/Test Tools


Comment:

 We all know this is an age-old discussion, but I recently learned that
 there's an accessibility benefit to tabs instead of spaces. It allows
 developers with vision difficulties to control the spacing in their editor
 which they cannot do with spaces:
 https://twitter.com/johnbillion/status/1380173004307595266.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55429#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 13:30:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 13:30:50 -0000
Subject: [wp-trac] [WordPress Trac] #51859: Add filter to
 get_the_author_link
In-Reply-To: <052.69822eaf6bde77cf6ee62ae12a27d833@wordpress.org>
References: <052.69822eaf6bde77cf6ee62ae12a27d833@wordpress.org>
Message-ID: <067.c9c5d6e0d3b43cc2553addf7274a9639@wordpress.org>

#51859: Add filter to get_the_author_link
-------------------------------------------------+-------------------------
 Reporter:  dshanske                             |       Owner:
                                                 |  davidbaumwald
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Formatting                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-refresh 2nd-opinion  |     Focuses:
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch needs-refresh 2nd-opinion


Comment:

 `@since` mentions needs to be refreshed. Also, instead of passing
 `$author_url` and `$display_name` specific variables, should we rather
 pass a full `WP_User` object?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51859#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 14:18:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 14:18:00 -0000
Subject: [wp-trac] [WordPress Trac] #54371: Add posts_results-like
 filters to WP_Query when return fields are ids or id=>parent
In-Reply-To: <055.7b327cf3f971cd1bc82c01df4c95cce4@wordpress.org>
References: <055.7b327cf3f971cd1bc82c01df4c95cce4@wordpress.org>
Message-ID: <070.7e5781bfdd339dddfff5062842d4cc9c@wordpress.org>

#54371: Add posts_results-like filters to WP_Query when return fields are ids or
id=>parent
-------------------------+---------------------
 Reporter:  sc0ttkclark  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Query        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------

Comment (by spacedmonkey):

 I think I prefer the approach from #41700 that only adds one filter but it
 cleaner for it.

 What is the benefit of multiple filters here?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54371#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 14:27:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 14:27:19 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.2154eb88199986aa8f2b2745c2f10000@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by jrf):

 @SergeyBiryukov I'm not a fan of some of the recent changes.

 Splitting long queries into separate parts and joining them using
 `implode()` makes the code ''less'' readable.

 If you want to improve those, you can either use multi-line strings or use
 `sprintf()`, which both make for more readable code.

 Example:
 {{{#!php
 <?php
 // Original code:
 $old_request   = "SELECT $found_rows $distinct $fields FROM {$wpdb->posts}
 $join WHERE 1=1 $where $groupby $orderby $limits";

 // More readable than implode:
 $old_request   = "
     SELECT $found_rows $distinct $fields
     FROM {$wpdb->posts}
     $join
     WHERE 1=1 $where
     $groupby
     $orderby
     $limits";

 // Alternative:
 $old_request   = "sprintf(
     'SELECT %s %s %s FROM %s %s WHERE 1=1 %s %s %s %s',
     $found_rows,
     $distinct,
     $fields,
     $wpdb->posts,
     $join,
     $where,
     $groupby,
     $orderby,
     $limits
 );
 }}}


 As for the changes from `array()` to `compact()`: '''this is a BC-break
 which should be reverted'''.
 You are changing the array which is passed to the filters from a
 numerically indexed array to an associative array and any code which is
 hooked into those filters which was approaching the array using numeric
 indexes will now be broken.

 See: https://3v4l.org/gUWOB

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:47>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 14:32:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 14:32:02 -0000
Subject: [wp-trac] [WordPress Trac] #51859: Add filter to
 get_the_author_link
In-Reply-To: <052.69822eaf6bde77cf6ee62ae12a27d833@wordpress.org>
References: <052.69822eaf6bde77cf6ee62ae12a27d833@wordpress.org>
Message-ID: <067.d2118920e5ccd3304627c51f74d0158f@wordpress.org>

#51859: Add filter to get_the_author_link
-------------------------------------------------+-------------------------
 Reporter:  dshanske                             |       Owner:
                                                 |  davidbaumwald
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Formatting                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-refresh 2nd-opinion  |     Focuses:
-------------------------------------------------+-------------------------

Comment (by davidbaumwald):

 @audrasjb That sounds fine.  Could use the `$authordata` global.  This
 would make all user data available to the filter callback.

 One other concern I have here is potential confusion with the existing
 [https://core.trac.wordpress.org/browser/branches/5.9/src/wp-includes
 /author-template.php#L372 author_link] filter.  I think renaming this new
 filter to `author_url_link_html` would be more appropriate.

 I'm working on adding some unit tests for this new filter.  I'll throw up
 a PR for easier review.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51859#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 14:38:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 14:38:59 -0000
Subject: [wp-trac] [WordPress Trac] #55430: Installation keeps on clobbering
 cshayward.com domain name with cjshayward.com
Message-ID: <054.746f00f9711b82c2b9a96e4206c399b3@wordpress.org>

#55430: Installation keeps on clobbering cshayward.com domain name with
cjshayward.com
----------------------------+-------------------------------
 Reporter:  CJSHayward      |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Database        |    Version:  5.9.2
 Severity:  critical        |   Keywords:  reporter-feedback
  Focuses:  administration  |
----------------------------+-------------------------------
 From https://stackoverflow.com/questions/71550140/how-can-i-unconfuse-my-
 server-between-cjshayward-com-and-cshayward-com:

 I have separate WordPress installations cjshayward.com and a present stub,
 cshayward.com. They are on the same host, with separate databases.

 I would like to log in to cshayward.com, but when I load cshayward.com/wp-
 admin, it has the right title but the form action is cjshayward.com/wp-
 login.php. Whenever I try to log in to the present stub's administrative
 console, it bounces me to the other site.

 I've tried deleting browsing history and using other browsers; I've looked
 in cshayward.com's wp-config.php to confirm no reference is stated to
 cjshayward.com, and I've looked through the Apache VirtualHost entry to
 confirm that HTTP connections are redirected to HTTPS and HTTPS refers to
 the files for the new site. Attempts to load cshayward.com/wp-admin
 redirect to https://cjshayward.com/wp-
 login.php?redirect_to=https%3A%2F%2Fcshayward.com%2Fwp-admin%2F&reauth=1 -
 on the old site, although the redirect URL is on the new site. The HTML is
 a mix of data from the old site and the new.

 How can I unconfuse the installation so that attempts to load
 cshayward.com/wp-admin redirect correctly to the new present stub's login
 apparatus?

 I can post non-private contents of wp-config data or query the database,
 but I do not presently know a reproducible way to log into the new site
 instead of the old, and looking at the config file plus Apache
 configuration has me drawing a near-blank.

 The source for https://cshayward.com/wp-login.php pulls the title for the
 new site and specifies a form submission URL on the old site, and not the
 unchanged title for the old site, but specifies to send the old site a
 redirect URL on the new site:


 {{{
     <!DOCTYPE html>
         <html lang="en-US">
         <head>
         <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
 />
         <title>Log In &lsaquo; C.S. Hayward: A Guide to &quot;The Good
 Parts&quot; &#8212; WordPress</title>
         <meta name='robots' content='max-image-preview:large, noindex,
 noarchive' />
     <link rel='dns-prefetch' href='//s.w.org' />
     <link rel='stylesheet' id='dashicons-css'
 href='https://cjshayward.com/wp-includes/css/dashicons.min.css?ver=5.9.2'
 type='text/css' media='all' />
     <link rel='stylesheet' id='buttons-css'  href='https://cjshayward.com
 /wp-includes/css/buttons.min.css?ver=5.9.2' type='text/css' media='all' />
     <link rel='stylesheet' id='forms-css'  href='https://cjshayward.com
 /wp-admin/css/forms.min.css?ver=5.9.2' type='text/css' media='all' />
     <link rel='stylesheet' id='l10n-css'  href='https://cjshayward.com/wp-
 admin/css/l10n.min.css?ver=5.9.2' type='text/css' media='all' />
     <link rel='stylesheet' id='login-css'  href='https://cjshayward.com
 /wp-admin/css/login.min.css?ver=5.9.2' type='text/css' media='all' />
         <meta name='referrer' content='strict-origin-when-cross-origin' />
                 <meta name="viewport" content="width=device-width" />
                 </head>
         <body class="login no-js login-action-login wp-core-ui  locale-en-
 us">
         <script type="text/javascript">
                 document.body.className = document.body.className.replace
 ('no-js','js');
         </script>
                 <div id="login">
                 <h1><a href="https://wordpress.org/">Powered by
 WordPress</a></h1>

                 <form name="loginform" id="loginform"
 action="https://cjshayward.com/wp-login.php" method="post">
                         <p>
                                 <label for="user_login">Username or Email
 Address</label>
                                 <input type="text" name="log"
 id="user_login" class="input" value="" size="20" autocapitalize="off" />
                         </p>

                         <div class="user-pass-wrap">
                                 <label for="user_pass">Password</label>
                                 <div class="wp-pwd">
                                         <input type="password" name="pwd"
 id="user_pass" class="input password-input" value="" size="20" />
                                         <button type="button"
 class="button button-secondary wp-hide-pw hide-if-no-js" data-toggle="0"
 aria-label="Show password">
                                                 <span class="dashicons
 dashicons-visibility" aria-hidden="true"></span>
                                         </button>
                                 </div>
                         </div>
                                                 <p
 class="forgetmenot"><input name="rememberme" type="checkbox"
 id="rememberme" value="forever"  /> <label for="rememberme">Remember
 Me</label></p>
                         <p class="submit">
                                 <input type="submit" name="wp-submit" id
 ="wp-submit" class="button button-primary button-large" value="Log In" />
 <input type="hidden" name="redirect_to" value="https://cjshayward.com/wp-
 admin/" />
 <input type="hidden" name="testcookie" value="1" />
                         </p>
                 </form>

                                         <p id="nav">
                                                                 <a
 href="https://cjshayward.com/wp-login.php?action=lostpassword">Lost your
 password?</a>
                         </p>
                                         <script type="text/javascript">
                         function wp_attempt_focus() {setTimeout(
 function() {try {d = document.getElementById( "user_login" );d.focus();
 d.select();} catch( er ) {}}, 200);}
     wp_attempt_focus();
     if ( typeof wpOnload === 'function' ) { wpOnload() }
 </script>
                                 <p id="backtoblog">
                         <a href="https://cjshayward.com/">&larr; Go to
 C.S. Hayward: A Guide to &quot;The Good Parts&quot;</a>          </p>
                         </div>
                         <script type='text/javascript'
 src='https://cjshayward.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0'
 id='jquery-core-js'></script>
     <script type='text/javascript' src='https://cjshayward.com/wp-
 includes/js/jquery/jquery-migrate.min.js?ver=3.3.2' id='jquery-migrate-
 js'></script>
     <script type='text/javascript' id='zxcvbn-async-js-extra'>
     /* <![CDATA[ */
     var _zxcvbnSettings = {"src":"https:\/\/cjshayward.com\/wp-
 includes\/js\/zxcvbn.min.js"};
     /* ]]> */
     </script>
     <script type='text/javascript' src='https://cjshayward.com/wp-
 includes/js/zxcvbn-async.min.js?ver=1.0' id='zxcvbn-async-js'></script>
     <script type='text/javascript' src='https://cjshayward.com/wp-
 includes/js/dist/vendor/regenerator-runtime.min.js?ver=0.13.9' id
 ='regenerator-runtime-js'></script>
     <script type='text/javascript' src='https://cjshayward.com/wp-
 includes/js/dist/vendor/wp-polyfill.min.js?ver=3.15.0' id='wp-polyfill-
 js'></script>
     <script type='text/javascript' src='https://cjshayward.com/wp-
 includes/js/dist/hooks.min.js?ver=1e58c8c5a32b2e97491080c5b10dc71c' id
 ='wp-hooks-js'></script>
     <script type='text/javascript' src='https://cjshayward.com/wp-
 includes/js/dist/i18n.min.js?ver=30fcecb428a0e8383d3776bcdd3a7834' id='wp-
 i18n-js'></script>
     <script type='text/javascript' id='wp-i18n-js-after'>
     wp.i18n.setLocaleData( { 'text direction\u0004ltr': [ 'ltr' ] } );
     </script>
     <script type='text/javascript' id='password-strength-meter-js-extra'>
     /* <![CDATA[ */
     var pwsL10n = {"unknown":"Password strength unknown","short":"Very
 weak","bad":"Weak","good":"Medium","strong":"Strong","mismatch":"Mismatch"};
     /* ]]> */
     </script>
     <script type='text/javascript' id='password-strength-meter-js-
 translations'>
     ( function( domain, translations ) {
         var localeData = translations.locale_data[ domain ] ||
 translations.locale_data.messages;
         localeData[""].domain = domain;
         wp.i18n.setLocaleData( localeData, domain );
     } )( "default", { "locale_data": { "messages": { "": {} } } } );
     </script>
     <script type='text/javascript' src='https://cjshayward.com/wp-admin/js
 /password-strength-meter.min.js?ver=5.9.2' id='password-strength-meter-
 js'></script>
     <script type='text/javascript' src='https://cjshayward.com/wp-
 includes/js/underscore.min.js?ver=1.13.1' id='underscore-js'></script>
     <script type='text/javascript' id='wp-util-js-extra'>
     /* <![CDATA[ */
     var _wpUtilSettings = {"ajax":{"url":"\/wp-admin\/admin-ajax.php"}};
     /* ]]> */
     </script>
     <script type='text/javascript' src='https://cjshayward.com/wp-
 includes/js/wp-util.min.js?ver=5.9.2' id='wp-util-js'></script>
     <script type='text/javascript' id='user-profile-js-extra'>
     /* <![CDATA[ */
     var userProfileL10n = {"user_id":"0","nonce":"1ddd65e585"};
     /* ]]> */
     </script>
     <script type='text/javascript' id='user-profile-js-translations'>
     ( function( domain, translations ) {
         var localeData = translations.locale_data[ domain ] ||
 translations.locale_data.messages;
         localeData[""].domain = domain;
         wp.i18n.setLocaleData( localeData, domain );
     } )( "default", { "locale_data": { "messages": { "": {} } } } );
     </script>
     <script type='text/javascript' src='https://cjshayward.com/wp-admin/js
 /user-profile.min.js?ver=5.9.2' id='user-profile-js'></script>
         <div class="clear"></div>
         </body>
         </html>
 }}}



 The "near" in near-blank is that the first, default HTTPS host in the
 Apache config is set to redirect to https://cjshayward.com, but this
 redirection should be an all or nothing deal. I can load the stub homepage
 from https://cshayward.com, so I don't think it is automatically
 redirecting; if that were happening, I'd expect a visit to the stub
 homepage to redirect to the original homepage, which isn't happening.

 This is true after wiping and re-creating the database.

 I read wordpress site address is to a different site and added to wp-
 config.php:


 {{{
 define('WP_SITE_URL', 'https://cshayward.com');
 define('WP_HOME', 'https://cshayward.com');

 }}}
 That still had things confused, but when I dropped and re-created the
 database with these settings in place, it stopped bouncing me to controls
 for the other site.

 --UPDATE--

 This represents an incomplete resolution.

 I was able, after making these changes, to get into cshayward.com/wp-admin
 itself and start editing a homepage. After 15 minutes or so the editor
 said my session had timed out and I needed to log in again, and the login
 redirected me to the login for cjshayward.com.

 Now the editor appears to be up to old tricks.

 More specifically, if I go to the "General Settings" panel, the "Wordpress
 Address (URL)" entry is cjshayward.com. Furthermore, if I change it to
 cshayward.com and click to save my changes, it displays a value of
 cjshayward.com that appears to be immune to change.

 From the console:


 {{{
 MariaDB [cshayward]> update cs_options set
 option_value="https://cshayward.com" where option_name = "siteurl";
 Query OK, 1 row affected (0.001 sec)
 Rows matched: 1  Changed: 1  Warnings: 0

 MariaDB [cshayward]> select * from cs_options limit 1;
 +-----------+-------------+-----------------------+----------+
 | option_id | option_name | option_value          | autoload |
 +-----------+-------------+-----------------------+----------+
 |         1 | siteurl     | https://cshayward.com | yes      |
 +-----------+-------------+-----------------------+----------+
 1 row in set (0.000 sec)

 }}}
 Then I reload the "General Settings" page and the option value is changed
 back.


 {{{
 MariaDB [cshayward]> select * from cs_options limit 1;
 +-----------+-------------+------------------------+----------+
 | option_id | option_name | option_value           | autoload |
 +-----------+-------------+------------------------+----------+
 |         1 | siteurl     | https://cjshayward.com | yes      |
 +-----------+-------------+------------------------+----------+
 1 row in set (0.000 sec)
 }}}

 I have never knowingly told the cshayward.com installation to go to
 cjshayward.com, and the hostname in /etc/hostname is technoluddites.org,
 which so far hasn't cropped up.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55430>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 14:48:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 14:48:38 -0000
Subject: [wp-trac] [WordPress Trac] #55430: Installation keeps on
 clobbering cshayward.com domain name with cjshayward.com
In-Reply-To: <054.746f00f9711b82c2b9a96e4206c399b3@wordpress.org>
References: <054.746f00f9711b82c2b9a96e4206c399b3@wordpress.org>
Message-ID: <069.ba9601e2fe2bf2367dca0d948103e63e@wordpress.org>

#55430: Installation keeps on clobbering cshayward.com domain name with
cjshayward.com
--------------------------+-----------------------------
 Reporter:  CJSHayward    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Database      |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  administration
--------------------------+-----------------------------
Changes (by ocean90):

 * status:  new => closed
 * severity:  critical => normal
 * version:  5.9.2 =>
 * milestone:  Awaiting Review =>
 * keywords:  reporter-feedback =>
 * resolution:   => invalid


Comment:

 Hello @CJSHayward, welcome to WordPress Trac!

 Please note that this Trac is used for enhancements and bug reporting for
 the WordPress core software, not for individual support questions. Stack
 Overflow or our [https://wordpress.org/support/forums/ support forums] are
 a better place for that.

 Anyway, to me this sounds like you're using an object cache and/or some
 advanced caching since your site has an `advanced-cache.php` drop-in in
 `wp-content`. You have to make sure that both sites are using different
 cache buckets.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55430#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 14:51:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 14:51:20 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.258b857fc0a17361843ae6277f7602df@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 Replying to [comment:47 jrf]:
 > As for the changes from `array()` to `compact()`: '''this is a BC-break
 which should be reverted'''.
 > You are changing the array which is passed to the filters from a
 numerically indexed array to an associative array and any code which is
 hooked into those filters which was approaching the array using numeric
 indexes will now be broken.
 >
 > See: https://3v4l.org/gUWOB

 Thanks for reviewing the changes and noting this!

 I will address the first suggestion shortly.

 For second one, however, unless I'm missing something, [52974] did **not**
 replace `array()` with `compact()`, but only relocated the `compact()`
 call while removing the redundant `array()` at the same time. All of these
 arrays were associative before the change, not numerically indexed.

 As far as I can tell, there is no functional difference between this:
 {{{
 $array = compact( array( 'a', 'b' ) );
 }}}
 and this:
 {{{
 $array = compact( 'a', 'b' );
 }}}
 https://3v4l.org/5WRUs seems to confirm that.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:48>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 15:00:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 15:00:50 -0000
Subject: [wp-trac] [WordPress Trac] #55431: add_theme_support for html5 on
 search-form not working
Message-ID: <053.dae1340eaa75431229a2d9f1fd7f4f8a@wordpress.org>

#55431: add_theme_support for html5 on search-form not working
---------------------------+-----------------------------
 Reporter:  blackawxs      |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Bundled Theme  |    Version:
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 I’m on WordPress 5.9.2 and using TwentyTwentyOne version 1.5

 I have a very odd situation within my child theme, in which the built in
 search form is not converting to HTML5 syntax.

 From my child theme I have the following files

 – style.css
 – screenshot.png
 – functions.php
 – front-page.php

 Within my functions.php, I have the following code:

 {{{#!php
   <?php
   function _ags_after_setup_theme() {
     add_theme_support( 'html5', array( 'search-form' ) );
   }
   add_action( 'after_setup_theme', '_ags_after_setup_theme' );
 }}}


 Within my font-page.php I have the following code :

 {{{#!php
 <?php
  *
  * @link https://developer.wordpress.org/themes/basics/template-hierarchy
 /#single-post
  *
  * @package WordPress
  * @subpackage Twenty_Twenty_One
  * @since Twenty Twenty-One 1.0
  */

 get_header();
 ?>

 <!--_ags - THE FRONT PAGE SEARCH TEST-->
 <p>the beginning of our front page content</p>
 <div class="search-form-container">
   <?php get_search_form(); ?>
 </div>

 <?php
 get_footer();
 }}}



 And when I go to my front page, the search form still looks like the
 following syntax:



 {{{
  <form role="search" method="get" class="search-form"
 action="http://nffa.agx:49206/">
         <label for="search-form-1">Search…</label>
         <input type="search" id="search-form-1" class="search-field"
 value="" name="s">
         <input type="submit" class="search-submit" value="Search">
   </form>
 }}}


 As you can see, no HTML5 conversion on the form.

 Why is that?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55431>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 15:05:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 15:05:39 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.6986f52d274a6a46570648eeac1232a2@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by jrf):

 > For second one, however, unless I'm missing something, [52974] did not
 replace array() with compact(), but only relocated the compact() call
 while removing the redundant array() at the same time. All of these arrays
 were associative before the change, not numerically indexed.

 @SergeyBiryukov Ah! I completely overlooked that those filters had a
 `compact()` within the filter call. My bad! (though still good to verify
 this was the case for all of them)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 15:27:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 15:27:06 -0000
Subject: [wp-trac] [WordPress Trac] #55431: add_theme_support for html5
 on search-form not working
In-Reply-To: <053.dae1340eaa75431229a2d9f1fd7f4f8a@wordpress.org>
References: <053.dae1340eaa75431229a2d9f1fd7f4f8a@wordpress.org>
Message-ID: <068.cca3085412d39f573ac027aded9c8ef2@wordpress.org>

#55431: add_theme_support for html5 on search-form not working
---------------------------+------------------------------
 Reporter:  blackawxs      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by joyously):

 The code is working as expected.
 The `get_search_form()` function first looks for a searchform.php file in
 the child or parent theme, and only if not found does it generate a form
 according to the `current_theme_supports` value for `html5`.
 Since the Twenty Twenty One theme supplies a searchform.php, that is what
 is output.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55431#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 16:55:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 16:55:38 -0000
Subject: [wp-trac] [WordPress Trac] #55412: Language "German (Austria)"
 outputs html lang incorrectly as "de-DE" not "de-AT" since WordPress
 version 5.9
In-Reply-To: <051.99371ec50aaee37bd8492a84a510e8a7@wordpress.org>
References: <051.99371ec50aaee37bd8492a84a510e8a7@wordpress.org>
Message-ID: <066.a46d49c35f9380053f2897d150a28070@wordpress.org>

#55412: Language "German (Austria)" outputs html lang incorrectly as "de-DE" not
"de-AT" since WordPress version 5.9
--------------------------+----------------------
 Reporter:  simjost       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  I18N          |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------

Comment (by simjost):

 @ocean90 thank you for the information, clarification and the quick
 action.
 The updated translations are available for WordPress version 5.9.2 (not
 below though).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55412#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 17:08:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 17:08:43 -0000
Subject: [wp-trac] [WordPress Trac] #54371: Add posts_results-like
 filters to WP_Query when return fields are ids or id=>parent
In-Reply-To: <055.7b327cf3f971cd1bc82c01df4c95cce4@wordpress.org>
References: <055.7b327cf3f971cd1bc82c01df4c95cce4@wordpress.org>
Message-ID: <070.ac7dd51f228bb6bc8aae93dd3742c41a@wordpress.org>

#54371: Add posts_results-like filters to WP_Query when return fields are ids or
id=>parent
-------------------------+---------------------
 Reporter:  sc0ttkclark  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0
Component:  Query        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------

Comment (by sc0ttkclark):

 @spacedmonkey In this case, the intention of the two separate filters is
 to allow the override to set up the posts array dependent upon how it
 should be. In one case it's a list of ID integers, in another it's a list
 of simple objects containing only ID and post_parent.

 If there was a suitable solution that simplified that based on the
 expectation of what $this->posts will contain on each return type, I'd
 love to see what that could be.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54371#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 17:22:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 17:22:16 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
Message-ID: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
----------------------------+-----------------------------
 Reporter:  stevegrunwell   |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Bootstrap/Load  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 The "plugin_loaded" action expects a single argument, `$plugin`, which
 should be a string representing the plugin that was just loaded (e.g.
 "jetpack/jetpack.php").

 The code to accomplish this currently looks like this:

 {{{
 // Load active plugins.
 foreach ( wp_get_active_and_valid_plugins() as $plugin ) {
         wp_register_plugin_realpath( $plugin );
         include_once $plugin;

         /**
          * Fires once a single activated plugin has loaded.
          *
          * @since 5.1.0
          *
          * @param string $plugin Full path to the plugin's main file.
          */
         do_action( 'plugin_loaded', $plugin );
 }
 unset( $plugin );
 }}}

 However, this can cause unexpected arguments to be passed to the action if
 the loaded plugin defines a `$plugin` variable, since they occupy the same
 variable scope. For example, consider this (very common) plugin pattern:

 {{{#!php
 # wp-content/plugins/my-plugin/my-plugin.php
 <?php
 /**
  * Plugin Name: My plugin
  */

 require_once __DIR__ . '/class-plugin.php';

 $plugin = new MyPlugin();
 $plugin->init();
 }}}

 When this plugin is loaded, the value of `$plugin` being passed to the
 "plugin_loaded" hook will be an instance of `MyPlugin`, but the
 expectation is that it will be the string "my-plugin/my-plugin.php".

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 17:35:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 17:35:27 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.e66df378500871068c20b8553db8451b@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
----------------------------+------------------------------
 Reporter:  stevegrunwell   |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Bootstrap/Load  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------

Comment (by joyously):

 WP has lots of global variables that other code can pollute. That's why
 the best practices page says to prefix everything:
 https://developer.wordpress.org/plugins/plugin-basics/best-practices
 /#prefix-everything

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 18:03:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 18:03:12 -0000
Subject: [wp-trac] [WordPress Trac] #55423: Gallery Block Issue
In-Reply-To: <053.35441a37a6642a61596ba7361ace4617@wordpress.org>
References: <053.35441a37a6642a61596ba7361ace4617@wordpress.org>
Message-ID: <068.b62fce991561cb8f517825a0d61754e6@wordpress.org>

#55423: Gallery Block Issue
--------------------------+------------------------------
 Reporter:  papazetis     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Gallery       |     Version:  5.9.2
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by papazetis):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 The issue is not related to WordPress.

 It seems it's an issue with wp all import cause the images are on gallery
 blocks but images IDs are not matching the ones on media library

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55423#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 18:31:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 18:31:38 -0000
Subject: [wp-trac] [WordPress Trac] #55433: Twenty Twenty-Two: Implement
 alternate json files
Message-ID: <050.99ce75ea0b7ae06ba452225ad2d4e6ee@wordpress.org>

#55433: Twenty Twenty-Two: Implement alternate json files
---------------------------+-----------------------------------
 Reporter:  kjellr         |      Owner:  (none)
     Type:  enhancement    |     Status:  new
 Priority:  normal         |  Milestone:  6.0
Component:  Bundled Theme  |    Version:
 Severity:  normal         |   Keywords:  needs-design-feedback
  Focuses:                 |
---------------------------+-----------------------------------
 When Twenty Twenty-Two was announced last year, the announcement post
 included some alternate json file mockups:

 https://make.wordpress.org/core/2021/10/06/introducing-twenty-twenty-two/

 These were not able to be bundled in with the theme, since the alternate
 theme.json styles functionality was not yet present in Gutenberg. Instead,
 they were temporarily built as a set of experimental child themes:

 https://github.com/WordPress/theme-experiments/pull/292

 Recently, support for alternate theme.json files has been added to
 Gutenberg, along with support for the fonts API. Together, these should
 unblock the original vision for these alternate styles.

 https://github.com/WordPress/gutenberg/pull/35619
 https://github.com/WordPress/gutenberg/pull/37140

 @beafialho and myself have recently made some minor color/font revisions
 to the original set of alternate styles, and we'd like to start building
 this in, with the goal of eventually merging this into the 6.0 release.

 [[Image(https://cldup.com/m5LhAqJU0F.png)]]

 I've got a patch begun, and will continue with it this week. I'm also
 marking this needs design feedback — I imagine we'll continue iterating on
 those colors and styles once we see them working in action.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55433>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 19:01:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 19:01:31 -0000
Subject: [wp-trac] [WordPress Trac] #55434: About Page for 6.0 Release
Message-ID: <054.18012c18e30c48289086da51f648bd5f@wordpress.org>

#55434: About Page for 6.0 Release
-------------------------+-------------------------------------------------
 Reporter:  webcommsat   |      Owner:  (none)
     Type:  enhancement  |     Status:  assigned
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Help/About   |    Version:
 Severity:  normal       |   Keywords:  message-strategy needs-design
  Focuses:  ui, docs,    |  needs-copy-review needs-docs needs-screenshots
  ui-copy                |
-------------------------+-------------------------------------------------
 This ticket includes the discussion, planning, bug scrubs, design, work
 and other records leading to the development and completion of the
 WordPress 5.9 release About page. Many teams are involved in this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55434>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 19:02:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 19:02:30 -0000
Subject: [wp-trac] [WordPress Trac] #46600: Twenty Nineteen: Flex order
 on comment form causes contents of comment_form_after to appear above the
 form
In-Reply-To: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
References: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
Message-ID: <074.b1cfb683f7ed0a64b28f84221b50ec35@wordpress.org>

#46600: Twenty Nineteen: Flex order on comment form causes contents of
comment_form_after to appear above the form
-----------------------------+---------------------------------
 Reporter:  garrett-eclipse  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Bundled Theme    |     Version:  5.0
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  accessibility, css
-----------------------------+---------------------------------
Changes (by sabernhardt):

 * keywords:  has-patch needs-refresh => has-patch


Comment:

 The pull request is updated, including the RTL stylesheet and correcting
 an HTML comment for another container.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46600#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 19:03:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 19:03:20 -0000
Subject: [wp-trac] [WordPress Trac] #55434: About Page for 6.0 Release
In-Reply-To: <054.18012c18e30c48289086da51f648bd5f@wordpress.org>
References: <054.18012c18e30c48289086da51f648bd5f@wordpress.org>
Message-ID: <069.1b11e70ff68739090a81c466f8060c79@wordpress.org>

#55434: About Page for 6.0 Release
-------------------------------------------------+-------------------------
 Reporter:  webcommsat                           |       Owner:  marybaum
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Help/About                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  message-strategy needs-design        |     Focuses:  ui, docs,
  needs-copy-review needs-docs needs-            |  ui-copy
  screenshots                                    |
-------------------------------------------------+-------------------------
Changes (by marybaum):

 * owner:  (none) => marybaum


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55434#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 19:04:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 19:04:53 -0000
Subject: [wp-trac] [WordPress Trac] #55434: About Page for 6.0 Release
In-Reply-To: <054.18012c18e30c48289086da51f648bd5f@wordpress.org>
References: <054.18012c18e30c48289086da51f648bd5f@wordpress.org>
Message-ID: <069.1e20d1ceea20dc636676f443b1f111b2@wordpress.org>

#55434: About Page for 6.0 Release
------------------------------------+--------------------------------
 Reporter:  webcommsat              |       Owner:  marybaum
     Type:  task (blessed)          |      Status:  assigned
 Priority:  normal                  |   Milestone:  6.0
Component:  Help/About              |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  needs-message-strategy  |     Focuses:  ui, docs, ui-copy
------------------------------------+--------------------------------
Changes (by marybaum):

 * keywords:
     message-strategy needs-design needs-copy-review needs-docs needs-
     screenshots
     => needs-message-strategy
 * type:  enhancement => task (blessed)
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55434#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 19:05:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 19:05:38 -0000
Subject: [wp-trac] [WordPress Trac] #55434: About Page for 6.0 Release
In-Reply-To: <054.18012c18e30c48289086da51f648bd5f@wordpress.org>
References: <054.18012c18e30c48289086da51f648bd5f@wordpress.org>
Message-ID: <069.5f8fd57d282529ca648d1419c3a31205@wordpress.org>

#55434: About Page for 6.0 Release
-------------------------------------+-------------------------------------
 Reporter:  webcommsat               |       Owner:  marybaum
     Type:  task (blessed)           |      Status:  assigned
 Priority:  high                     |   Milestone:  6.0
Component:  Help/About               |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-message-strategy   |     Focuses:  ui, docs,
  needs-design                       |  administration, ui-copy
-------------------------------------+-------------------------------------
Changes (by marybaum):

 * keywords:  needs-message-strategy => needs-message-strategy needs-design
 * priority:  normal => high
 * focuses:  ui, docs, ui-copy => ui, docs, administration, ui-copy


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55434#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 19:09:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 19:09:22 -0000
Subject: [wp-trac] [WordPress Trac] #55434: About Page for 6.0 Release
In-Reply-To: <054.18012c18e30c48289086da51f648bd5f@wordpress.org>
References: <054.18012c18e30c48289086da51f648bd5f@wordpress.org>
Message-ID: <069.c05c963e3e2672df6908b8bddd8cd607@wordpress.org>

#55434: About Page for 6.0 Release
-------------------------------------+-------------------------------------
 Reporter:  webcommsat               |       Owner:  marybaum
     Type:  task (blessed)           |      Status:  assigned
 Priority:  high                     |   Milestone:  6.0
Component:  Help/About               |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-message-strategy   |     Focuses:  ui, docs,
  needs-design                       |  administration, ui-copy
-------------------------------------+-------------------------------------
Description changed by davidbaumwald:

Old description:

> This ticket includes the discussion, planning, bug scrubs, design, work
> and other records leading to the development and completion of the
> WordPress 5.9 release About page. Many teams are involved in this.

New description:

 This ticket includes the discussion, planning, bug scrubs, design, work
 and other records leading to the development and completion of the
 WordPress 6.0 release About page. Many teams are involved in this.

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55434#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 19:16:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 19:16:11 -0000
Subject: [wp-trac] [WordPress Trac] #52501: Bad date format in data
 picker, depends on time format settings
In-Reply-To: <051.f223d58062d517f16d87e4b494eab58a@wordpress.org>
References: <051.f223d58062d517f16d87e4b494eab58a@wordpress.org>
Message-ID: <066.82ac7f837197544fc7a19ff33d09a1c8@wordpress.org>

#52501: Bad date format in data picker, depends on time format settings
-----------------------------+------------------------------
 Reporter:  MarekTP          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit  |     Version:  5.6.1
 Severity:  normal           |  Resolution:
 Keywords:  needs-patch      |     Focuses:
-----------------------------+------------------------------

Comment (by webcommsat):

 Highlighted in component bug scrub. To request polyglots assistance in
 testing based on last update by @sabernhardt.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52501#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 19:33:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 19:33:05 -0000
Subject: [wp-trac] [WordPress Trac] #48496: Filters post_row_actions and
 page_row_actions not apply at AJAX inline-save action
In-Reply-To: <058.4bc92a6567386d379f4b329794fdf944@wordpress.org>
References: <058.4bc92a6567386d379f4b329794fdf944@wordpress.org>
Message-ID: <073.6cfcd861c5268306731f3cffe2d71b3f@wordpress.org>

#48496: Filters post_row_actions and page_row_actions not apply at AJAX inline-save
action
-------------------------------------------------+-------------------------
 Reporter:  andrejovdienko                       |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:  5.2.4
 Severity:  normal                               |  Resolution:
 Keywords:  reporter-feedback needs-testing-     |     Focuses:
  info                                           |  administration
-------------------------------------------------+-------------------------
Changes (by webcommsat):

 * keywords:   => reporter-feedback needs-testing-info


Comment:

 Reporting feedback and needs testing info added to keywords in the bug
 scrub.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48496#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 19:44:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 19:44:46 -0000
Subject: [wp-trac] [WordPress Trac] #44990: Unhandle post_ids variable
 in custom bulk actions
In-Reply-To: <051.4a22d4afca12f27e5ee752cb7c9d64d4@wordpress.org>
References: <051.4a22d4afca12f27e5ee752cb7c9d64d4@wordpress.org>
Message-ID: <066.56827c09616aae6c92309073c47f5fc3@wordpress.org>

#44990: Unhandle post_ids variable in custom bulk actions
--------------------------------------+------------------------------
 Reporter:  gaupoit                   |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:  4.9.8
 Severity:  minor                     |  Resolution:
 Keywords:  dev-feedback 2nd-opinion  |     Focuses:
--------------------------------------+------------------------------

Comment (by marybaum):

 In the scrub: @davidb says, " I'll track down the commits here and see if
 my hunch is correct.  I'll ping the reporter to see if it's still an
 issue."

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44990#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:17:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:17:29 -0000
Subject: [wp-trac] [WordPress Trac] #55435: use_block_editor_for_post_type
 filter is broken in 5.9.2
Message-ID: <051.55ce10038aea4a0f1daf84dfbb7d1aac@wordpress.org>

#55435: use_block_editor_for_post_type filter is broken in 5.9.2
--------------------------+-----------------------------
 Reporter:  haykuro       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  trunk
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 https://github.com/WordPress/WordPress/commit/93d4851bbf9175bd62859ae3d42d266dd947b1f8

 This commit seems to have broken the `use_block_editor_for_post_type`
 filter in WP >= 5.9.

 https://github.com/WordPress/WordPress/blob/5.9.2/wp-includes/default-
 filters.php#L592

 Is part of default-filters:
 {{{#!php
 <?php
 add_action( 'use_block_editor_for_post_type',
 '_disable_block_editor_for_navigation_post_type', 10, 2 );

 }}}

 But that function `_disable_block_editor_for_navigation_post_type` is only
 registered if user is on admin screen.


 So, if you're on homepage and try to: `apply_filters(
 'use_block_editor_for_post_type', true, 'post' )` it will return null and
 throw a warning:

 {{{#!php
 call_user_func_array() expects parameter 1 to be a valid callback,
 function '_disable_block_editor_for_navigation_post_type' not found or
 invalid function name
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55435>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:18:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:18:20 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.40822469e36f23819e7ac0aa8ff9380f@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch needs-testing  |  javascript
-------------------------------------+-------------------------------------

Comment (by marybaum):

 Update: I'll do some review to see if the issues are fixed, then we can
 recheck at next week's scrub (28-3-2022).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35483#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:21:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:21:35 -0000
Subject: [wp-trac] [WordPress Trac] #55435:
 use_block_editor_for_post_type filter is broken in 5.9.2
In-Reply-To: <051.55ce10038aea4a0f1daf84dfbb7d1aac@wordpress.org>
References: <051.55ce10038aea4a0f1daf84dfbb7d1aac@wordpress.org>
Message-ID: <066.747c7dedbcc1f58bf86c2dc12a184425@wordpress.org>

#55435: use_block_editor_for_post_type filter is broken in 5.9.2
--------------------------+------------------------
 Reporter:  haykuro       |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  reviewing
 Priority:  normal        |   Milestone:  5.9.3
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => reviewing
 * milestone:  Awaiting Review => 5.9.3


Comment:

 Thanks for the report and welcome to WordPress Trac @haykuro,

 Moving for 5.9.3 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55435#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:21:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:21:36 -0000
Subject: [wp-trac] [WordPress Trac] #44990: Unhandle post_ids variable
 in custom bulk actions
In-Reply-To: <051.4a22d4afca12f27e5ee752cb7c9d64d4@wordpress.org>
References: <051.4a22d4afca12f27e5ee752cb7c9d64d4@wordpress.org>
Message-ID: <066.41352de38011752434b506b661d6c5a6@wordpress.org>

#44990: Unhandle post_ids variable in custom bulk actions
-------------------------------------+------------------------------
 Reporter:  gaupoit                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit          |     Version:  4.9.8
 Severity:  minor                    |  Resolution:
 Keywords:  reporter-feedback close  |     Focuses:
-------------------------------------+------------------------------
Changes (by davidbaumwald):

 * keywords:  dev-feedback 2nd-opinion => reporter-feedback close


Comment:

 @gaupoit It looks like this was resolved in
 [https://core.trac.wordpress.org/changeset/51111 r51111].  I'm going to
 flag this as a `close` candidate, but would like your feedback about
 whether the issue is fixed for you in the latest version of WordPress.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44990#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:23:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:23:11 -0000
Subject: [wp-trac] [WordPress Trac] #55229: Super broad selector for
 images max-width on WP 5.9
In-Reply-To: <051.86e5ffd74af378070ef933d2a403a255@wordpress.org>
References: <051.86e5ffd74af378070ef933d2a403a255@wordpress.org>
Message-ID: <066.58635f73343ae2be26f7b3bf970e2ff9@wordpress.org>

#55229: Super broad selector for images max-width on WP 5.9
--------------------------+--------------------------------
 Reporter:  hvianna       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Formatting    |     Version:  5.9.1
 Severity:  major         |  Resolution:  reported-upstream
 Keywords:                |     Focuses:  css
--------------------------+--------------------------------
Changes (by audrasjb):

 * keywords:  reporter-feedback needs-screenshots close =>
 * status:  new => closed
 * resolution:   => reported-upstream
 * milestone:  5.9.3 =>


Comment:

 Closing this ticket as `reported-upstream` since it was fixed on Gutenberg
 side.
 https://github.com/WordPress/gutenberg/issues/39021

 It's on the Gutenberg list for 5.9.3 backports.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55229#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:23:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:23:31 -0000
Subject: [wp-trac] [WordPress Trac] #55229: Super broad selector for
 images max-width on WP 5.9
In-Reply-To: <051.86e5ffd74af378070ef933d2a403a255@wordpress.org>
References: <051.86e5ffd74af378070ef933d2a403a255@wordpress.org>
Message-ID: <066.63bfd8e35ff9a5cf8588e5441a4417ae@wordpress.org>

#55229: Super broad selector for images max-width on WP 5.9
--------------------------+--------------------------------
 Reporter:  hvianna       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Formatting    |     Version:  5.9.1
 Severity:  major         |  Resolution:  reported-upstream
 Keywords:                |     Focuses:  css
--------------------------+--------------------------------

Comment (by audrasjb):

 Thanks everyone for reporting the issue 🙌

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55229#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:23:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:23:59 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.744492274a14b98dee4419d643fd3e3f@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  marybaum
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots needs-testing                      |  accessibility
-------------------------------------------------+-------------------------
Changes (by marybaum):

 * owner:  joedolson => marybaum
 * status:  accepted => assigned


Comment:

 Looks like we need to test the patch. I can do that when I'm working with
 the previous ticket from the scrib of 3-16-22.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55364#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:28:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:28:09 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.0e3972b157cc4fff958156ba9e19ac20@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
-------------------------------------------------+-------------------------
 Reporter:  ademos                               |       Owner:  gavinwye
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch needs-design needs-      |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by webcommsat):

 * keywords:  needs-patch needs-design => needs-patch needs-design needs-
     testing


Comment:

 Highlighted in component bug scrub 14 March 2022.
 Copying over update written by Nalini who is unable to add comments on
 this ticket.

 Summary:
 - this ticket was last updated three years ago as needing design for a
 prototype design.
 - Estelaris asked design channel for a review and design prototype. When
 update comes back from design, Mary advised core can produce a patch if
 still is a problem.
 - webcommsat: could not replicate the issue and asked if anyone else
 could.
 - MaryBaum and Meher to test async and add findings to the ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:28:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:28:20 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.361092c87352f6dd0325ec40b3427ee2@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
 Reporter:  ademos                    |       Owner:  marybaum
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+------------------------------
Changes (by marybaum):

 * keywords:  needs-patch needs-design needs-testing => needs-patch needs-
     design
 * owner:  gavinwye => marybaum
 * status:  accepted => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:29:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:29:31 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.342526dc816d707958d4fc2642a429e2@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
 Reporter:  ademos                    |       Owner:  marybaum
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+------------------------------

Comment (by marybaum):

 Added to my list of things to test. Also, @meher volunteered to test.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:29:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:29:31 -0000
Subject: [wp-trac] [WordPress Trac] #55435:
 use_block_editor_for_post_type filter is broken in 5.9.2
In-Reply-To: <051.55ce10038aea4a0f1daf84dfbb7d1aac@wordpress.org>
References: <051.55ce10038aea4a0f1daf84dfbb7d1aac@wordpress.org>
Message-ID: <066.f30275e67bc8ed514aac1c34612e49c6@wordpress.org>

#55435: use_block_editor_for_post_type filter is broken in 5.9.2
--------------------------+------------------------
 Reporter:  haykuro       |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  5.9.3
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by haykuro):

 * status:  reviewing => closed
 * resolution:   => duplicate


Comment:

 Duplicate of #54795.

 I just noticed there's an existing similar ticket here:
 https://core.trac.wordpress.org/ticket/54795 (2 months ago)

 My apologies if this is a duplicate.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55435#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:32:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:32:50 -0000
Subject: [wp-trac] [WordPress Trac] #53082: when using quick edit on
 category the formatting is stripped from category description
In-Reply-To: <051.0bd9fb208d53e1e3483f8d587bca3890@wordpress.org>
References: <051.0bd9fb208d53e1e3483f8d587bca3890@wordpress.org>
Message-ID: <066.e4a673353cb511510a198d26d62ef999@wordpress.org>

#53082: when using quick edit on category the formatting is stripped from category
description
-------------------------------+------------------------------
 Reporter:  Polinet            |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit    |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by webcommsat):

 Component bug scrub 14 March 2022:
 - @webcommsat could not replicate the issue
 - post scrub @marybaum could not replicate the issue
 - confirmed ticket could be fixed by @jbaudras could be closed as 'works
 for me'

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53082#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:33:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:33:16 -0000
Subject: [wp-trac] [WordPress Trac] #55230: Release 5.9.1 breaks
 administration login.
In-Reply-To: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
References: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
Message-ID: <072.47d58994784354f8d19fd5eb4c2c47e7@wordpress.org>

#55230: Release 5.9.1 breaks administration login.
------------------------------------+-----------------------------
 Reporter:  carlduranleau           |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  5.9.3
Component:  Login and Registration  |     Version:  5.9.1
 Severity:  blocker                 |  Resolution:
 Keywords:  reporter-feedback       |     Focuses:  administration
------------------------------------+-----------------------------
Changes (by audrasjb):

 * keywords:  needs-patch reporter-feedback => reporter-feedback


Comment:

 Hello @carlduranleau, do you still reproduce the issue? Several people
 tried to reproduce it on their side using WP_DEBUG set to true, and nobody
 succeed.

 Marking for `reporter-feedback`, pending steps to help reproduce the
 issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55230#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:37:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:37:43 -0000
Subject: [wp-trac] [WordPress Trac] #53082: when using quick edit on
 category the formatting is stripped from category description
In-Reply-To: <051.0bd9fb208d53e1e3483f8d587bca3890@wordpress.org>
References: <051.0bd9fb208d53e1e3483f8d587bca3890@wordpress.org>
Message-ID: <066.87ed00d73be122515a494bf1438c2fb0@wordpress.org>

#53082: when using quick edit on category the formatting is stripped from category
description
-------------------------------+------------------------------
 Reporter:  Polinet            |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit    |     Version:
 Severity:  normal             |  Resolution:  worksforme
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by webcommsat):

 * status:  new => closed
 * resolution:   => worksforme


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53082#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:41:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:41:45 -0000
Subject: [wp-trac] [WordPress Trac] #42892: save_post_customtype not
 firing on quick edit
In-Reply-To: <054.6f8cdca06529a52d657a38d45e4928a2@wordpress.org>
References: <054.6f8cdca06529a52d657a38d45e4928a2@wordpress.org>
Message-ID: <069.1587722e498be0a8a38bea16e42db3fd@wordpress.org>

#42892: save_post_customtype not firing on quick edit
-----------------------------+------------------------------
 Reporter:  dangerd512       |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit  |     Version:  4.9.1
 Severity:  normal           |  Resolution:
 Keywords:  close            |     Focuses:
-----------------------------+------------------------------

Comment (by webcommsat):

 Bug scrub summary 14 March & 21 March 2022.
 - this could not be reproduced in recent versions of WordPress. It appears
 to be no longer an issue from other comments too. @jbaudras confirmed
 could be closed as 'works-for-me'
 - testing done in scrubs by @webcommsat, @nalininonstopnewsuk, @marybaum,
 @jbaudras

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42892#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:42:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:42:04 -0000
Subject: [wp-trac] [WordPress Trac] #42892: save_post_customtype not
 firing on quick edit
In-Reply-To: <054.6f8cdca06529a52d657a38d45e4928a2@wordpress.org>
References: <054.6f8cdca06529a52d657a38d45e4928a2@wordpress.org>
Message-ID: <069.30d5790f610b7a80ce29afc45c239aed@wordpress.org>

#42892: save_post_customtype not firing on quick edit
-----------------------------+------------------------------
 Reporter:  dangerd512       |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit  |     Version:  4.9.1
 Severity:  normal           |  Resolution:  worksforme
 Keywords:  close            |     Focuses:
-----------------------------+------------------------------
Changes (by webcommsat):

 * status:  new => closed
 * resolution:   => worksforme


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42892#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:42:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:42:56 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2355117=3A_Possible_5?=
 =?utf-8?b?LjkgQnVnOiBVbmtub3duIGNoYXJhY3RlciAo77+8IG9yICVlZiViZiViYyAp?=
 =?utf-8?q?_on_content_title?=
In-Reply-To: <053.b81fc379153db7c724cf676bc0bbe3b4@wordpress.org>
References: <053.b81fc379153db7c724cf676bc0bbe3b4@wordpress.org>
Message-ID: <068.0265d85b748164ffdb236a1483fdd03b@wordpress.org>

#55117: Possible 5.9 Bug: Unknown character ( or %ef%bf%bc ) on content title
--------------------------+-----------------------
 Reporter:  cantuaria     |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  5.9.3
Component:  Permalinks    |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => assigned


Comment:

 ''self assigning for further investigation.''

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55117#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:45:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:45:42 -0000
Subject: [wp-trac] [WordPress Trac] #42474: bulk_edit_posts should honor
 the show_in_quick_edit property of taxonomies
In-Reply-To: <050.81ed0281315d9cf8d32d1d2e89f90090@wordpress.org>
References: <050.81ed0281315d9cf8d32d1d2e89f90090@wordpress.org>
Message-ID: <065.3ba6903ac7aa85629b28ba04e3edd196@wordpress.org>

#42474: bulk_edit_posts should honor the show_in_quick_edit property of taxonomies
-------------------------------------+------------------------------
 Reporter:  Chouby                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  performance
-------------------------------------+------------------------------

Comment (by webcommsat):

 Adding summary from @nalininonstopnewsuk as she is unable to add changes
 to the ticket.

 - This has a patch and appears just to need testing. Request to promote it
 at devchat on 16 March 2022.
 - Any additional updates requested to @sabernhardt to try and get this
 into a future release, and to @chouby if there was any update for the
 ticket






 Nalini:speech_balloon:  20:52
 If this is still live, could it be added to open floor for dev chat this
 week to get some testing of the patch to move it forward @marybaum?
 (edited

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42474#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:48:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:48:00 -0000
Subject: [wp-trac] [WordPress Trac] #42474: bulk_edit_posts should honor
 the show_in_quick_edit property of taxonomies
In-Reply-To: <050.81ed0281315d9cf8d32d1d2e89f90090@wordpress.org>
References: <050.81ed0281315d9cf8d32d1d2e89f90090@wordpress.org>
Message-ID: <065.3c83ecf3ecff65f2d8caa6dc72408d02@wordpress.org>

#42474: bulk_edit_posts should honor the show_in_quick_edit property of taxonomies
-------------------------------------+------------------------------
 Reporter:  Chouby                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  performance
-------------------------------------+------------------------------

Comment (by marybaum):

 Pending testing from @meher. Slack was down for a lot of India last week,
 wo presumably she'll catch up in due course.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42474#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:48:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:48:45 -0000
Subject: [wp-trac] [WordPress Trac] #41833: Excerpt disappear in excerpt
 mode post list, after quick edit
In-Reply-To: <052.2fc790b84d9b7f6d6fa7c67a6ba76c70@wordpress.org>
References: <052.2fc790b84d9b7f6d6fa7c67a6ba76c70@wordpress.org>
Message-ID: <067.3206087c3ed3e580447c87f108e58162@wordpress.org>

#41833: Excerpt disappear in excerpt mode post list, after quick edit
-----------------------------+------------------------------
 Reporter:  satnapar         |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit  |     Version:  4.8.1
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by webcommsat):

 Ticket raised in bug scrubs 14 March 2022 and requested testing in Dev
 Chat 16 March 2022.

 Please test. Thanks

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41833#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:55:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:55:43 -0000
Subject: [wp-trac] [WordPress Trac] #41833: Excerpt disappear in excerpt
 mode post list, after quick edit
In-Reply-To: <052.2fc790b84d9b7f6d6fa7c67a6ba76c70@wordpress.org>
References: <052.2fc790b84d9b7f6d6fa7c67a6ba76c70@wordpress.org>
Message-ID: <067.e0ccbe6653aa18b0d3c81b05ea191a07@wordpress.org>

#41833: Excerpt disappear in excerpt mode post list, after quick edit
-----------------------------+------------------------------
 Reporter:  satnapar         |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit  |     Version:  4.8.1
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by marybaum):

 @webcommsat just tested this and replicated the issue. I will test it too,
 and if I can replicate it too, it's a real thing, and it needs a patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41833#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 20:58:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 20:58:03 -0000
Subject: [wp-trac] [WordPress Trac] #55023: get_header() notice: Theme
 without header.php is deprecated
In-Reply-To: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
References: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
Message-ID: <064.4b2a224556f8772c38d9c8732f9b4ed9@wordpress.org>

#55023: get_header() notice: Theme without header.php is deprecated
--------------------------+------------------------
 Reporter:  kpdaa         |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  5.9.3
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  multisite
--------------------------+------------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => accepted


Comment:

 ''Self assigning for further investigation, and hopefully ship a patch in
 5.9.3.''

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55023#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 21:00:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 21:00:23 -0000
Subject: [wp-trac] [WordPress Trac] #41494: Quick Edit update
 functionality is inconsistent.
In-Reply-To: <059.2a50ead819621c356fcc8fa82385fffa@wordpress.org>
References: <059.2a50ead819621c356fcc8fa82385fffa@wordpress.org>
Message-ID: <074.4a0dbd6a77f59d482db81a91bb1b5a1f@wordpress.org>

#41494: Quick Edit update functionality is inconsistent.
-----------------------------+------------------------------
 Reporter:  umangvaghela123  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  needs-patch      |     Focuses:  administration
-----------------------------+------------------------------

Comment (by webcommsat):

 Component bug scrub 14 March 2022 - Ticket requested for advice on how
 best to take this forward to @costdev and @audrasjb

 There is currently no patch for this, nor update during the last five
 years. There is a suggestion for a tweak in Ajax.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41494#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 21:01:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 21:01:21 -0000
Subject: [wp-trac] [WordPress Trac] #40492: Twenty Fifteen: Jumping if
 there is content just before the closing body tag
In-Reply-To: <057.284cc44ea09922081368f4d3ce3a80d4@wordpress.org>
References: <057.284cc44ea09922081368f4d3ce3a80d4@wordpress.org>
Message-ID: <072.1d6e0a6b2689aa351fabefd89cdf3d52@wordpress.org>

#40492: Twenty Fifteen: Jumping if there is content just before the closing body
tag
-------------------------------------+-------------------------
 Reporter:  stephenharris            |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:  4.7.1
 Severity:  minor                    |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  javascript
-------------------------------------+-------------------------
Changes (by sabernhardt):

 * keywords:  has-patch needs-testing dev-feedback => has-patch needs-
               testing


Comment:

 I found my mistake: using fixed position to show the link made the `body`
 and `#page` height values the same. Text alignment with static position
 displays the link, and the body height is greater than `#page`.

 {{{
 function sabwp_twenty_fifteen_top_link_static() {
         echo '<div style="text-align:right;"><a href="#page"
 style="background:rgba(255,244,111,0.8);color:#157;padding:10px;">Back to
 top</a></div>';
 }
 add_action('wp_footer', 'sabwp_twenty_fifteen_top_link_static', 10);
 }}}

 The post content area needs to be shorter than the header, too.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40492#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 21:08:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 21:08:06 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2355117=3A_Possible_5?=
 =?utf-8?b?LjkgQnVnOiBVbmtub3duIGNoYXJhY3RlciAo77+8IG9yICVlZiViZiViYyAp?=
 =?utf-8?q?_on_content_title?=
In-Reply-To: <053.b81fc379153db7c724cf676bc0bbe3b4@wordpress.org>
References: <053.b81fc379153db7c724cf676bc0bbe3b4@wordpress.org>
Message-ID: <068.20712e99d005b7c2364b8c35f4dc1c9d@wordpress.org>

#55117: Possible 5.9 Bug: Unknown character ( or %ef%bf%bc ) on content title
--------------------------+-----------------------
 Reporter:  cantuaria     |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  5.9.3
Component:  Permalinks    |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------

Comment (by cantuaria):

 Just an update, looking at Google results again, the number of results
 containing this symbol at the URL in WordPress sites, increased
 substantitally, currently there is almost 30 pages of results for last
 week (when I created the ticket there had only 3 pages of results for the
 previous week), I assume this is due to more and more sites using the
 latest version.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55117#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 21:18:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 21:18:57 -0000
Subject: [wp-trac] [WordPress Trac] #55023: get_header() notice: Theme
 without header.php is deprecated
In-Reply-To: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
References: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
Message-ID: <064.dfab64caeffbe5212dbf6748138b7692@wordpress.org>

#55023: get_header() notice: Theme without header.php is deprecated
--------------------------+------------------------
 Reporter:  kpdaa         |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  5.9.3
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  multisite
--------------------------+------------------------

Comment (by manfcarlo):

 Just notifying that this was also reported at
 https://github.com/WordPress/gutenberg/issues/33989

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55023#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 22:04:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 22:04:32 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.a273003e77565bb449c28ab74ac34936@wordpress.org>

#36949: Term exists should use get_terms internally
----------------------------+---------------------------
 Reporter:  spacedmonkey    |       Owner:  spacedmonkey
     Type:  enhancement     |      Status:  reopened
 Priority:  normal          |   Milestone:  6.0
Component:  Taxonomy        |     Version:  2.3
 Severity:  normal          |  Resolution:
 Keywords:  needs-dev-note  |     Focuses:  performance
----------------------------+---------------------------

Comment (by peterwilsoncc):

 @spacedmonkey I am happy if you'd prefer that.

 @Chouby are you able to create the follow up ticket to ensure you get
 props when it gets committed?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36949#comment:38>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 22:15:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 22:15:51 -0000
Subject: [wp-trac] [WordPress Trac] #55436: Image Galleries are NOT
 displayed properly on SAFARI
Message-ID: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>

#55436: Image Galleries are NOT displayed properly on SAFARI
--------------------------+-----------------------------
 Reporter:  learnamo      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.2
 Severity:  critical      |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 WordPress image galleries are not displayed properly on the latest version
 of Safari released a week ago.

 Here is a screenshot of an image gallery on my website:
 https://www.icloud.com/iclouddrive/0a5zJXeBHnspN46JrJ80kJDHQ#1._Gallery_-
 _Working_fine

 Here is a screenshot of the same image gallery when you visit my website
 using the latest version of Safari: https://www.icloud.com/iclouddrive
 /01dPiwpfzrqvqKwucQy-9k-Kw#2._Gallery_-_Broken

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55436>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 22:33:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 22:33:24 -0000
Subject: [wp-trac] [WordPress Trac] #52252: PHP Notice when `monthnum`
 query var is set without the `year` QV
In-Reply-To: <048.2fa2f5cdba4027ca826911ac161e1c42@wordpress.org>
References: <048.2fa2f5cdba4027ca826911ac161e1c42@wordpress.org>
Message-ID: <063.0127e34446f5aef23cc05e4cdc3b38aa@wordpress.org>

#52252: PHP Notice when `monthnum` query var is set without the `year` QV
----------------------------------------------+----------------------------
 Reporter:  dd32                              |       Owner:  (none)
     Type:  defect (bug)                      |      Status:  reviewing
 Priority:  normal                            |   Milestone:  Future
                                              |  Release
Component:  Query                             |     Version:  4.3
 Severity:  normal                            |  Resolution:
 Keywords:  has-patch early needs-unit-tests  |     Focuses:
----------------------------------------------+----------------------------
Changes (by johnbillion):

 * owner:  johnbillion => (none)


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52252#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 22:34:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 22:34:05 -0000
Subject: [wp-trac] [WordPress Trac] #38734: Dogfood the Settings API
In-Reply-To: <055.9a97e3749b862643d6e29c1f16370fb9@wordpress.org>
References: <055.9a97e3749b862643d6e29c1f16370fb9@wordpress.org>
Message-ID: <070.163af50e742d13f06728a55c597f9d3b@wordpress.org>

#38734: Dogfood the Settings API
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  (none)
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  Future Release
Component:  Options, Meta APIs       |     Version:  2.7
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch settings-    |     Focuses:  accessibility,
  api                                |  administration
-------------------------------------+-------------------------------------
Changes (by johnbillion):

 * owner:  johnbillion => (none)


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38734#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 22:36:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 22:36:47 -0000
Subject: [wp-trac] [WordPress Trac] #53945: Local test workflow changes
 for installing Composer dependencies
In-Reply-To: <058.4f5cf461be4aeaed98ad865942be298b@wordpress.org>
References: <058.4f5cf461be4aeaed98ad865942be298b@wordpress.org>
Message-ID: <073.be3cf2fff5026d5bcadda7038a56249b@wordpress.org>

#53945: Local test workflow changes for installing Composer dependencies
------------------------------------------------+--------------------------
 Reporter:  hellofromTonya                      |       Owner:  johnbillion
     Type:  task (blessed)                      |      Status:  reopened
 Priority:  normal                              |   Milestone:  6.0
Component:  Build/Test Tools                    |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  has-patch has-testing-instructions  |     Focuses:
------------------------------------------------+--------------------------

Comment (by johnbillion):

 What's left to do here?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53945#comment:43>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 23:02:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 23:02:18 -0000
Subject: [wp-trac] [WordPress Trac] #54476: Improve image engine
 detection when output format adjusted with filter (example: WebP output)
 (was: Improve image engine detection when output format adjusted with
 filter.)
In-Reply-To: <059.dd466e6070f6af55c5f5b41615375d51@wordpress.org>
References: <059.dd466e6070f6af55c5f5b41615375d51@wordpress.org>
Message-ID: <074.59019fcfcfbf6f903c6d9aa0be2bba16@wordpress.org>

#54476: Improve image engine detection when output format adjusted with filter
(example: WebP output)
-------------------------------------+------------------------------
 Reporter:  adamsilverstein          |       Owner:  adamsilverstein
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.8
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+------------------------------

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54476#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 23:21:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 23:21:32 -0000
Subject: [wp-trac] [WordPress Trac] #55436: Image Galleries are NOT
 displayed properly on SAFARI
In-Reply-To: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
References: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
Message-ID: <067.d920fe6c748bc53287928065b1caf17c@wordpress.org>

#55436: Image Galleries are NOT displayed properly on SAFARI
--------------------------+------------------------------
 Reporter:  learnamo      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by vijayhardaha):

 Hey,
 I am unable to reproduce the issue https://snipboard.io/Fpct4y.jpg

 I am using **Safari Version 15.4 (17613.1.17.1.6)** & **macOs 12.3**

 You might be having a cache issue or something. Try Private window on
 safari.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55436#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 23:26:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 23:26:38 -0000
Subject: [wp-trac] [WordPress Trac] #51859: Add filter to
 get_the_author_link
In-Reply-To: <052.69822eaf6bde77cf6ee62ae12a27d833@wordpress.org>
References: <052.69822eaf6bde77cf6ee62ae12a27d833@wordpress.org>
Message-ID: <067.6a56451f48b8ca55e9f98e2d9a3184a0@wordpress.org>

#51859: Add filter to get_the_author_link
-------------------------------------------------+-------------------------
 Reporter:  dshanske                             |       Owner:
                                                 |  davidbaumwald
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Formatting                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch 2nd-opinion has-unit-      |     Focuses:
  tests assigned-for-commit                      |
-------------------------------------------------+-------------------------
Changes (by davidbaumwald):

 * keywords:  has-patch 2nd-opinion has-unit-tests => has-patch 2nd-opinion
     has-unit-tests assigned-for-commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51859#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 23:27:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 23:27:02 -0000
Subject: [wp-trac] [WordPress Trac] #52714: Add New User Autofill Bug
In-Reply-To: <054.9df492b8b2e085ae076fb5ca2a33644c@wordpress.org>
References: <054.9df492b8b2e085ae076fb5ca2a33644c@wordpress.org>
Message-ID: <069.967e17c8afe2d7edf9fd5e82f53e1ec4@wordpress.org>

#52714: Add New User Autofill Bug
-------------------------------------------------+-------------------------
 Reporter:  clonemykey                           |       Owner:
                                                 |  davidbaumwald
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:  5.6.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing assigned-    |     Focuses:  ui,
  for-commit                                     |  administration
-------------------------------------------------+-------------------------
Changes (by davidbaumwald):

 * keywords:  has-patch needs-testing => has-patch needs-testing assigned-
     for-commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52714#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 23:43:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 23:43:40 -0000
Subject: [wp-trac] [WordPress Trac] #55436: Image Galleries are NOT
 displayed properly on SAFARI
In-Reply-To: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
References: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
Message-ID: <067.af52c6d49f88fd7fcb2c82f0b7e0341b@wordpress.org>

#55436: Image Galleries are NOT displayed properly on SAFARI
--------------------------+------------------------------
 Reporter:  learnamo      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by learnamo):

 Replying to [comment:1 vijayhardaha]:
 > Hey,
 > I am unable to reproduce the issue https://snipboard.io/Fpct4y.jpg
 >
 > I am using **Safari Version 15.4 (17613.1.17.1.6)** & **macOs 12.3**
 >
 > You might be having a cache issue or something. Try Private window on
 safari.

 Hi @vijayhardaha,

 Thank you for your reply!

 The issue does not occur all the time. However, I invite you to visit the
 following pages with Chrome and Safari, so that you can spot the
 differences in the galleries:

 https://learnamo.com

 https://learnamo.com/lezioni/

 Best wishes,
 Graziana

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55436#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 23:47:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 23:47:11 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.c2d27a9804bc95ec8ceac71fbc1dd845@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
--------------------------------------+-----------------------
 Reporter:  Presskopp                 |       Owner:  audrasjb
     Type:  enhancement               |      Status:  accepted
 Priority:  normal                    |   Milestone:  6.0
Component:  Administration            |     Version:  4.7
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  ui-copy
--------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests dev-feedback => has-patch has-unit-
     tests


Comment:

 Just for information, I plan to update the patch and commit it tomorrow :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:47>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 23:50:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 23:50:49 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs
 file
In-Reply-To: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
References: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
Message-ID: <064.f1f91b55c0d784c4c6eb185056441a1d@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
-------------------------+------------------------------
 Reporter:  helen        |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------------------

Comment (by costdev):

 @helen I'll be going through the commits you have listed to check them as
 requested.

 What do you think is the best way to make commit suggestions for
 [https://github.com/WordPress/wordpress-develop/pull/2433 PR 2433]? Should
 we just leave a review comment on `# PHPCS`, for example, with the hashes
 and changesets so that they can be considered for the addition?

 Aside from that, we have `# Pinking shears` and `# PHPCS` at the moment.
 This seems like a manageable limit for now given the number of "Coding
 Standards" commits to be checked.

 I'm curious about everyone's thoughts on the approach and wonder when we
 should consider the PR for merging into Core. If the idea has support,
 should we commit the PR once commits have been reviewed and verified as
 stylistic-only changes, then proceed with additional PRs in a step-by-step
 approach, or?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 23:54:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 23:54:59 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.8cf8216869d973259a554f79cb3b4650@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
--------------------------------------+------------------------
 Reporter:  pbearne                   |       Owner:  flixos90
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------
Changes (by flixos90):

 * owner:  (none) => flixos90
 * status:  new => reviewing
 * milestone:  Awaiting Review => 6.0


Comment:

 This request has come up before in other places (e.g. media chat), and I
 agree it's worth addressing. Currently, every plugin that wants to do
 something to image tags in the frontend has to re-implement the same logic
 that core already has here.

 We also ran into it during the Performance Lab plugin development, but it
 has come up before. I think this enhancement is worth being included in
 WordPress 6.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 21 23:56:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 21 Mar 2022 23:56:32 -0000
Subject: [wp-trac] [WordPress Trac] #52683: Twenty Twenty-One: Block
 "more" text in link can't be changed
In-Reply-To: <053.542859deaa6edd2ec48c5fd6868ec812@wordpress.org>
References: <053.542859deaa6edd2ec48c5fd6868ec812@wordpress.org>
Message-ID: <068.71ad062527827c62b05769d1a2e771f5@wordpress.org>

#52683: Twenty Twenty-One: Block "more" text in link can't be changed
------------------------------------+------------------------
 Reporter:  neokendev               |       Owner:  audrasjb
     Type:  defect (bug)            |      Status:  reviewing
 Priority:  normal                  |   Milestone:  6.0
Component:  Bundled Theme           |     Version:  5.6.2
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+------------------------

Comment (by sabernhardt):

 @audrasjb Long posts should have a "Continue reading" link when blog and
 archive pages have the "Summary" Excerpt setting.

 With Summary, `the_excerpt` creates a link only when truncating the post
 text. If the post content is shorter than the `excerpt_length` value
 (default 55 words), it does not create a link to continue reading.

 But to get More link text specific to a post, that would only work with
 the Full text setting.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52683#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 00:08:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 00:08:08 -0000
Subject: [wp-trac] [WordPress Trac] #48030: HTML5 input types are not
 being reset when submitting the addtag form
In-Reply-To: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
References: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
Message-ID: <072.ccea722b9f26a22e66bc7bf3e8409df5@wordpress.org>

#48030: HTML5 input types are not being reset when submitting the addtag form
-------------------------------------+-------------------------------------
 Reporter:  stevegrunwell            |       Owner:  davidbaumwald
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:
 Severity:  minor                    |  Resolution:
 Keywords:  needs-testing needs-     |     Focuses:  ui, javascript,
  patch                              |  administration
-------------------------------------+-------------------------------------

Comment (by davidbaumwald):

 Per discussion with @peterwilsoncc, including the parent in the selector
 would force plugins/themes to follow the same pattern to take advantage of
 the form reset on submission.  As there's currently many plugins making
 use of this feature, the safe thing to do here is to omit the parent
 selector.

 However, the buttons do need to be accounted for.  Updated patch incoming.
 Would appreciate some additional testing to make sure we've covered the
 default fields while also allowing for extenders to use the feature with
 their added fields/buttons.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48030#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 00:08:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 00:08:54 -0000
Subject: [wp-trac] [WordPress Trac] #48030: HTML5 input types are not
 being reset when submitting the addtag form
In-Reply-To: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
References: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
Message-ID: <072.3f934320cd57c346d9c79f63ea24e3ec@wordpress.org>

#48030: HTML5 input types are not being reset when submitting the addtag form
-------------------------------------+-------------------------------------
 Reporter:  stevegrunwell            |       Owner:  davidbaumwald
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:
 Severity:  minor                    |  Resolution:
 Keywords:  needs-testing needs-     |     Focuses:  ui, javascript,
  patch                              |  administration
-------------------------------------+-------------------------------------
Changes (by davidbaumwald):

 * Attachment "48030.3.diff" added.

 Updated patch excluding buttons types

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48030>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 00:09:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 00:09:08 -0000
Subject: [wp-trac] [WordPress Trac] #48030: HTML5 input types are not
 being reset when submitting the addtag form
In-Reply-To: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
References: <057.11661e12a7358cff0bac7319663003fd@wordpress.org>
Message-ID: <072.c91b67d75cadfa89cf413d6e784b3bf8@wordpress.org>

#48030: HTML5 input types are not being reset when submitting the addtag form
-----------------------------+---------------------------------------------
 Reporter:  stevegrunwell    |       Owner:  davidbaumwald
     Type:  defect (bug)     |      Status:  reopened
 Priority:  normal           |   Milestone:  6.0
Component:  Taxonomy         |     Version:
 Severity:  minor            |  Resolution:
 Keywords:  needs-testing    |     Focuses:  ui, javascript, administration
  has-patch                  |
-----------------------------+---------------------------------------------
Changes (by davidbaumwald):

 * keywords:  needs-testing needs-patch => needs-testing has-patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48030#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 00:13:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 00:13:01 -0000
Subject: [wp-trac] [WordPress Trac] #55436: Image Galleries are NOT
 displayed properly on SAFARI
In-Reply-To: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
References: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
Message-ID: <067.4e5f79d4ee11d011c231c6915d40d126@wordpress.org>

#55436: Image Galleries are NOT displayed properly on SAFARI
--------------------------+------------------------------
 Reporter:  learnamo      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by vijayhardaha):

 Hey @learnamo,

 I checked the other pages, At the start, I didn't find anything, then I
 refresh the quickly so many time then I encountered this issue
 https://snipboard.io/47rZsa.jpg

 Here link and image HTML is rendered, but the image source is showing `1px
 x 1px` I also checked the network tab to check if that specific file is in
 the rendering list, so it wasn't there.

 To me, it looks like a Jetpack Lazy load issue. It's Ok most of the time
 but it randomly produces this behavior.

 You can try to disable the lazy load option from jetpack and then If
 you're able to see the same issue.

 You can also ask about it in Jetpack Support Forum to understand the cache
 on this kind of behavior
 https://wordpress.org/support/plugin/jetpack/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55436#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 00:13:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 00:13:26 -0000
Subject: [wp-trac] [WordPress Trac] #36308: get_attached_file() destroys
 file paths on Windows
In-Reply-To: <050.92eb671f89732a16ad562052bc684b6b@wordpress.org>
References: <050.92eb671f89732a16ad562052bc684b6b@wordpress.org>
Message-ID: <065.5cae94476d10696a6aa0661f72e031c1@wordpress.org>

#36308: get_attached_file() destroys file paths on Windows
-------------------------------------------------+-------------------------
 Reporter:  Whissi                               |       Owner:  stevenlinx
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch has-unit-   |     Focuses:
  tests dev-feedback                             |
-------------------------------------------------+-------------------------
Changes (by davidbaumwald):

 * keywords:  good-first-bug has-patch has-unit-tests => good-first-bug has-
     patch has-unit-tests dev-feedback


Comment:

 Refreshed the latest patch with [https://github.com/WordPress/wordpress-
 develop/pull/2442 PR #2442].  The magic sauce here is the `path_join`
 which uses `path_is_absolute` to make sure the root path isn't duplicated
 in the resulting path.

 I was able to verify this fixes the issue.  To test on Windows:

 1. Create a media item.
 1. Set its `_wp_attached_file` meta to something like
 `C:/WWW/Sites/demo/htdocs/wordpress/wp-
 content/uploads/2016/03/example.jpg`.
 1. Call `get_attached_file` for the attachment ID.

 Pre-patch, you should see a duplicated root in the path, as reported
 originally.  Post-patch, the path should be just what you set in as
 `_wp_attached_file`.

 Since we're messing with file paths here, I'd appreciate a good looks at
 this by some more experienced contributors/committers, even with the added
 tests.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36308#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 00:40:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 00:40:05 -0000
Subject: [wp-trac] [WordPress Trac] #55428: Improve cache priming in
 wp_get_nav_menu_items
In-Reply-To: <056.daace05c4d79828512617a4516e19c3a@wordpress.org>
References: <056.daace05c4d79828512617a4516e19c3a@wordpress.org>
Message-ID: <071.c74677fcd223e2da54bb309bd72c4661@wordpress.org>

#55428: Improve cache priming in wp_get_nav_menu_items
--------------------------+--------------------------
 Reporter:  spacedmonkey  |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Menus         |     Version:  3.0
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  performance
--------------------------+--------------------------
Changes (by peterwilsoncc):

 * milestone:  Awaiting Review => 6.0


Comment:

 The PR bot missed [https://github.com/WordPress/wordpress-
 develop/pull/2437#pullrequestreview-916529542 my review]. Linked for
 reference.

 While testing the pull request, I discovered the current priming of the
 term cache misses and each term is queried individually. I've moved this
 to the 6.0 milestone as I think it warrants it for the potential
 performance boost.

 Unit test notes:

 * it would be good to make sure the caches continue to be hit during the
 fetching and rendering of menus. If tests currently exist, I suspect they
 are not testing a render, terms or both but this needs confirming.

 Manual testing notes:

 * REST API endpoint for FSE

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55428#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 02:25:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 02:25:05 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.336fcac00abe754db9ce42dc3e64e250@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
----------------------------+------------------------------
 Reporter:  stevegrunwell   |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Bootstrap/Load  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  close           |     Focuses:
----------------------------+------------------------------
Changes (by peterwilsoncc):

 * keywords:   => close


Comment:

 My inclination is to close this ticket without a fix. No matter the
 variable name WP uses, a plugin could override it.

 If a plugin is trying to override the variable maliciously, the plugin
 author is missing the opportunity to do truly evil things by been able to
 run code on the web server.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 03:31:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 03:31:29 -0000
Subject: [wp-trac] [WordPress Trac] #55437: Bugfix: Display correct theme in
 site editor
Message-ID: <054.2c8a29c0d20871f5ff204327eeee5dbc@wordpress.org>

#55437: Bugfix: Display correct theme in site editor
-------------------------+-------------------------------------------------
 Reporter:  ptahdunbar   |      Owner:  (none)
     Type:  defect       |     Status:  new
  (bug)                  |
 Priority:  normal       |  Milestone:  Awaiting Review
Component:               |    Version:  trunk
  Administration         |
 Severity:  normal       |   Keywords:  has-patch needs-testing 2nd-opinion
  Focuses:  ui,          |
  administration         |
-------------------------+-------------------------------------------------
 Scenario:
 Child themes inherit template parts from the parent theme but on the site
 editor page, the "Added by" column defaults to displaying the child theme
 even though the template parts are inherited from the parent.

 This creates confusion as to where the actual templates are located.

 Patch:
 https://github.com/ptahdunbar/WordPress/commit/25bbf034af03c9a4ea33a79d01f4d9c079750344

 Probably should look into _build_block_template_result_from_post() as
 well.

 Possibly related to [52062]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55437>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 03:40:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 03:40:55 -0000
Subject: [wp-trac] [WordPress Trac] #55436: Image Galleries are NOT
 displayed properly on SAFARI
In-Reply-To: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
References: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
Message-ID: <067.5048d819bcd651c119b67927f6590565@wordpress.org>

#55436: Image Galleries are NOT displayed properly on SAFARI
-------------------------------+------------------------------
 Reporter:  learnamo           |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Editor             |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by costdev):

 * keywords:   => reporter-feedback
 * version:  5.9.2 =>
 * component:  General => Editor
 * severity:  critical => normal


Comment:

 @vijayhardaha, thanks for investigating this issue!

 Hi @learnamo, welcome to Trac!

 Please try disabling the Jetpack lazy load option as @vijayhardaha
 suggested and let us know if the gallery displays as expected.

 If the issue still occurs, please
 [https://github.com/WordPress/gutenberg/issues/new?assignees=&labels=&template=Bug_report.yml
 open a new issue] on the Gutenberg repository and comment here with a link
 to the issue.

 -----

 - Adding the `reporter-feedback` keyword as this issue currently requires
 a response from @learnamo.

 - The `Version` parameter is used to indicate which version of WordPress
 Core introduced an issue. As this isn't verified as an WordPress Core
 issue, I'll reset the `Version`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55436#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 04:33:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 04:33:53 -0000
Subject: [wp-trac] [WordPress Trac] #39736: Thumbnail src image link to
 direct large image, cause low page speed
In-Reply-To: <051.09fafdab9fadfe7e2a24415120ab233a@wordpress.org>
References: <051.09fafdab9fadfe7e2a24415120ab233a@wordpress.org>
Message-ID: <066.ea1bb622b3965db49f28466a80129fe2@wordpress.org>

#39736: Thumbnail src image link to direct large image, cause low page speed
-----------------------------+------------------------------
 Reporter:  mcky909          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Post Thumbnails  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  Need-More-info   |     Focuses:
-----------------------------+------------------------------
Changes (by nayana123):

 * keywords:   => Need-More-info


Comment:

 Hello @mcky909,

 I have checked the above issues from my end and could not be reproduced
 them now.

 Thank you

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39736#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 04:43:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 04:43:17 -0000
Subject: [wp-trac] [WordPress Trac] #54795: Bootstrap: Move navigation
 post type hooks to `admin-filters.php`
In-Reply-To: <047.3037a2798a4e649c49aff9a105ba0546@wordpress.org>
References: <047.3037a2798a4e649c49aff9a105ba0546@wordpress.org>
Message-ID: <062.3feb4f643cc5dca5e347ecb2f9174b19@wordpress.org>

#54795: Bootstrap: Move navigation post type hooks to `admin-filters.php`
----------------------------+---------------------
 Reporter:  dlh             |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Bootstrap/Load  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+---------------------

Comment (by noisysocks):

 > Should the new default actions and filters in 5.9 that call admin-only
 functions be moved to admin-filters.php? (They seemed to work as expected
 there when I tested.)

 This sounds right to me.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54795#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 05:00:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 05:00:36 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.49cb1d10859dc7e31dcde6e097c55473@wordpress.org>

#36907: Improved sticky post query
----------------------------------------+---------------------------
 Reporter:  spacedmonkey                |       Owner:  spacedmonkey
     Type:  enhancement                 |      Status:  assigned
 Priority:  normal                      |   Milestone:  6.0
Component:  Query                       |     Version:  3.5
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:  performance
----------------------------------------+---------------------------

Comment (by peterwilsoncc):

 [attachment:"36907.patch"] looks good to me.

 Not to self so I don't look it up again, `get_posts()` has `no_found_rows`
 set already so it's not needed here.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 05:37:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 05:37:17 -0000
Subject: [wp-trac] [WordPress Trac] #33885: meta_form performs a
 potentially expensive query
In-Reply-To: <050.42392201b1b954ae7ab98d4bbdbb19bc@wordpress.org>
References: <050.42392201b1b954ae7ab98d4bbdbb19bc@wordpress.org>
Message-ID: <065.138e6a3f47d57c48680352c83cc3ca56@wordpress.org>

#33885: meta_form performs a potentially expensive query
-------------------------------------+-------------------------------------
 Reporter:  jorbin                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Administration           |     Version:  4.3.1
 Severity:  critical                 |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  administration,
  needs-unit-tests                   |  performance
-------------------------------------+-------------------------------------

Comment (by chaion07):

 Thanks @jorbin for reporting this. This ticket was reviewed during a
 recent [https://wordpress.slack.com/archives/C02RQBWTW/p1647925574535769
 bug scrub session by the core team]. Here's the feedback received:
 01. change the JOIN part of the query, the approach is similar to #49278
 02. change the meta_key length

 Cheers!

 Props to @hilayt24 & @craigfrancis

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33885#comment:93>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 06:07:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 06:07:16 -0000
Subject: [wp-trac] [WordPress Trac] #40927: Passing a float as the
 position in add_menu_page can override other menu items
In-Reply-To: <054.3952f5b90c4dd00f8f2ab13814b18548@wordpress.org>
References: <054.3952f5b90c4dd00f8f2ab13814b18548@wordpress.org>
Message-ID: <069.b6ebe318063bf0fc4363d3c0bf7fd8f2@wordpress.org>

#40927: Passing a float as the position in add_menu_page can override other menu
items
-------------------------------------------------+-------------------------
 Reporter:  justinbusa                           |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.8
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:
  testing                                        |  administration
-------------------------------------------------+-------------------------
Changes (by chaion07):

 * keywords:  has-patch => has-patch dev-feedback needs-testing


Comment:

 Thanks @justinbusa for reporting this. The core team reviewed this ticket
 recently during a
 [https://wordpress.slack.com/archives/C02RQBWTW/p1647926913626359 bug
 scrub session]. Based on the feedback we're updating the ticket with the
 following:

 01. Added workflow needs-testing & dev-feedback
 02. Suggested approach should be to include the sort taken from $menu and
 applied to $submenu

 Props to @costdev

 Cheers!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40927#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 06:20:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 06:20:17 -0000
Subject: [wp-trac] [WordPress Trac] #40927: Passing a float as the
 position in add_menu_page can override other menu items
In-Reply-To: <054.3952f5b90c4dd00f8f2ab13814b18548@wordpress.org>
References: <054.3952f5b90c4dd00f8f2ab13814b18548@wordpress.org>
Message-ID: <069.c8a6c1f7c5386091bbfbc0a54abd3535@wordpress.org>

#40927: Passing a float as the position in add_menu_page can override other menu
items
-------------------------------------------------+-------------------------
 Reporter:  justinbusa                           |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.8
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:
  testing                                        |  administration
-------------------------------------------------+-------------------------

Comment (by costdev):

 To clarify:

 The testing and feedback should be for the approach
 [https://core.trac.wordpress.org/attachment/ticket/40927/40927.2.patch
 40927.2.patch] uses to resolve the ticket's issue, as well as
 testing/giving feedback on the change in the `$submenu` sorting algorithm
 to confirm that it doesn't introduce a regression and improves efficiency
 as intended.

 Additionally, as the change to the sorting algorithm isn't strictly part
 of this ticket, this change might be worth committing separately to make
 the history clearer.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40927#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 07:19:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 07:19:13 -0000
Subject: [wp-trac] [WordPress Trac] #55438: Flaky result when saving widgets
 in the Widgets Editor
Message-ID: <055.23828018540e63ab9c395b5e1a6cc1f2@wordpress.org>

#55438: Flaky result when saving widgets in the Widgets Editor
--------------------------+-----------------------------
 Reporter:  kevin940726   |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Widgets       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:  rest-api      |
--------------------------+-----------------------------
 I discovered this while trying to migrate the
 [https://github.com/WordPress/gutenberg/blob/3b1674a147c8e943b0d3727e0f4cbe379c2d9922/packages
 /e2e-tests/specs/widgets/editing-widgets.test.js#L123-L233 editing-
 widgets] e2e tests in Gutenberg. I think the test is currently skipped for
 the same reason.

 By un-skipping the test and running it several times, it sometimes fails
 at the last step where the snapshot doesn't match. It mysteriously
 contains a `wp_inactive_widgets: ''` field in the serialized result. I
 think the bug is from a race condition in the REST API. I managed to
 record a HAR file so that you can plug it in Chrome's devtools and inspect
 it.

 I'm not familiar with the PHP side of the code, but it seems like
 sometimes a widget block won't be saved to the specified sidebar, and
 instead be put inside `wp_inactive_widgets`.

 Maybe someone with more knowledge around this can help debugging it? Sorry
 that there's isn't a reliable reproduction steps though.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55438>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 07:19:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 07:19:56 -0000
Subject: [wp-trac] [WordPress Trac] #55438: Flaky result when saving
 widgets in the Widgets Editor
In-Reply-To: <055.23828018540e63ab9c395b5e1a6cc1f2@wordpress.org>
References: <055.23828018540e63ab9c395b5e1a6cc1f2@wordpress.org>
Message-ID: <070.036e35ea6150623baccfa8d3dc6a3cac@wordpress.org>

#55438: Flaky result when saving widgets in the Widgets Editor
--------------------------+------------------------------
 Reporter:  kevin940726   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Widgets       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  rest-api
--------------------------+------------------------------
Changes (by kevin940726):

 * Attachment "widgets.har" added.

 HAR file of the process when saving the widgets

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55438>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 07:40:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 07:40:48 -0000
Subject: [wp-trac] [WordPress Trac] #55401: Subpages of a web page can
 be called twice
In-Reply-To: <055.3f14c28994df00d9eeb59ba7b17bab48@wordpress.org>
References: <055.3f14c28994df00d9eeb59ba7b17bab48@wordpress.org>
Message-ID: <070.278f44a4212e7b0942804f8f4740b0c9@wordpress.org>

#55401: Subpages of a web page can be called twice
--------------------------+------------------------------
 Reporter:  manuel10503   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Permalinks    |     Version:  5.9.2
 Severity:  major         |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------

Comment (by ugyensupport):

 Yes, I can reproduce above mentioned bug.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55401#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 08:22:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 08:22:54 -0000
Subject: [wp-trac] [WordPress Trac] #55427: Make .wp-block-post stylable
 via theme.json
In-Reply-To: <057.fb998f3d5443fde321d262c424a5e2cb@wordpress.org>
References: <057.fb998f3d5443fde321d262c424a5e2cb@wordpress.org>
Message-ID: <072.1c251376c4a02303dcbec21dadbfe00d@wordpress.org>

#55427: Make .wp-block-post stylable via theme.json
-----------------------------+--------------------------------
 Reporter:  Clarus Dignus    |       Owner:  (none)
     Type:  feature request  |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Themes           |     Version:
 Severity:  normal           |  Resolution:  reported-upstream
 Keywords:                   |     Focuses:
-----------------------------+--------------------------------
Changes (by ocean90):

 * status:  new => closed
 * version:  5.9.2 =>
 * resolution:   => reported-upstream
 * milestone:  Awaiting Review =>


Comment:

 Hello @clarus-dignus, welcome to WordPress Trac!

 I see you already have posted this in
 https://github.com/WordPress/gutenberg/issues/39599 too which is actually
 the better place for such requests. Thus I'm closing this ticket as
 reported-upstream.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55427#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 08:51:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 08:51:58 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args filter
Message-ID: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>

#55439: Introduce term_exists_args filter
-------------------------+-----------------------------
 Reporter:  Chouby       |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Taxonomy     |    Version:  trunk
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 [52921], as each time `get_terms()` replaces a direct sql query,
 introduced a breaking changed.

 `get_terms()` is widely used and can be filtered with `terms_clauses`. The
 issue is that this filter will now be applied to `term_exists()` when it
 was not applied prior to [52921].

 Currently there is no way to determine if the call to `get_terms()` is
 done by `term_exists()` or not, so we cannot disable the filter
 accordingly. Unless using an ugly hack with debug_backtrace()...

 A new filter `term_exists_args` would allow to work around the breaking
 chanege in an elegant way.

 Related:
 [40994] introduced the filter `wp_get_object_term_args` after
 `wp_get_object_terms()` switched to use `get_terms()` since [38667].
 #42104 Same issue for `transform_query()`
 #54534 Same issue for `get_terms_by()`

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 08:54:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 08:54:24 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.15ecae3c258b6de37e8aa118d48c0b0c@wordpress.org>

#36949: Term exists should use get_terms internally
----------------------------+---------------------------
 Reporter:  spacedmonkey    |       Owner:  spacedmonkey
     Type:  enhancement     |      Status:  reopened
 Priority:  normal          |   Milestone:  6.0
Component:  Taxonomy        |     Version:  2.3
 Severity:  normal          |  Resolution:
 Keywords:  needs-dev-note  |     Focuses:  performance
----------------------------+---------------------------

Comment (by Chouby):

 @peterwilsoncc @spacedmonkey I opened #55439

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36949#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 09:07:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 09:07:34 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.0942b85a885e450a9411ed9eda4047c6@wordpress.org>

#55439: Introduce term_exists_args filter
-------------------------+---------------------------
 Reporter:  Chouby       |       Owner:  spacedmonkey
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  6.0
Component:  Taxonomy     |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------------
Changes (by spacedmonkey):

 * owner:  (none) => spacedmonkey
 * status:  new => assigned
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 09:08:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 09:08:56 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.011d7083ee938437fb4e9864420fe2af@wordpress.org>

#55439: Introduce term_exists_args filter
-------------------------+---------------------------
 Reporter:  Chouby       |       Owner:  spacedmonkey
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  6.0
Component:  Taxonomy     |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------------

Comment (by spacedmonkey):

 Thanks for the ticket @Chouby.

 There is a PR for your review at [https://github.com/WordPress/wordpress-
 develop/pull/2444 #2444]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 09:25:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 09:25:24 -0000
Subject: [wp-trac] [WordPress Trac] #55428: Improve cache priming in
 wp_get_nav_menu_items
In-Reply-To: <056.daace05c4d79828512617a4516e19c3a@wordpress.org>
References: <056.daace05c4d79828512617a4516e19c3a@wordpress.org>
Message-ID: <071.9e8bdc811d4924d078b6dac1e10aac6d@wordpress.org>

#55428: Improve cache priming in wp_get_nav_menu_items
--------------------------+---------------------------
 Reporter:  spacedmonkey  |       Owner:  spacedmonkey
     Type:  enhancement   |      Status:  assigned
 Priority:  normal        |   Milestone:  6.0
Component:  Menus         |     Version:  3.0
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  performance
--------------------------+---------------------------
Changes (by spacedmonkey):

 * owner:  (none) => spacedmonkey
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55428#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 09:39:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 09:39:33 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.aefce4f10e8b7cbb4c6869c1a1ccfec1@wordpress.org>

#55439: Introduce term_exists_args filter
-------------------------+---------------------------
 Reporter:  Chouby       |       Owner:  spacedmonkey
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  6.0
Component:  Taxonomy     |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+---------------------------

Comment (by Chouby):

 It's perfect for me.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 09:57:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 09:57:15 -0000
Subject: [wp-trac] [WordPress Trac] #55428: Improve cache priming in
 wp_get_nav_menu_items
In-Reply-To: <056.daace05c4d79828512617a4516e19c3a@wordpress.org>
References: <056.daace05c4d79828512617a4516e19c3a@wordpress.org>
Message-ID: <071.5f4b6d2112d48a4caaadd7ace18f55ec@wordpress.org>

#55428: Improve cache priming in wp_get_nav_menu_items
--------------------------+---------------------------
 Reporter:  spacedmonkey  |       Owner:  spacedmonkey
     Type:  enhancement   |      Status:  closed
 Priority:  normal        |   Milestone:  6.0
Component:  Menus         |     Version:  3.0
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |     Focuses:  performance
--------------------------+---------------------------
Changes (by spacedmonkey):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52975" 52975]:
 {{{
 #!CommitTicketReference repository="" revision="52975"
 Menus: Improve cache priming in the `wp_get_nav_menu_items` function.

 In `wp_get_nav_menu_items` multiple function calls to `get_terms` and
 `get_posts` were being used to load post/term objects into
 memory. This change replaces calls to `get_terms` and `get_posts` with
 calls to `_prime_post_caches` and
 `_prime_term_caches`. These functions are designed to prime object caches
 and do not have the overhead of a query object. This
 change also replaces multiple queries with a single query, saving many SQL
 queries per page load.

 Props Spacedmonkey, peterwilsoncc.
 Fixes #55428.
  --This line, and those below,
 will be ignored--

 M    src/wp-includes/nav-menu.php
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55428#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 10:16:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 10:16:21 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.4c29d52392cf6eb1a1d8be6cd2c9205a@wordpress.org>

#55439: Introduce term_exists_args filter
-------------------------------------+---------------------------
 Reporter:  Chouby                   |       Owner:  spacedmonkey
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+---------------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch needs-refresh


Comment:

 The PR looks great to me, I added a small nitpick concerning docblocks :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 10:54:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 10:54:05 -0000
Subject: [wp-trac] [WordPress Trac] #55440: Introduce a wrapper fro
 setcookie()
Message-ID: <050.af6a2ce285a103574b8543c6096d653d@wordpress.org>

#55440: Introduce a wrapper fro setcookie()
-------------------------+-----------------------------
 Reporter:  Chouby       |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 Recent browsers expect the parameter `samesite` to be set. A new parameter
 `sameparty` is on its way too.

 The old (PHP < 7.3) `setcookie()` signature doesn't accept these new
 parameters. It's however possible to set them with a hack.

 I propose to introduce a new `wp_set_cookie()` function to support all
 versions of PHP. I also propose to introduce a filter in this function.
 This should help for #37000.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55440>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 10:54:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 10:54:58 -0000
Subject: [wp-trac] [WordPress Trac] #55440: Introduce a wrapper fro
 setcookie()
In-Reply-To: <050.af6a2ce285a103574b8543c6096d653d@wordpress.org>
References: <050.af6a2ce285a103574b8543c6096d653d@wordpress.org>
Message-ID: <065.4193aa2b1a58a11242f8bd1eead56ce9@wordpress.org>

#55440: Introduce a wrapper fro setcookie()
-------------------------+------------------------------
 Reporter:  Chouby       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------
Changes (by Chouby):

 * Attachment "55440.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55440>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 10:56:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 10:56:58 -0000
Subject: [wp-trac] [WordPress Trac] #55440: Introduce a wrapper fro
 setcookie()
In-Reply-To: <050.af6a2ce285a103574b8543c6096d653d@wordpress.org>
References: <050.af6a2ce285a103574b8543c6096d653d@wordpress.org>
Message-ID: <065.6aaaa07d2b927415ee644c5c2fc9515f@wordpress.org>

#55440: Introduce a wrapper fro setcookie()
-------------------------+------------------------------
 Reporter:  Chouby       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------------------
Changes (by Chouby):

 * keywords:   => has-patch


Comment:

 The first patch is proposed for feedback on the function itself. It
 doesn't include the replacement of the current calls to `setcookie()` by
 `wp_set_cookie()`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55440#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 11:34:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 11:34:46 -0000
Subject: [wp-trac] [WordPress Trac] #54725: Test tool and unit test
 improvements for 6.0
In-Reply-To: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
References: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
Message-ID: <073.a96cc4d539449c4efae1d51a7a380794@wordpress.org>

#54725: Test tool and unit test improvements for 6.0
--------------------------------------+---------------------
 Reporter:  hellofromTonya            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by spacedmonkey):

 In [changeset:"52976" 52976]:
 {{{
 #!CommitTicketReference repository="" revision="52976"
 Build/Test Tools: Make comment cache group persistent in object-cache.php.

 After the comment cache group was made persistent in [37613], also make
 persistent in object-cache.php used for PHPUnit tests.

 See #54725
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54725#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 12:03:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 12:03:08 -0000
Subject: [wp-trac] [WordPress Trac] #55427: Make .wp-block-post stylable
 via theme.json
In-Reply-To: <057.fb998f3d5443fde321d262c424a5e2cb@wordpress.org>
References: <057.fb998f3d5443fde321d262c424a5e2cb@wordpress.org>
Message-ID: <072.c3df3e56c2a98fbb313ff992697092e8@wordpress.org>

#55427: Make .wp-block-post stylable via theme.json
-----------------------------+--------------------------------
 Reporter:  Clarus Dignus    |       Owner:  (none)
     Type:  feature request  |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Themes           |     Version:
 Severity:  normal           |  Resolution:  reported-upstream
 Keywords:                   |     Focuses:
-----------------------------+--------------------------------

Comment (by Clarus Dignus):

 Replying to [comment:1 ocean90]:
 > Hello @clarus-dignus, welcome to WordPress Trac!
 >
 > I see you already have posted this in
 https://github.com/WordPress/gutenberg/issues/39599 too which is actually
 the better place for such requests. Thus I'm closing this ticket as
 reported-upstream.

 Thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55427#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 12:34:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 12:34:54 -0000
Subject: [wp-trac] [WordPress Trac] #55430: Installation keeps on
 clobbering cshayward.com domain name with cjshayward.com
In-Reply-To: <054.746f00f9711b82c2b9a96e4206c399b3@wordpress.org>
References: <054.746f00f9711b82c2b9a96e4206c399b3@wordpress.org>
Message-ID: <069.36c6979d80434bde1e1de400c33971e3@wordpress.org>

#55430: Installation keeps on clobbering cshayward.com domain name with
cjshayward.com
--------------------------+-----------------------------
 Reporter:  CJSHayward    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Database      |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  administration
--------------------------+-----------------------------

Comment (by CJSHayward):

 There is no advanced-cache.php in wp-content; an ls yields:


 {{{
 root at technoluddites:~/cshayward# ls
 index.php        wp-blog-header.php    wp-cron.php        wp-mail.php
 license.txt      wp-comments-post.php  wp-includes        wp-settings.php
 readme.html      wp-config.php         wp-links-opml.php  wp-signup.php
 wp-activate.php  wp-config-sample.php  wp-load.php        wp-trackback.php
 wp-admin         wp-content            wp-login.php       xmlrpc.php
 root at technoluddites:~/cshayward#
 }}}


 I was trying to report this as a defect, apparently multiple defects.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55430#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:06:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:06:55 -0000
Subject: [wp-trac] [WordPress Trac] #54188: Different theme screenshot
 sizes are displayed in the customizer preview
In-Reply-To: <049.1b0f361e8b6821157b6f7ccf636e2184@wordpress.org>
References: <049.1b0f361e8b6821157b6f7ccf636e2184@wordpress.org>
Message-ID: <064.273dd6b2f3eef923b3dc7661f207564c@wordpress.org>

#54188: Different theme screenshot sizes are displayed in the customizer preview
-------------------------------------------------+-------------------------
 Reporter:  poena                                |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests needs-    |     Focuses:
  testing has-testing-info                       |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * keywords:  has-patch needs-unit-tests needs-testing => has-patch needs-
     unit-tests needs-testing has-testing-info


Comment:

 Marking as having `has-testing-info` as the instructions are in the
 description and screenshots.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54188#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:16:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:16:17 -0000
Subject: [wp-trac] [WordPress Trac] #54188: Different theme screenshot
 sizes are displayed in the customizer preview
In-Reply-To: <049.1b0f361e8b6821157b6f7ccf636e2184@wordpress.org>
References: <049.1b0f361e8b6821157b6f7ccf636e2184@wordpress.org>
Message-ID: <064.66ea2dca685956de2c5e61753e7d568f@wordpress.org>

#54188: Different theme screenshot sizes are displayed in the customizer preview
-------------------------------------------------+-------------------------
 Reporter:  poena                                |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info                                   |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * keywords:  has-patch needs-unit-tests needs-testing has-testing-info =>
     has-patch needs-testing has-testing-info


Comment:

 As this ticket addresses visual styling to hold the preview within a set
 sized container, A PHP unit test is not useful for this patch. Why? While
 it could capture the output buffer to check if the HTML and CSS are
 expected, it cannot check the result to ensure the changes actually
 resolve the preview issue.

 Removing the keyword.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54188#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:18:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:18:53 -0000
Subject: [wp-trac] [WordPress Trac] #54188: Different theme screenshot
 sizes are displayed in the customizer preview
In-Reply-To: <049.1b0f361e8b6821157b6f7ccf636e2184@wordpress.org>
References: <049.1b0f361e8b6821157b6f7ccf636e2184@wordpress.org>
Message-ID: <064.21f96d8b768129798a11fae0ae7a0cdc@wordpress.org>

#54188: Different theme screenshot sizes are displayed in the customizer preview
-------------------------------------------------+-------------------------
 Reporter:  poena                                |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info                                   |
-------------------------------------------------+-------------------------

Comment (by Boniu91):

 @poena Could you tell us what is the 1st theme in the screenshot? Second
 theme is TwentyTwenty but I can't identify the other one.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54188#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:23:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:23:51 -0000
Subject: [wp-trac] [WordPress Trac] #53177: WP_User_Query does not
 accept fields as string except ID
In-Reply-To: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
References: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
Message-ID: <065.eec0c1e233e07d7691839ebf86a0f736@wordpress.org>

#53177: WP_User_Query does not accept fields as string except ID
-------------------------------------------------+-------------------------
 Reporter:  rilwis                               |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:  4.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:  docs
  tests needs-refresh                            |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * keywords:  has-patch needs-testing has-unit-tests => has-patch needs-
     testing has-unit-tests needs-refresh


Comment:

 For [https://github.com/WordPress/wordpress-develop/pull/1779 PR 1779], I
 changed its target from `master` to `trunk`. It needs a rebase against
 `trunk` before a code review and testing can happen. @pbearne can you
 refresh the PR please?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53177#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:29:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:29:16 -0000
Subject: [wp-trac] [WordPress Trac] #53177: WP_User_Query does not
 accept fields as string except ID
In-Reply-To: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
References: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
Message-ID: <065.b21e04db44f3becb7de31b1ce05b67e2@wordpress.org>

#53177: WP_User_Query does not accept fields as string except ID
-------------------------------------------------+-------------------------
 Reporter:  rilwis                               |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:  4.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:  docs
  tests needs-refresh needs-testing-info         |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * keywords:  has-patch needs-testing has-unit-tests needs-refresh =>
     has-patch needs-testing has-unit-tests needs-refresh needs-testing-
     info


Comment:

 For testers to test and provide a Test Report, step-by-step testing
 instructions are needed to reproduce the issue and then validate if the PR
 resolves it. What can be helpful is to also provide code samples of how to
 test and/or any dependencies (such as a script or plugin).

 @rilwis could you provide testing instructions?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53177#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:35:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:35:27 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.517513764112fc76e21f3de5d9b36cd5@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
----------------------------+------------------------------
 Reporter:  stevegrunwell   |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Bootstrap/Load  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  close           |     Focuses:
----------------------------+------------------------------

Comment (by stevegrunwell):

 The issue isn't so much with what the ''plugin'' could do so much as that
 the "plugin_loaded" hook does not behave in a predictable or consistent
 manner.

 Consider the following example callback that simply logs plugins as
 they're loaded:

 {{{
 add_action('plugin_loaded', function ($plugin) {
     Logger::info(sprintf('Plugin %s was loaded', $plugin));
 });
 }}}

 Depending on what a third-party plugin does (or does not do) to the
 `$plugin` variable, this will either log "Plugin some-plugin/some-
 plugin.php was loaded" or throw an error (e.g. "Object of class SomePlugin
 cannot be converted to string").

 This puts the onus of type-checking the value from the hook on each and
 every callback:

 {{{
 add_action('plugin_loaded', function ($plugin) {
     if (! is_scalar($plugin)) {
         Logger::info('Some plugin was loaded, but we can\'t tell which
 one!');
     } else {
         Logger::info(sprintf('Plugin %s was loaded', $plugin));
     }
 });
 }}}

 The problem only becomes more apparent once scalar typehints are
 introduced (PHP 7.0+):

 {{{
 add_action('plugin_loaded', function (string $plugin) {
     Logger::info(sprintf('Plugin %s was loaded', $plugin));
 });
 }}}

   Uncaught TypeError: {closure}(): Argument #1 ($plugin) must be of type
 string, SomePlugin given

 Not to raise problems without solutions, there are a few ways this could
 be addressed:

 1. Wrap the `include_once` call in a closure to isolate its variable
 scope:
 {{{
 ( function () use ( $plugin ) {
     include_once $plugin;
 } )();
 }}}

 2. (Probably more "The WordPress Way™") Create a named function that
 includes the given file in an isolated scope, then call that within the
 `foreach ( wp_get_active_and_valid_plugins() as $plugin )` loop:
 {{{
 function load_plugin_file( $plugin ) {
     include_once $plugin;
 }
 }}}
 3. Update the DocBlock to indicate that this argument has type "mixed" and
 cannot be relied upon.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:38:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:38:06 -0000
Subject: [wp-trac] [WordPress Trac] #36710: Symlinked directories should
 not be deleted recursively
In-Reply-To: <048.ef6e38ed06a006607f1b9410360ae699@wordpress.org>
References: <048.ef6e38ed06a006607f1b9410360ae699@wordpress.org>
Message-ID: <063.24e5c6848f7ec750cefc503eacedc070@wordpress.org>

#36710: Symlinked directories should not be deleted recursively
-------------------------------------------------+-------------------------
 Reporter:  andy                                 |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Filesystem API                       |     Version:
 Severity:  major                                |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:
  testing-info                                   |  administration
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * milestone:  6.0 => Future Release


Comment:

 Given how long ago active contributions happened in this ticket and that
 it needs testing instructions for testers to properly test it to reproduce
 the issue and validate if the patch resolves it, moving this ticket back
 to `Future Release`.

 Once step-by-step testing instructions are provided, this one is ready to
 move back into a major release cycle.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36710#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:44:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:44:06 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.2d5e0e15c9413d2a7af21ed4855967c5@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+-----------------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Future Release
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  needs-patch    |     Focuses:
---------------------------+-----------------------------
Changes (by ocean90):

 * keywords:  close => needs-patch
 * component:  Bootstrap/Load => Plugins
 * milestone:  Awaiting Review => Future Release


Comment:

 This looks like a simple fix we can do. There was a previous change in
 [28644] although it was later adjusted in [50787].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:50:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:50:02 -0000
Subject: [wp-trac] [WordPress Trac] #55430: Installation keeps on
 clobbering cshayward.com domain name with cjshayward.com
In-Reply-To: <054.746f00f9711b82c2b9a96e4206c399b3@wordpress.org>
References: <054.746f00f9711b82c2b9a96e4206c399b3@wordpress.org>
Message-ID: <069.cee015032b6e1e1fd20a369531f97f91@wordpress.org>

#55430: Installation keeps on clobbering cshayward.com domain name with
cjshayward.com
--------------------------+-----------------------------
 Reporter:  CJSHayward    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Database      |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  administration
--------------------------+-----------------------------

Comment (by johnbillion):

 @CJSHayward Please check the wp-content directory instead of its parent
 directory. Regardless, the best place for you to get support with this
 issue is the main https://wordpress.org/support forums as this is almost
 certainly an issue specific to the configuration of your site and not a
 WordPress core problem.

 Best of luck!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55430#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:53:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:53:03 -0000
Subject: [wp-trac] [WordPress Trac] #54713: Build/Test Tools: Add unit
 tests for `feed_links_extra()`.
In-Reply-To: <051.ac57845cfdc90a01711f5456345a3c1d@wordpress.org>
References: <051.ac57845cfdc90a01711f5456345a3c1d@wordpress.org>
Message-ID: <066.7f7b099e7c85886732eea061fe9fefc6@wordpress.org>

#54713: Build/Test Tools: Add unit tests for `feed_links_extra()`.
--------------------------------------------+-----------------------------
 Reporter:  costdev                         |       Owner:  hellofromTonya
     Type:  task (blessed)                  |      Status:  reviewing
 Priority:  normal                          |   Milestone:  6.0
Component:  Build/Test Tools                |     Version:
 Severity:  normal                          |  Resolution:
 Keywords:  has-patch has-unit-tests early  |     Focuses:
--------------------------------------------+-----------------------------
Changes (by hellofromTonya):

 * owner:  costdev => hellofromTonya
 * status:  assigned => reviewing


Comment:

 Reassigning code review to me to get it into my review queue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54713#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:53:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:53:29 -0000
Subject: [wp-trac] [WordPress Trac] #54703: Remove comment feed link if
 get_post_comments_feed_link() returns empty
In-Reply-To: <055.48a2d3aa5fd769d9b992e03efd5e4a5e@wordpress.org>
References: <055.48a2d3aa5fd769d9b992e03efd5e4a5e@wordpress.org>
Message-ID: <070.44f55a74aac11a5547540a46756458d9@wordpress.org>

#54703: Remove comment feed link if get_post_comments_feed_link() returns empty
-------------------------------------+-----------------------
 Reporter:  barryceelen              |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Feeds                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  template
-------------------------------------+-----------------------

Comment (by Boniu91):

 @barryceelen Thank you for creating the ticket. Could you post the exact
 steps that should be done in order to reproduce the issue and confirm the
 patch?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54703#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 13:55:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 13:55:16 -0000
Subject: [wp-trac] [WordPress Trac] #54736: get_sample_permalink unsets
 $post->filter even though this is a public property.
In-Reply-To: <054.685942439bfac8ab8cda6bec7f965545@wordpress.org>
References: <054.685942439bfac8ab8cda6bec7f965545@wordpress.org>
Message-ID: <069.4fee96d21d3cdb1ed484dd5344592ef8@wordpress.org>

#54736: get_sample_permalink unsets $post->filter even though this is a public
property.
----------------------------------------+-----------------------------
 Reporter:  herregroen                  |       Owner:  hellofromTonya
     Type:  defect (bug)                |      Status:  assigned
 Priority:  normal                      |   Milestone:  6.0
Component:  Posts, Post Types           |     Version:  2.7.1
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+-----------------------------
Changes (by hellofromTonya):

 * owner:  (none) => hellofromTonya
 * status:  new => assigned


Comment:

 Assigning to me for review and unit tests.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54736#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 14:01:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 14:01:58 -0000
Subject: [wp-trac] [WordPress Trac] #52970: Improve text in help tabs of
 Personal Data Exporter/Eraser
In-Reply-To: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
References: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
Message-ID: <066.bf35c92a6288fd198b17ceb95712f6f9@wordpress.org>

#52970: Improve text in help tabs of Personal Data Exporter/Eraser
-------------------------------------------------+-------------------------
 Reporter:  dimadin                              |       Owner:  marybaum
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Help/About                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:  privacy,
  screenshots has-privacy-review                 |  ui-copy
-------------------------------------------------+-------------------------

Comment (by Boniu91):

 @dimadin Thank you for creating the ticket and prviding the patch. Could
 you post the exact steps that should be done in order to reproduce the
 issue and confirm the enhancements?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52970#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 14:22:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 14:22:14 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.f5941dab7b4104218f1ece2440b2b809@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+-----------------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Future Release
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  needs-patch    |     Focuses:
---------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * Attachment "55432.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 14:22:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 14:22:21 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.646b5d8780696cbec1e0b650187acacb@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+-----------------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Future Release
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  needs-patch    |     Focuses:
---------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * Attachment "55432.2.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 14:28:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 14:28:42 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.974cf673b3853252f5e84b04c9314edf@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------
Changes (by SergeyBiryukov):

 * keywords:  needs-patch => has-patch
 * milestone:  Future Release => 6.0


Comment:

 * [attachment:"55432.diff"] follows the precedent of [28644] and renames
 `$plugin` to `$_wp_plugin_file` to reduce the chance of a conflict.
 * [attachment:"55432.2.diff"] takes another approach more in line with
 [50787] and introduces a new function, `wp_load_plugin_file()`, to be used
 whenever we need to load a plugin file in core.

 I think [attachment:"55432.2.diff"] would be preferred here.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 14:34:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 14:34:28 -0000
Subject: [wp-trac] [WordPress Trac] #55437: Bugfix: Display correct
 theme in site editor
In-Reply-To: <054.2c8a29c0d20871f5ff204327eeee5dbc@wordpress.org>
References: <054.2c8a29c0d20871f5ff204327eeee5dbc@wordpress.org>
Message-ID: <069.13973dd81f190abcfdedf9ba6bb9095c@wordpress.org>

#55437: Bugfix: Display correct theme in site editor
-------------------------------------------------+-------------------------
 Reporter:  ptahdunbar                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing 2nd-opinion  |     Focuses:  ui,
                                                 |  administration
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * component:  Administration => Themes
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55437#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 14:35:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 14:35:37 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.85b4aaee61d8ea99affcda82d9e74ce1@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------

Comment (by joyously):

 Making a function to load a plugin would have drastic effects, because all
 the global variables would not be available. This is the same as themes,
 where certain global variables are imported to the function that loads
 templates.

 If you have to make a change here, I vote for renaming the variable.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 14:42:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 14:42:51 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.bc0deec1319d9c638720fd91ec8af6c4@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests assigned-   |     Focuses:  ui-copy
  for-commit                                     |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests assigned-
     for-commit


Comment:

 I refreshed the patch to replace the occurrences of "can not" with
 "cannot".

 Marking as `assigned-for-commit`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:50>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 14:44:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 14:44:53 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.9479bbc71077fdd5311547c348028d47@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
--------------------------------------+----------------------------
 Reporter:  flixos90                  |       Owner:  joedolson
     Type:  defect (bug)              |      Status:  accepted
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:  4.5
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  accessibility
--------------------------------------+----------------------------

Comment (by antonvlasenko):

 Steps to test this PR:
 1. Activate a non-block theme like `Twenty Twenty-One`.
 2. Go to the `Media Library`.
 3. Upload a new image to the media library.
 4. Set attachment properties like `Alternative Text`, `Title`, `Caption`,
 `Description`.
 5. Go to the `Appearance -> Customize` page.
 6. Go to the `Site Identity`, click on the `Select Logo`.
 7. Set a new cropped logo for the theme using the image you uploaded.
 8. Go to the `Media Library`.
 9. Open the last (cropped) image.
 10. Make sure that the original attachment properties (i.e. `Alternative
 Text`, `Title`, `Caption`, `Description`) have been copied over to the
 cropped image.
 11. Repeat steps 2-3.
 12. Reset all attachment properties (leave the fields empty).
 13. Repeat steps 5-9.
 14. Make sure that the `Title` field contains name of the cropped file.
 15. Make sure that the `Description` field contains url of the cropped
 file.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 14:54:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 14:54:59 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.fe18067da7c861fe5f1d191e80009182@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52977" 52977]:
 {{{
 #!CommitTicketReference repository="" revision="52977"
 Coding Standards: Use multi-line strings for the `$this->request` property
 in `wp-includes/class-wp-*-query.php`.

 This further improves the readability by replacing `implode()` calls with
 string interpolation.

 Follow-up to [52973].

 Props jrf.
 See #54728.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:50>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 15:03:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 15:03:49 -0000
Subject: [wp-trac] [WordPress Trac] #52970: Improve text in help tabs of
 Personal Data Exporter/Eraser
In-Reply-To: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
References: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
Message-ID: <066.012f7f801aff121627240feff0fb0a1b@wordpress.org>

#52970: Improve text in help tabs of Personal Data Exporter/Eraser
-------------------------------------------------+-------------------------
 Reporter:  dimadin                              |       Owner:  marybaum
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Help/About                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:  privacy,
  screenshots has-privacy-review                 |  ui-copy
-------------------------------------------------+-------------------------

Comment (by paapst):

 Hi @Boniu91, thank you for volunteering to test the patches on this
 ticket.

 The issue is that the help text about erasing data and the text about
 exporting data needs improvement. Both of the pull requests contain that
 improvement: https://github.com/WordPress/wordpress-develop/pull/2115  and
 https://github.com/WordPress/wordpress-develop/pull/2116

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52970#comment:50>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 15:10:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 15:10:41 -0000
Subject: [wp-trac] [WordPress Trac] #53589: Twenty Twenty One:
 Translation file loaded twice
In-Reply-To: <050.fd27a9de8a8ccfd9c34a5214c2ee833a@wordpress.org>
References: <050.fd27a9de8a8ccfd9c34a5214c2ee833a@wordpress.org>
Message-ID: <065.8c283cac40fd5e84bad66d4dc7ea4099@wordpress.org>

#53589: Twenty Twenty One: Translation file loaded twice
------------------------------------+--------------------------
 Reporter:  Chouby                  |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  6.0
Component:  Bundled Theme           |     Version:  5.6
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:  performance
------------------------------------+--------------------------

Comment (by zodiac1978):

 Hi @sabernhardt - could you explain to me why you milestoned this for 6.0.
 The bundled themes could be updated independently from core updates, or
 not? So why do we wait to fix it? There were several theme updates in the
 meantime. Any reason for this? Just curious. :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53589#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 15:15:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 15:15:17 -0000
Subject: [wp-trac] [WordPress Trac] #54188: Different theme screenshot
 sizes are displayed in the customizer preview
In-Reply-To: <049.1b0f361e8b6821157b6f7ccf636e2184@wordpress.org>
References: <049.1b0f361e8b6821157b6f7ccf636e2184@wordpress.org>
Message-ID: <064.3ee24dc1257903ec0691f8a9298a5c0e@wordpress.org>

#54188: Different theme screenshot sizes are displayed in the customizer preview
-------------------------------------------------+-------------------------
 Reporter:  poena                                |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Themes                               |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info                                   |
-------------------------------------------------+-------------------------

Comment (by poena):

 The theme is called c
 https://wordpress.org/themes/c/

 The linked meta ticket lists a few other themes with different screenshot
 sizes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54188#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 15:19:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 15:19:01 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "55432.diff" removed.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 15:19:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 15:19:01 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.d5ce86747c57a29b1d09e5e23e9b9b08@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "55432.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 15:38:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 15:38:16 -0000
Subject: [wp-trac] [WordPress Trac] #47513: JavaScript TypeError when
 Video Playlists use native video elements
In-Reply-To: <051.e1395a3430ffb65f830023f935afff26@wordpress.org>
References: <051.e1395a3430ffb65f830023f935afff26@wordpress.org>
Message-ID: <066.a2d3830f4d5e46cb4ff3a7b9681b5dd1@wordpress.org>

#47513: JavaScript TypeError when Video Playlists use native video elements
-----------------------------+------------------------------
 Reporter:  afercia          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Editor           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  javascript
-----------------------------+------------------------------
Changes (by afercia):

 * Attachment "47513.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47513>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 15:44:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 15:44:10 -0000
Subject: [wp-trac] [WordPress Trac] #47513: JavaScript TypeError when
 Video Playlists use native video elements
In-Reply-To: <051.e1395a3430ffb65f830023f935afff26@wordpress.org>
References: <051.e1395a3430ffb65f830023f935afff26@wordpress.org>
Message-ID: <066.4cf2eea628058fd2a79259f9cf9260d2@wordpress.org>

#47513: JavaScript TypeError when Video Playlists use native video elements
---------------------------------------+-------------------------
 Reporter:  afercia                    |       Owner:  afercia
     Type:  defect (bug)               |      Status:  assigned
 Priority:  normal                     |   Milestone:  6.0
Component:  Editor                     |     Version:
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:  javascript
---------------------------------------+-------------------------
Changes (by afercia):

 * keywords:  has-screenshots => has-screenshots has-patch
 * owner:  (none) => afercia
 * status:  new => assigned
 * milestone:  Awaiting Review => 6.0


Comment:

 I can still reproduce the JS TypeError, even now that MediaElementJS has
 been updated to version 4.2.16 in [49070].

 [attachment:"47513.diff"] introduces a simple check to avoid the error.

 To test:
 - repeat the steps in this ticket description
 - observe there are no errors in your browser's console
 - check the .ogv video plays

 Moving to 6.0 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47513#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 15:55:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 15:55:15 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.09ae92f744b1cfd0702b87944e326b15@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests assigned-   |     Focuses:  ui-copy
  for-commit commit                              |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests assigned-for-commit => has-patch has-
     unit-tests assigned-for-commit commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:51>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 16:23:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 16:23:47 -0000
Subject: [wp-trac] [WordPress Trac] #39176: Merge two similar "terms"
 strings in the REST API
In-Reply-To: <049.84dc22ac33ac743863834088046de721@wordpress.org>
References: <049.84dc22ac33ac743863834088046de721@wordpress.org>
Message-ID: <064.e97ddeb68a4ef6080a230e457b2b17cb@wordpress.org>

#39176: Merge two similar "terms" strings in the REST API
------------------------------+--------------------------
 Reporter:  ramiy             |       Owner:  rachelbaker
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:  4.8
Component:  Taxonomy          |     Version:
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:  rest-api
------------------------------+--------------------------

Comment (by audrasjb):

 In [changeset:"52978" 52978]:
 {{{
 #!CommitTicketReference repository="" revision="52978"
 Administration: Replace contracted verb forms for better consistency.

 This changeset replaces contracted verb forms like `doesn't`, `can't`, or
 `isn't` with non-contracted forms like `does not`, `cannot`, or `is not`,
 for better consistency across the WordPress administration. It also
 updates some corresponding unit tests strings.

 Props Presskopp, socalchristina, aandrewdixon, francina, SergeyBiryukov,
 JeffPaul, audrasjb, hellofromTonya.
 Fixes #38913.
 See #39176.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39176#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 16:23:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 16:23:48 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.bf13abe730daffa8e8378056c947caa0@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests assigned-   |     Focuses:  ui-copy
  for-commit commit                              |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52978" 52978]:
 {{{
 #!CommitTicketReference repository="" revision="52978"
 Administration: Replace contracted verb forms for better consistency.

 This changeset replaces contracted verb forms like `doesn't`, `can't`, or
 `isn't` with non-contracted forms like `does not`, `cannot`, or `is not`,
 for better consistency across the WordPress administration. It also
 updates some corresponding unit tests strings.

 Props Presskopp, socalchristina, aandrewdixon, francina, SergeyBiryukov,
 JeffPaul, audrasjb, hellofromTonya.
 Fixes #38913.
 See #39176.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 16:29:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 16:29:20 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.600fc7a42b94dc78608ab925798dadc4@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests assigned-   |     Focuses:  ui-copy
  for-commit                                     |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests assigned-for-commit commit => has-
     patch has-unit-tests assigned-for-commit
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Looks like this initial patch doesn’t (hmm… or even better: does not)
 handle a few occurrences. I'm preparing a follow-up patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 16:33:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 16:33:15 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.d789e14ec2222577a9e40587b392fe92@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests assigned-   |     Focuses:  ui-copy
  for-commit                                     |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 New PR: https://github.com/WordPress/wordpress-develop/pull/2447

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:54>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 17:08:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 17:08:59 -0000
Subject: [wp-trac] [WordPress Trac] #36723: Add caching to
 wp_old_slug_redirect
In-Reply-To: <056.7ffbc2e33d1a1f5775af17a89b38afc3@wordpress.org>
References: <056.7ffbc2e33d1a1f5775af17a89b38afc3@wordpress.org>
Message-ID: <071.f7564cda1c56f7ccf197fd923ee047b2@wordpress.org>

#36723: Add caching to wp_old_slug_redirect
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:
Component:  Posts, Post Types                    |     Version:  2.1
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback has-unit-     |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 Refreshed my patch as a PR [https://github.com/WordPress/wordpress-
 develop/pull/2448 #2448].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36723#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 17:11:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 17:11:49 -0000
Subject: [wp-trac] [WordPress Trac] #36723: Add caching to
 wp_old_slug_redirect
In-Reply-To: <056.7ffbc2e33d1a1f5775af17a89b38afc3@wordpress.org>
References: <056.7ffbc2e33d1a1f5775af17a89b38afc3@wordpress.org>
Message-ID: <071.365f91f7d8085809783b93e218587dbe@wordpress.org>

#36723: Add caching to wp_old_slug_redirect
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Posts, Post Types                    |     Version:  2.1
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback has-unit-     |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * milestone:   => Future Release


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36723#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 17:28:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 17:28:45 -0000
Subject: [wp-trac] [WordPress Trac] #36710: Symlinked directories should
 not be deleted recursively
In-Reply-To: <048.ef6e38ed06a006607f1b9410360ae699@wordpress.org>
References: <048.ef6e38ed06a006607f1b9410360ae699@wordpress.org>
Message-ID: <063.9ecd326f206dfcf92e8948045b168de0@wordpress.org>

#36710: Symlinked directories should not be deleted recursively
-------------------------------------------------+-------------------------
 Reporter:  andy                                 |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Filesystem API                       |     Version:
 Severity:  major                                |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:
  testing-info                                   |  administration
-------------------------------------------------+-------------------------

Comment (by Dreamsorcerer):

 It's been several years since I looked at this, but test instructions
 should be fairly easy, something along the lines of:

 Download a plugin outside of the WP directory.
 Symlink that plugin into the plugins directory (`ln -s /path/to/plugin
 /path/to/wp-content/plugins/`).
 Observe that the plugin is installed and working correctly on the website.
 Delete (and probably try upgrading on a second test) the plugin through
 the website admin.
 Observe that no errors occurred and the plugin is no longer on the
 website.
 Observe that the original plugin (outside WP directory) is still present
 with no files deleted (symlinking again should result in the plugin being
 installed and working again).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36710#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 17:30:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 17:30:05 -0000
Subject: [wp-trac] [WordPress Trac] #40613: Add query cache to
 WP_User_Query class
In-Reply-To: <059.e61f80535b2a78c2a40357612ead1152@wordpress.org>
References: <059.e61f80535b2a78c2a40357612ead1152@wordpress.org>
Message-ID: <074.faf0255f715d19193d205a044d66c46b@wordpress.org>

#40613: Add query cache to WP_User_Query class
-------------------------------------+------------------------------
 Reporter:  johnjamesjacoby          |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Users                    |     Version:  3.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  performance
-------------------------------------+------------------------------

Comment (by OllieJones):

 A similar issue crops up in the Gutenberg editor's REST request to
 populate the author dropdown.

 The REST request looks like this

 https://giantsite.example.com/wp-
 json/wp/v2/users?context=view&who=authors&per_page=50&_fields=id,name&_locale=user

 Enhancing its performance requires judicious filtering at the
 `'rest_user_query'` hook.

 (Just like handling the Posts and Pages panels requires judicious
 filtering on `'wp_dropdown_users_args'`.)

 Why are these slow? They need to examine each user's `wp_capabilities`
 metadata, which holds a serialized php object. It's expensive for MariaDB
 / MySQL to filter on this sort of predicate.

     WHERE ... meta_key = 'wp_capabilities' AND meta_value LIKE
 '%"author"%'

 for two reasons. One is the notorious `LIKE '%something'` dbms performance
 killer. The other is the fact that `meta_value` columns are CLOBs, which
 take extra work for the dbms to retrieve. And retrieve them it must, one
 for every user. In a megauser installation, that is *very* slow. It also
 hammers the dbms internal cache, potentially slowing down everything else.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40613#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 17:37:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 17:37:39 -0000
Subject: [wp-trac] [WordPress Trac] #53589: Twenty Twenty One:
 Translation file loaded twice
In-Reply-To: <050.fd27a9de8a8ccfd9c34a5214c2ee833a@wordpress.org>
References: <050.fd27a9de8a8ccfd9c34a5214c2ee833a@wordpress.org>
Message-ID: <065.2916ab9c1c934e6a440c5de20162b55f@wordpress.org>

#53589: Twenty Twenty One: Translation file loaded twice
------------------------------------+--------------------------
 Reporter:  Chouby                  |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  6.0
Component:  Bundled Theme           |     Version:  5.6
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:  performance
------------------------------------+--------------------------

Comment (by sabernhardt):

 Even when bundled themes are updated separately from the WordPress
 versions, the ticket has a milestone according to the WP (minor) version
 number. I did not find an obvious reason to rush this change before the
 major release, but if it's ready sooner, committers can move the milestone
 earlier.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53589#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 17:41:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 17:41:10 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.a9fe29edc434f4815f5e766a54a061c8@wordpress.org>

#55439: Introduce term_exists_args filter
-------------------------------------+---------------------------
 Reporter:  Chouby                   |       Owner:  spacedmonkey
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+---------------------------

Comment (by spacedmonkey):

 @audrasjb Feedback fixed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 17:47:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 17:47:45 -0000
Subject: [wp-trac] [WordPress Trac] #55196: Twenty Twenty-Two - Search
 Magnifying SVG icon
In-Reply-To: <050.906544f38ac4c2f87c212c7e1f45cbe1@wordpress.org>
References: <050.906544f38ac4c2f87c212c7e1f45cbe1@wordpress.org>
Message-ID: <065.08cfa257a00ddf565d5ad5a8cc71a8ea@wordpress.org>

#55196: Twenty Twenty-Two - Search Magnifying SVG icon
--------------------------+--------------------------------
 Reporter:  utz119        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  reported-upstream
 Keywords:                |     Focuses:  accessibility
--------------------------+--------------------------------

Comment (by mecurran):

 When is this scheduled to be added to the wordpress core search block?  I
 am running WordPress v5.9.2 and the aria label only appears if Gutenberg
 is installed and active.  I am running a custom theme, not Twenty Twenty
 Two.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55196#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 17:52:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 17:52:35 -0000
Subject: [wp-trac] [WordPress Trac] #36723: Add caching to
 wp_old_slug_redirect
In-Reply-To: <056.7ffbc2e33d1a1f5775af17a89b38afc3@wordpress.org>
References: <056.7ffbc2e33d1a1f5775af17a89b38afc3@wordpress.org>
Message-ID: <071.172272b8209189568b2f71218a4d2c60@wordpress.org>

#36723: Add caching to wp_old_slug_redirect
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Posts, Post Types                    |     Version:  2.1
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback has-unit-     |     Focuses:
  tests                                          |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * owner:  (none) => spacedmonkey
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36723#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 17:54:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 17:54:01 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.03f2e3ac4301b4cc3ce0e3b22cfb4865@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests assigned-   |     Focuses:  ui-copy
  for-commit                                     |
-------------------------------------------------+-------------------------

Comment (by SergeyBiryukov):

 Thanks for the commit! Trac does not show the diff for [52978] here due to
 a large number of changes, but I have reviewed it on GitHub and most of
 the changes look good to me :)

 I think these two strings could use some further improvement, they seem a
 bit weird as is:

 * "If for some reason this does not work, do not worry. It does not work
 on all web hosts."
  * Suggested: "If for some reason this does not work, do not worry. **It
 may not work** on all web hosts."
 * "There are not any events scheduled near %1$s at the moment."
  * Suggested: "**There are no events** scheduled near %1$s at the moment."

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:56>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 19:11:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 19:11:45 -0000
Subject: [wp-trac] [WordPress Trac] #55430: Installation keeps on
 clobbering cshayward.com domain name with cjshayward.com
In-Reply-To: <054.746f00f9711b82c2b9a96e4206c399b3@wordpress.org>
References: <054.746f00f9711b82c2b9a96e4206c399b3@wordpress.org>
Message-ID: <069.14e10ea53953f39443bf4a4ae5bab1c7@wordpress.org>

#55430: Installation keeps on clobbering cshayward.com domain name with
cjshayward.com
--------------------------+-----------------------------
 Reporter:  CJSHayward    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Database      |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  administration
--------------------------+-----------------------------

Comment (by CJSHayward):

 **--ADDITIONAL UPDATE--**

 I had an advanced-cache.php from a copied plugin.

 I have moved out all plugins except for classic editor and widgets. I do
 not detect any change in behavior.

 **--FURTHER ADDITIONAL UPDATE--**

 I've tried tearing down and rebuilding the site, and have gotten apparent
 success for the time, but the behavior reappears.

 I've added the classic editor for posts and widgets to wp-content/plugins,
 and twentysixteen and twentysixteen-ux-tweaks-child (the latter is the
 active theme at https://cjshayward.com) to wp-content/themes, and nothing
 else. Earlier I had a caching plugin that could have accounted to observed
 changes, but that has never been at the current build. Adding the
 definitions advocated at https://stackoverflow.com/questions/19471263
 /wordpress-site-address-is-to-a-different-site has not changed behavior
 with the current site.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55430#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 19:57:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 19:57:35 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.c34ddfbf564a0fa5a312e1a3603f00f0@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests assigned-   |     Focuses:  ui-copy
  for-commit                                     |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 In [changeset:"52979" 52979]:
 {{{
 #!CommitTicketReference repository="" revision="52979"
 Administration: Replace contracted verb forms for better consistency.

 This changeset replaces contracted verb forms like `doesn't`, `can't`, or
 `isn't` with non-contracted forms like `does not`, `cannot`, or `is not`,
 for better consistency across the WordPress administration. It also
 updates some corresponding unit tests strings.

 Follow-up to [52978].

 See #38913.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:57>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 20:17:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 20:17:33 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.3c478d51a8a08b0c2b8b9e5e0508d84c@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
--------------------------------------+-----------------------
 Reporter:  Presskopp                 |       Owner:  audrasjb
     Type:  enhancement               |      Status:  reopened
 Priority:  normal                    |   Milestone:  6.0
Component:  Administration            |     Version:  4.7
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  ui-copy
--------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests assigned-for-commit => has-patch has-
     unit-tests


Comment:

 Ah thank you for the post-commit review @SergeyBiryukov.
 The above PR addresses those issues :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:59>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 20:18:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 20:18:28 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.904284715ecd416b2a446d5e1830c84b@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
---------------------------------------------+-----------------------
 Reporter:  Presskopp                        |       Owner:  audrasjb
     Type:  enhancement                      |      Status:  reopened
 Priority:  normal                           |   Milestone:  6.0
Component:  Administration                   |     Version:  4.7
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  ui-copy
---------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests commit


Comment:

 Committing the changes right now, and closing this ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:60>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 20:18:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 20:18:49 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.a4e60bdd3c943775253e767c42f1c467@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests commit      |     Focuses:  ui-copy
  assigned-for-commit                            |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch has-unit-tests commit => has-patch has-unit-tests
     commit assigned-for-commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:61>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 20:47:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 20:47:07 -0000
Subject: [wp-trac] [WordPress Trac] #55441: In wp_insert_term,
 pass $args as an additional parameter to after-insert actions
 (create_term, created_term, et al)
Message-ID: <051.80966e4799316bbd47b607a57d393a55@wordpress.org>

#55441: In wp_insert_term, pass $args as an additional parameter to after-insert
actions (create_term, created_term, et al)
-------------------------+-----------------------------
 Reporter:  mboynes      |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Taxonomy     |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 @johnbillion [https://github.com/alleyinteractive/wordpress-
 fieldmanager/issues/831 reported an issue to Fieldmanager] where it would
 save term meta to additional terms if any were added or updated as a side
 effect of adding/updating a term in the WordPress admin. Guarding against
 this when editing a term is simple since there's a term ID to check
 against, but I've had to [https://github.com/alleyinteractive/wordpress-
 fieldmanager/pull/832/files#diff-
 683aac44c2d38dd2ea1f9084f864fafb04cd37323f494a39602be25db008bc38 jump
 through a few hoops to guard against this when creating new terms].
 Through this process I've come to realize that there's an opportunity for
 improvement to core. As it currently stands, when
 [https://github.com/WordPress/WordPress/blob/6f39380c34c5665e4b78e0733d25c39043d7ac94
 /wp-includes/taxonomy.php#L2577-L2685 all of the actions fire in
 wp_insert_term() after the term is inserted], there's no way to guarantee
 that the action firing relates to a specific call of `wp_insert_term()`.
 If the actions included the `$args` array passed to that function, then a
 developer could use that information to target a specific call to
 `wp_insert_term()`, especially when core calls it to insert a term from
 the canonical form in the WordPress admin (since it passes `$_POST`
 wholesale as the `$args` argument).

 This would entail adding the argument to the following actions:

 * `create_term`
 * `create_{$taxonomy}`
 * `created_term`
 * `created_{$taxonomy}`
 * `saved_term`
 * `saved_{$taxonomy}`

 If there's appetite for this update, I'm happy to submit a patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55441>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 20:49:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 20:49:12 -0000
Subject: [wp-trac] [WordPress Trac] #55436: Image Galleries are NOT
 displayed properly on SAFARI
In-Reply-To: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
References: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
Message-ID: <067.20a2c5e54eeeed460f9dcd4e581539ab@wordpress.org>

#55436: Image Galleries are NOT displayed properly on SAFARI
-------------------------------+------------------------------
 Reporter:  learnamo           |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Editor             |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by learnamo):

 You guys were right!

 I turned lazy loading off and everything was just fine! I have already
 contacted Jetpack to signal this bug.

 Thank you guys for your help! You are amazing!

 Replying to [comment:4 costdev]:
 > @vijayhardaha, thanks for investigating this issue!
 >
 > Hi @learnamo, welcome to Trac!
 >
 > Please try disabling the Jetpack lazy load option as @vijayhardaha
 suggested and let us know if the gallery displays as expected.
 >
 > If the issue still occurs, please
 [https://github.com/WordPress/gutenberg/issues/new?assignees=&labels=&template=Bug_report.yml
 open a new issue] on the Gutenberg repository and comment here with a link
 to the issue.
 >
 > -----
 >
 > - Adding the `reporter-feedback` keyword as this issue currently
 requires a response from @learnamo.
 >
 > - The `Version` parameter is used to indicate which version of WordPress
 Core introduced an issue. As this isn't verified as a WordPress Core
 issue, I'll reset the `Version`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55436#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 20:57:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 20:57:03 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.1866f5a3bc6dad7b7c59d2fc8cc50504@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests commit      |     Focuses:  ui-copy
  assigned-for-commit                            |
-------------------------------------------------+-------------------------

Comment (by JeffPaul):

 Apologies, some personal issues have slowed me lately and didn't get
 around to that updated commit in the PR, thanks for picking that up
 @audrasjb!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:62>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 21:00:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 21:00:47 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.fbda72b598893a3215544f74dfb8401e@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests commit      |     Focuses:  ui-copy
  assigned-for-commit                            |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 No worries @JeffPaul! Thank you!

 Unit tests are passing on PR2449.
 Let's commit it and close the ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:63>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 21:05:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 21:05:46 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.448a3e5d714881d564aeed77813c3918@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit      |     Focuses:  ui-copy
  assigned-for-commit                            |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52980" 52980]:
 {{{
 #!CommitTicketReference repository="" revision="52980"
 Administration: Rephrase some sentences after [52978].

 Follow-up to [52978], [52979].

 Props SergeyBiryukov.
 Fixes #38913.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:64>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 21:10:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 21:10:12 -0000
Subject: [wp-trac] [WordPress Trac] #38913: Aggregation of contracted
 and not contracted verb forms (cannot, doesn't)?
In-Reply-To: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
References: <053.6e82a07ce47cc4d1b857275a22c4d5e2@wordpress.org>
Message-ID: <068.da43945b2128dea3141b88ac5876b63e@wordpress.org>

#38913: Aggregation of contracted and not contracted verb forms (cannot, doesn't)?
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.7
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit      |     Focuses:  ui-copy
  assigned-for-commit                            |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 In [changeset:"52981" 52981]:
 {{{
 #!CommitTicketReference repository="" revision="52981"
 Administration: Remove a duplicate sentence after [52980].

 Follow-up to [52980], [52979], [52978].

 Props SergeyBiryukov.
 Fixes #38913.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38913#comment:65>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 21:40:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 21:40:15 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.9a86d74e34129e38154fd825b5b6e88a@wordpress.org>

#36949: Term exists should use get_terms internally
----------------------------+---------------------------
 Reporter:  spacedmonkey    |       Owner:  spacedmonkey
     Type:  enhancement     |      Status:  closed
 Priority:  normal          |   Milestone:  6.0
Component:  Taxonomy        |     Version:  2.3
 Severity:  normal          |  Resolution:  fixed
 Keywords:  needs-dev-note  |     Focuses:  performance
----------------------------+---------------------------
Changes (by peterwilsoncc):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 Replying to [comment:39 Chouby]:
 > @peterwilsoncc @spacedmonkey I opened #55439

 Thank you, I really appreciate it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36949#comment:40>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 21:59:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 21:59:34 -0000
Subject: [wp-trac] [WordPress Trac] #55442: count(): Parameter must be an
 array or an object that implements Countable in
 /var/www/html/wp-includes/post-template.php on line 319
Message-ID: <053.e311b440ab3eabcc6680846a6bbaea8c@wordpress.org>

#55442: count(): Parameter must be an array or an object that implements Countable
in /var/www/html/wp-includes/post-template.php on line 319
--------------------------+-----------------------------
 Reporter:  davidscpl     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Call get_the_content() with no arguments and $post is null. If post is
 null then this is ran:
 {{{#!php
  $elements = compact( 'page', 'more', 'preview', 'pages', 'multipage' );
 }}}

 Associate array has keys with null values. Then on lin3 319 is
 {{{#!php
 if ( $elements['page'] > count( $elements['pages'] ) ) {
 }}}

 Which causes this notice:

 {{{
 Warning: count(): Parameter must be an array or an object that implements
 Countable in /var/www/html/wp-includes/post-template.php on line 319
 Notice: Trying to access array offset on value of type null in
 /var/www/html/wp-includes/post-template.php on line 325
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55442>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 22:40:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 22:40:48 -0000
Subject: [wp-trac] [WordPress Trac] #55442: count(): Parameter must be
 an array or an object that implements Countable in
 /var/www/html/wp-includes/post-template.php on line 319
In-Reply-To: <053.e311b440ab3eabcc6680846a6bbaea8c@wordpress.org>
References: <053.e311b440ab3eabcc6680846a6bbaea8c@wordpress.org>
Message-ID: <068.60ed020a007ca1d9e6ac5fee46a63cd0@wordpress.org>

#55442: count(): Parameter must be an array or an object that implements Countable
in /var/www/html/wp-includes/post-template.php on line 319
--------------------------+------------------------------
 Reporter:  davidscpl     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by audrasjb):

 Hello and welcome to WordPress Trac @davidscpl,

 I tried to reproduce the issue using the following steps, but it didn't
 succeed.

 - Using a fresh WordPress 5.9.2 installation
 - Enable WP_DEBUG/WP_DEBUG_DISPLAY constants
 - In one of the Bundled Themes, open the 404.php template and add the
 following code:

 {{{
 global $post;
 var_export( $post );
 echo get_the_content();
 }}}

 It echoes `NULL` (line 2). **No PHP warning.**

 Could you please provide more details on how we can reproduce the issue?

 Thanks!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55442#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 22:40:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 22:40:58 -0000
Subject: [wp-trac] [WordPress Trac] #55442: count(): Parameter must be
 an array or an object that implements Countable in
 /var/www/html/wp-includes/post-template.php on line 319
In-Reply-To: <053.e311b440ab3eabcc6680846a6bbaea8c@wordpress.org>
References: <053.e311b440ab3eabcc6680846a6bbaea8c@wordpress.org>
Message-ID: <068.dc310a3d2d924f7e3e069627c529a3a8@wordpress.org>

#55442: count(): Parameter must be an array or an object that implements Countable
in /var/www/html/wp-includes/post-template.php on line 319
-------------------------------+------------------------------
 Reporter:  davidscpl          |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  General            |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by audrasjb):

 * keywords:   => reporter-feedback


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55442#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 22:43:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 22:43:25 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.c90f88a49426ed62177b51f83da4648a@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-22 at 22.42.06.png" added.

 Before - Object cache

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 22:43:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 22:43:56 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.a0fcf7b109ff6c9578ac9a4b2b50a5e5@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-22 at 22.40.35.png" added.

 Before post query

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 22:44:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 22:44:15 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.475fce6acf1708c609eba0dfdb212666@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-22 at 22.41.10.png" added.

 After - Single query

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 22:45:06 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 22:45:06 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.e6e20fdf851e0b595c9a02dd8fb83ce2@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-22 at 22.38.49.png" added.

 Before - page performance

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 22:45:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 22:45:32 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.464aa2cef51ac148cc3e096a26d14512@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-22 at 22.37.55.png" added.

 After - page performance

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 22:50:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 22:50:45 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.8f2bb6baa906e7b375e00380affe4a6e@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 After some more testing with a menu with 200 items in it, I found some
 interesting results.

 Currently, there is one query to get all the object ids and another to get
 post objects ( menu items ). In my test, with a menu with 200 items, this
 resulted to two queries returning 200 rows. The post query, results in an
 extremely long query with 200 ids in an IN state in the query.

 Replacing with a taxonomy query, means one single request. I will admit,
 this query is a little slower that the original WP_Query. But as you are
 replace two queries with one, it there is still a net performance win. Not
 to mention less stress on the database, not returning 200 rows in two
 queries.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 23:15:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 23:15:33 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and use
 for output
Message-ID: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  adamsilverstein
  adamsilverstein        |
     Type:  enhancement  |     Status:  assigned
 Priority:  normal       |  Milestone:  6.0
Component:  Media        |    Version:  trunk
 Severity:  normal       |   Keywords:  has-patch has-unit-tests needs-
  Focuses:  performance  |  testing needs-dev-note
-------------------------+-------------------------------------------------
 === Summary
 This ticket introduces core support for generating and using additional
 mime types for sub-sized image uploads, with a focus on the WebP format.
 In addition, it filters frontend content to use the modern format when
 available for an image. After this change, WordPress will generate and use
 WebP sub sizes by default when available.

 Currently, when users upload images in a supported mime type like JPEG or
 WebP, WordPress creates sub-sized images of the same type for use on the
 front end (WordPress does not currently create sub-sized images for TIFF,
 GIF or PNG images). In WordPress 5.8 we introduced the
 `image_editor_output_format` filter to enable filtering the mime type used
 to save images.

 This ticket introduces the capability to generate more than a single mime
 type. For example, when users upload JPEG images, WordPress can
 automatically generate both WebP and JPEG sub-sized images. Then WordPress
 can use the WebP images when serving up the front end. JPEG images are
 still being generated by default, to support other use-cases outside of
 common web browsers (e.g. email newsletters) where WebP may not be
 supported yet.

 The above is only the default though - the behavior of which image formats
 are generated and used can be customized via filters.

 === New Filters

 This patch introduces two new filters, one to control the mime types
 WordPress generates when you upload an image and one to control which
 image mime type is used for displaying images on the front end of the
 website.

 ==== Mime type image generation filter

 This patch adds a new filter named `wp_upload_image_mime_transforms` (and
 similarly named function) that maps the upload image mime type to an array
 of one or more output mime types:

 By default, the mapping is:
 {{{
         array(
                 'image/jpeg'        => array( 'image/jpeg', 'image/webp'
 ),
                 'image/webp'      => array( 'image/webp', 'image/jpeg' ),
         );

 }}}
 The attachment id is also passed to the filter for context.

 ==== Mime type front end output filter

 This patch adds a new filter `wp_content_image_mimes` for the front end
 that specifies the preferred format(s) to use for content output (as long
 as the image file is available). When outputting images in the content,
 the first mime type available will be used. The attachment id and context
 are also passed to the filter.

 === WebP as a default output format for images
 On the front end, sites will benefit from using WebP in place of JPEG for
 their images. Research on
 https://github.com/WordPress/performance/issues/7 indicates images will
 average around a 30% overall file size reduction. This work also includes
 verifying the visual image quality of the output using
 [https://github.com/kornelski/dssim dssim].

 === Developers Note
 The function `make_subsize`      in both of core’s bundled WP_Image_Editor
 implementations (WP_Image_Editor_Imagick and WP_Image_Editor_GD) has been
 updated to accept a `$mime_type` parameter which in turn passed the mime
 type to the `_save` function (which already supports a `$mime_type`
 parameter). If your code implements `​​WP_Image_Editor::make_subsize()`
 make sure you update your function to support the `$mime_type` parameter.
 Plugins that modify image use (CDN, S3) or already create alternate mime
 types should test integrating with the code on this ticket and consider
 supporting the new sources meta data.


 === How to Test
 Test with this patch or the Performance Lab [https://wordpress.org/plugins
 /performance-lab/ plugin]
 Create a post and upload a jpeg image, placing in the post
 Publish the post and view it’s source code, the image URLs should be
 “.webp” images

 === Technical Details
 * In src/wp-admin/includes/image.php::wp_create_image_subsizes:
 loop through all of the mime types returned from the
 `​​wp_upload_image_mime_transforms` filter, generating sub-sized images
 for every mime format supported by the system.  Default when a type isn’t
 mapped in the array  is outputting in the mime type of the uploaded image.
 The first type is the “primary” mime type and is stored exactly like
 current WordPress uploads (no change)
 “Full” sized images are created for each mime type supported by the system
 with a `-{mime extension}` appended to the file name
 When images over `big_image_size_threshold` are uploaded, the primary
 image gets a `-scaled` suffix (unchanged), alternate types get a `-{mime
 extension}-scaled` suffix
 Similarly, alternate mime rotated images get a  `-{mime
 extension}-rotated` suffix
 New image meta `sources` array stores each mime type created for each full
 sized image and for each sub-sized image - both the file name (`file`) and
 size (`filesize`) are stored.
 In src/wp-admin/includes/image.php::_wp_make_subsizes:
 Using a mapping (from the input file mime type) provided by
 `wp_upload_image_mime_transforms`, output sub sized images in one or more
 output mime types

 * In src/wp-admin/includes/image.php
 Add a new function `wp_upload_image_mime_transforms` as well as a matching
 filter named `wp_upload_image_mime_transforms` . Returns an array with the
 list of valid mime types that a specific mime type should be converted
 into.
 In src/wp-includes/class-wp-image-editor-gd.php and src/wp-includes/class-
 wp-image-editor-imagick.php:
 Update `make_subsize` to accept a new `mime_type` parameter that gets
 passed to the `_save` function when set (which already has a mime_type
 parameter). Add the new parameter to internal function calls as well.

 * In src/wp-includes/media.php: Adds  new function
 `wp_image_use_alternate_mime_types` that is called for every image in
 `wp_filter_content_tags`. This function:
 Adds a new filter `wp_content_image_mimes` that returns the mime type(s)
 to try to use for output, in the order they should be tried. The default
 order to try is array( 'image/webp', 'image/jpeg' ), meaning if a WebP
 version of the image exists, WordPress will use that image for the image
 tag output
 Replaces all image components (including urls in the `src` and `srcset`
 attributes) when the same image is available in the preferred mime type
 Returning an empty array will skip any image mime type substitution ( ie.
 `add_filter( ‘wp_content_image_mimes’, ‘__return_empty_array’ );`

 * In src/wp-includes/post.php::wp_delete_attachment_files:
 Delete additional mime type images referenced in the image meta root
 ‘sources’ array as well as each sizes->sources array when present. This
 ensures that additional mime images are cleaned up if the original image
 is deleted.

 * In src/js/_enqueues/vendor/plupload/wp-plupload.js and
 src/js/_enqueues/vendor/plupload/handlers.js retry count is raised from 4
 to 8. Should this be filterable? Note: needs to be changed in Gutenberg as
 well, see
 https://github.com/WordPress/gutenberg/blob/23f11a18726bf69717595451ab3250cb67b426f6/packages
 /api-fetch/src/middlewares/media-upload.js#L38

 === PHPUnit test changes
 New sources data added to expected results in `
 test_wp_generate_attachment_metadata_pdf`, `test_crop_setting_for_pdf`
 Remove new `wp_content_image_mimes` filter for tests in
 tests/phpunit/tests/media.php

 === Todo items remain for this patch:
 - Add tests for new filters `wp_content_image_mimes` and
 `wp_upload_image_mime_transforms`
 - Add full sized alternate mime creation for PDF upload special handling,
 see https://github.com/WordPress/wordpress-
 develop/pull/2393/files#r832651580
 - Add REST support from https://github.com/WordPress/performance/pull/224
 (or in follow up ticket)
 - Improve naming of rotated/cropped alternate mime images

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 23:16:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 23:16:08 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.494cf5e5d50eacd66e7aec1b6e67132a@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note                         |  performance
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * Attachment "55443.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 23:22:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 23:22:51 -0000
Subject: [wp-trac] [WordPress Trac] #55442: count(): Parameter must be
 an array or an object that implements Countable in
 /var/www/html/wp-includes/post-template.php on line 319
In-Reply-To: <053.e311b440ab3eabcc6680846a6bbaea8c@wordpress.org>
References: <053.e311b440ab3eabcc6680846a6bbaea8c@wordpress.org>
Message-ID: <068.1e978a65a4d28f52f3fecaeec668ec6e@wordpress.org>

#55442: count(): Parameter must be an array or an object that implements Countable
in /var/www/html/wp-includes/post-template.php on line 319
-------------------------------+------------------------------
 Reporter:  davidscpl          |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  General            |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  template
-------------------------------+------------------------------
Changes (by davidbaumwald):

 * focuses:   => template


Comment:

 Related: #42814, #47824.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55442#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 23:41:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 23:41:58 -0000
Subject: [wp-trac] [WordPress Trac] #55442: count(): Parameter must be
 an array or an object that implements Countable in
 /var/www/html/wp-includes/post-template.php on line 319
In-Reply-To: <053.e311b440ab3eabcc6680846a6bbaea8c@wordpress.org>
References: <053.e311b440ab3eabcc6680846a6bbaea8c@wordpress.org>
Message-ID: <068.13fc8164dbed51da9477e48f7f0fe576@wordpress.org>

#55442: count(): Parameter must be an array or an object that implements Countable
in /var/www/html/wp-includes/post-template.php on line 319
-------------------------------+------------------------------
 Reporter:  davidscpl          |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  template
-------------------------------+------------------------------
Changes (by SergeyBiryukov):

 * component:  General => Posts, Post Types


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55442#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 23:48:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 23:48:57 -0000
Subject: [wp-trac] [WordPress Trac] #55444: Sticky posts are limited to 5
Message-ID: <056.93fd87dc2b3d2cbc54d6372c12a75b30@wordpress.org>

#55444: Sticky posts are limited to 5
-------------------------------+-----------------------------
 Reporter:  spacedmonkey       |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Posts, Post Types  |    Version:
 Severity:  normal             |   Keywords:
  Focuses:                     |
-------------------------------+-----------------------------
 The call to get sticky posts in WP_Query uses `get_posts`. As no limit is
 sent, the default limit to 5 posts. This means, that is the site has 15
 sticky posts, only 5 sticky posts will ever be shown on the front end.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55444>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 22 23:58:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 22 Mar 2022 23:58:52 -0000
Subject: [wp-trac] [WordPress Trac] #55444: Sticky posts are limited to 5
In-Reply-To: <056.93fd87dc2b3d2cbc54d6372c12a75b30@wordpress.org>
References: <056.93fd87dc2b3d2cbc54d6372c12a75b30@wordpress.org>
Message-ID: <071.e176b2f8a49b236f271d6f44c110469c@wordpress.org>

#55444: Sticky posts are limited to 5
----------------------------------------+------------------------------
 Reporter:  spacedmonkey                |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Posts, Post Types           |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:
----------------------------------------+------------------------------
Changes (by spacedmonkey):

 * keywords:   => needs-patch good-first-bug


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55444#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 00:28:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 00:28:50 -0000
Subject: [wp-trac] [WordPress Trac] #54035: Update Jcrop to the latest
 version
In-Reply-To: <058.77f0721436c76442699c4ef03e0313ad@wordpress.org>
References: <058.77f0721436c76442699c4ef03e0313ad@wordpress.org>
Message-ID: <073.28588a6875216b48d383c5a65676af4d@wordpress.org>

#54035: Update Jcrop to the latest version
-------------------------------------------------+-------------------------
 Reporter:  Hareesh Pillai                       |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  External Libraries                   |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch commit      |     Focuses:
  assigned-for-commit                            |
-------------------------------------------------+-------------------------
Changes (by davidbaumwald):

 * keywords:  good-first-bug has-patch => good-first-bug has-patch commit
     assigned-for-commit


Comment:

 After conferring with @SergeyBiryukov about this, this seems to have been
 replaced with
 `imgAreaSelect`([https://core.trac.wordpress.org/changeset/14907 r14907])
 and is no longer used by Core.

 Sergey's recommendation:
 >I think adding a comment might be a good idea, similar to the one added
 for Cropper in https://core.trac.wordpress.org/changeset/11742:
 >{{{ // Not used in core, replaced by imgAreaSelect. }}}

 >I think it's safe to update to 0.9.15 if there are no major changes.
 >It was updated to 0.9.12 while being already unused:
 https://core.trac.wordpress.org/changeset/25549

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54035#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 00:29:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 00:29:53 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.8d744d9642a2d789c4beae5631841373@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------
Changes (by ironprogrammer):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests has-
     screenshots


Comment:

 Thank you for the patch, @antonvlasenko!

 == Test Report

 For [https://github.com/WordPress/wordpress-develop/pull/2441 PR 2441].
 Sincere apologies for stomach grumbles caused by these test images 😋

 === Env
 * WordPress 6.0-alpha-52448-src
 * Chrome 99.0.4844.74
 * macOS 12.3 (Monterey)
 * Theme: Twenty Twenty-One
 * Gutenberg DISABLED 🔴

 === Steps to Test
 1. Activate a non-block theme like **Twenty Twenty-One**.
 2. Navigate to ''Media > Library''.
 3. Upload a new image to the media library, at least 512x512 pixels in
 size.
 4. Set attachment properties for ''Alternative Text'', ''Title'',
 ''Caption'', and ''Description''.
 5. Go to the ''Appearance > Customize''.
 6. Select **Site Identity**, and under the **Logo** section, click "Select
 Logo".
 7. Select the image just uploaded.
 8. Click the "Select" button to open the crop tool.
 9. Select the region to crop, and click the "Crop image" button.
 10. Click "Publish"* and close the Customizer.
 11. Navigate to ''Media > Library''.
 12. Select the latest image added (the cropped logo).
 13. Observe that the ''Alt Text'', ''Title'', ''Caption'', and
 ''Description'' previously set are populated in the **Attachment Details**
 sidebar. ✅
 14. Repeat steps 2-3.
 15. Reset all attachment properties (clear all fields).
 16. Go to the ''Appearance > Customize''.
 17. Select **Site Identity**, and under the **Logo** section, click
 "Change Logo".
 18. Repeat steps 7-12.
 19. Observe that ''Title'' contains the **name** of the cropped file, and
 that ''Description'' contains the **URL** of the cropped file. The other
 two fields remain empty. ✅

 (* NB: you do not need to publish for this test, but it avoids popups and
 revision notices in subsequent steps.)

 === Expected Results (✅)
 - **Attachment Details** attributes are preserved when set on the source
 image.✅
 - When attributes are blank, the ''Title'' and ''Description'' attributes
 are automatically set to the cropped file **name** and **URL**,
 respectively.✅

 === Screenshots
   [[Image(https://cldup.com/RUxY0udTup.png)]]
   ''Original uploaded image (Step 3).''

   [[Image(https://cldup.com/3zwaAryoSI.png)]]
   ''Cropped logo image retains attributes (Step 13).''

   [[Image(https://cldup.com/KEjaIbr00c.png)]]
   ''Image with cleared attributes (Step 15).''

   [[Image(https://cldup.com/DkvvJMfaay.png)]]
   ''Cropped logo image defaults Title and Description to name and URL
 (Step 19).''

 === Additional Notes
 This PR preserves attachment details for the Customizer's **Logo** crops,
 but crops to the **Site Icon** do not retain those attributes -- the
 system exhibits the same behavior as in Step 19 above. This is out of
 scope for the reported issue, but worth noting here.

   [[Image(https://cldup.com/A6Fmgaq4Hw.png)]]
   ''Crop for **Site Icon** does not retain attributes from original image
 (**Additional Notes**).''

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 01:17:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 01:17:59 -0000
Subject: [wp-trac] [WordPress Trac] #55441: In wp_insert_term,
 pass $args as an additional parameter to after-insert actions
 (create_term, created_term, et al)
In-Reply-To: <051.80966e4799316bbd47b607a57d393a55@wordpress.org>
References: <051.80966e4799316bbd47b607a57d393a55@wordpress.org>
Message-ID: <066.ce68df1769a0127264474564a105a41c@wordpress.org>

#55441: In wp_insert_term, pass $args as an additional parameter to after-insert
actions (create_term, created_term, et al)
-------------------------+-----------------------------
 Reporter:  mboynes      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  Taxonomy     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * keywords:   => needs-patch
 * milestone:  Awaiting Review => Future Release


Comment:

 Hi there, thanks for the ticket! I think passing `$args` to these filters
 makes sense.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55441#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 03:57:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 03:57:40 -0000
Subject: [wp-trac] [WordPress Trac] #55445: Should WP_Post_Type preserve
 Array of capability_type?
Message-ID: <055.23221db9c67c9e0fdbe3ea734534790a@wordpress.org>

#55445: Should WP_Post_Type preserve Array of capability_type?
-------------------------------+-----------------------------
 Reporter:  Howdy_McGee        |      Owner:  (none)
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Posts, Post Types  |    Version:
 Severity:  minor              |   Keywords:
  Focuses:                     |
-------------------------------+-----------------------------
 If I register a post type with `capability_type` as an array
 `capbility_type => array( 'singular', 'plural' )`. The WP_Post_Type object
 only holds onto the singular capability_type. Should the object preserve
 the array since it has singular and plural?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55445>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 04:43:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 04:43:04 -0000
Subject: [wp-trac] [WordPress Trac] #55446: Typos on documentation
Message-ID: <053.21e753cad686c0f60264d66e908115cd@wordpress.org>

#55446: Typos on documentation
-------------------------+-----------------------------
 Reporter:  Farallon5    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 On this page:
 https://wordpress.org/support/article/wordpress-editor/

 In the section:
 https://wordpress.org/support/article/wordpress-editor/#the-anatomy-
 of-a-block

 There are several typos in this paragraph.

 Here is a corrected version:

 Each block consists of a Block Toolbar, a Block Settings Sidebar and the
 Block Content. Depending on the block’s purpose the buttons of the Block
 Toolbar will change and so will **the** settings items in the Block
 settings sidebar.

 All the core blocks are divided into three sections:
 1) Description in how a block works
 2) The items in the Block Tools
 3) What you can change in the Block Settings Sidebar.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55446>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 04:49:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 04:49:12 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.ee39d540e93c28c5c6bd8e7eb50a7e58@wordpress.org>

#36907: Improved sticky post query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  assigned
 Priority:  normal                           |   Milestone:  6.0
Component:  Query                            |     Version:  3.5
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests commit


Comment:

 The pull request looks good for commit, marking as such.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 05:24:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 05:24:49 -0000
Subject: [wp-trac] [WordPress Trac] #55447: 2022 theme giving warning for
 deprecated header and footer.
Message-ID: <062.6a93411087dfded9f2ee0241db8a2a43@wordpress.org>

#55447: 2022 theme giving warning for deprecated header and footer.
--------------------------------+-----------------------------
 Reporter:  divyesh16coderkube  |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  General             |    Version:  5.9.2
 Severity:  minor               |   Keywords:
  Focuses:                      |
--------------------------------+-----------------------------
 We have created template and used 'get_header()' & 'get_footer()' in that
 but then it displaying deprecated message for them.

 Error => Deprecated: Theme without footer.php is deprecated since version
 3.0.0 with no alternative available. Please include a footer.php template
 in your theme. in C:\xampp\htdocs\dvs\miniplanner\wp-
 includes\functions.php on line 5516

 So, how can we use 'get_header()' & 'get_footer()', please let us know.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55447>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 06:47:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 06:47:20 -0000
Subject: [wp-trac] [WordPress Trac] #53177: WP_User_Query does not
 accept fields as string except ID
In-Reply-To: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
References: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
Message-ID: <065.7aef8d7558d163296892acd0ed533421@wordpress.org>

#53177: WP_User_Query does not accept fields as string except ID
-------------------------------------------------+-------------------------
 Reporter:  rilwis                               |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:  4.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-unit-    |     Focuses:  docs
  tests needs-refresh needs-testing-info         |
-------------------------------------------------+-------------------------

Comment (by rilwis):

 @hellofromTonya ,

 Here is a simple code to test:


 {{{
 add_action( 'init', function() {
         $users = get_users( [
                 'fields' => 'display_name',
         ] );
         print_r( $users ); // Expect an array of display names, but got an
 array of IDs.
 } );
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53177#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 10:12:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 10:12:43 -0000
Subject: [wp-trac] [WordPress Trac] #55447: 2022 theme giving warning
 for deprecated header and footer.
In-Reply-To: <062.6a93411087dfded9f2ee0241db8a2a43@wordpress.org>
References: <062.6a93411087dfded9f2ee0241db8a2a43@wordpress.org>
Message-ID: <077.1573dbf46b96d3c16c839c924f40d02d@wordpress.org>

#55447: 2022 theme giving warning for deprecated header and footer.
--------------------------------+------------------------
 Reporter:  divyesh16coderkube  |       Owner:  (none)
     Type:  defect (bug)        |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  Themes              |     Version:  5.9.2
 Severity:  minor               |  Resolution:  duplicate
 Keywords:                      |     Focuses:
--------------------------------+------------------------
Changes (by SergeyBiryukov):

 * status:  new => closed
 * resolution:   => duplicate
 * component:  General => Themes
 * milestone:  Awaiting Review =>


Comment:

 Hi there, welcome to WordPress Trac!

 Thanks for the report, we're already tracking this issue in #55023.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55447#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 10:22:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 10:22:42 -0000
Subject: [wp-trac] [WordPress Trac] #55448: WP_Widget_Block outputs empty
 container if widget has no output
Message-ID: <058.aa6e76f89b6bf6a1bd18b3d2b12c863b@wordpress.org>

#55448: WP_Widget_Block outputs empty container if widget has no output
----------------------------+-----------------------------
 Reporter:  stiofansisland  |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Widgets         |    Version:  5.9.2
 Severity:  major           |   Keywords:
  Focuses:  ui              |
----------------------------+-----------------------------
 There are many widgets that for some reason or another will not output any
 content, this can be for many reasons, one example would be for a logged
 in/out user.

 When you create your own widget class you have control of the widget()
 output function and can return an empty string to prevent any output.

 The WP_Widget_Block class which is used as a sort of wrapper contains its
 own widget() class which prevents no output even if the block has no
 content.

 This has left empty boxes showing for many plugins widgets on sites and
 breaks the backward compatibility of the widgets system.

 This should be as easy fix, I will create and submit a patch soon.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55448>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 10:28:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 10:28:13 -0000
Subject: [wp-trac] [WordPress Trac] #49278: Improve meta query
In-Reply-To: <053.f456e8069a5775465fadeab7ad94e33c@wordpress.org>
References: <053.f456e8069a5775465fadeab7ad94e33c@wordpress.org>
Message-ID: <068.2ed707d3db16ef6970a91f4b377f9d34@wordpress.org>

#49278: Improve meta query
-------------------------------------------------+-------------------------
 Reporter:  jillebehm                            |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Query                                |     Version:  5.3.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback early early-  |     Focuses:
  like-actually-early has-unit-tests             |  performance
-------------------------------------------------+-------------------------

Comment (by craigfrancis):

 As we have a Dev Chat today, I'll summarise my conversation with Mark so
 far:

 - The current patch does not change anything if the query uses `OR` (ref
 `$this->has_or_relation`), which does not help @jillebehm
 ([https://gist.github.com/craigfrancis/9230be877423e73a28475b061495fee7
 rough example]). This is because `find_compatible_table_alias()` will try
 to re-use an existing alias, which would have specified the `meta_key`
 from the first condition.
 - In my own basic tests, which does not represent real data, I was able to
 get similar improvements by changing the field to `varchar(191)` (ref
 #33885), or running `OPTIMIZE TABLE`, because the updated INDEX info would
 lead to a much better query execution plan.
 - I have a small concern about how the `get_meta_sql` filter/hook might be
 affected; e.g. a plugin that modifies the 'join' string (e.g. to apply
 their own version of this fix), but I think they should expect changes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49278#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 10:37:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 10:37:25 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.3f5663e46cef4af84710bc0d294c9924@wordpress.org>

#36907: Improved sticky post query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Query                            |     Version:  3.5
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------
Changes (by spacedmonkey):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52982" 52982]:
 {{{
 #!CommitTicketReference repository="" revision="52982"
 Query: Improved sticky post query

 Ensure that the parameters `update_post_meta_cache`,
 `update_post_term_cache`, `cache_results`, `suppress_filters` and
 `lazy_load_term_meta` that are passed to WP_Query, are also passed down to
 the secondary query used to get sticky
 posts.

 Props Spacedmonkey, peterwilsoncc, rehanali, uday17035.
 Fixes #36907.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 10:38:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 10:38:47 -0000
Subject: [wp-trac] [WordPress Trac] #53822: Inconsistent handling of
 block equivalents of legacy widgets
In-Reply-To: <055.cf7fed96bebbe5453d9262459634b9ef@wordpress.org>
References: <055.cf7fed96bebbe5453d9262459634b9ef@wordpress.org>
Message-ID: <070.f3bf2d1eafad63dbcd2c74bc7339543b@wordpress.org>

#53822: Inconsistent handling of block equivalents of legacy widgets
--------------------------+------------------------------
 Reporter:  Frank Klein   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Widgets       |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by stiofansisland):

 * Attachment "53822.patch" added.

 Fix

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53822>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 10:42:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 10:42:21 -0000
Subject: [wp-trac] [WordPress Trac] #55448: WP_Widget_Block outputs
 empty container if widget has no output
In-Reply-To: <058.aa6e76f89b6bf6a1bd18b3d2b12c863b@wordpress.org>
References: <058.aa6e76f89b6bf6a1bd18b3d2b12c863b@wordpress.org>
Message-ID: <073.357509895db5268e6364e79fbec535ec@wordpress.org>

#55448: WP_Widget_Block outputs empty container if widget has no output
----------------------------+------------------------------
 Reporter:  stiofansisland  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Widgets         |     Version:  5.9.2
 Severity:  major           |  Resolution:
 Keywords:                  |     Focuses:  ui
----------------------------+------------------------------
Changes (by stiofansisland):

 * Attachment "55448.patch" added.

 Fix

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55448>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 10:44:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 10:44:47 -0000
Subject: [wp-trac] [WordPress Trac] #19901: Speeding up Dashboard and
 Comment moderation SQL load
In-Reply-To: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
References: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
Message-ID: <070.e01a1ea47bd4a7ae1437762db4b4601e@wordpress.org>

#19901: Speeding up Dashboard and Comment moderation SQL load
-------------------------------------------------+-------------------------
 Reporter:  FolioVision                          |       Owner:
                                                 |  markjaquith
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Comments                             |     Version:  3.3
 Severity:  major                                |  Resolution:
 Keywords:  needs-testing dev-feedback has-      |     Focuses:
  patch                                          |  performance
-------------------------------------------------+-------------------------

Comment (by uday17035):

 I have created PR with the required changes. @spacedmonkey could you
 please review it?

 @markjaquith if you won't mind, may I own this ticket?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19901#comment:30>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 10:56:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 10:56:54 -0000
Subject: [wp-trac] [WordPress Trac] #55448: WP_Widget_Block outputs
 empty container if widget has no output
In-Reply-To: <058.aa6e76f89b6bf6a1bd18b3d2b12c863b@wordpress.org>
References: <058.aa6e76f89b6bf6a1bd18b3d2b12c863b@wordpress.org>
Message-ID: <073.f18f75d65fdadc3601ac4c8478cfd8d2@wordpress.org>

#55448: WP_Widget_Block outputs empty container if widget has no output
----------------------------+------------------------------
 Reporter:  stiofansisland  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Widgets         |     Version:  5.9.2
 Severity:  major           |  Resolution:
 Keywords:                  |     Focuses:  ui
----------------------------+------------------------------
Changes (by stiofansisland):

 * Attachment "55448.diff" added.

 Fix in .diff format

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55448>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 11:19:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 11:19:38 -0000
Subject: [wp-trac] [WordPress Trac] #53822: Inconsistent handling of
 block equivalents of legacy widgets
In-Reply-To: <055.cf7fed96bebbe5453d9262459634b9ef@wordpress.org>
References: <055.cf7fed96bebbe5453d9262459634b9ef@wordpress.org>
Message-ID: <055.cf7fed96bebbe5453d9262459634b9ef@wordpress.org>

#53822: Inconsistent handling of block equivalents of legacy widgets
--------------------------+------------------------------
 Reporter:  Frank Klein   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Widgets       |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by stiofansisland):

 * Attachment "53822.patch" removed.

 Fix

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53822>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 11:20:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 11:20:58 -0000
Subject: [wp-trac] [WordPress Trac] #55448: WP_Widget_Block outputs
 empty container if widget has no output
In-Reply-To: <058.aa6e76f89b6bf6a1bd18b3d2b12c863b@wordpress.org>
References: <058.aa6e76f89b6bf6a1bd18b3d2b12c863b@wordpress.org>
Message-ID: <073.2db175557d3a0e3ee079621566714eba@wordpress.org>

#55448: WP_Widget_Block outputs empty container if widget has no output
----------------------------+---------------------
 Reporter:  stiofansisland  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  Widgets         |     Version:  5.9.2
 Severity:  major           |  Resolution:
 Keywords:  has-patch       |     Focuses:  ui
----------------------------+---------------------
Changes (by SergeyBiryukov):

 * keywords:   => has-patch
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55448#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 11:20:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 11:20:59 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.e237b47f7dda8c02c68741993350cc1e@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------

Comment (by antonvlasenko):

 Thank you so much for the test reports, @ironprogrammer!
 I appreciate it.
 >  crops to the Site Icon do not retain those attributes
 IMO it's better to implement this fix in the scope of another PR as it
 will require implementing new unit tests. Thank you for reporting.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 11:30:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 11:30:36 -0000
Subject: [wp-trac] [WordPress Trac] #55449: More filter options for
 searching theme's & plugins - "Last updated" / "Test with my WP version".
Message-ID: <053.5016a78b82512560a5c1927d5f201dff@wordpress.org>

#55449: More filter options for searching theme's & plugins - "Last updated" /
"Test with my WP version".
--------------------------------+-----------------------------
 Reporter:  NekoJonez           |      Owner:  (none)
     Type:  enhancement         |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  Plugins             |    Version:
 Severity:  normal              |   Keywords:
  Focuses:  ui, administration  |
--------------------------------+-----------------------------
 When I'm looking in WP to install a new theme/plugin I find it quite
 annoying that I'm unable to filter my search results a bit more.

 When I'm looking for a new plugin for a certain goal, I would love to
 filter on two things.

 1) If the plugin is tested or not (and working) on my current WP version.
 2) If the plugin got a recent update. (Maybe this might be a setting the
 user can choose. Since, for some is recent 1 year and for others it's 1
 month.)

 I think these filter options, with maybe checkmarks ...? could fit nicely
 on where I placed green in the attached screenshot.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55449>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 11:31:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 11:31:02 -0000
Subject: [wp-trac] [WordPress Trac] #55449: More filter options for
 searching theme's & plugins - "Last updated" / "Test with my WP version".
In-Reply-To: <053.5016a78b82512560a5c1927d5f201dff@wordpress.org>
References: <053.5016a78b82512560a5c1927d5f201dff@wordpress.org>
Message-ID: <068.0a83251722de62def9ae95fa11762577@wordpress.org>

#55449: More filter options for searching theme's & plugins - "Last updated" /
"Test with my WP version".
-------------------------+---------------------------------
 Reporter:  NekoJonez    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Plugins      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui, administration
-------------------------+---------------------------------
Changes (by NekoJonez):

 * Attachment "Opera screenshot.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55449>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 11:32:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 11:32:56 -0000
Subject: [wp-trac] [WordPress Trac] #54437: Warning not in bold?
In-Reply-To: <053.79ef35713d160dce241eff046fd87735@wordpress.org>
References: <053.79ef35713d160dce241eff046fd87735@wordpress.org>
Message-ID: <068.e32f7334c96a53a8279af36c91d1da26@wordpress.org>

#54437: Warning not in bold?
-------------------------+-------------------------------------------------
 Reporter:  NekoJonez    |       Owner:  (none)
     Type:  defect       |      Status:  new
  (bug)                  |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:  5.8.3
 Severity:  trivial      |  Resolution:
 Keywords:               |     Focuses:  ui, administration, template,
                         |  coding-standards
-------------------------+-------------------------------------------------
Changes (by NekoJonez):

 * focuses:  administration, coding-standards => ui, administration,
     template, coding-standards
 * type:  enhancement => defect (bug)
 * version:  5.8.2 => 5.8.3


Comment:

 In the latest dev builds, the locations are changed:

 https://build.trac.wordpress.org/browser/trunk/wp-
 includes/functions.php?marks=1582#L1592
 https://build.trac.wordpress.org/browser/trunk/wp-includes/class-wp-
 theme.php?marks=284#L285

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54437#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 11:33:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 11:33:19 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.86fb219d40bce7249e4dad49064baaae@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------

Comment (by antonvlasenko):

 Just FYI: this PR has some breaking changes.
 Currently, WordPress always overwrites `Title` and `Description`
 properties (with `name` and `url` of the image file respectively) when we
 crop an image.
 If this PR gets merged, these properties will only be populated
 (overwritten) if `Title` and `Description` properties of the original
 image are empty.
 I'm not sure if that's desired behaviour, but I can't think of a better
 implementation.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:29>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 11:35:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 11:35:01 -0000
Subject: [wp-trac] [WordPress Trac] #55450: WP_Upgrader::run docblock
 incorrect
Message-ID: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>

#55450: WP_Upgrader::run docblock incorrect
-----------------------------+-----------------------------
 Reporter:  paulkevan        |      Owner:  (none)
     Type:  defect (bug)     |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:  trunk
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 The docblock description for the `run` function inaccurately has the
 default value for `clear_working` as `false`, whereas the default is
 `true`.

 The ordering of the array values should also be updated to be consistent
 with the docblock, similar to the `install_package` function.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55450>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 11:43:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 11:43:37 -0000
Subject: [wp-trac] [WordPress Trac] #55444: Sticky posts are limited to 5
In-Reply-To: <056.93fd87dc2b3d2cbc54d6372c12a75b30@wordpress.org>
References: <056.93fd87dc2b3d2cbc54d6372c12a75b30@wordpress.org>
Message-ID: <071.6eba380329ce25344de923013218fca8@wordpress.org>

#55444: Sticky posts are limited to 5
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Posts, Post Types                    |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch good-first-bug           |     Focuses:
  reporter-feedback                              |
-------------------------------------------------+-------------------------
Changes (by azouamauriac):

 * keywords:  needs-patch good-first-bug => needs-patch good-first-bug
     reporter-feedback


Comment:

 Hello @spacedmonkey  what are the steps to reproduce the bug please? I
 created six posts and made all of them sticky, I created a block page, use
 query loop to show only stickies posts and then I go to front page and all
 my six stickies posts are show up.

 So how can I reproduce the bug here? Thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55444#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 12:19:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 12:19:52 -0000
Subject: [wp-trac] [WordPress Trac] #54725: Test tool and unit test
 improvements for 6.0
In-Reply-To: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
References: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
Message-ID: <073.448a3aeea75794c03670b6e4e02e8572@wordpress.org>

#54725: Test tool and unit test improvements for 6.0
--------------------------------------+---------------------
 Reporter:  hellofromTonya            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by jrf):

 I've opened DRAFT PR https://github.com/WordPress/wordpress-
 develop/pull/2453

 Most changes in that PR are ready for commit, except for the "WIP/DEBUG"
 commit at the top of the stack.

 See the PR description for additional context.

 There is one documentation fix commit in the chain which belong with
 #54729

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54725#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 13:35:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 13:35:31 -0000
Subject: [wp-trac] [WordPress Trac] #55451: Same URL in page and post
 creates conflict
Message-ID: <051.144998b3d38dd74024af14bef1870a8a@wordpress.org>

#55451: Same URL in page and post creates conflict
--------------------------+-----------------------------
 Reporter:  fotisps       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Taxonomy      |    Version:  5.9.2
 Severity:  normal        |   Keywords:  needs-patch
  Focuses:                |
--------------------------+-----------------------------
 When someone creates a page and a post with the same URL, without any
 other prefix in the URL there is a confusion because the user cannot
 understand if sees the post or the page. If he type the url, he will be
 redirect to the page and not to the post.
 Paradigm:
 Page: www.domain.com/myname
 Post: www.domain.com/myname
 User is directed to the Page if he types the URL.

 This could be prevented by cross checking all the URLs that have been
 generated in every post type in order not to have duplicates and give a
 suffix or a prefix to the final url of the post or the page.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55451>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 14:07:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 14:07:01 -0000
Subject: [wp-trac] [WordPress Trac] #55450: WP_Upgrader::run docblock
 incorrect
In-Reply-To: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
References: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
Message-ID: <068.74133815c981b5e94218180215fe2944@wordpress.org>

#55450: WP_Upgrader::run docblock incorrect
-----------------------------+----------------------------
 Reporter:  paulkevan        |       Owner:  davidbaumwald
     Type:  defect (bug)     |      Status:  reviewing
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+----------------------------
Changes (by davidbaumwald):

 * owner:  (none) => davidbaumwald
 * status:  new => reviewing
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55450#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 14:29:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 14:29:40 -0000
Subject: [wp-trac] [WordPress Trac] #55451: Same URL in page and post
 creates conflict
In-Reply-To: <051.144998b3d38dd74024af14bef1870a8a@wordpress.org>
References: <051.144998b3d38dd74024af14bef1870a8a@wordpress.org>
Message-ID: <066.7eb961cb32bd56d57500762706c7c07d@wordpress.org>

#55451: Same URL in page and post creates conflict
--------------------------+------------------------
 Reporter:  fotisps       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Permalinks    |     Version:  5.9.2
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by SergeyBiryukov):

 * keywords:  needs-patch =>
 * resolution:   => duplicate
 * status:  new => closed
 * component:  Taxonomy => Permalinks
 * milestone:  Awaiting Review =>


Comment:

 Hi there, welcome back to WordPress Trac!

 Thanks for the report, we're already tracking this issue in #13459.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55451#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 14:33:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 14:33:29 -0000
Subject: [wp-trac] [WordPress Trac] #47513: JavaScript TypeError when
 Video Playlists use native video elements
In-Reply-To: <051.e1395a3430ffb65f830023f935afff26@wordpress.org>
References: <051.e1395a3430ffb65f830023f935afff26@wordpress.org>
Message-ID: <066.266ebfbc3b9f5723f7c8cefc8c5d574e@wordpress.org>

#47513: JavaScript TypeError when Video Playlists use native video elements
---------------------------------------+-------------------------
 Reporter:  afercia                    |       Owner:  afercia
     Type:  defect (bug)               |      Status:  assigned
 Priority:  normal                     |   Milestone:  6.0
Component:  Media                      |     Version:
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:  javascript
---------------------------------------+-------------------------
Changes (by afercia):

 * component:  Editor => Media


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47513#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 14:36:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 14:36:56 -0000
Subject: [wp-trac] [WordPress Trac] #54437: Warning not in bold?
In-Reply-To: <053.79ef35713d160dce241eff046fd87735@wordpress.org>
References: <053.79ef35713d160dce241eff046fd87735@wordpress.org>
Message-ID: <068.e8dd4e9e094ff3b8cbc677ac40c00d0a@wordpress.org>

#54437: Warning not in bold?
-------------------------------------+-------------------------------------
 Reporter:  NekoJonez                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  General                  |     Version:
 Severity:  trivial                  |  Resolution:
 Keywords:  needs-patch good-first-  |     Focuses:  ui, administration,
  bug                                |  template, coding-standards
-------------------------------------+-------------------------------------
Changes (by SergeyBiryukov):

 * keywords:   => needs-patch good-first-bug
 * version:  5.8.3 =>
 * milestone:  Awaiting Review => 6.0


Old description:

> Most of the warnings in WP have the "warning" part in bold. Yet, there
> are a few that aren't in bold.
>
> Except these:
>
> https://build.trac.wordpress.org/browser/trunk/wp-includes/class-wp-
> theme.php?marks=284#L284
> https://build.trac.wordpress.org/browser/trunk/wp-
> includes/functions.php?marks=1582#L1582
>
> For the sake of being consistent, shouldn't these have bold tags as well?

New description:

 Most of the warnings in WP have the "warning" part in bold. Yet, there are
 a few that aren't in bold.

 Except these:

 https://build.trac.wordpress.org/browser/tags/5.9.2/wp-
 includes/functions.php?marks=1583#L1582
 https://build.trac.wordpress.org/browser/tags/5.9.2/wp-includes/class-wp-
 theme.php?marks=284#L283

 For the sake of being consistent, shouldn't these have bold tags as well?

--

Comment:

 Thanks for the ticket!

 Updated the description with permanent links so that the locations do not
 change. Removing the version, as these messages were not introduced in
 5.8.2 or 5.8.3.

 It looks like most of the "Error:" prefixes in core are placed inside a
 `<strong>` tag, so I think it makes sense to do the same here.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54437#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 14:48:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 14:48:43 -0000
Subject: [wp-trac] [WordPress Trac] #54725: Test tool and unit test
 improvements for 6.0
In-Reply-To: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
References: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
Message-ID: <073.aee88b39e74cc6dd5e064e300c60822c@wordpress.org>

#54725: Test tool and unit test improvements for 6.0
--------------------------------------+---------------------
 Reporter:  hellofromTonya            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52983" 52983]:
 {{{
 #!CommitTicketReference repository="" revision="52983"
 Tests: Remove some unused variables in `phpunit/tests/filters.php`.

 Follow-up to [29422], [31014].

 Props azouamauriac.
 See #54725.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54725#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 15:02:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 15:02:04 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.2d738942a636e31ad2f3171e2030c66d@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52984" 52984]:
 {{{
 #!CommitTicketReference repository="" revision="52984"
 Docs: Adjust documentation in `get_post_galleries()` tests per the
 documentation standards.

 Follow-up to [52190], [52797].

 Props azouamauriac, SergeyBiryukov.
 See #54725, #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:45>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 15:02:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 15:02:04 -0000
Subject: [wp-trac] [WordPress Trac] #54725: Test tool and unit test
 improvements for 6.0
In-Reply-To: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
References: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
Message-ID: <073.f9c8c51002460296c120255cc5649978@wordpress.org>

#54725: Test tool and unit test improvements for 6.0
--------------------------------------+---------------------
 Reporter:  hellofromTonya            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52984" 52984]:
 {{{
 #!CommitTicketReference repository="" revision="52984"
 Docs: Adjust documentation in `get_post_galleries()` tests per the
 documentation standards.

 Follow-up to [52190], [52797].

 Props azouamauriac, SergeyBiryukov.
 See #54725, #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54725#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 15:53:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 15:53:20 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.d149056664a566882bb35e5846757826@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots                                    |  accessibility
-------------------------------------------------+-------------------------

Comment (by hellofromTonya):

 Replying to [comment:29 antonvlasenko]:
 > Just FYI: this PR has some breaking changes.
 > Currently, WordPress always overwrites `Title` and `Description`
 properties (with `name` and `url` of the image file respectively) when we
 crop an image.
 > If this PR gets merged, these properties will only be populated
 (overwritten) if `Title` and `Description` properties of the original
 image are empty.
 > I'm not sure if that's desired behavior, but I can't think of a better
 implementation.

 [https://github.com/WordPress/wordpress-develop/pull/2441 PR 2441] does
 pre-populate a new cropped image's properties from the original image's
 properties - including the `Title` and `Description`. The `Title` though
 doesn't compare if the user edited it though - proposing that change in
 the code review.

 The PR seems to align to [#comment:2 the intent proposed by @flixos90]
 >fill in the values the user entered for the original image (as defaults)

 But yes, both the `Title` and `Description` properties existing behavior /
 values are changed by the PR.

 What about the original intent? Looking at the existing data and [33280] /
 #29211 that added this functionality:

 * there's no discussion about the properties.
 * and thus, both `Title` and `Description` seem to be generic placeholders
 to create the new cropped image.

 To me, as a user, I'd expect to retain the original image's properties and
 be given the ability to modify them when cropping. If the [#comment:1
 properties sidebar is also exposed as @Clorith proposed], then the user is
 given that ability.

 Hey @flixos90 @Clorith what do you think today (as this one is an oldie)?
 Any concerns about changing the existing behavior for the `Title` and
 `Description`? Or does it still make sense today to pre-populate with the
 original image's properties and show the properties sidebar?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:30>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 16:13:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 16:13:10 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.41af2b740143c73665e1120bc424019c@wordpress.org>

#36907: Improved sticky post query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Query                            |     Version:  3.5
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------
Changes (by SergeyBiryukov):

 * Attachment "36907.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 16:13:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 16:13:29 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.b2b95c5f8c54e02705c33311e89d1417@wordpress.org>

#36907: Improved sticky post query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  reopened
 Priority:  normal                           |   Milestone:  6.0
Component:  Query                            |     Version:  3.5
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------
Changes (by SergeyBiryukov):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 It's not quite clear why [52982] removed the `'nopaging' => true` argument
 from the `get_posts()` call in question, as neither the ticket nor the
 commit message mention the removal.

 With that change, only 5 sticky posts are displayed now. This is a
 backward compatibility break, see #55444.

 [attachment:"36907.diff"] restores `'nopaging' => true` and reorder the
 parameters for consistency with similar calls elsewhere.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 16:15:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 16:15:10 -0000
Subject: [wp-trac] [WordPress Trac] #55444: Sticky posts are limited to 5
In-Reply-To: <056.93fd87dc2b3d2cbc54d6372c12a75b30@wordpress.org>
References: <056.93fd87dc2b3d2cbc54d6372c12a75b30@wordpress.org>
Message-ID: <071.dcc7b0f7a88ee107ed0c6eb528e97f60@wordpress.org>

#55444: Sticky posts are limited to 5
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Posts, Post Types                    |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch good-first-bug           |     Focuses:
  reporter-feedback                              |
-------------------------------------------------+-------------------------

Comment (by SergeyBiryukov):

 I have reproduced the issue with these steps:
 1. Switch the theme to Twenty Twenty-One.
 2. Create 10 sticky posts.
 3. Create 10 non-sticky posts.
 4. On the home page, there are now 10 non-sticky posts and 5 sticky posts
 (instead of 10).

 It looks like this was introduced in [52982] / #36907 as a result of
 removing the `'nopaging' => true` argument from the `get_posts()` call in
 question. It's not quite clear why it was removed, as neither the ticket
 nor the commit message mention the removal. With `'nopaging' => true`
 restored, all 10 sticky posts are displayed as expected.

 This seems like a backward compatibility break, so I have reopened #36907
 with a patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55444#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 16:26:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 16:26:17 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.fac376cede11e48a1b3d4eb2c2e53f04@wordpress.org>

#36907: Improved sticky post query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  reopened
 Priority:  normal                           |   Milestone:  6.0
Component:  Query                            |     Version:  3.5
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52985" 52985]:
 {{{
 #!CommitTicketReference repository="" revision="52985"
 Tests: Use a more descriptive name for the sticky posts test that verifies
 the parameters from the main query.

 Reorder the parameters of the `get_posts()` call for consistency with
 similar calls elsewhere.

 Follow-up to [52982].

 See #36907.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 16:27:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 16:27:55 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.1ce61a3c2f2cb71930a6898cdf6b916d@wordpress.org>

#36907: Improved sticky post query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  reopened
 Priority:  normal                           |   Milestone:  6.0
Component:  Query                            |     Version:  3.5
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------
Changes (by SergeyBiryukov):

 * Attachment "36907.2.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 16:28:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 16:28:29 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.0a247172bc0043a95809d501efbd2b0a@wordpress.org>

#36907: Improved sticky post query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  reopened
 Priority:  normal                           |   Milestone:  6.0
Component:  Query                            |     Version:  3.5
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------

Comment (by SergeyBiryukov):

 [attachment:"36907.2.diff"] is a refresh after [52985].

 This could also use a unit test.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 16:30:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 16:30:33 -0000
Subject: [wp-trac] [WordPress Trac] #55444: Sticky posts are limited to 5
In-Reply-To: <056.93fd87dc2b3d2cbc54d6372c12a75b30@wordpress.org>
References: <056.93fd87dc2b3d2cbc54d6372c12a75b30@wordpress.org>
Message-ID: <071.e29022d1968b72eae6d444372b8e0331@wordpress.org>

#55444: Sticky posts are limited to 5
-------------------------------+------------------------
 Reporter:  spacedmonkey       |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Posts, Post Types  |     Version:
 Severity:  normal             |  Resolution:  duplicate
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------
Changes (by SergeyBiryukov):

 * keywords:  needs-patch good-first-bug reporter-feedback => reporter-
     feedback
 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 Let's continue in #36907 to avoid confusion.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55444#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 16:57:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 16:57:17 -0000
Subject: [wp-trac] [WordPress Trac] #53177: WP_User_Query does not
 accept fields as string except ID
In-Reply-To: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
References: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
Message-ID: <065.0b57d56c022dcbe59a9b581b4d7e9ad5@wordpress.org>

#53177: WP_User_Query does not accept fields as string except ID
-------------------------------------------------+-------------------------
 Reporter:  rilwis                               |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:  4.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:  docs
  testing-info needs-testing                     |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * keywords:
     has-patch needs-testing has-unit-tests needs-refresh needs-testing-
     info
     => has-patch has-unit-tests has-testing-info needs-testing


Comment:

 Thank you @pbearne for rebasing and refreshing the PR.

 Thank you @rilwis for providing testing information.

 Will ping in the #core-test Slack channel to alert testers this is ready
 for testing and a Test Report.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53177#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 17:21:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 17:21:43 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.4a069088831646a44423efdf196d5824@wordpress.org>

#36907: Improved sticky post query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  reopened
 Priority:  normal                           |   Milestone:  6.0
Component:  Query                            |     Version:  3.5
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------

Comment (by spacedmonkey):

 Good catch @SergeyBiryukov . No paging / posts per page was removed at the
 last minute. It should not have been. I have created a follow on PR at
 [https://github.com/WordPress/wordpress-develop/pull/2454 #2454]. Can you
 take a look?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 17:21:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 17:21:52 -0000
Subject: [wp-trac] [WordPress Trac] #55450: WP_Upgrader::run docblock
 incorrect
In-Reply-To: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
References: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
Message-ID: <068.e45937016ce184b91ca1ccddf81bd9b1@wordpress.org>

#55450: WP_Upgrader::run docblock incorrect
-----------------------------+----------------------------
 Reporter:  paulkevan        |       Owner:  davidbaumwald
     Type:  defect (bug)     |      Status:  reviewing
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  docs
-----------------------------+----------------------------
Changes (by davidbaumwald):

 * focuses:   => docs


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55450#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 18:02:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 18:02:41 -0000
Subject: [wp-trac] [WordPress Trac] #55450: WP_Upgrader::run docblock
 incorrect
In-Reply-To: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
References: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
Message-ID: <068.2844677dda1ef603d55cad896ff04601@wordpress.org>

#55450: WP_Upgrader::run docblock incorrect
-----------------------------+----------------------------
 Reporter:  paulkevan        |       Owner:  davidbaumwald
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:  fixed
 Keywords:  has-patch        |     Focuses:  docs
-----------------------------+----------------------------
Changes (by davidbaumwald):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52986" 52986]:
 {{{
 #!CommitTicketReference repository="" revision="52986"
 Upgrade/Install: Fix the docs for the default value of `$clear_working` in
 `WP_Upgrader::run`.

 The current docblock for `WP_Upgrader::run` indicates the default value
 for the `clear_working` key of the `$options` argument is `false`.
 However, in the code directly below, the default is shown to be `true.
 This change updates the docblock to correct the default.

 This commit also reorders the `$defaults` to match the order they appear
 in the docblock.

 Props paulkevan.
 Fixes #55450.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55450#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 19:18:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 19:18:56 -0000
Subject: [wp-trac] [WordPress Trac] #55450: WP_Upgrader::run docblock
 incorrect
In-Reply-To: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
References: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
Message-ID: <068.9fa473bb707b28b4b1144a85bd8efb1a@wordpress.org>

#55450: WP_Upgrader::run docblock incorrect
-----------------------------+----------------------------
 Reporter:  paulkevan        |       Owner:  davidbaumwald
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  2.8
 Severity:  normal           |  Resolution:  fixed
 Keywords:  has-patch        |     Focuses:  docs
-----------------------------+----------------------------
Changes (by costdev):

 * version:  trunk => 2.8


Comment:

 Introduced in [11005].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55450#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 19:26:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 19:26:50 -0000
Subject: [wp-trac] [WordPress Trac] #55450: WP_Upgrader::run docblock
 incorrect
In-Reply-To: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
References: <053.84011a42cc1fdaad9d4456d220facf74@wordpress.org>
Message-ID: <068.1d186e1301697f7c848a2ce612ad9df6@wordpress.org>

#55450: WP_Upgrader::run docblock incorrect
-----------------------------+----------------------------
 Reporter:  paulkevan        |       Owner:  davidbaumwald
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  2.8
 Severity:  normal           |  Resolution:  fixed
 Keywords:  has-patch        |     Focuses:  docs
-----------------------------+----------------------------

Comment (by SergeyBiryukov):

 And the docs were added in [30758].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55450#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 20:10:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 20:10:39 -0000
Subject: [wp-trac] [WordPress Trac] #55431: add_theme_support for html5
 on search-form not working
In-Reply-To: <053.dae1340eaa75431229a2d9f1fd7f4f8a@wordpress.org>
References: <053.dae1340eaa75431229a2d9f1fd7f4f8a@wordpress.org>
Message-ID: <068.32174f3bae23f0001c19aa5e02892464@wordpress.org>

#55431: add_theme_support for html5 on search-form not working
---------------------------+----------------------
 Reporter:  blackawxs      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:  invalid
 Keywords:                 |     Focuses:
---------------------------+----------------------
Changes (by costdev):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Hi @blackawxs, thanks for opening this ticket!

 @joyously is correct. See the results in different scenarios below.


 With `searchform.php` and without `html5: search-form` theme support:
 {{{#!php
 <form role="search" method="get" class="search-form"
 action="http://localhost/wordpress-develop/src/">
         <label for="search-form-1">Search…</label>
         <input type="search" id="search-form-1" class="search-field"
 value="" name="s">
         <input type="submit" class="search-submit" value="Search">
 </form>
 }}}

 With `searchform.php` and with `html5: search-form` theme support:
 {{{#!php
 <form role="search" method="get" class="search-form"
 action="http://localhost/wordpress-develop/src/">
         <label for="search-form-1">Search…</label>
         <input type="search" id="search-form-1" class="search-field"
 value="" name="s">
         <input type="submit" class="search-submit" value="Search">
 </form>
 }}}

 Without `searchform.php` and without `html5: search-form` theme support:
 {{{#!php
 <form role="search" method="get" id="searchform" class="searchform"
 action="http://localhost/wordpress-develop/src/">
         <div>
                 <label class="screen-reader-text" for="s">Search
 for:</label>
                 <input type="text" value="" name="s" id="s">
                 <input type="submit" id="searchsubmit" value="Search">
         </div>
 </form>
 }}}

 Without `searchform.php` and with `html5: search-form` theme support:
 {{{#!php
 <form role="search" method="get" class="search-form"
 action="http://localhost/wordpress-develop/src/">
         <label>
                 <span class="screen-reader-text">Search for:</span>
                 <input type="search" class="search-field"
 placeholder="Search …" value="" name="s">
         </label>
         <input type="submit" class="search-submit" value="Search">
 </form>
 }}}

 As this is the expected behaviour, I'll close this ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55431#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 21:41:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 21:41:19 -0000
Subject: [wp-trac] [WordPress Trac] #55452: `safecss_filter_attr` removes
 background-images with URL parameters
Message-ID: <050.6833b796084a793232f1982c6ec0c100@wordpress.org>

#55452: `safecss_filter_attr` removes background-images with URL parameters
--------------------------+-----------------------------
 Reporter:  ryelle        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Formatting    |    Version:
 Severity:  normal        |   Keywords:
  Focuses:  css           |
--------------------------+-----------------------------
 If you try to add a background-image using an inline style, and the URL
 has query parameters (specifically, an `&`), the background-image will be
 stripped from the content.

 What seems to be happening: the `&` is encoded, and becomes `&amp;`, and
 when `safecss_filter_attr` splits the `$css` into separate declarations,
 it does so just by [https://github.com/WordPress/wordpress-
 develop/blob/ee96cedcb891c6a6e5b7b30a6f1c247345161b88/src/wp-
 includes/kses.php#L2242 breaking on a semicolon], which breaks the URL
 value. For example, `background-
 image:url(https://fake.test/image.png?a=1&b=2);` becomes `background-
 image:url(https://fake.test/image.png?a=1&amp` and `b=2)`, and neither are
 valid CSS.

 **To reproduce:**

 Try adding this Media & Text block, which uses this image:
 [https://img.rawpixel.com/s3fs-
 private/rawpixel_images/website_content/a005-scottw-465.jpg?w=1200&h=1200&fit=clip&crop=default&dpr=1&q=75&vib=3&con=3&usm=15&cs=srgb&bg=F4F4F3&ixlib=js-2.2.1&s=06d4e5a9962096a6010029591ae36198
 https://img.rawpixel.com/s3fs-
 private/rawpixel_images/website_content/a005-scottw-465.jpg?w=1200&h=1200…]

 {{{
 <!-- wp:media-text
 {"mediaId":null,"mediaType":"image","imageFill":true,"focalPoint":{"x":"0.75","y":"0.72"}}
 -->
 <div class="wp-block-media-text alignwide is-stacked-on-mobile is-image-
 fill"><figure class="wp-block-media-text__media" style="background-
 image:url(https://img.rawpixel.com/s3fs-
 private/rawpixel_images/website_content/a005-scottw-465.jpg?w=1200&h=1200&fit=clip&crop=default&dpr=1&q=75&vib=3&con=3&usm=15&cs=srgb&bg=F4F4F3&ixlib=js-2.2.1&s=06d4e5a9962096a6010029591ae36198
 );background-position:75% 72%"><img src="https://img.rawpixel.com/s3fs-
 private/rawpixel_images/website_content/a005-scottw-465.jpg?w=1200&h=1200&fit=clip&crop=default&dpr=1&q=75&vib=3&con=3&usm=15&cs=srgb&bg=F4F4F3&ixlib=js-2.2.1&s=06d4e5a9962096a6010029591ae36198"
 alt="" /></figure><div class="wp-block-media-text__content"><!--
 wp:paragraph {"placeholder":"Content…","fontSize":"medium"} -->
 <p class="has-medium-font-size">"<a rel="noreferrer noopener"
 href="https://www.rawpixel.com/image/430579/free-photo-image-palm-tree-
 palm-africa" target="_blank">Palm trees at Cape Town, South Africa</a>" by
 Scott Webb is marked with <a rel="noreferrer noopener"
 href="https://creativecommons.org/publicdomain/zero/1.0/?ref=openverse"
 target="_blank">CC0 1.0</a>.</p>
 <!-- /wp:paragraph --></div></div>
 <!-- /wp:media-text -->
 }}}

 When you save and view the post, the background-image is gone.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55452>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 21:47:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 21:47:46 -0000
Subject: [wp-trac] [WordPress Trac] #55452: `safecss_filter_attr`
 removes background-images with URL parameters
In-Reply-To: <050.6833b796084a793232f1982c6ec0c100@wordpress.org>
References: <050.6833b796084a793232f1982c6ec0c100@wordpress.org>
Message-ID: <065.a7f0bad23e72a629122fc9f78461dd72@wordpress.org>

#55452: `safecss_filter_attr` removes background-images with URL parameters
--------------------------+-----------------------------
 Reporter:  ryelle        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Formatting    |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  css
--------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * keywords:   => needs-patch
 * milestone:  Awaiting Review => Future Release


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55452#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 22:53:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 22:53:14 -0000
Subject: [wp-trac] [WordPress Trac] #12208: Add Quick Edit To Media
 Library list view
In-Reply-To: <054.00bcba52b0aecdec43d5c3b91601979e@wordpress.org>
References: <054.00bcba52b0aecdec43d5c3b91601979e@wordpress.org>
Message-ID: <069.2e80359e0ded259a7c330eb059cadb5b@wordpress.org>

#12208: Add Quick Edit To Media Library list view
-------------------------------------------------+-------------------------
 Reporter:  queenofdiy                           |       Owner:  (none)
     Type:  feature request                      |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch bulk-reopened 2nd-       |     Focuses:
  opinion                                        |  administration
-------------------------------------------------+-------------------------

Comment (by webcommsat):

 We have this ticket on the agenda for the component bug scrub on Monday 28
 March 2022. Is there anything any of the contributors want to raise for
 this? We will start with looking at whether this issue has been resolved.
 Thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/12208#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 22:56:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 22:56:20 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.dbfb81ccb3d15b827c7743029dd27a1d@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------

Comment (by jrf):

 I tend to agree with @peterwilsoncc here: this should be a "wontfix" as
 this can only happen when a plugin is ''doing it wrong''.

 > The issue isn't so much with what the plugin could do so much as that
 the "plugin_loaded" hook does not behave in a predictable or consistent
 manner.

 That's the case, though, with '''''every single filter''''' in WP, as well
 as with '''''every action using WP global vars'''''.

 Think: a filter provides a `string` and expects a string back, the first
 function filtering returns an array, the second function filtering is
 getting a `TypeError` if they don't do any type checking before using the
 received parameter.

 Also see: https://core.trac.wordpress.org/ticket/51525

 As for the proposed solutions:

 > Wrap the include_once call in a closure (or named function) to isolate
 its variable scope

 I agree with @joyously that is bound to cause problems due to global
 variables not being available and not being explicitly approached as
 global variables. It's the kind of BC-break which will break plenty of
 ''not that well-coded/older'' plugins.

 > If you have to make a change here, I vote for renaming the variable.

 That, again would be a BC-break, albeit smaller. This is a documented
 global variable in WordPress, even though only available in this limited
 context, and changing the name of the variable will:
 1) still not prevent people from overwriting the ''new'' name.
 2) may break plugins relying on the `$plugin` variable being available in
 that context.

 > Update the DocBlock to indicate that this argument has type "mixed" and
 cannot be relied upon.

 That's not a solution, that's turning the problem around and making it
 worse. The documented type is correct and should stay documented as
 `string`. Anything else is giving plugins license to deliberately change
 WP global variables.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 22:59:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 22:59:00 -0000
Subject: [wp-trac] [WordPress Trac] #12684: Add Edit to Bulk Actions
 menu on Categories screen
In-Reply-To: <048.4063e18bb40690d6fb5bd259eeeb7db9@wordpress.org>
References: <048.4063e18bb40690d6fb5bd259eeeb7db9@wordpress.org>
Message-ID: <063.af77f0b7810d094243fc82e4ad62ded7@wordpress.org>

#12684: Add Edit to Bulk Actions menu on Categories screen
-----------------------------+------------------------------------
 Reporter:  jane             |       Owner:  dipalidhole27gmailcom
     Type:  feature request  |      Status:  assigned
 Priority:  normal           |   Milestone:  Future Release
Component:  Quick/Bulk Edit  |     Version:  3.0
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  ui
-----------------------------+------------------------------------

Comment (by webcommsat):

 This ticket is on the agenda for the component bug scrub on Monday 28
 March 2022, 20:00 UTC. Does anyone have an update or can test the
 refreshed patch if this is still needed. @dipalidhole27gmailcom @vinod-
 dalvi Thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/12684#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 23:00:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 23:00:34 -0000
Subject: [wp-trac] [WordPress Trac] #12684: Add Edit to Bulk Actions
 menu on Categories screen
In-Reply-To: <048.4063e18bb40690d6fb5bd259eeeb7db9@wordpress.org>
References: <048.4063e18bb40690d6fb5bd259eeeb7db9@wordpress.org>
Message-ID: <063.57a11132b641c8803610045a87980d16@wordpress.org>

#12684: Add Edit to Bulk Actions menu on Categories screen
-----------------------------+------------------------------------
 Reporter:  jane             |       Owner:  dipalidhole27gmailcom
     Type:  feature request  |      Status:  assigned
 Priority:  normal           |   Milestone:  Future Release
Component:  Quick/Bulk Edit  |     Version:  3.0
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  ui
-----------------------------+------------------------------------

Comment (by webcommsat):

 This ticket is on the agenda for the component bug scrub on Monday 28
 March 2022, 20:00 UTC. Does anyone have an update or can test the
 refreshed patch if this is still needed. @dipalidhole27gmailcom @vinod-
 dalvi Thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/12684#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 23:11:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 23:11:01 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.3a7342ce638678300fddaa06151ab273@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------

Comment (by azouamauriac):

 If we definitely agree to rename the variable here, I think
 [https://prnt.sc/AOZseuQd4awd this both] worth to be renamed...

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 23:12:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 23:12:20 -0000
Subject: [wp-trac] [WordPress Trac] #55411: Deprecated error in
 WordPress 5.9 on PHP 8.1
In-Reply-To: <057.e87e31fe46e8b38d8b6a8b2085d74bb7@wordpress.org>
References: <057.e87e31fe46e8b38d8b6a8b2085d74bb7@wordpress.org>
Message-ID: <072.da6279a7ba3df8557be1ce87d9ba2a2c@wordpress.org>

#55411: Deprecated error in WordPress 5.9 on PHP 8.1
-------------------------------------+------------------------------
 Reporter:  meysamnorouzi            |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  General                  |     Version:  5.9.2
 Severity:  normal                   |  Resolution:
 Keywords:  php81 reporter-feedback  |     Focuses:
-------------------------------------+------------------------------
Changes (by jrf):

 * keywords:   => php81 reporter-feedback


Comment:

 Deprecations are not errors. A lot of WordPress functions all suffer from
 similar issues and we should implement a **proper**, consistent solution
 for all, which is why these issues have not been addressed yet as a
 discussion is needed on the solution direction.

 The only time it would be possible to get these deprecation notices, is if
 these functions are being called with a `null` being passed to a non-
 nullable parameter, which is ''doing it wrong''. More than anything, the
 incorrect function ''call'', should be fixed. Not the function where the
 deprecation is thrown.

 For that a full backtrace of the notices is needed to determine where the
 incorrect function ''call'' is being made.

 As for the deprecations from the `Requests_*` classes, see the dedicated
 ticket about upgrading the external Requests library: #54504

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55411#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 23:16:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 23:16:43 -0000
Subject: [wp-trac] [WordPress Trac] #55313: Fix PHP Plugin
In-Reply-To: <053.c6421cf766a1fb9860c631944634d9b1@wordpress.org>
References: <053.c6421cf766a1fb9860c631944634d9b1@wordpress.org>
Message-ID: <068.03213558889199c4b87af583546c1ae5@wordpress.org>

#55313: Fix PHP Plugin
--------------------------+----------------------
 Reporter:  ppatel821     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.9.1
 Severity:  normal        |  Resolution:  invalid
 Keywords:  close         |     Focuses:
--------------------------+----------------------
Changes (by jrf):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 As @joyously correctly surmised, this is a problem with your theme, not
 with WordPress Core. Please report this to the theme author.

 Also note that the issue IMO is unrelated to the WordPress upgrade you
 mention you did, but is in actual fact related to  a PHP upgrade I suspect
 you've done (or your host did). This is a new deprecation as of PHP 8.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55313#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 23:20:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 23:20:56 -0000
Subject: [wp-trac] [WordPress Trac] #55453: Update Sodium Compat to 1.17.1
 (PHP 8.1 compatibility)
Message-ID: <047.3ce4be26e3b1e349429ff906ba6e05c0@wordpress.org>

#55453: Update Sodium Compat to 1.17.1 (PHP 8.1 compatibility)
--------------------------------+-------------------------------
 Reporter:  jrf                 |      Owner:  (none)
     Type:  task (blessed)      |     Status:  new
 Priority:  normal              |  Milestone:  6.0
Component:  External Libraries  |    Version:  trunk
 Severity:  normal              |   Keywords:  needs-patch php81
  Focuses:                      |
--------------------------------+-------------------------------
 Sodium_Compat 1.17.1 has just been released and includes further
 improvements for PHP 8.1 compatibility.

 The version included with WP should be updated.

 Full details:
 * https://github.com/paragonie/sodium_compat/releases/tag/v1.17.1
 * https://github.com/paragonie/sodium_compat/compare/v1.17.0...v1.17.1

 I've reviewed the diff and would strongly recommend an update at the
 earliest convenience.


 Previously: #48371, #51399, #51925, #53274, #53907
 Related: #54730

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55453>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 23 23:26:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 23 Mar 2022 23:26:24 -0000
Subject: [wp-trac] [WordPress Trac] #12208: Add Quick Edit To Media
 Library list view
In-Reply-To: <054.00bcba52b0aecdec43d5c3b91601979e@wordpress.org>
References: <054.00bcba52b0aecdec43d5c3b91601979e@wordpress.org>
Message-ID: <069.6269acc69931336b0740f38dee9cced2@wordpress.org>

#12208: Add Quick Edit To Media Library list view
-------------------------------------------------+-------------------------
 Reporter:  queenofdiy                           |       Owner:  (none)
     Type:  feature request                      |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch bulk-reopened 2nd-       |     Focuses:
  opinion                                        |  administration
-------------------------------------------------+-------------------------

Comment (by galbaras):

 Quick Edit is definitely not available in Media Library List View on
 WordPress 5.9.2, neither for individual entries nor as a bulk action.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/12208#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 01:24:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 01:24:08 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.5cfb5672f8a1d370932be63527af29ba@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 I logged some [https://github.com/WordPress/wordpress-
 develop/pull/2399#discussion_r833811929 notes on the pull request] using a
 testing plugin to loop through some various sized menus using the old and
 the new code.

 I was seeing the longer query @spacedmonkey documents above but the
 cumulative result of the patch was a positive.

 It would be good to get some feedback from hosts with separate web and
 MySQL servers to make sure that's not a problem.

 Generally, I'm in favour of this going in.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 01:44:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 01:44:25 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.a776c5b05d847633ab58106999a605cd@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "55432.3.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 01:48:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 01:48:18 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "55432.3.diff" removed.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 01:48:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 01:48:18 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.d62908b5cf5ef3dd731bb4026c5a9575@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------
Changes (by SergeyBiryukov):

 * Attachment "55432.3.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 01:49:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 01:49:55 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.8f314971d520cf7f6242afd83600ec54@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
---------------------------+---------------------
 Reporter:  stevegrunwell  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  6.0
Component:  Plugins        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------

Comment (by SergeyBiryukov):

 Replying to [comment:7 jrf]:
 > > If you have to make a change here, I vote for renaming the variable.
 >
 > That, again would be a BC-break, albeit smaller. This is a documented
 global variable in WordPress, even though only available in this limited
 context, and changing the name of the variable will:
 > 1) still not prevent people from overwriting the ''new'' name.
 > 2) may break plugins relying on the `$plugin` variable being available
 in that context.

 Thanks for taking the time to look into this! I might be missing
 something, but I could not find the `$plugin` variable being documented as
 a global anywhere in core, only as a parameter of the `plugin_loaded`
 action, which the renaming should not affect. You're right that it does
 not completely prevent overwriting the new name, however the chance of
 accidentally overwriting a name like `$_wp_plugin_file` would be much
 lower than for `$plugin`.

 [attachment:"55432.3.diff"] is a minor adjustment to more closely follow
 [28644] and address the concern of the `$plugin` variable still being
 available.

 Replying to [comment:8 azouamauriac]:
 > If we definitely agree to rename the variable here, I think
 [https://prnt.sc/AOZseuQd4awd this both] worth to be renamed...

 Good catch, thanks!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 02:11:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 02:11:16 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.cf5f503d149624a6f9e414906d937ed2@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
------------------------------+---------------------
 Reporter:  stevegrunwell     |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  6.0
Component:  Plugins           |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+---------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch => has-patch commit


Comment:

 [attachment:"55432.3.diff"] looks suitable to me and matches the precedent
 in #28102.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 02:28:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 02:28:02 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.e1e98e671daf70e46c4aa392602d80df@wordpress.org>

#55439: Introduce term_exists_args filter
-------------------------------------+---------------------------
 Reporter:  Chouby                   |       Owner:  spacedmonkey
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+---------------------------

Comment (by peterwilsoncc):

 Per note on GitHub, I made a mistake with my naming suggestion yesterday
 but once we have that down I think this is good for commit. I'll hold off
 adding the keyword for now so it doesn't get committed prematurely.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 02:52:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 02:52:49 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.cfa2028e8b0b2e9e1543aa55344da66d@wordpress.org>

#36907: Improved sticky post query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  reopened
 Priority:  normal                    |   Milestone:  6.0
Component:  Query                     |     Version:  3.5
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests commit => has-patch has-unit-tests


Comment:

 Removing commit keyword while the follow up commit is finalised.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 03:14:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 03:14:38 -0000
Subject: [wp-trac] [WordPress Trac] #26746: Avoid translating several
 times post type and taxonomy default labels
In-Reply-To: <050.ffb69c1467709412179c846d3531474f@wordpress.org>
References: <050.ffb69c1467709412179c846d3531474f@wordpress.org>
Message-ID: <065.cd3b1583633cd0ac56ac9f261adcfe8c@wordpress.org>

#26746: Avoid translating several times post type and taxonomy default labels
-------------------------------+-----------------------------
 Reporter:  Chouby             |       Owner:  SergeyBiryukov
     Type:  enhancement        |      Status:  reviewing
 Priority:  normal             |   Milestone:  6.0
Component:  Posts, Post Types  |     Version:  3.0
 Severity:  normal             |  Resolution:
 Keywords:  has-patch early    |     Focuses:  performance
-------------------------------+-----------------------------

Comment (by peterwilsoncc):

 I asked a question on the [https://github.com/WordPress/wordpress-
 develop/pull/2404 linked pull request] about changing the priority of some
 default hooks. It's a minor back-compat break so it would be good to know
 why it's needed so the cost/benefit can be evaluated.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/26746#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 03:16:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 03:16:19 -0000
Subject: [wp-trac] [WordPress Trac] #6479: Encourage people to change
 default tagline
In-Reply-To: <055.e530d469b6d3d46c70a1707e6bd1ead0@wordpress.org>
References: <055.e530d469b6d3d46c70a1707e6bd1ead0@wordpress.org>
Message-ID: <070.5c36ca7e2df6f931545a60e1616c6a36@wordpress.org>

#6479: Encourage people to change default tagline
-------------------------------------------------+-------------------------
 Reporter:  markjaquith                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  2.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-unit-  |     Focuses:
  tests needs-refresh                            |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 @audrasjb Fair, leave that for now and it can be discussed to consider
 further implications.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/6479#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 03:20:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 03:20:58 -0000
Subject: [wp-trac] [WordPress Trac] #38197: Update Pingback function To
 Add Return
In-Reply-To: <052.5dccca3f7b2d0dfeda445aede5477115@wordpress.org>
References: <052.5dccca3f7b2d0dfeda445aede5477115@wordpress.org>
Message-ID: <067.7a798bfe4129d572c2b022cecb859b28@wordpress.org>

#38197: Update Pingback function To Add Return
-------------------------------------------------+-------------------------
 Reporter:  dshanske                             |       Owner:  (none)
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Pings/Trackbacks                     |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch needs-      |     Focuses:
  unit-tests                                     |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * owner:  nathanatmoz => (none)


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38197#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 03:43:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 03:43:10 -0000
Subject: [wp-trac] [WordPress Trac] #55455: clean_site_details_cache()
 doesn't clean all site caches
Message-ID: <048.81ee7aa7953fb70d778fafbf2abf5df8@wordpress.org>

#55455: clean_site_details_cache() doesn't clean all site caches
--------------------------------+-----------------------------
 Reporter:  dd32                |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  low                 |  Milestone:  Awaiting Review
Component:  Networks and Sites  |    Version:  4.7
 Severity:  minor               |   Keywords:
  Focuses:  multisite           |
--------------------------------+-----------------------------
 clean_site_details_cache() clear's two caches:
 {{{
         wp_cache_delete( $site_id, 'site-details' );
         wp_cache_delete( $site_id, 'blog-details' );
 }}}

 https://github.com/WordPress/wordpress-
 develop/blob/0b800e21c311e302824e4a025946a6fdb4f6c794/src/wp-includes/ms-
 blogs.php#L322-L337

 But there's a third used within `get_blog_details()` that's closely
 related to those two caches:
 {{{
         if ( $get_all ) {
                 $details = wp_cache_get( $blog_id . 'short', 'blog-
 details' );
         } else {
                 $details = wp_cache_get( $blog_id, 'blog-details' );
 }}}

 One could argue that the `blog-details` caches are not related to the
 `site-details` caches, but one would expect that if it clears some of
 them, that it'll clear all of them.

 `clean_blog_cache()` is a
 [https://developer.wordpress.org/reference/functions/clean_blog_cache/
 much more comprehensive function] though:
 {{{
         wp_cache_delete( $blog_id, 'sites' );
         wp_cache_delete( $blog_id, 'site-details' );
         wp_cache_delete( $blog_id, 'blog-details' );
         wp_cache_delete( $blog_id . 'short', 'blog-details' );
         wp_cache_delete( $domain_path_key, 'blog-lookup' );
         wp_cache_delete( $domain_path_key, 'blog-id-cache' );
         wp_cache_delete( $blog_id, 'blog_meta' );
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55455>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 05:14:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 05:14:03 -0000
Subject: [wp-trac] [WordPress Trac] #43668: Image cropping fails for
 many PHP locales, if set
In-Reply-To: <050.84997cbd24df2d38e0626dca342884b6@wordpress.org>
References: <050.84997cbd24df2d38e0626dca342884b6@wordpress.org>
Message-ID: <065.f1420cc515d0f13fb868a48e8596aca4@wordpress.org>

#43668: Image cropping fails for many PHP locales, if set
--------------------------+------------------------------
 Reporter:  knutsp        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |     Focuses:  javascript
--------------------------+------------------------------

Comment (by marcelschulz):

 This bug still exists as of March 2022 (5.9.2).

 Have you ever found a solution to it?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43668#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 09:27:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 09:27:13 -0000
Subject: [wp-trac] [WordPress Trac] #55456: Double escaping wp_user-settings
Message-ID: <053.4e95668003a2859da7231085e66ad927@wordpress.org>

#55456: Double escaping wp_user-settings
--------------------------+-----------------------------
 Reporter:  phatkoala     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Users         |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Fresh install of WordPress with no plugins and using default Twenty Twenty
 Two theme.

 Either directly insert test data;
 {{{
 INSERT INTO wp_usermeta (user_id, meta_key, meta_value) VALUES (1,
 'wp_user-settings', 'foo=1&bar=1');
 }}}

 Or activate this plugin;
 {{{
 <?php
 /*
 Plugin Name: Ampersand Test
 */
 register_activation_hook( __FILE__, function(){
     set_user_setting( 'foo', 1 );
     set_user_setting( 'bar', 1 );
 } );
 }}}

 The name of the attributes and their values are completely arbitrary and
 have no impact on the behaviour.

 Now go to your "Profile" page (/wp-admin/profile.php) and press "Update
 Profile".  Wait 5 seconds and repeat.

 The value of wp-user_settings in the database and COOKIE is being double
 escaped (escaped on read and escaped on write).

 Therefore the value of wp-user_settings does this;
  - foo=1&bar=1
  - foo=1&ampbar=1
  - foo=1&ampampbar=1
  - foo=1&ampampampbar=1
  - and so forth

 Once the value of wp-user_settings becomes too long and/or combined with a
 user using the same browser with multiple logins, the length of the
 COOKIE(s) will become too large and the request header will be rejected by
 Apache/Nginx.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55456>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 10:21:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 10:21:41 -0000
Subject: [wp-trac] [WordPress Trac] #55457: Function media_handle_sideload
 doesn't return with some pdf files due to Imagick
Message-ID: <054.38ed8e868f783744c66bfed0a71653de@wordpress.org>

#55457: Function media_handle_sideload doesn't return with some pdf files due to
Imagick
--------------------------+-----------------------------
 Reporter:  alceomazza    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Upload        |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 I'm trying to upload procedurally some media with `media_handle_sideload`,
 but some pdf files cause the execution flow to froze without
 `media_handle_sideload` returning a value nor launching an `Exception`.
 This happens when the Imagick module is installed.

 === Environment
 * **OS**: CentOS 7
 * **PHP Version**: 7.4.28
 * **WordPress Version**: 5.9.2
 * **Imagick Version**: 6.9.10-68

 === Debug snippet
 The bug can be verified calling the function `alceo_handle_media_debug`
 {{{#!php
 <?php

 function alceo_handle_media_debug() {
     alceo_handle_media( 'https://life365.s3.eu-
 central-1.amazonaws.com/IT/p/11822/file/FilamentClear_2018.pdf' );
 }

 function alceo_handle_media( $url ) {
     $path_info = pathinfo( parse_url( $url )['path'] );
     $file_type = wp_check_filetype( $path_info['basename'] );

     if ( ! $file_type['ext'] ) {
         return;
     }

     require_once( ABSPATH . 'wp-admin/includes/media.php' );
     require_once( ABSPATH . 'wp-admin/includes/file.php' );
     require_once( ABSPATH . 'wp-admin/includes/image.php' );

     $media_title = $path_info['basename'];

     $tmp_name = download_url( $url );

     if ( is_wp_error( $tmp_name ) ) {
         error_log( print_r( $tmp_name, true ) );
     }

     $file = array(
         'name' => $media_title,
         'tmp_name' => $tmp_name,
     );

     try {
         $media_id = media_handle_sideload(
             $file, 0, null, array(
                 'post_author' => 0,
                 'post_name' => sanitize_title( $media_title ),
             )
         );
     } catch ( \Exception $e ) {
         error_log( print_r( $e, true ) );
     }

     if ( is_wp_error( $media_id ) ) {
         error_log( print_r( $tmp_name, true ) );
     }
 }
 }}}

 === Testing
 I've tried to test adding these `error_log` lines into method
 `pdf_load_source` of class `WP_Image_Editor_Imagick` (file `wp-includes
 /class-wp-image-editor-imagick.php`)
 {{{#!php
 <?php

 class WP_Image_Editor_Imagick extends WP_Image_Editor {

     // ...

     protected function pdf_load_source() {
         error_log( "Into pdf_load_source" );
         $filename = $this->pdf_setup();
         error_log( "Filename: " . print_r( $filename, true ) );

         if ( is_wp_error( $filename ) ) {
             return $filename;
         }

         try {
             error_log( "Trying with " . print_r( $this->image, true ) );
             // When generating thumbnails from cropped PDF pages,
 Imagemagick uses the uncropped
             // area (resulting in unnecessary whitespace) unless the
 following option is set.
             $this->image->setOption( 'pdf:use-cropbox', true );
             error_log( "Option use cropbox true" );

             // Reading image after Imagick instantiation because
 `setResolution`
             // only applies correctly before the image is read.
             $this->image->readImage( $filename );
             error_log( "Image read tried" );
         } catch ( Exception $e ) {
             error_log( "Catched" );
             // Attempt to run `gs` without the `use-cropbox` option. See
 #48853.
             $this->image->setOption( 'pdf:use-cropbox', false );
             error_log( "Option use cropbox false" . print_r( '', true ) );

             $this->image->readImage( $filename );
             error_log( "Image read" . print_r( '', true ) );
         }

         return true;
     }

     // ...
 }
 }}}

 with this result in `debug.log`:

 {{{
 [23-Mar-2022 14:36:23 UTC] Into pdf_load_source
 [23-Mar-2022 14:36:23 UTC] Filename: /<host_path>/wp-
 content/uploads/2022/03/Product-XXXXX-FilamentClear_2018-1.pdf[0]
 [23-Mar-2022 14:36:23 UTC] Trying with Imagick Object
 (
 )

 [23-Mar-2022 14:36:23 UTC] Option use cropbox true

 }}}

 And none of the following `error_log` prints coming after this last line.

 === Other details
 * This happens with some pdf files (the one from the url in the code being
 one of them)
 * I've tried changing php version to the latest 8.1, but the issue
 persists

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55457>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 10:25:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 10:25:07 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.648742f91b6d3dcb7b8756ccbe54e52c@wordpress.org>

#55439: Introduce term_exists_args filter
-------------------------------------+---------------------------
 Reporter:  Chouby                   |       Owner:  spacedmonkey
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Taxonomy                 |     Version:  trunk
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+---------------------------
Changes (by spacedmonkey):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52987" 52987]:
 {{{
 #!CommitTicketReference repository="" revision="52987"
 Taxonomy: Introduce `term_exists_default_query_args` filter.

 In [52921] `term_exists` was converted to use `get_terms`. This change
 adds a filter called `term_exists_default_query_args`
 to the `term_exists` function to allow developers to modify the arguments
 passed to `get_terms` before the query is run.

 Props Chouby, Spacedmonkey, peterwilsoncc.
 Fixes #55439.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 10:29:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 10:29:23 -0000
Subject: [wp-trac] [WordPress Trac] #36949: Term exists should use
 get_terms internally
In-Reply-To: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
References: <056.1a2e8f10898bbe1a60a5bf48d1b66f05@wordpress.org>
Message-ID: <071.fcea4309b19f27497effcc9208844992@wordpress.org>

#36949: Term exists should use get_terms internally
----------------------------+---------------------------
 Reporter:  spacedmonkey    |       Owner:  spacedmonkey
     Type:  enhancement     |      Status:  closed
 Priority:  normal          |   Milestone:  6.0
Component:  Taxonomy        |     Version:  2.3
 Severity:  normal          |  Resolution:  fixed
 Keywords:  needs-dev-note  |     Focuses:  performance
----------------------------+---------------------------

Comment (by spacedmonkey):

 #55439 was committed in [52987].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36949#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 10:30:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 10:30:07 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.5ec8803d920bf7d04aae26840018ff8d@wordpress.org>

#55439: Introduce term_exists_args filter
--------------------------------------+---------------------------
 Reporter:  Chouby                    |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  trunk
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch needs-dev-note  |     Focuses:
--------------------------------------+---------------------------
Changes (by spacedmonkey):

 * keywords:  has-patch needs-refresh => has-patch needs-dev-note


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 10:50:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 10:50:39 -0000
Subject: [wp-trac] [WordPress Trac] #54672: Deprecated errors on PHP 8.1
In-Reply-To: <049.769106222dfb2f1fbb9791a62b1556f6@wordpress.org>
References: <049.769106222dfb2f1fbb9791a62b1556f6@wordpress.org>
Message-ID: <064.486d15b5d20cfda020e523283f238e34@wordpress.org>

#54672: Deprecated errors on PHP 8.1
--------------------------+------------------------
 Reporter:  okvee         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.9
 Severity:  normal        |  Resolution:  duplicate
 Keywords:  php81         |     Focuses:
--------------------------+------------------------

Comment (by hyperpolymath):

 Thanks - I see the point about them not being plugin specific, and I agree
 it is php8.1 but does the error not suggest in this that these are just
 instantly fixed in the plugin (if only temporarily) by a compatibility fix
 with the formatting of the call the plugin is making to get the data from
 WP in the wp-includes directory. Each line seems to be just asking for it
 to be appropriately made, so far as I can see, with a qualifier of void,
 mixed or bool as appropriate to the call, rather than what I am assuming
 is an unspecified call from the plugin. Although, I will admit, php is not
 my programming language and I am new to wp, so I might be misreading what
 is showing here.

 If it is not as simple, that's fine, but do I need to do anything to
 mitigate a known or obvious threat, or is using the plugin in the interim
 fine?

 thank you,

 Jonathan

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54672#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 11:10:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 11:10:41 -0000
Subject: [wp-trac] [WordPress Trac] #55456: Double escaping
 wp_user-settings
In-Reply-To: <053.4e95668003a2859da7231085e66ad927@wordpress.org>
References: <053.4e95668003a2859da7231085e66ad927@wordpress.org>
Message-ID: <068.e248e704ac17f0e97bf52f16f5d81346@wordpress.org>

#55456: Double escaping wp_user-settings
--------------------------+------------------------------
 Reporter:  phatkoala     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Users         |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by azouamauriac):

 * keywords:   => needs-patch


Comment:

 Hi @phatkoala welcome to trac! Thanks for the report and the steps to
 reproduce it. I'm able to reproduce it.

 Hope it will be fixed ASAP.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55456#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 11:18:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 11:18:01 -0000
Subject: [wp-trac] [WordPress Trac] #55458: Media loading issue and got
 error: The search API provider is currently experiencing an error. Try
 again in a few seconds
Message-ID: <057.2371638112d232ba9b62cb89fa0db294@wordpress.org>

#55458: Media loading issue and got error: The search API provider is currently
experiencing an error. Try again in a few seconds
---------------------------+------------------------------------------
 Reporter:  Suresh Shinde  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Media          |    Version:  5.9.2
 Severity:  normal         |   Keywords:  has-screenshots has-dev-note
  Focuses:                 |
---------------------------+------------------------------------------
 Produced error at https://wordpress.org/patterns/new-pattern/

 If I searched particular image by keyword for example "profile" it shows
 pagination 1 to 118.

 If I clicked page 1, page 2, page 3 and last page it shows same images as
 in page 2 and page 118. Sometime it shows 'No results found for "profile"'

 For more information here are screenshots;
 [[Image()]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55458>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 11:19:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 11:19:11 -0000
Subject: [wp-trac] [WordPress Trac] #55458: Media loading issue and got
 error: The search API provider is currently experiencing an error. Try
 again in a few seconds
In-Reply-To: <057.2371638112d232ba9b62cb89fa0db294@wordpress.org>
References: <057.2371638112d232ba9b62cb89fa0db294@wordpress.org>
Message-ID: <072.69858f708fa15cbdf9cf44e26aab5147@wordpress.org>

#55458: Media loading issue and got error: The search API provider is currently
experiencing an error. Try again in a few seconds
------------------------------------------+------------------------------
 Reporter:  Suresh Shinde                 |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  Awaiting Review
Component:  Media                         |     Version:  5.9.2
 Severity:  normal                        |  Resolution:
 Keywords:  has-screenshots has-dev-note  |     Focuses:
------------------------------------------+------------------------------
Changes (by Suresh Shinde):

 * Attachment "patterns-openverse-API.png" added.

 Search API issue

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55458>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 11:19:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 11:19:55 -0000
Subject: [wp-trac] [WordPress Trac] #55458: Media loading issue and got
 error: The search API provider is currently experiencing an error. Try
 again in a few seconds
In-Reply-To: <057.2371638112d232ba9b62cb89fa0db294@wordpress.org>
References: <057.2371638112d232ba9b62cb89fa0db294@wordpress.org>
Message-ID: <072.e66080285aa93796063decb2c8d5ddc6@wordpress.org>

#55458: Media loading issue and got error: The search API provider is currently
experiencing an error. Try again in a few seconds
------------------------------------------+------------------------------
 Reporter:  Suresh Shinde                 |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  Awaiting Review
Component:  Media                         |     Version:  5.9.2
 Severity:  normal                        |  Resolution:
 Keywords:  has-screenshots has-dev-note  |     Focuses:
------------------------------------------+------------------------------
Changes (by Suresh Shinde):

 * Attachment "issue-2.png" added.

 After clicking on pagination, no image issue

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55458>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 11:20:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 11:20:40 -0000
Subject: [wp-trac] [WordPress Trac] #55458: Media loading issue and got
 error: The search API provider is currently experiencing an error. Try
 again in a few seconds
In-Reply-To: <057.2371638112d232ba9b62cb89fa0db294@wordpress.org>
References: <057.2371638112d232ba9b62cb89fa0db294@wordpress.org>
Message-ID: <072.f751187e4cc0abc29963dbb6fd44ab41@wordpress.org>

#55458: Media loading issue and got error: The search API provider is currently
experiencing an error. Try again in a few seconds
------------------------------------------+------------------------------
 Reporter:  Suresh Shinde                 |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  Awaiting Review
Component:  Media                         |     Version:  5.9.2
 Severity:  normal                        |  Resolution:
 Keywords:  has-screenshots has-dev-note  |     Focuses:
------------------------------------------+------------------------------
Changes (by Suresh Shinde):

 * Attachment "step2.png" added.

 Same Images after clicking on different page

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55458>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 11:21:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 11:21:04 -0000
Subject: [wp-trac] [WordPress Trac] #55458: Media loading issue and got
 error: The search API provider is currently experiencing an error. Try
 again in a few seconds
In-Reply-To: <057.2371638112d232ba9b62cb89fa0db294@wordpress.org>
References: <057.2371638112d232ba9b62cb89fa0db294@wordpress.org>
Message-ID: <072.8559ddcadcde46c1d64328a6017f24a1@wordpress.org>

#55458: Media loading issue and got error: The search API provider is currently
experiencing an error. Try again in a few seconds
------------------------------------------+------------------------------
 Reporter:  Suresh Shinde                 |       Owner:  (none)
     Type:  defect (bug)                  |      Status:  new
 Priority:  normal                        |   Milestone:  Awaiting Review
Component:  Media                         |     Version:  5.9.2
 Severity:  normal                        |  Resolution:
 Keywords:  has-screenshots has-dev-note  |     Focuses:
------------------------------------------+------------------------------
Changes (by Suresh Shinde):

 * Attachment "last.png" added.

 Same Images after clicking on different page

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55458>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 11:48:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 11:48:03 -0000
Subject: [wp-trac] [WordPress Trac] #54672: Deprecated errors on PHP 8.1
In-Reply-To: <049.769106222dfb2f1fbb9791a62b1556f6@wordpress.org>
References: <049.769106222dfb2f1fbb9791a62b1556f6@wordpress.org>
Message-ID: <064.16a97eca7e314d227b7533681d4cc87a@wordpress.org>

#54672: Deprecated errors on PHP 8.1
--------------------------+------------------------
 Reporter:  okvee         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.9
 Severity:  normal        |  Resolution:  duplicate
 Keywords:  php81         |     Focuses:
--------------------------+------------------------

Comment (by jrf):

 Replying to [comment:4 hyperpolymath]:
 > Thanks - I see the point about them not being plugin specific, and I
 agree it is php8.1 but does the error not suggest in this that these are
 just instantly fixed in the plugin (if only temporarily) by a
 compatibility fix with the formatting of the call the plugin is making to
 get the data from WP in the wp-includes directory. Each line seems to be
 just asking for it to be appropriately made, so far as I can see, with a
 qualifier of void, mixed or bool as appropriate to the call, rather than
 what I am assuming is an unspecified call from the plugin. Although, I
 will admit, php is not my programming language and I am new to wp, so I
 might be misreading what is showing here.
 >
 > If it is not as simple, that's fine, but do I need to do anything to
 mitigate a known or obvious threat, or is using the plugin in the interim
 fine?


 @hyperpolymath You seem to be talking about something different than the
 above as you refer multiple times to "the plugin". Trac is not for plugin
 support or plugin bug fixes. Trac is for WordPress Core, so I suggest you
 ask your questions about whatever plugin you're talking about in the
 support forum of the plugin.


 And just so you know: no, these shouldn't be fixed by type casting at the
 point of deprecation. In most cases, the ''function call'' passing the
 incorrectly typed data should be fixed, not the function ''receiving'' the
 data. This involves backtraces and figuring out where exactly the
 incorrect function call (or calls) is being made.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54672#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 13:29:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 13:29:23 -0000
Subject: [wp-trac] [WordPress Trac] #54672: Deprecated errors on PHP 8.1
In-Reply-To: <049.769106222dfb2f1fbb9791a62b1556f6@wordpress.org>
References: <049.769106222dfb2f1fbb9791a62b1556f6@wordpress.org>
Message-ID: <064.72b5b8696f82f006713413655da91a90@wordpress.org>

#54672: Deprecated errors on PHP 8.1
--------------------------+------------------------
 Reporter:  okvee         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.9
 Severity:  normal        |  Resolution:  duplicate
 Keywords:  php81         |     Focuses:
--------------------------+------------------------

Comment (by hyperpolymath):

 thanks that clarifies the situation, and is really useful as I was a bit
 confused about why I was sent here, but makes more sense now. And yes, of
 course that makes sense re the calls, although what is called and is sent
 are inherently linked and both sides have a role and decision as to what
 happens there. If the issue is that data is stored badly, but you are
 careful about the query it should be possible to extract it. That, of
 course, does not fix the way it is stored, but that is out of your
 control, and I agree. And, of course, much better that it is fixed where
 it originates rather than passing that off outwards.

 I presumed that in any case, these decisions are made in some kind of
 negotiation in a developers community for plugin developers anyway, but I
 am not experienced with or familiar with how this works her. If plugins
 report errors as if they are with your plug in, then it does them no
 favours in themselves, but also if people put out that is where a problem
 seems to have occurred, and some breach or problem happens, the
 reputational hit can end up unfairly shared.

 Anyway, I hope it was useful highlighting it, and if not, my apologies.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54672#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 13:33:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 13:33:40 -0000
Subject: [wp-trac] [WordPress Trac] #53115: Twenty Twenty: number inputs
 have too much padding
In-Reply-To: <058.91e6ff0735e7e5ad214924238f7ad1a6@wordpress.org>
References: <058.91e6ff0735e7e5ad214924238f7ad1a6@wordpress.org>
Message-ID: <073.cbabaecc156ec3af780525e7ac4e1f90@wordpress.org>

#53115: Twenty Twenty: number inputs have too much padding
-------------------------------------+--------------------------
 Reporter:  helgatheviking           |       Owner:  sabernhardt
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css
-------------------------------------+--------------------------

Comment (by ugyensupport):

 Tested with browsers, it looks good.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53115#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 14:07:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 14:07:13 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.cf31a0e567c7fb55bb69e7d7e193ad20@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots has-testing-info                   |  accessibility
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * keywords:  has-patch has-unit-tests has-screenshots => has-patch has-
     unit-tests has-screenshots has-testing-info


Comment:

 = Test Report

 Patch tested: [https://github.com/WordPress/wordpress-develop/pull/2441 PR
 2441]

 Env:
 - OS: macOS Big Sur
 - Localhost: wp-env
 - WordPress: `trunk`
 - Browser: Firefox and Edge
 - Plugins: none
 - Theme: Twenty Twenty

 == Testing Steps

 1. Activate Twenty Twenty or any other non-block theme.
 2. Go to Media > Library.
 3. Upload at least one image. (In my case, I uploaded 4 different images
 with different metadata to pre-populate the properties.)
 4. For certain tests, set the attachment properties for alt test, title,
 caption, and/or description.
 5. Go to the Appearance > Customize > Site Identity.
 6. In the Logo section, click "Select Logo".
 7. Select an image.
 8. Click the "Select" button. Expected behavior: Crop modal opens.
 9. Select a region to crop.
 10. Click the "Crop image" button.
 11. Click "Publish"* and close the Customizer.
 12. Go to Media > Library.
 13. Click on the cropped logo image to open its properties screen. Test:
 Check that the properties are properly populated. Expected behavior:
    * Title:
        * Is `cropped-[filename]` ''when'' the original image's title is
 the filename (meaning the image did not have a title in its metadata when
 uploaded or the title property wasn't manually changed in step 4).
        * Is the same as the original image's title when the original title
 is not the filename (meaning the image either has a title in its metadata
 or the title property was manually changed in step 4).
    * Alt text: matches the original image's alt text property.
    * Caption: matches the original image's caption property.
    * Description:
        * Cropped image's URL ''when'' the original image's description
 property is empty.
        * Else, matches the original image's description property.

 == Test Results

 Scenarios:

 ||= Original Title =||= Original Alt =||= Original Caption =||= Original
 Description =||= Cropped Correct? =||
 || filename ||  ||  || || ✅ ||
 || filename || alt ||  || || ✅ ||
 || filename ||  || caption || || ✅ ||
 || filename ||  ||  || description || ✅ ||
 || filename || alt || caption || || ✅ ||
 || filename || alt || || description || ✅ ||
 || filename || alt || caption || description || ✅ ||
 || title ||  ||  || || ✅ ||
 || title || alt ||  || || ✅ ||
 || title ||  || caption || || ✅ ||
 || title ||  ||  || description || ✅ ||
 || title || alt || caption || || ✅ ||
 || title || alt || || description || ✅ ||
 || title || alt || caption || description || ✅ ||

 == Summary

 - Able to reproduce the reported issue ✅
 - After applying the patch and tested each of the scenarios, patch works
 as expected ✅

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:31>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 14:11:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 14:11:20 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.eb070252d5ae9a2e2800a3dfab74e760@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots has-testing-info                   |  accessibility
-------------------------------------------------+-------------------------

Comment (by hellofromTonya):

 [https://github.com/WordPress/wordpress-develop/pull/2441/ PR 2441] LGTM
 for pre-populating cropped file properties from the original image.
 Approved the PR.

 `commit` is pending feedback from @flixos90 and @Clorith about changing
 the title and description's existing behavior ([#comment:29 see comment 29
 above]).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 14:46:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 14:46:30 -0000
Subject: [wp-trac] [WordPress Trac] #54035: Update Jcrop to the latest
 version
In-Reply-To: <058.77f0721436c76442699c4ef03e0313ad@wordpress.org>
References: <058.77f0721436c76442699c4ef03e0313ad@wordpress.org>
Message-ID: <073.fa06d219f75f09399ae5c86356ea138d@wordpress.org>

#54035: Update Jcrop to the latest version
-------------------------------------------------+-------------------------
 Reporter:  Hareesh Pillai                       |       Owner:
                                                 |  davidbaumwald
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  External Libraries                   |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch commit      |     Focuses:
  assigned-for-commit                            |
-------------------------------------------------+-------------------------
Changes (by davidbaumwald):

 * owner:  (none) => davidbaumwald
 * status:  new => accepted


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54035#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 14:52:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 14:52:28 -0000
Subject: [wp-trac] [WordPress Trac] #54035: Update Jcrop to the latest
 version
In-Reply-To: <058.77f0721436c76442699c4ef03e0313ad@wordpress.org>
References: <058.77f0721436c76442699c4ef03e0313ad@wordpress.org>
Message-ID: <073.f0ba2f04b819ff1b3de101ebe5040809@wordpress.org>

#54035: Update Jcrop to the latest version
-------------------------------------------------+-------------------------
 Reporter:  Hareesh Pillai                       |       Owner:
                                                 |  davidbaumwald
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  External Libraries                   |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch commit      |     Focuses:
  assigned-for-commit                            |
-------------------------------------------------+-------------------------

Comment (by karpstrucking):

 side note, this will prompt a required change to the developer code
 reference:
 https://developer.wordpress.org/reference/functions/wp_enqueue_script
 /#default-scripts-and-js-libraries-included-and-registered-by-wordpress

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54035#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 14:55:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 14:55:44 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.28dd0bd4901c17cfa98733c7bb041274@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
--------------------------------------+------------------------
 Reporter:  pbearne                   |       Owner:  flixos90
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+------------------------

Comment (by pbearne):

 PR refreshed with review changes

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 15:18:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 15:18:45 -0000
Subject: [wp-trac] [WordPress Trac] #55453: Update Sodium Compat to
 1.17.1 (PHP 8.1 compatibility)
In-Reply-To: <047.3ce4be26e3b1e349429ff906ba6e05c0@wordpress.org>
References: <047.3ce4be26e3b1e349429ff906ba6e05c0@wordpress.org>
Message-ID: <062.55478c9bbdccd8aba3600f68f2ae2647@wordpress.org>

#55453: Update Sodium Compat to 1.17.1 (PHP 8.1 compatibility)
--------------------------------+-----------------------------
 Reporter:  jrf                 |       Owner:  SergeyBiryukov
     Type:  task (blessed)      |      Status:  closed
 Priority:  normal              |   Milestone:  6.0
Component:  External Libraries  |     Version:  trunk
 Severity:  normal              |  Resolution:  fixed
 Keywords:  needs-patch php81   |     Focuses:
--------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52988" 52988]:
 {{{
 #!CommitTicketReference repository="" revision="52988"
 Upgrade/Install: Update sodium_compat to v1.17.1.

 The latest version of sodium_compat includes further improvements for PHP
 8.1 compatibility.

 Release notes:
 https://github.com/paragonie/sodium_compat/releases/tag/v1.17.1

 A full list of changes in this update can be found on GitHub:
 https://github.com/paragonie/sodium_compat/compare/v1.17.0...v1.17.1

 Follow-up to [49741], [51002], [51591].

 Props jrf, paragoninitiativeenterprises.
 Fixes #55453.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55453#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 17:42:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 17:42:37 -0000
Subject: [wp-trac] [WordPress Trac] #55433: Twenty Twenty-Two: Implement
 alternate json files
In-Reply-To: <050.99ce75ea0b7ae06ba452225ad2d4e6ee@wordpress.org>
References: <050.99ce75ea0b7ae06ba452225ad2d4e6ee@wordpress.org>
Message-ID: <065.7e4479809bc991418a8740dcd1f94345@wordpress.org>

#55433: Twenty Twenty-Two: Implement alternate json files
---------------------------------------------+---------------------
 Reporter:  kjellr                           |       Owner:  (none)
     Type:  enhancement                      |      Status:  new
 Priority:  normal                           |   Milestone:  6.0
Component:  Bundled Theme                    |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  needs-design-feedback has-patch  |     Focuses:
---------------------------------------------+---------------------

Comment (by kjellr):

 A quick update on this effort:

 The theme.json files have been built in the linked PR. Technically, we are
 blocked by two issues:

 - Webfonts declared in styles variants are not loaded:
 https://github.com/WordPress/gutenberg/issues/39702
 - Duotone does not render in the site editor:
 https://github.com/WordPress/gutenberg/issues/35331

 From a design perspective, there's some followup work needed as well:

 In order to fully showcase the possibilities here, I'd like to work on
 pushing each of the style variations apart just a bit more. Maybe
 adjusting some of the colors that are similar to each other, adjusting
 some font sizes and spacing, etc. I think this update (and feature) will
 be showcased in the best light if we can make each option feel totally
 transformative — almost like a theme switch. That'll show off the
 possibilities of the feature really nicely.

 I'll keep exploring next week along those lines, but in the meantime,
 here's a quick GIF of the current state, running against Gutenberg trunk:

 [[Image(https://cldup.com/muNykJAaLs.gif)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55433#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 19:41:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 19:41:40 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs
 file
In-Reply-To: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
References: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
Message-ID: <064.c44745d78a8f7d33da51e8e9392cc830@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
-------------------------+------------------------------
 Reporter:  helen        |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------------------

Comment (by helen):

 @costdev Thanks for taking a look! I think review comments and suggestions
 on the PR will work great.

 I hadn't really thought a whole lot about the "MVP" point of this - I
 think your instinct is right, we can get these pinking shears and PHPCS
 ones verified and then commit this, and then work on adding coding
 standards ones in a second pass. However, before settling on that, does
 anybody have a sense of how many coding standards-type commits there are?
 A rough estimate based on keyword searches of commits is good enough.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 20:05:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 20:05:55 -0000
Subject: [wp-trac] [WordPress Trac] #54035: Update Jcrop to the latest
 version
In-Reply-To: <058.77f0721436c76442699c4ef03e0313ad@wordpress.org>
References: <058.77f0721436c76442699c4ef03e0313ad@wordpress.org>
Message-ID: <073.b0593fc5203bef5a5b62a1f168d6875f@wordpress.org>

#54035: Update Jcrop to the latest version
-------------------------------------------------+-------------------------
 Reporter:  Hareesh Pillai                       |       Owner:
                                                 |  davidbaumwald
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  External Libraries                   |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  good-first-bug has-patch commit      |     Focuses:
  assigned-for-commit                            |
-------------------------------------------------+-------------------------
Changes (by davidbaumwald):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52989" 52989]:
 {{{
 #!CommitTicketReference repository="" revision="52989"
 External Libraries: Update Jcrop to version 0.9.15.

 For a full list of changes, see
 https://github.com/tapmodo/Jcrop/compare/v0.9.12...v0.9.15.

 This change also adds a comment in `script-loader.php` indicating that
 this library is no longer used by core.

 Follow-up to [10846], [10863], [11015], [21633], [25549].

 Props hareesh-pillai, karpstrucking, SergeyBiryukov.
 Fixes #54035.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54035#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 20:23:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 20:23:39 -0000
Subject: [wp-trac] [WordPress Trac] #50866: Media Uploader Blows Up File
 Sizes
In-Reply-To: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
References: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
Message-ID: <063.247461c41cfc9e1a48e834b45cd62179@wordpress.org>

#50866: Media Uploader Blows Up File Sizes
-------------------------------------+-------------------------------------
 Reporter:  hvar                     |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4.2
 Severity:  major                    |  Resolution:
 Keywords:  has-patch has-unit-      |     Focuses:  administration,
  tests dev-feedback needs-testing   |  performance
  has-testing-info                   |
-------------------------------------+-------------------------------------
Changes (by costdev):

 * Attachment "50866.2.diff" added.

 Patch refreshed against trunk.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50866>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 20:28:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 20:28:26 -0000
Subject: [wp-trac] [WordPress Trac] #50866: Media Uploader Blows Up File
 Sizes
In-Reply-To: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
References: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
Message-ID: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>

#50866: Media Uploader Blows Up File Sizes
-------------------------------------+-------------------------------------
 Reporter:  hvar                     |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4.2
 Severity:  major                    |  Resolution:
 Keywords:  has-patch has-unit-      |     Focuses:  administration,
  tests dev-feedback needs-testing   |  performance
  has-testing-info                   |
-------------------------------------+-------------------------------------
Changes (by costdev):

 * Attachment "50866.2.diff" removed.

 Patch refreshed against trunk.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50866>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 20:28:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 20:28:26 -0000
Subject: [wp-trac] [WordPress Trac] #50866: Media Uploader Blows Up File
 Sizes
In-Reply-To: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
References: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
Message-ID: <063.1d25f05a172789336012fffdc1216958@wordpress.org>

#50866: Media Uploader Blows Up File Sizes
-------------------------------------+-------------------------------------
 Reporter:  hvar                     |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4.2
 Severity:  major                    |  Resolution:
 Keywords:  has-patch has-unit-      |     Focuses:  administration,
  tests dev-feedback needs-testing   |  performance
  has-testing-info                   |
-------------------------------------+-------------------------------------
Changes (by costdev):

 * Attachment "50866.2.diff" added.

 Patch refreshed against trunk.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50866>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 20:29:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 20:29:13 -0000
Subject: [wp-trac] [WordPress Trac] #50866: Media Uploader Blows Up File
 Sizes
In-Reply-To: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
References: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
Message-ID: <063.7981a023f2389b6758d72f651de6e3c2@wordpress.org>

#50866: Media Uploader Blows Up File Sizes
-------------------------------------+-------------------------------------
 Reporter:  hvar                     |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4.2
 Severity:  major                    |  Resolution:
 Keywords:  has-patch has-unit-      |     Focuses:  administration,
  tests dev-feedback needs-testing   |  performance
  has-testing-info                   |
-------------------------------------+-------------------------------------

Comment (by costdev):

 - Patch has been refreshed against `trunk`.
 - Added `$message` parameter to the unit test's assertions.
 - The unit tests appear to be failing on my end.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50866#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 20:38:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 20:38:59 -0000
Subject: [wp-trac] [WordPress Trac] #53485: completing coverage for
 wp_date()
In-Reply-To: <051.6b3f2d0c983a9dc116c5291f00492814@wordpress.org>
References: <051.6b3f2d0c983a9dc116c5291f00492814@wordpress.org>
Message-ID: <066.210af94a00a1e99eb859fbb8f2c26aec@wordpress.org>

#53485: completing coverage for wp_date()
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  hellofromTonya
     Type:  defect (bug)              |      Status:  accepted
 Priority:  normal                    |   Milestone:  6.0
Component:  Date/Time                 |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-unit-tests has-patch  |     Focuses:
--------------------------------------+-----------------------------

Comment (by megphillips91):

 I'd like to help. I realized that I need a way to get wp_date but just the
 month, or just the date, or just the year. In my research, I do not think
 is currently supported, but could be fairly easy to implement as an
 enhancement. I think I can help with this and would like to if you would
 like a hand. Please let me know,

 Meg

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53485#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 21:35:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 21:35:40 -0000
Subject: [wp-trac] [WordPress Trac] #48116: Proposal: Tracking PHP
 Extension Usage
In-Reply-To: <048.0c9bc69fdc01bc4193fe8197408e65e2@wordpress.org>
References: <048.0c9bc69fdc01bc4193fe8197408e65e2@wordpress.org>
Message-ID: <063.d274a2630fdc7e64abdbff6b8b2e5320@wordpress.org>

#48116: Proposal: Tracking PHP Extension Usage
-------------------------------------------------+-------------------------
 Reporter:  dd32                                 |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  dev-feedback has-patch needs-        |     Focuses:
  refresh                                        |
-------------------------------------------------+-------------------------
Changes (by SergeyBiryukov):

 * keywords:  dev-feedback has-patch => dev-feedback has-patch needs-refresh


Comment:

 A couple of notes on the latest patch:
 * `$gd_info` and `$imagick_info` are defined but never used.
 * `$gd_supported_formats` is defined twice.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48116#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 21:51:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 21:51:04 -0000
Subject: [wp-trac] [WordPress Trac] #55070: Image Editing Cropping is
 not working properly
In-Reply-To: <051.999fb09cf1346fd9db383fea344080be@wordpress.org>
References: <051.999fb09cf1346fd9db383fea344080be@wordpress.org>
Message-ID: <066.9ddb79dc7cb3def630a00dbfe06a4488@wordpress.org>

#55070: Image Editing Cropping is not working properly
--------------------------+---------------------
 Reporter:  andy786       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Media         |     Version:  5.9
 Severity:  critical      |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+---------------------

Comment (by antonvlasenko):

 I'm able to reproduce this bug.
 I'm working on a patch and I will submit it as soon as it's ready.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55070#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:09:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:09:38 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.932b41eff7f66b13eb2b1fa7413572a9@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots has-testing-info                   |  accessibility
-------------------------------------------------+-------------------------

Comment (by flixos90):

 Replying to [comment:30 hellofromTonya]:
 > Hey @flixos90 @Clorith what do you think today (as this one is an
 oldie)? Any concerns about changing the existing behavior for the `Title`
 and `Description`? Or does it still make sense today to pre-populate with
 the original image's properties and show the properties sidebar?

 This still makes sense to me today, I think it's a UX flaw that this
 information isn't taken over when cropping the image. I also just reviewed
 the PR and left a few minor comments, but it's pretty much good to go from
 my end.

 Thank you @antonvlasenko and everyone involved in getting this fixed after
 all these years! :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:33>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:14:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:14:17 -0000
Subject: [wp-trac] [WordPress Trac] #36308: get_attached_file() destroys
 file paths on Windows
In-Reply-To: <050.92eb671f89732a16ad562052bc684b6b@wordpress.org>
References: <050.92eb671f89732a16ad562052bc684b6b@wordpress.org>
Message-ID: <065.66248f205742b9380bbb0a657d5642af@wordpress.org>

#36308: get_attached_file() destroys file paths on Windows
-------------------------------------------------+-------------------------
 Reporter:  Whissi                               |       Owner:  stevenlinx
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch has-unit-   |     Focuses:
  tests dev-feedback has-testing-info needs-     |
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  good-first-bug has-patch has-unit-tests dev-feedback =>
     good-first-bug has-patch has-unit-tests dev-feedback has-testing-info
     needs-testing


Comment:

 Per the discussion in the bug scrub, adding `has-testing-info` and `needs-
 testing` for extra confidence after David's tests were successful.

 See [https://core.trac.wordpress.org/ticket/36308#comment:15 this comment]
 for testing instructions.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36308#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:18:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:18:34 -0000
Subject: [wp-trac] [WordPress Trac] #41445: post_parent can prevent
 media from embedding correctly
In-Reply-To: <051.36e9b448a18da0e6248fb03458b3410b@wordpress.org>
References: <051.36e9b448a18da0e6248fb03458b3410b@wordpress.org>
Message-ID: <066.b27c14984ce46898a6e930634c37be1f@wordpress.org>

#41445: post_parent can prevent media from embedding correctly
-------------------------------------------------+-------------------------
 Reporter:  loboyle                              |       Owner:
                                                 |  adamsilverstein
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.9.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing dev-         |     Focuses:  rest-api
  feedback needs-unit-tests                      |
-------------------------------------------------+-------------------------

Comment (by costdev):

 Per the discussion in the bug scrub, I'm adding `has-testing-info`. See
 [https://core.trac.wordpress.org/ticket/41445 the ticket's description]
 for testing instructions.

 Does anyone have any further thoughts on how to proceed without the
 additional, expensive meta query? Is the radical approach in
 [https://core.trac.wordpress.org/ticket/41445#comment:41 this comment]
 desirable, or?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41445#comment:44>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:18:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:18:51 -0000
Subject: [wp-trac] [WordPress Trac] #41445: post_parent can prevent
 media from embedding correctly
In-Reply-To: <051.36e9b448a18da0e6248fb03458b3410b@wordpress.org>
References: <051.36e9b448a18da0e6248fb03458b3410b@wordpress.org>
Message-ID: <066.fb7851e59f9d07916548c3f42c40c17d@wordpress.org>

#41445: post_parent can prevent media from embedding correctly
-------------------------------------------------+-------------------------
 Reporter:  loboyle                              |       Owner:
                                                 |  adamsilverstein
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.9.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing dev-         |     Focuses:  rest-api
  feedback needs-unit-tests has-testing-info     |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  has-patch needs-testing dev-feedback needs-unit-tests => has-
     patch needs-testing dev-feedback needs-unit-tests has-testing-info


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41445#comment:45>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:21:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:21:22 -0000
Subject: [wp-trac] [WordPress Trac] #42957: Usernames ending in a period
 generate invalid reset password links in certain email clients
In-Reply-To: <053.6ac86000e6ab38aac81c6a705c869e8a@wordpress.org>
References: <053.6ac86000e6ab38aac81c6a705c869e8a@wordpress.org>
Message-ID: <068.f70c28471c4be9e2ff4e96b264724b84@wordpress.org>

#42957: Usernames ending in a period generate invalid reset password links in
certain email clients
-------------------------------------------------+-------------------------
 Reporter:  paulcline                            |       Owner:
                                                 |  hellofromTonya
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note dev-feedback                              |
-------------------------------------------------+-------------------------

Comment (by costdev):

 Per the discussion on the bug scrub, pinging @hellofromTonya to see if
 you've had time to do further investigation on a possible alternative
 approach?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42957#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:29:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:29:23 -0000
Subject: [wp-trac] [WordPress Trac] #48116: Proposal: Tracking PHP
 Extension Usage
In-Reply-To: <048.0c9bc69fdc01bc4193fe8197408e65e2@wordpress.org>
References: <048.0c9bc69fdc01bc4193fe8197408e65e2@wordpress.org>
Message-ID: <063.062c6365ddfc817f86335d1d0f178d0a@wordpress.org>

#48116: Proposal: Tracking PHP Extension Usage
-------------------------------------------------+-------------------------
 Reporter:  dd32                                 |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  dev-feedback has-patch needs-        |     Focuses:
  refresh                                        |
-------------------------------------------------+-------------------------

Comment (by costdev):

 I see that [https://github.com/WordPress/wordpress-develop/pull/1096/ PR
 1096], while in `Draft`, was updated 2 months ago and uses an alternative
 approach to the `$gd_info`, `$imagick_info` and `gd_supported_formats`
 variables. However,
 [https://core.trac.wordpress.org/attachment/ticket/48116/48116.3.diff
 48116.3.diff] was proposed for `commit`.

 @adamsilverstein, can you confirm whether the PR is an updated version of
 the patch and is the `commit` candidate, or if
 [https://core.trac.wordpress.org/attachment/ticket/48116/48116.3.diff
 48116.3.diff] does indeed need a refresh?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48116#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:31:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:31:18 -0000
Subject: [wp-trac] [WordPress Trac] #48116: Proposal: Tracking PHP
 Extension Usage
In-Reply-To: <048.0c9bc69fdc01bc4193fe8197408e65e2@wordpress.org>
References: <048.0c9bc69fdc01bc4193fe8197408e65e2@wordpress.org>
Message-ID: <063.48884c96a209ba321bfd19f22589f747@wordpress.org>

#48116: Proposal: Tracking PHP Extension Usage
-------------------------------------------------+-------------------------
 Reporter:  dd32                                 |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  dev-feedback has-patch needs-        |     Focuses:
  refresh                                        |
-------------------------------------------------+-------------------------

Comment (by adamsilverstein):

 @costdev I think you are right, I updated the PR but never updated the
 patch. I'll get this updated.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48116#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:32:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:32:53 -0000
Subject: [wp-trac] [WordPress Trac] #50061: Image_meta original_image as
 valid image_size
In-Reply-To: <051.fcac2d537ccf7d42b6074e7bff75a5fd@wordpress.org>
References: <051.fcac2d537ccf7d42b6074e7bff75a5fd@wordpress.org>
Message-ID: <066.d0a2bc8cf3ea99cca38c7f020b7c8ab6@wordpress.org>

#50061: Image_meta original_image as valid image_size
--------------------------+-----------------------
 Reporter:  tomcent       |       Owner:  antpb
     Type:  enhancement   |      Status:  accepted
 Priority:  normal        |   Milestone:  6.0
Component:  Media         |     Version:  5.3
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |     Focuses:
--------------------------+-----------------------

Comment (by adamsilverstein):

 Noting that we don't currently store the original size (width/height or
 filesize) info which we probably should consider to make getting the data
 more efficient in the new function (which would use the data when
 available).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50061#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:36:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:36:40 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.0b5addc2c703c85d800215dfcd332f0e@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
-------------------------------------------------+-------------------------
 Reporter:  giox069                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Filesystem API                       |     Version:  3.7
 Severity:  normal                               |  Resolution:
 Keywords:  reporter-feedback dev-feedback has-  |     Focuses:
  patch needs-testing                            |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  reporter-feedback dev-feedback has-patch => reporter-feedback
     dev-feedback has-patch needs-testing


Comment:

 Per the discussion in the bug scrub, I'm adding `needs-testing`.

 Are there any testing instructions that can be provided to testers?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:41:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:41:35 -0000
Subject: [wp-trac] [WordPress Trac] #50866: Media Uploader Blows Up File
 Sizes
In-Reply-To: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
References: <048.ae16c18d531a2f779a0632d2af589169@wordpress.org>
Message-ID: <063.39f757a9458d0d3b6234b8033c45913a@wordpress.org>

#50866: Media Uploader Blows Up File Sizes
-------------------------------------+-------------------------------------
 Reporter:  hvar                     |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:  5.4.2
 Severity:  major                    |  Resolution:
 Keywords:  has-patch has-unit-      |     Focuses:  administration,
  tests dev-feedback needs-testing   |  performance
  has-testing-info                   |
-------------------------------------+-------------------------------------

Comment (by peterwilsoncc):

 Related #36477, possibly a duplicate as it's the same underlying problem.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50866#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 22:59:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 22:59:51 -0000
Subject: [wp-trac] [WordPress Trac] #49278: Improve meta query
In-Reply-To: <053.f456e8069a5775465fadeab7ad94e33c@wordpress.org>
References: <053.f456e8069a5775465fadeab7ad94e33c@wordpress.org>
Message-ID: <068.a4437ba8362fc644d413913502b8f328@wordpress.org>

#49278: Improve meta query
-------------------------------------------------+-------------------------
 Reporter:  jillebehm                            |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Query                                |     Version:  5.3.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback early early-  |     Focuses:
  like-actually-early has-unit-tests             |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * milestone:  6.0 => Future Release


Comment:

 This was discussed in a bug scrub today.

 Due to the complexity of the task and the patch still requiring some work,
 it was decided to move it off the 6.0 milestone.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49278#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 23:55:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 23:55:20 -0000
Subject: [wp-trac] [WordPress Trac] #51142: Invalid Moment.js locale
 from get_user_locale()
In-Reply-To: <058.2846ac89cb2c84cdad00d08c8829781c@wordpress.org>
References: <058.2846ac89cb2c84cdad00d08c8829781c@wordpress.org>
Message-ID: <073.0d26e7ddfcea3c998329766f701dd248@wordpress.org>

#51142: Invalid Moment.js locale from get_user_locale()
--------------------------------+-------------------------
 Reporter:  slightlyfaulty      |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  6.0
Component:  External Libraries  |     Version:  5.0
 Severity:  normal              |  Resolution:
 Keywords:  has-patch           |     Focuses:  javascript
--------------------------------+-------------------------
Changes (by noisysocks):

 * milestone:  Awaiting Review => 6.0


Comment:

 I opened [https://github.com/WordPress/wordpress-develop/pull/2456 a PR]
 which should fix this. Noting this comment here for extra visibility:

 > An alternative to this PR is to remove the inline script from moment
 altogether. It was added in
 https://core.trac.wordpress.org/changeset/44262 without any note. I
 believe it was a mistake. It's not necessary since @wordpress/date will
 also call moment.updateLocale / moment.defineLocale and @wordpress/date is
 the only part of WP Admin that relies on moment localisation. It's
 possible that third party plugins now rely on this, though. What do you
 think @hellofromTonya @SergeyBiryukov?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51142#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 24 23:57:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 24 Mar 2022 23:57:20 -0000
Subject: [wp-trac] [WordPress Trac] #52695: Incorrect way to
 updateLocale in moment.js add_inline_script
In-Reply-To: <056.37677b6a845f75e31b2baf87ba24a473@wordpress.org>
References: <056.37677b6a845f75e31b2baf87ba24a473@wordpress.org>
Message-ID: <071.66fb80601d06523bcac3e1c136a3eeae@wordpress.org>

#52695: Incorrect way to updateLocale in moment.js add_inline_script
--------------------------------+---------------------
 Reporter:  yoancutillas        |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  6.0
Component:  External Libraries  |     Version:  5.6.2
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:
--------------------------------+---------------------
Changes (by noisysocks):

 * milestone:  Awaiting Review => 6.0


Comment:

 Thanks for spotting this! The [https://github.com/WordPress/wordpress-
 develop/pull/2456 fix] I opened for #51142 also addresses this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52695#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 00:40:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 00:40:40 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.790ffc7797117f2e39688acc12e2c10b@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
-------------------------------------------------+-------------------------
 Reporter:  giox069                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Filesystem API                       |     Version:  3.7
 Severity:  normal                               |  Resolution:
 Keywords:  reporter-feedback dev-feedback has-  |     Focuses:
  patch needs-testing                            |
-------------------------------------------------+-------------------------

Comment (by afragen):

 If the fallback is to check `ftp_size`, is there some reason to even try
 `ftp_nlist`?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 01:09:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 01:09:51 -0000
Subject: [wp-trac] [WordPress Trac] #48222: "Show password" button
 overlaps with the LastPass icon
In-Reply-To: <058.0d699b3273d056c061d95a9b99cee6c0@wordpress.org>
References: <058.0d699b3273d056c061d95a9b99cee6c0@wordpress.org>
Message-ID: <073.22adfefc67dceab7fa611b529cfb3c70@wordpress.org>

#48222: "Show password" button overlaps with the LastPass icon
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:
                                                 |  sabernhardt
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Login and Registration               |     Version:  5.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch needs-     |     Focuses:  ui
  design-feedback needs-testing early            |
-------------------------------------------------+-------------------------

Comment (by sabernhardt):

 That screenshot looks the same (to me) as 48222.10.diff, but this patch
 does need more than design feedback.
 - Setting `display: block` on `.login .button.wp-hide-pw` overrides `.no-
 js .hide-if-no-js`.
 - The JS change affects the user pages (Profile, New User, Edit User). The
 text includes "password" on larger screens, and the ARIA label is stuck at
 "Hide password" whether the password is showing or not.

 Regarding the design:
 - Preventing overlap of password manager icons over the password itself
 seems impossible without including extra padding. That would not make
 sense for people who do not use a password manager.
 - I do not want to try forcing a width for the toggle button (for example,
 using both text strings in `span` tags and hiding one with `visibility:
 hidden`). However, **moving the icon** to the other side of the text could
 make the width difference between the two text strings less noticeable.
 - The bottom margin could be slightly more (16px instead of 12).

 I [https://github.com/sabernhardt/wordpress-develop/pull/2 drafted a PR]
 to explore some revisions. (Note: The PR is still on my fork and may
 change.)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48222#comment:61>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 02:31:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 02:31:29 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
In-Reply-To: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
References: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
Message-ID: <066.95ae54f579a6b6a95f19ad514ea403d5@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
----------------------------------------+----------------------------
 Reporter:  crs1138                     |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:  5.8.3
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:  accessibility
----------------------------------------+----------------------------
Changes (by rsiddharth):

 * Attachment "53234.2022032000.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55370>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 02:32:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 02:32:44 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
In-Reply-To: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
References: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
Message-ID: <066.bbfb057101525ee09275cf3582a31417@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
--------------------------------------+----------------------------
 Reporter:  crs1138                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Formatting                |     Version:  5.8.3
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  accessibility
--------------------------------------+----------------------------
Changes (by rsiddharth):

 * keywords:  needs-patch good-first-bug => good-first-bug has-patch


Comment:

 @ryokuhi, I've uploaded the initial version of the patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55370#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 02:33:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 02:33:59 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
In-Reply-To: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
References: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
Message-ID: <066.75ac916ac382a7c96cc617cb0d0df6e6@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
--------------------------------------+----------------------------
 Reporter:  crs1138                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Formatting                |     Version:  5.8.3
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  accessibility
--------------------------------------+----------------------------
Changes (by rsiddharth):

 * Attachment "55370.v202203242230.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55370>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 02:35:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 02:35:13 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
In-Reply-To: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
References: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
Message-ID: <066.3b4ef6d4643b4aed07843b2f069a2ab2@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
--------------------------------------+----------------------------
 Reporter:  crs1138                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Formatting                |     Version:  5.8.3
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  accessibility
--------------------------------------+----------------------------

Comment (by rsiddharth):

 Ignore 53234.2022032000.patch; uploaded the wrong one.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55370#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 02:57:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 02:57:38 -0000
Subject: [wp-trac] [WordPress Trac] #54437: Warning not in bold?
In-Reply-To: <053.79ef35713d160dce241eff046fd87735@wordpress.org>
References: <053.79ef35713d160dce241eff046fd87735@wordpress.org>
Message-ID: <068.d0d9d72d830c15e7b869ad4e455d8ecf@wordpress.org>

#54437: Warning not in bold?
-------------------------------------+-------------------------------------
 Reporter:  NekoJonez                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  General                  |     Version:
 Severity:  trivial                  |  Resolution:
 Keywords:  needs-patch good-first-  |     Focuses:  ui, administration,
  bug                                |  template, coding-standards
-------------------------------------+-------------------------------------
Changes (by oakesjosh):

 * Attachment "54437.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54437>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 02:58:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 02:58:54 -0000
Subject: [wp-trac] [WordPress Trac] #54437: Warning not in bold?
In-Reply-To: <053.79ef35713d160dce241eff046fd87735@wordpress.org>
References: <053.79ef35713d160dce241eff046fd87735@wordpress.org>
Message-ID: <068.d1afee6dad726652899e0edc7ae05029@wordpress.org>

#54437: Warning not in bold?
-------------------------------------+-------------------------------------
 Reporter:  NekoJonez                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  General                  |     Version:
 Severity:  trivial                  |  Resolution:
 Keywords:  good-first-bug has-      |     Focuses:  ui, administration,
  patch                              |  template, coding-standards
-------------------------------------+-------------------------------------
Changes (by oakesjosh):

 * keywords:  needs-patch good-first-bug => good-first-bug has-patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54437#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 03:18:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 03:18:22 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs
 file
In-Reply-To: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
References: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
Message-ID: <064.30a26a7e04a2a870229d481d4a8648bd@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
-------------------------+------------------------------
 Reporter:  helen        |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------------------

Comment (by costdev):

 There are 421 commits beginning with "Coding Standard" (case-insensitive).

 - See [https://gist.github.com/costdev/30cf2b80e003190bb66267e6abd83abd
 #file-cs-commits-log here] for the `HASH # [REVISION]` format.
 - See [https://gist.github.com/costdev/30cf2b80e003190bb66267e6abd83abd
 #file-cs-commits-with-subjects-log here] for the `HASH # [REVISION] #
 SUBJECT` format.

 The second one should be easier to pick out commits that deal with
 PHPCS/WPCS configuration rather than stylistic changes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 04:45:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 04:45:34 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs
 file
In-Reply-To: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
References: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
Message-ID: <064.01502ae86e97221dca37fcc36c708d4a@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
------------------------------+------------------------------
 Reporter:  helen             |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  General           |     Version:
 Severity:  minor             |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+------------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch => has-patch commit


Comment:

 I think this is good to go in as an MVP.

 The initial commit can go in as a `See` rather than a `Fixes` and further
 commits added once the act of committing gets additional eyes on the
 ticket.

 I consider this tooling related so commits can go in during source freeze.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 05:31:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 05:31:30 -0000
Subject: [wp-trac] [WordPress Trac] #55456: Double escaping
 wp_user-settings
In-Reply-To: <053.4e95668003a2859da7231085e66ad927@wordpress.org>
References: <053.4e95668003a2859da7231085e66ad927@wordpress.org>
Message-ID: <068.423e4d1eba006a1beb8ec74d80d43153@wordpress.org>

#55456: Double escaping wp_user-settings
-------------------------------------------------+-------------------------
 Reporter:  phatkoala                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:  2.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback has-testing-  |     Focuses:
  info needs-testing                             |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  has-patch => has-patch dev-feedback has-testing-info needs-
     testing
 * version:  5.9.2 => 2.7
 * milestone:  Awaiting Review => 6.0


Comment:

 == Test Report

 === Env
 * Server: Apache (Linux)
 * WordPress: 6.0-alpha-52448-src
 * Browser: Chrome 99.0.4844.51
 * OS: Windows 10
 * Theme: Twenty Twenty-One
 * Plugins: None activated.

 === Steps to reproduce
 1. Save the plugin code in this ticket's description to `wp-
 content/plugins/ampersand_test/ampersand_test.php`.
 2. Navigate to `Plugins > Installed Plugins`.
 3. Activate the `Ampersand Test` plugin.
 4. Navigate to `Users > Profile`.
 5. Open the database and navigate to `{prefix}_usermeta`.
 6. Filter for `wp_user-settings`.
 7. See that the value contains `&ampfoo=1&ampbar=1`.
 8. Refresh the `Profile` page.
 9. Repeat steps 5 and 6.
 10. See that the value contains `&amp&ampfoo=1&amp&ampbar=1`.

 === Cleanup
 1. Edit the database entry and remove `&amp&ampfoo=1&amp&ampbar=1`.
 2. Save.
 3. Navigate to `Plugins > Installed Plugins`.
 4. Deactivate the `Ampersand Test` plugin, then reactivate it.

 === Steps to test [https://github.com/WordPress/wordpress-
 develop/pull/2458 PR 2458]
 1. Checkout [https://github.com/WordPress/wordpress-develop/pull/2458 PR
 2458].
 2. Open the database and navigate to the `{prefix}_usermeta` table.
 3. Filter for `wp_user-settings`.
 4. See that the value contains `&foo=1&bar=1`.
 5. Refresh the `Profile` page.
 6. See that the value still contains `&foo=1&bar=1`.

 === Results
 1. Issue reproduced. ✅
 2. [https://github.com/WordPress/wordpress-develop/pull/2458 PR 2458]
 resolves the issue. ✅

 === Notes
 1. Introduced in [8784].
 2. Milestoning for 6.0 to get this some visibility.
 3. Adding `dev-feedback` to verify that this approach has no unintended
 side effects / BC breaks.
 4. Adding `has-testing-info` and `needs-testing` to get some tester
 creativity on this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55456#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 05:52:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 05:52:43 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.66c05f1fd7f9797795a7f6932d619a2c@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
-------------------------------------------------+-------------------------
 Reporter:  giox069                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Filesystem API                       |     Version:  3.7
 Severity:  normal                               |  Resolution:
 Keywords:  reporter-feedback dev-feedback has-  |     Focuses:
  patch needs-testing                            |
-------------------------------------------------+-------------------------

Comment (by afragen):

 Related #53318

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 05:57:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 05:57:00 -0000
Subject: [wp-trac] [WordPress Trac] #53318: FTPext method exists()
 returns always false for files!
In-Reply-To: <050.cd9a40e2a7be30b2d8eb40460ecf9ddd@wordpress.org>
References: <050.cd9a40e2a7be30b2d8eb40460ecf9ddd@wordpress.org>
Message-ID: <065.f1833b8e3772b99d5850d46af260259f@wordpress.org>

#53318: FTPext method exists() returns always false for files!
--------------------------------------+---------------------
 Reporter:  arl1nd                    |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Filesystem API            |     Version:  5.7.2
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch dev-feedback  |     Focuses:  docs
--------------------------------------+---------------------

Comment (by afragen):

 Related #51170

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53318#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 09:31:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 09:31:21 -0000
Subject: [wp-trac] [WordPress Trac] #55459: Change Login Label name
Message-ID: <052.fad3b75ff87264e7068a28a8f72505aa@wordpress.org>

#55459: Change Login Label name
------------------------------------+-----------------------------
 Reporter:  wparslan                |      Owner:  (none)
     Type:  enhancement             |     Status:  new
 Priority:  normal                  |  Milestone:  Awaiting Review
Component:  Login and Registration  |    Version:
 Severity:  normal                  |   Keywords:  needs-patch
  Focuses:  accessibility           |
------------------------------------+-----------------------------
 I wanted to change the Login Labels of my Login Page and couldn't find
 anything to hook as it is only labeled with raw values.

 It would be a lot better if there was anything else than gettext function
 to change the value. Maybe a filter.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55459>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 09:55:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 09:55:07 -0000
Subject: [wp-trac] [WordPress Trac] #36907: Improved sticky post query
In-Reply-To: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
References: <056.3d869f6613968a9b112cc6108cfa738f@wordpress.org>
Message-ID: <071.64bb0f7ce30e2dd65a7a9aafdf4ee057@wordpress.org>

#36907: Improved sticky post query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  reopened
 Priority:  normal                    |   Milestone:  6.0
Component:  Query                     |     Version:  3.5
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------

Comment (by spacedmonkey):

 In [changeset:"52990" 52990]:
 {{{
 #!CommitTicketReference repository="" revision="52990"
 Query: Ensure that sticky post query returns all sticky posts.

 Ensure that the `posts_per_page` parameter submit to sticky post query
 matches the number of sticky posts requested.

 Follow-up to [52982]

 Props Spacedmonkey, peterwilsoncc.
 See #36907.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36907#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 11:04:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 11:04:11 -0000
Subject: [wp-trac] [WordPress Trac] #55459: Change Login Label name
In-Reply-To: <052.fad3b75ff87264e7068a28a8f72505aa@wordpress.org>
References: <052.fad3b75ff87264e7068a28a8f72505aa@wordpress.org>
Message-ID: <067.b6ca8c567402383476185a2c16961d52@wordpress.org>

#55459: Change Login Label name
------------------------------------+------------------------------
 Reporter:  wparslan                |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Login and Registration  |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  needs-patch             |     Focuses:
------------------------------------+------------------------------
Changes (by sabernhardt):

 * focuses:  accessibility =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55459#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 11:45:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 11:45:37 -0000
Subject: [wp-trac] [WordPress Trac] #55360: Add limit to query in
 WP_Tax_Query
In-Reply-To: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
References: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
Message-ID: <071.da52b99e619f5387a961e9f2dcfd4ade@wordpress.org>

#55360: Add limit to query in WP_Tax_Query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  4.7
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------
Changes (by spacedmonkey):

 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55360#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 11:47:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 11:47:13 -0000
Subject: [wp-trac] [WordPress Trac] #54015: Unable to pass _embed param
 to enveloped REST API requests
In-Reply-To: <056.7a3e907025d46dd4af28a7d94ff54e4b@wordpress.org>
References: <056.7a3e907025d46dd4af28a7d94ff54e4b@wordpress.org>
Message-ID: <071.30d51e7387cf28bc376e477c867479fa@wordpress.org>

#54015: Unable to pass _embed param to enveloped REST API requests
----------------------------------------+-----------------------------
 Reporter:  spacedmonkey                |       Owner:  spacedmonkey
     Type:  defect (bug)                |      Status:  assigned
 Priority:  normal                      |   Milestone:  Future Release
Component:  REST API                    |     Version:  5.4
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:  rest-api
----------------------------------------+-----------------------------

Comment (by spacedmonkey):

 @TimothyBlynJacobs I am not sure what you mean there. Any chance you could
 put together a test for this or point in the direction of one.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54015#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 12:03:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 12:03:19 -0000
Subject: [wp-trac] [WordPress Trac] #55460: Improve comment query cache key
 generation
Message-ID: <056.034103b77cb91507279f86861d47d215@wordpress.org>

#55460: Improve comment query cache key generation
--------------------------+----------------------------------------
 Reporter:  spacedmonkey  |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:  Future Release
Component:  Comments      |    Version:  3.1
 Severity:  normal        |   Keywords:  needs-patch good-first-bug
  Focuses:  performance   |
--------------------------+----------------------------------------
 Follow on from #55352.

 Improve cache key generation in WP_Comment_Query to improve likely that
 cache is reused. Unsetting `update_comment_meta_cache` and
 `update_comment_post_cache`, would improve cache keys, as this fields do
 not affect the cache.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55460>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 12:05:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 12:05:51 -0000
Subject: [wp-trac] [WordPress Trac] #55460: Improve cache key generation
 in WP_Comment_Query (was: Improve comment query cache key generation)
In-Reply-To: <056.034103b77cb91507279f86861d47d215@wordpress.org>
References: <056.034103b77cb91507279f86861d47d215@wordpress.org>
Message-ID: <071.7ed448845ce4857d9bb14b1d653475ae@wordpress.org>

#55460: Improve cache key generation in WP_Comment_Query
----------------------------------------+-----------------------------
 Reporter:  spacedmonkey                |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  Future Release
Component:  Comments                    |     Version:  3.1
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:  performance
----------------------------------------+-----------------------------

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55460#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 12:08:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 12:08:17 -0000
Subject: [wp-trac] [WordPress Trac] #55461: Improve cache key generation in
 WP_Network_Query
Message-ID: <056.d13ed3c690dcbe4f318e2a175491c637@wordpress.org>

#55461: Improve cache key generation in WP_Network_Query
----------------------------------+----------------------------------------
 Reporter:  spacedmonkey          |      Owner:  (none)
     Type:  defect (bug)          |     Status:  new
 Priority:  normal                |  Milestone:  Awaiting Review
Component:  Networks and Sites    |    Version:  4.6
 Severity:  normal                |   Keywords:  needs-patch good-first-bug
  Focuses:  multisite,            |
  performance                     |
----------------------------------+----------------------------------------
 Follow on from #55352.

 Improve cache key generation in WP_Network_Query to improve likely that
 cache is reused. Unsetting `update_network_cache`, would improve cache
 keys, as this fields do not affect the cache.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55461>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 12:10:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 12:10:15 -0000
Subject: [wp-trac] [WordPress Trac] #55461: Improve cache key generation
 in WP_Network_Query
In-Reply-To: <056.d13ed3c690dcbe4f318e2a175491c637@wordpress.org>
References: <056.d13ed3c690dcbe4f318e2a175491c637@wordpress.org>
Message-ID: <071.cca028214e04b5737c0c1af13bfd1948@wordpress.org>

#55461: Improve cache key generation in WP_Network_Query
----------------------------------------+----------------------------------
 Reporter:  spacedmonkey                |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Networks and Sites          |     Version:  4.6
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:  multisite,
                                        |  performance
----------------------------------------+----------------------------------
Changes (by spacedmonkey):

 * type:  defect (bug) => enhancement


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55461#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 12:11:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 12:11:54 -0000
Subject: [wp-trac] [WordPress Trac] #55462: Improve cache key generation in
 WP_Site_Query
Message-ID: <056.788faa0f83ecc66621ed2f44c8bdd070@wordpress.org>

#55462: Improve cache key generation in WP_Site_Query
----------------------------------+----------------------------------------
 Reporter:  spacedmonkey          |      Owner:  (none)
     Type:  enhancement           |     Status:  new
 Priority:  normal                |  Milestone:  Awaiting Review
Component:  Networks and Sites    |    Version:  4.6
 Severity:  normal                |   Keywords:  needs-patch good-first-bug
  Focuses:  multisite,            |
  performance                     |
----------------------------------+----------------------------------------
 Follow on from #55352.

 Improve cache key generation in WP_Site_Query to improve likely that cache
 is reused. Unsetting `update_site_cache` and `update_site_meta_cache`,
 would improve cache keys, as this fields do not affect the cache.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55462>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 12:18:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 12:18:11 -0000
Subject: [wp-trac] [WordPress Trac] #55463: Add a limit to _prime_*_cache
 functions
Message-ID: <056.1f9f83d71c348d6b749c027aaa736ece@wordpress.org>

#55463: Add a limit to _prime_*_cache functions
--------------------------+----------------------------------------
 Reporter:  spacedmonkey  |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Cache API     |    Version:
 Severity:  normal        |   Keywords:  needs-patch good-first-bug
  Focuses:  performance   |
--------------------------+----------------------------------------
 The _prime_*_cache functions, like `_prime_post_cache` do a simple query
 to prime caches. This does a IN request to get all the objects. As we know
 the number of objects we wish returned, as have an array, we can add a
 simple LIMIT to the query to improve the performance of the query.

 Example:

 {{{#!php
 $fresh_posts = $wpdb->get_results( sprintf( "SELECT $wpdb->posts.* FROM
 $wpdb->posts WHERE ID IN (%s) LIMIT %d", implode( ',', $non_cached_ids ),
 count( $non_cached_ids ) ) );
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55463>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 12:21:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 12:21:04 -0000
Subject: [wp-trac] [WordPress Trac] #55463: Add a limit to
 _prime_*_cache functions
In-Reply-To: <056.1f9f83d71c348d6b749c027aaa736ece@wordpress.org>
References: <056.1f9f83d71c348d6b749c027aaa736ece@wordpress.org>
Message-ID: <071.50e37b74edd8c211b391b059f80b5cac@wordpress.org>

#55463: Add a limit to _prime_*_cache functions
----------------------------------------+------------------------------
 Reporter:  spacedmonkey                |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Cache API                   |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:  performance
----------------------------------------+------------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-25 at 12.19.15.png" added.

 Before change

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55463>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 12:21:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 12:21:29 -0000
Subject: [wp-trac] [WordPress Trac] #55463: Add a limit to
 _prime_*_cache functions
In-Reply-To: <056.1f9f83d71c348d6b749c027aaa736ece@wordpress.org>
References: <056.1f9f83d71c348d6b749c027aaa736ece@wordpress.org>
Message-ID: <071.91128d6facda6c419d55c2ca973458a4@wordpress.org>

#55463: Add a limit to _prime_*_cache functions
----------------------------------------+------------------------------
 Reporter:  spacedmonkey                |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Cache API                   |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:  performance
----------------------------------------+------------------------------
Changes (by spacedmonkey):

 * Attachment "Screenshot 2022-03-25 at 12.20.14.png" added.

 After change

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55463>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 13:00:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 13:00:05 -0000
Subject: [wp-trac] [WordPress Trac] #55464: W3C compatible
Message-ID: <053.b101c89d5d302887f49f2e1133e5bff3@wordpress.org>

#55464: W3C compatible
-------------------------+-----------------------------
 Reporter:  spink9010    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:  5.9.2
 Severity:  normal       |   Keywords:  needs-testing
  Focuses:               |
-------------------------+-----------------------------
 Please test compatibility with W3C
 Thanks in advance

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55464>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 13:01:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 13:01:14 -0000
Subject: [wp-trac] [WordPress Trac] #55464: W3C compatible
In-Reply-To: <053.b101c89d5d302887f49f2e1133e5bff3@wordpress.org>
References: <053.b101c89d5d302887f49f2e1133e5bff3@wordpress.org>
Message-ID: <068.e9001a638a77fbe1080a0871cf25b0b6@wordpress.org>

#55464: W3C compatible
---------------------------+------------------------------
 Reporter:  spink9010      |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  5.9.2
 Severity:  normal         |  Resolution:
 Keywords:  needs-testing  |     Focuses:
---------------------------+------------------------------
Changes (by spink9010):

 * Attachment "w3c-compatible.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55464>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 13:43:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 13:43:45 -0000
Subject: [wp-trac] [WordPress Trac] #53177: WP_User_Query does not
 accept fields as string except ID
In-Reply-To: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
References: <050.7a532f1587592d74c55a28a712ff8ed2@wordpress.org>
Message-ID: <065.329f389fe4e62485f9ef3f4ae4131a85@wordpress.org>

#53177: WP_User_Query does not accept fields as string except ID
-------------------------------------------------+-------------------------
 Reporter:  rilwis                               |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:  4.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:  docs
  testing-info needs-testing                     |
-------------------------------------------------+-------------------------

Comment (by Boniu91):

 == Test Report

 === Env
 * WordPress 5.9.2 and 6.0-alpha-52448-src
 * Windows 10
 * Theme: Twenty Twenty One

 === Steps to test
 1. On WordPress 5.9.2 add the code mentioned
 [https://core.trac.wordpress.org/ticket/53177#comment:14]
 2. User ID is displayed on the frontend
 3. Update the WordPress to this specific patch
 4. User display_name as a string is displayed on the frontend

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53177#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 14:33:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 14:33:20 -0000
Subject: [wp-trac] [WordPress Trac] #55352: Improve cache key generation
 in WP_Term_Query
In-Reply-To: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
References: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
Message-ID: <071.ba8de68489ebbe25582d7f912c393e37@wordpress.org>

#55352: Improve cache key generation in WP_Term_Query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  4.7
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------

Comment (by johnjamesjacoby):

 I’d like to kindly suggest, rather than inlining everything in existing
 methods, that a new method be used to reshape these arguments for improved
 cache key usage.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55352#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 15:13:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 15:13:21 -0000
Subject: [wp-trac] [WordPress Trac] #6479: Encourage people to change
 default tagline
In-Reply-To: <055.e530d469b6d3d46c70a1707e6bd1ead0@wordpress.org>
References: <055.e530d469b6d3d46c70a1707e6bd1ead0@wordpress.org>
Message-ID: <070.a1f0495aeb47107d74af909dc7ccb9f7@wordpress.org>

#6479: Encourage people to change default tagline
-------------------------------------------------+-------------------------
 Reporter:  markjaquith                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  2.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-unit-  |     Focuses:
  tests needs-refresh needs-codex                |
-------------------------------------------------+-------------------------
Changes (by milana_cap):

 * keywords:  has-patch needs-testing needs-unit-tests needs-refresh => has-
     patch needs-testing needs-unit-tests needs-refresh needs-codex


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/6479#comment:40>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 15:26:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 15:26:30 -0000
Subject: [wp-trac] [WordPress Trac] #55352: Improve cache key generation
 in WP_Term_Query
In-Reply-To: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
References: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
Message-ID: <071.b51221fe5dd703102d2e17e4940d3f7a@wordpress.org>

#55352: Improve cache key generation in WP_Term_Query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  4.7
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------

Comment (by spacedmonkey):

 Created some related tickets to improve cache be generation for other
 Query classes.

 #55460, #55461, #55462

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55352#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 15:27:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 15:27:41 -0000
Subject: [wp-trac] [WordPress Trac] #40582: Capitalize character - "CTRL
 + a" -> "CTRL + A"
In-Reply-To: <053.d5236948cdeb29a18238315f2650dd19@wordpress.org>
References: <053.d5236948cdeb29a18238315f2650dd19@wordpress.org>
Message-ID: <068.bf3fd5871b1042813eac7f0f5bf76993@wordpress.org>

#40582: Capitalize character - "CTRL + a" -> "CTRL + A"
-----------------------------------+-----------------------
 Reporter:  Presskopp              |       Owner:  audrasjb
     Type:  enhancement            |      Status:  closed
 Priority:  normal                 |   Milestone:  6.0
Component:  Administration         |     Version:  4.7.4
 Severity:  minor                  |  Resolution:  fixed
 Keywords:  has-patch needs-codex  |     Focuses:  ui-copy
-----------------------------------+-----------------------
Changes (by milana_cap):

 * keywords:  has-patch => has-patch needs-codex


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40582#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 15:29:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 15:29:30 -0000
Subject: [wp-trac] [WordPress Trac] #55462: Improve cache key generation
 in WP_Site_Query
In-Reply-To: <056.788faa0f83ecc66621ed2f44c8bdd070@wordpress.org>
References: <056.788faa0f83ecc66621ed2f44c8bdd070@wordpress.org>
Message-ID: <071.a1228f8be638a575a5aff256a413e72c@wordpress.org>

#55462: Improve cache key generation in WP_Site_Query
----------------------------------------+----------------------------------
 Reporter:  spacedmonkey                |       Owner:  (none)
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Networks and Sites          |     Version:  4.6
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch good-first-bug  |     Focuses:  multisite,
                                        |  performance
----------------------------------------+----------------------------------

Comment (by spacedmonkey):

 Related: #42252 #42284

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55462#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 15:30:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 15:30:05 -0000
Subject: [wp-trac] [WordPress Trac] #42942: Provide a
 post_date_column_time hook for media files
In-Reply-To: <054.b8ba66020e3f87a90d888b926a23b5f9@wordpress.org>
References: <054.b8ba66020e3f87a90d888b926a23b5f9@wordpress.org>
Message-ID: <069.6f1bc61f8d9b764af97a30eb0e5a7c91@wordpress.org>

#42942: Provide a post_date_column_time hook for media files
-------------------------------------------------+-------------------------
 Reporter:  ivanlutrov                           |       Owner:
                                                 |  davidbaumwald
     Type:  feature request                      |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  5.1
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch dev-feedback needs-dev-    |     Focuses:
  note needs-docs                                |
-------------------------------------------------+-------------------------
Changes (by milana_cap):

 * keywords:  has-patch dev-feedback needs-dev-note => has-patch dev-
     feedback needs-dev-note needs-docs


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42942#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 15:41:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 15:41:10 -0000
Subject: [wp-trac] [WordPress Trac] #10886: WordPress should not
 unnecessarily query posts at page load
In-Reply-To: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
References: <053.931185c546a0edbf3024f49b87a08e43@wordpress.org>
Message-ID: <068.519c0adbe1587bf5cb10017996f15997@wordpress.org>

#10886: WordPress should not unnecessarily query posts at page load
-------------------------------------------------+-------------------------
 Reporter:  junsuijin                            |       Owner:
                                                 |  spacedmonkey
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Bootstrap/Load                       |     Version:  2.8.4
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-unit-tests early has-patch       |     Focuses:
  needs-dev-note needs-docs                      |  performance
-------------------------------------------------+-------------------------
Changes (by milana_cap):

 * keywords:  has-unit-tests early has-patch needs-dev-note => has-unit-
     tests early has-patch needs-dev-note needs-docs


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/10886#comment:42>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 15:45:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 15:45:00 -0000
Subject: [wp-trac] [WordPress Trac] #49728: [PHP 8] Prepare for the
 internal functions throwing `TypeError` or `ValueError` exceptions on
 unexpected types/values
In-Reply-To: <055.10729326741625e8d0bd4e84786c665e@wordpress.org>
References: <055.10729326741625e8d0bd4e84786c665e@wordpress.org>
Message-ID: <070.0f9feb746ae934282b116c42c9b92bd9@wordpress.org>

#49728: [PHP 8] Prepare for the internal functions throwing `TypeError` or
`ValueError` exceptions on unexpected types/values
-------------------------------------------------+-------------------------
 Reporter:  ayeshrajans                          |       Owner:
                                                 |  hellofromTonya
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Build/Test Tools                     |     Version:
 Severity:  minor                                |  Resolution:
 Keywords:  needs-patch needs-unit-tests needs-  |     Focuses:
  dev-note php8 needs-docs                       |
-------------------------------------------------+-------------------------
Changes (by milana_cap):

 * keywords:  needs-patch needs-unit-tests needs-dev-note needs-codex php8
     => needs-patch needs-unit-tests needs-dev-note php8 needs-docs


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49728#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 15:52:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 15:52:44 -0000
Subject: [wp-trac] [WordPress Trac] #49760: Twenty Fifteen: Add gradient
 background options that fit the theme color scheme
In-Reply-To: <055.4dbf0f6607ab62354dd71eb4ff739b6a@wordpress.org>
References: <055.4dbf0f6607ab62354dd71eb4ff739b6a@wordpress.org>
Message-ID: <070.e651f8ec65b2e42643083ce3858286d8@wordpress.org>

#49760: Twenty Fifteen: Add gradient background options that fit the theme color
scheme
-------------------------------------------------+-------------------------
 Reporter:  ianbelanger                          |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  good-first-bug has-patch commit      |     Focuses:  ui
  needs-codex                                    |
-------------------------------------------------+-------------------------
Changes (by milana_cap):

 * keywords:  good-first-bug has-patch commit => good-first-bug has-patch
     commit needs-codex


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49760#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 15:54:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 15:54:40 -0000
Subject: [wp-trac] [WordPress Trac] #49762: Twenty Thirteen: Add
 gradient background options that fit the theme color scheme
In-Reply-To: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
References: <055.86bd25ea1734196a3534b540687f4391@wordpress.org>
Message-ID: <070.58e5806fb7a3435983d2327ff1c3b01d@wordpress.org>

#49762: Twenty Thirteen: Add gradient background options that fit the theme color
scheme
-------------------------------------------------+-------------------------
 Reporter:  ianbelanger                          |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-screenshots commit     |     Focuses:  ui, css
  needs-codex                                    |
-------------------------------------------------+-------------------------
Changes (by milana_cap):

 * keywords:  has-patch has-screenshots commit => has-patch has-screenshots
     commit needs-codex


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49762#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 16:11:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 16:11:18 -0000
Subject: [wp-trac] [WordPress Trac] #53951: Twenty Twenty: Search modal
 aria-expanded
In-Reply-To: <050.12159b56833732edace4c7af59831987@wordpress.org>
References: <050.12159b56833732edace4c7af59831987@wordpress.org>
Message-ID: <065.bf85147e04ed608a0b1fc02fb7ad4651@wordpress.org>

#53951: Twenty Twenty: Search modal aria-expanded
-------------------------------------+-------------------------------------
 Reporter:  utz119                   |       Owner:  alexstine
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-testing-   |     Focuses:  accessibility,
  instructions dev-feedback          |  javascript
-------------------------------------+-------------------------------------
Changes (by afercia):

 * Attachment "53951.2.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53951>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 16:18:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 16:18:38 -0000
Subject: [wp-trac] [WordPress Trac] #53951: Twenty Twenty: Search modal
 aria-expanded
In-Reply-To: <050.12159b56833732edace4c7af59831987@wordpress.org>
References: <050.12159b56833732edace4c7af59831987@wordpress.org>
Message-ID: <065.e6ffa62263e45f061a70ed3c0c72a4d9@wordpress.org>

#53951: Twenty Twenty: Search modal aria-expanded
-------------------------------------+-------------------------------------
 Reporter:  utz119                   |       Owner:  alexstine
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-testing-   |     Focuses:  accessibility,
  instructions needs-testing         |  javascript
-------------------------------------+-------------------------------------
Changes (by afercia):

 * keywords:  has-patch has-testing-instructions dev-feedback => has-patch
     has-testing-instructions needs-testing


Comment:

 Looking a bit into this issue, seems to me the root problem is that `aria-
 expanded` needs to be handled on multiple elements at once. Ideally, the
 state of the toggle search buttons for mobile and desktop should be
 synced.

 [attachment:"53951.2.diff"] changes the `twentytwentyToggleAttribute`
 function so that:
 - It selects all the toggles with the same `data-toggle-target` attribute
 of the passed element.
 - Loops through the collected toggles to update their aria-expanded
 attribute.

 I kept the role="dialog" added in previous patches and also added an aria-
 label to the dialog.

 Some testing would be greatly appreciated. Things to test:
 - Both the desktop and mobile Search toggle buttons get their aria-
 expanded attribute updated, in all cases: click, Escape key press, click
 outside. On both the desktop and responsive view.
 - Check the mobile menu toggle still works as expected.
 - Check the mobile sub-menus toggles still work as expected.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53951#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 16:21:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 16:21:25 -0000
Subject: [wp-trac] [WordPress Trac] #41445: post_parent can prevent
 media from embedding correctly
In-Reply-To: <051.36e9b448a18da0e6248fb03458b3410b@wordpress.org>
References: <051.36e9b448a18da0e6248fb03458b3410b@wordpress.org>
Message-ID: <066.ebee1892dec2f5e5d10fcb7fdc8a6954@wordpress.org>

#41445: post_parent can prevent media from embedding correctly
-------------------------------------------------+-------------------------
 Reporter:  loboyle                              |       Owner:
                                                 |  adamsilverstein
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.9.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing dev-         |     Focuses:  rest-api
  feedback needs-unit-tests has-testing-info     |
-------------------------------------------------+-------------------------

Comment (by Krstarica):

 @galbaras has a point. There are several ways media can be handled:
 1) Upload media during post editing
 2) Add existing media in the new post
 3) Upload media using Media Library, then use it in the post
 4) Reference existing media using custom field/plugin

 WordPress creates relationship between media and post for (1) scenario
 only. This should be definitely reviewed (in the new ticket?)

 In the meantime we should probably completely remove post_parent check,
 because we don't have a clue whether media is added to the post using (2),
 (3) and (4) scenario.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41445#comment:47>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 16:23:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 16:23:22 -0000
Subject: [wp-trac] [WordPress Trac] #32747: WP Admin Menus/SubMenus
 Overlap in small screen
In-Reply-To: <053.19f81590b59ff77c2a9b31983b4caf91@wordpress.org>
References: <053.19f81590b59ff77c2a9b31983b4caf91@wordpress.org>
Message-ID: <068.4f7c1d5f973dc48692252f6d49c4d168@wordpress.org>

#32747: WP Admin Menus/SubMenus Overlap in small screen
-------------------------------------+-------------------------------------
 Reporter:  turtlepod                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Administration           |     Version:  4.2.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  ui, accessibility, css
-------------------------------------+-------------------------------------
Changes (by ryokuhi):

 * keywords:  has-patch => has-patch needs-testing


Comment:

 We reviewed this ticket today during the Accessibility Team's weekly bug-
 scrub.
 The PR probably needs to be refreshed, as there are changes to the
 `package-lock.json` file which should not be included with the patch.
 Still, I'm adding the `needs-testing`  label to bring a few extra eyes on
 this ticket to see if it solves the issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32747#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 16:38:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 16:38:02 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.65fe3b78a6120f0455878423f6677413@wordpress.org>

#41136: Login forms lacking autocomplete attributes
------------------------------+--------------------------------------------
 Reporter:  johnjamesjacoby   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  6.0
Component:  Login and         |     Version:
  Registration                |
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  accessibility, administration
------------------------------+--------------------------------------------
Changes (by joedolson):

 * owner:  (none) => joedolson
 * status:  new => accepted


Comment:

 From a technical standpoint, using any autocomplete on any field anywhere
 introduces the same security issue, so I'm not sure to what degree we
 should take responsibility for that. Any software can be used in both a
 private and a shared environment.

 There's a relevant conversation here:
 https://github.com/w3c/wcag/issues/2110

 One thing I think this will need is to provide a filter so that
 autocomplete can be disabled; sites with higher security needs might need
 an easy way to disable this feature.

 Overall, however, I think this is more of a benefit than a potential for
 harm. Would benefit from some additional voices on the security side,
 however.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 16:44:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 16:44:27 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.40d5ff38fec9c685d50236fc743e37a7@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
---------------------------------------------+------------------------
 Reporter:  pbearne                          |       Owner:  flixos90
     Type:  enhancement                      |      Status:  reviewing
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+------------------------
Changes (by flixos90):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests commit


Comment:

 This is good to go I think. I'm planning to commit it next week.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 16:46:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 16:46:56 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.42cf2ea75875e6d14d3dfe6fde79c157@wordpress.org>

#55439: Introduce term_exists_args filter
--------------------------------------+---------------------------
 Reporter:  Chouby                    |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  trunk
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch needs-dev-note  |     Focuses:
--------------------------------------+---------------------------

Comment (by SergeyBiryukov):

 In [changeset:"52991" 52991]:
 {{{
 #!CommitTicketReference repository="" revision="52991"
 Docs: Adjust the `term_exists_default_query_args` filter docs per the
 documentation standards.

 Follow-up to [52987].

 See #55439.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 16:51:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 16:51:21 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.b88b535f6eb4ebf9d6ff9500b14aed8c@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52992" 52992]:
 {{{
 #!CommitTicketReference repository="" revision="52992"
 Docs: Use third-person singular verbs for function descriptions in `wp-
 includes/taxonomy.php`, per the documentation standards.

 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 17:29:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 17:29:13 -0000
Subject: [wp-trac] [WordPress Trac] #46600: Twenty Nineteen: Flex order
 on comment form causes contents of comment_form_after to appear above the
 form
In-Reply-To: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
References: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
Message-ID: <074.ad6bb4abc01d9235989b60ff0ce4775b@wordpress.org>

#46600: Twenty Nineteen: Flex order on comment form causes contents of
comment_form_after to appear above the form
-------------------------------------+---------------------------------
 Reporter:  garrett-eclipse          |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:  5.0
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  accessibility, css
-------------------------------------+---------------------------------
Changes (by sabernhardt):

 * keywords:  has-patch => has-patch needs-testing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46600#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 17:31:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 17:31:46 -0000
Subject: [wp-trac] [WordPress Trac] #55465: Fix hiding playlist buttons from
 Add Media modal dialog
Message-ID: <050.9ad45b6ab193d23ba29b02fdabcee22e@wordpress.org>

#55465: Fix hiding playlist buttons from Add Media modal dialog
-------------------------------------+-----------------------------
 Reporter:  erengy                   |      Owner:  (none)
     Type:  defect (bug)             |     Status:  new
 Priority:  normal                   |  Milestone:  Awaiting Review
Component:  Media                    |    Version:  5.9.2
 Severity:  minor                    |   Keywords:
  Focuses:  ui, css, administration  |
-------------------------------------+-----------------------------
 ==== How to reproduce

 On a fresh installation of WordPress 5.9.2 with
 [[https://wordpress.org/plugins/classic-editor/|Classic Editor]] plugin
 enabled, add the following lines to the default theme's `functions.php`:

 {{{#!php
 <?php
 add_filter('media_library_show_audio_playlist', '__return_false');
 add_filter('media_library_show_video_playlist', '__return_false');
 }}}

 Then go to `/wp-admin/post-new.php` and click the Add Media button.

 These filters are supposed to allow hiding the
 [[https://developer.wordpress.org/reference/hooks/media_library_show_audio_playlist/|Create
 Audio Playlist]] and
 [[https://developer.wordpress.org/reference/hooks/media_library_show_video_playlist/|Create
 Video Playlist]] buttons, which is not the case. The buttons are still
 visible in the Add Media modal dialog.

 Workarounds include filtering `media_view_strings` instead, or enqueing
 additional styles to hide the buttons.

 The discussion at Ticket [ticket:43009] focuses on the behavior //after//
 uploading an audio/video file rather than the initial state, hence the new
 ticket.

 ==== Reason

 ✅ **PHP:**
 [[https://developer.wordpress.org/reference/functions/wp_enqueue_media/|wp_enqueue_media]]
 function sets `attachmentCounts` according to the filter results.

 ✅ **JavaScript:** `menuItemVisibility` function is called, which adds
 `hidden` class to the elements.

 ❌ **CSS:** In `media-views.css`, `.media-menu .media-menu-item` selector
 wins over `.media-frame .hidden`, setting the elements' `display` property
 to `block` instead of `none`.

 ==== Proposed fix

 Since there are similar rules of higher specificity (e.g. `.attachments-
 browser .uploader-inline.hidden`, `.media-embed .setting input.hidden`) in
 the same CSS file, I thought adding the following rule would be
 appropriate:

 {{{#!css
 .media-menu .media-menu-item.hidden {
         display: none;
 }
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55465>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 17:45:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 17:45:37 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.2959aaab61ee704f0ad1464bb97637af@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots has-testing-info                   |  accessibility
-------------------------------------------------+-------------------------

Comment (by Clorith):

 This makes sense from my end as well, once you are done cropping the
 interface also now shows the cropped version and its data so that covers
 my original concerns as well, so looks good!

 (And can i say thank you for those amazing test scenarios and the details
 they provide, I am loving them!)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 17:51:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 17:51:15 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.fb1fb8827c77eb05a4eb14bcc6629f54@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots has-testing-info commit            |  accessibility
-------------------------------------------------+-------------------------
Changes (by joedolson):

 * keywords:  has-patch has-unit-tests has-screenshots has-testing-info =>
     has-patch has-unit-tests has-screenshots has-testing-info commit


Comment:

 Awesome! Let's get this moving! I'm marking for commit; I'll do a final
 review and take care of this soon.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 17:55:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 17:55:46 -0000
Subject: [wp-trac] [WordPress Trac] #55464: W3C compatible
In-Reply-To: <053.b101c89d5d302887f49f2e1133e5bff3@wordpress.org>
References: <053.b101c89d5d302887f49f2e1133e5bff3@wordpress.org>
Message-ID: <068.20b3c4ebf6611d0cdef46813e5613887@wordpress.org>

#55464: W3C compatible
-------------------------------+------------------------------
 Reporter:  spink9010          |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  General            |     Version:  5.9.2
 Severity:  normal             |  Resolution:
 Keywords:  close 2nd-opinion  |     Focuses:  template
-------------------------------+------------------------------
Changes (by sabernhardt):

 * keywords:  needs-testing => close 2nd-opinion
 * focuses:   => template


Comment:

 Hi and welcome to Trac!

 A3 Lazy Load has a GitHub repository for development and reporting issues
 with the plugin. [https://github.com/a3rev/a3-lazy-load/issues/30 Issue
 #30] addresses the `srcset`, if you would like to add any comments there.

 Regarding the search form, #16539 and #23850 already replaced the
 `searchsubmit` ID with a `search-submit` class for any theme that supports
 HTML5 and uses the default search form. The `get_search_form()` function
 retained the ID for compatibility with older themes. Because
 [https://wpdirectory.net/search/01FZ0VGSN74Q042AT6BVPS57P6 many themes
 still use the ID selector] and would break if the ID is either changed or
 removed, I think the function needs to keep that.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55464#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 18:43:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 18:43:48 -0000
Subject: [wp-trac] [WordPress Trac] #37057: Creation of an esc_html
 functions for _n(), _nx(), _ex(), and number_format_i18n()
In-Reply-To: <051.927fde7eb9770090aac47ffe99674f7d@wordpress.org>
References: <051.927fde7eb9770090aac47ffe99674f7d@wordpress.org>
Message-ID: <066.3a6864ef9cb48cdefc012692eaac1de5@wordpress.org>

#37057: Creation of an esc_html functions for _n(), _nx(), _ex(), and
number_format_i18n()
-------------------------+------------------------------
 Reporter:  zakkath      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  I18N         |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+------------------------------

Comment (by malthert):

 +1 from me.

 {{{#!php
 <?php
 // random to give a simple example
 $count = rand( 1, 10 );
 $color = rand( 1, 100 ) % 2 === 0 ? 'green' : 'blue';

 printf( esc_html_n( '%s elephant', '%s elephants', $count, 'textdomain' ),
 esc_html( $color ) );

 // or also for cases like:
 printf( _n( '%d years, %d month', '%d years, %d months', $diff->m,
 'customnew' ), esc_html( $diff->y ), esc_html( $diff->m ) )
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37057#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 18:58:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 18:58:32 -0000
Subject: [wp-trac] [WordPress Trac] #53318: FTPext method exists()
 returns always false for files!
In-Reply-To: <050.cd9a40e2a7be30b2d8eb40460ecf9ddd@wordpress.org>
References: <050.cd9a40e2a7be30b2d8eb40460ecf9ddd@wordpress.org>
Message-ID: <065.855f98657670c4ff8b41a68bdb630528@wordpress.org>

#53318: FTPext method exists() returns always false for files!
--------------------------------------+------------------------
 Reporter:  arl1nd                    |       Owner:  (none)
     Type:  defect (bug)              |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Filesystem API            |     Version:  5.7.2
 Severity:  normal                    |  Resolution:  duplicate
 Keywords:  needs-patch dev-feedback  |     Focuses:  docs
--------------------------------------+------------------------
Changes (by afragen):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  6.0 =>


Comment:

 Duplicate of #51170.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53318#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 20:07:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 20:07:36 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.df1831ecdf20a5a489d5c30ae2545210@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
-------------------------------------------------+-------------------------
 Reporter:  giox069                              |       Owner:  afragen
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Filesystem API                       |     Version:  3.7
 Severity:  normal                               |  Resolution:
 Keywords:  reporter-feedback dev-feedback has-  |     Focuses:
  patch needs-testing                            |
-------------------------------------------------+-------------------------
Changes (by afragen):

 * owner:  (none) => afragen
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 20:09:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 20:09:24 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.6098166f510e38dcae2c67586210b21e@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
--------------------------------------------------+-----------------------
 Reporter:  giox069                               |       Owner:  afragen
     Type:  defect (bug)                          |      Status:  assigned
 Priority:  normal                                |   Milestone:  6.0
Component:  Filesystem API                        |     Version:  3.7
 Severity:  normal                                |  Resolution:
 Keywords:  dev-feedback has-patch needs-testing  |     Focuses:
--------------------------------------------------+-----------------------
Changes (by afragen):

 * keywords:  reporter-feedback dev-feedback has-patch needs-testing => dev-
     feedback has-patch needs-testing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 21:03:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 21:03:23 -0000
Subject: [wp-trac] [WordPress Trac] #46600: Twenty Nineteen: Flex order
 on comment form causes contents of comment_form_after to appear above the
 form
In-Reply-To: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
References: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
Message-ID: <074.ceeb612e15c93edf2de627cebff71016@wordpress.org>

#46600: Twenty Nineteen: Flex order on comment form causes contents of
comment_form_after to appear above the form
-------------------------------------------------+-------------------------
 Reporter:  garrett-eclipse                      |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:  5.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing assigned-    |     Focuses:
  for-commit commit needs-dev-note               |  accessibility, css
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch needs-testing => has-patch needs-testing assigned-
     for-commit commit needs-dev-note


Comment:

 Thank you @sabernhardt for the changes.
 The pull request looks good to me know.
 Self assigning for `commit` and adding `needs-dev-note` keyword so this
 new class could be referenced on a Bundled Themes dev note or in the Misc
 changes dev note 📗

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46600#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 21:03:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 21:03:40 -0000
Subject: [wp-trac] [WordPress Trac] #46600: Twenty Nineteen: Flex order
 on comment form causes contents of comment_form_after to appear above the
 form
In-Reply-To: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
References: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
Message-ID: <074.0ee0d6e362f200825fd2ce15e9eeae0f@wordpress.org>

#46600: Twenty Nineteen: Flex order on comment form causes contents of
comment_form_after to appear above the form
-------------------------------------------------+-------------------------
 Reporter:  garrett-eclipse                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:  5.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing assigned-    |     Focuses:
  for-commit commit needs-dev-note               |  accessibility, css
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => accepted


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46600#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 21:19:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 21:19:00 -0000
Subject: [wp-trac] [WordPress Trac] #46600: Twenty Nineteen: Flex order
 on comment form causes contents of comment_form_after to appear above the
 form
In-Reply-To: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
References: <059.a50e0718d76d3d9bf46bc990767438c3@wordpress.org>
Message-ID: <074.1e97e3fae4e9ccabc3c08cac8daefc27@wordpress.org>

#46600: Twenty Nineteen: Flex order on comment form causes contents of
comment_form_after to appear above the form
-------------------------------------------------+-------------------------
 Reporter:  garrett-eclipse                      |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Bundled Theme                        |     Version:  5.0
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch needs-testing assigned-    |     Focuses:
  for-commit commit needs-dev-note               |  accessibility, css
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52993" 52993]:
 {{{
 #!CommitTicketReference repository="" revision="52993"
 Twenty Nineteen: Override flex order in comment form.

 This change updates Twenty Nineteen bundled theme to fix the DOM order in
 the comment form, and to add a new `.comment-form-wrapper` class to change
 `flex` display to `block` for this specific area.

 Props garrett-eclipse, audrasjb, sabernhardt.
 Fixes #46600.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46600#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 21:21:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 21:21:31 -0000
Subject: [wp-trac] [WordPress Trac] #53234: Application password access
 text is misleading for Super Admins
In-Reply-To: <055.0e9d1b8f7ea2e3fdeb10ed7ba49893b2@wordpress.org>
References: <055.0e9d1b8f7ea2e3fdeb10ed7ba49893b2@wordpress.org>
Message-ID: <070.d0f1a2364bd03bb2828f303106cf2d2d@wordpress.org>

#53234: Application password access text is misleading for Super Admins
--------------------------------------+------------------------
 Reporter:  johnbillion               |       Owner:  audrasjb
     Type:  defect (bug)              |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Application Passwords     |     Version:  5.6
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  multisite
--------------------------------------+------------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => reviewing


Comment:

 Thanks for updating the patch!
 Self assigning for review.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53234#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 21:33:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 21:33:05 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.bcdfe0d4dcfdc5c56e324dd2b7da661d@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by audrasjb):

 In [changeset:"52994" 52994]:
 {{{
 #!CommitTicketReference repository="" revision="52994"
 Docs: Use third-person singular verbs for function descriptions in `wp-
 includes/rewrite.php`, per the documentation standards.

 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:47>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 21:33:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 21:33:27 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.6373277ecd274272ea2e73de27ab96a9@wordpress.org>

#55337: Optimize preload paths for post and site editors
------------------------------+-----------------------
 Reporter:  jsnajdr           |       Owner:  audrasjb
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  5.9.3
Component:  Editor            |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch commit
 * owner:  (none) => audrasjb
 * status:  new => accepted


Comment:

 Self assigning for commit 👍

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55337#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 21:48:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 21:48:59 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.79d8cb96e0d339734bd5b4db67dc7e7e@wordpress.org>

#55337: Optimize preload paths for post and site editors
------------------------------+-----------------------
 Reporter:  jsnajdr           |       Owner:  audrasjb
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  5.9.3
Component:  Editor            |     Version:  trunk
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52995" 52995]:
 {{{
 #!CommitTicketReference repository="" revision="52995"
 Editor: Optimize preload paths for post and site editors.

 This patch optimizes preload paths in post and site editors so that they
 match the real requests:

 - Remove the `/` preload as the payload is very big and the response is
 not needed on any critical path.
 - Modify the preloaded path for `/wp/v2/taxonomies` so that it corresponds
 to what `loadTaxonomyEntities` requests. After Gutenberg PR 37685 was
 merged to core, these preloads need to be modified to use `context=view`
 instead of `context=edit`.
 - Modify the `/wp/v2/users/me path` so that it matches the real request
 (no query params).
 - Add a preload of `/wp/v2/settings` because it is requested on critical
 path (editor boot). Site editor already preloads this, the changeset is
 only adding it to the post editor.

 This is related to Gutenberg PR 39256 which introduces compatibility code
 to modify the preload paths with a filter, when the Gutenberg plugin is
 active.

 See https://github.com/WordPress/gutenberg/pull/39256.

 Props jsnajdr, noisysocks.
 Fixes #55337.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55337#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Fri Mar 25 21:51:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Fri, 25 Mar 2022 21:51:10 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.cb1ef7ea731abc3b260e2b09143acb48@wordpress.org>

#55337: Optimize preload paths for post and site editors
-----------------------------------+-----------------------
 Reporter:  jsnajdr                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  reopened
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Editor                 |     Version:  trunk
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch commit => has-patch fixed-major
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for backport consideration.

 Before merging this to branch 5.9, @noisysocks shouldn't we also backport
 the changes introduced in the Gutenberg PRs mentioned above?

 (ping @mamaduka)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55337#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 02:50:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 02:50:29 -0000
Subject: [wp-trac] [WordPress Trac] #54547: Fatal error when updating to
 5.9 Beta 1 using WP-CLI on LocalWP
In-Reply-To: <054.267100f5e53757c2d940584c469abb13@wordpress.org>
References: <054.267100f5e53757c2d940584c469abb13@wordpress.org>
Message-ID: <069.7a8d160f8eb43e2cff157eeb49453553@wordpress.org>

#54547: Fatal error when updating to 5.9 Beta 1 using WP-CLI on LocalWP
-----------------------------+---------------------
 Reporter:  nielslange       |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:
 Severity:  blocker          |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+---------------------

Comment (by afragen):

 I believe this issue was fixed in WP-CLI 2.6.0, which happens to be
 included in latest LocalWP.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54547#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 02:59:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 02:59:53 -0000
Subject: [wp-trac] [WordPress Trac] #55385: Error in Search
In-Reply-To: <061.caa3b2cb4d146df3b0520cddfdc2b8c5@wordpress.org>
References: <061.caa3b2cb4d146df3b0520cddfdc2b8c5@wordpress.org>
Message-ID: <076.d2b5fca113d22ed0d261047256b21a25@wordpress.org>

#55385: Error in Search
-------------------------------+------------------------------
 Reporter:  himanshushokhanda  |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Posts, Post Types  |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by erengy):

 This is likely related to Apache's ModSecurity module rather than
 WordPress. `.profile` is a
 [[https://github.com/coreruleset/coreruleset/blob/0eb7fafbc8093097524d3376bc33c5b882c160ba/rules
 /restricted-files.data#L46|restricted filename]] at OWASP ModSecurity Core
 Rule Set.

 See also: https://serverfault.com/questions/932614/apache-issue-with-
 profile-in-the-url

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55385#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 03:20:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 03:20:23 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.249c72d04c127e18b816b405c3001103@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
------------------------------+-----------------------
 Reporter:  giox069           |       Owner:  afragen
     Type:  defect (bug)      |      Status:  assigned
 Priority:  normal            |   Milestone:  6.0
Component:  Filesystem API    |     Version:  3.7
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------
Changes (by costdev):

 * keywords:  dev-feedback has-patch needs-testing => has-patch commit


Comment:

 This ticket proposes making `WP_Filesystem_FTPext::exists()` and
 `WP_Filesystem_ftpsockets` compliant with RFC 959 by only using NLST on
 directories, rather than on both directories and files.

 -----

 Using `ftp_nlist()` requires checking an array. As the number of files in
 the directory are unknown, this approach has inconsistent performance.

 Using `ftp_size()` looks like a better option. While the
 [https://www.php.net/manual/en/function.ftp-size.php PHP Manual] says that
 it may not be available on all servers, I spoke to @rawrly in the
 #hosting-community channel who believes that this may be because the FTP
 `SIZE` command was introduced in 2002 and in the years that followed, this
 may not have been enabled by some. However, this is believed to be less
 and less likely as things move towards sFTP.

 -----

 [https://github.com/WordPress/wordpress-develop/pull/2460 PR 2460] uses:
 - `WP_Filesystem_FTPext::is_dir()` and
 `WP_Filesystem_FTPsockets::is_dir()` to check for a directory.
 - `WP_Filesystem_FTPext::size()` (which uses `ftp_size()` internally) to
 check for a file.
 - `WP_Filesystem_ftpsockets::size()` (which uses
 [https://core.trac.wordpress.org/browser/tags/5.9/src/wp-admin/includes
 /class-ftp.php#L420 ftp_base::filesize] internally) to check for a file.

 This approach seems sound to me, as the respective `::is_dir()` and
 `::size()` should be returning accurate results.

 -----

 I've tested [https://github.com/WordPress/wordpress-develop/pull/2460 PR
 2460] with `FS_METHOD` set to `ftpext` and `ftpsockets`.

 In both cases, these were the results when using the respective
 `::exists()` method:
 ||= **Test** =||= **Result** =||
 || A directory that exists || true ||
 || An empty hidden file || true ||
 || A non-empty hidden file || true ||
 || An empty file || true ||
 || A non-empty file || true ||
 || A directory that does not exist || false ||
 || A file that does not exist || false ||

 -----

 In addition, the following Dashboard actions continue to work as expected
 for both `ftpext` and `ftpsockets`:

 **Plugins**
 - Install plugin from dot org
 - Install plugin from .zip
 - Delete plugin via Dashboard

 **Themes**
 - Install theme from dot org
 - Install theme from .zip
 - Delete theme via Dashboard

 **Media**
 - Upload image via Media Library
 - Delete image via Media Library

 -----

 Nominating [https://github.com/WordPress/wordpress-develop/pull/2460 PR
 2460] as a `commit` candidate.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 04:03:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 04:03:21 -0000
Subject: [wp-trac] [WordPress Trac] #55466: Build Tools: create Docker test
 environment that use non-direct filesystems
Message-ID: <051.27302f5abe717f3ad7c97284b687ab6d@wordpress.org>

#55466: Build Tools: create Docker test environment that use non-direct filesystems
------------------------------+-----------------------------
 Reporter:  afragen           |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  Build/Test Tools  |    Version:
 Severity:  normal            |   Keywords:  dev-feedback
  Focuses:                    |
------------------------------+-----------------------------
 Recently when writing a PR for #51170, @costdev and I, mostly Colin as I
 let him do this, had a somewhat difficult time setting up a testing
 environment that used FTPext or FTPsockets.

 It would be awesome if this could be built into a Docker image for testing
 with WordPress-develop.

 If this can be done it might be worthwhile to setup environments for the
 other file system methods too.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55466>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 04:14:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 04:14:08 -0000
Subject: [wp-trac] [WordPress Trac] #55466: Build Tools: create Docker
 test environment that use non-direct filesystems
In-Reply-To: <051.27302f5abe717f3ad7c97284b687ab6d@wordpress.org>
References: <051.27302f5abe717f3ad7c97284b687ab6d@wordpress.org>
Message-ID: <066.10f84487a02b5f0ab877ac40748e1d7f@wordpress.org>

#55466: Build Tools: create Docker test environment that use non-direct filesystems
------------------------------+------------------------------
 Reporter:  afragen           |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  dev-feedback      |     Focuses:
------------------------------+------------------------------

Comment (by costdev):

 This was what was I used to get `ftpext`/`ftpsockets` working:

 - An FTP server: I used `vsftpd` on Ubuntu.
 - FTP `write` permissions: This involves uncommenting `# write_enable=YES`
 in `/etc/vsftpd.conf`.
 - Write access to the necessary folders (i.e. `Site Health > Info > File
 system permissions`).
 - A new user for FTP:
 {{{#!sh
 sudo useradd FTP_USER
 sudo passwd FTP_USER
 (enter password):
 }}}
 - Entries in `wp-config.php`:
 {{{#!php
 define( 'FS_METHOD', 'ftpext' ); // Or 'ftpsockets'.

 define( 'FTP_BASE', '/var/www/html/wordpress-develop/src/' );
 define( 'FTP_USER', 'FTP_USER' );
 define( 'FTP_PASS', 'password' );
 define( 'FTP_HOST', 'localhost' );
 define( 'FTP_SSL', false );
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55466#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 04:35:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 04:35:50 -0000
Subject: [wp-trac] [WordPress Trac] #54983: The post has already been
 deleted.
In-Reply-To: <054.b565d5fc304533066dbe4bca29195998@wordpress.org>
References: <054.b565d5fc304533066dbe4bca29195998@wordpress.org>
Message-ID: <069.c993cd7665fe034ee7d2544cac64c5a5@wordpress.org>

#54983: The post has already been deleted.
-------------------------------------------------+-------------------------
 Reporter:  sumitsingh                           |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Posts, Post Types                    |     Version:  5.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch has-       |     Focuses:
  testing-info needs-testing                     |  administration
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  has-screenshots => has-screenshots has-patch has-testing-info
     needs-testing
 * version:  5.9 => 5.4
 * severity:  major => normal


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54983#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 04:54:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 04:54:26 -0000
Subject: [wp-trac] [WordPress Trac] #51096: Meta boxes hooked on
 'edit_form_after_title' don't appear on block-editor page
In-Reply-To: <050.a403877d122307fd40d7fe34ed3c9928@wordpress.org>
References: <050.a403877d122307fd40d7fe34ed3c9928@wordpress.org>
Message-ID: <065.edc2b181a7086717e55e09df37bd5cd8@wordpress.org>

#51096: Meta boxes hooked on 'edit_form_after_title' don't appear on block-editor
page
--------------------------+----------------------
 Reporter:  apedog        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by costdev):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  6.0 =>


Comment:

 - This issue was not able to be reproduced.
 - There are
 [https://github.com/wordpress/gutenberg/issues?q=is%3Aissue+metaboxes+position+is%3Aclosed
 numerous closed issues] on the Gutenberg repository that mention metabox
 positioning. Without more information, it's not clear which, if any, of
 these issues may relate to the reported issue.
 - If this is still an issue and can be reproduced, this should be
 discussed on the [https://github.com/wordpress/gutenberg/issues Gutenberg
 repository].

 Given all of the above, I'll close this ticket as `invalid`, but if an
 existing Gutenberg issue deals with this problem, or a new issue is
 reported, drop a link into this ticket and change the resolution to
 `reported-upstream`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51096#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 04:54:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 04:54:56 -0000
Subject: [wp-trac] [WordPress Trac] #51096: Meta boxes hooked on
 'edit_form_after_title' don't appear on block-editor page
In-Reply-To: <050.a403877d122307fd40d7fe34ed3c9928@wordpress.org>
References: <050.a403877d122307fd40d7fe34ed3c9928@wordpress.org>
Message-ID: <065.208b0e4a78526ecc260d9bc37ad49aaa@wordpress.org>

#51096: Meta boxes hooked on 'edit_form_after_title' don't appear on block-editor
page
--------------------------+-------------------------
 Reporter:  apedog        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:  worksforme
 Keywords:                |     Focuses:
--------------------------+-------------------------
Changes (by costdev):

 * resolution:  invalid => worksforme


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51096#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 05:53:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 05:53:51 -0000
Subject: [wp-trac] [WordPress Trac] #41445: post_parent can prevent
 media from embedding correctly
In-Reply-To: <051.36e9b448a18da0e6248fb03458b3410b@wordpress.org>
References: <051.36e9b448a18da0e6248fb03458b3410b@wordpress.org>
Message-ID: <066.f79e01b688acafcf4e57d8b2f17905cf@wordpress.org>

#41445: post_parent can prevent media from embedding correctly
-------------------------------------------------+-------------------------
 Reporter:  loboyle                              |       Owner:
                                                 |  adamsilverstein
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.9.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing dev-         |     Focuses:  rest-api
  feedback needs-unit-tests has-testing-info     |
-------------------------------------------------+-------------------------

Comment (by galbaras):

 There are also scenarios where the same image is included in more than one
 post, of which only one is inaccessible. Currently, if post_parent is
 inaccessible, that's the end of the road (false negative), and if it's
 accessible, this might be a problem (false positive).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41445#comment:48>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 06:45:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 06:45:49 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
In-Reply-To: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
References: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
Message-ID: <066.ba3c9847b285f61359559409600e86e7@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
--------------------------------------+----------------------------
 Reporter:  crs1138                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Formatting                |     Version:  5.8.3
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  accessibility
--------------------------------------+----------------------------

Comment (by mukesh27):

 Thanks for the patch!

 Using which method do you have created the patch?

 If you're doing a first time contribution then check these links in order
 to create a valid patch in Trac.

 https://make.wordpress.org/core/handbook/tutorials/working-with-patches/
 https://make.wordpress.org/core/handbook/best-practices/writing-patches/

 If you're familiar with code and git, you can use the wordpress-develop
 Github repository to easily contribute to WordPress:
 https://make.wordpress.org/core/handbook/contribute/git/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55370#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 06:46:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 06:46:26 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
In-Reply-To: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
References: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
Message-ID: <066.8890fbf8d094e12e2ce5dc4453c7bd37@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
--------------------------------------+----------------------------
 Reporter:  crs1138                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Formatting                |     Version:  5.8.3
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  accessibility
--------------------------------------+----------------------------
Changes (by mukesh27):

 * Attachment "55370.patch" added.

 Working patch

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55370>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 07:39:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 07:39:00 -0000
Subject: [wp-trac] [WordPress Trac] #55456: Double escaping
 wp_user-settings
In-Reply-To: <053.4e95668003a2859da7231085e66ad927@wordpress.org>
References: <053.4e95668003a2859da7231085e66ad927@wordpress.org>
Message-ID: <068.9e75391683d1f4db03432db58fcfe1e4@wordpress.org>

#55456: Double escaping wp_user-settings
-------------------------------------------------+-------------------------
 Reporter:  phatkoala                            |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:  2.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback has-testing-  |     Focuses:
  info needs-testing                             |
-------------------------------------------------+-------------------------

Comment (by azouamauriac):

 Hi thanks for test report, and thanks @phatkoala for the PR

 Replying to [comment:3 costdev]:
 > 2. [https://github.com/WordPress/wordpress-develop/pull/2458 PR 2458]
 resolves the issue. ✅
 He updated the PR, and when I tested it, here is the result:
 [https://github.com/WordPress/wordpress-
 develop/pull/2458/commits/11713240ed17512f5a792ee9194000bfc2400b72 before
 the last PR: ][https://prnt.sc/Bej0-MVvbgSj] ;
 [https://github.com/WordPress/wordpress-
 develop/pull/2458/commits/11713240ed17512f5a792ee9194000bfc2400b72 after
 the last PR ] : [https://prnt.sc/ZZ53foh-Xs3b]; So I think you should use
 commit link instead of PR since it can be updated anytime and commiters
 can be involved in mistakes. I think it is [https://github.com/WordPress
 /wordpress-
 develop/pull/2458/commits/3df1812b5e25121e8c45000f0fc7584459c352a2 this
 commit] you have tested and agreed(I guess). I tested it too, and it fixes
 the bug, but I am not so fan of the way, while I am still thinking about
 how to fix it properly, I agree with the commit though.
 > 1. Introduced in [8784].
 IMO the bug is due to [https://prnt.sc/xNaBmE9cCBQA this line] in this
 function
 [https://prnt.sc/SZ75h7yPGkum WP_User::__get]
 (if you comment [https://prnt.sc/xNaBmE9cCBQA this line] everything will
 work fine) introduced in [18597].
 Also, just for information, I've made some tests on 4.9.20 version and the
 bug is not present there, while it's present in 5.8 where I've done some
 tests too.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55456#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 09:18:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 09:18:27 -0000
Subject: [wp-trac] [WordPress Trac] #42486: The Tools screen is blank
 for users who cannot manage categories or tags
In-Reply-To: <055.732cdcd11cbc97b5d4f7bace3ca5d1de@wordpress.org>
References: <055.732cdcd11cbc97b5d4f7bace3ca5d1de@wordpress.org>
Message-ID: <070.732f0cf414d1245e1372d15ba6cf886e@wordpress.org>

#42486: The Tools screen is blank for users who cannot manage categories or tags
-------------------------------------------------+-------------------------
 Reporter:  johnbillion                          |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Administration                       |     Version:  4.9
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch 2nd-opinion has-           |     Focuses:
  screenshots                                    |
-------------------------------------------------+-------------------------

Comment (by paaljoachim):

 I see that this ticket has stalled.
 Should the top level Tools item just be hidden for now for user roles that
 only see the Tools title and a blank page until additional uses for the
 Tools screen can be tackled?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42486#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 09:52:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 09:52:27 -0000
Subject: [wp-trac] [WordPress Trac] #55316: Counter for total plugins is
 not updated after a plugin is deleted
In-Reply-To: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
References: <050.1150621b36fd5ab38c23cf605c504dee@wordpress.org>
Message-ID: <065.252c737a7775f300d93c8b8e0447e0b6@wordpress.org>

#55316: Counter for total plugins is not updated after a plugin is deleted
-------------------------------------------------+-------------------------
 Reporter:  mitogh                               |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Plugins                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-testing-info       |     Focuses:  ui,
  needs-refresh                                  |  administration
-------------------------------------------------+-------------------------

Comment (by kebbet):

 Sorry, the number function can not be used with JavaScript so just ignore
 that part of the ”suggestion ”.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55316#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 10:22:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 10:22:12 -0000
Subject: [wp-trac] [WordPress Trac] #55436: Image Galleries are NOT
 displayed properly on SAFARI
In-Reply-To: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
References: <052.2b28e3baf62cfffabf75ba80d6ef2802@wordpress.org>
Message-ID: <067.4257b4830c7f866dc03a9bed53f0cb1e@wordpress.org>

#55436: Image Galleries are NOT displayed properly on SAFARI
--------------------------+----------------------
 Reporter:  learnamo      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:
--------------------------+----------------------
Changes (by costdev):

 * keywords:  reporter-feedback =>
 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 @learnamo Great to hear! I'll close this ticket as `invalid` now that we
 know it's an issue with a plugin.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55436#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 15:26:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 15:26:29 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to
 allow for named parameters in WP 6.0
In-Reply-To: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
References: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
Message-ID: <072.d2daf4083f9524d1ba023681aded93b7@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
-----------------------------+---------------------
 Reporter:  peterwilsoncc    |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  php80 has-patch  |     Focuses:
-----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52996" 52996]:
 {{{
 #!CommitTicketReference repository="" revision="52996"
 Code Modernization: Rename parameters that use reserved keywords in `wp-
 admin/includes/class-ftp.php`.

 While using reserved PHP keywords as parameter name labels is allowed, in
 the context of function calls using named parameters in PHP 8.0+, this
 will easily lead to confusion. To avoid that, it is recommended not to use
 reserved keywords as function parameter names.

 This commit renames the `$string` parameter of
 `ftp_base::glob_pattern_match()` to `$subject`.

 Follow-up to [52946].

 Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
 See #55327.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55327#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 16:41:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 16:41:18 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.4360e1bc13444555ef57c64f12f7f6f1@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
------------------------------+-----------------------
 Reporter:  giox069           |       Owner:  afragen
     Type:  defect (bug)      |      Status:  assigned
 Priority:  normal            |   Milestone:  6.0
Component:  Filesystem API    |     Version:  3.7
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------

Comment (by pbiron):

 I've tested the PR with both `ftpext` and `ftpsockets` FS_METHOD and I get
 results consistent with @costdev (although I only tested in the context of
 the uses of `::exists()` that are exercised by `WP_Upgrader`).

 My only concern is the comment from @rawrly about `SIZE` not being
 implemented by some FTP servers.  For reference, the `SIZE` command was
 introduced in [https://datatracker.ietf.org/doc/html/rfc3659#section-4 RFC
 3659 - Extensions to FTP].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 17:40:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 17:40:30 -0000
Subject: [wp-trac] [WordPress Trac] #55370: Enable aria-controls and
 aria-expanded in content
In-Reply-To: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
References: <051.dc03991af641b6ff50232695165f265e@wordpress.org>
Message-ID: <066.b3511b0e0a3e3b65cbdbd71dc0d7b713@wordpress.org>

#55370: Enable aria-controls and aria-expanded in content
--------------------------------------+----------------------------
 Reporter:  crs1138                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Formatting                |     Version:  5.8.3
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  accessibility
--------------------------------------+----------------------------

Comment (by rsiddharth):

 Replying to [comment:7 mukesh27]:
 > Thanks for the patch!
 >
 > Using which method do you have created the patch?
 >
 > If you're doing a first time contribution then check these links in
 order to create a valid patch in Trac.
 >
 > https://make.wordpress.org/core/handbook/tutorials/working-with-patches/
 > https://make.wordpress.org/core/handbook/best-practices/writing-patches/
 >
 > If you're familiar with code and git, you can use the wordpress-develop
 Github repository to easily contribute to WordPress:
 https://make.wordpress.org/core/handbook/contribute/git/

 Thank you @mukesh27,

 I created the patch using `svn diff` as described in
 https://make.wordpress.org/core/handbook/tutorials/working-with-
 patches/#creating-a-patch-with-the-command-line

 I'm using the svn checkout at https://develop.svn.wordpress.org/trunk/ for
 creating the patches.

 From the patch you uploaded it looks like you're using
 https://core.svn.wordpress.org/trunk/

 The documentation at https://make.wordpress.org/core/handbook/tutorials
 /installing-wordpress-locally/from-svn/#1-2-using-command-line uses
 https://develop.svn.wordpress.org/trunk/ svn checkout.

 Which svn checkout is the correct one to use?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55370#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 17:43:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 17:43:09 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.c54970a7baafc33d04975ddc7a484f8f@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
------------------------------+-----------------------
 Reporter:  giox069           |       Owner:  afragen
     Type:  defect (bug)      |      Status:  assigned
 Priority:  normal            |   Milestone:  6.0
Component:  Filesystem API    |     Version:  3.7
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------

Comment (by costdev):

 As a safety, we could follow this flow:

 1. Check if it's a directory. If `true`, it exists. Return `true`.
 2. Check for the availability of the SIZE command.
   - As `ftp_size()` may still exist and be callable even when the SIZE
 command is not available, `function_exists()` or `is_callable()` wouldn't
 be effective here.
   - So how can we verify the SIZE command is available? What file do we
 know exists? Oh yeah, this one (`__FILE__`)
 3. If `ftp_size()` returns `-1` for `__FILE__`, we can fall back to
 `ftp_nlist()`.

 Like this (untested):

 {{{#!php
 // Use SIZE, if available.
 if ( -1 !== $this->size( __FILE__ ) ) {
    return -1 !== $this->size( $file );
 }

 // Run NLST on the directory.
 $dir   = dirname( $file );
 $files = ftp_nlist( $this->link, dir );

 return $files && in_array( $file, $files, true );
 }}}

 Thoughts on the approach?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 18:13:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 18:13:11 -0000
Subject: [wp-trac] [WordPress Trac] #55467:
 WP_REST_Meta_Fields::update_meta_value handles update_metadata return value
 incorrectly
Message-ID: <057.a09b8b8a818d0f8b9503e8ed33e08838@wordpress.org>

#55467: WP_REST_Meta_Fields::update_meta_value handles update_metadata return value
incorrectly
---------------------------+-----------------------------
 Reporter:  wordpressscyt  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  General        |    Version:  5.9
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 In the WP_REST_Meta_Fields::update_meta_value method the update_metadata
 function is used and handles every "false" return value from this function
 as an error.

 See https://github.com/WordPress/wordpress-
 develop/blob/0b800e21c311e302824e4a025946a6fdb4f6c794/src/wp-includes
 /rest-api/fields/class-wp-rest-meta-fields.php#L392

 update_metadata returns false if the value is not updated. That also
 happens if the old and new value are the same. Which is obviously not an
 error.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55467>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 18:39:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 18:39:17 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.62c6cd3c60c15a0f2945cd31fc1699b5@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
------------------------------+-----------------------
 Reporter:  giox069           |       Owner:  afragen
     Type:  defect (bug)      |      Status:  assigned
 Priority:  normal            |   Milestone:  6.0
Component:  Filesystem API    |     Version:  3.7
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------

Comment (by pbiron):

 I just found a [https://stackoverflow.com/a/16224707 StackOverflow reply]
 where someone who claims to be the author of particular FTP server
 software mentions that his FTP server specifically returns an error if the
 `SIZE` command is issued when `TYPE` is not `BINARY` :-(

 He quotes from the section about the `SIZE` command in the
 [https://datatracker.ietf.org/doc/html/rfc3659#section-4.2 RFC]:

   4.2.  Error Responses
   Where the command is correctly parsed but the size is not available,
   perhaps because the pathname identifies no existing entity or because
   the entity named cannot be transferred in the current MODE and TYPE
   (or at all), then a 550 reply should be sent.
   ....
   The presence of the 550 error response to a SIZE
   command MUST NOT be taken by the client as an indication that the
   file cannot be transferred in the current MODE and TYPE.  A server
   may generate this error for other reasons -- for instance if the
   processing overhead is considered too great.

 note: the server responding with anything other than a `213` response code
 will result in `ftp_size()` returning `-1`...see the
 [https://github.com/php/php-
 src/blob/efbb2198d4e5a01167d1a8c2937b848f75ac4d19/ext/ftp/ftp.c#L1120 PHP
 source for ftp_size()].

 So, maybe using `ftp_size()` to check for file existence is **not** a
 viable approach?  Of course, I'm not saying that we shouldn't use
 it...just try to make sure we don't introduce other problems with this
 "fix".

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 20:14:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 20:14:00 -0000
Subject: [wp-trac] [WordPress Trac] #55467:
 WP_REST_Meta_Fields::update_meta_value handles update_metadata return value
 incorrectly
In-Reply-To: <057.a09b8b8a818d0f8b9503e8ed33e08838@wordpress.org>
References: <057.a09b8b8a818d0f8b9503e8ed33e08838@wordpress.org>
Message-ID: <072.1463ad2463fff7d2e5a15ea77268152f@wordpress.org>

#55467: WP_REST_Meta_Fields::update_meta_value handles update_metadata return value
incorrectly
--------------------------------+-----------------------------
 Reporter:  wordpressscyt       |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Future Release
Component:  Options, Meta APIs  |     Version:  5.9
 Severity:  normal              |  Resolution:
 Keywords:  needs-patch         |     Focuses:  rest-api
--------------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * keywords:   => needs-patch
 * focuses:   => rest-api
 * component:  General => Options, Meta APIs
 * milestone:  Awaiting Review => Future Release


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55467#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 21:42:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 21:42:17 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.b4682c1c3473092eb6bd948bef0012da@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
------------------------------+-----------------------
 Reporter:  giox069           |       Owner:  afragen
     Type:  defect (bug)      |      Status:  assigned
 Priority:  normal            |   Milestone:  6.0
Component:  Filesystem API    |     Version:  3.7
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------

Comment (by afragen):

 PR updated to use `ftp_rawlist()` after `is_dir()` check in FTPext. This
 avoids any potential incorrectly configured FTP servers.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sat Mar 26 22:08:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sat, 26 Mar 2022 22:08:41 -0000
Subject: [wp-trac] [WordPress Trac] #2189: Calendar Stuck on December
 2005
In-Reply-To: <051.6ffb286dc5958d09b1776dd8c899f01b@wordpress.org>
References: <051.6ffb286dc5958d09b1776dd8c899f01b@wordpress.org>
Message-ID: <066.d55e2eaa4a567744e87ec4eef937a795@wordpress.org>

#2189: Calendar Stuck on December 2005
---------------------------------------+--------------------------
 Reporter:  macmanx                    |       Owner:  markjaquith
     Type:  defect (bug)               |      Status:  closed
 Priority:  normal                     |   Milestone:
Component:  Template                   |     Version:  2.0
 Severity:  normal                     |  Resolution:  fixed
 Keywords:  calendar has-patch commit  |     Focuses:
---------------------------------------+--------------------------

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/2189#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 03:31:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 03:31:37 -0000
Subject: [wp-trac] [WordPress Trac] #55467:
 WP_REST_Meta_Fields::update_meta_value handles update_metadata return value
 incorrectly
In-Reply-To: <057.a09b8b8a818d0f8b9503e8ed33e08838@wordpress.org>
References: <057.a09b8b8a818d0f8b9503e8ed33e08838@wordpress.org>
Message-ID: <072.d9a0d4ab969eb8e038cbac77261d8607@wordpress.org>

#55467: WP_REST_Meta_Fields::update_meta_value handles update_metadata return value
incorrectly
--------------------------------+-----------------------
 Reporter:  wordpressscyt       |       Owner:  (none)
     Type:  defect (bug)        |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  Options, Meta APIs  |     Version:  5.9
 Severity:  normal              |  Resolution:  invalid
 Keywords:  needs-patch         |     Focuses:  rest-api
--------------------------------+-----------------------
Changes (by TimothyBlynJacobs):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Future Release =>


Comment:

 Hi @wordpressscyt,

 Welcome to trac! Yes, you are correct that `update_metadata` can return
 `false` in those instances which is why we first check whether the stored
 value is equal to the proposed new value before calling the function in
 the previous lines of the `WP_REST_Meta_Fields::update_meta_value` method.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55467#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 10:34:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 10:34:44 -0000
Subject: [wp-trac] [WordPress Trac] #55468: Categories Block Needs a Filter
Message-ID: <051.e110ca9a82df84f573dc2fc510e609b7@wordpress.org>

#55468: Categories Block Needs a Filter
-------------------------+-----------------------------
 Reporter:  noumaan      |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Widgets      |    Version:  5.9.2
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 In the legacy Categories widget, users and developers were able to use the
 {{{
 widget_categories_args
 }}}
 \\
 filter to modify the results. For instance, they were able to exclude
 specific categories or display empty categories.

 Would be nice if this filter could also be used by the new category block.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55468>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 10:36:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 10:36:52 -0000
Subject: [wp-trac] [WordPress Trac] #55468: Categories Block Needs a
 Filter
In-Reply-To: <051.e110ca9a82df84f573dc2fc510e609b7@wordpress.org>
References: <051.e110ca9a82df84f573dc2fc510e609b7@wordpress.org>
Message-ID: <066.c86efcacc0ef95fa9afa755a56e3e2ab@wordpress.org>

#55468: Categories Block Needs a Filter
-------------------------------+------------------------------
 Reporter:  noumaan            |       Owner:  (none)
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Widgets            |     Version:  5.9.2
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by costdev):

 * keywords:   => reporter-feedback


Comment:

 Hi @noumaan, thanks for opening this ticket!

 Can you open
 [https://github.com/WordPress/gutenberg/issues/new?assignees=&labels=&template=Feature_request.md
 a feature request issue] posted on the Gutenberg repo for this and paste
 the link in here afterwards?

 Thanks!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55468#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 14:23:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 14:23:21 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2355426=3A_Two_Categor?=
 =?utf-8?q?ies_in_one_URL=3B_Shows_Posts_that_are_in_BOTH_Categories_doesn?=
 =?utf-8?b?4oCZdCB3b3Jr?=
In-Reply-To: <052.b660308ba71f82752846ccca94c32639@wordpress.org>
References: <052.b660308ba71f82752846ccca94c32639@wordpress.org>
Message-ID: <067.31c93e83c3f8cddc991095ffd49e5443@wordpress.org>

#55426: Two Categories in one URL; Shows Posts that are in BOTH Categories doesn’t
work
--------------------------+------------------------------
 Reporter:  gooloode      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by bcworkz):

 Confirmed. SQL contains a `0=1` clause when category name contains a '+'.

 I thought a workaround would be to use "pre_get_posts" action to intercept
 "category_name" query vars containing a '+' and compose a "tax_query" arg
 instead using `'operator => 'AND',`. Same result, the SQL ends up with a
 `0=1` clause.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55426#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 14:43:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 14:43:40 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to
 allow for named parameters in WP 6.0
In-Reply-To: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
References: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
Message-ID: <072.b8467b38828417a80918865344aca13f@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
-----------------------------+---------------------
 Reporter:  peterwilsoncc    |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  php80 has-patch  |     Focuses:
-----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52997" 52997]:
 {{{
 #!CommitTicketReference repository="" revision="52997"
 Code Modernization: Rename parameters that use reserved keywords in `wp-
 admin/includes/class-plugin-upgrader.php`.

 While using reserved PHP keywords as parameter name labels is allowed, in
 the context of function calls using named parameters in PHP 8.0+, this
 will easily lead to confusion. To avoid that, it is recommended not to use
 reserved keywords as function parameter names.

 This commit renames the `$return` variable in `Plugin_Upgrader` class
 methods to `$response` and updates the documentation accordingly.

 Follow-up to [47409], [52946], [52996].

 Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
 See #55327.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55327#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 14:53:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 14:53:36 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to
 allow for named parameters in WP 6.0
In-Reply-To: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
References: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
Message-ID: <072.3164b1bc1485c8ff04ed5e5b2e80c2b5@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
-----------------------------+---------------------
 Reporter:  peterwilsoncc    |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  php80 has-patch  |     Focuses:
-----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"52998" 52998]:
 {{{
 #!CommitTicketReference repository="" revision="52998"
 Code Modernization: Rename parameters that use reserved keywords in `wp-
 admin/includes/class-theme-upgrader.php`.

 While using reserved PHP keywords as parameter name labels is allowed, in
 the context of function calls using named parameters in PHP 8.0+, this
 will easily lead to confusion. To avoid that, it is recommended not to use
 reserved keywords as function parameter names.

 This commit renames the `$return` variable in `Theme_Upgrader` class
 methods to `$response` and updates the documentation accordingly.

 Follow-up to [47409], [52946], [52996], [52997].

 Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
 See #55327.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55327#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 17:10:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 17:10:57 -0000
Subject: [wp-trac] [WordPress Trac] #55469: WP_Filesystem_SSH2::chmod()
 should use ssh2_sftp_chmod()
Message-ID: <050.fbdbb5d719d997694ffc63d7ff371857@wordpress.org>

#55469: WP_Filesystem_SSH2::chmod() should use ssh2_sftp_chmod()
----------------------------+-----------------------------
 Reporter:  pbiron          |      Owner:  (none)
     Type:  enhancement     |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Filesystem API  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 `WP_Filesystem_SSH2::chmod()` currently uses `::run_command( sprintf(
 'chmod %o %s', $mode, escapeshellarg( $file ) ), true )` (which calls
 [https://www.php.net/manual/en/function.ssh2-exec.php ssh2_exec()]).  It
 has essentially been this way since `WP_Filesystem_SS2` was introduced in
 [8812].

 However, some sftp servers do not allow `ssh2_exec()` to be run,
 generating PHP warnings such as:

 > PHP Warning:  ssh2_exec(): Unable to request command execution on remote
 host

 and on those severs all calls to `WP_Filesystem_SSH2::chmod()` basically
 become noops.

 Luckily, starting with version [https://pecl.php.net/package/ssh2/0.12
 0.12], the ssh2 extension introduced
 [https://www.php.net/manual/en/function.ssh2-sftp-chmod.php
 ssh2_sftp_chmod()], and `WP_Filesystem_SSH2::chmod()` should be changed to
 use it.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55469>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 17:13:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 17:13:33 -0000
Subject: [wp-trac] [WordPress Trac] #55469: WP_Filesystem_SSH2::chmod()
 should use ssh2_sftp_chmod()
In-Reply-To: <050.fbdbb5d719d997694ffc63d7ff371857@wordpress.org>
References: <050.fbdbb5d719d997694ffc63d7ff371857@wordpress.org>
Message-ID: <065.4cee342c7664df020c94b705a34d4381@wordpress.org>

#55469: WP_Filesystem_SSH2::chmod() should use ssh2_sftp_chmod()
-------------------------------------+------------------------------
 Reporter:  pbiron                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Filesystem API           |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+------------------------------
Changes (by pbiron):

 * keywords:  has-patch => has-patch needs-testing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55469#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 17:48:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 17:48:01 -0000
Subject: [wp-trac] [WordPress Trac] #55470: Allow for finer-grained
 callbacks for wp_list_comment
Message-ID: <052.54eef39f2f9b530d01d7b3e4e9f43d12@wordpress.org>

#55470: Allow for finer-grained callbacks for wp_list_comment
-------------------------+-----------------------------
 Reporter:  dshanske     |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Comments     |    Version:  2.7
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 I've implemented a variety of different custom comment types, so
 logically, I'd like to allow for default customized comment output for
 these different types and still allow a theoretical theme to provide its
 own callback.

 Unfortunately, the only two options are a custom callback or a custom
 Comment Walker. Using the 'wp_list_comments_args' filter to make a custom
 comment walker the default, and reimplementing the start_el option is the
 only way to do this...but this means again, the possibility of
 unanticipated interaction.

 So, in thinking about this, proposing two enhancement options...looking
 for thoughts before I write up some code for consideration.

 1. Enhance the callback argument in wp_list_comments. Allow it to be an
 associative array or a string. If an associative array, the key would be
 comment_type. It would allow the 'all' parameter key, which would mean
 that the 'all' callback would be used if nothing more specific was
 provided. If this is a string, it would just set that to the all parameter
 and use the same logic. This would allow differing callbacks to be called
 per comment...if you choose to display them mixed.
 1. Add a filter inside start_el to allow for greater logic at this point
 before triggering the built-in or custom callback on a per-comment basis.

 Now, ideally, the solutions would be found in #35214 with some form of
 comment registration, but as that would have to be backward compatible,
 and that it has been 6 years since that conversation started suggests this
 simpler solution may make sense in the interim and even afterward.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55470>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Sun Mar 27 22:02:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Sun, 27 Mar 2022 22:02:33 -0000
Subject: [wp-trac] [WordPress Trac] #55352: Improve cache key generation
 in WP_Term_Query
In-Reply-To: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
References: <056.83ec256dbe1fbdf4ccbdd87da2264554@wordpress.org>
Message-ID: <071.b8ca796866dfe9ce7146a0a5acdd1a81@wordpress.org>

#55352: Improve cache key generation in WP_Term_Query
--------------------------------------+---------------------------
 Reporter:  spacedmonkey              |       Owner:  spacedmonkey
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Taxonomy                  |     Version:  4.7
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+---------------------------

Comment (by peterwilsoncc):

 Replying to [comment:10 johnjamesjacoby]:
 > I’d like to kindly suggest, rather than inlining everything in existing
 methods, that a new method be used to reshape these arguments for improved
 cache key usage.

 What benefit does this provide?

 Most of the changes were to normalize the DB query as it's sanitized.
 While nessesary for the cache key, this also improves hits to the DB
 servers query cache.

 Normalizing the WP cache is about three lines of code.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55352#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 00:00:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 00:00:12 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.ec90ea0dddcf73147cd290ef7619e4bb@wordpress.org>

#41136: Login forms lacking autocomplete attributes
------------------------------+--------------------------------------------
 Reporter:  johnjamesjacoby   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  6.0
Component:  Login and         |     Version:
  Registration                |
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  accessibility, administration
------------------------------+--------------------------------------------

Comment (by peterwilsoncc):

 Replying to [comment:12 joedolson]:
 > One thing I think this will need is to provide a filter so that
 autocomplete can be disabled; sites with higher security needs might need
 an easy way to disable this feature.

 According to caniuse, browsers ignore `off` for the following fields

 * Chrome, Edge: intentionally ignores `autocomplete="off"` when the user
 uses the browser's autofill functionality.
 * Firefox: ignores `autocomplete="off"` for login forms
 * Safari: ignores the `off` value for username, email and password fields

 It's also worth noting that since [comment:3 comment#3] several years ago,
 support for autocomplete has become universal with the exceptions noted
 above.

 > Overall, however, I think this is more of a benefit than a potential for
 harm. Would benefit from some additional voices on the security side,
 however.

 From a security perspective, I think it's fine to include the autocomplete
 values. I don't think adding filters is necessary given the browser
 manufacturers' decisions documented above.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 00:43:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 00:43:17 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.8349afc6b327c54d291890a54a3ed4af@wordpress.org>

#41136: Login forms lacking autocomplete attributes
------------------------------+--------------------------------------------
 Reporter:  johnjamesjacoby   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  6.0
Component:  Login and         |     Version:
  Registration                |
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  accessibility, administration
------------------------------+--------------------------------------------

Comment (by joedolson):

 Thanks for the second opinion, @peterwilsoncc! That matches what I was
 thinking, so sounds great.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 00:46:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 00:46:42 -0000
Subject: [wp-trac] [WordPress Trac] #53705: Plugin upgrade deletes files
 from other in-progress upgrades
In-Reply-To: <051.3864d53d4c261f039340696626d8cf5c@wordpress.org>
References: <051.3864d53d4c261f039340696626d8cf5c@wordpress.org>
Message-ID: <066.ab637af0fca86e21ab083d0c81aac7b8@wordpress.org>

#53705: Plugin upgrade deletes files from other in-progress upgrades
-----------------------------+---------------------
 Reporter:  bpayton          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  5.8
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+---------------------

Comment (by peterwilsoncc):

 Replying to [comment:6 bpayton]:
 > Instead of deleting old upgrade files on the fly, I think wp-
 content/upgrade/ cleanup should probably happen as part of a focused WP-
 Cron event, perhaps only deleting plugin dirs that are at least X hours
 old. I am working on a patch to propose this.
 >
 > Maybe it would be better to just add a condition so leftover `wp-
 content/upgrade/` subdirectories are only removed if they are over X units
 of time old (maybe over a day old to be really conservative). It's kind of
 a hack, but it's also simpler than worrying about WP-Cron events for
 cleanup and seems very low risk.

 I've been thinking about this and don't think it's a wise idea.

 In terms of meeting the website owners expectations: this approach would
 leave unexpected files on the server in an unexpected location.

 If the file names are predictable then a more targeted delete while
 preparing for the upgrade could be a better solution.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53705#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 03:15:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 03:15:34 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.d8b22ac36ec2e37966e6f0367daf08ab@wordpress.org>

#32998: What's a weblog?
-----------------------------------------+----------------------
 Reporter:  johnjamesjacoby              |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  low                          |   Milestone:  6.0
Component:  Options, Meta APIs           |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+----------------------
Changes (by peterwilsoncc):

 * Attachment "32998.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 03:16:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 03:16:24 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.20142b30993c013c7b2e1d461b758e4a@wordpress.org>

#32998: What's a weblog?
-----------------------------------------+----------------------
 Reporter:  johnjamesjacoby              |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  low                          |   Milestone:  6.0
Component:  Options, Meta APIs           |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+----------------------

Comment (by peterwilsoncc):

 In [attachment:"32998.diff"] : Minimal text per @webcommsat's suggestion
 above.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 05:37:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 05:37:33 -0000
Subject: [wp-trac] [WordPress Trac] #55207: WP_Query returns published
 sticky posts when post_status is set to draft
In-Reply-To: <052.c676576c2767ef4d8d1a735f953c8fae@wordpress.org>
References: <052.c676576c2767ef4d8d1a735f953c8fae@wordpress.org>
Message-ID: <067.188ac2e48d0cb5de49b98c24d841e6fa@wordpress.org>

#55207: WP_Query returns published sticky posts when post_status is set to draft
---------------------------------+-----------------------------
 Reporter:  NomNom99             |       Owner:  (none)
     Type:  defect (bug)         |      Status:  new
 Priority:  normal               |   Milestone:  Future Release
Component:  Query                |     Version:
 Severity:  normal               |  Resolution:
 Keywords:  early needs-refresh  |     Focuses:
---------------------------------+-----------------------------
Changes (by peterwilsoncc):

 * keywords:  early => early needs-refresh
 * milestone:  6.0 => Future Release


Comment:

 This was discussed during a bug scrub today.

 It was decided to take it off the 6.0 milestone to allow time to make a
 more considered decision around the two points that have been debated
 above:

 a) only post statuses of the type requested should be returned, or
 b) sticky posts are returned regardless of the query made,
 `ignore_sticky_posts` prevents that.

 As the ticket touches WP_Query, it's not possible to rush a decision on
 this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55207#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 05:47:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 05:47:11 -0000
Subject: [wp-trac] [WordPress Trac] #37110: Update to jQuery 3.*
In-Reply-To: <050.949831ff19c802b11513f4e9e00dd893@wordpress.org>
References: <050.949831ff19c802b11513f4e9e00dd893@wordpress.org>
Message-ID: <065.d695279dc941a182e520e56ed6f3f978@wordpress.org>

#37110: Update to jQuery 3.*
-------------------------------------------------+-------------------------
 Reporter:  jorbin                               |       Owner:
                                                 |  SergeyBiryukov
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  External Libraries                   |     Version:
 Severity:  critical                             |  Resolution:
 Keywords:  early has-patch needs-testing        |     Focuses:  javascript
  needs-screenshots has-dev-note                 |
-------------------------------------------------+-------------------------

Comment (by chaion07):

 Thanks @jorbin for reporting this. As we discussed this ticket during a
 [https://wordpress.slack.com/archives/C02RQBWTW/p1648444095971569 recent
 bug-scrub session], we still don't have any actionable items. Considering
 jQuery migration being a long term, multi-release project; the team is
 aiming for small steps to be made during the 6.0 cycle.

 Props to @peterwilsoncc

 Cheers!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37110#comment:207>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 05:54:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 05:54:45 -0000
Subject: [wp-trac] [WordPress Trac] #49985: REST API: Using _embed and
 _fields query parameters in the same query
In-Reply-To: <059.6e499a4b3c74df8b6283d93cb09764e4@wordpress.org>
References: <059.6e499a4b3c74df8b6283d93cb09764e4@wordpress.org>
Message-ID: <074.7a8ee297766910118af0fadc740f2e83@wordpress.org>

#49985: REST API: Using _embed and _fields query parameters in the same query
--------------------------------------------+------------------------------
 Reporter:  anouarbenothman                 |       Owner:
                                            |  TimothyBlynJacobs
     Type:  defect (bug)                    |      Status:  assigned
 Priority:  normal                          |   Milestone:  Future Release
Component:  REST API                        |     Version:  5.4
 Severity:  normal                          |  Resolution:
 Keywords:  early has-patch has-unit-tests  |     Focuses:  rest-api
--------------------------------------------+------------------------------
Changes (by peterwilsoncc):

 * milestone:  6.0 => Future Release


Comment:

 This was discussed during a bug scrub today, due to the lack of activity
 on the ticket and PR recently it was decided to move this off the 6.0
 milestone.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49985#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 05:58:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 05:58:58 -0000
Subject: [wp-trac] [WordPress Trac] #51857: Add rollback for failed
 plugin/theme updates
In-Reply-To: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
References: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
Message-ID: <065.29d5fc2b54735c129b2449beaebf0351@wordpress.org>

#51857: Add rollback for failed plugin/theme updates
-------------------------------------------------+-------------------------
 Reporter:  pbiron                               |       Owner:  pbiron
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  early has-testing-info needs-unit-   |     Focuses:
  tests needs-testing has-patch dev-feedback     |
  needs-dev-note                                 |
-------------------------------------------------+-------------------------
Changes (by afragen):

 * keywords:
     early has-testing-info needs-unit-tests needs-testing has-patch dev-
     feedback
     =>
     early has-testing-info needs-unit-tests needs-testing has-patch dev-
     feedback needs-dev-note


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51857#comment:204>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 06:46:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 06:46:19 -0000
Subject: [wp-trac] [WordPress Trac] #54042: Extending wpdb::prepare() to
 support table/field names, and IN() operator
In-Reply-To: <056.f04485e63ca681f362f38671080f1fa1@wordpress.org>
References: <056.f04485e63ca681f362f38671080f1fa1@wordpress.org>
Message-ID: <071.4963d1e5276db66365b1638b17cf0a4a@wordpress.org>

#54042: Extending wpdb::prepare() to support table/field names, and IN() operator
-------------------------------------------------+-------------------------
 Reporter:  craigfrancis                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Database                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:
  testing early has-unit-tests                   |
-------------------------------------------------+-------------------------

Comment (by chaion07):

 Thanks @craigfrancis for reporting this. We reviewed this ticket during a
 [https://wordpress.slack.com/archives/C02RQBWTW/p1648445542357159 recent
 bug-scrub session]. Here's the highlight from the discussion:

 01. We think that we're getting a bit close to beta to be making changes
 to $wpdb
 02. There's been a bit of activity in GitHub and the team appreciate
 @craigfrancis efforts as we're getting some good reviews from Committers.
 03. @peterwilsoncc has volunteered to reach out to people via Slack aiming
 for this to be done by this Friday.

 Props to @peterwilsoncc & @markparnell

 Cheers!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54042#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 06:51:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 06:51:32 -0000
Subject: [wp-trac] [WordPress Trac] #50163: Perform a canonical redirect
 when paginated states of the front page are not found
In-Reply-To: <048.165d8bffb8836886d21b5da24cca372d@wordpress.org>
References: <048.165d8bffb8836886d21b5da24cca372d@wordpress.org>
Message-ID: <063.288090f4e150cc7807c00fb1d274e5ce@wordpress.org>

#50163: Perform a canonical redirect when paginated states of the front page are
not found
-------------------------------------------------+-------------------------
 Reporter:  dd32                                 |       Owner:
                                                 |  hellofromTonya
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Canonical                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-screenshots needs-     |     Focuses:
  unit-tests early                               |
-------------------------------------------------+-------------------------

Comment (by chaion07):

 Thanks @dd32 for reporting this. We reviewed this ticket during a
 [https://wordpress.slack.com/archives/C02RQBWTW/p1648446179688289 recent
 bug-scrub session]. The team is hopeful that @hellofromTonya can take look
 at her convenience for this ticket to be moving forward during the 6.0
 cycle.

 Props to @peterwilsoncc

 Cheers!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50163#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 06:53:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 06:53:31 -0000
Subject: [wp-trac] [WordPress Trac] #54042: Extending wpdb::prepare() to
 support table/field names, and IN() operator
In-Reply-To: <056.f04485e63ca681f362f38671080f1fa1@wordpress.org>
References: <056.f04485e63ca681f362f38671080f1fa1@wordpress.org>
Message-ID: <071.a4d794c2d41821ecc4d7b75e365040ac@wordpress.org>

#54042: Extending wpdb::prepare() to support table/field names, and IN() operator
-------------------------------------------------+-------------------------
 Reporter:  craigfrancis                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Database                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:
  testing early has-unit-tests                   |
-------------------------------------------------+-------------------------

Comment (by craigfrancis):

 Yep, the focus has been on #52506, and while I’d like both of these
 features to be landed at the same time (they work well together), it can
 wait if there isn’t enough time.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54042#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 06:56:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 06:56:13 -0000
Subject: [wp-trac] [WordPress Trac] #47911: redirect_guess_404_permalink
 does not consider public custom posts status
In-Reply-To: <057.f467c50faaad6f9e4ee68f82be64a456@wordpress.org>
References: <057.f467c50faaad6f9e4ee68f82be64a456@wordpress.org>
Message-ID: <072.d74a55a1939c20737a66b7b38e817da8@wordpress.org>

#47911: redirect_guess_404_permalink does not consider public custom posts status
-------------------------------------------------+-------------------------
 Reporter:  goaroundagain                        |       Owner:
                                                 |  peterwilsoncc
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Canonical                            |     Version:  5.2.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests early       |     Focuses:
  needs-refresh needs-dev-note                   |
-------------------------------------------------+-------------------------
Changes (by chaion07):

 * keywords:  has-patch has-unit-tests early needs-refresh => has-patch has-
     unit-tests early needs-refresh needs-dev-note
 * owner:  SergeyBiryukov => peterwilsoncc


Comment:

 Thanks @goaroundagain for reporting this. We discussed this ticket during
 a [https://wordpress.slack.com/archives/C02RQBWTW/p1648446855030119 recent
 bug-scrub session]. Based on the feedback received from the team we're
 updating the ticket with the changes:

 01. Changing owner from @SergeyBiryukov to @peterwilsoncc since Peter
 volunteered to push up to a PR. He also wrote the code.
 02. Adding keyword needs-dev-note

 Props to @peterwilsoncc

 Cheers!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47911#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 09:29:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 09:29:57 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.bd0f3ac34c8476baba41c196a2ef120b@wordpress.org>

#32998: What's a weblog?
--------------------------------+----------------------
 Reporter:  johnjamesjacoby     |       Owner:  (none)
     Type:  enhancement         |      Status:  new
 Priority:  low                 |   Milestone:  6.0
Component:  Options, Meta APIs  |     Version:
 Severity:  minor               |  Resolution:
 Keywords:  has-patch commit    |     Focuses:  ui-copy
--------------------------------+----------------------
Changes (by audrasjb):

 * keywords:  has-patch needs-copy-review => has-patch commit


Comment:

 The new description looks good to me, thanks for refreshing it to
 implement the suggested copy changes @peterwilsoncc.
 Self assigning for `commit`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 09:30:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 09:30:23 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.f714cca2816c6a7e117235eee98914a0@wordpress.org>

#32998: What's a weblog?
--------------------------------------------------+----------------------
 Reporter:  johnjamesjacoby                       |       Owner:  (none)
     Type:  enhancement                           |      Status:  new
 Priority:  low                                   |   Milestone:  6.0
Component:  Options, Meta APIs                    |     Version:
 Severity:  minor                                 |  Resolution:
 Keywords:  has-patch commit assigned-for-commit  |     Focuses:  ui-copy
--------------------------------------------------+----------------------
Changes (by audrasjb):

 * keywords:  has-patch commit => has-patch commit assigned-for-commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 09:44:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 09:44:12 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.b76e1044626ec5111b454b89c71c686f@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by audrasjb):

 In [changeset:"52999" 52999]:
 {{{
 #!CommitTicketReference repository="" revision="52999"
 Docs: Use third-person singular verbs for function descriptions in `wp-
 includes/template.php`, per the documentation standards.

 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:48>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 09:50:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 09:50:01 -0000
Subject: [wp-trac] [WordPress Trac] #50997: Block Editor showing blank
 in WordPress 5.5
In-Reply-To: <056.b731661352751b6c9d7c7e45ebbd2b78@wordpress.org>
References: <056.b731661352751b6c9d7c7e45ebbd2b78@wordpress.org>
Message-ID: <071.52f7ad82ba9c0143e2b6572548daccf8@wordpress.org>

#50997: Block Editor showing blank in WordPress 5.5
--------------------------+-----------------------
 Reporter:  david-woakes  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:  5.5
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------

Comment (by jornfranke):

 Replying to [comment:3 johnxba]:
 > "Uncaught EvalError: call to Function() blocked by CSP" is Firefox
 complaining (F12) about the use of eval in scripts. Eval must not be used
 in scripts because it is a security risk. CSP (Content Security Policy)
 can be used to enforce protection.
 > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-
 Security-Policy]
 >
 > Why eval should not be used in Javascript:
 [https://developer.mozilla.org/en-
 US/docs/Web/JavaScript/Reference/Global_Objects/eval]
 >
 > The error appears when wp-admin is used and an admin is logged in. In
 the current version of WordPress, two of the scripts containing eval
 according to Firefox are:
 > wp-includes/js/wp-util.min.js?ver=5.8:2
 > wp-includes/js/underscore.min.js?ver=1.8.3:2
 >
 > Please remove the use of eval in scripts in WordPress.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50997#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 09:50:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 09:50:22 -0000
Subject: [wp-trac] [WordPress Trac] #50997: Block Editor showing blank
 in WordPress 5.5
In-Reply-To: <056.b731661352751b6c9d7c7e45ebbd2b78@wordpress.org>
References: <056.b731661352751b6c9d7c7e45ebbd2b78@wordpress.org>
Message-ID: <071.ee4fda79af0f01d29599726fa96a3e5d@wordpress.org>

#50997: Block Editor showing blank in WordPress 5.5
--------------------------+-----------------------
 Reporter:  david-woakes  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:  5.5
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------

Comment (by jornfranke):

 Can anyone say if this has been resolved in 5.9.x?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50997#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 09:53:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 09:53:46 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.115901199670b2edaf4641b2174ff25b@wordpress.org>

#32998: What's a weblog?
--------------------------------------------------+----------------------
 Reporter:  johnjamesjacoby                       |       Owner:  (none)
     Type:  enhancement                           |      Status:  new
 Priority:  low                                   |   Milestone:  6.0
Component:  Options, Meta APIs                    |     Version:
 Severity:  minor                                 |  Resolution:
 Keywords:  has-patch commit assigned-for-commit  |     Focuses:  ui-copy
--------------------------------------------------+----------------------

Comment (by webcommsat):

 @audrasjb and @peterwilsoncc thanks for the replies.
 My suggested text was to add to the previous comment, that is, to replace
 the second sentence from @costdev. I would suggest using @costdev first
 sentence too. 'An avatar is an image that can be associated with a user
 across multiple websites.'

 So the completed text change would be:
 'An avatar is an image that can be associated with a user across multiple
 websites. In this area, you can choose to display avatars of users who
 interact with the site.'

 Apologies for any extra work that causes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 09:54:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 09:54:44 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.9e9679704a9f946e3c956a9469cca37f@wordpress.org>

#32998: What's a weblog?
-------------------------------------+----------------------
 Reporter:  johnjamesjacoby          |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  low                      |   Milestone:  6.0
Component:  Options, Meta APIs       |     Version:
 Severity:  minor                    |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  ui-copy
-------------------------------------+----------------------
Changes (by audrasjb):

 * keywords:  has-patch commit assigned-for-commit => has-patch needs-
               refresh


Comment:

 Alright, let's remove this from the `commit` list for now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 10:12:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 10:12:34 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.4b01491780a100c5a5dd994d34d5d436@wordpress.org>

#32998: What's a weblog?
-----------------------------------------+----------------------
 Reporter:  johnjamesjacoby              |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  low                          |   Milestone:  6.0
Component:  Options, Meta APIs           |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+----------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch needs-copy-review


Comment:

 @webcommsat could you please proof read the above PR?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 10:13:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 10:13:19 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.632bdcf1ae6b2e6781ff3fdeb1f41fac@wordpress.org>

#32998: What's a weblog?
-----------------------------------------+----------------------
 Reporter:  johnjamesjacoby              |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  low                          |   Milestone:  6.0
Component:  Options, Meta APIs           |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+----------------------

Comment (by audrasjb):

 PR Link: https://github.com/WordPress/wordpress-develop/pull/2467/files

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 10:22:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 10:22:25 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.396ac0618001f45b345f3df906b5719b@wordpress.org>

#32998: What's a weblog?
-----------------------------------------+----------------------
 Reporter:  johnjamesjacoby              |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  low                          |   Milestone:  6.0
Component:  Options, Meta APIs           |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+----------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-28 à 12.21.58.png" added.

 Testing the above PR

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 10:23:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 10:23:18 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.9675a15888a0ff4a0b7e057e208140be@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by johnbillion):

 In [changeset:"53000" 53000]:
 {{{
 #!CommitTicketReference repository="" revision="53000"
 Docs: Correct the documented return types for date and time related
 functions and filters.

 See #54729
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 10:33:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 10:33:37 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.51d45721b7e696a2bc598c5ab041bc3e@wordpress.org>

#32998: What's a weblog?
-----------------------------------------+----------------------
 Reporter:  johnjamesjacoby              |       Owner:  (none)
     Type:  enhancement                  |      Status:  new
 Priority:  low                          |   Milestone:  6.0
Component:  Options, Meta APIs           |     Version:
 Severity:  minor                        |  Resolution:
 Keywords:  has-patch needs-copy-review  |     Focuses:  ui-copy
-----------------------------------------+----------------------

Comment (by webcommsat):

 Thank you @audrasjb - that looks fine and incorporates both @costdev and
 my comments. Thanks so much for looking at this and the PR.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 10:49:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 10:49:49 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.ca7a250bb6f56f7d264a18fe551f7d11@wordpress.org>

#32998: What's a weblog?
-------------------------------------------------+-------------------------
 Reporter:  johnjamesjacoby                      |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  low                                  |   Milestone:  6.0
Component:  Options, Meta APIs                   |     Version:
 Severity:  minor                                |  Resolution:
 Keywords:  has-patch commit has-copy-review     |     Focuses:  ui-copy
  assigned-for-commit                            |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch needs-copy-review => has-patch commit has-copy-
     review assigned-for-commit


Comment:

 Thanks for the review!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 10:55:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 10:55:04 -0000
Subject: [wp-trac] [WordPress Trac] #32998: What's a weblog?
In-Reply-To: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
References: <059.800962da21d93544f4b9ace3230a5e7c@wordpress.org>
Message-ID: <074.1ea7d6aa3f5a6a6b8d1e1e2064bd5f31@wordpress.org>

#32998: What's a weblog?
-------------------------------------------------+-------------------------
 Reporter:  johnjamesjacoby                      |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  low                                  |   Milestone:  6.0
Component:  Options, Meta APIs                   |     Version:
 Severity:  minor                                |  Resolution:  fixed
 Keywords:  has-patch commit has-copy-review     |     Focuses:  ui-copy
  assigned-for-commit                            |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53001" 53001]:
 {{{
 #!CommitTicketReference repository="" revision="53001"
 Options, Meta APIs: Rephrase the description of the "Avatars" section.

 This changeset clarifies the description of the "Avatars" section in
 Discussion Settings screen.

 Props johnjamesjacoby, helen, netweb, GaryJ, sabernhardt, costdev,
 audrasjb, webcommsat, peterwilsoncc.
 Fixes #32998.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32998#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 11:46:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 11:46:53 -0000
Subject: [wp-trac] [WordPress Trac] #55471: Enhancement: Social Media block
 - Adding mailto for email
Message-ID: <050.de6b723177713ce59e7d6d41233906cd@wordpress.org>

#55471: Enhancement: Social Media block - Adding mailto for email
-------------------------+-----------------------------
 Reporter:  mmiixx       |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:
 Severity:  minor        |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 Hi,
 Social Media block is great to use. Unfortunately, adding email address
 m at milanstojanovic.com to the footer of my website:
 - Keeps icon looking grayed out
 - Won't open as mailto: in email client

 For example check the footer here: https://www.milanstojanovic.com/

 If possible please consider this for future enhancements. Thank you.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55471>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 12:11:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 12:11:54 -0000
Subject: [wp-trac] [WordPress Trac] #55472: Duplicate link alert
Message-ID: <051.4313189bf1334c2a4e049b126e0b3d71@wordpress.org>

#55472: Duplicate link alert
-------------------------------+-----------------------------
 Reporter:  alisonn            |      Owner:  (none)
     Type:  enhancement        |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Posts, Post Types  |    Version:  5.9.2
 Severity:  normal             |   Keywords:
  Focuses:                     |
-------------------------------+-----------------------------
 When a duplicate pretty link is created (e.g. a page and a post with the
 same url) would it be possible for WordPress to flag this up with some
 kind of alert?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55472>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 12:59:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 12:59:09 -0000
Subject: [wp-trac] [WordPress Trac] #55472: Duplicate link alert
In-Reply-To: <051.4313189bf1334c2a4e049b126e0b3d71@wordpress.org>
References: <051.4313189bf1334c2a4e049b126e0b3d71@wordpress.org>
Message-ID: <066.ae94a0031db5d4eb5e6a5cb06bdf84a8@wordpress.org>

#55472: Duplicate link alert
-------------------------------+------------------------
 Reporter:  alisonn            |       Owner:  (none)
     Type:  enhancement        |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Posts, Post Types  |     Version:  5.9.2
 Severity:  normal             |  Resolution:  duplicate
 Keywords:                     |     Focuses:
-------------------------------+------------------------
Changes (by SergeyBiryukov):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 Hi there, welcome to WordPress Trac!

 Thanks for the ticket, we're already tracking this issue in #13459.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55472#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 13:15:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 13:15:51 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.23222fbf490d60c12ba5461e877a4bf4@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by audrasjb):

 In [changeset:"53002" 53002]:
 {{{
 #!CommitTicketReference repository="" revision="53002"
 Docs: Use third-person singular verbs for function descriptions in `wp-
 admin/includes/theme.php` and `wp-admin/includes/theme-install.php`, per
 the documentation standards.

 See #54729.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:50>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 13:22:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 13:22:53 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to
 allow for named parameters in WP 6.0
In-Reply-To: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
References: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
Message-ID: <072.8641ed3aa21750b711797d3b769b531f@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
-----------------------------+---------------------
 Reporter:  peterwilsoncc    |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  php80 has-patch  |     Focuses:
-----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"53003" 53003]:
 {{{
 #!CommitTicketReference repository="" revision="53003"
 Code Modernization: Rename parameters that use reserved keywords in `wp-
 admin/includes/class-wp-debug-data.php`.

 While using reserved PHP keywords as parameter name labels is allowed, in
 the context of function calls using named parameters in PHP 8.0+, this
 will easily lead to confusion. To avoid that, it is recommended not to use
 reserved keywords as function parameter names.

 This commit renames the `$var` parameter to `$mysql_var` in
 `WP_Debug_Data::get_mysql_var()`.

 Additionally, `$type` is renamed to `$data_type` in
 `WP_Debug_Data::format()` for clarity.

 Follow-up to [51522], [52946], [52996], [52997], [52998].

 Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
 See #55327.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55327#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 13:27:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 13:27:05 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.cf67690e8d26bcb3bc9ce9587d56d3d9@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
--------------------------------------------------+-----------------------
 Reporter:  stevegrunwell                         |       Owner:  audrasjb
     Type:  defect (bug)                          |      Status:  accepted
 Priority:  normal                                |   Milestone:  6.0
Component:  Plugins                               |     Version:
 Severity:  normal                                |  Resolution:
 Keywords:  has-patch commit assigned-for-commit  |     Focuses:
--------------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch commit => has-patch commit assigned-for-commit
 * owner:  (none) => audrasjb
 * status:  new => accepted


Comment:

 I opened the above PR to make sure to run unit tests against those changes
 before commit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 13:57:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 13:57:22 -0000
Subject: [wp-trac] [WordPress Trac] #55432: The $plugin parameter of the
 "plugin_loaded" action can be polluted by individual plugins
In-Reply-To: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
References: <057.7e77777d32586171902fc7c34d48c95f@wordpress.org>
Message-ID: <072.6956df3d615964619b5361ddb4d66273@wordpress.org>

#55432: The $plugin parameter of the "plugin_loaded" action can be polluted by
individual plugins
--------------------------------------------------+-----------------------
 Reporter:  stevegrunwell                         |       Owner:  audrasjb
     Type:  defect (bug)                          |      Status:  closed
 Priority:  normal                                |   Milestone:  6.0
Component:  Plugins                               |     Version:
 Severity:  normal                                |  Resolution:  fixed
 Keywords:  has-patch commit assigned-for-commit  |     Focuses:
--------------------------------------------------+-----------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53004" 53004]:
 {{{
 #!CommitTicketReference repository="" revision="53004"
 Plugins: Avoid stomping of some variables in `wp-settings.php`.

 This changeset decreases the chance of accidentally overwriting some
 variables located in `wp-settings.php`, as the chance of overriding a
 variable called `$_wp_plugin_file` would be lower than for `$plugin`,
 `$mu_plugin` or `$network_plugin`.

 Props stevegrunwell, joyously, peterwilsoncc, ocean90, SergeyBiryukov,
 jrf, azouamauriac.
 Fixes #55432.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55432#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 14:00:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 14:00:32 -0000
Subject: [wp-trac] [WordPress Trac] #55473: Update the About page for 5.9.3
Message-ID: <052.f2a1e7431679cc70e1e24f308acd0086@wordpress.org>

#55473: Update the About page for 5.9.3
----------------------------+-----------------------------
 Reporter:  audrasjb        |      Owner:  audrasjb
     Type:  task (blessed)  |     Status:  assigned
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Help/About      |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+-----------------------------
 Let's not forget to update the about page with 5.9.3 changes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55473>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 14:00:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 14:00:50 -0000
Subject: [wp-trac] [WordPress Trac] #55473: Update the About page for
 5.9.3
In-Reply-To: <052.f2a1e7431679cc70e1e24f308acd0086@wordpress.org>
References: <052.f2a1e7431679cc70e1e24f308acd0086@wordpress.org>
Message-ID: <067.b6e92defbebdb885cc1fc091da0accb9@wordpress.org>

#55473: Update the About page for 5.9.3
----------------------------+-----------------------
 Reporter:  audrasjb        |       Owner:  audrasjb
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  5.9.3
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+-----------------------
Changes (by audrasjb):

 * milestone:  Awaiting Review => 5.9.3


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55473#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 14:53:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 14:53:24 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.d9efee65096bf424abc13ace01239dac@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note                         |  performance
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * Attachment "55443.2.diff" added.

 latest from PR

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 15:22:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 15:22:10 -0000
Subject: [wp-trac] [WordPress Trac] #54015: Unable to pass _embed param
 to enveloped REST API requests
In-Reply-To: <056.7a3e907025d46dd4af28a7d94ff54e4b@wordpress.org>
References: <056.7a3e907025d46dd4af28a7d94ff54e4b@wordpress.org>
Message-ID: <071.d51496f92b641edbb3bbe030a4e077df@wordpress.org>

#54015: Unable to pass _embed param to enveloped REST API requests
----------------------------------------+-----------------------------
 Reporter:  spacedmonkey                |       Owner:  spacedmonkey
     Type:  defect (bug)                |      Status:  assigned
 Priority:  normal                      |   Milestone:  Future Release
Component:  REST API                    |     Version:  5.4
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:  rest-api
----------------------------------------+-----------------------------

Comment (by TimothyBlynJacobs):

 Something along the lines of this:

 {{{#!php
 $this->expectOutputString( 'json body that we expect' );

 $_GET['embed'] = 'link';
 rest_get_server()->serve_request('/endpoint/to/test');
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54015#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 15:54:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 15:54:44 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.27d4bc740aeaf7eb1d7d2b9d84e6d3df@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note                         |  performance
-------------------------------------------------+-------------------------
Description changed by adamsilverstein:

Old description:

> === Summary
> This ticket introduces core support for generating and using additional
> mime types for sub-sized image uploads, with a focus on the WebP format.
> In addition, it filters frontend content to use the modern format when
> available for an image. After this change, WordPress will generate and
> use WebP sub sizes by default when available.
>
> Currently, when users upload images in a supported mime type like JPEG or
> WebP, WordPress creates sub-sized images of the same type for use on the
> front end (WordPress does not currently create sub-sized images for TIFF,
> GIF or PNG images). In WordPress 5.8 we introduced the
> `image_editor_output_format` filter to enable filtering the mime type
> used to save images.
>
> This ticket introduces the capability to generate more than a single mime
> type. For example, when users upload JPEG images, WordPress can
> automatically generate both WebP and JPEG sub-sized images. Then
> WordPress can use the WebP images when serving up the front end. JPEG
> images are still being generated by default, to support other use-cases
> outside of common web browsers (e.g. email newsletters) where WebP may
> not be supported yet.
>
> The above is only the default though - the behavior of which image
> formats are generated and used can be customized via filters.
>
> === New Filters
>
> This patch introduces two new filters, one to control the mime types
> WordPress generates when you upload an image and one to control which
> image mime type is used for displaying images on the front end of the
> website.
>
> ==== Mime type image generation filter
>
> This patch adds a new filter named `wp_upload_image_mime_transforms` (and
> similarly named function) that maps the upload image mime type to an
> array of one or more output mime types:
>
> By default, the mapping is:
> {{{
>         array(
>                 'image/jpeg'        => array( 'image/jpeg', 'image/webp'
> ),
>                 'image/webp'      => array( 'image/webp', 'image/jpeg' ),
>         );
>
> }}}
> The attachment id is also passed to the filter for context.
>
> ==== Mime type front end output filter
>
> This patch adds a new filter `wp_content_image_mimes` for the front end
> that specifies the preferred format(s) to use for content output (as long
> as the image file is available). When outputting images in the content,
> the first mime type available will be used. The attachment id and context
> are also passed to the filter.
>
> === WebP as a default output format for images
> On the front end, sites will benefit from using WebP in place of JPEG for
> their images. Research on
> https://github.com/WordPress/performance/issues/7 indicates images will
> average around a 30% overall file size reduction. This work also includes
> verifying the visual image quality of the output using
> [https://github.com/kornelski/dssim dssim].
>
> === Developers Note
> The function `make_subsize`      in both of core’s bundled
> WP_Image_Editor implementations (WP_Image_Editor_Imagick and
> WP_Image_Editor_GD) has been updated to accept a `$mime_type` parameter
> which in turn passed the mime type to the `_save` function (which already
> supports a `$mime_type` parameter). If your code implements
> `​​WP_Image_Editor::make_subsize()` make sure you update your function to
> support the `$mime_type` parameter.
> Plugins that modify image use (CDN, S3) or already create alternate mime
> types should test integrating with the code on this ticket and consider
> supporting the new sources meta data.
>

> === How to Test
> Test with this patch or the Performance Lab
> [https://wordpress.org/plugins/performance-lab/ plugin]
> Create a post and upload a jpeg image, placing in the post
> Publish the post and view it’s source code, the image URLs should be
> “.webp” images
>
> === Technical Details
> * In src/wp-admin/includes/image.php::wp_create_image_subsizes:
> loop through all of the mime types returned from the
> `​​wp_upload_image_mime_transforms` filter, generating sub-sized images
> for every mime format supported by the system.  Default when a type isn’t
> mapped in the array  is outputting in the mime type of the uploaded
> image.
> The first type is the “primary” mime type and is stored exactly like
> current WordPress uploads (no change)
> “Full” sized images are created for each mime type supported by the
> system with a `-{mime extension}` appended to the file name
> When images over `big_image_size_threshold` are uploaded, the primary
> image gets a `-scaled` suffix (unchanged), alternate types get a `-{mime
> extension}-scaled` suffix
> Similarly, alternate mime rotated images get a  `-{mime
> extension}-rotated` suffix
> New image meta `sources` array stores each mime type created for each
> full sized image and for each sub-sized image - both the file name
> (`file`) and size (`filesize`) are stored.
> In src/wp-admin/includes/image.php::_wp_make_subsizes:
> Using a mapping (from the input file mime type) provided by
> `wp_upload_image_mime_transforms`, output sub sized images in one or more
> output mime types
>
> * In src/wp-admin/includes/image.php
> Add a new function `wp_upload_image_mime_transforms` as well as a
> matching filter named `wp_upload_image_mime_transforms` . Returns an
> array with the list of valid mime types that a specific mime type should
> be converted into.
> In src/wp-includes/class-wp-image-editor-gd.php and src/wp-includes
> /class-wp-image-editor-imagick.php:
> Update `make_subsize` to accept a new `mime_type` parameter that gets
> passed to the `_save` function when set (which already has a mime_type
> parameter). Add the new parameter to internal function calls as well.
>
> * In src/wp-includes/media.php: Adds  new function
> `wp_image_use_alternate_mime_types` that is called for every image in
> `wp_filter_content_tags`. This function:
> Adds a new filter `wp_content_image_mimes` that returns the mime type(s)
> to try to use for output, in the order they should be tried. The default
> order to try is array( 'image/webp', 'image/jpeg' ), meaning if a WebP
> version of the image exists, WordPress will use that image for the image
> tag output
> Replaces all image components (including urls in the `src` and `srcset`
> attributes) when the same image is available in the preferred mime type
> Returning an empty array will skip any image mime type substitution ( ie.
> `add_filter( ‘wp_content_image_mimes’, ‘__return_empty_array’ );`
>
> * In src/wp-includes/post.php::wp_delete_attachment_files:
> Delete additional mime type images referenced in the image meta root
> ‘sources’ array as well as each sizes->sources array when present. This
> ensures that additional mime images are cleaned up if the original image
> is deleted.
>
> * In src/js/_enqueues/vendor/plupload/wp-plupload.js and
> src/js/_enqueues/vendor/plupload/handlers.js retry count is raised from 4
> to 8. Should this be filterable? Note: needs to be changed in Gutenberg
> as well, see
> https://github.com/WordPress/gutenberg/blob/23f11a18726bf69717595451ab3250cb67b426f6/packages
> /api-fetch/src/middlewares/media-upload.js#L38
>
> === PHPUnit test changes
> New sources data added to expected results in `
> test_wp_generate_attachment_metadata_pdf`, `test_crop_setting_for_pdf`
> Remove new `wp_content_image_mimes` filter for tests in
> tests/phpunit/tests/media.php
>
> === Todo items remain for this patch:
> - Add tests for new filters `wp_content_image_mimes` and
> `wp_upload_image_mime_transforms`
> - Add full sized alternate mime creation for PDF upload special handling,
> see https://github.com/WordPress/wordpress-
> develop/pull/2393/files#r832651580
> - Add REST support from https://github.com/WordPress/performance/pull/224
> (or in follow up ticket)
> - Improve naming of rotated/cropped alternate mime images

New description:

 === Summary
 This ticket introduces core support for generating and using additional
 mime types for sub-sized image uploads, with a focus on the WebP format.
 In addition, it filters frontend content to use the modern format when
 available for an image. After this change, WordPress will generate and use
 WebP sub sizes by default when available.

 Currently, when users upload images in a supported mime type like JPEG or
 WebP, WordPress creates sub-sized images of the same type for use on the
 front end (WordPress does not currently create sub-sized images for TIFF,
 GIF or PNG images). In WordPress 5.8 we introduced the
 `image_editor_output_format` filter to enable filtering the mime type used
 to save images.

 This ticket introduces the capability to generate more than a single mime
 type. For example, when users upload JPEG images, WordPress can
 automatically generate both WebP and JPEG sub-sized images. Then WordPress
 can use the WebP images when serving up the front end. JPEG images are
 still being generated by default, to support other use-cases outside of
 common web browsers (e.g. email newsletters) where WebP may not be
 supported yet.

 The above is only the default though - the behavior of which image formats
 are generated and used can be customized via filters.

 === New Filters

 This patch introduces two new filters, one to control the mime types
 WordPress generates when you upload an image and one to control which
 image mime type is used for displaying images on the front end of the
 website.

 ==== Mime type image generation filter

 This patch adds a new filter named `wp_upload_image_mime_transforms` (and
 similarly named function) that maps the upload image mime type to an array
 of one or more output mime types:

 By default, the mapping is:
 {{{
         array(
                 'image/jpeg'        => array( 'image/jpeg', 'image/webp'
 ),
                 'image/webp'      => array( 'image/webp', 'image/jpeg' ),
         );

 }}}
 The attachment id is also passed to the filter for context.

 ==== Mime type front end output filter

 This patch adds a new filter `wp_content_image_mimes` for the front end
 that specifies the preferred format(s) to use for content output (as long
 as the image file is available). When outputting images in the content,
 the first mime type available will be used. The attachment id and context
 are also passed to the filter.

 === WebP as a default output format for images
 On the front end, sites will benefit from using WebP in place of JPEG for
 their images. Research on
 https://github.com/WordPress/performance/issues/7 indicates images will
 average around a 30% overall file size reduction. This work also includes
 verifying the visual image quality of the output using
 [https://github.com/kornelski/dssim dssim].

 === Developers Note
 The function `make_subsize`      in both of core’s bundled WP_Image_Editor
 implementations (WP_Image_Editor_Imagick and WP_Image_Editor_GD) has been
 updated to accept a `$mime_type` parameter which in turn passed the mime
 type to the `_save` function (which already supports a `$mime_type`
 parameter). If your code implements `​​WP_Image_Editor::make_subsize()`
 make sure you update your function to support the `$mime_type` parameter.
 Plugins that modify image use (CDN, S3) or already create alternate mime
 types should test integrating with the code on this ticket and consider
 supporting the new sources meta data.


 === How to Test
 Test with this patch or the Performance Lab [https://wordpress.org/plugins
 /performance-lab/ plugin]
 Create a post and upload a jpeg image, placing in the post
 Publish the post and view it’s source code, the image URLs should be
 “.webp” images

 === Technical Details
 * In src/wp-admin/includes/image.php::wp_create_image_subsizes:
 loop through all of the mime types returned from the
 `​​wp_upload_image_mime_transforms` filter, generating sub-sized images
 for every mime format supported by the system.  Default when a type isn’t
 mapped in the array  is outputting in the mime type of the uploaded image.
  * `_wp_get_primary_and_additional_mime_types` extracts the primary and
 additional mime types
  * “Full” sized images are created for each mime type supported by the
 system with a `-{mime extension}` appended to the file name
  * When images over `big_image_size_threshold` are uploaded, the primary
 image gets a `-scaled` suffix (unchanged), alternate types get a `-{mime
 extension}-scaled` suffix
  * Similarly, alternate mime rotated images get a  `-{mime
 extension}-rotated` suffix
  * New image meta `sources` array stores each mime type created for each
 full sized image and for each sub-sized image - both the file name
 (`file`) and size (`filesize`) are stored.
  * In src/wp-admin/includes/image.php::_wp_make_subsizes:
  * Using a mapping (from the input file mime type) provided by
 `wp_upload_image_mime_transforms`, output sub sized images in one or more
 output mime types

 * In src/wp-admin/includes/image.php
  * Add a new function `wp_upload_image_mime_transforms` as well as a
 matching filter named `wp_upload_image_mime_transforms` . Returns an array
 with the list of valid mime types that a specific mime type should be
 converted into.
  * In src/wp-includes/class-wp-image-editor-gd.php and src/wp-includes
 /class-wp-image-editor-imagick.php:
  * Update `make_subsize` to accept a new `mime_type` parameter that gets
 passed to the `_save` function when set (which already has a mime_type
 parameter). Add the new parameter to internal function calls as well.

 * In src/wp-includes/media.php: Adds  new function
 `wp_image_use_alternate_mime_types` that is called for every image in
 `wp_filter_content_tags`. This function:
  * Adds a new filter `wp_content_image_mimes` that returns the mime
 type(s) to try to use for output, in the order they should be tried. The
 default order to try is array( 'image/webp', 'image/jpeg' ), meaning if a
 WebP version of the image exists, WordPress will use that image for the
 image tag output
  * Replaces all image components (including urls in the `src` and `srcset`
 attributes) when the same image is available in the preferred mime type
  * Returning an empty array will skip any image mime type substitution (
 ie. `add_filter( ‘wp_content_image_mimes’, ‘__return_empty_array’ );`

 * In src/wp-includes/post.php::wp_delete_attachment_files:
  * Delete additional mime type images referenced in the image meta root
 ‘sources’ array as well as each sizes->sources array when present. This
 ensures that additional mime images are cleaned up if the original image
 is deleted.

 * In src/js/_enqueues/vendor/plupload/wp-plupload.js and
 src/js/_enqueues/vendor/plupload/handlers.js retry count is raised from 4
 to 8. (Should this be filterable)? This change is to accommodate the
 larger potential number of images that need to be created. Note: needs to
 be changed in Gutenberg as well, see
 https://github.com/WordPress/gutenberg/blob/23f11a18726bf69717595451ab3250cb67b426f6/packages
 /api-fetch/src/middlewares/media-upload.js#L38

 === PHPUnit test changes
 New sources data added to expected results in `
 test_wp_generate_attachment_metadata_pdf`, `test_crop_setting_for_pdf`
 Remove new `wp_content_image_mimes` filter for tests in
 tests/phpunit/tests/media.php

 === Todo items remain for this patch:
 - Add tests for new filters `wp_content_image_mimes` and
 `wp_upload_image_mime_transforms`
 - Add full sized alternate mime creation for PDF upload special handling,
 see https://github.com/WordPress/wordpress-
 develop/pull/2393/files#r832651580
 - Add REST support from https://github.com/WordPress/performance/pull/224
 (or in follow up ticket)
 - Improve naming of rotated/cropped alternate mime images

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 16:12:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 16:12:10 -0000
Subject: [wp-trac] [WordPress Trac] #55057: WebP EXIF data missing and
 images are not rotated in the same way JPEG images are rotated.
In-Reply-To: <050.cb1caad48c4abb96a7d234f408387e2f@wordpress.org>
References: <050.cb1caad48c4abb96a7d234f408387e2f@wordpress.org>
Message-ID: <065.9c7682a415facebc4a389046ef714547@wordpress.org>

#55057: WebP EXIF data missing and images are not rotated in the same way JPEG
images are rotated.
--------------------------+------------------------------
 Reporter:  mitogh        |       Owner:  adamsilverstein
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Media         |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  performance
--------------------------+------------------------------

Comment (by codekraft):

 Replying to [comment:3 mitogh]:
 > Thanks for taking a look into this @adamsilverstein I tried to find some
 alternatives for `exif_read_data` that can be used for WebP but I was not
 lucky enough to find information.
 >
 > Let me know in case I can help with anything else on this one.

 @mitogh I found a way to get the exif metadata without any php module and
 I can retrieve some information such as the orientation of the images...
 The issue with webp is that the exif data are stored inside the image in
 RIFF format while the different php modules (which @adamsilverstein has
 listed) are not able to grab them (and this makes me think that in the
 various servers this will come in a very long time)

 This is a poc of how exif icc xmp and animations could be extracted using
 php:
 https://gist.github.com/erikyo/c9365b0bc49d599f1be14b2f7feeed91

 You will get (for the images that store the exif meta) an array with the
 information of the image and a field "orientation" like this:

 [orientation] => 0008


 {{{
 1        2       3      4         5            6           7          8

 888888  888888      88  88      8888888888  88                  88
 8888888888
 88          88      88  88      88  88      88  88          88  88      88
 88
 8888      8888    8888  8888    88          8888888888  8888888888
 88
 88          88      88  88
 88          88  888888  888888
 }}}


 This is the way to get the orientation but I was wondering if it would be
 interesting to write a library that allows avoid the dependency of the
 EXIF php module. What do you think? it's worth of it?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55057#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 16:16:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 16:16:21 -0000
Subject: [wp-trac] [WordPress Trac] #54426: Add a "Copy URL to
 clipboard" row action in Media > Library...similar to the botton on the
 Edit Media screen
In-Reply-To: <050.9285dabd471bc0880785e0ab08880a2b@wordpress.org>
References: <050.9285dabd471bc0880785e0ab08880a2b@wordpress.org>
Message-ID: <065.7e1f027ce6b58899ae1092bad5dcac91@wordpress.org>

#54426: Add a "Copy URL to clipboard" row action in Media > Library...similar to
the botton on the Edit Media screen
-------------------------------------+-------------------------------------
 Reporter:  pbiron                   |       Owner:  davidbaumwald
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  has-screenshots has-     |     Focuses:  ui, accessibility,
  patch needs-testing needs-dev-     |  javascript
  note needs-codex                   |
-------------------------------------+-------------------------------------
Changes (by milana_cap):

 * keywords:  has-screenshots has-patch needs-testing needs-dev-note => has-
     screenshots has-patch needs-testing needs-dev-note needs-codex


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54426#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 16:27:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 16:27:15 -0000
Subject: [wp-trac] [WordPress Trac] #53094: Twenty Twenty-One: Dark mode
 issue
In-Reply-To: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
References: <049.8f5e952a4a7f43fe6c743eb5b5d2f902@wordpress.org>
Message-ID: <064.7f53d95086117d8ebe2b1812ab26928a@wordpress.org>

#53094: Twenty Twenty-One: Dark mode issue
-----------------------------+-----------------------------
 Reporter:  kpdaa            |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Future Release
Component:  Bundled Theme    |     Version:  5.7.1
 Severity:  normal           |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  css
-----------------------------+-----------------------------
Changes (by sabernhardt):

 * milestone:  6.0 => Future Release


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53094#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 18:49:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 18:49:30 -0000
Subject: [wp-trac] [WordPress Trac] #55474: Backport bugfixes from Gutenberg
 into Core for WP 5.9.3
Message-ID: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>

#55474: Backport bugfixes from Gutenberg into Core for WP 5.9.3
----------------------------+----------------------
 Reporter:  audrasjb        |      Owner:  mamaduka
     Type:  task (blessed)  |     Status:  assigned
 Priority:  normal          |  Milestone:  5.9.3
Component:  Editor          |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+----------------------
 This ticket aims to track backports needed from Gutenberg to Core for WP
 5.9.3.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55474>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 18:50:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 18:50:57 -0000
Subject: [wp-trac] [WordPress Trac] #55474: Backport bugfixes from
 Gutenberg into Core for WP 5.9.3
In-Reply-To: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
References: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
Message-ID: <067.4f6c40ce6d862dcb7a88c6ef9e758436@wordpress.org>

#55474: Backport bugfixes from Gutenberg into Core for WP 5.9.3
----------------------------+-----------------------
 Reporter:  audrasjb        |       Owner:  mamaduka
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  5.9.3
Component:  Editor          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+-----------------------

Comment (by audrasjb):

 @mamaduka here is a tracking ticket for Gutenberg backports.
 You can refer to this ticket in the incoming PR, and I can handle the
 related commit(s) :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55474#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:26:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:26:40 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.a0266b948832c03877f250d0e61a8840@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note                         |  performance
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * Attachment "55443.3.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:29:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:29:00 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.5a822685f02745e2975254ffa98d84b1@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note                         |  performance
-------------------------------------------------+-------------------------

Comment (by adamsilverstein):

 [attachment:"55443.3.diff"] brings latest from PR.

 Note for reviewers:
 - review [https://github.com/WordPress/wordpress-
 develop/pull/2393/files?w=1 without whitespace  changes] since diff is
 much smaller that way
 - most of the changes are to tests + new tests

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:34:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:34:55 -0000
Subject: [wp-trac] [WordPress Trac] #53951: Twenty Twenty: Search modal
 aria-expanded
In-Reply-To: <050.12159b56833732edace4c7af59831987@wordpress.org>
References: <050.12159b56833732edace4c7af59831987@wordpress.org>
Message-ID: <065.7c33c9d9f6b7aa6652ef1e1cbafedf84@wordpress.org>

#53951: Twenty Twenty: Search modal aria-expanded
-------------------------------------+-------------------------------------
 Reporter:  utz119                   |       Owner:  alexstine
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-testing-   |     Focuses:  accessibility,
  instructions needs-testing         |  javascript
-------------------------------------+-------------------------------------
Changes (by alexstine):

 * Attachment "53951.3.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53951>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:36:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:36:57 -0000
Subject: [wp-trac] [WordPress Trac] #53951: Twenty Twenty: Search modal
 aria-expanded
In-Reply-To: <050.12159b56833732edace4c7af59831987@wordpress.org>
References: <050.12159b56833732edace4c7af59831987@wordpress.org>
Message-ID: <065.76165eca54c1a3e54409dc18905a8999@wordpress.org>

#53951: Twenty Twenty: Search modal aria-expanded
-------------------------------------+-------------------------------------
 Reporter:  utz119                   |       Owner:  alexstine
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-testing-   |     Focuses:  accessibility,
  instructions needs-testing         |  javascript
-------------------------------------+-------------------------------------

Comment (by alexstine):

 In 53951.3.diff, I made one improvement to ensure the close search button
 did not receive aria-expanded attribute. This is one extra conditional
 check added to @afercia patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53951#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:38:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:38:55 -0000
Subject: [wp-trac] [WordPress Trac] #55231: Excessive <svg> elements? As
 of 5.9.1 Release - Not present in 5.9.
In-Reply-To: <051.9862ad593165538c22b687f64973704f@wordpress.org>
References: <051.9862ad593165538c22b687f64973704f@wordpress.org>
Message-ID: <066.741e7820bea576f09163c3873f67c852@wordpress.org>

#55231: Excessive <svg> elements? As of 5.9.1 Release - Not present in 5.9.
-----------------------------+--------------------------------
 Reporter:  mvaleno          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Editor           |     Version:  5.9.1
 Severity:  normal           |  Resolution:  reported-upstream
 Keywords:  has-screenshots  |     Focuses:
-----------------------------+--------------------------------
Changes (by audrasjb):

 * keywords:  has-screenshots needs-testing => has-screenshots
 * status:  new => closed
 * resolution:   => reported-upstream
 * milestone:  5.9.3 =>


Comment:

 Closing this ticket as it's being addressed upstream on Gutenberg side.
 See https://github.com/WordPress/gutenberg/issues/39008.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55231#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:40:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:40:48 -0000
Subject: [wp-trac] [WordPress Trac] #55262: Custom color options for
 selected text in the block editor for WordPress WordPress 5.9.1 are
 obscured
In-Reply-To: <051.49d7218e17c2384b15522d824d2ddaf3@wordpress.org>
References: <051.49d7218e17c2384b15522d824d2ddaf3@wordpress.org>
Message-ID: <066.e54f00b33c099ecc05de21db8b91f0ea@wordpress.org>

#55262: Custom color options for selected text in the block editor for WordPress
WordPress 5.9.1 are obscured
--------------------------+--------------------------------
 Reporter:  drusso1       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:  5.9
 Severity:  normal        |  Resolution:  reported-upstream
 Keywords:                |     Focuses:  ui
--------------------------+--------------------------------
Changes (by audrasjb):

 * keywords:  close =>
 * status:  new => closed
 * resolution:   => reported-upstream
 * milestone:  5.9.3 =>


Comment:

 Closing this ticket as it was reporter upstream on Gutenberg repository:
 https://github.com/WordPress/gutenberg/issues/39106

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55262#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:41:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:41:00 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.abebe624fb3d941d30377f5e31ebbf79@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots needs-design-        |     Focuses:  ui, ui-
  feedback has-patch i18n-change                 |  copy
-------------------------------------------------+-------------------------
Changes (by webcommsat):

 * keywords:
     has-screenshots needs-design-feedback has-patch i18n-change needs-
     copy-review
     => has-screenshots needs-design-feedback has-patch i18n-change


Comment:

 Passed this for copy review from @marybaum.
 Keeping this message nice and simply for users new to blocks in FSE is the
 key. I support the text by @ironprogrammer and the option for the user to
 find out more.

 Removing copy-review tag to move this ticket on.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:31>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:42:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:42:43 -0000
Subject: [wp-trac] [WordPress Trac] #55475: Add Lists to Favorites for
 Plugins
Message-ID: <054.6be7adfcc4382bb98753fa9cb941778b@wordpress.org>

#55475: Add Lists to Favorites for Plugins
-------------------------+-----------------------------
 Reporter:  dansoschin   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Plugins      |    Version:
 Severity:  minor        |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 Currently, you can click the "heart" icon next to a plugin name in the
 WordPress.org plugins directory.

 Example for Gutenberg: https://wordpress.org/plugins/gutenberg/
 Screenshot: https://cloudup.com/c-Uk_AX1Vg0

 Your favorites show up in your WordPress.org profile.
 Example here: https://profiles.wordpress.org/dansoschin/#content-favorites

 I would like to propose the ability to create lists of favorites so that
 you can "heart" a favorite and then are prompted to add it to a new list,
 add it to an existing list, or add it to all lists.

 The purpose of this would be for folks who work on multiple projects and
 might like to create groups of plugins for various types of projects.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55475>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:46:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:46:30 -0000
Subject: [wp-trac] [WordPress Trac] #55053: Large theme and plugin
 metaboxes are overlaid over the backend block editor when switching preview
 modes
In-Reply-To: <056.502fcc1d2ace565e206f58c3e7f62c43@wordpress.org>
References: <056.502fcc1d2ace565e206f58c3e7f62c43@wordpress.org>
Message-ID: <071.bb58021f5fc778e85c8e48f3e62c7025@wordpress.org>

#55053: Large theme and plugin metaboxes are overlaid over the backend block editor
when switching preview modes
--------------------------+--------------------------------
 Reporter:  quantum_leap  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  5.9
 Severity:  normal        |  Resolution:  reported-upstream
 Keywords:                |     Focuses:
--------------------------+--------------------------------
Changes (by audrasjb):

 * status:  new => closed
 * resolution:   => reported-upstream
 * milestone:  5.9.3 =>


Comment:

 Since this ticket was fixed upstream and as it's marked for backport to
 the next point release, we can safely close this ticket as `reported-
 upstream`. Thank you all for reporting the issue :)

 https://github.com/WordPress/gutenberg/issues/38062

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55053#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:49:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:49:48 -0000
Subject: [wp-trac] [WordPress Trac] #55476: Add heart icon for favorite
 plugins to plugin page in the "add plugin' area of wp-admin
Message-ID: <054.0ed5a4529ec43e97b4fa567aadab2518@wordpress.org>

#55476: Add heart icon for favorite plugins to plugin page in the "add plugin' area
of wp-admin
-------------------------+-----------------------------
 Reporter:  dansoschin   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Plugins      |    Version:
 Severity:  minor        |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 Currently, you can click the "heart" icon next to a plugin name in the
 WordPress.org plugins directory.

 Example for Gutenberg: https://wordpress.org/plugins/gutenberg/
 Screenshot: https://cloudup.com/c-Uk_AX1Vg0

 Your favorites show up in your WordPress.org profile.
 Example here: https://profiles.wordpress.org/dansoschin/#content-favorites

 I would like to propose the ability to see and click the heart icon within
 the "add plugin" area of wp-admin.
 Example here: https://cloudup.com/c_20nOmOJyX

 This would enable you to see that you have previously favorited a plugin
 and/or add/remove the plugin from your favorites list(s).

 When you click a specific plugin's "more details" link, we would also show
 the heart icon on that screen as well, likely on the right side along with
 the other meta data, perhaps above the version number.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55476>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:50:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:50:09 -0000
Subject: [wp-trac] [WordPress Trac] #55230: Release 5.9.1 breaks
 administration login.
In-Reply-To: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
References: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
Message-ID: <072.74019dd8f636000684e08388e9413868@wordpress.org>

#55230: Release 5.9.1 breaks administration login.
------------------------------------+-----------------------------
 Reporter:  carlduranleau           |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  5.9.3
Component:  Login and Registration  |     Version:  5.9.1
 Severity:  blocker                 |  Resolution:
 Keywords:  reporter-feedback       |     Focuses:  administration
------------------------------------+-----------------------------

Comment (by webcommsat):

 I could not reproduce this, happy to try again when we have the steps
 listed too. Thanks
 Replying to [comment:9 audrasjb]:
 > Hello @carlduranleau, do you still reproduce the issue? Several people
 tried to reproduce it on their side using WP_DEBUG set to true, and nobody
 succeed.
 >
 > Marking for `reporter-feedback`, pending steps to help reproduce the
 issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55230#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 19:53:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 19:53:18 -0000
Subject: [wp-trac] [WordPress Trac] #55476: Add heart icon for favorite
 plugins to plugin page in the "add plugin' area of wp-admin
In-Reply-To: <054.0ed5a4529ec43e97b4fa567aadab2518@wordpress.org>
References: <054.0ed5a4529ec43e97b4fa567aadab2518@wordpress.org>
Message-ID: <069.c64d6bf831a76ddfff02565e6bc1cd17@wordpress.org>

#55476: Add heart icon for favorite plugins to plugin page in the "add plugin' area
of wp-admin
-------------------------+------------------------------
 Reporter:  dansoschin   |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Plugins      |     Version:
 Severity:  minor        |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by audrasjb):

 Hello @dansoschin and thank you for opening this ticket and for the
 proposal.

 That would have been a good idea but as for now, we don't log WordPress
 users to their WordPress.org account so we don't have any way to find
 their favorites.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55476#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:16:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:16:59 -0000
Subject: [wp-trac] [WordPress Trac] #55476: Add heart icon for favorite
 plugins to plugin page in the "add plugin' area of wp-admin
In-Reply-To: <054.0ed5a4529ec43e97b4fa567aadab2518@wordpress.org>
References: <054.0ed5a4529ec43e97b4fa567aadab2518@wordpress.org>
Message-ID: <069.e69b87655a5c79ea932f817a439e3113@wordpress.org>

#55476: Add heart icon for favorite plugins to plugin page in the "add plugin' area
of wp-admin
-------------------------+------------------------------
 Reporter:  dansoschin   |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Plugins      |     Version:
 Severity:  minor        |  Resolution:  invalid
 Keywords:               |     Focuses:
-------------------------+------------------------------
Changes (by dansoschin):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Oh, yikes, thank you for pointing that out - I glossed over that
 completely. Thank you for the explanation.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55476#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:17:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:17:44 -0000
Subject: [wp-trac] [WordPress Trac] #55476: Add heart icon for favorite
 plugins to plugin page in the "add plugin' area of wp-admin
In-Reply-To: <054.0ed5a4529ec43e97b4fa567aadab2518@wordpress.org>
References: <054.0ed5a4529ec43e97b4fa567aadab2518@wordpress.org>
Message-ID: <069.2327b1212665c3a27002b5f9ee008c47@wordpress.org>

#55476: Add heart icon for favorite plugins to plugin page in the "add plugin' area
of wp-admin
-------------------------+------------------------------
 Reporter:  dansoschin   |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Plugins      |     Version:
 Severity:  minor        |  Resolution:  invalid
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by dansoschin):

 Agreed! Overlooked that connection - thanks again for the clarification.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55476#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:17:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:17:53 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs
 file
In-Reply-To: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
References: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
Message-ID: <064.34c5961e4a6ea8cf6bf9f93c1d442ad5@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
------------------------------+---------------------
 Reporter:  helen             |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  6.0
Component:  General           |     Version:
 Severity:  minor             |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+---------------------
Changes (by helen):

 * milestone:  Awaiting Review => 6.0


Comment:

 Replying to [comment:7 costdev]:
 > There are 421 commits beginning with "Coding Standard" (case-
 insensitive).

 Whew. Let's leave that for separate commits then. Thanks for looking into
 that!

 I left [https://github.com/WordPress/wordpress-
 develop/pull/2433#discussion_r836808137 one more thought] about whether to
 leave commits in but commented out for future us, once we resolve that
 then I agree on a commit with `see`. I'll dust off these SVN muscles again
 :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:20:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:20:48 -0000
Subject: [wp-trac] [WordPress Trac] #54741: About page - use version as
 variable
In-Reply-To: <053.041018366bfdebe133766db5c6cb7a84@wordpress.org>
References: <053.041018366bfdebe133766db5c6cb7a84@wordpress.org>
Message-ID: <068.00c2e294515e3c19bc511d373092123c@wordpress.org>

#54741: About page - use version as variable
-------------------------------------+------------------------------
 Reporter:  Presskopp                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Help/About               |     Version:  5.9
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+------------------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch needs-refresh


Comment:

 The idea looks good to me, but I’d suggest the field guide url could be
 translatable as well, since some Locales are translating this post.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54741#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:21:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:21:38 -0000
Subject: [wp-trac] [WordPress Trac] #52970: Improve text in help tabs of
 Personal Data Exporter/Eraser
In-Reply-To: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
References: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
Message-ID: <066.1fdbce024df205bc7eba75a4d9c62cbe@wordpress.org>

#52970: Improve text in help tabs of Personal Data Exporter/Eraser
-------------------------------------------------+-------------------------
 Reporter:  dimadin                              |       Owner:  marybaum
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Help/About                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:  privacy,
  screenshots has-privacy-review                 |  ui-copy
-------------------------------------------------+-------------------------

Comment (by webcommsat):

 From today's component scrub:
 - there is no testing needed on this ticket at present
 - @chantabourne could you please advise on getting a legal check for this
 please. Comment 45 may also be useful. Thank you.
 https://core.trac.wordpress.org/ticket/52970#comment:45

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52970#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:30:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:30:59 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.2f09db5fa6b239830083b36fb3925bb5@wordpress.org>

#55337: Optimize preload paths for post and site editors
-----------------------------------+-----------------------
 Reporter:  jsnajdr                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  closed
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Editor                 |     Version:  trunk
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 Backported to branch 5.9 in [53005].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55337#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:31:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:31:53 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.eac56490cf1b221110e998b008391159@wordpress.org>

#55337: Optimize preload paths for post and site editors
-----------------------------------+-----------------------
 Reporter:  jsnajdr                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  closed
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Editor                 |     Version:  trunk
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------

Comment (by audrasjb):

 Oops. I forgot to make sure this can be backported. @noisysocks @mamaduka
 is it ok to backport it to branch 5.9 right now?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55337#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:34:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:34:31 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.cc069aeb9d64de31a1e4c75626143d47@wordpress.org>

#55337: Optimize preload paths for post and site editors
-----------------------------------+-----------------------
 Reporter:  jsnajdr                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  reopened
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Editor                 |     Version:  trunk
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * status:  closed => reopened
 * resolution:  fixed =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55337#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:40:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:40:03 -0000
Subject: [wp-trac] [WordPress Trac] #55261: Add a "file size" column to
 the media library menu
In-Reply-To: <055.952e2bc0d068d35e2b1c7a7dbbb6064c@wordpress.org>
References: <055.952e2bc0d068d35e2b1c7a7dbbb6064c@wordpress.org>
Message-ID: <070.ad855a35dcd3309101866204e1bf5401@wordpress.org>

#55261: Add a "file size" column to the media library menu
-------------------------------------------------+-------------------------
 Reporter:  siyavashebr                          |       Owner:  (none)
     Type:  feature request                      |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots needs-docs has-      |     Focuses:
  patch                                          |  administration
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 It is worth noting that in 6.0, file size will be stored in as part of
 post meta. There is also a new helper function called, `wp_filesize`. See
 #49412 for more information.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55261#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:42:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:42:12 -0000
Subject: [wp-trac] [WordPress Trac] #38741: Introduce the concept of a
 large site in order to speed up the Users screen when there are many users
In-Reply-To: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
References: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
Message-ID: <070.aa4d0c8927ff9ea2fac524255746a7cd@wordpress.org>

#38741: Introduce the concept of a large site in order to speed up the Users screen
when there are many users
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  spacedmonkey
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  early has-patch has-     |     Focuses:  administration,
  unit-tests commit                  |  multisite, performance
-------------------------------------+-------------------------------------
Changes (by johnbillion):

 * keywords:
     early has-patch dev-feedback needs-testing 2nd-opinion needs-unit-
     tests
     => early has-patch has-unit-tests commit


Comment:

 I'm happy with the state of Jonny's PR and I think we should get this
 committed so we've plenty of time for testing. @spacedmonkey over to you.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38741#comment:79>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:44:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:44:19 -0000
Subject: [wp-trac] [WordPress Trac] #54741: About page - use version as
 variable
In-Reply-To: <053.041018366bfdebe133766db5c6cb7a84@wordpress.org>
References: <053.041018366bfdebe133766db5c6cb7a84@wordpress.org>
Message-ID: <068.daeeade6be2d6b21e13a33702e45e85b@wordpress.org>

#54741: About page - use version as variable
-------------------------------------+------------------------------
 Reporter:  Presskopp                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Help/About               |     Version:  5.9
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:
-------------------------------------+------------------------------
Changes (by Presskopp):

 * Attachment "54741.4.diff" added.

 patch makes the url translatable and also adjusted it from giving a 'Page
 Not Found'

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54741>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 20:51:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 20:51:17 -0000
Subject: [wp-trac] [WordPress Trac] #55203: Bug with get_post_galleries
In-Reply-To: <054.81596698acf7ab31a6e411a237b1af4c@wordpress.org>
References: <054.81596698acf7ab31a6e411a237b1af4c@wordpress.org>
Message-ID: <069.f68ef0b644e21c7fd525e17ac38e74e8@wordpress.org>

#55203: Bug with get_post_galleries
-------------------------------------------------+-------------------------
 Reporter:  BinaryMoon                           |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Media                                |     Version:  5.9
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit      |     Focuses:
  fixed-major                                    |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53006" 53006]:
 {{{
 #!CommitTicketReference repository="" revision="53006"
 Media: Make `get_post_galleries()` only return galleries.

 This change makes sure only gallery content is returned by
 `get_post_galleries()`. It fixes an issue where non gallery block content
 was also returned by the function.

 Props BinaryMoon, costdev, glendaviesnz.
 Merges [52797] to the 5.9 branch.
 Fixes #55203.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55203#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 21:53:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 21:53:24 -0000
Subject: [wp-trac] [WordPress Trac] #52970: Improve text in help tabs of
 Personal Data Exporter/Eraser
In-Reply-To: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
References: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
Message-ID: <066.ed8acc9a8111e46ff8496cf298bde6e7@wordpress.org>

#52970: Improve text in help tabs of Personal Data Exporter/Eraser
-------------------------------------------------+-------------------------
 Reporter:  dimadin                              |       Owner:  marybaum
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Help/About                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:  privacy,
  screenshots has-privacy-review                 |  ui-copy
-------------------------------------------------+-------------------------

Comment (by paapst):

 @webcommsat @marybaum As comment 45 indeed mentioned: That legal check has
 already been done before 5.9. I know @hellofromTonya has asked
 @chantaboune about this ticket about 4 months ago. And if I remember
 correctly the answer from Josepha was that there is no one legally
 representing the project, so there will be no "official" legal check other
 than that from volunteers with a legal background.
 What has been done since then is that the text has been mentioned in the
 core-privacy channel for additional feedback, and after that, it has been
 thoroughly checked by myself.  I am a law professor specialising in
 privacy law and IT law. I received my PhD on the topic of open source
 projects and policies, and I am also responsible for the legal research
 that has been done for the [https://wordpress.org/plugins/complianz-gdpr/
 Complianz plugin].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52970#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 22:23:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 22:23:28 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.8e17effcf6e21220692b0102e70be818@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
 Reporter:  ademos                    |       Owner:  marybaum
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+------------------------------

Comment (by paaljoachim):

 I went ahead and added a prototype.
 The focus is on removing current tags in the Bulk Edit mode.
 https://www.figma.com/proto/enUiWahhLPdHAe7VOTlUeU/Bulk-edit-remove-tags
 ?node-id=1%3A2&scaling=min-zoom&page-id=0%3A1&starting-point-node-id=1%3A2

 Let me know if you would like me to extend the prototype.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:40>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 22:42:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 22:42:44 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs
 file
In-Reply-To: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
References: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
Message-ID: <064.bb2589e1903b18c650a92a78b786859a@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
------------------------------+-----------------------
 Reporter:  helen             |       Owner:  helen
     Type:  enhancement       |      Status:  assigned
 Priority:  normal            |   Milestone:  6.0
Component:  General           |     Version:
 Severity:  minor             |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------
Changes (by peterwilsoncc):

 * owner:  (none) => helen
 * status:  new => assigned


Comment:

 I've answered the question inline on the PR.

 Assigning to Helen for commit as an MVP.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 23:10:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 23:10:22 -0000
Subject: [wp-trac] [WordPress Trac] #55015: Site Editor not working for
 TwentyTwentyTwo Child theme
In-Reply-To: <057.2d2b97539ca085d46839b9afdcd566fc@wordpress.org>
References: <057.2d2b97539ca085d46839b9afdcd566fc@wordpress.org>
Message-ID: <072.51b23fd706c209dd157ad65435154bc1@wordpress.org>

#55015: Site Editor not working for TwentyTwentyTwo Child theme
---------------------------+---------------------
 Reporter:  mervinpraison  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  5.9.4
Component:  Bundled Theme  |     Version:  5.9
 Severity:  major          |  Resolution:
 Keywords:  needs-patch    |     Focuses:
---------------------------+---------------------
Changes (by audrasjb):

 * milestone:  5.9.3 => 5.9.4


Comment:

 This issue still needs a patch and WordPress 5.9.3 RC1 is scheduled
 tomorrow.
 Moving for 5.9.4 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55015#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 23:11:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 23:11:13 -0000
Subject: [wp-trac] [WordPress Trac] #54905: PHP notice while accessing
 Customizer
In-Reply-To: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
References: <051.9c2a17d74e4bb75a06812a0d838fa122@wordpress.org>
Message-ID: <066.25f879343d7a9ec7d97e47990bdce06e@wordpress.org>

#54905: PHP notice while accessing Customizer
-------------------------------------------------+-------------------------
 Reporter:  Boniu91                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  5.9.4
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info has-screenshots                   |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * milestone:  5.9.3 => 5.9.4


Comment:

 This issue still needs a patch and WordPress 5.9.3 RC1 is scheduled
 tomorrow.
 Moving for 5.9.4 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54905#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 23:12:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 23:12:57 -0000
Subject: [wp-trac] [WordPress Trac] #55230: Release 5.9.1 breaks
 administration login.
In-Reply-To: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
References: <057.1670da42e118d9d1a8fcb4ffc1415dc9@wordpress.org>
Message-ID: <072.a289ee92bb455e821a54ef5c5aba2ce0@wordpress.org>

#55230: Release 5.9.1 breaks administration login.
------------------------------------+-----------------------------
 Reporter:  carlduranleau           |       Owner:  (none)
     Type:  defect (bug)            |      Status:  new
 Priority:  normal                  |   Milestone:  5.9.4
Component:  Login and Registration  |     Version:  5.9.1
 Severity:  blocker                 |  Resolution:
 Keywords:  reporter-feedback       |     Focuses:  administration
------------------------------------+-----------------------------
Changes (by audrasjb):

 * milestone:  5.9.3 => 5.9.4


Comment:

 This issue still needs reproduction steps and WordPress 5.9.3 RC1 is
 scheduled tomorrow.
 Moving for 5.9.4 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55230#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 23:13:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 23:13:25 -0000
Subject: [wp-trac] 
 =?utf-8?q?=5BWordPress_Trac=5D_=2355117=3A_Possible_5?=
 =?utf-8?b?LjkgQnVnOiBVbmtub3duIGNoYXJhY3RlciAo77+8IG9yICVlZiViZiViYyAp?=
 =?utf-8?q?_on_content_title?=
In-Reply-To: <053.b81fc379153db7c724cf676bc0bbe3b4@wordpress.org>
References: <053.b81fc379153db7c724cf676bc0bbe3b4@wordpress.org>
Message-ID: <068.2bbe1ebc42aa96ec20439bb2ef39f3ce@wordpress.org>

#55117: Possible 5.9 Bug: Unknown character ( or %ef%bf%bc ) on content title
--------------------------+-----------------------
 Reporter:  cantuaria     |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  5.9.4
Component:  Permalinks    |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Changes (by audrasjb):

 * milestone:  5.9.3 => 5.9.4


Comment:

 This issue still needs a patch and WordPress 5.9.3 RC1 is scheduled
 tomorrow.
 Moving for 5.9.4 consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55117#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Mon Mar 28 23:46:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Mon, 28 Mar 2022 23:46:19 -0000
Subject: [wp-trac] [WordPress Trac] #47911: redirect_guess_404_permalink
 does not consider public custom posts status
In-Reply-To: <057.f467c50faaad6f9e4ee68f82be64a456@wordpress.org>
References: <057.f467c50faaad6f9e4ee68f82be64a456@wordpress.org>
Message-ID: <072.7821bd94375160bc56c19e4aa786fead@wordpress.org>

#47911: redirect_guess_404_permalink does not consider public custom posts status
-------------------------------------------------+-------------------------
 Reporter:  goaroundagain                        |       Owner:
                                                 |  peterwilsoncc
     Type:  enhancement                          |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Canonical                            |     Version:  5.2.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests early       |     Focuses:
  needs-dev-note                                 |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 In the [https://github.com/WordPress/wordpress-develop/pull/2470 linked
 pull request]:

 * built upon the previous work in [attachment:"47911_htdat_3.diff"]
 * now uses `is_post_status_viewable()` to determine public post statuses
 * added `esc_sql` to the SQL `IN()`
 * extended tests to include custom public, private, internal and protected
 statuses

 Is `pre_redirect_guess_404_permalink` adequate in terms of filters or
 should a filter for the post statuses to include be added?

 Naming suggestions are welcome if you think the filter is needed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47911#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 00:01:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 00:01:29 -0000
Subject: [wp-trac] [WordPress Trac] #52970: Improve text in help tabs of
 Personal Data Exporter/Eraser
In-Reply-To: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
References: <051.1fd5e5c7e8db44b69cca58d665815035@wordpress.org>
Message-ID: <066.6dfd65e961982beb1b3bbbd236252361@wordpress.org>

#52970: Improve text in help tabs of Personal Data Exporter/Eraser
-------------------------------------------------+-------------------------
 Reporter:  dimadin                              |       Owner:  marybaum
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Help/About                           |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:  privacy,
  screenshots has-privacy-review                 |  ui-copy
-------------------------------------------------+-------------------------

Comment (by webcommsat):

 Thanks @paapst for the info. It came up in today's component bug scrub to
 help move this ticket forward, and to ask Josepha. Your previous comment
 was highlighted in today's scrub. Thanks for adding the additional
 information.

 @audrasjb and @davidbaumwald for awareness and any input on next steps
 following the discussion in the scrub today. The [latest
 patch]https://core.trac.wordpress.org/attachment/ticket/52970/Update_for_ticket_52970_new.patch.
 Thanks.

 Replying to [comment:53 paapst]:
 > @webcommsat @marybaum As comment 45 indeed mentioned: That legal check
 has already been done before 5.9. I know @hellofromTonya has asked
 @chantaboune about this ticket about 4 months ago. And if I remember
 correctly the answer from Josepha was that there is no one legally
 representing the project, so there will be no "official" legal check other
 than that from volunteers with a legal background.
 > What has been done since then is that the text has been mentioned in the
 core-privacy channel for additional feedback, and after that, it has been
 thoroughly checked by myself.  I am a law professor specialising in
 privacy law and IT law. I received my PhD on the topic of open source
 projects and policies, and I am also responsible for the legal research
 that has been done for the [https://wordpress.org/plugins/complianz-gdpr/
 Complianz plugin].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52970#comment:54>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 01:35:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 01:35:23 -0000
Subject: [wp-trac] [WordPress Trac] #50900: 5.5-RC3 - Code Editor Broken
 (change of behavior; Inserts br in content)
In-Reply-To: <052.c0f2df3ddb9b98e0056b17a8a3400f28@wordpress.org>
References: <052.c0f2df3ddb9b98e0056b17a8a3400f28@wordpress.org>
Message-ID: <067.32cf67910a4fa435c2172c11c4f995cf@wordpress.org>

#50900: 5.5-RC3 - Code Editor Broken (change of behavior; Inserts br in content)
--------------------------+-----------------------
 Reporter:  Justin_K      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:  5.5
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Description changed by costdev:

Old description:

> While testing out my plugins against 5.5, there has been a breaking
> change in the post editor: while in CODE EDITOR mode (note: not visual
> editor) mode, the instant the mouse focus is taken out of the content
> box, it appends &lt;br /&gt; tags at the end of every line.  This is
> expected with the visual editor, but not with the code editor.  The
> regression breaks the functionality of my plugin.
>
> Here's a short video showing the behavior:
> https://lnk2.tk/snaps/2020-08-11_11.31.07.mp4

New description:

 While testing out my plugins against 5.5, there has been a breaking change
 in the post editor: while in CODE EDITOR mode (note: not visual editor)
 mode, the instant the mouse focus is taken out of the content box, it
 appends &lt;br /&gt; tags at the end of every line.  This is expected with
 the visual editor, but not with the code editor.  The regression breaks
 the functionality of my plugin.

 **Link removed**

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50900#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 01:38:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 01:38:54 -0000
Subject: [wp-trac] [WordPress Trac] #50900: 5.5-RC3 - Code Editor Broken
 (change of behavior; Inserts br in content)
In-Reply-To: <052.c0f2df3ddb9b98e0056b17a8a3400f28@wordpress.org>
References: <052.c0f2df3ddb9b98e0056b17a8a3400f28@wordpress.org>
Message-ID: <067.a885def3cc027fe2b17295680354a716@wordpress.org>

#50900: 5.5-RC3 - Code Editor Broken (change of behavior; Inserts br in content)
--------------------------+------------------------
 Reporter:  Justin_K      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:  5.5
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by costdev):

 * status:  reopened => closed
 * resolution:   => duplicate


Comment:

 Re-closing ticket as a duplicate of #2833.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50900#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 01:55:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 01:55:24 -0000
Subject: [wp-trac] [WordPress Trac] #22316: Plugin Dependencies (Yet
 Another Plugin Dependencies Ticket)
In-Reply-To: <056.dd52dedca2457b5bc3a0cb986370b731@wordpress.org>
References: <056.dd52dedca2457b5bc3a0cb986370b731@wordpress.org>
Message-ID: <071.de1cd88f540c7ff539a02b219004c4b7@wordpress.org>

#22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)
-------------------------------------------------+-------------------------
 Reporter:  Viper007Bond                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Upgrade/Install                      |     Version:  3.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  dev-feedback has-patch early needs-  |     Focuses:
  design-feedback needs-dev-note                 |
-------------------------------------------------+-------------------------
Changes (by afragen):

 * keywords:  dev-feedback has-patch early => dev-feedback has-patch early
     needs-design-feedback needs-dev-note


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/22316#comment:258>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 01:55:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 01:55:51 -0000
Subject: [wp-trac] [WordPress Trac] #22316: Plugin Dependencies (Yet
 Another Plugin Dependencies Ticket)
In-Reply-To: <056.dd52dedca2457b5bc3a0cb986370b731@wordpress.org>
References: <056.dd52dedca2457b5bc3a0cb986370b731@wordpress.org>
Message-ID: <071.44fbaa0301d21ad599032351345bb83c@wordpress.org>

#22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)
-------------------------------------------------+-------------------------
 Reporter:  Viper007Bond                         |       Owner:  afragen
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Upgrade/Install                      |     Version:  3.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  dev-feedback has-patch early needs-  |     Focuses:
  design-feedback needs-dev-note                 |
-------------------------------------------------+-------------------------
Changes (by afragen):

 * owner:  (none) => afragen
 * status:  new => assigned


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/22316#comment:259>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 02:13:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 02:13:22 -0000
Subject: [wp-trac] [WordPress Trac] #54582: Problem with deleting old
 files at the end of a core update when the filesystem is case-insensitive
In-Reply-To: <050.439148f3204025f20e2acf004716f3ed@wordpress.org>
References: <050.439148f3204025f20e2acf004716f3ed@wordpress.org>
Message-ID: <065.20bd12b9c43f59325fe1a63dfea1e6df@wordpress.org>

#54582: Problem with deleting old files at the end of a core update when the
filesystem is case-insensitive
-------------------------------------------------+-------------------------
 Reporter:  pbiron                               |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  Future
                                                 |  Release
Component:  Upgrade/Install                      |     Version:
 Severity:  major                                |  Resolution:
 Keywords:  needs-patch needs-testing early      |     Focuses:
  early-like-actually-early                      |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * milestone:  6.0 => Future Release


Comment:

 As this doesn't have a patch and is tagged early (actually early).

 I'm going to bump this from 6.0 as we're a couple of weeks from beta and
 it doesn't appear anyone has bandwidth to work on this issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54582#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 02:38:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 02:38:26 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.77a180cdf0ba684d807243c29ee93fcb@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
-------------------------------------------------+-------------------------
 Reporter:  isaumya                              |       Owner:
                                                 |  adamsilverstein
     Type:  feature request                      |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  refresh                                        |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests commit => has-patch has-unit-tests
     needs-refresh


Comment:

 @adamsilverstein The latest PR is in draft and there are a few
 `error_log()` calls in [attachment:"53232.3.diff"] so I've removed the
 `commit` keyword.

 Will you have bandwidth to refresh the patches or would it be best if the
 ticket were bumped from the 6.0 milestone?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 02:46:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 02:46:04 -0000
Subject: [wp-trac] [WordPress Trac] #54713: Build/Test Tools: Add unit
 tests for `feed_links_extra()`.
In-Reply-To: <051.ac57845cfdc90a01711f5456345a3c1d@wordpress.org>
References: <051.ac57845cfdc90a01711f5456345a3c1d@wordpress.org>
Message-ID: <066.efb28c308fa40d7be7828e5a330a0128@wordpress.org>

#54713: Build/Test Tools: Add unit tests for `feed_links_extra()`.
--------------------------------------+-----------------------------
 Reporter:  costdev                   |       Owner:  hellofromTonya
     Type:  task (blessed)            |      Status:  reviewing
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests early => has-patch has-unit-tests


Comment:

 I discussed this with @costdev via Slack.

 To avoid making changes to `WP_Query` in a ticket designed to add tests,
 the tests that fail without the query changes will be left out for this
 release.

 A follow up ticket will be created to fix the bug that was found while
 writing the tests. And to decide whether the bug is in feeds or
 `WP_Query`.

 Removing the `early` keyword as this will no longer touch `WP_Query`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54713#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 03:20:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 03:20:46 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs
 file
In-Reply-To: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
References: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
Message-ID: <064.80d66226ab95b875b9ada7a6d00f24d0@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
------------------------------+-----------------------
 Reporter:  helen             |       Owner:  helen
     Type:  enhancement       |      Status:  assigned
 Priority:  normal            |   Milestone:  6.0
Component:  General           |     Version:
 Severity:  minor             |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------

Comment (by helen):

 In [changeset:"53007" 53007]:
 {{{
 #!CommitTicketReference repository="" revision="53007"
 Build/Test Tools: First pass at a .git-blame-ignore-revs file.

 This suppresses certain commits from Git blame views, notably in the
 GitHub UI as well as the command line. These commits are purely stylistic
 and excluding them from these views helps to reduce the noise when doing
 code archaeology.

 Still to come: More coding standards commits as they are reviewed.

 Props helen, costdev, peterwilsoncc.
 See #55422
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 03:21:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 03:21:08 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.319dc533fa379dbc67624091e50c8ad6@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
-------------------------------------------------+-------------------------
 Reporter:  isaumya                              |       Owner:
                                                 |  adamsilverstein
     Type:  feature request                      |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  refresh                                        |  performance
-------------------------------------------------+-------------------------

Comment (by adamsilverstein):

 @peterwilsoncc thanks, i will update the patch/pr.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 03:30:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 03:30:20 -0000
Subject: [wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs
 file
In-Reply-To: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
References: <049.d28988312d1c7e977a5c81ef78ff2402@wordpress.org>
Message-ID: <064.05ef007dbb5091c5268ce7bd908d6a91@wordpress.org>

#55422: Add a .git-blame-ignore-revs file
------------------------------+-----------------------
 Reporter:  helen             |       Owner:  helen
     Type:  enhancement       |      Status:  assigned
 Priority:  normal            |   Milestone:  6.0
Component:  General           |     Version:
 Severity:  minor             |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------

Comment (by helen):

 Noticed [12733] / 8ef8b7bad509520896877fdac4882192d746d51a while checking
 out the [https://github.com/WordPress/wordpress-develop/blame/trunk/src
 /wp-admin/includes/plugin.php much improved visual blame], just leaving a
 note here for further commits :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 04:33:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 04:33:46 -0000
Subject: [wp-trac] [WordPress Trac] #40927: Passing a float as the
 position in add_menu_page can override other menu items
In-Reply-To: <054.3952f5b90c4dd00f8f2ab13814b18548@wordpress.org>
References: <054.3952f5b90c4dd00f8f2ab13814b18548@wordpress.org>
Message-ID: <069.79f1ded3b4c8d5e11d55bdaf7df0376b@wordpress.org>

#40927: Passing a float as the position in add_menu_page can override other menu
items
-------------------------------------------------+-------------------------
 Reporter:  justinbusa                           |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  4.8
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-        |     Focuses:
  testing needs-refresh needs-unit-tests         |  administration
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch dev-feedback needs-testing => has-patch dev-feedback
     needs-testing needs-refresh needs-unit-tests


Comment:

 I've linked a [https://github.com/WordPress/wordpress-develop/pull/2471
 pull request] based on [attachment:"40927.2.patch"] to get the tests
 running.

 The tests are currently failing, I suspect due to the following:

 * PR is storing with the array key `(string) $position + (a tiny randomish
 number)` whereas the tests are testing for the key `(int) $position`.
 * change in sorting algorithm, possibly.

 ----

 For now, let's target the bug that passing different values can result in
 an override (64.64 replacing 64).

 Avoiding collisions with a tiny randomish number can wait as it's
 documented that only one menu item can own a `$position` value.

 It's strongly advised against but it is currently possible to manipulate
 the `$menu` global directly. For example, I could remove the comments menu
 with:

 {{{#!php
 <?php
 global $menu;
 unset( $menu[25] );
 }}}

 It's not a good idea to do so but it would be nice not to break backward
 compatibility if other options are available.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/40927#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 04:57:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 04:57:26 -0000
Subject: [wp-trac] [WordPress Trac] #53224: Super admin cannot set an
 application password on a site they're not a member of
In-Reply-To: <055.77d7d74ec7ed8f111cfb71f64c34a804@wordpress.org>
References: <055.77d7d74ec7ed8f111cfb71f64c34a804@wordpress.org>
Message-ID: <070.875d80b40c4df46825cac15097f65d53@wordpress.org>

#53224: Super admin cannot set an application password on a site they're not a
member of
-------------------------------------------------+-------------------------
 Reporter:  johnbillion                          |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Application Passwords                |     Version:  5.6
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:  multisite
  feedback                                       |
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 @johnjamesjacoby is the TL;DR of your comment on the PR that
 @johnbillion's selection of the `manage_sites` cap check is correct?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53224#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 05:46:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 05:46:17 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.b8c3e5a3dde144817171a7abb135e64d@wordpress.org>

#55337: Optimize preload paths for post and site editors
-----------------------------------+-----------------------
 Reporter:  jsnajdr                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  reopened
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Editor                 |     Version:  trunk
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------

Comment (by Mamaduka):

 @audrasjb, this looks good for backporting. Thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55337#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 05:47:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 05:47:59 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.41722fe6f0c75caf1c9b77367af6b3d2@wordpress.org>

#55337: Optimize preload paths for post and site editors
-----------------------------------+-----------------------
 Reporter:  jsnajdr                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  reopened
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Editor                 |     Version:  trunk
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------

Comment (by jsnajdr):

 > shouldn't we also backport the changes introduced in the Gutenberg PRs
 mentioned above?

 The https://github.com/WordPress/gutenberg/pull/39256 PR doesn't need to
 be backported at all, because it just patches the preload paths with a
 filter, while this Core patch modifies the source. It's a compat code that
 will disappear during 6.0 release.

 This patch should be safe to backport to 5.9 and will add value for 5.9
 users: preloads will match what the block editor actually requests, while
 now some of them are futile.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55337#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 06:42:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 06:42:56 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.87d21c5ed7684c2f8c5109087e24d2a1@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+------------------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+------------------------------

Comment (by mikeschroder):

 Just tested and can verify this seems to improve things when applied to
 the 5.9 branch.

 Do you think it'd be a good candidate for backport for the 5.9.3 release?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 07:34:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 07:34:24 -0000
Subject: [wp-trac] [WordPress Trac] #55337: Optimize preload paths for
 post and site editors
In-Reply-To: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
References: <051.3cc270bd638cb2ab0bbe4aa5931f6c80@wordpress.org>
Message-ID: <066.ea15a66a72f731a9bc09b691fa6ef45a@wordpress.org>

#55337: Optimize preload paths for post and site editors
-----------------------------------+-----------------------
 Reporter:  jsnajdr                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  closed
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Editor                 |     Version:  trunk
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 Alright, thank you all.
 The patch was backported to branch 5.9 in [53005], so I'm closing this
 ticket as fixed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55337#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 08:49:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 08:49:39 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.368d2411d6ec1f49e992ac31ddbde5c4@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change needs-refresh                           |  copy
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-screenshots needs-design-feedback has-patch i18n-change =>
     has-screenshots has-patch i18n-change needs-refresh


Comment:

 Thank you for confirming.
 @antonvlasenko are you able to update your PR with the above wording
 please?

 Adding `needs-refresh` workflow keyword.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 08:53:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 08:53:47 -0000
Subject: [wp-trac] [WordPress Trac] #54878: Don't show links to the
 Customizer when installing themes using api.wordpress.org
In-Reply-To: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
References: <057.58d6b8a0356e7d8352dbbb7dc92773a9@wordpress.org>
Message-ID: <072.b2a2d5e95e9a72f2704d6186e69242f2@wordpress.org>

#54878: Don't show links to the Customizer when installing themes using
api.wordpress.org
-------------------------------------------------+-------------------------
 Reporter:  antonvlasenko                        |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Themes                               |     Version:  5.9
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-screenshots commit     |     Focuses:
  fixed-major                                    |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * owner:  (none) => audrasjb
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53008" 53008]:
 {{{
 #!CommitTicketReference repository="" revision="53008"
 Themes: Hide block themes live preview link following installation.

 Prevent the Customizer/Live Preview button from showing for installed
 block themes when on the theme installation page.

 Props antonvlasenko, costdev, ironprogrammer.
 Merges [52819] to the 5.9 branch.
 Fixes #54878.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54878#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 09:11:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 09:11:13 -0000
Subject: [wp-trac] [WordPress Trac] #55241: Disabling
 "settings.color.duotone" within theme.json causes fatal error undefined
 variable $filter
In-Reply-To: <060.9051795adbc800c8c3362db8df670ecc@wordpress.org>
References: <060.9051795adbc800c8c3362db8df670ecc@wordpress.org>
Message-ID: <075.8f7912c90ad9ffb86150d3b2befacf85@wordpress.org>

#55241: Disabling "settings.color.duotone" within theme.json causes fatal error
undefined variable $filter
-----------------------------------+-----------------------
 Reporter:  aliakseyenkaihar       |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  closed
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Themes                 |     Version:  5.9.1
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53009" 53009]:
 {{{
 #!CommitTicketReference repository="" revision="53009"
 Themes: Avoid undefined variable warning on `get_svg_filters()`.

 This change fixes an undefined variable warning thrown when `duotone`
 color setting was set to null in Block Themes `theme.json` file.

 Follow-up to [52768].

 Props aliakseyenkaihar, audrasjb, rafiahmedd.
 Merges [52791] to the 5.9 branch.
 Fixes #55241.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55241#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 09:15:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 09:15:18 -0000
Subject: [wp-trac] [WordPress Trac] #54541: Add actions to template
 loading to assist with collecting debug info
In-Reply-To: <050.81a746532009d81ed322112d3f906dbf@wordpress.org>
References: <050.81a746532009d81ed322112d3f906dbf@wordpress.org>
Message-ID: <065.ded6e7be7a4f06f22b758bc33de5bc0c@wordpress.org>

#54541: Add actions to template loading to assist with collecting debug info
-------------------------+--------------------------
 Reporter:  rmccue       |       Owner:  johnbillion
     Type:  enhancement  |      Status:  reviewing
 Priority:  normal       |   Milestone:  6.0
Component:  Themes       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  performance
-------------------------+--------------------------
Changes (by johnbillion):

 * owner:  (none) => johnbillion
 * status:  new => reviewing
 * type:  defect (bug) => enhancement
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54541#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 09:16:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 09:16:21 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.b7361ceaa484222242b69e4314f00592@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change needs-refresh                           |  copy
-------------------------------------------------+-------------------------

Comment (by antonvlasenko):

 > Removing copy-review tag to move this ticket on.
 Thank you.
 @audrasjb Thanks for the ping.
 Yes, I will let you know once it's ready.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:33>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 10:53:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 10:53:00 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.dce9dc81e9befb32aed6fd764574f7f6@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * owner:  (none) => spacedmonkey
 * status:  new => assigned
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 11:05:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 11:05:43 -0000
Subject: [wp-trac] [WordPress Trac] #55372: Use tax_query in
 wp_get_nav_menu_items
In-Reply-To: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
References: <056.12d558db7e95d8b127f9b8e74452a479@wordpress.org>
Message-ID: <071.f4b7233dbb79916d50d7fdcab3249b4b@wordpress.org>

#55372: Use tax_query in wp_get_nav_menu_items
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Menus                                |     Version:  3.0
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch needs-unit-tests good-     |     Focuses:
  first-bug                                      |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53010" 53010]:
 {{{
 #!CommitTicketReference repository="" revision="53010"
 Menus: Convert `wp_get_nav_menu_items` function to use a taxonomy query.

 Change the `wp_get_nav_menu_items` function to replace the call to
 `get_objects_in_term` with a simple taxonomy query. This change improves
 performance as it results in one fewer query to retrieve menu items from
 the
 database.

 Props Spacedmonkey, peterwilsoncc.
 Fixes #55372.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55372#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 11:15:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 11:15:49 -0000
Subject: [wp-trac] [WordPress Trac] #47280: SQL_CALC_FOUND_ROWS is
 deprecated as of MySQL 8.0.17
In-Reply-To: <053.464f3453501834c73527d32600b297e3@wordpress.org>
References: <053.464f3453501834c73527d32600b297e3@wordpress.org>
Message-ID: <068.624febdb995090555cf5083e4cbfd7d8@wordpress.org>

#47280: SQL_CALC_FOUND_ROWS is deprecated as of MySQL 8.0.17
--------------------------------------+-----------------------------
 Reporter:  javorszky                 |       Owner:  johnbillion
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  Future Release
Component:  Database                  |     Version:
 Severity:  major                     |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+-----------------------------

Comment (by spacedmonkey):

 Related: #36881

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47280#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 12:30:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 12:30:26 -0000
Subject: [wp-trac] [WordPress Trac] #53565: Split packages and blocks
 into separate Weback configs
In-Reply-To: <051.dd67e5bae90e3bb8d46f8d1a7cc649cf@wordpress.org>
References: <051.dd67e5bae90e3bb8d46f8d1a7cc649cf@wordpress.org>
Message-ID: <066.ee432787ca1662c7954277d71dbfcf42@wordpress.org>

#53565: Split packages and blocks into separate Weback configs
------------------------------+-----------------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Future Release
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+-----------------------------

Comment (by gziolo):

 The bug report shared by @SergeyBiryukov should be fixed in #55311.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53565#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 12:33:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 12:33:07 -0000
Subject: [wp-trac] [WordPress Trac] #53565: Split packages and blocks
 into separate Weback configs
In-Reply-To: <051.dd67e5bae90e3bb8d46f8d1a7cc649cf@wordpress.org>
References: <051.dd67e5bae90e3bb8d46f8d1a7cc649cf@wordpress.org>
Message-ID: <066.d750668f177bb8e271c9d69b76cc266d@wordpress.org>

#53565: Split packages and blocks into separate Weback configs
------------------------------+-----------------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Future Release
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+-----------------------------

Comment (by gziolo):

 By the way, this issue can be closed because we were able to split the
 webpack config in WordPress 5.9 release cycle. Relate commit [51501].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53565#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 12:33:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 12:33:50 -0000
Subject: [wp-trac] [WordPress Trac] #53565: Split packages and blocks
 into separate Weback configs
In-Reply-To: <051.dd67e5bae90e3bb8d46f8d1a7cc649cf@wordpress.org>
References: <051.dd67e5bae90e3bb8d46f8d1a7cc649cf@wordpress.org>
Message-ID: <066.e39a27f97c609ae7da4f1725cdfed949@wordpress.org>

#53565: Split packages and blocks into separate Weback configs
------------------------------+-----------------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  Future Release
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch         |     Focuses:
------------------------------+-----------------------------
Changes (by gziolo):

 * status:  new => closed
 * resolution:   => fixed


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53565#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 12:41:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 12:41:18 -0000
Subject: [wp-trac] [WordPress Trac] #38741: Introduce the concept of a
 large site in order to speed up the Users screen when there are many users
In-Reply-To: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
References: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
Message-ID: <070.27223cfff03e678ec99217d7b45104b0@wordpress.org>

#38741: Introduce the concept of a large site in order to speed up the Users screen
when there are many users
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  spacedmonkey
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  early has-patch has-     |     Focuses:  administration,
  unit-tests commit                  |  multisite, performance
-------------------------------------+-------------------------------------
Changes (by spacedmonkey):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53011" 53011]:
 {{{
 #!CommitTicketReference repository="" revision="53011"
 Users: Introduce the concept of a large site to single site installations.

 Currently in WordPress multisite there is a concept of large networks. The
 function `wp_is_large_network` is used to determine if a network has a
 large number of sites or users. If a network is marked as large, then
 expensive queries to calculate user counts are not run on page load but
 deferred to scheduled events. However there are a number of places in a
 single site installation where this functionality would also be useful, as
 expensive calls to count users and roles can make screens in the admin
 extremely slow.

 In this change, the `get_user_count` function and related functionality
 around it is ported to be available in a single site context. This means
 that expensive calls to the `count_users` function are replaced with
 calls to `get_user_count`. This change also includes a new function called
 `wp_is_large_user_count` and a filter of the same name, to mark if a site
 is large.

 Props johnbillion, Spacedmonkey, Mista-Flo, lumpysimon, tharsheblows,
 obenland, miss_jwo, jrchamp, flixos90, macbookandrew, pento, desrosj,
 johnjamesjacoby, jb510, davidbaumwald, costdev.
 Fixes #38741.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38741#comment:80>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 12:54:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 12:54:15 -0000
Subject: [wp-trac] [WordPress Trac] #19901: Speeding up Dashboard and
 Comment moderation SQL load
In-Reply-To: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
References: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
Message-ID: <070.376f98a11a6b09cd9b4fb3c8d579cf6e@wordpress.org>

#19901: Speeding up Dashboard and Comment moderation SQL load
--------------------------------------------+--------------------------
 Reporter:  FolioVision                     |       Owner:  markjaquith
     Type:  enhancement                     |      Status:  accepted
 Priority:  normal                          |   Milestone:  6.0
Component:  Comments                        |     Version:  3.3
 Severity:  major                           |  Resolution:
 Keywords:  needs-testing has-patch commit  |     Focuses:  performance
--------------------------------------------+--------------------------
Changes (by spacedmonkey):

 * keywords:  needs-testing dev-feedback has-patch => needs-testing has-
     patch commit
 * milestone:  Future Release => 6.0


Comment:

 I have reviewed @uday17035 patch. It looks good to merge to me. I like the
 improve unit test.

 I am going to move this ticket into 6.0 milestone in hope that it can be
 merged.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19901#comment:32>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 12:56:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 12:56:11 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.dfc98bd369d6dd459d3a96d4031569d9@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
---------------------------+---------------------
 Reporter:  pgpagely       |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  5.9.3
Component:  Script Loader  |     Version:  5.9.1
 Severity:  major          |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+---------------------
Changes (by SergeyBiryukov):

 * milestone:  Awaiting Review => 5.9.3


Comment:

 Looks like this was committed in [52939], though the commit is not linked
 here, probably due to a Trac glitch.

 Moving for 5.9.3 consideration, per comment:12.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 12:58:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 12:58:31 -0000
Subject: [wp-trac] [WordPress Trac] #53565: Split packages and blocks
 into separate Weback configs
In-Reply-To: <051.dd67e5bae90e3bb8d46f8d1a7cc649cf@wordpress.org>
References: <051.dd67e5bae90e3bb8d46f8d1a7cc649cf@wordpress.org>
Message-ID: <066.e40a0de6563210f26760d9123c78107a@wordpress.org>

#53565: Split packages and blocks into separate Weback configs
------------------------------+------------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:  duplicate
 Keywords:  has-patch         |     Focuses:
------------------------------+------------------------
Changes (by SergeyBiryukov):

 * resolution:  fixed => duplicate
 * milestone:  Future Release =>


Comment:

 Replying to [comment:3 gziolo]:
 > The bug report shared by @SergeyBiryukov should be fixed in #55311.

 Perfect, thanks!

 Seems like this one can be closed as a duplicate of #53690 then.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53565#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:04:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:04:41 -0000
Subject: [wp-trac] [WordPress Trac] #55474: Backport bugfixes from
 Gutenberg into Core for WP 5.9.3
In-Reply-To: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
References: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
Message-ID: <067.4f1cb9fcb4e7fc8a0950555bfe88ff46@wordpress.org>

#55474: Backport bugfixes from Gutenberg into Core for WP 5.9.3
--------------------------------------+-----------------------
 Reporter:  audrasjb                  |       Owner:  mamaduka
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  5.9.3
Component:  Editor                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------

Comment (by audrasjb):

 In [changeset:"53012" 53012]:
 {{{
 #!CommitTicketReference repository="" revision="53012"
 Editor: Use `wp_unique_id()` instead of `uniqid()` to generate CSS class
 names.

 Backports changes from https://github.com/WordPress/gutenberg/pull/38891.
 See https://github.com/WordPress/gutenberg/issues/38889.

 Props westonruter, mamaduka.
 See #55474.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55474#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:07:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:07:28 -0000
Subject: [wp-trac] [WordPress Trac] #55474: Backport bugfixes from
 Gutenberg into Core for WP 5.9.3
In-Reply-To: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
References: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
Message-ID: <067.47e1957f0b10992a45dfce19949cc79b@wordpress.org>

#55474: Backport bugfixes from Gutenberg into Core for WP 5.9.3
--------------------------------------+-----------------------
 Reporter:  audrasjb                  |       Owner:  mamaduka
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  5.9.3
Component:  Editor                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------

Comment (by audrasjb):

 In [changeset:"53013" 53013]:
 {{{
 #!CommitTicketReference repository="" revision="53013"
 Editor: Use `wp_unique_id()` instead of `uniqid()` to generate CSS class
 names.

 Backports changes from https://github.com/WordPress/gutenberg/pull/38891.
 See https://github.com/WordPress/gutenberg/issues/38889.

 Props westonruter, mamaduka.
 Merges [53012] to the 5.9 branch.
 See #55474.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55474#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:13:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:13:07 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.372dd7febc642b806ea266a36342534f@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change                                         |  copy
-------------------------------------------------+-------------------------
Changes (by antonvlasenko):

 * keywords:  has-screenshots has-patch i18n-change needs-refresh => has-
     screenshots has-patch i18n-change


Comment:

 I've updated the wording.
 cc: @audrasjb
 [[Image(https://cldup.com/GdyP-_vlsF.png)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:19:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:19:40 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to
 allow for named parameters in WP 6.0
In-Reply-To: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
References: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
Message-ID: <072.b2e2d0a419fba5ced75dd48d2ce74c58@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
-----------------------------+---------------------
 Reporter:  peterwilsoncc    |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  php80 has-patch  |     Focuses:
-----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"53014" 53014]:
 {{{
 #!CommitTicketReference repository="" revision="53014"
 Code Modernization: Rename parameters that use reserved keywords in `wp-
 admin/includes/class-wp-filesystem-base.php`.

 While using reserved PHP keywords as parameter name labels is allowed, in
 the context of function calls using named parameters in PHP 8.0+, this
 will easily lead to confusion. To avoid that, it is recommended not to use
 reserved keywords as function parameter names.

 This commit renames the `$echo` parameter to `$verbose` in
 `WP_Filesystem_Base::find_base_dir()` and `::get_base_dir()`, and updates
 the documentation accordingly. This matches the class property of the same
 name.

 Follow-up to [52946], [52996], [52997], [52998], [53003].

 Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
 See #55327.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55327#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:26:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:26:54 -0000
Subject: [wp-trac] [WordPress Trac] #55474: Backport bugfixes from
 Gutenberg into Core for WP 5.9.3
In-Reply-To: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
References: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
Message-ID: <067.df1e66800c76fd1663c01fa8d391844d@wordpress.org>

#55474: Backport bugfixes from Gutenberg into Core for WP 5.9.3
--------------------------------------+-----------------------
 Reporter:  audrasjb                  |       Owner:  mamaduka
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  5.9.3
Component:  Editor                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------

Comment (by audrasjb):

 In [changeset:"53015" 53015]:
 {{{
 #!CommitTicketReference repository="" revision="53015"
 Editor: Change location of block support styles in `wp_head`.

 Backports changes from https://github.com/WordPress/gutenberg/pull/39164.

 Props ndiego, alexstine, cbravobernal, mamaduka.
 See #55474.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55474#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:34:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:34:52 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.18233c0b44a0e7b4204499eebdac753f@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note needs-docs needs-codex  |  performance
-------------------------------------------------+-------------------------
Changes (by milana_cap):

 * keywords:  has-patch has-unit-tests needs-testing needs-dev-note =>
     has-patch has-unit-tests needs-testing needs-dev-note needs-docs
     needs-codex


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:37:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:37:08 -0000
Subject: [wp-trac] [WordPress Trac] #38741: Introduce the concept of a
 large site in order to speed up the Users screen when there are many users
In-Reply-To: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
References: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
Message-ID: <070.1e2024f40227dd4bf25dd660f308c2b2@wordpress.org>

#38741: Introduce the concept of a large site in order to speed up the Users screen
when there are many users
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  spacedmonkey
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  early has-patch has-     |     Focuses:  administration,
  unit-tests commit                  |  multisite, performance
-------------------------------------+-------------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"53016" 53016]:
 {{{
 #!CommitTicketReference repository="" revision="53016"
 I18N: Move code out of a translatable string in `get_user_count()` and
 related functions.

 Follow-up to [53011].

 See #38741.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38741#comment:82>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:44:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:44:05 -0000
Subject: [wp-trac] [WordPress Trac] #53212: add post_type-specific
 version of the register_post_type_args filter
In-Reply-To: <050.9272e3495e02d50f60b170dffa0cf8e0@wordpress.org>
References: <050.9272e3495e02d50f60b170dffa0cf8e0@wordpress.org>
Message-ID: <065.d4691b70b8daee487858a836b7c0fba2@wordpress.org>

#53212: add post_type-specific version of the register_post_type_args filter
-------------------------------------------------+-------------------------
 Reporter:  pbiron                               |       Owner:  dlh
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Posts, Post Types                    |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-dev-note needs-unit-tests      |     Focuses:
  needs-patch needs-docs                         |
-------------------------------------------------+-------------------------
Changes (by milana_cap):

 * keywords:  needs-dev-note needs-unit-tests needs-patch => needs-dev-note
     needs-unit-tests needs-patch needs-docs


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53212#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:47:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:47:32 -0000
Subject: [wp-trac] [WordPress Trac] #55474: Backport bugfixes from
 Gutenberg into Core for WP 5.9.3
In-Reply-To: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
References: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
Message-ID: <067.12d27897666222e06d34d2267618ab4f@wordpress.org>

#55474: Backport bugfixes from Gutenberg into Core for WP 5.9.3
--------------------------------------+-----------------------
 Reporter:  audrasjb                  |       Owner:  mamaduka
     Type:  task (blessed)            |      Status:  assigned
 Priority:  normal                    |   Milestone:  5.9.3
Component:  Editor                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------

Comment (by audrasjb):

 In [changeset:"53017" 53017]:
 {{{
 #!CommitTicketReference repository="" revision="53017"
 Editor: Change location of block support styles in `wp_head`.

 Backports changes from https://github.com/WordPress/gutenberg/pull/39164.

 Props ndiego, alexstine, cbravobernal, mamaduka.
 Merges [53015] to the 5.9 branch.
 See #55474.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55474#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 13:52:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 13:52:10 -0000
Subject: [wp-trac] [WordPress Trac] #38741: Introduce the concept of a
 large site in order to speed up the Users screen when there are many users
In-Reply-To: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
References: <055.97ac093a8b92617e1098c75543bb32e3@wordpress.org>
Message-ID: <070.0ef8ce71da22ed10d94835520a50048b@wordpress.org>

#38741: Introduce the concept of a large site in order to speed up the Users screen
when there are many users
-------------------------------------+-------------------------------------
 Reporter:  johnbillion              |       Owner:  spacedmonkey
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:  fixed
 Keywords:  early has-patch has-     |     Focuses:  administration,
  unit-tests commit                  |  multisite, performance
-------------------------------------+-------------------------------------

Comment (by SergeyBiryukov):

 In [changeset:"53018" 53018]:
 {{{
 #!CommitTicketReference repository="" revision="53018"
 Users: Move `get_user_count()` and related functions to `wp-
 includes/user.php`.

 The new location is next to the pre-existing `count_users()` function,
 along with other user-specific functions, and should be a more appropriate
 place in terms of consistency.

 This affects:
 * `get_user_count()`
 * `wp_maybe_update_user_counts()`
 * `wp_update_user_counts()`
 * `wp_schedule_update_user_counts()`
 * `wp_is_large_user_count()`

 Follow-up to [53011], [53016].

 See #38741.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38741#comment:83>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 14:17:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 14:17:29 -0000
Subject: [wp-trac] [WordPress Trac] #55057: WebP EXIF data missing and
 images are not rotated in the same way JPEG images are rotated.
In-Reply-To: <050.cb1caad48c4abb96a7d234f408387e2f@wordpress.org>
References: <050.cb1caad48c4abb96a7d234f408387e2f@wordpress.org>
Message-ID: <065.7d7769f8131321e56c9549442d859081@wordpress.org>

#55057: WebP EXIF data missing and images are not rotated in the same way JPEG
images are rotated.
--------------------------+------------------------------
 Reporter:  mitogh        |       Owner:  adamsilverstein
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Media         |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  performance
--------------------------+------------------------------
Changes (by codekraft):

 * Attachment "arrow.avif" added.

 test file arrow.avif (exif has orientation 8)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55057>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 14:21:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 14:21:17 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.394f95d40ab49e7ca73be09cc9f20bec@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  marybaum
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots commit                             |  accessibility
-------------------------------------------------+-------------------------
Changes (by marybaum):

 * keywords:  a11y-proximity has-patch has-screenshots needs-testing =>
     a11y-proximity has-patch has-screenshots commit
 * status:  assigned => accepted


Comment:

 Applied the patch to a local site running 5.9.2 and Twenty-Twenty-Two, and
 it works nicely!

 Recommend moving this along to commit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55364#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 14:34:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 14:34:30 -0000
Subject: [wp-trac] [WordPress Trac] #53951: Twenty Twenty: Search modal
 aria-expanded
In-Reply-To: <050.12159b56833732edace4c7af59831987@wordpress.org>
References: <050.12159b56833732edace4c7af59831987@wordpress.org>
Message-ID: <065.c82468816efb891fc933513bbfc79c3a@wordpress.org>

#53951: Twenty Twenty: Search modal aria-expanded
-------------------------------------+-------------------------------------
 Reporter:  utz119                   |       Owner:  alexstine
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-testing-   |     Focuses:  accessibility,
  instructions needs-testing         |  javascript
-------------------------------------+-------------------------------------
Changes (by afercia):

 * Attachment "53951.4.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53951>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 14:36:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 14:36:35 -0000
Subject: [wp-trac] [WordPress Trac] #55476: Add heart icon for favorite
 plugins to plugin page in the "add plugin' area of wp-admin
In-Reply-To: <054.0ed5a4529ec43e97b4fa567aadab2518@wordpress.org>
References: <054.0ed5a4529ec43e97b4fa567aadab2518@wordpress.org>
Message-ID: <069.3385a51bd4a123623784b7c44cd9547b@wordpress.org>

#55476: Add heart icon for favorite plugins to plugin page in the "add plugin' area
of wp-admin
-------------------------+----------------------
 Reporter:  dansoschin   |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Plugins      |     Version:
 Severity:  minor        |  Resolution:  invalid
 Keywords:               |     Focuses:
-------------------------+----------------------
Changes (by davidbaumwald):

 * milestone:  Awaiting Review =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55476#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 14:41:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 14:41:52 -0000
Subject: [wp-trac] [WordPress Trac] #55477: Add Custom Post Types Archive
 Pages to Sitemap
Message-ID: <056.8f28439faf2085af9d4e6d0618d7459d@wordpress.org>

#55477: Add Custom Post Types Archive Pages to Sitemap
--------------------------+-----------------------------
 Reporter:  delitestudio  |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Sitemaps      |    Version:  5.9.2
 Severity:  major         |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 The CPT archive pages do not appear in the sitemap, and there are no
 suitable hooks to add them (e.g. `wp_sitemaps_posts_query_args`,
 `wp_sitemaps_posts_pre_url_list`, etc.).

 In my opinion it is necessary:

 * automatically include all archive pages of custom posts with
 `has_archive` other than `false`, and
 * insert a hook to add additional links

 Thanks!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55477>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 14:47:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 14:47:25 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.ce1e9160a53025f6fb418240389791b7@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note needs-docs needs-codex  |  performance
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * Attachment "55443.4.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 14:49:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 14:49:38 -0000
Subject: [wp-trac] [WordPress Trac] #55439: Introduce term_exists_args
 filter
In-Reply-To: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
References: <050.1e2fd0dada12d898127a9c3f5d6417ed@wordpress.org>
Message-ID: <065.d971788e6f6d39c918b860be46399395@wordpress.org>

#55439: Introduce term_exists_args filter
-------------------------------------------------+-------------------------
 Reporter:  Chouby                               |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Taxonomy                             |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch needs-dev-note needs-docs  |     Focuses:
-------------------------------------------------+-------------------------
Changes (by milana_cap):

 * keywords:  has-patch needs-dev-note => has-patch needs-dev-note needs-
               docs


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55439#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 14:52:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 14:52:36 -0000
Subject: [wp-trac] [WordPress Trac] #53951: Twenty Twenty: Search modal
 aria-expanded
In-Reply-To: <050.12159b56833732edace4c7af59831987@wordpress.org>
References: <050.12159b56833732edace4c7af59831987@wordpress.org>
Message-ID: <065.91df535eae5e998b20ea285da3c02c70@wordpress.org>

#53951: Twenty Twenty: Search modal aria-expanded
-------------------------------------+-------------------------------------
 Reporter:  utz119                   |       Owner:  alexstine
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-testing-   |     Focuses:  accessibility,
  instructions needs-testing         |  javascript
-------------------------------------+-------------------------------------

Comment (by afercia):

 Thanks @alexstine, good catch.

 I just noticed there's one more issue related to another button. When the
 mobile navigation menu is open, there's a 'Close menu' button. The aria-
 expanded attribute on this button isn't handled correctly.

 Also, there's one more inconsistency:
 - The 'Close Menu' button does have an initial aria-expanded attribute
 which is printed out on the PHP side.
 - The 'Close search' button does not.

 We could argue whether a 'Close' button really needs an aria-expanded
 attribute. To me, a 'Close' button implies that something is open /
 expanded. Removing this aria-expanded attribute would also make things
 easier to fix on the JavaScript side.

 The latest patch [attachment:"53951.4.diff"]
 - Removes aria-expanded from the 'Close Menu' button.
 - On the JavaScript side, skips both the 'Close search' and 'Close Menu'
 buttons by checking whether the attribute to toggle exists.

 Some testing would be nice.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53951#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:01:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:01:35 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.8820c6886f40687405614318ed030850@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+-----------------------
 Reporter:  ademos                    |       Owner:  marybaum
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+-----------------------
Changes (by marybaum):

 * milestone:  Awaiting Review =>


Comment:

 This is also true of categories:the Bulk Edit UI lets us add categories
 but not remove them. In fact, it doesn't show which categories are even
 already applied.

 Quick edit, on a single post, shows the applied categories and lets us
 uncheck the boxes, but that goes away once we're in bulk mode.

 So this is part of a broader UI discussion and needs to go to a future
 release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:08:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:08:27 -0000
Subject: [wp-trac] [WordPress Trac] #53951: Twenty Twenty: Search modal
 aria-expanded
In-Reply-To: <050.12159b56833732edace4c7af59831987@wordpress.org>
References: <050.12159b56833732edace4c7af59831987@wordpress.org>
Message-ID: <065.a1b75db53969e20370767d9a72928fdd@wordpress.org>

#53951: Twenty Twenty: Search modal aria-expanded
-------------------------------------+-------------------------------------
 Reporter:  utz119                   |       Owner:  alexstine
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-testing-   |     Focuses:  accessibility,
  instructions needs-testing         |  javascript
-------------------------------------+-------------------------------------

Comment (by alexstine):

 @afercia Your patch works perfectly. None of the close buttons get aria-
 expanded anymore and attribute values seem to stay in sync.

 Thanks!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53951#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:08:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:08:56 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.c5adbfd8f7f79df532e1600651fc9328@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
-------------------------------------------------+-------------------------
 Reporter:  isaumya                              |       Owner:
                                                 |  adamsilverstein
     Type:  feature request                      |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  refresh                                        |  performance
-------------------------------------------------+-------------------------
Changes (by adamsilverstein):

 * Attachment "53232.4.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:13:55 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:13:55 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.9193feeecc00a0302c3a15dc038b5e85@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
-------------------------------------------------+-------------------------
 Reporter:  isaumya                              |       Owner:
                                                 |  adamsilverstein
     Type:  feature request                      |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  refresh                                        |  performance
-------------------------------------------------+-------------------------

Comment (by adamsilverstein):

 @peterwilsoncc updated patch, ready for review.


 > The latest PR is in draft

 I generally open draft PRs to run tests and garner feedback but since we
 don't merge in GitHub I always keep them as draft. The draft status is not
 an indication of readiness!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:54>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:14:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:14:23 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.72ec07c4cc796799707fd364d19ef472@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
 Reporter:  ademos                    |       Owner:  marybaum
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+------------------------------

Comment (by marybaum):

 Have confirmed the behavior with tags, and I'll note here that the same
 thing is true of categories. You can add them in the Bulk Editor but not
 change them or remove any--the UI doesn't show which categories are
 checked.

 The Quick Editor does show which categories are checked, and you can
 uncheck and recheck to your heart's content.

 I took a look at @paaljoachim's Figma prototype--it's faithful to the tags
 UI in the post editors, both block and Classic, and therefore slightly
 different from the Categories UI. My question: should it be?

 @paaljoachim, does it make sense for you to own this process, and the
 ticket, going forward?

 Or, should we use a single pattern style for both categories and tags, and
 standardize that across Bulk, Quick, block and Classic editors?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:20:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:20:30 -0000
Subject: [wp-trac] [WordPress Trac] #54916: Admin panel's "Customizer"
 sub menu is replaced with "Widgets" for block based themes
In-Reply-To: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
References: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
Message-ID: <066.19632fee465b7abf1959288e94da8100@wordpress.org>

#54916: Admin panel's "Customizer" sub menu is replaced with "Widgets" for block
based themes
-----------------------------------+-----------------------
 Reporter:  Rufus87                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  accepted
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Administration         |     Version:  5.9
 Severity:  major                  |  Resolution:
 Keywords:  2nd-opinion has-patch  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-29 à 17.20.00.png" added.

 Using a classic theme: no change

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54916>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:20:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:20:53 -0000
Subject: [wp-trac] [WordPress Trac] #54916: Admin panel's "Customizer"
 sub menu is replaced with "Widgets" for block based themes
In-Reply-To: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
References: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
Message-ID: <066.3ee59f9a9e16fcb72f1090e8e1d20b9d@wordpress.org>

#54916: Admin panel's "Customizer" sub menu is replaced with "Widgets" for block
based themes
-----------------------------------+-----------------------
 Reporter:  Rufus87                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  accepted
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Administration         |     Version:  5.9
 Severity:  major                  |  Resolution:
 Keywords:  2nd-opinion has-patch  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-29 à 17.19.46.png" added.

 Using a block theme without widget support: no change

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54916>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:21:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:21:46 -0000
Subject: [wp-trac] [WordPress Trac] #54916: Admin panel's "Customizer"
 sub menu is replaced with "Widgets" for block based themes
In-Reply-To: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
References: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
Message-ID: <066.440703df6a75a57533e26b1353e525b2@wordpress.org>

#54916: Admin panel's "Customizer" sub menu is replaced with "Widgets" for block
based themes
-----------------------------------+-----------------------
 Reporter:  Rufus87                |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  accepted
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Administration         |     Version:  5.9
 Severity:  major                  |  Resolution:
 Keywords:  2nd-opinion has-patch  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * Attachment "Capture d’écran 2022-03-29 à 17.19.30.2.png" added.

 Using a block theme which supports widgets: the menu is located at the
 last position

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54916>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:23:34 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:23:34 -0000
Subject: [wp-trac] [WordPress Trac] #54916: Admin panel's "Customizer"
 sub menu is replaced with "Widgets" for block based themes
In-Reply-To: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
References: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
Message-ID: <066.9a0b0c4ead6bf47a99fb5c1d81a827d5@wordpress.org>

#54916: Admin panel's "Customizer" sub menu is replaced with "Widgets" for block
based themes
----------------------------+-----------------------
 Reporter:  Rufus87         |       Owner:  audrasjb
     Type:  defect (bug)    |      Status:  accepted
 Priority:  normal          |   Milestone:  5.9.3
Component:  Administration  |     Version:  5.9
 Severity:  major           |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  2nd-opinion has-patch => has-patch


Comment:

 As everyone was comfortable with this proposal during the last bug
 scrub(s), I'd suggest to go with this solution.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54916#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:32:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:32:40 -0000
Subject: [wp-trac] [WordPress Trac] #55023: get_header() notice: Theme
 without header.php is deprecated
In-Reply-To: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
References: <049.8ae3174727f1c07ec2b6f7b68ce06010@wordpress.org>
Message-ID: <064.fe12c0c4ec6d27e0389718eed40e159e@wordpress.org>

#55023: get_header() notice: Theme without header.php is deprecated
--------------------------+------------------------
 Reporter:  kpdaa         |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  5.9.4
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  multisite
--------------------------+------------------------
Changes (by audrasjb):

 * milestone:  5.9.3 => 5.9.4


Comment:

 Since WordPress 5.9.3 Release Candidate is supposed to be released today,
 and as this ticket is still waiting for a patch, let's move it to
 milestone 5.9.4.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55023#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:34:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:34:09 -0000
Subject: [wp-trac] [WordPress Trac] #55163: Block editor package updates
 for 5.9.2
In-Reply-To: <057.592ddbec8c4672824192e46eda976f2d@wordpress.org>
References: <057.592ddbec8c4672824192e46eda976f2d@wordpress.org>
Message-ID: <072.7112dc3e604a2b6a22cecb6ef17a76ec@wordpress.org>

#55163: Block editor package updates for 5.9.2
----------------------------+-------------------------
 Reporter:  peterwilsoncc   |       Owner:  (none)
     Type:  task (blessed)  |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Editor          |     Version:
 Severity:  normal          |  Resolution:  duplicate
 Keywords:                  |     Focuses:  javascript
----------------------------+-------------------------
Changes (by audrasjb):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  5.9.3 =>


Comment:

 Closing this as duplicate of #55474.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55163#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:34:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:34:44 -0000
Subject: [wp-trac] [WordPress Trac] #55172: Twenty Twenty-Two: Add
 "Accessibility Ready" tag to theme in repository
In-Reply-To: <047.b9d143ec205798743730f710212f590b@wordpress.org>
References: <047.b9d143ec205798743730f710212f590b@wordpress.org>
Message-ID: <062.d2c0563feac651e9ea27b2c02e7b520c@wordpress.org>

#55172: Twenty Twenty-Two: Add "Accessibility Ready" tag to theme in repository
----------------------------+----------------------------
 Reporter:  bph             |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  5.9.4
Component:  Bundled Theme   |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  accessibility
----------------------------+----------------------------
Changes (by audrasjb):

 * milestone:  5.9.3 => 5.9.4


Comment:

 Moving to the next point release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55172#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:35:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:35:52 -0000
Subject: [wp-trac] [WordPress Trac] #55189: Automatic removal of
 "Zero-width non-joiner" in URL
In-Reply-To: <053.3e9eb622a7f5219df8181821b4d758f9@wordpress.org>
References: <053.3e9eb622a7f5219df8181821b4d758f9@wordpress.org>
Message-ID: <068.1213504d5bb877ea6ead726844373b21@wordpress.org>

#55189: Automatic removal of "Zero-width non-joiner" in URL
--------------------------+---------------------
 Reporter:  man4toman     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.4
Component:  Permalinks    |     Version:  5.9
 Severity:  critical      |  Resolution:
 Keywords:  2nd-opinion   |     Focuses:
--------------------------+---------------------
Changes (by audrasjb):

 * milestone:  5.9.3 => 5.9.4


Comment:

 Given 5.9.3 is supposed to be released soon, and as this ticket is still
 waiting for a patch, let's move it to milestone 5.9.4.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55189#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:36:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:36:25 -0000
Subject: [wp-trac] [WordPress Trac] #55195: Calling `::parent()` on a
 child theme object where parent theme is missing `index.php` returns false
 in WP5.9
In-Reply-To: <050.b5d912731774c2eca5c548a70ab051d9@wordpress.org>
References: <050.b5d912731774c2eca5c548a70ab051d9@wordpress.org>
Message-ID: <065.ca107a94790bb1e72b70354fcbf3682c@wordpress.org>

#55195: Calling `::parent()` on a child theme object where parent theme is missing
`index.php` returns false in WP5.9
--------------------------+---------------------
 Reporter:  robdxw        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  5.9.4
Component:  Themes        |     Version:  5.9
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+---------------------
Changes (by audrasjb):

 * milestone:  5.9.3 => 5.9.4


Comment:

 Given 5.9.3 is supposed to be released soon, and as this ticket is still
 waiting for a patch, let's move it to milestone 5.9.4.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55195#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:38:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:38:40 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.f2296f79e7999e729ea3612db06bbdea@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
-----------------------------------+-----------------------
 Reporter:  pgpagely               |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  accepted
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Script Loader          |     Version:  5.9.1
 Severity:  major                  |  Resolution:
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch fixed-major
 * owner:  (none) => audrasjb
 * status:  new => accepted


Comment:

 Alrighty, I'm going to backport this one to branch 5.9 now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:42:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:42:00 -0000
Subject: [wp-trac] [WordPress Trac] #55311: Style and JS URLs for some
 blocks are broken when using WP outside of the current prefix
In-Reply-To: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
References: <052.71705d312df930659699caa7e0d22c46@wordpress.org>
Message-ID: <067.b82d9a8e25ab7cc48e70066200fd4af6@wordpress.org>

#55311: Style and JS URLs for some blocks are broken when using WP outside of the
current prefix
-----------------------------------+-----------------------
 Reporter:  pgpagely               |       Owner:  audrasjb
     Type:  defect (bug)           |      Status:  closed
 Priority:  normal                 |   Milestone:  5.9.3
Component:  Script Loader          |     Version:  5.9.1
 Severity:  major                  |  Resolution:  fixed
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-----------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53019" 53019]:
 {{{
 #!CommitTicketReference repository="" revision="53019"
 Editor: Fix broken asset URLs when using WP outside of the regular
 directory

 Both CSS and JS URLs were totally broken for some of the newer blocks
 (e.g. the navigation block in the 2022 theme) when WP core is outside of
 the current directory using a different prefix.

 Props gziolo, SergeyBiryukov, pgpagely, Mamaduka.
 Merges [52939] to the 5.9 branch.
 Fixes #55311.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55311#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:50:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:50:41 -0000
Subject: [wp-trac] [WordPress Trac] #54916: Admin panel's "Customizer"
 sub menu is replaced with "Widgets" for block based themes
In-Reply-To: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
References: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
Message-ID: <066.bd2b0a0d1cbab0e0774f93fb19d05dbb@wordpress.org>

#54916: Admin panel's "Customizer" sub menu is replaced with "Widgets" for block
based themes
------------------------------+-----------------------
 Reporter:  Rufus87           |       Owner:  audrasjb
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  5.9.3
Component:  Administration    |     Version:  5.9
 Severity:  major             |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch => has-patch commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54916#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 15:57:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 15:57:24 -0000
Subject: [wp-trac] [WordPress Trac] #54916: Admin panel's "Customizer"
 sub menu is replaced with "Widgets" for block based themes
In-Reply-To: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
References: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
Message-ID: <066.76c230a23487c673133a878ad7867a08@wordpress.org>

#54916: Admin panel's "Customizer" sub menu is replaced with "Widgets" for block
based themes
------------------------------+-----------------------
 Reporter:  Rufus87           |       Owner:  audrasjb
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  5.9.3
Component:  Administration    |     Version:  5.9
 Severity:  major             |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53020" 53020]:
 {{{
 #!CommitTicketReference repository="" revision="53020"
 Administration: Do not specify menu order for the Widgets menu when the
 active theme is a block theme.

 When using a block theme that declares Widgets support, it's better to not
 specify a menu order for the Widgets menu to avoid conflicts between menu
 items order.

 Props Rufus87, ironprogrammer, audrasjb, hellofromTonya, davidbaumwald.
 Fixes #54916.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54916#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 16:00:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 16:00:48 -0000
Subject: [wp-trac] [WordPress Trac] #54916: Admin panel's "Customizer"
 sub menu is replaced with "Widgets" for block based themes
In-Reply-To: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
References: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
Message-ID: <066.0292f2a6b0896097c53b0014445d8cc5@wordpress.org>

#54916: Admin panel's "Customizer" sub menu is replaced with "Widgets" for block
based themes
------------------------------------------+-----------------------
 Reporter:  Rufus87                       |       Owner:  audrasjb
     Type:  defect (bug)                  |      Status:  reopened
 Priority:  normal                        |   Milestone:  5.9.3
Component:  Administration                |     Version:  5.9
 Severity:  major                         |  Resolution:
 Keywords:  has-patch commit fixed-major  |     Focuses:
------------------------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch commit => has-patch commit fixed-major
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Reopening for backport to branch 59

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54916#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 16:22:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 16:22:48 -0000
Subject: [wp-trac] [WordPress Trac] #54916: Admin panel's "Customizer"
 sub menu is replaced with "Widgets" for block based themes
In-Reply-To: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
References: <051.12e6e8abced3b1041082f6effe24f1a7@wordpress.org>
Message-ID: <066.025862b38ea038fa7a49f5fe3033c478@wordpress.org>

#54916: Admin panel's "Customizer" sub menu is replaced with "Widgets" for block
based themes
------------------------------------------+-----------------------
 Reporter:  Rufus87                       |       Owner:  audrasjb
     Type:  defect (bug)                  |      Status:  closed
 Priority:  normal                        |   Milestone:  5.9.3
Component:  Administration                |     Version:  5.9
 Severity:  major                         |  Resolution:  fixed
 Keywords:  has-patch commit fixed-major  |     Focuses:
------------------------------------------+-----------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53021" 53021]:
 {{{
 #!CommitTicketReference repository="" revision="53021"
 Administration: Do not specify menu order for the Widgets menu when the
 active theme is a block theme.

 When using a block theme that declares Widgets support, it's better to not
 specify a menu order for the Widgets menu to avoid conflicts between menu
 items order.

 Props Rufus87, ironprogrammer, audrasjb, hellofromTonya, davidbaumwald.
 Merges [53020] to the 5.9 branch.
 Fixes #54916.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54916#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 16:29:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 16:29:05 -0000
Subject: [wp-trac] [WordPress Trac] #52409: Upload method SSH2 shouldn't
 use hardwired ssh-rsa hostkey
In-Reply-To: <057.3602062aad03c8dfd1ad5b35e08c8718@wordpress.org>
References: <057.3602062aad03c8dfd1ad5b35e08c8718@wordpress.org>
Message-ID: <072.e30782a00bfd42cd1df1bd27e94b7c6e@wordpress.org>

#52409: Upload method SSH2 shouldn't use hardwired ssh-rsa hostkey
----------------------------+-----------------------------
 Reporter:  richybkreckel   |       Owner:  SergeyBiryukov
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  5.9.3
Component:  Filesystem API  |     Version:
 Severity:  normal          |  Resolution:  fixed
 Keywords:  fixed-major     |     Focuses:
----------------------------+-----------------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53022" 53022]:
 {{{
 #!CommitTicketReference repository="" revision="53022"
 Filesystem API: Include the `ssh-ed25519` public key signature algorithm
 as an alternative to `ssh-rsa`.

 The `ssh-rsa` signature algorithm is disabled by default as of OpenSSH
 8.8, which breaks SSH2 uploads in WordPress on modern systems. `ssh-
 ed25519` is one of the suggested alternatives, supported since OpenSSH
 6.5.

 References:

 - OpenSSH 8.2 release notes
 - OpenSSH 8.7 release notes
 - OpenSSH 8.8 release notes

 Follow-up to [8865].

 Props richybkreckel, dd32, SergeyBiryukov.
 Merges [52807] to the 5.9 branch.
 Fixes #52409.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52409#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 16:33:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 16:33:31 -0000
Subject: [wp-trac] [WordPress Trac] #55121: classic widgets with no
 settings won't show up in 5.9
In-Reply-To: <055.8e03d473425ccb044fc650bf3cf2c1f7@wordpress.org>
References: <055.8e03d473425ccb044fc650bf3cf2c1f7@wordpress.org>
Message-ID: <070.e321736647b679b31ddff20a6480dbdb@wordpress.org>

#55121: classic widgets with no settings won't show up in 5.9
----------------------------+-----------------------
 Reporter:  joncampbell     |       Owner:  (none)
     Type:  defect (bug)    |      Status:  reopened
 Priority:  normal          |   Milestone:  5.9.4
Component:  Widgets         |     Version:  5.9
 Severity:  normal          |  Resolution:
 Keywords:  has-patch php8  |     Focuses:
----------------------------+-----------------------
Changes (by audrasjb):

 * milestone:  5.9.3 => 5.9.4


Comment:

 Moving to milestone 5.9.4.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55121#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 16:59:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 16:59:20 -0000
Subject: [wp-trac] [WordPress Trac] #55478: Thumbnail not generating for
 uploaded PDF files
Message-ID: <050.1fa33ae7645721316a8cf0ed450e2ac0@wordpress.org>

#55478: Thumbnail not generating for uploaded PDF files
----------------------------+-----------------------------
 Reporter:  cyjosh          |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Media           |    Version:  5.9.2
 Severity:  normal          |   Keywords:
  Focuses:  administration  |
----------------------------+-----------------------------
 This might be related to this issue:
 https://core.trac.wordpress.org/ticket/55457
 But in my case, uploading PDF files via the media library does not
 generate a preview thumbnail.

 Running {{{wp media regenerate --only-missing}}} generates the thumbnails.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55478>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 17:14:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 17:14:12 -0000
Subject: [wp-trac] [WordPress Trac] #41833: Excerpt disappear in excerpt
 mode post list, after quick edit
In-Reply-To: <052.2fc790b84d9b7f6d6fa7c67a6ba76c70@wordpress.org>
References: <052.2fc790b84d9b7f6d6fa7c67a6ba76c70@wordpress.org>
Message-ID: <067.d408f75953ec11ccbe1699f10a830cdd@wordpress.org>

#41833: Excerpt disappear in excerpt mode post list, after quick edit
-----------------------------+------------------------------
 Reporter:  satnapar         |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit  |     Version:  4.8.1
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by marybaum):

 The local site I use for testing runs 5.9.2 and Twenty Twenty-Two at the
 moment, and my Bulk/Quick Edit UI doesn't ever show the excerpt--doesn't
 even have a screen option to show it. Neither has, to my knowledge, any
 version of WordPress or Genesis, or any Genesis child theme I've ever
 used.

 So I am completely unable to give gfood guidance on this.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41833#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 17:17:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 17:17:38 -0000
Subject: [wp-trac] [WordPress Trac] #55478: Thumbnail not generating for
 uploaded PDF files
In-Reply-To: <050.1fa33ae7645721316a8cf0ed450e2ac0@wordpress.org>
References: <050.1fa33ae7645721316a8cf0ed450e2ac0@wordpress.org>
Message-ID: <065.31a32d3d8d629b8ee2dd97f8ef95c694@wordpress.org>

#55478: Thumbnail not generating for uploaded PDF files
--------------------------+------------------------------
 Reporter:  cyjosh        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  5.9.2
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  administration
--------------------------+------------------------------
Changes (by cyjosh):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Looks like this is a specific issue to PHP 8 on WP Engine hosting.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55478#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 17:25:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 17:25:46 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.3c1da8e56360855bb473cda3c5ae9792@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------
Changes (by azouamauriac):

 * Attachment "54728.6.diff" added.

 Fix "WordPress.PHP.StrictComparisons.LooseComparison" in src/wp-admin/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 18:14:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 18:14:32 -0000
Subject: [wp-trac] [WordPress Trac] #55480: Add filter to modify description
 in plugin card
Message-ID: <051.94a4e115d6db28b6e051abfb65a2ef2b@wordpress.org>

#55480: Add filter to modify description in plugin card
-----------------------------+-----------------------------
 Reporter:  afragen          |      Owner:  (none)
     Type:  enhancement      |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:
 Severity:  normal           |   Keywords:  has-patch
  Focuses:  administration   |
-----------------------------+-----------------------------
 I've found it desirable to be able to modify the description of the plugin
 card in the plugin install list table.

 If possible I would like to add a filter for this variable.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55480>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 18:40:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 18:40:59 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.9652c0be5d310e20816d59ccded00bff@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch 2nd-opinion    |  javascript
-------------------------------------+-------------------------------------
Changes (by joedolson):

 * keywords:  has-screenshots title-attribute has-patch needs-testing =>
     has-screenshots title-attribute has-patch 2nd-opinion


Comment:

 @afercia In the post title source that theTitle pulls, the emoji is an
 `<img>` with an alt attribute containing the emoji character. As a result,
 calling `.replace( /<.[^<>]*?>/g, '' )` removes the emoji. So I'm not sure
 that problem is solved. Is this replacement necessary? If we can assume
 that the source is already escaped in PHP, I'm not sure we need to do
 this.

 Other than that, this looks like it works well to me. I'd appreciate a
 second opinion on the necessity of escaping the JS post title; but if we
 end up still losing the emoji in the screen reader text, I'd still think
 this can be committed.

 Everything works well as far as I can see.

 Tested in NVDA/Chrome, Jaws/Firefox, Jaws/Edge.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35483#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 18:49:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 18:49:29 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.dd841e0ea5912e76d3c86f5dc0a67062@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots commit                             |  accessibility
-------------------------------------------------+-------------------------
Changes (by joedolson):

 * owner:  marybaum => joedolson


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55364#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:07:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:07:14 -0000
Subject: [wp-trac] [WordPress Trac] #55364: Proximity of controls: Quick
 Edit and Bulk Edit forms improvements
In-Reply-To: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
References: <051.0b3191a1c02c5f0ec134d9ee1a128932@wordpress.org>
Message-ID: <066.0048ab3dbbe220f7029e981b9b564112@wordpress.org>

#55364: Proximity of controls: Quick Edit and Bulk Edit forms improvements
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Quick/Bulk Edit                      |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  a11y-proximity has-patch has-        |     Focuses:
  screenshots commit                             |  accessibility
-------------------------------------------------+-------------------------
Changes (by joedolson):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53023" 53023]:
 {{{
 #!CommitTicketReference repository="" revision="53023"
 Quick/Bulk Edit: Position action buttons in close proximity.

 Move the Submit and Cancel buttons in quick edit forms to be next to each
 other and change the order of the buttons. Improve accessibility for low
 vision and cognitive impairments for quick editing.

 Props afercia, marybaum.
 Fixes #55364.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55364#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:07:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:07:37 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.acbf0b99a3f3024ef39b61b4064967bb@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit                                  |  copy
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53024" 53024]:
 {{{
 #!CommitTicketReference repository="" revision="53024"
 Customizer: When a block theme is active, add an information about Site
 Editor in the Customizer.

 This change adds an information notice to the customizer when a block
 theme is active and the customizer is also available (for example when a
 plugin activates it), to encourage people to use the Site Editor for the
 best full site customization experience.

 Props ironprogrammer, antonvlasenko, Clorith, audrasjb, psmits1567,
 tobifjellner, costdev, webcommsat.
 Fixes #54939.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:09:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:09:52 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.1c7df8e24d242f85c0434b954574c8e0@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-screenshots has-patch i18n-change commit => has-
     screenshots has-patch i18n-change commit fixed-major


Comment:

 Reopening for backport consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:10:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:10:00 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.826cf7944c9fd33fedf806687179401b@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  closed => reopened
 * resolution:  fixed =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:38>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:12:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:12:17 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.42c609edfdb31d6018d5bb16bc219415@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 Hmm.

 I committed the proposed patch, but I can see at least 2 accessibility
 issues.

 - Links that open a new windows should be announced
 - With `$switch_to_site_editor_label`, the same link is used for both the
 button text and its `aria-label`

 I'm unsure about the best solution: fix the issues directly or revert this
 commit before 5.9.3 and move the issue to the next major.

 Thoughts?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:20:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:20:13 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.d9f5400689ac81189c61e4adce249dc9@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch 2nd-opinion    |  javascript
-------------------------------------+-------------------------------------

Comment (by joedolson):

 There aren't a lot of examples of data passed from PHP into JS via
 wp.i18n, but in `plugin-install.js` the plugin title is passed without
 escaping. Also noting @swissspidy's [https://pascalbirchler.com
 /internationalization-in-wordpress-5-0/ comments on escaping in JS
 internationalization].

 So, overall, I don't think this is necessary.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35483#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:22:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:22:46 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.d9623c6a9df48061c7a966f4150d2251@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------

Comment (by antonvlasenko):

 @audrasjb
 > Links that open a new windows should be announced
 I can create another PR that will remove the `target="_blank"` attribute.
 It seemed logical to me to open this page in a new window.
 Users might want to continue editing their theme after learning about Full
 Site Editing. If the the `target="_blank"` attribute is not used, they
 would need to go to the WordPress admin section again to edit their theme.
 I didn't know such links had to be announced.

 > With `$switch_to_site_editor_label`, the same link is used for both the
 button text and its aria-label
 I don't exactly understand this issue.
 `$switch_to_site_editor_label` contains text that says `Use Site Editor`.
 Is there any issue with having this exact text in 2 different places?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:40>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:25:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:25:18 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.9786a0773e8e5d94d115d4c865504cbc@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 - Yes opening a new window needs to be announced at least in a screen
 reader text.
 - Text duplication needs to be removed to avoid duplicate read on screen
 reader text tools.

 I'm going to add a PR to fix those issues :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:42>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:28:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:28:01 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.c216ebdb9b5a4ab662501a62602579b3@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 Also, the translator texts are wrong, the incoming PR will fix a small
 i18n issue :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:44>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:40:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:40:04 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.bce1241af3f48ed8b78ddf5a21406365@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by knutsp):

 {{{#!php
 <?php
 1 === $_GET['test']
 }}}
 will never evaluate to true, as `$_REQUEST` values are all strings. Keep
 the loose comparison.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:51>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:43:52 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:43:52 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.245855c7a16d30309446488cc3b1f8a2@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch 2nd-opinion    |  javascript
-------------------------------------+-------------------------------------
Changes (by joedolson):

 * Attachment "35483.3.diff" added.

 Patch refreshed; escaping of theTitle removed

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35483>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 19:55:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 19:55:50 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.a0f605246c102489907bdc1b7d88b228@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53025" 53025]:
 {{{
 #!CommitTicketReference repository="" revision="53025"
 Customizer: Accessibility fixes following [53024].

 This changeset fixes a few issues spotted after [53024].

 - Remove target blank on HelpHub link
 - Remove duplicate information in `aria-label`
 - Small i18n fixes

 Follow-up to [53024].

 Props joedolson, audrasjb, pbiron.
 Fixes #54939.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:46>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 20:04:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 20:04:28 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.35ef8f4164d22e104933b1d5beb2d5e4@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 Reopening for proper backport.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:48>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 20:04:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 20:04:37 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.416030ef7998a64214c591f861803ea7@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  closed => reopened
 * resolution:  fixed =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 20:16:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 20:16:53 -0000
Subject: [wp-trac] [WordPress Trac] #54939: When a block theme is active,
 add Site Editor link and notice to the Customizer UI
In-Reply-To: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
References: <058.38ec45b3a73253386e84de8f26bbf933@wordpress.org>
Message-ID: <073.543b8f03dd84e96f451eb61707e037ee@wordpress.org>

#54939: When a block theme is active, add Site Editor link and notice to the
Customizer UI
-------------------------------------------------+-------------------------
 Reporter:  ironprogrammer                       |       Owner:  marybaum
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  5.9.3
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-screenshots has-patch i18n-      |     Focuses:  ui, ui-
  change commit fixed-major                      |  copy
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53026" 53026]:
 {{{
 #!CommitTicketReference repository="" revision="53026"
 Customizer: When a block theme is active, add an information about Site
 Editor in the Customizer.

 This change adds an information notice to the customizer when a block
 theme is active and the customizer is also available (for example when a
 plugin activates it), to encourage people to use the Site Editor for the
 best full site customization experience.

 Props ironprogrammer, antonvlasenko, Clorith, audrasjb, psmits1567,
 tobifjellner, costdev, webcommsat, joedolson, pbiron.
 Merges [53024] and [53025] to the 5.9 branch.
 Fixes #54939.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54939#comment:50>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 20:47:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 20:47:40 -0000
Subject: [wp-trac] [WordPress Trac] #54728: Coding Standards fixes for
 WP 6.0
In-Reply-To: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
References: <058.7a155b0f785c70523f1d802c18e37284@wordpress.org>
Message-ID: <073.466778525f687b450ec3335ff5adf701@wordpress.org>

#54728: Coding Standards fixes for WP 6.0
----------------------------+-------------------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  coding-standards
----------------------------+-------------------------------

Comment (by jrf):

 Replying to [comment:51 knutsp]:
 > {{{#!php
 > <?php
 > 1 === $_GET['test']
 > }}}
 > will never evaluate to true, as `$_REQUEST` values are all strings. Keep
 the loose comparison.
 >

 Or do a strict comparison, but compare against the right type, i.e. `'1'
 === $_GET['test']` ;-)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54728#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 21:09:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 21:09:56 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.231ba4c86a79856169b8d22731c9d8ba@wordpress.org>

#41136: Login forms lacking autocomplete attributes
------------------------------+--------------------------------------------
 Reporter:  johnjamesjacoby   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  6.0
Component:  Login and         |     Version:
  Registration                |
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  accessibility, administration
------------------------------+--------------------------------------------
Changes (by joedolson):

 * Attachment "41136.2.diff" added.

 Sets autocomplete values for login/register

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 21:15:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 21:15:35 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.f01caf1f4e8a5ea52e92af120e8d1aed@wordpress.org>

#41136: Login forms lacking autocomplete attributes
-------------------------------------+-------------------------------------
 Reporter:  johnjamesjacoby          |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Login and Registration   |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch needs-       |     Focuses:  accessibility,
  testing                            |  administration
-------------------------------------+-------------------------------------
Changes (by joedolson):

 * keywords:  needs-patch => needs-patch needs-testing


Comment:

 New patch sets autocomplete values on:

 - on login username
 - on login password
 - on register username
 - on register email
 - added autocomplete=off to show_blog_form() blog title and blog name
 fields.

 In the login username field in wp-login.php, I used
 `autocomplete='username'`, though the form accepts either username or
 email. Perhaps this should be filterable? To the best of my knowledge,
 `autocomplete="username"` is the appropriate value for a username field
 that accepts an email address.

 I also omitted autocomplete on the 'lost password' form, which also
 accepts either username or email. For the lost password, I'm less certain
 what would be ideal.

 Testing:
 - verify that autocomplete values are present and match data type in any
 log-in or register form.
 - verify whether using autocomplete="username" will produce an email
 address if the user has used their email address as a log-in value.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 21:29:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 21:29:05 -0000
Subject: [wp-trac] [WordPress Trac] #55344: Resources for hidden widgets
 are loaded on WP dashboard
In-Reply-To: <053.4ed27fa406a39cbf13813ae1048c8a9f@wordpress.org>
References: <053.4ed27fa406a39cbf13813ae1048c8a9f@wordpress.org>
Message-ID: <068.4a6b0eb680eb3f7a1af48e7a63537148@wordpress.org>

#55344: Resources for hidden widgets are loaded on WP dashboard
----------------------------+------------------------------
 Reporter:  josklever       |       Owner:  adamsilverstein
     Type:  defect (bug)    |      Status:  accepted
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  5.9.1
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  performance
----------------------------+------------------------------
Changes (by adamsilverstein):

 * keywords:   => needs-patch
 * owner:  (none) => adamsilverstein
 * status:  new => accepted


Comment:

 Hey @josklever - thanks for reporting this issue. I can confirm that the
 screen options controls don't do anything to alter loading of associated
 scripts. Guessing this has been a bug for a long time, since the Dashboard
 was introduced.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55344#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 21:36:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 21:36:12 -0000
Subject: [wp-trac] [WordPress Trac] #55344: Resources for hidden widgets
 are loaded on WP dashboard
In-Reply-To: <053.4ed27fa406a39cbf13813ae1048c8a9f@wordpress.org>
References: <053.4ed27fa406a39cbf13813ae1048c8a9f@wordpress.org>
Message-ID: <068.71f9d6ace108e01d5f33e37cb7431b01@wordpress.org>

#55344: Resources for hidden widgets are loaded on WP dashboard
----------------------------+------------------------------
 Reporter:  josklever       |       Owner:  adamsilverstein
     Type:  defect (bug)    |      Status:  accepted
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  5.9.1
 Severity:  normal          |  Resolution:
 Keywords:  needs-patch     |     Focuses:  performance
----------------------------+------------------------------

Comment (by josklever):

 In addition there's also a closed state of a dashboard widget. In that
 case the content doesn't need to be rendered until it's opened. And opened
 widgets that are below the fold, might even be loaded only after scrolling
 with lazy loading.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55344#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 21:46:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 21:46:27 -0000
Subject: [wp-trac] [WordPress Trac] #37750: Cropping custom logo should
 preserve attachment properties
In-Reply-To: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
References: <052.cccf42bca4850ff8240dc5b5fae48adb@wordpress.org>
Message-ID: <067.090476db9a74209c078f311a298778bc@wordpress.org>

#37750: Cropping custom logo should preserve attachment properties
-------------------------------------------------+-------------------------
 Reporter:  flixos90                             |       Owner:  joedolson
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  4.5
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests has-        |     Focuses:
  screenshots has-testing-info commit            |  accessibility
-------------------------------------------------+-------------------------
Changes (by joedolson):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53027" 53027]:
 {{{
 #!CommitTicketReference repository="" revision="53027"
 Media: Preserve attachment properties on cropping custom logo.

 Migrate the alternative text, title, description, and caption of an image
 over to the cropped copy of the image after cropping. Ensure that
 characteristics added to an image prior to cropping are not lost.

 Props flixos90, Clorith, afercia, antonvlasenko, ironprogrammer,
 hellofromTonya.
 Fixes #37750.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37750#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 22:56:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 22:56:23 -0000
Subject: [wp-trac] [WordPress Trac] #51857: Add rollback for failed
 plugin/theme updates
In-Reply-To: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
References: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
Message-ID: <065.a3d08146d1d38f28ed843f38ce07bef8@wordpress.org>

#51857: Add rollback for failed plugin/theme updates
-------------------------------------------------+-------------------------
 Reporter:  pbiron                               |       Owner:  pbiron
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  early has-testing-info needs-unit-   |     Focuses:
  tests needs-testing has-patch dev-feedback     |
  needs-dev-note                                 |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * milestone:  6.0 => Future Release


Comment:

 I'm bumping this from the 6.0 milestone as I don't think the PR close
 enough to ready for a ticket marked `early`.

 There are a few architectural discussions taking place on the pull
 request. These ought to be moved here and discussed without the presence
 of code.

 Once these have been decided, the `needs-unit-tests` keyword will need to
 be addressed: there are a few plugins in the tests/phpunit/data directory
 but you may need to add an "upgrade".

 If unit tests prove difficult, you may be able to use them in combination
 with end-to-end tests.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51857#comment:206>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 23:06:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 23:06:45 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.808ff6e25d8fb40ce455b0fdc97a2f58@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note needs-docs needs-codex  |  performance
-------------------------------------------------+-------------------------

Comment (by pbiron):

 In a comment on the [https://make.wordpress.org/core/2022/03/28/enabling-
 webp-by-default/#comment-42739 Enabling WebP by default] make/core post I
 asked "if a site already has a bunch of JPEGs in the media library, will
 regenerating the thumbnails (intermediate sizes) via either `wp media
 regenerate` or a plugin like [https://wordpress.org/plugins/regenerate-
 thumbnails/ Regenerate Thumbnails] automatically produce the WebP
 versions?"

 Just reporting here that I have now tested this with WP 5.9.2,
 [https://wordpress.org/plugins/performance-lab/ Performance Lab]
 1.0.0-beta.3, WP-CLI 2.6.0, and `Regenerate Thumbnails` 3.1.5 and it all
 works as I expected it to.

 Nice work!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 23:11:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 23:11:27 -0000
Subject: [wp-trac] [WordPress Trac] #55481: Add custom headers for
 `update_plugins_{$hostname}` filter's package
Message-ID: <054.06c012211d38a08258471603b2363253@wordpress.org>

#55481: Add custom headers for `update_plugins_{$hostname}` filter's package
-----------------------------+-----------------------------
 Reporter:  natsumesou       |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Plugins          |    Version:  trunk
 Severity:  normal           |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 This `update_plugins_{$hostname}` filter may aim to update private
 plugins, but this feature has no authentication logic.
 When I add to GitHub's release zipball URL to this filter, I can update
 only public repository's zipball.
 So I think this filter need custom headers to package's URL(e.g.
 Authorization header).

 Thank you.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55481>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 23:53:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 23:53:41 -0000
Subject: [wp-trac] [WordPress Trac] #55481: Add custom headers for
 `update_plugins_{$hostname}` filter's package
In-Reply-To: <054.06c012211d38a08258471603b2363253@wordpress.org>
References: <054.06c012211d38a08258471603b2363253@wordpress.org>
Message-ID: <069.84447724be05d29e6d27f526776ebf93@wordpress.org>

#55481: Add custom headers for `update_plugins_{$hostname}` filter's package
-------------------------------+------------------------------
 Reporter:  natsumesou         |       Owner:  (none)
     Type:  feature request    |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Upgrade/Install    |     Version:  trunk
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by pbiron):

 * keywords:   => reporter-feedback
 * component:  Plugins => Upgrade/Install


Comment:

 @natsumesou Thank you for the ticket...and welcome to Trac.

 If I understand what you problem is, you can use the
 [https://developer.wordpress.org/reference/hooks/http_request_args/
 http_request_args] filter to add the `Authentication` header.

 You should be able to do something like (note: the following code has
 **not** been tested):

 {{{#!php
 add_filter(
   'http_request_args',
   function( $parsed_args, $url ) {
     if ( MY_UPDATE_URL === $url ) {
       if ( empty( $parsed_args['headers'] ) ) {
         $parsed_args['headers'] = array();
       }

       $parsed_args['headers']['AUTHORIZATION'] = MY_AUTH_HEADER_VALUE;
     }

     return $parsed_args;
   },
   10,
   2
 );
 }}}

 where `MY_UPDATE_URL` and `MY_UPDATE_URL` are just placeholders (and not
 to be interpreted as PHP constants) and should be replaced by whatever
 your use case requires.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55481#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 23:54:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 23:54:31 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.1835adc19528e57d95994bf5f593f696@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
-------------------------------------------------+-------------------------
 Reporter:  isaumya                              |       Owner:
                                                 |  adamsilverstein
     Type:  feature request                      |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  refresh                                        |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * Attachment "53232.5.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Tue Mar 29 23:56:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Tue, 29 Mar 2022 23:56:37 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.d07e71bcdaa2dd0d7edbb4c8d4517728@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
---------------------------------------------+-----------------------
 Reporter:  pbearne                          |       Owner:  flixos90
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------
Changes (by flixos90):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53028" 53028]:
 {{{
 #!CommitTicketReference repository="" revision="53028"
 Media: Introduce `wp_content_img_tag` filter.

 This filter allows modifying individual `img` tags within a blob of
 content that are by default processed by the `wp_filter_content_tags()`
 function. The addition of this filter facilitates plugins that tweak
 images to accomplish this goal without re-implementing duplicate content
 image parser logic, which furthermore can have a negative performance
 impact due to additional regular expressions.

 In addition to the filterable `img` tag, the filter receives the context
 (typically the function or filter in which the content is parsed) and the
 attachment ID. The latter may be 0, in case the image is not an attachment
 (for example when it is an external image URL).

 Props adamsilverstein, flixos90, pbearne, peterwilsoncc.
 Fixes #55347.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:11:38 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:11:38 -0000
Subject: [wp-trac] [WordPress Trac] #55481: Add custom headers for
 `update_plugins_{$hostname}` filter's package
In-Reply-To: <054.06c012211d38a08258471603b2363253@wordpress.org>
References: <054.06c012211d38a08258471603b2363253@wordpress.org>
Message-ID: <069.fe519471532730b8674987987e70ac70@wordpress.org>

#55481: Add custom headers for `update_plugins_{$hostname}` filter's package
-------------------------------+------------------------------
 Reporter:  natsumesou         |       Owner:  (none)
     Type:  feature request    |      Status:  closed
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Upgrade/Install    |     Version:  trunk
 Severity:  normal             |  Resolution:  invalid
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------
Changes (by natsumesou):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 @pbiron Thank you for your advice.
 I was able to update my private repo's zipball by your sample.
 I'm sorry for bothering you.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55481#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:13:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:13:08 -0000
Subject: [wp-trac] [WordPress Trac] #55481: Add custom headers for
 `update_plugins_{$hostname}` filter's package
In-Reply-To: <054.06c012211d38a08258471603b2363253@wordpress.org>
References: <054.06c012211d38a08258471603b2363253@wordpress.org>
Message-ID: <069.4bfe158d47022db25054d7ff2072c8a2@wordpress.org>

#55481: Add custom headers for `update_plugins_{$hostname}` filter's package
-------------------------------+------------------------------
 Reporter:  natsumesou         |       Owner:  (none)
     Type:  feature request    |      Status:  closed
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Upgrade/Install    |     Version:  trunk
 Severity:  normal             |  Resolution:  invalid
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by pbiron):

 No bother at all.  Glad you got your problem solved!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55481#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:15:04 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:15:04 -0000
Subject: [wp-trac] [WordPress Trac] #55482: Remove my name from contributors
 list
Message-ID: <053.2b6114be6792b3044e921d0159c4c44a@wordpress.org>

#55482: Remove my name from contributors list
--------------------------+-----------------------------
 Reporter:  techboyg5     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hi there, I would like to remove my name from the Credits page in
 WordPress. Thank you!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55482>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:15:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:15:28 -0000
Subject: [wp-trac] [WordPress Trac] #55483: Remove my name from contributors
 list
Message-ID: <053.1d234820d878641ac9781c7a988b6deb@wordpress.org>

#55483: Remove my name from contributors list
--------------------------+-----------------------------
 Reporter:  techboyg5     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hi there, I would like to remove my name from the Credits page in
 WordPress. Thank you!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55483>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:16:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:16:05 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.a66701a630fc55262d6617387a1d19d6@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
-------------------------------------------------+-------------------------
 Reporter:  isaumya                              |       Owner:
                                                 |  adamsilverstein
     Type:  feature request                      |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  refresh                                        |  performance
-------------------------------------------------+-------------------------

Comment (by peterwilsoncc):

 [attachment:"53232.5.diff"] is [attachment:"53232.4.diff"] with a few
 minor modifications:

 * fixes the alignment of a few docblock `@param` tags
 * expands the description of `wp_img_tag_add_decoding_async_attr()`
   - generically indicates it adds the `decoding` attribute rather than the
 value
   - expands the explanation to indicate what the attribute does, accepted
 values and how developers can modify it.

 I've also noticed that how this works is quite different to adding the
 default `lazy` tag, `lazy` includes:

 * `wp_lazy_loading_enabled()
 * `wp_get_loading_attr_default()`
 * `wp_omit_loading_attr_threshold()`

 This results in some differences in how the `decoding` attribute is added
 by default to images, particularly avatars. As these features are very
 similar in intent, it seems logical to use a similar APIs.

 I realise there was some discussion above as to whether developers
 ''ought'' to disable it but we need to account for environments in which
 they need to. For example headless environments converting WP images tags
 to their smarter defaults.

 In `wp_get_attachment_image()` the attribute ought to be added as a
 default argument to allow developers to override the value by passing an
 argument. The new argument should be added to the docblock too.

 Sorry I didn't post all this yesterday, but the `error_log()`s in the
 previous patch were early in the source and an immediate blocker.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:55>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:20:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:20:07 -0000
Subject: [wp-trac] [WordPress Trac] #53997: Add some unit tests for the
 WP_Upgrader class
In-Reply-To: <058.bec97243adb774205d0f064e3cab1339@wordpress.org>
References: <058.bec97243adb774205d0f064e3cab1339@wordpress.org>
Message-ID: <073.4b204d18d383409442c17a992813a7a8@wordpress.org>

#53997: Add some unit tests for the WP_Upgrader class
--------------------------------------+---------------------
 Reporter:  SergeyBiryukov            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Upgrade/Install           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by costdev):

 [https://github.com/WordPress/wordpress-develop/pull/1751 PR 1751] on
 #54245 uses `getMockBuilder()`.

 [https://github.com/WordPress/wordpress-develop/pull/2463 PR 2463] above
 uses `WP_Upgrader` directly and aims to achieve 100% (or as near as
 possible) line/branch coverage for `WP_Upgrader`.

 #54245 notes that there is accidental coverage of `WP_Upgrader` elsewhere
 in the test suite, though a single test class that covers each line/branch
 and in doing so, demonstrates how to hit each line/branch for future path
 coverage improvements, would be ideal IMO.

 It would be good to get some input on the preferred approach for Core.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53997#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:20:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:20:45 -0000
Subject: [wp-trac] [WordPress Trac] #55483: Remove my name from
 contributors list
In-Reply-To: <053.1d234820d878641ac9781c7a988b6deb@wordpress.org>
References: <053.1d234820d878641ac9781c7a988b6deb@wordpress.org>
Message-ID: <068.5a66aa3d45865095949974fd072916fc@wordpress.org>

#55483: Remove my name from contributors list
--------------------------+------------------------
 Reporter:  techboyg5     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by costdev):

 * status:  new => closed
 * resolution:   => duplicate
 * milestone:  Awaiting Review =>


Comment:

 Duplicate of #55482.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55483#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:46:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:46:36 -0000
Subject: [wp-trac] [WordPress Trac] #55484: class-wp-editor.php line 1697
Message-ID: <050.6482079791df9a6ae016d9a05467fef2@wordpress.org>

#55484: class-wp-editor.php line 1697
--------------------------+-----------------------------
 Reporter:  karin2        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Editor        |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:  javascript    |
--------------------------+-----------------------------
 Line 1697 of class-wp-editor.php should end with a semicolon.

 Otherwise, if the page is compressed errors are in the console and the
 editor isn't functioning correctly.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55484>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:49:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:49:11 -0000
Subject: [wp-trac] [WordPress Trac] #55485: Clarify
 `wp_should_load_separate_core_block_assets()`,
 `block.json` script expectations
Message-ID: <054.7e9fba539d9dcb6981be818cbdd6148a@wordpress.org>

#55485: Clarify `wp_should_load_separate_core_block_assets()`, `block.json` script
expectations
---------------------------+-----------------------------
 Reporter:  jeremyfelt     |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Script Loader  |    Version:
 Severity:  normal         |   Keywords:
  Focuses:  docs           |
---------------------------+-----------------------------
 In the `block.json`
 [https://github.com/WordPress/gutenberg/blob/45a8e6be0eb7fca87d64ce8140792b30e6bc4a20/schemas/json/block.json
 schema], the `script` property is described as:

 > "Block type frontend and editor script definition. It will be enqueued
 both in the editor and when viewing the content on the front of the site."

 From that description, I expect the `script` set in my block's
 `block.json` to load in the editor and on the front-end when my block is
 in use. I do not expect the script to load on the front-end when my block
 is not in use.

 If I activate TwentyTwentyTwo, everything works as expected.

 If I activate TwentyTwentyOne, my script appears on every front-end view,
 whether or not the block is loaded.

 The cause of this can be tracked to
 `wp_should_load_separate_core_block_assets()`, which has a short
 description of:

 > Checks whether separate styles should be loaded for core blocks on-
 render

 This implies at the beginning of the function documentation that the
 function will only apply to **core** blocks.

 The longer description helps a bit, but is muddied up in talking about
 core and third-party blocks separately when in reality it seems that they
 are treated the same. It mentions `block-library/style.css`, which itself
 implies this _might_ be talking about styles rather than all assets.

 The filter inside the function, `should_load_separate_core_block_assets`,
 defaults to `false` for themes that are not FSE and has a short
 description of:

 > Filters whether block styles should be loaded separately.

 The longer description refers only to "core block assets".

 -----
 == Proposal

 My guess is that we can't just change the filter to default to `true`,
 though that would be ideal. :)

 I think the function docs could be clarified with something like:

 {{{
 /**
  * Checks whether block assets should always load or only on-render.
  *
  * When this function returns true, block assets defined by the `script`
 and
  * `style` properties in `block.json` are loaded on-render.
  *
  * When this function returns false, these block assets are always loaded,
  * regardless of whether the block is rendered in a page.
  *
  * This only affects front end and not the block editor screens.
 }}}

 And the filter docs with something like:

 {{{
  * Filters whether block assets should always load or load only on-render.
  *
  * Returning false loads all block assets, regardless of whether they are
 rendered
  * in a page or not. Returning true loads block assets only when they are
 rendered.
 }}}

 Previously #53505

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55485>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 00:58:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 00:58:08 -0000
Subject: [wp-trac] [WordPress Trac] #55425: Customize: Fetch presence of
 published pages more optimally (refactor)
In-Reply-To: <050.79f4190ca6567d9d247a2239b48b872b@wordpress.org>
References: <050.79f4190ca6567d9d247a2239b48b872b@wordpress.org>
Message-ID: <065.ed59c3cbb6477483298664886160c33f@wordpress.org>

#55425: Customize: Fetch presence of published pages more optimally (refactor)
-------------------------+-----------------------------
 Reporter:  nagpai       |       Owner:  nagpai
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  Future Release
Component:  Customize    |     Version:  4.7
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+-----------------------------
Changes (by dlh):

 * version:  5.9.2 => 4.7
 * milestone:  Awaiting Review => Future Release


Comment:

 Welcome back to Trac, @nagpai! Thanks for the report.

 The current logic was added for #38013, where `'number' => 1` was
 mentioned specifically in the description but not the final patch, so it
 seems like it was an oversight.

 Care to submit a patch or a Pull Request? Once we have a patch, I think
 this ticket can be added to the 6.0 milestone.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55425#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 01:02:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 01:02:26 -0000
Subject: [wp-trac] [WordPress Trac] #55486:
 register_block_type_from_metadata does NOT work within a theme but as a
 plugin
Message-ID: <053.e46d8344c58d919e208bab8d0e0ea619@wordpress.org>

#55486: register_block_type_from_metadata does NOT work within a theme but as a
plugin
------------------------------+-----------------------------
 Reporter:  andre3600         |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  General           |    Version:  5.9.2
 Severity:  minor             |   Keywords:  needs-refresh
  Focuses:  coding-standards  |
------------------------------+-----------------------------
 I created a wordpress block and it guides me to the official documentation
 and it came to work as an external plugin, taking into account the
 architecture of block.json for its use, however it has not worked for me
 when the block is required to be integrated into a theme, delivery wrong
 path request looking in plugin folder plus adding another path.

 example error peticion

 https://domain.local/wp-content/plugins/D:/xampp/htdocs/wp-
 content/themes/NewsPaper/inc/gutenberg/myblock/index.js?ver=d395fe5d9d90bd6565685c91d8d38888

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55486>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 03:14:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 03:14:01 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.30acfe1989fef2662c33bd34325d7fcb@wordpress.org>

#41136: Login forms lacking autocomplete attributes
-------------------------------------+-------------------------------------
 Reporter:  johnjamesjacoby          |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Login and Registration   |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch needs-       |     Focuses:  accessibility,
  testing                            |  administration
-------------------------------------+-------------------------------------

Comment (by peterwilsoncc):

 > I also omitted autocomplete on the 'lost password' form, which also
 accepts either username or email. For the lost password, I'm less certain
 what would be ideal.

 My instinct is `username` but if you could ask for advice is accessibility
 circles that would be lovely.

 I did some quick testing and it seems to be working as expected.

 #43886 is related but for fields that need the new-password autocomplete
 value.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 03:31:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 03:31:24 -0000
Subject: [wp-trac] [WordPress Trac] #19901: Speeding up Dashboard and
 Comment moderation SQL load
In-Reply-To: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
References: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
Message-ID: <070.e6c8d3660f8d34bdb26c537c28a8a18a@wordpress.org>

#19901: Speeding up Dashboard and Comment moderation SQL load
--------------------------------------------+---------------------------
 Reporter:  FolioVision                     |       Owner:  spacedmonkey
     Type:  enhancement                     |      Status:  assigned
 Priority:  normal                          |   Milestone:  6.0
Component:  Comments                        |     Version:  3.3
 Severity:  major                           |  Resolution:
 Keywords:  needs-testing has-patch commit  |     Focuses:  performance
--------------------------------------------+---------------------------
Changes (by peterwilsoncc):

 * owner:  markjaquith => spacedmonkey
 * status:  accepted => assigned


Comment:

 Reassigning this to you, Jonny, as it seems your most likely to commit
 when the time comes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19901#comment:33>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 05:55:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 05:55:13 -0000
Subject: [wp-trac] [WordPress Trac] #55448: WP_Widget_Block outputs
 empty container if widget has no output
In-Reply-To: <058.aa6e76f89b6bf6a1bd18b3d2b12c863b@wordpress.org>
References: <058.aa6e76f89b6bf6a1bd18b3d2b12c863b@wordpress.org>
Message-ID: <073.1a940b8ea66cd28b96aaad5960ce12a9@wordpress.org>

#55448: WP_Widget_Block outputs empty container if widget has no output
-------------------------------------+---------------------
 Reporter:  stiofansisland           |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Widgets                  |     Version:  5.9.2
 Severity:  major                    |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  ui
-------------------------------------+---------------------
Changes (by mehedi890):

 * keywords:  has-patch => has-patch needs-testing


Comment:

 Hi there!

 I've tested this patch and its works for me
 Still, I'm adding the {{{needs-testing}}} label to bring a few extra eyes
 to this ticket to see if it solves the issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55448#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 06:35:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 06:35:17 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.438ca514513dc158505df787349ad5b6@wordpress.org>

#41136: Login forms lacking autocomplete attributes
-------------------------------------+-------------------------------------
 Reporter:  johnjamesjacoby          |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Login and Registration   |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch needs-       |     Focuses:  accessibility,
  testing                            |  administration
-------------------------------------+-------------------------------------

Comment (by rianrietveld):

 Thanks so much for going ahead with this.

 Especially because the rules in the new WCAG 2.2, that is still in draft,
 will probably be even be more stricter [3.3.6. Accessible
 authentication](https://www.w3.org/WAI/standards-guidelines/wcag/new-
 in-22/#337-accessible-authentication-a]. (Don't shoot the messenger)

 The values for autocomplete can be found on
 [MDN web docs The HTML autocomplete attribute]
 (https://developer.mozilla.org/en-
 US/docs/Web/HTML/Attributes/autocomplete)

 To comply to WCAG 2.1 AA for the login form we need:
 username on "Username or Email Address"
 current-password on "Password"

 And possibly if we want to take this further on more login/create account
 forms:

 For retrieving a forgotten password:
 username on "Username or Email Address"

 For creating a new password (so the browser doen't fill out the existing
 password)
 new-password

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 06:56:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 06:56:05 -0000
Subject: [wp-trac] [WordPress Trac] #55487: I am not able to add favicon /
 site icon with latest Full Site Editing
Message-ID: <057.7514de5cf9d7ee41e097cbd0c97faacf@wordpress.org>

#55487: I am not able to add favicon / site icon with latest Full Site Editing
-----------------------------+------------------------------------
 Reporter:  Suresh Shinde    |      Owner:  (none)
     Type:  feature request  |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  General          |    Version:  5.9.2
 Severity:  normal           |   Keywords:  needs-docs needs-patch
  Focuses:                   |
-----------------------------+------------------------------------
 I am using latest WordPress and latest Twenty Twenty-Two.

 As before, I was use to set from customizer settings.

 I am searching for setting/option for favicon.

 Please help.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55487>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 08:10:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 08:10:01 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.667c12150a9c3fbc8ce87240e4e3718f@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note needs-docs needs-codex  |  performance
-------------------------------------------------+-------------------------

Comment (by markhowellsmead):

 When converting medium-resolution photographs (approx 1600px – 2500px on
 the long edge), WebP files are often larger than the JPEG equivalent. (In
 my tests using my own photography, in around 60% of cases.) This change
 might make the “modern image format” test of Page Speed Insights happy,
 but enforcing WebP by default on sites which use a lot of photography will
 often cause longer image loading times.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 08:55:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 08:55:21 -0000
Subject: [wp-trac] [WordPress Trac] #53465: PHP 8.1.: the default value
 of the flags parameter for htmlentities() et all needs to be explicitly set
In-Reply-To: <047.e1df10f349b504efb4b82629cb43ab1e@wordpress.org>
References: <047.e1df10f349b504efb4b82629cb43ab1e@wordpress.org>
Message-ID: <062.2303de798486b5650d87b01746ca4523@wordpress.org>

#53465: PHP 8.1.: the default value of the flags parameter for htmlentities() et
all needs to be explicitly set
-------------------------------+-------------------------------
 Reporter:  jrf                |       Owner:  (none)
     Type:  task (blessed)     |      Status:  new
 Priority:  normal             |   Milestone:  6.0
Component:  General            |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  needs-patch php81  |     Focuses:  coding-standards
-------------------------------+-------------------------------

Comment (by GaryJ):

 According to https://www.php.net/manual/en/function.htmlentities.php, the
 default for flags for PHP 8.1 was "changed from `ENT_COMPAT` to
 `ENT_QUOTES | ENT_SUBSTITUTE | ENT_HTML401`".

 I don't know what difference that `ENT_HTML401` might make (there's also a
 `ENT_HTML5` flag available as well), but might be something else to
 consider.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53465#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 09:39:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 09:39:13 -0000
Subject: [wp-trac] [WordPress Trac] #55482: Remove my name from
 contributors list
In-Reply-To: <053.2b6114be6792b3044e921d0159c4c44a@wordpress.org>
References: <053.2b6114be6792b3044e921d0159c4c44a@wordpress.org>
Message-ID: <068.595eb0d3e677f2356a64ace18d29829b@wordpress.org>

#55482: Remove my name from contributors list
--------------------------+--------------------------------
 Reporter:  techboyg5     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  reported-upstream
 Keywords:                |     Focuses:
--------------------------+--------------------------------
Changes (by johnbillion):

 * status:  new => closed
 * resolution:   => reported-upstream
 * milestone:  Awaiting Review =>


Comment:

 I've moved this to https://meta.trac.wordpress.org/ticket/6227.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55482#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 10:43:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 10:43:23 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to
 allow for named parameters in WP 6.0
In-Reply-To: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
References: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
Message-ID: <072.0ce77344a53d98cab8ff5f1e6604feae@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
-----------------------------+---------------------
 Reporter:  peterwilsoncc    |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  php80 has-patch  |     Focuses:
-----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"53029" 53029]:
 {{{
 #!CommitTicketReference repository="" revision="53029"
 Code Modernization: Rename parameters that use reserved keywords in `wp-
 admin/includes/class-wp-importer.php`.

 While using reserved PHP keywords as parameter name labels is allowed, in
 the context of function calls using named parameters in PHP 8.0+, this
 will easily lead to confusion. To avoid that, it is recommended not to use
 reserved keywords as function parameter names.

 This commit renames the `$string` parameter to `$text` in
 `WP_Importer::min_whitespace()`.

 Follow-up to [52946], [52996], [52997], [52998], [53003], [53014].

 Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
 See #55327.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55327#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 11:28:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 11:28:44 -0000
Subject: [wp-trac] [WordPress Trac] #55474: Backport bugfixes from
 Gutenberg into Core for WP 5.9.3
In-Reply-To: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
References: <052.121b881dfdc48ca17f21abca9661c006@wordpress.org>
Message-ID: <067.633514580e9c56482370dea9a6195b62@wordpress.org>

#55474: Backport bugfixes from Gutenberg into Core for WP 5.9.3
--------------------------------------+-----------------------
 Reporter:  audrasjb                  |       Owner:  mamaduka
     Type:  task (blessed)            |      Status:  closed
 Priority:  normal                    |   Milestone:  5.9.3
Component:  Editor                    |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------
Changes (by audrasjb):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53030" 53030]:
 {{{
 #!CommitTicketReference repository="" revision="53030"
 Update WordPress packages for 5.9.3.

 Updated packages:

 - @wordpress/block-directory at 3.0.29
 - @wordpress/block-library at 6.0.28
 - @wordpress/customize-widgets at 2.0.29
 - @wordpress/edit-post at 5.0.29
 - @wordpress/edit-site at 3.0.29
 - @wordpress/edit-widgets at 3.1.24

 Props mamaduka, jorgefilipecosta.
 Fixes #55474.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55474#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 11:44:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 11:44:12 -0000
Subject: [wp-trac] [WordPress Trac] #53465: PHP 8.1.: the default value
 of the flags parameter for htmlentities() et all needs to be explicitly set
In-Reply-To: <047.e1df10f349b504efb4b82629cb43ab1e@wordpress.org>
References: <047.e1df10f349b504efb4b82629cb43ab1e@wordpress.org>
Message-ID: <062.0ff567108c40dce006ca5800396b1056@wordpress.org>

#53465: PHP 8.1.: the default value of the flags parameter for htmlentities() et
all needs to be explicitly set
-------------------------------+-------------------------------
 Reporter:  jrf                |       Owner:  (none)
     Type:  task (blessed)     |      Status:  new
 Priority:  normal             |   Milestone:  6.0
Component:  General            |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  needs-patch php81  |     Focuses:  coding-standards
-------------------------------+-------------------------------

Comment (by jrf):

 Replying to [comment:3 GaryJ]:
 > According to https://www.php.net/manual/en/function.htmlentities.php,
 the default for flags for PHP 8.1 was "changed from `ENT_COMPAT` to
 `ENT_QUOTES | ENT_SUBSTITUTE | ENT_HTML401`".
 >
 > I don't know what difference that `ENT_HTML401` might make (there's also
 a `ENT_HTML5` flag available as well), but might be something else to
 consider.


 The `ENT_HTML401` makes no difference as the value of that constant is
 `0`, so the "bit" value remains the same with or without.
 The `ENT_HTML401` part is not an actual change, just better documentation.

 See:
 * https://github.com/php/doc-en/pull/361#issuecomment-925931381
 * https://github.com/php/php-src/pull/7514

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53465#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 12:05:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 12:05:03 -0000
Subject: [wp-trac] [WordPress Trac] #55487: I am not able to add favicon
 / site icon with latest Full Site Editing
In-Reply-To: <057.7514de5cf9d7ee41e097cbd0c97faacf@wordpress.org>
References: <057.7514de5cf9d7ee41e097cbd0c97faacf@wordpress.org>
Message-ID: <072.29b8b15c8575fded4b54749a512e7a7c@wordpress.org>

#55487: I am not able to add favicon / site icon with latest Full Site Editing
------------------------------------+------------------------------
 Reporter:  Suresh Shinde           |       Owner:  (none)
     Type:  feature request         |      Status:  closed
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  General                 |     Version:  5.9.2
 Severity:  normal                  |  Resolution:  duplicate
 Keywords:  needs-docs needs-patch  |     Focuses:
------------------------------------+------------------------------
Changes (by Suresh Shinde):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Duplicate of #54370.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55487#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 13:04:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 13:04:22 -0000
Subject: [wp-trac] [WordPress Trac] #55435:
 use_block_editor_for_post_type filter is broken in 5.9.2
In-Reply-To: <051.55ce10038aea4a0f1daf84dfbb7d1aac@wordpress.org>
References: <051.55ce10038aea4a0f1daf84dfbb7d1aac@wordpress.org>
Message-ID: <066.3d018b2885fa2cb8464257d3a66a6642@wordpress.org>

#55435: use_block_editor_for_post_type filter is broken in 5.9.2
--------------------------+------------------------
 Reporter:  haykuro       |       Owner:  audrasjb
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by audrasjb):

 * milestone:  5.9.3 =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55435#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 13:06:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 13:06:48 -0000
Subject: [wp-trac] [WordPress Trac] #19901: Speeding up Dashboard and
 Comment moderation SQL load
In-Reply-To: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
References: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
Message-ID: <070.0bf1a44f7f11bca5bdd88c5bb7a2b97f@wordpress.org>

#19901: Speeding up Dashboard and Comment moderation SQL load
--------------------------------------------+---------------------------
 Reporter:  FolioVision                     |       Owner:  spacedmonkey
     Type:  enhancement                     |      Status:  assigned
 Priority:  normal                          |   Milestone:  6.0
Component:  Comments                        |     Version:  3.3
 Severity:  major                           |  Resolution:
 Keywords:  needs-testing has-patch commit  |     Focuses:  performance
--------------------------------------------+---------------------------

Comment (by spacedmonkey):

 @peterwilsoncc I am happy with the patch. I am going to commit if you are
 happy.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19901#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 13:12:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 13:12:42 -0000
Subject: [wp-trac] [WordPress Trac] #53951: Twenty Twenty: Search modal
 aria-expanded
In-Reply-To: <050.12159b56833732edace4c7af59831987@wordpress.org>
References: <050.12159b56833732edace4c7af59831987@wordpress.org>
Message-ID: <065.7717437e4392704bdef16ac10aacccb7@wordpress.org>

#53951: Twenty Twenty: Search modal aria-expanded
-------------------------------------+-------------------------------------
 Reporter:  utz119                   |       Owner:  alexstine
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-testing-   |     Focuses:  accessibility,
  instructions                       |  javascript
-------------------------------------+-------------------------------------
Changes (by afercia):

 * keywords:  has-patch has-testing-instructions needs-testing => has-patch
     has-testing-instructions


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53951#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 13:21:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 13:21:16 -0000
Subject: [wp-trac] [WordPress Trac] #37181: Use metadata api in
 *_network_options
In-Reply-To: <056.a9a12042e8bbc071a4a535ac583bce0b@wordpress.org>
References: <056.a9a12042e8bbc071a4a535ac583bce0b@wordpress.org>
Message-ID: <071.3f34a6d4115e167b5b6bf1e2c912bfb3@wordpress.org>

#37181: Use metadata api in *_network_options
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Networks and Sites                   |     Version:  4.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch ms-roadmap dev-feedback    |     Focuses:  multisite,
  has-unit-tests                                 |  performance
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 I spent some time on this ticket refreshing it so that is applies clearly
 to core. There is a new ready for review at [https://github.com/WordPress
 /wordpress-develop/pull/2478 #2478].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37181#comment:60>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 13:32:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 13:32:41 -0000
Subject: [wp-trac] [WordPress Trac] #21077: Add support for custom ports
 in multisite site addresses
In-Reply-To: <050.da44ba80528d7e12580241ce17e26436@wordpress.org>
References: <050.da44ba80528d7e12580241ce17e26436@wordpress.org>
Message-ID: <065.c07fb000c889a4968513c0b3a6d440a1@wordpress.org>

#21077: Add support for custom ports in multisite site addresses
----------------------------------------+-----------------------------
 Reporter:  djzone                      |       Owner:  (none)
     Type:  enhancement                 |      Status:  reopened
 Priority:  normal                      |   Milestone:  Future Release
Component:  Bootstrap/Load              |     Version:  3.4
 Severity:  normal                      |  Resolution:
 Keywords:  needs-unit-tests has-patch  |     Focuses:  multisite
----------------------------------------+-----------------------------

Comment (by spacedmonkey):

 I spent another couple of hours hacking on this problem, still finding
 issues. The issue, as I see, it where to store the custom port. If you
 store it as part of a domain, then that makes issues all over core, when
 domain is no longer domain but domain + port. I had to make lots of
 changes to get multisite to even bootstrap. The best place to store port
 number is in site ( blog ) meta. This keep the port number close to the
 site in meta but does not break anything.

 I prototyped how this might work in
 [https://gist.github.com/spacedmonkey/bf9f9cacb4d3aa8e99c1faaa4e51a447
 this] sunrise.php dropin.

 What made it hard to test, was the lack of this filter.

 {{{#!php
 $allowed_ports = apply_filters( 'allowed_multisite_ports', array( ':80',
 ':443' ) );
 }}}


 To help third parties be able to work out their own solution for this, I
 recommend a new ticket to add this filter. That way this functionality is
 not blocked while we work on another solution.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/21077#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 13:39:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 13:39:42 -0000
Subject: [wp-trac] [WordPress Trac] #55488: Add a filter to array of allow
 ported number in multisite.
Message-ID: <056.b9d8ec21eb951b68a995c2c21a95782c@wordpress.org>

#55488: Add a filter to array of allow ported number in multisite.
--------------------------------+-----------------------------
 Reporter:  spacedmonkey        |      Owner:  (none)
     Type:  enhancement         |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  Networks and Sites  |    Version:
 Severity:  normal              |   Keywords:  needs-patch
  Focuses:  multisite           |
--------------------------------+-----------------------------
 The allowed port numbers to setup a multisite are fixed. See this line.

 {{{#!php
         if ( ( false !== $has_ports && ! in_array( $has_ports, array(
 ':80', ':443' ), true ) ) ) {

 }}}

 However, a site maintainer may want to change these values to help enable
 serving their multisite from a custom port.

 This ticket is a breakout from #21077

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55488>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 13:40:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 13:40:29 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.7987af7781113f4541594b594069959f@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch 2nd-opinion    |  javascript
-------------------------------------+-------------------------------------

Comment (by afercia):

 @joedolson thanks for testing. On my side (macOS), the emoji is a Unicode
 character. See attached screenshot. If I recall correctly, it depends on
 the operating system / browser native support for emojis. It there's no
 support, an image is used instead of the Unicode character.

 Curious to know how the emoji is rendered within the post title `aria-
 label` attribute for you.

 Regardless, removing the escaping is fine by me, if there are no
 objections.

 There's one pending item:
 - Do we want to set initial focus on the ARIA live region also for the
 Quick Edit form?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35483#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 13:41:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 13:41:07 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.7adc8a44650351cb07d892efbbb6c66d@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch 2nd-opinion    |  javascript
-------------------------------------+-------------------------------------
Changes (by afercia):

 * Attachment "emoji.png" added.

 Emoji as Unicode character

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35483>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 14:24:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 14:24:43 -0000
Subject: [wp-trac] [WordPress Trac] #50523: Redesign the admin Image
 Editor
In-Reply-To: <051.74d9cdaaf425ce95ec1174a13630090b@wordpress.org>
References: <051.74d9cdaaf425ce95ec1174a13630090b@wordpress.org>
Message-ID: <066.e072bdf170990355ccd0ac8fb70c96c0@wordpress.org>

#50523: Redesign the admin Image Editor
--------------------------+--------------------------------
 Reporter:  afercia       |       Owner:  joedolson
     Type:  enhancement   |      Status:  accepted
 Priority:  normal        |   Milestone:  6.0
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-design  |     Focuses:  ui, accessibility
--------------------------+--------------------------------

Comment (by antpb):

 Just noting that this will likely not make it in 6.0 due to the amount of
 decisions still to be made in this effort. We're leaving in 6.0 until
 there is a 6.1 milestone to continue discussions on it through this
 release cycle.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50523#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 15:04:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 15:04:57 -0000
Subject: [wp-trac] [WordPress Trac] #55486:
 register_block_type_from_metadata does NOT work within a theme but as a
 plugin
In-Reply-To: <053.e46d8344c58d919e208bab8d0e0ea619@wordpress.org>
References: <053.e46d8344c58d919e208bab8d0e0ea619@wordpress.org>
Message-ID: <068.a931399c28be379d1622ab34263e422e@wordpress.org>

#55486: register_block_type_from_metadata does NOT work within a theme but as a
plugin
---------------------------+------------------------------
 Reporter:  andre3600      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  5.9.2
 Severity:  minor          |  Resolution:
 Keywords:  needs-refresh  |     Focuses:
---------------------------+------------------------------
Changes (by jrf):

 * focuses:  coding-standards =>


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55486#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 15:11:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 15:11:03 -0000
Subject: [wp-trac] [WordPress Trac] #55489: SHORTINIT define make error in
 the core
Message-ID: <051.9d661f0592b16f7f25a9c01d9665ef1c@wordpress.org>

#55489: SHORTINIT define make error in the core
----------------------------+-----------------------------
 Reporter:  gerendo         |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Bootstrap/Load  |    Version:  5.9.2
 Severity:  critical        |   Keywords:  has-screenshots
  Focuses:                  |
----------------------------+-----------------------------
 hi brothers and sisters
 I am a software developer .. in my current project i use WordPress as
 dashboard for web app using WordPress Rest-API .. for trying to minimize
 the response time of the API . I try to minimize the load of WordPress
 libraries by define this constant (SHORTINIT) in the wp-config.php .. I
 got that error [[https://prnt.sc/BCnjCnsmyv0k]]

 ''Error: Call to a member function main() on null in
 D:\wamp64\www\wordpress\wp-includes\functions.php on line 1310''

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55489>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 15:16:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 15:16:08 -0000
Subject: [wp-trac] [WordPress Trac] #50855: sanitize_file_name function
 not working as expected if there is '%20' in filename
In-Reply-To: <054.29c50c1e5cfc88b2b1054326da4b13cd@wordpress.org>
References: <054.29c50c1e5cfc88b2b1054326da4b13cd@wordpress.org>
Message-ID: <069.940712b192fe28ac3d08e908305aedbc@wordpress.org>

#50855: sanitize_file_name function not working as expected if there is '%20' in
filename
-------------------------------------------------+-------------------------
 Reporter:  dishitpala                           |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Formatting                           |     Version:  5.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-screenshots has-unit-  |     Focuses:
  tests dev-feedback                             |
-------------------------------------------------+-------------------------

Comment (by craigfrancis):

 I'm wondering if
 [https://core.trac.wordpress.org/attachment/ticket/50855/50855.2.diff
 50855.2.diff] is the correct approach, by simply moving the current
 `array( '%20', '+' )` up 1 line, so both ways of URL encoding a space are
 handled before `$special_chars`.

 As to the failing `wp_unique_filename()` test, that is:

 {{{
 wp_unique_filename( $testdir, '12%af34567890#~!@#$..%^&*()|_+qwerty
 fgh`jkl zx<>?:"{}[]="\'/?.png' )

 -'12af34567890 at ..^_qwerty-fghjkl-zx.png'
 +'12af34567890 at ..^_-qwerty-fghjkl-zx.png'
 }}}

 The extra `'-'` is coming from the `'+'` before `qwerty`, so maybe just
 update the expected test result?

 Tonya, I agree this could be a breaking change (e.g. while this usually
 has other issues as well, a developer could save files using
 `sanitize_file_name()` and store the original file names in their
 database)... but there has kinda been a breaking change already, where the
 feature that replaces `'%20'` and `'+'` so they became `'-'` was broken (I
 presume WordPress wanted to visually separate words in a file name, even
 when the name was URL encoded).

 An alternative would be to simply remove that line, and don't handle the
 URL encoding of spaces.

 ---

 Tangent stuff...

 Tonya, thanks for finding [https://core.trac.wordpress.org/changeset/35122
 Changeset 35122], the addition of `'%'` and `'+'` in `$special_chars` via
 [https://core.trac.wordpress.org/changeset/35122 Changeset 35122] did
 break this feature (oddly `test_replace_spaces()` explicitly tests `'multi
 %20 +space.png' => 'multi-20-space.png'`).

 For the [https://github.com/WordPress/wordpress-develop/pull/1873 patch
 from Tonya], the `'%20'` replacement happens before `$special_chars` on
 [https://github.com/WordPress/wordpress-
 develop/blob/7120c9cda9c9994e54d3432b967a85bc2c383025/src/wp-
 includes/formatting.php#L2020 line 2020]; but keeps the `'+'` replacement
 on [https://github.com/WordPress/wordpress-
 develop/blob/7120c9cda9c9994e54d3432b967a85bc2c383025/src/wp-
 includes/formatting.php#L2022 line 2022], I where don't think that will do
 anything (Peter has come to the same conclusion).

 I'm going to trust the `$special_chars` is complete (I'm not sure if there
 are other problematic characters)... but either way, they can be replaced
 by a hyphen or be removed. Both replacement methods are safe, and I'm
 pretty sure it's just personal taste on which one to use (e.g.
 "MyFile(1).jpg", should that be "MyFile1.jpg" or "MyFile-1.jpg"?). For now
 I'd prefer to stay with `'%20'` and `'+'`, with a separate discussion on
 what other characters could be replaced by a hyphen.

 To answer your questions, I think the `'+'` should be replaced with a
 `'-'`, because that seems to be the intended and original behaviour (why
 the `array( '%20', '+' )` was added in the first place). Secondly, I don't
 think leaving `'20'` was by design (a half encoded value), and I cannot
 think of any issue with replacing `'%20'` with a `'-'` in a function that
 intentionally removes bad characters from a file name.

 With PHP, the `urlencode()` function follows RFC 1738 and its use of URI
 defined in RFC 1630 (ref
 [https://datatracker.ietf.org/doc/html/rfc1630#page-7 page 7], which says
 "Within the query string, the plus sign is reserved as shorthand notation
 for a space."), this is why a space is often encoded a space to `'+'`
 ([https://github.com/php/php-
 src/blob/48e07076209c6163ecb4a756f73f511f1f09200e/ext/standard/url.c#L536
 source]), whereas `rawurlencode()` follows RFC 3986 and encodes a space to
 `'%20'` (i.e. it drops the special case). In both cases we are assuming
 the file name has been URL encoded.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50855#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 15:24:28 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 15:24:28 -0000
Subject: [wp-trac] [WordPress Trac] #55486:
 register_block_type_from_metadata does NOT work within a theme but as a
 plugin
In-Reply-To: <053.e46d8344c58d919e208bab8d0e0ea619@wordpress.org>
References: <053.e46d8344c58d919e208bab8d0e0ea619@wordpress.org>
Message-ID: <068.97d509108408af9a1d38ac45dfb47028@wordpress.org>

#55486: register_block_type_from_metadata does NOT work within a theme but as a
plugin
---------------------------+------------------------------
 Reporter:  andre3600      |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:  5.9.2
 Severity:  minor          |  Resolution:
 Keywords:  needs-refresh  |     Focuses:
---------------------------+------------------------------

Comment (by joyously):

 I think this is working as designed, with the design being that themes
 should not supply blocks since they can be switched at any time, even
 programmatically.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55486#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 16:21:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 16:21:01 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.8a66f6160be6050a4714481fecb8f73e@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch 2nd-opinion    |  javascript
-------------------------------------+-------------------------------------

Comment (by joedolson):

 @afercia Interesting. It's also rendered as an emoji within the aria-label
 for me, but is an `img` in the post title itself.


 Re: quick edit. I could go either way, but I think that having the initial
 focus land on the first editable field makes more sense when that field is
 the post title for a single post than when it's a removal button for one
 of a group of posts, as it would be in bulk edit. From a speed
 perspective, setting focus to the container just adds an extra tab stop
 and I don't see that you get any helpful extra information from that.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35483#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 16:21:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 16:21:29 -0000
Subject: [wp-trac] [WordPress Trac] #35483: Accessibility improvements
 for the Bulk Edit form
In-Reply-To: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
References: <051.87a7aaace03b7b3e0228eb25eaedecae@wordpress.org>
Message-ID: <066.e6661a22bc2a5fc7bde8c17ce49fd997@wordpress.org>

#35483: Accessibility improvements for the Bulk Edit form
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  afercia
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.0
Component:  Quick/Bulk Edit          |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots title-   |     Focuses:  ui, accessibility,
  attribute has-patch 2nd-opinion    |  javascript
-------------------------------------+-------------------------------------
Changes (by joedolson):

 * Attachment "35483-row-title.png" added.

 Emoji in row title & aria-label

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35483>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 16:39:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 16:39:29 -0000
Subject: [wp-trac] [WordPress Trac] #55489: SHORTINIT define make error
 in the core
In-Reply-To: <051.9d661f0592b16f7f25a9c01d9665ef1c@wordpress.org>
References: <051.9d661f0592b16f7f25a9c01d9665ef1c@wordpress.org>
Message-ID: <066.71d73cf2cde6eea9d714911e2d3f039e@wordpress.org>

#55489: SHORTINIT define make error in the core
-----------------------------+------------------------------
 Reporter:  gerendo          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Bootstrap/Load   |     Version:  5.9.2
 Severity:  critical         |  Resolution:
 Keywords:  has-screenshots  |     Focuses:  rest-api
-----------------------------+------------------------------
Changes (by sabernhardt):

 * focuses:   => rest-api


Old description:

> hi brothers and sisters
> I am a software developer .. in my current project i use WordPress as
> dashboard for web app using WordPress Rest-API .. for trying to minimize
> the response time of the API . I try to minimize the load of WordPress
> libraries by define this constant (SHORTINIT) in the wp-config.php .. I
> got that error [[https://prnt.sc/BCnjCnsmyv0k]]
>
> ''Error: Call to a member function main() on null in
> D:\wamp64\www\wordpress\wp-includes\functions.php on line 1310''

New description:

 hi brothers and sisters
 I am a software developer .. in my current project i use WordPress as
 dashboard for web app using WordPress Rest-API .. for trying to minimize
 the response time of the API . I try to minimize the load of WordPress
 libraries by define this constant (`SHORTINIT`) in the wp-config.php .. I
 got that error [[https://prnt.sc/BCnjCnsmyv0k]]

 `Error: Call to a member function main() on null in
 D:\wamp64\www\wordpress\wp-includes\functions.php on line 1310`

--

Comment:

 Hi and welcome to Trac! Thanks for the report!

 [https://core.trac.wordpress.org/browser/tags/5.9.2/src/wp-
 includes/functions.php#L1310 Line 1310] is in the `wp()` function.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55489#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 17:48:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 17:48:25 -0000
Subject: [wp-trac] [WordPress Trac] #55489: Defining SHORTINIT creates
 an error when index.php is loaded (was: SHORTINIT define make error in the
 core)
In-Reply-To: <051.9d661f0592b16f7f25a9c01d9665ef1c@wordpress.org>
References: <051.9d661f0592b16f7f25a9c01d9665ef1c@wordpress.org>
Message-ID: <066.85ef3d10a08fe19708d540057ffb5a45@wordpress.org>

#55489: Defining SHORTINIT creates an error when index.php is loaded
-----------------------------------+------------------------------
 Reporter:  gerendo                |       Owner:  (none)
     Type:  defect (bug)           |      Status:  new
 Priority:  normal                 |   Milestone:  Awaiting Review
Component:  Bootstrap/Load         |     Version:  5.9.2
 Severity:  normal                 |  Resolution:
 Keywords:  has-screenshots close  |     Focuses:  rest-api
-----------------------------------+------------------------------
Changes (by TimothyBlynJacobs):

 * keywords:  has-screenshots => has-screenshots close
 * severity:  critical => normal


Comment:

 `SHORTINIT` doesn't load the majority of WordPress, you can see where it
 [https://github.com/WordPress/wordpress-
 develop/blob/bcb3299a37712b61eb9b2a92c0b2fcc81e5d3d9d/src/wp-
 settings.php#L149 stops loading in `wp-settings.php`]. This includes the
 REST API.

 It looks like you are defining `SHORTINIT` for all requests to WordPress,
 which is not a supported configuration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55489#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 19:31:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 19:31:49 -0000
Subject: [wp-trac] [WordPress Trac] #55489: Defining SHORTINIT creates
 an error when index.php is loaded
In-Reply-To: <051.9d661f0592b16f7f25a9c01d9665ef1c@wordpress.org>
References: <051.9d661f0592b16f7f25a9c01d9665ef1c@wordpress.org>
Message-ID: <066.64240b4d56bade2c0c6095485f87472a@wordpress.org>

#55489: Defining SHORTINIT creates an error when index.php is loaded
-----------------------------------------------+---------------------------
 Reporter:  gerendo                            |       Owner:  (none)
     Type:  defect (bug)                       |      Status:  new
 Priority:  normal                             |   Milestone:  Awaiting
                                               |  Review
Component:  Bootstrap/Load                     |     Version:  5.9.2
 Severity:  normal                             |  Resolution:
 Keywords:  has-screenshots close 2nd-opinion  |     Focuses:  rest-api
-----------------------------------------------+---------------------------
Changes (by SergeyBiryukov):

 * keywords:  has-screenshots close => has-screenshots close 2nd-opinion


Comment:

 Replying to [comment:2 TimothyBlynJacobs]:
 > `SHORTINIT` doesn't load the majority of WordPress, you can see where it
 [https://github.com/WordPress/wordpress-
 develop/blob/bcb3299a37712b61eb9b2a92c0b2fcc81e5d3d9d/src/wp-
 settings.php#L149 stops loading in `wp-settings.php`]. This includes the
 REST API.

 Maybe we could check early in the REST API bootstrap whether `SHORTINIT`
 is defined, and display an appropriate error message in that case? I think
 that would be a better developer experience.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55489#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 19:34:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 19:34:15 -0000
Subject: [wp-trac] [WordPress Trac] #55489: Defining SHORTINIT creates
 an error when index.php is loaded
In-Reply-To: <051.9d661f0592b16f7f25a9c01d9665ef1c@wordpress.org>
References: <051.9d661f0592b16f7f25a9c01d9665ef1c@wordpress.org>
Message-ID: <066.a9669c07303f09fbfa468a9599c35f01@wordpress.org>

#55489: Defining SHORTINIT creates an error when index.php is loaded
-----------------------------------------------+---------------------------
 Reporter:  gerendo                            |       Owner:  (none)
     Type:  defect (bug)                       |      Status:  new
 Priority:  normal                             |   Milestone:  Awaiting
                                               |  Review
Component:  Bootstrap/Load                     |     Version:  5.9.2
 Severity:  normal                             |  Resolution:
 Keywords:  has-screenshots close 2nd-opinion  |     Focuses:  rest-api
-----------------------------------------------+---------------------------

Comment (by TimothyBlynJacobs):

 I think placing it in the REST API would be too late. I think the code
 would need to live in `wp()` and it wouldn't really be specific to the
 REST API I think, just any request that utilizes the WP request handler.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55489#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 20:05:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 20:05:51 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.9b64721c53687de340f2f6588e93813f@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
 Reporter:  ademos                    |       Owner:  marybaum
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+------------------------------

Comment (by paaljoachim):

 Checking using WordPress 5.9.2
 Let's say that I bulk edit three posts that all have a common category
 "Books".
 These also uses the same tag "Fantasy" which are to be replaced.

 **Expectations based on quick editing one post.**
 I would expect when bulk editing these three posts to see the category
 "Books" checked and listed on the top of the categories list.  I would
 also expect to see the tag "Fantasy" in the Tags list. So that I could
 replace the tag "Fantasy" with "Scifi" and click the Update button and see
 all three posts with the "Scifi" tag.

 Currently bulk editing 2 or more posts does not show any checked
 categories or list any tags used. Both are blank. This breaks the
 consistency in comparison for quick editing a single post.

 ----

 I would suggest to first make bulk edit for two or more posts work. To
 where it is similar to quick edit of one post. Keeping the current method
 in place.

 - **Common shared categories are checked and (should be) listed at the top
 of the Categories list.** Unchecking and clicking Update will remove the
 unchecked categories from the bulk edited posts.

 - **Common shared tags are seen in the tags screen.** Removing either by
 clicking into and manually removing as can be done in Quick Edit or
 clicking the x inside the circle as I mocked up further above will remove
 tags from the bulk edited posts.

 I would say that consistency between Quick Edit and Bulk Edit is a very
 important aspect. As a user learns to use the Quick Edit there is the
 expectation that Bulk Edit would work the same way.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:43>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 20:31:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 20:31:29 -0000
Subject: [wp-trac] [WordPress Trac] #53232: Add async decoding attribute
 as default to the HTML image tags generated by WordPress
In-Reply-To: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
References: <051.c820b018dadf1a41d3bccedf28725bf1@wordpress.org>
Message-ID: <066.d982eab37b95ce4619ddf084d79b2525@wordpress.org>

#53232: Add async decoding attribute as default to the HTML image tags generated by
WordPress
-------------------------------------------------+-------------------------
 Reporter:  isaumya                              |       Owner:
                                                 |  adamsilverstein
     Type:  feature request                      |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  refresh                                        |  performance
-------------------------------------------------+-------------------------

Comment (by adamsilverstein):

 Thanks for the feedback and update patch @peterwilsoncc - will review &
 test!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53232#comment:57>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 20:39:07 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 20:39:07 -0000
Subject: [wp-trac] [WordPress Trac] #55490: wp-enqueue error generated by
 Appearance => Widgets
Message-ID: <054.01432c1f6a32204836648f89ff8d4401@wordpress.org>

#55490: wp-enqueue error generated by Appearance => Widgets
--------------------------+-----------------------------
 Reporter:  ksmithcamp    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Widgets       |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Many complaints about this but I don't think issue has been resolved.
 Bringing up the admin screen for Appearance => Widgets generates this
 message:

 PHP Notice:  wp_enqueue_script() was called incorrectly. "wp-editor"
 script should not be enqueued together with the new widgets editor (wp-
 edit-widgets or wp-customize-widgets). Please see Debugging in WordPress
 for more information. (This message was added in version 5.8.0.) in
 /home/dh_kscwksp/lirworkshop.dreamhosters.com/wp-includes/functions.php on
 line 5768

 AND I seem unable to turn off the display you see in the screenshot using
 WPDEBUGGER, no matter what I do to settings, deactivation, removal.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55490>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 20:39:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 20:39:29 -0000
Subject: [wp-trac] [WordPress Trac] #55490: wp-enqueue error generated
 by Appearance => Widgets
In-Reply-To: <054.01432c1f6a32204836648f89ff8d4401@wordpress.org>
References: <054.01432c1f6a32204836648f89ff8d4401@wordpress.org>
Message-ID: <069.63497fa378ae1da6781ae8520bec9864@wordpress.org>

#55490: wp-enqueue error generated by Appearance => Widgets
--------------------------+------------------------------
 Reporter:  ksmithcamp    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Widgets       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by ksmithcamp):

 * Attachment "Screen Shot 2022-03-30 at 4.37.18 PM.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55490>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 20:52:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 20:52:46 -0000
Subject: [wp-trac] [WordPress Trac] #38809: Better wp namespace in
 password-strength-meter.js
In-Reply-To: <051.ffc2a98922d31cf626b3d162412b43b5@wordpress.org>
References: <051.ffc2a98922d31cf626b3d162412b43b5@wordpress.org>
Message-ID: <066.4beb2e89107e91e43790ed61869aa0dc@wordpress.org>

#38809: Better wp namespace in password-strength-meter.js
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Administration                       |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:  javascript
  testing-info close                             |
-------------------------------------------------+-------------------------
Changes (by davidbaumwald):

 * owner:  davidbaumwald => (none)


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/38809#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 21:03:15 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 21:03:15 -0000
Subject: [wp-trac] [WordPress Trac] #51857: Add rollback for failed
 plugin/theme updates
In-Reply-To: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
References: <050.28fc9181b285acd253041ad0e732946d@wordpress.org>
Message-ID: <065.e4cbb304eafe630a4275f8e5772c248a@wordpress.org>

#51857: Add rollback for failed plugin/theme updates
-------------------------------------------------+-------------------------
 Reporter:  pbiron                               |       Owner:  pbiron
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  early has-testing-info needs-unit-   |     Focuses:
  tests needs-testing has-patch dev-feedback     |
  needs-dev-note                                 |
-------------------------------------------------+-------------------------

Comment (by afragen):

 We are currently working on another approach that is a combination of a
 filter and some file checks to that should identify VirtualBox.

 Unfortunately there is no perfect `coded` solution.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51857#comment:207>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Wed Mar 30 23:30:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Wed, 30 Mar 2022 23:30:51 -0000
Subject: [wp-trac] [WordPress Trac] #55015: Site Editor not working for
 TwentyTwentyTwo Child theme
In-Reply-To: <057.2d2b97539ca085d46839b9afdcd566fc@wordpress.org>
References: <057.2d2b97539ca085d46839b9afdcd566fc@wordpress.org>
Message-ID: <072.b2c56a5f253ce80890679df3cdfeea06@wordpress.org>

#55015: Site Editor not working for TwentyTwentyTwo Child theme
---------------------------+---------------------
 Reporter:  mervinpraison  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  5.9.4
Component:  Themes         |     Version:  5.9
 Severity:  normal         |  Resolution:
 Keywords:  needs-patch    |     Focuses:
---------------------------+---------------------
Changes (by peterwilsoncc):

 * component:  Bundled Theme => Themes
 * severity:  major => normal


Comment:

 I've moved this to the themes component as the issue will occur for any
 site in which the child theme and parent theme are in different folders.
 The symptom is apparent with the bundled theme but the cause is elsewhere.

 I've also reduced the severity to `normal` as having two or more theme
 directories is an uncommon set up. For sites with a single theme directory
 the child themes work as expected.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55015#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 00:38:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 00:38:56 -0000
Subject: [wp-trac] [WordPress Trac] #19901: Speeding up Dashboard and
 Comment moderation SQL load
In-Reply-To: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
References: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
Message-ID: <070.6f0071955039d963929ed165c29a4b38@wordpress.org>

#19901: Speeding up Dashboard and Comment moderation SQL load
-------------------------------------------------+-------------------------
 Reporter:  FolioVision                          |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Comments                             |     Version:  3.3
 Severity:  major                                |  Resolution:
 Keywords:  needs-testing has-patch commit       |     Focuses:
  assigned-for-commit                            |  performance
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):

 * keywords:  needs-testing has-patch commit => needs-testing has-patch
     commit assigned-for-commit


Comment:

 @spacedmonkey Go for it, I've hit approve on the PR and assigned you for
 commit.

 I've run `phpunit --filter Tests_Get_Comment_Count` with the new tests
 with and without the patch applied and the results are identical,
 everything passes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19901#comment:35>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 00:44:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 00:44:42 -0000
Subject: [wp-trac] [WordPress Trac] #55360: Add limit to query in
 WP_Tax_Query
In-Reply-To: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
References: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
Message-ID: <071.4e5f4f7455cc61fcdb47e85818c02410@wordpress.org>

#55360: Add limit to query in WP_Tax_Query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  assigned
 Priority:  normal                           |   Milestone:  6.0
Component:  Taxonomy                         |     Version:  4.7
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests commit


Comment:

 Linked [https://github.com/WordPress/wordpress-develop/pull/2396 pull
 request] approved, @spacedmonkey are you able to take the honors for
 commit?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55360#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 00:55:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 00:55:30 -0000
Subject: [wp-trac] [WordPress Trac] #54713: Build/Test Tools: Add unit
 tests for `feed_links_extra()`.
In-Reply-To: <051.ac57845cfdc90a01711f5456345a3c1d@wordpress.org>
References: <051.ac57845cfdc90a01711f5456345a3c1d@wordpress.org>
Message-ID: <066.62a860d25d531feee01980be2eef8f24@wordpress.org>

#54713: Build/Test Tools: Add unit tests for `feed_links_extra()`.
--------------------------------------+-----------------------------
 Reporter:  costdev                   |       Owner:  hellofromTonya
     Type:  task (blessed)            |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------------
Changes (by peterwilsoncc):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53033" 53033]:
 {{{
 #!CommitTicketReference repository="" revision="53033"
 Build/Test Tools: Add unit tests for `feed_links_extra()`.

 Props costdev, hellofromTonya.
 Fixes #54713.
 See #54725.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54713#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 00:55:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 00:55:30 -0000
Subject: [wp-trac] [WordPress Trac] #54725: Test tool and unit test
 improvements for 6.0
In-Reply-To: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
References: <058.ef48a8e18f6094886e999723ee87a81d@wordpress.org>
Message-ID: <073.3e0e4a55309bc2755fb9935246f9e522@wordpress.org>

#54725: Test tool and unit test improvements for 6.0
--------------------------------------+---------------------
 Reporter:  hellofromTonya            |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by peterwilsoncc):

 In [changeset:"53033" 53033]:
 {{{
 #!CommitTicketReference repository="" revision="53033"
 Build/Test Tools: Add unit tests for `feed_links_extra()`.

 Props costdev, hellofromTonya.
 Fixes #54713.
 See #54725.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54725#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 01:00:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 01:00:36 -0000
Subject: [wp-trac] [WordPress Trac] #54713: Build/Test Tools: Add unit
 tests for `feed_links_extra()`.
In-Reply-To: <051.ac57845cfdc90a01711f5456345a3c1d@wordpress.org>
References: <051.ac57845cfdc90a01711f5456345a3c1d@wordpress.org>
Message-ID: <066.5f39056250f6179213d2f75ed451f572@wordpress.org>

#54713: Build/Test Tools: Add unit tests for `feed_links_extra()`.
--------------------------------------+-----------------------------
 Reporter:  costdev                   |       Owner:  hellofromTonya
     Type:  task (blessed)            |      Status:  closed
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------------

Comment (by peterwilsoncc):

 @costdev I've committed the tests that were passing as noted above.

 Are you able to create a follow up ticket for the `is_post_type_archive`
 issue you discovered and note it here?

 That will allow the tests to hit 100% once it's decided which piece of
 code is buggy.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54713#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 01:46:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 01:46:37 -0000
Subject: [wp-trac] [WordPress Trac] #55484: class-wp-editor.php line 1697
In-Reply-To: <050.6482079791df9a6ae016d9a05467fef2@wordpress.org>
References: <050.6482079791df9a6ae016d9a05467fef2@wordpress.org>
Message-ID: <065.75e92bd1f9a0a33ffd78efecbff75f14@wordpress.org>

#55484: class-wp-editor.php line 1697
--------------------------+------------------------------
 Reporter:  karin2        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  javascript
--------------------------+------------------------------

Comment (by dd32):

 Welcome to Trac @karin2!

 For others, here's the code in question:
 https://core.trac.wordpress.org/browser/trunk/src/wp-includes/class-wp-
 editor.php?marks=1697-1699&rev=52978#L1692

 And here's what it'd look like if compressed..
 {{{
 ... window.wpActiveEditor = id;}}}}if ( typeof tinymce !== 'undefined' ) {
 ...
 }}}

 My undertstanding is that a `;` is not required in this case, as it's
 implicit after `}` or newlines.

 @karin2 Can you provide information as to what browser & error message
 you're seeing is?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55484#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 02:32:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 02:32:05 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.5461a80a619b55c6011b632412a75833@wordpress.org>

#41136: Login forms lacking autocomplete attributes
------------------------------+--------------------------------------------
 Reporter:  johnjamesjacoby   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  6.0
Component:  Login and         |     Version:
  Registration                |
 Severity:  normal            |  Resolution:
 Keywords:  needs-testing     |     Focuses:  accessibility, administration
  has-patch                   |
------------------------------+--------------------------------------------

Comment (by peterwilsoncc):

 Thanks for following up @rianrietveld.

 In the [https://github.com/WordPress/wordpress-develop/pull/2480/ linked
 pull request], I've added the `autocomplete="username"` attribute to the
 forgotten password page.

 To keep this ticket focused on current usernames and passwords, let's
 focus on `new-password` in #43886. It's also on the 6.0 milestone but is
 slightly more nuanced.

 @joedolson If you're happy with my addition on the PR, feel free to commit
 at your convienience. Your changes tested well during manual testing.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 02:35:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 02:35:08 -0000
Subject: [wp-trac] [WordPress Trac] #55491: Replace unload from heartbeat js
Message-ID: <054.abc67d9ec8da6401c6285c9a9c8e3479@wordpress.org>

#55491: Replace unload from heartbeat js
-------------------------+-----------------------------
 Reporter:  shawfactor   |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:  5.9
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 Right now the heartbeat javascript library uses an unload handler, this
 means that where ever it is used the page is not elgible for the bfcache
 in many browsers.

 https://web.dev/bfcache/


 Wordpress could get a significant performance improvement if this listener
 was replaced by using the page visibility api or a combination of pagehide
 handlers. Which i assume are possible in jquery

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55491>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 02:42:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 02:42:09 -0000
Subject: [wp-trac] [WordPress Trac] #55491: Replace unload from
 heartbeat js
In-Reply-To: <054.abc67d9ec8da6401c6285c9a9c8e3479@wordpress.org>
References: <054.abc67d9ec8da6401c6285c9a9c8e3479@wordpress.org>
Message-ID: <069.dd17077a0daa71c3269fc0a843674d5f@wordpress.org>

#55491: Replace unload from heartbeat js
----------------------------+--------------------------------------
 Reporter:  shawfactor      |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  javascript, performance
----------------------------+--------------------------------------
Changes (by peterwilsoncc):

 * focuses:   => javascript, performance
 * component:  General => Administration
 * version:  5.9 =>


Comment:

 Putting this on the performance focus to get some eyes on it.

 According to the [https://caniuse.com/page-transition-events caniuse
 listing for the related pageshow and pagehide events], browser support is
 at 97% of all users.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55491#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 03:12:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 03:12:36 -0000
Subject: [wp-trac] [WordPress Trac] #55491: Replace unload from
 heartbeat js
In-Reply-To: <054.abc67d9ec8da6401c6285c9a9c8e3479@wordpress.org>
References: <054.abc67d9ec8da6401c6285c9a9c8e3479@wordpress.org>
Message-ID: <069.89245785a370559c70905e55f7faf326@wordpress.org>

#55491: Replace unload from heartbeat js
----------------------------+--------------------------------------
 Reporter:  shawfactor      |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  javascript, performance
----------------------------+--------------------------------------

Comment (by shawfactor):

 Even if 97% is not enough I'd assume that it is possible to test support
 and fallback to unload where appropriate. Note my javascript is not up too
 the task of fixing this myself unfortunately.

 Ideally the whole api would be rewritten without a jquery dependency, but
 that should probably be kept as a separate issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55491#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 03:13:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 03:13:03 -0000
Subject: [wp-trac] [WordPress Trac] #54589: Audit and preload current
 "from" version files into memory before upgrading filesystem to the "to"
 version
In-Reply-To: <058.2a41f8a958a91084b1dda258d6b2cacc@wordpress.org>
References: <058.2a41f8a958a91084b1dda258d6b2cacc@wordpress.org>
Message-ID: <073.333d0a658c6333f1106420a335a58454@wordpress.org>

#54589: Audit and preload current "from" version files into memory before upgrading
filesystem to the "to" version
--------------------------------------------+-----------------------------
 Reporter:  hellofromTonya                  |       Owner:  (none)
     Type:  enhancement                     |      Status:  new
 Priority:  normal                          |   Milestone:  Future Release
Component:  Upgrade/Install                 |     Version:  2.7
 Severity:  normal                          |  Resolution:
 Keywords:  early has-patch has-unit-tests  |     Focuses:
--------------------------------------------+-----------------------------
Changes (by peterwilsoncc):

 * milestone:  6.0 => Future Release


Comment:

 I'm moving this off the milestone for now, it looks like it still has a
 bit of work before it's ready for merging.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54589#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 03:29:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 03:29:23 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive
 elements for KSES
In-Reply-To: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
References: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
Message-ID: <064.c9685864ff3970fa41a8080d44c6e42b@wordpress.org>

#55407: Allow case-insensitive elements for KSES
----------------------------------------+---------------------
 Reporter:  r-a-y                       |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+---------------------
Changes (by peterwilsoncc):

 * Attachment "55407.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 03:44:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 03:44:03 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive
 elements for KSES
In-Reply-To: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
References: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
Message-ID: <064.1c0535e36893ae9bb104c2d361c22a18@wordpress.org>

#55407: Allow case-insensitive elements for KSES
----------------------------------------+---------------------
 Reporter:  r-a-y                       |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+---------------------

Comment (by peterwilsoncc):

 I'll resolve this ticket with the documentation fix in
 [attachment:"55407.diff"].

 As browsers treat HTML tags and attributes without case sensitivity, KSES
 needs to as well to match the behavior.

 The affect of this is KSES does need to be a little stricter with
 developers when adding elements to the array of supported values. This
 requires the values all be in lowercase.

 I did consider whether it could be resolved by code to allow both
 uppercase and lowercase elements in the allow list, but it would have a
 performance hit looping through the array each time and would cause
 problems for developers wishing to remove elements from the allow list.
 Removing `div` would also require removing `DIV`, `Div`, `DIv`, and the
 other possible combinations.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 03:47:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 03:47:14 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive
 elements for KSES
In-Reply-To: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
References: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
Message-ID: <064.7a097b2c070314dac9a725bdf6c639e5@wordpress.org>

#55407: Allow case-insensitive elements for KSES
----------------------------------------+---------------------
 Reporter:  r-a-y                       |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+---------------------
Changes (by peterwilsoncc):

 * Attachment "55407.2.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 03:52:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 03:52:46 -0000
Subject: [wp-trac] [WordPress Trac] #53399: Docblock improvements for WP
 5.9
In-Reply-To: <051.b8ed776e7cd9b539f85cdd4bc3d74787@wordpress.org>
References: <051.b8ed776e7cd9b539f85cdd4bc3d74787@wordpress.org>
Message-ID: <066.7be08a844e59d79b6bfc3306a6860967@wordpress.org>

#53399: Docblock improvements for WP 5.9
--------------------------------------+---------------------
 Reporter:  desrosj                   |       Owner:  (none)
     Type:  task (blessed)            |      Status:  closed
 Priority:  normal                    |   Milestone:  5.9
Component:  General                   |     Version:
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:  docs
--------------------------------------+---------------------

Comment (by peterwilsoncc):

 In [changeset:"53034" 53034]:
 {{{
 #!CommitTicketReference repository="" revision="53034"
 KSES: Document HTML allow list is in lowercase.

 Expand documentation of the `wp_kses_allowed_html` hook to indicate that
 developers must add permitted HTML tags and attributes in lowercase for
 KSES to recognise they are permitted.

 Props r-a-y, SergeyBiryukov, peterwilsoncc.
 Fixes #55407.
 See #53399.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53399#comment:133>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 03:52:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 03:52:46 -0000
Subject: [wp-trac] [WordPress Trac] #55407: Allow case-insensitive
 elements for KSES
In-Reply-To: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
References: <049.532816623a1c13ba146d59ccc784cdaa@wordpress.org>
Message-ID: <064.3239091c0f8662597f0fb459c17f182c@wordpress.org>

#55407: Allow case-insensitive elements for KSES
----------------------------------------+----------------------------
 Reporter:  r-a-y                       |       Owner:  peterwilsoncc
     Type:  defect (bug)                |      Status:  closed
 Priority:  normal                      |   Milestone:  6.0
Component:  Formatting                  |     Version:
 Severity:  normal                      |  Resolution:  fixed
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+----------------------------
Changes (by peterwilsoncc):

 * owner:  (none) => peterwilsoncc
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53034" 53034]:
 {{{
 #!CommitTicketReference repository="" revision="53034"
 KSES: Document HTML allow list is in lowercase.

 Expand documentation of the `wp_kses_allowed_html` hook to indicate that
 developers must add permitted HTML tags and attributes in lowercase for
 KSES to recognise they are permitted.

 Props r-a-y, SergeyBiryukov, peterwilsoncc.
 Fixes #55407.
 See #53399.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55407#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 04:20:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 04:20:58 -0000
Subject: [wp-trac] [WordPress Trac] #55492: `Dismiss Errors` button
 alignment is not centered in Media Library.
Message-ID: <053.4fe5c4fa6528e6e4d1c4ac58c8aa0653@wordpress.org>

#55492: `Dismiss Errors` button alignment is not centered in Media Library.
-------------------------+-------------------------------------------------
 Reporter:  iamjaydip    |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:  5.9.2
 Severity:  normal       |   Keywords:  has-patch has-screenshots needs-
  Focuses:               |  testing
-------------------------+-------------------------------------------------
 When I drag/upload an SVG image in the Media library then it shows a mime
 types error and the "Dismiss Errors" button is not aligned properly.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55492>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 04:23:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 04:23:21 -0000
Subject: [wp-trac] [WordPress Trac] #55492: `Dismiss Errors` button
 alignment is not centered in Media Library.
In-Reply-To: <053.4fe5c4fa6528e6e4d1c4ac58c8aa0653@wordpress.org>
References: <053.4fe5c4fa6528e6e4d1c4ac58c8aa0653@wordpress.org>
Message-ID: <068.0cbfc5b39a524c6b5c3ae3c7798e6f58@wordpress.org>

#55492: `Dismiss Errors` button alignment is not centered in Media Library.
-------------------------------------------------+-------------------------
 Reporter:  iamjaydip                            |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:  5.9.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-screenshots needs-     |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by iamjaydip):

 * Attachment "55492.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55492>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 04:26:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 04:26:10 -0000
Subject: [wp-trac] [WordPress Trac] #55492: `Dismiss Errors` button
 alignment is not centered in Media Library.
In-Reply-To: <053.4fe5c4fa6528e6e4d1c4ac58c8aa0653@wordpress.org>
References: <053.4fe5c4fa6528e6e4d1c4ac58c8aa0653@wordpress.org>
Message-ID: <068.530c5309b26dc858ca24799239251c93@wordpress.org>

#55492: `Dismiss Errors` button alignment is not centered in Media Library.
-------------------------------------------------+-------------------------
 Reporter:  iamjaydip                            |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:  5.9.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-screenshots needs-     |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------
Changes (by iamjaydip):

 * Attachment "55492.png" added.

 Please find the attachment to good understand the issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55492>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 05:05:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 05:05:45 -0000
Subject: [wp-trac] [WordPress Trac] #50567: Set $post filter in
 update_post_cache()
In-Reply-To: <048.1eeec1936ec5f77048352a7675dec2ed@wordpress.org>
References: <048.1eeec1936ec5f77048352a7675dec2ed@wordpress.org>
Message-ID: <063.453942b7a2de35bad48dde85e450b6cb@wordpress.org>

#50567: Set $post filter in update_post_cache()
--------------------------------------+----------------------------
 Reporter:  Cybr                      |       Owner:  peterwilsoncc
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Posts, Post Types         |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+----------------------------
Changes (by peterwilsoncc):

 * keywords:  has-patch needs-unit-tests => has-patch has-unit-tests
 * owner:  hellofromTonya => peterwilsoncc
 * version:  5.5 =>
 * type:  defect (bug) => enhancement


Comment:

 I've pushed some tests to the PR and updated against trunk. I've asked for
 a second set of eyes to look at the tests in the hope I can get this
 committed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50567#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 06:51:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 06:51:54 -0000
Subject: [wp-trac] [WordPress Trac] #54239: tests for
 wp_fuzzy_number_match
In-Reply-To: <051.62c9969ea7921f6ca8e6a74dacabcadb@wordpress.org>
References: <051.62c9969ea7921f6ca8e6a74dacabcadb@wordpress.org>
Message-ID: <066.d86f3d1a9bfa67a137d6e82654abd0ab@wordpress.org>

#54239: tests for wp_fuzzy_number_match
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  hellofromTonya
     Type:  defect (bug)              |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:  5.3
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------------
Changes (by costdev):

 * component:  General => Build/Test Tools


Comment:

 Moving to the Build/Test Tools component.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54239#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 07:06:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 07:06:21 -0000
Subject: [wp-trac] [WordPress Trac] #55493: Docs: Typo in
 `wp_fuzzy_number_match()`.
Message-ID: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>

#55493: Docs: Typo in `wp_fuzzy_number_match()`.
-------------------------+----------------------------------------
 Reporter:  costdev      |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  6.0
Component:  General      |    Version:  5.3
 Severity:  trivial      |   Keywords:  needs-patch good-first-bug
  Focuses:  docs         |
-------------------------+----------------------------------------
 The `@return` annotation in `wp_fuzzy_number_match()` has a typo:

   @return bool Whether the numbers match whithin the specified precision.

 "whithin" should be "within".

 [https://github.com/WordPress/wordpress-
 develop/blob/cab053271e272a21b4d140e50ac0d6a78094ecd5/src/wp-
 includes/functions.php#L8423 See source].

 Let's try to keep this one for someone who hasn't submitted a patch
 before. This is a great way to learn the workflow of contributing to Core.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55493>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 07:17:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 07:17:25 -0000
Subject: [wp-trac] [WordPress Trac] #55493: Docs: Typo in
 `wp_fuzzy_number_match()`.
In-Reply-To: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
References: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
Message-ID: <066.151eae418400cfd621678369325235a7@wordpress.org>

#55493: Docs: Typo in `wp_fuzzy_number_match()`.
--------------------------------------+---------------------
 Reporter:  costdev                   |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  General                   |     Version:  5.3
 Severity:  trivial                   |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  docs
--------------------------------------+---------------------

Comment (by kebbet):

 Also, see: https://core.trac.wordpress.org/ticket/54729

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55493#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 07:22:12 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 07:22:12 -0000
Subject: [wp-trac] [WordPress Trac] #54239: tests for
 wp_fuzzy_number_match
In-Reply-To: <051.62c9969ea7921f6ca8e6a74dacabcadb@wordpress.org>
References: <051.62c9969ea7921f6ca8e6a74dacabcadb@wordpress.org>
Message-ID: <066.02a442b3d39eb21a0174f91e20819f9d@wordpress.org>

#54239: tests for wp_fuzzy_number_match
-------------------------------------------------+-------------------------
 Reporter:  pbearne                              |       Owner:
                                                 |  hellofromTonya
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Build/Test Tools                     |     Version:  5.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  refresh                                        |
-------------------------------------------------+-------------------------
Changes (by costdev):

 * keywords:  has-patch has-unit-tests => has-patch has-unit-tests needs-
     refresh


Comment:

 I have left a review on the PR which suggests changes for:

 - Consistency in the test suite.
 - Stricter assertions.
 - Ensuring that dataset keys show correctly when using the `--testdox`
 parameter.
 - More datasets.

 Most of these changes are very quick to make and can be landed in 6.0.

 Additional datasets will take some thought, so these could be added later
 if they need more consideration.

 @pbearne let us know whether you have time to work on the requested
 changes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54239#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 07:34:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 07:34:18 -0000
Subject: [wp-trac] [WordPress Trac] #46122: Code cleanup on $role_links
 to follow precedent from 46112
In-Reply-To: <059.4deb77cf64139c7a065a9bd8b030dd46@wordpress.org>
References: <059.4deb77cf64139c7a065a9bd8b030dd46@wordpress.org>
Message-ID: <074.4b04e27876ecace6e40cc432083f4fd9@wordpress.org>

#46122: Code cleanup on $role_links to follow precedent from 46112
-----------------------------------------+-------------------------------
 Reporter:  garrett-eclipse              |       Owner:  SergeyBiryukov
     Type:  enhancement                  |      Status:  reviewing
 Priority:  normal                       |   Milestone:  6.0
Component:  Users                        |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch close 2nd-opinion  |     Focuses:  coding-standards
-----------------------------------------+-------------------------------
Changes (by costdev):

 * keywords:  has-patch => has-patch close 2nd-opinion


Comment:

 Both of the current patches,
 [https://core.trac.wordpress.org/attachment/ticket/46122/46122.diff
 46122.diff] and
 [https://core.trac.wordpress.org/attachment/ticket/46122/46122.2.diff
 46122.2.diff] no longer apply cleanly against `trunk`.

 In addition, #42066 seeks to standardise the link generation for the
 `get_views()` method in list tables, which may make this ticket obsolete.

 Adding `close` and `2nd-opinion` to see what consensus is on closing this
 ticket in favour of #42066.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46122#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 07:37:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 07:37:19 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.b10c39e2983cbe2437ebad11a5f8ce25@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by costdev):

 Related: #55493

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:51>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 07:38:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 07:38:57 -0000
Subject: [wp-trac] [WordPress Trac] #55493: Docs: Typo in
 `wp_fuzzy_number_match()`.
In-Reply-To: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
References: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
Message-ID: <066.6ab392eb7162ef60eb153d7a19982758@wordpress.org>

#55493: Docs: Typo in `wp_fuzzy_number_match()`.
---------------------------------------------+---------------------
 Reporter:  costdev                          |       Owner:  (none)
     Type:  enhancement                      |      Status:  new
 Priority:  normal                           |   Milestone:  6.0
Component:  General                          |     Version:  5.3
 Severity:  trivial                          |  Resolution:
 Keywords:  good-first-bug has-patch commit  |     Focuses:  docs
---------------------------------------------+---------------------
Changes (by costdev):

 * keywords:  good-first-bug has-patch => good-first-bug has-patch commit


Comment:

 Thanks for the patch @kebbet! The PR looks good to me. Adding `commit`.

 I have also linked this ticket in #54729 as a related ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55493#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 08:07:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 08:07:09 -0000
Subject: [wp-trac] [WordPress Trac] #55493: Docs: Typo in
 `wp_fuzzy_number_match()`.
In-Reply-To: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
References: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
Message-ID: <066.c7cebf9aeb92adc3087ebf54b45c2080@wordpress.org>

#55493: Docs: Typo in `wp_fuzzy_number_match()`.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  5.3
 Severity:  trivial                              |  Resolution:
 Keywords:  good-first-bug has-patch commit      |     Focuses:  docs
  assigned-for-commit                            |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  good-first-bug has-patch commit => good-first-bug has-patch
     commit assigned-for-commit
 * owner:  (none) => audrasjb
 * status:  new => accepted


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55493#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 08:14:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 08:14:22 -0000
Subject: [wp-trac] [WordPress Trac] #55493: Docs: Typo in
 `wp_fuzzy_number_match()`.
In-Reply-To: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
References: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
Message-ID: <066.67724fea6fb023888e9a5d1a71669f2d@wordpress.org>

#55493: Docs: Typo in `wp_fuzzy_number_match()`.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  5.3
 Severity:  trivial                              |  Resolution:
 Keywords:  good-first-bug has-patch commit      |     Focuses:  docs
  assigned-for-commit                            |
-------------------------------------------------+-------------------------

Comment (by audrasjb):

 @kebbet as said in the ticket description, tickets labelled `good-first-
 bug` should be kept for people who never contributed to WordPress Core
 before, as it is a great way to learn how to create a patch, etc :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55493#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 08:15:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 08:15:47 -0000
Subject: [wp-trac] [WordPress Trac] #55493: Docs: Typo in
 `wp_fuzzy_number_match()`.
In-Reply-To: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
References: <051.01f3b3ee04dd6bc7e27acb291c57465a@wordpress.org>
Message-ID: <066.0914f2817cff8af3524b3162ddf25f59@wordpress.org>

#55493: Docs: Typo in `wp_fuzzy_number_match()`.
-------------------------------------------------+-------------------------
 Reporter:  costdev                              |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  General                              |     Version:  5.3
 Severity:  trivial                              |  Resolution:  fixed
 Keywords:  good-first-bug has-patch commit      |     Focuses:  docs
  assigned-for-commit                            |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53035" 53035]:
 {{{
 #!CommitTicketReference repository="" revision="53035"
 Docs: Typo correction in `wp_fuzzy_number_match` DocBlock.

 Props costdev, kebbet.
 Fixes #55493.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55493#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 08:29:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 08:29:27 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.842d3ac4fcdfd500b43b02a4d45c66b4@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
----------------------------+-----------------------
 Reporter:  giox069         |       Owner:  afragen
     Type:  defect (bug)    |      Status:  assigned
 Priority:  normal          |   Milestone:  6.0
Component:  Filesystem API  |     Version:  3.7
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------
Changes (by audrasjb):

 * keywords:  has-patch commit => has-patch


Comment:

 `commit` removed, please feel free to re-add the keyword when the PR is ok
 :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 09:07:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 09:07:17 -0000
Subject: [wp-trac] [WordPress Trac] #19901: Speeding up Dashboard and
 Comment moderation SQL load
In-Reply-To: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
References: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
Message-ID: <070.8547827be316d9b179ea9fade5bba2b0@wordpress.org>

#19901: Speeding up Dashboard and Comment moderation SQL load
-------------------------------------------------+-------------------------
 Reporter:  FolioVision                          |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Comments                             |     Version:  3.3
 Severity:  major                                |  Resolution:  fixed
 Keywords:  needs-testing has-patch commit       |     Focuses:
  assigned-for-commit                            |  performance
-------------------------------------------------+-------------------------
Changes (by spacedmonkey):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53036" 53036]:
 {{{
 #!CommitTicketReference repository="" revision="53036"
 Comments: Improve performance of the `wp_count_comments` function.

 Improve performance of the `wp_count_comments` function by replacing a
 complex query with multiple calls to the `get_comments` function. Passing
 the `count` parameter to the `get_comments` function results in a simple
 count query that returns quickly. Using `get_comments` also means that
 query is cached and run through filters.


 Props FolioVision, markjaquith, nacin, ryan, coffee2code, wonderboymusic,
 ComputerGuru, jb510, SergeyBiryukov, Znuff, Rahe, uday17035, spacedmonkey,
 peterwilsoncc.
 Fixes #19901.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19901#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 09:22:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 09:22:23 -0000
Subject: [wp-trac] [WordPress Trac] #55494: Include only Sticky Posts bug
Message-ID: <054.86751fa343f4221d0446a1cbe1015e66@wordpress.org>

#55494: Include only Sticky Posts bug
--------------------------+-----------------------------
 Reporter:  ricoverato    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Editor        |    Version:  5.9.2
 Severity:  critical      |   Keywords:
  Focuses:  template      |
--------------------------+-----------------------------
 Hi there, in wordpress 5.9 last version, using editor to compose pages
 template, you may verify that if in 'Query loop' block you choose to
 select and view only sticky posts, it does not work. It shows instead all
 posts. Even Include and Exclude options are not working.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55494>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 09:47:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 09:47:43 -0000
Subject: [wp-trac] [WordPress Trac] #55438: Flaky result when saving
 widgets in the Widgets Editor
In-Reply-To: <055.23828018540e63ab9c395b5e1a6cc1f2@wordpress.org>
References: <055.23828018540e63ab9c395b5e1a6cc1f2@wordpress.org>
Message-ID: <070.d65affbfcd6554e2e51ec515fb651444@wordpress.org>

#55438: Flaky result when saving widgets in the Widgets Editor
--------------------------+------------------------------
 Reporter:  kevin940726   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Widgets       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  rest-api
--------------------------+------------------------------

Comment (by zieladam):

 These two could be related:

 https://core.trac.wordpress.org/ticket/53657
 https://github.com/WordPress/gutenberg/issues/33335

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55438#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 10:04:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 10:04:39 -0000
Subject: [wp-trac] [WordPress Trac] #55360: Add limit to query in
 WP_Tax_Query
In-Reply-To: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
References: <056.8802a9742370e452f3944c3b15dd7b2a@wordpress.org>
Message-ID: <071.426575001ab0a82f4f36128ab6845c15@wordpress.org>

#55360: Add limit to query in WP_Tax_Query
---------------------------------------------+---------------------------
 Reporter:  spacedmonkey                     |       Owner:  spacedmonkey
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Taxonomy                         |     Version:  4.7
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:  performance
---------------------------------------------+---------------------------
Changes (by spacedmonkey):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53037" 53037]:
 {{{
 #!CommitTicketReference repository="" revision="53037"
 Taxonomy: Improve performance by taxonomy queries by adding a limitting
 requested terms.

 Add a limit to the number of terms requested in taxonomy queries. This
 improves the performance of the query and the likelihood of hitting an
 existing term query cache.

 Props Spacedmonkey, peterwilsoncc, flixos90.
 Fixes #55360.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55360#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 10:23:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 10:23:14 -0000
Subject: [wp-trac] [WordPress Trac] #33073: Some strings need "no HTML
 entities" translator comments
In-Reply-To: <048.563845dd8576d913c71cd9f2e2dbd5ab@wordpress.org>
References: <048.563845dd8576d913c71cd9f2e2dbd5ab@wordpress.org>
Message-ID: <063.57c9a5f74e91572143c1d02eebf31a36@wordpress.org>

#33073: Some strings need "no HTML entities" translator comments
-------------------------+---------------------
 Reporter:  xibe         |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  I18N         |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  needs-patch  |     Focuses:
-------------------------+---------------------

Comment (by Presskopp):

 We just had this issue/discussion in the german polyglots theme, so we can
 see it's still a valid point to be patched. I'm not sure if we need
 comments to tell the translator to not use entities or if we'd need a
 software side patch to convert entities when they appear. However, I'd
 appreciate if this could go forward somewhere.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33073#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 10:48:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 10:48:26 -0000
Subject: [wp-trac] [WordPress Trac] #55495: Translate global style variations
Message-ID: <053.472024708c20d0731a62485ee75847ec@wordpress.org>

#55495: Translate global style variations
-------------------------+-----------------------------
 Reporter:  oandregal    |      Owner:  oandregal
     Type:  enhancement  |     Status:  assigned
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  I18N         |    Version:
 Severity:  normal       |   Keywords:
  Focuses:               |
-------------------------+-----------------------------
 WordPress 6.0 is adding the concept of style variations to Global Styles.
 These are separate `theme.json` files that provide a different set of
 styles.

 There're a few things we need to do to be able to translate what they
 provide:

 - make the `title` key from any `theme.json` translatable
   - requires changes to wp-cli i18n command
   - update the i18n schema available in core
 - make wp-cli's i18n-command look for `theme.json` files under the
 `styles/` folder of a theme (in addition to what it now does of looking in
 the top-level folder)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55495>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 10:54:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 10:54:03 -0000
Subject: [wp-trac] [WordPress Trac] #55495: Translate global style
 variations
In-Reply-To: <053.472024708c20d0731a62485ee75847ec@wordpress.org>
References: <053.472024708c20d0731a62485ee75847ec@wordpress.org>
Message-ID: <068.520e751236a3f739167e437e19dc2546@wordpress.org>

#55495: Translate global style variations
-------------------------+------------------------------
 Reporter:  oandregal    |       Owner:  oandregal
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  I18N         |     Version:
 Severity:  normal       |  Resolution:  fixed
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------------------
Changes (by gziolo):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 Committed with [53038].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55495#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 10:54:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 10:54:13 -0000
Subject: [wp-trac] [WordPress Trac] #55495: Translate global style
 variations
In-Reply-To: <053.472024708c20d0731a62485ee75847ec@wordpress.org>
References: <053.472024708c20d0731a62485ee75847ec@wordpress.org>
Message-ID: <068.e525bb0c29ab0fbfa8cca53fb1690c83@wordpress.org>

#55495: Translate global style variations
-------------------------+------------------------
 Reporter:  oandregal    |       Owner:  oandregal
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  6.0
Component:  I18N         |     Version:
 Severity:  normal       |  Resolution:  fixed
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------------
Changes (by gziolo):

 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55495#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 11:35:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 11:35:01 -0000
Subject: [wp-trac] [WordPress Trac] #52028: Twenty Fifteen: H5 and H6
 headings have the same font size
In-Reply-To: <049.a134b1e283dcba945e47be1b5eab0e4f@wordpress.org>
References: <049.a134b1e283dcba945e47be1b5eab0e4f@wordpress.org>
Message-ID: <064.5898b37d52f63e4d94f2ff6e4f6ca29c@wordpress.org>

#52028: Twenty Fifteen: H5 and H6 headings have the same font size
--------------------------------------+---------------------
 Reporter:  poena                     |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  6.0
Component:  Bundled Theme             |     Version:  4.1
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  css
--------------------------------------+---------------------
Changes (by viralsampat):

 * Attachment "52028.2.patch" added.

 I have changed the tag font size to 20 pixels for desktop and also made
 respective changes for responsive devices. Please let me know if you have
 any query about the same.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52028>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 11:38:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 11:38:35 -0000
Subject: [wp-trac] [WordPress Trac] #53115: Twenty Twenty: number inputs
 have too much padding
In-Reply-To: <058.91e6ff0735e7e5ad214924238f7ad1a6@wordpress.org>
References: <058.91e6ff0735e7e5ad214924238f7ad1a6@wordpress.org>
Message-ID: <073.38bf8f4e298558d535fd0b3367faeba6@wordpress.org>

#53115: Twenty Twenty: number inputs have too much padding
-------------------------------------+--------------------------
 Reporter:  helgatheviking           |       Owner:  sabernhardt
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Bundled Theme            |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css
-------------------------------------+--------------------------

Comment (by nayana123):

 Tested with cross-browsers, it's looking good now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53115#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 11:57:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 11:57:44 -0000
Subject: [wp-trac] [WordPress Trac] #48282: Twenty Nineteen: Captioned
 image is not aligned correctly on IE11
In-Reply-To: <058.707f6353aa94bbf6fec541c4c6f40aef@wordpress.org>
References: <058.707f6353aa94bbf6fec541c4c6f40aef@wordpress.org>
Message-ID: <073.7b27cecd94be8e57bb64f8a0304ca753@wordpress.org>

#48282: Twenty Nineteen: Captioned image is not aligned correctly on IE11
-------------------------------------+------------------------------
 Reporter:  mspatovaliyski           |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Bundled Theme            |     Version:  5.2.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css
-------------------------------------+------------------------------
Changes (by nayana123):

 * keywords:  has-patch => has-patch needs-testing


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48282#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:01:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:01:01 -0000
Subject: [wp-trac] [WordPress Trac] #54833: Twenty Eleven: screen_icon()
 and get_current_theme() are deprecated
In-Reply-To: <053.6933286b542e65c78a5c101fd302689f@wordpress.org>
References: <053.6933286b542e65c78a5c101fd302689f@wordpress.org>
Message-ID: <068.3de31be129d678ce76cee5aa33c46989@wordpress.org>

#54833: Twenty Eleven: screen_icon() and get_current_theme() are deprecated
--------------------------------------+------------------------------
 Reporter:  Presskopp                 |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Bundled Theme             |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+------------------------------
Changes (by viralsampat):

 * Attachment "54833.2.diff" added.

 Removed the deprecated screen_size(), since it does produce any output
 during render, get_current_theme() replaced with static value, since a
 theme name is static. Also, made small changes based on coding standard.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54833>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:02:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:02:46 -0000
Subject: [wp-trac] [WordPress Trac] #55496: Escaping function missing.
Message-ID: <055.47c21e308f0655151d281269da7b55c4@wordpress.org>

#55496: Escaping function missing.
----------------------------+-----------------------------
 Reporter:  chintan1896     |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  General         |    Version:
 Severity:  normal          |   Keywords:  has-patch
  Focuses:  administration  |
----------------------------+-----------------------------
 Escaping function missing in /wp-admin/menu-header.php file.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55496>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:03:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:03:19 -0000
Subject: [wp-trac] [WordPress Trac] #55496: Escaping function missing.
In-Reply-To: <055.47c21e308f0655151d281269da7b55c4@wordpress.org>
References: <055.47c21e308f0655151d281269da7b55c4@wordpress.org>
Message-ID: <070.8424fb5d04195339d52734d386db5648@wordpress.org>

#55496: Escaping function missing.
--------------------------+------------------------------
 Reporter:  chintan1896   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  administration
--------------------------+------------------------------
Changes (by chintan1896):

 * Attachment "55496.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55496>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:14:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:14:43 -0000
Subject: [wp-trac] [WordPress Trac] #51090: Twenty Nineteen: Gutenberg
 default displayed color picker is not working
In-Reply-To: <056.16379c125bf86951a290c53888868417@wordpress.org>
References: <056.16379c125bf86951a290c53888868417@wordpress.org>
Message-ID: <071.8d812d04d3ace4d0dbc06cdefd12d0b3@wordpress.org>

#51090: Twenty Nineteen: Gutenberg default displayed color picker is not working
---------------------------+------------------------------
 Reporter:  kishanjasani   |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:  5.5
 Severity:  major          |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+------------------------------

Comment (by nayana123):

 Checked with the latest version of WP and it's looking good.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51090#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:29:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:29:44 -0000
Subject: [wp-trac] [WordPress Trac] #55462: Improve cache key generation
 in WP_Site_Query
In-Reply-To: <056.788faa0f83ecc66621ed2f44c8bdd070@wordpress.org>
References: <056.788faa0f83ecc66621ed2f44c8bdd070@wordpress.org>
Message-ID: <071.5503d016f733d8c5537cfe3f64f889e5@wordpress.org>

#55462: Improve cache key generation in WP_Site_Query
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Networks and Sites                   |     Version:  4.6
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch has-unit-   |     Focuses:  multisite,
  tests                                          |  performance
-------------------------------------------------+-------------------------

Comment (by furi3r):

 @spacedmonkey PR ready.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55462#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:36:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:36:00 -0000
Subject: [wp-trac] [WordPress Trac] #55497: Twenty Twenty-Two : H5 and H6
 headings have the same font size
Message-ID: <057.a83e79b53c536b752d5b70b7efd965c0@wordpress.org>

#55497: Twenty Twenty-Two : H5 and H6 headings have the same font size
---------------------------+-----------------------------
 Reporter:  priyankkpatel  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  Bundled Theme  |    Version:
 Severity:  normal         |   Keywords:
  Focuses:                 |
---------------------------+-----------------------------
 Working on the new Twenty Twenty-Two theme, I found that the H5 and H6
 heading are having same font-size e.g. 18px.

 H6 heading should be smaller in size than H5.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55497>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:38:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:38:58 -0000
Subject: [wp-trac] [WordPress Trac] #55498: Permalink Settings Page
 Accessibility Improve
Message-ID: <053.06db99f017cbf7d27f8f904f21b948fd@wordpress.org>

#55498: Permalink Settings Page Accessibility Improve
---------------------------+-----------------------------
 Reporter:  rishishah      |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  General        |    Version:  trunk
 Severity:  normal         |   Keywords:
  Focuses:  accessibility  |
---------------------------+-----------------------------
 On the Permalink Settings page, the current accessibility score is 94 for
 Desktop 92 for Mobile devices.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55498>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:39:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:39:16 -0000
Subject: [wp-trac] [WordPress Trac] #55498: Permalink Settings Page
 Accessibility Improve
In-Reply-To: <053.06db99f017cbf7d27f8f904f21b948fd@wordpress.org>
References: <053.06db99f017cbf7d27f8f904f21b948fd@wordpress.org>
Message-ID: <068.e30eb190b32e90369c2c4d829fc9d3e3@wordpress.org>

#55498: Permalink Settings Page Accessibility Improve
--------------------------+------------------------------
 Reporter:  rishishah     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility
--------------------------+------------------------------
Changes (by rishishah):

 * Attachment "Screenshot 2022-03-31 at 6.06.01 PM.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55498>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:42:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:42:45 -0000
Subject: [wp-trac] [WordPress Trac] #55499: $pagenow is used but not define
 in documentation of this function
 add_customize_screen_to_heartbeat_settings()
Message-ID: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>

#55499: $pagenow is used but not define in documentation of this function
add_customize_screen_to_heartbeat_settings()
--------------------------+-----------------------------
 Reporter:  jontyravi     |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.8
 Severity:  normal        |   Keywords:  has-patch
  Focuses:  docs          |
--------------------------+-----------------------------
 global $pagenow is used
 add_customize_screen_to_heartbeat_settings($settings) in this function.
 But it is not mentioned in the documentation of the function.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55499>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:43:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:43:01 -0000
Subject: [wp-trac] [WordPress Trac] #55498: Permalink Settings Page
 Accessibility Improve
In-Reply-To: <053.06db99f017cbf7d27f8f904f21b948fd@wordpress.org>
References: <053.06db99f017cbf7d27f8f904f21b948fd@wordpress.org>
Message-ID: <068.62f6555f2e906d50055a0f35aa3c4747@wordpress.org>

#55498: Permalink Settings Page Accessibility Improve
--------------------------+------------------------------
 Reporter:  rishishah     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility
--------------------------+------------------------------
Changes (by rishishah):

 * Attachment "55498.patch" added.

 Here is the patch to fix and improve accessibility score to 100 on desktop
 and 98 on Mobile

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55498>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:45:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:45:01 -0000
Subject: [wp-trac] [WordPress Trac] #55499: $pagenow is used but not
 define in documentation of this function
 add_customize_screen_to_heartbeat_settings()
In-Reply-To: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
References: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
Message-ID: <068.e086854fa8a0c2306a6420ddffebf9f6@wordpress.org>

#55499: $pagenow is used but not define in documentation of this function
add_customize_screen_to_heartbeat_settings()
--------------------------+------------------------------
 Reporter:  jontyravi     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  docs
--------------------------+------------------------------
Changes (by jontyravi):

 * Attachment "55499.patch" added.

 I have added patch of this ticket

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55499>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:45:40 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:45:40 -0000
Subject: [wp-trac] [WordPress Trac] #55461: Improve cache key generation
 in WP_Network_Query
In-Reply-To: <056.d13ed3c690dcbe4f318e2a175491c637@wordpress.org>
References: <056.d13ed3c690dcbe4f318e2a175491c637@wordpress.org>
Message-ID: <071.7e92741ac1e1151d279c4ffcf955ca3a@wordpress.org>

#55461: Improve cache key generation in WP_Network_Query
-------------------------------------------------+-------------------------
 Reporter:  spacedmonkey                         |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Networks and Sites                   |     Version:  4.6
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch has-unit-   |     Focuses:  multisite,
  tests                                          |  performance
-------------------------------------------------+-------------------------

Comment (by furi3r):

 @spacedmonkey PR ready.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55461#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:48:32 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:48:32 -0000
Subject: [wp-trac] [WordPress Trac] #55497: Twenty Twenty-Two : H5 and
 H6 headings have the same font size
In-Reply-To: <057.a83e79b53c536b752d5b70b7efd965c0@wordpress.org>
References: <057.a83e79b53c536b752d5b70b7efd965c0@wordpress.org>
Message-ID: <072.c0cafdc2771755f85cca6752326d83e7@wordpress.org>

#55497: Twenty Twenty-Two : H5 and H6 headings have the same font size
---------------------------+------------------------------
 Reporter:  priyankkpatel  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by kjellr):

 Hi there! This is actually an intentional design decision. The difference
 in hierarchy between the H5 and H6 is communicated through font weight,
 not font size.

 [[Image(https://cldup.com/h85aO6amkx.png)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55497#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:50:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:50:29 -0000
Subject: [wp-trac] [WordPress Trac] #55497: Twenty Twenty-Two : H5 and
 H6 headings have the same font size
In-Reply-To: <057.a83e79b53c536b752d5b70b7efd965c0@wordpress.org>
References: <057.a83e79b53c536b752d5b70b7efd965c0@wordpress.org>
Message-ID: <072.64ff044635e6fa67b220709b25fc3b3a@wordpress.org>

#55497: Twenty Twenty-Two : H5 and H6 headings have the same font size
---------------------------+------------------------------
 Reporter:  priyankkpatel  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------
Changes (by priyankkpatel):

 * Attachment "55497.1.diff" added.

 Theme.json updated to serve different sizes for h5 and h6

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55497>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:51:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:51:08 -0000
Subject: [wp-trac] [WordPress Trac] #55499: $pagenow is used but not
 define in documentation of this function
 add_customize_screen_to_heartbeat_settings()
In-Reply-To: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
References: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
Message-ID: <068.a1ed874f64b62f8cc19d9ae833b9adb7@wordpress.org>

#55499: $pagenow is used but not define in documentation of this function
add_customize_screen_to_heartbeat_settings()
--------------------------+------------------------------
 Reporter:  jontyravi     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.8
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  docs
--------------------------+------------------------------
Changes (by jontyravi):

 * Attachment "55499.2.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55499>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:51:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:51:26 -0000
Subject: [wp-trac] [WordPress Trac] #55497: Twenty Twenty-Two : H5 and
 H6 headings have the same font size
In-Reply-To: <057.a83e79b53c536b752d5b70b7efd965c0@wordpress.org>
References: <057.a83e79b53c536b752d5b70b7efd965c0@wordpress.org>
Message-ID: <072.209d2556e67160ca0a2df40b83a80631@wordpress.org>

#55497: Twenty Twenty-Two : H5 and H6 headings have the same font size
---------------------------+------------------------------
 Reporter:  priyankkpatel  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Bundled Theme  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:
---------------------------+------------------------------

Comment (by priyankkpatel):

 Hi @kjellr ,
 Thanks for the comment. That make sence.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55497#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 12:55:35 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 12:55:35 -0000
Subject: [wp-trac] [WordPress Trac] #52303: Accessibility issues in
 revisions screen
In-Reply-To: <053.3c3e9cae92ebdb74d01353b06aa5ac56@wordpress.org>
References: <053.3c3e9cae92ebdb74d01353b06aa5ac56@wordpress.org>
Message-ID: <068.cfa62e67a4de48fd3404b0423b4d5c88@wordpress.org>

#52303: Accessibility issues in revisions screen
--------------------------+--------------------------------------------
 Reporter:  joedolson     |       Owner:  joedolson
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Revisions     |     Version:  3.6.1
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  ui, accessibility, javascript
--------------------------+--------------------------------------------
Changes (by rishishah):

 * Attachment "52303.patch" added.

 Here is the patch for "Fix headings hierarchy (current H3 headings should
 be H2)"

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52303>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:09:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:09:47 -0000
Subject: [wp-trac] [WordPress Trac] #48879: Changing Site Admin Email
 Assumes Username and Who Took the Action (which may be incorrect)
In-Reply-To: <055.1b81494cae6182d64bd06e6e7dbaa0fa@wordpress.org>
References: <055.1b81494cae6182d64bd06e6e7dbaa0fa@wordpress.org>
Message-ID: <070.23cc75cb4c5170a5e9529a3b8ec4b070@wordpress.org>

#48879: Changing Site Admin Email Assumes Username and Who Took the Action (which
may be incorrect)
-------------------------------------------------+-------------------------
 Reporter:  MadtownLems                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Users                                |     Version:  5.3
 Severity:  minor                                |  Resolution:
 Keywords:  good-first-bug has-patch dev-        |     Focuses:  multisite
  feedback                                       |
-------------------------------------------------+-------------------------
Changes (by rehanali):

 * Attachment "#48879.patch" added.

 Added patch

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48879>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:16:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:16:36 -0000
Subject: [wp-trac] [WordPress Trac] #55499: $pagenow is used but not
 define in documentation of this function
 add_customize_screen_to_heartbeat_settings()
In-Reply-To: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
References: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
Message-ID: <068.9e7fbfac04c0a2e5ce21efb480d1e327@wordpress.org>

#55499: $pagenow is used but not define in documentation of this function
add_customize_screen_to_heartbeat_settings()
-------------------------+------------------------------
 Reporter:  jontyravi    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:  5.8
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  docs
-------------------------+------------------------------
Changes (by bhrugesh12):

 * type:  defect (bug) => enhancement


Comment:

 Add doc comment for $global variable $pagenow. Find the latest attachment.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55499#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:17:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:17:18 -0000
Subject: [wp-trac] [WordPress Trac] #55499: $pagenow is used but not
 define in documentation of this function
 add_customize_screen_to_heartbeat_settings()
In-Reply-To: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
References: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
Message-ID: <068.e089edc4317a82fdc82e40245ecd8bb5@wordpress.org>

#55499: $pagenow is used but not define in documentation of this function
add_customize_screen_to_heartbeat_settings()
-------------------------+------------------------------
 Reporter:  jontyravi    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:  5.8
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  docs
-------------------------+------------------------------
Changes (by bhrugesh12):

 * Attachment "55499.3.diff" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55499>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:21:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:21:20 -0000
Subject: [wp-trac] [WordPress Trac] #55494: Include only Sticky Posts bug
In-Reply-To: <054.86751fa343f4221d0446a1cbe1015e66@wordpress.org>
References: <054.86751fa343f4221d0446a1cbe1015e66@wordpress.org>
Message-ID: <069.5bd97b1431e515ffad4c92a5fd2273b4@wordpress.org>

#55494: Include only Sticky Posts bug
--------------------------+------------------------------
 Reporter:  ricoverato    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.2
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:  template
--------------------------+------------------------------

Comment (by priyankkpatel):

 Hi There,
 I have installed fresh WordPress and activated the Twenty Twenty-Two there
 for FSE and I created/edited the page template but it is working fine for
 me.
 Can you please give it a try one more time using fresh WordPress install?
 Thanks

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55494#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:39:14 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:39:14 -0000
Subject: [wp-trac] [WordPress Trac] #55500: Ability to change slug of
 Attachments
Message-ID: <056.6644f42e9ec8d624a0a7ee644aa6999c@wordpress.org>

#55500: Ability to change slug of Attachments
--------------------------+-----------------------------
 Reporter:  nidhishanker  |      Owner:  (none)
     Type:  enhancement   |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  5.9.2
 Severity:  normal        |   Keywords:  needs-patch
  Focuses:  performance   |
--------------------------+-----------------------------
 [[Image()]]As WordPress facilitates to change permalink/slug of Post
 Types, it is suggested to enable editing the slug of Attached Media.

 Right now after uploading an image, it is possible to update all
 information except the media slug.

 In my case, the slug had some encrypted or random character and now I want
 to change the slug of Attachment.

 Note: Required screenshots are attached.
 []

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55500>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:39:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:39:47 -0000
Subject: [wp-trac] [WordPress Trac] #55500: Ability to change slug of
 Attachments
In-Reply-To: <056.6644f42e9ec8d624a0a7ee644aa6999c@wordpress.org>
References: <056.6644f42e9ec8d624a0a7ee644aa6999c@wordpress.org>
Message-ID: <071.b4fe7a8f4dac3d22ccdd29b69f2bae5b@wordpress.org>

#55500: Ability to change slug of Attachments
--------------------------+------------------------------
 Reporter:  nidhishanker  |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  performance
--------------------------+------------------------------
Changes (by nidhishanker):

 * Attachment "after-image-upload.png" added.

 Attachment after uploading media.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55500>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:40:11 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:40:11 -0000
Subject: [wp-trac] [WordPress Trac] #55500: Ability to change slug of
 Attachments
In-Reply-To: <056.6644f42e9ec8d624a0a7ee644aa6999c@wordpress.org>
References: <056.6644f42e9ec8d624a0a7ee644aa6999c@wordpress.org>
Message-ID: <071.deb7f15bd6ebe4148dbffee93d6664c8@wordpress.org>

#55500: Ability to change slug of Attachments
--------------------------+------------------------------
 Reporter:  nidhishanker  |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  performance
--------------------------+------------------------------
Changes (by nidhishanker):

 * Attachment "after-image-renamed.png" added.

 Attachment after renaming media but permalink remains steady.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55500>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:48:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:48:37 -0000
Subject: [wp-trac] [WordPress Trac] #14179: Theme asking to update
 (theme with same name on WordPress.org)
In-Reply-To: <058.1888876aa9afb2ce12323566fee2c44f@wordpress.org>
References: <058.1888876aa9afb2ce12323566fee2c44f@wordpress.org>
Message-ID: <073.9d4f7050435d6f6f642930b022d903fd@wordpress.org>

#14179: Theme asking to update (theme with same name on WordPress.org)
-------------------------------------------------+-------------------------
 Reporter:  design_dolphin                       |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  6.0
Component:  Upgrade/Install                      |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests needs-    |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------

Comment (by leemon):

 I hope this will get into WP6.0

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/14179#comment:85>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:56:36 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:56:36 -0000
Subject: [wp-trac] [WordPress Trac] #55501: Multiple loader issue on admin
 general setting page.
Message-ID: <060.a1c64ff42e543ce2dbbcd1edf5b9154c@wordpress.org>

#55501: Multiple loader issue on admin general setting page.
---------------------------------------+-----------------------------
 Reporter:  bhaveshkhadodara           |      Owner:  (none)
     Type:  defect (bug)               |     Status:  new
 Priority:  normal                     |  Milestone:  Awaiting Review
Component:  General                    |    Version:  5.9.2
 Severity:  normal                     |   Keywords:  needs-patch
  Focuses:  administration, multisite  |
---------------------------------------+-----------------------------
 When you select a new language from the general settings page and click
 submit multiple times, multiple loader images are appended.

 Step 1: Open settings -> general page
 Step 2: Select a new language from the site language option.
 Step 3: click the "Save Changes" button multiple times.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55501>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:57:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:57:08 -0000
Subject: [wp-trac] [WordPress Trac] #55501: Multiple loader issue on
 admin general setting page.
In-Reply-To: <060.a1c64ff42e543ce2dbbcd1edf5b9154c@wordpress.org>
References: <060.a1c64ff42e543ce2dbbcd1edf5b9154c@wordpress.org>
Message-ID: <075.6c2967cd2131c5179337fb0307718840@wordpress.org>

#55501: Multiple loader issue on admin general setting page.
------------------------------+----------------------------------------
 Reporter:  bhaveshkhadodara  |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  General           |     Version:  5.9.2
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  administration, multisite
------------------------------+----------------------------------------
Changes (by bhaveshkhadodara):

 * Attachment "Loader Issue on setting page.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55501>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 13:57:10 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 13:57:10 -0000
Subject: [wp-trac] [WordPress Trac] #55501: Multiple loader issue on
 admin general setting page.
In-Reply-To: <060.a1c64ff42e543ce2dbbcd1edf5b9154c@wordpress.org>
References: <060.a1c64ff42e543ce2dbbcd1edf5b9154c@wordpress.org>
Message-ID: <075.64009cb51038746e319e41d1fcdab484@wordpress.org>

#55501: Multiple loader issue on admin general setting page.
------------------------------+----------------------------------------
 Reporter:  bhaveshkhadodara  |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  General           |     Version:  5.9.2
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  administration, multisite
------------------------------+----------------------------------------
Changes (by bhaveshkhadodara):

 * Attachment "Loader Issue on setting page.2.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55501>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:03:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:03:05 -0000
Subject: [wp-trac] [WordPress Trac] #55502: Spacing Issue of Input field
 Under Mobile Device
Message-ID: <053.9eb4742680fd10cf5ecb3ab8db9dc266@wordpress.org>

#55502: Spacing Issue of Input field Under Mobile Device
--------------------------------+-----------------------------
 Reporter:  tejas5989           |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  General             |    Version:  5.9.2
 Severity:  normal              |   Keywords:  has-patch
  Focuses:  ui, administration  |
--------------------------------+-----------------------------
 I have attached a screenshot of the Responsive device for the Writing
 option under Setting Options where **Port** input field of **Mail Server**
 get messed with each other.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55502>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:04:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:04:23 -0000
Subject: [wp-trac] [WordPress Trac] #55503: Post Date display issue if we
 set empty from General Settings page
Message-ID: <053.b21b3a6386e31f62eaf63a305e719594@wordpress.org>

#55503: Post Date display issue if we set empty from General Settings page
----------------------------+-----------------------------
 Reporter:  rishishah       |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Administration  |    Version:
 Severity:  normal          |   Keywords:
  Focuses:  administration  |
----------------------------+-----------------------------
 Hello,

 I have faced one issue with the post date field on the backend side.

 If we set empty Date and Time format from the General Settings page then
 the post date will be empty displaying on the edit screen of an
 article(any post type).
 We need to set any default date and time format to display or make the
 Date format and Time format field required. If any admin set it empty
 mistakenly then it will take hours to figure out the root cause of the
 issue.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55503>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:04:37 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:04:37 -0000
Subject: [wp-trac] [WordPress Trac] #55503: Post Date display issue if
 we set empty from General Settings page
In-Reply-To: <053.b21b3a6386e31f62eaf63a305e719594@wordpress.org>
References: <053.b21b3a6386e31f62eaf63a305e719594@wordpress.org>
Message-ID: <068.69d24d2ae1629dcf7e95586ea64796b8@wordpress.org>

#55503: Post Date display issue if we set empty from General Settings page
----------------------------+------------------------------
 Reporter:  rishishah       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  administration
----------------------------+------------------------------
Changes (by rishishah):

 * Attachment "post date bug.jpg" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55503>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:04:39 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:04:39 -0000
Subject: [wp-trac] [WordPress Trac] #55502: Spacing Issue of Input field
 Under Mobile Device
In-Reply-To: <053.9eb4742680fd10cf5ecb3ab8db9dc266@wordpress.org>
References: <053.9eb4742680fd10cf5ecb3ab8db9dc266@wordpress.org>
Message-ID: <068.eac3f09959290bf4c4f57f791bbc5c07@wordpress.org>

#55502: Spacing Issue of Input field Under Mobile Device
--------------------------+---------------------------------
 Reporter:  tejas5989     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, administration
--------------------------+---------------------------------
Changes (by tejas5989):

 * Attachment "#55502.patch" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55502>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:05:13 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:05:13 -0000
Subject: [wp-trac] [WordPress Trac] #55502: Spacing Issue of Input field
 Under Mobile Device
In-Reply-To: <053.9eb4742680fd10cf5ecb3ab8db9dc266@wordpress.org>
References: <053.9eb4742680fd10cf5ecb3ab8db9dc266@wordpress.org>
Message-ID: <068.4a35e644789a984bc0080ecf71be13a1@wordpress.org>

#55502: Spacing Issue of Input field Under Mobile Device
--------------------------+---------------------------------
 Reporter:  tejas5989     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, administration
--------------------------+---------------------------------
Changes (by tejas5989):

 * Attachment "WP-admin-writing-screen.jpg" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55502>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:06:22 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:06:22 -0000
Subject: [wp-trac] [WordPress Trac] #55501: Multiple loader issue on
 admin general setting page.
In-Reply-To: <060.a1c64ff42e543ce2dbbcd1edf5b9154c@wordpress.org>
References: <060.a1c64ff42e543ce2dbbcd1edf5b9154c@wordpress.org>
Message-ID: <075.cdfacff679be640ac32ade4ca784a209@wordpress.org>

#55501: Multiple loader issue on admin general setting page.
------------------------------+----------------------------------------
 Reporter:  bhaveshkhadodara  |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  General           |     Version:  5.9.2
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:  administration, multisite
------------------------------+----------------------------------------
Changes (by jariwalasagar):

 * Attachment "55501.patch" added.

 Applied patch for this ticket.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55501>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:09:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:09:09 -0000
Subject: [wp-trac] [WordPress Trac] #55501: Multiple loader issue on
 admin general setting page.
In-Reply-To: <060.a1c64ff42e543ce2dbbcd1edf5b9154c@wordpress.org>
References: <060.a1c64ff42e543ce2dbbcd1edf5b9154c@wordpress.org>
Message-ID: <075.fc80cf05bb745a09a84e532c63ac2aca@wordpress.org>

#55501: Multiple loader issue on admin general setting page.
------------------------------+----------------------------------------
 Reporter:  bhaveshkhadodara  |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  General           |     Version:  5.9.2
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:  administration, multisite
------------------------------+----------------------------------------
Changes (by jariwalasagar):

 * keywords:  needs-patch => has-patch


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55501#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:25:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:25:27 -0000
Subject: [wp-trac] [WordPress Trac] #55504: Pullquote Block: Need Option to
 change casing of the citation text
Message-ID: <058.b42e25aee68c5461d5ecbaa19a959df8@wordpress.org>

#55504: Pullquote Block: Need Option to change casing of the citation text
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  (none)
  bhaveshdesai13         |
     Type:  defect       |     Status:  new
  (bug)                  |
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  General      |    Version:  5.9.2
 Severity:  minor        |   Keywords:  needs-design-feedback has-
  Focuses:  css          |  screenshots
-------------------------+-------------------------------------------------
 We have the option to change the casing of the Quote text in the Pullquote
 block settings but not for the citation text.
 [https://prnt.sc/pMbEDbmOqSjW]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55504>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:29:18 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:29:18 -0000
Subject: [wp-trac] [WordPress Trac] #55504: Pullquote Block: Need Option
 to change casing of the citation text
In-Reply-To: <058.b42e25aee68c5461d5ecbaa19a959df8@wordpress.org>
References: <058.b42e25aee68c5461d5ecbaa19a959df8@wordpress.org>
Message-ID: <073.9cb902a5065e2e284ba84c5aee40a4e9@wordpress.org>

#55504: Pullquote Block: Need Option to change casing of the citation text
-------------------------------------------------+-------------------------
 Reporter:  bhaveshdesai13                       |       Owner:  (none)
     Type:  feature request                      |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  General                              |     Version:  5.9.2
 Severity:  minor                                |  Resolution:
 Keywords:  needs-design-feedback has-           |     Focuses:  css
  screenshots                                    |
-------------------------------------------------+-------------------------
Changes (by bhaveshdesai13):

 * type:  defect (bug) => feature request


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55504#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:30:58 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:30:58 -0000
Subject: [wp-trac] [WordPress Trac] #55503: Post Date display issue if
 we set empty from General Settings page
In-Reply-To: <053.b21b3a6386e31f62eaf63a305e719594@wordpress.org>
References: <053.b21b3a6386e31f62eaf63a305e719594@wordpress.org>
Message-ID: <068.fa3af6195b4d723e73e2fabd178f676c@wordpress.org>

#55503: Post Date display issue if we set empty from General Settings page
----------------------------+------------------------------
 Reporter:  rishishah       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  administration
----------------------------+------------------------------
Changes (by rishishah):

 * Attachment "55503.patch" added.

 Applied patch to add default value if anyone kept blank Date and Time
 format field.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55503>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 14:45:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 14:45:09 -0000
Subject: [wp-trac] [WordPress Trac] #55502: Spacing Issue of Input field
 Under Mobile Device
In-Reply-To: <053.9eb4742680fd10cf5ecb3ab8db9dc266@wordpress.org>
References: <053.9eb4742680fd10cf5ecb3ab8db9dc266@wordpress.org>
Message-ID: <068.bf2562cdedd8227141c3dab9d269be65@wordpress.org>

#55502: Spacing Issue of Input field Under Mobile Device
--------------------------+---------------------------------
 Reporter:  tejas5989     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui, administration
--------------------------+---------------------------------
Changes (by viralsampat):

 * Attachment "55502.diff" added.

 I have added CSS for mobile devices.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55502>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 15:19:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 15:19:26 -0000
Subject: [wp-trac] [WordPress Trac] #55327: PHP 8.0: improvements to
 allow for named parameters in WP 6.0
In-Reply-To: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
References: <057.dcc49bb86c8fa8cf2894927282c1e076@wordpress.org>
Message-ID: <072.69621d8c5609659dc45e8ca7bb3b2f5e@wordpress.org>

#55327: PHP 8.0: improvements to allow for named parameters in WP 6.0
-----------------------------+---------------------
 Reporter:  peterwilsoncc    |       Owner:  (none)
     Type:  task (blessed)   |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  php80 has-patch  |     Focuses:
-----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"53039" 53039]:
 {{{
 #!CommitTicketReference repository="" revision="53039"
 Code Modernization: Rename parameters that use reserved keywords in `wp-
 admin/includes/class-wp-list-table.php`.

 While using reserved PHP keywords as parameter name labels is allowed, in
 the context of function calls using named parameters in PHP 8.0+, this
 will easily lead to confusion. To avoid that, it is recommended not to use
 reserved keywords as function parameter names.

 This commit renames the `$default` parameter to `$default_value` in
 `WP_List_Table::get_items_per_page()`.

 Follow-up to [52946], [52996], [52997], [52998], [53003], [53014],
 [53029].

 Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
 See #55327.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55327#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 15:24:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 15:24:45 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.236c823a03e8e5ee118ddd6a41c955d3@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
---------------------------------------------+-----------------------
 Reporter:  pbearne                          |       Owner:  flixos90
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------

Comment (by superpoincare):

 This filter seems to be running twice.

 So if I modify the img tag, like add some attribute, it will be added
 twice.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 15:26:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 15:26:23 -0000
Subject: [wp-trac] [WordPress Trac] #54729: Docblock improvements for WP
 6.0
In-Reply-To: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
References: <058.e97648b36f9e1c40d59d78da529f4b69@wordpress.org>
Message-ID: <073.6fdfb9eb995ad4181bb4e4abf68f0715@wordpress.org>

#54729: Docblock improvements for WP 6.0
----------------------------+---------------------
 Reporter:  hellofromTonya  |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  6.0
Component:  General         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------

Comment (by SergeyBiryukov):

 In [changeset:"53040" 53040]:
 {{{
 #!CommitTicketReference repository="" revision="53040"
 Docs: Add missing descriptions for `WP_List_Table::get_items_per_page()`
 parameters.

 Follow-up to [53039].

 Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
 See #54729, #55327.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54729#comment:52>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 15:34:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 15:34:19 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.73c18eb184df9e87287dd04f75202e71@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
---------------------------------------------+-----------------------
 Reporter:  pbearne                          |       Owner:  flixos90
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------

Comment (by pbearne):

 Replying to [comment:10 superpoincare]:
 > This filter seems to be running twice.
 >
 > So if I modify the img tag, like add some attribute, it will be added
 twice.

 Can you share the code that runs this twice?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 15:35:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 15:35:51 -0000
Subject: [wp-trac] [WordPress Trac] #54239: tests for
 wp_fuzzy_number_match
In-Reply-To: <051.62c9969ea7921f6ca8e6a74dacabcadb@wordpress.org>
References: <051.62c9969ea7921f6ca8e6a74dacabcadb@wordpress.org>
Message-ID: <066.187fb4a83096f70932bef40959c81e22@wordpress.org>

#54239: tests for wp_fuzzy_number_match
-------------------------------------------------+-------------------------
 Reporter:  pbearne                              |       Owner:
                                                 |  hellofromTonya
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Build/Test Tools                     |     Version:  5.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  refresh                                        |
-------------------------------------------------+-------------------------

Comment (by pbearne):

 I am working on this

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54239#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 15:37:47 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 15:37:47 -0000
Subject: [wp-trac] [WordPress Trac] #51170: FTP automatic updates are
 not RFC 959 compliant for NLST command
In-Reply-To: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
References: <051.09b6bf2c60c82933c8667a9375698057@wordpress.org>
Message-ID: <066.68ac7dce1fb78506bfa2ee9dcc1f2999@wordpress.org>

#51170: FTP automatic updates are not RFC 959 compliant for NLST command
----------------------------+-----------------------
 Reporter:  giox069         |       Owner:  afragen
     Type:  defect (bug)    |      Status:  assigned
 Priority:  normal          |   Milestone:  6.0
Component:  Filesystem API  |     Version:  3.7
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+-----------------------

Comment (by costdev):

 [https://github.com/WordPress/wordpress-develop/pull/2460 PR 2460] has now
 been tested using vsftpd, Filezilla server and PureFTP.

 In all three cases, the PR returns the expected results:

 ||= **Test** =||= **Result** =||
 || A directory that exists || true ||
 || An empty hidden file || true ||
 || A non-empty hidden file || true ||
 || An empty file || true ||
 || A non-empty file || true ||
 || A directory that does not exist || false ||
 || A file that does not exist || false ||

 If passed a directory path, the PR uses the relative `::is_dir()` method
 to check for an existing directory.

 - If this passes, it returns `true` for an existing directory.
 - If it fails, it uses `ftp_rawlist()` to check for a file.

 When using `ftp_rawlist()` on a path that doesn't exist, some FTP servers
 will return `false`, others will return an empty array. The PR uses a
 falsy check to cover both of these instances.

 -----
 `ftp_rawlist()` uses the FTP "LIST" command. Per RFC 959:
  This command causes a list to be sent from the server to the passive DTP.
 If the pathname specifies a directory or other group of files, the server
 should transfer a list of files in the specified directory.  **If the
 pathname specifies a file then the server should send current information
 on the file**.

 (my emphasis)

 `ftp_rawlist()` is called without passing the `-a` flag, used to include
 hidden files, which had caused issues in attempts to patch this issue in
 previous tickets. In testing, it became apparent that Filezilla Server
 doesn't support adding the flag, and already shows hidden files.
 -----
 After successful testing using three different pieces of FTP server
 software, on both the `WP_Filesystem_FTPext` and
 `WP_Filesystem_ftpsockets` filesystem methods, this looks ready for
 `commit` to me.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51170#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 15:38:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 15:38:49 -0000
Subject: [wp-trac] [WordPress Trac] #55503: Post Date display issue if
 we set empty from General Settings page
In-Reply-To: <053.b21b3a6386e31f62eaf63a305e719594@wordpress.org>
References: <053.b21b3a6386e31f62eaf63a305e719594@wordpress.org>
Message-ID: <068.8c0d1da906280bc5071daaa55f5cc024@wordpress.org>

#55503: Post Date display issue if we set empty from General Settings page
--------------------------+------------------------------
 Reporter:  rishishah     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Date/Time     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  administration
--------------------------+------------------------------
Changes (by SergeyBiryukov):

 * component:  Administration => Date/Time


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55503#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 15:51:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 15:51:09 -0000
Subject: [wp-trac] [WordPress Trac] #55499: $pagenow is used but not
 define in documentation of this function
 add_customize_screen_to_heartbeat_settings()
In-Reply-To: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
References: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
Message-ID: <068.159eb8f590a8aac5bfe3f8a6a03aac26@wordpress.org>

#55499: $pagenow is used but not define in documentation of this function
add_customize_screen_to_heartbeat_settings()
-------------------------------------+------------------------------
 Reporter:  jontyravi                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  General                  |     Version:  5.8
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  docs
-------------------------------------+------------------------------
Changes (by kebbet):

 * keywords:  has-patch => has-patch needs-refresh


Comment:

 A search for `string $pagenow` in the `src`-directory gives that `global`
 variables should be declared between the `since`-tag and the `param`-tags
 in the docblock.

 Something like
 {{{
 * Filters heartbeat settings for the Customizer.
 *
 * @since 4.9.0
 *
 * @global string $pagenow Description
 *
 * @param array $settings Current settings to filter.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55499#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 15:57:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 15:57:50 -0000
Subject: [wp-trac] [WordPress Trac] #55502: Spacing Issue of Input field
 Under Mobile Device
In-Reply-To: <053.9eb4742680fd10cf5ecb3ab8db9dc266@wordpress.org>
References: <053.9eb4742680fd10cf5ecb3ab8db9dc266@wordpress.org>
Message-ID: <068.1ac14e552bb1971ba55c3c26d1328570@wordpress.org>

#55502: Spacing Issue of Input field Under Mobile Device
----------------------------+---------------------------------
 Reporter:  tejas5989       |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Administration  |     Version:  5.9.2
 Severity:  normal          |  Resolution:  duplicate
 Keywords:  has-patch       |     Focuses:  ui, administration
----------------------------+---------------------------------
Changes (by sabernhardt):

 * status:  new => closed
 * resolution:   => duplicate
 * component:  General => Administration
 * milestone:  Awaiting Review =>


Comment:

 Thanks for the report!

 This issue already has ticket #50177, and the change should be included in
 WordPress 6.0.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55502#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 16:17:01 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 16:17:01 -0000
Subject: [wp-trac] [WordPress Trac] #55499: $pagenow is used but not
 define in documentation of this function
 add_customize_screen_to_heartbeat_settings()
In-Reply-To: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
References: <053.d973e53e11c67a0499e608bd6b3a847e@wordpress.org>
Message-ID: <068.45ed6a7f4e292dd770643b9d19ceabfa@wordpress.org>

#55499: $pagenow is used but not define in documentation of this function
add_customize_screen_to_heartbeat_settings()
-------------------------------------+------------------------------
 Reporter:  jontyravi                |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  General                  |     Version:  4.9
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  docs
-------------------------------------+------------------------------
Changes (by kebbet):

 * version:  5.8 => 4.9


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55499#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 16:24:50 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 16:24:50 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.ead34ce3d6b829f268f27105e2e16a14@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
---------------------------------------------+-----------------------
 Reporter:  pbearne                          |       Owner:  flixos90
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------

Comment (by superpoincare):

 Hi @pbearne,

 Something like:

 {{{#!php
 <?php
 add_filter( 'wp_content_img_tag', function( $filtered_image ) {
         return "<tag>$filtered_image</tag>";
 } );
 }}}

 leads to:


 {{{
 <tag><tag><img src="https://demo2.cloudwp.dev/trial-3z1wywz1/wp-
 content/themes/twentytwentytwo/assets/images/flight-path-on-
 transparent-d.png" alt="Illustration of a bird flying."/></tag></tag>
 }}}

 in HTML.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 16:33:26 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 16:33:26 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.ea395f880e959cbfe17c2f83378ba190@wordpress.org>

#41136: Login forms lacking autocomplete attributes
-------------------------------------+-------------------------------------
 Reporter:  johnjamesjacoby          |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Login and Registration   |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-testing has-patch  |     Focuses:  accessibility,
  commit                             |  administration
-------------------------------------+-------------------------------------
Changes (by joedolson):

 * keywords:  needs-testing has-patch => needs-testing has-patch commit


Comment:

 That works for me.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 16:34:31 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 16:34:31 -0000
Subject: [wp-trac] [WordPress Trac] #54239: tests for
 wp_fuzzy_number_match
In-Reply-To: <051.62c9969ea7921f6ca8e6a74dacabcadb@wordpress.org>
References: <051.62c9969ea7921f6ca8e6a74dacabcadb@wordpress.org>
Message-ID: <066.7561629a5837829f9140b08ace191f56@wordpress.org>

#54239: tests for wp_fuzzy_number_match
--------------------------------------+-----------------------------
 Reporter:  pbearne                   |       Owner:  hellofromTonya
     Type:  defect (bug)              |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.0
Component:  Build/Test Tools          |     Version:  5.3
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------------

Comment (by pbearne):

 refreshed
 the merge from trunk broke it so I created a new PR

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54239#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 16:37:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 16:37:05 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.129bc3198f4baafe35fe93e8cdfa9bd4@wordpress.org>

#41136: Login forms lacking autocomplete attributes
------------------------------+--------------------------------------------
 Reporter:  johnjamesjacoby   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:  6.0
Component:  Login and         |     Version:
  Registration                |
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  accessibility, administration
------------------------------+--------------------------------------------
Changes (by joedolson):

 * keywords:  needs-testing has-patch commit => has-patch commit


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:21>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 16:39:24 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 16:39:24 -0000
Subject: [wp-trac] [WordPress Trac] #13459: Conflict between post and
 page slugs/permalinks when permalink setting is set to /%postname%/
In-Reply-To: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
References: <056.ab0c26cb7cfc7d43db5ebede27ea6cdb@wordpress.org>
Message-ID: <071.1ff2247e328329dfd099c7252c32d19c@wordpress.org>

#13459: Conflict between post and page slugs/permalinks when permalink setting is
set to /%postname%/
--------------------------+-----------------------------
 Reporter:  jamescollins  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Permalinks    |     Version:  2.9.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------

Comment (by bobbingwide):

 I've written some round trip black box PHPUnit tests demonstrating two
 problems.

 See https://github.com/bobbingwide/dupes where you'll find the tests and
 notes on how to run them. They rely on `wp_remote_get()` actually
 requesting the content for the permalink and then seeing if it got what it
 was asking for.

 The tests currently produce two failures.

 1. The original problem, where the duplicate page is returned instead of
 the post.
 2. The inability to retrieve the post by its post ID, when there's a
 duplicate page.

 There are other failing scenarios for which I've not yet written tests.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/13459#comment:73>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 16:41:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 16:41:44 -0000
Subject: [wp-trac] [WordPress Trac] #55503: Post Date display issue if
 we set empty from General Settings page
In-Reply-To: <053.b21b3a6386e31f62eaf63a305e719594@wordpress.org>
References: <053.b21b3a6386e31f62eaf63a305e719594@wordpress.org>
Message-ID: <068.7a4b764bae2c3428990b80a4abbd2fd1@wordpress.org>

#55503: Post Date display issue if we set empty from General Settings page
--------------------------+------------------------------
 Reporter:  rishishah     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Date/Time     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  administration
--------------------------+------------------------------

Comment (by Rarst):

 Technically empty string ''is'' a valid date format. I would be wary of
 introducing a special case for it, given it is long established feature
 and upstream PHP functions do not act like that.

 Also I am not sure anyone in the wild uses it to blank output
 ''purposely'', but can't be sure they are not either.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55503#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 16:59:46 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 16:59:46 -0000
Subject: [wp-trac] [WordPress Trac] #55505: Update @wordpress packages and
 backport changes from Gutenberg plugin into Core
Message-ID: <058.582086e8dab2e8797c9df68a699142c9@wordpress.org>

#55505: Update @wordpress packages and backport changes from Gutenberg plugin into
Core
----------------------------+--------------------
 Reporter:  hellofromTonya  |      Owner:  (none)
     Type:  task (blessed)  |     Status:  new
 Priority:  normal          |  Milestone:  6.0
Component:  Editor          |    Version:
 Severity:  normal          |   Keywords:
  Focuses:                  |
----------------------------+--------------------
 - Update `@wordpress` packages with packages published from Gutenberg.
 - Backport PHP changes from Gutenberg's `lib/compat/wordpress-6.0/` files.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55505>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 17:04:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 17:04:30 -0000
Subject: [wp-trac] [WordPress Trac] #43886: Chrome autofills password
 over "new password" field when updating user.
In-Reply-To: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
References: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
Message-ID: <070.1c023b8497713d198b892c81c9ca0db8@wordpress.org>

#43886: Chrome autofills password over "new password" field when updating user.
-------------------------+-----------------------------
 Reporter:  WraithKenny  |       Owner:  joedolson
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  administration
-------------------------+-----------------------------
Changes (by joedolson):

 * owner:  (none) => joedolson
 * status:  new => accepted


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43886#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 17:05:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 17:05:53 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.760f2e2532d2d7334caef92213d6d3e1@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
---------------------------------------------+-----------------------
 Reporter:  pbearne                          |       Owner:  flixos90
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------

Comment (by pbearne):

 I added another unit test
 I am not seeing this issue
 So we check the function is not being called twice

 {{{#!php
 <?php
         public function test_wp_filter_content_tag_test() {
                 $content = '<p>Image, standard. Should have srcset and
 sizes.</p>
                         <img src="http://url.tld" alt="" />';
                 add_filter(
                         'wp_content_img_tag',
                         static function( $filtered_image ) {
                                 return "<tag>$filtered_image</tag>";
                         }
                 );
                 $this->assertSame( '<p>Image, standard. Should have srcset
 and sizes.</p>
                         <tag><img src="http://url.tld" alt="" /></tag>',
 wp_filter_content_tags( $content ) );
         }
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 17:06:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 17:06:43 -0000
Subject: [wp-trac] [WordPress Trac] #55506: HTML tags not escaped
Message-ID: <056.dd5d8c909551f713d24e56527523721b@wordpress.org>

#55506: HTML tags not escaped
--------------------------------+-----------------------------
 Reporter:  gvgvgvijayan        |      Owner:  (none)
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  WordPress.org Site  |    Version:  5.9
 Severity:  normal              |   Keywords:
  Focuses:  docs                |
--------------------------------+-----------------------------
 https://developer.wordpress.org/reference/since/5.9.0/page/3/

 https://imgur.com/a/Gebwf2z

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55506>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 17:07:21 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 17:07:21 -0000
Subject: [wp-trac] [WordPress Trac] #55506: HTML tags not escaped
In-Reply-To: <056.dd5d8c909551f713d24e56527523721b@wordpress.org>
References: <056.dd5d8c909551f713d24e56527523721b@wordpress.org>
Message-ID: <071.27697e754c8da44a0886b6b75ec7093a@wordpress.org>

#55506: HTML tags not escaped
--------------------------------+------------------------------
 Reporter:  gvgvgvijayan        |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  WordPress.org Site  |     Version:  5.9
 Severity:  normal              |  Resolution:
 Keywords:                      |     Focuses:  docs
--------------------------------+------------------------------
Changes (by gvgvgvijayan):

 * Attachment "html-broken.png" added.


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55506>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 17:11:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 17:11:51 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.7da133d0ab5ad01c68cfe55774c54d36@wordpress.org>

#41136: Login forms lacking autocomplete attributes
------------------------------+--------------------------------------------
 Reporter:  johnjamesjacoby   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  6.0
Component:  Login and         |     Version:
  Registration                |
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:  accessibility, administration
------------------------------+--------------------------------------------
Changes (by joedolson):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 In [changeset:"53041" 53041]:
 {{{
 #!CommitTicketReference repository="" revision="53041"
 Login and Registration: Add autocomplete attributes.

 Set valid autocomplete attributes for registration and login fields for
 username, email, and current password. Autocomplete values are required in
 WCAG 2.1 at level AA for login forms.

 Props johnjamesjacoby, dhanendran, rianrietveld, joedolson, peterwilsoncc.
 Fixes #41136.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 17:23:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 17:23:17 -0000
Subject: [wp-trac] [WordPress Trac] #43886: Chrome autofills password
 over "new password" field when updating user.
In-Reply-To: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
References: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
Message-ID: <070.aed8f72cac58465bf2100eb7cb92b6d9@wordpress.org>

#43886: Chrome autofills password over "new password" field when updating user.
-------------------------+--------------------------------------------
 Reporter:  WraithKenny  |       Owner:  joedolson
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  accessibility, administration
-------------------------+--------------------------------------------
Changes (by joedolson):

 * focuses:  administration => accessibility, administration


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43886#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 17:36:33 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 17:36:33 -0000
Subject: [wp-trac] [WordPress Trac] #43886: Chrome autofills password
 over "new password" field when updating user.
In-Reply-To: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
References: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
Message-ID: <070.1b7c4d11f8fedb3bbb299af2696571b2@wordpress.org>

#43886: Chrome autofills password over "new password" field when updating user.
-------------------------+--------------------------------------------
 Reporter:  WraithKenny  |       Owner:  joedolson
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  accessibility, administration
-------------------------+--------------------------------------------

Comment (by joedolson):

 Looking at the [https://github.com/WordPress/wordpress-
 develop/pull/2273/files#r831768359 PR and the comments on it], I think
 this is mostly good; but in my opinion the database password field needs
 to be left as autocomplete="off".

 The database password is mostly a one-time use password, and unlikely to
 be represented in a user's keychain, so 'current-password' is most likely
 to suggest an invalid password, if it offers anything, and I don't believe
 'new-password' would ever offer a valid suggestion, since this is not a
 password-generating field.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43886#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 17:37:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 17:37:16 -0000
Subject: [wp-trac] [WordPress Trac] #55480: Add filter to modify
 description in plugin card
In-Reply-To: <051.94a4e115d6db28b6e051abfb65a2ef2b@wordpress.org>
References: <051.94a4e115d6db28b6e051abfb65a2ef2b@wordpress.org>
Message-ID: <066.872baab321b6012b65a6d4849773e352@wordpress.org>

#55480: Add filter to modify description in plugin card
-----------------------------+-----------------------------
 Reporter:  afragen          |       Owner:  SergeyBiryukov
     Type:  enhancement      |      Status:  reviewing
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:  administration
-----------------------------+-----------------------------
Changes (by SergeyBiryukov):

 * owner:  (none) => SergeyBiryukov
 * status:  new => reviewing
 * milestone:  Awaiting Review => 6.0


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55480#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 17:43:43 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 17:43:43 -0000
Subject: [wp-trac] [WordPress Trac] #43886: Chrome autofills password
 over "new password" field when updating user.
In-Reply-To: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
References: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
Message-ID: <070.c9f116afcaf5f27287e823bcf81f52c7@wordpress.org>

#43886: Chrome autofills password over "new password" field when updating user.
-------------------------+--------------------------------------------
 Reporter:  WraithKenny  |       Owner:  joedolson
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  accessibility, administration
-------------------------+--------------------------------------------
Changes (by joedolson):

 * Attachment "43886.2.diff" added.

 Patch refreshed; database password change removed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43886>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 18:25:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 18:25:45 -0000
Subject: [wp-trac] [WordPress Trac] #55507: CSS Fix required in
 twenty-twenty-two.css to prevent overflow issue with single product layouts
 when using WooCommerce
Message-ID: <049.f51a3a4bc05c69379eb787fbddc59337@wordpress.org>

#55507: CSS Fix required in twenty-twenty-two.css to prevent overflow issue with
single product layouts when using WooCommerce
--------------------------+-----------------------------
 Reporter:  1wdtv         |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Themes        |    Version:  5.9.2
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Twenty-TwentyTwo Theme needs a tweak to the css for the following class to
 prevent any WooCommerce single product from causing an overflow issue.

 This css rule needs the addition of "overflow:hidden", as shown below


 {{{
 .woocommerce div.product {
     position: relative;
     max-width: 1000px;
     overflow: hidden;
 }
 }}}


 Otherwise, the layout looks as follows:
 https://i.gyazo.com/1b2597db9b8383c3c0e573bf277fa269.png

 When overflow:hidden is added, site properly displays single product as
 follows:
 https://i.gyazo.com/30bf8a7ac31e815aac94be726fbce565.png

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55507>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 18:33:00 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 18:33:00 -0000
Subject: [wp-trac] [WordPress Trac] #41136: Login forms lacking
 autocomplete attributes
In-Reply-To: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
References: <059.8e5606699c311e328445f1f39444e32a@wordpress.org>
Message-ID: <074.59d2255af518829d4a04eca86a7282f2@wordpress.org>

#41136: Login forms lacking autocomplete attributes
------------------------------+--------------------------------------------
 Reporter:  johnjamesjacoby   |       Owner:  joedolson
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  6.0
Component:  Login and         |     Version:
  Registration                |
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:  accessibility, administration
------------------------------+--------------------------------------------

Comment (by rianrietveld):

 Thank you!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/41136#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 19:13:02 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 19:13:02 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.de766abf58b0e5f2280b4d4a6128da05@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
 Reporter:  ademos                    |       Owner:  marybaum
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+------------------------------

Comment (by joedolson):

 Currently, bulk editing is done on a model where all values are empty by
 default, and submission of additional data is added to posts (if that data
 has multiple instances, e.g. categories/tags) or replaced (if it's unique,
 e.g. author/status).

 Having any of the current data for the selected posts makes this
 considerably more complex, as the form would now need to fetch data for
 every selected post and compare the data for all tags & categories. That's
 trivial if we're comparing three posts, a couple taxonomies, and each
 taxonomy has a couple dozen elements, but I have some doubts about the
 scalability.

 I do think it's a weakness that there's no option to remove terms in bulk
 editing, however. I think we should be looking at a context-insensitive
 interface for bulk removing terms.

 The current interface is dedicated to adding new terms to selected posts.
 If we added an option to toggle the action those fields perform - e.g., a
 checkbox that switches the behavior to 'Remove Categories' or 'Remove
 Tags', then we could avoid needing to identify which terms were common
 between all the selected posts.

 We still wouldn't be able to simultaneously remove and add terms in bulk
 edit, but it would be a significant improvement over what we have now.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859#comment:45>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 19:13:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 19:13:41 -0000
Subject: [wp-trac] [WordPress Trac] #19859: "Bulk Edit" Missing The
 Ability To Edit Tags
In-Reply-To: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
References: <050.2b0195c1ae7131e635a9bdfdd387968b@wordpress.org>
Message-ID: <065.7695f1aa4f1b398171fed7ad7ed16d73@wordpress.org>

#19859: "Bulk Edit" Missing The Ability To Edit Tags
--------------------------------------+------------------------------
 Reporter:  ademos                    |       Owner:  marybaum
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Quick/Bulk Edit           |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  needs-patch needs-design  |     Focuses:
--------------------------------------+------------------------------
Changes (by joedolson):

 * Attachment "19859-mockup.png" added.

 Mockup showing 'remove selected' option

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19859>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 19:32:19 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 19:32:19 -0000
Subject: [wp-trac] [WordPress Trac] #55484: class-wp-editor.php line 1697
In-Reply-To: <050.6482079791df9a6ae016d9a05467fef2@wordpress.org>
References: <050.6482079791df9a6ae016d9a05467fef2@wordpress.org>
Message-ID: <065.6d6a3b785d965eba96638386970eec93@wordpress.org>

#55484: class-wp-editor.php line 1697
--------------------------+------------------------------
 Reporter:  karin2        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  5.9.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  javascript
--------------------------+------------------------------

Comment (by karin2):

 Keep in mind that all JavaScript for this area is compressed into one
 line. Thus causing the error.

 **Code causing error:**
 ----
 var initialize = function(){...}if (typeof tinymce !== 'undefined'){...
 ----

 **Browsers tested:**

 Firefox:
 98.0.2 (64-bit)
 ----
 Uncaught SyntaxError: unexpected token: keyword 'if'
 ----


 Chrome
 100.0.4896.60 (64-bit)
 ----
 Uncaught SyntaxError: Unexpected token 'if'
 ----

 Most likely all other browsers as well. Since when the JavaScript is
 compressed, ie: one line, there is no semicolon to define the ending of
 the statement.

 Portions of the TinyMCE editor is broken, as well. Endless loader and the
 TinyMCE buttons are not displayed.
 When the semicolon is applied, as below, the error is gone and everything
 is working.

 **The Fix: (Adding Semicolon)**
 ----
 var initialize = function(){....};if (typeof tinymce !== 'undefined'){....
 ----

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55484#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 19:50:44 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 19:50:44 -0000
Subject: [wp-trac] [WordPress Trac] #52714: Add New User Autofill Bug
In-Reply-To: <054.9df492b8b2e085ae076fb5ca2a33644c@wordpress.org>
References: <054.9df492b8b2e085ae076fb5ca2a33644c@wordpress.org>
Message-ID: <069.b760b398720ef45528e6886fae2faf85@wordpress.org>

#52714: Add New User Autofill Bug
-------------------------------------------------+-------------------------
 Reporter:  clonemykey                           |       Owner:
                                                 |  davidbaumwald
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Users                                |     Version:  5.6.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing assigned-    |     Focuses:  ui,
  for-commit                                     |  administration
-------------------------------------------------+-------------------------

Comment (by sabernhardt):

 The latest patch on #43886 includes the `new-password` values on the New
 User page (but not the `off` value for the username).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52714#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 19:52:48 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 19:52:48 -0000
Subject: [wp-trac] [WordPress Trac] #43886: Chrome autofills password
 over "new password" field when updating user.
In-Reply-To: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
References: <055.006b0bba2d633bb6a2d027bd96a73036@wordpress.org>
Message-ID: <070.bf6b4631e7532432bef9cf47d01b0044@wordpress.org>

#43886: Chrome autofills password over "new password" field when updating user.
-------------------------+--------------------------------------------
 Reporter:  WraithKenny  |       Owner:  joedolson
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:  6.0
Component:  Users        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  accessibility, administration
-------------------------+--------------------------------------------

Comment (by sabernhardt):

 [attachment:"43886.2.diff"] includes the New User page. If no further
 change is necessary for #52714, both tickets could be closed with the same
 commit.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43886#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 20:17:56 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 20:17:56 -0000
Subject: [wp-trac] [WordPress Trac] #55506: HTML tags not escaped
In-Reply-To: <056.dd5d8c909551f713d24e56527523721b@wordpress.org>
References: <056.dd5d8c909551f713d24e56527523721b@wordpress.org>
Message-ID: <071.a8bad52b7d87cc240bece69e3deb3ec7@wordpress.org>

#55506: HTML tags not escaped
--------------------------------+------------------------------
 Reporter:  gvgvgvijayan        |       Owner:  (none)
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  WordPress.org Site  |     Version:  5.9
 Severity:  normal              |  Resolution:
 Keywords:  2nd-opinion         |     Focuses:  docs
--------------------------------+------------------------------
Changes (by azouamauriac):

 * keywords:   => 2nd-opinion


Comment:

 Hi there, welcome to core trac; thanks for the report;

 Seems like the right place to report this kind of issue is
 [https://meta.trac.wordpress.org/newticket here].
 RE: [https://prnt.sc/VTo81CkFK-nu]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55506#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 20:20:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 20:20:42 -0000
Subject: [wp-trac] [WordPress Trac] #48222: "Show password" button
 overlaps with the LastPass icon
In-Reply-To: <058.0d699b3273d056c061d95a9b99cee6c0@wordpress.org>
References: <058.0d699b3273d056c061d95a9b99cee6c0@wordpress.org>
Message-ID: <073.dbefe9f0e1d85ba39dea7f0711df9430@wordpress.org>

#48222: "Show password" button overlaps with the LastPass icon
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:
                                                 |  sabernhardt
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Login and Registration               |     Version:  5.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-screenshots has-patch needs-     |     Focuses:  ui
  design-feedback early needs-refresh            |
-------------------------------------------------+-------------------------
Changes (by sabernhardt):

 * keywords:  has-screenshots has-patch needs-design-feedback needs-testing
     early => has-screenshots has-patch needs-design-feedback early needs-
     refresh
 * type:  defect (bug) => enhancement


Comment:

 The patch needs to reflect the new `autocomplete` values, and would need
 further revisions to make the login toggle button consistent with the
 profile page and potential new uses on setup-config.php and options-
 writing.php (#3534 and #9883).

 Changing the type to enhancement since this is well beyond the original
 scope of a bugfix.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48222#comment:68>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 20:38:03 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 20:38:03 -0000
Subject: [wp-trac] [WordPress Trac] #19901: Speeding up Dashboard and
 Comment moderation SQL load
In-Reply-To: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
References: <055.c7fb7faa472b1f2f74d793cc24af5d1c@wordpress.org>
Message-ID: <070.5cc6185fc8545a732dac05f768c5c202@wordpress.org>

#19901: Speeding up Dashboard and Comment moderation SQL load
-------------------------------------------------+-------------------------
 Reporter:  FolioVision                          |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Comments                             |     Version:  3.3
 Severity:  major                                |  Resolution:  fixed
 Keywords:  needs-testing has-patch commit       |     Focuses:
  assigned-for-commit                            |  performance
-------------------------------------------------+-------------------------

Comment (by johnbillion):

 Trivia: With this optimisation now in place, some WordPress admin screens
 will perform zero database queries when a persistent object cache is in
 use and the cache is warm. Neat.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/19901#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 20:45:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 20:45:29 -0000
Subject: [wp-trac] [WordPress Trac] #55070: Image Editing Cropping is
 not working properly
In-Reply-To: <051.999fb09cf1346fd9db383fea344080be@wordpress.org>
References: <051.999fb09cf1346fd9db383fea344080be@wordpress.org>
Message-ID: <066.908ed216b6b18984521ee25d46ee5357@wordpress.org>

#55070: Image Editing Cropping is not working properly
--------------------------+---------------------
 Reporter:  andy786       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.0
Component:  Media         |     Version:  5.9
 Severity:  critical      |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------

Comment (by antonvlasenko):

 Steps to test this PR:
 1. Upload a relatively large image to the Media Gallery (at least 2000x
 1500 pixels). It's just easier to test this issue with a bigger image.
 2. Click on the image.
 3. Click on the "Edit Image" button below the image.
 4. Crop the image (using the "Crop" button above the image).
 5. A cropped image should be about 400 x 400 pixels in size. Either width
 or height of the cropped image must not exceed 767 pixels.
 6. Save the cropped image (click on the "Save" button).
 7. You should be able to see the cropped image. Before the fix, WordPress
 would display the original image and not the cropped one.
 8. [Additional step] You can crop the image again and observe that it's
 displayed correctly.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55070#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 21:20:08 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 21:20:08 -0000
Subject: [wp-trac] [WordPress Trac] #55508: Floating links in Save postbox
Message-ID: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>

#55508: Floating links in Save postbox
--------------------------+-----------------------------
 Reporter:  sabernhardt   |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Media         |    Version:
 Severity:  normal        |   Keywords:  needs-patch
  Focuses:  css           |
--------------------------+-----------------------------
 When on smaller screens, links for "Uploaded by" and "Uploaded to" float
 to the opposite side of the text.

 {{{
         .misc-pub-section > a {
                 float: right;
                 font-size: 16px;
         }
 }}}

 Screenshot from @sumitsingh (#54811):

 [[Image(https://core.trac.wordpress.org/raw-
 attachment/ticket/54811/Screenshot_2022-01-13-19-05-27-776_com.android.chrome.jpg)]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55508>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 21:20:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 21:20:57 -0000
Subject: [wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and
 use for output
In-Reply-To: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
References: <059.ca56f5c85c01a14ae68fdc38f60b9c06@wordpress.org>
Message-ID: <074.a626b95a20367aad767759d08afddd3e@wordpress.org>

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.0
Component:  Media                                |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-dev-note needs-docs needs-codex  |  performance
-------------------------------------------------+-------------------------

Comment (by eatingrules):

 Replying to [comment:14 markhowellsmead]:
 > enforcing WebP by default on sites which use a lot of photography will
 often cause longer image loading times.

 This is just one of many reasons why this feature should not be in core.

 There is strong, legitimate opposition to this proposal being shared in
 [https://make.wordpress.org/core/2022/03/28/enabling-webp-by-default/: the
 announcement blog post comments]  - I won't repeat them here, but I hope
 everyone will click over to see that discussion.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 21:24:16 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 21:24:16 -0000
Subject: [wp-trac] [WordPress Trac] #55508: Floating links in Save
 postbox
In-Reply-To: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
References: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
Message-ID: <070.f9ee6068d36703acac75bda453103703@wordpress.org>

#55508: Floating links in Save postbox
--------------------------+------------------------------
 Reporter:  sabernhardt   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  css
--------------------------+------------------------------

Comment (by joedolson):

 See #54811 for related issue. Probably can solve in a single patch.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55508#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 21:24:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 21:24:49 -0000
Subject: [wp-trac] [WordPress Trac] #55508: Floating links in Save
 postbox
In-Reply-To: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
References: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
Message-ID: <070.b698d754076746a99d3344a1b52b6b58@wordpress.org>

#55508: Floating links in Save postbox
--------------------------+------------------------------
 Reporter:  sabernhardt   |       Owner:  joedolson
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  css
--------------------------+------------------------------
Changes (by joedolson):

 * owner:  (none) => joedolson
 * status:  new => accepted


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55508#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 21:33:27 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 21:33:27 -0000
Subject: [wp-trac] [WordPress Trac] #55509: CSS conflict in Custom Fields
 table
Message-ID: <057.400e162815f03bec1006e511f146fb6b@wordpress.org>

#55509: CSS conflict in Custom Fields table
---------------------------+-----------------------------
 Reporter:  princeofabyss  |      Owner:  (none)
     Type:  defect (bug)   |     Status:  new
 Priority:  normal         |  Milestone:  Awaiting Review
Component:  General        |    Version:  5.9.1
 Severity:  normal         |   Keywords:
  Focuses:  css            |
---------------------------+-----------------------------
 When using the [https://wordpress.org/support/article/custom-fields/
 Custom Fields] feature, there are two conflicting CSS styles.

 More specifically the background-color in the following CSS bit:


 {{{
 #postcustomstuff table {
   margin: 0;
   width: 100%;
   border: 1px solid #dcdcde;
   border-spacing: 0;
   background-color: #f6f7f7;
 }
 }}}


 with the background-color in the following CSS bit:

 {{{

 .alternate, .striped > tbody > :nth-child(2n+1), ul.striped > :nth-
 child(2n+1) {
   background-color: #f6f7f7;
 }
 }}}


 resulting in all rows of the table in div#postcustomstuff to have the same
 background color (#f6f7f7)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55509>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 21:45:25 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 21:45:25 -0000
Subject: [wp-trac] [WordPress Trac] #54811: Complete media url is not
 showing.
In-Reply-To: <054.c79f56ec01ca32ba6f91f248193c9c6c@wordpress.org>
References: <054.c79f56ec01ca32ba6f91f248193c9c6c@wordpress.org>
Message-ID: <069.698966f9d76b7bc66689fe986b763d62@wordpress.org>

#54811: Complete media url is not showing.
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Media                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots          |     Focuses:  ui, accessibility,
  reporter-feedback                  |  administration
-------------------------------------+-------------------------------------
Changes (by sabernhardt):

 * Attachment "54811.diff" added.

 Adding `break-word` styles for sample permalink (on Posts, Media or
 Comments) as well as setting to `inline-block`

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54811>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 21:46:41 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 21:46:41 -0000
Subject: [wp-trac] [WordPress Trac] #54811: Complete media url is not
 showing.
In-Reply-To: <054.c79f56ec01ca32ba6f91f248193c9c6c@wordpress.org>
References: <054.c79f56ec01ca32ba6f91f248193c9c6c@wordpress.org>
Message-ID: <069.6cafb91592cb110adcc9183bed183341@wordpress.org>

#54811: Complete media url is not showing.
-------------------------------------+-------------------------------------
 Reporter:  sumitsingh               |       Owner:  joedolson
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Posts, Post Types        |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots has-     |     Focuses:  ui, accessibility,
  patch                              |  css, administration
-------------------------------------+-------------------------------------
Changes (by sabernhardt):

 * keywords:  has-screenshots reporter-feedback => has-screenshots has-patch
 * focuses:  ui, accessibility, administration => ui, accessibility, css,
     administration
 * component:  Media => Posts, Post Types


Comment:

 (The floating issue is on ticket #55508.)

 I thought of creating a `.break-word` class for the permalink plus the
 Original file name (#55393) and any other elements that might need it.

 On the other hand, I think the permalink could benefit from setting
 `display` to `inline-block`, which also would require a `max-width`.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54811#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 21:56:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 21:56:05 -0000
Subject: [wp-trac] [WordPress Trac] #55508: Floating links in Save
 postbox
In-Reply-To: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
References: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
Message-ID: <070.5961745e1680c0938561b95b4fe89b2e@wordpress.org>

#55508: Floating links in Save postbox
--------------------------+------------------------------
 Reporter:  sabernhardt   |       Owner:  joedolson
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  css
--------------------------+------------------------------
Changes (by sabernhardt):

 * Attachment "image-details-float-right.png" added.

 screenshot with both "Uploaded by" and "Uploaded to" links

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55508>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 21:56:54 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 21:56:54 -0000
Subject: [wp-trac] [WordPress Trac] #55508: Floating links in Save
 postbox
In-Reply-To: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
References: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
Message-ID: <070.9ed95a5d3b96394d3241e56a6c062ddd@wordpress.org>

#55508: Floating links in Save postbox
--------------------------+------------------------------
 Reporter:  sabernhardt   |       Owner:  joedolson
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  css
--------------------------+------------------------------
Changes (by sabernhardt):

 * Attachment "55508.diff" added.

 removing float and larger font size

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55508>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 22:10:49 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 22:10:49 -0000
Subject: [wp-trac] [WordPress Trac] #53705: Plugin upgrade deletes files
 from other in-progress upgrades
In-Reply-To: <051.3864d53d4c261f039340696626d8cf5c@wordpress.org>
References: <051.3864d53d4c261f039340696626d8cf5c@wordpress.org>
Message-ID: <066.fc207f153f652ad7afc64f717458eab4@wordpress.org>

#53705: Plugin upgrade deletes files from other in-progress upgrades
-----------------------------+---------------------
 Reporter:  bpayton          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.0
Component:  Upgrade/Install  |     Version:  5.8
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+---------------------

Comment (by bpayton):

 Replying to [comment:16 peterwilsoncc]:
 > Replying to [comment:6 bpayton]:
 > I've been thinking about this and don't think it's a wise idea.
 >
 > In terms of meeting the website owners expectations: this approach would
 leave unexpected files on the server in an unexpected location.
 >

 @peterwilsoncc, thank you for taking time to think about this.

 I agree that leaving unexpected files on a server is undesirable, but I
 don't believe this code bears primary responsibility for that cleanup.
 Here's my thinking:

 In general, WordPress attempts to cleanup working files after an upgrade
 is done or an error occurs.

 Core updates attempt to clean up working files. (refs:
 [https://github.com/WordPress/wordpress-
 develop/blob/16baa3877991d521cb69df712f1e1be9f61791bb/src/wp-
 admin/includes/class-core-upgrader.php#L157-L158 1],
 [https://github.com/WordPress/wordpress-
 develop/blob/16baa3877991d521cb69df712f1e1be9f61791bb/src/wp-
 admin/includes/update-core.php#L978-L979 2], [https://github.com/WordPress
 /wordpress-develop/blob/16baa3877991d521cb69df712f1e1be9f61791bb/src/wp-
 admin/includes/update-core.php#L992-L993 3], [https://github.com/WordPress
 /wordpress-develop/blob/16baa3877991d521cb69df712f1e1be9f61791bb/src/wp-
 admin/includes/update-core.php#L1027-L1028 4],
 [https://github.com/WordPress/wordpress-
 develop/blob/16baa3877991d521cb69df712f1e1be9f61791bb/src/wp-
 admin/includes/update-core.php#L1201-L1202 5],
 [https://github.com/WordPress/wordpress-
 develop/blob/16baa3877991d521cb69df712f1e1be9f61791bb/src/wp-
 admin/includes/update-core.php#L1392-L1393 6],
 [https://github.com/WordPress/wordpress-
 develop/blob/16baa3877991d521cb69df712f1e1be9f61791bb/src/wp-
 admin/includes/update-core.php#L1433-L1434 7])

 The WP_Upgrader class knows how to clean up after itself after installing
 a package. The WP_Upgrader::install_package() method takes a
 `clear_working` argument, and if that argument is truthy, the working
 files are [https://github.com/WordPress/wordpress-
 develop/blob/16baa3877991d521cb69df712f1e1be9f61791bb/src/wp-
 admin/includes/class-wp-upgrader.php#L604-L607 cleaned up after
 installation]. And it looks like `clear_working` is generally set to true:

 - WP_Upgrader::run() is the only method in core that calls
 WP_Upgrader::install_package(), and WP_Upgrader also takes a
 `clear_working` argument that defaults to true.
 - Plugin_Upgrader calls WP_Upgrader::run() three times and each call
 passes `"clear_working" => true`. (refs: [https://github.com/WordPress
 /wordpress-develop/blob/143df6e76363d59f9bbad1d33747a0ff8d05299e/src/wp-
 admin/includes/class-plugin-upgrader.php#L135 1],
 [https://github.com/WordPress/wordpress-
 develop/blob/143df6e76363d59f9bbad1d33747a0ff8d05299e/src/wp-
 admin/includes/class-plugin-upgrader.php#L222 2],
 [https://github.com/WordPress/wordpress-
 develop/blob/143df6e76363d59f9bbad1d33747a0ff8d05299e/src/wp-
 admin/includes/class-plugin-upgrader.php#L337 3])
 - Theme_Upgrader calls WP_Upgrader::run() four times and each call passes
 `"clear_working" => true`. (refs: [https://github.com/WordPress/wordpress-
 develop/blob/143df6e76363d59f9bbad1d33747a0ff8d05299e/src/wp-
 admin/includes/class-theme-upgrader.php#L173 1],
 [https://github.com/WordPress/wordpress-
 develop/blob/143df6e76363d59f9bbad1d33747a0ff8d05299e/src/wp-
 admin/includes/class-theme-upgrader.php#L248 2],
 [https://github.com/WordPress/wordpress-
 develop/blob/143df6e76363d59f9bbad1d33747a0ff8d05299e/src/wp-
 admin/includes/class-theme-upgrader.php#L324 3],
 [https://github.com/WordPress/wordpress-
 develop/blob/143df6e76363d59f9bbad1d33747a0ff8d05299e/src/wp-
 admin/includes/class-theme-upgrader.php#L324 4])
 - Language_Pack_Upgrader calls WP_Upgrader::run() once and passes
 `"clear_working" => true`. (ref: [https://github.com/WordPress/wordpress-
 develop/blob/143df6e76363d59f9bbad1d33747a0ff8d05299e/src/wp-
 admin/includes/class-language-pack-upgrader.php#L243-L256 1])

 I believe this shows that [https://github.com/WordPress/wordpress-
 develop/blob/trunk/src/wp-admin/includes/class-wp-upgrader.php#L312-L318
 the cleanup code in question here] is a second line of defense, where
 WordPress takes the opportunity to clean up working files that should have
 been cleaned up earlier.

 If that is true, I think it is probably reasonable for this second line of
 defense to only clean up working files that are past a certain age. It
 honestly seems like the safer thing to do since __this code naturally does
 not know why the working files are there to begin with, and that lack of
 knowledge is the source of this bug__.

 Does this make sense, and if so, does it influence your thinking at all on
 [https://core.trac.wordpress.org/attachment/ticket/53705/avoid-corrupting-
 concurrent-plugin-upgrades.diff the only-delete-older-working-files
 patch]?

 In case it helps, I think the patch could be adjusted to clean up files
 that are older than an hour or even a number of minutes. In retrospect,
 requiring files to be over a day old seems excessive.

 >
 > If the file names are predictable then a more targeted delete while
 preparing for the upgrade could be a better solution.

 Since this cleanup code assumes all pre-existing working files are left
 over and need to be cleaned up, I'm not sure how better naming would
 prevent it from removing things that are in the process of being
 installed. Would you be up for explaining further?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53705#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 22:12:20 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 22:12:20 -0000
Subject: [wp-trac] [WordPress Trac] #53028: Inconsistent Capitalisation
In-Reply-To: <053.7a5028a140f27c5b08b94d28a92fcac2@wordpress.org>
References: <053.7a5028a140f27c5b08b94d28a92fcac2@wordpress.org>
Message-ID: <068.bcd0ec871347defe6c8e029f4b20a236@wordpress.org>

#53028: Inconsistent Capitalisation
-------------------------------------------------+-------------------------
 Reporter:  Presskopp                            |       Owner:  audrasjb
     Type:  defect (bug)                         |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.0
Component:  Text Changes                         |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-patch needs-      |     Focuses:  ui-copy
  refresh                                        |
-------------------------------------------------+-------------------------

Comment (by marybaum):

 AFter a cursory skim of the ticket, I'd break things down this way: leave
 it lower-case when talking about documentation as a concept, or a
 collective ("Please read the documentation!" and change to uppercase when
 we're talking about the Documentation Team ("For this release our
 Documentation Team reps suggested these people as leads.")

 @davidbaumwald does that capture your distinction between proper and non-
 proper nouns?

 (Seems to me improper nouns are the ones we don't say in family-friendly
 settings ;-D)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53028#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 22:18:57 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 22:18:57 -0000
Subject: [wp-trac] [WordPress Trac] #51383: PHP error body class added
 for suppressed errors
In-Reply-To: <051.123698ccf50d6de1ce079cfd9386be12@wordpress.org>
References: <051.123698ccf50d6de1ce079cfd9386be12@wordpress.org>
Message-ID: <066.4f979d10b70afcf0a2a3453dd5a90d10@wordpress.org>

#51383: PHP error body class added for suppressed errors
-------------------------------------+-----------------------------
 Reporter:  desrosj                  |       Owner:  hellofromTonya
     Type:  defect (bug)             |      Status:  reviewing
 Priority:  normal                   |   Milestone:  6.0
Component:  Administration           |     Version:  5.5
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+-----------------------------

Comment (by costdev):

 Per the discussion in the bug scrub, pinging @hellofromTonya to see if
 you've had time/have time to do the review on this?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51383#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 22:23:42 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 22:23:42 -0000
Subject: [wp-trac] [WordPress Trac] #51383: PHP error body class added
 for suppressed errors
In-Reply-To: <051.123698ccf50d6de1ce079cfd9386be12@wordpress.org>
References: <051.123698ccf50d6de1ce079cfd9386be12@wordpress.org>
Message-ID: <066.d888922ef2a12b087e2f5a8654b8c362@wordpress.org>

#51383: PHP error body class added for suppressed errors
-------------------------------------------------+-------------------------
 Reporter:  desrosj                              |       Owner:
                                                 |  hellofromTonya
     Type:  defect (bug)                         |      Status:  reviewing
 Priority:  normal                               |   Milestone:  6.0
Component:  Administration                       |     Version:  5.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing needs-       |     Focuses:
  refresh                                        |
-------------------------------------------------+-------------------------
Changes (by audrasjb):

 * keywords:  has-patch needs-testing => has-patch needs-testing needs-
               refresh


Comment:

 The patch doesn't apply anymore against trunk.
 I'm adding a PR right now :)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51383#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 22:28:45 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 22:28:45 -0000
Subject: [wp-trac] [WordPress Trac] #55508: Floating links in Save
 postbox
In-Reply-To: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
References: <055.dc5f69f8ac19b580719ae4e0e696b7ec@wordpress.org>
Message-ID: <070.4877ffe45d3a52c0655537ab039bf691@wordpress.org>

#55508: Floating links in Save postbox
--------------------------+------------------------------
 Reporter:  sabernhardt   |       Owner:  joedolson
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  css
--------------------------+------------------------------
Changes (by sabernhardt):

 * keywords:  needs-patch => has-patch


Comment:

 Floating the links on mobile started with r26134
 ([https://core.trac.wordpress.org/ticket/25858#comment:29
 25858.responsive.diff])

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55508#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 22:30:53 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 22:30:53 -0000
Subject: [wp-trac] [WordPress Trac] #52622: Fix PHP Warning on PHP7.2 in
 class-wp-http-curl.php
In-Reply-To: <057.c3a7b36a7a48782370cf5b1fd68bb9b5@wordpress.org>
References: <057.c3a7b36a7a48782370cf5b1fd68bb9b5@wordpress.org>
Message-ID: <072.27ea87db95fcb405efa1a14d07d72702@wordpress.org>

#52622: Fix PHP Warning on PHP7.2 in class-wp-http-curl.php
-------------------------------------+-------------------------------------
 Reporter:  sjoerdlinders            |       Owner:  SergeyBiryukov
     Type:  defect (bug)             |      Status:  reviewing
 Priority:  normal                   |   Milestone:  6.0
Component:  HTTP API                 |     Version:  5.6.2
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-unit-    |     Focuses:  administration,
  tests php8                         |  coding-standards
-------------------------------------+-------------------------------------

Comment (by costdev):

 This ticket was discussed in tonight's bug scrub. Has there been any
 progress with the discussion off-Trac?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52622#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 22:32:29 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 22:32:29 -0000
Subject: [wp-trac] [WordPress Trac] #55498: Permalink Settings Page
 Accessibility Improve
In-Reply-To: <053.06db99f017cbf7d27f8f904f21b948fd@wordpress.org>
References: <053.06db99f017cbf7d27f8f904f21b948fd@wordpress.org>
Message-ID: <068.9338cddb403153cf59fc40986ff0fd77@wordpress.org>

#55498: Permalink Settings Page Accessibility Improve
--------------------------+-------------------------------------
 Reporter:  rishishah     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Permalinks    |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  accessibility, ui-copy
--------------------------+-------------------------------------
Changes (by sabernhardt):

 * focuses:  accessibility => accessibility, ui-copy
 * component:  General => Permalinks
 * version:  trunk =>


Comment:

 Thanks for the report!

 Yes, that input needs a label, though it should describe the input better
 than the base URL does. "Custom Permalink Structure Tags" is one option,
 and I welcome other ideas.

 There are a few other considerations on this screen:
 - The radio buttons could have `aria-describedby` values connecting each
 to its example URL.
 - The radio button labels still wrap both the input and text (not
 separated, using `id` and `for`).
 - "Available tags:" could be a `legend` for a `fieldset` to group the
 related buttons.
 - I would like to wrap the custom text input plus its (probably non-
 visual) label and base URL within a `<span class="code"></div>` for better
 RTL support, which might fit well with #47755 instead.
 - When navigating by keyboard, editing the custom input value ''on
 changing'' the radio buttons can cause problems. This JS issue can be on
 its own ticket; I'm not sure about the others.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55498#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 22:33:51 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 22:33:51 -0000
Subject: [wp-trac] [WordPress Trac] #48393: Fix from #38903 prevents
 options autoload parameter update
In-Reply-To: <051.6e1b42bbb70ebebfa7f41864a2f376f1@wordpress.org>
References: <051.6e1b42bbb70ebebfa7f41864a2f376f1@wordpress.org>
Message-ID: <066.1b86acd989cba56ee368b30fc3901da9@wordpress.org>

#48393: Fix from #38903 prevents options autoload parameter update
-------------------------------------+-----------------------------
 Reporter:  aboltro                  |       Owner:  SergeyBiryukov
     Type:  defect (bug)             |      Status:  accepted
 Priority:  normal                   |   Milestone:  6.0
Component:  Options, Meta APIs       |     Version:
 Severity:  major                    |  Resolution:
 Keywords:  2nd-opinion needs-patch  |     Focuses:  administration
-------------------------------------+-----------------------------

Comment (by costdev):

 Per the discussion in the bug scrub, pinging @SergeyBiryukov to see if
 this ticket is still on your radar?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48393#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 22:43:09 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 22:43:09 -0000
Subject: [wp-trac] [WordPress Trac] #54915: Username,
 email and password fields must be ltr in rtl locale
In-Reply-To: <053.4f38abea21a29f9eb209358027b8e501@wordpress.org>
References: <053.4f38abea21a29f9eb209358027b8e501@wordpress.org>
Message-ID: <068.c5701c328a91c385eca8b0eacf167d70@wordpress.org>

#54915: Username, email and password fields must be ltr in rtl locale
-------------------------------------+-------------------------------------
 Reporter:  man4toman                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.0
Component:  Users                    |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots has-     |     Focuses:  ui, css, rtl,
  testing-info has-patch needs-      |  administration
  refresh                            |
-------------------------------------+-------------------------------------
Changes (by sabernhardt):

 * keywords:  has-screenshots has-testing-info has-patch => has-screenshots
     has-testing-info has-patch needs-refresh


-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/54915#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 23:24:23 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 23:24:23 -0000
Subject: [wp-trac] [WordPress Trac] #55347: There should be filter for
 image tag in wp_filter_content_tags()
In-Reply-To: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
References: <051.4c28ae614b265b131f10f373a6050f15@wordpress.org>
Message-ID: <066.1d209b076ab42f65e4dd162ec0187272@wordpress.org>

#55347: There should be filter for image tag in wp_filter_content_tags()
---------------------------------------------+-----------------------
 Reporter:  pbearne                          |       Owner:  flixos90
     Type:  enhancement                      |      Status:  closed
 Priority:  normal                           |   Milestone:  6.0
Component:  Media                            |     Version:
 Severity:  normal                           |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit  |     Focuses:
---------------------------------------------+-----------------------

Comment (by peterwilsoncc):

 I was able to reproduce the issue @superpoincare reports:

 The issue occurs when an identical image tag appears in `the_content`
 twice and either of the following are true:

 * the image includes each of the attributes WP Core adds by default,
 prompting core not to replace them
 * the addition of these custom attributes is disabled via filters

 WP has done this in the core functionality for a while, but it's never
 mattered as the `<img />` tag was only replaced by an `<img />` tag.

 With the filter, a developer may wish to replace the images tag by
 wrapping it in another tag (for example `<picture />` with an `<img />`
 fallback). With the new filter, Core does need to replace the tag once and
 once only.

 I'll create a follow up issue and assign it to @flixos90

 ----

 These are the tests I used to reproduce the issue.

 {{{#!php
 <?php
 /**
  * @ticket 55347
  */
 public function
 test_wp_filter_content_tags_with_identical_images_custom_attributes() {
         $img         = get_image_tag( self::$large_id, '', '', '',
 'medium' );
         $img         = str_replace( '<img ', '<img srcset="custom"
 sizes="custom" loading="custom" ', $img );
         $the_content = "$img\n\n$img";

         add_filter(
                 'wp_content_img_tag',
                 function( $filtered_image ) {
                         return "<span>$filtered_image</span>";
                 }
         );

         $actual = wp_filter_content_tags( $the_content );
         $this->assertStringNotContainsString( '<span><span>', $actual );
 }

 /**
  * @ticket 55347
  */
 public function
 test_wp_filter_content_tags_with_identical_images_disabled_core_filters()
 {
         $img         = get_image_tag( self::$large_id, '', '', '',
 'medium' );
         $the_content = "$img\n\n$img";

         add_filter( 'wp_lazy_loading_enabled', '__return_false' );
         add_filter( 'wp_img_tag_add_width_and_height_attr',
 '__return_false' );
         add_filter( 'wp_img_tag_add_srcset_and_sizes_attr',
 '__return_false' );

         add_filter(
                 'wp_content_img_tag',
                 function( $filtered_image ) {
                         return "<span>$filtered_image</span>";
                 }
         );

         $actual = wp_filter_content_tags( $the_content );
         $this->assertStringNotContainsString( '<span><span>', $actual );
 }
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55347#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 23:29:30 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 23:29:30 -0000
Subject: [wp-trac] [WordPress Trac] #33388: WP_Theme should use
 get_file_data() for retrieving page templates
In-Reply-To: <048.061a085f96668a234b38023317b1e563@wordpress.org>
References: <048.061a085f96668a234b38023317b1e563@wordpress.org>
Message-ID: <063.5103514b9daf10d40653eea7ebd56675@wordpress.org>

#33388: WP_Theme should use get_file_data() for retrieving page templates
-------------------------------------+-----------------------------
 Reporter:  dd32                     |       Owner:  SergeyBiryukov
     Type:  defect (bug)             |      Status:  reviewing
 Priority:  normal                   |   Milestone:  6.0
Component:  Themes                   |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  needs-testing has-patch  |     Focuses:
-------------------------------------+-----------------------------
Changes (by costdev):

 * Attachment "33888.3.diff" added.

 Patch refreshed against trunk. Added missing `{}` in `if` statements,
 removed extraneous semi-colon + PHPCS fixes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33388>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 23:35:17 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 23:35:17 -0000
Subject: [wp-trac] [WordPress Trac] #55510: The `wp_content_img_tag` filter
 can appear to run twice when used to wrap image tags
Message-ID: <057.11e6dbf516bdb1288e9082093e4cebd4@wordpress.org>

#55510: The `wp_content_img_tag` filter can appear to run twice when used to wrap
image tags
---------------------------+------------------------------------------
 Reporter:  peterwilsoncc  |      Owner:  flixos90
     Type:  defect (bug)   |     Status:  assigned
 Priority:  normal         |  Milestone:  6.0
Component:  Media          |    Version:
 Severity:  normal         |   Keywords:  needs-patch needs-unit-tests
  Focuses:                 |
---------------------------+------------------------------------------
 Follow up to [53028] for #55347.

 The new `wp_content_img_tag` can be problematic if a developer wishes to
 replace an `<img />` tag by wrapping it in another tag, eg `<span><img
 /><span>` or, more likely, the `<picture />` tag.

 If an image tag appears twice or more in a posts content and none of the
 WP default changes (width and height, responsive images, lazy loading)
 then each time the filter runs the image tag will be replaced.

 The same issue will occur if `wp_filter_content_tags()` is run multiple
 times on the same blob of HTML, although in that instance the double
 wrapping will occur for all images.

 cc @pbearne

 Please see example unit tests in the follow up comment.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55510>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 23:43:05 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 23:43:05 -0000
Subject: [wp-trac] [WordPress Trac] #55510: The `wp_content_img_tag`
 filter can appear to run twice when used to wrap image tags
In-Reply-To: <057.11e6dbf516bdb1288e9082093e4cebd4@wordpress.org>
References: <057.11e6dbf516bdb1288e9082093e4cebd4@wordpress.org>
Message-ID: <072.7407b37405b2d755fb1855efa2df29c0@wordpress.org>

#55510: The `wp_content_img_tag` filter can appear to run twice when used to wrap
image tags
------------------------------------------+-----------------------
 Reporter:  peterwilsoncc                 |       Owner:  flixos90
     Type:  defect (bug)                  |      Status:  assigned
 Priority:  normal                        |   Milestone:  6.0
Component:  Media                         |     Version:
 Severity:  normal                        |  Resolution:
 Keywords:  needs-patch needs-unit-tests  |     Focuses:
------------------------------------------+-----------------------

Comment (by peterwilsoncc):

 Three unit tests, two with the same image included twice under certain
 circumstances, one with the `wp_filter_content_tags()` function running on
 the content multiple times.

 Please check there is not a situation in WP in which the
 `wp_filter_content_tags()` function will run twice on the same blob of
 content. I do wonder if any sites run it on save to avoid the performance
 hit, but I'd expect them to disable it on render.

 {{{#!php
 <?php
 /**
  * Test an image included twice that already contains the attributes WP
 adds.
  *
  * @ticket 55347
  */
 public function
 test_wp_filter_content_tags_with_identical_images_custom_attributes() {
         $img         = get_image_tag( self::$large_id, '', '', '',
 'medium' );
         $img         = str_replace( '<img ', '<img srcset="custom"
 sizes="custom" loading="custom" ', $img );
         $the_content = "$img\n\n$img";

         add_filter(
                 'wp_content_img_tag',
                 function( $filtered_image ) {
                         return "<span>$filtered_image</span>";
                 }
         );

         $actual = wp_filter_content_tags( $the_content );
         $this->assertStringNotContainsString( '<span><span>', $actual );
 }

 /**
  * Test an image included twice when attribute modification is disabled.
  *
  * @ticket 55347
  */
 public function
 test_wp_filter_content_tags_with_identical_images_disabled_core_filters()
 {
         $img         = get_image_tag( self::$large_id, '', '', '',
 'medium' );
         $the_content = "$img\n\n$img";

         add_filter( 'wp_lazy_loading_enabled', '__return_false' );
         add_filter( 'wp_img_tag_add_width_and_height_attr',
 '__return_false' );
         add_filter( 'wp_img_tag_add_srcset_and_sizes_attr',
 '__return_false' );

         add_filter(
                 'wp_content_img_tag',
                 function( $filtered_image ) {
                         return "<span>$filtered_image</span>";
                 }
         );

         $actual = wp_filter_content_tags( $the_content );
         $this->assertStringNotContainsString( '<span><span>', $actual );
 }

 /**
  * Test wrapping an image when the `wp_filter_content_tags()` function
 runs multiple times.
  *
  * @ticket 55347
  */
 public function test_wp_filter_content_tags_with_the_function_run_twice()
 {
         $the_content = get_image_tag( self::$large_id, '', '', '',
 'medium' );

         add_filter(
                 'wp_content_img_tag',
                 function( $filtered_image ) {
                         return "<span>$filtered_image</span>";
                 }
         );

         $actual = wp_filter_content_tags( wp_filter_content_tags(
 $the_content ) );
         $this->assertStringNotContainsString( '<span><span>', $actual );
 }

 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55510#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

From noreply at wordpress.org  Thu Mar 31 23:50:59 2022
From: noreply at wordpress.org (WordPress Trac)
Date: Thu, 31 Mar 2022 23:50:59 -0000
Subject: [wp-trac] [WordPress Trac] #35500: Login page: user can change
 password on " " but can't log in with new password.
In-Reply-To: <054.cf9e3d0204e900fc1a0039fd96a81b85@wordpress.org>
References: <054.cf9e3d0204e900fc1a0039fd96a81b85@wordpress.org>
Message-ID: <069.77a0078d68e29334dd4a04c6f28d4630@wordpress.org>

#35500: Login page: user can change password on " " but can't log in with new
password.
-----------------------------------------------+---------------------------
 Reporter:  antonrinas                         |       Owner:
                                               |  hellofromTonya
     Type:  defect (bug)                       |      Status:  assigned
 Priority:  lowest                             |   Milestone:  6.0
Component:  Login and Registration             |     Version:
 Severity:  normal                             |  Resolution:
 Keywords:  has-patch has-testing-info commit  |     Focuses:
-----------------------------------------------+---------------------------
Changes (by costdev):

 * keywords:  has-patch needs-testing has-testing-info => has-patch has-
     testing-info commit


Comment:

 == Test Report

 === Environment
 * Server: nginx - Local by Flywheel
 * WordPress: 5.9.2
 * Browser: Chrome 99.0.4844.84
 * OS: Windows 10
 * Theme: Twenty Twenty-Two
 * Plugins:
   * Email Log 2.4.8

 === Steps
 1. Go to the Password Reset screen.
 2. Type one or more spaces into both password fields.
 3. Click `Save Password` button. => Notice it let you. ✅
 4. Try to log in with that "space-only" password. => Notice it fails. ✅
 5. Apply patch
 [https://core.trac.wordpress.org/attachment/ticket/35500/35500.1.diff
 35500.1.diff].
 6. Request another password reset and go to the Password Reset screen.
 7. Type one or more spaces into both password fields.
 8. Click `Save Password` button.
 9. This time notice an error message is displayed and the Password Reset
 screen reloads. ✅

 === Results
 1. Issue reproduced.
 2. Patch
 [https://core.trac.wordpress.org/attachment/ticket/35500/35500.1.diff
 35500.1.diff] resolves the issue.

 -----
 - Removing `needs-testing`.
 - Adding `commit` for consideration.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/35500#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform