Restrict Asset Volumes on Per Site Basis
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
Similar to entries, it would be nice to define assets volumes on a per-site bases. Currently, volumes are shared across all sites and elements are propagated to all sites.
Another option would be to provide an event at Element::getSupportedSites method. One coupe prevent auto-propogation across all sites if they choose.
Additional info
- Craft version: 3.0.35
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.
Research direction
Start by reviewing the issue's existing multi-site behavior and the referenced Element::getSupportedSites method. Determine whether the intended change is per-site asset volumes or an event to prevent automatic propagation. Done should mean asset volumes and their elements can be restricted to selected sites without affecting other sites.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100