__group__ ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter Future Releases 29161 $pagenow variable not set in admin pages on Windows systems Administration 3.9.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2014-08-09T10:59:05Z 2021-12-27T21:25:33Z "In the most recent version of WordPress: `vars.php`, starting line 25: {{{#!php if ( is_network_admin() ) preg_match('#/wp-admin/network/?(.*?)$#i', $_SERVER['PHP_SELF'], $self_matches); elseif ( is_user_admin() ) preg_match('#/wp-admin/user/?(.*?)$#i', $_SERVER['PHP_SELF'], $self_matches); else preg_match('#/wp-admin/?(.*?)$#i', $_SERVER['PHP_SELF'], $self_matches); }}} The ""/"" character does not match the ""\"" character found as the directory separator on Windows systems. This causes various issues throughout the entirety of the administration pages, notably that ""add_meta_box"" ceases to function correctly. Would recommend it be changed to something like this: {{{#!php $ds = preg_quote(DIRECTORY_SEPARATOR); if ( is_network_admin() ) preg_match('#'.$ds.'wp-admin'.$ds.'network'.$ds.'?(.*?)$#i', $_SERVER['PHP_SELF'], $self_matches); elseif ( is_user_admin() ) preg_match('#'.$ds.'wp-admin'.$ds.'user'.$ds.'?(.*?)$#i', $_SERVER['PHP_SELF'], $self_matches); else preg_match('#'.$ds.'wp-admin'.$ds.'?(.*?)$#i', $_SERVER['PHP_SELF'], $self_matches); }}} Thanks for the wonderful software!" Craxic Future Releases 49870 "Admin Email Verification ""The Email is Correct"" leads to White Screen" Administration 5.4 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-04-10T16:39:15Z 2020-05-02T23:37:48Z "On every one of my sites, clicking on ""The Email is Correct"" leads to a white screen, and no email sent. A console error on this white screen reads: ""The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature."" See screenshot: https://rogueeasyweb.tinytake.com/tt/NDIwMzkzNF8xMzA4MjE4Mg I've been simply clicking in Remind me Later to get around it. This has been happening for months and months now, across multiple WP updates, and on at least 10 different sites on a few different hosts. Sorry I do not have a stock installation sitting around with no plugins/themes to test on. Using Firefox v74.0.1 on Windows 10" rogueeasyweb Future Releases 39762 Change in DOM Element Properties as seen in Javascript Event Handlers Between 4.6.2 and 4.7+ Administration 4.7 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-02-01T22:37:55Z 2021-04-06T05:27:06Z "I'm seeing a problem that appears to be related to the change introduced by ticket #37973 in 4.7. I don't see this issue in 4.6.2. I filed ticket #39739 earlier this week that documented another problem related to this change as well. This problem is also related to a ""select all"" checkbox but has to do with the state of child checkboxes within javascript event handlers being different between 4.6.2 and 4.7. In short, I have an event handler for ""click"" for the ""manage-column check-column"" checkbox (simplified HTML shown below). This event handler looks for child checkboxes in the table (""nslb_import_rows"") and triggers their ""click"" event accordingly. The ""click"" events are triggered so that additional HTML can be displayed on the page if certain conditions are met when the individual rows are selected / unselected or en masse via this ""select all"". {{{
Name
Steven
David
}}} Please note the first element with the class ""nslb-dynamic-content"". As the name implies, this content is created dynamically and added to the page via javascript as certain other options on the page are chosen. Because the inner HTML is added dynamically, when this code in common.js at line 459 at the 4.6.2 level executes: {{{ $('thead, tfoot').find('.check-column :checkbox').on( 'click.wp-toggle-checkboxes', function( event ) { ... }}} it doesn't find any elements that match the search criteria as they are not present on the page yet, therefore no event handlers are registered here. The HTML at this point would look only like this: {{{
}}} Conversely, the code in common.js at 4.7+ on line 452 that replaced this line {{{ $body.on( 'click.wp-toggle-checkboxes', 'thead .check-column :checkbox, tfoot .check-column :checkbox', function( event ) { ... }}} fires when the ""manage-column check-column"" checkbox is clicked even though it's in HTML that is added dynamically. This is because the line in 4.7+ handles click events in the body and then evaluates whether or not a ""check-column"" checkbox was clicked in a or as part of click event processing itself thereby finding my ""manage-column check-column"" checkbox"" in the DOM at that point. The net of effect of all this is a change in the value of the ""clicked"" property of these child checkboxes when my own click event handler executes. For example, in 4.6.2, if no checkboxes are selected on the page and I click my ""manage-column check-column"" checkbox, the ""clicked"" properties for the child checkboxes are ""false"" because the event handler on line 459 in common.js doesn't execute. However, in 4.7+ given the same scenario, the ""clicked"" properties for the child checkboxes are already ""true"" because the event handler on line 452 in common.js does execute each time. You could actually argue the behavior in 4.6.2 is defective since the handler does not get registered for ""check-column"" checkboxes added dynamically. FYI, if I hard code this exact HTML statically, then the 4.6.2 event handler does get registered and the ""clicked"" property for child checkboxes is consistent between 4.6.2 and 4.7+. Additionally, the code in common.js at the 4.7+ level could potentially trigger the ""click"" event for any child checkboxes it finds as opposed to just modifying their ""checked"" property, although I'm not sure of the ramifications of that type change." reldev Future Releases 44036 Checkboxes appearing strangely in FireFox responsive view Administration normal normal Awaiting Review defect (bug) new reporter-feedback 2018-05-10T11:52:31Z 2020-04-15T04:31:10Z "When I switch to mobile view in FireFox, the checkboxes are appearing strangely! Please see screenshot. WordPress version: 5.0-alpha-43205 FireFox version: 59.0.2 (64-bit) OS: Ubuntu 14.04 Steps to reproduce: 1. Go to /wp-admin/edit.php?post_type=page 2. Press Shift+Ctrl+M to bring up smaller view" subrataemfluence Future Releases 52611 Error searching post Administration 5.6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-02-22T20:12:44Z 2021-12-11T23:18:20Z "When I use the post search engine the second time I get the error: ""invalid content type"". The first time I enter a search term, everything is fine. The problem is when I try to do a second search. I hope they can correct it. Note: I use WordPress in Spanish and updated to the latest version: 5.6.2. But the problem is present from previous versions: 5.6.1, ... [[Image(https://i.ibb.co/26c5z9h/error-wordpress.png)]]" diego777 Future Releases 57156 Icons missing in iOS Lockdown Mode Administration normal normal Awaiting Review defect (bug) new reporter-feedback 2022-11-19T19:52:21Z 2022-11-21T20:39:34Z "Have you made any progress on a back-end workaround or better explanation for why all of the icons on mobile devices (WordPress, and numerous other third party applications) all have broken ""squares"" on all of these products. The superficial cause is iOS16 in lockdown mode. But it's breaking all of our products including yours. It will get worse when MacOS Ventura gets released into GA and has the same behavior. I suspect it is a result of loading external JS in the https zone, such as previous problems with XSS and mixed content that have broken other web technologies in the past. There is a workaround called ""How to exclude apps or websites from Lockdown Mode"" at the URL below. Best, https://support.apple.com/en-in/HT212650" noexitorescape Future Releases 57943 Massive SQL statement shown in Dashboard WordPress Events and News. WordPress database error Got a packet bigger than 'max_allowed_packet' Administration normal normal Awaiting Review defect (bug) new reporter-feedback 2023-03-17T19:21:55Z 2023-03-17T22:20:25Z "=== Bug Report Massive SQL statement shown in Dashboard WordPress Events and News. WordPress database error Got a packet bigger than 'max_allowed_packet' === Environment - OS: Windows 10 - Server: Apache (WINNT) - PHP: 8.2.0 - WordPress: 6.2-RC2 - Browser: Edge - Theme: Twenty Ten 3.7 - MU-Plugins: None activated - Plugins:   * WordPress Beta Tester 3.3.1   * WP SMS 6.1.1 === Steps to Reproduce Not sure but maybe: 1. Debugging enabled. {{{ define( 'WP_DEBUG', true); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', true ); }}} 2. Set max_allowed_packet to very low value. 3. GO to http://localhost/test/wp-admin/index.php x. 🐞 Bug occurs. === Expected Results 1. ✅ WordPress Events and News should be shown. 2. ✅ If failed a user friendly message shown in GUI 3. ✅ Not to log 18 MB of errors. === Actual Results 1. ❌ Massive SQL statement was shown 2. ❌ User friendly error message was not shown in GUI 2. ❌ Logging was made of 18MB Some few lines from the logfile. {{{ 17-Mar-2023 18:13:23 UTC] WordPress database error Got a packet bigger than 'max_allowed_packet' bytes for query INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ( '_transient_feed_d117b5738fbd35bd8c0391cda1f2b5d9', 'a:4:{s:5:\""child\"";a:1:{s:0:\""\"";a:1:{s:3:\""rss\"";a:1:{i:0;a:6:s:4:\""data\"";s:3:\""\n\n\n\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:s:7:\""version\"";s:3:\""2.0\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:1:{s:0:\""\"";a:1:{s:7:\""channel\"";a:1:{i:0;a:6:{s:4:\""data\"";s:61:\""\n \n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\"";s:7:\""attribs\"";a:0:}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:1:{s:0:\""\"";a:5:{s:5:\""title\"";a:1:{i:0;a:5{s:4:\""data\"";s:16:\""WordPress Planet\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:28:\""http://planet.wordpress.org/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""language\"";a:1:{i:0;a:5:{s:4:\""data\"";s:2:\""en\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:47:\""WordPress Planet - http://planet.wordpress.org/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""item\"";a:50:{i:0;a:6:{s:4:\""data\"";s:13:\""\n \n \n \n \n \n \n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:5:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:39:\""WordCamp Central: WordCamp Buffalo 2023\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:39:\""https://central.wordcamp.org/?p=3163106\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:64:\""https://central.wordcamp.org/news/2023/03/wordcamp-buffalo-2023/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1802:\""WordCamp Buffalo 2023 logo. Design by Ben Dunkle.\n\n\n\n

Buffalo again will host the region’s WordCamp for bloggers and web designers and developers of all skill levels. Novices are very welcome. WordCamp Buffalo will be held Saturday, May 6, 2023.

\n\n\n\n

Registration opens at 8:00am. Sessions begin at 9 a.m. and continue through 5 p.m. This year’s WordCamp will be held at Ken-Ton Elmwood Commons, 3200 Elmwood Ave Suite 110, Kenmore, NY 14217. Tickets are required in advance.

\n\n\n\n

The $25 ticket cost covers WordCamp Buffalo swag, morning coffee, lunch, and the evenings’s after-party food. Participants are strongly encouraged to bring their laptops or tablets. Ticket purchase and program details are available at buffalo.wordcamp.org/2023. The capacity for this event is about 120 people, so getting tickets early is advised.

\n\n\n\n

WordCamps are held worldwide, locally run and purposely at a low cost for accessibility to all. WordCamp Buffalo is dedicated to WordPress, blogging and web facility. WordCamps are sponsored by WordPress, the open-source, free, not-for-profit platform for individuals, groups and businesses to build their own blogs and websites. WordPress.org began in 2003. Its administrators call it the “largest self-hosted blogging tool in the world, used on millions of sites and seen by tens of millions of people every day.”

\n\n\n\n

Similar to previous years, Buffalo’s 2023 WordCamp will divide its workshops along two tracks, with sessions for every ability and level of use.

\n\n\n\n

Speakers will include WordPress users from Buffalo, Rochester, and beyond, with experience ranging from user/blogger to advanced developer.

\"";s:7:\ }}} If you need the full log, let me know but as I don't know what's included I don't want share in the public ticket. " ipajen Future Releases 58478 Text mis-aligned count bubbles on mobile Administration 6.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-06-08T06:56:34Z 2023-06-08T07:19:58Z "Hi, Small UI issue in the mobile device. it is not properly alignment on a mobile device. For more information, you can see mentioned screenshot." sumitsingh Future Releases 44516 Unable to edit theme's file on multisite from default editor Administration 4.9.6 normal normal Awaiting Review defect (bug) new reporter-feedback 2018-07-04T21:38:12Z 2019-12-21T19:50:24Z "I am using WP 4.9.6 and on multisite when I tried editing theme's files from the editor it shows that it generated some fatal error. The actual message is 'Unable to communicate back with site to check for fatal errors, so the PHP change was reverted. You will need to upload your PHP file change by some other means, such as by using SFTP.' Please see: https://prnt.sc/k2mshy" prashantvatsh Future Releases 47465 current_action function - return types Administration 5.3 normal minor Awaiting Review defect (bug) new reporter-feedback 2019-06-03T12:32:37Z 2019-06-06T09:18:44Z "I received a PHP notice ""Array to string conversion"" that led me to the current_action() function in class-wp-list-table.php. This function can return an array as a valid value. For example this request will return an array: http://localhost/site/?action[]=1&action[]=2 But in this case: PHPDoc is incorrect. Should be: {{{ @return string|false|array }}} or/and this may break some of the scripts that use this function. simply because they use the result value as a string. Possible solution: add an additional check: IF array THAN take only the first value of the result. Thanks!" madeinua Future Releases 39003 menu_page_url() not working on Ajax call Administration 4.6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2016-12-01T13:50:38Z 2023-02-20T17:36:29Z `menu_page_url( 'menu_slug', false )` is always returning empty string on AJAX response. The `global $_parent_pages;` is return NULL on AJAX call. But the same menu slug is working on normal page load. vinoth06 Future Releases 45977 on the dashboard, cannot expand/collapse dashboard boxes. Administration 5.0.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2019-01-14T03:25:22Z 2019-02-01T02:43:17Z "I just recently upgraded to 5.0.3 and noticed that I cannot expand/collapse dashboard boxes in admin (with the little triangle button at the upper right corner of boxes) " eynugget Future Releases 57364 remove_meta_box for commentstatusdiv stores null value for comments configuration. Administration 6.1.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-12-21T10:46:15Z 2023-06-17T12:23:15Z "Removing meta box commentstatusdiv for e.g. some user roles stores null value for comments configuration in database, after a user without that meta box stores the post. Example: - post edit as admin **with** commentstatusdiv meta box - meta box commentstatusdiv -> Allow comments is **activated** - Post edit as user **without** commentstatusdiv meta box - save post as user - post edit as admin - meta box commentstatusdiv -> Allow comments is **deactivated**" phlegx Future Releases 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 Future Releases 49714 Explore UI for destructive controls & contexts Travel_girl Administration normal normal Future Release enhancement assigned reporter-feedback 2020-03-27T16:03:04Z 2024-01-29T15:38:05Z "After considering ticket #49603, we think that WordPress should take a look at the consistency of informing users when they are in a destructive context and when a control will have destructive consequences. In general, we have a standing expectation that these controls will be red & have text that clearly indicates the action to be taken, but this should be reviewed for consistency. Reviewing #49603 showed that the 'Force Erase Personal Data' control is blue, which doesn't match expectations. The intention of 49603 is to draw attention to the fact that the 'Erase Personal Data' screen is entirely dedicated to destructive actions. While using a background color to indicate this may not be the ideal choice, the concept is well worth exploring. Summary: review destructive actions & contexts to ensure clarity and maximize error prevention. " joedolson Future Releases 52893 Not possible to filter by category (and/or date) and by author in wp-admin/edit.php Administration normal normal Awaiting Review enhancement new reporter-feedback 2021-03-23T20:01:51Z 2021-09-17T23:18:42Z "Hello == The problem Currently, **in the Posts screen (some.url/wp-admin/edit.php)** I can filter posts by category and/or date. However, that screen shows posts written by other authors. Then, **if I click on my own author to filter out the posts by different authors, the filter by category and/or date is lost**. == Expected behavior When the user clicks on the author, the Posts screen should show the **posts list filtered by category, date AND author as well**. == Additional information In the Posts screen, the link address in my author is **some.url/wp-admin/edit.php?post_type=post&author=authorId**. So, the filter by author is lost because **the actual url parameters for month and category are not being kept in that link address**. However, if in my browser's address bar I add at the end of the url the parameter '&author=' and my author's id, **I get the page keeping the filter by category and/or date AND by author as well**. Thus, WordPress knows how to handle this request, but **there is no way to do it from the Posts screen UI**." rafaelatias Future Releases 38019 Notify site admin when domain or IP changes and Search Engine Visibilty is set to off Administration 3.0 normal normal Awaiting Review enhancement new reporter-feedback 2016-09-10T19:13:23Z 2020-02-15T10:08:59Z "It would be very valuable to me (and some other wp folks too) if I could get an '''email notification''' when a site is moved from '''localhost''' or '''staging''' to '''production''' site and '''Search Engine Visibility''' is set to '''Discourage'''. It could be as easy as setting two options, domain and ip and checking them in some hook. If not matching and SEO off - send email. The possibility of a misfire and an occasional nag is well worth the SEO points, or so the SEO guys say." vaniivan Future Releases 43366 _default_wp_die_handler() Need filter code for update css style. Administration 4.9.4 normal normal Awaiting Review feature request new reporter-feedback 2018-02-20T10:49:46Z 2020-12-20T01:14:28Z "wp-includes\functions.php Line no 2768. " ravipatel Future Releases 57707 "Issue with ""Add New Application Password"" in profile page leading to empty error message" Application Passwords 6.1.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-02-13T18:42:06Z 2023-02-22T11:52:59Z "The issue I would like to report is in the profile page. When I try to ""Add New Application Password"", the request goes to the link ""Site Address (URL)/wp-json/wp/v2/users/1/application-passwords?_locale=user"" instead of the link ""WordPress Address (URL)/wp-json/wp/v2/users/1/application-passwords?_locale=user"". As a result, an empty error message appears if the ""Site Address"" is different from the ""WordPress Address"". [[Image(https://i.ibb.co/8N0B7xF/Screenshot-20230213-092733.png)]]" king-a-s Future Releases 55870 WP App Passwords Should be URL Decoded Application Passwords 5.6 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-05-29T04:05:15Z 2022-05-30T04:52:34Z "Using OAuth 2 based. authentication IETF recommends for [https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1 client id/secrets] URL [https://datatracker.ietf.org/doc/html/rfc6749#appendix-B encoded] forms. Which means, by using some node OpenID clients, we always get `Authorization: Basic urlSafeEncodedBase64String('user:pass')`. This fails to authenticate as [https://github.com/WordPress/wordpress-develop/blob/0a6c37ceb0a86bebf0b287ac12d200e67bbf948f/src/wp-includes/user.php#L474 WordPress doesn't decode] the `user` and `pass` which could also be clientId and clientSecret in OAuth2. This could be solved by using `urldecode( string $str )`. BEFORE {{{#!php .php` and then include them at the top of the root file? stephenharris Future Releases 53146 Bundled Themes: More consistent styling of the search block Bundled Theme 5.7.1 normal normal Awaiting Review defect (bug) assigned reporter-feedback 2021-05-04T00:39:10Z 2023-07-11T04:26:12Z "The search block is missing styling from the theme. The search widget in the footer has the styles in the stylesheet. The search block used on pages and posts does not have styles. The unstyled attributes are: {{{ .wp-block-search .wp-block-search__input .wp-block-search__button svg }}} Image of the search block on a page vs the search bar widget in the footer. [https://t2.dhostingsites.com/wp-content/uploads/2021/05/Screenshot-2021-05-03-5.36.53-PM-e1620088694646.png] [https://t2.dhostingsites.com/search-block-doesnt-have-styles/]" deborah86 Future Releases 52051 Customize shortcut is not visible in mobile view Bundled Theme 5.6 low normal Awaiting Review defect (bug) new reporter-feedback 2020-12-12T21:05:18Z 2022-06-17T08:14:19Z "Hello Guys, Mistake: [https://www.screenpresso.com/=OvQQd] Solution: [https://www.screenpresso.com/=dBanc] please check and let me know Thanks," urvik1 Future Releases 57758 Header > Group background color in adds padding to backend but not front end Bundled Theme 6.1.1 normal minor Awaiting Review defect (bug) new reporter-feedback 2023-02-17T16:41:01Z 2023-05-17T21:40:59Z setting Group background color in header adds padding to backend but not front end frdmsun Future Releases 60612 Twenty Fifteen: mobile menu unresponsive in 3.6 Bundled Theme 6.4.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2024-02-23T00:31:51Z 2024-02-23T12:50:42Z "Hi. I am using the Twenty Fifteen theme at my personal homepage that can be found at https://perbovbjerg.dk When using the 3.6 version of the theme the mobile menu is unresponsive on my phone and tablet. It works fine enough when I simulate a phone or tablet in my browser. But as I rollback to version 3.5 everything works just fine" perbovbjerg Future Releases 59298 Twenty Fourteen : search block is having issue with alignment. Bundled Theme 6.3.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-09-06T14:08:03Z 2023-09-06T21:29:35Z "Steps to reproduce the issue :- 1. Activate Twenty Fourteen theme. 2. Choose Search block. 3. Apply center align and check in front side. 4. Apply Right align and then check in front side. You can able to see that center aligned is having issue. I have attached video for better understanding. Video URL :- https://share.cleanshot.com/6p3TmBFwZ91llFT5V52R" nidhidhandhukiya Future Releases 46948 Twenty Nineteen - JS error on mobile menu when no visible items Bundled Theme normal normal Awaiting Review defect (bug) new reporter-feedback 2019-04-16T15:00:46Z 2019-07-04T14:43:59Z "Looks like there's an issue with the JS that populates the 'more' (...) menu on mobile. If there are no visible menu links inside the main menu on mobile and all of them are inside the 'more' menu, then the JS will break. I do not think this is an issue on a Child Theme. Line 128 priority-menu.js: {{{ prependElement( hiddenList, ! visibleList.lastChild || null === visibleList.lastChild ? visibleList.previousElementSibling : visibleList.lastChild ); }}} Regarding `.lastChild`. The `visibleList` element: {{{ // Adds the necessary UI to operate the menu. var visibleList = container.parentNode.querySelector('.main-menu[id]'); }}} If no items are inside the visible list (and all items are inside the more menu) then `visibleList` will indeed return as a Node, however `lastChild` will return null. This means the value will not be catched properly by this inline condition: {{{ visibleList.previousElementSibling : visibleList.lastChild }}} And `null` will be passed to the second argument of the `prependElement` function when it is not a node - and cause a JS error. _https://wordpress.org/support/topic/javascript-error-on-child-theme/#post-11433882_ " anevins Future Releases 55994 Twenty Seventeen: Header image zooms in when scrolling down on Mobile Safari Bundled Theme normal trivial Awaiting Review defect (bug) new reporter-feedback 2022-06-16T14:44:08Z 2023-06-21T17:40:17Z "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 Future Releases 42848 Twenty Seventeen: Pre-sized Header Media not used Bundled Theme 4.8.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-12-09T00:13:00Z 2021-09-01T23:36:31Z "Theme: Twenty Seventeen Version: current The theme customizer has an option to add Header Media and recommends dimensions of 2000 x 1200 pixels. When images are uploaded, WordPress automatically creates a size 2000 x 1200 pixel. The bug When adding a new header image in the customizer, sizing of the original is still required, i.e. it does not automatically choose the pre-sized 2000 x 1200 image. Steps to replicate: 1. Upload an image. Login to your FTP space and you will see a file sized to 2000 x 1200. 2. Go into customizer, Header Media, Add new image, select the one you just uploaded. Note that it will require you to size it to 2000 x 1200." madriverweb Future Releases 51434 Twenty Twelve: CSS issue with the Columns block padding Bundled Theme normal normal Awaiting Review defect (bug) new reporter-feedback 2020-10-01T23:08:14Z 2020-10-08T21:27:18Z "https://prnt.sc/urk4n3 {{{ .wp-block-columns.alignwide .wp-block-group .wp-block-group__inner-container{ margin: 10px 10px 20px 10px; } }}}" ravipatel Future Releases 52772 Twenty Twenty-One: Block editor from adds overlap option by default to columns Bundled Theme normal normal Awaiting Review defect (bug) new reporter-feedback 2021-03-11T08:28:59Z 2022-07-08T16:26:48Z " When I create a new columns block, the editor adds the overlap option by default, so the class “is-style-twentytwentyone-columns-overlap” gets added. I do not want this, but I can’t seem to get rid of it although the class is not in my inc/block-patterns.php file. I’m using a created child theme for Twenty Twenty One theme (latest version updated on 2021/03/11. The documentation (https://wordpress.org/support/article/twenty-twenty-one/#overlapping-columns) mentions ""an optional style called overlap"" but I get it by default. " shapesgraphicstudio Future Releases 56202 Twenty Twenty-One: Error when displaying the columns on the phone Bundled Theme 6.0 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-07-12T11:42:02Z 2022-07-13T22:59:24Z "Hi, I Have found a problem in my websites. I have been using the basic twenty twenty-one theme, it is up to date as well as the wp version and all my plugins. The columns dont seem to be vizualized properly in phones, even when I tick the box (stack on phones) I have fix it for my self doing a ccs personalization with this, but stil seem to me correct to fix the problem, no to have to use extra css. .wp-block-columns { display: flex; margin-bottom: 1.75em; box-sizing: border-box; flex-wrap: wrap!important; align-items: normal!important; } Unfortunately I dont know coding but maybe some oen from the colaborator could check this. Ill leave some pictures so you know what I mean: [[Image(https://freeimage.host/i/w1EQp9)]] [[Image(https://freeimage.host/i/w1EtIe)]] [[Image(https://freeimage.host/i/w1EbLb)]] " josefigueroa92 Future Releases 53649 Twenty Twenty-One: Footer widget CSS grid Bundled Theme 5.8 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-07-12T19:23:47Z 2023-01-16T12:49:06Z "WordPress 5.8 RC2 When placing a block such as slider using [Slick](https://github.com/kenwheeler/slick) in footer (may happens with other blocks), the width of the footer can be longer than the available on the theme causing to display an horizontal scrollbar and messed up the width of the 3 footer widgets columns. Solution: in Twenty Twenty-One theme, when the CSS Grid columns width is defined, use minmax() in combination with 1fr. {{{ grid-template-columns: repeat(2, minmax( 0, 1fr )); grid-template-columns: repeat(3, minmax( 0, 1fr )); }}} " htmgarcia Future Releases 52277 Twenty Twenty-One: max-width set to none Bundled Theme 5.6 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-01-11T08:49:09Z 2022-01-25T09:23:57Z Max-width property on desktop (Firefox 69) set to none. halny Future Releases 57355 Twenty Twenty-Three Theme bug: marking text in backend is black Bundled Theme 6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-12-19T12:51:47Z 2023-03-06T05:57:26Z "Wordpress.com Twenty Twenty-Three theme Electric Design with change: color 2 blue >> black In the Gutenberg editor or Site Editor: BUG: when I mark text, the marking is black. As the text is also black, it is not possible to see the marked text. This has been in another color in the previous theme (Twenty Twenty-Two). " nmschaller Future Releases 58669 Twenty Twenty-Three: Search input border does not display on font side. Bundled Theme normal normal Awaiting Review defect (bug) new reporter-feedback 2023-06-29T12:59:15Z 2023-09-04T06:59:41Z "I have reviewed Search block in different different themes and I found search input border does not display in frontend side for Twenty Twenty-Three. Please check the below provided video recording for a better understanding. Video Recording: https://share.cleanshot.com/Px5DpDrD3DLYKF1rYVd5" upadalavipul Future Releases 56929 Twenty Twenty-Three: Sticky posts not visually different than regular posts Bundled Theme 6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-10-28T17:14:13Z 2023-03-06T06:17:25Z "When a sticky post exists, it isn't styled differently than other posts. The TT3 theme correctly: - Puts a sticky post as first in the blog roll - Applies the `sticky` class - Also shows the post in the original position, without the `sticky` class This was found when doing QA of the 6.1 release candidate: - https://make.wordpress.org/test/2022/09/21/help-test-wordpress-6-1/ == Replication - Install 6.1 and be sure that TT3 is active - Import the theme unit test data: - https://github.com/WPTT/theme-test-data - Navigate to the posts homepage and note that the sticky post doesn't look visually different than other posts but it does have the correct `sticky` class - Navigate to older posts until you find the sticky post where it should be. Note that it correctly does not have the `sticky` class Here's a screenshot to help visualize: https://i.getf.ly/wbuQpJqn " bgturner Future Releases 59015 Twenty Twenty-Three: Theme failure after updates Bundled Theme 6.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-09T05:03:36Z 2023-09-09T09:38:49Z "I updated WordPress to 6,3 - all OK. I updated Twenty-Twenty-three theme. Twenty-Twenty-three Live Preview returns completely blank screen. (Active theme : Generate Press works fine)" rossbateson Future Releases 55264 Twenty Twenty-Two Looks Bad on Firefox Bundled Theme 5.9 normal critical Awaiting Review defect (bug) new reporter-feedback 2022-02-26T14:51:04Z 2022-03-04T22:35:16Z "There are two issues in twenty twenty-two that I have. Unfortunately, the 1.1 release has not fixed them. Others have reported the same issues to the support forum. I am using a staging site to test and customize the new theme for one of my sites. I am about ready to go public with it but for these issues. The customized theme looks good with the Google Chrome and Microsoft Edge browsers, and on my iPhone. But with Firefox the header navigation bar is always expanded, and the page content appears in plain text. I have made no customization to the fonts or to the navigation bar. The problem must be the way Firefox renders the core code. A less critical issue is that on Chrome and Edge, pages load in plain text before quickly becoming formatted. This is not a disabling issue, as is the Firefox issue, but it is annoying. Where should I go from here? I don’t think I should go online when I can’t deliver a decent looking site to Firefox users." aichedvs Future Releases 56626 Twenty Twenty-Two: Elements with alignfull in the content provoke a horizontal scrollbar Bundled Theme 6.1 normal normal Future Release defect (bug) new reporter-feedback 2022-09-22T16:09:12Z 2023-02-07T09:59:10Z "Add a cover block with full alignment to the content and you'll see a horizontal scrollbar. Current CSS: {{{ margin-left: calc(-1 * var(--wp--custom--spacing--outer)) !important; margin-right: calc(-1 * var(--wp--custom--spacing--outer)) !important; }}} Fix: {{{ margin-left: calc(-0.5 * var(--wp--custom--spacing--outer)) !important; margin-right: calc(-0.5 * var(--wp--custom--spacing--outer)) !important; }}} " markhowellsmead Future Releases 52634 Twenty Twenty: Child Theme Search Modal Safari Throws Error in Parent asset/index.js Bundled Theme 5.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-02-24T02:39:40Z 2021-10-28T04:00:39Z "Twenty Twenty child theme, search modal on safari throws error in parent asset/index.js when search toggle clicked. Works fine in all other browsers. TypeError: null is not an object (evaluating 'modal.querySelectorAll') elements = modal.querySelectorAll( selectors ); null is not an object (evaluating 'modal.querySelectorAll')" wp89mkt Future Releases 54412 Twenty Twenty: Letters move when opening accordion menu Bundled Theme 5.8.1 normal normal Future Release defect (bug) new reporter-feedback 2021-11-10T10:25:53Z 2023-04-28T15:53:28Z "I haven't changed anything, this is the original version of Twenty Twenty. This happens in any browser of the latest version, I have Windows 10. Gif - \\https://gifyu.com/image/ePvd screen - \\https://ibb.co/tX7XjTJ " mike77777 Future Releases 55324 Twenty Twenty: Scroll to top not working Bundled Theme normal normal Awaiting Review defect (bug) new reporter-feedback 2022-03-06T08:56:27Z 2022-06-24T07:11:04Z "For whatever reason, in my installation the scroll to top arrow doesn't work. I changed {{{#!php }}} to {{{#!php }}} and it was working again. Maybe worth patching? Another alternative would be {{{#!php }}} " Presskopp Future Releases 48967 Twenty Twenty: gallery and page cover image overlap each other on iPad audrasjb Bundled Theme 5.3.1 normal normal Awaiting Review defect (bug) reviewing reporter-feedback 2019-12-13T23:19:05Z 2019-12-16T20:42:36Z On iPad, page titles(cover or featured images) and galleries overlap each other. This happens only on the pages that have galleries and only on iPad. They work well on PC and iPhone. juliahsun Future Releases 58836 Remove IE specific checks from more default themes (6.4) Bundled Theme normal normal Future Release enhancement new reporter-feedback 2023-07-18T09:26:42Z 2023-09-12T20:24:03Z "Follow-up to #56699 Remove IE conditional statements and register external resources without enqueuing them for four more themes: - Twenty Eleven - Twenty Twelve - Twenty Fourteen - Twenty Sixteen" sabernhardt Future Releases 52869 Twenty Twenty-One: Text isn't vertically centered to the checkbox Bundled Theme 5.6 normal normal Awaiting Review enhancement new reporter-feedback 2021-03-20T11:20:23Z 2021-04-29T14:44:11Z "I think we should add `vertical-align: middle;` into the line 1344 to have text aligning centerally vertically to the checkbox. Currently the code is like this: {{{ @supports (-webkit-appearance: none) or (-moz-appearance: none) { input[type=checkbox], input[type=radio] { -webkit-appearance: none; -moz-appearance: none; position: relative; width: 25px; height: 25px; border: var(--form--border-width) solid var(--form--border-color); background: var(--global--color-white); } }}} " ooker Future Releases 54985 Twenty Twenty-Two: Add viewport meta Bundled Theme 5.9 normal critical Awaiting Review enhancement new reporter-feedback 2022-01-29T12:45:10Z 2022-01-29T13:26:55Z "Hello, I am a WordPress developer and I developed many sites and custom plugins and themes. We found that in your latest theme which is ""Twenty Twenty-Two"", you don't use a responsive port which is cause issues in the plugin's front-end design so, I request you please add below meta port which is perfect for all plugins and other plugins. Because we need to add manually in our plugin with the 'wp_head' hook I hope you will add meta port. Meta Port: Thank you." divyeshsapariya35 Future Releases 59506 Removed all the layout I had created on the main page Bundled Theme 6.4 normal normal Awaiting Review feature request new reporter-feedback 2023-09-29T18:44:52Z 2024-01-22T11:59:11Z "Al implementar el tema 2024, borró todo lo que había creado en la página principal, de últimas entradas, al menos tengo una página con el mismo diseño; pero fue doloroso, empezaré desde cero. Gracias por su atención. ---- [Google translation]: When implementing the 2024 theme, it deleted everything I had created on the main page, from last posts, at least I have a page with the same design; but it was painful, I'll start from scratch. Thank you for your time." samuelsuiri Future Releases 57463 Twenty Twenty Three has no base styles for Bundled Theme 6.1.1 normal normal Awaiting Review feature request new reporter-feedback 2023-01-14T16:21:03Z 2024-02-02T04:08:55Z "I am seeing that Twenty Twenty Three has no styles period, but I find this strange. As a plugin author who tries my best to inherit the theme's styles.... well that's not possible when there aren't styles. One of my plugins renders a `
` and I would prefer it to look like any other tables on the site, but there is no style to inherit. I tried adding a `wp-block-table` class to a wrapper, but that doesn't help either since the style for the table block is in core and only loads when the table block is present. What's the best suggestion here? I can style my own tables, but then they are destined to look different from the theme and it's not practical to provide different styles for every theme. " helgatheviking Future Releases 53198 Twenty Twenty-One: Why is the verse block not supported? Bundled Theme normal normal Awaiting Review feature request new reporter-feedback 2021-05-13T10:36:08Z 2021-05-13T13:49:09Z "The theme seems to not support the [https://wordpress.com/support/wordpress-editor/blocks/verse-block/ verse block] anymore. This is the style in the editor: {{{ pre.wp-block-verse { padding: 0; color: currentColor; } }}} And here is the style in the frontend: {{{ .wp-block-verse { font-family: var(--entry-content--font-family); } }}} Why is that? " ooker Future Releases 49899 detected an advanced-cache.php file in the wp-content directory. It seems that this is not the advanced-cache.php file. Please remove this file and disable any other caching plugins to use this . Cache API normal normal Awaiting Review enhancement new reporter-feedback 2020-04-13T22:19:40Z 2020-04-14T11:27:37Z "==== How to Reproduce ==== Simply install and activate two cache plugins that use advanced-cache.php file from the admin dashboard one after another. Isn't that time to change how WordPress use the advanced-cache.php file? Why not make wp-settings.php file to look for: /wp-content/*-advanced-cache.php In this way cache plugin developers will be able to create file with their name and functionality such as: /wp-content/-advanced-cache.php In this way there will be no file replacing/removing and etc. and the whole plugin fight on who to use the advanced-cache.php file will be resolved. There will be no problem to have: /wp-content/-advanced-cache.php /wp-content/-advanced-cache.php /wp-content/-advanced-cache.php The other possible (with eventually slower processing) solution is the advanced-cache.php file to be searched for in all of the plugins directory: /wp-content/plugins/* In this way each plugin can store their advanced-cache.php file in their own plugin root folder: /wp-content/plugins//advanced-cache.php /wp-content/plugins//advanced-cache.php /wp-content/plugins//advanced-cache.php And again this will be resolved. Any ideas on that? Thanks in advance." jeffreycooper Future Releases 46388 WP_User::get_data_by(): Cache non-existent users to prevent triggering multiple queries Cache API 5.2 normal normal Future Release enhancement new reporter-feedback 2019-03-01T11:24:01Z 2021-06-15T19:14:20Z "Assume you use the WP_User::get_data_by() function to get the main user fields queried against an ID: {{{ WP_User::get_data_by('ID', 1337); }}} If you call this function multiple times - by calling the function directly or indirectly by using functions like get_userdata or get_avatar - and an user with the given ID does not exist, the database-query is getting executed multiple times resulting in duplicate queries: {{{ SELECT * FROM wp_users WHERE ID = '1337' }}} To prevent triggering multiple queries, non-existing users should get stored inside the WP Object Cache similar as in the get_option() function for non-existing options. The attached patch checks if the user ID exists in the WP Object Cache inside of the notusers-array so the WP_User::get_data_by() function returns FALSE if this is the case: {{{ // Prevent non-existent users from triggering multiple queries $notusers = wp_cache_get( 'notusers', 'users' ); if ( isset( $notusers[ $user_id ] ) ) { return false; } }}} If the user is not existent in the notusers-array but he also does not exist inside of the database, the user gets added to the WP Object Cache before the WP_User:get_data_by() function returns FALSE: {{{ // User does not exist, so we must cache its non-existence if ( ! is_array( $notusers ) ) { $notusers = array(); } $notusers[ $user_id ] = true; wp_cache_set( 'notusers', $notusers, 'users' ); }}} " Asgaros Future Releases 53310 All Comments are not visible in comment section in WordPress Backend Post Section Comments 5.7.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-05-31T15:25:09Z 2021-06-25T07:21:03Z "All Comments are not visible in comment section in WordPress Back-end Post Section - Ex : 1. If I have 104 Comment in My Post then I am able to see only latest 100 comment 2. If I have 21 Comment in Post then I am able to see only 20 comments **Reference Video Link:** https://www.loom.com/share/45c015457f81401ea4cabbb562c5ef34 **Note : This issue occurs in Backend post section**" shailu25 Future Releases 48724 Button text type when editing a comment Comments normal normal Awaiting Review defect (bug) new reporter-feedback 2019-11-19T12:21:37Z 2019-12-05T05:29:09Z "When editing a comment in wp-admin the button to update says ""Update How"" instead of Update Now. As per attached screenshot. (on latest WordPress 5.3)" tchburn Future Releases 52875 If a post is in trash related comments cannot be removed or trashed Comments normal normal Awaiting Review defect (bug) new reporter-feedback 2021-03-21T08:27:43Z 2023-03-29T18:53:32Z Comments to trashed or removed posts need to be visible with a clear note in the 'In response to' column that they are related to the trashed/removed post. oglekler Future Releases 51589 Missing whitespace between comment reply title and cancel comment reply link Comments normal normal Awaiting Review defect (bug) new reporter-feedback 2020-10-21T17:55:10Z 2020-11-08T15:13:16Z "Hi, There's a missing whitespace between the comment reply title and the cancel comment reply link. This results in: ""Reply to A WordPress CommenterCancel reply"". The {{{cancel-comment-reply-link}}} is wrapped in {{{}}} tags. In file comment-template there's a whitespace before the opening tag: {{{'cancel_reply_before' => ' ',}}} But somehow it's being ignored in comment form. Stripped perhaps? Was not able to find what causes this. More info here: https://wordpress.org/support/topic/cancel-comment-reply-link-in-comments-form/." Guido07111975 Future Releases 41788 PHP Fatal error: Call to a member function has_cap() on a non-object in wp-includes/comment.php Comments 4.8.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-09-03T22:16:34Z 2020-12-14T19:20:14Z "{{{#!php if ( ! empty( $commentdata['user_id'] ) ) { $user = get_userdata( $commentdata['user_id'] ); $post_author = $wpdb->get_var( $wpdb->prepare( ""SELECT post_author FROM $wpdb->posts WHERE ID = %d LIMIT 1"", $commentdata['comment_post_ID'] ) ); } if ( isset( $user ) && ( $commentdata['user_id'] == $post_author || $user->has_cap( 'moderate_comments' ) ) ) { }}} If get_userdata() returns false, this code can lead to a fatal error." kirbyde Future Releases 54621 Unsaved comment warning without any changes made when click on Publish, Update or Preview Buttons Comments 4.6 normal major Awaiting Review defect (bug) assigned reporter-feedback 2021-12-14T14:42:58Z 2022-03-18T16:47:44Z "Hi Team, I got unsaved comment changes warning without any changes made in the content of the custom post type post, here is screenshot: https://i.imgur.com/PQmirDL.png I see new codes are added in the WordPress core file: wp-admin/js/edit-comments.js And there is some condition issue, the code is have strict equality comparison operator to undefined ID which is not present in the custom post type: #replyrow Screenshot: https://i.imgur.com/kAHNkrs.png Please review it. Thanks" askaryabbas Future Releases 58604 title_reply_to Value of comment_form() Function Isn't Working Comments 6.2.2 normal major Awaiting Review defect (bug) new reporter-feedback 2023-06-22T18:37:20Z 2024-01-10T11:48:50Z "Hello everyone, friends; I encountered a problem when customizing the comment form. If I add the **title_reply_to** value to the **comment_form()** function, get the **reply_to_text** value in the **get_comment_reply_link()** function. Has anyone had this problem before? Or am I experiencing this problem due to an error? {{{#!php '...', ); $args = array( 'title_reply' => __('Leave a Reply', 'xxx'), // This value works 'title_reply_to' => __('Leave a Reply to %s', 'xxx'), // This value doesn't work 'title_reply_before' => '

', // The problem is when I add an icon to this value 'title_reply_after' => '

', 'fields' => apply_filters('comment_form_default_fields', $fields) ); comment_form($args); }}} " metinmete Future Releases 45998 Comments trashed after reply Comments 5.0.3 normal normal Awaiting Review enhancement new reporter-feedback 2019-01-16T02:58:34Z 2019-01-16T16:42:52Z "I found A Bug into your software. Which is Whenever I click on **Approve and Reply** option in comments, then it's automatically trashed.. Please Fix it." pkkarn Future Releases 60533 The comment tree is old – maybe it’s worth changing it? Comments normal normal Awaiting Review enhancement new reporter-feedback 2024-02-13T19:54:34Z 2024-02-20T02:26:48Z "Maybe it’s worth considering a new approach to comments on WordPress? It’s about the tree – the rooting of comments. Currently it may be level 10. And later there is no reply button – because they usually get narrower. Or maybe it’s worth ending this rooting and switching to something – where every statement will be treated as a response. Completely without roots and their depth – which has been causing problems in long conversations for years. Maybe it would be worth creating it like on the forums – i.e. on a completely different system, without this limitation. Isn’t it worth thinking about? Sometimes conversations are long and it’s a real pain to keep talking to anyone on WordPress. Because – either they are becoming narrower – or the comment ends after the 10th comment – because it cannot be moved as a child. It is probably worth changing it to some other approach, more known from forums – where the number of comments and conversations as – answer to answer does not matter how many of them there are." Danishsard Future Releases 43183 wp-comments-post.php endpoint support for OPTIONS Comments normal normal Awaiting Review enhancement new reporter-feedback 2018-01-30T17:13:04Z 2019-07-01T12:24:37Z "Under some circumstance we may need cross-posting from one domain to another (without the wp-json API). At least lets preflight requests flow normally https://github.com/WordPress/WordPress/pull/338 " drzraf Future Releases 57534 Cron events stop working after PHP 8.0 update Cron API 5.9 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-01-23T18:37:56Z 2023-08-08T16:18:52Z "Hello, I noticed that all wordpress cron events cease ruining upon migrating to PHP 8.0. When I change back to 7.4 the crdo events resume. " domagron Future Releases 57589 transition_post_status hook does not fire when cron publishes scheduled post. Cron API 6.1.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-01-30T22:32:39Z 2023-01-31T20:16:19Z "Ever since the most recent 6.1 update, a critical hook of ours is not firing any more. We have a custom cache clearing plugin that clears the nginx, redis and Cloudflare cache for a bunch of our landing pages. It runs on our site when a post's status changes from from 'future' to 'publish', from 'publish' to 'trash' or when a post is originally published of updated. We use the transition_post_status hook to trigger these cache clears. Everything was working great until the 6.1/6.1.1 updates. After the wp 6.1 update, the manual publish/update operations done directly using the wp-admin work fine, but when our cron runs to publish a scheduled post the transition_post_status hook does not fire at all. But here is the most curious thing... the ""publish_future_post"" cron job is not created when we schedule a post for the future. The function check_and_publish_future_post() uses this cron job to decide what posts need to be published, but the cron job never appears in my action scheduler or in my events tab of the wp-control plugin. So that mean that the wp_publish_post() function does not run, and the filter hooks don't fire. But the post DOES publishes as expected on the wp-cron. It is beyond weird, and i cant figure it out. Here is what I have done and tested thus far: I have tested all of the following hooks: none of them work either: - transition_post_status - future_to_publish - future_post I am using a manual cron fired from my ubuntu server, and I have confirmed my cron is firing using an output.log, and I can also confirm that other wp-cron jobs are running as as normal. I have tried both a conventional wget 'doing_wp_cron' and a wp-cli cron jobs, and both fail (see examples below): - * * * * * wget -q -O - --no-check-certificate https://domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1 - * * * * * cd /path/to/www; /usr/local/bin/wp cron event run --due-now >/dev/null 2>&1 In order to get back to where we were, I have had to spin up my own cron that publishes future posts myself, so I have solved this issue on my end, but I cannot be the only one experiencing this, so I thought that I would submit this information for your review, thanks!" tele2rn Future Releases 32306 wp-cron throws 500 errors for SSL enabled sites Cron API 4.2.1 normal critical Awaiting Review defect (bug) reopened reporter-feedback 2015-05-08T07:49:05Z 2017-11-14T14:01:53Z "I have several WP installs that are throwing 500 error codes when calling wp-cron.php after a pageview. The error is not consistent - it will sometimes return 200, and sometimes 500. All the installs I see this on use SSL with properly signed certs with SNI in use on the server under Apache. Instances on the same server where do not use SSL have not shown this issue at all. I have managed to reproduce this on a clean WP install running twentyfifteen with no plugins installed so it doesn't appear to be plugin related. Oddly, I don't get any PHP warnings when it happens (though I've tested that if I force a php script in the same pool to throw an error, it does get captured) - I do get the following recorded in the Apache Virtualhost error log (redacted): [Fri May 08 08:29:34.479946 2015] [core:error] [pid 13870:tid 140644332824320] [client xxxx:xxxx:x:xx:xxxx:xx:x:x:57492] AH00524: Handler for fastcgi-script returned invalid result code 32 Apache access log (redacted): xxxx:xxxx:x:xx:xxxx:xx:x:x - - [08/May/2015:08:29:26 +0100] ""POST /wp-cron.php?doing_wp_cron=1431070166.8151741027832031250000 HTTP/1.0"" 500 4066 ""-"" ""WordPress/4.2.2; https://www.domain.com"" System config is as follows: * Fully patched Debian Jessie running on amd64 arch with kernel 3.16.0 * Webserver: Apache/2.4.10 (Debian), mod_fastcgi/mod_fastcgi-SNAP-0910052141, mod_fcgid/2.3.9, mod_python/3.3.1, Python/2.7.9, OpenSSL/1.0.1k * MySQL 5.5.43-0+deb7u1 * PHP 5.6.7+dfsg-1 running under PHP-FPM (seen with and without opcache in place) * Wordpress 4.2.2 fresh install (also seen on 4.2.1) with all plugins removed. The server listens both on IPv4 and IPv6 - I've tried forcing wp-cron to use IPv4 by setting the hostname in /etc/hosts but that makes no difference. Refer also to : https://wordpress.org/support/topic/wp-cron-throwing-500-errors-on-ssl-sites?replies=9" coatesg Future Releases 57521 Appearance -» Customize not working after update 5.8 Customize normal normal Awaiting Review defect (bug) new reporter-feedback 2023-01-21T17:47:59Z 2023-02-22T18:11:18Z "The appearance -» customize is not working after wordpress update to version 5.8 and above. The only thing that appears in the info is ""your are customising"" but the menu and submenus doesn’t appear or load. I tried to uninstalled all plugins, used the default themes (Twenty Twenty 2.1 and Twenty Twenty-One 1.7) but it still doesn’t work. I tried on versions 5.8, 5.9, 6.0 and 6.1. Only in version 5.7 it working normally! In the server is installed PHP version 7.4. Thanks for the help!" va2m Future Releases 57899 Bad javascript in customize-controls.js for padding-top causes bugs Customize normal normal Awaiting Review defect (bug) new reporter-feedback 2023-03-09T23:06:44Z 2023-03-21T16:38:35Z "The code for sections ""Release header element if it is sticky."" and ""Reset position of the sticky header."" is very bad old code and should be coded in a more modern way now. This code causes bugs in many situations and should either be eliminated all together and replaced with modern css only/instead or improved javascript to not include a forced css for padding-top." akissz Future Releases 55686 Blank sheet when I try customuze site. I can't see prewiev changes Customize 5.9.3 normal critical Awaiting Review defect (bug) new reporter-feedback 2022-05-05T15:49:52Z 2022-05-07T02:51:09Z "WordPress 5.9.3 This problem occur even when I deactivate all plugins and use the default theme. server on Plesk I install Wordpres, but i don't know how to solve this problem. " lesenkotetiana Future Releases 43444 CSS Editor Error Not Displaying Correctly Customize 4.9 normal normal Future Release defect (bug) new reporter-feedback 2018-02-28T22:55:14Z 2019-12-05T04:48:01Z "Every time I’m making a change in the custom CSS I get this annoying message that should only appear when I’m ready to publish changes. When I click publish and there’s errors, that’s when this notification needs to appear. I get it when I’m in the process of editing CSS and it always throws off my position when and I lose the location of where I was editing. It’s even worse when Inspect Element is pulled up. It should ONLY be giving me an error message when I’m going to publish the CSS changes. It’s literally notifying me of errors when I’m not finished editing the CSS. When I click “Publish” it needs to be notifying me of errors and then to confirm, not make me lose my placement and give me an error when I’m not even finished writing out what I need to… Screen capture: https://www.youtube.com/watch?v=cWyD4cYfpEA" nistuj817 Future Releases 56825 Customiser colour picker and popups broken in 6.1 RC1 Customize normal normal Awaiting Review defect (bug) new reporter-feedback 2022-10-14T15:10:39Z 2022-10-18T08:35:55Z "When using the customiser, and selecting a colour, using a colour picker, in the 6.1RC1, the colour selector hovers under the page, rendering it badly, and making it hard to make changes within the colour picker. Here is how it looks in 6 https://www.bathroom-images.com/wp-content/uploads/2022/10/Wordpress_6.png Here's how it looks in 6.1 https://www.bathroom-images.com/wp-content/uploads/2022/10/Wordpress_6__RC1.png As you can see, it's obscured by the scrollbar, making the editing of colours impossible. It seems to happen to all of the popups for editing things in the customiser, killing usability. https://www.bathroom-images.com/wp-content/uploads/2022/10/typography_6_1_RC1.png Showing a typography selector drifting offscreen to the left, making it unusable. I noticed this issue in Gutenberg releases before, when testing, so it's somewhere inside the Gutenberg part of the code. Sorry I'm not technical enough to identify the cause." tecazwebdev Future Releases 31980 Customizer Theme Switcher Details Modal: previous/next/close buttons require double taps on IOS Customize 4.2 normal normal Future Release defect (bug) new reporter-feedback 2015-04-15T14:33:53Z 2021-05-22T20:12:17Z "Per comment:34:ticket:31794, there's an issue where double taps are required to trigger the previous/next/close buttons in the theme details modal. " DrewAPicture Future Releases 46301 Customizer iframe warning Customize 5.1 normal minor Awaiting Review defect (bug) new reporter-feedback 2019-02-21T22:46:34Z 2021-05-30T19:44:25Z "The preview in customizer (customize.php) causes a warning message in the browser console: An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing. Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive." mensmaximus Future Releases 43585 Dynamically created setting not received on previewer Customize normal normal Future Release defect (bug) new reporter-feedback 2018-03-20T14:38:12Z 2019-12-15T04:40:24Z "I try to create dynamic setting & control on customizer, but setting is not propagated on previewer when setting created. Setting that dynamically created will only available on previewer when previewer refreshed. i create a simple plugin to explain this issue : https://gist.github.com/jegbagus/e6bfe04fe45f4fa91b1fdc1c3b5b7a89 please take a look at browser console to see the message" jegbagus Future Releases 52208 Favicon - Error when choosing / cropping an image Customize 5.6 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-01-03T11:47:53Z 2022-05-05T07:33:08Z "Hi, Steps to reproduce (using either Firefox or Chrome, latest versions in both cases): - WordPress 5.6 (Theme Twenty Fourteen 3.0) - Go to change the favicon of your theme - Select any image in the media library Two issues happen from here: - If your image is already 512x512px then nothing happens, you can not choose the image, you get stuck in the media library. - If your image is not already a square one, you can crop it but when hitting ""crop"", an error shows up (and no issues appear in the debug console) => https://i.ibb.co/sgqhHsx/Word-Press-Favicon.jpg I'm not sure if this issue is related to WordPress 5.6 or if it was already there before 5.6. I'm also not sure if the theme might be related to this issue as I haven't tested other themes. Thank you for your help. BR, Stephane." stfa76 Future Releases 57170 Fix invalid menu-item-parent Customize normal normal Future Release defect (bug) new reporter-feedback 2022-11-21T23:16:13Z 2024-02-05T20:37:38Z "Follow up to #56926. There seems to be a bug in the Customizer that may set `$menu_item->menu_item_parent` to be the same as `$menu_item->ID`. Steps to reproduce: https://core.trac.wordpress.org/ticket/56926#comment:21. There also seems to be a related JS error: {{{ Uncaught TypeError: parentControl is undefined .../wp-admin/js/customize-nav-menus.js?ver=6.2-alpha-54642-src:2330 }}} " azaozz Future Releases 35559 Image wrapped in anchor disappear in Customizer (Safari) Customize 4.4 normal normal Awaiting Review defect (bug) new reporter-feedback 2016-01-21T13:40:20Z 2021-05-23T18:52:05Z Medium and large size images that set as a featured images displaying through the_post_thumbnail disappear when viewing from customizer if height is not set strictly (400px for example). It disappear time to time – try to reload page or click menu links to update customizer window. halftones Future Releases 51962 Race condition in wp_get_custom_css_post() would clear the custom CSS entry Customize 4.7 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-12-08T03:11:04Z 2020-12-08T04:59:57Z "Our production system was recently affected by a (what it looks to me) race condition in `wp_get_custom_css_post()`; for reference here's the code in question: {{{#!php if ( get_stylesheet() === $stylesheet ) { $post_id = get_theme_mod( 'custom_css_post_id' ); if ( $post_id > 0 && get_post( $post_id ) ) { $post = get_post( $post_id ); } // `-1` indicates no post exists; no query necessary. if ( ! $post && -1 !== $post_id ) { $query = new WP_Query( $custom_css_query_vars ); $post = $query->post; /* * Cache the lookup. See wp_update_custom_css_post(). * @todo This should get cleared if a custom_css post is added/removed. */ set_theme_mod( 'custom_css_post_id', $post ? $post->ID : -1 ); } } else { }}} Our database went down after retrieving the `$post_id` from options. `get_post()` failed silently followed by `new WP_Query( $custom_css_query_vars );` that failed too while the DB was down. Eventually the DB became available and the `custom_css_post_id` setting was set to `-1`. As a result our website's styling was affected until we were able to restore the custom CSS stored in the `custom_css` post. I think better error handling within the `wp_get_custom_css_post()` could prevent such side effect from taking place." candrei Future Releases 45669 Theme Default Suggested Header Image Not display Customize 5.0.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2018-12-17T08:03:45Z 2019-11-09T09:15:31Z " After Theme Setup, changes on default we select default image will not save after the publish of suggested image in customize section in every them i tested please resolve this bug." deepaksk45 Future Releases 46352 Using a single quote locks up UI Customize normal normal Awaiting Review defect (bug) new reporter-feedback 2019-02-26T20:52:41Z 2021-12-15T06:11:40Z "Using the latest versions of WP and WC, and the Twenty-Sixteen theme while updating the appearance, and entering the Site Header Tagline, I tried to use a single quote. The entire UI locks up and goes to la-la land.. After a few Chrome says ""this page is unresponsive..."" Thought maybe someone might like to know about it.. Havent tried other themes or text lines.. Thanks " grampysbbq Future Releases 53854 When opening Appearance/Customize, a different theme is activated, destroying all settings Customize normal normal Awaiting Review defect (bug) new reporter-feedback 2021-08-01T20:33:19Z 2021-08-02T00:16:08Z "Hi there: Twice today, I have clicked on Appearance/Customize and the site has activated a completely different theme, destroying all my settings and necessitating a complete site restore. Twice. The first time, I thought I'd clicked on a wrong button, but this second time I was careful. It's definitely a bug! Tracy Cooper-Posey Site where the error was produced: https://StoriesRulePress.com" TracyCP Future Releases 44511 Widgets generated by wp_register_sidebar_widget can not be add via customizer Customize 4.9.6 normal major Future Release defect (bug) new reporter-feedback 2018-07-04T10:47:29Z 2022-04-22T03:50:54Z "Single use widgets, generated by `wp_register_sidebar_widget` and managed by `wp_register_widget_control` always return an ""Invalid value"" error in Customizer. They also block saving in Customizer. **We still can add them via appearance/widgets.php and go back to customizer.** Example to reproduce: {{{#!php 'POC for Customize bug' ) ); wp_register_widget_control('poc_widget', 'poc_widget', 'poc_widget_control'); } function poc_widget_display(){ echo '

POC for Customize bug

'; } function poc_widget_control(){ echo '

You should see a red notice ""Invalid value"" just above

'; } }}} " bastho Future Releases 43122 customize.php fails to load with default changeset_uuid bpayton Customize 4.7 normal normal Awaiting Review defect (bug) assigned reporter-feedback 2018-01-18T00:46:13Z 2021-05-30T17:26:42Z "I am seeing a rare condition where users are unable to load the Customizer with no specified changeset and see the message ""Cheatin, uh? This changeset cannot be further modified."" In all cases, I am seeing two `customize_changeset` posts with the same GUID post name, one with draft status and the other with published status. When WP_Customize_Manager attempts to find a changeset to load by default, it finds the draft with the GUID, and when it attempts to load the post, it finds the published post with the same GUID and dies with the message mentioned above. I read WP_Customizer and theorized how this could be happening but have no theory worth mentioning. Still, this seems like some kind of race condition." bpayton Future Releases 60228 has_published_pages method does not always return intended result Customize 6.0 normal minor Awaiting Review defect (bug) new reporter-feedback 2024-01-10T18:07:22Z 2024-01-11T08:06:10Z "The has_published_pages method in class-wp-customizer-manager.php has the potential to return an inaccurate result. It only checks the retrieval of a single page. Thus if there are any 'get_pages' filters utilized to remove that first page from the return, then the has_published_pages method returns false when there are other published pages. Even if there are tens of pages published the function will still return false if that first page is filtered out of the get_pages call. This potentially inaccurate return can cause the Homepage Settings sub-menu to disappear from the Appearance->Customize menu. A more accurate measure of if the user has published pages would not rely on a single page." sconroy Future Releases 32768 Customizer Widgets and Themes search improvements Customize 4.2 normal normal Future Release enhancement assigned reporter-feedback 2015-06-23T18:06:29Z 2021-05-22T20:29:24Z "Widgets and Themes search would need the same improvements done for the Menu Customizer. Widgets: - activating ""Add a Widget"" with the Space bar doesn't prevent the default action, as a result the search field gets a space character and the placeholder text is gone. See https://github.com/voldemortensen/menu-customizer/issues/107 Both: - the search results (or no results) should be announced to assistive technologies, possible use case for wp.a11y.speak see #32720 - a short description of the ""live"" search functionality could help, see the Menu items search in core, i.e.: aria-describedby=""menu-items-search-desc""" afercia Future Releases 52648 Problem with certain passwords not working to login to mysql db Database 5.2 normal major Awaiting Review defect (bug) new reporter-feedback 2021-02-25T03:26:23Z 2021-02-25T14:41:39Z "After migrating my WordPress blog from 1and1 hosting to a FAMP server the blog would not come up and complained it couldn't connect to the database. When the database was migrated the same username and password were retained from the 1and1 site. I traced the problem to wp-db.php in wp-includes on the following line: @mysqli_real_connect( $this->dbh, $host, $this->dbuser, $this->dbpassword, null, $port, $socket, $client_flags ); By hardcoding this password into this line: @mysqli_rea$this->dbpasswordl_connect( $this->dbh, $host, $this->dbuser, ""SpivknocKs3%"", null, $port, $socket, $client_flags ); The WordPress blog would come up. (Note this is no longer the password for the database.) I also echoed $this->dbpassword and it was the same as the hard coded password but only the hardcoded version of the password would allow a connection to the database. I changed the password for the database to one containing only upper and lowercase characters and numbers and it would connect fine and the blog would work. The problem was not quite this easy however. It also depended on whether I was logging in as ""user""@""localhost"" or ""user""@""127.0.0.1"". Both users existed on the mysql database and both had the same GRANTS. I tested the mysqli_real_connect() call independent of WordPress using the CONSTANT declarations from wp-conf.php pasted into the php manual reference code for this call and got similar results. I had moved the blog to a server running FreeBSD 12, apache 2.4, php 7.4, and mysql 5.7 when this problem started. I am currently running WordPress 5.2.9 running Arclite theme." kellnerp Future Releases 56533 dbDelta() ignores changes to column nullability (NULL/NOT NULL) Database 6.0.2 normal major Awaiting Review defect (bug) new reporter-feedback 2022-09-08T12:04:42Z 2022-09-08T12:32:28Z "`dbDelta()` ignores changes to the nullability of columns. Test case: {{{#!php query(""DROP TABLE dbdelta_bug_test""); $wpdb->query($create); require_once ABSPATH . 'wp-admin/includes/upgrade.php'; dbDelta($update); }}} **Expected result:** Column `value` is nullable. **Actual result:** `dbDelta()` doesn't detect any changes to the table. " matt_fw Future Releases 59172 wp_query meta_query NOT EXISTS not creating correct sql query Database 6.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-23T12:53:28Z 2023-09-05T16:55:37Z "With the following wp_query: {{{#!php ""ids"", ""post_type"" => ""shop_order"", ""post_status"" => array('wc-processing'), ""posts_per_page"" => ""-1"", ""offset"" => ""0"", 'meta_query' => array( 'relation' => 'AND', array( 'key' => 'scg_is_glass', 'value' => ""1"", ), [ 'relation' => 'OR', [ 'key' => 'scg_processed', 'value' => ""0"", 'compare' => '=', ], [ 'key' => 'scg_processed', 'value' => ""0"", 'compare' => 'NOT EXISTS', ], ] ), 'date_query' => array( array( 'after' => date('Y-m-d', strtotime('-1 month')), ), ), ); }}} The outputeed sql query is the following: SELECT wp_posts.ID FROM wp_posts LEFT JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id ) LEFT JOIN wp_postmeta AS mt1 ON ( wp_posts.ID = mt1.post_id ) LEFT JOIN wp_postmeta AS mt2 ON ( wp_posts.ID = mt2.post_id AND mt2.meta_key = 'scg_processed' ) WHERE 1=1 AND (wp_posts.post_date > '2023-07-23 23:59:59') AND ( ( wp_postmeta.meta_key = 'scg_is_glass' AND wp_postmeta.meta_value = '1' ) AND ( ( mt1.meta_key = 'scg_processed' AND mt1.meta_value = '0' ) OR **mt2.post_id IS NULL** ) ) AND wp_posts.post_type = 'shop_order' AND ((wp_posts.post_status = 'wc-processing')) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC If you looked at the bolded (mt2.post_id IS NULL) above you would expect it to be: **( mt2.meta_key = 'scg_processed' AND mt2.meta_value IS NULL )**" anteatersa Future Releases 44163 wpdb->update() fails, showing no error message Database normal normal Awaiting Review defect (bug) new reporter-feedback 2018-05-20T18:54:05Z 2018-05-21T13:52:46Z "It's my second report about the incompletness of wpdb->update function. 1-2 years ago I've reported the scenario when it failed to update, but `last_error` was empty. Now, another scenario, when it fails , but `last_error` is empty, is the following: i.e. create a table with ""NOT NULL"" {{{#!php query(""CREATE TABLE IF NOT EXISTS `example_table` ( `rowID` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(150) NOT NULL, `id` varchar(150) NOT NULL, `data` LONGTEXT NOT NULL DEFAULT '', PRIMARY KEY (`rowID`), UNIQUE KEY `rowID` (`rowID`) ) "". $wpdb->get_charset_collate() ."" AUTO_INCREMENT=1;"" ); }}} then insert some empty value: {{{ $wpdb->insert(""example_table"", array(""name"" => ""James"", ""id""=>""123"", ""data""=>""blabla"") ); }}} then try to update {{{ $wpdb->update(""example_table"", array(""name""=>""Jonathan""), array(""id""=>""133"") ); }}} it doesnt update. I have dumped `$this->dbh` (in wp-db.php 1887 line), and it shows affected lines: 0 `last_error` is empty. After spending much time, found that I was missing ""required"" parameter and added {{{ $wpdb->update(""example_table"", array(""name""=>""Jonathan"", ""data""=>""new-blabla""), array(""id""=>""133"") ); }}} (""NOT NULL"" requirement caused failure) so, it's good, last_error contained some information, when affected lines are 0, or like such scenarios." tazotodua Future Releases 46947 ‘❤’ in Comment Generates DB Error Database 5.1.1 normal normal Future Release defect (bug) new reporter-feedback 2019-04-16T13:02:03Z 2019-04-17T11:51:53Z "I got the following error message notice when a post comment included the ‘’ special character. When I approved the comment, there was no further error message generated. I have not seen this message before – but then again, we rarely get special character in comments. I am using WordPress 5.1.1. The WP-config: ‘define(‘DB_CHARSET’, ‘utf8′);’ Can someone please advise how to fix this? Regards and thanks, Angus Error message: *** [Thu Mar 21 02:17:57.574584 2019] [php7:notice] [pid 24789] [client 68.40.22.245:41759] WordPress database error Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8mb4_unicode_ci,COERCIBLE) for operation ‘=’ for query SELECT comment_ID FROM xxxcomments WHERE comment_post_ID = 134978 AND comment_parent = ‘0’ AND comment_approved != ‘trash’ AND ( comment_author = ‘Rhonda Lott’ AND comment_author_email = ‘xxx@yahoo.com’ ) AND comment_content = ‘Amen And Amen! Thank you Rabbi!\xe2\x9d\xa4\xf0\x9f\x94\xa5\xf0\x9f\x92\xaf\xf0\x9f\x99\x8c’ LIMIT 1 made by wp_handle_comment_submission, wp_new_comment, wp_allow_comment, referer: https://www.hiskingdomprophecy.com/its-time-to-unearth-the-truth/ ***" HisKingdomProphecy Future Releases 52253 New filter on wp-db.php Database normal normal Awaiting Review enhancement new reporter-feedback 2021-01-08T05:03:34Z 2021-01-08T18:54:25Z "I need to filter the database returned rows for a plugin I am developping. I cannot accomplish the functionality with current filters. I think that other devs may benefit from these couples of filters I propose. These lines of code placed in substitution of lines 2001 to 2006 of wp-db.php do the job. {{{ $this->last_result[ $num_rows ] = $row; /** * Filters the database returned row in a mysqli context. * * @since 5.6.1 * @param object $row Database fetched row. * @param string $query Database query. */ $row = apply_filters( 'returned_row_mysqli', $row, $query ); $num_rows++; } } elseif ( is_resource( $this->result ) ) { while ( $row = mysql_fetch_object( $this->result ) ) { $this->last_result[ $num_rows ] = $row; /** * Filters the database returned row in a mysql context. * * @since 5.6.1 * @param object $row Database fetched row. * @param string $query Database query. */ $row = apply_filters( 'returned_row_mysql', $row, $query ); $num_rows++; }}} Thanks in advance." guelben Future Releases 49028 Provide functionality to suppress $wpdb query filter Database 5.4 normal normal Awaiting Review enhancement new reporter-feedback 2019-12-18T12:41:59Z 2020-02-08T13:52:34Z "The custom query class `wpdb` methods (`get_col`, `get_car`, `update`, `delete`...) all use the underlying `query` method which (since WP 2.1) has a filter hook 'query' which allows modification of the sql query. Some queries are specific to the internals of a plugin's functionality and are not meant to be exposed to other plugins/functionality, however, currently, there is no mechanism to suppress this filter. Would it make sense to add a boolean flag on the `$wpdb` instance which would allow developers to suppress any query modification? Something like `$wpdb->suppress_filters` which would be set to false by default." aurovrata Future Releases 40675 Accented letter at end of line displays wrong Editor 4.7.4 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-05-05T09:48:17Z 2020-11-24T06:25:54Z "In WordPress (last version) if a line of text '''ends with an accented letter''' (ie ""Università""), the accented letter is displayed as a ""?"" (unknown character). If replaced with à it displays correctly. It happens on all wordpress sites I have (different plugins, different themes)." niente0 Future Releases 57289 Allow child themes to use template parts from parent themes in Full Screen Editor Editor 6.1.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-12-07T05:34:05Z 2022-12-13T16:50:08Z "Creating template parts in a theme for the Full Site Editor does not allow template parts from a parent theme to be used by a child theme. These will show when editing a template, and allow you to insert/update/delete them when editing templates, but an error message shows on the public-facing page - ""Template part has been deleted or is unavailable: *template-name*"". All that is needed is an additional check if a child theme is active and if so check against the parent theme as well as the child theme." catacaustic Future Releases 49382 Big span gap appears before feature SVG img in Gutenberg editor Editor 5.3.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-02-07T11:35:59Z 2020-12-07T05:33:12Z "After I inser SVG featured image to the post, appeared span tag () before img tag. It makes a huge gap before image. See the screenshot here: https://imgur.com/a/08MAGvG " MorgunovVit Future Releases 52049 Block editor borders disappeared Editor normal major Awaiting Review defect (bug) new reporter-feedback 2020-12-12T18:31:33Z 2020-12-14T19:16:20Z "All I see in the editor after updating to 5.6 is a long html code. It is such a pain to edit the website like that. So please, please bring back the separate scrollable boxes with borders. Thank you! " ldstudi Future Releases 59896 Block editor default styles not loaded when stylesheet with the same name as the theme is registered Editor 6.4 normal normal Future Release defect (bug) new reporter-feedback 2023-11-13T16:59:09Z 2023-12-18T21:42:36Z "I've got a custom theme that lives in a directory called ""coderpad"". Inside the theme I load a custom stylesheet with the handle ""coderpad"" which is registered via the ""init"" hook and enqueued via the ""wp_enqueue_scripts"" hook. I don't load any sort of custom editor styles as part of this theme. After upgrading to WordPress 6.4 the block editor fails to load any default styles. The content in the editor looks like a big wall of text without any formatting. My simple workaround is to only register the stylesheet when it's not an admin request: {{{ if ( ! is_admin() ) { wp_register_style( 'coderpad', get_template_directory_uri() . '/assets/css/coderpad.min.css', array(), null, 'all' ); } }}} This issue also appears to not happen if I rename the stylesheet handle to something like ""coderpad-foo"" Here are two screenshots of what is happening: https://imgur.com/a/kgKkrmw I'm not sure if there is logic somewhere that detects if a stylesheet with the same handle as the theme directory is registered then don't load default styles but thought I would post about this unexpected behavior. " kingkool68 Future Releases 49782 Block editor problem after WP upgrde Editor 5.4 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-04-02T16:39:39Z 2020-11-27T11:42:17Z "stuartahamilton (@stuartahamilton) 4 hours, 55 minutes ago Since the WordPress update I have not been able to edit posts in the block editor as haf way down each page, the blocks are blocked (!) by a series of drop down menus as in the image link. Two of the these are related to plugins – Yoast and Ultimate Social Media. If I disable these the dropdowns disappear. One is, rather unfortunately, related to the theme I use, which is a real problem for such a large site. But one of the dropdowns is actually for the post settings themselves. Which I can do nothing about as that’s an actual WP thing. Anyone else having this problem? Fixes, advice, anything would be good. I’ve temporarily went back to the classic editor but would rather have a proper fix. Many thanks. The page I need help with: https://i.postimg.cc/wjYXt2LL/wperror.jpg" stuartahamilton Future Releases 53963 Block editor tools slots are empty Editor 5.8 normal critical Awaiting Review defect (bug) new reporter-feedback 2021-08-20T03:16:17Z 2021-08-20T14:48:04Z "Hello. I lost my editor tools in some point, when I click block I get No block selected. Also, there are fewer around the menu where you edit your text, no image icon etc. I am using WP 5.8 " dreamsofbeauty Future Releases 55369 Block styles preview are unstyled since 5.9 if styles are in a global editor styles css Editor 5.9.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-03-11T05:45:09Z 2022-03-11T18:49:16Z "Hello, Block stlyes registered with {{{ wp.blocks.registerBlockStyle( 'acf/featured-news', { name: 'featured-news-black', label: 'Featured news black', isDefault: false, } ); }}} Editor stylesheet enqueued with: {{{ function legit_block_editor_styles() { wp_enqueue_style( 'legit-editor-styles', get_theme_file_uri( '/style-editor.css' ), false, '11.0', 'all' ); } add_action( 'enqueue_block_editor_assets', 'legit_block_editor_styles' ); }}} Since WordPress 5.9 the iframe that shows the block styles show them unstyled as doesn't include the style-editor.css Thank you " JohnDBB Future Releases 52794 Blocks not entering in correct place Editor 5.7 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-03-12T15:46:40Z 2021-03-31T21:55:57Z "I updated to WordPress 5.7, and ever since it's had this new glitch. Especially when I open a post and go to add a block for the first time in that session, it will insert the block at the very end of the post, instead of in the middle where I wanted it. Usually after that first glitch it works fine, but every once in a while it will do it again though I haven't determine the pattern for that one. Also, if I ever click out to the side of a block, perhaps to get a clearer image of what I just did, it will scroll me all the way down to the bottom of the post. This happens every time I do that. Since I use a lot of images, this is a huge annoyance. Thanks!" amyolsen12 Future Releases 57126 Broken CSS for Buttons (previously created by Gutenberg block editor) after WP 6.1 Update Editor 6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-11-16T11:55:57Z 2022-11-16T22:39:11Z "Have multiple sites using popular free themes (Blocksy and OceanWP) and the button CSS (layout, colors, etc) is all broken after recent update to WP version 6.1 According to Blocksy theme devs, they say it's due to the WP core update that could have been handled differently to avoid this issue. Only way to fix is to manually open every post or page with a button and then re-save the page. This is very time-intensive process for large sites with 100's or 1000's of posts and pages and also trying to remember or figure out which posts have buttons on them in the first place. Seems that WP core dev team should release a fix/patch for this issue. See for further clarification: https://wordpress.org/support/topic/anyone-seeing-broken-buttons-css-afer-last-updates/ https://wordpress.org/support/topic/mobile-view-for-buttons-is-wrong-css-no-margin-or-alignment/ Thank you " wordmax Future Releases 53912 Bug when using Block-styles loading enhancements in WP 5.8 Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2021-08-11T05:16:43Z 2024-01-30T05:15:22Z "I'm not sure if this is a a bug, but when enabling this feature on Windows some of the blocks assets are not loaded on the frontend. When checking the {{{register_block_style_handle}}} function, some blocks are ignored as the {{{$is_core_block}}} variable is false due to slash inconsistencies in the {{{$metadata['file']}}} variable. Style of blocks that are registered from {{{register_core_block_types_from_metadata}}} are loaded, but the blocks that are registered from their respective directory; such as {{{register_block_core_latest_comments}}} are not loaded. Thank you!" wilbertalvis Future Releases 51186 CMD S Not saving/updating posts Editor normal minor Awaiting Review defect (bug) new reporter-feedback 2020-08-29T13:01:13Z 2021-05-04T06:01:57Z "Hi there, I have detected this today: pressing CMD S is not saving/updating posts. It shows the animation, as the post was being saved but it is not. I am using the classical editor. I am running WordPress 5.5 and have the following plugins installed: Add Categories to Pages AddToAny Share Buttons Classic Editor Contact Form Maker CSS & JavaScript Toolbox Lockdown WP Admin Select Post Snippets Select Really Simple SSL Really Simple SSL Select TinyMCE Advanced TinyMCE Advanced Urvanov Syntax Highlighter Wordpress Hide Posts WP Disable Automatic Updates " HairyPotter Future Releases 57006 Cannot set font BOLD for multiple lines of text Editor 6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-11-05T12:20:54Z 2022-11-05T15:35:38Z "This was present before but it's not an option anymore. Selecting multiple rows of text cannot be CTRL+B or set to Bold anymore. You have to set to bold each line individually. " xecutable Future Releases 59303 Can’t use colors with selected text in Gutenberg Editor 6.3.1 normal major Awaiting Review defect (bug) new reporter-feedback 2023-09-06T23:33:36Z 2023-09-07T14:13:38Z "The form to add color to text was always a bit buggy with Gutenberg. But, since a few versions it doesn’t work anymore. The area with colors appear below the right column. Some versions ago page could be moved to reveal the palette, but now it’s no more possible. See the image below: [[Image(https://i.postimg.cc/ZRZLvL0V/IMG-6233.jpg)]]" locksoft Future Releases 56423 Changing Title changes URL Editor normal major Awaiting Review defect (bug) new reporter-feedback 2022-08-23T19:00:53Z 2022-08-23T23:06:19Z "Having the URL change whenever the a page or post Title changes is a major hazard. You can say ""works as designed""; but this is not a good design - people can edit a Title and get an unexpected URL change, breaking links and requiring re-direction of the accidental URL. At a minimum, upon hitting the Update button, user should be warned that URL is about to change - and required to approve this before page is re-published." RBM7777 Future Releases 56693 Copying and Pasting Sporadically duplicates the pasted content, which cannot then be removed Editor 6.0.2 normal normal Awaiting Review defect (bug) assigned reporter-feedback 2022-09-29T18:21:31Z 2022-12-09T15:36:32Z Sometimes when we paste content over highlighted content, it duplicates it and then won't let us quickly remove the dups. adamvanbuskirk Future Releases 47865 Custom Post Types – Published Posts – Preview Changes URL’s – Page not Found Editor 5.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2019-08-12T14:45:41Z 2020-11-05T03:36:39Z "Seeing as I started a forum discussion on this, perhaps the best place to start is there: https://wordpress.org/support/topic/custom-post-types-published-posts-preview-changes-urls-page-not-found/ It includes all I believe should be relevant to the topic." SwansonPhotos Future Releases 60256 Edit the link Editor 6.2.1 normal normal Awaiting Review defect (bug) assigned reporter-feedback 2024-01-15T15:20:47Z 2024-01-15T15:34:43Z "I have a small image e.g. an arrow with an anchor link on it e.g. ""#section1"". I copy this image and want to edit the link. Then it adds the complete admin url to the link like this: https://gazetamercantil.com" mercantil Future Releases 51490 Editor Styles Not Loading in Correct Sequence for Blocks Editor 5.5.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-10-09T16:43:04Z 2021-01-28T22:44:20Z "In the block editor, styles loaded by WP core are overriding those from editor-style.css in a custom theme I'm building, causing particular display issues with line heights and margins for header blocks. It appears as though this is due to an error at line 190 of edit-form-blocks.php, the file that sets up $editor_settings. The line: **if ( $editor_styles && current_theme_supports( 'editor-styles' ) ) { ** The current_theme_supports check should be for 'editor-style' rather than 'editor-styles'. As a result, styles from editor-style.css are being skipped. (Some earlier sequence is loading the styles from editor-style.css, so they do exist in the block editor. However, the WP core styles loaded in edit-form-blocks.php are overriding them.)" susanwrotethis Future Releases 53136 "Error with ""Add to Reusable blocks"" in WordPress 5.7.1" Editor 5.7.1 normal normal Future Release defect (bug) new reporter-feedback 2021-05-03T08:10:05Z 2021-08-31T14:06:33Z "Error when ""adding the first paragraph style to the reuse block"" in a new post with `core/paragraph` added (or used) in `register_block_style()` in WordPree 5.7.1 The error message is Error statement The editor has encountered an unexpected error Additional code (functions.php / Theme: Twenty Twenty-One) {{{#!php 'blue-paragraph', 'label' => __( 'Blue paragraph' ), 'inline_style' => '.is-style-blue-paragraph { color: blue; }', ) ); }}} [[Image(https://f.easyuploader.app/20210503102556_54394978.gif)]] [[Image(https://f.easyuploader.app/20210503102810_6e724b33.png)]] " sawamura Future Releases 57008 FSE Margin settings not working Editor 6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-11-05T19:44:46Z 2022-11-05T20:02:47Z In my test site, when I change the slider for margin settings for a block (eg buttons, social icons) the margin looks correct in the editor but does not appear in the final page. jcoonrod Future Releases 55271 Featured Image Section Disappears In Block Editor Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2022-02-28T05:37:56Z 2022-03-08T14:18:32Z For some reason, the Featured Image Section just plain disappears in the Block Editor. I have to download the Classic Editor Plugin to see it. I thought this was a one time problem but it's a constant one when using WordPress 5.9.1 zennie62 Future Releases 49676 Gallery Block upload does not link to the right image Editor 5.3.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-03-22T18:08:50Z 2020-11-24T04:36:45Z "When uploading images directly from the Gallery Block, the image used is a fixed resolution image rather than the scaled image. The scaled image is the only one accessible through the Media Library, but the Gallery Block links to a fixed-size image. This is bad for performance, as the linked image is huge even when displayed in a tiny Gallery matrix: https://travellingsquirrel.altervista.org/kata-beach-in-phuket-the-quieter-alternative-to-patong {{{ img src=""https://travellingsquirrel.altervista.org/wp-content/uploads/2020/03/20190208_182104-3000x2250.jpg }}} It also makes any edit through the Media Library to not be applied to the displayed image, and vice-versa." romain145 Future Releases 49891 Gutenberg Block Cover - Fixed Background Editor 5.4 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-04-13T11:38:23Z 2020-12-15T05:41:32Z Hello! In the latest versions of Google Chrome (80-81) and similar browsers, the fixed background in the Cover block has stopped working. It does not depend on the theme, nor on the installed plugins, nor on the custom code. Checked on working sites, on a local server. Php 7.4 and below. WordPress 5.4. Windows 10 Home Operating System. zabavljaev Future Releases 48888 HTML being stripped from shortcode blocks in blog posts Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2019-12-05T18:24:31Z 2020-12-07T05:26:55Z "Hi team I have a MailChimp newsletter signup form in the sidebar of my blog. Occasionally I add the same signup form to the body of my blog posts. Previously when I have done this, the one from the sidebar has been removed and just the one in the blog post is displayed. I tried to do this yesterday and discovered that wherever I have done this, now neither signup form shows. I asked my tech guy to take a look and he found that whenever the shortcode for the newsletter signup form is included in a blog post, the HTML is being stripped from the code meaning it’s not displayed. He suggested I try adding the form to a blank page and embedding it in my blog post to fix the issue. I did this using Elementor and it didn’t work. My tech guy is fairly sure this is a bug as he doesn’t think any of the HTML should be being messed with. And he said he’s fairly sure it’s a WordPress bug not a plugin or theme bug. I am unsure how long this issue has being going on for. Has anyone else reported a similar bug? I’m using the latest stable version of WP." kmwade Future Releases 50443 Heading h2 rest api level Editor 5.4.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-06-22T00:26:00Z 2020-11-23T03:43:01Z "Во всех заголовках кроме h2, возвращаются нормальные атрибуты уровня. Не знаю с чем это связано. {{{ { ""blockName"": ""core/heading"", ""attrs"": [], ""innerBlocks"": [], ""innerHTML"": ""\n

222222222222222

\n"", ""innerContent"": [ ""\n

222222222222222

\n"" ], ""content"": { ""text"": ""222222222222222"" } }, }}} " zavod008 Future Releases 55884 Image aligned center disappears in the editor Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2022-06-01T01:46:52Z 2022-06-02T13:29:44Z An old bug returns. In the editor window, when you align an image to center, it disappears in the editor but still is visible when looking at the published page/post. See attached screenshot of the editor.[[Image(https://websentia.com/wp-content/uploads/2022/05/missingImageAlignCenter.png)]] stinkykong Future Releases 53154 Image in 'Media & Text' block not affected by 'Additional CSS class(es)' Editor 5.7.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-05-04T14:43:26Z 2021-05-19T13:55:30Z After the update, styles added to the image's 'Additional CSS class(es)' on the 'Media & Text' block no longer work. danieldau Future Releases 48796 "Image size reporting as ""thumbnail"" after most recent update" Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2019-11-26T15:53:35Z 2020-11-05T06:16:41Z "Recently, I noticed, when editing images in my existing blog posts, that the image size reported for all of the images on my blog is ""thumbnail"", when in fact, they were inserted into the post as ""large"" or ""full"". Is this a glitch that will be fixed? I hope so because there are old images in my blog, which were originally inserted incorrectly, and ARE in fact inserted as thumbnails. I correct these when I come across them in my editing, but now it's impossible to tell which ones are wrong because every image reports as being a ""thumbnail image"". Will this be corrected? " happy hooligans Future Releases 54995 Impossible to type apostrophe in WP 5.9 + Twenty Twenty One theme Editor 5.9 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-01-30T09:02:25Z 2022-06-17T06:51:40Z "Working from a Chromebook with US international keyboard, the usual keys for typing single apostrophe ' and double apostrophe "" do not work in the Gutenberg editor." nmschaller Future Releases 53968 In 5.8 Metaboxes hide post editor completely Editor 5.8 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-08-20T11:11:34Z 2021-09-10T15:21:29Z "In 5.8, when editing posts, pages or anything else, metaboxes hide the page title and the page content by default every time you open a post for editing. I use page as euphemism for all custom post types. Expected behaviour: metaboxes are below the page title and page content as is normal Current behaviour: metaboxes hide the title and the content, which cannot be edited without closing the metaboxes each time you open the page. The problem: 90% of the time the user wants to edit the title or content, most metaboxes are meant to be edited once and forgotten. browser: Safari, Mac OS" robertjakobson Future Releases 59553 In Beta 6.4-beta2, when trying to add a row or container, I get the error Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2023-10-05T21:47:56Z 2023-10-30T18:16:41Z "This block has encountered an error and cannot be previewed. " texasfixer Future Releases 55040 In WordPress 5.9 color palette overlap with circular color picker issue Editor 5.9 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-02-02T06:44:10Z 2022-02-03T09:40:45Z "In WordPress 5.9 color palette overlap with circular color picker issue are occured when we hover on circular color picker. I have attached screenshot for it." multidots1896 Future Releases 53867 Multiple reusable blocks issues since 5.8 Editor 5.8 normal major Awaiting Review defect (bug) new reporter-feedback 2021-08-03T07:37:45Z 2022-01-31T09:45:31Z "I am having multiple reusable blocks issues since 5.8:- 1. They are not displaying as designed. For example, I have a reusable block that spans the entire width of a post, but when you view the live post, it only occupies the right third of the post width. In another example, I have coloured the background, but the background is only showing as white. 2. When inserting a reusable block into a post, 2 instances of the reusable block get inserted." gizmo2501 Future Releases 42028 On-screen elements missing or dead in Mac OS 10.13 and Google Chrome Editor 4.7.4 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-09-29T03:17:26Z 2020-09-23T05:41:57Z "There are some bizarre bugs that appear when using Chrome (current version, Version 61.0.3163.100 (Official Build) (64-bit) as well as Chrome Canary (Version 63.0.3225.0 (Official Build) canary (64-bit) ) and WordPress 4.7.4, which include a) If I create a link then try to edit it so I can set the ""load in new tab"" check box, the page will ""freeze"" (become totally unresponsive, refusing to acknowledge clicks or scrolling, until I reloaded the Wordpress page) b) My ""edit snippet"" section is missing, requiring me to load this page in Safari to set the snippet. Relatedly, I am pretty sure setting a focus keyword in Chrome will not cause it to be saved, since I set it but then it was blank when the article was loaded in Safari. c) Perhaps most frustratingly, the Visual and Text tabs are nonfunctional in Chrome. I cannot access the page source, which I need for various scripts, as I should be able to. Please fix ASAP! Enclosing screenshots of the nonfunctional elements. [[Image(https://s3-us-west-2.amazonaws.com/megumi.img/ScreenShot2017-09-29at12.08.15PM.jpg)]] [[Image(https://s3-us-west-2.amazonaws.com/megumi.img/ScreenShot2017-09-29at12.10.42PM.jpg)]] [[Image(https://s3-us-west-2.amazonaws.com/megumi.img/ScreenShot2017-09-29at12.12.22PM.jpg)]]" ppayne Future Releases 59170 Overlapping text when posting using iPhone Editor 6.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-23T09:27:02Z 2023-09-05T16:30:50Z "I have a website and I always get article submissions from authors, they write using Microsoft Office (maybe they use a bit older version, because the new 365 desktop version has no problem), on my iPhone I open the article using Office 365, and a strange thing happens : 1. If I use a block editor, the text will overlap 2. If I use the classic editor, many spaces are lost so that many words are attached without spaces. here I provide you an example of overlapping text: [https://drive.google.com/file/d/1c167tWdPd6k_n7_tWeRwi-9qOmgZ34nr/view?usp=sharing] the website is freshly installed using twenty twenty three theme." readonecc Future Releases 55039 Page template automatically changed when page is reload Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2022-02-02T06:36:21Z 2022-02-02T08:08:26Z "I am noticing some issues with page and post templates in production site. If I make an update on a page or a post that has a specific template, it reverts back to ""default template"". Example: This page should have ""Card Review"" template, but it has automatically changed to ""default template"". If template is changed, it reverts again to ""default template"" after page reload. This is not normal behavior. I have already updates wordpress version. current version is 5.9. Thanks & Regards, Sapna Vaghela." sapnamonocept Future Releases 57443 Page template label sticks to default Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2023-01-11T13:32:01Z 2023-01-18T00:51:59Z "After changing the template in the wordpress editor, ""Default Template"" stays as the template label (despite the template has been changed and everything else works fine). https://ibb.co/Vjsx719" permanyer Future Releases 49193 Parent Page selector not available in Page Attributes when using Block Editor Editor 5.3.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-01-14T03:35:40Z 2021-01-13T17:58:53Z "We're running a multisite with around 190 child sites on it. When our users are using the block editor, the ""Parent Page"" drop down selector does not appear within the Page Attributes box. I've tried using the default wordpress theme - same result. Our test platform, on the same server with an identical configuration and plugin set but which only has a couple of child sites is not experiencing this problem - however, it does take a couple of seconds for this individual dropdown selector to load. The other diference is that the multisite where the issue exists is showing an error in developer tools that says ""Uncaught (in promise) SyntaxError: Unexpected token < in JSON at position 6 " Brandicoot Future Releases 53037 Post Attributes UI issue in page list Editor 5.7.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-04-15T06:51:35Z 2022-05-25T10:25:02Z "Hi Add new page in UI issue.So how we can fixed this? Also i think we need to update ""Post Attributes"" to ""page Attributes"" . like post type name with Attributes. you can think about last suggestion. Thank you." sumitsingh Future Releases 57965 Post Featured Image block on a Single template doesn't have explicit width and height Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2023-03-21T18:07:28Z 2023-03-23T02:24:27Z "Post Featured Image block on a Single template doesn't have explicit width and height. (BTW, in an Archive context, the Post Featured Image block does have width and height) See screenshots: [[Image(https://drive.google.com/file/d/1K1HWVCXvvj0zEXxU9QPPPdB6rgwwhvKQ/view?usp=drivesdk)]] [[Image(https://drive.google.com/file/d/1bEC9CjdIvgDMRMzQgUJHTu1LP08EJ3jN/view?usp=drivesdk)]]" asafm7 Future Releases 41732 Potential Core Issue Editor 4.8.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-08-26T01:56:27Z 2020-11-16T06:53:16Z "I posted [https://wordpress.org/support/topic/wordpress-core-issue/ this] a couple of weeks ago and I haven't heard anything so I assume its not in the ideal place. I asked one of the developers of the products I initially thought the issue was associated with (and who have also recreated/tested this issue without their products present) for a suggestion and they recommended posting a ticket here. I've been battling to narrow this problem down for a long time now. Over a year ago I discovered an issue which as it turns out impacts the editor view in visual mode. Sorry I don't recall the version this started happening in. I assume it was around 4.0 Initially I thought it was either the GeneratePress theme or Yoast SEO plugin however their support/developers have helped me to recreate the issue without their products installed. I'm not sure why but at this stage the issue occurs using WordPress and twenty-sixteen theme when various types of content are present in visual mode but not when using the twenty seventeen theme to my knowledge. After a load of time and testing the common denominator in all the tests is WordPress itself. I attached an image below which shows the area in the code which fluctuates. It may help cut through some of the info and get to the problem. There are a number of other attachments found within the associated thread above. [https://1drv.ms/f/s!AjEGKOtzUwy1gclEHoZZ9-DCW52S4Q] Thanks" doubledworks Future Releases 58191 "Preview mode button breaks in custom post types in wordpress 6.2 - manually removing ""preview_nonce="" from url fixes it" Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2023-04-25T15:30:58Z 2023-04-30T09:18:03Z "Hi, After updating to wordpress 6.2 from wordpress 6.1.1 the Preview mode for my custom post type stopped working. I have a custom post type which publishes a different type of post. Whenever I click on preview to see the custom post type preview, it adds ""preview_nonce="" to the url. This causes the page to be completely blank other than the header and sidebar. When I remove the ""preview_nonce="" from the url the preview works perfectly. I noticed that if I click preview from the list of custom posts rather than from the preview button in the custom post type, it loads perfectly fine without the preview_nonce in the url. Is this a wordpress bug? " gabez123 Future Releases 54345 Publish Date Transparent Css Issue Editor 5.8.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-10-30T03:47:10Z 2021-10-30T05:30:20Z "While editing an article i see Publish Date Transparent Css Issue, in simple words, the custom date selection button is not visible." itssamimtahir Future Releases 53172 React-dom mistake Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2021-05-08T21:05:40Z 2021-05-13T14:36:24Z "http://prntscr.com/12isc2j react-dom.js?ver=16.13.1:1680 Warning: Failed prop type: You provided a value prop to a form field without an onChange handler. This will render a read-only field. If the field should be mutable use defaultValue. Otherwise, set either onChange or readOnly. Its not whole time, its happening sometimes. I don’t understand why does this mistake appear" andrewpolnikov Future Releases 46376 Right hand column (update page) gets stuck Editor 5.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2019-02-28T16:43:03Z 2020-11-30T04:50:15Z "Not sure how to explain this: 1) Edit a page 2) If page has a warning notice at top, e.g ""there is a more recent version of this page, restore?"" 3) Right hand menu will scroll down as you go down the page, but not back up. So if you edit something at the bottom of the page, you can't get back to the save button. 4) Dismiss the warning notice before you scroll and the menu works normally." TPDave Future Releases 56240 Social Icons Block bug Editor 6.0 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-07-18T09:50:21Z 2022-07-18T13:42:35Z "When adding the social icon block, the + button is missing. All that shows is ""click plus to add"" Tried using the default twenty themes with same result. Fresh install of latest WordPress stable. " mplayer Future Releases 55566 Start value in List block doesn't work Editor 5.9.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-04-12T20:27:36Z 2022-04-13T10:48:31Z "Hi. I just noticed that ""Start value"" option in List block doesn't work - no matter what start value you type, it always starts from 1. The start value changes in Gutenberg editor, but is not visible in front end, not even in post preview. To reproduce this issue just add a List block in Gutenberg editor and try to change ""Start value"" from 1 to any other number. Then preview or publish the post and you'll see that it doesn't work and ""1"" always shows up." kacper3355 Future Releases 46206 Strange behaviour with links inside a table Editor 5.0.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2019-02-07T20:53:49Z 2020-11-23T16:54:45Z "I'n currently using WP 5.0.3. There is some strange behaviour with links that are inside a table. Check box ""open link in a new window"" did nothing until I switched to HTML and added a space before link text (
}}} There are two issues (maybe related). First, this is tag soup. For various reasons (parsing with XML tools, better HTML code understanding and maintenance...), the Code Editor should not omit opening and closing tags. Here, the first `

` does not have a matching opening tag and the last `

` does not have a matching closing tag. Moreover, in HTML5 parsing, the first `

` is parsed as if it were `

`, i.e. an empty paragraph; and the text before it should really be in a paragraph for consistency. If the Code Editor thought that the `
}}} " vinc17 Future Releases 56950 The default margin for .wp-block-image disappears after WordPress 6.1 Editor 6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-11-02T05:11:20Z 2023-08-28T16:21:49Z "So, I have a few websites running on WordPress, and one of them has just been updated automatically to the 6.1 update, and I noticed that the images don't have any space with the text below them. After inspecting them, I found out that the margin for .wp-block-image was no longer there. By default, it was: .wp-block-image { margin: 0 0 1em; } But after 6.1, it's gone. Check out the screenshots just to be clear. https://i.imgur.com/L9EjpTY.png https://i.imgur.com/Qq6bbYQ.png" anonymized_14771642 Future Releases 57287 Type error calling Styles > Customize > Blocks from FSE Editor 6.1.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-12-07T03:48:59Z 2022-12-13T16:29:10Z "From FSE, When I open Styles pane, Then click ""Blocks"" I receive an error: {{{ TypeError: Cannot use 'in' operator to search for 'color' in at http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:72801 at Array.forEach () at ll (http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:72639) at Tl (http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:82514) at Cl (http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:82422) at Xl (http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:103806) at ct (http://localhost:10043/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:43430) at os (http://localhost:10043/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:111136) at Ur (http://localhost:10043/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77643) at Ir (http://localhost:10043/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77571) }}}" ritterml Future Releases 56953 TypeError: Cannot destructure property 'themeSupportsLayout' of '(0 , p.useSelect)(...)' as it is undefined Editor 6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-11-02T10:43:03Z 2022-11-03T16:33:26Z "Hi this morning with update of WP to 6.1 have a lot of problems. I tried to deactive all plugins and I think that is an error of Core. TypeError: Cannot destructure property 'themeSupportsLayout' of '(0 , p.useSelect)(...)' as it is undefined. at https://domain.com/wp-includes/js/dist/block-editor.min.js?ver=d39738cb7c1202964677:26:193469 at ct (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:43430) at os (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:111136) at Ur (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77643) at Ir (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77571) at Dr (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77434) at Pr (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:74429) at https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:30173 at unstable_runWithPriority (https://domain.com/wp-includes/js/dist/vendor/react.min.js?ver=17.0.1:9:7431) at xn (https://domain.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:29950) I tried to reinstall WP but the link is on 404: https://downloads.wordpress.org/release/it_IT/wordpress-6.1.zip I've bug on editor of themes, on create new content and on front-end Please fix the problem" pigot4 Future Releases 47978 Upload files with Media Library takes much load time to upload image Editor 5.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2019-09-05T13:34:08Z 2020-11-05T04:48:54Z "Theme: Twenty Nineteen Version: 5.2.3 Steps to Reproduce: 1) Go to Gallery 2) Select Media Library 3) Go to Upload image with less than 2 mb size 4) The image will take much more time to upload and it will continue to stay in progress. Note: Please check the screenshot link below for the same. https://www.screencast.com/t/8nP8shWWW2UY" anjalirai Future Releases 52741 Video embeds (YouTube and Wistia) do not show on page. Editor 5.6.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-03-09T20:56:33Z 2021-04-08T20:16:52Z "When adding a Wistia video embed using the Gutenberg editor's ""embed"" block the video embed does not show in the page. Upon inspection of the DOM, I noticed that if you toggle the .wp-block-embed__wrapper from position: relative to off the video shows. The offending CSS style is located ""/wp-includes/css/dist/block-library/style.css"" on line: 502. I've simply deleted this style and the embed seems to work again without any issues across browsers and devices. To reproduce the issue, create a new post and add an embed block in between a heading and above a paragraph. Paste in a Wisitia video link and save. " kevinwoodfield Future Releases 51215 WordPress 5.5 no longer respects Headings values when pasting in text Editor 5.5.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-09-02T08:15:33Z 2020-11-26T05:41:41Z "In previous versions of WordPress, if you wrote a post outside of WordPress and then imported it, the import process would respect any Headings you made - so if you set H2, H3, H4, etc, in OneNote or Word, when you imported it, the Headings values you set would transfer to the WordPress post. Now, in 5.5, this no longer happens. If you paste in text, all the Headings come in as Paragraphs. This is incredibly annoying and it is very time-consuming to go back and change them, constantly referring to your written document to see what the Headings values should be. I am submitting this as a bug, as this was not how previous versions worked and is not mentioned in the release notes, so I imagine it is unintended." gizmo2501 Future Releases 58032 WordPress 6.2 breaks post edit screens in Safari 13 Editor 6.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-03-31T10:44:51Z 2023-04-01T22:09:12Z "After updating to 6.2, post edit screens are white screen in Safari 13.1.2. Many block editor related JS errors in the Console, see attached screenshot. Version 6.1.1 was working fine, I could work in the code editor without issues. I fully expect this ticket to get cancelled because of older Safari version. But my mac does not go beyond High Sierra, so this is it then for older Macs and Safari. I have a slight hope the errors are fixable. " rembem Future Releases 60662 "WordPress 6.5-beta3-57738 - Full Site Editor breaks after installing ""Contact Form 7""" Editor trunk normal normal Awaiting Review defect (bug) new reporter-feedback 2024-02-29T22:38:04Z 2024-03-01T07:48:57Z "Hi- I am using WordPress 6.5-beta3-57738 running Twenty Twenty-Four CHILD theme. I ran into an issue after installing Contact Form 7 plugin where the site editor breaks as shown in the attached images. BEFORE-INSTALLING-CONTACT-FORM-7-PLUGIN https://emailmarketing.capstonebpo.com/wp-content/uploads/2024/02/before-installing-contact-form-7.jpg AFTER-INSTALLING-CONTACT-FORM-7-PLUGIN https://emailmarketing.capstonebpo.com/wp-content/uploads/2024/02/after-installing-contact-form-7.jpg Rajesh" capstonebpo Future Releases 59092 WordPress Editor not working after updating to 6.3 - Showing Blank Screen Editor 6.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-08-13T11:44:49Z 2023-11-09T18:49:51Z I’m getting a blank page when I add a new post or edit a post. I cleared all caches and cookies but not worked. Tried deactivating all plugins, changing the theme to Twenty Twenty-Three. But the issue is not fixed yet. jaagofoundation Future Releases 52556 WordPress is adding   always Editor 5.6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-02-17T14:44:45Z 2021-02-23T10:01:41Z "Hello, This bug is happening only if gutenberg editor is disabled. Ill try to explain in best way how wordpress is adding this  . 1. Create a new page 1.1 Type a title or without both give same result. 1.2 In content there should be nothing 1.3 Publish 2. After publish try to leave the page editing lest say clicking on dashboard from the menu. Wordpress will promp asking to save changes. If you are in visual editor and swap to text editor you will notice that   was added. 3. If you click update everytime wordpress will add a new   In inspector i have notice this script {{{ }}} If i put a breakpoint and reload the page will return thousandsSeparator undefined I dont know much about this function and the idea behind it but any ideas how to prevent this would be great. " snuffybg Future Releases 53620 add_meta_box $callback firing after publish or update but not updating dom html Editor 5.7.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-07-07T15:02:56Z 2023-08-11T19:42:17Z "Basically, the callback in add_meta_box is firing after I update my post (got the spinning circle in the meta box header), returning new updated html, but the new html is not applied to the actual page. The following metabox just renders a random number: {{{#!php 3. click Preview button 4. script is fired in brower ; chrome console output 123 can you fix this problem?" lizhe1985 Future Releases 55737 web site error (in south korea) Editor normal normal Awaiting Review defect (bug) new reporter-feedback 2022-05-15T17:57:52Z 2022-05-15T21:35:01Z "Error: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node. at hr (https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=6.1-alpha-53394:1:68782) at hr (https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=6.1-alpha-53394:1:68855) at hr (https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=6.1-alpha-53394:1:68855) at dr (https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=6.1-alpha-53394:1:68293) at Ar (https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=6.1-alpha-53394:1:80486) at unstable_runWithPriority (https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react.min.js?ver=6.1-alpha-53394:1:7430) at xn (https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=6.1-alpha-53394:1:29947) at Vr (https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=6.1-alpha-53394:1:78650) at Nr (https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=6.1-alpha-53394:1:74769) at https://wordpress.org/gutenberg/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=6.1-alpha-53394:1:30170" ranode Future Releases 57812 wp-block-image caption Editor 6.1.1 normal minor Awaiting Review defect (bug) new reporter-feedback 2023-02-26T20:53:14Z 2023-03-06T07:29:23Z "In wp-block-image block caption at the front end shows " iouweb Future Releases 56917 Block menu editor Editor normal normal Awaiting Review enhancement new reporter-feedback 2022-10-27T06:42:41Z 2022-10-27T07:25:03Z "I would suggest an enhancement in the post editor while editing link menus some context help should appear when you hover the mouse on the links. Also, I would like to have a way to revert to the classic menu editor. For the moment it seems a lot more faster and functional to work with it. " capbussat Future Releases 57922 Changing class-wp-editor.php Insert/Edit Link header from H1 to H3 or other Editor 6.1.1 normal normal Awaiting Review enhancement new reporter-feedback 2023-03-14T18:43:46Z 2023-03-14T23:05:22Z "Hey there! I am using the wordpress core feature of having a blog page host all our posts. There is a modal in the class-wp-editor.php file located in the wp-includes directory. On line 1868 (or around there) a modal is shown with the title ""Insert/edit link"". This line is wrapped in an H1 which from an SEO standpoint is really unfortunate as google sees that as a title for the page. Even if you put an additional H1 on the page above the modal, google will still see it as the title of the page. And in our case that's every paginated blog page. I think it would be really beneficial for everyone to change that header to an h3 or lower. H2 is fine as well but I don't think it requires that level. Thank you! All the best, D" donniewalden707 Future Releases 57595 Filter comments_array not called for Block comments Editor normal normal Awaiting Review enhancement new reporter-feedback 2023-02-01T00:38:55Z 2023-02-01T07:47:01Z "This is the code for `render_block_core_comment_template()`: {{{ // Get an array of comments for the current post. $comments = $comment_query->get_comments(); if ( count( $comments ) === 0 ) { return ''; } $comment_order = get_option( 'comment_order' ); if ( 'desc' === $comment_order ) { $comments = array_reverse( $comments ); } $wrapper_attributes = get_block_wrapper_attributes(); return sprintf( '
    %2$s
', $wrapper_attributes, block_core_comment_template_render_comments( $comments, $block ) ); }}} But that doesn't allow a plugin author to provide a custom ordering. In my case I am adding comment voting and we want to reorder comments by their up/down votes. I believe that the following line should be inserted prior to the `$wrapper_attributes` assignment: {{{ $comments = apply_filters( 'comments_array', $comments, $block->context[postId] ); }}} " cmautner Future Releases 48789 Provide ability to drag and drop images among and between Gutenberg Blocks Editor 5.3 normal normal Awaiting Review enhancement new reporter-feedback 2019-11-25T17:59:19Z 2020-11-24T23:44:04Z "It is not possible to drag and drop images between the different GB blocks. For Example, if I make an image Block I cannot drag the image out of the block and drop into another block. Therefore, to improve UX WordPress should provide the ability to drag and drop images among and between Gutenberg Blocks" Pcosta88 Future Releases 57626 Searches to add a link in post-edit, to be sortable/filterable to better find tags Editor normal trivial Awaiting Review enhancement new reporter-feedback 2023-02-03T14:30:14Z 2023-03-20T13:51:02Z "Currently when adding a link to a post, I can search for a term and get back a mix of posts, pages and tags. This is the intended behaviour. However, if the search term I am using is broad (e.g. 'Movies') and there are more than 20 posts on my site featuring the word Movies (this is often the case for a broad term), then WordPress will prioritise returning me 20 search results that are all posts, and will not return the Movies tag. This is a general sorting issue, the search function prioritises posts over tags. I'd like see a change where an exact tag match would always appears as the top result. If not, then an option to filter the search, perhaps with checkboxes to show Posts/Pages/Tags etc." joshduffetywong Future Releases 32143 wpLink function getAttrs() missing link-text Editor 4.2 normal normal Awaiting Review enhancement new reporter-feedback 2015-04-27T07:04:06Z 2020-11-24T01:38:12Z "After last update to 4.2 wpLink() was renewed and the title-input was replaced. Instead of title, you can now insert/change the link text. https://core.trac.wordpress.org/browser/trunk/src/wp-includes/js/wplink.js?rev=32017 But in function getAttrs() the val of link-text was forgotten. Therfor I proporse to add this line in getAttrs(): linktext: $.trim( inputs.text.val() ), Also it would be nice to populate the link-text field with the document title of a chosed intern element, like it was made with the old title-field before. " xwolf Future Releases 57721 Twenty Twenty-Three > Site Editor > stylizing of captions in the Image block Editor normal normal Awaiting Review feature request new reporter-feedback 2023-02-14T18:59:23Z 2023-02-16T15:49:37Z In the Site Editor -> Styles -> Blocks -> Image Block I was expecting controls to edit the font and alignment of the image captions (the text that goes under the image). ddegner Future Releases 58272 Accessibility issues with core embed block's handling of Flickr and TikTok joedolson* Embeds 6.2 normal normal Future Release defect (bug) accepted reporter-feedback 2023-05-08T21:57:00Z 2024-02-05T20:43:59Z "There is an accessibility error with the embed iFrame for Flickr and TikTok. Specifically, that the iFrame is missing a title, with no ""title"" attribute, or the ""title"" attribute being empty. Site Improve is requesting that the frame provide an attribute titie="""", and to add a description of the content in the title. There is also an ""Link without a text alternative"" message for the link, stating that ""links should always have a text alternative"". In order for a link to be readable by screen reader users links must all contain either plain text, or in the case of a linked image, alt text describing where the link goes. If the linked image contains text, a good general rule is to make the alt text the same, or similar to the text in the image. The same issue goes with the inline (iframe) frame, that does not include a text altnerative. All three of these issues will lower page accessibility for those using screen readers. Thanks for your help. " markcmorantt Future Releases 58706 SoundCloud block error Embeds 6.2.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-07-03T17:12:27Z 2023-07-03T23:31:01Z "Hello, I am running 6.2.2. Whenever I paste any SoundCloud story into the Block Editor, I always get an error that reads ""Sorry, this content could not be embedded"". I'm able to use the HTML block and embed that way. It appears others are seeing this problem too: https://wordpress.org/support/topic/soundcloud-embeds-stopped-working-2/ Thanks for your help! -Tyler" paywall Future Releases 53935 Vimeo oembed force player with large height on blog post Embeds 5.8 normal minor Awaiting Review defect (bug) new reporter-feedback 2021-08-16T17:08:49Z 2021-08-18T19:46:11Z "Hi, When embedding a Vimeo Video Player on a blog post, the admin automatic embed display the player correctly but the published version have height that is way bigger than the player. How to reproduce : - create a new blog post - insert text before - embed a Vimeo video with link : player.vimeo.com/video/VIDEOID - insert text after - publish post -> the vimeo video player is with large blank space on top and bottom More details : Seems like this is the iframe code on the WP Public page : >> this width / height seems large and does not seems to come from the site theme either. " Trouffman Future Releases 49989 Invision embed code supported by WordPress Embeds normal normal Awaiting Review enhancement new reporter-feedback 2020-04-23T20:34:05Z 2020-11-12T13:19:57Z "Hi all, Is there any possibility that WordPress consider **Invision embed codes** to be accepted in their security list? [https://wordpress.org/support/article/embeds/#okay-so-what-sites-can-i-embed-from] Using the IFrame tag that Invision provides, results in a very weird experience. The prototype is half-hidden and it is not responsive. [https://support.invisionapp.com/hc/en-us/articles/360027579812-Embedding-Screens-Prototypes#embedding-a-full-mobile-prototype] Thank you very much!" ArtGoddess Future Releases 43962 Ziggeo oEmbed Whitelisting Embeds normal normal Awaiting Review enhancement new reporter-feedback 2018-05-04T15:30:02Z 2023-05-30T09:29:32Z "Disclaimer: Not sure this is the right place, but we were forwarded from Developer Support to post this here. As per: https://make.wordpress.org/core/handbook/contribute/design-decisions/#whitelisting-oembed-providers We would like to apply to be considered from oEmbed whitelisting on Wikipedia. As per the different criteria you list there: - be well-established, popular, and mainstream services We have been around since 2012 and won a variety of awards for being the best API for video recording and playback. - properly and fully implement the oEmbed specification, We do and are being recognized as oEmbed provider by Tumblr, Embedly, Facebook, LinkedIn and Twitter. - Is the service is popular enough for core developers to have heard of it before? Is it “mainstream?” We have participated as sponsors in all major hackathons (including TC Disrupt) and have established our own yearly hackathon videohackday.com for the past four years now; we are the go to place for engineers and companies alike for all video recording and playback needs. - Does this service have a large following on Twitter, Facebook, or other social media? Is its Twitter account verified? We have around 4.5k followers on Twitter, much more than most other SaaS companies. The account is not verified because Twitter vertification has been stopped. - Is its oEmbed endpoint clearly established and properly documented? (Sometimes, they are just a developer’s pet project that may not be supported.) Yes. See https://ziggeo.com/docs - Does the oEmbed endpoint work with WordPress’ oEmbed auto-discovery? If not, could it be made to work with additional HTML tags or attributes being whitelisted? It should work with auto-discovery. - Does the service make an effort to build relationships with developers, such as through robust APIs? Our main business is an API. - How old is the service? 6 years - Does it have a well-established Wikipedia article? (Seriously.) Yes. - Has anyone written a WordPress plugin that leverages the service in some way, whether adding it as an oEmbed provider, creating a shortcode, or leveraging other APIs of the service? Do these plugins have any noticeable adoption or traction that would indicate usage and demand? Yes. Ziggeo has an official plugin on WP. Thank you for your consideration." oliverfriedmann Future Releases 46226 PeerTube 'automatic' embed Embeds normal trivial Future Release feature request new reporter-feedback 2019-02-10T14:55:06Z 2019-09-03T18:42:12Z "Would it be possible to add support for automatic Peertube embeds, the same as YouTube embeds work. https://peertube.video/videos/watch/217eefeb-883d-45be-b7fc-a788ad8507d3 " haywardgb Future Releases 57277 Emojis after translate update Emoji 6.1.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-12-05T20:40:37Z 2022-12-06T19:38:28Z "Dears, Every time my WordPress update translations I lost all my emojis in my posts. 🏃‍♂️​🏃‍♀️ The emojis changes to ? or ?? I hope can found one solution because I change all the emojis one by one, and sometimes I no remember the emoji I write. language spanish theme Generatepress Best regards" Guillermo77 Future Releases 56907 Export Child theme produces corrupt zip file Export 6.0.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-10-25T22:42:50Z 2022-10-27T02:59:48Z "Export of a theme from the Site Editor with any year theme from WordPress including twentytwentytwo, produces a working zip file. However if you have a child theme of any year theme from WordPress including twentytwentytwo, produces a corrupt zip file. The error reported by ZipRepair.net is: Your .zip file had the following issue: End of Central Directory record could not be found. All files were recovered from the corrupt zip by ZipRepair.net This corrupt zip file occurs without any changes to the child theme from the parent theme and without any plugins active. Only the child functions.php and style.css exist." meushar Future Releases 55764 Export of menus Export normal normal Awaiting Review feature request new reporter-feedback 2022-05-18T09:12:39Z 2022-05-19T08:22:54Z "​It will be time saving a lot if WordPress allows export ​of ​menus​. ​ " martiniwebb Future Releases 51990 Codemirror does not support JSX by default as mentioned External Libraries 5.5.3 normal major Awaiting Review defect (bug) new reporter-feedback 2020-12-09T13:57:14Z 2022-08-24T19:04:52Z "Hi, I found an issue with the core code. It is mentioned on this link that the CodeMirror lib will support JSX by default in the editor. https://make.wordpress.org/core/2017/10/22/code-editing-improvements-in-wordpress-4-9 But when I use JSX mode, I do see an invalid System error in the editor. Please see this image: https://user-images.githubusercontent.com/1482075/100721177-eab92a00-33b6-11eb-84c8-a15da679d79d.png {{{ { indentUnit: 2, tabSize: 2, mode: 'jsx' } }}}" webbdeveloper Future Releases 59423 Datepicker in wordpress do not follow the Date format set in the settings External Libraries normal normal Awaiting Review defect (bug) new reporter-feedback 2023-09-21T12:21:16Z 2023-09-24T03:43:08Z "Go to wordpress > Settings > General over there select ""Date Format"" > ""Custom date"" and set it to ""jS F Y"" Once you do this it will show you date to be like this 21st September 2023 Now Add the below code in your theme function.php file this code will create a shortcode [datepicker] {{{#!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 Future Releases 51353 Smart Quote Bug Formatting 5.5.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2020-09-18T22:20:57Z 2020-09-18T23:21:36Z "Hi there, There is a bug when you type a word between quotes """" at the end of a line, when nothing is followed after the last quote, it will be only be one directional way like that : « « It seems to work correctly only if the quotes are followed by a space and a character. eg: ""Hello"" world will return « Hello » world ""Hello world"" will return « Hello world« Thanks to take time to look at it." xanathos Future Releases 56433 invalid regex used in preg_replace Formatting normal normal Awaiting Review defect (bug) new reporter-feedback 2022-08-24T20:34:43Z 2022-08-24T20:53:40Z "Found in /wp-includes/formatting.php line 5385 {{{ $string = preg_replace( '@<(script|style)[^>]*?>.*?@si', '', $string ); }}} I tried this exactly as it is and it does nothing" chocofc1 Future Releases 46538 Aligning gallery results in conflicting classes added Gallery 5.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2019-03-16T07:55:15Z 2019-08-08T12:44:26Z "When a gallery is created in the Visual editor it's class is set to alignundefined. After it is saved and I view the result it's class has no alignment set. So far so good. When I close the editing and go back to manage posts list and I reopen the same post to be edited the gallery class is still set to alignundefined. Still good. When I set the alignment to 'Align left' and save the post, the result is that the gallery class is set to 'alignleft'. Still good. But here it comes: When I close the editing again and go back to manage posts list and I reopen the same post to be edited the gallery class is now set to 'alignleft alignleft', so twice the same class. And from there on, one 'alignleft' class will be staying in the class attribute. So if I change the alignment to 'Align center' and save the post, the result will be that the class attribute of the
` and closing `

` tags do not appear in the editor and are automatically handled by the editor. If I try to add them to fix things, they are automatically removed. So, now the problem with this automatic handling: The Code Editor generates tag soup with empty paragraphs in td elements. For instance, the generated HTML code looks like this: {{{
text
text

text
text

text

` implied an opening `

` just after it, it is wrong! In short, the generated code should be: {{{

text
text

text
text

text

}}} This is not correct from a semantics and accessibility point of view for all the reasons mentioned in #31654. The row header should be the cell with the main object the table refers to: the Post title, the Plugin name, etc. We could also consider to use the `abbr` attribute: http://www.w3.org/TR/html5/tabular-data.html#attr-th-abbr that would be consistent with what is currently proposed in [comment:21:ticket:32170 sortable column headers ticket]" afercia Future Releases 48751 "Make the list table ""action links"" always visible or provide an option for that" audrasjb Administration normal normal Future Release defect (bug) reviewing 2019-11-21T11:02:33Z 2020-10-09T14:34:08Z "I usually approve comments via the notification email which takes me to a page where there's an ""Approve"" button like this: https://i.19ft.com/525a403c.png However, another comment came in while I was on the site and I navigated via the menu system to the Pending comments to this page: https://i.19ft.com/d855a816.png I am a sighted user with full ability to use a keyboard. However, rarely use a mouse due to RSI-type pain and so struggled to work out how to approve this comment. I eventually worked out that you have to hover over the comment to get a set of links up with ""Approve"", ""Reply"", ""Quick Edit"", etc available. As a non-mouse-using user, it should be possible to access these links, Maybe by making them always visible via a setting in my user profile. (I've also attached the image files that I've linked to)" akrabat Future Releases 58789 Not countable. row_actions @ /wp-admin/includes/class-wp-list-table.php Administration 6.2 normal major Awaiting Review defect (bug) new 2023-07-12T05:11:05Z 2023-10-30T19:43:58Z "Commonly getting not countable for the users lists, across many sites not sure of the source of the issue, but easy solution seems to be to modify. `/wp-admin/includes/class-wp-list-table.php` {{{ protected function row_actions( $actions, $always_visible = false ) ++ if(!isset($actions)) { return ''; } $action_count = count( $actions ); if ( ! $action_count ) { return ''; } }}}" Nate1 Future Releases 48048 Parent pages are not visible in the Page Attributes metabox Administration 5.2.3 normal normal Awaiting Review defect (bug) new 2019-09-16T08:46:42Z 2019-09-16T08:46:42Z "This appears to have only started happening regularly after I had already set a few pages to have parents. Eventually, the behaviour was consistent. In this metabox there should be a page called **MOVAX Manipulator**, but as you can see there is not. (metabox.gif attached) But, the page **is** visible and can be selected when in quick edit mode (quick-edit.gif attached). I was able to replicate this on a fresh instance of WordPress using Twenty Nineteen theme and no plugins activated. As I am able to work around this issue by using the quick edit option, I'm labelling this issue as normal severity." mikeyott Future Releases 54808 Posts search term does not wrap well on mobile Administration 5.8.3 normal normal Future Release defect (bug) new 2022-01-13T11:20:59Z 2023-11-02T14:35:21Z "Hi, I just tried to find blog usage on mobile device. Then some UI issue for related search text on post listing page. More information see SS." sumitsingh Future Releases 50184 Proper margin for inputs in 'Discussion Settings' page mobile/tablet view Administration normal normal Awaiting Review defect (bug) new 2020-05-16T08:02:57Z 2023-11-07T11:12:03Z The inputs haven't proper margin, please check the screenshot. man4toman Future Releases 35204 Refresh HiDPI support Administration normal normal Awaiting Review defect (bug) new 2015-12-22T19:38:43Z 2023-03-14T19:20:01Z "As a continuation of #22238... In newer versions of Chrome, loading the admin bar CSS provides these console warnings: > Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) This was enabled first in ​[22629]. Matt Micklick (@iammattthomas) researched and suggests we update as follows. This is what our HiDPI media query looks like: {{{ @media print, (-o-min-device-pixel-ratio:5/4), (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) { /* Styles go here */ } }}} We specify min-resolution in dpi because of browser support. While Firefox, Chrome, and Opera support min-resolution and the dppx unit, Internet Explorer and Safari do not. Specifically, the most current version of IE supports min-resolution declared in dpi but not dppx. The most recent version of Safari only recognizes -webkit-min-device-pixel-ratio. In order to avoid notices in the Chrome console, we can add an additional declaration of min-resolution in dppx. We'll add it last, so that browsers that support it will use it. As a bonus, we can remove the Opera-specific selector. Since Opera has used Blink as its layout engine for over a year there's no need to continue including it. Opera's CSS support now mirrors Chrome's. Finally we'll move the Webkit-specific selector last in the set, as we do with other browser-specific declarations in CSS. So the new syntax would look like this: {{{ @media print, (min-resolution: 120dpi), (min-resolution: 1.25dppx), (-webkit-min-device-pixel-ratio: 1.25) { /* Styles go here */ } }}} " lancewillett Future Releases 48531 Regression: styling of most form elements is uneven or off-center audrasjb* Administration 5.3 normal normal Future Release defect (bug) accepted 2019-11-07T19:51:35Z 2020-07-21T20:15:42Z "Introduced in #47477. The change that caused this is the overriding of line-height and adding min-height to all ""single-line"" form elements: {{{ input[type=""text""], input[type=""password""], input[type=""date""], input[type=""datetime""], input[type=""datetime-local""], input[type=""email""], input[type=""month""], input[type=""number""], input[type=""search""], input[type=""tel""], input[type=""time""], input[type=""url""], input[type=""week""] { padding: 0 8px; /* inherits font size 14px */ line-height: 2; /* 28px */ /* Only necessary for IE11 */ min-height: 30px; } }}} This causes problems in many plugins and in some external packages like the UI in the classic editor/TinyMCE." azaozz Future Releases 49575 Responsive glitch with expanded side admin menu when moving down to small screen Administration normal normal Awaiting Review defect (bug) new 2020-03-03T22:01:52Z 2020-03-03T22:01:52Z "Hello, If you restrict your browser to medium size the side admin menu will be collapsed. If you expand this and then reduce screen size more to go to mobile view you briefly see an empty sidebar panel as the responsive actions switch to mobile. Cheers" garrett-eclipse Future Releases 41077 Revisions for code edits Administration normal normal Awaiting Review defect (bug) new 2017-06-15T14:47:58Z 2017-06-16T13:46:35Z "We should let people restore previous versions of their code in case they make mistakes. More details TBA." karmatosed Future Releases 52344 SVG images overflows UI Administration 5.6 normal minor Awaiting Review defect (bug) new 2021-01-22T08:03:03Z 2021-02-02T08:02:34Z "Hello, This issue seems related to #51868. Using WP5.6 the issue can be triggered by installing MailPoet 3.58.0. (issue is not related to MailPoet, I just use this as a trigger example, maybe due to its interface on the right) When MailPoet is not selected the UI (including SVG-icons) seems fine. Selecting MailPoet however seems to trigger SVG-icons above MailPoet to grow and overflow to UI. Please see attached images for a better understanding: https://i.ibb.co/vxvxfrq/svg-normal.jpg https://i.ibb.co/t4RDMQt/svg-overflow.jpg Thank you for having a look at this issue. With best regards, TheRealShadowHunter" therealshadowhunter Future Releases 52035 The `add_submenu_page()` position is ignored. Administration normal normal Awaiting Review defect (bug) new 2020-12-11T16:03:26Z 2024-02-26T17:01:33Z "Hello, I'm not sure that the `add_submenu_page()` position argument is being applied properly. See the below example: {{{#!php
""+caption+""
""); I tried to add the following code to check if resize is possible: jQuery(""#TB_window"").css(""width"",""450""); jQuery(""#TB_window"").css(""height"",""120""); this failed generally (although it worked when executing the command in the browser console) " harmr Future Releases 44710 Upload plugin and theme functionalities are not removing uploaded files after failure conditions. Administration 4.9.7 normal normal Awaiting Review defect (bug) new 2018-08-03T00:11:59Z 2020-12-25T07:25:08Z "Within wp-admin, an administrator user may upload files by using the Upload Plugin functionality (Plugins -> Add New -> Upload plugin) and the Upload Theme functionality (Appearance -> Themes -> Add New -> Upload Theme) These processes uploads the user submitted file to /wp-content/uploads/{month} first, then attempts to extract it to the plugins or theme directory (The form expects a .zip file, yet allows any mime-type or extension for uploaded files, such as images, or .php files). If the process fails for any reason the uploaded file remains in /wp-content/uploads/ and/or /wp-content/upgrade/ It would be best if the plugin and theme upload functionalities properly clean up the uploaded files if a plugin or theme fail to properly get extracted and/or installed. Note: On successful installations of a plugin or theme, the uploaded file is being properly removed from /wp-content/uploads/ and/or /wp-content/upgrade/ " rawrly Future Releases 50815 Use consistent checks for displaying the Filter button in different list tables SergeyBiryukov Administration normal normal Future Release defect (bug) reviewing 2020-07-29T23:01:05Z 2021-06-08T22:08:04Z "As an extension of #40188, let's bring some consistency to `class-wp-posts-list-table.php` and `class-wp-ms-sites-list-table.php` to check `$this->has_items()`, instead of `! empty( $output )`. " whyisjake Future Releases 59446 Use script helper functions in admin to enable Content-Security-Policy opt-in Administration 5.7 normal normal Future Release defect (bug) new 2023-09-25T23:39:22Z 2023-11-03T17:27:17Z "In #58664 the script helper functions—`wp_get_script_tag()`, `wp_print_inline_script_tag()`, `wp_get_inline_script_tag()`—were leveraged to eliminate manual construction of script tags on the frontend and the login screen. These were introduced in #39941. This made it possible to opt-in (see [https://gist.github.com/westonruter/c8b49406391a8d86a5864fb41a523ae9 example plugin]) to a Strict Content-Security-Policy ([https://csp.withgoogle.com/docs/strict-csp.html Strict CSP]) to guard against any possible XSS exploits. The scope in #58664 was limited to the frontend and the login screen because of the sheer number of inline scripts printed on the wp-admin. Additionally, the site editor and block editors make use of dynamically-constructed script tags in the editor iframe which is a Strict CSP violation. Much of the work to rework inline scripts to use `wp_print_inline_script()` in the admin can be seen in an [https://github.com/WordPress/wordpress-develop/pull/498 existing PR] (now stale) from @enricocarraro. See also #59444 which is about how to improve the developer experience of working with these JavaScript string literals." westonruter Future Releases 58335 WordPress Dashboard Collapse Menu Transition issue. Administration 5.2 low normal Awaiting Review defect (bug) new 2023-05-17T04:37:06Z 2024-01-11T21:01:22Z "Hi When I collapse the menu it's showing awkward. See the video: https://d.pr/v/34K9H4 I think this issue should be fixed as soon as possible. Regards" shuvo52 Future Releases 57129 Wrong Page Template Displayed in 6.1.x Administration 6.1.1 normal major Awaiting Review defect (bug) new 2022-11-16T13:14:15Z 2023-02-23T21:49:10Z "Starting with 6.1, the wrong (newly revamped?) page template display in the page editing screen shows the wrong template. In the attached screen shots, the page in question is using a template called ""Blog Landing Page"", but the display says ""Default template"". When you click ""Default template"", it brings up the selector box which shows that it is indeed the Blog Landing Page template, but even when the selection is made again and the ""Update"" button is clicked, the wrong template name is displayed. I first noticed this error with WordPress 6.1, and it is still there in 6.1.1." taupecat Future Releases 59272 wp-admin search/column order not working when running not on port 80 Administration 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-02T12:49:40Z 2023-09-02T12:49:40Z "Hey, we are currently running WP 6.3.1 internally on a different port ( localhost:8182 ). WordPress itself works without problems. Only when you on the wp-admin page search for a keyword in a CPT or change the order, the port gets deleted from the URL. I found following part of the core source where the problem happens: https://github.com/WordPress/WordPress/blob/master/wp-admin/includes/class-wp-list-table.php#L1381 Would be nice to respect the site url from the settings or not delte the port when used." canic Future Releases 34957 #a11y-focus: Standardizing the handling of :focus and :hover adamsoucie Administration 4.4 normal normal Future Release enhancement assigned 2015-12-09T23:47:22Z 2019-05-06T16:06:43Z "After the discussion of [ticket:34876] with @mor10 and @michaelarestad, we've realized there are two main cases: * Times when the :focus and :hover states can be the same * Times when they need to be different In order to tackle the general :focus problem we'll need to: 1. Define which elements fall into which category 1. Establish a standard implementation for each category 1. Implement the new standards This could quickly evolve into a larger project, but we want to start resolve the :focus/:hover to make sure that gets addressed. This ticket is intended to start the conversation and put the attention on :focus. This is an important a11y issue, as [ticket:34876] shows there are still elements that lack a :focus state completely. As part of this plan, we'll identify those elements lacking :focus and address both the lack of :focus and the correct implementation at the same time." adamsoucie Future Releases 27916 Add New Post screen nonce failure should redirect to Edit Post screen Administration normal normal Future Release enhancement new 2014-04-19T13:27:55Z 2017-05-12T19:19:25Z "Last night I added a new post, but I didn't publish it, I just left the Add New post screen open. I did a few other things and then put the computer to sleep. This morning I got up, checked the draft, and then hit publish. But the nonces had expired, so I was shown the ""Are you sure you want to do this?"" screen. I hit ""try again"", but I was returned to the Add New Post screen. I really thought I had lost the post. (Oh, the agony.) Fortunately, I really hadn't, because it was saved as a draft. But it really scared me. Instead of causing folks to have a heart-attack, we could direct them to the Edit Post screen with the draft they were working on loaded, instead of the Add new post screen." jdgrimes Future Releases 36882 Add a reusable admin CSS class for destructive actions joedolson* Administration normal normal Future Release enhancement accepted 2016-05-18T22:54:26Z 2023-09-27T03:27:23Z "As generally recommended, plugin authors should not use regular buttons for destructive actions, like removing something. However, while there are standardized classes for buttons in WordPress admin (`button`, `button-primary`, `button-secondary`), a similar standardized class is missing for the destructive link. There are several locations in the admin where such links are displayed, but these are all styled using their individual selectors. Therefore plugin authors who want to use this style must either use one of these selectors (that probably do not fit the use-case at all) or recreate the style manually. Therefore I propose to standardize these style rules for a specific class, for example something like `delete-button` or `delete-link`." flixos90 Future Releases 42952 Add comments about JS removal of message query_arg Administration 4.9.1 normal normal Awaiting Review enhancement new 2017-12-21T01:20:25Z 2022-03-02T22:21:43Z "This is a follow-up to #23367. Can someone '''please''' add some inline doc about how Javascript actually removes `&message=x` from the URL - Specifically in `/wp-admin/edit-form-advanced.php:186` (in WP 4.9.1). As a plugin developer who looks up source code for solutions, I was wracking my brain around seeing `$_GET['message']` as the main argument for showing admin notices, but never seeing it in backend. Took unnecessarily long time to figure out it actually exists and is just hidden." davidsword Future Releases 50442 Add prefixes to all admin notices (Warning, Error, Success, Info) joedolson* Administration normal normal 6.6 enhancement accepted 2020-06-21T14:39:17Z 2024-02-06T15:13:03Z "This is a continuation #47656 From @afercia comment (ticket:47656#comment:47) - Make sure all the Error and Warning notices use respectively an ""Error:"" and ""Warning:"" text prefix - Further discuss whether also the ""Success"" and ""Info"" notices should use a similar text prefix - Update documentation related to admin notices, for example: https://codex.wordpress.org/Plugin_API/Action_Reference/admin_notices and https://developer.wordpress.org/reference/hooks/admin_notices/ - Create a new issue on the Gutenberg GitHub to add text prefixes for the editor notices: right now, none of them uses a prefix (see screenshot below) I would like to add - Combine strings constructed like `__('Error:') . __('any string')` into one string for better context for translators." kebbet Future Releases 26691 Admin Color Schemes: generic classes for colors Administration 3.8 normal normal Future Release enhancement new 2013-12-20T15:59:01Z 2020-09-19T06:53:21Z "Our team is trying to adapt our plugin to the new admin color schemes. It would be great if we could have generic CSS class declarations that allow us to apply the current scheme's background/text colors to our elements. Something like .admin-color-flat .sidebar-background-color{ background-color: #.... } .admin-color-vineyard .sidebar-background-color{ background-color: #.... } This would allow plugin developers to leverage those schemes without having to reinvent the wheel every time, and would make their plugins adapt to any third-party color scheme people may be using on their site. WordPress already adds the current color schema class to the body tag. But then I don't see anything in the CSS that I could use to recycle, let's say, the admin sidebar current background color and use it as the background color for my metabox headers. Yes, I could do this in jQuery, but I was hoping for a pure CSS approach. " coolmann Future Releases 11515 Admin needs standardized way of handling messages (notices) displayed to the user Administration 3.0 normal normal Future Release enhancement new 2009-12-19T19:53:03Z 2018-11-16T18:43:03Z "If you try to upload a media item under Media > Add new without an uploads directory, you get the following vague error message: {{{ Error saving media attachment. }}} If you try instead to upload from the post edit page, you get a much more helpful message: {{{ Unable to create directory /path/wp-content/uploads. Is its parent directory writable by the server? }}} In each case, the root error is the same, but the second error message points the way to a solution. Even if the user doesn't know herself what that message means, it's a message that provides the necessary information to someone else who does and is trying to help the user. The first message is completely useless, as it states only what we already know: something went wrong. The reason Media > Add new doesn't offer a helpful message is that the error is generated on one page request, and ''then'' the user is redirected to another page. We need a standard, cross-page-load way of conveying messages in admin. I've thought of a few possible ways of doing this: * Define and use a standardized set of error codes and associated error messages. This is similar to what happens currently on many pages: the unhelpful ""Error saving media attachment."" appears when the message argument is set to ""3."" What I'm suggesting would use a common set of message codes across the admin and be much more detailed. So the above situation would instead produce a message like ""Unable to create the uploads directory."" * Save error messages to a cookie. Unlike the previous method, this would allow messages to be made particular to their event. * Have some kind of user messaging stack. New messages would be pushed into a user's stack (stored in usermeta) and popped off after a certain time, or when read, etc. This has the advantage of lasting across sessions and browsers and being usable for other applications, such as PMs between users. What do you think?" filosofo Future Releases 18769 Admin should not break if URL changes Administration normal normal Awaiting Review enhancement new 2011-09-24T22:58:42Z 2022-02-06T14:07:17Z "We manage a lot of users who have WordPress blogs, and probably the number one user support request we have to field comes out of this situation: 1. User decides they want to move their WordPress, 2. They move the folder to a new URL, 3. Their admin page stops working, because it still had the old URL hard-coded. This is silly and should be fixed." AmbushCommander Future Releases 48928 Align selects in .form-table's within admin settings with their neighbour inputs for a more uniform feel Administration normal normal Awaiting Review enhancement new 2019-12-10T18:43:46Z 2022-09-09T08:11:09Z "Hello, Reviewing the admin settings on several screens I feel they can be given a more uniform appearance if the selects matched the width of their neighbour .regular-text inputs. See attached screens. Having these select a uniform width with the inputs provides a more consistent alignment. Thoughts? Thanks" garrett-eclipse Future Releases 40223 Allow arrow key navigation in (all?) modals Administration 4.8 normal normal Awaiting Review enhancement new 2017-03-21T19:37:46Z 2024-02-26T12:20:19Z "Would be nice, if we could use arrow keys to navigate trough details of plugins, themes, etc inside modal on install, update and list screens. [[Image(http://i.imgur.com/hxBL2sM.png)]]" marsjaninzmarsa Future Releases 40686 CSS: introduce naming and usage conventions for JS targeting Administration normal normal Awaiting Review enhancement new 2017-05-07T13:34:50Z 2021-05-06T21:56:00Z "As part of the broader goal of the [https://make.wordpress.org/core/2014/12/19/core-css-roadmap/ CSS roadmap], it would be great to start introducing CSS classes naming and usage conventions for JS targeting. This need clearly emerged during the ongoing exploration to revamp the Settings API, and woud benefit all the codebase. Work on the Settings API is happening on GitHub and [https://github.com/wpaccessibility/settings-api-enhanced/issues/11 there's an open issue for this]. Quoting from the doc @helen prepared to share some thoughts (the doc is available on the GitHub issue): > Reusing styling class names is fragile and obscures intent when doing long-term maintenance. Personally, I can only add that I can't count the number of times when touching some CSS class or ID forced me to check all the codebase to make sure they weren't used also for JavaScript related purposes :) " afercia Future Releases 39852 "Change the confusing ""Screen Options"" button text" Administration normal normal Awaiting Review enhancement new 2017-02-12T08:52:23Z 2017-03-21T19:12:44Z "From a new users perspective the label ""Screen Options"" doesn't make any sense. Seems technical, it doesn't express anything meaningful. From a general perspective by reading a buttons text it should be clear to users what it does. Besides that the text Screen Options is not that common either. In my opinion, It would be easier and meaningful if it uses one of these : '''1. see more''' '''2. more information''' '''3. display more''' '''Google Books Ngram Viewer '''how many times these terms has been used (from year 1800 to 2000) [[Image(http://i.imgur.com/QgOeB0e.png)]] '''Google Trends '''[[Image(http://i.imgur.com/CA2SHv4.png)]] Reference: 1. Design Words With Data [https://medium.com/dropbox-design/design-words-with-data-fe3c525994e7#.hv4ce0o2q] 2. How To Design Words [https://medium.com/@jsaito/how-to-design-words-63d6965051e9#.tfmbqs2ux]" cryptex_vinci Future Releases 47544 Code Editor not listing files/folders in the right order Administration 5.2.1 normal minor Future Release enhancement new 2019-06-15T08:13:32Z 2019-08-28T17:28:38Z "On new installations on test sites, I have seen the correct order for listing of files/folders in the code editor. ie: - important files - folders - files in the root. However, in my installation, I don't get the same order. Example screenshot attached. [[Image(https://i.imgur.com/MSaqTUc.png)]] readme.txt and composer.json should be lower in the list. " superpoincare Future Releases 41804 Combine and Relocate Editor Menu Link Administration normal normal Awaiting Review enhancement new 2017-09-05T16:21:07Z 2020-11-24T01:59:00Z "While discussing #31779, I recommended the following: 1. Move the Editor into the Tools menu, or into Tools > Available Tools. It fits better there anyway: it's not a visual editor for the Appearance, as other things are in the Appearance menu), but the other problem with Plugins > Editor is it's right beside one of the most clicked buttons in the UI (Add New). It's too easy to discover. You could also move the warning messages suggested above into a box on Available Tools. Instead of a warning, it becomes the context for launching the Editor. Plus, what else is going on in that page anyway. :) 1. To do the above, combine the Theme and Plugin editors into one. Separate the edit dropdown with headings for Theme and Plugins. @melchoyce recommended splitting this out into a separate ticket (ticket:31779#comment:54)." cliffseal Future Releases 37228 Consider to rethink and improve the list tables pagination links Administration normal normal Future Release enhancement new 2016-06-29T14:04:15Z 2019-04-19T20:13:48Z "Splitting this out from #33962. See also #32558. Quickly discussed at WCEU 2016 Vienna's Contributor Day with @karmatosed and @hugobaeta and noticed the pagination links offer room for design improvements. Looks like there are no apparent reasons (other than historical ones) why the top and bottom pagination links should differ and maybe the editable input field should be displayed only when there are more than 3 pages. As @helen pointed out, also the interactions could benefit from some rethink. This would probably be a very nice ticket for designers willing to contribute :) Current state on 4.6 trunk: [[Image(https://cldup.com/jPRxp_462C.png)]] with longer translated strings: [[Image(https://cldup.com/lkdtPkEn0P.png)]]" afercia Future Releases 7797 Consolidate iframe headers Administration 2.7 normal normal Future Release enhancement assigned 2008-09-26T23:35:46Z 2019-03-15T00:31:49Z "Currently iframes are being used in multiple locations (ie. thickbox, plugin re-activation, etc) and in each case, theres generally a function for the header and footer, or its inline. What i suggest, Is to create a standard set of admin templates which print the headers out for the pages. And a side suggestion:[[BR]] As an added bonus, It should probably be possible to automatically detect if it was loaded via thickbox ($_GET[TB_iframe] shouldnt be set) and serve the correct header (ie. Full admin side menu if no thickbox)" DD32 Future Releases 39707 Create onboarding flowchart for users of WP.org installations Administration 4.7.1 normal normal Awaiting Review enhancement new 2017-01-26T17:42:47Z 2017-04-03T16:45:50Z Chatting in the [design channel on Slack](https://wordpress.slack.com/archives/design), we believe documentation should exist for user onboarding. While this is somewhat related to the customizer project for setting up an install, a general user flowchart should be created. alwaysbrightblue Future Releases 48644 Establish guidelines for button order Administration normal normal Future Release enhancement new 2019-11-14T21:23:53Z 2022-03-09T14:03:04Z "''This issue has been moved from GitHub to Trac to increase visibility.'' Original GitHub discussion: https://github.com/WordPress/gutenberg/issues/7534#issuecomment-549980093 There is a need to establish guidelines for button ''group'' position and button ''order'' within the group. There are two patterns that need to be documented: - **A pattern for the button group position**. It's OK for the group position to be different based on context ( e.g. right-aligned group in dialogs). This also includes making sure that related buttons are in close proximity (existing trac issue: #40822). - **A pattern for button order**. A consistent button order is important for accessibility so that the first and second actions are predictable throughout the UI (e.g. confirm is always first and cancel is always second). Important to note that currently the [https://github.com/WordPress/gutenberg/blob/ed31b3a27be2faf6a60a52609e4e13c263989bfe/packages/components/src/modal/README.md WordPress Component documentation] aligns buttons to the right, with the primary action second in the visual order: [[Image(http://cldup.com/g0FeStpTYa.png)]] == Button group placement This one is a bit easier because as explained above, it's OK for the group position to be different based on context. Usually you want the buttons on the left for screens with forms because that’s where the eye travels. Same logic can be applied to dialogs as well — actions are usually on the right because that’s where the eye travels. We can figure out what patterns to standardize and document them. == Button order === Platform conventions For dialogs: on Windows, primary is always first. For Apple and Google, primary is always second: [[Image(http://cldup.com/2XlrtvLb_N.png)]] In some cases primary first is the ideal order, but sometimes primary second is the ideal order. This is where we are blocked. If we deviate and have inconsistent ordering, then this is not ideal from an a11y point of view. === Button order options ==== Option A [[Image(http://cldup.com/Dq0URpOzDD.png)]] - Primary action is always first (to the left), regardless of button alignment - Secondary action is to the right of the primary action The disadvantage here is that it’s in conflict with the idea that primary or confirming actions suggest ''forward motion'' and secondary or dismissive actions suggest ''backward motion''. Sometimes it can be subtle like: - **Ok** (forward) and **Cancel** (backward) - **Agree** (forward) and **Disagree** (backward) Sometimes it’s more literal like: - **Continue** (forward) and **Cancel** (backward) - **Next** (forward) and **Back** (backward) If the primary action is the first action, it can look wrong and unnatural: [[Image(http://cldup.com/-TPEm9EuQl.png)]] Here’s a real example in WP Admin, of where I think Option A falls short: [[Image(http://cldup.com/Y70_6ejJtu.png)]] Notice in the second dialog how the “Go Back” button is on the right, when it should be on the left to indicate backward motion. Additionally, in a NUX or wizard type of interface where there are multiple steps, it usually makes sense to have a ""Back"" and ""Next"" button (Next is usually the primary action). It would look unnatural if the Back button was on the right. ==== Option B [[Image(http://cldup.com/Qc2C_OthsH.png)]] - Primary action is always second (to the right), regardless of button alignment - Secondary action is to the left of the primary action The disadvantage here is that it feels “unnatural” for the primary action to be second in a settings form context. It seems like the primary action should be the leftmost one because that’s where the eye travels. ==== Option C [[Image(http://cldup.com/NvNzBm60xG.png)]] - The visual and DOM button order is different, depending on button group alignment - If button group is aligned to the right, the primary action is second (to the right) - If button group is aligned to the left, the primary action is first (to the left) More reading: - [https://adamsilver.io/articles/where-to-put-buttons-in-forms/ Where to put buttons on forms] by Adam Silver - [https://www.nngroup.com/articles/ok-cancel-or-cancel-ok/ OK-Cancel or Cancel-OK? The Trouble With Buttons] by NN/g " drw158 Future Releases 47579 Featured image Drag and Drop UI / UX Administration normal normal Future Release enhancement new 2019-06-20T13:48:34Z 2019-07-31T19:11:46Z "Hello! I've been advised this applies to Core / Design so I'm going to report my feedback here as well. This is an issue related to Gutenberg but it's not a part of the Block Editor. It's a Gutenberg feature but one that's in Core. **Original GitHub issue:** https://github.com/WordPress/gutenberg/issues/10426 **Issue:** The featured image visually appears as drag and drop, however, it's just a button. Drag and drop does not work. **Motivation:** I personally find it confusing and when I raise the question to other WordPress users their feedback is the same. They assumed it was drag and drop but never tried it. **Suggestions:** Option 1. Update the UI (technically a roll back) to appear as a button or link. This would match the UI with the user experience. Option 2. Add drag and drop support. Since this is a part of Gutenberg, the necessary JavaScript / API for this function should already be there. " emaildano Future Releases 50699 Fix and improve arranging metaboxes azaozz Administration normal normal Future Release enhancement assigned 2020-07-19T17:32:37Z 2022-06-03T20:04:33Z "Follow-up to #49288. In 5.5 the drop-areas when dragging/arranging of metaboxes on the Dashboard and the old Edit Post screen were fixed/improved. However that introduced an always visible drop-area on the Dashboard when only one metabox is visible. Seems better to fix that bug and at the same time improve/enhance how metaboxes are dragged/moved/arranged in general." azaozz Future Releases 27127 Improve plugin search on installed plugins page Administration 3.8 normal normal Awaiting Review enhancement new 2014-02-14T17:16:53Z 2023-04-12T16:18:45Z "If you have lots of plugins installed trying to find one in the installed plugin page is not quick. The search box is quite slow ( requires a page refresh ). Adding some JavaScript that transforms the current search box into a quickfind box would help solve this problem. As the user types a keyword the JavaScript searched across the displayed text for the plugin, only displaying the plugins that contain that keyword." enej Future Releases 39617 Improve the Dashboard Screen and Welcome dashboard widget Administration 4.7.1 normal normal Awaiting Review enhancement new 2017-01-17T20:04:18Z 2017-03-23T19:03:03Z "Currently the welcome dashboard widget only offers a few options, it does not cover making sure that a new has added a site name, site description, set permalinks or made sure that a user has created their first page and post on the site. https://codex.wordpress.org/Dashboard_Screen#Welcome Giving users a better flow from the dashboard screen would help them get started on their site." lukecavanagh Future Releases 44391 Improving the notification badges in admin menu hedgefield Administration normal normal Awaiting Review enhancement assigned 2018-06-18T10:24:13Z 2021-11-10T18:32:07Z "During the WCEU contributor day we received the request from the A11y team to look at the notification badges in the admin menu. Their red color and lack of context was seen as something that could be improved. So together with Jayman Pandya, Rich Copping, Jasper Cheyney and Vasilis Baimas we looked at different ways to improve this. We first explored ways to add more context with text or expandable rollovers or tooltips, but agreed that this was not good. So we focused on improving the styling itself. I've attached the design explorations we did below. By moving the badge onto the icon, adding a border and optionally omitting the number (this should be tested), we felt like this would be a nice improvement for the visually impaired, as well as a more calming design layout. Adrian Roselli took a look and agreed that this would be a good improvement, with his preference also going to design 3 and 4 (with 1 being the current situation). We will try to make a PR for this if this sounds like a good idea to you all too. Putting the badge on the icon is also a nice step towards the pattern of the notification center proposal: #43484" hedgefield Future Releases 47890 Indentation within Post Publish (Classic Editor) and Comment Save Metaboxes: Administration normal normal Awaiting Review enhancement new 2019-08-17T12:53:54Z 2021-12-14T18:43:02Z "This is a spinoff from ticket #43587, as suggested by @melchoyce https://core.trac.wordpress.org/ticket/43587#comment:23 to add an indentation for subitems of the Post Publish Metabox for the Classic Editor and the Comment Save Metabox. " birgire Future Releases 33566 Keyboard shortcuts for all functionality of Dashboard + Admin Menu while in read mode Administration 4.3 normal normal Future Release enhancement reopened 2015-08-26T21:52:34Z 2022-12-07T13:50:13Z "I'm constantly hitting cmd+s (or meta+s) in the appearance file editor. I'm also constantly looking for a short cut to preview or publish a post. Aside from the accessibility assistance, I think an addition like this would make WordPress very ""Power User"" friendly. I know the meta+s command works in the post/page editor but the interaction is so subtle, I'd to do it a few times before I saw the ""Draft saved..."" comment at the bottom. I had a notion that something like meta-key + down arrow might overlay a set of keyboard instructions. Things like ""cmd/ctrl + s = Save Draft, cmd/ctrl + shift + L = Preview Post, cmd/ctrl + p = Publish Post/Page"" etc. Obviously, this needs work. Is this something in the pipeline? If not is this something I can propose?" tady Future Releases 51343 Move Current Submenu to top of Admin Menu Administration normal minor Awaiting Review enhancement new 2020-09-18T12:48:11Z 2022-09-09T07:29:48Z "I propose moving the **current open submenu** to the **top of the adminmenu** so users can more easily navigate to submenu items without having to scroll. This would be especially helpful when using smaller viewports and/or sites with large/numerous submenus. The following CSS accomplishes this: {{{ #adminmenu { display: flex; flex-flow: column; } .wp-has-current-menu { order: 1; } .wp-not-current-submenu { order: 2; } #collapse-menu { order: 3; } }}} " markpraschan Future Releases 38453 New UI for the settings page of the dashboard Administration normal normal Awaiting Review enhancement new 2016-10-23T12:00:08Z 2019-10-26T09:12:42Z "The dashboard settings page is very basic looking - build using simple table markup and has almost zero stylings applied. I would like to suggest a change to this, where new visual elements and better organization is added to the page. Meaning - better separation between different components, description, larger click area/input fields, validation of the input fields and so on. In short - bring the settings pages to more modern look. It won't add new features to it, so the users won't be required to make choices but instead it will make the general experience of the page better. I am attaching sample mockup/idea screenshot I had on top of which I can work more based on the feedback and if this is needed in the first place. Any input regarding is welcome. ---- Here is the screenshot: [[Image(http://i.imgur.com/KQHZiHk.png)]] The validation is there to show how it can look, not that I focus on this. Honestly, I believe while it would be awesome it's not of very high priority to have it. Another thing I want to comment about the design - the tabs on top are also only an idea, I can see how they can be a problem instead of a solution, so thoughts regarding this is also welcome. It's there just to show it visually" xavortm Future Releases 48452 Proposal: improve distinction between buttons and other controls Administration normal normal Future Release enhancement new 2019-10-28T21:08:05Z 2021-03-02T16:32:57Z "New button styles were introduced in ticket #34904. As discussed in the comments on this blog post, [https://make.wordpress.org/design/2019/09/06/discussion-higher-contrast-form-fields-and-buttons/ Discussion: Higher contrast form fields and buttons], the secondary (or default) button style is no sufficiently distinct from input fields and other similar UI controls. This ticket attempts to remedy the issue and create a consistent styling of UI controls that is more usable. By seeing a set of UI controls together, we can figure out the best approach holistically. **The main concern that was raised is that the new default buttons are styled similarly to inputs, and it could be confusing for folks if they can't differentiate them.** Example: [[Image(http://cldup.com/wvn2VchDdY.png)]] Proposed solutions, compared directly: [[Image(http://cldup.com/vYhbr_PI36.png)]] - Option A: subtle background color, bold text - Option B: blue and bold text - Option C: subtle drop shadow, bold text In context, with more UI: Option A [[Image(http://cldup.com/7nma8vFVbm.png)]] Option B [[Image(http://cldup.com/XYDICcgCV7.png)]] Option C [[Image(http://cldup.com/bThhBvpVUp.png)]] --- Something to be considered separately from color and shadow is shape. What about using square corners for text inputs? [[Image(http://cldup.com/z8G9_qr_AX.png)]] Note: - These mockups do not include interactive states, although those will need to be explored. I think it's important these styles stand on their own first. - Testing these styles in the context of a real UI in WordPress will be the next step. - Please ignore labels and text. This is just to test the UI styling. - Text is using the default macOS system font. - Even though dark mode doesn't exist in WP, it's a good test to see how the styles hold up in an inverted color scheme. - I believe all proposed solutions meet AA color contrast guidelines. - Shadows will be removed it Windows high contrast mode, and we need some other visual indication other than color to distinguish the UI elements. This is my first ticket, so apologies if I missed any standard practices." drw158 Future Releases 43303 Providing hooks for html table markups in do_settings_{sections|fields} Administration normal normal Awaiting Review enhancement new 2018-02-13T00:48:48Z 2023-07-03T12:55:58Z "I Apologize if this is silly thing but having hooks may enable customization opportunity for opening/closing table markups of '''do_settings_sections''' and likewise with fields. while maintaining table markups by default for core & other Settings API pages. '''do_settings_sections''' {{{ echo ''; do_settings_fields( $page, $section['id'] ); echo '
'; }}} Something like {{{ do_action( 'do_settings_sections_opening_wrapper_{$page}, 'default_handler' ); }}} " aranwer104 Future Releases 16413 Settings page needs HTML refactoring and UI improvements joedolson* Administration 3.1 normal normal Future Release enhancement accepted 2011-01-30T20:22:09Z 2023-11-10T16:20:51Z "The settings pages haven't had much attention or improvement in a while. We need to refactor the HTML on the settings pages, as they are still using tables instead of divs. We also want to make some minor UI improvements including: - clearer differentiation between option groupings - using consistent text styles for descriptions and links (including the time zone/date format comment) - restructure for better readability Comment if you have any other" chexee Future Releases 41442 Show nearby events in dashboard events widget in a per country basis Administration 4.8 normal normal Awaiting Review enhancement new 2017-07-25T18:51:10Z 2018-04-25T12:52:15Z "Hi! I've noticed that the new events dashboard widget don't show all WordCamps in a country basis. It shows only that ones nearby in kilometres, 400 kms as seen in code (https://meta.trac.wordpress.org/browser/sites/trunk/api.wordpress.org/public_html/events/1.0/index.php?rev=5559&marks=707,708#L703). That way, i.e., for an Spanish WordPress user from Madrid (in the geographical center of the Country) it going to be impossible to know about WordCamps in Chiclana (Cádiz) or others far away from that 400 kms standard, and totally impossible for anybody to know about a WordCamp in Las Palmas (Canary Islands), and impossible for anyone that lives in Canary Islands to know about continent WordCamps. It could be possible to extend/change the range to a country basis (best) or more kilometres?" fernandot Future Releases 57925 Unclear message when URL for non-existing admin page is called Administration 4.6 normal normal Awaiting Review enhancement new 2023-03-15T01:07:55Z 2023-03-15T17:47:14Z "If you try to visit the admin page of a plugin that is currently inactive, then currently (WordPress 6.2) the error message given is: {{{Sorry, you are not allowed to access this page.}}} Even though in this case there may not even be such a page defined. I got this message when I followed a link to the settings page of a plugin that had automatically disabled itself. A user misunderstood this message in https://wordpress.org/support/topic/after-plugin-disabled-sorry-you-are-not-allowed-to-access-this-page/ One may reach this message if following an outdated bookmark to a plugin's admin page. If possible, this particular case ""There is currently no such admin page defined in this system."" would be a better, and more actionable message." tobifjellner Future Releases 31818 Uniform Search Form Display/Experience joedolson* Administration 4.2 normal normal Future Release enhancement accepted 2015-03-31T11:05:37Z 2023-04-28T15:20:54Z "In our recent testing of the search functionality we've found that there are currently five different search types across the admin. A full description of what the tests entailed, their results, and a link to the Slack discussion can be found here: https://make.wordpress.org/accessibility/2015/03/30/usertest-the-search-functions-in-the-admin/ To summarise, these are the five that we've found: * Search input without submit button, no live search (need to press Enter) * e.g. Media Library list mode * Search input without submit button, live search fires “as you type” * e.g. Media Library grid mode, Themes (add new, wp.org API), Network Themes (add new, wp.org API) * Search input no submit button, live search fires “as you type” (more a “filter current collection” than a search) * e.g. Themes (installed themes), Customizer add widget, Plugins (installed plugins) * Search input with hidden submit button, press Enter or tab and submit the hidden button (after the search, the “typeselector” select appears) * e.g. Plugins (add new), Network Plugins (add new) * “Classic” search: search input with submit button, press Enter or submit button * e.g. Posts, Categories, Tags, Pages, Comments, Users, Network index: search users, Network index: search sites, Network Sites, Network Users, Network Themes (installed), Network Plugins (installed) What we'd like to propose is to bring this down to two and ensure they work well. This could then be used as a launchpad to further unify the search experience and use a single type across the board. The lucky two would be: * the classic one, the same for every search, with visible submit button (already commonly used) * the dynamic one, with some improvements like adding wp.a11y.speak to show the results count, and making sure focus doesn’t change dynamically " Cheffheid Future Releases 60625 Update user interface for Site icon selection Administration trunk normal normal 6.6 enhancement new 2024-02-23T15:39:53Z 2024-03-05T15:37:15Z "Currently a user can set a site icon in two places outside the site editor: the general settings screen (added in 6.5) and the Customizer. Both these places have currently a design with some years to it. This ticket is aimed to discuss the design of these two places, and possible come up with a new one, and implement it. Note that a preview also is displayed in the media modal when cropping the site icon. This ticket has it's roots in ticket #54370" kebbet Future Releases 55543 `add_menu_page` incorrectly requires SVG icon data URIs be base64 encoded Administration normal normal Future Release enhancement new 2022-04-07T23:00:35Z 2022-10-29T22:24:46Z "To determine if a developer is using an SVG in a menu, `add_menu_page` checks for a string beginning with `data:image/svg+xml;base64,`. [https://css-tricks.com/probably-dont-base64-svg/ SVGs aren't required to be base64 encoded] and encoding with base64 can increase the size of the attribute. The check ought to be modified to allow for additional encodings. " peterwilsoncc Future Releases 19707 admin-ajax.php requests via http regardless of force_ssl_admin() state Administration normal normal Awaiting Review enhancement reopened 2012-01-01T00:53:52Z 2018-03-06T13:31:02Z "Noticing these requests failing: ""NetworkError: 403 Forbidden - http://HOSTNAMEwp-admin/admin-ajax.php"" My server explicitly denies http to wp-admin. SSL only. Looks like admin_url() is giving http rather than https. I suspect this bug actually lies somewhere in get_site_url(), but I don't have time to triage this right now. This is technically a security bug since WP should always obey force_ssl_admin(), but I don't think anything is being leaked or compromised. You don't get access to anything, and nothing being sent over the wire is sensitive since it still obeys the rules of the protocol (cookie is secure). It's just a nuisance." robertaccettura Future Releases 41558 create a (reusable) wp_default_admin_scripts Administration 2.6 normal normal Awaiting Review enhancement new 2017-08-03T23:53:48Z 2022-06-29T02:24:54Z "I had to create an admin-like form in the frontend, for guests submitting content. I needed to provide {{{meta/post-box}}}, {{{autocompletion}}} and needed {{{media-views}}}, {{{wp-color-picker}}}, ... I thought {{{wp_enqueue_script()}}} would do the trick... until I discovered the {{{ if(is_admin()) }}} inside {{{wp_default_scripts()}}}. I had no other choice than copy/pasting ~210 WP LoC in my own PHP files Is there a really good reason for reserving all that cool client-side stuff to admin dashboard only? plugin/themes developers may want to load and use it for good and having all that libs already registered by core is useful. I suggest: 1. moving all the admin-oriented script into {{{wp_default_admin_scripts()}}} which should be reusable (even if non-admin), and run it if (is_admin). 2. moving all the {{{localize()}}} corresponding to these admin scripts into another {{{wp_default_admin_scripts_settings()}}} function somehow wrapped by {{{if(! is_admin())}}} 3. Document how to correctly bootstrap the dashboard in the frontend and a couple of common gotchas of these scripts (like that ajax-dashboard-pingback feature forcefully pulled as JS-dependencies and which can't be stopped, ...) " drzraf Future Releases 34991 Introduce a typographic measure for the admin screens Administration normal normal Future Release feature request assigned 2015-12-10T22:03:26Z 2020-11-12T12:14:16Z "For optimal readability, lines of text shouldn't exceed a certain length. In typography, this is called [https://en.wikipedia.org/wiki/Measure_(typography) measure] and looking around for references you will find several (different) recommendations, starting from 45-50 characters per line till 90 or even more. By the way, there's no such a thing as an absolute, perfect, number to fit all the different cases. It depends on many different factors, starting from the typeface used, its metrics, if it's a single column or multi-column layout etc. That said, when a line of text is really, really, too long, then readability, usability, and accessibility, they're all seriously affected. I'd like to encourage typography lovers and designers to start some discussion, research, and development with the long-term goal to improve typography in the admin screens. Trying to implement a ''measure'' could be a nice start. Also, I'd like to propose to consider the introduction of a new ""typography"" focus tag for Trac. In the screenshots below: a couple examples of some admin screens rendered on a large display with the browser's window maximized. [[Image(https://cldup.com/Lqn6W2CVsy.png)]] [[Image(https://cldup.com/CV2JcdQI1w.png)]] " afercia Future Releases 31284 List tables with fixed header on scroll Administration normal normal Future Release feature request new 2015-02-10T16:33:44Z 2019-01-14T17:37:47Z "I think it would be interesting, the WordPress through their APIs, allowing fix the header of a table when the scroll action is happening. A page that could make use of this functionality is the Posts list. [[Image(http://i.imgur.com/86AE2x0.png)]] and [[Image(http://i.imgur.com/O7v0Rfg.png)]] When the user has many posts, to scroll down the page, the table header is not more visible. This could also be very useful for plugin authors. That have pages with listings." Apiweb Future Releases 39635 Make insertion of generic dismissible notices in frontend code possible Administration 4.7.1 normal normal Awaiting Review feature request new 2017-01-19T02:51:45Z 2020-02-15T10:41:45Z "As a plugin developer I want to employ dismissible notices on an admin screen. All is fine as long as I use the hook in server-side code to insert them on page load. But if I want to use them in frontend code (for example to notify users of Ajax events), the only way to access the initialisation code is to hijack one of the events in [source:trunk/src/wp-admin/js/common.js#L415 common.js#L415] - with possibly heavy side effects. It would be easy to add a generic event like `wp-notice-added` that is not used by specific actions to make the live of developers easier." ccprog Future Releases 55344 Resources for hidden widgets are loaded on WP dashboard adamsilverstein* Administration normal normal Future Release feature request accepted 2022-03-08T17:39:03Z 2023-07-21T10:00:14Z "When plugins are placing widgets on the WordPress dashboard and these are hidden via the Screen Options the resources of those widgets are still loaded. In the Sources tab of the browser console this can easily be checked. I've noticed this with multiple plugins, so it looks like a core bug. It would save resources and increase performance of the dashboard if hidden items are not loaded. I've asked in the #performance Slack channel, where I was asked to create a ticket to report this as a bug." josklever Future Releases 39613 Use Shift + Delete to bypass Trash/Prompt Administration normal normal Awaiting Review feature request new 2017-01-17T08:24:39Z 2017-07-10T16:10:59Z "There are times where deleting many single items is necessary, but the bulk edit interface isn't desirable. For these situations, it might be nice to have a Shift + Delete interface, that bypasses the warnings and sends items straight to being permanently deleted. bbPress is my current example of this, where it's not uncommon to want to cherry-pick several topics/replies for different bulk actions in the same view, or mass-delete topic tags where dozens of spam tags exist and clicking ""Delete"" in every action-row brings up a dedicated prompt. Yes, you can check the boxes and use Bulk Edit to delete them, but UX wise that approach requires a bit more planning than you usually want to do when you're in cleanup mode. It isn't comfortable to queue up a bunch of internal todo's just to moderate a queue of topics & replies, but it does feel comfortable to have identified something needing doing, and to be able to do that think as quickly as possible." johnjamesjacoby Future Releases 40330 Reconsider the usage of infinite scrolling across the admin Administration normal normal Future Release task (blessed) assigned 2017-04-01T14:24:24Z 2021-05-08T11:20:11Z "As accessibility team, we've often discussed and we're aware of some a11y issues in the WordPress admin but haven't formalized them in a Trac ticket yet. That's because they're general, broad, issues and they probably can't be solved soon, as they have a big impact on the way some relevant parts of the user interface are built. They would require some extensive discussion and research. Nevertheless, if we're not going to at least open a discussion, the solution is not going to happen 🙂 . During the last accessibility weekly meeting we've decided to open a series of tickets and use a special keyword to group them, something like `a11y-task`. This is the first ticket of the series. Infinite scrolling (sometimes known as ""endless scrolling"") can be a serious accessibility barrier. It's used in the admin in a few places, for example: - Media Grid - Add Themes screens - Customizer > Add menu items - Editor > Insert/Edit link > Search - any other places? For a comprehensive view of all the potential issues, I'd refer to the list of resources below. I'd recommend everyone to have a look at those posts. I'd say the issues can be grouped in three different categories: accessibility, usability, and performance. Just to mention some of the most relevant ones: - a11y: it's impossible or very hard for keyboard users to reach content placed after an infinite scrolling region: think for example at the Media Grid, where tabbing through attachments loads more and more attachments (potentially hundreds or thousands of them) forcing users to keep tabbing indefinitely - a11y: no audible feedback or instructions about how infinite scrolling works, the current and total number of items, or when new items get loaded - usability: infinite scrolling often breaks the browser's history - usability: there's no JS fallback - performance: memory footprint can be huge, especially when loading hundreds of big images, see the Theme install screens Resources mostly focused on accessibility: http://adrianroselli.com/2014/05/so-you-think-you-built-good-infinite.html http://simplyaccessible.com/article/infinite-scrolling/ http://www.webaxe.org/infinite-scrolling-and-accessibility/ http://www.ssbbartgroup.com/blog/infinite-scrolling-impact-on-assistive-technologies-series-1/ Resources mostly focused on usability: https://webmasters.googleblog.com/2014/02/infinite-scroll-search-friendly.html https://www.nngroup.com/articles/infinite-scrolling/ https://www.sitepoint.com/ux-infinite-scroll-good-bad-maybe/ http://www.webdesignerdepot.com/2015/11/how-infinite-scrolling-breaks-ux/ https://www.smashingmagazine.com/2016/03/pagination-infinite-scrolling-load-more-buttons/ https://www.smashingmagazine.com/2013/05/infinite-scrolling-lets-get-to-the-bottom-of-this/ Resources focused on memory footprint: http://engineering.linkedin.com/linkedin-ipad-5-techniques-smooth-infinite-scrolling-html5 https://www.sencha.com/blog/the-making-of-fastbook-an-html5-love-story/ http://dannysu.com/2012/07/07/infinite-scroll-memory-optimization/ Maybe for the future: the ARIA role `feed` https://www.w3.org/TR/wai-aria-1.1/#feed (at the time of writing, ARIA 1.1 is still a Candidate Recommendation, and as far as I know, no assistive technologies support the role `feed`) See also: http://www.ssbbartgroup.com/blog/differences-aria-1-0-1-1-additions-role/ See #19815, #28927, #28998. " afercia Future Releases 40925 Review the usage of the change event on select elements joedolson* Administration normal normal Future Release task (blessed) accepted 2017-06-05T12:47:01Z 2023-09-22T16:09:18Z "See also #31634 The change event can be problematic when used on select elements because browsers fire the event in different ways across different platforms. In this ticket I'll try to clarify what this difference is, why it matters for keyboard users, and why some actions shouldn't be triggered when a select option gets selected. On macOS, when using the keyboard to navigate content and a select element gets focused, using the arrow keys always opens the select ""drop-down"": [[Image(https://cldup.com/rU6roN4wAO.png)]] This behavior allows users to explore the content of the select, scroll through the options, and select an option pressing Enter or Spacebar. This way, the change event fires after an explicit user action. Instead, on Windows using the arrow keys on a select doesn't automatically open the ""drop-down"". To clarify what happens, I've made a short video using the Archives and Categories widgets as an example: https://cloudup.com/iuFxQ7CkA7k Historically, this behavior was typical of all browsers on Windows, except Firefox. However, a recent change made Firefox behave like all the other browsers. For more details, see https://bugzilla.mozilla.org/show_bug.cgi?id=1350700 Since the drop-down doesn't open (it does only when pressing Alt+Down arrow), it's hard to scroll the list of options without firing the event at each arrow keys press. Users would need to explore the content of the select before making a choice, and to do so they use the arrow keys. However, while exploring the select content, the action associated to the change event runs. In the case of these widgets, the action triggers a full page reload. Actions that have a big impact like a full page reload or a complete change of context should only be triggered after an intentional choice of the user, i.e. when pressing a button close to the select. In other cases, when the action triggers minor changes, using the change event could be OK. The best option would probably be to evaluate the interaction on a case by case basis. There are a few places in WordPress where the change event is used this way, not pretending to be a complete list, here's some of them: Media views: - Filter by type - Filter by date Customizer - Menu > Menu locations - Static front page > A static page" afercia Future Releases 23432 "Review usage of target=""_blank"" in the admin" sabernhardt* Administration 3.2 normal normal Future Release task (blessed) accepted 2013-02-09T15:26:25Z 2023-11-17T17:54:28Z "Some links in the Setting Pages (General, Discussion, Permalink) pages open in same window, which sometime can be awful. [[BR]] While the users can press cmd/ctrl + click and click the link to open it in new tab but If the user does not open the link in new window, options (which are not saved) will be lost and one have to go through them again.[[BR]] Also links in the Edit Profile page and all the links in the help tab open in new window except a few.(so it is possible that users may just click it thinking them to alike other links which open in new window)[[BR]] So a consistency will be there and ux can be a little better." theadityajain Future Releases 26504 Semantic elements for non-link links joedolson* Administration 3.8 normal normal Future Release task (blessed) accepted 2013-12-09T14:29:18Z 2024-01-30T15:12:56Z "Using the [http://heydonworks.com/revenge_css_bookmarklet/ revenge.css bookmarklet] on the dashboard gives a very [http://d.pr/i/yVYh clear indication] that some of the links on there are semantically incorrect - they should be buttons, even if they should look like links. The Actual Buttons Are Actual section of this [http://coding.smashingmagazine.com/2013/08/20/semantic-css-with-intelligent-selectors/ article] sums it up nicely why. Unless the accessibility team have indicated otherwise, each of the 74+ occurrences (only counting PHP files, more in JS files) of links with `href=""#""` should probably be a ` // Basic CSS: .no-button { background: none; border: none; color: #0074a2; } .no-button:hover { color: #2EA2C9; cursor: pointer; } " GaryJ Future Releases 47682 "The links ""hover"" color has insufficient color contrast" joedolson* Administration normal normal 6.6 task (blessed) accepted 2019-07-11T12:32:43Z 2024-02-06T15:50:53Z "Supersedes #35622 and #47157. During the contributor day at WCEU 2019, it was proposed to merge #35622 and #47157. They're strictly related and the root issue needs to be tackled holistically across the whole WordPress admin. == Problem Default links (and ""button-links"") in WordPress are blue. The ones for destructive actions are red. Generally, the default colors for their normal state do have a sufficient color contrast ratio of 4.5:1 with the background. However, the colors used for the ""hover"" (and ""active"") state don't. == Relevant standard W3C Web Content Accessibility Guidelines (WCAG) [https://www.w3.org/TR/WCAG21/#contrast-minimum 1.4.3 Contrast (Minimum) (Level AA)] == Details #35622 dived into the red links issue and after some exploration it became clear that finding a color **pair** (one color for the normal state and one for the hover/active state) that always works across the admin, is nearly impossible given the several, different, background colors used in the admin pages. Part of the problem is that the hover color is ""lighter"" than the default one. Worth noting the color used for the ""focus"" state is darker instead. More importantly, there are several different background colors, including [https://core.trac.wordpress.org/ticket/35783 an arguable amount of grey shades]. Trying to summarise the reason why #35622 didn't progress: - darkening the ""hover"" red forced to darken also the default red - once a new color pair was identified, it worked well on ''some'' backgrounds - however, it didn't work on other darker backgrounds - started from scratch and further darkened the color pair - it worked on more backgrounds - found edge cases - darkened the color pair again - at some point the normal red was so dark to look almost ""brownish"" - failure The same problem applies to the blue links, as reported in the WPCampus accessibility report. See #47157. == Some examples **The ""hover"" blue `#00a0d2`:** 3.02 contrast ratio on white background 2.67 contrast ratio on the admin default grey background `#f1f1f1` 2.87 contrast ratio on the tables zebra-stripe grey `#f9f9f9` **The ""hover"" red `#dc3232`:** 4.62 contrast ratio on white background (which is OK) 4:39 contrast ratio on the tables zebra-stripe grey `#f9f9f9` 4.09 contrast ratio on the default grey `#f1f1f1` 4.16 contrast ratio on media views grey `#f3f3f3` 3.98 contrast ratio on customizer grey `#eee` Note: these are just a few examples. There are more background colors to take into consideration and also edge cases, e.g. the yellow background for unapproved comments. == Some screenshots [[Image(http://cldup.com/q5MYm6DKL1.png)]] [[Image(http://cldup.com/rawfy7Eth9.png)]] [[Image(http://cldup.com/IoW1cBF-Pl.png)]] [[Image(http://cldup.com/PGDfF4zXTZ.png)]] [[Image(http://cldup.com/PMx2qmF8zQ.png)]] [[Image(http://cldup.com/Kgp8htI4g5.png)]] [[Image(http://cldup.com/vdAtUeFEyZ.png)]] == Questions and possible options - Does the hover state needs to be communicated with a color change in the first place? - If so, does the hover color needs to be ""lighter""? Using the darker color already used for the ""focus"" state may help. Generally, the color used for the hover state shouldn't be ""lighter"", as that reduces contrast right in the moment when users need it the most. - Are there better ways other than a color change? For example: toggling the link underline, or using a border, or an additional shape, would allow to use just one color and greatly simplify things. == Background colors Background colors are an important part of this problem. I do realise design considerations led to use different background colors in different parts of the WordPress admin. For example, the media views and the customizer made some autonomous design choices for their background colors. There are historical reasons for that. However, this led over time to a great inconsistency across the admin. For the greater good of maintenance, consistency, and simplification, I'd strongly suggest to start by exploring a way to drastically standardise the shades of grey used as background in WordPress. Ideally, there shouldn't be more than 3-4 shades of ""light"" grey used for the background. Some work in this regard was done in #35783 but there's still a lot of work to be done. == Note on accessibility standards for links According to [https://make.wordpress.org/core/handbook/best-practices/coding-standards/accessibility-coding-standards/#links-underline-or-no-underline the WordPress accessibility coding standards]: > When links can be identified as such by the context, for example because they're part of a menu, or a set of links clearly identified as user interface controls, they don't necessarily need to be underlined. In all the other cases, especially for links surrounded by other text (in a line or block of text), links need to be always underlined. " afercia Future Releases 24766 Title attributes galore. They serve no useful purpose. sabernhardt* Administration normal normal Future Release task (blessed) accepted 2013-07-16T00:29:25Z 2024-02-14T19:05:13Z "This is a full list of methods, including what files they're from, where HTML title attributes are in use. The title attribute provides a tooltip on certain browsers. Other than that, it is essentially useless. As provided in WordPress, the title attribute is both redundant and useless, because in most cases, it is a complete duplicate of the link's text. Therefore the tooltip provided is of no value whatsoever. For users of assistive technologies, the title attribute is useless at best and sometimes an annoyance. Users of text-to-speech software who have configured their software to do so will hear the title attribute twice. Essentially the extensive use of title attributes throughout WordPress Core amounts to unnecessary code bloat. I recommend eliminating the title attributes from all of the methods below: {{{ // user.php wp_authenticate_username_password() // post-template.php wp_page_menu() wp_get_attachment_link() // media.php get_image_tag() // media-template.php wp_print_media_templates() // link-template.php edit_term_link() edit_post_link() edit_comment_link() edit_bookmark_link() get_adjacent_post_rel_link() the_shortlink() // default-widgets.php widget() // comment-template.php comments_popup_link() comment_form() // class-wp-theme.php markup_header() // class-wp-editor.php wp_fullscreen_html(). There is one title attribute here on what I think is a TinyMCE button. If that looks like a button, it should actually be a button. // class-wp-customize-section.php render() // category-template.php get_category_parents() get_the_category_list() wp_generate_tag_cloud() start_el() // bookmark-template.php _walk_bookmarks() // author-template.php get_the_author_link() the_author_posts_link() wp_list_authors() // rss.php wp_rss() get_rss() // general-template.php get_calendar() // class-wp-admin-bar.php _render_item() }}} * Note: Ignored: All Third party classes " karlgroves Future Releases 51838 Add first-time user message to application passwords form describing what this form is Application Passwords 5.6 normal normal Future Release enhancement new 2020-11-20T18:20:10Z 2021-01-27T06:30:16Z "I think the application passwords form could use a first-time user message detailing what this feature is and what clicking ""Yes, I approve of this connection."" actually means. The form on its own is a bit short on messaging indicating what it actually is. I think for users bouncing over from a mobile app to this, it probably makes sense since the mobile app has the opportunity to provide the context that the app needs permission in order to work with your site. For someone looking to use social engineering to get users to give up app passwords, sending a user a phishing email with a link to this form and telling them they need to reconnect Jetpack (or insert trusted brand here) to access their account doesn't seem all that malicious. Jetpack users will already be familiar with a connection process and the messaging here is similar enough where it might not raise red flags when it should. With a full OAuth implementation we would see a list of permissions being granted to this application. Since that's not a part of this feature, full access is granted to the app in question. For administrators, that means the ability to create another admin account or change the password of the existing one which would effectively lead to site takeover. That isn't conveyed anywhere on this page. I think we just need to make users aware of the context in which they should've arrived on this page, and what level of access they are giving this application (and really the application here is a URL, the user needs to determine if they trust the URL). There's a WP pointer when you navigate to the plugin file editor that functions as a bit of a speedbump and also lets users know there's the potential to break things by using this feature. I think app passwords needs similar treatment." wfmatt Future Releases 51942 Application Password pagination Application Passwords 5.6 normal normal Awaiting Review enhancement new 2020-12-04T17:48:19Z 2021-02-01T14:11:15Z "Currently, the Application Password entries are stored on one page. Not sure how many entries are we expecting, but it might be worth using pagination here for better UX." Boniu91 Future Releases 40706 pasting text that has emojis into a new post breaks autosave and save draft Autosave 4.7.4 normal normal Awaiting Review defect (bug) new 2017-05-09T20:30:32Z 2017-05-09T20:35:10Z "When copying text that includes emoji's into the editor, then clicking save draft, the page refreshes and doesn't save any of the text in the editor. Copying initially from Google Docs with and without emojis. I haven't specifically limited it down to only Google Docs copying; i'm not a writer and i hate emojis so. Good luck on the bug hunt, but it's definitely a thing. " ryno267 Future Releases 44766 Microsoft-IIS/6.0 problem with wp_fix_server_vars Bootstrap/Load 4.9.8 normal major Awaiting Review defect (bug) new 2018-08-09T16:38:39Z 2018-08-09T16:38:39Z "The current function assumes problems that are fixed in many IIS versions nowadays and causes more problems. Currently, the function fails to detect mod_rewrite correctly in some instances and duplicates the query_string because it falls in the third condition on load.php:75 (duplication of the query string happens at load.php:90. Suggestion : just look in the already existing REQUEST_URI if the query string exists." davidwebca Future Releases 21573 NOBLOGREDIRECT interfering with 404 errors Bootstrap/Load 3.4.1 normal normal Future Release defect (bug) new 2012-08-14T07:32:06Z 2019-09-07T10:10:12Z When the `NOBLOGREDIRECT` constant is defined, 404 pages on the main site will not work and instead redirect to URL defined in `NOBLOGREDIRECT`. This is the cause of the `maybe_redirect_404` action/function, which is not needed and should be removed. bungeshea Future Releases 41578 Assure that $_SERVER['PATH_INFO'] is available Bootstrap/Load 4.8.1 normal normal Awaiting Review enhancement new 2017-08-07T00:27:14Z 2017-08-10T06:19:40Z "I use the [http://www.fefe.de/gatling/ gatling] web server on one of my servers (low ressorce consumption). gatling will not set the PATH_INFO environment variable if no path info is available which causes the home page of WP to enter an endless redirect loop. I managed to fix this by setting {{{$_SERVER['PATH_INFO']}}} to the empty string in an unhandled condition in wp-includes/load.php. " glehner Future Releases 54117 Changing memory limit descriptions Bootstrap/Load 5.8.1 normal minor Awaiting Review enhancement new 2021-09-13T11:22:55Z 2023-11-28T14:01:11Z "Hi, A couple of things that stand out, WP_MAX_MEMORY_LIMIT is for the admin side of the site and WP_MEMORY_LIMIT is for the visitor side. If these were updated in the next version to more friendly names like WP_VISITOR_MEMORY_LIMIT and WP_ADMIN_MEMORY_LIMIT, it would be easier to set up these limits. How is the memory limit decided for WordPress? I've overridden the defaults since my server has 1GB max memory for PHP, so I've set them to 512 and 1024 respectively but is there a reason why the memory limits are set to arbitrary figures and not a percentage of the limit?" fyremoon Future Releases 43712 Improve the user experience when a fatal error or uncaught exception occurs Bootstrap/Load normal normal Awaiting Review enhancement new 2018-04-06T14:43:43Z 2019-01-16T06:50:09Z "If a WordPress page request dies with a catchable fatal error or uncaught exception, WordPress just falls back on PHP's default error handling behavior. What this typically means is: * The page HTML gets cut off at a random point (wherever the error occurred), so the page looks broken but with no indication to the user that anything went wrong. * The request returns with a 200 status (which can result in the broken page being cached in all sorts of places). Proposed improvement: * Use set_error_handler() and set_exception_handler() early in the WordPress bootstrap process to give a better experience by default. For comparison, the way Drupal handles this is that it [https://api.drupal.org/api/drupal/includes%21theme.inc/function/theme_render_template/7.x buffers all output from the theme] (only actually printing it much later on in the page request). That way, if a fatal error or exception does occur, no output has been sent yet, so it can always [https://api.drupal.org/api/drupal/includes%21errors.inc/function/_drupal_log_error/7.x set a ""500 Service unavailable"" header and display a maintenance page instead]. There are pros and cons to that approach, but in any case, I'm not sure that WordPress could be changed to use it in a backwards-compatible way. However, what does seem possible to me is: * The error handler could check headers_sent() to see if output was already sent. * If no output was sent yet, just call wp_die() to display a standard error page with a 500 error. * If output already was sent, maybe at least try to print some kind of HTML before dying so the user can see that something is broken which wasn't their fault. I'm thinking something like an ""Oops - something went wrong and the page didn't finish loading"" message, ideally themed as a simple floating bar at the bottom of the browser window." David_Rothstein Future Releases 38650 Provide some guidance on what conditionals can/should be used in default-filters.php Bootstrap/Load low minor Awaiting Review enhancement new 2016-11-03T22:37:50Z 2017-06-21T23:12:12Z There are a lot of things you can't use in `default-filters.php`, such as `get_option()` or `is_customize_preview()`. Those deeply familiar with how load works might have some idea as to what's safe and what isn't, but it's generally confusing and a little opaque. I'd suggest some kind of inline comment at the top explaining the point of the file and what's generally safe (i.e. stuff in `load.php` as I understand?). helen Future Releases 54961 "Revise ""Technical Difficulties"" email to remove feature history and improve clarity of action steps" Bootstrap/Load 5.2 normal normal Future Release enhancement new 2022-01-27T21:25:05Z 2022-12-17T15:29:26Z "As someone who supports websites for numerous people and organizations, I've found that the ""Technical Difficulties"" email with recovery link is confusing to many people. I've had multiple people wonder if it's spam and many others be generally confused by it. I would suggest the following changes based on the feedback I have heard: - Change the first line to clearly indicate there is a potential problem with the website and drop the reference to WordPress 5.2. This is not important information anymore. - Move all technical information to the end of the email so as not to intimidate and confuse non-technical recipients - Be clear that there may or may not be an active problem. I will note that probably half of the emails I see sent are for temporary errors during updates that seem to have no lasting impact on the site. - Suggest people contact their website host -OR- developer (currently, only the host is mentioned) I have included a copy of the email for easy reference at the end of this issue. I'd be happy to work up the patch for this once a few other folks weigh in to either confirm or amend the suggestions I have. > Howdy! > > Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. > > In this case, WordPress caught an error with one of your plugins, Jetpack. > > First, visit your website ({url}) and check for any visible issues. Next, visit the page where the error was caught ({error path}) and check for any visible issues. > > Please contact your host for assistance with investigating this issue further. > > If your site appears broken and you can't access your dashboard normally, WordPress now has a special ""recovery mode"". This lets you safely login to your dashboard and investigate further. > > {recovery mode link} > > To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires. > > When seeking help with this issue, you may be asked for some of the following information: > WordPress version > Current theme: > Current plugin: > PHP version > > > > Error Details > =============" mrwweb Future Releases 42264 Systematic way of dealing with compat code and polyfills Bootstrap/Load normal normal Awaiting Review enhancement new 2017-10-18T21:14:14Z 2018-05-23T10:31:48Z "The way compatibility code and fallback/polyfill functionality is currently handled has a few issues: * As everything resides in one big file, all of the code is parsed every time. * As everything resides in one file, problems like the PHP 7.2 parsing error for the autoload polyfill can crop up (as the polyfill is written with now deprecated code). * If the requirements change, it is non-trivial to remove unneeded code again. I'd like the suggest a more systematic way of loading the compatibility layer. The basic premise is that the PHP version of the current server is detected, and then an individual compatibility file is loaded for each version that is not already supported by the server. This provides a clean way of structuring the compatibility layer, giving a good overview of what is needed when, and what can be discarded. It also only loads the code that is needed. Here's the main mechanism that would make this work: {{{#!php public_query_vars` fails. I have attached a simple plugin that illustrates the problem. Steps to reproduce: 1. Download the plugin. 2. Run `phpunit` inside of it. 3. Test #1 succeeds while test #2 fails. The relevant excerpts from the plugin are included below. Endpoint registration: {{{ add_action( 'init', function() { add_rewrite_endpoint( 'custom-endpoint', EP_ROOT ); add_rewrite_endpoint( 'custom-endpoint-2', EP_ROOT ); }); }}} Tests: {{{ class TestRewriteEndpoint extends WP_UnitTestCase { public function setUp() { parent::setUp(); $this->set_permalink_structure( '/%year%/%monthnum%/%day%/%postname%/' ); $this->qvs = $GLOBALS['wp']->public_query_vars; // print_r( $this->qvs ); } public function tearDown() { $GLOBALS['wp']->public_query_vars = $this->qvs; parent::tearDown(); } public function test_is_custom_endpoint_added() { $this->assertContains( 'custom-endpoint', $GLOBALS['wp']->public_query_vars ); } public function test_is_custom_endpoint_2_added() { $this->assertContains( 'custom-endpoint-2', $GLOBALS['wp']->public_query_vars ); } } }}} This may possibly be related to #34346, though in this case I am not using `go_to()`." ericdaams Future Releases 59981 PHPUnit tests for is_main_network Build/Test Tools normal normal Awaiting Review defect (bug) new 2023-11-28T23:34:10Z 2024-02-27T18:45:47Z pbearne Future Releases 56615 Running `build` scripts on Windows machines produces different results gziolo Build/Test Tools 6.1 normal normal 6.6 defect (bug) reopened 2022-09-21T14:21:34Z 2024-02-20T09:48:20Z "When running `npm run build:dev` on a Windows machine, the hashes calculated by Webpack are different and not as expected. This seems to be related to an encoding issue with how the `remove-accents` dependency is read and compiled. Slack discussion thread: https://wordpress.slack.com/archives/C02RQBWTW/p1663687669117549?thread_ts=1663687642.461539&cid=C02RQBWTW" desrosj Future Releases 53781 Tests_Embed_Template tests fail when run in isolation Build/Test Tools normal minor Awaiting Review defect (bug) new 2021-07-26T10:25:19Z 2021-09-28T03:32:26Z "When running the `Tests_Embed_Template` test in isolation, two of the tests fail. {{{ phpunit --filter Tests_Embed_Template }}} {{{ #) Tests_Embed_Template::test_oembed_output_post_with_thumbnail DOMDocument::loadHTML(): AttValue: "" expected in Entity, line: 10 path/to/wp/tests/phpunit/tests/oembed/template.php:66 #) Tests_Embed_Template::test_oembed_output_attachment DOMDocument::loadHTML(): AttValue: "" expected in Entity, line: 10 path/to/wp/tests/phpunit/tests/oembed/template.php:110 }}} Accidentally discovered when I added the `import` group to the `` `` and ran the complete test suite and those two tests - which are unrelated to the `import` tests - started erroring out. A tentative conclusion from that can be that: 1. The `Tests_Embed_Template` tests have an undeclared dependency on the tests in the `import` group. 2. The `Tests_Embed_Template` tests only pass by accident due to the **''order''** in which the tests are run, which is not guaranteed and can be influenced in more recent PHPUnit versions, so cannot be relied upon. Also see: https://phpunit.readthedocs.io/en/stable/configuration.html#the-executionorder-attribute This needs further investigation. Solution direction: The test should be made independent of the `import` tests. Originally reported in https://core.trac.wordpress.org/ticket/53363#comment:39" jrf Future Releases 45088 Update package-lock.json for Mac, Linux, and Windows cross-platform compatibility Build/Test Tools normal minor Future Release defect (bug) new 2018-10-12T11:53:43Z 2018-10-29T12:07:42Z "Doing a ""clean"" `npm install` after #45064 on Windows 10 changed the package-lock.json a bit, adding a few `""optional"": true`. " azaozz Future Releases 31092 travis-ci builds skip lots of tests due to environment configuration Build/Test Tools normal normal Future Release defect (bug) new 2015-01-21T19:20:30Z 2020-11-09T19:36:28Z "See #30284. travis-ci builds (eg https://travis-ci.org/aaronjorbin/develop.wordpress/jobs/47713725) are skipping a bunch of tests. I haven't yet looked into it in detail, but I'm guessing it's a combination of the following: - Missing image-related PHP extensions (gd, exif) - ru_RU system domain must be installed (`Tests_DB::test_locale_floats()`) - MySQL versions don't support utf8mb4 - WordPress Importer plugin not available Ideally, the only tests skipped in CI are those that depend on *WordPress* configurations, and we run separate builds for each relevant config. In the case of our current tests, the only WP config that matters is multisite, and we're already running separate multisite tests, so we should expect to see that some tests are skipped on MS, and others skipped on non-MS. All OS, PHP, MySQL, and webserver-related skips should be eliminated. Anyone who's interested in chasing this down, here's how I'd go about it: - Fork https://github.com/aaronjorbin/develop.wordpress and set it up to run on Travis. - Modify the build so that it runs `phpunit -v`. I think you should be able to do just by changing the `script` command in .travis.yml - Check in and push up. The first Travis run should give you a full report of what's being skipped, and why - Start hacking at the `before_script` section as necessary to get the necessary prerequisites installed. http://docs.travis-ci.com/user/languages/php/#PHP-installation and the following sections should be a good starting point." boonebgorges Future Releases 42064 wp_crop_image() does not work when fopen() is disabled Build/Test Tools 4.9 normal normal Awaiting Review defect (bug) new 2017-10-02T19:10:07Z 2021-08-11T21:01:03Z "While running the WordPress PHP Unit testing framework, a single test for wp_crop_image() failed consistently. After @danielbachhuber debugged the test, he found that wp_crop_image() was failing because it depended on _load_image_to_edit_path, which he said is dependent on fopen(). WordPress is supposed to function when fopen() is disabled. wp_crop_image's dependency on fopen is incorrect. To reproduce the issue: Disable allow_url_fopen in PHP Setup the PHPUnit Test Runner (https://github.com/WordPress/phpunit-test-runner) Run the PHPUnit Test Runner. The test runner should report the following failed test: Tests_Image_Functions::test_wp_crop_image_url Failed asserting that WP_Error Object (...) is not an instance of class ""WP_Error"". /../../../phpunit-test-runner/wp-test-runner/tests/phpunit/tests/image/functions.php:317 The WP_Error object reports the following: Fobject(WP_Error)#9993 (2) { [""errors""]=> array(1) { [""invalid_image""]=> array(1) { [0]=> string(21) ""File is not an image."" } } [""error_data""]=> array(1) { [""invalid_image""]=> string(60) ""https://asdftestblog1.files.wordpress.com/2008/04/canola.jpg"" } } The image is a valid image otherwise, such as when viewed through the browser. The test fails on PHP 5.6, PHP 7.0, and PHP 7.1 when fopen is disabled." jadonn Future Releases 34693 Add browser-based testing and automated acceptance tests (BrowserStack) Build/Test Tools normal normal Future Release enhancement assigned 2015-11-15T23:43:07Z 2020-09-15T01:55:03Z "Automated testing in WordPress is primarily focused on PHPUnit testing, with some JavaScript QUnit tests. While the PHP tests are run against every version of PHP since 5.2, the JavaScript tests are limited to one single browser environment (PhantomJS). This has meant that browser-specific bugs have been introduced (e.g. #30781) because manual testing isn't always performed in all the browsers that WordPress supports. We should connect WordPress unit tests with something like BrowserStack to run the QUnit tests in the various browsers. While we're at it, the unit/integration testing in PHPUnit and QUnit only take us so far in WordPress as it is. What WordPress is missing are acceptance tests that fire up an actual browser to do actual tasks that users would perform when using WordPress. Such acceptance tests would make WordPress much more resilient against regressions, and it would open up a lot of new areas for automated testing that are currently very difficult to test using unit/integration tests. For instance, the Customizer heavily uses data from both PHP and JavaScript along with Ajax requests between the two. To create unit/integration testing mocks for PHP, JS, and Ajax requests adds a lot of testing overhead and is also difficult to maintain. I believe acceptance testing would allow much more of WordPress to be tested automatically, and it would allow tests to be written by more people. See also https://wordpress.slack.com/archives/core/p1419407324003594" westonruter Future Releases 35318 Automate anti-virus scanning of WordPress zips Build/Test Tools normal normal Awaiting Review enhancement new 2016-01-05T16:36:15Z 2022-01-29T10:48:46Z "In WordPress 4.4, some files were marked as malware by antivirus vendors. This sucks for users. I think we should automate scanning of WordPress packages so that we can alert antivirus vendors as soon as possible that they are miss flagging WordPress files. one api that could work is https://www.virustotal.com/en/documentation/public-api/ , but we should investigate that and other possible options. " jorbin Future Releases 37261 Consider removing the `$start` argument from `WP_UnitTest_Generator_Sequence` Build/Test Tools 4.4 normal normal Awaiting Review enhancement new 2016-07-03T12:46:17Z 2019-02-25T01:46:45Z "As a follow up to [35244] and [37299], I wonder whether the `$start` argument in `WP_UnitTest_Generator_Sequence` still makes sense. Currently the class handles two things: - Global increments (via the static incrementor variable). - Local increments (via the `$start` argument). So I'd propose to remove the `$start` argument. A different, simpler class could be used for local increments instead." Frank Klein Future Releases 54154 Core medias e2e tests Build/Test Tools normal normal Future Release enhancement new 2021-09-21T12:17:40Z 2022-09-02T15:17:22Z "This ticket is a sub ticket of #52895. Here is an overview of e2e tests that are already implemented and those that need implementation in Core: https://docs.google.com/spreadsheets/d/1QTlGV3WYmRZKhtqzUasbv_XELFCwu1su7c4qe-SePMY/edit#gid=0. And here are the tests scenarios I drafted: https://docs.google.com/document/d/1HvZCiCBvRRU978NX6wbP4JrMu5f1-OPjYVTgjkV5CCo/edit?usp=sharing --------------------------------------------------------------------------------------- This ticket is for medias e2e tests." justinahinon Future Releases 54157 Core menus e2e tests Build/Test Tools normal normal Future Release enhancement new 2021-09-21T13:03:13Z 2022-09-02T15:17:39Z "This ticket is a sub ticket of #52895. Here is an overview of e2e tests that are already implemented and those that need implementation in Core: https://docs.google.com/spreadsheets/d/1QTlGV3WYmRZKhtqzUasbv_XELFCwu1su7c4qe-SePMY/edit#gid=0. And here are the tests scenarios I drafted: https://docs.google.com/document/d/1HvZCiCBvRRU978NX6wbP4JrMu5f1-OPjYVTgjkV5CCo/edit?usp=sharing --------------------------------------------------------------------------------------- This ticket is for menus e2e tests." justinahinon Future Releases 54156 Core widgets e2e tests Build/Test Tools normal normal Future Release enhancement new 2021-09-21T12:49:40Z 2022-09-02T15:17:31Z "This ticket is a sub ticket of #52895. Here is an overview of e2e tests that are already implemented and those that need implementation in Core: https://docs.google.com/spreadsheets/d/1QTlGV3WYmRZKhtqzUasbv_XELFCwu1su7c4qe-SePMY/edit#gid=0. And here are the tests scenarios I drafted: https://docs.google.com/document/d/1HvZCiCBvRRU978NX6wbP4JrMu5f1-OPjYVTgjkV5CCo/edit?usp=sharing --------------------------------------------------------------------------------------- This ticket is for widgets e2e tests." justinahinon Future Releases 53737 Create a way to autogenerate end-to-end test code from manual testing steps for WordPress core lucatume Build/Test Tools normal normal Future Release enhancement assigned 2021-07-22T12:17:32Z 2022-07-05T16:41:26Z "As part of the proposal to [https://make.wordpress.org/core/2020/08/07/e2e-end-to-end-testing-in-core-working-group-proposal/ bring end-to-end (e2e) testing to WordPress core], we would like to find a way to autogenerate end-to-end tests from manual testing steps. WordPress uses the [https://jestjs.io/ Jest] test framework for its e2e tests. Jest uses JavaScript code to create tests. Like most testing frameworks, it's built for developers who code the tests to be run on the front end, typically via a decoupled browser instance. However, this means that only those familiar with writing JavaScript code would be able to create new or edit existing tests. This creates a barrier to entry for those who would like to contribute to testing efforts but are not coders. Traditionally performing front-end testing would have been done by contributors following a manual process (i.e., physically filling in fields, clicking on buttons, etc.). Therefore, it would make sense to find a way to continue to allow these testers to contribute to the e2e test suite. We would like to find a way to autogenerate e2e tests, to somehow record and save the process of manual testing and convert that into JavaScript code that is compatible with the Jest framework. This initiative aims to empower any contributor to contribute to the e2e testing efforts without knowing how to code an automated test." psykro Future Releases 45132 Explore better implementation of Autosaves Controller unit tests Build/Test Tools normal normal Future Release enhancement new 2018-10-19T13:55:25Z 2019-02-14T18:07:09Z "In [43768], we had to introduce an edge case where `tests/rest-api/rest-autosaves-controller.php` is run last in the test suite because the definition of `DOING_AUTOSAVE` pollutes the test suite. We can't remove `DOING_AUTOSAVE`, but we could potentially avoid defining it during a test suite run. Or maybe there are other ideas we can explore. ""Done"" for this issue would be a solution where `tests/rest-api/rest-autosaves-controller.php` can be tested as a part of the standard test suite execution order, not last." danielbachhuber Future Releases 29792 Grunt: Add a stylelint precommit task to check for CSS syntax errors netweb Build/Test Tools normal normal Future Release enhancement assigned 2014-09-29T13:07:40Z 2021-11-11T21:59:32Z "We need to do a better job of catching sad syntax errors and problems in our CSS before commit - things like parse errors, empty rules, units on zero values, and possibly duplicate properties (when alone, not as a part of a group). There may also be a thing or two that we could enforce per our own standards, such as requiring a comment to follow any declaration with `!important`. CSSLint seems to do most of these, provided we turn off the majority of its checks. Many of those checks (vendor prefixes, selector specificity, etc.) either are not relevant to our set up (due to Autoprefixer, for example) or are just not feasible given our current CSS and possibly not desirable for this project. Interested to know if there are any other tools out there that perhaps fit the job better, and defining the parameters of what we would like to check." helen Future Releases 40281 Improve Documentation for HTTP Unit Testing Build/Test Tools 4.8 normal normal Awaiting Review enhancement reopened 2017-03-27T22:42:10Z 2021-11-16T18:39:48Z Improve Commenting for HTTP Unit Testing. bhubbard Future Releases 37521 Introduce a procedure for deprecating code used in Unit Tests Build/Test Tools 4.6 normal normal Awaiting Review enhancement new 2016-07-30T08:22:16Z 2019-02-25T01:47:03Z "WordPress has different utility functions to mark functions, methods, hooks, etc. in the core codebase as deprecated, and a dedicated file (`deprecated.php`) to move obsolete code to. I consider that it would be useful to introduce the approach of deprecating code to the unit tests as well. An example for obsolete code would be the `_unregister_post_type()` and `_unregister_taxonomy()` functions in the unit test utils. Since [36316], these test framework functions are only wrappers for core functions. As such, it would be appropriate to use the core functions in the tests, and deprecate the test framework functions. Let's explore how we could handle this in the unit test framework." Frank Klein Future Releases 59486 Make test suite compatible with PHPUnit 10 / 11 Build/Test Tools 6.4 normal normal Future Release enhancement new 2023-09-28T08:58:42Z 2024-03-07T09:58:11Z "PHPUnit 10 was released back in February of 2023, and included [https://github.com/sebastianbergmann/phpunit/blob/10.0.0/ChangeLog-10.0.md#1000---2023-02-03 many breaking changes] - they completely rewrote the internal functionality of PHPUnit (mainly the event system for extending the test runner). Besides that, they upped the minimum PHP version to >=8.1, so for WordPress, it could only be used on PHP versions of >=8.1. While this is not a huge and critical update, since the tests are running fine on PHP versions all the way up to version 8.3, it would be a good idea to start preparing for PHPUnit 10 compatibility. Besides being up to date, it will allow external testing library maintainers (such as [https://github.com/lucatume/wp-browser wp-browser] or [https://github.com/dingo-d/wp-pest wp-pest]), to use the latest versions of both PHPUnit, or dependencies that are using PHPUnit 10 (such as PestPHP v2 which depends on PHPUnit 10). I understand that this is a huge undertaking, but it's okay to have a ticket open for this (I didn't find one opened while searching, could be wrong tho), so that we can keep track of changes, and maybe create a roadmap or a to-do list of what needs to be fixed in order to make WordPress test suite compatible with PHPUnit 10. " dingo_d Future Releases 42668 Remove WordPress Importer tests from default test suite Build/Test Tools normal normal Awaiting Review enhancement new 2017-11-23T08:28:49Z 2017-11-29T23:59:39Z "The importers were removed from Core in r14764, 8 years ago. But the [https://core.trac.wordpress.org/browser/trunk/tests/phpunit/tests/import tests] are still located in the core test suite, and are run by default. We should exclude these tests from running by default as a first step, as it means running 14 tests less. Ultimately these tests should be migrated to the [https://github.com/WordPress/wordpress-importer Importer plugin repository], where they can assist with development." Frank Klein Future Releases 50209 Remove all uploads between test methods Build/Test Tools 4.0 normal normal Awaiting Review enhancement new 2020-05-19T11:09:00Z 2020-05-21T08:13:10Z "Commit r29120 added a curious feature to the WordPress testing framework: selective uploads deletion between test runs. What it means is that the first time that `WP_UnitTestCase::setUp()` is called for a test case, it will create a list of all files contained in the uploads directory. This list, stored in the static `$ignore_files` property, allows to selectively delete files uploaded during tests. This code was added so that tests can be run against a development installation of WordPress. In opposition to running tests against a throwaway installation, as should be the case. There are three issues with this behavior: 1. Scanning the uploads directory is slow. If you have too many files in that directory, the test runner will ""hang"" before running the first test. Ultimately it will result in a memory exhaustion error. 2. Attachments are not properly deleted. `_delete_all_data()` runs a SQL query that deletes the database entries of attachments, but not the associated files. Since the function is called before `wpTearDownAfterClass` runs, there's no way to do manual cleanups in tests. The next test case that gets booted up will add the remaining files to the list of files to ignore, making it impossible to do selective uploads deletion. See #41978. 3. There is no automatic clean up of uploads between test methods or test cases, leaving files lingering around. Even after all tests have been run. In short this approach is slow, half-baked, and unneeded. We should therefore remove it, and have uploads be cleared the same as any other fixture. Since this behaviour has been around for years now, we can't unfortunately just remove it, so I propose that we use a feature flag for disabling it." Frank Klein Future Releases 54537 Tests: Enable PHP version check once PHP 8.0 compatibility is achieved. Build/Test Tools 5.9 normal normal Future Release enhancement new 2021-11-29T21:24:57Z 2023-04-06T12:39:27Z "A test checking if the current recommended PHP version is actively supported was temporarily disabled in [52260]. This should be enabled once PHP 8.0 compatibility is achieved. Related: #54528" Hareesh Pillai Future Releases 41781 do not forcefully phpunit delete fixtures data Build/Test Tools 4.8.1 normal normal Awaiting Review enhancement new 2017-09-02T02:06:22Z 2017-09-02T02:06:22Z "When phpunit runs, there are at least three places where test-data are removed (see below). Fixture deletion is good in its principle. But it's also sometimes painful, especially when one is in the process of developing tests and need to run the testsuite many times. WP (re)installation + shared XML fixture loading could easily be '''very''' slow (especially given XML importer slowness). If your plugin's testsuite does not even contains destructive operations (or controlled destructions) then all that time spent in testsuite (re)installation is very frustrating. (In my case it's 1 minutes 50 versus 2 seconds) It would be good if developers could control whether or not fixtures are deleted & database cleaned, when phpunit starts/finishes. Places that need change: * [https://github.com/WordPress/wordpress-develop/blob/ce8a915/tests/phpunit/includes/bootstrap.php#L68 system( WP_PHP_BINARY ... install.php)] * [https://github.com/WordPress/wordpress-develop/blob/ce8a915/tests/phpunit/includes/bootstrap.php#L101 _delete_all_posts()] There is also: [https://github.com/WordPress/wordpress-develop/blob/ce8a91/tests/phpunit/includes/testcase.php#L83 _delete_all_data() inside tearDownAfterClass()] but this one can be easily overriden. Could a couple of filter/action/define/whatever could be made so that data cleanup, being the default, could be disabled if developer wants to? thx" drzraf Future Releases 39159 Add APC to automated test matrix Build/Test Tools normal normal Awaiting Review feature request new 2016-12-07T19:58:12Z 2020-11-09T19:50:50Z We already have a test run using memcache, but APC is different and @jaquith's object cache drop-in is heavily used enough that it makes sense to also run the automated tests using it. Inspired by #39132 jorbin Future Releases 55429 Coding Standard: Use spaces for JSON instead of tabs Build/Test Tools normal normal Awaiting Review feature request new 2022-03-21T09:15:09Z 2022-03-21T12:22:30Z "When PHP outputs JSON using `json_encode`, there's no option to output it with tabs instead of spaces. This is particularly relevant in since https://github.com/WordPress/gutenberg/pull/39048 merged - we now convert theme.json files that were using tabs to spaces. We could use a regex to convert these spaces back to tabs, but maybe its simpler to default to spaces for JSON files since that is the format that PHP uses. Opening this ticket to start the discussion..." scruffian Future Releases 30017 Many automated tests are unnecessarily slow wonderboymusic Build/Test Tools normal normal Future Release task (blessed) assigned 2014-10-17T02:07:19Z 2021-03-24T14:47:08Z "Our test suite is getting bigger (that's good!). But many of our tests are, of necessity, integration and functional tests that require lots of setup: creating factory data, resetting globals, etc. This process can be slow (that's bad!). Poking around in the tests, it looks like some of the worst offenders are those who create lots of database content in the `setUp()` method. Creating more dummy data than is absolutely necessary to test an assertion is - at best - wasteful. At worst, it actually introduces unnecessary variables into what is supposed to be a narrowly defined test. (Fake but illustrative example: if you create 25 posts to test some default value in `WP_Query`, you now have to worry about pagination in addition to whatever value you're testing.) Changing existing tests is a tedious and potentially dangerous task - you don't want to introduce regressions into our regression-preventing tests. But if we can shave 10-20% off of the execution time of our suite (which I think is a pretty conservative estimate), it'd be a huge step toward getting more people to actually run the dang things, as well as things like continuous integration. Opening this ticket for discussion and/or patches." boonebgorges Future Releases 50182 Majority of bundled themes have broken mobile nav menus when JS turned off Bundled Theme normal normal Future Release defect (bug) new 2020-05-15T22:59:57Z 2020-05-30T09:55:59Z "I tried turning off JavaScript in my browser (via DevTools in Chrome) and then activated each core theme to see if I could access mobile nav menu items. Unfortunately, for the themes which have an expandable mobile nav menu, the majority fail to gracefully degrade when JavaScript is disabled (either on purpose or the script fails to load over the network). Themes which gracefully degrade by just revealing all the nav menu items: * Twenty Nineteen * Twenty Seventeen * Twenty Sixteen Themes which show a mobile nav menu button which does nothing when tapped: * Twenty Twenty (mobile search also broken) * Twenty Fifteen * Twenty Fourteen (mobile search also broken) * Twenty Thirteen * Twenty Twelve" westonruter Future Releases 44656 Multiple themes: Empty site title leaves empty anchor tag in header Bundled Theme normal normal Future Release defect (bug) new 2018-07-27T15:53:04Z 2023-06-09T23:51:09Z "I just noticed something weird the other day with Twenty Twelve. I removed the title all together (no I did not hide it) and when I looked at the source code this is what I saw: {{{

}}} It's an H1 tag with an empty anchor? This shouldn't happen I don't think. So I download a few other themes and did the same thing and sure enough all that was left was an empty H1 tag with an empty anchor tag. I do not know why anyone would want to do this **BUT** If the site title is removed completely, meaning not hidden and not entered not entered either in ""**Settings**"" or ""**Site Identity**"" in the customizer, then the site H1 site title tag should not be displayed. I am not sure if this is a bug so I thought I would enter it in. I looked all over and could not find any information or any other tickets regarding this. I apologize if its a waste of time. Thanks in advance." tsquez Future Releases 60298 Text embedded in theme template is not translatable audrasjb Bundled Theme normal normal 6.6 defect (bug) reopened 2024-01-19T14:42:50Z 2024-02-21T13:06:41Z "Related to an issue reported on Gutenberg: https://github.com/WordPress/gutenberg/issues/55983 Default block themes embed some text inside the template as content or attributes. However, template files are HTML files and cannot use PHP translation functions like pattern files. As a result, English will always be displayed, even if the user changes the site language. As far as I've researched, the following passages are untranslatable text. == Twenty Twenty-Three - `Newer Posts`: - [https://core.trac.wordpress.org/browser/tags/6.4.2/src/wp-content/themes/twentytwentythree/templates/archive.html#L21 archive.html, line 21] - [https://core.trac.wordpress.org/browser/tags/6.4.2/src/wp-content/themes/twentytwentythree/templates/home.html#L23 home.html, line 23] - [https://core.trac.wordpress.org/browser/tags/6.4.2/src/wp-content/themes/twentytwentythree/templates/search.html#L21 search.html, line 21] - `Older Posts`: - [https://core.trac.wordpress.org/browser/tags/6.4.2/src/wp-content/themes/twentytwentythree/templates/archive.html#L22 archive.html, line 22] - [https://core.trac.wordpress.org/browser/tags/6.4.2/src/wp-content/themes/twentytwentythree/templates/home.html#L24 home.html, line 24] - [https://core.trac.wordpress.org/browser/tags/6.4.2/src/wp-content/themes/twentytwentythree/templates/search.html#L22 search.html, line 22] - `Mindblown: a blog about philosophy.`: [https://core.trac.wordpress.org/browser/tags/6.4.2/src/wp-content/themes/twentytwentythree/templates/home.html#L6 home.html, line 6] == Twenty Twenty-Four - `Posts`: [https://core.trac.wordpress.org/browser/tags/6.4.2/src/wp-content/themes/twentytwentyfour/templates/index.html#L6 index.html, line 6]" wildworks Future Releases 53021 Twenty Eleven: Button Block alignment Bundled Theme normal normal Awaiting Review defect (bug) new 2021-04-12T11:02:00Z 2021-04-28T14:59:04Z "When adding a Button Block to a page or post with the theme Twenty Eleven, the center alignment is incorrect. Steps to replicate: 1. Add Button Block to post 2. Align Button Block to be centered 3. view on desktop or mobile and you will see the button is not aligned centered, but more to the right. Screenshot: https://d.pr/i/N5mZx6 I was also able to replicate the same issue on the theme Twenty Twelve" spanglishwebs Future Releases 46802 Twenty Eleven: Dark Mode Featured Post gradient overlay is overlapping ianbelanger Bundled Theme normal normal Future Release defect (bug) assigned 2019-04-04T18:48:57Z 2019-04-04T19:59:12Z While reviewing #46770 @desrosj noticed that the gradient overlay on `.featured-post .feature-image.small:after` is 10px lower than it should be while in the `Dark Color Scheme`. It becomes very noticeable due to the fact that the background it overlaps is a dark grey, while the gradient overlay is black. See screenshot ianbelanger Future Releases 38982 Twenty Eleven: Navigation dropdown menus broken on android devices Bundled Theme 4.6.1 lowest normal Future Release defect (bug) new 2016-11-29T17:50:49Z 2019-04-09T23:56:24Z "On a site running Twenty Eleven, tapping the top level menu item opens that page, rather than opening that item's child menu items and waiting for something to be selected. This results in the child menu opening briefly, but being lost on the page load. Issue isn't present on iOS or desktop devices, but I was able to reproduce in both Chrome and Firefox on an HTC M9 running android 6.0. Originally reported here: https://en.forums.wordpress.com/topic/problem-with-drop-down-menu-when-using-2011-theme-on-mobile?replies=3 The issue happens on both of the sites mentioned, the self hosted and the one on WordPress.com." shireling Future Releases 55063 Twenty Eleven: Quote block italic styling works in reverse Bundled Theme 5.9 normal normal Future Release defect (bug) new 2022-02-03T15:34:47Z 2022-02-03T16:51:04Z "Hey! I've been browsing through the trac for this issue, but I wasn't able to locate it. Here are the steps to replicate the issue: 1. Activate Twenty Eleven theme 2. Create a new page and add a Quote block 3. Write some text. You'll notice the quote text is italic by default 4. Try to make the text italic through the editor and save the changes. The output should make the text non-italic, even though it'll appear as italic in the editor. I tested this with the latest version of Gutenberg(12.5.0) and WordPress 5.9 " robertghetau Future Releases 30686 Twenty Fourteen/Thirteen/Twelve Navbar submenu behaviour Bundled Theme 4.0.1 normal normal Awaiting Review defect (bug) assigned 2014-12-12T08:11:58Z 2024-03-07T05:22:09Z "As you all may know, both 2014/13/12 themes require you to hover over a menu item in order to access the submenu item. This isn't a problem for desktops but for touchscreen devices this may pose a problem. I notice this problem has largely been addressed at least for the 2013 and 2012 themes for Android, iOS and Windows Phone devices (see https://core.trac.wordpress.org/ticket/24767#comment:35). However, on my Windows 8 tablet, it still registers the first tap as a click on both Internet Explorer 11 and Mozilla Firefox (Google Chrome works fine). I believe both browsers somehow do not declare whether the device is a touchscreen. In addition, for the 2014 theme, the (partial) fix isn't even implemented (I don't know how it got implemented for both 2013 and 2012 themes but was overlooked for 2014), therefore you will still find it hard to click on sub-menus if you're using an Android device. As for the 2013 and 2012 themes, I know that the Windows 8 tablet userbase is comparatively small, but I believe it will grow over the years. I'm not sure how this can be fixed in the mean time (since the hover/click behaviour seems to rely on a touchscreen detection), but I would like to suggest the following: - In the Twenty Fifteen theme, this issue seems to be fixed once and for all, as the dropbox arrow next to the menu item is a separate link. Clicking on the arrow itself will maximise/minimise the sub-menu, instead of linking you to the menu item itself. - However, the Twenty Fifteen theme's menu is only available at the side, instead of the top. - Thus, if the improvements made in the Twenty Fifteen theme could be backported to Fourteen, Thirteen and Twelve. It would be great! P.S. I'm not sure what to classify this ticket under, but I guess I will leave it as a 'bug' since the hover and click issues have not been completely addressed, especially on the Twenty Fourteen theme. The same behaviour occurs on WordPress 4.0.1 and 4.1 RC." trenzterra Future Releases 26723 Twenty Fourteen: Hatom Errors Bundled Theme 3.8 low normal Future Release defect (bug) reopened 2013-12-26T14:50:13Z 2022-07-08T17:17:26Z "Greetings. Getting this on Google's Structured Data Testing tool. Extracted structured data hatom-feed hatom-entry: Error: At least one field must be set for HatomEntry. Error: Missing required field ""entry-title"". Error: Missing required field ""updated"". Error: Missing required hCard ""author"". The 1st two are caused by using WordPress with a static home page, this started with the 3.8 release. I am using a theme designed in Artisteer that worked fine before the 3.8 release. Artisteer is no help pointing the finger at WordPress. Activating WP 2014 theme solves the 1st 2 errors but the below still shows. Error: Missing required field ""updated"". Error: Missing required hCard ""author"". The second two have been present showing as ""Warnings"" in self hosted WordPress sites for a long time. However since a recent Google algorithm chance those warnings are now Errors. An announcement from Google. http://googlewebmastercentral.blogspot.com/2013/12/structured-data-dashboard-new-markup_12.html Below is a screen shot of one of my sites Google webmaster tools accounts. http://www.doc1952.com/hatom-errors.jpg All of my sites structured data thumbnails have disappeared from search results. I have posted about this situation in the WordPress forums with no help so far. http://wordpress.org/support/topic/google-structured-data-missing-required-field-authorship-thumbnails-gone?replies=10 Thanks for your help with this. Ed Koon www.doc2014.com " fidosysop Future Releases 42043 Twenty Fourteen: Menu problems on iPad Air 2 Bundled Theme normal normal Future Release defect (bug) new 2017-09-30T18:15:32Z 2021-09-09T14:02:31Z "When viewing a Twenty Fourteen (2014)-themed blog on an iPad air 2 in landscape alignment it is impossible to access submenu items. Either the arrow to expand the submenu has to be separate so it can be activated without also activating the menu or the menu should be displayed as a compact menu (three bars that expand, like on a mobile or in portrait alignment). Hovering isn't really an option on an iPad. At first glance it seems there are many bugs opened for menus, but none for the 2014-theme. An example of this behavior can be found at https://talkwards.wordpress.com/ (at least for now... it should be repeatable with any blog that has a menu with subitems though). This behavior exists on Wordpress.com. I'm assuming they're using the latest version of Wordpress..." erikalm Future Releases 42035 Twenty Fourteen: Non-Responsive Sub-Menus on iPad Pro in Horizontal View Bundled Theme 4.8.2 normal normal Awaiting Review defect (bug) new 2017-09-29T17:00:29Z 2018-08-11T11:54:36Z "It seems that the sub-menu items are not responsive and do not work on some devices such as iPad Pro in the theme Twenty Fourteen when the device is in the horizontal view. '''The steps to reproduce: ''' - activate the theme Twenty Fourteen; - create a menu with sub-menu items in the Appearance - Customize; - select the display location for the menu to be ""Top Primary Menu""; - save and publish your settings; - go to your site on iPad Pro and try clicking on the menu to make a sub-menu appear in the - horizontal view. '''What I expected:''' the sub-menu items to appear '''What happened:''' the sub-menus did not appear and were not responsive '''Further details:''' I tested on iPad Pro and iPad 4; the issue seems to be happening on iPad Pro specifically - I suspect because it has a desktop view in the horizontal position where you can see all of the items. On iPad 4, the menu is a hamburger menu, and once you click to open it, all menu items are visible. " katinthehatsite Future Releases 59529 Twenty Fourteen: Search bar showing on different line on iPadOS 17 Bundled Theme normal major Awaiting Review defect (bug) new 2023-10-04T01:38:45Z 2023-10-18T14:55:52Z "The search toggle element doesn't show on the same level as the menu for iPadOS 17 devices — that is both when checking on Chrome and Safari. 1. Get a device with iPadOS 16 and reproduce it showing as expected: https://wp-themes.com/twentyfourteen/ 2. Update to iPadOS 17 and see the issue with the search on Safari or Chrome PS: I'm considering this major severity as the issue is on an important part of a default theme — even if it's an old theme and we can only reproduce on IOS 17 devices. Originally reported by @fgruen here: https://wordpress.org/support/topic/display-problem-with-search-box-on-apple-ipad/?view=all" foosantos Future Releases 59164 Twenty Nineteen : Site Title Block Color Section is not reflecting properly in Editor & Frontend Side Bundled Theme normal normal Awaiting Review defect (bug) new 2023-08-22T12:42:49Z 2023-08-24T04:40:34Z "In Twenty Nineteen theme, 1. The colour selected is not reflected on the frontend side 2. When we select the background then the colour is not reflected in the editor also. Video of the issue generated : https://drive.google.com/file/d/1dv9C0hRltm6bLbmfvw53sSEFj5Zz_lw0/view?usp=sharing" pitamdey Future Releases 47051 Twenty Nineteen theme sub-menu returns error in WAVE accessibility tool nataliemac Bundled Theme 5.0 normal normal Future Release defect (bug) assigned 2019-04-26T16:21:38Z 2019-11-03T21:23:14Z "I'm building a site in (a child theme of) Twenty Nineteen. In the top menu, each instance of a menu item that has a child item is returning one error in the WAVE accessibility tool. The reported error is ""empty button"" and below is the explanation: What It Means A button is empty or has no value text. Why It Matters When navigating to a button, descriptive text must be presented to screen reader users to indicate the function of the button. How to Fix It Place text content within the " johnfclifford Future Releases 45904 Twenty Nineteen: .button doesn't override link color Bundled Theme 5.0 normal normal Future Release defect (bug) new 2019-01-10T16:00:41Z 2024-02-01T08:48:17Z "Originally reported by @crunnells in Twenty Nineteen's GitHub repo: I noticed this one [https://2019.wordpress.net/ the theme demo site] when I tried to change the ""Get in touch"" button into a link. If you put a link inside of an element with the `.button` class, the link color is the same color blue as the background, so the text can't be read. The same thing occurs when you try ``, so we'll need to have an override on the link color so that it's readable. Moved over from: https://github.com/WordPress/twentynineteen/issues/746" laurelfulford Future Releases 53681 Twenty Nineteen: Audio are lacking bottom margin Bundled Theme normal normal Awaiting Review defect (bug) new 2021-07-16T16:40:25Z 2021-08-13T17:00:40Z "Audio in Twenty Nineteen are lacking a bottom margin Posts that have audio: Cover block with background image is too close to the media. Attached is a screenshot from Mozilla Firefox " PGeorgiev Future Releases 45750 Twenty Nineteen: Bug in the menu on mobile devices; only partially visible desktop version of the menu sometimes shown instead of fullscreen mobile menu Bundled Theme 5.0 normal normal Future Release defect (bug) new 2018-12-23T11:35:44Z 2020-02-24T21:01:15Z When I click on the menu icon on websites (I've tried multiple websites, including uncustomized new installs) with the Twenty Nineteen theme, using a mobile device (iPhone 5s), it opens the mobile (fullscreen) version of the menu about half the time, but it otherwise opens the desktop version of the menu (non-fullscreen) which is only partially visible on a mobile device and not possible to use properly. I experienced this problem with the 5.01 and 5.02 versions of WordPress and the 1.0 and 1.1 versions of Twenty Nineteen. jklv Future Releases 56536 Twenty Nineteen: Button align right not working Bundled Theme normal normal Awaiting Review defect (bug) new 2022-09-08T18:14:56Z 2023-03-20T16:53:32Z "Steps to reproduce: 1. Activate the theme Twenty Nineteen. 2. Add the button block. 3. Set the alignment as right. You will see it will not align in the right, it will align on the left." smit08 Future Releases 58099 Twenty Nineteen: Button block does not respect custom width in the editor Bundled Theme 5.7 normal normal Future Release defect (bug) new 2023-04-06T15:52:52Z 2023-04-06T21:38:08Z "Steps to reproduce the issue :- 1. Activate Twenty Nineteen theme. 2. Choose button block. 3. Apply width from 25, 50 or 75. You can able to see a different changes user side but editor side it remains same. I have attached video for better understanding. Video URL :-https://share.cleanshot.com/RQYncB59N8Yf42TzvMdQ" nidhidhandhukiya Future Releases 56220 Twenty Nineteen: Centered H2 headings on full-width Cover blocks are not correctly centered Bundled Theme normal normal Future Release defect (bug) new 2022-07-14T15:40:20Z 2022-08-10T21:17:31Z "When H2 headings are added to a full-width Cover block and centered in the block editor, they do not appear visually centered on screen. This does not affect other heading sizes, only H2. == Steps to reproduce - Add a Cover block to a page and set the block to Full width - Add an H2 Heading block on top of the Cover block - Set the H2 Heading to center alignment - Add other elements like an H1 heading or paragraph and center those as well - View published page == What you expected to happen All centered elements should be centered horizontally. == What actually happened Only the H2 headings are not correctly centered; they are displayed too far to the left. Other elements are correctly centered. == Workaround This custom CSS may be used as a workaround: {{{ @media only screen and (min-width: 1168px) { .entry .entry-content .wp-block-cover.alignfull h2 { max-width: unset; } } }}} == Specs Replicated with Twenty Nineteen 2.3 WordPress 6.0.1 Gutenberg 13.6.0 active or inactive No other plugins active Firefox 102.0.1 / Chrome 103.0.5060.114 / Safari 15.3 MacOS 12.2.1 Browser size: ~~1008 x 499~~ 1512 × 748" zoonini Future Releases 59263 Twenty Nineteen: File block does not respect center alignment setting Bundled Theme 5.0 normal normal Awaiting Review defect (bug) new 2023-09-01T13:31:31Z 2023-09-01T18:06:36Z "In the Twenty Nineteen Theme, the File Block element may not be centered correctly on the front end of the website. This misalignment can result in a visually uneven layout. For a better understanding, I have attached a video. https://www.awesomescreenshot.com/video/20417359?key=343f6fb217d9d85baa05a68bcd238f6a Thank you." truptikanzariya Future Releases 57396 Twenty Nineteen: Font size issue in Cover Block Bundled Theme 6.1.1 normal normal Awaiting Review defect (bug) new 2022-12-29T12:49:00Z 2023-06-08T13:30:12Z "In Twenty Nineteen Theme, when we add a Cover block on the editor side and add the overlay text after that change the font size of the text then the changes are not reflected in the backend as well as frontend side, and I think instead of changing the text size, this is changed the Image size. Steps to replicate: 1: Activate the Twenty Nineteen Theme 2: Add Cover block 3: Add Image and Text 4: Change the Font Size of the text from the Typography settings 5: View the page/post at editor side 6: Save Page/Post 7: View the page/post at the front side For better understanding, I provide a video attachment link. Video link: https://share.cleanshot.com/BxwGn4Db3gCrbhlD3v8L Thanks." kajalgohel Future Releases 45902 Twenty Nineteen: Mobile menu isn't scrollable Bundled Theme 5.0 normal normal Future Release defect (bug) new 2019-01-10T15:08:19Z 2020-02-24T21:08:50Z "As originally reported by @anevins in the Twenty Nineteen GitHub repo: https://github.com/WordPress/twentynineteen/issues/713 Twenty Nineteen's mobile menu uses a `fixed` position, and does not allow for vertical scrolling when menu items extend beyond the screen height. In this screenshot for instance, it's impossible to scroll down and see the additional menu items: [[Image(https://cldup.com/-nMFdadUIZ-3000x3000.png)]] Normally, this would be solved by applying `display: block` (instead of `table`), and `overflow-x: scroll` to the submenu. However, in this case, that results in long menus visible under their children submenus: [[Image(https://cldup.com/x3H73ceFfZ.gif)]]" kjellr Future Releases 45796 Twenty Nineteen: Mobile menu needs improvement for navigating on touchscreen via keyboard Bundled Theme 5.0 normal normal Future Release defect (bug) new 2018-12-30T19:32:14Z 2020-02-24T21:03:04Z "Copied over from https://github.com/WordPress/twentynineteen/issues/723#issuecomment-450173083 (hattip @afercia): When the ""more"" menu is expanded on a touchscreen device, there are several hidden tab stops that cause issues when navigating the site via keyboard. These are: * hidden sub-menu items are still focusable * all the links in the page are still focusable When the menu is open it's still possible to tab away from the menu and navigate with the keyboard through all the focusable elements in the page. If the intent is to show a full-screen menu, the menu should behave like a modal and tabbing should be constrained within the modal." laurelfulford Future Releases 45901 Twenty Nineteen: On single posts with featured images, tall menus appear clipped Bundled Theme normal normal Future Release defect (bug) new 2019-01-10T14:56:59Z 2021-05-11T20:00:58Z "When viewing posts with featured images on desktop screens, tall menus are contained only within the featured image/header area. Overflow is cut off: [[Image(https://cldup.com/qMVpzNV5XH.thumb.png)]] A fix (removing `overflow: hidden;` from `.site-header.featured-image`) was pursued over on the Twenty Nineteen Github, but it led to problems in Internet Explorer: https://github.com/WordPress/twentynineteen/pull/724 --- Originally reported on the Twenty Nineteen GitHub repository: https://github.com/WordPress/twentynineteen/issues/720 " kjellr Future Releases 56143 Twenty Nineteen: Separator block alignment issue Bundled Theme 5.0 normal minor Awaiting Review defect (bug) new 2022-07-05T11:02:37Z 2022-07-05T18:08:42Z "Twenty Nineteen Themes Separator Block select Default style not center aligned in editor and Front side Steps to replicate: 1: Activate the Twenty Nineteen Theme 2: add Separator block 3: Select Default style I have given the video link of the issue below. https://www.loom.com/share/7f80bd907043491fbe8c28d30dd4cc1a" umesh84 Future Releases 46158 Twenty Nineteen: Slight flash of desktop menu when closing mobile menu Bundled Theme 5.0.3 normal minor Future Release defect (bug) new 2019-01-31T19:45:21Z 2019-01-31T19:47:30Z "Moved over from the discussion on #45905: When using Twenty Nineteen on a mobile device, you sometimes get a brief flash of the desktop menu when closing the mobile menu. Steps to reproduce: 1. Start with a test site with a longer menu, so you have the `...` more button. 2. Tap on the `...` button on a mobile device. 3. Click the 'Back' button. " laurelfulford Future Releases 45906 Twenty Nineteen: Wide alignment does not match front-end when the sidebar is active Bundled Theme 5.0.2 normal normal Future Release defect (bug) new 2019-01-10T16:28:48Z 2019-01-23T21:00:24Z "Originally reported in Twenty Nineteen's GitHub repo by @afercia: When viewing in the editor, the 'wide' block is not the same width as it appears on the front-end, when the sidebars in the editor are open. In the front-end, the wide image is always larger than the paragraph content even at smaller viewports, until it goes fully responsive under 768. This is not the case in the editor, so the views don't match. Steps to replicate: 1. In the editor, add an Image block and set it to 'wide' width. 2. Add a paragraph block, and give it a background colour (to better see it's size). 3. Compare their widths when the editor sidebars are open; the paragraph and wide image appear to be the same width. 4. Publish the page. 5. View the front-end, and note the 'wide' image and paragraphs are not the same width. Original ticket here: https://github.com/WordPress/twentynineteen/issues/667" laurelfulford Future Releases 47460 Twenty Nineteen: heading style breaks headings in content added by core or plugins in the front end Bundled Theme normal normal Awaiting Review defect (bug) new 2019-06-02T10:53:15Z 2019-06-02T10:53:15Z "The Twenty Nineteen style for headings uses some CSS generated content to draw a short horizontal line before the headings. This comes from the `post-section-dash` mixin used for various elements, for example the h1-h2 headings, `entry-title`, `author-title`, and `comments-title`. So far so good. But when ""external"" content is added to a Twenty Nineteen page, the horizontal line CSS rule targets any H1 and H2 headings. For example, when adding the media modal in the front end, the modal headings break. See attached screenshots. This also applies to any content added by plugins when the added content includes H1 and H2 headings. Seems to me this CSS selectors should be better scoped to try to target only the headings within the theme content: https://github.com/WordPress/twentynineteen/blob/b604f127c2cae10bd48bbbec0fbbbff2cd31f957/sass/elements/_elements.scss#L55-L58 " afercia Future Releases 46055 Twenty Seventeen: Blockquotes aligned right are not rechecked when widgets are added in the Customizer Bundled Theme normal normal Future Release defect (bug) new 2019-01-21T22:02:28Z 2019-01-23T19:19:31Z "While working on testing #40103 using the Customizer I discovered that when a widget is added, removed, or updated in the sidebar Twenty Seventeen does not recheck that the sidebar is empty enough to push the blockquote to the right. To reproduce: - Create a post with a blockquote two or three paragraphs down the page. - Give the blockquote the `alignright` class. - Remove widgets from the sidebar so that there is only one (none works too). - Open the Customizer. - You should see the [https://cldup.com/ygEYYBp6Bv-3000x3000.png example image posted] on #40103. - Add or change widgets in the sidebar to make the height of the sidebar pass the blockquote. The content will overlap the blockquote and it will not be pushed back into the content area as it should." desrosj Future Releases 55561 Twenty Seventeen: Blurry header image on mobile Bundled Theme 5.9.3 normal normal Awaiting Review defect (bug) new 2022-04-12T08:32:41Z 2024-02-14T21:39:33Z "Steps to reproduce - Add a custom header image via the Customizer on Twenty Seventeen - View the site on desktop - View the site on mobile/use responsive design mode to see image on a smaller screen Image used: https://philnicktestahome.files.wordpress.com/2019/09/cropped-pexels-photo-2745258.jpeg This appears to be caused by the Responsive images settings inside the theme." robertghetau Future Releases 42353 Twenty Seventeen: Header video does not load below 900px after resized and refreshed. Bundled Theme 4.8.2 normal normal Awaiting Review defect (bug) new 2017-10-27T08:39:51Z 2019-11-14T12:27:23Z "Header Media video does not load on screen size less than 900px after resized and refreshed. Instead Header Media Image is loaded. Tested on Twenty Seventeen theme and WordPress version 4.8.2. Steps: Set the video URL in the customizer's Header Media. Resize the screen and refreshed below 900px. The video does not load instead header image is shown. " sachyya sachet Future Releases 53551 Twenty Seventeen: List based widgets need style adjustments in the widget editor Bundled Theme 5.8 normal normal Future Release defect (bug) new 2021-06-29T13:15:32Z 2021-06-29T13:46:59Z "In Twenty Seventeen, list based widgets need some styling adjustments in the widget editor to better match how they are displayed on the front end. - The archives and categories widgets are displaying list bullets. - The recent posts, recent comments, archives, and categories widgets are missing the top/bottom borders. - The user display and post names in the recent comments widget should be bold." desrosj Future Releases 43243 Twenty Seventeen: Menu Items are overlapped Bundled Theme 4.9.4 normal normal Awaiting Review defect (bug) new 2018-02-07T09:01:50Z 2018-02-09T04:04:28Z "Menu Items are overlapped Steps: 1. Installed WordPress 4.9.4 2. Imported file""themeunittestdata.wordpress.xml"" 3. Activate Menu 3. Try to overlap and open inner menu items Issue: Menu Items are overlapped and some part is not displayed. " nilamacharya Future Releases 40796 Twenty Seventeen: Overriding WordPress globals is prohibited Bundled Theme 4.7.5 normal normal Awaiting Review defect (bug) new 2017-05-18T06:04:14Z 2019-11-14T12:26:19Z "In Twenty Seventeen theme, global variable $post is overridden at line 145 of /inc/template-tags.php As per theme review guidelines Overriding WordPress globals is prohibited. " maneshtimilsina Future Releases 46080 "Twenty Seventeen: Pullquote Block - ""Write citation…"" Text color not working at frontend" Bundled Theme 5.0.3 normal normal Future Release defect (bug) new 2019-01-23T11:39:10Z 2019-01-30T19:42:33Z When I add Pullquote Block in editor and assign text color from the Color setting it's working properly in backend but it's not working properly in frontend. iamjaydip Future Releases 56073 Twenty Seventeen: Pullquote Block: Color and Font size issue Bundled Theme 6.0 normal normal Awaiting Review defect (bug) new 2022-06-26T11:57:58Z 2022-06-26T11:57:58Z "In the Twenty Seventeen theme, when we add a pullquote block and color to text, the color is not reflected in the editor, but will be properly shown on the frontend. Also, changing the font size doesn't work, not reflected in the editor and forntend. Steps to replicate: 1.Activate Twenty Seventeen theme 2. Insert pullquote block 3. Add text 4. Add color and change font size" nitman43 Future Releases 58413 Twenty Seventeen: Search block is having issue when you apply width and alignment. Bundled Theme 6.2.2 normal normal Awaiting Review defect (bug) new 2023-05-26T09:10:42Z 2023-06-01T23:35:22Z "Steps to reproduce the issue :- 1. Activate Twenty Seventeen theme. 2. Choose Search block. 3. Apply width 4. Now apply alignment left or right. You can able to see that the applied width is not looking proper when alignment has been choosen. I have attached video for better understanding. Video URL :- https://share.cleanshot.com/xNx3pKbZ2znyhz4l58CT" nidhidhandhukiya Future Releases 40930 Twenty Seventeen: Sharing buttons not showing with Video, Audio, or Gallery post format Bundled Theme normal normal Awaiting Review defect (bug) new 2017-06-06T12:05:46Z 2017-06-06T16:01:50Z "'''What's expected:''' When sharing buttons are setup to show on the front page, they should be showing regardless of the post format. '''What happened:''' Sharing buttons aren't showing with Video, Audio, or Gallery format. [[Image(https://cldup.com/gbtIq-Ohq4-3000x3000.png,75%)]] Discussed with @thomasguillot, who figured out the cause: {{{ if ( ! is_single() ) { // If not a single post, highlight the video file. if ( ! empty( $video ) ) { foreach ( $video as $video_html ) { echo '
'; echo $video_html; echo '
'; } }; }; }}} If it’s not single, only the video is displayed and nothing else, the sharing buttons require something like the_content() but it’s not being called for video post formats. This also applies to audio, and gallery post format. " chocopress Future Releases 40456 Twenty Seventeen: Submenu greater than 10 items not visible Bundled Theme 4.7.3 normal normal Awaiting Review defect (bug) new 2017-04-14T22:06:02Z 2021-09-02T10:09:26Z If you add more than 10 items to a sub menu in twenty seventeen, only the top 9 items are visible when the menu expands. The remaining items are displayed off the bottom of the screen and inaccessible. When this happens, the submenu should become two column (or 3, or 4, etc.) MusicalSaw Future Releases 58708 Twenty Seventeen: caption alignment is different in editor and frontend Bundled Theme 5.8 normal normal Awaiting Review defect (bug) new 2023-07-04T05:46:57Z 2023-08-21T15:35:40Z In Twenty Seventeen theme the table caption is center in the editor but it is aligned to the left in the frontend pitamdey Future Releases 59946 Twenty Sixteen: PullQuote Block border color not showing on frontend Bundled Theme normal minor Awaiting Review defect (bug) new 2023-11-22T04:20:45Z 2023-11-23T00:09:38Z "In Twenty Sixteen, add a pullquote block and apply border and colour to it. it showing on frontend Video url - https://drive.google.com/file/d/1J3nBmyGlt1TFFh5_ksvv97x9CcJu-2ns/view?usp=sharing" pranitdugad Future Releases 51236 Twenty Sixteen: Quotes don't inherit group color settings Bundled Theme normal normal Future Release defect (bug) new 2020-09-03T20:41:20Z 2021-11-03T07:42:15Z If you have a quote inside of a group block, the group block's text color settings are not carried into the quote. melchoyce Future Releases 41822 Twenty Twelve: Submenus not working on touch screen devices Bundled Theme 4.8.1 normal normal Awaiting Review defect (bug) new 2017-09-07T08:16:52Z 2019-01-02T11:27:16Z "Appears identical to #24767 When tapping on a menu item with a submenu, the submenu briefly appears but then the browser loads the link at the top menu item. Site should be viewed in Landscape orientation for the regular menu to be visible. Confirmed on ​http://wp-themes.com/twentytwelve/ in Chrome 60 on Android 7.1.2 (Nexus 5X) The user who reported it suspects it might be related to https://www.chromestatus.com/feature/5093566007214080 From http://en.forums.wordpress.com/topic/submenu-links-broken-on-touch-devices-chrome-56" kokkieh Future Releases 55892 Twenty Twelve: submenu hidden under slideshow block Bundled Theme 3.5 normal normal Awaiting Review defect (bug) new 2022-06-01T10:47:12Z 2022-06-14T20:11:14Z "This is a replica of this issue: https://github.com/Automattic/wp-calypso/issues/63939 Steps to replicate: 1. Activate the theme Twenty Twelve 2. Add 3 elements to the same submenu on the site 3. Add a slideshow at the start of a page " robertghetau Future Releases 57415 Twenty Twenty One: Text color not reflected backend and Front side in media & text block Bundled Theme 6.1.1 normal normal Awaiting Review defect (bug) new 2023-01-03T13:34:51Z 2023-01-17T08:13:05Z "In Twenty Twenty One Theme: when we add a media & Text Block on the Editor side and add the Text after apply the link on the Text and change color to the text but changes are not reflected backend and Front side. Steps to replicate: 1: Activate the Twenty Twenty One Theme 2: media & text block 3: Add Image and Text 4: add Link on the Text after change color For better understanding, I provide a video attachment link. Video link: https://www.loom.com/share/ceea0db29302412b8bc2b3fb8dcea151 " umesh84 Future Releases 57034 Twenty Twenty Three: Query loop block carousal view pattern spacing issue Bundled Theme 6.1 normal normal Awaiting Review defect (bug) new 2022-11-08T13:23:07Z 2023-09-09T09:32:50Z "In Twenty Twenty Three Theme: Query loop block carousal spacing issue. 1)Activate Twenty Twenty Three Theme 2)Add Query loop block and click on choose button 3)Choose pattern layout displaying and select a carousal view layout. 4)We need to fix spacing issue in layout from left and right hand side." multidots1896 Future Releases 59957 Twenty Twenty and Twenty Twenty-One: Details block padding issue when setting its alignment to full-width Bundled Theme 6.3 normal normal Awaiting Review defect (bug) new 2023-11-24T06:34:44Z 2023-12-13T19:36:35Z "Hello Team, I have worked on the **""Twenty Twenty""** theme and found that the **""Twenty Twenty""** theme contains an issue for the ""Details"" block. The padding is not displaying properly on the back-end side. The front-end side looks good. When we set **""Full Width""** from the components toolbar group Here, I have provided screenshots: **Front-end:** [[Image(https://share.cleanshot.com/5lDkjpfwVVwwxFRlNvwl)]] **Back-end:** [[Image(https://share.cleanshot.com/zdf5SNvpv7kzrHRL9F8N)]] Thanks," viralsampat Future Releases 60616 Twenty Twenty-Four: There is shaking effect while selecting Maelstrom style Bundled Theme 6.4.3 normal normal Awaiting Review defect (bug) new 2024-02-23T06:27:36Z 2024-03-12T15:44:43Z "When I select the Maelstrom style it continuously gives a shaking effect. Is this given purposely as its name suggests? 🤔 == Bug Report === Description I observed the constant shaking effect for Maelstrom style. === Environment - WordPress: 6.4.3 - 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. Now, open a style 3. Click on **Browse Style** 4. Select **Maelstrom** style 5. Now, observe the shaking effect as shown in the screenshot. === Expected Results 1. If we select any other styles they don't behave strangely whereas here it seems like a bug. But not sure if such an effect is given purposely. === Actual Results 1. ❌ It should not shake like other styles. === Supplemental Artifacts Add as Attachments " krupajnanda Future Releases 54204 Twenty Twenty-One:
...
}}} **Remediation Guidance** Turn the form into an actual `
` element. Wrap `
` tags (with accompanying `` elements) around groups of controls explaining what they are. Use the id on the `` element with the form attribute on the ""Select"" button to designate this as the form's submit button. Add text to the ""Edit"" link that opens in a new window or tab, informing users that this will happen. When the form in the new tab/window is submitted, users should be brought back to the original form. **Recommended Code** {{{
...
Filter media options
Media options result
  • ...
...
Attachment Details ...
...
...
1820 × 1213
Edit Image Opens in a new window
...
}}} **Relevant standards** * 1.3.1 Info and Relationships (Level A) https://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic * 1.3.3 Sensory Characteristics (Level A) https://www.w3.org/TR/WCAG20/#content-structure-separation-understanding * 3.3.2 Labels or Instructions (Level A) https://www.w3.org/TR/WCAG20/#minimize-error-cues * 4.1.2 Name, Role, Value (Level A) https://www.w3.org/TR/WCAG20/#ensure-compat-rsv **Note**: This issue may be a duplicate with other existing accessibility-related bugs in this project. This issue comes from the Gutenberg accessibility audit, performed by Tenon and funded by WP Campus. This issue is GUT-50 in Tenon's report" anevins Future Releases 47148 Insufficient labelling and inappropriate nesting of form controls joedolson* Media normal minor Future Release defect (bug) accepted 2019-05-06T15:16:18Z 2024-02-05T20:03:21Z "Moved from the WPCampus accessibility report issues on GitHub, see: https://github.com/WordPress/gutenberg/issues/15288 * **Severity**: * Low * **Affected Populations**: * Blind * Low-Vision * Cognitively Impaired * **Platform(s)**: * Windows - Screen Reader * Windows - ZoomText * Mac - VoiceOver * Android - TalkBack * iOS - VoiceOver * **Components affected**: * Media Dialog **Issue description** In the ""Featured Image"" modal dialog's ""Media Library"" tab, users can choose an image to be the featured image; this is presented as a series of checkbox elements which, once checked, show a button to uncheck inside the custom checkbox element. This button is in the Tab order, however its only name is ""Deselect"", it doesn't tell the user what is being deselected. Users must infer what this button does from context, and may wonder why it's next to seemingly-ordinary checkboxes which themselves are natively unselectable. The button role of these buttons does not convey that the user is checking or unchecking an item, and their placement inside the checkbox elements is semantically confusing, and may be functionally confusing since one focusable element is nested inside another. Screen reader users hear that a list is present, yet find that they cannot navigate by list-items. **Issue Code** {{{
  • ...
}}} **Remediation Guidance** Allow the list semantics to remain available by not overriding the `
  • ` elements' native list-item roles. Remove the ` }}} **Remediation Guidance** When users have performed an action, such as clicking another block (or whatever action causes ""No block selected"" to appear in the Block panel), clear the live region so that users who encounter it while manually reading do not hear it. Refill the live region when users change color modes. The hidden file selection button should be hidden from all users with display: none whenever it is not visible nor meant to be used. **Recommended Code** {{{
    }}} **Note**: This issue may be a duplicate with other existing accessibility-related bugs in this project. This issue comes from the Gutenberg accessibility audit, performed by Tenon and funded by WP Campus. This issue is GUT-41 in Tenon's report ''**Note**: The a11y-speak live regions are used in core as well. In several places. Thus, clearing the live regions shouldn't depend on a specific user action or scenario. It would require a more generic solution, preferably avoiding setTimeout() which seems to me a very fragile solution by its own nature.''" anevins Future Releases 58733 The load more button appears even when there is only one image in the feature image selection window. joedolson* Media 6.3 normal normal Awaiting Review defect (bug) accepted 2023-07-06T13:22:35Z 2023-07-21T15:20:00Z "Load more button appears in the popup window for replacing the feature image, even when there is only one image available. Steps to reproduce the issue: 1. Go to the post editor in WordPress. 2. Locate the section where you can edit the feature image for the post. 3. Click on the ""Replace"" button to select a new image. 4. The popup window will open, showing the available images. Despite there being only one image in the selection, the ""Load More"" button is present in the popup window. Video Link: https://www.loom.com/share/c0e9faa4cc86455eb30bdaf2149b5a60 === Environment - WordPress: 6.3-beta3-56143 - PHP: 7.4.21 - Server: Apache/2.4.46 (Unix) OpenSSL/1.0.2u PHP/7.4.21 mod_wsgi/3.5 Python/2.7.13 mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_perl/2.0.11 Perl/v5.30.1 - Database: mysqli (Server: 5.7.34 / Client: mysqlnd 7.4.21) - Browser: Chrome 114.0.0.0 (macOS) - Theme: Twenty Twenty-Three 1.1 - MU-Plugins: None activated - Plugins: * WordPress Beta Tester 3.5.0" aparnajl Future Releases 58483 UI issue in uploasd multiple media in mobile Media 6.2.2 normal normal Awaiting Review defect (bug) new 2023-06-08T07:40:16Z 2023-06-08T07:40:16Z "Hi, We need to add padding on the right side for maintaining alignment on the right side in uploading multiple media on mobile. The more informed nation you can see mentioned screenshot. " sumitsingh Future Releases 48111 Update usage of `multi_resize` to utilize new `wp_create_image_subsizes()` function kirasong Media 5.3 normal normal Future Release defect (bug) assigned 2019-09-23T17:48:40Z 2020-02-21T09:41:15Z "As mentioned in https://core.trac.wordpress.org/ticket/40439#comment:61 There are two uses of `multi_resize()` that will need to be updated to use the new `wp_create_image_subsizes()` function introduced in #40439. - In the [https://github.com/WordPress/WordPress-develop/blob/master/src/wp-admin/includes/image-edit.php#L947 image editor] (`src/wp-admin/includes/image-edit.php`). - In [https://github.com/WordPress/WordPress-develop/blob/master/src/wp-admin/includes/image.php#L583 PDF Thumbnails/Fallback Thumbnail Support] (`src/wp-admin/includes/image.php`). " antpb Future Releases 34465 Uploader in Media Modal Not Working When Certain Library Arguments Present Media 4.0 normal normal Awaiting Review defect (bug) new 2015-10-27T13:32:55Z 2017-09-18T00:16:15Z "I noticed this bug while working on a plugin that deals with the media modal. I'm using the following code to create a media modal on a button view: {{{ function frame(){ // Destroy the previous collection frame. if ( this._frame ) { this.stopListening( this._frame ); this._frame.dispose(); } this._frame = wp.media( { className: 'media-frame rwmb-media-frame', multiple : true, title : 'Select Media', library : { type : 'image', }, frame: 'select', } ); //Event stuff goes here this._frame.open(); }, }}} The issue is when uploading a file using the upload tab in the media modal. The file uploads but it never appears in the Media Library tab like it does in the core media modal used by the editor. The side Attachment Details panel shows the file information but the file itself doesn't appear on the grid. Attached is a screen cap from a user of the plugin. " Funkatronic Future Releases 40289 Uploading 2 files with the same name but different casing, overwrites existing files Media 4.7.3 normal normal Awaiting Review defect (bug) reopened 2017-03-28T22:23:44Z 2017-06-08T09:36:11Z "Problem: Under normal circumstances, if I upload a file to the media library but a file with a similar name was previously uploaded, wordpress would change the name of the new file (by adding a dash and a number). However, If I upload 2 files with the same name, BUT WITH DIFFERENT CAPITALIZATION, wordpress won't rename the second file and will just reference the older one. So if for example, I already had the file cover.jpg in my library and I've created a new post and uploaded the file COVER.JPG, it will show in the post the older image of (cover.jpg)." quickim Future Releases 42484 WP ajax call fail when executing long time 'ERR_SPDY_PROTOCOL_ERROR'. Media 4.8.3 normal normal Awaiting Review defect (bug) new 2017-11-09T12:18:18Z 2017-11-09T12:38:47Z "Hello, I have one ajax script that is uploading 25MB video on server and convert on server. This core process doing by only WordPress ajax file. This process is run successfully but after uploading and conversion ajax automatically fail and give me this error ""ERR_SPDY_PROTOCOL_ERROR"". This error i am facing from last update(4.8.3). so i think there is issue regarding ajax call in WordPress 4.8.3 version. I am WordPress Developer with 6+ years of experience and i have found this bug. Please review this bug. There is attach one image related to error. [[Image(http://webidroid.com/WP_ajax_err.png)]] " gaurangsondagar Future Releases 55057 WebP EXIF data missing and images are not rotated in the same way JPEG images are rotated. adamsilverstein Media 5.8 normal normal Future Release defect (bug) assigned 2022-02-03T01:25:58Z 2022-07-07T18:29:05Z "When a WebP image is uploaded with the rotated exif this exif is ignored and the image is uploaded as it is instead of rotating the image when a JPEG version is uploaded the rotation happens as it should creating a `-rotated.jpeg` version of the original image. **Result when uploading a JPEG version** [[Image(https://user-images.githubusercontent.com/3921289/152251451-201251d2-409f-42d6-a302-a93bfe3aec3c.png)]] **Result when uploading a WebP version** [[Image(https://user-images.githubusercontent.com/3921289/152251458-1f3d98ac-5b40-4728-97a9-a3c05aa7cbb7.png)]] Steps to replicate the problem: - Create a WebP version of the original JPEG image (you can use imagemagick to do this) - Upload the WebP version of the image and observe the image is not rotated the same way it happens with the JPEG version. Original JPEG image used to test this behavior can be found at (and attached as part of this report): - https://www.flickr.com/photos/brevity/6221434141/in/photostream/ Related with the performance ticket: - https://github.com/WordPress/performance/issues/146 **Media handling information from the installation where this is happening: ** Active editor WP_Image_Editor_Imagick ImageMagick version number 1691 ImageMagick version string ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org Imagick version 3.7.0 File uploads Enabled Max size of post data allowed 100M Max size of an uploaded file 100M Max effective file size 100 MB Max number of files allowed 20 Imagick Resource Limits area: 122 MBdisk: 1073741824file: 786432map: 512 MBmemory: 256 MBthread: 1 ImageMagick supported file formats 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, AVI, AVIF, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DJVU, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FILE, FITS, FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, H, HALD, HDR, HEIC, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, LABEL, M2V, M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIDEO, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV GD version bundled (2.1.0 compatible) GD supported file formats GIF, JPEG, PNG, WebP, BMP Ghostscript version 9.53.3" mitogh Future Releases 53941 When converting images after uploading the original image may not be converted Media 5.8 normal normal Future Release defect (bug) new 2021-08-17T03:12:58Z 2021-11-16T18:57:42Z "This is less noticeable when the original image is larger than the ""big image threshold"" (and not a PNG) as the scaled image is converted. To reproduce: - Set image conversion, for example GIF to JPEG. - Upload image.gif that is smaller than 2560x2560px. - Note that image.gif is listed in the Gallery and present in the uploads directory but it's sub-sizes have been converted to JPEGs like image-150x150.jpg, etc. Expected behavior: the original image should be converted." azaozz Future Releases 40250 When cropping a image right after scaling, the crop selection will show incorrect dimensions adamsilverstein Media 4.7.3 normal normal Future Release defect (bug) reviewing 2017-03-24T11:04:59Z 2021-01-28T19:53:54Z "Steps to reproduce: - Upload any image to the media library. - Press ""Edit Image"" on the uploaded image. - Scale the image up or down by any dimension. - Try to crop the image afterwards with the drag selection on the image. On the screenshot provided you will notice the crop dimensions are actually larger then the image size. The bug only seems to appear when the page is not being refreshed, indicating the correct values are probably not being passed to the javascript handling the cropping after a scaling operation. [[Image(source:http://imgur.com/fEj6uDP)]] (Screenshot: http://imgur.com/fEj6uDP) " level level Future Releases 55345 When uploading image through featured image section, the image item count is wrong. Media normal normal Awaiting Review defect (bug) new 2022-03-08T17:45:56Z 2022-06-08T14:17:41Z "When uploading image through featured image section, the image item count is wrong. === Env * 5.9.1 * Brave, Chromium * Win 10 * Theme : TT2 * Plugins: None === Test Instruction * Open Post Editor and click on 'Set featured image' option. * Notice the total number of existing images * Upload a new image into the featured image section. * Now notice the number of images (+2) * Reload the page, and now the count corrects itself. When uploading image directly to the featured image section of the post editor, the media item count works correctly. " alanjacobmathew Future Releases 45980 WordPress 5.0.3 PDF is opening empty page in Chrome and not showing content Media 5.0.3 normal normal Awaiting Review defect (bug) reopened 2019-01-14T10:34:54Z 2019-01-30T07:38:23Z "Hi, I have some links that open pdf. On firefox or safari, when I clic on the link, the pdf is opend on another page. I can see the pdf. On Chrome, when I clic, anoter page is open but the page is empty. I can see on the url that the pdf is open https://www.....de/wp-content/uploads/2018/07/TEST.pdf but it is empty. And it worked before (not with WordPress 5.0.1) And it doesn't work with new pdf too. MAny thanks for you help" Timama Future Releases 30402 WordPress does not respect the bit-depth of the original image when resizing Media 3.9.2 normal normal Awaiting Review defect (bug) new 2014-11-19T08:15:02Z 2021-03-04T15:09:12Z "i have uploaded 8 bit depth indexed color png, near 1400x1800 size image in wordpress and inserted it into post , and original image was near 500 kB and the smaller width-height version made by wp is near 1400 kB, because it is 24 or 32 bits per pixel png. (this is useless. i have edited html code to use full version because it is smaller by weight and it is scaled by size so it is ok)." qdinar Future Releases 36308 get_attached_file() destroys file paths on Windows Media 4.4.2 normal normal Future Release defect (bug) assigned 2016-03-23T15:45:03Z 2023-05-31T15:30:19Z "While working on ticket #36273 I noticed that ''get_attached_file()'' from ''wp-includes/post.php'' will destroy paths normalized by ''wp_normalize_path()'' on Windows: For example the function starts with {{{#!php $file = get_post_meta( $attachment_id, '_wp_attached_file', true ); // $file = 'C:/WWW/Sites/demo/htdocs/wordpress/wp-content/uploads/2016/03/example.jpg' }}} However this will become {{{#!php $file = 'C:\WWW\Sites\demo\htdocs\wordpress/wp-content/uploads/C:/WWW/Sites/demo/htdocs/wordpress/wp-content/uploads/2016/03/example.jpg' }}} due to {{{#!php if ( $file && 0 !== strpos($file, '/') && !preg_match('|^.:\\\|', $file) && ( ($uploads = wp_upload_dir()) && false === $uploads['error'] ) ) $file = $uploads['basedir'] . ""/$file""; }}} This is similar to ticket #24824 however we are dealing will full qualified paths here, not URLs (well, both are URIs...). PS: Yes, `$uploads['basedir']` contains mixed directory separators. That's another thing." Whissi Future Releases 53200 image quality reduction in smaller images Media 5.7.2 normal normal Awaiting Review defect (bug) new 2021-05-13T13:01:43Z 2021-05-13T13:01:43Z "So what happens is you upload a full size image to wordpress in my case project53.co.uk and I am using a goodlayers theme but I have repeated the same process on a stoc install on a different site and have the same issue. On this site for example the easiest one to see it on is the woman and look at the cheeks as full size looks ok and has colour and smaller images looks toned down and grey and it is wordpress changing the image quality with the smaller images. this is the details send from our dev guy For now - I have removed the thumbnails that the site was trying to use (I had set it to 'full', which should have been used, but the theme didn't want to co-operate) and then regenerated the thumbnails - pretty much forcing the site to use the full-size image. It may occur elsewhere in the site - hard to say until I've seen every possible variation of an image on the theme - but as long as we repeat the same steps to remove the thumbnail size and regenerate, it will be fine. You could just remove all regenerated sizes and ensure that sizes are set by the container the image is in; that would definitely stop it. So if you see another image (or multiple images) having the same problem: Inspect that image and see what thumbnail size it is using. (You can generally tell by the suffix on the end of the image name, e.g. blahblah-800x600.jpg) Go into Goodlayers Options > Miscellaneous > Thumbnail sizing Remove the thumbnail size that it's using Go into Tools > Regenerate Thumbnails Ensure that the thumbnail size that you remove is not there Click Advanced Options, and check the box which says ""Delete unselected thumbnails"" - this will remove that size from the server and tell WordPress it doesn't exist If it was me - I'd unregister all of the thumbnails and just limit the size of images which are being uploaded - and use that size globally throughout the theme (if the size doesn't exist it should fallback to the full size image as default). That doesn't necessarily have to be the case - but you just don't want 5MB images on a page - because then you'll have all the page speed problems to deal with! " digitalmountain Future Releases 46390 image_default_link_type is not seen by Gutenberg Media 5.1.1 normal normal Awaiting Review defect (bug) reopened 2019-03-01T12:34:42Z 2022-04-05T02:26:53Z "I have in option.php the image_default_link_type set to file so that by default the ""link to "" for all media files is by default set to media. Since upgrading to Gutenberg 5.1, this feature appears to be deactive." brianjcameron Future Releases 54205 jqxhr is undefined inside of deferred.done() when using wp.media to add a custom image upload Media 5.8.1 normal major Awaiting Review defect (bug) new 2021-09-30T20:55:42Z 2022-05-31T14:33:33Z "I have done all the usual trouble shooting and found this is being cause by a new block of code added to wp-util.js in 5.8.1. Specifically lines 121-134. The jqXHR property does not exist inside of the done() object and therefor always errors out. This is removing a key functionality of a clients admin that makes it where no new products can be added without a horrible workaround." metawebdevelopment Future Releases 59641 manually setting fetchpriority on image should prevent core from adding fetchpriority attribute Media 6.3 normal normal 6.6 defect (bug) new 2023-10-16T20:44:56Z 2024-02-17T13:44:33Z "When working on testing the automated fetchpriorty attribute core now adds for images, I discovered this bug: If users manually set fetchpriority=""high"" on an image either programmatically or using a plugin, core will not change that setting, however it unexpectedly sets fetchpriority=""high"" on another image. === Steps to reproduce 1. install this plugin to add a manual fetchpriority dropdown: https://github.com/adamsilverstein/wp-fetchpriority-control 2. create a post with several large images 3. select the first image and apply fetchpriority=""high"" (under advanced) 3. publish the post and view its source **Expected results:** Only the first image should have the `fetchpriority=""high""` attribute, setting high fetchpriority on more than one image reduces the effect of adding the attribute. **Actual result:** Core applies `fetchpriority=""high""` to the second image so the first two images contain the attribute. " adamsilverstein Future Releases 45802 media_upload_tabs not supported in 5.0? Media normal normal WordPress.org defect (bug) reopened 2019-01-01T04:37:22Z 2019-06-04T19:16:22Z "I noticed the instructions here are incorrect at least for the latest WordPress 5.0 https://codex.wordpress.org/Inserting_Media_into_Posts_and_Pages At least, I can't seem to find the add media and it appears to be replaced by Gallery and Image, which shows upload/media-library/insert-from-url. Unfortunately it looks like there is no longer a way to get to this dialog and use extra upload-tabs to the left on the dialog shown in the tutorial linked above. In other words [https://developer.wordpress.org/reference/hooks/media_upload_tabs/ media_upload_tabs] doesn't do anything? If so, it should probably note this on that filter page and on the codex page. " programmin Future Releases 46209 mediaelement CSS loading at bottom of body Media 4.9 normal normal Future Release defect (bug) new 2019-02-07T21:55:20Z 2023-01-31T13:55:35Z "The question was asked in #42751 why we are loading mediaelement css in the body. It was agreed in the recent Media meeting that this is better fit for it's own ticket for discussion. ---- Mentioned by @themezly : While we are at it, why are we loading mediaelement CSS files at the bottom of body http://prntscr.com/hh0808 ? CSS files should always be in head. " antpb Future Releases 46544 mp3 file with different file mime type and content type when uploading should not be rejected Media 5.1 normal major Awaiting Review defect (bug) new 2019-03-17T02:51:33Z 2023-01-27T02:33:41Z "{{{#!php wp_print_media_templates(). llvasconcellos Future Releases 41372 when no any media. at that time this section is not usable. so Please hide when no any media. Media normal major Awaiting Review defect (bug) reopened 2017-07-20T07:57:16Z 2017-11-06T06:02:03Z When no any media at that time this section is not usable. So please hide when no any media. rushabh4486 Future Releases 53187 wp_filter_content_tags added too early Media 5.5 normal normal Awaiting Review defect (bug) new 2021-05-11T19:15:40Z 2021-07-26T16:31:46Z "Currently wp_filter_content_tags filter is added to the_content filters with default priority, this means that if the iframe is outputted by shortcode it will not get the lazy loading attribute. I think that it should be added after do_shortcode has run with priority of 12." maciejmackowiak Future Releases 32117 wp_get_attachment_metadata sizes array file misses path if using year/month organizing Media 4.2 normal normal Awaiting Review defect (bug) new 2015-04-24T15:58:51Z 2017-08-14T13:15:29Z "wp_get_attachment_metadata returns array like this: {{{ [""metadata""]=> array(5) { [""width""]=> int(3072) [""height""]=> int(2304) [""file""]=> string(25) ""2015/03/GC702D01_high.jpg"" [""sizes""]=> array(4) { [""thumbnail""]=> array(4) { [""file""]=> string(25) ""GC702D01_high-200x150.jpg"" [""width""]=> int(200) [""height""]=> int(150) [""mime-type""]=> string(10) ""image/jpeg"" } }}} as you can see, ""file"" in the first level of the array contains year and month (as i do have turned on organizing in year/month structure for uploads), but ""file"" in the second level for (e.g. in this case) the thumbnail size is only the file name, without the path. This is at least confusing, make it difficult to get the URL of the file - each size need to be then requested separately by wp_get_attachment_image_src function. IMO optimal solution would be to use full path in both `$metadata['file']` and `$metadata['sizes'][$size]['file']` so the same name would have the same structure. But i do not know if it wouldn't have some compatibility issues. Less optimal imo would be to add there also the path - it can be there only once in the top level, as all sizes are currently always in the same folder, but i think this could lock us from possible changes / plugin modifications etc. E.g. I think that it would be great, if it would be possible (and even default) to have size name, as a folder, so that we would have thumbnails in uploads/thumbnail, medium size in uploads/medium ... - this would highly reduce the number of images in one folder in default settings and would reduce the problems with displaying them on most systems. And also if we would want to delete some defined size, we could simply delete one folder and save space. So the second optimal would be to show the path in `sizes[$size]` subarray, e.g. {{{ [""metadata""]=> array(5) { [""sizes""]=> array(4) { [""thumbnail""]=> array(4) { [""file""]=> string(25) ""GC702D01_high-200x150.jpg"" [""path""]=> string(25) ""2015/03/"" } }}}" thomask Future Releases 58611 wp_get_missing_image_subsizes can return incorrect subsizes for a rotated image antpb Media 6.2.2 normal normal Future Release defect (bug) assigned 2023-06-23T12:33:44Z 2024-02-05T20:27:49Z "During the upload of a rotated image to the Media Library, the `wp_get_missing_image_subsizes()` function often returns missing subsizes for the non-rotated original image that will never be generated for the rotated image. This means for example, if a plugin is filtering `wp_update_attachment_metadata` and waiting for all thumbnails to have been generated before performing some action, it may be told that there are missing thumbnails for a rotated image, that will not be generated. Therefore it will not be able to perform that action as not all the thumbnails are deemed to be available." ianmjones Future Releases 51421 wp_get_missing_image_subsizes returns thumbnail sizes for animated GIFs Media 5.5.1 normal normal Awaiting Review defect (bug) new 2020-09-30T14:27:32Z 2020-10-01T14:36:20Z "While thumbnails are not created for animated GIFs to avoid the problem of users picking a thumbnail size to insert into their content and unexpectedly getting a static image instead of an animated GIF, they are generated for static GIFs. The `wp_get_missing_image_subsizes` function however recognizes animated GIFs as an image format that can have subsizes generated, and so returns a list of missing thumbnail sizes that will never be created. This causes problems for various plugins when checking whether all required thumbnails exist before commencing processing the GIF etc." ianmjones Future Releases 43413 wp_prepare_attachment_for_js missing image size medium_large Media 4.9.4 normal normal Future Release defect (bug) new 2018-02-25T18:54:29Z 2019-04-15T18:12:50Z "I have a function that creates a media size in case the size is called but is missing in meta. https://gist.github.com/danyj/2edb3d83bae4c363bf839f0dd5f1343f usage {{{ thz_create_missing_attachment_size(13031,'medium_large'); }}} every missing file size is recreated and exists in by wp_prepare_attachment_for_js size key except the media_large because it is missing here. https://github.com/WordPress/WordPress/blob/dfa68397063daf90a8758896693f137f9b981856/wp-includes/media.php#L3297-L3304 Basically if meta has been updated the wp_prepare_attachment_for_js is not checking for sizes but manually goes by that array . Not sure if the missing size key is left out on purpose but when you compare the wp_prepare_attachment_for_js to wp_get_attachment_metadata the data is not same " Themezly Future Releases 58240 wp_read_image_metadata() doesn't handle Exif array values joedolson* Media normal normal Future Release defect (bug) accepted 2023-05-03T06:02:01Z 2024-02-05T20:25:50Z "Some images appear to have multiple values for some headers, which causes `wp_read_image_metadata()` to return `'Array'` for some fields. A real-life example are these images: - https://wordpress.org/photos/photo/3056444e62/ - https://wordpress.org/photos/photo/7716444e53/ - https://wordpress.org/photos/photo/5376444e57/ Looking at the return value from `exif_read_data()` for one of these, you'll see arrays below. However `wp_read_image_metadata()` includes lines like `(string) $exif['FocalLength'];`. It looks like `iPhone 13 mini` might be common between the above examples {{{ [...] 'SectionsFound' => string(19) ""ANY_TAG, IFD0, EXIF"" 'COMPUTED' => array(6) { [...] 'ApertureFNumber' => string(5) ""f/1.6"" } [...] 'Make' => string(5) ""Apple"" 'Model' => string(48) ""iPhone 13 mini back dual wide camera 5.1mm f/1.6"" 'Exif_IFD_Pointer' => int(106) 'ApertureValue' => array(2) { [0] => string(9) ""1356/1000"" [1] => string(9) ""8803/1000"" } [...] 'FocalLength' => array(2) { [0] => string(9) ""5100/1000"" [1] => string(10) ""10884/1000"" } 'ShutterSpeedValue' => array(2) { [0] => string(10) ""10884/1000"" [1] => string(19) ""1124129791/84149760"" } }}} As a result on the above Photo pages you'll see something like this: {{{ Focal Length: Arraymm Shutter Speed: 1/0 }}} This could be related to the image processing application being used, or the sections found in the image. I'd be tempted to just select the first array key in those cases." dd32 Future Releases 60178 wp_video_shortcode() outputs invalid HTML Media normal normal Awaiting Review defect (bug) new 2024-01-02T22:09:17Z 2024-02-15T07:25:42Z "Did an audit of a website and found several invalid HTML for video tags that were output with `wp_video_shortcode()`. The errors: * Bad value `1` for attribute `loop` on element `video` * Bad value `1` for attribute `autoplay` on element `video` * Bad value `1` for attribute `muted` on element `video` Based on documentation from Mozilla, all 3 are boolean attributes. Here is an example of function usage that produced the HTML validation errors: {{{#!php wp_get_attachment_url(9999), 'class' => 'my-custom-video', 'poster' => '', 'loop' => 'true', 'autoplay' => 'true', 'muted' => 'true', 'height' => 1080, 'width' => 1920 ] ); }}} This part in `wp_video_shortcode()` is the culprit: {{{#!php $v ) { $attr_strings[] = $k . '=""' . esc_attr( $v ) . '""'; } }}} Currently, we are using the filter to clean up these attributes like this: {{{#!php ' . /* translators: %s: Asterisk symbol (*). */ sprintf( __( 'Required fields are marked %s' ), '*' ) . '

    ' . '' . $item . '
    '; } }}} The foreach loop that goes through all fields could easily check if any field has the ""required"" attribute and rather use that as a condition to show the message instead of `$item`." webzunft Future Releases 60345 Add duplicate checking for uploaded attachments Media normal normal Awaiting Review enhancement new 2024-01-25T16:39:34Z 2024-01-25T16:39:34Z "It can be very difficult to tell whether you've already added a given document or image to your media library if it's no longer in recent items. The lack of sorting or filtering makes specific difficult to locate. Based on a [https://wordpress.slack.com/archives/C02SX62S6/p1706115251959409 conversation on duplicate detection in #core-media], we think that a starting point for this is to hash the meta data for an attachment at the time of upload and store that as attachment meta. We could then check for that hash value before uploading a new document, and prompt the user to use the old attachment if it already exists. The specific meta data would probably need to vary depending on the type of attachment." joedolson Future Releases 39626 Add video poster in media browser Media normal normal Awaiting Review enhancement new 2017-01-18T15:07:26Z 2020-03-02T16:17:23Z "When you upload images you get to see amazing thumbnails in the browser. This unfortunately isn't the case for videos. Could we somehow have this? This is what we currently have: [[Image(https://cldup.com/yK6Hu9pZgw.png, 50%)]]" karmatosed Future Releases 31139 Allow editing of video embed parameters in the media modal wonderboymusic Media normal normal Future Release enhancement reopened 2015-01-26T18:53:55Z 2017-07-10T17:33:41Z Unsure if this is possible, but it would be pretty sweet if you could adjust available video embed parameters, such as height/width, straight from the media modal. It could fit pretty well on this screen: https://cloudup.com/caoYOVuWM41 melchoyce Future Releases 36270 Allow filtering of the final HTML output of media related shortcodes Media 4.7.2 normal normal Awaiting Review enhancement new 2016-03-18T02:33:02Z 2020-04-09T09:00:28Z "Sometimes it is required to further process the final HTML output of the media related shortcodes, eg {{{caption}}} or {{{gallery}}}, so as to add extra HTML code such as enclosing div or span elements or just modify the existing HTML code during run time. For instance the final output of {{{img_caption_shortcode}}} could be filtered: https://core.trac.wordpress.org/browser/tags/4.4.2/src/wp-includes/media.php#L1537 Passing all relevant image attachment data, like ID and size, would also be very useful. I hope that I am not missing anything but right now the only way to insert code inside the {{{
    }}} or {{{
    }}} block seems to be the complete override of the {{{img_caption_shortcode}}} function. " gnotaras Future Releases 41854 Allow filters to be added for the Media Library in Grid Mode & Insert Media Media 4.8.1 normal normal Awaiting Review enhancement new 2017-09-11T08:02:45Z 2017-09-17T14:41:55Z "Hello, I would like to suggest the action '''restrict_manage_posts''' and '''pre_get_posts''' to be used by the Media Library in Grid Mode. It would also be great to have this available in Insert Media or when picking a Featured Image. That will allow many developers to add useful filters and avoid users to look desperately for their images/photos :) Many users have been asking this and most of them believed it was a bug (List Mode and Grid mode look very similar so the absence of filters for the Grid Mode is actually not logical). Thanks a lot :)" TigrouMeow Future Releases 33054 Better featured image/attachment sanity checks Media 4.2.2 normal normal Awaiting Review enhancement new 2015-07-20T22:19:09Z 2017-06-27T16:16:22Z "Use case: Add a post: If a user uploads a featured image and the file fails to write to disk, the post record contains the url to the image but of course the image is broken. The end state is one where the featured image is simply broken, but the post record references the image. Possible solutions: 1. Do an extra sanity check after write to disk that the image was actually created. If there was a failure alert the user. This is probably the easiest. 2. Or reverse the order of operations, making it transactional in nature. That is, create the image(s) first, check if successful, and then update the post record. If there is a failure show an alert to the page, and don't write the image path to the post record as the file doesn't exist. It is alot cleaner to not have an image than having a broken one. It is also better if the image was successfully written to disk but the post url failed to update for some reason; we can always re choose from the media library. a. Going above and beyond, the sanity check would keep track of thumbnail sizes to be created and make sure they all were successful. If not, don't update the post record and remove the thumbnail sizes that did write to disk. Once again treat as a transaction; all or nothing. Extended impact: Many folks use image compression plugins or tools that compress the images before writing to disk. Currently if those items fail usually by timeout you are left with a broken image and the url is in the meta. I propose that there be a pre-check as to the thumbnails to be created before the image write even occurs (add a new action hook that keeps track of the thumbnails we expect from add_image_size) and then check on the backside to make sure we have the image(s) we expect. After that all sanity check rules proposed above would apply." ShawnLunny Future Releases 50169 Consistency in Gallery and Image block settings Media 5.4.1 normal normal Future Release enhancement reopened 2020-05-14T14:24:11Z 2020-07-21T22:10:08Z "In the Gutenberg repo we have been tracking an issue focused on unifying the Gallery and Image editing experience. Currently, it's a bit disconnected from image settings and this ticket aims to change the Gallery block to create instances of image blocks rather than raw markup https://github.com/WordPress/gutenberg/issues/11436 From the issue: Is your feature request related to a problem? Please describe. Single and gallery options should be similar to each other. I added one image to a gallery and want to resize it in a similar way to how I resize single images. Not possible. I want to add images by clicking the standard add image media library screen but it only says upload an image. It should be identical to the single image media selection options. Describe the solution you'd like I would like to see much more consistency between single image and gallery options. It should be very easy to go from one to the other with similar options. As one begins working with images an expectation is created that image options should be similar between various blocks that handle images. Single image options [[Image(http://user-images.githubusercontent.com/5323259/47937002-c17bf600-dedf-11e8-9823-ad596ce22764.png)]] Gallery image options [[Image(https://user-images.githubusercontent.com/5323259/47937047-dfe1f180-dedf-11e8-8b08-0db18edc2eb2.png)]] Single image upload media options: [[Image(https://user-images.githubusercontent.com/5323259/47937075-ee300d80-dedf-11e8-8bb1-44a47574e2ac.png)]] Gallery upload media options: [[Image(https://user-images.githubusercontent.com/5323259/47937095-fbe59300-dedf-11e8-88d9-6dbea7190f78.png)]] Captions are also different from single images to the gallery. Top example shows the Gallery and bottom a single image. [[Image(https://user-images.githubusercontent.com/5323259/47940629-8e3f6400-deeb-11e8-9ff6-cfa71c5daccf.png)]] Btw It would also be very helpful to be able to rearrange the gallery images by using drag and drop. " antpb Future Releases 53645 Convert heic to a web safe image format. Media normal normal Awaiting Review enhancement new 2021-07-12T17:07:39Z 2024-02-08T08:58:08Z "[https://support.apple.com/en-gb/HT207022 As of ios 11], Apple start using the HEIF format to save images. Sadly HEIF files can not be viewed in web browsers. For those taking images on their iPhone, this would mean to embed a raw iPhone photo, would require them to use a third party tool to convert that image into a web safe format like jpeg. WordPress core should convert this image to a web safe format while keeping the original for reference. " spacedmonkey Future Releases 48485 Custom image size not generated if identical to original size joedolson* Media 5.2.4 normal minor Future Release enhancement accepted 2019-11-03T09:31:22Z 2024-01-29T20:19:18Z "When defining a custom image size using `add_image_size` and uploading an image that has exactly the same dimensions of that image size, the new image size is not added. This also means that -- when adding the newly defined image size -- to the Insert Media screen using the `image_size_names_choose`-filter, the custom image size does not appear in the dropdown menu. Even though I can understand why this happens from a server load / storage point of view, I feel the unexpected behaviour (to end users) is a bigger problem. An even prettier fix would be to detect the custom image size is identical to the original size and map the custom image size URL to the original file URL (e.g. through a symbolic link). {{{#!php __( 'Project-foto' ), ) ); } add_filter( 'image_size_names_choose', 'custom_media_sizes' ); }}} " brampeerlings Future Releases 42829 Debugging image uploads with wp_generate_attachment_metadata Media normal normal Awaiting Review enhancement new 2017-12-07T14:24:22Z 2019-02-14T21:28:56Z "Because of the if statement declared in image.php on line 181 ([https://core.trac.wordpress.org/browser/tags/4.9/src/wp-admin/includes/image.php#L181]) it seems impossible to retrieve the error message, what is supplied by the wp_upload_bits() function. Please return this message or implement a new function what verifies what the error messages are trying to inform the user about." Fleuv Future Releases 39346 Display Error if GD library ins't installed/enabled Media 4.7 normal normal Awaiting Review enhancement new 2016-12-20T18:47:03Z 2018-01-04T18:55:29Z "I recently moved a website to a new server and ran the Regenerate Thumbnails plugin which ended up breaking my site because it couldn't generate the image sizes. Looking at their reviews there are a number of people bashing the plugin for breaking their sites because they do not have the GD library installed. I was very confused for awhile and I couldn't google the issue I was having but then remembered it required the GD library. This isn't an issue only directed at the plugin because when you upload an image it will only show the full size available which left me puzzled for awhile. I think if we could display an error in the media library after uploading an image that it failed to create the image sizes because of the missing PHP library that would be very helpful." stormrockwell Future Releases 43608 Display missing module error for GD when on Media Settings Media 4.6 normal normal Future Release enhancement new 2018-03-22T06:16:06Z 2019-04-15T18:22:33Z "When WordPress is installed on a server is [http://php.net/manual/en/book.image.php missing the GD PHP image library], there should be an admin level warning displayed on the Media Settings admin page. Without the GD module there will be '''no intermediate image sizes created when images are uploaded in the media library''' (the media gallery just uses the full image size by default) [https://pasteboard.co/Hd2hc9L.jpg Without Admin Notice] The Media Settings page should display an admin warning / error that tells the user that they're missing that module and without it no intermediate images will be created. The whole page talks about the various images size and without GD none of these settings will be used for anything. I've created a simple gist that displays an admin notice if the '''GD library isn't loaded''' and the current user is on the '''Media Settings''' page. [https://pasteboard.co/Hd2hVdk.jpg With Admin Level Notice] [https://gist.github.com/simonrcodrington/be60b6daae0b966a559878c4ba16d9d0] This has come up a few times now where images haven't been created in the media library and no one has known why. Sometimes hosting providers don't include this extension or they are just not loaded. Having an admin level notice here would make sense. " simonrcodrington Future Releases 40427 Expose a JavaScript API to extend the Media Manager Media 4.8 normal normal Awaiting Review enhancement new 2017-04-12T17:30:38Z 2021-05-20T20:29:03Z "After talking with @mikeschroder as Pressnomics about how hard it was to extend the media manager, I wanted to open the discussion here for ways we could improve that. One way I made it work for the Stock Photo plugins at GoDaddy was to override core bindHandlers (see https://github.com/godaddy/wp-stock-photos/blob/master/assets/js/stock-photos.manifest.js#L13) and register my new view. One problem with that approach is that it makes it hard for anyone else to extend it for themselves. I'm turning out to the community so we can discuss ways we could expose hooks that would let anyone extend any part of the media manager experience. This could pave the way for awesome new plugins." jonathanbardo Future Releases 39262 Fall back to ImageMagick command line when the pecl imagic is not available on the server Media 4.7 normal normal Awaiting Review enhancement new 2016-12-13T11:59:23Z 2019-05-16T13:22:06Z The patch allows WordPress to fall back to the ImageMagick command line when the imagic pecl is not available on the server. Patch attached. Hristo Sg Future Releases 40441 High server resource usage and timeouts during image uploads Media normal normal Awaiting Review enhancement new 2017-04-13T18:53:52Z 2017-04-14T14:25:12Z "When uploading an image, server resource usage can run high and the resize process can easily timeout causing the upload to fail. This is often down the creation of intermediate image sizes and is especially noticeable when plugins/themes have custom image sizes defined. This issue has been mentioned before in both #37840 and #36534. #40439 proposes saving the progress of intermediate image creation so resizing can be resumed on retry. This ticket is mainly for discussion around ways to reduce potential server implications when uploading an image and creating intermediate image sizes." enshrined Future Releases 54452 Image Aspect Ratio on resize Media 5.8.2 normal trivial Awaiting Review enhancement new 2021-11-16T10:54:08Z 2021-11-16T10:54:08Z "With the picture block the css resize the picture width but never the height so it break is aspect ratio. Just need to add a height: auto to .wp-block-image img ." edgarwes Future Releases 34367 Image Editing: Orientation-aware rotation icons Media normal normal Future Release enhancement reviewing 2015-10-20T05:38:51Z 2019-06-04T20:17:04Z "Having just processed a massive set of images and needing to rotate several of them, I noticed a small issue with the way the WordPress image editor's rotation icons work. They're generally much better than the standard rotation arrows you'd normally see, providing a visual of an image being rotated one way or another from portrait to landscape. But if you're looking at a landscape image that needs to rotate one way or the other, it's somewhat disorienting trying to decide which button to push, since you're essentially rotating it one more time past the orientation indicated in the icon. By contextually adjusting these icons to reflect the orientation of the image in the editor, we could eliminate an extra cognitive step during the image editing process (see proposed screenshots). Probably the easiest way to go about fixing this would be to add a class for the image's orientation somewhere in a container div, then add some css to rotate these buttons when the image is already landscape, so that they indicate that clicking would make them rotate into portrait orientation." celloexpressions Future Releases 53013 Improve media library grid management tools joedolson* Media normal normal Future Release enhancement accepted 2021-04-09T19:07:03Z 2023-10-18T16:18:07Z "The list view & the media modal both support bulk selection tools that aren't available in the media library's grid view. We should explore ways of moving the media grid view towards greater feature equivalence with these other views, including options such as: - One-click deletion - Select multiple items - View attachment titles (helps differentiate between two versions of an image) - Copy URL for attachment Prompted by #51363. While a custom context menu is not something we consider to be viable for accessibility reasons, the intent of that ticket is definitely worthwhile. " joedolson Future Releases 40123 Improve media uploading flow Media normal normal Awaiting Review enhancement new 2017-03-12T12:30:16Z 2019-01-14T17:54:02Z "Currently once you upload an image it just leaves you back at screen. We should consider on success offering next steps. We could use this as a chance to add encouragement: [[Image(https://cldup.com/sS6jT02xtn.PNG, 50%)]]" karmatosed Future Releases 39618 Insert PDF Thumbnail into Editor Media 4.7 normal normal Future Release enhancement new 2017-01-17T22:00:29Z 2019-12-09T15:38:51Z "[38949] is awesome, but the next logical move is to allow content editors to easily insert the PDF thumbnail into the Editor upon Insert Media. There will need to be a UI for allowing the content editor to choose whether to insert the image or the textual link. The easiest place for this to live without a major UI overhaul would be in the Insert Media workflow itself. In fact the ""Size"" pull-down menu doesn't really do anything right now for PDFs, so it would be a good place to add an option ""Document Link Only"", and then honour the other sizes when selected and actually insert the image. " tomauger Future Releases 42986 Insert default filters to wp_delete_file to don't delete core files. Media 4.9.1 normal normal Awaiting Review enhancement reopened 2017-12-27T11:57:51Z 2019-03-22T13:34:35Z " I am see many plugins that don't use wordpress method to delete files ( are using unink ) and exist wp_delete_file. Really you can insert filter, but I think that if didn't have filter by default you can use method to remove anything, including core files. If all agree and approve this ticket I can implement." lenon Future Releases 43023 Make Core Image Handling More Extensible Media 4.9.1 normal normal Awaiting Review enhancement new 2018-01-04T21:35:41Z 2020-08-21T03:34:07Z "As we are beginning to see many new and promising formats such as WebP (#35725), APNG, and HEIF/HEVC (#42775), it is probably time to revisit all of the image-related code in the Core, providing filters and hooks so that plugins and themes can choose to support them. Based on the work in #35725, it is clear there are a number of areas with insufficient extensibility, making it impossible for such work to be done by third-party code. [[BR]] '''WRAPPERS''' `getimagesize()`: Due to various bugs and inconsistencies within PHP, direct calls to this function should be replaced with a wrapper function capable of providing filtered responses. #35725 includes this in its patch. [[BR]] '''FILTERS''' Many functions include hard-coded datasets or conditions. By wrapping those in filters, third-party code can alter behavior accordingly. * `wp_stream_image()` * `wp_save_image_file()` * `wp_generate_attachment_metadata()` - The extensions-by-type need to be filterable. * `load_image_to_edit()` - The $mime_type switch needs a filterable default. * getid3.lib.php `ImageTypesLookup()` - Types need to be filterable. * class-phpmailer.php `_mime_types()` - Types need to be filterable. * image classes `supports_mime_type()` * class-wp-theme `get_screenshot()` - Filterable types. * `gd_edit_image_support()` - Filterable responses for both conditions. * `translate_smiley()` - Needs filterable types. * `wp_get_image_mime()` * `wp_attachment_is()` - Filterable extensions. * `wp_mime_type_icon()` - Filterable test for image files. [[BR]] '''OTHER''' There are additional areas that require more complicated solutions. * `file_is_displayable_image()` - Relies on constants which may not be defined, even in cases where an image type is actually supported. Haha. * wp-admin/includes/schema.php - $misc_exts needs to be filterable. * class-wp-image-editor-gd `load()` - Needs a filter around the resource creation. `imagecreatefromstring()` does not work consistently depending on the GD version installed. * class-wp-image-editor-gd `_save()` - Needs a filter to handle alternative MIME types. * class-wp-image-editor-gd `stream()` - Needs some means of specifying alternative headers and callbacks. * class-wp-image-editor-imagick `thumbnail_image()` - Needs some means of specifying options for different image types. * class-wp-image-editor-imagick `stream()` - Needs a shortcut filter to allow for completely different handling. (This is a quirk of the PHP extension not always properly communicating with the system binary, leading to segfaults, etc.) * class-wp-customize-media-control `to_json()` - Needs some method of altering the $type matching. [[BR]] '''ROADBLOCKS''' Additional requirements, such as defining missing PHP constants, might not be possible by the time plugin or theme code is executed. However by the time official PHP support lands, we can probably consider adding such values to the `compat.php` file (without necessarily providing a full blessing for the filetype within the Core)." blobfolio Future Releases 32622 Make the text of the Image delete AYS dialog clearer Media 4.3 normal normal Awaiting Review enhancement new 2015-06-12T02:30:01Z 2017-06-15T09:53:56Z "When you delete Images from the Media Library, the warning dialog currently reads: ""You are about to permanently delete the selected items."" This text could be a little clearer, and indicate that, once deleted: - Attached Images will not be visible in any Posts or Pages they are attached to. - Both Attached and Unattached Images will not be available online at all." lastnode Future Releases 40120 Media on mobile action links missable Media normal normal Awaiting Review enhancement new 2017-03-12T12:19:47Z 2017-03-16T19:45:14Z "The following is how on an iPhone 7 Plus the media interaction links look: [[Image(https://cldup.com/TLmN2U_8fW.PNG, 50%)]] They are smaller than the body text and also very missable at the bottom. Can we at least increase their size and see about moving to top?" karmatosed Future Releases 40124 Media on uploading only gives me edit options Media normal normal Future Release enhancement new 2017-03-12T12:32:20Z 2023-09-05T15:07:41Z "This shows on mobile but is also desktop issue. [[Image(https://cldup.com/_ZB6QmO5gZ.PNG, 50%)]] Says 'edit' but doesn't give me option to view or delete." karmatosed Future Releases 43227 Media uploaded to post should remove underscores and hyphens from text inserted into title attribute Media normal normal Future Release enhancement new 2018-02-05T11:04:43Z 2023-02-02T16:29:19Z "When adding a new image into a post my file name will typically be called something like: descriptive-name-of-image.jpg Once this image is uploaded wp will automatically set the title and will default to the name of the image ""descriptive-name-of-image"" if no title meta data is available in the image. I think a better default action would be to replace the hyphens/underscores with spaces and possibly capitalising the first letter making the title ""Descriptive name of image""." mrmadhat Future Releases 40403 Media: Allow disabling of auto-save for attachment changes in Media Library Media normal normal Awaiting Review enhancement new 2017-04-10T18:57:38Z 2017-10-16T06:45:09Z "When in the select frame of the media library and the user has selected an attachment, the fields for that attachment including the title, caption, and description can all be modified. The user may very well be expecting that the changes they are making to be ''localized'' to the current context for which they are inserting the image. For example, a user may want to provide a unique caption for an image when selecting it into one post vs the caption for the image when it is inserted into another post. Nevertheless, when the user does make a change to the caption, it will get written into the underlying `attachment` post and will thus change the caption on the `attachment` single template and any galleries in which the image appears. These are the fields in question: [[Image(attachment-fields-in-media-library-select-frame.png, width=400px)]] All of this to say that the behavior to auto-save back changes to an attachment as changes are made in the media library should be able to be disabled, or should perhaps be disabled by default if not in a management context on the Media admin screen. Also, when the media library is opened in the customizer, a user should expect all changes to be previewable without impacting the site before hitting Save & Publish. The customizer is supposed to guard against the “save and surprise” experience. In the case of the Media Library, it can be even worse because it is “auto-save and surprise” and the auto-save behavior isn't even stated. So if auto-save isn't disabled by default in the media library across WordPress in a non-management context, then at least it seems it should be disabled in the context of the customizer. The conversation for this started in the context of the image widget, and unexpected behavior for when modifying fields in the select frame versus modifying fields in the edit frame (which, as in the edit post screen, do not auto-save but are local to the post being edited). See https://wordpress.slack.com/archives/C0381N237/p1491845195064777 See also #37887, which would still allow for changes to be made in the media library, but for the changes to defer to being published until the user hits Save & Publish in the Customizer. " westonruter Future Releases 41409 No point in storing empty EXIF/IPTC data on post meta table Media 4.9 normal normal Awaiting Review enhancement new 2017-07-22T15:37:02Z 2019-01-31T21:49:00Z "- Post meta tables are bloated with often not used EXIF/IPTC data for each image attachments. - `wp_read_image_metadata()` generates `aperture`, `credit`, `camera`, `caption`, `created_timestamp`, `copyright`, `focal_length`, `iso`, `shutter_speed`, `title`, `orientation`, `keywords`. and the data often stored as empty key/value pairs on each attachment metadata. - I see no problem on filling default/empty values upon retrieving the data. - and mentioning the core currently has no way of using ''stored'' `image_meta`." geminorum Future Releases 30876 Paste an image into the Media Library Media normal normal Future Release enhancement new 2015-01-01T00:12:16Z 2018-03-30T22:44:19Z Github has some nice UX where you can paste an image into a comment. It would be nice if the Media Library supported something similar. danielbachhuber Future Releases 22938 Presentation of hierarchical taxonomy in Media modal should be checkboxes rather than comma-separated tag list wonderboymusic Media 3.5 normal normal Future Release enhancement assigned 2012-12-14T14:10:16Z 2018-09-24T08:07:27Z Since 3.5, using register_taxonomy_for_object_type on attachments, if the taxonomy used is hierarchical, whereas in the edit attachment UI you see the normal list of checkboxes, in the corresponding modal it is presented as a comma-separated list of slugs, as if it were a non-hierarchical taxonomy (tags rather than categories). I'm sure this is not a bug / mistake / oversight, but at best it's a little unintuitive (you need to have memorised the category slugs to add new ones) and worst a bit dangerous (risk of adding unwanted categories), and it would be great if in future it was presented here too as a list of checkboxes. yeswework Future Releases 41462 Promote media details admin page to full post page Media 4.9 normal normal Future Release enhancement new 2017-07-27T17:43:26Z 2023-10-18T16:01:34Z "Currently when editing media metadata, you either get the modern library modal with the image on the left and various fields on the right. When you click ""Edit more details"" you get a blast from the past with an old-school version of WordPress admin where everything looks uninspired and, for new users, broken. Based on user feedback it turns out some site owners use the Attachment Page feature to provide contextual info, commenting, etc for media items. One example was a teacher who uploaded student images to a gallery, then had each image link to the attachment page where further information and images were provided in the ""description"" field (so the post content) and parents could leave comments. Since media items in reality are full fledged posts with their own post content, the media details admin view should be upgraded to a full post page with proper WYSIWYG editing for the Description field, custom fields, and ability to control things like commenting. This would also be an ideal place to visualize in what posts a media item is in use across the site." mor10 Future Releases 35094 Replace static with Dynamic Image Sizes for inserted images Media normal normal Awaiting Review enhancement new 2015-12-15T02:27:38Z 2018-08-16T20:36:21Z "== Proposal == Change the behavior of the add image size selector from hard-coding `width` and `height` attributes to adding size-based classes to the `` element to allow theme authors to define what Thumbnail, Small, Medium, and Large means. This creates Dynamic Image Sizes that change and adapt when a site owner switches from one theme to the next. === Practical Implementation === - Create new theme feature for dynamic-images - When an image size is selected (eg. ""medium""), the a class formatted as `size-[selected-size]`, (eg. `size-medium`) is added to the `` tag. - Theme developers add CSS rules for `.size-thumbnail`, `.size-small`, `.size-medium`, and `.size-large`. These rules can define whatever parameters the theme developer desires, but must include either `width`, `max-width` or both. Theme developers are also free to use media queries to change this behavior depending on viewport width. - '''Ideal, optional:''' Remove the `width` and `height` attributes from `` markup as they serve no practical purpose once RICG and class-based sizing is implemented. == Rationale == With Responsive Images in core, the modality of the image size selector no longer makes sense. The image size selector hard-codes pixel sizes to images added in posts and pages based on the physical width and height of the image file, but with the new srcset + sizes markup, these image sizes no longer have a real world rationale as the browser selects the image source dynamically. I propose a change in what happens when an image size (thumbnail, small, medium, large, original) is selected from a pre-defined pixel size to a dynamic size defined by the current active theme. This would allow theme designers and developers to add image sizes as part of their art direction and design, and displayed image sizes would change depending on the current active theme without the site owner having to make changes to individual images to make them fit. In simple terms, move from this: [[Image(http://mor10.com/wp-content/uploads/2015/06/Slide1-700x394.png)]] to this: [[Image(http://mor10.com/wp-content/uploads/2015/06/Slide2-700x394.png)]] == Backwards Compatibility == This has the potential of being a breaking change. The most obvious solution would be to make dynamic image sizes a `theme feature` along the lines of html5 comments and title-tag: {{{ add_theme_support( 'dynamic-images' ); }}} == Practical Application == This change would work within the existing framework of how WordPress adds images because the only practical change in the actual post/page is the addition of a new class in the `` tag. To apply to existing posts and pages, the classes could be added by piggybacking off the dynamic rewriting of the `` element done by Responsive Images. == Challenges == - Some authors physically resize images to fit a specific display. This in itself is a problem because it counteracts the responsive nature of the web, but it is a fact that must be considered. An implementation of Dynamic Image Sizes could cause some authors to be frustrated that their carefully sized images suddenly change display. This would likely only happen on old static-width sites as properly built themes with RWD would already override such forced sizing except for the full-width versions of images. - Currently an author can use click-and-drag behaviors to resize an image in the editor. This would be hard to replicate using the proposed CSS model, but is not impossible: One solution could be generating inline CSS for custom image sizes, and possibly adding a .size-custom class to the `` tag. Another clearner option could be to remove the click-and-drag resizing option and instead provide percentage-based options. When discussing this it is important to note that such forced click-and-drag resizing goes against the natural behavior of images in a mobile-first RWD environments." mor10 Future Releases 40869 Replacing an image in content editor Media 4.7.5 normal normal Awaiting Review enhancement new 2017-05-26T10:42:10Z 2017-05-26T13:36:33Z "Hello, I noticed a strange behaviour in WordPress User Experience while dealing with images. Let's say for example you want to replace an existing image in the content editor while creating or editing a post/page. Right now this is only possible when this 'existing' image is part of your Media Library and probably has an attachment post_id. What about people that have added images from external urls or maybe even placeholder images that have been adding to their content via custom TinyMCE buttons. When you press Edit on those images you can't easily replace them for an image inside your Media Library. I think this is a little odd and we should be able to replace any image in our editor for one inside our library so I made this little change what will make the 'Replace' button always show up in the Image Details modal. /wp-includes/media-template.php :line: 885 {{{
    <# if ( data.attachment && window.imageEdit ) { #>
    "" /> "" />
    <# else if ( data.attachment && window.imageEdit ) { #>
    "" />
    <# } #>
    }}} **Todo. While adding a new image to the editor we get a small JavaScript error. " MacPresss Future Releases 22966 Show admin-cropped thumbnails instead of WordPress-cropped thumbnails Media normal normal Awaiting Review enhancement new 2012-12-16T22:22:59Z 2023-08-29T15:35:39Z "Used to be able to see which images have been cropped (and which ones haven't) in image search results. Now have to click 'edit image' and check the image individually. It's valuable for the publisher to see what his/her readers will see on the front end of the site when the 'thumbnail' function is called (either publisher's hard-cropped image or full un-cropped image). Useful especially for publishers that are pulling images from a time before 'thumbnails' existed in WP. Main reason this is an issue is that when an un-cropped thumbnail is selected as the featured image, it will be stretched/distorted to dimensions of thumbnail settings in function.php." beerpulse Future Releases 49830 Store rotation data for uploaded videos Media normal normal Future Release enhancement new 2020-04-06T17:44:17Z 2022-03-10T15:57:25Z If the video format supports and the data is found in the exif data, store the rotation angle in video metadata. spacedmonkey Future Releases 46554 Uploaded images goes to wrong folder/date structure antpb Media 5.1 normal normal 6.6 enhancement assigned 2019-03-18T11:24:37Z 2024-02-12T09:21:41Z "Hello Team All test are from fresh install, default theme, no settings change, no plugin… ""Organize my uploads into month- and year-based folders” option checked. Images upload date: 17/03/2019 Single “Test Page” published date: 27/11/2018 In WordPress 4.7 – 4.7.13 – 4.8 – 4.8.9: images uploaded from Media Library goes to …/2019/03 folder… RIGHT images uploaded from single “Test Page” goes to …/2018/11 folder… RIGHT In WordPress 4.9 – 4.9.10 – 5.0.4 – 5.1.1: images uploaded from Media Library goes to …/2019/03 folder… RIGHT images uploaded from single “Test Page” goes to …/2019/03 folder… WRONG!!! From 4.9 version has anything changed in the way WordPress handles image uploads? If YES, how to go back to the old way (thus images uploaded from single “Test Page” goes to “published date” folder… and not to “upload date” folder)? Thanks!" kartiks16 Future Releases 39330 WP_Image_Editor_Imagick: get pdf from url Media 4.8 normal normal Awaiting Review enhancement new 2016-12-19T13:59:58Z 2024-01-16T13:00:28Z It is not possible to use the class, if an url is passed as filepath. With this little patch it is possible (I know it's not perfect. Maybe someone can make it better) wordpressrene Future Releases 59421 "loading=""lazy"" attribute is not applied at all" Media 6.3.1 normal minor Awaiting Review enhancement new 2023-09-21T06:54:52Z 2023-09-27T13:46:58Z "Steps to reproduce: Start new WordPress 6.3.1 instance. Use default twenty-twenty-three theme. Create new post. Insert some images. None of the images (including below the fold ones) get loading attribute. It is expected that below the fold images get loading=""lazy"" attribute." lovor Future Releases 39791 sanitize_file_name() optimizations Media 4.8 normal normal Awaiting Review enhancement new 2017-02-05T23:24:33Z 2018-01-20T13:49:47Z "This changeset: [29290] added this line: {{{#!php $filename = str_replace( array( '%20', '+' ), '-', $filename ); }}} But because of this changeset it can be removed as those chars aren't present anymore: [35122] '''Additional proposals''' 1.) After many years new special characters are added step-by-step to sanitize_file_name(). Now almost all characters of the reserved file system, reserved URI and unsafe URL characters lists are part of it, except of: reserved file system chars (https://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words) {{{ chr(0), ..., chr(32) }}} the reserved URI char (https://tools.ietf.org/html/rfc3986#section-2.2): {{{ @ }}} the unsafe URL char (https://www.ietf.org/rfc/rfc1738.txt): {{{ ^ }}} non-printing DEL: {{{ chr(127) }}} Finally you should add all these chars to avoid future bug reports: {{{#!php $special_chars = array( // file system reserved https://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words '<', '>', ':', '""', '/', '\\', '|', '?', '*', // control characters http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx // note: \t, \n and \r are chr(9), chr(10) and chr(13) chr(0), chr(1), chr(2), chr(3), chr(4), chr(5), chr(6), chr(7), chr(8), chr(9), chr(10), chr(11), chr(12), chr(13), chr(14), chr(15), chr(16), chr(17), chr(18), chr(19), chr(20), chr(21), chr(22), chr(23), chr(24), chr(25), chr(26), chr(27), chr(28), chr(29), chr(30), chr(31), // non-printing character chr(127), // non-breaking space chr(160), // URI reserved https://tools.ietf.org/html/rfc3986#section-2.2 '#', '[', ']', '@', '!', '$', '&', ""'"", '(', ')', '+', ',', ';', '=', // URL unsafe characters https://www.ietf.org/rfc/rfc1738.txt '{', '}', '^', '~', '`' ); }}} If you do that, do not forget to change this line: {{{#!php $filename = preg_replace( '/[\r\n\t -]+/', '-', $filename ); }}} to that (because we replaced the other chars already): {{{#!php $filename = preg_replace( '/[ -]+/', '-', $filename ); }}} and remove this line because we cover it already through chr(160): {{{#!php $filename = preg_replace( ""#\x{00a0}#siu"", ' ', $filename ); }}} Source: https://en.wikipedia.org/wiki/Whitespace_character#Unicode 2.) mb_strtolower() could be used to raise windows/unix interoperability (when downloading ftp backups or moving the host) because of their different behaviour in case-sensitivity. " mgutt Future Releases 40915 wordpress should issue a warning if no graphic library is installed Media 4.7.5 normal normal Awaiting Review enhancement new 2017-06-03T14:58:23Z 2017-06-10T07:07:59Z "Hi people! I've installed wordpress on my site, and I had no library for image manipulation installed. Iin that case, I got no thumbnails. Due to css of my site, I was not initially aware of my site, cause the layout was right. So, I think that a warning on admin to the ones that don't have GD or imagick installed could be a good thing. I know that this is a strange corner case :)" waltercruz Future Releases 43263 wp_audio_shortcode() preload default: should it be metadata or none? Media 3.6 normal normal Awaiting Review enhancement new 2018-02-08T19:17:59Z 2018-02-08T19:45:50Z "Using this ticket to open a discussion about the `audio` tag’s `preload` attribute defaulting to `none` in `wp_audio_shortcode()`. `none` won’t display the audio’s total time in the player (until the user hits play). So the effect of this default is millions of sites’ players display total times of “00:00”. (You can specify preload as a shortcode attr, but most sites don’t. ) Setting the `preload` attribute to `metadata` does extract and display total time upon page-load. Also `metadata` is both the `wp_video_shortcode()` default and the HTML-spec suggested default (to browser makers): https://developer.mozilla.org/en-US/docs/Web/HTML/Element/audio#attr-preload Bandwidth might be the valid concern, tho, as some browsers preload an excessive amount of metadata (I'm looking at you, Chrome) . See results of tests by @blobfolio: https://wordpress.slack.com/archives/C02SX62S6/p1518116191000138 FYI, the default `'preload' => 'none'` is here: https://core.trac.wordpress.org/browser/tags/4.9/src/wp-includes/media.php#L2223 FYI-2, you can change that with the `wp_audio_shortcode` filter (via regex on the HTML output): https://gist.github.com/hearvox/098774e9887442d39ddc6e34bedb10b1" hearvox Future Releases 41895 wp_calculate_image_srcset filter: Improve the documentation for, or rename, this filter so it's clear it should work on an array. Media 4.9 normal normal Awaiting Review enhancement new 2017-09-16T18:29:18Z 2017-09-16T20:25:06Z "= The Problem = Despite having the same name as the `wp_calculate_image_srcset()` function and being inside of that function the `wp_calculate_image_srcset` filter, [https://core.trac.wordpress.org/browser/tags/4.8.1/src/wp-includes/media.php#L1203 here in the current release], does not directly modify the output of the function as convention would dictate. This leads to confusion, so theme and plugin developers do things that lead to bugs. The `wp_calculate_image_srcset` filter filters the `$sources` variable, which is an array of arrays, each containing information about one of the image sources that WP has decided to add to the srcset. However the `wp_calculate_image_srcset()` ''function'' returns either a string HTML [https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img srcset attribute for use on an img tag] or false if there's only one source or some other failure. Because the `wp_calculate_image_srcset()` ''function'' can return false, developers assume that `wp_calculate_image_srcset` filters can return false as well, thus converting the `$sources` array into a boolean `false`. This causes a problem when a second plugin or theme also tries to filter `wp_calculate_image_srcset` and tries to loop over the values in `$sources`, (`foreach( false)` causes a PHP warning). = Real-World Examples= This is happening in the real world: If you're hosted on WPEngine, and use Themeco's X or Pro theme, the PHP warning pops up in some of your pages, (especially in WPEngine's staging environment). This is because X and Pro use `wp_calculate_image_srcset` to change `$sources` to false, then WPEngine's Must-Use plugin tries to iterate over `$sources`. When contacted about the problem, (with the suggestion they return an empty array), Themeco's response was ""In looking over WordPress' official documentation for that function/hook, I believe that boolean false should be the correct value to return"" with a link to the documentation for the ''function''. When the issue was raised in the the [https://www.facebook.com/groups/advancedwp/ Advanced WP Facebook Group] a prominent member of the WP community [https://www.facebook.com/groups/advancedwp/permalink/1624922314236643/?comment_id=1625126477549560&reply_comment_id=1625763707485837¬if_t=group_comment_reply¬if_id=1505579798429304 appears to have made the same logical jump], that the filter filters the output of the function, and wouldn't listen to any further discussion. = Possible suggestions to improve the situation = 1. If we're ok with setting `$sources` to false, the docblock for the `wp_calculate_image_srcset` filter should be changed to indicate that the `$sources` variable being passed to a filter may not be a variable. 2. If we're not ok with setting `$sources` to false, maybe we should add a `_doing_it_wrong()` if `$sources` type is changed from an array. 3. Whatever we do, we should document an expected return type in the docblock for the filter. 3. Since the filter doesn't actually filter the output of the function, the filter name could be changed to something like `wp_calculate_image_srcset_sources`. I know this is a breaking change, which may never happen because it's a breaking change, but it would be the best fix, if breaking changes can be dealt with." johnnyb Future Releases 30377 wp_check_filetype is broken when checking urls with parameters audrasjb Media 4.0 normal normal Future Release enhancement reopened 2014-11-18T05:05:03Z 2022-04-08T04:24:45Z "The function in ./wp-includes/media.php named wp_check_filetype has a bug. It works properly when checking a url such as http://example.org/coolfile.mp4 but as soon as you add parameters to it (a common practice when attempting to embed un-cached or amazon pre-signed urls) like so: http://example.org/coolfile.mp4?extra=true¶ms=true ... it fails to return the extension / content type. The fix for this should be *very* easy. The preg_match in this function that looks like this currently: {{{ $ext_preg = '!\.(' . $ext_preg . ')$!i'; }}} could be adjusted to ignore the query string (if there is one) and just return the true extension like so: {{{ $ext_preg = '!\.(' . $ext_preg . ')(\?.*)?$!i'; }}} I've tested this change in my local environment and it works great. " supercleanse Future Releases 30180 wp_get_attachment_image_src does not return alt or meta antpb Media normal normal Future Release enhancement assigned 2014-10-29T18:42:55Z 2023-07-21T15:37:32Z "In practical use,wp_get_attachment_image_src is very useful for displaying an attached image - but requires a separate call to get any other image meta or the alt attribute. In addition to making any application that needs alt attr or meta data for display simpler, having the alt attribute present in this function increases the likelihood that developers will use the alt attribute in their ultimate output. " joedolson Future Releases 41279 Make PDF Thumbnail (WP 4.7 feature) accessible via the Media Manager Media normal normal Awaiting Review feature request new 2017-07-09T19:24:26Z 2020-10-21T12:55:14Z "When you upload a PDF file WordPress creates a ""preview image"" - This was added as of WP 4.7 This feature request to have that image also added into the database so that it is accessible via the Media Manager. The use case for this feature is that I have a Monthly Newsletter and want to use the preview image (page 1 of the PDF) as the featured image for the post where I am putting the link to the PDF Additionally some plugins (like visual composer) allow you to insert single images, however, you need to be able to select it from the media manager, not just put in a URL" sflwa Future Releases 19834 More Robust Capabilities for Attachments Media normal normal Awaiting Review feature request new 2012-01-15T00:43:40Z 2020-09-10T14:05:33Z "Attachments/files should have their own set of capabilities mirroring those of posts, in addition to upload_files. Specifically: - read_attachments - edit_attachments - edit_others_attachments - delete_attachments - delete_others_attachments Currently, attachments rely on the edit_posts capability, which can create complications if you don't want your users to see the ""Posts"" sidebar item, or don't want them to be able to delete the attachments they upload. " walkinonwat3r Future Releases 42633 Suggestion to provide Better Page and Image Management Media 4.9 normal normal Awaiting Review feature request new 2017-11-20T03:41:59Z 2017-11-20T05:24:14Z "**** This is not bug report but a suggestion **** Not at all sure if this is the right place for this however, I've been using wordpress for about 12 months now and believe it lacks somewhat in the management of pages and media. I believe that it would help tremendously helpful if we could: (1) organize pages into groups or folders as it can be overwhelming with the current long list of pages when we are working on large sites with a lot of pages, and (2) similarly, organize media into folders so for example, we could keep site media separate from post media. Thanks for listening" sixlinksrule Future Releases 40140 upload_url_path doesn't seem to make any effect Media 4.7.3 normal normal Awaiting Review feature request new 2017-03-13T06:53:00Z 2018-12-27T21:15:21Z "An site of mine had '''http://site.com/articlefiles/''' as the place to receive uploads, equally it was '''/site/root/articlefiles''' on the filesystem, instead of '''/site/root/wp-content/uploads'''. Now I migrated the site into a multisite installation as site 2 and uploads are going into /site/root/articlefiles/site/2/ and all previous uploads in old posts are linked as '''http://site.com/articlefiles/site/2/something.jpg''', causing broken images and links cause they originally don't have the ""site/2"" part. Editing the post, these links and images do not have the ""site/2"" part either. WordPress is rewriting the URL dynamically when reading the posts. I want to keep compatibility with '''http://site.com/articlefiles/''' and '''/site/root/articlefiles''' without the ""site/2"" part. I was expecting '''upload_url_path''' on options table to be the solution but it doesn't work. I put there '''http://site.com/articlefiles/'''. How can I keep URL and path compatibility when migrating a single site to a non-primary site of multi site installation ? Thank you in advance" avibrazil Future Releases 43494 Can't change/delete menu items in Customizer on mobile audrasjb* Menus normal normal Future Release defect (bug) accepted 2018-03-07T23:30:18Z 2023-01-06T12:25:28Z "On mobile/tablet browser (only Android, Chrome browser tested), menu items can be added and reorganized, but the drop-down toggle for further options doesn't work. As a result menu items cannot be removed. To reproduce: 1. Log in to admin in mobile / tablet browser 2. Go to Customizer -> Menus 3. Add menu item to a menu 4. Attempt to edit / delete menu item Originally reported by community user Sue Jenkins on Twitter: https://twitter.com/LuckychairNews/status/969682449176211456" mor10 Future Releases 53449 Child Walker classes change the $args parameter data type and default value signatures for start_el and end_el Menus normal normal Awaiting Review defect (bug) new 2021-06-18T15:54:35Z 2023-08-03T21:38:00Z "The following Walker classes have code smells for changing the data type of the `$args` parameter when extending from the `Walker::start_el` and `end_el`: - `Walker_Nav_Menu` - `Walker_Nav_Menu_Checklist` - `Walker_Nav_Menu_Edit` What is the code smell? The parent defines the `$args` parameter as an `array` data type with a default value of an empty array. The child classes change the parameter's data type to `stdClass` with a default value of `null`. These changes need investigation to determine if these changes are needed and why." hellofromTonya Future Releases 14142 Custom Walker class for navigation menus Menus 3.0 normal normal Future Release defect (bug) reopened 2010-06-29T14:16:18Z 2019-04-19T18:31:41Z "I have tried to extend the Walker_Nav_Menu class, I just needed to overwrite the start_el method. So i added ""walker""=>""My_Walker"" to wp_nav_menu, I've got an error message, that the method ""walk"" could not be accessed statically. After a short look at the code in ""nav-menu-template"", I realized that in the method ""walk_nav_menu_tree"" the object initializer ""new"" is missing. My solution can be found in the attached file. As you can see, I've just added a ""new"" in front of $r->walker And it works" dennis.winter Future Releases 58044 Issue with wp_setup_nav_menu_item Menus 6.2 normal normal Awaiting Review defect (bug) new 2023-04-01T16:20:53Z 2023-04-08T14:55:59Z "`/wp-includes/nav-menu.php` has an issue handling bad `$menu_item`. The problem is with trying to call `get_post_status()`. If a post with type `nav_menu_item` has a problem (I think not having a correct parent or something), the call to `get_post($menu_item->object_id)` returns NULL which then causes an error message from `get_post_states()`. I had to search the site database to find the offending menu item on my theme development site and deleted the bad menu. I think I likely deleted a page or post that had been include in a menu definition, or perhaps it was because I typically use the Parent Page to define the default menu, which is still supported but seldom used. This error only seems to appear when using the Customizer, I'm guessing while it is generating the ''Menus'' option. Didn't get error from Dashboard Menu, nor have I tried this on a block theme. The problem is found around line 833 in `nav-menu.php`. Here's a possible fix which worked with my bad menu definition, but the problem might be deeper. {{{#!php type_label = $object->labels->singular_name; // Denote post states for special pages (only in the admin). if ( function_exists( 'get_post_states' ) ) { $menu_post = get_post( $menu_item->object_id ); /* * Suggested fix for bad nav_menu_item post - likely caused by now missing parent * which can result in $menu_post being NULL at this point * */ if ($menu_post != NULL) { //*** add a NULL check $post_states = get_post_states($menu_post); if ($post_states) { $menu_item->type_label = wp_strip_all_tags(implode(', ', $post_states)); } } // end of added NULL check } } else { $menu_item->type_label = $menu_item->object; $menu_item->_invalid = true; } }}} " wpweaver Future Releases 18271 Item hierarchy should be maintained when adding to menu Menus 3.2.1 normal minor Future Release defect (bug) new 2011-07-27T20:13:35Z 2023-11-17T10:54:16Z "Situation: Create a hierarchy of categories or pages and go to create a custom menu. In the meta boxes on the left hand side, the categories and pages are shown in hierarchical arrangement. Select all categories (for example) and add to menu. Expected behaviour: All links are added to custom menu and the hierarchy is maintained appropriately Actual behaviour: Hierarchy is lost and all menu items are top-level This was originally raised by Jane in #17029 however the changeset in the ticket only applies to showing hierarchy in the meta boxes and doesn't cover maintaining hierarchy when adding to menu." JohnONolan Future Releases 47436 Menu depth doesn't affect menu-item-has-children Menus 5.2.1 normal trivial Awaiting Review defect (bug) new 2019-05-30T17:19:32Z 2021-08-21T22:47:18Z "Hi, When you add a depth of 1 to wp_nav_menu it removes all the sub menus, but it leaves menu-item-has-children class on the original menu li tags, which means it is styled like it has a dropdown." mikeybinns Future Releases 37971 Menus screen: improve the responsive view Menus normal normal Awaiting Review defect (bug) new 2016-09-07T17:30:27Z 2019-04-05T19:01:01Z "Noticed while working on #37969, the responsive view of the Menus screen needs some improvements. Not sure if there's already a specific ticket (haven't found one). Some CSS rules used in this screen work just in the ""Desktop"" view: 100% widths+margins, some floats, the `13em` spacing between menu item titles and controls and probably more stuff need to be reset/adjusted. Not sure it nesting the menu items can work on very small displays, probably needs a different approach. Any thoughts welcome! [[Image(https://cldup.com/qvBPJULT7f.png)]]" afercia Future Releases 41351 Searching for a category returns nothing if category is empty Menus normal normal Awaiting Review defect (bug) new 2017-07-17T21:53:56Z 2019-11-22T21:53:08Z "Hi, In the navigation menu creation page, when you are trying to add a category to the menu, if the category is empty, it won't show up in the search results. However, if the category itself is empty but has a child that is not empty, it will still be shown. I have a blog with over 500 categories, and I'm trying to add some of them to the menu but they have no posts yet. Navigating through category list is going to take time, and is also frustrating. Now I've tracked down the issue to `/wp-admin/includes/nav-menu.php`, ( starting at line 588 ) but can't find a filter or hook to do so. This line (109) seems to be responsible for doing the search: {{{ $terms = get_terms( $matches[2], array( 'name__like' => $query, 'number' => 10, )); }}} According to the documentations, this function accepts an argument for showing empty terms 'hide_empty' => false, but I can't see such option in this part of core's code. I've added this option to the core (temporarily) to see if it solves the issue, and it does. The other `get_term()` functions withing this template file mostly use `'hide_empty' => false` so I'm not sure either this one was overlooked or not, I tagged this as a bug though." jackjohansson Future Releases 38801 Terms with the same name indistinguishable in Menu section Menus normal normal Future Release defect (bug) new 2016-11-15T19:10:08Z 2017-08-18T12:52:07Z "== Problem == Let's say we have a WooCommerce site (although likely all taxonomies/terms are liable to this problem) with the following categories: Men, Women. Each of the categories has a subcategory called Shoes. When in Appearance -> Menu and trying to add a link to Shoes (whichever), there's no way to distinguish the 2 Shoes categories, as the parents are not displayed and no indenting is applied. No matter if we use the Latest, All or Search filter. == Solution == Keep in mind that ""All"" uses pagination, so indenting might not be the best solution. An idea is a hover with the parents listed, but this would be tricky on mobile. Maybe just make a ""Show parents"" switch above the field (or in the Screen Options) and if it's checked, show the parents after the taxonomy/term's name? Like: Shoes (Women -> Shoes). Just getting rid of pagination in the ""All"" view could cause problems with a lot of values and would not help the Search function within the menu creator." eclare Future Releases 39056 Twenty Seventeen: No Default Menu option creates extra work Menus 4.7 normal normal Awaiting Review defect (bug) reopened 2016-12-04T17:28:41Z 2018-03-05T13:42:50Z "A new WordPress site is created with a sample post, and sample page. In previous themes, there was a menu with Home and Sample Page listed, which was nice to see where the menu lives, and preview what a page looks like. On Twenty Seventeen there is no default menu. This prevents me from both identifying where those links would be, as well as not allowing me to view the Sample Page." ElfIRL Future Releases 43033 User can not see updated Icon in editing Menu with live preview Menus 4.9.1 normal normal Awaiting Review defect (bug) new 2018-01-06T06:48:54Z 2018-02-05T14:06:38Z "Bug: User can not see updated Icon in editing Menu with live preview Attachment for steps: https://www.screencast.com/t/jOBHlmVeUTdO Steps: 1. Navigate to Appearance->Menus from left rail 2. Select ""Menu with Live preview"" 3. Select Menu and click on 'Add Items"" 4. Sect ""Pages"" and add some page, User can see that ""+"" icon is changed to Tickmark sign 5. User will remove it from menu,Now User can not see previous symbol again to add Thanks" nilamacharya Future Releases 42288 Validation of custom menu link Menus 4.8.2 normal normal Awaiting Review defect (bug) new 2017-10-20T05:38:04Z 2018-06-14T13:40:20Z "1. go to menus page 2. try to add custom menu link with label only. without a URL. expected and actual result: validation failed and link cannot be added. 1. go to menus page 2. add custom menu link with label and URL: '#' 3. save menu 4. edit the custom link from the menu and remove the URL. 5. click save expected result: validation failed and menu won't be saved. actual result: menu saved. no validation." dvirhazout Future Releases 40090 Walker::display_element does not populate $args[0]->has_children when it is cast as an Object Menus 4.7.3 normal normal Awaiting Review defect (bug) new 2017-03-09T23:39:09Z 2017-03-10T00:38:08Z "When using the various hooks in {{{Walker_Nav_Menu}}}, the {{{$args}}} argument is expected to have a {{{has_children}}} object property. Walker::display_element only creates and populates this property if {{{$args[0]}}} exists and is an array. {{{#!php has_children = ! empty( $children_elements[ $id ] ); if ( isset( $args[0] ) && is_array( $args[0] ) ) { $args[0]['has_children'] = $this->has_children; // Back-compat. } }}} But {{{wp_nav_menu()}}} casts $args as an object ensuring that this assignment will always fail. = Suggested Fix = Add an additional check for object type and assign appropriately. {{{#!php has_children = ! empty( $children_elements[ $id ] ); if ( isset( $args[0] ) && is_array( $args[0] ) ) { $args[0]['has_children'] = $this->has_children; // Back-compat. } else if ( isset( $args[0] ) && is_object( $args[0] ) ) { $args[0]->has_children = $this->has_children; } }}} " JoelStransky Future Releases 42566 When I use wp_nav_menu I get a huge update_meta_cache query regardless of theme Menus 4.8.3 normal normal Awaiting Review defect (bug) reopened 2017-11-15T23:53:36Z 2021-01-26T02:32:23Z "Hi there, I've got a wordpress site that's been up and running for a couple of years now. I always keep core+plugins up to date, and although I use a custom theme, I'm pretty happy with how it's working. Recently however it started to crash regularly - and the server guys notified me that it was mysql that was causing it. So I installed Query Monitor and took a look - there was a massive query which looked like this: {{{ SELECT post_id, meta_key, meta_value FROM ajs_postmeta WHERE post_id IN (11178,9677,9060,7417,7354, ) ORDER BY meta_id ASC }}} This was returning 20,000 rows each time the page was loading. This obviously overloaded the server during peak times and it needed rebooting. This is the code that was causing the problem (I know this because I replaced it and the offending query disappeared) {{{#!php 'header-menu', 'container' => 'nav', 'container_class' => 'nav-menu-holder nav-menu-landing nav-new', 'menu_class' => 'nav-menu', 'walker' => new themeslug_walker_nav_menu)); }}} So I replaced wp_nav_menu with static HTML and the query size reduced as it was no longer calling wp_nav_menu. I thought it might have been something I'd done in my theme - so I removed the custom walker, which didn't have any effect, and played about with some settings. I tried using the recommendation here: [https://hitchhackerguide.com/2011/11/01/reducing-postmeta-queries-with-update_meta_cache]/ but that had no effect. So the next step was to try a different menu. So I deleted my menu (which had 70/80 items in it) and added 5 new items to a new menu. That then gave the following query: {{{ SELECT post_id, meta_key, meta_value FROM ajs_postmeta WHERE post_id IN (11178,9677,9060,7417,7354) ORDER BY meta_id ASC }}} which is the same query as above but without the lots of additional ids - as this menu only had 5 items. This returned around 450 rows - so it's not hard to see that a menu with 70/80 items would get up to 20,000. The last thing I tried was to change to the default theme and disable all plugins (bar Query Monitor) and tried again. I associated my test menu (with the 5 items) with the 2017 theme top menu and checked query monitor - it still showed this query: {{{ SELECT post_id, meta_key, meta_value FROM ajs_postmeta WHERE post_id IN (11178,9677,9060,7417,7354) ORDER BY meta_id ASC }}} with the same number of rows. So my question is this - is this something that is a problem in core wordpress, seeing as this update_meta_cache() method seems to be creating massive queries if you have a larger than average menu - even 15/20 items would create a fairly large result set each time. I've been googling like crazy as I really want to get this sorted - but I can't seem to find a solution, and I'm wondering if it's something in the latest release. There's no difference between browser or OS that I can see - its just something wrong (I think) with the update_meta_cache method as it relates to the wp_nav_menu function. Anyway, happy for you to take a look at my config etc - let me know what you need. Best email to get me on is andy@weboptimize.co.uk or you can call my UK mobile on 07791-107755 Thanks Andy" andyseaton83 Future Releases 44329 current-menu-item class not applied to home link with starter content audrasjb Menus low normal Future Release defect (bug) reviewing 2018-06-08T03:12:20Z 2019-07-09T05:43:31Z "When viewing starter content in the customizer the home link does not get the current-menu-item class applied when you view the home page. The menu-item-object-{$type} class is also missing $type, so it just has the class menu-item-object- applied. When viewing a customizer changeset of the starter content before actually publishing - the home link is not given the current-menu-item class as well. The menu-item-object-{$type} class is still missing $type in this class too. After publishing the starter content the front end appears to have .current-menu-item correctly applied to the menu when navigating. However, when viewing the site in the customizer - the home link now always has the current-menu-item class applied regardless of which page you visit. This results in two links having current-menu-item applied ( the home link and the currently viewed link ). At this point the menu-item-object-{$type} class now has $type === 'custom', so the class menu-item-object-custom is properly applied. Additional notes: - I was only testing with fresh wp installs. - I was using default permalink structure. - I noticed this issue with other themes that provide starter content, but it also happens with twentyseventeen - #43401 does not seem to fix the issues outlined in the steps below. Expected results: I expected for menu items to have the current-menu-item classes properly applied when viewing changesets, the customizer preview would accurately reflect the frontend display, and that current-menu-item would not be applied to two different links when previewing pages in the customizer. Steps to replicate: 1. Use latest trunk (this does also occur on 4.9.6). 2. Have fresh_site option set to 1 to get starter_content. 3. Activate twentyseventeen theme. 4. Go to customizer. 5. Starter content should be populated - inspect the ""Home"" link which doesn't appear to have current-menu-item added, and has the incomplete class menu-item-object- as well. 6. Click on one of the other pages - the link properly reflects the current-menu-item class. 7. Save draft and open the changeset url provided. 8. Click on one of the other pages other than home, and the same issue occurs. 9. Go back into customizer, publish the changeset, and view the site now on the frontend. The home page link is now properly given current-menu-item, and menu-item-object-custom is correct. 10. Click on one of the other links, and the home link no longer has current-menu-item applied, and is applied correctly to the new page you're on. 11. Click on customize - once the customizer loads, the home link AND the link your were looking at both have current-menu-item applied, only the previewed page should have this class." timph Future Releases 40649 parent_file filter seems to be overwritten by get_admin_page_parent call Menus 4.7.4 normal normal Awaiting Review defect (bug) new 2017-05-03T13:37:51Z 2019-06-10T22:21:53Z "In wp-admin/menu-header.php the filter `parent_file` seems to have little to no impact most of the time. This is because the global `$parent_file` variable often gets immediately overwritten by the `get_admin_page_parent` function call. {{{#!php }}} '''Menu with a location''' {{{ }}}" benoitchantre Future Releases 41800 Ability to collapse multi-level menus in the Menu editor Menus 4.9 normal normal Awaiting Review enhancement new 2017-09-05T14:04:37Z 2017-09-07T15:59:19Z "When creating large menu structures in the Appearance > Menu editor, it can be very overwhelming when there's a number of top-level items with child items... almost becoming an eyesore and confusingly difficult to navigate. Could we work to make any menu item within the editor have the ability to be collapsed? Along with the default state upon loading the editor to have them collapsed, with an icon to expand it." atomicjack Future Releases 13273 "Allow ""'non-clickable"" menu items" Menus 3.0 normal normal Future Release enhancement new 2010-05-06T10:58:50Z 2023-11-10T16:19:53Z "In the new menu generator I'm missing the option to create ""non-clickable"" menu items. What I'm after is that I want to create for example a main menu item with the title ""Links"" which is non-clickable (no url attached to it) and basically only acts as an umbrella item for the actual links I want to locate as subitems of the item ""Links"". - Home - Something else - Links (this one should be non-clickable) - external link 1 - external link 2 - etc I think that an optional tickbox in the add link section will do the trick. Basically, all it has to do is to ""disable"" the check whether or not a valid URL format has been submitted and, of course, it has to trigger some modified html output. Hope you guys can add this in the 3.0 release because this would basically complete the menu generator :) Keep up the good work and I'm really looking forward to the 3.0 release!" stgoos Future Releases 35127 Allow wp_nav_menu() function to add container attributes, including Schema.org structured data Menus 4.4 normal normal Awaiting Review enhancement new 2015-12-17T00:06:34Z 2017-03-07T15:29:38Z "I'd like to propose an enhancement that would improve the flexibility of the `wp_nav_menu()` function to allow additional attributes to be added to the `