New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath() #8127

Closed
lbausch opened this Issue Mar 24, 2015 · 13 comments

Comments

Projects
None yet
@lbausch
Copy link
Contributor

lbausch commented Mar 24, 2015

After crafting a new application with laravel new foo and running composer update in the foo directory, the following happens:

Writing lock file
Generating autoload files
PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath() in /tmp/foo/vendor/laravel/framework/src/Illuminate/Foundation/Console/ClearCompiledCommand.php on line 28



  [Symfony\Component\Debug\Exception\FatalErrorException]                             
  Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath()  



Script php artisan clear-compiled handling the post-update-cmd event returned with an error



  [RuntimeException]                                                                                                                                                                                              
  Error Output: PHP Fatal error:  Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath() in /tmp/foo/vendor/laravel/framework/src/Illuminate/Foundation/Console/ClearCompiledCommand  
  .php on line 28                                                                                                                                                                                                 



update [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--lock] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--with-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [packages1] ... [packagesN]

I also saw issue #8124 but the provided solution did not help here.

@coldKingdom

This comment has been minimized.

Copy link

coldKingdom commented Mar 24, 2015

I had the same problem. Deleted the compiled.php-file in the vendor directory manually, and then it started to work again.

@0xMatt

This comment has been minimized.

Copy link
Contributor

0xMatt commented Mar 24, 2015

Confirming issue on a fresh 5.0.* install as of a few moments ago.

@Helrunar

This comment has been minimized.

Copy link

Helrunar commented Mar 24, 2015

Can confirm issue too, delete the compiled.php and it work again

@GrahamCampbell

This comment has been minimized.

Copy link
Member

GrahamCampbell commented Mar 24, 2015

Thank you @Helrunar. For anyone reading this, you need to delete your compiled files otherwise the old code will be used by laravel to try to generate the compiled file. Just a technical limitation.

@imuneer

This comment has been minimized.

Copy link

imuneer commented Mar 30, 2015

Can confirm the issue. Let me check deleting the file compiled.php.....

Yes it is working.

@teertz

This comment has been minimized.

Copy link

teertz commented Apr 2, 2015

Yea, had the same problem.
Deleting the file vendor/compiled.php – helps

@rdjoks

This comment has been minimized.

Copy link

rdjoks commented Apr 2, 2015

Yes me too, replace a lot of files in my project directory but that didn't work, had to remove compiled.php, run php artisan clear-compiled and then composer update

@GuillaumeDievart

This comment has been minimized.

Copy link

GuillaumeDievart commented Apr 5, 2015

@GrahamCampbell You'll envisage to fix this bug ?

@larryweya

This comment has been minimized.

Copy link

larryweya commented Apr 13, 2015

Ran into the same issue but my compiled.php was in storage/framework/compiled.php not in vendor/compiled.php

@GrahamCampbell

This comment has been minimized.

Copy link
Member

GrahamCampbell commented Apr 13, 2015

@larryweya Yes, this happens if your file permissions are incorrect and we're not able to write to the vendor folder. We'll use that storage folder as a fallback in 5.0.

@phpclub

This comment has been minimized.

Copy link

phpclub commented Apr 16, 2015

Can confirm issue too, delete the compiled.php

@Ardakilic

This comment has been minimized.

Copy link

Ardakilic commented Apr 16, 2015

I can confirm this, too. deleting vendor/compiled.php manually and running again works like a charm.

@GrahamCampbell

This comment has been minimized.

Copy link
Member

GrahamCampbell commented Jul 18, 2015

See #9678.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment