The component is designed to attach files to the order miniShop2, both from the back-end, and from the front-end.
In the back end, files are displayed on the tab built into the edit box of the miniShop2 order.

As you know, after placing an order by an anonymous user, the user is created at the specified email when ordering. So this user is attached to the files that were downloaded when placing an order.

Creating the file download form
It's best to place the snippet in chunk tpl.msOrder so that the form is not displayed in the empty basket.

MsofForm snippet options:

• tpl — Template call form,
• order — Order ID. By default, 0,
• user — User ID. By default the current one,
• source — The source of the files. By default, it is specified from the msof_source setting,
• anonym — Allow anonymous users to use the form,
• dropzone — An array Dropzone parameters, you can JSON,
• maxFiles — Maximum number of files. By default 2,
• maxFilesize — The maximum file size in MB. Default is 2.

Example of a call:

{'!msofForm' | snippet : [
    'maxFiles' => 20,
    'maxFilesize' => 10,
    'anonym' => false,
]}

Important

To allow the user to download files from the front end, add the msOrderFilesPolicy access policy to the group. The same applies to the anonymous authors.

Creating files in a letter to the user / manager
In the right place of the letter template, we write a pdoResources snippet call with our msOrderFiles model:

{'!pdoResources' | snippet : [
    'class' => 'msOrderFile',
    'loadModels' => 'msOrderFiles',
    'where' => [
        'order_id' => $order['id'],
        'active' => 1,
    ],
    'sortby' => '{"rank":"ASC"}',
    'tplWrapper' => '@INLINE <ul>{$output}</ul>',
    'tpl' => '@INLINE <li><a href="{("site_url" | option) ~ $url}">{$name}</a></li>',
]}

It is important to consider that this solution is 100% working for miniShop2 >= 2.4, because was checked only on it. Although you can try to combine with earlier versions of the store, most likely, even without significant edits.

List of order files
To display the list of files of a specific order (for example, in the user's personal cabinet), you need to use the pdoResources snippet:

{'!pdoResources' | snippet : [
    'class' => 'msOrderFile',
    'loadModels' => 'msOrderFiles',
    'where' => [
        'active' => 1,
        'order_id' => 10,
    ],
    'sortby' => '{"rank":"ASC"}',
    'tplWrapper' => '@INLINE <ul>{$output}</ul>',
    'tpl' => '@INLINE
        <li><a href="{$url}">{$name}</a></li>
    ',
]}

Placeholders for the parameter tpl

• id — id of the order file,
• order_id — order id in ms2,
• source — id of the source of files,
• name — the name of the file,
• description — description of the file,
• file — the name of the file with the extension,
• url — the path to the file, starting from the root of the site,
• mime — the file type, according to the MIME standard,
• ext — file extension,
• hash — hash, which is used to compare the uniqueness of the downloaded file,
• size — the size of the file in bytes,
• createdon — the date the file was downloaded,
• createdby — the id of the user who uploaded the file,
• rank — the position number of the file in the list,
• active — whether the file is active.

MsOrderFiles source file

In the source file, in addition to the standard settings (basePath, baseUrl), you can specify:

• allowedFileTypes — a list of file extras that can be downloaded,
• fileNameType — familiar to many of ms2Gallery, means the method of renaming a file,
• positionNewFiles — position of new files in the list. In other words, where to upload new files: to the beginning or to the end.

The author thanks Mikhail Voevodsky for the idea of the extra.
Thread in MODX.PRO community.