PLUTO-52 ·
pluto404: /administrar/docentes/[id] dead link from /admin/solicitudes (live, 3 real-user hits)
- Ref
PLUTO-52(#924)- Project
pluto- Status
- done
- Priority
- normal
- Type
- bug
- Assigned
- —
- Created by
- wi-cli-venus
- Created
- 2026-06-12T05:50:20.408Z
- Updated
- 2026-06-12T06:11:30.290Z
- Closed
- 2026-06-12T06:11:30.290Z
Questions
No questions.
Event log
-
From appEvents analysis (db-pluto-cc, 2026-06-12). clientError:not-found, route /administrar/docentes/[uuid], 3 hits in rapid succession 2026-04-24, actor 98b5383b, referrer /admin/solicitudes. The access-requests admin page links to /administrar/docentes/[id] which 404s. Fix: correct the link in admin/solicitudes OR implement the route. Read-only finding — needs coder.
-
CORRECTION (db resolved actor): 98b5383b = Elazar (admin, testing the app), same person behind the other /admin 404s — NOT real-user traffic. But the broken link is genuine: /admin/solicitudes links to /administrar/docentes/[id], a route that does not exist; any admin clicking through hits the 404. Still a real link bug to fix (implement the docente-detail route OR repoint the link), just low urgency — no real users affected yet.
-
Not-a-bug / stale (coder verified, read-only). The 3 /administrar/docentes/[id] 404s are ALL 2026-04-24; that route's [id]/page.tsx was CREATED 2026-04-27 (2e7adc4) — 404s predate the route by 3 days. Route exists+works now, docente eeb083a6 exists, ZERO docente 404s since 04-24. Also: NO /admin/solicitudes -> /administrar/docentes/[id] link exists in current code OR git history (db's 'referrer=/admin/solicitudes' did not hold up) — the only builder is docentes-grid.tsx:637 (legit, manageRoster-gated, off the /administrar/docentes list). Nothing to repoint or implement. Same April-testing-stale pattern as PLUTO-53/55.