The relevant section of my routes.php: http://laravel.io/bin/mkJyn
I have two routes (people/list and people) which point to the same controller/method. However, the first one (people/list) returns a blank screen with no errors in the log while the second one (people) returns the correct view. It seems that the routing logic is not finding the browse() method, though it is loading PersonController. Any idea why that would be??
I think you need to namespace you controller or rename list to something else, sounds like a conflict to me. try changing to "lista" or something, to test it out...
Can you show the controller method that handles the request.
I've tried changing the route from people/list to people/all, but it still only works for the people/ route. If the conflict was in the controller, I'd expect none of the routes in the group to work, but everything else works correctly (both in that route group and in the controller). Using Sharma Profiler, I don't get a WSOD but rather a white screen plus the debug bar, so nothing is throwing a fatal error. Using Log, I can see that the controller class is created (__construct() executes). For whatever reason, the browse() method is only executed when the route is people/.
@mcraz, The controller method has nothing but returning Response::make() in it. The problem is that the method is not executed except for Route::get('/')
.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community