We are giving away our first UI kit for free. It includes over 130 sections, built with TailwindCSS, for your awesome projects.

All the sections are fully responsive and available in HTML, VueJS, and React.
You can use them on unlimited personal and commercial projects.

If you were watching the virtual 72nd Primetime Emmy Awards last night, you no doubt caught the debut of a new trailer for WandaVision, the first standalone series to be released in Phase Four of the MCU. The studio offered a sneak peek last year during D23 Expo 2019, Disney’s annual fan extravaganza. Lacking any actual footage, that teaser was just snippets of The Dick van Dyke Show interspersed with snippets of the Scarlet Witch (Elizabeth Olsen) and Vision (Paul Bettany) from the various MCU films. At the time, I was skeptical of the concept, but this new trailer is quite promising and gives me hope that Marvel can pull it off.

WandaVision is meant to be a kind of sitcom/epic superhero mashup, with Kat Dennings reprising her role as Darcy from the Thor films, alongside Randall Park reprising his Ant Man and the Wasp role as FBI agent Jimmy Woo. Kathryn Hahn (Crossing Jordan) will play a “nosy neighbor,” and Teyonah Parris (Mad Men) plays a grown-up Monica Rambeau, daughter of Carol Danvers’ BFF Maria Rambeau, introduced in Captain Marvel. Within the MCU timeline, it takes place after the events of Avengers: Endgame, and its events will directly tie in to Doctor Strange in the Multiverse of Madness, currently slated for a 2022 release. 

Per the official description: “WandaVision will follow the story of Elizabeth Olsen and Paul Bettany’s superhero characters, the Scarlet Witch and Vision. The series is a blend of classic television and the Marvel Cinematic Universe in which Wanda Maximoff and Vision—two super-powered beings living idealized suburban lives—begin to suspect that everything is not as it seems.”

During last fall’s New York Comic-Con, Tom King mentioned that the show would draw on the 2016 comic book limited series by King and Gabriel H. Walta, The Vision. In that storyline, Vision “creates” a wife and two children and settles into a seemingly idyllic suburban life in Washington, DC—but things soon take a darker turn. (There’s also a comics storyline in which Wanda creates a world where everyone gets their heart’s desire, so reality-warping is certainly within her canonical powers.) The studio also released a few set photos earlier this year that confirmed rumors that WandaVision would feature the live-action debut of S.W.O.R.D. (the Sentient World Observation and Response Department), a subdivision of S.H.I.E.L.D. charged with handling alien threats to Earth.

The trailer opens in the style of a wholesome 1950s family sitcom as “Twilight Time” by The Platters plays in the background. (Side note: I will forever be creeped out by this song after it was used in the 1998 The X-Files episode “Kill Switch,” co-written by none other than William Gibson.) ”This is our home now. I want us to fit in,” Wanda tells Vision, and voila! He suddenly has a more human appearance, just in time for dinner with the neighbors. But they find they can’t answer even the simplest personal questions: when they moved in, where they moved from, and of course, why they don’t have any children (it is the 1950s).

That’s the cue to shift into different eras of classic television in succession, including a brief glimpse of Monica Rambeau. It looks like showrunner Jac Schaeffer and the writing team are having a lot of fun with the concept, and that lighthearted energy dominates the trailer. “We are an unusual couple, you know,” Wanda says as we briefly shift back to the 1950s at the end. “Oh, I don’t think that was ever in question,” Vision replies. And it looks like this will be a most unusual series.

There’s no official release date yet, but WandaVision is expected to debut on Disney+ in December 2020. (The original plan was for a spring 2021 release, so we’re getting it a bit earlier than expected.)

Listing image by YouTube/Disney+

Apple’s latest mobile operating system introduces two new options that will delight anyone who doesn’t want to be wedded to Apple’s web browser and email apps. You can now set your own default web browser and email apps, but not every app supports the feature—not even Gmail.

I’ll explain.

As previously noted, app developers must update their apps in order to allow them to be considered as a potential “default” web browser or email client in iOS 14. Since Apple didn’t reveal last Wednesday’s iOS 14 launch was going to take place until last Tuesday, it’s no surprise that not every email client nor web browser has already been updated with the ability to be set as your default.

For example, you can set Edge, Chrome, or Firefox as a default browser, but not Brave (yet). For email apps, Hey, Spark, and Outlook can all be set as your default email application in iOS 14, but not… Gmail. Or not yet, which is surprising given that Chrome can be set as a default browser. (You’d think the updates that permitted this option would have gone hand-in-hand, but here we are.)

If you tap on an email link in Messages or Safari with Gmail as the only email client installed on your iOS 14 iPhone, you’ll see this prompt:

If you would rather not restore Mail, thanks, you can now either wait for Google to update Gmail to allow it to be set as a default email app—which it will surely do at some point soon—or you can use the following workaround.

Simply switch to using Chrome as your default web browser (if you haven’t already). When you tap on email links within the iOS version of Google’s browser, it’ll launch the Gmail app (if you also have that installed). I just tried it using one of the email links in my weekly Tech 911 column and it worked perfectly.

So, yes, you’ll have to use a Google product to be able to effectively use a Google product within iOS 14 (for now), and this trick will only work in Chrome, and not with any other email links you encounter on your iPhone or iPad. Still, it’s something; it actually confused me at first, as I thought that it meant the “Gmail as a default email client” feature had already rolled out—perhaps I had set it up and forgot? Nope. It’s just a Chrome quirk, though a welcome one.

KISSIMMEE, FL—Biden made a campaign stop in Florida this week to celebrate Hispanic Heritage Month and reach out to his favorite voters: the Hispanics. In an effort to appeal to the voters, he performed a cultural celebration of Hispanic heritage by dancing in a sombrero and fake mustache, eating a burrito, and firing a pistola in the air.

“Hey there, fellow Latinx!” Biden said. “Before I begin, I would like to show you my Mexican celebration dance which I will perform to the tune of ‘La Cucaracha,’ Enjoy!” 

Biden then turned to a cassette player on the podium and pressed play. As the well known Spanish folk song began to play, Biden performed a dance in his traditional Mexican clothing he had recently purchased at a Spirit Halloween Store. Halfway through the performance, he yelled out, “You kids ain’t seen nothing yet! Watch this!” 

Biden then began to hop around and shoot an old fashioned Mexican pistola into the air. When he was finished, he sat down on the stage and ate a giant burrito for about 20 minutes.

When he was finished, the hall erupted in applause as the audience of several individuals stood on their feet to cheer the performance.

Biden knew he had nailed the performance, and that the Hispanic vote was in the bag. He was put back on ice in the basement until he is needed to go win over other ethnic groups.

If you are new in Laravel 8 and looking for a step by step tutorial for Laravel 8 CRUD example app then this post will help you to learn how to make a complete CRUD application using Laravel 8. Before starting we have to check our system requirement is okay to use Laravel 8. The Laravel 8 minimum requirements are listed below so that you can confirm either your system is okay or not to install Laravel 8 project for making a Laravel 8 CRUD application.

Laravel 8 requirements

• PHP >= 7.3
• BCMath PHP Extension
• Ctype PHP Extension
• Fileinfo PHP Extension
• JSON PHP Extension
• Mbstring PHP Extension
• OpenSSL PHP Extension
• PDO PHP Extension
• Tokenizer PHP Extension
• XML PHP Extension

Steps for making Laravel 8 CRUD

• Step 01: Install Laravel 8
• Step 02: Database Configuration
• Step 03: Make model & migration
• Step 04: Make controller
• Step 05: Define routes
• Step 06: Make views

Step 01: Install Laravel 8

First, install a fresh new Laravel 8 project. To do that, open your command prompt and run the artisan command below. This command will install and create a new Laravel 8 project for you. Before running this command make sure you have a stable internet connection. This command will take some times depends on your internet connection speed.

composer create-project laravel/laravel laravel8-project 8.0

N.B: Replace the laravel8-project with your project name. According to this name, a folder will create in your project directory.

Step 02: Database Configuration

Now create a database in MySQL via phpMyAdmin or other MySQL clients which you. Now open .env file from Laravel 8 project and update the database details.

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

Here laravel8 is our database name. If your database name different then update it and save. Our project creation finished and the database is ready to use.

Step 03: Make model & migration

We will make a contact list Laravel 8 CRUD example application. So that we need a contacts table in our database. Here we do not create the table manually. Here we use Laravel migration. When we’ll run our migration that will make the table for us. Run the command in your terminal.

php artisan make:model Contact -m

This command will make a Contact.php model class file into the app/Models directory of our Laravel 8 project and a migration file will be created into the database migrations directory.

Now open the migration file from database/migrations directory of your Laravel 8 project and replace the code with below.

<?php

use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class CreateContactsTable extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('contacts', function (Blueprint $table) {
            $table->bigIncrements('id');
            $table->string('name');
            $table->string('email');
            $table->string('phone');
            $table->timestamps();
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::dropIfExists('contacts');
    }
} 

Our migration file is ready. Now run the migration with this command. This command will create our tables in our database.

php artisan migrate

Step 04: Make controller

In our controller, all our business login will be coded to make Laravel 8 CRUD system. To make the controller run the command.

php artisan make:controller ContactController

By this command, a file will be created in app/Http/Controllers name with ContactController.php. Write the code below in the ContactController.php

<?php namespace App\Http\Controllers;

use App\Contact;
use Response;
use App\Http\Requests;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;

class ContactController extends Controller
{

    public function index()
    {
        $data = Contact::orderBy('id','desc')->paginate(10)->setPath('contacts');
        return view('admin.contacts.index',compact(['data']));
    }

    public function create()
    {
        return view('admin.contacts.create');
    }

    public function store(Request $request)
    {
        $request->validate([
         'name' => 'required',
         'email' => 'required|email',
         'phone' => 'required'
        ]);

        Contact::create($request->all());
        return redirect()->back()->with('success','Create Successfully');
    }

    public function show($id)
    {
       $data =  Contact::find($id);
       return view('admin.contacts.show',compact(['data']));
    }

    public function edit($id)
    {
       $data = Contact::find($id);
       return view('admin.contacts.edit',compact(['data']));
    }

    public function update(Request $request, $id)
    {
        $request->validate([
         'name' => 'required',
         'email' => 'required|email',
         'phone' => 'required'
        ]);

        Contact::where('id',$id)->update($request->all());
        return redirect()->back()->with('success','Update Successfully');
        
    }

    public function destroy($id)
    {
        Contact::where('id',$id)->delete();
        return redirect()->back()->with('success','Delete Successfully');
    }

}

Step 05: Define routes

Open the web.php file from routes folder and write the routes like below.

Route::resource('contacts','ContactController');

Here we are using the Laravel resource route which will make all our required routes that are needed for Laravel 8 CURD example app.

Step 06: Make views

Here is the final part, We need some forms and HTML markup to show our records and data insert, update. Let’s make those views. Create a folder inside views folder name with contacts so that all views are related to contact CRUD will be in the same folder and organized.

We need the Laravel H package for making HTML form easily. Install it by the composer.

composer require haruncpi/laravel-h

Create an index.blade.php to show all our records from the database.

@extends('layout') 
@section('content')
<div class="col-md-12">

    <div class="table-responsive">
        <table class="table table-bordered table-condensed table-striped">
            <thead>

                <th>ID</th>
                <th>NAME</th>
                <th>EMAIL</th>
                <th>PHONE</th>
                <th>ACTION</th>
            </thead>

            <tbody>
                @foreach($data as $row)
                <tr>

                    <td></td>
                    <td></td>
                    <td></td>
                    <td></td>

                    <td>
                        <a href="" class="btn btn-primary">Edit</a>

                        <form action="" method="post">
                            @csrf @method('DELETE')
                            <button class="btn btn-danger" type="submit">Delete</button>
                        </form>

                    </td>
                </tr>
                @endforeach
            </tbody>

        </table>
    </div>
    <div>
        <?php echo $data->render(); ?>
    </div>
</div>

@endsection

Create a create.blade.php file for insert data.

@extends('layout')

@section('content')
{!! F::open(['action' =>'ContactController@store', 'method' => 'POST'])!!}
    
    <div class="col-md-6">
        
			 <div class="form-group required">
				{!! F::label("NAME") !!}
				{!! F::text("name", null ,["class"=>"form-control","required"=>"required"]) !!}
			</div>

			 <div class="form-group required">
				{!! F::label("EMAIL") !!}
				{!! F::text("email", null ,["class"=>"form-control","required"=>"required"]) !!}
			</div>

			 <div class="form-group required">
				{!! F::label("PHONE") !!}
				{!! F::text("phone", null ,["class"=>"form-control","required"=>"required"]) !!}
			</div>

   
        <div class="well well-sm clearfix">
            <button class="btn btn-success pull-right" title="Save" type="submit">Create</button>
        </div>
    </div>
 
{!! Form::close() !!}
@endsection

Create an edit.blade.php file to edit data.

@extends('layout')

@section('content')
    {!! F::open(['action' =>['ContactController@update',$data->id], 'method' => 'PUT'])!!}
    
        <div class="col-md-6">

            
			 <div class="form-group required">
				{!! F::label("NAME") !!}
				{!! F::text("name", $data->name ,["class"=>"form-control","required"=>"required"]) !!}
			</div>

			 <div class="form-group required">
				{!! F::label("EMAIL") !!}
				{!! F::text("email", $data->email ,["class"=>"form-control","required"=>"required"]) !!}
			</div>

			 <div class="form-group required">
				{!! F::label("PHONE") !!}
				{!! F::text("phone", $data->phone ,["class"=>"form-control","required"=>"required"]) !!}
			</div>



            <div class="well well-sm clearfix">
                <button class="btn btn-success pull-right" title="Save" type="submit">Update</button>
            </div>
        </div>
        
    {!! Form::close() !!}
@endsection

Now our Laravel 8 CRUD app is ready to use. To test the Laravel 8 CRUD app operation first, run the server by php artisan serve command and then open your browser and browse http://localhost:8000/contacts

Hope this step by step tutorial on Laravel 8 CRUD app will help you to make your won CRUD system using Laravel 8. If you find this tutorial helpful then please share this with others.

How do I fix this?

The problem here is that Laravel has no idea where to look for your controller, so all we have to do is let it know! There are 3 ways you can accomplish this:

• Add the namespace back manually so you can use it as you did in Laravel 7.x and before
• Use the full namespace in your route files when using the string-syntax
• Use the action syntax (recommended)

Adding the namespace manually

This is fairly simple. Go into your RoutesServiceProvider.php file and you’ll see the following:

All you need to do is add the following three lines to this file and Laravel will go back to using the default namespace as in Laravel 7.x:

What did we just do? We declared the $namespace variable with the default Namespace for our controllers and told laravel to use that for our web and api routes.

If you try to run your app again, everything should be working.

Using the full namespace

This one involves changing all your route declarations, but the idea is simple: prepend your controller names with their namespace. See the following example for our PostsController inside the app/Http/Controllers folder.

If you try again, everything should be running smoothly.

Using the Action Syntax

This is the alternative I personally recommend as I find it more typo-proof and in my experience provides better IDE support as we are explicitly telling the code which class to use. Instead of using our usual string syntax, we can use the action syntax where we specify the class and method to use in an array:

Notice here we are not passing the PostsController within quotes but rather PostsController::class, which internally will return ‘App\Http\Controllers\PostsController’. The second value in the array is the method to call within that controller, meaning: “In PostsController.php call the ‘all’ method.

Again, if you try to run your app again, everything should be up and running.

Closing Remarks

By now, your app should be up and running again. If not, please feel free to ask for help. Everyone in the community is eager to give a hand.

Whether you added the namespace manually, specified the full namespace in your routes, or went with the action syntax, what you just did is tell Laravel in which namespace your controllers actually are, so now it actually knows where to look.

If you liked what you read or want to learn more cool stuff related to Laravel, you can follow me on Twitter, where I post about coding, entrepreneurship, and living a better life.