bug: campaign detail pages ignore the route id and always render one hardcoded mock campaign

[JamesVictor-O]

Problem

Every campaign detail route ignores its own params.id and renders one hardcoded mock campaign, regardless of which campaign was actually clicked.

app/marketplace/[id]/page.tsx:

export default function CampaignDetailPage({ params }: { params: { id: string } }) {
  const campaign = campaignDetailMock;   // params.id is never read

app/dashboard/business/campaigns/[id]/page.tsx:

const campaign = campaignDetail; // always mock for now — params.id ignored

Meanwhile the marketplace grid correctly generates distinct links for each of the 13 campaigns in components/marketplace/marketplace-data.ts (nextgen-wallet, lumen-node, cross-border, ...), via Link href={/marketplace/${campaign.id}} in marketplace-grid.tsx. Every one of those routes currently renders the identical campaignDetailMock object (id: "quantum-wearables"), no matter which card was clicked.

Compounding bug

ApplicationForm's "already applied" check is keyed by campaign-application:${campaignId} in sessionStorage, and campaignId defaults to campaignDetailMock.id (components/marketplace/application-form.tsx:17-21) since the page never passes the real id down. So once a creator applies to any campaign, every other campaign's detail page falsely shows "APPLICATION SUBMITTED!" as if they'd already applied to that one too.

Concrete failure scenario

1. Creator browses the marketplace, clicks into "NextGen Wallet Launch" — sees the "Quantum Wearables" brief/budget/requirements instead.
2. Clicks into "Lumen Node Validator" — sees the exact same "Quantum Wearables" content again.
3. Applies to one campaign. Every other campaign in the marketplace now silently shows as already-applied, blocking legitimate applications to genuinely different campaigns.

Expected behaviour

Look up the campaign by params.id from the same dataset used to build the marketplace/dashboard lists, and 404/redirect on an unknown id. Scope the sessionStorage "already applied" key to the real per-campaign id, not a shared default.

Note: app/dashboard/business/campaigns/[id]/page.tsx also still types params synchronously ({ id: string }) rather than Promise<{ id: string }> — unlike the already-correct app/dashboard/creator/campaigns/[id]/page.tsx, which does async function ... { params: Promise<PageParams> } and await params. The app is on Next.js 16, where dynamic route params are async; align the business page to the same pattern while wiring up the real id lookup, since it's currently only harmless because the page never reads params.id at all.

Files

• app/marketplace/[id]/page.tsx
• app/dashboard/business/campaigns/[id]/page.tsx
• components/marketplace/application-form.tsx — sessionStorage key scoping

Acceptance criteria

• app/marketplace/[id]/page.tsx renders the campaign matching params.id, not a hardcoded mock
• app/dashboard/business/campaigns/[id]/page.tsx does the same, and adopts the async params: Promise<{id: string}> pattern already used on the creator side
• An unknown id shows a proper not-found state instead of falling back to an arbitrary campaign
• The "already applied" sessionStorage key is scoped per real campaign id — applying to one campaign no longer marks unrelated campaigns as applied

[nyuiela]

I'd like to take this.

I looked at apps/frontend/app/marketplace/[id]/page.tsx on current HEAD. generateMetadata and the page both bind campaignDetailMock and never read params.id. ApplicationForm defaults campaignId to campaignDetailMock.id, so campaign-application:${id} in sessionStorage is shared across every marketplace card.

Plan:

• Resolve the campaign from marketplace-data.ts by params.id (404 if missing) and pass that id into ApplicationForm.
• Do the same lookup on app/dashboard/business/campaigns/[id]/page.tsx.
• Keep the mock object only as a fixture, not the runtime source.

please assign this to me if that works.

[SudiptaPaul-31]

Hey Maintainer!!! My name is Sudipta Paul a very old contributor of GrantFox and other platform having quite a lot of experience in open source and working with full stack issues as well as very much proficient in writing contracts and would love to work on this issue and contribute to your project, May I be assigned to this task

[Wetshakat]

Hi maintainer
I will like to work on this issue
ETA 4hrs

[grantfox-oss]

🦊 GrantFox — @SudiptaPaul-31 has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #142)
2. Your PR will be reviewed by the Ads-Bazaar maintainers

Good luck! Track your progress on GrantFox.