Category Archives: Laravel

Laravel Tutorials

Laravel Passing Multiple Parameters In Route to Controller

Today in this tutorial, we will learn to pass multiple parameters through named route to controller method. In this Laravel Passing Multiple Parameters In Route to Controller tutorial you will learn to pass multiple parameters using route to controller. You will also learn to define route with multiple parameters in laravel so that can access them in controller method.

Passing Multiple Parameters Using Route to Controller

Sometimes we need to pass multiple parameters in URL so that we can get those parameters in controller method to perform required action. In this example, will first define a route with multiple parameters and then we will add a controller method accepting multiple parameters. Then we will setup a link with named route having multiple parameters.

Define route with multiple parameters

Now we will learn to define route with multiple parameters.

Syntax (route):-

Below is basic syntax to define a get request route accepting multiple parameters:

Route::get('test/{paramter1}/{paramter2}', 'Somecontroller@somemethod');

1	Route::get('test/{paramter1}/{paramter2}', 'Somecontroller@somemethod');

Example:-

Now, lets define a example get route accepting multiple parameters as below:

Route::get('/posts/show-post/{id}/{name}','PostController@show_post')->name('post.show');

1	Route::get('/posts/show-post/{id}/{name}','PostController@show_post')->name('post.show');

Define Controller Method With Multiple Parameters

Now we will learn to define a controller method accepting multiple parameters.

Syntax (Controller Method):-

Below is basic syntax for controller method accepting multiple parameters as below:

public function somemethod($paramter1, $paramter2){
	//my code
}

public function somemethod($paramter1, $paramter2){

//my code

}

Example:-

<?php

namespace App\Http\Controllers\Admin;

use Illuminate\Http\Request;
use App\Http\Controllers\Controller;
use DB;

class PostController extends Controller
{

public function show_post($id,$name){
echo $id.' - '.$name;
}

}

<?php

namespace App\Http\Controllers\Admin;

use Illuminate\Http\Request;

use App\Http\Controllers\Controller;

use DB;

class PostController extends Controller

{

public function show_post($id,$name){

echo $id.' - '.$name;

}

Define Named Route With Multiple Parameters

Now, we can setup a named route link in view as below:

 <a class="btn btn-success" href="{{route('post.show',['id'=>$post->id,'name'=>$post->title])}}">Show</a>

1	<a class="btn btn-success" href="{{route('post.show',['id'=>$post->id,'name'=>$post->title])}}">Show</a>

Laravel Session Not Working In Constructor

Leave a reply

Laravel Session Not Working In Constructor

Back in laravel 5.2, we were able to interact with the session directly in a controller constructor. However, this has changed in laravel 5.3. Now in Laravel 5.3, you can’t access the session or authenticated user in your controller’s constructor because the middleware has not run yet. As an alternative, you may define a Closure based middleware directly in your controller’s constructor. Using an inline middleware, we can directly hook into the request’s routing, so that we have full access to the session:

Laravel Inline middleware

Using an inline middleware, we can directly hook into the request’s routing, so that we have full access to the session:

Example:-

public function __construct()
{
$this->middleware(function ($request, $next) {

$uInfo = Session::get('user_info');
if(isset($uInfo) && !empty($uInfo)){
	return redirect('/user-dashboard');
}
return $next($request);
});

}

public function __construct()

{

$this->middleware(function ($request, $next) {

$uInfo = Session::get('user_info');

if(isset($uInfo) && !empty($uInfo)){

return redirect('/user-dashboard');

}

return $next($request);

});

}

Laravel Prevent Browser Back Button After Logout

Leave a reply

Laravel Prevent Browser Back Button After Logout

In this example, we will learn to prevent browser back button after user logout, so that he will not be able to access auth protected routes or pages after logout.

In Laravel, it is quite a common problem that when user logout and then click on the back button in browser the browser shows the last loaded page from the website. In this article, I’ll show you how to prevent back button after logout in Laravel application. In Laravel, when a user logout from application and then hit the browser back button then he will be sent back to the page he was visiting before logout. Ideally, user should not be allowed to access auth middleware protected routes or pages. User should be redirect back to application login page instead of the page he was visiting.

In this tutorial, we will prevent this issue by using laravel middleware. We will create a middleware and use it with routes to prevent back button history.

Create New Middleware

In this step, we will create a new middleware using following command:

php artisan make:middleware PreventBackHistory

1	php artisan make:middleware PreventBackHistory

Middleware Configuration

Open up PreventBackHistory.php file in app/Http/Middleware folder and replace codes with the following codes below:

app/Http/Middleware/PreventBackHistory.php

<?php

namespace App\Http\Middleware;

use Closure;

class PreventBackHistory {
  /**
   * Handle an incoming request.
   *
   * @param  \Illuminate\Http\Request  $request
   * @param  \Closure  $next
   * @return mixed
   */
  public function handle($request, Closure $next) {
    $response = $next($request);

    return $response->header('Cache-Control','nocache, no-store, max-age=0, must-revalidate')
            ->header('Pragma','no-cache')
            ->header('Expires','Sat, 26 Jul 1997 05:00:00 GMT');
  }
}

<?php

namespace App\Http\Middleware;

use Closure;

class PreventBackHistory {

/**

* Handle an incoming request.

* @param \Illuminate\Http\Request $request

* @param \Closure $next

* @return mixed

public function handle($request, Closure $next) {

$response = $next($request);

return $response->header('Cache-Control','nocache, no-store, max-age=0, must-revalidate')

->header('Pragma','no-cache')

->header('Expires','Sat, 26 Jul 1997 05:00:00 GMT');

}

Register Middleware

In this step we have to register middleware, open Kernel.php in app/Http folder and add a new middleware in $routeMiddleware variable array as below:

app/Http/Kernel.php

<?php

namespace App\Http;

use Illuminate\Foundation\Http\Kernel as HttpKernel;

class Kernel extends HttpKernel {
  .....
  .....

  /**
   * The application's route middleware.
   *
   * These middleware may be assigned to groups or used individually.
   *
   * @var array
   */
  protected $routeMiddleware = [
    .....

    'prevent-back-history' => \App\Http\Middleware\PreventBackHistory::class,
  ];

}

<?php

namespace App\Http;

use Illuminate\Foundation\Http\Kernel as HttpKernel;

class Kernel extends HttpKernel {

.....

/**

* The application's route middleware.

* These middleware may be assigned to groups or used individually.

* @var array

protected $routeMiddleware = [

.....

'prevent-back-history' => \App\Http\Middleware\PreventBackHistory::class,

];

}

Add Middleware in Route

Now open routes/web.php files and add “prevent-back-history” middleware in route file as below:

routes/web.php

Route::group(['middleware' => 'prevent-back-history'],function(){
  Auth::routes();
  Route::get('/home', 'HomeController@index');
});

Route::group(['middleware' => 'prevent-back-history'],function(){

Auth::routes();

Route::get('/home', 'HomeController@index');

});

Laravel Clear Cache After Logout

Leave a reply

Laravel Clear Cache After Logout

In this example, we will learn to destroy session, cookies, cache and prevent browser back button after user logout, so that he will not be able to access auth protected routes or pages after logout.

Here is the logout function code that worked for me:

public function logout(Request $request) {
    header("cache-Control: no-store, no-cache, must-revalidate");
    header("cache-Control: post-check=0, pre-check=0", false);
    header("Pragma: no-cache");
    header("Expires: Sat, 26 Jul 1997 05:00:00 GMT");
    Session::flush();
    $request->session()->regenerate();
    Session::flash('succ_message', 'Logged out Successfully');
    return redirect('signin');
}

public function logout(Request $request) {

header("cache-Control: no-store, no-cache, must-revalidate");

header("cache-Control: post-check=0, pre-check=0", false);

header("Pragma: no-cache");

header("Expires: Sat, 26 Jul 1997 05:00:00 GMT");

Session::flush();

$request->session()->regenerate();

Session::flash('succ_message', 'Logged out Successfully');

return redirect('signin');

}

Here, we are flushing the session and cache then after redirecting user to login page.

Laravel Clear Cache on Shared Hosting without Artisan command

Leave a reply

Laravel Clear Cache on Shared Hosting

In this laravel clear cache shared hosting tutorial, I’ll show you how to clear cache on shared hosting using laravel route. In shared host we dont have access to command line (CLI), in this tutorial I’ll show you to clear cache without artisan command.To clear laravel cache we have to define routes in our application’s routes/web.php file that invoke the various laravel clear cache commands. This way we can clear Laravel cache by accessing specific routes in the browser.

Laravel Clear Route Cache On Shared Hosting

Lets define “route-cache” route in routes/web.php file to clear route cache without using artisan command.

 Route::get('/route-cache', function() {
     $exitCode = Artisan::call('route:cache');
     return 'Routes cache cleared';
 });

Route::get('/route-cache', function() {

$exitCode = Artisan::call('route:cache');

return 'Routes cache cleared';

});

Laravel Clear Config Cache On Shared Hosting

Lets define “config-cache” route in routes/web.php file to clear config cache without using artisan command.

 Route::get('/config-cache', function() {
     $exitCode = Artisan::call('config:cache');
     return 'Config cache cleared';
 });

Route::get('/config-cache', function() {

$exitCode = Artisan::call('config:cache');

return 'Config cache cleared';

});

Laravel Clear Application Cache On Shared Hosting

Lets define “clear-cache” route in routes/web.php file to clear application cache without using artisan command.

 Route::get('/clear-cache', function() {
     $exitCode = Artisan::call('cache:clear');
     return 'Application cache cleared';
 });

Route::get('/clear-cache', function() {

$exitCode = Artisan::call('cache:clear');

return 'Application cache cleared';

});

Laravel Clear View Cache On Shared Hosting

Lets define “view-clear” route in routes/web.php file to clear view cache without using artisan command.

 Route::get('/view-clear', function() {
     $exitCode = Artisan::call('view:clear');
     return 'View cache cleared';
 });

Route::get('/view-clear', function() {

$exitCode = Artisan::call('view:clear');

return 'View cache cleared';

});

Insert data using Database Seeder in Laravel

Leave a reply

Insert data using Database Seeder in Laravel

There are many instances where we need a populated database with test data in order to test the working of various operation. Populating Test data manually is time consuming, but Laravel provides a simple method of seeding test data in your database automatically instead doing it manually. In laravel you are required to created seeder classed per table, all these classes are stored in the database/seeds directory.

Today in this article, we will learn how to insert data using Database Seeder in Laravel. I’ll show you how to create database seeder class for a table, seed data in seeder, call database seeder and run database seeder. In this example, we assume that we already have admins table created and wants to seed some test data into it.

Create Seeder Using Artisan Command

Seeder class file can be generated using following artisan command:

Syntax:-

php artisan make:seeder <TableNameSeeder>

1	php artisan make:seeder <TableNameSeeder>

Example:-

php artisan make:seeder AdminsTableSeeder

1	php artisan make:seeder AdminsTableSeeder

Once the above command is executed, this will generate a seeder class file in the database/seeds directory. This class has a default run() method.

database/seeds/AdminsTableSeeder.php

<?php

use Illuminate\Database\Seeder;

class PostsTableSeeder extends Seeder
{
/**
* Run the database seeds.
*
* @return void
*/
public function run()
{
//
}
}

<?php

use Illuminate\Database\Seeder;

class PostsTableSeeder extends Seeder

{

/**

* Run the database seeds.

* @return void

public function run()

{

}

Add Data In Seeder Class file

Lets open seeder class file and within default run() method, we can populate single or multiple records as following:

Add Single Record:-

<?php
use Illuminate\Database\Seeder;
use Illuminate\Support\Facades\DB;

class AdminsTableSeeder extends Seeder
{
/**
* Run the database seeds.
*
* @return void
*/
public function run()
{

DB::table('admins')->insert([
'name' => "Keith",
'email' => 'keith@gmail.com',
'password' => bcrypt('secret'),
]);

}
}

<?php

use Illuminate\Database\Seeder;

use Illuminate\Support\Facades\DB;

class AdminsTableSeeder extends Seeder

{

/**

* Run the database seeds.

* @return void

public function run()

{

DB::table('admins')->insert([

'name' => "Keith",

'email' => 'keith@gmail.com',

'password' => bcrypt('secret'),

]);

}

Add Multiple Records:-

 public function run()
{

DB::table('admins')->insert(array(
array(
'name' => "Steve",
'email' => 'steve@gmail.com',
'password' => bcrypt('secret'),
),
array(
'name' => "Laura",
'email' => 'laura@gmail.com',
'password' => bcrypt('secret'),
)
));

}

public function run()

{

DB::table('admins')->insert(array(

array(

'name' => "Steve",

'email' => 'steve@gmail.com',

'password' => bcrypt('secret'),

array(

'name' => "Laura",

'email' => 'laura@gmail.com',

'password' => bcrypt('secret'),

)

));

}

Call Seeder

Laravel comes with a default seeder class named DatabaseSeeder which is executed by default when the db:seed command invoked. This class can be used to call user-defined seeders like this:

public function run()
{
$this->call([
AdminsTableSeeder::class
]);
}

public function run()

{

$this->call([

AdminsTableSeeder::class

]);

}

Run Seeder

Once the seeder classes are setup, we are ready to run laravel seeders using following artisan command:

php artisan db:seed

1	php artisan db:seed

We can also run a specific seeder class directly without adding it to the DatabaseSeeder class as following:

php artisan db:seed --class=AdminsTableSeeder

1	php artisan db:seed --class=AdminsTableSeeder

Call Seeder from Route

\Artisan::call('db:seed');

1	\Artisan::call('db:seed');

Call Seeder from Controller

\Artisan::call('db:seed', array('--class' => 'AdminsTableSeeder'));

1	\Artisan::call('db:seed', array('--class' => 'AdminsTableSeeder'));

Call Seeder from Migration

\Artisan::call('db:seed');

1	\Artisan::call('db:seed');

Laravel Separate Admin Panel | Multiple Authentication System Using Guards

Leave a reply

Laravel 5.8 Multiple Authentication Using Custom Guard

In this Laravel multi (auth) authentication tutorial we will learn how to create separate admin panel or login using custom guard. Laravel multi (auth) authentication system allows to create multiple users login in single application.

While developing a laravel application there comes situations where we want create separate user login or separate user/admin panel for users having different privileges or access rights in same application. In laravel this can be achieved in following ways –

1. Laravel multi (auth) authentication using middleware

2. Laravel multi (auth) authentication Using Guards

In one of my previous article we have created separate admin login using laravel multi (auth) authentication using MIddleware In this article we will creating separate admin login using laravel multi (auth) authentication system with guard.

Install Laravel 5.8

First of all we need to create a fresh laravel project, download and install Laravel 5.8 using the below command

composer create-project --prefer-dist laravel/laravel laraMultiAuth

1	composer create-project --prefer-dist laravel/laravel laraMultiAuth

Configure Database In .env file

Now, lets create a MySQL database and connect it with laravel application. After creating database we need to set database credential in application’s .env file.

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=laramultiauth
DB_USERNAME=root
DB_PASSWORD=

DB_CONNECTION=mysql

DB_HOST=127.0.0.1

DB_PORT=3306

DB_DATABASE=laramultiauth

DB_USERNAME=root

DB_PASSWORD=

Create User Authentication Scaffolding

Laravel comes with in-built user authentication system, use the below command to generate default authentication scaffolding for user –

php artisan make:auth

1	php artisan make:auth

This command will generate required authentication Controller files, views and add routes in our web.php routes file that are required for user authentication system.

Creat Admin Migration

Now, we have to define table schema for admins table. Open terminal and use the following artisan command to generate <timestamp>create_admins_table.php migration.

php artisan make:migration create_admins_table

1	php artisan make:migration create_admins_table

Once this command is executed you will find a migration file created under “database/migrations”. Open migration file created (<timestamp>create_admins_table.php) and modify up method as following –

public function up()
{
    Schema::create('admins', function (Blueprint $table) {
        $table->bigIncrements('id');
        $table->string('name');
        $table->string('email')->unique();
        $table->string('password');
        $table->rememberToken();
        $table->timestamps();
    });
}

public function up()

{

Schema::create('admins', function (Blueprint $table) {

$table->bigIncrements('id');

$table->string('name');

$table->string('email')->unique();

$table->string('password');

$table->rememberToken();

$table->timestamps();

});

}

Run Migration

Now, run following command to migrate database schema.

php artisan migrate

1	php artisan migrate

After, the migration executed successfully the admins table will be created in database along with migrations, password_resets and users table.

Create Admin Model

Next we need to create a Admin model class. To make the model for the admins, run the following command:

php artisan make:model Admin

1	php artisan make:model Admin

Again our Admin model is really simple for now, this model will be like the user model and extends the Authenticable class. Open Admin model in app/Admin.php and add the following:

app/Admin.php

<?php

namespace App;

use Illuminate\Notifications\Notifiable;
use Illuminate\Foundation\Auth\User as Authenticatable;

class Admin extends Authenticatable
{
    use Notifiable;
    protected $guard = "admin";

    /**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $fillable = [
        'name', 'email', 'password',
    ];

    /**
     * The attributes that should be hidden for arrays.
     *
     * @var array
     */
    protected $hidden = [
        'password', 'remember_token',
    ];

}

<?php

namespace App;

use Illuminate\Notifications\Notifiable;

use Illuminate\Foundation\Auth\User as Authenticatable;

class Admin extends Authenticatable

{

use Notifiable;

protected $guard = "admin";

/**

* The attributes that are mass assignable.

* @var array

protected $fillable = [

'name', 'email', 'password',

];

/**

* The attributes that should be hidden for arrays.

* @var array

protected $hidden = [

'password', 'remember_token',

];

}

A typical model in laravel extends eloquent model but as we will be using this model for authentication so we will extend it with authenticatable class which is an alias of User class used for laravel authentication. We are also using notifiable trait which is used for password reset notification.

Add admin guard

Next we need to add a new guard for admin. Laravel guards are used for authentication which manages multiple authenticated instances from multiple tables. Open config/auth.php file and add a custom guard and provider for admins. Add admin guard in guards array as following:

'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],

        'api' => [
            'driver' => 'token',
            'provider' => 'users',
            'hash' => false,
        ],

        'admin' => [
            'driver'=>'session',
            'provider' => 'admins'

        ]
    ],

'guards' => [

'web' => [

'driver' => 'session',

'provider' => 'users',

'api' => [

'driver' => 'token',

'provider' => 'users',

'hash' => false,

'admin' => [

'driver'=>'session',

'provider' => 'admins'

]

Now we need to add a provider for admins in providers array as following:

'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => App\User::class,
        ],

        'admins' => [
            'driver' => 'eloquent',
            'model' => App\Admin::class

        ]

        // 'users' => [
        //     'driver' => 'database',
        //     'table' => 'users',
        // ],
    ],

'providers' => [

'users' => [

'driver' => 'eloquent',

'model' => App\User::class,

'admins' => [

'driver' => 'eloquent',

'model' => App\Admin::class

]

// 'users' => [

// 'driver' => 'database',

// 'table' => 'users',

// ],

Add Auth routes for Admin

Next, we need to create the route for admin authentication. Open the routes/web.php file and add the following code in it.

Route::namespace("Admin")->prefix('admin')->group(function(){
	Route::get('/', 'HomeController@index')->name('admin.home');
	Route::namespace('Auth')->group(function(){
		Route::get('/login', 'LoginController@showLoginForm')->name('admin.login');
		Route::post('/login', 'LoginController@login');
		Route::post('logout', 'LoginController@logout')->name('admin.logout');
	});
});

Route::namespace("Admin")->prefix('admin')->group(function(){

Route::get('/', 'HomeController@index')->name('admin.home');

Route::namespace('Auth')->group(function(){

Route::get('/login', 'LoginController@showLoginForm')->name('admin.login');

Route::post('/login', 'LoginController@login');

Route::post('logout', 'LoginController@logout')->name('admin.logout');

});

Create Auth Controller for Admin

Now, we will create admin login and home/dashboard controller files. For simplicity we’ll copy user auth login controller file:

app/Http/Controllers/Auth/LoginController.php

1	app/Http/Controllers/Auth/LoginController.php

into app/Http/Controllers/Admin/Auth and fix the class namespaces and update Admin LoginController as following:

<?php

namespace App\Http\Controllers\Admin\Auth;

use App\Http\Controllers\Controller;
use Illuminate\Foundation\Auth\AuthenticatesUsers;
use Illuminate\Http\Request;
use Illuminate\Support\Facades\Auth;

class LoginController extends Controller
{
    /*
    |--------------------------------------------------------------------------
    | Login Controller
    |--------------------------------------------------------------------------
    |
    | This controller handles authenticating users for the application and
    | redirecting them to your home screen. The controller uses a trait
    | to conveniently provide its functionality to your applications.
    |
    */

    use AuthenticatesUsers;

    /**
     * Where to redirect users after login.
     *
     * @var string
     */
    protected $redirectTo = '/admin';

    /**
     * Create a new controller instance.
     *
     * @return void
     */
    public function __construct()
    {
        $this->middleware('guest:admin')->except('logout');
    }

    public function showLoginForm(){
        return view('admin.auth.login');
    }

    /**
     * Log the user out of the application.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return \Illuminate\Http\Response
     */
    public function logout(Request $request)
    {
        $this->guard()->logout();

        $request->session()->invalidate();

        return redirect()->route('admin.login');
    }
    
     /**
     * Get the guard to be used during authentication.
     *
     * @return \Illuminate\Contracts\Auth\StatefulGuard
     */
    protected function guard()
    {
        return Auth::guard('admin');
    }

}

<?php

namespace App\Http\Controllers\Admin\Auth;

use App\Http\Controllers\Controller;

use Illuminate\Foundation\Auth\AuthenticatesUsers;

use Illuminate\Http\Request;

use Illuminate\Support\Facades\Auth;

class LoginController extends Controller

{

|--------------------------------------------------------------------------

| Login Controller

|--------------------------------------------------------------------------

| This controller handles authenticating users for the application and

| redirecting them to your home screen. The controller uses a trait

| to conveniently provide its functionality to your applications.

use AuthenticatesUsers;

/**

* Where to redirect users after login.

* @var string

protected $redirectTo = '/admin';

/**

* Create a new controller instance.

* @return void

public function __construct()

{

$this->middleware('guest:admin')->except('logout');

}

public function showLoginForm(){

return view('admin.auth.login');

}

/**

* Log the user out of the application.

* @param \Illuminate\Http\Request $request

* @return \Illuminate\Http\Response

public function logout(Request $request)

{

$this->guard()->logout();

$request->session()->invalidate();

return redirect()->route('admin.login');

}

/**

* Get the guard to be used during authentication.

* @return \Illuminate\Contracts\Auth\StatefulGuard

protected function guard()

{

return Auth::guard('admin');

}

Create HomeController.php file into app/Http/Controllers/Admin directory and update it as following:

<?php
namespace App\Http\Controllers\Admin;
use App\Http\Controllers\Controller;
class HomeController extends Controller
{
    /**
     * Create a new controller instance.
     *
     * @return void
     */
    public function __construct()
    {
        $this->middleware('auth:admin');
    }
    /**
     * Show the application dashboard.
     *
     * @return \Illuminate\Http\Response
     */
    public function index()
    {
        return view('admin.home');
    }
}

<?php

namespace App\Http\Controllers\Admin;

use App\Http\Controllers\Controller;

class HomeController extends Controller

{

/**

* Create a new controller instance.

* @return void

public function __construct()

{

$this->middleware('auth:admin');

}

/**

* Show the application dashboard.

* @return \Illuminate\Http\Response

public function index()

{

return view('admin.home');

}

Update Guest Middleware

Now we need to update the guest middleware RedirectIfAuthenticated for the admin auth guard. Open app/Http/Middleware/RedirectIfAuthenticated.php and add a check for the admin guard, so the handle method will now look something like this:

public function handle($request, Closure $next, $guard = null)
{
    if (Auth::guard($guard)->check()) {
        
        if($guard == "admin"){
            //user was authenticated with admin guard.
            return redirect()->route('admin.home');
        } else {
            //default guard.
            return redirect()->route('home');
        }

    }

    return $next($request);

}

public function handle($request, Closure $next, $guard = null)

{

if (Auth::guard($guard)->check()) {

if($guard == "admin"){

//user was authenticated with admin guard.

return redirect()->route('admin.home');

} else {

//default guard.

return redirect()->route('home');

}

return $next($request);

}

Update Exception Handler

At the moment if an user is authenticated they will redirect back to the same place, no matter what the guard is. Open app/Exceptions/Handler.php and add the unauthenticated method as following:

app/Exceptions/Handler.php

Add following directives on top:

use Illuminate\Auth\AuthenticationException;
use Auth;

1 2	use Illuminate\Auth\AuthenticationException; use Auth;

Add following method in handler class:

protected function unauthenticated($request, AuthenticationException $exception)
    {
        if (in_array('admin', $exception->guards())) {
            return $request->expectsJson()
                ? response()->json([
                      'message' => $exception->getMessage()
                ], 401)
                : redirect()->guest(route('admin.login'));
        }
    
        return $request->expectsJson()
            ? response()->json([
                  'message' => $exception->getMessage()
            ], 401)
            : redirect()->guest(route('login'));
    }

protected function unauthenticated($request, AuthenticationException $exception)

{

if (in_array('admin', $exception->guards())) {

return $request->expectsJson()

? response()->json([

'message' => $exception->getMessage()

], 401)

: redirect()->guest(route('admin.login'));

}

return $request->expectsJson()

? response()->json([

'message' => $exception->getMessage()

], 401)

: redirect()->guest(route('login'));

}

This will override the parent handler method.

Add Admin Views

Next we we will create all relevant views files for admin.

Admin Layout:-

Create the following directory resources/views/admin/layouts and in it we’ll add a new file app.blade.php and put following code in it:

resources/views/admin/layouts/app.blade.php

<!DOCTYPE html>
<html lang="{{ app()->getLocale() }}">
<head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">

    <!-- CSRF Token -->
    <meta name="csrf-token" content="{{ csrf_token() }}">

    <title>{{ $pageTitle ?? config('app.name', 'Admin') }}</title>

    <!-- Scripts -->
    <script src="{{ asset('js/app.js') }}" defer></script>

    <!-- Fonts -->
    <link rel="dns-prefetch" href="https://fonts.gstatic.com">
    <link href="https://fonts.googleapis.com/css?family=Raleway:300,400,600" rel="stylesheet" type="text/css">

    <!-- Styles -->
    <link href="{{ asset('css/app.css') }}" rel="stylesheet">
</head>
<body>
    <div id="app">
        <nav class="navbar navbar-expand-md navbar-light navbar-laravel">
            <div class="container">
                <a class="navbar-brand" href="{{ route('admin.home') }}">
                    Admin
                </a>
                <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
                    <span class="navbar-toggler-icon"></span>
                </button>

                <div class="collapse navbar-collapse" id="navbarSupportedContent">
                    <!-- Left Side Of Navbar -->
                    

                    <!-- Right Side Of Navbar -->
                    <ul class="navbar-nav ml-auto">
                        <!-- Authentication Links -->
                        @guest('admin')
                            <li><a class="nav-link" href="{{ route('admin.login') }}">{{ __('Admin Login') }}</a></li>
                        @else
                            <li class="nav-item dropdown">
                                <a id="navbarDropdown" class="nav-link dropdown-toggle" href="#" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false" v-pre>
                                    {{ Auth::user()->name }} <span class="caret"></span>
                                </a>

                                <div class="dropdown-menu" aria-labelledby="navbarDropdown">
                                    <a class="dropdown-item" href="{{ route('admin.logout') }}"
                                       onclick="event.preventDefault();
                                                     document.getElementById('logout-form').submit();">
                                        {{ __('Logout') }}
                                    </a>

                                    <form id="logout-form" action="{{ route('admin.logout') }}" method="POST" style="display: none;">
                                        @csrf
                                    </form>
                                </div>
                            </li>
                        @endguest
                    </ul>
                </div>
            </div>
        </nav>

        <main class="py-4">
            @yield('content')
        </main>
    </div>
</body>
</html>

<!DOCTYPE html>

<html lang="{{ app()->getLocale() }}">

<head>

<title>{{ $pageTitle ?? config('app.name', 'Admin') }}</title>

</head>

<body>

Admin

</a>

</button>

@guest('admin')

<li><a class="nav-link" href="{{ route('admin.login') }}">{{ __('Admin Login') }}</a></li>

@else

{{ Auth::user()->name }} <span class="caret"></span>

</a>

<a class="dropdown-item" href="{{ route('admin.logout') }}"

onclick="event.preventDefault();

document.getElementById('logout-form').submit();">

</a>

@csrf

</form>

</div>

</li>

@endguest

</ul>

</div>

</nav>

@yield('content')

</main>

</div>

</body>

</html>

Admin Login:-

Create the following directory resources/views/admin/auth and in it we’ll add a new file login.blade.php and put following code in it:

resources/views/admin/auth/login.blade.php

@extends('admin.layouts.app')

@section('content')
<div class="container">
    <div class="row justify-content-center">
        <div class="col-md-8">
            <div class="card">
                <div class="card-header">{{ __('Admin Login') }}</div>

                <div class="card-body">
                    <form method="POST" action="{{ route('admin.login') }}">
                        @csrf

                        <div class="form-group row">
                            <label for="email" class="col-sm-4 col-form-label text-md-right">{{ __('E-Mail Address') }}</label>

                            <div class="col-md-6">
                                <input id="email" type="email" class="form-control{{ $errors->has('email') ? ' is-invalid' : '' }}" name="email" value="{{ old('email') }}" required autofocus>

                                @if ($errors->has('email'))
                                    <span class="invalid-feedback">
                                        <strong>{{ $errors->first('email') }}</strong>
                                    </span>
                                @endif
                            </div>
                        </div>

                        <div class="form-group row">
                            <label for="password" class="col-md-4 col-form-label text-md-right">{{ __('Password') }}</label>

                            <div class="col-md-6">
                                <input id="password" type="password" class="form-control{{ $errors->has('password') ? ' is-invalid' : '' }}" name="password" required>

                                @if ($errors->has('password'))
                                    <span class="invalid-feedback">
                                        <strong>{{ $errors->first('password') }}</strong>
                                    </span>
                                @endif
                            </div>
                        </div>

                        <div class="form-group row">
                            <div class="col-md-6 offset-md-4">
                                <div class="checkbox">
                                    <label>
                                        <input type="checkbox" name="remember" {{ old('remember') ? 'checked' : '' }}> {{ __('Remember Me') }}
                                    </label>
                                </div>
                            </div>
                        </div>

                        <div class="form-group row mb-0">
                            <div class="col-md-8 offset-md-4">
                                <button type="submit" class="btn btn-primary">
                                    {{ __('Login') }}
                                </button>

                                <a class="btn btn-link" href="{{ route('password.request') }}">
                                    {{ __('Forgot Your Password?') }}
                                </a>
                            </div>
                        </div>
                    </form>
                </div>
            </div>
        </div>
    </div>
</div>
@endsection

@extends('admin.layouts.app')

@section('content')

<div class="card-header">{{ __('Admin Login') }}</div>

@csrf

<label for="email" class="col-sm-4 col-form-label text-md-right">{{ __('E-Mail Address') }}</label>

<input id="email" type="email" class="form-control{{ $errors->has('email') ? ' is-invalid' : '' }}" name="email" value="{{ old('email') }}" required autofocus>

@if ($errors->has('email'))

<strong>{{ $errors->first('email') }}</strong>

</span>

@endif

</div>

<label for="password" class="col-md-4 col-form-label text-md-right">{{ __('Password') }}</label>

<input id="password" type="password" class="form-control{{ $errors->has('password') ? ' is-invalid' : '' }}" name="password" required>

@if ($errors->has('password'))

<strong>{{ $errors->first('password') }}</strong>

</span>

@endif

</div>

<label>

<input type="checkbox" name="remember" {{ old('remember') ? 'checked' : '' }}> {{ __('Remember Me') }}

</label>

</div>

</button>

</a>

</div>

</form>

</div>

@endsection

Admin Home/Dashboard:-

Create the following directory resources/views/admin/ and in it we’ll add a new file home.blade.php and put following code in it:

resources/views/admin/home.blade.php

@extends('admin.layouts.app')

@section('content')
<div class="container">
    <div class="row justify-content-center">
        <div class="col-md-12">
            <div class="card">
                <div class="card-header">Admin Dashboard</div>

                <div class="card-body">
                    @if (session('status'))
                        <div class="alert alert-success">
                            {{ session('status') }}
                        </div>
                    @endif

                    You are logged in!
                </div>
            </div>
        </div>
    </div>
</div>
@endsection

@extends('admin.layouts.app')

@section('content')

<div class="card-header">Admin Dashboard</div>

@if (session('status'))

</div>

@endif

You are logged in!

</div>

@endsection

Create Admin Seeder

Generate a admin seeder file with following artisan command:

php artisan make:seeder AdminsTableSeeder

1	php artisan make:seeder AdminsTableSeeder

Lets open database/seeds/AdminsTableSeeder.php file created and populate admin user in it as following:

<?php
use Illuminate\Database\Seeder;
use Illuminate\Support\Facades\DB;

class AdminsTableSeeder extends Seeder
{
    /**
     * Run the database seeds.
     *
     * @return void
     */
    public function run()
    {
        
        DB::table('admins')->insert(array(
        	array(
				'name' => "Steve",
				'email' => 'steve@gmail.com',
				'password' => bcrypt('secret'),
        	),
        	array(
				'name' => "Laura",
				'email' => 'laura@gmail.com',
				'password' => bcrypt('secret'),
        	)
        ));

    }
}

<?php

use Illuminate\Database\Seeder;

use Illuminate\Support\Facades\DB;

class AdminsTableSeeder extends Seeder

{

/**

* Run the database seeds.

* @return void

public function run()

{

DB::table('admins')->insert(array(

array(

'name' => "Steve",

'email' => 'steve@gmail.com',

'password' => bcrypt('secret'),

array(

'name' => "Laura",

'email' => 'laura@gmail.com',

'password' => bcrypt('secret'),

)

));

}

Call Admin Seeder

Lets open database/seeds/DatabaseSeeder.php and call AdminsTableSeeder in run method as following:

database/seeds/DatabaseSeeder.php

public function run()
    {
        $this->call(AdminsTableSeeder::class);
    }

public function run()

{

$this->call(AdminsTableSeeder::class);

}

Run Admin Seeder

Lets open terminal and run seeder using following artisan command:

php artisan db:seed

1	php artisan db:seed

Start Application Server

Now we are ready to run our example so lets start the development server using following artisan command –

php artisan serve

1	php artisan serve

Now, open the following URL in browser to see the output –

http://localhost:8000/admin/login

Output:-

admin_login

http://localhost:8000/admin/

Output:-

admin_home

http://localhost:8000/register/

Output:-

user_register

http://localhost:8000/login/

Output:-

user_login

http://localhost:8000/home/

Output:-

user_dashboard

Laravel Fix 150 “Foreign key constraint is incorrectly formed” error In Migration

Leave a reply

Laravel “Foreign key constraint is incorrectly formed” Error

In Laravel 5.8, sometime when you generate a create table migration with a foreign key constraints, running migration may encounter 150 “Foreign key constraint is incorrectly formed” error. This is mainly happens when you take foreign key column of integer type instead of bigInteger, and this new laravel convention was causing this error. In Laravel 5.8, when you create a new table migration it will be generated with an ‘id’ column of bigInteger type instead of integer like old laravel version.

$table->bigIncrements('id');

1	$table->bigIncrements('id');

Instead of (in Laravel Old versions):

$table->increments('id');

1	$table->increments('id');

In that case we have to use bigInteger for foreign key column instead of an integer. So your code will look like this:
Example:-

Schema::create('posts', function (Blueprint $table) {
            $table->bigIncrements('id');
            $table->unsignedBigInteger('user_id');
            $table->string('title');
            $table->string('body');
            $table->timestamps();
            $table->foreign('user_id')->references('id')->on('users');
        });

Schema::create('posts', function (Blueprint $table) {

$table->bigIncrements('id');

$table->unsignedBigInteger('user_id');

$table->string('title');

$table->string('body');

$table->timestamps();

$table->foreign('user_id')->references('id')->on('users');

});

Or you could also use increments instead of bigIncrements for ‘id’ column in table creation of reference table.

$table->increments('id'); // ok

1	$table->increments('id'); // ok

instead of:

$table->bigIncrements('id'); // was the error.

1	$table->bigIncrements('id'); // was the error.

The main difference between Integer and BigInteger is of their size:
int => 32-bit
bigint => 64-bit

Laravel Clear View Cache

Leave a reply

Laravel Clear View Cache

In this Laravel Clear View Cache tutorial, I’ll show you how to clear view cache in laravel application. You’ll learn to clear view cache using artisan command as well as learn to clear laravel view cache on shared host from browser.

Clear View Cache Using Artisan Command

To clear compiled view files cache in laravel use the php artisan view:clear artisan command as given below :

php artisan view:clear

1	php artisan view:clear

Clear View Cache On Shared Host

Most of the times in shared hosting servers we don’t have SSH access to the server. In that case, to clear laravel view cache we have define a route in our application’s routes/web.php file that invoke the laravel clear view cache command. This way we can clear view cache by accessing specific routes in the browser.

 Route::get('/view-clear', function() {
     $exitCode = Artisan::call('view:clear');
     return 'View cache cleared';
 });

Route::get('/view-clear', function() {

$exitCode = Artisan::call('view:clear');

return 'View cache cleared';

});

Laravel Clear config cache

Leave a reply

Laravel Clear Config Cache

In this Laravel Clear config Cache tutorial, I’ll show you how to clear config cache in laravel application. You’ll learn to clear config cache using artisan command as well as learn to clear laravel config cache on shared host from browser.

Clear Config Cache Using Artisan Command

To clear config cache in laravel use the php artisan config:cache artisan command as given below :

php artisan config:cache

1	php artisan config:cache

Laravel Clear Config Cache On Shared Host

Most of the times in shared hosting servers we don’t have SSH access to the server. In that case, to clear laravel config cache we have define a route in our application’s routes/web.php file that invoke the laravel clear config cache command. This way we can clear config cache by accessing specific routes in the browser.

 Route::get('/config-cache', function() {
     $exitCode = Artisan::call('config:cache');
     return 'Config cache cleared';
 });

Route::get('/config-cache', function() {

$exitCode = Artisan::call('config:cache');

return 'Config cache cleared';

});

Laravel Clear route cache

Leave a reply

Laravel Clear Route Cache

In this Laravel Clear Route Cache tutorial, I’ll show you how to clear route cache in laravel application. You’ll learn to clear route cache using artisan command as well as learn to clear laravel route cache on shared host from browser.

Clear Route Cache Using Artisan Command

To clear route cache in laravel use the php artisan route:clear artisan command as given below :

php artisan route:clear

1	php artisan route:clear

Laravel Clear Route Cache On Shared Host

Most of the times in shared hosting servers we don’t have SSH access to the server. In that case, to clear laravel route cache we have define a route in our application’s routes/web.php file that invoke the laravel clear route cache command. This way we can clear route cache by accessing specific routes in the browser.

 Route::get('/route-cache', function() {
     $exitCode = Artisan::call('route:cache');
     return 'Routes cache cleared';
 });

Route::get('/route-cache', function() {

$exitCode = Artisan::call('route:cache');

return 'Routes cache cleared';

});

Laravel Clear App Cache

Leave a reply

Laravel Clear App Cache

In this Laravel Clear App Cache tutorial, I’ll show you how to clear app cache in laravel application. You’ll learn to clear app cache using artisan command as well as learn to clear laravel app cache on shared host from browser.

Clear App Cache Using Artisan Command

To clear laravel application cache use the php artisan cache:clear artisan command as given below :

php artisan cache:clear

1	php artisan cache:clear

Clear App Cache On Shared Host

Most of the times in shared hosting servers we don’t have SSH access to the server. In that case, to clear laravel application cache we have define a route in our application’s routes/web.php file that invoke the laravel clear application cache command. This way we can clear application cache by accessing specific routes in the browser.

 Route::get('/clear-cache', function() {
     $exitCode = Artisan::call('cache:clear');
     return 'Application cache cleared';
 });

Route::get('/clear-cache', function() {

$exitCode = Artisan::call('cache:clear');

return 'Application cache cleared';

});