Throw new NotFoundHttpException("Controller method not found.");

gravitano

replied 10 years ago

On your browser just go to below address:

http://localhost:8000/users/test

Last updated 1 year ago.

0

jedarlington

replied 10 years ago

I am having the exact same issue as this and cannot work out why an exception is being thrown. Did navigating to the URL work for you?

Last updated 1 year ago.

0

zenry

replied 10 years ago

what is the output of

$ php artisan routes

Last updated 1 year ago.

0

jedarlington

replied 10 years ago

I have just deleted the files I created to route to and started again and the controller appears to be functional now, I am unsure as to why.

Last updated 1 year ago.

0

rasparac

replied 10 years ago

+--------+----------------------------------------------------------+------+----
------------------------------+----------------+---------------+
| Domain | URI                                                      | Name | Act
ion                           | Before Filters | After Filters |
+--------+----------------------------------------------------------+------+----
------------------------------+----------------+---------------+
|        | GET index/{one?}/{two?}/{three?}/{four?}/{five?}         |      | Use
rsController@getIndex         |                |               |
|        | GET /                                                    |      | Use
rsController@getIndex         |                |               |
|        | GET registration/{one?}/{two?}/{three?}/{four?}/{five?}  |      | Use
rsController@getRegistration  |                |               |
|        | POST registration/{one?}/{two?}/{three?}/{four?}/{five?} |      | Use
rsController@postRegistration |                |               |
|        | GET login/{one?}/{two?}/{three?}/{four?}/{five?}         |      | Use
rsController@getLogin         |                |               |
|        | POST login/{one?}/{two?}/{three?}/{four?}/{five?}        |      | Use
rsController@postLogin        |                |               |
|        | GET dashboard/{one?}/{two?}/{three?}/{four?}/{five?}     |      | Use
rsController@getDashboard     |                |               |
|        | POST logout/{one?}/{two?}/{three?}/{four?}/{five?}       |      | Use
rsController@postLogout       |                |               |
|        | GET {_missing}                                           |      | Use
rsController@missingMethod    |                |               |
|        | GET login/test/{one?}/{two?}/{three?}/{four?}/{five?}    |      | Pro
filesController@getTest       |                |               |
|        | GET login/{_missing}                                     |      | Pro
filesController@missingMethod |                |               |
+--------+----------------------------------------------------------+------+----
------------------------------+----------------+---------------+

Last updated 1 year ago.

0

usm4n

replied 10 years ago

Solution

Routes are First In First Out, sometimes the order of registering them matters make sure your deep routes come first. For instance:

Route::controller('/','IndexController');
Route::controller('users','UsersController');

The above code will throw the same error when you will try to access /user route... the correct order is:

Route::controller('users','UsersController');
Route::controller('/','IndexController');

Last updated 1 year ago.

0

Moderators