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
ImageVariants have no asset collection assigned #3560
Comments
For a customer I solved this by using an aspect on A possible proper solution would be: When an |
Created a draft PR, so we can discuss this solution. Potential issue: When the original asset's asset collections are changed later, should that be kept in sync? |
ping… any opinions on the above question? |
I agree with the solution. And I also think that it makes sense to keep the collections in sync. Everything else would be error-prone. |
If the variants get collections assigned we should keep them in sync with the original asset, otherwise it gets really confusing. Seems we are avoiding to seperate the variants from the assets. However this would be more of a long term topic. |
Seems like this is still in issue in 7.3.10 |
Description
When an
ImageVariant
is created by means of cropping in the Neos UI inspector, it is not assigned to anAssetCollection
. This leads to issues if access to assets not being in an asset collection is limited.Steps to Reproduce
Expected behavior
The crop is created and assigned to the node property, becoming visible in the inspector (and the content, once applied.)
Actual behavior
The crop is in fact created, but since it is not accessible (due to step 1 above), it's metadata cannot be fetched (an error notice is shown) and the property will in fact be emptied.
Affected Versions
Neos: 5.3+
The text was updated successfully, but these errors were encountered: