Hi all,
I have Magento 2 hosted on a VPS , managed by Plesk Onyx.
I'm attempting the upgrade on a staging website within the same environment. I think the issue might have come from auto-updates on Plesk Onyx as my Composer version is 2.0.0.
I'm wondering how I can downgrade? I've provided an image of the errors below.
composer --version
Composer version 1.7.2 2018-08-16 16:57:12
Magento 2.2.6:
Installed composer/composer
package version:
$ composer show composer/composer | grep versions
versions : * 1.4.1
Dependencies which have composer/composer
requirements and their constraints:
$ composer depends composer/composer
magento/composer 1.2.0 requires composer/composer (1.4.1)
magento/framework 101.0.6 requires composer/composer (^1.4)
magento/magento2-base 2.2.6 requires composer/composer (1.4.1)
magento/product-community-edition 2.2.6 requires composer/composer (1.4.1)
magento/project-community-edition 2.2.6 requires composer/composer (@alpha)
After the Magento 2.3.0 upgrade:
Installed composer/composer
package version:
$ composer show composer/composer | grep versions
versions : * 1.7.3
Dependencies which have composer/composer
requirements and their constraints:
$ composer depends composer/composer
magento/composer 1.4.0 requires composer/composer (^1.6)
magento/framework 102.0.0 requires composer/composer (^1.6)
magento/magento2-base 2.3.0 requires composer/composer (^1.6)
magento/product-community-edition 2.3.0 requires composer/composer (^1.6)
magento/project-community-edition 2.3.0 requires composer/composer (@alpha)
Thanks for this, everytime I run a composer command I keep getting the yellow message that the image shows to do with API
when I run composer update --no-plugins like it tells me to, it is the same error as this image shows
Have you checked shared composer versions, Please check what is required based on your magento version. Yellow message that is fine, that is not an error.
@callam_kidsawdid you find a solution to this? I'm having the same issue.
I tried installing composer locally but every time I run composer update the process gets killed, even when specifying the memory limit.
Thanks.
@denialdesign No, sorry.
The website I maintain is not very 'big' so to speak.
In the end, I made a subdomain, installed Magento 2.3.5 and replicated the current store. I had it live within 3 days.