Site breaks when trying to choose existing media
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- next.js, react, typescript
- Domain
- frontend
Research direction
Start by reproducing the failure from the image field with “choose from existing,” then close the media picker as described. Inspect the admin media picker and image-field flow involved in the dismissal; done means the picker closes without the admin crashing, the image field remains usable, and the existing-media workflow still works.
Written by the indexing model from the issue text.
Description
https://github.com/user-attachments/assets/45ddac1c-7da7-459f-afb6-19f0f5531dd1
Describe the Bug
I have a problem with the image field. I have beforechanges in my media collection to move images to YYYY/MM/filename so there's no duplicate images to deal with. The problem I'm having is when I clicking on "choose from existing" the media panel popups and then disappears. The image field disappears and you can't click on anything on the site. Enclosed is a screen capture of the problem and zip of my src to look around
Link to the code that reproduces this issue
none
Reproduction Steps
Click on choose from existing and then close the media picker. Usually the second click is when the admin crashes.
Which area(s) are affected?
Not sure
Environment Info
Binaries:
Node: 24.15.0
npm: 11.16.0
Yarn: N/A
pnpm: N/A
Relevant Packages:
payload: 3.85.0
next: 16.2.6
@payloadcms/db-mongodb: 3.85.0
@payloadcms/graphql: 3.85.0
@payloadcms/next/utilities: 3.85.0
@payloadcms/richtext-lexical: 3.85.0
@payloadcms/translations: 3.85.0
@payloadcms/ui/shared: 3.85.0
react: 19.2.6
react-dom: 19.2.6
Operating System:
Platform: linux
Arch: arm64
Version: #22-Ubuntu SMP PREEMPT_DYNAMIC Mon May 25 15:37:49 UTC 2026
Available memory (MB): 15433
Available CPU cores: 4
- Dominant language
- TypeScript
- Stars
- 44.8k
- Forks
- 4.2k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 53
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.
More from payloadcms/payload
-
area: ui Bug status: needs-triage v3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
payloadcms/payload#18215 · 1 comment ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
payloadcms/payload#18163 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
payloadcms/payload#18161 ·
-
area: core Bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
payloadcms/payload#18072 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
payloadcms/payload#18067 · 1 comment ·
All issues in payloadcms/payload
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·