I apologize if this has been answered elsewhere, but I've looked through the documentation and forums and I can't seem to figure this out.
I would like to namespace the classes in my FuelPHP app, using a namespace similar to MyApp\Core. Am I required to make two new directories in APPPATH/classes just to do this?
For example, if I wanted to create a class called MyClass in MyApp\Core, do I HAVE to put myclass.php in APPPATH/classes/myapp/core/myclass.php?
The MyApp\Core namespace seems to work fine for controllers and models. I have MyApp\Core\Model_Item in APPPATH/classes/model and it loads and runs just fine when called from a controller using the MyApp\Core namespace and stored in APPPATH/classes/controller. However, when I try to call MyApp\Core\MyClass, I get the error that the class MyApp\Core\MyClass cannot be found. Oddly enough, it says that the error occurred on the last line of APPPATH/classes/myclass.php.
All files that I want in my namespace have the namespace MyApp\Core; line at the top. I even tried adding
to my application bootstrap, but to no effect. I also tried adding an Autoloader::add_class() call for the MyClass class, but it didn't work.
Am I missing something, or is it just not possible to use namespaces for classes in APPPATH/classes? If it's not possible, why not?
UPDATE: Now I'm even more confused. I've tried putting MyClass into the global namespace and the same thing happens. Class not found error on the last line of myclass.php.
I'm starting to think this might have something to do with my class so here it is. I'm trying to extend FuelPHP's logging to log to a database as well.
I'm having more or less the same problems with namespaces as you. I cant get it to work.
I think the docs do not include this info as it should to be clear. My problem is with a PSR-0 compliant library that I dont know how to add. I manage to add it as add_classes but not the namespaces.
I hope someone else throws some light over this topic coz I'm nearly the full desperation.
Have you tried to create a package instead of putting that in your application?
As Harro says me some months ago:
A module can be seen as a reusable application component, a package can be seen as a reusable core/framework component. The first provides frontend functionality, the second backend.
If you want to create a package this is how:
Create a folde under "packages" folder. I'll use "mypackage"
The Autoloader supports PSR-0 compliant libraries. In the bootstrap, in the add_namespace() call, add 'true' as third parameter to indicate it's a PSR-0 namespace, and your classes will load fine.
Technically you can do this in app too, but it will be messy. A package is a lot cleaner.
After several more hours of trying various things, including ilNotturno/Harro's suggestion of putting the class in a package, I still couldn't get it to work.
Finally made a test class that just echoed out some text, and it worked fine. Turns out, either PHP or Fuel doesn't like it when you extend a class in a different namespace. Taking out extends Fuel\Core\Log gets rid of the error and the class works (after switching parent calls to Fuel\Log). Given a stackoverflow question asking about extending across namespaces, I'm thinking it's FuelPHP. Thoughts?
Out of curiosity, is it bad FuelPHP practice to use namespaced classes in my app?
"Technically you can do this in app too, but it will be messy. A package is a lot cleaner."
Were you just talking about Composer and other external packages? Because it seems kind of silly to create a package for a few classes that are part of my app.
Extending across namespaces isn't a problem at all, I do it all the time. So it must be related to what you do and how you do it.
There is no real practice, using packages and modules makes stuff more reusable, but if you want them in your app/classes folder, no problem. That's entirely up to you, and Fuel's flexibility lets you do that.
Donate
