Class 'App\Http\Controllers\Storage' not found

now it's returning 404

If you don't import your class at the beginning of the file and use it like this Storage::delete($team->logo); autoloader tries to find the class relatively to your current namespace. What is in your case App\Http\Controllers so autoloader look for class App\Http\Controllers\Storage . If you don't want autoloader look for class relatively to your current namespace you can add backslash in front of your class \Storage::delete($team->logo) or just import the class at the beginning of the file use Storage; and use it like you did. Checkout this link to learn more about namespaces PHP namespaces

i did try " use Storage " and it still returning 404 :(

with this?

$team=Team::findOrFail($id);
    \Storage::delete($team->logo);
    $team->delete();
    return response()->json(['data' => $team],200);

or app('filesystem')->delete($team->logo)

yes i tried that still the same issue and i ve allready run the cmd php artisan storage:link and nothing of these tries solved my issue

pls dd after each step

$team=Team::findOrFail($id);
dd('ok');    
\Storage::delete($team->logo);
    $team->delete();
    return response()->json(['data' => 'deleted'],200);

I think it can't find the team with that id . maybe you are trying to remove already removed team

The reason why you have 404 can be several.

1. Your destroy controller method "listen" for DELETE request but you do different type of request
2. You using findOrFail($id) method which gives you 404 when model with given ID is not in DB.

Try to do dd($id) at the very beginning of the destroy method so we can see if it even hits your method.

no i checked my data base and the team still exists

it returns the team s id

@sadok what do you have after this?

$team=Team::findOrFail($id);
dd($team);

  public function destroy($id)
  {
    dd($id);
    $team=Team::findOrFail($id);
    $team->delete();
    \Storage::delete($team->logo);
    return response()->json(['data' => $team],200);
  }

in postman i can see it returning the team id that i want to delete , but it doesn't get deleted

@rin4ik the problem is that Storage can't be found witch is not logic , that's so weird, it's driving me crazy

HTML forms cannot do DELETE request so you need to do form method spoofing manually. Postman can do DELETE.

<form action="YOUR_DELETE_ROUTE" method="POST">
    {{ method_field('DELETE') }}
    {{ csrf_field() }}
    <input type="submit">
</form>

Form Method Spoofing

Notice the {{ method_field('DELETE') }} what generates <input type="hidden" name="_method" value="DELETE"> and tells laravel that this is DELETE REQUEST even the method is set to POST.

This code is also in the wrong order...

$team=Team::findOrFail($id);
$team->delete();
\Storage::delete($team->logo);

You need to delete the $team->logo before you delete the $team. If you delete $team first, $team->logo doesn't exist any longer.

// import the storage facade
use Illuminate\Support\Facades\Storage;

public function destroy($id)
{    
    $team=Team::findOrFail($id);
    Storage::delete($team->logo);
    $team->delete();

    return response()->json(['data' => $team], 200);
}

I already gave you that answer https://laracasts.com/discuss/channels/laravel/class-apphttpcontrollersstorage-not-found/replies/428058

@rin4ik that's true , i didn't notice that you changed the order. thank you very much, and thanks for all members for helping me and giving me many new informations that i can use in the future.

@sadok you have to choose my answer as solution then!

Maybe if you took the time to actually explain it it would have been more obvious. He can choose whatever post helped him the most.

he wants to become a developer he should read and try to understand the code not the explanations! I've provided that code before you. maybe you just read my code and gave that answer I don't know.

Sometimes explanations just help; it's part of teaching which is what the forum is about. You answer your way, I'll answer mine, but you shouldn't be telling the OP what post he needs to choose as the answer lol. That's just lame.

GTH

Try using Storage at top of class and after clearing all cache update the composer and give permissions to write logs to storage folder

    <?php
        namespace App\Http\Controllers;

        use Illuminate\Http\Request;
        use Illuminate\Http\UploadedFile;
        use Storage;
        use App\User;
        use App\Team;
        use App\Club;

      class TeamController extends Controller
      {

          public function destroy($id)
          {
             $team=Team::findOrFail($id);
             $team->delete();
             Storage::delete($team->logo);
             return response()->json(['data' => $team],200);
         }
     }

   b).   php artisan cache:clear
   c).   composer update
   d).   sudo chmod -R 0777 storage/

Add this use Storage;

Great, Useful Info for us, Thanks https://www.southeastwholesalecars.com.au/