mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Status page has no auto-theme button #2693
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2693
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wc7086 on GitHub (Oct 17, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
Description
👟 Reproduction steps
Edit status page
👀 Expected behavior
Allows the status page to automatically select a theme
😓 Actual Behavior
Status page has no auto-theme button
🐻 Uptime-Kuma Version
1.23.3
💻 Operating System and Arch
Windows Server 2012 x64
🌐 Browser
EDGE 118.0.2088.46
🐋 Docker Version
No response
🟩 NodeJS Version
18.18.2
📝 Relevant log output
No response
@chakflying commented on GitHub (Oct 17, 2023):
Please check if you are actually running the latest version.
@wc7086 commented on GitHub (Oct 17, 2023):
Sorry, I typed the wrong system, I am using
Windows Server 2012Installation command(https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install#-non-docker)
Update Command(https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update#--non-docker)
@chakflying commented on GitHub (Oct 17, 2023):
The page should also show your Frontend version if installed correctly.
You have most likely updated incorrectly, and the frontend is stuck in an old version. Please follow the instructions in the wiki carefully, make sure there are no errors during the
download-diststep before restarting the server.@wc7086 commented on GitHub (Oct 17, 2023):
When I repeated the upgrade process and cleared the browser cache, the front-end version showed up correctly. This could be a caching issue. I will revise the content of this issue later.