__group__ ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter Slated for Next Release 58051 Attachment custom fields not rendered after upload antpb Media 6.2 normal normal 6.6 defect (bug) assigned 2023-04-02T02:23:40Z 2024-03-06T16:20:39Z "This is a follow-up to #40909. Attachment custom fields added via `attachment_fields_to_edit` are no longer rendered just after an image is uploaded. Clicking away and back will restore the custom field markup, but is quite inconvenient." trepmal Slated for Next Release 60548 Image editor: improve the browsePopup function joedolson* Media 6.3 normal normal 6.6 defect (bug) accepted 2024-02-15T14:10:11Z 2024-03-06T16:59:58Z "While auditing all the remaining jQuery deprecations still to address in core, I noticed a couple things that offer room for improvements in the `browsePopup` function of the core image editor. 1. The `browsePopup` function uses the `window.event` property, which is deprecated and should not be used. This is the `global` event. Instead, the event should be passed as a function parameter. Aside: instead of using inline events, it could have been better to consider a more modern approach. 2. When using the keyboard to navigate the items in the 'Image rotation' dropdown menu, the page scrolls. See attached animated GIF. There's some code in place to prevent page scrolling you may need to reduce your viewport height. See [55919] / #50523 " afercia Slated for Next Release 60666 Unwanted section appears as a sidebar in 'Create gallery' section joedolson* Media 5.0 normal normal 6.6 defect (bug) accepted 2024-03-01T09:04:35Z 2024-03-06T16:46:30Z "Unwanted section with 'Actions' and 'Create gallery' texts appear in the sidebar of Media Library and nothing happens on selection or click of the texts. To find the issue, please go through the below steps. 1.From the 'File' block add the block 'Gallery', then select Media Library. 2.Unwanted sidebar section with the specified texts appears." ukdrahul Slated for Next Release 37287 wp_print_admin_notice_templates() does not use _n*() for plural forms swissspidy I18N 4.6 normal normal 6.6 defect (bug) assigned 2016-07-05T12:23:24Z 2024-02-28T14:25:48Z "Function wp_print_admin_notice_templates() (https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes/update.php#L615) does not properly use _n() and related functions for plural forms of its strings. It just makes a simple if (count ===1) check and uses two different strings - one for singular, one for plural form. This presents a problem when translating into languages that have more than one plural form, or more complicated rules for singular form usage. For example, in Lithuanian we also use singular form for 21, 1241 and any other number that ends with 1 (except for 11). And we have two plural forms - one for numbers ending with a zero, another for everything else. In current situation we can not have a proper translation here. " ideag Slated for Next Release 60647 Script Modules: Allow modules to depend on existing WordPress scripts jonsurrell Script Loader trunk normal normal 6.6 feature request assigned 2024-02-27T15:40:59Z 2024-03-21T08:07:18Z "Script modules cannot depend on existing scripts such as `wp-url`, `wp-i18n`, or `wp-api-fetch`. Script modules should be able to leverage the functionality available in existing scripts." jonsurrell Tickets Awaiting Review 57365 """Attempt Block Recovery"" functionality broken for buttons ""Convert to.."" click" Editor 6.1.1 normal normal Awaiting Review defect (bug) new 2022-12-21T12:16:37Z 2022-12-30T05:56:34Z "When i edit the HTML manually and click away, the ""Attempt Block Recovery"" error appears. == BUG: **Clicking on the ""''Convert to HTML''"" or ""''Convert to Blocks''"" does nothing.** [[Image(https://i.imgur.com/fzLTpaH.png)]] The button ""Attempt Block Recovery"" itself works and reverts the action to the previous state before I edited the html. I also screenshotted the red text from the console: [[Image(https://i.imgur.com/1l0PjIv.png)]]" mikulabc Tickets Awaiting Review 60082 """Copied"" tooltip should be hidden when another attachment URL is copied (in list mode)" Media 6.0 normal normal Awaiting Review defect (bug) new 2023-12-15T13:05:00Z 2024-03-12T15:39:27Z "In the media list view, clicking the ""Copy URL"" action link displays previously clicked ""Copy URL"". The previously clicked row showing ""Copied!"" when hover the media again. === Environment - WordPress: 6.4.2 - PHP: 8.2.0 - Server: Apache/2.4.54 (Unix) OpenSSL/1.0.2u PHP/8.2.0 mod_wsgi/3.5 Python/2.7.18 mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_perl/2.0.11 Perl/v5.30.1 - Database: mysqli (Server: 5.7.39 / Client: 8.2.0) - Browser: Firefox 119.0 (macOS) - Theme: Twenty Twenty-Four 1.0 - MU-Plugins: None activated - Plugins: * WordPress Beta Tester 3.5.5 === Steps to Reproduce 1. Go to media library 2. Click ""Copy URL"" of one of the media. 3. Click ""Copy URL"" of another media. 4. The previously clicked row showing ""Copied!"" when hover the media again. === Expected Results 1. The previously ""Copied!"" tooltip should be close after clicking the next one. === Actual Results 1. The previously clicked row showing ""Copied!"" when hover the media again." jayadevankbh Tickets Awaiting Review 40899 '&' Is always escaped in the JavaScript template. General 4.7.5 normal normal Awaiting Review defect (bug) new 2017-06-01T08:41:12Z 2020-09-08T13:05:47Z "When I tried the JavaScript template, '&' was always escaped. Source: {{{ }}} Rendering: {{{

&

Unscaped: Wo&r'l""d

Escaped: W<i>o</i>&r'l""d

}}} While checking the interpolation of the variable, '&' was always converted to '& amp;'. Is this a specification or a bug? " tmatsuur Tickets Awaiting Review 35887 Adding multiple media to post - selecting image size Media 4.4.2 normal normal Awaiting Review defect (bug) new 2016-02-20T12:03:10Z 2023-10-25T04:35:24Z "When clicking ""Add Media"" to add images to a post, you can select multiple images. With all images selected, logic follows that if you change the ""ATTACHMENT DISPLAY SETTINGS"" size from default ""Medium"" to ""Full Size"", that all selected images would have the same setting changed, but when you add them, only the one image that was highlighted is actually ""Full Size"" and the rest which were selected, but not highlighted, are still ""Medium"". I think when adding multiple media, all should be changed to size that is selected in ""ATTACHMENT DISPLAY SETTINGS""." myburgh.bernard@… Tickets Awaiting Review 31416 An accessibility issue with the Publish metabox Posts, Post Types 4.1.1 normal normal Awaiting Review defect (bug) new 2015-02-22T22:03:33Z 2018-12-09T20:28:05Z "Taking a closer look at the Publish metabox for posts I realise that it has what I would call a bug. Take a look at the image attached. It tells me a post is published, while it's still asking for confirmation to be published. This screen shows up when first a post is set to private -and so gets published privately- and next is set to public, without hitting the 'Publish' button. The post is actually published privately, which should show up as it's status, as it normally does. It tells me though it's published (which impies it should be published publicly). I stumbled upon this, while I was searching for a more intiutive solution for inexperienced posters on one of my sites to post privately. I found two threads in forums which adress this issue: https://wordpress.org/support/topic/how-to-set-new-post-visibility-to-private-by-default?replies=14 http://wordpress.stackexchange.com/questions/118970/set-posts-of-a-custom-post-type-to-be-private-by-default Neither of threads mention (or seem to be aware?) of this shortcoming, while both try to solve the same issue I'm having. I question whether this problem can be solved, while the Publish metabox has such shortcomings. I hope that by fixing this little bug, it might actually be possible to create a more accessisble Publish metabox for guests on a site, maybe by a hack or plugin, but preferably within the WP core files. [[Image(http://www.basbva.nl/wp-content/uploads/2015/02/publish-metabox-bug.jpg)]]" basbva Tickets Awaiting Review 58432 "BUG: Custom Core Block Variation details not updated in ""Settings Sidebar"" section" Editor normal major Awaiting Review defect (bug) new 2023-05-31T06:10:30Z 2023-06-13T16:31:52Z "**Issue:** When adding a custom **core block variation**, the details ( title, icon, description ) are not updated in the **""Settings Sidebar""** section. Hence there is no way to distinguish between custom core block **variations** and core **blocks** once a block is added. **How to reproduce:** 1. Add support for block variations to your existing theme. {{{ function prefix_editor_assets() { wp_enqueue_script( 'prefix-block-variations', get_template_directory_uri() . '/assets/js/blocks/block-variations.js', array( 'wp-blocks' ) ); } add_action( 'enqueue_block_editor_assets', 'prefix_editor_assets' ); }}} 2. Create a custom **core block variation** {{{ wp.blocks.registerBlockVariation( 'core/group', { name: 'card-group', title: 'Card group', description: 'A group with card styling', label: 'Card group', icon: 'wordpress', attributes: { className: 'card-group', }, innerBlocks: [ [ 'core/heading', { content: '' } ], [ 'core/paragraph', { content: '' } ], ] } ); }}} 3. Check inside editor for new core block variation. 4. Add new core block variation and check the siderbar with the block selected. Attaching pic & screen recording of the issue as well. Note: I used the following tutorial by **Carolina Nymark** to create the variation https://fullsiteediting.com/lessons/block-variations/ " deepakvijayan Tickets Awaiting Review 42459 "Comments metabox doesn't load all the comments when clicking ""Show more comments"" link" Comments 4.8.3 normal normal Awaiting Review defect (bug) new 2017-11-07T18:04:17Z 2018-07-31T18:11:29Z "Recently, I found an issue related to the Comments meta-box on a post edit screen. To reproduce the bug, go to the article with a certain number of comments. Suppose there are 25 comments. Then go to the post edit screen, enable the comments and scroll down to view all the comments(you will see 10). Then click the link ""Show more comments"" at the bottom of the section. You will see the second part of the comments (10 again), and the link ""Show more comments"" will disappear. You may notice that you can't load the remaining comments(5). Why this happened? My short investigation below. I found that on my opinion there is a mismatch in amount of loaded comments between the ''commentBox'' object(`/wp-admin/js/post.js`) and comments meta-box init script(`/wp-admin/includes/meta-boxes.php`). First have a look at `/wp-admin/includes/meta-boxes.php:741` {{{#!php }}} As you can see there are 10 comments set to be loaded. Then go to `/wp-admin/js/post.js:42-45` {{{#!js if ( ! num ) num = 20; this.st += num; }}} As you can see there is default `num` value set to 20. Important: then commentBox.st was increased by a `num` value. But now have a look at ""Show more comments"" link onclick attribute. {{{#!php Show more comments }}} As you can see `commentsBox.load(26)` call will update `commentBox.st` but then `commentBox.get(26, 20)` will be called (because `num = 20`). But to fit the init script(`meta-boxes.php`) it should be `commentBox.get(26, 10)`. My solution here is to set default `num` value to 10. So I guess `/wp-admin/js/post.js:42` should looks like this: {{{#!js if ( ! num ) num = 10; }}} Let me know if I missed something and we can't accept new default `num` value. I have tested it on my local end. It works well after I changed `num` default value to 10." rku4er Tickets Awaiting Review 45106 Concerns related to moving mce_external_plugins filter to WP_Scripts::__construct Script Loader 5.0 normal normal Awaiting Review defect (bug) new 2018-10-17T13:19:26Z 2019-01-16T22:59:17Z "In r43723 the `mce_external_plugins` filter was moved to a function called via `wp_default_scripts` which, in turn, is called from `WP_Scripts::__construct` (via `WP_Scripts::init`). While the `wp_default_packages_inline_scripts` function calling the `apply_filters( 'mce_external_plugins'` is only triggered in case the `did_action( 'init' )` returns true, there might be cases when the `WP_Scripts` object is being reinitialised after the `init` and thus code hooked to `mce_external_plugins` trying to enqueue or register a script causes an infinite loop, since the constructor of the `WP_Scripts` class is calling the filter, which calls the constructor again. This does not feel like something what would matter in 99% of time, but, for instance, this breaks core unit tests which are reinitialising the WP_Scripts object, eg.: `Test_WP_Customize_Selective_Refresh::test_register_scripts`. in case such a piece of code is being used. An example of a code used in a mu-plugin and breaking the mentioned test: {{{#!php Please wait ... }}} you will receive an error in the web development console section: {{{ GET https://DOMAIN.COM/wp-includes/js/tinymce/plugins/code/plugin.min.js Status 404 Not Found }}} == Does problem occur when all plugins deactivated and use the default theme? N/A == what is the expected output or result? What did you see instead? The expected outcomes would be: 1) the direcotry and file '//DOMAIN.COM/wp-includes/js/tinymce/plugins/code/plugin.min.js'would be available 2) tinymce would show the code icon 3) no error displayed == additional information Not that this really matters for this, more related to wordpress version os: alma 8.8 php: 7.4.33 AND 8.1 browser: not applicable " jobst Tickets Awaiting Review 43505 Display of html encoded text in dashboard. Plugins normal normal Awaiting Review defect (bug) new 2018-03-08T21:59:56Z 2018-03-08T22:57:45Z "I have discussed the issue in this thread https://make.wordpress.org/polyglots/2018/02/26/hello-18/, I report here the issue of the display of the text in UI, not the editorial choice of the translation itself. In fr_FR and fr_CA, there where changes done (last year?) to accomodate french ponctuation typographic rules but also, I guess, make sure the text doesnt fall on two line inadvertantly (ex. ""text !"", so a non-breaking space is inserted instead of a space). This non-breaking space is inserted as html encoded entity and it looks like it is displayed as is, without decoding like it is visible in this exemple screenshot : https://imgur.com/a/iVy9h " anonym999999 Tickets Awaiting Review 50554 Do not use iframe for plugin information dialog Plugins normal normal Awaiting Review defect (bug) new 2020-07-03T22:38:07Z 2020-10-08T23:11:45Z When you click a plugin title in the Add Plugins page, the plugin information dialog displays inside an iframe. This causes a problem if your htaccess file has X-Frame-Options: DENY. A solution to this problem would be to not use an iframe for the dialog. techboyg5 Tickets Awaiting Review 49894 Drag & Drop image upload error on multisite install when no upload space available Editor normal normal Awaiting Review defect (bug) new 2020-04-13T13:19:19Z 2020-12-15T05:38:22Z "On a multisite installation, a maximum upload space can be limited. When using the classic editor and it's drag-and-drop upload feature while not having enough available space for a site, the image file ends up being loaded in the browser (at least in chrome) with following JS error in console: {{{ Uncaught TypeError: Cannot read property 'uploader' of undefined in wp-includes/js/media-views.js:5268 }}} See: https://core.trac.wordpress.org/browser/trunk/src/js/media/views/uploader/editor.js?rev=46800#L161 I would expect the classic editor to display an error similar to the one which is being displayed in media modal when attempting to upload a file while not having any available space: {{{ Upload Limit Exceeded Sorry, you have used your space allocation of 1 MB. Please delete some files to upload more files. }}} " david.binda Tickets Awaiting Review 46557 Dragging image to uploader directly from another website causes redirection Upload normal normal Awaiting Review defect (bug) new 2019-03-18T16:28:19Z 2019-03-18T16:28:19Z "1. Drag image from another website to editor 2. Image is handled correctly and embeded in content (by hotlink, but some may argue it's desired behavior) 1. Open Media Library modal (or Media admin page) 2. Drag and drop image from another website 3. Dropzone overlay is presented indicating ability to drop image to upload 4. Redirection to image URL is fired instead There is no issue when image is dragged to Desktop first and then from Desktop to Library." marsjaninzmarsa Tickets Awaiting Review 54706 EMBED AND IMAGE SLIDER DON'T WORK Post Formats normal major Awaiting Review defect (bug) new 2021-12-29T10:24:43Z 2021-12-29T10:24:43Z "The blocks ""**Embed**"" and ""**Image Slider**"" does not work. As I view my articles with incognito, these two blocks didn't show anything. Just a white blank. This article is an example: [https://nowmods.com/simple-realistic-3d-far-cry-6/] Some capture for more specific: [https://drive.google.com/drive/u/0/folders/1sl_xIjjaQwe3UVhz4ZnFCSNsQr1NuSDH] Really glad if there will be some fix on this! Thank you." anhdoan Tickets Awaiting Review 57142 Fix to the deprecated code inside wp-tinymce.js TinyMCE 6.1.1 normal normal Awaiting Review defect (bug) new 2022-11-18T04:15:45Z 2022-11-18T16:54:06Z In the current version `Event.path` is used in `wp-tinymce.js` which is deprecated and need to be replaced with `Event.composedPath()` isrgrajan Tickets Awaiting Review 56429 Gutenberg author box missing Editor 6.0.1 normal normal Awaiting Review defect (bug) new 2022-08-24T14:03:31Z 2022-11-05T22:30:57Z "There is a bug related to the author box missing when all of the following conditions are true: - When there are more than 70 users in a WP installation - When an Editor creates a post and saves it as a draft. This must be the only post of that user - If all the users are ordered alphabetically, that user must be above 60 in the order When this is true, if another Editor opens that draft, the author box won't be visible. There is an additional request that should fetch that user and it's returning error 403 If Administrator opens it, the author box is present The cause for the bug is the last condition that fails here - https://github.com/WordPress/WordPress/blob/master/wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php#L445 because the function checks for the author of the post" lgadzhev Tickets Awaiting Review 53863 Gutenberg fails with wp 5.8 Editor 5.8 normal critical Awaiting Review defect (bug) new 2021-08-03T01:40:57Z 2021-08-03T07:38:03Z "I had to rollback to fix this. The WP 5.8 Gutenberg crashed with this info: TypeError: Cannot read property '$el' of undefined at new m (https://bestredlighttherapy.com/wp-includes/js/dist/media-utils.min.js?ver=5e105975fcfe18922cd4f0163466f454:2:3795) at Yg (https://bestredlighttherapy.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:68:243) at rh (https://bestredlighttherapy.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:98:274) at zj (https://bestredlighttherapy.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:228:490) at Th (https://bestredlighttherapy.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:223) at tj (https://bestredlighttherapy.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:152) at Te (https://bestredlighttherapy.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:146:151) at https://bestredlighttherapy.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:61:68 at unstable_runWithPriority (https://bestredlighttherapy.com/wp-includes/js/dist/vendor/react.min.js?ver=16.13.1:25:260) at Da (https://bestredlighttherapy.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:60:280) I did turn off all plugins and switched to the default theme. Only rolling back the main version allowed me to get into Gutenberg." dogrescuer Tickets Awaiting Review 55368 Handle ajax failure when doing actions on themes/plugins Administration 5.9.2 normal normal Awaiting Review defect (bug) reopened 2022-03-11T05:36:32Z 2022-05-30T17:21:05Z "When maintenance mode is active or the server is unresponsive for any reason, there are some ui issues in ajax-related messages like: - When trying to delete a plugin: ""Deleting..."" forever. No error shown. - When trying to enable auto-updates on a plugin: ""Enabling..."" forever. ""The request could not be completed"" error is shown. Same for disabling. - When trying to delete a theme: ""Deletion failed: undefined"" error shown. - When trying to enable a theme: ""Enabling..."" forever. ""The request could not be completed."" error shown. Same for disabling. Check the screenshots attached below. I tried to stay short in title description but I'm not sure it's 100% clear." mirkolofio Tickets Awaiting Review 57284 IMG tag in Custom HTML widget and also in post made w/ Classic Editor causes 404 on save/update Widgets 6.1.1 normal major Awaiting Review defect (bug) new 2022-12-06T15:51:46Z 2022-12-06T16:41:39Z "I am running two blogs, both with the latest version of WordPress, 6.1.1. (I first noticed this on my previous version installed, 6.0.3 but have since updated, which did not solve the problem.) This issue exists on both WordPress installs I am running, to be clear. No need to walk through my discovery process here, but I noticed I could not save and edit I made to an existing Custom HTML widget - it would just sit w/ the save gif spinning. I noticed in the console it threw a ""Failed to load resource: the server responded with a status of 404 (Not Found)"". I then created a new test Custom HTML widget and it saved and was editable no problem. Much experimenting later, I found that the presence of a standard HTML ""img"" tag broke the save. I added full alt, title, src attribs to the tag - no change. I even used a blank ""img"" tag with no attribs at all -- the save still broke. 404. I had earlier run across an inability to edit and save old posts created with the Classic HTML plug-in, which was something I used to do all the time. I could create a new post and save it and edit it fine. Seemed odd. I just went back and added an ""img"" tag to the post and -- boom -- ""page not found."" Same issue, it seems. That's why I could not save my edit of the old posts -- all of them have an ""img"" tag or two in them. It seems that the presence of such a tag causes the AJAX submit to be corrupted somehow. The error, on Widget save, points to the file admin-ajax.php. I will attach a screenshot of the situation, for what it's worth. I can't say when this issue (which seems the same issue, to me as a web developer, between the two different examples here) began, but I've certainly edited content in the above fashion without incident in the past year. Right now I cannot edit or create Custom HTML widgets with images, and must -- for posts -- resort to using the block editor on the classic posts and dealing with the less-than-ideal HTML Source view it presents to make edits. Many thanks and I do hope this can soon be resolved. blakespot@gmail.com" blakespot Tickets Awaiting Review 58729 Incorrect Information Displayed in Media Library Window when Uploading Featured Image Media normal normal Awaiting Review defect (bug) new 2023-07-06T11:29:00Z 2023-10-20T01:34:47Z "I encountered an issue while attempting to upload a featured image for a post on WordPress. The problem arises when I access the Media Library window, as it displays incorrect information regarding the number of uploaded items. Steps to Reproduce: 1. Log in to the WordPress admin panel. 2. Navigate to the ""Posts"" section and select an existing post or create a new one. 3. Click on the ""Set featured image"" button within the post editor. 4. After uploading the first image its showing wrong information of number of media, Instead of **Showing 1 of 1 media items** its showing **Showing 1 of 2 media items** 5. It appears that the number of media items is inconsistent when I attempt to open the media library again by selecting the ""replace"" option. Video Link : https://www.loom.com/share/f87871494c5145c385f2343b454fe262 " adhun Tickets Awaiting Review 55899 Installer screen, button is NOT disabled when username is emtpy Upgrade/Install normal normal Awaiting Review defect (bug) new 2022-06-02T11:13:42Z 2022-10-12T18:15:16Z The install button is disabled upon entry. But it will ENABLE even when the username is still fully empty. ramon fincken Tickets Awaiting Review 58145 JS error: Uncaught ReferenceError: Element is not defined Editor 6.2 normal normal Awaiting Review defect (bug) new 2023-04-17T13:20:21Z 2023-11-22T12:35:42Z "I've got a console error on editor level uncaught ReferenceError: Element is not defined file: wp-polyfill-inert.js line:30 {{{ (function () { // Return early if we're not running inside of the browser. if (typeof window === 'undefined') { return; } // Convenience function for converting NodeLists. /** @type {typeof Array.prototype.slice} */ var slice = Array.prototype.slice; /** * IE has a non-standard name for ""matches"". * @type {typeof Element.prototype.matches} */ var matches = Element.prototype.matches || Element.prototype.msMatchesSelector; }}} suggestion {{{ (function () { // Return early if we're not running inside of the browser. if (typeof window === 'undefined' || window?.Element) { return; } // Convenience function for converting NodeLists. /** @type {typeof Array.prototype.slice} */ var slice = Array.prototype.slice; /** * IE has a non-standard name for ""matches"". * @type {typeof Element.prototype.matches} */ var matches = Element.prototype.matches || Element.prototype.msMatchesSelector; }}} " jankyz Tickets Awaiting Review 39894 JS heartbeat can run before ready causing exception General 3.6 normal normal Awaiting Review defect (bug) new 2017-02-16T19:29:05Z 2017-07-03T21:29:52Z Sometimes where my page is loading slowly I can get the error attached, where the element isn't yet available. programmin Tickets Awaiting Review 49431 Media uploader window leaves behind orphan button element in Block Editor Media 5.0 normal normal Awaiting Review defect (bug) new 2020-02-14T07:13:52Z 2022-05-06T02:59:54Z "This issue was originally reported in the Gutenberg Github repo - https://github.com/WordPress/gutenberg/issues/9184. Reporting this here as well—currently it looks like a fix might need to be applied in core, but also possibly in both Gutenberg and core. ---- **Describe the bug** Whenever you focus an Image Block or Gallery Block, a button element is created just before the closing body tag. Then, after blurring, the button is still there. This can be performed indefinitely times, leading to a massive amount of orphan button elements ---- **Steps to reproduce** 1. Open up the block editor 2. Open up dev tools and inspect the closing body tag 3. In the editor sidebar, switch between the document and the block tab and back again 4. Check the dev tools, observe that button(s) are appended to the dom every time the document tab is opened Expected: No buttons are appended " talldanwp Tickets Awaiting Review 51323 Multiple Reference Id backend issue in Inner block component Editor normal normal Awaiting Review defect (bug) new 2020-09-16T11:44:19Z 2020-09-18T14:45:52Z "We want to show multiple inner blocks on backend in same block. For example, If we have one widget and in to that, If we want to use two reusable blocks. We need to add two values. But, Currently, It shows just one value in backend. In frontend, It works fine because we have PHP based rendering. In backend, It show same reusable multiple times, even if we have selected different reusable blocks. You can check in screenshot about reference id. https://ibb.co/R0Pw6wK" posimyththemes Tickets Awaiting Review 59511 Navigation Block issue Editor 6.3.1 normal normal Awaiting Review defect (bug) new 2023-10-01T16:20:25Z 2023-10-28T05:02:20Z While trying to add and edit description or any metadata on nav items. As soon as I press any key, it gets refresh. amitpomu Tickets Awaiting Review 60072 No upper limit restriction for number of posts set via Site Editor and the value entered by the user chang Themes normal normal Awaiting Review defect (bug) new 2023-12-14T12:41:07Z 2024-02-15T16:24:55Z "=== Description No upper limit restriction for number of posts set via Site Editor and the value entered by the user changes === Environment - WordPress: 6.4.2 - PHP: 7.4.33 - Server: Apache/2.4.54 (Unix) OpenSSL/1.0.2u PHP/7.4.33 mod_wsgi/3.5 Python/2.7.18 mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_perl/2.0.11 Perl/v5.30.1 - Database: mysqli (Server: 5.7.39 / Client: mysqlnd 7.4.33) - Browser: Chrome 118.0.0.0 (macOS) - Theme: Twenty Twenty-Four 1.0 - MU-Plugins: None activated - Plugins: * WordPress Beta Tester 3.5.5 === Steps to Reproduce 1. Goto Site Editor 2. In the No. of posts per page option give a huge number and save the changes x. 🐞 Bug occurs. === Expected Results 1. ✅ It should show the maximum number of posts allowed per page exceeded validation message or the value added by the user === Actual Results 1. ❌ Goto Site Editor again and we can see the number changed to 9223372036854776000 2. There is no upper limit validation and the value entered by the user changed to some random values [[Image('https://ibb.co/gygWt9N')]] [[Image('https://ibb.co/RywQtrH')]] " jomonthomaslobo1 Tickets Awaiting Review 55390 Not able to choose Color picker in customizer when the blocks are added in widget Editor 5.9.2 normal major Awaiting Review defect (bug) new 2022-03-15T13:21:58Z 2022-03-16T09:17:28Z "Hi Team, I hope you are doing well and safe! I would like to highlight an issue with the color picker in the customizer when using the blocks in widgets. 1. For choosing the custom color, whenever you click on the color selection, it will trigger a click event where it will ask you to leave the site or not? Here is the screenshot: https://share.bsf.io/YEur81BW 2. The color selection palette is not properly displayed. Here is the screenshot: https://share.bsf.io/wbuzJ0zq Furthermore, I have gone ahead and found that this issue is coming from WordPress version 5.9.2 Also, I have demonstrated a video that would help you check it on your end too. This issue is occurring on default themes as well as other famous themes as well. Here is the screencast: https://share.bsf.io/yAuKoy2J I would suggest you please check this on priority and release a patch for this issue, as users are facing lots of issues due to this. Looking forward to your response." nileshc Tickets Awaiting Review 43295 One theme update notice is showing in another Theme Details popup Themes 4.9.4 normal normal Awaiting Review defect (bug) new 2018-02-12T12:23:43Z 2021-01-15T12:56:53Z "Steps to reproduce this bug: 1. Go to Appearance -> Themes 2. Click on the ""Update Now"" link showing on theme thumbnail. It will start updating the theme. 3. Now in the same time, click on the Theme Details by hovering over another theme. 4. It will display a popup of the theme details. Hold on few seconds while the theme gets updated. 5. You will see the green ""Updated"" notice in this popup of another theme. See the attached screenshots." ibachal Tickets Awaiting Review 49859 Post autosave called multiple times Autosave 5.4 normal major Awaiting Review defect (bug) new 2020-04-09T12:15:18Z 2020-04-09T12:15:18Z "Hi everyone. I found an issue, which is mostly not related to wordpress core but the fix should be handled in wp core itself. autosave.js works just great except one point. If there is move than one wysiwyg editor in admin post edit screen (no matter how it is added, in my case it is created ACF plugin, but it can be just a custom meta box field implemented as wysiwyg editor field ), and there is and autosave for current post, then 'tinymce-editor-init.autosave' jquery event triggered on jQuery(document) will call checkPost() js method wysiwyg editors count times. As a result ""The backup of this post in your browser is different from the version below"" notice is rendered the same count times. If there are 6 wysiwyg editors including wp native one (I have 5 custom ones), 'tinymce-editor-init.autosave' is called 6 times, and as a result ""The backup of this post in your browser is different from the version below"" notice is rendered 6 times. This is very easy to reproduce. Please review. Thanks in advance. Rafik I." Rufus87 Tickets Awaiting Review 57753 Quickedit characters on date fields Quick/Bulk Edit 6.1.1 normal trivial Awaiting Review defect (bug) new 2023-02-17T09:45:45Z 2023-02-22T20:51:17Z "I know this isn't a massive issue as content editors should use their common sense, but it seems like a user can enter random characters into the date/times via quick edits - Select a post - Press ‘Quick Edit’ - Try to insert letters, special characters in the ‘year’, ‘month’, ‘hour’, ‘minutes’ fields - Press ‘Enter’ " garbagedisco Tickets Awaiting Review 56250 ReferenceErrors encountered when running QUnit tests Build/Test Tools normal normal Awaiting Review defect (bug) new 2022-07-19T16:35:59Z 2023-08-07T17:44:51Z "When running QUnit tests, there are a handful of errors output: {{{ Error: ReferenceError: QUnit is not defined at :130:13 at HTMLDocument. (:132:2) }}} Even with these errors, no tests actually fail. The number of errors also differences between `grunt qunit` (3) and `grunt qunit:compiled` (6)." desrosj Tickets Awaiting Review 48784 Search box in Select / Upload image pop-up not working with cropped images Media 5.3 normal normal Awaiting Review defect (bug) reopened 2019-11-24T20:52:28Z 2020-03-28T20:10:45Z "Hi, it seems that the search field in the pop-up of selecting or uploading images can not find the images which have been cropped before. For example, if I go to Appearance / Customize and want to change the Logo image, and I am asked to cropped the image, that image won't show in the search field. It will show the non cropped image, but not the cropped one. Thank you! In the attached image you can see how the search field can do find the filename ""Foto-de-Javier-1.jpg"" using just the letters ""jav"". But there is another image in the Media which name is ""cropped-Foto-de-Javier-1.jpg"" and this one does not appear." javierr Tickets Awaiting Review 48361 Select Files on iOS doesn't trigger on modal if start on Upload Files tab and switch to Media Library tab adamsilverstein Media normal normal Awaiting Review defect (bug) assigned 2019-10-17T23:27:06Z 2019-11-03T19:46:59Z "Hello, I came across an odd issues on a client site recently using ACF and the Gallery field so I did a fresh install and found the issue resides in core as well. In short the 'Select Files' button doesn't trigger the uploader if you trigger the media modal starting on 'Upload Files' and then switching to 'Media Library' when there's no files present. To reproduce use an iOS device (iPad/iPhone); 1. Install a clean WordPress 2. Create a new post. 3. Add a Gallery block 4. Click the 'Media Library' button. 5. If your Media Modal opens with 'Media Library' tab selected then switch to 'Upload Files' and reload the screen. 6. Your Media Modal should open on 'Upload Files' now. 7. Switch to the Media Library tab now. 8. Click the 'Select Files' button that appears below the 'No items found' text. 9. Note the uploader isn't triggered. This seems to only occur when there's no items in your media library and you are using the Media Modal but your settings have it open on 'Upload Files' first and then you switch to 'Media Library'. I initially came across this with an ACF Gallery field, but in my clean install it was the Gallery block that I was able to reproduce the issue with. All the best, Cheers " garrett-eclipse Tickets Awaiting Review 25886 Sortable items gets stuck when dragging over TinyMCE Editor normal normal Awaiting Review defect (bug) new 2013-11-08T22:37:45Z 2020-11-24T06:09:01Z "When dragging a metabox over an active TinyMCE instance in a post/page edit screen, the metabox can get ""stuck"" (i.e., it stopping moving with the mouse). This only happens with TinyMCE and not the ""Text"" textarea. '''To reproduce:''' 1. Uninstall plugins 1. Install a default theme (I used Twenty Thirteen) 1. Go to ''Pages > Add New'' 1. If it is not activated already, click the ""Visual"" tab to activate the TinyMCE instance 1. Grab the featured image metabox to activate the sortable (i.e., drag and drop) functionality 1. Move the box over the TinyMCE area 1. Continual movement over the area will cause it to get stuck The following screen grab shows how the cursor separates from the metabox as it gets stuck: [[Image(http://f.cl.ly/items/0j2s0f2f2D3M2e393P3K/Screen%20Shot%202013-11-08%20at%202.33.36%20PM.png)]] It's kinda hard to understand it with that image, so here's a movie that shows the issue: http://f.cl.ly/items/1B151E3N0i3j092Z062m/broken-drag-and-drop.mov I have tested this in Safari, Firefox, and Chrome on OS X. All browsers produce the same issue. The issue persists with MP6 as well." tollmanz Tickets Awaiting Review 58733 The load more button appears even when there is only one image in the feature image selection window. joedolson* Media 6.3 normal normal Awaiting Review defect (bug) accepted 2023-07-06T13:22:35Z 2023-07-21T15:20:00Z "Load more button appears in the popup window for replacing the feature image, even when there is only one image available. Steps to reproduce the issue: 1. Go to the post editor in WordPress. 2. Locate the section where you can edit the feature image for the post. 3. Click on the ""Replace"" button to select a new image. 4. The popup window will open, showing the available images. Despite there being only one image in the selection, the ""Load More"" button is present in the popup window. Video Link: https://www.loom.com/share/c0e9faa4cc86455eb30bdaf2149b5a60 === Environment - WordPress: 6.3-beta3-56143 - PHP: 7.4.21 - Server: Apache/2.4.46 (Unix) OpenSSL/1.0.2u PHP/7.4.21 mod_wsgi/3.5 Python/2.7.13 mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_perl/2.0.11 Perl/v5.30.1 - Database: mysqli (Server: 5.7.34 / Client: mysqlnd 7.4.21) - Browser: Chrome 114.0.0.0 (macOS) - Theme: Twenty Twenty-Three 1.1 - MU-Plugins: None activated - Plugins: * WordPress Beta Tester 3.5.0" aparnajl Tickets Awaiting Review 27473 Thickbox width and height parameters are ignored when using TB_iframe Administration 3.8 normal normal Awaiting Review defect (bug) new 2014-03-21T18:18:19Z 2021-12-17T21:11:56Z "I tried to load a thickbox with custom width and height parameters, like the codex says: ?TB_iframe=true&width=450&height=120 anyway regardsless of what values I use, custom with and height values are ignored. I debugged /wp-includes/js/thickbox/thickbox.js and parameters are read in correctly, anyway it does not have any effect when setting them for iframe-tag on line 198: jQuery(""#TB_window"").append(""
""+caption+""
""); I tried to add the following code to check if resize is possible: jQuery(""#TB_window"").css(""width"",""450""); jQuery(""#TB_window"").css(""height"",""120""); this failed generally (although it worked when executing the command in the browser console) " harmr Tickets Awaiting Review 45852 Tick Box Open link in new tab... Editor 5.0.2 normal normal Awaiting Review defect (bug) new 2019-01-07T14:30:58Z 2020-01-22T06:26:44Z "I've found that when I insert a link into a new page and I edit the link, although I can tick in the edit box, open link in new tab, it does not work. The link opens in the same page and when I go back and tick the box again, it still does not work. The check-box isn't sending the command to open the link in a new tab. Many thanks. I can wait. " Motorised Tickets Awaiting Review 55012 TinyMCE editor not rendering correctly in visual mode using wp_editor function in a meta box on a page with the Block editor enabled in WP 5.9 TinyMCE 5.9 normal major Awaiting Review defect (bug) new 2022-01-31T17:51:40Z 2023-12-21T12:47:56Z "Using the wp_editor function on a meta box on WP 5.9 with the block editor enabled on a page results in the TinyMCE editor not rendering correctly in Visual mode. I note that there are several prior tickets about this same issue which unfortunately seem to have been unresolved due to being unable to be reproduced consistently: [https://core.trac.wordpress.org/ticket/52133 #52133], [https://core.trac.wordpress.org/ticket/52050 #52050], [https://core.trac.wordpress.org/ticket/53644 #53644]. Sadly I am also unable to reproduce this bug consistently either, I am experiencing it on both the development version and live versions of a particular site I'm working on at the moment, prior to the 5.9 update the wp_editor had been working correctly on both of these sites. As a test I made two clean installations on another server of both 5.8 and 5.9 with no additional plugins and a simple theme with metabox added to it and the wp_editor works correctly. So there is something specific about the particular combination of code in my site that is preventing the wp_editor from working in visual mode that didn't seem to be occurring before 5.9 for some reason, even though on these simple test installations they seem to be fine. I am able to workaround the issue by the following steps: switch to the Text view tab in the wp_editor, refresh the page and then switch back to the Visual view tab. These steps were indicated in one of the previous tickets linked above. The following is an example of the code I am using to add the metabox with wp_editor in it: {{{ function tools_next_steps_metabox() { global $post; $custom = get_post_custom( $post->ID ); $next_steps_links = isset( $custom[ 'next_steps_links' ][0] ) ? $custom[ 'next_steps_links' ][0] : ''; echo '
    '; echo '
  • This panel allows entering of text content for the “Next Steps” stage of the tool.
  • '; echo '
  • '; wp_editor( $next_steps_links, 'next_steps_links_id', array( 'wpautop' => true, 'tinymce' => array( 'toolbar1' => 'bold,italic,bullist,link,unlink', ), 'media_buttons' => false, 'quicktags' => array( 'buttons' => 'strong,em,underline,ul,li,link' ), 'textarea_name' => 'next_steps_links', 'textarea_rows' => get_option('default_post_edit_rows', 10), 'teeny' => true, ) ); wp_editor( $next_steps_links, 'next_steps_links_id' ); echo '
  • '; echo '
'; } add_action( 'add_meta_boxes', 'render_page_metaboxes' ); function render_page_metaboxes() { add_meta_box( 'a_tools_next_steps_metabox', 'Next Steps', 'tools_next_steps_metabox', 'page', 'normal', 'low' ); } }}} I appreciate this is perhaps not the most helpful ticket but given that issue has been reported in the past there is obviously some circumstance where using metaboxes and the wp_editor on pages using the block editor results in the editor not getting activated on load when the wp_editor is in visual mode. On the pages where I have the error occurring I have tried disabling the block editor on those pages and the wp_editor works correctly when the block editor is disabled. " rickcurran Tickets Awaiting Review 53976 Twenty Twenty-One: Anchor link on the same page causes the menu button icon to turn upside down Bundled Theme normal normal Awaiting Review defect (bug) new 2021-08-22T14:00:07Z 2021-08-22T16:55:40Z "As reported and requested in [https://wordpress.org/support/topic/menu-button-auto-scrolls-to-top-when-pressed-scroll-to-top-change-button-icon/]. If you have an anchor link on the same page, the icon turs upside down. Example. In website.com/one/ if you add a link to website.com/one/#anchor, this will cause the issue. An example will be a scroll to top button as in the report mentioned. Video showing (the bug report is for the second option. The first one was solved too in the report, but may not be the best solution, and, as the theme is not prepared to have a fixed header, and the problem is that when clicking the menu button, it automatically scrolls to the top, may not be relevant, but you can check on the report mentioned at first). In the video you can see in 0:09 when I click ""ARRIBA"", that is a scroll to top in casael.com using casael.com/#inicio [https://youtu.be/zW7R58KM_BA] Problem is in primary-navigation.js {{{ document.addEventListener( 'click', function( event ) { // If target onclick is with # within the href attribute if ( event.target.hash && event.target.hash.includes( '#' ) ) { wrapper.classList.remove( id + '-navigation-open', 'lock-scrolling' ); twentytwentyoneToggleAriaExpanded( mobileButton ); // Wait 550 and scroll to the anchor. setTimeout(function () { var anchor = document.getElementById(event.target.hash.slice(1)); anchor.scrollIntoView(); }, 550); } } }}} Possible Solution: Change {{{ document.addEventListener( 'click', function( event ) { }}} to {{{ document.querySelector('.primary-menu-container').addEventListener( 'click', function( event ) { }}} The function was being activated all the time, and that function should only work when the mobile menu is open. Now, you can use #anchors to move on the same page off the menu without “glitching” the menu icon. That change is tested and working without any problems." joelbermudez Tickets Awaiting Review 49025 Twenty Twenty: Modal menu link with hash should scroll to that section on the page. Bundled Theme 5.3.1 normal normal Awaiting Review defect (bug) new 2019-12-18T08:13:10Z 2021-06-12T09:39:29Z "Based on this support ticket: https://wordpress.org/support/topic/possible-bug-anchor-links-dont-work-in-js-flow-out-menu/ A possible fix would be to add this code in `index.js`, after [https://github.com/WordPress/WordPress/blob/c67763478840fabf689ecbd175dc682da1623069/wp-content/themes/twentytwenty/assets/js/index.js#L156 line 156]: {{{ goToAnchor: function() { document.addEventListener( 'click', function( event ) { var target = event.target; if ( target.closest( '.modal-menu' ) && 'a' === target.tagName.toLowerCase() ) { var url, targetHref; url = location.href.split( '#' )[ 0 ]; targetHref = target.href; this.untoggleModal( target.closest( '.cover-modal.active' ) ); if( '' !== target.hash && -1 !== targetHref.indexOf( url ) ) { setTimeout( function() { var fakeEl = document.createElement( 'a' ); fakeEl.href = targetHref; fakeEl.click(); }, 550 ); } } }.bind( this ) ); }, }}} And after [https://github.com/WordPress/WordPress/blob/c67763478840fabf689ecbd175dc682da1623069/wp-content/themes/twentytwenty/assets/js/index.js#L105 line 105], a call to the method: `this.goToAnchor();` " acosmin Tickets Awaiting Review 59355 TypeError: Cannot read properties of undefined (reading 'hasClass') in wp-auth-check.min.js Security 6.3.1 normal normal Awaiting Review defect (bug) new 2023-09-15T04:00:17Z 2023-09-15T04:03:37Z "Here is the trace: {{{ at HTMLDocument.(.../wp-includes/js/wp-auth-check.min.js:2:655) at HTMLDocument.dispatch(.../wp-admin/load-scripts.php:2:39997) at v.handle(.../wp-admin/load-scripts.php:2:37968) at Object.trigger(.../wp-admin/load-scripts.php:2:70063) at HTMLDocument.(.../wp-admin/load-scripts.php:2:70665) at Function.each(.../wp-admin/load-scripts.php:2:3129) at e..each(.../wp-admin/load-scripts.php:2:1594) at e..trigger(.../wp-admin/load-scripts.php:2:70640) at Object.(https://wednesdaynighthop.com/wp-includes/js/heartbeat.min.js:2:2186) at c(.../wp-admin/load-scripts.php:2:25266) }}} " chamois_blanc Tickets Awaiting Review 55139 TypeError: k is not iterable Editor 5.9 normal normal Awaiting Review defect (bug) new 2022-02-10T19:19:27Z 2022-02-10T19:19:27Z "When I am in the block editor and try typing something in the box search get the below error, see image 01 and 02. [[Image(https://inqmatic.com/wp-content/uploads/2022/02/image_01.png)]] [[Image(https://inqmatic.com/wp-content/uploads/2022/02/image_02.png)]] The error is: {{{ TypeError: k is not iterable at f (https://c0.wp.com/c/5.9/wp-includes/js/dist/block-editor.min.js:26:86949) at https://c0.wp.com/c/5.9/wp-includes/js/dist/block-editor.min.js:26:86506 at Array.map () at m (https://c0.wp.com/c/5.9/wp-includes/js/dist/block-editor.min.js:26:86496) at p (https://c0.wp.com/c/5.9/wp-includes/js/dist/block-editor.min.js:26:86043) at https://c0.wp.com/c/5.9/wp-includes/js/dist/block-editor.min.js:12:14633 at Object.useMemo (https://c0.wp.com/c/5.9/wp-includes/js/dist/vendor/react-dom.min.js:220:462) at c.useMemo (https://c0.wp.com/c/5.9/wp-includes/js/dist/vendor/react.min.js:30:236) at Wg7J.t.a (https://c0.wp.com/c/5.9/wp-includes/js/dist/block-editor.min.js:12:14608) at Le (https://c0.wp.com/c/5.9/wp-includes/js/dist/vendor/react-dom.min.js:100:3) }}} further, this error appear then update to wordpress 5.9. Thanks." zirtrex Tickets Awaiting Review 54046 Uncaught SyntaxError: Invalid regular expression Editor 5.8 normal normal Awaiting Review defect (bug) new 2021-08-31T22:34:14Z 2021-09-11T23:50:56Z "Hi I am trying to install a fresh version of WordPress on my server but the problem is, on the add new post page, I am getting this error: {{{ Uncaught SyntaxError: Invalid regular expression: /[!-/:-@[-`{-~б─-б©ц≈ц╥Б──-Б╞©Б╦─-Б╧©]/: Range out of order in character class at new RegExp () at Module.pC98 (wordcount.min.js?ver=61ab1af9326f4d5fda7ed01990e1be70:2) at t (wordcount.min.js?ver=61ab1af9326f4d5fda7ed01990e1be70:2) at wp.wordcount.YLtl (wordcount.min.js?ver=61ab1af9326f4d5fda7ed01990e1be70:2) at wordcount.min.js?ver=61ab1af9326f4d5fda7ed01990e1be70:2 }}} however everything is fine even with this error until I try to install SEO plugins, like Yoast SEO and Rank Math SEO, but the cause of the problem is WordPress I tried everything to see if this problem will gone away or not Tested with php 7.4 and 8.0 Tested with chrome, firefox and opera Tested with mysql and mariadb, also tested with different charset " mmakenzi Tickets Awaiting Review 50511 Update is not always shown live Upgrade/Install 5.4.2 normal normal Awaiting Review defect (bug) new 2020-06-29T16:18:59Z 2023-03-12T21:53:50Z "Hello, I have several WordPress websites running. It always strikes me when I import updates that the update process is not always displayed. The page just stays gray at that moment. At the end, when everything is ready, the actual content is shown, which is otherwise always displayed live. Why is that? It's not just one side, sometimes all, sometimes one, then sometimes another, I don't see any system behind it. The updates work wonderfully, but this process is not always 100% the same. Does someone know the behavior? I think it would be good if the page shows where WordPress is located step by step, because sometimes I think the system hangs, which is not the case. Here is an example from just now, the page was gray for almost 20 seconds (1st screenshot) and then everything came with one swing (2nd screenshot). Screenshot 1: https://ibb.co/2g8NThd Screenshot 2: https://ibb.co/GcCWB9B The browser doesn't seem to matter, I have already observed this with both the new Edge and Firefox. Maybe someone has an idea 🙂 Thank you! Translated from https://de.wordpress.org/support/topic/updatevorgang-wird-nicht-immer-angezeigt/" vincenz17 Tickets Awaiting Review 59307 Urgent, Uncaught TypeError: this.activateMode is not a function Media 6.3.1 normal critical Awaiting Review defect (bug) new 2023-09-07T08:06:16Z 2023-09-07T08:06:16Z "It's very urgent. There is no response when clicking the media button on the add/edit article page. Showing an error every click on the media button: Uncaught TypeError: this.activateMode is not a function at media-views.min.js?ver=6.3.1:2:59604 at It (provider.js:2:586804) at Function.ma (provider.js:2:621991) at n._createModes (media-views.min.js?ver=6.3.1:2:59564) at n.initialize (media-views.min.js?ver=6.3.1:2:58973) at n.initialize (media-views.min.js?ver=6.3.1:2:79857) at n.initialize (media-views.min.js?ver=6.3.1:2:73432) at n.initialize (media-views.min.js?ver=6.3.1:2:63143) at h.View (load-scripts.php?c=1&load%5Bchunk_0%5D=wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks,jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-mouse,jquer&load%5Bchunk_1%5D=y-ui-sortable,underscore,backbone,wp-util,wp-backbone,media-models,moxiejs,plupload&ver=6.3.1:151:14648) at n.constructor (load-scripts.php?c=1&load%5Bchunk_0%5D=wp-polyfill-inert,regenerator-runtime,wp-polyfill,wp-hooks,jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-mouse,jquer&load%5Bchunk_1%5D=y-ui-sortable,underscore,backbone,wp-util,wp-backbone,media-models,moxiejs,plupload&ver=6.3.1:155:2602)" jjproitech Tickets Awaiting Review 42288 Validation of custom menu link Menus 4.8.2 normal normal Awaiting Review defect (bug) new 2017-10-20T05:38:04Z 2018-06-14T13:40:20Z "1. go to menus page 2. try to add custom menu link with label only. without a URL. expected and actual result: validation failed and link cannot be added. 1. go to menus page 2. add custom menu link with label and URL: '#' 3. save menu 4. edit the custom link from the menu and remove the URL. 5. click save expected result: validation failed and menu won't be saved. actual result: menu saved. no validation." dvirhazout Tickets Awaiting Review 42484 WP ajax call fail when executing long time 'ERR_SPDY_PROTOCOL_ERROR'. Media 4.8.3 normal normal Awaiting Review defect (bug) new 2017-11-09T12:18:18Z 2017-11-09T12:38:47Z "Hello, I have one ajax script that is uploading 25MB video on server and convert on server. This core process doing by only WordPress ajax file. This process is run successfully but after uploading and conversion ajax automatically fail and give me this error ""ERR_SPDY_PROTOCOL_ERROR"". This error i am facing from last update(4.8.3). so i think there is issue regarding ajax call in WordPress 4.8.3 version. I am WordPress Developer with 6+ years of experience and i have found this bug. Please review this bug. There is attach one image related to error. [[Image(http://webidroid.com/WP_ajax_err.png)]] " gaurangsondagar Tickets Awaiting Review 43149 WP-API JS Client not triggering change event when using setMeta/setMetas helpers REST API 4.9 normal normal Awaiting Review defect (bug) new 2018-01-23T16:49:55Z 2020-10-25T04:19:42Z "As briefly [https://wordpress.slack.com/archives/C5UNMSU4R/p1516717879000467 mentioned] on Slack earlier today the `model.setMeta()` helper method introduce in #41055 has a couple of weaknesses. 1/ The `meta` attribute is undefined when creating a new model, which makes sense, but causes `setMetas()` to silently fail at set new meta values; using `setMeta()` causes an error. {{{#!javascript var post = new wp.api.models.Post( { id : 1234 } ); post.setMetas( { foo : 'bar' } ); // post.attributes.meta remains undefined post.setMeta( 'foo', 'bar' ); // TypeError: metas is undefined }}} 2/ When the `meta` attribute is properly defined, some changes in meta values fail to trigger a change event. Provided that the above issue does not show: {{{#!javascript var post = new wp.api.models.Post( { id : 1234 } ); post.on( 'change:meta', console.log ); post.set( 'meta', { foo : 'bar' } ); // trigger change event post.setMetas( { foo : 'BAR' } ); // Does not trigger change event post.setMeta( 'foo', 'BAR' ); // Does not trigger change event }}} Values are correctly updated; the `change` event is just not triggered as it should. The only way I found to make this work is to clone the `meta` attribute in `setMeta()`/`setMetas()`. As of now these methods simply retrieve the `meta` attribute using `get()` and then `_.extend()` to add/update properties, which doesn't seem enough to make Backbone consider it a change." caercam Tickets Awaiting Review 50132 Word Counter on Classic Editor is bugged Editor 5.4.1 normal normal Awaiting Review defect (bug) new 2020-05-08T19:28:22Z 2020-11-24T16:14:30Z "On the Classic Editor, sometimes words after a new line or new paragraph are not counted properly. If you create 10 lines, each consisting of 10 words each, only 91 words will be accounted for. This seems to be mostly a JavaScript bug, but can potentially affect any other word-counting function on WP too, if their implementation is similar." matpratta Tickets Awaiting Review 48768 WordPress 5.3 ajax bug with Elementor 2.7.5 Query 5.3 normal critical Awaiting Review defect (bug) new 2019-11-22T15:17:38Z 2019-11-22T15:17:38Z "To whom it may concern, I was working on my WordPress site and updated it to the latest version available (5.3), before had the 5.2.4 version, i also updated the plugin Elementors to the latest version 2.7.5 . I noticed that when i was trying to access their build in option, build query, for the elements, it would give and ajax error of type : **core-query uncaught TypeError: Cannot read property 'ajax' of undefined** . I tried to downgrade the Elementor to a previous version but it didn't work, than i downgraded the WordPress one version older and it worked normally. " argentum95 Tickets Awaiting Review 52305 WordPress Classic & Gutenberg Editor - ENTER key casing Textarea View Position To Jump Editor normal normal Awaiting Review defect (bug) new 2021-01-15T11:10:01Z 2021-02-09T20:12:24Z "Steps to reproduce: (on Windows 10 x64, Chrome latest browser version) 1) Install latest and greatest WordPress* - with ""2021"" theme as active (theme is irrelevant, actually) - absolutely no plugins should be active EXCEPT WordPress Classic Editor: **wordpress.org/plugins/classic-editor/** * NOTE: exact/latest WP version is not actually relevant, either, because this bug is an ongoing issue for at least a 6-12 months now - can't say for sure - it's just that I finally found the time to investigate it on a clean fresh system. - Activate plugin, switch to **Classic Editor** mode for new posts, and switch from **Visual** to **Text** input mode (this is very important!). 2) Create new post in Text mode - Simply copy-paste provided demo html text (demo lorem ipsum text with sufficient length should be used, to provide enough ""page scroll"" or reduce browser's window width to approx 1200 pixels to emulate older laptop computer) + add some h3 tags (for easier orientation, as long as you do not scroll all the way down to the end of the text, but position mouse cursor to the end of a paragraph somewhere in the middle you should be able to reproduce this bug. - save the post - now edit the post (it is best to activate DevTools and disable browser caching just to be sure everything is freshly loaded every time) - when you **position mouse cursor somewhere in the middle** of the article **at the end of a paragraph or html element** and hit **ENTER** key on the keyboard (to create new paragraph line), Editor will jump its position and text will completely shift outside visible area to the top! This is a bug that exists for about a year or so and it is very annoying (to say at least), particularly to us who are used to work directly with html tags in Text mode. Bug seems to originate in TinyMCE editor's scroll function that is triggered when we hit Enter key (according to debugger). It uses math function to calculate position of the top toolbar with commands. (?) See provided video recording to visualize the bug itself. Sometimes it may not occur, but try to repeat it again, and it should reproduce. I would likely to know if there's an easy fix for this. Thanks!" Darko A7 Tickets Awaiting Review 52308 "WordPress Editor does not preserve ""blank"" (empty) lines in Code/Text mode" Editor normal normal Awaiting Review defect (bug) new 2021-01-15T13:51:13Z 2021-01-15T13:51:13Z "This issue exists in WordPress Classic (TinyMCE) Editor for ages, and similar issue exists in new Block editor, when used in Code mode. I will try to explain it as briefly as possible, but there's a video attached for a quick demonstration, as well. **1) WordPress Block Editor** - Switch to Code mode - Type a lot of html text with some tags (e.g. h3, h4, h5 sections and paragraphs) - Whenever you insert an empty line between title tags (h1-h6), on scroll action Editor will remove them! This condenses all the text and makes our brains short circuiting e.g. we can no longer easily visualize different paragraphs and sections when working with huge amount of text / lengthy articles! This behavior should be fixed / js code that is doing this must be optional and left disabled, if we desire so. Or removed completely, as it is counter-intuitive and counter-productive. **2) WordPress Classic Editor** - Situation with Classic editor is little better. As long as we stay in Text mode, editor will keep our line spacings between header titles/tags and other tags and paragraphs. - However, as soon as we switch to Visual Editing mode, and update the article, all the line spaces / ""custom formatting"" will be lost! Now, I need to switch on occasion to Visual, but I like to mostly work in Text mode, because of full control and freedom. The HTML output produced in Code/Text modes does not actually change, so this annoying thing is not even justified by WYSIWYG standard e.g. it does not affect the end result. But it makes our lives miserable with the editor's mind of its own. To be honest, I'd like to have a simple editor, much like this one we have here on Track during posting issues. It presents us with a plain textarea input and commands on top, and that's it! It works. Please see attached video for illustration. Thanks!" Darko A7 Tickets Awaiting Review 55484 class-wp-editor.php line 1697 Editor 5.9.2 normal normal Awaiting Review defect (bug) new 2022-03-30T00:46:36Z 2022-03-31T19:32:19Z "Line 1697 of class-wp-editor.php should end with a semicolon. Otherwise, if the page is compressed errors are in the console and the editor isn't functioning correctly." karin2 Tickets Awaiting Review 58644 embed height fix Embeds 4.4 normal normal Awaiting Review defect (bug) new 2023-06-27T15:59:11Z 2023-06-27T16:48:10Z "It seems that this fixes the issue of embeds cutting off at the bottom. It would be great if it could be implemented into the core. I have tested it and it works and fixes the issue: [https://medium.com/@wlarch/overwrite-and-bypass-wordpress-iframe-height-dimension-limit-using-javascript-9d5035c89e37 Overwrite and bypass WordPress iframe height dimension limit using JavaScript]" iamhugo76 Tickets Awaiting Review 60378 gdlr-edit-box.js Uncaught TypeError: temp_settings is undefined Editor 6.4.2 normal critical Awaiting Review defect (bug) new 2024-01-30T11:56:51Z 2024-01-30T11:56:51Z "Uncaught TypeError: temp_settings is undefined code: var temp_settings = tinyMCEPreInit.mceInit.content;" changhsinjung Tickets Awaiting Review 54205 jqxhr is undefined inside of deferred.done() when using wp.media to add a custom image upload Media 5.8.1 normal major Awaiting Review defect (bug) new 2021-09-30T20:55:42Z 2022-05-31T14:33:33Z "I have done all the usual trouble shooting and found this is being cause by a new block of code added to wp-util.js in 5.8.1. Specifically lines 121-134. The jqXHR property does not exist inside of the done() object and therefor always errors out. This is removing a key functionality of a clients admin that makes it where no new products can be added without a horrible workaround." metawebdevelopment Tickets Awaiting Review 53677 load_script_textdomain() doesn't work for subdirectory themes, or those in alternate theme roots I18N normal normal Awaiting Review defect (bug) new 2021-07-16T07:08:25Z 2021-07-16T07:12:08Z "load_script_textdomain() attempts to load script translations for themes, but fails to generate the correct relative filename when the theme is within a sub-directory or alternate theme root. WordPress supports three main formats for theme directories (See [https://core.trac.wordpress.org/browser/trunk/src/wp-includes/theme.php#L427 search_theme_directories()]) 1. wp-content/themes/$theme 2. wp-content/custom-theme-root/$theme 3. wp-content/themes/a-directory-of-themes/$theme (and likewise for the custom $theme_root) The first case is covered, but when using the other two, the generated relative path and subsequent path md5 is incorrect. For example, given the file `.../themes/a-directory-of-themes/$theme/build/index.min.js` instead of generating the md5 of `build/index.js` it generates it of `$theme/build/index.js`. I'm unsure what it would do with the custom theme roots, all that I can tell is that the use-case doesn't appear to be covered in the function." dd32 Tickets Awaiting Review 52926 mobile compatibility library sortable list input field ignores touch event External Libraries 5.7 normal normal Awaiting Review defect (bug) new 2021-03-27T03:54:44Z 2021-05-26T02:22:35Z "The ability to edit a WP backend menu item custom url input field has not worked on my iPad iOS 14.4.1 using Safari and Chrome. Any text input field simply doesn't respond. Select choice list controls recognize touch. I am using Admin Menu Editor Version 1.9.9 plugin. On Mar 26, 2021, at 08:56, Janis Elsts wrote: Unfortunately, it looks like it's currently not feasible to fix this issue. It appears that problem is in one of the JS libraries that is part of WordPress itself. It's a mobile compatibility library that's supposed to translate touch events into simulated mouse events. It doesn't seem to work correctly when you tap an input field that's inside a sortable list, like the menu item list in Admin Menu Editor. I don't have enough mobile development experience to replace the existing JS library with something better, so this bug may remain unfixed until/unless WordPress core developers fix the underlying issue." edtorrey Tickets Awaiting Review 49627 oEmbedding - Privacy by design - Inconsistencies & Legal concerns Embeds normal normal Awaiting Review defect (bug) new 2020-03-12T11:41:19Z 2020-03-23T01:14:09Z "oEmbedding is now driven by two files : * {{{wp-includes/class-wp-oembed.php}}} and its list of ""popular"" oEmbed providers : array ( pattern => array( oembed_url, regex [boolean] ) ) This list is loaded in {{{wp-settings.php}}} with this instruction : {{{$GLOBALS['wp_embed'] = new WP_Embed();}}} This list of providers is filterable with hook {{{'oembed_providers'}}}, but the hook appears to be fired before {{{'plugins_loaded'}}} and {{{'init'}}} hooks. The modus operandi to alter the ""popular"" providers list is described here : [https://wordpress.org/support/article/embeds/] . * {{{wp-includes/js/dist/block-library.js}}} The data structure is here different due to some visual aspects (Gutenberg) Several variables with name like {{{'embedXxxxxIcon'}}} are objects containing svg icons and another list of oEmbed providers with a specific variable called 'common' which is a set of -- name => settings ( title, name svg icon, keywords, description ) => patterns 1) the lists of oEmbed providers are not identical in php and javascript. 2) in each list, the patterns for each oEmbed provider can be different. 3) the once driven oEmbedding process by the php array that could be filtered or altered (""popular"" oEmbed providers) is not possible anymore. If you are using the Classic editor or Gutenberg, the process to retrieve the data and the structure of the data are different as shown in screenshot1 (Classic trunk) and screenshot2 (Gutenberg 5.3). 'Classic editor' is using {{{admin-ajax.php}}} and retrieves a specific json format. 'Gutenberg' is using the rest-api and calls a url such as {{{'index.php?rest_route=/oembed/1.0/proxy&url....&_locale=user'}}} and retrieves the full oembed json from the provider. In the class-wp-oembed-controller, the code executed seems similar to Classic editor (data2html) but the result is obviously different. Both are caching the html code in post_meta table, 'Gutenberg' is caching the json result of oembed in options table. This means that the filter 'oembed_result' is by-passed when oembed content is displayed in 'Gutenberg'. 4) if a site decides to remove one or all references to ""popular"" or ""trusted"" (vocabulary differs in code comments) oEmbed providers or add its own, this is not possible anymore when using Gutenberg, because the javascript providers list is hard-coded and cannot be altered. For obvious local regulations, it is important to be consistent and coherent in the oembedding policy choices of each site for each site. This is a regression and an infringement to the ""Privacy by design"" policy adopted by wordpress open source project. 5) i am not going to discuss how the ""popular"" providers got elected by a ""popular"" vote or an electoral college and if they had a superpac to get elected (or more accurately ""be referenced""). On some websites, these arbitrary choices that cannot be altered may contervene to website policy e.g. educational blogs for kids, or local laws. In some countries, this can be considered as political [ethymology definition : ""life in the city""] choice and can put at risk wordpress users : loading in their browsers references to forbidden sites. Surveillance is everywhere and not all countries are democracies. 6) it is important, that in WordPress, all ""popular"" oEmbed providers removed or added by filter, be removed or added in any form of code (Gutenbeg specific blocks included) (privacy by design). This implies a unique reference list of providers (filterable/alterable in php) with some extra information for visual aspects under Gutenberg. The javascript variables must be generated (or not if providers is an empty array) from the php list (with some default values if extra information is not provided). To simply and easily : a) add a new provider on both sides and specific svg icons. b) remove a ""popular"" provider with an easy {{{wp_oembed_remove_provider( 'tactic' ); }}} rather than {{{wp_oembed_remove_provider( '#https?://(www\.)?tactic\.com/.*/video/.*#i' );}}} c) {{{wp_oembed_remove_all_providers()}}} is also welcome. 7) it could be interesting to offer optional and intermediate solutions to oEmbedding as it is processed today (privacy by design) : a) insert specific html ( usually iframe : fully intrusive) b) insert link to url with thumbnail when available {{{}}} (less intrusive) c) insert link as text {{{(some title or text if available or url)}}} (no oEmbedding : not intrusive) Requires to cache the complete json answer indifferently ('Classic' or 'Gutenberg'). 8) it could be interesting to encapsulate the oembedding result in a custom html5 element (privacy by design) such as {{{ ... }}} to allow theme developpers to add specific js on embedded content. 9) The oEmbed providers listed in wordpress are referenced by wordpress. Definitely change the vocabulary used in the code comments. Do not use ""popular"" or ""trusted"" providers but 'referenced providers', because this is the most accurate definition. Regards related #43713, related https://wordpress.org/support/article/embeds/ ps : as a remainder, GDPR chapter IV title is Controller and Processor." arena Tickets Awaiting Review 55332 problem with quick comment discarded changes Posts, Post Types 5.9.1 normal minor Awaiting Review defect (bug) new 2022-03-07T22:56:11Z 2023-08-09T15:08:12Z "The function discardCommentChanges in js/edit-comments.js does not seem to be working as intended. When using the quick comment editor, the function is called when an edit is started, and it does nothing at that point as expected. But if you click away from the form, nothing stops you and you lose your comment changes. On the other hand, if a plugin enqueues edit-comment.js, buddyboss-platform does (I don't know how/why), and you are editing a post (my attached example is an event venue), the function is triggered on update. With no comments involved, the original content is an empty string and the editied comment is undefined and that triggers the popup warning that changes might be lost." LinuxArchitect Tickets Awaiting Review 41229 the tag read more is not working Editor 4.8 normal normal Awaiting Review defect (bug) new 2017-07-03T12:17:48Z 2017-07-03T22:11:01Z "Hello, I have wordpress on a Hebrew language and when I try to add read more tag on post it's not show up in the frontend" yohanankap Tickets Awaiting Review 51721 wp-admin/js/post.(min.)js does not successfully validate post dates within years 0000—0100 Editor 2.9 normal normal Awaiting Review defect (bug) new 2020-11-06T15:29:43Z 2020-11-10T17:42:02Z "When adding or editing a post, `wp-admin/js/post.(min.)js` does not correctly set the year on a JavaScript `Date` object when validating the post date. == To reproduce: 1. Add or edit a post 2. In the ''Publish'' meta box, click ''Edit'' next to the publish date. 3. Enter a validate date, with the year in the range 0—100. 4. See that the date input is highlighted red and marked invalid. == In depth This happens because in JavaScript, when passing a two-digit year to the `Date` constructor, it thinks that it is for the 1900 century. Even passing a string such as `0050` seems to be type-casted to a number. [http://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date#Two_digit_years_map_to_1900_%E2%80%93_1999 See more on MDN]." wongjn Tickets Awaiting Review 43535 wp-mediaelement.min.js?ver=4.9.4:1 crashes, making the Widgets in customize.php unusable General 4.9.4 normal normal Awaiting Review defect (bug) new 2018-03-13T09:57:51Z 2018-03-13T10:29:44Z "When accessing **wp-admin/customize.php** with a live preview, I am unable to add menu items or to switch between ""Text/Visual"" for the text widgets. At the first sight, it seems to be a problem with Javascript. The console looks like having an error with the media gallery - `Uncaught TypeError: Cannot read property 'indexOf' of null` (see screenshot for details). [[Image(https://cloudup.com/cLbAt2w2Kas)]] There is also a second error in the console - which does not seem related - but it may prove helpful: `Error parsing header X-XSS-Protection: 1; mode=block; report=https://www.google.com/appserve/security-bugs/log/youtube: insecure reporting URL for secure page at character position 22. The default protections will be applied.` I have also disabled live preview with a `die()`, the situation is the same - which makes me think the error is more related to the way media gallery interprets some part of the content while rendering customize.php. Everything works smoothly for **wp-admin/widgets.php** (no Javascript errors). There may be other sections that are affected, but I can confirm these two: * Widgets > Footer X > Any text widgets: cannot switch between Visual and Text (stays blocked on Visual) * Menu > Main Menu > Add items: items are not clickable (and the first one is not folded). Browser: Chrome 64.0" radual Tickets Awaiting Review 55030 wp_enqueue_script( 'jquery-ui-autocomplete' ) - is enqueueing a bunch of extra scripts I don't need Script Loader normal normal Awaiting Review defect (bug) new 2022-02-01T16:56:14Z 2022-02-18T11:57:05Z "When I enqueue default scripts located in WP, specifically {{{#!php tag included in JSON General normal normal Awaiting Review defect (bug) new 2022-01-24T16:01:50Z 2022-01-25T08:08:48Z "**NOTE** > This ticket is **already posted at May 22nd 2020 to hackerone.com** `#880749` and reviewed by the security team. > I've created this ticket for public hardening under their instruction. == Description: `wp_set_script_translations` is a function that provides translation strings for [@wordpress/i18n](https://developer.wordpress.org/block-editor/packages/packages-i18n/) library. The JSON will be output just before the targeted script without checking the string `""], } } } }}} == Recommendations Escape JSON string `` == Impact * Attackers can inject any JavaScript code they like. * Translation files can be provided from 3rd party(e.g. voluntary contributors), but hard to detect it's correct or not because they are written in foreign languages for the original authors." Takahashi_Fumiki Tickets Awaiting Review 49381 Add Javascript Documentation to privacy-tools.js Privacy normal normal Awaiting Review enhancement new 2020-02-07T06:26:43Z 2020-02-07T06:26:43Z "Stemming from a [https://core.trac.wordpress.org/ticket/44264#comment:18 comment] on #44264 the privacy-tools.js functions should be properly documented; Javascript Documentation guidelines - https://make.wordpress.org/core/handbook/best-practices/inline-documentation-standards/javascript/#functions" garrett-eclipse Tickets Awaiting Review 48977 Add a new test case for E2E test Build/Test Tools normal normal Awaiting Review enhancement new 2019-12-15T05:30:44Z 2021-03-08T05:56:53Z "Now the E2E test has only one case to test WordPress. So we can add a new test case ** Test case WordPress has two default content. - Post ""Hello world"", post_id=1 - Page: ""Sample Page"", post_id=2 So we can test to these page are these page exists. ** Expect - localhost?p=1 -> should return HTTP200 - localhost?p=2 -> should return HTTP200 - localhost?p=404 -> should return HTTP404" hideokamoto Tickets Awaiting Review 47518 Add an explanatory message to the Revisions screen for locked posts adamsilverstein Revisions normal normal Awaiting Review enhancement assigned 2019-06-10T15:30:43Z 2021-04-30T17:44:27Z "It's possible for a user to navigate to the revisions screen for a post that's locked due to another user editing it, and not be able to restore any revisions due to the fact that the post is locked. In this situation no message is shown on the Revisions screen that explains why the `Restore This Revision` button is disabled. Under normal operating procedure it's not easy to get to the Revisions screen for a locked post, but it is possible. A workflow related plugin, audit trail, or revisions list can make it possible to navigate directly to a revision without going via the otherwise locked editing screen. 1. User A navigates to the revisions screen for a non-locked post. 2. User B visits the editing screen for the post. 3. User A clicks `Return to editor` on the revisions screen. 4. User A chooses not to take over, and clicks `Go back`. User A is now shown the revisions screen for a locked post and the `Restore This Revision` button is disabled for all revisions but with no explanatory information." johnbillion Tickets Awaiting Review 60345 Add duplicate checking for uploaded attachments Media normal normal Awaiting Review enhancement new 2024-01-25T16:39:34Z 2024-01-25T16:39:34Z "It can be very difficult to tell whether you've already added a given document or image to your media library if it's no longer in recent items. The lack of sorting or filtering makes specific difficult to locate. Based on a [https://wordpress.slack.com/archives/C02SX62S6/p1706115251959409 conversation on duplicate detection in #core-media], we think that a starting point for this is to hash the meta data for an attachment at the time of upload and store that as attachment meta. We could then check for that hash value before uploading a new document, and prompt the user to use the old attachment if it already exists. The specific meta data would probably need to vary depending on the type of attachment." joedolson Tickets Awaiting Review 49378 Add warning banner about no-js in wp-admin Administration normal normal Awaiting Review enhancement new 2020-02-06T17:44:40Z 2020-02-07T01:59:52Z "WordPress is becoming more and more depending on Javascript. Javascript may be unavailable for various reasons: - JS blocked in browser, either in general or for the current domain - If the site is accessed over https while site URL is set to http, then JS objects may be blocked due to mix content rules. If/when JS is unavailable, weird errors may occur in the admin panel, and the error texts may not immediately hint about the real reason. See #43900 for instance. Obviously, the block editor is totally depending on JS, and it's already got a warning banner on it own ( #45453 ). But I think it by now would be good to add a similar warning banner at the top of the wp-admin page: Please note that Javascript seems to be unavailable. You may have it blocked or you may be mixing access via https and http. This may lead to unexpected errors. So I suggest that we " tobifjellner Tickets Awaiting Review 54778 Adding Filters in UI (Plugins) Plugins 5.8.3 normal normal Awaiting Review enhancement new 2022-01-10T10:50:03Z 2023-05-20T06:47:16Z "**Problem:** Searching for any particular plugins shows the related plugins based on the keywords, out of which some old and unmaintained plugins also appear in the results which might be a vulnerability issue for their users. **Possible Solution:** Adding Filters to categorize the results for searchers query: 1. Latest to Oldest 2. Oldest to Latest 3. Most Downloads 4. Least Downloads 5. Highest Rated 6. Lowest Rated **Exception:** Adding the filters, rather than completely changing the way the results appear (such as: showing the most updated results first, etc) would be more useful, and it would be more fair for all publishers/plugin-maintainers. **Possible Improvements:** Reducing the risk of downloading incompatible old, untrusted, unmaintained plugins leading to vulnerability or other risks in website (business :D)." ritvikux Tickets Awaiting Review 50441 Allow CORS for RSS feed Feeds normal normal Awaiting Review enhancement new 2020-06-20T18:22:19Z 2021-10-08T06:59:23Z "I'm developing an in-browser RSS reader and want to get an RSS feed from my blog on WP.com but browser (both Chrome and FF) shows me the error: {{{ Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wordpress.com/blog/feed/. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). }}} Here is a small example to reproduce: {{{ }}} This is quite popular thing that a lot of peoples tries to do: https://www.google.com/search?q=wordpress+feed+cors That's one of the main reasons why most browser JS RSS readers requires to use a dedicated proxy server that will make a server to sever call to retrieve the RSS: * https://github.com/sdepold/jquery-rss proxies RSS fetch via Feedr. * https://github.com/enginkizil/FeedEk proxies RSS fetch via Feed API * https://github.com/rbren/rss-parser uses https://cors-anywhere.herokuapp.com The fix is easy: {{{ add_action( 'pre_get_posts', 'add_header_origin' ); function add_header_origin() { if (is_feed()){ header( 'Access-Control-Allow-Origin: *' ); } } }}} But I wan't the fix to be added into WP trunk because my reader will mostly consume RSS from wordpress.com or many other WP blogs. It should be fine to allow CORS requests to feed. The only one problem is a security concern. Hacker can make a DDoS by pasting on some popular site an tag with src to WP feed and this will produce a big load to WP instance. But here we can add a simple check: when browser requests an image it sends the header `Accept: image/webp,image/apng,image/*,*/*;q=0.8` while JS RSS headers can set the `Accept` header manually to `application/rss+xml`. Actually the rss-parser already sends the `Accept: application/rss+xml`. So on the server side we can just check that client requested exactly the feed and only then try to generate it. As far I see this is something really important (because already used workarounds) and it should be easy to implement and safe to enable by default. So I'll set Major severity. " stokito Tickets Awaiting Review 47447 Allow client-side storing of comment meta Comments normal normal Awaiting Review enhancement new 2019-05-31T15:46:52Z 2019-05-31T15:46:52Z "As a modern counterpart to #12431, I think it'd be nice if plugins could add comment meta from the client side as well. An example use case would be [https://github.com/iandunn/compassionate-comments a plugin that identifies toxic comments, and then encourages the author to rephrase it to be more kind before it gets submitted]. It's currently possible by adding a `preprocess_comment` callback that examines `$_POST`, verifies and sanitizes the data, and then adds it to `$commentdata` before that gets passed to `wp_insert_comment()`. It could be much easier and standardized, though. Ideally, I think a client-side script should be able to just append a hidden input field named `comment_meta[]` to the `.form-submit` element, and have it be automatically added via `wp_insert_comment()`, rather than being ignored by `wp_handle_comment_submission()`. Since it's coming from the client side, the data can't be trusted. We need to verify that it was added by the enqueued script, and then sanitize it. Maybe there could be something similar to `register_post_meta()` with a `allow_in_form` boolean param, and a `sanitize_callback` param." iandunn Tickets Awaiting Review 49352 Allow get_proxy_item to be filtered/altered before a response is sent to the editor. Embeds normal normal Awaiting Review enhancement new 2020-02-03T16:13:40Z 2020-02-03T16:13:40Z "**tl;dr:** Add a filter in {{{\WP_oEmbed_Controller::get_proxy_item}}} so certain non-oembed sites can still be embeded using a custom handler from a plugin. **Scenario:** I would like to create a generic oEmbed provider on my own site similar to iframely.com. So when a user posts a link in the editor that isn't a oembed provider, I would like to be able to filter the response from {{{\WP_oEmbed_Controller::get_proxy_item}}} and not having it reply with {{{return new WP_Error( 'oembed_invalid_url', get_status_header_desc( 404 ), array( 'status' => 404 ) );}}}. In my ideal case I could catch this and pipe the URL in question through my own proxy endpoint and create a custom oEmbed result from meta and open graph tags generated from the original HTML of the link to be embeded. Currently it seems, that I can only replace the all embeds through a custom handler, similar to what iframely does: https://github.com/itteco/iframely-wordpress/blob/master/iframely/iframely.php#L19-L23 " neverything Tickets Awaiting Review 51200 Consider a better way to deprecate JavaScript code Script Loader normal normal Awaiting Review enhancement new 2020-08-31T20:56:32Z 2020-08-31T21:30:53Z "Background: #51123 At the moment, we have some established functions for deprecating PHP functionality: * `_deprecated_function()` * `_deprecated_constructor()` * `_deprecated_file()` * `_deprecated_argument()` * `_deprecated_hook()` As well as some files to move deprecated functions to: * `wp-admin/includes/deprecated.php` * `wp-admin/includes/ms-deprecated.php` * `wp-includes/deprecated.php` * `wp-includes/ms-deprecated.php` * `wp-includes/pluggable-deprecated.php` We don't, however, have a similar way to deprecate JavaScript functionality, sometimes leading to more breakage than necessary when removing global objects or properties without backward compatibility considerations. [48923] attempted to improve things a bit introducing `deprecatedProperty()`. Some ideas previously suggested to further make sure we have a way to deprecate JavaScript code properly: * Have a clear deprecation policy of when the affected code should be removed. * Use the [https://developer.wordpress.org/block-editor/packages/packages-deprecated/ @wordpress/deprecated] package (suggested by @ocean90 in comment:33:ticket:51123). * Create a `deprecated.js` file for the code to be moved to (suggested by @desrosj on Slack)." SergeyBiryukov Tickets Awaiting Review 40427 Expose a JavaScript API to extend the Media Manager Media 4.8 normal normal Awaiting Review enhancement new 2017-04-12T17:30:38Z 2021-05-20T20:29:03Z "After talking with @mikeschroder as Pressnomics about how hard it was to extend the media manager, I wanted to open the discussion here for ways we could improve that. One way I made it work for the Stock Photo plugins at GoDaddy was to override core bindHandlers (see https://github.com/godaddy/wp-stock-photos/blob/master/assets/js/stock-photos.manifest.js#L13) and register my new view. One problem with that approach is that it makes it hard for anyone else to extend it for themselves. I'm turning out to the community so we can discuss ways we could expose hooks that would let anyone extend any part of the media manager experience. This could pave the way for awesome new plugins." jonathanbardo Tickets Awaiting Review 27127 Improve plugin search on installed plugins page Administration 3.8 normal normal Awaiting Review enhancement new 2014-02-14T17:16:53Z 2024-03-22T14:43:38Z "If you have lots of plugins installed trying to find one in the installed plugin page is not quick. The search box is quite slow ( requires a page refresh ). Adding some JavaScript that transforms the current search box into a quickfind box would help solve this problem. As the user types a keyword the JavaScript searched across the displayed text for the plugin, only displaying the plugins that contain that keyword." enej Tickets Awaiting Review 51159 Let's expand our context specific escaping methods for wp_json_encode(). Security normal normal Awaiting Review enhancement new 2020-08-27T18:54:00Z 2020-08-27T18:59:19Z " This document is largely sourced from a document written by @mdawaffe. Full credit to him for the research and thoughts put forward here. What I'd like to do is move this toward some actionable functions and developer best practices moving forward. `wp_json_encode()` is a handy helper for turning PHP into Javascript, and it is widely used in different places to serialize different variables. Imagine this hypothetical scenario: {{{ BAD:
}}} `json_encode()` serializes data into a string that can be used as a JavaScript literal* (e.g., `null`, `true`, `false`, `1234` (numbers), `""strings""`, `[ ""arrays"" ]`, and `{ ""objects"": ""oh my""}`.) JSON serialization, though, has nothing to do with HTML, and so does not treat characters that are special in HTML (`<`, `>`, `&`, `'`, `""`) in any special way: essentially, the code above is as bad as `echo $_GET['foo']`. Securing the above code is as simple as it always is in WordPress. We’re echoing data inside an HTML text node, so we use `esc_html()`: {{{ OK:
}}} Unfortunately, while secure 😀, this code is not actually correct ☹️. For historical reasons, `esc_html()` will not touch HTML entities (`&`): || Input || `htmlspecialchars()` || `esc_html()` || || `&` || `&` 😀 || `&` 😀 || || `&` || `&amp;` 😀 || `&` ☹️ || In the example above, if there are any HTML entities in $_GET, they will be echoed verbatim to the page, which means they will appear unescaped to the page’s visitor. === In an HTML Text Node === To faithfully represent the contents of a JSON blob in an HTML text node, the following code must be used: {{{ GOOD:
 `&amp;`
); ?>
}}}

This code is only appropriate for outputting JSON in HTML text nodes. There are several other contexts where we would like to output JSON, and each of those different contexts requires different treatment.

=== As an HTML Attribute Node === 

Though the HTML5 `.dataset` API only accepts string values for `data-*` attributes, jQuery will automatically parse `data-*` attribute values that are JSON serializations. So, when using jQuery, the following pattern is often handy:

{{{
BAD:
}}} Handy but, as we should know by now, insecure 😀. We need to HTML-escape the output. Like `esc_html()`, `esc_attr()` also leaves HTML entities untouched, so, again, the solution is to “manually” use `_wp_specialchars()`: {{{ GOOD:
`&amp;` ); ?>'> }}} It’s important to note that this code snippet is suitable for whole HTML attributes. It is not appropriate for use on part of an HTML attribute. In general, when we want to output a JSON blob as part of an HTML attribute, it’s because we’re trying to use it as a JavaScript literal: {{{ BAD: )""> }}} We’ve seen that using json_encode() by itself in this context is not secure, but neither is using the above HTML attribute code (`_wp_specialchars( json_encode(), … )`). In the `data-foo` case above, we’re outputting JSON. In the `onclick` case, we’re outputting a JavaScript literal. `_wp_specialchars()` does enough to the JSON blob to make it safe for use as an HTML attribute, but it does not do anything to make it safe for use within JavaScript. Despite claiming above that `json_encode()` outputs JavaScript literals, it’s more complicated than that. In a ` }}} There are multiple ways in which this is insecure. First, for some pages, HTML entities and the characters they represent are one and the same in the ` }}} Exactly how HTML entities are interpreted in }}} If we’re outputting a string, we can URL-encode it in PHP and URL-decode it in JavaScript. (We do have to make sure we use the right functions: `rawurlencode()` is slightly better than `urlencode()` here, and `decodeURIComponent()` is required over JavaScript’s deprecated `unescape()`.) The useful property of URL-encoding that we’re exploiting is that the transformed string is guaranteed not to have any characters in it that are regarded as special in the HTML context (`<`, `>`, `&`, `'`, `""`), so there’s no way to output `""` or an HTML Comment Opener. For non-scalar data, this can be extended via json_encode(): {{{ GOOD: }}} Rather than using the output of `json_encode()` as a JavaScript literal, the code above URL-encodes the whole serialization (braces, quotation marks and all), and we URL-decode and parse the resulting string in JavaScript to get back the structured data. This URL-encoding is a bit tedious and results in some ugly looking JavaScript. (Ugly JavaScript is better than vulnerable JavaScript!) We can instead use JavaScript’s Unicode-escaping: HTML Special Characters: {{{ }}} PHP’s `json_encode()` has an `$options` parameter, which can be used to always Unicode-escape these HTML special characters: {{{ ALMOST (PHP 5.3+): }}} These constants are only available as of PHP 5.3. Also, just replacing those characters isn’t good enough. We also need to Unicode-escape ``` and `$` because of their special meanings in JavaScript template literals. {{{ GOOD (PHP 5.3+): }}}" whyisjake Tickets Awaiting Review 54884 Load scripts conditionally to reduce page loading and processing time Script Loader normal normal Awaiting Review enhancement new 2022-01-23T09:56:03Z 2022-02-20T02:13:34Z "There are some core scripts, like `wp-polyfill` (+ `regenerator-runtime`?) and `jquery-migrate`, that are only needed on browsers lacking certain capabilities, yet these scripts are loaded on every page by default, whether the browser needs them or not. Since mobile browsers typically have the required capabilities, it's particularly important to avoid loading unnecessary scripts on them. This will improve user experience and PageSpeed scores, without any downside. Fortunately, browser capabilities can be detected with minimal JavaScript code, and only the necessary scripts added dynamically to the page using `appendChild()` (or maybe by manipulating script tag attributes?). There are also cases, such as `wp-embed`, that are only needed when there is an object embedded on the page, which can be detected in PHP. In both cases, there may be cases where the above scripts have dependencies that must be loaded, so both the respective front-end and back-end code must take dependencies into account. Also, browser checks should be done early and requires scripts inserted so as to provide their functions to subsequent code that relies on it (not trivial, I know, but I trust the skills of the WordPress team/community)." galbaras Tickets Awaiting Review 56774 Need more options on pre-existing blocks. Formatting 6.0.2 normal normal Awaiting Review enhancement new 2022-10-09T20:46:32Z 2022-10-09T20:46:32Z "I have the following queries regarding css customisation through pre-existing blocks. I want to add an option to: Add borderRadius to featured/post-image/cover/image Add breakpoints (let's say Bootstrap 5 responsive grid) More control over navigation/header padding/margin Set a default image when the post featured image is missing More control on the drop-down, especially translucent background-color and border-radius" adsingh14 Tickets Awaiting Review 52093 Open password field on click of New Password label on profile.php Users 4.3 normal minor Awaiting Review enhancement new 2020-12-16T15:24:52Z 2020-12-31T21:19:49Z "Enhancement Proposal: Where: In the Account Management section of the user's profile What: Trigger opening the password field when clicking on the **New Password** label The click event of every field on `profile.php` cursor focuses on the input field next to it. But that is not the case with ""New Password"" label. The enhancement proposal makes the new password label consistent with the other labels. " guddu1315 Tickets Awaiting Review 60234 Script Modules API: Add a translations API Script Loader normal normal Awaiting Review enhancement new 2024-01-11T15:14:58Z 2024-02-27T15:47:35Z "Now that WordPress is going to support native ES modules through the new [https://core.trac.wordpress.org/ticket/56313 Modules API], we should start discussing possible translation APIs to support internationalization/localization, similar to what `wp_set_script_translations` provides for the Scripts API. Some of the initial considerations are: - It should support the dynamic loading of translations when used in conjunction with dynamic imports (`import()`) to avoid downloading all the translations on page load. - Ideally, it should download the translations required in the initial page load in parallel to avoid waterfalls on page load. - Ideally, it should rely only on available PHP and JavaScript APIs, and not require any specific tooling. - Ideally, the APIs should be as transparent as possible to the developers. Please share your opinions and ideas. Let's use this ticket for discussion." luisherranz Tickets Awaiting Review 39282 The process for approving and then replying to a comment can be made more visible Comments 3.1 low normal Awaiting Review enhancement new 2016-12-14T18:17:51Z 2020-09-01T15:53:25Z "The workflow for approving and then immediately replying to a comment has a shortcut in WordPress, but it's not obvious. If you don't know about it, you can waste time and effort switching between the pending and approved views on the comment moderation screen after approving a comment and then wanting to reply to it. The `Reply` link on a pending comment is actually a shortcut for approving and then replying to a comment. The `Reply` link text should be updated to `Approve and Reply` to reflect this and make comment moderation a more enjoyable process." johnbillion Tickets Awaiting Review 27405 Widget Customizer: Fade out sidebar sections that lack any rendered widgets Widgets 3.9 normal normal Awaiting Review enhancement new 2014-03-13T21:44:19Z 2017-06-07T00:24:28Z "Currently when there is a widget that is not rendered in the current URL being previewed (e.g. via Widget Visibility), the widget control in the customizer will become semi-transparent to indicate it is not being rendered. The same semi-transparent indicator would be useful for sidebars that are empty or which lack any rendered widgets. Originally reported in https://github.com/x-team/wp-widget-customizer/issues/76" westonruter Tickets Awaiting Review 29910 esc_attr does not properly deal with json_encode Formatting normal normal Awaiting Review enhancement new 2014-10-09T17:54:32Z 2017-05-07T03:11:39Z "Current doing something like esc_attr( json_encode( $data ) ); doesn't work properly. Since the input to json_encode() above can contain '"'. And for calls to json_encode() lacking the JSON_HEX_AMP option, that '"' is left unaltered. Running '"' through esc_attr() also leaves it unaltered since esc_attr() does not double-encode. This means we end up with an attribute like {{{ data-gallery=""{"foo":"""} }}} which is interpreted by the browser as {{{ {""foo"":""""""} }}} which results in a JSON decoded error. The preferred workaround is to include the JSON_HEX_AMP (and friends) options, but these are not available until 5.3.0. Alternatively, we can use _wp_specialchars( , , , true ) instead of esc_attr(), which will double-encode. Since we can't rely on JSON_HEX_AMP, we do both. I would like to see a function like {{{ esc_json_encode( $data ) }}} That you can use to encode json data and pass it to the html. I have included a file that includes a functions that does just that. " enej Tickets Awaiting Review 48499 request: bundle unminified jQuery External Libraries 5.2.4 normal normal Awaiting Review enhancement new 2019-11-05T10:24:47Z 2019-11-05T15:53:15Z "This is a follow-up to #47020. WordPress is including a patched jQuery 1.12.4 now as we require this version but need to patch in security related fixes; whereas jQuery is supporting only newer versions. However we do not include an unminified jQuery. As a result this makes this makes it very hard to verify certain which patches are included, as the source code is not available, and the minification process differs from jQuery's therefore an online diff contains a lot of false positives. To have verifiable patches I'd like to request that we please keep a list of fixes somewhere (whether it's ticket numbers or full documentation), start including an unmodified jQuery, and verify the bundled jQuery contains all patches post 1.12.4. " pacifika Tickets Awaiting Review 53902 Automating the creation of inline javascript and inline stylesheet nonces or hashes Security normal normal Awaiting Review feature request new 2021-08-09T13:27:25Z 2022-01-03T22:22:26Z "Inline javascripts and stylesheets are fairly common in the WordPress ecosystem. Site managers wishing to harden WordPress via a Content Security Policy have a choice between allowing such inline code via the ""unsafe-inline"" directive or must find a way to include either hashes or nonces in the CSP and, for nonces, in the code itself. While there are means to determine hashes for static javascript or stylesheets, this is hardly possible for dynamically created code. It would help better secure WordPress sites if WP included the functionality that could automate the creation of nonces or hashes and automatically include them in a function that sends the appropriate, dynamically created, header via PHP or perhaps by writing to .htaccess or the like." Josiah S. Carberry Tickets Awaiting Review 47285 Better Management of External Asset Dependencies Script Loader normal major Awaiting Review feature request new 2019-05-15T18:36:15Z 2021-01-25T22:53:10Z "**Tl;Dr**: there **must** be a way for WordPress Plugins to indicate compatible versions of external dependencies, so as to reduce enqueuing multiple copies of the same external library. The issue is urgent with the ecosystem's migration to Blocks. **Problem** We've all been there; you install 3 plugins, and your website is enqueuing four copies of FontAwesome, and two copies of Bootstrap. Plus an extra one of each from your theme. Plus 3 different datepicker libraries and two ``s. Rough testing on Chrome on an 18-month old MacBook Air suggests The limit would probably need to be less than about 64-256 in order to keep the browser responsive (without modifying the unperformant code). The disadvantage of this approach is that long passwords can not be input by the keyboard, or will be truncated if pasted in. This might be an issue for users that use password managing software like OnePassword. We would need to investigate how long the passwords generated by such software is. For reference and comparison; - The server-side limit is currently 4096: https://github.com/WordPress/WordPress/blob/master/wp-includes/class-phpass.php#L217 - If a password is set that is longer than 4096 characters, WP silently fails to save the password." BevanR Tickets with Patches 51142 Invalid Moment.js locale from get_user_locale() External Libraries 5.0 normal normal Future Release defect (bug) new needs-unit-tests 2020-08-25T22:28:16Z 2023-06-30T08:37:12Z "`get_user_locale()` returns a locale in the format `en_US`, which is passed directly to Moment.js, e.g. `moment.updateLocale( 'en_US', {...} )`. Since Moment.js doesn't actually support two-part locales, this causes some issues. For example, `moment().format( 'Do' )` returns `25` where it should return `25th`. This is because the local *ordinal* is lost as a result of setting an undefined locale. The locale should either be passed in a format that Moment.js understands, such as `en`, or `moment.defineLocale( 'en_US', { parentLocale: 'en' } )` should be called before `moment.updateLocale( 'en_US', {...} )`. AFAIK these are equivalent. You can see the issue reproduced here: https://codepen.io/slightlyfaulty/pen/WNwpMmG Of course, swapping out old dusty Moment.js for its super modern and popular drop-in replacement [https://day.js.org/ Day.js] is also an option " slightlyfaulty Tickets with Patches 36157 Permalink UI shown without typing a title Permalinks 2.5 normal normal defect (bug) new needs-unit-tests 2016-03-07T15:11:15Z 2019-06-04T20:55:42Z "When creating a new post and jumping straight to the content to write a post the permalink UI will still be shown. '''Steps to reproduce:''' * 'Add New' post in the admin * Type content inside the post content field. * Wait until an autosave triggers and finishes. This step can also be achieved by putting `wp.autosave.server.triggerSave();` inside the console. '''Expected behaviour:''' The permalink UI isn't shown because no title has been set yet. '''Actual behaviour:''' The permalink UI is shown with a post ID as the slug." atimmer Unpatched Enhancements 42487 Avoid redundant crops for all Customizer media controls. Media normal normal Future Release enhancement new needs-unit-tests 2017-11-09T17:09:17Z 2019-02-07T21:45:56Z "In WordPress 4.9, we made use of context metadata to keep from producing redundant crops in the media library for custom headers (see #21819). We should extend this behavior to all other media controls in the Customizer (e.g., custom logos, site icon, etc.). There are a few parts to the implementation to keep in mind: 1. We should only create one cropped attachment per context for a given site/theme option. So for instance, if a custom logo has already been cropped from an attachment for the theme being customized, we should replace that attachment instead of creating a new one. However, we ''should'' create a new attachment if the crop was created for a different theme (this may not apply to site-level settings). 2. The context of an attachment should be included in the JSON model returned by `wp_prepare_attachment_for_js()` and used to filter contextual crops out of the main media attachment library. However, it would be great if those were ''not'' filtered when you've opened the media library from the context which those attachments are created/selected." joemcgill Unpatched Enhancements 35857 Add QUnit tests for Customizer preview, including Selective Refresh Customize 3.4 normal normal Future Release task (blessed) assigned needs-unit-tests 2016-02-18T08:26:15Z 2023-03-17T17:06:23Z "Initial Customizer unit tests for PHP and JS were added in #28579. The QUnit tests were done specifically for the Customizer controls (pane) and not the Customizer preview. This was understandable since he preview was devoid of much unique JS functionality. With the introduction of the Selective Refresh component (#27355), this has changed. There needs to be a new QUnit test suite specifically for the Customizer preview. See @valendesigns initial foundation work here: https://github.com/xwp/wp-customize-partial-refresh/pull/32/files#diff-6fcbfd120899db12c05cdb1f6142cd87 " westonruter Candidates for Closure 41387 Avoid 403's from AJAX requests from postbox.js Administration normal normal Awaiting Review defect (bug) new reporter-feedback 2017-07-20T15:34:23Z 2021-07-24T20:24:11Z "While making some improvements to a plugin's admin pages I changed the HTML in my meta boxes to be more inline with WordPress core. I then noticed that I was getting 403's from the closed-postboxes AJAX request each time I toggled the display of the postbox. Since I don't have a requirement for the open/closed state of my postboxes to persist I don't need the AJAX requests. Consequently I don't have a #closedpostboxesnonce. So, to avoid the 403's I changed postbox.js to not perform the AJAX request if the nonce isn't set. " bobbingwide Candidates for Closure 57899 Bad javascript in customize-controls.js for padding-top causes bugs Customize normal normal Awaiting Review defect (bug) new reporter-feedback 2023-03-09T23:06:44Z 2023-03-21T16:38:35Z "The code for sections ""Release header element if it is sticky."" and ""Reset position of the sticky header."" is very bad old code and should be coded in a more modern way now. This code causes bugs in many situations and should either be eliminated all together and replaced with modern css only/instead or improved javascript to not include a forced css for padding-top." akissz Tickets Needing Feedback 43444 CSS Editor Error Not Displaying Correctly Customize 4.9 normal normal Future Release defect (bug) new reporter-feedback 2018-02-28T22:55:14Z 2019-12-05T04:48:01Z "Every time I’m making a change in the custom CSS I get this annoying message that should only appear when I’m ready to publish changes. When I click publish and there’s errors, that’s when this notification needs to appear. I get it when I’m in the process of editing CSS and it always throws off my position when and I lose the location of where I was editing. It’s even worse when Inspect Element is pulled up. It should ONLY be giving me an error message when I’m going to publish the CSS changes. It’s literally notifying me of errors when I’m not finished editing the CSS. When I click “Publish” it needs to be notifying me of errors and then to confirm, not make me lose my placement and give me an error when I’m not even finished writing out what I need to… Screen capture: https://www.youtube.com/watch?v=cWyD4cYfpEA" nistuj817 Candidates for Closure 39762 Change in DOM Element Properties as seen in Javascript Event Handlers Between 4.6.2 and 4.7+ Administration 4.7 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-02-01T22:37:55Z 2021-04-06T05:27:06Z "I'm seeing a problem that appears to be related to the change introduced by ticket #37973 in 4.7. I don't see this issue in 4.6.2. I filed ticket #39739 earlier this week that documented another problem related to this change as well. This problem is also related to a ""select all"" checkbox but has to do with the state of child checkboxes within javascript event handlers being different between 4.6.2 and 4.7. In short, I have an event handler for ""click"" for the ""manage-column check-column"" checkbox (simplified HTML shown below). This event handler looks for child checkboxes in the table (""nslb_import_rows"") and triggers their ""click"" event accordingly. The ""click"" events are triggered so that additional HTML can be displayed on the page if certain conditions are met when the individual rows are selected / unselected or en masse via this ""select all"". {{{
Name
Steven
David
}}} Please note the first element with the class ""nslb-dynamic-content"". As the name implies, this content is created dynamically and added to the page via javascript as certain other options on the page are chosen. Because the inner HTML is added dynamically, when this code in common.js at line 459 at the 4.6.2 level executes: {{{ $('thead, tfoot').find('.check-column :checkbox').on( 'click.wp-toggle-checkboxes', function( event ) { ... }}} it doesn't find any elements that match the search criteria as they are not present on the page yet, therefore no event handlers are registered here. The HTML at this point would look only like this: {{{
}}} Conversely, the code in common.js at 4.7+ on line 452 that replaced this line {{{ $body.on( 'click.wp-toggle-checkboxes', 'thead .check-column :checkbox, tfoot .check-column :checkbox', function( event ) { ... }}} fires when the ""manage-column check-column"" checkbox is clicked even though it's in HTML that is added dynamically. This is because the line in 4.7+ handles click events in the body and then evaluates whether or not a ""check-column"" checkbox was clicked in a or as part of click event processing itself thereby finding my ""manage-column check-column"" checkbox"" in the DOM at that point. The net of effect of all this is a change in the value of the ""clicked"" property of these child checkboxes when my own click event handler executes. For example, in 4.6.2, if no checkboxes are selected on the page and I click my ""manage-column check-column"" checkbox, the ""clicked"" properties for the child checkboxes are ""false"" because the event handler on line 459 in common.js doesn't execute. However, in 4.7+ given the same scenario, the ""clicked"" properties for the child checkboxes are already ""true"" because the event handler on line 452 in common.js does execute each time. You could actually argue the behavior in 4.6.2 is defective since the handler does not get registered for ""check-column"" checkboxes added dynamically. FYI, if I hard code this exact HTML statically, then the 4.6.2 event handler does get registered and the ""clicked"" property for child checkboxes is consistent between 4.6.2 and 4.7+. Additionally, the code in common.js at the 4.7+ level could potentially trigger the ""click"" event for any child checkboxes it finds as opposed to just modifying their ""checked"" property, although I'm not sure of the ramifications of that type change." reldev Tickets Needing Feedback 36512 Color picker has disappeared from input in custom post type. Administration 4.5 normal normal defect (bug) new reporter-feedback 2016-04-13T14:55:37Z 2022-07-07T17:30:40Z "In a custom plugin I've created some metaboxes with color picker fields. Here how I call the color picker style : {{{ add_action( 'admin_enqueue_scripts', 'le_chiffre_add_color_picker' ); function le_chiffre_add_color_picker( $hook ) { // $hook to apply a check for admin page. wp_enqueue_style( 'wp-color-picker' ); wp_enqueue_script( 'custom-script-handle', plugins_url( 'custom-script.js', __FILE__ ), array( 'wp-color-picker' ), false, true ); } }}} the HTML input (created dynamically): {{{ }}} and the js for my input fields, loading the color picker: {{{ (function( $ ) { // Add Color Picker to all inputs that have 'color-field' class $(function() { $('.color-field').each(function(){ $(this).wpColorPicker(); }); }); })( jQuery ); }}} With WordPress 4.4.2 everything worked like a charm (I even did a reverse from 4.5 to 4.4.2 to be sure of it) and now with the 4.5 version, the color picker doesn't show up on my fields... I didn't found anybody having the same issue. Have a nice day David THOMAS " anou Candidates for Closure 59423 Datepicker in wordpress do not follow the Date format set in the settings External Libraries normal normal Awaiting Review defect (bug) new reporter-feedback 2023-09-21T12:21:16Z 2023-09-24T03:43:08Z "Go to wordpress > Settings > General over there select ""Date Format"" > ""Custom date"" and set it to ""jS F Y"" Once you do this it will show you date to be like this 21st September 2023 Now Add the below code in your theme function.php file this code will create a shortcode [datepicker] {{{#!php (media-views.min.js?ver=5.8-alpha-50521:2) at f (underscore.min.js?ver=1.8.3:2) }}} and the trace: {{{ (anonymous) @ media-views.min.js?ver=5.8-alpha-50521:2 f @ underscore.min.js?ver=1.8.3:2 setTimeout (async) (anonymous) @ underscore.min.js?ver=1.8.3:2 p @ backbone.min.js?ver=1.4.0:2 f @ backbone.min.js?ver=1.4.0:2 c @ backbone.min.js?ver=1.4.0:2 n.trigger @ backbone.min.js?ver=1.4.0:2 (anonymous) @ media-models.min.js?…r=5.8-alpha-50521:2 c @ load-scripts.php?c=0…r=5.8-alpha-50521:2 fireWith @ load-scripts.php?c=0…r=5.8-alpha-50521:2 (anonymous) @ wp-util.min.js?ver=5.8-alpha-50521:2 c @ load-scripts.php?c=0…r=5.8-alpha-50521:2 fireWith @ load-scripts.php?c=0…r=5.8-alpha-50521:2 l @ load-scripts.php?c=0…r=5.8-alpha-50521:2 (anonymous) @ load-scripts.php?c=0…r=5.8-alpha-50521:2 load (async) send @ load-scripts.php?c=0…r=5.8-alpha-50521:2 ajax @ load-scripts.php?c=0…r=5.8-alpha-50521:2 s.ajax.s.ajax @ load-scripts.php?c=0…r=5.8-alpha-50521:5 (anonymous) @ wp-util.min.js?ver=5.8-alpha-50521:2 s.Deferred.s.Deferred @ load-scripts.php?c=0…r=5.8-alpha-50521:5 send @ wp-util.min.js?ver=5.8-alpha-50521:2 sync @ media-models.min.js?…r=5.8-alpha-50521:2 fetch @ backbone.min.js?ver=1.4.0:2 more @ media-models.min.js?…r=5.8-alpha-50521:2 more @ media-models.min.js?…r=5.8-alpha-50521:2 edit @ media-editor.min.js?…r=5.8-alpha-50521:2 edit @ mce-view.min.js?ver=5.8-alpha-50521:2 edit @ mce-view.min.js?ver=5.8-alpha-50521:2 onclick @ plugin.min.js?wp-mce-49110-20201110:1 c.fire @ tinymce.min.js?ver=49110-20201110:2 fire @ theme.min.js?wp-mce-49110-20201110:1 o @ theme.min.js?wp-mce-49110-20201110:1 C @ tinymce.min.js?ver=49110-20201110:2 d @ tinymce.min.js?ver=49110-20201110:2 }}} " Chouby Tickets Needing Feedback 47545 Getting undefined wp.media.frame.state() after click on featured image preview antpb Media 5.2.1 normal normal Future Release defect (bug) assigned reporter-feedback 2019-06-15T13:29:15Z 2023-02-26T04:43:26Z " In WP 5.x: - When I click on the featured image preview the wp.media.frame.state().get('selection') is undefined. - But, when I click on the ""Replace image"" button wp.media.frame.state().get('selection') returns the selected attachment object (which is the expected behaviour). While in WP 4.x it returns correctly the attachment when I click on the featured image preview. " nlemsieh Candidates for Closure 57707 "Issue with ""Add New Application Password"" in profile page leading to empty error message" Application Passwords 6.1.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2023-02-13T18:42:06Z 2023-02-22T11:52:59Z "The issue I would like to report is in the profile page. When I try to ""Add New Application Password"", the request goes to the link ""Site Address (URL)/wp-json/wp/v2/users/1/application-passwords?_locale=user"" instead of the link ""WordPress Address (URL)/wp-json/wp/v2/users/1/application-passwords?_locale=user"". As a result, an empty error message appears if the ""Site Address"" is different from the ""WordPress Address"". [[Image(https://i.ibb.co/8N0B7xF/Screenshot-20230213-092733.png)]]" king-a-s Tickets Needing Feedback 29458 No longer able to catch click event of dashicons edit/delete Media 3.9 normal normal defect (bug) new reporter-feedback 2014-09-01T19:55:53Z 2019-06-04T20:08:56Z "In WP4 RC it's no longer possible to catch the dashicons edit button click through the tinyMCE onclick event. For example: {{{ tinymce.activeEditor.on('click', function() {alert('clicked')} ) }}} Never alerts. Is there a reason something's doing preventdefault or preventBubble? 3.9 was not affected by this. Are all shortcodes now '''required''' to do wp.mce.views.register(shortcodename, object) and include edit: function in the object? Related: (#28169)" programmin Candidates for Closure 42028 On-screen elements missing or dead in Mac OS 10.13 and Google Chrome Editor 4.7.4 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-09-29T03:17:26Z 2020-09-23T05:41:57Z "There are some bizarre bugs that appear when using Chrome (current version, Version 61.0.3163.100 (Official Build) (64-bit) as well as Chrome Canary (Version 63.0.3225.0 (Official Build) canary (64-bit) ) and WordPress 4.7.4, which include a) If I create a link then try to edit it so I can set the ""load in new tab"" check box, the page will ""freeze"" (become totally unresponsive, refusing to acknowledge clicks or scrolling, until I reloaded the Wordpress page) b) My ""edit snippet"" section is missing, requiring me to load this page in Safari to set the snippet. Relatedly, I am pretty sure setting a focus keyword in Chrome will not cause it to be saved, since I set it but then it was blank when the article was loaded in Safari. c) Perhaps most frustratingly, the Visual and Text tabs are nonfunctional in Chrome. I cannot access the page source, which I need for various scripts, as I should be able to. Please fix ASAP! Enclosing screenshots of the nonfunctional elements. [[Image(https://s3-us-west-2.amazonaws.com/megumi.img/ScreenShot2017-09-29at12.08.15PM.jpg)]] [[Image(https://s3-us-west-2.amazonaws.com/megumi.img/ScreenShot2017-09-29at12.10.42PM.jpg)]] [[Image(https://s3-us-west-2.amazonaws.com/megumi.img/ScreenShot2017-09-29at12.12.22PM.jpg)]]" ppayne Candidates for Closure 37878 Post filtering and use of Quick Edit Quick/Bulk Edit 4.7 normal normal Awaiting Review defect (bug) new reporter-feedback 2016-08-30T09:51:44Z 2023-02-07T19:06:34Z "Assuming I have a draft post I want to quickly publish. - I head to the Posts page. - I click on Draft above the list of posts, - I then click on Quick Edit, - Change the Post Status to Publish and Click update, - The Post Status will now be updated although it still appears on this list. A more expected result would be to remove / hide this post on update and also update the numbers of each status using AJAX. This also happens when changing to any other Post Status and includes Pages and Custom Post Types. " ShaneJones Tickets Needing Feedback 59915 Preview Whilst Editing Broken Editor 6.4.2 normal minor defect (bug) new reporter-feedback 2023-11-16T09:46:01Z 2024-02-09T12:52:31Z "When editing a page or post, trying to preview using the top right icon results in the URL wp-admin/undefined Previewing from the list of posts or pages works OK" simonjonharding Candidates for Closure 39946 Private posts can be sticky when bulk editing them from wp-admin/edit.php Quick/Bulk Edit normal normal Awaiting Review defect (bug) new reporter-feedback 2017-02-22T22:10:00Z 2023-02-07T19:11:34Z "[[Image(https://cldup.com/ZsJC4iH0GM.png)]] Although it's not possible to inline-edit a Private post to be sticky or to Publish a private post as sticky from the Publish meta box, as shown on the above screen capture, it's possible to do it using the Bulk edit action of the `wp-admin/edit.php` screen." imath Candidates for Closure 54179 Raw JS is prematurely ended with a tag when HTML tags are present within JS strings. General normal normal Awaiting Review defect (bug) new reporter-feedback 2021-09-24T13:42:03Z 2021-09-26T01:26:06Z "We are using a custom JS file that is reaching out to a web service, building a string from the data, and setting it as the innerHTML to a DOM Element already on the page. For some reason, HTML tags in this string were causing our script to get cut short, and whatever remained would instead by interpreted as HTML. A JavaScript snippet such as the following: {{{ myElement.innerHTML = ‘

My Content

’; }}} would cause a tag to be inserted between the

and
tags, cutting the JS short, leaving the rest to be read as HTML. The fix was to replace every tag in these strings with a chain of concatenations: {{{ myElement.innerHTML = ‘<’ + ‘div>’ + ‘<’ + ‘p>My Content’ + ‘<’ + ‘/p>’ + ‘<’ + ‘/div>’; }}} I don’t know what was causing this, but this workaround prevented whatever was processing our JavaScript from recognizing and interpreting the HTML tags." joshuapeck9898 Tickets Needing Feedback 35837 The auto-update in media editor rewrites user inputs Media 4.4.2 normal normal defect (bug) new reporter-feedback 2016-02-15T13:04:34Z 2019-06-04T20:22:32Z "Hello while the media editor is opened in ""lightbox"" where the auto-upade is applied the input fields loose their focus on each autoupade making the editing really uncomfortable. see this video https://youtu.be/ULmiAf2N6kA all the fields that you can see in this video were hooked up like so: https://gist.github.com/twentyfortysix/d7dcdc931aed3f2529a9#file-register_media_field-php" o----o Candidates for Closure 52634 Twenty Twenty: Child Theme Search Modal Safari Throws Error in Parent asset/index.js Bundled Theme 5.3 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-02-24T02:39:40Z 2021-10-28T04:00:39Z "Twenty Twenty child theme, search modal on safari throws error in parent asset/index.js when search toggle clicked. Works fine in all other browsers. TypeError: null is not an object (evaluating 'modal.querySelectorAll') elements = modal.querySelectorAll( selectors ); null is not an object (evaluating 'modal.querySelectorAll')" wp89mkt Tickets Needing Feedback 54412 Twenty Twenty: Letters move when opening accordion menu Bundled Theme 5.8.1 normal normal Future Release defect (bug) new reporter-feedback 2021-11-10T10:25:53Z 2023-04-28T15:53:28Z "I haven't changed anything, this is the original version of Twenty Twenty. This happens in any browser of the latest version, I have Windows 10. Gif - \\https://gifyu.com/image/ePvd screen - \\https://ibb.co/tX7XjTJ " mike77777 Candidates for Closure 57287 Type error calling Styles > Customize > Blocks from FSE Editor 6.1.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2022-12-07T03:48:59Z 2022-12-13T16:29:10Z "From FSE, When I open Styles pane, Then click ""Blocks"" I receive an error: {{{ TypeError: Cannot use 'in' operator to search for 'color' in at http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:72801 at Array.forEach () at ll (http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:72639) at Tl (http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:82514) at Cl (http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:82422) at Xl (http://localhost:10043/wp-includes/js/dist/edit-site.min.js?ver=3ab3e2570a5c4c270c72:12:103806) at ct (http://localhost:10043/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:43430) at os (http://localhost:10043/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:111136) at Ur (http://localhost:10043/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77643) at Ir (http://localhost:10043/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77571) }}}" ritterml Candidates for Closure 54621 Unsaved comment warning without any changes made when click on Publish, Update or Preview Buttons Comments 4.6 normal major Awaiting Review defect (bug) assigned reporter-feedback 2021-12-14T14:42:58Z 2022-03-18T16:47:44Z "Hi Team, I got unsaved comment changes warning without any changes made in the content of the custom post type post, here is screenshot: https://i.imgur.com/PQmirDL.png I see new codes are added in the WordPress core file: wp-admin/js/edit-comments.js And there is some condition issue, the code is have strict equality comparison operator to undefined ID which is not present in the custom post type: #replyrow Screenshot: https://i.imgur.com/kAHNkrs.png Please review it. Thanks" askaryabbas Candidates for Closure 54312 Widgets editor blocks Widgets 5.8.1 normal major Awaiting Review defect (bug) new reporter-feedback 2021-10-23T13:38:21Z 2022-02-16T08:32:44Z "Hi there, we have noticed a bug in widgets block. When editing Widgets in Blocks will repeat with errors and the console shows it is a JSON error stating 'The response is not a valid JSON response' and also says 503 error with it. Troubleshooting I have done: - Have tried downgrading versions, errors will be removed but unable to move widgets around. Now I have the current version. - Deactivating all plugins, one reactivated they come back and it is not related to a plugin. - did permalinks, - re did htaccess file - classic widgets plugin also takes away errors but you cant move widgets. none of these steps worked. Some guidance on what is happening would be greatly appreciated. Thank you " donno1 Candidates for Closure 52556 WordPress is adding   always Editor 5.6.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2021-02-17T14:44:45Z 2021-02-23T10:01:41Z "Hello, This bug is happening only if gutenberg editor is disabled. Ill try to explain in best way how wordpress is adding this  . 1. Create a new page 1.1 Type a title or without both give same result. 1.2 In content there should be nothing 1.3 Publish 2. After publish try to leave the page editing lest say clicking on dashboard from the menu. Wordpress will promp asking to save changes. If you are in visual editor and swap to text editor you will notice that   was added. 3. If you click update everytime wordpress will add a new   In inspector i have notice this script {{{ }}} If i put a breakpoint and reload the page will return thousandsSeparator undefined I dont know much about this function and the idea behind it but any ideas how to prevent this would be great. " snuffybg Candidates for Closure 56403 Write 'Activated' instead of 'Installed' for activated theme audrasjb Themes normal normal Awaiting Review defect (bug) reviewing reporter-feedback 2022-08-18T09:08:42Z 2022-08-18T15:22:40Z On theme-install page, there have text for all installed theme but it should be 'Activated' instead of 'Installed' for activated theme. alireyad Candidates for Closure 53789 all kinds of error messages using WordPress 5.8 Widgets block editor Widgets 5.8 normal major Awaiting Review defect (bug) new reporter-feedback 2021-07-26T22:35:24Z 2021-10-13T23:48:14Z "After the Upgrade to WordPress 5.8, in the backend when I choose Appearance / Widgets (to edit widgets), I get error messages like these: The ""blog_subscription"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""google_translate_widget"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""recent-posts"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""text"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""nav_menu"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""text"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""text"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""text"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""text"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""text"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""bbpmmymessages"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""text"" block was affected by errors and may not function properly. Check the developer tools for more details. The ""search"" block was affected by errors and may not function properly. Check the developer tools for more details. I installed and activated the Classic Widget Editor plugin so I could function. Later (after an update from one of the Widget providers), I deactivated the CWE plugin so I could see if this provider's widgets were now working with the 5.8 Widget block editor. (Some were fixed, some weren't). Unbelievably, though, I got more errors than before showing that widget blocks which seemed to be working before now were not working! I got a lot of Internal Error messages, whereas before I only saw one or two of these. Did switching to the Classic Widget Editor and then deactivating cause more problems? Now every time I try to access the 5.8 Widgets block editing, I get new or different errors. Very confusing and upsetting. " janecarole Candidates for Closure 43453 heartbeat_received filter requires data in order to execute Plugins 3.6 normal normal Awaiting Review defect (bug) new reporter-feedback 2018-03-01T15:38:38Z 2022-02-26T22:34:38Z "With regards to the heartbeat api, the plugin developer handbook states: Not every feature will need all three of these steps. For example, if you don’t need to send any data to the server, you can use just the latter two steps. But this does not seem to be the case given this line of of [https://core.trac.wordpress.org/browser/tags/4.9/src/wp-admin/includes/ajax-actions.php#L2808 wp_ajax_heartbeat]. This makes it less useful if you just want to include some new data on an interval. It requires an approach like: {{{ #!javascript $( document ).on('heartbeat-send', (e, data) => { data.wouldLikeFilterToTrigger = true; }); $(document).on('heartbeat-tick', (e, data) => { // do something with data generated by filter console.log(data); }); }}} If you omit the send event, the filter on the server never runs. It seems like this constraint should be lifted, or at the very least the documentation should be updated." brianscaturro Tickets Needing Feedback 35504 response to adding data to taxonomy shows in a wrong place Taxonomy 4.4.1 normal normal defect (bug) new reporter-feedback 2016-01-17T22:55:55Z 2020-06-04T05:50:50Z "Hello, i created a custom taxonomy and when i try to add an item, item will be successfully add but response from ajax request to add this data show's in wrong place and the table not getting updated. response data showing as the message value instead. i toke screenshot. and i tested my codes and wordpress healthy time and time over. I'm Sure it's core bug. [[Image(http://uupload.ir/files/kuv1_bug.jpg)]]" ehsanaghaei Candidates for Closure 59132 Create two filters in wp_scripts() and wp_styles(). Script Loader 4.2 normal normal Awaiting Review enhancement new reporter-feedback 2023-08-17T18:19:00Z 2023-11-27T21:00:48Z "I'd like to know if it's possibile to change this: {{{#!php bulk_upgrade( array( $plugin ) );}}} called, and any other update progress run on same time. Eg: there are translations update exists and when contain errors on translations update, the plugin update tell that the plugin fail to download, but the plugins successfully updated. " arrayiterator Candidates for Closure 32143 wpLink function getAttrs() missing link-text Editor 4.2 normal normal Awaiting Review enhancement new reporter-feedback 2015-04-27T07:04:06Z 2020-11-24T01:38:12Z "After last update to 4.2 wpLink() was renewed and the title-input was replaced. Instead of title, you can now insert/change the link text. https://core.trac.wordpress.org/browser/trunk/src/wp-includes/js/wplink.js?rev=32017 But in function getAttrs() the val of link-text was forgotten. Therfor I proporse to add this line in getAttrs(): linktext: $.trim( inputs.text.val() ), Also it would be nice to populate the link-text field with the document title of a chosed intern element, like it was made with the old title-field before. " xwolf Candidates for Closure 40872 Add $item argument to start_lvl (nav menu walker) Menus 4.7.5 normal normal Awaiting Review feature request new reporter-feedback 2017-05-26T20:08:47Z 2017-06-28T07:45:39Z "Would it be possible to add the $item argument inside the start_lvl function? Other than the usual dropdown menu, I'd also like to build megamenus and to make that possible, I need to use different ul tags (along with some JavaScript components). These custom ul tags will be different based on the parent li ((array) $item->classes) and $depth. " mireillesan