作曲家更新后,Laravel 4.2 artisan CLI不再起作用 [英] Laravel 4.2 artisan CLI does not work anymore after composer update
本文介绍了作曲家更新后,Laravel 4.2 artisan CLI不再起作用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我刚刚在生产服务器上运行了"composer update",并收到了以下错误消息:
I just ran "composer update" on my production server, and received this error:
Script php artisan clear-compiled handling the post-update-cmd event returned with an error
当我尝试任何"php artisan"命令时,我没有收到任何结果.
When I try any "php artisan" commands, I do not receive any results.
我尝试删除composer.lock文件和供应商文件夹,然后再次运行"composer install",但没有结果.
I have tried deleting my composer.lock file and my vendor folder, and ran "composer install" again, but no results.
这是我的composer.json文件:
Here is my composer.json file:
{
"name": "laravel/laravel",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"type": "project",
"require": {
"laravel/framework": "4.2.*",
"bllim/laravalid": "dev-laravel4",
"facebook/php-sdk-v4" : "~5.0"
},
"autoload": {
"classmap": [
"app/commands",
"app/controllers",
"app/composers",
"app/models",
"app/database/migrations",
"app/database/seeds",
"app/tests/TestCase.php"
]
},
"scripts": {
"post-install-cmd": [
"php artisan clear-compiled",
"php artisan optimize"
],
"post-update-cmd": [
"php artisan clear-compiled",
"php artisan optimize"
],
"post-create-project-cmd": [
"php artisan key:generate"
]
},
"config": {
"preferred-install": "dist"
},
"minimum-stability": "stable"
}
我的生产服务器运行PHP 5.6和Apache 2.4.
My production server runs PHP 5.6 and Apache 2.4.
推荐答案
我通过以下步骤解决了这个问题:
I solved this problem by following steps:
- 删除供应商文件夹和composer.lock
- 将composer.jason更改为默认
- 运行composer安装
- 运行作曲家更新
- 在bllim验证文件夹转换器"中将其转换为转换器"
- 再次运行作曲家更新
这篇关于作曲家更新后,Laravel 4.2 artisan CLI不再起作用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文