The question is about doing this with .htaccess, but why not disabling author pages from within WordPress instead? This would achieve the same result while making the subdirectory concern irrelevant altogether (and also works regardless of permalink structure settings) Sample code that sets all urls to author pages to a 404 error: add_action( ‘template_redirect’, function() … Read more
Here are a couple of options: WP htaccess Control – will let you manually edit your .htaccess file All-in-one htaccess Plugin – will let you dynamically create an .htaccess file based on which modules/features you want set up When all else fails, turn to Google …
If you are using any CDN service like Cloudflare, then you can use the forwarding URL feature I mean you can set this rule: *example.com/* https://www.example.com/$2 this way, the HTTPS and www will be added to all URLs, this can be handled via web server too, but using a CDN service, will reduce the load … Read more
Here is what I have in my own .htaccess file that does what you’re looking for: # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On Options +FollowSymLinks RewriteBase / RewriteRule ^index\.php$ – [L] RewriteRule ^example.html$ /wp-content/raw/example.html [L] RewriteRule ^download$ /wp-content/raw/download-ebook.html [L] RewriteRule ^thanks$ /wp-content/raw/book-opt-in-thank-you.html [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # … Read more
By creating a physical directory the same as a (virtual) WordPress URL you have created a conflict. The URL needs to be routed through WP, but the default front-controller (the .htaccess code shown above) specifically excludes physical directories from being rewritten. The 403 Forbidden error comes about because you don’t have a directory index document … Read more
it opens the site in the domain Have you tested inner pages, not just the homepage? A seeming inconsistency in your config is that you have defined DocumentRoot /var/www/html/10_sites/ in your vHost(s) yet you have set RewriteBase /10_sites/ in your .htaccess file. Unless your site files are located in /var/www/html/10_sites/10_sites/ (yes, the last directory repeated … Read more
Assuming you’re on Linux, if you go to your wp-content/plugins folder and run grep -R ‘htaccess’ * it should let you know if any plugins are addressing that file by name
WordPress uses those markers to put its rules between. I never have and never would put custom rules in there. Check out insert_with_markers() and save_mod_rewrite_rules() in wp-admin/includes/misc.php Most notably this comment block which answers your question: /** * Inserts an array of strings into a file (.htaccess ), placing it between * BEGIN and END … Read more
My suggestion is: use the same standard .htaccess configuration for WordPress on a single domain in each WordPress directory. <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> Along with it, add a small CODE to make sure users are redirected to the … Read more
Before I give you the CODE, let me explain a few points: Point 1: It’s better if you only allow https links. Mixing http & https for the same content breaks the security added by https. With http, you can never be sure that your visitors are shown the same page you are providing from … Read more