You must have a typo somewhere or is calling the wrong route.
The error say view [things.show] not found
View [things.show] not found.
but the ThingyController.php have [thingy.show] not [things.show]
//ThingyController.php
return View::make('thingy.show', $data);
fraserk said:
You mush have a typo somewhere or is calling the wrong route.
The error say View [things.show] not found. but the //ThingyController.php return View::make('thingy.show', $data);
say thingy.show
Thanks fraserk for your speedy response, however I'm sure there are no typos. $data is merely an array of data that I am passing to the view, which works fine.
Further in "ThingyController.php", if I make the view as in "ThingiesController.php" like so:
// This is ThingyController.php
// but showing the view of ThingiesController.php
return View::make('thingies.show', $data);
oddly the view is found. Both views are identical too.
I have destroyed the VM instance and restarted so I don't think it's a caching issue.
I'm wondering if there's a conflict with the 2 routes?
EDIT:
Fraserk, I apologise, you were correct with the typo, although it wasn't in my code. The damn show.blade.php file was named as "show,blade.php" (notice the comma instead of period). Sorry, so dumb of me.
Happens to me all the time. Glade you got it working..
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community