Title: PHP.INI
Last modified: August 31, 2016

---

# PHP.INI

 *  [bcr8tive](https://wordpress.org/support/users/bcr8tive/)
 * (@bcr8tive)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/phpini-11/)
 * Hi. I’m not sure where it went, but when I first ran the update I had some message
   about appending the php.ini file?
 * I’m hoping this isn’t something required with this most recent update. I’m not
   comfortable with server side changes (if that’s what that is ?) – it’s really
   Greek to me. Is there something I HAVE to do now to the ini file for WF to run
   properly? OR will WF run straight out of the box as it has been…
 * I see that the interface has changed and I’m going to have to get accustomed 
   to all of the concatenating and reorganization – so I can understand what is 
   where, from where it used to be and what it’s doing etc –
 * Is there a user manual for all of these changes that we can refer to?
 * [https://wordpress.org/plugins/wordfence/](https://wordpress.org/plugins/wordfence/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [wfasa](https://wordpress.org/support/users/wfasa/)
 * (@wfasa)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/phpini-11/#post-7322167)
 * Hello bcr8tive,
    in most common server configurations Wordfence will run “straight
   out of the box”. The latest releases have a new feature called “Web Application
   Firewall” (WAF). It’s primary job is to intercept attacks before WordPress themes
   and plugins have loaded, thus significantly decreasing the risk of successful
   attacks. The Firewall needs to go through a quick configuration process which
   you do on the page “Firewall” which you can find in the Wordfence menu.
 * You do not have to use the Firewall. You can leave it deactivated or choose to
   not enable it. Wordfence will then continue to protect your site like it always
   has. It just wont have the extended protection that the new feature offers.
 * You can find more information about WAF [here](https://docs.wordfence.com/en/WAF).
   Let me know if you have any more questions.
 *  Thread Starter [bcr8tive](https://wordpress.org/support/users/bcr8tive/)
 * (@bcr8tive)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/phpini-11/#post-7322176)
 * Thank you so much for the clarification. Sounds like an extra layer of protection
   and a lot of additional effort on your part, so thanks for that too. I will read
   thru the link as time permits and try to implement it. Will check in if I run
   into any issues.
 * Thanks again! (waves) xo

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘PHP.INI’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [htaccess](https://wordpress.org/support/topic-tag/htaccess/)
 * [php.ini](https://wordpress.org/support/topic-tag/php-ini/)
 * [user manual](https://wordpress.org/support/topic-tag/user-manual/)
 * [version changes](https://wordpress.org/support/topic-tag/version-changes/)

 * 2 replies
 * 2 participants
 * Last reply from: [bcr8tive](https://wordpress.org/support/users/bcr8tive/)
 * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/phpini-11/#post-7322176)
 * Status: not resolved