Stars ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter 49820 Input and select elements are misaligned in the admin area Administration 5.4 normal trivial Awaiting Review defect (bug) new 2020-04-05T16:36:03Z 2020-04-13T07:38:57Z When placed side by side with inline select boxes, input elements are vertically misaligned in the admin area. Setting vertical-align to middle after line 78 of the /wp-admin/css/forms.css file – similarly to how select boxes are defined later in this stylesheet – seems to fix the problem. luigipulcini 1 45874 Content Section is overlapping the menu background valentinbora* Administration 5.0.2 normal trivial Awaiting Review enhancement accepted reporter-feedback 2019-01-09T12:36:13Z 2024-01-17T20:19:39Z "Hi, Just uploading some content into WordPress dashboard and saw a little layout bug, I'm not sure if it is kept like this but I thought, maybe it should be behind the menu background completely. As I have uploaded a screenshot, once the menu height finishes then the content is showing below. it should be behind the menu bar. [[Image(http://ahmadgulzar.com/wpscr.png)]] it can be fixed by just changing z-index of #adminmenuback from 1 to 3 {{{ #adminmenuback { position: fixed; top: 0; bottom: -120px; z-index: 3; } }}} Thanks " ahmadgulzar 2 54857 "New column ""template"" in pages/""screen options"" (enhancement)" Administration normal trivial Awaiting Review enhancement new 2022-01-19T11:15:03Z 2022-05-18T13:55:48Z " With WP5.9 FSE themes, editable “templates” are introduced . Therefore, in the list of “Pages” should now be a new column that displays the selected template name for each page. I suggest to offer a new checkable column option “Templates” within Pages/“Screen Options” to get a better overview of the assigned templates. " iStag 24795 OS X Treatment Administration 3.6 normal trivial Future Release enhancement new has-patch 2013-07-18T15:54:01Z 2017-02-05T14:09:10Z "Just a minor annoyance. Certain things are inherently different about using a Mac over any other Operating system. Specific to my case is keymappings. While I suspect most Mac users are smart enough to read ""Ctrl + A"" and translate that to ""CMD + A"", we should be explicit when we can. This patch inrtroduces pluggable function is_osx() that is really basic. Sadly, relies on User Agents and so is inherently flawed, but mainly useful anyway. Using this function, the Permalinks Options screen uses Command A instead of CTRL A when .htaccess is not writable. A little thing but annoying enough to warrant a patch." technosailor 46354 Update Count - Value Should Change as Updates are Applied Administration 5.1 low trivial Future Release enhancement new dev-feedback 2019-02-26T22:58:59Z 2020-02-14T10:54:33Z "The Update Count, shown in the Admin Bar, and the Admin Menu (against 'Dashboard' > 'Updates', and optionally against 'Plugins') should change to reflect the outstanding number of Updates available as Updates are Applied, whether they are applied individually on the Plugin Screen, or in bulk through the Updates Screen. This is not a high priority issue at all, but an extremely minor cosmetic change. I suspect that Javascript could be used to change the value as an Update completes successfully in any scenario. " Lucanos 44910 function for discriminating during auto saving Autosave normal trivial Awaiting Review feature request new has-patch 2018-09-07T05:33:12Z 2018-09-07T06:01:17Z "I want a function to distinguish auto saving like **wp_doing_cron** or **wp_doing_ajax**. The following code can be simplified. before {{{ if ( defined( 'DOING_AUTOSAVE' ) && DOING_AUTOSAVE ) { //do something } }}} after {{{ if ( wp_doing_autosave() ) { //do something } }}} " mt8.biz 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 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 55994 Twenty Seventeen: Header image zooms in when scrolling down on Mobile Safari Bundled Theme normal trivial Awaiting Review defect (bug) new close 2022-06-16T14:44:08Z 2024-03-28T08:57:15Z "Steps to replicate - Open TwentySeventeen demo site in Mobile Safari (https://twentyseventeendemo.wordpress.com). - Watch the header image as you scroll down the page. (Note that this only seems to happen in Mobile Safari, and doesn't appear in Chrome/Safari on the desktop even with a small window) The header image zooms in slightly when scrolling down, providing a jarring experience for the viewer. The header image should not change size when scrolling. Originally reported here: https://github.com/Automattic/themes/issues/678" mrfoxtalbot 46233 Twenty Sixteen: Theme includes Screen Reader Text inside Card Bundled Theme low trivial Awaiting Review defect (bug) new reporter-feedback 2019-02-11T12:47:41Z 2021-10-26T23:35:14Z The function twentysixteen_entry_meta includes the screen reader text inside the span property using the author mf class. That means when parsed it would say, 'Author David Shanske' The screen reader text should be inside the byline span but outside the author vcard span. dshanske 45741 Theme block style dependencies while enqueuing Bundled Theme 5.0.2 normal trivial Awaiting Review enhancement new 2018-12-22T13:17:50Z 2021-11-30T16:02:34Z "Bundled themes enqueue a block style, such as /css/blocks.css in twentytwelve. These css rules sometimes overwrite the rules in the files with handles ''wp-block-library'' and ''wp-block-library-theme'' While the dependencies seem to be maintained, for the sake for completeness, shouldn't dependencies be made explicit in bundled themes' functions.php files? For example, dependencies in this enqueue? {{{ wp_enqueue_style( 'twentytwelve-block-style', get_template_directory_uri() . '/css/blocks.css', array( 'twentytwelve-style' ), '20181018' ); }}} " superpoincare 1 55112 Twenty Twenty-Two: Button design Bundled Theme 5.9 normal trivial Awaiting Review enhancement new has-patch 2022-02-08T10:22:04Z 2022-02-08T14:44:45Z "It seems button elements are not styled in Twenty Twenty-Two such as {{{ }}} The browser default button appears with such code. It would be great if they have a style like other default themes. " umchal 60462 Twenty Twenty: Cover template overflows browser bar on mobile Bundled Theme normal trivial Awaiting Review enhancement new has-patch 2024-02-07T14:36:50Z 2024-02-07T23:32:42Z "Hey there! Twenty Twenty's cover template fills the whole background with the article image. This works as expected on desktop. On mobile however, some content gets covered by the browser bar. Replacing ''vh'' with ''dvh'' fixes that: {{{#!css .screen-height { min-height: 100dvh; } }}}" twiddler 50026 Twenty Twenty: Full height with short content Bundled Theme normal trivial Awaiting Review enhancement new dev-feedback 2020-04-28T22:35:16Z 2023-06-21T23:01:09Z "With the `twentytwenty` theme, when the height of the content in a page does not fill up the entire viewport, the page ends up with extra trailing whitespace. If we treat the `
` as a flex box the page will always be filled: {{{ body { display: flex; flex-direction: column; min-height: 100vh; } main#site-content { flex: 1 } }}} " beaucollins 2 58189 post_type parameter in update_post_caches() accepts more than a single post type Cache API normal trivial Awaiting Review defect (bug) new has-patch 2023-04-25T09:16:03Z 2023-07-16T05:57:03Z In `update_post_caches()`, the `post_type` parameter is documented as only accepting a single post type, which is inaccurate. It actually accepts a single post type, 'any' for any post type, and also an array of post types. DrewAPicture 1 45417 Lack of actions when wp_cache_flush is called Cache API normal trivial Future Release enhancement new dev-feedback 2018-11-26T14:08:25Z 2018-12-02T22:48:40Z "The function definition of wp_cache_flush doesn't have a do_action call, and neither does WP_Object_Cache->flush. https://core.trac.wordpress.org/browser/tags/4.9.8/src/wp-includes/cache.php#L97 https://core.trac.wordpress.org/browser/tags/4.9.8/src/wp-includes/cache.php#L498 I want to be able to run additional code whenever the object cache is flushed but currently I can't. Fixing this should be as trivial as adding {{{ do_action('wp_cache_flush'); }}} to the function definition of wp_cache_flush. I don't care about the name of the action or if it runs before or after the flush, I'd just like to have this functionality in the core. Preferably before WordPress 6.0. " k1sul1 1 51725 Canonical redirect and user_trailingslashit() Canonical 5.5.2 normal trivial Awaiting Review defect (bug) new needs-unit-tests 2020-11-07T01:06:54Z 2024-01-25T11:39:58Z "Hi, this bug is quite difficult to spot and it appears only when ''redirect_canonical()'' function is used to force the canonical redirect on front page and the trailing slashes are not added to the permalinks. Happily it is nothing serious. **How to reproduce this bug?** **Step 1. Remove the trailing slashes from WP permalinks:** First of all, you need to use ""Custom structure"" mode in Permalinks settings and remove the trailing slash (''/%postname%/'' => ''/%postname%'') in the adjacent input field. Therefore, the value of ''$wp_rewrite->use_trailing_slashes'' is changed to false. **Step 2. Trigger the canonical redirect on front page** Now let's disable the feed URL by redirecting the visitors trying to access it: {{{#!php ''http://example.com''). The problem is that the PHP notice is displayed then: ''Notice: Undefined index: path in /var/www/vhosts/maciejbis.net/example.com/wp-includes/canonical.php on line 576
Lorem Ipsum quam quasi mollitia
tags do not work Embeds normal minor Awaiting Review defect (bug) new 2018-05-14T14:31:21Z 2019-01-17T00:56:14Z "If an oEmbed has more than ten {{{}}} tags {{{WP_oEmbed::_strip_newlines}}} (called by {{{oembed_dataparse}}}} filter) returns a wrong result for it. All {{{}}} tags get temporarily replaced by a token, the newline stripping gets done and then the tokens {{{}}} get replaced back to their HTML. The tokens unfortunately are just {{{__PRE__}}} plus a counter (e.g. {{{__PRE__0}}}, {{{__PRE__1}}}) Thus if there are more than ten {{{}}} tags there will be tokens like {{{__PRE__10}}}. These obviously clash with previous tokens. Granted, this is ''quite'' uncommon but nonetheless it should be fixed in my opinion." jagszent 57451 Cross Site Request Forgery on Admin of any wordpress site to export files Export normal minor Awaiting Review defect (bug) new 2023-01-12T13:13:23Z 2023-03-20T04:34:24Z "[Marked as No Impact By WordPress Hackerone Team] Cross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they’re currently authenticated. With a little help of social engineering (such as sending a link via email or chat), an attacker may trick the users of a web application into executing actions of the attacker’s choosing Steps To Reproduce: 1. Login to WordPress Backend as an Admin 2. Go-to Tools > Export > Select what to export 3. Select the Data you want to export. Capture this request using a web-proxy like BurpSuite 4. Since this is a GET request, Copy the URL to which request is made. 5. Send this URL to another admin or user with equal rights. 6. When he clicks on the URL, he shall download the file automatically. The endpoint vulnerable: `http:///wp-admin/export.php?download=true&content=all&cat=0&post_author=2&post_start_date=0&post_end_date=0&post_status=0&page_author=0&page_start_date=0&page_end_date=0&page_status=0&attachment_start_date=0&attachment_end_date=0&submit=Download+Export+File` Recommendations Enforce CSRF protection like wpNonce Token for file export endpoint. Impact Unauthorised File Download on an administrator's PC An attacker can write a script which sends 100s of GET requests at once to the endpoint, and share the script to another user, and when he downloads 100 files at once, it shall also consume his disk space" f41z4n 2 7813 export function does not preserve encoding tott Export 2.7 normal minor Future Release defect (bug) new has-patch 2008-09-30T20:07:25Z 2019-03-15T00:31:35Z "when exporting strings are always converted to utf-8 while header and encoding is set to encoding used in blog. this causes trouble when importing later." tott 1 57711 PclZipUtilTranslateWinPath() fails when php_uname() function not available External Libraries 6.1.1 normal minor Future Release defect (bug) new has-patch 2023-02-14T10:40:37Z 2023-12-03T01:10:39Z "In PclZip class (wp-admin/includes/class-pclzip.php) PclZipUtilTranslateWinPath() calls php_uname(). If that function is disabled then the call fails. php_uname() is disabled on EasyWP host (part of Namecheap). https://www.namecheap.com/support/knowledgebase/article.aspx/9901/2279/easywp-list-of-php-functions-disabled-on-easywp-platform/ Core handles this by checking whether php_uname() exists (in wp-admin/includes/class-wp-debug.php). Is it possible to get PclZip to do the same? I checked PclZip host site (http://www.phpconcept.net) but there was no contact info there. This error arose while using https://wordpress.org/plugins/simply-static/" daymobrew 1 34130 Thickbox previous arrow External Libraries 4.3.1 normal minor Awaiting Review defect (bug) new close 2015-10-02T15:22:51Z 2021-03-15T21:51:46Z "The previous arrow in Thickbox does not work reliably. It sometimes displays 2 images, sometimes displays just the caption. Since that problem does not happen with the buttons, I suggest using the ""trigger"" function instead. The following code seems to work more reliably (staring at line 137): {{{ function goPrev(){ if(jQuery(document).unbind(""click"",goPrev)){jQuery(document).unbind(""click"",goPrev);} jQuery(""#TB_window"").remove(); jQuery(""body"").append(""""); tb_show(TB_PrevCaption, TB_PrevURL, imageGroup); return false; } jQuery(""#TB_prev"").click(goPrev); function goNext(){ jQuery(""#TB_window"").remove(); jQuery(""body"").append(""""); tb_show(TB_NextCaption, TB_NextURL, imageGroup); return false; } jQuery(""#TB_next"").click(goNext); jQuery(document).bind('keydown.thickbox', function(e){ if ( e.which == 27 ){ // close tb_remove(); } else if ( (e.which == 190) || (e.which == 39) ){ // display next image jQuery(""#TB_next"").trigger( ""click"" ); } else if ( (e.which == 188) || (e.which == 37) ){ // display previous image jQuery(""#TB_prev"").trigger( ""click"" ); } return false; }); }}}" Eric3D 2 8828 Tags and Categories are undifferentiable in Atom and RSS feeds Feeds 2.7 low minor Future Release enhancement new has-patch 2009-01-09T11:48:18Z 2018-02-08T16:03:00Z "In RSS feeds this can be achieved using the 'domain' attributes of the category element. This is already done in WordPress export through the wxr_post_taxonomy function, so we just have to do the same in RSS feeds. In Atom feeds this can be achieved using the 'scheme' attributes of the category element. The Atom standard is not explicit about what to put in this scheme attributes. There is [http://edward.oconnor.cx/2007/02/representing-tags-in-atom an interesting topic on Edward O’Connor blog]. In my proposed patch, i decided to use the 1st representation and i also considered seriously the 2nd. In the patch, i'm also adding the 'label' attribute to the atom category element and changed the 'term' attribute to be the tag slug. Seems this are currently the best practices in the Atom community." znarfor 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 50287 FS_METHOD=ssh2 breaks some plugins Filesystem API 5.4.1 normal minor Awaiting Review defect (bug) new has-patch 2020-05-30T21:44:41Z 2020-08-27T20:24:02Z "Some plugins expect WS_Filesystem() call to work properly without options. SSH2 method requires several options to work. When plugin does not call request_filesystem_credentials() it becomes broken by FS_METHOD=ssh2 constant. WordPress can use FTP_* constants as defaults in WP_Filesystem_SSH2 when none options are provided to constructor." denkoren 49719 PHP warning when updating ro_RO translation to latest version Filesystem API 5.3.2 normal minor Awaiting Review defect (bug) new reporter-feedback 2020-03-28T15:22:55Z 2023-03-12T02:10:55Z "The PHP warning is this: {{{ Warning: chmod(): Operation not permitted in /var/www/html/wp-admin/includes/class-wp-filesystem-direct.php on line 168 }}} Everything seems to work fine after that. I have a big number of plugins but do not know how to test this with them disabled. I use a customized version of TwentyTwenty. Thank you." silviubogan 18 48689 PHP warnings after updating to WP 5.3: ftp_nlist() and ftp_pwd() expect missing parameters costdev Filesystem API 5.3 normal minor 6.6 defect (bug) assigned needs-unit-tests 2019-11-17T23:24:37Z 2024-02-06T05:48:16Z "I updated several websites to WP 5.3 without any problems. But on one wesite I got these PHP warnings both in the backend and in the website: {{{ Warning: ftp_nlist() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 402 Warning: ftp_pwd() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 226 Warning: ftp_pwd() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 226 Warning: ftp_pwd() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 226 Warning: ftp_nlist() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 402 Warning: ftp_pwd() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 226 Warning: ftp_pwd() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 226 Warning: ftp_pwd() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 681 Warning: ftp_pwd() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 226 Warning: ftp_pwd() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 226 Warning: Cannot modify header information - headers already sent by (output started at /wp-admin/includes/class-wp-filesystem-ftpext.php:402) in /wp-includes/functions.php on line 5946 Warning: Cannot modify header information - headers already sent by (output started at /wp-admin/includes/class-wp-filesystem-ftpext.php:402) in /wp-admin/includes/misc.php on line 1252 Warning: Cannot modify header information - headers already sent by (output started at /wp-admin/includes/class-wp-filesystem-ftpext.php:402) in /wp-admin/admin-header.php on line 9 }}} I suppressed the ouput by ""muting"" the function calls with '@' in the file 'class-wp-filesystem-ftpext.php', i.e. changed {{{ftp_nlist()}}} to {{{@ftp_nlist()}}} etc.. I will be glad if any reason can be found and fixed until the next WP upgrade. " Hinjiriyo 3 24925 Improve no disk space error handling when updating plugins Filesystem API normal minor Awaiting Review enhancement new dev-feedback 2013-08-02T11:25:24Z 2021-07-20T23:02:17Z "I received the following uninformative error message when trying to update a plugin (roughly translated from Finnish): {{{ Error on updating BulletProof Security. Cannot create folder. /[WPDIR]/wp-content/upgrade/bulletproof-security.tmp. }}} The error was caused by not having enough disk space. The plugin update should check if that's the reason for the error and then display a more informative error message." Daedalon 1 46561 Make wp_normalize_path() on Windows resolve drive letter for drive–relative paths Filesystem API 3.9 normal minor Awaiting Review enhancement new dev-feedback 2019-03-19T09:18:48Z 2023-03-12T08:45:38Z "Though rarely used, Windows allows to omit drive letter in file path to treat is as drive–relative. This causes inconsistency where paths pointing to the same dir are not normalized to the same representation by `wp_normalize_path()`: {{{#!php Theme File Editor or Tools > Plugin File Editor The user is served a pop-up to let them know that they're editing the theme/plugin files and this could break the site. See screenshot attached. Just noting that the buttons aren't aligned. I am using Google Chrome Version 110.0.5481.77 (Official Build) (arm64) iOS: MacOS Monterey Version 12.6.1 Macbook Pro 16 inch, 2021 Chip: Apple M1 Max Here's how to view the popup: https://d.pr/i/QbYXe1 Here's a link to the screenshot of the mis-alignment: https://d.pr/i/UfpuJa " kimclow 1 60124 Grouping a Quote Block turns the Quote to a Paragraph Formatting 6.4.2 normal minor Awaiting Review defect (bug) new 2023-12-21T03:10:24Z 2023-12-21T03:10:24Z "When using the Block Editor and attempting to 'group' an existing Quote block, the 'Quote' block gets converted to a 'Paragraph' block. My expectation is that the Quote block would be grouped inside of a Group block, but instead it seems to convert the Quote block into a Group block and then has the quote content as a paragraph block within." hanttula 5 17491 Make is_email() compliant with RFC5322 (updated by RFC6854) Formatting 3.1.2 normal minor Future Release defect (bug) reopened needs-unit-tests 2011-05-18T14:48:52Z 2023-04-14T13:59:42Z is_email('toto.@toto.com') returns true arena 1 53041 colors.css is using the old blue. Formatting 5.7.1 normal minor Awaiting Review defect (bug) new dev-feedback 2021-04-15T12:51:29Z 2021-04-15T12:51:29Z "I love the new color pallet, but I noticed that colors.css overrules the new link color in common.css. colors.css is still using hex 0073aa, while common.css is using hex 2271b1. " DuisterDenHaag 1 24487 is_email() does not recognize IDN domains Formatting 3.5.1 normal minor Future Release defect (bug) new has-patch 2013-06-03T08:24:36Z 2021-04-28T09:58:52Z "Insufficient validation of the domain name in function is_email of wp-includes/formatting.php. !WordPress 3.5.1 > , including trunk. Test for invalid characters does not test Unicode symbols in international domain, such as Cyrillic domains and other Unicode domains." OlegCorner 1 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
andtags. 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 5 47594 Add nbsp symbol codes to convert throught sanitize_title SergeyBiryukov* Formatting 5.3 normal minor Future Release enhancement accepted has-patch 2019-06-23T17:06:42Z 2021-10-28T21:01:12Z "Default filters needs to be supplemented nbsp codes such as {{{ [ '%e2%80%af', '%e2%80%87', '%e2%81%a0' ] }}} and {{{ [ ' ', ' ', ' ', ' ', '', '' ] }}} " hokku 2 44906 "Include greek accent characters on ""remove_accents"" function" Formatting 4.9.8 normal minor Awaiting Review enhancement new dev-feedback 2018-09-06T19:53:57Z 2018-09-13T01:19:43Z "Hi, I extended the ""remove_accents"" function to support greek accents. If you wish you can add it in core. I have just added greek characters after: {{{#!php elseif ( 'el' == $locale ) { }}} Thanks {{{#!php 'a', 'º' => 'o', 'À' => 'A', 'Á' => 'A', 'Â' => 'A', 'Ã' => 'A', 'Ä' => 'A', 'Å' => 'A', 'Æ' => 'AE','Ç' => 'C', 'È' => 'E', 'É' => 'E', 'Ê' => 'E', 'Ë' => 'E', 'Ì' => 'I', 'Í' => 'I', 'Î' => 'I', 'Ï' => 'I', 'Ð' => 'D', 'Ñ' => 'N', 'Ò' => 'O', 'Ó' => 'O', 'Ô' => 'O', 'Õ' => 'O', 'Ö' => 'O', 'Ù' => 'U', 'Ú' => 'U', 'Û' => 'U', 'Ü' => 'U', 'Ý' => 'Y', 'Þ' => 'TH','ß' => 's', 'à' => 'a', 'á' => 'a', 'â' => 'a', 'ã' => 'a', 'ä' => 'a', 'å' => 'a', 'æ' => 'ae','ç' => 'c', 'è' => 'e', 'é' => 'e', 'ê' => 'e', 'ë' => 'e', 'ì' => 'i', 'í' => 'i', 'î' => 'i', 'ï' => 'i', 'ð' => 'd', 'ñ' => 'n', 'ò' => 'o', 'ó' => 'o', 'ô' => 'o', 'õ' => 'o', 'ö' => 'o', 'ø' => 'o', 'ù' => 'u', 'ú' => 'u', 'û' => 'u', 'ü' => 'u', 'ý' => 'y', 'þ' => 'th', 'ÿ' => 'y', 'Ø' => 'O', // Decompositions for Latin Extended-A 'Ā' => 'A', 'ā' => 'a', 'Ă' => 'A', 'ă' => 'a', 'Ą' => 'A', 'ą' => 'a', 'Ć' => 'C', 'ć' => 'c', 'Ĉ' => 'C', 'ĉ' => 'c', 'Ċ' => 'C', 'ċ' => 'c', 'Č' => 'C', 'č' => 'c', 'Ď' => 'D', 'ď' => 'd', 'Đ' => 'D', 'đ' => 'd', 'Ē' => 'E', 'ē' => 'e', 'Ĕ' => 'E', 'ĕ' => 'e', 'Ė' => 'E', 'ė' => 'e', 'Ę' => 'E', 'ę' => 'e', 'Ě' => 'E', 'ě' => 'e', 'Ĝ' => 'G', 'ĝ' => 'g', 'Ğ' => 'G', 'ğ' => 'g', 'Ġ' => 'G', 'ġ' => 'g', 'Ģ' => 'G', 'ģ' => 'g', 'Ĥ' => 'H', 'ĥ' => 'h', 'Ħ' => 'H', 'ħ' => 'h', 'Ĩ' => 'I', 'ĩ' => 'i', 'Ī' => 'I', 'ī' => 'i', 'Ĭ' => 'I', 'ĭ' => 'i', 'Į' => 'I', 'į' => 'i', 'İ' => 'I', 'ı' => 'i', 'IJ' => 'IJ','ij' => 'ij', 'Ĵ' => 'J', 'ĵ' => 'j', 'Ķ' => 'K', 'ķ' => 'k', 'ĸ' => 'k', 'Ĺ' => 'L', 'ĺ' => 'l', 'Ļ' => 'L', 'ļ' => 'l', 'Ľ' => 'L', 'ľ' => 'l', 'Ŀ' => 'L', 'ŀ' => 'l', 'Ł' => 'L', 'ł' => 'l', 'Ń' => 'N', 'ń' => 'n', 'Ņ' => 'N', 'ņ' => 'n', 'Ň' => 'N', 'ň' => 'n', 'ʼn' => 'n', 'Ŋ' => 'N', 'ŋ' => 'n', 'Ō' => 'O', 'ō' => 'o', 'Ŏ' => 'O', 'ŏ' => 'o', 'Ő' => 'O', 'ő' => 'o', 'Œ' => 'OE','œ' => 'oe', 'Ŕ' => 'R','ŕ' => 'r', 'Ŗ' => 'R','ŗ' => 'r', 'Ř' => 'R','ř' => 'r', 'Ś' => 'S','ś' => 's', 'Ŝ' => 'S','ŝ' => 's', 'Ş' => 'S','ş' => 's', 'Š' => 'S', 'š' => 's', 'Ţ' => 'T', 'ţ' => 't', 'Ť' => 'T', 'ť' => 't', 'Ŧ' => 'T', 'ŧ' => 't', 'Ũ' => 'U', 'ũ' => 'u', 'Ū' => 'U', 'ū' => 'u', 'Ŭ' => 'U', 'ŭ' => 'u', 'Ů' => 'U', 'ů' => 'u', 'Ű' => 'U', 'ű' => 'u', 'Ų' => 'U', 'ų' => 'u', 'Ŵ' => 'W', 'ŵ' => 'w', 'Ŷ' => 'Y', 'ŷ' => 'y', 'Ÿ' => 'Y', 'Ź' => 'Z', 'ź' => 'z', 'Ż' => 'Z', 'ż' => 'z', 'Ž' => 'Z', 'ž' => 'z', 'ſ' => 's', // Decompositions for Latin Extended-B 'Ș' => 'S', 'ș' => 's', 'Ț' => 'T', 'ț' => 't', // Euro Sign '€' => 'E', // GBP (Pound) Sign '£' => '', // Vowels with diacritic (Vietnamese) // unmarked 'Ơ' => 'O', 'ơ' => 'o', 'Ư' => 'U', 'ư' => 'u', // grave accent 'Ầ' => 'A', 'ầ' => 'a', 'Ằ' => 'A', 'ằ' => 'a', 'Ề' => 'E', 'ề' => 'e', 'Ồ' => 'O', 'ồ' => 'o', 'Ờ' => 'O', 'ờ' => 'o', 'Ừ' => 'U', 'ừ' => 'u', 'Ỳ' => 'Y', 'ỳ' => 'y', // hook 'Ả' => 'A', 'ả' => 'a', 'Ẩ' => 'A', 'ẩ' => 'a', 'Ẳ' => 'A', 'ẳ' => 'a', 'Ẻ' => 'E', 'ẻ' => 'e', 'Ể' => 'E', 'ể' => 'e', 'Ỉ' => 'I', 'ỉ' => 'i', 'Ỏ' => 'O', 'ỏ' => 'o', 'Ổ' => 'O', 'ổ' => 'o', 'Ở' => 'O', 'ở' => 'o', 'Ủ' => 'U', 'ủ' => 'u', 'Ử' => 'U', 'ử' => 'u', 'Ỷ' => 'Y', 'ỷ' => 'y', // tilde 'Ẫ' => 'A', 'ẫ' => 'a', 'Ẵ' => 'A', 'ẵ' => 'a', 'Ẽ' => 'E', 'ẽ' => 'e', 'Ễ' => 'E', 'ễ' => 'e', 'Ỗ' => 'O', 'ỗ' => 'o', 'Ỡ' => 'O', 'ỡ' => 'o', 'Ữ' => 'U', 'ữ' => 'u', 'Ỹ' => 'Y', 'ỹ' => 'y', // acute accent 'Ấ' => 'A', 'ấ' => 'a', 'Ắ' => 'A', 'ắ' => 'a', 'Ế' => 'E', 'ế' => 'e', 'Ố' => 'O', 'ố' => 'o', 'Ớ' => 'O', 'ớ' => 'o', 'Ứ' => 'U', 'ứ' => 'u', // dot below 'Ạ' => 'A', 'ạ' => 'a', 'Ậ' => 'A', 'ậ' => 'a', 'Ặ' => 'A', 'ặ' => 'a', 'Ẹ' => 'E', 'ẹ' => 'e', 'Ệ' => 'E', 'ệ' => 'e', 'Ị' => 'I', 'ị' => 'i', 'Ọ' => 'O', 'ọ' => 'o', 'Ộ' => 'O', 'ộ' => 'o', 'Ợ' => 'O', 'ợ' => 'o', 'Ụ' => 'U', 'ụ' => 'u', 'Ự' => 'U', 'ự' => 'u', 'Ỵ' => 'Y', 'ỵ' => 'y', // Vowels with diacritic (Chinese, Hanyu Pinyin) 'ɑ' => 'a', // macron 'Ǖ' => 'U', 'ǖ' => 'u', // acute accent 'Ǘ' => 'U', 'ǘ' => 'u', // caron 'Ǎ' => 'A', 'ǎ' => 'a', 'Ǐ' => 'I', 'ǐ' => 'i', 'Ǒ' => 'O', 'ǒ' => 'o', 'Ǔ' => 'U', 'ǔ' => 'u', 'Ǚ' => 'U', 'ǚ' => 'u', // grave accent 'Ǜ' => 'U', 'ǜ' => 'u', ); // Used for locale-specific rules $locale = get_locale(); if ( 'de_DE' == $locale || 'de_DE_formal' == $locale || 'de_CH' == $locale || 'de_CH_informal' == $locale ) { $chars[ 'Ä' ] = 'Ae'; $chars[ 'ä' ] = 'ae'; $chars[ 'Ö' ] = 'Oe'; $chars[ 'ö' ] = 'oe'; $chars[ 'Ü' ] = 'Ue'; $chars[ 'ü' ] = 'ue'; $chars[ 'ß' ] = 'ss'; } elseif ( 'da_DK' === $locale ) { $chars[ 'Æ' ] = 'Ae'; $chars[ 'æ' ] = 'ae'; $chars[ 'Ø' ] = 'Oe'; $chars[ 'ø' ] = 'oe'; $chars[ 'Å' ] = 'Aa'; $chars[ 'å' ] = 'aa'; } elseif ( 'ca' === $locale ) { $chars[ 'l·l' ] = 'll'; } elseif ( 'sr_RS' === $locale || 'bs_BA' === $locale ) { $chars[ 'Đ' ] = 'DJ'; $chars[ 'đ' ] = 'dj'; } elseif ( 'el' == $locale ) { $chars[ 'Ά' ] = 'Α'; $chars[ 'ά' ] = 'α'; $chars[ 'Έ' ] = 'Ε'; $chars[ 'έ' ] = 'α'; $chars[ 'Ί' ] = 'Ι'; $chars[ 'ί' ] = 'ι'; $chars[ 'ΐ' ] = 'ϊ'; $chars[ 'Ύ' ] = 'Υ'; $chars[ 'ύ' ] = 'υ'; $chars[ 'ΰ' ] = 'ϋ'; $chars[ 'Ή' ] = 'Η'; $chars[ 'ή' ] = 'η'; $chars[ 'Ό' ] = 'Ο'; $chars[ 'ό' ] = 'ο'; $chars[ 'Ώ' ] = 'Ω'; $chars[ 'ώ' ] = 'ω'; } $string = strtr($string, $chars); } else { $chars = array(); // Assume ISO-8859-1 if not UTF-8 $chars['in'] = ""\x80\x83\x8a\x8e\x9a\x9e"" .""\x9f\xa2\xa5\xb5\xc0\xc1\xc2"" .""\xc3\xc4\xc5\xc7\xc8\xc9\xca"" .""\xcb\xcc\xcd\xce\xcf\xd1\xd2"" .""\xd3\xd4\xd5\xd6\xd8\xd9\xda"" .""\xdb\xdc\xdd\xe0\xe1\xe2\xe3"" .""\xe4\xe5\xe7\xe8\xe9\xea\xeb"" .""\xec\xed\xee\xef\xf1\xf2\xf3"" .""\xf4\xf5\xf6\xf8\xf9\xfa\xfb"" .""\xfc\xfd\xff""; $chars['out'] = ""EfSZszYcYuAAAAAACEEEEIIIINOOOOOOUUUUYaaaaaaceeeeiiiinoooooouuuuyy""; $string = strtr($string, $chars['in'], $chars['out']); $double_chars = array(); $double_chars['in'] = array(""\x8c"", ""\x9c"", ""\xc6"", ""\xd0"", ""\xde"", ""\xdf"", ""\xe6"", ""\xf0"", ""\xfe""); $double_chars['out'] = array('OE', 'oe', 'AE', 'DH', 'TH', 'ss', 'ae', 'dh', 'th'); $string = str_replace($double_chars['in'], $double_chars['out'], $string); } return $string; } }}} " papazetis 1 49129 Incorrect German Umlaut substitutions Formatting 5.4 normal minor Awaiting Review enhancement new dev-feedback 2020-01-04T00:18:46Z 2020-01-04T09:39:30Z "Hello, as a native speaker, I find the German Umlaut substitutions quite strange. Correctly, ü is turned into ue, but Ü is turned into Ue. Since the second character should be considered as part of the former character, the former capitalization should be respected. This is especially strange in uppercase text: FRÖHLICH -> FROeHLICH KÖNNEN -> KOeNNEN If it was changed to be all uppercase, it would work much better: FRÖHLICH -> FROEHLICH KÖNNEN -> KOENNEN When used at the start of a word, it would also work fine, if capitalized: ÖFFENTLICH -> OEffentlich ÜBERGANG -> UEbergang Therefore, I would propose changing the table located in wp-includes/formatting.php:1941 (https://github.com/WordPress/WordPress/blob/master/wp-includes/formatting.php#L1941) to the following: {{{ if ( 'de_DE' == $locale || 'de_DE_formal' == $locale || 'de_CH' == $locale || 'de_CH_informal' == $locale ) { $chars['Ä'] = 'AE'; $chars['ä'] = 'ae'; $chars['Ö'] = 'OE'; $chars['ö'] = 'oe'; $chars['Ü'] = 'UE'; $chars['ü'] = 'ue'; $chars['ß'] = 'ss'; }}} Though, to be entirely correct, the surrounding characters would have to be checked, which would be difficult, given the current architecture. There even is a capital ß now, which would be substituted with SS. I am happy to hear any second opinions on this. Best regards, Benedikt" bmuessig 47557 Sanitize Email Suggestion Formatting 5.2.1 normal minor Awaiting Review enhancement new needs-unit-tests 2019-06-18T15:19:58Z 2023-03-23T16:11:52Z "I am using WooCommerce and I've noticed several customer emails come through like... {{{ example@example.com1234 example@example.com1234567812345678 }}} It's mostly due to the email input being the last one before the credit card step, but these emails are passing the validation and sanitization that exists: is_email and sanitize_email. I am doing something like the following to fix... {{{#!php tags Formatting 5.5.1 normal minor Awaiting Review enhancement new 2020-10-08T12:49:54Z 2020-10-08T12:49:54Z "Like the title says, wp_kses_post filters javascript tags, but not the actual javascript itself. If you sanitize some content using wp_kses_post that contains world!""; wp_kses_post($str); Outputs: hello myvar = 'foobar'; world! Expected output: hello world!" janmiddelkoop 54136 Slideshow gallery shown as a tiled gallery when using shortcode with Classic Editor Gallery 5.8.1 normal minor Awaiting Review defect (bug) new close 2021-09-16T19:18:33Z 2021-12-15T03:15:56Z "The issue is happening with the Gallery Block, [https://wordpress.com/support/wordpress-editor/blocks/gallery-block/2/ when added through the Classic Editor as explained here.] Adding it with the shortcode {{{[gallery]}}} and the variable {{{type: slideshow}}} outputs it as a tiled gallery instead of showing a slideshow. [https://wordpress.org/support/topic/what-options-are-currently-available-in-the-wordpress-gallery-shortcode-2 This was initially reported here as a Jetpack issue], but I was able to reproduce it without Jetpack installed, and with a default theme (Twenty Seventeen). " muffinpeace 1 47744 WordPress default galleries do not display properly on Safari 10.1 and possibly other older browsers Gallery 5.2.2 normal minor Awaiting Review defect (bug) new 2019-07-20T20:48:07Z 2019-07-25T21:38:27Z "The following thread details the problem: [https://stackoverflow.com/questions/33636796/chrome-safari-not-filling-100-height-of-flex-parent] Images are nested inside a flex container. The child elements have a height of 100% which does not work on these older browsers such as Safari 10.1. This is because the parent element does not have a set height. So the child element doesn't know what 100% height is. The correct way to do it is to remove the 100% height from everything and use flex throughout the elements. {{{ .wp-block-gallery .blocks-gallery-image, .wp-block-gallery .blocks-gallery-item { flex-direction: row; } .wp-block-gallery .blocks-gallery-image figure, .wp-block-gallery .blocks-gallery-item figure { height: auto; align-items: stretch; } .wp-block-gallery.is-cropped .blocks-gallery-image a, .wp-block-gallery.is-cropped .blocks-gallery-image img, .wp-block-gallery.is-cropped .blocks-gallery-item a, .wp-block-gallery.is-cropped .blocks-gallery-item img { height: auto; display: flex; } .wp-block-gallery .blocks-gallery-image figcaption, .wp-block-gallery .blocks-gallery-item figcaption { left: 0; } }}} The above CSS fixes the issue and should replace the current CSS. " billybidley 51828 gallery items not aligned when row has less items than column count Gallery 5.5.3 normal minor Awaiting Review defect (bug) new has-patch 2020-11-19T20:42:47Z 2020-11-19T20:42:47Z "If a gallery contains not enough images to fill up all columns, in some cases the layout looks wrong. In the last row, the images are spaced evenly over the row, but the alignment is off. Screenshot with problem: https://snipboard.io/yZEabf.jpg The problem, as far as I can see, is that there aren't enough gallery-item flex boxes to ensure the layout matches the layout of a full row. I simple fix (although I am altogether not sure if this is the right way to go) is to end the row with just as many empty gallery items as needed to fill up the row. The attached patch does this, and seems to fix the problem. Screenshot with fix: https://snipboard.io/IdtlJh.jpg I would also be fine if the three images were spaced evenly over the row, but then the left and right alignment should be the same. I don't know how that could be achieved. This is with the neve theme. I don't have a reproduction with the default theme, sorry." rolekwp 59843 Headers of the table on make.wordpress blog breaks after a few second of load ( check the url in description) General normal minor Awaiting Review defect (bug) new 2023-11-08T18:56:49Z 2023-11-08T19:25:19Z "The header of the first table in the following link breaks after a moment. https://make.wordpress.org/core/2023/11/08/merging-performant-translations-into-core/ " thekt12 2 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 52359 Links in Gutenberg Continue to be Built When Typing General normal minor Awaiting Review defect (bug) new 2021-01-25T12:35:42Z 2021-01-25T15:39:39Z "If adding a link to the trailing word or phrase in Gutenberg, the link continues to be built when you continue typing. Basically, the anchor tag keeps getting pushed to the right as you type. To reproduce...type a word or phrase and end in a linking word or phrase. For this example, we will link to the word WordPress. Highlight WordPress, click the link icon in the toolbar and add the URL https://www.wordpress.org. Then continue typing. The new text will continue as part of the link. Expected behavior would be that the link does not continue to be built after the target word or phrase." dlfulle 2 60579 Notice: Undefined index: name in /wp-includes/class-wp-roles.php on line 293 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 2 46346 Page counts and related calculations typically expect and document ints but are actually floats SergeyBiryukov General normal minor Future Release defect (bug) reviewing has-patch 2019-02-26T02:22:17Z 2021-10-13T18:27:34Z Should be an int, not calculated using rounding, preventing off-by-one errors. lev0 1 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 56098 Post Excerpt style in query loop not able to override if paragraph color is set in the global style. General 6.0 normal minor Awaiting Review defect (bug) new has-patch 2022-06-30T04:18:39Z 2022-07-12T16:54:34Z "Post Excerpt style in query loop not able to override if paragraph color is set in the global style. ex. The paragraph colour is set to RED. The Query loop excerpt colour is set to GREEN. The final output will be RED. " tnchuntic 1 54851 Prevent unnecessary code comments from being output to the front end General normal minor Awaiting Review defect (bug) new 2022-01-18T13:01:39Z 2022-01-19T13:44:18Z "Gutenberg's ""Post Comments"" block appears to pull its code from the WordPress' theme compat `comments.php` file here: https://github.com/WordPress/wordpress-develop/blob/a0b1f27de6c928fde51bbc7078b32ca9c9d6ed8d/src/wp-includes/theme-compat/comments.php#L30-L75 This includes some code comments that may be useful for developers, but don't actually need to be send to the front end: [[Image(http://cldup.com/ebPNDuXdBe.png)]] I'd suggest we change these from HTML comments to PHP comments, so they aren't visible in the outputted markup. --- Related: https://github.com/WordPress/gutenberg/issues/37989 Tested with Gutenberg 12.4 WordPress 5.8.3" kjellr 2 55930 Provide comment syntax for templates and template parts General 6.0 normal minor Awaiting Review defect (bug) new 2022-06-06T05:59:02Z 2023-01-17T21:16:31Z "''Thanks to all of you for working on this great Free Software project! '' I'm trying to add copyright and license information to my theme. I do so using SPDX headers using REUSE tool [https://reuse.software]. This adds information to the `.html` files using HTML comments (``). The **Site Editor** in **WordPress 6.0** doesn't seem able to handle with regular HTML comments in templates and template parts. On a new theme created using `new-empty-theme.php` this results in the following `index.html` page for example: {{{ }}} It renders just fine, but in the Site Editor these comments of templates and template parts get treated as blocks. This results in an error for each template and page template that has the HTML annotations: ""**This block has encountered an error and cannot be previewed.**''''"" [[Image(https://user-images.githubusercontent.com/7458098/172100897-8fdc7d30-13c1-443d-b951-d9d004c73118.png)]] Copying the block contents (source code) the resulting output is as follows: {{{
}}} So it seems that the comment is treated as a paragraph. Besides this being valid HTML, I couldn't find anything about a separate comment syntax in the [https://developer.wordpress.org/themes/block-themes/templates-and-template-parts/] documentation. **I expect the Site Editor to ignore non-wp comments rather than trying to parse them as blocks.** ''I documented some other experiences with using REUSE on WordPress themes in an issue at the REUSE project: [https://github.com/fsfe/reuse-tool/issues/537]'' " wprediscovered 1 33141 Search form clear button is clipped in Safari (OS X) General low minor Awaiting Review defect (bug) new has-patch 2015-07-27T15:06:53Z 2017-05-23T17:20:12Z "Safari's search boxes have an ""X"" to clear the search terms. It is getting clipped. OS X. The reason for this appears to be the padding on the search box, and that we're doing this: {{{ input[type=""search""] { -webkit-appearance: textfield; } }}} which we HAVE to do in Safari in order to control certain aspects of the display. [[Image(https://cldup.com/J90Zt5PGQW-3000x3000.png)]] There is a pseudo-selector we might be able to use to fix this: `::-webkit-search-cancel-button {}`" markjaquith 54282 Search terms wrapped in double quotes never return results directly from iOS Safari keyboard General 5.8.1 normal minor Awaiting Review defect (bug) new reporter-feedback 2021-10-17T21:39:08Z 2021-10-25T16:21:23Z "If a search term wrapped in double quotes is entered into a search field on a WordPress site in iOS Safari, it will never return results, even if the search term is known to exist on the website. The bug is caused by some lack of sanitisation of the type of double-quotes that are sent by the iOS Safari keyboard. That this is the case can be revealed by typing the search term, wrapped in double quotes, in a plain text editor on iOS, copying and pasting that into the WordPress search field in the browse and hitting return to perform the search; then, the search term succeeds in finding the (known to exist) result. " sadhaka 60572 block_core_navigation_render_inner_blocks loses caret for parent items 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 55486 register_block_type_from_metadata does NOT work within a theme but as a plugin General 5.9.2 normal minor Awaiting Review defect (bug) new needs-refresh 2022-03-30T01:02:26Z 2023-05-30T12:34:44Z "I created a wordpress block and it guides me to the official documentation and it came to work as an external plugin, taking into account the architecture of block.json for its use, however it has not worked for me when the block is required to be integrated into a theme, delivery wrong path request looking in plugin folder plus adding another path. example error peticion https://domain.local/wp-content/plugins/D:/xampp/htdocs/wp-content/themes/NewsPaper/inc/gutenberg/myblock/index.js?ver=d395fe5d9d90bd6565685c91d8d38888" andre3600 1 46780 wpColorPicker() close() method uses iris 'toggle' instead of 'hide' which can unexpectedly open the color pane General 5.1 normal minor Awaiting Review defect (bug) new has-patch 2019-04-03T07:09:04Z 2019-05-23T09:49:02Z "Using the close() method, one would expect that the color picker will get closed anyway and that nothing else would happen, even if the picker in question was already closed. However, when calling the close() method on an already closed picker (e.g. when you call close() on a set of three pickers, where only 2 might be open), the color pane will get displayed. While the close() method correctly will remove the wp-picker-open class and will set the aria-expanded attribute to false regardless, the actual iris picker is just using toggle: {{{ this.element.iris( 'toggle' ); }}} Instead, it would be safer to use {{{ this.element.iris( 'hide' ); }}} which would also be more in line with how the class and attribute are handled." maximus80 5 53262 "wp_robots() (via wp_die) triggers a ""doing_it_wrong_trigger_error"", but should not." General 5.7 normal minor Awaiting Review defect (bug) new dev-feedback 2021-05-23T21:43:29Z 2022-08-03T15:31:55Z "Hello there. In my plugin, I need to die early, like, right after the plugins are loaded, imagine this for a shortcut: `add_action( 'plugins_loaded', 'wp_die' );` This is the output: ''Notice: 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 /wp-includes/functions.php on line 5313'' {{{ # Time Memory Function Location 1 0.0002 369912 {main}( ) .../admin.php:0 2 0.0003 370552 require_once( '/wp-load.php' ) .../admin.php:34 3 0.0003 370960 require_once( '/wp-config.php' ) .../wp-load.php:37 4 0.0003 375568 require_once( '/wp-settings.php' ) .../wp-config.php:88 5 0.0410 1735152 do_action( ) .../wp-settings.php:423 6 0.0411 1735528 WP_Hook->do_action( ) .../plugin.php:484 7 0.0411 1735528 WP_Hook->apply_filters( ) .../class-wp-hook.php:316 8 0.0882 3856336 wp_die( ) .../class-wp-hook.php:292 9 0.0882 3874480 _default_wp_die_handler( ) .../common.php:275 10 0.0884 3876304 wp_robots( ) .../functions.php:3497 11 0.0884 3876304 apply_filters( ) .../robots-template.php:32 12 0.0884 3876712 WP_Hook->apply_filters( ) .../plugin.php:212 13 0.0884 3878216 wp_robots_noindex_embeds( ) .../class-wp-hook.php:292 14 0.0884 3878216 is_embed( ) .../robots-template.php:93 15 0.0884 3878216 _doing_it_wrong( ) .../query.php:881 16 0.0885 3879304 trigger_error ( ) .../functions.php:5313 }}} another notice will be trigger, same thing but line 13 will be `wp_robots_noindex_search`. Since WP 5.7 the `wp_robots()` function is called in a `wp_die()`, but `wp_die()` can be called before the query is done, this is not too soon to die ''(for once, got it?)''. A possible patch is to delay these default filters a bit later ''(wp-includes/default-filters.php)'' instead of adding them right away: {{{ add_action( 'wp', 'wp_late_robots_check' ); function wp_late_robots_check() { add_filter( 'wp_robots', 'wp_robots_noindex_embeds' ); add_filter( 'wp_robots', 'wp_robots_noindex_search' ); } }}} Thanks for your attention." juliobox 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 59916 API Docs: update comment endpoint does't have example request gavande1 General normal minor Awaiting Review enhancement assigned 2023-11-16T11:02:29Z 2023-11-27T18:39:26Z "**Details** I noticed that the comment update API endpoint doesn't have an example request, even though the API document has a title for it. **Link to doc** https://developer.wordpress.org/rest-api/reference/comments/#example-request-2" gavande1 56846 "All test classes that use the ""wp"" prefix should be renamed for consistency" General normal minor Awaiting Review enhancement new has-patch 2022-10-18T18:42:18Z 2023-07-25T21:15:25Z "About 170 PHP test classes use lowercase `w` and only 34 test classes use capital `W` in the `wp` prefix. Examples: `wp` : `Tests_Formatting_wpParseStr` `Wp` : `Tests_Category_WpListCategories` According to [https://make.wordpress.org/core/handbook/testing/automated-testing/writing-phpunit-tests/#test-classes| this document], the correct spelling is `Wp`. So, all test classes that use the `wp` prefix should be renamed for consistency." antonvlasenko 1 53541 Arguments passed to load_template() should be extracted General 5.8 normal minor Awaiting Review enhancement new dev-feedback 2021-06-28T12:52:53Z 2021-06-28T16:24:41Z "As was originally voiced in this thread when ability to pass arguments to templates was added in v5.5, these arguments should be extracted. As a plugin developer today, the new $args passing does provide as good an experience in terms of simplicity and documentation as the older method of passing query vars. This is because query vars are extracted. So if I'm building a plugin that has a product template and I want to render out $product variables, or pass an object in $product, then which would I prefer to offer to theme developers: Use `$args['product']` to access the $product object. OR Use `$product` to access the product object. Clearly having the vars extracted makes them easier to access. Perhaps the objection to this is that aside from the exception made for query vars we normally try to avoiding using extract(). However in this case I think an exception is warranted. Otherwise the effort put into making argument passing available is somewhat wasted because plugin developers will likely prefer to use query vars simply because they are extracted automatically. Another potential way to enable this would be through an option argument passed to load_template (which would have to first go through locate_template() as well, and that would be $extract_args = false, or $extract_args = true. I'd opt for the later to set the default to extract, but just having that option would let developers control the naming of variables they make available in templates. Reference to the announcement, argument passing in 5.5 https://make.wordpress.org/core/2020/07/17/passing-arguments-to-template-files-in-wordpress-5-5/ load_template() on trak: https://core.trac.wordpress.org/browser/tags/5.7.1/src/wp-includes/template.php#L709 " caseymilne 1 60355 Can't save object to metadata with `readonly` properties General normal minor Future Release enhancement new needs-docs 2024-01-26T15:45:41Z 2024-02-12T21:52:11Z "If I have class with `readonly` property {{{#!php $property_value ) { $value->$property_name = map_deep( $property_value, $callback ); // <--------- } }}} " Cawa-93 59432 Compliant with W3C coding standards General 6.3.1 normal minor Awaiting Review enhancement new 2023-09-23T08:04:02Z 2023-11-10T22:15:06Z "When validating any WordPress site, warnings appear: 1. Trailing slash on void elements has no effect and interacts badly with unquoted attribute values. Example: `` `` Also in tags img, button etc 2. The type attribute for the style element is not needed and should be omitted. Example: `00000000000000000000
xxxxxxxxxxxxxxxxxxxx
00000000000000000000
xxxxxxxxxxxxxxxxxxxx