Title: Manually Configuring iThemes
Last modified: August 22, 2016

---

# Manually Configuring iThemes

 *  [JoePhilpott](https://wordpress.org/support/users/joephilpott/)
 * (@joephilpott)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/manually-configuring-ithemes/)
 * Hi
 * I haven’t allowed iThemes Security to write to wp-config.php and .htaccess so
   I need to manually place configuration options in those files.
 * How do I do this? What do I add to these files?
 * Thanks
 * [https://wordpress.org/plugins/better-wp-security/](https://wordpress.org/plugins/better-wp-security/)

Viewing 1 replies (of 1 total)

 *  [gcampton](https://wordpress.org/support/users/gcampton/)
 * (@gcampton)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/manually-configuring-ithemes/#post-5523076)
 * On the iThemes dashboard, once you have all your required settings, scroll down
   until you see the htaccess code. Copy paste it in your .htaccess file and you’re
   done.
 * I wouldn’t go removing the code that’s already in the .htaccess (it should be
   the permalink code)

Viewing 1 replies (of 1 total)

The topic ‘Manually Configuring iThemes’ is closed to new replies.

 * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351)
 * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/)
 * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [gcampton](https://wordpress.org/support/users/gcampton/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/manually-configuring-ithemes/#post-5523076)
 * Status: not resolved