You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Asset link type would greatly benefit from having a default upload location. Currently when adding an asset the users are shown the root of the selected volume, but in our experience authors never create the right folder structure to cleanly order their assets, and shove everything at the root.
Our data models often require one document belonging to one entry, and we'd like the folder path to reflect that.
What's your proposed solution?
In the Asset link settings, there could be a Default Upload Location field, which could include variables like {slug}, and the option to upload directly to the field. Similarly to Craft, users would be a offered to Add an assset or Upload or file.
Alternatively, perhaps we could have the ability to select a custom native Assets field in place of the default field.
Additional context
No response
The text was updated successfully, but these errors were encountered:
What are you trying to do?
The Asset link type would greatly benefit from having a default upload location. Currently when adding an asset the users are shown the root of the selected volume, but in our experience authors never create the right folder structure to cleanly order their assets, and shove everything at the root.
Our data models often require one document belonging to one entry, and we'd like the folder path to reflect that.
What's your proposed solution?
In the Asset link settings, there could be a Default Upload Location field, which could include variables like
{slug}
, and the option to upload directly to the field. Similarly to Craft, users would be a offered to Add an assset or Upload or file.Alternatively, perhaps we could have the ability to select a custom native Assets field in place of the default field.
Additional context
No response
The text was updated successfully, but these errors were encountered: