Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
renders a field for uploading files into a Magnolia workspace. This field is used by the Assets app for uploading assets into the dam workspace. It extends the basic upload field field and adds the following enhancements to the completed view:
class: info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinition
Here's the completed view for an uploaded image.
Here's the completed view for an uploaded video.
Simple DAM upload field configuration:
form: tabs: - name: tabUpload label: Upload fields: - name: upload class: info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinition label: Upload asset binaryNodeName: jcr:content editFileName: true
Node name | Value |
---|---|
form | |
tabs | |
tabUpload | |
fields | |
upload | |
binaryNodeName | jcr:content |
class | info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinition |
label | Upload asset |
editFileName | true |
You can use common field properties and the properties in the tables below in a basic upload field definition:
<field name> | required Name of the field. |
| optional, default is Regular expression to filter allowed files by their MIME type. For example, to allow only Excel files set the value to |
| optional, default is Name of the subnode that will contain the file binary and related information. |
| optional, default is When set to |
| optional, default is When set to |
| optional, default is Maximum file size in bytes. |
Caption properties. Values are typically retrieved from a message bundle.
<field name> | required Name of the field |
Empty view | |
| optional, default is Text displayed as tooltip on the upload button. |
| optional, default is Text displayed as label for dropping invitation. |
| optional, default is You have aborted the upload of your file Text displayed in the warning note. |
In progress view | |
| optional, default is Text displayed as title. |
| optional, default is Text displayed as file upload ratio. |
Completed view | |
| optional, default is Text displayed as file detail header. |
| optional, default is Text displayed as file name label. |
| optional, default is Text displayed as file size label. |
| optional, default is Text displayed as file format label. |
| optional, default is Text displayed as file source label. |
| optional, default is Text displayed as tooltip on the delete icon. |
| optional, default is Text displayed on the upload button. |
| optional, default is Text displayed in the success note. |
| optional, default is Text displayed in the error note. |
| optional, default is Text displayed in the warning when file size > |
| optional, default is Text displayed in the warning when file type not in |
| optional, default is Text displayed in the warning when the user interrupts the upload. |
Caption properties specific to the DAM upload field.
<field name> | required Name of the field |
| optional, default is Text displayed as tooltip when you hover over the preview action icon. |
| optional, default is Text displayed as tooltip when you hover over the edit action icon. |
When using the basic upload field in a composite field use the DelegatingCompositeFieldTransformer. The other transformer classes do not work.
It's possible to configure the in dialogs or other apps, but keep in mind the file will placed into the workspace for which the field has been configured. For example, if you use the field in a dialog for a component template, then that file, when uploaded using the field, would be stored in the website workspace not the dam workspace. This is the same behavior as all other fields. It's best practice, whenever possible, to keep your assets in the DAM and link to them using a link field.
3 Comments
Dương Hoàng Giang
How i can upload my file from the website into Magnolia CMS JCR workspace ?Can you show me the way to do that with Java
Christoph Meier
This field is meant to use within a form for instance within a dialog. To make this happen, a bunch of Java classes is involved
. To store a file - just use Assets app. Or create a dialog to store the file as asset on the
dam
workspace or as binary file on a workspace of your choice.Who should be able to store files? Magnolia editors, authors, visitors, public users?
Once again - dear Dương Hoàng Giang - you should describe your use case much more precise.
Dương Hoàng Giang
Thanks for your advice. In my case I want to public user can upload file (.doc, .pdf,..) in public instance and authors can manage it in Magnolia CMS how i can do that ? Do you understand me ?