Deleting files in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when you delete a file using Laravel's Storage facade?

Consider this Laravel code snippet:

use Illuminate\Support\Facades\Storage;

Storage::delete('documents/report.pdf');

What is the result of running this code if the file exists?

Laravel

use Illuminate\Support\Facades\Storage;

Storage::delete('documents/report.pdf');

A The file 'documents/report.pdf' is removed from the storage disk and returns true.

B The file is moved to a trash folder for recovery later.

C The file remains unchanged and the method returns false.

D An exception is thrown if the file exists.

💡 Hint

Think about what the Storage facade's delete method does when the file exists.

Laravel's Storage::delete method removes the specified file from the disk and returns true if successful. It does not move files to trash or throw exceptions if the file exists.

📝 Syntax

intermediate

Which Laravel code correctly deletes multiple files at once?

You want to delete these files: 'a.txt', 'b.txt', and 'c.txt' from storage. Which code snippet does this correctly?

A Storage::deleteAll(['a.txt', 'b.txt', 'c.txt']);

B Storage::delete('a.txt', 'b.txt', 'c.txt');

C Storage::delete(['a.txt', 'b.txt', 'c.txt']);

D Storage::delete(['a.txt' => true, 'b.txt' => true, 'c.txt' => true]);

💡 Hint

Check the method signature for deleting multiple files in Laravel Storage.

Storage::delete accepts an array of file paths to delete multiple files at once. Passing multiple string arguments or associative arrays is invalid.

🔧 Debug

advanced

Why does this Laravel code fail to delete the file?

Look at this code:

use Illuminate\Support\Facades\Storage;

$file = 'uploads/image.png';
Storage::delete($file);

The file exists but is not deleted. What is the most likely cause?

Laravel

use Illuminate\Support\Facades\Storage;

$file = 'uploads/image.png';
Storage::delete($file);

A The default storage disk is not set to the disk where the file exists.

B The file path is missing a leading slash.

C Storage::delete requires the full URL, not relative path.

D The file is locked by another process and cannot be deleted.

💡 Hint

Think about where Laravel looks for files when deleting.

Storage::delete deletes files from the default disk configured in filesystems.php. If the file is on another disk, you must specify it. A missing leading slash or URL instead of path is not the issue.

❓ state_output

advanced

What is the return value of Storage::delete when deleting multiple files?

Given this code:

use Illuminate\Support\Facades\Storage;

$result = Storage::delete(['file1.txt', 'file2.txt', 'file3.txt']);

Assuming 'file1.txt' and 'file3.txt' exist and are deleted, but 'file2.txt' does not exist, what is the value of $result?

Laravel

use Illuminate\Support\Facades\Storage;

$result = Storage::delete(['file1.txt', 'file2.txt', 'file3.txt']);

A The number of files successfully deleted

B false

C An array of booleans indicating each file's deletion success

D true

💡 Hint

Check Laravel's documentation on Storage::delete return values.

Storage::delete returns true if all files were deleted or did not exist. It returns false only if any file could not be deleted due to an error.

🧠 Conceptual

expert

Which Laravel method should you use to delete a file and handle failure gracefully?

You want to delete a file and log a message if deletion fails without throwing an exception. Which approach is best?

A Use Storage::deleteOrFail which throws exceptions on failure.

B Use Storage::delete and check its boolean return value to log failure.

C Use unlink() PHP function directly and catch exceptions.

D Use Storage::remove which returns detailed error messages.

💡 Hint

Consider Laravel's Storage methods and their behavior on failure.

Storage::delete returns true or false without throwing exceptions, allowing you to handle failure gracefully. unlink() is a PHP function but does not integrate with Laravel's storage disks. deleteOrFail throws exceptions. Storage::remove does not exist.

Practice

1. Which Laravel method is used to delete a file from storage?

easy

A. Storage::delete()

B. Storage::remove()

C. Storage::destroy()

D. Storage::unlink()

Solution

1. Step 1: Identify the Laravel file deletion method

   Laravel uses the Storage facade to manage files, and the method to delete files is delete().

2. Step 2: Confirm the correct method name

   Other methods like remove(), destroy(), and unlink() do not exist in Laravel's Storage facade.

3. Final Answer:

   Storage::delete() -> Option A

4. Quick Check:

   File deletion method = Storage::delete() [OK]

Hint: Remember: Laravel uses Storage::delete() to remove files [OK]

Common Mistakes:

• Confusing delete() with remove()
• Using unlink() which is a PHP function, not Laravel method
• Trying to use destroy() which is for models, not files

2. Which of the following is the correct syntax to delete a single file named 'example.txt' in Laravel?

easy

A. Storage::remove('example.txt');

B. Storage::delete(['example.txt']);

C. Storage::delete('example.txt');

D. Storage::deleteFile('example.txt');

Solution

1. Step 1: Understand the method parameter for single file deletion

   To delete a single file, pass the file path as a string to Storage::delete().

2. Step 2: Check the syntax correctness

   Storage::delete('example.txt'); correctly uses a string argument. Storage::delete(['example.txt']); uses an array which is valid but for multiple files. Options C and D use invalid method names.

3. Final Answer:

   Storage::delete('example.txt'); -> Option C

4. Quick Check:

   Single file delete uses string argument [OK]

Hint: Use a string for one file, array for many in Storage::delete() [OK]

Common Mistakes:

• Passing an array when deleting a single file
• Using non-existent methods like remove() or deleteFile()
• Forgetting the semicolon at the end

3. What will be the result of this Laravel code snippet?

use Illuminate\Support\Facades\Storage;

$result = Storage::delete(['file1.txt', 'file2.txt']);
var_dump($result);

medium

A. Always returns false

B. true if all files deleted, false otherwise

C. Throws an error because array is not allowed

D. An array of booleans for each file deletion

Solution

1. Step 1: Understand Storage::delete() with array input

   When passing an array of file paths, Storage::delete() attempts to delete all files and returns true only if all deletions succeed.

2. Step 2: Analyze the return value

   The method returns a boolean, not an array. It returns false if any file fails to delete.

3. Final Answer:

   true if all files deleted, false otherwise -> Option B

4. Quick Check:

   Storage::delete(array) returns boolean [OK]

Hint: Storage::delete(array) returns true only if all files deleted [OK]

Common Mistakes:

• Expecting an array of booleans as return
• Thinking array input causes error
• Assuming it always returns false

4. Identify the error in this Laravel code snippet for deleting a file:

use Illuminate\Support\Facades\Storage;

if (Storage::exists('oldfile.txt')) {
    Storage::delete('oldfile.txt');
} else {
    echo 'File does not exist';
}

medium

A. Storage::delete() requires array, not string

B. Missing import of Storage facade

C. Storage::exists() does not exist

D. No error; code works correctly

Solution

1. Step 1: Check if Storage facade is imported

   The code imports Storage correctly with use Illuminate\Support\Facades\Storage;.

2. Step 2: Verify method usage

   Storage::exists() checks if file exists, and Storage::delete() accepts a string for single file deletion. The conditional prevents errors if file is missing.

3. Final Answer:

   No error; code works correctly -> Option D

4. Quick Check:

   Check existence before delete is correct pattern [OK]

Hint: Check file exists before delete to avoid errors [OK]

Common Mistakes:

• Forgetting to import Storage facade
• Assuming delete() needs array always
• Using non-existent methods

5. You want to delete multiple files but only if they exist to avoid errors. Which Laravel code snippet correctly deletes 'a.txt', 'b.txt', and 'c.txt' safely?

hard

A. foreach (['a.txt', 'b.txt', 'c.txt'] as $file) {
if (Storage::exists($file)) {
Storage::delete($file);
}
}

B. Storage::delete(['a.txt', 'b.txt', 'c.txt']);

C. foreach (['a.txt', 'b.txt', 'c.txt'] as $file) {
Storage::delete($file);
}

D. Storage::delete('a.txt', 'b.txt', 'c.txt');

Solution

1. Step 1: Understand safe deletion of multiple files

   To avoid errors, check if each file exists before deleting it.

2. Step 2: Analyze each option

   foreach (['a.txt', 'b.txt', 'c.txt'] as $file) { Storage::delete($file); } deletes without checking existence, risking errors. Storage::delete(['a.txt', 'b.txt', 'c.txt']); deletes all at once but may fail if some files don't exist. foreach (['a.txt', 'b.txt', 'c.txt'] as $file) { if (Storage::exists($file)) { Storage::delete($file); } } checks existence before deleting each file, preventing errors. Storage::delete('a.txt', 'b.txt', 'c.txt'); uses invalid syntax.

3. Final Answer:

   foreach (['a.txt', 'b.txt', 'c.txt'] as $file) { if (Storage::exists($file)) { Storage::delete($file); } } -> Option A

4. Quick Check:

   Check existence before delete in loop for safety [OK]

Hint: Check each file exists before deleting in a loop [OK]

Common Mistakes:

• Deleting files without existence check
• Passing multiple strings instead of array
• Using invalid method signatures