FuelPHP Forums

Request::active()->module;
Request::active()->controller;
Request::active()->action; The construction of the ACL is entirely up to you, I for one use functional roles, which are not linked to fysical pieces of code. You pass the data to check yourself, you have to think of how you are going to code module names into it. In FuelPHP, we commonly use the notation "module::controller", maybe you could use that?

As the name says, it returns the controller name. Which is a class name. There is no direct mapping from the URI to a controller name. It might be the case if you're not routing and don't use folders or namespaces in your app, but there isn't in all other cases. FuelPHP allows you to map a URI like /this/that/theother/here to a controller called "theother" in the namespace "\This\That". Or use "\Controller\Name" (class Name in the namespace Controller) instead of class Controller_Name. If you want segments, use Request::active()->uri->segment() or Request::active()->uri->segments(). This question has been answered several times. When it comes to ACL's, you should not use the segment, as it is not unique. If you want a unique mapping, you need both the namespace and the class name mapped. Besides this, your ACL's are going to get very complex if you use this system, and your application grows both in terms of code and user groups or roles. Define your roles, map roles to functional names, and names to rights. Like in the example:

* Regular example with role "user" given create & read rights on "comments":
*   'user'  => array('comments' => array('create', 'read')),

then you check in your code if the user has 'create' rights on the function 'comments'. It will make it very clear, both in the ACL definitions and in your code, what is meant by this.

That's why I wrote that you should not rely on it. And you should not do that either on a controller name. What will happen if you protect or give access to your controller hardcoded, and I do this:

class Controller_Blog2 extends Controller_Blog {}

If I call this one, all of a sudden your ACL system doesn't work anymore, because your ACL's are handcoded on the controller name 'blog'. Now, if you follow my suggestion and go the functional route, you will check if the user has_access() to 'blog.read' (is allowed to read blogs). No matter what I do, the code is only executed if the user has that right. Also, a lot of people mis-use the before() method to add these checks. So then I do

class Controller_Blog2
{
    public function action_index()
    {
        // this will bypass your has_access() check in the before() method
        $controller = new Controller_Blog($request, $response);
        return $controller->action_yours();
    }
}

And again your access system is useless...