__group__ Stars Comments ticket summary reporter owner component _version priority severity milestone type _status workflow _created modified _description _reporter Has Patch / Needs Testing 14 60754 Block Hooks: Incorrect context passed when setting ignored hooked blocks metadata Bernhard Reiter General trunk normal normal 6.5.1 defect (bug) new has-patch 2024-03-12T11:17:36Z 2024-03-28T12:32:36Z "Since [57790], the `rest_pre_insert_wp_template` and `rest_pre_insert_wp_template_part` hooks in the Templates Controller are used to call `inject_ignored_hooked_blocks_metadata_attributes()`, which in turn sets the `ignoredHookedBlocks` metadata attribute on anchor blocks upon writing to the DB. The latter function applies the `hooked_block_types`, `hooked_block`, and `hooked_block_{$hooked_block_type}` filters, in order to inform which blocks should be hooked to a given anchor block. Each of these filters is given a `$context` argument, which in the case of templates (and template parts, respectively) is the containing `WP_Block_Template` object. Since the `rest_pre_insert_`-prefixed filters only pass a `stdClass` object for the relevant `$changes` that need to be made to the relevant template (or template part), `$context` is constructed by fetching the existing template (or part) via `get_block_template()` (using the template/part ID present in the network `$request`). This isn't quite how things should be: `hooked_block_types`, `hooked_block`, and `hooked_block_{$hooked_block_type}` should be given a `$context` object that reflects the template (part) that is about to be persisted to the database, ''not'' the one that's currently stored there. A filter might e.g. look for the presence of a certain block in the template's content; that block might not have been present in the previous version of a template (stored in the DB) but might've been added by the user in the editor (and will be part of the payload that's used to update the DB)." Bernhard Reiter Needs Merging from Trunk 33 109 60398 "WordPress 6.4.3 MacOS/Linux Compressed Zip plugin archives ""Incompatible Archive"" on upload" Endymion00 peterwilsoncc Upload 6.4.3 normal normal 6.4.4 defect (bug) reopened commit 2024-01-31T11:42:20Z 2024-03-20T20:52:58Z "If I zip a plugin folder using MacOS right-click Compress command in the contextual menu, those archives are no longer accepted when using upload plugin. It returns ""Incompatible Archive"". This has worked up until now. Probably related to recent security updates for the plugin and theme uploader. If I create a zip on the command line of the same folder that works correctly." Endymion00 Needs Dev / Bug Wrangler Feedback 2 9 60808 Twenty Twenty-Four: Black outline around the Navigation block submenu-expanding button jordesign Bundled Theme trunk normal normal 6.5.1 defect (bug) new dev-feedback 2024-03-20T03:01:53Z 2024-03-28T07:05:58Z "This appears to be a regression introduced in https://core.trac.wordpress.org/changeset/57739 Brought over from the Gutenberg repo: https://github.com/WordPress/gutenberg/issues/59944 ---- == Description When a sub-menu item is present, when clicking on the sub-menu item or on the parent menu item, a black border is shown around the items. [[Image(https://cldup.com/kNOVprCJ_d.png)]] Video: https://cloudup.com/cm8LVp_p6kN == Step-by-step reproduction instructions 1. go to the site editor 2. add a navigation block 3. add an item and a sub item 4. publish changes and visit the site 5. click on the sub-menu item and on the parent item 6. see the black border == Environment info WordPress 6.5 RC2 2024 theme == Please confirm that you have searched existing issues in the repo. Yes == Please confirm that you have tested with all plugins deactivated except Gutenberg. Yes" jordesign Needs Merging from Trunk 2 9 60827 Patterns menu item, put back the context parameter. kebbet audrasjb I18N trunk normal normal 6.5.1 defect (bug) reopened has-patch 2024-03-22T14:14:46Z 2024-03-27T22:44:53Z "This is a follow up for the next minor release, 6.5.1 and the previous ticket #60825 The commit message by @audrasjb in [57864] stated: `A follow-up changeset will be needed to replace the current __() function with _x() and put back the context parameter.` This is what should replace the call to `__()`: `_x( 'Patterns', 'site editor menu item' )`" kebbet Needs Reporter Feedback / Steps To Reproduce 4 6 60809 .editor-styles-wrapper styles opacity changed killerbeez Editor trunk normal normal 6.5.1 defect (bug) new reporter-feedback 2024-03-20T03:57:30Z 2024-03-25T23:27:02Z "In WordPress 6.4.3, the block editor automatically applies this to `.editor-styles-wrapper`: {{{ .editor-styles-wrapper.mce-content-body, .editor-styles-wrapper.editor-styles-wrapper { opacity: 1; } }}} While testing WordPress 6.5, this no longer occurs. Our theme has `opacity: 0` applied to the body, and we use jQuery to change it to `opacity: 1` when the DOM is loaded. This means that in 6.5, our block editor has 0 opacity. The issue for us is that this also applies to the block editor and as a result we see a grey box instead of the blocks of content. In testing with WordPress Alpha 6.6 or with the latest Gutenberg activated this doesn't appear to be the case, is there a reason this was removed from the 6.5 core?" killerbeez Needs Merging from Trunk 1 30 60290 Changeset #56635 breaks template loading in multisite network using switch_to_blog() metropolis_john joemcgill Themes 6.4.2 normal normal 6.4.4 defect (bug) reopened changes-requested 2024-01-18T19:53:51Z 2024-03-06T08:27:49Z "The changes to the `locate_template()` function in https://core.trac.wordpress.org/changeset/56635 that replaced STYLESHEETPATH and TEMPLATEPATH constants with the relevant functions have broken the `get_template_part()` functionality in a multisite network that uses `switch_to_blog()`. Expected behavior: `get_template_part()` should only look in the active theme of the current site even after `switch_to_blog()` is used. In WP 6.4.2, if `switch_to_blog(1)` is used in site 2, then `get_template_part()` is called, only the active theme of site 1 is searched for the template part. `switch_to_blog()` should only affect database calls and should not allow theme developers to pull template parts from the theme of another site in a network. " metropolis_john Needs Patch 1 2 60716 "Font Library: Replace error message ""A font face matching those settings already exists"" with notice" oglekler Editor trunk normal normal 6.5.1 enhancement new 2024-03-07T03:25:56Z 2024-03-20T21:13:07Z If the font already exists, it is not an error, and should not scare the user. oglekler Needs Dev / Bug Wrangler Feedback 3 21 60614 Button block's Outline style does not have border in non-framed editor viralsampat Editor trunk normal normal 6.5.1 defect (bug) new dev-feedback 2024-02-23T03:44:34Z 2024-03-25T04:18:49Z "Hello, I have reviewed the button block and found that the button ""outline"" does not appear on the editor side. Here, I have attached its screenshots: **Environment info -----------------** Device: Macbook M1 OS: 14.3.1 (23D60) Browser: Google Chrome Version 121.0.6167.184 (Official Build) (arm64) WordPress version: 6.4.3 running, Gutenberg 17.7.0, Theme active: Twenty Twenty-Two, Thanks," viralsampat Needs Patch 3 60836 Static homepage display settings: the posts page is not being assigned to the Blog Home template or Index template west7 Themes trunk normal normal 6.5.1 defect (bug) new 2024-03-24T23:44:19Z 2024-03-25T11:10:20Z "When I use 6.5 Beta Tester plugin and change to static homepage display, Home and Blog, the blog page is assigned to the Pages template, not the Blog Home or Index template. I don't have any other plugins installed, only Beta Tester. I am using Local and tried both the Twenty Twenty-Two and Twenty Twenty-Four themes. The expected output when changing to static homepage display is that the posts page will be assigned to the Blog Home template or Index template. " west7