ticket summary owner workflow __group__ _version priority severity milestone type _status _created modified _description _reporter Comments 60600 found some spelling mistakes swissspidy General normal normal WordPress.org defect (bug) reviewing 2024-02-22T11:47:53Z 2024-02-22T12:10:41Z "I found some spelling mistakes in the WordPress Plugin documentation No.1 ---- https://developer.wordpress.org/plugins/shortcodes/shortcodes-with-parameters/#parsing-attributes:~:text=shortcode.%20In%20the-,exampe,-above%2C%20it%20will It will be - ""example"" not exampe. No.2 ---- https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/#basic-strings:~:text=To%20echo%20a,instead%20of%20writing%3A and it will be ""translation"" not tranlsation. " azimjamshed 1 60000 alot of tags is too many dev-feedback General normal normal WordPress.org enhancement new 2023-12-01T18:06:00Z 2024-01-09T16:12:22Z "[[Image(https://core.trac.wordpress.org/raw-attachment/ticket/13237/alot-of-bugs.gif)]] Previously: - #50000 - #40000 - #30000 - #20000 - #13536 - #13237 Changed with thanks to @joostdevalk. See #60001 " jorbin 2 53216 A Gutenberg Block repo dev-feedback General normal normal WordPress.org feature request new 2021-05-16T09:26:52Z 2023-04-20T13:38:47Z "Right now the plugin has it's repository, and the themes have one. The Gutenberg blocks are now often shipped in a plugin (and sometimes even in a theme). These plugins often ship many blocks when only one or a few are needed. This can cause bloated websites, and takes away flexibility. My suggestion is, why not an extra repo for Gutenberg blocks, or maybe even extensions in general (custom post types as well, but not super sure about that). You'd have a super easy separation of concerns: - Theme repo for styles - Plugin repo for functionality - Gutenberg(/Add-on) repo for added blocks(/types) It would then be amazing if you could choose from a few separate blocks, or if you really like a company/developer, maybe a small set of blocks that go well together. I know it sounds like a big change, but I like thinking big and I think that's what we're doing with Gutenberg anyway. We could also just clone the system for the plugin repo and only make a few adjustments. Thoughts?" tomjdevisser 4 56856 Blogger Importer: File class-feed.php is deprecated Import 4.7 normal normal WordPress.org defect (bug) new 2022-10-19T19:41:56Z 2023-11-28T22:56:10Z "The Blogger Importer plugin (tested v0.9) causes the following deprecation notice: PHP Deprecated: File class-feed.php is deprecated since version 4.7.0! Use fetch_feed() instead. in ../wp-includes/functions.php on line 5577 `class-feed.php` was deprecated in [39449]. " ironprogrammer 3 56857 Blogger Importer: File class-wp-feed-cache.php is deprecated Import 5.6 normal normal WordPress.org defect (bug) new 2022-10-19T20:58:34Z 2022-10-19T20:58:34Z "The Blogger Importer plugin (tested v0.9) causes the following deprecation notice: PHP Deprecated: File class-wp-feed-cache.php is deprecated since version 5.6.0 with no alternative available. This file is only loaded for backward compatibility with SimplePie 1.2.x. Please consider switching to a recent SimplePie version. in ../wp-includes/functions.php on line 5587 `class-wp-feed-cache.php` was deprecated in [49565]. " ironprogrammer 56858 Blogger Importer: Undefined (dynamic) properties Import normal normal WordPress.org defect (bug) new 2022-10-19T21:24:34Z 2022-10-21T01:29:57Z "Under PHP 7.4, the Blogger Importer plugin causes notices like the following: ''If new posts are imported:'' Undefined property: Blogger_Importer::$posts_done in ../blogger-importer/blogger-importer.php on line 408 == Background [https://github.com/WordPress/blogger-importer/commit/f1c9d6a7fe42fe4b88b475c9a92a96bd7cee8dba f1c9d6a7] introduced several dynamic properties to the `Blogger_Importer` class, such as counters for skipped and imported posts. In PHP 8.0 dynamic properties log as warnings, [https://php.watch/versions/8.2/dynamic-properties-deprecated in 8.2 as deprecations], and in 9.0 result in fatal errors. " ironprogrammer 5 8578 Blogger import incorrectly reports saved user information Import normal normal WordPress.org defect (bug) new 2008-12-11T16:53:52Z 2019-03-15T00:30:30Z "I installed a fresh copy of WordPress 2.7 and was importing content from a Blogger site. Before beginning to import, the page claimed that Blogger account information was saved in the database and that I could restart the process. Even after pressing the ""Clear account information"" button, the message still appeared." covert215 2 39301 Importer associates all posts with uncategorized term in WP4.7 PHP7 Import 4.7 normal normal WordPress.org defect (bug) new 2016-12-16T01:00:20Z 2017-04-01T08:33:47Z "The WordPress Importer plugin fails to remove the uncategorized term from the post which has at least one category set. It's a pretty quick fix, though. wordpress-importer.php after line 729 Insert: {{{#!php if ( 'category' == $term['domain'] ) $post_is_categorized = TRUE; }}} wordpress-importer.php after line 753 Insert: {{{#!php if ( isset( $post_is_categorized ) && $post_is_categorized ) { wp_remove_object_terms( $post_id, 'uncategorized', 'category' ); unset( $post_is_categorized ); } }}} And BTW, is there somewhere I can make pull requests for WP like on github? That will make it much easier to suggest code changes. " staymanhou 5 24995 Importer does not check to see if DOM is available Import 3.6 normal normal WordPress.org defect (bug) new 2013-08-08T20:55:34Z 2017-02-21T09:11:58Z "I have a WordPress network with many blogs. I exported a few posts from one blog (export file attached with some details sanitized). I then imported the posts into another blog. Not only does the import probably do nothing, the '''/''blogname''/wp-admin/import.php''' page stops rendering after: {{{
/wp-admin/edit.php?post_type=page:1
Checking page content, indeed there are TWO id=""post_parent"" in the TBODY id=inlineedit, and other later in the TR id=bulk-edit
Bug appears with all plugins turned off, and fresh install as well.
Reproduce: Simply open the ""All pages"" menu on admin panel, and see the console for the DOM form errors.
" iarovuo 3
24447 Avoid losing data after nonces expire iseulde early Administration normal major Future Release defect (bug) assigned 2013-05-29T07:55:35Z 2020-05-14T19:23:54Z "Happens when an admin page containing a form is left open for more than 24 hours and the user decides to submit the form. This is quite rare for most admin pages as the users typically spend short time there. However this can happen on the Edit Post screen too despite that we refresh the basic nonces every `wp_nonce_tick` (12 hours):
- The user starts new post.
- At some point the Internet connection is lost.
- The user decides to finish later and puts the computer to sleep (closes the laptop, etc.).
- The user decides to continue writing more than 24 hours after that.
At this point all nonces have expired and cannot be updated as we've missed the previous nonce_tick update." azaozz 31
38809 Better wp namespace in password-strength-meter.js close Administration normal normal Future Release defect (bug) reviewing 2016-11-15T23:27:37Z 2022-03-30T20:52:46Z "Currently, `password-strength-meter.js` uses this pattern to pass the wp object as argument:
{{{
window.wp = window.wp || {};
var passwordStrength;
(function($){
wp.passwordStrength = {
...
})(jQuery);
}}}
so `wp` inside the IIFE is, technically, undefined, even if WordPress considers `wp` a global object. Also the first line is pointless if then `window.wp` is not passed as argument." afercia 11
40218 Button and select box alignment issue in page view Administration normal normal Future Release defect (bug) new 2017-03-21T12:33:37Z 2024-02-24T23:43:41Z "Hi,
Button and select box are not aligned in the page view. I have attached screenshot for more information.
Thanks" sagarprajapati 13
60045 Change to add_new label displays wrong label for old post types joedolson* Administration 6.4 normal normal Future Release defect (bug) accepted 2023-12-11T02:32:49Z 2024-03-12T15:27:00Z "In #47125, the label for adding a new item in the menu changed its default value from Add New to Add New Post, with developers advised to change their code to match when creating custom content types.
To me this was a mistake; an appropriate label already existed with that wording: the add_new_item label.
If it was desired to change what displayed in the menu, the right fixing was to use display add_new_item, rather than changing the entire meaning of add_new.
I have always registered custom post types by setting add_new_item to 'Add New MyPostType', and leaving add_new out of the array entirely, since there was never a need to override the wording of 'Add New'.
Now, all of my post types for all clients over many years are displaying 'Add New Post'.
Can this change please be reverted, and replaced by displaying add_new_item when you wanted to display the item name, as it was always intended to be used?" smerriman 6
55768 Checkboxes not displayed when images are turned off in browser Administration 5.3 normal normal Future Release defect (bug) new 2022-05-18T09:24:11Z 2022-05-19T07:59:09Z When images are turned off in browser, the checked post categories in the admin post dashboard disappear. martiniwebb 4
42586 Code Editor: Inconsistent results between finding in CodeMirror vs browser Administration 4.9 normal major Future Release defect (bug) new 2017-11-16T16:43:25Z 2022-11-17T23:54:13Z "When in the Appearance/Editor, f'rinstance, when editing a child theme's CSS file, the Ctrl-F (Search) no longer works. SOMETIMES it will find a string IF that string is on the VISIBLE portion of the screen. It will NOT find that string in the file if the string is NOT visible.
Sometimes it will not find the string at all - visible or not.
A serious impeiment to the Editor!" wpress2010 47
57030 Condition is not strictly checked on options-general.php file SergeyBiryukov needs-unit-tests Administration 3.0 normal normal Future Release defect (bug) assigned 2022-11-08T09:56:56Z 2023-07-06T03:14:17Z In options-general.php file it is 0 is being compared with another variable which is $current_offset. As 0 is numeric value this needs to be compared. rakibwordpress 6
47505 Create a comprehensive input validation API for WordPress editor and administration interface audrasjb* needs-unit-tests Administration normal normal Future Release defect (bug) accepted 2019-06-07T14:24:03Z 2019-10-04T15:43:46Z "Currently, WordPress lacks a comprehensive API for validating form input and alerting users to errors or missing fields. One example of how this can cause problems was captured by @conner_bw in #47018 -- failing to fill in the required ‘Name’ field when creating a new taxonomy term highlights the field in red but provides no textual message indicating that a required field is missing. As noted by @afercia:
> there are at least two WCAG success criteria (1 is level A, the other one is level AA) that requires a clear identification of the item in error and clear suggestions for correction.
([https://wordpress.slack.com/archives/C02RP4X03/p1556291609088300 See Slack discussion])
The lack of input validation mechanisms has also been noted as a shortcoming in Gutenberg ([https://twitter.com/thespacedmonkey/status/1136570949048909824 see tweet] from @spacedmonkey about this).
In the [https://wordpress.slack.com/archives/C02RP4X03/p1556291406082600 Slack discussion] of #47018, the Accessibility team agreed that the broader goal of researching and planning a comprehensive form validation API would be a valuable project that would benefit all users. This ticket should serve as a starting point for that exploration process. One example of how this could work shared during the discussion was something along the lines of Tenon’s React-based form validation library: [https://www.tenon-ui.info/forms-full-demo]
Two use cases that this API should cover:
- Required input is missing
- Required input is not the expected type
To be continued!" greatislander 11
46307 Custom admin menu items don't provide their title on medium breakpoint garrett-eclipse Administration normal normal Future Release defect (bug) assigned 2019-02-22T06:52:05Z 2019-02-22T17:11:21Z "With custom admin menus if no submenu is provided for them they don't have a flyout on hover which on medium breakpoint leaves them only identified by their icon.
Note: Core menus all have submenus so this only affects custom menus developers introduce.
It would be nice to still provide the submenu flyout with only the wp-submenu-head item present as that would provide the title of the item.
The submenu items are introduced here with the first item being the wp-submenu-head. Am thinking moving the empty check into the ul would leave the flyout providing the title.
https://github.com/WordPress/WordPress/blob/92aa2f9e92a4e1ad5471d87d5292587c5cee5702/wp-admin/menu-header.php#L178-L250" garrett-eclipse 3
38899 Deletion of auto-drafts and trashed posts never gets scheduled unless user accesses admin pages westonruter* dev-feedback Administration normal normal Future Release defect (bug) accepted 2016-11-22T03:55:27Z 2021-06-07T09:58:35Z "As [https://core.trac.wordpress.org/ticket/38615#comment:37 noted] in #38615:
It turns out that the cron event that does `wp_delete_auto_drafts()` is only scheduled when a user lands on `post-new.php`:
{{{#!php
Generated content should be searchable, selectable, and available to assistive technologies. The content property applies to speech and generated content '''must''' be rendered for speech output.
Some interesting data about browsers and screen readers support (i.e. which ones announce CSS generated content) here: http://tink.uk/accessibility-support-for-css-generated-content/. Please consider these data are from March 2015, so they're probably a bit outdated.
'''What this means in practice'''
In the best case, screen readers will try to read the generated content as a character, and if there's no character that matches, they may announce `You are currently on a text element`. See #37513 for a specific use case.
[[Image(https://cldup.com/xOaq2xSczn.png)]]
In the worst case, when the generated content maps to an actual recognisable character, screen readers will just announce the character. A couple simple examples:
`content: ""\00d7"";` gets read out as ""times""
`content: ""\25BA"";` gets read out as ""black right pointing pointer""
Maybe in the future it will be possible to use a CSS-only solution, see:
Alternative Text for Speech
https://www.w3.org/TR/css-content-3/#alt
which will (hopefully) introduce the ability to specify alternative text for the CSS generated content property, after a slash:
`content: ""\25BA"" / """";`
There's no browser support so far.
'''A possible solution'''
When CSS generated content is ''not'' intended to be available for speech output, then it should always be wrapped by an element (for example a ``) with an `aria-hidden=""true""` attribute. At the moment, this is the only reliable way to hide CSS generated to assistive technologies.
Of course, trying to apply this solution to all the CSS generated content currently used in core would be a huge task. There may be better solutions, worth researching a bit. Worth also considering there's an ongoing effort to replace the CSS font icons currently used in core with SVG icons. That could help mitigating the issue, but it will still stand for any other non-icons generated content.
Any thoughts and feedback welcome!
" afercia 11
48793 Issue in selecting option from auto-suggest drop-down using plugin editor. Administration 5.3 normal normal Future Release defect (bug) new 2019-11-26T05:39:39Z 2020-11-05T06:14:27Z "Hello Team,
I noticed that when I edit the plugin/theme using the editor in the backend, it gives auto-suggest. But when I start typing, I could not select any option from the drop-down (by navigating using up/down arrow keys). It is selected sometimes only if I could manage to press enter at the same time.
PFA
" sonali1215 1
32892 List table: Select %s shouldn't be a row header Administration 4.2 normal normal Future Release defect (bug) assigned 2015-07-05T14:59:41Z 2018-10-12T15:31:29Z "See related #31654 and #26167.
In all the List Tables in the admin, the ""Select %s"" (where %s is the name of the Post, Attachment, Plugin, User, etc,) is used as row header:
{{{
}}}
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 2
33002 List table: avoid redundant Edit links and reduce noise for screen readers Administration 4.2 normal normal Future Release defect (bug) new 2015-07-15T14:01:49Z 2019-06-04T19:30:55Z "Splitting this out from #32254.
In all the List Tables (except Comments) there are redundant adjacent ""Edit"" links. They have different text and they point to the same resource (the edit screen). For example, in the screenshot below ""Scheduled"" and ""Edit"" (the row actions one) serve the same purpose.
[[Image(https://cldup.com/jY65ziCiL4.png)]]
As pointed out in #32254 the row actions ""Edit"" link may represent some sort of feedback given to users about what they can do, specifically if they have permission to edit and I see the potential confusion in removing it.
On the other hand, that's completely redundant and confusing for screen reader users who will just hear the same information twice, multiplied for the default 20 items per page makes a total of 40 ""Edit"" links. Considering also the title attributes, screen readers will read out something like this:
{{{
Scheduled link Edit “Scheduled”
Edit link Edit this item
}}}
We should try to find a way to hide the redundant link just for assistive technologies. Would be a bit tricky since `aria-hidden` would silence screen readers but wouldn't remove the tab stop. Any thoughts more than welcome.
" afercia 8
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 47
38076 Network admin plugin pages can be accessed on non-multisite dev-feedback Administration normal normal Future Release defect (bug) new 2016-09-16T19:56:07Z 2021-07-06T10:28:05Z "I just noticed that it's theoretically possible to access a plugin-generated page in the network admin panel even if we're not on a multisite setup. The same applies to the user admin panel as well.
To replicate, create a plugin that uses `add_menu_page()` with a slug `my_test_page`, hooked into `network_admin_menu`. Then manually go to the URL `http://yourdomain.com/wp-admin/network/admin.php?page=my_test_page`.
This happens because the `is_multisite()` check happens only after including the general `wp-admin/admin.php` administration bootstrap file which takes care of any plugin pages by itself. The problem is we can't do it before because WordPress hasn't been loaded then. A possible solution would be to split the `require_once` statement in `wp-admin/network/admin.php` into two, one to load the WordPress core functions, the other to load `wp-admin/admin.php`.
I don't think this is a very critical issue, but I thought it should be a ticket. It's very unlikely that anyone tries to access a network admin URL when they don't have a multisite. On the other hand, we catch that in other areas (through `! is_multisite()` checks), so we might try to do it here as well." flixos90 1
37712 Opacity not applied to admin menu icon when it selected has-patch Administration normal normal Future Release defect (bug) new 2016-08-18T08:09:28Z 2020-11-20T01:26:01Z "Opacity not applied to single menu with custom menu logo when it selected.
But it work fine where menu has sub-menu and following css applied for it.
{{{
#adminmenu li.menu-top:hover .wp-menu-image img, #adminmenu li.wp-has-current-submenu .wp-menu-image img {
opacity: 1;
}
}}}
So here css rule missing for single menu with custom menu logo.
When I applied following css then it work fine.
{{{
#adminmenu li.menu-top.current .wp-menu-image img {
opacity: 1;
}
}}}
" chandrapatel 1
51383 PHP error body class added for suppressed errors has-patch Administration 5.5 normal normal Future Release defect (bug) reviewing 2020-09-23T18:27:14Z 2023-09-19T12:42:00Z "When a PHP error occurs in the admin that is suppressed using the `@` operator, the `.php-error` class is still added to the `` even though the error will not be output.
To reproduce, use error suppression on code that invokes an `E_WARNING` level error. I discovered this with code calling the `mkdir()` method within the `WP_Filesystem_Direct` [https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes/class-wp-filesystem-direct.php#L533 class for a pre-existing directory].
`@mkdir( ABSPATH . 'wp-content/themes/' );` should reproduce the issue after ensuring nothing else is actively capturing and processing PHP errors (such as [https://wordpress.org/plugins/query-monitor/ Query Monitor]).
Follow up to #35155 in 5.5 and #51073 in 5.5.1." desrosj 35
52151 Post / Page Title Columns broken has-patch Administration 5.6 normal normal Future Release defect (bug) new 2020-12-22T11:38:39Z 2024-03-05T16:23:51Z "The posts screen in wp-admin is wrapping the post title vertically so that the page becomes unreadable.
WordPress 5.6 running WP-Blossom theme.
screen cap here
https://1drv.ms/u/s!As8R6Nv2QLWnk9MRrGAJmuNIJ1QDoA?e=dcHWT7
sorry couldn't work out how to upload image ....
[[Image(https://1drv.ms/u/s!As8R6Nv2QLWnk9MRrGAJmuNIJ1QDoA?e=dcHWT7)]]
" pascoedj 19
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 4
31199 Potential reference to unset variable in get_bulk_actions (WP_Posts_List_Table) chriscct7* reporter-feedback Administration normal normal Future Release defect (bug) accepted 2015-02-01T16:44:14Z 2019-01-14T04:42:47Z "get_post_type_object can return null in some cases, which causes a notice when current_user_can is called later in the function.
Attached a patch to check if delete_posts is set, and to only add actions if it is. Thanks!" sgrant 3
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 19
58455 The admin menu remains sticky when displaying warning or error messages on the Site Health page. audrasjb has-patch Administration normal normal Future Release defect (bug) reviewing 2023-06-05T12:15:55Z 2024-02-20T09:54:47Z "Improper Sticky Behavior of Admin Menu when displaying warning or error messages on the Site Health page.
Refrance: https://www.loom.com/share/3565aaf2d04e4b0b87dee361ee8335bb" dhrumilk 53
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 8
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 5
15386 WP_List_Table::get_columns does not work for plugins scribu close Administration 3.1 high major Future Release defect (bug) reopened 2010-11-11T14:42:28Z 2023-02-16T20:06:44Z "Creating a new table based on the WP_List_Table class does not work as the get_columns method is not being called.
The problem is when WP_List_Table::get_column_info() calls get_column_headers() instead of $this->get_columns() where all the column data is stored.
Moving the filter manage_*_columns from get_column_headers() into WP_List_Table::get_column_info() along with passing $this->get_columns() fixes this issue." ptahdunbar 24
40581 When all columns are 'special' ... has-patch Administration normal normal Future Release defect (bug) new 2017-04-26T17:10:37Z 2019-03-02T16:12:56Z "In an admin page list, when all columns are 'special', no columns settings
" Arena94 3
9716 WordPress Theme/Plugin editor adds blank lines has-patch Administration 2.7.1 normal normal Future Release defect (bug) reopened 2009-05-03T20:32:01Z 2022-07-13T19:45:44Z "When I edit theme css in theme editor in WP admin
!WordPress reformats my CSS and adds a blank life between entrys in css.
it adds a cr and line break ....
In other words if you have a 100 line css
download with FTP look at in text editor
it is now 200 lines
as WP added blank lines to css
it should not be adding things to the CSS?
It may only do this when it wraps window but I think not it appears to add blank lines.
Imagine the damage to a 1000 line CSS it spaces every entry by 1 line!!!!!!!!!!!!!! It stiil works but it messes it up.
THAT IS COFIRMED ONE EDIT DOUBLE SPACE ENTIRE CSS... VERY BAD
Here is part of the problem but not the double space in total.
When you down load the file in FTP and it is in windows encoding
the line endings.
So you ftp back and all is fine.
Now you are at the coffee shop and what a quick change, so you login to WP admin and theme editor edit CSS.
Now you get home and download in ftp to continue your work on CSS.
The file is now mac formatted (or thinks it is) so when you edit the line endings do not contain the right line breaks for windows OR WP theme editor as it ignores them. This explains the wierd spacing though not the double spacing .... why is it converting to mac and yet ignores mac?!
weird.. it adds a CR tag
must be bug
again though its still double spacing on edit IN windows line ending though if you down load cSS its tagged mac format...
Use notepad 2 or Note pad plus to see the error.
When ever you edit with !WordPress editor it adds cr and says css is now mac formatted.
FTP download the file and now see all the extra CR's it adds.
So it likes CR only so I convert to CR only and it beaks CSS it wants CR LF to work but if that is the case why does the online editor add CR only?????????????????????????
" Vistronic 26
47690 remove_submenu_page() doesn't remove corresponding entry from $_wp_submenu_nopriv johnbillion dev-feedback Administration normal normal Future Release defect (bug) reviewing 2019-07-12T10:41:09Z 2020-04-13T10:43:50Z "It can sometimes be desirable to give access to a submenu to a user that wouldn't normally have access to it.
Calling `remove_submenu_page()` and then calling `add_submenu_page()` to re-register the screen with a different user capability doesn't work completely because the entry that gets added to the `$_wp_submenu_nopriv` global by `add_submenu_page()` doesn't get removed by `remove_submenu_page()`.
This means the menu item appears but access to the screen is denied when `user_can_access_admin_page()` is called, resulting in a `Sorry, you are not allowed to access this page` error.
" johnbillion 4
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 7
58638 Add 'close' button to dashboard widgets oglekler dev-feedback Administration normal normal Future Release enhancement assigned 2023-06-27T04:59:43Z 2024-02-12T09:12:32Z In the Dashboard it isn't obvious that widgets can be removed from it via Screen options and sometimes widgets are annoying, or you just don't need them. I suggest adding `close` button into dashboard widget header. oglekler 15
32940 Add IDs to Admin Hyperlinks dev-feedback Administration 4.3 normal normal Future Release enhancement new 2015-07-09T12:18:59Z 2020-02-15T22:37:53Z "Suggestion: add Ids to the primary admin interface hyperlinks.
Adding IDs to primary anchor tags in the admin UI makes it far easier to create and maintain UI test suites such as Selenium IDE. UI testing catches problems that phpUnit is not designed to address.
Example: Pages / Add New
xpath = /html/body/div/div[1]/div[2]/ul/li[5]/ul/li[3]/a
css = html.wp-toolbar body.wp-admin.wp-core-ui.js.edit-php.auto-fold.admin-bar.post-type-page.branch-4-3.version-4-3.admin-color-fresh.locale-en-us.customize-support.sticky-menu.svg div#wpwrap div#adminmenumain div#adminmenuwrap ul#adminmenu li#menu-pages.wp-has-submenu.wp-has-current-submenu.wp-menu-open.menu-top.menu-icon-page ul.wp-submenu.wp-submenu-wrap li a
Would be nice to reference key elements with things like a#menu-page-add-new instead. Especially when updates to WP Core change the higher level HTML DOM classesor structures.
" charlestonsw 2
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 2
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 10
38097 Add ability to Settings API to assign positioning has-patch Administration 4.7 normal normal Future Release enhancement new 2016-09-19T14:39:59Z 2021-06-01T17:28:50Z "When using the Settings API to add a settings field, particularly if adding to an existing settings screen, it would be nice to have some way of positioning the new field, as you can with add_menu_page, for instance.
So, I've just updated a plugin in which I've added a single settings to the existing ""General"" settings screen. It's date related and it would sit nicely in a specific position on that screen, but I have no control over it. So, a ""position"" field, as add_menu_page has, would be a nice addition to provide a more nuanced result." dartiss 8
51086 Add native support for tabbed settings pages in WP Admin joedolson* Administration normal normal Future Release enhancement accepted 2020-08-20T20:07:36Z 2021-12-17T16:46:26Z "There are a lot of plugins out there handling tabbed setting screens in different ways, so it may be time to introduce a standard API for this pattern.
This patch adds a new `do_tabbed_settings_sections()` function which works just like the Settings API's `do_settings_sections()` function, but prints each section heading as a tab/panel combination. In situations where there's only one section to render, the new function will fall back to its un-tabbed sibling.
The patch also includes a standard script for tabbing between different setting sections, with support for linking directly to a particular tab via the URL hash (e.g. !https://example.com/wp-admin/options-general.php?page=some-settings-page#some-tab-ID)." stevegrunwell 8
43841 Add request confirmation and security logging for major user actions Administration normal normal Future Release enhancement new 2018-04-24T10:10:51Z 2018-04-24T11:15:16Z "This is a follow-up from #43443.
We can extend the methods and functionality added for privacy request to other ""major"" user actions:
- Lost password notifications.
- Changing email addresses.
- Deleting accounts.
This will form the base for a user security log screen where admins will be able to see notifications, verify requests, and keep track of other user activities." azaozz 2
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 9
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 23
26605 Appearance of recent/future posts in dashboard looks off on mobile. has-patch Administration 3.8 normal normal Future Release enhancement new 2013-12-13T13:24:18Z 2019-07-22T18:22:30Z "When viewing the dashboard on a small screen device, the layout of the date and post title in the recent/future post section of the layout of the site activity widget looks funny when the title is fairly long.
I think it might be better to have the date on a separate line.
[[Image(https://dl.dropboxusercontent.com/s/h8jpr8305isg0gy/2013-12-13%20at%2013.17%202x%20%281%29.png)]]
" mattheu 10
49616 Audit /wp-admin and sentence-case UI elements (buttons, drop-downs) for better readability has-patch Administration normal normal Future Release enhancement new 2020-03-10T14:24:09Z 2021-01-19T16:16:04Z "I know this has been done throughout Gutenberg and in core to some extent (see #49371 and #48412). Would it be worth doing a sweep of the remainder of /wp-admin to sentence-case UI elements once and for all?
Examples:
* ""Add New Post"" becomes ""Add new post""
* ""All Categories"" becomes ""All categories""
The case for sentence case, h/t @danhauk:
* Sentence case improves readability by allowing users to see proper shapes of words without the breaking flow of Capital Letters (i.e. Title Case is harder to read quickly because of how we typically read using the shapes of words.)
* Sentence case respects the difference between proper nouns and the other words. For example, “Upgrade to premium plan” vs. “Upgrade to Premium Plan” could have very different meanings.
* i18n: some languages capitalize different things (e.g. all nouns are capitalized in German). Title case adds cognitive load when users have to figure out which words are nouns, for example.
I welcome your thoughts!" sixhours 3
31696 Better select, multi-select, and autocomplete/suggestion inputs in the admin dev-feedback Administration normal normal Future Release enhancement new 2015-03-19T16:47:15Z 2018-06-06T20:52:02Z "I know this has been brought up before, but can't find the original ticket. That said, a few months ago Helen brought up a potential integration of the Select2 library but, due to licensing issues, we were unable to proceed with it at the time ([https://github.com/select2/select2/issues/2468 GH issue]). The licensing issue has now been resolved and, since I've been unable to find the original ticket, I'm opening a new one along with a preliminary patch to add Select2 to core.
At the moment, this patch is based on a new CSS class (select2) being added to any select field that should implement the Select2 library. I've added it to the select fields on the Settings->General page as an example, but didn't want to implement it system-wide until the community had a chance to speak up RE: where does/doesn't Select2 belong, or should it actually be implemented everywhere. The language and timezone fields seemed an obvious choice given their inherent size, but things like the emoji field under Settings->Reading that have a finite number of options seem less obvious.
Discuss!" section214 21
58781 Change wording of field description for tagline dev-feedback Administration normal normal Future Release enhancement new 2023-07-11T06:26:54Z 2024-01-19T06:33:34Z "This is a follow-up to #57675
I [https://core.trac.wordpress.org/ticket/57675#comment:28 raised my concerns there], but it was too late in the cycle. So here we go:
These are my concerns about the solution we use now:
1) The example is misleading, the tagline should be meaningful, and just not like in the example
Using a unique and descriptive tagline is important for search engine optimization (SEO) purposes, as it helps convey the website's purpose and relevance to both search engines and visitors.
2) The “ and ” could be misunderstood so people would enter quotation marks into the tagline.
This can impact the visual presentation and readability of the tagline to visitors.
To keep the iconic phrase ""Just another WordPress site"" while being informative at the same time we could formulate:
In a few words, explain what this site is about. We're sure your site is so much more than ""Just another WordPress site""" Presskopp 13
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 3
31354 Compound settings confusing with screen readers (checkboxes) joedolson* Administration 4.1 normal normal Future Release enhancement accepted 2015-02-17T03:08:21Z 2024-01-30T15:19:40Z "There are a number of settings in the admin that are made out of multiple variables. That is, they combine a checkbox/radio button toggle and a value.
When you can see it, it makes sense because it forms a logical sentence and everything works out great.
When you rely on a screen reader, it doesn't really come across as such and there's no link between the different inputs in the setting.
For example:
[[Image(http://i.imgur.com/0r0lDSn.png)]]
As you tab through the different fields, NVDA (with default settings) will announce:
- Break comments into page with - checkbox (not) checked.
- top level comments per page and the - edit fifty.
- page displayed by default - combo box last collapsed.
We need to come up with a pattern that can be applied to split up these toggle/value inputs and clear up confusion this may create.
It would be nice if the inputs for the actual values stay disabled until the appropriate toggle is enabled as well (similar to how the home/blog static page selectors work).
This issue concerns the following fields:
'''On /wp-admin/options-discussion.php:'''
- Automatically close comments on articles older than X days
- Enable threaded (nested) comments X levels deep
- Break comments into pages with X top level comments per page and the X page displayed by default.
- Comments should be displayed with the X comments at the top of each page
'''On /wp-admin/network/settings.php'''
- Limit total size of files uploaded to X MB
Could use input from accessibility and UI teams on how to best tackle this. :)
" Cheffheid 15
31356 Compound settings confusing with screen readers (radio buttons) joedolson* has-patch Administration 4.1 normal normal Future Release enhancement accepted 2015-02-17T03:50:45Z 2024-02-13T15:46:42Z "Similar to #31354, #31144 - but worth noting separately.
As mentioned in #31144, the ""main"" label for radio buttons is never announced which is removing the context for them.
Additional issues with this arise when the setting has a ""Custom"" option with an input field. When tabbing from the radio button to the ""Custom"" input field two things happen:
- It will automatically set the radio button option to ""Custom""
- It announces the current value of said input field without further context. Ie. 'F j, Y'.
The former is not a huge deal, because it automatically updates the input field for ""Custom"" to whatever the value of the previously selected radio button was.
The latter is a bit odd and confusing if you have no further context as to why it's being announced or what it's announcing even means.
Having the input field inactive/unfocusable unless ""Custom"" is selected would probably help with this and remove unnecessary focus on this field when it's ultimately unwanted.
This applies to:
'''On /wp-admin/options-general.php:'''
- Date Format
- Time Format
'''On /wp-admin/options-permalink.php:'''
- Main permalinks setting
Here, too, additional input from accessibility and UI teams more than welcome." Cheffheid 11
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 2
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 6
35554 De-emphasise WordPress Version in the admin has-patch Administration normal normal Future Release enhancement new 2016-01-21T09:54:32Z 2022-05-06T10:49:33Z "Currently WordPress is very proud of the version it's running - but version strings are not exactly the most important piece of information to a regular user.
I'd like to bring it back to displaying only the major version (ie. `Version 4.4`, not `Version 4.4.1`).
A few of us have kicked the idea around over the years, and making the version number less specific as we move towards faster point releases really makes a lot of sense.
There's two options which could be taken:
1. Simply bring it back to x.y (`Version 4.4`). attachment:major.minor.diff
2. Remove it entirely, including the `You are running WordPress x.y.z running Theme X theme.` message in the at-a-glance widget. attachment:remove-all-version-mentions.diff
The second option is a harder-line approach, but removes information that most users have no need to see most of the time. They'll still see update nags when a new version comes out (Well, except for the million or more of sites which choose to enable automatic updates for major versions too) and the version string will always be available on the update screen where it's useful." dd32 55
48641 Discussion: links that look like buttons (and vice versa) dev-feedback Administration normal normal Future Release enhancement new 2019-11-14T17:23:30Z 2021-03-04T21:51:54Z "''This issue has been moved from GitHub to Trac to increase visibility.'' Original GitHub discussion: https://github.com/WordPress/gutenberg/issues/7534#issuecomment-549980093
== Summary
Sometimes, `` elements are made to look like visual buttons to users, even though they are not actually using the `