Upgrade laravel












0














Hello after I installed Laravel,
I try to update the version 5.5 to 5.6 and unable to throws me an error:
- laravel/framework v5.6.9 requires php ^7.1.3 -> your PHP version (7.0.10) does not satisfy that requirement.



I use XAMPP with PHP 7.2.10.
I installed Composer with php 7 And does not help.
Thanks










share|improve this question






















  • on your cmd you can run php -v to see the actual version. Due to mutiple php installation, sometimes it happens.
    – Tuhin
    Nov 18 '18 at 13:37










  • If I check in CMD registered PHP 7.0.10 . But in path C:xamppphp I get PHP 7.2.10 . How to coordinate their sons? Project Save On XAMPP folder. Thanks for the quick reply.
    – YairBaruch
    Nov 18 '18 at 13:45


















0














Hello after I installed Laravel,
I try to update the version 5.5 to 5.6 and unable to throws me an error:
- laravel/framework v5.6.9 requires php ^7.1.3 -> your PHP version (7.0.10) does not satisfy that requirement.



I use XAMPP with PHP 7.2.10.
I installed Composer with php 7 And does not help.
Thanks










share|improve this question






















  • on your cmd you can run php -v to see the actual version. Due to mutiple php installation, sometimes it happens.
    – Tuhin
    Nov 18 '18 at 13:37










  • If I check in CMD registered PHP 7.0.10 . But in path C:xamppphp I get PHP 7.2.10 . How to coordinate their sons? Project Save On XAMPP folder. Thanks for the quick reply.
    – YairBaruch
    Nov 18 '18 at 13:45
















0












0








0







Hello after I installed Laravel,
I try to update the version 5.5 to 5.6 and unable to throws me an error:
- laravel/framework v5.6.9 requires php ^7.1.3 -> your PHP version (7.0.10) does not satisfy that requirement.



I use XAMPP with PHP 7.2.10.
I installed Composer with php 7 And does not help.
Thanks










share|improve this question













Hello after I installed Laravel,
I try to update the version 5.5 to 5.6 and unable to throws me an error:
- laravel/framework v5.6.9 requires php ^7.1.3 -> your PHP version (7.0.10) does not satisfy that requirement.



I use XAMPP with PHP 7.2.10.
I installed Composer with php 7 And does not help.
Thanks







php laravel






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 18 '18 at 13:32









YairBaruchYairBaruch

33




33












  • on your cmd you can run php -v to see the actual version. Due to mutiple php installation, sometimes it happens.
    – Tuhin
    Nov 18 '18 at 13:37










  • If I check in CMD registered PHP 7.0.10 . But in path C:xamppphp I get PHP 7.2.10 . How to coordinate their sons? Project Save On XAMPP folder. Thanks for the quick reply.
    – YairBaruch
    Nov 18 '18 at 13:45




















  • on your cmd you can run php -v to see the actual version. Due to mutiple php installation, sometimes it happens.
    – Tuhin
    Nov 18 '18 at 13:37










  • If I check in CMD registered PHP 7.0.10 . But in path C:xamppphp I get PHP 7.2.10 . How to coordinate their sons? Project Save On XAMPP folder. Thanks for the quick reply.
    – YairBaruch
    Nov 18 '18 at 13:45


















on your cmd you can run php -v to see the actual version. Due to mutiple php installation, sometimes it happens.
– Tuhin
Nov 18 '18 at 13:37




on your cmd you can run php -v to see the actual version. Due to mutiple php installation, sometimes it happens.
– Tuhin
Nov 18 '18 at 13:37












If I check in CMD registered PHP 7.0.10 . But in path C:xamppphp I get PHP 7.2.10 . How to coordinate their sons? Project Save On XAMPP folder. Thanks for the quick reply.
– YairBaruch
Nov 18 '18 at 13:45






If I check in CMD registered PHP 7.0.10 . But in path C:xamppphp I get PHP 7.2.10 . How to coordinate their sons? Project Save On XAMPP folder. Thanks for the quick reply.
– YairBaruch
Nov 18 '18 at 13:45














3 Answers
3






active

oldest

votes


















0














Have a look at your composer.json. It is possible that there is a configuration parameter config.platform.php which contains the value 7.0.10. This feature allows to simulate a specific PHP version to composer. If you don't need it, you can remove it or force composer to install anyway by using the --ignore-platform-reqs parameter when updating the packages.






share|improve this answer





















  • Thank you i'm run $ composer update --ignore-platform-reqs and it's work!
    – YairBaruch
    Nov 18 '18 at 13:59










  • The php version dependency is there because Laravel is using features that were introduced in that version. Telling composer to ignore the dependency might allow it to install, but will cause it to fail during runtime whenever a page is requested that uses one of those unsupported features
    – Travis Britz
    Nov 18 '18 at 15:19












  • @TravisBritz Surely that has to be kept in mind. But as the author mentioned he is on v7.2.10, I'd assumed that will be no problem.
    – Namoshek
    Nov 18 '18 at 16:03










  • In cases where a package requires an arbitrary php version it's a fine solution, but in this case Laravel actually does need php 7.1 for some components. Since they're getting this error it indicates that v7.2.10 isn't actually being used, so ignoring the version requirement just hides the error until it causes issues later, instead of fixing the cause (some kind of misconfiguration).
    – Travis Britz
    Nov 18 '18 at 16:18










  • I get your point, but that's already part of my answer as well (and to be precise, my answer starts with that). It's just that I don't like repeating what other answers or comments already pointed out.
    – Namoshek
    Nov 18 '18 at 16:21



















0














If you are on Linux Debian, you can easily install the latest version of php with sudo apt-get install php x.x. On windows, this link might help. Then, try installing or upgrading Laravel from cmd and it should work sweet! Re-installing the latest verion of XAMPP may also do the work for you.






share|improve this answer





















  • Thanks for the quick reply. I use Windows 10.
    – YairBaruch
    Nov 18 '18 at 13:46



















0














You have to update your system's PATH environment variable so that it finds the newer version of php from your command line. You might have more than one installed right now, so it uses the first one it finds when it looks through the directories defined in your PATH. After updating the path variable, you might have to log out for it to apply.



You can check the version used by your command line with php --version. To see which version Apache is configured with, use phpinfo().






share|improve this answer





















  • Many thanks very much. It works.
    – YairBaruch
    Nov 19 '18 at 8:13











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53361422%2fupgrade-laravel%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Have a look at your composer.json. It is possible that there is a configuration parameter config.platform.php which contains the value 7.0.10. This feature allows to simulate a specific PHP version to composer. If you don't need it, you can remove it or force composer to install anyway by using the --ignore-platform-reqs parameter when updating the packages.






share|improve this answer





















  • Thank you i'm run $ composer update --ignore-platform-reqs and it's work!
    – YairBaruch
    Nov 18 '18 at 13:59










  • The php version dependency is there because Laravel is using features that were introduced in that version. Telling composer to ignore the dependency might allow it to install, but will cause it to fail during runtime whenever a page is requested that uses one of those unsupported features
    – Travis Britz
    Nov 18 '18 at 15:19












  • @TravisBritz Surely that has to be kept in mind. But as the author mentioned he is on v7.2.10, I'd assumed that will be no problem.
    – Namoshek
    Nov 18 '18 at 16:03










  • In cases where a package requires an arbitrary php version it's a fine solution, but in this case Laravel actually does need php 7.1 for some components. Since they're getting this error it indicates that v7.2.10 isn't actually being used, so ignoring the version requirement just hides the error until it causes issues later, instead of fixing the cause (some kind of misconfiguration).
    – Travis Britz
    Nov 18 '18 at 16:18










  • I get your point, but that's already part of my answer as well (and to be precise, my answer starts with that). It's just that I don't like repeating what other answers or comments already pointed out.
    – Namoshek
    Nov 18 '18 at 16:21
















0














Have a look at your composer.json. It is possible that there is a configuration parameter config.platform.php which contains the value 7.0.10. This feature allows to simulate a specific PHP version to composer. If you don't need it, you can remove it or force composer to install anyway by using the --ignore-platform-reqs parameter when updating the packages.






share|improve this answer





















  • Thank you i'm run $ composer update --ignore-platform-reqs and it's work!
    – YairBaruch
    Nov 18 '18 at 13:59










  • The php version dependency is there because Laravel is using features that were introduced in that version. Telling composer to ignore the dependency might allow it to install, but will cause it to fail during runtime whenever a page is requested that uses one of those unsupported features
    – Travis Britz
    Nov 18 '18 at 15:19












  • @TravisBritz Surely that has to be kept in mind. But as the author mentioned he is on v7.2.10, I'd assumed that will be no problem.
    – Namoshek
    Nov 18 '18 at 16:03










  • In cases where a package requires an arbitrary php version it's a fine solution, but in this case Laravel actually does need php 7.1 for some components. Since they're getting this error it indicates that v7.2.10 isn't actually being used, so ignoring the version requirement just hides the error until it causes issues later, instead of fixing the cause (some kind of misconfiguration).
    – Travis Britz
    Nov 18 '18 at 16:18










  • I get your point, but that's already part of my answer as well (and to be precise, my answer starts with that). It's just that I don't like repeating what other answers or comments already pointed out.
    – Namoshek
    Nov 18 '18 at 16:21














0












0








0






Have a look at your composer.json. It is possible that there is a configuration parameter config.platform.php which contains the value 7.0.10. This feature allows to simulate a specific PHP version to composer. If you don't need it, you can remove it or force composer to install anyway by using the --ignore-platform-reqs parameter when updating the packages.






share|improve this answer












Have a look at your composer.json. It is possible that there is a configuration parameter config.platform.php which contains the value 7.0.10. This feature allows to simulate a specific PHP version to composer. If you don't need it, you can remove it or force composer to install anyway by using the --ignore-platform-reqs parameter when updating the packages.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 18 '18 at 13:41









NamoshekNamoshek

2,9362719




2,9362719












  • Thank you i'm run $ composer update --ignore-platform-reqs and it's work!
    – YairBaruch
    Nov 18 '18 at 13:59










  • The php version dependency is there because Laravel is using features that were introduced in that version. Telling composer to ignore the dependency might allow it to install, but will cause it to fail during runtime whenever a page is requested that uses one of those unsupported features
    – Travis Britz
    Nov 18 '18 at 15:19












  • @TravisBritz Surely that has to be kept in mind. But as the author mentioned he is on v7.2.10, I'd assumed that will be no problem.
    – Namoshek
    Nov 18 '18 at 16:03










  • In cases where a package requires an arbitrary php version it's a fine solution, but in this case Laravel actually does need php 7.1 for some components. Since they're getting this error it indicates that v7.2.10 isn't actually being used, so ignoring the version requirement just hides the error until it causes issues later, instead of fixing the cause (some kind of misconfiguration).
    – Travis Britz
    Nov 18 '18 at 16:18










  • I get your point, but that's already part of my answer as well (and to be precise, my answer starts with that). It's just that I don't like repeating what other answers or comments already pointed out.
    – Namoshek
    Nov 18 '18 at 16:21


















  • Thank you i'm run $ composer update --ignore-platform-reqs and it's work!
    – YairBaruch
    Nov 18 '18 at 13:59










  • The php version dependency is there because Laravel is using features that were introduced in that version. Telling composer to ignore the dependency might allow it to install, but will cause it to fail during runtime whenever a page is requested that uses one of those unsupported features
    – Travis Britz
    Nov 18 '18 at 15:19












  • @TravisBritz Surely that has to be kept in mind. But as the author mentioned he is on v7.2.10, I'd assumed that will be no problem.
    – Namoshek
    Nov 18 '18 at 16:03










  • In cases where a package requires an arbitrary php version it's a fine solution, but in this case Laravel actually does need php 7.1 for some components. Since they're getting this error it indicates that v7.2.10 isn't actually being used, so ignoring the version requirement just hides the error until it causes issues later, instead of fixing the cause (some kind of misconfiguration).
    – Travis Britz
    Nov 18 '18 at 16:18










  • I get your point, but that's already part of my answer as well (and to be precise, my answer starts with that). It's just that I don't like repeating what other answers or comments already pointed out.
    – Namoshek
    Nov 18 '18 at 16:21
















Thank you i'm run $ composer update --ignore-platform-reqs and it's work!
– YairBaruch
Nov 18 '18 at 13:59




Thank you i'm run $ composer update --ignore-platform-reqs and it's work!
– YairBaruch
Nov 18 '18 at 13:59












The php version dependency is there because Laravel is using features that were introduced in that version. Telling composer to ignore the dependency might allow it to install, but will cause it to fail during runtime whenever a page is requested that uses one of those unsupported features
– Travis Britz
Nov 18 '18 at 15:19






The php version dependency is there because Laravel is using features that were introduced in that version. Telling composer to ignore the dependency might allow it to install, but will cause it to fail during runtime whenever a page is requested that uses one of those unsupported features
– Travis Britz
Nov 18 '18 at 15:19














@TravisBritz Surely that has to be kept in mind. But as the author mentioned he is on v7.2.10, I'd assumed that will be no problem.
– Namoshek
Nov 18 '18 at 16:03




@TravisBritz Surely that has to be kept in mind. But as the author mentioned he is on v7.2.10, I'd assumed that will be no problem.
– Namoshek
Nov 18 '18 at 16:03












In cases where a package requires an arbitrary php version it's a fine solution, but in this case Laravel actually does need php 7.1 for some components. Since they're getting this error it indicates that v7.2.10 isn't actually being used, so ignoring the version requirement just hides the error until it causes issues later, instead of fixing the cause (some kind of misconfiguration).
– Travis Britz
Nov 18 '18 at 16:18




In cases where a package requires an arbitrary php version it's a fine solution, but in this case Laravel actually does need php 7.1 for some components. Since they're getting this error it indicates that v7.2.10 isn't actually being used, so ignoring the version requirement just hides the error until it causes issues later, instead of fixing the cause (some kind of misconfiguration).
– Travis Britz
Nov 18 '18 at 16:18












I get your point, but that's already part of my answer as well (and to be precise, my answer starts with that). It's just that I don't like repeating what other answers or comments already pointed out.
– Namoshek
Nov 18 '18 at 16:21




I get your point, but that's already part of my answer as well (and to be precise, my answer starts with that). It's just that I don't like repeating what other answers or comments already pointed out.
– Namoshek
Nov 18 '18 at 16:21













0














If you are on Linux Debian, you can easily install the latest version of php with sudo apt-get install php x.x. On windows, this link might help. Then, try installing or upgrading Laravel from cmd and it should work sweet! Re-installing the latest verion of XAMPP may also do the work for you.






share|improve this answer





















  • Thanks for the quick reply. I use Windows 10.
    – YairBaruch
    Nov 18 '18 at 13:46
















0














If you are on Linux Debian, you can easily install the latest version of php with sudo apt-get install php x.x. On windows, this link might help. Then, try installing or upgrading Laravel from cmd and it should work sweet! Re-installing the latest verion of XAMPP may also do the work for you.






share|improve this answer





















  • Thanks for the quick reply. I use Windows 10.
    – YairBaruch
    Nov 18 '18 at 13:46














0












0








0






If you are on Linux Debian, you can easily install the latest version of php with sudo apt-get install php x.x. On windows, this link might help. Then, try installing or upgrading Laravel from cmd and it should work sweet! Re-installing the latest verion of XAMPP may also do the work for you.






share|improve this answer












If you are on Linux Debian, you can easily install the latest version of php with sudo apt-get install php x.x. On windows, this link might help. Then, try installing or upgrading Laravel from cmd and it should work sweet! Re-installing the latest verion of XAMPP may also do the work for you.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 18 '18 at 13:41









Mukesh AryalMukesh Aryal

12




12












  • Thanks for the quick reply. I use Windows 10.
    – YairBaruch
    Nov 18 '18 at 13:46


















  • Thanks for the quick reply. I use Windows 10.
    – YairBaruch
    Nov 18 '18 at 13:46
















Thanks for the quick reply. I use Windows 10.
– YairBaruch
Nov 18 '18 at 13:46




Thanks for the quick reply. I use Windows 10.
– YairBaruch
Nov 18 '18 at 13:46











0














You have to update your system's PATH environment variable so that it finds the newer version of php from your command line. You might have more than one installed right now, so it uses the first one it finds when it looks through the directories defined in your PATH. After updating the path variable, you might have to log out for it to apply.



You can check the version used by your command line with php --version. To see which version Apache is configured with, use phpinfo().






share|improve this answer





















  • Many thanks very much. It works.
    – YairBaruch
    Nov 19 '18 at 8:13
















0














You have to update your system's PATH environment variable so that it finds the newer version of php from your command line. You might have more than one installed right now, so it uses the first one it finds when it looks through the directories defined in your PATH. After updating the path variable, you might have to log out for it to apply.



You can check the version used by your command line with php --version. To see which version Apache is configured with, use phpinfo().






share|improve this answer





















  • Many thanks very much. It works.
    – YairBaruch
    Nov 19 '18 at 8:13














0












0








0






You have to update your system's PATH environment variable so that it finds the newer version of php from your command line. You might have more than one installed right now, so it uses the first one it finds when it looks through the directories defined in your PATH. After updating the path variable, you might have to log out for it to apply.



You can check the version used by your command line with php --version. To see which version Apache is configured with, use phpinfo().






share|improve this answer












You have to update your system's PATH environment variable so that it finds the newer version of php from your command line. You might have more than one installed right now, so it uses the first one it finds when it looks through the directories defined in your PATH. After updating the path variable, you might have to log out for it to apply.



You can check the version used by your command line with php --version. To see which version Apache is configured with, use phpinfo().







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 18 '18 at 15:32









Travis BritzTravis Britz

1,04446




1,04446












  • Many thanks very much. It works.
    – YairBaruch
    Nov 19 '18 at 8:13


















  • Many thanks very much. It works.
    – YairBaruch
    Nov 19 '18 at 8:13
















Many thanks very much. It works.
– YairBaruch
Nov 19 '18 at 8:13




Many thanks very much. It works.
– YairBaruch
Nov 19 '18 at 8:13


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53361422%2fupgrade-laravel%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

How to send String Array data to Server using php in android

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

Is anime1.com a legal site for watching anime?