There are two types of rewrite rules you can generate via the API and add_rewrite_rule: internal rules and external rules. External rules get inserted into your .htaccess file, and must be in a format that can be parsed by Apache’s mod_rewrite. Internal rules get added to the WordPress internal rewrite rule array and must be … Read more
I’d say either change the order, put (2) before (1), or be more specific with the rules. E.g. from/([a-zA-Z]*)/?
I am new to WordPress rewrites, so after some StackExchange reading i have figured it out. All rewrites should be passed to index.php, then i can call the page that i want to redirect to, like this: function custom_rewrite_basic() { add_rewrite_rule( ‘validate_data.php’, ‘index.php?pagename=validate-data’, ‘top’ ); } add_action( ‘init’, ‘custom_rewrite_basic’ ); In addition i wanted to … Read more
flush_rewrite_rules is firing, but it’s too late; the previous rewrite setting has already determined your register_post_type args at the start of the request, so you’re just flushing the “old” rules. You could try re-registering the post type just before flushing, but I’m not sure of the wider implications or even if this will work. If … Read more
on the rewrite flush, the rewrite rule created by the custom post type overwrite yours because the target is the same. to avoid this, you can use this filter const TAXONOMY_PUBLICACOES = “publicacoes”; add_filter(TAXONOMY_PUBLICACOES . “_rewrite_rules”, function ($rules) { unset($rules[“publicacoes/(.+?)/page/?([0-9]{1,})/?$”]); return $rules; });
In the pl_custom_rewrite_rules() function, change the REGEX pattern to ^new_slug/(.*)$ as in: add_rewrite_rule( ‘^new_slug/(.*)$’, ‘index.php?name=$matches[1]’, ‘top’ ); because WordPress strips the preceeding / from the request path (WP::$request), so using the ^/new_slug never evaluates to true. Additionally, in the pl_custom_permalink() function, remove the global $post; line because the function already receiving the proper post data … Read more
It’s not showing up because internal rewrites must point to index.php. This isn’t your theme’s index.php file, it’s the main root WordPress bootstrap file. This is how WP detects what should be an internal rule (parsed in PHP) and an external rule (added to htaccess). The other issue you will have is that page_name isn’t … Read more
In WordPress, the request path, e.g. path/to/something as in example.com/path/to/something?query=string&if=any, is saved in WP::$request which is accessible via the global $wp variable, so in your case, you can do so to check if the page is /dashboard/products: global $wp; // Note: No trailing slashes. $is_my_page = ( ‘dashboard/products’ === $wp->request ); // Or without the … Read more
Okay! So I got this working by just changing the rewrite_rule to include the event… function aca_award_cat_rewrite_rule() { add_rewrite_rule( ‘^awards/([^/]*)/award-category/([^/]*)/?’, ‘index.php?competition=$matches[1]&award_category=$matches[2]’, ‘top’ ); }
Is that correct? It’s correct that rules with a $after value of top (or anything other than bottom) will be placed above all other rules (that have been registered by the time your code runs). However, the rules would actually be in the same order add_rewrite_rule() is called, so as for the ones in question, … Read more