"Please provide a valid cache path" error in laravel

LaravelLaravel 5

Laravel Problem Overview


I duplicated a working laravel app and renamed it to use for another app. I deleted the vendor folder and run the following commands again:

composer self-update

composer-update

npm install

bower install

I configured my routes and everything properly however now when I try to run my app in my browser I get the following errors:

> InvalidArgumentException in Compiler.php line 36: Please provide a > valid cache path. > > ErrorException in Filesystem.php line 111: > file_put_contents(F:\www\example\app\storage\framework/sessions/edf262ee7a2084a923bb967b938f54cb19f6b37d): > failed to open stream: No such file or directory

I have never had this issue before, I do not know what is causing it neither do I know how to fix it, I have googled online for a solution but have found none so far.

Laravel Solutions


Solution 1 - Laravel

Try the following:

create these folders under storage/framework:

  • sessions
  • views
  • cache

Now it should work

Solution 2 - Laravel

Try this:

  1. php artisan cache:clear
  2. php artisan config:clear
  3. php artisan view:clear

Solution 3 - Laravel

So apparently what happened was when I was duplicating my project the framework folder inside my storage folder was not copied to the new directory, this cause my error.

Solution 4 - Laravel

The cause of this error can be traced from Illuminate\View\Compilers\Compiler.php

public function __construct(Filesystem $files, $cachePath)
{
    if (! $cachePath) {
        throw new InvalidArgumentException('Please provide a valid cache path.');
    }

    $this->files = $files;
    $this->cachePath = $cachePath;
}

The constructor is invoked by BladeCompiler in Illuminate\View\ViewServiceProvider

/**
 * Register the Blade engine implementation.
 *
 * @param  \Illuminate\View\Engines\EngineResolver  $resolver
 * @return void
 */
public function registerBladeEngine($resolver)
{
    // The Compiler engine requires an instance of the CompilerInterface, which in
    // this case will be the Blade compiler, so we'll first create the compiler
    // instance to pass into the engine so it can compile the views properly.
    $this->app->singleton('blade.compiler', function () {
        return new BladeCompiler(
            $this->app['files'], $this->app['config']['view.compiled']
        );
    });

    $resolver->register('blade', function () {
        return new CompilerEngine($this->app['blade.compiler']);
    });
}

So, tracing back further, the following code:

$this->app['config']['view.compiled']

is generally located in your /config/view.php, if you use the standard laravel structure.

<?php
return [
    /*
    |--------------------------------------------------------------------------
    | View Storage Paths
    |--------------------------------------------------------------------------
    |
    | Most templating systems load templates from disk. Here you may specify
    | an array of paths that should be checked for your views. Of course
    | the usual Laravel view path has already been registered for you.
    |
    */
    'paths' => [
        resource_path('views'),
    ],
    /*
    |--------------------------------------------------------------------------
    | Compiled View Path
    |--------------------------------------------------------------------------
    |
    | This option determines where all the compiled Blade templates will be
    | stored for your application. Typically, this is within the storage
    | directory. However, as usual, you are free to change this value.
    |
    */
    'compiled' => realpath(storage_path('framework/views')),
];

realpath(...) returns false, if the path does not exist. Thus, invoking

'Please provide a valid cache path.' error.

Therefore, to get rid of this error, what you can do is to ensure that

storage_path('framework/views')

or

/storage/framework/views

exists :)

Solution 5 - Laravel

Ensure the below folders in storage directory:

  • logs
  • framework
  • framework/cache
  • framework/cache/data
  • framework/sessions
  • framework/testing
  • framework/views

Below is a command-line snippet that does for you

cd storage
mkdir logs
mkdir framework
mkdir framework/cache && framework/cache/data
mkdir framework/sessions
mkdir framework/testing
mkdir framework/views
chgrp -R www-data ../storage
chown -R www-data ../storage

Solution 6 - Laravel

Run these command to create required directories:

cd storage/
mkdir -p framework/{sessions,views,cache}
chmod -R 775 framework

That's it!

Solution 7 - Laravel

You can edit your readme.md with instructions to install your laravel app in other environment like this:

## Create folders

```
#!terminal

cp .env.example .env && mkdir bootstrap/cache storage storage/framework && cd storage/framework && mkdir sessions views cache

```

## Folder permissions

```
#!terminal

sudo chown :www-data app storage bootstrap -R
sudo chmod 775 app storage bootstrap -R

```

## Install dependencies

```
#!terminal

composer install

```

Solution 8 - Laravel

You need to create folders inside "framework". Please Follow these steps:

cd storage/
mkdir -p framework/{sessions,views,cache}

You also need to set permissions to allow Laravel to write data in this directory.

chmod -R 775 framework
chown -R www-data:www-data framework

Solution 9 - Laravel

Try the following:

create these folders under storage/framework:

  • sessions
  • views
  • cache/data

if still it does not work then try

php artisan cache:clear
php artisan config:clear
php artisan view:clear

if get an error of not able to clear cache. Make sure to create a folder data in cache/data

Solution 10 - Laravel

Check if the following folders exists, if not create these folders.

  • storage/framework/cache
  • storage/framework/sessions
  • storage/framework/testing
  • storage/framework/views

Solution 11 - Laravel

I solved the problem when I created framework folder inside storage folder and its subfolders sessions, views and cache.

Go to your cmd or terminal then type your project root path and after that type the following:

cd storage
mkdir framework
cd framework
mkdir sessions
mkdir views
mkdir cache

Go to your project root path back again and run composer update

After that artisan works perfectly.

Solution 12 - Laravel

  1. Start by clearing the cache
php artisan cache:clear
php artisan config:clear
php artisan view:clear
  1. If it doesn't work, ensure the all the following folders are available
logs
framework
framework/cache 
framework/sessions 
framework/views
  1. If none of the suggestions works, verify that the config file config/view.php is present. If not, you can get a copy of this file for the Laravel you're using and copy it to the project config folder.

Solution 13 - Laravel

Step 1、Create these folders

  • mkdir -p storage/{app,framework,logs}
  • mkdir -p storage/framework/{sessions,views,cache}
  • chmod -R 777 storage

Step 2、Clear cache/config/view

  • php artisan cache:clear
  • php artisan config:clear
  • php artisan view:clear

Solution 14 - Laravel

Please run in terminal,

   sudo mkdir storage/framework
   sudo mkdir storage/framework/sessions
   sudo mkdir storage/framework/views
   sudo mkdir storage/framework/cache
   sudo mkdir storage/framework/cache/data

Now you have to change permission,

   sudo chmod -R 777 storage

Solution 15 - Laravel

step 1 : php artisan storage:link

step 2 : create these folders inside storage folder

Ensure the below folders in storage directory:

logs
framework
framework/cache 
framework/sessions 
framework/views

It worked for me

Solution 16 - Laravel

My 2 cents

Remove everything inside storage and then do this:

> cd storage/
> mkdir -p framework/{sessions,views,cache}
> chmod -R 755 framework

// This last line depends on your user group settings so 
// it may not be applicable to you.
> chown -R www-data:www-data framework

Worked for me =)

Solution 17 - Laravel

Issue on my side(while deploying on localhost): there was views folder missing.. so if you have don't have the framework folder the you 'll need to add folders. but if already framework folder exist then make sure all above folders i.e

  1. cache
  2. session
  3. views

exists in your framework directory.

Solution 18 - Laravel

If this happens on server:

sudo mkdir logs framework framework/cache framework/sessions framework/views
sudo chgrp -R www-data storage
sudo chmod -R ug+rwx storage

Solution 19 - Laravel

I solved this problem by adding this line in my index.php:

$app['config']['view.compiled'] = "storage/framework/cache";

Solution 20 - Laravel

Your storage directory may be missing, or one of its sub-directories. The storage directory must have all the sub-directories that shipped with the Laravel installation.

Solution 21 - Laravel

May be the storage folder doesn't have the app and framework folder and necessary permission. Inside framework folder it contains cache, sessions, testing and views. use following command this will works.

Use command line to go to your project root: 
cd {your_project_root_directory}
Now copy past this command as it is: 
cd storage && mkdir app && cd app && mkdir public && cd ../ && mkdir framework && cd framework && mkdir cache && mkdir sessions && mkdir testing && mkdir views && cd ../../ && sudo chmod -R 777 storage/

I hope this will solve your use.

Solution 22 - Laravel

I also had a similar case after copying a project on a production server. The public folder was accessed by Apache via a symbolic link.

For Apache or the PHP service, the path to the project has not changed, thus they used cached file paths that lead to the old project repository.

Restarting Apache and PHP service resolved the issue.

Solution 23 - Laravel

step 1 : php artisan storage:link

step 2 : create these folders inside storage folder

Ensure the below folders in storage directory:

logs framework framework/cache framework/sessions framework/views It worked for me

This worked for me too

Solution 24 - Laravel

In my case, the config cache files are all missing in boostrap/cache... so solution to me is php artisan config:cache to re-create cache files at boostrap/cache.

Solution 25 - Laravel

Error :'Please provide a valid cache path.' error.

If these type error comes then the solution given below :-

please create data folder inside storage/framework/cache

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
Questionuser3718908x100View Question on Stackoverflow
Solution 1 - LaravelMauricio Wanderley MartinsView Answer on Stackoverflow
Solution 2 - LaravelthefallenView Answer on Stackoverflow
Solution 3 - Laraveluser3718908x100View Answer on Stackoverflow
Solution 4 - LaravelghabxView Answer on Stackoverflow
Solution 5 - Laraveluser3785966View Answer on Stackoverflow
Solution 6 - LaravelRanjan FadiaView Answer on Stackoverflow
Solution 7 - LaravelAlex Benincasa SantosView Answer on Stackoverflow
Solution 8 - LaravelSohail AhmedView Answer on Stackoverflow
Solution 9 - LaravelMohsin YounasView Answer on Stackoverflow
Solution 10 - LaravelRAMA KRISHNAView Answer on Stackoverflow
Solution 11 - Laravelborisoft82View Answer on Stackoverflow
Solution 12 - LaravelNdifon Desmond YongView Answer on Stackoverflow
Solution 13 - LaravelTansy ZView Answer on Stackoverflow
Solution 14 - LaravelRashed ZamanView Answer on Stackoverflow
Solution 15 - LaravelRashid IqbalView Answer on Stackoverflow
Solution 16 - LaravelWhite RabbitView Answer on Stackoverflow
Solution 17 - LaravelFarid AbbasView Answer on Stackoverflow
Solution 18 - LaravelOstap BrehinView Answer on Stackoverflow
Solution 19 - LaravelcriusView Answer on Stackoverflow
Solution 20 - LaravelNaveed AliView Answer on Stackoverflow
Solution 21 - LaravelSujon Chondro ShilView Answer on Stackoverflow
Solution 22 - LaravelKarkanView Answer on Stackoverflow
Solution 23 - LaravelMélissa View Answer on Stackoverflow
Solution 24 - Laravelfree2idol1View Answer on Stackoverflow
Solution 25 - Laraveluser13483704View Answer on Stackoverflow