BuidlZone-Labs/zicket-web

Broken Navigation Routes Hit 404 Pages Across App

Open

#173 opened on Jul 29, 2026

View on GitHub
 (9 comments) (0 reactions) (1 assignee)TypeScript (43 forks)auto 404
Stellar Wavebugfrontendgood first issuehelp wanted

Repository metrics

Stars
 (4 stars)
PR merge metrics
 (PR metrics pending)

Description

Category

Bug

Priority

Critical

Description

Multiple primary navigation links throughout the header, signup, and verification flows link to non-existent route paths:

  1. Header.tsx#L44 contains { name: "Plans", href: "/plans" }, but no app/plans directory exists.
  2. SignupForm.tsx#L21 redirects to router.push("/verify") instead of /auth/verify.
  3. VerifyPage#L67 redirects to router.push("/dashboard") which loads outside the organizer layout navigation (/zkorg).

Proposed Solution

  1. Create app/plans/page.tsx or update navigation items to point to valid routes.
  2. Fix route path references in SignupForm.tsx to /auth/verify.
  3. Align dashboard redirection after verification to /zkorg.

Acceptance Criteria

  • Clicking "Plans" in header navigates to a valid plans page.
  • Submitting the signup form navigates to /auth/verify.
  • Completing mail verification navigates to /zkorg.
  • No 404 errors encountered in primary user auth flows.

Files

  • app/components/Header.tsx
  • app/components/Auth/SignupForm.tsx
  • app/auth/verify/page.tsx

Contributor guide

Research direction
Inspect the app directory structure to map existing routes. For each affected file, trace how navigation links and router.push calls are constructed. Verify the correct paths for the plans page, auth verify page, and dashboard (zkorg) by looking at existing pages and route groupings.
Tech stack
typescriptreactnextjs
Domain
frontendauthentication
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNext.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75