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

Confusing note about picture usage in elements#zoom when element is trashed #1026

Closed
rbjoern84 opened this issue May 25, 2016 · 2 comments
Closed

Comments

@rbjoern84
Copy link

rbjoern84 commented May 25, 2016

Problem

When you go to pictures#zoom and look at the elements the picture is assigned in you will see no difference between available elements and trashed elements. The screenshot shows a trashed element:

bildschirmfoto 2016-05-25 um 13 00 52

This is confusing because when you click on a link of a trashed element you will be redirected to the page the element was rendered on but the element can not be found on the page because its in the trash. The problem is the user won't think of the trash. This gets annoying if you want to delete the picture in the library and you are looking for its element.

Expectation

  1. In pictures#zoom you would want to see a note on the trashed element (where the picture is assigned in) that it is actually trashed.
  2. When you click the link to the (trashed) element you should be redirected to the page but you should see the trash modal open with the highlighted element inside.
@tvdeyen
Copy link
Member

tvdeyen commented May 25, 2016

  1. Easy
  2. Extremely complicated

What about:

Only not trashed elements count as assignments? And pictures should be deletable if assigned to trashed elements.

@rbjoern84
Copy link
Author

If someone moves the trashed element back to the page the picture is not there anymore. In this case moving it back from the trash does not really make sense anymore.

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

2 participants