Massassignmentexception In Model.Php Laravel 5 Tutorial

If you would like to know more about Laravel, watch our Laravel live lesson with Isaac Castillo, teacher of our recent Laravel course.

In the previous part, we’ve bootstrapped our Laravel CRUD application by creating the database, some controllers, basic routes and simple views. In this part, we’ll wrap things up and implement proper CRUD.

If you’d like to follow along through this interactive walk through Laravel’s docs, please catch up by reading the first part now.

Creating A Record

Continuing right where we left off, let’s create the page where we’ll actually perform this action. In our , let’s return a view like this:

And now, in our views directory, let’s create , and enter some starter content:

At this point, we could manually create a form, but Laravel offers a package to lighten this load for us – Illuminate/Html. Let’s pull that in quickly by running the following command:

Now, inside our file, let’s add the service provider to the list:

Let’s add the aliases:

We can now easily create a form in our file. Let’s go ahead and do that using the form facade and blade syntax:

Check out this screenshot of our view so far.

One important thing to note here is that I’ve specified the route on which we will POST to, according to our resourceful routes list. We’ll use the store method to process the data, so let’s head back to our , and start processing that data.

Let’s turn our heads to requests in Laravel.

The Request facade will grant you access to the current request that is bound in the container.

We can obtain our request instance in two ways, according to the documentation. Let’s stick with the dependency injection method. Our method should now look like this:

Now, we can dump out the information to see what gets posted. We’ll use the helper function, , which is included by default in Laravel. It combines Symphony’s VarDupmer component, and the PHP function. Add the following to the method:

Now submit the empty form, and you’ll see the data. Go back and fill in some dummy data in the form, and you’ll see the request updated. If we’re not interested in any validation, then saving the new task to the database is easy. In the docs for Eloquent, we’ll notice that we can call the method to create a new row in our table. Let’s do that by adding the following to our method. We’ll also redirect back to where we came from:

We’re ready to create a new task now. Let’s go ahead and enter some dummy data and submit it. Uh oh… there’s a . Laravel by default prevents mass assignment, which is a good thing. This just means that we have to declare which fields are mass-assignable. I suggest you read up on this, but here’s what our updated model will look like:

Now, let’s try to add our task again. If we were successful, we should be redirected back to where we came from, i.e. the “create task” page. There’s no indication right now as to whether the task was successfully added, but let’s check the database through the command line:

We should see the table returned with our new entry. Sweet! What about success messages and validation? Let’s first validate our input, to make sure all fields are required. Laravel ships with a really easy-to-use Validator class, and a quick read should have us going in no time. We’re validating in our controller, so let’s look at that section. Let’s validate our input by adding this to the beginning of the method:

Notice now that if we leave out any of our input, the rest of our method doesn’t execute, and we remain on the page with whatever input has already been entered. Laravel will automatically throw an error, which we can access in our blade template. Let’s insert the following snippet above our form:

Now, we’ll see the errors neatly written out for us.

What about a success message? Well, if our validator passes, the rest of our code will execute, and we can redirect back with a Session flash message. Update the method to create a new flash message:

Now, we can add this to our blade template:

Here’s what we should see.

We’re now validating and adding tasks, as well as passing data back to the view for output. Excellent. We still need a way to actually see our records.

Reading Records

Back in our method, we can now output all tasks that we’ve created so far. Add this to the method:

We can access and output the tasks like this:

Here’s a screenshot for the index view.

Let us now figure out how we’re going to display a single record. In this current app, it’s probably not necessary because we’re already outputting all the information, but we’ll do it anyway. If we look at our routes list, it’s apparent that the route is the way to go. It accepts a wildcard in the URL, and for our app, we’ll use the ID of the task. As before, we’ll create a file and extend our master layout:

Now, let’s update our method:

If we navigate to a URL with a random wildcard – – we should see our dummy template. Let’s actually fetch the correct task. Using Eloquent, we can search for a record with the matching ID, and if none are found, we’ll throw a which we can catch. If the record is found, we can access it in our view. Here’s the updated method:

Now in our view, we can output the record properly like this:

Navigate to , and you should see the output.

Back in our view, we can now output the links to each individual task:

Notice that we passed in the correct wildcard based on the task ID. You should now be able to click through nicely! Let’s move on to editing.

Updating A Record Using Form-Model Binding

By now, you probably realize how easy it is to get a new view ready for our RESTful app. It’s no different this time, so we’ll create the file, pull in the master layout, and link the corresponding controller method to it. Here’s the method:

And here’s the view to match:

If you look at the routes list, you’ll notice that the edit route also accepts a wildcard. We’ll be consistent and use the ID. Navigating to will display the dummy page, but let’s pull in the proper content. First of all, we can update all our “edit” links on the and views like this:

Notice again how we’re calling the correct route and passing in the corresponding wildcard. In our edit template, we’re going to want a similar form to the one we used to create a task, but it would be pretty useful if the form was already populated with the existing fields. Thanks to Laravel’s form-model binding, this is a piece of cake. We’ll copy over the create form, although a better practice would be to extract this to a partial of some sort. In any case, we’ll copy it over, and bind our model to it:

Notice how we’re using a PATCH request in the form to stay in line with our RESTful resource. Notice also how we are calling on the variable , binding it to the model, and referencing the ID which will be used to look up the table. This means that we have to pass in the correct task. In the , we can update the method to this:

Just like before, if an ID isn’t found, we’ll get the . We can, at this point, copy over our errors snippet again, but this isn’t very DRY at all. Don’t worry, we can fix that easily by leveraging partials. Blade allows us to reference any file by using the directive. First, let’s create a folder in our views directory called partials. In there, I’ll create a sub-directory called , and then a file called . Let’s copy over our errors snippet into this new file:

Now, we can reference it in any of our files like this:

We can now replace the original snippet in our template with this partial reference, and reference it in our edit template as well. The whole edit view should look like this now:

Here’s a screenshot of the view when we’re editing a task.

Let’s jump into our method now, which will receive the data from the form submission, and try to update our record. Like before, we’ll validate our input, and log the errors in our view if any exist. If validation passes, we’ll grab the input, update the task, save it, and redirect back with a success message. Here’s what the method looks like:

Try it out and see for yourself, it works! You can now create, read, and update records, but let’s cross the final hurdle.

Deleting A Record

Deleting a record RESTfully actually requires a DELETE request. You can get around this outside the controller with JavaScript, but that’s a bit beyond the scope of this article. If we view a single task, you’ll notice that I left a placeholder button there to delete it. We actually need to change this into a form that sends a DELETE request to the method, and handle the record deletion there. Here’s our updated show template incorporating the delete form:

Inside our , we can handle the request in the method, rounding off our RESTful controller. Once again, Eloquent makes this a breeze. We’ll fetch the associated record in the table, delete it, and redirect back to the task list:

At this point, let’s refactor our flash message into the master layout file so that it shows up on every template whenever a flash message is posted. We can remove it from the create and edit templates, and keep it only in the master layout like this:

Now, navigate to a task, and delete it. You’ll be redirected back to the task list with a flash message informing you that the task has successfully been deleted. Of course, your task list will be updated to match.

Wrapping Up

We’ve tapped into a lot of core concepts in this tutorial, and touched on a lot of neat Laravel functionality. By building up this CRUD application from scratch, we’ve gotten our taste buds wet with the Laravel workflow.

You should have a solid base and understanding to go on and build something yourself. I highly recommend checking out the various parts of the documentation to see what’s available, and just experimenting around as well. Use this as a building block, and get out there and show off your artisanal spirit. Feedback? Comments? Leave them below!

Continue learning about Laravel with our Laravel live lesson. One teacher, one lesson, followed by your Laravel questions.

I'm a web designer & developer from Trinidad & Tobago, with a degree in Mechanical Engineering. I love the logical side of the web, and I'm an artist/painter at heart. I endorse progressive web techniques, and try to learn something every day. I try to impart my knowledge as much as possible on my personal blog, I love food, I surf every weekend, and I have an amazing creative partnership with fellow mischief maker Elena. Together, we run SAYSM.

Today, Laravel 5 validation example is our main topic and let’s discuss it with some examples. Laravel is the fastest growing PHP MVC Framework, which provides us fluent API to build our web application and so we have also an API about Validate our form requests. If you are new to Laravel 5.4 then check out my this article Laravel 5.4 CRUD example from scratch

Content Overview

Step 1: Create project of Laravel 5 Validation

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

That command will install Laravel project, and next would be to edit the .env file to update your database credentials. Now go to terminal and type 

php artisan migrate

It will create two tables for us in the database.

Step 2: Make model Item.php of our project Laravel Validation

We need to validate our items table in our database, so we need to create one model and one migration for that. So, go to the terminal and type following command.

php artisan make:model Item -m

It will create both Item model as well as create_items_table.

Now, create a controller for Items table

php artisan make:controller ItemController --resource

It will create one controller file with the boilerplate in it.

Step 3: Generate database migrations for items table.

Now, we need to define the database fields in migration. So go to the database >> migrations >> create_migration_table and put the following code in it.

<?php // create_items_table use Illuminate\Support\Facades\Schema; use Illuminate\Database\Schema\Blueprint; use Illuminate\Database\Migrations\Migration; class CreateItemsTable extends Migration { /** * Run the migrations. * * @return void */ public function up() { Schema::create('items', function (Blueprint $table) { $table->increments('id'); $table->string('name'); $table->integer('price'); $table->timestamps(); }); } /** * Reverse the migrations. * * @return void */ public function down() { Schema::dropIfExists('items'); } }

Go to the terminal and type

php artisan migrate

Step 4: Make view file for Laravel Form Validation.

We need to create one view for forms, and then we need to submit that form to our server and check against our validation rules. If any of the rules does not fulfill our requirement, then we need to display an error.

Go to the routes file routes >> web.php and add the following code in it.

// web.php Route::get('items/add', 'ItemController@create'); Route::post('items/add', 'ItemController@store');

Go to the ItemController file and add the following code in create function.

// ItemController.php /** * Show the form for creating a new resource. * * @return \Illuminate\Http\Response */ public function create() { return view('itemForm'); }

Step 5: Made view on Laravel 5.4 Form Validation

I have created one view file inside resources >> views >> itemForm.blade.php

<!-- itemForm.blade.php --> <!DOCTYPE html> <html> <head> <meta charset="utf-8"> <title>Item Validation Form</title> <link rel="stylesheet" href="{{asset('css/app.css')}}"> </head> <body> <div class="container"> <form method="post" action="{{url('items/add')}}"> {{csrf_field()}} <div class="form-group"> <label for="itemName">Item Name:</label> <input type="text" class="form-control" id="itemName" name="name"> </div> <div class="form-group"> <label for="price">Price:</label> <input type="text" class="form-control" id="price" name="price"> </div> <button type="submit" class="btn btn-default">Submit</button> </form> </div> </body> </html>

Step 6: Mass Assignment Exception

Possible Errors

Mass assignment exception in Laravel

Possible Solutions

Go to your database table related model and put the following code in it. In my case,  it is an Item.php

// Item.php protected $fillable = ['name', 'price'];

This will resolve  Mass assignment exception

If you do not define the table name in Model, then Laravel will assume that you have created table “items” because my model name is Item.php. So Laravel always gives table name plural and model name singular. Perfect naming convention in Object Orientated Relational Mapping.

Step 7: Make validation rule in ItemController.php file. 

Now we are going to define very simple validation rule against our form fields. So go to the ItemController.php file and put the following code in store function.  It will automatically redirect to form page if any of the rules gets failed.

Controller class of Laravel is by default provides us validate method, which takes two arguments.

  1. $request
  2. Our validation rules array

If any of the rules are failed, then It will store an array of the errors and puts into flash session. So in form page, we can get that errors object by calling $errors->all()

So we need to display error in itemForm.blade.php

<!-- itemForm.blade.php --> <!DOCTYPE html> <html> <head> <meta charset="utf-8"> <title>Item Validation Form</title> <link rel="stylesheet" href="{{asset('css/app.css')}}"> </head> <body> <div class="container"> <br /> @if ($errors->any()) <div class="alert alert-danger"> <ul> @foreach ($errors->all() as $error) <li>{{ $error }}</li> @endforeach </ul> </div> @endif @if (\Session::get('success')) <div class="alert alert-success"> <p>{{ \Session::get('success') }}</p> </div> @endif <form method="post" action="{{url('items/add')}}"> {{csrf_field()}} <div class="form-group"> <label for="itemName">Item Name:</label> <input type="text" class="form-control" id="itemName" name="name"> </div> <div class="form-group"> <label for="price">Price:</label> <input type="text" class="form-control" id="price" name="price"> </div> <button type="submit" class="btn btn-default">Submit</button> </form> </div> </body> </html>

Now go to the form page by typing URL: http://localhost:8000/items/add 

Do not fill any data and submit the form. You will get some errors like this.


This is flash session so after refreshing the page; validation errors are gone. If everything is correct, then you can see the form page that Item is created.

Step 8: Form Request Validation In Laravel 5.4

For more complex validation scenarios, you may wish to create a “form request.” Form requests are custom request classes that contain validation logic. Create a form request class, use the  Artisan CLI command:

php artisan make:request FormRequest

Now, we will use the second example, where we do not use validate() function provided by laravel in the controller, we just pass this FormRequest class as a Dependency Injection.

First, we make another controller called FormController

php artisan make:controller FormController --resource

We need to create two more routes for out application.

// web.php Route::get('formitem/add', 'FormController@create'); Route::post('formitem/add', 'FormController@store');

Now, we need to create one another view called RequestForm.blade.php

<!-- RequestForm.blade.php --> <!DOCTYPE html> <html> <head> <meta charset="utf-8"> <title>Item Validation Form</title> <link rel="stylesheet" href="{{asset('css/app.css')}}"> </head> <body> <div class="container"> <br /> @if ($errors->any()) <div class="alert alert-danger"> <ul> @foreach ($errors->all() as $error) <li>{{ $error }}</li> @endforeach </ul> </div> @endif @if (\Session::get('success')) <div class="alert alert-success"> <p>{{ \Session::get('success') }}</p> </div> @endif <form method="post" action="{{url('formitem/add')}}"> {{csrf_field()}} <div class="form-group"> <label for="itemName">Item Name:</label> <input type="text" class="form-control" id="itemName" name="name"> </div> <div class="form-group"> <label for="price">Price:</label> <input type="text" class="form-control" id="price" name="price"> </div> <button type="submit" class="btn btn-default">Submit</button> </form> </div> </body> </html>

Code the FormController function to return a RequestForm view.

// FormController.php /** * Show the form for creating a new resource. * * @return \Illuminate\Http\Response */ public function create() { return view('RequestForm'); }

Now, we just need to pass FormRequest as a dependency to the store function of the FormController class.

<?php namespace App\Http\Controllers; use Illuminate\Http\Request; use App\Item; use App\Requests\FormRequest; class FormController extends Controller { /** * Display a listing of the resource. * * @return \Illuminate\Http\Response */ public function index() { // } /** * Show the form for creating a new resource. * * @return \Illuminate\Http\Response */ public function create() { return view('RequestForm'); } /** * Store a newly created resource in storage. * * @param \Illuminate\Http\Request $request * @return \Illuminate\Http\Response */ public function store(FormRequest $request) { Item::create([ 'name' => $request->get('name'), 'price'=> $request->get('price') ]); return back()->with('success', 'You have just created one item'); } /** * Display the specified resource. * * @param int $id * @return \Illuminate\Http\Response */ public function show($id) { // } /** * Show the form for editing the specified resource. * * @param int $id * @return \Illuminate\Http\Response */ public function edit($id) { // } /** * Update the specified resource in storage. * * @param \Illuminate\Http\Request $request * @param int $id * @return \Illuminate\Http\Response */ public function update(Request $request, $id) { // } /** * Remove the specified resource from storage. * * @param int $id * @return \Illuminate\Http\Response */ public function destroy($id) { // } }

Now, only remaining the thing is that to code the FormRequest file, which is in the app >> Http >> Requests >> FormRequest.php Fill the array of rules function with the validation field.

<?php // FormRequest.php namespace App\Http\Requests; use Illuminate\Foundation\Http\FormRequest; class FormRequest extends FormRequest { /** * Determine if the user is authorized to make this request. * * @return bool */ public function authorize() { return false; } /** * Get the validation rules that apply to the request. * * @return array */ public function rules() { return [ 'name' => 'required', 'price' => 'required' ]; } }

Now, go to the following URL: http://localhost:8000/formitem/add

Submit the data without fill the form, and you will get the errors and form will not submit.

For more Validation rules, you can find on official Laravel website.

I have put Laravel 5 validation example from scratch code on GitHub

Github Link:

Steps to use Github code

  1. Clone the repo in your local.
  2. Go to the root of the project and run command “composer update
  3. Edit .env file and use your MySQL database credentials.
  4. Run the command “php artisan migrate
  5. Now, we need to bootstrap Laravel server so run “php artisan serve
  6. If now go to this URL: http://localhost:8000/items/add

If you still have doubt in this tutorial, then ask in the comment below, I am happy to help you out.

Leave a Comment


Your email address will not be published. Required fields are marked *