You can revert to the default WordPress rewrite rules. This line already handles checking for existing physical directories: RewriteCond %{REQUEST_FILENAME} !-d Your problem does not lie with WordPress, but with some other problem with your server/htaccess files. You have not provided enough information to solve your problem, but it probably is an issue with file … Read more
I think you should take a step back and clarify what you are actually trying to do. Usually with WordPress there is no need to throw around with crazy redirects, virtual pages and file includes. Although you can do all these things (mentioning WP_Rewrite). When all you want is passing parameters to a page all … Read more
Please change the permissions of .htaccess to read-only by accessing it via SFTP, SSH, cPanel ‘File Manager’ or whatever the tool you have.
There are rewrite rules involved, so I believe the order does indeed matter. Your suggested order looks correct.
Be aware, the AJAX file admin-ajax.php is in the wp-admin directory too. So I guess your site is using AJAX to send requests in the background to the admin directory. Clicking it away lets the AJAX request fail, but the error isn’t displayed. Change the .htaccess to: AuthType Basic AuthName ‘YOUR_AUTH_NAME’ AuthUserFile PATH_TO_HTPASSWORD <Files ‘*’> … Read more
With localhost, you need to make sure that your mod_rewrite is on. You can do this in your httpd.conf file in MAMP. MAMP > CONF > APACHE > ORIGINAL > httpd.conf. Uncomment this line: LoadModule rewrite_module modules/mod_rewrite.so
More reliable will be allowing specific IP instead of domain using REMOTE_ADDR header. You can use HTTP_REFERRER header but it is not reliable. You can do it via using rest_authentication_errors filter. add_filter( ‘rest_authentication_errors’, ‘wpse150207_filter_incoming_connections’ ); function wpse150207_filter_incoming_connections( $errors ){ $allowed_ips = array( ‘127.0.0.1’ ); $request_server = $_SERVER[‘REMOTE_ADDR’]; if( ! in_array( $request_server, $allowed_ips ) ) return … Read more
You might have edited your .htaccess file in Windows notepad or text editor. If you did use Windows text editor then it must have added some special chars in .htaccess file and that will lead to 500 internal server error. Never edit in Windows text editor. Use notepad++ for editing .htaccess and .htpasswd files.
In my experience you don’t need to mess with .htaccess with a WordPress site. Just set the General Settings -> “WordPress Address” and “Site Address” to the preferred version (www or non www) and WordPress takes care of the redirection for you.
You can add a RewriteRule to your .htaccess to instruct mod_rewrite to stop processing any URI that begins with Staff/ or resolves to Staff: # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ – [L] RewriteRule ^/?Staff(/|$) – [END,NC] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> In effect, this … Read more