Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Link fieldtype allows multiple assets per drag and drop

Open
#12,033 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
laravel, php
Domain
frontend

Research direction

Reproduce the issue in a fresh Statamic installation by adding a link fieldtype to a blueprint and dropping multiple images into its upload area. Compare its behavior and save-time validation with an asset fieldtype configured with max_items set to 1. Done means the link field handles multiple dropped assets consistently with the asset fieldtype; the issue does not specify which behavior should be preferred.

Written by the indexing model from the issue text.

Description

fieldtypes
Bug description

When adding multiple assets per drag and drop to a link field, it keeps all three instead of just one. After saving there's only one left. The asset fieldtype (with max_items set to 1) also allows that, but throws a validaton error on save, so editors have a little more control over which assets they need to delete.

There are kind of two minor bugs in this issue: The behaviour of being able to upload multiple assets into the asset fields and the different behaviour of validation of the asset fieldtype component and the link asset component. Both are confusing for editors, but I think having the same validation with both components would already help a lot. I can open another issue if that's better.

Here's a screen recording of the behaviour of the link asset component:
https://github.com/user-attachments/assets/a736b359-f369-428d-97eb-c0261dc3f8b2

How to reproduce
  • Set up a fresh Statamic
  • Add a link fieldtype to any blueprint
  • Drag and drop multiple images into the upload area
Logs

Environment
Environment
Application Name: Statamic
Laravel Version: 12.21.0
PHP Version: 8.3.13
Composer Version: 2.8.4
Environment: local
Debug Mode: ENABLED
URL: testsystem-2025-08.test
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 0
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 5.63.0 PRO
Installation

Fresh statamic/statamic site via CLI

Additional details

No response

Dominant language
PHP
Stars
4.9k
Forks
647
Avg merge
1d 7h
Merged PRs (30d)
103

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from statamic/cms

All issues in statamic/cms

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.