How to clear cache in Laravel (route, config, view)?
Jul 19, 2025 am 02:22 AMLaravel cache will cause the modified routes, configurations or views to not take effect after a long time, and the cache needs to be cleared manually. 1. After modifying the route, run php artisan route:clear to clear the route cache; 2. After changing the configuration file, run php artisan config:clear to clear the configuration cache; 3. When the view content is not updated, run php artisan view:clear or delete the storage/framework/views file to clear the view cache; 4. If you are not sure of the source of the problem, you can run multiple commands in one click to clear all caches, such as php artisan config:clear, php artisan route:clear, php artisan view:clear, php artisan cache:clear, and even php artisan optimize:clear to solve the problem comprehensively.
Laravel cache will cause some problems after being used for a long time, such as if the route, configuration or view is not effective after modifying it. At this time, you need to manually clear the cache. This matter is not complicated, but you have to know how to operate it.

Clear the routing cache
Laravel caches routes to improve performance, but after changing routes/web.php
or other routing files, the new content will not take effect immediately. To clear the routing cache, just run the following command:
-
php artisan route:clear
This command deletes the routing cache file. If you are not sure if it is a routing problem, you can try it. In addition, sometimes the route fails after the code is deployed, which may be because no new cache is generated. At this time, you can regenerate it with php artisan route:cache
.

Clear the configuration cache
After the configuration file is changed, such as changing the .env
file or config/app.php
, Laravel will not automatically read new content because it uses cached configuration. Clearing the configuration cache is also very simple:
-
php artisan config:clear
If you find that the configuration does not take effect after deployment, this command will likely be solved. In the development environment, cache configuration is generally not required, but in the production environment, it will be cached for performance, so remember to clear or regenerate it during deployment.

Clear view cache
View cache mainly affects Blade templates. If you change the page content but it doesn't show it, it may be a problem with view caching. There are two ways to clear:
- Manually delete all
.php
files instorage/framework/views
directory - Or run
php artisan view:clear
You can also specify to clear certain view caches, such as clearing only caches in a certain directory, but they are generally not available. Most of the time, just clear the entire view cache.
Sometimes the page does not change after deployment, you can try this command. Especially since the Blade template has been changed but has not taken effect, clearing the view cache can basically solve the problem.
Common practices: Clear all caches with one click
If you are not sure which part of the cache is causing the problem, or want to solve various cache-related exceptions at once, you can directly run a few commands to clear:
-
php artisan config:clear
-
php artisan route:clear
-
php artisan view:clear
-
php artisan cache:clear
Sometimes php artisan optimize:clear
is added, which will clear more types of caches, including caches for events, services, routes, etc.
Basically these are the operations. Although each command is simple, figuring out which cache affects which function is the key to quickly solving the problem.
The above is the detailed content of How to clear cache in Laravel (route, config, view)?. 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 ways to add custom validation rules in Laravel: using closures, Rule classes, and form requests. 1. Use closures to be suitable for lightweight verification, such as preventing the user name "admin"; 2. Create Rule classes (such as ValidUsernameRule) to make complex logic clearer and maintainable; 3. Integrate multiple rules in form requests and centrally manage verification logic. At the same time, you can set prompts through custom messages methods or incoming error message arrays to improve flexibility and maintainability.

The core methods for Laravel applications to implement multilingual support include: setting language files, dynamic language switching, translation URL routing, and managing translation keys in Blade templates. First, organize the strings of each language in the corresponding folders (such as en, es, fr) in the /resources/lang directory, and define the translation content by returning the associative array; 2. Translate the key value through the \_\_() helper function call, and use App::setLocale() to combine session or routing parameters to realize language switching; 3. For translation URLs, paths can be defined for different languages ??through prefixed routing groups, or route alias in language files dynamically mapped; 4. Keep the translation keys concise and

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

ServiceProvider is the core mechanism used in the Laravel framework for registering services and initializing logic. You can create a custom ServiceProvider through the Artisan command; 1. The register method is used to bind services, register singletons, set aliases, etc., and other services that have not yet been loaded cannot be called; 2. The boot method runs after all services are registered and is used to register event listeners, view synthesizers, middleware and other logic that depends on other services; common uses include binding interfaces and implementations, registering Facades, loading configurations, registering command-line instructions and view components; it is recommended to centralize relevant bindings to a ServiceProvider to manage, and pay attention to registration

The core methods for handling exceptions and recording errors in Laravel applications include: 1. Use the App\Exceptions\Handler class to centrally manage unhandled exceptions, and record or notify exception information through the report() method, such as sending Slack notifications; 2. Use Monolog to configure the log system, set the log level and output method in config/logging.php, and enable error and above level logs in production environment. At the same time, detailed exception information can be manually recorded in report() in combination with the context; 3. Customize the render() method to return a unified JSON format error response, improving the collaboration efficiency of the front and back end of the API. These steps are

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.
