In PHP, ZipArchive::addEmptyDir() helps with ZIP archives. Adds an explicit empty directory entry to a ZIP archive; it does not recursively copy a directory tree.
What Is ZipArchive::addEmptyDir() in PHP?
The function or method has a specific purpose: Adds an explicit empty directory entry to a ZIP archive; it does not recursively copy a directory tree. The following examples show the main call, one additional situation, and an application-style use.
Syntax:
<?php
ZipArchive::addEmptyDir(string $dirname, int $flags = 0): bool
Parameters and Return Value
$dirname— directory entry to create.$flags— flags controlling name encoding or lookup.
Example 1: Basic Usage
Adds an explicit empty directory entry to a ZIP archive; it does not recursively copy a directory tree.
<?php
$archivePath = sys_get_temp_dir() . "/example-guide.zip";
$archive = new ZipArchive();
if ($archive->open($archivePath, ZipArchive::CREATE) !== true) { throw new RuntimeException("Cannot open ZIP"); }
$result = $archive->addEmptyDir("reports/");
var_dump($result);
$archive->close();
This example demonstrates the central operation. The final output depends on the supplied input and, where relevant, the runtime or connected service.
Example 2: Handling a Different Case
<?php
$archivePath = sys_get_temp_dir() . "/second-guide.zip";
$archive = new ZipArchive();
if ($archive->open($archivePath, ZipArchive::CREATE) !== true) { throw new RuntimeException("Cannot open ZIP"); }
$result = $archive->addEmptyDir("reports/");
var_dump($result);
$archive->close();
The second example focuses on a different input or failure condition, so the behavior can be distinguished from the basic case.
Practical Example
<?php
$archivePath = sys_get_temp_dir() . "/practical-guide.zip";
$archive = new ZipArchive();
if ($archive->open($archivePath, ZipArchive::CREATE) !== true) { throw new RuntimeException("Cannot open ZIP"); }
$result = $archive->addEmptyDir("reports/");
var_dump($result);
$archive->close();
The practical example demonstrates how the same subject fits into a larger application. Use your own file paths, endpoints and validated inputs rather than copying sample settings directly.
Important Behavior and Edge Cases
- Adds an explicit empty directory entry to a ZIP archive; it does not recursively copy a directory tree.
- Check the return value and exceptions for failure before using the result. If an extension or external system is required, the example only works when that dependency is available. ZIP entries and uploaded files must never be treated as trusted merely because their extension looks correct.
- Close the ZIP archive to finalize changes; extraction requires checks against path traversal and oversized expanded content.
Comparison With Related Functions
| Approach | Difference |
|---|---|
| ZipArchive::addEmptyDir | Adds an explicit empty directory entry to a ZIP archive; it does not recursively copy a directory tree. |
| ZipArchive::open | Opens an archive and selects read or write mode before entry operations. |
Common Beginner Mistakes
| Mistake | Correct Approach |
|---|---|
| Forgetting to close an archive | Call close() and check its result so changes are committed. |
| Assuming archive entry names are safe to extract | Check extracted paths, entry counts and expanded file sizes. |
| Treating a ZIP password as automatic encryption | Choose entry encryption explicitly when writing encrypted archives. |
Key Takeaways
- Adds an explicit empty directory entry to a ZIP archive; it does not recursively copy a directory tree.
- Check the return value and exceptions for failure before using the result. If an extension or external system is required, the example only works when that dependency is available. ZIP entries and uploaded files must never be treated as trusted merely because their extension looks correct.
- Close the ZIP archive to finalize changes; extraction requires checks against path traversal and oversized expanded content.
Adds an explicit empty directory entry to a ZIP archive; it does not recursively copy a directory tree. Use this approach when its capabilities and constraints match the application. Handle invalid data, failure conditions and resource cleanup explicitly.