Try this: public function login_article($id){ if(user checks out){ return Redirect::route('view_article',array('id'=>$id)); } }
Nope that doesn't help. Now I've heard buzz about "controller to controller" actions not being a good way to handle things, I wonder if this is the issue. I've been thrown this exception when I have a GET route and my form (by default) is POST, so I have to explicitly make the form use GET. In this case, where the form is POST, going to a POST route, and then redirecting to a GET route, is there something I need to do to make that second request GET? Here's the big question: Are there two requests? What's my name? Where am I?? .. lol.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community