You’ve put the code in the wrong place. The HTTP to HTTPS directives must go before the WordPress front-controller, otherwise it’s simply never going to get processed for anything other than direct file requests. Your custom directives should also be outside the # BEGIN WordPress block, otherwise WordPress itself is likely to override your directives … Read more
In short yes… ‘External’ Rewrite Rules If in add_rewrite_rule the rule is isn’t directed to index.php then the rule is treated as an ‘external’ rule (i.e. not to be processed by WordPress’ internal handing of rewrites) and instead written to the .htaccess file. I.e. if: add_rewrite_rule(‘^nutrition/([^/]*)/([^/]*)/?’,’somethingelse.php?p=12&food=$1 &variety=$2′,’top’); is used instead of add_rewrite_rule(‘^nutrition/([^/]*)/([^/]*)/?’,’index.php?p=12&food=$matches[1]&variety=$matches[2]’,’top’); Then the rule … Read more
The protection from .htaccess is for the folder /wp-admin it’s not for the URL Open up your ftp programme (or download WordPress) and look inside /wp-admin By only allowing your IP access this folder you’re blocking a lot of possible exploit issues (as mentioned in comments below). I always prefer to login at mysite.com/wp-admin and … Read more
I wouldn’t use htaccess for that. What I would do is make a ‘download page’ template and use it to ‘serve’ the files. By doing that, I can do a check with is_user_logged_in() Codex and redirect with wp_login_url() Codex Just do: if ( is_user_logged_in() ) : //file link else : wp_login_url(); endif; I think it’s … Read more
Check to see if a person is logged in: <IfModule mod_rewrite.c> RewriteCond %{REQUEST_FILENAME} (.*) RewriteCond %{HTTP_COOKIE} !wordpress_logged_in_([a-zA-Z0-9_]*) [NC] RewriteRule .* – [F,L] </IfModule> The same applies as it did 10 years ago. This code in .htaccess doesn’t have anything to do with how WordPress might be setting cookies. And this does not “check to see … Read more
The best way to deal with Form Posts in WordPress is to use a special endpoint, /wp-admin/admin-post.php. POST data can be messed up, both by the WP Query call, and by any redirects that happen. So you set up your form with this action: <form action=”<?= admin_url(‘admin-post.php’) ?>” method=”post”> <input type=”hidden” name=”action” value=”special_action”> <?php wp_nonce_field(‘special_action_nonce’, … Read more
The .htaccess file is not actually required for WordPress to “work”. However, it is required if you wish to create a more user-friendly URL structure (ie. anything other than “plain” permalinks, as Jack suggests). This is also why the default WordPress .htaccess file surrounds the directives in an <IfModule mod_rewrite.c> container. It “works” if “mod_rewrite” … Read more
You could set up a multisite installation with sunrise configuration. This would allow you to manage one installation for your multiple domains. Be sure your hosting is ready for it.
As you’ve discovered WordPress ignores rewrite rules added into your .htaccess file manually. Not many people actually know WordPress has in-built functions, a core rewriting class that allows you to add custom rewrite rules into your themes functions.php file. You can read up on the WP_Rewrite class here and if you do a search on … Read more
This .htaccess file looks like it is for a network that uses sub-folders but the URL address that you say you are trying is for a network that uses sub-domains. Which type are you using? Have you followed the steps in the /wp-admin/network/setup.php page correctly? Another idea is that you have added SSL but the … Read more