Error when upgrading from 2.2.6 to 2.2.7
I'm trying to upgrade 2.2.6
When I run the web setup wizard I get this response.
Check Component Dependency
We found conflicting component dependencies.
Command "update" failed: 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
- magento/product-community-edition 2.2.7 requires composer/composer 1.4.1 -> satisfiable by composer/composer[1.4.1].
- magento/product-community-edition 2.2.7 requires composer/composer 1.4.1 -> satisfiable by composer/composer[1.4.1].
- Conclusion: don't install composer/composer 1.4.1
- Installation request for magento/product-community-edition 2.2.7 -> satisfiable by magento/product-community-edition[2.2.7].
When I try the command line upgrade I just get memory errors due to forkbomb protection.
My composer version is 1.6.4 so newer than 1.4.1
The site is on shared hosting so I can't downgrade or upgrade composer.
magento2.2.6
edited yesterday
Abhishek Panchal
3,4122829
asked yesterday
Denial Design
8112
add a comment |
I'm trying to upgrade 2.2.6
When I run the web setup wizard I get this response.
Check Component Dependency
We found conflicting component dependencies.
Command "update" failed: 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
- magento/product-community-edition 2.2.7 requires composer/composer 1.4.1 -> satisfiable by composer/composer[1.4.1].
- magento/product-community-edition 2.2.7 requires composer/composer 1.4.1 -> satisfiable by composer/composer[1.4.1].
- Conclusion: don't install composer/composer 1.4.1
- Installation request for magento/product-community-edition 2.2.7 -> satisfiable by magento/product-community-edition[2.2.7].
When I try the command line upgrade I just get memory errors due to forkbomb protection.
My composer version is 1.6.4 so newer than 1.4.1
The site is on shared hosting so I can't downgrade or upgrade composer.
magento2.2.6
edited yesterday
Abhishek Panchal
3,4122829
asked yesterday
Denial Design
8112
Will deleting thevendorfolder and runningcomposer installandcomposer updatefix this?
– Denial Design
11 hours ago
add a comment |
I'm trying to upgrade 2.2.6
When I run the web setup wizard I get this response.
Check Component Dependency
We found conflicting component dependencies.
Command "update" failed: 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
- magento/product-community-edition 2.2.7 requires composer/composer 1.4.1 -> satisfiable by composer/composer[1.4.1].
- magento/product-community-edition 2.2.7 requires composer/composer 1.4.1 -> satisfiable by composer/composer[1.4.1].
- Conclusion: don't install composer/composer 1.4.1
- Installation request for magento/product-community-edition 2.2.7 -> satisfiable by magento/product-community-edition[2.2.7].
When I try the command line upgrade I just get memory errors due to forkbomb protection.
My composer version is 1.6.4 so newer than 1.4.1
The site is on shared hosting so I can't downgrade or upgrade composer.
magento2.2.6
edited yesterday
Abhishek Panchal
3,4122829
asked yesterday
Denial Design
8112
I'm trying to upgrade 2.2.6
When I run the web setup wizard I get this response.
Check Component Dependency
We found conflicting component dependencies.
Command "update" failed: 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
- magento/product-community-edition 2.2.7 requires composer/composer 1.4.1 -> satisfiable by composer/composer[1.4.1].
- magento/product-community-edition 2.2.7 requires composer/composer 1.4.1 -> satisfiable by composer/composer[1.4.1].
- Conclusion: don't install composer/composer 1.4.1
- Installation request for magento/product-community-edition 2.2.7 -> satisfiable by magento/product-community-edition[2.2.7].
When I try the command line upgrade I just get memory errors due to forkbomb protection.
My composer version is 1.6.4 so newer than 1.4.1
The site is on shared hosting so I can't downgrade or upgrade composer.
magento2.2.6
magento2.2.6
edited yesterday
Abhishek Panchal
3,4122829
asked yesterday
Denial Design
8112
edited yesterday
Abhishek Panchal
3,4122829
asked yesterday
Denial Design
8112
edited yesterday
Abhishek Panchal
3,4122829
edited yesterday
Abhishek Panchal
3,4122829
edited yesterday
Abhishek Panchal
3,4122829
3,4122829
asked yesterday
Denial Design
8112
asked yesterday
Denial Design
8112
asked yesterday
Denial Design
8112
8112
Will deleting thevendorfolder and runningcomposer installandcomposer updatefix this?
– Denial Design
11 hours ago
add a comment |
Will deleting thevendorfolder and runningcomposer installandcomposer updatefix this?
– Denial Design
11 hours ago
Will deleting the
vendor folder and running composer install and composer update fix this?– Denial Design
11 hours ago
Will deleting the
vendor folder and running composer install and composer update fix this?– Denial Design
11 hours ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f256795%2ferror-when-upgrading-from-2-2-6-to-2-2-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f256795%2ferror-when-upgrading-from-2-2-6-to-2-2-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Will deleting the
vendorfolder and runningcomposer installandcomposer updatefix this?– Denial Design
11 hours ago