I've installed Magento with sample data on a virtual machine. Now I'm trying to install Live Search for it. I used the instructions from this link. As the instruction says, I run the command below:
composer require magento/live-search
But it gives me an error:
Problem 1
- magento/live-search 2.0.0 requires magento/module-live-search-metrics 2.0.0 -> could not be found in any version, there may be a typo in the package name.
- magento/live-search 2.0.1 requires magento/module-live-search-metrics 2.0.1 -> could not be found in any version, there may be a typo in the package name.
- magento/live-search 2.0.2 requires magento/module-live-search-metrics 2.0.2 -> could not be found in any version, there may be a typo in the package name.
- magento/live-search 2.0.3 requires magento/module-live-search-metrics 2.0.3 -> could not be found in any version, there may be a typo in the package name.
- Root composer.json requires magento/live-search ^2.0 -> satisfiable by magento/live-search[2.0.0, 2.0.1, 2.0.2, 2.0.3].
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
- It's a private package and you forgot to add a custom repository to find it
Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require magento/live-search:*" to figure out if any version is installable, or "composer require magento/live-search:^2.1" if you know which you need.
As I can see, it says magento/module-live-search-metrics does not exist, but I couldn't find anyone else who has the same problem as mine, which means this is only my problem.
You just have to type:
composer require magento/module-live-search
and that's it =)
Related
I'm trying to install a module on a Drupal 8.9.6 using composer 2.0 but I get the next error:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- cweagans/composer-patches 1.6.7 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
- drupal/varbase_heroslider_media 7.13.0 requires cweagans/composer-patches ~1.0 -> satisfiable by cweagans/composer-patches[1.6.7].
- drupal/varbase_heroslider_media is locked to version 7.13.0 and an update of this package was not requested.
You are using Composer 2, which some of your plugins seem to be incompatible with. Make sure you update your plugins or report a plugin-issue to ask them to support Composer 2.
Then, I've tried to update cweagans/composer-patches to 1.7 because this issue was solved here. But I get the next error:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/drupal-library-installer-plugin 0.3 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
- drupal/varbase_heroslider_media 7.13.0 requires drupal/drupal-library-installer-plugin ^0.3 -> satisfiable by drupal/drupal-library-installer-plugin[0.3].
- drupal/varbase_heroslider_media is locked to version 7.13.0 and an update of this package was not requested.
You are using Composer 2, which some of your plugins seem to be incompatible with. Make sure you update your plugins or report a plugin-issue to ask them to support Composer 2.
Ok, then, I've tried to update drupal/drupal-library-installer-plugin I get again the first error. It is a circle and I can't update Drupal.
How could I do it?
drupal/drupal-library-installer-plugin has not seen any updates since more than five years(!). Either search for an alternative, or downgrade Composer to v1
When I tried to install Elasticsearch for my Laravel instance using the following command:
composer require elasticsearch/elasticsearch
I got this error:
Problem 1
- elasticsearch/elasticsearch v7.6.0 requires guzzlehttp/ringphp dev-fork-elasticsearch -> no matching package found.
- tamayo/laravel-scout-elastic 5.0.0 requires elasticsearch/elasticsearch ^5.0 -> satisfiable by
elasticsearch/elasticsearch[5.0.x-dev].
- tamayo/laravel-scout-elastic 5.0.0 requires elasticsearch/elasticsearch ^5.0 -> satisfiable by
elasticsearch/elasticsearch[5.0.x-dev].
- tamayo/laravel-scout-elastic 5.0.0 requires elasticsearch/elasticsearch ^5.0 -> satisfiable by
elasticsearch/elasticsearch[5.0.x-dev].
- Can only install one of: elasticsearch/elasticsearch[v7.6.1, 5.0.x-dev].
- Installation request for elasticsearch/elasticsearch ^7.6 -> satisfiable by elasticsearch/elasticsearch[v7.6.0, v7.6.1].
- Installation request for tamayo/laravel-scout-elastic ^5.0 -> satisfiable by tamayo/laravel-scout-elastic[5.0.0].
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting see
https://getcomposer.org/doc/04-schema.md#minimum-stability for more
details.
- It's a private package and you forgot to add a custom repository to find it
Read https://getcomposer.org/doc/articles/troubleshooting.md for
further common problems.
Installation failed, reverting ./composer.json to its original
content.
then I tried to install the package mentioned in the error using the following command:
composer require guzzlehttp/ringphp
and I got the following warning:
Package guzzlehttp/ringphp is abandoned, you should avoid using it. No
replacement was suggested. Package guzzlehttp/streams is abandoned,
you should avoid using it. No replacement was suggested
Then I tried to install it again, and I got the same error.
What can I do to address the problem?
Please simply try installing it again - according to Packagist, there is a version 7.6.1 available that does not depend on such packages any more. This is something you can also find on https://github.com/elastic/elasticsearch-php/releases
I'm trying to install LiipImagineBundle with Symfony 5 but I'm getting this error :
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for liip/imagine-bundle ^2.2 -> satisfiable by liip/imagine-bundle[2.2.0].
- liip/imagine-bundle 2.2.0 requires symfony/asset ^3.4|^4.2 -> no matching package found.
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
- It's a private package and you forgot to add a custom repository to find it
Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
Installation failed, reverting ./composer.json to its original content.
How can I fix this ?
I've seen this : Add support for Symfony 5
Then it's a matter of time.
Just working my way through the Userfrosting 4 tutorial. The basic app is up and running and am now creating the first sprinkle under "Your First UserFrosting Site".
On running composer update I get the following:
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- userfrosting/config dev-master requires userfrosting/support ^4.0.0 -> no matching package found.
- userfrosting/config dev-master requires userfrosting/support ^4.0.0 -> no matching package found.
- Installation request for userfrosting/config dev-master -> satisfiable by userfrosting/config[dev-master].
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
I've replaced my code with the copied / pasted code from the tutorial and still get the errors. I've absolutely no idea where to go from here - any pointers would be appreciated.
Make sure you have the latest version (4.0.11-alpha as of now) since the component versioning was changed/fixed in a recent version.
The core composer.json file shoudn't use the dev-master version of userfrosting/config component anymore, but one of the 4.0.x version. See : https://github.com/userfrosting/UserFrosting/blob/master/app/sprinkles/core/composer.json#L31. If you have a custom ^composer.json` file in your sprinkle, you don't need to add the packages define in the core composer file again.
That being said, if you're still having some issues, you can try running composer clear-cache as composer might have cached some outdated info.
I'm using xampp on Windows 8 and I want to run composer.phar update for installing Yii2-useraccording do the description here:
http://yii2-user.readthedocs.org/en/latest/getting-started/installation.html
But when I do that, no update happens.
Instead, I got shown the version number of composer and a list of the possible commands with composer.
There is no error-message and update is in the list of the possible commands.
I have tried composer update too, but with that I'm getting an error message:
Problem 1
- yiisoft/yii2 2.0.1 requires bower-asset/jquery 2.1.*#stable | 1.11.*#stabl
e -> no matching package found.
- yiisoft/yii2 2.0.0 requires bower-asset/jquery 2.1.*#stable | 1.11.*#stabl
e -> no matching package found.
- yiisoft/yii2 2.0.1 requires bower-asset/jquery 2.1.*#stable | 1.11.*#stabl
e -> no matching package found.
- Installation request for yiisoft/yii2 * -> satisfiable by yiisoft/yii2[2.0
.0, 2.0.1].
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your min
imum-stability setting
see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> f
or more details.
Seems like you missed execution of this command:
composer global require "fxp/composer-asset-plugin:~1.1.1"
It should be executed only once.
You can find more information about it in official documentation and plugin Github page.
this problem is recursive since 2014, like other than AssetsManager, permissions .... and somes php Warning or Fatal, at the begin of installation. I do not know how "Composer" elsewhere. But frankly with Yii2 is a calamity. Then as yii2 already does not need it for bugs. The accumulation of 2 it is a disaster. So...
composer global require "fxp/composer-asset-plugin:~1.0"
With ~ you get the last version of composer-asset-plugin...
But that's often not enought !!!!