How to display validation errors in Laravel?
Jul 27, 2025 am 04:13 AMLaravel automatically provides the $errors variable in Blade templates to display validation errors. 2. Use $errors->first('field') to show the first error for a specific field, and old('field') to repopulate input values. 3. Display all errors at the top of the form using $errors->any() and $errors->all() within a loop. 4. Apply conditional CSS classes like 'has-error' to highlight invalid fields based on $errors->has('field'). 5. When using Form Requests, Laravel automatically handles validation and redirects with errors if it fails. 6. For manual validation, use Validator::make() and return redirect()->back()->withErrors($validator)->withInput() to make errors available in the view. 7. Laravel automatically returns JSON error responses for AJAX requests, and the $errors variable is always shared in views, making validation error handling simple and seamless.
In Laravel, displaying validation errors is straightforward and well-integrated into the framework. When validation fails during a form submission, Laravel automatically redirects back with the input and any error messages stored in the session. Here's how you can display those errors in your views.

1. Using $errors
in Blade Templates
Laravel makes a special $errors
variable available in all Blade views. This variable is an instance of Illuminate\Support\MessageBag
, and it contains any validation errors from the previous request.
You can display errors for a specific field like this:

<input type="text" name="email" value="{{ old('email') }}"> @if ($errors->has('email')) <span style="color: red;"> {{ $errors->first('email') }} </span> @endif
old('email')
repopulates the field with the previously submitted value.$errors->first('email')
gets the first error message for theemail
field.
2. Displaying All Errors at the Top
If you want to show a summary of all validation errors at the top of the form:
@if ($errors->any()) <div style="color: red;"> <ul> @foreach ($errors->all() as $error) <li>{{ $error }}</li> @endforeach </ul> </div> @endif
This is useful for giving users an overview of what went wrong.

3. Per-Field Error Styling
You can also conditionally apply CSS classes if a field has errors:
<div class="form-group {{ $errors->has('email') ? 'has-error' : '' }}"> <label>Email</label> <input type="email" name="email" value="{{ old('email') }}"> @if ($errors->has('email')) <span class="error-text">{{ $errors->first('email') }}</span> @endif </div>
This helps visually highlight problematic fields.
4. Working with Form Requests
If you're using a Form Request (like StoreUserRequest
), Laravel handles the validation automatically. Just make sure your controller method type-hints the request:
public function store(StoreUserRequest $request) { // Validation passes automatically // Save user logic here }
After failed validation, Laravel redirects back with errors — same as manual validation.
5. Manual Validation in Controller
If you validate manually using the Validator
facade:
use Illuminate\Support\Facades\Validator; public function store(Request $request) { $validator = Validator::make($request->all(), [ 'email' => 'required|email', 'name' => 'required|min:3' ]); if ($validator->fails()) { return redirect()->back() ->withErrors($validator) ->withInput(); } // Proceed if valid }
-
withErrors($validator)
puts the errors in the session so$errors
is available in the view.
Key Points to Remember
- Laravel automatically shares the
$errors
variable in all views. - Use
old()
to repopulate form fields. - Always redirect after a validation failure (don’t render directly).
- With AJAX requests, Laravel returns a JSON response with errors automatically.
Basically, just check $errors
in your Blade template and display messages where needed. It’s simple and works out of the box.
The above is the detailed content of How to display validation errors in Laravel?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three main ways to set environment variables in PHP: 1. Global configuration through php.ini; 2. Passed through a web server (such as SetEnv of Apache or fastcgi_param of Nginx); 3. Use putenv() function in PHP scripts. Among them, php.ini is suitable for global and infrequently changing configurations, web server configuration is suitable for scenarios that need to be isolated, and putenv() is suitable for temporary variables. Persistence policies include configuration files (such as php.ini or web server configuration), .env files are loaded with dotenv library, and dynamic injection of variables in CI/CD processes. Security management sensitive information should be avoided hard-coded, and it is recommended to use.en

To enable PHP containers to support automatic construction, the core lies in configuring the continuous integration (CI) process. 1. Use Dockerfile to define the PHP environment, including basic image, extension installation, dependency management and permission settings; 2. Configure CI/CD tools such as GitLabCI, and define the build, test and deployment stages through the .gitlab-ci.yml file to achieve automatic construction, testing and deployment; 3. Integrate test frameworks such as PHPUnit to ensure that tests are automatically run after code changes; 4. Use automated deployment strategies such as Kubernetes to define deployment configuration through the deployment.yaml file; 5. Optimize Dockerfile and adopt multi-stage construction

Laravel's configuration cache improves performance by merging all configuration files into a single cache file. Enabling configuration cache in a production environment can reduce I/O operations and file parsing on each request, thereby speeding up configuration loading; 1. It should be enabled when the application is deployed, the configuration is stable and no frequent changes are required; 2. After enabling, modify the configuration, you need to re-run phpartisanconfig:cache to take effect; 3. Avoid using dynamic logic or closures that depend on runtime conditions in the configuration file; 4. When troubleshooting problems, you should first clear the cache, check the .env variables and re-cache.

When choosing a suitable PHP framework, you need to consider comprehensively according to project needs: Laravel is suitable for rapid development and provides EloquentORM and Blade template engines, which are convenient for database operation and dynamic form rendering; Symfony is more flexible and suitable for complex systems; CodeIgniter is lightweight and suitable for simple applications with high performance requirements. 2. To ensure the accuracy of AI models, we need to start with high-quality data training, reasonable selection of evaluation indicators (such as accuracy, recall, F1 value), regular performance evaluation and model tuning, and ensure code quality through unit testing and integration testing, while continuously monitoring the input data to prevent data drift. 3. Many measures are required to protect user privacy: encrypt and store sensitive data (such as AES

To build a PHP content payment platform, it is necessary to build a user management, content management, payment and permission control system. First, establish a user authentication system and use JWT to achieve lightweight authentication; second, design the backend management interface and database fields to manage paid content; third, integrate Alipay or WeChat payment and ensure process security; fourth, control user access rights through session or cookies. Choosing the Laravel framework can improve development efficiency, use watermarks and user management to prevent content theft, optimize performance requires coordinated improvement of code, database, cache and server configuration, and clear policies must be formulated and malicious behaviors must be prevented.

User permission management is the core mechanism for realizing product monetization in PHP development. It separates users, roles and permissions through a role-based access control (RBAC) model to achieve flexible permission allocation and management. The specific steps include: 1. Design three tables of users, roles, and permissions and two intermediate tables of user_roles and role_permissions; 2. Implement permission checking methods in the code such as $user->can('edit_post'); 3. Use cache to improve performance; 4. Use permission control to realize product function layering and differentiated services, thereby supporting membership system and pricing strategies; 5. Avoid the permission granularity is too coarse or too fine, and use "investment"

The core idea of PHP combining AI for video content analysis is to let PHP serve as the backend "glue", first upload video to cloud storage, and then call AI services (such as Google CloudVideoAI, etc.) for asynchronous analysis; 2. PHP parses the JSON results, extract people, objects, scenes, voice and other information to generate intelligent tags and store them in the database; 3. The advantage is to use PHP's mature web ecosystem to quickly integrate AI capabilities, which is suitable for projects with existing PHP systems to efficiently implement; 4. Common challenges include large file processing (directly transmitted to cloud storage with pre-signed URLs), asynchronous tasks (introducing message queues), cost control (on-demand analysis, budget monitoring) and result optimization (label standardization); 5. Smart tags significantly improve visual

Laravel's EloquentScopes is a tool that encapsulates common query logic, divided into local scope and global scope. 1. The local scope is defined with a method starting with scope and needs to be called explicitly, such as Post::published(); 2. The global scope is automatically applied to all queries, often used for soft deletion or multi-tenant systems, and the Scope interface needs to be implemented and registered in the model; 3. The scope can be equipped with parameters, such as filtering articles by year or month, and corresponding parameters are passed in when calling; 4. Pay attention to naming specifications, chain calls, temporary disabling and combination expansion when using to improve code clarity and reusability.
