__group__ ticket summary reporter component _version priority severity milestone type _status workflow _created modified _description _reporter Last Week 60818 Typo in wp-admin/includes/class-pclzip.php nithins53 General normal trivial 6.6 defect (bug) new commit 2024-03-21T12:33:40Z 2024-03-21T15:14:14Z "If we go through wp-admin/includes/class-pclzip.php on line number 51 we can see it is mentioned "" reserved for **''futur''** use "". It should be ""reserved for ''**future**'' use""" nithins53 Last Week 60814 several typo corrections in formatting.php file shailu25 Formatting normal trivial 6.6 defect (bug) accepted commit 2024-03-20T17:06:23Z 2024-03-20T17:36:50Z "several typo corrections in wp-includes/formatting.php file inline comments `parethesis` -> `parenthesis` `paretheses` -> `parentheses` `puctuation` -> `punctuation`" shailu25 Old Tickets 60650 sanitize_locale_name() should reject non-strings dd32 I18N 6.2.1 lowest trivial Awaiting Review defect (bug) new 2024-02-28T05:46:20Z 2024-02-28T09:53:14Z "While debugging some locale-related oddities, I ran into `sanitize_locale_name()` happily accepting arrays. {{{ wp> sanitize_locale_name( [ 'test@test' => 'test@test' ] ); array(1) { 'test@test' => string(8) ""testtest"" } }}} This is not uncommon for WordPress functions that rely upon `preg_replace()` and a number of other sanitize functions behave similarly. I would expect an array input to return either `''` as `array( .. )` is not a valid string." dd32 Old Tickets 60646 Docs: Incorrect return type specified for get_post_custom with negative post ID value roytanck Posts, Post Types 5.8 normal trivial Future Release defect (bug) new has-patch 2024-02-27T15:11:58Z 2024-03-08T12:03:04Z "On the documentation page for `get_post_custom`, the return type section says: ""False for an invalid $post_id (non-numeric, zero, or negative value)."" https://developer.wordpress.org/reference/functions/get_post_custom/ However, the function applies `absint` to the `$post_id`. So if its value would be negative (i.e. -10), this would be converted a positive value (10), and `get_post_meta` would be called for that post. This post ID can then either exists (resulting in an array being returned) or not (empty string). Perhaps a negative numerical value should not converted? There's a potential for mix-ups? If we keep the code as is, the docs should probably specify that negative values are converted to positive." roytanck Old Tickets 60565 download_url() returns inaccurate error message on missing URL argument hinnerk HTTP API 6.4.3 normal trivial 6.6 enhancement reviewing has-patch 2024-02-16T20:53:37Z 2024-02-19T19:48:29Z "Expected: {{{#!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 Old Tickets 60732 Update old document URLs to new ones mkismy General normal minor 6.6 enhancement accepted has-patch 2024-03-08T15:53:24Z 2024-03-20T11:17:56Z "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 Old Tickets 60729 YouTube embed start= chrdre 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 Old Tickets 60721 redirect_canonical suddenly causes issues with paramter values and CDN retrovertigo 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 Old Tickets 60668 Missing translation in login_header() first parameter juliobox Login and Registration 2.1 normal minor 6.6 enhancement accepted has-patch 2024-03-01T10:22:14Z 2024-03-02T09:19:02Z "Hey there Actuel code from WP (wp-login.php): {{{#!php Typography > Font > Manage Font : While fetching the the fonts, the loader is not alight in the centre. It should have equal top bottom spacing. krupajnanda Editor normal minor Awaiting Review defect (bug) new 2024-02-23T06:06:15Z 2024-02-27T05:35:40Z "== Bug Report === Description I believe the loader that appears should have equal spacing from top to bottom. === Environment - WordPress: 6.5-beta2 - PHP: 8.0.30-dev - Server: PHP.wasm - Database: WP_SQLite_Translator (Server: 5.5 / Client: 3.40.1) - Browser: Chrome 121.0.0.0 - OS: macOS - Theme: Twenty Twenty-Four 1.0 - MU Plugins: * 0-playground.php * 0-sqlite.php * WordPress WXZ Exporter 0.1 - Plugins: * Create Block Theme 1.13.8 * Debug Bar 1.1.4 * Health Check & Troubleshooting 1.7.0 * Test Reports 1.1.0 * User Switching 1.7.3 * WordPress Importer Git loader 0.8.2 === Steps to Reproduce 1. Go to Themes > Editor 2. Click on any heading or paragraph 3. Now, open a style 4. Click on Typography 5. Click on Font > Manage Fonts icon 6. Now, observe the loader appearing here which does not equal spacing from top-bottom. === Expected Results 1. ✅ IMO it should be centre-aligned. === Actual Results 1. ❌ Uneven top-bottom spacing. === Supplemental Artifacts Add as Attachments" krupajnanda Old Tickets 60581 Redundant variable type check david.binda Shortcodes trunk normal minor 6.6 enhancement new has-patch 2024-02-20T14:07:32Z 2024-02-20T14:13:38Z After the r57597, which is ensuring that the return type of the `shortcode_parse_atts` function is always an array, the `is_array` check in [https://core.trac.wordpress.org/browser/trunk/src/wp-includes/media.php?rev=57597#L5068 get_post_galleries] function is, IMHO, no longer needed. david.binda Old Tickets 60579 Notice: Undefined index: name in /wp-includes/class-wp-roles.php on line 293 mrsize General 6.4.3 normal minor Awaiting Review defect (bug) new has-patch 2024-02-20T09:56:44Z 2024-02-21T10:26:47Z "[[Image(http://servtest.ovh/notice-wp.jpg)]] I have some notices on my dashboard, and fix the bug by modifying the function in core file, line 279 : {{{#!php roles ) ) { return; } $this->role_objects = array(); $this->role_names = array(); foreach ( array_keys( $this->roles ) as $role ) { // Vérifier si 'name' est défini pour le rôle actuel if ( isset( $this->roles[ $role ]['name'] ) ) { $this->role_objects[ $role ] = new WP_Role( $role, $this->roles[ $role ]['capabilities'] ); $this->role_names[ $role ] = $this->roles[ $role ]['name']; } else { // Gérer le cas où 'name' n'est pas défini (éventuellement définir une valeur par défaut) $this->role_objects[ $role ] = new WP_Role( $role, $this->roles[ $role ]['capabilities'] ); $this->role_names[ $role ] = 'Nom par défaut'; } } /** * Fires after the roles have been initialized, allowing plugins to add their own roles. * * @since 4.7.0 * * @param WP_Roles $wp_roles A reference to the WP_Roles object. */ do_action( 'wp_roles_init', $this ); } }}} " mrsize Old Tickets 60572 block_core_navigation_render_inner_blocks loses caret for parent items anaid General 6.4.3 normal minor Awaiting Review defect (bug) new 2024-02-19T12:18:58Z 2024-02-25T10:35:35Z "When we build a menu via the blocks editor the regular way, and create a parent menu items with a submenu, the parent menu item is (somehow) marked as a parent. It receives a caret automatically in Twenty Twenty Four theme. When programmatically creating a menu via `block_core_navigation_render_inner_blocks`, the parent-child relationship is not marked automatically. There is no dropdown caret in the parent menu item. Reproduction scenario: - Twenty Twenty Four theme - Go to Editor and manually create Navigation - Parent item ""Post A"" - Add a submenu - Child item ""Post B"" - View the website. Post A is parent, has a dropdown caret and Post B is below it Now, do it programmatically via block_core_navigation_render_inner_blocks: {{{ function block_core_navigation_render_inner_blocks($items) { return new WP_Block_List(array( new WP_Block([ 'blockName' => 'core/navigation-link', 'attrs' => [""label"" => ""Post A""], 'innerBlocks' => array(new WP_Block([ 'blockName' => 'core/navigation-link', 'attrs' => [""label"" => ""Post B""], 'innerBlocks' => [], 'innerHTML' => '', 'innerContent' => [], ])), 'innerHTML' => '', 'innerContent' => [], ]) )); } }}} View the website. There is no dropdown caret applied to the parent post (Post A)" anaid Old Tickets 60519 Link widget always displays rating xurxodiz Widgets 6.4.3 normal minor Awaiting Review defect (bug) new 2024-02-13T02:19:47Z 2024-02-13T11:25:56Z "Using the latest WP version, when you add links through the Link Manager and use a Widget to display them in e.g. a sidebar, the links always show the rating regardless of the widget setting ""Show rating"" being unchecked. You can test it simply by creating a link, adding it to a link widget and placing it in a widget area. I've traced the problem to a gap in logic in the 'update' function of /wp-includes/widgets/class-wp-widget-links.php 'rating' setting is not taken care of when updating the instance settings, so it is always set to 1 as default during $instance array update. It can be fixed by adding the following line after line 114: {{{#!php $instance['rating'] = ! empty( $new_instance['rating'] ) ? (int) $new_instance['rating'] : 0; }}} Same as it is done in line 114 for 'limit' setting. Thanks." xurxodiz Old Tickets 60468 "WP_Query matches any post when query parameter ""name"" is an empty string" miyarakira Query normal minor Awaiting Review defect (bug) new 2024-02-07T17:25:07Z 2024-02-07T17:25:07Z "`WP_Query` matches any post when query parameter `name` is an empty string. For example: {{{ $query = new WP_Query([ 'name' => '', 'post_type' => 'post', 'posts_per_page' => 1, ]); var_dump($query->posts); }}} The same is true for `get_posts()` which uses `WP_Query` internally. This might be the intended behavior, but it's unintuitive and surprising. It can (did) cause a bug in user code that expects such a query to return no results." miyarakira Old Tickets 60429 Deprecated: Implicit conversion from float to int loses precision retrovertigo I18N normal minor Awaiting Review defect (bug) new 2024-02-03T02:42:48Z 2024-03-07T09:10:41Z "**Describe the bug** Running WordPress 6.4.3 this PHP warning comes up: {{{ Deprecated: Implicit conversion from float 4294967295 to int loses precision in /var/www/html/wp-includes/pomo/mo.php on line 208 }}} **To Reproduce** 1. Run WordPress 6.4.3 2. Switch on WP_DEBUG and WP_DEBUG_DISPLAY 3. Load the site 4. See warning printed out See https://github.com/LeoColomb/pomo/issues/16 for a screenshot. " retrovertigo Old Tickets 60427 "small ""ü"" in page as anchor causes a mistake when try to save (wrong JSON-response)" gregordoehnert Posts, Post Types 6.4.3 normal minor Awaiting Review defect (bug) assigned 2024-02-02T19:00:04Z 2024-02-02T19:00:04Z "I tried to make some changes on a page with pre-block content. It contains some anchors and everytime I tried to save the page after some small changes I got the alert ""Aktualisierung fehlgeschlagen. Die Antwort ist keine gültige JSON-Antwort."". The well know answer that there is something wrong with JSON. I found the reason is that in the anchors where small ""ü"" (a german umlaut). It happened with the anchor target as well as with the anchor link. And at the same time there are some anchors with other umlauts, namely with a big ""Ü"", which do not cause the issue." gregordoehnert Old Tickets 60370 Test Tools: Clarifying reusable workflows in Github CI youknowriad Build/Test Tools normal minor Awaiting Review enhancement new 2024-01-29T12:59:58Z 2024-01-29T13:00:51Z "While working on https://github.com/WordPress/wordpress-develop/pull/5922 we had to increase the timeout limit for one of the reusable workflows of the repository: phpunit-tests-run.yml The problem is that the update were not being taken into consideration in the PR because we explicitly refer to the ""trunk"" version of that workflow in `phpunit-tests.yml` Github does offer a way to use relative links to other workflows from the same repository (instead of URLs), ti would have solved the issue there but it comes with a set of tradeoffs that need to be considered. For example, updating Node.JS version in the reusable workflow would need to be done for all the previous branches that WP still supports while forcing the use of the ""trunk"" workflow means we can update in a single place. The initial discussion about this happened on the following Slack Thread https://wordpress.slack.com/archives/C02RQBWTW/p1706523051675219 I'm opening this ticket so we can track this discussion and potentially address it (or not). " youknowriad Yesterday 60855 wp_mkdir_p can error when simultaneous requests attempt to create the same directory grantmkin General normal normal Awaiting Review defect (bug) new 2024-03-27T18:54:56Z 2024-03-27T18:54:56Z "When two requests happen at the same time that both attempt to create a new directory with `wp_mkdir_p`, a race condition can occur that results in one request creating the directory and the other triggering an error. The issue happens when both of the requests reach the `file_exists` check at nearly the same time: https://github.com/WordPress/wordpress-develop/blob/e73db80196c0044503633bda41511258a9516a8b/src/wp-includes/functions.php#L2059 The directory does not exist yet, so the check fails and both requests continue execution of the function. Then the requests are in a race to get to the code where the directory is actually created using `mkdir`: https://github.com/WordPress/wordpress-develop/blob/e73db80196c0044503633bda41511258a9516a8b/src/wp-includes/functions.php#L2082 The first request to reach that point will successfully create the directory and return true, the second will return false when `mkdir` fails because the directory already exists. This causes an error upstream in the code because `wp_mkdir_p` is expected to return true when the directory already exists. Found when testing the font library on new installs, see https://github.com/WordPress/gutenberg/issues/59023#issuecomment-2022746082" grantmkin Yesterday 60854 Block Hooks: Allow insertion as first or last child of Template Part block Bernhard Reiter General normal normal Future Release enhancement new 2024-03-27T17:11:00Z 2024-03-27T17:11:00Z "In [https://github.com/WordPress/gutenberg/pull/57754 GB#57754], a mechanism was introduced to allow insertion of hooked blocks into the Navigation block, in particular as its `first_child` or `last_child`, thus fixing #59743. The latter was achieved by storing the `ignoredHookedBlocks` array in the corresponding `wp_navigation` post's post meta (instead of a `metadata` attribute on the anchor block). This technique could be applied to other blocks that fetch their inner blocks from a separate DB record (rather than having them stored inline); these are sometimes referred to as ""controlled inner blocks"". There might not be a large number of container blocks with controlled inner blocks into which we'd want to inject hooked blocks; however, there's at least one obvious example: The Template Part block. It's currently not possible to inject a hooked block as its first or last child. Note however that the code that inserts hooked blocks into the Navigation block's `wp_navigation` post objects currently lives in Gutenberg. Consequently, it's advisable to absorb that code into Core first (i.e. to fix #60759) before tackling this issue." Bernhard Reiter Yesterday 60853 Apostrophe is not displaying correct in German when using the Plugin WPML kasteelkevakanties I18N 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-27T16:31:55Z 2024-03-27T16:58:34Z "The apostrophe ' is not displaying correct in German using the WPML plugin. If you type the apostrophe (') it is not displayed at the top but instead it is at the bottom. This is not correct. I have contacted WPML for the issue, but they say that there is nothing they can do, because WordPress shows Apostrophes as per German standards on the front." kasteelkevakanties Yesterday 60852 Block Templates: Make conditional tags work when processing content for REST API Bernhard Reiter General normal normal Future Release feature request new 2024-03-27T16:26:53Z 2024-03-27T16:26:53Z "@ndiego brought up to me that it might be desirable to make [https://developer.wordpress.org/themes/basics/conditional-tags/ conditional tags] such as [https://developer.wordpress.org/reference/functions/is_singular/ `is_singlular`] or [https://developer.wordpress.org/reference/functions/is_user_logged_in/ `is_user_logged_in`] work in Block Hook related filters ([`hooked_block_types`](https://developer.wordpress.org/reference/hooks/hooked_block_types/), `hooked_block`, `hooked_block_{$hooked_block_type}`). These conditional tags will probably work on the frontend; the problem is that they ''won't'' work in the editor, which is why we it is not recommended to use them for hooked blocks, as they would produce a mismatch between what's in on the frontend and what's in the editor (e.g. a block that's conditionally hooked based on the return value of `is_singular` might correctly show up on the frontend, but not in the editor when rendering the single posts template). To fix this, we'd likely need to set the relevant information during processing of a block template's content that precedes sending it to the client via the REST API (i.e. probably somewhere inside of [https://developer.wordpress.org/reference/functions/get_block_template/ `get_block_template()`] and [https://developer.wordpress.org/reference/functions/get_block_templates/ `get_block_templates()`] or inside the functions that they call). In theory, the relevant information should be available, as the server knows which template(s) to respond with to a given request, and they are given as an argument (`$id` or `$query`, respectively) to the aforementioned functions. However, implementing the fix is probably still non-trivial for Template Hierarchy related conditional tags, as they all return values based on the global `$wp_query` object; we'd thus need to set properties on that global during block template processing, or extend all Template Hierarchy related conditional tags to account for this scenario. I'm not quite sure if this would benefit any code other than Block Hooks filters. Dynamic Blocks can largely use conditional tags already, since their PHP code is typically only run on the frontend, but not for populating the editor." Bernhard Reiter Yesterday 60851 Bulk edit and quickedit needs more space for longer translations zodiac1978 Quick/Bulk Edit 6.3 normal normal Awaiting Review enhancement new 2024-03-27T13:34:07Z 2024-03-27T13:34:07Z "In #25753 we introduced more space (5em was the default, we needed 7em) for `.locale-de-de .inline-edit-row fieldset label span.title` in the German locale. After that, #28303 added this change to the new formal locale `.locale-de-de-formal` But in #33212 this was removed again by @ocean90 and the new default was 6em. This wasn't enough for ru_RU which got 8em. In WordPress 6.2 the string ""Parent"" was translated with ""Eltern"" and for this 6em was okay: https://translate.wordpress.org/projects/wp/6.2.x/admin/de/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=16083988&filters%5Btranslation_id%5D=105887217 But in WordPress 6.3 this was changed to ""Übergeordnet"": https://translate.wordpress.org/projects/wp/6.3.x/de/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=16507337&filters%5Btranslation_id%5D=109126351 Now the translation is too long and 6em space is not sufficient anymore. Re-adding the 7em width would solve this issue again. There is also the same problem with the Polish locale which has a very long translation: https://translate.wordpress.org/projects/wp/dev/pl/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=16087645&filters%5Btranslation_id%5D=106835593" zodiac1978 Yesterday 60850 Localize script not working in WordPress 6.5-RC3-57856 dev28 Script Loader trunk normal normal Awaiting Review defect (bug) assigned close 2024-03-27T08:40:18Z 2024-03-27T08:54:21Z "During my testing of the plugin, I encountered an issue with the localized script while using the 6.5 beta version. Specifically, I noticed a JavaScript error that prevented the script from working as intended. However, I would like to clarify that this issue is not present in the current version, and the localized script works flawlessly without any errors. https://prnt.sc/zFevup7B2iU4 https://prnt.sc/YR0FXm_l__D9 **System info: ** ` ### wp-core ### version: 6.5-RC3-57856 site_language: en_US user_language: en_US timezone: +05:00 permalink: /%postname%/ https_status: false multisite: false user_registration: 0 blog_public: 0 default_comment_status: open environment_type: production user_count: 1 dotorg_communication: true ### wp-paths-sizes ### wordpress_path: /home/worldwebusers/phpdev3/public_html/wordpressbeta wordpress_size: 54.67 MB (57325890 bytes) uploads_path: /home/worldwebusers/phpdev3/public_html/wordpressbeta/wp-content/uploads uploads_size: 1.35 MB (1419920 bytes) themes_path: /home/worldwebusers/phpdev3/public_html/wordpressbeta/wp-content/themes themes_size: 36.91 MB (38701146 bytes) plugins_path: /home/worldwebusers/phpdev3/public_html/wordpressbeta/wp-content/plugins plugins_size: 6.99 MB (7332893 bytes) database_size: 2.75 MB (2883584 bytes) total_size: 102.68 MB (107663433 bytes) ### wp-active-theme ### name: Twenty Twenty-Four (twentytwentyfour) version: 1.0 author: the WordPress team author_website: https://wordpress.org parent_theme: none theme_features: core-block-patterns, post-thumbnails, responsive-embeds, editor-styles, html5, automatic-feed-links, widgets-block-editor, block-templates theme_path: /home/worldwebusers/phpdev3/public_html/wordpressbeta/wp-content/themes/twentytwentyfour auto_update: Disabled ### wp-themes-inactive (13) ### Twenty Eleven: version: 4.5, author: the WordPress team, Auto-updates disabled Twenty Fifteen: version: 3.6, author: the WordPress team, Auto-updates disabled Twenty Fourteen: version: 3.8, author: the WordPress team, Auto-updates disabled Twenty Nineteen: version: 2.7, author: the WordPress team, Auto-updates disabled Twenty Seventeen: version: 3.5, author: the WordPress team, Auto-updates disabled Twenty Sixteen: version: 3.1, author: the WordPress team, Auto-updates disabled Twenty Ten: version: 4.0, author: the WordPress team, Auto-updates disabled Twenty Thirteen: version: 4.0, author: the WordPress team, Auto-updates disabled Twenty Twelve: version: 4.1, author: the WordPress team, Auto-updates disabled Twenty Twenty: version: 2.5, author: the WordPress team, Auto-updates disabled Twenty Twenty-One: version: 2.1, author: the WordPress team, Auto-updates disabled Twenty Twenty-Three: version: 1.3, author: the WordPress team, Auto-updates disabled Twenty Twenty-Two: version: 1.6, author: the WordPress team, Auto-updates disabled ### wp-plugins-active (2) ### Loan Calculator WP: version: 1.2.3, author: World Web Technology, Auto-updates disabled Loan Calculator WP Pro: version: 1.0.0, author: World Web Technology, Auto-updates disabled ### wp-plugins-inactive (5) ### Akismet Anti-spam: Spam Protection: version: 5.3.2, author: Automattic - Anti-spam Team, Auto-updates disabled Classic Editor: version: 1.6.3, author: WordPress Contributors, Auto-updates disabled Hello Dolly: version: 1.7.2, author: Matt Mullenweg, Auto-updates disabled Reviews Sorted: version: 2.3.10, author: Reviews Sorted, Auto-updates disabled WP Custom Post Type Filter: version: 1.0.0, author: WWT, Auto-updates disabled ### wp-media ### image_editor: WP_Image_Editor_Imagick imagick_module_version: 1809 imagemagick_version: ImageMagick 7.1.1-29 Q16-HDRI x86_64 21991 https://imagemagick.org imagick_version: 3.7.0 file_uploads: 1 post_max_size: 512M upload_max_filesize: 512M max_effective_size: 512 MB max_file_uploads: 20 imagick_limits: imagick::RESOURCETYPE_AREA: 62 GB imagick::RESOURCETYPE_DISK: 9.2233720368548E+18 imagick::RESOURCETYPE_FILE: 768 imagick::RESOURCETYPE_MAP: 31 GB imagick::RESOURCETYPE_MEMORY: 16 GB imagick::RESOURCETYPE_THREAD: 1 imagick::RESOURCETYPE_TIME: 0 imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, ASHLAR, AVI, AVS, BAYER, BAYERA, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUBE, CUR, CUT, DATA, DCM, DCR, DCRAW, DCX, DDS, DFONT, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FARBFELD, FAX, FF, FILE, FITS, FL32, FLV, FRACTAL, FTP, FTS, FTXT, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, HALD, HDR, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, KERNEL, LABEL, M2V, M4V, MAC, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPEG, MPG, MPO, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORA, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PHM, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PS, PS2, PS3, PSB, PSD, PTIF, PWP, QOI, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGB565, RGBA, RGBO, RGF, RLA, RLE, RMF, RSVG, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, STRIMG, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TM2, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YAML, YCbCr, YCbCrA, YUV gd_version: 2.3.3 gd_formats: GIF, JPEG, PNG, WebP, BMP, AVIF, XPM ghostscript_version: 9.25 ### wp-server ### server_architecture: Linux 3.10.0-1160.114.2.el7.x86_64 x86_64 httpd_software: Apache/2.4.6 php_version: 8.1.27 64bit php_sapi: cgi-fcgi max_input_variables: 1500 time_limit: 300 memory_limit: -1 max_input_time: 600 upload_max_filesize: 512M php_post_max_size: 512M curl_version: 7.29.0 NSS/3.90 suhosin: false imagick_availability: true pretty_permalinks: true htaccess_extra_rules: false current: 2024-03-27T08:25:43+00:00 utc-time: Wednesday, 27-Mar-24 08:25:43 UTC server-time: 2024-03-27T13:25:38+05:00 ### wp-database ### extension: mysqli server_version: 5.7.36 client_version: mysqlnd 8.1.27 max_allowed_packet: 1073741824 max_connections: 151 ### wp-constants ### WP_HOME: undefined WP_SITEURL: undefined WP_CONTENT_DIR: /home/worldwebusers/phpdev3/public_html/wordpressbeta/wp-content WP_PLUGIN_DIR: /home/worldwebusers/phpdev3/public_html/wordpressbeta/wp-content/plugins WP_MEMORY_LIMIT: 2048M WP_MAX_MEMORY_LIMIT: -1 WP_DEBUG: false WP_DEBUG_DISPLAY: false WP_DEBUG_LOG: false SCRIPT_DEBUG: false WP_CACHE: false CONCATENATE_SCRIPTS: undefined COMPRESS_SCRIPTS: undefined COMPRESS_CSS: undefined WP_ENVIRONMENT_TYPE: Undefined WP_DEVELOPMENT_MODE: undefined DB_CHARSET: utf8 DB_COLLATE: undefined ### wp-filesystem ### wordpress: writable wp-content: writable uploads: writable plugins: writable themes: writable `" dev28 Yesterday 60849 Meta is saved twice in auto-draft mode 79mplus General normal normal Awaiting Review defect (bug) new has-patch 2024-03-27T06:02:24Z 2024-03-28T02:35:17Z "Steps to reproduce the bug: 1. Go to Add new page for any post type. 2. Add the first custom field (can be new or existing) » Click Add Custom Field 3. Add a second custom field (can be new or existing) » optionally click Add Custom Field 4. Click Save/Update. 5. Notice that the first custom field entered has been saved twice. " 79mplus Yesterday 60847 Style Engine: continue get_classnames loop after adding the default classname ramonopoly Editor trunk normal normal Awaiting Review enhancement new has-patch 2024-03-27T00:23:59Z 2024-03-27T00:24:16Z "The `WP_Style_Engine` class has a method get_classnames that builds classnames. It loops over an array to add each classname. There should be a `continue` in the loop after adding the default classname. Syncs changes from: https://github.com/WordPress/gutenberg/pull/60153 **Why?** Because we've added the first classname by virtue of testing for `true`. The following tests all expect a string: `get_slug_from_preset_value` only works on a string, not a boolean." ramonopoly 2 Days Ago 60846 When creating a new template, the Choose a pattern screen doesn't honor the `template_hierarchy` filter aljullu Editor 6.1 normal normal Future Release defect (bug) new has-patch 2024-03-26T12:49:19Z 2024-03-26T17:43:46Z "Currently, in blocks themes it's possible to use the {{{${type}_template_hierarchy}}} filter to alter the template hierarchy. However, those filters are not taken into consideration by the `Choose a pattern` popup screen that appears when creating a new template in the Site Editor, causing a mismatch between the editor and the frontend. **Steps to reproduce** 1. Add this code snippet to your site. You can use the [https://wordpress.org/plugins/code-snippets/ Code Snippets plugin]: {{{#!php Editor > Templates > Add New Template > Pages and select any page. 4. Notice in the Choose a pattern screen the suggested content to start with is from the Page template, instead of the Single template. Expected result: the Site Editor should follow the filter in the same way the frontend does. So in step 4 the Single template should appear in the Choose a pattern screen, instead of the Page template. **Actual result screenshot** [[Image(https://github.com/WordPress/gutenberg/assets/3616980/7598c990-1a64-4df3-b509-47d83fc59239)]] **Expected result screenshot** [[Image(https://github.com/WordPress/gutenberg/assets/3616980/fff09fd9-5600-4969-89f6-dab6523f50de)]] **Real life use case** In WooCommerce, there are Product Category and Product Tag templates. Currently, they fall back to the default WordPress taxonomy templates, but we would like them to fall back to a custom WooCommerce template named Product Catalog. While this would work in the frontend, the experience would be confusing in the editor, as creating a Product Category archive template wouldn't suggest the same ""starting point"" from what's seen in the frontend." aljullu 3 Days Ago 60842 PHPunit tests for wp_check_invalid_utf8 pbearne Build/Test Tools normal normal Awaiting Review defect (bug) new 2024-03-25T20:25:12Z 2024-03-25T20:25:12Z pbearne 3 Days Ago 60841 Create token lookup class. dmsnell General trunk normal normal Awaiting Review feature request new has-patch 2024-03-25T17:13:32Z 2024-03-25T17:16:14Z "In the HTML API it would be nice to perform spec-compliant attribute encoding and decoding. This requires a divergence from current Core behavior; namely, to rely on the set of defined named character references rather than a list that has been combined over time. Specifically when parsing HTML character references I keep finding the need for two operations: - is this substring an HTML character reference? - what, if any, is the next character reference in this string at this offset? For the first question it's possible to use `in_array( $substring, $character_reference_names, true )`, even though this may not be optimal. It's a reasonable first step. For the second question I'm unaware of a strong implementation available in PHP or WordPress. The change motivating this is moving from //split a string into potential character references and non-character-reference contents and then check if each one is valid// and towards a single-pass parser that is less likely to be confused by strings that are almost character references. There is a potential for improving the speed of handling character references, but it is not a driving goal. {{{#!php read_token( $html, $at ); if ( false !== $name ) { $decoded .= substr( $html, $was_at, $was_at - $at ) . entity_lookup( 'attribute', $name ); $at += strlen( $name ); } else { ++$at; } }}} https://github.com/WordPress/wordpress-develop/pull/5337/files#diff-e2bc0d3d983191acdb2effe67311dc37666eae53d59983281b34a7b4eed238acR1124-R1163 A final need involves mapping a token to a value, but this may be best relegated to another class or application code. For example, mapping from named character reference to UTF-8 bytes representing the corresponding Code Point. ---- My proposal is adding a new class `WP_Token_Set` providing at least two methods for normal use: - `contains( $token )` returns whether the passed string is in the set. - `read_token( $text, $offset = 0 )` indicates if the character sequence starting at the given offset in the passed string forms a token in the set, and if so, returns the longest matching sequence. It also provides utility functions for pre-computing these classes, as they are designed for relatively-static cases where the actual code is intended to be generated dynamically, but stay static over time. For example, HTML5 defines the set of named character references and indicates that the list //shall not// change or be expanded. [https://html.spec.whatwg.org/#named-character-references-table HTML5 spec] - `static::from_array( array $words )` generates a new token set from the given array of tokens. - `to_array()` dumps the set of tokens into an array of string tokens. - `static::from_precomputed_table( $table )` instantiates a token set from a precomputed table, skipping the computation for building the table and sorting the tokens. - `precomputed_php_source_table()` generates PHP source code which can be loaded with the previous static method for maintenance of the core static token sets. ---- Having a semantic class for this work provides an opportunity to optimize lookup without demanding that the user-space (or Core-space) code change. There are more methods that could be useful but which aren't included in the proposal because they haven't been necessary: - `add( $token )` and `remove( $token )` for dynamically altering the table. Also, this is currently limited to store tokens of byte-length <= 256 for practical implementation details (it has not been necessary to store longer tokens). ## How can I provide feedback? I'm happy to do all the work of documenting the class, adding tests, and cleaning up the code for inclusion. What I'd appreciate from you is feedback on the idea, the naming of the class and the methods, whether you have considered other ideas similar to this before, feedback on the general approach taken in the linked PRs. Thank you all." dmsnell 3 Days Ago 60840 Composer: update to WordPressCS 3.1.0 jrf Build/Test Tools trunk normal normal 6.6 task (blessed) new 2024-03-25T16:58:01Z 2024-03-25T17:07:33Z "WordPressCS 3.1.0 has just been released and is fully prepared for the WP 6.5 release. It is recommended for WP Core to update as soon as convenient. The impact on existing Core code is expected to be low to non-existent, but the release does provide more safeguards for the future. Refs: * https://github.com/WordPress/WordPress-Coding-Standards/releases/tag/3.1.0 * https://github.com/WordPress/WordPress-Coding-Standards/compare/3.0.1...3.1.0 Previous: #59161 Props: @garyj, @dingo_d, @rodrigosprimo, @chouby, @westonruter @bjorsch" jrf 3 Days Ago 60839 WordPress issue > WordPress 6.5 RC3 and 6.4.3, crop feature not working: Invalid Paramter vivekawsm General 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-25T11:12:30Z 2024-03-25T11:12:30Z "Description The crop feature is not working and showing error when clicking on the apply option. Issue existing on both WordPress 6.5 RC3 and 6.4.3. === Environment - WordPress: 6.5-RC3-57872 - PHP: 8.0.30 - Server: TasteWP-S4 Official/3.0.0 - Database: mysqli (Server: 8.0.32-0ubuntu0.20.04.2 / Client: mysqlnd 8.0.30) - Browser: Firefox 123.0 (Windows 10/11) - Theme: Twenty Twenty-Four 1.0 - MU-Plugins: None activated - Plugins: * WordPress Beta Tester 3.5.5 === Expected Results Crop should work when clicked on the apply option === Actual Results Invalid Paramter error showing when clicked on the apply option Attach video url for reference : https://www.loom.com/share/2b35d8d654284820b67b031e9a8e6d4b" vivekawsm 4-7 Days Ago 60836 Static homepage display settings: the posts page is not being assigned to the Blog Home template or Index template west7 Themes trunk normal normal 6.5.1 defect (bug) new 2024-03-24T23:44:19Z 2024-03-25T11:10:20Z "When I use 6.5 Beta Tester plugin and change to static homepage display, Home and Blog, the blog page is assigned to the Pages template, not the Blog Home or Index template. I don't have any other plugins installed, only Beta Tester. I am using Local and tried both the Twenty Twenty-Two and Twenty Twenty-Four themes. The expected output when changing to static homepage display is that the posts page will be assigned to the Blog Home template or Index template. " west7 4-7 Days Ago 60835 Fix and improve handling of uploading of font files azaozz Upload normal normal 6.6 defect (bug) new 2024-03-24T20:04:05Z 2024-03-24T23:12:22Z "Follow up to #60652 and [57868]. As discussed at https://github.com/WordPress/wordpress-develop/pull/6211 the code that enables uploading of font files by replacing the output of `wp_handle_upload()` by using the `upload_dir` filter is not the best solution. In addition it implements nested filters that can be pretty confusing so understand and/or use for plugin and theme authors. A more straightforward solution is needed for this and similar cases in the future." azaozz 4-7 Days Ago 60834 separators do not always show on page lyleleverich Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2024-03-24T18:43:45Z 2024-03-25T08:09:52Z It appears that separators do not show when the page is viewed under some conditions. We suspect it is when a photo is loaded just above the separator after the page has been saved. Deleting the separator and replacing it does not work. Adding a paragraph between the separators and photo does not work. Only adding a second separator will result in a single separator to show on the viewed page. lyleleverich 4-7 Days Ago 60833 WordPress menu looks like a fail after update to 6.4.3 vizvizka Themes normal normal Awaiting Review defect (bug) new reporter-feedback 2024-03-24T17:52:17Z 2024-03-26T17:36:23Z After I updated WordPress, the menu looks very different and ugly on top right side. I tried to change the menu's appearance via block editor, I deleted the menu items and reenetered them. The same thing happens every time. Is it a bug or problem about my side? vizvizka 4-7 Days Ago 60832 add_meta_box breaks on plugin sub-pages if add_menu_page has dynamic title malcure Menus 6.4.3 normal normal Awaiting Review defect (bug) new has-patch 2024-03-24T06:31:45Z 2024-03-27T17:06:26Z "add_meta_box breaks on plugin sub-pages if add_menu_page has dynamic title. Poc and fix attached. The reason is that if the menu title is dynamic like 'My Plugin ' . $count . ''" malcure 4-7 Days Ago 60831 Investigate flakey `Tests_Admin_wpSiteHealth ::test_object_cache_thresholds()` test swissspidy Site Health normal normal Awaiting Review defect (bug) new 2024-03-23T11:33:04Z 2024-03-23T11:33:04Z "The following two tests / datasets ''sometimes'' fail for certain hosting providers: {{{ Tests_Admin_wpSiteHealth::test_object_cache_thresholds::test_object_cache_thresholds with data set #2 Tests_Admin_wpSiteHealth::test_object_cache_thresholds with data set #2 ('terms_count', 1) Failed asserting that false is true. /tmp/wp-test-runner/tests/phpunit/tests/admin/wpSiteHealth.php:482 Tests_Admin_wpSiteHealth::test_object_cache_thresholds::test_object_cache_thresholds with data set #3 Tests_Admin_wpSiteHealth::test_object_cache_thresholds with data set #3 ('options_count', 100) Failed asserting that false is true. /tmp/wp-test-runner/tests/phpunit/tests/admin/wpSiteHealth.php:482 }}} Example: https://make.wordpress.org/hosting/test-results/r57871/digitoimistodude-r57871/ Maybe these are just issues with that particular host, but perhaps there's also a opportunity to make the tests more robust. So let's try to look into it to find out more." swissspidy 4-7 Days Ago 60830 Advanced Editor Tools - SIMPLE SORT robtcyn Editor 5.9.2 normal normal Awaiting Review enhancement new 2024-03-22T22:22:40Z 2024-03-23T05:54:32Z "Under the Edit button, add SORT SELECTED TEXT. Here is an example of what I am trying to sort. I currently copy it to Libre Office, do a sort, then return it to the web page - which is: https://xml3.com/songs/songs-for-smaller-scale-ukuleles/ • Achy Breaky Heart • Banana Boat Song • Billy Boy • Hush Little Baby • It Ain’t Gonna Rain No More • Jambalaya (On the Bayou) • Skip to my Lou • Tom Dooley • Tulsa Time • Waltz Across Texas • You Never Can Tell • Born in the USA • Everyday People • Feelin Alright " robtcyn 4-7 Days Ago 60829 Improve shortcode support for link fields Code Muffin Editor normal normal Awaiting Review enhancement new 2024-03-22T16:55:25Z 2024-03-26T16:44:12Z "Using a shortcode in a link field currently prepends {{{http://}}} to the field. They still render on the frontend, but this makes them functionally unusable because the resulting href is always prepended by that {{{http://}}}. This is due to the JS function {{{correctURL}}} (in [https://github.com/WordPress/wordpress-develop/blob/4.4/src/wp-includes/js/wplink.js#L88 wp-includes/js/wplink.js]), which adds it if the URL does not start with {{{http:}}}, {{{https:}}}, {{{?}}} {{{#}}} or {{{/}}}. I suggest adding {{{[}}} to that list of allowed characters, so shortcodes can be used too." Code Muffin 4-7 Days Ago 60828 tests for wp_check_browser_version pbearne Build/Test Tools normal normal Awaiting Review defect (bug) new has-patch 2024-03-22T16:30:47Z 2024-03-22T16:38:00Z pbearne 4-7 Days Ago 60827 Patterns menu item, put back the context parameter. kebbet I18N trunk normal normal 6.5.1 defect (bug) reopened has-patch 2024-03-22T14:14:46Z 2024-03-27T22:44:53Z "This is a follow up for the next minor release, 6.5.1 and the previous ticket #60825 The commit message by @audrasjb in [57864] stated: `A follow-up changeset will be needed to replace the current __() function with _x() and put back the context parameter.` This is what should replace the call to `__()`: `_x( 'Patterns', 'site editor menu item' )`" kebbet 4-7 Days Ago 60826 Fix incorrect use of add_theme_support( 'editor-style(s)' ) Soean Themes normal normal Awaiting Review defect (bug) new has-patch 2024-03-22T12:13:58Z 2024-03-22T20:51:21Z "In the functions `add_editor_style()`, `remove_editor_styles()` and `remove_theme_support()` the Theme `$feature` parameter`editor-style` is used instead of `editor-styles`. It should be: `add_theme_support( 'editor-styles' );` See docs: https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-support/#editor-styles See code docs: https://github.com/WordPress/wordpress-develop/blob/8d0aed455b1790c5d51386f7675d9e8d68e48edf/src/wp-includes/theme.php#L2672" Soean 4-7 Days Ago 60824 Add filters to to wp_verify_nonce() tymotey Security trunk normal normal Awaiting Review enhancement new has-patch 2024-03-22T06:32:01Z 2024-03-22T10:01:55Z "Allow a more customizable way to interact with wp_verify_nonce(). Improvements are meant to allow plugins to be able to modify/log the nonce sent, also allowing easy control on the return value in each situation(verify 1, verify 2, nonce failed to verify)." tymotey Last Week 60822 Fix Docker environment for ARM devices in WP <= 6.3 desrosj Build/Test Tools normal normal 6.6 defect (bug) new has-patch 2024-03-21T19:28:02Z 2024-03-21T19:28:31Z "Follow up to #59930. The MySQL Docker containers for versions 5.7 and below do not support recent Apple silicone chips. Previously this was fixed by including `amd64/` as a prefix to the image name in the `docker-compose.yml` file (see [54096]). However, this stopped working after recent updates to Docker Desktop. In `trunk` and 6.4/6.5 branches, [57568] fixed the issue by bumping the default version of MySQL to 8.0 and removed the `amd64/` prefix. Since raising that default version is not a good solution for older branches, a different one needs to be committed to 6.3 and backported. A [https://github.com/WordPress/wordpress-develop/pull/5843 PR on GitHub is open with the proposed fix for the older branches]." desrosj Last Week 60820 Improve wording of the 'Login Details' mail pixelverbieger Text Changes normal normal Awaiting Review enhancement assigned reporter-feedback 2024-03-21T15:26:56Z 2024-03-22T11:15:38Z "When creating a new user (as admin), they receive a very short e-mail in which a user name and a link are simply sent without comment. I would like the text of this e-mail to be a little more informative. The password reset emails are a good example. There we write ""Someone has requested a password reset for the following account"", state the site name, the user name and then write the link. The text of the login detail mail could read: ""Someone has created an account for you in their website foo.com. Your username is foo.name. To set your password, visit the following address: ..."" " pixelverbieger Last Week 60817 Investigate potentially failing `test_should_set_chmod()` test swissspidy Build/Test Tools normal normal Future Release defect (bug) new dev-feedback 2024-03-21T09:46:06Z 2024-03-21T09:46:06Z "This is a follow-up to #57774, which added a suite of new tests in 6.5. Since that milestone is soon closing, I am opening this to further investigate the `\Tests_Filesystem_WpFilesystemDirect_Mkdir::test_should_set_chmod()` test, which seems to fail on a certain host. See https://make.wordpress.org/hosting/test-results/r57860/wpmudevbot-r57860/ This could either be an issue with the host, core, or simply the test itself. This test is also the last one with an `is_windows()` check. Would be good if we could get rid of this env-specific check and maybe rely on comparing with `FS_CHMOD_DIR` instead." swissspidy Last Week 60816 Attachment pages conflicting with actual pages ayeshamalik Permalinks 6.4.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2024-03-21T09:04:38Z 2024-03-22T22:35:13Z The attachment pages are conflicting with the slug of the actual website's pages. What nonsense this is, It is totally frustrating. I don't know what is going on at the WordPress core team. ayeshamalik Last Week 60809 .editor-styles-wrapper styles opacity changed killerbeez Editor trunk normal normal 6.5.1 defect (bug) new reporter-feedback 2024-03-20T03:57:30Z 2024-03-25T23:27:02Z "In WordPress 6.4.3, the block editor automatically applies this to `.editor-styles-wrapper`: {{{ .editor-styles-wrapper.mce-content-body, .editor-styles-wrapper.editor-styles-wrapper { opacity: 1; } }}} While testing WordPress 6.5, this no longer occurs. Our theme has `opacity: 0` applied to the body, and we use jQuery to change it to `opacity: 1` when the DOM is loaded. This means that in 6.5, our block editor has 0 opacity. The issue for us is that this also applies to the block editor and as a result we see a grey box instead of the blocks of content. In testing with WordPress Alpha 6.6 or with the latest Gutenberg activated this doesn't appear to be the case, is there a reason this was removed from the 6.5 core?" killerbeez Last Week 60808 Twenty Twenty-Four: Black outline around the Navigation block submenu-expanding button jordesign Bundled Theme trunk normal normal 6.5.1 defect (bug) new dev-feedback 2024-03-20T03:01:53Z 2024-03-28T07:05:58Z "This appears to be a regression introduced in https://core.trac.wordpress.org/changeset/57739 Brought over from the Gutenberg repo: https://github.com/WordPress/gutenberg/issues/59944 ---- == Description When a sub-menu item is present, when clicking on the sub-menu item or on the parent menu item, a black border is shown around the items. [[Image(https://cldup.com/kNOVprCJ_d.png)]] Video: https://cloudup.com/cm8LVp_p6kN == Step-by-step reproduction instructions 1. go to the site editor 2. add a navigation block 3. add an item and a sub item 4. publish changes and visit the site 5. click on the sub-menu item and on the parent item 6. see the black border == Environment info WordPress 6.5 RC2 2024 theme == 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" jordesign Last Week 60805 Reading Settings: add option to discourage AI services from crawling the site jeherve Privacy normal normal Awaiting Review feature request new 2024-03-19T12:06:28Z 2024-03-19T12:06:28Z "I'd like to suggest a new addition to the bottom of the Reading Settings screen in the dashboard: [[Image(https://cldup.com/p6xw24IFff.png)]] This new section would help site owners indicate whether or not they would like their content to be indexed by AI services and used to train future AI models. There have been a lot of discussions about this in the past 2 years: content creators and site owners have asked whether their work could and should be used to train AI. Opinions vary, but at the end of the day I believe most would agree that as a site owner, it would be nice if I could choose for myself, for my own site. In practice, I would imagine the feature to work just like the Search Engines feature just above: when toggled, it would edit the site's `robots.txt` file and disallow a specific list of AI services from crawling the site. ---- There are typically 4 main approaches to discouraging AI Services from crawling your site: 1. You can add `robots.txt` entries matching the different User Agents used by AI services, and asking them not to index content via a `Disallow: /`. - **This seems to be the cleanest approach, and the one that AI services are the most likely to respect.** - This also has an important limitation ; it relies on a list of AI User Agents that would have to be kept up to date. It would obviously be hard for that list to ever be fully exhaustive. ''See an example of the user agents we would have to support below.'' 2. You can add an `ai.txt` file to your site, as [https://site.spawning.ai/spawning-ai-txt suggested by Spawning AI] here. - However, we have no guarantee AI services currently recognize and respect this file. 3. You could add a meta tag to your site's `head`: ``. This is something that was apparently first [https://www.deviantart.com/team/journal/UPDATE-All-Deviations-Are-Opted-Out-of-AI-Datasets-934500371 implemented by DeviantArt]. - I do not know if this is actually respected by AI services. It is not an HTML standard today. In fact, discussions for a new HTML standard are still in progress, and suggest a different tag ([https://github.com/whatwg/html/issues/9334 reference]). - If a standard like that were to be accepted, and if AI Services agreed to use it, it may be the best implementation in the future since we would not have to define a list of AI services. 4. You can completely block specific User Agents from accessing the site. - I believe we may not want to implement something that drastic and potentially blocking real visitors in WordPress Core. This is something that is better left to plugins. ---- Some plugins already exist that implement some of the approaches above. It shows that there may be interest to include such a feature in Core. - [https://wordpress.org/plugins/cellarweb-chatbot-blocker/ ChatBot Blocker] - [https://wordpress.org/plugins/simple-noai-and-noimageai/ Simple NoAI and NoImageAI] - [https://wordpress.org/plugins/block-ai-crawlers/ Block AI Crawlers] - [https://wordpress.org/plugins/block-chat-gpt-via-robots-txt/ Block Chat GPT via robots.txt] - [https://wordpress.org/plugins/block-common-crawl-via-robots-txt/ Block Common Crawl via robots.txt] - [https://github.com/thefrosty/wp-block-ai-scrapers WordPress Block AI Scrapers] ---- If we were to go with the first option, here are some examples of the User Agents we would have to support: - `Amazonbot` -- https://developer.amazon.com/support/amazonbot - `anthropic-ai` -- https://www.anthropic.com/ - `Bytespider` -- https://www.bytedance.com/ - `CCBot` -- https://commoncrawl.org/ccbot - `ClaudeBot` -- https://claude.ai/ - `cohere-ai` -- https://cohere.com/ - `FacebookBot` -- https://developers.facebook.com/docs/sharing/bot - `Google-Extended` -- https://blog.google/technology/ai/an-update-on-web-publisher-controls/ - `GPTBot` -- https://platform.openai.com/docs/gptbot - `omgili` -- https://webz.io/blog/web-data/what-is-the-omgili-bot-and-why-is-it-crawling-your-website/ - `omgilibot` -- https://webz.io/blog/web-data/what-is-the-omgili-bot-and-why-is-it-crawling-your-website/ - `SentiBot` -- https://sentione.com/ - `sentibot` -- https://sentione.com/ This list could be made filterable so folks can extend or modify that list as they see fit." jeherve Last Week 60803 Include fonts directory in `get_space_used()` calculation peterwilsoncc Editor normal normal Awaiting Review defect (bug) new 2024-03-19T02:46:16Z 2024-03-19T11:37:00Z "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 Last Week 60801 New sessions are created when user authenticates but there already are active sessions robert681 Login and Registration 6.4.3 normal normal Awaiting Review defect (bug) new 2024-03-18T18:28:41Z 2024-03-19T11:49:09Z "**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 Last Week 60800 Twenty Twenty-One: prevent PHP 8 fatal error from non-string in $tags_list josephscott Bundled Theme normal normal 6.6 defect (bug) new has-patch 2024-03-18T16:07:35Z 2024-03-19T09:40:33Z "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 Last Week 60799 Change the Header Tag in Link Modal from