FuelPHP Forums

FuelPHP uses a mechanism called URI segment routing.

It means that it will look at the segments of the URI (the path of the requested URL), and will map that to a controller action method.

If for example your URL is http://example.org/try/this/out/please, the framework will look for:
- a controller called Controller_This_Out in the module "try", with a method called "action_please"
- a controller called Controller_This in the module "try", with a method called "action_out"
- a controller called Controller_This_Out_Please in the module "try", with a method called "action_index"
- a controller called Controller_Try_This_Out in the application, with a method called "action_please"
- a controller called Controller_Try_This in the application, with a method called "action_out"
- a controller called Controller_Try_This_Out_Please in the module "try", with a method called "action_index"

This is the default behaviour, and can be altered by defining routes, which can map the URI segments to another controller.

Once the controller method is located, it is called, and the rest is up to you as a developer. If you're using a standard controller (extends \Controller), your method should return either a Response object with the response you want to send back to the browser, a View object, or a Theme object. If your controller extends Controller_Template, your method should assign data to the defined template, the returned output will be created automatically by the framework.

As for files on disk, the structure maps to the class name (and the other way around).

So, if you have a controller in app/classes/controller/try/this.php, it must contain a class called Controller_Try_This. If this then contains a method called "action_out", you can call this method using the URL "http://example.org/try/this/out".