{"id":11293,"date":"2026-07-10T15:04:45","date_gmt":"2026-07-10T09:34:45","guid":{"rendered":"https:\/\/4ksamachar.com\/?p=11293"},"modified":"2026-07-10T15:04:45","modified_gmt":"2026-07-10T09:34:45","slug":"gutenberg-times-wordpress-7-0-1-fixes-registration-spam-wp_kses-css-corruption-and-7-0-admin-design-glitches","status":"publish","type":"post","link":"https:\/\/4ksamachar.com\/?p=11293","title":{"rendered":"Gutenberg Times: WordPress 7.0.1 Fixes Registration Spam, wp_kses() CSS Corruption, and 7.0 Admin Design Glitches"},"content":{"rendered":"<p class=\"wp-block-paragraph\">WordPress 7.0.1 is now available. As the first maintenance release of the 7.0 cycle, it\u2019s strictly a bug-fix release: every included ticket addresses either a regression introduced during 7.0 development or an issue intentionally deferred at the end of the cycle.<\/p>\n<p class=\"wp-block-paragraph\">The release ships fixes for 17 core Trac tickets and 14 Gutenberg PRs. Because this is a maintenance release, sites with automatic background updates enabled will update to 7.0.1 automatically \u2014 everyone else should update as soon as possible. Here\u2019s what stands out for each audience.<\/p>\n<p class=\"wp-block-paragraph\">Kudos to release lead Aaron Jorbin and his team for pushing this release over the finish line and getting it into hands of WordPress users quickly. <\/p>\n<h2 class=\"wp-block-heading\">The most important fixes for end users<\/h2>\n<p class=\"wp-block-paragraph\"><strong>Registration page spam is shut down (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/63085\" target=\"_blank\" rel=\"noopener\">#63085<\/a>).<\/strong> The account registration page could be abused to send \u201cLogin details\u201d spam emails from your site. This is arguably the most impactful fix in the release for anyone running a site with open registration \u2014 it protects both your users\u2019 inboxes and your domain\u2019s email reputation.<\/p>\n<p class=\"wp-block-paragraph\"><strong>The 7.0 admin reskin gets its rough edges sanded off.<\/strong> WordPress 7.0\u2019s refreshed admin design shipped with a handful of visual glitches that this release cleans up:<\/p>\n<ul class=\"wp-block-list\">\n<li>Form elements are now standardized in the mobile viewport (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64999\" target=\"_blank\" rel=\"noopener\">#64999<\/a>)<\/li>\n<li>The image editor\u2019s scale and crop inputs no longer mismatch in size, and the info icon uses the new color scheme (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64937\" target=\"_blank\" rel=\"noopener\">#64937<\/a>, <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65428\" target=\"_blank\" rel=\"noopener\">#65428<\/a>)<\/li>\n<li>The publish settings panel no longer crowds its primary action buttons together (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65286\" target=\"_blank\" rel=\"noopener\">#65286<\/a>)<\/li>\n<li>The Media Library\u2019s loading spinner is properly aligned in the modal filter toolbar, and the search bar no longer jumps position after a search (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65275\" target=\"_blank\" rel=\"noopener\">#65275<\/a>, <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65296\" target=\"_blank\" rel=\"noopener\">#65296<\/a>)<\/li>\n<li>A \u201cblack flash\u201d that briefly appeared on wp-admin pages before the interface finished loading is gone (Gutenberg <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/78493\" target=\"_blank\" rel=\"noopener\">#78493<\/a>)<\/li>\n<\/ul>\n<p class=\"wp-block-paragraph\"><strong>Emoji behave correctly again.<\/strong> Two related fixes: the emoji detection script is once more printed in the admin (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65310\" target=\"_blank\" rel=\"noopener\">#65310<\/a>), and certain characters are no longer incorrectly replaced by Twemoji images (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64318\" target=\"_blank\" rel=\"noopener\">#64318<\/a>).<\/p>\n<p class=\"wp-block-paragraph\"><strong>Accessibility improvements to the new revisions experience.<\/strong> The Visual History \/ Revisions feature introduced in 7.0 receives several accessibility fixes: focus now moves to the revisions slider when entering revisions mode, and changed blocks are marked with a CSS outline as a secondary, non-color indicator \u2014 important for users with low vision or color blindness (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65122\" target=\"_blank\" rel=\"noopener\">#65122<\/a>, Gutenberg <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/77530\" target=\"_blank\" rel=\"noopener\">#77530<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/78393\" target=\"_blank\" rel=\"noopener\">#78393<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79691\" target=\"_blank\" rel=\"noopener\">#79691<\/a>).<\/p>\n<h2 class=\"wp-block-heading\">The most important fixes for developers<\/h2>\n<p class=\"wp-block-paragraph\"><strong><code>wp_kses()<\/code> no longer corrupts valid CSS (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65270\" target=\"_blank\" rel=\"noopener\">#65270<\/a>).<\/strong> Since 7.0 RC4, <code>wp_kses()<\/code> could mangle legitimate <code>background-image: url(\u2026)<\/code> declarations into a broken <code>style=\")\"<\/code> attribute. If your theme or plugin outputs inline background images through KSES-filtered content, 7.0.1 restores expected behavior \u2014 any workarounds you shipped can now be removed.<\/p>\n<p class=\"wp-block-paragraph\"><strong><code>global-styles-inline-css<\/code> can be dequeued again (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65336\" target=\"_blank\" rel=\"noopener\">#65336<\/a>).<\/strong> Since 7.0, developers were unable to remove the global styles inline stylesheet. If your build pipeline or performance optimization strips this and re-serves it another way, that control is back.<\/p>\n<p class=\"wp-block-paragraph\"><strong>PHP 8.5 compatibility fix in <code>wp_get_attachment_image_src()<\/code> (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64742\" target=\"_blank\" rel=\"noopener\">#64742<\/a>).<\/strong> An incorrect array access triggered issues under PHP 8.5. If you\u2019re testing sites on newer PHP versions, this removes one blocker.<\/p>\n<p class=\"wp-block-paragraph\"><strong>A removed Navigation function returns as a deprecated shim (Gutenberg <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/78484\" target=\"_blank\" rel=\"noopener\">#78484<\/a>).<\/strong> <code>block_core_navigation_submenu_render_submenu_icon()<\/code> was removed in 7.0, breaking themes and plugins that called it directly. It\u2019s restored as a deprecated shim \u2014 but treat this as your migration notice, not a reprieve. Update any code that references it.<\/p>\n<p class=\"wp-block-paragraph\"><strong>Editor state management fixes reduce false \u201cunsaved changes\u201d warnings.<\/strong> Two Gutenberg fixes matter here: <\/p>\n<ul class=\"wp-block-list\">\n<li>controlled\/mode block changes are now marked non-persistent (<a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79350\" target=\"_blank\" rel=\"noopener\">#79350<\/a>), and <\/li>\n<li>related navigation entities are no longer dirtied during passive renders (<a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79000\" target=\"_blank\" rel=\"noopener\">#79000<\/a>). <\/li>\n<\/ul>\n<p class=\"wp-block-paragraph\">Together these should mean fewer spurious dirty states and a cleaner undo history \u2014 a quality-of-life improvement if you build with template parts and navigation blocks.<\/p>\n<p class=\"wp-block-paragraph\"><strong>Block Visibility: \u201chide everywhere\u201d keeps working after a block opts out of visibility support (<a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65389\" target=\"_blank\" rel=\"noopener\">#65389<\/a>).<\/strong> If you register blocks that disable visibility support, previously hidden instances now stay hidden as expected.<\/p>\n<h2 class=\"wp-block-heading\">How to update<\/h2>\n<p class=\"wp-block-paragraph\">You can update directly from <strong>Dashboard \u2192 Updates<\/strong> in your site\u2019s admin, run <code>wp core update<\/code> with WP-CLI, or download WordPress 7.0.1 from WordPress.org and install it manually. Sites that support automatic background updates for minor releases will begin updating on their own shortly.<\/p>\n<p class=\"wp-block-paragraph\">The full ticket list is available in the<a href=\"https:\/\/make.wordpress.org\/core\/2026\/07\/01\/wordpress-7-0-1-rc1-is-now-available\/\" target=\"_blank\" rel=\"noopener\"> release candidate announcement<\/a>, Trac report 4, and the 7.0.x editor tasks board on GitHub.<\/p>\n<h2 class=\"wp-block-heading\">What\u2019s next: WordPress 7.1<\/h2>\n<p class=\"wp-block-paragraph\">With 7.0.1 out the door, attention turns to the next major release: WordPress 7.1 is scheduled for August 19, 2026. To see what\u2019s planned for the release, check out the <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/19\/roadmap-to-7-1\/\" target=\"_blank\" rel=\"noopener\">Roadmap to 7.1<\/a> on the Make WordPress Core blog.<\/p>\n<p class=\"wp-block-paragraph\">\n","protected":false},"excerpt":{"rendered":"<p>WordPress 7.0.1 is now available. As the first maintenance release of the 7.0 cycle, it\u2019s strictly a bug-fix release: every included ticket addresses either a regression introduced during 7.0 development or an issue intentionally deferred at the end of the cycle. The release ships fixes for 17 core Trac tickets and 14 Gutenberg PRs. Because [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-11293","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"blog_post_layout_featured_media_urls":{"thumbnail":"","full":""},"categories_names":{"1":{"name":"Uncategorized","link":"https:\/\/4ksamachar.com\/?cat=1"}},"tags_names":[],"comments_number":"0","wpmagazine_modules_lite_featured_media_urls":{"thumbnail":"","cvmm-medium":"","cvmm-medium-plus":"","cvmm-portrait":"","cvmm-medium-square":"","cvmm-large":"","cvmm-small":"","full":""},"_links":{"self":[{"href":"https:\/\/4ksamachar.com\/index.php?rest_route=\/wp\/v2\/posts\/11293","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/4ksamachar.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/4ksamachar.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/4ksamachar.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/4ksamachar.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=11293"}],"version-history":[{"count":0,"href":"https:\/\/4ksamachar.com\/index.php?rest_route=\/wp\/v2\/posts\/11293\/revisions"}],"wp:attachment":[{"href":"https:\/\/4ksamachar.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=11293"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/4ksamachar.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=11293"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/4ksamachar.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=11293"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}