Ok guys, I did further research. Basically, all I had to do was add “Satisfy Any” argument. So the main .htaccess file looked like the one I posted in my initial thread. Then for the specific folder, I created a new .htaccess file (/folder/.htaccess). Then added this: <Files wp-login.php> Satisfy Any </Files> Much thanks to … Read more
Comment out the following by adding hash tags before it #RewriteCond %{REQUEST_URI} !^/images/ #RewriteCond %{REQUEST_URI} !^/images #RewriteCond %{REQUEST_URI} !.*images(.*) and see if that helps.
You ask: How does that work ? As far as I can read it, it only specifies not to rewrite certain urls (using -), These files are included within the WordPress PHP scripts, so there’s no need to access them in the browser, but notice the rewrite flags. Here’s some information on the F, L … Read more
When a URL is processed by WordPress, its index.php script is loaded with the path to the requested page. Because in this case the index.php script is always found, a normal 404 error will never trigger (via ErrorDocument 404 …). If the requested URL does not match a page that WP knows about, WP will … Read more
Put this in your .htaccess file after your password protection on the entire site: <Files “page.php”> Allow from all Satisfy any
How do we add a second IP address that is allowed to see the site in development? We can just append just second REMOTE_ADDR like this since the default flag is [AND] # BEGIN Maintenance <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{REMOTE_ADDR} !^11\.111\.111\.11$ #First Address RewriteCond %{REMOTE_ADDR} !^123\.45\.67\.89$ #Second Address RewriteCond %{REQUEST_URI} !^/maintenance\.html$ RewriteRule … Read more
IP address validation during authentication – for a selected user only Here’s a way to hook into the authenticate filter and validate the IP address for a given user during authentication. The user can see the invalid IP address error like shown here: /** * Validate IP Address During Authentication – For A Given User … Read more
I found a simple plugin that did the job for me. This is what my .htaccess file looks like now for my sub-domain: <IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{HTTPS} !=on [NC] RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] # BEGIN WordPress #RewriteEngine On RewriteBase / RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php … Read more
I solved it by logging in into admin panel and saving site URL with a trailing slash at the end.
When the directive is included as part of the WordPress directives It simply needs to go before the WordPress front-controller. In fact, you should not include this as “part of the WordPress directives” as WP itself tries to maintain this block of code and could override your custom directives in a future update. You should … Read more