Kohana 3.1 routes with default subdirectories?

Yes, it can be cleaned better. Kohana developers encourage people using this framework to add as much routes as needed You can even specify them for each action which will enable you to change URLs in the future (eg. Instead of user/login you may wish to have signin ), if you use proper methods to generate links etc.(eg Route::url() helper) Now, saying that, here is the other way to specify the user route: Route::set('user', '(/(/))', array('controller' => '(user|admin_user)')) ->defaults(array( 'controller' => 'user', 'action' => 'index', )) Which will match only the requests, where the first part of the URI is given and is equal either to user or admin_user Previously the controller part was optional, thus was also matching calls to URI.

Yes, it can be cleaned better. Kohana developers encourage people using this framework to add as much routes as needed. You can even specify them for each action which will enable you to change URLs in the future (eg.

Instead of /user/login you may wish to have /signin), if you use proper methods to generate links etc. (eg. Route::url() helper). Now, saying that, here is the other way to specify the user route: Route::set('user', '(/(/))', array('controller' => '(user|admin_user)')) ->defaults(array( 'controller' => 'user', 'action' => 'index', )); Which will match only the requests, where the first part of the URI is given and is equal either to user or admin_user.

Previously the controller part was optional, thus was also matching calls to / URI.

Works perfectly. Thankyou. – Das123 Aug 28 at 21:46.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.