Hook into parse_query instead: add_action( ‘parse_query’, function() { add_rewrite_rule( ‘go/([^/]+)/?$’, ‘index.php?redirect_to=$matches[1]’, ‘top’ ); add_rewrite_tag( “%redirect_to%”, ‘([^&]+)’ );` } ); Reason: init is too early, query_vars haven’t been set yet. wp_head is too late, no can redirect at that point.
I register custom post type on init action and the validate which I’m writing about is set to register_setting inside admin_init action. This is the key to your issue. You’re registering the custom post type, and presumably you’re setting up the rewrite rules in that registration. When you call flush_rewrite_rules(), the rules are rebuilt right … Read more
Got it to work, changing the regex from (.+) to (.*) Maybe helpful for others searching same rewrite on search and pagination. add_rewrite_rule(‘discover/interiors/interior-results/(.*)/page/([0-9]{1,})/?’, ‘index.php?pagename=discover/interiors/interior-results&tag1=$matches[1]&paged=$matches[2]’, ‘top’ ); add_rewrite_rule(‘discover/interiors/interior-results/(.*)’, ‘index.php?pagename=discover/interiors/interior-results&tag1=$matches[1]’, ‘top’ );
Simple way: In my plugins, register_activation_hook always have a line like delete_option(‘rewrite_rules’); when I’m creating custom post types. WordPress will properly rebuild them. I’ve provided a detailed answer Also another inspiring answer here
If you are in https://localhost/cc and use a relative lnk with href=”https://wordpress.stackexchange.com/login” (relative to current domain/site), the browser (not WordPress) will take you to https://localhost/login; if the link is href=”https://wordpress.stackexchange.com/questions/267557/login” (relative to current path) the browser will take you to https://localhost/cc/login. Relative links work like that, nothing to do with WordPress. That is why many … Read more
Flushing rules forces them to be rebuilt from whatever is currently registered, so you should register post types before flushing. This is why you must register your post types in a plugin activation hook as well as on init, otherwise your rules won’t exist on subsequent requests if you’re flushing on activation.
This is controlled by the with_front argument in your taxonomy registration code: register_taxonomy( ‘genre’, ‘artist’, array( ‘rewrite’ => array( ‘slug’ => ‘genre’, ‘with_front’ => false, // don’t prepend static prefix from post permalink ), // your other args… ) );
Setting the hierarchical property of the post type to true let’s you set parent posts for them: ‘hierarchical’ => true,
(Revised answer) So Let’s See The Issues With Your Rewrite Rule.. The first parameter passed to add_rewrite_rule() (which is the regular expression pattern) should not start with home_url() or any functions which outputs the website URL. So this is wrong: home_url() . ‘/car/([^/]*)/([^/]*)/?’ because the generated regular expression (RegEx) pattern would be: http://example.com/car/([^/]*)/([^/]*)/? which will … Read more
Solution would be a little tricky but you’re on the right path. You need to register taxonomy and post type with dynamic rewrite: function wpse346452_cpt() { register_taxonomy( ‘campaign’, ‘asset’, array( ‘label’ => ‘Campaing’ ) ); register_post_type( ‘asset’, array( ‘public’ => true, ‘label’ => ‘Asset’, ‘rewrite’ => array( ‘slug’ => ‘%campaign_name%’, ), ) ); } add_action( … Read more