If Laravel routes are similar to Symfony’s, then the sequence they are in matters, because the routes are checked in a top down fashion.
I couldn’t find any mention about route sequence in the Laravel docs. But here, from the Symfony docs (which are tons better than the Laravel docs).
Earlier Routes always Win
What this all means is that the order of the routes is very important. If the blog_show route were placed above the blog route, the URL /blog/2 would match blog_show instead of blog since the {slug} parameter of blog_show has no requirements. By using proper ordering and clever requirements, you can accomplish just about anything.
I also had problems with Laravel routes.php because I was used to CodeIgniter’s way of defining routes.
I have this reminder at the top of my Laravel routes.php file:
// ----------------------------------------------
// GETS LEAST FIRST NOT LIKE CodeIgniter !!!!
// ----------------------------------------------
Route::post('dashboard/{type?}', 'DashboardController@store');
Route::get('dashboard/{type?}/create', 'DashboardController@create');
I would be tempted to start with no routes and add them one at a time
I am not sure but I think CodeIgniter ver: 3.03 has changed the order of the routes.php and now it is similar to Laravel.