Been stuck on this for the better part of the day... Can anyone think of what might be wrong? 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 it redirects 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. I have tried all the obvious artisan commands: route:clear
, route:cache
, cache:clear
, view:clear
, clear-compiled
, config:clear
, optimize
... AllowOveride All
is in the apache conf for this vhost. I checked for other caches, including OPcache and it looks like there aren't any set up.
from Newest questions tagged laravel-5 - Stack Overflow https://ift.tt/2BZYFWn
via IFTTT
Aucun commentaire:
Enregistrer un commentaire