Just wondering if anyone might have an insight into this or at least how to proceed with debugging. I have a very straightforward route:
Route::get('incidents/{incident}', 'IncidentsController@show');
It works fine in my testing environment. I'm using route model binding with the Incident eloquent model. In production it's barfing out the RouteCollection NotFoundHttpException when I navigate to the url:
https://example.com/application/incidents/1411667
Not that it would matter, but the incident does exist in the database. When I run php artisan route:list
on the server, it shows that the route exists. All other routes are working.I am using the web middleware on the Route::group that this is part of.
from Newest questions tagged laravel-5 - Stack Overflow https://ift.tt/2PPpQpD
via IFTTT
Aucun commentaire:
Enregistrer un commentaire