Media database bug (Image / PDF)

[philippkdhl]

Describe the Bug

When you upload an image to Payload, smaller resolution versions of the image are also generated (provided you have configured this). Then you need to save.
If you edit the image after saving and replace it with a PDF, all images with the adjusted resolution are deleted, but the link in the database remains.

Link to the code that reproduces this issue

i cant push the repo - i will add the media collection

Reproduction Steps

1. Upload an Image (configure also imageSizes)
2. Save the image
3. Edit image and delete the upload
4. replace the upload with an pdf

--> The images will be deleted on disk but the image size entry will be keept in database

Which area(s) are affected?

Not sure

Environment Info

Binaries:
  Node: 22.16.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  payload: 3.80.0
  next: 16.2.1
  @payloadcms/db-mongodb: 3.80.0
  @payloadcms/email-nodemailer: 3.80.0
  @payloadcms/graphql: 3.80.0
  @payloadcms/next/utilities: 3.80.0
  @payloadcms/payload-cloud: 3.80.0
  @payloadcms/plugin-search: 3.80.0
  @payloadcms/richtext-lexical: 3.80.0
  @payloadcms/translations: 3.80.0
  @payloadcms/ui/shared: 3.80.0
  react: 19.2.4
  react-dom: 19.2.4
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Enterprise
  Available memory (MB): 64957
  Available CPU cores: 14

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload

[immotus]

That is surely an edgy case 🤣
I would not have even thought of such a bait and swap scenario)))