Mar 7, 2016
20
1
3
Bristol
cPanel Access Level
Root Administrator
Hmm, today I set it back to use PHP-FPM in the UI and it works ok.

I was setting it up as per the guide in the documentation rather than just setting it to 'On' in WHM MultiPHP.

Does setting it as 'On' in MultiPHP create all the files and sockets as needed? Maybe there was a clash when I created the files manually?
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,909
2,229
463
Mar 7, 2016
20
1
3
Bristol
cPanel Access Level
Root Administrator
Yes, I took the exact steps there for php56, everything exactly as it says with the right user and domain used in filenames.

When I enabled it again yesterday and thought it was working, it turns out it was not. My blog started throwing all sorts of PHP errors about strict standards, yet it was the same PHP version as before. If I turn on PHP-FPM in WHM for my site, I get strict/deprecated errors, if I turn it off I don't. This seem wrong, PHP-FPM should be in no way effecting the rules and configuration of my PHP files.

Deprecated: Non-static method Concrete5_Model_Config::get() should not be called statically, assuming $this from incompatible context in /home/pixelhero/public_html/concrete/core/models/user.php on line 103

Strict Standards: Declaration of Concrete5_Model_Page::add() should be compatible with Concrete5_Model_Collection::add($data) in /home/pixelhero/public_html/concrete/core/models/page.php on line 12

Strict Standards: Declaration of Concrete5_Model_Page::duplicate() should be compatible with Concrete5_Model_Collection::duplicate() in /home/pixelhero/public_html/concrete/core/models/page.php on line 12

Deprecated: Non-static method Concrete5_Model_CollectionVersion::get() should not be called statically, assuming $this from incompatible context in /home/pixelhero/public_html/concrete/core/models/collection.php on line 32

These are not showing when I disable PHP-FPM.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,909
2,229
463
Hello Richard,

I've moved these posts into a separate thread to ensure it's handled appropriately.

Internal case EA-5425 is open to address an issue where the default PHP-FPM configuration values override the global php.ini configuration values. I'll update this thread with more information on the status of this case as it becomes available. In the meantime, the temporary workaround is to manually edit the PHP-FPM configuration file for the domain name.

In regards to making custom changes to PHP INI directives for domains using PHP-FPM, we have a resource on this topic at:

Tutorial - Managing php.ini directives with PHP-FPM

Thank you.
 
Last edited: