__group__ ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter Future Releases 39254 When in Customizer Preview, starter content posts are not displayed in the loop westonruter* Customize 4.7 normal normal Future Release defect (bug) accepted needs-unit-tests 2016-12-12T21:03:24Z 2020-05-27T04:33:56Z "As discussed in [https://wordpress.slack.com/archives/core-customize/p1481567934000409 Slack], posts in Starter Content aren't appearing in the posts list. Being able to display the bundled content, specifically posts, is key for an improved user experience when configuring a new theme. Posts give structure to the theme, allowing users to see exactly how the theme will look with content. This would also allow theme developers to completely match the content bundled with the theme to the content on the theme’s demo site. This helps address the popular complaint amongst WordPress users that a newly installed theme looks nothing like the demo." tiagonoronha Future Releases 33371 Undefined Indexes for Movable Type and TypePad Importer. westi* Import normal normal defect (bug) accepted reporter-feedback 2015-08-14T08:25:25Z 2019-12-06T05:07:37Z "Display notice in ""Assign Authors"" ( WP_DEBUG = true ) . {{{ Notice: Undefined index: upload_type in movabletype-importer/movabletype-importer.php on line 233 Notice: Undefined index: id in movabletype-importer/movabletype-importer.php on line 248 }}}" mt8.biz Future Releases 38079 Add hooks before output for each action in wp-login.php voldemortensen Login and Registration 4.7 normal normal Future Release enhancement assigned reporter-feedback 2016-09-17T19:13:19Z 2017-10-03T05:59:58Z "7 years ago, in #9682, `wp-login.php` was made more pluggable. The thing is, if you just want to change the look (as my plugin ""Theme My Login"" does), you also have to replicate the logic. Having an action that fires just before the `login_header()` call in each case of the action handler switch should be sufficient. One such hook is already present for one action: `lost_password`. However, the hook `register` is already in use for the register link as is the format `{$action}_form`. So, I propose using `pre_{$action}_form`. Patch incoming." jfarthing84 Future Releases 45874 Content Section is overlapping the menu background valentinbora* Administration 5.0.2 normal trivial Awaiting Review enhancement accepted reporter-feedback 2019-01-09T12:36:13Z 2024-01-17T20:19:39Z "Hi, Just uploading some content into WordPress dashboard and saw a little layout bug, I'm not sure if it is kept like this but I thought, maybe it should be behind the menu background completely. As I have uploaded a screenshot, once the menu height finishes then the content is showing below. it should be behind the menu bar. [[Image(http://ahmadgulzar.com/wpscr.png)]] it can be fixed by just changing z-index of #adminmenuback from 1 to 3 {{{ #adminmenuback { position: fixed; top: 0; bottom: -120px; z-index: 3; } }}} Thanks " ahmadgulzar Future Releases 49714 Explore UI for destructive controls & contexts Travel_girl Administration normal normal Future Release enhancement assigned reporter-feedback 2020-03-27T16:03:04Z 2024-01-29T15:38:05Z "After considering ticket #49603, we think that WordPress should take a look at the consistency of informing users when they are in a destructive context and when a control will have destructive consequences. In general, we have a standing expectation that these controls will be red & have text that clearly indicates the action to be taken, but this should be reviewed for consistency. Reviewing #49603 showed that the 'Force Erase Personal Data' control is blue, which doesn't match expectations. The intention of 49603 is to draw attention to the fact that the 'Erase Personal Data' screen is entirely dedicated to destructive actions. While using a background color to indicate this may not be the ideal choice, the concept is well worth exploring. Summary: review destructive actions & contexts to ensure clarity and maximize error prevention. " joedolson Future Releases 34475 get_comment_link incorrect page number in returned url. SergeyBiryukov Comments 4.3.1 normal normal Future Release defect (bug) reviewing needs-unit-tests 2015-10-28T16:36:42Z 2019-10-03T22:15:05Z Since 4.3 core update the get_comment_link function returns incorrect page numbers for paginated comments. Have tried using default twentyfifteen theme with no plugins enabled and issue still persists. Property118 Future Releases 45694 Undefined Index: caption_id SergeyBiryukov Media 5.0.1 normal normal Future Release defect (bug) reviewing reporter-feedback 2018-12-18T21:41:16Z 2019-01-16T05:56:42Z "Discovered this randomly on a local project. {{{ Notice: Undefined index: caption_id in /var/www/html/wp-includes/media.php on line 1572 }}} Discovered with PHP 7.2.10 and WordPress 5.0.1 It's just a warning but one nonetheless. Attached will be the patch." Soben Future Releases 52464 The value of argument passed to the update_option_new_admin_email() is not a valid email. SergeyBiryukov Networks and Sites normal normal Awaiting Review defect (bug) reviewing needs-unit-tests 2021-02-07T12:08:54Z 2022-09-29T17:38:21Z "While creating a patch for ticket #43706, I found out that the function `update_option_new_admin_email()` is responsible for the template. It does accept two parameters, however, the first parameter `$old_value` does not seem to get the correct value. When checking the value, it holds the value `new_admin_email` instead of the old email address. Thanks!" tremidkhar Future Releases 52820 Possible logic error in wp_trim_excerpt() SergeyBiryukov Posts, Post Types normal normal Future Release defect (bug) reviewing reporter-feedback 2021-03-15T16:26:58Z 2022-04-30T05:23:17Z "https://core.trac.wordpress.org/browser/tags/5.7/src/wp-includes/formatting.php#L3845 Reading this code, it looks like the `wp_trim_excerpt` filter's `$raw_excerpt` parameter will be empty if `$text` as supplied to the function is empty. This should be the value of `$text` at L3824 should it not? Or do I mis-understand?" theMikeD Future Releases 52458 "WordPress version check is passing ""false"" value to ""esc_url"" causing errors (in the logs)" SergeyBiryukov Upgrade/Install 5.3 normal normal Future Release defect (bug) reviewing reporter-feedback 2021-02-05T22:26:28Z 2021-08-19T21:06:47Z "At least one code-path that leads to this situation is via the following line: https://github.com/WordPress/wordpress-develop/blob/master/src/wp-includes/update.php#L197 The response of WordPress.org for core does not return a value for all ""package"" entries. Thus passing `false` to the `esc_url` array_map. {{{#!php Array ( [full] => https://downloads.wordpress.org/release/wordpress-5.6.1.zip [no_content] => https://downloads.wordpress.org/release/wordpress-5.6.1-no-content.zip [new_bundled] => https://downloads.wordpress.org/release/wordpress-5.6.1-new-bundled.zip [partial] => [rollback] => ) }}} In the esc_url function, the value is checked for an empty string, but no type safety is applied. The subsequent logic calls `ltrim` which expects the input to be a string. If this is not the case, there will be an error thrown about this. This has been added on July 1st, 2019. See: https://github.com/WordPress/wordpress-develop/commit/78e096fe98531d0799c42705d1329f808e9ee944 " jipmoors Future Releases 60397 Invalidate opcache after theme / plugin updates seebeen Upgrade/Install 6.4.2 normal normal Awaiting Review defect (bug) assigned dev-feedback 2024-01-31T10:10:01Z 2024-01-31T12:29:13Z "Depending on the server opcache configuration, there is a high possibility of getting an Internal Server Error, or similar after updating a plugin / theme. Specific opchache settings I've verified that trigger the error are: {{{ [opcache] opcache.enable=1 opcache.enable_cli=1 opcache.memory_consumption=256 opcache.interned_strings_buffer=24 opcache.max_accelerated_files=130987 opcache.max_wasted_percentage=2 opcache.use_cwd=1 opcache.validate_timestamps=1 opcache.revalidate_freq=5 opcache.revalidate_path=0 opcache.save_comments=1 opcache.enable_file_override=1 }}} Error happens because validate_timestamps is set to 1 and revalidate_freq is greater than 0. This means that after plugin update, error 500 will stay for up to revalidate_freq seconds due to invalid opcache. This can be mitigated by adding a opcache_invalidate or opcache_reset call upon successful update." seebeen Future Releases 34796 Facing an issue when using wp_remote_get with streams (non-blocking mode) rmccue* HTTP API 4.3.1 normal normal defect (bug) accepted reporter-feedback 2015-11-26T22:45:06Z 2019-06-04T19:53:49Z "On some hosting providers (like wpengine.com) I've encountered an issue when using wp_remote_get with streams (non-blocking mode) which on the other hand uses PHP native functions stream_socket_client, stream_context_create and stream_set_blocking. The issue is that HTTP request (non-blocking) never succeed, it just hangs/stuck on the initial call of stream_socket_client and neither errors or exception are generated. I've investigated the issue deeper and it seems that many people over the Internet have it. The issue can be resolved after invoking stream_socket_client we put usleep(5000) and then stream_set_blocking($handler, 0). It seems that the initial time for stream_socket_client is not enough and that's why it needs more time in order to process the HTTP request. PHP Bugtracker https://bugs.php.net/bug.php?id=64803 WordPress 4.3.1 PHP 5.5 Is it possible to add additinal parameter on wp_remote_get or if there is any other way to achieve setting usleep parameter will help us to precisely configure HTTP requests. I am adding patch file" bangelov Future Releases 43178 Rethinking what “captions” means for video postphotos Media 5.1 normal normal Future Release enhancement assigned reporter-feedback 2018-01-29T16:32:59Z 2023-10-19T18:38:35Z "'''Because different users will use the word ""caption"" in different ways, it would be helpful to look at reducing this term in WordPress media and clarifying all media terms as a whole.''' Captions carry a meaning in the video industry that is closely related to subtitles. It's recommended that we change how we describe our images, videos, and other media used within WordPress. ''Note: For architectural reasons, the field data should be left alone, but we need a better label for the associated meta. I also talked about this a bit in #31177'' This proposal further explores the messy language in media attachments and focuses on clear description so that all users can understand them, including clarifying WordPress' use of video subtitles. A proposal to revising these terms is below. Images 1) Wherever images use {{{data-setting=""title""}}} - instead of ""Title"" the English label should read ""Media Title."" 2) Wherever images use {{{data-setting=""caption""}}} - instead of ""Caption"" the English label should read ""Image Caption."" Because the specific term ""photo captioning"" describes a widely-used industry term, it should be clarified here but not removed. 3) Wherever images use {{{data-setting=""description""}}} - instead of ""Description"" the English label should read ""Longer Description."" This is because theme developers do not output this data beyond attachment pages and having three ill-described content areas - alt, caption, description - is an anti-pattern to describe what these images. Videos 1) Wherever images use {{{data-setting=""title""}}} - instead of ""Title"" the English label should read ""Media Title."" 2) Wherever video use {{{data-setting=""caption""}}} - instead of ""Caption"" the English label should read ""Media Description."" 3) Wherever images use {{{data-setting=""description""}}} - instead of ""Description"" the English label should read ""Longer Description."" This is because theme developers do not output this data beyond attachment pages and having three ill-described content areas - alt, caption, description - is an anti-pattern to describe these images. By adjusting these terms and exposing utility of the meta values, this level of clarity will greatly enhance the ability for all users, especially those helping create content for both multi-lingual and Deaf audiences, to understand the meta values in managing media work without the need to read documentation. Goals: 1. Because videos are reused on separate posts and all subtitled videos should contain this as a part of their output, create a meta value (or some other object type) that stores associated SRTs per language. 2. Allow for a better way for all videos that stores the associated SRTs to be associated with a language or as another kind of subtitle track - i.e. commentary, descriptive text, etc. 3. Allow videos uploaded at the same time with the same subtitle file name (or in a language structure) to be associated with each other. Assume the default core language for videos with no LANG code and associate the only subtitle as belonging to default core’s. (If there’s only one SRT with no lang suffix, it’s probably a caption.) If we leave the existing labels as-is, new and old users will both continue to put the wrong information in because of the lack of context to each field. Whatever fix we decide on, this should also be further adjusted in each target language that WordPress core is released in." postphotos Future Releases 60003 PHP error in wp_match_mime_types() pbearne General 6.4 normal normal Awaiting Review defect (bug) assigned reporter-feedback 2023-12-02T09:04:05Z 2024-02-15T16:23:51Z "PHP ERROR: `Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /.../wp-includes/post.php on line 3308` FIX: change LINE 3308 to: {{{ if ( $real && preg_match( ""#$pattern#"", $real ) ^^^^^^^^^ }}}" argaliano15 Future Releases 60820 Improve wording of the 'Login Details' mail marybaum Text Changes normal normal Awaiting Review enhancement assigned reporter-feedback 2024-03-21T15:26:56Z 2024-03-22T11:15:38Z "When creating a new user (as admin), they receive a very short e-mail in which a user name and a link are simply sent without comment. I would like the text of this e-mail to be a little more informative. The password reset emails are a good example. There we write ""Someone has requested a password reset for the following account"", state the site name, the user name and then write the link. The text of the login detail mail could read: ""Someone has created an account for you in their website foo.com. Your username is foo.name. To set your password, visit the following address: ..."" " pixelverbieger Future Releases 46155 Responsive images (srcset) not working on cropped files. joemcgill General normal major Awaiting Review defect (bug) assigned reporter-feedback 2019-01-31T02:51:55Z 2019-05-15T13:36:42Z "When adding images to a page or using wp_get_attachment_image() function in a page template, responsive images do not get generated if the image size is set to 'crop' (e.g. thumbnail or a custom size). Basically, srcset is not added in html. Other sizes are OK though. To reproduce the bug, make sure an image size is set to 'crop'. Then upload a new image and add it to a page selecting a **full size first**. Update the page and then remove the image from the page. Update and then insert it again and this time make sure to select the **cropped image size**. Update. You will see that a standard tag is generated in the frontend. E.g.: {{{ }}} instead of {{{ }}} I have tested it on WP 5.0.3 and even tried downgrading to 4.9.9 and 4.9.8 but it's the same. Tested with all plugins deactivated and on the default twenty-something theme. I have tried it on PHP 7.1, 7.2 and 5.6. Tested both Guttenberg and the classic editor." olgri Future Releases 59550 "Attribute ""loading"" with value ""lazy"" is missing" joemcgill Media 6.3 normal normal Awaiting Review defect (bug) reviewing reporter-feedback 2023-10-05T14:27:06Z 2023-10-06T08:14:04Z "Hello, we just encountered an error with the wp_get_attachment_image() function. Since version 6.3 the loading=""lazy"" attribute isn't present in the image tag anymore. We upgraded the versions one after another and detected a change with the update on version 6.3. The documentation states ""Defaults to 'lazy'"" which is wrong now. This is a serious issue for the performance of many sites that rely on the default lazy loading behaviour by using wp_get_attachment_image(). For testing this we just echoed the result of wp_get_attachment_image() with an example static attachment ID from our media library." r3dluke Future Releases 35092 Remove crop check in wp_prepare_attachment_for_js() for sizes joemcgill Media 3.5 normal normal defect (bug) reviewing reporter-feedback 2015-12-15T02:20:36Z 2019-06-04T20:20:01Z Currently only cropped images generated on the fly are displayed. This due to a {{{! $downsize[3] }}} check. This change was made in #22598 and with the patch supplied I deleted this check. then medium/large does show up. markoheijnen Future Releases 58272 Accessibility issues with core embed block's handling of Flickr and TikTok joedolson* Embeds 6.2 normal normal Future Release defect (bug) accepted reporter-feedback 2023-05-08T21:57:00Z 2024-02-05T20:43:59Z "There is an accessibility error with the embed iFrame for Flickr and TikTok. Specifically, that the iFrame is missing a title, with no ""title"" attribute, or the ""title"" attribute being empty. Site Improve is requesting that the frame provide an attribute titie="""", and to add a description of the content in the title. There is also an ""Link without a text alternative"" message for the link, stating that ""links should always have a text alternative"". In order for a link to be readable by screen reader users links must all contain either plain text, or in the case of a linked image, alt text describing where the link goes. If the linked image contains text, a good general rule is to make the alt text the same, or similar to the text in the image. The same issue goes with the inline (iframe) frame, that does not include a text altnerative. All three of these issues will lower page accessibility for those using screen readers. Thanks for your help. " markcmorantt Future Releases 23436 Media Gallery - Cropping Image and then Cropping a thumbnail from that crop doesn't work. joedolson* Media 3.5 normal normal Awaiting Review defect (bug) accepted close 2013-02-10T17:20:00Z 2022-12-07T16:05:48Z "'''A recipe for repeating the bug behavior:''' Navigate to Library in the admin sidebar. Click ""Add new"". Drag the 800x480 copy of this or any image to the drag and drop area: http://en.wikipedia.org/wiki/File:Cheese_platter.jpg (I suggest this image for ease of recipe duplication and best explanation.) After the blue status bar has completed, ""Edit"" to bring the media edit window up in a new tab. Click ""Edit Image"" below the actual image. Drag anywhere inside the image to create a cropping box. In the ""Image crop"" pane, set the crop area to 500px width, 100px height. Drag the cropping box so that the fancy toothpick is as far left as possible along the horizontal axis of the cropping box, but centered vertically. Click the ""Crop"" icon. Click ""Save"". Click ""Update"". Click ""Edit Image"" once again. Drag inside the newly-cropped image again to create a new cropping box. In the ""Image Crop"" pane, change the cropping dimensions to 150 x 100. Drag the box so the fancy toothpick is somewhere in the left third within the crop boundary. '''Important:''' In the thumbnail settings pane, set ""Apply Settings to:"" '''Thumbnail'''. Click the ""Crop"" icon. Click ""Save"". Click ""Update"". Click ""Library"" in the admin sidebar. The newly preferred thumbnail for our previously-cropped image does not save. Thumbnail remains default, based on center of previously-cropped image. Instead, you will see a small wheel of cheese sliced into six wedges with garnishes for the thumbnail, even though we chose the part with the fancy toothpick." gr33nman Future Releases 23562 Using Speech Recognition Software with the Add Media Panel joedolson* Media 3.5.1 normal normal Future Release defect (bug) accepted reporter-feedback 2013-02-20T16:06:02Z 2023-08-24T13:36:57Z "Linked to #23560 this ticket specifically concerns the speech recognition user's accessibility experience of the Add Media functionality. I'm using Dragon Naturally Speaking with IE9 on Windows 7 - a typical setup as Dragon works best with IE. Within the Edit Post screen I can use Dragon to action the Add Media link successfully. The command in Dragon for such an action is ""Click Add Media"". This works, but then I run into the following problem: * With the exception of Set Featured Image, none of the other links on the panel appear to be directly accessible with Dragon. * If I select Set Featured Image I can't action any of the other links. Dragon users can use voice commands to replicate pressing the tab key. The experience then mirrors that outlined in #23560 - but of course this cannot be used to select the images or other files. It is possible for Dragon users to interact with screens using mouse commands but it is an incredibly laborious and time consuming process - used only as a last resort. If one of the images is selected, the information panel for that images opens to the right. Unfortunately none of the input fields (for title, alt, etc) are directly available to Dragon. Ironically, the Insert Into Post button can be accessed directly with a voice command. Some investigation needs to be done as to why most of the links and input fields cannot be directly accessed by Dragon when the panel is opened. This is a parallel with the situation on the Theme Customizer panel. It is interesting that the Set Featured Image link and the Insert Into Post button '''can''' be directly accessed. What is different about them? " grahamarmfield Future Releases 31199 Potential reference to unset variable in get_bulk_actions (WP_Posts_List_Table) chriscct7* Administration normal normal Future Release defect (bug) accepted reporter-feedback 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 Future Releases 43122 customize.php fails to load with default changeset_uuid bpayton Customize 4.7 normal normal Awaiting Review defect (bug) assigned reporter-feedback 2018-01-18T00:46:13Z 2021-05-30T17:26:42Z "I am seeing a rare condition where users are unable to load the Customizer with no specified changeset and see the message ""Cheatin, uh? This changeset cannot be further modified."" In all cases, I am seeing two `customize_changeset` posts with the same GUID post name, one with draft status and the other with published status. When WP_Customize_Manager attempts to find a changeset to load by default, it finds the draft with the GUID, and when it attempts to load the post, it finds the published post with the same GUID and dies with the message mentioned above. I read WP_Customizer and theorized how this could be happening but have no theory worth mentioning. Still, this seems like some kind of race condition." bpayton Future Releases 43076 current-menu-item for archive menu item on singular page audrasjb Menus normal normal Future Release defect (bug) assigned reporter-feedback 2018-01-12T09:51:43Z 2020-01-17T00:02:45Z If I have CPT with archive and singular page and I add to menu url to archive and I go to singular page of CPT then should be add current-menu-item to menu item of archive sebastian.pisula Future Releases 47139 function wp_logout_url urlencode causes issues in items wrap nav walker. audrasjb Menus normal normal Awaiting Review defect (bug) reviewing reporter-feedback 2019-05-06T14:42:44Z 2019-08-02T11:09:52Z "Hi The function wp_logout_url returns a encoded logout url. This used to work before without any issues. {{{ string(128) ""http://wprtdev.tst/wp-login.php?action=logout&_wpnonce=72f1be58e4&redirect_to=http%3A%2F%2Fwprtdev.tst%2F%3Floggedout%3Dtrue"" }}} But if you parse this url as a list element in the menu walker you get a warning and error {{{ Warning: sprintf(): Too few arguments in /var/docs/wprtdev.tst/public/wp-includes/nav-menu-template.php on line 261
}}} because the walker uses %3$s for the items wrap and the encoded url has %3Afor : and %3F for ? It is not possible to add a logout url into the items wrap like this {{{ 'items_wrap'=>'