FuelPHP Forums

Yay, thank you! Really appreciate it!

As the property name indicates, it contains the name of the controller (as in the class name). It includes the namespace, because you need that to uniquely identify the controller. \Controller_Name is different from \Module\Controller_Name. For the same reason, the action property contains the name of the action called (without the 'action_' prefix), and the method property contains the complete method name, with the 'action_' prefix. If you need a URI segment, use the uri property (which is an instance of the URI class) of the Request object, and the segment methods it provides.

Except that it's used in request class to call the action from that controller which is internal fuelphp problem?

Actually the primary reason for the existance of the properties is internal, that they're also available is secundairy.

So why we need full namespaced class name in Request::active()->controller property?

Because that's the controller, it's not called "controller_segment" it's called controller. And why "we" need it? Because that's where the Request::execute() method takes its cues from. I'll repeat: that's the primary reason for the existance of these properties - that they're available t you is still secundairy.

You have the controller name available. \Namespace\Controller_Name IS the controller name. What you want is the URI segment. You get that using \Request::active()->uri->segments(). If you want to extract the 'Name' part of the controller name, use

echo substr(\Inflector::denamespace(\Request::active()->controller), 11);

I wasn't being sarcastic, I may have doubled down a bit but how the framework works is important. But also one thing you seem to miss is that segments don't necessarily match the module/controller/action, when using routing it may get to a whole different point than originally requested. This is why module = module dirname, controller = controller classname and action = method name (though without the action_ prefix as that may not be used when a Controller::router() method is present).
These are a technical description of the Request, not of the URI. And that's why they don't match those.