1

I have strange problem. After upgrading from 5.2.39 to 5.2.40 or 5.2.41 I get Throw exception if view cache path is empty.

I cannot revert the change - after upgrade all Composer or Artisan comments fail I guess is related to the change in Laravel 5.2.40.

How I can fix this?

A problem like this was fixed here but the solution doesn't work in my case.

Dirty fix

Only preemption for future damage. I still cannot fix the damaged app. I replaced laravel/framework": "5.2.*",with "laravel/framework": "5.2.39", to avoid breaking up this and other apps I have built. After the change the composer update would not disrupt my app.

Community
  • 1
  • 1
Peter
  • 2,634
  • 7
  • 32
  • 46
  • If composer or artisan comments failed then try remove vendor folder then run composer install – Imtiaz Pabel Aug 07 '16 at 10:53
  • I have tested taht solution. Didn't help. At the other question they just had no cache folders, which made the error to appear. I have the folder in place. This must be some strange compatibility issue within the app itself. – Peter Aug 07 '16 at 10:58
  • did you tried using remove bootstrap/cache? – Imtiaz Pabel Aug 07 '16 at 11:00
  • I just tried. I got `file_put_contents(D:\www\!Buluoge\bootstrap/cache/services.php): failed to open stream: No such file or directory` – Peter Aug 07 '16 at 11:34
  • remove bootstrap/cache then remove "post-install-cmd" part from composer.json and then run composer install – Imtiaz Pabel Aug 07 '16 at 11:41
  • Nope. Still `file_put_contents(D:\www\!Buluoge\bootstrap/cache/services.php): failed to open stream: No such file or directory` – Peter Aug 07 '16 at 12:28
  • this is a duplicate of http://stackoverflow.com/questions/38483837/please-provide-a-valid-cache-path, there is an answer to it an a work arround too – am05mhz Apr 01 '17 at 01:19

2 Answers2

3

I was having this problem too and I solve it when add the folder views in storage/framework, so just be sure that all folders did exists.

Vinicius Alcantara
  • 186
  • 1
  • 5
0

I had the same problem and I fixed it like this:

Create these folders under storage/framework:

sessions views cache

You probably will need to give permission to storage folder again like this:

sudo chmod -R 777 storage/
Himanshu Upadhyay
  • 6,558
  • 1
  • 20
  • 33