How To Solve The Page Expired 419 Error In Laravel

In this tutorial I will give you solution of page expired 419 error in laravel.

Many times we faced “The page has expired due to inactivity. Please refresh and try again”. error in Laravel. This problem is caused by the csrf_token. So, below i have added 2 solutions of this error check and apply as per your requirments.

Read More : How To Solve The Page Expired 419 Error In Laravel

Read More : How To Generate QRcode In Laravel

Thanks for reading !!

#laravel page expired error #419 error in laravel #how to solved 419 error in laravel #laravel #error

Seamus  Quitzon

Seamus Quitzon


Php how to delete multiple rows through checkbox using ajax in laravel

First thing, we will need a table and i am creating products table for this example. So run the following query to create table.

CREATE TABLE `products` (
 `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
 `name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
 `description` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
 `created_at` timestamp NULL DEFAULT CURRENT_TIMESTAMP,
 `updated_at` datetime DEFAULT NULL,

Next, we will need to insert some dummy records in this table that will be deleted.

INSERT INTO `products` (`name`, `description`) VALUES

('Test product 1', 'Product description example1'),

('Test product 2', 'Product description example2'),

('Test product 3', 'Product description example3'),

('Test product 4', 'Product description example4'),

('Test product 5', 'Product description example5');

Now we are redy to create a model corresponding to this products table. Here we will create Product model. So let’s create a model file Product.php file under app directory and put the code below.


namespace App;

use Illuminate\Database\Eloquent\Model;

class Product extends Model
    protected $fillable = [

Step 2: Create Route

Now, in this second step we will create some routes to handle the request for this example. So opeen routes/web.php file and copy the routes as given below.


Route::get('product', 'ProductController@index');
Route::delete('product/{id}', ['as'=>'product.destroy','uses'=>'ProductController@destroy']);
Route::delete('delete-multiple-product', ['as'=>'product.multiple-delete','uses'=>'ProductController@deleteMultiple']);

#laravel #delete multiple rows in laravel using ajax #laravel ajax delete #laravel ajax multiple checkbox delete #laravel delete multiple rows #laravel delete records using ajax #laravel multiple checkbox delete rows #laravel multiple delete

Kole  Haag

Kole Haag


How to Solve: Nova Spatie 422 error "This disk is not configured as a backup disk"

Spatie’s Laravel Components are surely known to most and are great helpers to build any kind of Laravel application or website. I’ve been using the Spatie’ Laravel Backup component on my projects. With my recent shift to Laravel Nova on my new project, I’ve started to look at the related Nova component. It worked fine, once I got over some initial trouble.

Once completed installing Spatie Backups, I’ve run a

artisan backup:runto see if it works: local backups worked as to expect and are considered “healthy”:

As usual, I’ve continued to set up B2 as my cloud filesystem and backup solution. The setup of B2 as your Laravel backup system is easy and done in a few minutes.

After this, I’ve installed the Nova component for Laravel backups using composer:

composer require spatie/nova-backup-tooland configured the tools as explained. While checking the Nova admin interface I’ve noticed that it isn’t working as expected. The loading icons kept spinning without any data showing up:

After checking the Firefox browser console I’ve noticed an odd HTTP-422 request with this message:

The message contained an error message, which I’ve not seen on the admin-panel:

This disk is not configured as a backup disk.

After some research in the code, I’ve found out this error was caused by a small misconfiguration in the config/backup.php file:

Once I’ve set this to B2 the backup overview & creation worked as expected:

I’m solving & documenting random issues I encounter in the daily coder life. Besides this, I’m writing about business and my side-projects. If you are interested in either of them, subscribe to my newsletter!

#laravel-nova #laravel-framework #laravel-tips-and-tricks #error-handling #coding #programming #computers #error-messages-in-laravel

Seamus  Quitzon

Seamus Quitzon


5 Laravel’s Hidden Gems

1. Stop on first validation error

By default, Laravel will check for all validation rules and return a list of errors. But if you want to stop this process after first validation failure, that’s how you can achieve it

    'title' => 'bail|required|unique:posts|max:255',
    'body' => 'required',

2. Find many

Most of us developers have used Eloquent’s method find to search for one specific id, but do you know we can pass multiple ids to find which will return a collection.

// Will return Eloquent Model
$user = User::find(1);
// Will return Eloquent Collection
$users = User::find([1,2,3]);

3. Relationship but with condition

Some times we need to apply where on relationships, instead of calling relationship and then chaining where we can achieve it by following:

// app/Post.php model
public function comments()
    return $this->hasMany(Comment::class);
public function approved_comments()
    return $this->hasMany(Comment::class)->where('approved', 1);

4. Rename pivotal table

In pivot table, if you want to rename pivot to some thing else, this can be done by following code:

public function podcasts() {
return $this->belongsToMany('App\Podcast')
// Then somewhere in Controller...
$podcasts = $user->podcasts();
foreach ($podcasts as $podcast) {
// instead of $podcast->pivot->created_at ...
echo $podcast->subscription->created_at;

#laravel #php #find many laravel #prepare for validation laravel #relationship but with condition laravel #rename pivotal table laravel #stop on first validation error laravel

Exceptions and Exception Handling in C#

C## and the .NET CLR use exceptions to show that an error condition has arisen during program execution. C## programs are under constant threat of running into some sort of problem. As a program’s complexity grows, the probability that something odd would happen during its execution also gets higher.

In this blog, we will go through the basics of Exception and Exception handling. We will also look at how we can achieve exception handling using try, catch, and finally blocks and how to create your own custom exceptions.


The errors which we are getting at the run time of the application is called an exception.

If any exception is coming into our application then the application is abnormally terminated. The Application is not considered as a good application if any exception is coming and it is not handled.

Every time when we are developing an application and it got successfully build without any errors. Then this happens


For that, it is good practice to use exception handling.

#c# #exception #exception handling #exception handling best practices #c++