Closed daun closed 1 month ago
Not a great solution, but it could work for you for now: Each container can have its own blueprint, so you could consider having a container just for your videos, and then in that blueprint you can put the video-specific fields.
@jasonvarga I've thought about that, but I prefer the user experience of having all media in a single asset container. But I can probably hide the video-specific options behind a Revealer. Or set a custom hidden is_video
field in the AssetCreated
event that I will have access to as it's part of the blueprint. So many options đŸ¤
It'd be great to get access to the underlying asset data in custom field conditions of asset blueprints. Currently, we only get access to the values of other fields in the same blueprint.
Example: only show an
autoplay
toggle in the asset blueprint if thepath
of the asset ends with.mp4
— this is currently not possible as the custom field conditions do not have access towidth
,height
,path
, etc.