WordPress 7.0.1 Now Available, Fixes 31 Bugs ![rw-book-cover](https://www.therepository.email/wp-content/uploads/2026/07/wordpress-7-0-1.jpg) 🔗 **Source:** [WordPress 7.0.1 Now Available, Fixes 31 Bugs](https://www.therepository.email/wordpress-7-0-1-now-available-fixes-31-bugs) > [!note]+ Document Notes > tags: [wordpress, maintenance-release, block-editor, wp-kses, release-management] > author: [MISSING] > source: The Repository > reference: https://www.therepository.email/wordpress-7-0-1-now-available-fixes-31-bugs > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: WordPress 7.0.1 Now Available, Fixes 31 Bugs > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [WordPress 7.0.1 Maintenance Release (WordPress.org News)](https://wordpress.org/news/2026/07/wordpress-7-0-1-maintenance-release/) - [WordPress 7.0.1 RC1 (Make WordPress Core)](https://make.wordpress.org/core/2026/07/01/wordpress-7-0-1-rc1-is-now-available/) - [WordPress 7.0 "Armstrong" coverage (The Repository)](https://www.therepository.email/wordpress-7-0-armstrong-ships-with-ai-infrastructure-modernized-dashboard-and-new-design-tools) - [WordPress 7.1 planning (The Repository)](https://www.therepository.email/wordpress-7-1-planning-kicks-off-with-august-19-release-date-during-wordcamp-us) - [Download WordPress](https://wordpress.org/download/) ## 📝 Summary - WordPress 7.0.1 shipped as a maintenance release fixing 31 bugs across Core and the block editor, seven weeks after 7.0 "Armstrong." - It matters because it stabilizes the areas 7.0 changed most — block editor, admin UI (the reskin), and media — where regressions surfaced after a milestone release. - Key stakeholders: core committer Aaron Jorbin (release lead) plus Brian Haas, Carlos Bravo, and Estela Rueda; 80+ total contributors; hosting providers and site owners. - Risk/tradeoff: only about a week of RC testing (RC1 on July 1) before final; sites with auto-updates were patched automatically, others must update manually. - Bottom line: a routine but consequential cleanup release, notably fixing a `wp_kses()` regression that corrupted inline CSS background images. ## 📖 Main Content - WordPress 7.0.1 is a maintenance (point) release. Maintenance releases fix bugs and regressions without adding features, following a major release. - The headline fix is a regression in `wp_kses()` — WordPress's HTML sanitization function — that mangled valid `background-image: url(…)` declarations down to a bare `style=")"`, breaking any theme or plugin using inline background images. - Several fixes address the admin "reskin" introduced in 7.0: inconsistent form elements on mobile, misaligned image editor scale/crop inputs, and a broken header logo on the network credits page. - The media library got fixes for a misaligned loading spinner and a search bar that jumped position after a search. - The block editor received 14 fixes: accessibility improvements to the visual revisions interface, a copy-to-clipboard callback that didn't always fire, a black flash on wp-admin pages before hydration, and a navigation block bug where Page List failed to detect whether it sat inside a submenu. - A Block Visibility fix: the "hide everywhere" setting broke when a block opted out of visibility support — a regression that appeared after 7.0. - Release cadence context: RC1 landed July 1, giving roughly a week of testing. WordPress 7.1 is scheduled for August 19 at WordCamp US in Phoenix, with Beta 1 on July 15. ### 🗒️ Notes - Scope: 31 bugs total, 14 of them in the block editor. - Release lead: Aaron Jorbin (core committer), with Brian Haas, Carlos Bravo, Estela Rueda. - `wp_kses()` regression is the most developer-relevant: sanitizer stripped valid inline `background-image` CSS to `style=")"`. Affected themes/plugins relying on inline background images. - Admin reskin fallout (all new in 7.0): mobile form rendering, image editor crop/scale alignment, network credits page logo. - Media library: spinner alignment + search bar position shift. - Block editor detail: revisions a11y, copy-to-clipboard callback reliability, pre-hydration black flash, navigation block Page List submenu detection. - Block Visibility: "hide everywhere" broke for blocks opting out of visibility support. - Timeline: 7.0 shipped ~7 weeks prior; RC1 July 1; final "just over a week" later; 80+ contributors credited. - Distribution: auto-background-update sites already patched; others update via dashboard or direct download. - Forward look: 7.1 targeted Aug 19 (WordCamp US, Phoenix); Beta 1 July 15. ## 📚 References - [WordPress 7.0.1 Maintenance Release](https://wordpress.org/news/2026/07/wordpress-7-0-1-maintenance-release/) — primary announcement - [WordPress 7.0.1 RC1](https://make.wordpress.org/core/2026/07/01/wordpress-7-0-1-rc1-is-now-available/) — release candidate post - [WordPress 7.0 "Armstrong" coverage](https://www.therepository.email/wordpress-7-0-armstrong-ships-with-ai-infrastructure-modernized-dashboard-and-new-design-tools) - [WordPress 7.1 planning](https://www.therepository.email/wordpress-7-1-planning-kicks-off-with-august-19-release-date-during-wordcamp-us) - [Download WordPress](https://wordpress.org/download/) ## 🗣️ Paraphrase - WordPress released a bug-fix update, 7.0.1, that resolves 31 issues in the core software and the block editor, arriving about seven weeks after the feature-heavy 7.0 release. - The fixes concentrate on the parts 7.0 overhauled: the block editor, the redesigned admin interface, and media handling — including a sanitizer bug that broke inline CSS background images, several admin-reskin alignment problems, and a batch of 14 block editor corrections. Auto-updating sites already have it; everyone else can update manually. ## 📰 Newsletter - WordPress 7.0.1 is out and it's the housekeeping kind of release — 31 bugs squashed, 14 of them in the block editor. If your theme leans on inline `background-image` CSS, you'll want this one: a `wp_kses()` regression had been quietly gutting those declarations down to a sad little `style=")"`. Aaron Jorbin led the effort with 80+ contributors pitching in. Auto-update sites are already sorted; the rest of us click "Update" and move on. Next up: 7.1 lands August 19 at WordCamp US in Phoenix, with Beta 1 on July 15. ## ✅ Action Items #### WordPress - Core: Note the `wp_kses()` inline-CSS regression pattern for future sanitizer-change review gates. - Accessibility: Track the visual revisions interface a11y fixes as a positive signal; verify against WCAG in future audits. - Hosting: Confirm auto-background-update coverage pushed 7.0.1 across managed fleets. - Support: Watch for tickets tied to inline background images or admin-reskin mobile form rendering. ## 🧪 Hypotheses - Not applicable to this source. This is a factual release announcement, not an argument generating testable claims. ### 📊 Methodology - Not applicable to this source. No study or empirical method is presented. ### ❓ Questions - Was one week of RC testing enough given the breadth of 7.0's admin/block changes, or should point releases after milestone releases get longer bake time? - Will the `wp_kses()` regression prompt tighter regression tests around sanitization of inline styles? ### 🔮 Future Research - Not applicable to this source. News item, no research gaps to pursue. ### 💡 Implications - Milestone releases (7.0) that touch broad surface area predictably generate regressions; a fast follow-up maintenance release is the mitigation pattern. - Sanitization changes carry outsized blast radius — a single `wp_kses()` regression affected any inline-background-image usage site-wide. ### 🧠 Learning Styles Assessment - Reading level estimate: approx. Flesch-Kincaid Grade 11–13 (dense technical vocabulary, moderate sentence length). Formula: Flesch-Kincaid Grade Level, estimated. #### 👀 Visual learners - Present: one dashboard screenshot with descriptive caption. - Improve: a before/after of the `style=")"` corruption; a timeline graphic of 7.0 → RC1 → 7.0.1 → 7.1. #### 🔊 Aural learners - Present: none. - Improve: a 60-second audio changelog summary. #### 🗣️ Verbal learners - Present: inline definition of `wp_kses()` as the sanitization function; concrete example (`style=")"`). - Improve: brief glossary for "maintenance release," "hydration," "reskin." #### 🧩 Kinesthetic learners - Present: direct "update from the dashboard or download it directly" call to action. - Improve: step-by-step update checklist. #### 🧠 Logical learners - Present: clear cause→effect on the sanitizer bug; numbered scope (31 bugs, 14 block editor). - Improve: a categorized table of fixes by subsystem. #### 🧑‍🤝‍🧑 Social learners - Present: contributor credits (named leads + 80+ contributors). - Improve: links to contributor discussion threads. #### 🧘‍♀️ Solitary learners - Present: self-contained update instructions. - Improve: a "what to test on your site" self-check. #### 🌿 Naturalistic learners - Not applicable to this source. No environmental framing relevant. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: figure has descriptive alt text and figcaption; paragraph structure is clean. - Improve: ensure headings hierarchy in the source page (article uses paragraphs only). #### Keyboard navigation - Not applicable to this source. Static article text; no interactive components to assess. #### Contrast and readability - Not assessable from HTML alone; presumed standard publisher styling. #### Text resizing and reflow - Present: responsive image `srcset`/`sizes` provided. #### Media and captions - Present: image alt text and figcaption. - Improve: no audio/video, so no captions needed. #### Forms and interactions - Not applicable to this source. No forms present. #### Standards reference - Alt text and figcaption support WCAG 2.2 1.1.1 (Non-text Content). ### 🌍 DEIB Assessment - Not applicable to this source. A technical release note with named international contributors (Carlos Bravo, Estela Rueda) but no DEIB content to evaluate. ### ✅ Logical Validity #### Strong reasoning - Causal clarity (para 3): the article ties the `wp_kses()` regression directly to corrupted `background-image` declarations and names the observable symptom (`style=")"`). Strong because cause, mechanism, and effect are all stated. - Contextual inference (para 2): frames the fixes as clustering in "areas that saw significant changes in 7.0," a reasonable inductive link between milestone churn and regressions. #### Fallacies - None material. Reporting is descriptive and sourced; no argumentative overreach. #### Tone of voice - Neutral, informational trade-press tone. Example: "The maintenance release, led by core committer Aaron Jorbin… addresses issues in the block editor, admin UI, and media." ### 🛡️ DARVO Analysis - Not applicable to this source. No accusation, defense, or conflict framing present. ## 🎯 Conclusion - Bottom line: WordPress 7.0.1 is a routine maintenance release that cleans up 31 bugs — most concentrated in the block editor, admin reskin, and media — with the standout being a `wp_kses()` sanitizer regression that broke inline background images. - Next steps for readers: if auto-updates are on, you're already patched; otherwise update via the dashboard. Developers relying on inline background CSS should confirm the fix resolved any `style=")"` corruption. Mark July 15 (7.1 Beta 1) and August 19 (7.1 release at WordCamp US). ## 🔄 Refactor Appendix — WordPress 7.0.1 Now Available, Fixes 31 Bugs > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) #### [H1] wp_kses regression corrupted inline background-image CSS > [!quote] ID:rw_manual > a regression in `wp_kses()` — the function WordPress uses to sanitize HTML — that was corrupting valid CSS `background-image: url(…)` declarations, stripping them down to a bare `style=")"` **Context & use**: - Para 3 of the article; the headline developer-facing fix in 7.0.1. - Matters because sanitization changes have site-wide blast radius: one regression hit every theme/plugin using inline background images. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### [H2] Maintenance releases stabilize milestone-release regression surface > [!quote] ID:rw_manual > addresses issues in the block editor, admin UI, and media, all areas that saw significant changes in 7.0’s milestone update **Context & use**: - Para 2; explains why the fixes cluster where they do. - Matters as a release-management pattern: big feature releases predictably need a fast follow-up. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Sanitizer changes carry site-wide blast radius **Claim** (one sentence, Courtney's voice): A change to a shared sanitization function like `wp_kses()` can break every consumer of a given markup pattern at once, so sanitizer edits need regression tests across all affected output shapes. **Evidence pointer**: [[#H1]] **Scope & conditions**: Holds for any centralized input/output filter; breaks down for narrowly scoped, single-caller helpers. **Links**: - [[WordPress Security Trinity]] — because applies-in sanitize/escape context - [[Regression testing]] — because evidence-for <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Watch whether 7.1 adds inline-style sanitization regression tests — https://make.wordpress.org/core/ #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Confirm 7.0.1 auto-updated across managed sites and check for inline background-image breakage — #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/WordPress 7.0.1 Now Available, Fixes 31 Bugs.md|WordPress 7.0.1 Now Available, Fixes 31 Bugs by therepository.email]] ## Highlights - all areas that saw significant changes in 7.0’s milestone update ([View Highlight](https://read.readwise.io/read/01kx6gwjtc783t1fc49tyvrpvx)) - Note: The maintenance-release-after-milestone pattern — fixes cluster where 7.0 changed most. - Tags: atom/literature/h2 - Among the more notable fixes is a regression in `wp_kses()` — the function WordPress uses to sanitize HTML — that was corrupting valid CSS `background-image: url(…)` declarations, stripping them down to a bare `style=")"`. The bug affected any theme or plugin relying on inline background images. ([View Highlight](https://read.readwise.io/read/01kx6gxbjxvtgv2eqdgsj5j4z4)) - Note: Headline developer-facing fix — a sanitizer regression with site-wide blast radius on inline background images. - Tags: atom/literature/h1 ## Links - [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] — A second release account reinforces the scale of corrective maintenance. - [[3. Resources/MOCs/Commons & Community Governance MOC]] — WordPress maintenance-release record.