ZIP and deletion

Download multiple files as ZIP

PHP ext-zip must be installed and enabled.

Use the safe generated download name:

return FileMagic::find([
    $firstId,
    $secondUuid,
    $fileModel,
])->downloadZip();

Choose the ZIP download name:

return FileMagic::find($targets)->downloadZip('project-documents');

Both project-documents and project-documents.zip produce project-documents.zip. Archive entries use each file's original name. Duplicate names become report (2).pdf, report (3).pdf, and so on, while preserving query order.

ZIP creation is streamed through bounded local temporary files instead of loading every source into memory. The temporary archive is deleted after the response is sent. zip.max_files and zip.max_size limit each operation; zip.max_size measures the uncompressed source bytes.

An empty result or any missing physical file fails the complete operation. FileMagic does not silently return a partial archive. downloadZip() creates only a temporary HTTP download and does not create another StoredFile record.

Delete

Single file:

$deleted = FileMagic::find($target)->delete();

Batch deletion:

$deleted = FileMagic::find($targets)->delete();

Batch deletion groups physical paths by disk. The normal path performs one bulk storage delete per disk and one database delete. If an adapter returns false or throws, FileMagic checks only that disk's paths individually: records are removed only for objects confirmed missing, while records for existing or unverifiable objects remain available for retry.

If only part of the operation completes, FileMagic first persists the confirmed state and then throws PartialFileDeletion. Use deletedCount(), failedCount(), and failedKeys() to report the result. You may safely retry the original FileMagic::find($targets)->delete(); already missing objects are treated as deleted.

Storage and the database do not share an ACID transaction, so deletion cannot be globally atomic. Batch deletion intentionally does not create backups.