Allow instances for asset fields

[foxtrotcz]

If possible asset fields should act the same as other fields and be reusable with instances.
Thanks.

[mini71]

Multi instance fields are extremly useful. Dear @brandonkelly , any chance that this will be possible for assets fields?

[brandonkelly]

It’s theoretically possible, but will take some effort, so didn’t make it into 5.0.

[mikesnoeren]

Not sure about the technical implications this would bring, but this feature would be very much appreciated! Currently it feels like the modular way of setting up the CMS only works for 70%, because of all the double relational fields.

In addition to that, would it be possible to have instanced fields bring their own settings? Kind of like how classes can extend eachother? That way we could alter field settings on instance level while creating entry types..

[brandonkelly]

@mikesnoeren That has been suggested before. See #8688 (comment)

[droemmelbert]

@brandonkelly I just want to emphasize that this feature request by @foxtrotcz is something I would also be very happy to see in the future!

[brandonkelly]

Coming in Craft 5.3 (#15400) 🎉

[brandonkelly]

Craft 5.3.0-beta.1 is out with support for multi-instance relational fields 🎉 (#15400)

We’re targeting August 6 for the GA release. If you’d like to test ahead of time, change your craftcms/cms requirement in composer.json to:

"craftcms/cms": "^5.3.0-beta.1",

and then run composer update.