Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Setting per-Site Assets need to be clearer, in create dialog #1968

Closed
narration-sd opened this issue Sep 5, 2017 · 0 comments
Closed

Setting per-Site Assets need to be clearer, in create dialog #1968

narration-sd opened this issue Sep 5, 2017 · 0 comments
Labels
enhancement improvements to existing features

Comments

@narration-sd
Copy link
Contributor

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:

  • 'Options when Sites are used', instead of 'Advanced', on the dropdown at bottom
  • 'Allow using different Assets according to Site' instead of 'Manage relations on a per-site basis'
  • 'Use assets only from a single site' instead of 'Relate assets from a specific site'
    -- 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

  1. Create a new Asset field, regular or Matrix
  2. note no apparent means to choose Asset/s used by Site
  3. discover 'Advanced' dropdown, but 'relate' language is foggy, if probably you guess what to set?

Additional info

PHP version 7.1.4-1+deb.sury.orgxenial+1
Database driver & version MySQL 5.7.17-0ubuntu0.16.04.1
Image driver & version GD 7.1.4-1+deb.sury.org
xenial+1
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

@brandonkelly brandonkelly added the enhancement improvements to existing features label Sep 6, 2017
@craftcms craftcms deleted a comment from codyjames Apr 25, 2018
@craftcms craftcms deleted a comment from codyjames Apr 25, 2018
@craftcms craftcms locked and limited conversation to collaborators Jun 22, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement improvements to existing features
Projects
None yet
Development

No branches or pull requests

2 participants