You ran into a feature of WordPress known as Canonical Redirect. The idea is that each page on your website will only have one URL. But since it is possible to get to a page with a different URL, it will force a redirect to the “true” URL. The reason for this is to prevent … Read more
Placing the htaccess file in the wp-admin directory did not work for me so I went a different route and it seems to be working very well. Below is what I have in my main htaccess file: <files wp-login.php> # set up rule order order deny,allow # default deny deny from all allow from x.x.x.x … Read more
The solution is to put the rewriterule just after RewriteEngine On. <IfModule mod_rewrite.c> RewriteEngine On RewriteRule ^definicje(.*)$ http://example.com/single-page/ [R=301,L] RewriteBase / RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule>
If you’re outputting a sitemap, there’s no reason to wait for the query for your page- which is what is producing the redirect. Hook an earlier action and you won’t need anything to counter the trailing slash, because it won’t happen- EDIT Here’s a complete version with registering query vars, rules, and parse_request action: // … Read more
This sounds like it’s probably caused by mod-evasive (or similar) plugin in Apache (or similar), blocking multiple consecutive requests as it thinks you are trying to run a denial of service (DOS) attack against the server. Try disabling any security plugins (Apache / web server ones, not WordPr
Is this normal behaviour? Yes. On a default Apache install, only index.html is set as the DirectoryIndex (the default setting). Either in the appropriate <VirtualHost> container, or main server config you need to add a <Directory> section that specifically targets the defined document root directory. For example: DocumentRoot /var/www/html <Directory “/var/www/html”> # Allow public access … Read more
The .htaccess directives block any HTTP request not coming from your IP address. However, I believe WP Cron is also an HTTP request that originates from the server. So, you need to also make an exception for the server’s external IP address. These directives can also be simplified a bit… For example: RewriteCond %{REMOTE_ADDR} !=203.0.113.111 … Read more
The best way to “programatically redirect these links and keep [your] .htaccess file clean” would actually be with a plugin. I know you stated “without using a plugin,” but you’ll get the same functionality from a plugin that you would if you wrote the code yourself. And, considering how non-user-friendly the WP rewrite scripts are, … Read more
You can add extra rules right after the ^index\.php$ line via the WP_Rewrite class, more specifically the add_external_rule() method. They are added to the non_rewrite_rules array, which is written in the mod_rewrite_rules() method. This is a very simple example. You should still flush the rewrite rules (once), either on plugin activation or by visiting the … Read more
Read on htaccess. You can try this, <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^phones$ /?page_id=1081 [L] </IfModule>