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
I accidentally found a solution. I was using a local XAMPP installation and there was no way around it. Though when I uploaded the site to a live server it worked fine. I hope this helps someone in the future. I’ve seen a lot of people with the same issue but never saw a solution…
Inbound vs Outbound links: I guess it’ll be helpful to clarify these concepts: Inbound links = links from another website to your own website. Outbound links = links from your website to another website. An external link would be any link that points to any domain other than the domain the link exists on. From … 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
There is a simple approach to hold download access on your file. 1. Using .htaccess: Upload a .htaccess file into your wp-content folder. Have a look if one exists already, then append this code to the end of the file. If you don’t have one, just create a new blank file and add this code … Read more
wp-admin-canonical is broken, as it assumes how WordPress is installed. there was a plugin to fix it, but the plugin was removed from the plugin repository apparently. It is still on github and pluginmirror though: https://github.com/wp-plugins/remove-wp-canonical-url-admin-hack http://www.pluginmirror.com/plugins/remove-wp-canonical-url-admin-hack/
Even though static files and directories do work with a mod_rewrite’d wordpress installation in the servers root you might need to exclude your CodeIgniter subdirectory from that mod_rewrite lineup. You can do so by placing an additional .htaccess file into the CodeIgniter directory and disable mod_rewrite in there: <IfModule mod_rewrite.c> RewriteEngine off </IfModule> Related: apache … 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
Replace Redirect 301 / http://newsite.com/ by RewriteRule ^(.*)$ http://newsite.com/ [L,R=301]
So, the canonical URL is https://example.com/…. (You appear to be describing a pointless intermediary redirect? You should only redirect to the final canonical URL, no need for anything in between.) This is just a standard HTTP to HTTPS redirect. You can do this using mod_rewrite at the top of your .htaccess file. For example: RewriteEngine … Read more