WordPress.org
Get WordPress

Make WordPress Core

Changes between Version 1 and Version 6 of Ticket #66047


Ignore:
Timestamp:
09/08/2026 09:29:50 AM (12 days ago)
Author:
369work
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #66047

    • Property Milestone Awaiting Review → 7.1.1
    • Property Keywords needs-testing added

  • Ticket #66047 – Description

    v1 v6  
    11== Bug Report
    22=== Description
    3 Site Editor (Appearance > Identity) goes completely blank after uploading and saving a new Site Icon, when the browser has accumulated stale site data (Cache storage / IndexedDB / Local storage) from a previous WordPress/Gutenberg version on the same site. 
     3Site Editor (Appearance > Identity) goes completely blank after uploading and saving a new Site Icon, when the browser has accumulated site data (Cache storage / IndexedDB / Local storage) from prior use of this site. In my case that prior use was repeated media uploads in the block editor.
    44
    55
    … …  
    2121
    2222=== Steps to Reproduce
    23 1. Use a browser profile that has previously visited this site's Site Editor across an earlier WordPress/Gutenberg version (accumulated Cache storage / IndexedDB / localStorage).
     231. Use a browser profile that has previously used this site's Site Editor and accumulated site data (Cache storage / IndexedDB / localStorage). A clean profile does not reproduce it.
    24242. Go to Site Editor > Styles > (or Appearance > Editor) > Identity.
    25253. Upload a new Site Icon and confirm the crop (removing an existing Site Icon reproduces the same crash as well).
    26264. Click Save, then confirm in the review/publish dialog.
    2727x.  The entire admin screen goes blank (only the admin toolbar remains visible).
     28
     29Please note: these steps may still not be enough to reproduce this. There is an additional precondition in the browser's stored state that I have not been able to identify.
     30 
    2831Query Monitor's toolbar item shows "Data collection ceased". The browser console shows:
    2932
    … …  
    4043=== Actual Results
    41441.  The Site Editor screen renders fully blank (no error message shown to the user) after the save confirmation. The site icon IS actually saved successfully server-side (visible elsewhere in wp-admin after reload) — this is a client-side rendering crash, not a save failure.
     452.  `wp-content/debug.log` stays empty — no PHP error is logged.
    4246
    4347=== Additional Notes
    … …  
    4852[[Image(console-error.png)]]
    4953
    50 - This suggests the Site Editor (likely the `wp/preferences` / editor state persisted in browser storage) does not gracefully handle stale data left over from an earlier WordPress/Gutenberg version, and crashes uncleanly instead of falling back.
     54- This site has always been WordPress 7.1. No version upgrade was involved, and the Gutenberg plugin had never been activated on it — the accumulated data is from ordinary use of 7.1 itself. Before hitting this, the same browser profile had been used for repeated media uploads in the block editor (HEIC upload testing for https://github.com/WordPress/gutenberg/issues/81043).
     55- I cleared the storage before inspecting its contents, so I cannot say which piece of stored state actually triggers this.
    5156
    52 - Possibly related to #65912 ("wordpress 7.1 broke site icon") — that report also involves the site icon breaking shortly after upgrading to 7.1, which would also involve stale pre-upgrade browser storage, though the visible symptom there (oversized icon in the toolbar) differs from this one (blank Site Editor screen).
    53 not claiming they're the same root cause.