__group__ ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter
Needs Patch 60803 Include fonts directory in `get_space_used()` calculation Editor normal normal Awaiting Review defect (bug) new 2024-03-19T02:46:16Z 2024-03-19T02:46:16Z "As font files can be uploaded by users other than the network administrators on multisite installs, the `get_space_used()` function may need to be modified to include the new folder.
This will ensure that all files are considered when calculating the amount of upload space available for individual sites on a multi-site install.
This isn't super urgent in the early days of the font library so can wait until a 6.5 point release." peterwilsoncc
Needs Patch 60802 Enable debug mode / debug options in site health Site Health normal minor Awaiting Review feature request new close 2024-03-18T19:34:03Z 2024-03-18T21:31:48Z "Debugging is a necessity for any developer and for WordPress users in general. As it stands now debug mode and the related debug options can only be enabled through manually editing the wp-config file to add or adjust wp-config constants. This makes debugging harder to access for everyone, and even more difficult to access for users that are either not familiar with ftp/ssh or who only have wp-admin access and not access to the filesystem.
Adding toggle options for debugging mode in the Site Health tools wp-admin page would make troubleshooting errors and issues easier and more accessible for all users with administrator access. As a bonus, this would also decrease the demand on web host technical support because users would be more equipt to identify plugin conflicts, php errors and other issues independently.
Proposed Site Health Options:
- 'Enable debugging on/off' -- WP_DEBUG true/false with false as default and subtext about only setting to true/on for troubleshooting bc of adverse performance effects.
- 'Enable debug log on/off' -- WP_DEBUG_LOG true/false - set to true/on as default and
- Site Health could and should have a tab to view contents of debug logs within wp-admin (maybe -tail 30 or the last 30-50 results, potentially could improve on this to hide duplicate entries, to hide warnings and notices and to grep/search for keywords)
- 'Show errors on front end on/off' - WP_DEBUG_DISPLAY true/false with a default to false so as not to expose debugging to end users and this could also have a toggle option to display errors only in wp-admin pages and not on the front end
- Debugging should be set to never display on the front end in the first place as a default (ever), that could probably be it's own ticket
- This could be expanded on to include toggle settings for SCRIPT_DEBUG and SAVEQUERIES constants
" amykamala
Needs Patch 60801 New sessions are created when user authenticates but there already are active sessions Login and Registration 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-18T18:28:41Z 2024-03-18T21:07:37Z "**The problem:** When a user logs in to WordPress a new session is created. If the user opens a new browser tab and navigates to website/wp-admin, the user does not need to authenticate because of the session cookies are saved in the browser, which is the expected behaviour. The same happens even when the user closes the browser completely and reopens it within the duration of that session.
However, if the user navigates to the URL *website/wp-login.php* on the website they are already logged in, the user is presented with a login page, and upon authenticating WordPress creates a new session and new cookies etc, instead of ""retrieving"" the existing logged-in session.
**How to reproduce:**
1. Log in to a WordPress website
2. Open a new browser tab on the same browser (you can close the previous one)
3. Navigate to the login page of the same website you are already logged in to: *website/wp-login.php*
4. Log in
At this point there are two different sessions for the same user in the database and in the browser the user has multiple sets of cookies for the different sessions.
**The issues this causes:**
1. Excessive amount of unnecessary session data in the database. We've seen some large websites with tens of thousands of session entries in the database.
2. Site admins who try to control / limit / manage the number of simultaneous user sessions with third party plugins end up having a lot of problems, such as locking out legit users etc
**Possible solution?:** There are a few possible solutions, however, the easiest one we can think of is to check for session cookies in the users' browsers whenever they access the *wp-login.php*, and if there are, retrieve that session." robert681
Needs Patch 60800 Twenty Twenty-One: prevent PHP 8 fatal error from non-string in $tags_list Bundled Theme normal normal 6.6 defect (bug) new 2024-03-18T16:07:35Z 2024-03-18T18:05:23Z "In `/inc/template-tags.php` there is a call to `get_the_tag_list()` - https://themes.trac.wordpress.org/browser/twentytwentyone/2.1/inc/template-tags.php#L154
The only check on the return value is an `if` condition. The problem is that a few lines down ( 159 ) it is required to be a string. But the `get_the_tag_list()` function is documented as being able to return `string|false|WP_Error` - https://developer.wordpress.org/reference/functions/get_the_tag_list/
When a `WP_Error` object is returned and used in the string context of the `printf()` a fatal error happens in PHP 8.1:
{{{
PHP Fatal error: Uncaught Error: Object of class WP_Error could not be converted to string in twentytwentyone/inc/template-tags.php:159
}}}
The `if` condition should be updated to ensure that the `printf()` only gets called if the return value of `get_the_tag_list()` is indeed a string. Something like:
{{{
if ( is_string( $tags_list ) ) {
}}}" josephscott
Needs Patch 60799 Change the Header Tag in Link Modal from
to
for Better Accessibility TinyMCE 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-18T15:38:57Z 2024-03-18T15:38:57Z "=== Problem:
Currently, the WordPress link insertion modal in the text editor uses an
tag for its title (""Insert/edit link""). This can create accessibility issues, as multiple
tags on a single page can confuse screen readers and undermine the semantic structure of the content, potentially leading to a poor user experience for people with disabilities.
=== Proposed Solution:
I suggest changing the
tag in the link insertion modal to a
tag, or alternatively to a tag if the heading level is not appropriate in the context of the modal's use. This change would improve the semantic HTML structure and enhance accessibility by maintaining a proper heading hierarchy.
=== Justification:
According to the HTML5 specification and accessibility guidelines, a page should have a clear and logical heading hierarchy. The main content should start with an
tag, followed by
,
, and so on. The current use of an
tag in the link modal disrupts this hierarchy, especially since this modal can appear on any page regardless of the existing heading structure.
Implementing this change will make WordPress more accessible and compliant with WCAG (Web Content Accessibility Guidelines) standards, which is crucial for users relying on screen readers and for SEO best practices.
=== Steps to Reproduce:
1. Go to the WordPress text editor.
2. Click on the 'Add link' button to open the link insertion modal.
3. Inspect the modal's title element, which is currently marked up as an
.
=== Possible Implementation:
The change can be implemented by modifying the HTML structure in the core WordPress files where the link modal is defined. Additionally, testing should be conducted to ensure that this change does not affect the modal's functionality and that it enhances the accessibility as intended.
I am looking forward to the community's input on this proposal and am happy to contribute to the implementation and testing phases.
" lyonmuller
Needs Dev / Bug Wrangler Feedback 60798 Investigate potentially failing Imagick PDF alpha channel test Media normal normal Awaiting Review defect (bug) new dev-feedback 2024-03-18T11:30:17Z 2024-03-18T11:31:33Z "The test `\Tests_Image_Editor_Imagick::test_remove_pdf_alpha_channel_should_remove_the_alpha_channel_in_preview()` was introduced in #39216 / [56271].
On some hosting providers, this test appears to be failing with errors such as this:
{{{
Tests_Image_Editor_Imagick::test_remove_pdf_alpha_channel_should_remove_the_alpha_channel_in_preview
The intermediate size could not be retrieved.
Failed asserting that false is of type ""array"".
/tmp/wp-test-runner/tests/phpunit/tests/image/editorImagick.php:680
}}}
Examples:
https://make.wordpress.org/hosting/test-results/r57849/wpsabot-r57849/
https://make.wordpress.org/hosting/test-results/r57848/wetopibot-r57848/
We should investigate this failure to see whether it's an issue in core or with the hosting provider.
The test mentions ""Ghostscript version >= 9.14"", so maybe it's just a matter of skipping the test if the installed Ghostscript version (`gs --version` I think) is older than that." swissspidy
Needs Patch 60796 An error for page and post without revisions support Posts, Post Types 6.4 normal normal Awaiting Review defect (bug) new 2024-03-18T10:03:04Z 2024-03-18T10:03:04Z "Since **6.4.0** the `$revisions_enabled` argument was added to the arguments array of `register_meta()` function (https://developer.wordpress.org/reference/functions/register_meta/#changelog).
For post and page with disabled revisions support there is an error:
Error: Function register_meta was called incorrectly. Meta keys cannot enable revisions support unless the object subtype supports revisions. Please see Debugging in WordPress for more information. (This message was added in version 6.4.0.).
In register_block_core_footnotes() function `revisions_enabled` argument is permanently set to true and it's makes this error." danielpietrasik
Needs Patch 60794 Central Payment Gateway API for WordPress and All Plugins Plugins normal major Awaiting Review enhancement new 2024-03-18T03:02:49Z 2024-03-18T18:13:30Z "I think it's time to add a built-in payment gateway API to WordPress. Each plugin develops its own API and we develop custom plugins for each plugin. This is ridiculous.
Imagine if there was a centralized API and PayPal, Stripe or any payment gateway was integrated for that API. All other plugins will use that API." beycanpress
Has Patch / Needs Testing 60793 wp_trigger error has a wrong wp_kses $allowed_html arguement. Formatting 6.4 normal normal Awaiting Review defect (bug) new has-patch 2024-03-18T02:04:16Z 2024-03-18T02:15:45Z "Elements and attributes need to be array keys, not values.
Came with: https://core.trac.wordpress.org/changeset/56707
Fix: https://github.com/WordPress/wordpress-develop/pull/6285" nico23
Has Patch / Needs Testing 60791 Pre-populate slug using URL parameters on new post edit screen. Posts, Post Types normal normal Awaiting Review enhancement new has-patch 2024-03-17T06:29:23Z 2024-03-17T15:28:10Z "get_default_post_to_edit() allows to pre-populate `post_title`, `content`, and `excerpt` from `$_REQUEST`.
This URL will pre-populate the title and the content:
/wp-admin/post-new.php?post_type=post&post_title=My+Title&content=aaaa
I have an use case where I need to do the same for the `post_name`:
https://wordpress.org/support/topic/set-title-and-slug-of-new-post-using-url-parameters/
I have a shortcode that allows me to load content from a custom post type, and it searches by slug (it needs to be this way for UX reasons).
If the post with the provided slug doesn't exist, I register an admin notice alerting that the shortcode is trying to load an unexisting post, and offer a link to create the missing post with the specified slug. I need the slug to be pre-populated with the URL parameter, just as it is possible to do for title, content, and excerpt." gerardreches
Needs Patch 60790 Editor has encountered an unexpected error Editor trunk normal normal Awaiting Review defect (bug) new 2024-03-16T10:02:59Z 2024-03-16T10:02:59Z "During the customization of the Blog template, an unexpected error was encountered by the editor when changing the line height after uploading a custom font.
" shilpamanoj
Needs Dev / Bug Wrangler Feedback 60789 Administration Email Address: Allow method to deactivate Administration normal normal Awaiting Review feature request new close 2024-03-16T01:23:43Z 2024-03-18T21:12:43Z "As a manager of many client sites, my email address is used on a lot of sites in the ""Administration Email Address"" in Settings > General.
Over time, clients move to other vendors, and sometimes this happens without the opportunity to change the Administration Email Address before it is moved. In many cases, this email address remains unchanged for years, and I continue to receive software update, user account, and other emails for accounts I have no contact with, and no way to access to change the setting.
This has been mentioned by other WordPress developers as well, and I believe it is a widespread problem, although one easy to dismiss on a day-to-day basis. I did a search through Trac tickets and didn't see anything like it, so I am posting this ticket in hopes that a solution can be reached.
Ideally, I'd like to see a solution that includes a time-sensitive link (similar to new account registrations) that would allow the owner of the admin to click through to the link, and agree to have the email address removed as the ""Administration Email Address""." andrewhoyer
Needs Patch 60788 Content-Disposition support in download_url() seems broken HTTP API 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-16T01:12:30Z 2024-03-16T01:12:30Z "
In https://core.trac.wordpress.org/changeset/51939 a change was made to resolve ticket https://core.trac.wordpress.org/ticket/38231 to make `download_url()` use the `Content-Disposition` header to specify the name of the downloaded file. I realize I'm a bit late to the party here since the ticket was opened more than 7 years ago and the change was made more than 2 years ago, but I think that this change was flawed and needs to be reconsidered (and possibly reverted entirely). The way it was implemented seems fundamentally broken and has the effect of making `download_url()` basically impossible to use reliably.
Consider the following simple PHP script named `echo.php`:
{{{#!php
'secupress',
'fields' => []
)
);
}}}
Since the doc says ''""@type bool $contributors Whether to return the list of contributors. **Default false**.""'' I should not receive this field.
Let see the response:
{{{#!php
string(37) ""SecuPress Free — WordPress Security""
[""slug""]=>
string(9) ""secupress""
[""version""]=>
string(7) ""2.2.5.1""
[""author""]=>
string(44) ""SecuPress""
[""author_profile""]=>
string(41) ""https://profiles.wordpress.org/secupress/""
[""contributors""]=>
array(4) {
...
}}}
There is. Same for those params that are ""false"" by default but still included: ""sections"", ""versions"", ""reviews"", ""banners"", ""active_installs"" (I don't know for ""group"", can't get the thing).
Also there is one param that is not affected by the arguments passed and always returned: ""num_ratings"".
Finally there is some fields that are always returned where the doc can't help, I tried to use they array keys to cancel them, no chance, this is : ""author', ""author_profile"" (those 2 may be forced, that's ok), ""support_threads"", ""support_threads_resolved"", ""upgrade_notice"", and ""requires_plugin"" (I know it's new, but don't forget it)
The patch may have to be done on w.org since this is the site that add too much data and to not respect the passed parameters.
Thanks for your time" juliobox
Needs Patch 60782 The method parameter is never used. General normal normal Awaiting Review enhancement new 2024-03-15T10:58:56Z 2024-03-15T11:27:28Z The function update_home_siteurl() has two parameters that newer used in the function block. patelmohip
Needs Dev / Bug Wrangler Feedback 60781 Expand or modify wp_get_environment_type function to allow more environment types Bootstrap/Load 5.5.1 normal normal Awaiting Review enhancement new dev-feedback 2024-03-15T09:49:27Z 2024-03-15T11:29:04Z "Currently the [https://developer.wordpress.org/reference/functions/wp_get_environment_type/ wp_get_environment_type()] function only allows 4 environment types:
{{{#!php
$wp_environments = array(
'local',
'development',
'staging',
'production',
);
}}}
But there are projects that have multiple environment types (CI, CD, pre-production, UAT, etc.).
So if you define the `WP_ENVIRONMENT_TYPE` to anything outside of these 4 environments, you'll end up with serving the `production` environment.
A trivial example would be where you'd like to change the color of your admin UI based on environments. I mean, sure you can use something like {{{defined('WP_ENVIRONMENT_TYPE') ? WP_ENVIRONMENT_TYPE : 'production'}}}, but what's the point of the `wp_get_environment_type` function then?
One alternative is to expand the `$wp_environments` variable with some of the industry most-used terms. Or just remove this check, and just return the value of `defined('WP_ENVIRONMENT_TYPE') ? WP_ENVIRONMENT_TYPE : 'production'` check." dingo_d
Changes Requested 60780 Twenty Twenty :- Button block having issue with letter spacing Bundled Theme 6.4.3 normal normal Awaiting Review defect (bug) new changes-requested 2024-03-15T09:34:25Z 2024-03-18T11:13:32Z "Steps to reproduce the issue :-
1. Activate Twenty Twenty theme.
2. Choose Button block.
3. Add text.
4. Now change the letter spacing.
You can able to see there is no difference in letter spacing in editor and front side both.
I have attached video for better understanding.
Video URL :- https://share.cleanshot.com/mpT4l41VskS7J26DB23b" nidhidhandhukiya
Needs Dev / Bug Wrangler Feedback 60778 Twenty Twenty-Three Theme: The Quote block style is not working as expected. Bundled Theme normal normal Awaiting Review defect (bug) new dev-feedback 2024-03-15T07:13:01Z 2024-03-15T10:06:33Z "Hello,
I have reviewed and found that the ""**Quote**"" block style is not working as expected into the **Twenty Twenty-Three** theme.
Here, I have attached video:
Issue: [https://share.cleanshot.com/78X9q3xkwy0kkT5HvHFL]
Thanks," viralsampat
Needs Patch 60777 New terms created when a term with commas is added in post editor Posts, Post Types 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-14T17:35:07Z 2024-03-14T17:35:07Z "When a taxonomy term has commas e.g ""Red, yellow & green"" and you add the term to a post in the post editor, the term gets added but new terms get created for the words before and after each comma. E.g you add the term ""Red, yellow & green"" to your post. That term will get added. However, you will also notice that two new terms have been created called ""Red"" and ""yellow & green"". Not sure if this is the case with both Gutenberg enabled." awesiome
Needs Patch 60776 Pullquote block having minor difference in spacing between editor and front side Editor 6.4.3 normal normal Awaiting Review defect (bug) new close 2024-03-14T15:34:47Z 2024-03-19T05:00:13Z "Steps to reproduce the issue :-
1. Activate Twenty Twenty Four theme.
2. Choose Pullquote block.
3. Add text and background to check the proper difference in both side.
Now check both the side editor and front.
You can able to see spacing difference in editor and frontend.
I have attached video for better understanding.
Video URL :- https://share.cleanshot.com/D39PTHnJ6TrspTC8XYMw" nidhidhandhukiya
Needs Patch 60775 Twenty Twenty Four :- Search block having issue with the width when we add first time. Bundled Theme 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-14T15:21:47Z 2024-03-14T15:21:47Z "Steps to reproduce the issue :-
1. Activate Twenty Twenty theme.
2. Choose Search block.
3. Give Width in px without change it in % or anything apply as defalut.
Now check both the side editor and front.
You can able to see no difference in width of search block.
Now change the width from the given option for example :- 25%
You can able to see a difference in editor and front end both.
Now change width paramater which is changed in %, Make it px and then change value.
You can able to see difference in width of search block in editor and front both the side.
I have attached video for better understanding.
Video URL :- https://share.cleanshot.com/hVRc9FjRz5PnKPCsVhrs" nidhidhandhukiya
Commit Candidates 60774 Make the user_login field readonly instead of disabled on the profile screen audrasjb* Users normal normal 6.6 enhancement accepted commit 2024-03-14T11:34:38Z 2024-03-14T14:18:12Z "This came up in an accessibility audit of one of the sites I work on. On the profile edit screen in wp-admin, the username is displayed using an input field with the `disabled` attribute. This field is skipped by screen readers, which leads to a ""loss of information"" for visually impaired users.
It's better to use `readonly` here. This is exactly what the field is used for, and readonly fields are read by screen readers." roytanck
Needs Patch 60773 Add a new Post from the editor Editor normal normal Awaiting Review enhancement new 2024-03-14T10:23:55Z 2024-03-14T11:34:51Z " When you are in the editor of an existing Post, there is no way to add a
new Post from there. You need to go back to ""View Posts"" -> ""Add New
Post"".
I would love to have this new usability feature added in the core." klevismiho
Has Patch / Needs Testing 60770 TimeZone select box compatibility with RTL directions Administration trunk normal normal Awaiting Review enhancement new has-patch 2024-03-13T15:35:10Z 2024-03-13T16:55:59Z "This patch fixes the time zone select box compatibility with RTL directions It sets auto direction which makes the options value compatible with both RTL and LTR directions
" farhad0
Needs Patch 60769 Block Hooks: Consolidate approach to get the list of hooked blocks. General normal normal Awaiting Review enhancement new 2024-03-13T14:28:40Z 2024-03-13T14:28:40Z "Our current approach to getting hooked blocks has two parts to it:
1. We use `get_hooked_blocks()` to get all of the hooked blocks which are hooked from the `block.json` file.
2. In function `insert_hooked_blocks` we apply the filter callbacks (passing a derived value from step 1 as the default value) to get hooked blocks that are applied by the `hooked_block_types` filter.
Currently it's a bit confusing and without knowledge you'd assume `get_hooked_blocks()` would retrieve ''all'' of the hooked blocks. Additionally it feels like you have to run a few different pieces of code separately and combine their resulting values to get a complete picture which could result in some bugs or unnecessary complexities.
I feel there's room for improvement to provide a better API for getting all of the hooked blocks by consolidating these two approaches into a single function somehow.
How this to work we would also need to know the current context so we can pass that data to the filter callbacks." tomjcafferkey
Needs Dev / Bug Wrangler Feedback 60766 i have faching this error how can i fix this General 6.4.3 normal major Awaiting Review defect (bug) new close 2024-03-13T07:32:45Z 2024-03-13T16:08:17Z "
`Warning: require(C:\xampp\htdocs\Nieuprawny/wp-includes/sodium_compat/autoload.php): Failed to open stream: No such file or directory in C:\xampp\htdocs\Nieuprawny\wp-includes\compat.php on line 338`
`Fatal error: Uncaught Error: Failed opening required 'C:\xampp\htdocs\Nieuprawny/wp-includes/sodium_compat/autoload.php' (include_path='C:\xampp\php\PEAR') in C:\xampp\htdocs\Nieuprawny\wp-includes\compat.php:338 Stack trace: #0 C:\xampp\htdocs\Nieuprawny\wp-settings.php(34): require() #1 C:\xampp\htdocs\Nieuprawny\wp-config.php(96): require_once('C:\\xampp\\htdocs...') #2 C:\xampp\htdocs\Nieuprawny\wp-load.php(50): require_once('C:\\xampp\\htdocs...') #3 C:\xampp\htdocs\Nieuprawny\wp-blog-header.php(13): require_once('C:\\xampp\\htdocs...') #4 C:\xampp\htdocs\Nieuprawny\index.php(17): require('C:\\xampp\\htdocs...') #5 {main} thrown in C:\xampp\htdocs\Nieuprawny\wp-includes\compat.php on line 338`" rajgt1
Has Patch / Needs Testing 60765 Typography Presets Editor trunk normal normal 6.6 defect (bug) new has-patch 2024-03-13T04:54:33Z 2024-03-13T05:36:36Z "
We should pass theme.json settings to global preset or style value-generating callbacks.
Currently `value_func` callable properties in `PRESETS_METADATA` do not have access to the current theme JSON settings.
An example:
`wp_get_typography_font_size_value()` needs to know other theme.json settings in order to correctly output values.
Styles generated by `WP_Theme_JSON::get_stylesheet` outside a WordPress instance, using custom settings will therefore have no effect.
See bug issue for further details: https://github.com/WordPress/gutenberg/issues/58135
This ticket is to sync the following Gutenberg PR: https://github.com/WordPress/gutenberg/pull/58362
" ramonopoly
Has Patch / Needs Testing 60763 Allow resizing the indivigual content areas in Appearance / Menus Menus trunk normal normal Awaiting Review enhancement new has-patch 2024-03-12T20:54:27Z 2024-03-12T20:57:22Z "The space to select posts, pages and custom posts for dropping into the menu is restricted to 200px height which makes it really difficult to select posts/pages when creating/editing menus.
The user experience will be greatly improved if the section can be resized." namith.jawahar
Needs Patch 60759 Block Hooks: Harmonize ignoredHookedBlocks metadata injection logic General normal normal 6.6 enhancement new 2024-03-12T15:15:43Z 2024-03-12T16:59:33Z "As of [57790] and https://github.com/WordPress/gutenberg/pull/59561, both the Templates and the Navigation endpoints use the [https://developer.wordpress.org/reference/hooks/rest_pre_insert_this-post_type/ `rest_pre_insert_*`] filter to inject the `ignoredHookedBlocks` metadata attribute into anchor blocks, prior to persisting a template, template part, or navigation menu to the database.
[https://wordpress.slack.com/archives/C02RQBWTW/p1709650462126059?thread_ts=1709649022.232249&cid=C02RQBWTW It has been requested] that these methods be harmonized, i.e. to use the `inject_ignored_hooked_blocks_metadata_attributes` filter for both templates/parts and navigation menus. In particular, this would allow removing some of the filters that are currently present in the Navigation block in favor of more ""generic"" functions.
Conceptually, the relevant filters are indeed quite similar; the major difference is that the one for the Navigation block (`block_core_navigation_update_ignore_hooked_blocks_meta`) injects a `_wp_ignored_hooked_blocks` post meta into the `wp_navigation` post object, in order to allow hooked blocks to be inserted as a Navigation block's first or last child (see #59743).
To harmonize the filters, we would thus have to add a conditional in `inject_ignored_hooked_blocks_metadata_attributes` to set the post meta if the post type is `wp_navigation`. (Later on, we might consider extending this to include template parts, where it might also be desirable to insert hooked blocks as a Template Part block's first or last child; however, this should be tackled separately, in order not to conflate refactoring and adding new functionality.)
----
Eventually, it might also be possible to harmonize injection of hooked blocks (which happens upon reading from the database, unlike the injection of the `ignoredHookedBlocks` attribute discussed above, which happens upon writing to it.)" Bernhard Reiter
Needs Patch 60756 Block Hooks: Toggle (re-)inserts hooked block in wrong position (if added by filter) General normal normal Awaiting Review defect (bug) new 2024-03-12T13:59:51Z 2024-03-12T14:48:27Z "As of [https://github.com/WordPress/gutenberg/pull/59396 this change], Block Hook toggles are displayed for hooked blocks that were added by a filter (rather than during block registration), ''if the containing template or template part has had user modifications''. (Displaying the toggle also for ''un''modified templates/parts is the subject of #59574, see especially https://core.trac.wordpress.org/ticket/59574#comment:13.)
There is still one more problem with these toggles: If the user disables the toggle to remove the hooked block, and then re-enables it to re-insert the latter, it's not possible for the client to infer ''where'' to insert it. Instead, it simply defaults to (re-)inserting it ''after'' the anchor block.
The reason is that once the hooked block is removed, no information about its position relative to its anchor block is available. The only available information is the `ignoredHookedBlocks` metadata attribute on the anchor block, which is an array of hooked block type names (e.g. `[""core/loginout"",""mycommerce/shopping-cart""]`). They do however not include the relative position of these hooked blocks. (This was considered in the original ticket #59646 for enabling Block Hooks in modified templates/parts, but ultimately dismissed.)" Bernhard Reiter
Needs Patch 60753 "Fatal error: Uncaught Error: Class ""wpdb"" not found in load.php" General normal normal Awaiting Review defect (bug) new 2024-03-12T07:29:07Z 2024-03-12T19:47:02Z "Hello, after updated php version in WordPress, i can't show admin login and errors are:
Fatal error: Uncaught Error: Class ""wpdb"" not found in
/home/mhd-01/www.xxxxxxxx.it/htdocs/wp-includes/load.php:428 Stack trace: #0
/home/mhd-01/www.xxxxxxxx.it/htdocs/wp-settings.php(120): require_wp_db() #1
/home/mhd-01/www.xxxxxxxx.it/htdocs/wp-config.php(98): require_once('...') #2
/home/mhd-01/www.xxxxxxxx.it/htdocs/wp-load.php(37): require_once('...') #3
/home/mhd-01/www.xxxxxxxx.it/htdocs/wp-admin/admin.php(34): require_once('...') #4
/home/mhd-01/www.xxxxxxxx.it/htdocs/wp-admin/index.php(10): require_once('...') #5
{main} thrown in /home/mhd-01/www.xxxxxxxx.it/htdocs/wp-includes/load.php on line 428
Is there any ideas about can i resolve this? Thanks.
I would login and not show any errors in my site on WordPress." danlelbachhuber
Needs Patch 60752 Fatal error: Uncaught Error: Class 'WpOrg\Requests\Hooks' not found General normal normal Awaiting Review defect (bug) new 2024-03-12T07:15:27Z 2024-03-12T19:36:57Z "I've been getting the same error message the last few days...makes me think it has something to do with the update?
I've tried: disabling plugins, and downloading/removing themes and reinstalling twenty twenty-one.
I'm new to WordPress, therefore have no backup, and at a complete loss here. Any guidance is much appreciated!
Fatal error: Uncaught Error: Class 'WpOrg\Requests\Hooks' not found in /home/sites/17a/3/36b2a5154b/practicalpathways/wp-includes/class-wp-http-requests-hooks.php:18 Stack trace: #0 /home/sites/17a/3/36b2a5154b/practicalpathways/wp-settings.php(249): require() #1 /home/sites/17a/3/36b2a5154b/practicalpathways/wp-config.php(92): require_once('/home/sites/17a...') #2 /home/sites/17a/3/36b2a5154b/practicalpathways/wp-load.php(50): require_once('/home/sites/17a...') #3 /home/sites/17a/3/36b2a5154b/practicalpathways/wp-admin/admin.php(34): require_once('/home/sites/17a...') #4 /home/sites/17a/3/36b2a5154b/practicalpathways/wp-admin/index.php(10): require_once('/home/sites/17a...') #5 {main} thrown in /home/sites/17a/3/36b2a5154b/practicalpathways/wp-includes/class-wp-http-requests-hooks.php on line 18
Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/sites/17a/3/36b2a5154b/practicalpathways/wp-includes/functions.php on line 5865
Notice: Function is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/sites/17a/3/36b2a5154b/practicalpathways/wp-includes/functions.php on line 5865" moustifi
Needs Patch 60750 Warning: these pages should not be the same as your Privacy Policy page! General 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-11T20:20:54Z 2024-03-11T20:20:54Z On Settings > Reading this message appears. The Privacy Page is NOT SELECTED. The homepage is another page and that is what is selected. There is nothing else in there. OctoTooT
Needs Patch 60748 auth_redirect() login check doesn't exist or doesn't work Login and Registration normal normal Awaiting Review defect (bug) new 2024-03-11T13:11:38Z 2024-03-11T13:33:04Z "The `auth_redirect()` documentation states:
""Checks if a user is logged in, if not it redirects them to the login page.""
[https://developer.wordpress.org/reference/functions/auth_redirect/]
However, unless a call to `auth_redirect()` is wrapped inside a `is_user_logged_in()` check, then it always sends people to the login page (even if a user is already logged in).
I don't know if the documentation is incorrect or if there is a bug in the code.
To reproduce, all you need to do is something like this:
{{{#!php
'string',
'author__not_in' => 'string',
'category__and' => 'string',
'category__in' => 'string',
'category__not_in' => 'string',
'post__in' => 'string',
'post__not_in' => 'string',
'post_name__in' => 'string',
'post_parent__in' => 'string',
'post_parent__not_in' => 'string',
'tag__and' => 'string',
'tag__in' => 'string',
'tag__not_in' => 'string',
'tag_slug__and' => 'string',
'tag_slug__in' => 'string',
}}}
Using most of the above query args in a `WP_Query::get_posts()` call result in a PHP fatal.
Things that expect scalars:
{{{
'attachment' => array(),
'author_name' => array(),
'feed' => array(),
}}}
Using any of the above query args result in a PHP fatal on a default WP installation:
{{{
alex@wayra core % cat .wp-env.json
{
""core"": null
}
}}}
http://localhost:8888/?attachment[]=admin
{{{
Fatal error: Uncaught TypeError: urlencode(): Argument #1 ($string) must be of type string, array given in /var/www/html/wp-includes/formatting.php:5683 Stack trace: #0 /var/www/html/wp-includes/formatting.php(5683): urlencode(Array) #1 /var/www/html/wp-includes/class-wp-query.php(2183): wp_basename(Array) #2 /var/www/html/wp-includes/class-wp-query.php(3824): WP_Query->get_posts() #3 /var/www/html/wp-includes/class-wp.php(696): WP_Query->query(Array) #4 /var/www/html/wp-includes/class-wp.php(816): WP->query_posts() #5 /var/www/html/wp-includes/functions.php(1336): WP->main('') #6 /var/www/html/wp-blog-header.php(16): wp() #7 /var/www/html/index.php(17): require('/var/www/html/w...') #8 {main} thrown in /var/www/html/wp-includes/formatting.php on line 5683
}}}
http://localhost:8888/?author_name[]=admin
{{{
Fatal error: Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in /var/www/html/wp-includes/class-wp-query.php:2358 Stack trace: #0 /var/www/html/wp-includes/class-wp-query.php(2358): str_contains(Array, '/') #1 /var/www/html/wp-includes/class-wp-query.php(3824): WP_Query->get_posts() #2 /var/www/html/wp-includes/class-wp.php(696): WP_Query->query(Array) #3 /var/www/html/wp-includes/class-wp.php(816): WP->query_posts() #4 /var/www/html/wp-includes/functions.php(1336): WP->main('') #5 /var/www/html/wp-blog-header.php(16): wp() #6 /var/www/html/index.php(17): require('/var/www/html/w...') #7 {main} thrown in /var/www/html/wp-includes/class-wp-query.php on line 2358
}}}
http://localhost:8888/?feed[]=admin
{{{
Fatal error: Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in /var/www/html/wp-includes/class-wp-query.php:1018 Stack trace: #0 /var/www/html/wp-includes/class-wp-query.php(1018): str_contains(Array, 'comments-') #1 /var/www/html/wp-includes/class-wp-query.php(1868): WP_Query->parse_query() #2 /var/www/html/wp-includes/class-wp-query.php(3824): WP_Query->get_posts() #3 /var/www/html/wp-includes/class-wp.php(696): WP_Query->query(Array) #4 /var/www/html/wp-includes/class-wp.php(816): WP->query_posts() #5 /var/www/html/wp-includes/functions.php(1336): WP->main('') #6 /var/www/html/wp-blog-header.php(16): wp() #7 /var/www/html/index.php(17): require('/var/www/html/w...') #8 {main} thrown in /var/www/html/wp-includes/class-wp-query.php on line 1018
}}}" xknown
Needs Patch 60739 Wrong redirection when installing with URI rewrite Upgrade/Install 3.7 normal normal Future Release defect (bug) new 2024-03-10T22:54:12Z 2024-03-13T21:48:16Z "I have a server where the users can build their own WordPress installations. The URL of such installation is like: https://example.com/u/user/wpfolder/
The folder on disk is like: /srv/http/public_html_user/wpfolder
But when the user tries to run the installation setup, an automatic redirection leeds to the following incorrect address: https://example.com/wpfolder/wp-admin/setup-config.php (notice that /u/user/ is missing)
So:
- REQUEST_URI is '/u/user/wpfolder'
- My document root is '/srv/http/public_html_user/'
- Therefore the document URI (relative to this document root) is '/wpfolder/index.php'
- And the $_SERVER[PHP_SELF] value is '/wpfolder/index.php'
I have found that the problem comes from the wp_guess_url function in wp-includes/functions.php file (line 6218):
{{{#!php
add( 'invalid_email', __( 'Error: There is no account with that username or email address.' ) );
$errors->add( 'invalid_email', __( 'Error: The email address is not correct.' ) );
$errors->add( 'user_email', __( 'Error: The email address is not correct.' ), array('form-field' => 'email', ) );
}}}
The 1st is an error message when you try to login using an email address that is not used as a user in this site, the key is ""invalid_email""
The 2nd is an error message when you try to register a new user with an email address that is not correctly formatted, the key is ""invalid_email""
The 3rd is an error message when you try to update your personal profile with an email address that is not correctly formatted, the key is ""user_email""
So we have 2 keys and 2 messages (like ""A1 A2 B2"", should be ""A1 B2 B2"") but the message 2 is sharing both, we should clearly decide is ""invalid_email"" is when the email does not exists in our site OR when the email is not correctly formatted.
I suggest that the 2nd message should share the ""user_email"" and let the ""invalid_*"" for the login stuff, like we already have ""invalidcombo"" or ""invalid_username"" that shares the same kind of issue.
thanks for your reading time" juliobox
Needs Reporter Feedback / Steps To Reproduce 60735 Problem: Updating failed. The response is not a valid JSON response General 6.4.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2024-03-09T02:50:17Z 2024-03-09T12:20:40Z "I encountered an error message when publishing or updating. Due to a mistake in a wrong sentence, the error message appears. You will get the error message ""Updating failed. The response is not a valid JSON response"". Why did it happen?
- WordPress 6.4.3 running theme GeneratePress.
- .htaccess file according to wp settings
- Permalinks postname settings
- Already started with HTTPS
- REST API no 404 error message" r3ndy
Needs Patch 60734 Deregistering Open Sans Script Loader 6.4.3 normal normal Awaiting Review enhancement new 2024-03-09T02:15:43Z 2024-03-09T10:31:21Z "I have wasted an entire day trying to figure out why my Open Sans styles were not applying. This is counterproductive/suboptimal.
As it turns out, Open Sans was packed in WP back in 2014, which is fine by me. More info: #28478
However it is **not** immediately **obvious** one needs to `wp_deregister_style('open-sans');` before he can register his own style.
Please, consider making an exception and make `wp_register_style()` automatically `wp_deregister_style(X)` if X equals 'open-sans'. Otherwise consider other courses of action that may prevent others from incurring in the same problem I did.
Thanks.
" ecv80
Needs Patch 60733 GitHub Actions updates and improvements for 6.6 Build/Test Tools normal normal 6.6 task (blessed) new 2024-03-09T01:05:07Z 2024-03-09T01:07:53Z "
This ticket is for various updates and improvements for Core's GitHub Actions workflows.
Previously:
- 6.5 (#59805)
- 6.4 (#58867)
- 6.3 (#57865)
- 6.2 (#57572)
" desrosj
Commit Candidates 60732 Update old document URLs to new ones audrasjb* General normal minor 6.6 enhancement accepted commit 2024-03-08T15:53:24Z 2024-03-12T06:51:33Z "Some articles that was in https://wordpress.org/documentation/ was moved under https://developer.wordpress.org/advanced-administration/ and the old URLs has a redirect.
However URLs in php files still refer to the old ones so I thought the URLs should be updated to avoid unnecessary redirects." mkismy
Needs Patch 60729 YouTube embed start= Embeds 6.4.3 normal minor Awaiting Review defect (bug) new 2024-03-08T07:24:54Z 2024-03-08T07:24:54Z "Hi. I am experiencing an issue where I am seeing the video start time being either randomized or shifted for each load.
Expected behavior: YouTube video embedded with a timestamp like {youtube_url}start=5064, video starts at 1:24:24 each time video is loaded on a blog post.
Issue 1: if ""resize for smaller devices"" is active the start point is randomized before posting. E.g. at 5064 it start approximately 30 seconds before it should (say 5034). I shift the start time to 5094 to try and compensate, resulting in it starting earlier than previously (say 5004). I leave it at 5064 and publish the blog post, with the result of it starting at 0 seconds (incognito mode, fresh browser, logged in).
Issue 2: Resize for smaller devices is turned off. Now the first time the video is loaded it starts where it is supposed to start at 5064 seconds (steps: start video -> refresh page -> start video -> refresh -> ...). But, for each time the blog post is loaded and the viewers presses play, the start time shifts back approximately 30 seconds. This does not happen in incognito mode, here it loads at the correct timestamp each time the page is reloaded and video started." chrdre
Needs Patch 60728 Install/upgrade latest supported version of plugin, when latest version of plugin is not supported Plugins trunk normal normal Future Release defect (bug) new close 2024-03-07T20:49:11Z 2024-03-14T13:38:00Z "== Expected behaviour ==
When a user finds a plugin to install and the latest version requires a newer version of WordPress, an older version of that plugin which does support the installed version of WordPress is installed.
When a user goes to the plugins page to update their plugins, the user is prompted to install newer versions of a plugin which still support the installed version of WordPress.
== Actual behaviour ==
User is presented with an error telling them that the plugin doesn't support their version of WordPress and can't be installed.
User is not shown any updates available for plugins where the latest version doesn't support the installed version, even if dozens of newer versions are available which do support it.
== Problem ==
This becomes a particular problem when using something like the Debian packaged version of WordPress (where the version will only be updated every 2 years) when combined with plugins (e.g. Yoast) that, for some reason, keep increasing the minimum version every few months to the latest release.
In the above situation, the user upgrades to a newer version of WordPress, but the plugin has already made a new release that requires an even newer version of WordPress. Thus the user doesn't get any notification or easy way to upgrade a plugin which is now several years old and doesn't work with the installed version of WordPress." Dreamsorcerer
Needs Patch 60727 Allow fine-grained control of when to use oEmbed for providers outside the explicit list Embeds normal normal Awaiting Review enhancement new 2024-03-07T18:30:45Z 2024-03-07T18:30:45Z "WordPress maintains a list of appvoed oEmbed providers. Developers are able to add or remove providers from this list.
WordPress also attempts to see if URLs, outside the provider list, support oEmbed - and if they do, it uses oEmbed for them. Unfortunately, this is currently an ""all or nothing"" appraoch. You can either agree to use all these random sites oEmbed, or none. I'd love to see a filter added to control whether or not a specific URL, outside the provider list, should use oEmbed.
For reference, our specific use case is we want to continue supporting oEmbed for the vast majority of sites that support it - but we've identified some specific domains that do a poor job of oEmbed, and we'd like to only turn it off for those domains." MadtownLems
Needs Patch 60726 The WordPress core password reset needs to pre-populate the username to meet WCAG 2.2 joedolson* Login and Registration normal normal 6.6 defect (bug) accepted 2024-03-07T17:09:25Z 2024-03-07T19:33:35Z "According to new WCAG 2.2 success criterion for [https://www.w3.org/TR/WCAG22/#dfn-processes 3.3.7 redundant entry].
The criterion establishes that information previously entered by or provided to the user that is required to be entered again the same process is either:
* auto-populated, or
* available for the user to select
There are 3 exceptions:
* re-entering the information is essential,
* the information is required to ensure the security of the content, or
* previously entered information is no longer valid.
Once the user has performed the process of requesting a new password, the redirected form should have the username filled-in to pass. As of now, this is the form that the user is redirected to:
" estelaris
Has Patch / Needs Testing 60724 TT2: Wrap Navigation block in Row within the header.html template part Bundled Theme trunk normal normal 6.6 defect (bug) new has-patch 2024-03-07T12:20:57Z 2024-03-13T09:31:10Z Now that the Block Hooks API has been released as part of WordPress 6.4 3PDs may want to insert their own blocks into the header of the TT2 theme, specifically after the Navigation block. This currently causes problems because the Navigation block and it's siblings are treated as flex items due to its parent being a Row block. tomjcafferkey
Has Patch / Needs Testing 60723 TT3: Wrap Navigation block in Row within the header.html template part tomjcafferkey Bundled Theme trunk normal normal 6.6 enhancement assigned has-patch 2024-03-07T12:11:25Z 2024-03-13T09:31:37Z Now that the Block Hooks API has been released as part of WordPress 6.4 3PDs may want to insert their own blocks into the header of the TT3 theme, specifically after the Navigation block. This currently causes problems because the Navigation block and it's siblings are treated as flex items due to its parent being a Row block. tomjcafferkey
Needs Reporter Feedback / Steps To Reproduce 60722 incorrect display of mail due to outdated version of PHP mailer Mail 6.4.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2024-03-07T10:47:34Z 2024-03-18T14:59:57Z "Good morning,
I am experiencing problems when displaying order confirmation emails and contact forms from multiple WordPress websites.
This code is displayed first in the emails:
Content-Type: text/html; charset=UTF-8
I've already been looking into what could be causing it. There it was indicated that it was due to the PHP Mailer version of WordPress. Could it be that the PHP Mailer update is not current with the new version (6.4.3) of WordPress?
Yours sincerely,
Diana" studiodv
Needs Patch 60721 redirect_canonical suddenly causes issues with paramter values and CDN Canonical 6.4.3 normal minor Awaiting Review defect (bug) new 2024-03-07T07:31:07Z 2024-03-07T07:31:07Z "Hi there,
I was just wondering if anything has changed regarding https://developer.wordpress.org/reference/functions/redirect_canonical/?
`https://some-domain.tld/?my_param=a+a`
triggers a 301 redirect to
`https://some-domain.tld/?my_param=a a`
Now our CDN is set to pass URLs with `my_param` straight on to WordPress. Since that response with a 301, that's what gets cached by the CDN and causes a redirect loop.
Is that something new? I hadn't had that issue before, but also not 100% sure if I sent a value like ""a+a"" before. Trying to figure out why this redirect loop happens now after years.
I'll leave that ticket to be a bug, but if nothing has changed in redirect_canonical() then I guess it can just be closed.
Thanks for your help." retrovertigo
Has Patch / Needs Testing 60719 Add fonts upload location to Site Health report Site Health normal normal 6.6 enhancement new has-patch 2024-03-07T06:05:53Z 2024-03-12T16:54:27Z Just like Site Health lists the paths to the plugins/themes/uploads directories, we should list the path to the fonts directory (and its size) there as well. swissspidy
Needs Patch 60718 Awareness of permission after updating cores, themes and plugins Upgrade/Install trunk normal normal Awaiting Review enhancement new 2024-03-07T04:41:04Z 2024-03-07T05:46:41Z "This is the major security concern now a day when people install/update plugins or themes on DEV/STAG/PROD after changing respective directory permission from **755** (7=rwx 5=r-x 5=r-x) to **777** (7=rwx 7=rwx 7=rwx)
Once installation/updation is complete, people forget to restore directory permission, and due to this, hackers might inject scripts into those directories.
To prevent this, we have to check directories and file permissions for it and give the notice on top of the admin section.
It will help to reduce security threats. " Girishpanchal
Needs Patch 60717 Font Library: Add an ability to replace font General trunk normal normal Awaiting Review enhancement new 2024-03-07T03:31:40Z 2024-03-17T18:54:01Z Instead of the error or notice that the font already exists, the font library should allow replacing the font. Sometimes a font can be corrupted for some reason, and you need to update it. So, the better flow should be to ask the users if they want to replace the font(s). oglekler
Needs Patch 60716 "Font Library: Replace error message ""A font face matching those settings already exists"" with notice" General trunk normal normal Awaiting Review defect (bug) new 2024-03-07T03:25:56Z 2024-03-17T18:53:45Z If the font already exists, it is not an error, and should not scare the user. oglekler
Has Patch / Needs Testing 60713 remove 'array_merge(...)' is used in a loop and is a resources greedy construction. from generate_rewrite_rules pbearne Rewrite Rules normal normal Awaiting Review defect (bug) assigned has-patch 2024-03-07T00:06:18Z 2024-03-12T18:03:03Z pbearne
Needs Patch 60710 save_post_{$post->post_type} hook returns inconsistent $_POST['tax_input'] format Taxonomy 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-06T19:55:52Z 2024-03-06T19:55:52Z "In the save_post_{$post->post_type} hook:
**Case 1**: If we do not make any changes to the taxonomy `$_POST['tax_input'][$term]` returns a comma delimited string WITH a space.
Output Example: ''Maple, Spring, Summer, Winter''
**Case 2**: If we modify the taxonomy (adding or removing), it eliminates the space:
Output Example: ''Spring,Summer,Winter''
Proposed solution, eliminate the space in the first case for consistency. " jenUnderscore_
Needs Patch 60708 REST page 2 item 0 === page 1 item 99 when requesting 100 posts from a post type REST API 6.4.3 normal major Awaiting Review defect (bug) new 2024-03-06T16:39:22Z 2024-03-11T06:51:24Z "in our case of a custom WP post type default REST API call
page 2 item 0 === page 1 item 99
when requesting 100 items per page.
(as of writing this.)
Demo:
https://deananddavid.com/wp-json/wp/v2/catering_article?lang=de&orderby=menu_order&order=asc&_fields=acf,catering_category,featured_media,id,title&per_page=100&page=1
https://deananddavid.com/wp-json/wp/v2/catering_article?lang=de&orderby=menu_order&order=asc&_fields=acf,catering_category,featured_media,id,title&per_page=100&page=2
This is no issue when requesting 99 items per page." vialars
Has Patch / Needs Testing 60706 Tests: Reduce usage of assertEquals for 6.6 Build/Test Tools normal normal 6.6 task (blessed) new has-patch 2024-03-06T06:55:52Z 2024-03-06T06:56:39Z "Follow-up to:
* #59655 (6.5)
* #58956 (6.4)
* #57855 (6.3)
* #56800 (6.2)
* #55654 (6.1)
* #54726 (6.0)
* #53364 (5.9)
* #52482 (5.8)
* #38266 (5.7)
The `assertEquals()` test method does not check that the types of the expected and actual values match. This can hide subtle bugs especially when the values are falsey.
Tasks:
* Switch to using `assertSame()` when the type of the value in the assertion is important
* Replace overall usage of `assertEquals()` with type-strict assertion methods, with the aim of potentially removing its usage altogether
To help ease the effort of merging tests, changes should also be made upstream in the Gutenberg repository." SergeyBiryukov
Has Patch / Needs Testing 60705 Test tool and unit test improvements for 6.6 Build/Test Tools normal normal 6.6 task (blessed) new has-patch 2024-03-06T06:53:46Z 2024-03-06T06:58:16Z "Previously:
* #59647 (6.5)
* #58955 (6.4)
* #57841 (6.3)
* #56793 (6.2)
* #55652 (6.1)
* #54725 (6.0)
* #53363 (5.9)
* #52625 (5.8)
* #51802 (5.7)
* #51344 (5.6)
This ticket is for various fixes and improvements in PHPUnit tests that don't have a more specific ticket, as well as general improvements to the GitHub Actions workflows that run automated testing." SergeyBiryukov
Needs Patch 60701 Bump default theme versions for WordPress 6.6 Bundled Theme normal normal 6.6 task (blessed) new 2024-03-06T05:03:35Z 2024-03-06T05:03:35Z "All bundled themes from 2010 to 2024 will need a version bump for the 6.6 release.
Previously:
#59816 - 6.5
#58832 - 6.4
#57857 - 6.3
#57689 - 6.2
#56450 - 6.1
#55754 - 6.0
#54783 - 5.9
#53277 - 5.8
#52704 - 5.7
#51919 - 5.6
#50889 - 5.5
#49743 - 5.4" mukesh27
Has Patch / Needs Testing 60700 Coding Standards fixes for WP 6.6 General normal normal 6.6 task (blessed) new has-patch 2024-03-06T05:03:13Z 2024-03-18T15:44:26Z "Previously:
- #59650 (6.5)
- #58831 (6.4)
- #57839 (6.3)
- #56791 (6.2)
- #55647 (6.1)
- #54728 (6.0)
- #53359 (5.9)
- #52627 (5.8)
- #51799 (5.7)
- #50767 (5.6)
- #49542 (5.5)
- #49222 (5.4)
- #47632 (5.3)
- #45934 (5.1)" mukesh27
Needs Patch 60699 Docblock improvements for 6.6 General normal normal 6.6 task (blessed) new 2024-03-06T04:57:35Z 2024-03-11T14:06:52Z "Previously:
- #59651 (6.5)
- #58833 (6.4)
- #57840 (6.3)
- #56792 (6.2)
- #55646 (6.1)
- #54729 (6.0)
- #53399 (5.9)
- #52628 (5.8)
- #51800 (5.7)
- #50768 (5.6)
- #49572 (5.5)
- #48303 (5.4)
- #47110 (5.3)
- #46543 (5.2)
- #42505 (5.1)
- #41017 (4.9)
- #39130 (4.8)
- #37770 (4.7)
- #32246 (4.6)" SergeyBiryukov
Needs Patch 60698 Add optimized set lookup class. General trunk normal normal Awaiting Review feature request new 2024-03-06T01:18:34Z 2024-03-06T01:18:34Z "In the course of exploratory development in the HTML API there have been a few times where I wanted to test if a given string is in a set of statically-known strings, and a few times where I wanted to check if the next span of text represents an item in the set.
For the first case, `in_array()` is a suitable method, but isn't always ideal when the test set is large.
{{{#!php
contains( '¬in' ) ) {
…
}
while ( true ) {
$was_at = $at;
$at = strpos( $text, '&', $at );
if ( false === $at ) {
$output .= substr( $text, $was_at )
break;
}
$name = $named_character_reference->read_token( $text, $at );
if ( false !== $name ) {
$output .= substr( $text, $was_at, $at - $was_at );
$output .= $named_character_replacements[ $name ];
$at += strlen( $name );
continue;
}
// No named character reference was found, continue searching.
++$at;
}
}}}
----
Further, because WordPress largely deals with large and relatively static token sets (named character references, allowable URL schemes, file types, loaded templates, etc…), it would be nice to be able to precompute the lookup tables if they are at all costly, as doing so on every PHP load is unnecessarily burdensome.
A bonus feature would be a method to add and a method to remove terms.
----
In [https://github.com/WordPress/wordpress-develop/pull/5373 #5373] I have proposed such a `WP_Token_Set` and used it in [https://github.com/WordPress/wordpress-develop/pull/5337 #5337] to create a spec-compliant, low-memory-overhead, and efficient replacement for `esc_attr()`.
The replacement `esc_attr()` is able to more reliably parse attribute values than the existing code and it does so more efficiently, avoiding numerous memory allocations and lookups." dmsnell
Has Patch / Needs Testing 60696 Block hooks: Allow insertion of a hooked block with attributes Editor normal normal Awaiting Review enhancement new has-patch 2024-03-05T21:07:33Z 2024-03-05T21:16:21Z "Previously, the `hooked_block_types` and `hooked_block_{$hooked_block_type}` filters were introduced to allow templates to be extended with blocks by third parties.
While those two filters work well with unique blocks, they prove challenging when working with generic blocks that can be customized via attributes. Attempting to hook a block into an area that has already inserted the same block type, but with different attributes won't work with the existing filters.
[This PR](https://github.com/woocommerce/woocommerce/pull/44860) demonstrates how attempting to set attributes via the `hooked_block_{$hooked_block_type}` filter will overwrite all of the same block types that have been hooked in.
It may be possible that block hooks aren't the appropriate venue for this API, but a way to insert blocks with attributes into templates is quite useful, even in the context of the core editor.
**Requirements:
**
* [ ] Allow insertion of blocks with block attributes in a single filter
* [ ] Allow checking anchor block properties before inserting hooked blocks
* [ ] (optional, but preferred) Allow nesting hooked blocks onto previous hooked blocks" joshuaflow
Has Patch / Needs Testing 60695 Links in the admin-menu are generated incorrectly for mu-plugins Administration normal normal Awaiting Review defect (bug) new has-patch 2024-03-05T15:27:57Z 2024-03-05T16:05:37Z "The function _wp_menu_output in wp-admin/menu-header.php checks if a file exists in the WordPress plugin directory. But it never checks if the file exists in the mu-plugins directory.
The result of this is that some plugins behave in an unexpected way when moved to mu-plugins. Especially their admin-menus stop working. One example of such a plugin is WPML.
E.g. lines 165-175:
{{{#!php
$arrow
"";
}
}}}
Not how the code in the 5th line only checks for WP_PLUGIN_DIR and not for WPMU_PLUGIN_DIR. This happens a few more times in this function.
" partiellkorrekt
Needs Dev / Bug Wrangler Feedback 60694 INDEX command denied to user 'wordpress'@'localhost' for table 'wp_trp_dictionary_bg_bg_en_us' Upgrade/Install 6.4.3 normal normal Awaiting Review defect (bug) new dev-feedback 2024-03-05T15:14:32Z 2024-03-05T15:14:32Z "Fresh install of Version 6.4.3. The only active plugin is TranslatePress - Multilingual Version 2.7.2 (Akismet and Hello Dolly are installed but not active).
Loggin in as admin, the following error is displayed:
INDEX command denied to user 'wordpress'@'localhost' for table 'wp_trp_dictionary_bg_bg_en_us'.
phpMyAdmin shows that the wordpress user does not have the 'INDEX' privilege.
Is there a reason why the INDEX privilege not be enabled for the wordpress database user?" 4x4ever
Needs Dev / Bug Wrangler Feedback 60693 """Previously approved comment"" for logged out users bug" Comments 6.4.3 normal normal Awaiting Review defect (bug) new dev-feedback 2024-03-05T14:30:41Z 2024-03-07T17:00:03Z "When ""Comment author must have a previously approved comment"" is checked in the discussion settings, comments made by registered users who are logged out, go to moderation every time. The check comment function looks for previous comments under their user id but if they have only commented while logged out, no id is recorded. This bug has caused our users and our team major frustration. Can someone please address? Thanks!" jmorti
Needs Dev / Bug Wrangler Feedback 60692 Plugin dependencies: Allow a mu-plugin to fulfil a dependency Upgrade/Install trunk normal normal 6.6 enhancement new dev-feedback 2024-03-05T10:59:05Z 2024-03-05T12:00:04Z "See discussion on #60504 for background.
An inactive plugin that has a dependency that is fulfilled by a mu-plugin is prevented from being activated as its dependency is considered unfulfilled. It should be possible for a mu-plugin to fulfil a plugin dependency.
It may be that a new filter or a default mu-plugin loader needs to be introduced so facilitate this." johnbillion
Needs Patch 60690 Consistency in Theme Update Warnings in Menu Menus normal normal Awaiting Review enhancement new 2024-03-05T10:29:33Z 2024-03-05T10:29:33Z "When plugins are plugins pending update, a warning appears under ""Plugins"". However, even if are pending theme updates, the same warning does not appear under ""Appearance"".
Considering that the security issues of an outdated theme can be the same as those of an outdated plugin, I think we should display the same warning in both cases.
In the following image you can see a site with an outdated theme and plugin. At a glance you can only see a warning about ""Plugins"", but no warning about ""Apparence"", only inside ""Apparence > Themes"".
Although ""Apparence"" has no updates, it would be nice to have the same warning as in ""Plugins"".
I am attaching pictures to illustrate this." Marc4
Needs Dev / Bug Wrangler Feedback 60689 Concerning use of external libraries External Libraries normal normal Awaiting Review feature request new dev-feedback 2024-03-05T08:20:16Z 2024-03-05T10:17:53Z "As you get more advanced in using wordpress the need arises to use external libraries like bootstrap,font library,icon libraries,tailwind etc,off course this can be added using insert code plugins.the biggest disadvantage of this is that
1.you cannot maintain libraries version
2.You cannot delete the libraries.
This problem can be solved through a feature request to create an interface to manage external libraries.In this feature:
1.User adds external libraries through a url
2.user can edit the libraries url
3.user can delete the libraries,libraries ceases to exist in the wordpress environment
4.Ability of the interface to distinguish/or give user opportunity to distinguish between and
}}}
(again, you see ‘&‘ instead of just ‘&’)
You can find these issues on: https://forcesail.ru/" forcesail
Needs Dev / Bug Wrangler Feedback 59538 Theme update message showing user wrong theme popup Themes 6.3.2 normal normal Awaiting Review defect (bug) new dev-feedback 2023-10-04T11:47:21Z 2023-10-06T11:54:22Z "When you are updating the theme and another theme popup is opened then the theme updated message shows on the opened popup twice message.
Video link: https://www.awesomescreenshot.com/video/21305588?key=95614ad9bc790ca5d1a26fa52a2e75e9" praful2111
Needs Reporter Feedback / Steps To Reproduce 59537 Quote toolbar is not shown for mobile view Editor 6.4 normal minor defect (bug) assigned reporter-feedback 2023-10-04T11:42:28Z 2023-12-04T19:39:23Z "1. Create a post
2. Add a quote
3. Check that the capture toolbar in the quote block is shown
4. Change screen size (ex. 768X1024)
5. Quote toolbar is not shown
" oksankaa
Needs Patch 59535 Page/Post scrolls up while converting quotes to paragraph Editor 6.3.1 normal minor Awaiting Review defect (bug) new 2023-10-04T11:37:35Z 2023-10-05T04:40:02Z "I found this while testing the capture toolbar for the quote block for WordPress 6.4 beta2, but was able to reproduce it in 6.3.1.
== Issue
In the block editor, Page/Post scrolls up while converting a quote to a paragraph.
== Steps to Reproduce
1. Open a post or page.
2. Insert Title and long text so that scroll bar appears.
3. At the end insert quote block
4. Write a quote and citation
5. Click on the block so that quote block toolbar appears
6. Click on quote icon (first icon in the quote toolbar)
7. Click on transform to ""Paragraph""
== Actual Result:
Page/Post scrolls up while converting a quote to a paragraph.
== Expected Result:
Page/Post should not scroll up while converting a quote to a paragraph.
" hardikgohil
Needs Patch 59529 Twenty Fourteen: Search bar showing on different line on iPadOS 17 Bundled Theme normal major Awaiting Review defect (bug) new 2023-10-04T01:38:45Z 2023-10-18T14:55:52Z "The search toggle element doesn't show on the same level as the menu for iPadOS 17 devices — that is both when checking on Chrome and Safari.
1. Get a device with iPadOS 16 and reproduce it showing as expected: https://wp-themes.com/twentyfourteen/
2. Update to iPadOS 17 and see the issue with the search on Safari or Chrome
PS: I'm considering this major severity as the issue is on an important part of a default theme — even if it's an old theme and we can only reproduce on IOS 17 devices.
Originally reported by @fgruen here: https://wordpress.org/support/topic/display-problem-with-search-box-on-apple-ipad/?view=all" foosantos
Needs Patch 59525 Add filter for `get_mu_plugins()` Plugins normal normal Awaiting Review enhancement new 2023-10-03T16:33:45Z 2023-10-25T22:35:43Z "In https://core.trac.wordpress.org/ticket/57278, there was a need to be able to filter MU-plugins on the UI. However, for WP-CLI, when we call `wp plugin list` for MU-plugins, it calls `get_mu_plugins()`. It'd be nice if it was filterable to match the changes on the UI end.
It does look like WP-CLI does have the filter `all_plugins` for the drop-in plugins at https://github.com/wp-cli/extension-command/blob/17b16548b5775616dcbbd92f7836e67bba02e8ba/src/WP_CLI/Fetchers/Plugin.php#L23 to match Core's at https://github.com/WordPress/WordPress/blob/2a2cbb3b497fa1b95f15b0d11a47a761fa2ccc21/wp-admin/includes/class-wp-plugins-list-table.php#L104, but that appears to only apply for the drop-ins." rebasaurus
Has Patch / Needs Testing 59522 Bug handling multisites where main site URL and main blog URL are different Networks and Sites 6.3 normal normal Awaiting Review defect (bug) new has-patch 2023-10-03T10:34:20Z 2024-01-30T17:00:13Z "WordPress 6.3 and up appear to break handling of multisites where the `BLOG_ID_CURRENT_SITE` and the domain and path for the network in the `wp_site` table do not point at the same blog. It treats the the site configured in `wp_site` as if it is also the main blog in the network (over-riding `BLOG_ID_CURRENT_SITE`). This results in image paths being broken on the site set in `wp_site` if it is not in the root directory.
How to recreate the bug:
1. In WordPress 6.2 or below, create a directory-based multisite, with 2 sites in the network, site 1 at just `http://localhost` and site 2 at `http://localhost/foo`. In `wp-config.php`, set both `SITE_ID_CURRENT_SITE` and `BLOG_ID_CURRENT_SITE` to `1`. In the `wp_site` table (which should only contain 1 entry, with ID `1`), set the domain to `localhost` and the path to `/foo/`.
2. Upload an image to the media library of `http://localhost/foo`. It should display correctly in the library, and have a URL of `http://localhost/onsblog/wp-content/uploads/sites/foo/[year]/[month]/[your-filename]`.
3. In the network site list, at `http://localhost/foo/network/sites.php`, `localhost` should be marked as the main site, reflecting the `BLOG_ID_CURRENT_SITE` constant.
4. Upgrade to WordPress 6.3 or 6.3.1.
5. In the media library of `http://localhost/foo`, the uploaded image will no longer display. If you view the image properties, it will report an image URL of `http://localhost/onsblog/wp-content/uploads/[year]/[month]/[your-filename]`, i.e. the subsite part of the path is missing.
6. In the network site list, `localhost/foo` is now marked as the main site, which does not reflect the `BLOG_ID_CURRENT_SITE` setting.
This bug also results in all images uploaded via the classic editor prior to 6.3 404-ing in the frontend on the affected subsite post-upgrade.
This behaviour was introduced in this commit: https://github.com/WordPress/WordPress/commit/05f19b1ed76af6d60855a1d44b8c15a166c5e36f, presumably unintentionally given the commit message. This line specifically is the issue: https://github.com/WordPress/WordPress/commit/05f19b1ed76af6d60855a1d44b8c15a166c5e36f#diff-254cbb80547c44f4b3a7ef37746bb5eb9f42bf29f0de5215034a8d1015928fecR242.
When the `WP_Network` object is populated via the `WP_Network::get_instance()` method, the `$id` property is populated via a WPDB query: https://github.com/WordPress/WordPress/blob/master/wp-includes/class-wp-network.php#L106. This returns the `id` from the database as a string (normally `'1'`), which is then passed into `WP_Network::__construct()`, resulting in the `id` property being populated as a string. Therefore this check:
{{{#!php
( defined( 'SITE_ID_CURRENT_SITE' ) && (int) SITE_ID_CURRENT_SITE === $this->id )
}}}
will always return false, as `$this->id` will be a string. Either `$this->id` should also be cast as an integer, or the `WP_Network::__construct()` method should perform type enforcement, e.g. by calling the same class's `__set()` method to set properties.
" robdxw
Needs Patch 59521 Issue with update_post_thumbnail_cache if using get_posts Media 6.3.1 normal normal Awaiting Review defect (bug) new 2023-10-03T09:25:40Z 2023-10-03T09:25:40Z "Hello,
I got this:
''Warning: Attempt to read property ""ID"" on int in /wp-includes/post-thumbnail-template.php on line 116''
I'm using:
{{{#!php
'ids' ) );
foreach ( $posts as $post_id ) :
$thumb = get_the_post_thumbnail( $post_id );
endforeach;
}}}
The **update_post_thumbnail_cache()** used in **get_the_post_thumbnail()** assumes **$wp_query->posts** always contains an array of **$posts objects**, while it can be an array of $posts IDs.
To prevent the warning it would be appropriate to check that $post is actually a post object.
The patched code:
{{{#!php
posts as $post ) {
$post = get_post( $post ); // Add this or check if is_integer( $post )
$id = get_post_thumbnail_id( $post->ID );
}}}
Thanks
Kind Regards" Xendo
Needs Patch 59519 Reconsider including Google branding and product in WordPress core (Google Fonts) General 6.4 normal normal Awaiting Review feature request new 2023-10-02T18:49:44Z 2023-10-05T16:09:55Z "In this [https://github.com/WordPress/gutenberg/issues/53307 Gutenberg Github issue], a Google Fonts integration is being added directly to WordPress core.
I know the great work being done is with the best of intentions: to help streamline things for users.
However, despite copying the font from Google Fonts, including this Google integration in WordPress core has a few problems.
- It is a ""vote of confidence"" in Google by the WordPress project
- It's free advertising for a brand in WordPress core
- It opens up future political problems for WordPress leadership to deal with
Are we willing to say that the WordPress project is giving a ""vote of confidence"" for Google, the brand? Are we willing to provide free marketing for Google in this way?
Furthermore, any other brands we might add to WordPress core in the future would also be getting that same ""vote of confidence"" from the WordPress project. Are we also willing to do it for them?
If so, how are we deciding who gets these ""votes of confidence""? Is there a process a brand should go through to earn this vote of confidence? What steps should they take? When do we/they know it's enough?
If we add this Google integration by default in WordPress core, it opens up a bunch of problems we can avoid. WordPress has a plugin interface for this exact type of thing. Why not use it? This could surely be made into a plugin, right?
So my request here is to reconsider adding a Google Fonts integration to WordPress core itself, and allowing it to be a plugin instead.
While I believe that manually uploading fonts is good enough, if a core integration with an outside font API is required, I would propose that it should use Openverse. This has already been done with the Media Library.
Additionally, (and this is somewhat beside the main point) but Google, specifically, doesn't have a great track record for keeping its products alive. The number of products killed by Google is astounding: https://killedbygoogle.com/
They also **just** sold their domains service to Squarespace, a direct competitor to the WordPress project.
In my opinion, these are reasons enough to be wary of adding Google products and branding directly to WordPress core.
" johnstonphilip
Needs Patch 59518 I getting ::marker and unable to remove bacause html not support Widgets 6.3.1 normal normal Awaiting Review defect (bug) new 2023-10-02T18:01:49Z 2023-10-02T18:01:49Z "we know
should be inside or
but here is without or
that's why a default ::maker showing each widget:
screenshot: (https://prnt.sc/zRxK-EEXoGej)
screenshot 2: (https://prnt.sc/cPCKcLZ3YEfq)" bmyadav91
Has Patch / Needs Testing 59516 Improve cache key generation in query classes thekt12 Query normal normal Future Release defect (bug) assigned has-patch 2023-10-02T13:35:14Z 2023-10-24T14:24:29Z "In query classes such as WP_Query, parameters like post_type enable the passing of an array of values. For instance, you can use post_type like this: ['post', 'page']. However, if a subsequent request is made with the array elements in a different order, like so: ['page', 'post'], it would lead to the generation of a different cache key, potentially causing the existing cache to be missed. Even though the cached results may be the same, this could result in a cache collision. It is advisable to reuse caches whenever possible to optimize performance.
This would effect the following cache keys.
- WP_Query
- WP_Term_Query
- WP_Network_Query
- WP_Site_Query
- WP_Comment_Query
Some sort of array sorting of the key values would mean that caches could be reused. " spacedmonkey
Needs Patch 59515 Multiple color palettes and font pairs Themes 6.3.2 normal normal Awaiting Review feature request new 2023-10-02T13:14:07Z 2023-10-02T19:23:41Z "I have some suggestions for block themes.
We can create a single color palette for a theme. When you want to change the color palette, a custom palette can be created.
So why don't themes have multiple predefined color palettes? Maybe you could say that style variations support this feature. Yes, partially. But style variations have many theme features; colors, fonts, spacing, etc. Users may only want to change the color palette. The theme's colors change with a single click. Users can add custom colors if they wish.
Themes can also have predefined font pairs. (Combination of two fonts)
Theme developers need to define keywords for color palettes and font pair to achieve both of these options. For example, the keywords ""primary"", ""secondary"", ""tertiary"", ""foreground"", ""background"" are reserved for color palettes. Or for font pairs ""primary font"", ""secondary font""...
This way users replace colors or font pairs with predefined ones." arkenon
Has Patch / Needs Testing 59514 Add more context to split_the_query filter Query 3.4 normal normal 6.6 enhancement new has-patch 2023-10-02T11:41:06Z 2024-03-13T15:45:24Z "Current the split_the_query filter has the current WP_Query instance as context. However to calculate the value you need the value variables.
- $old_request
- $limits
- $fields
- $q ( query arguments ).
It is worth noting that `$this->request` can be received by `WP_Query` instance and `$wpdb->posts` can be received from global $wpdb.
With this extra context, will be make the filter much more useful.
" spacedmonkey
Needs Patch 59511 Navigation Block issue Editor 6.3.1 normal normal Awaiting Review defect (bug) new 2023-10-01T16:20:25Z 2023-10-28T05:02:20Z While trying to add and edit description or any metadata on nav items. As soon as I press any key, it gets refresh. amitpomu
Has Patch / Needs Testing 59510 Add filter for the block-template viewport meta tag General 6.4 normal normal Awaiting Review enhancement new has-patch 2023-09-30T20:43:31Z 2023-09-30T21:04:09Z "The base block-template.php used for full site editing does not provide a hook for modifying the viewport meta tag. Despite being inserted into wp_head by the `_block_template_viewport_meta_tag` action hook, the actual tag is basically hard coded and untouchable: https://github.com/WordPress/wordpress-develop/blob/00ed25e2c9b20607418cbe8a6103c336d1bf92bd/src/wp-includes/block-template.php#L273-L275.
This ticket introduces a new filter which allows for customization of this meta tag. " joemaller
Needs Docs or Unit Tests 59509 Shortcode attributes named 0 are ignored Shortcodes 6.3.1 normal normal Awaiting Review defect (bug) new needs-unit-tests 2023-09-30T12:14:06Z 2023-10-04T10:02:59Z "Shortcode attributes in the form `0=...` are not picked up during parsing.
This is because the parser checks for an empty name with `empty(..)`, which also returns true for the string `'0'`." ourous
Needs Docs or Unit Tests 59507 global-styles-and-settings.php in wp_theme_has_theme_json Themes 6.3.1 normal normal Awaiting Review defect (bug) new needs-unit-tests 2023-09-29T18:45:19Z 2023-10-02T17:29:27Z "Wordpress 6.3.1 , php 8.1.23
{{{#!php
Taxonomy normal normal Awaiting Review enhancement assigned has-patch 2023-09-29T14:49:59Z 2023-09-29T15:01:44Z "Currently, there is no option to get child terms of multiple parent terms. There is a
'**parent**' parameter that returns child terms of only one parent term.
There is a '**post parent in**' parameter for '**WP_Query**' and '**get_posts()**' to get child posts of multiple parent posts, but there is no similar parameter for '**WP_Term_Query**', and '**get_terms()**'.
So, I suggest a new parameter '**parents in**' to get child terms from multiple parent terms IDs. The parameter on get_terms() will be like below:
{{{#!php
'category',
'parents__in' => array( 2, 3, 4 )
) );
}}}
" plugindevs
Needs Patch 59498 I18N issue in site editor Editor 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-29T10:02:37Z 2023-09-29T10:32:31Z "Hi,
In the site editor, when a template or a template part, or even a style...is modified, the following message is displayed: ""Last modified a few seconds ago"".
This string corresponds to: [https://translate.wordpress.org/projects/wp/dev/fr/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=135&filters%5Btranslation_id%5D=131480]
and as it's a variable we can't translate it.
In french, for example, the message is ""Dernière modification il y a a few seconds"".
In spanish, the message is ""Última modificación hace a few seconds""
We have a break in I18N here, due to this variable.
Thanks for the modification.
" jdy68
Needs Reporter Feedback / Steps To Reproduce 59497 There are pages or posts are not working update General 6.4 normal normal Future Release defect (bug) new close 2023-09-29T09:20:22Z 2023-12-14T20:16:31Z "I recently performed a fresh installation of WordPress 6.4. However, I have encountered an issue where I am unable to update posts or pages. I have attached a video URL to illustrate the problem. Please review the video, and if you have any questions or can identify the issue, kindly let me know.
Video URL : https://www.awesomescreenshot.com/video/21181741?key=0bcb4cbfebeac453b9dcd5d8c428290a
### Environment
WordPress: 6.4-beta1
PHP: 8.0.28
Server: Apache/2.4.56 (Unix) OpenSSL/1.1.1t PHP/8.0.28 mod_perl/2.0.12 Perl/v5.34.1
Database: mysqli (Server: 10.4.28-MariaDB / Client: 8.0.28)
Browser: Chrome 117.0.0.0 (macOS)
Theme: Twenty Twenty-Four 1.0
MU-Plugins: None activated
Plugins: WordPress Beta Tester 3.5.4" utsav72640
Has Patch / Needs Testing 59494 Passing orderby as array in URL results in Notice Administration 4.0 normal normal Awaiting Review defect (bug) new has-patch 2023-09-29T04:26:14Z 2023-10-04T12:32:15Z "Visiting `/wp-admin/edit.php?post_type=page&orderby[menu_order]=ASC&orderby[title]=ASC`
or
`/wp-admin/edit.php?post_type=page&orderby%5Bmenu_order%5D=ASC&orderby%5Btitle%5D=ASC` (URL encoded version) throws the following notice:
{{{
Notice: Array to string conversion in /Users/siddharth/Sites/osp/app/public/wp-includes/formatting.php on line 1104
}}}
Since multiple values can be passed to `orderby` in `get_posts()` or `WP_Query()`, this behaviour should also be consistent via URL.
There error occurs at this line: https://github.com/WordPress/WordPress/blob/master/wp-admin/includes/class-wp-list-table.php#L391 because `esc_attr()` expects a string but `$_REQUEST['orderby']` is an array." NomNom99
Has Patch / Needs Testing 59493 Blank CSS line removed from code Bundled Theme normal minor Future Release defect (bug) reopened has-patch 2023-09-29T00:05:51Z 2024-02-14T18:27:37Z Removed a blank CSS which is not needed in the code. ravipatel
Needs Patch 59491 Create more flexible structure for handling of feeds in admin news widgets Administration normal normal Awaiting Review enhancement new 2023-09-28T20:03:36Z 2023-09-28T20:03:36Z "Currently (in WordPress 6.3), the Admin widget ""WordPress events and News"" uses two feeds for presentation of WordPress news:
- https://wordpress.org/news/feed/
- https://planet.wordpress.org/feed/
(currently, the widget shows the headlines for the two latest posts in the ""news"" feed and the headlines for the three latest posts in the ""Tavern"" feed. But this configuration has changed at various points: some posts have been listed with excerpts, the number of posts has changed, etc.)
Both these URL's can be ""translated"", so that localized versions may, for instance, divert this to the corresponding newsfeed in their own language. Several language teams use this opportunity.
I'd like to propose a more flexible structure for these posts, where a locale team would be able to configure posts to be included from 1, 2 or 3 feeds, and how many posts to pull from each of these feeds.
It would probably be good to visualize to the user what feeds are used, along with their names.
If we lift this out of the localization structure to some Meta-structure, then we might even allow users to select a different locale's feed configuration (or even configure their own." tobifjellner
Needs Patch 59488 Add index to comment_type and comment_approved fields in comment table Comments 3.0 normal normal Awaiting Review enhancement new 2023-09-28T12:43:53Z 2023-09-28T12:43:53Z "Follow on from #58368
It is common to query comments by `comment_type` or `comment_approved`. There are several query done in the admin to get counts for different screens. But for sites with many comments, this results in slow returning queries. Add database indexes to these two fields to improve database performance. " spacedmonkey
Needs Patch 59486 Make test suite compatible with PHPUnit 10 / 11 Build/Test Tools 6.4 normal normal Future Release enhancement new 2023-09-28T08:58:42Z 2024-03-07T09:58:11Z "PHPUnit 10 was released back in February of 2023, and included [https://github.com/sebastianbergmann/phpunit/blob/10.0.0/ChangeLog-10.0.md#1000---2023-02-03 many breaking changes] - they completely rewrote the internal functionality of PHPUnit (mainly the event system for extending the test runner). Besides that, they upped the minimum PHP version to >=8.1, so for WordPress, it could only be used on PHP versions of >=8.1.
While this is not a huge and critical update, since the tests are running fine on PHP versions all the way up to version 8.3, it would be a good idea to start preparing for PHPUnit 10 compatibility.
Besides being up to date, it will allow external testing library maintainers (such as [https://github.com/lucatume/wp-browser wp-browser] or [https://github.com/dingo-d/wp-pest wp-pest]), to use the latest versions of both PHPUnit, or dependencies that are using PHPUnit 10 (such as PestPHP v2 which depends on PHPUnit 10).
I understand that this is a huge undertaking, but it's okay to have a ticket open for this (I didn't find one opened while searching, could be wrong tho), so that we can keep track of changes, and maybe create a roadmap or a to-do list of what needs to be fixed in order to make WordPress test suite compatible with PHPUnit 10.
" dingo_d
Has Patch / Needs Testing 59485 Invalid username Users 6.3.1 normal normal Awaiting Review defect (bug) new has-patch 2023-09-28T07:08:08Z 2023-09-29T13:37:09Z "Steps to reproduce this issue in the latest WordPress.
=>Go to WordPress admin
=>Register new user with username dot "".""
=>It will create a user with username dot and blank user_nicename
I have provide solution here.
Thanks!!" rinkalpagdar
Has Patch / Needs Testing 59482 Tests: Introduce Reflection API helper methods. costdev Build/Test Tools normal normal 6.6 task (blessed) assigned has-patch 2023-09-28T02:39:22Z 2024-02-26T11:05:32Z "In unit tests, the Reflection API is often used to get or set a `private` or `protected` property's value, or to invoke a `private` or `protected` method.
To do so, the `Reflection::setAccessible()` method must be called with `true` before use, then should be called again with `false` afterwards. There are quite a lot of instances in the test suite where the Reflection API is used, and for a decent number of these, accessibility is not reset.
For brevity, much like `assertSameSets()`, and to ensure that accessibility is always reset, this ticket aims to introduce new methods to the `WP_UnitTestCase_Base` class:
`::reflect_and_invoke( object $obj, string $method, mixed ...$args ) : mixed`
- Reflects a `private` or `protected` method and invokes it.
- Returns the method's return value.
`::reflect_and_get_value( object $obj, string $property ) : mixed`
- Reflects a `private` or `protected` property and gets its value.
- Returns the property's value.
`::reflect_and_set_value() : mixed`
- Reflects a `private` or `protected` property and sets its value.
- Returns the previous value for convenient resetting.
While this means the creation of new `Reflection` objects and two calls to `::setAccessible()` for each, I think that this is worthwhile as it helps us have a more robust test suite, with less code to write in test methods. Plus, we could also explore possible caching in future." costdev
Has Patch / Needs Testing 59481 dbDelta do useless request when type case is not the same between query and describe result Database 6.3 normal normal Awaiting Review defect (bug) new has-patch 2023-09-27T22:17:19Z 2023-10-17T22:40:55Z "While debugging why a call to `dbDelta` was not working, I discovered in the function output (an array of performed changes) that it was doing some useless changes: ""Changed type of wp_table.field from varchar(255) to VARCHAR(255)"".
Indeed, on my MySQL 8.0.31 Windows x64 version (installed by Wampserver), if I do ""DESCRIBE wp_table"", the ""Type"" column of the result is always lowercase. If somehow, you wrote your ""CREATE TABLE"" statements with a different case for varchar columns, dbDelta will detect a change. It does it only for varchar. If I change my varchar to be lowercase in the SQL I use for dbDelta, it doesn't try to change the type.
{{{#!php
prefix.'table` (
`object_id` INT(10) NOT NULL,
`group_term_slug` VARCHAR(255) NOT NULL
) '.$wpdb->get_charset_collate().';';
$result = dbDelta($sql); // Will contain both ""Created table wp_table"" and ""Changed type of wp_table.field from varchar(255) to VARCHAR(255)""
$sql = 'CREATE TABLE `'.$wpdb->prefix.'table` (
`object_id` INT(10) NOT NULL,
`group_term_slug` varchar(255) NOT NULL
) '.$wpdb->get_charset_collate().';';
$result = dbDelta($sql); // Will NOT contain ""Changed type of wp_table.field from varchar(255) to VARCHAR(255)"", only ""Created table wp_table""
}}}
" tristanleboss
Needs Patch 59479 'Erase Personal Data' simply doesn't work Privacy 6.3.1 normal critical Awaiting Review defect (bug) new 2023-09-27T20:42:01Z 2023-09-27T20:42:01Z "Here's the steps:
1. Set up a fresh WordPress install on my local machine
2. Add a new subscriber user to that WordPress install
3. Go to 'Export Personal Data'
4. Put in an export request without requiring email confirmation
5. Click on 'download personal data' on the new request entry
6. Open the downloaded content and confirm that there are fields that need to be deleted listed in 'export.json'. There are. These fields include: 'User Nice Name', 'User Email', 'User Display Name'
7. Go to 'Erase Personal Data'
8. Add a new erasure request without requiring confirmation
9. Click 'erase personal data' on the new erasure item
10. Get the message 'No personal data was found for this user'
Looking at the user's profile does show that nothing was erased or anonymized.
Per https://wordpress.org/documentation/article/tools-erase-personal-data-screen/:
'To confirm what data will be erased by this tool, Go to Tools > Export Personal Data from Administration Screens, and export Personal data.'
None of the items that were in the export were erased. The line in that doc doesn't make sense, as the export includes the user's username, which will definitely not be erased.
I have replicated this behavior on other hosted sites. There's something wrong with either the tool, the docs, or the feedback from WordPress. Please let me know where I'm going wrong, or if this is actually something that needs fixing." kingfisherwebdev
Needs Patch 59478 term_exists() to return false if no terms exist Taxonomy normal normal Awaiting Review enhancement new 2023-09-27T11:38:10Z 2023-09-27T13:51:31Z "When using the function `term_exists()` in `wp-includes/taxonomy.php`, it returns `null` if no terms exist. This behaviour seems incorrect and is inconsistent with other similar functions in the same file (`taxonomy_exists()` is one example).
It would make more sense to return `false`." rossb2
Needs Patch 59464 Images hard-coded in block theme templates lack `width` and `height` attributes Themes 6.4 normal normal 6.6 defect (bug) new 2023-09-26T17:10:25Z 2024-03-13T15:33:21Z "All images hard coded into block templates and patterns should have height and width attributes (applies e.g. to the TT4 theme).
It also prevents loading optimization attributes from being added to these images, so effectively this harms both load time performance and leads to layout shifts." spacedmonkey
Needs Patch 59462 Blocks: Introduce a way to enqueue view scripts only when needed for interactivity Editor 6.4 normal normal 6.6 enhancement assigned 2023-09-26T16:47:58Z 2024-02-12T20:55:48Z "It's based on the discussion started by @felixarntz in https://github.com/WordPress/wordpress-develop/pull/5262#discussion_r1336258326 when reviewing the current handling for interactive blocks back ported from the Gutenberg plugin for WordPress 6.4 Beta 1.
As of today, the view scripts get enqueued during block rendering in `WP_Block::render`:
https://github.com/WordPress/wordpress-develop/blob/6a61084beca680a78ed581d035d76d592d4ef117/src/wp-includes/class-wp-block.php#L271-L274
The custom code used with all core blocks applies the optimization by ensuring that these view scripts are only listed for enqueuing when the block instance of a given type is going to need them. For example, in the Image block, the view script is only useful when the Lightbox feature is activated for the block. There can be multiple block instances of the same type, so the view script gets removed from the list when the functionality isn't used. However, as soon as any block instance needs it, it must be added and never removed.
The reason why we didn't go with `wp_enqueue_script()` and `wp_dequeue_script()` is that the script handle would still need to get removed from `view_script_handles` for the block type as it gets automatically registered through `block.json` and later enqueued in the code path shared in the snippet above. It would still have to be manually enqueued when it is needed.
In the long run, I hope we can develop some sort of automatic detection based on Interactivity API directives that would inform whether a view script is necessary for the block. It could even allow us to introduce new strategies that allow loading scripts based on some triggers like: when a user hovers over a UI element or when the UI element is visible on the screen." gziolo
Needs Patch 59461 Gutenberg tools bar not appearing on top of the page (MacOS 13.5.2 and Safari 16.6) Editor 6.3.1 normal major Awaiting Review defect (bug) new 2023-09-26T16:27:47Z 2023-09-27T13:57:50Z "If I select ""toolbar over the blocks"" it works, but if I choose to have it fixed on top of the page it simply disappears.
On Chrome it perfectly works, so I think it's something related to Safari." locksoft
Needs Patch 59458 Duplicate PHP version in PHPUnit job names on GitHub Actions Build/Test Tools low trivial Future Release defect (bug) new 2023-09-26T14:00:05Z 2023-10-16T09:20:06Z "1. Go to [https://github.com/WordPress/wordpress-develop/commits/trunk Commits] page.
2. Click on any of the GitHub Actions result icons (a green check mark or a red cross mark).
3. Note the duplicate PHP version in the job names, e.g.:
{{{
PHPUnit Tests / PHP 7.0 / PHP 7.0 / MariaDB 10.11
PHPUnit Tests / PHP 7.0 / PHP 7.0 / MariaDB 10.11 multisite
PHPUnit Tests / PHP 7.0 / PHP 7.0 / MariaDB 10.4
PHPUnit Tests / PHP 7.0 / PHP 7.0 / MariaDB 10.4 multisite
PHPUnit Tests / PHP 7.0 / PHP 7.0 / MariaDB 10.6
PHPUnit Tests / PHP 7.0 / PHP 7.0 / MariaDB 10.6 multisite
...
}}}
The same is displayed in GitHub Actions checks on individual PRs.
Appears to be related to [56439]." SergeyBiryukov
Needs Patch 59457 Twenty Nineteen - Calendar block having issue with text color editor side. Bundled Theme normal normal Awaiting Review defect (bug) new 2023-09-26T13:16:19Z 2023-09-26T13:16:19Z "Steps to reproduce the issue :-
1. Activate Twenty Nineteen theme.
2. Choose Calendar block.
3. Apply text color from inspector.
You can able to see the choosen font color front side but in editor side it may not change as per the selected color.
I have attached video for better understanding.
Video URL :- https://share.cleanshot.com/DlNN9jMJzk7KJcYP4L44" nidhidhandhukiya
Needs Patch 59451 Saving draft and previewing page sometimes causes whole site to hang Autosave 6.3.1 normal major Awaiting Review defect (bug) new 2023-09-26T12:11:09Z 2023-09-26T12:11:09Z "Hello,
I've been running into an issue while editing pages, where I'll save a draft of a page and preview it, and occasionally the preview will start to load and never finish. At the same time, if I open any other page of the site in a new tab, it will also get stuck loading. The problem only resolves when I close all tabs viewing the site, meaning changes are lost.
This bug occurs on multiple WordPress sites, across different hosts, devices, locations and users. The only common factors I can see are Windows (10 & 11) Google Chrome (latest) and WordPress itself (latest, 6.3.1).
Many thanks,
Tristan" tristanmsg
Needs Patch 59446 Use script helper functions in admin to enable Content-Security-Policy opt-in Administration 5.7 normal normal Future Release defect (bug) new 2023-09-25T23:39:22Z 2023-11-03T17:27:17Z "In #58664 the script helper functions—`wp_get_script_tag()`, `wp_print_inline_script_tag()`, `wp_get_inline_script_tag()`—were leveraged to eliminate manual construction of script tags on the frontend and the login screen. These were introduced in #39941. This made it possible to opt-in (see [https://gist.github.com/westonruter/c8b49406391a8d86a5864fb41a523ae9 example plugin]) to a Strict Content-Security-Policy ([https://csp.withgoogle.com/docs/strict-csp.html Strict CSP]) to guard against any possible XSS exploits. The scope in #58664 was limited to the frontend and the login screen because of the sheer number of inline scripts printed on the wp-admin. Additionally, the site editor and block editors make use of dynamically-constructed script tags in the editor iframe which is a Strict CSP violation.
Much of the work to rework inline scripts to use `wp_print_inline_script()` in the admin can be seen in an [https://github.com/WordPress/wordpress-develop/pull/498 existing PR] (now stale) from @enricocarraro.
See also #59444 which is about how to improve the developer experience of working with these JavaScript string literals." westonruter
Needs Patch 59444 Add language injection comments for embedded languages in PHP General 6.4 normal normal Future Release enhancement new 2023-09-25T20:01:45Z 2023-09-26T17:27:22Z "As part of #4773 and #58775, many manually-constructed inline `
_edit_link`.
For most post types, including pages and posts, the `_edit_link` template looks something like this: post.php?post=%d.
get_edit_post_link() replaces the placeholder %d with the correct post id to build the edit post link.
Each page under Site Editor sidebar contains a link to admin/revision.php for page revisions.
However since the ""Go to editor"" links are constructed using `page_object->_edit_link`, they will always link to post editor.
I would expect the links to return me to the editor from which I last came.
The upshot is that we want the `_edit_link` template to vary depending on the origin of the referring URL. For pages, that means if we're coming from the Site Editor, the return template should be something similar to what the wp_template post object uses, which is site-editor.php?postType=%s&postId=%d&canvas=edit.
The question is ""what would be the best way to do this?""
Challenges:
1. admin/revision.php does not know where the revision is coming from, that is Post Editor vs Site Editor, but we could use some sort of `$_GET` query param on `revisions.php` to solve that. E.g., let's call it editor: `revision.php?revision=150&editor=site`. That is very specific and might be too narrow.
2. If 1, what then? Whether we grab the query param on the revision page and pass it to `get_edit_post_link` (thereby changing the function signature), or modify `get_edit_post_link` to do the lot internally, we'd still have to build the link accordingly to some pattern.
3. If 2, where would we store that pattern? `_edit_link` is taken. Maybe a new property on the post object? `_edit_site_link` or something.
It can be done I think without great fuss using the `get_edit_post_link` filter. With it we can return whatever we want.
We would just have to come up with migration approach for Core and I'm not sure what the best option would be.
Thank you for considering this issue!
For discussion and context see: https://github.com/WordPress/gutenberg/issues/51343#issuecomment-1724580879" ramonopoly
Has Patch / Needs Testing 59416 Add a GitHub Action which alerts contributors to a WordPress Playground link to use for testing PRs Build/Test Tools normal normal 6.6 task (blessed) new has-patch 2023-09-20T20:53:28Z 2024-03-06T06:44:58Z "The following approach could help bring in many new folks to help with testing PRs as they no longer need to have a local set up and able to load patches/PRs locally and can quickly jump into a WordPress Playground environment to help test.
----
Gutenberg has a GitHub Action that builds a ZIP of the plugin ([https://github.com/WordPress/gutenberg/blob/trunk/.github/workflows/build-plugin-zip.yml workflow file], [https://github.com/WordPress/gutenberg/actions/runs/6250831688 example Gutenberg PR with built ZIP attached]) which then [https://developer.wordpress.org/playground/ WordPress Playground] makes use of in the [https://playground.wordpress.net/gutenberg.html Gutenberg PR Previewer].
Taking that above functionality a step further and integrating for Core:
1. Add a GitHub Action for [https://github.com/WordPress/wordpress-develop/ wordpress-develop] that builds a ZIP of core for a PR (similar to the Gutenberg action).
2. Have that same action also add a comment to the PR with a link to a WordPress Playground that's built using the ZIP from the PR. So a comment like:
> Thanks <@PR-author>! Here's a link to a site created from this PR that can be used for testing: .
In my quick review of the [https://wordpress.github.io/wordpress-playground/ WordPress Playground documentation] it does reference an ability to [https://wordpress.github.io/wordpress-playground/build-your-first-app/#preview-pull-requests-from-your-repositorypreview pull requests from your repository], but I think that's crafted more for plugin developers and not for WordPress core itself. I took a look at [https://wordpress.github.io/wordpress-playground/api/client/interface/ReplaceSiteStep/ ReplaceSiteStep], but I think that's just for loading in alternate content and not a full on separate WordPress ZIP. So, this functionality might require additional functionality within WordPress Playground but I'll try and chase down folks from that team to comment here on the topic.
" JeffPaul
Needs Patch 59414 XML-RPC - add updateMedia endpoint XML-RPC normal normal Future Release enhancement new 2023-09-20T19:33:26Z 2024-03-05T15:53:56Z "In #58582, @thomashorta reported on alt attributes missing from the XML RPC endpoints. Fetching that data was fixed in [56637], but adding an endpoint to update media that specifically handles media data like alt attributes requires a more substantial enhancement.
From #58582:
Updating MediaItems through the XML-RPC API is also done directly by the Posts API, more specifically through wp.editPost (codex), which also doesn't support an alt field. This makes sense, as this API is more generic, but at the same time, there are no specific updateMedia methods in the Media API.
Suggestion for updating
I'm not sure about this one, but I think a new method in the Media API would be needed (e.g.: wp.updateMediaItem) to properly manipulate a specific input struct and call the Post update functions internally." joedolson
Needs Patch 59413 PHP Warning: Undefined property: stdClass::$plugin Plugins 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-20T17:17:32Z 2023-10-27T22:06:50Z "Just checking php www-error.log and saw that there was this error:
PHP Warning: Undefined property: stdClass::$plugin in /var/www/html/my-website/wp-admin/includes/class-wp-automatic-updater.php on line 228
Site is working as usual but the log is full of these warnings.
PHP 8.0.27
Apache 2.4.37
WordPress 6.3.1" zerofoolcoder
Needs Dev / Bug Wrangler Feedback 59410 Getting waring related Warning: array_flip() expects parameter 1 to be array Administration 6.3.1 normal normal Awaiting Review defect (bug) new close 2023-09-20T09:51:01Z 2023-10-03T11:23:07Z "Hey Core Team,
when I am using the switch user plugin and after switching user gets a warning on the top bar more information you can see the mentioned screenshot.
For more information see mentioned screenshot.
" sumitsingh
Needs Patch 59408 how to fix below error Plugins 6.3 normal critical Awaiting Review defect (bug) new 2023-09-20T09:02:30Z 2023-09-20T09:02:30Z Fatal error: Uncaught Error: Call to undefined function topdeal_options() in /home/u380733166/domains/books.lk/public_html/wp-content/plugins/sw_woocommerce/includes/sw-woocommerce-shortcodes.php:960 Stack trace: #0 /home/u380733166/domains/books.lk/public_html/wp-includes/class-wp-hook.php(310): topdeal_buton('') #1 /home/u380733166/domains/books.lk/public_html/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(NULL, Array) #2 /home/u380733166/domains/books.lk/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /home/u380733166/domains/books.lk/public_html/wp-includes/general-template.php(3069): do_action('wp_footer') #4 /home/u380733166/domains/books.lk/public_html/wp-includes/template-canvas.php(25): wp_footer() #5 /home/u380733166/domains/books.lk/public_html/wp-includes/template-loader.php(106): include('/home/u38073316...') #6 /home/u380733166/domains/books.lk/public_html/wp-blog-header.php(19): require_once('/home/u38073316...') #7 /home/u380733166/domains/books.lk/public_html/index.php(17 in /home/u380733166/domains/books.lk/public_html/wp-content/plugins/sw_woocommerce/includes/sw-woocommerce-shortcodes.php on line 960 nirmal1985
Needs Patch 59403 Inconsistent version numbering Upgrade/Install normal minor Awaiting Review defect (bug) new 2023-09-20T07:19:32Z 2023-09-26T16:03:07Z "WP releases versions with a mix of Major/Minor and Major/Minor/Release, which causes issues when using version_compare with a consistent annotation.
e.g.
WP 6.3
WP 6.3.1
If you use `version_compare( $wp_version, '6.3.0', '<' )` it will be unexpectedly true-ish for WP 6.3, since 6.3.0 is newer than 6.3 in PHP versioning.
Versioning should be made consistent with Major/Minor/Release not only for WP core from the next release, but ideally also a requirement for all submitted plugins, to avoid unexpected behavior due to inconsistent versioning." kkmuffme
Needs Early Attention 59402 Plugin cannot be uninstalled if uninstall crashes swissspidy Plugins 2.7 normal normal 6.6 defect (bug) assigned has-patch 2023-09-20T06:59:37Z 2024-02-19T09:31:50Z "If a plugin register the ""register_uninstall_hook"" conditionally (e.g. only on activation,...) a plugin cannot be uninstalled anymore if it exits (e.g. timeout,...) during uninstall.
This is because the uninstall file/callback is removed from the option before the actual uninstall happens:
https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-admin/includes/plugin.php#L1253
https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-admin/includes/plugin.php#L1269
" kkmuffme
Needs Patch 59396 Allow the user to add a poster to YouTube videos Editor 6.4 normal normal Awaiting Review feature request new 2023-09-19T16:07:10Z 2023-09-19T16:07:10Z "YouTube embedded videos get YouTube's branding before they get fired, which is not really clean.
Instead, I'd like being able to set a poster." schwipps
Changes Requested 59390 Incorrect method / function args used in bin/tests/core/tests/rest-api/wpRestMenuItemsController.php Menus 5.9 normal normal 6.6 defect (bug) new changes-requested 2023-09-19T11:47:40Z 2024-02-17T16:14:41Z "The `Tests_REST_WpRestMenuItemsController::check_get_menu_item_response` method accepts 2 arguments, however 3 are passed to the method in https://core.trac.wordpress.org/browser/trunk/tests/phpunit/tests/rest-api/wpRestMenuItemsController.php?rev=56549#L885
It feels like the `Tests_REST_WpRestMenuItemsController::check_menu_item_data` method was meant to be used here." david.binda
Needs Patch 59384 `wp_create_nonce()` should not have a default parameter General normal normal Awaiting Review enhancement new 2023-09-18T12:13:31Z 2023-09-18T12:13:31Z "If `wp_create_nonce()` is called multiple times, it will produce the same nonce, since `wp_create_nonce`'s `$action` defaults to `-1`.
This might be against the developer's expectation ""I called this twice, should get a different nonce"", so it might be interpreted as a security trap in a way.
{{{#!php
wp> wp_create_nonce()
=> string(10) ""6f11a1efea""
wp> wp_create_nonce()
=> string(10) ""6f11a1efea""
}}}
This is a minor issue/devex improvement, just being more explicit about the nonce's action." bor0
Has Patch / Needs Testing 59381 Issue with WordPress Year Widget for Years Below 1000 General normal normal Awaiting Review defect (bug) new close 2023-09-18T07:27:37Z 2023-10-03T15:17:28Z "I have noticed that the WordPress year widget does not function correctly when years below 1000 are used. For instance, I have created a history page where historical event dates are entered in WordPress date field. When entering a date with a year below 1000, WordPress displays such dates with leading zeros in admin area.
For example, if I enter the date as 01.01.420 (dd.mm.yyyy), the Year Archive widget leads to /420/, which does not work as expected (4040 Not found). However, if I manually add a leading zero in front /0420/, it displays correctly as /0420/.
How can this issue be resolved?
Thank you." idovecer
Needs Patch 59378 Image Aspect Ratio Not Staying Fixed In Mobile View Media 6.3.1 normal major Awaiting Review defect (bug) new 2023-09-17T15:59:42Z 2023-10-06T05:28:27Z "When an image size is adjusted within the post/page editor, by clicking on the image and dragging it, the aspect ratio of that image does not stay fixed when looking at it in mobile. The image width looks squished.
See this example page. (Ignore the date created. This was just created this morning.)
https://www.insidewaters.com/mobile-aspect-ratio-bug-test-page/
This problem is affecting hundreds of existing post/pages, not just newly created post/pages, and it would require an immense amount of work to fix manually on each image across multiple websites of ours.
You can see the problem on the page linked to below that was created awhile ago. The top camera picture gets squished in mobile.
https://www.tropicalsnorkeling.com/waterproof-snorkel-cameras/
All plugins and themes were turned off to test for conflicts. " gpwebnut
Needs Patch 59376 Shortcodes no longer working General normal normal Awaiting Review defect (bug) new 2023-09-17T15:13:17Z 2023-09-17T15:13:17Z This is a problem isn't it if word-press updates can suddenly disallow short-codes because of their updates. I am not sure I can work with an organisation that does this. My entire site, weeks of work thrown out of the window. To say i am furious is an understatement but i expect that is why it is done isn't it? I would say it is a major major drawback. All the code is fine, had it checked just wordpress team stamping its feet for money longtimenoc
Has Patch / Needs Testing 59375 "Plugin_Upgrader assumption causes incorrect ""Activate Plugin"" link after plugin installation resulting in ""The plugin does not have a valid header"" error" Plugins 6.3.1 normal normal Awaiting Review defect (bug) new has-patch 2023-09-17T13:13:19Z 2023-09-18T02:02:16Z "''Observed in WordPress 6.3.1''
== Issue Summary ==
The ""Activate Plugin"" link after installing a new plugin is inconsistent with the ""Activate"" link generated in the Installed Plugins listing table.
The ""Activate Plugin"" link on the plugin installation screen makes assumptions that produces an incorrect link which results in the user encountering the ""The plugin does not have a valid header"" error.
== Steps to Reproduce ==
1. Create a plugin that contains another plugin.
1.a. The contained plugin's basename should be lexicographically less than the wrapper plugin which you are actually trying to install. For example, ""hello-pro/hello-pro.php"" is the main plugin which contains ""hello-pro/hello/hello.php"" as a base/dependency plugin.
2. Add the plugin via wp-admin > Plugins > Add New and upload the plugin zip file.
3. Upon successful installation, click the ""Activate Plugin"" link.
3.a. Notice that the ""?action=activate&plugin=..."" plugin value is wrong as it refers to the contained plugin's main file within the wrapper plugin.
4. Observe the wp_die() error screen which says ""The plugin does not have a valid header""
== Problematic Source Code ==
The incorrect ""Activate Plugin"" link is generated here:
https://github.com/WordPress/WordPress/blob/3546f04e160fbd31b46ba70b583d0a1d9fe1d80b/wp-admin/includes/class-plugin-installer-skin.php#L115
The offending assumption is here:
https://github.com/WordPress/WordPress/blob/3546f04e160fbd31b46ba70b583d0a1d9fe1d80b/wp-admin/includes/class-plugin-upgrader.php#L546
Caused by an arbitrary situation here:
https://github.com/WordPress/WordPress/blob/3546f04e160fbd31b46ba70b583d0a1d9fe1d80b/wp-admin/includes/plugin.php#L348
=== Explanation ===
The ""Activate Plugin"" link on the ""Installing plugin from uploaded file"" screen in wp-admin uses the least lexicographic plugin basename discovered within the plugin's files. This is an arbitrary situation which can result in the incorrect plugin basename being referenced for activation, which ultimately results in the user experiencing an error screen.
== Desired Solution ==
The ""Activate Plugin"" link after adding a new plugin and the ""Activate"" link in the installed plugin's table row actions should match. The ""Activate"" link in the plugins listing table is preferred as it refers to the correct plugin basename for activation." michelleblanchette
Needs Patch 59374 "Bulk Edit does not let me remove ""Uncategorized"" for categorized posts" Posts, Post Types 6.3.1 normal normal Awaiting Review feature request new 2023-09-17T11:23:39Z 2023-09-17T11:23:39Z "Bulk Edit Posts does not let you remove category ""Uncategorized"" even when the posts do all have an additional Category." cmdgw
Needs Patch 59373 TypeError: str_contains() argument must be of type string, array given in wp-login.php Login and Registration 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-16T23:06:41Z 2023-10-05T01:24:43Z "This seems to affect PHP 8.0 and higher.
Downstream report at https://github.com/jquery/infrastructure-puppet/issues/34
> Seems to be an upstream issue where a `$_GET` or `$_REQUEST` key is checked for existence but not for type, thus prone to misuse when crafting query parameters in the array-form that PHP supports.
Easily reproduced, for example, at:
* HTTP 500 https://timotijhof.net/wp-login.php?redirect_to[x]=y
* HTTP 500 https://jquery.com/wp-login.php?redirect_to[x]=y
" TimoTijhof
Has Patch / Needs Testing 59365 Deprecated notice when calling get_admin_page_title() on some dashboard pages. Administration normal minor Awaiting Review defect (bug) new has-patch 2023-09-15T11:35:39Z 2023-09-17T17:22:35Z "{{{
Deprecated preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated
wp-admin/includes/plugin.php:2092
preg_replace()
wp-admin/includes/plugin.php:2092
get_plugin_page_hookname()
wp-admin/includes/plugin.php:2056
get_plugin_page_hook()
wp-admin/includes/plugin.php:1980
get_admin_page_title()
}}}
This occurs on all pages where global `$plugin_page` is null (Plugins, Tools, etc.)
" apedog
Needs Patch 59364 When editing Styles > Layout or Block > * > Dimensions, every possible (and unnecessary) combination of global settings is copied to custom styles Editor 6.3.1 normal blocker Awaiting Review defect (bug) new 2023-09-15T10:04:37Z 2023-09-15T10:04:37Z "In the site editor, when making changes in Styles > Layout, it looks like every possible core block style and setting is copied and saved in the custom styles (wp_global_styles).
This results in a ton of unnecessary global styles and settings, such as default colors and default font sizes, even in a theme that has defined settings.color.defaultPalette as false for example.
As far as I can tell the only styles option that triggers this are the options in Styles > Layout.
I've tried other options such as Typography, Colors, and individual block settings, and they all seem to work as expected in that the only thing saved in the custom styles is the option being edited.
No issue with WP 6.2.2
It seems this bug was introduced in WP 6.3
The Gutenberg issue for reference: https://github.com/WordPress/gutenberg/issues/53868" uxl
Needs Patch 59363 wp_tag_cloud and apply_filters Editor 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-15T09:59:24Z 2023-09-15T10:19:33Z "Line https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/blocks/tag-cloud.php#L28
{{{
$tag_cloud = wp_tag_cloud( $args );
}}}
has to be changed to
{{{
$tag_cloud = wp_tag_cloud(
apply_filters(
'widget_tag_cloud_args',
$args
)
);
}}}
to be in line with documentation:
https://developer.wordpress.org/reference/hooks/widget_tag_cloud_args/
I will attach a patch as documented here:
https://make.wordpress.org/core/handbook/contribute/git/
" steffenkrueger
Needs Dev / Bug Wrangler Feedback 59362 Display deprecated function usage in Site Health Site Health 6.3.1 normal normal Awaiting Review enhancement new dev-feedback 2023-09-15T09:17:44Z 2023-09-16T19:27:31Z "== Enhancement Request ==
=== Summary ===
WordPress Site Health provides valuable information about the health and performance of a WordPress instance. However, it does not offer any insights into whether the instance is using deprecated functions, classes, constructors, hooks, file_includes, which can be crucial for maintaining the site's compatibility with future WordPress versions.
This enhancement ticket proposes adding an additional check to Site Health that detects and displays information about any deprecated functions, classes, constructors, hooks, file_includes, being used within the WordPress instance.
Adding a ""Deprecated Functions"" check to the Site Health tool will be a enhancement for WordPress administrators, helping them identify and replace deprecated functions, classes, constructors, hooks, file_includes, plugins, themes, ensuring the site's long-term stability and compatibility with upcoming WordPress updates.
=== Details ===
The deprecated function check should be integrated into the existing Site Health tool as follows:
1. Log: Log deprecated functions, classes, constructors, hooks, file_includes
2. Display Check Results: Under a ""Deprecated Functions"" check, display a list of deprecated functions, classes, constructors, hooks and file_includes used in the WordPress instance. Result should
* include the function, class, constructor, hook or file_include name
* the version in which it was deprecated
* which Plugin or Theme called it,
* when in was called the last time
* a brief explanation of the recommended action.
=== Implementation Suggestions ===
* Utilize existing WordPress core functionality for detecting usage of deprecated functions
* Add a action to 'deprecated_{[]}_run' that logs the usage of a deprecated functions
* Use debug_backtrace() do indentify the source / code.
* The check results should display the log entries with status 'recommended'.
* Keep the log process ""stupid"" and put logic etc. into the check, to avoid complexity and potential crashes.
=== Challenges ===
* To provide the administrator with sufficient information so that they are capable of taking action.
* Decision on how long entries stay in the log e.g. only show deprecated function calls of the last 30 days or allow the (administrative ) user to clear the log?
* Should there be one check in Site Health of all kinds of deprecated? Or one for each?
=== Why It's Important ===
WordPress is constantly evolving, and maintaining compatibility with newer versions is crucial for security and performance reasons. Deprecated functions may be removed in future releases, causing issues for sites that rely on them. By providing this information in Site Health, WordPress can empower site administrators to keep their installations future proof.
" Michi91
Needs Docs or Unit Tests 59361 update_post_meta() strict checks can cause false negatives Options, Meta APIs normal normal Future Release defect (bug) new needs-unit-tests 2023-09-15T07:47:12Z 2023-09-15T07:47:12Z "Follow up: #22192
{{{
add_post_meta( $post_id, 'key', 1 );
update_post_meta( $post_id, 'key', 1 );
}}}
The update should not work, because they are the same. However, the meta meta cache will have ""1"" as a string, and then it will strict compare it to 1 as an integer. Thus, an unnecessary update will run.
It is quite common to use integers and booleans directly into these functions. They should be smart enough to recognize that ""1"" == 1 == true and ""0"" == 0 == false, and that any numeric string is also equal to a properly cast integer.
The new changes need unit tests.
Ticket from which this was spun: #22189, saving navigation menus is slow.
cc. @flixos90 @spacedmonkey @joemcgill" mukesh27
Needs Patch 59355 TypeError: Cannot read properties of undefined (reading 'hasClass') in wp-auth-check.min.js Security 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-15T04:00:17Z 2023-09-15T04:03:37Z "Here is the trace:
{{{
at
HTMLDocument.(.../wp-includes/js/wp-auth-check.min.js:2:655)
at
HTMLDocument.dispatch(.../wp-admin/load-scripts.php:2:39997)
at
v.handle(.../wp-admin/load-scripts.php:2:37968)
at
Object.trigger(.../wp-admin/load-scripts.php:2:70063)
at
HTMLDocument.(.../wp-admin/load-scripts.php:2:70665)
at
Function.each(.../wp-admin/load-scripts.php:2:3129)
at
e..each(.../wp-admin/load-scripts.php:2:1594)
at
e..trigger(.../wp-admin/load-scripts.php:2:70640)
at
Object.(https://wednesdaynighthop.com/wp-includes/js/heartbeat.min.js:2:2186)
at
c(.../wp-admin/load-scripts.php:2:25266)
}}}
" chamois_blanc
Needs Docs or Unit Tests 59354 Unnecessary queries performed when updating a post without providing categories or tags Posts, Post Types normal normal Awaiting Review defect (bug) new needs-unit-tests 2023-09-14T22:43:53Z 2023-09-14T22:43:53Z "Given an existing post with at least some categories or tags present, updating the post via `wp_update_post()` (which calls `wp_insert_post()`) with data that does not include categories or tags, many unnecessary taxonomy-related database queries are performed. This slows down the saving significantly.
* If `$postarr` doesn't contain a `post_category` element, there's no point in calling `wp_set_post_categories()`.
* If `$postarr` doesn't contain a `tags_input` element, there's no point in calling `wp_set_post_tags()`
== Todo ==
* Need tests to verify the above is correct
* Need a list of queries that are performed before and after the change
== To reproduce ==
1. Publish a post with at least one category
2. Update the post via:
{{{#!php
$id,
'post_content' => 'Hello, World!',
] );
}}}
3. Observe that a significant number of unnecessary taxonomy queries are performed" johnbillion
Needs Patch 59351 Add support for querying by an exact date with WP_Date_Query Query normal normal Awaiting Review enhancement new 2023-09-14T20:45:11Z 2023-09-15T23:08:04Z "WP_Date_Query lacks the ability to query for posts with a specific date. Currently, to query for a post with a specific date string you would need to break it down to multiple arguments:
{{{#!php
[
'year' => date( 'Y', $date ),
'month' => date( 'm', $date ),
'day' => date( 'd', $date ),
'hour' => date( 'H', $date ),
'minute' => date( 'i', $date ),
'second' => date( 's', $date ),
],
] );
}}}
There is no argument on WP_Date_Query that accepts a `strtotime()`-compatible string for an exact date match. One workaround is to use a combination of before/after to get a simplified query.
Adding support for an exact match can be used when querying for posts from a specific date as well as including/excluding posts from a specific date for a complex query. Suggested syntax:
{{{
// Query for posts after January 1st, 2013 OR exactly on November 7th, 2010
[
'date_query' => [
'relation' => 'OR',
[
'after' => 'January 1st, 2013',
],
[
'exact' => 'November 7th, 2010',
],
],
]
}}}
Relates to #18694." sean212
Needs Patch 59348 Excerpt block length is not full customizable any more Posts, Post Types normal normal Awaiting Review defect (bug) new 2023-09-14T11:40:32Z 2023-09-14T15:19:35Z "Since the latest changes in /src/wp-includes/blocks/post-excerpt.php now the excerpt length is not fully customizable any more. The problem is that previously `$excerpt = get_the_excerpt();` was used, which was filterable with `get_the_excerpt`, but now this excerpt is just getting forcefully trimmed by `wp_trim_words` based on the `excerptLength` option. Which is: a) A number forced to be between 10-100 b) now can not be changed or overwritted with custom code in any way.
If I want to display the excerpt of a post on the post's page, now there is no way to correctly display an excerpt that is longer than 100 words. I think this is a loss in features and a bad practice to limit the excerpt's usage in this way. At least allow `$excerpt_length = $attributes['excerptLength'];` to be modified with the already existing `excerpt_length` filter.
Mentioned change:
https://core.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=56065%40trunk%2Fsrc%2Fwp-includes%2Fblocks%2Fpost-excerpt.php&old=55246%40trunk%2Fsrc%2Fwp-includes%2Fblocks%2Fpost-excerpt.php" frzsombor
Needs Patch 59344 Link UI Goes Off The Screen, Can't Acces Advanced Editor 6.3.1 normal major Awaiting Review defect (bug) new 2023-09-14T01:26:38Z 2023-09-14T01:26:38Z "As it says above, can't edit links or access ""advanced"" for links on left side of the screen ... UI pops up mostly out of the window." hmnvtn
Needs Patch 59342 Plugins: Provide notification of testing/compatability with current version of WP in plugin/update list Plugins normal normal Awaiting Review enhancement new 2023-09-14T00:15:58Z 2023-09-14T00:15:58Z "An enhancement suggestion from the Support Forums
https://wordpress.org/support/topic/idea-plugin-status-preview-before-wordpress-update/
The menu for installing/updating plugins could show if a plugin is compatible with the current installed WordPress version. A similar page which just shows the activated (and maybe installed) plugins and the compatibility to the new wordpress version would be nice.
It would also be nice if update-core.php automatically analyze the contents of that page. If every plugins seems to be compatible the update runs. If not everything reports to be compatible there could be a warning with a list of the entries which can cause problems. So at this point it is on your decision to continue or to abort." jordesign
Needs Patch 59340 """Open in new tab"" checkbox in hyperlink entry doesn't save" Editor 6.3 normal normal Awaiting Review defect (bug) new 2023-09-13T16:37:54Z 2023-09-29T15:48:45Z "When interfacing, the ""Open in new tab"" selection sometimes doesn't work. Rapidly entering the information on a slow internet connection should reproduce the bug.
It's probably tied to network information, where the ""Save"" button SHOULD send a delayed network transmission of the update. Instead, it drops the information.
This compounds as a worse problem with the new UI information, since it requires several clicks to confirm each hyperlink's present status.
The workaround is to wait 2-3 seconds after selecting the checkbox but before selecting ""Save"".
This most heavily affects power users and users with slow internet connections." phileossopher
Needs Patch 59339 Conversion to webp causes fatal error when original image is a palette image (as opposed to truecolor) Media 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-13T13:41:52Z 2023-09-13T13:41:52Z "I am working on an image conversion plugin. I've run into a bug when the original image is a ""paletter image""[https://www.thecoderscamp.com/paletter-image-not-supported-by-webp/]"", or in other words, an image that has an indexed palette rather than being truecolor. I believe it's a png.
The error I get is:
{{{
Fatal error: Paletter image not supported by webp in /home/username/public_html/wp-includes/class-wp-image-editor.php on line 584
}}}
And how I'm using it:
{{{#!php
image_path );
$new_file_info = $this->get_editor()->save( $this->image_path, 'image/webp' );
}}}
This method worked fine on hundreds of images of png, jpg, and tiff until I ran into this one that has a ""palette"".
In `wp-includes/class-wp-image-editor-gd.php:487`, if the image loaded into WP_Image_Editor is a png, we check for a palette and convert to true color before saving. I believe that we need to also check in the webp conditional and, just like for png, convert to truecolor first.
" jakeparis
Has Patch / Needs Testing 59337 Change the escape esc_attr() to esc_url() General normal normal Awaiting Review defect (bug) new has-patch 2023-09-13T11:51:04Z 2023-09-14T05:41:00Z "Change the esc_attr() function to esc_url() in ""wp-admin/user-edit.php""" truptikanzariya
Has Patch / Needs Testing 59334 In Theme Twenty Nineteen, Twenty seventeen & Twenty Twenty-Two Comment section Reply and cancel reply has no space between them Bundled Theme normal normal Awaiting Review defect (bug) new has-patch 2023-09-13T05:47:18Z 2023-10-18T13:13:27Z "In Theme Twenty Nineteen, Twenty seventeen & Twenty Twenty-Two, in the comment section on clicking reply the reply to user and cancel reply have no space between them
Reference Video : https://drive.google.com/file/d/1YBcQquFQdZz7CpUZs3gzYBfK869CTWDB/view
" pitamdey
Needs Patch 59332 Can't customize search in header General 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-12T19:52:07Z 2023-10-05T14:35:32Z "The search block can't be customized when added to the header navigation. It can be added, but when any customizations are selected, such as ""Change button position"" -> ""No button"", the search box only flickers and nothing changes. This applies to any change I try to make from the toolbar.
To reproduce problem:
1. Go to Appearance -> Template Parts
2. Select Header
3. Add navigation block, and add search box to end of nav
4. Try to customize the search block
I'm using:
- WordPress version 6.3.1; Gutenberg plugin is not installed, tested on custom theme, and Twenty Twenty-Two
- Happening in both Chrome and Edge browsers
- Using desktop with Windows 11
GIF of issue: https://imgur.com/a/PYccoLh" christinameyne
Needs Patch 59331 Image optimizations fail to apply when using Timber Media 6.3 normal normal Future Release defect (bug) new 2023-09-12T17:46:01Z 2023-09-12T21:45:19Z "A user [https://mastodon.social/@grigs@front-end.social/111052735378137214 reported] hero images were getting `loading=lazy` on their site. After inquiring, I found they were using Timber for templating. It makes sense that the logic in `wp_get_loading_optimization_attributes()` wouldn't work properly in this case since it is tightly bound to WordPress's templating system(s). This may actually be an issue better fixed in Timber itself, but ideally WordPress core should be able to do the right thing with alternate templating systems (or even complex templates written in the WordPress way). Ultimately, this may require the use of output buffering and HTML Tag Processor as [https://github.com/WordPress/performance/issues/805 proposed] for a module in the Performance Lab plugin. See #59331 for adding output buffering for template renders with a filter for post-processing.
Here's how to reproduce the issue with Timber:
1. Install and activate the [https://wordpress.org/plugins/timber-library/ Timber plugin] from WordPress.org.
2. Install and activate the [https://github.com/timber/starter-theme Timber Starter Theme] from GitHub (i.e. download the ZIP).
3. Add a new post with an initial large image or a featured image.
4. See the image has `loading=lazy` and is missing `fetchpriority=high` on the frontend.
Initial image block:
{{{
}}}
Featured image markup:
{{{
}}}" westonruter
Has Patch / Needs Testing 59330 Improvement in wp_parse_args for mutli-dimensional arrays General 6.3.1 normal trivial Awaiting Review enhancement new has-patch 2023-09-12T13:36:22Z 2023-09-17T15:54:28Z "I noticed the function doesn't work well when multi-dimensional arrays are present:
Example:
Consider having following default params and settings.
{{{
$defaults = array(
'settings' => array(
'option1' => 'default-value-1',
'option2' => 'default-value-2'
)
);
$settings = array(
'settings' => array(
'option1' => 'new-value-1',
)
);
$return = wp_parse_args($settings, $defaults);
}}}
The above example will return:
{{{
Array
(
[settings] => Array
(
[option1] => new-value-1
)
)
}}}
It will completely ignore the option2 key.
My suggestion is to update wp_parse_args from:
{{{
if (is_array($defaults) && $defaults) {
return array_merge($defaults, $parsed_args);
}
}}}
with:
{{{
if ( is_array( $defaults ) && $defaults ) {
return array_replace_recursive($defaults, $parsed_args);
}
}}}
" Stachethemes
Needs Patch 59329 "Firefox gets ""ReferenceError: Â is not defined"" in unminified moxie.js" Upload normal minor defect (bug) new close 2023-09-12T13:04:50Z 2023-11-04T09:36:22Z "In unminified moxie.js, there exists some weird Unicode characters on line 7391, between the BinaryReader constructor fn and the call to Basic.extend(). In a hex editor, you can see the character bytes are ""C2A0"", which is a random Korean Hangul character in Unicode.
In Firefox (as of the latest 117), when using Divi, this causes an exception when loading unminified moxie.js. Firefox's Js loader interprets the first byte alone as Â, and fails while loading moxie.js.
I can replicate this in FF+Divi, but the problem does not appear in Chrome, Safari, or in FF when using other builders like Classic/Gutenberg/Elementor/Beaver. Minification strips out the problem bytes.
This link, https://stackoverflow.com/a/1462039/1201409, suggests the error is leftover from an earlier era of encoding a nonbreaking space before UTF-8 replaced other encodings.
Regardless of how the bytes got in there (and whether FF/Divi have bugs), they shouldn't be there, and luckily, the fix is trivial: delete them." kinggmobb
Needs Dev / Bug Wrangler Feedback 59324 User list Users 5.2.2 normal normal Awaiting Review defect (bug) new dev-feedback 2023-09-11T11:22:54Z 2023-09-13T03:40:28Z "Hello,
I have the site and operates well. But suddenly, the Users menu from dashboard, I can not see the users list even I've loggined as a admin.
[[Image(https://imgur.com/a/NxdJG85)]]
From the back-end, it seems there are the data in there, but seems the front-end is not displaying the list.
Is there any similar case reported?
So far, I deactivated all plug-in, but no sucess. I have checked the wp-admin/users.php file but no problem.
Please let me know where I can look for. Thanks.
" kylechoi
Has Patch / Needs Testing 59321 "Block styles set via the ""css"" property in theme.json are ignored on the frontend in classic/hybrid themes" Editor 6.3.1 normal normal Awaiting Review defect (bug) new has-patch 2023-09-11T08:33:26Z 2023-09-14T06:42:37Z "### Description
Block styles set via the ""css"" property in theme.json are ignored on the frontend in classic/hybrid themes. An example:
{{{
""blocks"": {
""core/latest-posts"": {
""color"": {
""background"": ""blue""
},
""css"": ""& li a {color: pink}""
}
}
}}}
The background color set via ""color"" can be seen in both the block editor and the frontend. The link color set via ""css"" can only be seen in the block editor.
Block themes (I tested [Twenty Twenty-Three](https://es.wordpress.org/themes/twentytwentythree/)) are not affected by this issue, just classic ones.
### Step-by-step reproduction instructions
1. Install and activate a classic theme that ships a theme.json file, such as [Astra ](https://wordpress.org/themes/astra/).
2. Edit the theme's theme.json file and add the following in the `styles` section:
{{{
""blocks"": {
""core/latest-posts"": {
""color"": {
""background"": ""blue""
},
""css"": ""& li a {color: pink}""
}
}
}}}
3. Edit a page and add a Latest Posts block and verify that the background color of the block is blue and the links are pink.
4. Save changes.
5. Head to the frontend version of the page and see that only the background color is applied. The links are not pink.
### Screenshots, screen recording, code snippet
**Block editor:**
[[Image(https://user-images.githubusercontent.com/2060659/253602606-e56391e7-e320-49f8-b939-7ac60f903a4b.jpg)]]
**Frontend:**
[[Image(https://user-images.githubusercontent.com/2060659/253602584-875cf30c-c96b-428e-93c6-71b1ad58cc2e.jpg)]]
### Environment info
I'm using WP 6.3.1
NO Gutenberg plugin installed.
PHP 8.0.22
MySQL 8.0.16
### Please confirm that you have searched existing issues in the repo.
Yes
### Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes" leemon
Has Patch / Needs Testing 59318 Block Themes Fatal Error in PHP 8.1 When Referring To Missing Template Parts Themes 6.3.1 normal normal Awaiting Review defect (bug) new has-patch 2023-09-08T14:32:27Z 2024-02-09T16:01:36Z "We have a system that manages template and template part posts, and have noticed that if a template refers to a template part that no longer exists or did not sync to the site, we get a cryptic PHP fatal error about passing null to preg_replace:
{{{
preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated
}}}
This occurs in template-part.php in the render_block_core_template_part function when calling shortcode_unautop:
{{{
// Run through the actions that are typically taken on the_content.
$content = shortcode_unautop( $content );
}}}
In this case $content contains the value null. My expectation is that this would fail gracefully, and there is a check if it is null further up the function, but it only runs if $debug is true:
{{{
// WP_DEBUG_DISPLAY must only be honored when WP_DEBUG. This precedent
// is set in `wp_debug_mode()`.
$is_debug = WP_DEBUG && WP_DEBUG_DISPLAY;
if ( is_null( $content ) && $is_debug ) {
}}}
Meaning that unless WP_DEBUG and WP_DEBUG_DISPLAY are both set to true, there is no protection against null being passed into shortcode_autop" TJNowell
Needs Patch 59317 Error on new pattern preview General 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-08T05:48:13Z 2023-09-08T06:44:50Z "While I try to create an new pattern and try to preview the pattern, the page redirects to the error page. On this page, following error will be shown.
TypeError: e is not a function
at https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/block-editor/index.min.js?ver=148cceb5deef937e87d2:135:7828
at renderContent (https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/components/index.min.js?ver=3426334688a22e73bc0c:33:5438)
at https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/components/index.min.js?ver=3426334688a22e73bc0c:3:13188
at St (https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:47627)
at pr (https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:54870)
at $s (https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:122623)
at Sl (https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:88649)
at kl (https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:88577)
at bl (https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:88440)
at dl (https://wordpress.org/patterns/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:85597)" labunchemjong
Needs Patch 59311 Error on feed link Feeds 6.3.1 normal major Awaiting Review defect (bug) new 2023-09-07T13:32:54Z 2023-09-07T13:32:54Z "Hi!
I am revising a web in my job, and I have saw that there is an error in the feed link, it shows all code instead the feed's page.
I hope that you could revise and solve this problem.
Regards,
Rubén." rubenbitrian
Has Patch / Needs Testing 59310 Parse blocks being applied unnecessarily Editor 5.3.1 normal normal Awaiting Review defect (bug) assigned has-patch 2023-09-07T13:03:47Z 2024-02-05T22:01:16Z The filter `wp_pre_kses_block_attributes` is applied to any field that runs through `wp_kses_hook`. Any fields on any object field that is run through `wp_filter_kses`. This includes fields like comment_author_email, user_email, term_name and user_last_name. It is extremely unlikely that these text fields will contain block data. This filter should be changed. spacedmonkey
Needs Patch 59308 Attachment custom fields not rendered in some cases Media 6.3.1 normal normal Future Release defect (bug) new 2023-09-07T09:50:21Z 2024-02-14T17:05:47Z "This is a follow-up to #58051.
I've noticed that in some cases custom fields added via `attachment_fields_to_edit` do not show up when the ""Featured Image"" modal is opened after clicking a ""featured image"". I then need to first click on another attachment and then back to have the custom fields show up.
It seems that this bug only happens when you have a lot of images (more than 1 page) and the featured image you're looking at is not on the first page. It's easy to reproduce.
If absolutely necessary I can set up a clean WordPress and make a screen recording of this bug, as I rather not share the images and data in our WordPress installation." SeBsZ
Needs Patch 59307 Urgent, Uncaught TypeError: this.activateMode is not a function Media 6.3.1 normal critical Awaiting Review defect (bug) new 2023-09-07T08:06:16Z 2023-09-07T08:06:16Z "It's very urgent. There is no response when clicking the media button on the add/edit article page.
Showing an error every click on the media button:
Uncaught TypeError: this.activateMode is not a function
at media-views.min.js?ver=6.3.1:2:59604
at It (provider.js:2:586804)
at Function.ma (provider.js:2:621991)
at n._createModes (media-views.min.js?ver=6.3.1:2:59564)
at n.initialize (media-views.min.js?ver=6.3.1:2:58973)
at n.initialize (media-views.min.js?ver=6.3.1:2:79857)
at n.initialize (media-views.min.js?ver=6.3.1:2:73432)
at n.initialize (media-views.min.js?ver=6.3.1:2:63143)
at h.View (load-scripts.php?c=1&load%5Bchunk_0%5D=wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks,jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-mouse,jquer&load%5Bchunk_1%5D=y-ui-sortable,underscore,backbone,wp-util,wp-backbone,media-models,moxiejs,plupload&ver=6.3.1:151:14648)
at n.constructor (load-scripts.php?c=1&load%5Bchunk_0%5D=wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks,jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-mouse,jquer&load%5Bchunk_1%5D=y-ui-sortable,underscore,backbone,wp-util,wp-backbone,media-models,moxiejs,plupload&ver=6.3.1:155:2602)" jjproitech
Needs Reporter Feedback / Steps To Reproduce 59303 Can’t use colors with selected text in Gutenberg Editor 6.3.1 normal major Awaiting Review defect (bug) new reporter-feedback 2023-09-06T23:33:36Z 2023-09-07T14:13:38Z "The form to add color to text was always a bit buggy with Gutenberg. But, since a few versions it doesn’t work anymore.
The area with colors appear below the right column. Some versions ago page could be moved to reveal the palette, but now it’s no more possible.
See the image below:
[[Image(https://i.postimg.cc/ZRZLvL0V/IMG-6233.jpg)]]" locksoft
Needs Patch 59301 Incorporate script loading strategies in WP Admin to improve performance where applicable Administration 6.3 normal normal Future Release enhancement new 2023-09-06T20:35:04Z 2024-01-29T19:44:23Z "As of #12009 the script loader now has the ability for scripts to be printed with `async` or `defer`. This is being used on the frontend now for block view scripts (#59115), the `comment-reply` script (#58870), and the `wp-embed` script (#58931). Nevertheless, these new script loading strategies are not currently being used in the admin. There may be opportunities to improve performance by doing so.
Typically only `jquery-core`, `jquery-migrate`, and `utils` (less frequently `moxiejs` and `plupload`, and even less frequently `wp-polyfill-inert`, `regenerator-runtime`, `wp-polyfill`, `wp-hooks`, `zxcvbn-async`, `wp-codemirror`, and `underscore`) are loaded in the `head` in the admin; furthermore, these scripts are concatenated together via `load-scripts.php`. For backwards-compatibility, these scripts might not be able to be delayed or moved to the footer. In other cases, there may be existing footer scripts that could be moved to the `head` and made to load with `defer`: this would ensure that they start loading sooner so that they can execute as soon as the document finishes loading. Other scripts could potentially be lazy-loaded only when needed (e.g. `zxcvbn`).
Note that the block/site editor screens will benefit the most from [https://github.com/WordPress/gutenberg/discussions/53260#discussioncomment-6870404 block lazy loading]." westonruter
Needs Patch 59299 Add Felt.com to the list of oEmbed providers Embeds normal normal Awaiting Review enhancement new 2023-09-06T15:45:40Z 2023-10-08T23:10:54Z "I'd like to request whitelisting the Felt.com's oEmbeds. Their mapping platform is both robust and user-friendly, and would be a great addition to WordPress users interested in sharing maps online.
Here's an example URL: https://felt.com/map/Learn-to-Use-Felt-Tutorial-0xljGYVlRzGfxNgRV9A6akC?loc=40.7849,-73.97533,13.94z&share=1
**Is the service is popular enough for core developers to have heard of it before? Is it “mainstream?”**
It's probably not mainstream yet, but it's a very well-known service in the GIS community.
**If similar services are already supported, how does this service compare in terms of size, features, and backing?**
As far as I know, core doesn't whitelist embeds for other mapping platforms. To embed maps from other providers (OpenStreetMaps, Google, Mapbox, etc.), a map block is required.
**Does this service have an established social media presence?**
Yes.
https://twitter.com/felt
http://threads.net/@feltmaps
http://mas.to/@felt
https://www.youtube.com/@feltmaps
**Is its oEmbed endpoint clearly established and properly documented? (Sometimes, they are just a developer’s pet project that may not be supported.)
**
It's supported, but as far as I know, it's not documented in their dev documents https://feltmaps.notion.site/Getting-Started-With-The-Felt-API-69c8b02b7d8e436daa657a04a2dbaffa
**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?**
Yes, the embed is discoverable.
**Does the service make an effort to build relationships with developers, such as through robust APIs?**
**How old is the service?**
The company was founded in 2021, the platform was launched at the beginning of 2022.
**Does it have a well-established Wikipedia article? (Seriously.)**
No, but they are contributors to several big open-source projects. More information https://felt.com/open-source, https://felt.com/blog/felt-flagship-member-of-qgis, and https://blog.qgis.org/2023/03/21/felt-is-our-first-sustaining-member
**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?**
No, as far as I know.
**Is the provider frequently proposed?**
No, this would be the first time." javiarce
Needs Reporter Feedback / Steps To Reproduce 59298 Twenty Fourteen : search block is having issue with alignment. Bundled Theme 6.3.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-09-06T14:08:03Z 2023-09-06T21:29:35Z "Steps to reproduce the issue :-
1. Activate Twenty Fourteen theme.
2. Choose Search block.
3. Apply center align and check in front side.
4. Apply Right align and then check in front side.
You can able to see that center aligned is having issue.
I have attached video for better understanding.
Video URL :- https://share.cleanshot.com/6p3TmBFwZ91llFT5V52R" nidhidhandhukiya
Has Patch / Needs Testing 59297 Remove unused variables General normal normal Awaiting Review defect (bug) new has-patch 2023-09-06T12:56:06Z 2024-02-19T23:49:34Z "I have reviewed the code and found some of the variables are defined but they do not use in the below files. Please check the below files:
Files:
1. wp-admin/includes/class-wp-privacy-policy-content.php
2. wp-admin/includes/post.php
" upadalavipul
Has Patch / Needs Testing 59291 HTML API: Expose raw tag markup to support existing filters HTML API 6.4 normal normal Awaiting Review enhancement new has-patch 2023-09-05T21:26:35Z 2023-09-19T00:50:37Z "Many existing filters in Core (e.g. `wp_targeted_link_rel`) pass segments of the raw HTML markup for matched tags where code implementing those hooks perform futher analyis on those segments. The HTML API attempts to hide the raw inner markup as much as possible, making it hard to provide full backwards compatability with these existing filters.
In this patch a new function is added which extracts the raw markup to maintain those existing behaviors. It requires a disclaimer to operate to try and encourage folks to use the structural and semantic methods provided by the HTML API.
Where possible, existing code and filters should be updated so that they no longer depend on the raw HTML." dmsnell
Needs Patch 59288 Blocks API JSX Map in Save function does not rerender Plugins 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-05T18:39:00Z 2023-09-05T18:39:00Z "Hi,
I am building a custom block, it is a hero slider.
In the parameters I am defining an attribute called slides which has an empty array as it's default value.
In the Edit function :
{{{
registerBlockType(""fa-gutenberg-blocks/fa-01-hero-slider"", {
edit: Edit,
save: Save,
});
}}}
It loads fine and I can create add new elements to it like so
{{{
const addSlide = () => {
const emptySlide = {
title: """",
description: """",
media: { url: """", id: null },
ctaLabel: """",
ctaURL: """",
backgroundColor: ""#CCC"",
};
const newCurrentSlide = slides.length;
setAttributes({
slides: [...slides, emptySlide],
});
setTimeout(() => {
setAttributes(
{
currentSlide: newCurrentSlide,
},
200
);
});
};
}}}
However in the Save function it does not load an empty array the attribute is undefined. To try and solve this I set the slides attribute to an empty array if undefined, as I added objects to the slides array they appeared in the Save function. I then called a array map method on the slides in the returned JSX in the save function which returned some html for each array item. When I loaded the the block on the actual page (not the edit screen) it did not render the mapped JSX html, but the attribute slides does contain the updated array.
To see the full code view the repo here : https://github.com/frankastin2023/fa-hero-slider
" frankastin2023
Changes Requested 59283 "Block Editor: Edit permalink slug for posts is only possible after clicking ""save as draft""" Editor normal normal 6.6 defect (bug) new changes-requested 2023-09-05T08:21:49Z 2024-02-05T21:01:58Z "Originally posted in Gutenberg https://github.com/WordPress/gutenberg/issues/50469
When creating a new post using the block editor, it's impossible to set the permalink of the post before you actually save the first draft of the post. It's different for the page editor where you can do so before.
@andrewserong tracked this to the `permalink_template` property not being set on the initial request to fetch the auto-draft post." youknowriad
Has Patch / Needs Testing 59282 WordPress should register custom error and exception handlers Bootstrap/Load 6.4 normal normal Awaiting Review feature request new has-patch 2023-09-04T20:06:18Z 2023-09-05T12:51:50Z "WordPress relies on PHP's `display_errors` setting for error reporting. One unfortunate result of that is that errors containing HTML may be served to the browser unescaped.
[https://github.com/WordPress/WordPress-Coding-Standards/ WordPress/WordPress-Coding-Standards] tries to help avoid this by having a sniff (WordPress.Security.EscapeOutput) that, among other things, asks that strings passed to `trigger_error()` and `throw new SomeClass()` be escaped. This is not a very good solution for a few reasons:
* It doesn't do anything about errors or exceptions thrown by PHP itself.
* It doesn't do anything about errors or exceptions thrown by libraries that might be bundled into themes or plugins or any custom code blog authors might inject.
* It means that text-based log files, non-HTML emails, CLI output, and the like will contain HTML entities.
Instead we should follow the principle that values should be escaped close to the point of output, when we know what kind of escaping will be needed. Which, in the context of PHP, means using `set_error_handler()` and `set_exception_handler()` to handle the outputting.
While #43712 is similar to this issue, the reasons and solution space are different. That ticket wants enhanced handling of errors for better user experience. This ticket is satisfied with the existing UX, it just wants error output fixed properly instead of trying to make every generated error be ""safe"" in order to avoid the potential bugs.
See also https://github.com/WordPress/WordPress-Coding-Standards/issues/2374#issuecomment-1703370109 where @jrf suggested I file this ticket.
" bjorsch
Needs Patch 59281 Support for Database Cursor Database normal normal Awaiting Review feature request new 2023-09-04T19:34:08Z 2023-09-27T13:47:35Z Is it possible to do a cursor query using the `$wpdb` instance or could it be added, which will return a generator (yield)? heera
Needs Dev / Bug Wrangler Feedback 59276 Wrong notice is showing up on the Privacy Policy page settings in WP dashboard. Privacy normal normal Awaiting Review defect (bug) new dev-feedback 2023-09-04T10:33:04Z 2023-09-05T10:35:59Z "If Admin does not select any page for Privacy policy from the Admin Dashboard and save the settings, the notice that appears shows that the page has been updated.
**How to reproduce:**
1. Navigate to Settings > Privacy.
2. Keep 'Change your Privacy Policy page' dropdown unselected.
3. Save settings by clicking on 'Use This Page' button.
**Expected Result:**
As there is no page selected in dropdown, it should not show the notice that page has been updated.
[[Image(https://ibb.co/3hyK6BY)]]
**Environment Details:**
WordPress version: 6.3.1
Browser: Chrome Version 116.0.5845.111
OS version: Windows 10
PHP version: 7.4.33
Server: Apache/2.4.57
Active Theme: Twenty Twenty-Three
Active Plugins: None
" anveshika
Needs Patch 59275 PHP 8.1 Deprecated function: rtrim(): Passing null to parameter Formatting 6.2.2 normal normal Awaiting Review defect (bug) assigned 2023-09-04T06:09:51Z 2023-09-04T06:11:47Z "Deprecated - rtrim(): Passing null to parameter #1 ($string) of type string is deprecated
used in
wp-includes/formatting.php:2809
rtrim()
wp-includes/formatting.php:2809
untrailingslashit()
wp-includes/formatting.php:2794
trailingslashit()
wp-content/mu-plugins/http-concat/concat-utils.php:27
WPCOM_Concat_Utils::realpath()
wp-content/mu-plugins/http-concat/cssconcat.php:84
WPcom_CSS_Concat->do_items()
wp-includes/functions.wp-styles.php:68
wp_print_styles()
wp-includes/class-wp-hook.php:308
do_action('wp_head')
wp-includes/general-template.php:3049
wp_head()
wp-includes/template-canvas.php:17
MU Plugin: http-concat" srishtis
Needs Patch 59274 (Updates) update-core.php Upgrade/Install 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-03T23:04:51Z 2023-09-03T23:16:15Z "I am using WordPress 6.3.1.
Theme: ColorMag Pro
URL: https://suncatcherstudio.com/
When I press on ""Updates"" rather than getting a graphical interface,
I am getting a list of textual links as shown in the attached
image. Is this a bug? This is the first time I noticed this problem.
https://billrosener.com/temp2/wordpress-updates-menu.png
Do you know how I can get back to a graphical version??
Thank you,
Bill
" rosener
Needs Patch 59273 Plugin: Create Block Theme Bug General 6.3 normal minor Awaiting Review defect (bug) assigned 2023-09-03T18:40:57Z 2023-09-04T11:40:34Z "I'm not sure where to file this bug. So please put it whereever it's relevant.
When I use the Create Block Theme plugin with WP 6.3 and try to install a Google Font this error comes up:
""Error: `DISALLOW_FILE_EDIT` cannot be enabled in wp-config.php to make modifications to the theme using this plugin.""
I have tried to enable this in the wp_config.php, but this does not work.
Adding fonts should be more easy in the theme. " perthykjaerjensen
Needs Patch 59272 wp-admin search/column order not working when running not on port 80 Administration 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-02T12:49:40Z 2023-09-02T12:49:40Z "Hey,
we are currently running WP 6.3.1 internally on a different port ( localhost:8182 ).
WordPress itself works without problems.
Only when you on the wp-admin page search for a keyword in a CPT or change the order, the port gets deleted from the URL.
I found following part of the core source where the problem happens:
https://github.com/WordPress/WordPress/blob/master/wp-admin/includes/class-wp-list-table.php#L1381
Would be nice to respect the site url from the settings or not delte the port when used." canic
Needs Patch 59271 Issue With the Duotone filter With Image in Editor Editor 6.3 normal normal Awaiting Review defect (bug) new 2023-09-02T07:06:23Z 2024-02-20T05:54:26Z "While Adding an Image & apply custom Duotone filter in it & choose custom Shadow & highlights to the image at that time image not display on front end with given shadows.
It works in backend editor, But in frontend it doesn't work properly. refer below video form same
https://www.awesomescreenshot.com/video/20433189?key=59d607fc51153fcb135dc6af3931b17c
WP Version : 6.3
PHP Version : 8.0" dhruval04
Needs Patch 59270 Excerpts Not Showing Bold Text ... Editor 6.3 normal normal 6.6 defect (bug) new 2023-09-02T01:47:36Z 2024-02-17T14:26:45Z The text itself shows, but it does not show the bold attributes as it did up until 6.2.2. hmnvtn
Has Patch / Needs Testing 59269 Add support for adding metadata in bulk Database normal normal Awaiting Review enhancement new has-patch 2023-09-01T22:39:01Z 2023-09-01T23:43:31Z "Related: #34848
This ticket aims to introduce functions for bulk inserting metadata in a manner that's more performant than calling the `add_*_meta()` functions multiple times per object. This is particularly beneficial during large imports or data generation where `add_*_meta()` is called many times for a large number of users, posts, comments, or terms.
This can be achieved by inserting all the metadata for the object in one INSERT query and only deleting the object's meta cache once. The existing filters and actions that are triggered when calling the `add_*_meta()` functions individually should still all be fired as expected, once for each meta key.
The performance benefit should grow as the number of rows to insert increases, because both the number of database queries and the number of cache deletions for the object should remain constant (`O(1)`) rather than increasing correspondingly to the number of rows (`O(n)`).
That said, there does appear to be a sweet spot after which the performance of one large INSERT query starts to degrade, although according to the PHPBench tests I've added it still remains overall more performant than multiple queries. Some more testing is needed across different payload sizes and database versions." johnbillion
Needs Patch 59266 Fatal error: Uncaught Error: Call to undefined function list_files() General normal normal Awaiting Review defect (bug) new 2023-09-01T17:37:05Z 2023-09-04T06:14:12Z Fatal error: Uncaught Error: Call to undefined function list_files() brunobird
Needs Patch 59265 Reset password form is not sending recovery email General 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-01T15:05:47Z 2023-09-01T15:05:47Z "Reset password email is not sending. Once you're ""domain.com/dashboard/retrieve-password/"" URL, after put email or username for recovery, email with link is never sent. It is in WP version 6.3.1" ardaniela
Needs Patch 59264 Some block parts (navigation) break when top level folder gets renamed Editor 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-01T14:03:12Z 2023-09-01T14:25:10Z "Steps to reproduce:
- clean install of 6.3.1
- set up any block theme as current theme
- rename the top folder where the wordpress installation is lying (i needed to do it because of switching URL)
-> block navigation is broken
This is also the case when put wordpress into troubleshooting mode or using any other block theme with a menu.
I tracked it down and it seems that some css is not coming any more to the page.
{{{
this is home.';
if ( is_front_page() ) echo '---------------> this is frontpage.';
?>
}}}
see image below where i added the php code
[[Image(https://share.getcloudapp.com/lluXB459)]]
The complete altered index.php of the 20-21 theme below
{{{#!php
this is home.';
if ( is_front_page() ) echo '---------------> this is frontpage.';
?>
=== [https://wiki.php.net/rfc/json_validate New json_validate() function]
>
> This function is a high-performance way to validate json prior to decoding it. This function cannot be polyfilled without a performance hit.
>
> However, due to the potential for using json for Denial-of-Service attack vectors (via a HUGE file/stream), I would strongly recommend for WP Core to start using this new function in all appropriate places wrapped within an `if ( function_exists() ) {}`.
>
> The `json_decode()` function is used 44 times within `src` (excluding external dependencies).
>
> We may want to consider introducing a `wp_json_decode()` function to ensure the use of `json_validate()` (when available).
> This would then mirror the already existing [https://developer.wordpress.org/reference/functions/wp_json_encode/ `wp_json_encode()`] function." jrf
Needs Dev / Bug Wrangler Feedback 59233 Improve error handling for unserialize() General normal normal 6.6 task (blessed) new dev-feedback 2023-08-28T23:47:32Z 2024-02-26T22:05:20Z "From https://core.trac.wordpress.org/ticket/59231:
> === [https://wiki.php.net/rfc/unserialize_warn_on_trailing_data Make unserialize() emit a warning for trailing bytes]
>
> While based on the current test suite, WP is not ''directly'' affected by this, the [https://developer.wordpress.org/reference/functions/maybe_unserialize/ `maybe_unserialize()`] function could still be confronted by data with trailing bytes.
>
> However, the call to the PHP native `unserialize()` within `maybe_unserialize()` silences all (PHP 8.0+: non-fatal) errors, so this new warning will not affect WP or its ecosystem as long as the `maybe_unserialize()` function is used.
>
> Having said that, a critical look at `maybe_unserialize()` may be warranted as the new warning in PHP is related to security issues discovered in other projects, so WP may want to consider rejecting unserialization for data throwing this warning.
>
> Also note that there are 7 uses of `unserialize()` in total within WP Core, one within `maybe_unserialize()`, but the function is also used in 6 other places and 5 of those do not use error silencing.
>
>
> === [https://wiki.php.net/rfc/improve_unserialize_error_handling Improve unserialize() error handling]
>
> This, again, affects the [https://developer.wordpress.org/reference/functions/maybe_unserialize/ `maybe_unserialize()`] function and this time, the code should probably be adjusted to handle the new errors which `unserialize()` can now throw.
>
> The change does not affect unserializing valid data, but in the case of invalid data, the type of and severity of the notices/warnings/catchable exceptions have been changed.
>
> All 7 uses of `unserialize()` in WP Core should be reviewed and for the 6 uses outside of the `maybe_unserialize()` function, it should be reviewed whether they can/should switch to using `maybe_unserialize()` and/or whether they should get their own (improved) error handling.
" jrf
Has Patch / Needs Testing 59232 Introduce #[Override] attribute to mark overloaded methods General 6.4 normal normal 6.6 enhancement new has-patch 2023-08-28T23:44:04Z 2024-02-12T09:16:58Z "From https://core.trac.wordpress.org/ticket/59231:
> === [https://wiki.php.net/rfc/marking_overriden_methods Marking overridden methods]
>
> This is a new feature which will be introduced in PHP 8.3, with limited validation functionality attached. The attribute basically allows to mark methods in a (child) class/interface which overload a method in a parent class or from an interface, as doing so intentionally.
>
> Per the RFC:
> > ... being able to express if a method is intended to override another method or implement an interface would make it easier to debug a mistake, to refactor and to clean up existing code. Another possible use case is to easily detect a possibly breaking change in a parent class that was provided by a library without needing to read the changelog in detail or missing some item in the list of changes
>
> I'd like to advocate for adding these attributes to WP Core in all the relevant places as it:
> * Increases awareness of the method overload for contributors.
> * Can serve as a warning that the method signature should not be touched (unless the parent method signature changes).
> * Has no downside as attributes are ignored in older PHP versions and in PHP versions where the attribute referenced does not exist.
>
> In the rare case that the attribute, once added, would result in a fatal error, that would be fantastic, as that means we have actually found a bug in WP before it got into a stable release." jrf
Has Patch / Needs Testing 59231 Prepare for PHP 8.3 General 6.4 normal normal 6.6 task (blessed) new has-patch 2023-08-28T23:15:51Z 2024-02-17T16:12:34Z "This is a meta ticket to track the efforts to prepare for PHP 8.3.
For PHP 8.0/8.1/8.2 specific fixes, please refer to the generic WP 6.4 PHP 8.x ticket: #58850
Please link patches related to a specific PHP 8.3 related task to the appropriate dedicated issue, if there is one (see the links in the description below).
Generic/one-off PHP 8.3 related patches can be linked to this ticket.
----
== PHP 8.3: Important dates
PHP 8.3 is [https://wiki.php.net/todo/php83 expected to be released on November 23 2023].
Other note-worthy dates:
* The first alpha was released on June 8th 2023.
* Feature freeze started on July 18, 2023.
**Note**:
The below represents the status per August 28, 2023. As PHP 8.3 is in feature freeze, these statuses should be reasonably reliable.
== Readiness of essential tooling
=== [https://github.com/composer/composer Composer]
Current status:
* CI for Composer itself was not yet being run against PHP 8.3. I've opened [https://github.com/composer/composer/pull/11601 a PR] for this. ''[JRF: this PR has since been merged]''
* I've ran linting, PHPCompatibility (bleeding edge) and the test suites against PHP 8.3 and found no problems for PHP 8.3 though.
* The only issues I've managed to identify are in the test suite of Composer, which has no impact on end-users of Composer.
=== [https://github.com/sebastianbergmann/phpunit PHPUnit]
Current status:
* CI for PHPUnit itself is being run against PHP 8.3.
* No known issues in the last release supported for the WP test suite (9.6.11).
=== [https://github.com/Yoast/PHPUnit-Polyfills PHPUnit Polyfills]
Current status:
* CI for PHPUnit Polyfills itself is being run against PHP 8.3.
* No known issues in the last release (1.1.0).
=== [https://github.com/wp-cli/wp-cli WP-CLI]
Current status:
* CI for WP-CLI was not (yet) being run against PHP 8.3. A [https://github.com/wp-cli/.github/pull/68 PR to change this has been opened and merged].
* **''Status unknown''**.
=== Other tooling
Other (PHP) tooling doesn't necessarily have to run against PHP 8.3 (yet), so has not been evaluated.
== Initial DevOps Tasks
Typical tasks which need to be executed to allow WordPress to prepare for PHP 8.3:
=== [https://github.com/WordPress/wpdev-docker-images Docker]
* Add PHP 8.3 to the Docker images. A [https://github.com/WordPress/wpdev-docker-images/pull/113 PR for this] was merged on July 26, 2023
=== GitHub Actions
* Add PHP 8.3 to the GitHub Actions `phpunit-tests.yml` configuration. [https://github.com/WordPress/wordpress-develop/pull/5106 GH PR #5106] ''[JRF: this PR has since been merged]''
Notes:
- Test failures on PHP 8.3 should not (yet) fail the build, but as the actual script to run the tests has been moved, it is currently impossible to use `continue-on-error` as that keyword is not supported when calling a reusable workflow... /cc @desrosj
== PHP 8.3 changes for which WordPress will need to prepare
=== [https://wiki.php.net/rfc/deprecations_php_8_3 Generic deprecations for PHP 8.3]
Based on initial (bleeding edge) PHPCompatibility scans + the tests, WP is not affected by the deprecations which passed from this RFC (not all of them did).
=== [https://wiki.php.net/rfc/deprecate_functions_with_overloaded_signature Deprecation of functions with overloaded signatures]
This RFC only partially affects PHP 8.3. If a replacement is readily available already, the deprecation of the overloaded signature takes place in PHP 8.3.
If no replacement was available, the replacement functions are being introduced in PHP 8.3 and the actual deprecation of the overloaded signature takes place in PHP 8.4.
Based on initial (bleeding edge) PHPCompatibility scans + the tests, WP is affected by two of the deprecations in PHP 8.3:
* `get_class()` and `get_parent_class()` - this is already being tracked in #58876, there is a patch available, which IMO is ready for commit. ''[JRF: the PR for this has since been merged]''
* `ReflectionProperty::setValue()` with static properties. [https://github.com/WordPress/wordpress-develop/pull/5105 GH PR #5105] ''[JRF: this PR has since been merged]''
The other deprecations in this RFC do not appear to affect WP Core at this time.
There is one - `stream_context_set_option()`, which will impact Requests, but only in PHP 8.4 and [https://github.com/WordPress/Requests/pull/822 a patch has already been pulled] for this.
=== [https://wiki.php.net/rfc/saner-inc-dec-operators Saner increment/decrement operators]
To my surprise, I have not found any issues in WP with this change based on the tests alone, but I would not be surprised if the odd issue around this gets reported over time.
=== [https://wiki.php.net/rfc/marking_overriden_methods Marking overridden methods]
This is a new feature with limited validation functionality attached. The attribute basically allows to mark methods in a (child) class/interface which overload a method in a parent class or from an interface, as doing so intentionally.
Per the RFC:
> ... being able to express if a method is intended to override another method or implement an interface would make it easier to debug a mistake, to refactor and to clean up existing code. Another possible use case is to easily detect a possibly breaking change in a parent class that was provided by a library without needing to read the changelog in detail or missing some item in the list of changes
I'd like to advocate for adding these attributes to WP Core in all the relevant places as it:
* Increases awareness of the method overload for contributors.
* Can serve as a warning that the method signature should not be touched (unless the parent method signature changes).
* Has no downside as attributes are ignored in older PHP versions and in PHP versions where the attribute referenced does not exist.
In the rare case that the attribute, once added, would result in a fatal error, that would be fantastic, as that means we have actually found a bug in WP before it got into a stable release.
Separate ticket to allow for discussing this proposal in more detail and for patches: #59232.
=== [https://wiki.php.net/rfc/unserialize_warn_on_trailing_data Make unserialize() emit a warning for trailing bytes]
While based on the current test suite, WP is not ''directly'' affected by this, the [https://developer.wordpress.org/reference/functions/maybe_unserialize/ `maybe_unserialize()`] function could still be confronted by data with trailing bytes.
However, the call to the PHP native `unserialize()` within `maybe_unserialize()` silences all (PHP 8.0+: non-fatal) errors, so this new warning will not affect WP or its ecosystem as long as the `maybe_unserialize()` function is used.
Having said that, a critical look at `maybe_unserialize()` may be warranted as the new warning in PHP is related to security issues discovered in other projects, so WP may want to consider rejecting unserialization for data throwing this warning.
Also note that there are 7 uses of `unserialize()` in total within WP Core, one within `maybe_unserialize()`, but the function is also used in 6 other places and 5 of those do not use error silencing.
=== [https://wiki.php.net/rfc/improve_unserialize_error_handling Improve unserialize() error handling]
This, again, affects the [https://developer.wordpress.org/reference/functions/maybe_unserialize/ `maybe_unserialize()`] function and this time, the code should probably be adjusted to handle the new errors which `unserialize()` can now throw.
The change does not affect unserializing valid data, but in the case of invalid data, the type of and severity of the notices/warnings/catchable exceptions have been changed.
All 7 uses of `unserialize()` in WP Core should be reviewed and for the 6 uses outside of the `maybe_unserialize()` function, it should be reviewed whether they can/should switch to using `maybe_unserialize()` and/or whether they should get their own (improved) error handling.
Separate ticket to allow for discussing this and the previously listed RFC in more detail and for patches: #59233.
=== [https://wiki.php.net/rfc/assert-string-eval-cleanup Deprecate remains of string evaluated code assertions]
As WP Core does not use assertions, it is not affected by the changes in this RFC.
Plugins/themes may still be affected, though I'd hope none of those would use `assert()`.*
* `assert()` is intended for dev-only use. The behaviour of `assert()` is heavily affected by ini settings which cannot be changed at runtime, which means that end-users may be confronted by unexpected fatal errors due to the use of `assert()` if they run on an incorrectly configured webhost.
=== [https://wiki.php.net/rfc/proper-range-semantics Define proper semantics for range() function]
This RFC adds a number of errors and warnings for incorrect use of the `range()` function.
WP Core has 8 uses of this function in `src`, 2 in `class-wp-text-diff-renderer-table.php` and 6 in various files from external dependencies.
I've visually reviewed each of these and they all look to be okay, though a check to safeguard that the WP native uses are covered sufficiently by tests would be prudent. [TODO]
=== [https://wiki.php.net/rfc/datetime-exceptions More Appropriate Date/Time Exceptions]
This RFC reclassifies warnings and errors from the DateTime extension to catchable Exceptions when the OO-interface is used (procedural use of the DateTime functionality is not affected).
Based on the tests, WP Core is not affected by this and as the DateTime use of WP Core is pretty well tested, I'm fairly confident, we'll be fine.
=== [https://wiki.php.net/rfc/json_validate New json_validate() function]
This function is a high-performance way to validate json prior to decoding it. This function cannot be polyfilled without a performance hit.
However, due to the potential for using json for Denial-of-Service attack vectors (via a HUGE file/stream), I would strongly recommend for WP Core to start using this new function in all appropriate places wrapped within an `if ( function_exists() ) {}`.
The `json_decode()` function is used 44 times within `src` (excluding external dependencies).
We may want to consider introducing a `wp_json_decode()` function to ensure the use of `json_validate()` (when available).
This would then mirror the already existing [https://developer.wordpress.org/reference/functions/wp_json_encode/ `wp_json_encode()`] function.
See: #59234
== Status of External Dependencies
=== [https://github.com/JamesHeinrich/getID3 GetID3]
Current status:
* Linting is enabled against PHP 8.3. The build passes without finding any PHP 8.3 related issues.
* **Important**: the project has no test suite, so the linting passing on PHP 8.3 is only a small comfort and does not provide any real security.
* In other words: **''status unknown''**.
* WordPress is using the latest version (1.9.22), see #56692
=== [https://github.com/PHPMailer/PHPMailer PHPMailer]
Current status:
* Linting and tests are being run against PHP 8.3.
* No known issues in the last release (6.8.0) (aside from something in the PHPMailer test suite, which doesn't affect WP).
* WordPress is using the latest version, see #57873
=== [https://github.com/WordPress/Requests Requests]
Current status:
* Linting and tests are being run against PHP 8.3.
* No known issues in the last release (2.0.7) (aside from something in the Requests test suite, which doesn't affect WP).
* WordPress is using the latest relevant version `2.0.6`, see #58079. Requests 2.0.7 only updated the certificates bundle, while WP uses its own)
=== [https://github.com/simplepie/simplepie SimplePie]
Current status:
* Tests are being run against PHP 8.3.
* No known issues in the current `master` branch.
* WordPress is behind and is still using version `1.5.8`, while the latest release is `1.6.0`, see #55604
I've done a test run of SimplePie 1.5.8 against PHP 8.3 and based on the tests, there are no relevant PHP 8.3 issues known at this moment.
=== [https://github.com/paragonie/sodium_compat Sodium Compat]
Current status:
* A [https://github.com/paragonie/sodium_compat/pull/160 PR has been opened] to enable running of the tests against PHP 8.3. The build passes without finding any PHP 8.3 related issues. ''[JRF: this PR has since been merged]''
* No known issues in the last release (1.20.0).
* WordPress is using the latest version, see #58224.
=== [https://github.com/openwall/phpass PHPass]
Current status:
* Tests are being run against PHP 8.3.
* No known issues in the current `main` branch, which translates to the `0.5.4` version.
* WordPress is using version `0.5.0`, but the script is a little out of sync with upstream, though not in a way that it impacts the running of WP on PHP 8.3." jrf
Needs Patch 59228 Links in 6.3 missing new window.nofollow.etc Editor 6.3 normal normal Awaiting Review defect (bug) new 2023-08-28T18:01:09Z 2024-01-25T21:05:12Z "Hi
Updated to 6.3 and when adding a link can add the link but there is no option for new window, nofollow, etc like before. I assume it is just missing not intentionally so passing it on. I can add it with code using the code editor but not as easy.
Thanks in advance" tradiecorp
Needs Patch 59216 add a filter on WP_User::get_data_by() Users normal normal Awaiting Review feature request new 2023-08-27T09:59:55Z 2023-08-27T09:59:55Z "Hello i speak about this function https://github.com/WordPress/wordpress-develop/blob/6.3/src/wp-includes/class-wp-user.php#L193-L260
function WP_User::get_data_by()
$user = $wpdb->get_row(
$wpdb->prepare(
""SELECT * FROM $wpdb->users WHERE $db_field = %s LIMIT 1"",
$value
)
);
It would be cool to filter the query or provide a own query.
Backstory: i run a shop under different domains and want that user can register with the same mail on different domains but in background is the same WP Instance.
" stefanxyz
Needs Reporter Feedback / Steps To Reproduce 59215 Bug in wp_set_post_categories function Taxonomy 6.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-27T07:58:34Z 2023-08-31T04:49:17Z `wp_set_post_terms( $post_id, $post_categories, 'category', $append );` category is being passed staticky. so `wp_set_post_categories` is not working to map custom category with custom post type. it is not making any entry for custom post type in the table `wp_term_relationships`. faaiq
Needs Patch 59211 Plugins should be sandboxed on update to prevent fatal errors Plugins normal normal Awaiting Review enhancement new 2023-08-26T11:33:27Z 2023-08-26T11:33:27Z "If a plugin is already active, it will be updated without sandboxing.
Steps to reproduce:
- install a plugin
- copy the plugin folder elsewhere
- make a change in code which will trigger a fatal error (call for non-existing class for example)
- bandle the changed folder into zip and install through the plugin upload" oglekler
Has Patch / Needs Testing 59207 Twenty Thirteen: correct styling for Button & File block links in front-end widget areas (Footer & Sidebar) Bundled Theme 5.8 normal normal Awaiting Review defect (bug) new has-patch 2023-08-25T17:56:24Z 2023-09-03T04:55:04Z "**Twenty Thirteen Theme:** Button Block Background & Text Color issue & File Button Text Color issue in Frontend Widget Section
**Step to Reproduce the Issue:**
===========================
1. Activate Twenty Thirteen Theme.
2. Take Button Block in Widget Section.
3. Check With Default Button styles and Also Check with Background Color & Text Color Selection in Button Block.**(Frontend & Backend button text Colors & Background colors are different)**
4. Check With File Block in Main Widget Area Section** (Button's Text Are not Visible in Frontend Footer)**
**
You will able to see below issues:**
============================
i) Default Button Background Color & Text Color are not same in Backend Widget Section and in Frontend.
ii) User Selected Text Color & Background Color are not showing in front-end Widget section.
iii) When Add File button in Footer Widget Section(Main Widget) , Text is not visible in Frontend Side in footer section.
I have attached video for better understanding.
Video URL : https://drive.google.com/file/d/1kZtfeubGmEWfMrS5cU78eqBXdwKcD8Po/view" shailu25
Changes Requested 59204 Twenty Nineteen: Separator block does not center as expected Bundled Theme normal normal 6.6 defect (bug) new changes-requested 2023-08-25T10:59:49Z 2024-02-05T20:56:50Z "Steps to reproduce the issue.
1. Activate Twenty Nineteen theme.
2. Take Separator block.
3. Choose WideLine option.
4. Applied Align-center
You can able to see both the side in editor and in the Front side that the Separator is not Center aligned.
I have attached video for better understanding.
Video URL :-https://share.cleanshot.com/TMvKdn60v7Jh0rzKmNG0" nidhidhandhukiya
Changes Requested 59203 Twenty Nineteen: fix Separator block's full-width size and placement Bundled Theme 6.3 normal normal Awaiting Review defect (bug) new changes-requested 2023-08-25T10:51:40Z 2023-09-06T03:55:07Z "Steps to Reproduce the issue :-
1. Activate Twenty Nineteen Theme.
2. Take Separator Block.
3. Choose Default from the styles.
4. Choose Full-width.
You can able to see two issues.
1> In editor side the separator is not visible.
2> Both side editor and front end even after applying full-width it is not showing in full width.
I have attached video for better understanding.
Video URL :- https://share.cleanshot.com/4ybJ9CQsCPR33NW1DPLm" nidhidhandhukiya
Needs Patch 59201 Taxonomy Query Loop Editor normal normal Awaiting Review feature request new 2023-08-25T08:22:58Z 2023-08-25T14:29:42Z "Hello,
In the page editor and FSE, we really need a way to query terms like the ""Query Loop"" block does.
Am I the only one who needs this?
A ""**Taxonomy Query Loop**"" block would list them by tree structure, displaying the title and description.
Either inherited from the query, or on a specific taxonomy and a specific parent term.
Thank you so much
Stephan" StephanR
Changes Requested 59195 deprecation notice triggered in post.php by passing null to parameter #2 in preg_match() Media 6.3 normal normal Awaiting Review defect (bug) new changes-requested 2023-08-24T20:01:52Z 2024-02-15T17:32:16Z "I've trying to force myself to use PHP 8.2 to get our plugins into shape, but am still running into a deprecation notice in post.php when viewing the Media Library in list mode:
{{{
PHP Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /sites/test.example.com/files/wp-includes/post.php on line 3298
}}}
Checking if $real is true before preg_match() is run seems to fix this particular one, but maybe to be safe an is_string( $real ) should be run also?" nosilver4u
Needs Patch 59194 Lazy Loading not applying at all in the front page template Editor 6.3 normal critical Awaiting Review defect (bug) new 2023-08-24T19:42:58Z 2023-08-24T19:51:22Z We have many sites built in the full site editor, but none of the images will lazy load within the front page template. No images have the lazy load attribute and google page speed insights detect that none of them are lazy loaded devoantor
Needs Reporter Feedback / Steps To Reproduce 59192 New image crop interface don't work in windows 10. Scale works. Media 6.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-24T18:33:19Z 2023-08-29T21:44:29Z "Win 10, 64GB RAM, Plenty SSD
Shared hosting, Dreamhost
Browsers tried: Chrome, Brave, Firefox, even Opera...
Loving the new image-edit interface concept, but:
Media -> Select Image -> Edit Image -> Crop -> AR: 1:1 -> Apply Crop -> ... Nothing
Save Edits remains gray. No changes made.
Media -> Select Image -> Edit Image -> Scale -> New Dim: 500w -> Scale ... ""Image Saved"" notice. ""Save Edits"" remains gray. Changes saved.
I'm trying to scale and crop an image. It looks like a better workflow than before, but this crop is still a no-go.
I am pretty familiar with the old method, so the new method will certainly be an improvement. I use WordPress's crop function regularly. I'd love to see the fixed asap.
Hope this helps.
Chris" Laughter On Water
Needs Patch 59191 Disqus Commenting Plugin Blocked by Twenty Twentythree Theme Comments normal normal Awaiting Review defect (bug) new close 2023-08-24T18:19:29Z 2023-08-24T20:03:20Z "Hi there,
This is Ryan at Disqus. We've noticed that WordPress theme Twenty Twenty-three blocks the Disqus Commenting Plugin from loading, which is confusing for WordPress site owners trying to use and test this plugin, or install Disqus generally to their site while using this theme.
Please note that the Disqus plugin is designed to load over and replace the native WP comments form. I've attached two images of the same page with different themes, and you can see Disqus appearing correctly in the theme with green background, but only the WP native comments form appears in the Twenty Twenty-three theme
We're happy to collaborate or provide additional details as needed, I can be reached directly at `email address removed`.
Edit by @audrasjb: email address removed." disqussupport
Needs Dev / Bug Wrangler Feedback 59182 Plugin/theme zip update screen max-width Upgrade/Install 5.5 normal minor Awaiting Review enhancement new dev-feedback 2023-08-24T09:55:54Z 2023-08-26T05:22:21Z "Hi,
Can we set the max-width to 100rem instead of 40rem?
Current CSS for wrap class.
{{{
.update-php .wrap {
max-width: 40rem;
}
}}}
it should be
{{{
.update-php .wrap {
max-width: 100rem;
}
}}}
let me know if this makes sense or not, please.
For more information see mentioned screenshot below.
" sumitsingh
Needs Dev / Bug Wrangler Feedback 59177 dbDelta doesn't handle changing the DEFAULT value of a column from NULL to '' Upgrade/Install normal normal Awaiting Review defect (bug) new dev-feedback 2023-08-23T15:40:02Z 2023-09-05T17:33:33Z "Shouldn't this be a strict comparison https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes/upgrade.php#L3064? Otherwise that condition will be false and the column will remain unchanged.
" bogdanhapcayardicom
Has Patch / Needs Testing 59173 Improve optimizations of get_site_url by not using switch_to_blog Networks and Sites normal normal Awaiting Review enhancement new has-patch 2023-08-23T14:15:11Z 2023-08-24T20:57:33Z "I belive a better approach would be to use the `WP_Site_Query` query, as in:
{{{#!php
domain . $site->path;
// If the network has a custom domain, use that instead.
if ( $site->domain !== \get_network()->domain ) {
$url = get_network()->domain . $site->path;
}
}
$url = set_url_scheme( $url, $scheme );
if ( $path && is_string( $path ) ) {
$url .= '/' . ltrim( $path, '/' );
}
/**
* Filters the site URL.
*
* @since 2.7.0
*
* @param string $url The complete site URL including scheme and path.
* @param string $path Path relative to the site URL. Blank string if no path is specified.
* @param string|null $scheme Scheme to give the site URL context. Accepts 'http', 'https', 'login',
* 'login_post', 'admin', 'relative' or null.
* @param int|null $blog_id Site ID, or null for the current site.
*/
return apply_filters( 'site_url', $url, $path, $scheme, $blog_id );
}
}}}
" PerS
Needs Reporter Feedback / Steps To Reproduce 59172 wp_query meta_query NOT EXISTS not creating correct sql query Database 6.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-23T12:53:28Z 2023-09-05T16:55:37Z "With the following wp_query:
{{{#!php
""ids"",
""post_type"" => ""shop_order"",
""post_status"" => array('wc-processing'),
""posts_per_page"" => ""-1"",
""offset"" => ""0"",
'meta_query' => array(
'relation' => 'AND',
array(
'key' => 'scg_is_glass',
'value' => ""1"",
),
[
'relation' => 'OR',
[
'key' => 'scg_processed',
'value' => ""0"",
'compare' => '=',
],
[
'key' => 'scg_processed',
'value' => ""0"",
'compare' => 'NOT EXISTS',
],
]
),
'date_query' => array(
array(
'after' => date('Y-m-d', strtotime('-1 month')),
),
),
);
}}}
The outputeed sql query is the following:
SELECT wp_posts.ID
FROM wp_posts
LEFT JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id )
LEFT JOIN wp_postmeta AS mt1 ON ( wp_posts.ID = mt1.post_id )
LEFT JOIN wp_postmeta AS mt2 ON ( wp_posts.ID = mt2.post_id AND mt2.meta_key = 'scg_processed' )
WHERE 1=1
AND (wp_posts.post_date > '2023-07-23 23:59:59')
AND (
( wp_postmeta.meta_key = 'scg_is_glass' AND wp_postmeta.meta_value = '1' )
AND (
( mt1.meta_key = 'scg_processed' AND mt1.meta_value = '0' )
OR **mt2.post_id IS NULL**
)
)
AND wp_posts.post_type = 'shop_order'
AND ((wp_posts.post_status = 'wc-processing'))
GROUP BY wp_posts.ID
ORDER BY wp_posts.post_date DESC
If you looked at the bolded (mt2.post_id IS NULL) above you would expect it to be:
**( mt2.meta_key = 'scg_processed' AND mt2.meta_value IS NULL )**" anteatersa
Needs Reporter Feedback / Steps To Reproduce 59170 Overlapping text when posting using iPhone Editor 6.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-23T09:27:02Z 2023-09-05T16:30:50Z "I have a website and I always get article submissions from authors, they write using Microsoft Office (maybe they use a bit older version, because the new 365 desktop version has no problem), on my iPhone I open the article using Office 365, and a strange thing happens :
1. If I use a block editor, the text will overlap
2. If I use the classic editor, many spaces are lost so that many words are attached without spaces.
here I provide you an example of overlapping text:
[https://drive.google.com/file/d/1c167tWdPd6k_n7_tWeRwi-9qOmgZ34nr/view?usp=sharing]
the website is freshly installed using twenty twenty three theme." readonecc
Has Patch / Needs Testing 59169 Deprecated arguments description is a bit misleading. General normal trivial Awaiting Review defect (bug) new close 2023-08-22T23:31:30Z 2023-08-23T09:39:10Z "Here: https://developer.wordpress.org/reference/functions/get_bloginfo/
in the description of the function
“Deprecated arguments include:
‘siteurl’ – Use ‘url’ instead”
is a bit misleading. “‘siteurl’ – Use ‘wpurl’ instead” is correct." sulemanhelp
Needs Patch 59164 Twenty Nineteen : Site Title Block Color Section is not reflecting properly in Editor & Frontend Side Bundled Theme normal normal Awaiting Review defect (bug) new 2023-08-22T12:42:49Z 2023-08-24T04:40:34Z "In Twenty Nineteen theme,
1. The colour selected is not reflected on the frontend side
2. When we select the background then the colour is not reflected in the editor also.
Video of the issue generated : https://drive.google.com/file/d/1dv9C0hRltm6bLbmfvw53sSEFj5Zz_lw0/view?usp=sharing" pitamdey
Needs Patch 59163 Fatal error: Cannot declare class WP_Metadata_Lazyloader, because the name is already in use in /home1/tarotcardco/public_html/wp-includes/class-wp-metadata-lazyloader.php on line 32 General normal normal defect (bug) reopened 2023-08-22T07:45:57Z 2023-08-22T11:24:59Z i can not login to backend how to fix this error ashwiniravipatil
Needs Patch 59162 Link not completely deleted in Firefox TinyMCE normal normal Awaiting Review defect (bug) new 2023-08-21T16:10:46Z 2023-08-24T20:23:11Z "**Steps to reproduce**
1. Create a new page
2. Insert a classic editor block
3. Enter ""Link1"" and ""Link2"" in separate paragraphs and link them to `https://link1.tld` and `https://link2.tld`. The resulting code should look like this:
{{{
}}}
4. Click on ""Save"" to close the block and reopen it afterwards
5. Start by marking the word ""Link1"" from the back, without clicking in the word first.
6. Press the Delete key on the keyboard. The text will be deleted, but the link will remain.
7. Press the Delete key again. The empty line will be deleted and the previously not completely deleted link will be applied to the text ""Link2"". Thus, Link2 no longer points to `https://link2.tld` but `https://link1.tld`.
**Expected result**
Link is completely deleted in step 6.
**Affected browsers**
Firefox (tested in version 116 on Windows 10 and 11)
**Test environment**
WordPress 6.3 with theme Twenty Twenty-Three 1.2 on PHP 8.1, no plugins installed" dawasi
Needs Patch 59158 Altering Details block styles doubling .wp-block-details class in the output Formatting 6.3 normal normal Awaiting Review defect (bug) new 2023-08-21T12:32:34Z 2023-08-21T13:47:23Z "By defaut Details block styles outputs styles for inner paragraph like:
{{{
.wp-block-details>:not(summary) {
margin-block-end: 0;
margin-block-start: var(--wp--style--block-gap);
}}}
----
If I want to change margin-block-start on the block level styles I use:
{{{
.wp-block-details>:not(summary) {
margin-block-start: 0;}
}}}
BUT it outputs:
{{{
.wp-block-details.wp-block-details>:not(summary) {
margin-block-start: 0;}
}}}
----
HOWEVER,
If I use the same in the Additional CSS section of Styles Editor it produce expected:
{{{
.wp-block-details>:not(summary) {
margin-block-start: 0;}
}}}
" randewoo
Has Patch / Needs Testing 59152 Need some css improvement on wordpress installation ( install.php ) page for mobile screen. General 6.4 normal normal Awaiting Review enhancement new has-patch 2023-08-20T09:51:54Z 2023-08-24T09:04:29Z We can improve the style ( spacing ) of description text below the password field on wordpress installation ( install.php ) page for mobile screen. See the screenshot for more clarification. ravigadhiyawp
Needs Dev / Bug Wrangler Feedback 59149 Inconsistent Behaviour of Block Editor while Adding/Searching for Blocks Editor 6.3 normal normal Awaiting Review defect (bug) new dev-feedback 2023-08-19T05:56:17Z 2023-09-02T06:32:59Z "WP Version 6.3
I'm facing an strange issue while searching the fields from the block editor.
When I'm at the end of page or when scroll to end of page then I'm trying to search a custom block it suddenly jump from its position. for details refer the below video url for same.
https://www.awesomescreenshot.com/video/20061317?key=12384a49ae5e729e95556d9498c1a107
" dhruval04
Needs Patch 59148 WordPress CDN/Mirror plugins/themes... General normal normal Awaiting Review feature request new 2023-08-19T04:16:53Z 2023-08-19T04:16:53Z "Hello.
Does the wordpress theme and plugin repository have a distributed CDN/Mirrors system?
We are a cloud hosting service provider in Vietnam.
Our customers 90% use wordpress. And when connecting to wordpress to download, update, and get plugin/theme information, the connection is often lost.
Because our country VN has a connection to the international or interrupted.
Don't know if WordPress.org has distributed servers to download data?" tranbinhcse
Has Patch / Needs Testing 59142 X/Twitter posts cannot be embedded Embeds normal normal 6.6 enhancement reopened has-patch 2023-08-18T15:42:05Z 2024-02-12T09:14:58Z When a link to a Tweet/X post is copied in the Twitter/X app (iPhone), it is the x.com address that is copied, not the twitter.com address. When this is inserted in a WordPress post, the post is not embedded, like a Twitter.com post. aphandersen
Needs Patch 59139 "Marketing / ""fairness"" : Change ""Classic Themes"" to ""Template Themes""" Themes normal normal Awaiting Review enhancement new 2023-08-18T12:03:39Z 2023-09-04T20:54:12Z "With total respect to the term ""Classic themes"", I think it feels old fashioned, which is a bit unfair to the power involved behind the scenes.
""Template Themes"" (WPTT) would be a recognition of WordPress pioneering a long time ago.
A tribute to it's visionary approach at that time.
And a tribute to its relevance and pioneering today, where we see so many tools and solutions being created with the same intent but not so powerful - if some recognition and dedication would be implemented to maintain it a state of the art solution.
FSE is super powerful.
PHP templating is super powerful." ridesirat
Needs Dev / Bug Wrangler Feedback 59138 Duotone filter selector does not apply when using Image block alignment Editor 6.3 normal normal Future Release defect (bug) new close 2023-08-18T10:52:33Z 2024-02-20T05:50:28Z "Steps to reproduce the issue :-
1. Activate Twenty Seventeen theme.
2. Choose Image block.
3. Use Alignment
4. Give Highlight or shadow to the block.
You can able to see it is working fine in editor side but having issue in front side when alignment is applied.
I have attached video for better understanding.
Video URL :- https://share.cleanshot.com/tDbCt0h3fTLVMMhbK4xt" nidhidhandhukiya
Needs Patch 59135 Ability to list plugins by activation date/time Administration normal normal Awaiting Review enhancement new 2023-08-17T20:47:28Z 2023-08-21T10:58:20Z "The idea here is to provide a way to show the list of active plugins ordered by activation date/time.
This was suggested by a friend of mine who was having a hard time tracking down which plugin on his site had caused a problem because he couldn't remember which one he had last activated. Given that deactivating plugins one at a time to track down which one is causing problems is a common technique, this seems like it might be generally helpful to WP users.
Details need to be flushed out on where and how to show this information. The plugins page seems like the most obvious target, the site health page might be another." josephscott
Changes Requested 59133 Collapse Menu title consistency Administration normal normal Awaiting Review enhancement new changes-requested 2023-08-17T18:25:16Z 2023-08-18T20:54:25Z "I notice a thing that every menu and submenu title in administration area are capitalize but Collapse menu title is different. I think it could be capitalize also.
" alireyad
Needs Reporter Feedback / Steps To Reproduce 59132 Create two filters in wp_scripts() and wp_styles(). Script Loader 4.2 normal normal Awaiting Review enhancement new reporter-feedback 2023-08-17T18:19:00Z 2023-11-27T21:00:48Z "I'd like to know if it's possibile to change this:
{{{#!php
myDynamicCallback(...);
self::myStaticCallback(...);
}}}
''**The 3 dots ""..."" are not omission - it is the syntax**''
Now this syntax actually works for `add_filter` however, it can fail (and I've encountered cases where it fails) for `remove_filter` which leads to very unexpected results.
Temporary bypass can be done using `remove_all_filters` or the old-school syntax `[__CLASS__, 'myStaticCallback']`.
The core issue is in the function `_wp_filter_build_unique_id` which generates the key under which the callback is stored, more specifically, in the way how the PHP's `spl_object_hash` work - this sentence from docs ""This id can be used as a hash key for storing objects, or for identifying an object, **as long as the object is not destroyed**.""
Now this is an educated wild guess, but I would guess that the callable objects created by the First-class callable syntax may not live that long and garbage collector can destroy them if it sees fit.
Anyways... the core is - `spl_object_hash` is NOT the right tool to cache ALL callables, but can only be used where the callable is passed around (e.g. stored in a variable) and therefore it is ensured it's still the same object (I would hope).
**Solution**
...for such cases is to create a `\ReflectionFunction` instance and check for `getClosureScopeClass()` and `getName()` :-)
https://www.php.net/manual/en/class.reflectionfunction.php
https://www.php.net/manual/en/reflectionfunctionabstract.getclosurescopeclass.php
https://www.php.net/manual/en/reflectionfunctionabstract.getname.php" jave.web
Needs Patch 59124 Dropdown navigation not displaying past the header Editor 6.3 normal major Awaiting Review defect (bug) new 2023-08-16T18:04:53Z 2023-08-16T18:58:36Z "This is happening on multiple sites. This is an example: https://www.mightyepiphyte.com/
Since the recent WordPress update the drop-down menu is no longer showing below the header." ManellyC
Needs Patch 59122 List blocks not working in 6.3 Post Formats 6.3 normal major Awaiting Review defect (bug) new 2023-08-16T15:49:38Z 2023-08-16T16:50:04Z "
List blocks can be created in editing, but it is glitchy and jumps around. When the post is saved, the list disappears, along with all information contained in it. Sometimes, it crashes the site (freezes, have to close out and restart)
This happened directly after updating to newest version 6.3
Reported by several people in forums https://wordpress.org/support/topic/ordered-unordered-lists-not-working-in-6-3/
" jennyd2
Needs Patch 59120 Measure interactivity metrics in performance tests Build/Test Tools normal normal Future Release defect (bug) new 2023-08-16T08:51:38Z 2023-10-27T10:15:36Z "This is a follow-up to #58360.
While we have some good load time metrics so far, we don't measure interactivity metrics yet.
We're particularly looking at these 3 metrics:
* [https://web.dev/tbt/ Total Blocking Time] (TBT)
* [https://web.dev/fid/ First Input Delay] (FID)
* [https://web.dev/inp/ Interaction to Next Paint] (INP)
They can be measured using libraries like Lighthouse or https://github.com/GoogleChrome/web-vitals.
Interactivity metrics require some sort of interaction during the test, so we need to figure out specifics.
" swissspidy
Needs Patch 59119 Measure layout stability metrics in performance tests Build/Test Tools normal normal Future Release defect (bug) new 2023-08-16T08:48:44Z 2023-08-16T08:48:44Z "This is a follow-up to #58360.
While we have some good load time metrics so far, we don't measure layout stability yet.
[https://web.dev/cls/ Cumulative Layout Shift] (CLS) can be measured using libraries like Lighthouse or https://github.com/GoogleChrome/web-vitals." swissspidy
Needs Patch 59117 The WORST of ALL Bugs (Version 6.3) General 6.3 normal normal Awaiting Review defect (bug) new 2023-08-15T21:47:15Z 2023-08-28T20:26:35Z "Dear friends, good afternoon. I know that, at 1st. Vista may believe that, this is not the right place to write this. But give me a few minutes and I will (de)show you that it is.
To gain time, below is the link to the ticket in which the subject was discussed;
https://wordpress.org/support/topic/huge-error-for-my-site-when-upgrading-to-6-3/page/2/#post-16969028
If they READ it all (That is, the 2 flaps that said ticket includes), they will realize (I hope) that…
1) It is a problem that you generated ONLY in the latest version 6.3
2) NONE of the solutions provided by v/collaborator WORKED.
3) They caused me (and they cause me) MANY inconveniences (even LEGAL)
To summarize (and in case you don't feel like reading so much, heh:)…
a) I have been designing my site on v/platform for +3 years. Ergo…
b) There is NO way for ME to implement the suggested fixes.
And that is why…
c) I am NOT going to update WordPress to its latest version (6.3) until this is resolved.
So, for finishing…
- Why do I say that it is a problem generated by you? Simple.
Because until version 6.2 I DID NOT have it.
- Why do I think they should fix it as soon as possible?
Because if you look, in the same forum, there are MANY similar claims in THAT sense.
And finally…
Why do I think this is the WORST security bug WordPress can have? Easy.
Because if it is not solved (FAST) I (and probably MANY more), will leave our installation with the previous version (6.2.2).
And – if so – as I'm sure you know, I'll be left open to whatever attacks you guys have sought to address with your latest version (6.3).
And then? So, if my hosting does not suspend me (Potential Legal Problem that I mentioned before), it could even affect other sites that are within my hosting (which is obviously shared, so I can NOT afford the ""luxury"" of anything else ).
Ergo. If many sites (like mine) do NOT update to 6.3 and like me, they share their hostings, a problem that is generated in one, could affect ALL of them.
Having said that…
If you keep track of these tickets, you'll see that in the +3 years I've been using WordPress, there was NEVER an entry to this section, which is said to be for…
…”suggest improvements and report bugs in WordPress”…
But it seemed necessary to me because, from what I see, SEVERAL days have passed since I created the ticket whose link I attached and, we did NOT find the solution.
And, what is worse, I do NOT think you will find them in the forums. Why? Simple.
Because if you READ the ticket in question in detail, you will see that the ONLY one in a position to provide a solution is WordPress itself!
That's all for now (I hope you understand).
I await your comments.
Thanks in advance.
Greetings.
PS: As I already mentioned in the ticket mentioned above, what will NOT happen is that…
I have to rewrite my ENTIRE site (+120 thousand words) for a problem that I did NOT create!
" atutrabajo
Needs Patch 59114 Infinite loop after upgrading from WordPress 6.1.3 to 6.2 Script Loader 6.3 normal normal Awaiting Review defect (bug) new 2023-08-15T20:20:09Z 2023-08-30T18:10:34Z "Regeristing a function with the 'wp_video_shortcode_library' filter hook that enqueues a script causes an infinite loop, resulting in WordPress running out of memory.
It seems that the $wp_scripts global is being set to null at some point and being reinitialized, which causes this loop since the 'wp_video_shortcode_library' filter is called as part of the wp_default_scripts function in script-loader.php. This is my theory anyways. I'm not familiar enough with the WordPress codebase to say for sure.
To recreate this issue, you can make a basic theme with an empty index.php, only the theme definition inside the style.css, an empty js file (to try to enqueue), and a functions.php that registers the hook.
{{{#!php
Limit: 20 row(s) (no early end due to SQL_CALC_FOUND_ROWS) (cost=744 rows=20) (actual time=12..13.1 rows=20 loops=1)
-> Sort: wp_posts.post_date DESC (cost=744 rows=3620) (actual time=12..12.8 rows=7407 loops=1)
-> Filter: ((wp_posts.post_type = 'attachment') and ((wp_posts.post_status = 'inherit') or (wp_posts.post_status = 'private'))) (cost=744 rows=3620) (actual time=0.0505..8.37 rows=7407 loops=1)
-> Index range scan on wp_posts using type_status_date over (post_type = 'attachment' AND post_status = 'inherit') OR (post_type = 'attachment' AND post_status = 'private') (cost=744 rows=3620) (actual time=0.0459..5.63 rows=7407 loops=1)
}}}
{{{
EXPLAIN ANALYZE SELECT SQL_CALC_FOUND_ROWS wp_posts.ID
FROM wp_posts
FORCE INDEX(idx_type_date)
WHERE 1=1
AND wp_posts.post_type = 'attachment'
AND ((wp_posts.post_status = 'inherit'
OR wp_posts.post_status = 'private'))
ORDER BY wp_posts.post_date DESC
LIMIT 0, 20
-> Limit: 20 row(s) (no early end due to SQL_CALC_FOUND_ROWS) (cost=142 rows=20) (actual time=0.214..15.3 rows=20 loops=1)
-> Filter: ((wp_posts.post_status = 'inherit') or (wp_posts.post_status = 'private')) (cost=142 rows=688) (actual time=0.211..15 rows=7407 loops=1)
-> Index lookup on wp_posts using idx_type_date (post_type='attachment') (reverse) (cost=142 rows=3619) (actual time=0.207..13.4 rows=7407 loops=1)
}}}
To replicate this, we've installed latest WordPress version and MySQL 8, and create the following post_status count structure:
{{{
mysql> select post_status, count(*) from wp_posts group by post_status;
+-------------+----------+
| post_status | count(*) |
+-------------+----------+
| inherit | 7407 |
| draft | 1 |
| publish | 23 |
| auto-draft | 1 |
+-------------+----------+
4 rows in set (0.01 sec)
}}}
Can this be considered as a core improvement to the wp_posts table that would directly benefit the Media related queries?
Basically, if MySQL 8 decides that the new index is faster, specially for Media search queries, it will simply pick that on up as opposed to using the original index or dropping it fully if it considers its much more efficient to do a full table scan.
From our database, a search query for term `test` shows an improvement of 0.5 seconds of this basic search media query:
{{{
MySQL []> SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts FORCE INDEX(type_status_date) WHERE 1=1 AND wp_posts.post_type = 'attachment' AND ((wp_posts.post_status = 'inherit' OR
wp_posts.post_status = 'private')) and post_title like ""%test%"" ORDER BY wp_posts.post_date DESC LIMIT 0, 1;
+---------+
| ID |
+---------+
| xxxxxxx |
+---------+
1 row in set, 1 warning (3.867 sec)
MySQL []> SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts FORCE INDEX(idx_type_date) WHERE 1=1 AND wp_posts.post_type = 'attachment' AND ((wp_posts.post_status = 'inherit' OR wppp_posts.post_status = 'private')) and post_title like ""%test%"" ORDER BY wp_posts.post_date DESC LIMIT 0, 1;
+---------+
| ID |
+---------+
| xxxxxxx |
+---------+
1 row in set, 1 warning (3.244 sec)
}}}
Thanks for considering this." ovidiul
Needs Patch 59104 duotone is not applied to videos in the cover block in safari Editor 6.3 normal normal Awaiting Review defect (bug) new 2023-08-14T16:01:43Z 2023-08-22T20:49:58Z "Dear Team,
duotone (svg filter) is not applied to videos in cover block in safari (screenshot safari). In edge for example it works (screenshot ms edge).
I would be very happy about a solution.
Many greetings
Kiril" kiandept
Needs Patch 59103 Gutenberg 16.4 Footnotes Critical Bug on PHP 8.0 Editor 6.3 normal critical Awaiting Review defect (bug) new 2023-08-14T15:58:42Z 2023-08-29T00:01:56Z "I am currently using WordPress version 6.3, PHP 8.0.
There is no issue initially when creating a post with the footnotes block, and is able to publish the post.
After a while, when trying to edit the same post again, I will see the critical error as such as seen in the attachment.
{{{
PHP Fatal error: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /wordpress/plugins/gutenberg/16.4.0/build/block-library/blocks/footnotes.php:37 Stack trace: #0 /wordpress/core/6.3/wp-includes/class-wp-block.php(258): gutenberg_render_block_core_footnotes(Array, '', Object(WP_Block)) #1 /wordpress/core/6.3/wp-includes/blocks.php(1133): WP_Block->render() #2 /wordpress/core/6.3/wp-includes/blocks.php(1171): render_block(Array) #3 /wordpress/core/6.3/wp-includes/class-wp-hook.php(310): do_blocks('
}}}
If I define the constant earlier, for example in the mu-plugins, the problem is solved.
Let me know, if I need to provide more details " margaritaperc
Needs Patch 59019 WP 6.3 deleted my additional CSS Upgrade/Install 6.3 normal critical Awaiting Review defect (bug) new 2023-08-09T11:01:22Z 2023-08-23T18:31:14Z "I’m developing a new site and trying out the FSE for the first time. My theme is a child of a third-party theme.
When I updated to WP 6.3 this morning it completely removed all of my CSS that I have been adding to the FSE > Styles > Additional CSS panel.
Luckily I had done a backup just before the update." petervandoorn
Needs Patch 59017 Duotone not working in 6.3 Editor 6.3 normal normal Future Release enhancement new 2023-08-09T07:35:24Z 2023-10-03T20:49:01Z "When the WordPress Accessibility Day website updated to 6.3 today the duotone filters we have set on images stopped working. Rolling core back to 6.2.2 solves this problem.
#58994 references changes to duotone in 6.3, however, bugs still exist.
Here's an example page on a site running 6.3 where duotone is no longer working: https://2023.wpaccessibility.day/about/organizers/. " alh0319
Needs Patch 59016 Able to login successfully .. but I'm unable to open wordpress dashboard.. General 6.3 normal normal Awaiting Review defect (bug) new 2023-08-09T07:06:53Z 2023-08-09T14:53:49Z skylerfashion
Needs Reporter Feedback / Steps To Reproduce 59015 Twenty Twenty-Three: Theme failure after updates Bundled Theme 6.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-09T05:03:36Z 2023-09-09T09:38:49Z "I updated WordPress to 6,3 - all OK.
I updated Twenty-Twenty-three theme.
Twenty-Twenty-three Live Preview returns completely blank screen.
(Active theme : Generate Press works fine)" rossbateson
Needs Patch 59014 PHP Fatal error in post-template.php Posts, Post Types 6.3 normal minor Awaiting Review defect (bug) new 2023-08-09T03:40:21Z 2023-10-31T00:34:33Z "Hi there,
I hope this email finds you well. Unfortunately, we've recently encountered a critical error that requires immediate attention. This issue pertains to the single page templates, specifically an example like this: https://volunteeringqld.org.au/governance/before-you-join/. The error was not present a week ago, and we're currently grappling to determine its cause. This problem was initially observed on both WP6.22 and WP6.3.
The post https://volunteeringqld.org.au/governance/before-you-join/ connected to a single template php `mytemplate/single-governance-before-you-join.php`, what calls `` what throws error ""There has been a critical error in this website"" and output steam finishes. Log error gives this line:
{{{
""PHP message: PHP Fatal error: Uncaught TypeError: Unsupported operand types: WP_Post - int in /.../wp-includes/post-template.php:330
Stack trace:
#0 /.../wp-includes/post-template.php(247): get_the_content()
#1 /.../wp-content/themes/volunteeringAU/single-governance-before-you-join.php(411): the_content()
#2 /.../wp-includes/template-loader.php(106): include('...')
#3 /.../wp-blog-header.php(19): require_once('...')
#4 /.../index.php(17): require('...')
#5 {main} thrown in /.../wp-includes/post-template.php on line 330', referer: https://volunteeringqld.org.au/governance/""
}}}
To address this, we have applied the following code snippet in `post-template.php` line 330:
{{{
if( ! is_int($page_no)) {
$page_no = 1; // Igor
//echo '';
}
}}}
When echo ancommented it gives
{{{
Array
(
[page] => WP_Post Object
(
[ID] => 5
[post_author] => 7
[post_date] => 2021-10-21 04:24:08
[post_date_gmt] => 2021-10-21 04:24:08
[post_content] =>
[post_title] => Home
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => home
[to_ping] =>
[pinged] =>
[post_modified] => 2023-05-26 13:50:03
[post_modified_gmt] => 2023-05-26 03:50:03
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://volunteeringqld.org.au/?page_id=5
[menu_order] => 0
[post_type] => page
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[more] => 1
[preview] =>
[pages] => Array
(
[0] =>
Achieving a good transition to the next volunteer who will take over from you has benefits for you, the organisation, and the incoming governance member. Let’s explore things you can do to ensure a good handover.
In this stage of your Governance journey we explore:
)
[multipage] => 0
)
}}}
As you can see, instead of having 1 in `$elements['page']`, it contains a `WP_Post` object of the very first post from the database, even not the one that is displayed.
We are hopeful that this information helps you in resolving the issue and that a solution will be included in an upcoming patch. Please don't hesitate to reach out if you require more details or assistance.
Best regards,
Igor
" volqld
Needs Patch 59012 Option to change Twitter Bird to Twitter X logo Bundled Theme normal normal Future Release enhancement reopened 2023-08-09T03:33:41Z 2023-08-15T05:29:38Z "The Twitter logo changed to X. The Twitter icon in the social widget block and embed block still has the bird logo in it.
" kafleg
Has Patch / Needs Testing 59009 units missing in media details Media normal normal Awaiting Review defect (bug) new has-patch 2023-08-08T22:15:29Z 2023-08-09T21:47:37Z "Some units are missing which have been there before, see #39667
Length and Dimensions have no units anymore. I don't know since when, just found out using v6.3
This is the view you get after clicking a video in media gallery (Attachment Details) and then click on ""Edit more details""" Presskopp
Needs Patch 59007 Allow to show an additional custom tagline on the blog page Themes 6.3 normal normal Awaiting Review enhancement new close 2023-08-08T20:51:06Z 2023-08-14T14:25:51Z "Hello everybody.
Here in Brazil, many major news portals have a part of the news that the editors call the Hat of the news.
It's like a subtitle of the news.
Ex:
Category: Politics
Hat: Confusion at the CPI
I would like to know if this is possible to be inserted in WordPress without the help of a plugin.
Example of sites that use this.
G1, UOL among others.
In this first print, see that the article is in the Politics category: https://prnt.sc/xOFhUjnjn7kT
But here, in the hat, the article category does not appear, a custom title appears: https://prnt.sc/zdaTa4W7DWSx" juniortavares
Changes Requested 59006 No title attribute on oEmbed and REST API s audrasjb Embeds 6.2.2 normal normal 6.6 enhancement reviewing changes-requested 2023-08-08T19:24:56Z 2024-02-20T09:28:35Z "By default, WordPress adds three `` of every post.
These are missing the `title=""...""` attribute. This means that some browsers will announce the links as ""alternate"" with no explanation of their destination - see screenshot attached.
The three links are:
{{{
}}}
Ideally, these would have `title=""JSON""`, `title=""oEmbed (JSON)""`, `title=""oEmbed (XML)""` or similar." edent
Needs Patch 58993 "metadata_exists() returns incorrect value when ""get_{$meta_type}_metadata"" filter returns false." Options, Meta APIs 6.2.2 normal normal Awaiting Review defect (bug) new 2023-08-07T14:58:38Z 2023-10-30T18:16:14Z "metadata_exists() applies the ""get_{$meta_type}_metadata"" filter. If the $single metadata value is false, 0, an empty string, or an empty array (see https://www.php.net/manual/en/language.types.boolean.php), then metadata_exists() will return false instead of true (ie. the metadata exists).
{{{
function metadata_exists( $meta_type, $object_id, $meta_key ) {
.
.
.
$check = apply_filters( ""get_{$meta_type}_metadata"", null, $object_id, $meta_key, true, $meta_type );
if ( null !== $check ) {
return (bool) $check;
}
}}}
If any value is returned, then the metadata exists, so the code should be:
{{{
function metadata_exists( $meta_type, $object_id, $meta_key ) {
.
.
.
$check = apply_filters( ""get_{$meta_type}_metadata"", null, $object_id, $meta_key, true, $meta_type );
if ( null !== $check ) {
return true;
}
}}}
js." jsmoriss
Needs Patch 58992 "get_metadata_raw() ""get_{$meta_type}_metadata"" filter can return incorrect value for $single = true" Options, Meta APIs 6.2.2 normal normal Awaiting Review defect (bug) new 2023-08-07T14:52:21Z 2023-10-30T18:10:59Z "The ""get_{$meta_type}_metadata"" filter includes the $single argument for the filter to return a single element or the complete metadata array. **If the single element happens to be an array**, and that array is returned because $single = true, then **the following code breaks the returned value** (it returns the first element instead of the array). If the array is an associative array, then it also breaks the returned value as `$check[0]` is not a valid element.
{{{
$check = apply_filters( ""get_{$meta_type}_metadata"", null, $object_id, $meta_key, $single, $meta_type );
if ( null !== $check ) {
if ( $single && is_array( $check ) ) {
return $check[0];
} else {
return $check;
}
}
}}}
Since $single is provided to the filter, the code should respect the returned value:
{{{
$check = apply_filters( ""get_{$meta_type}_metadata"", null, $object_id, $meta_key, $single, $meta_type );
if ( null !== $check ) {
return $check;
}
}}}
js." jsmoriss
Needs Patch 58991 Twenty Twenty One: font-weight setting doesn't work on button block Bundled Theme normal normal Awaiting Review defect (bug) new 2023-08-07T12:31:18Z 2023-08-07T12:31:18Z "Originally reported by @upadalavipul in the Gutenberg project.
https://github.com/WordPress/gutenberg/issues/53338
The Button block can have their font-weight changed using the Appearance control in the block sidebar. This style is applied to the element with the `.wp-block-button` class as inline style. However, Twenty Twenty One applies font-weight to the element with the `.wp-block-button__link` class in it, so that style is not applied." wildworks
Needs Patch 58989 Avatar block alignment is not working well in some themes Editor normal normal Awaiting Review defect (bug) new close 2023-08-07T07:02:48Z 2024-02-07T08:55:35Z "Avatar block alignment is not working in some themes like Twenty Twenty-one, Twenty nineteen, Twenty Seventeen and Twenty Sixteen but it is working fine with Twenty Twenty-two & Twenty Twenty-Three.
**The Main issue is that centre align is not reflected in editor side**
Here is a Video of the issue along with how it works :
https://drive.google.com/file/d/1YIng2VrJY9Zt1dgqD-Pg7_Lps4LaDoIW/view?usp=sharing" pitamdey
Needs Patch 58987 Unify usage of die(), die( '-1' ), exit(); General normal minor Awaiting Review enhancement new 2023-08-06T09:46:23Z 2023-08-06T12:46:51Z "like mentioned [[https://core.trac.wordpress.org/ticket/58420#comment:6|here]] I'd like to know if we want to unify the different die() calls we use:
{{{#!php
// Don't load directly.
if ( ! defined( 'ABSPATH' ) ) {
die( '-1' );
}
}}}
(mostly used, having a comment)
{{{#!php
if ( ! defined( 'ABSPATH' ) ) {
die();
}
}}}
(**not** having a comment), like seen in **\wp-admin\link-parse-opml.php**, **\wp-admin\site-health-info.php**
or even
{{{#!php
if ( ! defined( 'ABSPATH' ) ) {
exit();
}
}}}
like seen in **\wp-includes\rss-functions.php**" Presskopp
Needs Dev / Bug Wrangler Feedback 58986 TypeError: Unsupported operand types: string * int * Date/Time 6.2.2 normal normal Future Release defect (bug) reopened dev-feedback 2023-08-05T17:08:48Z 2024-03-18T17:57:31Z "Path: `/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php`
File: `class-wp-rest-posts-controller.php`
Line: 1833
**Expression Error:** `get_option('gmt_offset') * HOUR_IN_SECONDS`
**Rais Exception:** `TypeError: Unsupported operand types: string * int`
Suggested Fix: `intval(get_option('gmt_offset')) * HOUR_IN_SECONDS`
Thanks
" nurielmeni
Needs Patch 58984 WordPress FontSizePicker Default Label issue Editor 6.2.2 normal normal Awaiting Review defect (bug) new 2023-08-04T20:41:49Z 2023-08-05T03:57:39Z "If you have five or fewer font sizes, the WordPress `FontSizePicker` component will default to the labels 'S / M / L / XL / XXL'.
There doesn't appear to be a way to change these labels, which can problematic, for example if your names begin XS rather than S, or you use numbers for names e.g. 10 / 30 / 50.
To recreate the issue, within `theme.json`, add the following (or another) example of 5 or fewer default typography sizes to `settings.typography.fontSizes`:
{{{
""fontSizes"": [
{
""size"": ""clamp(0.625rem, 0.3438rem + 0.75vw, 1rem)"",
""slug"": ""10"",
""name"": ""10""
},
{
""size"": ""clamp(1rem, 0.7188rem + 0.75vw, 1.375rem)"",
""slug"": ""20"",
""name"": ""20""
},
{
""size"": ""clamp(1.25rem, 0.9688rem + 0.75vw, 1.625rem)"",
""slug"": ""30"",
""name"": ""30""
},
{
""size"": ""clamp(1.5rem, 1.2188rem + 0.75vw, 1.875rem)"",
""slug"": ""40"",
""name"": ""40""
},
{
""size"": ""clamp(1.875rem, 1.5938rem + 0.75vw, 2.25rem)"",
""slug"": ""50"",
""name"": ""50""
}
]
}}}
Then when editing any page, attempt to amend the paragraph size of text (or any other block that uses your font sizes). You'll see that the labels within the `FontSizePicker` component are 'S / M / L / XL / XXL', which have no relationship to the names that you'd set in `theme.json`.
Part of a solution could be to add a 'shortLabel' field to `theme.json` `settings.typography.fontSizes`, which would be used instead of the defaults by the `FontSizePicker` react component, when five or fewer font sizes are used.
An alternative solution would be to provide a slider, similar to padding and margin resizing." paulpooka
Needs Patch 58983 Old error message from 5.1 reappeared in 6.2.2 Networks and Sites 6.2.2 normal normal Awaiting Review defect (bug) new 2023-08-04T16:33:41Z 2023-08-08T16:29:04Z "The following error message appears in multisite installations after upgrade to 6.2.2
Performing the network upgrade doesnt seem to get rid of the message
`Notice: Function wp_check_site_meta_support_prefilter was called incorrectly. The wp_blogmeta table is not installed. Please run the network database upgrade. Please see Debugging in WordPress for more information. (This message was added in version 5.1.0.) in .../wp-includes/functions.php on line 5865`
The table itself doesnt seem to exist in the database nor is it being created. Its no affecting any multi site functionality though.
The hosting is Wp-Engine if that matters." namith.jawahar
Needs Patch 58982 Tools > Export does not include termmeta data for post categories Export 6.3 normal normal Awaiting Review enhancement new 2023-08-04T12:44:38Z 2023-08-04T18:07:11Z "Steps to reproduce
* Populate some posts and categories on a clean WordPress installation.
* Add some term meta fields to those categories.
* Go to Tools > Export and export Posts, then All categories.
* The export file contains no `wp:category` entry for any categories, hence categories term meta fields are not included.
* Go back to Tools > Export and export Posts, then a single category.
* The new export file contains no `wp:category` entry for the selected category, hence its term meta fields are not included either.
" jadpm
Needs Patch 58979 "Layout breaking while editing an Image from ""Image Details Edit"" screen." Media 6.3 normal normal Awaiting Review defect (bug) new 2023-08-04T04:57:06Z 2023-08-07T16:13:03Z "== Bug Report
=== Description
The layout is breaking while editing an Image from ""Image Details Edit"" screen.
=== Environment
- WordPress: 6.3-RC3
- PHP: 7.4.12
- Server: Apache/2.4.46 (Unix) OpenSSL/1.0.2u PHP/7.4.12 mod_wsgi/3.5 Python/2.7.13 mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_perl/2.0.11 Perl/v5.30.1
- Database: mysqli (Server: 5.7.32 / Client: mysqlnd 7.4.12)
- Browser: Chrome 114.0.0.0 (macOS)
- Theme: Twenty Twenty-Three 1.2
- MU-Plugins: None activated
- Plugins:
* WordPress Beta Tester 3.5.2
=== Steps to Reproduce
1. Open Media -> Library
2. Select an Image
3. Click the ""Edit Image"" button below the Image
4. Click ""Crop Image"". Crop settings are visible to the right of the Image
5. Now Click ""Scale Image"". Layout breaks.
x. 🐞 Bug occurs.
=== Expected Results
1. ✅ Layout Should not break. At the very least, it should be consistent for scale and crop.
=== Actual Results
1. ❌ Layout breaks and lack of consistency.
I am attaching Screenshots for reference." deepakvijayan
Needs Patch 58975 Replace image deletes the link! Editor 6.1.1 normal normal Awaiting Review defect (bug) new 2023-08-03T20:18:55Z 2023-08-03T20:18:55Z "For the image block Gutenberg block, in a widget sidebar panel, I noticed that whenever I go to ""replace"" the image for a Gutenberg widget - with one that is higher resolution for example, the link of the image goes away!
Noted this on several, both with ""upload"" and going to media library and uploading there." programmin
Needs Patch 58969 Privacy setting > The ''Copied'' text also shows, When double-clicking on the 'Copy suggested policy text to clipboard' option, Privacy 6.3 normal normal Awaiting Review defect (bug) new 2023-08-03T12:09:39Z 2023-08-07T16:11:03Z "
When double clicked the ''Copy suggested policy text to clipboard'' and paste it to the notes the ''copied'' text is also showing ( Only when double clicking )
=== Environment
- WordPress: 6.3-RC3-56344
- PHP: 7.4.33
- Server: TasteWP-S4 Official/3.0.0
- Database: mysqli (Server: 8.0.32-0ubuntu0.20.04.2 / Client: mysqlnd 7.4.33)
- Browser: Firefox 116.0 (Windows 10/11)
- Theme: Twenty Twenty-Three 1.2
- MU-Plugins: None activated
- Plugins:
* WordPress Beta Tester 3.5.2
=== Steps to Reproduce
1. Open the wordpress 'policies' section
2. Double Click on the 'Copy suggested policy text to clipboard 'option
3. Paste the policy on the notepad or notes
4. ''Copied '' text is showing
=== Expected Results
When you double-click on the 'Copy suggested policy text to clipboard' option, the 'Copied' text should not be displayed.
=== Actual Results
When you double-click the 'Copy suggested policy text to clipboard' option, the 'Copied' text is also displayed." vivekawsm
Needs Reporter Feedback / Steps To Reproduce 58967 Shortcode block text is not visible General 6.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-03T10:05:20Z 2023-08-14T10:18:36Z "Steps to reproduce the issue:
1. Create new page
2. Insert cover block
3. Insert shortcode block inside cover block
4. Result: shortcode block title and text are not visible because they are showing up with white font" johnquail
Needs Patch 58965 No luck running WP when running PHP 8.2.8 + mysql Ver 15.1 Database 6.2.2 normal normal Awaiting Review defect (bug) new 2023-08-02T22:29:45Z 2023-08-02T23:00:52Z "Welp, cannot figure out how to get the latest version of WP installed...when I load it I get this error message:
Your PHP installation appears to be missing the MySQL extension which is required by WordPress.
Please check that the mysqli PHP extension is installed and enabled.
I am using php-fpm and can see I have enabled: mysqlnd, pdo, pdo_mysql
Obv can't run mysqli anymore...so I am not even sure why I am seeing this mysqli error?
Anyone know how to work around it? Hopefully, it's just something dumb on my part but I am a bit restricted on the server this is running. " boyz2men
Needs Patch 58954 php 8.1 preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated General 6.2.2 normal normal Awaiting Review defect (bug) new 2023-08-01T12:43:30Z 2023-08-01T20:40:21Z "
Encountered when editing a page at /wp-admin/post.php?post=2&action=edit
On line 6811 of wp-includes/post.php
{{{
$ext = preg_replace( '/^.+?\.([^.]+)$/', '$1', $file );
}}}
I found a lot of these tickets on trac, but couldnt find any for this specific instance.
" TwentyZeroTwo
Needs Patch 58952 Add search to get_the_archive_title() Themes normal normal Awaiting Review enhancement new 2023-08-01T09:40:07Z 2023-10-27T22:09:16Z "Add search archive title to get_the_archive_title():
{{{#!php
Please wait ...
}}}
you will receive an error in the web development console section:
{{{
GET https://DOMAIN.COM/wp-includes/js/tinymce/plugins/code/plugin.min.js
Status 404 Not Found
}}}
== Does problem occur when all plugins deactivated and use the default theme?
N/A
== what is the expected output or result? What did you see instead?
The expected outcomes would be:
1) the direcotry and file '//DOMAIN.COM/wp-includes/js/tinymce/plugins/code/plugin.min.js'would be available
2) tinymce would show the code icon
3) no error displayed
== additional information
Not that this really matters for this, more related to wordpress version
os: alma 8.8
php: 7.4.33 AND 8.1
browser: not applicable
" jobst
Has Patch / Needs Testing 58948 Use Elvis operator (`:?`) to replace repeating ternary patterns (`a ? a : b`) General 6.3 normal trivial Awaiting Review enhancement new close 2023-07-31T17:54:39Z 2023-10-17T20:11:44Z "This is a somewhat big change, but a simple one at that.
Replaces `a ? a : b` patterns of ternary statements to use the Elvis operator `a ?: b`.
Null coalescing operator (`??`) was added in PHP 7.0, which WordPress now requires as the minimum version. However, to make this ticket focused and easier to review, this ticket only proposes the Elvis operator.
On tainted lines, it follows WordPress CS to use uppercase constants (`NULL` instead of `null`, for example), and removes a few cases of unnecessary braces. Apart from them, the diff output should be quite minimal and straight forward.
Perhaps, the review will be easier with word-diff (`git show --word-diff`), or on GitHub, where it highlights word diffs in the line-diff mode.
Thank you." ayeshrajans
Needs Patch 58945 Issues with downloading and unpacking plugins with PHP 8.2 Upgrade/Install 6.2.2 normal normal Awaiting Review defect (bug) new 2023-07-31T10:56:24Z 2023-10-28T23:46:33Z "Hello,
I've encountered an issue when trying to download and install plugins or update WordPress on PHP 8.2, both from the admin dashboard and using WP-CLI. This issue does not occur on PHP 8.1.
When attempting to install or update a plugin, the ZIP file is downloaded correctly, but when it comes to unzipping and installing, the process ends with an error of ""Could not copy file."". The same issue occurs during a WordPress update.
I conducted a series of tests trying to pinpoint the issue. I carried out tests with both native PHP functions (curl, copy) and WordPress functions (download_url, unzip_file) that are typically used for downloading and installing plugins and updates.
Moreover, I noticed that the issue also arises when trying to update to a previous version via WP-CLI. In this case, after the ZIP file is downloaded, unzipped, and attempted to install, an error of ""Warning: Could not copy file."" is produced.
Here seems to be a WP-CLI cache clearing issue as empty zip files remain
Given the above, I suspect that the problem might be due to some incompatibility between PHP 8.2 and the WordPress functions used for downloading and installing plugins and updates.
Could someone take a look at this issue? Any help would be greatly appreciated.
{{{
:~/public_html$ wp plugin update classic-editor
Downloading update from https://downloads.wordpress.org/plugin/classic-editor.1.6.3.zip...
Unpacking the update...
Installing the latest version...
Removing the old version of the plugin...
Plugin updated successfully.
+----------------+-------------+-------------+---------+
| name | old_version | new_version | status |
+----------------+-------------+-------------+---------+
| classic-editor | 1.6.1 | 1.6.3 | Updated |
+----------------+-------------+-------------+---------+
Success: Updated 1 of 1 plugins.
:~/public_html$ wp plugin update classic-editor --version=1.6.1
Installing Classic Editor (1.6.1)
Downloading installation package from https://downloads.wordpress.org/plugin/classic-editor.1.6.1.zip...
Unpacking the package...
Installing the plugin...
Removing the old version of the plugin...
Plugin updated successfully.
Success: Installed 1 of 1 plugins.
:~/public_html$ wp plugin update classic-editor
Downloading update from https://downloads.wordpress.org/plugin/classic-editor.1.6.3.zip...
Using cached file '/home/***/.wp-cli/cache/plugin/classic-editor-1.6.3.zip'...
Error: Error copying cached file /home/***/.wp-cli/cache/plugin/classic-editor-1.6.3.zip to https://downloads.wordpress.org/plugin/classic-editor.1.6.3.zip
:~/.wp-cli/cache/plugin$ ls -l
total 0
-rw-r--r-- 1 *** *** 0 Jul 31 10:40 classic-editor-1.6.1.zip
-rw-r--r-- 1 *** *** 0 Jul 31 10:40 classic-editor-1.6.3.zip
}}}
" pablo07
Needs Reporter Feedback / Steps To Reproduce 58944 Upload to Media Library not replicating to all pod's 6.2.2 Media 6.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-07-31T10:18:52Z 2023-10-04T15:34:54Z "Hello, after updating from WP 6.1.1 to 6.2.2 the new uploaded images start to apear ""broken"" on Media Library. If we refresh the page several time's we will see the image ok, but if we refresh it again it will be broken. We are running the WP in kubernetes, so we have several pod's. This behaviour means the uploaded image is no longer been replicated to all pod's. So it only exist's in one pod.
After reverting to 6.1.1 all is ok." vitorgandra
Needs Patch 58941 I have found a lot of bugs in fact General normal normal Awaiting Review defect (bug) new 2023-07-31T07:07:49Z 2023-07-31T07:07:49Z "Previously I've already reported a bug as the following link:
https://core.trac.wordpress.org/ticket/58875
There is a bug also for the styling in theme.json.
I found that once the default style in theme.json file is set, sometimes it is impossible to change again by the user as the style in theme.json have been set to !important.
For example, I've set the color for general text to be dark grey, and if I now assign a blue color to the paragraph text, this property is being overridden by theme.json's setting, as I can inspect the property of that text. It has been set to !important.
Well, I think that there is really a lot of bugs since I am just a normal user, I am not even a professional web developer. I can discover so many bugs within just a week.
I appreciate the search bar feature, but other than that, it is a bit horrible. " titanchan
Needs Patch 58939 Option to bypass fetch_feed cache on call. Feeds normal minor Awaiting Review feature request new 2023-07-30T20:47:35Z 2023-07-30T20:47:35Z "I have a use case where users are limited to the normal 12 hour cache restrictions, but I would like to enable admins to be able to bypass the cache and pull the feed.
Maybe a filter or optional parameter that would allow this? " picard102
Needs Patch 58938 Custom permalink indexing issue Customize 6.2.2 normal critical Awaiting Review defect (bug) new 2023-07-30T10:35:29Z 2023-07-30T10:35:29Z "Good morning,
If we choose the personalized permalink and remove the ""/"" at the end.
The site will not index, except for the homepage.
No message will appear in the search console.
Bug found twice on sites that weren't indexed for more than 30 days.
This unblocked the situation in 24 hours.
Cordially,
LECLERC-WEB" lavega45
Has Patch / Needs Testing 58935 White page on admin.php in WordPress Dashboard General normal normal Awaiting Review enhancement new has-patch 2023-07-29T18:09:08Z 2023-08-02T10:22:12Z "Hello there,
As we all know, plugins (e.g. WooCommerce, etc.) are using `wp-admin/admin.php` to handle their option pages.
e.g. `http://localhost/wp-admin/admin.php?page=wc-admin`
The problem is, when we navigate to `admin.php` without any query string, it shows a white screen. I believe we can improve it by showing a message or redirecting to the main page of the dashboard.
e.g. `http://localhost/wp-admin/admin.php`" masoudin
Has Patch / Needs Testing 58934 Twenty Twelve: Table Block does not align center on front end Bundled Theme 5.0 normal normal Awaiting Review defect (bug) new has-patch 2023-07-29T14:42:36Z 2023-08-02T05:45:03Z "The table block align center isn't working properly in the Twenty Twelve theme.
https://www.awesomescreenshot.com/video/19525205key=509a355b0cb5d20ad84771b9693fbad2" truptikanzariya
Needs Reporter Feedback / Steps To Reproduce 58933 plugin-install.php search works incorrect Plugins 6.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-07-29T11:41:02Z 2023-08-08T16:43:13Z "i got 29 pages as result of search but after i go to last page
more results coming
also search very weak by default
many irrelevant results coming after search with 2 keywords
" AlexeyVertinsky
Has Patch / Needs Testing 58932 wp_setup_nav_menu_item() throws PHP warning when using virtual menu-items Menus 5.4 normal normal Awaiting Review defect (bug) new has-patch 2023-07-29T00:25:24Z 2023-07-29T00:35:45Z "I believe this bug was introduced in [changeset:""47211""]
=== TLDR ===
`wp_setup_nav_menu_item()` calls `get_post()` but does no sanity checking before calling `get_post_states()` with what might be a null. Adding a simple `if ( $menu_post !== null )` before calling `get_post_states()` resolves this issue.
I've added a patch.
=== Details ===
I have an old plugin (pre-dating above commit) that renders custom dynamically-generated drop-down menus (eg. recent posts, yearly archives).
The plugin is somewhat based on https://www.ibenic.com/understanding-wordpress-menu-items/ but is a bit more involved. It's a stable and simple plugin.
The way the plugin works is it adds a single menu-item meta-box in the Menu editor page. However on the front it dynamically generates submenu items that don't show on the Edit Menu page. On the front the plugin creates virtual/fake `WP_Post` objects at runtime that are fed into `Walker_Nav_Menu_Checklist`. Therefore these objects have no corresponding `$menu_post` in the database.
Since WordPress 5.4, core throws multiple `Attempt to read property ""post_status|ID"" on null` notices on every page load. These notices have been upgraded to warnings in PHP 8.
{{{
wp-admin/includes/template.php:2288
get_post_states()
wp-includes/nav-menu.php:839
wp_setup_nav_menu_item()
wp-includes/nav-menu.php:839
array_map()
wp-includes/nav-menu.php:727
wp_get_nav_menu_items()
wp-admin/nav-menus.php:596
}}}" apedog
Needs Patch 58927 Set featured image missing General 6.2.2 normal major Awaiting Review defect (bug) reopened close 2023-07-28T07:13:02Z 2023-08-24T22:53:05Z "Latest version 6.2.2, php version 8.1
Why it happens - unknown
Happens even if all plugins deactivated, changed theme
Expected set featured image button, this section is missing
Theme support added to the functions.php, but this happens with all twenty themes as well
Server information below
Set featured image is missing, cannot set featured image. Tried all browsers, disabling all plugins, changing theme. Only installing ""disable gutenberg"" plugin helps and ""set featured image"" back again.
Fresh install.
Also this happens with other older websites (v6.1.1)
On some websites it works fine, but there is slight delay before it appears.
cPanel Version 110.0 (build 7)
Apache Version 2.4.57
MySQL Version 10.3.38-MariaDB-log-cll-lve
Architecture x86_64
Operating System linux
Path to Sendmail /usr/sbin/sendmail
Path to Perl /usr/bin/perl
Perl Version 5.16.3
Kernel Version 3.10.0-962.3.2.lve1.5.80.el7.x86_64" ernasx
Needs Patch 58924 Add a small precision on the documentation of the register_taxonomy function Taxonomy 6.2.2 normal minor Awaiting Review feature request new 2023-07-27T13:57:55Z 2023-07-27T14:15:27Z "Hello,
I was wondering if it wouldn't be interesting to add a little clarification here https://github.com/WordPress/wordpress-develop/blob/12a0205829c1411f16b4e216a713a153bcc62e2f/src/wp-includes/taxonomy.php#L410 .
Indeed, I searched for a while why when editing a CPT I did not have the categories in the form of a checkbox. By searching on https://developer.wordpress.org/reference/functions/register_taxonomy/ I found no indication about the change of UI of the choice of categories on the edition of a post.
I would find it interesting to add a very small precision to indicate that the `hierarchical` parameter changes the way of choosing its categories on a post: checkboxes if it is true, input text if false.
I hope I wrote and classified my ticket correctly, sorry if not, this is my first ticket / first contribution." ltrihan
Has Patch / Needs Testing 58921 wp_kses_allowed_html doesn't allow to add esi:include Formatting 3.5 normal normal Awaiting Review defect (bug) new has-patch 2023-07-27T10:19:28Z 2023-10-12T05:21:52Z "In my plugin I want to implement an [ESI exclusion](https://www.w3.org/TR/esi-lang/) for Litespeed using their filter like this:
{{{#!php
}}}
However, using the unescaped echo is bad practice and is not allowed by WooCommerce (my plugin is published on woocomerce.com, so I can't upload a version that's using `echo`).
So I tried using `wp_kses`.
Using the `wp_kses_allowed_html` filter, one could add custom tags to `wp_kses`. But it doesn’t work in this particular case because the ESI tag contains a colon `esi:include`.
I’m stuck here. I can’t change the [ESI specification](https://www.w3.org/TR/esi-lang/) which specifies the tag `esi:include`.
Litespeed (or any other technology that uses ESI) must consume the `esi:include` tag to work. That means we need to output the script somehow.
I think there should be a way to add custom tags like `esi:include`." alekv
Has Patch / Needs Testing 58917 Email Sending validation doesn't occur when password reset is sent from the Users page Users normal normal Awaiting Review defect (bug) new has-patch 2023-07-26T16:29:48Z 2023-08-15T04:37:20Z "Suppose my site isn't configured to send emails. So, when a user tries to reset his password from the public login page, he gets the below error.
https://prnt.sc/q_Z3IIC1f_dy
This is expected, but now, if I log in as an admin account, navigate under the Users page, and try to send the reset link for that user, I can see no validation error. The email doesn't get sent in real, but I can't see the error that my site isn't configured for sending emails.
https://prnt.sc/O9k_QpycwCfh
I think this type of behaviour is kind of confusing for users. We should show that validation error in the admin panel as well." rajinsharwar
Needs Patch 58916 Wrong User Password Reset Security 6.2 normal normal Awaiting Review defect (bug) new 2023-07-26T15:29:38Z 2023-07-29T00:28:47Z "We have a lot of users in our database. We occasionally have users in our database that have similar usernames, for instance: 'user 1' and 'user1'.
When a password needs to be reset via the e-mail reset link, sometimes the user_activation_key is populated for the wrong user when it was intended for 'user 1', it will be populated for 'user1' or the other way around.
They all have different user nicenames and e-mail addresses, but there must be some sanitizing going on with the username and password resets that is making similar but different usernames not technically unique.
" dappelman
Needs Patch 58914 Full-site editing theme warning about missing header.php Themes 6.2.2 normal minor Awaiting Review defect (bug) new 2023-07-26T13:46:15Z 2023-07-26T20:13:38Z "When using a theme compatible with full site editing, I get this warning from time to time when the page is redirecting. This can be replicated also in WordPress 6.3-RC2-56310 running Twenty Twenty-Three theme.
Deprecated: File Theme without header.php is deprecated since version 3.0.0 with no alternative available. Please include a header.php template in your theme. in /public/wp-includes/functions.php on line 5653" Iulia Cazan
Has Patch / Needs Testing 58909 width problem in the administration interface Administration normal normal Awaiting Review defect (bug) new has-patch 2023-07-26T07:58:35Z 2024-02-23T17:48:23Z "Hi,
With quick edit mode (any post), and with french language, the French translation causes line breaks in the author and password columns :
" pasglop
Needs Early Attention 58905 Ensure locate_template only loads theme files Themes normal normal 6.6 defect (bug) new needs-unit-tests 2023-07-25T19:44:43Z 2024-02-17T13:41:42Z "It's possible to have locate_template load files that are not template files which could be unexpected behavior that breaks the display of a page.
The chance this breaks something is, I think, not infinitesimal. Therefore, this should go in early.
An initial patch is attached.
" jorbin
Needs Patch 58904 delete_expired_transients() does not delete expired transient created with a false/empty transient name Options, Meta APIs 6.3 normal normal Awaiting Review defect (bug) new 2023-07-25T19:40:24Z 2023-07-25T19:40:24Z "Due to a typo/bug in my plugin code, I found that WordPress accepts empty strings, null, and false for the $transient arg, aka: the transient name, in set_transient() function which creates transients in the options database with values of simply `_transient_` and `_transient_timeout_`.
The empty string transient is not be cleaned up by the `delete_expired_transients()` routine.
Related is patch #58903, though I do not feel comfortable making a patch for this issue as the fix requires has SQL calls." jeremyescott
Needs Dev / Bug Wrangler Feedback 58903 set_transient() allows invalid transient name Options, Meta APIs normal normal Future Release defect (bug) new changes-requested 2023-07-25T19:33:17Z 2024-02-08T20:13:48Z "Due to a typo/bug in my plugin code, I found that WordPress accepts empty strings, null, and false for the `$transient` arg, aka: the transient name, in `set_transient()` function which creates transients in the options database with values of simply `_transient_` and `_transient_timeout_`.
That said... the transient created with an empty string continued to work (could be set and get and deleted). Because the typo in my code referenced a variable that held the transient name but was empty, the get, set, and delete function calls worked (annoyingly).
I did observer two issues...
1. In the event two developers cause the same mistake/error, their transients will collide with each other.
2. More importantly, I observed the empty string transient will not be cleaned up by the delete_expired_transients routine. (The Transients Manager plugin must use delete_expired_transients() as it could not delete the transient either.) I will submit a second ticket for this issue.
Upon review of the set_transient() and add_option() code, I observed several opportunities to improve, including:
- return false for empty $transient value
- return false for bool, non-scalar $transient values
- cast $transient as string
- return false for strings with more than 172 characters
These false returns will guide developers to fix issues with malformed $transient names.
I have a pull request to github ready to follow this ticket." jeremyescott
Changes Requested 58902 add_query_arg() should esc_url_raw() REQUEST_URI Formatting normal normal 6.6 defect (bug) new changes-requested 2023-07-25T17:43:33Z 2024-02-22T11:22:14Z "add_query_arg assumes that the query argument is an acceptable query argument. In order to help developers from accidently making a URL an unacceptable URL.
Some related tickets: #16859, #22951, and #22300.
The security team has reviewed this and ok'd it being worked on in public. " jorbin
Has Patch / Needs Testing 58901 Flush 'user_activation_key' after successfully login rajinsharwar Login and Registration normal normal 6.6 enhancement assigned has-patch 2023-07-25T08:38:46Z 2024-02-12T09:18:32Z "Hi all,
Let's imagine the next steps:
1. User goes to `{site_url}/wp-login.php?action=lostpassword` for getting reset password link to its email.
2. Then go to email and open the reset password link with an expiration time (`DAY_IN_SECONDS` by default). It has been resolved [https://core.trac.wordpress.org/ticket/32429 a long time ago]. But then he remembers his old password and login using a second web browser with its username and old password. At the same time, the link to reset the password remains active in the first browser for a whole day.
3. If it's a public laptop anybody can use the reset password link and login with new credentials and make some hacker things.
**Suggestions:**
Flush the 'user_activation_key' after successful login:
wp-includes/user.php::line 113 before
{{{
do_action( 'wp_login', $user->user_login, $user );
}}}
Can be added this line:
{{{
global $wpdb;
$wpdb->update(
$wpdb->users,
array(
'user_activation_key' => '',
),
array( 'ID' => $user->ID )
);
}}}
Best Regards!" nsinelnikov
Has Patch / Needs Testing 58900 Escaping: Output String did not run through a proper escaping function Security 3.4 normal normal Awaiting Review defect (bug) new close 2023-07-25T04:17:08Z 2023-12-08T21:03:05Z "In class-wp-customize-control.php on line 642 'New page title' did not run through any escaping function. I think esc_html_e() should be applied.
" armondal
Needs Dev / Bug Wrangler Feedback 58887 "Add a Pattern menu item to the ""+ New"" menu in the WP admin toolbar" Toolbar normal normal Future Release enhancement new dev-feedback 2023-07-24T07:49:59Z 2023-09-08T17:59:08Z "The WP admin toolbar has a menu with the text ""New"" and a dropdown with
links to adding a new post, media, page and user.
Consider adding a link to the patterns creation interface to this menu.
The new menu item should only be visible for users with the correct permissions.
" poena
Needs Patch 58886 When editing a pattern getting console error on chrome browser Editor normal normal Awaiting Review defect (bug) new 2023-07-24T07:49:43Z 2023-07-24T07:49:43Z "Chrome: Version 115.0.5790.102 (Official Build) (64-bit)
screenshot: https://prnt.sc/3XQEoNPkzv1A
" chiragrathod103
Needs Dev / Bug Wrangler Feedback 58884 "The image size for the Site Logo block is hard coded to ""full""" audrasjb* General normal normal Awaiting Review enhancement accepted close 2023-07-23T19:41:10Z 2023-09-20T08:27:57Z "The recommended size for the site icon is 512x512.
The Site Logo block is coded to use the ""full"" size, in general-templates.php:
{{{
$image = wp_get_attachment_image( $custom_logo_id, 'full', false, $custom_logo_attr );
}}}
If the icon is at the recommended size of 512x512, the full size is much too big for the common use of the Site Logo block (in the header). That leads to a ""Properly size images"" warning in page-speed tools." asafm7
Needs Patch 58880 HOLD 6.3 and FIX Template Parts vs. Patterns Editor normal major Awaiting Review defect (bug) new 2023-07-23T02:10:29Z 2023-07-25T00:15:33Z "In 6.3 ""Template Parts"" are now found under Patterns and rumored to eventfully be called
""Patterns""? Whoa! NOT GOOD! It is becoming WAY TOO confusing for my clients.
PLEASE keep Template Parts (""Partial Templates"" or ""Sub-Templates"" if you like) under the Templates section. If you think is better to call them ""Partial Templates"" or ""Sub-Templates"" that could be good.
**Here is what I’m suggesting:**
== Patterns
=== WP Library
-xxxx
-xxxx
=== ''user created''
-xxxx
-xxxx
== Templates
=== Full Templates
-Page
-Blog
-Blog List
-404
-''user created''
-etc.
=== Partial Templates or “Sub-Templates” or “Template Parts”
-Header
-Footer
-''user created''
-etc.
Thank you,
Douglas Knoyle" dougster123
Needs Patch 58875 The hover effect in theme.json is not working Editor 6.2.2 normal normal Awaiting Review defect (bug) new close 2023-07-22T07:14:21Z 2024-02-16T21:56:10Z "While the color of nav links is working, the hover color of those is not working.
{{{
""core/navigation"": {
""color"": {
""text"": ""var(--wp--preset--color--midred-2)""
},
""elements"": {
""link"": {
"":hover"": {
""color"": {
""text"": ""var(--wp--preset--color--lightred-3)""
}
}
}
}
}
}}}" titanchan
Needs Dev / Bug Wrangler Feedback 58874 Code Modernization: Consider using the null coalescing operator. costdev* General normal normal Future Release enhancement accepted dev-feedback 2023-07-22T05:41:48Z 2024-03-11T06:27:11Z "== Overview
There are currently around 500 instances of `isset( $var ) ? $var : 'default'` in Core.
In [https://make.wordpress.org/core/2020/03/20/updating-the-coding-standards-for-modern-php/ Updating the Coding Standards for modern PHP], the proposal states:
> The spaceship `<=>`, null coalesce `??` and null coalesce equals `??=` operators can not be used in WordPress Core until the minimum PHP version has been raised to PHP 7.0 (spaceship and null coalesce) or PHP 7.4 (null coalesce equals).
With [https://make.wordpress.org/core/2023/07/05/dropping-support-for-php-5/ the dropping of PHP 5 support in WordPress 6.3], we can now make use of the [https://www.php.net/manual/en/migration70.new-features.php#migration70.new-features.null-coalesce-op null coalescing operator].
> The null coalescing operator (`??`) has been added as syntactic sugar for the common case of needing to use a ternary in conjunction with `isset()`. It returns its first operand if it exists and is not `null`; otherwise it returns its second operand.
> [https://www.php.net/manual/en/migration70.new-features.php#migration70.new-features.null-coalesce-op PHP.net]
This allows changes from:
{{{#!php
prop ) ? $obj->prop : 'default';
}}}
to:
{{{#!php
prop ?? 'default';
}}}
== Proposal
This ticket proposes that we update these as the above instances often result in very long lines or very cumbersome conditions. This follows on from similar changes to use `str_starts_with()`, `str_ends_with()` and `str_contains()`, helps usher in the bump to a PHP 7 minimum for WordPress in a safe way compared to other PHP 7+ features, and promotes increased contribution as prospective contributors see WordPress not just enforcing a minimum PHP version or using new features in ''new'' code, but modernising its ''existing'' codebase.
As we're very early in 6.4-alpha, making this change now is as ""perfect"" as we could hope to be considering this will invalidate ''some'' patches. However, given the verbosity of `isset()` ternaries, these usually occur on their own line with very little extra code, so the number of invalidated patches should be ''relatively'' low.
== Considerations
1. Backporting: This may add extra work if backports involve changing lines containing the affected `isset()` ternaries. This applies to security backports as well as WordPress 6.3 minor releases. However, our earlier changes to `str_starts_with()`, `str_ends_with()` and `str_contains()` had a greater risk of creating extra work.
2. Invalidated patches: Patches that change lines containing the affected `isset()` ternaries will need a refresh. This ''is'' a negative, but it's also likely to be relatively straightforward to resolve for each patch. Our earlier changes to `str_starts_with()`, `str_ends_with()` and `str_contains()` risked invalidating many more patches compared to this proposal.
3. Readability: While objectively this is a benefit for brevity, readability is subjective.
4. [https://make.wordpress.org/core/handbook/contribute/code-refactoring/ Code refactoring should not be done just because we can]: This page details several things needed for proposals such as this:
- **Unit tests**, even if the code was not previously covered. We can’t afford regressions, and this will improve our test coverage.
- The behaviour of the null coalescing operator is the same as `isset( $var ) ? $var : 'default'`. This proposal does not suggest changing any other instances at this time.
- **Performance benchmarks**, before and after. We can’t afford regressions.
- The behaviour and performance of the null coalescing operator is the same as `isset( $var ) ? $var : 'default'`. This proposal does not suggest changing any other instances at this time.
- **Proper justification and clear rationale of changes are both necessary**. Too often it is impossible to determine the purpose, objective, or focus of these patches. Code should not be rewritten under the cloaks of readability, narrow personal opinion, or general subjectiveness.
- Much like the changes to `str_starts_with()`, `str_ends_with()` and `str_contains()`, this provides brevity in the codebase, and per-instance has a much greater reduction in code.
- It reduces our time reading and writing code - I appreciate there will be an adjustment period for some.
- It provides a clear signal to prospective contributors and to extenders that WordPress is moving forward, encouraging participation and observation for future changes." costdev
Needs Patch 58873 Add function to pass variables to scripts Script Loader 5.7 normal normal Awaiting Review feature request new 2023-07-22T03:36:51Z 2023-07-22T03:36:51Z "Since WordPress 5.7 using `wp_localize_scripts` to pass variables to registered scripts throws a `_doing_it_wrong` notice.
The suggested ""correct"" way of passing variables to scripts, using `wp_add_inline_script`, feels like a step backwards.
- Instead of just passing a variable name and value through a PHP function, that abstracts all of this away, we now have to write fully qualified JavaScript code in PHP strings.
- We have to actually parse/decode the values being passed on a case-by-case basis. `wp_localize_script` did this reliably.
- Using `wp_add_inline_script` is more verbose and prone to errors. Static analysis tools will not work on PHP strings.
- It makes for uglier code that is less human-readable.
On a personal note,
Converting to `wp_add_inline_script` feels a lot more like I'm ""doing it wrong"" than using `wp_localize_script`. It's simple, short and it works. (I do feel chagrined to see Query Monitor show up brown on every page load. But not enough to go and make my code uglier.)
I also doubt other ""in the wild"" developers will forego the use of `wp_localize_script` because of the `_doing_it_wrong` notice. The `wp_add_inline_script` alternative is simply not as robust.
Suggestion:
Add a function `wp_pass_variables_to_script` (or probably a shorter name) to re-introduce the robust functionality provided by `wp_localize_script`." apedog
Needs Patch 58872 wpautop not disabled when blocks are inserted dynamically Formatting 6.1.1 normal minor Awaiting Review defect (bug) new 2023-07-21T18:17:09Z 2023-07-21T18:17:09Z "**WP Version** Tested on 6.1.1, but seems to still be present on the trunk.
**Context**
Our theme has multiple page-header styles. Users can insert any one of those as the first block of a page, or leave it out. If it's left out, we inject a default header block as the first block of the page using a customer WP_Block_Parser.
We've also imported a large number of pages from a previous pre-Gutenberg WP system, so not all posts have block content.
**The Problem**
On legacy posts that do not have block content, wpautop is enabled, ''even for the injected header block'', resulting in extraneous and
tags. If there's even a single block in the post content, the block renders normally.
The source of the issue is that do_blocks (https://core.trac.wordpress.org/browser/trunk/src/wp-includes/blocks.php#L1166) renders the blocks based on the results of the parser, but disables `wpautop` based on a call to has_blocks(), which uses the unparsed content to determine if there are any blocks in the post.
I recognize this is an edge case, as we're dealing with both legacy content and an (ab?)use of a custom block parser to inject blocks into blockless content, so it's not likely to be a high priority. But if the ""block_parser_class"" hook is going to allow us to override the parser, do_blocks should respect the blocks that are returned regardless of the original content string, and override wpautop accordingly.
**Test Cases**
Attached are:
* A single.php page template file that succinctly captures the problem
* The contents of two pages. One has no blocks and shows the wpautop problem. The other contains a single block and shows wpautop being disabled correctly. Use the Code Editor to enter this content into a page or post." jbeninger
Has Patch / Needs Testing 58871 support uca14.0.0 collation in database where available Database 6.3 normal normal Awaiting Review enhancement new has-patch 2023-07-20T23:36:30Z 2023-09-25T00:17:50Z "Like #32105 supporting a modern collation is a good idea.
MariaDB added this in 10.10.1 (ref: https://jira.mariadb.org/browse/MDEV-27009).
As the current default is case insensitive, we'll follow the same insensitivity and use accent insensitive.
So of the collations available, use uca1400_ai_ci.
ref: https://mariadb.com/kb/en/supported-character-sets-and-collations/#collations" danielblack
Needs Patch 58862 Add filter to allow to change who can add new users with their username on multisite Users normal normal Awaiting Review enhancement new 2023-07-20T09:58:00Z 2023-07-20T10:23:43Z "On multisite, currently, only users with the `manage_network_users` capability can add new users with their usernames. Others need to know the email address of the user in said network.
Since WordPress Multisite is used a lot nowadays to create ""trusted"" networks where all users, for example, work for the same company, allowing users with lower capability sets to add users with their usernames would be helpful.
Let's say an agency has created the network for a big institution, and they usually don't grant a role that gives `manage_network_users` capability for many users, if any. For example, at work, we grant that only for their IT admins since they typically don't go and mess around with multisite settings that can break sites or the installation. For the people working in marketing, we might give administrator roles only on singular sites.
That's how WordCamp.org also works. There are only a handful of people who have roles with `manage_network_users` capability and WordCamp organisers do get administrator role on their event's website.
Both examples lead to situations where the multisite installation is ""trusted"", e.g. users most probably know each other or in the case of WordCamp.org, their usernames and profiles are public since WordPress.org uses WordPress.org user tables.
In these situations, it would be easier for the single site administrators to search users with autocomplete rather than trying to guess which email the user has used.
The default behaviour should still be checked against `manage_network_users` capability since not all multisite installations are ""trusted"", hence the filter.
Related issue in WordCamp.org repository: https://github.com/WordPress/wordcamp.org/issues/780" sippis
Has Patch / Needs Testing 58860 Potential security issue in is_super_admin Users normal normal Awaiting Review defect (bug) new has-patch 2023-07-20T09:44:15Z 2023-07-20T17:54:25Z "{{{
function is_super_admin( $user_id = false ) {
if ( ! $user_id ) {
$user = wp_get_current_user();
} else {
$user = get_userdata( $user_id );
}
...
}
}}}
If user is logged in as super admin and do `is_super_admin(0);` it will return true;
It would be best to use strict comparison:
{{{
function is_super_admin( $user_id = false ) {
if ( false === $user_id ) {
$user = wp_get_current_user();
} else {
$user = get_userdata( $user_id );
}
...
}
}}}" Stachethemes
Needs Patch 58859 On pattern edit page not able to open settings panel after close it General normal normal Awaiting Review defect (bug) new 2023-07-20T07:22:57Z 2023-07-20T07:22:57Z "I am trying to edit the pattern and found an issue with the setting panel.
Once I closed the settings panel not able to open it by clicking on the setting icon at the top right corner
Here I am adding a video
https://www.awesomescreenshot.com/video/19274744?key=3fab6b5bb4b249bf197c388f6b47d24e" mikinc860
Needs Patch 58857 Menu class should be in BODY tag Menus 6.2.2 normal normal Awaiting Review enhancement new 2023-07-20T03:57:48Z 2023-07-26T17:29:55Z "Currently, if you assign a class to a menu item, the class is only usable to the menu link alone. It would be 'very' beneficial to have the class in the BODY tag. If you want to keep them separate, you could preface the class with 'body-'.
So I have a menu link for 'Sponsors' and I assign the class 'g-sponsor' to the menu link.
Right now, it would show similar to this:
It would be great to have it added to the body class like this:
This the class can be use for 'any' element on the page instead of just the menu link.
FYI, I have a lot of experience in Joomla and they have had this functionality since the beginning. Now that I am migrating all Joomla websites to WordPress, I no longer have this functionality.
It should be a core function of the menu class.
Just a suggestion.
Luke Douglas
Webbering.com" LukeDouglas
Needs Dev / Bug Wrangler Feedback 58855 Fix and enhance wp_is_development_mode() to be able to return whether a development mode is beiung used General normal normal Future Release enhancement new dev-feedback 2023-07-19T22:10:58Z 2024-01-30T14:39:56Z "Follow up from: https://core.trac.wordpress.org/ticket/57487#comment:71.
The (new in 6.3) `wp_is_development_mode()` helper function cannot be used to check whether a development mode is enabled or not. It can only check for a particular development mode setting: either plugin, theme or core.
Being able to check whether a development mode is enabled or not will enhance the above function and improve consistency. Currently this can be achieved by using the returned value from `wp_get_development_mode()` as boolean." azaozz
Needs Patch 58854 Users should be able to reset their user preferences to default Users normal normal Awaiting Review feature request new 2023-07-19T17:41:45Z 2023-07-26T20:15:50Z "I work with many end users of the block editor and one thing that has come up frequently is sometimes their user preferences settings have created a view state of the editor that makes it difficult to find a certain feature and gets confusing when we are training them.
What I'm hoping for is an option to reset a user's preferences. This would reset all options under Preferences back to default, reset any other toggle they have (full screen, toolbar, etc.)
Ideally both a user and an admin would be able to access this function. Thanks for the consideration!
Related: https://wordpress.org/support/topic/reset-a-users-preferences-ie-block-editor-preferences/" bozzmedia
Needs Patch 58849 Document supported $args for register_rest_route() REST API normal normal Future Release enhancement new 2023-07-19T11:53:01Z 2023-07-19T17:00:04Z "`$args` seems awfully sparse for how important it is:
[[Image(https://github.com/WordPress/gutenberg/assets/36432/3d6f6ef2-3e15-4c0a-9bb9-9c3b4822c118)]]
It would be nice if all of the supported values were documented." danielbachhuber
Has Patch / Needs Testing 58844 Revisions: Compare Revisions layout issues on mobile Revisions 3.6 normal normal Future Release defect (bug) new has-patch 2023-07-18T20:45:48Z 2023-11-30T22:50:02Z "This is a follow-up to #33830.
""Restore This Revision"" button in wp-admin revision page can become hidden behind the diff panel in mobile view, particularly if the post author has a longer name.
The problem occurs when the author info (Name & Timestamp) stacks below the Avatar. " plari
Needs Patch 58843 Permissions issue with wordpress multisite Users 6.2.2 normal normal Awaiting Review defect (bug) new 2023-07-18T19:01:21Z 2023-07-18T19:01:21Z "I have a multisite wordpress installation that is current v 6.2.2
I have the main site and one additional site. Same issue on both sites, but I have been focused on the main site. I have created the new user in the main site and am sure the user has permissions to that site.
I have an issue where an editor level user cannot see any pages in the backend. It says there are 96 pages, 84 published, however none are visible.
If I create & publish a new page with that user account, that one page is visible.
If I change the author to a different user (editor level or other) it is no longer visible to the original editor account.
I have tried using the User Role Editor plugin and have even reset all roles to core defaults. The same issue remains.
It seems only a super admin level account is able to view all the pages no matter who created them.
" NF Graphic Design
Needs Patch 58842 "Add a ""change date/time notation"" / ""timezone"" checkbox when changing site languages" Administration normal normal Awaiting Review enhancement new 2023-07-18T17:08:17Z 2023-07-18T17:08:17Z "When I install WP, I usually do it in English. Yet, for some cases I have to change the locale to Dutch.
Now, I notice that the timezone and datetime notation stays in the old locale. Which is understandable... We don't want to force it on the user. That's why I'm suggesting that we add a checkbox or two so the user has the choice to also change the datetime/timezone setting to the locale default if they change.
It would make things a bit more flexible." NekoJonez
Needs Patch 58840 Add Canva as an oEmbed provider Embeds normal normal Future Release enhancement new 2023-07-18T15:06:41Z 2023-08-24T14:38:34Z "**Is the service is popular enough for core developers to have heard of it before? Is it “mainstream?”**
It is quite popular with over 100 million users according to Wikipedia.
**If similar services are already supported, how does this service compare in terms of size, features, and backing?
**
Not sure.
**Does this service have an established social media presence?**
Almost 300k followers on Twitter: https://twitter.com/canva
**Is its oEmbed endpoint clearly established and properly documented? (Sometimes, they are just a developer’s pet project that may not be supported.)**
Only found https://www.canva.com/embeds/ and https://www.canva.dev/blog/engineering/how-canva-makes-content-embeddable-and-why-you-should-too/ about this
**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?
**
oEmbed discovery does not work for Canva because the meta tag is very far down in the page source and WP only parses the first few KB of the response.
**Does the service make an effort to build relationships with developers, such as through robust APIs?**
Not sure. They do seem to have good dev docs and an engineering blog.
**How old is the service?**
Over 10 years old.
**Does it have a well-established Wikipedia article? (Seriously.)**
Yes. https://en.wikipedia.org/wiki/Canva
**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?**
Years ago they had their own official WordPress plugin but it has been abandoned: https://wordpress.org/plugins/canva/
**Is the provider frequently proposed?**
First time AFAIK." swissspidy
Needs Patch 58838 Author filter on a posts list page Posts, Post Types normal normal Awaiting Review feature request new 2023-07-18T10:57:32Z 2023-07-18T10:57:32Z "**Current Behaviour**
Under the user list, it shows only the published count but when visiting the list page from the user list then it shows all the published and drafts in the list and the count shows different.
**Expected Behaviour**
If the draft, pending, or any other types are available then it should have a proper count based on the selected author.
**Suggestion**
The Author filter allows administrators to filter and view posts created by specific authors quickly. This feature is handy when managing large amounts of content or coordinating with multiple authors, making it easier to locate and work with particular posts.
Redirecting from the user list page the default author should have to be preselected in the author filter." mikinc860
Has Patch / Needs Testing 58837 Horizontal Scroll Issue in theme/plugin Editor Page File Navigation Section General 6.3 normal minor Awaiting Review defect (bug) new has-patch 2023-07-18T09:45:04Z 2023-07-19T12:52:37Z "The bug pertains to the horizontal scroll behavior of the file navigation section on the theme/plugin editor page when the display width is below 780 pixels.
**Expected Behavior:**
The file navigation section should adapt its layout and display the necessary elements within the available width, without requiring horizontal scrolling.
**Current Behavior:**
When the display width falls below 780 pixels, the file navigation section in the theme/plugin editor page fails to adjust its layout properly. As a result, some elements within the file navigation section extend beyond the visible area, causing a horizontal scroll to appear.
**Steps to Reproduce:**
1. Open the theme/plugin editor page.
2. Reduce the width of the display to below 780 pixels.
3. Navigate to the file navigation section on the editor page.
Video Link: https://www.awesomescreenshot.com/video/19213200?key=de8384bcde8ae4bd0a80d87836612609
" mikinc860
Needs Reporter Feedback / Steps To Reproduce 58836 Remove IE specific checks from more default themes (6.4) Bundled Theme normal normal Future Release enhancement new reporter-feedback 2023-07-18T09:26:42Z 2023-09-12T20:24:03Z "Follow-up to #56699
Remove IE conditional statements and register external resources without enqueuing them for four more themes:
- Twenty Eleven
- Twenty Twelve
- Twenty Fourteen
- Twenty Sixteen" sabernhardt
Needs Patch 58828 Whenever bulk updates are done in wp-admin/update-core.php, no feedback is given, until all updates are done williampatton Upgrade/Install 6.2.2 normal normal Future Release defect (bug) assigned 2023-07-18T05:46:45Z 2024-03-13T04:31:21Z "This bug exists since I know WP, and it still persists on the latest version.
1. Go to wp-admin/update-core.php
2. Check all boxes for pending updates
3. Click update
- The page reloads.
- Nothing happens. The page just stays grey (admin bar etc are there, but the page itself is empty)
- After a while, which can be a very long while if a lot of updates are pending, the screen gets populated (without page reload) with log like
{{{#!php
The update process is starting. This process may take a while on some hosts, so please be patient.
Enabling Maintenance mode…
Updating Plugin {Plugin name} (1/12)
{Plugin name} updated successfully. Show details.
Updating Plugin {Plugin name}
[etc]
All updates have been completed.
Go to Plugins page | Go to WordPress Updates page
}}}
This log clearly should happen _while_ it is updating, and not once it is done.
There is no spinner, no feedback, nothing that tells the user ""something is working""
" bedas
Needs Patch 58826 Please add a default post relations table Database normal critical Awaiting Review enhancement new 2023-07-17T22:10:52Z 2023-07-17T22:10:52Z "As I am sure you know, people have bee using wordpress for a lot of things other than a simple blogging platform. And while your structure allows for basic functionality and relationships, There is a lot of room for improvement. As people continue to add more and more custom post types and related meta, the default posts/post meta tables will quickly become filled and make web queries slow.
In addition, the taxonomy system is very limiting, as that is not the only way one would want to group like items. The most common way, would be POST relationships. If a Class has many students, and students have many classes, Displaying an intermediary page between the two is very difficult with the current set up. Therefore, I'd like to request an extension to the database structure as described below in the link below. At minimum the 1st option should be considered as an alternative to archive pages with taxonomies.
[https://imgur.com/a/L9q4bAf]
If I type domain.exp/articles/for/baseball where baseball is a sports custom post type and arcticles is just one of several custom post types, I expect a query select * from articles where hobby_slug = 'baseball'
Currently everyone expects me to make the sport CPT a taxonomy, but if the sport has its own custom fields, and taxonomies already attached, that does not work. This system would be usable in a thousand different use cases and would make your platform more versatile. USERS, comments, posts and custom post types are all Models. Make it easier to establish any relation between them please.
" jcc5018
Has Patch / Needs Testing 58824 Add a filter to change the classes in posts list table in admin General normal normal Awaiting Review enhancement new has-patch 2023-07-17T19:26:57Z 2023-07-21T18:04:39Z "Currently, there is no way to change the classes in the posts list table, and the posts list table template is hardcoded. So there is no way to add any classes, for example, specific classes for custom post types there.
**Proposal:**
Add a filter to ""WP_List_Table::get_table_classes()"" function, like this:
{{{#!php
_args['plural'] ), $this );
}}}
" zahardoc
Needs Patch 58822 Gutenberg - releases must work with the latest react version General 6.3 normal blocker Awaiting Review defect (bug) new 2023-07-17T17:43:40Z 2023-07-17T17:59:23Z "Gutenberg is falling behind more and more, bundling outdated/unmaintained packages, preventing the use of the latest react.
e.g. https://www.npmjs.com/package/@wordpress/block-editor bundles
>""react-autosize-textarea"": ""^7.1.0"",
Which requires react 16 (!!).
There are far more examples than that, that all shipped with WP 6.2.
Github issues for dependencies mostly go unhandled too, because there are 200 packages now + the @types ones (which are also inconsistent, since some have types bundled while others haven't)
The way gutenberg is maintained, organized and managed needs some major discussion and overhaul by someone who has enough credentials in the WP community to provide a clear plan ahead with Gutenberg." malthert
Needs Patch 58819 Critical error on this website Site Health 6.2.2 normal normal Awaiting Review defect (bug) new 2023-07-17T08:48:21Z 2023-07-18T08:28:00Z "Hi,
recently we (and our clients) are receiving more and more ""critical error"" messages.
Looking at the message in detail we see, that the message (and the whole error detection) refers to an outdated PHP version (e.g. 7.0). Yet the monitored WP implementation works with PHP version 8.0
Question: why does the routine use an outdated and unused PHP version for the monitoring?
It would be fine if the error detection routine would use the same PHP version for its monitoring as the website uses.
Or if these particular messages could be stopped, as they are not only useless but confusing. " ewerkstatt
Needs Patch 58817 Edit page in wordpress default editor cousing overload on 3 diffrent servers. General normal normal Awaiting Review defect (bug) new 2023-07-17T06:00:35Z 2023-07-17T06:00:35Z "Hello guys, how are you?
I think i found something very wired and i not so sure issue connected to the core, but it is worth a try.
I have 3 different machines on Google cloud, dedicated machine for 1 WordPress site. (e2-micro machine)
All my 3 websites identical with the same design, theme, plugins and code.
The only different between them is the language of WordPress.
The problem is, i am experience overload on all the machines when editing a page in the default WordPress editor.
Even if i only get in the default editor and only refresh the editor (F5), i get overload on my machine.
**I notice jumps of 150mb – 200mb when i refreshing the page.**
What causing kswapd0 to be triggered on my server and this is look like this:
https://ibb.co/fNdYrxn
In the start all the 3 VMs was experience the same overload.
I was suspect on the post revision + autosave and wp-cron.
**So, i limit the time of wp-cron and turn off the post revision completely + autosave for 1 day in wp-config:**
define( 'AUTOSAVE_INTERVAL', 86400 );
define( 'WP_POST_REVISIONS', false );
define( 'WP_CRON_LOCK_TIMEOUT', 60 );
This helps a lot for all the 3 websites in general.
But still i was getting overload on 2 different machines.
Only in my English, WordPress not experience overload anymore. (this way i think isiue is with the language of WordPress as well)
My other 2 WordPress websites in different language experience overload after 24 any time i am editing a page… (the other WordPress is in Catalan and Spanish)
**So for the final conclusion:**
1. I suspect in Autosave, because issue happens after 24 hours (i change the wp-config).
2. I think it is a language issue too. (websites identical as i said before)
3. In the English WordPress, we not experience the overload (we're still seeing 150 – 200mb when refreshing the page, but don't have overload).
4. Why when i refresh the default page editor it consumes 150mb – 200mb?
Be happy for your help guys.
" 123nadav
Needs Patch 58816 MariaDB 11.x: deprecated alias for MySQL Build/Test Tools normal normal Awaiting Review defect (bug) reopened 2023-07-17T05:10:50Z 2024-01-25T04:35:12Z "Since MariaDB 11.0, there is a “deprecated warning message”:
{{{
PHPUnitFrameworkException: mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead
mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead
}}}
One random test where you can find it:
https://make.wordpress.org/hosting/test-results/r56244/wpsaedgebot-r56244/" JavierCasares
Needs Patch 58815 Opinionated styles (add_theme_support(wp-block-styles)) set margin top to 0 for image and other blocks Editor 6.3 normal normal Awaiting Review defect (bug) new 2023-07-16T23:53:36Z 2023-08-23T07:36:52Z "Is `add_theme_support('wp-block-styles')` being deprecated in WP 6.3? If not, maybe it needs to be updated.
The extra block styles include margin settings, for example
{{{
.wp-block-image {
margin: 0 0 1em;
}
}}}
This is done for image, audio, embed, table or video blocks.
The top margin styling is overridden in WP 6.2 by styles with targeting such as
{{{
body .is-layout-flow > * + * {
margin-block-start: var(–wp–preset–spacing–normal);
}
}}}
so the blocks get the `margin-top` which they require as per the page layout.
However, WP 6.3 changes the targeting of these styles to, for example
{{{
:where(body .is-layout-flow) > * {
margin-block-start: var(–wp–preset–spacing–normal);
}
}}}
This is less specific, with the result that the `wp-block-styles` margin setting overrides it and will set the margin-tops to 0 for the above blocks.
This will affect existing content on many sites which use this `add_theme_support` and these blocks.
Twenty twenty-two theme is an example.
To test, create a page with a paragraph followed by an image, in twenty twenty-two theme." aileenf
Has Patch / Needs Testing 58813 Editing Slug to an Existing Slug causes wrong content to display Editor normal normal Awaiting Review defect (bug) new has-patch 2023-07-14T19:14:37Z 2023-07-19T18:52:15Z "**NOTE** This only works if you have the Classic Editor plugin active.
I made a ticket there - https://github.com/WordPress/classic-editor/issues/201 - but they said it's a core bug.
I am aware this is a weird one.
The setup is as follows:
1. Make a clean website
2. Make a couple posts (content does not matter)
3. Install and Activate Classic Editor
4. Make a new post and save as draft
5. Copy the permalink from an existing post and paste it into the new post as the permalink, save as DRAFT (do not publish)
6. You will see the NEW post has a -2 added to the permalink (this is as expected)
7. Open the ORIGINAL existing post with the non -2
8. The post will display the content (title and all!) from the NEW post that is still in draft (this is NOT expected)
This **does not** happen with the Block Editor, it can only be reproduced in Classic Editor, however the CE side feels this is a bug in core.
I dug up that this is fixed in Gutenberg per #52422 however it still exists in classic editor.
I can confirm that this happens from WP 4.9.x through 6.0.x '''without''' Classic Editor.
As of 6.1.3, this is fixed in Block Editor, and only appears if you have the Classic Editor active." Ipstenu
Needs Dev / Bug Wrangler Feedback 58808 Proposal: track object cache type in update checks Upgrade/Install normal normal Awaiting Review enhancement new dev-feedback 2023-07-14T10:54:07Z 2023-07-14T16:49:23Z "Related: #56751, #48116
I think it would be helpful to send the `wp_using_ext_object_cache()` value as part of the update requests.
We already send the list of installed PHP extensions, so it's possible to know whether e.g. redis or memcached are installed, but not if they are actually used.
Ideally we would also know the exact type of object cache that is being used (e.g. if it's actually redis or memcached or something else). That would be also very useful for the `wp cache type` command, [https://github.com/wp-cli/cache-command/issues/68#issuecomment-1433755427 as suggested here].
This could be done via `WP_Object_Cache::get_type()` and a `wp_cache_type()` function for example." swissspidy
Needs Patch 58806 Unexpected ordering result when ordering based on multiple clauses Query 6.2.2 normal normal Awaiting Review defect (bug) new 2023-07-14T08:17:52Z 2023-07-14T08:17:52Z "I am not sure if this is a bug or this is a mis-understanding from my side on how the ordering works but
Consider the following `WP_Query`:
{{{#!php
'ids',
'post_type' => 'post',
'post_status' => 'publish',
'posts_per_page' => -1,
'meta_query' => [
'relation' => 'OR',
'sticky_clause' => [
'key' => '_sticky',
'type' => 'UNSIGNED',
],
[
'key' => '_sticky',
'compare' => 'NOT EXISTS',
],
],
'orderby' => [
'sticky_clause' => 'desc',
'title' => 'asc',
],
]
);
}}}
The expected behavior is that the query should show posts that have a `_sticky` meta first, then shows the rest of the posts sorted by their title alphabetically.
However it doesn't happen.
{{{
array(7) {
[0]=>
string(20) ""A guide to WordPress""
[1]=>
string(27) ""Brotherhood of creativeness""
[2]=>
string(30) ""Gather all information you can""
[3]=>
string(16) ""Yet another post""
[4]=>
string(12) ""Hello world!""
[5]=>
string(36) ""Opera browser released a new version""
[6]=>
string(27) ""Zebras are cool and relaxed""
}
}}}
In the above output of post titles, the `""Hello World!""` has `_sticky` meta, but the sorting isn't correct (nor alphabetically and nor by `_sticky` meta first)
This is the SQL query generated by this query:
{{{#!php
SELECT
wp_posts.ID
FROM
wp_posts
LEFT JOIN wp_postmeta ON (
wp_posts.ID = wp_postmeta.post_id
)
LEFT JOIN wp_postmeta AS mt1 ON (
wp_posts.ID = mt1.post_id
AND mt1.meta_key = '_sticky'
)
WHERE
1 = 1
AND (
wp_postmeta.meta_key = '_sticky'
OR mt1.post_id IS NULL
)
AND wp_posts.post_type = 'post'
AND (
(wp_posts.post_status = 'publish')
)
GROUP BY
wp_posts.ID
ORDER BY
CAST(
wp_postmeta.meta_value AS UNSIGNED
) DESC,
wp_posts.post_title ASC
}}}
If I am not wrong the issue happens at the position `ORDER BY CAST(wp_postmeta.meta_value AS UNSIGNED) DESC`, it should use the alias instead of the table name here (should be `mt1.meta_value`)" pelentak
Needs Patch 58803 Infinite loop in canonical.php Canonical 6.2 normal minor Awaiting Review defect (bug) new 2023-07-13T17:49:02Z 2023-08-30T17:44:26Z "A site 24x7 monitor that points to a URL on our website leads to an error with infinite loops reported.
This error started after the page being pointed by the monitor received a new Slug, leading to HTTP redirection due to autocomplete to the closest URL. Still, I believe it occurs only during periods of transient availability of our shared host.
Looking at the source code [REF2] I believe there is potential for an infinite loop on line 800. Possible fix in [REF3].
By assigning the result of redirect_canonical() to a variable ($chained_redirect) before the if statement, we ensure that the same value is used throughout the if block preventing unnecessary recursive calls.
References
----------
[REF1]
HTTP/1.1 508 Loop Detected
Server : nginx
...
[REF2]
https://github.com/WordPress/wordpress-develop/blob/6.2/src/wp-includes/canonical.php#L780-812
[REF3]
// Protect against chained redirects.
$chained_redirect = redirect_canonical($redirect_url, false);
if (!$chained_redirect) " emerlen
Needs Dev / Bug Wrangler Feedback 58801 Prefetch Block Editor from Posts page adamsilverstein Editor normal normal Future Release enhancement assigned needs-unit-tests 2023-07-13T15:44:37Z 2023-12-04T22:00:53Z "One of the most common user journeys in wp-admin for creating or editing a Post is navigating to the Posts page (`wp-admin/edit.php`) then to the Block Editor (either by clicking a post to edit or clicking the ""New Post"" button or sidebar menu).
We can greatly increase up the speed with which the editor loads by prefetching the edit screen once the user reaches the Posts page. Prefetch will ""prime the html cache"" for all of the resources needed by the editor, resulting in the editor loading much faster for users.
Note: since users can also reach the editor from the wp-admin bar, we might want to consider adding prefetch when the user interacts or opens the ""New"" menu. However, to keep this initial proposal small and easier to test I decided to limit the scope to the Posts page." adamsilverstein
Has Patch / Needs Testing 58799 Need to add filter to register a template in [NEW] WordPress site editor through a plugin Editor 6.2.2 normal blocker Awaiting Review enhancement new has-patch 2023-07-13T11:55:00Z 2024-03-01T10:09:22Z "I am trying to add a new template in the WordPress site editor like this like this
but unable to do it with my custom plugin.
I have found a filter to register a custom template
{{{
add_filter( 'default_template_types', 'register_template_type' );
function register_template_type( $templates ) {
$templates['help-us'] = array(
'title' => _x( 'Page: Help Us', 'Template Name' ),
'description' => __( 'Displays Help Us template' ),
);
return $templates;
}
}}}
after adding this code I have figured out that by adding a file in the theme's template directory help-us.html I was able to register and display my custom template.
**What if I want to add a custom template via plugin?**
I was not able to find a way to add a custom template via the plugin. Previously I was using customizer in my plugin to customize the layout of a page with some custom functionality, now I am looking for a way to customize this page with the help of NEW site editor.
**REF**: https://wordpress.stackexchange.com/questions/417325/how-to-register-a-template-in-new-wordpress-site-editor-through-a-plugin
After going through, I figured out that we just need to make the template html file visible from the plugin to the template loop in order to display it. So I went over and added filter hooks in two places which just worked for me.
We need to add filters in following two lines;
1- wp-includes\block-template-utils.php:263
{{{
$themes = array(
get_stylesheet() => get_stylesheet_directory(),
get_template() => get_template_directory(),
);
// NEW Filter hook
$themes = apply_filters( 'block_editor_templates_files', $themes, $template_type );
$template_files = array();
}}}
2- wp-includes\block-template-utils.php:306
{{{
$themes = array(
get_stylesheet() => get_stylesheet_directory(),
get_template() => get_template_directory(),
);
// NEW Filter hook
$themes = apply_filters( 'block_editor_templates_files', $themes );
}}}
Looking forward to your feedback and consideration.
Thanks
" saadiqbal
Needs Patch 58798 Fix possible PHP warning in /wp-includes/feed.php Feeds 6.2.2 normal normal Awaiting Review defect (bug) new 2023-07-13T10:12:27Z 2023-11-27T12:36:13Z "If some plugins or themes use ""enclosure"" meta field as a one-line string, it results in PHP warnings:
PHP Warning: Undefined array key 2 in /wp-includes/feed.php on line 484
PHP Warning: Undefined array key 1 in /wp-includes/feed.php on line 494
It happens because there is no check of string content there:
{{{
foreach ( (array) get_post_custom() as $key => $val ) {
if ( 'enclosure' === $key && is_array( $val ) ) {
foreach ( (array) $val as $enc ) {
$enclosure = explode( ""\n"", $enc );
/ Only get the first element, e.g. 'audio/mpeg' from 'audio/mpeg mpga mp2 mp3'.
$t = preg_split( '/[ \t]/', trim( $enclosure[2] ) );
$type = $t[0];
/**
* Filters the RSS enclosure HTML link tag for the current post.
*
* @since 2.2.0
*
* @param string $html_link_tag The HTML link tag with a URI and other attributes.
*/
echo apply_filters( 'rss_enclosure', '' . ""\n"" );
}
}
}
}}}
**Proposal:**
Add checks if the enclosure is an array, and each item can be exploded into exactly 3 items:
{{{
if ( 'enclosure' === $key && is_array( $val ) ) {}
}}}
And this:
{{{
$enclosure = explode( ""\n"", $enc );
if ( 3 !== count( $enclosure ) ) {
continue;
}
}}}
" zahardoc
Needs Patch 58795 Multisite Network Admin Sites - Search doesn't work well Networks and Sites normal normal Awaiting Review defect (bug) new 2023-07-12T20:36:32Z 2023-07-24T19:45:39Z The built-in Search functionality in the Multisite Network Admin area has not been working well. Whenever I update a Site Name on a Subsite to be the unique Subdomain, the Search box does not seem to index or cache the new Site Name (even after I clear the cache on the network). So the only way to find sites on my multisite network is to browse through hundreds of site domains until I find the one I am looking for. If I know the Site ID, I can input it into the Search box and the site comes right up. For some reason, text from the subdomain in the Site Name field do not seem to get searched through. paulpleasant
Needs Patch 58794 Edit Image UX needs improvement Media 6.3 normal major Awaiting Review defect (bug) new 2023-07-12T12:25:30Z 2023-07-15T20:38:10Z "== Bug Report
=== Description
When **editing**(scale and crop) an image via ""**Attachment details**"". The **settings** for the selected feature are shown at the **end of the popup**. This would be fine in the case of smaller images. But for **larger images**, especially ones in the **portrait orientation**, these settings are not visible on the screen unless one scrolls down. There seems to be room for UX improvement here.
I think we can keep the settings on the **right-hand side** of the popup, which would remove the need to scroll down to use them, no matter what the image size is.
Also, I felt this must have been done as such since not all features need a settings section. But can't that be handled by maybe toggling the section altogether? ( if placed on the right that is )
Attaching videos for reference. The video names describe the test cases.
=== Environment
- WordPress: 6.3-beta4
- PHP: 7.4.12
- Server: Apache/2.4.46 (Unix) OpenSSL/1.0.2u PHP/7.4.12 mod_wsgi/3.5 Python/2.7.13 mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_perl/2.0.11 Perl/v5.30.1
- Database: mysqli (Server: 5.7.32 / Client: mysqlnd 7.4.12)
- Browser: Chrome 114.0.0.0 (macOS)
- Theme: Twenty Twenty-Three 1.1
- MU-Plugins: None activated
- Plugins:
* WordPress Beta Tester 3.5.1
=== Steps to Reproduce
1. Navigate to Media Library
2. Select a large Image to edit(preferably Portrait orientation)
3. Edit Image
4. Click on the ""Scale"" button
5. Nothing happens
6. Settings are shown at the end of the popup which can only be seen if scrolled.
=== Expected Results
1. On clicking the ""Scale"" button, the settings to edit the scale should be visible to the user.
=== Actual Results
1. Right now ""Scale & Crop"" settings are only visible if scrolled down(for bigger images)." deepakvijayan
Needs Patch 58789 Not countable. row_actions @ /wp-admin/includes/class-wp-list-table.php Administration 6.2 normal major Awaiting Review defect (bug) new 2023-07-12T05:11:05Z 2023-10-30T19:43:58Z "Commonly getting not countable for the users lists, across many sites not sure of the source of the issue, but easy solution seems to be to modify.
`/wp-admin/includes/class-wp-list-table.php`
{{{
protected function row_actions( $actions, $always_visible = false )
++ if(!isset($actions)) { return ''; }
$action_count = count( $actions );
if ( ! $action_count ) {
return '';
}
}}}" Nate1
Needs Patch 58787 when upload it multi upload duplicate the files in the media Upload 6.2.2 normal normal Awaiting Review defect (bug) new 2023-07-11T21:56:53Z 2023-10-30T19:36:30Z "{{{
$attachment_id->get_error_message());
} else {
// The file was uploaded successfully
$response = array('success' => 'File uploaded successfully with attachment ID ' . $attachment_id);
}
} else {
// No file was selected
$response = array('error' => 'No file selected.');
}
// Send the response back to the client-side script
echo json_encode($response);
}
// IMPORTANT: Don't forget to exit at the end of your callback function
exit;
}
?>
}}}" wasimo
Needs Patch 58786 Support for adding custom, post-level meta descriptions in WP core. Editor normal normal Awaiting Review feature request new 2023-07-11T21:22:29Z 2023-10-30T13:25:23Z "Hi, the WordPress page/post editor needs a field for a custom written meta description.
Meta descriptions are ubiquitous, been around forever, supported by all other (major) CMSs out there, an accessibility feature.
Users should not need to install third party software for something this basic.
Thanks." xroox
Needs Dev / Bug Wrangler Feedback 58781 Change wording of field description for tagline Administration normal normal Future Release enhancement new dev-feedback 2023-07-11T06:26:54Z 2024-01-19T06:33:34Z "This is a follow-up to #57675
I [https://core.trac.wordpress.org/ticket/57675#comment:28 raised my concerns there], but it was too late in the cycle. So here we go:
These are my concerns about the solution we use now:
1) The example is misleading, the tagline should be meaningful, and just not like in the example
Using a unique and descriptive tagline is important for search engine optimization (SEO) purposes, as it helps convey the website's purpose and relevance to both search engines and visitors.
2) The “ and ” could be misunderstood so people would enter quotation marks into the tagline.
This can impact the visual presentation and readability of the tagline to visitors.
To keep the iconic phrase ""Just another WordPress site"" while being informative at the same time we could formulate:
In a few words, explain what this site is about. We're sure your site is so much more than ""Just another WordPress site""" Presskopp
Needs Patch 58774 Sorting Posts after Published Date OR Last Update should be a standard function Date/Time 6.2.2 normal normal Awaiting Review feature request new 2023-07-10T20:19:01Z 2023-07-10T20:19:01Z "I am quite surprised that it is not a standard WP function to let the users of my website choose whether to sort Posts after Published Date OR Last Update Date!
I have not even been able to find a plugin that adds this function. " hero2
Needs Patch 58773 Improve oEmbed lazy loading adamsilverstein Embeds normal normal Future Release defect (bug) assigned 2023-07-10T20:09:21Z 2023-12-20T16:47:44Z "== Why lazy load oEmbed iframes?
* Lazy loading prevents wasted resources from loading if the user never scrolls down to view the oEmbed
* Iframe lazy loading is handled directly by the browser, making the change simple (add a single attriute) and ensuring users get a great experience
== Lazy loaded oEmbeds history
WordPress has [https://make.wordpress.org/core/2021/02/19/lazy-loading-iframes-in-5-7/ lazy loaded iframes] since version 5.7 and the original proposal included lazy loading for oEmbed iframes (as long as the provider also included width and height attributes).
Ultimately, dynamic addition of lazy loading of oEmbeds was removed from core because it was found to create issues, especially with embeds of other WordPress posts.
== Proposed Solution
This ticket proposes slightly different approach that relies on altering the iframe instance on the fly for each oEmbed. In particular:
* When the oEmbed iframe HTML is displayed, if it doesn't already contain a `loading` attribute, it is run through `wp_iframe_tag_add_loading_attr` to add the lazy loading iframe under the correct conditions
* Will not add lazy loading to WordPress iframes because of the `data-secret` check
* Only adds lazy loading to iframes with the height and width present.
* Runs before the `oembed_result` filter, so developers can remove the attribute if desired.
" adamsilverstein
Needs Patch 58771 Someone logged onto my WordPress Admin Site, changed the password, and created a User Registration Security normal normal Awaiting Review defect (bug) new 2023-07-10T16:16:34Z 2023-07-10T16:16:34Z "I checked settings and the ""Anyone can register"" is unchecked.
I was able to regenerate a password and delete the user registration.
I received several emails over the weekend regarding this activity. My password was 15 characters long, so I am not sure how anyone could have figured out my password. I am concerned and wanted to let someone know of this security vulnerability.
EMAIL 1: 7/8/2023 07:18 AM
Howdy! Some plugins have automatically updated to their latest versions on your site at https://www.privotechnologies.com. No further action is needed on your part.
These plugins are now up to date:
- Protect Uploads (from version 0.3 to 0.4)
If you experience any issues or need support, the volunteers in the WordPress.org support forums may be able to help.
https://wordpress.org/support/forums/
The WordPress Team
EMAIL 2: 07/10/2023 12:20 AM
New user registration on your site Privo Technologies, Inc.:
Username: wadminw
Email: wadminw@wordpress.com
EMAIL 3: 07/10/2023 12/21 AM
New user registration on your site Privo Technologies, Inc.:
Username: wadminw
Email: wadminw@wordpress.com
EMAIL 4: 07/10/2023 5:46 AM
Hi privomain,
This notice confirms that your password was changed on Privo Technologies, Inc..
If you did not change your password, please contact the Site Administrator at pgoldberg@privotechnologies.com
This email has been sent to peter.goldberg@comcast.net
Regards,
All at Privo Technologies, Inc.
https://www.privotechnologies.com
EMAIL 5: 07/10/2023 5:47 AM
New user registration on your site Privo Technologies, Inc.:
Username: admmega123
Email: admmega123@outlook.com
" peterg1206
Has Patch / Needs Testing 58765 the_block_template_skip_link() - XSS vulnerability - Apply FIX Security 5.8 normal normal Awaiting Review enhancement new has-patch 2023-07-08T12:07:38Z 2023-07-08T15:25:45Z "Dear people at WordPress,
I have already reported this problem on HackerOne, it has been reviewed by a member of the WordPress security team, and they asked me to publish the issue here.
Issue:
I would like to implement on my website the CSP (Content Security Policy): require-trusted-types-for ‘script’;
If I do it, I get the following error message in the browser Console:
“This document requires TrustedHTML assignment”
because “innerHTML” is used in this script: `the_block_template_skip_link()`
Impact
DOM XSS
FIX: in the script, replace ""innerHTML"" with ""innerText"" and the skiplink will still work.
I have done that on my own homepage:
`remove_action( 'wp_footer', 'the_block_template_skip_link' );`
and then I have added the skiplink again, replacing ""innerHTML"" with ""innerText"" in the script.
The code works (used theme: Twenty Twenty-Three)." micromadness
Needs Dev / Bug Wrangler Feedback 58764 Incorrect return type in `WP_Rewrite::using_index_permalinks()`. costdev Permalinks 2.7 normal normal Awaiting Review defect (bug) assigned dev-feedback 2023-07-08T10:08:29Z 2023-07-31T12:58:33Z "== Overview
In [8899], [https://github.com/WordPress/wordpress-develop/blob/6.2/src/wp-includes/class-wp-rewrite.php#L357-L373 WP_Rewrite::using_index_permalinks()] was documented to return `bool`. However, its actual return type is `int|false`.
A guard explicitly returns `false`, however the final return statement returns the result of a `preg_match()` call.
Per [https://www.php.net/manual/en/function.preg-match.php the PHP manual]:
> `preg_match()` returns 1 if the pattern matches given subject, 0 if it does not, or false on failure.
== Docs change, or `bool` cast?
=== Docs change
We could change the return type to:
{{{#!php
@return int|false 1 if permalink links are enabled and index.php is in the URL,
0 if permalinks are enabled but there was a failure,
false if permalinks are disabled.
}}}
However, I think this is an overly complicated return for a method called `using_index_permalinks()` that suggests, and is currently documented as, a simple `bool` return type.
=== `bool` cast: Is there a backward compatibility concern?
Yes, but a very small one.
WP Directory shows:
- [https://wpdirectory.net/search/01H4T8ZA3EYAHNCJH57EKTSYH2 all 135 plugins] and [https://wpdirectory.net/search/01H4TEEJ598PDEK1WCRJ4C3SGW all 138 themes] that call this method use a loose check on the result, treating `0` and `false` as ""No, it does not use index permalinks"". These are safe from a `(bool)` cast.
- It's possible that someone out there is using `1 === $wp_rewrite->using_index_permalinks()`, but as the method is documented to return `bool`, they're most likely using a loose check after an assumed attempt of `true ===` would have always failed, as the method currently ''never'' returns `true`.
=== When does `preg_match()` return `false`?
Per PHP-src, a call to [https://github.com/php/php-src/blob/c6b9db2131deda7ca0683a6006fe9ae8dd767f51/ext/pcre/php_pcre.c#L1465 preg_match] eventually leads to [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L589C26-L589C58 pcre_get_compiled_regex_cache_ex].
The following failure conditions are listed:
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L642 Empty regular expression]
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L654 Delimiter must not be alphanumeric, backslash, or NUL]
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L698 No ending delimiter '%c' found]
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L700 No ending matching delimiter '%c' found]
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L750 Unknown modifier '%c']
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L752 NUL is not a valid modifier]
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L764 The /e modifier is no longer supported, use preg_replace_callback instead]
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L779 Failed to generate locale character tables]
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L801 Compilation failed: %s at offset %zu]
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L852 Internal pcre2_pattern_info() error %d]
- [https://github.com/php/php-src/blob/master/ext/pcre/php_pcre.c#L862 Internal pcre_pattern_info() error %d]
=== Which of these failures could happen here?
In the context of `WP_Rewrite::using_index_permalinks()`, there is only one possible failure: `WP_Rewrite::$index` contains the delimiter, `#`. [https://3v4l.org/M94EH 3v4l].
The `index` property is set to `'index.php'` by default. However, it's a `public` property and could therefore be directly overridden, or set in a subclass of `WP_Rewrite`.
WP Directory shows:
- [https://wpdirectory.net/search/01H4TBP4HXJZQ8G58BGB6A0QFE 0 plugins] directly assign a value to this property.
- [https://wpdirectory.net/search/01H4TBT9RAKWGY41CCPD320RBA 0 themes] directly assign a value to this property.
- [https://wpdirectory.net/search/01H4TBW9JQNVX9Q580Z0FPD6DH 1 plugin] extends the `WP_Rewrite` class, but does not set a value for the property.
- [https://wpdirectory.net/search/01H4TC0P3CYKZ27FK2KBGJQSP5 0 themes] extend the `WP_Rewrite` class.
=== Can we prevent the potential failure?
Yes, by using `preg_quote( $this->index, '#' )`. [https://3v4l.org/CYsS7 3v4l].
=== ''Should'' we prevent the potential failure?
As demonstrated by the failure, the regex is currently susceptible to special characters. When the default value of `$this->index` (`'index.php'`) is concatenated, the resulting pattern is `'#^/*index.php#'`.
See the `.`? The `preg_match()` call is currently vulnerable to `index[any character except newline]php`. [https://3v4l.org/LQSOG 3v4l].
Given this, it's possible that a developer out there has set a custom `$index` value that contains a regex pattern. However, I think that's very unlikely.
Contrarily, the flawed regex has the potential to cause false positives if, for example, the permalink structure starts with `/index2php`. While that's also unlikely, using `preg_quote()` here would prevent that false positive.
-----
== Call for opinions
1. Should we just change the documented return type and description? If so, what makes sense here?
2. OR should we cast the result to `bool`?
3. ADDITIONALLY should we use `preg_quote()` here to prevent the potential failure?" costdev
Needs Early Attention 58763 Inconsistent add/get/update/delete_post_meta() functions leads to deleting post metadata. General normal major 6.6 defect (bug) new has-patch 2023-07-08T09:48:05Z 2024-02-19T20:57:08Z "The add_post_meta(), delete_post_meta(), and update_post_meta() functions all use wp_is_post_revision() to add/delete/update the metadata of the post, not its revision. That's fine, but the get_post_meta() function does NOT use wp_is_post_revision().
As a consequence, if you use get_post_meta() and update_post_meta() during the saving process for a revision, the post metadata ends up being overwritten/deleted: The get_post_meta() function gets the **revision** metadata, and then the update_post_meta() function updates the **post** metadata, NOT the revision metadata.
js." jsmoriss
Needs Patch 58761 Make the filter option_page_capability_options available when access options.php directly Options, Meta APIs normal normal Awaiting Review defect (bug) new 2023-07-08T05:43:13Z 2023-07-08T05:43:13Z "The problem is that when wp-admin/options.php is accessed directly $option_page is Empty, and the filter for option_page_capability_options is bypassed.
For a requirement to prevent direct access to this page, which exposes all WordPress options, this filter is needed to modify the capability from 'manage_options' to 'do_not_allow'.
For any other settings page the value of $option_page is set to something other than 'options' and would not be affected by this change.
I'd also suggest the 'back compat' comment is irrelevant and could be removed (or at least better explained if it is relevant).
The suggested change is from:
{{{#!php
Permalinks.
4. Scroll down to the Optional section." sabernhardt
Needs Patch 58720 Page-Specific template in Site Editor detaches itself from the page when page slug is updated. Editor normal normal Awaiting Review defect (bug) new 2023-07-05T19:15:26Z 2023-10-31T03:16:11Z "If the page slug is updated, the Page-Specific template that was created within the Appearance > Editor section will detach itself from the page.\\
\\
**Steps to Reproduce**\\
1. Create a new page.\\
2. Create a new page-specific template within Appearance > Editor specifically for the page you created.\\
3. Change the slug (URL) of the newly created page.\\
4. Upon changing the slug, you will notice that the page-specific template becomes detached from the page, meaning it is no longer associated with it." talhaqureshi
Has Patch / Needs Testing 58719 Bump the minimum PHP version to 7.2 johnbillion* General normal normal 6.6 enhancement accepted has-patch 2023-07-05T17:59:52Z 2024-03-11T04:40:57Z "Background: #51043, #57345
Per discussion in #51043 (and reaffirmed in #57345, specifically https://core.trac.wordpress.org/ticket/57345#comment:29 and https://core.trac.wordpress.org/ticket/57345#comment:83 ), for WordPress to consider dropping support for a PHP version, the versions need to get below 5% usage, regardless of the WordPress version used on those sites.
As of 5 July 2023, [PHP usage for all WordPress sites](https://wordpress.org/about/stats/)
- PHP 5.6 is at 3.93%
- PHP 7.0 is at 2.05%
- PHP 7.1 is at 1.38%
#57345 is slated to drop support for 5.6, which means barring the unlikely event that migrating users choose PHP 7.0 or 7.1 instead of a later version, the collective usage of PHP 7.0+7.1 is <%5 and eligible to be dropped.
That said (and as evidenced in the referenced tickets), dropping support for a PHP version is an orchestrated event that requires leadership approval, coordination with web hosts, and an announcement post that gives users ample time to prepare.
In an effort to prevent some of the planning hiccups around previous version drops, and hopefully continuing to standardize the process, I propose we already begin planning the eventual removal of the next slated PHP version.
Specifically,
* We should choose a ""go/no-go"" date for when we should evaluate the stats and determine which versions (collectively) meet the <%5 threshold (my assumption is that we will want to pad #57345 to see where the migrations land).
* We should determine the minimum ideal time before dropping support for an announcement post (several in #57345 suggested 2-3 months advanced notice)
Previously:
#57345 Bumping the minimum PHP version to 7.0 in WordPress 6.3 (targeted)
#46594 Bumping the minimum PHP version to 5.6 in WordPress 5.2
#16917 Bumping the minimum PHP version to 5.2 in WordPress 3.2
" justlevine
Has Patch / Needs Testing 58715 WP Themes: Improve various globals documentation. Bundled Theme normal normal Awaiting Review defect (bug) new has-patch 2023-07-05T13:04:58Z 2024-01-22T06:56:12Z "I have reviewed the code and found some of the files need to be improved comment code. Please check the below files.
File Name:
- wp-content/themes/twentysixteen/functions.php
- wp-content/themes/twentytwelve/functions.php
- wp-content/themes/twentytwenty/functions.php" upadalavipul
Needs Patch 58714 View post link issue in post/article listing screen Posts, Post Types normal normal Awaiting Review defect (bug) new 2023-07-05T10:04:19Z 2023-07-05T10:04:19Z "Hello,
View post or permalink not generated when ""public"" argument is ""false"" in custom post type but ""View"" link show in post/article listing screen if ""public"" argument is ""false"" so It should be not shown in listing screen" hiren1094
Needs Patch 58710 REST: media (images) deleted or replaced are returned by their new id when requested by their old id REST API 6.2.2 normal major Awaiting Review defect (bug) new 2023-07-04T12:08:44Z 2023-10-16T14:53:56Z "An article has got a featured image assigned (id X).
The featured image is replaced* using Media library (id Y).
REST API for article delivers old image id (X).
Upon requesting fields (id, src) for old image id (X) from REST API media endpoint, the field id returned is the new image id (Y).
I expect the requested id and the returned id to match.
Alternatively I like to be able to get to know which id returned correlates to which id requested.
Example: https://deananddavid.com/wp-json/wp/v2/media/?include=77793&_fields=id,source_url&per_page=100
""include"" as per documentation requests certain ids. Notice the returned id is 77795 (5 instead 3 at last digit).
'* the replacement was done by an editor. I don't know the exact procedure she/he took." vialars
Needs Patch 58709 Bug 6.3 beta-3: Black screen when selecting blocks in List view outside the block editor viewport. Editor normal major Awaiting Review defect (bug) new 2023-07-04T06:06:04Z 2023-07-04T06:54:43Z "When using the List View in the block editor, if a block is not currently visible in the viewport of the editor, selecting that block from the List View results in a black screen.
Steps to Reproduce:
- Install WordPress **6.3 Beta-3**.
- Create a new post or page.
- Add multiple blocks, ensuring that some of them are not currently visible within the viewport of the block editor.
- Switch to List View to see the list of blocks.
- Choose ""Select"" from Tools.
- Attempt to select a block from the List View that is not currently visible in the viewport.
Screenshot - https://share.getcloudapp.com/p9uZbOz2" abhijitnage
Needs Patch 58708 Twenty Seventeen: caption alignment is different in editor and frontend Bundled Theme 5.8 normal normal Awaiting Review defect (bug) new 2023-07-04T05:46:57Z 2023-08-21T15:35:40Z In Twenty Seventeen theme the table caption is center in the editor but it is aligned to the left in the frontend pitamdey
Needs Patch 58707 Page looks fine, but after clicking to edit page, some text disappears, even after deactivating all plug-ins General 6.2.2 normal normal Awaiting Review defect (bug) new 2023-07-04T02:10:13Z 2023-08-25T21:04:41Z "My theme is Twenty Twenty-One.
Text after some footnotes seems to disappear in edit mode, but I have the same issue even after deactivating the footnote plug-in, as well as all other plug-ins.
This started happening after I upgraded to the latest version of WordPress. Before I upgraded, my site had quit working altogether. After I upgraded WordPress, my site came back, but the editing of pages is messing up, as described above." avnerstein
Needs Reporter Feedback / Steps To Reproduce 58706 SoundCloud block error Embeds 6.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-07-03T17:12:27Z 2023-07-03T23:31:01Z "Hello,
I am running 6.2.2.
Whenever I paste any SoundCloud story into the Block Editor, I always get an error that reads ""Sorry, this content could not be embedded"".
I'm able to use the HTML block and embed that way.
It appears others are seeing this problem too: https://wordpress.org/support/topic/soundcloud-embeds-stopped-working-2/
Thanks for your help!
-Tyler" paywall
Needs Patch 58700 wp_set_comment_status() modifies post_content Comments 6.2.2 normal major Awaiting Review defect (bug) new 2023-07-03T04:42:14Z 2023-07-14T21:06:45Z "I've created a standalone PHP script that runs on cron and uses wp_set_comment_status() to automatically approve select comments (based on user name, ip address, etc).
When a comment is approved, if the post_content contains a video tag, the video tag is rewritten.
From :
{{{
}}}
To :
{{{
}}}
My code :
{{{#!php
$comTime )
{
wp_set_comment_status($comment_id, 'approve', false);
}
}}}
Any idea why this is happening? I've had to go back and edit a lot of posts due to this issue." tweakfreaks
Needs Patch 58694 Enhancement in wordpress Database API Database 6.2.2 normal normal Awaiting Review feature request reopened 2023-07-01T12:11:08Z 2023-08-30T17:51:17Z "Hi
im a wordpress developer and freelancer
i also do wordpress Database optimization for my customers and I have a very smart suggestion to optimize the database structure of Beloved WordPress!
issue: Keep in mind that every plugin and theme installed in WordPress will inject some data (options/post-metas/ etc) to the wpdb and when you remove them their data will remain (unused) inside user wp database with no clue or indication of what template or plugin the information was for!
My suggestion: you can simply add an extra Argument for the core functions for adding options or metas (update_option or update_post_meta/update_user_meta) this Arg will add that plugin or theme base name to the added option or meta added like this -> update_option(""myopt"", ""myvalue"", $autoload, ""wooslider"")
which the 4th arg is the name of my example plugin and its REQUIRED type ALSO the name of the plg/theme can be auto inserted from an PHP constant -> (define('WOODMART_CORE', __FILE__); )
NOTE: By using this new system, whenever a person wants to manually optimize the database, she/he can easily find out which information is not needed and quickly query and delete them, Also, the plugins that perform database cleaning are much easier and more efficient, fully automatically find out which plugins no longer exist and which information is related to them and can be deleted without any trouble!
See the pic plz...
https://mdezign.ir/wp-content/uploads/2023/07/aasdsadasdasd.jpg
Consider this as a Great New development in order to optimize and speed up all WordPress sites!
Thanks a lot.
" mdesignfa
Has Patch / Needs Testing 58693 wordpress posts custom-meta box issue Options, Meta APIs 6.2.2 normal normal Awaiting Review defect (bug) new has-patch 2023-07-01T11:37:35Z 2023-07-02T06:30:37Z "Hello to the WordPress development team!
im a wordpress plugin developer and I developed a Custom-Plugin for my customer (www.delbarbash.com) and I found a critical issue with post/products meta_box
when i disable custom_meta (checkbox) form the screen-options (top-page) and reload the admin posts page or products page But again, the field was taken by PHP rendered (I saw this from view-page-source)
Issue: and when i update some product meta value from database or by ajax or somewhere else and then update the post the post will send the old meta_keys and meta_values to the wpdb and it seems to be a bug or malfunction Of course I disabled entirely the meta_box with the aid of remove_meta_box function (in my plugin)
My suggestion: to get rid of this weird issue I suggest a new system that when a user disable this meta_box (or all other boxes) from screen option an JS Confirmation take effect and ask the user (if you dont have un-saved values on this page, we will reload the page again) After page reload the page must-not render that box with PHP again! (instead of hidden that box with just CSS)
Thanks a lot!
Thank you for considering and checking my request and believe that this can be a big problem!" mdesignfa
Needs Patch 58688 Posts get unlinked from our site's taxonomy when being converted to Block Editor General normal normal Awaiting Review defect (bug) assigned 2023-06-30T16:01:52Z 2023-06-30T16:01:52Z "Sorry, I don't know how to describe this better. I work for HelloSubscription and we usually link our posts at hellosubscription.com by categories (news, coupons, reviews). We have taxonomies to link them to our directory (boxes.hellosubscription.com) so the post gets redirected to the right brand/box (we are a subscription box reviews website). However, these past week or so, whenever we convert the posts from Classic editor to Block editor, these taxonomies gets removed so the posts we publish doesn't get link to our directory page.
Sorry if this sounds confusing, but that's basically our little problem now." hspaula
Needs Patch 58679 meta key field in usermeta table should NOT use accent insensitive collations Security normal major Awaiting Review defect (bug) new 2023-06-30T09:09:50Z 2023-10-30T18:22:48Z "Looking at the latest string of vulnerability issues that came up related to the [Ultimate Member plugin](https://wordpress.org/plugins/ultimate-member/) I discovered that the usermeta table has an accent insensitive collation for the `meta_key` field. This results in queries for `wp_cãpăbilitiës` to return the actual `wp_capabilities` row! See `update_metadata()` function in wp-includes/meta.php
Imagine the attack surface this brings. In fact, don't imagine, just look at the recent attacks in the wild.
Fix: use accent insensitive collations (or even ASCII BINARY)" madhazelnut
Needs Patch 58676 Twenty Twenty-Two: Comment text box is touching the screen border for mobile devices Bundled Theme normal normal Awaiting Review defect (bug) new 2023-06-30T04:53:24Z 2023-09-09T09:38:01Z "The comment textarea box is touching the screen border so the design does not look proper for different mobile devices like iPhone 12 pro, iPhone XR etc.
Screenshot: [https://share.cleanshot.com/jFVNrx7tRZ2dNzvcjyfr]" himshekhar07
Needs Reporter Feedback / Steps To Reproduce 58669 Twenty Twenty-Three: Search input border does not display on font side. Bundled Theme normal normal Awaiting Review defect (bug) new reporter-feedback 2023-06-29T12:59:15Z 2023-09-04T06:59:41Z "I have reviewed Search block in different different themes and I found search input border does not display in frontend side for Twenty Twenty-Three.
Please check the below provided video recording for a better understanding.
Video Recording: https://share.cleanshot.com/Px5DpDrD3DLYKF1rYVd5" upadalavipul
Has Patch / Needs Testing 58668 "wrong ""domain"" returned by wpmu_validate_blog_signup when using on subsite in subdomain multisite" General 3.0 normal minor Awaiting Review defect (bug) new has-patch 2023-06-29T06:25:06Z 2023-06-29T06:30:52Z "`wpmu_validate_blog_signup` function relies on global `$domain` which will give wrong results when its triggered on subsite of subdomain multisite. In cases like this, `$domain` will be set to current subsite, which will lead to unexpected value of ""domain"" element in returned array.
Triggering the function on subsite will lead to ""domain"" element having value like ""newsite.currentsubsite.network"" instead of ""newsite.network"".
To fix this, `$domain` should be set based on `$current_network->domain` instead of global `$domain`." maniu
Needs Patch 58666 added HTML tags in HTML block Formatting 6.2.2 normal major Awaiting Review defect (bug) new 2023-06-29T02:41:45Z 2023-06-29T02:41:45Z If you add code, like css or javascript to an HTML block, save it and revisit it later on, HTML tags have been added, mostly line breaks . This breaks the added code. RichWP - Felix
Needs Patch 58663 Emoji: Consider eliminating expiry-based invalidation of wpEmojiSettingsSupports sessionStorage cache Emoji 6.3 lowest trivial Future Release defect (bug) new 2023-06-28T20:06:05Z 2023-07-19T16:09:30Z "Currently the results of the emoji-loader's tests for whether or not emoji are supported get cached in the browser's `sessionStorage` for 1 week. For most users, this expiration will never be reached since the browser tab would be closed and the `sessionStorage` cleared anyway. For the minority of users who keep a single tab open for weeks at a time, including those who restore tabs after installing an OS update, there can be scenarios where (1) the OS or Twemoji was updated to support emoji but the cache causes Twemoji to still be loaded, or (2) the emoji support was not changed and yet the browser re-checks support after a week unnecessarily.
See [https://github.com/WordPress/wordpress-develop/pull/4562#discussion_r1243983163 GitHub pull request discussion] for more context and possible solutions.
Nevertheless, as of #58472 the emoji tests have been greatly optimized so the cost of re-calculating support unnecessarily is not a meaningful performance hit, especially since ever since emoji support was introduced until now, the tests were being run on every page load anyway. This may not be worth the effort to resolve." westonruter
Needs Patch 58662 Transients cannot contain non-ascii characters Cache API 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-28T19:34:17Z 2023-06-28T19:34:17Z "set_transient reference says:
* Transient name is expected to not be SQL-escaped. Must be 172 characters or fewer in length.
* Transient value must be serializable if non-scalar. Expected to not be SQL-escaped.
Making note of above, and trying to set transient value with plain text, but containing non-ascii characters, the function fails to save the transient.
Using simple preg_replace('/[^A-Za-z0-9 ]/','', )); solves the problem, but the transient no longer contains the original text string.
As far as I see, serialization or json encoding the text string does not help, as it would still contain non-ascii characters.
So, either the set_transient function should accept more complex value parameters, or documentation should state the limitation on the value parameter.
I understand this may also be due to underlying memcached, but I do not see any mention in WP_Object_Cache documentation either that there are any limitations for the value/data to be stored." iarovuo
Needs Patch 58659 Bullet points General normal normal Awaiting Review defect (bug) new 2023-06-28T14:45:13Z 2023-06-29T09:14:32Z When adding a bullet pointed list, I am unable to easily make a new bullet point. Hitting 'enter' does not make a new bullet point. mrwilsondfsa
Needs Patch 58658 WP_Locale add get_month_genitive() method I18N 4.4 normal minor Awaiting Review enhancement new 2023-06-28T14:07:49Z 2023-06-28T14:36:02Z "The `WP_Locale` class has `get_month()` and `get_month_abbrev()` methods, but does not have `get_month_genitive()`. It should be there as well.
We should add such a code:
{{{
/**
* Retrieves the full translated month in genitive case by month number.
*
* @since 6.2.3
*
* @param string|int $month_number From 1 to 12. If a number less than 10 is
* passed in integer or string format, a '0' will be added before it.
*
* @return string Translated full month name in genitive case.
*/
public function get_month_genitive( $month_number ) {
return $this->month_genitive[ zeroise( $month_number, 2 ) ];
}
}}}
" Tkama
Needs Patch 58650 Reset cache in development mode Cache API normal normal Awaiting Review enhancement new 2023-06-28T00:47:17Z 2023-06-28T17:47:41Z "https://core.trac.wordpress.org/ticket/57487 added support for development mode in order that the WordPress code is aware of different methods and levels of caching.
Tests in the Gutenberg plugin utilize methods such as `wp_theme_has_theme_json`.
In Core, this method checks the current development mode and deal with the cache accordingly.
Because Gutenberg had not set the required constants, PHP unit tests were failing, probably because the cache was not being cleared between tests (`$can_use_cached` was always true).
In order to get the tests running on the Gutenberg CI, the constant `WP_RUN_CORE_TESTS` needed to be declared in [Gutenberg's PHPUnit bootstrap file]https://github.com/WordPress/gutenberg/pull/51950/files#diff-a51f75ea7a86ddd18edea3fe94a0482427795fcd7b247e6959149cbac60964dfR27.
PR: https://github.com/WordPress/gutenberg/pull/51950
An alternative way suggested by @noisysocks was for Core to update Core's implementation of `wp_theme_has_theme_json` to cache the return value in a way that is reset by `wp_clean_theme_json_cache`.
cc @flixos90
Related discussion:
https://github.com/WordPress/wordpress-develop/commit/4a16702090984caef24af5a07d598cc5afff2fdc#r119747488
" ramonopoly
Needs Patch 58649 Legacy Widget does not save additional css classes Widgets 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-28T00:31:32Z 2023-06-28T00:31:32Z "Additional CSS Classes do not save on Legacy Widgets.
* Install a new WordPress 6.2.2 site.
* Activate a non-block theme that supports widgets. I used Twenty Twenty-One
* Navigate to Appearance > Widgets
* Select Footer area
* Add a Navigation Menu (this creates a Legacy Widget) or add a Legacy Widget
* Navigate to the Legacy Widget block options Advanced > Additional CSS Class(es)
* Add any class name and update the widget area
* Refresh admin screen
* Navigate back to the Legacy Widget block options Advanced > Additional CSS Class(es)
* The additional class name has not been saved.
Also - if a legacy widget has any class names for earlier non-block-enabled widget areas, the class names are not pulled through to the Legacy Widget block options.
If you edit a Legacy Widget, it will lose any additional class names previously applied (before the widget area was blockified).
Loom recording example: https://www.loom.com/share/89afd2521bd44b25adc22642fd9be030" DeveloperWil
Needs Patch 58647 wp_generate_attachment_metadata generates scaled images Media 6.2.2 normal major Awaiting Review defect (bug) new 2023-06-27T21:34:17Z 2023-06-27T21:34:17Z "When using wp_generate_attachment_metadata() it seems to ignore the filter to turn off ""big_image_size_threshold"".
add_filter( 'big_image_size_threshold', '__return_false' );
$generateThumbs = wp_generate_attachment_metadata( $attachmentId, $file );
This results in a scaled version of the media being created and _wp_attached_file meta being replaced with the scaled versions path.
" picard102
Needs Patch 58644 embed height fix Embeds 4.4 normal normal Awaiting Review defect (bug) new 2023-06-27T15:59:11Z 2023-06-27T16:48:10Z "It seems that this fixes the issue of embeds cutting off at the bottom. It would be great if it could be implemented into the core.
I have tested it and it works and fixes the issue:
[https://medium.com/@wlarch/overwrite-and-bypass-wordpress-iframe-height-dimension-limit-using-javascript-9d5035c89e37 Overwrite and bypass WordPress iframe height dimension limit using JavaScript]" iamhugo76
Needs Patch 58640 Navigation Block renders wrong menu Menus 6.2.2 normal major Awaiting Review defect (bug) new 2023-06-27T07:15:00Z 2023-06-27T07:25:32Z I have been experiencing a problem with block editor in the theme block theme that I am developing. The core/navigation block does not renders the manu I select in editor. However, in editor, the menu that gets rendered is one selected. mechaartistix
Has Patch / Needs Testing 58639 Entity Name vs. Entity Number, for 6.4 Administration normal normal Awaiting Review defect (bug) new has-patch 2023-06-27T06:18:42Z 2023-06-27T06:18:42Z "This is a follow up ticket to #30796, which had some changes included in WordPress 6.3. See that ticket for discussion and history.
The list of @sabernhardt findings of strings using `’`: [https://docs.google.com/spreadsheets/d/1HrJsZSuTfWeAiZFu1STBrhrMT6U49qeeb26-cjUIiFo/edit?usp=sharingText strings with the apostrophe character code]
A PR at GitHub with some changes implemented from that list: [https://github.com/WordPress/wordpress-develop/pull/4672 PR #4672]" kebbet
Needs Dev / Bug Wrangler Feedback 58638 Add 'close' button to dashboard widgets oglekler Administration normal normal Future Release enhancement assigned dev-feedback 2023-06-27T04:59:43Z 2024-02-12T09:12:32Z In the Dashboard it isn't obvious that widgets can be removed from it via Screen options and sometimes widgets are annoying, or you just don't need them. I suggest adding `close` button into dashboard widget header. oglekler
Needs Patch 58636 Automatic Sanitization of Nonces in wp_verify_nonce Security normal normal Awaiting Review enhancement new 2023-06-26T21:28:18Z 2023-06-26T21:28:18Z "There's a [in-depth discussion](https://github.com/WordPress/WordPress-Coding-Standards/issues/869) in the WordPress Coding Standards repository over the question of whether nonces should be sanitized prior to being passed to `wp_verify_nonce()`.
At present, developers are required to sanitize the input themselves before it's passed to `wp_verify_nonce`. This practice is mandates by the PHPCS WordPress Coding Standard:
{{{
#!php
insert` function is advantageous due to its automatic data preparation.
However, this solution does raise a potential issue with pluggable nonces. If a nonce created by `wp_create_nonce` employs characters outside of the standard range and if `wp_verify_nonce` is not also plugged to accommodate these special characters, this implementation could potentially break.
We must also assume that a plugged `wp_verify_nonce` should sanitize the nonce it receives.
While there are some concerns associated with sanitizing nonces, the benefits largely outweigh the risks. These benefits include improved development experience, and stronger security, especially given the fact that many WordPress developers do not utilize PHPCS with WordPress Core Security Rules in their codebase, and may therefore be unaware of the need for nonce sanitization. This presents an opportunity to build a safer and more developer-friendly environment." lucasbustamante
Needs Patch 58631 "decoding=""async"" is added wildly, even if loading=""eager"" is there" General 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-26T14:54:25Z 2023-06-28T12:45:57Z "Could we do something about {{{decoding=""async""}}} parameter being added wildly on EVERY image?
It might seem to be a good idea, but it's not. I'm developing custom themes, and although it was introduced in 6.1, it touched me probably with some changes in 6.2 where {{{ wp_filter_content_tags() }}} is replacing images without the parameter (and {{{wp_get_attachment_image_attributes}}} filter is not called in this case. I was using loading=""eager"" for my hero images (rendered in the template via Timber) which should be a no-no to adding decoding=""async"" for that.
I might help to fix the issue if somebody guides me through track and svn (but I'm fluent in git repos if there is finally a way to contribute this way).
Suggesting - checking for fetch priority and loading=eager params, and if present, do not add {{{decoding=""async""}}} or {{{loading=""lazy.""}}}
I'm currently doing this, but it's silly to be fixing it on every site:
{{{#!php
'...',
);
$args = array(
'title_reply' => __('Leave a Reply', 'xxx'), // This value works
'title_reply_to' => __('Leave a Reply to %s', 'xxx'), // This value doesn't work
'title_reply_before' => '
', // The problem is when I add an icon to this value
'title_reply_after' => '
',
'fields' => apply_filters('comment_form_default_fields', $fields)
);
comment_form($args);
}}}
" metinmete
Needs Patch 58600 wp_query Enhancement Query 6.2 normal normal Awaiting Review feature request new close 2023-06-22T13:21:56Z 2023-07-03T16:51:04Z "I wolud like to enhance the wp_query to retrive post base on catgory orders.
Category Ex. with post
Mobile -: Post-1, Post-3, Post-6
Appliance -: Post-2, Post-8, Post-10
I Need Posts like in this order using wp_query of order by category ASC/DESC
Current output is according to ID order
Post-1
Post-2
Post-3
Post-6
Post-8
Post-10
Expected output
Post-2
Post-8
Post-10
Post-1
Post-3
Post-6" thakordarshil
Needs Patch 58595 Add a new admin page with support information and resources Help/About 3.1 normal normal Awaiting Review enhancement new 2023-06-22T01:08:57Z 2023-06-22T01:08:57Z "The links under the 'W' menu are little used links in a high-traffic context. They are also external links in a menu that otherwise only accesses information within WordPress.
Following up from discussions on #55960, I'm proposing that we remove the dropdown of links currently attached to the 'W' menu and replace it with a single link for support and resource information.
This would allow us to create a page that offers much more significant user and developer assistance by directing users to a wide variety of resources on WordPress.org.
" joedolson
Needs Patch 58594 Media file changes no longer trigger updated/modified statuses. Media 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-21T19:54:38Z 2023-06-21T19:54:38Z "In older versions of WP, when media files like PDFs were updated it would trigger an event that could be listened to and acted upon by plugins.
In the current version of WP (6.2.2) if a user changes the uploaded date or otherwise modifies a media file's properties, the change is no longer picked up by audit trail plugins like WP Activity Log, nor is it seen as an update to a ""post"".
Plugins that have ""Clear cache whenever a post or page is updated"" functionality are now broken when it comes to media file changes.
For instance, if a site is using Sucuri's WAF and caching plugin as well as the Enable Media Replace plugin, when a user replaces a media file with a new one it doesn't trigger Sucuri's cache clearing functionality anymore. I have reviewed both Enable Media Replace and Sucuri's plugins to make sure neither of them are at fault for breaking this functionality. Additionally, neither Sucuri nor WP Activity Log pick up the changes to display in their activity logs.
I do not know if media file post types were explicitly excluded from using the process pages and posts use to broadcast changes, but this new behavior is only present in the most recent version(s) of WP and is a bug if this wasn't a planned change." sbeaney
Needs Patch 58593 Slow list of posts in the admin panel (with a large wp_posts table) Query 6.2.2 normal normal Awaiting Review enhancement new 2023-06-21T17:23:18Z 2023-06-26T15:42:55Z "Hello. With a large wp_posts table (more than 1 GB, more than 100k published posts), the list of posts in the admin panel may open for several seconds. Slow SQL query that calculates the number of ""my"" posts:
SELECT COUNT( 1 )
FROM wp_posts
WHERE post_type = ''
AND post_status NOT IN ( 'trash','auto-draft','inherit','request-pending','request-confirmed','request-failed','request-completed' )
AND post_author = 1
Solution:
ALTER TABLE `wp_posts`
ADD KEY `type_status_author` (
`post_type`,
`post_status`,
`post_author`
);" Shoorf
Needs Patch 58583 edit widget gutenberg blocks > can't see or add reusable blocks Widgets 6.2.2 normal major Awaiting Review defect (bug) new close 2023-06-20T22:05:31Z 2023-11-01T21:26:28Z No longer can + see or add reusable blocks when trying to edit widget areas using gutenberg block editor wordmax
Needs Patch 58574 PHP warnings General 6.2.2 normal normal Awaiting Review defect (bug) new close 2023-06-19T12:27:42Z 2023-06-19T20:58:50Z "Hey,
I'm using PHP 8.1, and I have encountered these PHP notices (I don't sure if they are all related to WordPress Core)
{{{
Warning: Undefined property: wpdb::$actionscheduler_actions in /home/......./....../wp-includes/class-wpdb.php on line 789
WordPress database error: [Table 'doryos1_dream_press.a' doesn't exist]
SELECT a.action_id FROM a WHERE 1=1 AND a.hook='rocket_preload_job_check_finished' AND a.status IN ('pending') ORDER BY a.scheduled_date_gmt ASC LIMIT 0, 5
Warning: Undefined property: wpdb::$actionscheduler_groups in /home/......./....../wp-includes/class-wpdb.php on line 789
WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE slug='rocket-preload'' at line 1]
SELECT group_id FROM WHERE slug='rocket-preload'
Warning: Undefined property: wpdb::$actionscheduler_groups in /home/......./....../wp-includes/class-wpdb.php on line 789
Deprecated: strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /home/......./....../wp-includes/class-wpdb.php on line 3255
Deprecated: strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /home/......./....../wp-includes/class-wpdb.php on line 3151
Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/......./....../wp-includes/class-wpdb.php on line 3177
WordPress database error: [Incorrect table name '']
SHOW FULL COLUMNS FROM ``
=====================================================
Notice: Function 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/......./....../wp-includes/functions.php on line 5865
}}}" dyos
Needs Patch 58567 Updates inconsistently missing from Updates page and no update count bubbles in admin menu Upgrade/Install normal normal Awaiting Review defect (bug) new 2023-06-18T00:50:49Z 2023-06-18T00:59:48Z "Until a few weeks ago, when there were X outstanding plugin updates, the Updates page showed them all, and the Updates and Plugins items in the admin menu showed a red bubble with X in it.
Now, when I log into WordPress, there are no red bubbles, and navigating to the Updates or Plugins page causes the bubbles to reappear, but the respective page may or may not show all the outstanding updates.
Sometimes, forcing the update check results in a full list, and sometimes, simply re-navigating to the same page completes the list. But sometimes, some updates disappear for no apparent reason.
I suspect this is related to having a premium plugin update on the list, but can't be sure. It just seems like partial lists contain a premium update, and often, it's one of those missing.
I've ruled out browser caching and there are no console errors or PHP error log message that could be related." galbaras
Has Patch / Needs Testing 58565 Twenty Fifteen: Border Style Issue in Pullquote Block Bundled Theme 5.4 normal normal Awaiting Review defect (bug) new has-patch 2023-06-17T08:01:41Z 2023-09-04T07:04:24Z "In the Twenty Fifteen Theme, when we add a Pullquote block in the Gutenberg editor (backend) and apply a border style, we can see that the border is displayed at the top and bottom in the Gutenberg editor. However, when we view the same Pullquote block on the frontend, the border is not visible.
" huzaifaalmesbah
Needs Patch 58559 Database error bug in wordpress current version Database normal normal Awaiting Review defect (bug) new 2023-06-16T13:10:15Z 2023-07-03T17:13:01Z "{{{
2023-06-16 8:52:53 47 [Warning] Aborted connection 47 to db: 'wordpressdb' user: 'wpuser' host: 'localhost' (Got an error reading communication packets)
2023-06-16 8:52:53 46 [Warning] Aborted connection 46 to db: 'wordpressdb' user: 'wpuser' host: 'localhost' (Got an error writing communication packets)
}}}
I am constantly seeing read and write errors in database due to wordpress in the current version. I have been running wordpress for years.
Upon checking the logs the read errors last query is
{{{
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID
FROM wp_posts
WHERE 1=1 AND (wp_posts.post_author = 2) AND ((wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish')))
ORDER BY wp_posts.post_date DESC
LIMIT 0, 32
}}}
The write error last query is
{{{
SELECT DISTINCT post_author FROM wp_posts WHERE post_type = 'post' AND post_status = 'publish' LIMIT 2
}}}
Both queries execute fine manually. The problem is not related to timeouts or max allowed packets as both execute manually.
I noticed they are both increasing the aborted clients value in mysql. There is also no quit sent at the end of the mysql connections.
It seems to be a bug within wordpress. I have literally gone through everything else possible to solve this bug." zoddshop63
Needs Patch 58553 Two query blocks on home template (FSE) breaks the second one Query 6.2 normal normal Awaiting Review defect (bug) new 2023-06-16T06:47:30Z 2023-06-16T06:47:30Z "On a site we have a home.html template where we display a custom query with sticky posts before the main query (inherited). We also filter the main query to do not display sticky posts again. Since we updated to 6.1.3 the second query skips the first post (that is the most recent non-sticky post).
After some debugging I realize that the `$wp_query->current_post` value is 0 after the first loop instead of -1, causing it to skip the first item (index 0) on the `$wp_query->posts array`. Following the logic in wp-includes I cannot find any obvious change introduced on 6.1.3 to produce this error.
I’ve reproduced the issue on a fresh new installation of wp (with 6.2 version):
* I have created several posts (duplications of Hello world)
* I have crated a new category.
* I have assigned three posts to the new category
* I have modified the home template (on the site editor) to add a custom query before the main one, where I display the three posts from the new category
[[Image(https://images2.imgbox.com/3d/5c/wfm9rpvl_o.png)]]
Result with wp 6.1.2
When I update to 6.1.3, the “last one” disapears:
[[Image(https://images2.imgbox.com/43/b0/OMZDY2ba_o.png)]]
I have found a quick fix that solves it:
{{{#!php
is_home){
global $wp_query;
//sets the $wp_query->current_post to -1
$wp_query->current_post = -1;
}
});
}}}
But I assume this may potentially affect more users and should be fixd on the core.
BTW: Using two custom queries doesn’t work for us because we want to keep the default pagination settings with the `/page/2` urls" acaballerog
Needs Dev / Bug Wrangler Feedback 58547 Twenty Seventeen: Calendar block header cells should be centered Bundled Theme 6.2.2 normal trivial Awaiting Review defect (bug) new dev-feedback 2023-06-15T17:51:49Z 2023-06-15T19:01:32Z "The th elements in the Calendar block are not centered like the rest of the text in the Calendar which looks odd.
" nkeller15
Has Patch / Needs Testing 58544 Need to verify safe website URL in comment form Comments normal normal Awaiting Review defect (bug) reopened has-patch 2023-06-15T12:18:00Z 2023-06-21T20:50:17Z "Hello,
We need to verify the website URL in the comment form and It should be safe before inserting into the database." hiren1094
Needs Reporter Feedback / Steps To Reproduce 58543 There are two problems with wordpress General 6.2.2 normal normal Awaiting Review defect (bug) reopened reporter-feedback 2023-06-15T12:10:26Z 2023-06-19T21:18:26Z The wordpress backend menu can't show submenus when hovering, and can't drag and drop images to sort images in the product gallery. wujuan911800262
Needs Patch 58542 Theme.json / Restricting general settings like font sizes on blocks generates a lot of duplication Themes normal normal Awaiting Review feature request new 2023-06-15T10:21:56Z 2023-06-15T10:21:56Z "Hello.
In my theme.json file, let's say I declare 20 font sizes in my settings / typography / fontSizes section. As per the official schema, it is an array of objects with a size, slug, and name property. I've seen a project declaring 20 of those.
Then I would like to restrict core/paragraphs to use only 5 of them, and core/headings to use only three.
With the current theme.json implementation, I need to declare a settings / blocks / ""core/paragraph"" object, then copy / paste the 5 font sizes objects I allow to my user to use with paragraphs.
The current problems I face are as follows :
- It generates a lot of code duplication
- The two declarations are not linked together, which can be used as an advantage, but also seen as an inconvenient, especially when adjusting main settings, which would then not be updated in blocks.
Proposal :
- Add a new attribute to the blocks settings, like ""restrict"", ""include"" or ""exclude"" which would be an array of slugs coming from the main settings declaration.
- It could work with color palettes, fontSizes, spaces, or any array that supports slugs.
- This way when declaring block specific settings, we could have less duplication, and a synchronization with main settings.
Example:
{{{#!json
{
""blocks"": {
""core/button"": {
""typography"": {
""fontSizesInclude"": [""sizeSlugA"",""sizeSlugB""]
},
""color"": {
""paletteExclude"": [""colorSlugA"",""colorSlugB""]
}
}
}
}
}}}
Thank you for your work and your time reading me.
Best Regards.
Jeremy." jdmweb
Needs Dev / Bug Wrangler Feedback 58541 WP_Filesystem_SSH2:put_contents (and others) does not check for $sftp_link to be up Filesystem API normal major Future Release defect (bug) new changes-requested 2023-06-15T06:47:39Z 2023-10-27T14:18:47Z "This is a bit long, as I need to explain the reason why it is a problem not to check for the link '$sftp_link' to be up.
In short: WordPress allows choosing between various FS_METHODS (wp-config.php), e.g. 'direct' or 'ssh2'. While neither choice will affect WordPress updating itself at all, it has implications when some plugins updating files writing content to a file (htaccess, css etc) via
{{{
$wp_filesystem->put_contents($file, $content);
}}}
The function put_contents should check whether the link is up.
There is a big difference how one needs to setup the '$wp_filesystem' instance if you use 'direct' or 'ssh2' - the first one does not need to connect, the second needs to setup a connection before being able to write.
For FS_METHODS 'direct':
{{{
global $wp_filesystem;
if(empty($wp_filesystem))
{
require_once ABSPATH . '/wp-admin/includes/file.php';
WP_Filesystem();
}
$wp_filesystem->put_contents($file, $content);
}}}
For FS_METHODS 'ssh2':
{{{
global $wp_filesystem;
if(empty($wp_filesystem))
{
require_once ABSPATH . '/wp-admin/includes/file.php';
WP_Filesystem();
// this is the ONLY difference to 'direct'
$wp_filesystem->connect();
}
$wp_filesystem->put_contents($file, $content);
}}}
In the file ABSPATH/wp-admin/includes/file.php (around line 2051) the function WP_Filesystem() simply sets up an instance of the class defined by FS_METHOD, but does NOT connect if FS_METHOD is set to 'ssh2'.
Now many plugins that need to write a file (css,htacess,etc) simply assume that FS_METHOD is set to 'direct' or even assume WP_Filesystem() will connect as well.
I have three plugins (there are more, but these are the ones I am 100% sure) that have problems writing
- Ultimate Addons for Elementor
- Astra Addons
- Sensei
Now I could tell those developers to do it properly.
However I think the function $wp_filesystem->put_contents() should CHECK whether the link is up and if NOT, call a function within the class and setup the link to the server, after all I would consider this is proper coding pratice.
{{{
public function put_contents( $file, $contents, $mode = false ) {
// so this is for people who come from the outside
// just setting up the class and dont care whether
// a call to ""connect"" is required.
error_log(""class-wp-filesystem-ssh2.php -> put_contents -> $file "");
if(!$this->sftp_link)
{
error_log(""class-wp-filesystem-ssh2.php link is null, connecting ...."");
// this function is similar to connect
$rc = $this->build_options_connect();
}
// put the contents
$ret = file_put_contents( $this->sftp_path( $file ), $contents );
if ( strlen( $contents ) !== $ret ) {
return false;
}
$this->chmod( $file, $mode );
return true;
}
}}}
The function $this->build_options_connect() sets up the required data structure similar to the function ""request_filesystem_credentials()"" in file ABSPATH/wp-admin/includes/file.php (around line 2250) and then sets up the connection similar to the function $wp_filesystem->connect() in file ABSPATH/wp-admin/includes/class-wp-filesystem-ssh2.php (around line 120).
I have done this on all of my servers for a few weeks now.
Message like this one example (of many) below have completely disappeared.
{{{
[10-Jun-2023 18:25:12 UTC] PHP Warning: file_put_contents(ssh2.sftp:///HIDDEN/htdocs/wp-content/uploads/uael_uploads/.htaccess): failed to open stream: operation failed in /HIDDEN/htdocs/wp-admin/includes/class-wp-filesystem-ssh2.php on line 283
}}}
While I stated 'has patch' (I do), let's first see what people say about this." jobst
Has Patch / Needs Testing 58539 Twenty Seventeen: Image block figcaption text alignment inconsistency Bundled Theme 5.8 normal normal Awaiting Review defect (bug) new has-patch 2023-06-14T19:45:56Z 2024-02-28T17:43:55Z "Steps to reproduce:
1. Activate Twenty Seventeen theme
2. Add an image using the image block
3. Notice center alignment of caption in the editor
4. Save page and view, noticing left alignment of caption now
" nkeller15
Needs Patch 58538 Wrong menu is shown after adding new Header Template parts Menus 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-14T18:51:11Z 2023-06-14T18:51:11Z "I believe I have found a repeatable bug, and workaround, pertaining to adding new Header Template Parts in WordPress 6.2.2, using multiple FSE themes.
The goal: To have (at least) three custom Page templates, each with a different Nav block in its header. The current site has a working header, containing a Nav block with ""menu 1"" selected from the Classic menu list, in the Front Page, Page (and other) Templates - so it's necessary to add two more Template Parts for Headers, and two new Custom Page Templates, using each new Header.
Steps:
- Add second Header Template Part, with a second menu selected from existing Classic menus.
- Add third Header Template Part, with a third menu selected from existing Classic menus.
- Add Custom Page Template 2, using Header Template Part 2, including Nav 2.
- Add Custom Page Template 3, using Header Template Part 3, including Nav 3.
**- Note that both new page Templates and Header Template Parts show the correct Nav menu in the editor.
**
- Assign one or more pages to Custom Page Template 2
- Assign one or more pages to Custom Page Template 3
- **BUG: All pages assigned to BOTH Custom Page Templates 2 and 3 will show only Nav menu 3**.
**In other words, creating the third Header Template Part seems to to overwrite the Nav menu selected in the second Header Template Part.
**
THE WORKAROUND:
For each of the two new Header Template Parts (2 and 3)
- Modify the menu of each Header Template Part in some way, such as:
- Add an item to the menu at the end (anything - just an empty item is fine).
- Save the Header Template Part, and test it. You will see the correct menu with the new item.
- Return to the Header Template Part, remove the extraneous item from the menu, and save it again.
- After doing this for both of Header Template Parts 2 and 3, they should then function correctly throughout the site.
" littleen
Needs Patch 58536 url_to_postid does not work at MS install in context of another blog when $wp_rewrite->use_verbose_page_rules differs Rewrite Rules normal normal Awaiting Review defect (bug) new 2023-06-14T11:18:44Z 2023-10-29T06:02:12Z "In a multisite installation, where there are blogs with mixed permastruct of some have the `$wp_rewrite->use_verbose_page_rules` set to `true` and some to `false`, the `url_to_postid` fails to find a post, since it's queried as a page, [https://core.trac.wordpress.org/browser/trunk/src/wp-includes/rewrite.php?rev=54364#L609 due to a falsey check].
As the rewrites rules are untouched upon `switch_to_blog` action and as the `url_to_postid` function works directly with the `rewrite_rules` option ([https://core.trac.wordpress.org/browser/trunk/src/wp-includes/rewrite.php?rev=54364#L563 via `WP_Rewrite::wp_rewrite_rules()` function] ), IMHO the best way to fix such a case would be to not rely on the property, but perform the same check as when the `use_verbose_page_rules` property is being set (see the attached patch)." david.binda
Needs Patch 58535 "Undefined array key ""file"" in function wp_calculate_image_srcset()" General normal normal Future Release defect (bug) new 2023-06-14T09:53:55Z 2023-06-14T16:19:41Z " I noticed the following two warnings in the error log:
{{{
PHP Warning: Undefined array key ""file"" in xxx/wp-includes/media.php on line 1367""
PHP Warning: Undefined array key ""file"" in xxx/wp-includes/media.php on line 1373""
}}}
" martinjhenne
Has Patch / Needs Testing 58527 Rest password error handling issue for email Users normal normal Awaiting Review defect (bug) new has-patch 2023-06-13T12:13:02Z 2023-06-23T08:48:39Z "Hello,
I am trying to reset password in user edit screen without configuring email services so I got **""Error: The email could not be sent. Your site may not be correctly configured to send emails. Get support for resetting your password.""** but same thing I am trying in user listing page so I got **""Password reset link sent.""**
this message.
so It should be same." hiren1094
Needs Dev / Bug Wrangler Feedback 58519 Inline styles block styles in bundled themes Bundled Theme 5.8 normal normal Awaiting Review enhancement new dev-feedback 2023-06-12T14:11:07Z 2023-06-19T16:59:26Z "In [50836] function was added, to inline block styles, so for better performance. There are a number of small stylesheets in bundled themes that could do with that could use this functionality. To opt-in a stylesheet, simply add the path add an extra piece of data of the stylesheet. Like this.
{{{#!php
wp_enqueue_style( 'twentyfifteen-block-style', get_template_directory_uri() . '/css/blocks.css', array( 'twentyfifteen-style' ), '20230122' );
wp_style_add_data( 'twentyfifteen-block-style', 'path', get_template_directory() . '/css/blocks.css' );
}}}
This could improve FE performance, as it remove a blocking request.
" spacedmonkey
Needs Patch 58518 """More info about performance optimization"" links in Site Health go to 404 error on WordPress.org" Site Health normal normal Awaiting Review defect (bug) new 2023-06-12T14:03:56Z 2023-06-13T06:47:37Z "On the Site Health page, at least under the ""Enqueued scripts"" improvements, the links for ""More info about performance optimization"" go to a broken link on wordpress.org (https://wordpress.org/support/article/optimization/). According to archive.org, it looks like that link was live as late as May 16, 2023. Not sure if there is now a new page. The only optimization page is https://wordpress.org/documentation/article/search-engine-optimization/." jeffgreendesign
Has Patch / Needs Testing 58516 url_to_postid does not return post id for static Posts page Rewrite Rules normal normal Awaiting Review defect (bug) new has-patch 2023-06-12T13:29:36Z 2023-06-12T13:38:13Z "Steps to reproduce:
- Create a page called ""Blog"", slug: blog. ID: 10 permalink: https://a.com/blog/
- Go to WordPress->Settings->Reading-> Your homepage displays -> A static page -> Posts page -> set the previously created ""Blog"" page.
- Call ->
{{{#!php
is_singular will return false.
The following code would solve this issue:
{{{#!php
posts) && $query->is_singular) {
return $query->post->ID;
} else {
if ($query->get_queried_object() instanceof WP_POST) {
return $query->queried_object_id;
}
return 0;
}
}}}
" nextendweb
Needs Dev / Bug Wrangler Feedback 58515 Need to use $wpdb->prepare instead of sprintf Query normal normal Awaiting Review defect (bug) new dev-feedback 2023-06-12T13:04:00Z 2023-06-22T07:25:46Z "Need to use $wpdb->prepare instead of sprintf in ""_prime_comment_caches"" functions.
File: wp-includes/comment.php" hiren1094
Needs Patch 58513 Uploading JSON file of 1MB or less fails to upload Upload 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-12T11:21:01Z 2023-06-12T11:25:04Z "When uploading a JSON file of exactly 1048577 bytes or less leads to:
{filename} has failed to upload.
Sorry, you are not allowed to upload this file type.
Even though the file type is allowed. Tested with JSON file of valid JSON of 1048578 bytes (success) and 1048577 byes (failure)." oliward@…
Needs Dev / Bug Wrangler Feedback 58512 Enhancing Security and User Experience: Addressing Password Length Limitations and Improving Validation Process Posts, Post Types 6.2.2 normal normal Awaiting Review defect (bug) new dev-feedback 2023-06-12T11:08:25Z 2023-07-14T11:31:15Z "When I attempted to use a password consisting of 256 characters and tried to publish my post, I encountered an error message stating, ""Updating failed. Could not update post in the database."" It appears that this issue may affect all users. Therefore, I kindly request that you consider addressing this problem by either fixing it or implementing validation on the input field to prevent such errors in the future.
I used below password for password protect post :
123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345
**Total Characters: 255**
Could you please verify the attached video URL, https://www.awesomescreenshot.com/video/18248088?key=dd7a62697a5b66aaf5d332dec3a0a9b9" utsav72640
Has Patch / Needs Testing 58511 Escaping function missing in wp-trackback.php Pings/Trackbacks normal normal Awaiting Review defect (bug) new has-patch 2023-06-12T06:30:58Z 2023-06-12T07:07:00Z Escaping function missing in wp-trackback.php file. utsav72640
Needs Dev / Bug Wrangler Feedback 58508 Gutenberg and CSS Editor 6.2.2 normal normal Awaiting Review defect (bug) new dev-feedback 2023-06-11T00:20:52Z 2023-06-11T00:20:52Z "ENGLISH
Hello. I created a page, but when I deleted a photo from the gallery, all the content was deleted.
Going to the revisions I was able to restore the content, but when updating, everything is deleted again.
I changed the version from PHP8.0 to 8.1 but still the same.
I deactivated the plugins and the error was repeated.
Finally, with all these changes, I restored the page revision that has all the content, but I added a full stop to some text, I UPDATED and the content was no longer deleted.
I activated all the plugins and the error returned.
I started to disable GUTENBERG first, restored the revision without making changes to it, saved the page and it works fine.
PS: I had to change from PHP8.1 to 8.0 because it throws errors in the Backend (css is disabled, still changing themes)
THEME: ASTRA
WP: 6.2.2
PHP at startup: 8.1
PHP at the end: 8.0
----
ESPAÑOL
Hola. He creado una página, pero al borrar una foto de la galería, se borró todo el contenido.
Yendo a la revisiones pude restaurar el contenido, pero al actualizar, vuelve a borrarse todo.
Cambié la versión de PHP8.0 a 8.1 pero seguía igual.
Desactivé los plugins y el error se repetía.
Por último, con todo estos cambios, restauré la revisión de página que tiene todo el contenido, pero le agregué un punto final a un texto, ACTUALICÉ y ya no se borró más el contenido.
Activé todos los plugins y volvió el error.
Empecé a desactivar primero GUTENBERG, restauré la revisión sin hacerle cambios, guardé la página y funciona bien.
PD: Tuve que cambiar de PHP8.1 a 8.0 porque arroja errores en el Backend (se desactiva el css, aún cambiando de temas)
TEMA: ASTRA
WP: 6.2.2
PHP al inicio: 8.1
PHP al final: 8.0
" aiteok
Has Patch / Needs Testing 58507 GitHub actions are failing General normal normal Awaiting Review defect (bug) new has-patch 2023-06-10T20:45:46Z 2023-06-10T20:58:12Z "GitHub actions are failing due to the following error:
{{{
- Installing squizlabs/php_codesniffer (3.6.0): Extracting archive
[Composer\Plugin\PluginBlockedException]
dealerdirect/phpcodesniffer-composer-installer contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe.
You can run ""composer config --no-plugins allow-plugins.dealerdirect/phpcodesniffer-composer-installer [true|false]"" to enable it (true) or disable it explicitly and suppress this exception (false)
See https://getcomposer.org/allow-plugins
}}}
" h71
Needs Patch 58505 Using WORDPRESS_DB_HOST variable Cannot connect to the database, must be configu General 6.2.2 normal major Awaiting Review defect (bug) new 2023-06-10T07:07:08Z 2023-11-18T13:21:13Z "I use kubernetes to run wordpress, and configure the WORDPRESS_DB_HOST variable, but it can not connect to the database, manually configure the database IP can be, mast have i to manually configure?
I also tried using docker and 'WORDPRESS_DB_HOST' didn't work either.
The image I used is wordpress:php8.2" chentc
Needs Patch 58504 Errors after WordPress 6.2.2 update General 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-10T06:25:36Z 2023-06-10T06:25:36Z "According to the instructions, the Twenty Twenty-Three theme without using any plugins and the errors I get when I activate my preferred theme are listed.
I would like to point out that these errors occur when trying to add New Plugin, New Themes. It also gives errors in language files.
I hope the problems will be fixed quickly. Good luck to you.
Status:
WordPress 6.2.2 running Twenty Twenty-Three theme.
Current version: 6.2.2
Last checked on June 10, 2023 at 9:16 am GMT+0300. Check again.
This site is automatically kept up to date with each new version of WordPress.
Switch to automatic updates for maintenance and security releases only.
Wordpress 6.2.2 Error List
General Language Error
""Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /home/oxowpxyz/oak.oxowp.xyz/wp-admin/includes/translation-install.php on line 68.""
Add new plugins page Error
""An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums.""
Add Themes page Error
""An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums.""" bakgun1
Needs Dev / Bug Wrangler Feedback 58502 Visiting /wp-admin/options-permalink.php causing Fatal Error Permalinks 6.2.2 normal normal Awaiting Review defect (bug) new close 2023-06-09T10:05:47Z 2023-06-28T15:48:07Z "I'm using WordPress 6.2.2 on PHP 8.1.x
`Fatal error: Uncaught ValueError: Unknown format specifier ""<"" in /wp-admin/options-permalink.php:38 Stack trace: #0 /wp-admin/options-permalink.php(38): sprintf() #1 {main} thrown in /wp-admin/options-permalink.php on line 38`
Here is the WordPress Health Status:
{{{
### wp-core ###
version: 6.2.2
site_language: bn_BD
user_language: bn_BD
timezone: Asia/Dhaka
permalink: /%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: /home/PATHTRUNCATED
wordpress_size: 685.79 MB (719102256 bytes)
uploads_path: /home/PATHTRUNCATED/wp-content/uploads
uploads_size: 584.80 MB (613205338 bytes)
themes_path: /home/PATHTRUNCATED/wp-content/themes
themes_size: 7.46 মেগাবাইট (7824982 bytes)
plugins_path: /home/PATHTRUNCATED/wp-content/plugins
plugins_size: 121.31 MB (127206397 bytes)
database_size: 25.04 MB (26253129 bytes)
total_size: 1.39 GB (1493592102 bytes)
### wp-dropins (1) ###
maintenance.php: true
### wp-active-theme ###
name: Twenty Fifteen (twentyfifteen)
version: 3.4
author: ওয়ার্ডপ্রেস টিম
author_website: https://wordpress.org/%20
parent_theme: none
theme_features: core-block-patterns, widgets-block-editor, automatic-feed-links, title-tag, post-thumbnails, menus, html5, post-formats, custom-logo, custom-background, editor-style, editor-styles, wp-block-styles, responsive-embeds, editor-color-palette, editor-gradient-presets, customize-selective-refresh-widgets, custom-header, widgets
theme_path: /home/PATHTRUNCATED/wp-content/themes/twentyfifteen
auto_update: off
### wp-themes-inactive (1) ###
Twenty Twenty-Three: version: 1.1, author: the WordPress team, automated updates is turned off
### wp-mu-plugins (1) ###
InfiniteWP - Client Loader: version: 1.0.1, author: Revmakx
### wp-plugins-active (1) ###
Maintenano: version: 0.0.1, author: nanodesigns, automated updates is turned off
### wp-media ###
image_editor: WP_Image_Editor_GD
imagick_module_version: not found
imagemagick_version: not found
imagick_version: not found
file_uploads: File uploads is turned off
post_max_size: 8M
upload_max_filesize: 2M
max_effective_size: 2 মেগাবাইট
max_file_uploads: 20
gd_version: 2.3.3
gd_formats: GIF, JPEG, PNG, WebP, BMP, AVIF, XPM
ghostscript_version: 9.25
### wp-server ###
server_architecture: Linux 4.18.0-348.20.1.lve.1.el7h.x86_64 x86_64
httpd_software: LiteSpeed
php_version: 8.1.18 64bit
php_sapi: litespeed
max_input_variables: 1000
time_limit: 180
memory_limit: 128M
admin_memory_limit: 256M
max_input_time: 60
upload_max_filesize: 2M
php_post_max_size: 8M
curl_version: 7.87.0 OpenSSL/1.1.1p
suhosin: false
imagick_availability: false
pretty_permalinks: true
htaccess_extra_rules: true
### wp-database ###
extension: mysqli
server_version: 10.3.39-MariaDB
client_version: mysqlnd 8.1.18
max_allowed_packet: 268435456
max_connections: 151
### wp-constants ###
WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /home/PATHTRUNCATED/wp-content
WP_PLUGIN_DIR: /home/PATHTRUNCATED/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: true
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
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
}}}" wzislam
Needs Reporter Feedback / Steps To Reproduce 58501 Need to change in docs comment in xmlrpc.php General normal normal Awaiting Review defect (bug) new reporter-feedback 2023-06-09T09:59:58Z 2023-06-13T05:07:37Z "Hello,
Need to change below the comment for this ""logIO()"" function.
Need to change comment ""logIO() - Writes logging info to a file."" line and It should be ""Writes logging info to a file - logIO()."" Also, add a full stop in the last for this line ""@param string $io Whether input or output""
As per phpcs coding standard." hiren1094
Has Patch / Needs Testing 58500 Twenty Twenty: Separator block's Default style is wider than Wide Line style in editor Bundled Theme 6.2.2 normal minor Awaiting Review defect (bug) new has-patch 2023-06-09T08:22:02Z 2023-06-10T09:27:47Z "Steps to reproduce the issue.
1. Activate Twenty Twenty theme.
2. Take separator block.
3. Choose wide-width and check that editor and front both side.
In front side default and wide width working as expected but in editor side it not works proper.
I have attached video for better understanding.
Video URL :- https://share.cleanshot.com/xLbqrymSPhRf1kPpSw7B" nidhidhandhukiya
Has Patch / Needs Testing 58499 Twenty Twenty theme table block having issue with color Bundled Theme 6.2.2 normal minor Awaiting Review defect (bug) new has-patch 2023-06-09T07:33:23Z 2023-07-13T06:57:04Z "Steps to reproduce the issue.
1. Activate Twenty Twenty theme.
2. Take table block.
3. Add some text.
4. Apply background color black or pink.
5. Now apply any color to the text.
You can able to see it will not take the value of that choosen color if black or pink is set as a background color for editor side.
Front side it is working fine it is having issue only in editor side.
I have attached video for better understandng.
Video URL :- https://share.cleanshot.com/plqBT1cn6hMbRR5g6Grz
" nidhidhandhukiya
Needs Dev / Bug Wrangler Feedback 58497 when the content of a page is structured into two columns, it causes the menu bar background to change unexpectedly. Bundled Theme 6.2.2 normal normal Awaiting Review defect (bug) new dev-feedback 2023-06-08T23:27:10Z 2024-02-01T09:31:25Z "Not sure how to put this one in to words.
1. I have a nav bar at the top of twenty twenty three. Background color is set works fine.
2. yesterday I tried out adding a two column block in a page content area on edit page. (Still learning the new flow. getting better at it but still a learning curve).
3. about half of the nav bar on these pages with columns in the content area turns white. Not all of the nave bar, but half.
4. Confused me and looked for css solution before realizing it was the same template working fine on other pages and then realized it was the column.
5. Removing the column from the page content area fixes the issue.
" noelhefele
Has Patch / Needs Testing 58495 Twenty Twenty: Pull Quote Block issues Bundled Theme 6.2.2 normal normal Awaiting Review defect (bug) new has-patch 2023-06-08T13:33:24Z 2023-06-10T04:38:59Z "Pull Quote block citation on Twenty Twenty theme has these issues:
1. Pull Quote citation is always shown in Italics in Block Editor but normal in Frontend.
2. Pull Quote is shown in Bold in Frontend even if not selected in Block Editor. Even selecting options from Appearance has no effect on the frontend.
3. If you make the citation Italic, it becomes Italic & bolder. Then if you select Bold, it becomes bold. But if you select Bold first and then Italic, font becomes bolder and not bold. The HTML element depends on the first chosen option.
How to Replicate:
1. Activate the Twenty Twenty theme
2. Insert Pull Quote block and enter quote and citation." jyolsna
Has Patch / Needs Testing 58492 Plugin Search Issue: Trimming of Keywords with Ampersand (&) upon Page Refresh Plugins 6.3 normal normal Awaiting Review defect (bug) new has-patch 2023-06-08T12:45:54Z 2023-07-14T15:41:28Z "I have encountered a peculiar issue with the plugin search functionality in the WordPress backend. When performing a plugin search using keywords that contain an ampersand (&) character and refreshing the page twice, the keywords are getting trimmed, resulting in incomplete search results.
Steps to Reproduce:
1. Access the WordPress backend.
2. Navigate to the Plugins section.
3. In the search box, enter keywords that include an ampersand character, e.g., ""search & replace""
4. Press Enter or click the Search button.
5. Note the search results.
6. Refresh the page twice by pressing F5 or using the browser's refresh button.
7. Observe that the search keywords are being trimmed to ""search"" only.
8. The search results are now incomplete, as the full keywords were not used for the search.
Expected Results:
The plugin search should retain the complete keywords, including the ampersand character, upon page refreshes. This would ensure accurate and consistent search results, even after multiple page refreshes.
Actual Results:
Upon refreshing the plugin search page twice, the keywords containing an ampersand (&) are trimmed, resulting in incomplete search results.
Reproducibility:
Consistently reproducible.
" adhun
Needs Patch 58491 UI problem when search for block while adding a post Editor 6.2.2 normal normal Awaiting Review defect (bug) new close 2023-06-08T12:35:02Z 2023-11-28T16:15:27Z "**Precondition:**
- Gutenberg version 15.9.1
- WP 6.2.2
- PHP 8.2.5
- Ubuntu 23.04
**Steps:**
1- Create a new post
2- Click the + icon and search for 'block'
3- The UI expands slowly with no interaction
Expected: spaces fit automatically
Screencast: https://jmp.sh/KsMTIFiM" mai21
Has Patch / Needs Testing 58490 Make wp_update_term_count function site context aware for the multisite Taxonomy normal normal Awaiting Review defect (bug) new has-patch 2023-06-08T12:32:40Z 2023-06-08T13:57:45Z "During the import process, a performance problem arose because of term counting with each insert. However, this issue was reported and resolved with ticket #5377. Unfortunately, the solution is not compatible with multisite.
The syndication plugin causes delays in the syndication of multiple posts between sites in the multisite, primarily because of the term counting required during each insert.
Suppose you need to synchronise content across subsites and want to enhance the sync performance by turning off the term counting logic. In that case, you would follow these steps.
{{{
$post_list = [1, 2, 3];
switch_to_blog(2);
wp_defer_term_counting(true);
do_multiple_syncs( $post_list );
wp_defer_term_counting(false);
restore_current_blog();
}}}
We made a change by disabling term counting during each insertion and performing it after the inserts, as planned. However, this caused some problems. The menus on our website kept disappearing without any apparent reason, and we had to resave them to restore them manually.
Upon inspection, it was discovered that the `wp_update_term_count` function does not consider the multisite when the term counting is disabled [https://github.com/WordPress/wordpress-develop/blob/6.2/src/wp-includes/taxonomy.php#L3464]. For instance, in the sync job mentioned above, if the list of term IDs from subsite 2 is added for a recount in a static variable, the function incorrectly recounts it in the main site.
The term count was updated to `0` in the database. This is because the term ID doesn't exist on the main site or no posts have been assigned. It causes the check (https://github.com/WordPress/wordpress-develop/blob/6.2/src/wp-includes/nav-menu.php#L721-L725) to fail on the `wp_get_nav_menu_items` function and menus disappear." sathyapulse
Has Patch / Needs Testing 58488 Improve performance of wp-admin -> Comments Administration normal normal Awaiting Review defect (bug) new has-patch 2023-06-08T11:12:24Z 2023-06-08T11:22:25Z "Our wp-admin -> Comments screens just got slower over time and the reason is the ""All comment types"" drop down filter.
Here's how much that single select box adds on some of our websites depending on the number of comments:
* 6 seconds for website with 2,668,659 comments
* 1 second for website with 795,581 comments
So it's really too much delay anytime you open wp-admin -> Comments just to get that single filtering option.
The problematic code is in the WP_Comments_List_Table::comment_type_dropdown() function which calls:
{{{#!php
get_comments( array(
'number' => 1,
'type' => $type,
) );
}}}
That code runs query like:
{{{#!sql
SELECT wp_comments.comment_ID FROM wp_comments
WHERE
( ( comment_approved = '0' OR comment_approved = '1' ) ) AND
comment_type IN ('pingback', 'trackback')
ORDER BY wp_comments.comment_date_gmt DESC LIMIT 0,1
}}}
As illustrated that query can take seconds to finish - as much as 6 seconds in our case and we have to wait that long anytime we open wp-admin -> Comments.
There are two causes of the poor performance:
=== **1) Missing comment_type index**
Running SQL EXPLAIN command on the query reveals that it only uses the comment_date_gmt index.
Adding the comment_type index helps: ALTER TABLE `wp_comments` ADD INDEX `comment_type` (`comment_type`)
Here's how much time adding that index took:
* 5 seconds for 2,668,659 comments (dedicated SQL server with low load)
* 23 second for 795,581 comments (shared server with higher load)
I see the wp-admin/includes/upgrade.php does a fair amount of ALTER TABLE with ADD INDEX.
We prepared that upgrade code in wp-admin/includes/upgrade.php.
And of course added that index for new install in wp-admin/includes/schema.php.
=== **2) Using ORDER BY when not required**
On one of our databases (using MariaDB) just adding the comment_type index fixed the issue, but on some other we **also** had to get rid of the ORDER BY in the query as it's not important when you are checking if there are any Pings.
get_comments() just does that automatically. This can be easily fixed by adding 'oderby' => 'none' to the call in WP_Comments_List_Table::comment_type_dropdown() in wp-admin/includes/class-wp-comments-list-table.php:
{{{#!php
get_comments(
array(
'number' => 1,
'orderby' => 'none',
'type' => $type,
)
)
}}}
This fix can be seen in the Github pull request.
---
With both fixes the performance is now much better:
* 0.4 seconds for website with 2,668,659 comments
* 0.12 seconds for website with 795,581 comments
" FolioVision
Needs Patch 58487 Text editor problem Posts, Post Types 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-08T11:07:40Z 2023-06-08T14:02:19Z "Hi, the < character causes corruption.
lines are concatenating and shortcodes don't work
1: https://ibb.co/yndnCP1
2: https://ibb.co/Rhd2r87
If there is no < character, everything will look normal.
3: https://ibb.co/1Xvvw7V" burhi
Needs Patch 58486 Using WordPress 5.7.8 (but also all other more recent branches) - characters are stripped through TinyMCE Copy paste from Word TinyMCE 5.7.2 normal normal Awaiting Review defect (bug) new 2023-06-08T09:44:51Z 2023-06-08T09:44:51Z "Hi
Using WordPress 5.7.8 (but also all other more recent branches) - characters are stripped through TinyMCE Copy paste from Word.
Under conditions: Bulleted list, from word, pasted, containing a dot at the end of the word.
Detailed descpription with fix here:
https://github.com/tinymce/tinymce/issues/3480
https://github.com/aautio/tinymce/commit/b5f4db5a8377d2beb9ca3a1a7164587b280acbf4
Seems implemented in TinyMCE since March 31 2021, however the update of TinyMCE editor has not yet been included in current WordPress versions.
Can this still be applied?
Kind regards,
Ralph Gortzen
Application manager Atos.net Group site.
" rgortzen
Has Patch / Needs Testing 58484 Site Health: Improve display of constants in debug data SergeyBiryukov Site Health 6.3 normal normal 6.6 enhancement reviewing has-patch 2023-06-08T08:05:12Z 2024-02-23T12:53:00Z "This is a follow up on #55741.
where we need to have just a single function to be called which determines the environment type.
As wp-admin/includes/class-wp-debug-data.php is already using:
{{{
$environment_type = wp_get_environment_type();
}}}
and later on:
this happens
{{{
// Check WP_ENVIRONMENT_TYPE.
if ( defined( 'WP_ENVIRONMENT_TYPE' ) && WP_ENVIRONMENT_TYPE ) {
$wp_environment_type = WP_ENVIRONMENT_TYPE;
} else {
$wp_environment_type = __( 'Undefined' );
}
}}}
so this is not the same as what happens at wp_get_environment_type();
So this ticket is where we remove that lines of code.
" ramon fincken
Needs Patch 58483 UI issue in uploasd multiple media in mobile Media 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-08T07:40:16Z 2023-06-08T07:40:16Z "Hi,
We need to add padding on the right side for maintaining alignment on the right side in uploading multiple media on mobile.
The more informed nation you can see mentioned screenshot. " sumitsingh
Has Patch / Needs Testing 58479 Add notice if no posts are selected in Bulk Edit quadthemes Quick/Bulk Edit 6.2.2 normal normal 6.6 enhancement assigned has-patch 2023-06-08T07:13:01Z 2024-02-18T16:10:37Z "On the Posts screen(s), clicking the bulk actions Apply button without selecting any posts does not show an error message.
1. Visit the Posts screen.
2. Choose ""Edit"" in the Bulk actions dropdown.
3. Without checking any checkboxes, click the Apply button. Nothing seems to happen.
4. Choose ""Move to Trash"" in the Bulk actions dropdown.
5. Click the Apply button. The page reloads but cannot move anything to Trash.
6. Choose ""Bulk actions"" at the top of the Bulk actions dropdown.
7. Click the Apply button. The page reloads with a query string in the URL.
I have checked and it should be a message on the page/post list as per added notice message on the plugin page.
For more information, you can see mentioned quick video.
Thank you" sumitsingh
Needs Reporter Feedback / Steps To Reproduce 58478 Text mis-aligned count bubbles on mobile Administration 6.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-06-08T06:56:34Z 2023-06-08T07:19:58Z "Hi,
Small UI issue in the mobile device. it is not properly alignment on a mobile device. For more information, you can see mentioned screenshot." sumitsingh
Needs Patch 58476 preg_split(): Passing null to parameter #2 ($subject) of type string is deprecated Posts, Post Types 6.3 normal normal Awaiting Review defect (bug) new 2023-06-08T00:16:08Z 2023-12-12T20:54:33Z "== Bug Report
=== Description
Using the filter hook 'the_content' and passing an empty string or null produces the preg_split deprecation notice in the convert_smilies() function.
=== Environment
- WordPress: 6.3-alpha-55892
- PHP: 8.2.2
- Server: Apache/2.4.54 (Win64) PHP/8.2.2 mod_fcgid/2.3.10-dev
- Database: mysqli (Server: 8.0.27 / Client: mysqlnd 8.2.2)
- Browser: Chrome 114.0.0.0 (Windows 10/11)
- Theme: Seele 1.1.1
- MU-Plugins:
* WP Migrate DB Pro Compatibility 1.1
- Plugins:
* bbPress 2.6.9
* Classic Widgets 0.3
* Contact Form 7 5.7.7
* Database Backup for WordPress 2.5.2
* Envato Market 2.0.8
* Force Plugin Updates Check 1.0.2
* Optimize Database after Deleting Revisions 5.0.110
* Query Monitor 3.12.3
* Redux Framework 4.4.1.4
* Regenerate Thumbnails 3.1.5
* Requite Core 1.1.13
* Slider Revolution 6.6.14
* Slider Revolution Paint-Brush Add-On 3.0.4
* Slider Revolution Particles Effect 3.3.2
* Slider Revolution Slicey Add-On 3.0.4
* Theme Check 20230417
* Ultimate Addons for WPBakery Page Builder 3.19.14
* WooCommerce 7.7.2
* WordPress Beta Tester 3.4.1
* WordPress Importer 0.8.1
* WPBakery Page Builder 6.13.0
* WP Crontrol 1.15.2
* WP Migrate DB Pro 1.8.1
* WP Migrate DB Pro CLI 1.3.2
* WP Migrate DB Pro Media Files 1.4.9
* WP Migrate DB Pro Multisite Tools 1.2
=== Steps to Reproduce
1. Use this filter, ensuring $content is empty or null: $content = apply_filters( 'the_content', $content );
preg_split(): Passing null to parameter #2 ($subject) of type string is deprecated
wp-includes/formatting.php:3482
preg_split()
wp-includes/formatting.php:3482
convert_smilies()
wp-includes/class-wp-hook.php:310
apply_filters('the_content')
x. 🐞 Bug occurs.
=== Expected Results
1. ✅ The filtered content.
=== Actual Results
1. ❌ The indicated deprecation error due to preg_split not liking a null value." KProvance
Has Patch / Needs Testing 58475 Twenty Twenty-Three: Aubergine variation's background implementation causes any block that impacts page height to impact header Bundled Theme low normal Awaiting Review defect (bug) new has-patch 2023-06-07T20:16:11Z 2023-06-20T16:59:53Z "Originally reported here and moving over: [https://github.com/WordPress/gutenberg/issues/51248 GB51248]
This variation does the following for the background:
{{{
linear-gradient(180deg, var(--wp--preset--color--base) 0 min(24rem, 10%), var(--wp--preset--color--secondary) 0% 30%, var(--wp--preset--color--base) 100%)
}}}
As Justin notes, in particular, the `min(24rem, 10%)` is essentially saying to use the lower value (either `24rem` or `10%`). On pages with little content, it is pretty much guaranteed to be 10% of the `` height.
As a result, any block that can change the page height will run into issues.
" annezazu
Needs Dev / Bug Wrangler Feedback 58474 Twenty Seventeen: Box shadow on Site Logo block looks odd Bundled Theme 6.2.2 normal minor Awaiting Review defect (bug) new dev-feedback 2023-06-07T15:26:43Z 2023-06-09T22:08:13Z "Steps to reproduce:
1. Activate the Twenty Seventeen theme
2. Add the Site Logo block to any page or post and add an image
3. Make sure link to home setting is toggled on
4. Save and view on front end
" nkeller15
Needs Patch 58473 The menu messages rework Menus normal minor Awaiting Review enhancement new 2023-06-07T06:49:51Z 2023-06-27T11:41:41Z "Compared to the page message after a page has been created or updated, the menu messages can be reworked
1. When a menu has been created, there is no message shown.[https://imgur.com/iBoAUDB]
2. When the menu has been saved, the message can be reworked. [https://imgur.com/4Dz1oDE]
This can be similar to the Pages created, updated message" 254volkan
Needs Patch 58470 Add configurable batching to `wp_scheduled_delete` for controlling cleanup operations Cron API 6.3 normal normal Awaiting Review enhancement new 2023-06-06T22:08:46Z 2023-06-07T14:17:17Z "When posts are trashed, they are automatically cleaned up by the `wp_scheduled_delete` wp-cron task. However, both the frequency that this cron task runs and the number of posts that can be cleaned up at once time lack configurability.
Imagine a shop which has more than 100,000 orders: trashing thousands or tens of thousands of them at once could cause the website to become unresponsive when it comes time to clean up the trash.
I suggest adding two constants:
||= Constant Name =||= Default Value =||= Description =||
|| `EMPTY_TRASH_SCHEDULE` || `daily` || The cron schedule on which the trash scheduler runs. This is useful for increasing the number of times the cleanup process runs when using batching to delete many posts. ||
|| `EMPTY_TRASH_BATCH_SIZE` || `50` || The maximum number of posts to delete at once. ||
It may also be useful for these and `EMPTY_TRASH_DAYS` to have filters to improve cleanup operations overall." johnrom
Needs Patch 58469 Changeset 55832 broke shortcodes saved in block attributes and rendered serverside Shortcodes 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-06T21:31:53Z 2023-06-07T16:29:15Z "simply put, if a shortcode is saved to a block attribute and rendered as part of its `render_callback`, it no longer parses the shortcode as `do_shortcode` is now called before `do_blocks`
see [55832]" brumack
Changes Requested 58455 The admin menu remains sticky when displaying warning or error messages on the Site Health page. audrasjb Administration normal normal Future Release defect (bug) reviewing changes-requested 2023-06-05T12:15:55Z 2024-02-20T09:54:47Z "Improper Sticky Behavior of Admin Menu when displaying warning or error messages on the Site Health page.
Refrance: https://www.loom.com/share/3565aaf2d04e4b0b87dee361ee8335bb" dhrumilk
Needs Patch 58452 Add text-wrap: balance to theme styles Bundled Theme 6.2.2 normal normal Future Release enhancement new 2023-06-04T07:21:40Z 2024-02-21T12:59:39Z "Chrome 114 has introduced ""text-wrap:balance"" for CSS.
The importance of it is explained in: https://developer.chrome.com/en/blog/new-in-chrome-114/
This helps in displaying content more evenly and often required for headings such as site title and description below it.
So WordPress themes should have it.
" superpoincare
Needs Patch 58450 WP_Comment_Query status argument documentation misses any Comments normal normal Awaiting Review defect (bug) new 2023-06-03T15:50:16Z 2023-06-03T15:50:16Z "In the code, there is a comment that reads 'any' overrides other statuses.
'all', if I read correctly, would not cover 'spam' or 'trash'.
So, the documentation should be amended." dshanske
Needs Patch 58448 inconsistency in the $items parameter to the handle_bulk_actions-{$screen} action Administration normal normal Awaiting Review enhancement new 2023-06-03T00:54:37Z 2023-06-03T00:54:37Z "The [https://developer.wordpress.org/reference/hooks/handle_bulk_actions-screen/ handle_bulk_actions-{$screen}] action is fired when custom bulk actions are applied on various screens that have list tables.
On `/wp-admin/plugins.php`, `$items` is an array of plugin paths relative to `WP_PLUGINS_DIR` (e.g., `classic-editor/classic-editor.php`).
On all the other screens, the `$items` parameter passed to the action's callback is an array of IDs (e.g., post IDs, term IDs, comment IDs, etc). The inconsistency this ticket is about that on some screens the IDs in `$items` are ints and on other screens they are strings.
Specifically, `/wp-admin/edit.php` (Posts list table), `/wp-admin/upload.php` (Media list table), and `/wp-admin/edit-comments.php` (Comments list table), the IDs are cast to ints via something like `array_map( 'intval', (array) $post_ids )` before `handle_bulk_actions-{$screen}` is fired.
However, on all the other screens (`/wp-admin/edit-tags.php`, `/wp-admin-link-manager.php` (Links list table), and `/wp-admin/users.php`) the IDs are strings.
I think it would be easier on developers (e.g., plugin authors) if when `$items` is an array of IDs, all IDs were ints.
I don't know if this case be changed at this stage due to BC considerations. But if it can be, I'd be happy to add a patch to that effect." pbiron
Needs Patch 58447 Posts with ‘Stick to the top of the blog’ should also stick to the top of the categories it belongs to Posts, Post Types 6.2.2 normal normal Awaiting Review feature request new 2023-06-02T18:38:43Z 2023-11-20T17:35:19Z "According to the WordPress documentation ‘Stick to the top of the blog’ seems to be designed to only stick to the top of the front page.
I don't think that makes sense. It should also stick to the top of the categories it belongs to! At least the main category. " hero2
Needs Patch 58446 Twenty Fourteen: no space between Buttons block and Columns block on front end Bundled Theme 5.9 normal normal Awaiting Review defect (bug) new 2023-06-02T18:30:51Z 2023-07-07T19:09:01Z "Follow the Steps to reproduce the issue.
1. Activate the Twenty-Fourteen theme.
2. Choose a Button and a column block.
3. Add some text.
4. Apply to customize styles
5. Now check it on the user side.
It is looking proper in the editor but having issues on the user side.
I have attached a video for better understanding.
Video Link:
[https://www.loom.com/share/48f0cb53627a4448a9133595fb0e54ff]
" algorithmsunlocks
Has Patch / Needs Testing 58442 Add parameters for the wp_get_archive function that allows to filter the archive for particular years and months. General normal normal Awaiting Review enhancement new has-patch 2023-06-02T09:00:49Z 2023-06-06T07:49:00Z "Right now there is no way to get the monthly archive for particular year
{{{#!php
prepare( ""WHERE post_type = %s AND post_status = 'publish'"", $parsed_args['post_type'] );
}}}
In order to do that we have to use the filter to change the where clause as below.
{{{#!php
significant image color problems Media normal normal Awaiting Review enhancement new 2023-05-31T17:10:59Z 2023-06-14T14:03:00Z "If you upload a JPG with an embedded profile (such as P3 or some other wide gamut), the reprocessed image in the media library is stripped of its color profile. This is likely to result in significant display errors for any image not encoded as sRGB, including: desaturation, clipping of gradients or vibrant colors, and hue shifts.
Tested with WP v6.2.2 and PHP v7.4.33
" gregbenz
Has Patch / Needs Testing 58433 WP version in Etag header in load-styles.php file General normal normal Awaiting Review enhancement new has-patch 2023-05-31T11:16:13Z 2023-06-19T00:44:33Z "Hi
I know there are plenty of plugins to hide WP version. You also decided to hide WP version from readme.html some time ago. When the user uses all possible methods to hide WP version, current version still can be checked by load-styles.php and load-scripts.php files. It is visible in eTag header.
I know, this is not a big issue but I think is worth considering to use here some hash or checksum.
Regards
Dawid " dav4
Needs Patch 58432 "BUG: Custom Core Block Variation details not updated in ""Settings Sidebar"" section" Editor normal major Awaiting Review defect (bug) new 2023-05-31T06:10:30Z 2023-06-13T16:31:52Z "**Issue:**
When adding a custom **core block variation**, the details ( title, icon, description ) are not updated in the **""Settings Sidebar""** section. Hence there is no way to distinguish between custom core block **variations** and core **blocks** once a block is added.
**How to reproduce:**
1. Add support for block variations to your existing theme.
{{{
function prefix_editor_assets() {
wp_enqueue_script(
'prefix-block-variations',
get_template_directory_uri() . '/assets/js/blocks/block-variations.js',
array( 'wp-blocks' )
);
}
add_action( 'enqueue_block_editor_assets', 'prefix_editor_assets' );
}}}
2. Create a custom **core block variation**
{{{
wp.blocks.registerBlockVariation(
'core/group',
{
name: 'card-group',
title: 'Card group',
description: 'A group with card styling',
label: 'Card group',
icon: 'wordpress',
attributes: {
className: 'card-group',
},
innerBlocks: [
[ 'core/heading', { content: '' } ],
[ 'core/paragraph', { content: '' } ],
]
}
);
}}}
3. Check inside editor for new core block variation.
4. Add new core block variation and check the siderbar with the block selected.
Attaching pic & screen recording of the issue as well.
Note: I used the following tutorial by **Carolina Nymark** to create the variation
https://fullsiteediting.com/lessons/block-variations/
" deepakvijayan
Needs Dev / Bug Wrangler Feedback 58427 Retain existing user session when changing password Users 4.0 normal normal Awaiting Review defect (bug) new dev-feedback 2023-05-30T03:59:13Z 2023-05-30T04:45:30Z "When a user changes their password, their existing user session is ignored and a new session is started.
This happens due to `wp_update_user()` not passing the current session token to `wp_set_auth_cookie()`.
https://github.com/WordPress/wordpress-develop/blob/e82251df5bd59fb4327d0b0aa7a57ade20fe97c2/src/wp-includes/user.php#L2717-L2735
This can cause problems for some plugins which use the `attach_session_information` hook, or, which add additional information to the current session through `WP_Session_Manager::update()`.
Other issues that occur is when the password is updated through the rest api, is that a new session will be created, but the response (and rest of the rest api processing) will be operating with the old session token, as that's what's set in `$_COOKIE`. So if any user fields in the rest-api response are reliant upon a piece of session metadata, it'll be incorrect for the following HTTP requests from the user.
The workaround for plugins is to hook to `attach_session_information` and when a new session is being created for the current user, copy the current sessions metadata over to the new session. This is less than ideal, as it's not clear that the new session is definitely the same as the clients session (ie. The newly created session might not come from `wp_set_auth_cookie()` and might be a new session created for another purpose).
PR attached, which retains the existing session when changing the password. " dd32
Needs Reporter Feedback / Steps To Reproduce 58419 Changing categories Taxonomy 6.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-05-29T03:10:19Z 2023-05-29T13:18:49Z "I have a post with a file in category A.
I add category B to the post so the post now should show in both category A & B.
The post moves and now shows in A & B but the wrong file is displayed in B.
I did a ""Replace"" and the file is now correct in both places." jgostl
Needs Docs or Unit Tests 58416 Media Title field should soft wrap in Media Modal: For better readability/editing of long titles. Media 3.5 normal normal Awaiting Review enhancement new needs-unit-tests 2023-05-26T20:48:37Z 2023-06-13T11:08:12Z "**Usability Issue:**
- In the **Media Modal** the **Title** field currently is an `` and as such is single line only.
- Scrolling a ~50 character long title within a ~20 char text field sucks.
- Soft wrapping would really benefit longer media titles in terms of instant readability and easy editing.
**Solution Approaches:**
1. Leaving it a `` and tweak it to soft wrapping with CSS only.
- I found the [https://stackoverflow.com/questions/5286663/wrapping-text-inside-input-type-text-element-html-css exact same request on StackOverflow] for HTML in general (CMS agnostic)
- Pure [https://stackoverflow.com/a/31814539/199400 CSS solutions for this] which once worked, became unsupported around 2016 in major browsers.
- Bottom line: `` is single line only and always, user agents allow no circumventions.
2. Alternative approach: Use a `