Error Magento 2.3.0 upgrade ( php requirement )
I'm upgrading Magento from 2.2.7 to 2.3.0 from composer.
Running in sequence
php bin/magento maintenance:enable
composer require magento/product-community-edition 2.3.0 --no-update
composer update
In the console I read several lines of error with sentences like
magento/framework 100.1.15 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.1.23) does not satisfy that requirement.
Can only install one of: magento/framework[102.0.0, 101.0.0].
I'm using php v7.1.23 and https://magento.com/tech-resources/download don't say nothing about issue on v 7.1.x.
So i don't understand why the upgrade isn't compatible.
How does this problem happen? Do I need to upgrade to php v7.2?
upgrade php-7 magento2.3 magento2.3.0
add a comment |
I'm upgrading Magento from 2.2.7 to 2.3.0 from composer.
Running in sequence
php bin/magento maintenance:enable
composer require magento/product-community-edition 2.3.0 --no-update
composer update
In the console I read several lines of error with sentences like
magento/framework 100.1.15 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.1.23) does not satisfy that requirement.
Can only install one of: magento/framework[102.0.0, 101.0.0].
I'm using php v7.1.23 and https://magento.com/tech-resources/download don't say nothing about issue on v 7.1.x.
So i don't understand why the upgrade isn't compatible.
How does this problem happen? Do I need to upgrade to php v7.2?
upgrade php-7 magento2.3 magento2.3.0
Can you please check if one of your extensions requiresmagento/framework 100.1.*
in its composer.json?
– sv3n
Nov 30 '18 at 16:11
In the error message there are lines like - modulo_x 1.0.0 requires magento/framework ~100.1.0|^101.0.0 -> satisfiable by magento/framework[101.0.7, 100.1.0, 100.1.1, 100.1.2, 100.1.3, 100.1.4..]
– Alfredo Lanzetta
Dec 3 '18 at 7:38
add a comment |
I'm upgrading Magento from 2.2.7 to 2.3.0 from composer.
Running in sequence
php bin/magento maintenance:enable
composer require magento/product-community-edition 2.3.0 --no-update
composer update
In the console I read several lines of error with sentences like
magento/framework 100.1.15 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.1.23) does not satisfy that requirement.
Can only install one of: magento/framework[102.0.0, 101.0.0].
I'm using php v7.1.23 and https://magento.com/tech-resources/download don't say nothing about issue on v 7.1.x.
So i don't understand why the upgrade isn't compatible.
How does this problem happen? Do I need to upgrade to php v7.2?
upgrade php-7 magento2.3 magento2.3.0
I'm upgrading Magento from 2.2.7 to 2.3.0 from composer.
Running in sequence
php bin/magento maintenance:enable
composer require magento/product-community-edition 2.3.0 --no-update
composer update
In the console I read several lines of error with sentences like
magento/framework 100.1.15 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.1.23) does not satisfy that requirement.
Can only install one of: magento/framework[102.0.0, 101.0.0].
I'm using php v7.1.23 and https://magento.com/tech-resources/download don't say nothing about issue on v 7.1.x.
So i don't understand why the upgrade isn't compatible.
How does this problem happen? Do I need to upgrade to php v7.2?
upgrade php-7 magento2.3 magento2.3.0
upgrade php-7 magento2.3 magento2.3.0
asked Nov 30 '18 at 16:02
Alfredo LanzettaAlfredo Lanzetta
115
115
Can you please check if one of your extensions requiresmagento/framework 100.1.*
in its composer.json?
– sv3n
Nov 30 '18 at 16:11
In the error message there are lines like - modulo_x 1.0.0 requires magento/framework ~100.1.0|^101.0.0 -> satisfiable by magento/framework[101.0.7, 100.1.0, 100.1.1, 100.1.2, 100.1.3, 100.1.4..]
– Alfredo Lanzetta
Dec 3 '18 at 7:38
add a comment |
Can you please check if one of your extensions requiresmagento/framework 100.1.*
in its composer.json?
– sv3n
Nov 30 '18 at 16:11
In the error message there are lines like - modulo_x 1.0.0 requires magento/framework ~100.1.0|^101.0.0 -> satisfiable by magento/framework[101.0.7, 100.1.0, 100.1.1, 100.1.2, 100.1.3, 100.1.4..]
– Alfredo Lanzetta
Dec 3 '18 at 7:38
Can you please check if one of your extensions requires
magento/framework 100.1.*
in its composer.json?– sv3n
Nov 30 '18 at 16:11
Can you please check if one of your extensions requires
magento/framework 100.1.*
in its composer.json?– sv3n
Nov 30 '18 at 16:11
In the error message there are lines like - modulo_x 1.0.0 requires magento/framework ~100.1.0|^101.0.0 -> satisfiable by magento/framework[101.0.7, 100.1.0, 100.1.1, 100.1.2, 100.1.3, 100.1.4..]
– Alfredo Lanzetta
Dec 3 '18 at 7:38
In the error message there are lines like - modulo_x 1.0.0 requires magento/framework ~100.1.0|^101.0.0 -> satisfiable by magento/framework[101.0.7, 100.1.0, 100.1.1, 100.1.2, 100.1.3, 100.1.4..]
– Alfredo Lanzetta
Dec 3 '18 at 7:38
add a comment |
4 Answers
4
active
oldest
votes
I had the same issue with php version conflict. In my case, I had to uninstall and install the php as upgrading via command line still caused the issue. Hope that helps!
Which php version currently you're using?
– Ashish Viradiya
Dec 6 '18 at 6:18
add a comment |
i think you'll have to not pass the --no-update
flag -- that tells composer to not update related packages.
magento/framework
in m2.3 requires "php": "~7.1.3||~7.2.0"
so that should resolve your issue.
If I remove--no-update
this error show up: Can only install one of: temando/module-shipping-m2[1.4.6, 1.3.7]. Installation request for magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0]. etc
– Alfredo Lanzetta
Dec 3 '18 at 7:53
add a comment |
Follow instructions as detailed in documentation https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
add a comment |
I had the exact same problem. In my case part of the problem was that there are 2 Braintree extensions, one that is built in and is advanced. Gene writes both but the 2nd has Apple Pay included. The 2nd one is not compatible with 2.3.0 right now. I was able to get Magento 2.2.6 to 2.3.0 upgrade to work after a lot of trial and error. Here is the procedure I followed.
Obviously backup everything first. I did it on a development copy first.
- Update all extensions
- run composer remove gene/module-braintree & composer remove paypal/module-braintree
- composer update
- composer require magento/module-braintree
- composer update
- Install Magento 2.2.7 (cannot go directly to 2.3.0)
- compile, deploy and clean caches - check it works
- Install Magento 2.3.0 by following these instructions, but DON'T run the composer update command. Make sure you remove the update folder and do that step, even though it says optional. https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
- Edit the composer.json file in the root.Remove any 3rd party repositories. Also remove any extensions you don't need. I found Sendgrid and Bronto were not compatible with 2.3 and only had to remove those. You will know if you try run "composer update" if it gives you any errors.
- Run composer update
- Once Magento 2.3.0 is installed, I found that it would not run any bin/magento commands. This was fixed by flushing redis. May be different for your server but mine was.
redis-cli -s /var/run/redis-multi-a751baae.redis/redis.sock -n 0 FLUSHDB - compile, deploy and clear caches
- I use WeltPixel Pearl theme and had to update that now for the site to work properly again.
I found one other issue with swatches not displaying and followed the instructions here to fix https://github.com/magento/magento2/issues/19688
Good Luck!
add a comment |
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%2f252015%2ferror-magento-2-3-0-upgrade-php-requirement%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same issue with php version conflict. In my case, I had to uninstall and install the php as upgrading via command line still caused the issue. Hope that helps!
Which php version currently you're using?
– Ashish Viradiya
Dec 6 '18 at 6:18
add a comment |
I had the same issue with php version conflict. In my case, I had to uninstall and install the php as upgrading via command line still caused the issue. Hope that helps!
Which php version currently you're using?
– Ashish Viradiya
Dec 6 '18 at 6:18
add a comment |
I had the same issue with php version conflict. In my case, I had to uninstall and install the php as upgrading via command line still caused the issue. Hope that helps!
I had the same issue with php version conflict. In my case, I had to uninstall and install the php as upgrading via command line still caused the issue. Hope that helps!
answered Nov 30 '18 at 18:58
rightnowtodayrightnowtoday
212
212
Which php version currently you're using?
– Ashish Viradiya
Dec 6 '18 at 6:18
add a comment |
Which php version currently you're using?
– Ashish Viradiya
Dec 6 '18 at 6:18
Which php version currently you're using?
– Ashish Viradiya
Dec 6 '18 at 6:18
Which php version currently you're using?
– Ashish Viradiya
Dec 6 '18 at 6:18
add a comment |
i think you'll have to not pass the --no-update
flag -- that tells composer to not update related packages.
magento/framework
in m2.3 requires "php": "~7.1.3||~7.2.0"
so that should resolve your issue.
If I remove--no-update
this error show up: Can only install one of: temando/module-shipping-m2[1.4.6, 1.3.7]. Installation request for magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0]. etc
– Alfredo Lanzetta
Dec 3 '18 at 7:53
add a comment |
i think you'll have to not pass the --no-update
flag -- that tells composer to not update related packages.
magento/framework
in m2.3 requires "php": "~7.1.3||~7.2.0"
so that should resolve your issue.
If I remove--no-update
this error show up: Can only install one of: temando/module-shipping-m2[1.4.6, 1.3.7]. Installation request for magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0]. etc
– Alfredo Lanzetta
Dec 3 '18 at 7:53
add a comment |
i think you'll have to not pass the --no-update
flag -- that tells composer to not update related packages.
magento/framework
in m2.3 requires "php": "~7.1.3||~7.2.0"
so that should resolve your issue.
i think you'll have to not pass the --no-update
flag -- that tells composer to not update related packages.
magento/framework
in m2.3 requires "php": "~7.1.3||~7.2.0"
so that should resolve your issue.
answered Nov 30 '18 at 18:22
Mark ShustMark Shust
517714
517714
If I remove--no-update
this error show up: Can only install one of: temando/module-shipping-m2[1.4.6, 1.3.7]. Installation request for magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0]. etc
– Alfredo Lanzetta
Dec 3 '18 at 7:53
add a comment |
If I remove--no-update
this error show up: Can only install one of: temando/module-shipping-m2[1.4.6, 1.3.7]. Installation request for magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0]. etc
– Alfredo Lanzetta
Dec 3 '18 at 7:53
If I remove
--no-update
this error show up: Can only install one of: temando/module-shipping-m2[1.4.6, 1.3.7]. Installation request for magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0]. etc– Alfredo Lanzetta
Dec 3 '18 at 7:53
If I remove
--no-update
this error show up: Can only install one of: temando/module-shipping-m2[1.4.6, 1.3.7]. Installation request for magento/product-community-edition 2.3.0 -> satisfiable by magento/product-community-edition[2.3.0]. etc– Alfredo Lanzetta
Dec 3 '18 at 7:53
add a comment |
Follow instructions as detailed in documentation https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
add a comment |
Follow instructions as detailed in documentation https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
add a comment |
Follow instructions as detailed in documentation https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
Follow instructions as detailed in documentation https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
answered Dec 3 '18 at 6:27
Allen InfanteAllen Infante
729
729
add a comment |
add a comment |
I had the exact same problem. In my case part of the problem was that there are 2 Braintree extensions, one that is built in and is advanced. Gene writes both but the 2nd has Apple Pay included. The 2nd one is not compatible with 2.3.0 right now. I was able to get Magento 2.2.6 to 2.3.0 upgrade to work after a lot of trial and error. Here is the procedure I followed.
Obviously backup everything first. I did it on a development copy first.
- Update all extensions
- run composer remove gene/module-braintree & composer remove paypal/module-braintree
- composer update
- composer require magento/module-braintree
- composer update
- Install Magento 2.2.7 (cannot go directly to 2.3.0)
- compile, deploy and clean caches - check it works
- Install Magento 2.3.0 by following these instructions, but DON'T run the composer update command. Make sure you remove the update folder and do that step, even though it says optional. https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
- Edit the composer.json file in the root.Remove any 3rd party repositories. Also remove any extensions you don't need. I found Sendgrid and Bronto were not compatible with 2.3 and only had to remove those. You will know if you try run "composer update" if it gives you any errors.
- Run composer update
- Once Magento 2.3.0 is installed, I found that it would not run any bin/magento commands. This was fixed by flushing redis. May be different for your server but mine was.
redis-cli -s /var/run/redis-multi-a751baae.redis/redis.sock -n 0 FLUSHDB - compile, deploy and clear caches
- I use WeltPixel Pearl theme and had to update that now for the site to work properly again.
I found one other issue with swatches not displaying and followed the instructions here to fix https://github.com/magento/magento2/issues/19688
Good Luck!
add a comment |
I had the exact same problem. In my case part of the problem was that there are 2 Braintree extensions, one that is built in and is advanced. Gene writes both but the 2nd has Apple Pay included. The 2nd one is not compatible with 2.3.0 right now. I was able to get Magento 2.2.6 to 2.3.0 upgrade to work after a lot of trial and error. Here is the procedure I followed.
Obviously backup everything first. I did it on a development copy first.
- Update all extensions
- run composer remove gene/module-braintree & composer remove paypal/module-braintree
- composer update
- composer require magento/module-braintree
- composer update
- Install Magento 2.2.7 (cannot go directly to 2.3.0)
- compile, deploy and clean caches - check it works
- Install Magento 2.3.0 by following these instructions, but DON'T run the composer update command. Make sure you remove the update folder and do that step, even though it says optional. https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
- Edit the composer.json file in the root.Remove any 3rd party repositories. Also remove any extensions you don't need. I found Sendgrid and Bronto were not compatible with 2.3 and only had to remove those. You will know if you try run "composer update" if it gives you any errors.
- Run composer update
- Once Magento 2.3.0 is installed, I found that it would not run any bin/magento commands. This was fixed by flushing redis. May be different for your server but mine was.
redis-cli -s /var/run/redis-multi-a751baae.redis/redis.sock -n 0 FLUSHDB - compile, deploy and clear caches
- I use WeltPixel Pearl theme and had to update that now for the site to work properly again.
I found one other issue with swatches not displaying and followed the instructions here to fix https://github.com/magento/magento2/issues/19688
Good Luck!
add a comment |
I had the exact same problem. In my case part of the problem was that there are 2 Braintree extensions, one that is built in and is advanced. Gene writes both but the 2nd has Apple Pay included. The 2nd one is not compatible with 2.3.0 right now. I was able to get Magento 2.2.6 to 2.3.0 upgrade to work after a lot of trial and error. Here is the procedure I followed.
Obviously backup everything first. I did it on a development copy first.
- Update all extensions
- run composer remove gene/module-braintree & composer remove paypal/module-braintree
- composer update
- composer require magento/module-braintree
- composer update
- Install Magento 2.2.7 (cannot go directly to 2.3.0)
- compile, deploy and clean caches - check it works
- Install Magento 2.3.0 by following these instructions, but DON'T run the composer update command. Make sure you remove the update folder and do that step, even though it says optional. https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
- Edit the composer.json file in the root.Remove any 3rd party repositories. Also remove any extensions you don't need. I found Sendgrid and Bronto were not compatible with 2.3 and only had to remove those. You will know if you try run "composer update" if it gives you any errors.
- Run composer update
- Once Magento 2.3.0 is installed, I found that it would not run any bin/magento commands. This was fixed by flushing redis. May be different for your server but mine was.
redis-cli -s /var/run/redis-multi-a751baae.redis/redis.sock -n 0 FLUSHDB - compile, deploy and clear caches
- I use WeltPixel Pearl theme and had to update that now for the site to work properly again.
I found one other issue with swatches not displaying and followed the instructions here to fix https://github.com/magento/magento2/issues/19688
Good Luck!
I had the exact same problem. In my case part of the problem was that there are 2 Braintree extensions, one that is built in and is advanced. Gene writes both but the 2nd has Apple Pay included. The 2nd one is not compatible with 2.3.0 right now. I was able to get Magento 2.2.6 to 2.3.0 upgrade to work after a lot of trial and error. Here is the procedure I followed.
Obviously backup everything first. I did it on a development copy first.
- Update all extensions
- run composer remove gene/module-braintree & composer remove paypal/module-braintree
- composer update
- composer require magento/module-braintree
- composer update
- Install Magento 2.2.7 (cannot go directly to 2.3.0)
- compile, deploy and clean caches - check it works
- Install Magento 2.3.0 by following these instructions, but DON'T run the composer update command. Make sure you remove the update folder and do that step, even though it says optional. https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html
- Edit the composer.json file in the root.Remove any 3rd party repositories. Also remove any extensions you don't need. I found Sendgrid and Bronto were not compatible with 2.3 and only had to remove those. You will know if you try run "composer update" if it gives you any errors.
- Run composer update
- Once Magento 2.3.0 is installed, I found that it would not run any bin/magento commands. This was fixed by flushing redis. May be different for your server but mine was.
redis-cli -s /var/run/redis-multi-a751baae.redis/redis.sock -n 0 FLUSHDB - compile, deploy and clear caches
- I use WeltPixel Pearl theme and had to update that now for the site to work properly again.
I found one other issue with swatches not displaying and followed the instructions here to fix https://github.com/magento/magento2/issues/19688
Good Luck!
answered yesterday
user3608473user3608473
211
211
add a comment |
add a comment |
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%2f252015%2ferror-magento-2-3-0-upgrade-php-requirement%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
Can you please check if one of your extensions requires
magento/framework 100.1.*
in its composer.json?– sv3n
Nov 30 '18 at 16:11
In the error message there are lines like - modulo_x 1.0.0 requires magento/framework ~100.1.0|^101.0.0 -> satisfiable by magento/framework[101.0.7, 100.1.0, 100.1.1, 100.1.2, 100.1.3, 100.1.4..]
– Alfredo Lanzetta
Dec 3 '18 at 7:38