phpinfo disabled but it's not in disable_functions

smatt

• July 28, 2016 04:15

Hi all, I've removed phpinfo from the disable_functions in the php.ini file (done through WHM's PHP config editor). I go to the phpinfo page but it still says it's disabled. I restarted Apache, no change. I rebooted the server, no change. phpinfo is not listed in disable_functions (after reboot). Is there another setting somewhere to enable/disable this? And on a related note but different note, I'm a little confused as to what should be in the disable_functions list. Most guides/tutorials say to put ini_set in there, but then common CMSs like Drupal won't work. Enable it on a per account basis, or for just within their own environment without opening a security risk? Any help on either appreciated.

• 

  Bdzzld

  • July 28, 2016 09:31

  Did you disable it in the correct php.ini file? Please check phpinfo() for the exact location of that file.

  0
• 

  smatt

  • July 28, 2016 09:51

  I can't check phpinfo(), it is disabled...! I'm trying to enable it. I removed it from disable_functions using WHM's PHP Configuration Editor. Verified the change was saved on CLI with grep phpinfo /usr/local/lib/php.ini - no result.

  0
• 

  Bdzzld

  • July 28, 2016 10:00

  Sorry smatt, I thought it was the other way around. php.ini is usually located @ /usr/local/lib/

  0
• 

  smatt

  • July 28, 2016 10:27

  ^ No problem. Any ideas on how to fix?

  0
• 

  Bdzzld

  • July 28, 2016 11:20

  You may need to view the php.ini file manually (via vi or pico) to see if it's actually overwritten. Sometimes there are multiple lines of disabled_functions

  0
• 

  smatt

  • July 28, 2016 11:37

  Yes I thought that might be the case too - checked for that, only one disable_functions row, phpinfo is definitely not there.

  0
• 

  smatt

  • July 28, 2016 16:05

  This has been resolved. Quirks of CageFS. After making a change to php.ini you have to force an update.

  0
• 

  cPanelMichael

  • July 28, 2016 17:39

  I'm happy to see the issue is now resolved. Thank you for updating us with the outcome.

  0

Please sign in to leave a comment.