Hi,
I have been looking at http://matrix.squiz.net/developer/technical-docs/screens/3 and wondering if there is a field for file uploads. I am making an update to one of our custom templates.
George
Matrix fields
There is no field as file uploads need to be stored somewhere, normally as assets linked to the main custom asset, although you can upload them into the data directory.
There are file upload widgets to help you paint and process file upload boxes. I suggest looking at the File asset itself and see how it does it. It stores the file in the data directory.
Rendering and handling of a file upload box is added through HTML only - there is not an attribute equivalent.
The code for this would need to reside in your [asset_type_code]_edit_fns.inc file.
However the most common way of using files in Matrix is to refer to an existing File asset by using the asset_picker attribute.
This is the most flexible way as the file can be moved within the system without affecting the link between your custom asset and the file.
Edit: Beaten to the post
Thanks. I will look into your suggestions.
At the moment we are using the file picker, but we would like to make the process a bit shorter, so that users can add their information as well as upload the file in one go, rather than upload, locate the file and then link it to the asset.
If streamlining the process is a priority, talk to your Squiz rep about custom asset development.
Recently for our clients, Squiz has created custom user assets to tailored requirements. For example, a user asset that needs to provide additional documentation to support their account can have a pdf file required upon creation, with an associated expiry date property for each supporting document. This can be used for security clearance or other purposes.
As you can imagine, having custom assets has benefits such as being able to discern between asset types for listings etc, and tight integration between core asset properties.
[quote]If streamlining the process is a priority, talk to your Squiz rep about custom asset development.
Recently for our clients, Squiz has created custom user assets to tailored requirements. For example, a user asset that needs to provide additional documentation to support their account can have a pdf file required upon creation, with an associated expiry date property for each supporting document. This can be used for security clearance or other purposes.
As you can imagine, having custom assets has benefits such as being able to discern between asset types for listings etc, and tight integration between core asset properties.[/quote]
Thanks Adam.