payloadcms / payloadcms/payload
Bug: @payloadcms/plugin-multi-tenant causes 404 with Next.js 16.2.3 + Turbopack
Open
Nobody has claimed this yet.
plugin: multi-tenant
stale
- Dominant language
- TypeScript
- Stars
- 44.8k
- Forks
- 4.2k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 53
Description
Describe the Bug
The @payloadcms/plugin-multi-tenant plugin causes a 404 error when navigating to tenant-enabled collections in the admin panel when using Next.js 16.2.3 with Turbopack.
Link to the code that reproduces this issue
https://github.com/metageeks-tech/payloadcms-testcms.git
Reproduction Steps
- Create a new Payload project with Next.js 16.2.3
- Install @payloadcms/plugin-multi-tenant@3.82.1
- Configure the plugin with collections enabled
- Navigate to /admin/collections/posts or any tenant-enabled collection
- Result: 404 error page
Which area(s) are affected?
plugin: multi-tenant
Environment Info
Next.js: 16.2.3 (with Turbopack)
Payload: 3.82.1
@payloadcms/plugin-multi-tenant: 3.82.1 (also tested 3.83.0-canary.3)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Clone the linked payloadcms-testcms reproduction and first reproduce the 404 at /admin/collections/posts using Next.js 16.2.3 with Turbopack and @payloadcms/plugin-multi-tenant. Trace the tenant-enabled collection route through the multi-tenant plugin and compare behavior without the plugin; done means the affected admin collection routes load instead of returning 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100