I've started playing around with Laravel. I want to create simple authentication logic using 'auth' filter for my route. The problem is when I set the route like this:
Route::get('/user', array('before' => 'auth', 'as' => 'user', function() {
return Redirect::action('UserController#index');
}));
Route::get('/login', 'UserController#login');
I get: [InvalidArgumentException] - Route [UserController#index] not defined
However, when I go with a basic route:
Route::get('/user', 'UserController#index');
the page renders successfully.
Can anyone see the problem?
You could try adjusting the route to use UserController#index
Route::get('/user', array(
'before' => 'auth',
'as' => 'user',
'uses' => 'UserController#index'
));
Related
i have this from my routes/web.php
Route::group([
'middleware' => 'user',
'prefix' => 'currency',
'as' => 'currency-'
], function (){
Route::get('/', [CurrencyController::class, 'index'])->name('currency');
Route::get('add', [CurrencyController::class, 'add'])->name('add');
Route::get('edit/{id}', [CurrencyController::class, 'edit'])->name('edit');
Route::post('add', [CurrencyController::class, 'form_add']);
});
i need to get the route with format the prefix name and the route name. So the result will be like currency-currency and currency-add.
can i do something like Route::PrefixRoute()?
you can access current request route name using one of the below methods.
public function index(Request $request){
dd($request->route()->getName());
}
or
request()->route()->getName()
or
import use Illuminate\Support\Facades\Route; so you can access like
Route::currentRouteName()
I have setup Laravel 5.5 and installed the default authentication scaffolding.
My application has two types of users - customers and staff - so I prefer to name the authentication guards that way, and the following configuration seems to work.
'guards' => [
'web' => [
'driver' => 'session',
'provider' => 'users',
],
'customers' => [
'driver' => 'session',
'provider' => 'customer-users',
],
'staff' => [
'driver' => 'session',
'provider' => 'staff-users',
],
'api' => [
'driver' => 'token',
'provider' => 'users',
],
My providers, customer-users and staff-users, use the standard eloquent driver, however they each return a different user type.
The problem is that I would like to remove the 'web' guard, since it's just cluttering the config file. When I do however, I get an exception somewhere deep in the Laravel middleware.
I can live with the extra clutter of course, but it does bother me that Laravel is relying on a configuration item that I can't change. Is this a Laravel bug, perhaps?
BTW - I don't have 'web' set as the default guard when I get the error...
By default web guard given by laravel which used for web authentication based on session driver with the table users. Now you have created your own custom guards and you are using it. So your wish to keep that web guard. But if you remove, you might be facing some internal issue, so best you keep it and it's not going to be the performance issue too.
How can I use middleware with resources?
Route::resource('myitem', ['middleware' => 'auth', 'uses' => 'App\\Controllers\\MyitemsController']);
Just followed https://laracasts.com/discuss/channels/general-discussion/struggling-with-routeresource-and-auth-middleware but unfortunately could not solve.
Getting error:
ErrorException (E_UNKNOWN)
Array to string conversion
Open: /vendor/laravel/framework/src/Illuminate/Routing/Router.php
protected function getResourceAction($resource, $controller, $method, $options)
{
$name = $this->getResourceName($resource, $method, $options);
return array('as' => $name, 'uses' => $controller.'#'.$method);
}
Using filter with resource was not working that why had to use Route::group
Route::group(array('before' => 'auth'), function()
{
Route::resource('myitem', 'App\\Controllers\\MyitemsController');
});
https://stackoverflow.com/a/17512478/540144
Middleware is a new feature of Laravel 5. In Laravel 4, filters where something similar. So instead of using the key middleware you should use before or after. Also, and that's where the error comes from, the second argument of Route::resource should be the controller name as string and the third one is an array of options:
Route::resource('myitem', 'App\\Controllers\\MyitemsController', ['before' => 'auth']);
Edit
Apparently before filters only work with resource routes when you wrap a group around it. See the OPs answer for an example...
I just came up against this and found the easiest way is to add the middleware straight to the controller.
I found my answer here:
http://laravel.com/docs/master/controllers
class MyitemsController extends Controller {
/**
* Instantiate a new MyitemsController instance.
*/
public function __construct()
{
$this->middleware('auth');
}
}
How to do this in Laravel 5. The Answer you have been waiting for.
Use middleware instead of before
Route::group(array('middleware' => 'auth'), function()
{
Route::resource('user', 'UserController',
['only' => ['edit']]);
}
To check if the route is setup, run:
php artisan route:list
which should show the following:
GET|HEAD | user/{user}/edit | user.edit | App\Http\Controllers\UserController#edit | auth
Note auth instead of guest
Better solution
Use middleware instead of before
Route::group(['middleware' => 'auth'], function(){
Route::resource('myitem', 'MyitemsController');
});
You can check if it's ok with:
php artisan route:list
How can I use Controllers instead of Routes when with dingo/api (https://github.com/dingo/api) package?
The documentation (https://github.com/dingo/api/wiki) uses routes only.
Dingo is just an extension of the Laravel router, so you can use controllers just like you do in any other Laravel project.
So this:
Route::api(['version' => 'v1', 'prefix' => 'api'], function()
{
Route::get('posts', function()
{
return Post::all();
});
});
would become:
Route::api(['version' => 'v1', 'prefix' => 'api'], function()
{
Route::get('posts', 'PostsController#index');
});
Do you mean connecting a controller to a specific dingo route? like this:
$api = app('Dingo\Api\Routing\Router');
then followed by
$api->version('v1', function($api){
$api->get('posts', 'PostsController#index');
});
But somehow Dingo cannot find the directory of controller, so what I do is start from App\ directory like this: App\Http\Controllers\PostsController#index .
so the correct syntax would be
$api->get('posts', 'App\Http\Controllers\PostsController#index');
I use custom routes which include namespace besides controller and action. So for ACL purposes I use MVC route name as ACL resource name. Now I need to obtain currently DISPATCHING route name. The only solution I've come up with is to get namespace/controller/action from Dispatcher and iterating over all the routes find an appropriate one.
Is there any easiest way to obtain currently dispatching (not just matched) route name?
Pretty easy
\Phalcon\DI::getDefault()->get('router')->getMatchedRoute()->getName();
You can use your router, dispatcher and base controller to get what you need. Consider this:
$router = new \Phalcon\Mvc\Router(false);
$routes = array(
'/{namespace:"[a-zA-Z]+}/:controller' => array(
'controller' => 2,
),
'/{namespace:"[a-zA-Z]+}/:controller/:action/:params' => array(
'controller' => 2,
'action' => 3,
'params' => 4,
),
);
foreach($routes as $route => $params) {
$router->add($route, $params);
}
Now in your base controller you can do this:
public function getNamespace()
{
return $this->dispatcher->getParam('namespace');
}
This way you can have the namespace currently being served in your controllers (so long as they extend your base controller).
If you need to get the namespace in a model you can always use the DI like so (base model):
public function getNamespace()
{
$di = \Phalcon\DI::getDefault();
return $di->dispatcher->getParam('namespace');
}