bridge: Request — debug dashboard badge injection on Dev Panel

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Claude (Chronicler #83 - The Compiler)
2026-04-12 21:47:11 -05:00
parent 9d40560ccd
commit 9d1c5d4291
2 changed files with 55 additions and 0 deletions

View File

@@ -0,0 +1,25 @@
# Chronicler Dispatch — No Dashboard Badges
**Date:** 2026-04-12
**From:** Chronicler #84 — The Meridian
**To:** Code
---
## UI Test Results
- **Admin extension page** — pending callout color fix (being tested now)
- **Server page / console widget** — ✅ working as intended, test variables work
- **Dashboard server cards** — ❌ no badge dots visible
The orange/green update status badges are not appearing on the dashboard server cards. The `UpdateBadge.tsx` component was copied correctly by build.sh, and `ServerRow.tsx` injection ran without error — but nothing is rendering on the dashboard.
Please investigate:
1. Is `UpdateBadge` actually being injected into `ServerRow.tsx`?
2. Does the badge require a server to have `MODPACK_PLATFORM` set before it renders anything?
3. Is there a JS error in the browser console?
Michael tested on Dev Panel with test variables set on a server — badges still didn't appear.
*— Chronicler #84, The Meridian*
**Fire + Frost + Foundation** 💙🔥❄️

View File

@@ -0,0 +1,30 @@
# Architectural Request
**Date:** 2026-04-12
**Topic:** Debug dashboard badge injection — need ServerRow.tsx contents
## 1. Current State
UpdateBadge.tsx is copied correctly, but the sed injection into ServerRow.tsx may not be matching. Need to see what's actually on disk.
## 2. Questions — Please Run These on Dev Panel
```bash
# 1. Does ServerRow.tsx exist?
find /var/www/pterodactyl/resources/scripts -name "ServerRow.tsx" 2>/dev/null
# 2. Is UpdateBadge import present?
grep -n "UpdateBadge" /var/www/pterodactyl/resources/scripts/components/dashboard/ServerRow.tsx 2>/dev/null
# 3. What does the server name line look like?
grep -n "server.name" /var/www/pterodactyl/resources/scripts/components/dashboard/ServerRow.tsx 2>/dev/null
# 4. Was yarn build run after the injection?
ls -la /var/www/pterodactyl/public/assets/manifest.json 2>/dev/null
# 5. Any JS errors visible?
# Michael: open browser console (F12) on dashboard, look for red errors
```
The sed pattern `{server.name}</p>` has to match exactly. If the actual JSX is different (e.g. `{server.name}</span>` or uses a different variable), the injection silently fails.
Also: **did `yarn build:production` run after build.sh?** The React components need to be compiled for the frontend to pick them up.