You might just need to flush permalinks. (Navigate to Settings > Permalinks and click “Save Changes”) If you can’t navigate to the permalinks page because of the error, you could try one of the other suggestions here Obviously make a backup of your database before performing any of them. If that doesn’t work there may … Read more
In order to catch either lang=en or lang=ru you can change those directives like this: RewriteCond %{QUERY_STRING} lang=(en|ru) # exclude all requests starting with /wp-admin/ RewriteCond %{REQUEST_URI} !^/wp-admin/ RewriteRule (.*) /%1/$1? [L,R=302] The (en|ru) part matches either en or ru and the surrounding parentheses make this a capturing group that can be referenced later. The … Read more
Assuming the redirect is for a resource or page that does not exist then you are most probably better off using a redirect plugin, not .htaccess, in order to prioritise “normal site visitors” and not the redirected traffic. With a redirect plugin, the redirect logic need only be processed for requests that would otherwise return … Read more
You’ll need the Header set …. directive, but to set it conditionally based on the URL. One way of doing this is to use mod_rewrite to set an environment variable (eg. ROBOTS_INDEX) when your URL criteria are met (for the URLs you want indexed) and use the env= argument to the Header directive to conditionally … Read more
To redirect just those 3 URLs (with variable ticket number) on the support subdomain then you can do something like the following before the WordPress front-controller (assuming the support subdomain resolves to the same place and is probably handled by WP) using mod_rewrite, in the root .htaccess file: RewriteCond %{HTTP_HOST} ^support\.example\.com [NC] RewriteRule ^((?:a/)?ticket/\d+)?$ https://support.example1.com/$0 … Read more
You could do something like the following in .htaccess before the existing WordPress directives. RewriteCond %{QUERY_STRING} ^uri=(/[^&]+) RewriteRule ^nextgen-share/(\d+/\d+)/full$ %1#gallery/$1 [QSD,NE,R,L] The RewriteRule pattern only matches against the URL-path, so you need the preceding RewriteCond directive in order to match the query string portion of the URL. If the /121212/8989/ part always consists of 6 … Read more
You appear to be lazy-loading responsive images, so whether the insecure images load (or rather “blocked”) is dependent on screen size. You have many data-srcset attributes that reference http:// – these also appear to reference your non-canonical “domain apex” (ie. example.com), as opposed to the canonical hostname with a www subdomain (ie. www.example.com), so these … Read more
Ordinarily, requests for physical directories (and files) are not routed to WordPress. You could make an exception for this one folder (or URL) and specifically rewrite requests for /connect to index.php (the WordPress front-controller). Try the following before the # BEGIN WordPress section: # Override directory RewriteRule ^connect index.php [L]
This would seem to be a “fault” of the way WordPress (the “server”) is reading the HTTP request headers. (If they are being read into an associative array without any normalisation then the comparison will naturally be case-sensitive.) This should arguably be “fixed” in WP. However, it’s possible to create a “workaround” in .htaccess and … Read more
At the top of your root .htaccess file (before the WordPress front-controller) add the following: # Redirect from /subdirectory/<anything> to `/<anything>` RewriteRule ^subdirectory/(.*) /$1 [R=302,L] Change the 302 (temporary) to 301 (permanent) only once you have confirmed it works OK in order to avoid caching issues. UPDATE: If I wanted to add a further rewrite … Read more