Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow choosing from multiple asset containers in asset fields #298

Closed
fitzage opened this issue Sep 2, 2020 · 2 comments
Closed

Allow choosing from multiple asset containers in asset fields #298

fitzage opened this issue Sep 2, 2020 · 2 comments

Comments

@fitzage
Copy link

fitzage commented Sep 2, 2020

In v2, I could set an asset container for a field, but then allow choosing a different asset container instead, which is not possible in v3. There are some reasons why I would like to see this added back in:

  • I would like specific fields to use a specific asset container, but then be able to have a field elsewhere that is able to choose from various asset containers so I don’t have to duplicate the image.
  • These asset containers might have different blueprints for their images, which is why just using multiple folders in one asset field doesn’t necessarily solve the problem.
  • I could convert my half dozen asset containers from V2 into folders in one asset container, but that means a LOT of work, particularly to update all existing asset fields.
@jasonvarga
Copy link
Member

With the way asset containers work in v3, I don't think this will ever happen. Not natively anyway. Maybe you could make a custom fieldtype.

@Swennet
Copy link

Swennet commented Oct 19, 2023

@jasonvarga Having this feature would solve a particular use case for us:

We would like to have a "shared" asset container linked to a filesystem outside of our project root that multiple Statamic websites can use. We would then attach two asset containers "Assets" and "Shared Assets" to our Asset fields.

We considered using a symlinked directory in our storage folder for this, but it seems like Flysystem doesn't support this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants