Hi!
If I understand correctly:
- modules are application specific routable functional extensions of the core
- packages are non-application specific non-routable functional extensions of the core
I am building a library that needs its own interface (for ajax validation calls) but is not application specific. Up until now, I was trying to build a package, but I am having problems routing ajax requests to a controller in my package.
In this thread Jelmer Schreuder says it shouldn't be done: http://fuelphp.com/forums/topics/view/387
Am I missing something, should I use a module instead (even if it is application agnostic)?
Can it still be done with package? I have tried creating a controller in package but I always get 404. How can do it?
The idea is that a package is a core extension.
As you don't route to core controllers, you also don't route to package controllers.
Instead, you create a controller in your application that extends your package controller (like you would extend the core controllers Controller_Template or Controller_Rest). If that controller happens to have 100% of all functionality, you don't have to do more.
Donate
