Title: Ninja php.ini vs. Default php.ini
Last modified: August 30, 2016

---

# Ninja php.ini vs. Default php.ini

 *  Resolved [basis104](https://wordpress.org/support/users/basis104/)
 * (@basis104)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/ninja-phpini-vs-default-phpini/)
 * Hi,
 * I ran into a htaccess/php.ini problem on a WHM/cPanel based shared hosting Apache
   server (su_PHP). The php based shop of a customer (in a subdir of public_html
   where also WP is located) stopped working and we had no idea why. Also another
   customer asked me why I changed the default upload file size to 3M…
 * This lead to the conclusion that the php.ini by Ninjafirewall results in setting
   php defaults instead of the stuff set in the global server php.ini for the whole
   hosting account with all subdirs. After copying all lines from /usr/local/lib/
   php.ini into the Ninja php.ini in the customer’s public_html, everything worked
   well again.
 * Now of course I would like to automaically adopt all changes to the server global
   php config without having to copy and paste every couple of months from the global
   php.ini to the dozens of local Ninja php.inis. Is there a possibilty to load 
   the global php.ini “into” the Ninja php.ini or a WHM/cPanel setting I might have
   missed?
 * Thanks.
 * [https://wordpress.org/plugins/ninjafirewall/](https://wordpress.org/plugins/ninjafirewall/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/)
 * (@nintechnet)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/ninja-phpini-vs-default-phpini/#post-6890628)
 * Hi,
 * I don’t know if you can use `SetEnv PHP_INI_SCAN_DIR` instead of `suPHP_ConfigPath`,
   as it would load the server INI and then the one included in the PHP_INI_SCAN_DIR(
   which could point to the home folder).
 * Otherwise, here is a thread from cPanel forum about php.ini and suPHP: [Methods to Increase Security on suPHP – Restricting who can use php.ini files](https://forums.cpanel.net/threads/methods-to-increase-security-on-suphp-restricting-who-can-use-php-ini-files.167186/)

Viewing 1 replies (of 1 total)

The topic ‘Ninja php.ini vs. Default php.ini’ is closed to new replies.

 * ![](https://ps.w.org/ninjafirewall/assets/icon-256x256.png?rev=976137)
 * [NinjaFirewall (WP Edition) - Advanced Security Plugin and Firewall](https://wordpress.org/plugins/ninjafirewall/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ninjafirewall/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ninjafirewall/)
 * [Active Topics](https://wordpress.org/support/plugin/ninjafirewall/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ninjafirewall/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ninjafirewall/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [nintechnet](https://wordpress.org/support/users/nintechnet/)
 * Last activity: [10 years, 5 months ago](https://wordpress.org/support/topic/ninja-phpini-vs-default-phpini/#post-6890628)
 * Status: resolved