Handling Multiple File Uploads in eForm for Evolution CMS

Single-file uploads are easy to support in legacy form workflows. Multiple files are where things get interesting. As soon as a field switches to name="file[]", the validation and processing logic has to understand an array of uploads instead of one file structure.

The original question was essentially this: if eForm already handles one uploaded file, what is the right way to adapt it for several files? The answer is to treat the upload field as a collection from the start and audit every custom hook that expects a scalar filename.

In practice that means:

• using array-style file input names;
• looping through the uploaded file set instead of reading one fixed index;
• keeping size, type, and error checks per file rather than once for the whole field.

This is one of those topics where old forum answers often stop at “yes, it is possible”. The more useful lesson is architectural: multiple-upload forms are not just a markup change, they are a different validation and processing shape.