Laravel中File::delete无法删除文件的问题排查

Hey there! Let's work through why your file deletion isn't going through—this is a super common snag, and we can break down the possible fixes step by step.

1. The Most Likely Culprit: Incorrect File Path #

First off: you’re probably using the wrong path when calling File::delete(). Remember, File::delete() expects an absolute server path, not just the relative path from your storage config.

For example, if you’re trying this:

File::delete('logo/' . $request->input('old_logo'));

That won’t work—it’s looking for the file in your project root, not the actual storage/app/public/logo/ directory.

Instead, use storage_path() to build the full absolute path:

use Illuminate\Support\Facades\File;

$oldLogoPath = storage_path('app/public/logo/' . $request->input('old_logo'));
File::delete($oldLogoPath);

Or even better—use Laravel’s Storage facade, which automatically respects your filesystems.php config (this is the recommended approach):

use Illuminate\Support\Facades\Storage;

Storage::disk('public')->delete('logo/' . $request->input('old_logo'));

This method leverages your configured disk paths, so you don’t have to hardcode anything and avoid path-related mistakes.

2. Confirm the File Actually Exists #

Sometimes the filename is correct, but the file is already gone, or there’s a case-sensitive typo (critical on Linux servers!). Add a quick check to rule this out:

$oldLogoPath = storage_path('app/public/logo/' . $request->input('old_logo'));

if (File::exists($oldLogoPath)) {
    File::delete($oldLogoPath);
} else {
    // Log or debug this to confirm the file is missing
    Log::warning('Old logo file not found: ' . $oldLogoPath);
}

3. Permissions Could Be Blocking Deletion #

Yes, permissions might be the issue. Your web server user (usually www-data for Apache, nginx for Nginx) needs write/delete access to the storage/app/public/logo/ directory.

To fix this:

• Check current permissions with:

  ls -l storage/app/public/
  

• Adjust ownership to match your web server user:

  chown -R www-data:www-data storage/
  

• Set proper directory permissions:

  chmod -R 755 storage/
  

4. Verify Your Filesystems Config #

Double-check your config/filesystems.php to make sure the public disk is pointing to the correct root directory:

'public' => [
    'driver' => 'local',
    'root' => storage_path('app/public'),
    'url' => env('APP_URL').'/storage',
    'visibility' => 'public',
],

If the root path is incorrect, even the Storage facade will fail to locate the file.

Start with the path check first—it’s the most frequent fix. If that doesn’t work, move on to verifying the file exists and checking permissions.

内容的提问来源于stack exchange，提问作者Tomas