__group__,ticket,summary,owner,component,_version,priority,severity,milestone,type,_status,workflow,_created,modified,_description,_reporter,Comments
Has Patch / Needs Testing,56499,count() used in the loop condition,,Comments,,lowest,normal,Awaiting Review,defect (bug),new,has-patch,2022-09-02T12:40:53Z,2022-09-21T15:22:51Z,The use of count() inside a loop condition is not allowed; assign the return value to a variable and use the variable in the loop condition instead.,krunal265,8
Has Patch / Needs Testing,33405,"Pagination - use of helip / ""..."" not logic in some cases",,Themes,4.2.4,lowest,trivial,,enhancement,new,has-patch,2015-08-18T16:40:31Z,2019-06-04T21:27:45Z,"Hi there,
I believe there is some improvement potential in the logic of the pagination. The ""..."" indicator does not really serve its purpose, in case you have it only hiding one page link - see attached screenshot.
Would propose to change the function generating the pagination to only use it in case it at least covers 2 page links.",th23,3
Needs Reporter Feedback / Steps To Reproduce,50223,Performance improvement: Avoid using array_unique() where possible,,General,,lowest,normal,Awaiting Review,enhancement,new,reporter-feedback,2020-05-22T08:53:55Z,2020-05-23T13:57:51Z,"We could improve performance by avoiding an expensive call to `array_unique( $array );` where possible.
A more performant option is `array_flip( array_flip( $array ) );`
How to test:
{{{#!php
sanitize_locale_name( [ 'test@test' => 'test@test' ] );
array(1) {
'test@test' =>
string(8) ""testtest""
}
}}}
This is not uncommon for WordPress functions that rely upon `preg_replace()` and a number of other sanitize functions behave similarly.
I would expect an array input to return either `''` as `array( .. )` is not a valid string.",dd32,2
Needs Patch,29260,Update site transients response differences,,Upgrade/Install,2.8,lowest,normal,,enhancement,new,,2014-08-19T06:18:59Z,2019-06-05T06:45:21Z,"Why do the update_themes and update_plugins have a different response type, one is an stdObject another is a simple array.
That being said the plugin and theme upgrader have the same discordance. Please make them so they are consistent with one another. ",krotz,1
Needs Patch,38037,Maximum User ID Issue,,Users,,lowest,normal,Awaiting Review,defect (bug),new,,2016-09-13T10:46:57Z,2019-04-10T07:47:18Z,"Hi,
We found that if you set the AUTO_INCREMENT value to 18446744073709551614 (which is 1 less than the maximum value of BIGINT), it creates a blank user in the admin user table. upon checking the mySQL database details, we found that the ID (_users) is 18446744073709551614 and the user_id (_usermeta) is 9223372036854775807. the reason for the test is, we have created a plugin that allows an admin to change the user ID of any user, so we where testing the maximum upper limits of. The only way to delete this user is manually, the delete option fails.
it would seem the ID (_users) supports 0 to 18446744073709551615
and
it would seem the user_id (_usermeta) supports -9223372036854775808 to 9223372036854775807
this can be checked in https://dev.mysql.com/doc/refman/5.5/en/integer-types.html
thanks",akaracing,1
Needs Patch,14876,wp_get_sidebars_widgets() assumes that widgets are enabled,,Widgets,,lowest,minor,,defect (bug),reopened,,2010-09-15T02:05:43Z,2019-06-05T06:45:15Z,"When a theme does not have any sidebars defined, wp_get_sidebars_widgets() will return the database option anyway.
This reveals a bug where a theme that does not have any widgets may still get the recent comments CSS injected into it. is_active_widget() is returning true because that widget was active when the sidebar option was last used.",nacin,13
Needs Dev / Bug Wrangler Feedback,37145,Admin submenu opens underneeth editor link tool,,Administration,4.5.2,low,minor,Future Release,defect (bug),assigned,dev-feedback,2016-06-22T07:00:54Z,2020-08-05T14:22:04Z,"Sub menus of the admin menu opens underneath the editor's link tool. Possibly a z-index problem.
[[Image(http://i.imgur.com/7PMPxb6.png)]]",Stoffe1,11
Needs Dev / Bug Wrangler Feedback,46354,Update Count - Value Should Change as Updates are Applied,,Administration,5.1,low,trivial,Future Release,enhancement,new,dev-feedback,2019-02-26T22:58:59Z,2020-02-14T10:54:33Z,"The Update Count, shown in the Admin Bar, and the Admin Menu (against 'Dashboard' > 'Updates', and optionally against 'Plugins') should change to reflect the outstanding number of Updates available as Updates are Applied, whether they are applied individually on the Plugin Screen, or in bulk through the Updates Screen.
This is not a high priority issue at all, but an extremely minor cosmetic change. I suspect that Javascript could be used to change the value as an Update completes successfully in any scenario.
",Lucanos,1
Needs Dev / Bug Wrangler Feedback,45924,"Twenty Nineteen: Consider making the ""—"" divider in the header translatable.",,Bundled Theme,5.0.2,low,normal,Future Release,enhancement,new,dev-feedback,2019-01-10T20:32:57Z,2024-03-28T17:36:21Z,"Twenty Nineteen uses an em dash to separate the site title from the tagline:
[[Image(https://cldup.com/n92WHtHO2t-3000x3000.png)]]
As originally noted by @pixolin in the Twenty Nineteen GitHub repository, in non-english languages, the em dash is not always the most appropriate/common character for this situation. To address this, we should consider allowing this to be translatable.
Note that the em dash is currently inserted (and hidden when appropriate) via CSS, so this could require a bit of a reworking of that functionality.
Original report: https://github.com/WordPress/twentynineteen/issues/557",kjellr,2
Needs Dev / Bug Wrangler Feedback,56205,Twenty Twenty: background color of column can affect the inner content color,,Bundled Theme,6.0,low,normal,Awaiting Review,enhancement,new,dev-feedback,2022-07-12T13:52:54Z,2024-03-23T20:29:21Z,"Steps to reproduce :-
1. Activate Twenty Twenty theme.
2. Choose Columns block.
3. Give background-colour Accent colour from the options.
4. In inner column give a white background.
all the text under that column block is not visible because it is by default taking white colour.
For better understanding please refer to this video.
Video URL:- [https://share.cleanshot.com/vskbRyILtP0XkAq8aid4]",nidhidhandhukiya,3
Needs Dev / Bug Wrangler Feedback,33735,Reduce Duplication and Improve Comment Notification Email Functions,SergeyBiryukov,Comments,,low,normal,Future Release,enhancement,reviewing,needs-unit-tests,2015-09-04T22:55:04Z,2021-01-27T19:20:55Z,"Had touched on this in #33587.
wp_notify_postauthor and wp_notify_moderator have some duplicative code that could be eliminated and simplified.
The functions for notification also lack a filter similar to the one for displaying the comment text.
Proposing the function to show the comment in text form in the notification be separated out into its own function with a filter, and the default text be improved somewhat.
",dshanske,31
Needs Dev / Bug Wrangler Feedback,33107,Add a Menu button: when clicked the icon does not rotate around center point,,Customize,3.9,low,normal,Future Release,enhancement,assigned,dev-feedback,2015-07-24T01:47:32Z,2021-05-22T21:08:48Z,"When clicking the ""Add a Menu"" button in the Menus area of the customizer, the icon doesn't quite rotate around its center point. On some browsers like Chrome and Firefox the icon is also misaligned and pulled up too high.
Here's the icon in Firefox for example:
[[Image(https://cldup.com/01NjVg0Qh7-3000x3000.png)]]
Screenshot of the rotated icon combined with its original position:
[[Image(https://cldup.com/uO_3o712gB-3000x3000.png)]]
Here's some short videos of how the icon rotates when clicked:
Firefox 39 (OS X)
https://cloudup.com/cBb9kdrvjNZ
Chrome 43 (OS X)
https://cloudup.com/ciNZeSgbab7
Safari 8 (OS X)
https://cloudup.com/cUmIW81nSht
Safari is the only one that looks correct. The issue is partly caused by the ""add"" icon not a perfect square (it appears 1px wider in some browsers). By using the transform-origin CSS property we can improve how the icon rotates.
Because of the icon being rendered 1px wider in some browsers it's not possible to get it exact, but it's certainly an improvement. Shown below are some videos of how they would look after some CSS adjustments using the transform-origin CSS property. Best viewed at normal size with the patch, but you get the idea:
Firefox 39 (OS X)
https://cloudup.com/ca2OWHuGe8q
Chrome 43 (OS X)
https://cloudup.com/c_5AROy460x
Safari 8 (OS X)
https://cloudup.com/c1YdWYfyMqd
Also tested in IE 11 on Windows.
First patch coming.",sumobi,8
Needs Dev / Bug Wrangler Feedback,43893,The maybe_create_table() function has two definitions,,Database,,low,normal,Awaiting Review,defect (bug),new,dev-feedback,2018-04-28T14:22:56Z,2020-09-01T16:05:56Z,"The `maybe_create_table()` function has two definitions:
1. https://github.com/WordPress/wordpress-develop/blob/c71a898f784d8435c07bcf9ec9e30560dd3abe19/src/wp-admin/includes/upgrade.php#L2187-L2219
2. https://github.com/WordPress/wordpress-develop/blob/c71a898f784d8435c07bcf9ec9e30560dd3abe19/src/wp-admin/install-helper.php#L40-L70
The latter is contained within a `function_exists()` check, but this still means the function's behaviour can differ depending on which definition happens to load.
The function is not used at all in WordPress core. It (they?) should probably be deprecated.",johnbillion,5
Needs Dev / Bug Wrangler Feedback,40779,function_exists() audit in wp-db.php,,Database,,low,minor,Awaiting Review,defect (bug),new,dev-feedback,2017-05-16T14:47:06Z,2021-06-01T12:50:59Z,"A few `function_exists()` checks can be removed from `wp-db.php`, thanks to recent load order changes, probably nobody having looked in a while, and generally being afraid to break DB drop-ins:
All of these functions are in files now loaded ahead of `require_wp_db()`:
* `is_multisite` (load.php)
* `_deprecated_function` (functions.php)
* `mb_strlen` (compat.php)
Bonus:
* `mb_check_encoding()` could *maybe* be a new function in compat.php (it's used 3 times in core, using `@` or `function_exists`)
----
The only caveats are the installation process, and 10+ year-old HyperDB versions that do the old-school deep-integration thing, of directly including files – they'll need extra scrutiny.",johnjamesjacoby,1
Needs Dev / Bug Wrangler Feedback,13066,Last-Modified headers for individual comment feeds are incorrect,jgci*,Feeds,3.0,low,normal,Future Release,defect (bug),accepted,dev-feedback,2010-04-21T07:32:34Z,2022-06-28T05:18:27Z,"The WP::send_headers function currently uses get_lastcommentmodified() to set the Last-Modified header for all comment feeds. This is a problem when used for individual post comment feeds. The function gets the last modified comment across all blog posts. That means that every time a comment is posted anywhere, the Last-Modified header for ALL comment feeds is refreshed. Issues:
1. This is technically incorrect, since only the global comment feed and one specific post's comment feed have changed with the last comment (not all possible comment feeds); and
2. It means that If-Modified-Since requests for other post comment feeds will not receive a 304 response when they should do (since their content hasn't changed). On blogs with many posts and many comment feeds, this will have a large impact on bandwidth because lots of requests will receive 200 responses where 304's would have done, just because a comment was posted on some other post.
If I've understood the flow correctly, $wp_query hasn't been fully set up at the time this function is called, so changing this behaviour would require some change in the flow of things (e.g., the handling of last modified headers for feeds moves into the do_feed() function). But doing so would mean that Last-Modified headers are correct/meaningful and that many more 304 responses can be served.
Any thoughts?",solarissmoke,11
Needs Dev / Bug Wrangler Feedback,2833,wpautop breaks style and script tags,,Formatting,2.0.3,low,normal,Future Release,defect (bug),reopened,dev-feedback,2006-06-17T20:36:00Z,2024-03-21T16:25:11Z,"When I create a post in which I want to include Javascript or some styles, WordPress 'breaks'when showing those posts, because all newlines in the SCRIPT and STYLE tag are converted into BR tags.
Example:
{{{
}}}
Becomes:
{{{
}}}
And:
{{{
}}}
Becomes
{{{
}}}
This happens because wpautop adds those BR tags to the post. (As it should, just not within STYLE or SCRIPT tags.)
I've made a (temporary?) workaround for this by creating a pre and post event for wpautop, which substitute the necessary newlines by a temporary value in the pre event and placing them back in the post event. Although I think this should be incorporated in wpautop itself.
See also: http://wordpress.org/support/topic/76433 and http://wordpress.org/support/topic/76297
While searching trac I also found ticket #2346, which is about the same problem, but which was for 2.0 and self-closed by the submitter?
P.S. I have TinyMCE turned of.",Nazgul,37
Needs Dev / Bug Wrangler Feedback,48951,email_too_short is not good email validation candidate,,Mail,5.4,low,trivial,Awaiting Review,feature request,new,dev-feedback,2019-12-12T14:23:07Z,2020-08-09T18:18:07Z,"Currently, both `is_email` and `sanitize_email` will invalidate/sanitize valid emails:
{{{#!php
'admin@mailserver1'
'm@m'
}}}
Both are valid emails. ICANN just discourages using them.
The problem comes when you work with decoupled WordPress, and the front end is using custom validation that allows such emails, but WordPress doesn't so you don't have consistent behavior. Plus this is just wrong, as the official specification allows such mails.
https://en.wikipedia.org/wiki/Email_address#Valid_email_addresses
",dingo_d,1
Needs Dev / Bug Wrangler Feedback,38630,Discourage usage of legacy properties in WP_Site,,Networks and Sites,4.5,low,normal,Future Release,enhancement,new,dev-feedback,2016-11-02T21:21:20Z,2021-11-22T07:25:30Z,"Working on #38597, it was figured out that the best solution for handling problems with IDE handling of `WP_Network`s magic ID property is to rename the actual properties to reflect our current naming conventions. This enhancement will encourage to use the new conventions while still supporting the old ones for legacy code.
Let's do the same for `WP_Site`:
* `$blog_id` (string) is replaced with `$id` (int)
* `$site_id` (string) is replaced with `$network_id` (int)
* both legacy names will continue to work through magic methods",flixos90,10
Needs Dev / Bug Wrangler Feedback,19686,404 - File or directory not found,,Permalinks,3.3,low,normal,,defect (bug),new,dev-feedback,2011-12-29T19:47:45Z,2019-06-04T21:03:41Z,"We are running Wordpress using multiuser with Buddypress. Users are getting the 404 error after they click the save button in their settings.
I'm opening this ticket to report the source of the problem.
Wordpress 3.x
Buddypress 1.5
Windows 2008 R2 (IIS 7.5)
Themes installed are all Buddypress compatible and all themes seem to be affected.
All option pages are affected.
Settings are updated when the user returns to the page - despite the error. A screen shot of the error can be seen at http://blogs.cnc.bc.ca/gagel/?attachment_id=38
The source of the problem appears to be in the wp_get_referer() function on line 164 in options.php. With the variables passed to the function it should redirect the user to the page they just submitted when they updated options. Instead they get the 404 error.
The page they're redirected to appears to be the absolute path of the submitted page appended to the absolute path again (minus the domain). So it looks like this:
userblog/wp-admin/userblog/wp-admin/options-general.php?settings-updated=true
When I switch out the wp_get_referrer() function with the variable $parent_page then the redirect worked as expected.
I'm uncertain about leaving it like this as my change may have introduced issues elsewhere...
This issue is discussed at http://wordpress.org/support/topic/recuring-404-file-or-directory-not-found-error?replies=8#post-2527566",kwgagel,9
Needs Dev / Bug Wrangler Feedback,10425,Improvements to IIS7 Rewriting Code,,Permalinks,2.8.1,low,normal,,enhancement,assigned,dev-feedback,2009-07-16T14:12:09Z,2019-06-04T21:03:34Z,"#8974 introduced a set of functions and changes which allow to automatically generate Rewrite Rules for Wordpress installs running on IIS7.
There are some issues with that implementation that I think are worth being written down and discussed somewhere so here we go:
1) There's no '''""Verbose"" option''' for IIS rules; while I can't say when it would make sense to have a verbose listing of all WordPress rewrite rules in `.htaccess`/`web.config` it might be something that should be available for both systems?
2) IIS does not add '''non wordpress rules''' (`$non_wp_rules`) to the `web.config` file (`iis7_url_rewrite_rules()`) which means that any custom rewriting which plugins/users can do on apache don't work on IIS.
3) At the moment it's assumed that there is only ONE single rule needed for IIS. Especially when looking at the merge with WPMU this is going to become a problem because WPMU uses '''multiple rules'''. Every rule has to have a unique name and functions like `iis7_rewrite_rule_exists()` and `iis7_delete_rewrite_rule()` only look for one rule with name ""wordpress"". Custom Rules (see 2) also won't work without a change here. For a partial fix see misc.php in [http://trac.mu.wordpress.org/attachment/ticket/991/991-webconfig.patch Patch on MU #991])
Any comments?",bforchhammer,9
Needs Dev / Bug Wrangler Feedback,38207,Disable Trackbacks by Default Keep Pingbacks On,,Pings/Trackbacks,,low,minor,Awaiting Review,enhancement,new,dev-feedback,2016-10-01T19:21:01Z,2017-03-07T23:23:29Z,"Trackback is a manual technology. Pingback is an automated technology(automatically pings sites linked to in post content).
The question comes from me as the component maintainer and I'm opening this as a place for if the proliferation of Trackback Spam and the manual requirement has made it worth disabling the receipt and/or sending of trackbacks by default while leaving pingbacks enabled.
I continue to be committed to pingback and the concept in general, but I have to ask regarding the interest in trackback. I'm putting out a call for comment in this regard.
The only recent trackback related requests involve expensive queries to send trackbacks(See #36824).
Related #37007.",dshanske,8
Needs Dev / Bug Wrangler Feedback,46991,Stop propagation on actions or filter,,Plugins,,low,normal,Awaiting Review,feature request,new,dev-feedback,2019-04-19T12:05:17Z,2020-11-19T12:02:38Z,"It would be great to stop further filter-hooks/action-observer when we reached a state that should not continue.
This helps especially for custom implementations:
* Rejection actions that should not run.
* Return filtered values without giving other plugins the chance to change them.
All just for specific cases.
Possible implementation:
* Normal but impossible: Event-Class as wrapper reflecting whether to continue or stop.
* Semi-normal-way: Throwing a exception like `\WP_Stop_Propagation_Exception` telling WP_Hook to stop.
* Absolute absurd way: Setting a global variable like `$stop_propagation = true`
... and there may be more.",screamingdev,4
Needs Dev / Bug Wrangler Feedback,24958,Large number of revisions cause memory exhaustion,adamsilverstein,Revisions,3.6,low,normal,Future Release,defect (bug),assigned,dev-feedback,2013-08-05T17:17:59Z,2021-05-06T11:20:18Z,"This may be a edge case, but if you have a a large number of revisions, a number of things can break.
Right now the post in question has about 1,055 revisions.
Noticeably, two things are happening:
Calling wp_update_post from a plugin fails with the following error:
{{{PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 16384 bytes) in /path/wp-includes/wp-db.php on line 1228}}}
Using the new revisions API to view earlier revisions returns
""Sorry, something went wrong. The requested comparison could not be loaded.""
and the error log contains the same memory exhaustion error.
I can seem to update from the post edit screen.
This is happening with the latest stable of 3.6 and only began happening after an update, so I suspect it's something in the new revision core/api. I haven't had a huge amount of time to investigate but my guess is it's trying to load too much revision data at one time? Maybe it should only try to load X amount of revisions at once?",jshreve,17
Needs Dev / Bug Wrangler Feedback,54463,Need 'wp_sitemaps_{provider}_url_list' filter for caching.,,Sitemaps,,low,normal,Awaiting Review,enhancement,new,dev-feedback,2021-11-17T19:12:36Z,2023-03-16T15:42:25Z,"Currently, there is a `wp_sitemaps_posts_pre_url_list` filter, which can be used to build a custom URL list or **retrieve it from cache**, but there is no filter that would allow us to filter the default URL list or save it to cache.
Before returning from `get_url_list()`, it would be great to have a `wp_sitemaps_posts_url_list` filter, which would allow us to filter the default URL list or **save it to cache**.",jsmoriss,1
Needs Dev / Bug Wrangler Feedback,38863,Text change when activating a theme,,Themes,,low,minor,Awaiting Review,enhancement,new,dev-feedback,2016-11-19T02:43:03Z,2022-06-10T05:43:12Z,"When switching themes, after activating we see:
New theme activated. Visit site
[/wp-admin/themes.php?marks=168#L168, /wp-admin/themes.php, L.168]
Because it needs not to be a NEW theme, I suggest the following:
''Theme changed and activated succesfully.'' ",Presskopp,5
Needs Dev / Bug Wrangler Feedback,11297,Don't email the admin when they create a user from the backend,,Users,2.9,low,minor,,enhancement,new,dev-feedback,2009-12-01T12:05:31Z,2019-06-05T06:44:57Z,"I just created the user myself. I already know I did it. I don't need to be told again.
Emails should only be sent to the admin when a user registers themselves (if that is enabled). They shouldn't be sent when the admin manually creates a new user.",caesarsgrunt,10
Needs Dev / Bug Wrangler Feedback,25419,Add icon support for widgets on the admin page and customize screens,,Widgets,3.9,low,minor,Future Release,enhancement,new,dev-feedback,2013-09-25T17:05:07Z,2018-03-05T20:34:27Z,"With the incorporation of live widget previews (widget customizer), an available widget browser is displayed which lists all widgets along with a dashicon for each. These icons should be incorporated into the widgets admin page now, as well.",westonruter,13
Needs Dev / Bug Wrangler Feedback,37096,Unit tests for xmlrpc_getposttitle() and xmlrpc_getpostcategory() along with patch to trim and unique returned values,SergeyBiryukov,XML-RPC,0.71,low,minor,Future Release,enhancement,reviewing,dev-feedback,2016-06-14T00:24:25Z,2022-01-20T13:01:43Z,In tonight's Contrib 2 core we created this unit test for xmlrpc_getposttitle() function,pbearne,17
Needs Early Attention,56091,Using %i for table/field names in wpdb::prepare(),craigfrancis,Database,6.1,low,minor,Future Release,enhancement,assigned,has-patch,2022-06-28T19:10:52Z,2024-01-29T20:10:29Z,"Now `wpdb::prepare()` supports `%i` for Identifiers (e.g. table/field names), via commit [53575], and ticket #52506.
Queries within WP Core should use this, to ensure variables are always quoted, and avoid static analysis tools flagging unescaped SQL input (a non-`literal-string`) for the `$query` parameter:
{{{#!php
prepare( ""SELECT ID FROM $wpdb->posts WHERE post_type = %s"", $post_type );
$wpdb->prepare( ""SELECT ID FROM %i WHERE post_type = %s"", $wpdb->posts, $post_type );
}}}
I'll write a patch for the first set, but I suspect there will be a lot of changes, and they should be checked carefully.",craigfrancis,13
Needs Docs or Unit Tests,23290,"When using switch_to_blog() with a persistent object cache that lacks wp_cache_switch_to_blog() support, non-persistent groups are not maintained",,Cache API,3.0,low,normal,,defect (bug),new,needs-unit-tests,2013-01-25T05:28:44Z,2019-06-04T19:41:33Z,"If you're using a persistent object cache that lacks the new `wp_cache_switch_to_blog()` support, WordPress core `else`s into a complete cache clobbering branch. It is smart about grabbing the global groups and re-adding those after `wp_cache_init()` is called, but it doesn't do the same for non-persistent groups. Those are a hardcoded array. So if you call `switch_to_blog()`, you would lose any custom-added non-persistent groups.",markjaquith,10
Needs Docs or Unit Tests,21627,Filter for custom-background CSS selector,peterwilsoncc,Customize,3.4.1,low,minor,Future Release,enhancement,assigned,needs-unit-tests,2012-08-18T11:46:55Z,2021-05-22T17:41:50Z,"There should be an easier way for changing the css selector from body to html or any other then making your own callback.
",Horttcore,28
Needs Docs or Unit Tests,49413,wp_exif_date2ts should use Datetime and accept an optional offset,Rarst,Date/Time,,low,normal,Future Release,defect (bug),reviewing,needs-unit-tests,2020-02-12T07:57:33Z,2022-01-19T12:47:53Z,"I think this falls under the date/time component. This function should be updated to use DateTime and to accept an optional timezone offset.
Right now, this is called by wp_read_image_metadata with the result the timestamp is wrong. This is because timestamps in exif are stored without timezone offsets, usually in local time. Storing it as a timestamp was therefore a mistake in my opinion as it will always be off. We should be assuming that the time is local site time unless an optional offset/timezone string is passed in.
Separately, as newer cameras and most cell phones do store that offset, will be proposing changes for that in a separate ticket. ",dshanske,23
Needs Docs or Unit Tests,46227,Add Rel-Feed Link to Header,,Feeds,,low,trivial,Future Release,enhancement,reviewing,needs-unit-tests,2019-02-10T17:35:29Z,2021-05-13T20:03:29Z,"When the front page is not the posts page, proposing that Core add a link in the header to the actual posts page, using the rel=feed designator.
https://blog.whatwg.org/feed-autodiscovery
Example
This would allow a system to figure out where the posts page is.",dshanske,35
Needs Docs or Unit Tests,45702,make_clickable() doesn't handle linked text being a URL with spaces within it,,Formatting,,low,trivial,Future Release,defect (bug),new,needs-unit-tests,2018-12-19T07:22:42Z,2019-04-03T16:39:31Z,"As reported in https://meta.trac.wordpress.org/ticket/3998
> {{{
> https://codex.wordpress.org/Roles and Capabilities
> }}}
> turns into:
> {{{
> https://codex.wordpress.org/Roles and Capabilities
> }}}
> Looks like either `make_clickable()` or `bbp_make_clickable()` is trying to make the URL clickable without taking the existing `` tag into account.
As I've commented on the ticket:
----
This is a problem in `bbp_make_clickable()`, but is also present in `make_clickable()`.
Given the input string of `https://codex.wordpress.org/Roles and Capabilities` both will return the invalid output.
Both contain the following to correct it:
{{{
return preg_replace( '#(]+?>|>))]+?>([^>]+?)#i', ""$1$3"", $r );
}}}
But as the resulting HTML is the following it's not matched (due to the `` - which assumes that neither the linked text never has spaces or isn't a URL)
{{{
https://codex.wordpress.org/Roles and Capabilities
}}}
Adjusting the regular expression to the following does work however for this specific case:
{{{
return preg_replace( '#(]+?>|>))]+?>([^>]+?)([^<]*)#i', ""$1$3$4"", $r );
}}}
As a work around, you can remove the spaces from the linked text, which avoids it:
`https://codex.wordpress.org/Roles and Capabilities`.
----
Also created https://bbpress.trac.wordpress.org/ticket/3237",dd32,3
Needs Docs or Unit Tests,37938,Make existing HTML parsing functionality from REST API and Press This reusable,kraftbj*,Pings/Trackbacks,4.2,low,minor,Future Release,enhancement,accepted,needs-unit-tests,2016-09-03T17:08:26Z,2023-05-30T11:34:09Z,"WordPress already has an HTML parsing function in the form of WP_Press_This::source_data_fetch_fallback and its private called functions.
Suggesting this be split off so it can be used elsewhere. Specifically, my use case is over on the Ping and Trackbacks component. One of the proposals I keep advocating for is improving the presentation.
As we already have this code in WordPress that allows for parsing of HTML for images, embeds, meta tags, etc, it should be used over writing new code to do the same.
But if it were to be called right now, it would reretrieve source HTML already retrieved by the Pingback code and passed into the comment array.",dshanske,9
Needs Docs or Unit Tests,9968,dynamically adding/removing filters breaks plugins,,Plugins,,low,normal,Awaiting Review,defect (bug),reopened,needs-unit-tests,2009-05-28T23:43:11Z,2020-03-02T15:43:22Z,"noticed this while doing something similar to this:
{{{
add_action('foo', 'bar1', 10);
add_action('foo', 'bar2', 20);
function bar1() {
remove_filter('foo', 'bar1', 10);
}
}}}
in the above, bar2() doesn't get called. it is because of the usage of next()/current() to loop through filters.
attached patch uses a foreach loop instead, to make it work.",Denis-de-Bernardy,17
Needs Docs or Unit Tests,41448,Contributors shouldn't be able to change the date of their drafts,,"Posts, Post Types",2.7,low,normal,Future Release,defect (bug),new,needs-unit-tests,2017-07-26T12:33:48Z,2017-08-04T13:24:10Z,"(I'm guessing that) contributors shouldn't be able to change a post's publication date—that's why the ''Publish'' box doesn't include the date when logged in as a contributor in the first place. However, if a contributor quick edits a post in the ''All Posts'' screen, they'll be able to change the post's date.
We should remove the date field from the ''Quick Edit'' form. Or, alternatively, we should allow contributors to edit this date while they're editing a post. Either way, both screens should be consistent.",davilera,2
Needs Docs or Unit Tests,33714,Add custom post types to the 'At a Glance' widget,,"Posts, Post Types",3.8,low,normal,,enhancement,new,needs-docs,2015-09-03T20:48:57Z,2019-06-04T21:03:54Z,"This patch introduces a new argument to the `register_post_type()` function which will list a custom post type in the 'At a Glance' widget.
A few notes:
- For backwards compatibility reasons the new argument is set to false by default.
- If no menu_icon argument is set, then it will default to `dashicons-marker`. This is the same behaviour as previous.
- I've added menu_icon arguments to the core post/page post_types. I'm not sure if this has any negative implications.
- Removed a small chunk of unnecessary CSS where the dashicons were hardcoded into the styling rather than using the existing `.dashicons` classes. (Related #27414)
- `wp_dashboard_quota()` was slightly refactored due to the removal of some of the CSS.",paulwilde,11
Needs Docs or Unit Tests,44236,Maintain consistency between privacy export report and archive filenames,GripsArt,Privacy,4.9.6,low,minor,Future Release,defect (bug),assigned,needs-unit-tests,2018-05-26T00:03:07Z,2019-01-27T09:03:40Z,"Prior to r43180, the export `.zip` filename changed every time it was regenerated; after that commit, it was reused to ensure links aren't broken (see #43905).
That commit didn't do anything to the `.html` filename, though, so after the initial regeneration, the value of `$obscura` will not match between the two filenames. I don't think this presents any issues for Core, and might not for plugins either, but it seems like they should be consistent, just to be safe.
If a plugin hooks into `wp_privacy_personal_data_export_file_created`, it may reasonably assume that the filenames to match, and do something like `str_replace( '.html', '.zip', $foo )`. That seems unlikely, since both filenames are passed to the callback, but it's better to be safe than sorry.",iandunn,21
Has Patch / Needs Testing,42254,Duplicate news entries in Events & News dashboard widget,Iceable,Administration,4.8,low,minor,Future Release,defect (bug),assigned,has-patch,2017-10-17T18:15:20Z,2023-10-11T14:26:43Z,"The first item in the News widget is always the latest post from the `wordpress.org/news` blog. The next 3 posts are selected from the `planet.wordpress.org` feed, which itself includes the `wordpress.org/news` blog.
This can lead to duplicate entries:
[[Image(https://cldup.com/R67ghZqMRh.png)]]
One potential solution is to search the list of Planet feed items, to check ifany of them match the current News item. If one does, it would be removed, so that the next oldest item takes its place.
Reported by @sergeybiryukov on Slack https://wordpress.slack.com/archives/C02RQBWTW/p1507073219000123
",iandunn,21
Has Patch / Needs Testing,51190,The display of the Media Uploads settings section should be improved,,Administration,4.0,low,minor,Awaiting Review,defect (bug),new,has-patch,2020-08-30T10:06:17Z,2020-11-09T20:37:02Z,"If a plugin adds new media uploads settings fields when it's not possible to edit the uploads path/url, the table's first row unlike following is displayed in one cell instead of using the full row space. See screenshot below.
[[Image(https://cldup.com/WoQoROPrzP.png)]]
I believe checking for existing custom media uploads settings should also be checked when choosing whether to use the `colspan=""2""` attribute of the the first cell. See attached patch.",imath,1
Has Patch / Needs Testing,26960,Audit extraneous HTML/CSS for the admin menu,,Administration,,low,normal,,enhancement,new,has-patch,2014-01-30T05:56:16Z,2019-06-04T19:41:55Z,"In working on #18380, I've noticed quite a bit of cruft that has built up over time, some of it directly related to the split between colors and structure. For example, the .wp-menu-arrow is no longer visible in the 3.8 redesign, but the HTML and CSS remain. Once #18380 and #26669 are complete, we should take a closer look at this.",helen,3
Has Patch / Needs Testing,33573,Use the site icon introduced in 4.3 for the My Sites page,,Administration,4.3,low,normal,Future Release,enhancement,new,has-patch,2015-08-27T17:27:32Z,2019-05-08T22:01:42Z,"Now that site icons are available in core, we should be able to use them on the network sites/my sites list.",morganestes,13
Has Patch / Needs Testing,45944,Twenty Nineteen: Added URL in :after styles for print.css is unreliable,,Bundled Theme,5.0.3,low,normal,Future Release,defect (bug),new,has-patch,2019-01-11T19:29:13Z,2022-07-20T23:47:48Z,"The print styles for Twenty Nineteen include a little snippet meant to append the URL to links so it's visible when printed:
{{{
a[href^=http]:after {
content: "" < "" attr(href) ""> "";
}
}}}
Via: https://themes.trac.wordpress.org/browser/twentynineteen/1.2/print.css#L85
[[Image(https://cldup.com/iUgRDksax1-3000x3000.png)]]
This snippet is based on recommendations in this article:
https://www.jotform.com/blog/css-perfect-print-stylesheet-98272/
In practice, this appears to be fairly unreliable. In testing, @Joyously and I only see those URLs sporadically, and haven't been able to pin down why.
More details: https://github.com/WordPress/twentynineteen/issues/609#issuecomment-439489841
If these rules aren't working correctly, I suggest we remove them from the theme. ",kjellr,2
Has Patch / Needs Testing,58475,Twenty Twenty-Three: Aubergine variation's background implementation causes any block that impacts page height to impact header,,Bundled Theme,,low,normal,Awaiting Review,defect (bug),new,has-patch,2023-06-07T20:16:11Z,2023-06-20T16:59:53Z,"Originally reported here and moving over: [https://github.com/WordPress/gutenberg/issues/51248 GB51248]
This variation does the following for the background:
{{{
linear-gradient(180deg, var(--wp--preset--color--base) 0 min(24rem, 10%), var(--wp--preset--color--secondary) 0% 30%, var(--wp--preset--color--base) 100%)
}}}
As Justin notes, in particular, the `min(24rem, 10%)` is essentially saying to use the lower value (either `24rem` or `10%`). On pages with little content, it is pretty much guaranteed to be 10% of the `
'; print_r( $columnshidden ); echo ''; } add_action('all_admin_notices', 'echo_current_user_manageedit_pagecolumnshidden'); }}} **Output for the broken tables :** {{{ Array ( [0] => cb [1] => title [2] => [3] => ) }}} ---------- After determining that `cb` & `title` were in fact added to the `$meta_value`you need to fix the table. This will do the trick: {{{ function delete_current_user_manageedit_pagecolumnshidden() { $user_id = get_current_user_id(); $meta_key = 'manageedit-pagecolumnshidden'; if( get_user_meta($user_id, $meta_key) ) delete_user_meta( $user_id, $meta_key ); } add_action ('admin_init', 'delete_current_user_manageedit_pagecolumnshidden'); }}} ''Side-Notes:'' *`columnshidden` appears [`wp_ajax_hidden_columns()`][1] & [`get_hidden_columns()`][2] *client-side functionality appears to be here in [`common.js`][3] which checks for the [hidden table headers][4] ---------- Similar issues with the screen options can be recreated for different situations that have nothing to do with the tables. **Recreate similar issue on nav-menus.php** 1. Go to http://example.com/wp-admin/nav-menus.php 2. Uncheck all the fields in the *""Show advanced menu properties""* Screen-Options tab 3. Add the screen options filter to hide them from display: `add_filter('screen_options_show_screen', 'remove_screen_options_tab');` 4. Reload http://example.com/wp-admin/nav-menus.php All of the hidden advanced menu properties will now be broken and are all visible even though they were unchecked. I'm not sure if this is the same issue, but it appears that overall screen options have a high change of not working properly ---------- ---------- **Other-Notes** These issues of broken tables might also have to do with the same functionality problem of how screen options update/render: http://wordpress.stackexchange.com/questions/31154/wp-list-table-custom-quick-edit-box-post-meta-data-missing-and-columns-change http://wordpress.stackexchange.com/questions/123182/custom-admin-column-disappearing-when-using-quick-edit?lq=1 http://wordpress.stackexchange.com/questions/144361/wordpress-admin-wp-table-list-show-incorrectly #21016 [1]: https://github.com/WordPress/WordPress/blob/448275cce483138f53ccfa586b2d28b7fe8b0785/wp-admin/includes/screen.php#L55 [2]: https://github.com/WordPress/WordPress/blob/270a57075c290736387b6551670fde34fb3f1851/wp-admin/includes/ajax-actions.php#L1307 [3]: https://github.com/WordPress/WordPress/blob/448275cce483138f53ccfa586b2d28b7fe8b0785/wp-admin/js/common.js#L29 [4]: https://github.com/WordPress/WordPress/blob/448275cce483138f53ccfa586b2d28b7fe8b0785/wp-admin/includes/screen.php#L17 [5]: http://codex.wordpress.org/Plugin_API/Filter_Reference/manage_$post_type_posts_columns",codecandid,6 Needs Dev / Bug Wrangler Feedback,35182,Site icon URLs don't respect SSL in admin,,Administration,4.4,normal,normal,,defect (bug),new,dev-feedback,2015-12-21T12:14:56Z,2019-06-04T19:33:29Z,"It appears that the following check in `wp_get_attachment_url()`: {{{#!php if ( is_ssl() && ! is_admin() && 'wp-login.php' !== $GLOBALS['pagenow'] ) { $url = set_url_scheme( $url ); } }}} prevents `get_site_icon_url()` from using SSL for serving the icon links in the head, which results in non-HTTPS icon URLs on all admin pages: [[Image(http://kaspars.net/wp-content/uploads/2015/12/site-icon-url-https.png)]] ",kasparsd,5 Needs Dev / Bug Wrangler Feedback,42486,The Tools screen is blank for users who cannot manage categories or tags,,Administration,4.9,normal,normal,Awaiting Review,defect (bug),assigned,dev-feedback,2017-11-09T17:05:12Z,2024-01-17T17:05:15Z,"Since Press This was removed in #41689, the Tools screen is only composed of the Categories and Tags Converter. For users who can't manage categories or tags (Authors and Contributors), the Tools screen is now completely empty. Subscribers currently don't see the Tools admin menu item. The Tools admin menu item should be removed if there's nothing to display on it.",johnbillion,38 Needs Dev / Bug Wrangler Feedback,25939,"add_options_page(..., 'options.php') and 1000 vars limit",SergeyBiryukov,Administration,,normal,normal,Awaiting Review,defect (bug),reviewing,dev-feedback,2013-11-13T15:00:43Z,2023-03-08T16:36:53Z,"(Related to the discussion in #14134) There is a ""common knowledge"" in the wilderness, suggesting having this for seeing all options at once, and I guess many admins have that enabled: {{{ add_options_page('All Settings', 'All Settings', 'administrator', 'options.php'); }}} At some point, the list grows to more than 1,000 variables, and: {{{ PHP Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini. in Unknown on line 0 }}} The '''option table is corrupted''' then. In the best scenario, the tail of the table is occupied with transients. The worst - real settings. ''(having a separate table for transients sounds like a good idea to me, BTW) '' '''Now, to the point: the ""All Settings"" panel should NOT have the [Save] button. It must be read-only. ''' Alternatively - AJAX save, similar to phpMyAdmin - for each option separately. ",tivnet,4 Needs Dev / Bug Wrangler Feedback,27804,bug when updating after domain change settings,,Administration,3.8.2,normal,normal,,defect (bug),new,dev-feedback,2014-04-14T22:07:08Z,2019-06-04T19:25:28Z,"I have found the following bug that affects for sure wordpress 3.8.2 and the latest 3.8.3. I have noticed this bug when I changed my domain settings: WordPress Address (URL) and Site Address (URL) from a domain say www.mydomain.org to www.mydomain.com. In the admin panel, when I get notified of new updates to be installed, installation of wordprewss, plugins and themes seems successful but is not performed. After a bit of banging my head on the problem, for curiosity decided to switch back to www.mydomain.org and all updates were installed! It's a bit annoying doing this procedure for every new updates. Can anybody reproduce this?",robomotic,1 Needs Dev / Bug Wrangler Feedback,35561,function wp_admin_canonical_url() not using configured site url when constructing canonical url link tag,,Administration,4.4.1,normal,normal,Awaiting Review,defect (bug),new,dev-feedback,2016-01-21T16:00:36Z,2023-10-05T08:26:19Z,"I was having an issue with the wp_admin_canonical_url() function in wp-admin/includes/misc.php and I have a suggested fix I am running word press behind a reverse nginx proxy on a different box so my main site is at http://www.rammount.com and the blog is at http://www.rammount.com/blog The blog url is set in the WordPress configuration. But when you log into the admin section the wp_admin_canonical_url() function does not pick up the configured url instead it constructs the url without the /blog. This of course breaks links in the admin section, constantly redirecting things to http://www.rammount.com without the /blog by changing the following line: `$current_url = set_url_scheme( 'http://' . $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'] );` to: `$current_url = set_url_scheme(home_url(add_query_arg(array(),$wp->request)) . $_SERVER['REQUEST_URI']);` the problem is solved. the proper url is created and as such the links in the admin section that use the canonical url link function correctly. Hoping to have this change evaluated for inclusion, so that I don't have to remake this edit every time one of my designers updates the WordPress installation?",ilude,13 Needs Dev / Bug Wrangler Feedback,47690,remove_submenu_page() doesn't remove corresponding entry from $_wp_submenu_nopriv,johnbillion,Administration,,normal,normal,Future Release,defect (bug),reviewing,dev-feedback,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 Needs Dev / Bug Wrangler Feedback,47788,send_headers hook does not work in wp-login or wp-admin,,Administration,5.2.2,normal,normal,Awaiting Review,defect (bug),new,dev-feedback,2019-07-28T10:18:17Z,2019-10-20T11:56:12Z,"Assume that I want to start using CSP (Content Security Policy) on my website. I add this to my theme's functions.php: {{{#!php body.blog- li#wp-admin-bar-site-name > a.ab-item:first-of-type, body.blog- #wpadminbar .ab-top-menu > li#wp-admin-bar-site-name.menupop:hover > .ab-item:first-of-type, body.blog- #wpadminbar .ab-top-menu > li#wp-admin-bar-site-name.menupop.hover > .ab-item:first-of-type { font-size: 0; // safely hide default text background-image: url(""""); background-size: ; background-position: center; background-repeat: no-repeat; min-width: 120px; } 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 Needs Dev / Bug Wrangler Feedback,19691,Cannot modify admin messages for /wp-admin/edit.php,,Administration,3.3,normal,normal,,enhancement,new,dev-feedback,2011-12-30T02:10:01Z,2019-06-04T19:22:50Z,"The admin console messages output on line `264` of WordPress 3.3's file `/wp-admin/edit.php` are not filterable. This causes problems when added row actions need to HTTP GET from to WordPress to modify a post and then display an appropriate message complete with a revert link ''(like the ""Trash"" link does.)'' An example use-case could be for a custom post type used for both quotes and invoices where a row action might be ''""Convert Quote to Invoice""'' where you'd want a message and link displayed at the top of the admin after similar to this: - ''Quote #{$post_id} converted to Invoice. __Revert__'' Currently the only way to accomplish this is to pick hooks before and after the messages are output and use PHP's output buffering; clearly not a ''""best practice""'' approach. In order to address this I'm proposing an '''`'admin_messages'`''' filter hook to run just before the messages are output: {{{ $messages = apply_filters( 'admin_messages', $messages ); }}} However, since messages are output in numerous locations in the WordPress admin it seemed best to add the hook in every location where messages are output, which is what my patch does. Thus a hook can look at `$pagenow` or `get_current_screen()` to decide it is needs to do anything. Also while searching for places in the admin code that echo messages I found `$messages` are sometimes an array of HTML where the entire array is echoed and other times the $messages are an array with an index passed via `$_GET` and only one message will be displayed. For those cases I created another hook '''`'admin_message'`''' ''(note that this hook name is singular)'': {{{ $message = apply_filters( 'admin_message', $message, $messages, $_GET['message'] ); }}} I really only found a specific need for `/wp-admin/edit.php` today, but it seemed that it would be better for consistency if all messages were made hook filterable. That's why I created a larger patch when all my use-case needs is one new line. Looking forward to your feedback. ",mikeschinkel,7 Needs Dev / Bug Wrangler Feedback,58781,Change wording of field description for tagline,,Administration,,normal,normal,Future Release,enhancement,new,dev-feedback,2023-07-11T06:26:54Z,2024-01-19T06:33:34Z,"This is a follow-up to #57675 I [https://core.trac.wordpress.org/ticket/57675#comment:28 raised my concerns there], but it was too late in the cycle. So here we go: These are my concerns about the solution we use now: 1) The example is misleading, the tagline should be meaningful, and just not like in the example Using a unique and descriptive tagline is important for search engine optimization (SEO) purposes, as it helps convey the website's purpose and relevance to both search engines and visitors. 2) The “ and ” could be misunderstood so people would enter quotation marks into the tagline. This can impact the visual presentation and readability of the tagline to visitors. To keep the iconic phrase ""Just another WordPress site"" while being informative at the same time we could formulate: In a few words, explain what this site is about. We're sure your site is so much more than ""Just another WordPress site""",Presskopp,13 Needs Dev / Bug Wrangler Feedback,44837,Coding Indentation Issues,,Administration,4.9.8,normal,minor,Awaiting Review,enhancement,new,dev-feedback,2018-08-24T09:00:25Z,2019-04-01T22:07:36Z,"I am seeing in wp-admin files that coding indentation is missing like this file edit-tags.php The codes are written like this {{{ }}} which needs to be indented properly to make it more understandable. This can be check in other files as well where we are writing HTML as well as PHP. In this tickets preview how exactly the code is written so I am adding a screenshot as well https://prnt.sc/kmcjeu",prashantvatsh,2 Needs Dev / Bug Wrangler Feedback,48641,Discussion: links that look like buttons (and vice versa),,Administration,,normal,normal,Future Release,enhancement,new,dev-feedback,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 `