-
Notifications
You must be signed in to change notification settings - Fork 4k
Closed
Description
Describe the bug
Upgrading a 3.13.x system to 4.x with your system theme set to dark causes the management UI to cease working.
Reproduction steps
- Clear your browser cache to start fresh.
- Enable your system's dark theme (optional)
- Start RabbitMQ 3.13.x and log into the management UI.
- Stop RabbitMQ 3.13.x, and start RabbitMQ 4.x.
- Return to the management UI and refresh/force-refresh it.
- Once refreshed, the UI ceases to work and the dev tools shows the following error:
content_script.js:1 content script loaded 38f38f44-a4a1-445f-b3a0-fb06aafaafae credentials.js:1 Injecting credentials patch sammy-0.7.6.min.js:5 [Wed May 28 2025 10:48:40 GMT-0700 (Pacific Daylight Time)] body Plugin Error: called use() but plugin (Sammy.Title) is not defined Cannot read properties of undefined (reading 'apply') TypeError: Plugin Error: called use() but plugin (Sammy.Title) is not defined Cannot read properties of undefined (reading 'apply') at Sammy.Application.use (sammy-0.7.6.min.js:5:7826) at Sammy.Application.dispatcher (main.js:77:10) at new Sammy.Application (sammy-0.7.6.min.js:5:6748) at start_app (main.js:197:11) at dispatcher_add (main.js:72:9) at dispatcher.js:1:1 main.js:78 Uncaught TypeError: this.setTitle is not a function at Sammy.Application.dispatcher (main.js:78:10) at new Sammy.Application (sammy-0.7.6.min.js:5:6748) at start_app (main.js:197:11) at dispatcher_add (main.js:72:9) at dispatcher.js:1:1
- After the above happens, you are unable to do anything in the management UI. Only clearing the cache resolves the issue. Thankfully, that appears to permanently resolve the issue. Running the UI in a private/incognito window also works, presumably because assets are not cached.
Expected behavior
Upgrading from 3.13.x to 4.x does not compromise the behavior of the management UI.
Additional context
Related issues: