cPanel & WHM Version 98 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!

Update PHP config editor to work with Magento 2.0 install requirements (-1, not "on" or "off")

Less Wright shared this idea 5 years ago
Not Planned

Anyone upgrading or installing Magento 2.0 will be blocked from using Cpanel to set the required PHP.ini setting via the PHP "advanced" config editor.


As part of installing Magento 2.0, the PHP.ini file is required to have the following setting:

Please open your php.ini file and set always_populate_raw_post_data to -1.


When you go to the 'advanced' edit page under WHM, it only allows you to set this setting (always_populate_raw_post_data) to either "On" or "Off".


The -1 is a new requirement so that, per the PHP docs:

"Setting always_populate_raw_post_data to -1 will opt into the new behaviour that will be implemented in a future version of PHP, in which $HTTP_RAW_POST_DATA is never defined."


Basically this setting is being phased out and to get the new behaviour, you have to set to -1.


However, WHM 'advanced' editor does not have an option to manually set this to -1.


Thus we, and all Magento 2.0 users to come, are effectively blocked from upgrading.


I can go in and manually edit the php.ini, but the concern is that WHM will simply overwrite this on the next reboot, etc. and we'll be back to a broken Magento 2.0 install.


Given that Magento 2.0 requires this, can you please update your editor to either allow a third -1 setting (vs. current "on" or "off", neither of which are sufficient for Magento 2.0), or else make it an open text box like other settings so we can manually update to -1?

Replies (2)

photo
1

Hi,


That UI is deprecated with EasyApache 4, and I don't think we'll be making any changes to the old PHP Configuration Editor. WHM will not override your php.ini file, which this editor adjusts. Any changes will be held through all EA rebuilds, etc. You can change this via the command line or another editor and it will stay for you.

photo
1

"WHM will not override your php.ini file"

The override was the main concern, otherwise directly editing Php.ini works great.


Thanks for the info!

Replies have been locked on this page!