Skip to content
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

Error creating project on Laravel 5.1 #13017

Closed
donkeysharp opened this issue Apr 4, 2016 · 3 comments
Closed

Error creating project on Laravel 5.1 #13017

donkeysharp opened this issue Apr 4, 2016 · 3 comments

Comments

@donkeysharp
Copy link

Hello as 5.1 is a LTS version of Laravel at job we decided to use it for internal project, just today I self-updated my composer installation and when trying to create a new Laravel 5.1 project with
$ composer create-project laravel/laravel blog "5.1.*"
I had the next error

> php -r "copy('.env.example', '.env');"
> php artisan clear-compiled
PHP Warning:  require(/home/donkeysharp/code/foo/vvvv/bootstrap/../vendor/autoload.php): failed to open stream: No such file or direct
ory in /home/donkeysharp/code/foo/vvvv/bootstrap/autoload.php on line 17
PHP Fatal error:  require(): Failed opening required '/home/donkeysharp/code/foo/vvvv/bootstrap/../vendor/autoload.php' (include_path=
'.:/usr/share/php:/usr/share/pear') in /home/donkeysharp/code/foo/vvvv/bootstrap/autoload.php on line 17
Script php artisan clear-compiled handling the pre-update-cmd event returned with an error

I fixed it by removing pre-update-cmd on composer.json and with composer install it finally installed the whole dependencies.

I thought it was a composer problem but there is no problem with Laravel 5.2 so I think the problem is on 5.1
I really love Laravel but as 5.1 is a LTS version and not being able to create a project seems to be bad publicity for the project.

I wanted to post this issue on https://github.com/laravel/laravel but it seems there isn't the option.

@vlakoff
Copy link
Contributor

vlakoff commented Apr 5, 2016

Known issue, still awaiting for the solution to be backported...
See notably #12827 and laravel/laravel#3699.

@GrahamCampbell
Copy link
Member

Thanks for reporting, but we're already aware of this. I'll speak to Taylor again, and see if he's willing to have this backported.

@Dumzy
Copy link

Dumzy commented Sep 24, 2016

check there is a file type called .env. check whether your group have it. If not replace that. It will solve. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants