Just do it in your .htaccess, it will be alot simpler. The important thing is that the rules are above WordPress’ rules. Setting L also states, that this shall be the last rule evaluated if a match was found # Redirect to https RewriteEngine On RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L] # Redirect non-www … Read more
Try using wp_redirect($url). See https://developer.wordpress.org/reference/functions/wp_redirect/ . So…something like: // set up the URL to redirect to $redirect_to = ‘https://www.example.com/page’; wp_redirect($redirect_to); exit; Note that exit is required to close out the code. See the docs in the above link.
It’s because you have set the Referrer Policy header incorrectly set in the W3TC page cache. Referrer Policy This header restricts the values of the referer header in outbound links. **Directive: same-origin** …will fix it. If your overall Directive is “same-origin” and you set the Referrer header to something different (such as “origin”), this error … Read more
So I’m not sure why that RewriteRule returned a 404 error for you, because I’ve tested it and it did work as expected — if permalinks are actually enabled, you would be redirected to the actual post permalink. And here’s the content of my .htaccess file: RewriteEngine On RewriteRule ^go/(\d+)$ /?p=$1 [R=302,L] # BEGIN WordPress … Read more
You can use conditional tag is_404() and wp action hook to redirect whenever the page can not be found. functions.php add_action( ‘wp’, ‘se344018_redirect_404’ ); function se344018_redirect_404() { if ( is_404() ) { wp_redirect( home_url() ); // // wp_redirect( home_url(‘some/page-slug’) ); exit; } }
The problem is not with WordPress — it does generate the proper permalink, be the post assigned to just grandson or son and father. It’s just that for the latter, the “chosen” category could be either son or father, but not both — and if it’s son (which has a parent category), then the permalink … Read more
To achieve this you don’t need the .htaccess in the servers directory itself. You can remove this and apache can use rules in the root WordPress .htaccess to do the rewrite you need, and you can usefully keep rewrite rules for your site in one place. You need a couple of rules to make this … Read more
You can use the following code: add_action( ‘request’, function( $request ){ if( empty( $request ) ){ wp_safe_redirect( get_home_url() . ‘/lunchtime-results/’ ); exit; } return $request; }); This can be added to your theme’s functions.php file. The code checks the current request arguments. When visiting the home page the request is empty; in all other cases … Read more
a) Would that work, and b) would this code be an acceptable way of doing it? Yes. But you should put the custom directive (the Redirect line) above the BEGIN marker, i.e. the # BEGIN WordPress line, because if not, then your custom directive will be gone when the WordPress rewrite rules are flushed/regenerated. So: … Read more
search is a reserved term, and should not be used as a query variable. The presence of any reserved query variable tells WordPress that the current query must be for something other than the front page, so it interprets it as an an archive query of some sort. The reason you get redirected to the … Read more