Unofficial Kohana 3.0 Wiki routing

routing:404_pages_by_catching_reflection_exception

2010-07-01T11:52:51+00:00

404 Error Pages by catching ReflectionException This is just a quick guide to accurately displaying a 404 error. Using a catch-all route won't work 100% of the time, because you can have the correct Controller, but the wrong action, and it will throw a ReflectionException.

routing:building_routes_with_subdirectories

2009-10-13T19:43:27+00:00

What if you wanted to use sub-directories in your controller and dynamically support these in your routing you can use the following examples as a starting point. Supporting a Single Sub-directory Let's consider the following controller ( Controller_Foo_Bar )

routing:creating_a_custom_404_page

2010-04-01T11:33:58+00:00

In order to have a custom 404 page in your Kohana application you'll want to try and catch all invalid routes and direct them to a controller/action specifically setup to display a 404 message. The following example route does this. While most custom routes should be defined before your default route, in this case the catch all should be defined after your default route. (*note: your default route will need to be more specific than the standard default route defined in the unedited application …

routing:differ_request_for_internal_and_external

2010-01-21T23:35:04+00:00

When using Kohana HMVC it is nice to differ the requests into external (the ones that come from the client) and the internal (sub-requests that are made within your application). To do so just check to see if the request is internal or external in the before() method of your template controller.

routing:how_to_redirect_the_user_request

2009-10-16T04:21:12+00:00

If you want to redirect the user request to a new page or a new route you can use the redirect() method from the Request Class Usage Request::instance()->redirect('http://kohanaphp.com'); Request::instance()->redirect('controller/action'); Request::instance()->redirect( Route::get('demo-sample')->uri(array('category'=>'books', 'id'=>5)) );

routing:how_to_test_the_routes

2009-10-19T16:14:58+00:00

Often you want to test the routes you've just created. You can go to the URI, but you can also do it with a little snippet as mentioned here. The snippet looks like: // Here you define the routes // ... Route::set('post', 'post/', array('id' => '[\d]+')) ->defaults(array( 'controller' => 'post', 'action' => 'index', )); // ... // The URI to test $uri = 'post/1'; // This will loop trough all the defined routes and // tries to match them with…

routing:ignoring_overflow_in_a_route

2009-10-13T17:30:31+00:00

By default a Kohana route looks like this. controller/action/id But what if you want your route to also support the following controller/action/id/and/anything/else/you/want/to/add/at/random You need to modify your default route and add a little regex in your application/bootstrap.php file.

routing:multi-language_with_a_route

2010-06-14T15:25:40+00:00

There are many ways to accomplish i18n functionality with Kohana. One way is to incorporate language into a Route. For example http://example.com/en-us/products // For English http://example.com/fr-fr/products // For French You can define your Route to catch the language portion of the request. The example below only allows English, French and Dutch to be requested and defaults to English.

routing:reverse_routing_and_pagination

2010-07-01T11:41:44+00:00

One of the great things about Routing in Kohana 3 is that you can generate link URLs which are attributed to a named route. This allows you to change the schema at the Route, and have it apply on both ends at the Controller and everywhere the Route is used to generate the controller.

routing:routing_basics

2010-06-20T20:51:28+00:00

Kohana 3.0s Route Class provides you with unlimited options on how to map specifically formatted requests to specific controllers and actions. Routes should be defined in your application/bootstrap.php file or in the modules/mymodule/init.php file by calling the Route::set() method.

routing:static_pages

2009-10-21T15:31:36+00:00

Kohana works extremely well for building dynamic web sites and applications. However not everything needs to be dynamic and creating a controller/action combination for every static page is a little over kill. Here is how you can create a controller and route to handle static pages and support i18n so that your site can be multilingual.