Title: passwordless coding configuration
Last modified: September 12, 2024

---

# passwordless coding configuration

 *  Resolved [klewis](https://wordpress.org/support/users/blackawxs/)
 * (@blackawxs)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/passwordless-coding-configuration/)
 * If I am intentionally getting this plugin for the purpose of using the passwordless
   add-on feature, does this plugin manipulate or write to the .htaccess file of
   WordPress behind the scenes, in order to function properly? or does it leave 
   that file alone? My WordPress hosting does not support .htaccess modifying.
    -  This topic was modified 1 year, 8 months ago by [klewis](https://wordpress.org/support/users/blackawxs/).

Viewing 1 replies (of 1 total)

 *  Plugin Author [Collins Agbonghama](https://wordpress.org/support/users/collizo4sky/)
 * (@collizo4sky)
 * [1 year, 8 months ago](https://wordpress.org/support/topic/passwordless-coding-configuration/#post-18011263)
 * No, it doesn’t manipulate .htaccess file. It does not even touch it.

Viewing 1 replies (of 1 total)

The topic ‘passwordless coding configuration’ is closed to new replies.

 * ![](https://ps.w.org/wp-user-avatar/assets/icon-256x256.png?rev=2532486)
 * [Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress](https://wordpress.org/plugins/wp-user-avatar/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-user-avatar/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-user-avatar/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-user-avatar/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-user-avatar/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-user-avatar/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Collins Agbonghama](https://wordpress.org/support/users/collizo4sky/)
 * Last activity: [1 year, 8 months ago](https://wordpress.org/support/topic/passwordless-coding-configuration/#post-18011263)
 * Status: resolved