This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Setting per-Site Assets need to be clearer, in create dialog #1968
Labels
enhancement
improvements to existing features
Description
Deciding how to make Asset definitions be per-Site is less than evident, as experience with early implementors of betta already shows. Could suggest changing th language as follows, on creating both stand-alone Asset and Matrix Asset fields:
-- the question that unrolls when you check this should also follow as 'Which site should Assets be used from?'
You can see my thought that the meaning of'relate' is vague for use, if not in database terms. The 'allow' hints that unless you actually save differing assets, the initial asset defined will be at first copied across -- trying not to think about trickiness on that point, and imagining Andris has.
The last option as I've made it really needs some further notes, that it has to do with Volumes defined according to Site; usually not the 'main' volume, but just for those images which need to differ. A complicated subject, so might deserve its own circle-question-mark Help link, would imagine. This could target a particular anchor in the doc, when the Assets field doc updates to Craft 3.
Steps to reproduce
Additional info
PHP version 7.1.4-1+deb.sury.org
xenial+1xenial+1Database driver & version MySQL 5.7.17-0ubuntu0.16.04.1
Image driver & version GD 7.1.4-1+deb.sury.org
Craft edition & version Craft Pro 3.0.0-beta.26 + dev-develop fdf21f6
Yii version 2.0.12
Twig version 2.3.2
Guzzle version 6.2.1
Imagine version 0.7-dev
Plugins
Doxter 3.1.4
Standards Agent 2.0.1
The text was updated successfully, but these errors were encountered: