📝 WordPress: Fix the Classic Editor Toolbar Missing After an Update
A core or plugin update bumps the version query string on every enqueued script and style so browsers know to fetch the new files instead of a cached copy — but that only works if nothing else is caching the admin screen itself. A caching plugin or server-level cache that’s been told (correctly or not) to also cache wp-admin pages can keep serving the pre-update HTML, which still points at script versions the browser has already cached too, so the toolbar’s init call never runs with matching, current files.
🔎 The Problem
Expected after update: <script src='.../wp-admin/js/editor.js?ver=6.7.1'></script> Actually served from a stale admin-page cache: <script src='.../wp-admin/js/editor.js?ver=6.6.2'></script> -> old editor.js loads against new TinyMCE core files -> toolbar never inits
✅ Fix: Confirm the Admin Screen Itself Isn’t Cached
- Hard-refresh the editor screen (bypassing browser cache) and check the page source for the actual script version numbers being loaded — if they don’t match the plugin/core version you just updated to, the HTML itself is stale.
- In your caching plugin’s settings, explicitly exclude
/wp-admin/from any page cache; the dashboard and editor should never be served from a cache in the first place. - Open the browser console on the editor screen and look for a script error from an unrelated plugin; one failing script before TinyMCE’s init call can stop the toolbar from being built even when every asset version is correct.
🚨 Why This Is Dangerous
- Troubleshooting a missing toolbar by reinstalling or downgrading the Classic Editor plugin, when the real cause is a stale cached admin page, can leave the site on an older plugin version than necessary while the actual caching misconfiguration goes unnoticed.
The one screen that always has to be live is the one you’re editing in — a cache that doesn’t know to leave wp-admin alone will eventually hand you yesterday’s editor instead of today’s.
