Following error occured when I try to run composer update or run any command:
PHP Fatal error: Call to undefined method Fxp\Composer\AssetPlugin\Package\Version\VersionParser::parseLinks() in /root/.composer/vendor/fxp/composer-asset-plugin/Repository/VcsPackageFilter.php on line 272
Fatal error: Call to undefined method Fxp\Composer\AssetPlugin\Package\Version\VersionParser::parseLinks() in /root/.composer/vendor/fxp/composer-asset-plugin/Repository/VcsPackageFilter.php on line 272
Try to remove the invalid / incomplete version by using
composer global remove fxp/composer-asset-plugin
In case that fails, you might remove the plugin folder manually from Composers home folder:
rm -rf ~/.composer/vendor/fxp
Then, reinstall the plugin and cross fingers that everything works now :)
composer global require "fxp/composer-asset-plugin:~1.1.1"
Related
I have Magento 2.3 and I want to use Magento Functional Testing Framework version 2.3 but when I run the command vendor/bin/mftf run:test AdminLoginTest to run the test, the following error occurs:
==== Redirecting to Composer-installed version in vendor/codeception ====
Fatal error: Uncaught Error: Call to undefined function Codeception\Lib\codecept_absolute_path() in /Users/hanhan/Deskto
p/workspace/magento2/vendor/codeception/codeception/src/Codeception/Lib/ParamsLoader.php:25
In the file PramsLoader.php, codecept_absolute_path() method is invoked and it gives the error because this method is not defined
$this->paramsFile = codecept_absolute_path($paramStorage);
How can i solve this ?
I happened to encounter the same error today. It's because there is an old vendor directory in dev/tests/acceptance where previously we store composer.json file and now moved to root. Deleting dev/tests/acceptance/vendor folder resolve the fatal error.
I am presenting the following problem and that is when opening my Yii2 application, the charge in my browser as follows http://localhost/basic/web/ and I get the following error: Fatal error: Cannot use 'Object' as class name as it is reserved in C:\xampp\htdocs\basic\vendor\yiisoft\yii2\base\Object.php on line 77
Run the "composer update" command
or composer.phar update
where your composer.json resides
I'm trying to start using laravel php framework. I'm trying to just call the index file and I get this error message.
C:\xampp\php\php.exe C:\xampp\htdocs\tutorials\lara\application\public\index.php
Fatal error: Interface 'Illuminate\Auth\Illuminate\Contracts\Auth\Factory' not found in C:\xampp\htdocs\tutorials\lara\application\bootstrap\cache\compiled.php on line 357
Process finished with exit code 255
Can anyone shine some light on what this means?
Your Illuminate\Auth\Illuminate\Contracts\Auth\Factory may not copied in your project,that why this is happening.So you need to be
Step 1 : Remove full vendor folder
Step 2 : Run from your terminal composer install
I'm trying to run unit tests on zurmo and I've a problem, when I try the EmailTemplateTest. I get
Fatal error: Class 'ZurmoBaseTest' not found in zurmo\app\protected\
modules\emailTemplates\tests\unit\EmailTemplateTest.php on line 42
If I try to include it with require it fixes this, but then
Fatal error: Class 'BaseTest' not found in zurmo\app\protected\modul
es\zurmo\tests\unit\ZurmoBaseTest.php on line 38
and
Fatal error: Class 'RedBeanDatabase' not found in zurmo\app\protecte
d\core\tests\unit\BaseTest.php on line 44
If I include them both I get the final
Fatal error: Class 'Yii' not found in zurmo\app\protected\core\model
s\RedBeanDatabase.php on line 37
What's the problem? Am I supposed to run it from some exact location or the installation is not default. I installed it with the settup and the app is working itself.
You bootstrap is likely missing the autoloader of your framework and / or your framework's PHPUnit extension.
For anyone else looking for the answer to this one. You should run it via TestSuite.php
phpunit TestSuite.php EmailTemplateTest
TestSuite.php will include the necessary files for you.
http://zurmo.org/tutorials/running-unit-tests-explained
I just tried to install a fresh instance of Laravel as described in the docs ( http://laravel.com/docs/quick#installation - "Via Composer"). Got this error from Composer:
...
Writing lock file
Generating autoload files
PHP Fatal error: Class 'Monolog\Logger' not found in ...\src\vendor\laravel\framework\src\Illuminate\Log\LogServiceProvider.php on line 23
{"error":{"type":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","message":"Class 'Monolog\\Logger' not found","file":"...\\src\\vendor\\laravel\\framework\\src\\Illuminate\\Log\\LogServiceProvider.php","line":23}}Script php artisan clear-c
ompiled handling the post-install-cmd event returned with an error: PHP Fatal error: Class 'Monolog\Logger' not found in ...\src\Illuminate\Log\LogServiceProvider.php on line 23
PHP Fatal error: Class 'Monolog\Logger' not found in ...\src\Illuminate\Log\LogServiceProvider.php on line 23
{"error":{"type":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","message":"Class 'Monolog\\Logger' not found","file":"...\\src\\vendor\\laravel\\framework\\src\\Illuminate\\Log\\LogServiceProvider.php","line":23}}Script php artisan optimiz
e handling the post-install-cmd event returned with an error: PHP Fatal error: Class 'Monolog\Logger' not found in ...\src\Illuminate\Log\LogServiceProvider.php on line 23
Uhm, what to do now? Tried to post it on the official forums but that wasn't possible due to an error there (forums are based on Laravel... yeah that's Karma!).
Solution: "composer dumpautoload -o"