Interesting Laravel routing url problems

Question

I've got (what is to me) an interesting url question.

This is my situation. I have what will be a user populated database, so I cannot be sure how many subareas I will have.

I will always have an area, one or more subareas, and a location that ends my url.

example: /area/subarea1/subarea2/location

This is slightly simplified from what I need. I need to be able to service the following urls as well;

/area/subarea1/location

/area/subarea1/subarea2/subarea3/location)

My routes look something like this:

Route::get('area/{subarea1}', 'SubareaController@show');
Route::get('area/{subarea1}/{location}', 'LocationController@show');
Route::get('area/{subarea1}/{subarea2}', 'SubareaController@show2');
Route::get('area/{subarea1}/{subarea2}/{location}', 'LocationController@show2');

So the problem here is that my routes are overriding each other, because they are essentially the same.

My question is this. Is there any way to differentiate these routes when they have the same url structure? And if not, is there a better way to handle multiple subareas between an area, and a location?

EDIT

Ok I've been tried naming my routes, but I can't seem to be able to use the named routes correctly with all my parameters in the view. I may look into the area/{subarea1}/subarea1/{subarea2}/subarea2 solution, even though I would rather not have the longer URL.

What about naming your routes?

Narendrasingh Sisodia
– Narendrasingh Sisodia

2016-07-08 06:24:41 +00:00
Commented Jul 8, 2016 at 6:24 — Narendrasingh Sisodia
– Narendrasingh Sisodia, Commented Jul 8, 2016 at 6:24

rzb · Accepted Answer · 2016-07-08 06:29:49Z

2

This happens because Laravel has no way to distinguish each route from the other. For example, it would route these 2 url's to the same action:

example.com/area/my-subarea-1/my-location
example.com/area/my-subarea-1/my-subarea-2

So you need different paths. Try this:

Route::get('area/subarea1/{subarea1}', 'SubareaController@show');
Route::get('area/subarea1/{subarea1}/location/{location}', 'LocationController@show');
Route::get('area/subarea1/{subarea1}/subarea2/{subarea2}', 'SubareaController@show2');
Route::get('area/subarea1/{subarea1}/subarea2/{subarea2}/location/{location}', 'LocationController@show2');

edited Jul 8, 2016 at 6:29

answered Jul 8, 2016 at 6:24

rzb

2,1736 gold badges22 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Aptorian Over a year ago

Thanks, this solution seems to be working. I may go back later and try the named routing solution to see if I can get a smaller url, as in it's current form it's quite unwieldy.

rzb Over a year ago

Naming the routes is always recommended because it helps you reference your routes across your app without worrying about them being changed someday, but it won't solve this specific issue. The url's would still be the same and overwrite each other.

Collectives™ on Stack Overflow

Interesting Laravel routing url problems

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related