Magento 2: System upgrade fails Readiness Check (always_populate_raw_post

Magento 2: System upgrade fails Readiness Check (always_populate_raw_post_data = 0)

I am trying to upgrade Magento 2.07 to 2.1. I pass all the checks apart from the one below:

Your PHP Version is 5.6.22, but always_populate_raw_post_data = 0. $HTTP_RAW_POST_DATA is deprecated from PHP 5.6 onwards and will be removed in PHP 7.0. This will stop the installer from running. Please open your php.ini file and set always_populate_raw_post_data to -1. If you need more help please call your hosting provider.

I had this problem on setup and got around it by editing my .user.ini by adding

always_populate_raw_post_data = -1

But this seems to be ignored by the upgrade utility. Any ideas? I am thinking it might be because my cron jobs are loading the server php.ini and not my .user.ini?

asked Jun 29 '16 at 21:29

caffeinehigh

3241721

bumped to the homepage by Community♦ yesterday

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

what does phpinfo() say? I have the same problem and if i check phpinfo() I see always_populate_raw_post_data -1 for both Local Value and Master Value.. but i still get the same error you get
– mrzhero
Jun 30 '16 at 7:22

1

Hi @mrzhero my phpinfo() says -1 for the local value. Which works perfect for the initial Magento 2 install. But the upgrade system seems to ignore this, possible bug I think. Since my store isn't very big I've just set up a fresh install of 2.1 and going to import everything in rather than keep pulling my hair out trying to get it to update.
– caffeinehigh
Jun 30 '16 at 20:03

1

You can try adding this to Magento's .htaccess: php_value always_populate_raw_post_data = -1. Issues like yours happen because there are typically at minimum two sets of PHP configurations: one for the PHP CLI and one for the web server. In addition, if you have multiple PHP versions installed, it gets more complicated.
– Steve Johnson
Jul 1 '16 at 16:16

@Steve Johnson I tried, still no luck. I made a test file that prints the output of $iniSetting = intVal(ini_get('always_populate_raw_post_data'));: the result is -1. When I run the Readiness Check however, it says always_populate_raw_post_data = 0.
– mrzhero
Jul 13 '16 at 14:59

add a comment |

I am trying to upgrade Magento 2.07 to 2.1. I pass all the checks apart from the one below:

Your PHP Version is 5.6.22, but always_populate_raw_post_data = 0. $HTTP_RAW_POST_DATA is deprecated from PHP 5.6 onwards and will be removed in PHP 7.0. This will stop the installer from running. Please open your php.ini file and set always_populate_raw_post_data to -1. If you need more help please call your hosting provider.

I had this problem on setup and got around it by editing my .user.ini by adding

always_populate_raw_post_data = -1

But this seems to be ignored by the upgrade utility. Any ideas? I am thinking it might be because my cron jobs are loading the server php.ini and not my .user.ini?

asked Jun 29 '16 at 21:29

caffeinehigh

3241721

bumped to the homepage by Community♦ yesterday

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

what does phpinfo() say? I have the same problem and if i check phpinfo() I see always_populate_raw_post_data -1 for both Local Value and Master Value.. but i still get the same error you get
– mrzhero
Jun 30 '16 at 7:22

1

Hi @mrzhero my phpinfo() says -1 for the local value. Which works perfect for the initial Magento 2 install. But the upgrade system seems to ignore this, possible bug I think. Since my store isn't very big I've just set up a fresh install of 2.1 and going to import everything in rather than keep pulling my hair out trying to get it to update.
– caffeinehigh
Jun 30 '16 at 20:03

1

You can try adding this to Magento's .htaccess: php_value always_populate_raw_post_data = -1. Issues like yours happen because there are typically at minimum two sets of PHP configurations: one for the PHP CLI and one for the web server. In addition, if you have multiple PHP versions installed, it gets more complicated.
– Steve Johnson
Jul 1 '16 at 16:16

@Steve Johnson I tried, still no luck. I made a test file that prints the output of $iniSetting = intVal(ini_get('always_populate_raw_post_data'));: the result is -1. When I run the Readiness Check however, it says always_populate_raw_post_data = 0.
– mrzhero
Jul 13 '16 at 14:59

add a comment |

I am trying to upgrade Magento 2.07 to 2.1. I pass all the checks apart from the one below:

Your PHP Version is 5.6.22, but always_populate_raw_post_data = 0. $HTTP_RAW_POST_DATA is deprecated from PHP 5.6 onwards and will be removed in PHP 7.0. This will stop the installer from running. Please open your php.ini file and set always_populate_raw_post_data to -1. If you need more help please call your hosting provider.

I had this problem on setup and got around it by editing my .user.ini by adding

always_populate_raw_post_data = -1

But this seems to be ignored by the upgrade utility. Any ideas? I am thinking it might be because my cron jobs are loading the server php.ini and not my .user.ini?

asked Jun 29 '16 at 21:29

caffeinehigh

3241721

I am trying to upgrade Magento 2.07 to 2.1. I pass all the checks apart from the one below:

Your PHP Version is 5.6.22, but always_populate_raw_post_data = 0. $HTTP_RAW_POST_DATA is deprecated from PHP 5.6 onwards and will be removed in PHP 7.0. This will stop the installer from running. Please open your php.ini file and set always_populate_raw_post_data to -1. If you need more help please call your hosting provider.

I had this problem on setup and got around it by editing my .user.ini by adding

always_populate_raw_post_data = -1

But this seems to be ignored by the upgrade utility. Any ideas? I am thinking it might be because my cron jobs are loading the server php.ini and not my .user.ini?

magento2 upgrade cron

asked Jun 29 '16 at 21:29

caffeinehigh

3241721

asked Jun 29 '16 at 21:29

caffeinehigh

3241721

asked Jun 29 '16 at 21:29

caffeinehigh

3241721

asked Jun 29 '16 at 21:29

caffeinehigh

3241721

asked Jun 29 '16 at 21:29

caffeinehigh

3241721

bumped to the homepage by Community♦ yesterday

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

bumped to the homepage by Community♦ yesterday

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

what does phpinfo() say? I have the same problem and if i check phpinfo() I see always_populate_raw_post_data -1 for both Local Value and Master Value.. but i still get the same error you get
– mrzhero
Jun 30 '16 at 7:22

1

Hi @mrzhero my phpinfo() says -1 for the local value. Which works perfect for the initial Magento 2 install. But the upgrade system seems to ignore this, possible bug I think. Since my store isn't very big I've just set up a fresh install of 2.1 and going to import everything in rather than keep pulling my hair out trying to get it to update.
– caffeinehigh
Jun 30 '16 at 20:03

1

You can try adding this to Magento's .htaccess: php_value always_populate_raw_post_data = -1. Issues like yours happen because there are typically at minimum two sets of PHP configurations: one for the PHP CLI and one for the web server. In addition, if you have multiple PHP versions installed, it gets more complicated.
– Steve Johnson
Jul 1 '16 at 16:16

@Steve Johnson I tried, still no luck. I made a test file that prints the output of $iniSetting = intVal(ini_get('always_populate_raw_post_data'));: the result is -1. When I run the Readiness Check however, it says always_populate_raw_post_data = 0.
– mrzhero
Jul 13 '16 at 14:59

add a comment |

what does phpinfo() say? I have the same problem and if i check phpinfo() I see always_populate_raw_post_data -1 for both Local Value and Master Value.. but i still get the same error you get
– mrzhero
Jun 30 '16 at 7:22

1

Hi @mrzhero my phpinfo() says -1 for the local value. Which works perfect for the initial Magento 2 install. But the upgrade system seems to ignore this, possible bug I think. Since my store isn't very big I've just set up a fresh install of 2.1 and going to import everything in rather than keep pulling my hair out trying to get it to update.
– caffeinehigh
Jun 30 '16 at 20:03

1

You can try adding this to Magento's .htaccess: php_value always_populate_raw_post_data = -1. Issues like yours happen because there are typically at minimum two sets of PHP configurations: one for the PHP CLI and one for the web server. In addition, if you have multiple PHP versions installed, it gets more complicated.
– Steve Johnson
Jul 1 '16 at 16:16

@Steve Johnson I tried, still no luck. I made a test file that prints the output of $iniSetting = intVal(ini_get('always_populate_raw_post_data'));: the result is -1. When I run the Readiness Check however, it says always_populate_raw_post_data = 0.
– mrzhero
Jul 13 '16 at 14:59

what does phpinfo() say? I have the same problem and if i check phpinfo() I see always_populate_raw_post_data -1 for both Local Value and Master Value.. but i still get the same error you get
– mrzhero
Jun 30 '16 at 7:22

Hi @mrzhero my phpinfo() says -1 for the local value. Which works perfect for the initial Magento 2 install. But the upgrade system seems to ignore this, possible bug I think. Since my store isn't very big I've just set up a fresh install of 2.1 and going to import everything in rather than keep pulling my hair out trying to get it to update.
– caffeinehigh
Jun 30 '16 at 20:03

You can try adding this to Magento's .htaccess: php_value always_populate_raw_post_data = -1. Issues like yours happen because there are typically at minimum two sets of PHP configurations: one for the PHP CLI and one for the web server. In addition, if you have multiple PHP versions installed, it gets more complicated.
– Steve Johnson
Jul 1 '16 at 16:16

@Steve Johnson I tried, still no luck. I made a test file that prints the output of $iniSetting = intVal(ini_get('always_populate_raw_post_data'));: the result is -1. When I run the Readiness Check however, it says always_populate_raw_post_data = 0.
– mrzhero
Jul 13 '16 at 14:59

add a comment |

1 Answer
1

active

oldest

votes

Found the problem on my server.

Check phpinfo() on your browser.

Check php -i | grep php.ini via SSH.

Compare the value of Loaded Configuration File: on my server, they were 2 different files. My host provider said they could change only the file I saw in phpinfo() and not the other one. Since Magento checks the value by running cron, it gets the configuration that I can't change.

So the only way for me was to bypass the checker.

I edited {magento_root}/setup/src/Magento/Setup/Model/PhpReadinessCheck.php:

private function checkPopulateRawPostSetting(){

    // HHVM and PHP 7does not support 'always_populate_raw_post_data' to be set to -1

    if (version_compare(PHP_VERSION, '7.0.0-beta') >= 0 || defined('HHVM_VERSION')) {

        return ;

}



return ; // <- THIS IS THE LINE I ADDED



[...]

After the cron jobs get executed, if you check {magento_root}/var/.setup_cronjob_status, you should see:

"php_settings_verified": {

        "responseType": "success",

        "data": 

    }

Run again the Readiness Check: the PHP Settings Check gets a green light.

Dirty workaround, but I don't know what else I can do.

answered Jul 13 '16 at 21:16

mrzhero

408149

Dirty workaround, yes. Since you're running Mage 2, why not use PHP 7.0 instead? They can run side-by-side like PHP 4 and 5 did for years on hosts.
– Brett
Jun 30 '17 at 3:28

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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f123493%2fmagento-2-system-upgrade-fails-readiness-check-always-populate-raw-post-data%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

Found the problem on my server.

Check phpinfo() on your browser.

Check php -i | grep php.ini via SSH.

So the only way for me was to bypass the checker.

I edited {magento_root}/setup/src/Magento/Setup/Model/PhpReadinessCheck.php:

private function checkPopulateRawPostSetting(){

    // HHVM and PHP 7does not support 'always_populate_raw_post_data' to be set to -1

    if (version_compare(PHP_VERSION, '7.0.0-beta') >= 0 || defined('HHVM_VERSION')) {

        return ;

}



return ; // <- THIS IS THE LINE I ADDED



[...]

After the cron jobs get executed, if you check {magento_root}/var/.setup_cronjob_status, you should see:

"php_settings_verified": {

        "responseType": "success",

        "data": 

    }

Run again the Readiness Check: the PHP Settings Check gets a green light.

Dirty workaround, but I don't know what else I can do.

answered Jul 13 '16 at 21:16

mrzhero

408149

Dirty workaround, yes. Since you're running Mage 2, why not use PHP 7.0 instead? They can run side-by-side like PHP 4 and 5 did for years on hosts.
– Brett
Jun 30 '17 at 3:28

add a comment |

Found the problem on my server.

Check phpinfo() on your browser.

Check php -i | grep php.ini via SSH.

So the only way for me was to bypass the checker.

I edited {magento_root}/setup/src/Magento/Setup/Model/PhpReadinessCheck.php:

private function checkPopulateRawPostSetting(){

    // HHVM and PHP 7does not support 'always_populate_raw_post_data' to be set to -1

    if (version_compare(PHP_VERSION, '7.0.0-beta') >= 0 || defined('HHVM_VERSION')) {

        return ;

}



return ; // <- THIS IS THE LINE I ADDED



[...]

After the cron jobs get executed, if you check {magento_root}/var/.setup_cronjob_status, you should see:

"php_settings_verified": {

        "responseType": "success",

        "data": 

    }

Run again the Readiness Check: the PHP Settings Check gets a green light.

Dirty workaround, but I don't know what else I can do.

answered Jul 13 '16 at 21:16

mrzhero

408149

Dirty workaround, yes. Since you're running Mage 2, why not use PHP 7.0 instead? They can run side-by-side like PHP 4 and 5 did for years on hosts.
– Brett
Jun 30 '17 at 3:28

add a comment |

Found the problem on my server.

Check phpinfo() on your browser.

Check php -i | grep php.ini via SSH.

So the only way for me was to bypass the checker.

I edited {magento_root}/setup/src/Magento/Setup/Model/PhpReadinessCheck.php:

private function checkPopulateRawPostSetting(){

    // HHVM and PHP 7does not support 'always_populate_raw_post_data' to be set to -1

    if (version_compare(PHP_VERSION, '7.0.0-beta') >= 0 || defined('HHVM_VERSION')) {

        return ;

}



return ; // <- THIS IS THE LINE I ADDED



[...]

After the cron jobs get executed, if you check {magento_root}/var/.setup_cronjob_status, you should see:

"php_settings_verified": {

        "responseType": "success",

        "data": 

    }

Run again the Readiness Check: the PHP Settings Check gets a green light.

Dirty workaround, but I don't know what else I can do.

answered Jul 13 '16 at 21:16

mrzhero

408149

Found the problem on my server.

Check phpinfo() on your browser.

Check php -i | grep php.ini via SSH.

So the only way for me was to bypass the checker.

I edited {magento_root}/setup/src/Magento/Setup/Model/PhpReadinessCheck.php:

private function checkPopulateRawPostSetting(){

    // HHVM and PHP 7does not support 'always_populate_raw_post_data' to be set to -1

    if (version_compare(PHP_VERSION, '7.0.0-beta') >= 0 || defined('HHVM_VERSION')) {

        return ;

}



return ; // <- THIS IS THE LINE I ADDED



[...]

After the cron jobs get executed, if you check {magento_root}/var/.setup_cronjob_status, you should see:

"php_settings_verified": {

        "responseType": "success",

        "data": 

    }

Run again the Readiness Check: the PHP Settings Check gets a green light.

Dirty workaround, but I don't know what else I can do.

answered Jul 13 '16 at 21:16

mrzhero

408149

answered Jul 13 '16 at 21:16

mrzhero

408149

answered Jul 13 '16 at 21:16

mrzhero

408149

answered Jul 13 '16 at 21:16

mrzhero

408149

Dirty workaround, yes. Since you're running Mage 2, why not use PHP 7.0 instead? They can run side-by-side like PHP 4 and 5 did for years on hosts.
– Brett
Jun 30 '17 at 3:28

add a comment |

Dirty workaround, yes. Since you're running Mage 2, why not use PHP 7.0 instead? They can run side-by-side like PHP 4 and 5 did for years on hosts.
– Brett
Jun 30 '17 at 3:28

Dirty workaround, yes. Since you're running Mage 2, why not use PHP 7.0 instead? They can run side-by-side like PHP 4 and 5 did for years on hosts.
– Brett
Jun 30 '17 at 3:28

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Mfrhtyj