[Plugin: Stealth Login] StealthLogin working – Common .htaccess mistakes
-
There are a lot of topics regarding the broken functionality of this plugin, but I have successfully installed this plugin on numerous WP sites, and recently ran into an issue with it not functioning properly on a new site. Turns out there are two issues that I had to correct, which I suspect are two common mistakes that are leading to so many negative comments in the forums.
1. Be sure that .htaccess files are not being ignored by your web server. In the appropriate Apache conf file (varies for your setup), use the AllowOverride directive to allow the use of .htaccess files in your WordPress site’s directory.
AllowOverride All
2. The .htaccess code that is generated by Stealth Login does not add a crucial piece of code for the rewrite functionality to work. Be sure to add the following before all of the Stealth Login code:
RewriteEngine On
Duh! If your site didn’t have the need for an .htaccess file before (new sites typically), chances are you wouldn’t have the RewriteEngine turned on. StealthLogin’s code requires this to function properly.
- The topic ‘[Plugin: Stealth Login] StealthLogin working – Common .htaccess mistakes’ is closed to new replies.