Laravel and using namespaces - Class not found

Question

I have created a php file under the Models folder provided by Laravel.

Inside I have:

// Filename: Models/Shoopy.php
namespace Whatever\Something;

class Shoopy
{
    public function Toot(){};
}

Now in another Model file I am using that namespace:

use \Whatever\Something\Shoopy;

class AnotherModel
{
    public function Spop()
    {
        $harr = new Shoopy();
    }
}

It comes up with a Laravel error:

class Whatever\Something\Shoopy not found

Any ideas?

Simon · Accepted Answer · 2016-08-20 20:33:14Z

2

I know this is an older issue, but if you go into your composer.json file, you'll probably see something like...

"autoload": {
    "classmap": [
        "database"
    ],
    "psr-4": {
        "App\\": "app/"
    }
},

What you can do is tell composer where Whatever should be, say if it was a different location (or sub-folder) from where Laravel normally keeps it's files.

"autoload": {
    "classmap": [
        "database"
    ],
    "psr-4": {
        "App\\": "app/",
        "Whatever\\": "app/Whatever",
    }
},

answered Aug 20, 2016 at 20:33

Simon

1311 gold badge1 silver badge10 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Jeff Lambert · Accepted Answer · 2014-08-26 14:32:48Z

1

Classes need to exist in files with directory paths that match their namespace. This is according to the PSR-0 Standard. In your example, try placing your Shoopy class in the file:

app/models/Whatever/Something/Shoopy.php

And then see if the autoloader can find it.

answered Aug 26, 2014 at 14:32

Jeff Lambert

24.7k4 gold badges72 silver badges98 bronze badges

5 Comments

Jimmyt1988 Over a year ago

oh... That's a bit annoying.

Jeff Lambert Over a year ago

It may be, but it was even more annoying back when there was absolutely no structure or standards whatsoever. You can always remove the namespace and leave the model where it is.

Jimmyt1988 Over a year ago

The problem is, the real Model name is Pagination, so it's likely there will be many plugins called Pagination, so just wanted to stamp a namespace on it... Oh well, looks like I should put it into composer in that case, then I can do it as I wanted

Jeff Lambert Over a year ago

If the class doesn't extend Eloquent, then it most likely doesn't really belong in the models folder. I generally add a directory underneath app/ for all of my 'helper' or service classes, and use that as a base namespace (you'd need to update your composer.json in order to get the autoloader to find that namespace)

Jimmyt1988 Over a year ago

I generally put all classes under the Models folder into separate folders, Abstract, Concrete, Objects, Eloquent, Helpers and auto load them in the config file... Thanks for the recommendation though. I use Models as the generic term for anything that is not a Controller or View

Collectives™ on Stack Overflow

Laravel and using namespaces - Class not found

2 Answers 2

Comments

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related